SAP Time Constraint in HR Infotypes

Time Constraint Value

1 = Record must have no gaps, no overlappings
2 = Record may include gaps, no overlappings
3 = Record may include gaps, can exist more than once
A = Infotype exists just once from Jan.1 1800 to Dec.12 9999
B = IT exists for maximum of once from Jan.1 1800 to Dec.12 9999
T = Time constraint is based on subtype or subtype table
Z = Time constraint for time management infotypes -> T554Y

Looking for articles on time module? Click here

Looking for other details about infotypes? Click here

Want to know the basics of an infotype? Click here

Time Constraint Definition
A time constraint indicates whether more than one infotype record may be available at one time. The following time constraint indicators are permissible:

1 = An infotype record must be available at all times. This record may have notime gaps. You may not delete the record last stored on the database because all records of this infotype would otherwise be deleted.
2 = Only one record may be available at one time, but time gaps are permitted.
3 = Any number of records may be valid at one time, and time gaps are permitted.

Other possible time constraint indicators are as follows:

A = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
View V_T582B Infotypes Which are Created Automically controls whether the system automatically creates the infotype record for an employee hiring or an applicant data entry action.
Infotypes with time constraintA may not be deleted.

B = Only one record may ever exist for this infotype. It is valid from 01/01/1800 to 12/31/9999. Splitting is not permissible.
Infotypes with time constraint B may be deleted.

T = The time constraint varies depending on the subtype.
Z: Refers to time management infotypes. The time constraint for these infotypes depends on the time constraint class defined in view V_T554S_I Absence: General Control. Collision checks are defined in view V_T554Y TimeConstraint Reaction.

The Concept of Collision Checks

When you enter a new record, the system carries out a check to ensure that there are no contradictory records for that particular employee and time period.

It is not possible, for example, to enter an absence record if there is already an attendance record in the system for the same employee and time period.

When you customize the system, you can determine the system reaction if time data records collide. There are four possible reactions:

    1. An employee is on Leave from Monday to Friday, but is required to interrupt the vacation and return to work on Wednesday.

      2. System reaction:

      When you enter this data for the attendance type Attendance hours, the system draws your attention to the fact that a leave record already exists for the period. The leave record is automatically delimited if you proceed to save the attendance record.

    2. You try to enter a Substitution record for an employee who is on leave.

      3. System reaction:

      The system does not allow this particular constellation, as it is not logical to assign a substitution to an employee who is not at work. An error message is displayed and the system rejects the record.

    3. You try to enter substitution data for an employee who already has an overtime record for the same day.

      4. System reaction:

      This combination is in fact permitted. Overtime and substitution records are not mutually exclusive. The substitution may involve the employee working different hours from normal, however. If this is the case, it may be that the new working time coincides with the period in which the employee is authorized to work overtime.
      It is therefore preferable that the system draws your attention to the collision so that you can check your entries.

    4. An employee is assigned to work a substitution, which involves longer hours than usual. You try to record the absence quotaTime off for overtime.

System reaction:

This constellation is allowed, since substitutions and absence quotas are not mutually exclusive. There is no time correlation between these two subtypes. The system therefore accepts the absence quota without drawing your attention to the existing substitution record.

Want to enhance infotypes, Click here

Maintaining Long Text on PA Infotypes

Out of the box functionality, you can type in comments through PA30 on some of the infotypes. 


But how do you have this cool feature for other infotypes, such as custom infotypes or infotypes not automatically default out of the box?

You can! Very easy as the matter of fact. You can point your table to V_T582A or go to the IMG via SPRO -> Personnel Management -> Personnel Administration -> Customizing Procedures -> Infotypes -> Infotypes

Select the infotype you want to maintain and select “Text Allowed”. 

Infotype Enhancement

Looking for other details about infotypes? Click here

Want to know the basics of an infotype? Click here

Want to enhance infotypes, Click here || Excel of all infotypes


 We can enhance any standard infotype only if it contains Customer include i.e., CI_Pxxxx….

For ex: We can’t enhance 0000(actions) infotype as b’coz it doesn’t contain Customer Include…..

To enhance an Infotype… follow these steps….

Go to Trans. Code PM01.
Select 3rd tab (4th Tab for ECC 6 Version)
Enter ur infotype no. & click on edit..
The screen moves to structure where u can enter additional field in CI_Pxxxx
Save it and Activate.
Come back to initial screen PM01 and click on “ALL” button ( “Generate Objects” for ECC 6)

There u can find the additional fields added to ur infotype in PA30 screen.

let us see the various options.

1) With start date (options in SPRO are 3 or 4): This is applicable if you are selecting ‘display’ in PA30, with only the ‘start date’ entered in the ‘period’ selection field.

a) Option 3: Only the record valid on the entered date will be displayed. Therefore, for IT0002 with time constraint 1, you will be able to see only one record. (you will not be able to use ‘next record’ or ‘previous record’ buttons).

b) Option 4: All records valid between the entered date and the CPU date will be displayed. (You will be able to use ‘next record’ or ‘previous record’ buttons to switch between records).

2) With end date (options in SPRO is 5): This is applicable if you are selecting ‘display’ in PA30, with both ‘start date’ and ‘end date’ entered in the ‘period’ selection field. Here, all records valid on at least one day in the selected period will be shown. (Please note that you will be able to see the record, even if the end date of the record is outside the selected period).

3) Without any date (options in SPRO is 1 or 2): This is applicable if you are selecting ‘display’ in PA30, without entering any date in the ‘period’ selection field.

a) Option 1: All valid records will be shown. (You will be able to use ‘next record’ or ‘previous record’ buttons).

b) Option 4: All records valid between the the CPU date and end date will be displayed.

OM Infotypes

In some respects, OM infotypes are similar to PA infotypes:

  1. Each infotypes has validity period (begin date and end date)
  2. Infotypes are described by time constraints (the difference is that OM infotypes vary for different objects
Infotype 1000 is the basis for OM information. Each organizational object has a record of infotype 1000.
Examples where custom infotypes were created:
  • Positions are linked to holiday premuim pay, night shift allowance
  • Jobs need specific experience needs, competencies
T777I contains the OM infotypes. We need to add an entry in this table for new infotypes.
The master data stored in OM infotypes will be stored in HRP* tables. for example, relationship (infotype 1001) will be stored in HRP1001 table.
For a real-time scenario which needs new OM infotypes click here
For more details on how to prepare OM infotypes click here 

Additional actions infotype – IT0302

About Infotype 0302

The Situation: SAP do not allow storing two infotypes of Time Constraint 1 with the same subtype on the same day, because it would be mean the delimitation date for both will be the same, in which case first Infotype would be overwritten by the latter one.

Under What circumsatances: Why would one want to Run Two Action on SAME DAY?
Many occasions when an employee may experience multiple personnel actions on the same day.

EX.1: There are occasions where a person could be ending maternity leave and starting a career break on the same day
EX 2: You hired an employee on a certain day and then for some reason you need to perform, Transfer Action to other location or Country Reassignment etc

So can We do it?: The answer is YES, you can!

To handle similar situations SAP created “Additional Actions” (Infotype 0302) to capture these additional/multiple actions on same day.

Tell me more about this Infotype 0302: This infotype cannot be maintained directly, but it is located for viewing at the bottom of the Actions infotype (0000).

To make use of this functionality, you need to set it up using the following IMG path:Personnel Management -> Personnel Administration -> Customizing Procedures -> Actions ->Set up personnel actions

To activate Additional actions, run report RPUEVSUP.
This sets the the value of the semantic code EVSUP to 1 for the group ADMIN in table T77S0
In table T529A, it sets the indicator U0302 for all personnel action types.
Additional Actions should be activated for all personnel number ranges.

If we do the same action again (i.e. we hire the same employee twice), the actions infotype (IT000) stores the latest of the two actions. When we activate additional actions, we can do 2 different actions on the same day.

Features of Infotype 0302 Addiitonal Actions:Infotype 0302 Additional Actions allows you to automatically log all of the personnel action types that are performed for an employee on a specific date. It allows you to perform and document several personnel action types for an employee in the R/3 System on the same day.

You can display and edit the data records logged in the infotype Additional Actions (0302) on the list screen of the infotype Actions (0000),whether you want to use the automatic logging of personnel action types in the infotype Additional Actions (0302)which personnel action type should be saved, that is preserved, in the infotype Actions (0000) if you perform another personnel action type for the employee on the same day

The system then logs all personnel action types that are executed for an employee and their related reasons in the Additional Actions infotype (0302). – It creates an Additional Actions record (0302) on the specified key date for each record in the Actions infotype (0000).

Check the STAT2 field entries youhave in Table T529A. This is how SAP determines if an action is a statuschanging one and only allows one of these each day. IF field STAT2 isblank, not a status change. Otherwise, a change. If a second statuschanging action is done, it will replace the first. Also, if actioncode/reason code combination is already there, it will overwrite.

Infotypes – basics

Looking for other details about infotypes? Click here

Want to know the basics of an infotype? Click here

Want to enhance infotypes, Click here || Excel of all infotypes


 Infotypes are also called information types and are pre-defined templates to enter sensible related information for an employee or applicant. for eg an address infotype would have fields like street & house no, city, pin code.This infotype is unique and is represented by an infotype number eg address has infotype no 0006.

There other infotypes like

0000 – Actions (to capture employee movement info in the orgnization)
0001 – Organizational Assignment (to capture employee positioning in the organization)
0002 – Personal Data
0006 – Address
0007 – Planned Working Time (Store planned working hours for the employee.)
0008 – Basic Salary
0009 – Bank Details
0014 – Recurring Payment
0015 – Additional payment
0016 – Contract Elements
2006 – Absence Quotas

The above infotypes together in the same sequence form a part of the Hiring Action.To make you understand this better just try and recollect the contents of your offer letter which your organization might have given you. It would possibly read “We are delighted to offer you the position (IT 0001) of ______. You will belong to ______ department (IT 0001). Your joining date will be ______(IT0000 or IT0041)and you will be paid a salary of ______ (IT 0008). You will be paid monthly allowances ______ (IT 0008 or IT 0014) and we are also offering you a joining bonus of ______ (IT 0015). You will be eligible for annual leave of ______ days (IT 2006) and sick leave of ______ (IT 2006).You will be on a probation for six months from the date of joining (probation date & confirmation date in IT0016). Your working hours will be from ____ hrs to ____ hrs beginning Monday to Friday (IT 0007) and we look forward to your presence on date ______(IT 0016)……

I hope this gives you some idea of what an infotype is.

This must have raised a question in many minds that “Hey ! I got the offer during my recruitment so how come this is being referred to after hiring?” Well thats simple – this is because all your relevant data that was captured during recruitment was transferred to the the master (called HR master data)during the hiring process.

So how was it captured in recruitment?
Well, this was captured using recruitment actions like shortlist candidate, for interview, make offer, offer accepted till you join the organization and sign the joining letter when your data actually gets transferred from the Recruitment module to the Personnel Administration module.

Again this data was captured in recruitment infotypes.

So we can now get an idea that in SAP HR ,all data is captured in infotypes.

Question and Answer

What are info types ?
Infotypes, known as information types are units of human resources information formed by grouping related data fields together. These are represented in the sap hr system by a unique 4 digit number eg. Personal Data (0002), Address (0006) etc. All customer infotypes fall in the number range from 9000 to 9999. The fields in the infotype would vary based on the country grouping for eg if any employee belongs to country grouping 10 than he would have the SSN no field in the Personal Data infotype which would not be seen in same infotype for country grouping 99.

*Infotype numbering in SAP HR sub module
0000-0999 Personal Administration (HR Master Data)
1000-1999 PD Infotypes ( OM etc)
2000-2999 Time Infotypes
4000-4999 Recruitment Infotypes
So whenever you are searching for a customer defined infotype make sure your search is restricted between 9000 -9999. The infotypes relevant to retroactive accounting for payroll and time infotypes are defined in theIMG . Personnel Administration–>Customizing Procedures–>Infotypes–>Define fields relevant for retroactive accounting–> Retroactive accounting relevance for payroll and time per IT

Under this node you define for each infotype the following:- 1.Check if no organizational assignment exists for the employee in IT0001-Organizational Assignment and throw an error, warning or no message.So whenever you are searching for a customer defined infotype make sure your search is restricted between 9000 -9999.The infotypes relevant to retroactive accounting for payroll and time infotypes are defined in theIMG . Personnel Administration–>Customizing Procedures–>Infotypes–>Define fields relevant for retroactive accounting–> Retroactive accounting relevance for payroll and time per IT

Under this node you define for each infotype the following:-
1.Check if no organizational assignment exists for the employee in IT0001-Organizational Assignment and throw an error, warning or no message.
2.Maintenance of this infotype is permissible, permissible with warning, or not permissible after the employee has left the organization (employee in inactive status).
3.Entries in payroll past are permissible, not permissible or check for entries in the payroll past are infotype specific.
4.Infotype is not relevant for retroactive accounting, change in the infotype triggers retroactive accounting or retroactive accounting is field-dependent according to table T588G where the fields whose change in values should trigger retroactive accounting are defined. Hence you can see the significance of field triggers in retroactive accounting where retroactive accounting for a given infotype can be restricted to changes in the past to certain fields of the infotype.
If there is case that we need to specify certain info types for certain countries only, below are the

IMG path you can maintain:
SPRO–>Personnel Administration–>Customizing Procedures–> Assign infotypes to countries

Infotype Creation (with screenshots)

Click here for screenshots on how to create infotypes

Custom infotype creation || Adding a new field || Change the look and feel


Looking for other details about infotypes? Click here

Want to know the basics of an infotype? Click here

Want to enhance infotypes, Click here || Excel of all infotypes


 You can create custom specific PA infotypes by using t-code PM01. Custom specific infotypes are numbered between 9000-9999. Following are the main steps to follow:

1. Goto transaction PM01 – Create Infotype
2. Enter the Infotype no., select PS Struture radio button under Subobjects and click on Create All tab. This will create the Module Pool, interface screen, customising table entries and data dictionary objects for your infotype.
3. You will be directed to the Data Dictionary screen where you will define the PS structure components and types. Save and activate the PS Structure (PSnnnn).
4. Next you customise your Infotype attributes like Time contraints etc in view table V_T582A and mention technical data details like Screen number (2000 for single screen and 3000 for list screen), dialog module – RP_nnnn and database table PAnnnn etc.
5. Finally you go to Screen Painter and edit your interface screen 2000. Save and activate the screen.

You do not need to create/change the module pool program MPnnnn00 as it it automatically generated by PM01 using the Pnnnn structure.


TO EDIT INFOTYPES WITH SUBTYPES

1) Go to Transaction PM01.
2) Enter the custom Infotype number which you want to create (Should be a 4 digit number, start with 9).
3) Select the ‘Employee Infotype’ radio button.
4) Select the ‘PS Structure Infotype’.
5) Click on Create… A separate table maintenance window appears…
6) Create a PS structure with all the fields you want on the Infotype
7) Save and Activate the PS structure
8) Go back to the initial screen of PM01.
9) Click on ‘All’ push button. It takes a few moments.
10) Click on ‘Technical Characteristics’. Infotype list screen appears
11) Click on ‘Change’(pencil) button
12) Select your Infotype and click on ‘Detail’ (magnifying glass) button
13) Give ‘T591A’ as subtype table
14) Give ‘T591S’ as subtype txt tab
15) Give your subtype field as subtype field
16) Save and come back to PM01 initial screen
17) Click on ‘Infotype Characteristics’ … Infotype list screen appears
18) Click on ‘Change’ (pencil) button
19) Click on ‘New Entries’
20) Enter your Infotype number and short text
21) Here we have to set different Infotype Characteristics as per the requirement. (Better open another session with some standard Infotype’s infotype characteristics screen and use as the reference to fill yours)
22) Save your entries.
23) Now the Infotype is created and ready to use.
24) If you want to change the layout of the Infotype as per your requirement…
25) In the PM01 initial screen…Select ‘Screen’ radio button and give 2000 as the screen name, then click on edit.
26) In the next screen.. Select ‘Layout Editor’ and click ‘Change’.
27) Screen default layout appears…here you can design/modify the screen..change the attributes of the fields..etc.
28) Save and activate. (Don’t forget to ‘Activate at every level)