ISU_IDE_TEST_MSCONS_INT SAP Function module - Test Function for German MSCONS

ISU_IDE_TEST_MSCONS_INT 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_IDE_TEST_MSCONS_INT into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM ISU_IDE_TEST_MSCONS_INT - ISU IDE TEST MSCONS INT

CALL FUNCTION 'ISU_IDE_TEST_MSCONS_INT' "Test Function for German MSCONS
  EXPORTING
    x_comevent =                " comevent      Event Within the Communication Level
*   x_contract =                " vertrag       Contract
*   x_anlage =                  " anlage        Installation
*   x_ext_pod =                 " ext_ui        Point of Delivery ID
*   x_int_pod =                 " int_ui        Internal Key for Point of Delivery
    x_keydate = SY-DATUM        " datum         Date and Time, Current (Application Server) Date
    x_from =                    " eedmdatefrom  Structure for From-Date
    x_to =                      " eedmdateto    Structure for To-Date
    .  "  ISU_IDE_TEST_MSCONS_INT

ABAP code example for Function Module ISU_IDE_TEST_MSCONS_INT

The ABAP code below is a full code listing to execute function module ISU_IDE_TEST_MSCONS_INT 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_x_comevent) = 'Check type of data required'.

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

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

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

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

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

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

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

CALL FUNCTION 'ISU_IDE_TEST_MSCONS_INT'
  EXPORTING
    x_comevent =                 ld_x_comevent
*   x_contract =                 ld_x_contract
*   x_anlage =                   ld_x_anlage
*   x_ext_pod =                  ld_x_ext_pod
*   x_int_pod =                  ld_x_int_pod
    x_keydate =                  ld_x_keydate
    x_from =                     ld_x_from
    x_to =                       ld_x_to
    .  "  ISU_IDE_TEST_MSCONS_INT

IF SY-SUBRC EQ 0.
  "All OK
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_x_comevent
 
 TYPE COMEVENT ,
ld_x_contract
 
 TYPE VERTRAG ,
ld_x_anlage
 
 TYPE ANLAGE ,
ld_x_ext_pod
 
 TYPE EXT_UI ,
ld_x_int_pod
 
 TYPE INT_UI ,
ld_x_keydate
 
 TYPE DATUM ,
ld_x_from
 
 TYPE EEDMDATEFROM ,
ld_x_to
 
 TYPE EEDMDATETO .


ld_x_comevent = 'Check type of data required'.
ld_x_contract = 'Check type of data required'.
ld_x_anlage = 'Check type of data required'.
ld_x_ext_pod = 'Check type of data required'.
ld_x_int_pod = 'Check type of data required'.
ld_x_keydate = 'Check type of data required'.
ld_x_from = 'Check type of data required'.
ld_x_to = 'Check type of data required'.