OM – Easy access paths

SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOCE
SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOME
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change > Go to > Reporting structure
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment > maintain cost center
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Position 

SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOCE
SAP Easy Access > SAP Menu > Organizational Management> Organizational Plan > Organization and staffing > PPOME
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD Change > Go to > Reporting structure
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment > maintain cost center
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Position 
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Account Assignment 
SAP Easy Access > SAP Menu > Organizational Management> Expert Mode > Simple Maintenance > PPOM_OLD > Go To > Cost Distribution

OM – PA Integration

To make integration between PA and OM (also read as integration between PA and PD)

IMG–> PA–> OM–> Basic settings –> integration–>set up integration with PA

set the integration switch PLOGI ORGA to X
Table T77S0 is the major table for OM – PA integration


Reports in relation to PA – OM


Report RHINTE00 is used to transfer data from PA to OM
RHINTE10 is to transfer OM data to PA tables
RHINTE30 is to update IT0001 (org assignment) for the person you have selected
RHINTE20 is to determine whether the data relevant for integration is available in PA and OM

Overview

It is important to realize that in PA, there are tables that contain objects from OM, i.e. for those items displayed on infotype 0001 Organizational Assignment. Sometimes the tables can get ‘out of step’ with those in PD – table HRP1000.

The tables are:

T513, T513S Object type C (Job)

T528B, T528T Object types S (Position) and A (Work center)

T527X Object type O (Organizational unit)

RHINTE00
This loops through all employees in PA by looking at positions on infotype 0001. It checks thecorresponding person to position relationship exists in PD (A008), if not it is created.

RHINTE10
Generally, the program RHINTE20 will be used instead of this one. This program loops through the PD table HRP1000. For each job, position, work centre and organization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also. The main difference with this program as opposed to RHINTE20 is that this one has the option to delete items from the PA tables, which no longer exist in PD.

RHINTE20
This program loops through the PD table HRP1000. For each job, position, work centre andorganization unit, corresponding entry is created in the PA tables, which are shown above. Run this with evaluation path o_s_p, which runs through Org units, jobs and positions or find a suitable alternative if you wish to update work centers also.

OM – Configuration Steps

Configurations Steps:

————————-

IMGPersonnel management Organizational management  Basic settings  Maintain number ranges  set up number assignment for all plan versions

Maintain object type:
IMGPersonnel management  Organizational management  Basic settings  Data model enhancement  maintain object type

Maintain infotypes
IMGPersonnel management Organizational management  Basic settings  Data model enhancement—infotype maintenance  maintain infotypes

Relationaship maintenance:
IMGPersonnel management Organisational management  Basic settings  Data model enhancement  Relationship maintenance  maintain relationships

Maintain evaluation paths:
IMGPersonnel management Organisational management  Basic settings Maintain evaluation paths

Maintain personnel actions:
IMGPersonnel management Organisational management  Basic settings Maintain personnel actions

Activate inheritance of account assignment features
IMGPersonnel management Organisational management  Basic settings Activate inheritance of account assignment features

Setup integration with Personnel Administration
IMGPersonnel management Organisational management  Basic settings Integration  Setup integration with PA

Transfer data from Pa
IMGPersonnel management Organisational management  Basic settings integration  transfer data from PA

Perepare integration with Pa
MGPersonnel management Organisational management  Basic settings integration Prepare integration with PA

Transfer data to PA
IMGPersonnel management Organisational management  Basic settings integration Transfer data to PA

Check integration consistency
IMGPersonnel management Organisational management  Basic settings integration Check integration consistency



To Set active plan version:
use command OOAP

Links to PPT’s

This is the link to the SAP Basics PPT.

Read/Download this if you want to know the basics of SAP, what is ERP, what modules does SAP provide, etc.
http://www.scribd.com/share/upload/5860000/2fwto6ad2lhvqm7fq1kr 
please add your comments….

EIC – Employee Interaction Center

This is the CRM face of HCM.

To explain this consider the below scenario:
HCM helps in managing payroll/benefits/time management/trainings/events management, etc.
Self Services(ESS/MSS) help HR to reduce effort by imparting work to associates themselves.
EIC is the next step where in addition to ESS/MSS, an employee can contact an EIC agent through mail/phone/chat/fax etc to answer the HR queries and needs.

this means value added services to the client
reduction in costs
streamlining business processes
enhancing service quality

The following SAP HR 4.6C modules must be implemented: Master Data, Payroll (optional: benefits, compensation, time management). The robustness of the EIC solution will depend on the HCM modules implemented.

for more queries refer to the below links

http://www.eicexperts.com/Docs/EIC_FAQ.pdf

http://www.eicexperts.com/Docs/Employee%20Interaction%20Center%20Solution%20Brief.pdf
http://www.eicexperts.com/Docs/EIC_Deployment_Options.pdf

Payroll for Concurrent Employment

Payroll for concurrent employment

 

If you have activated concurrent employment in your SAP R/3 System, the system uses a version of the payroll program, personnel calculation schemas, and functions that all support concurrent employment.  A concurrently employed person has several personnel assignments stored in SAP R/3 as personnel numbers. The personnel assignments that belong to the same payroll area have payroll run for them at the same time. SAP R/3 therefore needs data from all personnel assignments at the same time for some processing steps in the personnel calculation schema. For these processing steps, SAP R/3 processes all personnel assignments in a synchronization point. At other places in the personnel calculation schema, SAP R/3 runs through the same steps several times, once per personnel assignment. The start and end of the processing per personnel assignment is indicated by the new function XPA. The payroll program generates a payroll result for each employee consisting of one or several parts on the level of the personnel assignment, and a common part for the person.  The payroll log shows the personnel assignment level and the person level. Using program H99_DISPLAY_PAYRESULT (Displaying the Payroll Results), you can also display the payroll result on both the personnel assignment level and person level.

 

If you want to evaluate wage types, which are stored in the payroll result on the person level, for each of a concurrently employed person’s personnel assignments, you must distribute them to the personnel assignments using the new function XDIST (Distribution of Person-Related Wage Types For Concurrent Employment).

 

 

Remuneration statement for concurrent employment

In a system in which concurrent employment is active, SAP R/3 outputs  the data of several personnel assignments of a concurrently employed person in one remuneration statement if payroll is run for them together.

 

 

Wage and salary payment for concurrent employment

If you use concurrent employment, you cannot implement the payment process

 

Cash Payment with Cash Breakdown List

 Based on wage type /557 (Cash Payment) or programs RPCMLI00 and RPCMLI09 (Cash Breakdown List). If you use concurrent employment and want to effect wage and salary payments in cash, you can implement the payment process

 

 

Posting to Accounting for concurrent employment

When posting to Accounting, SAP R/3 needs organizational information about the employee to be able to post wage types correctly. The system takes the information from table WPBP (Work Place/Basic Pay) in the payroll result. However, with concurrent employment, the wage types on the person level (in table RT_PERSON) are not directly related to organizational information about the employee. In this case, SAP R/3 uses the organizational information from table WPBP in the payroll result of the personnel assignment that is specified for each wage type entry in the field

 

 

PostPerno

In table RT_PERSON. Different personnel assignments can be specified for the wage type entries.

 

 

Effects on the dataset

In a system in which concurrent employment is active, SAP R/3 uses new tables, programs, functions, and personnel calculation schemas. In a system that supports concurrent employment, some programs and functions also have additional or changed functionality.

 

Note

In the following, a lowercase x stands for a country-specific letter, that is, K for Canada or U for USA.

 

 

New tables in the payroll result

Some of the wage types processed in payroll are stored at the person level. To do this, SAP R/3 uses the following tables in the payroll result:

         o RT_PERSON (Results Table for Person)

         o CRT_PERSON (Cumulated Results Table for Person)

         o BT_PERSON (Payment Information Table for Person)

 

 

New programs

o RPCALCx0_CE (Payroll Driver) Version of program RPCALCx0 (Payroll Driver) that supports  concurrent employment.

 o RPCEDTx0_CE (Remuneration Statement – Person) Version of program RPCEDTx0 (Remuneration Statement) that supports concurrent employment.

o RPCDTCx0_CE (Data Medium Exchange Preliminary Program); only for USA Version of program RPCDTCx0 (Data Medium Exchange Preliminary Program) that supports concurrent employment.

o RPCIPE00_CE (Posting to Accounting: Create Posting Run) Version of program RPCIPE00 (Posting to Accounting: Generate Posting Run) that supports concurrent employment.

 

 

Changed program

o H99_DISPLAY_PAYRESULT (Displaying Payroll Results) Enables you to display payroll results on the person level.

 

 

New functions

o XPA (Start and End of Processing per Personnel Assignment)

Indicates the start and end of a loop in the personnel calculation schema, in which the personnel assignments of an employee are processed separately. The loop is started with XPA LOOP and ended with XPA ENDL. Outside of this loop, all personnel assignments of an employee are processed together within synchronization points.

o XWPBP (Compare WPBP Splits for Concurrent Employment)

Ensures that the same WPBP splits are set for a concurrently employed person in all personnel assignments to which the same grouping value is assigned for grouping reason XXPY (Payroll Run (Payroll Area)).

o PRBEG (Deductions: Preparation of V0, OV0, ORT, etc. for Retroactive Accounting)

 Prepares tables V0 (Variable Assignment), OV0, and ORT for deductions within a retroactive accounting run when arrears are processed, and ensures the data in these tables is consistent.

o XNET (Calculation of Net Amount)

Contains some of the processing steps performed by personnel calculation rules X040 (Payment Amount Before Transfer) and X041 (Read Balances Carried Forward (Differences)) in a system without concurrent employment.

o XPAY (Determining Payments)

 –  Contains the processing steps performed by functions P0009 (Processing Request for Bank Details) and P0011 (Processing Request for External Transfers) in a system without concurrent employment.

 –  Contains some of the processing steps performed by personnel calculation rules X040 (Payment Amount Before Transfer), X04A (Import Claim from Previous Period), and X047 (Cumulation of Payment Amount) in a system without concurrent employment.

o XRETR (Retroactive Accounting)

Contains the processing steps performed by personnel calculation rules X041 (Read Balances Carried Forward (Differences)), X042 (Formation of Differences, Transfer of Non-Revisable Wage Types), and X043 (Storage of New Payment Amount according to DT) in a system without concurrent employment.

o XDIST (Distribution of Person-Related Wage Types for Concurrent Employment)

Distributes person-related wage types to the personnel assignments of a concurrently employed person.

 

 

Changed functions

o EXPRT (Export Interim or Final Results to Databases)

 –  Exports payroll results to file PCL2 for all personnel assignments of an employee for which the payroll has run.

 –  Performs the processing steps contained in personnel calculation rule X070 (Termination if table IT is not Empty) in a system without concurrent employment.

o ADDCU (Update Cumulations)

 –  Forms cumulations per personnel assignment. For wage types stored on the person level, this function also forms cumulations per grouping stored for the wage type.

 –  Stores the relevant wage types of table RT_PERSON in table CRT_PERSON too.

 –  Performs the processing steps that are contained in function SORT (Sort Internal Tables) in a system without concurrent employment.

o SETCU (Process Previous Cumulations)

–  Transfers table CRT per personnel assignment and table CRT_PERSON per person from the previous payroll period to the current payroll period.

–  Also forms table LRT_PERSON from table RT_PERSON of the previous payroll period.

–  Performs on the personnel assignment level the processing steps that are performed by personnel calculation rule X006 (Import Relevant Wage Types to LRT) in a system without concurrent employment.

o P9ZNC (Zero Net Checks, Check Existence of IT9)

Creates an entry in table BT_PERSON instead of table BT.

o LIMIT (Limiting Deductions)

Forms wage type classes per personnel assignment. You can also use this function to specify a limit for a personnel assignment grouping. This limit overrides the limits for individual personnel assignments of this grouping.

o PREND (Modify DDNTK Table after Last Loop)

Controls whether personnel assignments of an employee are processed in the following payroll period if they are inactive but still have entries in table ARRRS.

 

 

New personnel calculation schemas

The new standard personnel calculation schema x00C for payroll was adjusted for the demands of concurrent employment. It has a different structure to the personnel calculation schema x000 and contains the new functions and new subschemas that support concurrent employment.

   

Restrictions

 All personnel assignments of a concurrently employed person that are under the same employer must have the same payroll area and payroll periodicity.

 If a concurrently employed person changes his or her employer for one personnel assignment, you have to create a new personnel assignment, i.e. a new personnel number. This also applies to retroactive changes in employer.

 Personnel calculation schemas are only processed at the personnel assignment level, not at the person level.

 You can only create company loans for individual personnel assignments, not for persons. If you want to create a company loan for a concurrently employed person, you have to store it is one of his or her personnel assignments. When this personnel assignment comes to an end you must transfer the company loan to another personnel assignment.

 Deductions are only processed at the personnel assignment level, not the person level.

 Averages are only processed at the personnel assignment level, not the person level.

 Using the Business Information Warehouse (BW) you can only evaluate payroll results, which payroll created on the person level, if you previously used function XDIST (Distribution of Person-Related Wage Types for Concurrent Employment) to distribute the results to the personnel assignments of the relevant employee.

 The off-cycle activities are not presently enabled for concurrent employment.

 Background processing with the HR Process Workbench is not presently enabled for concurrent employment.

 Concurrent employment is currently only available for the Canada and USA country versions.

 

 

Effects on Customizing

For concurrent employment, make the following additional settings in Customizing for Payroll

😮  In the section Distribute Person-Related Wage Types With Concurrent Employment, specify which person-related wage types are distributed by function XDIST to the personnel assignments ofan employee, and how distribution is effected.

 o  Section Limits for Deductions

: –  When creating a rule for limits, you can determine whether the amount of the rule for limits is formed on the person or personnel assignment level. You can specify this in the IMG activity Define Rules for Limits in the field From Person Tables

. –  In the IMG activity Set Up Wage Type Classes and Attach Limits, you can assign a grouping reason to a wage type class.

Batch Data Communication (BDC) in SAP R/3

Introduction

The early versions of R/3, SAP has been providing batch interfacing techniques. Among these techniques, Batch Data Communication (BDC) is the oldest one. BDC is not bi-directional; it is an integration tool in its typical form. It can only be used for uploading data into RJ3. BDC works through an ABAP program and works on the principle of simulating user input for transactional screen.

The purpose of the Batch Data Communication is to transfer data. The BDC can transfer data from one SAP System to another SAP System or can transfer data from non-SAP System to SAP System too. To transfer data BDC uses normal transaction codes. Two methods are provided to BDC to do this work.

SAP has provided two different types of methods for BDC to do its work. Among these, the first one is called the classical method or session method. Through this method the data can be read by the BDC program from a sequential dataset file. This sequential dataset file is stored in batch-input session. In order to .run the transaction in this session, what one needs is to execute the session. For this, follow these few steps: you can start and subsequently monitor the session firstly from – System à Services à Batch Input or have the session run in the background. In this method to generate the required session, you have to use the function module BDC _ NSERT and BDC _CLOSE.

In the second method the BDC has to use the ABAP statement CALL TRANSACTION USING statement to run a transaction. In the second method, unlike in the first type, you do not need BDC to create a session.


Data Transfer

During the process of data transfer, data is transferred into the SAP R/3 System. This transfer is from an external system to SAP R/3 system. Whenever you transfer data from an external system into an R/3 System, you can use data transfer because it is installed and regularly transfers data from an external system into an R/3 System.

As discussed, with the help of BDC, you can transfer the required data from a non-SAP system to an SAP system. For this kind of data transfer you are required to write an ABAP program. This ABAP program would help to export the concerned data to a sequential dataset file. The data in this file has to be stored. This should be stored in a format, which is acceptable to SAP batch input program. But, to transfer data from a SAP system to another SAP system, you can take the aid of RFC or CPI-C.

SAP application supports the data transfer of numerous SAP business objects. The said data transfer program specifies the data format definition, which is necessary to import the data into the R/3 System. There are three methods available for transferring data:

Direct Input: In this method the SAP function modules execute the consistency checks. However, there are other means of checking with the help of screens. The Direct Input Method has considerable performance advantages.

Call Transaction: In this method you can check the data consistency with the help of screen logic.

Batch Input Session: In this method data consistency is checked with the help of screen logic.

Direct Input Method

Among the methods of data transfer through BDC, direct input method is the one that is used, especially in case of transferring large amount of data. In order to enhance the batch input procedure, the system offers you with the direct input technique.

There is a distinction between the batch input technique and this technique. Unlike batch input technique, this technique does not create sessions. Instead, it stores the data directly. Moreover, it does not process screens. The data has to be entered directly into the corresponding database tables. The system calls a number of function modules which execute necessary checks, if any required. In the case of errors, the direct input technique has a facility to restart the entire mechanism. However, if you want to restart the entire mechanism in case you faced an error, then direct input programs must be executed in the background only. One has to use program RBMVSHOW or Transaction BMV0 to maintain and start these programs.

Call Transaction Method

Call Transaction method is another method used for Data Transfer. In this type of method your program will use the ABAP statement CALL TRANSACTION USING in order to run a SAP transaction. In this type external data need not be deposited in a session for being processed later on. Instead, the entire batch input process takes place inline in your program.

Here, the data transfer program must convert the data that has to be transferred into the SAP system. This is as per requirement by the SAP data structure or the transaction which is using it. It is to be remembered that a conversion of the data types may be necessary at different times during the process.

Suppose there is a data type mismatch then you have to convert the data types to type C. In this regard the data transfer program should be capable of exporting the data in SAP format to the sequential file. At the time of uploading the data into the SAP system, the BDC program reads the data from the above mentioned sequential file.

Batch Input Session Method

This is the third method for data transfer. If you use the batch input method to transfer data, then you should remember that an ABAP program has to read the external data which is to be entered in the R/3 System. Subsequently, it stores the concerned data a “batch input session.” The batch Input session records the actions which are required in the process of transferring data into the system. This can be done by using normal SAP transactions.

As soon as the program generates the said session, you will be able to run the session in order to execute the SAP transactions in it. Moreover, you can start the session, and at the same time, can monitor a session with the help of batch input management function. For this you have to choose:

System à Services à Batch input. Moreover, you can have the session run in the background processing.

Writing a Data Transfer Program

If you want to write a data transfer program, you have to follow the steps mentioned below.

Firstly, you will analyze the structure of the existing data. Subsequently, your job is to specify the conversions, which are essential to fill the SAP data structures.

Secondly, you have to generate the SAP data structure. In case the program is written in ABAP, you will require only the required tables in the concerned program with the help of TABLES statement.

Thirdly, you will have to initialize the SAP data structure.

Fourthly, fill the structure with data, performing any conversions and error checking that are required.

Finally, you will write the sequential file. In the SAP system this sequential file is typically required for making the data available to the batch input program.

Batch Input Method

Batch input method is a type of data transfer method. It is used for bulk data transfer; it is one of the primary ways by which data can transferred into the R/3 System. This method is not for near real-time data transfers.

There are various typical uses of batch input. One of the ways includes the one-time import of data. This import of data is from a legacy system into a newly installed R/3 System. In addition to it, another typical use is for periodic (i.e. hourly, daily…, and so on) transfers of data. These transfers are from external systems or legacy systems which are still in use into R/3 system where all enterprise data is consolidated.

The R/3 applications deliver different programs for batch input, which are ready to be used. However, in some cases a customer has to write his or her own batch input program. This is required in order to convert the concerned data from a legacy System or from a proprietary format into an R/3 data format.

The process flows for a batch input are discussed below.

Data Transfer Decision-Making: It is with a decision to transfer data from an external source into R/3 that the process of batch input begins. It is probable that the external source may be a legacy system that is being replaced. A one-time bulk data transfer is foreseen in this regard. Alternatively, the external source may be an external system that is to remain in use. In this case, a regularly recurring bulk data transfer is foreseen.

Setting up Batch-Input for Data Transfers: If R/3 standard one-time or regular data transfers are required, then by means of customizing settings in the R/3 Customizing System in SAP ASAP set up will occur. You must set up custom batch input procedures by hand, which means the system administrator must schedule the data conversion program that creates the batch input session. The system administrator and the batch input programmer must determine the following: how frequently data is made available from the external system, how frequently the conversion program should run, and whether the conversion program runs in R/3 (ABAP program) or in a host system (external program).

Processing Batch Input Sessions: When a batch input session is processed, then the actual transfer of data into R/3 takes place. Little attention is required in processing of batch input sessions by the system administrator. Usually, the starting of batch input sessions is automated by the system administrator. If necessary, the administrators can also start batch input session explicitly from transaction SM35.

Checking Batch Input Sessions: For a system administrator the routine activity is to check daily or more frequently in transaction SM35 whether all batch input sessions have been completed successfully. It is the schedule for running batch input sessions on which the schedule for checking sessions depends upon. For doing this check the R/3 System provides easy-to-use batch input management tools.

Analyzing Errors: It is the duty of the system administrator to analyze the problem if one or more transactions in a session end in errors. Usually, the assistance of the affected data entry specialist or department for this analysis will be needed by the system administrator. In the situation where the problem was caused by incorrect data conversion or incorrect generation of the batch input session then the programmer who wrote the data conversion program may also need  to be involved.

Error Handling in Batch Input Method

It is found that most problems usually fall into one of the following two categories discussed below.

In this case either required data is missing from the batch-input session or invalid data has been included in the session. Errors in the data conversion program or the presence of unexpected types of data or incorrect data in the legacy database are the possible external causes of this type of problem. Within R/3, the causes for this type of problem include incorrect or incomplete customizing in an application. For example, a legacy data type may not have been foreseen in the check table entries made in application customizing.

This case mainly includes technical/programming problems. The data is entered by a batch input session by running R/3 transactions non- interactively. Therefore, a typical technical or programming problem is the incorrect identification of one of the data fields in a transaction. Thus, the conversion program may not fill a required data field or may have provided invalid values.

Conclusion

I have gone through the details of batch data communication and various methods used to transfer data. One can make use of BDC to transfer data from a SAP to SAP system. In addition, it can transfer data from a non SAP system to SAP system too. I have discussed the various methods of BDC and the error handling in the respective methods.

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

  1. 0000 – Actions (to capture employee movement info in the orgnization)
  2. 0001 – Organizational Assignment (to capture employee positioning in the organization)
  3. 0002 – Personal Data
  4. 0006 – Address
  5. 0007 – Planned Working Time (Store planned working hours for the employee.)
  6. 0008 – Basic Salary
  7. 0009 – Bank Details
  8. 0014 – Recurring Payment
  9. 0015 – Additional payment
  10. 0016 – Contract Elements
  11. 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

1.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

  1. 0000-0999 Personal Administration (HR Master Data)
  2. 1000-1999 PD Infotypes ( OM etc)
  3. 2000-2999 Time Infotypes
  4. 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 the
IMG . 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 the
IMG . 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)

Personnel Number Generation

For SAP not to generate personnel numbers:

IMG – Personnel Management -> Personnel Administration -> Basic
Settings -> PE03 – Determine defaults for number ranges

In this work step we use the feature NUMKR, to determine whether we
want to use internal or external number assignment when hiring new
employees

For e.g.
01 – External
02 – Internal (use this for your case)