Predefined Integration Mappings for Direct Item Procurement
As a continuation of the Direct Item Procurement (DIP) capability, the integration layer has now been enhanced with a new Direct Procurement Flag.
DIP inventories are intended to move vendor > receiving > work center (WC) without entering regular storage. To support this behavior, a new flag has been introduced — ensuring that only the required manufacturing-related movements are integrated, while store-level adjustments are suppressed.
New Flag Introduced
|
Flag |
Meaning |
Usage |
|
Direct Procurement Flag |
Identifies whether the inventory transaction belongs to a DIP flow |
Used by integration to determine whether inventory histories should be processed or ignored |
How the Flag Works
|
Condition |
Interpretation |
Integration Result |
|
HDP = True + ACF = True |
Direct procurement with auto-consume |
Storage-level IHTs are suppressed, and destination_type_code is sent as Manufacturing |
|
Either HDP = False or ACF = False |
Standard procurement or non-DIP flow |
No restrictions: all IHTs follow regular integration and destination_type_code is sent as Inventory |
Inventory Histories Automatically Suppressed When HDP = True and ACF = True
NOTE: Transactions where HDP =True and ACF = False are NOT supported, currently. In such cases, even if its not a DIP flow, the Inventory Adjustments will not be sent to Fusion.
The following Predefined Integrations are impacted to prevent unintended posting of store-level updates to Fusion ERP during DIP:
- Inventory adjustments
- Putaway-driven storage transitions
- Manufacturing pick confirmations (when auto-consume is enabled)
RECOMMENDATIONS:
- Modifying inventory is NOT recommended in DIP. We DO NOT recommend performing any inventory adjustments like Split IBLPN, Modify IBLPN, or IB sorting for DIP flow.
- On performing modify before Putaway explicitly, the destination type code will be updated to "Inventory", causing discrepancy. For DIP flow, the destination type code must be "Manufacturing" as inventory is not impacted.
To know more, please refer to the Integration Guide.
Steps to enable and configure
You don't need to do anything to enable this feature.