FKK_EBPP_CA_GRP_BY_VKONT SAP Function module - ContractAccountERPReceivablesPayablesRegisterItemByIDQueryResponse

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

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

Pattern for FM FKK_EBPP_CA_GRP_BY_VKONT - FKK EBPP CA GRP BY VKONT

CALL FUNCTION 'FKK_EBPP_CA_GRP_BY_VKONT' "ContractAccountERPReceivablesPayablesRegisterItemByIDQueryResponse
  EXPORTING
*   it_r_bpid =                 " fkk_rt_gpart  Range Table GPART
    iv_contract_account_id =    " vkont_kk      Contract Account Number
*   is_r_clearingstatuscode =   " fkk_ebpp_range_cleastatco  Rangestruktur für Buchungskreis
*   it_r_company_id =           " fkk_rt_bukrs  Range table for company code
*   it_r_postingdate =          " fkk_rt_budat  Range Table for BUDAT
*   iv_maxopsplitduedate =      " datum         Date
*   iv_minclsplitcldate =       " datum         Date
*   is_processing_cond =        " fkk_without_lastreturned_query  Proxy Structure (generated)
*   iv_xwith_group =            " xfeld         with SplitItemGroup
  IMPORTING
    et_contract_account =       " fkk_ebpp_tt_contractaccount  table type for ContractAccount node
    es_processing_cond =        " fkk_without_lastreturned_respo  Proxy Structure (generated)
  CHANGING
    ct_messages =               " fkk_ebpp_t_bapiret2  table type for bapiret2
    .  "  FKK_EBPP_CA_GRP_BY_VKONT

ABAP code example for Function Module FKK_EBPP_CA_GRP_BY_VKONT

The ABAP code below is a full code listing to execute function module FKK_EBPP_CA_GRP_BY_VKONT 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_et_contract_account  
 
 TYPE FKK_EBPP_TT_CONTRACTACCOUNT
,
ld_es_processing_cond  
 
 TYPE FKK_WITHOUT_LASTRETURNED_RESPO
.


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

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

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

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

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

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

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

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

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

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

CALL FUNCTION 'FKK_EBPP_CA_GRP_BY_VKONT'
  EXPORTING
*   it_r_bpid =                  ld_it_r_bpid
    iv_contract_account_id =     ld_iv_contract_account_id
*   is_r_clearingstatuscode =    ld_is_r_clearingstatuscode
*   it_r_company_id =            ld_it_r_company_id
*   it_r_postingdate =           ld_it_r_postingdate
*   iv_maxopsplitduedate =       ld_iv_maxopsplitduedate
*   iv_minclsplitcldate =        ld_iv_minclsplitcldate
*   is_processing_cond =         ld_is_processing_cond
*   iv_xwith_group =             ld_iv_xwith_group
  IMPORTING
    et_contract_account =        ld_et_contract_account
    es_processing_cond =         ld_es_processing_cond
  CHANGING
    ct_messages =                ld_ct_messages
    .  "  FKK_EBPP_CA_GRP_BY_VKONT

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_ct_messages
 
 TYPE FKK_EBPP_T_BAPIRET2 ,
ld_et_contract_account
 
 TYPE FKK_EBPP_TT_CONTRACTACCOUNT ,
ld_it_r_bpid
 
 TYPE FKK_RT_GPART ,
ld_es_processing_cond
 
 TYPE FKK_WITHOUT_LASTRETURNED_RESPO ,
ld_iv_contract_account_id
 
 TYPE VKONT_KK ,
ld_is_r_clearingstatuscode
 
 TYPE FKK_EBPP_RANGE_CLEASTATCO ,
ld_it_r_company_id
 
 TYPE FKK_RT_BUKRS ,
ld_it_r_postingdate
 
 TYPE FKK_RT_BUDAT ,
ld_iv_maxopsplitduedate
 
 TYPE DATUM ,
ld_iv_minclsplitcldate
 
 TYPE DATUM ,
ld_is_processing_cond
 
 TYPE FKK_WITHOUT_LASTRETURNED_QUERY ,
ld_iv_xwith_group
 
 TYPE XFELD .


ld_ct_messages = 'Check type of data required'.
ld_it_r_bpid = 'Check type of data required'.
ld_iv_contract_account_id = 'Check type of data required'.
ld_is_r_clearingstatuscode = 'Check type of data required'.
ld_it_r_company_id = 'Check type of data required'.
ld_it_r_postingdate = 'Check type of data required'.
ld_iv_maxopsplitduedate = 'Check type of data required'.
ld_iv_minclsplitcldate = 'Check type of data required'.
ld_is_processing_cond = 'Check type of data required'.
ld_iv_xwith_group = 'Check type of data required'.