SAIMPTLOGFIN Batch Has Different Behavior in Case of PVOID (Doc ID 1153814.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Sales Audit - Version 12.0.8 to 12.0.11.1 [Release 12.0]
Information in this document applies to any platform.
Checked for relevance on 12 Jan 2012
Checked for relevance July 2013


Symptoms

'Saimptlogfin' batch perform differing behaviors in PVOID activity in the following cases:


Case 1:


1. Create a store/day.
2. Upload a RTLOG (Retail Transaction Log) file two times for a particular store day and run all ReSA (Retail Sales Audit) batches with 'Posupld' batch.
    For example, if the TRAN_SEQ_NO for the first transaction is 27369001, and for the duplicate transaction is 27370001. SA_EXPORTED also have export record for both TRAN_SEQ_NO.
3. Post void the duplicate transaction (27370001).  New TRAN_SEQ_NO 27371001 is generated for the PVOID transaction.
4. Run 'Saimptlogfin' batch.  All transactions get status 'V', instead of the voided transaction only.
    Also, the original transaction 27369001 gets deleted from SA_EXPORTED table.  Only duplicate transaction 27370001 exists there with status 'P' instead of status 'V'.


Case 2 :

1. Create a store/day.
2. Upload a RTLOG file two times for a particular store/day and run all RESA batches with 'Posupld' batch.
    For example, if the TRAN_SEQ_NO for the first transaction is 27372001, and for the duplicate transaction is 27373001. SA_EXPORTED also have export record for both TRAN_SEQ_NO.
3. Post void the duplicate transaction (27373001).   New TRAN_SEQ_NO 27374001 is generated for the PVOID transaction.
4. Make store/day as fully loaded, then run "Saimptlogfin" batch.  It works fine except that the duplicate transaction 27373001 has its entry to SA_TRAN_HEAD_REV table, but SA_TRAN_HEAD shows REV_NO equal to 1 instead of 2.
5. SA_TRAN_HEAD has following entry:

   TRAN_SEQ_NO     REV_NO
   27372001             1
   27373001             1
   27374001             1


And SA_TRAN_HEAD_REV has following entry:

   TRAN_SEQ_NO     REV_NO
   27373001             1


Due to this, data shows discrepancies between ReSA-RDW and ReSA-RMS.

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