Cloud Readiness / Oracle Order Management Cloud
What's New
Expand All


  1. Update 21B
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
    1. Order Management
        1. Specify How Long to Wait Before Giving Control to Users After Submitting Sales Orders
        2. Use Credit Card Tokens to Improve Security When You Import Sales Orders Through REST API
        3. Recover Sales Orders That Fail When Updating Advanced Shipment Notices in Drop Ship Flows
    2. Configurator
        1. Revise the Quantity of an Existing Configuration Using a REST Service
        2. Unrelease Models in Production from the Configurator Modeling Work Area
    3. Channel Revenue Management
      1. Supplier Channel Management
        1. Manage Supplier Rebate Programs
        2. Upload Inventory Receipts
        3. Calculate Accruals for Supplier Rebate Programs
        4. Create Manual Accrual Adjustments for Supplier Rebate Programs
        5. Manage Claims for Supplier Rebate Programs
        6. Account for Supplier Rebate Programs Accruals and Claims
        7. Include Supplier Rebate Programs in the Supplier Checkbook
    4. Global Order Promising
        1. Schedule Sales Orders for Back-to-Back Items Using Transactional Supply
        2. Extract Available Sources for an Item Organization Using a REST Service

Update 21B

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
15 APR 2021 Order Management Recover Sales Orders That Fail When Updating Advanced Shipment Notices in Drop Ship Flows Updated document. Delivered feature in update 21B.
15 APR 2021 Configurator Unrelease Models in Production from the Configurator Modeling Work Area Updated document. Revised feature information.
19 MAR 2021     Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

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. For details about how to compare your configured job roles to predefined job roles and add security artifacts to your configured job roles, see the Security Console and Roles and Role Assignments chapters in the Oracle SCM Cloud: Securing SCM guide on the Oracle Help Center.

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.

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

Column Definitions:

Features Delivered Enabled

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.

Features Delivered Disabled = Action is needed 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
(Features 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.

Action is Needed BEFORE Use by End Users
(Features 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*

Order Management

Specify How Long to Wait Before Giving Control to Users After Submitting Sales Orders

Use Credit Card Tokens to Improve Security When You Import Sales Orders Through REST API

Recover Sales Orders That Fail When Updating Advanced Shipment Notices in Drop Ship Flows

Configurator

Revise the Quantity of an Existing Configuration Using a REST Service

Unrelease Models in Production from the Configurator Modeling Work Area

Channel Revenue Management

Supplier Channel Management

Manage Supplier Rebate Programs

Upload Inventory Receipts

Calculate Accruals for Supplier Rebate Programs

Create Manual Accrual Adjustments for Supplier Rebate Programs

Manage Claims for Supplier Rebate Programs

Account for Supplier Rebate Programs Accruals and Claims

Include Supplier Rebate Programs in the Supplier Checkbook

Global Order Promising

Schedule Sales Orders for Back-to-Back Items Using Transactional Supply

Extract Available Sources for an Item Organization Using a REST Service

Order Management

Specify How Long to Wait Before Giving Control to Users After Submitting Sales Orders

Specify the number of seconds to wait before giving control back to the user for sales orders that have a lot of order lines.

Improve your user's efficiency and experience. Give the user control to navigate away from the sales order while Order Management processes the submit instead of having to wait.

Steps to Enable

  1. Go to the Setup and Maintenance work area, then go to the task.
  • Offering: Order Management
  • Functional Area: Orders
  • Task: Manage Order Management Parameter
  1. On the Manage Order Management Parameters page, set the value for the Response Time in Seconds parameter.

Tips And Considerations

  • Response Time in Seconds doesn't come predefined with a value.

  • You can specify a value of 5 seconds to 240 seconds.

  • If you set a value, then Order Management returns control according to the time it takes to finish processing the submit, not according to the number of order lines.

  • If you don't set a value, then Order Management gives control back to the user only after it finishes submitting all the order lines in the order.
  • If Order Management finishes submitting the order to fulfillment before the time that you specify elapses, then Order Management displays the same success message or error message that it displays when you don't use Response Time in Seconds.

  • If Order Management doesn't finish submitting the order to fulfillment before the time that you specify elapses, then the Order Management work area displays a dialog that you can use to navigate away from the sales order while Order Management continues to process the submit. If you're still on the order page, then you can refresh the page to get an updated order status. If you navigate away from the order page, then you can search for the sales order and get a status update. If you encounter an error or warning, you can edit the order or discard the draft just like you can if you don't set a value in the parameter.

  • This feature works only when you click Submit in the Order Management work area to create, revise, or cancel a sales order. It doesn't apply during order import.

  • This feature applies to all users and all business units.

Key Resources

  • Oracle Supply Chain Management Cloud: Implementing Order Management Guide, available on Oracle Help Center.

Role Information

  • Order Entry Specialist
  • Order Manager

Use Credit Card Tokens to Improve Security When You Import Sales Orders Through REST API

Order Management sends token details to Oracle Fusion Payments to validate, authorize and process the payment. You can send details about the credit card token on the order header and the order line. Use this feature to get the value that identifies the authorization request and the authorized amount from the CyberSource payment gateway.

Use these new attributes in your REST API payload.

Resource

Attribute

Description

payments

CardTokenNumber

Token number from the service that provides the token for the card number. If you import a token and an authorization, then you must include a value for CardTokenNumber.

payments

CardFirstName

First name of the card holder.

payments

CardLastName

Last name of the card holder.

payments

CardExpirationDate

Expiration date on the credit card. Provide a value in the format YYYY/MM/DD.

payments

CardIssuerCode

Abbreviation that identifies the organization that issues the card, such as Visa or MasterCard.

payments

MaskedCardNumber

Masked format that displays only the last four digits of a card number, and replaces all other digits with an X, for security purposes. The length of the value for MaskedCardNumber must match the length of the number on the card. For example, for a Visa card with number 4123456789012345, set MaskedCardNumber to XXXXXXXXXXXX2345.

payments

AuthorizationRequestId

Value that uniquely identifies the authorization request that you receive from the token service. If you don't want to use CardTokenNumber to authorize your import, then you must provide a value for AuthorizationRequestId or VoiceAuthorizationCode. If you provide a value for both of these attributes, then the import uses AuthorizationRequestId.

payments

VoiceAuthorizationCode

Abbreviation that identifies the voice authorization. If you don't want to use CardTokenNumber to authorize your import, then you must provide a value for AuthorizationRequestId or VoiceAuthorizationCode. If you provide a value for both of these attributes, then the import uses AuthorizationRequestId.

payments

PaymentServerOrderNumber

Number that identifies the card payment that Oracle Payment Server authorized.

payments

AuthorizedAmount

Amount that the token service authorized for the transaction. If you provide a value in the AuthorizationRequestId in your import payload, then you must also include a value for AuthorizedAmount.

Here's an example of a REST API payload that imports credit card details.

Example of a REST API Payload That Imports Credit Card Details

Here's a summary of how it works.

  1. You import your REST API payload.
  2. Order Management Cloud calls Oracle Fusion Payments.
  3. Payments communicates with CyberSource to validate and store the details that you import.
  4. Payments sends the Payment Transaction Extension Identifier to Order Management.
  5. To view credit card details, go to the Order Management work area, open your sales order, go to the Billing and Payment Details tab, then use the Payment Status dialog on the order line.

Payment Status Dialog on the Order Line

Meet the Data Security Standards (DSS) that the PCI Security Standards Council specifies. Specify exact, credit card details in a secure way to pay for the transaction. Use the card token without handling any sensitive credit card details.

Send a value that identifies the authorization request to your upstream source system.

Steps to Enable

Use the FOM_ENABLE_CARD_PAYMENT order profile. For details, see the Use Order Profiles to Control Order Management Behavior topic on Oracle Help Center.

Tips And Considerations

  • You can process credit card details in Oracle Fusion Applications only under controlled availability.
  • Credit card processing is available only for Oracle Fusion Applications services that use Oracle Fusion Payments.
  • Credit card processing is available only in data centers where Fusion Applications Payments is certified for Payment Card Industry Data Security Standard (PCI DSS v3.2.1).
  • You can use Oracle Fusion Payments only with payment gateways that can process tokens and credit card payments.  For details about the certified data centers and payment gateways that you can use, see Is Credit Card Processing Supported In Oracle Fusion Applications? (Doc ID 1949941.1) on My Oracle Support.
  • Send tokenization attributes for the credit card only when the Payment Method attribute equals Credit Card. If you don't use this method, then Order Management won't create the sales order.
  • The Credit Card Token attribute is required only if your import payload includes the token attributes for the credit card.

Warnings

  • You must never send credit card numbers to Oracle Fusion Cloud Service that aren't tokenized. If they aren't tokenized, then you must modify them so they don't reveal the actual card number. For example, you can truncate the number so that you send no more than the first six digits or the last four digits of the number.
  • You must never send the credit card data, including credit card tokens, outside the supported business flows through a file, attachment, email, descriptive flexfield, or any other attribute.

Key Resources

  • Oracle Supply Chain Management Cloud: Implementing Order Management Guide, available on the Oracle Help Center.

Role Information

  • Order Specialist Entry
  • Order Manager

Recover Sales Orders That Fail When Updating Advanced Shipment Notices in Drop Ship Flows

Oracle Order Management Cloud uses one of these flows to manage a drop shipment:

  • Advance Shipment Notice (ASN)
  • AP Invoice Match

Oracle Receiving Cloud raises a business event for these flows to publish the shipment details, and Order Management uses that event to update fulfillment details on the sales order.

In some situations, Order Management can’t process the event, the status on the sales order remains in Awaiting Shipping status, but the status on the purchase order is different depending on what fulfillment shipped.

What Fulfillment Shipped Status on the Purchase Order
The entire sales order Closed for Receiving
Only part of the sales order Open

Now, the status on the sales order isn't synchronized with the status on the purchase order. Currently, to fix this problem, you send an updated advance shipment notice through a web service payload to move the sales order to Awaiting Billing status, and then to invoicing.

Use this feature to prevent order lines from being stuck when Order Management processes an advance shipment notice.

Order Management will automatically attempt to fix the problem five times in approximately 120 minutes. Each attempt will try to recover from technical errors that occur in the environment when processing the advance shipment notice. If these retries fail, then you can use the Recover Errors scheduled process or the Recover Order action.

Steps to Enable

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

Tips And Considerations

You can only recover some errors when you use the Recover Order action. If you can't use Recover Order, then run the Recover Errors scheduled process.

Key Resources

See the Indicate an Ownership Change During Drop Ship topic, available on the Oracle Help Center.

Role Information

  • Order Administrator

Configurator

Revise the Quantity of an Existing Configuration Using a REST Service

Use a REST API to change the root quantity of an existing configuration and receive a new revision of that configuration. You can maintain the previous configuration and use the new revision going forward.

You can quote a single configured product to your customers and change the ordered quantity as the business requirements change when booking the order for your customers.

Steps to Enable

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

Tips And Considerations

Consider the following sample JSON input payload to revise the quantity of an existing configuration:

{

   "quantity": 3

}

This payload provides the quantity attribute that will be used when invoking the custom action reviseQuanity on an existing configuration.

Key Resources

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

Unrelease Models in Production from the Configurator Modeling Work Area

From the Configurator Models work area, you can now unrelease the latest version of models in production to revert to their previously released versions. Models can now be unreleased from workspaces containing modified snapshots. The set of models being unreleased no longer needs to include referring models.

Unrelease Models from a Released Workspace Within the Configurator Modeling Work Area

Watch a Demo

Enables a modeler to revert to the prior released version of a model, directly from the Configurator Models work area, when changes to a model may have been released inadvertently

Steps to Enable

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

Tips And Considerations

Unrelease is limited to future-effective models. Models released with a past-effective start date can't be unreleased.

Key Resources

Role Information

Users who are assigned configured job roles that contain these privileges are able to access this feature:

  • Configurator Workspace Release privilege (ORA_CZ_RELEASE_WORKSPACE_PRIV)

Channel Revenue Management

Supplier Channel Management

Creates and administers supplier trade programs, optimizing the execution and impact of programs and promotions across the demand chain.

Manage Supplier Rebate Programs

Manage your supplier rebate programs to define the rules of rebate promotions from your suppliers. You can create the supplier rebate program from a program type, which acts as a template for the program. You can define supplier terms including date effectivity on 1 of 5 date contexts (including requested delivery date, purchase order date, receiving transaction date, requested ship date, and actual ship date). You need to define the supplier site, product eligibility, as well as the discounts provided (either percent and amount-based rebates), and which of your bill-to or ship-to locations are eligible. You can also identify alternate distributors or supplier sites.

Supplier Rebate Program

Program Checkbook

Watch a Demo

  • Reduce margin leakage via visibility, so as to not miss claiming it.
  • Reduce administrative costs of vendor rebates via centralized supplier programs, record accruals, and automated channel accounting.
  • Empower purchasing to negotiate with a clear understanding of margins inclusive of supplier rebates.

Supplier Rebate

Supplier Rebate Flow

Business Process Diagram

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Additional Steps:

  • Manage User Statuses (for Program)
  • Manage Program Types

Key Resources

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:
    • Supplier Channel Manager (ORA_CJM_SUPPLIER_CHANNEL_MANAGER)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Manage Supplier Programs (CJM_MANAGE_SUPPLIER_PROGRAMS)
  • To use the REST service for this feature, the following job roles or privileges are required:
    • Job Role Name and Code:
      • Supplier Channel Manager (ORA_CJM_SUPPLIER_CHANNEL_MANAGER)
    • Privilege and Code:
      • Manage Channel Program Types using REST Service (CJM_MANAGE_CHANNEL_PROGRAM_TYPES_REST_SERVICE)
      • Manage Channel Programs using REST Service (CJM_MANAGE_CHANNEL_PROGRAMS_REST_SERVICE)

Upload Inventory Receipts

Load Transactions is a scheduled process that extracts and uploads receiving transactions, along with receipt and purchase orders details, via a delivered integration with Oracle Inventory Management Cloud and Oracle Procurement Cloud. This data is uploaded to a channel batch.

Load Transactions Scheduled Process

Watch a Demo

  • Faster realization from supplier rebates via automation
    • Reduced time to implement
    • Reduced cost of ownership

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Additional Steps:

  • Manage Channel Profile Options
    • Set your profile: Minimum Number of Days of Receipt Data from Initial Load

Tips And Considerations

  • Channel Profile Option: Minimum Number of Days of Receipt Data from Initial Load
  • Please refer to the implementation guide for more details about this Channel Profile Option before running Load Transactions.

Key Resources

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:
    • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Load Transactions (CJM_LOAD_TRANSACTIONS)

Calculate Accruals for Supplier Rebate Programs

You can create accruals for supplier rebate programs using the scheduled process, Create Accruals for Channel Batch. This process checks to see if an accrual can be recorded for each receiving transaction in a channel batch.

Based on the channel setting, Event for Triggering Supplier Rebate Accrual, you can either choose to record accruals upon receipt of supplier invoice for received goods; or record accruals immediately upon receipt of goods. If you choose to record accruals on supplier invoicing, then the application checks to see if goods received have been invoiced through Payables. Channel Revenue Management uses this setting to trigger accrual events to Subledger Accounting.

Potential accruals that are eligible, but not yet earned are also tracked. If eligible for a rebate and earned, then an earned accrual is tracked and interfaced to Subledger Accounting. Potential and earned accruals can be viewed from within the program checkbook or the supplier checkbook.

Create Accruals for Channel Batch Scheduled Process

Watch a Demo

  • Faster realization from supplier rebates via automation
  • Visibility to potential accruals based on received goods before supplier invoicing.

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Additional Steps:

  • Manage Channel Settings 
    • Supplier Rebate > Event for Triggering Supplier Rebate Accrual at the business unit level

Tips And Considerations

  • Manage Channel Setting
    • Category: Supplier Rebate
    • Setting: Event for Triggering Supplier Rebate Accrual
    • Based on this setting, you can choose to record accruals upon the receipt of supplier invoice for received goods, or record accruals immediately upon the receipt of goods.
  • Understand how your implementation wishes to trigger earned accruals for supplier rebates in each business unit. Generally, most organizations trigger earned accruals upon the receipt of supplier invoice for received goods; because it validates that the received goods were not delivered in error, and there can be no doubt which received goods are being accrued and claimed with an invoice number. 
  • There are no potential accruals if the setting is to record accruals upon receiving goods because the accruals will be immediately earned and not require waiting for the invoice from the supplier.

Event for Triggering Supplier Rebate Accruals

Key Resources

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:
    • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Create Accruals for Channel Batch (CJM_CREATE_ACCRUALS_FOR_CHANNEL_BATCH)

Create Manual Accrual Adjustments for Supplier Rebate Programs

Create manual accrual adjustments to correct missed accruals or reverse invalid accruals for rebate programs from suppliers. You can create accrual adjustments through the Manage Supplier Rebate Adjustments user interface. You can view and search manual adjustments, and export adjustments to a spreadsheet.

Supplier Rebate Adjustments

Watch a Demo

Reduce margin leakage via centralized and tracked accruals.

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Additional Steps:

  • Manage Adjustment Types and Adjustment Reasons

Key Resources

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:
    • Supplier Channel Manager (ORA_CJM_SUPPLIER_CHANNEL_MANAGER)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Manage Supplier Manual Adjustments (CJM_MANAGE_SUPPLIER_MANUAL_ADJUSTMENT)

Manage Claims for Supplier Rebate Programs

Generate claims for supplier rebate programs based on the available accruals to collect payment from suppliers. You can optionally review claims before submitting for supplier payment. After a claim has been invoiced and fully paid in Payables, the Close Settled Claims process updates the settlement documents with the debit memo details or the invoice details, and closes the claim.

You can remove accruals from claims and optionally reverse the accruals as well.

Supplier Rebate Claim

Claim Status Transitions

Watch a Demo

  • Fast, accurate accounting for supplier rebates via automation
    • Reduced time to implement
    • Reduced cost of ownership
    • Empower finance with visibility of accruals and accounting integration

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Additional Steps:

  • Manage User Statuses (for Claim)
  • Manage Claim Types
  • Manage Claim Reasons
  • Manage Claim Sources (for Supplier Rebates)
    • Assign default claim type and default claim reason
    • Configure default settlement method
  • Manage Channel Settings 
    • Claim Owner at business unit level (optional)
  • Manage Supplier Trade Profiles
    • Claim Owner

Key Resources

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:
    • Supplier Channel Manager (ORA_CJM_SUPPLIER_CHANNEL_MANAGER)
    • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Manage Supplier Claims (CJM_MANAGE_SUPPLIER_CLAIMS)
    • Generate Supplier Claims (CJM_GENERATE_SUPPLIER_CLAIMS)
    • Close Settled Claims (CJM_CLOSE_SETTLED_CLAIMS)
    • Manage Supplier Manual Adjustments (CJM_MANAGE_SUPPLIER_MANUAL_ADJUSTMENT)

Account for Supplier Rebate Programs Accruals and Claims

Automate accounting for accruals, adjustments, and claims using Subledger Accounting. You can configure Subledger Accounting rules to use the values of the sources assigned to the accounting attributes and the accounting rules to create the subledger journal entries for accruals, adjustments, and claims. These entries are then posted to the general ledger.

Supplier Rebate Journal Entries

Processes That Trigger Accounting Events

Watch a Demo

  • Fast, accurate accounting for supplier rebates via automation 
    • Reduced time to implement
    • Reduced cost of ownership
    • Empower finance with visibility of accruals and accounting integration

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Additional Steps:

  • Manage SLA Setups for Channel events

Key Resources

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:
    • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Sweep Channel Transaction Accounting Events (CJM_SWEEP_CHANNEL_TRANSACTION_ACCOUNTING_EVENTS_PRIV)

Include Supplier Rebate Programs in the Supplier Checkbook

You now have visibility across both supplier rebate and supplier ship and debit programs in the supplier checkbook. You can view the financial status and performance of your suppliers, supplier sites, and programs; including potential rebates, rebates earned, paid, and the balances available for supplier payment.

Supplier Checkbook

Watch a Demo

  • Empower finance with actionable visibility to what can be collected from suppliers this month, what suppliers owe.
  • Empower purchasing to negotiate with a clear understanding of margins inclusive of supplier rebates.

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. Assumes you have already implemented Oracle Procurement Cloud, Oracle Inventory Management Cloud, and Oracle Payables Cloud.
  2. You must opt in to the functional area named: Channel Revenue Management. Then opt in to the feature named: Supplier Channel Management. Opting into this feature area enables all of the Supplier Rebate features described here.
  3. If you previously opted into the
    • Channel Revenue Management functional area and the Supplier Channel Management feature, then this feature is automatically available to you.

Key Resources

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:
    • Supplier Channel Manager (ORA_CJM_SUPPLIER_CHANNEL_MANAGER)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • View Supplier Checkbook (CJM_VIEW_SUPPLIER_CHECKBOOK)

Global Order Promising

Schedule Sales Orders for Back-to-Back Items Using Transactional Supply

High-volume retail and wholesale distribution businesses may schedule back-to-back transfers and back-to-back purchase 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, global order promising can now access supply information directly from Oracle Cloud Supply Chain Execution in real time. Global order promising schedules back-to-back transfer and purchase orders using up-to-the-second inventory balances.

Note that all other types of availability checking and scheduling other than back-to-back transfers or purchases continue to rely on collected data.

Watch a Demo

Use the most current inventory information available to promise back-to-back orders for items stocked at hundreds of stores, depots, and suppliers.

Steps to Enable

  1. Set the MSP_ENABLE_GOP_WITH_NEW_ARCH profile option to this new value: Yes, with source-based promising.

  2. In the Product Information Management work area, using the Create Items or Manage Items task, for items to be promised with this feature, set the following in the Items Specification tab: 

  • Set the Check ATP item attribute to the Source Based Promising option
  • Set the Back-to-Back Enabled item attribute to Yes

Tips And Considerations

  • This feature is available for back-to-back items only.
  • REST web services for this feature are available primarily for Check Availability inquiry calls.

Key Resources

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 to this predefined job role 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 this privilege are able to access this feature:
    • Schedule Fulfillment Line (MSP_SCHEDULE_ORCHESTRATION_ORDER_FULFILLMENT_LINE_PRIV)

Extract Available Sources for an Item Organization Using a REST Service

Oracle Cloud Supply Chain Planning applications may need to coexist with other enterprise applications that you have. You can use technologies, such as file-based data import (FBDI) or REST API, to enable integrations with other applications. With this update, you can extract available upstream sources, and their attributes, associated with a sourcing rule assignment using the resource Supply Sources.

While querying this REST resource with the finder called findSources, you need to provide values for three parameters:

  • Assignment Set Name
  • Item Name
  • Organization Code

The REST service will then provide the most specific set of sourcing rules for the combination of these parameters.

You can use this Item Sources REST service to simplify integrations and support standards-based interoperability with your other applications and external systems.

Steps to Enable

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

  • The Supply Chain Planning section of the REST API for Oracle Supply Chain Management Cloud guide on the Oracle Help Center.

Role Information

Users who are assigned any of these predefined job roles are automatically able to access this feature:

  • Planning Administration (ORA_MSP_PLANNING_ADMINISTRATION_DUTY)
  • Supply Chain Planning Application Administrator (ORA_MSC_SUPPLY_CHAIN_PLANNING_APPLICATION_ADMINISTRATOR_JOB)
  • Sales and Operations Planner (ORA_MSC_SALES_AND_OPERATIONS_PLANNER_JOB)
  • Supply Chain Planner (ORA_MSC_SUPPLY_CHAIN_PLANNER_JOB)
  • Materials Planner (ORA_MSC_MATERIALS_PLANNER_JOB)
  • Order Promising Manager (ORA_MSC_ORDER_PROMISING_MANAGER_JOB)

Users who are assigned configured job roles that contain this privilege are able to access this feature:

  • View Planning Sourcing Rule (MSP_VIEW_PLANNING_SOURCING_RULE_PRIV)