5 Setting Up Fusion Applications Cloud Data Sources

Follow these procedures to deploy Oracle Business Intelligence Applications (Oracle BI Applications) with a Fusion Applications Cloud data source.

Topics:

• Overview of Oracle Fusion Applications Cloud Source System Support

• Fusion Applications Cloud Source System Deployment Options

• Fusion Applications Cloud Source System Deployment Roadmap

• Create a Service Request to Deploy Oracle BI Cloud Connector Console

• Provision a User For Export and Import of BI Data from Fusion UCM

• Provision a User for Oracle Business Intelligence Cloud Connector Access

• Register the Fusion Applications Source

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

• Extract Data into Universal Content Management using BI Cloud Connector Console

• Synchronize Deletes in Your Cloud Extract

• Configure Proxy Settings for WebLogic Server

• Managing Fusion Flex Extensions in Release 11.1.1.10.3

• Set Up Key Flex Fields for Financials Fusion Applications Source Data

• Setting Up Key Flex Fields for HCM Fusion Applications Source Data

Overview of Oracle Fusion Applications Cloud Source System Support

You can enable your on-premises deployment of Oracle BI Applications to consume data from your Fusion Cloud Services, providing you with a comprehensive set of analytics that span your on-premises and cloud service systems to give you a complete view of your business.

Along with the many supported on-premises source business systems, support for Oracle Fusion Applications Cloud Services enables a robust hybrid analytics solution to deliver the complete picture regardless of where the data originates.

You can securely connect your on-premises Oracle BI Applications deployment to your Oracle Fusion Applications Cloud Service, which automates the flow of data from your source system to your Oracle Business Analytics Warehouse, enabling your hybrid analytics solution.

Key features include:

• Extracts are from VOs and not direct from DB.

• Leverages Standard Security Methods of Source Cloud Systems to secure data in-transit.

Fusion Applications Cloud Source System Deployment Options

When migrating to the Cloud, you can enable your on-premises deployment of Oracle BI Applications to consume data from your Fusion Cloud Services using these deployment options.

Hybrid Data Sources Category

Cloud-Only Data Sources

Fusion Application Cloud Source System Deployment Roadmap

You can deploy a Fusion Applications Cloud data source to your on-premises deployment of Oracle BI Applications.

Prerequisites for deployment:

• Oracle BI Applications 11.1.1.10.3

• Oracle Cloud Applications; refer to the Oracle BI Applications 11.1.1.10.3 Certification Matrix for the certified Cloud Application releases.

To deploy a Fusion Applications Cloud data source:

1. Create a service request to deploy Oracle BI Cloud Connector Console (BICCC) on your Fusion Applications pod. Additionally, create a service request to review sizing of your Fusion Applications pod for Oracle BI Cloud Connector Console usage. See Create Service Requests for Oracle BI Cloud Connector Console.
2. Provision a new or existing Fusion Applications user with export and import privileges for Oracle Business Intelligence. See Provision a User For Export and Import of BI Data from Fusion UCM.
3. Provision a User for Oracle Business Intelligence Cloud Connector Access.
4. Register the Fusion Applications Source.
5. Create a Load Plan and Specify Offerings and Fact Groups to Load.
6. Extract Data into Universal Content Management using BI Cloud Connector Console.
7. Synchronize Deletes in Your Cloud Extract.
8. Configure Proxy Settings for WebLogic Server. If you have already configured WebLogic server to allow any external connection, then you can skip this step.
9. Set up the Key Flex Fields before you execute the load plan (created in the step 5) if you are deploying Key Flex Fields for Financials. See Setting Up Key Flex Fields for Financials Fusion Applications Source Data.
10. Set Up Key Flex Fields for HCM Fusion Applications Source Data.

Creating Service Requests for Oracle Business Intelligence Cloud Connector Console

Create a service request if you're deploying Oracle Fusion Applications data sources.

Sign in to My Oracle Support (support.oracle.com) and create a service request to review sizing of your Oracle Fusion Applications pod for Oracle BI Cloud Connector Console usage. When the service request is received, the Oracle Cloud Services team reviews the available disk space and UCM tablespace on the applicable Oracle Fusion Applications pod and increases the space as required.

Note:

In Oracle Fusion Applications Release 10 and higher, Oracle BI Cloud Connector Console is automatically deployed and no separate service request is required to deploy it.

Log a service request, and specify the following details:

• Action: Review sizing for BICCC

• Problem type: Specify this information:

  • Service Type: Oracle Fusion Global Human Resource Cloud Service

  • Problem Type: Hosting Services – Application

  • Sub-Problem Type: Review sizing for BICCC

  • BIA Deployment: On-premise

  • User ID: <User ID for Business Intelligence Cloud Connector Console (BICCC) access>

  • FA POD details: <POD ID>

  • FA POD: <Stage and Production>

• Inputs: This service request initiates the review of available disk space and UCM tablespace on the applicable Fusion pod. Provide the Oracle Fusion Applications POD details in the service request. This must include the POD identifier (the URL used to access the Fusion environment).

When the service request is resolved, Oracle Cloud Services provides you with the UCM Server and Oracle BI Cloud Connector Console URLs.

Provisioning a User for Export and Import of BI Data from Fusion UCM

Provision a new or existing user in Oracle Fusion Applications with privileges to download data from Fusion Universal Content Management (UCM).

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

To provision a user for Fusion access:

1. Create a new user, or use an existing user in Oracle Fusion Applications that has privileges to download data from Fusion UCM.
2. Using Oracle Authorization Policy Manager (APM), assign the following application role to the applicable new or existing user:

   Application Role	Display Name
   OBIA_EXTRACTTRANSFORMLOAD_RWD	Upload and download data from on-premises system to cloud system

Provisioning a User for Oracle BI Cloud Connector Console Access

Use these steps to provide additional users access to the Oracle BI Cloud Connector Console (BICCC) user interface.

The service request that you created to deploy the Oracle BI Cloud Connector Console performs the setup for the identified user. See Creating Service Requests for Oracle Business Intelligence Cloud Connector Console. Complete these steps only if additional users need to access the console.

For Oracle Fusion Applications Data Sources

Use the Security Console in Oracle Fusion Applications to create an administrative role that inherits the Oracle BI Cloud Connector Console privileges from existing roles and assign the user to that role.

To provision a user:

1. In Oracle Fusion Applications, navigate to the Security Console in the Navigator.

2. In the Security console, create a BICC_ADMIN role.

   1. Click Create Role.

   2. In the Basic Information page, enter the following values and click Next.

      1. Role Name: BICC_ADMIN

      2. Role Code: BICC_ADMIN

      3. Role Category: BI — Abstract Roles

   3. Click the Add icon in the Role Hierarchy list.

   4. In the Add Role Membership dialog, search for ESS.

   5. In the search results, confirm that the ESS Administrator role is displayed and then click Add Role Membership.

   6. Search for ORA_ASM_APPLICATION_IMPLEMENTATION_ADMIN_ABSTRACT and click Add Role Membership.

   7. Search for OBIA_EXTRACTTRANSFORMLOAD_RWD and click Add Role Membership.

   8. Close the Add Role Membership dialog.

   9. Click Next.

   10. In the Users page, click Add User.

   11. In the Add User dialog, search for the name of the user you want to assign access to, and then click Add User to Role.

   12. Close the Add User dialog.

   13. Click Next.

   14. Click Save and close.

Registering the Fusion Applications Source

Register the Oracle Fusion Applications source.

Ensure that the applicable SDS schemas have been created during installation and configuration of Oracle BI Applications. For Oracle Fusion Applications cloud source systems, ensure that you select the Oracle Fusion 11 SDS schema in the Select Components dialog of Oracle Fusion Middleware Repository Creation Utility.

See Creating Schemas Using Business Analytics Applications Suite RCU

Note:

If you haven't created the applicable SDS schemas during installation and configuration of Oracle BI Applications, then you can create them as a post-installation step.

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

To Register the Oracle Fusion Applications Source:

1. Log in to Oracle 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.
   
   Description of the illustration 103-register-fusion-step2.gif
3. Click the Add icon (+) to display the Register Source dialog.
   
   Description of the illustration 103-register-fusion-step3.gif
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.

   • Optionally, in the Description field, enter a short description to help administrators and implementers identify and use this data source in Configuration Manager.

   • In the Data Source Number field, enter an integer or use the spinner to specify a number to identify data in the Oracle Business Analytics Warehouse. This number must be unique within Configuration Manager.

   • In the Source Load Technology, select ODI External File to define the cloud adapter mode.

5. Click Next to display the external file location details.
6. In the External File Location Details dialog, specify the following details, and then click Save:
   
   Description of the illustration 103-register-fusion-step6.gif

   1. Protocol – Select https.

   2. Host and Port – Specify the host and port details provided by the Oracle Cloud Services in your service request when it's closed.

   3. User Name and Password – Specify the user name and password of the user that you provisioned for export and import of BI data from Fusion Universal Content Management server. See Provisioning a User for Export and Import of BI Data from Fusion UCM.

   4. Click Test UCM Connection to test the connection.

Creating a Load Plan and Specifying Offerings and Fact Groups to Load

Create a load plan and specify offerings and fact groups to load.

To create a 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.
   
   Description of the illustration 103ps1-define-lp-step2.gif
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.
   
   Description of the illustration 103ps1-define-lp-step4.gif
5. Click Save.
6. In the list of Load Plans, select the new load plan, and click Generate.

Setting up ODI Agent Concurrent Sessions

For optimal performance, set the maximum number of sessions for Oracle Data Integrator (ODI) Agent to no more than five. To set up the maximum number of sessions supported by an agent:

1. Log into ODI Studio.

2. Display the Topology tab, and navigate to the Physical Architecture tab.

3. Expand Agents and select the applicable ODI Agent.

   
   Description of the illustration 103ps1-define-lp-step6_3.gif
4. In the agent details pane, set the maximum number of sessions and threads supported by the agent as 5. If you're creating a new agent, then ensure that you set the maximum number of sessions supported by the agent as 5.

Extracting Data into Universal Content Management using Oracle BI Cloud Connector Console

You can extract data from your cloud source into the Universal Content Management (UCM) server using the Oracle BI Cloud Connector Console (BICCC).

Use the Oracle BI Cloud Connector Console URL provided to you in the SR that you logged to deploy Oracle BI Cloud Connector Console and the login details of the applicable user to log into this console. See Create a Service Request to Deploy Fusion Applications Cloud Source System Data, Provision a User For Export and Import of BI Data from Fusion HCM, Provision a User for Oracle Business Intelligence Cloud Connector Access

You can also start Oracle BI Cloud Connector Console using a HTTP URL based on the following format: http://<FA OHS Host>:<FA OHS Port>/biacm

Description of the illustration biain_biccc1.gif

To extract data from a cloud source to UCM:

Note:

Oracle BI Applications on-premises users must extract data to UCM.

1. From the landing page, select the Configure Cloud Extract link on the Tasks bar.
2. In the list of Offerings, select the check box next to the Cloud source system functional areas that you want to deploy.
   
   Description of the illustration biain_biccc2.gif
3. Click Save, then Done
4. To reset the last extract date so that a full data load is performed at the next load for the selected Offering, instead of an incremental load, click Reset to Full Extract icon in the tool bar and click OK when the application displays the warning message. You typically use this option if your business requirements have changed or if fact data has been corrupted. You can reset to full extract at offering and VO level.
   
   Description of the illustration biain_biccc3.gif

   Note:

   You set up a Scheduled Load Plan in Oracle BI Applications Configuration Manager (BIACM) to extract from UCM server into Oracle Business Analytics Warehouse. To reset the extraction on Oracle Business Analytics Warehouse, use the BIACM option: Manage Load Plans\Execute\Execute Reset Data Warehouse Scenario. See Manage Load Plans Toolbar Options in Oracle Business Intelligence Applications ETL Guide.
5. To schedule the extract, click the Schedule icon in the tool bar.
   
   Description of the illustration biain_biccc5.gif
6. Click the + icon to create a new schedule.
   
   Description of the illustration biain_biccc6.gif
7. Specify when you want to perform the cloud extract.
8. Click Schedule, then Done.
9. Click the Configure External Storage link on the Tasks bar.
10. Select UCM as the storage type.
    
    Description of the illustration biain_biccc4.gif
11. View the configuration information displayed on this page and click Save, then Done.

Synchronizing Deletes for a Cloud Extract

If you're loading data into the Universal Content Management (UCM) server using a Cloud Extract, then you use Oracle BI Cloud Connector Console (BICCC) to synchronize deletes in the source system with deletes in the Cloud Extract data.

Before you start, log into Oracle BI Cloud Connector Console using the Web link and user name supplied to you by Oracle Cloud Support. You can also start Oracle BI Cloud Connector Console using a HTTP URL based on the following format: http://<FA OHS Host>:<FA OHS Port>/biacm.

To synchronize your Cloud Extract data:

1. Select the Configure Cloud Extract link on the Tasks pane.
2. Click the Manage Extract Schedules icon () to display the Schedules dialog.
   
   Description of the illustration bicc-schedule-setup.gif
   
3. Click the Add icon () to create a new schedule.
4. Use the Name field to specify a short name to identify this schedule in Oracle BI Cloud Connector Console.
   
   Description of the illustration data_sync_cloud_extract.gif
   
5. Select ‘Deleted Record Extract’ from the Job Type drop down.
6. Use the Recurrence drop down to specify when you want to synchronize the data.
   You typically schedule the synchronization to run at a time when the load on the Fusion Applications source system is low, for example, during off-peak hours. In addition, you must schedule the synchronization so that it doesn't conflict with the Cloud Extract or the data load into the Oracle Business Analytics Warehouse.
7. Save the details.

Configuring Proxy Settings for WebLogic Server

To use external web services or HTTP data sources when Oracle BI Applications is configured behind a firewall or requires a proxy to access the internet, you must configure Oracle WebLogic Server to allow the web service requests and to be aware of the proxy.

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

Define the proxy host and the non-proxy hosts to WebLogic BI and ODI-managed server (bi_server1 and ODI_server1) by setting the following parameters:

• -Dhttp.proxyHost - specifies the proxy host. For example:

  -Dhttp.proxyHost=www-proxy.example.com

• -Dhttp.proxyPort - specifies the proxy host port. For example:

  -Dhttp.proxyPort=80

• -Dhttp.nonProxyHosts - specifies the hosts to connect to directly, not through the proxy. Specify the list of hosts, each separated by a "|" character; a wildcard character (*) can be used for matching. For example:

  -Dhttp.nonProxyHosts="localhost|*.example1.com|*.example2.com

To set these proxy parameters and the Web service configuration for your WebLogic Server:

1. Sign in to Weblogic Admin Console, click Lock and Edit, navigate to Environments, and expand Servers.
2. In Servers, click bi_server1, and select the Server_start tab.
3. In the Server_start tab, click Arguments, and enter the following in the Argument dialog:

   Note:

   Don't erase existing arguments; add these lines along with the existing arguments.

   -Dhttps.proxyHost=www.proxy.example.com -Dhttps.proxyPort=80
   -Dhttp.proxyHost=www.proxy.example.com -Dhttp.proxyPort=80
   -Dhttp.nonProxyHosts=localhost|*.mycompany.com|*.mycorporation.com|*.otherhost
   .com
   -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl  
   -Djavax.xml.soap.SOAPFactory=oracle.j2ee.ws.saaj.soap.SOAPFactoryImpl
   -Djavax.xml.soap.SOAPConnectionFactory=oracle.j2ee.ws.saaj.client.p2p.HttpSOAP
   ConnectionFactory

   where:

   www-proxy.example.com is an example proxy host.

   80 is the example proxy port.

   localhost|*.mycompany.com|*.mycorporation.com|*.otherhost.com are example non-proxy hosts.

   For hosts with http protocol, you can add -Dhttp.proxyHost and -Dhttp.proxyPort.

Managing Fusion Flex Extensions in Release 11.1.1.10.3

This section applies to the Oracle BI Applications release 11.1.1.10.3 and to Oracle Fusion Applications.

The warehouse tables, by default, carry a limited number of extension columns. For char type columns there are usually around 30 char columns in the warehouse tables that can be used for extensions. At times there could be cases where you end up with more than 30 columns. In such a case, only 30 columns would get mapped for extensions while the remaining columns get loaded in the SDS.

This section explains the current options available in such a case and provides a way by which you can control the columns that should get mapped rather than just let the algorithm decide which columns should get mapped.

Option 1: Using the BI Applications Enabled Flag on the Fusion side

This is the recommended approach.

If all the flexfields you defined on the VO aren't relevant for BI Applications, you can restrict the flex extensions in BI Applications to only those that are relevant to BI Applications, by following these steps:

1. Enable the BI Enabled option.

   When you define a flex field in Fusion, you see the BI Enabled option. Enabling this option ensures that this flex field gets extended to the repository and eventually flows into the BI Applications. However, if some columns aren't required for BI Applications, you can disable this option for those columns.

   
   Description of the illustration bi_enabled1-gif.gif
2. On editing the selected flex field, you can see the option for existing flexfields. Disable the option for the ones that aren't required for BI Applications.

   Note:

   Disabling the BI Enabled option disables it for OTBI as well. Disable this option only if it isn't required for OTBI as well as BI Applications. There is currently no way to disable it only for BI Applications.

3. After disabling the option, wait until the BI Extender runs again to update the repository. Post that schedule, run a full extract, and do a full load again. Drop the SDS tables and reset the warehouse (using the option in the Configuration Manager) before running the full load.

Option 2: Specifying a Column Exclude List in ODI Repository:

If Option 1 isn't feasible, then try this option. The Extension framework in BI Applications looks at the ODI repository to identify which columns are extension columns. A workaround is to add the extension columns you don't need in BI Applications, to the ODI repository against the VO. This way the extension framework treats them as regular columns and not extension columns.

Based on your use case, follow either of these instructions:

• You've access to the extended Fusion repository

• You don't have access to the extended Fusion repository

If you've access to the Fusion source repository from your ODI environment, follow these steps:

1. Run the Oracle BI Applications reverse knowledge module (RKM).

2. Log in to the ODI repository using the ODI studio, navigate to the Models tab, and open Oracle Fusion 11 HCM model as shown below.

   Note:

   The Fusion Connection should be pointing to the BI Server with the extended repository.

   
   Description of the illustration 103ps1-ffe-option2-1.gif

3. Set the Mask property to %.FLEX_BI_BaseWorkerAsgDFF_VI as shown below. This prevents attempts to refresh the model for all the VOs.

4. Click Reverse Engineer to bring all the VO’s extension columns into the model.
   Description of the illustration 103ps1-ffe-option2-2.gif

5. Once you see all the extension columns against the VO’s definition, identify the extension columns that are needed for your business, and then delete the required columns from the data store.

   For Example, if SE_HRBP_ extension column is needed for your business, delete it and save the changes.

   For the remaining extension columns which you don't need, or if you don't want the column to be populated or created in SDS, use the flexfield OBI Populate Column in SDS to remove them.

6. Edit the flexfield value to set the value as N (by default the flexfield value is be set to Y), and save the changes.

If you don't have access to the fusion source repository from your ODI Environment, follow these steps:

In this case, since you don't have access to the fusion source environment, there is no way to run RKM to reverse engineer a VO to add all extensible columns to it. Hence you should add all unused extensible columns manually against a VO’s data store.

Note:

In Oracle Fusion Applications, the extractor provides mdcsv files which contain the metadata of the extended columns. Refer to that mdcsv file when you're manually adding the columns in the ODI.

1. Log in to the ODI repository using the ODI studio, navigate to the Models tab, find the data store, and open it as shown below.
   Description of the illustration 103ps1-ffe-option2-3.gif

2. Click Add to add columns. Choose the correct data type, length and other options, and save the changes.

   If you don't want the column to be populated or created in the SDS, then use the flexfield OBI Populate Column in SDS to remove them.

3. Edit the columns and go to the Flexfields tab. By default, the flexfield value is set to Y. Edit the flexfield value, set the value to N, and save the changes.

4. Run the RKM to update the newly added extensible column’s short name.

5. Navigate to the Models tab and open the Oracle Fusion 11 HCM model.

6. Click the Reverse Engineer tab and set the Mask property to%.FLEX_BI_BaseWorkerAsgDFF_VI as shown below. This prevents attempts to refresh the model for all the VOs.
   Description of the illustration 103ps1-ffe-option2-4.gif

7. Set the INTROSPECT_SOURCE option to false, the USE_LOG option to false, and enable the REFRESH_SDS_FLEXFIELDS mode by changing the option value to true.

8. Click Reverse Engineer to bring all VO extension columns into the model.

   Note:

   If you've already loaded data, then you need to do a full load again. Reset the warehouse, make sure that all warehouse tables are empty, and reload.

Option 3

If Option 1 and 2 aren't possible, then use option 3. In this option you attempt to manually update the backend table that controls the mapping between the source column and the target warehouse column. Identify a column that has already been mapped but is not required, and then run backend update statements to switch it to a column that should get mapped instead.

As an example, assume that CATEGORY10_ extension column isn't required and you want to switch this mapping with INTERNATIONAL__STATUS_ extension column.

1. Connect to BIApps warehouse schema using SQL tools.

2. Run the following update script:

   UPDATE W_ETL_FLEX_SQL SET FLEX_SRC_ATTRIB     ='INTERNATIONAL__STATUS_', 
   ATTRIB_SQL_EXPRESSION='ASGDFF.INTERNATIONAL__STATUS_'WHERE FLEX_CODE     
   ='HRASG'  AND FLEX_SRC_TABLE      
   ='HcmTopModelAnalyticsGlobalAM.BaseWorkerAsgDFFBIAM.FLEX_BI_BaseWorkerAsgDFF_VI' AND FLEX_SRC_ATTRIB ='CATEGORY10_'
   AND FLEX_ ATTRIB='ASSIGNMENT_ATTR14_CHAR' 
   AND DATASOURCE_NUM_ID   =200;
   
   COMMIT;
   

   Note:

   If the data is already loaded then you need to reload it to use the new mapping. Don't attempt to truncate all warehouse tables before doing the reload. Instead use the reset warehouse option in the Configuration Manager. Truncating all warehouse tables truncates the mapping table as well.

Setting Up Key Flex Fields for Financials Fusion Applications Source Data

If applicable, load the financial KFF data for GL#, CAT# and LOC# KFFs into Oracle Business Analytics Warehouse.

These instructions only apply if you're deploying a Fusion Applications cloud data source.

1. Enable and set up the VOs for extraction in Oracle BI Cloud Connector Console. See Using Oracle BI Cloud Connector Console to Configure Cloud Extract.
2. Configure the ODI repository in ODI. See Using ODI to Set Up Key Flex Fields.

Using Oracle BI Cloud Connector Console to Configure Cloud Extract

When you've completed the key flexfield (KFF) setup in Oracle Fusion Applications and deployed the flexfield, view objects (VO) are generated for each segment that you've enabled for Oracle Business Intelligence (BI). Each VO must be seeded and enabled for BI extraction so that it can be loaded into Oracle Business Analytics Warehouse.

To seed and enable VOs for extraction:

1. In Oracle BI Cloud Connector Console, navigate to the Configure Cloud Extract link on the Tasks pane to display the Configure Cloud Extract dialog.
2. Scroll down to the Data Store area.
3. Click Add to display the Add Data Store dialog, specify the details, then click Save and Close.

   Note:

   VO names are case-sensitive.

   You must add VOs in the GL Journals under the Oracle Financial Analytics Offering, as shown in the example screen shot.

   
   Description of the illustration biain_finkff1-gif.gif
4. To enable VOs for extraction, select the parent Offering, Functional Area, FG/DG, or individual VO.
5. Enable and add these VOs for extraction.

   • For the GL# KFF, you must add the BI Flattened VO along with the segment VOs generated for the segment labels mapped to BI Objects in your Fusion setup.

     The BI Flattened VO name for GL# that must be added is FscmTopModelAM.AccountBIAM.FLEX_BI_Account_VI.

   • The VOs generated for segment labels FA_COST_CTR (mapped to Dim – Cost Center), GL_ACCOUNT (mapped to Dim – Natural Account Segment), and GL_BALANCING (mapped to Dim – Balancing Segment) are known prior. You must add these VOs:

     FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_FA_COST_CTR_VI
     FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_FA_COST_CTR_VI
     FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_GL_BALANCING_VI
     FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_GL_BALANCING_VI
     FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_GL_ACCOUNT_VI
     FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_GL_ACCOUNT_VI
     

     Note:

     For these VOs, ensure that you enable all the columns for the select list.

     When you add the TREECODE view objects, you must enable the Disable Effective date filter option. Additionally, ensure that invunitsofmeasurep view object is disabled for Human Capital Management. For Fusion Supply Chain Management and Customer Relationship Management, deploy the INV_UOM_CLASSES descriptive flexfield forinvunitsofmeasurep view object.

   • The VOs generated for any segment label apart from FA_COST_CTR, GL_BALANCING and GL_ACCOUNT, and mapped to the BI Object Dim – GL Segmentx aren't known before hand as the VO names depends on the segment label. Therefore, you must add the VO names based on the naming pattern.

     If the segment is a tree segment (if you've created hierarchies for value sets used for those segments), then the VOs are named:

     FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_<segment label>_VI

     FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_<segment label>_VI

     If the segment is a non-tree segment (if you've NOT created hierarchies for value sets used for those segments), then the VOs are named:

     FscmTopModelAM.AccountBIAM.FLEX_VS_<segment label>_VI

     For example:

     Segment Label	Tree v/s Non Tree	VO Name
     PRODUCT	Tree	FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_PRODUCT_VI FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_PRODUCT_VI
     ORG	Non Tree	FscmTopModelAM.AccountBIAM.FLEX_VS_ORG_VI

     Note:

     When you add TREECODE VOs, you must enable the Disable Effective date filter option.

     For the CAT# and LOC# KFFs, you need to add the BI Flattened VO for each KFF.

     The BI Flattened VO name for CAT# that needs to be added is FscmTopModelAM.CategoryBIAM.FLEX_BI_Category_VI. The BI Flattened VO name for LOC# that needs to be added is FscmTopModelAM.LocationBIAM.FLEX_BI_Location_VI.

   • For Units of Measure (UOM) extensions, add the FscmTopModelAM.InvUomPublicViewAM.InvUnitsOfMeasurePVO view object.

   Once you've added these VOs and completed the extraction process, the data files for these VOs are downloaded into the physical location configured for replication stage files logical schema in ODI (Fusion 9: DS_FUSION_9_0_REPLSTG_FILES, Fusion 10: DS_FUSION_10_0_REPLSTG_FILES).

   The files generated for GL# segment labels mapped to Dim – GL Segmentx (Dim – GL Segment 1-10) have corresponding pre-seeded data stores using a generic naming convention in ODI. The next step is to rename the corresponding files with appropriate file names so that they can load the corresponding data stores.

   The mapping between the files generated and the new file names corresponding to the data stores is based on the segment label to BI Object mapping and setup for that segment (tree versus non-tree).

   Taking the same example as mentioned in the previous steps, – PRODUCT label is mapped to Dim – GL Segment 1 and is a tree segment, and ORG label is mapped to Dim – GL Segment2 and is a non tree segment, then the mapping between the generated files and the new files are:

   File Generated	New File Name
   File_FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_PRODUCT_VI	File_FscmTopModelAM.AccountBIAM.FLEX_TREE_VS_GL_SEGMENT1_VI
   File_FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_PRODUCT_VI	File_FscmTopModelAM.AccountBIAM.FLEX_TREECODE_VS_GL_SEGMENT1_VI
   File_FscmTopModelAM.AccountBIAM.FLEX_VS_ORG_VI	File_FscmTopModelAM.AccountBIAM.FLEX_VS_GL_SEGMENT2_VI

   This mapping has to be provided in a configuration file named FinKFFFileRename.cfg, which is used in the downstream processes to load the data from those files.

6. Create and save this configuration file in the same location with all the data files generated in this procedure.

   This configuration file has to be placed in the replication staging location in the ODI environment (the location where the files are copied and placed from UCM to ODI).

   The configuration file has to be created as a comma delimited file, and the format of the entries in the file has to be as shown in this sample entry. Save the file when you're done making the entries.

   <Generated File Name>,<New File Name based on the pre seeded data store>

   A sample entry in the file would look like this:

   file_fscmtopmodelam_accountbiam_flex_vs_gl_management_vi,file_fscmtopmodelam_accountbiam_flex_vs_gl_segment2_vi
   

   Create the configuration file in the same platform (Windows or Linux) where you'll eventually save this file. Avoid copy and paste from one platform to the other. This avoids issues regarding special characters in text files when crossing different platforms.

Using ODI to Set Up Key Flex Fields

The BI (business intelligence) flattened VO (view object) generated for each key flexfield (KFF) has columns relating to each segment label. Use this procedure to set up the mappings for these columns.

1. For CAT# KFF, check the csv file generated for the BI flattened VO for the list of additional columns for each segment - file_fscmtopmodelam_categorybiam_flex_bi_category_vi%.csv.

   These segment columns end with “_” or “_c”. For example, BASED_CATEGORY_, MINOR_CATEGORY_.

   You must add these new columns in the file data store and the VO data store in ODI.

   Navigate to the file data store to add the new columns.
   Description of the illustration 103ps1-set-kff-step1_1.gif
   Description of the illustration 103ps1-set-kff-step1_2.gif
2. Add the new columns to the FILE_FSCMTOPMODELAM_CATEGORYBIAM_FLEX_BI_CATEGORY_VI data store with the default data type of String (50,50) for all columns.
   
   Description of the illustration 103ps1-set-kff-step2.gif

   For LOC# KFF, check the CSV file generated for the BI flattened VO for the list of additional columns for each segment - file_fscmtopmodelam_locationbiam_flex_bi_location_vi%.csv. These segment columns end with “_” or “_c”. The corresponding file data stores for LOC# KFF is FILE_FSCMTOPMODELAM_LOCATIONBIAM_FLEX_BI_LOCATION_VI.

3. Repeat the configuration steps for the corresponding VO data stores in ODI.

   The VO data stores are in the path shown in the image. Use the default data type of Varchar(50, 50).

   • CAT# KFF VO data store: FscmTopModelAM.CategoryBIAM.FLEX_BI_Category_VI

   • LOC# KFF VO data store: FscmTopModelAM.LocationBIAM.FLEX_BI_Location_VI

   
   Description of the illustration 103ps1-set-kff-step3_1.gif

   Scroll down to locate the VO data stores.
   Description of the illustration 103ps1-set-kff-step3_2.gif
   Description of the illustration 103ps1-set-kff-step3_3.gif

4. For the newly added columns in both the file data store and VO data store, set the flexfield value for OBI SDS Column Short Name.

   Ensure that the flexfield value is the same as the column name. Also, ensure that you set the flexfield value ODI Populate Column to Y in SDS for these columns.

   These images display example flexfield values.

   For example, CAT# KFF File Data Store Column:
   Description of the illustration 103ps1-set-kff-step4_1.gif

   For example, CAT# KFF VO Data Store Column:
   Description of the illustration 103ps1-set-kff-step4_2.gif

5. Repeat for LOC# KFF.
6. Execute GENERATE_SDS_DDL in INCR_REFRESH_MODE.

   This process updates the SDS table to include the new extended columns.

7. When you have added the columns in the appropriate data stores, map the columns in the corresponding ODI mappings to load the data.
8. For the CAT# KFF, edit the FTS mapping located under the SDE_FUSION_V1_ADAPTOR folder to map these new columns.
   
   Description of the illustration 103ps1-set-kff-step8.gif
9. Create a one-to-one mapping between the segment columns in FTS_FUSION_FscmTopModelAM.AccountBIAM.FLEX_BI_Account_VI.
   
   Description of the illustration 103ps1-set-kff-step9.gif
10. Save the changes, then regenerate the underlying scenario for the package.
11. Similarly, if you have LOC# KFF, edit the corresponding FTS mapping to map the new columns:

    LOC# KFF FTS mapping: FTS_FUSION_FscmTopModelAM.LocationBIAM.FLEX_BI_Location_VI.

12. Save the changes and regenerate the underlying scenarios for the packages.
13. Edit the SDE mapping for CAT# KFF to map these new columns to corresponding columns in the staging table.

    The SDE mapping is located in the same SDE_FUSION_V1_Adaptor folder.
    Description of the illustration 103ps1-set-kff-step13_1.gif

    The column mapping is based on the segment label to BI Object mapping done in your Fusion Applications configuration.

    For CAT# KFF, if you have mapped BASED_CATEGORY and MINOR_CATEGORY then you can use them as the Major and Minor category.
    Description of the illustration 103ps1-set-kff-step13_2.gif

14. Save the changes and regenerate the underlying scenario for the package.
15. If applicable, complete similar steps for LOC# KFF based on the columns that you extend for these:

    • SDE mapping: SDE_FUSION_FixedAssetLocationDimension

    • Staging table: W_ASSET_LOCATION_DS

Setting Up Key Flex Fields for HCM Fusion Applications Source Data

If applicable, load the HCM KFF data mentioned in this topic into Oracle Business Analytics Warehouse.

These instructions only apply if you're deploying a Fusion Applications cloud data.

When you've completed the KFF setup in Fusion and deployed the Flexfield, VOs are generated for each segment that you've enabled for BI. Each VO must be seeded and enabled for BI extraction so that it can be loaded into Oracle Business Analytics Warehouse.

To set up key flex fields for HCM Fusion applications source date:

1. Use Oracle BI Cloud Connector Console to load the View Objects (VOs) listed in Supported View Objects below:

   1. On the Fusion Applications pod, start Oracle BI Cloud Connector Console using a HTTP URL based on the following format: http://<FA OHS Host:<FA OHS Port/biacm

   2. In Oracle BI Cloud Connector Console, select the Configure Cloud Extract link on the Tasks pane to display the Configure Cloud Extract dialog.

      
      Description of the illustration biain_hcmkff1-gif.gif

   3. Scroll down to the Data Store area.

   4. For each of the View Objects (VOs) listed in the Supported View Objects table below, click the Add icon (+) to display the Add Data Store dialog and create a new data store.

      
      Description of the illustration biain_hcmkff2-gif.gif

   Note:

   FscmTopModelAM.InvUomPublicViewAM.InvUnitsOfMeasurePVO view object could fail if you haven't deployed the INV_UOM_CLASSES flexfield. If you encounter a failure, then disable this view object for Human Capital Management using Oracle BI Cloud Connector Console.

   The next scheduled Cloud Extract executed by Oracle BI Cloud Connector Console extracts these VOs and generates files as required by you. Then, the next scheduled load plan executed by Configuration Manager downloads the newly generated FLEX files and loads the flexfield changes into the Oracle Business Analytics Warehouse.

Supported View Objects

Presentation Table Name in Fusion Applications	Target Table	Model Name	VO Name
Assignment Extensible Attributes	W_HR_ASSIGNMENT_DS/D	Dim – HR Assignment	HcmTopModelAnalyticsGlobalAM.BaseWorkerAsgDFFBIAM.FLEX_BI_BaseWorkerAsgDFF_VI
Assignment History Extensible Attributes	W_HR_ASSIGN_ADDL_D	Dim – HR Assignment History	HcmTopModelAnalyticsGlobalAM.BaseWorkerAsgDFFBIAM.FLEX_BI_BaseWorkerAsgDFF_VI HcmTopModelAnalyticsGlobalAM.BaseWorkerAsgLegDDFBIAM.FLEX_BI_BaseWorkerAsgLegD DF_VI HcmTopModelAnalyticsGlobalAM.WorkRelationshipDFFBIAM.FLEX_BI_WorkRelationshipDFF_VI HcmTopModelAnalyticsGlobalAM.WorkRelationshipLegDDFBIAM.FLEX_BI_WorkRelationsh ipLegDDF_VI HcmTopModelAnalyticsGlobalAM.ContractDFFBIAM.FLEX_BI_ContractDFF_VI HcmTopModelAnalyticsGlobalAM.ContractLegDDFBIAM.FLEX_BI_ContractLegDDF_VI
Person Extensible Attributes	W_HR_PERSON_DS/D	Dim – HR Person	HcmTopModelAnalyticsGlobalAM.PersonsDFFBIAM.FLEX_BI_PersonsDFF_VI HcmTopModelAnalyticsGlobalAM.PersonDetailsDFFBIAM.FLEX_BI_PersonDetailsDFF_VI HcmTopModelAnalyticsGlobalAM.PersonTypeUsagesDFFBIAM.FLEX_BI_PersonTypeUsagesD FF_VI
Person Extensible Attributes	W_HR_PERSON_LEG_DS/D	Dim – HR Person Legislation	HcmTopModelAnalyticsGlobalAM.PersonLegislativeInfoDFFBIAM.FLEX_BI_PersonLegislativeInfoDFF_VI HcmTopModelAnalyticsGlobalAM.CitizenshipDFFBIAM.FLEX_BI_CitizenshipDFF_VI HcmTopModelAnalyticsGlobalAM.EthnicityDFFBIAM.FLEX_BI_EthnicityDFF_VI HcmTopModelAnalyticsGlobalAM.PersonLegDDFBIAM.FLEX_BI_PersonLegDDF_VI HcmTopModelAnalyticsGlobalAM.PersonNameDFFBIAM.FLEX_BI_PersonNameDFF_VI HcmTopModelAnalyticsGlobalAM.PersonNameLegDDFBIAM.FLEX_BI_PersonNameLegDDF_VI HcmTopModelAnalyticsGlobalAM.ReligionDFFBIAM.FLEX_BI_ReligionDFF_VI HcmTopModelAnalyticsGlobalAM.PersonVisaLegDDFBIAM.FLEX_BI_PersonVisaLegDDF_VI HcmTopModelAnalyticsGlobalAM.VisaPermitDFFBIAM.FLEX_BI_VisaPermitDFF_VI
Position Extensible Attributes	W_HR_POSITION_DS/D	Dim – HR Position	HcmTopModelAnalyticsGlobalAM.PositionCustomerFlexBIAM.FLEX_BI_PositionCustomerFlex_VI
Pay Grade Extensible Attributes	W_PAY_GRADE_DS/D	Dim – Pay Grade	HcmTopModelAnalyticsGlobalAM.GradeCustomerFlexBIAM.FLEX_BI_GradeCustomerFlex_VI
Job Extensible Attributes	W_JOB_DS/D	Dim – Job	HcmTopModelAnalyticsGlobalAM.JobCustomerFlexBIAM.FLEX_BI_JobCustomerFlex_VI
Location Extensible Attributes	W_BUSN_LOCATION_DS/D	Dim - Worker Location	HcmTopModelAnalyticsGlobalAM.LocationCustomerFlexBIAM.FLEX_BI_LocationCustomerFlex_VI
Department Extensible Attributes	W_INT_ORG_DS/D	Dim - Department
Payroll Extensible Attribute	W_PAY_PAYROLL_D	Dim - Payroll Details	HcmTopModelAnalyticsGlobalAM.AllPayrollsDDFBIAM.FLEX_BI_AllPayrollsDDF_VI
Candidate Extensible Attributes	W_SCCN_CANDIDATE_D	Dim - Succession Candidate	HcmTopModelAnalyticsGlobalAM.PlanCandidateDFFBIAM.FLEX_BI_PlanCandidateDFF_VI
Workforce Event Type Extensible Attributes	W_WRKFC_EVENT_TYPE_D W_WRKFC_EVNT_ADDL_D W_WRKFC_EVNTRSN_ADDL_D	Dim - HR Workplace Event Type	HcmTopModelAnalyticsGlobalAM.ActionReasonsDFFBIAM.FLEX_BI_ActionReasonsDFF_VI HcmTopModelAnalyticsGlobalAM.ActionsDFFBIAM.FLEX_BI_ActionsDFF_VI HcmTopModelAnalyticsGlobalAM.ActionsLegDDFBIAM.FLEX_BI_ActionsLegDDF_VI
Project Attribute Extension	PROJECT_ADDL_D	Dim - Project	FscmTopModelAM.PJF_PROJECTS_ALLBIAM.FLEX_BI_PJF_PROJECTS_ALL_VI
Task Attribute Extension	TASK_ADDL_D	Dim - Task	FscmTopModelAM.TaskDffBIAM.FLEX_BI_TaskDff_VI
N/A	Employee_ADDL_D	Dim - Employee
N/A	W_UOM_CONVERSION_G	N/A