Blueprints → Install and Configure Oracle EBS for Incorta On-Premises

About the Oracle EBS Blueprint for Incorta On-Premises

The Incorta Oracle E-Business Suite (EBS) blueprint provides a new, faster, more effective option for analyzing and understanding your data, with no data modeling or extract, transform, load (ETL) required. You will get instant access to up-to-date, consolidated enterprise resource planning (ERP) data and can build all of the high-performance reports you need on your own.

With an extensive library of prebuilt content, Oracle EBS users gain immediate access to rich content areas and sample dashboards that are easily customizable and logically grouped by department and persona to help answer the most-pressing business questions quickly.

In addition, the Oracle EBS Blueprints expedite your organization’s migration from legacy reporting tools, and drastically speed your Oracle EBS-based reporting and analytics project’s time to value. They also let you more quickly add new data sources to your Oracle EBS analysis.

The following are the Oracle EBS modules for which blueprints are available in the on-premises version of the Incorta Direct Data Platform™:

Financial Modules

Supply Chain Planning Modules

Business Flows

  • Order to Cash
  • Procure to Pay

Other Modules

Note

The Supply Chain Planning Modules apply only to customers using Oracle Advanced Supply Chain Planning (ASCP) or Value Chain Planning (VCP).

Each blueprint module represents a 1:1 mapping of the corresponding tables and relationships in Oracle EBS. Also included is prebuilt metadata that can be used to load data for each module from the Oracle database and view it in prebuilt dashboards.

Note

The Incorta on-premises EBS blueprint supports Oracle EBS version R12.x.

Install the Oracle EBS Blueprint

The Oracle EBS Blueprint requires the following ZIP file:

  • FullInstallEBSVer<VERSION_NUMBER>.zip

The Oracle EBS blueprint requires the import of a tenant file to an Incorta Cluster. A CMC Administrator can perform the tenant import. A systems administrator with root access to the host can copy the tenant data files, configure Spark, and configure the necessary datasources.

Here are the steps to install the Oracle EBS Blueprint:

  • Contact Incorta Support to obtain the Oracle EBS Blueprint ZIP file. Download and unzip the file.
  • Within the unzipped Oracle EBS Blueprint file, locate the ebsVer<VERSION_NUMBER>.zip file.

Import the EBS Blueprint Tenant

  • Import the ebsVer<VERSION_NUMBER>.zip tenant:

    • Sign in to the CMC.
    • In the Navigation bar, select Clusters.
    • In the cluster list, select a Cluster name.
    • In the canvas tabs, select Tenants.
    • Select +Import Tenant.
    • Drag and drop the ebsVer_<VERSION_NUMBER>.zip to the Click or drag a file here to upload panel in the Import a tenant to the cluster dialog.
    • Select Next.
    • Verify or enter the tenant properties.
    • Verify or enter the tenant email properties.
    • Select Create.

Tenant Properties

Property Control Description
Name text box Enter the tenant name. Select Check to determine if a Tenant already exists with the name entered.
Username text box Enter the username for the Super User
Password text box Enter the password for the Super User
Email text box Enter the email address for the Super User
Path text box Enter the shared storage path for tenant related data
Pause scheduled jobs toggle Enable this property if the imported tenant will have all scheduled jobs paused on import

Tenant Email Properties

Property Control Description
Sender’s Username Auth toggle Enable this property if the email requires username authentication
System Email Username text box Enable Sender’s Username Auth to configure this property. Enter the username for the system email.
System Email Address text box Enter the email address for the system email
System Email Password text box Enter the password for the system email address
SMTP Host text box Enter the Simple Mail Transfer Protocol (SMTP) host for the system email
SMTP Port text box Enter the SMTP port number
Share Notifications toggle Enable this property to share notifications

Copy the EBS Blueprint Tenant Data Files

The EBS Blueprint package contains the following CSV data files that you must copy to the Tenant data folder:

  • contentTypeLookup.csv
  • Date_US.csv
  • Month_US.csv
  • Period.csv
  • Quarter.csv

Here are the steps to perform a secure copy of the CSV files using scp:

    INCORTA_NODE_HOST=100.101.102.103
    cd ~/Downloads/FullInstallEBSVer5/Data
    scp -i ~/.ssh/host_pemkey.pem  contentTypeLookup.csv Date_US.csv Month_US.csv Period.csv Quarter.csv incorta@${INCORTA_NODE_HOST}:/tmp/

Secure shell into the host.

    ssh -i ~/.ssh/host_pemkey.pem incorta@${INCORTA_NODE_HOST}

Copy the CSV data files to the /<INCORTA_INSTALLATION_PATH>/Tenants/<TENANT_NAME>/data directory in bash shell.

    sudo su incorta
    INCORTA_INSTALLATION_PATH=/home/incorta/IncortaAnalytics
    cp /tmp/contentTypeLookup.csv /tmp/Date_US.csv /tmp/Month_US.csv /tmp/Period.csv /tmp/Quarter.csv $INCORTA_INSTALLATION_PATH/Tenants/bp_oracle_ebs/data

Configure Spark for the EBS Blueprint

Allocate 10 GB or more to the Spark Worker process, and restart Spark:

  • Edit the <INCORTA__INSTALLATION_PATH>/IncortaNode/spark/conf/spark-env.sh file with vim.
    vim /home/incorta/IncortaAnalytics/IncortaNode/spark/conf/spark-env.sh
  • Set the SPARK_WORKER_MEMORY value to 10g (or greater)

    SPARK_WORKER_MEMORY = 10g
  • Restart Spark

    cd /home/incorta/IncortaAnalytics/IncortaNode
    ./stopSpark.sh
    ./startSpark.sh
  • Check the Spark configuration using the Spark Master UI: http://<HOST_NAME>:9091.

Configure the EBS Blueprint Datasources

  • Sign in to the Incorta Direct Data Platform™.
  • In the Navigation bar, select Data.
  • In the Context bar, select the External Data Source tab.

Edit the EBS Data Source

  • Select Edit (pen icon) to the right of the EBS datasource.
  • Enter the EBS connection properties for your instance:

    • Username
    • Password
    • Connection Pool: 10
    • Connection String: jdbc:oracle:thin:@<HOST>:<PORT>/<DATABASE>

Edit the VCP Data Source (for ASCP customers only)

  • Select Edit (pen icon) to the right of the VCP datasource.
  • Enter the VCP connection properties for your instance:

    • Username
    • Password
    • Connection Pool: 10
    • Connection String: jdbc:oracle:thin:@<HOST>:<PORT>/<DATABASE>

Edit the Incorta (Metadata) Data Source

  • Select Edit (pen icon) to the right of the Incorta datasource.
  • Enter the EBS connection properties for your instance:

    • Username
    • Password
    • Connection Pool: 10
    • Connection String: jdbc:mysql://<HOST>:<PORT>/<DATABASE>

Edit the SparkSQL Data Source

  • Select Edit (pen icon) to the right of the SparkSql datasource.
  • Enter the SparkSQL connection properties for your instance:

    • Username
    • Password
    • Connection Pool: 10
    • Connection String: jdbc:postgresql://<HOST>:5442/<TENANT_NAME>
    Note

    The port is the Data Store (DS) port defined in the CMC.

Configure the Oracle EBS Blueprint

To configure the Oracle EBS Blueprint, update the corresponding Session Variables and perform a full load of the EBS COMMON Schemas.

Update EBS Blueprint Session Variables

  • Sign in to the Incorta Direct Data Platform™.
  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Session Variables tab.
  • Edit the query for the following variables with information for your EBS instance, by selecting Edit (pen icon) to the right of each variable:

    • Default_Book_Type_code
    • Default_Fiscal_Year
    • Default_Ledger
    • Default_Period
    • Default_Period_2
    • Default_Start_Date

Perform a Full Load of the EBS COMMON Schemas

  • Sign in to the Incorta Direct Data Platform™.
  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • Select each of the schemas below. In the Action bar, select LoadLoad nowFull.

    • EBS_ITEM_COMMON
    • EBS_CAL_COMMON
    • EBS_FND_COMMON
    • EBS_HR_COMMON
    • EBS_FIN_COMMON
    • EBS_PARTY_COMMON

To configure a specific Oracle Cloud ERP module, refer to the list of Finance Modules, Supply Chain Planning Modules, Business Flows, or Other Modules and select the module for configuration details.

Important

Monitor your Incorta host disk space as you load the EBS schemas. For large tables, to limit full data loads, add a SQL clause WHERE CREATION_DATE > <DATE>.

Apply Optional Customizations to the Oracle EBS Blueprints

Following are common Oracle EBS customizations that you can optionally incorporate into the blueprint:

Configure the Initial Extract Date

Optionally configure the $$Default_InitialExtractDate global variable to store the initial extract date, or rolling period. This will limit rows for large transaction tables during full load.

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Global Variables tab.
  • In the list view of global variables, select the Default_InitialExtractDate global variable to open it.
  • Update the Value.
  • Select Ok.

Here are the steps to update the SQL query for the tables you would like to limit:

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select a schema to open it.
  • In the Schema Designer, in the Tables section, select a table to open it.
  • In the Table Editor, select the EBS SQL icon to open the Data Source dialog.
  • In the Data Source dialog,

    • In Query, add WHERE creation_date >= $$Default_InitialExtractDate as shown below.
    • Select Done.
  • Select Save.
  • In the Action bar, select Done.
Note

The $$Default_InitialExtractDate global variable should be used to limit transaction tables only. If you apply a limit to reference data, it may lead to missing foreign keys.

Configure Additional Segments for the General Ledger Account Key Flexfields

The required configurations 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 EBS 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.

Determine the Chart of Accounts to Use for Reporting

Run the SQL query below if the chart of accounts to use for reporting are not already known:

    SELECT
       NAME AS LEDGER_NAME,
       CHART_OF_ACCOUNTS_ID,
       MAX(GLB.LAST_UPDATE_DATE)
    FROM
       APPS.GL_LEDGERS GL,
       APPS.GL_BALANCES GLB
    WHERE
       GL.LEDGER_ID = GLB.LEDGER_ID
    GROUP BY
       NAME,
       CHART_OF_ACCOUNTS_ID
    ORDER BY
       3 DESC;

Get the List of Segments by Chart of Accounts ID

Run the following SQL against your Oracle EBS database to get the SEGMENT_NUMs and FLEX_VALUE_SET_IDs for the GL# KFF:

    SELECT
       FIFS.ID_FLEX_NUM AS CHART_OF_ACCOUNT_ID,
       FIFS.SEGMENT_NUM,
       FIFS.SEGMENT_NAME,
       FIFS.APPLICATION_COLUMN_NAME,
       FIFS.FLEX_VALUE_SET_ID,
       LISTAGG(FSAV.SEGMENT_ATTRIBUTE_TYPE, ',') WITHIN GROUP(
           ORDER BY
               FSAV.SEGMENT_ATTRIBUTE_TYPE
       ) AS QUALIFIERS
    FROM
       APPS.FND_ID_FLEX_SEGMENTS FIFS
       LEFT JOIN APPS.FND_SEGMENT_ATTRIBUTE_VALUES FSAV ON FIFS.ID_FLEX_CODE = FSAV.ID_FLEX_CODE
       AND FIFS.ID_FLEX_NUM = FSAV.ID_FLEX_NUM
       AND FIFS.APPLICATION_COLUMN_NAME = FSAV.APPLICATION_COLUMN_NAME
       AND FSAV.ATTRIBUTE_VALUE = 'Y'
    WHERE
       FIFS.ID_FLEX_CODE = 'GL#'
    GROUP BY
       FIFS.ID_FLEX_NUM,
       FIFS.SEGMENT_NUM,
       FIFS.SEGMENT_NAME,
       FIFS.APPLICATION_COLUMN_NAME,
       FIFS.FLEX_VALUE_SET_ID
    ORDER BY
       FIFS.ID_FLEX_NUM,
       FIFS.SEGMENT_NUM

An example will demonstrate the remaining steps involved. In this example, we will add an additional segment for CHART_OF_ACCOUNT_ID 50194, which has 4 segments:

SEGMENT1 → Company (qualifying segment)
SEGMENT2 → Department (qualifying segment)
SEGMENT3→ Account (qualifying segment)
SEGMENT4→ Intercompany (qualifying segment)

Configure the Segments to Use for Reporting

The Oracle EBS blueprint has three segment value tables in the EBS_FIN_COMMON schema: GL_ACCOUNT_SEG, GL_COSTCENTER_SEG, and GL_BALANCING_SEG. You can use these tables if they match the segments in your Oracle EBS instance. The fourth segment, Intercompany, will be added since it is needed for reporting.

Add a new table for the additional segment

Here are the steps to create a new table for the Intercompany segment:

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select the EBS_FIN_COMMON schema to open it.
  • In the Schema Designer, in the Action bar, select +NewTableSQL Database.
  • In the Data Source dialog, enter the following properties

    • For Data Source, select EBS.
    • Enable Incremental.
    • For Query, enter

      SELECT
         FIFS.ID_FLEX_NUM,
         B.ID_FLEX_STRUCTURE_NAME CHART_OF_ACCOUNT,
         FIFS.APPLICATION_COLUMN_NAME,
         FIFS.SEGMENT_NAME,
         FFV.FLEX_VALUE CC_SEG_VALUE,
         FFV.DESCRIPTION,
         GCC.CODE_COMBINATION_ID
      FROM
         APPS.FND_ID_FLEX_SEGMENTS FIFS,
         APPS.FND_FLEX_VALUES_VL FFV,
         APPS.FND_SEGMENT_ATTRIBUTE_VALUES FSAV,
         APPS.GL_CODE_COMBINATIONS GCC,
         APPS.FND_ID_FLEX_STRUCTURES_TL B
      WHERE
         FIFS.ID_FLEX_CODE = 'GL#'
         AND FIFS.ID_FLEX_NUM = FSAV.ID_FLEX_NUM
         AND FIFS.ID_FLEX_CODE = FSAV.ID_FLEX_CODE
         AND FSAV.SEGMENT_ATTRIBUTE_TYPE = 'GL_INTERCOMPANY'
         AND FSAV.ATTRIBUTE_VALUE = 'Y'
         AND FIFS.APPLICATION_COLUMN_NAME = FSAV.APPLICATION_COLUMN_NAME
         AND FIFS.FLEX_VALUE_SET_ID = FFV.FLEX_VALUE_SET_ID
         AND DECODE(
             FIFS.APPLICATION_COLUMN_NAME,
             'SEGMENT1',
             GCC.SEGMENT1,
             'SEGMENT2',
             GCC.SEGMENT2,
             'SEGMENT3',
             GCC.SEGMENT3,
             'SEGMENT4',
             GCC.SEGMENT4,
             'SEGMENT5',
             GCC.SEGMENT5
         ) = FFV.FLEX_VALUE
         AND GCC.CHART_OF_ACCOUNTS_ID = FIFS.ID_FLEX_NUM
         AND FIFS.APPLICATION_ID = B.APPLICATION_ID
         AND FIFS.ID_FLEX_CODE = B.ID_FLEX_CODE
         AND B.LANGUAGE = 'US'
         AND FIFS.ID_FLEX_NUM = B.ID_FLEX_NUM
    • For Update Query, enter

      SELECT
         FIFS.ID_FLEX_NUM,
         B.ID_FLEX_STRUCTURE_NAME CHART_OF_ACCOUNT,
         FIFS.APPLICATION_COLUMN_NAME,
         FIFS.SEGMENT_NAME,
         FFV.FLEX_VALUE CC_SEG_VALUE,
         FFV.DESCRIPTION,
         GCC.CODE_COMBINATION_ID
      FROM
         APPS.FND_ID_FLEX_SEGMENTS FIFS,
         APPS.FND_FLEX_VALUES_VL FFV,
         APPS.FND_SEGMENT_ATTRIBUTE_VALUES FSAV,
         APPS.GL_CODE_COMBINATIONS GCC,
         APPS.FND_ID_FLEX_STRUCTURES_TL B
      WHERE
         FIFS.ID_FLEX_CODE = 'GL#'
         AND FIFS.ID_FLEX_NUM = FSAV.ID_FLEX_NUM
         AND FIFS.ID_FLEX_CODE = FSAV.ID_FLEX_CODE
         AND FSAV.SEGMENT_ATTRIBUTE_TYPE = 'GL_INTERCOMPANY'
         AND FSAV.ATTRIBUTE_VALUE = 'Y'
         AND FIFS.APPLICATION_COLUMN_NAME = FSAV.APPLICATION_COLUMN_NAME
         AND FIFS.FLEX_VALUE_SET_ID = FFV.FLEX_VALUE_SET_ID
         AND DECODE(
            FIFS.APPLICATION_COLUMN_NAME,
            'SEGMENT1',
            GCC.SEGMENT1,
            'SEGMENT2',
            GCC.SEGMENT2,
            'SEGMENT3',
            GCC.SEGMENT3,
            'SEGMENT4',
            GCC.SEGMENT4,
            'SEGMENT5',
            GCC.SEGMENT5
        ) = FFV.FLEX_VALUE
        AND GCC.CHART_OF_ACCOUNTS_ID = FIFS.ID_FLEX_NUM
        AND FIFS.APPLICATION_ID = B.APPLICATION_ID
        AND FIFS.ID_FLEX_CODE = B.ID_FLEX_CODE
        AND B.LANGUAGE = 'US'
        AND FIFS.ID_FLEX_NUM = B.ID_FLEX_NUM
        AND GCC.LAST_UPDATE_DATE > ?
                                                                                                  ```
  • Select Add.
  • Select Yes for the following warning message: This table does not have a key defined. If you run an incremental load the new data will be added to the existing data, without applying any updates. Are you sure this is what you are trying to do?
  • For table name, enter GL_INTERCOMPANY_SEG.
  • In the Table Editor, for the CODE_COMBINATION_ID column, for Function, select key.
  • Select Done.

Load the New Values Table for the Additional Segment

Perform a full load of the GL_INTERCOMPANY_SEG table. Select the down arrow at the far right of the GL_INTERCOMPANY_SEG and select Load Table.

Create Joins from the Transaction Tables to the New Segment Table

Following are the transaction tables joined to each of the existing segment tables:

EBS_AP.AP_EXP_REPORT_DISTS_ALL
EBS_AP.AP_EXPENSE_REPORT_HEADERS_ALL
EBS_AP.AP_EXPENSE_REPORT_LINES_ALL
EBS_AP.AP_PAYMENT_DISTRIBUTIONS_ALL
EBS_AP.AP_RECURRING_PAYMENTS_ALL
EBS_AR.AR_CASH_RECEIPT_HISTORY_ALL
EBS_AR.AR_DISTRIBUTIONS_ALL
EBS_AR.AR_RECEIVABLE_APPLICATIONS_ALL
EBS_AR.AR_RECEIVABLES_TRX_ALL
EBS_AR.RA_CUST_TRX_LINE_GL_DIST_ALL
EBS_AR_MV.GL_CODES_MV
EBS_FIN_COMMON.AP_BANK_ACCOUNTS_ALL
EBS_INV.MTL_MATERIAL_TRANSACTIONS
EBS_PO.PO_REQ_DISTRIBUTIONS_ALL
EBS_PO.RCV_PARAMETERS
EBS_PO.RCV_SHIPMENT_LINES

For each transaction table listed above, create a join to GL_INTERCOMPANY_SEG. Here are the steps for the first transaction table, EBS_AP.AP_EXP_REPORT_DISTS_ALL.

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select the EBS_AP schema to open it.
  • In the Schema Designer, in the Tables section, select the AP_EXP_REPORT_DISTS_ALL transaction table to open it.
  • In the Action bar, select +Newjoin (as child).
  • For Child, for Select a column, select CODE_COMBINATION_ID.
  • For Parent

    • For Select Schema, select EBS_FIN_COMMON.
    • For Select Table, select GL_INTERCOMPANY_SEG.
    • For Select a column select CODE_COMBINATION_ID.

Update the Business View Label for the Additional Segment

Update the segments in the CodeCombination view of the GeneralLedger business schema with the following steps:

  • In the Navigation bar, select Business Schema.
  • In the Business Schema Manager, in the list view of business schemas, select the GeneralLedger 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 Edit (vertical ellipsis icon).
    • Enter Intercompany (SEGMENT4) in Label for SEGMENT4.
  • In the Action bar, select Done.

Create a New Business View for the Additional Segment

Create a new Business View called InterCompany in the GeneralLedger business schema with the following steps:

  • In the Navigation bar, select Business Schema.
  • In the Business Schema Manager, in the Action bar, select +NewAdd New View.
  • Drag and drop G_INTERCOMPANY_SEG from the Data panel to the business schema view.
  • Name the Business View InterCompany.
  • In the Action bar, select Done.

Create New Hierarchies for the Additional Segment

Create a new InterCompany hierarchy table with the following steps:

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select the EBS_FIN_COMMON schema to open it.
  • In the Schema Designer, in the Action bar, select +NewTableSQL Database.
  • In the Data Source dialog, enter the following properties

    • For Data Source, select EBS.
    • For Query, enter

      WITH FV AS (
         SELECT
             DISTINCT FLEX_VALUE_SET_ID,
             FLEX_VALUE,
             DESCRIPTION
         FROM
             APPS.FND_FLEX_VALUES_VL
         WHERE
             FLEX_VALUE_SET_ID = $$FLEX_VALUE_SET_ID
      )
      SELECT
         H.CHILD_FLEX_VALUE,
         H.PARENT_FLEX_VALUE,
         H.LAST_UPDATE_DATE,
         CD.DESCRIPTION CHILD_DESC,
         PD.DESCRIPTION PARENT_DESC
      FROM
         (
             SELECT
                 FLEX_VALUE_SET_ID,
                 CHILD_FLEX_VALUE,
                 PARENT_FLEX_VALUE,
                 LAST_UPDATE_DATE
             FROM
                 APPS.GL_SEG_VAL_NORM_HIERARCHY
             WHERE
                 FLEX_VALUE_SET_ID = $$FLEX_VALUE_SET_ID START WITH PARENT_FLEX_VALUE = 'PT' CONNECT BY NOCYCLE PARENT_FLEX_VALUE = PRIOR CHILD_FLEX_VALUE
         ) H
         LEFT OUTER JOIN FV CD ON CD.FLEX_VALUE_SET_ID = H.FLEX_VALUE_SET_ID
         AND CD.FLEX_VALUE = H.CHILD_FLEX_VALUE
         LEFT OUTER JOIN FV PD ON PD.FLEX_VALUE_SET_ID = H.FLEX_VALUE_SET_ID
         AND PD.FLEX_VALUE = H.PARENT_FLEX_VALUE
  • Select Add.
  • Select Yes for the following warning message: This table does not have a key defined. If you run an incremental load the new data will be added to the existing data, without applying any updates. Are you sure this is what you are trying to do?
  • For table name, enter InterCompany_Hierarchy.
  • Select Done.
Note

If the segment has multiple parents, a limited number of separate attributes or hierarchies can be created in Incorta.

Join the New Segment Hierarchy Table to the Segment Values Table

Here are the steps to create a join between InterCompany_Hierarchy and GLCODECOMBINATIONS.SEGMENT4:

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select the EBS_FIN_COMMON schema to open it.
  • In the Schema Designer, in the Tables section, select the GL_CODE_COMBINATIONS table to open it.
  • In the Action bar, select +NewJoin.
  • For Child, for Select a column, select SEGMENT4.
  • For Parent

    • For Select Table, select InterCompany_Hierarchy.
    • For Select a column select CHILD_FLEX_VALUE.
  • Select Done.
  • In the Action bar, select +NewJoin.
  • For Child

    • For Select Table, select InterCompany_Hierarchy.
    • For Select a column, select PARENT_FLEX_VALUE.
  • For Parent

    • For Select Table, select InterCompany_Hierarchy.
    • For Select a column select CHILD_FLEX_VALUE.
  • Select Done.

Add the New Business View and Columns to a Blueprint Dashboard Insight

Here are the steps to add InterCompany or any of its columns to a blueprint dashboard insight:

  • In the Navigation bar, select Content.
  • Select a dashboard to open it.
  • For an insight on a dashboard tab, select Edit (pen icon).
  • In the Analyzer, in the Data panel, add the GeneralLedger business schema if it has not already been added.
  • In the Data panel, drag and drop InterCompany or any of its columns to a tray in the Insight panel.

Configure Asset Category and Asset Location Key Flexfields

If you are using Oracle Fixed Assets, you may have additional segments in the Asset Category and Asset Location KFFs, for which you need to add segment columns to the Asset Category and Asset Location business views of the Fixed Asset Details business schema.

Identify the Asset Category KFF Segments

Run the following SQL against your Oracle EBS database to get a list of the segments in the asset category flexfield:

SELECT
   FIFS.ID_FLEX_NUM AS CHART_OF_ACCOUNT_ID,
   FIFS.SEGMENT_NUM,
   FIFS.SEGMENT_NAME,
   FIFS.APPLICATION_COLUMN_NAME,
   FIFS.FLEX_VALUE_SET_ID,
   LISTAGG(FSAV.SEGMENT_ATTRIBUTE_TYPE, ',') WITHIN GROUP(
       ORDER BY
           FSAV.SEGMENT_ATTRIBUTE_TYPE
   ) AS QUALIFIERS
FROM
   APPS.FND_ID_FLEX_SEGMENTS FIFS
   LEFT JOIN APPS.FND_SEGMENT_ATTRIBUTE_VALUES FSAV ON FIFS.ID_FLEX_CODE = FSAV.ID_FLEX_CODE
   AND FIFS.ID_FLEX_NUM = FSAV.ID_FLEX_NUM
   AND FIFS.APPLICATION_COLUMN_NAME = FSAV.APPLICATION_COLUMN_NAME
   AND FSAV.ATTRIBUTE_VALUE = 'Y'
WHERE
   FIFS.ID_FLEX_CODE = 'CAT#'
GROUP BY
   FIFS.ID_FLEX_NUM,
   FIFS.SEGMENT_NUM,
   FIFS.SEGMENT_NAME,
   FIFS.APPLICATION_COLUMN_NAME,
   FIFS.FLEX_VALUE_SET_ID
ORDER BY
   FIFS.ID_FLEX_NUM,
   FIFS.SEGMENT_NUM

Update the Asset Category KFF Segments in the Business View

Here are the steps to change the labels in the AssetCategory business views of the FixedAssetDetails business schema to reflect your implementation:

  • In the Navigation bar, select Business Schema.
  • In the Business Schema Manager, in the list view of business schemas, select the FixedAssetDetails business schema to open it.
  • In the Business Schema Designer, select the AssetCategory business view to expand it.
  • Update the labels to reflect the Asset Category KFF segment names.
  • In the Action bar, select Done.

Identify the Asset Location KFF Segments

Run the following SQL against your Oracle EBS database to get a list of the segments in the asset location flexfield:

SELECT
   FIFS.ID_FLEX_NUM AS CHART_OF_ACCOUNT_ID,
   FIFS.SEGMENT_NUM,
   FIFS.SEGMENT_NAME,
   FIFS.APPLICATION_COLUMN_NAME,
   FIFS.FLEX_VALUE_SET_ID,
   LISTAGG(FSAV.SEGMENT_ATTRIBUTE_TYPE, ',') WITHIN GROUP(
       ORDER BY
           FSAV.SEGMENT_ATTRIBUTE_TYPE
   ) AS QUALIFIERS
FROM
   APPS.FND_ID_FLEX_SEGMENTS FIFS
   LEFT JOIN APPS.FND_SEGMENT_ATTRIBUTE_VALUES FSAV ON FIFS.ID_FLEX_CODE = FSAV.ID_FLEX_CODE
   AND FIFS.ID_FLEX_NUM = FSAV.ID_FLEX_NUM
   AND FIFS.APPLICATION_COLUMN_NAME = FSAV.APPLICATION_COLUMN_NAME
   AND FSAV.ATTRIBUTE_VALUE = 'Y'
WHERE
   FIFS.ID_FLEX_CODE = 'LOC#'
GROUP BY
   FIFS.ID_FLEX_NUM,
   FIFS.SEGMENT_NUM,
   FIFS.SEGMENT_NAME,
   FIFS.APPLICATION_COLUMN_NAME,
   FIFS.FLEX_VALUE_SET_ID
ORDER BY
   FIFS.ID_FLEX_NUM,
   FIFS.SEGMENT_NUM

Update the Asset Location KFF Segments in the Business View

Here are the steps to change the labels in the AssetLocation business views of the FixedAssetDetails business schema to reflect your implementation:

  • In the Navigation bar, select Business Schema.
  • In the Business Schema Manager, in the list view of business schemas, select the FixedAssetDetails business schema to open it.
  • In the Business Schema Designer, select the AssetLocation business view to expand it.
  • Update the labels to reflect the Asset Location KFF segment names.
  • In the Action bar, select Done.

Configure Descriptive Flexfields

You can configure Descriptive Flexfields (DFFs) you would like to use for reporting.

Get the list of DFF segments used by customer

Run the following SQL against your Oracle EBS database to identify the DFFs:

SELECT
   DFF.APPLICATION_ID APPLICATION_ID,
   DFF.DESCRIPTIVE_FLEXFIELD_NAME FLEXFIELD_CODE,
   DFFTL.TITLE FLEXFIELD_NAME,
   DFFCTX.DESCRIPTIVE_FLEX_CONTEXT_CODE CONTEXT_CODE,
   DFF.CONTEXT_COLUMN_NAME CONTEXT_COLUMN_NAME,
   DFFCOL.APPLICATION_COLUMN_NAME COLUMN_CODE,
   DFFCOLTL.FORM_LEFT_PROMPT COLUMN_NAME,
   DFFCOL.FLEX_VALUE_SET_ID FLEX_VALUE_SET_ID,
   DFF.APPLICATION_TABLE_NAME APPLICATION_TABLE_NAME
FROM
   APPS.FND_DESCR_FLEX_COLUMN_USAGES DFFCOL,
   APPS.FND_DESCRIPTIVE_FLEXS DFF,
   APPS.FND_DESCRIPTIVE_FLEXS_TL DFFTL,
   APPS.FND_DESCR_FLEX_CONTEXTS DFFCTX,
   APPS.FND_DESCR_FLEX_CONTEXTS_TL DFFCTXTL,
   APPS.FND_DESCR_FLEX_COL_USAGE_TL DFFCOLTL
WHERE
   (
       DFFCTXTL.APPLICATION_ID = DFFCTX.APPLICATION_ID
       AND DFFCTXTL.DESCRIPTIVE_FLEXFIELD_NAME = DFFCTX.DESCRIPTIVE_FLEXFIELD_NAME
       AND DFFCTXTL.DESCRIPTIVE_FLEX_CONTEXT_CODE = DFFCTX.DESCRIPTIVE_FLEX_CONTEXT_CODE
   )
   AND (
       DFF.APPLICATION_ID = DFFTL.APPLICATION_ID
       AND DFF.DESCRIPTIVE_FLEXFIELD_NAME = DFFTL.DESCRIPTIVE_FLEXFIELD_NAME
   )
   AND (
       DFF.APPLICATION_ID = DFFCOL.APPLICATION_ID
       AND DFF.DESCRIPTIVE_FLEXFIELD_NAME = DFFCOL.DESCRIPTIVE_FLEXFIELD_NAME
   )
   AND (
       DFFCOL.APPLICATION_ID = DFFCTX.APPLICATION_ID
       AND DFFCOL.DESCRIPTIVE_FLEXFIELD_NAME = DFFCTX.DESCRIPTIVE_FLEXFIELD_NAME
       AND DFFCOL.DESCRIPTIVE_FLEX_CONTEXT_CODE = DFFCTX.DESCRIPTIVE_FLEX_CONTEXT_CODE
   )
   AND (
       DFFCOL.APPLICATION_ID = DFFCOLTL.APPLICATION_ID
       AND DFFCOL.DESCRIPTIVE_FLEXFIELD_NAME = DFFCOLTL.DESCRIPTIVE_FLEXFIELD_NAME
       AND DFFCOL.DESCRIPTIVE_FLEX_CONTEXT_CODE = DFFCOLTL.DESCRIPTIVE_FLEX_CONTEXT_CODE
       AND DFFCOL.APPLICATION_COLUMN_NAME = DFFCOLTL.APPLICATION_COLUMN_NAME
   )
   AND (
       DFFCOL.APPLICATION_ID = 222
       AND DFFCOL.DESCRIPTIVE_FLEXFIELD_NAME LIKE 'HZ_PARTIES%'
   )
   AND (DFFCTX.ENABLED_FLAG = 'Y')
   AND (DFFCTXTL.LANGUAGE = DFFCOLTL.LANGUAGE)
   AND (DFFCTXTL.LANGUAGE = DFFTL.LANGUAGE)
   AND (DFFTL.LANGUAGE IN ('US'))

In the example above, HZ_PARTIES has two DFFs in the Telco context: Connection and IMEI. This example will illustrate how you can add DFFs to the Oracle EBS blueprint.

Add Custom Columns to the Physical Schema

To add the DFFs to the HZ_PARTIES table of the EBS_PARTY_COMMON schema, you can modify the Query and Update Query SQL as follows:

  • In the Navigation bar, select Schema.
  • In the Schema Manager, select the Schemas tab.
  • In the list view of physical schemas, select the EBS_PARTY_COMMON schema to open it.
  • In the Schema Designer, in the Tables section, select the HZ_PARTIES table to open it.
  • In the Table Editor, select the EBS SQL icon to open the Data Source dialog.
  • In the Data Source dialog

    • In Query, add ATTRIBUTE11 and ATTRIBUTE12 to the end of the SELECT statement.
    • In Update Query, add ATTRIBUTE11 and ATTRIBUTE12 to the end of the SELECT statement.
  • Select Validate.
  • Select Done.

Query

Update Query

Load Data into the Custom Columns

Here are the steps to load the HZ_PARTIES table and preview the data:

  • Select the down arrow at the far right of the HZ_PARTIES and select Load Table.
  • Select the HZ_PARTIES table to open it.
  • In the Table Editor, in the Columns section, select Preview Data to view a sample of the data in the custom columns.

Add the Custom Columns to the Business Schema Views

Here are the steps to add the custom columns to the OrderCustomerInformation business view:

  • In the Navigation bar, select Business Schema.
  • In the Business Schema Manager, select the OM_SalesOrders business schema to open it.
  • In the Business Schema Designer, select the OrderCustomerInformation business view to open it.
  • Drag and drop Attribute11 and Attribute12 from the Data panel to the business schema view.
  • Change the Name and Label of Attribute11 to Connection.
  • Change the Name and Label of Attribute12 to IMEI.
  • In the Action bar, select Done.

If a single DFF has multiple contexts, use a formula column in the business view to evaluate the segment column based on attribute category.

Here is an example of an HZ_PARTIES DFF with multiple contexts, Life Sciences Customer and Physician. The query below is used to identify the DFF contexts:

SELECT
DESCRIPTIVE_FLEXFIELD_NAME,
DESCRIPTIVE_FLEX_CONTEXT_CODE,
    APPLICATION_COLUMN_NAME,
    END_USER_COLUMN_NAME
FROM
    FND_DESCR_FLEX_COL_USAGE_VL
WHERE
    DESCRIPTIVE_FLEXFIELD_NAME LIKE 'HZ_PARTIES%';

In this example, you can use a case statement to determine the context:

  • Drag and drop New Formula to the business view.
  • Select Set Formula.
  • In the Formula Builder, enter the following:

    CASE(
    EBS_PARTY_COMMON.HZ_PARTIES.ATTRIBUTE_CATEGORY = "Life Sciences Customer",
    EBS_PARTY_COMMON.HZ_PARTIES.ATTRIBUTE11,
    EBS_PARTY_COMMON.HZ_PARTIES.ATTRIBUTE12
    )
  • Select Validate & Save.
  • In the Action bar, select Done.

Add the New Custom Columns to a Blueprint Dashboard Insight

Here are the steps to add the Connection and IMEI columns to a blueprint dashboard insight:

  • In the Navigation bar, select Content.
  • Select a dashboard to open it.
  • For an insight on a dashboard tab, select Edit (pen icon).
  • In the Analyzer, in the Data panel, add the OM_SalesOrders business schema if it has not already been added.
  • In the Data panel, drag and drop Connection or IMEI to a tray in the Insight panel.

Modify Currency Conversion Logic

You can modify the currency conversion logic in the business schemas, as needed. For example, here are the steps to modify the AvgRate formula in the Payments business view of the BillingAndTax business schema:

  • In the Navigation bar, select Business Schema.
  • In the Business Schema Manager, select the BillingAndTax business schema to open it.
  • In the Business Schema Designer, for the Payments business view, select Edit (vertical ellipsis icon).
  • For AvgRate, select Change Formula:

    • In the Formula Builder, modify the formula as necessary.
    • Select Validate & Save.
  • In the Action bar, select Done.

Configure Seeded Session Variables

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

Variable Name Description Type Query
Default_Book_Type_code This variable is used to provide a default fixed asset book type Session SELECT 'OPS CORP' FROM dual
Default_Global_Currency This variable is used to provide a default currency Session query('USD')
Default_Exch_Rate_Type This variable is used to provide a default exchange rate type Session query('Corporate')
Default_Fiscal_Year This variable is used to provide a default fiscal year in the financial dashboards Session query(2010)
Default_Ledger This variable is used to provide a default ledger value in the financial dashboards Session SELECT 'Vision Operations (USA)' FROM dual
Default_Period This variable is used to provide a default fiscal period in the financial dashboards Session SELECT 'Nov-09' FROM dual
Default_Period_2 This variable is used to provide a default fiscal period in the financial dashboards Session SELECT 'Sep-09' FROM dual
Default_Start_Date This variable is used to provide a default start date Session query(2007)

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 Data Security

Configure additional data security as required. There is a seeded session variable for org based data security named ORG_IDS_EBS_EXAMPLE.

For example, if you want to secure RA_CUSTOMER_TRX_ALL using org security, add a table security filter as follows:

or($user='admin',inlist(EBS_AR.RA_CUSTOMER_TRX_ALL.ORG_ID,$ORG_IDS_EBS_EXAMPLE))

If any other form of data security is required, refer to Data Security Using Session Variables.

EBS Blueprint Security Groups

The EBS Blueprint tenant includes the following security groups:

Feature Supported
ReportAdmins Analyze User, Schema Manager, User, User Manager
ReportUsers Individual Analyzer, User

Additional Information

Table Placeholders

Some tables have 1=0 in the SQL because they are not used in the blueprints, and as a result, data is not loaded into the table. If these tables are needed for your implementation, you can modify the SQL to load the table.

FND Lookups

You can support FND_LOOKUPS by using a lookup() function in a formula field so that you do not need to join to the table. For example:

lookup(EBS_FND_COMMON.FND_LOOKUP_VALUES.MEANING, EBS_FND_COMMON.FND_LOOKUP_VALUES.LOOKUP_TYPE,'TRANSFER STATUS', EBS_FND_COMMON.FND_LOOKUP_VALUES.LOOKUP_CODE,EBS_PA.PA_COST_DISTRIBUTION_LINES_ALL.TRANSFER_STATUS_CODE , EBS_FND_COMMON.FND_LOOKUP_VALUES.LANGUAGE,'US')

EBS Hierarchies

For EBS hierarchies like Account or Cost Center, use EBS_GL.GL_SEG_VAL_NORM_HIERARCHY. For segments without multiple parents, use one of the following two approaches:

  • Incorta self join hierarchy
  • Flattened data

For segments that have multiple parents, further analyze the top nodes for the given segment. You can create a limited number of top nodes as separate attributes or hierarchies within Incorta.

Calendars

The Gregorian calendar is supported with a join to the EBS_CAL_COMMON.GREGORIAN_CALENDAR table. This table is loaded from the Date_US.csv file.

The fiscal calendar is supported with a join to the EBS_CAL_COMMON.GL_DATE table.

Multi-Currency

Out of the box, amounts in Entered and Accounted currency are supported. To support other global currencies, such as USD, for the multi-ledger use case, use the EBS_FIN_COMMON.GL_DAILY_RATES table and customize it as required. Perform a lookup to this table to get the exchange rate and multiply it with the base amount. For an example, refer to one of the following fields in the CollectionsManager.Payments schema:

  • Amount Due Original (AR Global)
  • Amount Due Original (Revenue Global)
  • Amount Due Remaining (AR Global)
  • Amount Due Remaining (Revenue Global)

Multiple Child Tables with a Common Parent

The Accounts Payable module has an example use case of multiple child tables with a common parent. AP_INVOICE_PAYMENTS_ALL is a child of AP_INVOICES_ALL. There is no direct path from AP_INVOICE_DISTRIBUTIONS_ALL to AP_INVOICE_PAYMENTS_ALL. As a result, it is not possible to report Payment Amount with Invoice Number and PO ID in one Incorta report. To resolve this issue, create a Materialized View that has the INVOICE_ID (key) and the aggregated payment amounts from the payments table, and make it the parent table of AP_INVOICES_ALL.