SAP BAPI_ADDRESSEMPIE_REQUEST Function Module for Create locked employee address record
BAPI_ADDRESSEMPIE_REQUEST is a standard bapi addressempie 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 addressempie request FM, simply by entering the name BAPI_ADDRESSEMPIE_REQUEST into the relevant SAP transaction such as SE37 or SE38.
Function Group: PADR_IE
Program Name: SAPLPADR_IE
Main Program:
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_ADDRESSEMPIE_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_ADDRESSEMPIE_REQUEST'"Create locked employee address record.
EXPORTING
EMPLOYEENUMBER = "Personnel number
* POSTALCODECITY = "Postal code
* STATE = "Region
* COUNTRY = "Country key
* BUS_ROUTE = "Bus route
* COMPANY_APARTMENT = "Company-owned apartment
* DISTANCE = "Distance in kilometers
* DISTANCE2 = "Distance in kilometers
* TELEPHONENUMBER = "Telephone number
* COMMTYPE1 = "Communication type 1
* COMMNUMBER1 = "Communication number 1
VALIDITYBEGIN = "Valid from date
* COMMTYPE2 = "Communication type 2
* COMMNUMBER2 = "Communication number 2
* COMMTYPE3 = "Communication type 3
* COMMNUMBER3 = "Communication number 3
* COMMTYPE4 = "Communication type 4
* COMMNUMBER4 = "Communication number 4
* COMMTYPE5 = "Communication type 5
* COMMNUMBER5 = "Communication number 5
* COMMTYPE6 = "Communication type 6
* COMMNUMBER6 = "Communication number 6
VALIDITYEND = "Validity end date
* NOCOMMIT = "COMMIT control at BAPI interface
ADDRESSTYPE = "Subtype
* CONAME = "C/O name
* STREETANDHOUSENO = "House number and street
* SCNDADDRESSLINE = "2nd address line
* CITY = "City
* DISTRICT = "District
IMPORTING
RETURN = "Structure for Return Code
EMPLOYEENUMBER = "Personnel number
SUBTYPE = "Subtype
OBJECTID = "Object identification
LOCKINDICATOR = "Lock indicator for HR master record
VALIDITYBEGIN = "Valid from date
VALIDITYEND = "Validity end date
RECORDNUMBER = "Number of infotype record
IMPORTING Parameters details for BAPI_ADDRESSEMPIE_REQUEST
EMPLOYEENUMBER - Personnel number
Data type: BAPIP0006-PERNROptional: No
Call by Reference: No ( called with pass by value option)
POSTALCODECITY - Postal code
Data type: BAPIP0006-PSTLZOptional: Yes
Call by Reference: No ( called with pass by value option)
STATE - Region
Data type: BAPIP0006-STATEOptional: Yes
Call by Reference: No ( called with pass by value option)
COUNTRY - Country key
Data type: BAPIP0006-LAND1Optional: Yes
Call by Reference: No ( called with pass by value option)
BUS_ROUTE - Bus route
Data type: BAPIP0006-BUSRTOptional: Yes
Call by Reference: No ( called with pass by value option)
COMPANY_APARTMENT - Company-owned apartment
Data type: BAPIP0006-WKWNGOptional: Yes
Call by Reference: No ( called with pass by value option)
DISTANCE - Distance in kilometers
Data type: BAPIP0006-ENTKMOptional: Yes
Call by Reference: No ( called with pass by value option)
DISTANCE2 - Distance in kilometers
Data type: BAPIP0006-ENTK2Optional: Yes
Call by Reference: No ( called with pass by value option)
TELEPHONENUMBER - Telephone number
Data type: BAPIP0006-TELNROptional: Yes
Call by Reference: No ( called with pass by value option)
COMMTYPE1 - Communication type 1
Data type: BAPIP0006LIE-COMMTYPE1Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMNUMBER1 - Communication number 1
Data type: BAPIP0006LIE-COMMNUMBER1Optional: Yes
Call by Reference: No ( called with pass by value option)
VALIDITYBEGIN - Valid from date
Data type: BAPIP0006-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
COMMTYPE2 - Communication type 2
Data type: BAPIP0006LIE-COMMTYPE2Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMNUMBER2 - Communication number 2
Data type: BAPIP0006LIE-COMMNUMBER2Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMTYPE3 - Communication type 3
Data type: BAPIP0006LIE-COMMTYPE3Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMNUMBER3 - Communication number 3
Data type: BAPIP0006LIE-COMMNUMBER3Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMTYPE4 - Communication type 4
Data type: BAPIP0006LIE-COMMTYPE4Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMNUMBER4 - Communication number 4
Data type: BAPIP0006LIE-COMMNUMBER4Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMTYPE5 - Communication type 5
Data type: BAPIP0006LIE-COMMTYPE5Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMNUMBER5 - Communication number 5
Data type: BAPIP0006LIE-COMMNUMBER5Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMTYPE6 - Communication type 6
Data type: BAPIP0006LIE-COMMTYPE6Optional: Yes
Call by Reference: No ( called with pass by value option)
COMMNUMBER6 - Communication number 6
Data type: BAPIP0006LIE-COMMNUMBER6Optional: Yes
Call by Reference: No ( called with pass by value option)
VALIDITYEND - Validity end date
Data type: BAPIP0006-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
NOCOMMIT - COMMIT control at BAPI interface
Data type: BAPI_STAND-NO_COMMITOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESSTYPE - Subtype
Data type: BAPIP0006-SUBTYOptional: No
Call by Reference: No ( called with pass by value option)
CONAME - C/O name
Data type: BAPIP0006-NAME2Optional: Yes
Call by Reference: No ( called with pass by value option)
STREETANDHOUSENO - House number and street
Data type: BAPIP0006-STRASOptional: Yes
Call by Reference: No ( called with pass by value option)
SCNDADDRESSLINE - 2nd address line
Data type: BAPIP0006-LOCATOptional: Yes
Call by Reference: No ( called with pass by value option)
CITY - City
Data type: BAPIP0006-ORT01Optional: Yes
Call by Reference: No ( called with pass by value option)
DISTRICT - District
Data type: BAPIP0006-ORT02Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_ADDRESSEMPIE_REQUEST
RETURN - Structure for Return Code
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
EMPLOYEENUMBER - Personnel number
Data type: BAPIP0006-PERNROptional: No
Call by Reference: No ( called with pass by value option)
SUBTYPE - Subtype
Data type: BAPIP0006-SUBTYOptional: No
Call by Reference: No ( called with pass by value option)
OBJECTID - Object identification
Data type: BAPIP0006-OBJPSOptional: No
Call by Reference: No ( called with pass by value option)
LOCKINDICATOR - Lock indicator for HR master record
Data type: BAPIP0006-SPRPSOptional: No
Call by Reference: No ( called with pass by value option)
VALIDITYBEGIN - Valid from date
Data type: BAPIP0006-BEGDAOptional: No
Call by Reference: No ( called with pass by value option)
VALIDITYEND - Validity end date
Data type: BAPIP0006-ENDDAOptional: No
Call by Reference: No ( called with pass by value option)
RECORDNUMBER - Number of infotype record
Data type: BAPIP0006-SEQNROptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_ADDRESSEMPIE_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 BAPIP0006LIE-COMMTYPE1, " | |||
| lv_commnumber1 | TYPE BAPIP0006LIE-COMMNUMBER1, " | |||
| lv_validitybegin | TYPE BAPIP0006-BEGDA, " | |||
| lv_employeenumber | TYPE BAPIP0006-PERNR, " | |||
| lv_commtype2 | TYPE BAPIP0006LIE-COMMTYPE2, " | |||
| lv_commnumber2 | TYPE BAPIP0006LIE-COMMNUMBER2, " | |||
| lv_commtype3 | TYPE BAPIP0006LIE-COMMTYPE3, " | |||
| lv_commnumber3 | TYPE BAPIP0006LIE-COMMNUMBER3, " | |||
| lv_commtype4 | TYPE BAPIP0006LIE-COMMTYPE4, " | |||
| lv_commnumber4 | TYPE BAPIP0006LIE-COMMNUMBER4, " | |||
| lv_commtype5 | TYPE BAPIP0006LIE-COMMTYPE5, " | |||
| lv_commnumber5 | TYPE BAPIP0006LIE-COMMNUMBER5, " | |||
| lv_commtype6 | TYPE BAPIP0006LIE-COMMTYPE6, " | |||
| lv_commnumber6 | TYPE BAPIP0006LIE-COMMNUMBER6, " | |||
| lv_subtype | TYPE BAPIP0006-SUBTY, " | |||
| lv_validityend | TYPE BAPIP0006-ENDDA, " | |||
| 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_ADDRESSEMPIE_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 | |
| 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_ADDRESSEMPIE_REQUEST | ||
ABAP code using 7.40 inline data declarations to call FM BAPI_ADDRESSEMPIE_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 BAPIP0006LIE INTO @DATA(ld_commtype1). | ||||
| "SELECT single COMMNUMBER1 FROM BAPIP0006LIE 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 BAPIP0006LIE INTO @DATA(ld_commtype2). | ||||
| "SELECT single COMMNUMBER2 FROM BAPIP0006LIE INTO @DATA(ld_commnumber2). | ||||
| "SELECT single COMMTYPE3 FROM BAPIP0006LIE INTO @DATA(ld_commtype3). | ||||
| "SELECT single COMMNUMBER3 FROM BAPIP0006LIE INTO @DATA(ld_commnumber3). | ||||
| "SELECT single COMMTYPE4 FROM BAPIP0006LIE INTO @DATA(ld_commtype4). | ||||
| "SELECT single COMMNUMBER4 FROM BAPIP0006LIE INTO @DATA(ld_commnumber4). | ||||
| "SELECT single COMMTYPE5 FROM BAPIP0006LIE INTO @DATA(ld_commtype5). | ||||
| "SELECT single COMMNUMBER5 FROM BAPIP0006LIE INTO @DATA(ld_commnumber5). | ||||
| "SELECT single COMMTYPE6 FROM BAPIP0006LIE INTO @DATA(ld_commtype6). | ||||
| "SELECT single COMMNUMBER6 FROM BAPIP0006LIE INTO @DATA(ld_commnumber6). | ||||
| "SELECT single SUBTY FROM BAPIP0006 INTO @DATA(ld_subtype). | ||||
| "SELECT single ENDDA FROM BAPIP0006 INTO @DATA(ld_validityend). | ||||
| "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