Cloud Readiness / Oracle Fusion Cloud Inventory Management
What's New
Expand All


  1. Update 22C
  1. Revision History
  2. Overview
  3. Pre-Update and Post-Update Tasks
  4. Optional Uptake of New Features (Opt In)
  5. Feature Summary
  6. Collaboration Messaging Framework
    1. Collaboration Messaging Framework
        1. Retrieve Large Purchase Order Payloads for B2B Messaging
        2. Send UBL PEPPOL Invoice Responses to Suppliers
  7. Inventory Management
    1. Inventory Management
        1. Create Bulk Reservations Using a REST Resource
        2. Purge Inventory Reservation Interface
        3. Use the Deliver-to Inventory Organization Time Zone When Fulfilling Supply Chain Demand
        4. Selected Inventory Management Bug Fixes in This Update
    2. Shipping
        1. Substitute Items for Transfer Order Lines Interfaced to an External WMS or 3PL
        2. Selected Shipping Bug Fixes in This Update
    3. Receiving
        1. Validate Expense Receipt Transaction Date
        2. Selected Receiving Bug Fixes in This Update
    4. Intrastat
        1. Print Country of Origin for Northern Ireland Intrastat Dispatches
    5. Cost Management
        1. Use Periodic Average Costing to Value Inventory
        2. Use Additional Subledger Accounting Sources in Cost Accounting
        3. Selected Cost Management Bug Fixes in This Update
    6. Fiscal Document Capture
        1. Process a Complementary Fiscal Document for a Bookkeeping Fiscal Document

Update 22C

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 Product Feature Notes
29 JUL 2022 Cost Management Use Additional Subledger Accounting Sources in Cost Accounting Updated document. Revised feature information.
25 JUL 2022 Cost Management Selected Cost Management Bug Fixes in This Update Updated document. Added a section.
22 JUN 2022 Inventory Management Use the Deliver-to Inventory Organization Time Zone When Fulfilling Supply Chain Demand Updated document. Shared a feature from Oracle Purchasing.
17 JUN 2022     Created initial document.

Overview

HAVE AN IDEA?

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

GIVE US FEEDBACK

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

DISCLAIMER

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

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

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

Column Definitions:

Report = New or modified, Oracle-delivered, ready to run reports.

UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.

UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.

Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.

Ready for Use by End Users
(Feature Delivered Enabled)

Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features.

Customer Must Take Action before Use by End Users
(Feature Delivered Disabled)

Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing.

Feature

Report

UI or
Process-Based:
Small Scale

UI or
Process-Based:
Larger Scale*

Collaboration Messaging Framework

Collaboration Messaging Framework

Retrieve Large Purchase Order Payloads for B2B Messaging

Send UBL PEPPOL Invoice Responses to Suppliers

Inventory Management

Inventory Management

Create Bulk Reservations Using a REST Resource

Purge Inventory Reservation Interface

Use the Deliver-to Inventory Organization Time Zone When Fulfilling Supply Chain Demand

Selected Inventory Management Bug Fixes in This Update

Shipping

Substitute Items for Transfer Order Lines Interfaced to an External WMS or 3PL

Selected Shipping Bug Fixes in This Update

Receiving

Validate Expense Receipt Transaction Date

Selected Receiving Bug Fixes in This Update

Intrastat

Print Country of Origin for Northern Ireland Intrastat Dispatches

Cost Management

Use Periodic Average Costing to Value Inventory

Use Additional Subledger Accounting Sources in Cost Accounting

Selected Cost Management Bug Fixes in This Update

Fiscal Document Capture

Process a Complementary Fiscal Document for a Bookkeeping Fiscal Document

Collaboration Messaging Framework

Collaboration Messaging Framework

Retrieve Large Purchase Order Payloads for B2B Messaging

Configure Oracle Collaboration Messaging Framework to process large purchase orders (typically more than 2,000-lines) when you initiate B2B communication. The payload for a large purchase order is retrieved in small parts from Oracle Purchasing and then combined and delivered as one purchase order, resulting in improved performance.

After you enable the feature, enter a value in the Large PO Processing section of the Manage Collaboration Messaging Configuration page in the Large PO Minimum Line Count field to specify the minimum number of lines in a large PO. Then enter a value in the PO Lines Retrieved in a Single Query field to specify the number of lines to retrieve from Oracle Purchasing in each part (1000 lines by default). The values you set in the Large PO Delivery Duration (30 minutes by default) and Large PO Delivery Attempt Interval (3 minutes by default) fields indicate how long and how often to attempt delivery of the PO.

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

Large Purchase Order Processing in Manage Collaboration Messaging Configuration

Steps to Enable

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

Offering: Order Management

Tips And Considerations

In general, a purchase order with more than 2,000 lines is considered a large purchase order, but you can determine the minimum line count for your large purchase orders based on your specific business needs.

Key Resources

  • Oracle Supply Chain Management Cloud: Configuring and Managing B2B Messaging guide available on Oracle Help Center.

Role And Privileges

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

  • Users who are assigned this predefined job role can access this feature:
    • B2B Administrator  (ORA_CMK_B2B_ADMINISTRATOR_ABSTRACT)
  • Users who are assigned configured job roles that contain this privilege are able to access this feature:
    • Manage Collaboration Messaging Configuration (CMK_MANAGE_COLLAB_MESG_CONFIG_PRIV)

Send UBL PEPPOL Invoice Responses to Suppliers

Use the new predefined message definition UBL-2-1-InvoiceApplicationResponse-Out to send details about rejected invoices in the UBL PEPPOL format to your suppliers.

Enable the procure-to-pay business process to exchange the associated document, Invoice Acknowledgment-Outbound.

Set up this message definition as an outbound collaboration message for a trading partner and then associate the trading partner, and the Invoice Acknowledgment-Outbound document with a supplier using the Manage Supplier B2B Configuration task in the Collaboration Messaging work area.

UBL-2-1-InvoiceApplicationResponse-Out Message Definition

Enables automated invoice status communication using the UBL PEPPOL application response message.

Steps to Enable

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

Key Resources

  • Configuring and Managing B2B Messaging for Oracle Applications Cloud guide available on the Oracle Help Center.

Role And Privileges

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)
  • Users who are assigned a configured job role that contains these privileges can access this feature:
    • Manage B2B Supplier Trading Partners (CMK_B2B_SUPPLIER_TRADING_PARTNERS_PRIV)
    • Manage B2B Trading Partners (CMK_B2B_TRADING_PARTNERS_PRIV)

Inventory Management

Inventory Management

Create Bulk Reservations Using a REST Resource

High order volumes for a scarce number of items can quickly strain your available supply. In this situation, you need the ability to quickly create a large number of reservations to ensure you don't overcommit your available supply. Now, you have the ability to create reservations in bulk using the Inventory Staged Reservations REST resource. This REST resource inserts the reservations into the reservation interface table and then uses the Manage Reservation Interface process to efficiently create the reservations.

This new REST resource lets you create reservations for a large number of orders more efficiently than using the existing Inventory Reservations REST resource to create reservations order by order.

Steps to Enable

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

  • Oracle Supply Chain Management Cloud: REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.

Role And Privileges

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)
    • Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Privilege Name and Code: Manage Inventory Staged Reservations Web Service (INV_MANAGE_INVENTORY_STAGED_RESERVATIONS_WEB_SERVICE_PRIV)

Purge Inventory Reservation Interface

When loading a large number of inventory reservations to support a high volume of orders, one simple data entry mistake can be replicated in thousands of lines. Whether you catch this mistake before the lines are processed or after, you need a quick way to delete a large number of lines with incorrect data. Now, you can run the Purge Reservations Interface process to purge data from the INV_RESERVATIONS_INTERFACE table. This process contains three available parameters to assist you in properly selecting the records you want to purge. The first parameter, Purge Data Before, purges any records created before your specified date. The second parameter, Status, lets you purge errored, pending, or all records. Finally, the third parameter, Load Request ID, lets you purge records for a specific file-based data import (FBDI) load.

This feature lets you quickly and efficiently clear out unnecessary or irrelevant reservation records from Oracle Fusion Cloud Inventory Management’s reservation interface table.

Steps to Enable

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

Tips And Considerations

You can use the Purge Data Before, Status, and Load Request ID parameters to purge the reservations interface.

Purge Inventory Reservations Interface Schedule Process

This schedule process has the following parameters:

  • Purge Data Before: Purges records in the reservation interface which are created before this date.
  • Status: Purges error, pending, or both error and pending records.
  • Load Request ID: Purges records for a specific load request. This is applicable for records loaded using the Reservation FBDI.

Key Resources

Role And Privileges

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)
    • Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Privilege Name and Code: Purge Inventory Reservations Interface (INV_PURGE_INVENTORY_RESERVATIONS_INTERFACE_PRIV)

Use the Deliver-to Inventory Organization Time Zone When Fulfilling Supply Chain Demand

Use the time zone specified on the inventory organization definition for deriving the local time zone for delivery and shipping locations. With this feature, Oracle Order Management back-to-back sales orders, Oracle Supply Planning, and Oracle Manufacturing can communicate the requested delivery or shipping dates to Procurement in the time zone of the deliver-to and ship-to organizations. In addition, requisitions sourced from min-max planning and PAR replenishment are now created in the time zone associated with the inventory organization. This ensures that the requested dates on purchase requisitions aren’t past dates as per the time zone specified in the deliver-to organization in the upstream applications.

Using this feature, the requested dates on purchase requests from external applications and those entered manually in UIs will be validated to ensure that they aren't past dates as per the current date in the time zone of the deliver-to organization. Also, the delivery and ship dates on related purchase orders will reflect the ship-to location local time zone.

These screen captures illustrates the feature for a back-to-back requisition and purchase order line:

Back-to-Back Sales Order Entered on Same Time Zone as Supply Warehouse

Supply Details on the Sales Order Fulfillment View Show the Schedule Ship Date on Warehouse Time Zone

Back-to-Back Requisition Line Shows the Requested Delivery Date on the Delivery-to Location Local Time Zone

Purchase Order for Back-to-Back Requisition Line Shows the Requested Delivery Date and Promised Delivery Date on the Ship-to Location Local Time Zone

Steps to Enable

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

Offering: Procurement

Define a Time Zone for the Inventory Organization in Setup and Maintenance > Manage Inventory Organizations > Manage Inventory Organization Parameters:

Manage Organization Parameters

Tips And Considerations

  • In the requisition import program (FBDI or Purchase Request Web Service), the requested delivery date and requested ship date are validated according to the local time zone of the destination inventory organization. If the inventory organization time zone isn't defined, the program assumes the UTC zone. In REST APIs and UIs, only the requested delivery date is supported and is validated in the same manner.
  • The requested delivery date also defaults for requisitions created using the requisition import program or manually entered in UIs. The default date is the current date in the destination inventory organization time zone plus the number of days in the offset profile: POR: Requested Delivery Date Offset.
  • For requisitions for one-time locations, the requested delivery date is according to the time zone of the default deliver-to organization in the Requisitioning BU.
  • You can't use this feature for purchase requests for drop ship sales orders. For drop ship sales orders, the requested delivery and ship dates are currently validated according to the time zone of the legal entity of the inventory organization. If the legal entity time zone isn't enabled, the date validation is based on the UTC.
  • For internal material transfers, the requested delivery date of the requisition line is converted from the inventory organization's local time zone to the UTC zone for transfer order creation.

Role And Privileges

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:
    • For creating requisitions using the UI:
      • Procurement Requester (ORA_POR_PROCUREMENT_REQUESTER_ABSTRACT) or
      • Procurement Preparer (ORA_POR_PROCUREMENT_PREPARER_ABSTRACT)       
    • For creating requisitions using the requisition import process (FBDI or Purchase Request Web Service):
      • Procurement Integration Specialist (ORA_PO_PROCUREMENT_INTEGRATION_SPECIALIST_JOB)           
      • Buyer (ORA_PO_BUYER_JOB)           
      • Procurement Manager (ORA_PO_PROCUREMENT_MANAGER_JOB)       
    • For creating requisitions using the REST API:           
      • Refer to the Job Roles and Privileges section in the REST API for Oracle Procurement Cloud documentation, available on the Oracle Help Center.
    • For creating purchase orders from requisitions:
      • Buyer (ORA_PO_BUYER_JOB)

If you're maintaining your own configured 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.

Restrict Active Picking Rule Creation and Update During Edition-Based Redefinition Maintenance    

With this update, Edition-Based Redefinition provides customers zero application downtime during patching. One exception is that active picking rules can't be created or updated during maintenance periods. This is enforced by an error message when users try to do so using the Manage Picking Rules task.    

Oracle reference: 33328945

Change Release Sequence Behavior on Lines with Shipset    

Prior to this update, when running pick release with enforce shipsets enabled and the primary release sequence sort attribute set to something other than Order, there were cases when shipsets were being excluded from picking erroneously.  Now, if the sort criteria values are different within a shipset, pick release takes the maximum and minimum value of the sort criteria and applies that to the entire shipset.    

Oracle reference: 29019416

Change Count Sequence to Lower Number    

With this update, if you try to change the starting count sequence number on the Edit Cycle Counts page to a number lower than the existing number, the page displays a warning message stating: If you change the starting count sequences to a lower number, you will get new count sequences with existing count sequence numbers. If you continue, this might result in errors while approving cycle count sequences or lead to inaccurate data in reports such as OTBI.     

Oracle reference: 33763636

Change Default Value of Line Status Parameter for Print Movement Request Pick Slip Report to Print Open Picks    

With this update, the default value of the Line Status to Print parameter is now set to Open Picks. This prints only the open picks, and it's faster to run. Prior to this release, the Line Status to Print parameter of the Print Movement Request Pick Slip Report had a default value of All. This printed completed picks, open picks, and unallocated movement requests in the report. When the report was run with the default value of All for this parameter, it took a lot of time and resources to print data that might not be useful.    

Oracle reference: 34031450

Update Transfer Order Number for Source Reference Field on Review Completed Transactions Page    

Prior to this update, the Source Reference field on the Review Completed Transactions page was showing the incorrect transfer order number for the Source Type of Transfer Order and Transaction Type of Transfer Order Issue. Now users can view the correct transfer order number for the Source Reference field.   

Oracle reference: 33880833

Add Legal Entity Field to Export Intrastat Collections    

The RTF file generated by Export Intrastat Collections now contains the Legal Entity field, which is also a part of the Print Intrastat Collections report. This ensures that both reports now have the same set of fields.    

Oracle reference: 33834128

Associate Serial Numbers to Reservation After Entering Locator for Subinventory    

You can enter serial numbers while creating reservations only after you enter the locator for a subinventory where locator control is prespecified. You can't associate serial numbers to a reservation for a dynamic locator-controlled subinventory without providing the locator using the Inventory Staged Transactions REST resource.    

Oracle reference: 33350493

Associate Trading Partner VAT Number to Intrastat Transaction to Show on Export Intrastat Collections Report    

You can enter the Trading Partner VAT number for the source transaction and save the Intrastat transaction. This lets you associate the Trading partner VAT number with the transaction and display it on the Export Intrastat Collections report.    

Oracle reference: 33571022

Update Demand Quantity for Sales Orders on Review Item Supply and Demand Page for Partially Picked or Staged Orders    

The demand quantity for a sales order on the Review Item Supply and Demand page is now correct even when the sales order is partially shipped or staged.    

Oracle reference: 33945331

Steps to Enable

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

Shipping

Substitute Items for Transfer Order Lines Interfaced to an External WMS or 3PL

Demand spikes, supplier backorders, and product recalls are just a few events that can cause a significant impact to your available on-hand quantities. In these types of situations, you can quickly run out of enough goods to fulfill your internal demands. However, you might have alternate goods that can serve the same purpose as the requested goods. When this situation arises, you need the ability to substitute these alternate goods to keep your operations running even when you're using an external execution system to fulfill your orders. Now, you can substitute requested goods when interfacing transfer order shipment lines to an external execution system. 

The ability to send substitute items to your external execution system when fulfilling transfer orders provides you greater flexibility to fulfill your internal orders and keeps your business running without unnecessary delays.

Steps to Enable

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

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

This feature uses the same opt-in that was used for the 22A feature Substitute Items during Pick Release for Transfer Orders.

In order to use this feature, you must opt in to the feature named: Substitute Items during Pick Release for Transfer Orders.

After you opt in, perform these steps:

Setup Steps in Inventory Management

Once the feature is enabled, you can see the new Enable substitution for external system integrations check box on the Manage Shipping Parameters page.

  1. In the Setup and Maintenance work area, select the Manage Shipping Parameters task:
    • Offering: Manufacturing and Supply Chain Materials Management
    • Functional Area: Shipping
    • Task: Manage Shipping Parameters
  2. Search for the organization and select the Enable substitution for external system integrations check box. This check box must be enabled for the source organization if you want the original item to be substituted with substitute items when the original item isn't available to meet the demand for a transfer order.

Manage Shipping Parameters

  1. In the Setup and Maintenance work area, select the Manage Inventory Organizations task:
    • Offering: Manufacturing and Supply Chain Materials Management
    • Functional Area: Inventory Management
    • Task: Manage Inventory Organizations
  2. Search for the organization and select the Warehouse accepts substitute items check box. This selection must be consistent with the destination inventory organization on the transfer order, and it ensures that the Allow item substitution check box is checked for any transfer order lines raised in that organization.

Manage Inventory Organization Parameters

  1. Optionally, complete setup steps to maintain item substitute relationships at the organization level.

When you opt in to use this feature, you must opt in to the feature named: Manage Related Items at the Organization Level. For instructions, refer to the Optional Uptake of New Features section of this document. This feature is only required when you want to maintain item substitute relationships at the destination organization level. It isn't required if you want to maintain all your relationships at the item master level.

Product Information Management Feature Opt In

Edit Features: Items

Setup Steps in Product Information Management

To set up the item substitute relationships, navigate to the Manage Items task.

  1. In the Setup and Maintenance work area, select the Manage Items task:
    • Offering: Manufacturing and Supply Chain Materials Management
    • Functional Area: Product Information Management
    • Task: Manage Items
  2. Select the Relationships tab, and then the Related items tab.

The relationships can be direct or chain relationships. In this case, item ORIGITEM has a direct relationship with three of its possible substitutes, and it also has a chain relationship through SUBITEM1 with SUBITEM2LOT. The relationships are defined at either the master or organization level and can’t be defined at both. If set at the organization level, the relationship refers to the destination organization in the context of a transfer order. If set at the master level, the relationship is always valid. The rank, within the level of the hierarchy, determines the order in which the items are considered by the Generate Shipment Request process. In this case, although the rank of item SUBITEM2LOT is second in line, it's considered last since it's a level deeper in the hierarchy than the other items. The type is always substitute, and you have the option of defining the relationship as reciprocal, therefore both ways.

Edit Item: Item Relationship Direct and Chain Relationship Setup

Tips And Considerations

  • The Generate Shipment Requests process sends the substituted transfer order lines to an external Third-Party Logistics provider (3PL) or Warehouse Management System (WMS). So the execution system isn't aware of the original requested item. 
  • The transfer order shipment lines for the available quantity of the original and substitute items are interfaced to the external system when the value of the Reservation Behavior for Integration to External Systems parameter on the Manage Shipping Parameters page is set to Partial.
  • The shipment lines are interfaced to an external system only when the entire requested quantity of the original item can be fulfilled by a combination of original and substitute items when the value of the Reservation Behavior for Integration to External Systems parameter on the Manage Shipping Parameters page is set to Full.
  • The Generate Shipment Request process substitutes the original requested item on the transfer order line with substitute items based on the ranks of the substitute items.
  • The Generate Shipment Request process reserves the original item on the transfer order line to the substitute item for the quantity which can be successfully interfaced to the external system.
  • The change management behavior for the substituted transfer order lines are in accordance with the regular change management behavior.
  • The ship confirmation of the entire substituted quantity from the external system closes the transfer order.
  • Back order action on the substitute transfer order item from the external system cancels the shipment line for the substitute item and creates a new line for the original item for the canceled quantity.
  • Product Information Management:
    • Item-substitute relationships are maintained at either the item master or destination organization level.
    • Both direct and chain item relationships are supported.
    • There can be many substitute item relationships defined. However, the Generate Shipment Request process only considers the first three viable substitutes for use by level in the hierarchy and rank.
    • Substitute items can be for different units of measure than the original item, with standard, interclass, and intraclass conversion required as appropriate. The exception is for dual unit of measure items, which must have the same primary and secondary unit of measure as the original item in the destination organization.
    • WARNING: It's recommended for the substitute items to have the same unit of measure as the original item. Having different units of measure can lead to fractional quantities left over in certain scenarios.

Key Resources

Role And Privileges

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:
    • Generate Shipment Request (WSH_GENERATE_SHIPMENT_REQUEST_PRIV)
    • Create Outbound Shipment Request (WSH_CREATE_SHIPMENT_REQUEST_PRIV)
    • Manage Shipment Web Service (WSH_MANAGE_SHIPMENT_WEB_SERVICE_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.

Update Print Mailing Label Report for Shipments Containing Alphanumeric Packing Units    

Prior to this update, the Print Mailing Label report completed in error when run for a shipment that contained an alphanumeric packing unit. This behavior has now been fixed for this update.    

Oracle reference: 33862390

Add Fields to Shipment Line REST Resource for Complete Decimal Values    

Prior to this update, the GET method of the Shipment Line REST resource was truncating decimal values of the Unit Price, Selling Price, Unit Weight, Unit Volume, and Volume fields. Now, new fields have been added to the Shipment Line REST Resource that show the complete decimal values. These new fields include LineUnitPrice, LineSellingPrice, LineUnitVolume, LineVolume, and LineUnitWeight.    

Oracle reference: 33857218

Update Apply Document Job Set Rules and Output Preferences Scheduled Process to Launch Document Job Sets    

Prior to this update, the Apply Document Job Set Rules and Output Preferences scheduled process triggered by the Perform Shipping Transaction scheduled process didn't launch document job sets. Therefore, no reports were being generated and attached. This behavior has been corrected in this update.    

Oracle reference: 33945727

Update Manage Transportation Schedules Setup Page to Accept Trading Partner with Apostrophe    

Prior to this update, the Manage Transportation Schedules Setup page gave an error when performing a search for a Trading Partner Type as Customer, Supplier, Organization, or Carrier if the trading partner name contained an apostrophe. For example, if the customer name was ABC's Paint. This behavior is corrected in this update.    

Oracle reference: 33947356

Improve Performance of Order Field on Create Pick Wave and Manage Pick Wave Release Rules Pages    

We've improved the performance of the Order field list of values on the Create Pick Wave and Manage Pick Wave Release Rules pages.    

Oracle reference: 33796768

Enhance Search and Navigation on Manage Shipment Lines Page    

On the Manage Shipment Lines page, when search results have more than 25 records and you navigate to the Edit Shipment Line page for any record that appears after the 25th record, you no longer lose the value in the navigation choice list on the Edit Shipment Line page.    

Oracle reference: 33847008

Support Pagination for Shipment Transaction Requests REST Resource for the GET Method    

The Shipment Transaction Request REST Resource now supports pagination using the GET method.    

Oracle reference: 34010440

Steps to Enable

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

Receiving

Validate Expense Receipt Transaction Date

Even when every effort to ensure that the data you enter for receipts is correct, mistakes happen. These data mistakes can be particularly problematic when dates are accidentally transposed during bulk data loads. For example, let’s say you accidentally enter a transaction date with the year 2002 instead of 2022, and then copy that date for 500 records. Due to this error, you now have all of these transactions stuck in your receipt accounting distributions because they failed budgetary control since there is no open budget period for 2002. Now, you have the ability to specify the maximum number of days prior to the current date in which you can create expense destination receipts for purchase orders and transfer orders using the Maximum Number of Days Prior to Current Date in Which an Expense Destination Transaction Can Be Created profile option.

The default value of the profile option is set at 180. Therefore, you can enter a transaction date in the past going back 180 days from the current date for receiving, put away, correction, and return transactions for expense destination receipts. You can always change and set the value of the profile option based on your business requirements. If you try to perform a transaction at a date past the value defined in the profile option, you receive the following message. You should then provide the correct date to process the transaction.

Receive Lines

This feature reduces errors associated with entering incorrect receiving transaction dates for expense receipts. It’s critical that transaction dates are validated prior to creating receiving transactions. By identifying date-related errors upstream in the process, transactions with incorrect dates can be prevented in downstream applications such as Oracle Cost Management. Ultimately, this feature saves your organization time, reduces errors, and improves data accuracy when closing and reconciling your budget periods, projects, and receipt accounting.

Additionally, the new Receiving profile option provides you with the flexibility to define the number of days in which a past-dated transaction is allowed for expense destination receipts. The default profile value is 180 days. However, you can configure a profile value to be more or less restrictive based on your organization's business requirements.

Steps to Enable

To use the Validate Expense Receipt Transaction Date feature, you must enable the Maximum Number of Days Prior to Current Date in Which an Expense Destination Transaction Can Be Created profile option. The profile value is supported only at the profile level of Site.

Here's how to configure the profile option:

  1. In the Setup and Maintenance work area, go to the Manage Receiving Profile Options task:
  • Offering: Manufacturing and Supply Chain Materials Management
  • Functional Area: Receiving
  • Task: Manage Receiving Profile Options
  1. On the Manage Receiving Profile Options page, enter Maximum Number of Days Prior to Current Date in Which an Expense Destination Transaction Can Be Created in the Profile Display Name field and click Search
  2. Enter the maximum number of days in the Profile Value field for the profile level of Site and click Save.

Manage Receiving Profile Options

Tips And Considerations

The Maximum Number of Days Prior to Current Date in Which an Expense Destination Transaction Can Be Created profile option has a default value of 180 days. However, you can change the profile value to be more or less restrictive based on your business needs.

The Validate Expense Receipt Transaction Date feature validates transactions created from the receiving pages, Receiving Receipt Import file-based data import (FBDI) process, and REST/SOAP services.

When you attempt to create a receiving transaction for a destination type as expense before the specified maximum number of days, you receive an error message like this: "You can't create the transaction because the transaction date is before 9/24/21. Use Manage Receiving Profile Options setup task to update profile value." For receiving transactions created using the Receiving Receipt Import FBDI, the error message displays in the receiving interface. When receiving transactions are created using the REST and SOAP services, the error message displays in the service response. In both cases, you can correct the transaction date and reprocess the transaction.

Key Resources

  • Watch Validate Expense Receipt Transaction Date Demo.
  • Oracle Supply Chain Management Cloud: Using Receiving guide, available on the Oracle Help Center.

Role And Privileges

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: 
    • Privilege Name and Code: 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)

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.

Add Transaction Date Validation for Receiving Transactions Performed Against Manufacturing Destination Purchase Orders    

Prior to this update, transaction dates weren't validated for receiving transactions related to the work order destination type of purchase orders. We now have a validation on performing receive, deliver, inspect, correct, and return to supplier transactions for purchase orders with the work order destination type, and we make sure the transaction date is validated based on the Transaction Date Validation Enabled inventory management profile option. This behavior is similar to the transaction date validation on purchase orders with the inventory destination type.    

Oracle reference: 33979926

Prevent Changes to Secondary Quantity on Inspect Pages for Quality-Based Inspections    

Currently, during receiving, inspection users can't split a line because the Split Line action is disabled if the Use Quality Inspection Plan option is enabled on the Manage Receiving Parameters page for the inventory organization. However, if the item is under dual UOM control, users can split the line by entering the secondary quantity on the Inspect Lines or Inspect Line pages. To prevent this behavior, the Secondary Quantity field is now a noneditable field on the Inspect Lines and Inspect Line pages.    

Oracle reference: 33883248

Steps to Enable

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

Intrastat

Print Country of Origin for Northern Ireland Intrastat Dispatches

As part of Great Britain's exit from the European Union (EU), updated Intrastat regulations clarify the different country codes to use when dispatching goods from Northern Ireland or Great Britain. To comply with this guidance, the Intrastat Collection Report now prints the country of origin as XI when goods are dispatched from Northern Ireland. This change is only applicable to the CSV file generated after running the Export Intrastat Collections process. The country of origin on the Manage Intrastat Transaction page continues to show United Kingdom for dispatches from Northern Ireland and Great Britain.

This feature ensures that the correct country code is printed on your Intrastat report when dispatching goods from Northern Ireland.

Steps to Enable

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

Tips And Considerations

The sales order dispatch transaction from Northern Ireland to a European Country is collected by Intrastat Collections.

Sales Order Dispatch Transaction from Northern Ireland

The Country of Origin appears as XI in the Print Intrastat Collections report for the above sales order dispatch transaction from Northern Ireland to a European Country.

Print Intrastat Collections Report

The Country of Origin appears as XI in the CSV file generated by the Export Intrastat Collections process for the above sales order dispatch transaction from Northern Ireland to a European Country.

Export Intrastat Collections

Key Resources

  • Watch the Print Country of Origin for Northern Ireland Intrastat Dispatches demo.
  • Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center.

Role And Privileges

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:
    • Tax Manager (ORA_ZX_TAX_MANAGER_JOB)
  • Users who are assigned configured job roles that contain these privileges are able to access this feature:
    • Print Intrastat Transactions (JMF_PRINT_INTRASTAT_TRANSACTIONS_PRIV_OBI)
    • Export Intrastat Transactions (JMF_EXPORT_INTRASTAT_TRANSACTIONS_PRIV_OBI)

Cost Management

Use Periodic Average Costing to Value Inventory

Use the periodic average cost method to value inventory by including all known period expenses, invoices, and other adjustments at the end of the period.

SET UP PERIODIC AVERAGE COSTING

To set up periodic average costing, you must complete the following tasks:

  1. Create a cost book for periodic average costing.
  2. Map new cost book to a cost organization.
  3. Create a cost profile with a cost method of periodic average.

Create Cost Book for Periodic Average Costing

The periodic average cost method applies to all items for a combination of cost organization and cost book. To create the new cost book for periodic average costing, complete the following steps:

  1. In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials offering and the Cost Accounting functional area.
  2. Click the Manage Cost Books
  3. Click Add Row.
  4. Enter a cost book name and description.
  5. Select Periodic Average Cost.

The following figure illustrates the Manage Cost Books page with the Periodic Average Cost option selected.

Create Periodic Average Cost Book on Manage Cost Books Page

Map Cost Book to Cost Organization

After you create your cost book for periodic average costing, you must map it to a cost organization.

  1. In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials offering and the Cost Accounting functional area.
  2. Click the Manage Cost Organization Relationships.
  3. Click Add Row.
  4. Select the cost organization you want to map to the periodic average cost book.
  5. In the Inventory Organizations area, map the inventory organizations that you would like to map to this cost organization.
  6. In the Relationships area, click the Cost Books.
  7. Click Add Row.
  8. Select the periodic average cost book, enter the required details including the ledger, first open period, and so on.
  9. Click Save and Close.

Depending on the ledger associated with the relationship, the cost book is primary, secondary, or ledgerless.  Ledgerless books are used for analysis purposes only. Only one period can be open for a periodic average cost book. You can open the next period once you address all period end validations and close the current period.

The following figure illustrates a periodic average cost book mapped to a cost organization.

Periodic Average Cost Book Mapped to Cost Organization on Manage Accounting Cost Organization Relationships Page

Create Cost Profile with Periodic Average Cost Method

Once you have created a cost book and a cost organization relationship, you must create a new cost profile with the periodic average cost method.

  1. In the Setup and Maintenance work area, select the Manufacturing and Supply Chain Materials offering and the Cost Accounting functional area.
  2. Click the Manage Cost Profiles.
  3. Click Create.
  4. Complete all the required fields.
  5. Select Periodic average for the cost method.
  6. Click Save and Close.

All periodic average cost book items must have the periodic average cost method selected. Only cost profiles that have a cost method of periodic average display in the Default Cost Profiles and Item Cost Profiles pages for periodic average cost books. Periodic average costs are calculated and maintained for a cost organization or a combination of cost organization and inventory organization. Because of this, the valuation structures you map to a cost profile with a periodic average cost method must be either at the cost organization or cost organization and inventory organization level.

The following figure illustrates a new cost profile with a periodic average cost method.

Cost Profile with Periodic Average Cost Method on Create Cost Profile Page

PERIODIC AVERAGE COSTING LOGIC

The periodic average cost is calculated using the following formula

Prior Period PAC * Opening Qty) + Sum of Current Period Cost Owned (Transaction Cost * Transaction Quantity) +  Adjustments

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                                (Opening Qty + Sum of Current Period Cost Owned Transaction Quantity)

Periodic average costs are calculated by adding all receipts (referred to as cost-owned transactions) and adjustments for a period.  These periodic average costs are applied to transactions that require a cost (referred to as cost-derived transactions).

You run the Create Cost Accounting Distributions process for a combination of a cost organization, a cost book, and a period that is either in Open or in Pending Close status. You can run the Create Cost Accounting Distributions process as many times as necessary in a period.  If there are new transactions or new resource rates or overheads when you run the process, all the existing cost calculations and distributions are discarded and new costs and distributions are created. Once the period has a pending close status, you can’t transfer new inventory transactions to Oracle Cost Management. When the period is closed, all the costs and distributions are frozen and you can run the Create Accounting process to create the accounting entries for the period. Note that you can only run the accounting process after the period is closed.

The following figure illustrates the logic of periodic average costing.

Cost Processing and Period End Processing When Using Periodic Average Cost

CONSIDERATIONS FOR PERIODIC AVERAGE COSTING

The following sections describe important considerations about how periodic average costing works with specific features and functionality.

Overhead Rules

Periodic average costing helps you to follow a full absorption cost method by providing tools and analysis that ensure that period expenses are fully absorbed. Full absorption is made possible by specifying the overhead rates and resource rates that can be modified during the accounting period.  You define overhead rules to apply to different kinds of supply chain transactions on the Manage Accounting Overhead Rules page. You can specify a period from which the rates are effective and can edit or delete the rates anytime during the period. Any changes are processed the next time you run the cost processor. You can use the Overhead Absorption Summary or Details OTBI report to review the overhead absorbed and make changes to the overhead rates if the period is not closed yet. You can’t change the overhead rates once the period is closed or final closed. The rates get carried forward to the next period. If you would like to change the rates for some of the rules, you can create a new revision by manually inserting a new row. Alternatively, you can use the Create Rule Revisions in Bulk option to change all rules that match specific criteria in an open period. You can also use the Cost Accounting Overhead Rules REST API to manage overheads for periodic average cost books. For more information, see the Cost Accounting Overhead Rules REST Endpoints topic in the REST API for Supply Chain Management Cloud guide.

The following figure illustrates overhead rules that are effective for a periodic average cost book.

Overhead Rules for Periodic Average Cost Books in Manage Accounting Overhead Rules Page

Resource Rates

Resource rates are created by defining a scenario that is effective from a specific period.  You can create only one scenario for a combination of cost organization, cost book, and period and you can edit it anytime during the period. Use the Resource Absorption Summary and Details reports to review the total resource costs absorbed in a period and make changes to the resource rates as long as the period isn’t closed. The resource rates are automatically available in the next period and are effective until you publish new rates. The resource rates can also be created and managed through the Manage in Spreadsheet feature.

The following figure illustrates resource rates created for a periodic average cost book.

Resource Rates Published for Periodic Average Costing

Cost Adjustments

Cost Adjustments let you change the cost of an item by changing the opening cost or by adding a value adjustment. The adjustments can be created from the Manage Periodic Average Cost Adjustments page or through the Periodic Average Cost Adjustments REST service. The Opening Cost Adjustment is used to override the opening cost of an item (cost of the item in the prior period) and can’t be edited once you have run the cost processor. Value adjustments can be used when you want to add a lump-sum adjustment, such as a rebate, and can be modified as long as the period isn’t closed.

The formula below shows the impact of the opening cost adjustment and value adjustment for periodic average costing.

(New Prior Period PAC * Opening Quantity) + Sum of Current Period (Transaction Cost * Transaction Quantity) + Value Adjustments

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

                                  (Opening Quantity + Sum of Current Period Transaction Quantity)

The following figure illustrates adjustments created for periodic average costing.

Create Value Adjustments and Opening Cost Adjustments Through the Periodic Average Cost Adjustments Page

The following adjustments are created when you run the cost processor:

  • Acquisition Cost Adjustments, when the purchase order receipt cost and the actual acquisition cost differ due to changes such as invoice price variances, changes in landed costs, and so on.
  • Product Cost Adjustments, when the actual work order cost is different from the cost used for provisional completions costed in a different period. Product cost adjustments aren’t created if the product completion and work order close are in the same period.
  • Variance Adjustments, to prevent the periodic average cost for a period from becoming negative. If either the value or the quantity in the periodic average formula becomes negative, then the periodic average cost can become negative. To prevent this, the cost processor creates a variance to ensure that the cost becomes zero and this cost is used for all cost-derived transactions in that period.

Period End Processing

For a periodic average cost book, the lifecycle of a period is illustrated in the following figure. As described earlier, you can have only one period in open, pending close, or closed status and you need to mark the period as Final Closed to be able to open the next period.

Period End Processing

The period end validation process is started automatically when you change the period status to either pending close, close or permanently closed and it validates if the period's transactions are processed successfully and if the overhead rates and resource rates are correctly processed for all transactions. You can run the period end validation manually anytime during the period to proactively uncover issues and fix them rather than wait until the end of the period. The Create Accounting Events process stages the accounting events when the period is closed. Once the period is closed, you can run the Create Accounting process in draft or final mode.

Reports and Analytics

Existing pages used to analyze items, such as item costs, gross margin, inventory valuation, and cost distributions have been updated to include periodic average item costs and distributions. Similarly, seeded reports, such as Inventory Valuation, In-Transit Valuation, and Work in Process Inventory Valuation have been updated to include periodic average information.

The following figure illustrated the Review Item Costs page with periodic average costing information.

Review Item Costs Page with Item Costs Calculated Using Periodic Average Cost Method

The following reports and analytical capabilities are available to support periodic average costing:

Periodic Average Cost Summary and Detail BI Publisher report to audit the costs calculated

Use the Periodic Average Cost Report to Audit and Analyze Periodic Average Costs

Overhead Absorption Summary and Details OTBI report to see overhead costs absorbed in the period

Use the Overhead Absorption Summary and Details Reports to Analyze the Overheads Absorbed for a Period

The periodic average cost method helps address regulatory and organizational requirements to support full absorption costing. It also helps smooth the impact of significant price changes due to currency or other external factors that occur in a period.

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

 The Opt-In becomes permanent when you associate a periodic average cost book with a cost organization.

Offering: Manufacturing and Supply Chain Materials Management Opt-in never expires.

Tips And Considerations

  • All items in the periodic average cost book use the periodic average cost method.
  • In a periodic average cost book, only one period can be open at a time. Once the current period is closed, the next period can be opened.
  • The Transaction Date Validation Enabled inventory profile has been updated to prevent new transactions from being created in a Pending Close period. You can create transactions in open or never opened periods if this profile option is set to validate cost accounting periods. As before, this profile considers the status of the primary cost book only.
  • For periodic average cost organizations and cost books, we recommend that you enable the General Ledger option "Prevent General Ledger Period Closure When Open Subledger Periods Exist" to ensure that general ledger periods can’t be closed before the costing period is closed.
  • The overhead rates, resource rates, and user cost adjustments can be edited several times during the period as long as the period is open or pending close. Once a period is closed or final closed, the rates and adjustments can’t be changed. The opening cost adjustment created for an item and period can’t be edited once it has been cost processed.
  • The overhead rates and resource rates can be defined to be effective from a specific period and are automatically available for subsequent periods until you create and publish a new version.
  • You can only create one scenario (used to manage resource rates and standard costs) for a combination of cost organization, cost book, and period and can edit it anytime during the period.
  • While defining a run control in the Create Cost Accounting Distributions process for a periodic average cost book and cost organization, ensure that you select the Automatically Update Period on Run Control to continue using the same run control for subsequent periods. Once a period is closed, the run control is updated with the next open period and this eliminates the need to create run controls for each period.
  • All in-transit transfers and direct transfers (across inventory organization)  will be costed based on prior period cost and hence are considered as cost owned transactions. If a prior period cost is not available, you can create a new cost by using the opening cost adjustment.
  • Product completions of work orders are done based on the provisional completion option selected in the cost profile. Currently, standard costs and prior period costs are the two options available.
  • If you need to adjust the cost of a specific receipt, you can use the Receipt Cost Adjustments option on the Manage Cost Adjustments page and REST service. This option only works for cost-owned receipts such as purchase order receipts but is not applicable for product completions.
  • You only can run the Create Accounting process when the period is closed or final closed. You can run the Create Cost Accounting Distributions process anytime during the period to calculate item costs, overhead absorption, inventory valuation, and gross margin information.

Key Resources

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

Role And Privileges

  • Users who are assigned to these predefined job roles are automatically able to access this feature to define a new profile:
    • Applications Implementation Consultant
  • 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:
    • Manage Periodic Average Cost Adjustments for creating/editing/deleting periodic average cost adjustments through the UI or REST

Use Additional Subledger Accounting Sources in Cost Accounting

Configure your subledger accounting rules and mapping sets for sales order issue event class for the cost of goods sold recognition and trade sales issue transactions in the subledger accounting using these additional sources.

  • Ship-to party identifier represents the Ship-to party of the Sales order transaction
  • Ship-to party site identifier represents the Ship-to party site of the Sales order transaction
  • Ship Party Site Attribute represents the Descriptive Flex Fields associated with the Ship-to party site of the Sales order transaction
  • Shipment Line Source Attribute represents the Source Descriptive Flex Fields related to the Shipment Line
  • Shipment Line Standard Attribute represents the Standard Descriptive Flex Fields related to the Shipment Line
  • Sold-to party identifier represents the Sold-to party of the Sales order transaction
  • Bill Customer Site Attribute represents the Bill-to Customer associated with the Sales order transaction
  • Bill Party Site Attribute represents the Descriptive Flex Fields related to the Bill-to Party Site

For projects and tasks, we have added the following subledger accounting sources:

  • Project Attribute Number represents the Project Header Descriptive Flex Fields attributes
  • Task Attribute represents the Project Task Descriptive Flex Field attributes
  • Project Expenditure Organization Identifier represents the Project Expenditure org
  • Project Owning Organization Identifier represents the Project / Task owning org

The subledger accounting sources for projects can be used for the following event classes as applicable:

  • Acquisition Cost Adjustment
  • Consigned Cost Accounting
  • Consigned Cost Adjustment
  • Consigned Ownership Change Delivery
  • Consigned Direct InterOrg Transfer
  • Consigned Intra Organization Transfer
  • Cost Adjustment
  • Direct Interorganization Transfer
  • Global Procurement
  • Internal Drop Shipment
  • In-Transit Interorganization Transfer
  • Intraorganization Transfer
  • Invoice Price Clearing
  • Miscellaneous Transaction
  • PO Delivery into Inventory
  • Sales Order Issue
  • Trade Cost Accounting
  • WIP Material Transaction

Additional sources help result in more accurate account derivations.

Steps to Enable

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

Tips And Considerations

  • To determine if the sources are mapped to the event class that you want to use, go to - Setup and Maintenance work area > Setup: Manufacturing and Supply ChainMaterials Management offering- Cost accounting area- Manage Subledger transaction Objects task- Select the event class and click on View source assignments.

  • To use values captured in Oracle Fusion Cloud Order Management fulfillment line extensible flexfields (EFF), map these sales order fulfillment line EFF attributes to shipment line source descriptive Flexfields segment using the service mapping provided in Oracle Order Management (Document ID: 2663219.1).

Key Resources

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

Role And Privileges

  • 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

Selected Cost Management Bug Fixes in This Update

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

Warning Message for Operations in Work Definitions That Don’t Have Associated Components or Resources

With this update, you might see this warning message on the View Scenario Exceptions page: The work definition snapshot is incomplete. This message is regarding operations in active work definitions that don’t have any associated components or resources. This helps you correct any oversight by adding components or resources to these operations and running the cost rollup again. However, if you have scenarios for your business to use empty operations in work definitions, you can ignore this warning message. The costs of your make items won’t be impacted with this change.

Oracle reference: 33909871

Steps to Enable

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

Fiscal Document Capture

Process a Complementary Fiscal Document for a Bookkeeping Fiscal Document

Fiscal documents that don't require generating transactions in Oracle Payables or Oracle Cost Management are imported, processed, and captured using bookkeeping fiscal flow for tax validation and fiscal compliance. This new fiscal process supports capturing price or quantity corrections for bookkeeping fiscal documents you recorded previously.

The three variations in the complementary fiscal documents include:

  • Price complementary for any corrections related to price on the original fiscal document
  • Quantity complementary for any quantity related corrections
  • Tax complementary for any difference in the tax amount

This enhances the automatic import and processing of electronic fiscal documents for fiscal flows that don't match purchase orders or shipments, and for when the fiscal documents are for fiscal reporting purposes only.

Steps to Enable

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

Tips And Considerations

You need to set the bookkeeping complementary fiscal flow as active in the Manage Fiscal Flows page before importing any complementary fiscal documents that are for fiscal reporting purposes only.

Manage Fiscal Flows

Key Resources

  • For more information about this feature, see the Using Fiscal Document Capture Guide, available on the Oracle Help Center.

Role And Privileges

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