Data Applications → Incorta Data Delivery of Oracle EBS for Data Destinations

About Incorta Data Delivery of Oracle EBS

Incorta Data Delivery streamlines the integration between Oracle E-Business Suite (EBS) and Data Destinations. Incorta Data Delivery accelerates data mart deployment, and automates data model design and source schema mapping with the Incorta Oracle EBS data application. The Incorta Oracle EBS data application provides a new, faster, more effective option for analyzing and understanding your data, with no data modeling or extract, transform, load (ETL) required.

Following is the high-level Incorta Data Delivery process:

  • Connect Incorta to your data source with a data application, and load pre-existing physical schema fact and dimension tables.
  • The physical schema tables are materialized into parquet.
  • Load the Data Destination using the previously materialized parquet.

Configure Incorta Data Delivery

To configure Incorta Data Delivery, the following steps are required:

Install and Configure the Oracle EBS Data Application

Incorta Data Delivery is pre-configured with sample Oracle EBS data, which will allow you to preview the Oracle EBS integration with your Data Destionation before you connect to and configure the data application for your Oracle EBS instance. If you would like to use your own Oracle EBS data, follow the steps in the Configure the Oracle EBS data application section of Data applications → Install and Configure Oracle EBS for Incorta Cloud.

External Data Sources

Here are the predefined External Data Sources:

External Data SourceTypeDescription
EBSoracleThis external data source connects to your Oracle EBS database. Refer to Configure the Oracle EBS data application for details on how to update the properties for your instance.
IncortamysqlThis external data source is for the Incorta metadata.
PostgrespostgresThis external data source is for Incorta over Incorta.
SparkSqlpostgresThis external data source is for materialized views.
Important

Do not delete the External Data Sources, as they are required.

Data Files

Here are the pre-defined Local Data Files used in the COMMON physical schemas:

  • Date_US.csv
  • Month_US.csv
  • Period.csv
  • Quarter.csv
Important

Do not delete the Local Data Files, as they are required.

Global Variables

Here are the pre-defined global variables:

Global VariableDescription
flex_value_set_idThis global variable is used in the Account_Hierarchy and CostCenter_Hierarchy tables in the EBS_FIN_COMMON physical schema. Refer to Configure the Oracle EBS data application for details on how to update the value of this global variable for your Oracle EBS instance.
Default_InitialExtractDateOptionally use this global variable to limit rows for large transaction tables during a full load. For example: last_update_date > $$Default_InitialExtractDate
Refer to Configure the Oracle EBS data application for more details.

Security Groups

Here are the pre-defined security groups:

Security GroupDescription
Super UserThis is the Administrator. You can change this password using the Profile Manager.

Create a Data Destination

To create a data destionation, please refer to this page for the most up-to-date list of destinations and their configuration instructions.

For more information on how to manage Data Destinations, refer to Tools → Data Manager.

Set a Data Destination for the Fact and Dimension physical schemas

Configure and set a Data Destination for each Fact and Dimension table listed for the applicable module(s).

Business ProcessModuleFact and Dimension Physical Schemas
Procure To PayAccount Payables (AP)
Procurement (PO)
EBS_COMMON_DIM_ALL
EBS_AP_FACTS_ALL
EBS_PO_FACTS_ALL
Order to CashAccount Receivables (AR)
Order Management (OM)
EBS_COMMON_DIM_ALL
EBS_AR_FACTS_ALL
EBS_OM_FACTS_ALL
General LedgerGeneral Ledger (GL)EBS_COMMON_DIM_ALL
EBS_GL_FACTS_ALL
Projects (PPM)Projects (PPM)EBS_COMMON_DIM_ALL
EBS_PRJ_FACTS_ALL
HCM CoreHCM CoreEBS_COMMON_DIM_ALL
EBS_HCM_FACTS_ALL
Fixed AssetsFixed AssetsEBS_COMMON_DIM_ALL
EBS_FA_FACTS_ALL

Load the physical schemas

Prerequisite

Before loading the Oracle EBS Fact and Dimension schemas, load the Oracle EBS base schemas as outlined in Data applications → Install and Configure Oracle EBS → Perform a Full Load of the Physical Schemas.

Here are the steps to perform a full load for each physical schema:

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select the base schema to open it.
  • In the Schema Designer, in the Action bar, select LoadFull Load.

Load the Base physical schemas

Business ProcessModule
Procure To PayAccount Payables (AP)
Procurement (PO)
Order ManagementAccount Receivables (AR)
Order Management (OM)
General LedgerGeneral Ledger (GL)
Projects (PPM)Projects (PPM)
HCM CoreHCM Core
Fixed AssetsFixed Assets

Load the Fact and Dimension physical schemas

Perform a load of the Fact and Dimension physical schemas for each Oracle Cloud ERP module:

Business ProcessModule
Procure To PayAccount Payables (AP)
Procurement (PO)
Order to CashAccount Receivables (AR)
Order Management (OM)
General LedgerGeneral Ledger (GL)
Projects (PPM)Projects (PPM)
HCM CoreHCM Core
Fixed AssetsFixed Assets

Additional Information

Here are the star schema models for each Oracle Cloud ERP Module.

Procure to Pay

Order to Cash

General Ledger

HCM Core

Projects (PPM) - Billing and Revenue

Projects (PPM) - Costing and Budgeting