ABAP HR forms an integral part of ABAP. It can be said as a sub-part / sub-module of ABAP.
Generally in ABAP, following activities are done:
1) Report developing
2) Table development
3) BAPIs / RFC
4) Data Processing
5) Database update
6) Function Building
7) Screens development/enhancement
8) Scripts and smart forms.
9) Java connectors etc.
This is done through the PROGRAMMING in ABAP builder using ABAP 4th generation languge and now, OO-ABAP. This may be related to any module of SAP like HR, FICO, SD, MM, CRM etc.
Now when it comes to ABAP HR, it is the development of ABAP in the area of HR to meet the clients requirements according to the functional specifications. They may be in any area of HR like in the areas of time aspects, pay aspects, OM aspects and Self Services like E-recruitment, ESS etc.
The following concepts are defined in ABAP HR which is different with other modules.
Use of Infotypes
The use of Logical Database
Use of Macros and Provide statement
Storage and Access of data
There is nothing much difference between ABAP and ABAP HR; except the way we retrieve the data from database. In general ABAP data is stored in Tables, but coming to ABAP HR employee data is sorted through Infotypes. The way we retrieve the data from infotypes is different in ABAP HR.
In general ABAP we use Logical database very rare, as in ABAP HR most of the programs use Logical data base to select data from Infotypes using Get Event.
In ABAP we use Read statement to read particular record, still in ABAP HR 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 different in ABAP HR comparing with ABAP. We use transaction code PA20 and PA30 to maintain data in infotypes.
PA20 is display mode and PA30 is change mode for Employee Data. 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 secret.