Cross-Reference Data
Before you can successfully share data between JD Edwards EnterpriseOne and a third-party vendor's system, you must set up cross-reference information. The system uses cross-reference information to map data from the JD Edwards EnterpriseOne database to the vendor's database, and vice versa.
To set up cross-reference data, you must first set up supplier records in the JD Edwards EnterpriseOne system. Then, you must set up cross-reference object types. Object types define the categories of data that you will pass between the two systems and include categories such as:
CURRENCY
ISO_COUNTRY
LANGUAGE
UOM (unit of measure)
REFID (reference ID)
After you set up cross-reference object types, set up business service properties to specify the application ID of each of your vendors. After you have set up the application ID, you enter cross-reference records for each of those application IDs. Cross-reference records map the values from one system to the values in the other system. This is necessary because many systems use different codes or values to represent the same information.
For example, the JD Edwards EnterpriseOne system uses the currency code USD to represent U.S. dollars. However, a third-party system might use a different code, such as 004, to represent U.S. dollars. In order for the two systems to share currency amounts in U.S. dollars, you must create a cross-reference record for this currency for the application ID used by that vendor. You associate the record with the CURRENCY cross-reference object type. When you create the record, you specify the value that represents the currency in the JD Edwards EnterpriseOne system (USD) and the value that represents that same currency in the vendor's system (004). You set up currency cross-reference records for all currencies in which your organization and vendors use.
When you enter cross-reference records, you also specify the third-party application ID for each vendor. Multiple vendors can share the same application ID; however, they must also use the same cross-reference values. If vendors must use different values, they must also use different application IDs.