My Oracle Support Banner

Transactions Workbench: Copied Transaction Has Wrong Due Date when Balance Forward Billing (BFB) is Not Enabled (Doc ID 1666594.1)

Last updated on DECEMBER 08, 2020

Applies to:

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


Attempting to copy a Transaction, with Proxima Payment Terms for Customers who have not enabled Balance Forward Billing (BFB), and find the Due Date is sometimes calculated incorrectly.

For Example:
Payment Term is set as follows:
  Billing Cycle = 20th of Month
  Day of Month = 25
  Months Ahead = 1

When creating a Transaction with Transaction Date = 27-NOV-2013, the Due Date is calculated as 25-DEC-2013 correctly.
However, when copying the Transaction for a customer not having BFB enabled, with the same Transaction Date, the Due Date is calculated as 25-NOV-2013, which is one month earlier than expected.


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
 1. Bug Summary
 2. Fixed Files
 3. Recommended Patches
 4. Solution Steps
 Still Have Questions?

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