What's New

Update 22D

Revision History

This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:

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 SCM Cloud: 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 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

Inventory Management

Inventory Management

Use Query by Example to Search for Items on Transfer Orders

When you consistently transfer a significant volume of goods between your warehouses, there are times when you need to make adjustments to specific order lines. Whether you’re adjusting the requested quantity, shipping method, or requested delivery date, if you have a large number of lines, it can be difficult to find a specific item on a transfer order. Now, you can use query by example to search for a particular item when editing your transfer order.

Query by Example on Edit Transfer Order

Enable the Query by Example functionality by clicking the icon. Once enabled, you can search for your item in the displayed field.

This feature provides you with an efficient way to find a specific item on your transfer order when you have a large number of goods on a single order.

Steps to Enable

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

Tips And Considerations

Consider using this feature if you have a transfer order with many lines and you want to locate a specific item.

Key Resources

• Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Management 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 any of these predefined job roles can access this feature:
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
  • Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)

• Users who are assigned a configured job role that contains this privilege can access this feature:
  • Manage Inventory Transfer Order (INV_MANAGE_INVENTORY_TRANSFER_ORDER_PRIV)

Use Approvals for Movement Requests

Use an approval-based workflow to route your requisition type movement requests to the appropriate approval authorities prior to executing the movement request. A workflow task generally passes from one user (or group of users) to another, usually for approvals. The users get notifications, for example when the task is assigned to them for approval. After all approvers act on the task, say by approving it, the task is complete and whatever was approved takes effect. You can configure approvals for the notifications to meet your own company's requirements.

Here are just a few examples of what you can do:

• Set how many levels of approval are needed for transactions for a specific organization.
• Define the assignees, based on say the supervisory hierarchy.
• Create approval groups so that the task can be assigned to a set of users in a group instead of an individual user.
• Get an FYI notification for the creator of the movement request.

Process for Movement Request Approvals

The image above shows the process for working on movement request approvals. Movement requests with a Requisition movement request type are enabled for approvals using workflow. Movement request types like Pick wave, Replenishment, and Shop floor don't go through the approval process and are preapproved as it happens today. You can enable approvals for movement requests by opting into the Use Approvals for Movement Requests feature.

Next, you can use the Manage Movement Request Approvals task to configure appropriate approval rules based on the movement request attributes to notify approvers for approval. More details are provided in the Steps to Enable section of this document.

Rules

Once the rules are configured, you are ready to create and submit the movement request. The Manage Movement Requests page is now enhanced to submit the movement request for approval when the opt in is enabled. Here are some important notes:

• The movement request is in Pending Approval status until it's approved.
• On approval, the movement request moves to Approved status. 
• On rejection by any of the approvers, the movement request moves to Rejected status and nothing more can be done on the movement request. 
• You can search for Approved, Rejected, and Pending Approval lines. 
• You can't edit or cancel a movement request in the Approved, Rejected, or Pending Approval status.

Manage Movement Requests

Notifications

Movement Request Approvals has implemented Oracle BI Publisher notification. When a user submits a Movement Request requisition type, it's sent for approval, and notifications are sent to approvers based on the rules and conditions defined on the setup page. Approvers receive an email as well as a notification in the global header section under the Notifications (bell) icon. Users can take actions like approve or reject through the email, by clicking the bell icon notification, or using the BPM Worklist.

Notifications

Inventory Movement Requests REST Resource

Today you can use the Inventory Movement Requests REST resource (inventoryMovementRequests) to create movement requests. You can choose to leave the movement requests in the default Incomplete status or set them to a Preapproved status. With the new approvals feature, this REST resource is now enhanced to be able to submit movement requests for approvals.

Once you opt into this feature, you can no longer use the REST resource to set the movement request to Preapproved status. If using REST, you now first create the movement request in Incomplete status. With the header ID of the incomplete movement request, you then submit the movement request for approval using the PATCH action on the REST resource. This updates the status of the movement request to Pending Approval and the approval workflow is initiated. You can only submit one movement request for approval at a time.

Transaction Console

• The Transaction Console gives you easy access to monitor and troubleshoot the approval processes.
• You can check the latest status of approval transactions and take necessary actions, for example recover failed transactions.
• You can search existing transactions and look for the approval history.
• You can access the simple and straightforward Process Details page.
• For faulted transactions, the Process Details page provides issue details and possible resolutions.
• You can add roles with the Review Approval Transactions privilege to provide access to the Transaction Console.

Transaction Manager

When issuing or transferring goods using movement requests in your organization, you may need the ability to route some, or all, of these requests to the proper approval authority before they can be executed. For instance, a very valuable and highly controlled item can only be moved within the warehouse under strict circumstances by specific personnel. As a result, you want specific individuals to be aware of and approve the movement of these goods. With the approval workflow available for movement requests, you now have a flexible rule-based approval mechanism to route your movement requests to the appropriate approval authorities prior to executing the movement requests.

Watch a Demo.

Steps to Enable

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

Offering: Manufacturing and Supply Chain Materials Management

In the Setup and Maintenance work area, use the Manage Movement Request Approvals setup task:

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Inventory Management
• Task: Manage Movement Request Approvals 

You can also optionally set up approval groups using the Manage Approval Groups task to configure rules for movement request approvals.

Setup and Maintenance Work Area

After selecting the Manage Movement Request Approvals task, you access the Manage Movement Request Approvals page:

Manage Movement Request Approvals

Movement Request Approval Stage and Participants

Oracle Fusion Cloud Inventory Management has a predefined stage for approvals for movement requests with different seeded participants.

Stage: Movement Request Approval Stage

Participants:

• Movement Request Parallel Consensus Participant
• Movement Request Serial Participant
• Movement Request FYI Participant
• Movement Request Parallel First Responder Wins Participant

Note that the participant name conveys both the participant type and the voting regime. For example, Movement Request Parallel First Responder Wins Participant has a participant type of Parallel and voting regime of First Responder Wins. This implies that all the approvers are notified in parallel and the first responder decision is final for that participant. You may choose to use and enable at least one or more of the participants for defining the approval rules.

Approval Rules

Approval rules are routing policies or rules that are evaluated to determine the approvers or FYI recipients for a business transaction. At least one rule with the condition Rule always applies must be created to prevent movement request approval transactions from getting stuck.

Rule Condition:

You can create rules on the approval task attributes to ensure the movement request approvals are routed to approvers based on the conditions for the business need.

Rules

Approval Task Attribute:

Here's the list of approval task attributes supported for creating approval rules:

• Created By
• Requester
• Destination Account
• Source Subinventory
• Destination Subinventory
• Organization
• Item
• Item Category (only Inventory functional area categories)
• Item Class
• Total Cost
• Transaction Type
• Movement Request Header DFF attributes
• Movement Request Line DFF attributes

Note that the user-defined attribute isn't supported. Also, conditions for approval task attributes with free text values only support Equals as the operator.

Actions

Action Types:

There are three types of actions:

• Approval Required: The movement request is routed for approvals.
• Automatic: The movement request can be approved or rejected automatically.
• Information Only: FYI tasks are sent to notify the specified people.

Route Using Attribute:

The Route Using attribute identifies the type of users needed to approve or receive notification of the movement request. The following list is supported for movement request approval. Each type has a specific set of parameters or properties that must be defined.

Route Using attributes include:

• Approval Group
• Job Level
• Single Approver
• Supervisory Hierarchy

Watch a Setup Demo.

Tips And Considerations

• The Use Approvals for Movement Requests feature is based on a permanent opt in. Choose to enable this opt in if you want approvals workflow for all your requisition type movement requests.

• Once you opt into the feature, all movement requests of type Requisition, across all inventory organizations, go through the approvals workflow.

• The user-defined attribute isn't supported when creating rules on the Manage Movement Request Approvals page.

• When defining conditions for rules, approval task attributes with free text values only support Equals as the operator.

• By default, a maximum of 25 movement request lines appear in the approval notification body.

• As a seeded configuration, the FYI notification is sent to the Created By user of the movement request once the request is approved.

• Customers can modify the notification using BI Publisher with the seeded Movement Request Approval Notification data model.

• It's recommended to submit one movement request header for approval at a time using the Inventory Movement Requests REST resource. REST doesn't support multiple submits for approval requests.

• By default, users who have access to the Transaction Console work area can see all transactions, from all product families.

Key Resources

• Watch Use Approvals for Movement Requests Readiness Training
• Oracle Fusion Cloud SCM: Using Inventory Management guide, available on the Oracle Help Center

Access Requirements

You have a couple of options for giving people access to the notifications body for movement request approval, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB) job role are automatically able to view the notifications for movement requests.

• Users who are assigned configured job roles that contain any one of these privileges are able to view the notifications for movement request approval:
  • Approve Inventory Movement Request Notification (INV_APPROVE_INVENTORY_MOVEMENT_REQUEST_NOTIFICATION_PRIV)

You have a couple of options for giving people access to define rules for movement request approvals, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB) or Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB) job roles are automatically able to configure approval rules for movement requests.

• Users who are assigned configured job roles that contain any one of these privileges are able to define approval rules for movement requests:
  • Manage Inventory Movement Request Approvals (INV_MANAGE_INVENTORY_MOVEMENT_REQUEST_APPROVALS_PRIV)

You have a couple of options for giving people access to the Transaction Console for recovering error transactions for movement request approvals, depending on whether you're assigning them predefined job roles or your own configured job roles.

• Users who are assigned Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB) job roles are automatically able to view and recover approval transactions for movement requests using the Transaction Console.

• Users who are assigned configured job roles that contain any one of these privileges are able to view and recover approval transactions for movement requests using the Transaction Console.
  • Review Approval Transactions (PER_REVIEW_APPROVAL_TRANSACTIONS_PRIV)

Use the Supply Request REST API to Set the Shipment Priority for a Transfer Order

Use the Supply Requests REST API to set the shipment priority on a transfer order line, which helps you improve how you prioritize shipments.

Here's how it works.

1. Oracle Applications come predefined to use values in the WSH_SHIPPING_PRIORITY lookup type for the shipping priority, such as Low, Medium, and High. To see the values that you can use, go to the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials Management offering, then search for and open the Manage Shipping Lookups task. On the Manage Shipping Lookups page, examine the lookup codes. You can reference them in your payload. If you don't see what you need, click Actions > New in the Lookup Codes area, then add new ones.

2. You use the Supply Request REST API to create or update the transfer order. Make sure you reference the value in the Lookup Code attribute from the Manage Shipping Lookups page in your REST API payload for the Shipment Priority.

3. Supply Chain Orchestration sends the shipment priority that you specify in REST API to Oracle Inventory Management, and Inventory Management sets the shipment priority on the transfer order line. Your warehouse manager can use the priority to prioritize shipping for the transfer order.

Sample Payload:

{

"InterfaceSourceCode": "EXT",

"InterfaceBatchNumber": "ss_rest_211215011",

"SupplyRequestStatus": "NEW",

"SupplyRequestDate": "2021-12-22T11:00:03.503-08:00",

"SupplyOrderSource": "EXT",

"SupplyOrderReferenceNumber": "211215011",

"SupplyOrderReferenceId": 1,

"ProcessRequestFlag": "Y",

"supplyRequestLines": [

{

"InterfaceBatchNumber": "ss_rest_211215011",

"InterfaceSourceCode": "EXT",

"SupplyOrderSource": "EXT",

"SupplyOrderReferenceLineNumber": "1",

"SupplyOrderReferenceLineId": 12112150511,

"SupplyType":"TRANSFER",

"DestinationOrganizationCode": "M1",

"SourceOrganizationCode": "M2",

"DestinationSubinventoryCode": "Stores",

"SourceSubinventoryCode": "Stores",

"ItemNumber": "DOS-IMT-Trfr-MM2",

"BackToBackFlag": "N",

"NeedByDate": "2021-12-22T01:01:12.123-08:00",

"Quantity": 15,

"UOMCode": "Ea",

"PreparerEmail": sendmail-test-discard@oracle.com,

"DeliverToRequesterEmail": sendmail-test-discard@oracle.com,

"RequestedShipDate": "2021-12-22T01:01:12.123-08:00",

"DestinationTypeCode": "INVENTORY",

"ShipmentPriorityCode":"HIGH"

}

]

}

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.

You can find details of the Supply Requests REST API in the Inventory Management section of the REST API for Oracle Fusion Cloud SCM documentation.

Key Resources

• Using Supply Chain Orchestration and Supply Chain Orchestration on the Oracle Help Center
• REST API for Oracle Fusion Cloud SCM 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 any of these predefined job roles can access this feature:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
  • Supply Chain Operations Manager (ORA_DOS_SUPPLY_CHAIN_OPERATIONS_MANAGER_JOB)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
  • Process Supply Order Interface (DOS_PROCESS_SUPPLY_ORDER_INTERFACE_PRIV)
  • View Supply Orders (DOS_VIEW_SUPPLY_ORDERS_PRIV)
  • Manage Supply Request Exceptions (DOS_MANAGE_SUPPLY_REQUEST_EXCEPTIONS_PRIV)
  • View Supply Order Exceptions and Status (DOS_VIEW_SUPPLY_ORDER_EXCEPTIONS_AND_STATUS_PRIV)
  • Manage Inventory Transfer Order (INV_MANAGE_INVENTORY_TRANSFER_ORDER_PRIV)

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

Selected Inventory Management Bug Fixes in This Update

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

Improve Locking Mechanism in Quantity Tree    

When there are multiple concurrent processes attempting to reserve the same item and organization combination, this can lead to cascading waits and lengthy processing times. Concurrency is handled through locks to serialize the processes. The more concurrency, the more the waits for locks, and the longer the run times of the processes. If a process waits and processes too long, it can strain the system and lead to a stuck thread and eventually impact the server. With this update, you can now manage the locking behavior around concurrent reservation seeking processes through configuration to reduce contention and processing times. Rather than waiting indefinitely for a lock, the process waits for a configurable time to acquire a lock and if no success, tries again after another configurable time. The number of tries to acquire a lock is configurable. If the process can’t acquire a lock even after the maximum retries, it returns an error. The three configurable items are managed through these profiles: ORA_INV_AVAIL_LOCK_WAIT, ORA_INV_AVAIL_LOCK_RETRIES, and ORA_INV_AVAIL_LOCK_TIMEOUT.    

Oracle reference: 33525967

Improve Performance of Pick Release Processing for High Volume of Order Lines     

With this update, pick release performance is enhanced to process a high volume of order lines. You can enable the INV_USE_IMPROVED_AVAILABILITY_QUERY profile option if you have a requirement to process a high volume of order lines through pick release. This enhancement uses an improved query to calculate Available to Reserve and Available to Transact quantities during the pick release run, which improves performance.    

Oracle reference: 34323925

Consolidate On-Hand Records in Staging Subinventory During Pick Release and Pick Confirm to Improve Performance    

Pick confirm moves material from a storage subinventory to a staging subinventory and calls the quantity tree for material availability checks. Pick confirm creates a unique on-hand record for every transaction in the staging subinventory. The increase in on-hand records affects the performance of both the pick release and pick confirm processes. With this update, you can now consolidate on-hand records in the staging subinventory during pick confirm if you enable the INV_CONSOLIDATE_ONHAND profile option. The records are consolidated based on the original receipt date populated for the item in the on-hand record. The combination of item, organization, revision, lot, subinventory, locator, project, task, and country of origin are used to consolidate the on-hand records. When the profile isn't enabled, the original receipt date is preserved even when subinventory transfers are performed for the item after the receipt of item in the storage subinventory. Note that the traceability of the transaction to the original transaction is lost when the on-hand records are consolidated. So any of your own functionality or reporting that uses the on-hand record transaction identifiers to link to original transactions is affected, and customers using that functionality aren’t recommended to enable this profile.    

Oracle reference: 34342663

Update the Purge Excess Inventory Reservations Scheduled Process to Delete Stuck Reservations for an Item Without the Transaction Enabled Attribute    

Prior to this update, the Purge Excess Inventory Reservations scheduled process didn't delete any stuck reservations for items which weren't enabled for the Transactable Enabled attribute on sales order issues. With this update, you can purge these excess reservations for a sales order even for an item that isn't enabled with the Transaction Enabled attribute.    

Oracle reference: 33964919

Update Reservations for Back-to-Back Items for Sales Order Lines That Haven't Been Interfaced to Shipping    

With this update, you can now create or update reservations using REST, file-based data import (FBDI), or the UI for back-to-back items on sales order lines that haven't been interfaced to shipping.     

Oracle reference: 33865514

Process Sales Order Issue Transactions from WMS with Multiple Lines for Same Item in Shipment    

With this update, you can now process sales order issue transactions from Oracle Warehouse Management with multiple lines for the same item in a shipment. The issue of relieving reservations for multiple lines for the same item when ship confirmation is done from Warehouse Management using the Perform Shipping Transactions process is now corrected. These shipment lines no longer get stuck in inventory with an error message stating that negative inventory balances aren't allowed in the organization.    

Oracle reference: 33838027

Steps to Enable

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

Shipping

Upload Serial Descriptive Flexfields Using Perform Shipping Transaction Import FBDI

File-based data import (FBDI) templates are the quickest and easiest way to upload large volumes of data. Now, when uploading your shipping transactions using the Perform Shipping Transaction Import FBDI template, you can provide data for your serial number descriptive flexfields (DFFs) when your serial number generation method is set to Entry at inventory pick or Entry at sales order, transfer order, or work order issue.

This enhancement to the Perform Shipping Transaction Import FBDI template lets you capture serial number descriptive flexfields. Now, you can upload additional information during processing ship confirmation transactions using the FBDI.

Perform Shipping Transaction Import FBDI

This table summarizes the attributes corresponding to each of the two serial number descriptive flexfields added in the FBDI template:

DFF Attributes

This feature provides you with a quick and efficient way to upload additional serial number data in your DFFs when importing a large number of shipping transactions using FBDI.

Watch a Demo.

Steps to Enable

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

Tips And Considerations

• Both serial number descriptive flexfields (Serial Numbers and Serial Attributes) are available to upload on the Perform Shipping Transactions Import FBDI.

• You can upload flexfield information for serial numbers with their serial number generation method set to Entry at inventory pick or Entry at sales order, transfer order, or work order issue.

• Separate segments for character, number, date, and timestamp are available to upload for the two serial number flexfields.

Key Resources

• Watch the Upload Serial Descriptive Flexfields Using Perform Shipping Transaction Import FBDI demo
• Oracle Fusion Cloud SCM: Using Shipping guide, available on the Oracle Help Center
• Oracle Fusion Cloud SCM: File-Based Data Import (FBDI) for SCM 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 to predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
  • Shipping Manager (ORA_WSH_SHIPPING_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Perform Shipment Transaction (WSH_PERFORM_SHIPMENT_TRANSACION_PRIV)

View Improved Pick Release Logs

When running a pick wave for a large number of orders, certain shipment lines can be excluded from selection for various reasons. For example, an order with many order lines on a shipment set can't be fully allocated during pick release. When this happens, it can be time consuming to try and investigate every shipment line that wasn’t released to your warehouse for picking.

Now, you can turn on enhanced pick release logging to view additional details about your pick wave. This feature provides you with summary level details in your pick release log. These additional details include the pick release demand selection criteria, pick release processing parameters, pick release sequence, the dynamic SQL statement used, and an overall count of the shipment lines that were excluded from selection with the reason those lines were excluded. Additionally, to see the exact shipment line numbers that were excluded, you can use the Enable Pick Release Detailed Logging profile option (ORA_WSH_PICK_RELEASE_ESS_DETAIL_LOGGING). This profile option value is set to N by default and must be set to Y to print the shipment line numbers in the log.

This feature provides you with a quick and easy way to identify which lines were excluded from being released to your warehouse for picking and why they were omitted.

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 23B

When you opt in to use this feature, you must opt in to the feature named: View Improved Pick Release Logs.

After you opt in, perform these steps:

• Optionally, set up the Enable Pick Release Detailed Logging profile option (ORA_WSH_PICK_RELEASE_ESS_DETAIL_LOGGING) to see the exact shipment line numbers that were excluded in the log. The profile value is supported only at the profile level of Site. This profile option value is N by default, and by default an overall count of the shipment lines that were excluded from selection with the reason those lines were excluded will print in the log.

Here's how to configure the profile option:

1. In the Setup and Maintenance work area, go to the Task panel tab.
2. Click Search and search for Manage Administrator Profile Values.
3. Click Manage Administrator Profile Values to open the page.
4. Enter Enable Pick Release Detailed Logging for the Profile Display Name or ORA_WSH_PICK_RELEASE_ESS_DETAIL_LOGGING for the Profile Option Code and click the Search button.
5. Select the profile option and go to the profile values.
6. Set the profile value to Y.

Manage Administrator Profile Values

Tips And Considerations

• The log messages print when pick release is performed using the Schedule Pick Wave scheduled process or the Release Pick Wave scheduled process (submitted by the Add to Release Schedule option on the Create Pick Wave page).

• The log file can be found as an attachment (Category: Enterprise Scheduler Job Log) in the Process Details section of the scheduled process.

Scheduled Processes

Key Resources

• Oracle Fusion Cloud SCM: Using Shipping 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 to predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
  • Shipping Manager (ORA_WSH_SHIPPING_MANAGER_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Create Pick Wave (WSH_CREATE_PICK_WAVE_PRIV)
  • Schedule Pick Wave (WSH_SCHEDULE_PICK_WAVE_PRIV)

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

• Predefined job role name and code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

• Privilege name and code for configured job roles:
  • Manage Application Profile Option (FND_APP_MANAGE_PROFILE_OPTION)

Send Unreserved Demand to an External WMS or 3PL

In today's fast-paced, just-in-time logistics environment, you need to fulfill your customer's orders as soon as possible. This means you may want to send orders to your external third-party logistics provider (3PL) or warehouse management system (WMS) before sufficient on-hand quantities are available. This way, you can quickly and efficiently cross-dock materials using your 3PL or WMS capabilities to fulfill outstanding orders faster.

Now, when integrating with an external 3PL or WMS, you can send unreserved shipment lines to your external execution system.

This feature provides you with greater flexibility in selecting which shipment lines you send to your external execution system and allows you to take advantage of your external execution system’s cross-docking capabilities.

Steps to Enable

In the Setup and Maintenance work area, use the Manage Shipping Parameters task to set the value of the Reservation Behavior for Integration to External Systems parameter to All lines without creating reservation:

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Shipping
• Task: Manage Shipping Parameters

Manage Shipping Parameters

Tips And Considerations

• By default, the Reservation Behavior for Integration to External Systems shipping parameter is set to Fully reserved lines.

• When the value of the Reservation Behavior for Integration to External Systems parameter on the Manage Shipping Parameters page is set to All lines without creating reservation:
  • The Generate Shipment Request process sends shipment lines to the external execution system without checking material availability and creating reservations.
  • Any reservation created prior to the Generate Shipment Request process is retained.

Key Resources

• Watch Send Unreserved Demand to an External WMS or 3PL Readiness Training
• Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center
• Oracle Fusion Cloud SCM: Using Shipping 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 to predefined job roles or your own configured job roles.

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
  • Shipping Manager (ORA_WSH_SHIPPING_MANAGER_JOB)
  • Shipping Agent     (ORA_WSH_SHIPPING_AGENT_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Create Outbound Shipment Request (WSH_CREATE_SHIPMENT_REQUEST_PRIV)
  • Schedule Pick Wave (WSH_SCHEDULE_PICK_WAVE_PRIV)
  • Manage Shipment Web Service (WSH_MANAGE_SHIPMENT_WEB_SERVICE_PRIV)

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

• Predefined job role name and code:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
  • Shipping Manager (ORA_WSH_SHIPPING_MANAGER)

• Privilege name and code for configured job roles:
  • Manage Shipping Organization Parameter (WSH_MANAGE_SHIPPING_ORGANIZATION_PARAMETER_PRIV)

Selected Shipping Bug Fixes in This Update

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

Add Data Security to the Confirm Shipments Scheduled Process    

Prior to this update, the submission of the Confirm Shipments scheduled process without specifying the Ship-from Organization parameter by a user who had access to some inventory organizations, but not all organizations, would process the ship confirmation for the shipments for all organizations. With this update, the user can only process ship confirmations for the accessible organizations.    

Oracle reference: 34261949

Update of Autocreating Shipments with Parallel Pick    

With this update, we've improved some functional and performance issues in the Parallel Pick Release process. Prior to this update, there were issues in the postpicking process like autocreation of shipment, autopacking, and autoshipping. There was also an issue with duplicate move order lines when shipment lines were created during the Parallel Pick Release process. With this fix, the Parallel Pick Release process now correctly recognizes when postpicking processes are requested and passes the correct actual ship date when autoshipping.  It also limits the records being selected in parallel picking to those that were created when picking begins.    

Oracle reference: 34397109

Steps to Enable

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

Receiving

Use Transaction Date as the Expenditure Item Date for Purchase Order Receipts

When using Project-Driven Supply Chain, the expenditure item date plays an important role in your project accounting flow. For example, the expenditure item date is used as the date for budgetary control and cost accruals. Because it plays such an important role in project-based orders, you need the expenditure item date accurately reflected for your transactions. Prior to this update, purchase order receipts used the date captured on the purchase order as the expenditure item date. If some of your items have long lead times, this can result in an inaccurate accounting picture once those goods are received. Now, purchase order receipts use the user-entered transaction date as the expenditure item date for project-based supply.

With this enhancement, the expenditure item date on the purchase order is no longer considered by Oracle Receiving during put away and other receiving transactions. Instead, the transaction date is passed to Oracle Cost Accounting and Oracle Receipt Accounting as the expenditure item date for Project-Driven Supply Chain transactions. Return and correction transactions in Receiving will also consider the transaction date for the expenditure item date. 

Examples:

This purchase order is created with the project-relation information and Expenditure Item Date as 7/20/22 for an inventory destination.

Purchase Order

This receiving put away transaction is performed with the transaction date (Receipt Date) as 6/27/22.

The transaction date in Receiving is available with the following labels, which are now considered for the expenditure item date for project-related transactions.

• Receipt Date on Receive Lines page
• Transaction Date on Put Away Lines page
• Return Date on Return Lines page
• Transaction Date on Correct Lines page
• Transaction Date in Self-Service receiving pages
• Transaction Date in receiving REST and SOAP services
• Transaction Date in receiving FBDI

Receive Lines

For inventory destination purchase orders, we can view the expenditure item date populated with the transaction date using the Review Completed Transactions page in Oracle Fusion Cloud Inventory Management.

We can see the Expenditure Item Date as 6/27/22 on the Review Completed Transactions page which is passed from Receiving on put away of the purchase order line.

Review Completed Transactions

This feature ensures that an accurate expenditure item date is used for purchase order receipts in the Project-Driven Supply Chain process.

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 23B

Tips And Considerations

• Purchase orders with inventory and expense destinations both consider the transaction date as the expenditure item date.

• For standard routing receipts where the receipt happens on date X and the put away on date Y, Receipt Accounting gets X for the receive transaction and Y for the deliver transaction as the expenditure item date, and Cost Accounting gets Y as the expenditure item date for Project-Driven Supply Chain transactions.

• The opt-in feature is always enabled after two releases, so from 23B.

• You can view the transaction date for the expenditure item date on the Review Completed Transactions, Review Receipt Accounting Distributions, Review Cost Accounting Distributions, and Manage Project Costs pages.

Key Resources

• Oracle Fusion Cloud SCM: Using Receiving 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 to predefined job roles or your own configured job roles.

•  Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Receiving Agent (ORA_RCV_RECEIVING_AGENT_JOB)
  • Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
  • Procurement Requester (ORA_POR_PROCUREMENT_REQUESTER_ABSTRACT)
  • Procurement Preparer (ORA_POR_PROCUREMENT_PREPARER_ABSTRACT)
  • Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature: 
  • Create Self-Service Receiving Receipt (RCV_CREATE_RECEIVING_RECEIPT_SELF_SERVICE_PRIV) 
  • Receive Receiving Shipment Line (RCV_RECEIVING_SHIPMENT_LINE_PRIV) 
  • Put Away Receiving Receipt (RCV_PUT_AWAY_RECEIVING_RECEIPT_PRIV)
  • Correct Receiving Receipt (RCV_CORRECT_RECEIVING_RECEIPT_PRIV)
  • Manage Receiving Receipt Returns (RCV_MANAGE_RECEIVING_RECEIPT_RETURNS)
  • Correct Self-Service Receiving Receipt (RCV_CORRECT_RECEIVING_RECEIPT_SELF_SERVICE_PRIV)
  • Manage Self-Service Receiving Receipt Return (RCV_MANAGE_RECEIVING_RECEIPT_RETURN_SELF_SERVICE_PRIV)

Selected Receiving Bug Fixes in This Update

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

Improve Performance of Receipt Elastic Search Ingestions    

Each time we receive a purchase order, Oracle Receiving ingests elastic search data in real time for the Account Payables receipt object. The real-time ingestion is done by inserting data into the FND_SEARCH_BULK_IMPORT table and then calling the scheduled process to ingest bulk records into Oracle Search Cloud Service. Due to the bulk receipts, a big number of ingestion job requests were being triggered, and other jobs were put on hold. With this update, the bulk ingestion job is no longer triggered on receipt.    

Oracle reference: 34208138

Update Performance of Manage Receiving Transactions Scheduled Process    

We've improved the performance of the Manage Receiving Transactions scheduled process. Prior to this update, users reported slow performance for the Manage Receiving Transactions scheduled process when trying to import bulk data using the Oracle Receiving file-based data import (FBDI).     

Oracle reference: 34257967

Pass Reference for Referenced Return of Expense Purchase Order Document    

Prior to this update, Oracle Receiving wasn't passing the disposition document reference (DISPOSITION_DOCUMENT_REFERENCE) for the recall process of an expense item while performing a referenced return of a purchase order. With this fix, the value correctly passes to the recalled product.    

Oracle reference: 34163334

Send Purchase Orders with Generate Changed Receipt Advice    

Prior to this update, the Generate Changed Receipt Advice scheduled process was sending a purchase order (not a newly created order, but one that was changed after creation) even though it was not ready to be accepted by the warehouse management system. The due date of the purchase order was in the future and it hadn't been interfaced to the warehouse management system. With this fix, the Generate Changed Receipt Advice scheduled process no longer sends future date orders that aren't ready to be accepted by the warehouse management system.    

Oracle reference: 34037369

Show Quantity Shipped on Purchase Order Schedule When ASN is Returned    

Prior to this update, we had a discrepancy on Receive Expected Shipments page when showing the quantity available after returning an advance shipment notice (ASN). With this fix, the quantity available is now shown correctly.    

Oracle reference: 34023748

Steps to Enable

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

Product Recall Management

Resolve Inbound Shipments and PO Schedules for Items on Recall

Receive notifications to guide you to count and quarantine inbound recalled parts. When you publish a recall notice for a recalled product, the recalled product may be in stock, issued to subinventories where the quantity isn’t tracked, expensed, or inbound.  When you locate and trace the recalled product, tasks are assigned, and notifications are sent based on your business rules.  Previously, for the recalled products that were part of an inbound shipment or a purchase order, notifications weren’t sent when the products were received. With this feature, when you receive an inbound recalled product, a notification is automatically sent so you can count and quarantine the recalled product. A recall trace line is generated for all the locations that received the product and a new count task is created. This enables the assigned person to count and move the recalled product to recall subinventory for the relevant disposal action. In the recall notice, the resolution of inbound shipment or open purchase order is changed to Count Task Generated when the count task is created.

The following image illustrates a received inbound shipment with updated resolution status.

Received Inbound Shipment with Updated Resolution Status

The following image shows the trace line based on the delivery of recalled product.

Trace Line for Product Delivery

If you replace the recalled products on a purchase order with a different product before shipment, the resolution status is updated as Replaced.  The following image illustrates an example of this.

Replaced Purchase Order

Alternately, you can manually mark an inbound trace line as exempt from recall if you receive confirmation from your supplier that the goods on the open PO schedules are free of defect. The following images illustrate how to mark a trace line as recall exempt.

Mark as Recall Exempt Button

Trace Line with Recall Exempt Status

When all the inbound trace lines in a recall notice have a resolution status, the deliver task assigned for each inventory organization in a recall notice is automatically closed. The following image illustrates an example of this.

Deliver Recalled Parts to Quarantine Location Task Completed

With count tasks automatically generated and notifications automatically sent for received recalled parts, there is tighter control over the recall process, enhancing consumer safety. With the resolution status getting updated for the inbound trace lines, you get more visibility about how the in-transit shipments and open PO schedules for recalled items get resolved. You no longer need to administer the tasks for delivered recalled items. 

Watch a Demo.

Steps to Enable

After you opt-in, you must perform the following steps to enable this feature:

• Under Receiving Parameters, select the Publish transactional business events option for your inventory organizations.

Navigation: Setup and Maintenance > Manufacturing and Supply Chain Materials Management offering > Receiving functional area > Manage Receiving Parameters task

• Define the FYI notification rules to notify the warehouse users and par counters to perform a recall count on the locations where the recalled item was delivered.

Navigation: Setup and Maintenance > Manufacturing and Supply Chain Materials Management offering > Facilities functional area > Manage Task Configurations for Supply Chain Management task > Search for ProductRecallTraceabilityFyi task in the Task Configurations tab on the BPM Worklist page.

Key Resources

• Watch Resolve Inbound Shipments and PO Schedules for Items on Recall Readiness Training

Refer to the following guides on the Oracle Help Center for more information:

• Implementing Manufacturing and Supply Chain Materials Management guide
• Using Product Recall Management guide

Access Requirements

Users who are assigned with the below mentioned predefined role are automatically able to access this feature:

• Job Role and Code:
  • Product Recall Manager (ORA_ENQ_PRODUCT_RECALL_MANAGER)

Cost Management

Calculate Acquisition Cost for Purchase Order Transactions with Enhanced Cost Processing

Use the enhanced cost processor to accurately calculate acquisition cost for purchase order transactions.

The redesigned acquisition cost processor, a sub-processor that handles all purchase related transactions, includes additional benefits over the existing logic. The improvements and benefits of the redesign include:

• Reconciliation improvements:
  • Enhanced logic to reconcile the Receiving Inspection account across Cost Accounting and Receipt Accounting.
  • For expense destination purchase orders, the expense accounting entry now includes both the functional and purchase order document currencies.
  • For the purchase order related transactions, the processor uses transaction dates instead of the cost accounting process date for more accurate currency translation calculations.
  • Invoice price variance adjustment events in Cost Accounting are posted to the General Ledger period that is same as the period used by Accounts Payable.
  • Transaction events are processed individually to honor transaction dates for more accurate currency translation calculations.
  • Absorb the entire invoice amount over the net delivered quantity rather than the ordered quantity on the purchase order.
  • Enables granular tracking, easier reconciliation and processing of each individual purchase order price events, and eliminates commingling of events.

• Handling multi-currency scenarios:
  • Avoids unnecessary cost variances for currency translation when the currency of the purchase order amount is the same as the functional currency of one of the secondary cost books but different than the functional currency of the primary cost book. 
  • Multiple purchase order price events with the same date can be processed in the same run of the acquisition cost processor. However, the processing of events is prioritized in this order starting with the PO receipt delivery followed by invoice and invoice corrections, landed cost charges, retro price events, PO returns, debit memo, and accrual clearing.
  • Improve accounting accuracy by reducing the decimal dust resulting from repeated currency conversions.

• Enhanced support for items purchased in their secondary unit of measure:
  • Support accurate acquisition cost calculation for catchweight scenarios for items tracked, purchased or transacted in secondary unit of measures.

• Additional improvements:
  • Eliminates unnecessary adjustments that were created for purchase order quantity changes.
  • Support cases when the payable accounting date on the associated invoice is in the future.
  • Handles purchasing in secondary unit of measure if the dual UOM feature is also opted-in by the customer.

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

Tips And Considerations

• Cross-currency conversions are usually set up in triangulation. Therefore, when defining currency conversions, ensure that your conversion rates triangulate to avoid discrepancies in currency conversion calculations. For example, if A to B is 1:2 and A to C is 1:3 then B to C must be 2:3.

• Flows related to fiscal documents will continue with the current functionality and will get processed only after the invoice is available in Cost Management.

• Not all decimal dust issues are eliminated. When the currency conversion rates are extremely large, their inverse can be extremely small, so some decimal dust issues can still happen.

• To maintain data accuracy, after you opt-in to this feature, you won't be able to opt-out.

Important! This feature will be automatically enabled in update 24D. If you don't enable this feature in production before update 24D, then be sure to test it in your stage (preproduction) environments before 24D so you're prepared when the feature becomes automatically enabled.

Key Resources

• Oracle Fusion Cloud SCM: Using Supply Chain Cost Management guide, available on the Oracle Help Center.

Access Requirements

Users who are assigned any of these predefined job roles are automatically able to access this feature: 

• Cost Accountant (ORA_CST_COST_ACCOUNTANT)

Users who are assigned configured job roles that contain these privileges are able to access this feature:

• Create Cost Distributions (CST_CREATE_COST_DISTRIBUTIONS_PRIV)

Expense Scrap and Use Accumulated WIP Balances with the Periodic Average Cost Method

You can use the options to expense scrap for manufacturing transactions and use the accumulated work in process balances for provisional completions with the periodic average cost method. These existing options are now available for the periodic average cost method too.

Use Accumulated Work in Process Balances and Expense Option for Scrap Accounting for Periodic Average Cost Method

Additionally, you can use the Resource Absorption Summary and the Resource Absorption Details reports to check whether the period resource expenses are absorbed. These reports would provide an insight on the total resource costs absorbed for a period and help to compare the information with the actual expenses incurred. These reports can be used for all cost methods, including periodic average cost method.

Absorption Summary Report That Shows the Total Resource Absorption for a Period

The option to use the accumulated work in process balances will help you to cost work orders with the actual work in process balances for work orders that span across periods, rather than using an estimated amount. The resource absorption reports will help you reconcile the resource costs absorbed across work orders for a period. You can use this to compare against the actual expenses incurred to ensure that you are absorbing the entire expenses.

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

Tips And Considerations

If you want to use the Expense Scrap and Use Accumulated WIP Balances with the Periodic Average Cost Method feature, then you must opt in to its parent feature: Use Periodic Average Costing to Value Inventory. If you’ve already opted in to this parent feature, then you don’t have to opt in again.

The Resource Absorption Summary and Detail reports are predefined Oracle Transactional Business Intelligence (OTBI) reports, and are available in the Reports and Analytics work area at Cost Management > Transactional Analysis Samples.

Key Resources

• Oracle Fusion Cloud SCM: Implementing Manufacturing and Supply Chain Materials Management, available on the Oracle Help Center.

Access Requirements

Users who are assigned any of these predefined job roles are automatically able to access this feature:

• Cost Accountant (ORA_CST_COST_ACCOUNTANT) for Cost Accounting.
• Applications Implementation Consultant

Use Enhanced Period Inventory Valuation and Gross Margin Reporting

Reconcile inventory valuation and report on gross margin more quickly using the enhanced reports processor data sources. This feature opt-in expires in update 23C. The previous reporting architecture for inventory valuation and gross margin is replaced with a new set of improved reporting tools. Improvements include updated processing logic for accounting intravaluation unit transfers, match cost dates with accounting dates, and handle negative inventory.

The following are some of the new functional capabilities introduced as part of this update.

1. Enhanced analytical infolets for Asset and Consigned Inventory valuation.

   

2. Redesigned Inventory Valuation page for streamlined reporting and reconciliation.

   

   New Inventory Valuation Page for Faster Reconciliation

3. Quickly review items by leveraging filters and exporting data to spreadsheets

   

   Leverage Filters and Export to Spreadsheet

4. Intuitively understand mismatch between costed values and accounted values in costing subledger at all levels.

   

   Identify Mismatches Readily

5. All inventory valuation and gross margin pages, reports , and OTBI and BICC extracts now work on the more performant cost reports processor data model.

6. The Cost Reports Processor can be run as a part of the Create Cost Accounting Distributions process. This process replaces the existing Refresh Cost Accounting Report Data process.

   

   Cost Reports Processor

7. The Cost Reports Processor is:

• Fast. The new report processor is incremental instead of full refresh.
• Real time. The report data automatically reflects the latest cost accounting result
• Prior period reporting data isn't unnecessarily recomputed. You can continue to view prior period reporting even if the current period is being calculated. 

8. All reporting objects listed in this table have been moved to the new cost reports processor data sources.

9. The Create Cost Accounting Distributions process has been enhanced to eliminate any reconciliation discrepancies between Inventory Valuation and General Ledger.

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

• Run the Cost Reports Processor as a separate run control in Create Cost Accounting Distributions to build data in the reports processor table for the first time.

• Once enabled, the Opt-in cannot be disabled after the Create Cost Accounting Distributions Process is run for the first time.

Tips And Considerations

• Important: This feature opt-in is scheduled to expire in 23C after which this feature becomes standard for all customers.  All existing reporting objects and views for item costs, inventory valuation and gross margin will be removed. You should transition to this feature by update 23B to avoid change management issues in 23C.

• List of Reporting Objects that will be deprecated in 23C and the new equivalent reports which replace them are included in this table:

• Any of your own reports that are based on old tables and views or OTBI artefacts will stop working from update 23C. Below are details of deprecated tables/views and the new tables/views they are replaced with:
• Cost Reports Processor:
  • All Reporting objects, pages, and reports fetch data from the cost reports processor based data sources. Ensure that Cost Reports Processor is run regularly using a schedule. If run times are reasonable then include Cost Reports Processor along with Create Cost Accounting Distributions process within the same run to always have real time data in your reports.
  • After you Opt-in:
    • The first run of the Create Cost Accounting Distributions with cost reports processor should be set up and run as a separate run control. The first run will build data in new data model objects and, therefore, may take more time because the data will be built from the first period.
    • For customers already using the cost reports processor, a full reports processor data rebuild will be required in update 22D to fully incorporate the latest features and fixes into the reports data sources. Therefore, you should set up a separate run control with only the Cost Reports Processor selected as the first run of the Create Cost Accounting Distributions for the cost organizations you have access to. The first run might take a longer time to process the data than regular runs, as it has to rebuild all the data.
      • Refresh Cost Accounting Report Data can be turned off by setting the profile option: ORA_CST_REFRESH_COST_ACCTG_REPORTS to NO. If required, you can still run the process manually to generate data for the old reports and views until Update 23B.
• Period BIP reports:
  • All BIP reports will now work in the context of periods. You can view data for the current date or for any prior period. Reporting for a specific valuation as-of date in prior period, except the period end date, isn't supported.

• Inventory - GL Reconciliation:
  • Perform reconciliation on a periodic basis after the period is closed.  This helps in load balancing because each month only the incremental data and balances need to be substantiated and reconciled.
  • All reports and UI now match Period Activity with Period Costed Value and Period Accounted Value to certify the amounts. 

1. If Period Activity doesn't match the Period Costed Value, make sure to resolve all negative inventory at item valuation unit level, resolve intravaluation unit in-transit transfers and ensure all transactions are costed. 
2. You can identify the exact item(s), if any, from the Review Inventory Valuation page where Period Activity doesn't match the Period Costed Value and take corrective action.
3. If Period Costed Value doesn't match Period Accounted Value, make sure all transactions are accounted. The Inventory Valuation Page now also shows transactions which aren't accounted or are costed and accounted across periods.
4. If Period Costed Value matches the Period Accounted Value but the Period Accounted Value doesn't match the balance in General Ledger, ensure:
   • Subledger accounting setup is configured to use inventory valuation account only for inventory items and only receipt and issue events hit inventory valuation account.
   • No manual journal entries are created in inventory valuation account without documentation and approval. Such manual journal entries, if any, should be treated as reconciling items.
   • Use inventory valuation account only for entries from costing subledger to ensure a hassle free reconciliation.
   • Use General Ledger tools such as Account Analysis report to flag activity not coming from cost accounting journal source and take corrective action.

• Don't turn off the account intravaluation unit transfers flag on item's cost profile if your valuation unit is at inventory organization level and you perform inventory accounting at subinventory level.
• Close periods on time to avoid costing and accounting transactions in different periods and avoid reconciliation issues. Ensure that prior periods are fully closed before starting cost processing for next period.

Key Resources

• Watch Use Enhanced Period Inventory Valuation and Gross Margin Reporting Readiness Training
• Oracle Supply Chain Management Cloud: Using Supply Chain Cost Management guide, available on the Oracle Help Center
• Opt-in Help Document

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 are automatically able to access this feature:
  • Cost Accountant (ORA_CST_COST_ACCOUNTANT) for Cost Accounting

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Review Inventory Valuation (CST_RUN_INVENTORY_VALUATION_REPORT)
  • Analyze Product Gross Margins (CST_ANALYZE_PRODUCT_GROSS_MARGINS)
  • Run Inventory Valuation Report (CST_RUN_INVENTORY_VALUATION_REPORT)
  • Run In-Transit Inventory Valuation Report (CST_RUN_INVENTORY_VALUATION_REPORT)
  • Run Layer Inventory Valuation Report (CST_RUN_LAYER_ INVENTORY_VALUATION_REPORT)

Fiscal Document Capture

Use REST Service to Confirm Item Deliveries in Fiscal Document Capture For Transfer Orders and RMAs

If you’re conducting supply chain operations in Brazil, you will need to capture fiscal documents for receipt transactions. Using Oracle Fiscal Document Capture, you can capture a fiscal document and confirm item deliveries against it. Using the REST service, you can create receipts recorded in an external application against a fiscal document line recorded in Oracle Fiscal Document Capture.

Use the REST service to perform the following functions:

1. Get all fiscal documents that are not in captured status using various parameters
2. Update delivered quantity of one or more fiscal document lines

The existing REST service that is used to confirm item deliveries is now further enhanced to also confirm item deliveries for additional fiscal flows - transfer orders, RMAs, dropship, consigned, and contract manufacturing.

You can update the received quantity using the following methods:

1. PATCH
2. POST(Bulk Patch)

You can also use the Oracle Excel Visual Builder plug-in with this REST service.

You can use the GET operations with various parameters. Here are some examples:

• Get all the fiscal document details for a source document type (i.e., Transfer Order) and source document number (i.e., Transfer Order number) in a business unit.

• Get all the fiscal document details for a source document type (i.e., Transfer Order), source document number (i.e., Transfer Order number), and source document line number (i.e., Transfer Order line number) in a business unit.

• Get the fiscal document details for a given fiscal document header ID 

• Get all fiscal documents in a business unit. You can use the option to exclude "Captured" fiscal documents.

• Get the fiscal document details using access key number in a business unit.

• Get the fiscal document details using the fiscal document number in a business unit.

• Get all the fiscal document details for an issuer in a business unit.

• Get all the fiscal document details for an inventory item in a business unit.

• Get all the fiscal document details using the issuer and inventory item in a business unit.

• Get all the fiscal document details using a receipt number in a business unit.

The following table lists the REST resources.

If your business process requires recording physical receipts of material outside Oracle Cloud, for example, in an external WMS or a 3PL system, you can use this REST service to create item deliveries against a fiscal document.

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.

Review the REST service definition in the REST API guides, available from the Oracle Help Center > your apps service area of interest > REST API. If you're new to Oracle's REST services you may want to begin with the Quick Start section.

Key Resources

• Refer to the REST APIs for Oracle Supply Chain Management Cloud documentation, available on the Oracle Help Center.

Access Requirements

You can give users access to this feature by assigning either predefined job roles or your own configured job roles

• Users assigned with these predefined job roles can automatically access this feature:
  • Fiscal Document Specialist (ORA_CMF_FISCAL_DOCUMENT_SPECIALIST_JOB)
  • Receiving Specialist (ORA_CMF_RECEIVING_SPECIALIST_JOB)

• Users assigned with configured job roles that contain these privileges can access this feature:
  • Capture Fiscal Document (CMF_ENTER_FISCAL_DOCUMENT)
  • Confirm Item Deliveries (CMF_CONFIRM_ITEM_DELIVERIES_PRIV)

Validate Fiscal Document Using a Scheduled Process

Validate multiple Brazilian fiscal documents using the “Import and Validate Electronic Fiscal Documents” scheduled process. The existing “Import Electronic Fiscal Documents” scheduled process is renamed to 'Import and Validate Electronic Fiscal Documents' and further enhanced to support bulk validation of the fiscal documents that were either manually created or imported via interface.  The new parameters added to this process allow you to either schedule the ESS process or run the process on demand for a controlled set of parameters.

Import and Validate Electronic Fiscal Documents

Automatic bulk validation of fiscal documents saves you from all the tiresome manual work. Your ability to schedule the process allows you to automatically validate the new FDs that are imported and pending validation.

Steps to Enable

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

Tips And Considerations

• Cancel the existing job scheduler and create a new schedule as the job has been renamed.
• If any parameters are left blank, the FDs continue to validate them as before.

Key Resources

• Oracle Supply Chain Management Cloud: Using Fiscal Document Capture guide, available on the Oracle Help Center.

Access Requirements

• Privilege Name and Code:
  • Process Electronic Fiscal Documents (CMR_PROCESS_E_FISCAL_DOCUMENTS)

• Job Role Name and Code:
  • Fiscal Document Specialist (ORA_CMF_FISCAL_DOCUMENT_SPECIALIST)

Supply Chain Financial Orchestration

Use Transactional UOM for Description Based Purchase Orders in Global Procurement

Process intercompany payables and receivable transactions using transactional UOM and quantity for description-based intercompany purchase orders. You can choose to use this option instead of setting up a service item in the financial orchestration system options.

In the Setup and Maintenance work area, go to the Manage Supply Chain Financial Orchestration System Options task.

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Supply Chain Financial Flows
• Task: Manage Supply Chain Financial Orchestration System Options

You have an option to configure the Global procurement business process flow for description lines either with a service item or without the service item setup using the check box, Consider service item for descriptive global purchase order processing.

If you deselect the Consider service item for descriptive global purchase order processing check box, Supply Chain Orchestration calculates the transfer price using the transactional UOM, and the transactional UOM is passed to Payables and Receivables for intercompany invoice generation.

You can simplify the setup configuration for descriptive global purchase orders while processing intercompany transactions. With this option, the transfer price will be calculated based on the transactional UOM. You need not setup the service items and UOM conversions for the service item in the Financial Orchestration System Options UI.

Steps to Enable

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

Key Resources

• Watch Supply Chain Financial Flows Enhancements Readiness Training
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management 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 Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB) can automatically access this feature.

• Users who are assigned the configured job roles that contain the Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV) privilege can automatically access this feature.

Configure Separate Supplier Accounts for Profit Center Business Units

You may have multiple Profit Center Business Units within your enterprise structure. Now you can configure separate supplier accounts for different profit center Business Units for your intercompany transactions.

In the Financial Orchestration work area open the Manage Profit Center Business Unit Party Relationships setup task.

For a profit center business unit, choose a supplier from the Supplier Number drop-down list.

You can now set up a separate supplier account for each Profit Center Business Unit defined under a legal entity. The supplier setups including the payment and tax details could be defaulted during creation of the intercompany invoices in Oracle Fusion Payables.

Steps to Enable

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

Key Resources

• Watch Supply Chain Financial Flows Enhancements Readiness Training

• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management 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 Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB) can automatically access this feature.

• Users who are assigned the configured job roles that contain the Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV) privilege can automatically access this feature.

Configure Additional Financial Orchestration Qualifiers to Model Your Financial Flows

Use the new financial orchestration qualifier attributes Bill to Party, Bill to Country, and Sold to Country, to model your financial flows for drop shipment, shipment, and nonshippable sales processes. You can now create qualifier rules based on these attributes to derive the financial flows for the appropriate business process type.

The new qualifier attributes are supported for Shipment, Drop Shipment, and Nonshippable Sales business process types.

In the Setup and Maintenance work area, use the Manage Supply Chain Financial Orchestration Qualifiers setup task.

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Supply Chain Financial Flows
• Task: Manage Supply Chain Financial Orchestration Qualifiers

You can now use the additional qualifier attributes to help configure rules based on these new parameters to orchestrate your financial flows.

Steps to Enable

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

Key Resources

• Watch Supply Chain Financial Flows Enhancements Readiness Training

• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management 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 Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB) can automatically access this feature.

• Users who are assigned the configured job roles that contain the Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV) privilege can automatically access this feature.