My Oracle Support Banner

WS: 43: Incorrect Next Status (NXTR) and No 2N, 3N Records Written in the Held Orders File (F4209) for Orders in Approval Review - P43080 (Doc ID 2764216.1)

Last updated on NOVEMBER 28, 2023

Applies to:

JD Edwards World Procurement - Version A9.4 and later
Information in this document applies to any platform.


After upgrade from A9.4 to A9.4.2, when approving a PO/Requisition with single or multi-level approval routes in Approvals Processing, the Approval Review program (P43080) writes an incorrect next status (NXTR) and does not write correct held order Approval status (ASTS) codes in the Held Orders file (F4209), 2N and 3N records. For a PO to move through Approvals Process and be fully processed/ approved, the programming relies on the Held Orders file (F4209) to write records with specific approval status code information (ie 0, 2A, 2N, 3N). When the file is not correct, the related programs cannot function properly.

Steps to Duplicate

1. Set up a single and a multi-level approval route in Approval Level Revisions (P43008).
2. Attach the Approval Route to the Branch Plant (B/P) in B/P Constants (P41001).
3. Set the processing options in Purchase Order (PO) Entry (P4311), to default the approval route from the B/P and add the status codes for approvals.

Test Incorrect Next Status

  1. For a single level approver, enter a Requisition (P4311). The next status (NXTR) = 110.
  2. PO / requisition OR is in approvals; A F4209 (Held Orders file record is written,)
  3. Approve the order via Approval Review (P43080) and the order next status is not updated = 120.

Test Incorrect Held Order file (F4209) records

  1. Update the approval route code in the Approval Level Revisions (P43008) with two responsible persons, one for $1.00 dollar and the other for $25,000.00 dollars.
  2. Create a purchase order (P4311) for $150.00 and note there are now two records in the F4209. The first F4209 record is for the originator, Approval Status (ASTS) set = O and the second is for the responsible approver with Approval Status (ASTS) set = 2N. This is correct.
  3. Approve the order in Approval Review (P43080). Now, the second F4209 record for the responsible approver writes Approval Status (ASTS) = 2A, this is correct. Note, a third record did not create for the originator = 3N. Dependent on single or multi-level routes, the F4209 will be missing 2N and 3N records, only 0 and 2A records are being created. 


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.