HR ABAP Query

[Former Member]

Hi,

Can anyone tell me why there exists multiple records in PAnnnn table for a pernr having different BEGDA n ENDDA's.

There are multiple records because for a single pernr there are many records BEGDA n ENDDA.

Why is it so??

Answers will be rewarded,

Regards,

Rohan

[Former Member]

Hi,

Can anyone tell me why there exists multiple records in PAnnnn table for a pernr having different BEGDA n ENDDA's.

There are multiple records because for a single pernr there are many records BEGDA n ENDDA.

Why is it so??

Answers will be rewarded,

Regards,

Rohan

[Former Member]

Hi Rohan

This is beacuse of the property of Time Constraint in infotypes.Whenever a new type of data for an employee is entered a validity time period for this is created.This time-based reaction is determined by the Time-Constraint.

Eg. Suppose if pernr 1000 has some data in PA0001(Org.Assignment) for the time period of 01.01.1995 upto 30.06.1995 and then it has another entry of data which starts from 01.07.1995 upto 31.12.9999.This may be due to the fact that previously the employee may be working in <b>finance deptt</b> and from 01.07.1995 he was shifted to <b>HR deptt</b>,then the record of employee exists but in diff org units and for different time periods.

For more information on time constraints,chk this

http://help.sap.com/saphelp_47x200/helpdata/en/48/35c9f24abf11d18a0f0000e816ae6e/frameset.htm

Hope this helps.

Neerja

[Former Member]

When you update an infotype, old data is not lost but archived for historical evaluation. The system records a specific period of validity for each infotype, This enables the system to store more than one infotype record at the same time, even if their validity periods overlap. This means that the time relationships between infotype records must be defined. The concept of time constraints enables you to do this.

"The system also contains the following time constraint indicators:

<b>Time Constraint A</b>

Infotypes with time constraint A must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.

Infotype records with time constraint A cannot be deleted.

<b>Time Constraint B</b>

Infotypes with time constraint B must have no more than one record. The system automatically assigns the record a validity period from January 01, 1800 through December 31, 9999. This validity period cannot be subdivided.

Infotype records with time constraint B can be deleted.

<b>Time Constraint T</b>

Infotype records with time constraint T depend on the subtype.

The principles of data entry and time constraints that apply to infotypes ensure that data is consistent and accurate. They also constitute the basis of time recording, payroll accounting, and reporting.

reward points if it is usefull ...

Girish