Known Issues for Oracle Fusion Analytics Warehouse

Learn about the issues you may encounter when using Oracle Fusion Analytics Warehouse and how to work around them.

Topics:

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Oracle Fusion Analytics Warehouse General Issues and Workarounds

Learn about the general issues you may encounter when using Oracle Fusion Analytics Warehouse and how to work around them.

Topics:

Issue with Failed Status for Renamed Custom Dimensions

When you edit an Add Dimension step, the current and subsequent steps enter into a failed status.

To work around this issue, delete the step and create it again.

Unable to Save Projects Prebuilt Analyses

You can't save the Projects prebuilt analyses (Project Cost Analysis, Project Cost Account Analysis, Cost Account Analysis by Project) because of incorrect security permissions. To fix this issue, a service administrator needs to update the analysis security permissions from view access to edit access.

  1. Log in as a user with the ServiceAdmin role.
  2. Navigate to the Catalog page, then navigate to the analysis you want to edit, right-click, and select Inspect.
  3. Click Share, and for each duty role you want to provide edit access to, select Edit.
  4. Click Save.

After you make this change, users with the duty roles assigned to the analysis can see, edit, and save the analysis.

Known Issues for Oracle Fusion ERP Analytics

Oracle Fusion ERP Analytics has a number of known issues.

Topics:

Aggregation of YTD Metrics Is Incorrect in Certain Scenarios

If you're aggregating YTD metrics across ledgers for a quarter and in one ledger, the last period of the quarter isn't open, then the aggregation won't include the metrics from that ledger.

In this example, Period 1, Period 2, and Period 3 exist in Quarter 1. Ledger A and Ledger B have balances for all three periods. Period 3 in Ledger C isn't open and shows no balance.

In this example, YTD Revenue for Quarter 1 across three ledgers shows as 16500 instead of 22500. If you aggregate by Ledger or Period, you obtain the correct balance.

Quarter Period Revenue YTD Ledger Name
Quarter1 Period1 3000 Ledger A
Quarter1 Period2 7000 Ledger A
Quarter1 Period3 10000 Ledger A
Quarter1 Period1 2500 Ledger B
Quarter1 Period2 5000 Ledger B
Quarter1 Period3 6500 Ledger B
Quarter1 Period1 4000 Ledger C
Quarter1 Period2 6000 Ledger C

Issue with Latest Payables Invoice Validation Status

The Incremental run in Fusion Analytics Warehouse depends on LAST_UPDATE_DATE. For certain scenarios when the APPROVAL_STATUS column in the AP_INVOICES_ALL table is updated, Fusion Analytics Warehouse doesn't update the LAST_UPDATE_DATE. APPROVAL_STATUS is mapped to Validation status. Because the LAST_UPDATE_DATE isn't changed, the incremental run doesn't fetch those changes and transfer them to the warehouse tables.

This issue doesn't currently have a workaround.

Receivables Invoice with In Arrears Invoicing Rule and Receivables Accounting in a Future Period Displays the Incorrect Transaction and Line Amount

The AR Revenue subject area has distribution accounting entries for Receivables transactions that are accounted. For transactions with the In Arrears invoicing rule, receivables accounting is generated at the end of the revenue recognition schedule. Transaction Amount and Line Amount for such transactions display the amounts based on the revenue that's recognized and the unrecognized revenue isn't included.

This issue doesn't currently have a workaround.

Can't Display Data in AP and AR Subject Areas if the Primary Ledger Isn't Selected in the Reporting Configuration

The AR and AP subject areas are secured by the Business Unit, which is linked to the Primary Ledger. If you select only the Secondary Ledger without the corresponding Primary Ledger in the Reporting configuration, then the Business Unit isn't populated in the Security context for the User Security assignment. Therefore, you can't analyze data in the AR and AP subject areas.

To work around this issue, select the Primary Ledger in the Reporting configuration.

Receipt Accounting Date Isn't Populated for Some of the Miscellaneous Receipt Accounting Distributions

The Receipt Accounting date for some of the Miscellaneous Receipt accounting distributions shows NULL, but the distribution for the CASH accounting class shows the date.

The workaround is to use the Receipt Distribution Accounting Date. This will have the date populated for all accounting distributions.

Asset Transactions Subject Area Doesn't Show Transactions of Tax Books Associated With Non-Primary Ledgers

The Asset Analysis subject area shows the primary ledger even if the tax book is associated with non-primary ledger.

The Asset Transactions subject area doesn't show transactions of tax books associated with non-primary ledgers.

Accounted Raw Cost, Accounted Burden Cost, and Accounted Burdened Cost Metrics Show a Value of Zero

Accounted Raw Cost, Accounted Burden Cost, and Accounted Burdened Cost metrics in the PPM - Projects Costs subject area are used with the GL Account Combination attribute.

If the GL Account Combination attribute isn't included in the Accounted Raw Cost, Accounted Burden Cost, and Accounted Burdened Cost metrics, the Debit and Credit entries negate each other and the metric value shows as zero.

Currency Conversion Rate Type Attributes Show Rate Type ID Data Instead of the User Rate Type Value

In the Projects Costs subject area, the Currency Conversion Rate Type attributes show the Rate Type ID data instead of the User Rate Type value.

This is the expected behavior.

Aggregation of Certain YTD Metrics Is Incorrect in the GL Profitability Subject Area When the Adjustment Period Flag Is Included in the Analysis

If you're analyzing YTD metrics at a quarter or year level, and if you include the adjustment period flag as a filter or attribute, the YTD amounts gets aggregated incorrectly for the Depreciation Expenses YTD, Income Tax Expense YTD, Interest Expense YTD, Other Income YTD, Other Operating Expense YTD, R&D Expense YTD, Sales & Marketing Expense YTD, and Total Operating Expenses YTD metrics in the GL Profitability subject area.

For example, Period 1, Period 2, Period 3, and Adj Period exist in Quarter 1, and the amounts for R&D Expense YTD are as shown below. When you remove the Period attribute and view the Quarter level balance for Quarter 1, you expect to see 10,000. However, it will aggregate the amounts and show 20,000 for Quarter 1 with the Adjustment Period flag set to N, and 10,000 for Quarter 1 with the Adjustment Period flag set to Y.

Quarter Period R&D Expense YTD Adjustment Period Flag
Quarter1 Period1 3000 N
Quarter1 Period2 7000 N
Quarter1 Period3 10000 N
Quarter1 Adj Period 10000 Y

To work around this issue, don't use the Adjustment Filter flag when you're analyzing Quarter- or Year-level balances for YTD metrics.

GL Segment Value of GL Account Shows ~No Value~ If That Segment Value Is Based on a Table-Validated Value Set

If the segment value of Chart of Account is based on a table validated value set, then the Value, Name, and description attributes of that GL Segment show ~No Value~ instead of the actual values.

To work around this issue, examine the segment value using the GL Account Combination attribute.

Intracompany Records Generated for AP Invoice Payments Has Invoice-Related Attributes Populated Randomly

When an AP payment is made against multiple invoices for which SLA generates the Intracompany or Balance records to balance the accounting entries, Fusion Analytics Warehouse associates these accounting entries with attributes related to invoice numbers randomly.

In these cases, Intracompany and Balance records aren't generated specific to the invoice in Fusion. Fusion Analytics Warehouse populates these entries with invoice-related attributes which is incorrect. This issue exists in the GL Account Analysis subject area, and doesn't have a workaround.

Accounting Transactions Related to Reporting Ledger Aren't Shown in the Assets Transactions Subject Area

If a Primary Ledger has an associated Reporting ledger, the accounting transactions of the Reporting Ledger aren't shown in the Assets Transactions subject area.

There's no workaround for this issue.

Drilling Down from Unaccounted Cost Summary to Unaccounted Cost Transactions in Project Cost Account Analysis Visualization Causes an Error

In the Project Cost Account Analysis visualization, drilling down from Unaccounted Cost Summary to Unaccounted Cost Transactions twice causes an error.

When you drill down the first time, the Project Number and Project Name filters apply. When you drill down again without deleting the previously applied filters, you see an error. To work around this issue, delete the old filter and drill down again.

Project Costs and Commitments Subject Areas Show Removed Team Member Records

The Project Costs and Commitments subject areas show records for team members who've been removed.

When you delete team members from a project in Oracle Fusion Cloud Applications, the incremental load doesn't update the records properly. The records update properly during a warehouse update. There isn't another workaround.

AR Aging Subject Area Aging Metrics by Party Dimension Doesn't Include Unapplied Receipts Records

In the AR Aging subject area, the party dimension is anchored to Bill-to Customer, therefore Aging metrics by Party dimension doesn't include the amounts related to Unapplied Receipts.

The Unapplied Receipts records only have Paying Customer values, so the Bill-to Customer value is null. To work around this issue, perform your analysis using the Customer dimension. The Common Customer dimension populates the Bill-to Customer for Transaction records and the Paying Customer for Unapplied Receipt records.

Opening Amount Doesn't Match the Closing Amount of the Prior Period in AR Aging and AP Aging Subject Areas

In the AR Aging and AP Aging subject areas, the Opening Amount doesn't match the prior period Closing amount due to unaccounted applied transactions.

This issue happens because the Closing amount is derived from the Remaining balance of the transaction in Fusion ERP Cloud, which is the amount remaining after considering all application activities. However the Activity amount is calculated in the warehouse using only the accounted transactions. Therefore, if there are application transactions that aren't accounted, these aren't included when calculating the activity amount, which impacts the Opening Amount since Opening Amount is calculated as Closing Amount - Activity Amount. To work around this issue, account all the transactions in Oracle Fusion Cloud Applications and check the amounts after an incremental run.