E1: FIN: Advanced Payment Term With Date Range And Workday Calendar Seems To Calculate (Discount) Due Date Incorrectly For Some Dates (P00071, P00145, P00146, P03B11, P0411, B0000163)
(Doc ID 2325454.1)
Last updated on MARCH 15, 2018
Applies to:JD Edwards EnterpriseOne Accounts Payable - Version 9.0 and later
JD Edwards EnterpriseOne Accounts Receivable - Version 9.0 and later
JD Edwards EnterpriseOne Sales Order Entry - Version 9.0 and later
JD Edwards EnterpriseOne Procurement and Subcontract Management - Version 9.0 and later
Information in this document applies to any platform.
Why does it appear that, when using an advanced payment term that has due date rules that use a date range, the Discount Due Date (F0411.DDJ) is calculated incorrectly for some dates?
For example, consider the following set up for a due date rule in Due Date Rule Revisions (P00146):
- Due date rule 2-10N:
- Based on date: 1 = Invoice Date
- Days to Add: 0
- Fixed Days: 0
- Months to Add: 0
- Calendar: M30
- Work day rule: 3 = Actual Days, Previous Work Day
- Range attached:
|From Day||To Day||Days To Add||Fixed Days||Months to Add|
When creating a voucher via Standard Voucher Entry with an Invoice Date (DIVJ) of 1-Sep-2017, the Discount Due Date (DDJ) is calculated as 20-Sep-2017. This seems incorrect as 1-Sep-2017 (which is a Friday) falls in the first range, day 1 - day 10, so only 10 days should have been added to the invoice date:
1-Sep-2017 + 10 = 11-Sep-2017
This is regardless of the use of a Workday Rule or not.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!