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
30 AUG 2023	Procurement Contracts	Collaborate on Contract Negotiations Using Oracle Content Management	Removed feature from update 23B.
26 JUN 2023	Purchasing	Enhancements to Transaction Console Diagnostic Log	Updated document. Revised tips and considerations.
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.
26 MAY 2023	Procurement Contracts	Collaborate on Contract Negotiations Using Oracle Content Management	Updated document. Added tips and considerations.
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.
29 MAR 2023	Sourcing	Display Supplier Item, Manufacturer, and Manufacturer Part Number in Negotiations	Updated document. Revised links to documentation.
15 MAR 2023	Procurement Contracts	Collaborate on Contract Negotiations Using Oracle Content Management	Updated document. Revised feature information.
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.

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

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

• Using Supply Chain Orchestration
• Supply Chain Orchestration
• availableSupplySources in REST API for Oracle Supply Chain Management Cloud

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 Management  No 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

• Using Supply Chain Orchestration
• Supply Chain Orchestration
• REST API for Oracle Supply Chain Management Cloud

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.

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

• Watch Use Service Mappings to Extend Supply Chain Orchestration's Integration with Inventory Readiness Training

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.

2. Select the Delivery Methods tab, and enter the username and password for the delivery method that you’re using.

TIE Kinetix Delivery Methods

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

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

2. Select a supplier and then select Edit Supplier B2B Configuration.

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

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

5. Select Manage Customer Account Collaboration Configuration on the Tasks panel tab, and search for your customers.

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

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

2. Search for the trading partner or user-defined service provider associated with the delivery method.

3. Select a trading partner or user-defined service provider, and then select Actions > Edit.

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

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

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.

2. Select the Business Process Setup tab on the Manage Collaboration Messaging Configuration page.

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

4. In the Configure Collaboration Documents section, select the outbound document.

Business Process and Outbound Document Selection

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

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

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

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

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.

Procurement Common

Common Procurement

Integrate and Extend Procurement Using REST Services

In this update, Oracle Fusion Cloud Procurement and Oracle Fusion Cloud Self Service Procurement deliver new and modified REST APIs to enable and simplify integration with external systems.

The new REST APIs introduced in this update are:

• Procurement Persons LOV
• Procurement Approved Supplier List Entries
• Approved Supplier List Source Documents

NOTE: The Procurement Approved Supplier List Entries and Approved Supplier List Source Documents resources were also made available in the November monthly update of 22C, the November monthly update of 22D, and the January monthly update of 23A.

These REST APIs are enhanced:

• Requisition Preferences
  • You can now provide a requester that's different from the preparer in requisition preferences during creation (POST) and update (PATCH) of requisitions. In update 23A, the requester and preparer had to be to be the same.

• Requisition Processing Requests
  • GET, POST, and PATCH are supported for the Source Contract Purchase Agreement attribute.

• Draft Purchase Orders
  • GET, POST, and PATCH are supported for the Override B2B Communication attribute.
  • Use the Request Funds Override Flag to request funds override when submitting purchase orders that are subject to budgetary controls for approval.

• Purchase Orders
  • GET is supported for these attributes: Supplier Communication Method, To Email, Cc Email, Bcc Email, Supplier Fax, and Override B2B Communication.
  • Use the Communicate custom action to recommunicate any purchase order revision by specifying the revision number in the Change Order Number attribute.

• Supplier Negotiation Responses
  • Use the Validate and Submit Negotiation Response custom action to validate and submit a draft supplier response.

You can use these new and modified REST services 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 to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• Refer to the REST API for Oracle Fusion Cloud Procurement documentation available on the Oracle Help Center.

Access Requirements

• Refer to the Job Roles and Privileges section in the REST API for Oracle Fusion Cloud Procurement documentation, available on the Oracle Help Center.

Common Technologies and User Experience

Approvals and Notifications

Remove Prefix from Subject Lines and Titles in Workflow Notifications

By default, email and in-app notifications sent out as part of a workflow or approval process have a prefix in the subject line or title, for example Action Required. If you have a specific requirement, you can choose to exclude that prefix in the notifications that are sent.

For a particular workflow task, you can set this up for specific combinations of task statuses and recipients. For example, you can exclude the prefix when the task status is Assigned and notifications are sent to the assignees. Your setup won't apply to FYI notifications, which will always show the prefix.

To remove the prefix from the notification subject line or title:

1. In the Setup and Maintenance work area, go to the Manage Task Configurations task in the Application Extensions functional area. Or, depending on your offering, you might use a different functional area or another approval setup task.

2. In BPM Worklist, on the Task Configuration tab, search for the workflow task in the Tasks to be configured pane.

3. Select the task from the search results and click the Edit task icon in the toolbar.

4. Click the Notifications subtab.

5. For any of the task status and recipient combinations, select the Exclude Notification Prefix check box.

Removing the prefix can help grab the readers' attention with a more direct notification subject line or title, say for notifications advertising special offers. For example, Action Required: Early Payment Offer - Accelerate Payments for up to USD 1000 becomes Early Payment Offer - Accelerate Payments for up to USD 1000 after the prefix is removed.

Steps to Enable

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

Tips And Considerations

You should use this feature only if you have a very specific requirement to do so. Otherwise, leave the prefix displayed in the notifications.

Key Resources

• Remove Prefix from Subject Lines and Titles in Workflow Notifications (available April 7, 2023)

Access Requirements

• To manage task configurations and exclude the prefix, you need a custom role that includes the BPM Workflow System Admin Role (BPMWorkflowAdmin).

Procurement

Purchasing

Search Requisitions by Line Descriptive Flexfields as a Buyer

Search for requisition lines using requisition line descriptive flexfields. As a buyer, you can now filter requisitions to be processed into purchase orders using descriptive flexfields.

To search for requisition lines using global and context-sensitive descriptive flexfields, use the Advanced Search option on the Process Requisitions page.

Search Requisition Lines Using Line Global Descriptive Flexfields

To add the context-sensitive segments to the search panel, use the Add Fields option after selecting a value for the context segment.

Search Requisition Lines Using Line Context-Sensitive Descriptive Flexfields

The newly added Additional Details column on the Search Results table displays the matched values of global and context-sensitive descriptive flexfields from the requisition line.

Use Additional Details Column to View the Matched Values of Global and Context-Sensitive Descriptive Flexfields

Steps to Enable

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

Tips And Considerations

• The Additional Information column on the Process Requisitions Search Results table has been renamed to Additional Line Information. This column will continue to display the global descriptive flexfields from the requisition line.

• The newly added Additional Requisition Information column on the Process Requisitions Search Results table displays global descriptive flexfields from the requisition header.

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:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned configured job roles that contain this privilege can access this feature:
  • Process Requisition Line (POR_PROCESS_REQUISITION_LINE_PRIV)

Use Order Date to Determine the Price on Purchase Orders

Use order date to determine the price on purchase orders instead of requested delivery or shipment dates. Before this update, the application always used the requested delivery or ship dates to derive the price on purchase order lines sourced from a blanket purchase agreement. As a result, existing purchase order lines would be repriced if a line's requested delivery or shipment dates were modified. When you use this feature, existing purchase order lines aren't repriced when the line's requested delivery or shipment dates are modified. Further, when requisition lines are sourced from a blanket purchase agreement, the price on requisition lines will be derived using the application date instead of the requested delivery date.

To use this feature, you must configure non-cumulative price breaks such that the order date lies between the start and end date of a price break.

In this example, the order date on a purchase order sourced from a blanket purchase agreement is 1/12/23. The blanket purchase agreement associated with the purchase order has noncumulative price breaks configured such that the order date lies between the start and end date of the first price break. The item price on 1/12/23 is 90 USD.

Noncumulative Price Breaks Configured on Blanket Purchase Agreements Such That the Order Date Lies Between the Start and End Date of a Price Break

When a change order is created to update the requested delivery date to 2/4/23, the price on the purchase order remains as unchanged.

Price of 90 USD is Derived on the PO Line Because the Order Date of 1/12/23 Lies between the Start and End Date of the First Price Break

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: Procurement

After you've enabled this feature, create a new blanket purchase agreement or edit an existing one and select the Use order date for order pricing control.

Blanket Purchase Agreement Configured with Use Order Date for Order Pricing

Tips And Considerations

• You can use the Edit Agreement UI or the File-Based Data Import process to specify a value for the new Use order date for the order pricing attribute.

• To use this feature, you must configure non-cumulative price breaks on blanket purchase agreements by specifying a start and end date. The purchase order date must lie between the start and end date of a price break for the application to determine the price correctly.
  • The Order Date can be viewed from the Manage Orders page and is derived as the earliest of these dates:
    • First Communication Date of the initial document
    • First Request for Acknowledgment Date of the initial document
    • Implementation Date of the initial document

  • If no date was found with the above conditions, Order Date is set to the application date.

• When you use this feature:
  • The price on purchase order lines created using the Draft Purchase Orders REST API, web services, file-based data import, or online will be derived using the order date.
    • The price on new purchase order lines added in a change order will be derived using the application date.
  • The Retroactive Price Update scheduled process will use the order date to identify price changes on eligible purchase order lines.

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:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned a configured job role that contains any of these privileges can access this feature:
  • Create Purchase Agreement (PO_CREATE_PURCHASE_AGREEMENT_PRIV)
  • Change Purchase Agreement (PO_CHANGE_PURCHASE_AGREEMENT_PRIV)
  • Create Purchase Order (PO_CREATE_PURCHASE_ORDER_PRIV)
  • Change Purchase Order (PO_CHANGE_PURCHASE_ORDER_PRIV)

To set up this feature, you'll need these predefined job roles, or a configured job role that contains this privilege: 

• Predefined job roles and codes:
  • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Privilege name and code for configured job roles:
  • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)

Derive the Charge Account on Purchase Orders and Requisitions Based on the Line Amount

Use the Transaction Account Builder to derive the charge account on purchase orders and requisitions based on the line amount. With the line amount as a new source, you can now configure account derivation rules to generate an asset account if the line amount goes above a certain threshold. This new source is expressed in the functional currency of the requisitioning business unit. 

Suppose that you want to account a purchase to either an expense account or an asset account based on the line amount. You can do so by setting account rule conditions to check if the line amount is less than or greater than $100.

These screenshots illustrate the new source and an example:

Source Line Amount

Account a Purchase as an Asset if the Line Amount Is Greater Than or Equal to $100

Account a Purchase as an Expense if the Line Amount Is Less Than $100

Steps to Enable

To use this feature, you need to configure your transaction account definition to add another priority to the account rule assigned to the PO Charge Account.

Key Resources

• To know more about Transaction Account builder, refer to the Define Transaction Accounting for Procurement topic.

Access Requirements

You have a couple of options for giving people access to set up and use 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:
  • Buyer (ORA_PO_BUYER_JOB)

To set up this feature, you'll need these predefined job roles:

• Predefined job role names and codes:
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
  • Accounting Hub Administration (ORA_XLA_ACCOUNTING_HUB_ADMINISTRATION_DUTY)

Route Purchase Orders for Approval Based on Referenced Documents

Use source document references, such as blanket and contract purchase agreements, master contracts, and negotiation references, to route purchasing documents for approval.

• The Sourced to Blanket Agreement approval attribute indicates whether a blanket purchase agreement reference exists on the purchase order line.

• The Sourced to Contract Agreement approval attribute indicates whether a contract purchase agreement reference exists on the purchase order line.

• The Master Contract Exists approval attribute Indicates whether a master contract exists on the document.

• The Negotiation Exists approval attribute indicates whether a negotiation reference exists on the purchasing document line.

You can create approval rules with Sourced to Blanket Agreement, Sourced to Contract Agreement, Master Contract Exists and Negotiation Exists approval attributes to route purchasing documents for approval.

Approval Rule with Document Reference Attributes

For example, you can submit a Purchase Order for approval based on the existence of a Blanket Purchase or Contract Purchase Agreement reference.

Similarly, you can submit a Blanket Purchase Agreement for approval based on the existence of Master Contract Agreement or Negotiation references.

Steps to Enable

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

Tips And Considerations

For blanket purchase agreement change orders, if you have defined an approval rule based on a line-level attribute such as Negotiation Exists but you only update the blanket purchase agreement header, then this approval rule won't apply since only modified lines are evaluated for approval by default. To remedy this:

• In the Setup and Maintenance work area, use the Manage Administrator Profile Values task to set the profile option "All Blanket Agreement Lines Evaluated for Change Order Approval" (ORA_BPA_CHANGE_APPROVAL_INCLUDE_ALL_LINES) to Y. This will ensure that all active blanket lines are evaluated for approval rules and routed accordingly. By default, this profile option is set to N.

Access Requirements

You have a couple of options for giving people access to set up and use 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:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned a configured job role that contain these privileges can access this feature:
  • Create Purchase Order (PO_CREATE_PURCHASE_ORDER_PRIV)
  • Change Purchase Order (PO_CHANGE_PURCHASE_ORDER_PRIV)

To set up this feature, you'll need this predefined job role, or a configured job role that contains this privilege:

• Predefined job role name and code:
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Privilege name and code for configured job roles:
  • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)

Override B2B Communication of Purchase Orders

Override B2B communication of those purchase orders where supplier sites are configured for B2B messaging. You can communicate your purchase orders to your suppliers using an alternate communication method, such as email or fax. Enable Override B2B communication on the purchase order to prevent B2B communication and communicate using the Communication Method setting instead.

This screenshot shows the Override B2B communication check box on the purchase order.

Override B2B Communication Check Box

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: Procurement

After you opt in to the feature, you will see the Override B2B communication check box for purchase orders where the supplier site is configured for B2B communication. Only buyers with the Override Purchase Order B2B Communication privilege can change the value.

Tips And Considerations

• Purchase orders with Override B2B communication enabled won't be communicated using B2B. If there is a Communication Method set on the purchase order, the order will be communicated using that method. If the Communication Method is None, the order won't be communicated.

• Purchase orders with Override B2B communication disabled will be communicated using the B2B message set up on the supplier site. 

• The Override B2B communication check box is only visible if there is a B2B message set up for the document type (purchase order, change order, cancellation order).

• The default value for Override B2B communication is disabled.

• Only buyers with the Override Purchase Order B2B Communication privilege can change the Override B2B communication value.

• You can set Override B2B communication using the application, file-based data import, or the Draft Purchase Orders REST resource.  

Access Requirements

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

• Users who are assigned a configured job role that contains this privilege can access this feature:
  • Override Purchase Order B2B Communication (PO_OVERRIDE_B2B_COMMUNICATION)

To set up this feature, you'll need this predefined job role:

• Predefined job role name and code:
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB) 

Accept Supplier Part Number Corrections from Purchase Order Acknowledgment Inbound Messages

You can now have the application configured to automatically flow down supplier part number corrections into purchase order lines from purchase order acknowledgment messages from suppliers. Such changes are possible even if the purchase order line is sourced from a blanket purchase agreement.

Before this update, supplier-initiated changes to correct the supplier item number for purchase orders on pending supplier acknowledgment status were only available through Oracle Supplier Portal. With this update, suppliers can also correct supplier item numbers through the Oracle Purchase Order Acknowledgment Inbound message on Oracle Fusion Cloud Collaboration Messaging Framework.

These screen captures illustrate the feature:

Purchase Order Sourced from a Blanket Purchase Agreement on Pending Supplier Acknowledgment Status

Processing of Purchase Order Acknowledgment Inbound Message with Supplier Item Correction

Generated Change Order with Supplier Item Correction and Change Reason

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: Procurement

To use this feature, you must opt in to the Correct the Supplier Item Number on Purchase Orders feature. If you previously opted in to the Correct the Supplier Item Number on Purchase Orders feature, then this feature is automatically enabled.

Key Resources

• For more information on changes made to the Oracle Purchase Order Acknowledgment Inbound message to support supplier part number corrections, refer to the Update Rules for Processing Complex Change Requests in Inbound Order Acknowledgments feature, available in the Oracle Fusion Cloud Procurement What's New, update 23B.

Access Requirements

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

• Users who are assigned these predefined job roles can access this feature:
  • Buyer (ORA_PO_BUYER_JOB)
  • Supplier Customer Service Representative (ORA_POS_SUPPLIER_CUSTOMER_SERVICE_REPRESENTATIVE_JOB)
  • Supplier Sales Representative (ORA_POS_SUPPLIER_SALES_REPRESENTATIVE_JOB)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Create Purchase Order (PO_CREATE_PURCHASE_ORDER_PRIV)
  • Change Purchase Order (PO_CHANGE_PURCHASE_ORDER_PRIV)
  • Acknowledge Purchase Order (PO_ACKNOWLEDGE_PURCHASE_ORDER_PRIV)

To set up this feature, you'll need these predefined job roles or a configured job role that contains this privilege:

• Predefined job role names and codes:
  • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Privilege name and code for configured job roles:
  • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)

Generate Reports on Purchase Orders with U.S. Federal Attributes Using OTBI

Include U.S. Federal attributes to generate reports on purchase orders using the Purchasing Real Time and Pending Change Orders Real Time subject areas. These attributes are available under these folders:

Procurement - Purchasing Real Time Subject Area:

• Purchase Order Header Detail: Enable for DATA Act reporting, DATA Act Award Type, Procurement Instrument Identifier, Parent Award ID, Federal Assistance Identification Number, Unique Record Identifier.

• Purchase Order Schedules > Purchase Order Schedule Detail: Trading Partner TAS, Trading Partner BETC.

• Purchase Order Distributions > Purchase Order Distribution Detail: BETC.

Procurement - Pending Change Orders Real Time Subject Area:

• Purchase Order Pending Change Order Header Detail: Enable for DATA Act reporting, DATA Act Award Type, Procurement Instrument Identifier, Parent Award ID, Federal Assistance Identification Number, Unique Record Identifier.

• Pending Change Schedules > Purchase Order Pending Change Order Schedule Detail: Trading Partner TAS, Trading Partner BETC.

• Pending Change Distributions > Purchase Order Pending Change Order Distribution Detail: BETC.

These screen captures illustrate the feature:

OTBI Report Using U.S. Federal Attributes from the Purchase Order Header Detail Folder

OTBI Report Using U.S. Federal Attributes from the Purchase Order Schedule Detail Folder

OTBI Report Using U.S. Federal Attributes from the Purchase Order Distribution Detail Folder

Steps to Enable

• To use this feature, you must enable U.S. Federal Financials. 

• The DATA Act reporting attributes are enabled for entry only if the Allow Manual Entry of Award Financial Information for DATA Act (ORA_FV_ALLOW_DATA_ACT_MANUAL_AWARD_ENTRY) profile option is enabled.

Key Resources

• You can add attributes to existing reports or use them in new reports. To learn more about how to create and edit reports, see the Creating and Administering Analytics and Reports guide.

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:
  • Buyer (ORA_PO_BUYER_JOB)
  • Purchase Analysis (ORA_PO_PURCHASE_ANALYSIS_ABSTRACT)
  • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • Procurement Contract Administrator (ORA_PO_PROCUREMENT_CONTRACT_ADMIN_JOB)

• Users who are assigned a configured job role that contains this duty role can access this feature:
  • Purchase Order Transaction Analysis Duty (FBI_PURCHASE_ORDER_TRANSACTION_ANALYSIS_DUTY)

Selected Purchasing Bug Fixes in This Update

This update includes some bug fixes that can change the way Oracle Purchasing 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.

Update Base Model Price as a Supplier User

Before this update, as a supplier, you couldn't update the base model price for a configured item using the Purchase Order web service. Supplier users could only make this change online through Oracle Supplier Portal. After this update, suppliers can use the Purchase Order web service and the user interface to update the base model price.

Oracle reference: 33493407

Validate Approval Action When Importing Purchase Orders and Purchase Agreements

Before this update, you could import purchase orders and agreements without selecting a value for the approval action parameter, although approval action is a required field. Purchasing documents imported with an empty approval action were automatically submitted for approval after import. From this update, the approval action parameter displays a default value: Submit for approval.

Oracle reference: 34626133

Prevent Creation of Multiple Purchase Orders for Sales Order Kits and Shipment Sets

Before this update, as a buyer, you could manually create multiple purchase orders from sales order lines that were part of a kit or shipment set. After you update to 23B, all sales order lines that are part of a kit or a shipment set must be placed onto a single purchase order.

Oracle reference: 33714858

Validate Required Descriptive Flexfields upon PO Submission

Before this update, as a buyer, you could submit a PO for approval even if no values were entered for required descriptive flexfields. From this update, you can set the ORA_PO_VALIDATE_REQUIRED_FLEXFIELDS profile option to Y so that the application validates that all required descriptive flexfields have been populated for orders submitted in the application. Enabling this profile option may result in slower performance when submitting orders with more than 200 lines.

Oracle reference: 34654876

Prevent Automatic Updates to Deliver-to Location When Requester Changes after Partial Receipt or Invoice

The deliver-to location is no longer rederived when the requester is manually updated on distribution for a schedule that has been partially received or invoiced.

Oracle reference: 34680190

Steps to Enable

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

External Purchase Prices

Select Multiple External Purchase Prices for an Item

Choose to manually select external purchase price lines for creating blanket purchase agreements.

You can now manually select multiple external purchase prices for an item and unit of measure combination in a requisitioning business unit. All the lines selected by you will be available in the blanket purchase agreements.

On the external purchase price page, select one or more external purchase price lines. In the More Actions drop-down, click Select for Purchasing. The status of the manually selected lines is shown as User Selected. You can also manually select lines using the visual builder add-in enabled excel template. Download the template from this page, manually select the lines for purchasing across different external purchase prices, and then upload the template. The selection criteria specified in the Manage External Purchase Prices Selection Criteria setup will not be applied to the items with manually selected lines. When more than one external purchase price line is selected for the same item and unit of measure combination, all the selected lines will be available in the blanket purchase agreements.

External Purchase Prices Lines

You can now have more than one blanket purchase agreement from different suppliers for the same item.

Steps to Enable

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

Access Requirements

• Users who are assigned the Purchase Pricing Manager (ORA_SCH_PURCHASE_PRICING_MANAGER_JOB) job role are automatically able to access this feature.

Approvals and Notifications

Enhancements to Transaction Console Diagnostic Log

The Transaction Console diagnostic log now includes two new sections you can enable and make use of.

• Task Level Configuration
• Transaction History

You can view these sections when you download the diagnostic log from any pending or error transaction details page in the Transaction Console.

Task Level Configuration

This section lists details of task configuration in BPM Worklist for the process type of the selected transaction. The details shown in this section are for the current configuration of the task, not from the time the transaction was initiated.

Transaction History

This section lists all the approval stages a transaction has passed through based on the approval rule configuration.

When diagnosing an issue, users can quickly get a snapshot of the task configuration and approval history in one place.

Steps to Enable

To create the profile option that controls whether these sections are in the log:

1. In the Setup and Maintenance work area, go to the Manage Applications Core Profile Options task in the Application Extensions functional area for your offering.

2. On the Manage Applications Core Profile Options page, click the New icon.

3. On the Create Profile Option page, enter HRC_TXN_TAC_DISABLE_EXTN_LOG as the profile option code.

4. Enter a display name that you can easily remember to help you find the profile option later, for example Disable Diagnostic Log.

5. From the Application list, select Common Work Setup.

6. From the Module list, select Application Common.

7. Click Save and Close.

8. On the Manage Profile Options page, select the Enabled and Updatable check boxes for the Site level.

9. Click Save.

To set the profile option value so the sections are included:

1. In the Setup and Maintenance work area, go to the Manage Applications Core Administrator Profile Values task in the Application Extensions functional area for your offering.

2. Search for the profile option code HRC_TXN_TAC_DISABLE_EXTN_LOG.

3. In the Profile Values section, set the Site to False.

Tips And Considerations

By default, the Task Level Configuration and Transaction History sections are included in the log. You can disable them, for example to improve performance, using the HRC_TXN_TAC_DISABLE_EXTN_LOG and HRC_TXN_TAC_DISABLE_RULE_AUDIT_TRAIL profile options.

• If the HRC_TXN_TAC_DISABLE_EXTN_LOG profile option is created and is set to true, the Task Level Configuration and Transaction History sections isn’t included in the diagnostic log.

• If the HRC_TXN_TAC_DISABLE_RULE_AUDIT_TRAIL profile option, which disables the audit trail segment along with rule details, is created and is set to true, the Task Level Configuration section isn’t included in the diagnostic log. If the profile option isn’t created or created and set to false then the Task Level Configuration section is omitted and only the Transaction History section is included.

Key Resources

• Manage Included Sections in Logs

Supplier Model

New Business Classifications for Enhanced ESG Reporting

Reports for ESG data are becoming mission-critical and, in many jurisdictions, required by regulation. Without standard business classifications, there's additional manual work to create them, which can lead to errors and an increased risk they will be missed in reporting.

Expanding the standard supplier business classifications to include LGBTQ+ Owned and Person with Disability Owned enhances ESG reporting.

Steps to Enable

The LGBTQ+ Owned and Person with Disability Owned classifications are added to the supplier business classifications lookup and are disabled by default. To enable, follow these steps:

1. In the Setup and Maintenance work area, go to the Manage Business Classifications Lookup task.
2. Enable the lookup meanings LGBTQ+ Owned and Person with Disability Owned.

Tips And Considerations

• If you have already added the LGBTQ+ Owned or Person with Disability Owned classifications to the supplier business classifications lookup, the new classifications are still added with an additional suffix in the name. You can decide whether to continue using your existing classifications or the new ones.

• You can create BI reports in the Supplier Real Time subject area using the new business classifications.

Access Requirements

You have a couple of options for giving people access to setup 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 setup this feature:
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Users who are assigned a configured job role that contains this privilege can setup this feature:
  • Manage Application Standard Lookup (FND_APP_MANAGE_STANDARD_LOOKUP_PRIV)

Sourcing

Display Supplier Item, Manufacturer, and Manufacturer Part Number in Negotiations

When negotiating items for manufacturing, distribution, or direct material procurement, you can now view the supplier item, manufacturer, and manufacturer part number associated with each item.

The manufacturer part number is a manufacturer-assigned, alphanumeric value that uniquely identifies the manufacturer's product. Different manufacturers can produce a specific inventory item, and each has a unique part number that can be associated to the item. Similarly, a supplier item (also referred to as, supplier part number) is the number or code assigned by each supplier to uniquely identify their product. The manufacturer part number and supplier item number are associated to the inventory item number used by the buying organization. The associations between the inventory item, its various supplier items, and manufacturer part numbers or both are maintained in the item master, specifically in Item Relationships of Product Master Data Management.

With this update, the supplier item, manufacturer and manufacturer part number are derived real-time from the item master relationship and displayed in the negotiation.

When suppliers are invited to a negotiation, they can view the supplier item, manufacturer, and manufacturer part number for each line item in the response spreadsheet attached in the negotiation invitation notification, if the 'Lines in separate spreadsheet' control has been enabled under 'Negotiation Document Format' in Manage Negotiation styles. Suppliers can also download the negotiation PDF document to view these details. They can respond to negotiations and identify their part number to provide an accurate quote. These fields are also available to suppliers in the response spreadsheets for efficient and accurate response preparation.

View Supplier Item, Manufacturer, and Manufacturer Part Number During Response Creation

Suppliers are able to identify the supplier item number correctly and provide an accurate quote for the line items. The extra burden of referencing the product catalog or other supplier item reference manually is eliminated.

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: Procurement

Tips And Considerations

Consider these when you're working with supplier item, manufacturer, and manufacturer part numbers:

• The supplier item and manufacturer part number must be associated with an inventory item in the item master to be derived and displayed in negotiations.

• If multiple supplier items and multiple manufacturer part numbers are mapped to an inventory item, then none of the part numbers will be displayed in negotiations.

• The supplier item, manufacturer, and manufacturer part number information is currently not displayed in the negotiation PDF document attached to the supplier invitation notification. It's recommended that suppliers download the negotiation PDF documents from supplier portal.

• Alternatively, if the supplier item, manufacturer, and manufacturer part number are required in the negotiation invitation notification, then it is recommended to use the split PDF + Lines only Response spreadsheet, which has the line item information displayed separately in the csv file.

Key Resources

Refer to Manage Item Relationships in Using Product Master Data Management on the Oracle Help Center.

Access Requirements

To use this feature, these roles are required:

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Procurement Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
  • Category Manager (ORA_PON_CATEGORY_MANAGER_JOB)
  • Sourcing Project Collaborator (ORA_PON_SOURCING_PROJECT_COLLABORATOR_ABSTRACT)
  • Supplier Bidder (ORA_PON_SUPPLIER_BIDDER_ABSTRACT)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Create Supplier Negotiation (PON_CREATE_SUPPLIER_NEGOTIATION_PRIV)
  • Edit Supplier Negotiation (PON_EDIT_SUPPLIER_NEGOTIATION_PRIV)
  • Create Response (PON_CREATE_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)
  • Edit Response (PON_EDIT_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)

Configure Online Message Notification with Oracle Analytics Publisher

A new Oracle Analytics Publisher template is now available for online messaging notification that can provide you an improved experience with supplier communication. You can now configure the content and layout of the online message notification using an Oracle Analytics Publisher template. You can also show additional fields by adding them to the template to meet your specific business requirements.

Online Message Notification Based on the Oracle Analytics Publisher Template

This feature helps ensure effective communication between suppliers and the buying organization leveraging a configurable template.

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

After you enable the feature, follow these steps to configure the template for online message notification:

1. In the Navigator, click Reports and Analytics.

2. In the Sourcing Business Intelligence Catalog, locate the Online Message Notification Report template, and then click Customize. This creates a copy of the template in your Custom folder.

3. Edit the template Online Message Notification Report.

4. Upload the template (select the appropriate locale for your instance).

Tips And Considerations

The attachments added to the message won't be displayed in the notification.

Key Resources

• Refer to the Overview of Analytics Publisher chapter in the Creating and Administering Analytics and Reports for Procurement 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 own configured job roles.

• Users who are assigned any of these predefined job roles can access this feature:
  • Category Manager (ORA_PON_CATEGORY_MANAGER_JOB)
  • BI Administrator Role (BIAdministrator)

Invite Additional Suppliers to a Large Negotiation

You can now invite additional suppliers to a large negotiation after it's published using a background process. The background process will generate the negotiation documents and response lines (.CSV) file, which will be sent to all the newly invited suppliers.

Invite Additional Suppliers

You can now invite additional suppliers to participate in the negotiation process based on your business need, after the large negotiation is published.

Steps to Enable

In the Setup and Maintenance work area, go to the Manage Negotiation Styles task.

• Offering: Procurement
• Functional area: Sourcing
• Task: Manage Negotiation Styles

On the Manage Negotiation Styles page, select and edit one of your existing negotiation styles, or create a new negotiation style. (You can't edit a predefined negotiation style.)

In the Controls section, under the Overview group, select the Large negotiation check box.

Negotiation Style Controls

Key Resources

• Review update 22D readiness training for the Oracle Sourcing Cloud feature Manage Large Negotiations for more details.

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 own configured job roles.

• Users who are assigned any of these predefined job roles can access this feature:
  • Category Manager (ORA_PON_CATEGORY_MANAGER_JOB)
  • Sourcing Project Collaborator (ORA_PON_SOURCING_PROJECT_COLLABORATOR_ABSTRACT)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Create Supplier Negotiation (PON_CREATE_SUPPLIER_NEGOTIATION_PRIV)
  • Edit Supplier Negotiation (PON_EDIT_SUPPLIER_NEGOTIATION_PRIV)
  • Manage Negotiation Supplier Invitation (PON_MANAGE_NEGOTIATION_SUPPLIER_INVITATION_PRIV)

Export a Range of Response Lines in Large Negotiations

While creating a response to a large negotiation, suppliers can now export a range of response lines by specifying From and To Line numbers. They can create their response in batches to efficiently manage high line volumes.

Select a Set of Response Lines to Export by Specifying From and To Line Numbers in Large Negotiations

When dealing with high line volumes, exporting the response lines in batches and then importing it, yields to better performance and efficiency.

Steps to Enable

In the Setup and Maintenance work area, go to the Manage Negotiation Styles task.

• Offering: Procurement
• Functional area: Sourcing
• Task: Manage Negotiation Styles

On the Manage Negotiation Styles page, select and edit one of your existing negotiation styles, or create a new negotiation style. (You can't edit a predefined negotiation style.)

In the Controls section, under the Overview group, select the Large negotiation check box.

Negotiation Style Controls

Key Resources

• Review update 22D readiness training for the Oracle Sourcing Cloud feature Manage Large Negotiations for more details.

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 own configured job roles.

• Users who are assigned any of these predefined job roles can access this feature:
  • Category Manager (ORA_PON_CATEGORY_MANAGER_JOB)
  • Supplier Bidder ABSTRACT (ORA_PON_SUPPLIER_BIDDER_ABSTRACT)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • For Supplier Bidders: Create Supplier Negotiation Response (PON_CREATE_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)
  • For Category Managers: Create Supplier Negotiation Response as Surrogate (PON_CREATE_SURROGATE_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)

Use Page Composer to Control Actions for Scoring-only Team Members

In this update, you can now use page composer to configure UI and actions for scoring-only team members. For example, you may want to restrict scoring only members from downloading line attachments or provide specific instructions on the UI screens. Use two new negotiation parameters - one to identify scoring only members, and another their price visibility access.

The two parameters supported here are:

1. IsNotScoringOnlyUser
2. IsPriceVisibilityEnabled

Using these parameters to configure UI pages and actions available to scoring-only members based on their price visibility access will help to accomplish business needs related to data security and audit compliance.

Steps to Enable

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

Tips And Considerations

To use the Page Composer parameters to configure UI pages and actions, follow these steps.

1. Create and enter a sandbox with 'Page Composer' option selected.

2. Navigate to the page where you need to make changes.

3. Select the 'Structure' tab on the top to display the 'dock area' on the page (the dock area can be re-positioned as needed)

4. Click on the action/button which needs to be updated/hidden.

5. Click on the edit icon on the dock area to display the Component properties for the selected label.

6. Click on the drop down next to 'Label' option and select 'Expression builder' option from the drop-down options to open the Expression editor.

7. In the Expression editor, enter the expression using the parameters as desired e.g. #{bindings.isPriceVisibilityEnabledFlag.inputValue==true && bindings.isNotScoringOnly.inputValue==true}

8. Click on 'OK' button to exit the Expression editor and return to the Component properties area

9. Click on 'Apply' and 'OK' button. Ensure the 'Visible' checkbox is checked.

10. Publish the sandbox.

Use Expression Editor to Enter Query with Parameters

Key Resources

• About Page Composer
• Guidelines for using Page Composer

Access Requirements

To use this feature, the following roles are required:

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Procurement Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

Subscribe to Negotiation Invitation Business Event for Outbound Integration

Many customers, including public sector in the Americas and EMEA are required to publish sourcing events on regulatory platforms and B2B sourcing marketplaces, to provide equal business opportunities. There's also a requirement to send a negotiation opportunity to suppliers who aren't registered. For all such requirements, integrations can be built that use a public business event when negotiations are published, and pass negotiation info using the Oracle REST web services.

The Negotiation Invitation public business event sends a signal that a negotiation is published, and is open for suppliers to respond. You can use it to enable outbound integration between your supplier negotiations and external systems using the Oracle Integration Cloud service.

After you enable the feature, the application can send a signal, along with a payload containing information about the negotiations. Integration specialists and administrators can subscribe to the public event using the Oracle ERP Cloud Adapter. Then, they can use the information in the payload to configure event handlers that perform business operations. These negotiation parameters are available in the payload.

• Auction Header ID
• Negotiation Number
• Negotiation Title
• Open Date
• Close Date
• Procurement BU
• ProcurementBU ID

This enables Oracle Sourcing customers build better integration to external applications such as B2B sourcing exchanges.

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: Procurement

Log in to Oracle Integration Cloud (OIC) as an integration user to create an integration. See Create Integrations chapter in Oracle Help Center.

Tips And Considerations

• Event is raised only for negotiations that aren't restricted to invited suppliers.
• Event is triggered when it opens for preview is a preview date is set, else when it opens for suppliers to respond.
• If negotiation approval is enabled, event is raised when negotiation is approved.
• For large negotiations, event is triggered once the invitations are sent after the publish ESS job is completed.
• Event is also triggered when amendment and new round negotiations are published.
• If Negotiation terms and conditions are enabled with option before viewing negotiation, event is triggered when the terms notification is sent.

Key Resources

• Using the Oracle ERP Cloud Adapter with Oracle Integration

Access Requirements

To use the Oracle ERP Cloud Adapter and to create an integration, you must assign specific roles to an integration user. See these links in Oracle Help Center for Roles and Privilege information.

• Assign Required Roles to an Integration User
• Procurement Integration Specialist (Job Role)

Spend Classification

Improve Classification Results with Phrase-Based Learning

Improve classification results by using the training data values for specific attributes as phrases rather than individual keywords. The values of certain attributes like supplier names recorded in an organization's spend data are rarely a single word as they’re typically made up of multiple words. You can now enable the classification matching algorithms to identify patterns in these attribute values using phrases during knowledge base creation, greatly improving the accuracy of the category predictions.

Create Knowledge Base

During knowledge base creation, define the attributes for which you want to incorporate phrase-based learning in the Create Knowledge Base dialog. You can select any attribute in the data set including additional classification attributes. The classification process compares these attributes as a whole string with other values from the same column. For example, if you selected the supplier name to be used for phrase-based learning, a supplier name like Vision Corporation will be considered as a single phrase and compared with all other supplier names only. An invoice with supplier name such as Vision College won't be considered a match for this particular training.

You can also include phrase-based learning in existing knowledge bases. Select the attributes and improve them with the same training sets.

Improve Knowledge Base

Improve classification results with phrase-based learning without having to make modifications to your existing training. Decide the attributes that you want to select for phrase-based learning based on your organization’s data. You can also use positive or negative influencers to help you determine which attributes to select for phrase-based learning.

Steps to Enable

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

Key Resources

• Refer to the Spend Classification chapter in Oracle Procurement Cloud documentation, available in the Oracle Help Center.

Access Requirements

• This feature is available without additional setup to users who have access to spend classification.

• You have a couple of options for giving people access to Spend Classification, 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:
    • Procurement Data Analyst (ORA_POI_PROCUREMENT_DATA_ANALYST_ABSTRACT)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Administer Spend Classification Application (POI_ADMINISTER_SPEND_CLASSIFICATION_PRIV)
    • Manage Spend Classification Batch (POI_MANAGE_SPEND_CLASSIFICATION_BATCH_PRIV)
    • View Spend Classification Work Area (POI_SPEND_CLASSIFICATION_WORKAREA_PRIV)

Manage Rules with Additionally Available Information

Identify which classification rules were used to improve category predictions through a new column in the batch details download file that displays the names of the rules that may have influenced the category prediction or modified the values of some of the attributes. With this additional information, you can work to understand how the rules have influenced the predictions and opt to revise or add new rules as necessary.

Batch Details

With this feature you can verify the efficiency of rules or tweak them in order to correctly normalize or classify your transactions. Eventually, the correct set of rules help you classify your transaction efficiently based on the logic your data requires and reduces the time otherwise spent on reviewing the classification results.

Steps to Enable

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

Key Resources

• Refer to the Spend Classification chapter in Oracle Procurement Cloud documentation, available in the Oracle Help Center.

Access Requirements

• This feature is available without additional setup to users who have access to spend classification.

• You have a couple of options for giving people access to Spend Classification, 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:
    • Procurement Data Analyst (ORA_POI_PROCUREMENT_DATA_ANALYST_ABSTRACT)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Administer Spend Classification Application (POI_ADMINISTER_SPEND_CLASSIFICATION_PRIV)
    • Manage Spend Classification Batch (POI_MANAGE_SPEND_CLASSIFICATION_BATCH_PRIV)
    • View Spend Classification Work Area (POI_SPEND_CLASSIFICATION_WORKAREA_PRIV)

Procurement Contracts

Upload Your Contract Document in the Background

You can upload your contract document from the Contract Terms page or Oracle Contracts Word add-in using an automated scheduled background process. You can continue to perform limited actions from the Contract Terms page or work on other contracts while the upload is in progress. You can override this option if you want to upload your document in real time.

Upload in Background

While the upload is in progress, the process status is displayed as a banner.

Upload Status Banner in Contract

You are notified by email when the contract document is uploaded and you can also view the notification in the application.

This is useful when uploading large documents that may take additional time.

Steps to Enable

Use the Allow background upload check box in the Edit Terms Template page

Allow Background Upload in Terms Template

Display Content Control in Downloaded Word Document

If you're using structured terms, you can choose to display content control boxes in Microsoft Word when the contract is downloaded.

When the contract is downloaded to Microsoft Word, you'll be able to see content control boxes when you click on each clause, clause title, or section title.

Content Control in Downloaded Contract

Hit the End key on your keyboard to exit the content control box and add a new section or clause. You can manually add new content using Word styles to mark new sections and clauses. Internal application users can also use the Oracle Contracts add-in.

Displaying content control boxes around existing sections and clauses make it easier to see where to add new content to the downloaded contract. This helps you quickly locate and view what changes were made to the contract when uploaded to the application.

Steps to Enable

Check the option Display content control in downloaded contract in the terms template to see content control boxes in Microsoft Word when any contract using that template is downloaded.

Edit Terms Template

Tips And Considerations

If you've chosen to display content control boxes, they'll only be displayed around existing content downloaded from the application. They won't be displayed around any new sections or clauses you've added.