WebSphere Message Brokers
File: ad20040_
Writer: Neil Dewhurst

Reference topic

This build: July 31, 2007 21:26:11

Field names of the IDOC parser structures

The field names of the Control Structure (DC) and the Data Structure (DD) that are used by the IDOC parser.

The field names are documented in the form that they are used in a SET statement of ESQL; for example:
SET OutputRoot.Properties = InputRoot.Properties;
SET OutputRoot.MQMD = InputRoot.MQMD;

Control structure (DC) fields

All the fields must be specified and set.

The syntax is:
<rootname>.<ParserName>.<foldername>.<fieldname>=
For example:
SET "OutputRoot"."IDOC"."DC"."docnum" = '0000000000000001';
SET "OutputRoot"."IDOC"."DC"."idoctyp" = 'MATMAS01'
The field names, which must be specified in order, are:
1) tabnam 2) mandt 3) docnum
4) docrel 5) status 6) direct
7) outmod 8) exprss 9) test
10) idoctyp 11) cimtyp 12) mestyp
13) mescod 14) mesfct 15) std
16) stdvrs 17) stdmes 18) sndpor
19) sndprt 20) sndpfc 21) sndprn
22) sndsad 23) sndlad 24) rcvpor
25) rcvprt 26) rcvpfc 27) rcvprn
28) rcvsad 29) rcvlad 30) credat
31) cretim 32) refint 33) refgrp
34) refmes 35) arckey 36) serial

Data structure (DD) fields

To access each DD segment, use the array suffix DD[1], DD[2], and so on.

The syntax is:
<rootname>.<ParserName>.DD[1].<fieldname>=
For example:
SET OutputRoot.IDOC.DD[I].segnam  = 'E2MAKTM001';
SET OutputRoot.IDOC.DD[I].mandt2   = '111';

The following table illustrates how the suffix 2 is used to give unique field names to the mandt and docnum fields.

The field names, which must be supplied in order, are:
1) segnam 2) mandt2 3) docnum2
4) segnum 5) psgnum 6) hlevel
Notes:
  • The last 1000 bytes of data in the DD segment are the bytes that are modelled in the MRM.
  • The DD segnam describes the model that the MRM uses.

Segment fields

The syntax is:
<rootname>.<ParserName>.DD[1].sdatatag.MRM.<fieldname>=
For example:
SET OutputRoot.IDOC.DD[I].sdatatag.MRM.msgfn = '006'
SET OutputRoot.IDOC.DD[I].sdatatag.MRM.spras_iso = 'EN'
Notes:
  • The sdatatag keyword indicates to the parser that it is the element that contains the data to be manipulated.
  • The MRM keyword indicates that the MRM handles the transformation.
msgfn spras maktx
msgfn spras_iso fill954

The fill954 keyword is the filler for the segment because an incoming IDoc to SAP must have 1000 byte segments.

Related concepts
Message flows overview
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:26:11

ad20040_ This topic's URL is: