Data Applications → Install and configure Oracle Cloud ERP

Configuration Prerequisites

Before you configure the Oracle Cloud ERP data application, your Oracle Cloud ERP administrator will need to create a single user with the correct roles to access the Oracle Cloud ERP Business Intelligence Cloud Connector (BICC) and Universal Content Management (UCM). Select the following links for instructions:

• Create BICC user and assign roles
• Create UCM user and assign roles

Installation and configuration steps

Here are the installation steps:

1. Install the data application
2. Configure the Oracle BICC and UCM
3. Schedule the offering extracts
4. Verify the extract in the UCM
5. Apply Required Customizations to the Oracle Cloud ERP Data Application
6. Apply Optional Customizations to the Oracle Cloud ERP Data Applications
7. Add New Fields to Existing Tables in Incorta
8. Add New VOs to Incorta

Refer to frequently asked questions and troubleshooting document if needed.

Step 1: Install the data application

If you have access to install or request the data application in Incorta Analytics:

1. Sign in to Incorta Analytics.
2. Select Marketplace in the navigation bar.
3. Search for and select Oracle Cloud ERP Financials and Supply Chain or Oracle Cloud Human Capital Management.
4. Select Contact to Install.

To install in the CAP (Administrators only):

1. Sign in to the CAP.
2. Select Data Apps in the navigation bar.
3. Search for and select Oracle Cloud ERP Financials and Supply Chain or Oracle Cloud Human Capital Management.
4. Select Install.

Step 2: Configure the Oracle BICC and UCM

1. Sign in to the Oracle BICC with the following URL and your host name: https://<YOUR_HOST_NAME>.oracledemos.com/biacm/.
2. In the toolbar, select Manage Offerings and Data Stores → Import Modifications.
3. In the Import Modifications dialog box that pops up:
   1. Select Choose File.
   2. Select the exportCustomization_<DATE>_<VERSION>.zip file from OracleFusion_<VERSION_NUMBER>.zip.
   3. Select Open.
   4. Select Import.
4. Select the Offering drop down list to view the Incorta offerings, such as Incorta AP.

Step 3: Schedule the offering extracts

For each Oracle Module you want to use, you need to schedule an extract for the corresponding offering. Refer to the Offerings Matrix below for details. For example, to use Advanced Payables (AP), schedule extracts for Incorta AP, Incorta PO, Incorta Common, and Incorta Finance Common.

1. Select the Manage Extract Schedules option from the toolbar to run the Incorta offerings extracts of interest.
2. In Schedules, select + to add a schedule.
3. In Schedule Details,
   1. For Job Type, select Application Data Extract.
   2. Enter a Name for the schedule.
   3. Select Next.
4. In Data Store List,
   1. From the Offering drop down list, select an Incorta offering.
   2. Select the Enabled for Extract checkbox in the view header to select all of the objects.
   3. Select Next.
5. In External Storage,
   1. For External Storage, select UCM.
   2. For Notification, select None.
   3. Select Save.

Step 4: Verify the extract in the UCM

• When the extract is complete, sign in to the UCM with the following URL:

Copy
https://<YOUR_HOST_NAME>/cs/idcplg?IdcService=GET_DOC_PAGE&Action=GetTemplatePage&Page=HOME_PAGE

• Select Search → Advanced.
• Under Search, select Expanded Form.
  • Under Security Group, enter OBIA%.
  • Select Search to see the list of .zip extract files.

Offerings Matrix

Step 5: Apply Required Customizations to the Oracle Cloud ERP Data Application

To connect the data application to your Oracle Cloud ERP instance, the following steps are required:

• Setup the Incorta Cloud Applications UCM connection
• Perform a full load of the physical schemas
• Configure the seeded session variables
• Configure the General Ledger (GL) Account Key Flexfields (KFFs)

You can apply optional Oracle Cloud ERP customizations to the data application. These steps are covered in detail below.

Setup the Incorta Cloud Applications UCM connection

• Sign in to the Incorta Cloud Admin Portal (CAP).
• In the Navigation bar, select Clusters.
• Select the Cluster you installed the Oracle Cloud ERP data application on.
• Select Incorta Analytics.
• In the Navigation bar, select Data.
• In the Data Manager, in the Context bar, select the External Data Source tab.
• In the List View of external data sources, for the Fusion data source, select Edit (pen icon).
• In the New Data Source dialog,
  • Enter your Oracle Cloud Applications Username.
  • Enter your Oracle Cloud Applications Password.
  • Enter your Oracle Cloud Applications URL for UCM storage: https://<YOUR\_HOST\_NAME>/idcws/GenericSoapPort
  • For Root Query Text, the default is dSecurityGroup <matches> OBIAImport. You can add the following to further filter the data as required: <AND> dDocTitle <matches> file_crmanalyticsam%
  • For Data Type Discovery Policy, leave the default value of Use Both Sample data and Metadata Definition Files selected.
  • For Metadata directory, leave the default value of /datafiles.
  • For File Name Pattern, leave the default value of file_<catalog>_<schema>_<table>-batch*.zip.
  • For File Criteria - Last Modified Timestamp, you can enter a timestamp to load only files created or modified after that date. Here is the default value: >= '2021-01-01 00:00'
  • Select Ok.

Perform a Full Load of the Physical Schemas

Perform a full load of the data for each physical schema that corresponds to the Oracle Module of interest. Refer to the Offerings Matrix for details. For example, if you are interested in Advanced Payables (AP), you will need to perform a full load of Fusion_CAL_COMMON, Fusion_ITEM_COMMON, Fusion_HR_COMMON , Fusion_FND_COMMON, Fusion_FIN_COMMON, Fusion_PARTY_COMMON, Fusion_AP, and Fusion_PO in the order listed. Here are the steps to perform a full load.

• In the Navigation bar, select Schema.
• In the Schema Manager, select the Schemas tab.
• In the Schema Designer, open each required physical schema. In the Action bar, select Load → Full Load.

Configure the Seeded Session Variables

Configure the following seeded session variables that are used to set default values for dashboard prompts:

Here are the steps to configure the variables:

• In the Navigation bar, select Schema.
• In the Schema Manager, select the Session Variables tab.
• Select Edit (pen icon) for the session variable you would like to configure.
• In the Internal Variable dialog,
  • Select Query to open the Formula Builder.
  • Update the query as necessary.
  • Select Done.
• Select Save.

Configure the General Ledger Account Key Flexfields

By default, the Oracle Cloud ERP data applications use three segments in the chart of accounts. If you use only three segments, follow the minimal configuration steps in this section. If you have additional segments, follow the steps under optional configurations to add additional segments.

Determine the Chart of Accounts to Use for Reporting

You can query Fusion_FIN_COMMON.Ledger.LEDGERCHARTOFACCOUNTSID by creating an insight to determine which chart of account to use.

Get the List of Segments by Chart of Accounts ID

• Sign in to Oracle Cloud Applications.
• Select My Enterprise → Setup and Maintenance.
• In Functional Areas, select Financial Reporting Structures.
• In Task, select Manage Chart of Accounts Structure Instances.
• In Manage Chart of Accounts Structure Instances,
  • In Key Flexfield Code, enter GL.
  • Select Search.
  • For the General Ledger Accounting Flexfield, select Actions → Manage Structure Instances.
  • In Manage Key Flexfield Structure Instances, select Operations Accounting Flex for Structure Name.
  • Select Search.
  • For Operations Accounting Flex, select Actions → Edit.
  • In Edit Key Flexfield Structure Instance: Operations_Accounting_Flex, you can view the mapping of account segments.

Update the Business View Labels for the Segments

Here are the steps to update the segments in the CodeCombination business view of the FusionGeneralLedger business schema:

• In the Navigation bar, select Business Schema.
• In the Business Schema Manager, in the list view of business schemas, select the FusionGeneralLedger business schema to open it.
• In the Business Schema Designer, select the CodeCombination business view to expand it.
• Verify the segment labels correspond to your requirements. Update the labels as necessary:
  • Select More Options (vertical ellipsis icon) → Edit.
  • Enter the new values in Label for SEGMENT1, SEGMENT2, or SEGMENT3. For example, the Label for SEGMENT1 may be Company, the Label for SEGMENT2 may be Department, and the Label for SEGMENT3 may be Account, depending on your implementation.
• In the Action bar, select Done.

Update the Join for the GL Account Segment

• Open the Fusion_XLA.XLA Accounts table, which contains the accounts for each module used in the GL reconciliation dashboards, such as Accounts Payable.
  • Select the correct segment field for the Account.
  • Select Done.
• Perform a full load of the Fusion_XLA.XLA Accounts table.
• Update the join to the Fusion_FIN_Common.CodeCombination table for the GL Account Segment in your implementation. For example, if segment 3 is the Account segment, update the join between Fusion_XLA.XLA_Accounts.ACCOUNT and Fusion_FIN_COMMON.CodeCombination to CODECOMBINATIONSEGMENT3.

• Perform a full load of Fusion_FIN_COMMON.CodeCombination.

Update the Chart of Accounts in the Materialized View

Here are the questions you need to answer to determine the parameters used in the Incorta Fusion_FIN_COMMON.GLAccountHierFlat materialized view:

• What is the name of the account tree that you want to use?
• What is the name of the account tree version that you want to use?
• What is the Oracle Foundation (FND) value set category name for the GL account hierarchy nodes?

You will use the answers above to update the materialized view. Refer to Set up the General Ledger Key Flexfields for Oracle Cloud ERP to navigate your environment for values specific to your implementation.

To update the chart of accounts materialized view, Fusion_FIN_COMMON.GLAccountHierFlat:

• Change the specific values of the following for your implementation:
  • treeversionname
  • segment
  • valuecategory
• Perform a full load.

For example, with segment 3 as the Account segment, make the following updates as indicated below:

Copy
SELECT
   gsh.dep31pk1value || ' - ' || lvl1.DESCRIPTION AS account_level1,
   gsh.dep30pk1value || ' - ' || lvl2.DESCRIPTION AS account_level2,
   gsh.dep29pk1value || ' - ' || lvl3.DESCRIPTION AS account_level3,
   gsh.dep28pk1value || ' - ' || lvl4.DESCRIPTION AS account_level4,
   gsh.dep27pk1value || ' - ' || lvl5.DESCRIPTION AS account_level5,
   gsh.dep26pk1value || ' - ' || lvl6.DESCRIPTION AS account_level6,
   gsh.dep25pk1value || ' - ' || lvl7.DESCRIPTION AS account_level7,
   gsh.dep24pk1value || ' - ' || lvl8.DESCRIPTION AS account_level8,
   gsh.dep0pk1value || ' - ' || lvl9.DESCRIPTION AS account_level9,
   gcc.CODECOMBINATIONSEGMENT1,
   gcc.CODECOMBINATIONSEGMENT2,
   gcc.CODECOMBINATIONSEGMENT3,
   gcc.CODECOMBINATIONSEGMENT4,
   gcc.CODECOMBINATIONSEGMENT5,
   gcc.CODECOMBINATIONSEGMENT6,
   gcc.codecombinationid,
   lvl2.FLEXVALUE lvl2_flexvalue,
   lvl3.FLEXVALUE lvl3_flexvalue,
   lvl4.FLEXVALUE lvl4_flexvalue
FROM
   Fusion_FIN_COMMON.flex_tree_vs_gl_account_vi gsh,
   (
       SELECT
           gcf.treestructurecode,
           gcf.treecode,
           gcf.treeversionid,
           gcf.dep0pk1value,
           MAX(gcf.distance) AS maxdistance
       FROM
           Fusion_FIN_COMMON.flex_tree_vs_gl_account_vi gcf,
           Fusion_FIN_COMMON.fndtreeversiontlp1 tvt
       WHERE
           gcf.treestructurecode = tvt.treestructurecode
           AND gcf.treecode = tvt.treecode
           AND gcf.treeversionid = tvt.treeversionid
           AND tvt.treeversionname = 'Account_Tree_Current1' /* <--- Update */
       GROUP BY
           gcf.treestructurecode,
           gcf.treecode,
           gcf.treeversionid,
           gcf.dep0pk1value
   ) hier,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl1,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl2,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl3,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl4,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl5,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl6,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl7,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl8,
   Fusion_FIN_COMMON.fndflexvaluespvo lvl9,
   Fusion_FIN_COMMON.CodeCombination gcc
WHERE
   gsh.dep0pk1value = hier.dep0pk1value
   AND gsh.distance = hier.maxdistance
   AND gsh.treestructurecode = hier.treestructurecode
   AND gsh.treecode = hier.treecode
   AND gsh.treeversionid = hier.treeversionid
   AND gsh.dep31pk1value = lvl1.FLEXVALUE
   AND gsh.dep30pk1value = lvl2.FLEXVALUE
   AND gsh.dep29pk1value = lvl3.FLEXVALUE
   AND gsh.dep28pk1value = lvl4.FLEXVALUE
   AND gsh.dep27pk1value = lvl5.FLEXVALUE
   AND gsh.dep26pk1value = lvl6.FLEXVALUE
   AND gsh.dep25pk1value = lvl7.FLEXVALUE
   AND gsh.dep24pk1value = lvl8.FLEXVALUE
   AND gsh.dep0pk1value = lvl9.FLEXVALUE
   AND gsh.dep0pk1value = gcc.CODECOMBINATIONSEGMENT3        /* <--- Update */
   AND lvl1.valuecategory = 'Account'                        /* <--- Update */
   AND lvl2.valuecategory = 'Account'                        /* <--- Update */
   AND lvl3.valuecategory = 'Account'                        /* <--- Update */
   AND lvl4.valuecategory = 'Account'                        /* <--- Update */
   AND lvl5.valuecategory = 'Account'                        /* <--- Update */
   AND lvl6.valuecategory = 'Account'                        /* <--- Update */
   AND lvl7.valuecategory = 'Account'                        /* <--- Update */
   AND lvl8.valuecategory = 'Account'                        /* <--- Update */
   AND lvl9.valuecategory = 'Account'                        /* <--- Update */

Update the Incorta Analyzer Table with the GL Account Segment

The Oracle Cloud ERP data application uses Segment 2 for the GL Account Segment. If you use a different segment column, update the Fusion_XLA.XLA_Accounts Incorta Analyzer table with the correct segment number.

• In the Schema Manager, open the XLA_Accounts table.
• In the Schema Designer, select the Incorta icon.
• In the Data Source dialog, select Edit (pencil icon).
• For ACCOUNT, select the right arrow (>) to open the pill properties.
• In Formula, update the segment number. For example, with segment 3 as the Account segment, change Fusion_FIN_COMMON.CodeCombination.CODECOMBINATIONSEGMENT2 to Fusion_FIN_COMMON.CodeCombination.CODECOMBINATIONSEGMENT3.

Step 6: Apply Optional Customizations to the Oracle Cloud ERP Data Applications

Following are common Oracle Cloud ERP customizations that you can optionally apply to the data application:

• Configure Descriptive Flexfields (DFFs)
• Configure additional segments for the General Ledger (GL) account Key Flexfields (KFFs)
• Drill to Oracle Cloud ERP from an Incorta insight

Configure Descriptive Flexfields

A flexfield is a set of placeholder fields, or segments that are associated with a business object. Oracle Cloud ERP provides three types of flexfields: descriptive, extensible, and key. Here are the steps to support a DFF for a table in Incorta:

• Determine the flex VO. In Oracle Cloud ERP, there is a separate VO object for a table’s flexfields. For example, for ContractHeaderP, the flex VO is FscmTopModelAM.ContractsCoreAM.HdrDFBIAM.FLEX_BI_ContractHeaderFlexfield_V.
• Import the flex VO into Incorta. Refer to Add New VOs to Incorta for the detailed steps.
• Join the flex VO as a parent table to the base VO. Use the key columns of the base VO to join to the flex VO key columns, which will have a column name similar to S_K_5000.
• Add the DESC_ field from the flex VO to a business schema with the appropriate label. For example, in contractHeader the end user DFF column name is ProjectMarket. Therefore, the flexfield value field in the VO would be DESC_PROJECTMARKET_, and the label would be Project Market.
• Load the VO.

Here are the DFF VOs included in the Fusion_FLX_COMMON schema:

Since flex VOs are deployment-specific, you need to perform the following steps to get the updated fields:

• Export the existing flex VO in the BICC.
• Download the metadata CSV (MDCSV) file from the BICC.
• Import the MDCSV file to Incorta.
• Save the flex VO.

If no fields are selected in the flex VO, edit the VO in the BICC:

• Select all fields.
• Select Save.

If you do not see some flex VOs in the BICC, deploy the DFFs from the Fusion Application with the following steps:

• Navigate to the Manage Descriptive FlexFields window.
• Query the DFF CODE.
• Select Edit (pen icon).
• If the BI Enabled check box is cleared, select it.
• Select Save.
• Deploy the flex code.
• Run the Import Oracle Fusion Data Extensions for Transactional Business Intelligence job.

Configure Additional Segments for the General Ledger Account Key Flexfields

The required customizations section above outlined the steps to configure the GL account to reflect your implementation of the GL# KFFs when you use only three segments in your Oracle Cloud ERP instance. This section outlines the steps to configure the GL account to reflect your implementation of the GL# KFFs when you use more than three segments.

Add new business views for additional qualifying segments. For example, create a new business view called product and add all the columns for that segment.

If the segment has no hierarchy, add the <segment name>_c and DESC_<segment_name> columns into the business view. If the segment has a hierarchy, the hierarchy is already flattened in the VO. Add all the columns for each level in the hierarchy to the business view.

Drill to Oracle Cloud ERP from an Incorta Insight

You can drill to Oracle Cloud ERP from an Incorta insight if a URL exists to pass the ID in. Here are some examples of URLs you can enter in the column URL field of an insight:

• Purchase Requisitions: https://<YOUR_HOST_NAME>/fscmUI/faces/FndOverview?fnd=%2FWEB-INF%2Foracle%2Fapps%2Fprc%2Fpor%2FmanageReq%2Fui%2Fflow%2FManageReqMainAreaFlow.xml%23ManageReqMainAreaFlow;paramInvokedApp%3DNOTIFICATION%3BparamReqHeaderId%{EBS_PO.PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID};;;false;256;;;&fndGlobalItemNodeId=itemNode_my_information_purchase_requisitions
• AP Invoices: https://<YOUR_HOST_NAME>/fscmUI/faces/deeplink?objType=AP_VIEWINVOICE&action=VIEW&objKey=InvoiceId={FusionPayablesTransactions.InvoiceHeaders.INVOICE_ID}

Step 7: Add New Fields to Existing Tables in Incorta

Here are the steps to add new fields into existing tables in Incorta:

• In the BICC, open a Data Store for a particular Offering.
  • Select Select Columns.
  • Select the Include checkbox for the field you want to add.
  • Select Save.
• In the Data Stores for Offering list view, select the gear icon and then Reset to Full Extract.

• In the UCM, select Search.
• In Title, enter the data store name in lowercase.
• Select Search.
• Delete all files with a date before today.

• In the BICC, schedule and run an extract for the new field.

• In Incorta, open the schema that contains the table.

  • Open the table in the Table Editor.
  • Select the checkbox for the new column.
  • Select Done.

• Perform a full load of the table.

• Select Preview Data to validate the data in the new column.

Step 8: Add New VOs to Incorta

There may be situations in which you want to bring in additional data from Oracle Cloud ERP. The primary method to bring Oracle Cloud ERP data into Incorta is through VOs. The data from VOs can be extracted from the Oracle BICC console. There are a lot of VOs pre-seeded in the BICC console that are already assigned to specific offerings and enabled for extract. Not all VOs are pre-seeded. However, any VO that is in Oracle Cloud ERP can be extracted from BICC as a custom VO extract.

Here are the high level steps to add a new VO:

• Identify the VO that contains the data needed for reporting in Incorta
• Find or add the VO in the BICC
• Download the VO MDCSV from the BICC and upload it to Incorta
• Extract the VO data from the BICC into the UCM
• Create the table corresponding to the new VO in Incorta

Identify the VO that contains the data needed for reporting in Incorta

• In Oracle Transactional Business Intelligence (OTBI), either create or run a report for the subject area of interest with the following URL and your host name: https://<YOUR_HOST_NAME>/analytics
• Select Administration → Manage Sessions.

• From the Cursor Cache list, select View Log for the report. The log contains a list of VO objects, as well as details on how a VO joins to other VOs.

• Copy the name of the VO of interest from the log.

Find or Add the VO in the BICC

• In the Oracle BICC, search for the VO.

• If the VO is not found, you can add the VO:
  • Select Manage Offerings and Data Stores from the toolbar.
  • Select an Offering from the list.
  • Select +.
  • In Data Store Key, enter the name of the VO.

• In Associate Offerings, make sure the name of the offering you would like to add the VO to is in Selected Offerings.
• Select Save.
• Select Select Columns.
• Select the Include checkbox for the columns you would like to add to the VO. You can select all columns with Select → Select All.

Download the VO MDCSV from the BICC and upload it to Incorta

• In the BICC, download the VO MDCSV file:
  • Select the gear icon, and then Extract Metadata Definition (MDCSV).
  • Unzip the MDCSV file.
  • Change the file extension from .MDCSV to .csv.
• In Incorta, upload the file to the datafiles folder. For more information, refer to the Upload one or more data files and folders, including subfolders and files section of the Connectors → File System document.

Extract the VO Data from the BICC into the UCM

• In the BICC, select Manage Extract Schedules to extract the VO data into the UCM.

Create the table corresponding to the new VO in Incorta

• In Incorta, use the Schema Wizard to create a physical schema table for the VO definitions.
• Create the joins from child to parent.
• Create any formula columns needed.
• Perform a full load of the physical schema.
• Create or update a business schema.
• Create new dashboards from the business schema, and validate the data and joins.

Additional Configurations

Support for Source System Row Deletion

• Create a new Oracle Cloud Applications data source.
• Select .pecsv for File Extension.

• In the BICC, perform a Primary Key Extract. Select Manage Extract Schedules, and for Job Type, select Active Primary Key Extract.
• Create a new schema, or use an existing one, and add the PK tables using the Schema Wizard.
• Perform a full load of the PK table.
• Create a join from the base table to the PK table, with the PK table as the parent.
• Create a table security filter on the base table that specifies a field of the parent table is not null. Here is an example: not(isNull(PK_Schema.PKTable.id)).

The deleted rows from the base table will always be filtered from the dashboards. If required, you can also schedule a periodic full load, such as every week, to filter the deleted records from the base table.

Add non-Oracle Cloud ERP tables in Incorta

There are many Fusion modules like Oracle Trade Management or Oracle Configure Price Quote (CPQ) that do not integrate with BICC. Here are the steps to add data from these modules:

• Create a CSV report using a tool like BI publisher, zip it, and name it with the following format: file_<catalog>_<schema>_<table>-batch*.zip. For more information onn how to define a destination file name dynamically using a date expression, refer to Fusion Middleware User's Guide for Oracle Business Intelligence Publisher.
• Upload the file to the UCM or OCI Object Storage.
• In Incorta, use the Schema Wizard or directly create a table in a schema using the Fusion data source. The connector will import the object from the .zip file .
• Sign in to to the Oracle Webcenter console and select New Check-In.

• In the Content Check-In Form,
  • For Type, select a document type.
  • For Title, enter a name for the file.
  • For Author, select the owner from the list.
  • For Security Group, select a security group.
  • For Primary File, select the CSV report to upload.
  • For Revision, enter the revision number. By default, the value will be 1.
  • For Release Date, select the release date. By default it will be set to the current date.
  • Select Check In.

• Once the document is uploaded successfully, select Search and then select Advanced Search.
  • Enter the Security Group in the Content Check-In Form to filter the results.

• Select Search. The CSV file will appear in the search results.

Oracle Cloud Infrastructure Object Storage

You can access BICC content in OCI Object Storage. Here are the steps:

• Sign in to your Oracle cloud account with the following URL: https://www.oracle.com/cloud/sign-in.html
• Enter your username and password.
• Navigate to the Object Storage tab, which lists the existing buckets associated with your region.

• Select Profile.

• Select API Keys in Resources.

• In the Add API Key dialog,
  • Select Download Private Key.
  • Select Download Public Key. Download the public key to the same directory as the private key.
  • Select Add.

• In the Configuration File Preview dialog, select Copy.

Create the OCI Configuration File

• Open a terminal session to the directory where you downloaded the keys.
• Enter Code <CONFIG_FILE_NAME>, to open a text file.
• Paste the Configuration File Preview content.
• Add a path to the private key file. For example: key_file=/Users/mac/Desktop/oci_test/<KEY_FILE_NAME>.

Create an Oracle Cloud Applications OCI Data Source in Incorta

• In the Navigation bar, select Data.
• In the Action bar, select + New → Add Data Source.
• In the Choose a Data Source dialog, in Application, select Oracle Cloud Applications.
• In the New Data Source dialog,
  • For Storage Type, select OCI Object Storage.
  • For OCI Configuration FIle Path, enter the path to the configuration file for OCI Object Storage that contains information about the user, profile, tenancy ID and region.
  • For OCI Configuration Profile, enter the profile you wish to access your data from. The configuration file can contain multiple profiles, each of which has its own authentication credentials, so you should select a specific profile to use.
  • For Bucket, ener the name of the bucket that contains the target data files. A bucket is a logical container for storing objects, such as a folder in a file system.
  • For Data Type Discovery Policy, leave Use Both Sample data and Metadata Definition Files selected.
  • For File Name Pattern, leave the default value of file_<catalog>_<schema>_<table>-batch*.zip.
  • For Keep file(s) for, select how long you would like to keep the files.
  • Select Ok.

Refer to the Set up Oracle Fusion SaaS Business Intelligence Cloud Connector (BICC) to use Oracle Cloud Infrastructure (OCI) Object Storage article for more information.