E1: 43: Changing Non Critical Field Updates Purchase Order Lines to Next Status 280
(Doc ID 2329691.1)
Last updated on MARCH 24, 2023
Applies to:
JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.1 and laterInformation in this document applies to any platform.
Symptoms
Purchase Order Entry (P4310)
Changing a non-critical field in Purchase Order Entry (P4310) is causing order lines to be changed to Next Status 280. This is causing confusion and wasted time in production and is occurring on a daily basis. In some cases it is resulting in duplicate shipments from vendors.
The issue can be reproduced at will with the following steps:
- Order Activity Rules (P40204) are set for OP/S purchase orders so when an order is at status 280/282 it has already been printed and sent to the Vendor.
- The PO Entry (P4310) Defaults Tab Option #4 (Override Next Status) is set to blank. So the Next Status will be updated based on the Order Activity Rules.
- The Order Revision Tab Option #2 (Next Status) is set to blank so changes to the order should not update the Next Status Code.
- Approvals Tab Option #4 (Reapprove Changed Lines) is set to 2 (Reapprove on change to user-defined critical fields only). This status should send the order into Reapproval (Next Status 230) if one of the user-defined critical fields is changed.
- In the user-defined critical fields (P43080) table, the buyer number is NOT designated as a critical field.
- Purchase Order Number 382102 OP has 3 lines currently at Status 280/282 for which a Purchase Order was already printed and sent to the vendor.
- The user goes into purchase order header for 382102 OP and changes the buyer number which is NOT a critical field.
- Nothing is changed on the order detail lines and the order is saved after making changes.
- When the user brings the order up in Open Purchase Order Inquiry (P4310), the 3 lines that were status 280/282 have been changed to 282/280. This will cause them to get processed again by the nightly batch job for PO Print (R43500) and the vendor will be sent the printed PO again.
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 |
Cause |
Solution |
References |