DAC not populating FACT table for the GL module - W_GL_OTHER_F (zero rows)

Question

All - We did our FULL loads from the Oracle Financials 11i into OBAW and got data in most of the dimension tables populated. HOWEVER, i am not seeing anything populating into the fact table W_GL_OTHER_F (zero rows). Following is a list of all dims / facts i am focusing towards for the GL module.
W_BUSN_LOCATION_D     (8)
W_COST_CENTER_D     (124)
W_CUSTOMER_FIN_PROFL_D     (6,046)
W_CUSTOMER_LOC_D     (4,611)
W_CUSTOMER_LOC_D     (4,611)
W_CUSTOMER_LOC_D     (4,611)
W_DAY_D     (11,627)
W_DAY_D     (11,627)
W_DAY_D     (11,627)
W_GL_ACCOUNT_D     (28,721)
W_INT_ORG_D     (171)
W_INVENTORY_PRODUCT_D     (395)
W_LEDGER_D     (8)
W_ORG_D     (3,364)
W_PRODUCT_D     (21)
W_PROFIT_CENTER_D     (23)
W_SALES_PRODUCT_D     (395)
W_STATUS_D     (7)
W_SUPPLIER_D     (6,204)
W_SUPPLIER_PRODUCT_D     (0)
W_TREASURY_SYMBOL_D     (0)
W_GL_OTHER_F <------------------------------------- NO FACT DATA AT ALL
Question for the group: Are there any specific settings which might be preventing us from getting data loaded into our FACT tables? I was doing research and found the following on the internet:
Map Oracle General Ledger account numbers to Group Account Numbers using the following file file_group_acct_names_ora.csv. Is this something that is necessary?
Any help / guidance / pointers are greatly appreciated.
Regards,

Answer 1

There are many things to configure before your first full load.
For the configuartion steps see Oracle Business Intelligence Applications Configuration Guide for Informatica PowerCenter Users
- http://download.oracle.com/docs/cd/E13697_01/doc/bia.795/e13766.pdf (7951)
- http://download.oracle.com/docs/cd/E14223_01/bia.796/e14216.pdf (796)
3 Configuring Common Areas and Dimensions
3.1 Source-Independent Configuration Steps
Section 3.1.1, "How to Configure Initial Extract Date"
Section 3.1.2, "How to Configure Global Currencies"
Section 3.1.3, "How to Configure Exchange Rate Types"
Section 3.1.4, "How to Configure Fiscal Calendars"
3.2 Oracle EBS-Specific Configuration Steps
Section 3.2.1, "Configuration Required Before a Full Load for Oracle EBS"
Section 3.2.1.1, "Configuration of Product Hierarchy (Except for GL, HR Modules)"
Section 3.2.1.2, "How to Assign UNSPSC Codes to Products"
Section 3.2.1.3, "How to Configure the Master Inventory Organization in Product Dimension Extract for Oracle 11i Adapter (Except for GL & HR Modules)"
Section 3.2.1.4, "How to Map Oracle GL Natural Accounts to Group Account Numbers"
Section 3.2.1.5, "How to make corrections to the Group Account Number Configuration"
Section 3.2.1.6, "About Configuring GL Account Hierarchies"
Section 3.2.1.7, "How to set up the Geography Dimension for Oracle EBS"
Section 3.2.2, "Configuration Steps for Controlling Your Data Set for Oracle EBS"
Section 3.2.2.1, "How to Configure the Country Region and State Region Name"
Section 3.2.2.2, "How to Configure the State Name"
Section 3.2.2.3, "How to Configure the Country Name"
Section 3.2.2.4, "How to Configure the Make-Buy Indicator"
Section 3.2.2.5, "How to Configure Country Codes"
5.2 Configuration Required Before a Full Load for Financial Analytics
Section 5.2.1, "Configuration Steps for Financial Analytics for All Source Systems"
Section 5.2.2, "Configuration Steps for Financial Analytics for Oracle EBS"
Section 5.2.2.1, "About Configuring Domain Values and CSV Worksheet Files for Oracle Financial Analytics"
Section 5.2.2.2, "How to Configure Transaction Types for Oracle General Ledger and Profitability Analytics (for Oracle EBS R12)"
Section 5.2.2.3, "How to Configure Transaction Types for Oracle General Ledger and Profitability Analytics (for Oracle EBS R11i)"
Section 5.2.2.4, "How to Specify the Ledger or Set of Books for which GL Data is Extracted"
5.3 Configuration Steps for Controlling Your Data Set
Section 5.3.1, "Configuration Steps for Financial Analytics for All Source Systems"
Section 5.3.2, "Configuration Steps for Financial Analytics for Oracle EBS"
Section 5.3.2.1, "How GL Balances Are Populated in Oracle EBS"
Section 5.3.2.2, "How to Configure Oracle Profitability Analytics Transaction Extracts"
Section 5.3.2.3, "How to Configure Cost Of Goods Extract (for Oracle EBS 11i)"
Section 5.3.2.4, "How to Configure AP Balance ID for Oracle Payables Analytics"
Section 5.3.2.5, "How to Configure AR Balance ID for Oracle Receivables Analytics and Oracle General Ledger and Profitability Analytics"
Section 5.3.2.6, "How to Configure the AR Adjustments Extract for Oracle Receivables Analytics"
Section 5.3.2.7, "How to Configure the AR Schedules Extract"
Section 5.3.2.8, "How to Configure the AR Cash Receipt Application Extract for Oracle Receivables Analytics"
Section 5.3.2.9, "How to Configure the AR Credit-Memo Application Extract for Oracle Receivables Analytics"
Section 5.3.2.10, "How to Enable Project Analytics Integration with Financial Subject Areas"
Also, another reason I had was that if you choose not to filter by set of books/type then you must still include the default values set of books id 1 and type NONE in the list on the DAC parameters (this is a consequence of strange logic in the decode statements for the sql in the extract etl).
I would recomend you run the extract fact sql prior to running your execution plan to sanity check how many rows you expect to get. For example, to see how many journal lines, use informatica designer to view mapplet SDE_ORA11510_Adaptor.mplt_BC_ORA_GLXactsJournalsExtract.2.SQ_GL_JE_LINES.3 in mapping SDE_ORA11510_Adaptor.SDE_ORA_GLJournals then cut paste the SQL to run your favourite tool such as sqldeveloper. You will have to fill in the $$ variables yourself.