Expand All


  1. Update 23C
  1. Revision History
  2. Overview
  3. Optional Uptake of New Features (Opt In)
  4. Feature Summary
  5. Supply Chain Orchestration
    1. Supply Chain Orchestration
        1. Use REST API to Process Supply Request Lines that Pass Validation
        2. Use the Supply Chain Orchestration Work Area to Synchronize Supply Documents
        3. Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning
        4. Extend Supply Chain Orchestration's Integration with Inventory Management
        5. Prevent Duplicate Supply Requests for Back-to-Back Sales Orders
        6. View Manual Reservations for Your Back-to-Back Sales Orders
        7. Use High-Volume Order Processing with Supply Chain Orchestration for Configured Items
  6. Collaboration Messaging Framework
    1. Collaboration Messaging Framework
        1. Define the File Extension for Your B2B Messages Delivered by Email or an Oracle Content Repository
        2. Retransmit Unsuccessful B2B Messaging-Enabled Purchase Orders
        3. Specify the Sender's Email Address for Outbound B2B Messages
  7. Procurement Common
    1. Common Procurement
        1. Integrate and Extend Procurement Using REST Services
        2. Worklist: Notifications and Approvals Work Area Includes New Task Filter
  8. Procurement
    1. Purchasing
        1. Process Requisitions Into Purchase Orders in the Invoice Currency of the Supplier Site
        2. Generate Reports on Purchase Orders Where B2B Communication Was Overridden
        3. Selected Purchasing Bug Fixes in This Update
    2. Supplier Model
        1. Next Generation User Experience for Supplier Self-Service Registration
        2. Selected Supplier Model Bug Fixes in This Update
    3. Sourcing
        1. Add Requisitions to an Existing Negotiation
        2. Create Purchasing Documents from a Large Negotiation
        3. Capture New Supplier Items in Negotiations
        4. Allow Scoring Only Members to Message Suppliers
        5. Copy Requisition Header Attachments to The Negotiation Header
    4. Spend Classification
        1. Create Reports in OTBI with Data from Expenses and Oracle Spend Classification
    5. Procurement Contracts
        1. Display Header and Footer on Downloaded Word Document
        2. Display Header and Footer on Downloaded Word Document

Update 23C

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
12 MAR 2024 Supplier Model Next Generation User Experience for Supplier Self-Service Registration Updated document. Revised tips and considerations and key resources.
15 NOV 2023

Supply Chain Orchestration

Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning

Updated document. Revised feature description.

16 OCT 2023 Supplier Model Next Generation User Experience for Supplier Self-Service Registration

Updated document. Revised feature information.

30 AUG 2023 Purchasing Selected Purchasing Bug Fixes in This Update Updated document. Added profile option name to one of the bug fixes.
10 AUG 2023 Supplier Model Next Generation User Experience for Supplier Self-Service Registration Updated document. Revised feature description and steps to enable.
20 JUN 2023 Common Procurement Integrate and Extend Procurement Using REST Services Updated document. Revised feature description.
02 JUN 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

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 Process Supply Request Lines that Pass Validation

Use the Supply Chain Orchestration Work Area to Synchronize Supply Documents

Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning

Extend Supply Chain Orchestration's Integration with Inventory Management

Prevent Duplicate Supply Requests for Back-to-Back Sales Orders

View Manual Reservations for Your Back-to-Back Sales Orders

Use High-Volume Order Processing with Supply Chain Orchestration for Configured Items

Collaboration Messaging Framework

Collaboration Messaging Framework

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

Retransmit Unsuccessful B2B Messaging-Enabled Purchase Orders

Specify the Sender's Email Address for Outbound B2B Messages

Procurement Common

Common Procurement

Integrate and Extend Procurement Using REST Services

Worklist: Notifications and Approvals Work Area Includes New Task Filter

Procurement

Purchasing

Process Requisitions Into Purchase Orders in the Invoice Currency of the Supplier Site

Generate Reports on Purchase Orders Where B2B Communication Was Overridden

Selected Purchasing Bug Fixes in This Update

Supplier Model

Next Generation User Experience for Supplier Self-Service Registration

Selected Supplier Model Bug Fixes in This Update

Sourcing

Add Requisitions to an Existing Negotiation

Create Purchasing Documents from a Large Negotiation

Capture New Supplier Items in Negotiations

Allow Scoring Only Members to Message Suppliers

Copy Requisition Header Attachments to The Negotiation Header

Spend Classification

Create Reports in OTBI with Data from Expenses and Oracle Spend Classification

Procurement Contracts

Display Header and Footer on Downloaded Word Document

Display Header and Footer on Downloaded Word Document

Supply Chain Orchestration

Supply Chain Orchestration

Use REST API to Process Supply Request Lines that Pass Validation

Use the Create Supply Request REST API to process supply request lines that pass validation. If your supply request includes more than one supply request line, and if you set the AllowPartialRequestFlag attribute to Y in your REST API payload, then REST API will process the lines that pass validation. It won't process the lines that don't pass validation and mark them in error. If you set AllowPartialRequestFlag to N, and if any line in the supply request doesn't pass validation, then REST API will reject all lines in the request, including the ones that do pass validation. The default value for AllowPartialRequestFlag is N.

Use this feature to process the supply request lines that pass validation when your supply request includes more than one supply request line.

Steps to Enable

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

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)

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

Use the Supply Chain Orchestration Work Area to Synchronize Supply Documents

Use the Supply Chain Orchestration work area to synchronize supply documents between Oracle Supply Chain Orchestration and Oracle Procurement. Use this feature in your outside processing flow when Supply Chain Orchestration can't record a purchase requisition or purchase order because of a technical failure.

Keep your data up to date so Supply Chain Orchestration has the latest purchasing details and can accurately orchestrate supply for your sales orders.

Steps to Enable

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

Offering: Manufacturing and Supply Chain Materials ManagementNo Longer Optional From: Update 24A

Tips And Considerations

Synchronize your purchase requisitions and purchase orders:

  1. Go to the Supply Orchestration work area, then click Tasks > Manage Supply Lines.
  2. On the Manage Supply Lines page, click a link in the Supply Order Number column, such as 300100083428746.
  3. On the Supply Order Details page, click Actions > Synchronize Supply Documents.

Supply Chain Orchestration will synchronize data for your purchase requisitions and purchase orders between Supply Chain Orchestration and Procurement.

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)
    • Synchronize Supply Document (DOS_SYNC_SUPPLY_DOCS)

Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning

Use your own group codes to manage purchase requests in the Buyer Planning work area, which is available as part of Oracle Fusion Cloud Supply Chain Planning starting in update 23D. You can already use predefined codes such as Buyer, Category, Item, Location, Supplier, and None. This new feature allows buyer planners to create their own group code, and then use it to organize purchase requests into a group and take advantage of price breaks, order minimums, and so on. Oracle Supply Chain Orchestration will send the group code for each purchase request to Oracle Fusion Cloud Procurement. Oracle Procurement will group these purchase requests into purchase requisitions according to the value in the Group Code attribute.

Use this feature to group purchase requests to take advantage of price breaks, order minimums and other constraints.

Steps to Enable

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

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)

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

Extend Supply Chain Orchestration's Integration with Inventory Management

Oracle Supply Chain Orchestration allows you to create service mappings to integrate with Oracle Inventory Management starting in update 23B. This feature extends that capability. You can include a change entity and other attributes when you map attributes between Supply Chain Orchestration and your inventory management system. Here are the new attributes that you can map:

  • SourceOrganizationId 
  • SourceSubinventoryCode 
  • DestinationLocationId
  • ItemRevision 
  • FreightCarrierId 
  • ModeOfTransportLookup
  • ServiceLevelLookup 
  • ShipmentPriorityLookup 
  • FirmFlag 
  • RepriceFlag 
  • AllowItemSubstitutionFlag

Use service mappings to tailor how you process the change that happens in your supply chain during order fulfillment. You can now use service mappings to integrate with inventory, procurement, or manufacturing.

Steps to Enable

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

Tips And Considerations

  • This is an enhancement to an existing opt-in feature that is always optional.
  • Make sure your integration can satisfy the validations that Inventory Management applies. Your request payload might be fine, but Inventory Management might not accept the request. 
  • Make sure the objects that you reference in your integration algorithm exist, especially when you query for more than one request line. If you reference an object that doesn't exist at runtime, you might encounter an error.
  • If you encounter an error, fix it, then use the Supply Chain Orchestration work area to resubmit your request.

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

Prevent Duplicate Supply Requests for Back-to-Back Sales Orders

Prevent Oracle Supply Chain Orchestration from creating excess supply when a communication problem happens. Sometimes there's a disruption that prevents Oracle Order Management from sending a supply request to Supply Chain Orchestration. The disruption might never get resolved and orchestration never receives the request, or receive it only after a long delay. If Order Management doesn't receive a reply from Supply Chain Orchestration after a specific amount time, then Order Management might resend a create, update, or cancel request, and this makes it difficult for Supply Chain Orchestration to interpret how to handle the resent request.

Use this feature to prevent Supply Chain Orchestration from creating duplicate supply requests for the same demand when there's a communication problem between Order Management and Supply Chain Orchestration.

Steps to Enable

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

Access Requirements

The feature is available to any privilege that can create and submit a sales order.

View Manual Reservations for Your Back-to-Back Sales Orders

You might need to manually create a reservation when Oracle Supply Chain Orchestration can't create enough supply to meet Oracle Order Management's demand. You can view these reservations in the Supply Orchestration work area:

  • View details about each reservation that you create manually in a back-to-back flow for your sales order.
  • View the work orders, purchase requests, and transfer orders that create supply for these reservations.
  • Click a link that takes you to the work order, purchase request, or transfer order.
  • View the current state of the supply lines and tracking lines for each manual reservation.
  • View an icon on each supply line and tracking line to quickly determine whether you're using it for a manual reservation.
  • The Supply Orchestration work area displays a manual reservation only when supply doesn't meet the requested quantity.

Get a picture of the supply that's allocated to the sales order outside of automated processing.

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 24A

Tips And Considerations

  • Supply Chain Orchestration doesn't modify a manual reservation for a demand change that it receives from Order Management.  Any necessary changes must be done manually.
  • The quantity for the work order, purchase request, or transfer order might be different from the reservation's quantity or the quantity on the supply or tracking line because other requests might also use the work order, purchase request, or transfer order.

Access Requirements

The feature is available to any privilege that can create and submit a sales order.

Use High-Volume Order Processing with Supply Chain Orchestration for Configured Items

Use High-Volume Order Processing with Supply Chain Orchestration to orchestrate the supply that you need to fulfill configured items when you have a high volume of sales orders to process.

Improve performance when you need to orchestrate fulfillment for sales orders that have a lot of configured items, or your configured items are large and complex and have many child components.

Steps to Enable

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

Access Requirements

The feature is available to any privilege that can create and submit a sales order with configured items.

Collaboration Messaging Framework

Collaboration Messaging Framework

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.

NOTE: This feature was also made available in the April monthly update of 23B.

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.

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

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

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.

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.

NOTE: This feature was also made available in the April monthly update of 23B.

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.

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:

  • Personal Shopping Lists
  • Supplier Negotiation Responses

These REST APIs are enhanced:

  • Purchase Requisitions
    • POST, PATCH, and SUBMIT are supported for the Overriding Approver attribute on the requisition header.
    • Use the Withdraw custom action to withdraw a requisition or requisition line.
    • Use the Copy Lines from Requisitions custom action to duplicate all lines of a requisition to a target requisition.
    • Use the Copy Line custom action to duplicate a line of a requisition within the same requisition.
  • Draft Purchase Orders
    • PATCH is supported for the attributes Deliver-to Location and Requester for both open and draft purchase orders.
  • Procurement Approved Supplier List Entries
    • GET, POST, and PATCH are supported for the supplier item attributes (Country of Origin, Minimum Order Quantity, Fixed Lot Multiple, Purchasing UOM) in the approved supplier list.
  • Supplier Negotiations
    • GET is supported for the attribute that controls whether scoring-only members can send and receive supplier messages.

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

Access Requirements

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

Worklist: Notifications and Approvals Work Area Includes New Task Filter

In the Worklist: Notifications and Approvals Work Area, a drop-down list has been added to filter tasks by when they were created. This additional filter applies only to the default My Tasks view, showing tasks created in the last seven days by default. The filter's options include 7, 14, or 30 days. Select All to display a complete list of tasks for you and your groups. The filter drop-down is also available in BPM Worklist if the My Tasks view and Me & My Groups filter are selected, which is the default.

Response time is improved by having a filtered list of tasks when the work area opens.

Steps to Enable

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

Tips And Considerations

  • Because the new task filter applies only to the default My Tasks view, if you select a different view in the work area, for example, Initiated Tasks, it won't be available.
  • If you don't see this new filter in 23B, you'll see it in 23C.

Key Resources

Procurement

Purchasing

Process Requisitions Into Purchase Orders in the Invoice Currency of the Supplier Site

Generate purchase orders from requisitions in the invoice currency of the supplier site. You can now create requisitions where the price is negotiated in a foreign currency and release purchase orders to fulfill them in the local currency of the business unit. To release the purchase orders in the local currency, you must set the supplier site invoice currency.

You can use this feature for these business scenarios:

  • Prices on blanket purchase agreements are negotiated with suppliers in a foreign currency (for example, USD), and purchase orders need to be generated from requisitions in the local currency (for example, INR).

  • Procurement Requester creates noncatalog requests by providing the negotiated price in a foreign currency (for example, USD), and purchase orders need to be generated from those requisitions in the local currency (for example, INR).

  • Requisitions originating from a punchout catalog contain the negotiated price in a foreign currency (for example, USD), and purchase orders need to be generated from those requisitions in the local currency (for example, INR).

These screen captures illustrate the feature:

In this example, a blanket agreement is created with the supplier site as Mumbai, and the price is negotiated in US dollars.

Blanket Agreement in Foreign Currency

The local invoice currency of the supplier site Mumbai is Indian Rupees.

Invoice Currency of the Supplier Site

A requisition is created in US Dollars, which is a foreign currency for the Vision India business unit.

Requisition in Foreign Currency

When the requisition is processed into a purchase order, it's created in Indian Rupees, which is the local currency of the Vision India business unit.

Purchase Order in Local Currency

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

  • You can use this feature for purchase orders created from backing requisitions regardless of how the purchase order was created from the requisition. The purchase order could have been created using touchless buying, the Process Requisitions page, or the Requisition Processing Requests REST API. However, purchase orders that don't have a backing requisition can't be released in a different currency if they reference a blanket purchase agreement.
  • When you cancel a purchase order, unfulfilled requisition demand will be reinstated in the purchase order currency instead of the original requisition line currency.
  • When using this feature:
    • The Conversion Rate Type on the purchase order defaults from the Procurement Business Unit Configuration.
    • The Conversion Date on the purchase order defaults from the purchase order creation date in the legal entity's time zone.
  • You can't procure configured items in the local currency using this feature.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

  • Create Purchase Order from Requisitions (PO_CREATE_PURCHASE_ORDER_FROM_REQUISITIONS_PRIV)

This privilege was available prior to this update.

Generate Reports on Purchase Orders Where B2B Communication Was Overridden

Generate reports and inquiries on purchase orders for which B2B communication was overridden for another communication method by the buyer. The Override B2B Communication attribute is now available in this subject area and folder:

  • Procurement - Purchasing Real-Time 
    • Purchase Order Header Detail

You can use this feature to get visibility into purchase orders where the supplier site was set up for B2B communication, but the buyer chose to override B2B communication.

This screen capture illustrates the feature:

OTBI Report with Override B2B Communication

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 Override B2B Communication of Purchase Orders feature. If you previously opted in to the Override B2B Communication of Purchase Orders feature, then this feature is automatically enabled.
  • After you have opted in to the feature, add the Override B2B Communication attribute 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.

Tips And Considerations

The Override B2B Communication attribute is available without opt in. However, to generate reports and inquiries on purchase orders where B2B communication was overridden, you must opt in to the Override B2B Communication of Purchase Orders feature.

Access Requirements

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)

This duty role was available prior to this update.

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.

Bypass Location Validation on Changes to Fulfilled Purchase Orders

Before this update, you couldn't make changes to purchase orders with invoicing or receipt activity if the default ship-to location, schedule's ship-to location, or distribution's deliver-to location were inactive. After this update, you can set the ORA_PO_SKIP_READONLY_LOC_VAL profile option to Y to submit changes even if the locations are inactive.

Oracle reference: 35171583

Validate End Date on Purchase Agreements

Before this update, you could update the End Date on a purchase agreement to a past date even if there were purchase orders in the approval hierarchy created after the updated end date. After this update, the purchase agreement change order won't get implemented if approved purchase orders are created after the updated end date.

Oracle reference: 34360380

Use Procurement BU Parameter in the Purge Processed Open Interface Documents Program

Before this update, the Purge Processed Open Interface Documents scheduled job deleted interface records from all procurement BUs irrespective of the value selected when running the job. After this update, the scheduled job will only delete the interface records (including those in other languages) for the Procurement BU selected as the input parameter.

Oracle reference: 35024239

Include Custom Document Styles in Purchase Order Approval Notification Titles

Before this update, you couldn't include user-defined document style names in the purchase order approval notification title. After this update, you can include these additional attributes in the approval notification title:  DocumentStyleDisplayName and DocumentTypeDisplayName. Use the Oracle BPM Worklist to configure the title.

Oracle reference: 35174219

Fix Drill down from Rejected Orders in the Orders Requiring Attention Infolet

When navigating to the Manage Orders search results from the count of rejected orders in the Orders Requiring Attention infolet, the search results will include closed documents so that the number of results shown on the Manage Orders page matches the count shown in the infolet.

Oracle reference: 34969326

Default the Communicate Updates Parameter on the Initiate Retroactive Price Update Scheduled Job

Before this update, when retroactive pricing was initiated using the Initiate Retroactive Price Update scheduled job, updated purchase orders weren't communicated to suppliers even when the Communicate Price Updates option was selected on the blanket agreement. After this update, the Communicate Updates parameter in the scheduled job will default from the agreement control so that price changes are communicated based on the agreement setup. To prevent the updated releases from being communicated to the supplier, uncheck the Communicate Updates parameter.

Oracle reference: 35112671

View Documents Matching the Range's End Value When Using Date Ranges to Search

Before this update, when you searched for purchase orders and purchase agreements using a condition like Closed Date between 1-Jan-2022 and 31-Jan-2022, documents whose closed date matched the range's end value, 31-Jan-2022, weren't returned in the search results. After this update, the search results will include documents matching the range's end value.

Oracle reference: 34842447

Steps to Enable

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

Supplier Model

Next Generation User Experience for Supplier Self-Service Registration

Supplier self-service registration greatly reduces work onboarding suppliers by eliminating internal data entry and improving supplier data quality. This enables your supplier management team to focus on more valuable activities like supplier qualification and performance evaluation.

If self-service registration isn’t extremely easy and intuitive for suppliers, it becomes a support burden for internal resources and results in low registration completion rates. Next generation supplier self-service registration is a completely redesigned user experience based on the Redwood Design System. Highlights include:

  • Guided process optimized for easy capture of profile details and other requirements
  • Geographically responsive data entry

The requester begins by entering their email to receive a one-time access code which is used to start their supplier registration. This security feature prevents bots from submitting registration requests and ensures a valid email is associated with each registration. The requester can return later to finish the registration by providing their email again to get a new access code which will retrieve their saved registration. The supplier registration URL is always the same for all users, even for users returning to finish their registration, which simplifies supplier support.

Registration Start: Enter Your Email

Registration Start: Enter Your Email

You can personalize the start page to communicate information about your supplier registration and onboarding process. You can also add information or corporate branding to tailor the email notification that sends the one-time access code.

Email with One-Time Access Code

Email with One-Time Access Code

Registration Start: Enter Access Code

Registration Start: Enter Access Code

After email verification, the requester is then guided to provide company information, contacts, addresses, business classifications, bank accounts, products and services categories, and questionnaire responses. These registration pages are simplified for quick entry and most of them can be configured as hidden, optional, or required. Two registration configurations are supported to capture different profile information depending on the intended supplier business relationship. You may wish to capture lighter profile requirements for prospective suppliers used in sourcing, and more detailed information for registration requests of suppliers you are approving for spend.

Company Details

Company Details

On company details, the country is required to drive defaulting on subsequent pages. Another usability improvement involves tax information, when returning to complete a registration the requester no longer needs to re-enter taxpayer ID and tax registration number.

Contacts

Contacts

On Contacts, the verified email is defaulted for the first contact, also the mobile, phone, and fax country codes are defaulted based on the country selected on company details.

Addresses

Addresses

On Addresses, the country is used to default the address country as well as the phone and fax country codes.

The Loqate Smart Address service is another integrated service in registration and is a highly recommended feature to opt-in. The service manages detailed address locations for over 240 countries and provides a superior user experience with an autosuggest address search that eliminates data entry and input errors.

Bank Accounts

Bank Accounts

Capturing a supplier bank account is greatly simplified with country-driven logic to help the requester quickly provide bank account details unique to the country. The default country layout presented is based on the country provided earlier. A seeded configuration is delivered for most countries out of the box. For example, the routing number is presented for a United States bank account, whereas sort code is used in the United Kingdom layout. You can modify or add country-specific rules to show or hide attributes, make them required or relabel them. Country-specific layouts help requesters provide the correct information only for the necessary fields which avoids having to return registrations for correction.

The Business Classifications page is streamlined to help the requester quickly determine if any of the diversity classifications are applicable to their company. If yes, the detailed form is presented to capture classification and certificate details. The Products and Services page presents summarized categories for selection indicating the types of goods and services the supplier can provide. The category tree is configurable providing flexibility on the level of detail you wish to track suppliers. Lastly, the Questionnaire page allows you to collect other requirements and documents unique to your business to evaluate potential suppliers. It can present conditional questions based on responses and on registration information provided earlier. 

After providing all information, the requester submits the request on the final page. On submission, guidance is provided if any corrections or missing information requires attention, if no, a success confirmation is presented with a registration request number for reference in any follow-up communications. You can personalize this page to include information such as contact details the requester can use for further communication.

Confirmation Message

Confirmation Message

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

The URLs to access the next-generation supplier registration flow are available on the Configure Procurement Business Function setup task. These URLs replace the old self-service registration URLs after you opt in to the feature.

The following setup steps are optional, depending on your requirements:

  1. Configure Supplier Registration and Profile Change Request setup task:  Access this setup task to update the configuration options and controls to meet your business process objectives for supplier registration.
  1. Use user interface text tool editor to change the company name shown on the registration pages.
  1. Use Country-Specific Bank Account Rules: You can create or update the country-specific bank account rules using the Bank Account User Rules REST API directly or via the Oracle Visual Builder Add-in for Excel. Supplier registration-specific rules are identified by the page name Supplier Registration. More details are available on Oracle Help Center, see Bank Account User Rules REST API.

 NOTE: When a bank account attribute has both a country-specific rule and a supplier registration rule defined, the latter is given priority, meaning the supplier registration rule is considered first. If a supplier registration rule doesn't exist, the seeded ORA page rule is considered else the attribute is displayed.

  1. Loqate supplier address service requires a SKU subscription and feature opt-in:
  • SKU:  Oracle Address, Email and Phone Verification Cloud Service
  • Opt-in: Smart Data Service for Supplier Addresses 

Tips And Considerations

  • In Update 23C, this new supplier self-service registration flow supports only your default language. Starting in Update 23D, it's enhanced to support multiple languages. You can append &ojSpLang=<language code> at the end of the registration URL if you want to send out language specific URL to your suppliers. For example, append &ojSpLang=es for Spanish suppliers. When no language is specified in the URL, it will use the browser language if that language is installed in your Fusion instance.

  • Use Visual Builder Studio to extend supplier registration for your organization:
    • In Updates 23C and 23D, you can add instruction text, hyperlinks, or images on registration pages to guide users on your registration process. You can also add conditions on your extensions based on country, procurement BU, business relationship, supplier type and organization type, to make these changes effective. Only the questionnaire page doesn’t support extension, however, instruction text can be added when setting up the questionnaire. Descriptive flexfields aren't supported until 24A.  Don't make other extension changes in VB Studio as they won't be compatible with future updates and will cause pages to not render correctly.
    • In Update 24A, a new simplified user interface will be available to extend individual attributes on select pages including descriptive flexfields. You will be able to make these attributes required or optional, read-only, or editable, and show or hide them based on specific criteria such as country.  Also, you’ll be able to add your company logo along with your company name. Refer to the 24A What's New when published for all the details.
  • After you opt-in to this feature, the old URLs won’t work except for saved or returned requests that requesters can still submit using the URLs sent to them.

  • This new registration flow uses the existing setup task, Configure Supplier Registration and Profile Change Request.  All settings in this setup task will continue to be followed in the new flow, for example; the configuration to hide business classification or setting attachments in company details as required for both business relationships. However, all personalizations enabled in your current registration flow that are still required need to be redone using Visual Builder Studio.

  •  After the registration request is submitted, all the existing functionalities including request to resubmit action and approvals remain unchanged.

Key Resources

  • Extend the Oracle Cloud Applications with Visual Builder Studio available on Oracle Help Center.
  • Supplier registration-specific bank account user rules are identified by the page name Supplier Registration. More details on the bank account user rules are available on Oracle Help Center, see Bank Account User Rules REST API.

  • Next Generation User Experience for Supplier Self-Service Registration TOI.

Access Requirements

  • Users who are assigned a configured job role that contains this privilege can create or update bank account rules:
    • Manage Bank (CE_MANAGE_BANK_PRIV)
  • Users who are assigned a configured job role that contains this privilege can configure the supplier registration pages:
    • Configure Supplier Registration (POZ_CONFIGURE_SUPPLIER_REGISTRATION_PRIV)

Selected Supplier Model Bug Fixes in This Update

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

Import Supplier Records Using FBDI Templates on Mac Computers

You can now download the latest FBDI templates to import supplier records from your Mac.

Oracle reference: 34967407

Remove Duplicate Search Results for Supplier Addresses with Alternate Names

Before this update, the supplier address search returns duplicate records in LOVs for address elements such as city, when alternate names are defined in address elements. With this update, you can set the  HZ_ADDRESS_DISABLE_ALT_NAMES profile option to Yes at the site level so that the duplicate search results are removed.

Oracle reference: 35083384

Steps to Enable

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

Sourcing

Add Requisitions to an Existing Negotiation

When processing requisitions, you can now add new requisition lines to either a draft or an active negotiation instead of creating a new negotiation every time. When adding requisitions to an active negotiation, an amendment is created.

The requisition lines are added to the negotiation with all relevant information such as price, quantity, requested date, and attachments. Suppliers from the requisition are added to the supplier invitation list as well.

When adding lines to a negotiation using the document builder in Oracle Purchasing, you have the option to group matching requisition lines into a single negotiation line. When matches are found, the quantity from the new requisition line is added to the existing negotiation line quantity. If no matches are found, then a new negotiation line is created for the requisition line.

Add Requisition Lines to Existing Negotiation

Search and Select Active or Draft Negotiations

Edit document builder for adding requisition lines to existing negotiations

Edit Document Builder for Adding Requisition Lines to Existing Negotiations

If you get a requisition for the same item for which there’s already an ongoing negotiation, you can now add it to the existing negotiation instead of creating a new negotiation.

Adding new requisition lines to existing negotiations leads to higher savings from better negotiation deals, and saves considerable time with fewer transactions, and automated processing.

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

  • The Group Requisition Lines option value is defaulted from the Configure Procurement Business Function setup page.
  • For purchase order outcome, requisition lines are grouped if these criteria match:
    • Line type
    • Item, Item revision, and Item description
    • Category
    • Unit of measure (UOM)
    • Requisitioning business unit
    • Ship-to location
  • For agreement outcome, requisition lines are grouped if these criteria match:
    • Line type
    • Item, item revision, and item description
    • Category
    • Unit of measure (UOM)
  • If different Requested delivery dates are specified for multiple requisition lines, which are grouped, then the earliest date is stamped on the negotiation line.
  • If two or more existing negotiation lines match the requisition line, then it’s added to the negotiation line with the highest line number.
  • If the requisition line has a suggested supplier, then it’s added to the negotiation invitation list, only if the supplier and supplier site combination doesn’t already exist in the draft negotiation. For negotiations in the Active status, this isn’t supported, since amendments currently don't support updating the supplier invitation list.
  • Both requisition header and line level attachments are copied to the negotiation line.
  • Only requisition attachments with these categories are copied to the negotiation line: To Buyer, To Supplier, and Miscellaneous.
  • If you have approvals set up, the amendment process will trigger approval of the changes made to the negotiation from adding the new requisition lines.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

  • Create Supplier Negotiation (ORA_PON_CREATE_SUPPLIER_NEGOTIATION_PRIV)

This privilege was available prior to this update.

Create Purchasing Documents from a Large Negotiation

You can now create purchasing documents for large negotiations in Oracle Purchasing using background processes.

You need to run two processes to create purchasing documents in Purchasing – Create Purchasing Documents and Submit Purchasing Documents.

Once award is completed, click the Create Purchasing Documents action to trigger a background process. You will be notified once this process completes.

Next, click the Review and Submit Purchasing Documents action to navigate to the page where you can review the purchasing documents. You now have the ability to search the lines in each purchasing document using multiple filtering criteria. You also have the option to retrigger purchasing document creation by clicking the Reset Purchasing Documents button.

After review, you can click Submit. This action triggers the Submit Purchasing Documents background process, which creates the purchasing documents in Purchasing. Once the process is successfully completed, you will be notified. Now you can view the purchasing documents created from the negotiation and can even drill down to the purchasing documents to view their details.

Actions to cancel or create purchasing documents for large negotiation award

Actions to Cancel or Create Purchasing Documents for Large Negotiation Award

Review and submit purchasing documents action

Review and Submit Purchasing Documents Action

Review and submit purchasing documents

Review and Submit Purchasing Documents

Monitor processes

Monitor Processes

View purchasing documents created from large negotiation award

View Purchasing Documents Created From Large Negotiation Award

You can now directly create purchasing documents in Oracle Purchasing from large negotiation award, based on your business need.

Steps to Enable

Setup: Negotiation Style

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

Negotiation Style Controls

Setup: Profile Option

  • A new profile option ORA_PON_CREATE_PO_MAX_LINES_LIMIT (Maximum Lines in a Large Negotiation Outcome Document) is introduced, which sets the upper limit for lines in a purchasing document created from the large negotiation award. If this limit is reached, another purchasing document is created for additional lines. The profile option value must not exceed 10,000.

Profile value setup

Profile Value Setup

Tips And Considerations

  • After update 23C, for all ongoing large negotiations, the Create Purchasing Documents action will be automatically available.

Key Resources

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

  • Create Purchase Order (ORA_PO_CREATE_PURCHASE_ORDER_PRIV)
  • Create Purchase Agreement (ORA_PO_CREATE_PURCHASE_AGREEMENT_PRIV)

This privilege was available prior to this update.

Capture New Supplier Items in Negotiations

In the 23B update, when negotiating inventory items, the supplier item, manufacturer, and manufacturer part number are displayed to suppliers, from item relationships in Product Information Management (PIM).

With this update, supplier bidders can provide new supplier items when creating responses to both inventory and description-based line items. The new supplier items are copied to the purchasing documents generated after award. In scenarios where there’s no supplier item for the inventory item, the new supplier item is automatically added to item relationships in Product Information Management (PIM) if enabled in BU configuration.

When creating a response to a negotiation with a backing requisition, the supplier bidders are presented with the supplier items coming from the requisition lines and can update them if needed. Similarly, when re-negotiating an existing blanket purchase agreement, the suppliers can view and update the supplier items captured in the agreement.

Capture New Supplier Item During Response Creation

Improve transaction accuracy and PIM data quality by capturing supplier items during response creation.

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 automatically add new supplier items (captured in negotiation responses) to item relationships in PIM, go to the Configure Procurement Business Function page, and select the Automatically add new supplier items to item relationships check box.

To facilitate seamless interaction between the Sourcing work area and Product Information Management (PIM) work area, an integration setup is required.

  1. Navigate to the Setup and Maintenance work area.
  2. Click Manage Setup Content.
  3. In Topology Definition, click Manage Integration of Additional Applications.
  4. Create a new integration setup.
  5. Fill the details as follows:
    1. Application Name: PON_DISPLAY_SUPP_ITEM_AND_MFG_PART_NUM
    2. Full URL: <customer_POD_URL>/fscmRestApi/resources/latest
    3. Partner Name: PON_DISPLAY_SUPP_ITEM_AND_MFG_PART_NUM
    4. Security Policy: oracle/wss_username_token_over_ssl_client_policy
    5. Username: <user name>
    6. Password: <As applicable>
  6. Click Apply and then click Save and Close.

Integration Setup with Product Information Management (PIM)

Tips And Considerations

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

  1. The new supplier item is updated in item relationships in PIM only when there is no existing supplier item already associated with the item.
  2. Capturing and updating the manufacturer or manufacturer part number isn’t supported yet.

Key Resources

Access Requirements

  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Create Supplier Negotiation (PON_CREATE_SUPPLIER_NEGOTIATION_PRIV)
    • Manage/Edit Supplier Negotiation (PON_EDIT_SUPPLIER_NEGOTIATION_PRIV)
    • Create Response (PON_CREATE_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)
    • Edit Response (PON_EDIT_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)
    • Create Supplier Negotiation Response as Surrogate (PON_CREATE_SURROGATE_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)
    • Submit Supplier Negotiation Response (PON_SUBMIT_SUPPLIER_NEGOTIATION_RESPONSE_PRIV)

Additionally, these privileges should be provided for an integration user to add new supplier item in Product Information Management:

  • Manage Trading Partner Item Rest (EGI_MANAGE_TPI_REST)
  • Manage Trading Partner Item Relationships Rest (EGI_MANAGE_TPI_REL_REST

These privileges were available prior to this update.

  • The Integration user should have the data security as per the below details:
  1. Data Resource: Item for Table EGP_SYSTEM_ITEMS_B
  2. Data Set: All values
  3. Actions: Maintain Item Basic

Allow Scoring Only Members to Message Suppliers

Currently, the scoring-only access members in the collaboration team can’t view the supplier names nor can they communicate with suppliers. In many cases, the scoring-only access members are required to know the background of the suppliers for better evaluation. They also need to message suppliers so that supplier queries on negotiation requirements are resolved in time.

With this feature, you can control which scoring-only members can see the supplier names and send an online message to suppliers. A new control, Supplier Messages is available when defining a collaboration team. Here you can select if the member with scoring-only access can send and receive supplier messages, only receive messages from suppliers, or be restricted from any messaging with suppliers.

Access to Supplier Messaging for Scoring only Members

  • Visibility of supplier information to scoring-only members promotes efficient evaluation of supplier responses.
  • Direct communication between suppliers and scoring-only members enables faster resolution of supplier queries.

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

  • You must use a negotiation style in which team scoring is enabled.
  • You must also enable team scoring in the negotiation.

Access Requirements

Users who are assigned a configured job role that contains these privileges can access this feature:

  • Create Supplier Negotiation (PON_CREATE_SUPPLIER_NEGOTIATION_PRIV)
  • Create Supplier Negotiation Template (PON_CREATE_SUPPLIER_NEGOTIATION_TEMPLATE_PRIV)
  • Edit Supplier Negotiation (PON_EDIT_SUPPLIER_NEGOTIATION_PRIV)
  • Manage Supplier Negotiation Collaboration Team (PON_MANAGE_SUPPLIER_NEGOTIATION_COLLABORATION_TEAM_PRIV)

These privileges were available prior to this update.

Copy Requisition Header Attachments to The Negotiation Header

Currently, when a negotiation is processed from a requisition, the attachments from the requisition header are copied to each negotiation line. This results in having duplicate attachments in the negotiation. High number of attachments may sometimes lead to delays or failure in sending approval notifications.

With this feature, the attachments from the requisition header are copied to the negotiation header instead of each negotiation line. When purchase orders are generated after award, the negotiation header attachments are copied to the PO header.

Requisition Header Attachments Copied to Negotiation Header

Copy requisition header attachments to the negotiation header instead of each negotiation line for improved performance when there are many lines.

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

  • Attachments with categories: To Buyer, To Supplier, and Miscellaneous are copied from Requisitions to Negotiations.
  • If your negotiation is awarded to multiple suppliers, then the attachments of the category 'To Supplier' that are specific to suppliers will be copied over to all the purchasing documents. This would result in suppliers receiving attachments that are not applicable to them. In such cases, the buyer must remove 'To Supplier' attachments from the negotiation header before creating the purchasing documents.

Access Requirements

Users who are assigned a configured job role that contains this privilege can access this feature:

  • Create Supplier Negotiation (PON_CREATE_SUPPLIER_NEGOTIATION_PRIV)

This privilege was available prior to this update.

Spend Classification

Create Reports in OTBI with Data from Expenses and Oracle Spend Classification

Use real-time recategorized expense transaction data from Spend Classification within your Oracle Transactional Business Intelligence dashboards. Create new reports or update your existing reports by adding approved expense line category predictions from Spend Classification to further your analysis and improve your reporting.

Expense Transactions Real Time subject area

After you’ve classified expenses in Spend Classification, you can unlock new insights into you spend through reports in OTBI that use your spend classification data.

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 on the Oracle Help Center.

Access Requirements

Users who are assigned the Business Intelligence Authoring (BI Author) duty role can create or extend OTBI reports. For further information on the privileges required to access expense reports, refer to the Security Reference for Financials guide on Oracle Help Center.

Procurement Contracts

Display Header and Footer on Downloaded Word Document

You can add images, logos, and contract attributes such as the contract number, contract type, party name and so on, to the header or footer of your layout template. Content you've added to the header and footer is displayed when you download the contract to Microsoft Word in DOCX format.

Display Header and Footer on Downloaded Word Document

Here are some examples of content you can add to the header or footer:

  • Attributes such as the contract number, contract type, party name
  • Descriptive flexfield values
  • Logos or images, in PNG or JPEG format
  • Tables

This improves the consistency of the contract when viewed across different formats such as RTF, Word, or PDF, and provides contextual information to easily identify to which contract the document relates.

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: Enterprise Contracts

Tips And Considerations

This feature aims to improve consistency across the contract formats, so bear in mind that any new content that you choose to add to the header or footer layout to be displayed in the downloaded Word document will also be reflected in the PDF preview since they use the same layout template.

Display Header and Footer on Downloaded Word Document

You can add images, logos, and contract attributes such as the contract number, contract type, party name and so on, to the header or footer of your layout template. Content you've added to the header and footer is displayed when you download the contract to Microsoft Word in DOCX format.

Display Header and Footer on Downloaded Word Document

Here are some examples of content you can add to the header or footer:

  • Attributes such as the contract number, contract type, party name
  • Descriptive flexfield values
  • Logos or images, in PNG or JPEG format
  • Tables

This improves the consistency of the contract when viewed across different formats such as RTF, Word, or PDF, and provides contextual information to easily identify to which contract the document relates.

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: Enterprise Contracts

Tips And Considerations

This feature aims to improve consistency across the contract formats, so bear in mind that any new content that you choose to add to the header or footer layout to be displayed in the downloaded Word document will also be reflected in the PDF preview since they use the same layout template.