Last updated on MARCH 10, 2016
Applies to:Oracle iProcurement - Version: 11.5.10 to 12.1.3 - Release: 11.5 to 12.1
Information in this document applies to any platform.
in procedure CUSTOM_VALIDATE_REQ_DIST in 11.5.10.
The "CUSTOM_UPDATE_CHARGE_ACCOUNT" procedure is changed but it does not get triggered
when one clicks on the 'Accounts' tab or when they navigate to Step 2 on requisition creation. It is only
triggered when one manually changes the charge account.
Customer does not enter the charge account manually. It is generated automatically. Now, based on
certain business logic some or all of the segments are changed programatically via
x_concatenated_segments in CUSTOM_VALIDATE_REQ_DIST in POR_CUSTOM_PKG.
The new procedure will not fire, since the user is not changing any of the segments manually.
Steps to reproduce
1. Customize por_custom_pkg to change the charge account based on some business logic
2. Go to create the requisition in iProcurement
3. Check if the charge account was changed after clicking the Accounts tab or when navigating to the
step 2 of the checkout process.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms