Update 23A

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
14 SEP 2023	Supplier Model	Create Supplier Sites with Longer Names	Updated document. Added opt in expiry.
06 MAR 2023	Purchasing	Search for Purchase Orders by Project Numbers and Task Numbers as a Buyer	Updated document. Revised screenshots and tips and considerations.
25 JAN 2023	Purchasing	Create Purchase Order Lines with Negative Amounts	Updated document. Revised tips and considerations.
25 JAN 2023	Common Procurement	Integrate and Extend Procurement Using REST Services	Updated document. Updated feature description with two new, backported resources.
11 JAN 2023	Purchasing	View Negotiation Details for Purchase Orders and Purchase Agreements Created as Negotiation Award Outcomes	Updated document. Revised tips and considerations.
15 DEC 2022	Common Procurement	Get News Feed Suggestions On Your Next Likely Actions	Updated document. Revised feature description.
02 DEC 2022			Created initial document.

Overview

HAVE AN IDEA?

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

GIVE US FEEDBACK

We welcome your comments and suggestions to improve the content. Please send us your feedback at oracle_fusion_applications_help_ww_grp@oracle.com.

DISCLAIMER

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

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

Optional Uptake of New Features (Opt In)

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

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

Here’s how you opt in to new features:

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

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

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

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

Opt In Expiration

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

Feature Summary

Supply Chain Orchestration

Supply Chain Orchestration

Improve Supply Tracking for Sales Orders in Your Back-to-Back Flows

Keep up-to-date with the latest changes in supply and manage supply requests in your back-to-back flow even when you ship only part of the order line.

Assume only some of the quantity for your order line is available to ship, so Order Management splits the order line into two fulfillment lines, fulfillment line x and fulfillment line y. Line x has the quantity that is available to ship. Line y has the quantity that isn't yet available to ship.

If you enable this feature, then Supply Chain Orchestration doesn't close the supply order when Oracle Shipping ships line x. Instead, Orchestration keeps the supply order open until Shipping also ships line y, or until Oracle Order Management cancels the request. Orchestration continues to orchestrate changes in demand and supply for line y as long as the supply order remains open.

Realize these benefits:

• Save time and work more efficiently. You don't have to manually create a new line for supply that isn't yet available. Supply Chain Orchestration will automatically create new supply for you.

• Track how much supply you have used even when Shipping has shipped only line x.

• Get timely updates so you can accurately track the progress that Orchestration is making to create supply for line y.

• Reduce or eliminate supply disruptions for line y. Orchestration will automatically update supply so it has the latest details for your line.

• Modify line y, and Orchestration will manage that change in your purchasing, inventory, or manufacturing organization. 

• Manage an interruption to supply on line y in the same way that you do when you haven't partially shipped the line.

• Manage supply recommendations even when you have partially shipped one or more of them.

• Manage any number of shipments.

• Track each partial or full cancellation.

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: Order Management  No Longer Optional From: Update 23C

Tips And Considerations

Consider these guidelines:

• If you need to take action on line y, then you must first use the Unschedule action on line y, and then use the Schedule action on line y. Orchestration will then create a new a supply order for the quantity on line y. For details, see Schedule Fulfillment Lines Manually.

• If you modify the warehouse or the item on line y, then Orchestration will cancel the supply order and make that supply available to other demand. It will also cancel any new supply that it's currently creating for line y. Orchestration will do this even if you enable the Defer Online Processing of Inventory Updates shipping parameter for the warehouse.

• If you enable the Defer Online Processing of Inventory Updates shipping parameter for the warehouse, then Supply Chain Orchestration won't use the Improve Supply Tracking for Sales Orders in Your Back-to-Back Flows feature for that warehouse.

• The split behavior in Order Management doesn't affect your purchase orders, work orders, or transfer orders.

Use This Feature with Other Features

You can enable only the Improve Supply Tracking for Sales Orders in Your Back-to-Back Flows feature, or you can also enable the Order Management's Update Attributes On Split Order Lines For Partial Shipments feature.

Features That You Enable	Description
Enable only the Improve Supply Tracking for Sales Orders in Your Back-to-Back Flows feature.	Orchestration keeps the supply order open, and it will track supply for line y until Shipping ships line y. You can modify the scheduled ship date or warehouse on line y, and Orchestration will automatically update supply so it has the latest details for line y. You can't modify the quantity on line y after Shipping ships line x.
Enable both features.	You can modify the quantity, scheduled ship date, or warehouse on line y even after Shipping ships line x. Order Management will use your revised values to fulfill the line and Orchestration will automatically update supply so it has the latest details for the line. If you enable the Update Attributes on Split Order Lines for Partial Shipments feature, then you also automatically enable the Improve Supply Tracking for Sales Orders in Your Back-to-Back Flows feature. For details, see Update Attributes on Split Order Lines for Partial Shipments.
Don't enable either feature.	Orchestration will close the supply order as soon as Shipping ships any part of the order line, and Orchestration won't track any other modifications that you make on the line. You can't modify the quantity on line y after Shipping ships line x.

Key Resources

• Watch Improve Supply Tracking for Sales Orders in your Back-to-Back Flows Readiness Training
• Implementing Order Management
• Using Supply Chain Orchestration

Access Requirements

• Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)

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.

Display Your Own Work Order Status

The Supply Chain Orchestration work area displayed only predefined statuses prior to update 23A. For example, assume you created your own status named MyStatus. The work area displayed one of the predefined statuses even if the work order's run time status was MyStatus. With this update, the work area will display MyStatus.

Oracle reference: 34543645

Steps to Enable

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

Collaboration Messaging Framework

Collaboration Messaging Framework

Receive a Brazil Electronic Freight Other Services Invoice

Use the new secretaria de fazenda (SEFAZ) Brazil Electronic Freight Other Services Invoice V3.00 message (BR_CTEOS_3.00_IN) to receive electronic freight invoices for other transportation-related services.

This predefined message definition is available as an inbound message (ORA_SZ_BR_CTEOS_3.0_IN) for the SEFAZ service provider on the Manage Collaboration Messaging Service Providers page. This message is processed with other Brazilian messages when using the Import Brazil Electronic Documents scheduled process.

ORA_SZ_BR_CTEOS_3.00_IN

This new predefined message allows you to implement conhecimento de transporte eletrônico (CT-e) electronic bill of lading for other services by taking advantage of the information that can be extracted from XML, reducing user manual intervention.

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

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 this privileges can access this feature:
  • Manage Service Provider (CMK_MANAGE_SERVICE_PROVIDER_PRIV)

Send and Receive UBL PEPPOL Electronic Invoices

Use the new predefined message definitions UBL-2.1-PEPPOL-Invoice-Out and UBL-2.1-PEPPOL-Invoice-In to send and receive universal business language (UBL) pan-European public procurement online (PEPPOL) invoice messages to and from PEPPOL access points.

UBL-2.1-PEPPOL-Invoice-Out Message

UBL-2.1-PEPPOL-Invoice-In Message

Set up these message definitions as outbound and inbound collaboration messages for a trading partner. Associate the trading partner and the invoice outbound document with a customer by using the Manage Customer Account Collaboration Configuration task. Associate the trading partner and invoice inbound document with a supplier by using the Manage Supplier B2B Configuration task in the Collaboration Messaging work area.

These new messages enrich the e-invoicing process by providing additional data elements to meet PEPPOL standards and some country-specific requirements.

Steps to Enable

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

Tips And Considerations

You must create the following list of domain value maps before you can exchange UBL PEPPOL messages. Populate each domain value map with the values from the code lists.

Domain Value Maps	Code Lists
CURRENCY_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/ISO4217/
INVOICE_TYPE_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-inv/
INVOICE_TRX_TYPE_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL1001-inv/
EAS_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/eas/
ICD_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/ICD/
CHARGE_REASON_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL7161/
UOM_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNECERec20/
COUNTRY_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/ISO3166/
PAYMENT_METHOD	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL4461/
TAX_CATEGORY_CODE	https://docs.peppol.eu/poacc/billing/3.0/codelist/UNCL5305/

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)
  • Manage Customer Account Collaboration Configuration (CMK_B2B_CUSTOMER_ACCOUNT_TRADING_PARTNERS_PRIV)

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:

• Shopping Lists
• Draft Supplier Negotiation Responses
• Procurement Approved Supplier List Entries (available in the January monthly update of 23A)
• Approved Supplier List Source Documents (available in the January monthly update of 23A)

These REST APIs are enhanced:

• Requisition Preferences
  • POST and PATCH are supported with the following restrictions:
    • Requester has to be the same as the Preparer.
    • Destination type can only be Expense.
    • Preference type can only be SSP.
    • Users who are assigned the Procurement REST Service duty role and its aggregate privileges can POST preferences for all users, while users with the Manage Requisition privilege can post their own preferences only.
  • DELETE is supported for integration user roles.

• Draft Purchase Orders
  • PATCH is supported for Note to Supplier on the order line, and Note to Receiver on the order schedule.
  • POST is supported for the Distribute Project Costs action.

• Purchase Orders
  • GET is supported for these attributes: Credit and Ordered Before Adjustments.

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.

Get News Feed Suggestions On Your Next Likely Actions

Get suggestions on your next likely actions in your news feed layout. This feature is currently in Controlled Availability and is available in Oracle Fusion Cloud Procurement. Artificial intelligence and machine learning algorithms predict and suggest the actions each user is most likely to take during a session. The algorithms use historic navigation behavior and patterns of each user and users like them to determine which navigation target they’re most likely to visit.

Oracle Fusion Cloud Applications have a wide range of functionality and it can sometimes be difficult to know how to navigate to a task. With news feed suggestions, you can get to the tasks that matter faster. For example, if reviewing and approving expense reports is a task commonly performed by managers in your organization, new managers will receive a suggestion in their news feed to perform that task. Or if a few team members are entering performance goals, other members of that team see this task as a suggestion in their news feed.

These are some of the business benefits of this feature:

• Receive recommendations in your news feed on your next likely actions during that session
• Discover actions that other users like you have taken within Fusion
• As an administrator, you can pin specific task flow pages as a suggestion to raise the visibility of the task

Suggestions Tab in the News Feed Layout Showing Six Recommendations

Steps to Enable

To enable this feature, you need to log a Service Request (SR) through My Oracle Support and request for a promotion code. This feature is currently in Controlled Availability and requires a promotion code. For details, see PRC:PO: How to Apply for News Feed Suggestions Under Controlled Availability (Doc ID 2915145.1).

Procurement

Purchasing

Classify Master Item Purchases Based on the Most Current Purchasing Category Association

Classify your master item purchases based on the most current purchasing category association per the item definition. Such purchases will no longer be classified as per the purchasing category on the source agreement line, which could have been from an older item definition. This feature applies to purchase orders created through UI, FBDI, and REST resources.

These screen captures illustrate the feature:

Purchasing Category Reclassification on Product Information Item Definition

Blanket Purchase Agreement for Item with Old Purchasing Category

Create Purchase Order Lines Sourced from Blanket Purchase Agreements Using the Item's definition Assigned Purchasing Category

Steps to Enable

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

Tips And Considerations

• Automatic document sourcing of purchasing agreements for master items on purchase orders no longer considers purchasing category as a matching criteria.

• This feature adds up to the previously available process of retrieving the purchasing category from the product information item definition when processing requisitions not sourced from blanket purchase agreements into purchase order lines.

Access Requirements

• Users who are assigned this predefined job role are automatically able to access this feature:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned configured job roles that contains this privilege are able to access this feature:
  • Create Purchase Order (PO_CREATE_PURCHASE_ORDER_PRIV)

Correct the Supplier Item Number on Purchase Orders

Correct the supplier item number on purchase orders via the Edit Change Order page. During the Purchase Order Acknowledgment process, as a supplier, you can update supplier item numbers to make corrections on purchase order lines sourced from blanket purchase agreements. Using the feature, buyers can also update the supplier item number on behalf of their suppliers.

Irrespective of the Purchase Order Acknowledgment process, suppliers and buyers can create a purchase change order to update the supplier item on open purchase order lines sourced from blanket purchase agreements.

A new Supplier Item Modified approval attribute is now available at the document line dimension to create approval rules to route change orders for approval when a supplier item is updated.

The BI Publisher data model used by the purchase order approval notifications includes a new data element to check if a supplier item is modified through a change order. You can use this attribute to add conditional formatting to your purchase approval notification template to bring the change to the approvers' attention.

These screen captures illustrate the feature:

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

Supplier Item Correction for a Purchase Order Sourced from a Blanket Purchase Agreement on Open Status

Supplier Item Modified Approval Attribute

Supplier Item Modified Conditional Format Displays Warning Message on Approval Notification

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't update the supplier item attribute through the Electronic Purchase Order Acknowledgment Collaboration Message Framework inbound message. Supplier-initiated changes for supplier items are only supported through the Supplier Portal.

• You can update supplier items on Incomplete and Open purchase orders sourced from blanket purchase agreements using the REST Draft Purchase Orders 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 any of these predefined job roles can set up this feature:
  • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Users who are assigned a configured job role that contains this privilege can set up this feature:
  • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)

• Users who are assigned these predefined job roles are automatically able to 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 configured job roles that contain these privileges are able to 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)

Copy Requisition Header Attachments to the Purchase Order Header

Copy requisition header attachments to the purchase order header. Before this update, the application copied the requisition header attachments onto each purchase order line that fulfilled the requisition. This resulted in duplicate attachments for the purchase order. In this update, the application can now copy the requisition header attachments to the purchase order header.

These screen captures illustrate the feature:

Requisition with Header Attachment

Requisition Header Attachment Copied on to the Purchase Order Header

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

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 set up this feature:
  • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Users who are assigned a configured job role that contains this privilege can set up this feature:
  • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)

• Users who are assigned this predefined job role can access this feature in Purchasing:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned a configured job role that contains this privilege can access this feature in Purchasing:
  • Create Purchase Order from Requisitions (PO_CREATE_PURCHASE_ORDER_FROM_REQUISITIONS_PRIV)

Specify a Contract Purchase Agreement When Processing Requisition Lines Using the Document Builder

Specify a contract purchase agreement as the source document when processing requisition lines into a purchase order using the document builder. Before this update, you could specify only blanket purchase agreements as the source document in the document builder.

This screen capture illustrates the feature:

Display of Contract Purchase Agreement in the Source Agreement Search

Steps to Enable

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

Tips And Considerations

When you add multiple requisition lines to the document builder one at a time, the contract purchase agreement of the first requisition line replaces the contract purchase agreement on the subsequent lines in the resulting purchase order.

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

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

Apply Discount to All Purchase Order Lines

Apply discounts to all purchase order lines with a single action. For percentage-based discounts, the same discount percentage is applied to all the lines. For amount-based discounts, the discount amount gets prorated to all the lines.

Before this update, you could enter the discount on purchase order lines, one line at a time. With this update, you can apply the discount to all purchase order lines with a single action initiated from the purchase order header. You can also view the total discount applied to a purchase order by clicking the information icon.

These screen captures illustrate the feature:

Initiate the Apply Discount Action from the Purchase Order Header

Enter the Discount Percent or Discount Amount to Apply to the PO Lines

View Total Discount Applied on a Purchase Order

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 Capture Supplier Discounts on Purchase Order Lines feature. If you previously opted in to the Capture Supplier Discounts on Purchase Order Lines feature, then this feature is automatically enabled.

Tips And Considerations

• You can use the Apply Discount action only through the UI.

• You can apply the discount to a purchase order using the Apply Discount action only if the base price of all lines in the purchase order is allowed to be changed. Here are the conditions under which the base price can't be changed:
  • The purchase order line has a source agreement line that doesn't allow the price to be changed.
  • The purchase order line is received or billed, and the procurement business unit configuration doesn't allow manual price updates.
  • The purchase order line is created from a punchout marketplace or a smart form that doesn't allow the price to be changed.
  • The purchase order line is for model items or configuration components.

• The Apply Discount action applies discounts only on the purchase order lines that aren't canceled or finally closed.

• The Apply Discount action overrides any previously applied discounts on purchase order lines. After a discount is applied using the Apply Discount action, you can manually update the discount amount on one or more purchase order lines if required.

• For fixed-price service lines having multiple schedules and distributions, the discounted price wouldn't be updated on the schedules and distributions. As a workaround, you can use the Oracle Visual Builder Add-in for Excel with the backend Draft Purchase Order REST API to update the discounted price on the purchase order schedules and distributions.

• The Discount Amount field is available in the GET response of the Draft Purchase Order and Purchase Order REST resources. It indicates the total discount applied on a purchase order. POST and PATCH operations aren't supported.

• The Discount Amount field is also added to the BI Publisher purchase order data model. To communicate discount amounts to suppliers using PDF or electronic methods, modify the corresponding layout and mapping.

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

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

Search for Purchase Orders by Project Numbers and Task Numbers as a Buyer

Search for purchase orders and purchase order schedules using project attributes such as project number and task number.

Also, with this update, in addition to searching purchase orders and purchase order schedules using the project attributes, you can also filter requisition lines using project attributes on the View Requisition Lines page. Before this update, you could search requisitions by project number and task number only on the Process Requisitions page. 

You must enter the requisitioning BU before entering a value for project number. Similarly, you must enter a project number before entering a task number.

These screen captures illustrates the feature :

Project Attributes to Search Purchase Orders 

Project Attributes to Search Purchase Order Schedules 

Project Attributes to Search Requisitions

Steps to Enable

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

Tips And Considerations

• To add project number and task number, use the Advanced Search option on the Manage Orders and View Requisition Lines pages.

• You must enter the requisitioning BU before entering a value for project number. Similarly, you must enter a project number before entering a task number.

• You must implement the Project Costing functional area of the Project Financial Management offering, using the Setup and Maintenance work area. This enables the display of the project number and task number attributes.

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 are automatically able to access this feature:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Search Purchase Order (PO_SEARCH_PURCHASE_ORDER_PRIV)
  • View Requisition Details as Buyer (POR_VIEW_REQUISITION_DETAILS_AS_BUYER_PRIV)

Import Purchase Orders with U.S. Federal Attributes

Include U.S. Federal attributes when you import purchase orders using file-based data import. You can now capture the federal attributes that are required for the Government wide Treasury Account Symbol Adjusted Trial Balance System (GTAS) and Data Act Reporting while importing purchase orders.

You can use the Enable for DATA Act Reporting, DATA Act Award Type, Procurement Instrument Identifier (PIID), Parent Award, Federal Assistance Identification Number (FAIN), and Unique Record Identifier (URI) attributes for Data Act reporting. You can use the BETC, Trading Partner TAS, and Trading Partner BETC attributes for CTA Reclassification transactions. 

Here's the list of U.S. Federal attributes in the file-based data import template for PO Headers:

Attribute Name	Column Name
Enable for DATA Act reporting	GLOBAL_ATTRIBUTE1
DATA Act Award Type	GLOBAL_ATTRIBUTE2
Procurement Instrument Identifier (PIID)	GLOBAL_ATTRIBUTE3
Parent Award ID	GLOBAL_ATTRIBUTE4
Federal Assistance Identification Number (FAIN)	GLOBAL_ATTRIBUTE5
Unique Record Identifier (URI)	GLOBAL_ATTRIBUTE6

Here's the list of U.S. Federal attributes in the file-based data import template for PO Schedules:

Attribute Name	Column Name
Trading Partner TAS	GLOBAL_ATTRIBUTE_NUMBER1
Trading Partner BETC	GLOBAL_ATTRIBUTE1

Here's the list of U.S. Federal attributes in the file-based data import template for PO Distributions:

Attribute Name	Column Name
BETC	GLOBAL_ATTRIBUTE1

These screen captures illustrate the feature:

U.S. Federal Attributes in the FBDI Template for PO Header

U.S. Federal Attributes in the FBDI Template for PO Schedules

U.S. Federal Attributes in the FBDI Template for PO Distributions

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.

Tips And Considerations

These global descriptive flex field segments are currently reserved only for U.S. Federal attributes:

• For federal attributes on PO Header: GLOBAL_ATTRIBUTE1, GLOBAL_ATTRIBUTE2, GLOBAL_ATTRIBUTE3, GLOBAL_ATTRIBUTE4, GLOBAL_ATTRIBUTE5, GLOBAL_ATTRIBUTE6

• For federal attributes on PO Schedules: GLOBAL_ATTRIBUTE_NUMBER1, GLOBAL_ATTRIBUTE1

• For federal attributes on PO Distributions: GLOBAL_ATTRIBUTE1

Key Resources

• To know about how to import data purchase orders using the File-Based Data Import (FBDI) template, refer to the Purchase Orders Import topic in the Purchasing chapter of the Oracle Fusion Cloud Procurement: File-Based Data Import (FBDI) for Procurement guide.

• To know more about U.S. Federal Financials, refer to the Reporting Attributes topic.

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 are automatically able to access this feature:
  • Buyer (ORA_PO_BUYER_JOB)

• Users who are assigned configured job roles that contain this privilege are able to access this feature:
  • Import Purchase Order (PO_IMPORT_PURCHASE_ORDER_PRIV)

Create Purchase Order Lines with Negative Amounts

Create purchase order lines with negative amounts to record credits to the ordered amount that you have negotiated with your supplier.  For example, you can use a negative amount line to represent credit for an equipment trade in. When you receive an invoice with a negative amount line, you can match the invoice line to the negative amount order line.

This screen capture illustrates the creation of a negative amount line in the application: 

Credit Line with Negative Amount

You can see how the Ordered amount breaks down into the Ordered Before Adjustments and Credit amounts at the order header. This screen capture illustrates the popup with the amount details.

Ordered Before Adjustments and Credit Amounts

The Ordered Before Adjustments and Credit fields are also available in the Purchase Order REST resource, Purchase Order data model, and Purchase Order Notification data model.

The Purchase Order Credit Amount metric is available in the Purchase Order Distribution folder of the Purchasing subject area. The Credit Amount and Credit Amount in Functional Currency metrics are available in the Purchase Order Measures folder of the Procure To Pay subject area. This screenshot illustrates the Purchase Order Credit Amount metric in the Purchasing subject area.

Purchase Order Credit Amount Metric

Watch a Demo.

Steps to Enable

To create negative amount purchase order lines, use a line type that has the Credit setting enabled and enable credit line types on a new document style.

1. Use the provided Credit line type, or create a new line type that has Credit setting enabled. Order lines created with credit line types can have a zero or negative amount.

Credit Line Type and Credit Setting

2. Create a new document style and enable the Credit Line Types Enabled setting. When you create purchase orders with this document style, you will be able to create lines with credit line types.

Credit Line Types Enabled on Manage Document Styles

Tips And Considerations

• Credit line types are only available for purchase order lines. You can't create requisitions, negotiations, or purchase agreements with credit line types.

• Credit line types are set to have a Purchase Basis of Amount, Product Type of Services, Match Approval Level of 2 Way, Invoice Match Option of Order, and Receipt Close Tolerance Percent of 100.

• Document styles with credit line types enabled can't support consignment terms, configuration ordering, outside processing, or complex work. 

• Purchase order lines with a credit line type (credit lines) can have a zero or negative amount.

• As credit line types are amount based, you can't enter an inventory item or quantity for credit lines.

• You can create and update credit lines through the application, or with FBDI or REST resources.

• You can't associate an agreement with a purchase order credit line.

• As the receipt close tolerance percent is set to 100, credit lines go into Closed for Receiving status after implementation.

• You can't create a receipt for a credit line. Receiving-related fields such as Over-Receipt Action are disabled. Accrue on Receipt is set to No and disabled. 

• You can create rules in the Transaction Account Builder for credit line types by using the new Line Type source.

• You can’t create a credit line if the requisitioning business unit is located in Brazil and has fiscal document processing enabled.

• You can't create a credit line if financial orchestration determines an agreement for the line.

Key Resources

• Watch Create and Invoice Purchase Order Lines with Negative Amounts Readiness Training

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 set up this feature:
  • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Users who are assigned a configured job role that contains this privilege can set up this feature:
  • Manage Procurement Configuration (PO_MANAGE_PROCUREMENT_CONFIGURATION_PRIV)

• Users who are assigned this predefined job role can access this feature in Purchasing:
  • Buyer (ORA_PO_BUYER_JOB)

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

View Negotiation Details for Purchase Orders and Purchase Agreements Created as Negotiation Award Outcomes

View the negotiation number for purchase orders and agreements created as negotiation award outcomes as either the buyer or the supplier. Use the negotiation number link to view negotiation details.

This screen capture illustrates the feature for a purchase order: 

View Negotiation on Purchase Order Header

Steps to Enable

To use this feature, use the page composer to expose the Negotiation field in the View and Edit Purchasing Document pages. Follow these steps.

1. Create and activate a sandbox with Page Composer
2. Navigate to the page on which you want to display the negotiation field and query a purchasing document that was created as a negotiation award outcome
3. Select Sandbox Mode: Edit on the top right corner
4. Select the Structure tab
5. Click on any field on the document header
6. On the Structure tree, click on Negotiation and select Edit
7. On the Component Properties, check Show Component and select OK
8. Confirm the Negotiation number is displayed
9. Exit and deploy the sandbox

These screen captures illustrate steps 6 and 7:

Select field from structure

Edit component properties

Tips And Considerations

Negotiation details you can view vary depending on your role as buyer, category manager, or supplier.

Key Resources

• Refer to the Page Content and Layout section of the Configuring and Extending Applications Guide for details on how to use Page Composer. 

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 these predefined job role can access this feature in Purchasing:
  • Buyer (ORA_PO_BUYER_JOB)
  • Category Manager (ORA_PON_CATEGORY_MANAGER_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 configured job roles that contain these privileges are able to access this feature:
  • Create Purchase Order (PO_CREATE_PURCHASE_ORDER_PRIV)
  • Change Purchase Order (PO_CHANGE_PURCHASE_ORDER_PRIV)
  • Create Purchase Agreement (PO_CREATE_PURCHASE_AGREEMENT_PRIV)
  • Change Purchase Agreement (PO_CHANGE_PURCHASE_AGREEMENT_PRIV)

Project Cost Distribution Using Award Funding Patterns

Define funding patterns to distribute project costs to awards and funding source combinations. Specify an expenditure item date range and task level to apply distribution rules that automatically split sponsored project costs. Automating the distribution ensures charging accuracy and removes the need to manually enter the award charging instructions. Grant administrators manage the funding patterns to ensure proper cost distribution throughout the duration of the sponsored project.

This new functionality, commonly referred to as “Award Distribution”, is set up and managed in the Grant Management offering and enables more efficient project cost capture across the procure to pay lifecycle and during import of costs from third party systems.

Funding patterns are created and maintained by Grant Administrators and are the core object of the functionality. The funding patterns are created once the project is funded by one or more award and funding sources.

Funding Pattern Search

Funding Pattern Maintenance

Project costs captured on requisitions, purchase orders, and accounts payable invoices can be distributed using applicable funding patterns by leaving the Contract Number and Funding Source fields blank.

Requisition with Blank Contract and Funding Source

When ready, you can use the new Distribute Project Costs action to distribute the costs entered using the funding pattern sets and rules to ensure accurate charging.

Requisition Distributed by Funding Pattern

Grant Accountants and Administrators can resolve errors by viewing failed distributions in the Project Cost Distribution Results page in real time with procurement staff, or simulating the same action in the Manage Project Costs work area, with the new Test Award Distribution functionality.  The cause of the error can be viewed and resolved accordingly. In the Manage Project Costs work area, the Test Award Distribution function will also display successful distributions to simulate the results of error resolution. This is only a simulation. The Import Project Costs action continues to be the function that creates costs on a project.

Manage Project Costs Simulation

If you chose to view the results, the list of costs, funding patterns, distribution sets, and rules used will be presented with a simulated successful or failed distribution.

View Project Cost Distribution Results

Grant accountants can also manage third party cost integrations that will leverage the funding patterns on costs imported with blank contract / award and funding patterns. If active funding patterns exist, the costs will be distributed using the associated sets and rules and any errors can be managed and tested as illustrated above.

Manage Third Party Cost import

Watch a demo.

The business benefit of this new feature is that it reduces the complexity associated with manually splitting distributions at cost capture and increases the accuracy of meeting the obligations associated with awards from both external and internal funding sources.

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: Grants Management  No Longer Optional From: Update 23C

You will need to opt-in to this feature in the Setup and Maintenance work area. The feature will always be enabled from update 23C onwards.

• The feature is at the highest level of Feature Opt-in for the Grants Management Offering

• Once you enable this feature, the following activities are required to enable the functionality:
  • Create Funding Patterns
    • Use the newly created awardFundingPatterns REST object to automate the creation and update of funding patterns
  • Set Funding Patterns to Active to enable:
    • Ability to leave Contract / Award and Funding Source values blank on sponsored projects in procurement and accounts payable distributions
    • Action to Test Award Distribution in Manage Project Costs work area

Tips And Considerations

You can use funding patterns to distribute project costs only if the funding patterns are in Active status.

Key Resources

• Watch Project Cost Distribution Using Award Funding Patterns Readiness Training
• Related help:
  • Using Grants Management

• Based on Idea 517345 from the Project Management Idea Labs on Oracle Cloud Customer Connect

Access Requirements

To use this feature, you need these privileges and roles:

• Privilege Name and Code:
  • Manage Award Funding Patterns (GMS_MANAGE_AWARD_FUNDING_PATTERNS_PRIV)
    • Allows users to manage award funding patterns assigned to a sponsored project.
    • Rolled up to Duty Role - Award Management (ORA_GMS_AWARD_MANAGEMENT_DUTY)
  • Distribute Award Project Costs and Quantities (PJC_DISTRIBUTE_AWARD_PROJECT_COSTS_AND_QUANTITIES_PRIV)
    • Allows users to initiate the Award Distribution process, which matches the costs and quantities provided to available award funding patterns, distributes costs as appropriate, and displays the results.
    • Rolled up to Job Roles:
      • Grant Management
        • Grants Accountant (ORA_PJF_GRANTS_ACCOUNTANT_JOB)
      • Procurement
        • Buyer (ORA_PO_BUYER_JOB)
        • Purchase Order Authoring (ORA_PO_SPO_CREATION_DUTY)
        • Category Manager (ORA_PON_CATEGORY_MANAGER_JOB)
        • Procurement Contract Administrator (ORA_PO_PROCUREMENT_CONTRACT_ADMIN_JOB)
        • Advanced Procurement Requester (ORA_POR_ADVANCED_PROCUREMENT_REQUESTER_ABSTRACT)
        • Procurement Preparer (ORA_POR_PROCUREMENT_PREPARER_ABSTRACT)
        • Procurement Requester (ORA_POR_PROCUREMENT_REQUESTER_ABSTRACT )
        • Contingent Worker (ORA_PER_CONTINGENT_WORKER_ABSTRACT)
        • Employee (ORA_PER_EMPLOYEE_ABSTRACT)
        • Requisition Self Service User (ORA_POR_REQUISITION_SELF_SERVICE_USER_DUTY)

Resend Approval Email Notifications

You can now resend approval email notifications for in-progress transactions. You can select one or more transactions in the Transaction Console page or drill-down to the Transaction details page for a transaction and use Resend Email Notification in the Actions menu to notify assignees.

Resend Email Notification in Actions Menu on the Details Page

Confirmation Message Displays for Selected Transactions

When you click Resend Email Notification, if there are multiple tasks and assignees in the transaction then those tasks and assignees display in a dialog box. You can select the assignees to whom you want to send the notification. By default, all the assignees are selected in the dialog box.

After the notification is sent, the appropriate status displays in the Status dialog box.

Status Dialog Box for Submitted Process

This feature provides the ability to resend email notifications in the event of any email deletions or loss of email data.

Steps to Enable

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

Tips And Considerations

• This action is available only to administrators and for in-progress assigned transactions.
• If there’s a change in the email ID after the first notification then on the resend the new email ID is automatically used.

Key Resources

• Manage Workflow Transactions
• Actions for Managing Transactions

Access Requirements

You need to grant administrators the Perform HCM Approval Transaction Actions (PER_PERFORM_APPROVAL_TRANSACTION_ACTIONS_PRIV) privilege.

Archive Reminder in Transaction Console

The Transaction Console work area now displays a yellow banner that reminds users to archive completed transactions. The banner displays when the archive process hasn't been run in the past 3 months.

You can use Archive Now to immediately archive the transactions. When you click Archive Now, a confirmation displays. If you click Dismiss, the notification is snoozed for 24 hours, after which the message displays again.

This feature improves the performance of the Transaction Console work area.

Steps to Enable

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

Key Resources

• Archive and Purge Transactions

Access Requirements

To access the Transaction Console work area, users need the Perform HCM Approval Transaction Actions (PER_PERFORM_APPROVAL_TRANSACTION_ACTIONS_PRIV) privilege.

Diagnostic Log Availability and Attachments in Transaction Console

The Transaction Console work area now lets you do the following:

• Download the diagnostic log for healthy pending transactions.
• View details of all the attachments added at any stage of the transaction in the diagnostic log.

Select an in-progress transaction, open the transaction details page, and use the Download link. This downloads the details of the transaction in .html format.

Any attachments that you add as part of the transaction are listed in the Attachments section in the .html file.

With this feature, you now have the ability to review the diagnostic log for more transactions, with more information in the log.

Steps to Enable

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

Key Resources

• Manage Workflow Transactions

Access Requirements

To access the Transaction Console work area, users need the Perform HCM Approval Transaction Actions (PER_PERFORM_APPROVAL_TRANSACTION_ACTIONS_PRIV) privilege.

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.

Prevent Buyers from Releasing Holds Initiated by External Applications

Before this update, as a buyer, you could release a purchase order hold and freeze initiated by Oracle Order Management, which could result in stuck sales orders. After this update, you can't release the hold and unfreeze such POs unless you have the Release Purchase Order Hold and Freeze Initiated by Requester privilege.

Oracle reference: 33493407

Delete Purchase Orders in Bulk Using the Draft Purchase Order REST Resource

Before this update, you could only delete one purchase order at a time using REST resources. After this update, you can delete multiple purchase orders in a single request.

Oracle reference: 34433319

Truncate Very Long Supplier Names

Before this update, the application didn't truncate long supplier names, which could sometimes affect the display of the user interface. After this update, the application truncates supplier names to 50 characters. You can hover over the field to see the full supplier name.

Oracle reference: 34617996

Steps to Enable

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

External Purchase Prices

Remove Requisitioning Business Units from Mappings

Delete requisitioning business units (BUs) mapped to a source organization from an existing requisitioning BU mapping. You can delete those requisitioning BUs where there are no purchase agreements created for the external purchase prices tied to those requisitioning BUs.

Once you delete a requisitioning BU from the mapping, the list of requisitioning BUs is automatically updated in the existing external purchase prices. Any approval rules defined using the requisitioning BU group name are also automatically updated.

Here are the requirements for deleting requisitioning BUs from a mapping: 

• A source organization must have more than one requisitioning BU mapped to it. If there’s only one requisitioning BU mapped to a source organization, you can’t delete that requisitioning BU from the mapping.  

• You can delete those requisitioning BUs where there are no purchase agreements created for the external purchase prices tied to those requisitioning BUs.

However, if purchase agreements exist for the external purchase prices that are tied to the requisitioning BUs, follow these steps to delete the requisitioning BUs:

1. Identify the external purchase price lines that are tied to the requisitioning BUs that you want to delete from the mapping and exclude them from purchasing. On the External Purchase Prices page, select those lines and click Exclude from Selection.

2. Submit the Import Purchase Agreements from External Purchase Prices scheduled process. This process will end date the excluded external purchase price lines in the purchase agreements. 

3. On the Mapping Details panel, delete the requisitioning BUs from the mapping.

4. Submit the Import Purchase Agreements from External Purchase Prices scheduled process again to create new purchase agreements with the revised list of requisitioning BUs for these external purchase prices.

5. You can cancel or end date the old purchase agreements.

Requisitioning BU Mapping

With this feature, you can delete requisitioning BUs from existing mappings. You no longer need to delete the entire mapping to remove requisitioning BUs. You also have the flexibility to work with mappings for which external purchase prices have already been created.

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.

Bypass Approval for Agreements Created from External Purchase Prices

Use the External Purchase Prices Options lookup to configure new options for purchase agreements that are created from external purchase prices. Choose to bypass approval, or to enable purchase agreements to allow ordering from unassigned supplier sites.

You now have the option to bypass the approval workflow for purchase agreements created from external purchase prices. This option is set in the new lookup code ORA_SCH_EPP_BPA_APRVL_OPTION in the External Purchase Prices Options lookup. It takes the default meaning of BYPASS, which automatically creates the purchase agreements and change orders in approved status without routing them through the approval workflow. Set this code to SUBMIT in case you want the purchase agreements and change orders to go through the approval workflow process.

The External Purchase Prices Options lookup also provides you with the new lookup code ORA_SCH_EPP_BPA_UNASIGND_SITE. The default value of this code is N. When you set this option to Y, the purchase agreements created from external purchase prices enable their referring POs to order from unassigned supplier sites.

External Purchase Prices Lookups

Bypassing approval workflows ensure that you can create and update purchase agreements faster. Now you can also enable purchase agreements to allow ordering from supplier sites other than those listed as purchasing sites in the business unit assignments.

Steps to Enable

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

Access Requirements

Users who are assigned Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB) or Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB) job roles will be able to update the external purchase prices lookups.

Supplier Model

Create Supplier Sites with Longer Names

Supplier sites sometimes need lengthy, descriptive naming conventions to meet supplier management requirements. With only 15 characters available for the supplier site name, meeting this requirement can be difficult. Create supplier sites with a name of up to 240 characters to better identify them; providing flexibility to satisfy the requirements of any naming convention.

Create Supplier Site with Longer Name

View Supplier Site with Longer Name

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

Tips And Considerations

• This feature is automatically enabled for new customers.

• For customers using Oracle Fusion Cloud Procurement prior to update 23A, review the impact of using a longer supplier site name in your business processes before enabling the feature, particularly with respect to supplier data integrations. For example, if you utilize Oracle Business Intelligence Cloud Connector (BICC) to extract supplier data for integration purposes, we suggest to increase the supplier site column size to match in downstream applications before turning on this feature.  It's not recommended to disable the feature once it's enabled.

Access Requirements

• Users who are assigned any of these predefined job roles can access this feature:
  • Supplier Manager (ORA_POZ_SUPPLIER_MANAGER_ABSTRACT)
  • Supplier Administrator (ORA_POZ_SUPPLIER_ADMINISTRATOR_ABSTRACT)

• Users who are assigned a configured job role that contains these privileges can access this feature:
  • Maintain Supplier Site (POZ_MAINTAIN_SUPPLIER_SITES_PRIV)
  • View Supplier Site (POZ_VIEW_SUPPLIER_SITES_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.

Replace Advanced Search Operators With Keywords in Supplier LOV

To address performance issues in the Supplier LOV search on pages like Merge Suppliers and Create Noncatalog Request across Oracle Fusion Cloud Procurement, advanced search operators such as Contains are removed. You can now search suppliers using Keywords in the Supplier LOV instead.

Oracle reference: 34270276

Steps to Enable

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

Sourcing

Extend a Closed Negotiation

You can now extend a closed negotiation to give suppliers more time to respond. When a closed negotiation is extended, all the participating suppliers are notified of the new deadline so that they can submit new responses or revise their previous responses. Suppliers that already submitted their final responses don't need to resubmit.

Extend a Closed Negotiation

Negotiation is Active After Extension

With this feature, category managers have more control and flexibility over the timeline for accepting supplier responses. In situations where suppliers missed the response submission deadline, or if there weren't enough supplier responses, category managers can easily extend the negotiation to increase the opportunity for receiving additional responses.

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 extend a negotiation that's in any of these statuses:
  • Closed
  • Closed (Locked)
  • Award in progress (for blind or open response visibility)

• You can't extend a sealed negotiation once it's unlocked.

• You can't extend a closed auction in the following scenarios:
  • If staggered closing is enabled.
  • If auto extend is triggered for 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 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:
  • Extend Supplier Negotiation (PON_EXTEND_SUPPLIER_NEGOTIATION_PRIV) 

Control Defaulting of Supplier Responses to Predefined Questions

In negotiations, you can add predefined questions from the questions library. When a supplier responds to these predefined questions in a negotiation, the responses get saved in the response repository. When supplier bidder creates a response, these responses to predefined questions are automatically defaulted. With this feature you can control the defaulting of the supplier responses from the response repository for the Procurement BU.

With this control you can decide if the suppliers must always provide a fresh response to the predefined questions in a negotiation.

Steps to Enable

Offering: Procurement

To enable this feature, in the Configure Procurement Business Function page, select  the Automatically populate responses to predefined questions check box.

Procurement BU Control for Defaulting Supplier Responses in Configure Business Function Setup Page

Tips And Considerations

• You can set up predefined questions using Manage Supplier Questions setup task.

• Supplier Qualification must be enabled to save supplier responses in the response repository, and to autopopulate the response values in new supplier responses. After award, supplier responses are automatically saved in the response repository, even if you choose to not autopopulate responses to predefined questions.

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) to access Setup and Maintenance to enable the feature.
  • 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)

Invite All Contacts to a Large Negotiation

With this feature, in large negotiations, you can now notify all the contacts for an invited supplier. When you publish a large negotiation, the background process will generate the negotiation documents and response lines (.CSV) file, which will now be sent to all contacts of the supplier.

Notify All Contacts While Inviting Suppliers

You are no longer required to select a specific contact to invite for a large negotiation, if you choose to notify all contacts.

Steps to Enable

Enable by setting a control on the negotiation style:

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

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

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

3. In the Controls section, under the Overview group, select the Large negotiation check box and under the Suppliers group, select the Send invitation to all contacts check box.

Negotiation Style Controls

Key Resources

• Review update 22D readiness training for the Oracle Sourcing Cloud feature Manage Large Negotiations for more details.
• Review update 22D readiness training for the Oracle Sourcing Cloud feature Invite All Supplier Contacts 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)

Use Parameters to Validate Negotiation Descriptive Flexfield Values

In negotiations, descriptive flexfields (DFFs) are supported for you to capture information specific to your business on the negotiation header (internal, and visible to suppliers), negotiation line (internal), and the negotiation abstract. In this update, parameters are available to derive and validate the values in the DFFs when creating a negotiation. You can do this using Page Composer.

DFFs can be configured using these negotiation attributes:

• Sourcing Negotiation Abstracts
  • AuctionHeaderId

• Sourcing Negotiation Header
  • NegotiationType
  • DocumentNumber (Negotiation Number)
  • AuctionHeaderId
  • ProcurementBUId
  • RequisitionBUId
  • BuyerId
  • DocumentStyleId

• Sourcing Negotiation Lines
  • CategoryId
  • ItemId
  • LineTypeId
  • ProcurementBUId
  • RequisitioningBUId
  • LineDescription
  • AuctionHeaderId
  • LineNumber

Defaulting DFF context or segment value, or limiting list of values based on negotiation header and line attributes can help reduce the data entry time for negotiations, and increase the accuracy of information captured in negotiation flexfields.

Steps to Enable

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

Tips And Considerations

To use the negotiation parameters to configure the flexfields you can follow these steps.

1. In the Setup and Maintenance work area, go to the Manage Sourcing Descriptive Flexfields task to setup negotiation DFFs and deploy them.    

• Offering: Procurement     
• Functional Area: Sourcing       
• Task: Manage Sourcing Descriptive Flexfields

2. The configurable parameters are supported for the following negotiation DFF entities:

• Supplier Negotiation Abstracts (PON_NEGOTIATION_ABSTRACTS)
• Supplier Negotiation Headers (PON_AUCTION_HEADERS)
• Supplier Negotiation Lines (PON_AUCTION_ITEM_PRICES)

To configure derivation of DFF values, you can use the Expression Builder function to create value sets and add a query using the new negotiation fields. Here is an example:

ITEM_DESCRIPTION=:{PARAMETER.LineDescription} and PRC_BU_ID=:{PARAMETER.ProcurmentBUId}

Then save changes and deploy the flexfields.

Create a Value Set Using Expression Builder

Key Resources

• Overview of Descriptive Flexfields
• Using and setting up Descriptive Flexfields

Access Requirements

• To use this feature, users who are assigned predefined job role are automatically able to access this feature:
  • Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)

Selected Sourcing Bug Fixes in This Update

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

Large Negotiations Included in Landing Page Metrics

Infolets on the Negotiations landing page are updated to include information for large negotiations:

• My Performance
• Completed Awards
• Closing Next

Oracle references: 34412369, 34422508, & 34406833

Steps to Enable

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

Spend Classification

Add or Modify Categories in Existing Taxonomies

Add new categories to an existing taxonomy or edit categories in a taxonomy by changing category names at any level. You can now use the Upload Taxonomy action to revise an active taxonomy, modify existing category names, or add new categories to extend the taxonomy. With this capability, you no longer need to delete the taxonomy you’d like to modify, upload a revised version, and then rebuild any impacted knowledge bases that were using the previous version of the taxonomy.

Here’s a sample file used for uploading taxonomies. In this example, we’ll add new categories and modify the names of categories in the highlighted rows.

Taxonomy Upload File

1. On the Configuration page go to the Taxonomies tab. In the menu for a taxonomy, click Download Categories.

2. In the downloaded file, make these changes:
   1. Add new categories for Services.
   2. Change the name of the leaf node Food to Food & Beverages.
   3. Change the name of the category Officeday to Administration. Check the spreadsheet for the category name Officeday at the same level and ensure that you change all instances of Officeday to Administration.

NOTE: You can change the name of the leaf node of any category without impacting other categories. But if you change the parent node of a category name, you must change all the instances of that category name.

Updated Taxonomy Upload File

3. Delete all the rows in which you haven’t made any changes and save the file.

Modified Records Only

4. In the Upload Categories dialog box, select the updated file and click Upload.

5. Click Classify to start the classification process. If you’ve added new categories, you should provide training for those categories, and then improve the knowledge base.

If you delete the all the categories in a taxonomy, you must improve all the associated knowledge bases. However, with this enhancement you can update and add categories without deleting the existing categories and hence eliminating the need to improve the knowledge bases. You’ll only need to provide additional training for new categories if you want to include them for prediction by the Spend Classification engine.

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)

Define Rules Using Additional Classification Attributes

Improve results by allowing classification process business rules to be defined using any of up to 20 additional attributes that can be included into each data set. This enhancement improves accuracy of the spend classification results by enabling key information stored in extended attributes to be used to tune the classification process. Furthermore, you can use the improved business rules with new comparison operators to check for blank values.

You can now define rules with more flexibility to normalize, exclude, and enrich data during the classification process. Use the extended additional attributes for creating rules that work for a specific purpose. For example, let’s say you mapped Classification Attribute 1 to Manufacturer in the Attributes tab of configuration. You can now setup rules that use manufacturer names to perform specific processing for subsets of the transactions in the data set.

Rules

Additionally, you can define rules that exclude transactions from a classification based on whether the value of an item is blank.

With rules, you can bring in automation and accuracy to category predictions based on the logic available in the unclassified data. Flexible rules help reduce the review time spent on 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)

Channel Revenue Management

Supplier Channel Management

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

Define Ship and Debit Program Eligibility based on Warehouse and Ship-to Address

Create ship and debit program qualifier rules based on ship-from warehouse and ship-to customer. For example, create a ship and debit program for a warehouse to move excess inventory, or manage freight costs specific to that location. Use a ship-to customer qualifier to restrict program eligibility to a specific customer location.

Supplier Ship and Debit programs can now include qualifier rules based on ship-from warehouses or ship-to customers.

Steps to Enable

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

Offering: Order Management

1. In the Order Management offering, enable the Channel Revenue Management functional area. Then opt in to the Supplier Channel Management feature.

Key Resources

• Watch Additional Qualifiers for the Ship and Debit Readiness Training
• Watch Supplier Channel Management Continuous Improvement Readiness Training.
• Oracle SCM Cloud: Using Oracle Channel Revenue Management Cloud, available on the Oracle Help Center.
• Oracle SCM Cloud: Implementing Oracle Channel Revenue Management Cloud, available on the Oracle Help Center.
• Oracle SCM Cloud: REST API for Oracle SCM Cloud, available on the Oracle Help Center.

Access Requirements

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

• Users who are assigned this predefined job role are automatically able to access this feature:
  • Supplier Channel Manager (ORA_CJM_SUPPLIER_CHANNEL_MANAGER_JOB)
  • Supplier Sales Representative (ORA_POS_SUPPLIER_SALES_REPRESENTATIVE_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Manage Supplier Claims (CJM_MANAGE_SUPPLIER_PROGRAMS_PRIV)
  • Manage Supplier Programs in Supplier Portal (CJM_MANAGE_SUPPLIER_PROGRAMS_IN_PORTAL_PRIV)