Deliver to Location is Stamped From Other Operating Unit Rather Than MO:Operating Unit
(Doc ID 2063352.1)
Last updated on SEPTEMBER 18, 2023
Applies to:
Oracle iProcurement - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
On : 12.1.3 version, Requisition Creation
ACTUAL BEHAVIOR:
----------------------
When attempting to create requisition from iProcurement, deliver to location is stamped from other Operating Unit
EXPECTED BEHAVIOR:
----------------------
Deliver to location should be stamped from same Operating Unit which is set at MO: Operating Unit
Due to this wrong deliver to location (which is also mapped to wrong inventory organization), requester gets the error while receiving from iProcurement:
ERROR
-----------------------
Your receipt could not be created due to unexpected error. Please contact your system administrator with the following information for further assistance.
"rvtptcontrol failed RVTTH-445: Subroutine No transaction Flow defined for these two operating units: <OPERATING UNIT X> and <OPERATING UNIT Y>. Action: Please use Defined Intercompany Transaction flow form to define the transact cannot read value for profile option INV_DEBUG_TRACE in routine &ROUTINE."
STEPS TO REPRODUCE
-----------------------
1. Set MO: Operating Unit a Operating Unit X at iProcurement Responsibility level
2. Login to iProcurement
3. Add the items via Catalog or Non Catalog
4. Move to Checkout Page
5. Check that deliver to location is defaulted from <OPERATING UNIT Y> (Location associated to Inventory organization belong to <OPERATING UNIT Y>)
6. Submit the requisition
7. Create a PO from this requisition
8. Login to iProcurement > Receiving
9. While creating receipt, get the above error
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 |