The driver includes two default Metadata files: HRMD_A03.meta and HRMD_A05.meta. These files contain the SAP metaschema definitions of the HRMD_A03 IDoc type, which is the standard HR Master Data IDoc for version 4.5B of SAP R/3; and the HRMD_A05 IDoc type, which is the standard HR Master Data IDoc for version 4.6C.
These files are provided for two distinct purposes:
The driver uses a metadata file to generate an Application Schema Map when requested via the option in iManager.
If a value is specified in the configuration, the driver opens the metadata file to determine if the encoding value specified is valid.
The following sections provide information to help you use the Metadata files:
A schema map must exist for the IDoc type that the driver consumes, whether the configuration parameter specifies the type or the driver selects a default type based on the version of the SAP Application server. Because only two maps are provided with the driver, you might need to create a new map for the IDoc type needed by the driver.
You can simply copy the HRMD_A05.meta file to a new file, such as HRMD_A06.meta. This is acceptable as long as you do not need to publish newer infotypes not found in the HRMD_A05 version. It is unlikely that newer infotypes will be needed.
The size of the metaschema definitions can create problems for your driver configuration. The schema refresh can take a long time to process, especially because a copy of the map is generated for each object type you choose to synchronize. Additionally, the size of the schema in the driver configuration can be extremely large and cumbersome to navigate. For these reasons, it is acceptable to reduce the number of infotypes in the metadata files.
You can edit the appropriate metadata file and remove all infotypes that are not used for your implementation. Simply search for the infotypes to remove (for examples, Infotype 0008 values can be found by searching for P0008) and deleting the SEGMENT: line and subsequent infotype field lines from the file. You should modify a copy of the original file. For most integrations, only 20-30 percent of the infotypes are actually used.
IMPORTANT:You must be careful that you do not remove infotypes that are useful for policies or other object types being synchronized. Two infotypes of this nature are Infotype 1000 (for Descriptions of non-person objects) and Infotype 1001 (Relationships between objects.) These are both used in the default driver configuration.
You should also not remove fields from infotypes that are used in your integration. Field removal is extremely hard to detect if a mistake is made or if you want to return to an earlier version.
There are many situations where an IDoc is extended with custom infotypes or infotype fields. Because the schema map is based on standard SAP IDoc types, you must manually create these types of metadata extensions. There are several areas of concern:
If the infotype is an extension to the IDoc (for example, Infotype Z0001), you must ensure that the infotype header fields are present in a standard format. These standard fields start with the field PERNR and extend through field RESE2 in data infotypes. If these fields are not present or contain no data, many of the driver features such as future-dating and history-dating do not work.
The format of new infotypes is similar to the standard infotypes. The first field should be <5 character infotype>:PERNR:0:8. When parsing an actual IDoc, the physical offset for the PERNR field is 63 (when starting from position 0.)
You can also create schema extensions directly to the Mapping Rule without the need to update the metadata file. If you choose this option, which is often easier, remember the physical offset mentioned above when determining where your data fields of interest begin. The format for a direct mapping is described in Section 1.6.3, Attribute Mapping from the SAP HR Database to the Identity Vault. Selecting field names is up to you, because the driver does not use them for processing, but they should be limited to 5 characters for consistency.