Outbound message extension for order create messages

The Report_NC_PurchaserOrder message includes the UserData XML element, which contains the UserDataField element. We can customize the UserData element to pass extra information not included in the Report_NC_PurchaserOrder outbound message by extending the SendXMLOrderMsg command and implementing either the getHeaderExtensionRecords() method or the getItemExtensionRecords()method, depending on whether we want to add the information at the header or item level. By default, both getHeaderExtensionRecords() and getItemExtensionRecords() methods return a null String value. Once implemented, both methods should return a String object that contains a series of UserDataField elements as follows:

The following table outlines the methods called for the XML elements of the Report_NC_PurchaseOrder message:

Message XML Element Method Called
Report_NC_PurchaserOrder Report_PO_Header getHeaderExtensionRecords()
Report_NC_PurchaserOrder Report_PO_Item getItemExtensionRecords()

The Order Create message includes the USRLST record, which contains the DATUSR_DATA data segment. DATUSR allows you to add optional fields to a message. We can customize the DATUSR records to pass extra information not included in the Order Create outbound message by extending the SendWCSOrderMsg command and implementing either the getHeaderExtensionRecords() method or the getItemExtensionRecords()method, depending on whether we want to add the information at the header or item level. By default, both getHeaderExtensionRecords() and getItemExtensionRecords() methods return a null String value. Once implemented, both methods should return a String object that contains a series of DATUSR records as follows:

The following table outlines the methods called for the sections of the Order Create message:

Message USRLST Section Method Called
Order Create <HEADER> getHeaderExtensionRecords()
Order Create <ITMDAT> getItemExtensionRecords()


Related tasks
Creating an outbound message


Related reference
Back-end integration legacy messages