E1: 43: Unable to Update Status Fields with Purchase Order Entry (P4310) on Accidentally Closed Direct Ship (OD) Purchase Order
(Doc ID 2849242.1)
Last updated on FEBRUARY 26, 2024
Applies to:
JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
The PO Print (R43500) was run two times consecutively on a Direct Ship (OD) purchase order with the processing option set to update the order status. As a result, the PO status was set to 400/999 without first receiving the PO. When the user attempts to use a PO Entry (P4310) version to change the status back to 300/400, the change is not allowed. This occurs even though the Display Tab Processing Option #2 (Status Code Protection) is Blank (Do not protect) on the PO Entry (P4310) version.
The client reproduced the issue with the following steps:
- User created a 3-line Direct Ship Sales Order (SD) at 520/521 status
- Each line was for a quantity of 1
- The related Direct Ship Purchase Order (OD) was created at 220/228 status for Line 1.000 only
- Sales Speed Status Update (P42040) was used to update line 1.000 of the SD to Status 528/560
- PO Speed Status Update (P43025) was used to update OD line 1.000 to Status 228/280
- PO Print (R43500) was used to update OD line 1.000 to Status 280/300
- PO Speed Status Update (P43025) was used to update OD line 1.000 to Status 300/400
- PO Print (R43500) was used to update OD line 1.000 to Status 400/999
- A PO Entry (P4310) version is selected that has Display Tab Processing Option #2 (Status Code Protection) set to Blank (Do not protect)
- The user attempts to use the PO Entry (P4310) version to change the status back to 300/400, but the change is not allowed.
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |