Oracle Fusion Cloud Financials
What's New

OPT IN FEATURES WITH FUTURE EXPIRATION

The features in the table below were originally delivered as Opt In but will, in a future update, no longer require Opt In to enable. You may still need to do some additional setup or configuration, as indicated in Column C. This advance notice of upcoming Opt In Expiration will help you plan for these changes. Once the Opt In has expired the feature will be included in the Features Originally Enabled Via the Opt In User Interface section below.

Important Note: If you have already enabled these features then NO further action is necessary.

(A) (B) (C)
Feature Module Feature
*Required*
the Opt In UI to Enable,
Originally Delivered in:
Feature
*No Longer Requires*
the Opt In UI to Enable,
Beginning in:
Action still required to enable for end users?
NO,
Delivered Ready
to Use
YES,
Customer Action Still
Required
Update 22B
Bonus Depreciation Calculation Basis for JapanJapan22B23A
Update 22A
Budget Balances Synchronization from Budget Transfers in Both Budgetary Control and General LedgerBudgetary Control22A22C (2)
Receipt Attachment After Expense Report ApprovalExpenses22A22C (1)
Update 21D
Asset Book Change During Source Lines PreparationAssets21D22C

FEATURES ORIGINALLY ENABLED VIA THE OPT IN USER INTERFACE

The features in the table below were originally delivered Disabled. That is, the features required you to take action in the Opt In UI to enable for end users (plus possibly take additional setup or configuration steps). Column A shows when these features were originally delivered.

Beginning in the update version specified in Column B, these features will no longer require the Opt In UI to enable for end users. However, you may still need to take additional setup or configuration steps to enable the feature, per Column C. If additonal customer action is still required to enable, click on the feature name to get more information.

Important Note: If you have already enabled these features in the Opt In UI then NO further action is necessary.

(A) (B) (C)
Feature Module Feature
*Required*
the Opt In UI to Enable,
Originally Delivered in:
Feature
*No Longer Requires*
the Opt In UI to Enable,
Beginning in:
Action still required to enable for end users?
NO,
Delivered Ready
to Use
YES,
Customer Action Still
Required
Update 22B
Budget Creation and Synchronization Using Spreadsheet for Both Budgetary Control and General LedgerBudgetary Control21D22B (1)
Update 21D
Detection of Duplicate ExpensesExpenses21B21D (2)
Allow Expense Type Account as Asset Clearing Account for GASB 34Assets21A21D
Additional Tax Drivers in Supplier Portal for Accurate Tax CalculationPayables21A21D (1)
Update 21C
Cash Pooling for Receivables Multifund AccountingReceivables21A21C
Update 21B
Configurable Collections Activity Management NotificationAdvanced Collections20D21B (1)
Configurable Budgetary Control Override Workflow NotificationsBudgetary Control20D21B (1)
Configurable Receivables Credit Memo Request Manual Entry Workflow NotificationReceivables20D21B (1)
Credit Memo Creation in the Earliest Open Accounting PeriodReceivables20D21B (1)
Lockbox Payment Matching with Balance Forward BillsReceivables20D21B
Review and Correct Accounting Exceptions for SubledgersSubledger Accounting20D21B (1)
Review and Correct Accounting Exceptions for SubledgersSubledger Accounting20C21B (2)
Configurable Payables Workflow NotificationsPayables17D21B
Update 21A
Configurable Cash Management Workflow NotificationsCash Management20D21A (1)
Configurable Intercompany Workflow NotificationsCommon Financials Features20D21A
Optimization of Workflow Rule EvaluationPayables20D21A (1)
Configurable Collections Bankruptcy Workflow NotificationAdvanced Collections20C21A (2)
Configurable Expenses Workflow NotificationsExpenses20C21A (2)
Assign the Primary Receipt Method to Manual TransactionsReceivables20C21A
Actionable Cards for Expense ReportsExpenses20B21A (2)
Configurable Journal Workflow NotificationsGeneral Ledger17D21A (1)

(1) SMALL Scale UI or Process-Based Feature: These features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

(2) LARGER Scale UI or Process-Based Feature: These features have more complex designs. Therefore, the potential impact to users is higher, meaning these features should be the focus of customer acceptance testing.