SAP HRHAP_DOC_CHANGE_LOG_WRITE Function Module for
HRHAP_DOC_CHANGE_LOG_WRITE is a standard hrhap doc change log write SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for hrhap doc change log write FM, simply by entering the name HRHAP_DOC_CHANGE_LOG_WRITE into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRHAP_IF_DOC_ACTION_LOG
Program Name: SAPLHRHAP_IF_DOC_ACTION_LOG
Main Program: SAPLHRHAP_IF_DOC_ACTION_LOG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRHAP_DOC_CHANGE_LOG_WRITE pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'HRHAP_DOC_CHANGE_LOG_WRITE'".
EXPORTING
PLAN_VERSION = "
* S_HEADER_STATUS = "
* T_BODY_COLUMNS = "
* T_BODY_ELEMENTS = "
* T_BODY_CELLS = "
* T_BODY_CELL_NOTES = "
* COMMIT = "
S_APPRAISAL_ID = "
S_DOC_PROCESSING = "
* T_HEADER_APPRAISER = "
* T_HEADER_APPRAISEE = "
* T_HEADER_PART_APPRAISERS = "
* T_HEADER_OTHERS = "
* S_HEADER_TEXTS = "
* S_HEADER_DATES = "
IMPORTING
S_RETURN = "
IMPORTING Parameters details for HRHAP_DOC_CHANGE_LOG_WRITE
PLAN_VERSION -
Data type: HAP_PLAN_VERSIONOptional: No
Call by Reference: Yes
S_HEADER_STATUS -
Data type: HAP_S_HEADER_STATUSOptional: Yes
Call by Reference: Yes
T_BODY_COLUMNS -
Data type: HAP_T_BODY_COLUMNSOptional: Yes
Call by Reference: Yes
T_BODY_ELEMENTS -
Data type: HAP_T_BODY_ELEMENTSOptional: Yes
Call by Reference: Yes
T_BODY_CELLS -
Data type: HAP_T_BODY_CELLSOptional: Yes
Call by Reference: Yes
T_BODY_CELL_NOTES -
Data type: HAP_T_BODY_CELL_NOTESOptional: Yes
Call by Reference: Yes
COMMIT -
Data type: BOOLE_DOptional: Yes
Call by Reference: Yes
S_APPRAISAL_ID -
Data type: HAP_S_APPRAISAL_IDOptional: No
Call by Reference: Yes
S_DOC_PROCESSING -
Data type: HAP_S_DOC_PROCESSINGOptional: No
Call by Reference: Yes
T_HEADER_APPRAISER -
Data type: HAP_T_HEADER_APPRAISEROptional: Yes
Call by Reference: Yes
T_HEADER_APPRAISEE -
Data type: HAP_T_HEADER_APPRAISEEOptional: Yes
Call by Reference: Yes
T_HEADER_PART_APPRAISERS -
Data type: HAP_T_HEADER_PART_APPRAISERSOptional: Yes
Call by Reference: Yes
T_HEADER_OTHERS -
Data type: HAP_T_HEADER_OTHERSOptional: Yes
Call by Reference: Yes
S_HEADER_TEXTS -
Data type: HAP_S_HEADER_TEXTSOptional: Yes
Call by Reference: Yes
S_HEADER_DATES -
Data type: HAP_S_HEADER_DATESOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for HRHAP_DOC_CHANGE_LOG_WRITE
S_RETURN -
Data type: BAL_S_MSGOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HRHAP_DOC_CHANGE_LOG_WRITE Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_s_return | TYPE BAL_S_MSG, " | |||
| lv_plan_version | TYPE HAP_PLAN_VERSION, " | |||
| lv_s_header_status | TYPE HAP_S_HEADER_STATUS, " | |||
| lv_t_body_columns | TYPE HAP_T_BODY_COLUMNS, " | |||
| lv_t_body_elements | TYPE HAP_T_BODY_ELEMENTS, " | |||
| lv_t_body_cells | TYPE HAP_T_BODY_CELLS, " | |||
| lv_t_body_cell_notes | TYPE HAP_T_BODY_CELL_NOTES, " | |||
| lv_commit | TYPE BOOLE_D, " | |||
| lv_s_appraisal_id | TYPE HAP_S_APPRAISAL_ID, " | |||
| lv_s_doc_processing | TYPE HAP_S_DOC_PROCESSING, " | |||
| lv_t_header_appraiser | TYPE HAP_T_HEADER_APPRAISER, " | |||
| lv_t_header_appraisee | TYPE HAP_T_HEADER_APPRAISEE, " | |||
| lv_t_header_part_appraisers | TYPE HAP_T_HEADER_PART_APPRAISERS, " | |||
| lv_t_header_others | TYPE HAP_T_HEADER_OTHERS, " | |||
| lv_s_header_texts | TYPE HAP_S_HEADER_TEXTS, " | |||
| lv_s_header_dates | TYPE HAP_S_HEADER_DATES. " |
|   CALL FUNCTION 'HRHAP_DOC_CHANGE_LOG_WRITE' " |
| EXPORTING | ||
| PLAN_VERSION | = lv_plan_version | |
| S_HEADER_STATUS | = lv_s_header_status | |
| T_BODY_COLUMNS | = lv_t_body_columns | |
| T_BODY_ELEMENTS | = lv_t_body_elements | |
| T_BODY_CELLS | = lv_t_body_cells | |
| T_BODY_CELL_NOTES | = lv_t_body_cell_notes | |
| COMMIT | = lv_commit | |
| S_APPRAISAL_ID | = lv_s_appraisal_id | |
| S_DOC_PROCESSING | = lv_s_doc_processing | |
| T_HEADER_APPRAISER | = lv_t_header_appraiser | |
| T_HEADER_APPRAISEE | = lv_t_header_appraisee | |
| T_HEADER_PART_APPRAISERS | = lv_t_header_part_appraisers | |
| T_HEADER_OTHERS | = lv_t_header_others | |
| S_HEADER_TEXTS | = lv_s_header_texts | |
| S_HEADER_DATES | = lv_s_header_dates | |
| IMPORTING | ||
| S_RETURN | = lv_s_return | |
| . " HRHAP_DOC_CHANGE_LOG_WRITE | ||
ABAP code using 7.40 inline data declarations to call FM HRHAP_DOC_CHANGE_LOG_WRITE
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects