FKK_SAMPLE_TFK2610 SAP Function module

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

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

Pattern for FM FKK_SAMPLE_TFK2610 - FKK SAMPLE TFK2610

CALL FUNCTION 'FKK_SAMPLE_TFK2610' "
  EXPORTING
    i_erkrs =                   " erkrs         Operating Concern
    i_char_name =               " erkrs_fnam_kk  Characteristic of an Operating Concern
    i_cobl =                    " fkkinv_cobl   Invoicing Account Assignment Block
    i_invbill_item =            " fkkinvbill_i  Billing Document Items
    i_invbill =                 " fkkinvbill    Billing Document
    i_inv_unit_public =         " fkkinv_unit_public_data  Invoicing Unit (Public Data)
  IMPORTING
    e_not_copa_relevant =       " xfeld
  CHANGING
    c_char_value =              " char30
    .  "  FKK_SAMPLE_TFK2610

ABAP code example for Function Module FKK_SAMPLE_TFK2610

The ABAP code below is a full code listing to execute function module FKK_SAMPLE_TFK2610 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_e_not_copa_relevant  
 
 TYPE XFELD
.


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

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

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

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

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

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

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

CALL FUNCTION 'FKK_SAMPLE_TFK2610'
  EXPORTING
    i_erkrs =                    ld_i_erkrs
    i_char_name =                ld_i_char_name
    i_cobl =                     ld_i_cobl
    i_invbill_item =             ld_i_invbill_item
    i_invbill =                  ld_i_invbill
    i_inv_unit_public =          ld_i_inv_unit_public
  IMPORTING
    e_not_copa_relevant =        ld_e_not_copa_relevant
  CHANGING
    c_char_value =               ld_c_char_value
    .  "  FKK_SAMPLE_TFK2610

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_c_char_value
 
 TYPE CHAR30 ,
ld_e_not_copa_relevant
 
 TYPE XFELD ,
ld_i_erkrs
 
 TYPE ERKRS ,
ld_i_char_name
 
 TYPE ERKRS_FNAM_KK ,
ld_i_cobl
 
 TYPE FKKINV_COBL ,
ld_i_invbill_item
 
 TYPE FKKINVBILL_I ,
ld_i_invbill
 
 TYPE FKKINVBILL ,
ld_i_inv_unit_public
 
 TYPE FKKINV_UNIT_PUBLIC_DATA .


ld_c_char_value = 'Check type of data required'.
ld_i_erkrs = 'Check type of data required'.
ld_i_char_name = 'Check type of data required'.
ld_i_cobl = 'Check type of data required'.
ld_i_invbill_item = 'Check type of data required'.
ld_i_invbill = 'Check type of data required'.
ld_i_inv_unit_public = 'Check type of data required'.