SAP ADDR_READ_INVALID_CHECKSTATUS Function Module for
ADDR_READ_INVALID_CHECKSTATUS is a standard addr read invalid checkstatus 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 read invalid checkstatus FM, simply by entering the name ADDR_READ_INVALID_CHECKSTATUS into the relevant SAP transaction such as SE37 or SE38.
Function Group: SZAP
Program Name: SAPLSZAP
Main Program: SAPLSZAP
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ADDR_READ_INVALID_CHECKSTATUS 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_READ_INVALID_CHECKSTATUS'".
EXPORTING
* READ_INVALID = 'X' "
* READ_VALID = ' ' "
* READ_NOT_CHECKED = ' ' "
TABLES
* ADDRESS_GROUPS = "
* ADDRESS_SELECTION = "
* INVALID_ADDRESSES = "
* VALID_ADDRESSES = "
* NOT_CHECKED_ADDRESSES = "
EXCEPTIONS
PARAMETER_ERROR = 1 INTERNAL_ERROR = 2
IMPORTING Parameters details for ADDR_READ_INVALID_CHECKSTATUS
READ_INVALID -
Data type: SZAD_FIELD-FLAGDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
READ_VALID -
Data type: SZAD_FIELD-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
READ_NOT_CHECKED -
Data type: SZAD_FIELD-FLAGDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ADDR_READ_INVALID_CHECKSTATUS
ADDRESS_GROUPS -
Data type: ADAGROUPSOptional: Yes
Call by Reference: No ( called with pass by value option)
ADDRESS_SELECTION -
Data type: ADDR1_SELOptional: Yes
Call by Reference: No ( called with pass by value option)
INVALID_ADDRESSES -
Data type: ADDR_CHCKDOptional: Yes
Call by Reference: No ( called with pass by value option)
VALID_ADDRESSES -
Data type: ADDR_CHCKDOptional: Yes
Call by Reference: No ( called with pass by value option)
NOT_CHECKED_ADDRESSES -
Data type: ADDR_CHCKDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
PARAMETER_ERROR - Incorrect parameter values
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR - Serious internal error (MESSAGE A...)
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ADDR_READ_INVALID_CHECKSTATUS 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_read_invalid | TYPE SZAD_FIELD-FLAG, " 'X' | |||
| lt_address_groups | TYPE STANDARD TABLE OF ADAGROUPS, " | |||
| lv_parameter_error | TYPE ADAGROUPS, " | |||
| lv_read_valid | TYPE SZAD_FIELD-FLAG, " SPACE | |||
| lv_internal_error | TYPE SZAD_FIELD, " | |||
| lt_address_selection | TYPE STANDARD TABLE OF ADDR1_SEL, " | |||
| lv_read_not_checked | TYPE SZAD_FIELD-FLAG, " SPACE | |||
| lt_invalid_addresses | TYPE STANDARD TABLE OF ADDR_CHCKD, " | |||
| lt_valid_addresses | TYPE STANDARD TABLE OF ADDR_CHCKD, " | |||
| lt_not_checked_addresses | TYPE STANDARD TABLE OF ADDR_CHCKD. " |
|   CALL FUNCTION 'ADDR_READ_INVALID_CHECKSTATUS' " |
| EXPORTING | ||
| READ_INVALID | = lv_read_invalid | |
| READ_VALID | = lv_read_valid | |
| READ_NOT_CHECKED | = lv_read_not_checked | |
| TABLES | ||
| ADDRESS_GROUPS | = lt_address_groups | |
| ADDRESS_SELECTION | = lt_address_selection | |
| INVALID_ADDRESSES | = lt_invalid_addresses | |
| VALID_ADDRESSES | = lt_valid_addresses | |
| NOT_CHECKED_ADDRESSES | = lt_not_checked_addresses | |
| EXCEPTIONS | ||
| PARAMETER_ERROR = 1 | ||
| INTERNAL_ERROR = 2 | ||
| . " ADDR_READ_INVALID_CHECKSTATUS | ||
ABAP code using 7.40 inline data declarations to call FM ADDR_READ_INVALID_CHECKSTATUS
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 FLAG FROM SZAD_FIELD INTO @DATA(ld_read_invalid). | ||||
| DATA(ld_read_invalid) | = 'X'. | |||
| "SELECT single FLAG FROM SZAD_FIELD INTO @DATA(ld_read_valid). | ||||
| DATA(ld_read_valid) | = ' '. | |||
| "SELECT single FLAG FROM SZAD_FIELD INTO @DATA(ld_read_not_checked). | ||||
| DATA(ld_read_not_checked) | = ' '. | |||
Search for further information about these or an SAP related objects