Oracle Integration - ERP Cloud Extracts Lab

Oracle Documentation

Background

Oracle Integration provides native connectivity to Oracle and non-Oracle Software as a Service (SaaS) and On-premises applications, such as Oracle ERP Cloud, Oracle Service Cloud, Oracle HCM Cloud, Salesforce.com, Workday, EBS, SAP, NetSuite and so on. Oracle Integration adapters simplify best practice connectivity to these applications by handling many of the underlying technical complexities often encountererd when integrating applications.


Use Case

This use case explores the use of Oracle Integration to extract data from Oracle Business Intelligence Publisher (BIP). This use case includes the following steps:

  • Get the most recent list of approved invoices.
  • Extract the most recent payment data and update other applications to reflect new payments.
  • Deliver the report to UCM or SFTP or trigger a report using ERP integration service.

The data file can be larger than 10MB. Oracle Integration supports handling large files as an attachment (instead of base64 encoding). We recommend that you use CSV format to reduce the size of the file.

See this blog article to learn how to handle files from various interfaces and file size constraints.

The following diagram shows the interaction between the systems involved in this use case.


Before You Begin

Some steps in this tutorial have a Copy to Clipboard icon next to them. Click this icon to copy the snippet of text to your clipboard and then paste where needed.

Your instructor will provide you the information you need to access the environments used in this lab.


For this lab we will provide you the following:

  • Oracle Integration
  • ERP Cloud
  • FTP Server

For this lab you will need the following:

  • FTP Client

Get Your Oracle Integration (OIC) Environment

Select your OIC Environment and enter your User Number to get the information needed to access Oracle Integration.

Select your OIC environment

 


Get Your ERP Cloud Environment

Select your ERP Cloud Payables environment to get the information needed to access Oracle ERP Cloud.

ERP Cloud Environment


Get Your FTP Environment

Select your FTP Environment to get the information to access the FTP server:

FTP Environment


Sign In

  1. Open your Oracle Integration instance.

  2. Enter your user name and password.

    Your password will be provided by the instructor.
  3. Click Sign In.

    The Home page appears.

    You are now logged in and ready to use Oracle Integration.


Create the ERP Bulk Extract Integration

  1. On the Home page, click Integrations, and then click Integrations.
  2. On the Integrations page, click Create.
  3. In the Select Integration Style dialog, select Scheduled Orchestration.
  4. Click Select.
  5. In the Create New Integration dialog, configure the integration:
    1. What do you want to call your integration?

      Enter ERP Bulk Extract

    2. In the What does this integration do? field, enter:

      This integration starts the extraction of payable transactions in the ERP Cloud.

  6. Click Create.

Create the Initiate Extract Activity

  1. Hover over the outgoing arrow for the Schedule activity and click Add icon.
  2. In the Search field, begin typing ERP Cloud to find your connection.
  3. Select the connection named ERP Cloud.

    The Configure Oracle ERP Cloud Endpoint wizard appears.

  4. Name your endpoint InitiateExtract.
  5. In the What does this endpoint do? field, enter

    This endpoint starts the extraction of payable transactions.

  6. Click Next.
  7. On the Actions page, select the Query, Create, Update or Delete Information option.
  8. Click Next.
  9. On the Operations page, from the Browse by list, select Services.
  10. In the Select a Service field, enter ERPIntegrationService and select it from the list.
  11. From the Operation to perform on the Business Object/Resource or Service list, select Export Bulk Data.
  12. Click Next.

    A summary of the properties you configured appears.

  13. Review the summary and click Done.
  14. On the Integration canvas, from the Layout list, select Horizontal.

  15. Click Save to save the integration.

Define the Data Mapping

A Map action named Map to InitiateExtract is automatically created. We'll define this data mapping.

  1. Select the Map to InitiateExtract action.
  2. Click Edit icon.

    The Data Mapping page appears.

    Note: Ignore the suggestion for recommended mappings.

  3. In the Target section, expand the InitiateExtract Request element.
  4. In cases where you are not mapping from source to target, for example when the target requires a literal value or expression, you need to manually create the target node:

    1. Right-mouse click on the desired node and select Create Target Node.
    2. Click Edit icon in the Expression editor to enable edit mode.

      Enter the desired literal value or expression in the Expression editor at the bottom of the page.


      Note: Literal values need to be enclosed in " "

      The literal values include in this lab guide are already enclosed in " ", so please do not add additional quotes.

    3. Click Save icon in the Expression editor to commit the data.

      Verify a graphic is added to the mapping canvas indicating your target node has the literal or expression correctly mapped.

      Literal Mapping

  5. Map the fields under the InitiateExtract Request element to the following literal values:

    • jobName: "oracle/apps/ess/financials/commonModules/shared/common/outbound,FinOutboundProcess"
    • parameterList: "92,/oracle/apps/ess/financials/commonModules/shared/common/outbound;PayablesTransactionsExtract,BIPREPORT,FULL_EXTRACT,#NULL,300000046987012,#NULL,#NULL,#NULL,#NULL,#NULL,12-19,N,N,300000046975971,#NULL,#NULL,#NULL,FULL_EXTRACT,#NULL,#NULL,#NULL,PayablesTransactionsExtract,#NULL"
    • jobOptions: "ExtractFileType=ALL"
    • callbackURL: skip this mapping for now. We will assign a value after we design and activate the callback flow.
    • notificationCode: 30
  6. Click Validate.
  7. Click Close.
  8. Click Save to save the integration.

Define the Tracking Fields

  1. In the Integration canvas, you should see an error icon Error icon next to the Last Saved field.

    The icon shows the number of errors you need to fix in your integration. You should have one error. To fix this error you need to add business tracking identifiers.

  2. On the Integration canvas, click Actions icon, and then select Tracking.

    Tracking selection

  3. In the Business Identifiers for Tracking dialog, from the Source section, select StartTime, and then click Edit icon.

    The selected field appears in the Tracking Fields table. The StartTime field is marked as Primary.

  4. Click Save.

    Notice there are no errors.

  5. On the Integration canvas, click Save, and then click Close.

Create the ERP Bulk Extract Callback Integration

  1. On the Integrations page, click Create.
  2. In the Select an Integration Style dialog, select App Driven Orchestration.
  3. Click Select.
  4. In the Create New Integration dialog, configure the integration:
    1. What do you want to call your integration?

      Enter ERP Bulk Extract Callback

    2. In the What does this integration do? field, enter:

      This integration is triggered when it receives a callback from the ERP Bulk Extract integration. When it receives the callback, it downloads the extract, and uploads it to an FTP server.

  5. Click Create.

Create the ERP Cloud Callback Trigger

  1. Hover over START and click Add icon.
  2. Begin typing ERP Cloud Callback in the Search field to find the connection to your ERP Cloud Callback.
  3. Select the connection named ERP Cloud Callback.

    The Configure SOAP Endpoint wizard appears.

  4. Name your endpoint BulkExtractCallback.
  5. In the What does this endpoint do? field, enter:

    This endpoint defines an ERP Cloud callback.

  6. Click Next.
  7. On the Operations page, from the Disable SOAP Action Validation options, select No.
  8. Click Next.
  9. On the Callback Operation page, from the type of response expected options, select No Response.
  10. Click Next.
  11. On the Headers page, from the Do you want to configure headers for this endpoint? options, select No.
  12. Click Next.

    A summary of the properties you configured appears.

  13. Review the summary and click Done.
  14. On the Integration canvas, from the Layout list, select Horizontal.

  15. Click Save to save the integration.

Create the Download Activity

  1. Hover over the outgoing arrow for the BulkExtractCallback activity and click Add icon.
  2. In the Search field, begin typing ERP Cloud Integration Service to find your connection.
  3. Select the connection named ERP Cloud Integration Service.

    The Configure SOAP Endpoint wizard appears.

  4. Name your endpoint DownloadFile.
  5. Click Next.
  6. On the Operations page, from the Operation list, select getDocumentsForFilePrefix.

    Be careful to select the correct operation as many of them have similiar names.

    GetDocuments For File Prefix

  7. Click Next.
  8. On the Headers page, select Accept attachments in response.

    Note: The SOAP adapter allows rich capability to accept content as an attachment, instead of base64-encoded data.

    If you don't see this option, it is likely you selected the wrong operation. Click Back and verify you have the correct operation.

  9. Click Next.

    A summary of the properties you configured appears.

  10. Review the summary and click Done.
  11. Click Save to save the integration.

Define the Data Mapping

A Map action named Map to DownloadFile is automatically created. We'll define this data mapping.

  1. Select the Map to DownloadFile action.
  2. Click Edit icon.

    The Data Mapping page appears.

  3. In the Target section, expand the OutboundSOAPRequestDocument, Body, then getDocumentsForFilePrefix elements.
  4. Click the Toggle Functions button located in the Target section toolbar.

  5. In the Component palette, expand the String node.
  6. Drag the concat function and drop it on prefix element in the Target section.
  7. In the Expression window, edit the concat function to use the following parameters:

    1. "ESS_"
    2. //requestId
    3. "_BIPReport0"

    The complete expression should read: concat ( "ESS_", //requestId, "_BIPReport0" )

  8. Click Save icon in the Expression editor to commit the expression.

  9. Map the account element to the following expression: "fin$/payables$/export$"
    1. Right-mouse click on the account node and select Create Target Node.

    2. Click Edit icon in the Expression editor to enable edit mode.

    3. Enter the literal value.

    4. Click Save icon in the Expression editor to commit the data.

  10. In the same way. map the comments element to the following expression: concat ( "processedby=", //requestId )
  11. Click Validate.
  12. Click Close.
  13. Click Save to save the integration.

Create the Write Extract Activity

  1. Hover over the outgoing arrow for the DownloadFile activity and click Add icon.
  2. In the Search field, begin typing FTP File Server to find your connection.
  3. Select the connection named FTP File Server.

    The Configure Oracle Adapter Endpoint Configuration Wizard appears.

  4. Name your endpoint WriteExtract.
  5. Click Next.
  6. On the Operations page, configure the following properties:

    1. From the Select Operation list, select Write File.
    2. In the Output Directory field, enter

      /upload/public_ftp/

    3. In the File Name Pattern field, enter

      PayablesExtract.xml

  7. Click Next.
  8. On the Schema page, from the Specify the structure for the contents of the file options, select No.

    For the purpose of this lab we will write the complete extract.

  9. Click Next.

    A summary of the properties you configured appears.

  10. Review the summary and click Done.
  11. Click Save to save the integration.

Define the Data Mapping

A Map action named Map to WriteExtract is automatically created. We'll define this data mapping.

  1. Select the Map to WriteExtract action.
  2. Click Edit icon.

    The Data Mapping page appears.

  3. In the Source section, expand $DownloadFile, then expand the getDocumentsForFilePrefixResponse, and then expand result.
  4. In the Target section, expand ICSFile.
  5. Map the Content element in the Source section to the FileReference element in the Target section.
  6. Click Validate.
  7. Click Close.
  8. Click Save to save the integration.

Define the Tracking Fields

  1. In the Integration canvas, you should see an error icon Error icon next to the Last Saved field.

    The icon shows the number of errors you need to fix in your integration. You should have one error. To fix this error you need to add business tracking identifiers.

  2. On the Integration canvas, click Actions icon, and then select Tracking.

    Tracking selection

  3. In the Business Identifiers for Tracking dialog, from the Source section, select requestId, and then click Edit icon.

    The selected field appears in the Tracking Fields table. The requestId field is marked as Primary.

  4. Click Save.

    Notice there are no errors.

  5. On the Integration canvas, click Save, and then click Close.

Activate the ERP Bulk Extract Callback Integration

  1. On the Integrations page, locate your integration and hover over it.

    The name of your integration is ERP Bulk Extract Callback .

    When you hover over the integration, a set of actions appear in the Status column.

  2. Click Activate icon.
  3. Select Enable Tracing, and then select Include Payload.

    Typically these options are disabled in production environments, but we'll enable them for the purpose of this lab.

  4. Click Activate.

    The activation will complete in a few seconds. If the activation succeeds, a confirmation message appears at the top of the page, and the status will change to Active.

  5. On the Integrations page, locate your integration and hover over it.

    The name of your integration is ERP Bulk Extract Callback .

    When you hover over the integration, a set of actions appear in the Status column.

  6. Click How to run icon.
  7. Copy the link in the WSDL URL without the ?wsdl at the end.

Map the Callback URL

  1. On the Integrations page, locate your ERP Bulk Extract integration and open it.

    The name of your integration is ERP Bulk Extract .

  2. Select the Map to InitiateExtract action.
  3. Click Edit icon.

    The Data Mapping page appears.

  4. In the Target section, right-mouse click on the callbackURL node and select Create Target Node.
  5. Click Edit icon in the Expression editor to enable edit mode.

  6. In the Expression window, paste the WSDL, enclosed in quotes, that you copied from the activated callback integration.
  7. Click Save icon in the Expression editor to commit the expression.

    Your mapping should look similiar to this.


    Mapping

  8. Click Validate.
  9. Click Close.
  10. Click Save to save the integration.

Activate the ERP Bulk Extract Integration

  1. On the Integrations page, locate your integration and hover over it.

    The name of your integration is ERP Bulk Extract .

    When you hover over the integration, a set of actions appear in the Status column.

  2. Click Activate icon.
  3. Select Enable Tracing, and then select Include Payload.

    Typically these options are disabled in production environments, but we'll enable them for the purpose of this lab.

  4. Click Activate.

    The activation will complete in a few seconds. If the activation succeeds, a confirmation message appears at the top of the page, and the status will change to Active.


Run the ERP Bulk Extract Integration

  1. On the Integrations page, locate your integration and hover over it.

    The name of your integration is ERP Bulk Extract .

    When you hover over the integration, a set of actions appear in the Status column.

  2. Click How to run icon.
  3. Click Submit Now, and then Submit Now again.

    A confirmation message with a link to track instance appears.

  4. Click Integrations in the top level navigation pane to return to Home.


    Home

  5. From Home, click Monitoring, then Integrations, then Tracking.
  6. Find your the integration instance with your integration name and click on the startTime link top open the integration instance flow.

    Confirm the flow was successfully completed.

  7. Click Menu and select View Activity Stream.


    Activity Stram

  8. Click on the last Message link in the Activity Stream labeled received from InitiateExtract and copy the Process Id returned in the result data element.


    Message


Verify

  1. Log in to the ERP Cloud:

    1. ERP Cloud URL:
    2. ERP Cloud User Name:

    3. ERP Cloud Password: Your password will be provided by the instructor.
  2. Select the Tools tab.
  3. Click Scheduled Processes.
  4. Expand Search and search for the Process Id returned from your integration.


    Process Search

  5. Click the process to open and verify that the Payables transaction job completed successfully.


    Process

  6. Using an FTP Client of your choice, log in to the FTP server.

  7. Open the following FTP directory and verify the PayablesExtract.xml file exists.

    /upload/public_ftp/

  8. Download the PayablesExtract.xml file and review.

Congratulations!

Congratulations! You have finished your integration flow.