Combined Totals Re-run After correction Transaction Totals Are Not Calculated Correctly And Cause Posting 0 Value For Earlier Revisions (Doc ID 1626905.1)

Last updated on AUGUST 17, 2016

Applies to:

Oracle Retail Sales Audit - Version 13.2.5 and later
Information in this document applies to any platform.

Symptoms

The issue described in this document is known to Oracle, and a fix already scheduled for future release.
This article will be updated as official patch information becomes available.


Combined totals that are re-run after correcting transaction error (ex: tran_out_bal) cause posting 0 value for earlier revisions in sa_sys_value table causing loading necessary data to GL

Steps to reproduce:

1- Prepare a combined total and approve it.
2- Load sale through RESA including transaction that will cause tran_out_bal error.
3- Run satotals and check first revision SYS_VALUE created in sa_sys_value table.
4- Fix tran_out_bal error for transaction in step 2.
5- Rerun the totals , check revisions of SYS_VALUE created in sa_sys_value table to find that second revision for totals is posted to be 0.

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