SAP Function Modules
HR_EVENT_CREATE SAP Function module - Create Event for Employees and Applicants using Infotype Operations
HR_EVENT_CREATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.
See here to view full function module documentation and code listing, simply by entering the name HR_EVENT_CREATE into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
HRWF
Released Date:
Not Released
Processing type: Remote-Enabled
Pattern for FM HR_EVENT_CREATE - HR EVENT CREATE
CALL FUNCTION 'HR_EVENT_CREATE' "Create Event for Employees and Applicants using Infotype Operations
EXPORTING
entity = " pspar-tclas Employee or applicant (transaction class)
* no_commit_for_queue = " sweflags-commitflag
TABLES
db_operations = " prelo Database operations of infotypes (PSOPER)
* before_image_when_update = " prelp Before image already filled at update
EXCEPTIONS
NO_POTENTIAL_BUSINESSOBJECT = 1 "
NO_INFOTYPE_OPERATION = 2 "
EVENT_COUPLING_DEACTIVATED = 3 "
. " HR_EVENT_CREATE
ABAP code example for Function Module HR_EVENT_CREATE
The ABAP code below is a full code listing to execute function module HR_EVENT_CREATE including all data declarations. The code uses the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the original method of declaring data variables up front. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8).
| it_db_operations | TYPE STANDARD TABLE OF PRELO,"TABLES PARAM |
| wa_db_operations | LIKE LINE OF it_db_operations , |
| it_before_image_when_update | TYPE STANDARD TABLE OF PRELP,"TABLES PARAM |
| wa_before_image_when_update | LIKE LINE OF it_before_image_when_update . |
DATA(ld_entity) = some text here
DATA(ld_no_commit_for_queue) = some text here
"populate fields of struture and append to itab
append wa_db_operations to it_db_operations.
"populate fields of struture and append to itab
append wa_before_image_when_update to it_before_image_when_update. . CALL FUNCTION 'HR_EVENT_CREATE' EXPORTING entity = ld_entity * no_commit_for_queue = ld_no_commit_for_queue TABLES db_operations = it_db_operations * before_image_when_update = it_before_image_when_update EXCEPTIONS NO_POTENTIAL_BUSINESSOBJECT = 1 NO_INFOTYPE_OPERATION = 2 EVENT_COUPLING_DEACTIVATED = 3 . " HR_EVENT_CREATE
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.
ABAP code to compare 7.40 inline data declaration with original syntax
The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.
DATA:
| ld_entity | TYPE PSPAR-TCLAS , |
| it_db_operations | TYPE STANDARD TABLE OF PRELO , |
| wa_db_operations | LIKE LINE OF it_db_operations, |
| ld_no_commit_for_queue | TYPE SWEFLAGS-COMMITFLAG , |
| it_before_image_when_update | TYPE STANDARD TABLE OF PRELP , |
| wa_before_image_when_update | LIKE LINE OF it_before_image_when_update. |
ld_entity = some text here
"populate fields of struture and append to itab
append wa_db_operations to it_db_operations.
ld_no_commit_for_queue = some text here
"populate fields of struture and append to itab
append wa_before_image_when_update to it_before_image_when_update.
Contribute (Add Comments)
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name HR_EVENT_CREATE or its description.