RAXTRX - The Same Payment Term Is Generating Different Due Date In Two Operating Unit

(Doc ID 1299130.1)

Last updated on AUGUST 25, 2017

Applies to:

Oracle Receivables - Version: 11.5.10.2 and later   [Release: 11.5.10 and later ]
Information in this document applies to any platform.
RAXTRX

Symptoms

On : 11.5.10.2 version, Transactions Related

One payment term setup with cutoff day 31, due day 25 and months ahead 0 .
Running the Autoinvoice Master Program in one org_id 2141, before day 31 and
the due date calculated is 25 of next month.
In another org id 708, the due date calculated is 25 of the same month
(before the invoice date).
Example:
Invoice date January 26
Due date calculated by Autoinvoice - February  25 for org_id 2141
Due date calculated by Autoinvoice -  January 25 for  org_id 708



EXPECTED BEHAVIOR
-----------------------
Expect to see due date February 25 in both cases

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Enter a Sales Orders in  OM with the same payment term
and run Autoinvoice

BUSINESS IMPACT
-----------------------
Due to this issue, invoice due date is wrong

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