TABLE OF CONTENTS

OPTIONAL UPTAKE OF NEW FEATURES (OPT-IN) ················································································································ 2

UPDATE 19B ······························································································································································································· 2

Revision History ························································································································································································ 2

Overview ······································································································································································································· 2

Optional Uptake of New Features (Opt In) ··································································································································· 3

Feature Summary ····················································································································································································· 4

Order Management ············································································································································································· 6

Set Up Sequences for Sales Order Numbers ··················································································································· 6

Specify Business Unit for Selling Profit Center for Goods and Services Tax ························································ 7

Integrate and Extend Order Management Using REST Services ·················································································· 9

Manage Sales Orders for Order Hub Using a REST Service ······················································································ 9

Configurator ························································································································································································· 10

Prevent Inadvertent Workspace Releases ······················································································································· 10

Integrate and Extend Configurator Using REST Services ······························································································ 10

Manage Configurator Models Using a REST Service ·································································································· 10

Manage Configurations Interactively Using a REST Service ···················································································· 11

Global Order Promising ································································································································································· 13

Integrate and Extend Global Order Promising Using REST Services ········································································ 13

Check Supply Availability Using a REST Service ·········································································································· 13

Schedule Orders Using a REST Service ·························································································································· 14

2

OPTIONAL UPTAKE OF NEW FEATURES (OPT-IN)

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 in the Opt-In UI to enable for end users (plus possibly take additional setup or configuration steps). action

Column A shows when these features were originally delivered.

Beginning in the update version specified in Column B, these features will the Opt-In UI to no longer requireenable 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.

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

See more information about the "No Longer Optional Features".

UPDATE 19B

REVISION HISTORY

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

Date Feature Notes

22 MAR 2019 Created initial document.

OVERVIEW

This guide outlines the information you need to know about new or improved functionality in this update.

SECURITY AND NEW FEATURES

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed.

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

3

1. 2. 3. 4.

1. 2. 3. 4.

5.

OPTIONAL UPTAKE OF NEW FEATURES (OPT IN)

We continue to add many new features to the Oracle Cloud Applications, and for some features, you can take advantage of new functionality at a pace that suits you by “opting in” to the feature when you’re ready. You can opt-in to a feature in two ways:  by using the New Features work area, or by using the Setup and Maintenance work area.

To opt-in using the New Features work area:

Click the , and then click (under the My Enterprise heading).Navigator New FeaturesOn the New Features page, select the offering that includes new features you’d like to review.Click for any feature that you want to opt-in to.Opt-InOn the Edit Features page, select the option for the feature, and then click .Enable Done

To opt-in using the Setup and Maintenance work area:

Click the , and then click .Navigator Setup and MaintenanceOn the Setup page, select your offering, and then click .Change Feature Opt-InOn the Opt-In page, click the icon.Edit FeaturesOn the Edit Features page, select the option for any feature you want to opt-in to. If the Enable Enablecolumn includes an Edit icon instead of a check box, then click the icon, select your feature options, and click . Save and CloseClick .Done

OPT-IN EXPIRATION

Some features include an opt-in expiration update, after which they are no longer optional. If you have not opted in to the feature by the expiration update, it will automatically be enabled for you in that update.

Click here to review details of all Oracle Applications Cloud features with an upcoming opt-in expiration update.

4

FEATURE SUMMARY

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Customer Action Required = You MUST take action before these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users (Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users (Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature Report

UI or Process-Based:

Small Scale

UI or Process-Based:

Larger Scale* Customer Action Required

Order Management

Set Up Sequences for Sales Order Numbers

Specify Business Unit for Selling Profit Center for Goods and Services Tax

Integrate and Extend Order Management Using REST Services

Manage Sales Orders for Order Hub Using a REST Service

Configurator

Prevent Inadvertent Workspace Releases

Integrate and Extend Configurator Using REST Services

Manage Configurator Models Using a REST Service

5

Ready for Use by End Users (Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users (Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature Report

UI or Process-Based:

Small Scale

UI or Process-Based:

Larger Scale* Customer Action Required

Manage Configurations Interactively Using a REST Service

Global Order Promising

Integrate and Extend Global Order Promising Using REST Services

Check Supply Availability Using a REST Service

Schedule Orders Using a REST Service

6

ORDER MANAGEMENT

SET UP SEQUENCES FOR SALES ORDER NUMBERS

Set up the sequence that Order Management uses for sales order numbers. Use the sequence to identify and track sales orders so you can audit them, and in some cases, to meet legal requirements. The order number doesn't change for the life cycle of the sales order.

In this update, you can:

Use a predefined order number sequence (ORA_FOM_DOC_SEQUENCE_AUTO).Specify the starting number for the sequence.

Here are the flows that this enhancement supports:

Create Order 

SaveSubmitCopy

Order Management Cloud uses the predefined document sequence for each sales order you create through these channels:

Work area in Order Management CloudDirect web service integration through SOA, REST, ADF, or HVOPFile based data import and batch import through the FBDI templateBusiness to business integration through EDI

Watch a Demo

Note these points:

Order Management uses the predefined sequence when it creates a sales order, a return order, or an order for an internal material transfer.

If you're updating from 19A to 19B, then you can use an upgrade script that Oracle provides. You apply the script during the update process. It resets the initial value of the ORA_FOM_DOC_SEQUENCE_AUTO predefined document sequence.

If you don’t want to use the predefined sequence, then you can enable the Retain Sales Order Number for Orchestration Order Number option. This option instructs Order Management to continue to use order numbers that some other system creates, and not to use the predefined sequence.

STEPS TO ENABLE

No steps are required to enable this feature.

TIPS AND CONSIDERATIONS

A user with appropriate privileges can modify the predefined document sequence. No constraints prevent the user from modifying or deleting the sequence. The user must be careful not to modify or delete the sequence in a way that will cause problems.

7

If this is your first deployment of Order Management and you're going live on 19B, then you must specify the Initial Value attribute for the document sequence.

KEY RESOURCES

Watch Order Management Infrastructure Enhancements Readiness TrainingOracle Supply Chain Management Cloud: Implementing Order Management, available on Oracle Help

.Center

SPECIFY BUSINESS UNIT FOR SELLING PROFIT CENTER FOR GOODS AND SERVICES TAX

In this update, Oracle Order Management Cloud supports using a selling profit center on a sales order line that's different from the business unit that Order Management uses. Use this feature to sell products that belong to more than one profit center in a single sales order. If you must use more than one tax registration across states, then you can set them up for the profit center but continue to use a single business unit in Order Management.

You can opt in to this feature according to your business needs.

Use an order management parameter to set the default value for the selling profit center to the business unit that Order Management uses or the business unit that the profit center of the shipping organization uses. The Order Management work area provides an option so the user can set the selling profit center on the order line.

8

If you set the parameter to Shipping Organization, then Order Management sets the default value for the selling profit center to the profit center that the organization parameters of the shipping warehouse specifies.

Order Management updates the selling profit center every time a downstream system updates the warehouse. If the user changes the warehouse in the Order Management work area, then Order Management doesn't update the selling profit center.

Tax determinants depend on the selling profit center, so Order Management sets the default value for tax determinants each time it updates the business unit for the selling profit center.

Order Management communicates the selling profit center to downstream applications, such as Shipping, Costing, Sales, Financial Orchestration, Tax, and Receivables. You can also use the selling profit center in the order information web service, an order management extension, or an interface mapping extension.

For details about using the selling profit center in an intercompany business flow for India Goods and Services Tax, see the related features in Oracle Inventory and Cost Management Cloud.

Watch a Demo

MANAGE ORDER MANAGEMENT PARAMETERS

9

STEPS TO ENABLE

You must opt in to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Order Management                         

TIPS AND CONSIDERATIONS

This feature can be used with an India Goods and Services Tax (GST) implementation or taxation in the EU. 

KEY RESOURCES

Watch Specify Business Unit for Selling Profit Center for Goods and Services Tax Readiness Training

ROLE INFORMATION

Job Roles and Job Codes: 

Order Entry Specialist (ORA_FOM_ORDER_ENTRY_SPECIALIST_JOB)Order Manager (ORA_DOO_ORDER_MANAGER_JOB)

INTEGRATE AND EXTEND ORDER MANAGEMENT USING REST SERVICES

MANAGE SALES ORDERS FOR ORDER HUB USING A REST SERVICE

Use REST services with Order Management Cloud so you can integrate with a system that resides outside of Order Management Cloud. In this update, use the Sales Orders for Order Hub service to create orders through the REST service, including orders for configured items and kits. The service supports all parts of a sales order, including order header, order lines, charges, sales credits, attachments, extensible flexfields, and other entities mentioned in the REST documentation.

STEPS TO ENABLE

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center> > REST API).  If you are new to Oracle's REST services you may want to your apps service area of interestbegin with the Quick Start section.

KEY RESOURCES

Watch Order Management Infrastructure Enhancements Readiness Training

Refer to the documentation on the REST APIs for Oracle Supply Chain Management Cloud Oracle Help Center.

ROLE INFORMATION

Job Role:

Order Entry Specialist

10

CONFIGURATOR

PREVENT INADVERTENT WORKSPACE RELEASES

Set the workspace release threshold to prevent the premature release of workspace participants into production. You set the threshold as the number of days out from the current date, beyond which point no workspaces can be released. By default the workspace release threshold is set to 1 day. Without this feature, you might inadvertently release a workspace into production without the ability to introduce new changes to your models until the effective start date of the unintentionally released workspace has passed.

Watch a Demo

STEPS TO ENABLE

No steps are required to enable this feature.

TIPS AND CONSIDERATIONS

To update the workspace release threshold value and for additional information, refer to Oracle Support note: 2471288.1

KEY RESOURCES

guide, available on the .Oracle SCM Cloud: Modeling Configurations for SCM Oracle Help CenterWatch Prevent Inadvertent Workspace Releases Readiness Training

ROLE INFORMATION

Job Role and Code:

Product Configurator Manager (ORA_CZ_PRODUCT_CONFIGURATOR_MANAGER_JOB)

INTEGRATE AND EXTEND CONFIGURATOR USING REST SERVICES

MANAGE CONFIGURATOR MODELS USING A REST SERVICE

Oracle Configurator Cloud provides REST based services to efficiently manage and administer large scale deployments.

Use the Configurator Models REST service to do the following:

Query model version detailsCreate and edit rule foldersEdit Configurator extension rule text

STEPS TO ENABLE

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center> > REST API).  If you are new to Oracle's REST services you may want to your apps service area of interestbegin with the Quick Start section.

11

TIPS AND CONSIDERATIONS

The following sample JSON input payload provides the basic information required to update the Configurator extension rule text for a particular model:

"RuleId": 300100174493690,

"RuleText": "def PvcEvent() {

    def baseNode = cxEvent.baseNode

    def config = cxEvent.configuration

    def root = config.getRootModels().get(0)

    def 16GB_RAM = root.getChildByName("High Capacity RAM - 16 GB")

    16GB_RAM.select() }"

KEY RESOURCES

Refer to the documentation, available on the  REST API for Oracle Supply Chain Management Cloud Oracle Help Center

ROLE INFORMATION

Job Role and Code:

Product Configurator Manager (ORA_CZ_PRODUCT_CONFIGURATOR_MANAGER_JOB)

Privilege Name and Code:

Manage Configurator Model Resources (CZ_MANAGE_CONFIGURATOR_MODEL_RESOURCES_PRIV)

MANAGE CONFIGURATIONS INTERACTIVELY USING A REST SERVICE

This feature enhances the Configurations REST API to interactively create and build valid configurations of items or services.

Enhancements to the Configurations REST API include:

Maintenance of the session state across multiple requestsRestore intermediately saved interactive configurationsRetrieve immediate runtime child nodes of a configuration nodeRetrieve runtime attributes of a specific node in the root model or a mandatory reference modelSelect and set the quantity of a node in the root and mandatory reference modelsUpdate the value of a supplemental nodeAdditional error messages and exception handling

12

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center> > REST API).  If you are new to Oracle's REST services you may want toyour apps service area of interestbegin with the Quick Start section.

TIPS AND CONSIDERATIONS

Below is a sample JSON input payload for the POST method of the Configurations REST API to create an active (interactive) configuration:

    "CallingApplicationCode": "FOM",   

    "InventoryItemNumber": "zCZ-AS100",   

    "InventoryOrganizationCode" : "V1",   

    "SessionEffectiveDate": "2018-11-28T00:00:01-07:00",   

    "FinishConfigurationFlag": false

Note that the  attribute is set to , to indicate that this resource will be an FinishConfigurationFlag falseinteractive configuration.

Below is a sample JSON response payload resulting from a POST method invocation of the configurations REST API:

    "ConfigHeaderId": 300100174170591,

    "ConfigRevisionId": 300100174170592,

    "ConfigurationId": "300100174170591_300100174170592",

    "Name": "zCZ-AS100 (Wed Nov 28 00:00:01 MST 2018)",

    "Description": "Audio System",

    "ValidConfigurationFlag": false,

    "CallingApplicationId": 10500,

    "CallingApplicationCode": "FOM",

    "InventoryItemNumber": "zCZ-AS100",

    "InventoryOrganizationCode": "V1",

    "FinishConfigurationFlag": false,

    "LineQuantity": 1,

    "HeaderAttributes": null,

    "AdditionalRootLineAttributes": null,

    "CustomParameters": "[{\"Name\":\"FinishConfigurationFlag\",\"Value\":\"N\"}]",

STEPS TO ENABLE

13

    "ManualPriceAdjustments": null,

    "OutputMode": "filtered",

    "ConfigurationSessionToken": "82E65BA967003441E0530803F00AC7F6300100174170591300100174170592",

    "CreatedBy": "SCMOPERATIONS",

    "CreatedOn": "2019-02-28T07:41:27-07:00",

    "LastUpdatedBy": "SCMOPERATIONS",

    "LastUpdatedOn": "2019-02-28T07:41:42.493-07:00",

    "ConfigurationState": "Active",

    "SessionEffectiveDate": "2018-11-28T00:00:01-07:00",

    . . .

This payload includes the  which identifies the newly created interactive configuration, in ConfigutrationIdaddition to the   attribute which will be needed as a HTTP header attribute for ConfigurationSessionTokenany subsequent interaction with this configuration.

KEY RESOURCES

Watch Manage Configurations Interactively Using a REST Service Readiness Training

Refer to the  documentation, available on the REST API for Oracle Supply Chain Management Cloud  Oracle r.Help Cente

GLOBAL ORDER PROMISING

INTEGRATE AND EXTEND GLOBAL ORDER PROMISING USING REST SERVICES

CHECK SUPPLY AVAILABILITY USING A REST SERVICE

Prior to placing a sales order, users need to know whether products are available for delivery, and if so, when. These users may be customers accessing an eCommerce solution, or call center representatives using a configure, price, and quote application. Starting with this update, Oracle Global Order Promising Cloud provides an Available Supplies REST API that users can invoke to evaluate the possible promising result by creating an inquiry and calling Global Order Promising, even before an order has been created.

As with the existing SOAP web service, users can use the REST service to ascertain potential supply sources and fulfillment dates, or the availability of supplies at one or more organizations or at a supplier. The request could either be in the form of a simple check of the available-to-promise (ATP) supply at item organizations or at a supplier, or a more detailed search for capable-to-promise (CTP) supply across the supply chain. Availability dates include shipment and delivery lead times as well.

14

STEPS TO ENABLE

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center> > REST API).  If you are new to Oracle's REST services you may want toyour apps service area of interestbegin with the Quick Start section.

Before enabling the Available Supplies REST service, the administrator should determine whether the new REST API is to be used by the business.

TIPS AND CONSIDERATIONS

Alternate availability options are not provided by the Check Availability action.Pegging information is not provided by the Check Availability action.

KEY RESOURCES

For detailed instructions about invoking the SCM Cloud REST services, access the REST API for Oracle guide on the > Supply Chain Planning > REST API: Supply Chain Management Cloud Oracle Help Center

Supply Chain Management.

ROLE INFORMATION

To use this feature, the following is required:

Job Role:

Order Promising Manager

SCHEDULE ORDERS USING A REST SERVICE

When customers submit sales orders for items, an enterprise must schedule fulfillment to provide accurate shipment and delivery dates and reduce the supply that is available to subsequent orders. Starting with this update, you can use the Order Promises REST service to carry out standard order promising activities. As with the existing SOAP web service, the REST service can schedule one or more order lines based on current and future availability, force scheduling on a specific date, or cancel scheduling for a previously scheduled order.

With this REST service, you can integrate Oracle Global Order Promising Cloud with external order management systems to promise or cancel orders. This service provides accurate shipment and delivery information that can be conveyed to external transaction systems to carry out order fulfillment, and ensures that the available supply is adjusted such that new orders can be promised based on the latest supply picture.

STEPS TO ENABLE

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center> > REST API).  If you are new to Oracle's REST services you may want toyour apps service area of interestbegin with the Quick Start section.

Before enabling the Order Promises REST service, the administrator should determine whether the new REST API is to be used by the business.

15

KEY RESOURCES

For detailed instructions about invoking the SCM Cloud REST services, access the REST API for Oracle Supply Chain Management Cloud guide on the > Supply Chain Planning > REST API: Oracle Help CenterSupply Chain Management.

ROLE INFORMATION

To use this feature, the following is required:

Job Role:

Order Promising Manager

---

16

Copyright © 2019, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.