Embedded Files
BAPI_EMPLOYEE_ENQUEUE & BAPI_EMPLOYEE_DEQUEUE
Standard Function modules to lock / unlock employees so that their records can be changed while they are not accessible to others for change. The user who has locked an employee can only unlock it.
HR_EMPLOYEE_ENQUEUE & HR_EMPLOYEE_DEQUEUE
Same as above but BAPI_EMPLOYEE_ENQUEUE / DEQUEUE are recommended.
You can transfer one data record. All validation checks take place that would take place in the individual maintenance screens in the dialog. Using this FM within LOOP, multiple employees can be processed.
Used to maintain employees / applicants master data. An internal table with proposed values with field names and field contents is constructed and passed to the FM.Several records or infotypes can be added at once. The data should be consistent. The same validation checks take place as would in the individual maintenance screens for the infotypes.
Reads Employee / Applicant master data. For the Employee, infotype, begin and end dates, it fetches the data into an internal table of the required type which may be created using the INFOTYPES statement.
HR_READ_INFOTYPE_AUTHC_DISABLE
to bypass the read access check. I don't think there is any F/M to disable the authorization check for HR_INFOTYPE_OPERATION which is understandable.
HR_GETEMPLOYEEDATA_FROMUSER
(RFC) fetches general data for the exported user-id (not pernr).
HR_FEATURE_BACKFIELD / BACKTABLE
reads the decision tree of a feature with the transferred field contents, and determines the expected return value for the field contents.
HR_READ_INFOTYPE
Read Employee/Applicant Data From Infotypes.
HR_CHECK_AUTHORITY_TCODE
Check user Authority for a transaction code.
Other resources
Other resources
Use of HR Function Modules
http://old.captainsap.fr/index.php?option=com_content&task=view&id=181&Itemid=40
Page updated
Google Sites
Report abuse