SAP Function Modules

HRHAP_DOCUMENT_FOLLOW_UP SAP Function module







HRHAP_DOCUMENT_FOLLOW_UP 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 HRHAP_DOCUMENT_FOLLOW_UP into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: HRHAP_IF_DOCUMENT
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM HRHAP_DOCUMENT_FOLLOW_UP - HRHAP DOCUMENT FOLLOW UP





CALL FUNCTION 'HRHAP_DOCUMENT_FOLLOW_UP' "
  EXPORTING
    plan_version =              " hap_plan_version  Plan Version
    appraisal_id =              " hap_appraisal_id  Appraisal ID
*   iv_run_within_doc_luw = SPACE  " boole_d
  IMPORTING
    s_return =                  " bal_s_msg     Application Log: Message Data
    .  "  HRHAP_DOCUMENT_FOLLOW_UP

ABAP code example for Function Module HRHAP_DOCUMENT_FOLLOW_UP





The ABAP code below is a full code listing to execute function module HRHAP_DOCUMENT_FOLLOW_UP 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).

DATA:
ld_s_return  TYPE BAL_S_MSG .

DATA(ld_plan_version) = 'Check type of data required'.
DATA(ld_appraisal_id) = 'Check type of data required'.
DATA(ld_iv_run_within_doc_luw) = 'Check type of data required'. . CALL FUNCTION 'HRHAP_DOCUMENT_FOLLOW_UP' EXPORTING plan_version = ld_plan_version appraisal_id = ld_appraisal_id * iv_run_within_doc_luw = ld_iv_run_within_doc_luw IMPORTING s_return = ld_s_return . " HRHAP_DOCUMENT_FOLLOW_UP
IF SY-SUBRC EQ 0. "All OK 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_s_return  TYPE BAL_S_MSG ,
ld_plan_version  TYPE HAP_PLAN_VERSION ,
ld_appraisal_id  TYPE HAP_APPRAISAL_ID ,
ld_iv_run_within_doc_luw  TYPE BOOLE_D .

ld_plan_version = 'Check type of data required'.
ld_appraisal_id = 'Check type of data required'.
ld_iv_run_within_doc_luw = 'Check type of data required'.

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 HRHAP_DOCUMENT_FOLLOW_UP or its description.