Error On Submitting Entry For Element Using Validation Formula (Doc ID 2455014.1)

Last updated on FEBRUARY 05, 2019

Applies to:

Symptoms

Global Payroll

ACTUAL BEHAVIOR
---------------
Customer uses has series of Elements that contain element entry validation formulas.
The validation formulas count the number of existing element entries and error the next entry if the count is going to be exceeded.

2. ICD entries for KIT(Keep In Touch) days made: 7 have been entered and processed, and a further 4 are now being entered in a batch. This totals 11 KIT days, which should cause an entry error:
3. Continue is then clicked and the Review page displays:
4. The request was then submitted and the expected validation error occurs. Note that it
generates the error for each record in the batch that causes the maximum limit breach:
5. Then click Back. The pending list is then re-displayed. There are 4 entries waiting to be
processed. The user decides to delete one of them as this was a duplicate and that would
leave a total of 10 to be recorded.
6. When one of the ‘New’ records is deleted the following message appears. Note the ‘null
pointer’ exception:
7. Select ‘Delete’ from presented options.
8. The selected record is now removed from the list and we are left with 10 records, 3 new
and 7 processed, as expected:
9. Then click Continue to complete the transaction. Another NullPointer exception is raised:
10. Click OK to return to the pending list. If we click Continue again the same NullPointer is
generated. We cannot continue without clicking Cancel.

EXPECTED BEHAVIOR
-----------------------
To be able to re-submit successfully after deleting the record that would trigger the validation formula.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1ICD entries for KIT days made: 7 have been entered and processed, and a further 4 are
now being entered in a batch. This totals 11 KIT days, which should cause an entry error:
3. Continue is then clicked and the Review page displays:
4. The request was then submitted and the expected validation error occurs. Note that it
generates the error for each record in the batch that causes the maximum limit breach:
5. Then click Back. The pending list is then re-displayed. There are 4 entries waiting to be
processed. The user decides to delete one of them as this was a duplicate and that would
leave a total of 10 to be recorded.
6. When one of the ‘New’ records is deleted the following message appears. Note the ‘null
pointer’ exception:
7. Select ‘Delete’ from presented options.
8. The selected record is now removed from the list and we are left with 10 records, 3 new
and 7 processed, as expected:
9. Then click Continue to complete the transaction. Another NullPointer exception is raised:
10. Click OK to return to the pending list. If we click Continue again the same NullPointer is
generated. We cannot continue without clicking Cancel.

Cause

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