My Oracle Support Banner

Salesprocess Batch Fails When POSU File Has Different Tax Amounts for Same Item (Doc ID 2880718.1)

Last updated on JULY 04, 2022

Applies to:

Oracle Retail Merchandising Foundation Cloud Service - Version 19.3 and later
Information in this document applies to any platform.

Symptoms

Salesprocess batch is failing with an error when POSU file has different tax amounts for different transactions having same consignment item.

ERROR
---------------
ORA-00001: unique constraint (RMS01.PK_INVC_DETAIL) violated@2CORESVC_SALES_UPLOAD_PRST_SQL.PERSIST_INVC_DETAIL
ORA-00001: unique constraint (RMS01.UK_INVC_DETAIL_VAT) violated returned by program unit CORESVC_SALES_UPLOAD_PRST_SQL.PERSIST_INVC_DETAIL_VAT.

Steps to Recreate:

  1. Create different sale transactions for same consignment item on same date but with different tax amount.
  2. Audit the storeday and run saexprms batch to generate POSU file.
  3. Run uploadsales batch using above POSU file.
  4. Run salesprocess and notice the error:
    ORA-00001: unique constraint (RMS01.PK_INVC_DETAIL) violated@2CORESVC_SALES_UPLOAD_PRST_SQL.PERSIST_INVC_DETAIL
    ORA-00001: unique constraint (RMS01.UK_INVC_DETAIL_VAT) violated returned by program unit CORESVC_SALES_UPLOAD_PRST_SQL.PERSIST_INVC_DETAIL_VAT.

Changes

 

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!

In this Document
Symptoms
Changes
Cause
Solution
References


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