E1: FIN: Advanced Payment Term With Date Range And Workday Calendar Calculates (Discount) Due Date Incorrectly For Some Dates (P00071, P00145, P00146, P03B11, P0411, B0000163)
Last updated on NOVEMBER 06, 2017
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.
When using an advanced payment term that has due date rules that use both a date range and a workday calendar, 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 incorrectly calculated as 20-Sep-2017.
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
11-Sep-2017 falls on a Monday, so the date is good to be used per the Work Day Rule.
If the based on date of a voucher (or A/R invoice etc) falls in the first range of an advanced payment term with ranges and a workday calendar, the values defined on that first range should always be used to calculate the correct (discount) due date.
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