2

When utilizing the intercompany functionality configured to sync batch on inventory transactions, the batch dimension synced should ideally mirror the shipping entity's inventory transactions. Upon shipping an intercompany Sales order where ship quantity < order quantity, current functionality separates the receiving region's inventory transactions for the mirrored line item into two with an unmatched batch dimension due to FEFO reservation. Due to the shared transactional information, the inventory transaction record on the receiving entity should match exactly in quantity and batch.

 

Our client use case is to have full traceability of item/batch product flow from one entity to another. Ideally, the batch and quantity shipped should be the batch and quantity received. The receiving region would utilize the shipped information in their own on-hand and re-use the product's physical labels internally since the batch flows between entities.

 

The desired configuration for the client's intercompany relationship is to allow batch number on inventory transactions for Intercompany purchase order > Intercompany sales order (InterCompanyActionPolicyTransferVendorEx_InventBatchId). Additionally, the item model group is setup with the inventory policy "FEFO date-controlled" (InventModelGroup_PdsCheck). The expectation with the flow of batch number between entities is so the receiving entity can utlize the product labels by Item/batch internal of their operations without the need to re-label with a different batch number.

 

Example: Order line calls for 10 cases of item 000000111

Shipping entity ships:

  • 8 cases of item 000000111, batch PO000000223

Receiving entity receives:

  • 6 cases of item 000000111, batch PO000000223
  • 2 cases of item 000000111, batch 260316-TFIL-006766


STATUS DETAILS
New