ISU_IDE_TEST_DELFOR SAP Function module - Test Function for German DELFOR

ISU_IDE_TEST_DELFOR 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_DELFOR 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_DELFOR - ISU IDE TEST DELFOR

CALL FUNCTION 'ISU_IDE_TEST_DELFOR' "Test Function for German DELFOR
  EXPORTING
    x_settldoc =                " e_edmsettldoc  Settlement Document
    x_sender =                  " service_prov  Service Providers
    x_receiver =                " service_prov  Service Providers
    xt_profile =                " t_eedmsettl_sndprofile  Profiles for Sending
  IMPORTING
    yt_not_sent_profile =       " t_eedmsettl_sndprofile  Profiles for Sending
    yt_error_log =              " t_eedmsettlmsg  General Error Messages
    yt_profhead =               " teprofhead    Table type for profile header data
    .  "  ISU_IDE_TEST_DELFOR

ABAP code example for Function Module ISU_IDE_TEST_DELFOR

The ABAP code below is a full code listing to execute function module ISU_IDE_TEST_DELFOR 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_yt_not_sent_profile  
 
 TYPE T_EEDMSETTL_SNDPROFILE
,
ld_yt_error_log  
 
 TYPE T_EEDMSETTLMSG
,
ld_yt_profhead  
 
 TYPE TEPROFHEAD
.


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

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

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

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

CALL FUNCTION 'ISU_IDE_TEST_DELFOR'
  EXPORTING
    x_settldoc =                 ld_x_settldoc
    x_sender =                   ld_x_sender
    x_receiver =                 ld_x_receiver
    xt_profile =                 ld_xt_profile
  IMPORTING
    yt_not_sent_profile =        ld_yt_not_sent_profile
    yt_error_log =               ld_yt_error_log
    yt_profhead =                ld_yt_profhead
    .  "  ISU_IDE_TEST_DELFOR

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_yt_not_sent_profile
 
 TYPE T_EEDMSETTL_SNDPROFILE ,
ld_x_settldoc
 
 TYPE E_EDMSETTLDOC ,
ld_yt_error_log
 
 TYPE T_EEDMSETTLMSG ,
ld_x_sender
 
 TYPE SERVICE_PROV ,
ld_yt_profhead
 
 TYPE TEPROFHEAD ,
ld_x_receiver
 
 TYPE SERVICE_PROV ,
ld_xt_profile
 
 TYPE T_EEDMSETTL_SNDPROFILE .


ld_x_settldoc = 'Check type of data required'.
ld_x_sender = 'Check type of data required'.
ld_x_receiver = 'Check type of data required'.
ld_xt_profile = 'Check type of data required'.