Last updated on JULY 25, 2017
Applies to:JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.1 and later
Information in this document applies to any platform.
Purchase Order Entry, in prior releases, would initiate at an order awaiting approval status, such as 220 230, for the Last and Next Status, per the order activity rules. Now, while the order appears to be created at 220 230, the orders going through approval processing get a status change update at order entry bumping the status. Orders that used to get entered at 220 230, for example, are now being entered at 230 230.
This is inconsistent with prior releases such as 8.12 or even 9.00 Base.
The P4310 application for Order Entry does not display the anticipated status code for the Last Status Code. As if the system is using the Next Status Code as the Last Status code. For example, for order type OO, after order entry the status codes should be 220/230. In 8.12 and above, the status codes display as 230/230.
With the introduction of Bug 14590715, the system now allows customers the ability to have a unique order awaiting approval line status, separate from the next status on the first order activity rule. This setup was important, as some customers may use the same document type and line type that will never use an approval process and would drive the next status to the value set in the order activity rules. With this fix, the logic of the approval process changed.
The P4310 first looks at the order activity rules to determine what the next and last status should be. Then the approval logic determines if the order should go into approvals and what the next status code should be. This means that for a client that does not update the order activity rules for a unique order awaiting approval line status, the approval status update will advance the order from 220/230 to 230/230. This is functioning as designed.
If it is desired to have a last status that is a different value than the awaiting approval status, the order activity rules could be setup, accordingly.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms