Update 21A

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
27 AUG 2021	Supply Chain Financial Orchestration	Use External Ship-to Locations and Internal Ship-from Locations in an Intercompany AP Invoice	Updated document. Added opt in expiration details.
27 AUG 2021	Supply Chain Financial Orchestration	Use Location of Final Discharge in an Intercompany AP Invoice	Updated document. Added opt in expiration details.
26 FEB 2021	Cost Management	Other Cost Management Changes in This Update	Updated document. Added a section.
29 JAN 2021	Intrastat Reporting	Update Intrastat Reporting for the United Kingdom's Exit from the European Union	Updated document. Added a backported feature.
18 DEC 2020			Created initial document.

Overview

This guide outlines the information you need to know about new or improved functionality in this update, and describes any tasks you might need to perform for the update. Each section includes a brief description of the feature, the steps you need to take to enable or begin using the feature, any tips or considerations that you should keep in mind, and the resources available to help you.

Security and New Features

The Role section of each feature identifies the security privilege and job role required to use the feature. If feature setup is required, then the Application Implementation Consultant job role is required to perform the setup, unless otherwise indicated. (If a feature doesn't include a Role section, then no security changes are required to use the feature.)

If you have created job roles, then you can use this information to add new privileges to those roles as needed. For details about how to compare your configured job roles to predefined job roles and add security artifacts to your configured job roles, see the Security Console and Roles and Role Assignments chapters in the Oracle SCM Cloud: Securing SCM guide on the Oracle Help Center.

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.

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

Cross-Product Enhancements

Link to SCM Application Pages Using Deep Links

In this update, Oracle Supply Chain Management Cloud delivers new deep links that provide easy navigation directly to application pages without using the menu structure. You can use these links in a variety of ways, such as in business intelligence reports, notifications, and third-party application pages.

New deep links in the update are listed by product:

• Supply Chain Collaboration
  • Manage Supply Collaboration Network (COLLABORATION_RELATIONSHIP,EDIT)

• Inventory Management
  • Review Completed Transactions
  • Inventory Pending Transactions
  • SSP Manage Receipts
  • View Receipts
  • Manage Lots
  • Manage Serial Numbers
  • Create ASN
  • Manage Movement Requests
  • Create ASBN
  • Manage Inbound Shipments - Shipment
  • Manage Inbound Shipments - Purchase Order
  • Receive Expected Shipments - Purchase Order
  • Receive Expected Shipments - ASN
  • Receive Expected Shipments - Transfer Order
  • Receive Expected Shipments - In-Transit Shipment
  • Receive Expected Shipments - RMA
  • Manage Transfer Order
  • Manage Shipment Lines
  • Edit Shipment

• Channel Revenue Management
  • Manage Customer Claims (CUSTOMER_CLAIM,NONE)
  • Customer Claim (CUSTOMER_CLAIM,EDIT)

• Manufacturing
  • Work Order (WIE_WORK_ORDER, VIEW)
  • Work Order (WIE_WORK_ORDER, EDIT)
  • Exception (WIE_PRODUCTION_EXCEPTION,EDIT)
  • Work Definition (WIS_WORK_DEFINITION,EDIT)
  • Edit Resource (WIS_RESOURCE,EDIT)

When you add deep links to reports or third-party application pages, users can simply click those links to go directly to the application pages they need to use, without any additional clicks or navigation. When a user clicks a deep link, that user's security assignment is honored; that is, users can access application pages only if they're assigned a job role that allows them access.

Steps to Enable

You can find all of the available deep links in the Deep Links work area. Some deep links, such as those assigned the NONE action, are ready to use as is. Other deep links, such as those assigned the EDIT action, require you to edit the link details before you can add the deep link to a report or third-party application page. Refer to the documentation listed in the Key Resources section for details and instructions.

Key Resources

For details about how to work with deep links, refer to these books on the Oracle Help Center:

• Oracle Applications Cloud: Configuring and Extending Applications
• Oracle SCM Cloud: Implementing Common Features for SCM

Role Information

You have a couple of options for giving people access to the Deep Links work area, 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 the Deep Links work area:

• Application Developer (FND_APPLICATION_DEVELOPER_JOB)
• Application Implementation Administrator (ORA_ASM_APPLICATION_IMPLEMENTATION_ABSTRACT)
• Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB)
• Procurement Application Administrator (ORA_PO_PROCUREMENT_APPLICATION_ADMIN_JOB)
• Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

Users who are assigned configured job roles that contain this privilege are able to access the Deep Links work area:

• View Administration Link (FND_VIEW_ADMIN_LINK_PRIV)

If you're using deep links specifically for reports, here are the privileges you need:

• For Business Intelligence Publisher:
  • BI Author Role (BIAuthor)
  • BI Consumer Role (BIConsumer)
  • BI Administrator (BIAdministrator)

• For Oracle Transactional Business Intelligence (OTBI):
  • BI Author Role (BIAuthor)
  • BI Consumer Role (BIConsumer)

Validate Unit of Measure Conversion Changes

Changes to a conversion for a unit of measure will now validate whether the change affects open transactions in Oracle Inventory Management Cloud or Oracle Cost Management Cloud.

Prior to this update, changes to the unit of measure standard conversion were not validated.  A warning was issued, but if changes were made by a user after the transactions were made with it, the change to the unit conversion could require a data fix.

With this change, if the unit of measure is not being used by open transactions in  Inventory Management, then the validation will succeed and changes to the conversion will trigger the existing warning. If the unit of measure is being used by any open transactions in Inventory, the user will be shown an error explaining that the change would be destructive due to open transactional data, and the update will not be permitted.

Steps to Enable

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

Check Subinventory and Supplier Schedules in Calculating Shipping and Receiving Dates

Check subinventory and supplier schedules when calculating shipping and receiving dates. Shipping and receiving dates that use transit times based on warehouse locations first search for inventory organizations, and then search for subinventories with the location, if no organizations are found. Transit times using a supplier address now search for supplier site and then supplier schedules that you set up in the Manage Transportation Schedules task when calculating shipping and receiving dates.

Anticipated shipping and receiving dates are used in Oracle Supply Chain Planning Cloud, Oracle Procurement Cloud, and Oracle Receiving Cloud applications. When the destination or origin of a transfer or shipment can be tied to a schedule, that schedule is used to adjust the calculated ship or receipt date, if the schedule shows it to be on a nonworking day of the week.

With this update, if the origin or destination is a warehouse location, additional effort is made to find the corresponding subinventory that uses the location to find the schedule if no warehouse with the location is found.  In addition, if you have defined shipping or receiving schedules for a supplier in the Manage Transportation Schedule task, any transit times using these as external supplier addresses will use the schedule in the calculation of anticipated ship or delivery dates.

Steps to Enable

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

Project-Driven Supply Chain

Project-Driven Supply Chain is an end-to-end, integrated solution across the Oracle Supply Chain Management and Project Management Cloud applications.  This solution is designed to support various business processes of manufacturing and asset-intensive companies.

You can use the Project-Driven Supply Chain solution to manage your supply chain processes in the context of projects without creating separate organizations for each project. You can also capture supply chain costs as project expenditures.

Accept Project-Specific Customer Returns

After shipping project-specific material to your customer, there’s always a chance that they might need to return some or all of those goods. If this happens, you need the return order to carry the specific project details, and the costs need to be credited appropriately to the project.

You can now create a return sales order with project and task details, receive the goods back into project-specific inventory, and receive a credit back to the project when appropriate.

The return flow begins with the creation of a referenced or unreferenced return sales order in Oracle Order Management Cloud. A referenced return sales order copies the project and task details from the original sales order. In contrast, an unreferenced return sales order requires the order entry clerk to enter those details manually. When creating a referenced return sales order, you can remove the project and task details before submitting the order if the project is no longer valid or you want to return the goods to common inventory. To allow the removal of the project and task from a referenced return sales order, set the Allow User to Remove Project Details on Reference Returns parameter to Yes. After the return sales order is submitted and released to your warehouse for receiving, you can no longer update the project or task attributes at any point in the return.

Intercompany Referenced RMA

When receiving returned goods into inventory, the project and task details you entered on the sales order are displayed during receipt and put away if the organization is enabled for inventory tracking by project. Furthermore, the on-hand quantity carries the project and task segregation after put-away. Suppose your organization isn't enabled for inventory tracking by project. In this case, the project and task details aren't displayed during receipt or put away and the on-hand quantity is added to your common inventory. If no project or task details are provided on a return sales order, the on-hand quantity is added to common inventory regardless of whether or not the organization is enabled to track inventory by project.

Receive and Put Away RMA in a Project-Tracked Inventory Organization

For non-intercompany returns to project inventory, there’s no notification to the project because there’s no additional cost to the project. You need to set up your business process to issue a credit to the customer from Project Billing. For intercompany returns to project inventory, a negative expenditure is interfaced in the context of the selling profit center. A positive expenditure is interfaced to the project in the context of the receiving entity. This provides you with the ability to track the project expenditure in the appropriate expenditure organizations.

Note that the accounting line type of project clearing is used instead of deferred return material authorization (RMA) gain or loss for the return receipt. However, if your project type isn't enabled for cost collection, the deferred RMA gain or loss accounting line type is used.

Project Clearing Accounting Line Type is Used for Trades Sales Return

Watch a Demo

This feature enables you to return project-specific material directly to your organization and ensures the correct charges are credited back to your projects upon return of goods. The on-hand received from the customer is segregated by project and task after the put-away transaction, thereby maintaining the project valuation. The receipt of RMA into project inventory streamlines the project cost collection for intercompany RMA receipts.

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

You'll need to enable opt-in for the Accept Project-Specific Customer Returns feature to receive project-based return orders into project inventory. But first, in the Offerings work area, you'll need to enable the Project-Driven Supply Chain feature for the Manufacturing and Supply Chain Management offering.

Opt in controls how project attributes are defaulted from the original sales order for referenced returns. When opt-in isn't enabled, the original sales order's project attributes won't be defaulted on the referenced return order; however, you can enter the project details manually. The project-based return order is received in common inventory when opt-in isn't enabled.

Accept Project-Specific Customer Returns

The Allow User to Remove Project Details On Referenced Return parameter has been introduced to allow removal of project details before order submission. The parameter values are Yes or No. The default value of this parameter is No, which indicates that the project details that have defaulted from the original sales order can’t be removed.

Allow User to Remove Project Details On Referenced Return

Tips And Considerations

• The project attributes from the original sales order won't be defaulted on a referenced return order when opt-in isn't enabled, but you can enter the project details manually.
• The project-based return order is received in common inventory when opt-in isn't enabled.
• You can create a your own orchestration process with line selection criteria to skip sending lines to accounts receivable when the project indicator value is Y.

Key Resources

• Watch Accept Project-Specific Customer Returns Readiness Training
• Oracle Supply Chain Management Cloud: Using Inventory Management guide, available on the Oracle Help Center.

Role Information

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:

• Order Entry Specialist (ORA_FOM_ORDER_ENTRY_SPECIALIST_JOB)
• Order Manager (ORA_DOO_ORDER_MANAGER_JOB)
• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
• Receiving Agent (ORA_RCV_RECEIVING_AGENT_JOB)
• Cost Accountant (ORA_CST_COST_ACCOUNTANT_JOB)
• Project Manager (ORA_PJF_PROJECT_MANAGER_JOB)
• Project Billing Specialist (ORA_PJF_PROJECT_BILLING_SPECIALIST

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

• Create Receiving Receipt by Web Service (RCV_CREATE_RECEIVING_RECEIPT_WEB_SERVICE_PRIV)
• Provide Receiving Transaction Details Web Service(RCV_PROVIDE_RECEIVING_TRANSACTION_DETAILS_WEB_SERVICE_PRIV)

Inventory Management

Maintain Detailed Reservations for Make, Buy, and Transfer Supply Orders

When purchasing or making goods for a specific customer order, you need to guarantee they get exactly what they ordered. In some cases, your customer's order might include special instructions or specific configurations that you’re obligated to honor. Similarly, if you reserve incoming supply to a specific priority customer order, you must ensure the items stay tied to that order after they’re in inventory.

In these circumstances, you need a way to help make sure that the exact item made or procured for this customer is actually shipped to them. You can now maintain detailed reservations to customer orders for items using the back-to-back process or incoming supply that you manually reserved to the order.

After the goods are completed or received, the reservation adjusts from the incoming supply document to the on-hand quantity at the most detailed level possible. Items not using serial or lot control are detailed to the subinventory and locator level, while lot or serial-controlled items are detailed to the subinventory, locator, and lot or serial level. If using project-driven supply chain processes, the project and task attributes are included in the reservation as well.

Watch a Demo

This feature ensures that when you reserve a specific supply document to a demand order, either manually or using the back-to-back process, the actual goods you make or procure with the supply order are used to fulfill the demand. The creation of detailed reservations for the make, buy, and transfer supply orders helps ensure that the exact item, lot, or serial number made or procured for the customer is actually shipped to the customer, thereby eliminating returns and enhancing customer satisfaction. With this feature, the reservation is detailed to the serial number level after the purchase order or transfer order is delivered or the work order is completed. This feature ensures that pick release creates picks for the same serial numbers that have been reserved to the sales order. After the shipment is confirmed, the same serial numbers are shipped to the customer. The reservation is automatically updated when the material received on a supply order reserved to a sales order is returned back to the supplier or to an internally sourced organization or to a work order to fix a product defect.

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 the sales order is manually reserved to on-hand after the supply document is received or completed, the reservation isn't automatically updated.

Key Resources

• Watch Maintain Detailed Reservations for Make, Buy and Transfer Supply Orders Readiness Training
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management Guide, available on the Oracle Help Center.

Role Information

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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_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:

• Manage Inventory Reservation Web Service (INV_MANAGE_INVENTORY_RESERVATION_WEB_SERVICE_PRIV)

Reserve Unreleased Orders

Unforeseen emergencies or natural disasters can generate demand spikes that quickly drive your on-hand quantities well below what's required to meet demand, or possibly even down to zero. When this happens, you need a way to reserve supply manually for priority orders before releasing the order to your warehouse. Now, on the Manage Reservations and Picks page, you can manually reserve supply before the sales order is released to the warehouse for shipping. You can also manually reserve transfer orders that are routed through Oracle Order Management Cloud.

The feature allows you to:

• Query reservations for unreleased orders on the Manage Reservations and Picks page. Use the new Order Interface Status query parameter to query these orders.

• Manually reserve unreleased orders with various supply types, such as purchase order, work order, etc. on the Create Reservations page.

• Purge excess reservations for unreleased orders using the Purge Excess Inventory Reservations Process scheduled process.

• Use the enhanced Inventory Reservations REST resource to manage reservations for unreleased orders.

Manage Reservations and Picks

Manage Reservations and Picks

Create Reservations

Purge Excess Inventory Reservations Process

Watch a Demo

Let’s say a particular item your organization manufactures and sells to customers has a long lead time. An unexpected spike in demand causes you to run out of on-hand quantity, but a priority customer order just came in. Luckily, you already have an open work order to replenish the item, and you want to ensure the almost completed work order fills this customer order. Before releasing the customer order to your warehouse for shipping, you can manually reserve the pending work order to the scheduled sales order for efficient fulfillment.

This feature helps you effectively manage reservations of incoming supply when on-hand quantity unexpectedly runs out. You can now efficiently and proactively plan your supply chain by reserving supplies against priority demands before releasing the order to your warehouse to manage unexpected changes. As a result, you'll have increased control of the fulfillment 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 21C

Tips And Considerations

• Schedule sales orders to reserve unreleased orders manually using the Manage Reservations and Picks task.
• The Inventory Reservations FBDI and ADFdi don't support reservations of unreleased orders.
• Partial manual reservations of unreleased orders against different supply types is supported.
• The Review Item Supply and Demand page doesn't support unreleased order demand.
• The Transfer Reserved Quantity action on the Manage Reservations and Picks page is disabled for orders awaiting release to shipping or inventory.
• You can't edit reservations for the canceled or unscheduled order lines of unreleased orders.

Key Resources

• Watch Reserve Unreleased Orders Readiness Training
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center.

Role Information

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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)   
• Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)

Users who are assigned configured job roles that contain this privileges are able to use this feature to purge excess reservations:

• Purge Excess Inventory Reservations Process (INV_PURGE_EXCESS_INVENTORY_RESERVATIONS_PROCESS_PRIV)

Use Dynamic Creation of Account Combination for Inventory Transactions

When performing transactions in your warehouse, you might run into situations where the general ledger account combination you need to use doesn't exist. For instance, let's say your organization uses a product code in the chart of accounts, and a recent shipment of a new product just came into your warehouse. Now, you need to issue some of this product out to various departments using a miscellaneous issue. However, when you try to perform the transaction, you find that the general ledger account combination doesn't exist for every department. Prior to this update, you had to contact the accounting department and ask someone to create this combination for you.

Now, any user that can create a miscellaneous transaction or movement request issue can dynamically create general ledger account combinations, as long as your organization allows the dynamic insertion of account combinations within the account structure.

This feature allows you to quickly and easily complete transactions without relying on other departments in your organization to create general ledger accounts. This saves you valuable time when performing routine warehouse transactions.

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

Opt In to Use Dynamic Creation of Account Combination for Inventory Transactions

After you opt in, you must enable Dynamic combination creation allowed for the Edit Key Flexfield structure instance:

1. In the Setup and Maintenance work area, on the Tasks panel tab, click Search. 
2. Enter Manage Key Flexfields in the search field and click Search.
3. Click Manage Key Flexfields in the Name column of the search results, and the Manage Key Flexfields page is displayed. 
4. In the Module field, select General Ledger and click OK. (The Module Type is APPLICATION.)  
5. In the Search Results section, select the General Ledger application and click Manage Structure Instances.
6. In the Structure Name field, select the name of the structure (for example, OPERATIONS_ACCOUNTING_FLEX) and click Edit.
7. In the Search Results section, select the instance on which you want to enable dynamic account combination and click Edit. 
8. Select the Dynamic combination creation allowed check box and click Save.

Enable Dynamic Combination Creation

Key Resources

• Watch Inventory Management Consolidated Enhancements Readiness Training
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center.

Role Information

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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)

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

• Create Miscellaneous Transaction (INV_CREATE_INVENTORY_TRANSACTION_MISCELLANEOUS_TRANSACTION_PRIV)

Perform Lot Split, Merge, and Translate Using REST APIs and FBDI

When dealing with goods that are under lot control, there are numerous events that might require you to break, combine, or transform some or all of the goods in a specific lot. For example, a weather event causes damage to your warehouse and spoils only a portion of a lot. The damaged portion of the lot is still usable for some, but not all, of your manufacturing processes. Thus, you need to split this quantity from the original lot and assign new lot numbers to ensure your goods are designated properly for future use. 

Similarly, maybe you regularly combine multiple lots into a single vat before use in downstream processes. When you merge all of these lots into a single vat, you assign a new unique lot number. Finally, in some industries, a chemical reaction process might require that you change the assigned lot number of an item when the process is complete. For example, let’s say you complete a work order for item 123 into lot A. After two weeks, the reaction process is complete, and the lot should change to lot B. This change indicates that the item is ready for the next step. The item itself hasn’t changed, and the additional overhead of a work order just to change the lot number isn’t desired. Additionally, you need the lot history retained. In these scenarios, a work order isn’t required. Now you can perform lot splits, merges, and translations within Oracle Inventory Management Cloud using REST APIs or file-based data import (FBDI).

You can use an inventory lot split transaction to split a single lot into multiple lots. For example, you can split a source lot into a single subinventory or among multiple subinventories. The resultant lots will inherit the lot attributes from the source lot. However, depending on your business requirements, you can change the resultant lot attributes. This feature is particularly useful if you need to change a lot attribute for selected items within a lot.

Inventory Lot Split

You can use an inventory lot merge transaction to merge multiple inventory lots into a single lot. For example, if you have four separate lots with similar characteristics, you can merge them into a single lot rather than maintaining four separate lots. The individual item quantities from the four source lots is summed for the resultant lot. The ability to merge lots reduces overhead for your organization, allowing you to manage the inventory lot as a single unit.

Inventory Lot Merge

You can use an inventory lot translate transaction to translate a single source lot into a single resultant lot via REST APIs or file-based data import (FBDI). For example, you can use a lot translate transaction to correct lots that have been entered incorrectly. Let's say you incorrectly specify lot A when entering a purchase order receipt. You can perform an inventory lot translate transaction to update the resultant lot to lot B. Inventory lot translate is only supported within an item.

Inventory Lot Translate

Three new fields have been introduced on both the Review Completed Transactions and Manage Pending Transactions pages: Lot Transaction Source, Lot Transaction Group, and Representative Lot. The Lot Transaction Source field allows you to identify which inventory lot represents the source lot. The Lot Transaction Group field is a user-defined value that provides you with a way to group your lot transactions. The Representative Lot field is used when performing lot merge transactions. This value in this field indicates which lot in the merge transaction is the representative lot.

Review Completed Transactions

The new split, merge, or translate lots feature lets you change lots dynamically, without the additional overhead of creating a work order or performing extraneous inventory transactions. This feature saves you time and improves operational efficiency.  

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

Enable Opt-In Feature

To use the Perform Lot Split, Merge, and Translate Using REST APIs and FBDI feature, you must configure your item in the Product Information Management work area. 

Here's how to enable your item for lot split, merge, and translate:

1. From the Navigator, click Product Management, and then click Product Information Management.
2. Select Manage Items on the Tasks panel tab.
3. On the Manage Items page, search for your Item.
4. In the Search Results section, click on the item name in the Item column. The Manage Items page is displayed.
5. Click on the Specifications tab.
6. In the Item Organization section, click Inventory.
7. In the Lot Split or Merge section, select Yes in the Lot Translate Enabled field to enable your item for lot split, merge, and translate transactions.
8. Optionally, you can set the Lot Divisible field to Yes, which allows you to perform partial lot split, merge, and translate transactions.

Item Lot Attributes

To enable material status control for a given transaction type, you must enable status control for the respective transaction type.

The Manage Inventory Transaction Sources and Types setup task allows you to Enable Status Control for a given inventory transaction type. This configuration lets you allow or deny inventory lot transactions based on material status.

In the Setup and Maintenance work area, select Manage Inventory Transaction Sources and Types:

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Inventory Management (click Show All Tasks)
• Task: Manage Inventory Transaction Sources and Types

Manage Inventory Transaction Sources and Types

Tips And Considerations

• Lot split, merge, and translate is only allowed when there is available quantity for the item.

• Lot attributes are inherited by the resultant lot and can be overridden if required.

• Both source and resultant lots must have the same value for the inventory tracking attributes.

• Serial number controlled items are supported for lot split, merge, and translate transactions.

• Disabled inventory lots can be reused for lot split, merge, and translate transactions.

• Lot translate to a different item is not supported.

• Consigned inventory is not supported for lot split, merge, and translate transactions.

• If the representative lot is not specified for a lot merge, the lot with the highest available quantity is used.

• Lot split, merge, and translate transactions support multiple transaction units of measure.

• Lot split, merge, and translate transactions support transactions at the inventory locator level.

• Three new columns have been introduced to the Inventory Transaction file-based data import spreadsheet: Source Lot, Lot Transaction Group Name, and Representative Lot.

• Use Current Cost is defaulted to Yes and can’t be changed for inventory lot transactions.

Key Resources

• Watch Perform Lot Split, Merge, and Translate Using REST APIs and FBDI Readiness Training

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

• For more information, refer to the View Inventory Lot Split, Lot Merge, and Lot Translation in Genealogy feature in manufacturing or product lifecycle management for quality management.

Role Information

You have a couple 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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)

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

• Manage Staged Inventory Transaction Web Service (INV_MANAGE_STAGED_INVENTORY_TRANSACTION_WEB_SERVICE_PRIV)

Support Item Transaction Defaults for Additional Transactions

This feature improves inventory transaction processing times by automatically defaulting the subinventory and location for miscellaneous transactions and interorganization transfers. For example, suppose your organization requires an Account Alias Issue transaction to default to a specific subinventory and locator. You can now configure a default subinventory and locator based on the transaction type and item. So, your warehouse personnel won't have to identify and enter that information manually. In addition, this feature prevents data entry errors by applying the defaults automatically. 

Now, you can create item transaction defaults for the following transaction types:

• Account Alias Issue
• Account Alias Receipt
• Account Issue
• Account Receipt
• Direct Interorganization Transfer

Create Miscellaneous Transaction

The ability to define item transaction defaults for these additional transaction types saves you valuable time when performing routine transactions in your warehouse.

Steps to Enable

To use this feature, you must configure the item transaction defaults on the Manger Item Transaction Defaults page:

1. In the Setup and Maintenance work area, go to the Manage Item Transaction Defaults task:

• Offering: Manufacturing and Supply Chain Materials Management
• Functional Area: Inventory Management
• Task: Manage Item Transaction Defaults

2. Select an organization, if one isn't already selected, and click OK.
3. Click Actions > Add and enter the default subinventory and locator for each item transaction type.  Note: When executing an inventory transaction, this setup configuration is used to determine the default subinventory and locator.
4. Click Save.

Manage Item Transaction Defaults

Tips And Considerations

• Item transaction defaults are only applicable for transactions created on the Create Miscellaneous Transaction and Create Interorganization Transfer pages.

• Item transaction defaults are not applicable for transactions created via FBDI or REST services.

Key Resources

• Watch Inventory Management Consolidated Enhancements Readiness Training
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center.

Role Information

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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)

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

• Create Miscellaneous Transaction (INV_CREATE_INVENTORY_TRANSACTION_MISCELLANEOUS_TRANSACTION_PRIV)
• Create Interorganization Transfer (INV_CREATE_INVENTORY_TRANSACTION_INTERORGANIZATION_TRANSFER_PRIV)

Use Query by Example for Cycle Count Subinventory Selection

When creating or updating a cycle count, it can be tedious to scroll through an entire list of subinventories to select which ones you want to include in the count. You need a quick and easy way to search for exactly which subinventory you want to include or remove from your count. Then, you need a quick way to verify that you have made the correct selections or adjustments. Now, you can query by example the Subinventory and Include in Count fields within the Subinventories to Count area when creating or updating a cycle count.

This feature allows you to easily search for subinventories using the query by example search framework. Query by example is displayed as a separate row immediately above the search results table, and you can enable it by selecting the Query by Example action or icon. There are two search attributes available: Subinventory and Include in Count. You can search for selected subinventories to include in your cycle count. The Include in Count column supports the values Yes and No. Yes indicates the subinventory is included in the count, and No indicates the subinventory isn't included in the count. Query by example is supported for both the create and edit cycle count process flows.

Edit Cycle Count

This feature provides you the ability to quickly search for specific subinventories to include in your count when creating or updating a cycle count. It also allows you to easily verify which subinventories you selected to include or exclude in your count.

Steps to Enable

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

Key Resources

• Watch Inventory Management Consolidated Enhancements Readiness Training
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center.

Role Information

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:

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

• Create Cycle Count (INV_CREATE_CYCLE_COUNT_PRIV)
• Manage Cycle Count (INV_MANAGE_CYCLE_COUNT_PRIV)

View Parent Lot, Material Status, and Disabled Columns in the Lot Dimension in OTBI

Oracle Transactional Business Intelligence (OTBI) lets you create ad hoc reports using real-time transactional data from Oracle Cloud Inventory Management to monitor your materials management processes. In this update, you can view additional lot details by adding the new Parent Lot, Material Status, Material Status Description, and Disabled columns to your reports in OTBI. These new columns are now available in the Lot dimension of the Inventory Balance Real Time and Inventory Transactions Real Time subject areas and in the Inventory Details dimension of the Shipping Real Time subject area.

OTBI Reports

The new Parent Lot, Material Status, Material Status Description, and Disabled columns in the Inventory Balances, Inventory Transactions, and Shipping subject areas provide you with additional reporting capability to help you quickly verify lot parameters.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Tips And Considerations

You can add the new Parent Lot, Material Status, Material Status Description, and Disabled columns to your existing reports, or create new reports that use these new columns. For details about creating and editing reports, see the Oracle SCM Cloud: Creating and Administering Analytics and Reports guide on the Oracle Help Center.

Key Resources

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

Role Information

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)

Process Pick Confirm Lines Individually or As a Group Using the Pick Transactions REST Resource

When you're processing a large number of pick confirm lines using the Pick Transactions REST resource, there's always a chance that some of the data you provide on some of those lines isn't correct. When errors occur, it's more efficient if all pick confirm lines with correct data are successfully processed, leaving you only the lines with errors to correct and reprocess. Now you can choose if the pick confirm lines you send using the Pick Transactions REST resource are processed as a group or individually using the RollbackAllLinesOnError object. If the value of the RollbackAllLinesOnError object is yes or not provided, then all pick confirm lines are rolled back and reprocessed even if only one line results in an error. If the value of the RollbackAllLinesOnError object is no, then each line is processed individually, allowing successful lines to complete and requiring you to reprocess only lines with errors. 

For organizations that process a large number of pick confirm lines using the Pick Transactions REST resource, but typically experience relatively few exceptions, this feature provides the flexibility to increase processing efficiency. Processing the lines individually means all successfully validated lines will progress, saving time and effort that you can redirect to managing only the exceptions.

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.

Tips And Considerations

• Use the RollbackAllLinesOnError object, passing yes or no, to indicate which lines to process as a group or individually.

Key Resources

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

Role Information

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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_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:

• Perform Pick Transaction by Web Service (INV_PERFORM_PICK_TRANSACTION_WEB_SERVICE_PRIV)

Relax Restrictions for Item Lot Attribute Changes

When configuring new items in the Product Information Management work area, your business requirements might dictate that you set up item attributes in a specific way. When configuring these item attributes, the decisions you make can significantly impact downstream transaction processing in areas like inventory, receiving, and shipping. Later, if your business requirements change, you might find that you need to adjust some of the item attributes accordingly.

For example, let’s say you set the lot control attribute for an item you purchased from suppliers to full lot control based upon internal control requirements. As time passes, your processes change and you no longer need to track this particular item’s lot information. You verify that there's no on-hand quantity for the item, no other pending transactions, and only some open purchase orders for your suppliers to fulfill. You can now update the lot control, grade control, child lot enabled, and shelf life control attributes for an item as long as you only have pending receiving transactions open for the item.

Relaxing restrictions for changes to item lot attributes improves product usability and provides you with greater flexibility when business requirements change or item attributes are misconfigured.

Steps to Enable

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

Key Resources

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

Role Information

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:

• Product Manager (ORA_EGP_PRODUCT_MANAGER_JOB)

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

• Manage Item (EGP_MANAGE_ITEM_PRIV)

Allow Changes to the Unit of Measure Code

Changes to the code on a unit of measure are now permitted with validation. After creating a unit of measure, if it is determined that the original data is incorrect, changes to the code of the unit will be allowed if the unit is not used by any item in Product Management.

Prior to this update, changes to the unit of measure code value were not permitted after it was saved.  If errors were made by a user, the renaming of the code of the unit of measure could require a data fix.

With this change, if the unit of measure is not yet in use in Product Management by being associated to any item as a primary or secondary unit of measure, nor as an element to any packaging strings, the validation will succeed and changes to the unit of measure code will be permitted.  The user will be alerted if the change would be destructive due to association with any items, and the update will not be permitted.

Steps to Enable

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

Other Inventory Management Changes in This Update

This section includes details about additional changes in this update that can change the way Oracle Inventory Management Cloud works.

Updates to Pending Transactions Restricted

You can no longer update the organization, transaction quantity, and unit of measure attributes, or delete records on the Manage Pending Transactions page for transaction sources defined by the application. These include all transaction sources except account, account alias, inventory, and user defined (which also covers all inventory transactions imported from file-based data import or web services). This change preserves the integrity of completed transactions throughout Oracle Inventory Management Cloud.

Bug reference: 31524773

Ability to Cancel Return Transfer Orders Removed

You can no longer cancel return transfer orders. This applies to execution in the UI, and through the Scheduled Processes work area, file-based data import, and web services. Prior to update 21A, a return transfer order cancelation left incomplete receiving and receipt accounting transactions.

Bug reference: 31484892

Update Transfer Order Destination Location Based on Destination Subinventory Change

For transfer orders interfaced to shipping only, a change to a destination subinventory now results in an update to the destination location. The destination location is updated to the location assigned to the destination subinventory. If there's no specified destination subinventory, it's updated to the location assigned to the destination inventory organization. This applies to execution in the UI, and through file-based data import and web services. Prior to update 21A, the destination location was fixed at the creation of a transfer order.

Bug reference: 31440217

Update Reservation on Return of Purchase Order, Work Order, or Transfer Order

Reservations now automatically update when a purchase order or transfer order that’s manually reserved to a sales order is returned for an item. This applies to all items except for back-to-back items. For a purchase order return, the reservation transfers back to the purchase order. For a transfer order return, the application deletes the reservation for the returned quantity when the quantity is returned back to the source organization. Previously, there were also issues in returning a manually reserved transfer order for serial, lot, and revision-controlled items. You can now return the quantity on a reserved transfer order or purchase order for lot, serial, and revision-controlled items. This update ensures that your reservations are accurate for supply orders manually reserved to sales orders.

Bug reference: 31685563

Shipping

Review Shipment Lines with Missing Inventory Controls

When confirming a shipment, there's a possibility one or more of your shipment lines is missing key details like what subinventory an item is coming from or what serial number is being shipped. While a warning message is displayed informing you that shipment lines are missing key data, the message doesn't specifically tell you what exactly is missing. Now, the Edit Shipment page includes the new Inventory Controls Missing column in which an Alert icon is displayed when key information missing. When you hover over the Alert icon, you'll see a message about exactly what's missing.

Edit Shipment Page - Inventory Controls Missing Column

This new feature provides you with the ability to review the shipment lines on the Edit Shipment page. Upon opening the page, the staged lines are evaluated for missing inventory controls. If an issue is found, an Alert icon is displayed on those lines so that you can quickly locate and review them. Additionally, detailed messages for each missing inventory control are displayed when you hover over this new icon in the new Inventory Controls Missing column in the lines table. You can look at the detailed messages and make the necessary edits on those lines. The staged lines are reevaluated for missing controls and cleared when you save the page. The new Inventory Controls Missing column is hidden by default.

Watch a Use Case Scenario Demo

This feature allows you to quickly identify which shipment lines are missing key information. You can then determine exactly what's missing and update the shipment lines to ensure that your shipment is confirmed without any issues.

In previous updates, you had no easy way to verify that all shipment lines were fully prepped, nor could you be confident that the shipments would confirm successfully. When you received warning messages upon ship confirm on lines with missing inventory controls, you'd have to dismiss the warnings by selecting No. Then you had to laboriously verify every line manually for all inventory controls, depending on the type of the item for that line. This task could take a lot of time if you had hundreds of lines in a shipment. After you manually verified and corrected all lines, you could try confirming the shipment again.

Now, when you navigate to the Edit Shipment page, all shipment lines are evaluated, and an Alert icon is displayed on lines with missing inventory control information. You can hover over the Alert icon to learn more about what inventory control information is missing for the line. Then you can make the necessary edits without the need to verify the inventory controls for each line item manually. After you have edited the lines for missing inventory control information, you can invoke the ship confirm action directly or save the changes to ensure that all lines are no longer missing information. Then you can invoke the ship confirm action again.

Steps to Enable

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

Key Resources

• Watch the Review Shipment Lines with Missing Inventory Controls Use Case Scenario Demo
• Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Management guide, available on the Oracle Help Center.

Role Information

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:

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
• Shipping Manager (ORA_INV_SHIPPING_MANAGER_JOB)
• Shipping Agent (ORA_INV_SHIPPING_AGENT_JOB)

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

• Manage Shipment (WSH_MANAGE_DELIVERY_PRIV)

Other Shipping Changes in This Update

This section includes details about additional changes in this update that can change the way Oracle Shipping Cloud works.

Ensure Shipment's Actual Ship Date is Later than the Picking Transaction Date

The application ensures that the shipment’s actual ship date is later than the picking transaction date of all lines in the shipment. This helps to account for the ownership transfer transactions and issue transactions, and ensures success in costing.

Here are the changes that were implemented to restrict the shipment’s actual ship date:

• Actual ship date field is no longer defaulted
• Actual ship date field accepts only future date and times
• Actual ship date field accepts only values later than the pick transaction date of all lines in the shipment
• If the actual ship date selected is not today, the time component defaults to 11:59:59 PM
• If the actual ship date selected is today, the time component defaults to current time at the time of processing

NOTE: This fix was also delivered in the November monthly update for 20C and 20D.

Bug reference: 31434334

New Status for Shipment Lines That Are Pending for Inventory Processing

After a shipment line is shipped with a shipment, the shipment line transfers to inventory through the creation of an issue transaction. While the inventory issue transaction is pending and awaiting processing, the status on the shipment line now displays as Pending inventory processing. Prior to 21A, the status of the shipment line displayed as Interfaced. This new status helps you notice the shipment lines that are pending for inventory processing. You can review the pending inventory transactions and resolve any processing errors.

Bug reference: 31357054

Receiving

View Trading Partner Item Details, Trading Partner Name, and Trading Partner Type Dimensions in the Receiving Subject Areas in OTBI

Oracle Transactional Business Intelligence (OTBI) lets you create ad hoc reports using real-time transactional data from Oracle Inventory Management Cloud to monitor your materials management processes. In this update, the Trading Partner Item Details, Trading Partner Name, and Trading Partner Type dimensions are now available in the following Receiving subject areas:

• In-Transit Advanced Shipment Notifications Real Time
• In-Transit Interorganization Inventory Transfers Real Time
• In-Transit Shipments Real Time
• Interorganization Receipts Real Time
• Purchase Receipts Real Time
• Receipts Real Time
• Transactions Real Time
• Unordered Receipts Real Time

Receiving - Transactions Real Time Subject Area

Using the Transactions Real Time subject area as an example, the new dimensions allow you to augment your receiving transactional reports with a number of trading partner-related attributes.

The new Trading Partner Item Details, Trading Partner Name, and Trading Partner Type dimensions provide additional reporting capability to help you easily view the details of your trading partner items for receiving-related transactions.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Tips And Considerations

You can add the new trading partner fields to your existing reports or create new reports that use these new fields. For details about creating and editing reports, see the Oracle SCM Cloud: Creating and Administering Analytics and Reports guide on the Oracle Help Center.

Key Resources

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

Role Information

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

• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)

View Manufacturer Name and Part Number When Receiving Goods

When you regularly order the same item from multiple suppliers or distributors, that item’s manufacturer part number might be the only easy and consistent way to identify goods. In this scenario, you need the ability to quickly cross-reference that the goods you’re physically receiving are the same as the goods you’re transacting into inventory. Now, you can view the manufacturer name and associated manufacturer part number as columns on the following pages:

• Self Service Receiving (My Receipts)
  • Receive Items
  • Receive Items - Create Receipts
  • Manage Receipts
  • Manage Receipts - Return Receipts
  • Manage Receipts - Correct Receipts

• Warehouse Receiving
  • Receive Expected Shipments
  • Receive Expected Shipments - Receive Lines
  • Receive Expected Shipments - Receive Line
  • Manage Inbound Shipments - Edit Shipment
  • Manage Inbound Shipments - Edit Shipment Line
  • Create ASN
  • Create ASN - Create ASN Details
  • Create ASBN
  • Create ASBN - Create ASN Details
  • Inspect Receipts
  • Inspect Receipts - Inspect Lines
  • Inspect Receipts - Inspect Line
  • Put Away Receipts
  • Put Away Receipts - Put Away Lines
  • Put Away Receipts - Put Away Line
  • Correct Receipts
  • Correct Receipts - Correct Lines
  • Correct Receipts - Correct Line
  • Return Receipts
  • Return Receipts - Return Lines
  • Return Receipts - Return Line
  • Manage Supplier Returns Without Receipt - Create Supplier Return Without Receipt
  • Manage Supplier Returns Without Receipt - Edit Supplier Return Without Receipt
  • Manage All Lines (Quick Search)

• Supplier Portal
  • Manage Inbound Shipments - Edit Shipment
  • Manage Inbound Shipments - Edit Shipment Line
  • Create ASN
  • Create ASN - Create ASN Details
  • Create ASBN
  • Create ASBN - Create ASBN Details

Additionally, the following REST resources now include the manufacturer and manufacturer part number attributes:

• Lines to Correct
• Lines to Inspect
• Lines to Receive
• Lines to Put Away
• Lines to Return
• Purchase Order Lines for Receiving
• Supplier Returns
• Receipt Advice Lines

Using Receive Expected Shipments as an example, enabling the manufacturer and manufacturer part number on the page provides a convenient way to cross-reference these attributes if labeled on the goods.

Receive Expected Shipments

Watch a Demo

This feature enables you to efficiently view and compare the manufacturer name and associated part number of the goods you’re physically receiving with the goods you’re transacting into inventory. You can also view these attributes when performing other receiving transactions, such as creating ASNs or returning goods.

Steps to Enable

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

Tips And Considerations

• The Manufacturer and Manufacturer Part Number columns are displayed next to the Supplier Item Number on the pages listed above.

• The Manufacturer and Manufacturer Part Number columns aren’t displayed by default, but you can enable them from the View menu.

• If there’s a single value for the Manufacturer and Manufacturer Part Number columns, it's displayed directly in the record.

• If there are multiple values for the Manufacturer and Manufacturer Part Number columns, the Multiple link is displayed in both columns. You can click on the Multiple link in either column to open a window that displays the full list of manufacturers and associated part numbers. The list is displayed in ascending rank order, as defined in the trading partner association, and then alphabetically.

• If the source document line is not a purchase order line, the manufacturer and manufacturer part number are sourced from the item master record in Oracle Product Hub Cloud. You create an item master record in the Product Information Management work area by completing two tasks: create the trading partner item and assign it to an inventory item. The manufacturer and manufacturer part number are sourced from values on the two pages where you complete these tasks.
  • Create the trading partner item on the Manage Trading Partner Items page (select Manage Trading Partner Items from the Task panel tab):
    • Trading Partner Type is Manufacturer
    • Status is Active
    • Current date is between the Start Date and End Date
  • Assign the trading partner item to an inventory item on the Edit Item page (Relationships tab > Trading Partner Items tab):
    • Trading Partner Item Status is Active or null
    • Relationship Status is not obsolete

• If the source document line is a purchase order line, the manufacturer and manufacturer part number are sourced from the purchase order line itself. There is always a one-to-one relationship between the purchase order line and manufacturer data.

Key Resources

• Watch the View Manufacturer Name and Part Number when Receiving Goods Demo
• Oracle Supply Chain Management Cloud: Using Inventory Management guide, available on the Oracle Help Center

Role Information

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:

• Procurement Requester (ORA_POR_PROCUREMENT_REQUESTER_ABSTRACT)
• Advanced Procurement Requester (ORA_POR_ADVANCED_PROCUREMENT_REQUESTER_ABSTRACT)
• Procurement Preparer (ORA_POR_PROCUREMENT_PREPARER_ABSTRACT)
• Receiving Agent (ORA_RCV_RECEIVING_AGENT_JOB)
• Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
• Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)

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

• Monitor Self-Service Receiving Receipt Work Area (RCV_MONITOR_RECEIVING_RECEIPT_SELF_SERVICE_WORK_AREA_PRIV)
• Monitor Receiving Receipt Work Area (RCV_MONITOR_RECEIVING_RECEIPT_WORK_AREA_PRIV)
• Access Supplier Portal Overview (POS_ACCESS_SUPPLIER_PORTAL_OVERVIEW_PRIV)
• Perform Receiving Receipt Transaction by Web Service (RCV_PERFORM_RECEIVING_RECEIPT_TRANSACTION_WEB_SERVICE_PRIV)

View Supplier Return Number and Supplier Return Line Number in the Inventory Transactions Real Time Subject Area in OTBI

View details of unreferenced supplier returns by adding the new Supplier Return Number and Supplier Return Line Number columns to your reports in Oracle Transactional Business Intelligence (OTBI). These new columns are now available in the Inventory Transactions Details dimension of the Inventory Transactions Real Time subject area.

Inventory Transactions Real Time

The new Supplier Return Number and Supplier Return Line Number columns provide you with additional reporting capability to help you easily view details of your unreferenced supplier returns.

Steps to Enable

Leverage new subject area(s) by adding to existing reports or using in new reports. For details about creating and editing reports, see the Creating and Administering Analytics and Reports book (available from the Oracle Help Center > your apps service area of interest > Books > Administration).

Tips And Considerations

You can add the new Supplier Return Number and Supplier Return Line Number columns to your existing reports, or create new reports that use these new columns. For details about creating and editing reports, see the Oracle SCM Cloud: Creating and Administering Analytics and Reports guide on the Oracle Help Center.

Key Resources

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

Role Information

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)

View Quantity Billed and Amount Billed Using the Receiving Transaction History REST Resource

Use the Quantity Billed and Amount Billed attributes in the Receiving Transactions History REST resource to view additional details about your historical receipt transactions. These attributes are not populated until the corresponding invoice is processed.

The Quantity Billed and Amount Billed attributes provide additional visibility into your historical receipt transactions when using the Receiving Transactions History REST resource to build your own reports or interfaces.

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

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

Role Information

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:

• Job Role Name and Code:
  • Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
  • Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
  • Receiving Agent (ORA_RCV_RECEIVING_AGENT_JOB)

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

• Review Receiving Transaction History (RCV_PROVIDE_RECEIVING_TRANSACTION_DETAILS_WEB_SERVICE_PRIV)

Intrastat Reporting

Update Intrastat Reporting for the United Kingdom's Exit from the European Union

As part of the United Kingdom's exit from the European Union (EU), Her Majesty's Revenue and Customs department (HMRC) issued refined guidance on Intrastat reporting requirements when trading goods with the United Kingdom. You can now specify when to exclude Great Britain for legal reporting units (LRUs) subject to Intrastat collections. Two new parameters, Exclude Dispatches From and Exclude Arrivals To, are available on the Manage Intrastat Parameters page. These parameters have no default value. You'll need to update these parameters when reporting requirements change so that you can exclude Intrastat reporting of transactions with Great Britain.

For EU LRUs, you should update the Exclude Dispatches From and Exclude Arrivals To parameters to Great Britain before collecting your January 2021 Intrastat transactions. Doing so excludes Intrastat reporting when EU countries trade goods with Great Britain.

European Union LRUs

Intrastat Parameters	Default Value	January 2021
Exclude Dispatches From	NA	Great Britain
Exclude Arrivals To	NA	Great Britain

For a United Kingdom LRU, you should update the Exclude Dispatches From parameter to Great Britain before collecting your January 2021 Intrastat transactions. Doing so excludes Intrastat reporting of goods originating from Great Britain and destined for an EU country. In the future, when you need to exclude arrival transactions into Great Britain for Intrastat reporting purposes, you can update the Exclude Arrivals To parameter to Great Britain.

United Kingdom LRUs

Intrastat Parameters	Default Value	January 2021	Future
Exclude Dispatches From	NA	Great Britain	Great Britain
Exclude Arrivals To	NA	NA	Great Britain

Dispatch and arrival transactions between any EU country and any Northern Ireland county are collected by the Intrastat report regardless of the value of the Exclude Dispatches From and Exclude Arrivals To parameters for a United Kingdom LRU.

NOTE: This feature was also made available in a monthly update of 20D.

This change ensures that you stay in compliance with the new Intrastat regulations published by HMRC for the United Kingdom's exit from the EU.

Steps to Enable

If you do business with any Northern Ireland counties in the United Kingdom, you need to ensure that a location is associated with any inventory organization, supplier site, customer site, or legal entity address based in a Northern Ireland county that has a postal code defined. Intrastat transactions are not collected if the postal code is blank and the destination or dispatch country is the United Kingdom.

1. In the Setup and Maintenance work area, go to the Manage Locations task:
   • Offering: Manufacturing and Supply Chain Materials Management Offering
   • Functional Area: Enterprise Profile
   • Task: Manage Locations
2. On the Manage Locations page, make sure a postal code is defined for legal addresses, supplier sites, and customer sites based in Northern Ireland counties. Intrastat transactions are not collected if the postal code is blank and the destination or dispatch country is the United Kingdom. If a postal code is not defined, select the entry you want to update and click Edit > Correct. Add the postal code. Then click Submit.

Ensure that the United Kingdom has been added to a tax zone.

1. In the Setup and Maintenance work area, go to the Manage Tax Zone Types task. In the Task panel tab, click Search, and search for Manage Tax Zone Types.
2. Click Manage Tax Zone Types to open the page.
3. Click Search on the Manage Zone Types page. (You don’t need to enter anything, just click Search.)
4. In the search results, select Economic Regions and click Next. The Manage Zones for Zone Type page is displayed.
5. Click Search on the Manage Zones for Zone Type page. (You don’t need to enter anything, just click Search.)
6. In the search results, click European Economic Community and a new page is displayed.
7. In the Associated Geographies section, locate the United Kingdom geography. If either the United Kingdom geography hasn't been defined or the end date has passed, you’ll need to create a new economic region and add the United Kingdom geography to it. Steps 9 and 10 explain how. If you don't need to create the United Kingdom geography, you can skip those steps. You can follow step 10 to create other geographies if you need them.
8. Click Done to go back to the Manage Zones for Zone Type page.

                       

Country Definition in Economic Zone

9. Create a new economic region:
   • In the Search Results section, click Actions > Create.
   • Enter a name for the zone in the Zone field.
   • Enter a code for the zone in the Code field.
   • Make sure the end date is in the future.
10. Associate a geography to the economic region:
    • In the Associated Geographies section, click Actions > Add.
    • Enter United Kingdom in the Country field.
    • Enter Country in the Geography Type field.
    • Enter United Kingdom in the Geography Name field.
    • Make sure the end date is in the future.
    • Repeat this step to add other geographies as needed.
    • Click Save and Close when you’ve finished adding geographies. 

Create Zone

If you created a new economic region for Intrastat that includes the United Kingdom, associate it with the Intrastat parameters.

1. In the Setup and Maintenance work area, go to the Manage Intrastat Parameters task:

Note: You might need to enable the Intrastat Reporting functional area first.

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

2. Select the legal entity and click Edit. The Edit Intrastat Parameters page is displayed.
3. In the Economic Zone field, select the new economic zone you created.
4. Associate the new economic zone with the Intrastat parameters for LRUs. The Exclude Dispatches From and Exclude Arrivals To parameters have no default value, so you’ll need to set them.
   • For an EU LRU, when you’re ready to run the Intrastat report for the month of January 2021, change the Exclude Dispatches From and Exclude Arrivals To parameters to Great Britain.
   • For United Kingdom LRUs, when you’re ready to run the Intrastat report for the month of January 2021, update the Exclude Dispatches From parameter to Great Britain. In the future, when you need to exclude arrival transactions into Great Britain for Intrastat reporting purposes, you can update the Exclude Arrivals To parameter to Great Britain.
5. Click Save and Close.

Manage Intrastat Parameters

Key Resources

• Oracle Supply Chain Management Cloud: Using Implementing Manufacturing and Supply Chain Materials guide, Intrastat Reporting chapter, available on the Oracle Help Center.

Role Information

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:

• Collect Intrastat Transactions (JMF_COLLECT_INTRASTAT_TRANSACTIONS_PRIV)
• Define Intrastat Parameters (JMF_DEFINE_INTRASTAT_PARAMETERS_PRIV)
• Manage Intrastat Transactions (JMF_MANAGE_INTRASTAT_TRANSACTIONS_PRIV)
• Manage Tax Zone Types (ZX_CREATE_TAX_ZONE_TYPE_PRIV)

Cost Management

Use RMA Line Price As the Incoming Receipt Cost on an Unreferenced RMA

Your business process may involve receiving customer-owned items for repair and return (depot repair). When you receive items for repair or return or buy back items that you don't sell, you create an unreferenced RMA with one of the following stated prices:

1. Zero, if the items are meant for depot repair
2. A credit value, if you are buying back the item and putting it in stock

After you receive the item and put it into inventory, the price on the RMA should be used as the acquisition cost. You can set up your cost profile to value the incoming inventory at the RMA price instead of valuing using the existing item cost. 

The following screenshot illustrates this new cost profile option.

Unreferenced RMA Receipt Cost Option

This feature provides the ability to configure your cost profile to appropriately cost the return receipts against an unreferenced RMA.

Steps to Enable

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

Tips And Considerations

• If you update this option in an existing cost profile, all item cost profiles assigned to the cost profile you changed, use the RMA line price.

• If there are any recurring charges on the RMA order, those charges are ignored when costing the RMA receipt using this new option and only the net sale price is used as the acquisition cost for the RMA receipt.

• If you select Existing Item Cost in the Unreferenced RMA Receipt Cost field and the RMA receipt is the first transaction for the item in the valuation unit, you have to set up a default cost element for it to be processed with a zero cost.

• If you receive a kit, which is made up of several items, the price on the order is for the kit, not the individual items.  However, the shipment and return receipt is created for each individual item, not the kit as a whole. Since the items are part of the kit and do not have prices, when the RMA receipt is recorded and you use the RMA cost as the price, the price is zero.

• If a return is received in a cost organization that is different than the cost organization where the original shipment was costed, the receipt is costed based on the value you selected for the Unreferenced RMA Receipt Cost option in the cost profile.

Key Resources

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

Role Information

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:

• Manage Cost Profile (CST_MANAGE_COST_PROFILE_PRIV)
• Create Cost Distributions (CST_CREATE_COST_DISTRIBUTIONS_PRIV)
• Review Cost Distributions (CST_REVIEW_COST_DISTRIBUTIONS_PRIV)

Cost and Account for Inventory Lot Transactions

When dealing with goods that are under lot control, there are numerous events that might require you to break, combine, or transform some or all of the goods in a specific lot. You can create lot split, merge or translate transactions in inventory to records these events. When you move these transactions to Cost Management then run the Create Cost Accounting Distributions process, distributions are created to record the movement of the inventory value from one lot and subinventory to another lot and subinventory

The following images show an example of a processed lot split transaction in Cost Management.

Review Cost Accounting Distributions for Lot Transactions

Review Cost Accounting Distributions for Lot Split Issue Transaction with 10 Quantity

Review Cost Accounting Distributions for Lot Split receipt Transaction with 9 Quantity

Review Cost Accounting Distributions for Lot Split Issue Transaction with 1 Quantity

This feature lets you cost and account for modified lots dynamically without the overhead of creating a work order or performing extraneous inventory transactions, saving you time and improving efficiency.

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

Feature: Perform Lot Split, Merge, and Translate Using REST APIS and FBDI

Tips And Considerations

1. The following new accounting events have been introduced for this feature:
   1. Lot Split
   2. Lot Merge
   3. Lot Translate

2. You must review and modify subledger journal entry rule sets to account for these transactions based on your accounting requirements. You can copy an existing journal entry rule set or use the seeded rule sets  to set up account rules for the new accounting events to meet your accounting requirements.

   Seeded Journal Entry Rule Sets for New Accounting events

3. The lot split, merge and translate transactions create distributions in cost accounting even when the account intravaluation transfer option in the cost profile is set to no.
4. You can use the Summarize Lot Transactions option in the cost profile to summarize lot transactions when the valuation unit on the cost profile for the item is higher than the lot level. Transactions for Lot - serial items cannot be summarized.
5. You can define accounting overhead rules for lot transactions in the Manage Accounting Overhead Rules page. Overheads for when the transaction is issued can only be expensed, while overheads defined for when the transaction is received can be included in inventory or expensed.
6. You can create receipt cost adjustments for the receipt leg of the lot transactions from the Manage Cost Adjustments page.

Key Resources

For more information, see the following guides available on the Oracle Help Center.

• Oracle SCM Cloud: Implementing Manufacturing and Supply Chain Materials Management Guide
• Oracle SCM Cloud: Using Supply Chain Cost Management

Role Information

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

• Application Implementation Consultant (ORA_ASM_APPLICATION_IMPLEMENTATION_CONSULTANT_JOB) for configuring account rules for the new accounting events.

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

• Create Cost Distributions (CST_CREATE_COST_DISTRIBUTIONS_PRIV)
• Review Cost Distribution (CST_REVIEW_COST_DISTRIBUTIONS_PRIV).

Other Cost Management Changes in This Update

This section includes details about additional changes in this update that can change the way Oracle Cost Management Cloud works.

Changed Data Access for the Transfer Transactions from Inventory to Costing Process

You must have data access to the appropriate cost organization to successfully run the Transfer Transactions from Inventory to Costing scheduled process. Prior to this update, you could run the scheduled process for any cost organizations, no matter your data access. Now, if you don’t have access to the selected cost organization for the process, the process ends with a Warning status. If you’ve scheduled the process without selecting a cost organization, the process transfers data for only those cost organizations to which you have data access. It logs error messages for any cost organizations to which you don’t have access. The errors logged in the request log file for the process indicate that you don’t have access to the cost organization for which the process is being run. 

Bug reference: 31709503

Expense Destination Purchase Orders Are Accounted for in Purchase Order and Functional Currencies

The expense amount for expense destination purchase orders is now automatically accounted for in both the functional currency and the purchase order currency. Prior to this update, the expense amount was accounted for only in the functional currency. This change ensures visibility of the expense amount accounted for in the purchase order currency. Also, the receiving inspection account is balanced in the purchase order currency as well as in the functional currency.

Bug reference: 25349563

Product Recall Management

You must opt in to the Product Recall Management functional area to enable the features in this section. You can find this functional area in the Manufacturing and Supply Chain Materials Management offering.

View Recall Notice Details When Reviewing Duplicates

You may receive recall notices from multiple sources for the same recalled item.  When you do, you mark specific notices as duplicates so tasks are only assigned to one notice. When you are reviewing duplicate notices on the Review Duplicate Notices page, you can now drill down to see notice details. You can review the line details, including manufacturer part number, recalled lot and serial information before marking the notice as a duplicate.

Being able to view notice details when reviewing duplicates allows you to make quicker and more informed decisions on which notices are duplicates.

Steps to Enable

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

Key Resources

• The Using Product Recall Management guide available on the Oracle Help Center.

Role Information

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)

View Details and History from Recall Notices Page

You manage all your product recall notices in the Recall Notices work area. You can now access notice details and history for closed or withdrawn notices from the Recall Notices work area. Just click View Details for the notice to access the Notice Details page. On the Notice Details page, you can review all the line, task, and location information.

The following screenshots show how to access the details from the Recall Notices work area.

View Details Button in Recall Notices Work Area

Notice Details for Closed Recall Notice

The View Details buttons gives you quick access to notice details and history for closed and withdrawn notices.

Steps to Enable

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

Key Resources

• The Using Product Recall Management guide available on the Oracle Help Center.

Role Information

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)

Enter Comments for Specific Actions Performed for a Recall Notice

When you perform certain tasks for a product recall, it is important to enter information on why you performed the task. You can now enter this information in the Comment field when you withdraw a notice or notice line and when you close or withdraw a task. For example, you may want to enter the transaction details for the tasks closed or justification for withdrawing the recall notices or tasks. These comments can be reviewed as a part of line details and task history for audit purposes.

This following screenshots show the Comment field.

Complete Task Comment

Withdraw Notice Comment

Entering comments for specific actions allows you to have detailed information on why you performed an action.

Steps to Enable

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

Key Resources

• The Using Product Recall Management guide available on the Oracle Help Center.

Role Information

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

• Job Role:
  • Product Recall Manager (ORA_ENQ_PRODUCT_RECALL_MANAGER)

Supply Chain Financial Orchestration

Use External Ship-to Locations and Internal Ship-from Locations in an Intercompany AP Invoice

To comply with tax regulations, companies set up rules to calculate tax based on the ship-to location on the source order document when creating intercompany invoices.

Prior to this update, Oracle Supply Chain Financial Orchestration passed the default ship-to location of the Selling Profit Center Business Unit when creating the intercompany AP invoice. With this update, Supply Chain Financial Orchestration will capture the actual ship-to location from the source document when creating the intercompany AP invoice.

This feature will enable companies to accurately model their tax rules based on the ship-to location as represented in the source order for various business flows.

The table below lists the ship-to locations that are derived based on the business flows:

Business Flow	New Value	Location Type
Global Procurement	Ship-to location in the purchase order schedule	Internal Location
Transfer Order	Ship-to location in the transfer order line	Internal Location
Internal Transfer	Ship-to inventory organization location	Internal Location
Shipment (IDS)	Actual customer ship-to location on the sales order	External Location
Non Shippable Sales	Actual customer ship-to location on the sales order, if available	External Location
Drop Shipment + GP	Actual customer ship-to location on the sales order	External Location
Drop Shipment + Shipment	Actual customer ship-to location on the sales order	External Location

Using the appropriate ship-to location on the source order document allows you to setup tax rules that comply with tax regulations when creating intercompany invoices.

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

Key Resources

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

Role Information

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV)

Use Location of Final Discharge in an Intercompany AP Invoice

To comply with tax regulations, companies set up rules to calculate tax based on the location of final discharge when creating intercompany invoices.

Prior to this update, Oracle Supply Chain Financial Orchestration passed the default ship-from inventory organization as the location of final discharge when creating an intercompany AP invoice. With this update, Supply Chain Financial Orchestration will capture the actual location of final discharge from the source transaction when creating the intercompany AP invoice.

The table below lists the location of final discharge that is derived based on the business flows:   

Business Flow	New Value	Source
Global Procurement	Location of final discharge	Receiving transaction
Drop Shipment with Procurement/Shipment	Location of final discharge	DOO fulfillment
Internal Transfer	Location of final discharge	If the ownership change event is receipt, then fetch from the receiving transaction. Else, fetch  from Buy Side tax determinants in the transfer order line.
Non Shippable Sales	Location of final discharge	If the ownership change event is receipt, then fetch from receiving transaction. Else, fetch from inventory transaction.
Shipment (IDS)	Location of final discharge	DOO fulfillment
Transfer Order	Location of final discharge	DOO fulfillment

Using the actual location of final discharge from the source transaction allows you to setup tax rules that comply with tax regulations when creating intercompany invoices.

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

Key Resources

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

Role Information

• Users who are assigned any of these predefined job roles are automatically able to access this feature:
  • Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)

• Users who are assigned configured job roles that contain these privileges are able to access this feature:
  • Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV)