My Oracle Support Banner

Item Integration With Secondary Barcode is Failing in USM (Doc ID 2912520.1)

Last updated on NOVEMBER 30, 2022

Applies to:

Oracle Retail Integration Cloud Service - Version 19.1 and later
Information in this document applies to any platform.

Symptoms

Item integration is getting failed in Universal Service Mapper (USM) layer when a secondary barcode is associated to a transaction level item.

Steps to Reproduce:

  1. Create 3 level of items in MFCS as below:
    Grand Parent with item_level 1 / Tran_level 2
    Parent item with item_level 2 / Tran_level 2
    Barcodes with item_level 3 / Tran_level 2
  2. For this, style item is created at first to which few items are linked with variants of size and color (differentiators). For one of the variant/sku item, a primary barcode is then linked and it was sent correctly to OWMS.
  3. A secondary barcode is then added to the same variant/sku item from before and when sending it to OWMS it returns an error because it cannot find the reference in OWMS.
  4. This occurs when the message carries a secondary barcode and gets the response as "Processing failed for entity item_barcode and file group XYZ".

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!

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