My Oracle Support Banner

Automatic Receipts: IBY Puts Receipt From Remitted To Confirmed With A Date From Next Period For Failures When Attempting to Reverse Receipt (Doc ID 1559458.1)

Last updated on FEBRUARY 20, 2019

Applies to:

Oracle Receivables - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

Cannot reverse a Receipt with an old date (i.e. the original settlement date as the GL_DATE of the confirmed row goes to next period).

You want to find out how the GL_DATE of the confirmed row in AR_CASH_RECEIPT_HISTORY_ALL is derived.

Example:
CONFIRMED
REMITTED
CONFIRMED -- This is done by the fetch program in IBY when the Bank rejects a Transaction and where the Customer has the problem with the GL_DATE.

The GL_DATE of this row is being derived as sysdate + 3 or 4 days.

If the fetch program in IBY is run today, it is putting the GL_DATE in AR_CASH_RECEIPT_HISTORY_ALLl as today + 3 days.
The GL_DATE is not passed while running the fetch program.

This is a problem because if this is done on the last day of the period, the GL_DATE is going to the next period.

Changes

 

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!


In this Document
Symptoms
Changes
Cause
Solution
 1. Bug Summary
 2. Fixed Files
 3. Recommended Patches
 4. Solution Steps
 Still Have Questions?
References


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