SAP ECRM_READ_CUSTOMIZINGTABLES Function Module for









ECRM_READ_CUSTOMIZINGTABLES is a standard ecrm read customizingtables 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 ecrm read customizingtables FM, simply by entering the name ECRM_READ_CUSTOMIZINGTABLES into the relevant SAP transaction such as SE37 or SE38.

Function Group: ECRM_DOWNLOAD_TO_CUSTOM
Program Name: SAPLECRM_DOWNLOAD_TO_CUSTOM
Main Program: SAPLECRM_DOWNLOAD_TO_CUSTOM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function ECRM_READ_CUSTOMIZINGTABLES 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 'ECRM_READ_CUSTOMIZINGTABLES'"
EXPORTING
* X_DIVISION = "
* X_DIVISIONTYP = "
* X_CONSUMTYP = "
* X_PODTYP = "
* X_GRIDLEVELTYPE = "
* X_VOLTAGELEVEL = "

TABLES
* YT_TSPA = "
* YT_TE369 = "
* YT_TE369T = "
* YT_TSPAT = "
* YT_TESPT = "
* YT_TE102 = "
* YT_TE102T = "
* YT_EUITYPE = "
* YT_EUITYPET = "
* YT_EGRIDLT = "
* YT_EGRIDLTT = "

EXCEPTIONS
SELECTION_FAILED = 1
.



IMPORTING Parameters details for ECRM_READ_CUSTOMIZINGTABLES

X_DIVISION -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_DIVISIONTYP -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_CONSUMTYP -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_PODTYP -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_GRIDLEVELTYPE -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

X_VOLTAGELEVEL -

Data type: FLAG
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for ECRM_READ_CUSTOMIZINGTABLES

YT_TSPA -

Data type: TSPA
Optional: Yes
Call by Reference: Yes

YT_TE369 -

Data type: TE369
Optional: Yes
Call by Reference: Yes

YT_TE369T -

Data type: TE369T
Optional: Yes
Call by Reference: Yes

YT_TSPAT -

Data type: TSPAT
Optional: Yes
Call by Reference: Yes

YT_TESPT -

Data type: TESPT
Optional: Yes
Call by Reference: Yes

YT_TE102 -

Data type: TE102
Optional: Yes
Call by Reference: Yes

YT_TE102T -

Data type: TE102T
Optional: Yes
Call by Reference: Yes

YT_EUITYPE -

Data type: EUITYPE
Optional: Yes
Call by Reference: Yes

YT_EUITYPET -

Data type: EUITYPET
Optional: Yes
Call by Reference: Yes

YT_EGRIDLT -

Data type: ECRM_GRID_LEVEL_TYPE_TRANSFER
Optional: Yes
Call by Reference: Yes

YT_EGRIDLTT -

Data type: EGRIDLTT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

SELECTION_FAILED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for ECRM_READ_CUSTOMIZINGTABLES 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_yt_tspa  TYPE STANDARD TABLE OF TSPA, "   
lv_x_division  TYPE FLAG, "   
lv_selection_failed  TYPE FLAG, "   
lt_yt_te369  TYPE STANDARD TABLE OF TE369, "   
lt_yt_te369t  TYPE STANDARD TABLE OF TE369T, "   
lt_yt_tspat  TYPE STANDARD TABLE OF TSPAT, "   
lv_x_divisiontyp  TYPE FLAG, "   
lt_yt_tespt  TYPE STANDARD TABLE OF TESPT, "   
lv_x_consumtyp  TYPE FLAG, "   
lv_x_podtyp  TYPE FLAG, "   
lt_yt_te102  TYPE STANDARD TABLE OF TE102, "   
lt_yt_te102t  TYPE STANDARD TABLE OF TE102T, "   
lv_x_gridleveltype  TYPE FLAG, "   
lt_yt_euitype  TYPE STANDARD TABLE OF EUITYPE, "   
lv_x_voltagelevel  TYPE FLAG, "   
lt_yt_euitypet  TYPE STANDARD TABLE OF EUITYPET, "   
lt_yt_egridlt  TYPE STANDARD TABLE OF ECRM_GRID_LEVEL_TYPE_TRANSFER, "   
lt_yt_egridltt  TYPE STANDARD TABLE OF EGRIDLTT. "   

  CALL FUNCTION 'ECRM_READ_CUSTOMIZINGTABLES'  "
    EXPORTING
         X_DIVISION = lv_x_division
         X_DIVISIONTYP = lv_x_divisiontyp
         X_CONSUMTYP = lv_x_consumtyp
         X_PODTYP = lv_x_podtyp
         X_GRIDLEVELTYPE = lv_x_gridleveltype
         X_VOLTAGELEVEL = lv_x_voltagelevel
    TABLES
         YT_TSPA = lt_yt_tspa
         YT_TE369 = lt_yt_te369
         YT_TE369T = lt_yt_te369t
         YT_TSPAT = lt_yt_tspat
         YT_TESPT = lt_yt_tespt
         YT_TE102 = lt_yt_te102
         YT_TE102T = lt_yt_te102t
         YT_EUITYPE = lt_yt_euitype
         YT_EUITYPET = lt_yt_euitypet
         YT_EGRIDLT = lt_yt_egridlt
         YT_EGRIDLTT = lt_yt_egridltt
    EXCEPTIONS
        SELECTION_FAILED = 1
. " ECRM_READ_CUSTOMIZINGTABLES




ABAP code using 7.40 inline data declarations to call FM ECRM_READ_CUSTOMIZINGTABLES

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!