Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 29 529618-002
Note: IDocs have a single tag, named IDOC, immediately below the top tag. You don’t
specify this tag; the Director provides for it automatically.
Here are the possible constructors for the IDocSegment class:
public IDocSegment(String tagName, String tableName, Segment[]
tagDefinitions)
public IDocSegment(String name, String tableName, SegmentFormatter
segmentFormatter, Segment[] tagDefinitions)
The IDoc Header
The first tag under the new IDocSegment should be IDOC.HEADER. This tag represents
an IDoc header.
For inbound documents, the Director recognizes both SAP version 3 headers (EDI_DC)
and SAP version 4 headers (EDI_DC40).
Outbound documents have version 4 headers by default. To generate outbound
documents using version 3 headers, use IDOC.HEADER_31I instead of
IDOC.HEADER.
The IDOC class
As the syntax suggests, IDOC.HEADER is an object provided by a class called IDOC.
The IDOC class contains statically initialized metadata objects that you can reuse in
various IDocs.
IDOC.HEADER is only one of the IDOC objects you will specify. Others are
formatters, which perform various types of data conversions. (See “Formatter Classes,”
later in this document.)
You may add other reusable metadata objects to the IDOC class or to your own class.
The IDoc Segment
Following the IDOC.HEADER is a Segment tag. Segment is SAP terminology for a
record or group of related fields in an IDoc. In XML, a segment is introduced by a tag
followed not by data, but by the tag of the first field in the segment.
In your metadata, a segment contains an array of tag definitions representing the fields
within the IDoc.