Register the Fusion Applications Source

Register the Fusion Applications source.

This task is part of the Fusion Applications Cloud Source System Deployment Roadmap.

To Register the Fusion Applications Source:

  1. Log in to BI Applications Configuration Manager as a user that has Enterprise Role -ASM_APPLICATION_IMPLEMENTATION_ADMIN_ABSTRACT.
  2. In the Tasks pane under System Setups, select the Define Business Intelligence Applications Instance link to display the Source Systems tab.
    This screenshot is described in surrounding text.
  3. Click the Add icon (+) to display the Register Source dialog.
    This screenshot is described in surrounding text.
  4. In the Register Source in Configuration Manager page, specify this information:
    • In the Product Line drop-down list, select Oracle Fusion.

    • In the Product Line Version, select the Oracle Fusion version being used.

    • In the Source Instance Name field, specify a unique name to identify the source system.

    • In the Data Source Number field, specify 200.

  5. Click Next to display the Edit Source in Oracle Data Integrator Topology page.
  6. Choose the context as Global from the drop-down and specify an ODI data server, jdbc details and host details of BI server.

    Enter dummy values as these are not needed for Fusion Applications Cloud-based ETL.

  7. Display the File Technology tab and provide details for ETL Source Files.

    The default Source File Connection location is MW_HOME/Oracle_BI1/biapps/etl/data_files/src_files/FUSION_1_0.

    This screenshot is described in surrounding text.
  8. Add JDBC URL column from the View menu and change the JDBC URL value from jdbc:snps:dbfile?OPT=TRUE to jdbc:snps:dbfile?ENCODING=UTF-8&OPT=TRUE to File connection.
    This graphic is described in the surrounding text.
  9. Save the details.

Register the File System Location for Download

Next, register the file system location for download and staging the files from FA UCM server in ODI studio.

While registering Fusion Data Source in BIACM, an ODI data server is created for File technology (see example screen shot FS_FA_DS in Step 1 below). Create two new physical schemas in ODI Topology under the existing data server:

  1. In ODI Studio, create the physical schema for download, upload, and enter the folder location in the Definition tab.
    img/GUID-01D789B3-35BE-4490-BF51-32FC6BFB12E0-default.gif

    Map to DS_FUSION10_DOWNLOAD_FILES in Global Context in the Context tab (add using + icon on right).

    This graphic is described in the surrounding text.
  2. Create Physical schema for staging and map to logical schema DS_FUSION10_REPLSTG_FILES.

    Refer to the screen shot for download of physical schema.

  3. Open Global context and map the logical schema DS_FUSION10_UPLOAD_FILES to newly created physical schema for download.

    These folders will be used by ODI Agent to download files and should be accessible to the ODI_server1.

    This graphic is described in the surrounding text.
  4. Add jdbc:snps:dbfile?ENCODING=UTF-8&OPT=TRUE to all File connection'BIAPPS_DW_FILE in Physical architecture.
    This graphic is described in the surrounding text.
  5. Update logical schema for 'DS_FUSION10_CRMSRCFILES, 'DS_FUSION10_HCMSRCFILES', 'DS_FUSION10_DOWNLOAD_FILES','DS_FUSION10_REPLSTG_FILES' and 'DS_FUSION10_UPLOAD_FILES' to 200.

Set the IS_SDS_DEPLOYED Variable

Next, verify that the IS_SDS_DEPLOYED variable is set to true for FUSION.

  1. In the Tasks pane, select the Manage Data Load Parameters link to display the Manage Data Load Parameters dialog.
  2. Use the Search area to locate the IS_SDS_DEPLOYED parameter for the Fusion source:
    1. In the Source Instance drop down, select the Fusion source that you have created.
    2. In the Parameter Code field, specify IS_SDS_DEPLOYED.
    3. Click Search.

      The IS_SDS_DEPLOYED parameter is displayed in the Data Load Parameters list.

      In the Data Load Parameters list, view the parameter returned by the search, and verify that the value is Yes.

      This screenshot is described in surrounding text.
  3. If the value is not Yes, then click Edit, and in the Parameter Value drop-down list, select YES, and save the details.
    This screenshot is described in surrounding text.

Create a Load Plan and Specify Offerings and Fact Groups to Load

Next, you create the load plan.

  1. In the Tasks pane, click Manage Load Plans to display the Load Plans dialog.
  2. Click Add (+) to display the Define Load Plan dialog.
    This screenshot is described in surrounding text.
  3. Use the Name field to specify a unique name, and in the Source Instances drop-down list select the Fusion source, then click Next to display the Select Fact Groups page.
  4. Select applicable offerings and fact groups.
    This screenshot is described in surrounding text.
  5. Click Save.
  6. In the list of Load Plans, select the new load plan, and click Generate.