sap hr abap

IBM Global Business Services

HR ABAP Jan-2007 © 2007 IBM Corporation

HR ABAP Technical Overview


© 2007 IBM Corporation2 Jan-2007HR ABAP

List of Topics

Logical DatabasesJoin & ProjectionReports / Repetitive StructuresClustersTime Data Infosets & Infoset Queries InfotypesLogical Database PCH



Logical Databases



What is a Logical Database ?

Logical databases are special ABAP programs that retrieve data and make it available to application programs. The most common use of logical databases is still to read data from database tables and linking them to executable ABAP programs while setting the program contents

Logical databases contain Open SQL statements that read data from the database. You do not therefore need to use SQL in your own programs

A logical database can read the lines of these tables one after the other into an executable program in a sequence which is normally defined by the hierarchical structure



Functions of the Logical Database PNP



Logical Databases provided by SAP

HR Logical Databases In Human Resources (HR), the following logical databases can be used as a data source for HR InfoSets:

PNP / PNPCE PAP PCH By selecting a logical database, you determine the HR data that can be reported on

using an InfoSet. Logical Database PCH This logical database generally enables you to report on all HR infotypes. However,

you are advised not to use this logical database unless you want to report on Personnel Planning data.

Logical Database PNP Use logical database PNP to report on HR master data. It is possible to use logical

database PCH to access this data, but PNP meets such reporting requirements more quickly because it is best suited to the task of selecting persons.



Structure of Logical Database

StructureThe structure defines the data view of the logical database.

SelectionsThe selections define a selection screen, which forms the user interface of the executable programs that use the logical database.

Database ProgramThe database program contains the ABAP statements used to read the data and pass it to the user of the logical database.



Structure of Logical Database

The structure of a logical database is usually based on the foreign key relationships between hierarchical tables in the SAP System.

Logical databases have a tree-like structure

The nodes must be structures defined in the ABAP Dictionary or data types from a type group



Linking a Logical Database to an Executable Program



Logical Structures and DB Tables in PA

SAP AG 1999

Logical Structures and Database Tables in PA

Logical structures

PnnnnKEY fields

Data fields

PSnnnn

Database tables

PAnnnnPAnnnn PBnnnnPBnnnnScreenfields

Qnnnn

Selectionfields PNP

PERNR

PCLnPCLn



LDB : Infotype Data Structure

SAP AG 1999

Infotype - Data Structures

PA0002PA0002

DB structure PAnnnn using infotype 0002 as an example

Infotype structure Pnnnn using infotype 0002 as an example

MANDT PAKEY PSHD1 PS0002

PSKEY PSHD1 PS0002



LDB - Screening



LDB – Data Retrieval



Calling a Logical Database Using a Function Module

LDB_PROCESS Function module is used to call logical databases independently from any ABAP program

Selection screen is not displayed The logical database does not trigger any GET events in the calling program, but

passes the data back to the caller in callback routines The depth to which the logical database is read is determined by specifying a

node name in the CALLBACK parameter For the GET event, the callback routine is executed directly after the data has

been read for the node, and before the subordinate nodes are processed. For the GET LATE event, the callback routine is processed after the subordinate

nodes have been processed.



Processing Infotypes in Logical Database



LDB – Processing Master Data Using Provide

SAP AG 1999

Processing Master Data

TABLES: PERNR.INFOTYPES: 0001, "Actions

0002, "Personal Data0006, "Addresses....

GET PERNR.PROVIDE * FROM P0002 BETWEEN PN-BEGDA AND PN-ENDDA.

WRITE...

ENDPROVIDE.



LDB - Loop Nesting

SAP AG 1999

Loop Nesting

GET PERNR.PROVIDE * FROM P0002 BETWEEN PN-BEGDA

AND PN-ENDDA.WRITE...

ENDPROVIDE.

PROVIDE * FROM P0006BETWEEN PN-BEGDA AND PN-ENDDA.WRITE...

ENDPROVIDE.

END-OF-SELECTION.

Infotypeloop

Infotypeloop

Employeeloop



LDB – Period Based Data - 1

SAP AG 1999

JANUARY - APRIL

MAY - AUGUST

SEPTEMBER - DECEMBER

Ms YMs Y

Period-Based Data (1)



LDB – Period Based Data - 2

SAP AG 1999

Org.Assignment

Data Selection

January December

January December

Org.Assignment

January December

Period-Based Data (2)



LDB – Screening Criteria

SAP AG 1999

Screening Criteria

Data selection

Person selection

PAnnnnPAnnnn

INFOTYPES: ...

GET PERNR.

PROVIDE...

WRITE...



LDB – Sort Order

SAP AG 1999

Sort Order

...

GET PERNR....

190919101899

Pers.areaPerNo. Name

100010001100

Sam Hawkins David Lindsay Karl May



LDB – Flow Control of Logical Database

SAP AG 1999

Flow Control for Logical Database

View of HR report attributes - flow control for logical database

Program Batch Online

ZPLIST00

ZPLIST10

1

2

1

2

1

2

3

Forward select options

Array fetch is active

Array fetch active and forward select options



Join and Projection



Joins and Projection



Joins in PROVIDE



Join / Subtypes

SAP AG 1999

Join / Subtypes

TABLES: PERNR.INFOTYPES: 0001, "Organizational Assignment


GET PERNR.PROVIDE * FROM P0002

* FROM P0006 BETWEEN PN-BEGDA AND PN-ENDDA

WHERE P0006-SUBTY = '1'.IF P0006_VALID = 'X'.

WRITE...ENDIF.

ENDPROVIDE.



Joins and Projection / Coding



Reading Time-Dependent Table Entries

SAP AG 1999

Reading Time-Dependent Table Entries

BEGDA

P0001-BEGDA

T513SENDDA

SELECT * FROM T513SWHERE SPRSL = SY-LANGUAND STELL = P0001-STELLAND ENDDA GE P0001-BEGDAAND BEGDA LE P0001-BEGDA.

ENDSELECT.



HR Macros

RP_PROVIDE_FROM_LAST

RP_PROVIDE_FROM_FIRST

RP_SET_DATA_INTERVAL

RP_READ_INFOTYPE

RP-READ-ALL-TIME-ITY



Options for Defining Modules

Macros can be defined in reports or includes using the ABAP command DEFINE

If a macro is changed, each report using this macro is automatically regenerated when it is executed

Macros can also be defined as RMAC macros. The source code of these modules is stored in the function section of the control table TRMAC

When you change an RMAC macro in the table TRMAC, the reports that use this macro are not regenerated automatically. You must regenerate them manually.



Macro Modules

SAP AG 1999

Macro Modules

TABLES: PERNR.INFOTYPES: 0001, "Organizational Assignment


GET PERNR.RP_PROVIDE_FROM_LAST P0001 SPACE PN-BEGDA PN-ENDDA.

WRITE...

* * * Include program DBPNPMAC.

DEFINE RP_PROVIDE_FROM_LAST.PNP-SW-FOUND = '0'.. . .

END-OF-DEFINITION.



Processing a Specific Infotype Record

SAP AG 1999

Processing a Specific Infotype Record

Data selection January December

TablePnnnn

January December

GET PERNR.RP_PROVIDE_FROM_LAST <Pnnnn> SPACE PN-BEGDA PN-ENDDA.IF PNP-SW-FOUND = 1.

WRITE...ENDIF.



Reading Infotype without using LDB (1)

SAP AG 1999

Reading Infotypes Without Logical DB (1)

PAnnnnPAnnnn

INFOTYPES: <nnnn>....CALL FUNCTION'HR_READ_INFOTYPE'...



Reading Infotype Without Using LDB (2)

SAP AG 1999

Reading Infotypes Without Logical DB (2)

INFOTYPES: 0002.DATA: return LIKE SY-SUBRC.

CALL FUNCTION 'HR_READ_INFOTYPE'EXPORTING. . .

PERNR = <person>INFTY = '0002'BEGDA = <begdat>ENDDA = <enddat>

IMPORTINGSUBRC = return

TABLESINFTY_TAB = P0002

EXCEPTIONSINFTY_NOT_FOUND = 1OTHERS = 2.



Updating Infotype Record

SAP AG 1999

Updating Infotype Records

PARAMETERS:persnum LIKE P0002-PERNR, natio_o LIKE P0002-NATIO DEFAULT 'DE',natio_n LIKE P0002-NATIO DEFAULT 'D'.

* Update infotype records

UPDATE PA0002SET NATIO = natio_nWHERE PERNR = persnumAND NATIO = natio_o.

IF SY-SUBRC = 0.WRITE: 'Modified records', SY-DBCNT.

ENDIF.



Reading Planning Infotypes with Function Module



Determining The Entry Date



Dynamic Actions



Indicator for Step

P Check conditions I Maintain infotype record W Set default values when creating a new record V Reference to another step F Call routine M Send mail

Tables used PSAVE To check old values of field PSPAR Transaction classes T001P Start dates and molga



Function character of step

02 for Change

04 for Create

06 for Change and create

08 for Delete

10 for Change and delete

12 for Create and delete



Calling Reports Using Dynamic Actions



Reports / Repetitive Structures



Infotype with repetitive Structure



Repetitive Structure / Evaluation (1)



Repetitive Structure / Evaluation (2)



ALV Data Structures

SAP AG 1999

ALV Data Structures

. . .TYPE-POOLS: SLIS.. . .DATA: alv_fieldcat TYPE slis_t_fieldcat_alv,

alv_layout TYPE slis_layout_alv.. . .

TYPES: BEGIN OF data_struc,pernr LIKE PERNR-PERNR,ename LIKE P0001-ENAME,. . .dar LIKE P0041-DAR01,. . .

END OF data_struc.

DATA: data_tab TYPE TABLE OF data_struc,data_tab_wa TYPE data_struc.



ALV Field Catalog



AVL Interface



Clusters



Clusters

Definition It is a database object, It is a file or table which link with Relid It combines the data from several tables with identical keys.



Clusters

Different Types Of Clusters PCL1 : Database for HR – Work Area PCL2 : Accounting Results ( Time / Payroll Results ) PCL3 : Recruitment/Applicant Tracking Data PCL4 : Documents Data PCL5 : Personnel Cost Planning



Clusters

PCL2 – Accounting Results table PCL2 is a Transparent table. PCL2-relid then it is called Cluster. PCL2- (XX) Where XX : - IN – India RX- International RU- USA FI- Finland RQ- Australia



Importing Data



Importing / Exporting with Macros



Importing/Exporting using a Buffer

SAP AG 1999

Importing/Exporting Using a Buffer

Import

Export

Program

UPDATE

PCLnPCLn

Buffer



Importing Using a Buffer



Data flow in Payroll



Payroll Results

SAP AG 1999

Payroll Results

Payroll result

Suzanne Werner January 19xx

WT01 Standard salary 5000 DMWT02 Bonus 300 DMWT03 Overtime 200 DM/101 Tot. gross amt 5500 DM. . . .

REPORT RPCLSTxy.



Reading the Cluster Directory

SAP AG 1999

Reading the Cluster Directory

*Table containing directory of payroll resultsDATA: BEGIN OF RGDIR OCCURS 100. INCLUDE STRUCTURE PC261. DATA: END OF RGDIR. DATA: COUNTRY LIKE T001P-MOLGA.... CALL FUNCTION 'CU_READ_RGDIR' EXPORTING PERSNR = PERNR-PERNR

IMPORTING MOLGA = country TABLES IN_RGDIR = RGDIR EXCEPTIONS NO_RECORD_FOUND = 1 OTHERS = 2.



Determining Current Payroll Result (1)

SAP AG 1999


DATA: number LIKE PC261-SEQNR.. . .GET PERNR.

. . .CALL FUNCTION 'CU_READ_RGDIR'. . .

CALL FUNCTION 'CD_READ_LAST' EXPORTING BEGIN_DATE = PN-BEGDA END_DATE = PN-ENDDA IMPORTING OUT_SEQNR = number TABLES RGDIR = RGDIR EXCEPTIONS NO_RECORD_FOUND = 1 OTHERS = 2.




SAP AG 1999


DATA: result TYPE PAY99_RESULT.DATA: rt_header TYPE LINE OF HRPAY99_RT. . . .

CALL FUNCTION 'PYXX_READ_PAYROLL_RESULT' EXPORTING CLUSTERID = 'RX' EMPLOYEENUMBER = p0001-pernr SEQUENCENUMBER = number * READ_ONLY_BUFFER = ' ' * READ_ONLY_INTERNATIONAL = ' ' * CHECK_READ_AUTHORITY = 'X'

. . . CHANGING PAYROLL_RESULT = result EXCEPTIONS . .LOOP AT result-INTER-RT INTO rt_header.

WRITE: / rt_header-LGART, ...ENDLOOP.



Clusters – Data Structure for Payroll Result

Structure for Payroll Results

DATA: result TYPE PAY99_RESULT . DATA: rt _ header TYPE LINE OF HRPAY99_RT . . . .

* Access to payroll result data WRITE: result -INTER-VERSC-FPPER,

. . . LOOP AT result -INTER-RT INTO rt _ header .

WRITE: / rt _ header -LGART, . . . ENDLOOP.

Structure : PAY99_RESULT

EVP Structure PC261

INTER Structure PAY99_INTERNATIONAL NAT Dummy for national part

VERSC Type PC202

RT Type HRPAY99_RT

BT CRT Type HRPAY99_CRT



Table Types for Payroll Results (1)

SAP AG 1999

Table Type for Payroll Results (1)

Payroll result

Dictionary

Table type: HRPAY99_TAB_OF_RESULTS

Aggregated data types:

Structures (field strings)

Tables

Line type: PAY99_RESULT

EVPStructure PC261

INTER Structure PAY99_INTERNATIONAL NATVERSCType PC202

RTType HRPAY99_RT

BTCRTType HRPAY99_CRT




SAP AG 1999


DATA: result_tab TYPE HRPAY99_TAB_OF_RESULTS,result_header TYPE PAY99_RESULT.

DATA: rt_header TYPE LINE OF HRPAY99_RT.DATA: rgdir LIKE PC261 OCCURS 0 WITH HEADER LINE....CALL FUNCTION 'PYXX_GET_EVALUATION_PERIODS'

EXPORTING CLUSTERID = <Cluster>

EMPLOYEENUMBER = PERNR-PERNR INPER_MODIF = <Period parameter>

INPER = <In-period>TABLES

RGDIR = rgdirEVALUATED_PERIODS = result_tab

EXCEPTIONSNO_PAYROLL_RESULTS = 1NO_ENTRY_FOUND_ON_CU = 2.




SAP AG 1999


CALL FUNCTION 'PYXX_GET_EVALUATION_PERIODS' EXPORTING . . .

IF SY-SUBRC = 0.LOOP AT result_tab INTO result_header.

WRITE: / PERNR-PERNR, P0001-ENAME,result_header-INTER-VERSC-FPPER,. . .

LOOP AT result_header-INTER-RT INTO rt_header.WRITE: / rt_header-LGART, . . .

ENDLOOP.ENDLOOP.

ENDIF.



Clusters - Display of Payroll Result(PC00_M40_CLSTR)



Clusters - Display of Cluster data – Payroll Result



Clusters - Important Structures to read Payroll data

1 . Payxx_result ( internal structures EVP/ INTER / NAT )

Where xx :- 99 = International DE = Germany IN = India FI = Finland 2. HRPAYxx_RT/ CRT/ WPBP……. Where xx :- 99 = International DE = Germany IN = India FI = Finland



Clusters - Function Modules To Read Payroll data

1. PYXX_GET_RELID_FROM_PERNR

2. CU_READ_RGDIR

3. CD_READ_LAST 4. PYXX_READ_PAYROLL_RESULT



Time Data



Time Data

SAP AG 1999

Time Data

Dependency of Time Data on Validity Period

Importing Time Data

Processing Time Data Using Internal Tables

Contents:



Time data and Validity Period

SAP AG 1999

Time Data and Validity Period

Leave

Data selectionperiod

15 days

PROVIDE...WRITE...

ENDPROVIDE. 15 days



Importing Time Data (1)

SAP AG 1999


PAnnnnPAnnnn

Data selection period

INFOTYPES: 2001, "Absences2002, "Attendances2005, "Overtime2010. "Employee

Remuneration Info GET PERNR.




SAP AG 1999


INFOTYPES: 0001,0002,...2005 MODE N.

GET PERNR.RP_PROVIDE_FROM_LAST P0001 SPACE PN-BEGDA PN-ENDDA.. . . .RP_READ_ALL_TIME_ITY PN-BEGDA PN-ENDDA.. . . .

LOOP AT P2005.WRITE...

ENDLOOP.



Importing Time Data to Internal Tables

SAP AG 1999

Importing Time Data to Internal Tables

TYPES:BEGIN OF overtime,bukrs LIKE P0001-BUKRS,werks LIKE P0001-WERKS,btrtl LIKE P0001-BTRTL,stdaz LIKE P2005-STDAZ,

END OF overtime.DATA: tab TYPE TABLE OF overtime WITH HEADER LINE.

GET PERNR.RP_PROVIDE_FROM_LAST P0001 SPACE PN-BEGDA PN-ENDDA.MOVE-CORRESPONDING P0001 TO tab.RP_READ_ALL_TIME_ITY PN-BEGDA PN-ENDDA.

LOOP AT P2005.MOVE-CORRESPONDING P2005 TO tab.COLLECT tab. (oder: APPEND tab.)

ENDLOOP. bukrs werks btrtl stdaz Work area(header line)

Data area



Processing Time Data with Internal Tables

SAP AG 1999

Processing Time Data with Internal Tables

WERKSBUKRStab - BTRTL

0001

0001

0002

0002

0001

0001

0002

0002

0001

0002

0003

0004

Footer processing

Header processingEND-OF-SELECTION.LOOP AT tab.AT FIRST....ENDAT.

AT NEW bukrs....ENDAT.

AT NEW werks....ENDAT.

Single recordprocessingAT END OF werks....ENDAT.

AT END OF bukrs....ENDAT.

AT LAST....ENDAT.

ENDLOOP.



Infosets and Infoset Query



Infosets and User Groups



Assign Infosets to User Groups ( Transaction SQ03 )



Reporting on Data from PNP/PNPCE and PCH

Logical database

PNP PCH PAP

Selection of Persons Objects from Personnel Planning

Applicants

Infotypes that can be included in the InfoSet

Infotypes for Personnel

Administration (0000-0999)

Time Management (2000-2999)

Payroll infotypes Infotypes for Personnel

Planning objects that can be related to persons

If the object type is specified:

Infotypes for the object type

Infotypes for objects that can be related to the specified object type

If the object type is not specified:

All infotypes

Infotypes for Recruitment (4000-4999)

Some infotypes for Personnel Administration (such as 0001 and 0002)

Customer infotypes



Procedure for Creating and Changing Infosets (SQ02)



Initial Maintenance Screen for Reporting on Person/Applicants



Ad Hoc Query



Creating Queries II



Ad Hoc Query: Overview



Restricting Reporting Set



Creating Queries



Infotypes



Infotype Data Structure

Four digit number nnnn

Unique identification

9000 to 9999 reserved for customer infotypes



Naming Conventions for Infotypes

0000 to 0999 – HR Master data / Applicant data

1000 to 1999 – Organizational Management

2000 to 2999 – Time data

4000 to 4999 – Applicant data

5000 to 5999 – Planning Infotypes

9000 to 9999 – Customer defined



Personnel Administration Transparent Tables

Key Fields

Administration Fields

Custom Fields



Database Table For Applicant Infotypes



Components of an Infotype



subroutinesMPnnnn40

PAI modules for the screensMPnnnn30

PBO modules for the screensMPnnnn20

The PROGRAM statement andthe declaration of common data objects

MPnnnn10

The include containsName of include

Infotype specific include programs

The main program MPnnnn00 only contains INCLUDE statements. If you create the main program using transaction PM01 Dialogs in HR, the system also creates the following four includes:



Each infotype has at least three screens: An initial screen ( 1000 )

Initial screen is used as technical interface Processed in background and not displayed

A single screen ( 2000 ) Its an interface between the system and the user It enables to create, display or maintain data records

A list screen ( 3000 ) Enables to list all records in info type

Infotype Screens



Initial Screens

Initial screen is used as technical interface

Screen 1000 is used for all infotypes

Processed in background.

Performs general initialization procedures



Initial Screen - Preview



Single Screen - Preview



List Screen - Preview



Infotype 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 No overlapping and no gaps. Eg : Infotype 0000 - Actions

2 No overlapping but time gaps are permitted. Eg : Infotype 0021 - Family Details

3 Overlapping and and time gaps are permitted. Eg : Infotype 0019 Monitoring of Task



Other Possible Time Constraints

A Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting and deletion is not permissible.

B Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting is not permissible, but may be deleted.

T The time constraint varies depending on the subtype.

Z Refers to time management infotypes.



The following tables must be maintained for each infotype:

Name of table Task

T582A Basic infotype characteristics

(database tables, single screen, list screen, time constraint, dialogmodule, and so on)

T582S Infotype short texts

T777A Technical Characteristics of Infotype (database table, dialog module, andso on)

T77ID Name of data field structure (PSnnnn)

Infotype Characteristics



Creating Personnel Administration Infotypes – Step 1



Created Objects



Enhancing Personnel Administration Infotypes – Overview



Enhancing Personnel Administration Infotypes – Procedure



Enhancing Infotypes – Created Objects



Creating HRP info types

Transaction code : ‘PPCI’.

(Personnel Planning Infotype Copier)




We can create the following kinds of info types:

Language-dependent field info types Language-independent field info types Language-dependent table info types Language-independent table info types

We can also specify whether an info type is country-specific or not




Start the Data Dictionary (SE11)

Select the Radio button Data Type Enter the HRI9nnn ( Where 9nnn is info type no).

Click on Create Button, and Create the required Structure

Save , Check and Activate the Structure




Go to T Code : PPCI

Enter Info the details

Info type : 9nnn Info type name : xxxxx

Click on Create, it will display Extended screen




♠ Here you can select Field info type / Table Info Type

♠ Language Dependent/ Independent

♠ Country Specific / not

♠ After selecting these options click on Create Button




After Creation of Infotype Maintain the Following Details using TCode: OOIT

Time Constraint

Infotype Per Object Type



Logical Database PCH(PNP)



Data Model



Relationship Between Basic Object Type



Table Infotype



Sequential Evaluation



Structural Evaluation



Evaluation Path



Maintaining Evaluation Path



Sequential Evaluation Coding



Structural Evaluations Coding



Structure Parameters



Setting Structure Condition



Filling Fields in the Selection Screen



Evaluating Additional Data on Relationship



Evaluating Table Infotype



Evaluating the Infotype Index



Questions ?



Thank You

sap hr abap

Documents

hr data

logical database pnp

sap hr logical databases

hr master data

database tables

following logical databases

hr infotypes

hr infosets