	AllExperts > Peoplesoft
	Search

About Matthew Bowden
Expertise
I am willing to share my know how gained from 15 years of supporting PeopleSoft payroll and related modules. I do not have access to an installed system at this time, so my knowledge will be from memory and analysis of provided facts

Experience
PeopleSoft Payroll -- development and support PeopleSoft Payroll Interface -- development and support PeopleSoft Benefits Administration -- support PeopleSoft COBOL -- Functional expert/programmer

Education/Credentials
BA Mathematics, PeopleSoft employee 1993 to 2004

You are here: Experts > Industry > IT Consulting > Peoplesoft > PeopleSoft Person Data / JOB Data

Peoplesoft - PeopleSoft Person Data / JOB Data

Expert: Matthew Bowden - 11/3/2009

Question
Hi Mathew,

We have recently upgraded to People Soft HR 9.0 and have identified a customization to be handled. Can you please share your suggestion on this
description/background of the issue:
After adding a Person Info on the Person Data component , when we hit the Add Relationship Button on Organization Relationships Page in the Person Data Component,People Soft Saves the person data and transfers control to to JOB_DATA .

Things would be good if a user adds the JOB DATA and save.

If the user doesn't enter and save ( or cancel) the corresponding JOB DATA for the position id just created on the PERSON_DATA,we end up with a POSITION ID whose person data exists but no JOB DATA.

we would want to come with a customisation that would not save the person data unless the job data has been created and saved ,so as to keep the Person Data and JOB data tables in sync.

Can you please suggest a work around or throw some ideas as to how to handle this in a better 7 easiest way .

thanks in advance

look forward for your reply .

Vishal

Answer
Vishal

Not my area of expertise, but I offer a line of thought. The creation of PERSON_DATA is valid for more that just employees, so it should not require creation of a position. If that is happening, you should treat it as a product defect. Conversely, requiring Job Data for every Person Data record would be contrary to this principle and thus would be a risky customization.

If the issue is that the automatic launch of Job Data creates the position, the same product defect issue should apply. If the Job Data process is cancelled that POSITION_ID created should be deleted. I would suggest you pin down the point in the process when the POSITION_ID is created. This would be needed for further analysis both by Oracle Support and for any customization you undertake.

Matthew Bowden

Add to this Answer Ask a Question