SAP EXIT_SAPLEACS_001 Function Module for IS-U: Individual Display of Historical Consumption Values
EXIT_SAPLEACS_001 is a standard exit sapleacs 001 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for IS-U: Individual Display of Historical Consumption Values 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 exit sapleacs 001 FM, simply by entering the name EXIT_SAPLEACS_001 into the relevant SAP transaction such as SE37 or SE38.
Function Group: XEACS
Program Name: SAPLXEACS
Main Program: SAPLXEACS
Appliation area: E
Release date: 22-Oct-1998
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EXIT_SAPLEACS_001 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 'EXIT_SAPLEACS_001'"IS-U: Individual Display of Historical Consumption Values.
EXPORTING
ANLAGE = "Installation Whose Values are Being Searched for
* MODNUMBER = "Number of Information Module
TABLES
XT_CONT = "Table for Container Values
YT_COLUMNS = "Structure for Fields to Displayed in FO
YT_ROWS = "Contents of Fields to be Displayed in FO
* YT_REFTABLE = "Table of References
Related Function Modules
Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.ISU_ANALYSE_DISPLAY_METHOD INTERNAL: Analysis of Method To Be Displayed
ISU_CONS_OVERVIEW_REMOTE Consumption Overview: Remote
ISU_CONS_OVERVIEW_REMOTE_2 Display Consumption Overview in IC WebClient
ISU_GET_ALL_HISTORY INTERNAL: Search for All Historical Values of an Operand
ISU_GET_ERCHV_HISTORY INTERNAL: Output of ERCHV
ISU_HISTORY_CONSUMPTION INTERNAL: Historical Rates and Consumption Values of an Installation
ISU_RATES_AND_CONSUMPTION INTERNAL: Rates and Consumption Values of an Installation
ISU_SHOW_ALL_HISTORY INTERNAL: Display All Historical Values of Operand
ISU_SHOW_ALL_HISTORY_TMP INTERNAL: Display All Historical Values of Operand
ISU_SHOW_CONSUMPTION_BILL INTERNAL: Action Module for Action on Table Control Field (Consumption)
IMPORTING Parameters details for EXIT_SAPLEACS_001
ANLAGE - Installation Whose Values are Being Searched for
Data type: EANL-ANLAGEOptional: No
Call by Reference: No ( called with pass by value option)
MODNUMBER - Number of Information Module
Data type: MODNUM_KKOptional: Yes
Call by Reference: Yes
TABLES Parameters details for EXIT_SAPLEACS_001
XT_CONT - Table for Container Values
Data type: SWCONTOptional: No
Call by Reference: No ( called with pass by value option)
YT_COLUMNS - Structure for Fields to Displayed in FO
Data type: EWICOLOptional: No
Call by Reference: No ( called with pass by value option)
YT_ROWS - Contents of Fields to be Displayed in FO
Data type: EWIROWOptional: No
Call by Reference: No ( called with pass by value option)
YT_REFTABLE - Table of References
Data type: FKKREFTABLEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for EXIT_SAPLEACS_001 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_anlage | TYPE EANL-ANLAGE, " | |||
| lt_xt_cont | TYPE STANDARD TABLE OF SWCONT, " | |||
| lv_modnumber | TYPE MODNUM_KK, " | |||
| lt_yt_columns | TYPE STANDARD TABLE OF EWICOL, " | |||
| lt_yt_rows | TYPE STANDARD TABLE OF EWIROW, " | |||
| lt_yt_reftable | TYPE STANDARD TABLE OF FKKREFTABLE. " |
|   CALL FUNCTION 'EXIT_SAPLEACS_001' "IS-U: Individual Display of Historical Consumption Values |
| EXPORTING | ||
| ANLAGE | = lv_anlage | |
| MODNUMBER | = lv_modnumber | |
| TABLES | ||
| XT_CONT | = lt_xt_cont | |
| YT_COLUMNS | = lt_yt_columns | |
| YT_ROWS | = lt_yt_rows | |
| YT_REFTABLE | = lt_yt_reftable | |
| . " EXIT_SAPLEACS_001 | ||
ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLEACS_001
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 ANLAGE FROM EANL INTO @DATA(ld_anlage). | ||||
Search for further information about these or an SAP related objects