Post-Voided Transactions are Not Being Written Correctly by SAEXPDW Batch: Revision Number Remains the Same in RDWT File
Last updated on AUGUST 17, 2016
Applies to:Oracle Retail Sales Audit - Version 14.0.1 and later
Information in this document applies to any platform.
The SAEXPDW batch job is not handling POST VOID transactions properly. The revision number remains the same after batch execution.
Steps to Reproduce:
- Create a sale transaction.
- Post void the same transaction.
- Ensure the RTLOG is consumed by Oracle Retail Sales Audit (ReSA).
- Run SAEXPDW.
- Review the RDWT file containing transaction and its associated post void transaction. Note that the revision numbers are the same.
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