An Example of Using a Business Event as a Trigger (Source) in an Integration

Overview

Sample Business Scenario

A business event "Event for OIP status update notification" (oracle.apps.ont.oip.statuschange.update) is used in this example to explain using the Oracle E-Business Suite Adapter to trigger an integration in Oracle Integration Cloud Service.

In this example, when a sales order is booked as part of the business flow, Oracle Order Management raises the event oracle.apps.ont.oip.statuschange.update, and a draft invoice is created in Oracle Accounts Receivables.

At the design time, you need to create an integration called "Order to Invoice" with Oracle E-Business Suite Order Management as a trigger (source) connected through the Oracle E-Business Suite Adapter and Oracle E-Business Suite Accounts Receivables as an invoke (target) connected through a generic REST Adapter. The "Order to Invoice" integration will subscribe to this business event.

During the runtime, when the status of the sales order is changed in the order header, the business event oracle.apps.ont.oip.statuschange.update is raised in Oracle E-Business Suite Order Management which triggers the integration. If the status of the sales order is "Booked", the order details information is fetched from Oracle E-Business Suite Order Management. The Oracle E-Business Suite Adapter prepares and propagates the order details as event payload from Order Management to invoke the integration endpoint in Oracle Integration Cloud Service. As a result, the draft invoice is created in Oracle Accounts Receivables.

Assumption

Using Business Events for Integrations in Oracle Integration Cloud Service

Based on the integration scenario, the following tasks are included in this section:

  1. Preparing the Oracle E-Business Suite Instances

  2. Establishing Oracle E-Businss Suite Connections

  3. Creating an Integration

  4. Adding the Oracle E-Business Suite Adapter (Trigger) and the REST Adapter (Invoke) to the Integration

  5. Creating Mappings

  6. Assigning Business Identifier for Tracking

  7. Activating and Testing the Integration

Preparing the Oracle E-Business Suite Instances

Before adding Oracle E-Business Suite connections, you must prepare the following Oracle E-Business Suite instances to ensure the required setup or configuration is in place.

Preparing the Order Management Instance

Perform the following tasks to ensure the required setup and configuration for Oracle E-Business Suite Order Management is ready for integrations in Oracle Integration Cloud Service:

  1. Ensure that you perform the required setup tasks to enable the Oracle E-Business Suite Adapter.

    These tasks include configuring Oracle E-Business Suite REST services, configuring the access to these services, deploying required REST services in Oracle E-Business Suite, and granting the user privileges to these services.

    Specifically, ensure that you deploy the following REST services and have grants for the operations user:

    • Metadata Provider REST service

      • Deploy the Metadata Provider API with "provider" as the service alias name

      • Deploy the Metadata Provider API with GET HTTP method for all the methods contained in the API

      • Grant the access privileges for all the methods contained in the API to the operations user

    • Event Manager REST service

      • Deploy the Event Manager API with "subscription" as the service alias name

      • Deploy the Event Manager API with POST HTTP method for all the methods contained in the API

      • Grant the access privileges for all the methods contained in the API to the operations user

    For detailed instructions on these tasks, see: Setup Tasks for Enabling the Oracle E-Business Suite Adapter.

  2. Ensure that you perform the required setup tasks to enable the inbound (trigger or source) integrations.

    These tasks include storing the ICS user credentials in Oracle E-Business Suite FND vault, setting up proxy URLs in Oracle E-Business Suite, and importing SSL certificates to Oracle E-Business Suite. For detailed instructions, see: Setup Tasks for Using the Oracle E-Business Suite Adapter as a Trigger (Source) Connection.

  3. Deploy the Order Management API, OE_ORDER_PUB (Process Order), as a REST service and grant the method access privileges to the operations user.

    In this example, only grant the "Get Order" method contained in the API to the operations user.

  4. Ensure that the profile option "OM: Raise Status Change Business Event" is set to Yes.

Preparing the Oracle Accounts Receivables Instance

Perform the following tasks to ensure the required setup and configuration for Oracle E-Business Suite Accounts Receivables is ready to use in an integration in Oracle Integration Cloud Service:

  1. Configure Oracle E-Business Suite Integrated SOA Gateway REST services.

    Follow the setup tasks as described in My Oracle Support Knowledge Document 556540.1 to configure Oracle E-Business Suite Integrated SOA Gateway Release 12.1.3 and apply the REST service patches to enable the REST service feature. For more information, see step 1, as described in Setup Tasks for Enabling the Oracle E-Business Suite Adapter.

  2. Deploy the Invoice Creation API as a REST service with the following requirements and grant the desired method access privilege to the operations user:

    • Deploy the Invoice Creation API with "invoice" as the service alias name

    • Deploy the Invoice Creation API with POST HTTP method only for the "Create Single Invoice" method contained in the API

      Note: PL/SQL APIs can be exposed as REST services only with POST HTTP method.

    • Grant the access privilege only for the Create Single Invoice method contained in the API to the operations user

    For information on deploying REST services, see Deploying REST Web Services, Administering Native Integration Interfaces and Services chapter, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

    For information on creating security grants for REST services, see Managing Grants for Interfaces with Support for SOAP and REST Web Services, Administering Native Integration Interfaces and Services chapter, Oracle E-Business Suite Integrated SOA Gateway Implementation Guide.

Establishing Oracle E-Business Suite Connections

Before creating an integration, you need to establish the following connections that will be used later in this example:

Creating the Connection for Oracle E-Business Suite Order Management

This section describes how to create a connection for the Oracle E-Business Suite Order Management instance by using the Oracle E-Business Suite Adapter. This connection will be added later as a trigger (source) in an integration.

Perform the following steps to establish the connection for Oracle E-Businss Suite Order Management in Oracle Integration Cloud Service:

  1. Log in to Oracle Integration Cloud Service.

  2. Click Connections in the Oracle Integration Cloud Service home page.

  3. Click Create New Connection.

  4. In the Create Connection - Select Adapter dialog appears.

    You can locate the Oracle E-Business Suite Adapter by entering a full or partial name to locate "Oracle E-Business Suite" from the dialog.

    For example, enter "Oracle E-Business Suite" in the Search field. The Oracle E-Business Suite Adapter is filtered from the list of adapters.

    Click the Select button for "Oracle E-Business Suite" to use the Oracle E-Business Suite Adapter. The New Connection - Information dialog appears.

  5. Enter the following information for the Oracle E-Business Suite Order Management connection:

    Creating the Order Management Connection

    the picture is described in the document text

    • Connection Name: Enter "Order Management".

    • Identifier: Accept the default populated identifier such as, ORDER_MANAGEMENT".

    • Connection Role: Select "Trigger and Invoke" role for this connection.

    • Description: Enter "Create an Oracle E-Business Suite Order Management connection" as the description.

    Click Create to create the connection.

  6. The Connection Details page is displayed for the "Order Management" connection you just created. Enter additional connection details by specifying the following information:

    • Email Address: Enter an administrator's email address to receive notifications if problems or changes occur in this connection.

    • Connection Properties: Click Configure Connectivity to open the Connection Properties dialog where you enter a URL (http://<ebs host name>:<port>) to connect to an Oracle E-Business Suite Order Management instance.

      Click OK to save your work.

    • Security: Click Configure Security to open the Credentials dialog.

      Enter operations as the username and its associated password in the Credentials dialog to access the Oracle E-Business Suite Order Management instance you specified earlier in the Connection Properties dialog.

      Click OK to save your work.

    After you specify the required connection information, the "Order Management" connection detail page appears.

  7. Click Test to test the "Order Management" connection you just specified.

  8. Click Save to save your connection.

    Click Exit Connection.

Oracle E-Business Suite connection "Order Management" appears in the Connections page.

Creating the Connection for Oracle E-Business Suite Accounts Receivables

As described earlier that Oracle E-Business Suite Order Management and Accounts Receivables are two different instances used in this example, you need to create a connection for the Oracle Accounts Receivables instance by using the REST Adapter. This connection will be added later as an invoke (target) to an integration.

  1. Log in to Oracle Integration Cloud Service.

  2. Click Connections in the Oracle Integration Cloud Service home page.

  3. Click Create New Connection.

  4. In the Create Connection - Select Adapter dialog appears.

    Enter "REST" in the Search field. The REST Adapter is filtered from the list of adapters.

    Searching REST Adapter in the Create Connection - Select Adapter Dialog

    the picture is described in the document text

    Click the Select button for "REST" to use the REST Adapter. The New Connection - Information dialog appears.

  5. Enter the following information for the Oracle E-Business Suite Accounts Receivables connection:

    Creating the Accounts Receivables Connection

    the picture is described in the document text

    • Connection Name: Enter "Receivables" as the connection name.

    • Identifier: Accept the default populated identifier such as "RECEIVABLES".

    • Connection Role: Select "Trigger and Invoke" role for this connection.

    • Description: Enter "Create a connection for Oracle E-Business Suite Receivables" as the description.

    Click Create to create the connection.

  6. The Connection Details page is displayed for the "Receivables" connection you just created. Enter additional connection details by specifying the following information:

    • Email Address: Enter an administrator's email address to receive notifications if problems or changes occur in this connection.

    • Click Configure Connectivity to open the Connection Properties dialog. Enter the following information:

      • Connection Type: Select "REST API Base URL".

      • Connection URL: Enter a connection URL (http://<ebs host name>:<port>/webservices/rest/invoice) for the Invoice Creation REST service with invoice alias name that you deployed earlier while preparing the Receivables instance.

        Entering the Connection Properties through the REST Adapter

        the picture is described in the document text

        Click OK to save your work.

      • Security: Click Configure Security to open the Credentials dialog.

        Accept the "Basic Authentication" as the default security policy.

        Enter operations as the username and its associated password in the Credentials dialog to access the Invoice Creation REST service you specified earlier in the Connection Properties dialog.

        Entering User Credentials in the Credentials Dialog

        the picture is described in the document text

        Click OK to save your work.

  7. Click Test to test the connection you just specified for Oracle E-Business Suite Accounts Receivables.

  8. Click Save to save your connection.

    Click Exit Connection

Oracle E-Business Suite connection "Receivables" now appears in the Connections page.

Creating an Integration

Based on the business scenario described earlier, you need to create an integration called "Order to Invoice" with the Orchestration pattern. This pattern allows you to orchestrate trigger, invoke, and switch activities if required into a process diagram in an integration. You can also add mappings on switch branches later if needed.

This section describes how to create an integration with the Orchestration pattern. Information on adding each activity in the diagram is explained later in this chapter.

Perform the following steps to create an integration:

  1. In the Integration Cloud Service toolbar, click Designer.

  2. In the Designer Portal, click Integrations.

  3. In the Integrations page, click New Integration.

    The Create Integration - Select a Style/Pattern dialog appears.

    Click Select for the "Orchestration" integration pattern that is used in this example.

    Creating the Integration with the Orchestration Pattern

    the picture is described in the document text

  4. The New Integration - Information dialog appears. Enter the following information:

    • What do you want to call your integration? Enter a meaningful name for your integration, such as "Order to Invoice".

    • Identifier: Accept the default identifier value "ORDER_TO_INVOICE".

    • Version: Accept the default version number.

    • What does this integration do? Enter "Create an integration for order to invoice" as the description for this integration.

    • Which package does this integration belong to? Leave it blank.

    Entering Integration Information in the New Integration - Information Dialog

    the picture is described in the document text

  5. Click Create and Save.

To complete the integration, you need to add the following tasks that are described in the next few sections:

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

In this example, you need to add the following activities in the integration:

Adding 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 page, drag and drop the Oracle E-Business Suite connection called "Order Management" from the TRIGGERS toolbar on the left to the large + section within the circle in the integration canvas.

    Dragging the Order Management Connection to the Center to Start the Integration

    the picture is described in the document text

    The Configure Oracle E-Business Suite Adapter Endpoint wizard appears.

  2. 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.

    Entering the Basic Information for the Adapter Endpoint with Business Event

    the picture is described in the document text

    Click Next to proceed with the rest of the configuration.

  3. 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) and description, is automatically populated in this page.

    Selecting a Desired Business Event

    the picture is described in the document text

    Click Next.

  4. 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 TRIGGER in the integration flow.

Adding a SWITCH with Two Branch Rules

Perform the following steps to add a SWITCH:

  1. Drag and drop the SWITCH action from the ACTIONS section on the left to the integration right after the Order_Status_Update activity.

    Adding the SWITCH Action After the Order_Status_Update Activity

    the picture is described in the document text

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

    Adding Two Branches to the Integration Flow

    the picture is described in the document text

  2. Click edit on the first rule. The Condition Builder page appears.

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

    • Enter "Booked Order" as the Expression Name.

    • In the Match field, select "All of" from the list.

    • In Source section, 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 to the right top under the New Condition section.

        • Select = from the drop-down list.

        • Enter 'STATUS_CODE' in the text box as the condition value.

        Click the Add Condition (+) icon.

      2. Drag and drop the Value element to the right top under the New Condition section.

        • Select = from the drop-down list.

        • Enter 'BOOKED' in the text box as the condition value.

        Click the Add Condition (+) icon.

    Editing the First Rule (Booked Order) with Required Condition

    the picture is described in the document text

    Save your work. Click Exit Condition Builder to return to the integration.

Adding 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. Drag and drop the Oracle E-Business Suite connection "Order Management" from the INVOKES toolbar on the left to the integration right after the Booked Order rule.

    The Configure Oracle E-Business Suite Adapter Endpoint 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".

    • 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.

    Selecting an API in the Web Services Page

    the picture is described in the document text

    Click Next.

  4. The selected API internal name OE_ORDER_PUB appears in the Operations page.

    In the Methods field, select a desired method name contained in the API. For example, select "GET_ORDER". The corresponding service status value is displayed in the Operations page, along with the description information.

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

    Selecting a Method as the Target Endpoint for the Integration

    the picture is described in the document text

    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).

    Displaying the Selected API Details in the Summary Page

    the picture is described in the document text

    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: Creating Mappings.

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

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

  1. Drag and drop the Oracle E-Business Suite connection "Receivables" from the INVOKES toolbar on the left to the integration, after the Get_Order activity in the Booked Order route.

    The Configure Oracle REST Endpoint 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".

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

    • What action does the endpoint perform? - 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.

    Entering the Basic REST Endpoint Information

    the picture is described in the document text

    Click Next.

  2. 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 Create_Invoice Activity Used in the 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.

    the picture is described in the document text

    Click Next and Next.

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

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

    • REST Service URL: http://<host name>:<port>/webservices/rest/invoice/create_single_invoice/.

    • Method: POST

    • Request Media Type: application/xml

    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: Creating Mappings

    Save the integration.

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

The "Order to Invoice" Integration Flow Diagram

the picture is described in the document text

Creating Mappings

Oracle E-Business Suite Business Event is defined by the WF_EVENT_T data structure. After adding the required connections to the integration, you need to create the following mappings to pass the required parameter values to the subsequent REST services:

Creating Mappings for the Get_Order Map

In this example, a sales order Header Id is available as one of the business event parameters. In WF_EVENT_T, event parameters are available as Name-Value pair in repeating Parameter element. To obtain the value of the Header Id parameter and pass it to the subsequent Get_Order service call, you need to create mappings for the Get_Order map.

  1. In the Order_Status_Update integration flow, click edit for the Get_Order map icon.

    Selecting the Get_Order Map for Mapping

    the picture is described in the document text

    The Mapper page is displayed.

  2. In the Mapper page, the business event related elements are displayed in the Source section, whereas the Get_Order related parameters are listed in the Target area. To obtain the value of the sales order Header Id (P_HEADER_ID) included as part of the event parameters and pass it to the subsequent Get_Order REST service, you need to define the XSL expression for the P_HEADER_ID parameter.

  3. Define the XSL expression for the P_HEADER_ID parameter by performing the following tasks:

    1. In the Target section, expand the GET_ORDER_Input node, and then the InputParameters node. Click the P_HEADER_ID element to open the Build Mappings page.

    2. In the Mapping area of the Build Mappings page, notice that the P_HEADER_ID element is displayed as the Target element.

    3. In Source section of the Build Mappings page, expand the BusinessEvent_Input node, then the InputParameters node, then the BusinessEvent node, then the ParameterList node, and then the Parameter node.

    4. Drag and drop the Value element from the Source section to the Mapping section as the value for the P_HEADER_ID element.

    5. Similarly, drag and drop the XSL element "if" and the Name element from the Source section to the Mapping section to define the XSL expression <xsl:if test="nssrcmpr:Name='HEADER_ID'">.

    6. Drag and drop the XSL element "for-each" from the Source section to the Mapping section to define the XSL expression <xsl:for-each select="/nssrcmpr:BusinessEvent_Input/nssrcmpr:InputParameters/nssrcmpr:BusinessEvent/nssrcmpr:ParameterList/nssrcmpr:Parameter">.

      Displaying the Mappings for the P_HEADER_ID Parameter

      the picture is described in the document text

    7. Save your work.

      Expand the nodes to ensure that the P_HEADER_ID parameter is included as part of the structure.

  4. Perform the following tasks to assign constant values to the target elements:

    1. In the Target section, expand the GET_ORDER_Input node, and then the RESTHeader node.

      Click the Responsibility element to open the Build Mappings page.

    2. Enter "ORDER_MGMT_SUPER_USER" in the text box as the value for the Responsibility element.

    Similarly, use the same approach to assign appropriate values to the target elements listed in the following table:

    Path Element Value
    GET_ORDER_Input/RESTHeader RespApplication ONT
    GET_ORDER_Input/RESTHeader SecurityGroup STANDARD
    GET_ORDER_Input/RESTHeader NLSLanguage AMERICAN
    GET_ORDER_Input/RESTHeader Org_Id 204
    GET_ORDER_Input/InputParameters P_API_VERSION_NUMBER 1.0
    GET_ORDER_Input/InputParameters P_INIT_MSG_LIST F
    GET_ORDER_Input/InputParameters P_ORG_ID 204

    After you complete the mappings for Get_Order, the mapped source values should appear in the Mapping column of the Target section.

    Displaying the Mappings for the Get_Order Activity

    the picture is described in the document text

  5. Click Save to save your work.

Creating Mappings for the Create_Invoice Map

Perform the following steps to create the mappings:

  1. In the Order_Status_Update integration flow, click edit for the Create_Invoice map icon.

    The Mapper page appears.

  2. Assign constant values to the target elements.

    1. In the Target section, expand the execute node, then the CREATE_SINGLE_INVOICE_Input node, and then the RESTHeader node.

      Click the Responsibility element to open the Build Mappings page.

    2. Enter "RECEIVABLES_VISION_OPERATIONS" in the text box as the value for the Responsibility element.

    Similarly, use the same approach to assign appropriate values to the target elements listed in the following table:

    Path Element Value
    CREATE_SINGLE_INVOICE_Input/RESTHeader RespApplication AR
    CREATE_SINGLE_INVOICE_Input/RESTHeader SecurityGroup STANDARD
    CREATE_SINGLE_INVOICE_Input/RESTHeader NLSLanguage AMERICAN
    CREATE_SINGLE_INVOICE_Input/RESTHeader Org_Id 204
    CREATE_SINGLE_INVOICE_Input/InputParameters P_API_VERSION 1.0
    CREATE_SINGLE_INVOICE_Input/InputParameters P_INIT_MSG_LIST T
    CREATE_SINGLE_INVOICE_Input/InputParameters P_COMMIT T
    CREATE_SINGLE_INVOICE_Input/InputParameters/P_BATCH_SOURCE_REC BATCH_SOURCE_ID 1188
    CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_HEADER_TBL/P_TRX_HEADER_TBL_ITEM TRX_HEADER_ID 101
    CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_HEADER_TBL/P_TRX_HEADER_TBL_ITEM CUST_TRX_TYPE_ID 1684
    CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_HEADER_TBL/P_TRX_HEADER_TBL_ITEM BILL_TO_CUSTOMER_ID 1290
    CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_HEADER_TBL/P_TRX_HEADER_TBL_ITEM SHIP_TO_CUSTOMER_ID 1290
    CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_HEADER_TBL/P_TRX_HEADER_TBL_ITEM COMMENTS Invoice created via ICS integration for booked Sales Order in Order Management

    After you complete this step, the mapped source values should appear in the Mapping column of the Target section.

    Displaying the Mappings with Constant Values

    the picture is described in the document text

  3. Add the following mapping for the header:

    • In the Source section, enter "HEADER_ID" in the Search field to locate this parameter.

      Select the HEADER_ID element from the X_HEADER_REC node.

    • In the Target section, expand the execute node, then the CREATE_SINGLE_INVOICE_Input node, then the InputParameters node, then the P_TRX_HEADER_TBL node, and then the P_TRX_HEADER_TBL_ITEM node.

      Select the TRX_NUMBER element.

    Drag the HEADER_ID element from the Source section to the TRX_NUMBER element in the Target section to map the data.

    After the mapping, the source element HEADER_ID should appear in the Mapping column next to the TRX_NUMBER element in the Target section.

    Mapping the Source HEADER_ID to the Target TRX_NUMBER

    the picture is described in the document text

  4. Use the same approach, as described in the previous step, to add the following sets of mappings for the line items:

    Source Path Source Element Target Path Target Element
    BusinessEvent_Input/InputParameters/BusinessEvent/X_LINE_TBL/X_LINE_TBL_ITEM LINE_NUMBER execute/CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_LINES_TBL/P_TRX_LINES_TBL_ITEM LINE_NUMBER
    BusinessEvent_Input/InputParameters/BusinessEvent/X_LINE_TBL/X_LINE_TBL_ITEM ORDERED_ITEM execute/CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_LINES_TBL/P_TRX_LINES_TBL_ITEM DESCRIPTION
    BusinessEvent_Input/InputParameters/BusinessEvent/X_LINE_TBL/X_LINE_TBL_ITEM ORDERED_QUANTITY execute/CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_LINES_TBL/P_TRX_LINES_TBL_ITEM QUANTITY_ORDERED
    BusinessEvent_Input/InputParameters/BusinessEvent/X_LINE_TBL/X_LINE_TBL_ITEM ORDERED_QUANTITY execute/CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_LINES_TBL/P_TRX_LINES_TBL_ITEM QUANTITY_INVOICED
    BusinessEvent_Input/InputParameters/BusinessEvent/X_LINE_TBL/X_LINE_TBL_ITEM UNIT_SELLING_PRICE execute/CREATE_SINGLE_INVOICE_Input/InputParameters/P_TRX_LINES_TBL/P_TRX_LINES_TBL_ITEM UNIT_SELLING_PRICE

    Once you complete this step, the mapped source values should appear next to the corresponding target elements with the green check mark icons:

    Displaying the Mappings for the Line Items

    the picture is described in the document text

  5. Assign the following values:

    • In the Target section, expand the execute node, then the CREATE_SINGLE_INVOICE_Input node, then the InputParameters node, and then the P_TRX_DIST_TBL node.

      Click the P_TRX_DIST_TBL_ITEM element to open the Build Mappings page.

      In the Mapping section, enter the following information:

      <nsmpr1:P_TRX_DIST_ID/>.

    • In the Target section, expand the execute node, then the CREATE_SINGLE_INVOICE_Input node, then the InputParameters node, and then the P_TRX_SALESCREDITS_TBL node.

      Click the P_TRX_SALESCREDITS_TBL_ITEM element to open the Build Mappings page.

      In the Mapping area, enter the following information:

      <nsmpr1:P_TRX_SALESCREDITS_ID/>.

    The newly assigned mapping values should appear next to the corresponding elements in the Target section.

    Displaying the Mappings

    the picture is described in the document text

    Save your work.

  6. Click Exit Mapper.

  7. Save the integration.

Assigning Business Identifier for Tracking

Perform the following steps to track payload fields in messages during runtime:

  1. In the Create Order Integration page, click Tracking.

    The Business Identifiers For Tracking dialog appears.

  2. From the Available Source Fields section, expand the BusinessEvent_Input node, then the InputParameters node, and then the BusinessEvent node.

    Drag and drop the Event Key element to the Tracking Field column in the table as the primary Tracking field.

  3. Click Done.

  4. Save your work and then click Exit Integration.

Activating and Testing the Integration

Perform the following steps to activate the integration:

  1. In the Integrations page, click Activate for the "Order to Invoice" integration that you created earlier.

  2. The Confirmation dialog appears. Click Activate to confirm this action.

    The status of the "Order to Invoice" integration is now changed to ACTIVE with a green check mark icon.

Testing the Integration at Runtime

  1. Log in to Oracle E-Business Suite as the operations user who has the Order Management Super User, Vision Operations (USA) responsibility.

  2. Select Order, Returns and then Sales Order from the navigation menu to open the Sales Orders form.

  3. In the Sales Orders form, select the Order Information tab.

  4. Create a new Sales Order for customer "A.C. Networks" with the following information:

    • Customer: A.C. Networks

    • Operation Unit: Vision Operations

    • Order Type: Mixed

    • Ship To Location: Provo (OPS) 3405 East Bay Blvd. Provo, UT 84606, US

    • Bill To Location: Provo (OPS) 3405 East Bay Blvd. Provo, UT 84606, US

    • Price List: Corporate

    • Currency: USD

    Creating a Sales Order in the Sales Orders Form

    the picture is described in the document text

  5. Select the Line Items tab to add the following line item:

    • Ordered Item: AS54888

    • Quantity: 1

    • Item Type: STANDARD

    • UOM: Each

    • Unit Price: Accept the populated unit price.

    • Request Date: Accept the populated date (such as 14-MAY-2016)

    Adding Line Items for the Sales Order

    the picture is described in the document text

  6. Save this new order.

    This order is created with "Entered" status.

  7. Click Book Order.

    The order status is now updated to "Booked". It internally raises a business event oracle.apps.ont.oip.statuschange.update which will trigger the integration.

In the design time, the "Order to Invoice" integration created earlier in Oracle Integration Cloud Service will subscribe to this business event. At runtime, since the order status is changed to "Booked", Oracle Order Management will raise the business event which triggers the integration in Oracle Integration Cloud Service. The order details information is fetched from Oracle E-Business Suite Order Management and passed as event payload to create the invoice in Oracle Accounts Receivables.

Monitoring the Result in Oracle Integration Cloud Service

  1. Log in to Oracle Integration Cloud Service.

    On the Integration Cloud Service toolbar, click Monitoring.

  2. In the navigation pane, click Tracking.

    The Tracking page appears.

  3. Click the instance created for the "Order to Invoice" integration.

    Displaying the Tracking Page for the Order to Invoice Integration

    the picture is described in the document text

  4. Click "Event Key" to display the flow diagram of the integration instance.

    This page provides the instance tracking information. Notice that the status of this instance is "Completed" indicating that the integration is executed successfully. You can verify if there is any error occurred if desired.

    Viewing and Tracking the Orchestration Flow of the Instance

    the picture is described in the document text

Validating the Result in Oracle E-Business Suite Accounts Receivables

Log in to Oracle Accounts Receivables as the operations user who has the Receivables, Vision Operations (USA) responsibility. Select Transactions and then Transactions from the navigation menu.

Locate the invoice transaction for the "A.C. Networks" customer by selecting Query for Transaction. The invoice should be created in Oracle Accounts Receivables.