To use WebSphere Message Broker's capability to transform SAP IDoc data, you must model the segment data of the IDoc in WebSphere Message Broker.
The messages 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 documents how to build the message model. An example prebuilt version of a message model is provided in SupportPac IA0F.
Use the following procedure to create your message model:
The message set must be added to a broker archive file and deployed to a broker execution group, because the IDoc parser uses the MRM parser to parse the IDoc segments you have defined.
The Runtime Parser property, the message set name, and the Custom Wire Format name are used when you create a message flow to process an IDoc. They 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.
When you get to the sdatatag tag in an ESQL statement, the next tag is MRM, which must be entered manually, and then the field name to be manipulated. Specify the name of the field within the message segment here, instead of 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';
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ac20030_ |