Purpose
This schema can be used to create a two-way cross-reference mapping between any provider and Gateway. The file describes the elements that keys are used to establish the links between the business objects in the provider application and the business objects in Gateway. The provider application can behave as the source provider or the destination provider. The major advantage of using this schema allows you to extend the use of your provider application by opening it up for integrations with more than one ERP application and therefore, can be used in multiple integration scenarios as long as the cross-mapping files contain common Gateway business objects.
Schema file
XRefDefinition.xsd
Contents
An XRefDefinitions element containing the following elements:
Element | Type | Parents | Description |
|---|---|---|---|
XRefDefinition | XRefDefinitionType | XRefDefinitions | The container element for the cross-reference element. |
XRefDefinitionType Table
Element | Type | Parents | Description |
|---|---|---|---|
AppName | string | XRefDefinition | The container element for the application name. Note: The name should match the appropriate /MetaData/App/Name that is specified in the *MetaData.xml file. |
XRefObjectDefinition | XRefObjectDefinitionType | XRefDefinition | The container element for elements that identify the object and the identifiers. |
XRefObjectDefinitionType Table
Element | Type | Parents | Description |
|---|---|---|---|
AppObjectName | string | XRefObjectDefinition | The container element for the application name. Note: The name should match the appropriate /MetaData/App/Name that is specified in the *MetaData.xml file. |
PDIObjectName | string | XRefObjectDefinition | The container element for the Gateway (PDI) business object name if different from the value specified by the Name element. |
AppKeyFieldName | string | XRefObjectDefinition | The container element for the name of the key field that is to be used to find the matching field in the application. |