SAP HRMGE_GET_F4_DOCUMENT_VERSION Function Module for Erzeugen des F4-Popups zur Bestimmung der Dokumentversion

Search SAP Function Modules

HRMGE_GET_F4_DOCUMENT_VERSION is a standard hrmge get f4 document version SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Erzeugen des F4-Popups zur Bestimmung der Dokumentversion processing and below is the pattern details for this FM, 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 hrmge get f4 document version FM, simply by entering the name HRMGE_GET_F4_DOCUMENT_VERSION into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRMGE00F4HELP
Program Name: SAPLHRMGE00F4HELP
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HRMGE_GET_F4_DOCUMENT_VERSION 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 'HRMGE_GET_F4_DOCUMENT_VERSION'"Erzeugen des F4-Popups zur Bestimmung der Dokumentversion
  EXPORTING
   DOCID =  "Business Document Service: Document ID
*  DYNPPROG =  "
*  DYNPNR =  "ABAP program, number of current screen
*  DYNPROFIELD =  "Field name
*  STEPL =  "Screens, current table line index
*  WINDOW_TITLE =  "
*  FIXED_POSITION = ' ' "
*  DISPLAY_MODE = ' ' "
   MESS_HANDLER =  "HR-Global employees: messages

 IMPORTING
   VERNO =  "BDS Document Template
   IS_OK =  "Return code (True = 'X', False = space)

.

IMPORTING Parameters details for HRMGE_GET_F4_DOCUMENT_VERSION

DOCID - Business Document Service: Document ID

Data type: BDS_DOCID
Optional: No
Call by Reference: No ( called with pass by value option)

DYNPPROG -

Data type: SY-REPID
Optional: Yes
Call by Reference: No ( called with pass by value option)

DYNPNR - ABAP program, number of current screen

Data type: SY-DYNNR
Optional: Yes
Call by Reference: No ( called with pass by value option)

DYNPROFIELD - Field name

Data type: HELP_INFO-DYNPROFLD
Optional: Yes
Call by Reference: No ( called with pass by value option)

STEPL - Screens, current table line index

Data type: HELP_INFO-STEPL
Optional: Yes
Call by Reference: No ( called with pass by value option)

WINDOW_TITLE -

Data type: C
Optional: Yes
Call by Reference: No ( called with pass by value option)

FIXED_POSITION -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

DISPLAY_MODE -

Data type: C
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MESS_HANDLER - HR-Global employees: messages

Data type: IF_HRGE_MESSAGE_HANDLER
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HRMGE_GET_F4_DOCUMENT_VERSION

VERNO - BDS Document Template

Data type: PMGES_OFFICE_DOC
Optional: No
Call by Reference: No ( called with pass by value option)

IS_OK - Return code (True = 'X', False = space)

Data type: PMGE_RETURN_CODE
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HRMGE_GET_F4_DOCUMENT_VERSION 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.

ABAP code using 7.40 inline data declarations to call FM HRMGE_GET_F4_DOCUMENT_VERSION

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