Update 19D

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	Feature	Notes
08 APR 2020	Oracle WMS Cloud Mobile App	Updated document. Revised feature information.
07 APR 2020	New Filter Option in Item Barcode UI	Updated document. Delivered feature in update 19D.
07 APR 2020	Point of Sale Interface Enhancements	Updated document. Delivered feature in update 19D.
07 APR 2020	Pull Pallets Equal to Defined Value in a Single Task Using RF Move LPN	Updated document. Delivered feature in update 19D.
07 APR 2020	View Consolidated Inventory in New Item Inventory by LPN UI	Updated document. Delivered feature in update 19D.
07 APR 2020	Warning Message for Serial Numbers in RF Receiving	Updated document. Delivered feature in update 19D.
07 APR 2020	Additional Support for Group by Priority Date	Updated document. Delivered feature in update 19D.
16 MAR 2020	SFTP PUT Scheduled Job for Multiple Facilities	Updated document. Delivered feature in update 19D.
16 MAR 2020	Simplify Document Label Designer Font Type Menu	Updated document. Delivered feature in update 19D.
16 MAR 2020	Upload and Download Reports in Web Reports	Updated document. Delivered feature in update 19D.
16 MAR 2020	Prevent Errors during Login	Updated document. Delivered feature in update 19D.
16 MAR 2020	Support for Ratelinx Ending	Updated document. Delivered feature in update 19D.
16 MAR 2020	Authenticate Users with Auth Token API	Updated document. Delivered feature in update 19D.
23 DEC 2019		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.

Give Us Feedback

We welcome your comments and suggestions to improve the content. Please send us your feedback at owms-cloud-comms_us@oracle.com.

Feature Summary

Functional Enhancements

Prevent Shipping LPNs with Serial Mismatch

Updates have been made to the Outbound Load UI, related to the Ship Load button. Now, any messages related to Ship Load (such as 1337, 1338) which have the Auto-Reject checked will not allow you to continue. This mainly impacts messages related to LPNs with a serial mismatch present.

Additional details for this update include:

• You will be provided the message but have to go back and correct any mismatched OBLPNs, by either removing the LPN from the load or adding the missing serial numbers.
• If message 1338 has the Auto-Reject flag unchecked, the system will give you the option to continue by selecting yes. The load will continue and ship.

Steps to Enable

1. From the Message Codes UI, select the Facility Message Code.
2. Click the Edit Facility Message Configuration button.
3. Select Enabled and Auto Reject to enable the message alert for LPNs with a serial mismatch.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Extend Additional Reports to Honor the Matching Criteria in Company Report Type UI

Updates have been added to the Company Report Type UI to add support so that the following report types work with existing matching criteria:

• Commercial Invoice (COMM_INV)
• Shipper’s Export Declaration (SED)
• Export Shipment Packing List (ESPL)

These reports now map to the following fields:

• Order type
• Ship Via
• Ship to country
• Cust Field
• Cust Field

Steps to Enable

1. To generate a report, from the Outbound Loads UI, click “Commercial Invoice”, “Export Shipment Packing List”, or “Shipper’s Export Declaration.” 
2. In the Company Report Type UI, configure with subreport type “WebReports”.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Unification of Oracle Warehouse Workforce Management Cloud and Oracle Warehouse Management Enterprise Cloud

To better align the Oracle WMS Cloud and Oracle WFM Cloud applications, WFM screens have been merged into the WMS application.  You now have the option to see WFM reports in WMS.  Also, all the WFM menus are now available in WMS. There is now only one URL and a single login to access both WMS and WFM functionality. However the sync between WMS and WFM still has to be setup and this has now been simplified.  You now have the ability to setup data sync between WMS and WFM using scheduled jobs without having to rely on support.  You can adjust the frequency of the jobs to meet your needs.

To support WFM functionality, the following scheduled jobs have been added in WMS:

1. Run WMS WFM Interface – Syncs up user activity data between WMS and WFM tables
2. Purge WMS Activity Track – Clear user activity data older than configurable number of days
3. Process Stage Track Record – Validates and moves user clock-in/clock-out information from stage tables to WFM tables  
4. Purge Stage Track Record – Clear user clock-in/clock-out data older than configurable number of days

Steps to Enable

To enable WFM for a facility, set Facility parameter “WRITE_WMS_ACTIVITY_RECORDS” to Yes.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Support for Ratelinx Ending

Previously, Oracle WMS Cloud supported Ratelinx as a carrier integration. However, as of April 2019, Ratelinx is no longer supported. To support this change:

1. Ratelinx has been removed from the Carrier Integration type drop-down in Oracle WMS Cloud.
2. Ratelinx de-manifest is no longer supported.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Prevent Errors During Login

An enhancement has been added to the Oracle WMS Cloud login button, so that in cases where the user clicks the login button, the system will disable the login button. Previously, users were getting the error "Cannot query "lgf_blrsupport": Must be "AuthUser" instance."  This login button update will prevent multiple login button clicks while the application loads. This update will also prevent users from getting login errors when logging in from multiple browsers.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Upload and Download Reports in Web Reports

Previously, in Web Reports, you would design a report in your test environment, and then you would need to re-design the report again in your production environment. Now, you can download the report from Web Reports and then upload the same report to your production environment.

Report upload and download options will now be available for users with the following roles:

• ADMINISTRATOR
• APP-ADMIN
• MANAGEMENT

NOTE: Non-administrator role users will NOT be able to view this option at all. Users with permissions can download/upload different types of reports like ExpressView, Express Report, Advanced Report and so on.

Steps to Enable

1. From the Web Reports UI, Reports menu, select the report you would like to download or upload.
2. Select the three slash sub-menu icon.
3. Select download or upload.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Simplify Document Label Designer Font Type Menu

Document Label Designer has been enhanced to simplify the current list in the Font Type drop-down menu.

NOTE: Arabic and Hebrew options may be present in the drop-down but are for future use and not currently fully supported.

The new updated list includes:

• LBL_WESTERN_EUROPEAN

If the user selects the Western European option, the user will be able to print in any of the following languages:ENGLISH, FRENCH, SPANISH, GERMAN, ITALIAN, ROMANIAN, CATALAN, RUSSIAN, POLISH, CZECH, UKRAINIAN, BULGARIAN, MACEDONIAN, SERBO_CROATIAN, GREEK,CYRILLIC, and LATIN

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Warning Message for Serial Numbers in RF Receiving

Prior to 19D, the system did not prompt any warning when the user scanned an unanticipated Serial number which was not present in a cartonized shipment.

Oracle WMS Cloud now includes a new warning message "Serial nbr % is not present on the shipment. Do you want to proceed?" that allows the user to accept and receive cartonized shipments after scanning any unintended serial numbers that are unavailable in the shipment detail.

IMPORTANT NOTE:

• The cartonized shipment should have the serial tracked item in Required, Validate, or allow Override status
• The LPN should have serial numbers mentioned in the details.

Additional details of this feature include:

1. You can search the warning message from the "MessageCodeView" UI with the message code (3101). You can configure this message (Auto-reject is unchecked) from the "Edit Facility message" configuration for a specific facility. By default, this message is enabled for all the facilities.
2. Users can configure the message as an error by enabling the Auto Reject checkbox from the Edit Facility Message Configuration screen.
3. If the message is configured as a hard error, then users cannot scan the serial number that is not available in the shipment details and users are directed to the serial scan screen. (When Auto reject checkbox is marked enabled for the particular facility.) 

Steps to Enable

To configure the message as an error:

1. From the Message Code View UI, search for the message code (3101).
2. Click the "Edit Facility message" action button.
3. Select the Facility, and check the "Auto Reject" checkbox. Click Submit.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Integration Enhancements

Purge Inventory History and Allocation Records

To improve the management of data and system performance, the following enhancements have been added to the system:

• Inventory history records that are in canceled status will be purged, but not extracted.
• Allocation records tied to OBLPN records will be purged ONLY if the OBLPN is in a status of SHIPPED or after SHIPPED (i.e. shipped/delivered/lost/canceled.)

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

WMS Cloud to SCM Cloud Integration Configurator

The guided setup process prompts for the information needed to automatically deploy the appropriate OIC process flows.  This update includes the current set of available OIC-based process flows:

• Receipt Advices for Purchase Orders
• Receipt Confirmations for Purchase Orders
• Shipment Requests for Sales Orders
• Shipment Confirmations for Sales Orders
• Inventory Transactions

 You can extend the pre-seeded integrations within OIC based on your company-specific requirements.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

New Action Code DTLUPDATE for Purchase Order, Inbound Shipment, and Order Interfaces

Some systems (when performing an update) only send the updated fields instead of the whole object. This reduces integration traffic, and improves processing times. Prior to 19D, any update/delete operation at the detail level for a Purchase Order (PO), Inbound Shipment or Order via the Input interface required users to send the entire header detail information. Previously, users needed to send the whole header values and whatever they sent would override current values,

In 19D, a new action code (DTLUPDATE) is available in the Purchase Order, Inbound Shipment, and Order Interfaces that allows you to create, update, and delete values at the detail level by keeping the header detail values intact each time when a new file is interfaced with only the key header fields. That is, the values on the non-mandatory fields are retained with the original value instead of updating the values to null.

NOTE: DTLUPDATE is available at the header level. If an update or delete needs to be done at the detail level (and there is no need to update or delete header values), then you can also use the new action code DTLUPDATE at the header level. You still need to send the key header fields, so that the system can identify the detail that needs to be updated. If you would like to update/delete the header information as well, then you need to use previous action codes such as update or delete.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

SFTP PUT Scheduled Job for Multiple Facilities

Previously, the SFTP PUT files scheduled job supported only one facility and users needed separate jobs to transfer the output files for each interface type. Now, you can configure a single SFTP PUT scheduled job (Multi Facility - SFTP PUT Files) to generate the files and place them in a relevant folder across multiple facilities for a particular interface type. This will reduce the number of scheduled jobs you'll need to create in a multi-facility environment.

This scheduled job accepts the following parameters:

• Hostname
• SFTP User
• Password
• Port
• Remote Directory
• Remote Sub Directory
• Interface
• File Search Pattern
• Max files to transfer
• WMS username

Refer to the following table for descriptions and detail about these parameters:

Parameter	Description
Hostname	Your remote SFTP hostname. For example: sftp://clienthost.com
SFTP User	Your remote SFTP user. For example: myremotesftp
Password	Your remote SFTP password. For example:  567Password!
Port	SFTP Port server. The default port is 22.
Remote Directory (Required)	Root folder where the file will be transferred to.  At least one folder with an absolute path (/data for e.g.) must be provided.
Remote Sub Directory (Optional)	Sub directory under the Remote Directory where the file(s) will be transferred. If left blank, this job will replicate the WMS folder structure on the remote system, starting with each facility. The following are examples: Left blank - files will be under <remote_directory>/facility/output/<interface type> Specific Path is provided, say folder1/folder2 - Files will be under <remote_directory>/folder1/folder2 Specific Path with keyword {fac}, say {fac}/files - Files will be under <remote_directory>/facility1/files, <remote_directory>/facility2/files etc. "{fac}" is a keyword which allows the end user to still maintain a facility-based separation of files without recreating the complete folder structure
Interface (Required)	Represents a valid output interface. Attempting to provide an un-supported interface will give a meaningful error with the supported interfaces. Currently, the supported interfaces are:  NOTE: these are case-sensitive. orderverification iblpn_info custinvsummary lpn_inventory shipping invsummary distribution_info pallet_shipping_info cntrshipping wavepickinfo oblpn_shipping_info ibshipment manifest invhistory iblpn_report route_instruction
File Search Pattern (Required)	Pattern to pick up files from WMS. for example, CINS*.csv or CINS*. Note - "," comma is NOT supported here. "CINS,IHT*" will not work.
Max files to transfer (Optional)	For one execution of the job maximum number of files to transfer. Leave blank to transfer all files
WMS username	User eligible for the COMPANY under which all facilities will be considered for this job.

Steps to Enable

1. From the Scheduled Jobs UI, create a Scheduled Job with Job Type Multi-Facility - SFTP Put Files.
2. Complete the following Job Parameter fields:
   • Hostname
   • SFTP User
   • Password
   • Port
   • Remote Directory
   • Remote Sub Directory
   • Interface
   • File Search Pattern
   • Max files to transfer
   • WMS username

   NOTE:  Remote Directory, Interface, and File Search Pattern are required fields.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Point of Sale Interface Enhancements

The Point of Sale (PFS) interface job processes messages for all eligible facilities of the interface user. However, the ordering was based on the facility. This could cause some issues when sales and returns happened in different facilities for the same inventory.

For example, if an inventory is sold in Facility 1 and returned to Facility 2 and Facility 2 records are processed before facility 1 then the return message will fail. The issue is more important when serial numbers are used.

This update includes the following changes:

• WMS will now process Point of Sale interface so that records are processed in the order they were submitted without ordering by facility.
• While looking up previous sales to process a return, WMS will NOT include ANY facility check (including eligibility checks). This is being done because the user setup to do the return may not have eligibility to the facility where the sale happened. As long as the sale transaction id and the user's company are the same, WMS will still process the return.
• Given that  a single PFS job (still) processes across multiple facilities the process input files multi fac job will IGNORE PFS files. Users need to switch from using process input files multi fac jobs to process input files jobs for PFS interface only. The PFS interface was never compatible with the process input multi fac job and this is being enforced now. 

NOTE:  The PFS interface is not compatible with the process for the Input Multi Facility scheduled job. Users should always use the Process Input Files Scheduled job for PFS interface instead of the Process Input Files Multi Facility Scheduled job.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

REST APIs

Available Yard Location REST API

The first Available REST API will identify yard locations with available capacity. After fetching this API, you will get the first yard location with capacity based on the yard location putaway sequence. If the putaway sequence is not configured, the fetch will display according to the yard location pick sequence. You first use this API to find which yard spot to use, and then you can use the Locate to Yard API to actually locate the trailer in a yard using the Locate to Yard REST API (POST .../entity/trailer/{id}/locate_to_yard/)

Upcoming IoT Fleet Monitoring enhancements plan to leverage a new REST API (First Available API) to help automate intelligent check-in of vehicles to the yard of your Oracle WMS Cloud facilities.

NOTE:  IoT is one example of where this API will be leveraged. However, this API can be used in other scenarios.

The following flow demonstrates how this REST API works with IoT FM to locate a trailer to the yard (when a dock is not available):

1. As soon as a load enters the warehouse geo-fence, IoT FM checks for dock door availability but does not find any.
2. IoT FM checks for available yard slot.
3. IoT FM locates trailer to yard.
4. IoT continuously monitors for next available dock door and checks-in.
5. Driver is notified of dock door.

You can Identify yard location by capacity using a GET request:

GET .../entity/location/yard/first_available

REQUEST 

The following are the Query String Filters for this API:

Name	Required	Type	Default	Description
facility_id		String		Facility context by id.
facility_id__code		String		Facility context by code.

• Only one of "facility_id" or "facility_id__code" is allowed per request.
• If no additional context is provided, the user's default facility/company will be used.

The following is an example GET request for facility ID:

GET .../entity/location/yard/first_available?facility_id=1

The following is an example GET request for facility ID code:

GET .../entity/location/yard/first_available?facility_id_code=STRAJB01

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.

Ship Load Using a REST API

You now have the option to Ship a Load with a new Ship Load API. This new API allows you to ship a load by uploading the load via ID or filter.

You can Ship the Load by ID via the following URL:

POST .../entity/load/{id}/ship/

You can Ship the Load by Filter via the following URL:

POST .../entity/load/ship/

This API includes the following features:

• Supports the ship load transaction for a load that is in the Loaded/ Loading Started /Checked Out status.
• An error is displayed if the load is in a "Cancelled", "Ship Load In Progress", or "Shipped" status.
• The ship load transaction can be performed either by providing the id or code for the company/facility along with the load number.
• A Ship Load confirmation file is generated after the load is shipped.

Once a load is shipped via the Ship Load API, the following applies to Inventory History Transaction (IHT) records:

• Inventory history IHT -3 '3 - Container Shipped' is written with respect to each container present on the load.

• For shipped loads with OBLPNs associated with asset inventory history, IHT- 58 '58 - Asset Shipped' is written with respect to each OBLPN associated with an asset.

• Inventory history IHT- 60 '60 - Load Shipped File' is written for the outbound Load shipped.

The Ship Load API supports the following validations:

• Ship Load API supports Order type with ''Single Order on multiple Loads':
  • If "Single Order on multiple Loads" is set to "Do not Allow" in the order type, the system displays the error message: "Load has Order/s marked to Prevent one order on different loads with Error."
  • When an order is in Packed status but only some of the packed OBLPNs are loaded.
  • When an order is in Packed status but some  OBLPNs are loaded to different loads.
  • For OBLPNs with pending audit if the Company parameter "ALLOW_LOAD_SHIP_WITH_AUDIT_PENDING" is set to no.

Company Parameter REQD_FIELDS_FOR_SHIPPING is defined:

• When the required fields configured for the parameter 'REQD_FIELDS_FOR_SHIPPING ' are not defined for the targeted load.
• When one of the container item on the load is serial number tracked and the number of serial numbers allocated do not match with the count of serial numbers present in the container.

SERIAL NUMBER VALIDATIONS 

• If company parameter ALLOW_LOAD_SHIP_WITH_AUDIT_PENDING = False and company parameter SERIAL_NUMBER_TRACKING_LEVEL is 1 or 2

• If  company parameter SERIAL_NUMBER_TRACKING_LEVEL is 0 or Non serial tracked items exist and company parameter ALLOW_LOAD_SHIP_WITH_AUDIT_PENDING = False

• This API will not show you any warning message like the UI or RF, and it will proceed with the Ship Load transaction.

• The Ship Load API does not generate multiple outbound files.

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.

Manage Item Image Using a REST API

In Oracle WMS Cloud, you have the option to upload an item image via the Item and Scheduled Job UIs. To upload an item image via a Scheduled Job, you run the init stage interface by placing the image files in the required folder. You can upload/update an image defined for a single item through the UI. In 19D, the system is now able to upload/update an image via a REST API. A new API "image_upload" is available that allows you to update an image either by Item ID or Item by Filter.

You can upload an image item by ID via the following URL:

POST .../entity/item/{id}/image_upload/

Example request body parameters:

{

"options": {

"image_data": "Enter the image URL"

}

}

You can upload an image item by Filters via the following URL:

POST .../entity/item/image_upload/

The following filters can be used in the parameters section of the request body to support item filters:

• company_id

NOTE: This additionally allows filtering on company code: "company_id__code"

Example request body parameters:

{

"parameters": {

"company_id__code": "Enter the company code",

"barcode": "Enter the items barcode"

}

}

Additionally,

1. The API accepts only valid Base64 format. 
2. Supports image formats such as gif, jpg, jpeg, png.
3. Any image greater than 200x200, then the API resizes the image to a max size of 200 X 200 pixels.

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.

Pick Confirm Using a REST API

The following are additional REST APIs that support the Oracle WMS Cloud Mobile App:

NOTE: The Oracle WMS Cloud Mobile App is one example of where this API will be leveraged. However, this API can be used in other scenarios.

MIGRATED LEGACY PICK CONFIRM API

Previously, the legacy Pick Confirm API required a Material Handling Equipment (MHE) system to be specified since it is designed to work with MHE waves. The pick confirm API uses specified MHE systems to match against the allocations. Its also used to lookup a parameter on the MHE system that controls a delay in the pick confirm close message processing. This new style API can be leveraged with or without an MHE system.

Also the API works only asynchronously and returns immediately after submitting a celery task for later processing. The following three new REST APIs (which are based on the legacy Pick Confirm API) have been added to support the Oracle WMS Cloud Mobile App:

PICK CONFIRM   

The Pick Confirm API tells the system information about what is being picked/packed. This API supports non-MHE mode and is a migration of the legacy "pick_confirm" API.

NOTE: Only JSON and XML formats will be accepted.

This API supports features of the legacy API including the following new parameters:

• mhe_mode_flg - true/false; default true
• async_flg - true/false; default true
• short_flg - true/false; default false
  • Replaces using the legacy "action_code" = "SHORT".

The Pick Confirm API can be called using the following POST request:

POST ..lgfapi/v10/pick_pack/pick_confirm/

These represent the request parameters required for a single pick/short:

Name	Required	Type	Default	Description
facility_id		Integer		Facility context by id.
facility_id__code		String		Facility context by code.
company_id		Integer		Company context by id.
company_id___code		String		Company context by code.
wave_nbr	X	String		Associated wave.
order_nbr	X	String		Associated sales order.
item_alternate_code	C	String		Item identifier.
item_barcode	C	String		Item identifier.
qty	X	Number	0	Quantity to be acted upon.
batch_nbr		String		Inventory batch/lot.
uom_qty		Number		Filter on Case or Pack quantity when searching for allocations.
allocation_uom		String		"UNITS", "PACKS", or "CASES".
reason_code		String		Reason for short.
pick_location	C	String		From location.
from_container_nbr	C	String		From container.
to_container_nbr	C	String		LPN inventory is packed into. Not required for short.
update_inventory_on_short_flg		Boolean	False	Also short source inventory on pick short?
close_container_status		String	"packed"	Final OBLPN status: "picked" or "packed".
short_on_close_flg		Boolean	False	Should any remaining unpacked quantity shorted?
mhe_system_code	C	String		MHE system.
short_flg		Boolean	False	Is this a short?

CLOSE LPN 

The Close LPN API replaces the legacy pick confirm API when the action code is closed. While performing pick and pack operations (either non cubed active picking or cubed picking), the Close action code indicates to WMS that the Outbound LPN being picked needs to be closed.

This API supports features of the legacy API including the following new parameter:

• async_flg - true/false; default true

The Close LPN API can be called using the following POST request:

POST ..lgfapi/v10/pick_pack/close_lpn/

WAVE COMPLETE

The Wave Complete API replaces the legacy API when the action code is Complete. This is an indicator to inform WMS that all picks are completed for that wave, and there are no more picks outstanding. When the Wave Complete API is invoked, the system performs the following:

• Any Outbound LPN's relevant for the wave_number shared in the API which are in In-Packing Status will be pushed to Packed Status.

• Any Outbound LPN's relevant for the wave_number shared in the API which are in In-Picking Status will be pushed to Picked Status.

• Any outstanding picks present for the wave number will be considered as shorted and not picked. The system will perform the relevant shorting updates and perform location/inbound LPN inventory updates based on the flag value shared in _update_invn_on_short_flg _ API argument.

This API supports features of the legacy API including the following new parameter:

• async_flg - true/false; default true
  • When false:
    • Instead of submitting a celery task at the end for later processing, it should be immediately processed and a response returned.
    • On success, return a 204 - "No Content" HTTP response status with no response body.
  • When true:
    • Return HTTP response status 202 - "Accepted" with no response body.
      • Signals that we received the request and it was successfully submitted for processing.

The Wave Complete API can be called using the following POST request:

POST ..lgfapi/v10/pick_pack/wave_complete/

The following table provides details about the query string parameters:

Name	Required	Type	Default	Description
facility_id		Integer		Facility context by id.
facility_id__code		String		Facility context by code.
company_id		Integer		Company context by id.
company_id___code		String		Company context by code.
wave_nbr	X	String		Associated wave.
update_inventory_on_short_flg		Boolean	False	Also short source inventory on pick short?
close_container_status		String	"packed"	Final OBLPN status: "picked" or "packed".
reason_code		String		Reason for short.
mhe_system_code		String		MHE system.
async_flg		Boolean	True	Run API asynchronously?

Request JSON Example:

{ "facility_id__code": "FAC", "company_id": 1, "wave_nbr": "WAVE001", "update_inventory_on_short_flg": true, "async_flg" true }

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.

Get Next Task Operation Using a REST API

The Next Task API allows you to determine the next task via an API operation.

You can search for the next task using the following GET request:

GET .../entity/task/next_task

The following table provides details about the query string parameters:

Name	Required	Type	Default	Description
facility_id		Integer		Facility context by id.
facility_id__code		String		Facility context by code.
location_barcode		String		User's current location.
task_type		String		Required task type.
ordering_rule		String		Order tasks by rule name.

• Facility ID/Facility Code
  • If a value isn't provided, the user's default facility context will be used.
  • Task look up is done relative to the user's facility and eligible company contexts.

• Location Barcode
  • If provided, search for task within the same location area (if available) and/or pick sequence (if available).

• Task Type
  • If provided, search for task only of the given type.

• Ordering Rule
  • If provided, order the found tasks by the corresponding field(s) and return the top result.
  • The value accepted by the API is that of the Task Ordering Rule's description.

The following is an example GET request using location barcode:

GET .../entity/task/next_task?location_barcode=MY_LOCN_BRCD&task_type=MY_TASK_TYPE&ordering_rule=MY_RULE

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.

Sort LPN to Pallet Using a REST API

The Sort LPN API allows you to "sort" an LPN to a Pallet in a sort location mimicking what the RF Inbound Sorting process does. The RF modules include: RF Sort LPN, and RF Inbound Sort Location.

You can sort an LPN to a pallet in a sort location with the following POST request:

POST .../entity/pallet/sort_lpn/

The following table provides details about the Input Parameters/Filters used to identify the target pallet:

Name	Required	Type	Default	Description
facility_id		integer		Facility context by id.
facility_id__code		string		Facility context by code.
company_id		integer		Company context by id.
company_id___code		string		Company context by code.
pallet_nbr	X	string		Target sort pallet.

The following is an example body for Sort LPN to Pallet:

{

"parameters": {

"facility_id": 1,

"company_id__code": "FOO",

"pallet_nbr": "PALLET001"

},

"options": {

"container_nbr": "LPN001",

"sort_zone": "ZONE01",

"sort_location_barcode": "BRCD001",

"sort_to_inventory": "pallet-call-directed-putaway"

}

}

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.

Sort LPN and Close Pallet Using a REST API

The Sort LPN/Close Pallet API is used as part of the inbound sorting process which groups LPNs to pallets in sort locations. At the end of the sorting process, we close the pallet indicating no more LPNS are to be added. This API mimics the RF IB Sort LPN module which calls the Sort LPN Close IB Pallet back end entry point with parameters.

You can Sort LPNs and Close Pallet with the following POST requests:

• POST .../entity/pallet/close_inbound_sorting/
• POST .../entity/pallet/{id}/close_inbound_sorting/

The following table provides details about the Input Parameters/Filters used to identify the target pallet:

Name	Required	Type	Default	Description
facility_id		integer		Facility context by id.
facility_id__code		string		Facility context by code.
company_id		integer		Company context by id.
company_id___code		string		Company context by code.
pallet_nbr	X	string		Target sort pallet.

The following table details the functional options:

Name	Required	Type	Default	Description
create_replen_task_flg		boolean	True	Generate a replenishment task on close?
task_type_description		string		Required type description for generated replen task. Valid when create_replen_task_flg = True.

The following is an example body for Create Replenishment Task Flag:

{

"parameters": {

"facility_id": 1,

"company_id__code": "FOO",

"pallet_nbr": "PALLET001"

},

"options": {

"create_replen_task_flg": true,

"task_type_description": "My Task Type"

}

}

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.

Replenish to Active Using a REST API

You can use the Replenishment/Replenish to Active API to complete an open replenishment task for an active location.

You can replenish to active with the following POST request:

POST .../lgfapi/v10/replenishment/replenish_to_active/

The following table provides details about the Input Parameters/Filters:

Name	Required	Type	Default	Description
facility_id		integer		Facility context by id.
facility_id__code		string		Facility context by code.
company_id		integer		Company context by id.
company_id___code		string		Company context by code.

The following table details the functional options:

Name	Required	Type	Default	Description
task_id	C	integer		"id" of task to be completed.
task_id__task_nbr	C	string		Business key for task to be completed.
replen_location_id	C	integer		"id" of active location to be replenished.
replen_location_id__barcode	C	string		Barcode of active location to be replenished
qty		decimal	Allocation Qty	Quantity to replenish.

The following is an example body for Replenish Location ID Barcode:

{

"facility_id" 1,

"company_id__code": "COMPANY",

"task_id": 1,

"replen_location_id__barcode": "LOCN1"

}

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.

Authenticate Users with Auth Token API

Oracle WMS Cloud is enhanced with advanced performance improvements in terms of security aspects by introducing a new API "auth_token", a token-based authentication that allows users to access the application. On posting this API, the system generates a token that is used by other application's APIs to authenticate the user credentials and gain access permission to the application. This token-based authentication validates the user based on the following condition being true:

1. Verify the user's credentials based on a valid username and password.
2. The system attempts for Max failed login as configured in the "Company Security Config" for a company. On attaining the max number of attempts, the system displays "Sign in failed - Invalid username or password" error.
3. If the user attempts to login after the password life that is defined during the user creation, the system displays "Login failed. Password expired" error.
4. If the user tries to login via support user account, then the life of the account is limited to the number of days defined during account creation.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

User Experience and Usability Enhancements

Oracle WMS Cloud Mobile App

Built in Oracle Visual Builder, the Oracle WMS Cloud Mobile app features modern, graphical, mobile screens that can both display images and scan barcodes on both iOS and Android-based devices.  This update includes an initial, limited set of pre-seeded mobile UI transactions and features.  Coming soon to the Apple App Store and Google Play Store.

To download and install from the Apple store for iPhone:

1. Launch the Apple store,
2. Tap the magnifying glass on the bottom right to search for Oracle WMS Cloud Mobile App.
3. Tap Get to download and install for free.

To download from the Google Play store for Android:

1. Launch the Google Play store.
2. From the top of the screen, type Oracle WMS Cloud Mobile App and tap search.
3. Select the app from the search results to download and install for free.

NOTE: The app layout is optimized for phone sized screens rather than tablet sized screens.

ORACLE WMS CLOUD MOBILE APP FEATURES 

When you first open the application, you will need to review and accept the End User License Agreement before using it for the first time. These are some of the general features available in the application:

• You can setup multiple profiles or environments within the app that allow you to point the app to different WMS cloud environments.
• The app supports both single and multi-field barcodes using the existing configuration available in the WMS Cloud service.
  • The app can use the device’s camera to scan barcodes or can also work with a barcode scanner attachment that converts the barcode into keyboard input.
  • The app is integrated with the same menu system as the existing Web and text based Mobile RF UI’s. A new menu type of “VBCS Mobile” and a new screen type “VBCS Mobile” have been added to the WMS Cloud product.  
  • The app supports the same literals and language translation configuration and features available with the WMS Cloud web UI and the text based Mobile RF.
  • The app supports display and upload of images. 
  • Some transactions have a screen configuration (settings icon) in the top right, where you can configure fields on that screen.
  • This initial version of the app has a limited set of WMS transactions. This list of transactions will increase with future updates.
  • The typical app menu icon (hamburger icon) on the top left has options to show the EULA and to logout. The menu of WMS transactions is displayed on the main screen itself.

APP PERMISSIONS 

• When accessing the device camera for the first time, it will request permission to access the camera.
• When uploading a photo from the device for the first time, the app will request permission to access your device photos and files.

ENVIRONMENT SETUP

Touch the environments icon on the bottom right to start adding a new environment. At least one environment must be setup before the app can login. You can use the + sign on the top right of the environments page to add additional environments. This way you can setup both your production and test environments (or more than one test, in case you have more). You will need to know the full URL of the WMS Cloud service that has been assigned to you.

An environment consists of:

• A name which can be anything the user prefers
• The instance name: the initial part of the domain name of the URL
• The environment code: the last part of the URL

For example:

https://z3.wms.ocs.oraclecloud.com/cust_env

Here z3 is the instance name and cust_env is the environment code

LOGIN

Chose an environment from the environment drop-down and enter a username and password. This is the same user and password that you would use to login to the Web UI or the text based mobile RF applications

The app displays the main mobile app menu. If it is blank, that means a Mobile App menu has not be setup for your user. This must be configured using the Web UI:

• Create a menu of type “VBCS Mobile” that consists of screens of type “VBCS Mobile”
• Assign the menu to a group.
• Make this group the default group for that user

TRANSACTIONS 

In update 19D, the following “VBCS Mobile” screens (transactions) are available:

ITEM INQUIRY 

• Look up an item by either keying in the item code or scanning its barcode.
• This will bring up a list of items. There may be more than one in case a partial item code was used for the search.
• Click on one item in the list to get more detailed information, including the picture of the item.
• You can touch the edit pen icon next to the image if you want to change it. You can either take a picture using the device camera or select an existing image on the phone.

CREATE LPN 

• Create an LPN for single or multiple items

NOTE: Batch and item attributes are not supported.

LPN INQUIRY 

• Allows you to type or scan to search for an LPN number.
• Displays LPN status (Inbound or Outbound)
• Tap the info to view IB Shipments details (Inbound LPN) or Order Detail (Outbound LPN)

RECEIVE LPN 

• Tap settings icon in top right of screen to adjust LPN screen configuration.
• Type LPN number, or scan with camera.
• Tap barcode screen and camera opens to scan.
• Type or scan location.
• Optionally the LPN can also be cross docked. A matching cross dock order must be available for the allocation to succeed.

NOTE: Currently, Receive LPN only supports receiving cartonised ASNs.

SHIP OBLPN

• Allows you to Ship OBLPN by typing or scanning OBLPN,
• Select output API to be invoked (LPN Inventory or OBLPN Shipping information.)

Steps to Enable

1. Open the Oracle WMS Cloud Mobile app.
2. Tap the + icon at the bottom right to setup your environment details.
3. At the login prompt, enter your WMS username and password.
4. Tap Signin.

Group Reserve Inventory by Priority Date

Previously, the Reserve Inventory Inquiry screen displayed records based on inventory identifiers like batch number, inventory attributes and priority date. The "Priority Date" column (added in 19C to the Reserve Inventory Inquiry), displayed records in reserve inventory inquiry by priority date. For some customer flows, the user may not want the system to display the reserve inventory records based on the Priority Date value, as it increased the number of rows on the Reserve Inventory UI. Users who did not need to track priority date (which is used in FEFO allocation) would end up seeing multiple records for a reserve location when there were multiple LPN's with the same sku if LPN's were received on different dates (due to different priority dates).

In 19D, Oracle WMS Cloud now allows you to group the Reserve inventory Inquiry records based on the Priority Date value by explicitly adding the priority date column to the data grid. Upon adding the Priority Date, the system breaks the inventory records based on the priority date and displays the records accordingly.

When the Priority date is not added to the data grid, then the system displays Reserve Inventory records without considering the priority date for grouping.

The following example illustrates the update:

Let’s say a Reserve Location has two LPN's with the same sku and different priority dates.

• Inbound LPN LPN 1 with SKU-1 having priority date as 20-10-2019 with a quantity of 10 units
• Inbound LPN LPN 2 with SKU-1 having priority date as 22-10-2019 with a quantity of 10 units

RESULT:

With Priority Date added to the data grid:

The system displays multiple records:

Location	Sku	Qty	Current LPN's	Priority Date
Location-1	SKU-1	10	1	20-10-2019
Location-1	SKU-1	10	1	22-10-2019

With Priority Date not added to data grid (default behavior):

Location	Sku	Qty	Current LPN's
Location-1	SKU-1	20	2

NOTE: Existing customers who have added priority date to the UI data grid will see the records displayed by priority date.

The above behavior is specific to the Reserve Inventory UI only. The system now displays all the Reserve Inventory columns in the default view except for the Priority Date column.

The following columns are added to the default view of the Reserve Inventory UI:

• Attribute H to Attribute O
• Current Qty in Packs
• Current Qty in Case
• Allocated Qty in Pack
• Allocated Qty in Case

The following are additional details about the priority date field/column:

• By default, the Priority Date field is not added to the data grid of the Reserve Inventory UI.
• No fields other than the Priority Date are displayed with the select/deselect option.
• The Priority Date column is also available in the drill down window of the Reserve Inventory Inquiry available via the Current LPN's hyperlink from the first screen of Reserve Inventory Inquiry.
• Export to CSV option will have priority date column displayed.

Steps to Enable

To group inventory records by priority date, from the Reserve Inventory view list, add the "Priority Date" column.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Additional Support for Group by Priority Date

Prior to 19D, the user had the ability to select/deselect the column from the Reserve Inventory UI. In 19D, an update was made where all the columns were displayed in the data grid except the Priority Date column. This change in the UI caused inconvenience for the customer.

For better usability, the Reserve Inventory UI is enhanced back to an option where the user can Select/Deselect the data grid column along with the Priority date column.

NOTE: The Inventory records are grouped by priority date when the user selects the Priority Date column. This behavior remains unchanged.

Also, an allocated quantity field displays the allocated value for the order which is used for packing and shipping from the warehouse. During a consolidate and replenishment flow, the replenishment allocated quantity is considered and displayed. Now, as part of this enhancement, the system does not display replenishment allocated quantity in the allocated quantity field of the Reserve Inventory UI.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

New Filter Option in Item Barcode UI

A new filter option "Item code" is now available in the search criteria of the Item Barcode UI that provides flexibility for users to be able to search item barcode by entering partial characters of item code. With this advanced select, the users can search for a particular single item with an item code text box that is added as a filter and fetch the records

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Pull Pallets Equal to Defined Value in a Single Task Using RF Move LPN

To save time for warehouse users during full LPN Picking, enhancements have been added to the RF Move LPN transaction, so that upon defining values in the "max-pallets-to-pull" screen parameter, the system now allows you to pull pallets equal to the value defined in the screen parameter in a single task. Also, upon creating a new task for the pending inventory, the system now has the same task priority value as the original task from which the new task was started.

Now, when the configured value in the screen parameter is more than one, users can end picking on the current pallet and start with a new pallet using a new hot key Ctrl-N (Pick Next Pallet.)

NOTE:  When pallets pulled into a respective task are less than the value configured in the screen parameter, the user still has the option to move the pending allocation to the new task. Upon entering Ctrl-E, the system will end the current task and creates a new task for the pending allocation. Also note, Ctrl-E has been renamed from "End Pallet" to "End Picking."

Steps to Enable

1. In the RF, go to the RF Move LPN (rf.inbound.cwrfmovelpn) screen parameter.
2. When you configure a value greater than one in the screen parameter  "max-pallets-to-pull" , the system should allow you to pull pallets equal to the value defined. 

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

View Consolidated Inventory in New Item Inventory by LPN UI

A new UI, Item Inventory by LPN is available in Oracle WMS Cloud that provides a consolidated view of all the LPN inventory (inbound and outbound) in the warehouse. This new UI replaces the deprecated IB LPN Inventory (IbLpnInvView) and OB LPN Inventory (ObLpnInvView) UIs in the system. Additionally, the previously configured screens "IB LPN Inventory" and "OB LPN Inventory" UIs are deprecated and are no longer available in the corresponding menu configuration.

Steps to Enable

1. Users need to configure the new module to the relevant groups.
2. Go to Modules > add Item Inventory by LPN.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

New Search Fields

Track User Activity with New Search Fields

To facilitate easy tracking of created or modified user activities and timestamps, Oracle WMS Cloud has added new fields. Create User, Create Timestamp, Modify User, and Modify Timestamp are now available in close to 60+ UIs in the application:

The following are some of the UIs where audit-related columns are available:

• Appointment
• Cubing Rule, Details
• Outbound Audit Rule
• Replenishment Template, Replenishment Rules
• Parcel Manifests
• Ship Via
• Work Order Wave Template
• Wave Template, Allocation Mode
• Trailers

NOTE: By default, these columns are not displayed on the UI grid.

Steps to Enable

You need to manually enable the audit columns from the view list to display the column on the selected UI. You can also sort the columns based on column selection.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Search Using Ship Via Option in Order Header UI

A new filter "Ship Via" search option is now available in the Order Header UI that allows you to filter the order containing a given ship via. The Ship via drop-down menu displays values in the format of "Ship Via Code/Description."

NOTE: By default, the Ship Via option displays a blank value.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

Filter Cycle Count Adjustment Based on Items

To further improve usability in Oracle WMS Cloud UIs, two new filter search fields "Item Code" and "Alternate Item Code" are available in the Cycle Count Adjustment Header view. These two fields allow you to filter the cycle count adjustment details so you can easily find the locations that have cycle count adjustments for these items.

NOTE: By default, these fields display a blank value.

Steps to Enable

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

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation

New Filter Search Options for Inventory, Wave Inquiry, and Manual Wave UIs

New filter search options and corresponding columns are now available in the following Oracle WMS Cloud UIs to help you better fine-tune your search results:

RESERVE INVENTORY UI

• Filter Options added in the Search Criteria are:
  • Alternate item code (Text box)
  • Location barcode (Text box)
  • Serial Nbr (Text box)
  • Location size type (Drop-down)

• Column added to the Data Grid:
  • Location size type

ACTIVE INVENTORY UI

• Filter Options added in the Search Criteria are:
  • Alternate item code  (Text box)
  • Location barcode (Text box)
  • Replenishment Zone  (Drop-down) - Displays Replenishment Zone code only.

• Column added to the Data Grid:
  • Location Barcode
  • Replenishment Zone

WAVE INQUIRY UI

• Order Type (Drop-down) -Displays Order Type description only and is available in the Wave Inquiry Detail UI.   

• Wave template (Text field).

MANUAL WAVE UI

• Filter Options added in the Search Criteria are:
  • Order Type (Text Box) - Displays Order Type description only.
  • Ship Via (Drop-Down)- Displays values in ShipViaCode/Description.

• Column added to the Data Grid:
  • Ship Via

NOTE: By default, these newly added columns are not displayed on the data grid.

Steps to Enable

1. From the Reserve Inventory UI, manually enable the Location size type column from the view list to display on the UI data grid. You can also sort the columns based on column selection.
2. From the Active Inventory UI, manually enable the Location Barcode and Replenishment Zone columns from the view list to display on the UI data grid.
3. From the Wave Inquiry UI, manually enable the Order type column from the view list to display on the UI data grid.
4. From the Manual Wave UI, manually enable the Ship Via column from the view list to display on the UI data grid.

Key Resources

• Oracle Warehouse Management Cloud - Update 19D Documentation