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
15 NOV 2023	Supply Chain Orchestration	Use Your Own Group Codes to Manage Purchase Requests in Buyer Planning	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.

Pre-Update and Post-Update Tasks

Depending on the features you're using in your Cloud applications, you may be required to perform certain steps immediately before or after your quarterly update. For details of these pre-update and post-update steps and the product areas that are affected, refer to Oracle Fusion Cloud SCM: Performing Your Quarterly Update (doc ID 2337485.1) on My Oracle Support.

Optional Uptake of New Features (Opt In)

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

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

Here’s how you opt in to new features:

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

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

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

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

Opt In Expiration

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

Feature Summary

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

• See Use REST API to Manage Supply Chain Orchestration and Using Supply Chain Orchestration on 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 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 Management  No 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

• See Using Supply Chain Orchestration and Supply Chain Orchestration on 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 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

• See Using Supply Chain Orchestration and Supply Chain Orchestration on 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 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 Management  No 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.

Quality Management

Quality Inspection Management

Sign for Quality Inspection Management E-Records Using Single Sign-on Through an External Authentication System

Companies that require electronic record keeping with nonbiometric electronic signatures are increasingly seeking ways to simplify their identity management approach and streamline the user login experience. They want to use a single set of login credentials to authenticate a user when signing electronic records and accessing any of their application systems. With this update, you can now configure single sign-on credentials for an e-signature user using Oracle Access Management as the identity provider to authenticate against an external authentication system instead of the Oracle WebLogic identity provider.

Single sign-on credentials can apply to the e-signature users for the Inspection Disposition e-signature and e-record transaction using the inline approval process.

Using Oracle Access Management as the identity provider for external authentication, you can synchronize the Oracle e-signature process with other existing application logins based on single sign-on credentials.

Steps to Enable

If you want to opt-in and use the Sign for Quality Inspection Management E-Records Using Single Sign-on Through an External Authentication System feature, you must:

1. Opt-in to its parent feature, Capture Electronic Records and Electronic Signatures for Supply Chain Management Transactions. If you’ve already opted into this parent feature, you don't need to opt in again.

2. Opt in to the feature named Reauthenticate E-Signature Users Using Oracle Access Manager.

Refer to the documentation on how to configure and manage Identity Federation with Oracle Access Management.

Tips And Considerations

• If you don't use an external authentication system, then there's no configuration change required.
• After the opt-in for this feature expires, you will see the login authentication page using Oracle Access Management instead of Business Process Management.

Access Requirements

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

• Edit Inspection Results (QA_EDIT_INSPECTION_RESULTS)

This privilege was available prior to this update.

Manufacturing

Manufacturing

Remove a Component During Discrete Manufacturing Work Execution

It's increasingly common for manufacturers of complex, discrete products to take a standard product, and customize it to to meet a customer order. This process could involve outsourced parts that later need to be removed or replaced as part of the customization. The part in question may be a component from a subassembly, which is either a purchased item or manufactured in-house.

Prior to this update, only rework and transform work orders allow a negative material quantity and issue transaction as the means of removing and replacing material on a product. Although rework and transform work orders can be collected and planned, they require that the product already exists in inventory to start the rework and transform process.

With this update, while executing standard or nonstandard discrete manufacturing work orders, you can now remove a component from an in-house or outsourced subassembly that wasn't previously issued to the work order using an ad hoc negative material issue transaction. You can use the negative material return transaction to reverse or correct the negative material issue transaction. This capability would be available in the user interface (UI), File-Based Data Import (FBDI) and ADFdi data import correction, and REST web services.

Negative Component Issue for a Work Order Operation

Negative material transactions gives the flexibility to remove a component not originally issued in a work order during normal production, with the additional benefit of using work order costing with a standard work order, maintaining more accurate inventory, and better management of work order execution in the manufacturing floor.

Steps to Enable

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

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

Tips And Considerations

Negative material quantities can be reported only as material transactions and cannot be specified in the work order or work definition. Following are the considerations while using this feature for lot controlled and serial controlled components:

• While removing a serial controlled component, the serial number must NOT be blank during the reporting of material issue transactions

• For serial controlled items where serial generation is the At receipt serial status, it must be defined but not used while reporting the material issue transactions

• Lot controlled components can be negative issued to an existing active lot of the item in inventory

Key Resources

• Refer to Remove a Component During Discrete Manufacturing Work Execution Release training in the Oracle Help Center

Access Requirements

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

• Report Material Transactions (WIP_REPORT_MATERIAL_TRANSACTIONS_PRIV)

This privilege was available prior to this update.

Mass Close Work Orders by Specifying a Closed Date Using the Scheduled Process

It's a common practice for manufacturing companies to close specific work orders for costing purposes soon after production has completed. However, the scheduled process for closing work orders assumes that the closed date is based on the current system date and time. With this update, you can specify a closed date when submitting the Close Work Orders program. You can either use the default system date and time or adjust the closed date in the past to align the costing period with the timespan between the work orders' release and production transactions.

Scheduled Process Parameters for Mass Close Work Orders

The ability to mass close work orders based on a specified closed date enables more accurate cost accounting closer to the actual completion of production.

Steps to Enable

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

Tips And Considerations

• You can also specify the closed date for a work order when updating the work order status to Closed through the Manage Work Orders page, Edit Work Order page, REST service, or File-based Data Import (FBDI).

• It's recommended that you submit the program manually with a Closed Date. If the closed date is not provided, scheduling this program on a periodic basis will use the default system date and time. If the date is provided, it would be automatically incremented based on the schedule.

Access Requirements

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

• Close Work Orders (WIP_CLOSE_WORK_ORDERS_PRIV)

This privilege was available prior to this update.

Sign for Manufacturing E-Records Using Single Sign-on Through an External Authentication System

Companies that require electronic record keeping with nonbiometric electronic signatures are increasingly seeking ways to simplify their identity management approach and streamline the user login experience. They want to use a single set of login credentials to authenticate a user when signing electronic records and accessing any of their application systems. With this update, you can now configure single sign-on credentials for an e-signature user using Oracle Access Management as the identity provider to authenticate against an external authentication system instead of the Oracle WebLogic identity provider.

Single sign-on credentials can apply to the e-signature users for the following Oracle Manufacturing e-signature and e-record transactions, covering both inline and deferred approval processes:

• Manufacturing Work Definition Management
• Manufacturing Standard Operation Management
• Manufacturing Work Order Approval
• Work Order Material Transaction
• Work Order Operation Transaction
• Work Order Output Transaction
• Orderless Transaction
• Production Exception Closure

The following is a screenshot of the Oracle Access Management login page for user authentication using single sign-on.

Oracle Access Management Login Page for User Authentication Using Single Sign-on

Using Oracle Access Management as the identity provider for external authentication, you can synchronize the Oracle e-signature process with other existing application logins based on single sign-on credentials.

Steps to Enable

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

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

If you want to opt-in and use the Sign for Manufacturing E-Records Using Single Sign-on Through an External Authentication System feature, you must:

1. Opt-in to its parent feature, Capture Electronic Records and Electronic Signatures for Supply Chain Management Transactions. If you’ve already opted into this parent feature, you don't need to opt in again.

2. Opt in to the feature named Reauthenticate E-Signature Users Using Oracle Access Manager.

Refer to the documentation on how to configure and manage Identity Federation with Oracle Access Management: https://docs.oracle.com/en/middleware/idm/access-manager/12.2.1.3/aiaag/introducing-identity-federation-oracle-access-management.html.

Tips And Considerations

• If you don't use an external authentication system, then there's no configuration change required.

• After the opt in for this feature expires, you will see the login authentication page using Oracle Access Management instead of Business Process Management.

Key Resources

• Refer to Implementing E-Signatures and E-Records and Using E-Signatures and E-Records in the Oracle Help Center.

Access Requirements

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

• Add Electronic Signatures (EDR_ADD_ESIGNATURES_TRANSACTIONS_PRIV)

This privilege was available prior to this update.

Improved Layout of the Manage Inventory Organization Parameters Page

On the Manage Inventory Organization Parameters Page, in the General Information area, some of the inventory organization fields in the Additional Usages section have been reordered. The Organization represents a contract manufacturer check box and the Supplier and Supplier Site fields have been moved above the Integrated System Type field. This change to the field order keeps related attributes adjacent to one another and in a more meaningful order.

Reordered Fields in the Additional Usages Section

Steps to Enable

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

IMPORTANT Actions and Considerations

Replaced and Removed Features

From time to time, Oracle replaces existing Cloud service features with new features, or removes existing features. Replaced features may be put on a path to removal from the Oracle Cloud Applications. As a best practice, you should use the newer version of a replaced feature as soon as the newer version is available.

This section identifies the features in this Cloud service that have been replaced or will be removed.

Module	Removed Feature	Target Removal	Replacement Feature	Replaced In	Additional Information
Manufacturing	Oracle Manufacturing Cloud Supervisor Mobile Application	TBD	See additional information	NA	As of July 31, 2023, the Oracle Manufacturing Cloud Supervisor Mobile Application will no longer be enhanced or updated, nor will technical support be provided for issues. As of October 31, 2023, the mobile application will no longer be available for download. If you're using the mobile app, please evaluate using mobile solutions provided by Oracle Partners in the Oracle Cloud Marketplace. You should move from the Oracle Manufacturing Cloud Supervisor Mobile Application to an alternative solution as soon as possible.