1. Using the Oracle E-Business Suite Adapter with Oracle Integration 3
  2. Implement Common Patterns Using the Oracle E-Business Suite Adapter

5 Implement Common Patterns Using the Oracle E-Business Suite Adapter

The Oracle E-Business Suite Adapter supports both inbound and outbound integrations in Oracle Integration. You can use the Oracle E-Business Suite Adapter as a trigger or as an invoke connection in an integration.

  • For Inbound Integration from Oracle E-Business Suite to Oracle Integration

    When adding the Oracle E-Business Suite Adapter as a trigger (source) connection, you can use either of the following interface types to trigger an inbound integration in Oracle Integration:

    • Business Event

    • XML Gateway Message


    This image shows the Basic Info page of the Oracle E-Business Suite Adapter Endpoint Configuration Wizard. The following fields are displayed top to bottom: “What do you want to call your endpoint?”, “What does this endpoint do?”, and “What do you want to configure the endpoint for?”. In the “What do you want to configure the endpoint for?" field, two options “Business Event” and “XML Gateway Map” from left to right are displayed.

  • For Outbound Integration from Oracle Integration to Oracle E-Business Suite

    When adding the Oracle E-Business Suite Adapter as an invoke (target) connection, you can use an Oracle E-Business Suite REST service to invoke an outbound integration from Oracle Integration. The available interface types that support this integration pattern are:

    • PL/SQL

    • Concurrent Program

    • Open Interface Table and View

    • Java API


    This image showns the Web Services page of Oracle E-Business Suite Adapter Endpoint Configuration Wizard. The drop-down list of the Interface Type field is highlighted to display the available interface types from the top to bottom: All, PL/SQL, Concurrent Program, Open Interface, and Java. PL/SQL is being selected.

    REST Header Mapping

    This type of integration requires the following RESTHeader elements to be passed as part of the input parameters in invoking Oracle E-Business Suite services. These header elements are used to set applications context values which are required in the API used in an integration for service invocation.

    • Responsibility: It represents responsibility_key (such as "SYSTEM_ADMINISTRATOR").

    • RespApplication: It represents Application Short Name (such as "FND").

    • SecurityGroup: It represents Security Group Key (such as "STANDARD").

    • NLSLanguage: It represents NLS Language (such as "AMERICAN").

    • Org_Id: It represents Org Id (such as "202").

    At design time, you need to map each of these RESTHeader elements from the Source section to the corresponding elements in the Target section while creating a mapping.


    This image shows the mapping for the RESTHeader elements, including Responsibility, RespApplication, SecurityGroup,NLSLanguage, and Org_Id. In the upper left, there is the Sources section with these RESTHeader elements. In the middle is the Mappings section. To the right is the Target section with these mapped RESTHeader elements shown. A green line indicates the mapping between the source and target elements.

    Additionally, you assign appropriate values to these elements if required in your mapping to pass application context values for invoking an Oracle E-Business Suite service. For example, you can assign the following values for each element listed in the table required to invoke a REST service.

    Element Value
    Responsibility 'ORDER_MGMT_SUPER_USER'
    RespApplication 'ONT'
    SecurityGroup 'STANDARD'
    NLSLanguage 'AMERICAN'
    Org_Id '204'

    After assigning each value listed above for the RESTHeader elements, you can find a box in the Mapping Canvas section displayed for each assigned target RESTHeader element.


    This image shows the mapping with assigned values for the RESTHeader elements, including Responsibility, RespApplication, SecurityGroup,NLSLanguage, and Org_Id. Each assigned value is shown in the Expression field at the bottom.

    For information about RESTHeader mapping, see the “Creating Mappings” section described in the following examples:

Topics: