SAP ADDR_GET_NEXT_COMM_TYPE Function Module for

Search SAP Function Modules

ADDR_GET_NEXT_COMM_TYPE is a standard addr get next comm type 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 get next comm type FM, simply by entering the name ADDR_GET_NEXT_COMM_TYPE into the relevant SAP transaction such as SE37 or SE38.

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

Function ADDR_GET_NEXT_COMM_TYPE 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_GET_NEXT_COMM_TYPE'"
  EXPORTING
*  STRATEGY =  "
*  ADDRESS_TYPE =  "Address type: 1,2,3 or ' '(default)
   ADDRESS_NUMBER =  "Address number (data are read directly)
*  PERSON_NUMBER =  "Person number (data are read directly)
*  IV_SEARCH_TIME = ' ' "

 IMPORTING
   COMM_TYPE =  "Communication Type (Key)
   COMM_VALUES =  "Communication Data
   UNDELIVER =  "Transfer Structure for Reason for Non-Delivery

TABLES
*  STRATEGY_TABLE =  "Communication strategy

EXCEPTIONS
   ADDRESS_NOT_EXIST = 1    PERSON_NOT_EXIST = 2    NO_COMM_TYPE_FOUND = 3    INTERNAL_ERROR = 4    PARAMETER_ERROR = 5 

.

IMPORTING Parameters details for ADDR_GET_NEXT_COMM_TYPE

STRATEGY -

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

ADDRESS_TYPE - Address type: 1,2,3 or ' '(default)

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

ADDRESS_NUMBER - Address number (data are read directly)

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

PERSON_NUMBER - Person number (data are read directly)

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

IV_SEARCH_TIME -

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

EXPORTING Parameters details for ADDR_GET_NEXT_COMM_TYPE

COMM_TYPE - Communication Type (Key)

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

COMM_VALUES - Communication Data

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

UNDELIVER - Transfer Structure for Reason for Non-Delivery

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

TABLES Parameters details for ADDR_GET_NEXT_COMM_TYPE

STRATEGY_TABLE - Communication strategy

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

EXCEPTIONS details

ADDRESS_NOT_EXIST - Address does not exist

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

PERSON_NOT_EXIST -

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

NO_COMM_TYPE_FOUND -

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

INTERNAL_ERROR -

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

PARAMETER_ERROR - Incorrect parameter values

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

Copy and paste ABAP code example for ADDR_GET_NEXT_COMM_TYPE 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.

ABAP code using 7.40 inline data declarations to call FM ADDR_GET_NEXT_COMM_TYPE

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.

Search for further information about these or an SAP related objects