SAP CUSTOMER_SELECT_NEXT_ID Function Module for Module for Block Reading of Customer Master Key
CUSTOMER_SELECT_NEXT_ID is a standard customer select next id SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Module for Block Reading of Customer Master Key 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 customer select next id FM, simply by entering the name CUSTOMER_SELECT_NEXT_ID into the relevant SAP transaction such as SE37 or SE38.
Function Group: V0SE
Program Name: SAPLV0SE
Main Program: SAPLV0SE
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUSTOMER_SELECT_NEXT_ID 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 'CUSTOMER_SELECT_NEXT_ID'"Module for Block Reading of Customer Master Key.
IMPORTING
LASTBLOCK = "DE-EN-LANG-SWITCH-NO-TRANSLATION
COMPLETE_RECORD_NUMBER = "DE-EN-LANG-SWITCH-NO-TRANSLATION
COMPLETE_BLOCK_NUMBER = "DE-EN-LANG-SWITCH-NO-TRANSLATION
TABLES
OUT_ID_TAB = "DE-EN-LANG-SWITCH-NO-TRANSLATION
EXCEPTIONS
FUNCTION_MISSING = 1
EXPORTING Parameters details for CUSTOMER_SELECT_NEXT_ID
LASTBLOCK - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SEL_FIELDS-READ_FLAGOptional: No
Call by Reference: No ( called with pass by value option)
COMPLETE_RECORD_NUMBER - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SEL_FIELDS-MAX_KUNNROptional: No
Call by Reference: No ( called with pass by value option)
COMPLETE_BLOCK_NUMBER - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: SEL_FIELDS-MAX_KUNNROptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CUSTOMER_SELECT_NEXT_ID
OUT_ID_TAB - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type: KUND01Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
FUNCTION_MISSING - DE-EN-LANG-SWITCH-NO-TRANSLATION
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUSTOMER_SELECT_NEXT_ID 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_lastblock | TYPE SEL_FIELDS-READ_FLAG, " | |||
| lt_out_id_tab | TYPE STANDARD TABLE OF KUND01, " | |||
| lv_function_missing | TYPE KUND01, " | |||
| lv_complete_record_number | TYPE SEL_FIELDS-MAX_KUNNR, " | |||
| lv_complete_block_number | TYPE SEL_FIELDS-MAX_KUNNR. " |
|   CALL FUNCTION 'CUSTOMER_SELECT_NEXT_ID' "Module for Block Reading of Customer Master Key |
| IMPORTING | ||
| LASTBLOCK | = lv_lastblock | |
| COMPLETE_RECORD_NUMBER | = lv_complete_record_number | |
| COMPLETE_BLOCK_NUMBER | = lv_complete_block_number | |
| TABLES | ||
| OUT_ID_TAB | = lt_out_id_tab | |
| EXCEPTIONS | ||
| FUNCTION_MISSING = 1 | ||
| . " CUSTOMER_SELECT_NEXT_ID | ||
ABAP code using 7.40 inline data declarations to call FM CUSTOMER_SELECT_NEXT_ID
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 READ_FLAG FROM SEL_FIELDS INTO @DATA(ld_lastblock). | ||||
| "SELECT single MAX_KUNNR FROM SEL_FIELDS INTO @DATA(ld_complete_record_number). | ||||
| "SELECT single MAX_KUNNR FROM SEL_FIELDS INTO @DATA(ld_complete_block_number). | ||||
Search for further information about these or an SAP related objects