FILA_ITEM_SET_PROD_LINK SAP Function module

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

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

Pattern for FM FILA_ITEM_SET_PROD_LINK - FILA ITEM SET PROD LINK

CALL FUNCTION 'FILA_ITEM_SET_PROD_LINK' "
  CHANGING
    cs_contract_header =        " filagf_contract_header  Contract Header
    ct_contract_items =         " filagf_cont_item_tab  Contract Items
    ct_conditions =             " filagf_condition_tab  Contract Conditions
    ct_billing =                " filagf_cont_bill_tab  Payment Plan
    ct_contract_class =         " filagf_cont_class_tab  Contract Classification
    ct_contract_prods =         " filagf_cont_prod_tab  Product Information
    ct_return =                 " bapiret2_t    Return Table
    .  "  FILA_ITEM_SET_PROD_LINK

ABAP code example for Function Module FILA_ITEM_SET_PROD_LINK

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

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

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

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

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

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

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

CALL FUNCTION 'FILA_ITEM_SET_PROD_LINK'
  CHANGING
    cs_contract_header =         ld_cs_contract_header
    ct_contract_items =          ld_ct_contract_items
    ct_conditions =              ld_ct_conditions
    ct_billing =                 ld_ct_billing
    ct_contract_class =          ld_ct_contract_class
    ct_contract_prods =          ld_ct_contract_prods
    ct_return =                  ld_ct_return
    .  "  FILA_ITEM_SET_PROD_LINK

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_cs_contract_header
 
 TYPE FILAGF_CONTRACT_HEADER ,
ld_ct_contract_items
 
 TYPE FILAGF_CONT_ITEM_TAB ,
ld_ct_conditions
 
 TYPE FILAGF_CONDITION_TAB ,
ld_ct_billing
 
 TYPE FILAGF_CONT_BILL_TAB ,
ld_ct_contract_class
 
 TYPE FILAGF_CONT_CLASS_TAB ,
ld_ct_contract_prods
 
 TYPE FILAGF_CONT_PROD_TAB ,
ld_ct_return
 
 TYPE BAPIRET2_T .


ld_cs_contract_header = 'Check type of data required'.
ld_ct_contract_items = 'Check type of data required'.
ld_ct_conditions = 'Check type of data required'.
ld_ct_billing = 'Check type of data required'.
ld_ct_contract_class = 'Check type of data required'.
ld_ct_contract_prods = 'Check type of data required'.
ld_ct_return = 'Check type of data required'.