SAP FKK_BIX_BIT2_SELECT_COUNT Function Module for
FKK_BIX_BIT2_SELECT_COUNT is a standard fkk bix bit2 select count 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 bit2 select count FM, simply by entering the name FKK_BIX_BIT2_SELECT_COUNT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKKBIX_BIT_DB
Program Name: SAPLFKKBIX_BIT_DB
Main Program: SAPLFKKBIX_BIT_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_BIX_BIT2_SELECT_COUNT 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_BIT2_SELECT_COUNT'".
EXPORTING
* IT_GPART_RANGE = "Range Table GPART
* IT_BITCRDATE_RANGE = "Range Table for Any Date
* IT_BILL_FIRST_RANGE = "Range Table for Any Date
* IV_BILL_PROCESS = "Billing Process
* IT_FURTHER_SEL = "Table Type for WHERE Clause
* IT_VKONT_RANGE = "Range Table VKONT
* IT_MDCAT_RANGE = "
* IT_SRCTATYPE_RANGE = "Ranges Table for SRCTATYPE_KK
* IT_SRCTAID_RANGE = "Ranges Table for SRCTAID_KK
* IT_BITCAT_RANGE = "Ranges Table for BITCAT_KK
* IT_SUBPROCESS_RANGE = "Ranges Table for SUB_PROCESS_KK
* IT_BITTYPE_RANGE = "Ranges Table for BITTYPE_KK
* IT_BITDATE_RANGE = "
IMPORTING Parameters details for FKK_BIX_BIT2_SELECT_COUNT
IT_GPART_RANGE - Range Table GPART
Data type: FKK_RT_GPARTOptional: Yes
Call by Reference: Yes
IT_BITCRDATE_RANGE - Range Table for Any Date
Data type: FKK_RT_DATUMOptional: Yes
Call by Reference: Yes
IT_BILL_FIRST_RANGE - Range Table for Any Date
Data type: FKK_RT_DATUMOptional: Yes
Call by Reference: Yes
IV_BILL_PROCESS - Billing Process
Data type: BILL_PROCESS_KKOptional: Yes
Call by Reference: Yes
IT_FURTHER_SEL - Table Type for WHERE Clause
Data type: FKK_MAD_TWHERELOptional: Yes
Call by Reference: Yes
IT_VKONT_RANGE - Range Table VKONT
Data type: FKK_RT_VKONTOptional: Yes
Call by Reference: Yes
IT_MDCAT_RANGE -
Data type: FKK_RT_MDCATOptional: Yes
Call by Reference: Yes
IT_SRCTATYPE_RANGE - Ranges Table for SRCTATYPE_KK
Data type: FKK_RT_SRCTATYPEOptional: Yes
Call by Reference: Yes
IT_SRCTAID_RANGE - Ranges Table for SRCTAID_KK
Data type: FKK_RT_SRCTAIDOptional: Yes
Call by Reference: Yes
IT_BITCAT_RANGE - Ranges Table for BITCAT_KK
Data type: FKK_RT_BITCATOptional: Yes
Call by Reference: Yes
IT_SUBPROCESS_RANGE - Ranges Table for SUB_PROCESS_KK
Data type: FKK_RT_SUBPROCESSOptional: Yes
Call by Reference: Yes
IT_BITTYPE_RANGE - Ranges Table for BITTYPE_KK
Data type: FKK_RT_BITTYPEOptional: Yes
Call by Reference: Yes
IT_BITDATE_RANGE -
Data type: FKK_RT_DATUMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for FKK_BIX_BIT2_SELECT_COUNT 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_it_gpart_range | TYPE FKK_RT_GPART, " | |||
| lv_it_bitcrdate_range | TYPE FKK_RT_DATUM, " | |||
| lv_it_bill_first_range | TYPE FKK_RT_DATUM, " | |||
| lv_iv_bill_process | TYPE BILL_PROCESS_KK, " | |||
| lv_it_further_sel | TYPE FKK_MAD_TWHEREL, " | |||
| lv_it_vkont_range | TYPE FKK_RT_VKONT, " | |||
| lv_it_mdcat_range | TYPE FKK_RT_MDCAT, " | |||
| lv_it_srctatype_range | TYPE FKK_RT_SRCTATYPE, " | |||
| lv_it_srctaid_range | TYPE FKK_RT_SRCTAID, " | |||
| lv_it_bitcat_range | TYPE FKK_RT_BITCAT, " | |||
| lv_it_subprocess_range | TYPE FKK_RT_SUBPROCESS, " | |||
| lv_it_bittype_range | TYPE FKK_RT_BITTYPE, " | |||
| lv_it_bitdate_range | TYPE FKK_RT_DATUM. " |
|   CALL FUNCTION 'FKK_BIX_BIT2_SELECT_COUNT' " |
| EXPORTING | ||
| IT_GPART_RANGE | = lv_it_gpart_range | |
| IT_BITCRDATE_RANGE | = lv_it_bitcrdate_range | |
| IT_BILL_FIRST_RANGE | = lv_it_bill_first_range | |
| IV_BILL_PROCESS | = lv_iv_bill_process | |
| IT_FURTHER_SEL | = lv_it_further_sel | |
| IT_VKONT_RANGE | = lv_it_vkont_range | |
| IT_MDCAT_RANGE | = lv_it_mdcat_range | |
| IT_SRCTATYPE_RANGE | = lv_it_srctatype_range | |
| IT_SRCTAID_RANGE | = lv_it_srctaid_range | |
| IT_BITCAT_RANGE | = lv_it_bitcat_range | |
| IT_SUBPROCESS_RANGE | = lv_it_subprocess_range | |
| IT_BITTYPE_RANGE | = lv_it_bittype_range | |
| IT_BITDATE_RANGE | = lv_it_bitdate_range | |
| . " FKK_BIX_BIT2_SELECT_COUNT | ||
ABAP code using 7.40 inline data declarations to call FM FKK_BIX_BIT2_SELECT_COUNT
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