My Oracle Support Banner

Data Import (DIMP) Takes Excessive Time to Complete Processing in Back Office (BO) (Doc ID 2035450.1)

Last updated on JUNE 07, 2021

Applies to:

Oracle Retail Back Office - Version 14.0.1 and later
Information in this document applies to any platform.


While processing a MOM jar, all the xml files are getting processed immediately.  However, ItemClassificationMod.xml alone takes a very long time to process in Back Office and fails with the below error:

"[error creating oracle.retail.stores.commerceservices.item.item.importdata.dto.RetailStoreItemDTO@69f2b7[changeTypeAttribute=UPS,retailStoreID=<STORE>, iDAttribute=100656015,taxGroupAttribute=0, vatCodeAttribute=<null>,regularPrice=13.99,compareAtPri...]

[Insert: oracle.retail.stores.commerceservices.item.pricing.importdata.dto.EventDTO@158d836[eventID=3012,retailStoreID=<STORE>,planEndDate=<null>,scheduledEnd=<null>, ownerName=<null>,planStartDate=Wed Jan 01 00:00:00 IST 1969,typeCode=PPC,statusCod...][ORA-00001: unique constraint (<USERID>.CO_EV_PK) violated...]"

Steps to Reproduce:

  1. Start the BO instance.
  2. Place the MOM jar created from Retail Merchandising System (RMS) in the <DIMP>\incoming folder.
  3. In the table MA_STS_FL_IMP, observe StoreOrgHier.xml and MerchandiseHier.xml process immediately.
  4. Observe that ItemClassificationMod.xml takes more than 40 minutes to process.
  5. After that, ItemExport.xml alone takes more than 20 minutes to process.
  6. In the MA_STS_BNDL_IMP table, there is more than an hour difference from record created and last modified. 
  7. Also observe the above mentioned exception calling multiple times in column DE_IMP_EXCP for ItemExport.xml in table MA_FL_IMP_FLRS.




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.