- Revision History
- Overview
- Optional Uptake of New Features (Opt In)
- Feature Summary
-
- Inventory Management
-
- Capture Requester for Requisition Movement Requests
- Create Miscellaneous Transactions with a New User Experience
- Perform Cycle Count Based on Item Category
- Suppress Subinventory Transfers from Min-Max Planning When On-Hand Balance in Source Subinventory is Zero
- Use Additional User-Friendly Keys for REST APIs
- Use Data Auditing on Lot and Serial Master
-
- Shipping
- Receiving
- Intrastat
- Cost Management
- Fiscal Document Capture
- Supply Chain Financial Orchestration
- Inventory Management
This document will continue to evolve as existing sections change and new information is added. All updates appear in the following table:
Date | Feature | Notes |
---|---|---|
18 MAY 2020 | Use Item Lead Times in Calculation of Expected Ship Date for Transfer Orders |
Removed feature from update 20B. |
20 MAR 2020 | Created initial document. |
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.
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.
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:
Access the Opt In page from the New Features Work Area
- Click the Navigator, and then click New Features (under the My Enterprise heading)
- On the New Features page, select the offering that includes new features you’d like to review
- Click Go to Opt In for any feature you want to opt in
- On the Edit Features page, select the Enable option for the feature, and then click Done
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.
Column Definitions:
Features Delivered Enabled
Report = New or modified, Oracle-delivered, ready to run reports.
UI or Process-Based: Small Scale = These UI or process-based features are typically comprised of minor field, validation, or program changes. Therefore, the potential impact to users is minimal.
UI or Process-Based: Larger Scale* = These UI or process-based features have more complex designs. Therefore, the potential impact to users is higher.
Features Delivered Disabled = Action is needed BEFORE these features can be used by END USERS. These features are delivered disabled and you choose if and when to enable them. For example, a) new or expanded BI subject areas need to first be incorporated into reports, b) Integration is required to utilize new web services, or c) features must be assigned to user roles before they can be accessed.
Ready for Use by End Users Reports plus Small Scale UI or Process-Based new features will have minimal user impact after an update. Therefore, customer acceptance testing should focus on the Larger Scale UI or Process-Based* new features. |
Action is Needed BEFORE Use by End Users Not disruptive as action is required to make these features ready to use. As you selectively choose to leverage, you set your test and roll out timing. |
|||||
---|---|---|---|---|---|---|
Feature |
Report |
UI or |
UI or |
|
||
Create Miscellaneous Transactions with a New User Experience |
||||||
Release Shipment Requests to an External 3PL or WMS Using Release Sequence Rules |
||||||
Get Overhead Rates for Standard Costed Make Items Using REST Services |
||||||
Use Primary Salesperson as an Additional Subledger Accounting Source |
||||||
Capture Additional Tax Determinants in a Brazilian Fiscal Document |
||||||
Use Enhanced Document Derivation When Importing Brazilian Fiscal Documents |
||||||
Process Referenced RMA as Unreferenced When Forward Flow Can't Be Determined |
||||||
Use Enhanced Financial Orchestration Qualifiers for Customer Drop Shipment Flows |
Capture Requester for Requisition Movement Requests
Requisition movement requests are a quick way for you to issue or transfer goods that don't require documentation support outside of a pick slip. When creating these transactions, you might need to track who requested the goods for internal reporting requirements. Alternatively, you may have the requirement to inform the requester of any product faults or recalls.
Now, you have the ability to specify a requester for requisition movement requests within the Create Movement Requests page, the Manage Movement Requests page, and when using the Inventory Movement Requests REST API. Additionally, you can view the requester within the Pending and Completed Transactions pages for future reference. This lets you specify and track who asked for the materials to be issued or transferred for internal reporting requirements, or in case you need to notify the requester that specific goods were found defective or recalled at a later date.
Create Movement Request
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
Requester is an optional field which can be entered on the Create Movement Request page.
Key Resources
- Oracle Supply Chain Management Cloud: Using Inventory Management guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Manage Inventory Inventory Movement Request (INV_MANAGE_INVENTORY_MOVEMENT_REQUEST)
- Duty Role Name and Code:
- Warehouse Transaction Maintenance Duty (ORA_INV_WAREHOUSE_TRANSACTION_MAINTENANCE_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR)
- Inventory Manager (ORA_INV_INVENTORY_MANAGER)
Create Miscellaneous Transactions with a New User Experience
Miscellaneous Transactions are a quick way for you to issue or receive goods that don't have or require documentation support. When creating a miscellaneous transaction, you need to specify whether or not to use the good's current cost for the transaction and enter repetitive information in some data fields. Additionally, you might have the desire to track who requested the goods so that you can inform them of any product issues or recalls.
Now, you have the ability to default the value of the Use Current Item Cost field. Also, you can create a new transaction line by copying an existing transaction line. These attributes copy onto the new transaction line:
- Subinventory
- Locator
- Reason
- Reference
- Inventory Project
- Inventory Task
- Project Costing Project
- Project Costing Task
- Expenditure Type
- Expenditure Organization
- Contract Number
- Funding Source
These changes improve your efficiency when creating new miscellaneous transactions and reduce the requirement to enter repetitive data for similar transaction lines.
Additionally, you can now specify who requested the transaction for internal auditing purposes or in case you need to notify who the goods were issued to should they be found defective or recalled at a later date.
Create Miscellaneous Transaction
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
To default the Use Current Item Cost field to Yes on the Create Miscellaneous Transactions page, select the Use Current Item Cost check box on the Manage Inventory Organization Parameters page.
Manage Inventory Organizations > Manage Organization Parameters
Key Resources
-
Watch Inventory Management Process Enhancements Readiness Training
- Oracle Supply Chain Management Cloud: Using Inventory Management guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privilege or roles are required:
- Privilege Name and Code:
- Create Miscellaneous Transaction (INV_CREATE_INVENTORY_TRANSACTION_MISCELLANEOUS_TRANSACTION)
- Duty Role Name and Code:
- Warehouse Transaction Maintenance Duty (ORA_INV_WAREHOUSE_TRANSACTION_MAINTENANCE_DUTY)
- Inventory Transaction Management Duty (ORA_INV_INVENTORY_TRANSACTION_MANAGEMENT_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
- Inventory Manager (ORA_INV_INVENTORY_MANAGER_JOB)
- Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR_JOB)
Perform Cycle Count Based on Item Category
When coordinating cycle counts within your organization, it sometimes makes sense to assign your goods based on a specific or common attribute. For instance, you can assign goods by a specific brand or a particular state the goods are in, like raw, semifinished, or fully finished. Due to the nature of your warehouse layout or inventory turnover, the goods that share this common attribute may be spread across multiple subinventories, but conveniently all belong to the same category of their assigned catalog. So, you need an easy way to add these common items to a cycle count, regardless of what subinventory they belong to.
Now, you have the ability to create a cycle count and assign items to that count based on existing categories. This provides you a quick way to assign items to a cycle count based on a grouping of specific or common attributes.
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 20D
In addition, you must select the Enable cycle count by item category check box on the Create Cycle Count: Enter Primary Details page in order to use this feature.
Create Cycle Count
Key Resources
-
Watch Inventory Management Process Enhancements Readiness Training
- Oracle Supply Chain Management Cloud: Using Inventory Management guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Manage Cycle Count (INV_MANAGE_CYCLE_COUNT)
- Duty Role Name and Code:
- Inventory Count Management Duty (ORA_INV_INVENTORY_COUNT_MANAGEMENT_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Inventory Manager (ORA_INV_INVENTORY_MANAGER)
Suppress Subinventory Transfers from Min-Max Planning When On-Hand Balance in Source Subinventory is Zero
This feature provides you with the ability to suppress the creation of replenishment movement requests when the item on-hand quantity is zero in the source subinventory. The feature improves the overall min-max planning process. For example, in your organization you may not want to create a replenishment movement request when the source subinventory has zero item on-hand quantity. Creating replenishment movement requests unnecessarily result in downstream activities to cancel unwanted movement requests. The intent of this feature is to provide you with more control over the replenishment movement request creation process.
The benefits of the feature include improvements in the min-max planning process by eliminating the creation of movement requests unnecessarily. Creating replenishment movement requests when there is no on-hand quantity in the source subinventory results in unneeded data in the system. Warehouse personnel need to spend time canceling replenishment movement requests from the system. For example, you can submit the min-max planning process for all subinventories within an organization. Let’s say there are 50 subinventories with zero item on-hand quantity. This results in 50 replenishment movement requests created with zero item on-hand quantity in the source organization. Your warehouse personnel need to then cancel the 50 movement replenishment requests. So, you can use this feature to configure whether or not you want to create a replenishment movement request when the source subinventory has zero on-hand quantity.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
The Include Subinventories Without On-Hand Quantities parameter has been added to the Print Min-Max Planning Report scheduled process. The default value for the new parameter is Yes. Leaving the default as Yes maintains the current behavior. Setting the parameter value to No invokes the new feature behavior. When the parameter value is No, the min-max planning process suppresses the creation of the replenishment movement request when the source subinventory has zero item on-hand quantity.
Print Min-Max Planning Report
Key Resources
-
Watch Inventory Management Process Enhancements Readiness Training
- Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management Guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Print Min-Max Planning Report (INV_PRINT_MIN_MAX_PLANNING_REPORT)
- Duty Role Name and Code:
- Inventory Transaction Management Duty (ORA_INV_INVENTORY_TRANSACTION_MANAGEMENT_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Inventory Manager (ORA_INV_INVENTORY_MANAGER)
Use Additional User-Friendly Keys for REST APIs
When using the available REST APIs in Oracle Inventory Management Cloud to build your own conffigured interfaces, integrate with external applications, or query specific information, you need the ability to quickly identify key information. In order to facilitate this, these REST APIs have been updated to include additional user-friendly fields:
- Available Quantity Details
- Use the Locator field to identify the corresponding locator ID
- Use the Owning Party Site field to identify the corresponding owning entity ID
- Inventory Reservations
- Use the Source Fulfillment Line Number field to identify the corresponding source fulfillment line ID
- Shipment Line Transaction Requests > Shipment Lines
- Use the Source System field to identify the corresponding source system ID
- Shipments > Outer Packing Units
- Use the Address field attributes to identify the corresponding ship-from and ship-to location IDs
- Shipments > Inner Packing Units
- Use the Address field attributes to identify the corresponding ship-from and ship-to location IDs
- Shipments > Shipping Costs
- Use the Packing Unit field to identify the corresponding packing unit ID
- Shipments > Packing Unit Costs
- Use the Packing Unit field to identify the corresponding packing unit ID
- Shipments > Shipment Line Costs
- Use the Packing Unit field to identify the corresponding packing unit ID
- Shipment Lines > Costs
- Use the Packing Unit field to identify the corresponding packing unit ID
- Shipping Exceptions
- Use the Item Number and Item Description fields to identify the corresponding item ID
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
To use this feature, the following privileges or roles are required.
For Inventory Available Quantity Details REST services:
- Privilege Name and Code:
- View Available Item Quantity by Web Service (INV_VIEW_AVAILABLE_ITEM_QUANTITY_WEB_SERVICE_PRIV)
- Duty Role Name and Code:
- Inventory Management Web Service (ORA_INV_INVENTORY_MANAGEMENT_WEB_SERVICE_DUTY)
For Inventory Reservations REST services:
- Privilege Name and Code:
- Manage Inventory Reservation Web Service (INV_MANAGE_INVENTORY_RESERVATION_WEB_SERVICE_PRIV)
- Duty Role Name and Code:
- Inventory Transaction Management (ORA_INV_INVENTORY_TRANSACTION_MANAGEMENT_DUTY)
For Shipping REST services:
- Privilege Name and Code:
- Manage Shipment Web Service (WSH_MANAGE_SHIPMENT_WEB_SERVICE)
- Duty Role Name and Code:
- Shipment Processing (ORA_WSH_DELIVERY_PROCESSING_DUTY)
Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Inventory Manager (ORA_INV_INVENTORY_MANAGER)
- Warehouse Operator (ORA_INV_WAREHOUSE_OPERATOR)
Use Data Auditing on Lot and Serial Master
As auditing requirements continue to grow in many regulated industries, you need an easy way to track changes to an increasing number of areas in your business. Lot and serial controlled items can face particular scrutiny when it comes to things like expiration dates or the sensitivity of the item.
Whether it's an update to the lot expiration date after a recertification inspection, or a change in the material status to comply with a recall, you need the ability to easily track and verify that appropriate changes were made.
Now, you can enable data auditing capabilities to include any changes to lot and serial attributes and their associated descriptive flexfields. As required, you can review these changes in the Audit Reports work area which provides you with information such as what operation was performed, when it was performed, and how the value was changed. This allows you to quickly and easily generate a data auditing report for use in internal and external auditing compliance.
Steps to Enable
There is no opt in for this feature, but you must complete certain setup steps to enable this feature.
- Navigate to the Manage Audit Policies page to configure lot and serial number business object attributes.
Manage Audit Policies
- Click the Configure Business Object Attribute button to open the Configure Business Object Attribute page.
- Select Inventory Management for the product.
- Select and expand Lot and Serial Number Audit Setup.
- Select Lot and Serial Number, and then click Save and Close.
Configure Business Object Attributes
Your setup to use this feature is complete.
Key Resources
-
Watch Inventory Management Process Enhancements Readiness Training
- Oracle Supply Chain Management Cloud: Using Inventory Management guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Manage Audit Policies (FND_MANAGE_AUDIT_POLICIES)
- Job Role Name and Code:
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
Send Partially Reserved Demand to an External 3PL or WMS
In today's fast paced, just-in-time logistics environment, you need to fulfill your customer's orders as soon as possible. This means you may want to send multiple shipments as soon as you make adequate on-hand inventory available. Therefore, you need to reserve available on-hand goods and send the corresponding shipment request to your external Third Party Logistics Provider (3PL) or Warehouse Management System (WMS) even if you don't have your customer's full order quantity in stock.
Now, when integrating with an external 3PL or WMS, partially reserved shipment lines are sent through the Generate Shipment Request process.
Steps to Enable
In the Setup and Maintenance work area, use the Manage Shipping Parameters task to set the value of the Reservation Behavior for Integration to External Systems parameter to Partial:
- Offering: Manufacturing and Supply Chain Materials Management
- Functional Area: Shipping
- Task: Manage Shipping Parameters
Manage Shipping Parameters
Tips And Considerations
By default, the Reservation Behavior for Integration to External Systems shipping parameter is set to Full.
Key Resources
- REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Manage Shipping Parameters (WSH_MANAGE_SHIPPING_ORGANIZATION_PARAMETER)
- Duty Role Name and Code:
- Shipping Administration Duty (ORA_WSH_SHIPPING_ADMINISTRATION_DUTY)
- Job Role Name and Code:
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR)
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Shipping Manager (ORA_WSH_SHIPPING_MANAGER)
Release Shipment Requests to an External 3PL or WMS Using Release Sequence Rules
When releasing orders for shipment to your external Third Party Logistics provider (3PL) or Warehouse Management System, you need to ensure that your orders are released in accordance with your specified priorities. Release sequence rules define the order in which shipment lines are processed. So far they are used when shipment lines are released to inventory. Now, the Generate Shipment Requests process respects the priority you defined in the release sequence rule specified when submitting the process to send shipment lines to your external execution system.
The Generate Shipment Requests process now respects the following priorities:
- Sales order
- Scheduled ship date
- Outstanding invoice value
- Shipping priority
Initial ship date is not respected as a priority because this parameter is determined by the external 3PL or WMS.
Steps to Enable
To use this feature, navigate to the Manage Pick Wave Release Rules task to select a value for the Release Sequence Rule attribute that you plan to use for sending shipment requests to your external execution system.
- In the Setup and Maintenance work area, use the Manage Pick Wave Release Rules task:
- Offering: Manufacturing and Supply Chain Materials Management
- Functional Area: Shipping
- Task: Manage Pick Wave Release Rules
- Choose the pick wave release rule and select Edit from the Actions menu.
- On the Edit Pick Wave Release Rule page, select the Options tab.
- Select a value for the Release Sequence Rule attribute.
Manage Pick Wave Release Rules
Key Resources
- REST API for Oracle Supply Chain Management Cloud guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Generate Shipment Request (WSH_GENERATE_SHIPMENT_REQUEST)
- Create Outbound Shipment Request (WSH_CREATE_SHIPMENT_REQUEST)
- Duty Role Name and Code:
- Shipment Management Duty (ORA_INV_INVENTORY_TRANSACTION_MANAGEMENT_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Shipping Manager (ORA_WSH_SHIPPING_MANAGER)
Allow Backorders Using a REST Service
When integrating with an external Third Party Logistics Provider (3PL) or Warehouse Management System (WMS), various situations arise that require you to backorder shipment lines. When this occurs, the WMS needs the ability to communicate these backorders to Oracle Inventory Management Cloud for accurate tracking purposes.
Now, you're able to communicate these backorders from your 3PL or WMS to Oracle Inventory Management Cloud using the Quantity to Backorder field on the Shipment Line Change Requests REST API. This enables you to keep your shipment statuses in sync between Oracle Inventory Management Cloud and your external 3PL or WMS.
Also, to facilitate the same using UI pages, you can use the Backorder action on the interfaced shipment lines using the Manage Shipment Lines page.
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
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Manage Shipment Web Service (WSH_MANAGE_SHIPMENT_WEB_SERVICE)
- Duty Role Name and Code:
- Shipment Processing Duty (ORA_WSH_DELIVERY_PROCESSING_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER)
- Shipping Manager (ORA_WSH_SHIPPING_MANAGER)
- Shipping Agent (ORA_WSH_SHIPPING_AGENT)
Use Enhanced Search for Self-Service Receipts
When placing large orders with your suppliers, there may be times when you have purchase orders with hundreds of lines. In these cases, your supplier may not send all of the requested goods in a single shipment. When this happens, you need the ability to search for specific purchase order lines, or a specific range of lines. Now, you can search the My Receipts page for a specific line or range of lines within a specific purchase order.
Additionally, when reviewing your broader search results, you may need to reference the purchase requisition description for notes about a specific purchase order line. Now, you have the ability to view the purchase requisition description as part of your search results.
Receive Items
In this example, the between operator is used to search for a range of lines for a particular purchase order. The requisition description is included in the search results.
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- The Purchase Order Line field is immediately accessible from the Advanced button on the Receive Items page.
- You must enable the requisition description from the View menu for the Description field to appear in the search results.
Key Resources
- Oracle Supply Chain Management Cloud: Using Receiving guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privilege or roles are required:
- Privilege Name and Code:
- Create Self-Service Receiving Receipt (RCV_CREATE_RECEIVING_RECEIPT_SELF_SERVICE_PRIV)
- Duty Role Name and Code:
- Receiving Management Requester (ORA_RCV_RECEIVING_MANAGEMENT_REQUESTER_DUTY)
- Job Role Name and Code:
- Procurement Requester (ORA_POR_PROCUREMENT_REQUESTER_ABSTRACT)
- Advanced Procurement Requester (ORA_POR_ADVANCED_PROCUREMENT_REQUESTER_ABSRACT)
- Procurement Preparer (ORA_POR_PROCUREMENT_PREPARER_ABSTRACT)
Manage Receipt Advice Using a REST Service
You can now use a REST API to send receipt advices to an external execution system, like a Third Party Logistics provider (3PL) or Warehouse Management System (WMS). Your external execution system can call the Receipt Advice Lines REST service to flag eligible receipt lines based on your specified criteria, such as organization, document number, and due date. The same service also retrieves details of those lines. The REST API considers both new and changed receipt advice lines for sending to external execution systems.
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
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Manage Receiving Receipt Advice Web Service (RCV_MANAGE_RECEIVING_RECEIPT_ADVICE_WEB_SERVICE_PRIV)
- Send Receiving Receipt Advice Web Service (RCV_SEND_RECEIVING_RECEIPT_ADVICE_WEB_SERVICE_PRIV)
- Duty Role Name and Code:
- Receiving Transaction Maintenance (ORA_RCV_RECEIVING_TRANSACTION_MAINTENANCE_DUTY)
- Receiving Management (ORA_RCV_RECEIVING_MANAGEMENT_DUTY)
- Job Role Name and Code:
- Warehouse Manager (ORA_INV_WAREHOUSE_MANAGER_JOB)
- Receiving Agent (ORA_RCV_RECEIVING_AGENT_JOB)
Derive Country of Supply for Intrastat Reporting from Legal Reporting Unit for Invoice Triangulation Method
Intrastat Reporting in Oracle Inventory Management Cloud collects, records, and reports statistics on the movement of material related to the trade of goods between countries in the European Union (EU). This facilitates your reporting requirements to the respective government and statutory bodies (Intrastat Authorities) based on the direction of the government legislation.
Oracle Inventory Management Cloud's Intrastat Reporting supports the concept of a triangular trade transaction. This is any transaction between three trading partners in three countries, where at least two of the parties are part of the economic zone. The triangulation method specifies how to analyze and generate the movement statistics records when the application encounters a triangular trade transaction. Here are the two possible methods:
- Invoice - movement record is based on the invoice and not the physical movement of goods.
- Shipment - movement record is created only on the physical movement of goods.
You may need to model your enterprise structures with complex, cross-country, intercompany flows that subsequently require you to adopt the invoice triangulation method.
For example, let's say you have a selling entity where the legal entity, business unit, and inventory organization are all located in Austria. Additionally, you have a supply warehouse located in Germany where the business unit and inventory organization are located, but the legal entity is in the Netherlands. Now, a customer in Austria places an order with your Austria entity, but you need to source the goods from your warehouse in Germany. You ship the goods from the Germany warehouse directly to the customer in Austria. An intercompany transaction resolves the financial obligation between the country of supply and selling business unit entities. Using the invoice triangulation method, you can ensure that when your warehouse in Germany rolls up to a legal entity in the Netherlands, the country of supply is listed as Germany, instead of being derived from the legal entity (Netherlands). Now you have the ability to derive the country of supply for Intrastat Reporting from the legal reporting unit association when using the invoice triangulation method.
Manage Intrastat Transactions
In another example, we see an intrastat sales order dispatch transaction that has a country of supply of France, despite belonging to Vision Europe (a legal entity registered in Germany). This is possible by creating and associating a legal reporting unit in France with the business unit where the goods are shipped from, also in France.
Steps to Enable
Financials > Manage Legal Reporting Unit
Select Scope
- Select the scope (legal entity) under which the legal reporting unit resides.
- Create new (or select and add if your legal reporting unit already exists).
Manage Legal Reporting Units
- Create a new legal reporting unit or highlight an existing one.
Manage Legal Reporting Units
- Select Manage Business Entities.
Manage Associated Business Entities
- Create a business unit association.
Tips And Considerations
-
This feature is aimed at organizations that operate within the European Union (EU) and have a complex enterprise structure, specifically ones that have business units and inventory organizations in multiple EU countries that belong to a single legal entity.
-
If a legal reporting unit isn't associated with a business unit, or a business unit is associated with multiple legal reporting units, the country of supply is derived from the address of the legal entity.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management Guide, available on the Oracle Help Center.
Role Information
To use this feature, the following privileges or roles are required:
- Privilege Name and Code:
- Collect Intrastat Transactions (JMF_COLLECT_INTRASTAT_TRANSACTIONS_PRIV)
- Duty Role Name and Code:
- EMEA Financial Reporting Duty (ORA_JE_EMEA_FINANCIAL_REPORTING_DUTY)
NOTE: This is an orphan duty that requires manual assignment to a job role from the Security Console.
Exclude Invoice Cost Variances from Cost Management
Oracle Cost Management Cloud provides an ability to value your inventory at the true acquisition costs. During receipt into inventory, inventory is valued at either purchase order price, including tax and any landed cost charges, or standard. Any differences between the standard cost and the purchase order price are expensed as a purchase price variance. Subsequently, any additional costs that are imported from Payables, such as invoice price variance, exchange rate variance and tax rate variance, are used to true up the inventory cost by applying them as acquisition cost adjustments. The true up of inventory cost is carried out based on the cost method.
- Actual cost (FIFO): acquisition cost adjustments apply to on-hand inventory as well as any consumption transactions such as sales order issues, work order issues, and transfers etc.
- Average cost: acquisition cost adjustments apply only to the extent of on-hand inventory and any adjustments pertaining to inventory that is consumed are expensed out into cost variance.
- Standard Cost: acquisition cost adjustments are always expensed out as a purchase price variance upto the extent of quantity delivered.
Since the amount being applied as an acquisition cost adjustment depends on proration to receipt quantity, there could be a remaining balance in receiving inspection account due to differences between receipt quantity and Invoice quantity. In case of standard costing, the remaining amount in the receiving inspection account being reflected in the balance sheet instead of an income statement account. This poses an accounting challenge since the accounting of these variances as an expense was already complete in Payables that then get reversed into balance sheet subsequently.
You can now exclude payables invoice cost variances from inventory valuation for inventory and work order destination purchase orders. You can use this for all cost methods when you do not intend to apply invoice cost variances as acquisition cost adjustments to item cost and inventory value.
Steps to Enable
You must set a profile option to enable this feature. Follow these instructions:
- In the Setup and Maintenance work area, go to the Manage Costing Profile Options task:
- Offering: Manufacturing and Supply Chain Materials Management
- Functional area: Cost Accounting
- Task: Manage Costing Profile Options
- On the Manage Costing Profile Options page, search for the profile option code named: ORA_CMR_IGNORE_AP_INV_VAR_ALL.
- In the Search Results, select the profile option, and then set the profile value to Yes at the site level.
Manage Costing Profile Options Page
- Click Save and Close.
Tips And Considerations
- When you collect costs in Oracle Project Portfolio Management Cloud from Cost Management, the invoice cost adjustments are not imported to a project for inventory and work order destination flows when the profile option is configured as ‘Yes’. Invoice cost adjustments for expense destination purchases will continue to be processed and accounted in receipt accounting.
Key Resources
- Oracle Supply Chain Management Cloud: Using Supply Chain Cost Management Guide available on the Oracle Help Center.
Role Information
- Job Role Name and Code:
- Cost Accountant (ORA_CST_COST_ACCOUNTANT)
Get Overhead Rates for Standard Costed Make Items Using REST Services
Use the Get Overhead Rates for Standard Costed Make Items REST API to retrieve the plant and work center overheads that have been defined in Oracle Cost Management Cloud. Using this REST API, you can query –
- Published and unpublished overhead rates.
- Overhead rates with fixed and percentage absorption types.
- Overhead rate details including cost elements and expense pool information.
You use the Get Overhead Rates for Standard Costed Make Items REST API to integrate with external systems that require the overhead rates setup. For example, you may want to estimate the total cost (material and overhead costs) of a configured item before booking its sales order. In this case, you can call this API to get the effective overhead costs set up for the model item as of the order date for your organization.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- REST API for Oracle Supply Chain Management Cloud Guide, available on the Oracle Help Center.
Role Information
- Privilege Name and Code:
- Manage Overhead Rates for Standard Costed Items by Web Service (ORA_CST_STD_OVERHEAD_RATES_WEB_SERVICE)
- Job Role Name and Code:
- Cost Accountant (OA_CST_COST_ACCOUNTANT)
Use Primary Salesperson as an Additional Subledger Accounting Source
The following sources are available when you create account rules, mapping sets, and description rules for sales order issue event class:
- Primary Salesperson
- Primary Salesperson Number
- Primary Salesperson Revenue Account
Steps to Enable
You don't need to do anything to enable this feature.
Tips And Considerations
- To determine if the sources are mapped to the event class that you want to use, refer to the Manage Subledger transaction Objects task in the Setup and Maintenance work area.
Key Resources
- Oracle Supply Chain Management Cloud: Implementing Manufacturing and Supply Chain Materials Management Guide, available on the Oracle Help Center.
Role Information
- Job Role Name and Code:
- Cost Accountant (ORA_CST_COST_ACCOUNTANT)
Capture Additional Tax Determinants in a Brazilian Fiscal Document
Use the following new tax determinants in Oracle Fiscal Document Capture Cloud to drive appropriate calculation of Brazilian taxes.
- Tax classification code
- Location of final discharge
- Assessable value
These determinants display in the Line Details section of the Manage Fiscal Document page. When you import a fiscal document, if the location of final discharge and tax classification code is the same in all source documents, these determinants are populated from the applicable source document.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Fiscal Document Capture Guide, available on the Oracle Help Center.
Role Information
- Privilege Name and Code:
- Capture Fiscal Document (CMF_ENTER_FISCAL_DOCUMENT)
- Call Tax Service (CMF_CALL_TAX_SERVICE)
- Job Role Name and Code:
- Fiscal Document Specialist (ORA_CMF_FISCAL_DOCUMENT_SPECIALIST)
Use Enhanced Document Derivation When Importing Brazilian Fiscal Documents
When a supplier sends a fiscal document, the fiscal document doesn’t always reference the underlying purchase order, line, and schedule information. Previously, when you imported a fiscal document that didn’t reference the source document, you cleared each exception individually. Now when you import a fiscal document, the matching source documents are associated, limiting manual intervention for exceptions.
The following information is used to determine the applicable source documents.
- CNPJ number to determine supplier or customer (if RMA)
- Associated business entity for the ship to taxpayer ID
- Fiscal document item number
- Purchase order header status
- Purchase order schedule status
If more than one match is found, the results are sorted by requested delivery date, promised delivery date, and header level creation date and ordered by oldest line and schedule.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Fiscal Document Capture Guide, available on the Oracle Help Center.
Role Information
- Privilege Name and Code:
- Capture Fiscal Document (CMF_ENTER_FISCAL_DOCUMENT)
- Job Role Name and Code:
- Fiscal Document Specialist (ORA_CMF_FISCAL_DOCUMENT_SPECIALIST)
Supply Chain Financial Orchestration
Process Referenced RMA as Unreferenced When Forward Flow Can't Be Determined
When your customer returns a product that was originally shipped on an intercompany sales order, Supply Chain Financial Orchestration uses the original shipment reference of the forward flow sales order that is referenced. If the shipment cannot be determined, you must clear the exception from the Monitor Financial Orchestration Execution page. In certain scenarios, you may not have original shipment reference and clearing exceptions on a case by case basis is time-consuming. This feature enables you to automatically process referenced customer return as unreferenced when the forward flow cannot be determined.
- Referenced customer return against migrated sales order
- Referenced customer return against bill-only sales orders
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Supply Chain Financial Orchestration Guide, available on the Oracle Help Center.
Role Information
- Job Role Name and Code:
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
- Privilege Name and Code:
- Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV)
Ignore Financial Orchestration for Bill-Only Flows
When you set up a financial orchestration flow for non-shippable sales, you can enable the flow for a bill-only process. Sometimes, you don’t need a bill-only process even though there is no shipment involved. In these cases, you can set a system option to ignore all financial orchestration for bill-only flows. The scenarios in which you might want to use this include:
- Credit only customer returns against an intercompany drop shipment sales order
- Bill-only flows for shippable items
You set up this option in the Manage Supply Chain Financial Orchestration System Options task in the Manufacturing and Supply Chain Materials Management offering in the Setup and Maintenance work area.
Manage Supply Chain Financial Orchestration System Options Page
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Supply Chain Financial Orchestration Guide, available on the Oracle Help Center.
Role Information
- Job Role Name and Code:
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
- Privilege Name and Code:
- Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV)
Use Enhanced Financial Orchestration Qualifiers for Customer Drop Shipment Flows
You set up a financial orchestration qualifier to help determine how a financial orchestration flow runs. When you set up a qualifier, you select an attribute or parameter, which is used to define a rule that determines when the qualifier is invoked in a financial orchestration flow. For example, setting the new supplier country attribute to Germany in a drop shipment flow determines that the qualifier is only invoked when the supplier is from Germany, rather than a different country. When setting up qualifiers, you can use the following new attributes:
- Supplier Related: supplier, supplier site, supplier country
- Customer Related: sold to party, country of sold to party, ship to party, ship to address, ship to country
- Order Related: order type, order management business unit
You set up qualifiers using the Manage Financial Orchestration Qualifiers task in the Manufacturing and Supply Chain Materials Management offering in the Setup and Maintenance work area.
Create Financial Orchestration Qualifier Page
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
- Oracle Supply Chain Management Cloud: Using Supply Chain Financial Orchestration Guide, available on the Oracle Help Center.
Role Information
- Job Role Name and Code:
- Supply Chain Application Administrator (ORA_RCS_SUPPLY_CHAIN_APPLICATION_ADMINISTRATOR_JOB)
- Privilege Name and Code:
- Maintain Supply Chain Financial Orchestration Flow (FOS_MAINTAIN_SUPPLY_CHAIN_FINANCIAL_TRADE_AGREEMENT_PRIV)