ISM_EVENT_2222 SAP Function module - Event 2222: Determine Transactions for Collective Bill

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

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

Pattern for FM ISM_EVENT_2222 - ISM EVENT 2222

CALL FUNCTION 'ISM_EVENT_2222' "Event 2222: Determine Transactions for Collective Bill
  EXPORTING
    x_applk =                   " applk_kk      Application Area
    x_herkf =                   " herkf_kk      Document Source Key
  TABLES
    t_fkkcl_orig =              " fkkcl_2220
* CHANGING
*   y_hvorg_coll =              " hvorg_kk      Main Transaction for Line Item
*   y_tvorg_coll =              " tvorg_kk      Subtransaction for Line Item
*   y_create_new_coll =         " boole-boole   Create New Collective Invoice
    .  "  ISM_EVENT_2222

ABAP code example for Function Module ISM_EVENT_2222

The ABAP code below is a full code listing to execute function module ISM_EVENT_2222 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:
it_t_fkkcl_orig  
 
 TYPE STANDARD TABLE OF FKKCL_2220,"TABLES PARAM
wa_t_fkkcl_orig
 
 LIKE LINE OF it_t_fkkcl_orig
.


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

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


DATA(ld_y_create_new_coll) = some text here

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

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

"populate fields of struture and append to itab
append wa_t_fkkcl_orig to it_t_fkkcl_orig.
.

CALL FUNCTION 'ISM_EVENT_2222'
  EXPORTING
    x_applk =                    ld_x_applk
    x_herkf =                    ld_x_herkf
  TABLES
    t_fkkcl_orig =               it_t_fkkcl_orig
* CHANGING
*   y_hvorg_coll =               ld_y_hvorg_coll
*   y_tvorg_coll =               ld_y_tvorg_coll
*   y_create_new_coll =          ld_y_create_new_coll
    .  "  ISM_EVENT_2222

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_y_hvorg_coll
 
 TYPE HVORG_KK ,
ld_x_applk
 
 TYPE APPLK_KK ,
it_t_fkkcl_orig
 
 TYPE STANDARD TABLE OF FKKCL_2220 ,
wa_t_fkkcl_orig
 
 LIKE LINE OF it_t_fkkcl_orig,
ld_y_tvorg_coll
 
 TYPE TVORG_KK ,
ld_x_herkf
 
 TYPE HERKF_KK ,
ld_y_create_new_coll
 
 TYPE BOOLE-BOOLE .


ld_y_hvorg_coll = 'Check type of data required'.
ld_x_applk = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_t_fkkcl_orig to it_t_fkkcl_orig.
ld_y_tvorg_coll = 'Check type of data required'.
ld_x_herkf = 'Check type of data required'.

ld_y_create_new_coll = some text here