Exporting Personnel Actions

 5 Replies
 0 Subscribed to this topic
 68 Subscribed to this forum
Sort:
Author
Messages
bkauffman
Basic Member Send Private Message
Posts: 11
Basic Member

I have an issue with testing in our organization. Sometimes it takes weeks for me to get our HR  department to enter personnel actions for testing purposes in a test product line after I apply a patch or MSP. Do you know of a way to use MS addins (or lawson program) to extract a range of personnel actions from our production product line and then use addins to import them into the test product line?  If I could achieve this, I could bypass the HR data entry and proceed with testing in a MUCH more timely basis.

Any suggestions that anyone might have would be GREATLY appreciated!

Deleted User
New Member Send Private Message
Posts: 0
New Member

That is a good idea if it is possible.  I just perform the actions myself if I need actions to test off of plus it gave me the knowledge of a daily user that I didnt have until I figured out how to use PA52.1

Deleted User
New Member Send Private Message
Posts: 0
New Member
I understand your frustration - we encounter the same problem here. I caution you, though, to continue make sure the owners of the data are involved in any testing that you do. We do as much testing as possible here, however, we don't know ALL of the various processings that the users go through on a daily basis, so they must be engaged when we test patches, ESPs or MSPs.
Jimmy Chiu
Veteran Member Send Private Message
Posts: 641
Veteran Member
Personnel Actions are in 2 tables. PADICT and PADICT2.

rngdbdump to a csv from the source productline. You can refine the rngdbdump to a range of data.

then

importdb -afu into the target productline
Jimmy Chiu
Veteran Member Send Private Message
Posts: 641
Veteran Member
Follow up, user defined action codes have "UF" as topic. Those are the one you want to dump to csv and load them to target productline.
Deleted User
New Member Send Private Message
Posts: 0
New Member
PA52.1 is kind of easy to use. The way I test it is to change something easy such address, or Job codes or Adjust Hire date. Once I have done this unit test, I pass the bucket to HR to do their things. They have a lot more stuff that I do not want to know.