HRABAP Basics

1.All reports that use the logical database PNP automatically contains DBPNPCOM module
2.SAPDBPNP is the name of the database program for the logical database PNP.
3.Why use LDB in HR Programming?–To reduce programming efforts -events driven, selection screen and data extraction provided by LDB.–Centralised authorisation checking.–Improved performance.•LDB for master data and payroll reporting–Master data (PA) reporting -PNP–Payroll reporting -PNP / selection screen: 900•Report categories –Determines which function keys are available, which selection parameters appear and the properties of the selection parameters.
4You can also read the records of an infotype for a particular personnel number without using the logical database,through RP-READ-INFOTYPE
5The macro RP-PROVIDE-FROM-LAST retrieves the last(latest) data record which is valid in the data selection period.
RP_PROVIDE_FROM_LAST Pnnnn SPACE PN-BEGDA PN-ENDDA.
6The macro RP-PROVIDE-FROM-FRST retrieves the first(start) data record which is valid in the data selection period.
7For every macro, whether the operation was successful or notwill be checked with PNP-SW-FOUND. If PNP-SW-FOUND = 1 , then the operation is successful.
8.A job is a general classification, such as Secretary, Computer Programmer, Instructor, and so on.
9. Positions are the individual employee assignments within a company.
10.work centers identify a location where work is carried out
11.Tasks are individual duties, responsibilities or assignments that employees are required to perform or may perform.
12.TCluster : set of data objects. This collection of data objects can consist of:
Fields used within reports
Field strings
Internal tables
13.You can store data clusters in ABAP/4 memory for short time and in database for longer time.
14.Client: self-contained unit in an R/3 System with separate master records and its own set of tables.
15.Company code : Represents the highest level of Company structure.
16.Personnel Area : It can represent large divisions within a company and Geographic locations.
17.Personnel Sub-area : Personnel sub areas are a subdivision of the personnel area. At this level ,the organizational aspects are controlled here.Country groupings , Public Holiday calendar and wage type structures comes under organizational aspects.
18.Employee Group : General classification of employees.
Active ,
Retired,
Contractors and
External Employees.
19.Employee Sub group : Division of employee groups.
Hourly based,
Salaried,
Executives and
Trainees
20.Payroll Area : The active employees are also divided into payroll areas that determine when they receive their paychecks like weekly or semi-monthly.
21.Organization Unit : Performs a specific set of functions within company Department or subsidiary etc
22.. Display HR Master data (PA20)
23. Maintain HR Master data (PA30)
24. Personnel Actions (PA40)
25.pm01 to create infotypes in PA
26.infotypes:To group related data fields
27.PAnnnn for transparent tables in Personnel Administration
28.PBnnnn for transparent tables in Recruitment
29.HRPnnnn for transparent tables in Personnel Planning
30Infotypecan be subdivided into subtype
31. which also controls the actions of the infotype.
32. E.g. Family/Related Person (IT0021).•Infotypecan be subdivided further by object identification. E.g. Family/Related Person (IT0021), subtype Child.
33.Infotypesnumber ranges
34. 0000-0999HR Master Data
35. 1000-1999Organisational management/personnel planning
36. 2000-2999Time management
37. 4000-4999Recruitment
38. 9000-9999Customer-developed enhancements
39.A time constraint indicates whether more than one infotype record may be available at one time.
40.Time and time constraints in infotypes–validity start (BEGDA) and end date (ENDDA) of a record –time constraint class
41.Time constraint 1:information that must exist. No overlapping and no gaps. E.g. the name of an employee. Creation of new record will automatically delimits the previous data record.–time constraint class .
42.Time constraint 2•information that can exist at any time but not required.No overlapping but time gaps are permitted. It may occur only once. E.g. spouse information in IT0021.–time constraint class
43.Time constraint 3 information that can occur as often as necessary. Overlapping and and time gaps are permittedE.g. child information.
44.The following time constraint indicators are permissible:
45. A Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting and deletion is not permissible.
46.B Only one record may exist, valid from 01/01/1800 to 12/31/9999. Splitting is not permissible, but may be deleted.
47.T The time constraint varies depending on the subtype.
48.Z Refers to time management infotypes.

49.The program code pertaining to this macro is stored in the control table RMAC
50.PCL1 is the database for HR application areas.It contains information
regarding the time recording.
51.PCL2 contains information regarding payroll accounting.
52.PCL3 contains applicant data.
53.PCL4 contains change documents for HR master data.
54.PCL5 contains hr cost planning
55.Cluster rx contains the payroll results for country x according to table
T500l.
56.When macro is used to import data,it is not directly get from database table PCL, instead it checks for the buffer directory whether it contains it in main memory.if it is there it takes it from main memory..otherwise it reads from PCL to mainmemory and from there to the report.
57.Standard import programs follow the naming convention RPCLSTxx..xx is cluster.
58.RP-EXP-Cn-xx ( n = 1,2,3,4 and xx is cluster)
59.RP-IMP-Cn-xx ( n = 1,2,3,4 and xx is cluster)
Naming convention for includes when defining clusters:
RPCnxxy0 n = 1, 2, 3 or 4 (for PCL1, PCL2, PCL3, PCL4)
xx = cluster ID
y = country indicator
60.Payroll Result Data (PCL2)Stored in the transparent table PCL2.
61.Example of some clusters available in PCL2:
62. CU -Cluster directory
63. RG -Payroll results (GB
64. B2 -Time management results
65. ZL-Personal shift plan–
66. PS-Generated schema–PT-Texts for generated schema•
67. Data is stored in CLUSTD field.
68. Payroll Result Data (PCL2)
69.Cluster Directory–Payroll directory is created for every employee.–Specific payroll results from an individual payroll period can only be accessed later via this cluster directory.–
70.Structure of cluster directory:•
• SEQNR -contains a sequence number
• ABKRS -contains the payroll group in which the employee’s wages are calculated.
• FPPER -for period of the payroll run
• FPBEG & FPEND -start and end date of the payroll period.
• IABKRS, IPERM, INPER, IPEND -contain the in period information.
• To optimise data selection, RGDIR table of cluster CU is replicated into HRPY_RGDIR.
71.Payroll results can be extracted using the following methods:–If there is a need to do processing at individual steps:
72.Read cluster directory using ‘CU_READ_RGDIR’•
73.Read valid period from cluster directory using ‘CU_READ_LAST’
74Read payroll results using ‘PYXX_READ_PAYROLL_RESULT’using SEQNO returned by ‘CU_READ_LAST’.
75.Using function module ‘PYXX_GET_EVALUATION_PERIODS’
76.Using function module ‘HR_GET_PAYROLL_RESULTS’to import current payroll results.–
77.RPMUST01 -Model report for monthly payroll results
78.RPMUST02 -Model report for monthly payroll results -more than one period.
79.Using LDB for HR-PY programming:–Available from SAP R/3 4.6c and above.–Screen 900 is assigned as the selection-screen at the program attribute.–PYORGSCREEN and PYTIMESCREEN need to be declared in TABLES statement for the extra payroll related selection-screen.–PAYROLL node to be declared in the NODE statement with reference type to PAYGB_RESULT for UK or PAY99_RESULT for international.

80. HR report category can be changed to use Payroll Results (Cluster) for selection screen customisation.