Fusion: CST : Financial Orchestration- Priority Functionality Usage In Case Of Same Selling Entity
(Doc ID 3023159.1)
Last updated on MAY 28, 2024
Applies to:
Oracle Fusion Inventory Management Cloud Service - Version 11.13.24.01.0 and laterInformation in this document applies to any platform.
Goal
Financial Orchestration- Priority Functionality Usage in case of same selling entity
We have defined 2 drops ship financial flow for XX business unit with different priorities.
1. Domestic Drop Ship – Priority 1 (P1)
a. Selling Business Unit: XX BU
b. Requisition & Procuring & Receiving Business Unit : XX BU
2. International Drop Ship – Priority 2 (P2)
a. Selling Business Unit: XX BU
b. Requisition & Procuring & Receiving Business Unit : Global Inventory BU
When a drop ship sales order is created with 2 lines with line 1 sourcing rules pointed to XX BU supplier and XX BU supplier site and line 2 sourcing rules pointed to Global Inventory supplier and Global Inventory BU Supplier Site, Requisition and Procurement BU are getting derived as XX BU for both the lines.
But the expectation is, we are looking forward for line 1 to create a purchase order in XX BU based on supplier & site combination provided and for line 2 to create a purchase order in Global inventory BU based on supplier and supplier site combination.
Solution
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
Goal |
Solution |