This topic contains sections marked as revised for this release
To build the message model for the IDOC parser, obtain the IDoc, model the IDoc, and use ESQL to access the fields of the IDoc.
To transform SAP IDoc data, model the segment data of the IDoc in WebSphere Message Broker.
The messages that are sent to, and received from, SAP applications are processed by the IDOC parser, which requires a message model to interpret the data correctly. This topic describes how to build the message model. SupportPac™ IA0F provides, as an example, a prebuilt version of a message model.
Create your message model.
Add the message set to a broker archive (bar) file and deploy the bar file to a broker execution group. The IDOC parser uses the MRM parser to parse the IDoc segments that you have defined.
The Message Domain property, the message set name, and the Custom Wire Format name, are used when you create a message flow to process an IDoc. These names appear as the values of the Message Domain, Message Set, and Message Format properties, respectively, of an MQInput node. Do not supply a Message Type property on the MQInput node because the IDOC parser uses the contents of the SAP-defined IDoc DD field segnam to provide the name of the message.
After the sdatatag tag in an ESQL statement, the next tag is MRM, which you must enter manually, followed by the field name that is to be manipulated. Specify the name of the field within the message segment here, not the name of the message segment.
For example, the following code sets the segment name of the IDoc:
SET OutputRoot.IDOC.DD[I].segnam = 'E2MAKTM001';The following example sets the msgfn field within the E2MAKTM001 segment:
SET OutputRoot.IDOC.DD[I].sdatatag.MRM.msgfn = '006';