This is a continuation of articles under OBIA.In the previous article I had mentioned about domain load. Once the domain load is complete the next step is to complete the set of tasks for the implementation module selected. This can be accomplished either through BIACM or FSM.
Some of the important configurations to be completed for financials are:
Data load Parameters
Data load parameters are used to control the nature of data loaded from the transactional system into the Business Analytics Warehouse. Fo financial analytics implementation 3 keys configurations are :
FSG enabled
Oracle provides the FSG hierarchy dimensions and you can view it from the seeded RPD in BMM layer.If you are not planning to load the FSG tables (GL Hierarchy tables) it is advisable to leave this option set to N. If not data load will take much longer to complete with FSG enabled. Some of the tables loaded for FSG are:
W_GL_ACCOUNT_DH
W_ORA_GL_HIER_AXCONTENT_DH_TMP
W_ORA_GL_HIER_DH_TMP
W_ORA_GL_HIER_NORM_HIER_DH_TMP
W_ORA_GL_HIER_RGE_DERV_DH_TMP
W_ORA_GL_HIER_CCID_DH_TMP
W_ORA_GL_HIER_CCID_REF_DH_TMP
The temporary table has to be set to a greater value since the ETL process with FSG consumes more table space.Here is a screen shot of the FSG hierarchy dimension provided by oracle.
Some customizations to RPD and dashboards would be needed to bring over those dimensions to get FSG report in BI.
Fed financial enabled
This option is for federal financials and it is suggested to turn it off if not using since the ETL is going to go over the packages related to Federal financials.
Initial extract date
It determines the date from which the data from the source system has to be loaded into your warehouse tables.
Reporting parameters
Some of the reporting parameters are to be set for financials analytics though it may seem to belong to other modules. This is defined in the task list as well.Master Organization, inventory caterogy set, purchasing category set are some of the reporting columns . If you do not have these setup, during the financial data load fails since product and inventory dimension tables are loaded. Now for such configurations you would need input from your inventory control SMEs.
An important note on Product Category Sets:Product category set having multiple categories assigned for an item is not supported. It causes duplicates in Product Dimensions during data load of financial module.
Domain Mappings and hierarchies
Group Account Configuration.
Domains are pre-seeded dimensional values that help define business metrics. For example, the data in domain Source Group Account (BI_GROUP_ACCOUNT) extracts and loads into the domain Group Account (W_GL_GROUP_ACCOUNT).
Group Account Number Configuration is an important step in the configuration of Financial Analytics, because it determines the accuracy of the majority of metrics in the General Ledger and Profitability module.
Group account to financial statement Item
By mapping your GL accounts against the group account numbers and then associating the group account number to a Financial Statement Item code, you have indirectly associated the GL account numbers to Financial Statement Item codes as well. This association is important to perform GL reconciliation and to ensure the subledger data reconciles with GL journal entries.
For example, when processing a GL journal that charges to a GL account which is associate to 'AP' Financial Statement Item code, then the ETL process will try to go against AP base fact table (W_AP_XACT_F), and try to locate the corresponding matching AP accounting entry. If that GL account is associated with the 'REVENUE' Financial Statement Item code, then the ETL program will try to go against the Revenue base fact table (W_GL_REVN_F), and try to locate the corresponding matching Revenue accounting entry.
Why we cannot extend the target domain codes.
Since BIAPPS product supports multiple source systems – that have a set of values which will cater to all sources and those are the conformed domains. Financial Statement Item codes are internal codes used by the ETL process to process the GL journal records during the GL reconciliation process against the subledgers.
In the next article I will continue on full data load
No comments:
Post a Comment