Real Time Information Director User Documentation
RTID Extensibility 
Hewlett-Packard Company  5  529618 - 001 
A sales order schedule detail record is inserted into the SLS_ORD_SCHEDULE_DT 
table for each E1EDP20 tag encountered in the input data. For each sales order schedule 
detail record the CURRENT_SCHEDULED_SHIP_DT column is populated from the 
WADAT tag. Note that the WADAT tag is nested under the custom segment ZEEDP20. 
Based on these requirements, the following mapping, abridged for clarity, can be used: 
new RecordSegment("E1EDP20", "SLS_ORD_SCHEDULE_DT", new TagDefinition[] 
{ 
  new Segment("ZEEDP20", new FieldElement[] { 
 new FieldElement("WADAT", "CURRENT_SCHEDULED_SHIP_DT"), 
  . . . 
 }), 
 . . . 
}) 
Note how the current scheduled ship date mapping is triggered by the ZEEDP20 custom 
XML segment. This segment is not defined in the SAP IDoc schema for the ORDERS05 
IDoc. Typically, different SAP sources use a variety of custom tags, so the mapping 
team must contain at least a business analyst or SAP analyst in addition to the data model 
designer and the metadata designer. 
Defining a New Native Document 
Native documents are an XML representation of data in the NonStop SQL database. 
Native documents can originate in a source system or be generated by the Director in 
response to subscriptions. The Director can generate a schema for any native document; 
producers and consumers of native documents can use the XML Schema to validate a 
document prior to submission or upon receipt. 
To create the metadata for a new native document, complete the following steps: 
•  Examine the structure of the data in the document, which determines how the 
document will be inserted into the data store 
•  Determine if inbound documents should be delserted or upserted. (Delserting 
means deleted all existing records pertaining to a document and inserting new 
records. Upserting means updating existing records and adding new records.) 
•  Determine what information from the database must be included in an outbound 
document. This means identifying the tables, and the relationship between the 
tables, that contain the needed data. 
•  Create new tables in the data model. (If a native document will extract data only 
from existing tables, then no changes are needed.) 
•  Create the XML Schema for the native document. 










