My Oracle Support Banner

Late Transactions Are Not Rolled-up Correctly By Fifgldn2 Batch Program (Doc ID 2423779.1)

Last updated on JULY 23, 2018

Applies to:

Oracle Retail Merchandising System - Version 16.0.1 and later
Information in this document applies to any platform.

Symptoms

Late transactions are not rolled-up correctly by fifgldn2 batch program

fifgldn2 - Processing of multiple late post transactions are not rolled up together in the STG_FIF_GL_DATA table when IF_TRAN_DATA table contains multiple late post transactions that have different TRAN_DATE but belongs to the same dept and location.

Example of IF_TRAN_DATA table details.
Record A
ITEM - 12345
DEPT - 101
LOCATION - 45056
TRAN_DATE - 23-May-2018

Record B
ITEM - 12345
DEPT - 101
LOCATION - 45056
TRAN_DATE - 22-May-2018

Record C
ITEM - 67890
DEPT - 101
LOCATION - 45056
TRAN_DATE - 20-May-2018

The batch program did not combine the late posted transactions in a single entry. Instead, it created an entry for each record base from its TRAN_DATA value. (They are rolled-up separately).


Steps to recreate:
The issue can be reproduced at will with the following steps:

1. Create a PO
2. Ship the created PO
3. Receive the PO (Note that the PO should be received for next month period)
4. Execute the SALSTAGE batch (this will create records in the IF_TRAN_TABLE for the late transactions)
5. Execute the fifgldn2 batch program (This will create records in the STG_FIF_GL_DATA table

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!


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