My Oracle Support Banner

Automatic Receipts Maturity Date Is Not Getting Derived As Expected Using Earliest Rule (Doc ID 2724871.1)

Last updated on JANUARY 14, 2021

Applies to:

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

Symptoms

On : 12.1.3 version, Receipts Related

ACTUAL BEHAVIOR
---------------
Automatic receipts is not selecting the maturity date as expected.

EXPECTED BEHAVIOR
-----------------------
Expect that if the maturity date rule is set to earliest, and the batch date and earliest due date is (as an example) Jan 01, that this would be the maturity date.
Yet, the maturity date is being picked up as Jan 20th.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Run the Automatic receipts and remittance program.
2. Enter a batch date of Jan 01.
3. Select the transactions and check the earliest due date which seems to be Jan 01.
4. See that the maturity date of the batch gets stamped with Jan 20th.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, The system appears to be calculating the incorrect maturity date of the receipt batch.

 

 

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
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.