My Oracle Support Banner

FA: SCM: OM: Fulfillment Line Shipped in WMS is Stuck with Error - Invalid lock code for order. (Doc ID 2972806.1)

Last updated on SEPTEMBER 12, 2023

Applies to:

Oracle Fusion Order Management Cloud Service - Version 11.13.17.11.0 and later
Information in this document applies to any platform.

Symptoms

An Order has been submitted in Fusion Order Management, the order is shipped using WMS. The user is unable to progress the order to invoice this. Errors are reported on the fulfillment line:

01.01:An error occurred in the target application WMS for action RELEASELOCK because APIInvocationError:ICS runtime execution error: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1Bad Request400<![CDATA[POST https://a33.wms.ocs.oraclecloud.com/fellowes/wms/lgfapi/v10/entity/order_hdr/bulk_unlock returned a response status of 400 Bad Request]]><![CDATA[{"reference":"03638f51-b7be-4a99-89ae-15ae8b14baee","code":"VALIDATION_ERROR","message":"Invalid lock code for order","details":null}.A 400 Bad Request Error indicates that the target service is unable (or refuses) to process the request sent by the client (Oracle Integration Cloud), due to an issue that is perceived by the server to be a client problem. You can trace the cURL representation of the request sent to the target service from the Oracle Integration Cloud server logs. Try invoking the target service using cURL. It may also be that one of the intermediaries (proxy, LBR) could be returning this code. ]]>Fault Dez

 

01.02:tails : <ns2:APIInvocationError xmlns:ns2="http://xmlns.oracle.com/cloud/generic/rest/fault/REST/UnockAPICall"><ns2:type/><ns2:title/><ns2:detail/><ns2:errorCode/><ns2:errorDetails><ns2:type>http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.1</ns2:type><ns2:title>Bad Request</ns2:title><ns2:errorCode>400</ns2:errorCode><ns2:errorPath>&lt;![CDATA[POST https://a33.wms.ocs.oraclecloud.com/fellowes/wms/lgfapi/v10/entity/order_hdr/bulk_unlock returned a response status of 400 Bad Request]]&gt;</ns2:errorPath><ns2:instance>&lt;![CDATA[{"reference":"03638f51-b7be-4a99-89ae-15ae8b14baee","code":"VALIDATION_ERROR","message":"Invalid lock code for order","details":null}.A 400 Bad Request Error indicates that the target service is unable (or refuses) to process the request sent by the client (Oracle Integration Cloud), due to an issue that is perceived by the server to be a client problem. You can trace the cURL representation of the request sent to the target service from the

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.