Personnel Actions (Transaction Data) 
Personnel Actions (Transaction Data)
Technical name: 0HR_PA_1
Technical Data
|
Type of DataSource |
Transaction Data |
|
Application Component |
Personnel Administration (PA-PA) |
|
Available from OLTP Release |
3.1H |
|
Available from Plug-In Release |
1999 |
|
RemoteCube Compatibility |
No |
Use
This DataSource contains information on personnel actions.
Delta Update
Delta update is not supported.
Fields of Origin in the Extract Structure
|
Field in Extraction Structure |
Description of Field in the Extract Structure |
Table of Origin |
Field in Table of Origin |
|
CALDAY |
Calendar day |
PA0000, PA0302 |
BEGDA |
|
PERNR |
Personnel number |
PA0000, PA0302 |
PERNR |
|
MASSN |
Action type |
PA0000, PA0302 |
MASSN |
|
MASSG |
Reason for action |
PA0000, PA0302 |
MASSG |
|
STAT2 |
Employment status |
PA0000 |
STAT2 |
Features of Extractor
Depending on your Customizing settings, personnel actions are read from infotype 0000 Actions or 0302 Additional Actions.
A special date calculation takes place for leaving actions. Actions are only identified as leaving actions if the employment status of the action is changed to the value withdrawn (STAT2 = o). For these actions, one day is subtracted from the start date of the action.
The date from which the employee left the company is used as the start date (BEGDA) of the leaving action in the Actions infotype (0000). If, for example, December 31, 2000 is the last working day of the employee, the start date of the leaving action is January 1, 2001.
From a reporting viewpoint, the employee left the company on December 31, 2000, which means that the fluctuation is to be paid up to December 31, 2000. R/3 reports on entries and leavings, such as RPLEAT00, work correspondingly.