SAP CRM_ISU_GRIDUSAGE_GET_DATA Function Module for Zugriff auf Netznutzungsdaten









CRM_ISU_GRIDUSAGE_GET_DATA is a standard crm isu gridusage get data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Zugriff auf Netznutzungsdaten 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 crm isu gridusage get data FM, simply by entering the name CRM_ISU_GRIDUSAGE_GET_DATA into the relevant SAP transaction such as SE37 or SE38.

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



Function CRM_ISU_GRIDUSAGE_GET_DATA 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 'CRM_ISU_GRIDUSAGE_GET_DATA'"Zugriff auf Netznutzungsdaten
EXPORTING
IV_ORDER_I_GUID = "Item GUID for a CRM Document
* IV_POD_GUID = "UUID in X form (binary)
* IV_LANGU = SY-LANGU "Language Key
* IV_FROM = "Grid Usage Start Date
* IV_TO = "End Date for Grid Usage

IMPORTING
ES_GRID_DATA = "Distribution Grid / Distributor Data
ET_GRIDUSAGE_DATA = "Table with Grid Usage Conditions

EXCEPTIONS
NO_GRID_ITEM_FOUND = 1 NO_PRICING_FOUND = 2 NOT_AVAILABLE = 3 ERROR_OCCURED = 4
.



IMPORTING Parameters details for CRM_ISU_GRIDUSAGE_GET_DATA

IV_ORDER_I_GUID - Item GUID for a CRM Document

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

IV_POD_GUID - UUID in X form (binary)

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

IV_LANGU - Language Key

Data type: SPRAS
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_FROM - Grid Usage Start Date

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

IV_TO - End Date for Grid Usage

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

EXPORTING Parameters details for CRM_ISU_GRIDUSAGE_GET_DATA

ES_GRID_DATA - Distribution Grid / Distributor Data

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

ET_GRIDUSAGE_DATA - Table with Grid Usage Conditions

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

EXCEPTIONS details

NO_GRID_ITEM_FOUND - Keine Netznutzungsposition gefunden

Data type:
Optional: No
Call by Reference: Yes

NO_PRICING_FOUND - Keine Information zur Preisquelle gefunden

Data type:
Optional: No
Call by Reference: Yes

NOT_AVAILABLE - RFC-Verbindung derzeit nicht verfügbar

Data type:
Optional: No
Call by Reference: Yes

ERROR_OCCURED - Internal Error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CRM_ISU_GRIDUSAGE_GET_DATA 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_es_grid_data  TYPE CRM_ISUT_GRID_DATA, "   
lv_iv_order_i_guid  TYPE CRMT_OBJECT_GUID32, "   
lv_no_grid_item_found  TYPE CRMT_OBJECT_GUID32, "   
lv_iv_pod_guid  TYPE SYSUUID-X, "   
lv_no_pricing_found  TYPE SYSUUID, "   
lv_et_gridusage_data  TYPE CRM_ISUT_GRIDUSAGE_DATA_TAB, "   
lv_iv_langu  TYPE SPRAS, "   SY-LANGU
lv_not_available  TYPE SPRAS, "   
lv_iv_from  TYPE CRM_ISUT_GRIDUSE_FROM, "   
lv_error_occured  TYPE CRM_ISUT_GRIDUSE_FROM, "   
lv_iv_to  TYPE CRM_ISUT_GRIDUSE_TO. "   

  CALL FUNCTION 'CRM_ISU_GRIDUSAGE_GET_DATA'  "Zugriff auf Netznutzungsdaten
    EXPORTING
         IV_ORDER_I_GUID = lv_iv_order_i_guid
         IV_POD_GUID = lv_iv_pod_guid
         IV_LANGU = lv_iv_langu
         IV_FROM = lv_iv_from
         IV_TO = lv_iv_to
    IMPORTING
         ES_GRID_DATA = lv_es_grid_data
         ET_GRIDUSAGE_DATA = lv_et_gridusage_data
    EXCEPTIONS
        NO_GRID_ITEM_FOUND = 1
        NO_PRICING_FOUND = 2
        NOT_AVAILABLE = 3
        ERROR_OCCURED = 4
. " CRM_ISU_GRIDUSAGE_GET_DATA




ABAP code using 7.40 inline data declarations to call FM CRM_ISU_GRIDUSAGE_GET_DATA

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 X FROM SYSUUID INTO @DATA(ld_iv_pod_guid).
 
 
 
DATA(ld_iv_langu) = SY-LANGU.
 
 
 
 
 


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!