I have 4 employees at this point that have PA13 records where the position information does not match what is on HR11. the position number is correct but all of the defaulted fields are showing from her previous position. I tried to do a pa52.5 to correct it but it doesn't do anything. I have tried turing off the data item atributes to update manually but it keeps telling me I must use action to change that field. I tried adding a new position and it tells me pos level does not exist for that effective date. GSC is looking at it but I was hoping someone may have run into this before. we are using version 8.1 talk about frustrating.

Was the problem caused by a position update, personnel action, or PA54? We had a similar problem in the past that was caused by using the PA54 to change the effective date for the action that created the new PAEMPPOS (PA13) record.

Basically you have two problems. One is to prevent it from recurring and the other is to clean up the bad data that has already been generated. GSC will probably ask you to load patches to fix the cause, assuming they figure out what caused the problem. Eventually.

Cleaning up the bad data is more problematic. GSC recommended we paint a screen of the PA13.2 that bypasses the rules and use it to load the correct values. We did this and it worked well. Unfortunately we still have to use it occasionally to clean up data.

I assume you have already run the PA113 just in case. There are other things you can try such as a combination of new actions, combine with history or reverse actions, and changing the previous PA13.2 record to match the current record and then deleting the current record. All of this is tricky and requires you to kind of feel you way through the solution and it may not work. Always try it in test first.

You might check HR10.1 with PO (which is position). This is the form that controls what must be updated with an action and has the rules for position defaulting for employee information. *Do it in TEST first*