1. Using the Oracle E-Business Suite Adapter with Oracle Integration 3
  2. Oracle E-Business Suite Adapter Samples
  3. An Example of Using a Business Event as a Trigger (Source) in an Integration
  4. Add the Oracle E-Business Suite Adapter (Trigger) and the REST Adapter (Invoke) to the Integration

Add the Oracle E-Business Suite Adapter (Trigger) and the REST Adapter (Invoke) to the Integration

In this example, the orchestration flow diagram created for this integration includes the following activities:

  • The Oracle E-Business Suite Adapter as a trigger activity called "Order_Status_Update" for the Oracle E-Business Suite Order Management instance

    This trigger activity uses the business event oracle.apps.ont.oip.statuschange.update through the Oracle E-Business Suite Adapter. When the status of a sales order is updated, Oracle Order Management raises this event.

    See: Add the Oracle E-Business Suite Adapter as a Trigger with a Business Event.

  • A switch added with two branches

    • The defined branch called "Booked Order" is the major orchestration flow for the integration.

    • The Otherwise branch is not used in this example.

    See: Add a Switch with Two Branch Rules.

  • Mappings defined for "Get_Order"

    It allows you to map and pass the order related parameters to the "Get_Order" activity to invoke the GET_ORDER REST Service.

    See: Create Mappings.

  • The Oracle E-Business Suite Adapter as an invoke activity called "Get_Order" for the Oracle E-Business Suite Order Management instance.

    This invoke activity uses the GET_ORDER operation of the Process Order (OE_ORDER_PUB) REST service when adding the Oracle E-Business Suite Adapter as an invoke. This service retrieves the sales order information.

    See: Add the Oracle E-Business Suite Adapter as an Invoke for the "Get_Order" Activity.

  • Mappings defined for "Create_Invoice"

    This activity assigns the sales order related elements from the "Get_Order" activity to the Invoice related elements in the "Create_Invoice" activity.

    See: Create Mappings.

  • The REST Adapter as an invoke activity called "Create_Invoice" for the Oracle E-Business Suite Accounts Receivables instance

    This activity configures a request payload using the XML schema file type and then creates an invoice in Oracle Accounts Receivables through the invocation of the CREATE_SINGLE_INVOICE REST service.

    See: Add the REST Adapter as an Invoke for the "Receivables" Activity.


This image shows the “Order to Invoice” integration orchestration flow. From top to bottom are the Order_Status_Update Oracle E-Business Suite Adapter icon, and a switch action with two branches. The left branch includes a Booked Order switch icon, Get_Order mapper icon, the Get_Order Oracle E-Business Suite Adapter icon, a Create_Invoice mapper icon, and the Create_Invoice REST Adapter icon. The right branch is an Otherwise element. The two branches come together and connect to a return action.

Topics:

Add the Oracle E-Business Suite Adapter as a Trigger with a Business Event

Perform the following steps to add the first activity called "Order_Status_Update" for the Oracle E-Business Suite Order Management connection:

  1. In the "Order to Invoice" integration canvas, click the + sign in the integration canvas or click Triggers Triggers icon on the side of the canvas. A list of trigger connections appears.

  2. Search the Oracle E-Business Suite connection called "Order Management" from the list of selection. The Oracle E-Business Suite Adapter Endpoint Configuration Wizard appears.

  3. Enter the following information in the Basic Info page:

    • What do you want to call your endpoint? - Enter "Order_Status_Update" as the endpoint name.

    • What does this endpoint do? - Enter the description of this integration endpoint.

    • What do you want to configure the endpoint for? - Select Business Event.

    Click Next to proceed with the rest of the configuration.

  4. In the Business Events page, specify the following information for your connection:

    • Product Family: Select "Order Management Suite" from the drop-down list.

    • Product: Select "Order Management" from the drop-down list.

    • Business Event: Select "Event for OIP status update notification" from the populated list.

      After you select an event name, the corresponding event information, including internal name (oracle.apps.ont.oip.statuschange.update), event status “Enabled”, and description, is automatically populated in this page.

    Click Next.

  5. The Summary page appears with the selected event information. The Oracle E-Business Suite Adapter source endpoint configuration is successfully created with the selected event.

    Click Done.

    The "Order_Status_Update" endpoint now appears as a trigger in the integration flow.

Add a Switch with Two Branch Rules

Perform the following steps to add a Switch:

  1. On the side of the canvas, click Actions Integration actions iconand drag the Switch action to the integration right after the Order_Status_Update activity.

    This action adds two rules allowing you to define routing expression branches for your integration.

  2. Click edit on the first rule. This invokes the Input Sources tree and Configure Route dialog.

  3. In the Configure Route dialog, enter the following information to create the condition: All of Name = 'STATUS_CODE' and Value = 'BOOKED':

    • Enter "Booked Order" as the Name.

    • In Source section of the Input Sources tree, expand the BusinessEvent_Input node, then the InputParameters node, then the BusinessEvent node, then the ParameterList node, and then the Parameter node.

      1. Drag and drop the Name element from the tree to the upper Value field in the Configure Route dialog.

        • Select = from the drop-down list.

        • Enter 'STATUS_CODE' in the lower Value field as the condition value.

        Click Add Condition.

      2. Drag and drop the Value element from the tree to the upper Value field in the Configure Route dialog.

        • Select = from the drop-down list.

        • Enter 'BOOKED' in the lower Value field as the condition value.

        Click Add Condition.

    • Select All of as the match list.


      This image shows the Configure Route dialog on the right and the Input Sources tree on the left. The Configure Route dialog shows the route name on top and then

    Click Save to save your work.

Add the Oracle E-Business Suite Adapter as an Invoke for the "Get_Order" Activity

Perform the following steps to add the Oracle E-Business Suite Adapter as an invoke connection:

  1. Click the + sign right after the Booked Order rule you created earlier. Locate the Oracle E-Business Suite connection "Order Management" from the Trigger Triggers icon section.

    The Oracle E-Business Suite Adapter Endpoint Configuration Wizard appears.

  2. In the Basic Info page, enter the following information:

    • What do you want to call your endpoint? - Enter "Get_Order" as the endpoint name.

    • What does this endpoint do? - Enter the description of this integration endpoint, such as "Get an order in Oracle E-Business Suite".

    Click Next.

  3. In the Web Services page, specify the following information for your target connection:

    • Product Family: Select "Order Management Suite" from the drop-down list.

    • Product: Select "Order Management".

    • Interface Type: Select "PL/SQL".

    • API: Select "Process Order API" from the populated list for this example.

      The corresponding API internal name (OE_ORDER_PUB) and description are automatically populated.

    Click Next.

  4. In the Operations page, select a desired method name contained in the selected API (OE_ORDER_PUB). For example, select "GET_ORDER". The corresponding service status value "Ready to Use" is displayed in this page, along with the description information.

    Note:

    The Service Status of the selected method GET_ORDER should be "Ready to Use".

    This image shows the Operations page of the Oracle E-Business Suite Adapter Endpoint Configuration Wizard. The following fields are displayed top to bottom: API, Methods, Service Status, and Description

    Click Next.

  5. The Summary page displays the selected API information. This includes the selected product family name (Order Management Suite), product name (Order Management), web service name (OE_ORDER_PUB), integration pattern (Synchronous), operation name (GET_ORDER), and the operation status (Ready to Use).

    Click Done.

    The "Get_Order" activity for Order Management now appears as part of the integration flow, along with the "Get_Order" map icon where you can define the mapping later. See: Create Mappings.

Add the REST Adapter as an Invoke for the "Receivables" Activity

Perform the following steps to add the REST Adapter as an invoke connection:

  1. Hover your cursor over the lines after the "Get_Order" activity that you just created, and then click the + sign. A list of invoke connections appears. Select the Oracle E-Business Suite connection "Receivables" from the list of selection.

    The Oracle REST Adapter Endpoint Configuration Wizard appears. Enter the following information in the Basic Info page:

    • What do you want to call your endpoint? - Enter the name of this endpoint, such as "Create_Invoice".

    • What does this endpoint do? - Enter the usage of this endpoint, such as "Provide REST endpoint with input payload for invoice creation".

    • Select to configure multiple resources or verbs (maximum 11)? - Leave this field unchecked.

    Click Next.

  2. In the Resource Configuration page, enter the following information:

    • What does this operation do? - Enter the usage of this operation, such as "Provide REST endpoint with input payload for invoice creation".

    • What is the endpoint's relative resource URI? - Enter "/create_single_invoice/".

    • What action do you want to perform on the endpoint? - Select "POST" from the drop-down list.

    • Configure a request payload for this endpoint - Select this check box indicating that a request payload is required in this activity.

  3. In the Request page, perform the following tasks:

    • In the "Select the request payload file" section, select the XML schema radio button.

      Please note that the request payload file type can be either XML schema or JSON format.

    • Browse and select the sample XSD for the Create Invoice REST service.

      For the sample XSD information, see Sample XSD for the Oracle E-Business Suite Adapter as a Trigger with a Business Event Example.

    • In the Element field, select "CREATE_SINGLE_INVOICE_Input" from the drop-down list.

    • In the "Select the type of payload with which you want the endpoint to receive" section, select the XML button as the payload type.


    Description of be_rest.gif follows
    Description of the illustration be_rest.gif

    In this example, we do not need to configure this endpoint to receive Response.

  4. Click Next. This displays the Summary page with the following REST service information that you specified earlier. Click Done.

    The "Create_Invoice" activity appears in the integration flow, listed as the last activity in the Booked Order rule.

    Similar to the "Get_Order" activity, the "Create_Invoice" map icon also appears (along with the "Create_Invoice" activity) where you can define the mapping later. See: Create Mappings.

    Save the integration.

At the end of this step, the integration flow contains the activities added in this section.