My Oracle Support Banner

XItem Processing in RMS 14.1 Changed to Synchronous Mode (Doc ID 2049192.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Retail Merchandising System - Version 14.1 and later
Information in this document applies to any platform.

Details

Issue Description

As part of the Retail Merchandising System (RMS) 14.1.x Item Induction feature, two modifications were made:

  1. Core processing of the external item (XITEM) interface and Item Induction were combined into a single package called CORESVC_ITEM.
  2. XITEM was made an ASYNCHRONOUS process, just like Item Induction is, through the Retail Merchandising System (RMS) User Interface (UI) when using spreadsheet upload/download.


These modifications caused several issues:

  1. XITEM Notifications:  Notifications remain pending in the RMS UI layer, as User could be different on Retail Integration Bus (RIB).
  2. Sequencing: ASYNC (asynchronous) queue processing does not guarantee the correct sequence of XITEM message processing (i.e., a CHILD item may consume before its PARENT item).

 

These issues have been resolved by changing to SYNCHRONOUS processing instead of submitting an ASYNCHRONOUS job.  Message handling is now being handled in the RIB layer.

Error Handling, Retry, and Reprocessing

NOTE:  The Item Induction process (upload from spreadsheet) remains an ASYNCHRONOUS operation.

 

Actions

To resolve this issue, please apply the following mandatory patches AFTER applying the below dependencies on top of RMS 14.1.1.  Apply these patches in the given sequence:

<Patch 21452184> - ITEM INDUCTION ASYNCHRONOUS PROCESS PROHIBITING ITEMS COMING IN TO RMS
<Patch 21644360> - CHILD ITEM NOT GETTING CREATED WHEN SEASON OF PARENT IS PROVIDED IN XML
<Patch 21638115> - SYSTEM IS ALLOWING TO HAVE MORE THAN PRIMARY COUNTRY FOR AN ITEM SUPPLIER THROUG

 

Dependency List for Mandatory Patches (apply in the sequence given):            

   -- If your environment is on “RMS 14.1.1 + Hot fixes”, you should apply only the missing fixes based on the dependency list below.
   -- If your environment is on 14.1, you must upgrade to RMS 14.1.1, then apply the dependency patches as given below.
   -- If you have any questions on applying these dependencies, please log a Service Request (SR).

<Patch 20802204>
<Patch 20817575>
<Patch 20813813>
<Patch 20901415>
<Patch 20891819>
<Patch 21096942>
<Patch 21216321>
<Patch 20796842>
<Patch 20844625>
<Patch 20781907>
<Patch 20915800>
<Patch 21076432>
<Patch 20968808>
<Patch 21164555>
<Patch 21175097>
<Patch 21212669>
<Patch 21202220>
<Patch 21226805>
<Patch 20930929>
<Patch 21178901>
<Patch 21321457>
<Patch 21438823>
Patch 21435675 
<Patch 21462418>

 

NOTE: In order to avoid the repetitive work of applying 27 individual hot fix patches one by one, you may refer to details on the Oracle Retail Merge Patch (ORMerge) utility in the RMS 14.1.X Installation Guide, available in the Oracle Retail Merchandising System Documentation Library.  This utility will allow you to create a merged "super patch" out of all 27 patches (24 dependencies plus the 3 mandatory patches) and apply it in one shot using the ORPatch utility.

 

Contacts

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
Details
Actions
Contacts
References

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