SAP BAPI_ADDRESSEMP_APPROVE Function Module for Unlock employee address
BAPI_ADDRESSEMP_APPROVE is a standard bapi addressemp approve SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Unlock employee address 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 addressemp approve FM, simply by entering the name BAPI_ADDRESSEMP_APPROVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: PADR
Program Name: SAPLPADR
Main Program: SAPLPADR
Appliation area: P
Release date: 16-Sep-1997
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function BAPI_ADDRESSEMP_APPROVE 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_ADDRESSEMP_APPROVE'"Unlock employee address.
EXPORTING
EMPLOYEENUMBER = "Personnel number
SUBTYPE = "Subtype
OBJECTID = "Object identification
LOCKINDICATOR = "Lock indicator for HR master record
VALIDITYBEGIN = "Valid from date
VALIDITYEND = "Valid To Date
RECORDNUMBER = "Number of Infotype Record
* NOCOMMIT = "COMMIT control at BAPI interface
IMPORTING
RETURN = "Structure for return code
IMPORTING Parameters details for BAPI_ADDRESSEMP_APPROVE
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 - Valid To 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)
NOCOMMIT - COMMIT control at BAPI interface
Data type: BAPI_STAND-NO_COMMITOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BAPI_ADDRESSEMP_APPROVE
RETURN - Structure for return code
Data type: BAPIRETURN1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BAPI_ADDRESSEMP_APPROVE 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_subtype | TYPE BAPIP0006-SUBTY, " | |||
lv_objectid | TYPE BAPIP0006-OBJPS, " | |||
lv_lockindicator | TYPE BAPIP0006-SPRPS, " | |||
lv_validitybegin | TYPE BAPIP0006-BEGDA, " | |||
lv_validityend | TYPE BAPIP0006-ENDDA, " | |||
lv_recordnumber | TYPE BAPIP0006-SEQNR, " | |||
lv_nocommit | TYPE BAPI_STAND-NO_COMMIT. " |
  CALL FUNCTION 'BAPI_ADDRESSEMP_APPROVE' "Unlock employee address |
EXPORTING | ||
EMPLOYEENUMBER | = lv_employeenumber | |
SUBTYPE | = lv_subtype | |
OBJECTID | = lv_objectid | |
LOCKINDICATOR | = lv_lockindicator | |
VALIDITYBEGIN | = lv_validitybegin | |
VALIDITYEND | = lv_validityend | |
RECORDNUMBER | = lv_recordnumber | |
NOCOMMIT | = lv_nocommit | |
IMPORTING | ||
RETURN | = lv_return | |
. " BAPI_ADDRESSEMP_APPROVE |
ABAP code using 7.40 inline data declarations to call FM BAPI_ADDRESSEMP_APPROVE
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 SUBTY FROM BAPIP0006 INTO @DATA(ld_subtype). | ||||
"SELECT single OBJPS FROM BAPIP0006 INTO @DATA(ld_objectid). | ||||
"SELECT single SPRPS FROM BAPIP0006 INTO @DATA(ld_lockindicator). | ||||
"SELECT single BEGDA FROM BAPIP0006 INTO @DATA(ld_validitybegin). | ||||
"SELECT single ENDDA FROM BAPIP0006 INTO @DATA(ld_validityend). | ||||
"SELECT single SEQNR FROM BAPIP0006 INTO @DATA(ld_recordnumber). | ||||
"SELECT single NO_COMMIT FROM BAPI_STAND INTO @DATA(ld_nocommit). | ||||
Search for further information about these or an SAP related objects