Same Transaction from POS Is Processed Multiple Times in SIM by ReSA File Parser (Doc ID 2097812.1)

Last updated on JULY 28, 2016

Applies to:

Oracle Retail Store Inventory Management - Version 13.2.8 and later
Information in this document applies to any platform.

Symptoms

The Retail Sales Audit (ReSA) File Parser does not perform any validation to avoid transaction duplication.  As a result, the same Transaction from Point of Service (POS) is processed multiple times in Store Inventory Management (SIM).


Sample Steps to Reproduce:

1. Run /ResaFileParser.sh sale_1.pub for Item:100025061
     - Sale was integrated without any issue in POS_TRANSACTION_HISTORY
2. Run /ResaFileParser.sh sale_1.pub for Item:100025061 for same file and data as Test case 1.
     - Sale was well integrated in POS_TRANSACTION_HISTORY. Transactions are duplicated in database
3. Run /ResaFileParser.sh sale_2.pub for Item:100025061 with 2 identical lines in file store and timestamps identical as previous test cases.
     - Sale was well integrated in POS_TRANSACTION_HISTORY. Transactions are duplicated in database.
4. Run /ResaFileParser.sh sale_1.pub sale_2.pub for Item:100025061. Identical data in both files
     - Sale was well integrated in POS_TRANSACTION_HISTORY. Transactions are duplicated in database.
5. Run /ResaFileParser.sh sale_1.pub sale_1.pub for Item:100025061. Identical files sent as parameters.
    - Only one file integrated in POS_TRANSACTION_HISTORY. Batch throws an error for second file. Sale was well integrated in POS_TRANSACTION_HISTORY. Transactions are duplicated in database.

Conclusion:
There is no validation done for duplicate transactions in ResaFileParser batch.

Due to this issue, Sales Value and Stock on Hand have discrepant values in SIM.

Cause

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 hundreds of Community platforms