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.

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:

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

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

1. Click the Navigator, and then click Setup and Maintenance.
2. On the Setup page, select your offering, and then click Change Feature Opt-In.
3. On the Opt-In page, click the Edit Features icon.
4. On the Edit Features page, select the Enable option for any feature you want to opt-in to. If the Enable column includes an Edit icon instead of a check box, then click the icon, select your feature options, and click Save and Close. 
5. Click 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.

Feature Summary

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 
  • Save
  • Submit
  • Copy

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

• Work area in Order Management Cloud
• Direct web service integration through SOA, REST, ADF, or HVOP
• File based data import and batch import through the FBDI template
• Business 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.

• 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 Training
• Oracle 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.

MANAGE ORDER MANAGEMENT PARAMETERS

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

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 > your apps service area of interest > REST API).  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

Watch Order Management Infrastructure Enhancements Readiness Training

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

Role Information

• Job Role:
  • Order Entry Specialist

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

• Oracle SCM Cloud: Modeling Configurations for SCM guide, available on the Oracle Help Center.
• Watch 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 details
• Create and edit rule folders
• Edit 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 > your apps service area of interest > REST API).  If you are new to Oracle's REST services you may want to begin with the Quick Start section.

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 REST API for Oracle Supply Chain Management Cloud documentation, available on the 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 requests
• Restore intermediately saved interactive configurations
• Retrieve immediate runtime child nodes of a configuration node
• Retrieve runtime attributes of a specific node in the root model or a mandatory reference model
• Select and set the quantity of a node in the root and mandatory reference models
• Update the value of a supplemental node
• Additional error messages and exception handling

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > REST API).  If you are new to Oracle's REST services you may want to begin 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 FinishConfigurationFlag attribute is set to false, to indicate that this resource will be an interactive 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\"}]",

    "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 ConfigutrationId which identifies the newly created interactive configuration, in addition to the ConfigurationSessionToken attribute which will be needed as a HTTP header attribute for any subsequent interaction with this configuration.

Key Resources

Watch Manage Configurations Interactively Using a REST Service Readiness Training

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

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.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > REST API).  If you are new to Oracle's REST services you may want to begin 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 Supply Chain Management Cloud guide on the Oracle Help Center > Supply Chain Planning > REST API: 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 > your apps service area of interest > REST API).  If you are new to Oracle's REST services you may want to begin 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.

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 Oracle Help Center > Supply Chain Planning > REST API: Supply Chain Management.

Role Information

To use this feature, the following is required:

• Job Role:
  • Order Promising Manager