SAP Function Modules

SD_COLLECTIVE_RUN_EXECUTE SAP Function module







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

Associated Function Group: V60P
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM SD_COLLECTIVE_RUN_EXECUTE - SD COLLECTIVE RUN EXECUTE





CALL FUNCTION 'SD_COLLECTIVE_RUN_EXECUTE' "
  EXPORTING
    v60p_input_rv60a =          " rv60a
*   v60p_input_smart = 'F'      " vbsk-smart
*   v60p_input_sammg =          " vbsk-sammg    Group
*   id_utasy = ' '              "
*   id_utswl = ' '              "
*   id_utsnl = ' '              "
*   id_no_new_run = ' '         "
*   id_invoice_list = SPACE     "
*   iv_opt_enabled = ABAP_FALSE  " abap_bool
  IMPORTING
    v60p_output_vbsk =          " vbsk
  TABLES
    v60p_input_vkdfif =         " vkdfif
    v60p_output_vbfs =          " vbfs
    v60p_output_vbss =          " vbss
    .  "  SD_COLLECTIVE_RUN_EXECUTE

ABAP code example for Function Module SD_COLLECTIVE_RUN_EXECUTE





The ABAP code below is a full code listing to execute function module SD_COLLECTIVE_RUN_EXECUTE 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_v60p_output_vbsk  TYPE VBSK ,
it_v60p_input_vkdfif  TYPE STANDARD TABLE OF VKDFIF,"TABLES PARAM
wa_v60p_input_vkdfif  LIKE LINE OF it_v60p_input_vkdfif ,
it_v60p_output_vbfs  TYPE STANDARD TABLE OF VBFS,"TABLES PARAM
wa_v60p_output_vbfs  LIKE LINE OF it_v60p_output_vbfs ,
it_v60p_output_vbss  TYPE STANDARD TABLE OF VBSS,"TABLES PARAM
wa_v60p_output_vbss  LIKE LINE OF it_v60p_output_vbss .

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

SELECT single SMART
FROM VBSK
INTO @DATA(ld_v60p_input_smart).


SELECT single SAMMG
FROM VBSK
INTO @DATA(ld_v60p_input_sammg).

DATA(ld_id_utasy) = 'some text here'.
DATA(ld_id_utswl) = 'some text here'.
DATA(ld_id_utsnl) = 'some text here'.
DATA(ld_id_no_new_run) = 'some text here'.
DATA(ld_id_invoice_list) = 'some text here'.
DATA(ld_iv_opt_enabled) = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_v60p_input_vkdfif to it_v60p_input_vkdfif.

"populate fields of struture and append to itab
append wa_v60p_output_vbfs to it_v60p_output_vbfs.

"populate fields of struture and append to itab
append wa_v60p_output_vbss to it_v60p_output_vbss. . CALL FUNCTION 'SD_COLLECTIVE_RUN_EXECUTE' EXPORTING v60p_input_rv60a = ld_v60p_input_rv60a * v60p_input_smart = ld_v60p_input_smart * v60p_input_sammg = ld_v60p_input_sammg * id_utasy = ld_id_utasy * id_utswl = ld_id_utswl * id_utsnl = ld_id_utsnl * id_no_new_run = ld_id_no_new_run * id_invoice_list = ld_id_invoice_list * iv_opt_enabled = ld_iv_opt_enabled IMPORTING v60p_output_vbsk = ld_v60p_output_vbsk TABLES v60p_input_vkdfif = it_v60p_input_vkdfif v60p_output_vbfs = it_v60p_output_vbfs v60p_output_vbss = it_v60p_output_vbss . " SD_COLLECTIVE_RUN_EXECUTE
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_v60p_output_vbsk  TYPE VBSK ,
ld_v60p_input_rv60a  TYPE RV60A ,
it_v60p_input_vkdfif  TYPE STANDARD TABLE OF VKDFIF ,
wa_v60p_input_vkdfif  LIKE LINE OF it_v60p_input_vkdfif,
ld_v60p_input_smart  TYPE VBSK-SMART ,
it_v60p_output_vbfs  TYPE STANDARD TABLE OF VBFS ,
wa_v60p_output_vbfs  LIKE LINE OF it_v60p_output_vbfs,
ld_v60p_input_sammg  TYPE VBSK-SAMMG ,
it_v60p_output_vbss  TYPE STANDARD TABLE OF VBSS ,
wa_v60p_output_vbss  LIKE LINE OF it_v60p_output_vbss,
ld_id_utasy  TYPE STRING ,
ld_id_utswl  TYPE STRING ,
ld_id_utsnl  TYPE STRING ,
ld_id_no_new_run  TYPE STRING ,
ld_id_invoice_list  TYPE STRING ,
ld_iv_opt_enabled  TYPE ABAP_BOOL .

ld_v60p_input_rv60a = 'Check type of data required'.

"populate fields of struture and append to itab
append wa_v60p_input_vkdfif to it_v60p_input_vkdfif.

SELECT single SMART
FROM VBSK
INTO ld_v60p_input_smart.


"populate fields of struture and append to itab
append wa_v60p_output_vbfs to it_v60p_output_vbfs.

SELECT single SAMMG
FROM VBSK
INTO ld_v60p_input_sammg.


"populate fields of struture and append to itab
append wa_v60p_output_vbss to it_v60p_output_vbss.
ld_id_utasy = 'some text here'.
ld_id_utswl = 'some text here'.
ld_id_utsnl = 'some text here'.
ld_id_no_new_run = 'some text here'.
ld_id_invoice_list = 'some text here'.
ld_iv_opt_enabled = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SD_COLLECTIVE_RUN_EXECUTE or its description.