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.

Commerce

Feature Action Required
Allow Removal of Entire Model Hierarchy from Quote Setup Required
Control Variable Naming Convention for Commerce Entities Setup Required

Configuration

Feature Action Required
Cascade Child Models in System Configuration Initialization Setup Required

Integration

Feature Action Required
Enable Single Sign-On for a Quick Registration Company Setup Required
Oracle Commerce Cloud Self-Service Portal – CPQ Integration Setup Required
Sales and Financial Accounts Integration Setup Required

Pricing

Feature Action Required
Dynamic Attribute-Based Matrix Pricing for Price Model and Price Agreements Setup Required
Sarbanes–Oxley Data Compliance in CPQ Pricing Setup Required
Support BML Scripting Before and After Pricing Engine Calculations Setup Required
Incremental Repricing Option for Commerce Actions Setup Required

Web Services

Feature Action Required
Collaborative Quote Queue REST APIs REST APIs
New Commerce REST API Endpoints REST APIs
Commerce REST API Enhancements REST APIs
Generate Configurator REST APIs REST APIs
Groups REST API REST APIs
New Pricing Setup REST APIs REST APIs
Pricing Setup REST API Enhancements REST APIs
Product Search REST APIs REST APIs
Sales Companies REST APIs REST APIs

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.

Commerce

Feature Impact
Add Unconfigured Models to a Transaction Small scale
Collaborative Quoting Architecture Enhancements Small scale

Configuration

Feature Impact
Product Workbench for CPQ Administrators Small scale
Auto Generation of BOM Simple Configurator Small scale
Performance Optimization for BOM Validation Small scale

Pricing

Feature Impact
Price Effectivity for Line Item Prices Small scale
Pricing Administration UX Enhancements Small scale
Sales Agreement Authoring Support in CPQ Pricing Small scale