SAP HR ABAP, HCM Training Material and Tutorials » ABAP HR

Creation of Custom Infotype in HR ABAP

admin — Fri, 24 Sep 2010 18:31:31 +0000

Step By Step process to create Custom Infotype

For list of Online Training Courses look at the above SAP TRAINING page.

Go to Transaction PM01 to Create custom Infotype.
Enter the custom Infotype number to be created. The number should be between the customer name space 9001 – 9999. This is the no. range interval to be used for the Custom Infotypes.
See to it that the ‘Employee Infotype’ and the ‘PS Structure’ radio buttons are selected on the screen.
Click on ‘All’ push button on the screen. A separate Dictionary window appears on the screen.
Maintain the structure (Provide fields) which will be included in the current custom Infotype. Include all the fields that are needed in the Infotype.
The PAKEY/PBKEY and PSHD1 structures are not required to be provided while creating the custom Infotype. They are created by the SAP automatically.
Save and Activate the PS structure and go back to the initial screen of PM01.
Now, click on ‘Technical Characteristics’. Infotype list screen appears.
Click on ‘Change’ (pencil) button and select your Infotype and click on ‘Detail’ (magnifying glass) button.
Save and come back to the PM01 initial screen.
Click on ‘Infotype Characteristics’. Infotype list screen appears.
Click on ‘Change’ (pencil) button and click on ‘New Entries’ button.
Enter your Infotype number and the short text for the Infotype.
Depending on the requirement, we will have to set the Infotype Characteristics. The best option would be to use the entries of a standard Infotype like 0000 (Actions) or 0001 (Org. Assignment) as a reference. Other way is to click on the F4 button for each parameter on the screen to understand its significance.
Save the entries.
Now the Infotype is created and ready to use.

Below additional information is provided for the above screen each field possible entries and its functionality.

Time constraint: 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 no time 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 Automatically controls whether the system automatically creates the Infotype record for an employee hiring or an applicant data entry action.

Infotypes with time constraint A 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 Time Constraint Reaction.

Maintenance permitted after leaving:

This field controls whether you can record master data after an employee has left the company. A warning tells you whether you are permitted to do so or not.

Indicator for entry of additional data:

Defines whether or not you can enter additional controlling objects for the Infotype.

Indicator: Text allowed for Infotype:

If you set this parameter, you can enter a text for Infotype records.

Indicator for access authorization (from/to date):

The Access auth. (access authorization) allows you to define the time period during which an Infotype can be accessed.

When you access Infotype data for a particular person (employee or applicant), the system reads his/her organizational assignment and the work area (Infotype, subtype and authorization level). (Also read the documentation on authorization objects HR Master data and HR Master data-extended check). Each Infotype will generally have records with different validity periods. One person may also have different organizational assignments (Organizational Assignment Infotype (0001)) over a certain time period. If different administrators (users) are responsible for these organizational assignments, this is taken into account when the authorization for a specific Infotype validity period is checked.

If you do not set this indicator (initial value), the administrator is authorized to access the Infotypes if the person had, has or will have an organizational assignment which, in accordance with the authorization profile allows him/her to access this data.

If you set this indicator (X), the authorization check depends on the current (system) date.

To simplify matters, the term ‘period of responsibility’ will be used in the following. If, during a particular period, a person has one (or more) organizational assignment(s) for which the administrator is responsible according to his/her authorization profile, then we refer to the entire validity period of this(these) organizational assignment(s) as the ‘period of responsibility’.

There are three different cases.

1. The period of responsibility begins in the future.

If the administrator has write authorization for the Infotype/subtype, this is valid for all Infotype records whose validity period is within the period of responsibility. Read authorization is valid for Infotype records which do not extend beyond the end of the period of responsibility.

2. The period of responsibility begins before the current date. Its end date is no more than a fixed number of days before the current date

In this case, write or read authorization is valid in all periods. There are no time restrictions on the authorizations of the administrator for the relevant Infotype records.

The tolerance period enables the administrator to access Infotype records that he/she was previously responsible for even if his period of responsibility has changed. You set up client-specific tolerance periods during the HR: Authorization main switch transaction.

3. The period of responsibility ends in the past. The end of the period of responsibility ends before the current date even if the tolerance period is taken into account.

In this case, the administrator does not have write authorization. Read authorization applies to Infotype records which are not valid beyond the end of the period of responsibility.

Reaction to: 1st date entered:

The three date reaction indicators control what type of databank search is carried out when no, one or two “dates” are entered on the selection screen.

Reaction to: First date entered

Allowed reaction indicators are:

3: a) Period indicator = I:

Record(s) valid on the date specified

b) Period indicator = S:

Record(s) whose key date is identical to the specified date

4: All records that were valid for at least one day between the date of entry and the CPU date.

Reaction to: 1st and 2nd dates entered:

The three date reaction indicators control what type of databank search is carried out when no, one or two “dates” are entered on the selection screen.

Reaction to: First and second dates entered

Allowed reaction indicators are:

5: All records that were valid for at least one day in the period specified.

Reaction to: No delimitation:

The three date reaction indicators control what type of databank search is carried out when no, one or two “dates” are entered on the selection screen.

Reaction to: No date specification

Reaction indicators that are allowed for no date delimitation:

1: Read all records

2: Record or records valid on CPU date

6: All records between CPU date and 31.12.9999

7: All records between 01.01.1900 and CPU date

Sort sequence of records:

Indicators for record sorting:

‘ ‘: in ascending order according to subtype, in descending order according to ‘from’ date of validity period

’1′: in descending order according to ‘from’ date of validity period, in ascending order according to subtype

’2′: in ascending order according to subtype, in ascending order according to ‘from’ date of validity period

’3′: in ascending order according to ‘from’ date of validity period, in ascending order according to subtype

Key for screen header layout

In table T582A Infotypes – Customer Specific Settings, each Infotype is assigned a header ID.

The following header IDs have been assigned:

00 – Initial screen of transactions PA20, PA30, PA51 and PA61

PB20, PB30, etc.

10 – Infotype 0000 – Actions
Infotype 4000 – Applicant Actions
03 – Infotype 0001 – Organizational Assignment
01 – Infotype 0002 – Personal Data
04 – All Infotypes of Time Management
02 – All other Infotypes

Header IDs are assigned a header modifier, from which the structure of the respective headers is defined, as well as the HR country modifier and transaction class in table T588I Assignment of Header ID/ Country Grouping to Header modifier.

Indicator specifying when data is chosen for the IT header:

You can use the Choose Data indicator to determine which selection period will be used to select data from the various Infotypes to structure the Infotype header.

Use

If you set the Choose Data indicator, you will use data that is valid for the start date of the current processed, or displayed, Infotype record to structure the Infotype header.
If you do not set the Selected Data indicator, the data that is valid for the system date will be used to structure the Infotype header.

Dependencies

By using the Data selection (Data Selection Control) indicator, you can implement both the start date and the system date in the Infotype Header Data Selection Control (T588H) table independently of the info(sub)type.

You must, however, have set the Choose Data indicator beforehand.

Example

A Basic Pay (0008) data record is valid from 01.01.1996 to 31.12.9999. The employee’s valid organizational assignment on 01.01.1996 should be displayed in the Infotype header.
The Personal Data (0002) Infotype is valid from the employee’s birth date.
There is no point in displaying the employee’s first valid organizational assignment since his or her birth date. Therefore, the system date is displayed for the employee’s valid organizational assignment.
A date-dependent text field is used for a field in the Organizational Assignment Infotype (0001) in the Infotype header.
The start date of the Organizational Assignment Infotype data record determined by the above settings is used to read this text. If more than one text is valid within the validity period of the Infotype record, the text that was valid at the start of the Infotype record is used.

Retroactive accounting relevance for payroll

When you make entries in the payroll past, the ‘Earliest Change in Master Data since Last Payroll ‘field is set in the Payroll Status Infotype (0003).

In the correction phase, when entries are made in the payroll past, the Payroll Correction field is also set.

When corrections are made in the current period, only the ‘Payroll Correction’ indicator is set.

Infotypes that are payroll relevant but not retroactive accounting relevant should be given the following keys:

Entry in past ‘E’

Retroactive accounting payroll ‘R’

Example

‘ ‘ = Infotype is not relevant to retroactive accounting,

‘R’ = Change triggers retroactive accounting,

‘T’ = Retroactive accounting is field-dependent according to T588G.

Reaction to Entry in Payroll Past

Permissibility of entries relating to the payroll past

SPACE (‘ ‘)

Entries which relate to past payroll periods are permitted.

This type of entry is like changing or creating a database record with a start date which lies in the last payroll period or prior to this. The system saves without displaying warning message.

‘X’

Entries which relate to past payroll periods are permitted. The system displays a warning message.

‘E’

Entries in the payroll past are not permitted. If payroll has has never been run for the employee in question, the entries are permitted.

‘I’

Whether or not entries in the payroll past are permitted depends on which Infotype is being processed. This entry is only suitable for certain Infotypes. If used in other Infotypes, the system does not perform a check.

Evaluating Repetitive Structures in HR ABAP Programming

admin — Thu, 20 May 2010 04:45:01 +0000

Before writing this post I would like to thank Manoj kumar, ShivrajSinha, Santhosh Somasekharan, Amolkumar Patil, Vishal Jindal, Bijay Kumar Barik, Devi, who has referred Abaphr.com in SAP SDN Forum.

In many master data Infotypes, data is entered in table form. This, for example, allows you to enter up to forty different wage types and their amounts. By scrolling, you can enter up to forty wage types. The structure of the wage type line is stored in the Infotype structure P0008, and the individual fields are numbered from one to forty. This means that each field of the wage type table is defined.

A loop offers a more streamlined method of evaluation. Here, one line of the repeat structure is evaluated each time the loop is executed

As SAP consultant you might know the structures. But what is the repetitive structures?. The sentence it self explains that in a structure, some fields are available multiple times with the sequence number change, like fieldname01, fieldname02, fieldname03 etc…

For example In Master data Infotypes we have:
Infotype 0008 (Basic Pay)
Infotype 0025 (Appraisals)
Infotype 0041 (Date Specifications)
Infotype 0052 (Wage Maintenance)

If we look at Infotype 0008 below fields are getting repeated 40 times (Lower versions of SAP only 20 times like 4.6C).
LGA01 – wage type1
BET01 – wage type Amount
ANZ01 – Number
EIN01 – Time/Measurement Unit
OPK01 – Operation Indicator for Wage Types

LGA02 – wage type2
BET02 – wage type amount
ANZ02 – Number
EIN02 – Time/Measurement Unit
OPK02 – Operation Indicator for Wage Types

Till

LGA40 – wage type40
BET40 – wage type amount
ANZ40 – Number
EIN40 – Time/Measurement Unit
OPK40 – Operation Indicator for Wage Types

For the above scenario we have multiple wage types for one Personnel number for one particular period. Viz.. Basic Pay, House rent allowance, conveyance, special allowance, car allowance, salary exempt, salary non exempt (All these are wage types).
For the above scenario wage types are stored in LGA01, LGA02, LGA03, LGA04, LGA05, LGA06, LGA07, and its amount correspondingly BET01, BET02, BET03, BET04, BET05, BET06, BET07. This is the brief overview about repetitive structures in SAP.

Now as a technical consultant your job starts. How do you read the data form repetitive structure Infotypes. For example we need to select basic wage from Infotype 0008 and display in report. We are not sure in which field the basic wage is going to be stored like it might be in LGA01 or LGA02 or LGA03 or LGA04. Here my question is, are we going to check 40 time IF condition for each field (LGA01 to LGA40). My answer is No. We have syntax in ABAP by using that we can achieve out target very easily.

Before going forward if you are new to ABAP HR, please go through the below Link:

SAP ABAP HR Program code using LDB PNP

The following Report shows you how to access these data fields. The example determines the wage type and its amount for particular period.

Data declarations: The required data declarations are first made at the beginning of the
Report. Fields LGART and BETRG are required to read the repetitive structures.

Tables: PERNR is used to get the standard selection screen as well work area.
Declare Tables: PERNR and press F8 you will get standard selection screen.

Infotypes: when we declare tables at the runtime of program will have work area the same way, when we declare Infotypes, will have internal table (we call as internal Infotype) with header with the structure of associated Infotype.

Macros:
You often only require the most recent or earliest Infotype record, not all Infotype records. In this case, use one of the following statements:

RP_PROVIDE_FROM_LAST Pnnnn SPACE PN-BEGDA PN-ENDDA.

These statements make the most recent or earliest record in the PN/BEGDA to PN/ENDDA data selection period available in the structure Pnnnn for infotype nnnn.
If the infotype has subtypes, replace the SPACE parameter by the appropriate subtype number.
When a record has been successfully read, the return code PNP-SW-FOUND = 1 is returned.

SAP ABAP HR Program code using LDB PNP

admin — Sun, 14 Feb 2010 09:44:21 +0000

Here is a basic abap hr program with screen shots step by step for learners who are having knowledge of abap. This is a basic program but you can use this template for every abap hr program and add if and else conditions change the Infotype numbers and field names based on your requirement.

Initially I don’t want to confuse the readers adding more coding at first program. All the scenarios are covered in next posts one by one by using the same program template.

Requirement: Select the data from Infotypes using logical database PNP (with out single select statement) and display in report. Fields like

Personnel number, Action Type, Reason for Action, Payroll area, Personnel ID Number

Infotypes Used: 0000, 0001, 0002.

Macros used:

RP-PROVIDE-FROM-LAST P0000 SPACE PN-BEGDA PN-ENDDA.

RP-PROVIDE-FROM-LAST P0001 SPACE PN-BEGDA PN-ENDDA.

RP-PROVIDE-FROM-LAST P0002 SPACE PN-BEGDA PN-ENDDA.

Selection screen:

There is selection screen is defined in this program but by using logical database PNP we do get standard selection screen.

Steps:

1) Go to se38 transaction

2) Enter the program name ZABAPHROVERVIEW and press on create

3) Enter the TITLE name, select TYPE as executable program, and LOGICAL DATA BASE AS PNP.

4) Press on save button.

And use the below code and execute you will get standard selection screen.

Standard selection screen:

Enter the personnel number and execute the program report display is ready for you…:)

Don’t you feel abap hr is easy….

Incase any question use the below comments section…..

SAP HR ABAP Interview Faq’s

admin — Mon, 14 Sep 2009 04:43:31 +0000

1) What is the difference between ABAP and HR ABAP
2) What is logical data base
3) What are logical data bases used in hr module
4) What is the difference between PNP and PNPCE
5) Explain GET PERNR concept when we use logical data base
6) Explain the program flow when we use logical database PNP or PNPCE
7) What are the program names for logical database PNP and PNPCE
8 ) What is report category and for what purpose do we use report category
9) What is Infotype and how it is different from tables
10) Why do we require Infotypes for HR module
11) What are the transaction codes to create the Infotypes
12) What is the process to enhance the Infotype
13) Importance of PA20, PA30 and PA40
14) How can we decide weather we can enhance the standard Infotype or not
15) What is PAKEY structure, PSHD1 structure and what type of fields it contains
16) What is PS structure
17) What are the payroll related Infotypes
18) What are the time related Infotypes
19) What are the personnel administration related Infotypes
20) What are the organizational related Infotypes
21) What is Macro
22) What are the standard macros do we use in HR ABAP
23) What is PNP-SW-FOUND
24) What is the difference between select statement and provide statement
25) Which function module reads the data for particular Infotype
26) What is repetitive structure and for which Infotype do we have
27) How do you retrieve the data for repetitive structures
28) Can we develop program without logical database for hr module data retrieval
29) By using which FM we can upload data into Infotype
30) If yes then why do we require logical database

31) What are advantages and disadvantages of logical data base
32) What is the transaction code to display the payroll results
33) What is payroll driver
34) Where the payroll results are stored
35) Explain the concept of clusters in payroll
36) How do you read the data from clusters
37) What is retro active accounting
38) In which cluster time results are stored
39) What is wage type
40) What is personnel area
41) What is personnel sub are
42) What is payroll area
43) What is the difference between semi-monthly and Bi-weekly payroll area
44) What is sequence number
45) What is For-period and In-period
46) What is off cycle payroll run
47) How do you execute the payroll
48) What is schema and transaction code
49) What is functions and transaction code
50) What is features and transaction code
51) What is the transaction code to modify the hr form
52) What are the FM do we use in OM
53) What is object in OM
54) Which FM do you use to find out who is reporting to whom
55) What all are the differences did you find in hr module between 4.7 and ECC6 versions

Please use below comments section to add more questions or answer the above questions. It would be appreciated if you answer the above questions, mention your name and company working for.

If you are interested to post your article as a different topic, feel free to reach me at abaphr.com@gmail.com or admin@abaphr.com.

Personnel Administration (PA):

admin — Mon, 26 Jan 2009 17:48:44 +0000

PA involves administrating employee data, commonly referred to Master Data. Master Data contains all employee data used in HR processing. Master Data includes Personal (Eg. address), Organizational (Position description), Benefits (Insurance, Pension), Time & Payroll.
Master Data is stored in Infotypes. Infotypes are tables (for user Data entry screen) that contain logically related employee data. Data can be stored for specific periods, which includes current and historical.

Components of PA:

• Personnel Area: represents a division of a company code into subunits. It is an organizational entity representing an area within an organization defined by specific aspects of personnel administration, time management and payroll. Personnel areas are subdivided into personnel subareas. Personnel area is specific to HR and is a four character alphanumeric identification. Eg. Personnel area 100 is for employees in Karnataka, 200 is for Chennai.

• Personnel Subarea: is a further subdivision of Personnel area. It may represent geographical locations. Functions include:
1. Set groupings for Time Management, so that work schedules, substitution and absence and leave types can be setup for individual personnel subareas.
2. Generate default pay scale type and area for an employee’s basic pay.
3. Define public holiday calendar.

• Employee Groups: divides or groups employees into various categories. Eg. Active employees, Retired employees, Contractors. Employee groups are used to generate default values for payroll accounting area and basic pay.

• Employee Subgroups: are further differentiated within the employee group. Eg. Salaried employees, Hourly employees, Unionized employees, Executives. The employee subgroup grouping for the payroll rule allows you to define different payroll procedures for different employee subgroups. For eg. you can specify whether an employee’s pay should be determined on hourly or monthly basis. The employee subgroup grouping for the work schedule defines the validity of work schedule, and the attendance or absence quota type determines the validity of time quotas.

Introduction on SAP HR module

admin — Mon, 26 Jan 2009 17:41:33 +0000

The SAP HR module enables companies to effectively manage information about the people in their organization. It is integrated with other SAP modules and external systems. From the Organization Management perspective, companies can model a business hierarchy, the relationships of employees to various business units and the reporting structure among employees. The Personnel Administration (PA) sub module helps employers to track employee master data, work schedules, salary and benefits information. The Personnel Development (PD) functionality focuses on employees’ skills, qualifications and career plans. Finally, the Time Evaluation and Payroll sub modules process attendance and absences, gross salary and tax calculations, and payments to employees and third party vendors.

What is HR?

The task of Human Resource Management is to produce the organizational hierarchies, relationship between employees and to allow storage and administration of employee data.

Organization:

We can define an organization as an individual enterprise(company or industry) in which someone is leading it and with some departments like HR, Marketing, Finance, R&D etc.
For any organization employees are the most powerful resource. So to maintain the employee related data we require one system which ensures accuracy and consistent within the organization.

We are going to discuss the following areas in HR.

1) Personnel Administration
2) Personnel Development
3) Time Management
4) Payroll

Useful Transaction codes in SAP HR module

admin — Sun, 18 Jan 2009 18:36:40 +0000

Master Data

PA10   Personnel File
PA20   Display HR Master Data
PA30   Maintain HR Master Data
PA40   Personnel Events
PA41   Change Hiring Data
PA42   Fast Data Entry for Events
PRMD   Maintain HR Master Data
PRMF   Travel Expenses: Feature TRVFD
PRML   Set Country Grouping via Popup
PRMM   Personnel Events
PRMO   Travel Expenses: Feature TRVCO
PRMP   Travel Expenses: Feature TRVPA
PRMS   Display HR Master Data
PRMT   Update Matchcode
PSO3   Infotype overview
PSO4   Individual maintenance of infotypes

Time Management

PA51   Display Time Data
PA53   Display Time Data
PA61   Maintain Time Data
PA62   List Entry of Additional Data
PA63   Maintain Time Data
PA64   Calendar Entry
PA70   Fast Data Entry
PA71   Fast Entry of Time Data
PBAB   Maintain vacancy assignments
PT01   Create Work Schedule
PT02   Change Work Schedule
PT03   Display Work Schedules

Payroll

PC00   Run Payroll
PC10   Payroll menu USA
PE00   Starts Transactions PE01,PE02,PE03
PE01   Schemas
PE02   Calculation Rules
PE03   Features
PE04   Create functions and operations
PE51   HR form editor
PRCA   Payroll calendar
PRCT   Current Settings
PRCU   Printing Checks USA
PRD1   Create DME
SM31   Maintain Tables
SM12   Locked Secessions
TSTC   Table lookup
SPR0   IMG
SE16   Data Browser (Table reports)
PP03   PD Tables
PP0M   Change Org Unit
P013   Maintain Positions
PO03   Maintain Jobs

Benefits

PA85   Benefits – Call RPLBEN11
PA86   Benefits – Call RPLBEN07
PA87   Benefits – Call RPLBEN09
PA89   COBRA Administration
PA90   Benefits Enrollment – Individual
PA91   Benefits – Forms
PA92   Benefits Tables – Maintain
PA93   Benefits Tables – Display
PA94   Benefits – Access Reporting Tree
PA95   Benefits IMG – Jump to Views
PA96   Benefits reporting
PA97   Salary Administration – Matrix
PA98   Salary Administration
PA99   Compensation Admin. – rel.changes
PACP   HR-CH: Pension fund, interface

Payroll

Benefits

General/Reporting

PM00   Menu for HR Reports
PM01   Dialogs in HR - Create custom infotypes
PRF0   Standard Form
PSVT   Dynamic Tools Menu
PAR1   Flexible employee data
PAR2   Employee list

PD – Organizational Management

PP0M   Change Org Unit
PO03   Maintain Jobs
PO13   Maintain Position
PO10   Maintain Organizational Unit
PP01   Maintain Plan Data (menu-guided)
PP02   Maintain Plan Data (Open)
PP03   Maintain Plan Data (event-guided)
PP05   Number Ranges
PP06   Number Range Maintenance: HRADATA
PP07   Tasks/Descriptions
PP69   Choose Text for Organizational Unit
PP90   Set Up Organization
PPO1   Change Cost Center Assignment
PPO2   Display Cost Center Assignment
PPO3   Change Reporting Structure
PPO4   Display Reporting Structure
PPO5   Change Object Indicators (O/S)
PPO6   Change Object Indicators O/S
PPOA   Display Menu Interface (with dyn.)
PPOC   Create Organizational Unit
PPOM   Maintain Organizational Plan
PPOS   Display Organizational Plan
PQ01   Events for Work Center
PQ02   Events for Training Program
PQ03   Events for Job
PQ04   Events for Business Event Type
PQ06   Location Events
PQ07   Resource Events
PQ08   Events for External Person
PQ09   Events for Business Event Group
PQ10   Events for Organizational Unit
PQ11   Events for Qualification
PQ12   Resource Type Events
PQ13   Events for Position
PQ14   Events for Task
PQ15   Events for Company
PSO5   PD: Administration Tools
PSOA   Work Center Reporting
PSOC   Job Reporting
PSOG   OrgManagement General Reporting
PSOI   Tools Integration PA-PD
PSOO   Organizational Unit Reporting
PSOS   Position Reporting
PSOT   Task Reporting

Recruitment

PB10   Init.entry of applicant master data
PB20   Display applicant master data
PB30   Maintain applicant master data
PB40   Applicant events
PB50   Display applicant actions
PB60   Maintain applicant actions
PB80   Evaluate vacancies
PBA0   Evaluate advertisements
PBA1   Applicant index
PBA2   List of applications
PBA3   Applicant vacancy assignment list
PBA4   Receipt of application

Macros in HR-ABAP programming

admin — Mon, 22 Dec 2008 13:51:25 +0000

Most commonly used Macros in ABAP-HR ?

Macro contains some part of source code which it will be useful for number of applications.( Like function modules )

Generally we use two macros in ABAP-HR or SAP-HR
RP-PROVIDE-FROM-LAST
RP-PROVIDE-FROM-FRST

Ex:
RP-PROVIDE-FROM-LAST P0000 SPACE PN-BEGDA PN-ENDDA.
IF PN-SW-FOUND = 1.
WRITE YOUR CONDITION.
ENDIF.

The macro RP-PROVIDE-FROM-LAST retrieves the last(latest) data record which is valid in the data selection period.
The macro RP-PROVIDE-FROM-FRST retrieves the first(start)data record which is valid in the data selection period.

For every macro, whether the operation was successful or not will be checked with PNP-SW-FOUND.
If PNP-SW-FOUND = 1 , then the operation is successful. ( same as sy-subrc but the value is in reverse case)

The macro RP-READ-INFOTYPE retrieves all the data record(s) which is valid in the data selection period.

If SY-SUBRC = 0 , then the process is successful.

All the Macros are stored in table TRMAC

Whenever you are using the macros like

RP-PROVIDE-FROM-LAST or
RP-PROVIDE-FROM-FRST,

check whether you have included logical database PNP in program attributes.

It is not necessary to include logical database PNP/PNPCE in your program when you are using the macro like

RP-READ-INFOTYPE A B C D E , where

A corresponds to PERNR which describes for which personnel number you require records.

B corresponds to INFOTYPE which describes from which infotype you require records.

C corresponds to data structure of the declared infotype (internal table like P0000 for infotype 0000) where all the records of the particular personnel number will be stored.

D corresponds to Start date.

E corresponds to End date.

What is Logical Database ?

admin — Tue, 16 Dec 2008 14:17:25 +0000

Logical database in SAP
The LDB is special type of ABAP program that combines the contents of certain related database tables and retrieve some related data and make it available to application programs.

In other words, a LDB is a method by which ABAP programs read and process the data. The sequence in which the data is supplied to the program is determined by a tree structure.

The LDB usually consists of the following components:

Structure
Selections
Database programs

Logical databases have a tree structure.A logical database can contain a maximum of 300 tables

SAPDBPNP is the name of the database program for the logical database PNP.

How are logical database used

1.Logical databases when generating an ABAP program

The selection screen generated contains the selections (SELECT-OPTIONS AND PARAMETERS) of both the logical database and the program.

The only database-specific selections displayed on the selection screen are those needed by the program for data retrieval purposes

2. Logical databases at run-time of an ABAP program

At run-time, the system processes the events in the program and in the logical database in the following order

Before displaying the selection screen, certain initializations (e.g. calculating default values such as key date, etc.) are performed for the selection screen by the logical database and the program.
The selection screen is displayed and the user enters data in the input fields.

The logical database and the program check that the input is correct and complete , but also that the user has the appropriate authorizations. If an error occurs, some fields are made ready for input again, so that the user can make the necessary correction(s).

In the event START-OF-SELECTION, the ABAP program performs any preliminary work (for ex, importing files).

The logical database reads the selected data and the program processes it within the GET events according to the sequence specified by the structure.

In the event END-OF-SELECTION, the ABAP program performs any concluding operations (for example, calculating totals, exporting files).

3 . Designing the selection screens
The standard selection screen of a logical database has a standard layout where SELECT-OPTIONS and PARAMETERS appear in the sequence they are declared, each on a new line. The system automatically generates such a screen for each program that does not have its own selection screen entered in the attributes.
You can define your own selection screens for any logical database . If the attributes of a program include the number of its own selection screen, the system uses this screen as a model when generating. Any program-specific selections appear after the database selections. The flow logic for such screens is also generated automatically and therefore cannot be modified. You cannot delete database selections

Functions of LDB:

Data retrieval :

The personnel data of each employee is loaded into the main memory where it can be accessed for processing.

Screening :

Employees can be selected according to the organizational criteria entered on the selection screen.

E.g…Hourly wage earners in a particular personnel sub area.
There are two types of screening..Person selection and data selection period.

Person selection defines those employees for whom a report is to be run.

E.g..Monthly wage earners in a specific personnel sub-area.
E.g..Personnel number range
E.g..Features of org.Assignment…Employees who assigned to certain cost center.
E.g..Employee status..Active or inactive.

The data selection period delimits the time period for which data is evaluated.
When you enter the data selection period,the provide loop retrieves the infotype records whose validity period overlaps with at least one day of this period.

Authorization check:

This ensures that the person starting the evaluation Is authorized to access the report data.

Lagical Data bases in HR ABAP:

PNP
PNPCE
PAP
PCH

Infotype 402 and Payroll results

hivamsi — Mon, 24 Nov 2008 08:56:16 +0000

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.

Difference between ABAP and HR ABAP

admin — Thu, 20 Nov 2008 12:23:22 +0000

ABAP vs HR ABAP

The following concepts are defined in ABAP HR which is different with other modules.

1) Use of Infotypes

2) The use of Logical Database

3) Use of Macros and Provide statement

4) Storage and Access of data

5) Authorization checks

There is nothing much difference between abap and hr abap. The way we retrieve the data from data base is deferent.

In general ABAP data is stored in Tables, but coming to HR ABAP employee data is sorted through Infotypes. The way we retrieve the data from infotypes is deferent in hr abap.

In general ABAP we use Logical data base very rare, as in HR ABAP most of the programs use Logical data base to select data from Infotypes by using Get event.

In ABAP we use read statement to read particular record, still in HR ABAP we do use read statement apart from that we have Macros and provide statement.

Macro is pre defined code (like function module) which reads data from internal table (internal infotype) based on dates.

Provide statement is like Select statement but selects data from internal table

Storage and access of data in hr abap is completely deferent in hr abap comparing with ABAP. We use transaction code PA20 and PA30 to maintain data in infotypes.

PA20 is display mode and PA30 is change mode. We can create, change, display, copy, and delete in infotypes with PA30 transaction.

For Infotypes authorizations can be maintained infotype and subtype (field) level as HR data is more sensitive and secrete.

Will discuss in detail of above bullet points as a separately.

More information on sap hr-abap infotypes

admin — Tue, 11 Nov 2008 08:13:40 +0000

More information on SAP hr abap infotypes:

Infotype data is period-based (time-dependent), in other words, it is only valid for specific periods. For this reason, each record has a start date and an end date.

The database does not normally contain only one record for each infotype and personnel number but several records with different validity periods.

E.g. 0001 – Org Assignment
0000 – Actions

Sap hr Infotype ranges:

0000 to 0999 – HR Master data / Applicant data (PA)

1000 to 1999 – Organizational Management (OM)

2000 to 2999 – Time data (TM)

4000 to 4999 – Applicant data

9000 to 9999 – Customer defined

Most commonly used infotypes in SAP HR:

0000 Actions

0001 Org. Assignment

0002 Personal Data

0003 Payroll Status

0006 Addresses

0007 Planned Working Time

0008 Basic Pay

0009 Bank Details

0014 Recur. Payments/Deds.

0015 Additional Payments

0021 Family details

0022 Education details

0041 Date Specifications

0167 Health Plans

0168 Insurance Plans

0169 Savings Plan

0170 Flexible Spending Account

0171 Gen. Benefits Information

0221 Manual Checks

0267 One time Payment off-cycle

2001 HR Time Record: Infotype 2001 (Absences)

2002 HR Time Record: Infotype 2002 (Attendances)

2006 HR Time Record: Infotype 2006 (Absence Quotas)

2005 HR Time Record: Infotype 2005 (Overtime)

2007 HR Time Record: Infotype 2007 (Attendance Quotas)

ABAP vs HR-ABAP

admin — Mon, 10 Nov 2008 15:08:26 +0000

What is the difference between abap and abap hr?

The following concepts are defined in ABAP HR which is different with other modules .

n Use of Infotypes

n The use of Logical Database

n Use of Macros and Provide statement

n Storage and Access of data

n Authorization checks

Infotype concept in sap hr, Creation of infotype, Enhancement of infotype

admin — Thu, 06 Nov 2008 16:28:35 +0000

What is Infotype?

Infotypes are information units through which we can enter the data into tables. The Infotypes are used to group related data fields together. In general words its data entry screen from where we can store the data into tables. Naming conversion of infotype is four digits numerical. Each infotype will have corresponding data base table to it.

For example

Infotype 0006 is Address

The data stored for this infotype in table PA0006.

We can view the infotype data in two ways using below transactions:

1)Go to transaction code SE11 and enter the PA0006 and display or

2)Go to transaction code PA20 and enter the employee number (ex 1000) and infotype number (0006) for address details and click on overview.

Changing the infotype data: If you want to change or create the infotype data for example 00006.

1)Go to transaction code PA30 and enter the employee number (example 1000) and infotype number (0006) for address details and click on create or change based on your requirement.

2)After creating of changing of infotype data click on over view to view all the records related to that particular employee.

The difference between the PA20 and PA30 transaction are display mode and change mode respectively.

Why Infotype?

As HR is related to time, we require old data as well as new data. The data we enter into the infotypes are automatically checked for accuracy and against the table entries.

In simple, HR data is huge and to access data easily we require Infotype.

For more information click on the link: hr_abap_training Consist of fallowing details.

Brief description of modules in SAP-HR

Concept of Infotypes

Infotype Structures

Creation of infotype

Enhancement of infotype

HR Macros

Use of Provide statement

Cluster reading for Payroll results

have a look at material page for more information

Useful function modules in ABAP-HR

admin — Mon, 03 Nov 2008 15:01:45 +0000

RS_PROGRAM_CHECK_NAME: To check program names if you are generating them.

RS_CORR_INSERT : To insert the correction request in the repository.

REPS_OBJECT_ACTIVATE: To activate repository objects, for example – to activate a newly generated program.

RS_DELETE_PROGRAM: To delete the program.

RS_ACCESS_PERMISSION: To lock or unlock a program.

Function Modules related to Date and Time Calculations

CALCULATE_DATE: Calculates the future date based on the input .

DATE_TO_DAY: Returns the Day for the entered date.

DATE_COMPUTE_DAY: Returns weekday for a date

DATE_GET_WEEK: Returns week for a date

RP_CALC_DATE_IN_INTERVAL: Add days / months to a date

Function Modules related to (ALV) ADVANCED LIST VIEWER

REUSE_ALV_LIST_DISPLAY: ABAP List viewer (LIST DISPLAY)

REUSE_ALV_GRID_DISPLAY: ALV GridControl full screen

REUSE_ALV_FIELDCATALOG_MERGE: Create field catalog from dictionary structure or internal table

Function Module related to Change Tracking

CHANGEDOCUMENT_READ_HEADERS: Read and format change documents

DAY_ATTRIBUTES_GET: Returns attributes for a range of dates specified

MONTHS_BETWEEN_TWO_DATES: To get the number of months between the two dates.

END_OF_MONTH_DETERMINE_2: Determines the End of a Month.

HR_HK_DIFF_BT_2_DATES: Find the difference between two dates in years, months and days.

FIMA_DAYS_AND_MONTHS_AND_YEARS: Find the difference between two dates in years, months and days.

MONTH_NAMES_GET: Get the names of the month

IDWT_READ_MONTH_TEXT: Get the MONTH TextWEEK_GET_FIRST_DAY : Get the first day of the week

HRGPBS_HESA_DATE_FORMAT: Format the date in dd/mm/yyyy format

SD_CALC_DURATION_FROM_DATETIME: Find the difference between two date/time and report the difference in hours

L_MC_TIME_DIFFERENCE: Find the time difference between two date/time

HR_99S_INTERVAL_BETWEEN_DATES: Difference between two dates in days, weeks, months

LAST_DAY_OF_MONTHS: Returns the last day of the month

DATE_CHECK_PLAUSIBILITY: Check for the invalid date.

DATE_2D_TO_4D_CONVERSION: Year entry: 2-character to 4-character.

DAY_IN_WEEK: Input date and will give the name of the day 1-monday,2-Tuesday….

SD_DATETIME_DIFFERENCE: Give the difference in Days and Time for 2 dates

Function Modules Related To Formatting

CLOI_PUT_SIGN_IN_FRONT: Displays the negative sign in front of the numeral.

RKD_WORD_WRAP: Wrap text into several lines

CONVERSION_EXIT_ALPHA_INPUT: Pad zeros to the number at the left

CONVERSION_EXIT_ALPHA_OUTPUT: Eliminate zeros to the number at the left

READ_EXCHANGE_RATE: Exchange Conversion

SPELL_AMOUNT: Transforms numeric values into text

Function Modules Related To Dialog Prompts

POPUP_TO_CONFIRM: Displays a popup dialog with a user defined message for confirmation

POPUP_TO_GET_VALUE: Displays a popup dialog requesting a value for a particular table-fieldname

SAPGUI_PROGRESS_INDICATOR: Displays a progress bar with text to denote the percentage of completion and status

FILENAME_GET: Displays a popup dialog to get the presentation server filename

F4_DATE: Displays a popup dialog to choose date

POPUP_TO_SELECT_MONTH: Display a pop-up to select a month

GET_PRINT_PARAMETERS: Printer parameters

Function modules related to RFC communication

RFC_CONNECTION_CLOSE: Close a RFC connection

RFC_GET_SYSTEM_INFO : Give system’s information of a remote system

Function modules related to reading/writing files

FILE_READ_AND_CONVERT_SAP_DATA: Uploads the file from either presentation or application server into an internal table

SUBST_GET_FILE_LIST: To get the list of files from Application Server.

ALSM_EXCEL_TO_INTERNAL_TABLE: Legacy Data Transfer w/ Excel

WS_FILE_DELETE: Delete files on UNIX server

PFL_COPY_OS_FILE: Copy UNIX files

EPS_GET_DIRECTORY_LISTING: Returns all files from a Server directory

Function Modules related to sending emails

SO_NEW_DOCUMENT_ATT_SEND_API1 – Sends emails with texts and attachments
SO_NEW_DOCUMENT_SEND_API1 – Sends emails with texts.

Function Modules related to F4 Help

F4IF_INT_TABLE_VALUE_REQUEST – F4 help also returning the value to be displayed in internal table

Function Modules related to data maintenance

VIEW_MAINTENANCE_CALL – To maintain data from a table

Function Modules related to FI, CO and SD Modules

FOR_ALL_SKC1A : Account subtotal

VC_I_GET_CONFIGURATION : Sales Purchase details configuration

SD_PRINT_TERMS_OF_PAYMENT : Print terms for unique payment

SD_PRINT_TERMS_OF_PAYMENT_SPLI : Print terms for some parcels payment

J_1B_NF_DOCUMENT_READ : Read NF details

J_1B_NF_VALUE_DETERMINATION : Read values from NF returned combined with J_1B_NF_DOCUMENT_READ using.

SAP HR ABAP, HCM Training Material and Tutorials » ABAP HR

Creation of Custom Infotype in HR ABAP

Maintenance permitted after leaving:

Indicator for entry of additional data:

Indicator: Text allowed for Infotype:

Indicator for access authorization (from/to date):

Reaction to: 1st date entered:

Reaction to: 1st and 2nd dates entered:

Reaction to: No delimitation:

Sort sequence of records:

Key for screen header layout

Indicator specifying when data is chosen for the IT header:

Use

Dependencies

Example

Retroactive accounting relevance for payroll

Example

Reaction to Entry in Payroll Past

Most Commented Posts

Evaluating Repetitive Structures in HR ABAP Programming

Related Posts

SAP ABAP HR Program code using LDB PNP

Related Posts

SAP HR ABAP Interview Faq’s

Related Posts

Personnel Administration (PA):

Related Posts

Introduction on SAP HR module

Related Posts

Useful Transaction codes in SAP HR module

Related Posts

Macros in HR-ABAP programming

Related Posts

What is Logical Database ?

Related Posts

Infotype 402 and Payroll results

Related Posts

Difference between ABAP and HR ABAP

Related Posts

More information on sap hr-abap infotypes

Related Posts

ABAP vs HR-ABAP

Related Posts

Infotype concept in sap hr, Creation of infotype, Enhancement of infotype

Related Posts

Useful function modules in ABAP-HR

Related Posts