 |
| ||||||||
FAQ KB0403515
Why was a Requisition set back to Composing with ERP push errors with an Order ID?
Question
Why was a Requisition set back to Composing with ERP push errors with an Order ID?
Answer
A Requisition is set back to Composing with an Order ID when there are multiple lines in that Requisition and at least one line does not have any push errors associated with it. In this case, an Order ID is sent back by the Enterprise Resource Planning (ERP) for the line/lines which does not have errors but the requisition is still set back to Composing as the other lines received a push error.
It is to be noted that, if there are two lines that are part of the same Order and one line receives ERP push error, Order ID is not updated on the other line. Purchase Order (PO) is not created, it will be hard deleted. A new PO request is sent to ERP the next time when the requisition is fully approved. So, if you see the Order ID updated on one of the lines, it always means that the Requisition is split into multiple POs. The lines without having Order ID will always be part of a different PO.
Once the errors are corrected on the latest Composing version of the requisition, lines which were part of the other order (that received ERP push error) are added to the same order in case the split fields are changed back to match the values as that of the lines which created a PO. If the split fields remain different on these lines, they will create a separate PO.
Applies To
Purchasing
Purchasing > Purchase Orders > Ordering Methods