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.

Key Metrics can't be Translated

In this release, text added as metadata to the key metrics feature can't be exported, translated, and brought back into the application as translated content.

Where shown (for example as a key metric description), that key metric metadata will be seen in the original language in which it was entered.

Missing Deck-style Filters in Migrated Content

In this release, a copy of decks has been migrated to core Oracle Analytics Cloud workbooks.

The deck-style filters for time and calendars can't be directly replicated in the workbooks. Migrated workbooks, rather than swapping between business time intervals (such as Current, Previous, or Last-N), use standard Oracle Analytics Cloud time filters. These time filters present multiple distinct periods based on columns in the subject area (such as Fiscal Year, Fiscal Quarter, and Fiscal Period). The migrated content, found in the Overview Dashboards folder, has been updated to use standard Oracle Analytics Cloud filters for time.

Unexpected Filter Context for Data Action Links in Migrated Content

For this release, in the migrated content, the navigation from converted decks (now called overview dashboards) has issues passing the filter context from the overview dashboards down to the detail workbooks.

The shared detail workbooks are optimized for navigation from decks to the drill-down content. Decks are the primary organization method, while overview dashboards supplement the decks only. There are fewer issues when no or limited context is passed from the filters on the overview dashboard to the detail workbooks.

To work around this issue, update the converted decks in the overview dashboards folder with your desired optimized navigation.

Error When Custom Path Included in Migrate Custom Content Utility Folder Name

In the Migrate Custom Content utility, if you include anything other than the name of the folder you want to create under Run Migration, an error occurs.

The migration process appends the folder you create to the /Shared Folders/custom content path. You don't need to include any text in the field other than the name of the folder. To avoid an error, include only the name of the folder in the field.

To work around the error, re-run the utility to clear the error. Then re-run the utility one more time using only the name of the folder in the field to populate your output in the specified folder.

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

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

Until Release 22.R3, the AR Revenue subject area had 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.

The AR Unaccounted Transactions functional area has been introduced in Release 22.R4. When this is activated, the AR Revenue subject areas show both accounted and unaccounted transactions as long as the transactions are Complete and the Revenue schedules are generated. Transaction Amount and Line Amount may still show incorrectly for partially accounted transactions in some scenarios when attributes such as Fiscal Period, Transaction Accounting Fiscal period (both anchored to Distribution Accounting Date), Accounted Indicator, Account Override Indicator, are used in the analysis. Partially accounted transactions are transactions having both accounted and unaccounted distributions in different periods.

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.

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

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 Applications. 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 Oracle Fusion Cloud Enterprise Resource Planning, 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 Fusion Applications Suite and check the amounts after an incremental run.

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.

Detail Line Number in the AR Revenue Subject Area is Incorrect

The detail line number in the AR Revenue subject area shows the same value as the parent line number.

This issue doesn't have a workaround.

Data Augmentation Doesn't Work for the AR Aging Subject Area

Data augmentation isn't supported for the AR Aging subject area currently.

To work around this issue, if you need any additional attributes, then try to add the attributes to the AR Transactions subject area and use it through cross-subject area analysis.

Records Dropped in Project Assets Subject Area When Adding Certain Metrics

Records are dropped in the Project Assets subject are when you add certain metrics.

Records are dropped in the Project Assets subject area when metrics such as Rejected CIP Cost, Capitalized Cost, Grouped CIP Cost, Unassigned CIP Cost, and Assigned CIP Cost are added, but there is no data for these metrics. If you need the Project Asset related attributes show, add the Grouped Cost metric along with the other metric. The Grouped Cost metric has a value for all Asset Lines, which resolves the error.

Data Validation of Total Outstanding Amount Metric Causes SOAP SERVER ERROR with the Invoice Accounting Status Filter Attribute

This issue is due to an OTBI bug.

To work around this issue, don't select the Invoice Accounting Status filter in the Data Validation of Total Outstanding Amount metric of the AP Aging Subject area. You can use filter as a pivot attribute.

Data Validated Amount of Tax Distribution in AR Subject Areas Doesn't Match Fusion Applications

When there's a deferred tax transaction while performing Data Validation, even if the totals match, the Account Class code doesn't match due to the Oracle Transactional Business Intelligence Deferred Tax classification. While Oracle Fusion ERP Analytics considers it a Tax instead of Tax Distribution Amount, Oracle Fusion ERP Analytics doesn't classify Deferred Tax at the Account Class level, but instead as a Tax line.

There isn't a workaround.

Data Validation of GL Balance Sheet Metrics May Show a Difference In Amounts More Than 15 Digits

Data Validation of GL Balance Sheet metrics may show a difference if the amounts are more than 15 digits long.

Oracle Transactional Business Intelligence rounds amounts that are more than 15 digits long, whereas Fusion Analytics supports amounts more than 15 digits long. Therefore, if the GL Balance Sheet amounts are more than 15 digits long, you may see a difference when performing data validation on these metrics:

  • Financials GL Balance Sheet Debit Activity Amount in Ledger Currency by Ledger and Fiscal Period
  • Financials GL Balance Sheet Credit Activity Amount in Ledger Currency by Ledger and Fiscal Period
  • Financials GL Balance Sheet Debit Activity Amount in Ledger Currency by Ledger and Fiscal Period

Remaining Balance Calculation in AP Aging Subject are with Withholding Tax Incorrect

In the AP Aging subject area, the Remaining balance calculation is incorrect when there's a Withholding tax applied at the Invoice Distribution level.

The withholding tax is calculated at the Invoice level based on the tax rate which assumes that the tax is applied to the entire invoice instead of a specific line/distribution.

Witholding Tax Calculation is Missing when Calculation Point is Payment

The Expense fact shows all of the invoice lines except where the Invoice includes a Withholding tax line.

This can be a manual entry when it's added during the creation of the invoice regardless of the calculation point, or added by the system based on the calculation point, either at Invoice or at Payment. In the case of the calculation point being at Payment, the accounting distribution for AWT appears in the Payment distribution. The Withholding tax calculation at Payment isn't currently considered in the analysis.

Data Validation of GL Detail Transaction Metrics May Show A Difference with Unposted Journal Lines Feature

If the preview feature Enabled Unposted Journal Lines is enabled, GL Detail transactions will show both unposted and posted journal lines.

The existing data validation query is restricted to only fetch posted journal lines, therefore you will see additional records in the warehouse that are unposted when the OTBI query doesn't fetch them. There is currently no workaround.

Data Validation of Total Transaction Amount in AP Invoices Doesn't Match OTBI with Retainage

If AP invoices have Retainage, the installment amount won't include the retainage amount although the Invoice amount will include Retainage.

The AP Invoices subject area in Fusion Analytics Warehouse is at the Installment level and the Total Transaction Amount metric is derived from the Installment amount. Data Validation of Total Transaction Amount in the Ledger Currency compares the Transaction amount calculated from the Installments which doesn't include Retainage. The subject area instead compares with the Invoice Amount in Oracle Transactional Business Intelligence which includes retainage, therefore the amounts don't match.

If you have a Retainage process, you need to use the data validation metric Total Transaction Amount in Document currency. This compares with the Gross amount metric in the Oracle Transactional Business Intelligence Payables Invoices - Installments Real Time subject area and both metrics are at the Installment level.

Backdated Invoices and Receipts Created in Fusion Receipts Don't Show Correct Amounts

Backdated Invoices and Receipts created in Fusion Applications Receivables do not show the correct remaining balance, schedule, or snapshot in the AR Aging subject area.

In the Receivables Aging preview feature (AR Aging which uses the accounting date for snapshot), if backdated transactions are created or updated and the transaction schedule status is Closed, the remaining amount and schedule status aren't updated correctly in the daily incremental run. As a workaround, to see the backdated transactions correctly, reset the Receivable Aging functional area manually or schedule to run a full load of this functional area daily, weekly, or monthly depending on your reporting needs.

In Purchase Orders Subject Area Closed PO Count Metric and Open PO Count Metric is Incorrect

In the Purchase Orders subject area, the purchase orders line status doesn't get updated in Fusion Analytics as it does in Oracle Fusion Cloud Applications.

This issue causes the Closed PO Count metric and Open PO Count metric to be incorrect in Fusion Analytics due to the last update date not being updated in the source, so the incremental load isn't updated in Fusion Analytics.

To work around this issue, reset the data pipeline for the Purchasing functional area on a weekly baseis. See Reset a Data Pipeline for a Functional Area. This issue will be fixed in a future release.

Some Requisitions in Requisitions Subject Area Don't Show Purchase Order Number

In the Requestions subject area, some requisitions don't show the purchase order number in Fusion Analytics even though there's a purchase order number against that requisition in the Oracle Fusion Cloud Applications source.

Note:

Inventory Balance Analysis is a preview feature.

The last update date isn't getting updated from the Oracle Fusion Cloud Applications source, so the incremental load isn't picking up these updates in Fusion Analytics.

To work around this issue, reset the data pipeline for the Purchasing functional area on a weekly basis. See Reset a Data Pipeline for a Functional Area.

Updated Name for DW_ORG_HIREARCHY_DENORM_DH Table

The DW_ORG_HIREARCHY_DENORM_DH Table in Oracle Fusion ERP Analytics is now named DW_ORG_HIERARCHY_DENORM_DH.

Old Records Created after IED with Time-Based Dimensions Missing from ERP Subject Areas

The Oracle Fusion ERP Analytics subject areas use Accounting calendar in the Time dimension.

If there are records that use dates that aren't part of the accounting calendar, these records will be dropped when you use the Time dimension. For example, if you defined your accounting calendar starting 2020 but have old transactions before that year (records with dates in 2019 and before) that were entered in Fusion Applications Suite as part of data conversion, these records will be dropped when you use the time-based dimensions. There is no work around for this issue.

Some Unapplied Receipts Missing in AR Aging

An Accounts Receivable receipt was created without a Paying customer is an Unidentified receipt.

An Accounts Receivable receipt created with a Paying customer, but not applied or partially applied to an invoice is an Unapplied receipt. If an unidentified receipt is created with a certain receipt status and later assigned a customer in a different receipt status, such Unapplied receipts are currently missing in the AR Aging snapshots.

Error Message with Cross-Subject Area Analyses Between Receivables Subject Area and PPM-Project Invoices Subject Area

You may encounter a table not found error message if only one of these functional areas – AR Unaccounted Transactions or Project Invoices Prior to Acceptance - is activated and you perform cross-subject area analysis between Accounts Receivables subject areas and the PPM- Project Invoices subject area.

Activate the Project Invoices Prior to Acceptance functional area to bring in invoices with statuses that are before the Accepted status as well in the PPM-Project Invoices subject area. Activating the AR Unaccounted Transactions functional area brings in Complete invoices that aren't yet accounted for in the AR Transactions and AR Revenue subject areas. When only one of these functional areas is activated, the query uses incorrect LTS which results in the table not found error.

To avoid this error activate both of these functional areas.

Warehouse Full Reload Schedule Tab Timezone Not Showing Same as Incremental Refresh Schedule

The Warehouse Full Reload Schedule tab timezone doesn't show the same timezone as the incremental refresh schedule.

The scheduled full reload works as expected when the incremental load for the day is triggered. There is no workaround for this issue.

Known Issues for Oracle Fusion SCM Analytics

Oracle Fusion SCM Analytics has this known issue.

Topics:

Known Issues for Fusion SCM Analytics Costing

These Known Issues address the Costing functions.

Topics:

Updates or Changes in Cost Accounting Distribution Details Aren't Seen in Cost Accounting Subject Area

Updates or changes in the cost accounting distribution details aren't seen in the Oracle Fusion SCM AnalyticsCost Accounting subject area.

The last update date in the Cost Accounting Distribution Lines table isn't getting updated in Oracle Fusion Cloud Supply Chain Planning. Because of this, Oracle Fusion SCM Analytics and Oracle Fusion Cloud Supply Chain Planning aren't synchronized.

To work around this issue, reset the Cost Accounting functional area manually or schedule a full load run of this functional area daily, weekly, or monthly depending on your reporting needs.

Known Issues for Fusion SCM Analytics Inventory

These Known Issues address the Inventory functions.

Topics:

Inventory Balance Analysis Shows On-Hand Data on Previous Day

The Inventory Balance Analysis data visualization shows on-hand data as being on the previous day.

Note:

Inventory Balance Analysis is a preview feature.

There is currently no workaround for this issue.

Inventory Receipts (Preview) Features Aren't Visible After Enabling Inventory Receipts Functional Area

After enabling the Inventory Receipts (Preview) Functional Area, features for the Functional Area aren't available.

To work around this issue, in the Preview Features panel of the Console, disable and enable (toggle) the Inventory Receipts functional area once to see all the Inventory Receipts (Preview) features.

Known Issues for Fusion SCM Analytics Manufacturing

These Known Issues address the Manufacturing functions.

Topics:

Reports for Manufacturing Operation Transactions Show Duplicate Results

The grain for the Manufacturing Operation Transactions subject area is at the Work Order Operation Transactions level and Work Order Outputs level.

You may see duplicate results if a report is built from both Work Order Operation Transactions level and Work Order Output level.

There is no workaround for this issue.

Serial and Lot Number Not Supported for Material Items and Product Items in Manufacturing Materials Subject Area

In the Manufacturing Materials subject area, the Serial and Lot Number attributes aren't supported at both the Material Items and Product Items levels.

To work around this issue, built reports using either the Material Item level or the Product Item level.

Known Issues for Fusion SCM Analytics Purchasing

These Known Issues address the Purchasing functions.

Topics:

Some Requisitions in Requisitions Subject Area Don't Show Purchase Order Number

In the Requestions subject area, some requisitions don't show the purchase order number in Fusion Analytics even though there's a purchase order number against that requisition in the Oracle Fusion Cloud Applications source.

Note:

Inventory Balance Analysis is a preview feature.

The last update date isn't getting updated from the Oracle Fusion Cloud Applications source, so the incremental load isn't picking up these updates in Fusion Analytics.

To work around this issue, reset the data pipeline for the Purchasing functional area on a weekly basis. See Reset a Data Pipeline for a Functional Area.

In Purchase Orders Subject Area Closed PO Count Metric and Open PO Count Metric is Incorrect

In the Purchase Orders subject area, the purchase orders line status doesn't get updated in Fusion Analytics as it does in Oracle Fusion Cloud Applications.

This issue causes the Closed PO Count metric and Open PO Count metric to be incorrect in Fusion Analytics due to the last update date not being updated in the source, so the incremental load isn't updated in Fusion Analytics.

To work around this issue, reset the data pipeline for the Purchasing functional area on a weekly baseis. See Reset a Data Pipeline for a Functional Area. This issue will be fixed in a future release.

Known Issues for Fusion SCM Analytics Sales Orders

These Known Issues address the Sales Orders functions.

Topics:

Project Attribute Columns are Deprecated in Sales Order Fulfillment Lines

Project attribute columns are deprecated from the Sales Order subject area.

Duplicate records were being created in scenarios when project attributes were updated. Therefore, to avoid incorrect data, project attribute columns are deprecated in Sales Order Fulfillment lines. Using Project attributes from Sales Order subject area for custom reports may show errors due to the deprecation of these attribute columns. Project attributes will be reintroduced once the issue is fixed.

Supplier and Supplier Site Columns Show Null Value in Back-to-back Sales Order Fulfillment Lines

Supplier and Supplier site columns show null value in the Back-to-back Sales Order fulfillment and Supply lines.

Duplicate records were being created in the Back-to-back Sales Order scenarios that have multiple POs with multiple Supplier and Supplier Sites for the same Supply Tracking Line. To avoid incorrect data, the Supplier and Supplier Sites columns are being populated with null values.

There is no work around for this.

Item Cost Subject Area Only Supports Cost Scenarios When Published with Inventory Transactions

Only cost scenarios that are published with inventory transactions are valid in Item Cost subject area analyses.

There is currently no work around for this issue.

Sales Credits Data Deleted in Fusion Applications Continues to Show in Fusion Analytics Warehouse

Sales Order Sales Credits records deleted from the Fusion Applications source continue to appear in Fusion Analytics Warehouse.

This scenario shows data mismatch between the Fusion Applications and Fusion Analytics Warehouse. This would be reintroduced once the issue is fixed in the Fusion source application.

To work around the issue, reset the warehouse (see Reset the Data Warehouse) and reload the data pipeline (see Reload 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.

Oracle Fusion CX Analytics Common Issues

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

When records such as Opportunity, Revenue Line. etc., are deleted in the source Fusion Applications. the deleted objects aren't deleted from Fusion Analytics Warehouse.

This scenario shows a data mismatch between Fusion Applications 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).

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 Fusion Cloud Sales Automation 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 Warehouse to the same currency as the corporate currency in Fusion Applications, 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.

Reset the Warehouse and Reload the Data if Existing Security Conditions in an Access Group are Modified

Whenever any new security condition is setup, Oracle Fusion Analytics Warehouse reads the data from Oracle Fusion Cloud Applications and applies the same security condition to the data.

If the existing security conditions are modified, the previous security conditions data may persist and provide an incorrect outcome. For example, if there is a security condition to grant a user access to all the Opportunities in EU region, then Oracle Fusion Analytics Warehouse copies over all the Opportunity Ids for EU region against that security condition. If the same condition is updated in Fusion CX Sales, to restrict the data to Opportunities only in Germany, then the new Opportunity IDs belonging to Germany (for this security condition) gets copied over. But the previous Opportunity IDs also exist in the system thereby giving an incorrect data security result.

To work around this issue, reset the data warehouse (see Reset the Data Warehouse) and refresh the data pipeline (see Refresh a Data Pipeline for a Functional Area.

Oracle Fusion CX Analytics Sales Issues

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

Topics:

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..

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.

To work around this issue:
  1. Add the column to the dimension using data augmentation.
  2. Create a new logical column based on step 1 using a semantic model extension.
  3. Hide the column created in step 1 using the semantic model extension security framework.

Note:

Use the Oracle Fusion Cloud Sales Automation 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.

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.

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).

Oracle Fusion CX Analytics Subscription Issues

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

Topics:

Incorrect Subscription MRR When the Field is Manually Edited in Fusion Applications

Subscription Product line details page may have the MRR field exposed from the Fusion Applications Composer.

The MRR field should be a read-only field, however it's editable, which is the issue. If the values of these fields change, then the CX - Subscription Historical Trend subject area shows an incorrect value.

For example, if a Customer has two subscriptions with MRR of $300 each, the trend would show as: 
||Period||MRR|| 
|Jan-2022|$600| 
|Feb-2022|$600| 
|Mar-2022|$600|
In the month of March 2022, if the user updates the MRR value to $400 for one of the subscriptions (which shouldn't be possible since it's a derived value), here's what one would expect to see and would actually see:
 ||Period||MRR (Expected to see)||MRR (would show up)|| 
|Jan-2022|$600|$700| 
|Feb-2022|$600|$700| 
|Mar-2022|$700|$700|

There isn't currently 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).

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).

Subscription Historical Trend Subject Area Inaccurately Shows Subscriptions as Active

If the ESS job to update the subscription status is run after the Oracle Fusion Analytics Warehouse incremental job, an expired subscription may show as Active in the Subscription Historical Trend subject area.

To avoid this issue, schedule the ESS job prior to the Oracle Fusion Analytics Warehouse incremental run.

If the data shows incorrectly, reset the warehouse (see Reset the Data Warehouse) and reset the data pipeline (see Reset a Data Pipeline for a Functional Area).

Subscription Historical Trend Subject Area Aggregate Date May Show Incorrect Values

In the Subscription Historical Trend subject area, the Aggregate Date dimension may show incorrect month-week-date column values when pulled in to the same report.

The Aggregate Date dimension specifies the date/week/month/year time interval over which the Subscription data has been aggregated. You can see the Active MRR (as an example) over the past 30 days or 52 weeks or 12 months etc.

When the month and date are added in the same report (not an intended use case), the date values may show incorrect data.

For example, the Subscription Aggregate Date has a value of 31/01/2021 12:00:00 AM, but the Subscription Aggregate Month has a value of 2021/02.

This is caused by the week rolling over to the month based on the join criteria: Week_End_Date = Month_Start_date.

For example: 
Week_code = '2021 Week14' 
period_start_date = 28-MAR-21 
period_end_date = 03-APR-21 
month_code = '2021 / 04' 
quarter_code = '2021 Q 2'

This issue occurs when the week spans two months and the week isn't a starting or end week of the corresponding year.

To work around this, don't use multiple time levels in the same report for the Aggregate Date dimension, because this date dimension analyzes the aggregated Subscription trends data for a specific time level, and isn't recommended for other time dimensions when aggregating data at multiple time levels.

Customers with Existing Subscriptions Show as New Customers in Subscription Reports

The initial extract date (IED) defined in Oracle Fusion Analytics Warehouse determines the data extract date from the Oracle Fusion Cloud Applications Suite. If transactions occurred before the initial extract date and are still active, they might not be captured.

For example, if a customer ordered a 3 year subscription for 1 Jan 2020 to 31 Dec 2022, and the initial extract date is set as 1st Jan 2021, then the subscription won't be captured in Oracle Fusion Analytics Warehouse unless you update the data. If the same customer orders another subscription on 1 Aug 2021, it becomes the first subscription in Oracle Fusion Analytics Warehouse for this customer and the application erroneously marks the transaction as a new Customer. You need to be sure to select the correct initial extract date before extracting data into the warehouse.

To work around this issue, run an ESS job before initiating the Oracle Fusion Analytics Warehouse incremental run. If the data still shows up incorrectly, reset the data warehouse (see Reset the Data Warehouse) and refresh the data pipeline (see Refresh a Data Pipeline for a Functional Areawould need to be [reloaded|https://docs.oracle.com/en/cloud/saas/analytics/fawag/reload-data-pipeline-functional-area.html]).

Global Security Granted in Subscription Doesn't Work in Access Groups or Other Security Models

Granting global security in a subscription, such as providing access to all subscriptions for a given user, doesn't work if the security is set up using access groups or other security models.

You can grant security access using one of these methods.

Option 1: Disable access group based security

  1. Copy the Subscription Specialist role.
  2. Remove these two duty roles from the user in Oracle Fusion Analytics Warehouse:
    • Subscription Business Unit Data Security (OA4F_CX_SUBSCRIPTION_BUSINESS_UNIT_DATA)
    • Subscription Custom and System Access Group Data Security (OA4F_CX_SUBSCRIPTION_CUSTOM_DATA)
  3. Assign the user to the Subscription Specialist role.

Option 2: Use FND Grants (BU-based security)

Prerequisite: User must be assigned the OA4F_CX_SUBSCRIPTION_BUSINESS_UNIT_DATA role.

Create a new Security Console security assignment for the user.

  1. Sign in to Oracle Fusion Analytics Warehouse.
  2. On the Home page, open the Navigator menu, click Console, and then click Security under Service Administration.
  3. On the Security page, click the Security Assignments tab.
  4. Click New Assignment
  5. Select the Subscription Business Units security context.
  6. In Security Values, select the appropriate business unit, and under Users select the appropriate user name.
  7. Click Add to Cart and then click View Cart.
  8. In Security Assignments, click Apply Assignments.

Option 3: Use Custom Security

Prerequisite: User must be assigned the OA4F_CX_SUBSCRIPTION_CUSTOM_DATA role.

You can grant custom global security using the Business Unit as an Object Attribute.

  1. Sign in to Oracle Fusion Analytics Warehouse as a Global Security Manager.
  2. Navigate to Tools and then to Sales and Service Access Management .
  3. Under Configure Groups, create a new access group with a rule set to the list of business units.
  4. Publish the rules.