SAP CUSTOMER_GET_NEXT_SEGMENTS Function Module for NOTRANSL: Nächste Segemente für Archivierungsvormerkung ermitteln
CUSTOMER_GET_NEXT_SEGMENTS is a standard customer get next segments SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Nächste Segemente für Archivierungsvormerkung ermitteln 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 get next segments FM, simply by entering the name CUSTOMER_GET_NEXT_SEGMENTS into the relevant SAP transaction such as SE37 or SE38.
Function Group: WR15
Program Name: SAPLWR15
Main Program: SAPLWR15
Appliation area: W
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUSTOMER_GET_NEXT_SEGMENTS 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_GET_NEXT_SEGMENTS'"NOTRANSL: Nächste Segemente für Archivierungsvormerkung ermitteln.
IMPORTING
O_BUKRS = "
O_VKORG = "
O_VTWEG = "
O_SPART = "
EXPORTING Parameters details for CUSTOMER_GET_NEXT_SEGMENTS
O_BUKRS -
Data type: KNB1-BUKRSOptional: No
Call by Reference: No ( called with pass by value option)
O_VKORG -
Data type: KNVV-VKORGOptional: No
Call by Reference: No ( called with pass by value option)
O_VTWEG -
Data type: KNVV-VTWEGOptional: No
Call by Reference: No ( called with pass by value option)
O_SPART -
Data type: KNVV-SPARTOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CUSTOMER_GET_NEXT_SEGMENTS 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_o_bukrs | TYPE KNB1-BUKRS, " | |||
| lv_o_vkorg | TYPE KNVV-VKORG, " | |||
| lv_o_vtweg | TYPE KNVV-VTWEG, " | |||
| lv_o_spart | TYPE KNVV-SPART. " |
|   CALL FUNCTION 'CUSTOMER_GET_NEXT_SEGMENTS' "NOTRANSL: Nächste Segemente für Archivierungsvormerkung ermitteln |
| IMPORTING | ||
| O_BUKRS | = lv_o_bukrs | |
| O_VKORG | = lv_o_vkorg | |
| O_VTWEG | = lv_o_vtweg | |
| O_SPART | = lv_o_spart | |
| . " CUSTOMER_GET_NEXT_SEGMENTS | ||
ABAP code using 7.40 inline data declarations to call FM CUSTOMER_GET_NEXT_SEGMENTS
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 BUKRS FROM KNB1 INTO @DATA(ld_o_bukrs). | ||||
| "SELECT single VKORG FROM KNVV INTO @DATA(ld_o_vkorg). | ||||
| "SELECT single VTWEG FROM KNVV INTO @DATA(ld_o_vtweg). | ||||
| "SELECT single SPART FROM KNVV INTO @DATA(ld_o_spart). | ||||
Search for further information about these or an SAP related objects