Real Time Information Director User Documentation

RTID Extensibility
Hewlett-Packard Company 10 529618 - 001
Adding Alternate Mappings for an IDoc
Perhaps you already have mappings for an IDoc type, for example the ORDERS05 IDoc.
These mappings include content and format metadata and are based on an existing data
model. In some cases you might need to create an additional mapping for the same IDoc
type: in other words, the Director needs to map the same IDoc in several different ways.
One reason for such a requirement is that different SAP source systems can have different
mappings for the same IDoc. For example, two SAP instances can generate ORDERS05
documents with differences in the data:
• With a different top tag, for instance ORDERS05 versus ORDERS05EXT. To
the Director, these are two different IDocs, because the top-level tag identifies the
metadata for a given IDoc.
• With the same top tag, but different mappings. To the Director, these are the same
IDoc, because the top-level tag is the same, but they should be treated differently,
because the mappings are not the same.
In both cases, the data stored in the database should look the same, regardless from which
SAP source system it was received.
Aliased or Variant?
To accommodate a new mapping of an existing IDoc, you must create an Aliased or
Variant document definition. To decide which to create, you must first to understand the
differences between the IDoc formats used by different source systems.
Obtain sample IDocs from each source system, and analyze the differences. If the IDoc
top tag is different from the top tag of the base document mapping, then create an Alias
document definition. If the IDoc top tag is the same as the top tag of the base document
mapping, then create a Variant document definition.
Before you create an aliased or variant document, take a look at the corresponding
section of the RTID Metadata Language module.
Creating Metadata for an Aliased Document
The steps creating an aliased or variant document definition are almost the same as for
creating a new IDoc mapping. However, because you already have a base document
definition, you can use that as a starting point. Refer to the RTID Metadata Language
module for information about the syntax you should use.
1. Start with the base document definition and create a new mapping. For example,
make a copy of the file Orders05.java and name it Orders05EXT.java.