You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

Nested PTO - ATO Model with Back to back Functionality requiring components to be shipped separately

in Inventory Management

Summary:

We have a scenario where we have created a nested PTO (P1) Model to contain an Option Class that contains another PTO (P2) Model (PTO Components) and an ATO Purchase Model. We want Child PTO model components to be shipped separately on different requested date. While ATO purchase is mutually exclusive to child PTO under the parent PTO. All the components are back to back enabled.

I am facing a below issues:

  1. Child PTO (P2) components are not kicking B2B PR/PO. While if a SO is directly created on Child PTO(P2) model (rather than P1), it works absolutely fine. Just that in nested arrangement, B2B is not triggering. However, orchestration does show awaiting Back to back shipment.
Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!