Running 2 Personnel Actions on the same date..

[seema]

have one query. My client would want to run more than one personnel action on the same day. I know this can be done through activating Additional Actions IT302.

If I run first action on 01.01.09 for Change in Pay, it gets saved in IT0000 Actions and when I run 2nd action on the same day for Correction for Change in Pay, system displays that this action will only be saved in IT0302 Additional Actions.

It displays the start date and the end date of the later action as 01.01.09. The end date for 1st action is 12.31.9999. But client want to see it reverse.

They want the end date for 1st action change in pay as 01.01.09 and end date for 2nd action Corrections should be 12.31.9999 as this action is carried out later,
so this is the most recent record for the employee.

Is there any way to do it???

Similar Threads:

• ABAP Program: Output of Date Format Suppose a date is given in the format 20050428 ho
• Calculation to determine the delivery date and release date
• Pricing date based on delivery date
• Set the baseline date=Invoice date
• How To Configure Personnel Actions

[seema]

The requirement would defeat the purpose of additional actions and it is not possible either.

Additional actions always have the same start date and end date but we can report off of AEDTM to get the chronology.

[seema]

Can you explain in detail what is AEDTM???

[seema]

AEDTM is a field on every infotype.

It is "Changed on" date field. It captures the date an infotype was created/changed/updated etc....

[seema]

Using AEDTM is one way of tracking record chronology but this is not necessary accurate. This is accurate if the action is done not on the same day.

However you cannot base on this if all actions are done on the same day. Using AEDTM will not be the solution.

Using view screen PA20/PA30, user just need to be trained that the first action will be shown on the infotype 0, and subsequent actions that are also effective from the same date will be shown under additional actions window chronologically from top (first) to bottom (last).

Internally, when many actions are performed effective from the same date SAP technically uses the IT Record No field to track the sequence of record creation.

THis is stored in Additional infotype, with the first record having IT Record No '000' and increment by 1 for subsequent actions.
For this reason, basing on AEDTM is not accurate as multiple actions can be performed on the same day.