Feature Summary

Features Delivered Disabled: Customer Action Required for Use

This table provides a summary of the features that require customer action before they can be used by end users. These features are delivered in a disabled state, and you can choose if and when to enable them.

Examples of such features include:

New or expanded BI subject areas that need to be incorporated into reports
Integration required to utilize new web services
Features that must be assigned to user roles before they can be accessed

These features are non-disruptive since they remain inactive until you take action. You can selectively enable them, allowing you to set your own testing and rollout schedule.

Supply Chain Orchestration

Feature	Action Required
Manage Configure to Order Changes Without Canceling Supply	Setup Required
Group Transfer Orders Using Source and Destination Organizations	Opt In plus Setup

Collaboration Messaging Framework

Feature	Action Required
Redwood: Manage External Message Definitions Using a Redwood Page	Setup Required
Simplify the Exchange of Invoices with Oracle Cloud Enterprises	Setup Required
Create a File Name Pattern for B2B Messages Sent Via SFTP, File Export, or Email	Setup Required
Receive a Brazil Electronic Freight Invoice with Additional Freight Service Types	Setup Required

SCM Common Components

Feature	Action Required
Create Guided Journeys for Redwood Pages in the Setup and Maintenance Work Area	Visual Builder

Inventory Management

Feature	Action Required
Redwood: Create Cycle Counts Using a Redwood Page	Setup Required
Redwood: View Item Quantities Using a Redwood Page	Setup Required
Integrate Manufacturing and Maintenance Direct Work Order Transactions with Your Warehouse Management System	Opt In plus Setup
Replenish Locations Using Radio Frequency Identification	Setup Required
View Item Shortages and Remedy Warehouse Stocking and Replenishment Issues	Setup Required

Receiving

Feature	Action Required
Redwood: Inspect Receipts Using a Redwood Page	Setup Required
Redwood: Create Receipt Returns Using a Redwood Page	Setup Required
Redwood: Create Unordered Receipts Using a Redwood Page	Setup Required
Redwood: Correct Receipts Using a Redwood Page	Setup Required
Redwood: View Receipts and Receipt Returns in Supplier Portal Using a Redwood Page	Setup Required
Redwood: Manage Inbound Shipments and Create ASN or ASBN Using a Redwood Page	Setup Required
Ship Your Receipt Returns Through Oracle Shipping When Goods Require Physical Return	Opt In plus Setup

Mobile Inventory

Feature	Action Required
Redwood: Inspect Received Goods Using a Mobile Device	Setup Required

Cost Management

Feature	Action Required
Enable Parallel Processing in COGS Processor	Opt In

Receipt Accounting

Feature	Action Required
Redwood: Review Receipt Accounting Exceptions using a New User Experience	Setup Required
Redwood: Audit Receipt Accrual Clearing Balances Using a New User Experience	Setup Required
Redwood: Create and Edit Accrual Cutoff Rules Using a New User Experience	Setup Required
Redwood: Review Receipt Accounting Distributions Using a New User Experience	Setup Required
Redwood: Review and Clear Open Receipt Accrual Balance Using a New User Experience	Setup Required
Account In-transit Inventory for Inbound Purchase Orders using INCO Terms	Setup Required
Automatically Generate Accrual Clearing Summary	Setup Required

Fiscal Document Capture

Feature	Action Required
Use PO for Freight Fiscal Flows except Freight Acquisition Fiscal Flow	Setup Required

Supply Chain Financial Orchestration

Feature	Action Required
Interface Warehouse Information with Receivables for a Procurement Flow	Setup Required
Match Payable Invoices to Receivable Invoices by Invoice Number	Setup Required
Create Intercompany Financial Flows for Subscriptions and During Transition	Setup Required

Features Delivered Enabled: Ready for Use by End Users

This table provides a summary of the features included in the document that are ready to be used by end users.

The impact of these features can be categorized as follows:

Larger Scale UI or Process-Based: These features have a higher potential impact on users due to their complex designs. Focus your acceptance testing on these features.
Small Scale UI or Process-Based: These features have minimal impact on users and typically involve minor changes to fields, validations, or programs.
Report: These features have minimal impact on users and include new or modified, Oracle-delivered, ready-to-run reports.