Configure Additional Actions for Efficient Data Maintenance

  • by Vamsi Mohan, SAP HR Consultant, Accenture
  • January 14, 2010
Learn how to configure an additional action and see the advantages of adding one.
Key Concept
Personnel actions are activities that involve a change of employment status or of employee master data. These activities could be hiring, promotion, transfer, pay change, disciplinary action, change of contract, or separation. You can use personnel actions to capture and update employee data for various employee events, and also change the employment status of an employee.

In a typical business scenario, you perform various actions for an employee — there may also be instances when you need to perform more than one action on the same day. For example, suppose you have performed a transfer action for an employee. Later in the day you are asked to perform a promotion action for the same employee. Now what happens if you perform the promotion action? The system doesn’t stop you from running another action, even though one action has already been executed on the same day. So when you perform the promotion action after the transfer action, the system deletes or overwrites the previously performed transfer action and saves the new promotion action. In addition, when you perform the second action, if there is a change in the employment status, then the system gives you an error.

The system gives out an error message because you cannot perform two different actions with the same begin date and each with a different employment status, as an employee cannot exist, having two different employment statuses on a single day. On any given day, an employee can have only one employment status. How can you perform more than one action on the same day without any action being deleted? The answer is that you need to configure additional actions. An additional action is a second action performed that does not overwrite the first action. Instead, it is stored in infotype 0302. Infotype 0302 is a log that has the details of all the actions run for an employee. This is required for the purpose of history, for audit, and also for reporting purposes. I’ll explain all you need to know about additional actions and how to configure them.

Vamsi Mohan

Vamsi Mohan works as an SAP ERP HCM consultant. He has been working in SAP ERP HCM for the past seven years in various assignments. Vamsi has rich experience in time management, payroll, LSO, ESS, and has been part of many implementations. Prior to joining Accenture, he was associated with TCS, IBM, and Dell. Vamsi has a master’s degree in business administration.

See more by this author


Comments

1/22/2014 2:57:59 AM
Somdeb Banerjee

Hi Vamsi,

A great article indeed.

Thank you.

Regards,
Somdeb.

Please log in to post a comment.

To learn more about subscription access to premium content, click here.