Real Time Information Director User Documentation

RTID Metadata Language
Hewlett-Packard Company 36 529618-002
new FieldElement("LDDAT", "LOADING_DT"),
new FieldElement("MBDAT", "MATERIAL_AVAILABILITY_DT"),
new FieldElement("WADAT", "CURRENT_SCHEDULED_SHIP_DT"),
new FieldElement("EDATU", "CUSTOMER_REQUESTED_RECEIPT_DT"),
new FieldElement("WMENG", "REQUESTED_QT")
})
}),
new RecordSegment("E1EDPA1","RL_SPEC_SO_DT_EV_OVRRD",ORDER_EVENT_TAGS),
The highlighted text below shows two record segments under E1EDP01. (Other
elements and qualified segments under E1EDP01 are omitted from the excerpt.)
new RecordSegment("E1EDP01","SALES_ORDER_DETAIL",new TagDefinition[]{
new FieldsElement("POSEX", new String[]
{"SALES_ORDER_ITEM_NO","PRECEDING_DOCUMENT_ITEM_NO"}, IDOC.ITEM_NO),
new FieldElement("ACTION", "SALES_ORDER_ITEM_ACTION_CD"),
…
new RecordSegment("E1EDP20","SLS_ORD_SCHEDULE_DT",new TagDefinition[]{
new FieldElement("WMENG", "CONFIRMED_QT"),
new FieldElement("EDATU", "SCHEDULE_LINE_DT"),
new FieldElement("EZEIT", "DELIVERY_TM"),
new Segment("ZEEDP20", new FieldElement[] {
new FieldElement("ETENR", "SCHEDULE_LINE_NO",
IDOC.LINE_NO),
new FieldElement("LDDAT", "LOADING_DT"),
new FieldElement("MBDAT", "MATERIAL_AVAILABILITY_DT"),
new FieldElement("WADAT", "CURRENT_SCHEDULED_SHIP_DT"),
new FieldElement("EDATU", "CUSTOMER_REQUESTED_RECEIPT_DT"),
new FieldElement("WMENG", "REQUESTED_QT")
})
}),
new RecordSegment("E1EDPA1","RL_SPEC_SO_DT_EV_OVRRD",ORDER_EVENT_TAGS),
Note: There must be a one-to-one correspondence between RelatedRecords in the
document content metadata and the RecordSegments in the document format metadata.
Furthermore, the content and format metadata must name the same tables and must be
nested similarly. (An inconsistency between the content and format metadata results in a
MetadataInconsistency exception.) For example, segments E1EDP20 and E1EDPA1 are
nested under E1EDP01 in ORDERS05 IDoc. This structure represents the fact that one
or more schedule lines and order event overrides can occur for each order detail.
Consequently the RelatedRecords for the SLS_ORD_SCHEDULE_DT table and the
RLS_SPEC_SO_DT_EV_OVRRD table must be nested under the RelatedRecords for
the SALES_ORDER_DETAIL table. No tag corresponds to SplitRecords and
HistoryRecords, because those are automatically associated with the parent record.
When the segment tag does not result in a new record, the metadata specifies a Segment
rather than a RecordSegment, as in the text highlighted below. Use Segment only if the
segment occurs once, at most, within the parent segment. This construct is most often
used for custom segments that begin with the letter Z, as in this example.
new RecordSegment("E1EDP01","SALES_ORDER_DETAIL",new TagDefinition[]{