Hi Heng,

Thanks for the update. We’re happy to help you, feel free to reach out anytime.

Regards,
Mahesh

Hi @User_HFXQV,

Please cross check the Match Type (MATC) field in F43121, if it is updated by value 4, then you have to re-receipt the PO as previous receipt was reversed.

The match type field (data item MATC) is the key to understanding the records in F43121.

• Match type 1 (MT1): The line was received.
• Match type 2 (MT2): The line was voucher/matched. This is a new record in addition to the MT1.
• Match type 3: The voucher was deleted. When you delete a voucher, the MT2 record is overwritten to a MT3.
• Match type 4: The receipt was reversed. When you reverse a receipt, the MT1 record is overwritten to a MT4.
• Match type 5: This MT must be manually entered through a file utility such as DFU. This is usually done because a purchasing voucher was deleted in A/P and manual corrections had to be made.

If data item MATC is update as 1 in F43121 for this case, I recommend raising a Service Request, so we can review your configuration in detail and investigate further.

Regards,
Mahesh

Hi @User_406JL,

Please follow steps to generate correct NN Sequence in India Localization:

1. In P0002 take form exit to "NN by CO/Y" and set up the next number for your legal company and a document type, say RI.
2. In the Processing Option of the application P7420565 set the document type to RI.
3. In the Processing Option of R42565, under the Default tab set the Document type to some dummy document type, say CC. Ensure that the document type specified in the Processing Option of R42565 is different from the one specified in the Processing Option of P7420565.
4. Set the Processing Option "Assign A/R Next Number" under the general tab of R42565 to 1.
5. In P7400003 make an entry for your legal company and Document Type (one specified in the Processing Option of P7420565 i.e RI) combination.

If the issue still persists, I recommend raising a Service Request, so we can review your configuration in detail and investigate further.

Regards,
Mahesh

Hi @User_4O6JL,

Thank you for the clarification. Glad to hear that the issue is now resolved.

Please feel free to reach out if you need any further assistance.

Regards,
Mahesh

Hi @User_DE61K,

This issue would be better addressed under a Service Request (SR) so we can investigate it in detail and provide appropriate support.

Please consider raising an SR with the relevant screenshots and steps to reproduce the behavior.

Regards,
Mahesh

Hi @User_O17JA,

In JD Edwards, approval processing is based on Order Type, not Line Type. Therefore, it is possible to configure approval workflows even for transactions with N line type.

As you mentioned that the orders are in status 220–230 but not appearing in the PO Approvals screen, it’s likely that the Override Next Status (Processing Option #4 on the Defaults tab of P4310 – Purchase Order Entry) is set to 230. This setting can bypass the approval process. To ensure approval is triggered correctly, please set this processing option to blank.

Kindly review your configuration accordingly. For more details on approval processing setup, refer to Oracle Doc ID 2090884.2

If the issue persists after these checks, I recommend raising a Service Request so we can examine your setup more closely and assist further.

Regards,
Mahesh

Hi @User_ZPLZ9,

You can print messages on Print Pick Slips (R42520) and Print Invoices (R42565) in JD Edwards using either the standard Print Message functionality or the Print Messages Preference setup.

For detailed guidance, please refer to the following Oracle documents:

• E1: 42: Creating Print Messages on Sales Orders and Invoices (Doc ID 2630379.1)
• E1: 42: Print Messages Preference (P40305/P40162) (Doc ID 625434.1)

Regards,
Mahesh

Hi,

You can check out below KM document which explains how using Advanced Preferences (Type 18) you can define what Price Effective Date should be populated. Here you have to make sure that the Pricing Based on Date (PD) field should be set to "7" to make sure Price Effective Date field gets populated with value defined in Advanced Preferences.
E1: 42: Sale Price Based on Date Advanced Preference (P4106/P4070/P4071/P4072/P4210/P42101) (Doc ID 625695.1)

However, to maintain a dynamic Price Effective Date, such as setting it to 15 days prior to the Requested Date for all orders, there appears to be no available functionality to achieve this requirement.

If there is any confusion or problem with the setup, please raise a SR with the Distribution team.

Regards,
Ankur Patel