Implementing GL Segment, GL Account, Asset Category and Asset Location Dimensions for Oracle Fusion Applications
You can implement GL Segment and GL Segment Hierarchy Dimensions.
Guidelines
-
If you need to report on only concatenated segments, then no configuration is required, and you can skip this section.
-
If you want only Group Account Num (and related attributes), then at a minimum you need to configure just the Natural Account dimension.
-
If you are exposing any GL Segments (including cost center, balancing segment, natural account), then you must go through the full configuration.
-
If you are exposing any Financial fact, then at a minimum you need to configure the Natural Account dimension, because you need group account number.
Mapping the GL Segment Labels to BI Objects in Oracle Fusion Applications
To enable GL Accounting Flexfield in Oracle BI Applications, sue the Manage Key Flexfields UI in Oracle Fusion Applications to configure the Accounting Flex Segments for BI and provide the mapping with BI Object names that should be used as dimensions for each of the Account Flexfield segments.
- For General Ledger, in each of the Accounting Flexfield segments, set the BI Enabled Flag to Y.
- Edit each of the segments and select the BI enabled check box, then save the details.
This should be done for all segments in every Structure instance that you intend to be mapped in the BI metadata repository (that is, the RPD file).
- Edit each of the segments and select the BI enabled check box, then save the details.
- Populate the BI Object Name for each of the Segment Labels.
This name is the Logical table name in the BI metadata repository (that is, the RPD file) that is used as the dimension for the corresponding segment.
- Choose Actions, then Manage Segment Labels.
- Populate the BI Object Name for all the segment labels that you need to map in the repository, then save the details.
The following table shows the BI Object Names for each Qualified Segment label.
Segment Label Code BI Object Name FA_COST_CTR
Dim - Cost Center
GL_BALANCING
Dim - Balancing Segment
GL_ACCOUNT
Dim - Natural Account Segment
For the non qualified segment labels, the BI Object Name should be populated with one of the 10 numbered Dim - Segments: Dim - GL Segment1, Dim - GL Segment2, Dim - GL Segment<n>, and so on, to Dim - GL Segment10.
Mapping the Asset Segment Labels to BI Objects in Oracle Fusion Applications
You can map the Assets segment labels to BI Objects in Oracle Fusion Applications.
- For Assets, in each of the Accounting Flexfield segments, set the BI Enabled Flag to Y.
- Edit each of the segments and select the BI enabled check box, then save the details.
This should be done for all segments in every Structure instance that you intend to be mapped in the BI metadata repository (that is, the RPD file).
- Edit each of the segments and select the BI enabled check box, then save the details.
- Populate the BI Object Name for each of the Segment Labels.
This name is the Logical table name in the BI metadata repository (that is, the RPD file) that is used as the dimension for the corresponding segment.
- Choose Actions, then Manage Segment Labels.
- Populate the BI Object Name for all the segment labels that you need to map in the BI metadata repository (that is, the RPD file), then save the details.
For the "qualified" segment labels, use the following BI Object Names for each Qualified Segment label:
Segment Label Code BI Object Name BASED_CATEGORY
Major Category
MINOR_CATEGORY
Minor Category
For all other segment labels, use any of the following values: Segment1, Segment2, and so on, to Segment10
For BI Object Names for "Fixed Asset Location (LOC#)" Key Flex Field, for all segment labels, use Segment1, Segment2, and so on, to Segment7.
Configuring GL Account, Asset Location, and Asset Category
If your Fusion applications are deployed on premises, then load the financial key flexfield data for GL account, asset location, and asset category key flexfields into Oracle Business Analytics Warehouse.
The BI flattened VO generated for each key flexfield has columns pertaining to each segment label. These columns are generated after deployment and hence there is no out of the box mapping for these columns downstream. Hence, you need to make changes to the necessary ODI artifacts to map those columns.
To configure GL account, asset location, and asset category, you need to complete the following ODI changes:
- These segment columns end with
_or_c. For example,FA_COST_CTR_andFA_COST_CTR_c,PRODUCT_andPRODUCT_c. Once you have identified them, you must add these new columns in the corresponding VO data store in ODI.. Use the default data type of Varchar (50,50). Ensure that you add them to the data stores for the appropriate Fusion release that you are using. - Edit the SDE mapping for
GL# KFFto map these new columns to the corresponding columns in the staging table.The SDE mapping is located in the appropriate Fusion folder based on the release you are on. For example, SDE_FUSION_11_Adaptor
The column mapping is based on the segment label to BI Object mapping done in your Fusion setup. For example, assuming that you have mapped PRODUCT label toDim – GL Segment1and ORG label toDim – GL Segment2,then the column mapping will look like:For example, assuming that you have mapped ALTACCT label toDim – GL Segment3and GL_MANAGEMENT label toDim – GL Segment5, then the column mapping will look like: - If applicable, make equivalent updates for CAT# and LOC#.
The corresponding mappings for both are as follows:
-
CAT# KFF
-
SDE mapping:
SDE_FUSION_FixedAssetCategoryDimension -
Staging table:
W_ASSET_CATEGORY_DS
-
-
LOC# KFF
-
SDE mapping:
SDE_FUSION_FixedAssetLocationDimension -
Staging table:
W_ASSET_LOCATION_DS
-
For CAT#KFF, if you have mapped BASED_CATEGORY and MINOR_CATEGORY and would like to use them as the Major and Minor Category, then the column mapping is:-
MAJOR_CATEGORY: FLEXVO.BASED_CATEGORY_
-
MINOR_CATEGORY: FLEXVO.MINOR_CATEGORY_
-
