At the moment I am trying to do a simple test of doing a Date tracked Update change on an Assignment Record where I change the Payroll and one Segment of the People Group.

I am using the API Hr_Assignment_Api.Update_Emp_Asg_Criteria. It is one I have used historically but it is giving me a problem. If I just change the Payroll it works fine, but when I add the People Group details it falls over with

ORA-2001 Flex_ID does not exist

Ideas ??

Wotcher, young Gus!

My take on this is, it's a value that is invalid for one of the valuesets on one of the people group segments. It could be the segment you're trying to change, OR it could be another segment that you're not interested in at all, but nevertheless contains a value that is no longer valid (because someone has disabled one or more hitherto-valid values). Recall that the API will always attempt to validate the current record prior to validating what you are trying to change. The rest of the message (which you have neglected to share with us, you little tease!) should tell you which segment it's complaining about, and possibly the value it doesn't like as well.

CT,

'young Gus'....wot a nice man !!

Actually that is all the message I get...that is why I am confused.

I am looking into something I found on metalink at the moment, there would seem to be some bug in the API regarding not auto inserting the People Group details and therfore getting this problem

Will let you know

Gus

Tried creatring the desired row in the pay_people_Groups table before I called the API...didn't work

Clive do you have an example script with a call to the update_emp_asg_criteria API

Cheers

Gus

I assume the 'allow dynamic inserts' check box is checked on the people group flex definition within the application?

Have you tried supplying all of the PPG segment values into the API call, not just the segment you are updating?

Yes the Checkbox is checked (do you remember the phrase 'Just check the Checkbox' when we where at Oracle ?? LOL)

I have just got it working......by

1) creating the People Group First in pay_people_Groups.
2) not setting any of the individual segments.
3) setting the parameter p_concat_segments. (ie the whole string)
4) setting the paramter p_people_group_id

Now need to find out if I need to do all of these as number 1 could be a pain for 12k emps

Hmmm, OK so that works... but, it's not exactly practical is it?

The thing to check with this API is, that the variables that reference those in/out parameters are explicitly set to NULL prior to each call, e.g. p_concat_segments, p_people_group_id - and whatever others are there. Theoretically the first successful call will set those to some non-null value, which unless they are reset to null will be taken as inputs on the next call.