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

Last updated on FEBRUARY 01, 2016

Applies to:

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

Symptoms

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.

Cause

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