Oracle Financials Cloud V1 Connector

Oracle Financials Cloud V1 Connector

Source Transformation mapping example

Source Transformation
mapping
example

You can map an Oracle Financials Cloud V1 source to a target and use the mapping to perform a
mapping
task.
To read and download the data from the Oracle Financials Cloud application, perform the following tasks:
  1. In
    Data Integration
    , click
    New
    Mapping
    Create
    .
    The
    New Mapping
    dialog box appears.
  2. Enter a name and description for the mapping.
  3. On the
    Source
    tab, perform the following steps:
    1. In the general properties, specify a name and description.
      The following image shows a sample of the Oracle Financials Cloud V1 mapping:
    2. In the
      Connection
      field, select the configured Oracle Financials Cloud V1 connection to connect to the Oracle Financials Cloud application.
      1. In the
        Operation
        field, select the required object in the
        Package Explorer
        section and select the required operation.
        The following image shows the list of the read operations:
        If you select the Custom Extract operation, you can provide your own custom arguments.
    3. In the
      Request Options
      section, click
      Configure
      to configure the request message.
      Specify the request message and attributes in the XML format. Request messages are different for each of the objects. When you read data from the Oracle Financials Cloud application, you can extract the data using the following extract modes:
      - FULL_EXTRACT
      - INCREMENTAL_EXTRACT
      - INCR_DATE_UPDATE
      - REGISTER_CUSTOM_EXTRACT
      - RERUN_MODE
      If you do not provide any argument value in the request message, the Secure Agent sets the P_EXTRACT_MODE extract mode to FULL_EXTRACT extract mode and sets the P_EXTRACT_NAME extract mode to the object name that you have selected.
      The following example shows a sample request message for the
      Receivable Adjustment Extract
      object:
      <!--1 or more repetitions:--> <proc:REQUEST_MESSAGE_INPUT xmlns:proc="http://xml.schemas/infa/procedure/"> <!--1 or more repetitions:--> <P_ORG_ID> 300000046987012 </P_ORG_ID> <!--1 or more repetitions:--> <P_ORDER_BY> ADJUSTMENT_NUMBER </P_ORDER_BY> <!--1 or more repetitions:--> <P_ADJ_NUMBER_LOW> <!--STRING--> </P_ADJ_NUMBER_LOW> <!--1 or more repetitions:--> <P_ADJ_NUMBER_HIGH> <!--STRING--> </P_ADJ_NUMBER_HIGH> <!--1 or more repetitions:--> <P_TRX_NUMBER_LOW> <!--STRING--> </P_TRX_NUMBER_LOW> <!--1 or more repetitions:--> <P_TRX_NUMBER_HIGH> <!--STRING--> </P_TRX_NUMBER_HIGH> <!--1 or more repetitions:--> <P_TAX_REGISTRATION_NUMBER> <!--STRING--> </P_TAX_REGISTRATION_NUMBER> <!--1 or more repetitions:--> <P_EXTRACT_MODE> FULL_EXTRACT </P_EXTRACT_MODE> <!--1 or more repetitions:--> <P_INCR_EXPORT_DATE> <!--DATE--> </P_INCR_EXPORT_DATE> <P_EXTRACT_DATE_FROM> <!--DATE--> </P_EXTRACT_DATE_FROM> <!--1 or more repetitions:--> <P_EXTRACT_DATE_TO> <!--DATE--> </P_EXTRACT_DATE_TO> <!--1 or more repetitions:--> <P_EXTRACT_NAME> ReceivablesAdjustmentsExtract </P_EXTRACT_NAME> <!--1 or more repetitions:--> <P_PARENT_EXTRACT_NAME> <!--STRING--> </P_PARENT_EXTRACT_NAME> </proc:REQUEST_MESSAGE_INPUT>
      For the arguments that you did not provide values in the request message, the Secure Agent considers the values of the argument as null. By default, the Secure Agent considers the value of the second last argument as the operation name. However, if you provide the value of the second last argument in the request message then the Secure Agent considers the value that you provide.
      If you encounter an error message when you validate the request message, you can ignore the error message and proceed. There is no impact in the output. However, if you want to remove the error message for the date type argument in the request message, you must provide the following XML code inside the date tag in the request message:
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xsi:nil="true"
      The following example shows a sample request message for the
      Custom Extract
      object:
      <proc:REQUEST_MESSAGE_INPUT xmlns:proc="http://xml.schemas/infa/procedure/"> <!--1 or more repetitions:--> <jobDefinitionName> <!-STRING-> </jobDefinitionName> <!--1 or more repetitions:--> <jobPackageName> <!-STRING-> </jobPackageName> <!--1 or more repetitions:--> <paramList> <!-STRING-> </paramList> </proc:REQUEST_MESSAGE_INPUT>
      When you configure the Custom Extract object, you must include the
      jobDefinitionName
      ,
      jobPackageName
      , and
      paramList
      parameter. When you define the
      paramList
      parameter, include comma separated values and if there are no parameters defined, include
      #NULL
      . To access the Custom Extract object, create custom user defined ESS job in the Oracle Financials Cloud Application.
      The following image shows the parameters defined in the Job Definition page:
  4. On the
    Field Mapping
    tab, select the elements in the response structure that you want to map to the output fields.
    Select the check box and expand the option. Select
    Map All Decendants
    Output Group
    to choose the source from where you want to read.
    The following image shows the response structure on the left pane in a hierarchical format and the output groups on the right pane in a relational format:
  5. On the
    Target transformations, specify the target connection, target type, object, and operation for the target transformations.
  6. Map the source and target.
  7. Click
    Save and Run
    the mapping.
  8. In
    Data Integration
    , click
    New
    Task
    .
  9. Click
    Mapping Task
    Create
    and select the mapping for the task.
    The following image shows the
    Mapping
    Task wizard with the applied mapping:

0 COMMENTS

We’d like to hear from you!