PunchOutOrderMessageHeader – operationsAllowed

There are a number of different cXML messages to handle different business documents that you will find in the cXML standard. The cXML protocol handler for AX2012 is implementing the procurement punchOut transactions. You can find these described in chapter 5 of the cXML user guide.

It’s worth noting that there are a few options are described in the cXML user guide for the PunchOutOrderMessage denoted by the attribute operationAllowed

<Total>

</Total>

</PunchOutOrderMessageHeader>

These are defined at “create”, “inspect” or “edit” which controls what can happen after the shipping basket data is returned from the suppliers website. As defined in the cXML User Guide the handling is as follows.

operationAllowed=”create”: disallows subsequent PunchOut sessions for these items. Users cannot inspect or edit these items.
operationAllowed=”inspect”: allows subsequent PunchOut sessions only to inspect these items. The items cannot be changed.
operationAllowed=”edit”: allows subsequent PunchOut sessions to both inspect and change these items.

In the current version of the cXML punchOut protocol for AX2012 the supplier could return the message with operationAllowed set to edit. But it’s handled in AX as a create. The user returns shopping basket data that needs to be changed then they should punch out again and fill in their basket.

Here is a quick walkthrough