ASNOutCre and ReceiptCre Messages Fail for Shipments Having Container Id Greater than 20 Characters (Doc ID 2302508.1)

Last updated on SEPTEMBER 06, 2017

Applies to:

Oracle Retail Store Inventory Management - Version 16.0 and later
Information in this document applies to any platform.

Symptoms

In Store Inventory Management (SIM) application, find that, the ASNOutCre and ReceiptCre messages published by SIM fail in SIM database table MPS_STAGED_MESSAGE, when the container id is longer than 20 characters in length.

Steps to Recreate :
 
1. Set Store admin parameter "SSCC Shipping Label ID Generation" value to "Manual"
2. Check and see that the EXTERNAL_ID column of SIM database table TSF_DELV_CONTAINER is defined as VARCHAR2(128)
3. Log into SIM and create a transfer shipment from Store 1 to Store 2
4. In container create screen, click on 'Info' and enter the container id that is more than 20 characters in length
5. Add an item and confirm
6. Find that SIM publishes a SOStatusCre message, which is processed successfully.
7. Dispatch the transfer and note that SIM publishes an ASNOutCre message
8. Find that the ASNOutCre message fails in SIM database table MPS_STAGED_MESSAGE with the following message:

oracle.retail.sim.common.core.SimServerException: Error processing message! [Inbound: false, MessageType: ASNOutCre, BusinessId: 230]
at oracle.retail.sim.service.mps.BaseSimMessageServiceHandler.buildException(Unknown Source)
...
...
...
Caused by: javax.validation.ConstraintViolationException
at org.eclipse.persistence.jaxb.JAXBBeanValidator.buildConstraintViolationException(JAXBBeanValidator.java:381)
... 70 more

 9. Log into Store 2 and receive the transfer
10. SIM publishes a ReceiptCre message, which also fails in SIM database table MPS_STAGED_MESSAGE with the following error message:

oracle.retail.sim.common.core.SimServerException: Error processing message! [Inbound: false, MessageType: ReceiptCre, BusinessId: SIM#8782]
at oracle.retail.sim.service.mps.BaseSimMessageServiceHandler.buildException(Unknown Source)
...
...
...
Caused by: javax.validation.ConstraintViolationException
at org.eclipse.persistence.jaxb.JAXBBeanValidator.buildConstraintViolationException(JAXBBeanValidator.java:381)
... 70 more

 

Changes

 

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms