Mismatch Between WMS 23A Parcel Manifest XML And XSD Elements Passed During Integrations Which Cause Integration To Fail (Doc ID 2931618.1)

Last updated on MARCH 01, 2023

Applies to:

Symptoms

Mismatch between WMS 23A parcel manifest XML and XSD elements.

After 23A upgrade in WMS(Warehouse Management Services), once the outbound manifest file is generated after closing the manifest in WMS, those files failed in the integration table due to mismatch between the WMS 23A upgrade generated XML elements and 23A XSD elements.
We found below additional elements were added in the outbound manifest XML, but same elements are not available in the XSD files which provided by oracle in xsd "lgf_parcel_manifest-23A.xsd" (Doc ID 2919682.1), due to this, the integration was not able to read the WMS XML records and it failed in integration table with below error.


"{status=CHANGED, instanceid=10.31.1.7:-6e221d78:1862408272f:36f1, eventtime=Thu Feb 09 11:48:02 GMT 2023, varid=null, varvalue={http://docs.oasis-open.org/wsbpel/2.0/process/executable}invalidVariables Details: BPCOR-6175: Invalid document"
 
below are the additional elements added in 23A outbound manifest XML.
<pallet_length>0</pallet_length>
<pallet_width>0</pallet_width>
<pallet_height>0</pallet_height>
<total_pallet_weight>0</total_pallet_weight>
<total_pallet_volume>0</total_pallet_volume>
<total_nbr_of_pallets>0</total_nbr_of_pallets>
<externally_planned_load_nbr>

Steps To Reproduce

==============

1. Go to Manifest UI screen.
2. Select any existing closed manifest and click on "Generate Manifest File".
3. The system will create new version (23A) outbound manifest XML file with records, and able to see above elements in XML file.

Changes

Cause

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