My Oracle Support Banner

ASNIn To SIOCS Must Not Fail If It Has A Container That Was Already Used On Another Existing ASN (Doc ID 2964352.1)

Last updated on JULY 31, 2023

Applies to:

Oracle Retail Enterprise Inventory Cloud Service - Version 23.1 and later
Information in this document applies to any platform.


Describe how the current product functionality is insufficient.
As per current SIOCS design, as documented in below article, ASN In message into SIOCS fails if it has a container that was already used on another existing ASN
Doc ID 2945299.1 - Why ASNIn Message Failing With Error "Delivery not processed. Container ID: XXXX already exist for ASN: YYYYY"

Business Impact: Whenever an ASN comes into SIOCS which has a container that conflicts with a container on older existing ASN, it fails to inject into SIOCS and then support team have to manipulate the ASN message to allow SIOCS to process it.


Provide a detailed description of the Enhancement Request.
Requirement: ASNIn to SIOCS must not fail if it has a container that was already used on another existing ASN

Business justification:
A store may receive ASNs from multiple sources, e.g. warehouses , vendors, etc. Retailer is unable to control what Container id will be used by each vendor when shipping deliveries to a store. Hence there are high chances that these container ids either conflict with a container id from another vendor or sometimes even with container id from the same vendor from an older ASN that is already existing in SIOCS.

Incidentally, In RMS, there is a system option - "Allow Duplicate Receiving", but this only checks the ASNin that gets integrated into RMS.

There must be a similar parameter in SIOCS, where Duplicate Container id check may be bypassed.
SIOCS must not reject an ASN if container id used on it is conflicting with a container id from another existing ASN.


Describe how this Enhancement will benefit your business.
It will process the ASNs from suppliers to stores automatically and successfully, without the need of manual intervention from support team, where they need to currently manipulate the container id in ASN message stuck in MPS staged table and then reprocess them individually.


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

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