My Oracle Support Banner

E1: 17: Contract Revisions - P1721 Does Not Allow Changing / Overwriting the Billable Duration (Alias: BDUR) Field in the Contract Detail Line (Doc ID 3050886.1)

Last updated on OCTOBER 01, 2024

Applies to:

JD Edwards EnterpriseOne Service Management - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

In P1721 - Contract Revisions if the users attempt to change the Billable Duration (Alias: BDUR) field, the new value is not saved, even if the line type setup in S/WM Attributes - P1793 allows them to modify the Billable Duration.

The issue can be reproduced at will with the following steps:

  1. In P40205 - Work With Line Types find the "EW" line type and take the row exit to S/WM Attributes - P1793. Make sure that the option "Allow User To Modify Duration" is checked (allowed).
  2. In P1720 and P1721 open an existing contract detail line and try to edit it or add a new contract with one line on the details. Use Start and End Dates like 01-Jan-2024 and 31-Dec-2024.
  3. In P1721 choose EW line and Elite package. Notice the Billable Duration (BDUR) is calculated based on the Contract Start and End Dates on the line details (not bill from and through dates).
  4. In P1721 try to change the value for Billable Duration (BDUR) and notice the new value is not preserved in grid when tab out. Also save and open the same contract details and notice the new value is not saved.

Note: This works fine for non-Billable Duration (Alias: CDUR) field. Also this used to work correctly in JDE 9.0 for both F1721.BDUR and F1721.CDUR fields.

Cause

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
Symptoms
Cause
Solution
References


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