HR Abap Technical Overview
HR Abap Technical Overview
HR ABAP
Technical Overview
List of Topics
▪Logical Databases
▪Join & Projection
▪Reports / Repetitive Structures
▪Clusters
▪Time Data
▪Infosets & Infoset Queries
▪Infotypes
▪Logical Database PCH
Logical Databases
▪ 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
▪ Structure
▪The structure defines the data view
of the logical database.
▪ Selections
▪The selections define a selection
screen, which forms the user
interface of the executable
programs that use the logical
database.
▪ Database Program
▪The database program contains the
ABAP statements used to read the
data and pass it to the user of the
logical database.
LDB - Screening
Joins in PROVIDE
Join / Subtypes
HR Macros
▪ RP_PROVIDE_FROM_LAST
▪ RP_PROVIDE_FROM_FIRST
▪ RP_SET_DATA_INTERVAL
▪ RP_READ_INFOTYPE
▪ RP-READ-ALL-TIME-ITY
▪ 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
Dynamic Actions
▪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
▪ 02 for Change
▪ 04 for Create
▪ 08 for Delete
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
Clusters
Importing Data
Payroll Results
Where xx :-
99 = International
DE = Germany
IN = India
FI = Finland
Where xx :-
99 = International
DE = Germany
IN = India
FI = Finland
▪ 1. PYXX_GET_RELID_FROM_PERNR
▪ 2. CU_READ_RGDIR
▪ 3. CD_READ_LAST
▪ 4. PYXX_READ_PAYROLL_RESULT
Time Data
Time Data
∙ Customer infotypes
Ad Hoc Query
Creating Queries II
Creating Queries
Infotypes
▪ Unique
identification
▪ 9000 to 9999
reserved for
customer infotypes
Key
Fields
Administration
Fields
Custom Fields
Components of an Infotype
Infotype Screens
Initial Screens
Processed in background.
▪ 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
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.
Infotype Characteristics
Created Objects
Select the Radio button Data Type Enter the HRI9nnn ( Where 9nnn is info
type no).
Go to T Code : PPCI
♠ Here you can select Field info type / Table Info Type
After Creation of Infotype Maintain the Following Details using TCode: OOIT
Time Constraint
Data Model
Table Infotype
Sequential Evaluation
Structural Evaluation
Evaluation Path
Structure Parameters
▪Questions ?
Thank You