Oracle® Business Intelligence Applications New Features Guide Version 7.9.6.2 Part Number E16811-01 |
|
|
View PDF |
This chapter contains the following topics:
Oracle BI Applications release 7.9.6.2 extracts JD Edwards EnterpriseOne 'Ledger Type' and maps it into the Ledger Dimension (W_LEDGER_D). This mapping provides:
The ability to filter or segregate data by Ledger Type for reporting and analysis.
New support for consolidation ('AC') and restatement ledgers ('XA'); in addition, to already supported Actuals and Budget ledgers.
Release 7.9.6.1 Supported Ledgers | Release 7.9.6.2 Supported Ledgers | Ledgers Not Supported |
---|---|---|
|
|
|
Table 2-1 and Table 2-2 provide an example of the difference in how records are populated into the Ledger Dimension prior to an after introducing support for Ledger Type. Note the changes for the following columns in release 7.9.6.2:
LEDGER_NAME contains the concatenation of Company and Ledger Type. There will be as many entries for company as there are Ledger Types. For example, assuming there are two Ledger Types (AA and A1) and two Companies (00001 and 00050), LEDGER_NAME will contain the four rows shown in the table once the load process is complete.
LEDGER_CATEGORY_CODE contains Ledger Type.
LEDGER_CATEGORY_NAME contains Ledger Type Name.
Table 2-1 Example of Ledger Dimension Table Prior to Support for Ledger Type
LEDGER_NAME | LEDGER_DESC | CURRENCY_CODE | LEDGER_CATEGORY_CODE | LEDGER_CATEGORY_NAME |
---|---|---|---|---|
00001 |
Fixed Asset Company #2 |
USD |
Null |
Null |
00050 |
SAR TESTING COMPANY |
USD |
Null |
Null |
Table 2-2 Example of Release 7.9.6.2 Ledger Dimension Table with Support for Ledger Type
LEDGER_NAME | LEDGER_DESC | CURRENCY_CODE | LEDGER_CATEGORY_CODE | LEDGER_CATEGORY_NAME |
---|---|---|---|---|
00001~AA |
Fixed Asset Company #2 |
USD |
AA |
Actuals |
00001~A1 |
Fixed Asset Company #2 |
USD |
A1 |
User Defined Actuals |
00050~AA |
SAR TESTING COMPANY |
USD |
AA |
Actuals |
00050~A1 |
SAR TESTING COMPANY |
USD |
A1 |
User Defined Actuals |
Dashboard prompts defined during the Financial Analytics configuration process will not require any additional changes because Ledger Name will display the new concatenated Ledger Name ("Company~Ledger Type") values.
Note:
LEDGER_CATEGORY_NAME and LEDGER_CATEGORY_CODE can be exposed as Dashboard prompts with a few modifications to the original product configuration:LEDGER_CATEGORY_NAME is already available in the Presentation Subject Area as part of the Ledger Dimension. Therefore, all that is needed is to define LEDGER_CATEGORY_NAME as a prompt for the required Dashboard page or pages.
LEDGER_CATEGORY_CODE is available in the RPD Business Model and Mapping (BMM) layer. Therefore, before defining as a Dashboard Page prompt, you will need to expose within the RPD Presentation Subject Area, as a member of the Ledger Dimension.
The following table summarizes the availability of each column across each area after the standard product configuration and associated action needed to define as a Dashboard page prompt.
Ledger Dimension Column | Dashboard Prompt | Presentation Subject Area | RPD BMM Layer | Action to Define as Dashboard Page Prompt |
---|---|---|---|---|
LEDGER_NAME | Yes | Yes | Yes | None. Already available as a Dashboard prompt. |
LEDGER_CATEGORY_NAME | No | Yes | Yes | Define as prompt in Dashboard Page. |
LEDGER_CATEGORY_CODE | No | No | Yes |
|
The ETL map is run by passing the Ledger Type value through DAC as comma separated values. By default, the value for Ledger Type is AA.
To run the ETL map for the new supported Ledger types, consolidation ('AC') and restatement ledgers ('XA'), the DAC Source System Parameter $$LEDGER_TYPES should include the required Ledger Types as comma separated values: 'AA', 'XA', 'AC'.
For more detailed instructions on running the ETL maps, refer to the Oracle® Business Intelligence Applications documentation.