E-CI: CI Save Method Returned True Even when Error Giving on Child Rows

(Doc ID 1368998.1)

Last updated on JANUARY 19, 2018

Applies to:

PeopleSoft Enterprise PT PeopleTools - Version 8.4 and later
Information in this document applies to any platform.
*** Checked for relevance on 12-Jun-2014 ***


On PeopleTools 8.51.12 with HCM 9.1 MP4, in a customized AE program, using a custom CI JOB_DATA to update data, it saved even when given incorrect values to a field in Job collection, e.g. ACTION

Error seen on customized AE log:

Invalid value -- press the prompt button or hyperlink for a list of valid values (15,11)
Error changing value. {FIU_CI_JOB_DATA2.JOB(1).ACTION_0} (91,34)

Actual vs Expected Behavior
CI.save run to success, it should have failed with error

Steps to Replicate:
1 ) Put an invalid Action value into the staging table that the CI is going to read from, for example: EJR.
2) When the Process ran, it succesfully saved CI even though it had an invalid value for the Action.
3) When check the row that was added for the employee, the Action that was there was Transfer.
     Which is the same value as the Max effective Dated row where used in the InsertItem Code. as follows:

    &oJob = &oJobCollection.InsertItem(&oMaxActEffdtRow.ItemNum);

    The ItemNum Property is 1, this is checked through a messagebox. It's the MaxEffective Dated row.
4) put messagboxes around it to show that the error is happening right at the time . It showed even there were Warnings/Errors Pending, the program still saves. The errors are being caught correctly, but the CI seems to be switching the invalid Action Immediately back to a valid value thus allowing program to save.
5) If use this code to insert into Job instead


    it behaves exactly as expected.


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