FKK_SAMPLE_8021 SAP Function module - BILL: Maintain Billing Account Header Data (BAPI)

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

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

Pattern for FM FKK_SAMPLE_8021 - FKK SAMPLE 8021

CALL FUNCTION 'FKK_SAMPLE_8021' "BILL: Maintain Billing Account Header Data (BAPI)
  EXPORTING
*   i_head_ins_bapi =           " bapi_fkkbibillacc_h_ins  BAPI Structure: Add Billing Account Header Data
*   i_head_upd_bapi =           " bapi_fkkbibillacc_h_upd  BAPI Structure: Update Billing Account Header Data
    i_extensionin_tab =         " bapiparex_tab_kk  FI-CA: Standard Table for Structure BAPIPAREX
  IMPORTING
    e_return_tab =              " bapiret2_tab_kk  FI-CA: Standard Table for Structure BAPIRET2
  CHANGING
    c_head_cust =               " fkkbibillacc_h_ci_si  Customer- and Application-Specific Billing Account Header Data
    c_extensionout_tab =        " bapiparex_tab_kk  FI-CA: Standard Table for Structure BAPIPAREX
    .  "  FKK_SAMPLE_8021

ABAP code example for Function Module FKK_SAMPLE_8021

The ABAP code below is a full code listing to execute function module FKK_SAMPLE_8021 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_return_tab  
 
 TYPE BAPIRET2_TAB_KK
.


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

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

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

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

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

CALL FUNCTION 'FKK_SAMPLE_8021'
  EXPORTING
*   i_head_ins_bapi =            ld_i_head_ins_bapi
*   i_head_upd_bapi =            ld_i_head_upd_bapi
    i_extensionin_tab =          ld_i_extensionin_tab
  IMPORTING
    e_return_tab =               ld_e_return_tab
  CHANGING
    c_head_cust =                ld_c_head_cust
    c_extensionout_tab =         ld_c_extensionout_tab
    .  "  FKK_SAMPLE_8021

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_head_cust
 
 TYPE FKKBIBILLACC_H_CI_SI ,
ld_e_return_tab
 
 TYPE BAPIRET2_TAB_KK ,
ld_i_head_ins_bapi
 
 TYPE BAPI_FKKBIBILLACC_H_INS ,
ld_c_extensionout_tab
 
 TYPE BAPIPAREX_TAB_KK ,
ld_i_head_upd_bapi
 
 TYPE BAPI_FKKBIBILLACC_H_UPD ,
ld_i_extensionin_tab
 
 TYPE BAPIPAREX_TAB_KK .


ld_c_head_cust = 'Check type of data required'.
ld_i_head_ins_bapi = 'Check type of data required'.
ld_c_extensionout_tab = 'Check type of data required'.
ld_i_head_upd_bapi = 'Check type of data required'.
ld_i_extensionin_tab = 'Check type of data required'.

SAP Documentation for FM FKK_SAMPLE_8021