Logged Changes in Infotype Data – RPUAUD00

Use

 

This report RPUAUD00 is used to display all changes that were made using infotype change documents (short: change documents ).

 

Prerequisites

 

So that changes to infotype fields (change, create, delete) are recorded as documents, you must make sure that these fields are maintained in the views HR Documents: Infotypes to be Logged (V_T585A), HR Documents: Field Group Definition (V_T585B) and HR Documents: Field Group Characteristics (V_T585C).

An archive can only be displayed if it has been created with Archive Administration (transaction SARA).

 

Features

 

You can create the following types of documents with this report:

* Long-term documents

Long-term documents are created for revision purposes. Changes made to infotypes are written to the database or can be archived. Long-term documents remain available until you delete them. The archiving object is called PA_LDOC.

Long-term documents evaluate data according to personnel numbers and infotypes. For this reason, the columns PersNo (personnel number) and Inftyp (infotype) are displayed at the top of the drilldown list.

* Short-term documents

Short-term documents are stored in the database. The data for short-term documents is selected according to date and time. In contrast to long-term documents, the columns Date and Time are displayed at the top of the drilldown list.

 

Selection

 

Specify the type of documents that you want to create under Read documents from database. To specify a document type, set the relevant indicator.

Under Selection, specify:

* which transaction classes are to be included in the selection with the relevant indicators
* which employees are to be selected, in the Personnel number field
* which data the system is to evaluate, in the Infotype field
* whether a specific change date, or a certain interval period is to be considered, in the Change date field
* whether you want to display the changes made by a specific user, in the User name field

 

Note

 

As a rule, the system reads the data from the database.

If you want additional archived data to be read, select Read from archive. Additional selection options are displayed under Archive selection:

* Also read from database

The documents currently in the database that belong to the archived data and meet the selection criteria are also displayed.

* Archive selection by user

This takes you to the Archive Administration: Read Data Selection screen. Select the required archive.

Specify how the documents are to be output, under Output options.

* Direct output of docs
* Output program selections
* New page per doc.

Only set this indicator if you have selected Direct output of docs..

* Sort

If you set one of the following indicators, the data is sorted in accordance with the indicators:

* Time
* Personnel number
* Infotype
* User
* Default currency

 

Output

 

The results are displayed in accordance with your Output options:

* Drilldown list

If you have not made any selections under Output options, the list contains an overview of the documents.

* Long-term documents

Thc columns at the head of the long-term documents are always displayed in this sequence: PersNo (personnel number), Inftyp (infotype), Date, Time, SqNo (sequence number) and Changed by.

* Short-term documents

Thc columns at the head of the short-term documents are always displayed in this sequence: Date, Time, SqNo (sequence number), PersNo (personnel number), Inftyp (infotype), and Changed by.

* Display program selections

If you have made a selection here, the output is in the form of a drilldown list. The selection options are also output.

* Detail List

* Documents

If you have selected Direct output of docs, the documents are displayed. The documents contain the information taken from the head of the drilldown table, and details on the changes made in an infotype.

If you have also selected New page per doc., each document is printed on a separate page.

 

Time Constraints in HR Master Data

Definition

 

Time constraints guarantee that exactly the data the system needs to be able to correctly process the employee data, handle personnel administration processes and run payroll for an employee is available in the system. Time constraints keep you from storing mutually incompatible data and prevent gaps from occurring in the data history.


Use

You use time constraints to define the following:

· Whether an infotype record must exist for an employee in the system

· Whether further records of the same infotypes may exist

· Whether these records can overlap in the validity period.

For certain infotypes, you can also assign different time constraints in relation to the infotype’s subtype.

When you enter infotypes, the system automatically checks if your input satisfies the time constraints’ conditions, and reacts by automatically delimiting data records or issuing error messages.


Structure

 

· Time Constraint 1

For the entire time that the employee works at the enterprise, exactly one valid infotype record must exist. The validity periods of the individual records must not overlap. When you create a new record, the system automatically uses the start date of the new record as the delimitation date of the old record. Gaps are only allowed between the employee’s entry date and the start date of the first record.

Time constraint 1 must be used for all of the infotypes containing information that must be available at all times. This is particularly true of personal and organizational assignment data.

 

Example

An Organizational Assignment infotype record (0001) must exist for all active or inactive employees in the SAP System. The system needs the data stored in this infotype for all business processes.

In addition, this data must be unique, in other words, the system must know precisely to which organizational units the employee belongs. That’s why only one record may exist at the same time.

 

· Time Constraint 2

No more than one valid record can exist at any one time. Records with constraint 2 must not overlap. Their existence is not obligatory. When you create a new record, the system delimits the previous record, if one exists. If the system delimits a record because of time constraint 2, it issues an appropriate message.

 

· Time Constraint 3

Any number of valid records can exist at any one time. The individual records do not conflict with each other.

 

Example

In the Powers of Attorney infotype (0030), you can store different powers of attorney. That’s why any number of records for this infotype can exist at the same time. Since not every employee in your company has powers of attorney, a record for this infotype does not have to exist in the system.

 

· Time Constraint A

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.

 

· Time Constraint 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.

 

· Time Constraint T

Infotype records with time constraint T depend on the subtype.

 

Example

For the Addresses infotype (0030), you can assign a different time constraint for each subtype. In this way, you can make sure that a main address always exists for the employee and you can also enter temporary residences, if necessary.

 

· Time Constraint Z

The infotypes you use for entering working and absence time have a special time constraint behavior. For more information, see Time Constraints in Time Management.

Payroll results – Infotype 402

Payroll results can be held in infotype 402, for this we need to do some configuration.
IMG Menu path – Personnel Admin –> Personnel Management –> HRIS –> Payroll Results.

Define Evaluation Results: The evaluation wage type is the name of the field – note it is not the actual wage type. The cumulation can be either M (Monthly cumulation), Q (Quarterly cumulation) and Y (Annual cumulation). If results have to be saved on IT 0402 this should be left blank. These 3 values relate to infotypes 0458 (Accounting infotype), 0459 (Quarterly Cumulation) and 0460 (Annual cumulation). The text entered in the field “Evaluation WTT Text” will be seen on the infotype. Choose either an amount or a number for the wage type.

Assign Wage Types: In this screen you do much the same as in the first step. In addition you need to link the different wage types to your evaluation wage type. You can also tick the checkbox to indicate that the wage type’s sign should change.

Set Up Payroll Accounting Infotypes: Highlight the wage type where you would like the results to appear – usually 402 to start with. Click on the evaluation assignment icon. Create your entry in the table that appears. Go back to the previous screen, select the infotype and click on the generate icon. You will notice the tick on the “generated” column once this has been done. The infotype should also be active. If you are doing this for the first time, you will need to tick the “acitve” box once you have generated the infotype.

Set Up Assignment for Payroll: Ensure your infotype exists in this table if you wish to have the infotype updated during the course of a payroll run. If you don’t have any data in this table, you can still run the report RPABRI00 to manually populate the infotypes.

So there are to ways to save the payroll results in 402 a) Maintain entries in T521F to automatically update infotype 402 after the payroll run. b) Run the RPABRI00 program to move the payroll data into infotype 402.

Configure OM Infotypes – add/hide tabs

For Example: Hiding or adding the Address infotype tab which gets displayed at the bottom of the PPOME screen.

                The tabs for infotypes can be configured by using the table T77OMTABUS

Steps to configure:

1.       Select the scenario OME0 (Organization and Staffing) from Scenario Definition (Hierarchy Framework).

2.       With the selected scenario, select Tab Page in Scenario for each Object Type tab on the left side under the tab Scenario Definition (Hierarchy Framework).

3.       Double click on the Tab Page in Scenario for each Object Type with the selected scenario.

4.       It will display columns like scenarios, Object type, tab page, sequence, report name etc. The last column would be Do not Display column. It should be checked if that particular infotype for Object Type needs to be displayed else it should be unchecked. 

 

Note: The columns are the combinations of Object type, tab page etc. So while performing the Do not Display column activity, these combinations should be checked thoroughly based on the requirement.

Developing OM Infotypes – PPCI

Although the need for creating OM ifotypes is rare, some projects do require this knowledge. In some ways OM infotypes are similar to their PA counterparts. For example:

  • Infotypes have a validity period – start date and end date
  • Each Organizational object has a record of infotype 1000 (object infotype)
OM Objects and infotypes are used when defining the organizational plan. From the user’s standpoint, the organizational plan is a display of the organizational structure that shows relationships between objects such as organizational units, positions and persons.
The most frequently used organizational objects are organizational units, position, job and person. The relationships between objects are represented in Infotype 1001. These infotypes form the organizational structure or hierarchy. The relation is defined in both the related objects.
PPCI (Personal Planning Infotype Copier) is used to develop OM infotypes. Suppose the client demands maximum loan limit to be defined for each and every position, then this is defined by creating a new OM infotype.
Use SE11 (ABAP Dictionary) to create a table. Create a few sample records in the table. It is a good idea to create the elementary search help ZLOAN in transaction SE11 with the selection method ZLOAN and the export parameter ZTTYP.

Employee Grievance – Infotype 102

The Grievance Process is triggered when an employee files a formal complaint against another employee or when a Supervisor, Manager, or the Human Resources department needs to document discipline for an employee. This process will also be utilized to document any necessary Grievance Resolution.

The Grievance Process has two steps: A grievance is filed against an employee and documented, and the discipline resulting from the filed Grievance is documented.

Use Transaction Code PA30, Go to infotype 102 (Grievances) and press Create button.

Select the subtype of grievance – (1 Greivance, 2 Discipline, 3 Harassment)

Select reason for grievance, supervisor name, grievance status etc.

IT 0105 – Communications

When a new subtype is created under Infotype 0105 Communications, how can we configure the new subtype to be a Short ID field (USRID) or Long ID field (USRID_LONG)?

The subtype of a Communications Infotype (IT 0105) can be configured either to be a short ID (30 char) or a long ID (241 char).

Use TCode SM31. Go to view V_T591C “Recipient Type for Communication Type”. This is a place where you can mention, what type of communication is your subtype (Ex: Text, Telephone, Email Address etc.) and also indicate if the new Subtype is a Long ID using the check box.

In addition, you can also define the Time Constraint of the new subtype.

Also try HRUSER – and link an user ID to an employee. linking this creates infotype 0105 for the employee HR master record

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.