SAP GET_NEXT_ANEP_SUM Function Module for Read line items for a control total
GET_NEXT_ANEP_SUM is a standard get next anep sum SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read line items for a control total 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 get next anep sum FM, simply by entering the name GET_NEXT_ANEP_SUM into the relevant SAP transaction such as SE37 or SE38.
Function Group: ABRA
Program Name: SAPLABRA
Main Program: SAPLABRA
Appliation area: A
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_NEXT_ANEP_SUM 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 'GET_NEXT_ANEP_SUM'"Read line items for a control total.
TABLES
T_ANEP = "Table of Asset Areas
T_ANEA = "
EXCEPTIONS
NO_RECORDS_FOUND = 1
TABLES Parameters details for GET_NEXT_ANEP_SUM
T_ANEP - Table of Asset Areas
Data type: ANEPOptional: No
Call by Reference: No ( called with pass by value option)
T_ANEA -
Data type: ANEAOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_RECORDS_FOUND - No records found
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for GET_NEXT_ANEP_SUM 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_t_anep | TYPE STANDARD TABLE OF ANEP, " | |||
| lv_no_records_found | TYPE ANEP, " | |||
| lt_t_anea | TYPE STANDARD TABLE OF ANEA. " |
|   CALL FUNCTION 'GET_NEXT_ANEP_SUM' "Read line items for a control total |
| TABLES | ||
| T_ANEP | = lt_t_anep | |
| T_ANEA | = lt_t_anea | |
| EXCEPTIONS | ||
| NO_RECORDS_FOUND = 1 | ||
| . " GET_NEXT_ANEP_SUM | ||
ABAP code using 7.40 inline data declarations to call FM GET_NEXT_ANEP_SUM
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