Update 22C

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	Product	Feature	Notes
10 AUG 2022	Order Management	Specify the Orchestration Process When You Import Through REST API	Updated document. Revised feature content.
20 JUL 2022	IMPORTANT Actions and Considerations	Price Request SOAP Service	Updated document. Changed target removal of service to 23D.
17 JUN 2022			Created initial document.

Overview

HAVE AN IDEA?

We’re here and we’re listening. If you have a suggestion on how to make our cloud services even better then go ahead and tell us. There are several ways to submit your ideas, for example, through the Ideas Lab on Oracle Customer Connect. Wherever you see this icon after the feature name it means we delivered one of your ideas.

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.

DISCLAIMER

The information contained in this document may include statements about Oracle’s product development plans. Many factors can materially affect Oracle’s product development plans and the nature and timing of future product releases. Accordingly, this Information is provided to you solely for information only, is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described remains at the sole discretion of Oracle.

This information may not be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates. Oracle specifically disclaims any liability with respect to this information. Refer to the Legal Notices and Terms of Use for further information.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle SCM Cloud: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

Oracle Cloud Applications delivers new updates every quarter. This means every three months you'll receive new functionality to help you efficiently and effectively manage your business. Some features are delivered Enabled meaning they are immediately available to end users. Other features are delivered Disabled meaning you have to take action to make available. Features delivered Disabled can be activated for end users by stepping through the following instructions using the following privileges:

• Review Applications Offering (ASM_REVIEW_APPLICATIONS_OFFERINGS_PRIV)
• Configure Oracle Fusion Applications Offering (ASM_CONFIGURE_OFFERING_PRIV)

Here’s how you opt in to new features:

1. Click Navigator > My Enterprise > New Features.
2. On the Features Overview page, select your offering to review new features specific to it. Or, you can leave the default selection All Enabled Offerings to review new features for all offerings.
3. On the New Features tab, review the new features and check the opt-in status of the feature in the Enabled column. If a feature has already been enabled, you will see a check mark. Otherwise, you will see an icon to enable the feature.
4. Click the icon in the Enabled column and complete the steps to enable the feature.

In some cases, you might want to opt in to a feature that's not listed in the New Features work area. Here's how to opt in:

1. Click Navigator > My Enterprise > Offerings.
2. On the Offerings page, select your offering, and then click Opt In Features.
3. On the Opt In page, click the Edit Features (pencil) icon for the offering, or for the functional area that includes your feature.
4. On the Edit Features page, complete the steps to enable the feature.

For more information and detailed instructions on opting in to new features for your offering, see Offering Configuration.

Opt In Expiration

Occasionally, features delivered Disabled via Opt In may be enabled automatically in a future update. This is known as an Opt In Expiration. If your cloud service has any Opt In Expirations you will see a related tab in this document. Click on that tab to see when the feature was originally delivered Disabled, and when the Opt In will expire, potentially automatically enabling the feature. You can also click here to see features with Opt In Expirations across all Oracle Cloud Applications.

Feature Summary

Collaboration Messaging Framework

Collaboration Messaging Framework

Retrieve Large Purchase Order Payloads for B2B Messaging

Configure Oracle Collaboration Messaging Framework to process large purchase orders (typically more than 2,000-lines) when you initiate B2B communication. The payload for a large purchase order is retrieved in small parts from Oracle Purchasing and then combined and delivered as one purchase order, resulting in improved performance.

After you enable the feature, enter a value in the Large PO Processing section of the Manage Collaboration Messaging Configuration page in the Large PO Minimum Line Count field to specify the minimum number of lines in a large PO. Then enter a value in the PO Lines Retrieved in a Single Query field to specify the number of lines to retrieve from Oracle Purchasing in each part (1000 lines by default). The values you set in the Large PO Delivery Duration (30 minutes by default) and Large PO Delivery Attempt Interval (3 minutes by default) fields indicate how long and how often to attempt delivery of the PO.

NOTE: This feature was also made available in the May monthly update of 22B.

Large Purchase Order Processing in Manage Collaboration Messaging Configuration

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Order Management

Tips And Considerations

In general, a purchase order with more than 2,000 lines is considered a large purchase order, but you can determine the minimum line count for your large purchase orders based on your specific business needs.

Key Resources

• Oracle Supply Chain Management Cloud: Configuring and Managing B2B Messaging guide available on Oracle Help Center.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned this predefined job role can access this feature:
  • B2B Administrator  (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)

• Users who are assigned configured job roles that contain this privilege are able to access this feature:
  • Manage Collaboration Messaging Configuration (CMK_MANAGE_COLLAB_MESG_CONFIG_PRIV)

Send UBL PEPPOL Invoice Responses to Suppliers

Use the new predefined message definition UBL-2-1-InvoiceApplicationResponse-Out to send details about rejected invoices in the UBL PEPPOL format to your suppliers.

Enable the procure-to-pay business process to exchange the associated document, Invoice Acknowledgment-Outbound.

Set up this message definition as an outbound collaboration message for a trading partner and then associate the trading partner, and the Invoice Acknowledgment-Outbound document with a supplier using the Manage Supplier B2B Configuration task in the Collaboration Messaging work area.

UBL-2-1-InvoiceApplicationResponse-Out Message Definition

Enables automated invoice status communication using the UBL PEPPOL application response message.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Configuring and Managing B2B Messaging for Oracle Applications Cloud guide available on the Oracle Help Center.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles can access this feature:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Manage B2B Supplier Trading Partners (CMK_B2B_SUPPLIER_TRADING_PARTNERS_PRIV)
  • Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)

Order Management

Order Management

Use Extensible Flexfields in Approval Rules

Before update 22C, you can't use an extensible flexfield as part of the condition in an approval rule. Starting in update 22C, now you can.

Assume some of your customers are government organizations and some aren't. You need to indicate whether the customer is a government organization when you create the sales order, so you create an extensible flexfield segment named Government Customer on the order header.

You then set up an order approval rule that does a compliance check to make sure the order meet's the government's various purchasing requirements.

If the governmentCustomer attribute on the order header is equal to Yes, then do compliance.

For example:

Approval Rule Condition

With this feature, you can use a flexfield to meet your specific requirements and improve the efficiency for your order approval flow.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You must synchronize each time you modify your flexfield set up.

1. Create or modify your flexfield.
2. Go to the Setup and Maintenance work area, then go to the task.

• Offering: Order Management
• Functional Area: Customers
• Task: Manage Task Configurations for Supply Chain Management

3. In the BPM Worklist area, search for SalesOrder, then click ApprovalHumanTask.
4. Click Configuration. If you have modified your flexfield set up, then you will see a warning:

5. Click Start Synchronization and wait until the message disappears.
6. Create a new approval rule or modify an existing one that uses your flexfield.

Key Resources

• Overview of Setting Up Approval
• Guidelines for Setting Up Your Approval Task
• Overview of Using Extensible Flexfields in Order Management
• Get Approvals for Sales Orders

Role Information

• Order Manager
• Order Entry Specialist

Specify the Orchestration Process When You Import Through REST API

Improve performance and decrease the time it takes to create a sales order. You can now specify the orchestration process name when you import a sales order through REST API. Before this update, you had to use a process assignment rule to specify which orchestration process to use when fulfilling an order line. You no longer have to run that rule. You can also use an order management extension to specify the orchestration process name.

Use this feature when you know which orchestration process you want to use and don't have complex business logic that requires you to select from different orchestration processes according to attribute values from the sales order.

If you specify the orchestration process name for any line in the sales order, then Order Management won't call the assignment rule for any line in the order. So you must specify the orchestration process name for each line in the order.

Steps to Enable

REST API

Include this code on the order line in your salesOrdersForOrderHub payload:

"OrchestrationProcessName": "ManualSchedulingProcess", // <= Use this property to specify the orchestration process name

Order Management Extension

If you import through REST API, then use the OrchestrationProcessName attribute in your extension to specify the orchestration process name on the order line, and use the On-Save or On Start of Submission Request extension point. For example:

line.setAttribute("OrchestrationProcessName","ManualSchedulingProcess");

For details, see Overview of Creating Order Management Extensions.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Order Entry Specialist (ORA_FOM_ORDER_ENTRY_SPECIALIST_JOB)
  • Order Manager (ORA_DOO_ORDER_MANAGER_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Get Sales Orders Using REST Services (FOM_SALES_ORDER_REST_GET_PRIV)
  • Create Sales Orders Using REST Services (FOM_SALES_ORDER_REST_POST_PRIV)
  • Update Sales Orders Using REST Services (FOM_SALES_ORDER_REST_PATCH_PRIV)
  • Delete Sales Orders Using REST Services (FOM_SALES_ORDER_REST_DELETE_PRIV)
  • Get Sales Order Requests Using REST Services (FOM_SALES_ORDER_REQUEST_REST_GET_PRIV)
  • Create Sales Order Requests Using REST Services (FOM_SALES_ORDER_REQUEST_REST_POST_PRIV)
  • Update Sales Order Requests Using REST Services (FOM_SALES_ORDER_REQUEST_REST_PATCH_PRIV)
  • Delete Sales Order Requests Using REST Services (FOM_SALES_ORDER_REQUEST_REST_DELETE_PRIV)

Use Order Management Extensions to Apply Holds on Order Lines

Use an order management extension to apply a hold on an order line. You can use the new applyHold method with the On Save or the On Start of Submission event to create a hold on an order line in a new sales order.

You can use the applyHold method only with a new sales order. You can't use it with a change order.

Here's an example that places a hold on each order line that has a quantity that's greater than 10.

def lines = header.getAttribute("Lines");

while(lines.hasNext()) {

def line = lines.next();

BigDecimal qty = line.getAttribute("OrderedQuantity");

if(qty.compareTo(new BigDecimal(10)) > 0) {

def hold = line.applyHold("DOO_RSRV"); // create a hold and use the DOO_RSRV hold code

hold.setAttribute("Comments", "Hold these order lines so we can review and approve them.");

}

}

where

applyHold("hold_code") specifies the applyHold method and the hold code to use when applying the hold. You must enclose the hold code with double quotation marks (" ").

Use an order management extension when you have a specific business requirement that you can't meet through Oracle Order Management's predefined hold behavior.

Steps to Enable

You don't need to do anything to enable this feature.

Key Resources

• Guidelines for Setting Up Holds on Sales Orders
• Overview of Creating Order Management Extensions

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned this predefined job role are automatically able to access this feature:
  • Order Administrator (ORA_DOO_ORDER_ADMINISTRATOR_JOB)

• Users who are assigned a configured job role that contains this privilege can access this feature:
  • Manage Order Management Extensions (FOM_MANAGE_ORDER_MANAGEMENT_EXTENSIONS_PRIV)

Selected Order Management Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Order Management works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

CTO Item Description Appears on Purchase Orders

Before update 22C, the Description attribute on the purchase order for a configure-to-order item displayed the item number instead of the description. This happens only in a back-to-back flow. After you update to 22C, the Description attribute contains the item description, not the number.

Oracle reference: 34082567

Steps to Enable

You don't need to do anything to enable this feature.

Channel Revenue Management

Deductions and Settlement

Provides research, administration, analysis, and settlement functionalities to quickly resolve deductions and settle claims, improving customer relationships and overall financial performance.

Resolve and Settle a Customer Claim Using a REST Service

Use a REST API to settle a customer claim. You can get and update details of claims, resolve claims, and settle claims in Receivables. REST support for manual claims is already available.

Resolve and settle customer claims with a REST service for improved productivity and effectiveness in taking control of customer deductions.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Order Management

1. You must opt in to the functional area named: Channel Revenue Management functional area. Then opt in to the feature named: Deductions and Settlement.
2. For Deductions and Settlement only:
   1. Under the offering named: Financials and functional area named: Receivables, navigate to the task named: Manage Receivables System Options. Search for and select your business unit. Click the Cash Processing tab. Select the Enable channel revenue management integration check box and click Save.

Key Resources

• Watch Deductions & Settlement Continuous Improvement Readiness Training.
• For more information on Channel Revenue Management, refer to the Oracle Cloud Readiness content for Order Management.
• For more information on the Channel Revenue Management Integration with Receivables, refer to the Oracle Cloud Readiness content for Financials.
• Oracle SCM Cloud: Using Oracle Channel Revenue Management Cloud, available on the Oracle Help Center.
• Oracle SCM Cloud: Implementing Oracle Channel Revenue Management Cloud, available on the Oracle Help Center.
• Oracle SCM Cloud: REST API for Oracle SCM Cloud, available on the Oracle Help Center.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning these predefined job roles or your own configured job roles.

• Users who are assigned this predefined job role are automatically able to access this feature:
  • Channel Claims Manager (ORA_CJM_CLAIMS_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Manage Customer Claims using REST Service (CJM_MANAGE_CHANNEL_CUSTOMER_CLAIM_REST_SERVICE_PRIV)

Settle an Invoice Deduction Claim with a Chargeback

Settle an invoice deduction claim with a chargeback. This settlement method is used to settle invalid invoice deductions. Chargebacks can't be combined with other settlement methods.

When an invoice based short payment is determined as invalid, settle it with a chargeback invoice in Receivables.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Order Management

1. You must opt in to the functional area: Channel Revenue Management functional area. Then opt in to the feature named: Deductions and Settlement.
2. For Deductions and Settlement only:
   1. Under the offering:  Financials and functional area: Receivables, navigate to the task: Manage Receivables System Options. Search for and select your business unit. Click the Cash Processing tab. Select the Enable channel revenue management integration check box and click Save.

Chargeback specific setup:

1. Configure AR to support chargeback invoices including Transaction Types and Chargeback Reasons.
2. Configure Claim Types to map to a Transaction Type in AR.
3. Configure Claim Reasons to map to a Chargeback Reason in AR.
4. Enable the Chargeback settlement method in the Invoice Deduction claim source setup.

Tips And Considerations

Chargebacks are good for closing out existing invoices with invalid short payments; however, they can also delay the closure and collection of the invalid deduction.  An alternate business process would be to keep the claim open, contact the customer informing them their short payment is invalid and request a debit memo from them.  When the debit memo from the customer is received, it's matching open credit memo can be applied close the invalid claim.

Key Resources

• Watch Deductions & Settlement Continuous Improvement Readiness Training.
• For more information on Channel Revenue Management, refer to the Oracle Cloud Readiness content for Order Management.
• For more information on the Channel Revenue Management Integration with Receivables, refer to the Oracle Cloud Readiness content for Financials.
• Oracle SCM Cloud: Using Oracle Channel Revenue Management Cloud, available on the Oracle Help Center.
• Oracle SCM Cloud: Implementing Oracle Channel Revenue Management Cloud, available on the Oracle Help Center.
• Oracle SCM Cloud: REST API for Oracle SCM Cloud, available on the Oracle Help Center.

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning these predefined job roles or your own configured job roles.

• Users who are assigned this predefined job role are automatically able to access this feature:
  • Channel Claims Manager (ORA_CJM_CLAIMS_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Manage Customer Claims (CJM_MANAGE_CUSTOMER_CLAIMS_PRIV)

Supply Chain Orchestration

Use Service Mappings to Extend Supply Chain Orchestration's Integration with Manufacturing

Use a service mapping to help you integrate Oracle applications. Use the service mapping to help meet your specific integration requirements in your back-to-back flow. Create a sales order in order management, orchestrate supply in supply chain orchestration, then create a work order in manufacturing. As an option, use an extensible flexfield to integrate data that's specific to your implementation. You can also use a service mapping to integrate data that travels from planning and inventory, to supply chain orchestration, and then to manufacturing.

For example, here's a service mapping that uses the WorkOrderRequest entity in the ManufactureRequestSource source to send a request to create a work order from Supply Chain Orchestration to manufacturing:

Modify supply orchestration data so they meet your own conditional requirements.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Manufacturing and Supply Chain Materials Management

1. Get the privileges you need to manage service mappings and algorithms.
2. Go to the Supply Chain Orchestration work area, click Tasks, then click one of:

• Manage Service Mappings
• Manage Algorithms

3. Create service mappings and algorithms.

Tips And Considerations

• Make sure your integration can send the validations that Manufacturing applies. Your import payload might be fine, but Manufacturing might not accept the request. For example, if the Name attribute and Id attribute don't reference the same customer, then Manufacturing uses only Id.

• Check for null conditions when you write expressions in your algorithms, especially when you query more than one request line. A null condition at runtime might create errors.

• If you encounter an error, fix it, then use the Supply Chain Orchestration work area to resubmit your request.

Role Information

• Use these predefined privileges to set up this feature:
  • Manage DOS Service Mappings
  • Manage DOS Algorithms
  • Administer Sandbox
  • View Modified Data, so you can view the runtime results

Use Supply Chain Orchestration to Add New Requisition Lines to Open Purchase Orders

Use this feature to add a new requisition line to an open purchase order instead of creating a new one. Use it when an Oracle application sends a request to Supply Chain Orchestration to create a purchase request to get goods or services from your supplier. Use this feature with these Oracle applications: Oracle Planning, Oracle Order Management, Oracle Inventory Management, or Oracle Manufacturing.

This feature automatically manages change that happens on each purchase order and in the Oracle application. It keeps your purchase orders, sales orders, and work orders synchronized with each other.

Here's how it works:

1. The Oracle application sends a request to Supply Chain Orchestration to create a purchase request.
2. Supply Chain Orchestration sends a request to Oracle Procurement, and Procurement creates a purchase request.
3. You add the purchase request to an open purchase order.
4. Supply Chain Orchestration automatically manages each change that it receives from the Oracle application. It automatically keeps the purchase orders, sales orders, and work orders synchronized in your back-to-back, contract manufacturing, and outside processing flows.

You don't have to enable the Use Supply Chain Orchestration to Add New Requisition Lines to Open Purchase Orders feature, but there is another feature in procurement that you do have to enable. Here's how:

1. Go to the Setup and Maintenance work area, select the Procurement offering, then click Change Feature Opt In.
2. In the row that has Purchasing in the Name column, click the pencil.
3. Enable the Add New Approved Requisitions to Existing Open Purchase Orders feature, then click Done.

Consolidate and maximize your open purchase orders. Avoid having unnecessary purchase orders for each of your suppliers.

Steps to Enable

You don't need to do anything to enable this feature.

Tips And Considerations

You can add a purchase request for planning or min-max processing to any open purchase order.

If you need to add a new requisition line to an open purchase order, then disable the Automatically Generate Orders option in the blanket purchase agreement for your item.

You can add a purchase request:

• In your back-to-back flow to any open purchase order except one that involves contract manufacturing or outside processing.
• For contract manufacturing only to a purchase order that's open for contract manufacturing.
• For outside processing only to a purchase order that involves outside processing.
• For a configure-to-order item only to a purchase order for a configure-to-order item.

Key Resources

• Using Supply Chain Orchestration

Role Information

if you have any of these predefined job roles, then you can automatically use this feature.

• Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
• Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)

If you're maintaining your own job role, no new privileges were introduced to support this feature.

Use FBDI to Firm a Transfer Order

Use this feature to firm a transfer order when you use the Import Supply Order FBDI (file-based data import) template to create or update a transfer order.

You can already use the Supply Request REST API to firm a transfer order when you update the order. Starting with update 22C, you can also use the Import Supply Order (DosSupplyOrderImportTemplate) FBDI template to do this. The template includes a new column, Firm Planned Flag (FIRM_PLANNED_FLAG), to support firming a transfer order.

NOTE: FBDI templates aren't currently supported on Mac computers.

Steps to Enable

Download and review the latest Import Supply Order import template in the File-Based Data Import for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center. To import data using the template, follow the instructions in the "Load Data into Tables" topic. 

Role Information

You have a couple of options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles can access this feature:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
  • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Process Supply Order Interface (DOS_PROCESS_SUPPLY_ORDER_INTERFACE_PRIV)
  • View Supply Orders (DOS_VIEW_SUPPLY_ORDERS_PRIV)
  • Manage Supply Request Exceptions (DOS_MANAGE_SUPPLY_REQUEST_EXCEPTIONS_PRIV)
  • View Supply Order Exceptions and Status (DOS_VIEW_SUPPLY_ORDER_EXCEPTIONS_AND_STATUS_PRIV)
  • Manage Inventory Transfer Order (INV_MANAGE_INVENTORY_TRANSFER_ORDER_PRIV)

If you're maintaining your own job roles, no new privileges were introduced to support this feature.

Selected Supply Chain Orchestration Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Supply Chain Orchestration works. This isn't a full list of all the bug fixes in this update. This list includes the bug fixes that can cause a noticeable change in application behavior.

Supply Request Indicates Which Lines Are In Error

Before update 22C, if you used the Create Supply Request page in the Supply Chain Orchestration work area to create a transfer request, and if there was a problem with a line in your request, then the work area displayed an error message but didn't indicate which lines were in error. Orchestration proceeded to create the transfer order for the lines with no errors. If you fixed the lines that were in error, didn't remove the lines that were already created, and then resubmitted the request, orchestration created another transfer order for the same lines that already had a transfer order. The same problem happened if you used the Manage Item Quantities page in the Inventory Management work area to create the request.

After you update to 22C, if there’s a problem with one or more lines in the request, then orchestration doesn’t create a transfer order for any lines. The work area displays an error icon for each line that has a problem, and you can click the icon to view a detailed message. You can fix the line or remove it, and then resubmit the request.

Oracle reference: 33494183

Steps to Enable

You don't need to do anything to enable this feature.

Global Order Promising

High-Volume Order Promising

Order promising is a critical business process that must scale with demand and continue to operate even if hardware failures occur. Recent changes to Oracle Fusion Cloud Global Order Promising provide a scale-out architecture for availability checking and scheduling requests across a horizontal grid, enhancing capacity and resilience. The new architecture also reduces operational overhead, making supply and reference data updates immediately available, and eliminating the need to refresh/restart the order promising server.

Migration to the new architecture is continuing over several updates. In the interim, Oracle Global Order Promising will automatically route some special case requests to the prior memory-resident C++-based solution.

After you opt in to the feature named High-Volume Order Promising, you can use the feature described in this section.

Manage Supplier Capacity for Assemble-to-Order Items by Model

If contract manufacturers build assemble-to-order items for your enterprise, then it’s usually not feasible to determine the supplier’s production capacity for a specific configuration when an order is scheduled. Because a supplier typically uses the same capacity to produce a variety of configurations, loading and consuming supplier capacity according to the production calendar for the assemble-to-order model from the approved supplier list (ASL) produces more accurate results. It’s also much easier to maintain supplier capacity information at a model level.

Note that you can still use a configured item’s lead time and calendar from the ASL if you need to adjust availability dates for specific configured items.

Achieve more accurate scheduling results for assemble-to-order items produced by contract manufacturers by managing supplier capacity at the model level, rather than for specific assemble-to-order configurations.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

Tips And Considerations

When you opt in to use this feature, you must opt in to the feature named: High-Volume Order Promising. Opting in to the High-Volume Order Promising feature also enables the feature described here. If you previously opted in to the High-Volume Order Promising feature, then this feature is automatically enabled.

Role Information

• Users who are assigned following predefined job roles are automatically able to access this feature:
  • Order Promising Manager (ORA_MSC_ORDER_PROMISING_MANAGER_JOB)

Use Real-Time On-Hand and In-Transit Supply Data for Available-to-Promise Calculations

High-volume retail and wholesale distribution businesses may schedule sales orders for thousands of items across hundreds or thousands of locations. To reduce the data processing volume and latency of collecting supply information for millions of item-locations, Oracle Global Order Promising can now access supply information directly from Oracle Supply Chain Execution applications in real time. With this access, Global Order Promising schedules available-to-promise supplies using up-to-the-second quantities for on-hand and in-transit supply.

Note that availability checking and scheduling capable-to-promise and profitable-to-promise requests continue to rely on collected data.

Provide more accurate available-to-promise dates across millions of item-location combinations by accessing on-hand and in-transit transaction data from Oracle Supply Chain Execution applications in real time.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

Tips And Considerations

• When you opt in to use this feature, you must opt in to the feature named: High-Volume Order Promising. Opting in to the High-Volume Order Promising feature also enables the feature described here. If you previously opted in to the High-Volume Order Promising feature, then this feature is automatically enabled.

• This solution is intended for use in businesses that rely heavily on meeting customer orders optimally by targeting fragmented supply across warehouses and distribution centers of their supply chain network to the extent possible. This solution doesn't recommend procurement or manufacturing new supply for fulfilling customer demand.

• Only the specific supply types On Hand and In Transit supplies are considered as available-to-promise supply by this solution. Any future supplies, including purchase orders and work orders, aren't considered. Only reservations against supported supply types are considered for supply-demand netting.

Role Information

• Users who are assigned the following predefined job role are automatically able to access this feature:
  • Order Promising Manager (ORA_MSC_ORDER_PROMISING_MANAGER_JOB)

Consume Supply Used for Counter Sales

In industries such as wholesale distribution, sales personnel fulfill some orders immediately from stock on hand. Oracle Fusion Cloud Order Management doesn’t require picking and shipping for these over-the-counter orders.

The Global Order Promising component of Oracle Fusion Cloud Order Management now supports this fulfillment mode when promising orders using real-time transactional supply. It adjusts available supply balances to reflect the quantities withdrawn from local stock at the facility for counter sales.

Schedule more accurately by adjusting available supply to reflect item quantities consumed for over-the-counter sales orders.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

Tips And Considerations

When you opt in to use this feature, you must opt in to the feature named: High-Volume Order Promising. Opting in to the High-Volume Order Promising feature also enables the feature described here. If you previously opted in to the High-Volume Order Promising feature, then this feature is automatically enabled.

Key Resources

• The Plan Counter Sales Orders readiness training available on Oracle Cloud Readiness for Supply Planning.

• The Reduce Inventory When a Sales Order Doesn't Require Picking or Shipping readiness training available on Oracle Cloud Readiness for Order Management

Role Information

• Users who are assigned the following predefined job role are automatically able to access this feature:
  • Order Promising Manager (ORA_MSC_ORDER_PROMISING_MANAGER_JOB)

Multilevel Allocation In Order Promising

Allocation rules help you honor commitments and distribute high-demand items more fairly by ensuring that a specified quantity or percentage of supply is available to meet demand. When you’re opted in to this feature, enhanced supply allocation rules that use a hierarchy of attribute-based nodes to balance the allocation of supply across your network are enabled. Child allocations share supply allocated to the parent node when needed.

After you opt in to the feature named High-Volume Order Promising, opt in to the feature named Multilevel Order Promising. Then you can use the features described in this section.

Multilevel Allocation in Order Promising

Allocation rules help you honor commitments and distribute high-demand items more fairly by ensuring that a specified percentage of supply is available to meet demand. When you're opted in to this feature, enhanced supply allocation rules that use a hierarchy of attribute-based nodes to balance the allocation of supply across your network are enabled. Child allocations share supply allocated to the parent node when needed.

Fairly allocate supplies for high-demand items with constrained availability within a framework supporting up to a three-level user-defined hierarchy of segments. Define supply allocation percentages for different segments.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

To use this feature, you must opt in to both the High-Volume Order Promising and Multilevel Allocation in Order Promising features. After you opt in to the High-Volume Order Promising feature, then you will be able to opt in to the Multilevel Allocation in Order Promising feature.

After opt in is enabled, perform these steps to leverage this feature.

1. Load Attributes and Attribute-Value relationships using the ScpPlanningAttributeValuesImportTemplate.xlsm file-based data import (FBDI) file template available from the File-Based Data Import (FBDI) for Oracle SCM guide on Oracle Help Center.

2. Navigate to the Plan Inputs work area > Manage Planning Attributes task > Allocation Attributes tab to set the Allocation Name hierarchy

3. Navigate to the Plan Inputs work area > Manage Planning Attributes task > Define Planning Attributes Mapping to select the Extensible Flexfields in the Sales Order Flexfields framework to map to the allocation names

4. Navigate to the Plan Inputs work area> Manage Supply Allocation Rules task to define allocation percentages for the nodes in the Allocation hierarchy

5. During order creation, for the earmarked extensible flexfields, select the allocation node names of each level in the hierarchy corresponding to the intended target allocation

Tips And Considerations

• While defining allocation rules, ensure that the sum of percentage allocation sums up to a hundred percent.

• While creating orders, ensure that the nodes selected in the extensible flexfields are aligned with the allocation node hierarchy defined and loaded through the file-based data import process.

• While leveraging the feature for consideration of shipped sales orders history, ensure that the interval defined for collection of shipped sales orders is aligned with the campaign duration. In addition, ensure that the allocation percentages defined for all of the allocation nodes in the allocation rule are maintained as stable values for the entire duration of the campaign.

Key Resources

• The Allocate Supply Based on Plan Attributes readiness training available on Oracle Cloud Readiness for Supply Planning

• The Control the Range of Shipment History to Include in Demand Class Allocations readiness training available on Oracle Cloud Readiness for Order Management

• The File-Based Data Import (FBDI) for Oracle SCM guide on Oracle Help Center

Role Information

You have a couple options for giving people access to this feature, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned following predefined job roles are automatically able to access this feature:
  • Order Promising Manager (ORA_MSC_ORDER_PROMISING_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Manage Allocation Attributes (MSC_MANAGE_ALLOCATION_ATTRIBUTES_PRIV)
  • Manage Allocation Data (MSC_MANAGE_ALLOCATION_DATA_PRIV)

Allocate Supply Based on Attributes in Order Promising

By default, Oracle Global Order Promising schedules order lines sequentially as they’re submitted, which may allow a few orders to consume all of the available supply. To distribute high-demand items more fairly to lower-priority customers, regions, or channels, you can now allocate a percentage or specified quantity of supply each week to order lines based on plan attributes. Order lines that match the values of the allocation attributes will have access to the allocated supply.

You can also control the date range of historical shipments to be included in the consumption of a supply allocation.

Honor commitments and distribute high-demand items more fairly by ensuring that a quantity or percentage of supply is allocated to sales orders with specific attribute values.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

Tips And Considerations

To use this feature, you must opt in to both the High-Volume Order Promising and Multilevel Allocation in Order Promising features. After you opt in to the High-Volume Order Promising feature, then you will be able to opt in to the Multilevel Allocation in Order Promising feature.

Access a Parent Node If Supply from a Child Allocation Node Is Depleted

You can define allocation rules in a hierarchy in which child allocations can share supply allocated to the parent node when needed.  For example, to better balance the use of supply to meet regional demand, you could use stock allocated for the European region for the country of Spain if the stock allocated to that country runs out.

The allocation hierarchy can have up to three levels. Supply is first consumed from the lowest-level node in the hierarchy in a given week. When that supply is depleted, supply allocated to the parent node for that same week is consumed.

Improve balance of supply across your network by allocating supply from a shared parent node when more-specific allocations are depleted.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

Tips And Considerations

To use this feature, you must opt in to both the High-Volume Order Promising and Multilevel Allocation in Order Promising features. After you opt in to the High-Volume Order Promising feature, then you will be able to opt in to the Multilevel Allocation in Order Promising feature.

Redeploy Unused Supply from Lower-Priority to Higher-Priority Allocations If Needed

Some nodes in your allocation hierarchy may be lower priority than others. In this case, rather than delay demand for a higher-priority allocation that was depleted (including its parent allocations), it’s better to take some supply from one or more lower-priority allocations, also known as redeployment.

You can assign a relative priority to each node to determine which nodes are eligible for redeployment. Consumption begins with the lowest priority sibling node in the hierarchy, and then proceeds from there if needed to higher priority sibling nodes until supply from all those with a lower priority than the original is consumed. From there, allocations from lower priority parent nodes in the hierarchy may also be accessed.

You can also specify a minimum percentage or quantity of an allocation that isn’t available for this redeployment (sometimes also called stealing) to preserve at least some of the allocation for demands that are specific to that allocation node.

To meet high-priority demand whenever possible, use lower priority allocations to fulfill orders after higher-priority allocations have been consumed.

Steps to Enable

Use the Opt In UI to enable this feature. For instructions, refer to the Optional Uptake of New Features section of this document.

Offering: Supply Chain Planning

Tips And Considerations

To use this feature, you must opt in to both the High-Volume Order Promising and Multilevel Allocation in Order Promising features. After you opt in to the High-Volume Order Promising feature, then you will be able to opt in to the Multilevel Allocation in Order Promising feature.

IMPORTANT Actions and Considerations

From time to time, Oracle replaces existing Cloud service features with new features, or removes existing features. Replaced features may be put on a path to removal. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

This section identifies the features in this Cloud service that have been replaced or will be removed.

Product	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
Pricing	Price Request SOAP Service	23D	Document Prices REST API	19A	No additional enhancements have been made to the Price Request SOAP service since update 19A. Until the SOAP service is removed in 23D, it will continue to work, but you should migrate to the Document Prices REST API at your earliest convenience. For details about the Document Prices REST API, refer to the REST API for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.