SAP HR_AT_GET_GEMEINDE_DATA Function Module for









HR_AT_GET_GEMEINDE_DATA is a standard hr at get gemeinde data 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 hr at get gemeinde data FM, simply by entering the name HR_AT_GET_GEMEINDE_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: 0PAM
Program Name: SAPL0PAM
Main Program: SAPL0PAM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HR_AT_GET_GEMEINDE_DATA 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 'HR_AT_GET_GEMEINDE_DATA'"
  EXPORTING
   I_GMDNR =  "

 IMPORTING
   E_GNAME =  "
   E_GMD_PLZ =  "
   ET_GMDCD_PSTLZ =  "
   E_GMDNR_EXISTING =  "

EXCEPTIONS
   NO_ENTRY = 1
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPL0PAM_001 HR-AT: Customer Exit for HR_AT_GET_ORG_DATA

IMPORTING Parameters details for HR_AT_GET_GEMEINDE_DATA

I_GMDNR -

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

EXPORTING Parameters details for HR_AT_GET_GEMEINDE_DATA

E_GNAME -

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

E_GMD_PLZ -

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

ET_GMDCD_PSTLZ -

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

E_GMDNR_EXISTING -

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

EXCEPTIONS details

NO_ENTRY -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_AT_GET_GEMEINDE_DATA 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_e_gname  TYPE GNAME, "   
lv_i_gmdnr  TYPE GMDNA, "   
lv_no_entry  TYPE GMDNA, "   
lv_e_gmd_plz  TYPE PSTLZ, "   
lv_et_gmdcd_pstlz  TYPE P03_PSTLZ_TAB, "   
lv_e_gmdnr_existing  TYPE ABAP_BOOL. "   

  CALL FUNCTION 'HR_AT_GET_GEMEINDE_DATA'  "
    EXPORTING
         I_GMDNR = lv_i_gmdnr
    IMPORTING
         E_GNAME = lv_e_gname
         E_GMD_PLZ = lv_e_gmd_plz
         ET_GMDCD_PSTLZ = lv_et_gmdcd_pstlz
         E_GMDNR_EXISTING = lv_e_gmdnr_existing
    EXCEPTIONS
        NO_ENTRY = 1
. " HR_AT_GET_GEMEINDE_DATA




ABAP code using 7.40 inline data declarations to call FM HR_AT_GET_GEMEINDE_DATA

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



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!