ISU_COMPR_VDEW_MSCONS_USG_IN2 SAP Function module - IS-U VDEW: MSCONS for Consumption Data and Meter Reading Results (Inboun

ISU_COMPR_VDEW_MSCONS_USG_IN2 is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name ISU_COMPR_VDEW_MSCONS_USG_IN2 into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: ECOMPR_VDEW_IN
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM ISU_COMPR_VDEW_MSCONS_USG_IN2 - ISU COMPR VDEW MSCONS USG IN2

CALL FUNCTION 'ISU_COMPR_VDEW_MSCONS_USG_IN2' "IS-U VDEW: MSCONS for Consumption Data and Meter Reading Results (Inbound)
  EXPORTING
    idoc_contrl =               " edidc         Control Record (IDoc)
*   x_receiver =                " e_dexservprovself  Own Service Provider
*   x_sender =                  " e_dexservprov  Third Party Service Provider
  IMPORTING
    y_idoc_status =             " bdidocstat    ALE IDoc Status (Subset of All IDoc Status Fields)
  TABLES
    idoc_data =                 " edidd         Data Record (IDoc)
  EXCEPTIONS
    USAGE_UPLOAD_ERROR = 1      "
    .  "  ISU_COMPR_VDEW_MSCONS_USG_IN2

ABAP code example for Function Module ISU_COMPR_VDEW_MSCONS_USG_IN2

The ABAP code below is a full code listing to execute function module ISU_COMPR_VDEW_MSCONS_USG_IN2 including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_y_idoc_status  
 
 TYPE BDIDOCSTAT
,
it_idoc_data  
 
 TYPE STANDARD TABLE OF EDIDD,"TABLES PARAM
wa_idoc_data
 
 LIKE LINE OF it_idoc_data
.


DATA(ld_idoc_contrl) = 'Check type of data required'.

DATA(ld_x_receiver) = 'Check type of data required'.

DATA(ld_x_sender) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
.

CALL FUNCTION 'ISU_COMPR_VDEW_MSCONS_USG_IN2'
  EXPORTING
    idoc_contrl =                ld_idoc_contrl
*   x_receiver =                 ld_x_receiver
*   x_sender =                   ld_x_sender
  IMPORTING
    y_idoc_status =              ld_y_idoc_status
  TABLES
    idoc_data =                  it_idoc_data
  EXCEPTIONS
    USAGE_UPLOAD_ERROR =         1
    .  "  ISU_COMPR_VDEW_MSCONS_USG_IN2

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_y_idoc_status
 
 TYPE BDIDOCSTAT ,
ld_idoc_contrl
 
 TYPE EDIDC ,
it_idoc_data
 
 TYPE STANDARD TABLE OF EDIDD ,
wa_idoc_data
 
 LIKE LINE OF it_idoc_data,
ld_x_receiver
 
 TYPE E_DEXSERVPROVSELF ,
ld_x_sender
 
 TYPE E_DEXSERVPROV .


ld_idoc_contrl = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
ld_x_receiver = 'Check type of data required'.
ld_x_sender = 'Check type of data required'.