SAP HRHAP_DOC_ACTION_LOG_WRITE Function Module for









HRHAP_DOC_ACTION_LOG_WRITE is a standard hrhap doc action 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 action log write FM, simply by entering the name HRHAP_DOC_ACTION_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_ACTION_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_ACTION_LOG_WRITE'"
  EXPORTING
   PLAN_VERSION =  "Plan Version
*  ENQUEUE_LOG = 'X' "
   S_APPRAISAL_ID =  "Appraisal ID
   ACTION =  "Action which was performed
*  ADMINISTRATOR =  "Flag: Administrator
*  S_STATUS =  "Document (Sub-)Status (if initial -> read in FM)
*  S_MESSAGE_VARIABLES =  "Message Variables
*  TEMPLATE_ID =  "Appraisal Template (if initial -> read in FM)
*  TRUSTED_CALL = ' ' "NO CHECK for Action Log Activation (ONLY IF TEMPLATE IS GIVEN)
*  COMMIT = ' ' "'X'=Commit (only possible if Appraisal exists already)

 IMPORTING
   S_RETURN =  "

EXCEPTIONS
   NOT_SUPPORTED = 1
.



IMPORTING Parameters details for HRHAP_DOC_ACTION_LOG_WRITE

PLAN_VERSION - Plan Version

Data type: HAP_PLAN_VERSION
Optional: No
Call by Reference: Yes

ENQUEUE_LOG -

Data type: BOOLE_D
Default: 'X'
Optional: Yes
Call by Reference: Yes

S_APPRAISAL_ID - Appraisal ID

Data type: HAP_S_APPRAISAL_ID
Optional: No
Call by Reference: Yes

ACTION - Action which was performed

Data type: CHAR3
Optional: No
Call by Reference: Yes

ADMINISTRATOR - Flag: Administrator

Data type: HAP_ADMINISTRATOR
Optional: Yes
Call by Reference: Yes

S_STATUS - Document (Sub-)Status (if initial -> read in FM)

Data type: HAP_S_STATUS_SUB
Optional: Yes
Call by Reference: Yes

S_MESSAGE_VARIABLES - Message Variables

Data type: HAP_S_MESSAGE_VARIABLES
Optional: Yes
Call by Reference: Yes

TEMPLATE_ID - Appraisal Template (if initial -> read in FM)

Data type: HAP_TEMPLATE_ID
Optional: Yes
Call by Reference: Yes

TRUSTED_CALL - NO CHECK for Action Log Activation (ONLY IF TEMPLATE IS GIVEN)

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

COMMIT - 'X'=Commit (only possible if Appraisal exists already)

Data type: CHAR1
Default: ' '
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for HRHAP_DOC_ACTION_LOG_WRITE

S_RETURN -

Data type: BAL_S_MSG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NOT_SUPPORTED - Action Log is not Supported

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRHAP_DOC_ACTION_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_not_supported  TYPE HAP_PLAN_VERSION, "   
lv_enqueue_log  TYPE BOOLE_D, "   'X'
lv_s_appraisal_id  TYPE HAP_S_APPRAISAL_ID, "   
lv_action  TYPE CHAR3, "   
lv_administrator  TYPE HAP_ADMINISTRATOR, "   
lv_s_status  TYPE HAP_S_STATUS_SUB, "   
lv_s_message_variables  TYPE HAP_S_MESSAGE_VARIABLES, "   
lv_template_id  TYPE HAP_TEMPLATE_ID, "   
lv_trusted_call  TYPE CHAR1, "   ' '
lv_commit  TYPE CHAR1. "   ' '

  CALL FUNCTION 'HRHAP_DOC_ACTION_LOG_WRITE'  "
    EXPORTING
         PLAN_VERSION = lv_plan_version
         ENQUEUE_LOG = lv_enqueue_log
         S_APPRAISAL_ID = lv_s_appraisal_id
         ACTION = lv_action
         ADMINISTRATOR = lv_administrator
         S_STATUS = lv_s_status
         S_MESSAGE_VARIABLES = lv_s_message_variables
         TEMPLATE_ID = lv_template_id
         TRUSTED_CALL = lv_trusted_call
         COMMIT = lv_commit
    IMPORTING
         S_RETURN = lv_s_return
    EXCEPTIONS
        NOT_SUPPORTED = 1
. " HRHAP_DOC_ACTION_LOG_WRITE




ABAP code using 7.40 inline data declarations to call FM HRHAP_DOC_ACTION_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.

 
 
 
DATA(ld_enqueue_log) = 'X'.
 
 
 
 
 
 
 
DATA(ld_trusted_call) = ' '.
 
DATA(ld_commit) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!