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 |
|---|---|
| Improve Processing After Supply Chain Orchestration Updates Supply or Demand | Opt In |
| Add Postprocessing Days When You Modify Ship Dates in Your Back-to-Back Flows | Opt In |
Constraint-Based Planning
| Feature | Action Required |
|---|---|
| Plan Components and Resources for Nonnettable Work Orders in Constrained Supply Planning | Opt In |
| Analyze Late Demands Due to Capacity Constraints | Opt In plus Setup |
Attribute-Based Planning and Constraint-Based Planning
| Feature | Action Required |
|---|---|
| Respect Configured Attributes in Constrained Supply Plans | Opt In |
Backlog Management
| Feature | Action Required |
|---|---|
| Use Pick-Pack Lead Time in Backlog Management | Opt In plus Setup |
| Import Routings Taking into Account Effectivity Start Dates | Opt In |
Production Scheduling
| Feature | Action Required |
|---|---|
| Consider Resource Calendars for Production Changeovers | Opt In |
| Schedule Planned Make Orders from Supply Planning | Opt In |
| Visualize Supplies and Demands in Gantt Chart | Opt In |
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.