cut over actions (PA40)

[Former Member]

Hi

for fresh implementation some cut over actions (PA40) i saw in previous projects

Any body kindly brief on this?

Rx

[Former Member · Accepted solution]

Hi Rex,

This is special action is normally used to assign employee to a position in organizational structure. As a rule during implementations no history for org. structure is created. So it is not possible to assign employee to a real position past in the histroy. Therefore following steps are done:

1. Hire employee as of real hiring date to 99999999 position,

2. Assign employee to a real position with cut over action.

Cheers!

[Former Member · Accepted solution]

Hi Semvladigo,

We have a fresh implementation and currently in the data upload phase. My client wants to upload all history data for all employees along with the history data for all the positions each employee held. So I have done the following -

1. Created all the positions needed and assigned it to the dummy org structure and then assigned it to employees with Hiring Action.

2. Run the Cut over Action to assign the positions currently held by employees to the current org structure.

Is this correct way?

Thanks.

[Former Member · Accepted solution]

Hi,

Yes, that's correct way in your case.

However normally clients do not require historical positions.

Cheers!

[Former Member · Accepted solution]

Thanks Semvladigo.

I believe we have to run the Cutover Action as of go-live date and the Org Structure will be active as of go-live date, is it correct?

[former_member51176]

Cutover actions are created and run to create the employee record in the production system and to make any required status changes.

A special info-group will have to be made with only creating an IT0000 record and actions created for each set of status change that is needed (to active, to retired, to inactive, to withdrawn).

One LSMW recording needs to be made in order to pull mass data into the production system.