SAP ADDR_COMM_DATA_VALIDITY_CHANGE Function Module for









ADDR_COMM_DATA_VALIDITY_CHANGE is a standard addr comm data validity change 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 comm data validity change FM, simply by entering the name ADDR_COMM_DATA_VALIDITY_CHANGE into the relevant SAP transaction such as SE37 or SE38.

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



Function ADDR_COMM_DATA_VALIDITY_CHANGE 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_COMM_DATA_VALIDITY_CHANGE'"
EXPORTING
* IV_ADDRESS_TYPE = '1' "Address type (1=Organization, 2=Person, 3=Contact person)
* IV_ADDRESS_HANDLE = ' ' "Handle for Creating Addresses/Persons (Bus. Addr. Services)
* IV_ADDRESS_NUMBER = ' ' "Address Number
* IV_PERSON_HANDLE = ' ' "Handle for Creating Addresses/Persons (Bus. Addr. Services)
* IV_PERSON_NUMBER = ' ' "Person Number
* IV_VALID_FROM_OLD = ' ' "Communication Data: Valid From (JJJJMMTTSSMMSS)
* IV_VALID_TO_OLD = ' ' "Communication Data: Valid Until (JJJJMMTTSSMMSS)
* IV_VALID_FROM_NEW = ' ' "Communication Data: Valid From (JJJJMMTTSSMMSS)
* IV_VALID_TO_NEW = ' ' "Communication Data: Valid Until (JJJJMMTTSSMMSS)

IMPORTING
EV_RETURNCODE = "Return code: Address data check error (E,W,I, ' ')

TABLES
ET_ERROR = "Transfer structure for error messages in the fn.gr. SZA0

EXCEPTIONS
ADDRESS_NOT_EXIST = 1 PARAMETER_ERROR = 2 INTERNAL_ERROR = 3
.



IMPORTING Parameters details for ADDR_COMM_DATA_VALIDITY_CHANGE

IV_ADDRESS_TYPE - Address type (1=Organization, 2=Person, 3=Contact person)

Data type: AD_ADRTYPE
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_ADDRESS_HANDLE - Handle for Creating Addresses/Persons (Bus. Addr. Services)

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

IV_ADDRESS_NUMBER - Address Number

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

IV_PERSON_HANDLE - Handle for Creating Addresses/Persons (Bus. Addr. Services)

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

IV_PERSON_NUMBER - Person Number

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

IV_VALID_FROM_OLD - Communication Data: Valid From (JJJJMMTTSSMMSS)

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

IV_VALID_TO_OLD - Communication Data: Valid Until (JJJJMMTTSSMMSS)

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

IV_VALID_FROM_NEW - Communication Data: Valid From (JJJJMMTTSSMMSS)

Data type: AD_VALFROM
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

IV_VALID_TO_NEW - Communication Data: Valid Until (JJJJMMTTSSMMSS)

Data type: AD_VALTO
Default: SPACE
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for ADDR_COMM_DATA_VALIDITY_CHANGE

EV_RETURNCODE - Return code: Address data check error (E,W,I, SPACE)

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

TABLES Parameters details for ADDR_COMM_DATA_VALIDITY_CHANGE

ET_ERROR - Transfer structure for error messages in the fn.gr. SZA0

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

EXCEPTIONS details

ADDRESS_NOT_EXIST - Address specified does not exist

Data type:
Optional: No
Call by Reference: Yes

PARAMETER_ERROR -

Data type:
Optional: No
Call by Reference: Yes

INTERNAL_ERROR - Serious internal error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ADDR_COMM_DATA_VALIDITY_CHANGE 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:
lt_et_error  TYPE STANDARD TABLE OF ADDR_ERROR, "   
lv_ev_returncode  TYPE AD_RETCODE, "   
lv_iv_address_type  TYPE AD_ADRTYPE, "   '1'
lv_address_not_exist  TYPE AD_ADRTYPE, "   
lv_parameter_error  TYPE AD_ADRTYPE, "   
lv_iv_address_handle  TYPE AD_HANDLE, "   SPACE
lv_internal_error  TYPE AD_HANDLE, "   
lv_iv_address_number  TYPE AD_ADDRNUM, "   SPACE
lv_iv_person_handle  TYPE AD_HANDLE, "   SPACE
lv_iv_person_number  TYPE AD_PERSNUM, "   SPACE
lv_iv_valid_from_old  TYPE AD_VALFROM, "   SPACE
lv_iv_valid_to_old  TYPE AD_VALTO, "   SPACE
lv_iv_valid_from_new  TYPE AD_VALFROM, "   SPACE
lv_iv_valid_to_new  TYPE AD_VALTO. "   SPACE

  CALL FUNCTION 'ADDR_COMM_DATA_VALIDITY_CHANGE'  "
    EXPORTING
         IV_ADDRESS_TYPE = lv_iv_address_type
         IV_ADDRESS_HANDLE = lv_iv_address_handle
         IV_ADDRESS_NUMBER = lv_iv_address_number
         IV_PERSON_HANDLE = lv_iv_person_handle
         IV_PERSON_NUMBER = lv_iv_person_number
         IV_VALID_FROM_OLD = lv_iv_valid_from_old
         IV_VALID_TO_OLD = lv_iv_valid_to_old
         IV_VALID_FROM_NEW = lv_iv_valid_from_new
         IV_VALID_TO_NEW = lv_iv_valid_to_new
    IMPORTING
         EV_RETURNCODE = lv_ev_returncode
    TABLES
         ET_ERROR = lt_et_error
    EXCEPTIONS
        ADDRESS_NOT_EXIST = 1
        PARAMETER_ERROR = 2
        INTERNAL_ERROR = 3
. " ADDR_COMM_DATA_VALIDITY_CHANGE




ABAP code using 7.40 inline data declarations to call FM ADDR_COMM_DATA_VALIDITY_CHANGE

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.

 
 
DATA(ld_iv_address_type) = '1'.
 
 
 
DATA(ld_iv_address_handle) = ' '.
 
 
DATA(ld_iv_address_number) = ' '.
 
DATA(ld_iv_person_handle) = ' '.
 
DATA(ld_iv_person_number) = ' '.
 
DATA(ld_iv_valid_from_old) = ' '.
 
DATA(ld_iv_valid_to_old) = ' '.
 
DATA(ld_iv_valid_from_new) = ' '.
 
DATA(ld_iv_valid_to_new) = ' '.
 


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!