E1: 43E: Prevent RSS Order Entry if Valid Approval Route Does Not Exist (Doc ID 3027353.1)

Last updated on JUNE 06, 2024

Applies to:

Symptoms

With RSS Approval Constants active at the Business Unit (Level 4), but where no route is added for a specific Business Unit in the Approval Authority application (P43E09A), the system does not prevent an order being raised in the P43E10, potentially for a large sum of money. No approval is triggered, nor any error or warning that a route does not exist. The order moves to ‘Approved’ status and a purchase order can be generated, without any approval being performed.

Ideally, there should be a check for a valid approval route, with Beginning/Ending Effective dates that include the order date, and to present a warning or error if no route is found. The system should cross check the BU entered in the P43E10 screen (or defaulted in) against the BU values that exist in the P43E09A.

The only known workaround is to set the Business Unit’s Posting Edit code (alias PECC) to an “N” value in the P0006 application, which triggers an error (for “BU xx PEC does not allow entry) but this is too restrictive; also the error can be circumvented by changing the Account number to one for a Business Unit that does allow Posting.

Changes

Cause

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