SAP BAPI_ADDRESSEMPDK_REQUEST Function Module for Create Locked Employee Address Record









BAPI_ADDRESSEMPDK_REQUEST is a standard bapi addressempdk request SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create Locked Employee Address Record 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 bapi addressempdk request FM, simply by entering the name BAPI_ADDRESSEMPDK_REQUEST into the relevant SAP transaction such as SE37 or SE38.

Function Group: PADR_DK
Program Name: SAPLPADR_DK
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BAPI_ADDRESSEMPDK_REQUEST 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 'BAPI_ADDRESSEMPDK_REQUEST'"Create Locked Employee Address Record
EXPORTING
EMPLOYEENUMBER = "
* POSTALCODECITY = "
* STATE = "
* COUNTRY = "
* BUS_ROUTE = "
* COMPANY_APARTMENT = "
* DISTANCE = "
* DISTANCE2 = "
* TELEPHONENUMBER = "
* COMMTYPE1 = "Communication type
* COMMNUMBER1 = "Communication Number
VALIDITYBEGIN = "
* COMMTYPE2 = "Communication type
* COMMNUMBER2 = "Communication Number
* COMMTYPE3 = "Communication type
* COMMNUMBER3 = "Communication Number
* COMMTYPE4 = "Communication type
* COMMNUMBER4 = "Communication Number
* COMMTYPE5 = "Communication type
* COMMNUMBER5 = "Communication Number
* COMMTYPE6 = "Communication type
* COMMNUMBER6 = "Communication Number
VALIDITYEND = "
* CITY_DISTRICT = "City/district (katakana)
* HOUSE_NO = "House number
* COUNTY_CDE = "County code
* HOUSE_ID = "Identification of an apartment in a building
* NOCOMMIT = "
ADDRESSTYPE = "
* CONAME = "
* STREETANDHOUSENO = "
* SCNDADDRESSLINE = "
* CITY = "
* DISTRICT = "

IMPORTING
RETURN = "
EMPLOYEENUMBER = "
SUBTYPE = "
OBJECTID = "
LOCKINDICATOR = "
VALIDITYBEGIN = "
VALIDITYEND = "
RECORDNUMBER = "
.



IMPORTING Parameters details for BAPI_ADDRESSEMPDK_REQUEST

EMPLOYEENUMBER -

Data type: BAPIP0006-PERNR
Optional: No
Call by Reference: No ( called with pass by value option)

POSTALCODECITY -

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

STATE -

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

COUNTRY -

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

BUS_ROUTE -

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

COMPANY_APARTMENT -

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

DISTANCE -

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

DISTANCE2 -

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

TELEPHONENUMBER -

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

COMMTYPE1 - Communication type

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

COMMNUMBER1 - Communication Number

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

VALIDITYBEGIN -

Data type: BAPIP0006-BEGDA
Optional: No
Call by Reference: No ( called with pass by value option)

COMMTYPE2 - Communication type

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

COMMNUMBER2 - Communication Number

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

COMMTYPE3 - Communication type

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

COMMNUMBER3 - Communication Number

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

COMMTYPE4 - Communication type

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

COMMNUMBER4 - Communication Number

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

COMMTYPE5 - Communication type

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

COMMNUMBER5 - Communication Number

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

COMMTYPE6 - Communication type

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

COMMNUMBER6 - Communication Number

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

VALIDITYEND -

Data type: BAPIP0006-ENDDA
Optional: No
Call by Reference: No ( called with pass by value option)

CITY_DISTRICT - City/district (katakana)

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

HOUSE_NO - House number

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

COUNTY_CDE - County code

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

HOUSE_ID - Identification of an apartment in a building

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

NOCOMMIT -

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

ADDRESSTYPE -

Data type: BAPIP0006-SUBTY
Optional: No
Call by Reference: No ( called with pass by value option)

CONAME -

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

STREETANDHOUSENO -

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

SCNDADDRESSLINE -

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

CITY -

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

DISTRICT -

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

EXPORTING Parameters details for BAPI_ADDRESSEMPDK_REQUEST

RETURN -

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

EMPLOYEENUMBER -

Data type: BAPIP0006-PERNR
Optional: No
Call by Reference: No ( called with pass by value option)

SUBTYPE -

Data type: BAPIP0006-SUBTY
Optional: No
Call by Reference: No ( called with pass by value option)

OBJECTID -

Data type: BAPIP0006-OBJPS
Optional: No
Call by Reference: No ( called with pass by value option)

LOCKINDICATOR -

Data type: BAPIP0006-SPRPS
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYBEGIN -

Data type: BAPIP0006-BEGDA
Optional: No
Call by Reference: No ( called with pass by value option)

VALIDITYEND -

Data type: BAPIP0006-ENDDA
Optional: No
Call by Reference: No ( called with pass by value option)

RECORDNUMBER -

Data type: BAPIP0006-SEQNR
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BAPI_ADDRESSEMPDK_REQUEST 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_return  TYPE BAPIRETURN1, "   
lv_employeenumber  TYPE BAPIP0006-PERNR, "   
lv_postalcodecity  TYPE BAPIP0006-PSTLZ, "   
lv_state  TYPE BAPIP0006-STATE, "   
lv_country  TYPE BAPIP0006-LAND1, "   
lv_bus_route  TYPE BAPIP0006-BUSRT, "   
lv_company_apartment  TYPE BAPIP0006-WKWNG, "   
lv_distance  TYPE BAPIP0006-ENTKM, "   
lv_distance2  TYPE BAPIP0006-ENTK2, "   
lv_telephonenumber  TYPE BAPIP0006-TELNR, "   
lv_commtype1  TYPE BAPIP0006LDK-COMMTYPE1, "   
lv_commnumber1  TYPE BAPIP0006LDK-COMMNUMBER1, "   
lv_validitybegin  TYPE BAPIP0006-BEGDA, "   
lv_employeenumber  TYPE BAPIP0006-PERNR, "   
lv_commtype2  TYPE BAPIP0006LDK-COMMTYPE2, "   
lv_commnumber2  TYPE BAPIP0006LDK-COMMNUMBER2, "   
lv_commtype3  TYPE BAPIP0006LDK-COMMTYPE3, "   
lv_commnumber3  TYPE BAPIP0006LDK-COMMNUMBER3, "   
lv_commtype4  TYPE BAPIP0006LDK-COMMTYPE4, "   
lv_commnumber4  TYPE BAPIP0006LDK-COMMNUMBER4, "   
lv_commtype5  TYPE BAPIP0006LDK-COMMTYPE5, "   
lv_commnumber5  TYPE BAPIP0006LDK-COMMNUMBER5, "   
lv_commtype6  TYPE BAPIP0006LDK-COMMTYPE6, "   
lv_commnumber6  TYPE BAPIP0006LDK-COMMNUMBER6, "   
lv_subtype  TYPE BAPIP0006-SUBTY, "   
lv_validityend  TYPE BAPIP0006-ENDDA, "   
lv_city_district  TYPE BAPIP0006LDK-CITY_DISTRICT, "   
lv_house_no  TYPE BAPIP0006LDK-HOUSE_NO, "   
lv_county_cde  TYPE BAPIP0006LDK-COUNTY_CDE, "   
lv_house_id  TYPE BAPIP0006LDK-HOUSE_ID, "   
lv_nocommit  TYPE BAPI_STAND-NO_COMMIT, "   
lv_objectid  TYPE BAPIP0006-OBJPS, "   
lv_addresstype  TYPE BAPIP0006-SUBTY, "   
lv_coname  TYPE BAPIP0006-NAME2, "   
lv_lockindicator  TYPE BAPIP0006-SPRPS, "   
lv_validitybegin  TYPE BAPIP0006-BEGDA, "   
lv_streetandhouseno  TYPE BAPIP0006-STRAS, "   
lv_validityend  TYPE BAPIP0006-ENDDA, "   
lv_scndaddressline  TYPE BAPIP0006-LOCAT, "   
lv_city  TYPE BAPIP0006-ORT01, "   
lv_recordnumber  TYPE BAPIP0006-SEQNR, "   
lv_district  TYPE BAPIP0006-ORT02. "   

  CALL FUNCTION 'BAPI_ADDRESSEMPDK_REQUEST'  "Create Locked Employee Address Record
    EXPORTING
         EMPLOYEENUMBER = lv_employeenumber
         POSTALCODECITY = lv_postalcodecity
         STATE = lv_state
         COUNTRY = lv_country
         BUS_ROUTE = lv_bus_route
         COMPANY_APARTMENT = lv_company_apartment
         DISTANCE = lv_distance
         DISTANCE2 = lv_distance2
         TELEPHONENUMBER = lv_telephonenumber
         COMMTYPE1 = lv_commtype1
         COMMNUMBER1 = lv_commnumber1
         VALIDITYBEGIN = lv_validitybegin
         COMMTYPE2 = lv_commtype2
         COMMNUMBER2 = lv_commnumber2
         COMMTYPE3 = lv_commtype3
         COMMNUMBER3 = lv_commnumber3
         COMMTYPE4 = lv_commtype4
         COMMNUMBER4 = lv_commnumber4
         COMMTYPE5 = lv_commtype5
         COMMNUMBER5 = lv_commnumber5
         COMMTYPE6 = lv_commtype6
         COMMNUMBER6 = lv_commnumber6
         VALIDITYEND = lv_validityend
         CITY_DISTRICT = lv_city_district
         HOUSE_NO = lv_house_no
         COUNTY_CDE = lv_county_cde
         HOUSE_ID = lv_house_id
         NOCOMMIT = lv_nocommit
         ADDRESSTYPE = lv_addresstype
         CONAME = lv_coname
         STREETANDHOUSENO = lv_streetandhouseno
         SCNDADDRESSLINE = lv_scndaddressline
         CITY = lv_city
         DISTRICT = lv_district
    IMPORTING
         RETURN = lv_return
         EMPLOYEENUMBER = lv_employeenumber
         SUBTYPE = lv_subtype
         OBJECTID = lv_objectid
         LOCKINDICATOR = lv_lockindicator
         VALIDITYBEGIN = lv_validitybegin
         VALIDITYEND = lv_validityend
         RECORDNUMBER = lv_recordnumber
. " BAPI_ADDRESSEMPDK_REQUEST




ABAP code using 7.40 inline data declarations to call FM BAPI_ADDRESSEMPDK_REQUEST

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.

 
"SELECT single PERNR FROM BAPIP0006 INTO @DATA(ld_employeenumber).
 
"SELECT single PSTLZ FROM BAPIP0006 INTO @DATA(ld_postalcodecity).
 
"SELECT single STATE FROM BAPIP0006 INTO @DATA(ld_state).
 
"SELECT single LAND1 FROM BAPIP0006 INTO @DATA(ld_country).
 
"SELECT single BUSRT FROM BAPIP0006 INTO @DATA(ld_bus_route).
 
"SELECT single WKWNG FROM BAPIP0006 INTO @DATA(ld_company_apartment).
 
"SELECT single ENTKM FROM BAPIP0006 INTO @DATA(ld_distance).
 
"SELECT single ENTK2 FROM BAPIP0006 INTO @DATA(ld_distance2).
 
"SELECT single TELNR FROM BAPIP0006 INTO @DATA(ld_telephonenumber).
 
"SELECT single COMMTYPE1 FROM BAPIP0006LDK INTO @DATA(ld_commtype1).
 
"SELECT single COMMNUMBER1 FROM BAPIP0006LDK INTO @DATA(ld_commnumber1).
 
"SELECT single BEGDA FROM BAPIP0006 INTO @DATA(ld_validitybegin).
 
"SELECT single PERNR FROM BAPIP0006 INTO @DATA(ld_employeenumber).
 
"SELECT single COMMTYPE2 FROM BAPIP0006LDK INTO @DATA(ld_commtype2).
 
"SELECT single COMMNUMBER2 FROM BAPIP0006LDK INTO @DATA(ld_commnumber2).
 
"SELECT single COMMTYPE3 FROM BAPIP0006LDK INTO @DATA(ld_commtype3).
 
"SELECT single COMMNUMBER3 FROM BAPIP0006LDK INTO @DATA(ld_commnumber3).
 
"SELECT single COMMTYPE4 FROM BAPIP0006LDK INTO @DATA(ld_commtype4).
 
"SELECT single COMMNUMBER4 FROM BAPIP0006LDK INTO @DATA(ld_commnumber4).
 
"SELECT single COMMTYPE5 FROM BAPIP0006LDK INTO @DATA(ld_commtype5).
 
"SELECT single COMMNUMBER5 FROM BAPIP0006LDK INTO @DATA(ld_commnumber5).
 
"SELECT single COMMTYPE6 FROM BAPIP0006LDK INTO @DATA(ld_commtype6).
 
"SELECT single COMMNUMBER6 FROM BAPIP0006LDK INTO @DATA(ld_commnumber6).
 
"SELECT single SUBTY FROM BAPIP0006 INTO @DATA(ld_subtype).
 
"SELECT single ENDDA FROM BAPIP0006 INTO @DATA(ld_validityend).
 
"SELECT single CITY_DISTRICT FROM BAPIP0006LDK INTO @DATA(ld_city_district).
 
"SELECT single HOUSE_NO FROM BAPIP0006LDK INTO @DATA(ld_house_no).
 
"SELECT single COUNTY_CDE FROM BAPIP0006LDK INTO @DATA(ld_county_cde).
 
"SELECT single HOUSE_ID FROM BAPIP0006LDK INTO @DATA(ld_house_id).
 
"SELECT single NO_COMMIT FROM BAPI_STAND INTO @DATA(ld_nocommit).
 
"SELECT single OBJPS FROM BAPIP0006 INTO @DATA(ld_objectid).
 
"SELECT single SUBTY FROM BAPIP0006 INTO @DATA(ld_addresstype).
 
"SELECT single NAME2 FROM BAPIP0006 INTO @DATA(ld_coname).
 
"SELECT single SPRPS FROM BAPIP0006 INTO @DATA(ld_lockindicator).
 
"SELECT single BEGDA FROM BAPIP0006 INTO @DATA(ld_validitybegin).
 
"SELECT single STRAS FROM BAPIP0006 INTO @DATA(ld_streetandhouseno).
 
"SELECT single ENDDA FROM BAPIP0006 INTO @DATA(ld_validityend).
 
"SELECT single LOCAT FROM BAPIP0006 INTO @DATA(ld_scndaddressline).
 
"SELECT single ORT01 FROM BAPIP0006 INTO @DATA(ld_city).
 
"SELECT single SEQNR FROM BAPIP0006 INTO @DATA(ld_recordnumber).
 
"SELECT single ORT02 FROM BAPIP0006 INTO @DATA(ld_district).
 


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!