When Deleting From Only Future Dated Rows in Job Data, Error "First Operand of . is NULL, so Cannot Access Member JOB (180,236) JOB.EMPLID.RowDelete" (Doc ID 1510178.1)

Last updated on OCTOBER 18, 2016

Applies to:

PeopleSoft Enterprise HRMS Human Resources - Version 9.1 to 9.1 [Release 9]
Information in this document applies to any platform.

Symptoms

When a Job record has only Future Dated rows, nothing current or past,  and you try to delete one of the future rows, you get the error: "First Operand of . is NULL, so Cannot Access Member JOB (180,236) JOB.EMPLID.RowDelete"

This could happen, for example, if you have a future-dated hire who calls to decline the job, so you enter a termination record, and then the person accepts the job.  When you delete the termination row you would get the error.

STEPS TO REPLICATE
------------------------
1. Create a new Employee ( Workforce Administration> Personal Administration> Add a person>
2. Select the Value of employee on the Organizational Tab
3. Save the Hire Row with a future date
4. Insert a new effective Sequence for the same Effective date as the Hire Row and use the Action of Termination – Save
5. Go back to the Termination Row and try to delete
6. System issues the following error: "First Operand of . is NULL, so  Cannot Access Member JOB (180,236) JOB.EMPLID.RowDelete"


ERROR MESSAGE
-----------------------
First Operand of . is NULL, so Cannot Access Member JOB (180,236) JOB.EMPLID.RowDelete"

Workaround

1.  Go into the Job Data Records in Correction Mode

2.  Go to the Hire Row and correct the Effective Date to Current System Date and save

3.  Go to the Termination row and select the "-" to delete that row - Save

4.  Go back to the Hire Row and restore the effective Date to the original value

Cause

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