Creating a Cross Reference

To create a cross reference:

1. On the Orchestrator Studio Home page, click the Cross References icon.

2. On the Cross References side panel, click the New button.

3. Create and name the cross reference as described in Creating a Component.

4. On the Cross References design page, in the Object Type drop-down list, select a cross-reference object type.

   This is the object type that is used to categorize the orchestration cross references in EnterpriseOne. See "Adding Orchestration Cross References" in the JD Edwards EnterpriseOne Tools Interoperability Guide

5. (Release 9.2.6.4) In the Third Party App ID field, enter the field name to further refine the mappings between EnterpriseOne and third-party systems.

   You can use the Third Party App ID field to define multiple sets of cross-references and then distinguish them. For example, you might be integrating to two or more external systems that use the same inbound value to be cross-referenced. This option enables you to define mappings that may have the same EnterpriseOne or third party value, but have a different cross-reference value for each of the external systems.

   This is an optional field and can be left blank. You can enter a literal value such as SystemA, or you can enter a variable name using the ${variableName} syntax. If you enter a variable name, then the variable name becomes a step input, and the orchestration calling it can either leave it blank for no filtering or pass in a value to perform filtering on the app id.

6. (Release 9.2.6.4) In the Cross Reference Direction section, you can select the Inbound or Outbound options to specify the direction of the cross-reference.

   If you select the Inbound (third-party value) option, the cross-reference will return its corresponding EnterpriseOne value. Conversely, if you select the Outbound (EnterpriseOne value) option, the cross-reference will return its corresponding third-party value. This option enables you to map data between EnterpriseOne and external systems bidirectionally.

7. Complete the Input Key (Third-party Value)and Output Key (EOne Value) columns to map the inputs to EnterpriseOne fields:

   • Input Key. The inputs can be one or many values. The inputs must correspond to the values or pipe (|) delimited values in the Third Party Value column in P952000. See Setting Up Cross References and White Lists in EnterpriseOne (P952000) for more information.

   • Output Key. The outputs can be one or many values. The outputs must correspond to the values or pipe (|) delimited values in the EOne Value column in P952000. See Setting Up Cross References and White Lists in EnterpriseOne (P952000) for more information.

8. If you enter any value by mistake, you can click the Remove (X) button to delete the entry.

9. Click the Save button, which saves the cross reference as a "Personal" UDO.

   The first time a new cross reference is saved, it is saved as a "Personal" UDO. Thereafter, you can use the UDO buttons that are described in the User Defined Object (UDO) Features in the Orchestrator Studio section to move the cross-reference to the appropriate status.

The output values in the cross reference are now available for mapping in subsequent orchestration steps.