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.
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.
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
- Issue with Latest Payables Invoice Validation Status
- Receivables Invoice with In Arrears Invoicing Rule and Receivables Accounting in a Future Period Displays the Incorrect Transaction and Line Amount
- Receipt Accounting Date Isn't Populated for Some of the Miscellaneous Receipt Accounting Distributions
- Accounted Raw Cost, Accounted Burden Cost, and Accounted Burdened Cost Metrics Show a Value of Zero
- Currency Conversion Rate Type Attributes Show Rate Type ID Data Instead of the User Rate Type Value
- Aggregation of Certain YTD Metrics Is Incorrect in the GL Profitability Subject Area When the Adjustment Period Flag Is Included in the Analysis
- GL Segment Value of GL Account Shows ~No Value~ If That Segment Value Is Based on a Table-Validated Value Set
- Intracompany Records Generated for AP Invoice Payments Has Invoice-Related Attributes Populated Randomly
- Opening Amount Doesn't Match the Closing Amount of the Prior Period in AR Aging and AP Aging Subject Areas
- Asset Transactions Subject Area Has Inconsistencies
- Incorrect Values for Header Released Amount and Line Released Amount Metrics in the Agreement Subject Area
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.
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.
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.
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.
Asset Transactions Subject Area Has Inconsistencies
In the Asset Transactions subject area, the Invoice Line Type isn't consistent with the source data.
There is no workaround for this issue
Invoice Validation Status Filter Attribute Causes Data Validation Error
When you validate the data of the Total Transaction Amount metric in the AP Invoices subject area, and use the Invoice Validation Status filter attribute, a SOAP SERVER ERROR occurs.
This issue occurs in the Oracle Fusion Cloud Applications versions 22A and 22B.
To work around this issue, don't select the Invoice Validation Status filter in the Data Validation of Total Transaction Amount metric of the AP Invoices Subject area. However you can choose this as a pivot attribute.
Supplier Dimension Shows Inaccurate Number of Parties
The Supplier Dimension Filter in Fusion Analytics Warehouse and the Data Validation tool shows more parties than with the Supplier usage type.
This isn't consistent with Oracle Fusion Cloud Financials. There is currently no workaround.
Incorrect Values for Header Released Amount and Line Released Amount Metrics in the Agreement Subject Area
The Header Released Amount and Line Released Amount metrics in the Agreement Subject Area shows incorrect values due to an error in identifying when the agreement was last updated.
To work around this issue, reset the data pipeline for the Purchase Agreement functional area every weekend. See Reset a Data Pipeline for a Functional Area.
Known Issues for Oracle Fusion SCM Analytics
Oracle Fusion SCM Analytics has this known issue.
Incorrect Values for Header Released Amount and Line Released Amount Metrics in the Agreement Subject Area
The Header Released Amount and Line Released Amount metrics in the Agreement Subject Area shows incorrect values due to an error in identifying when the agreement was last updated.
To work around this issue, reset the data pipeline for the Purchase Agreement functional area every weekend. See Reset a Data Pipeline for a Functional Area.
Known Issues for Oracle Fusion CX Analytics
Learn about the issues you may encounter when using Oracle Fusion CX Analytics and how to work around them.
Topics:
- Data Deleted in Fusion Application Shows in Fusion Analytics Warehouse
- Activity Count Shows an Incorrect Value When Any Recurring Appointment Changes
- Revenue Line Amount Shows an Incorrect Value When Quantity, UnitPrice, and Revenue Amount Updates with the Addition of a Split Line
- Opportunity Quotes Subject Area Shows Quote for a Deleted Opportunity
- Issue with Custom Fixed Choice List, Custom Dynamic Choice List, and CLOB Extension Attributes
- INDUSTRY_CLASS_CATEGORY Field Shows Old Value
- Subscription Invoice Amount Shows Incorrect Value After Changes
- Corporate/CRM Currency May Show Old Corporate Currency Code
- Renewed Subscriptions Many Not Show Renewed Date
Data Deleted in Fusion Application Shows in Fusion Analytics Warehouse
When records such as Opportunity, Revenue Line. etc., are deleted in the Fusion source application. the deleted objects aren't deleted from Fusion Analytics Warehouse.
This scenario shows a data mismatch between the Fusion Analytics application and Fusion Analytics Warehouse.
To work around the issue, the reset the warehouse (see Reset the Data Warehouse) and reload the data pipeline (see Reload a Data Pipeline for a Functional Area).
Activity Count Shows an Incorrect Value When Any Recurring Appointment Changes
When a recurring meeting is updated, for example increasing or decreasing the number of recurrences or other changes, then the Last Update Date column isn't updated in the Activity and the Activity Resource tables.
The Incremental run in Fusion Analytics Warehouse depends on Last Update Date. Because the date isn't changed, the incremental run doesn't fetch those changes and transfer them to the warehouse tables.
To work around the issue, the reset the warehouse (see Reset the Data Warehouse) and reload the data pipeline (see Reload a Data Pipeline for a Functional Area).
Revenue Line Amount Shows an Incorrect Value When Quantity, UnitPrice, and Revenue Amount Updates with the Addition of a Split Line
When a Revenue Line is Split, and Quantity, Unit Price, and Revenue Amount are also updated at the same time and saved, the Last Updated Date doesn't update, so the updated Revenue Line related details aren't read by the warehouse.
The Incremental run in Fusion Analytics Warehouse depends on Last Update Date. Because the date isn't changed, the incremental run doesn't fetch those changes and transfer them to the warehouse tables.
To work around the issue, the reset the warehouse (see Reset the Data Warehouse) and reload the data pipeline (see Reload a Data Pipeline for a Functional Area).
Opportunity Quotes Subject Area Shows Quote for a Deleted Opportunity
When an Opportunity is deleted, the Quotes table still has a reference to the deleted Opportunity, therefore it's still considered a valid Opportunity Quote.
To work around this issue, for reports built using the CX-Opportunity Quotes subject area, include a fact or any attribute from an Opportunity or other dimension.
Issue with Custom Fixed Choice List, Custom Dynamic Choice List, and CLOB Extension Attributes
The custom attributes created for an object are added to the warehouse using the Data Augmentation feature.
For the custom fields of type Fixed Choice List (FCL), Dynamic Choice List (DCL), CLOB, the field labels don't show up.
- Add the column to the dimension using data augmentation.
- Create a new logical column based on step 1 using a semantic model extension.
- Hide the column created in step 1 using the semantic model extension security framework.
Note:
Use the Oracle CX Sales Application Composer Confiuration Report for information about customer fields, their physcial column names, and their labels. See How to View Application Composer Changes in Cloud Customizing Sales.INDUSTRY_CLASS_CATEGORY Field Shows Old Value
The INDUSTRY_CLASS_CATEGORY field populates when a new Lead is created and the value is set in the profile option: MOT_INDUSTRY_CLASS_CATEGORY.
When this profile option changes, and an existing Lead with an old Industry Classification value updates, the database still saves an incorrect older code against the INDUSTRY_CLASS_CATEGORY.
This issue doesn't currently have a workaround..
Subscription Invoice Amount Shows Incorrect Value After Changes
A subscription invoice amount may show an incorrect value when changes are made to the invoice after it's first generated.
When the billing lines are updated in existing subscriptions invoices, however the last updated date doesn't change in the system. Therefore, the changes aren't updated in the warehouse.
To work around the issue, the reset the warehouse (see Reset the Data Warehouse) and reload the data pipeline (see Reload a Data Pipeline for a Functional Area).
Corporate/CRM Currency May Show Old Corporate Currency Code
If the corporate or CRM currency is changed in Fusion Applications, then the data created with the older corporate currency continues to show values with the original corporate currency code in Oracle Fusion CX Analytics.
For example, you create opportunities in Oracle CX Sales with the corporate currency of US dollars. If the corporate currency changes to euros, and the Oracle Fusion CX Analytics report uses facts from the CX Currency folder, then Oracle Fusion CX Analytics shows older opportunities in US dollars and newer opportunities in euros.
To work around this issue, set the analytics currency in Fusion Analytics Warehouseto the same currency as the corporate currency in Fusion Analytics, and you can use the facts from the analytics currency folder. This ensures the currency is consistent between applications. See Set Up the Pipleine Parameters.
Renewed Subscriptions Many Not Show Renewed Date
When a subscription is renewed, thereby creating a new subscription, the last updated date for the subscription doesn't change.
Because the updated date isn't captured, the warehouse doesn't show the Renewed Date accurately even though the subscription was created by the renewal process.
To work around the issue, the reset the warehouse (see Reset the Data Warehouse) and reload the data pipeline (see Reload a Data Pipeline for a Functional Area).
Oracle Cloud Known Issues for Oracle Fusion Analytics Warehouse
F55808-04
July 2022
Copyright © 2021, 2022, Oracle and/or its affiliates.