SAP FKK_BIX_IFCOMP_PROVIDER_CTR_30 Function Module for









FKK_BIX_IFCOMP_PROVIDER_CTR_30 is a standard fkk bix ifcomp provider ctr 30 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.


See here to view full function module documentation and code listing for fkk bix ifcomp provider ctr 30 FM, simply by entering the name FKK_BIX_IFCOMP_PROVIDER_CTR_30 into the relevant SAP transaction such as SE37 or SE38.

Function Group: FKKBIX_BIT_IFCOMP
Program Name: SAPLFKKBIX_BIT_IFCOMP
Main Program: SAPLFKKBIX_BIT_IFCOMP
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FKK_BIX_IFCOMP_PROVIDER_CTR_30 pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.
CALL FUNCTION 'FKK_BIX_IFCOMP_PROVIDER_CTR_30'"
  EXPORTING
   IV_BITCAT =  "
   IT_BIT2_TX =  "
   IT_BIT2_TT =  "
   IV_IFCOMP =  "
   IT_IFCOMP =  "
   IT_BIT0_IT =  "
   IT_BIT0_PY =  "
   IT_BIT0_TX =  "
   IT_BIT0_TT =  "
   IT_BIT2_IT =  "
   IT_BIT2_PY =  "

 IMPORTING
   ET_BIT2_IT_CHG =  "
   ET_BIT2_PY_CHG =  "
   ET_BIT2_TX_CHG =  "
   ET_BIT2_TT_CHG =  "
   ET_BIT2_MSG =  "
.



IMPORTING Parameters details for FKK_BIX_IFCOMP_PROVIDER_CTR_30

IV_BITCAT -

Data type: BITCAT_KK
Optional: No
Call by Reference: Yes

IT_BIT2_TX -

Data type: FKKBIXBIT2_TX_ALL_TAB
Optional: No
Call by Reference: Yes

IT_BIT2_TT -

Data type: FKKBIXBIT2_TT_ALL_TAB
Optional: No
Call by Reference: Yes

IV_IFCOMP -

Data type: BIT_IFCOMP_KK
Optional: No
Call by Reference: Yes

IT_IFCOMP -

Data type: FKKBIXBIT_IFCOMP_TAB
Optional: No
Call by Reference: Yes

IT_BIT0_IT -

Data type: FKKBIXBIT0_IT_ALL_TAB
Optional: No
Call by Reference: Yes

IT_BIT0_PY -

Data type: FKKBIXBIT0_PY_ALL_TAB
Optional: No
Call by Reference: Yes

IT_BIT0_TX -

Data type: FKKBIXBIT0_TX_ALL_TAB
Optional: No
Call by Reference: Yes

IT_BIT0_TT -

Data type: FKKBIXBIT0_TT_ALL_TAB
Optional: No
Call by Reference: Yes

IT_BIT2_IT -

Data type: FKKBIXBIT2_IT_ALL_TAB
Optional: No
Call by Reference: Yes

IT_BIT2_PY -

Data type: FKKBIXBIT2_PY_ALL_TAB
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FKK_BIX_IFCOMP_PROVIDER_CTR_30

ET_BIT2_IT_CHG -

Data type: FKKBIXBIT2_IT_ALL_TAB
Optional: No
Call by Reference: Yes

ET_BIT2_PY_CHG -

Data type: FKKBIXBIT2_PY_ALL_TAB
Optional: No
Call by Reference: Yes

ET_BIT2_TX_CHG -

Data type: FKKBIXBIT2_TX_ALL_TAB
Optional: No
Call by Reference: Yes

ET_BIT2_TT_CHG -

Data type: FKKBIXBIT2_TT_ALL_TAB
Optional: No
Call by Reference: Yes

ET_BIT2_MSG -

Data type: FKKBIXBIT2_MSG_TAB
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_BIX_IFCOMP_PROVIDER_CTR_30 Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

DATA:
lv_iv_bitcat  TYPE BITCAT_KK, "   
lv_et_bit2_it_chg  TYPE FKKBIXBIT2_IT_ALL_TAB, "   
lv_it_bit2_tx  TYPE FKKBIXBIT2_TX_ALL_TAB, "   
lv_it_bit2_tt  TYPE FKKBIXBIT2_TT_ALL_TAB, "   
lv_iv_ifcomp  TYPE BIT_IFCOMP_KK, "   
lv_et_bit2_py_chg  TYPE FKKBIXBIT2_PY_ALL_TAB, "   
lv_it_ifcomp  TYPE FKKBIXBIT_IFCOMP_TAB, "   
lv_et_bit2_tx_chg  TYPE FKKBIXBIT2_TX_ALL_TAB, "   
lv_it_bit0_it  TYPE FKKBIXBIT0_IT_ALL_TAB, "   
lv_et_bit2_tt_chg  TYPE FKKBIXBIT2_TT_ALL_TAB, "   
lv_it_bit0_py  TYPE FKKBIXBIT0_PY_ALL_TAB, "   
lv_et_bit2_msg  TYPE FKKBIXBIT2_MSG_TAB, "   
lv_it_bit0_tx  TYPE FKKBIXBIT0_TX_ALL_TAB, "   
lv_it_bit0_tt  TYPE FKKBIXBIT0_TT_ALL_TAB, "   
lv_it_bit2_it  TYPE FKKBIXBIT2_IT_ALL_TAB, "   
lv_it_bit2_py  TYPE FKKBIXBIT2_PY_ALL_TAB. "   

  CALL FUNCTION 'FKK_BIX_IFCOMP_PROVIDER_CTR_30'  "
    EXPORTING
         IV_BITCAT = lv_iv_bitcat
         IT_BIT2_TX = lv_it_bit2_tx
         IT_BIT2_TT = lv_it_bit2_tt
         IV_IFCOMP = lv_iv_ifcomp
         IT_IFCOMP = lv_it_ifcomp
         IT_BIT0_IT = lv_it_bit0_it
         IT_BIT0_PY = lv_it_bit0_py
         IT_BIT0_TX = lv_it_bit0_tx
         IT_BIT0_TT = lv_it_bit0_tt
         IT_BIT2_IT = lv_it_bit2_it
         IT_BIT2_PY = lv_it_bit2_py
    IMPORTING
         ET_BIT2_IT_CHG = lv_et_bit2_it_chg
         ET_BIT2_PY_CHG = lv_et_bit2_py_chg
         ET_BIT2_TX_CHG = lv_et_bit2_tx_chg
         ET_BIT2_TT_CHG = lv_et_bit2_tt_chg
         ET_BIT2_MSG = lv_et_bit2_msg
. " FKK_BIX_IFCOMP_PROVIDER_CTR_30




ABAP code using 7.40 inline data declarations to call FM FKK_BIX_IFCOMP_PROVIDER_CTR_30

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!