Cloud Readiness / Oracle Fusion Cloud Supply Chain Collaboration
What's New
Expand All


  1. Update 23B
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
  6. Supply Chain Orchestration
    1. Supply Chain Orchestration
        1. Use REST API to Get Supply Sources for Internal Material Transfers
        2. Include Reference Details for Supply Requests on REST API Error Messages
        3. Use Service Mappings to Extend Supply Chain Orchestration's Integration with Inventory
        4. Selected Supply Chain Orchestration Bug Fixes in This Update
  7. Collaboration Messaging Framework
    1. Collaboration Messaging Framework
        1. Log In-Process Inbound B2B Messages
        2. Update Rules for Processing Complex Change Requests in Inbound Order Acknowledgments
        3. Exchange B2B Messages with Your Trading Partners Using TIE Kinetix
        4. Define the File Extension for Your B2B Messages Delivered by Email or an Oracle Content Repository
        5. Specify the Sender's Email Address for Outbound B2B Messages
        6. Retransmit Unsuccessful B2B Messaging-Enabled Purchase Orders
  8. Supply Chain Collaboration
    1. Supply Chain Collaboration
        1. Send Process Forecast B2B Messages to Suppliers on Demand
        2. Add Commit Reason Codes and User Notes to Your Reports in OTBI
        3. View Relationship Candidates for Order Forecasts with Quantity Greater Than Zero Only

Update 23B

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 Module Feature Notes
31 MAY 2023

Collaboration Messaging Framework

Specify the Sender's Email Address for Outbound B2B Messages

Updated document. Revised feature description.

31 MAY 2023

Collaboration Messaging Framework

Retransmit Unsuccessful B2B Messaging-Enabled Purchase Orders

Updated document. Added a feature that was backported in the May monthly update of 23B.

27 APR 2023

Collaboration Messaging Framework

Define the File Extension for Your B2B Messages Delivered by Email or an Oracle Content Repository

Updated document. Added a feature that was backported in the April monthly update of 23B.

27 APR 2023

Collaboration Messaging Framework

Specify the Sender's Email Address for Outbound B2B Messages

Updated document. Added a feature that was backported in the April monthly update of 23B.

03 MAR 2023     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 Fusion Cloud SCM: 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 Configure Offerings.

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:

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
(Feature Delivered Enabled)

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

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

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

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Supply Chain Orchestration

Supply Chain Orchestration

Use REST API to Get Supply Sources for Internal Material Transfers

Include Reference Details for Supply Requests on REST API Error Messages

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

Selected Supply Chain Orchestration Bug Fixes in This Update

Collaboration Messaging Framework

Collaboration Messaging Framework

Log In-Process Inbound B2B Messages

Update Rules for Processing Complex Change Requests in Inbound Order Acknowledgments

Exchange B2B Messages with Your Trading Partners Using TIE Kinetix

Define the File Extension for Your B2B Messages Delivered by Email or an Oracle Content Repository

Specify the Sender's Email Address for Outbound B2B Messages

Retransmit Unsuccessful B2B Messaging-Enabled Purchase Orders

Supply Chain Collaboration

Supply Chain Collaboration

Send Process Forecast B2B Messages to Suppliers on Demand

Add Commit Reason Codes and User Notes to Your Reports in OTBI

View Relationship Candidates for Order Forecasts with Quantity Greater Than Zero Only

Supply Chain Orchestration

Supply Chain Orchestration

Use REST API to Get Supply Sources for Internal Material Transfers

Use the availableSupplySources REST resource to get the supply sources that can fulfill a request for an internal material transfer. Get the one source that can most effectively fulfill the request, or get a list of up to six sources, ranked according to how effectively they can fulfill the request. Get the actual quantity that's currently on hand in each source.

Add flexibility to how you select and use the supply source for each of your internal material transfers.

Steps to Enable

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

Tips And Considerations

  • Use the findBestAvailableSupplySource finder to get the most effective source.
  • Use the findAllAvailableSupplySources finder to get the list of all supply sources. This finder gets a maximum of 6 sources, ranked according to how effectively each one fulfills the request.
  • Get the actual quantity that's currently on hand for each supply source.
  • You can only read data, so you can use only the GET operation.

Key Resources

Access Requirements

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 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)
    • Get Best Or All Available Supply Sources (DOS_GET_BEST_OR_ALL_AVAILABLE_SOURCES_PRIV)
    • View Total On Hand Quantity in Supply Source (DOS_VIEW_AVAILABLE_ONHAND_QTY_PRIV)

Include Reference Details for Supply Requests on REST API Error Messages

Add the value of the SupplyOrderReferenceNumber attribute and the SupplyOrderReferenceLineNumber attribute as a prefix on each error message that REST API returns when it processes a supply request. Use the prefix to troubleshoot problems with the request.

Reduce the amount of time you need to troubleshoot and fix problems when you import through REST API.

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 ManagementNo Longer Optional From: Update 23D

Tips And Considerations

Here's an example of an error message that REST API returns.

{

  "title": "Bad Request",

  "status": "400",

  "o:errorDetails": [

  {

    "detail": "SupplyOrderReferenceNumber:A190102, SupplyOrderReferenceLineNumber:100, MessageType:ERROR, MessageText:The supply order wasn't created because the destination subinventory code, source subinventory code, or both aren't correct."

    },

  {

    "detail": "SupplyOrderReferenceNumber:A190102, SupplyOrderReferenceLineNumber:100, MessageType:ERROR, MessageText:The supply order wasn't created because the shipment priority isn't correct. Ensure that a valid shipment priority is specified in the supply request."

  }

  ]

}

Key Resources

Access Requirements

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 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.

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

Use a service mapping to help integrate your Oracle applications. Use the service mapping to meet your specific integration requirements in your transfer order flow. Create a sales order in Oracle Order Management, orchestrate supply in Oracle Supply Chain Orchestration, then create a transfer order in Oracle Inventory Management. 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 purchasing, to supply chain orchestration, and then to inventory.

For example, here's a service mapping that uses the TransferOrderRequest entity in the TransferRequestSource service to send a request to create a transfer order from Supply Chain Orchestration to inventory:

Modify supply orchestration data so it meets your requirements.

Watch a Demo.

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 that you need to manage service mappings and algorithms.
  1. Go to the Supply Chain Orchestration work area, click Tasks, then click one of:
  • Manage Service Mappings
  • Manage Algorithms

Watch a Setup Demo.

Tips And Considerations

  • Make sure your integration can send the validations that Inventory Management applies. Your request payload might be fine, but Inventory Management might not accept the request. 
  • Check for empty values when you write expressions in your integration algorithm, especially when you for query more than one request line. A empty value at runtime might create errors.
  • If you encounter an error, fix it, then use the Supply Chain Orchestration work area to resubmit your request.

Key Resources

Access Requirements

  • 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

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.

Create Transfer Orders That Are Valid When You Import Through File-Based Data Import

Before update 23B, if you used the DosSupplyOrderImportTemplate.xlsm file to import a transfer request, and if the project details in your import weren't valid, then the Load Interface File for Import scheduled process finished successfully, reported the error in its error log, and the Process Supply Chain Orchestration Interface scheduled process created the transfer order without project details.  

After you update to 23B, if the project details in your import aren't valid, then the Process Supply Chain Orchestration Interface scheduled process won't create the transfer order but will instead report the error in its error log. 

Oracle reference: 34862468

Map the Project Organization ID from Supply Chain Orchestration to Procurement

Before update 23B, Oracle Supply Chain Orchestration ignored any mapping that you provided for the ProjectOrganizationId attribute to Oracle Fusion Cloud Procurement. After you update to 23B, if you map the ProjectOrganizationId attribute to Oracle Procurement, then Supply Chain Orchestration will include it when it communicates supply details to Procurement.

Oracle reference: 34902854

Steps to Enable

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

Collaboration Messaging Framework

Collaboration Messaging Framework

Log In-Process Inbound B2B Messages

Inbound B2B messages are logged after all setup validations are completed and before processing begins. You can see a list of inbound messages that are In-Process on the Collaboration Messaging History page. After processing is complete, the status updates to reflect the outcome.

When a message with multiple instances of the same document type is received, the original message status is Received. The message status of each instance is In-Process. The message ID generated for each instance is a concatenation of the original message ID and a number representing the counter of the document type.

Message with Multiple Instances of an Inbound Invoice

You can check the latest status of messages by using the new action Refresh Status. And the Refresh and Download Payloads buttons have been replaced with icons, as shown below.

New Action Refresh Status and Icons for Refresh and Download Payloads

Now you can see a log of the inbound messages being processed early in the process flow. You can check the message status and submit them for reprocessing if there are errors.

Steps to Enable

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

Tips And Considerations

When a message contains multiple instances of a B2B document, you can find all documents received in that message on the Collaboration Messaging History page. To retrieve those documents, enter the original Message ID followed by a percent sign (for example, IN_81046%) in the Message ID search criteria.

Key Resources

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

Access Requirements

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:
    • 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 Collaboration Messaging History (CMK_COLLAB_MESG_HISTORY_PRIV)

Update Rules for Processing Complex Change Requests in Inbound Order Acknowledgments

The new version of the Oracle Purchase Order Acknowledgment Inbound message (Oracle-1-0-B2B-Purchase-Order-Acknowledgment-In-V2) has updated processing rules that support the following scenarios:

  • If the Buyer Managed Transport check box is selected for a purchase order (PO) and the acknowledgment received includes a promised delivery date, the acknowledgment is now processed and no longer skipped as before. Additionally, the promised delivery date is recorded, along with a note. You need to create two descriptive flexfields at the PO line level for this purpose, B2B Provided Date and B2B Provided Date-Note. If the Buyer Managed Transport check box isn't selected for a PO and the acknowledgment received includes a promised ship date, the acknowledgment is processed, and the two descriptive flexfields are populated.
  • A unit price may now be included with an item substitution code. When the acknowledgment is processed, the price on the PO line is updated, and the substitute item is recorded in the descriptive flexfield created for this purpose (B2B Substitute Supplier Item).
  • When a part number correction is provided in the acknowledgment received, the supplier item number can be updated on the PO line if the feature Correct the Supplier Item Number on Purchase Orders is enabled. Otherwise, you need to create a descriptive flexfield for B2B Part Number Correction, which will be populated with the corrected part number.

Oracle-1-0-B2B-Purchase-Order-Acknowledgment-In-V2

Steps to Enable

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

Tips And Considerations

Enable the feature Correct the Supplier Item Number on Purchase Orders if you want to update the supplier item number on your PO line when you receive a part number correction.

Key Resources

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

Access Requirements

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:
    • 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)

Exchange B2B Messages with Your Trading Partners Using TIE Kinetix

A new predefined service provider, TIE Kinetix, is available for your procure-to-pay and electronic invoicing needs. You can use TIE Kinetix to connect with your trading partners via the Pan-European Public Procurement Online (PEPPOL) network. TIE Kinetix is a certified PEPPOL access point and solution provider.

When you use the Tie Kinetix predefined service provider, you benefit by having one messaging standard and delivery method to exchange messages with your trading partners. In addition, the messages and delivery methods are predefined, thereby streamlining the B2B setup in the Collaboration Messaging work area.

Steps to Enable

At a high level, to set up the TIE Kinetix service provider:

  1. Configure TIE Kinetix to exchange messages with your trading partners.
  2. Create trading partners.
  3. Associate trading partners with your suppliers or customers.
  4. Select the documents you want to exchange with your suppliers or customers.

These steps are detailed in the Configuring and Managing B2B Messaging for Oracle Applications Cloud guide.

Configure the Predefined Service Provider TIE Kinetix

  1. Select Manage Collaboration Messaging Service Providers from the Tasks panel tab, and search for the TIE Kinetix service provider.
  1. Select the Delivery Methods tab, and enter the username and password for the delivery method that you’re using.

TIE Kinetix Delivery Methods

  1. Select the Outbound Collaboration Messages tab, link the delivery method (test or production) with the messages, and activate those messages you plan to exchange with your trading partners. The following messages are available:
  • OAGIS purchases order outbound message (OAGIS_10.1_PROCESS_PO_OUT)
  • OAGIS change purchase order outbound message (OAGIS_10.1_CHANGE_PO_OUT)
  • Universal Business Language (UBL) PEPPOL outbound invoice message (UBL-2.1-PEPPOL-Invoice-Out)

TIE Kinetix Outbound Collaboration Messages

  1. Select the Inbound Collaboration Messages tab, and activate the messages you plan to use. The following messages are available:
  • UBL invoice application response message (UBL-2-1-InvoiceApplicationResponse-In)
  • OAGIS acknowledgment purchase order inbound message (OAGIS_10.1_ACK_PO_IN)
  • OAGIS invoice inbound message (OAGIS_10.1_PROCESS_INVOICE_IN)
  • UBL PEPPOL invoice inbound message (UBL-2.1-PEPPOL-Invoice-In)
  • OAGIS shipment inbound message (OAGIS-10.1-Process-Shipment-In-V2)

TIE Kinetix Inbound Collaboration Messages

Create Trading Partners

After completing the service provider setup, create your trading partners.

  1. Select Manage B2B Trading Partners on the Tasks panel tab.
  2. On the Manage B2B Trading Partners page, select Actions > Create, and add your trading partners.
  3. Select TIE Kinetix as the service provider.

Create a Trading Partner

Associate Trading Partners with Your Suppliers or Customers

Next, associate the trading partners with your suppliers or customers for your procure-to-pay documents.

  1. Select Manage Supplier B2B Configuration on the Tasks panel tab, and search for your suppliers.
  1. Select a supplier and then select Edit Supplier B2B Configuration.
  1. On the Edit Supplier B2B Configuration page, select the Trading Partner Assignment tab and click Actions > Add Row to add a trading partner and the TIE Kinetix service provider.

Trading Partner Assignment

  1. On the Edit Supplier B2B Configuration page, select the Document Setup tab, and add the documents that you want to exchange with the selected supplier.

Document Setup for Supplier Sites

  1. Select Manage Customer Account Collaboration Configuration on the Tasks panel tab, and search for your customers.
  1. Select a customer. On the Edit Customer Account Collaboration Configuration page, select the TIE Kinetix service and trading partners in the Associated Service Providers section.
  1. In the Collaboration Documents for Service Provider section, select the documents you want to exchange (outbound invoices or inbound invoice acknowledgments).

Customer Account Collaboration Configuration

Tips And Considerations

TIE Kinetix supports both OAGIS and UBL PEPPOL-compliant inbound invoices. However, only one message definition can be active for a given document.

Key Resources

  • Refer to the How You Configure Predefined Service Providers section of the Configuring and Managing B2B Messaging for Oracle Applications Cloud guide on the Oracle Help Center.

Access Requirements

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

  • Users who are assigned this predefined job role 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)
    • Manage Customer Account Collaboration Configuration (CMK_B2B_CUSTOMER_ACCOUNT_TRADING_PARTNERS_PRIV)
    • Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)

Define the File Extension for Your B2B Messages Delivered by Email or an Oracle Content Repository

You can specify a B2B message file extension for the email and file export delivery methods. The extension you specify is used for B2B messages delivered by email or messages retrieved from an Oracle content repository by your trading partner.

To specify a file extension:

  1. In the Collaboration Messaging work area, click Manage B2B Trading Partners or Manage Collaboration Messaging Service Providers in the Tasks panel tab.
  1. Search for the trading partner or user-defined service provider associated with the delivery method.
  1. Select a trading partner or user-defined service provider, and then select Actions > Edit.
  1. On the Edit Trading Partner page, select the Delivery Methods tab to add a new delivery method type of Email or File Export and specify the file extension. You can also add a file extension for existing delivery methods of these types.
  1. Enter up to four characters in the File Extension field. B2B messages will have the file extension you entered. If you don’t enter a file extension, the .zip default is used.

Email Delivery Method

Email Delivery Method

You can send B2B messages to trading partners by email without triggering corporate firewall rules that strip zipped email attachments.

Steps to Enable

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

Tips And Considerations

The file extension you enter doesn’t change the file compression method. The file remains a Zip compressed file, but with the file extension you entered. Your trading partner will need to change the extension back to .zip to extract B2B messages upon receipt.

Key Resources

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

Access Requirements

  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)
    • Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)
  • These privileges were available prior to this update.

Specify the Sender's Email Address for Outbound B2B Messages

You can configure an email address for the sender of your B2B documents instead of using the application-generated one. And you can monitor the inbox of the email address you configured for replies.

Your trading partners can add the sender email address to their approved list of emails to ensure continued communication.

Steps to Enable

In Setup and Maintenance, select the Manage Collaboration Messaging Configuration task.

  1. In the Setup and Maintenance work area, go to the Manage Collaboration Messaging Configuration task in the Manufacturing and Supply Chain Materials Management offering.
  1. Select the Business Process Setup tab on the Manage Collaboration Messaging Configuration page.
  1. In the Collaboration Business Process section, select the business process that includes the document you want to transmit using the new sender email address you configured.
  1. In the Configure Collaboration Documents section, select the outbound document.

Business Process and Outbound Document Selection

Business Process and Outbound Document Selection

  1. Click the Configure Additional Details button and enter the sender's email address in the dialog box. This email address is used as the sender for all outbound B2B messages associated with the selected document.

Configure Additional Details Dialog Box

Configure Additional Details Dialog Box

Tips And Considerations

For best practices on email security, refer to the Configure Email Security documentation available on the Oracle Help Center.

Key Resources

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

Access Requirements

  • Users who are assigned a configured job role that contains this privilege can access this feature:
    • Manage Collaboration Messaging Configuration (CMK_MANAGE_COLLAB_MESG_CONFIG_PRIV)
  • This privilege was available prior to this update.

Retransmit Unsuccessful B2B Messaging-Enabled Purchase Orders

You can get a list of untransmitted purchase orders and either retransmit them in bulk or download the list for further review. To generate the list, use the new Retransmit Purchase Orders dialog box on the Manage Collaboration Messaging History page. You invoke the new dialog box by clicking on a warning icon or from the Actions menu on that page.

You'll see a warning icon on the Manage Collaboration Messaging History page if there are purchase orders that B2B message transmission wasn't initiated for when you select one of these document types:

  • Purchase Order - Outbound
  • Purchase Order Change - Outbound
  • Purchase Order Cancellation - Outbound

When you click the warning icon, a warning message appears.

Retransmit Warning Icon and Message

Retransmit Warning Icon and Message

If you click Yes, the Retransmit Purchase Orders dialog box appears. Or you can select Actions > Retransmit on the Manage Collaboration Messaging History page to invoke the dialog box.

Retransmit Purchase Orders Dialog Box

Retransmit Purchase Orders Dialog Box

The From Date and Orders to Retransmit fields are required. The other fields are optional.

The Orders to Retransmit field includes these options:

Menu Option

Explanation

Orders for which B2B transmission wasn't initiated

Retransmits all untransmitted purchase orders, including prior untransmitted versions

Orders with the B2B messaging status of Terminated

Retransmits purchase orders that have a status of Terminated

All

Retransmits all untransmitted purchase orders and those with a status of Terminated

Click Search on Retransmit Purchase Orders dialog box to see the number of orders found. You can download the list of purchase orders found or initiate retransmission of the orders.

To set the minimum time an order can be in process before you can terminate processing:

  1. In the Setup and Maintenance work area, go to the Manage Collaboration Messaging Configuration task in the Manufacturing and Supply Chain Materials Management offering.

  2. Enter a value in the Minimum In-Process Duration field on the General Setup tab of the Manage Collaboration Messaging Configuration page. The value you enter determines the minimum time an order can be in process before you can terminate it. The default value is 60 minutes.

The Terminate Processing option is available on the Actions menu.

Minimum In-Process Duration

Minimum In-Process Duration

You can now review untransmitted purchase orders with the option to transmit them in bulk. This feature reduces any potential interruption of B2B message exchange with your suppliers.

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.

Access Requirements

  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Manage Collaboration Messaging Configuration (CMK_MANAGE_COLLAB_MESG_CONFIG_PRIV)
    • Manage Collaboration Messaging History (CMK_COLLAB_MESG_HISTORY_PRIV)
    • Extensible Data Model Used for Electronic Messaging Profile (PO_ELECTRONIC_COMM_DATA_MODEL)
    • These privileges were available prior to this update.

Supply Chain Collaboration

Supply Chain Collaboration

Today’s global supply chains increase manufacturers’ reliance on suppliers, contract manufacturers, and other trading partners. To be successful, companies must synchronize their activities across multiple tiers of trading parties. Oracle Fusion Cloud Supply Chain Collaboration enables companies to jointly plan supply, gain visibility into trading partner data, coordinate contract manufacturing execution, and measure performance across their trading networks. Trading partners are actively involved in the decision-making process, so they can exchange early warning signs and collaboratively resolve supply chain issues. Depending on the size and technical sophistication of each supplier, your company can interact using a portal-based user interface, standards-based B2B messages, or web services. Customers can also tailor Oracle Supply Chain Collaboration’s flexible, predefined business processes to their unique requirements. Enhanced collaboration results in more dynamic trading relationships, as well as increased reliability and efficiency of supply.

Send Process Forecast B2B Messages to Suppliers on Demand

Until this update, for suppliers enabled for B2B messaging, the Process Forecast message was sent as a full payload each time planners published a plan from Oracle Supply Planning. With this update, you have the option to schedule the Process Forecast B2B message on demand. This option enables you to receive the updates from all your planners before sharing order forecasts with your suppliers and contract manufacturers.

After you enable this feature, you must use the Publish B2B Outbound Messages for Order Forecasts scheduled process to share your order forecasts with your suppliers and contract manufacturers.

Tools > Scheduled Processes > Publish B2B Outbound Messages for Order Forecasts

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

If you want to use the Send Process Forecast B2B Messages to Suppliers on Demand feature, then you must opt in to its parent feature: Supply Collaboration. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Additionally, on the Manage Supply Chain Collaboration Settings page in the Setup and Maintenance work area, you must enable a new collaboration setting. 

  • Set the Schedule B2B publish process from the Publish B2B Outbound Messages for Order Forecasts scheduled process collaboration setting to Yes.
  • When this setting is Yes, then your order forecasts are only shared with your B2B enabled suppliers and contract manufacturers when you run the Publish B2B Outbound Messages for Order Forecasts scheduled process.

My Enterprise > Setup and Maintenance > Manage Supply Chain Collaboration Settings

Access Requirements

You have a few 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:
    • Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_COLLAB_PLANNER)
  • Users who are assigned configured job roles that contain this privilege are able to access this feature:
    • Schedule Order Forecast Decomposition (VCS_SCHEDULE_ORDER_FORECAST_DECOMP)

Add Commit Reason Codes and User Notes to Your Reports in OTBI

As an enterprise planner, you need to review supplier performance and ensure supplier accountability on a consistent basis. With this update, you can use the Commit Reason Codes attribute and the notes attributes while generating reports on order forecasts and commits in Oracle Transactional Business Intelligence (OTBI).

Using data for the current collaboration cycle, you can now create reports that use the new attributes to compare the current collaboration cycle measures with a supplier’s historical commitments. You can use these reports to see and analyze the reasons for changes in values for specific time periods.

Both the Current Order Forecast Details and the Order Forecast Details folders in the Supply Chain Collaboration – Supply Planning Real Time subject areas now contain these new attributes:

  • Commit Mismatch Reason
  • Commit Mismatch Reason Code
  • Note to Planner
  • Note to Supplier

Subject Area: Supply Chain Collaboration – Supply Planning Real Time

Steps to Enable

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

Access Requirements

You have a few 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:
    • Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_COLLAB_PLANNER)
  • Users who are assigned configured job roles that contain this duty are able to access this feature:
    • Supply Chain Collaboration Transaction Analysis Duty (FBI_SUPPLY_COLLAB_PLANNER_TRANSACTION_ANALYSIS_DUTY)

View Relationship Candidates for Order Forecasts with Quantity Greater Than Zero Only

With this update, additional constraints are considered when creating collaboration relationships to ensure collaboration relationship candidates aren’t created for zero quantity order forecasts.

Prior to this update, collaboration relationship candidates were created for all combinations of item, organization, and supplier site within the scope of a plan created in Oracle Supply Planning. The relationship candidates were created if the item and organization was a valid combination and an approved supplier list existed for the item and supplier site combination. This behavior was applicable to all supplier sites, including those enabled for B2B.

Now, additional constraints are also considered when creating collaboration relationship candidates:

  • A valid sourcing rule in Supply Planning.
  • A collaboration relationship for either a B2B or non-B2B enabled supplier site in Oracle Supply Chain Collaboration.

This update reduces the number of collaboration relationship candidates created, and along with the new Oracle Supply Planning profile option called Publish Order Forecast Using Sourcing Rules, reduces the number of zero order forecast records that are published. These reductions in numbers reduce both the time required to publish the order forecast and the time it would take Supply Collaboration to process the extra zero order forecast records.

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

If you want to use the View Relationship Candidates for Order Forecasts with Quantity Forecasts Greater Than Zero Only feature, then you must opt in to its parent feature: Supply Collaboration. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

Additionally, you must enable a new collaboration setting on the Manage Supply Chain Collaboration Setting page in the Setup and Maintenance work area.

  • Set the Exclude unpublished order forecasts with zero quantities from the decomposition process collaboration setting to Yes.
  • When this collaboration setting is Yes, then your collaboration relationship candidates and related order forecasts won't be created for zero quantity order forecasts.

My Enterprise > Setup and Maintenance > Manage Supply Chain Collaboration Settings

Tips And Considerations

In Oracle Supply Planning, a new profile option called Publish Order Forecast Using Sourcing Rules, ORA_MSC_PUB_ORDR_FCST_USNG_SRCNG, has been added to reduce the number of zero order forecast records produced by the Publish Order Forecast action from Supply Planning.

  • Previously, the Publish Order Forecast scheduled process published an order forecast for all item and organization combinations where a record existed for the item in the Approved Supplier List, regardless of whether there was any demand for the item and organization combination.
  • If the Publish Order Forecast Using Sourcing Rules profile option is enabled, then a zero order forecast record is only published if there’s an associated sourcing rule. This approach reduces the number of zero order forecast records that are published, which reduces both the time required to publish the order forecast and the time it would take Supply Collaboration to process extra zero order forecast records.

Access Requirements

You have a few 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:
    • Supply Chain Collaboration Planner (ORA_VCS_SUPPLY_COLLAB_PLANNER)
  • Users who are assigned configured job roles that contain this privilege are able to access this feature:
    • Edit Forecasts as Enterprise User (VCS_EDIT_ORDER_FORECAST_ENTERPRISE)