Update 23D

Revision History

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

Overview

HAVE AN IDEA?

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

GIVE US FEEDBACK

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

DISCLAIMER

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

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

Warehouse Management

WMS Common

Infer UOM from Alternate Item Barcode

In your warehouse, you would be dealing with the same Item in different UOMs that belong to the same UOM class. For example, you could receive an item in one UOM while fulfilling a sales order in another. The ability to transact an item in several UOMs simplifies transactions. Also, the ability to identify the item and the UOM in a single scan helps to reduce multiple scans in the warehouse, thereby enhancing warehouse user productivity and reducing user errors. In line with this, WMS now allows you to infer UOM from the item barcode scanned upon receipt. To do so, set the screen parameter for receiving qty-uom to 'Infer UOM from Item Barcode'. You must also configure the alternate item barcodes for the item.

Associate SAAS Application Configuration with Oracle Content Management (OCM/OCE) Configuration Detail

In order to integrate WMS with OCM, a parent record needs to be created in the SAAS App Configuration screen with details of the OCM parameter values. Creation of a parent record also creates a repository and channel in OCM for the parent and the IDs are stored in OCE Configuration Detail.  Similarly a dedicated SAAS App Configuration record can also be created for a particular facility/company in case values other than that on parent record are required to connect to OCM; and the repo, channel ID for the dedicated facility/company is stored in OCE Configuration Detail.  

There was previously no indicator in OCE Configuration Detail that indicated which records were reliant on the SAAS App Configuration parent record and which were not. This made it difficult to update SAAS App Configuration information. To assist you in this, a new field SAAS App Configuration ID is added to OCE Configuration Detail to distinguish between a parent record and facility-specific records in SaaS App Configuration.

Extend Support for Additional Screens in Configuration Export/Import Tool

We are expanding the configuration export/import tool capabilities to additional screens in the current release, allowing you to easily migrate and replicate UI configurations between facilities, companies, and environments. Some of the screens where we’ve added the action button for configuration export/import is available are: Input interface configuration, Vendor characteristics, Label Template, Replenishment Zone Type xref, Breaks view, Staffing plan view etc.

Extend Support for Additional Tables for Purge Handling

Implementing an automatic purging process improves system performance by eliminating old, obsolete data. This improves query performance and reduces processing times for other tasks that rely on these tables, as well as improving data integrity and reliability. It also reduces the possibility of errors or inconsistencies in subsequent operations and analyses. In this release we are adding the Serial Number History table as part of automated purge handling.

Inbound Logistics

Support Receiving the Same Item in Different UOMs for the Same LPN

You may need to receive the same item in different UOMs in your receiving operations dependent on your storage or shipment requirements. Your warehouse user can now receive the same item in an LPN, in different UOMs of the same UOM class. This simplifies your inbound operations. To accomplish this, you must create a record in the Item Barcode UI screen and update the UOM and Quantity per UOM fields. 'Infer UOM from Item Barcode' is now one of the values for the 'qty-uom' screen parameter on the RF receiving module.

Improvements to Receiving REST API

Additional fields have been added to the Receiving REST API to validate and track po_nbr, po_seq_nbr, batch_nbr, expiry_date, manufacture_date, serial numbers, and inventory attributes when their values are provided in the API request. These are now available via REST API for both cartonized and non-cartonized receiving.

Enhance Rule-Based Selection Criteria Screens

Several new fields have been added to the selection criteria screens in Putaway Type Determination Rules, Movement Request Search in Replenishment Templates, Dynamic Wave Search in Wave Templates, Task Creation Template, and Cubing Rules. These extra fields will assist you in achieving precision in your inventory management activities by ensuring that goods are allocated to the required locations, that the correct orders are allocated during waving, and also task management and cubing during waving are optimized.

Inventory Operations

Generate Inventory Balance Snapshots by ERP Bucket

It is critical for your business to ensure the accuracy of your on-hand inventory at your warehouse. You must also ensure that the inventory is in sync between the ERP systems and your warehouse. To assist you in ensuring inventory accuracy, WMS now has the ability to generate an inventory balance snapshot at the ERP bucket level, which can be further broken down by expiration dates, inventory attributes, batches, and serials.

Support Cycle Counting the Same Item in Different UOMs for the Same LPN/Location

Items in your warehouse may be stored in different UOMs of the same UOM class for ease of inbound/outbound operations. So, when performing a cycle count to guarantee inventory accuracy, it would be more convenient if it could be done in the same UOM as how it is stored. WMS now allows you to cycle count the same item in different UOMs for the same LPN or Location, simplifying cycle count processes and reducing unnecessary case/pack opening while cycle counting, as well as minimizing counting errors.

Perform Create LPN in Cases and Packs

Apart from allowing primary UOM, it is critical for a warehouse handling goods in multiple UOMs of the same UOM class that your warehouse operator has the ability to Create LPN in cases and packs for inventory operations. This contributes to faster transactions but with fewer errors. With this in mind, WMS can now Create LPN transactions in cases and packs. To support this, a new module parameter 'qty-uom' has been added to the RF Create LPN screen, with module parameter options of Units, Packs, Cases, and Cases/Packs/Units.

Perform Non-Tasked Cycle Counting for a Specific Item in Deferred Mode

Your picking locations (active locations) may contain different kinds of Items kept in the same location or distinct batches of the same item. Earlier Cycle counting was not permitted in the deferred mode for any given item or item inventory combination. WMS now allows you to cycle count a specific item or item inventory combination in an active location in delayed mode. To enable this, set the parameter update-locn-invn-mode to 'counted items only' or 'counted item inventory combination'. This will help you to cycle count and approve specific Items without affecting the other items in the same location and ensuring inventory accuracy.

Auto Removal of Inherited Lock Code on LPN When Transferring from a Location

When relocating the LPN between locations (or departments), you may have requirements that the location lock code and the ERP summary bucket associated to the lock code be updated on the LPN. For example, if the received inventory is taken to a QC location for quality control, the LPN will be inherited with the QC location's lock code. However, once QC is completed and the LPN is taken out from the QC location, the lock code should be automatically removed. To help with this, a new checkbox 'Remove Inherited Location Lock on Unlocate' has been added to the Lock Code screen.

Support FEFO for Multi-Item LPN Allocation

In industries where inventory is expiry controlled, it is critical that items with the earliest expiry date get dispatched out of the warehouse to reduce inventory wastage. In addition to the existing FIFO (First-In-First-Out), LIFO (Last-In-First-Out), Quantity Ascending/Descending, and Location Pick Sequence methods, WMS now supports FEFO (First-Expiry-First-Out) allocation method during waving for Multi-Item LPN.

Add Velocity Code to Facility-Level Item Definition

The frequency with which your item is dispatched from a facility owing to demand varies, depending on factors such as geographical location, seasonality, consumer preferences, and so on. As a result, the same Item can have a different velocity in each of your facilities. WMS now allows you to add velocity code for an Item at the Item Facility level, assuring accurate velocity code for Items in each Facility.

Split Inbound LPNs Marked for Quality Control (QC)

You may have encountered situations in your warehouse when some inventory that has come in for quality control has a mixture of damaged and good items. In this scenario, the user would want to split the LPN in QC status, move the good inventory to a new LPN, and keep the damaged items on the LPN in QC status and then execute a quality check on this LPN.  WMS now allows you to do the same using a new screen parameter 'allow-split-for-qc-lpns' in the Split LPN module. This saves you time and optimizes the workflow as you can approve or reject the remaining inventory after splitting it in QC.

Outbound Logistics

Improvements to Planned Load Interface for Action Code at the Order Level

Load planning at your warehouse may be performed by Oracle Transportation Management (OTM) or other transportation systems, and the planned load information will be transmitted to WMS. In certain circumstances, the same order line may be split among multiple transportation loads, and these transportation loads may be rescheduled from OTM based on the multiple factors. WMS now allows you to update/replan transportation loads by supporting UPDATE and DELETE action code at the order detail level.

Support System Driven Alternate Location During Picking

When performing picking transactions, you may encounter instances in which there is no eligible item inventory at the location and must pick from an another location by manually overriding the recommended location. In this situation, the warehouse user is responsible for identifying and selecting the correct item inventory. WMS has been enhanced so that the system now calculates the next best place for picking inventory, allowing you to automatically locate alternate inventory locations and reducing the need for time-consuming and error-prone manual searches. You can now concentrate on the primary objective of picking products rather than hunting for inventories.

Extend Post Packing Transaction to Support Load Assignment, Manifesting and Pallet Handling

Previously, you had to switch between RF screens to execute post-packing adjustments for outbound LPNs such as Load Assignment, Manifesting, and Pallet Handling. To accomplish these operations, the RF module 'Post Packing OBLPN updates and handling' has been enhanced. A new screen parameter 'perform-load-assignment' has been added to allow you to assign load only after post packing operations have been completed. In addition, a new screen parameter 'perform-manifesting' has been added to assist you in manifesting the load. When dealing with outbound pallets, you can now adjust the 'container-type' parameter value to Pallet. These changes will help your warehouse user be more efficient by shortening the time between transaction executions.

Initiate Loading Based on Trailer Scan

Previously, your warehouse user could start loading by scanning the location or the load number. WMS now provides the capability of initiating loading by scanning the Trailer number connected with a Load. This helps to streamline your loading procedures and reduces errors when you initiate loading. In the RF Load Outbound LPN module, a new screen parameter "initiate_loading_by_trailer" has been added for the same.

Warehouse Workforce Management

Auto Clock In/Clock Out of Facility and Work Area

Most warehouses require users to clock in and out of the facility in order to record the time stamps of all users entering and exiting the warehouse/facility. However, the majority of this is done manually or using third-party time management software. Based on user actions, WMS now allows you to automatically clock in and out of the facility/work area. When you log into the RF, you will be immediately clocked in. When you do a work-area-specific operation, the system will now automatically clock you in to that work area as well. The system will also move between work areas based on where the activity is carried out. When your inactivity time surpasses the threshold set, the system will automatically clock you out as well.

WMS Mobile App

Support Lots and Expiry Date During Receiving

The WMS Mobile APP now supports receiving items with Batch/Expiry Dates in both cartonized and non-cartonized shipment scenarios. The batch and expiration prompt values would depend on the shipment type's 'Cartonized receiving batch and expiry prompt control' and 'Non-Cartonized receiving batch and expiry prompt control' values.

Delete Oracle Content Management (OCM) Files Using a REST API

With the ability to delete files associated with specific entities, this API streamlines the file management process and enhances your workflow efficiency.The File Delete API offers two methods for entity deletion - by ID and by filters. You can use this flexibility to tailor your deletion requests precisely to your needs.

Cloud SCM Integration

Predefined Integration Mappings from Inventory Management for Manufacturing and Maintenance Work Order Picking Request

As a manufacturer, you would need to move the components to various supply subinventory or work center/areas during the manufacturing process. It is critical on the shop floor to ensure that components are moved quickly, easily, and methodically from inventory locations in the warehouse to supply sub inventory or work centers/areas. Predefined integration mappings for Work Order Picking Request (Movement Request) from Oracle Fusion Cloud Inventory Management and Manufacturing/Maintenance to Oracle Fusion Cloud Warehouse Management are now available to help with this. These Oracle designed integration mappings have been prebuilt for Oracle Integration Cloud (OIC).

A work order is created in Oracle Fusion Cloud Manufacturing or Maintenance to begin the process. Following that, the work order is released and picking requests are created in Inventory Management. For reservable items, Inventory Management automatically creates a Movement request and high level reservations. In the case of non-reservable items, a movement request is created with no high-level reservations. The Inventory Management movement requests are then interfaced to WMS creating movement requests. Movement request lines for both Pick and Move, and Pick and Issue scenarios will get created in WMS.

Predefined Integration Mappings to Inventory Management for Manufacturing and Maintenance Work Order Picking Confirmations

Once the movement request is created in WMS, The replenishment wave program is used to generate allocations and tasks. Warehouse workers execute the tasks and validate the picks as the material is replenished from the source to the destination supply locations or to work centers. WMS generates inventory history, and inventory transactions are recorded, and reservations in inventory management updated. The picked quantity details and reservation details are utilized to update the Manufacturing or Maintenance work order component quantities. The movement request is closed when all the lines are picked.

Predefined integration mappings are now available for sending the work order picking confirmations (movement request pick confirmation) from WMS back to Oracle Inventory Management.

Predefined Integration Mappings to Inventory Management for Manufacturing and Maintenance Work Order Picking Cancellations

Depending upon the availability of your items/raw materials, the warehouse user may not be able to complete movement request picking in WMS and will have to resort to cancellation of the movement request line qty either fully or partially. Predefined integration mappings is now available for communicating when Movement Request lines are Shorted or Cancelled so that Oracle Inventory Management is aware that current movement request will not be utilized and that they don’t have to anticipate further picks against the movement request line.

Predefined Integration Mappings to Transportation Management for Order Line Split Across Different Planned Loads

A single order/order line may be shipped in a single load or multiple loads from Oracle Transportation Management (OTM) depending on the Order type, Order quantity, Container/Equipment type, or other deciding factors. These factors are taken into consideration when OTM plans the load and sends the planned load information to WMS. Predefined integration mappings are now available to handle the scenarios where order line is split across different planned loads.