Creating a Cross Reference

You must define the orchestration inputs before you can create a cross reference. See Adding Inputs to an Orchestration for more information.

To create a cross reference:

1. Access the Cross Reference design page:

   • On the Orchestrator Home page, click the Cross References icon. And then on the Cross References design page, click the New Cross Reference button.

     OR

   • After adding a Cross Reference step to the grid in the Orchestration design page, click the Edit button next to the step.

   The Orchestrator Studio displays the Cross Reference design page.

2. In the Cross Reference field, enter a name for the cross reference.

3. In the space provided, enter a short description with a maximum of 200 characters. This description appears below the cross reference name in the component list.

4. Click the Edit Long Description button to add a long description to provide more detail about the purpose of the component.

5. In the Object Type field, enter a name for the object type.

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

6. (Studio 5.1.0) Click the Product Code drop-down list to select a product code to associate with the cross reference.

   This gives an administrator the option to manage UDO security for orchestration components by product code.

7. Complete the Input Key and Output Key columns to map the inputs to EnterpriseOne fields:

   • Input Key. The inputs can be one or many values. The inputs must correspond to the value 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 value 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 values by mistake, you can click the X button next to the field to delete the entry.

9. Click the Save button, which saves the white list 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 described in the User Defined Object (UDO) Features section to move the rule to the appropriate status.

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