SAP ADDR_VERSION_DELETE_CHECK Function Module for









ADDR_VERSION_DELETE_CHECK is a standard addr version delete check 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 addr version delete check FM, simply by entering the name ADDR_VERSION_DELETE_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function ADDR_VERSION_DELETE_CHECK 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 'ADDR_VERSION_DELETE_CHECK'"
EXPORTING
* ADDRESS_HANDLE = ' ' "
* ADDRESS_NUMBER = ' ' "
* DATE_FROM = '00010101' "
NATION = "
* BLK_EXCPT = "

IMPORTING
RETURNCODE = "

TABLES
* ERROR_TABLE = "

EXCEPTIONS
ADDRESS_NOT_EXIST = 1 PARAMETER_ERROR = 2 VERSION_NOT_EXIST = 3 INTERNAL_ERROR = 4 ADDRESS_BLOCKED = 5
.



IMPORTING Parameters details for ADDR_VERSION_DELETE_CHECK

ADDRESS_HANDLE -

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

ADDRESS_NUMBER -

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

DATE_FROM -

Data type: ADCP-DATE_FROM
Default: '00010101'
Optional: Yes
Call by Reference: No ( called with pass by value option)

NATION -

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

BLK_EXCPT -

Data type: AD_BLKFLAG
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ADDR_VERSION_DELETE_CHECK

RETURNCODE -

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

TABLES Parameters details for ADDR_VERSION_DELETE_CHECK

ERROR_TABLE -

Data type: ADDR_ERROR
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

ADDRESS_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

VERSION_NOT_EXIST -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

ADDRESS_BLOCKED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ADDR_VERSION_DELETE_CHECK 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_returncode  TYPE SZAD_FIELD-RETURNCODE, "   
lt_error_table  TYPE STANDARD TABLE OF ADDR_ERROR, "   
lv_address_handle  TYPE SZAD_FIELD-HANDLE, "   SPACE
lv_address_not_exist  TYPE SZAD_FIELD, "   
lv_address_number  TYPE ADCP-ADDRNUMBER, "   SPACE
lv_parameter_error  TYPE ADCP, "   
lv_date_from  TYPE ADCP-DATE_FROM, "   '00010101'
lv_version_not_exist  TYPE ADCP, "   
lv_nation  TYPE ADCP-NATION, "   
lv_internal_error  TYPE ADCP, "   
lv_blk_excpt  TYPE AD_BLKFLAG, "   
lv_address_blocked  TYPE AD_BLKFLAG. "   

  CALL FUNCTION 'ADDR_VERSION_DELETE_CHECK'  "
    EXPORTING
         ADDRESS_HANDLE = lv_address_handle
         ADDRESS_NUMBER = lv_address_number
         DATE_FROM = lv_date_from
         NATION = lv_nation
         BLK_EXCPT = lv_blk_excpt
    IMPORTING
         RETURNCODE = lv_returncode
    TABLES
         ERROR_TABLE = lt_error_table
    EXCEPTIONS
        ADDRESS_NOT_EXIST = 1
        PARAMETER_ERROR = 2
        VERSION_NOT_EXIST = 3
        INTERNAL_ERROR = 4
        ADDRESS_BLOCKED = 5
. " ADDR_VERSION_DELETE_CHECK




ABAP code using 7.40 inline data declarations to call FM ADDR_VERSION_DELETE_CHECK

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 RETURNCODE FROM SZAD_FIELD INTO @DATA(ld_returncode).
 
 
"SELECT single HANDLE FROM SZAD_FIELD INTO @DATA(ld_address_handle).
DATA(ld_address_handle) = ' '.
 
 
"SELECT single ADDRNUMBER FROM ADCP INTO @DATA(ld_address_number).
DATA(ld_address_number) = ' '.
 
 
"SELECT single DATE_FROM FROM ADCP INTO @DATA(ld_date_from).
DATA(ld_date_from) = '00010101'.
 
 
"SELECT single NATION FROM ADCP INTO @DATA(ld_nation).
 
 
 
 


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!