SAP FKK_BIX_BIT4_IT_SELECT Function Module for









FKK_BIX_BIT4_IT_SELECT is a standard fkk bix bit4 it select 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 bit4 it select FM, simply by entering the name FKK_BIX_BIT4_IT_SELECT into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_BIX_BIT4_IT_SELECT 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_BIT4_IT_SELECT'"
EXPORTING
* I_BILLDOCNO = "
* IT_BITDATE_RANGES = "
* IT_BITTIME_RANGES = "
* IT_VTREF_RANGES = "
* IT_WHERE = "
* I_MAX_NUM_BITS = 1000 "
* IT_BILLDOC_SRCITEM = "
* I_BIT_GRPNO = "
* I_SRC_GROUP = "
* IT_SRCTATYPE_RANGES = "
* IT_SRCTAID_RANGES = "
* IT_BITCAT_RANGES = "
* IT_BITTYPE_RANGES = "
* IT_SUBPROCESS_RANGES = "

IMPORTING
ET_BIT4_IT = "
.



IMPORTING Parameters details for FKK_BIX_BIT4_IT_SELECT

I_BILLDOCNO -

Data type: BILLDOCNO_KK
Optional: Yes
Call by Reference: Yes

IT_BITDATE_RANGES -

Data type: FKK_RT_BITDATE
Optional: Yes
Call by Reference: Yes

IT_BITTIME_RANGES -

Data type: FKK_RT_BITTIME
Optional: Yes
Call by Reference: Yes

IT_VTREF_RANGES -

Data type: FKK_RT_VTREF
Optional: Yes
Call by Reference: Yes

IT_WHERE -

Data type: FKK_MAD_TWHEREL
Optional: Yes
Call by Reference: Yes

I_MAX_NUM_BITS -

Data type: DDSHMAXREC
Default: 1000
Optional: Yes
Call by Reference: Yes

IT_BILLDOC_SRCITEM -

Data type: FKKINVBILL_S_TAB
Optional: Yes
Call by Reference: Yes

I_BIT_GRPNO -

Data type: BIT_GRPNO_KK
Optional: Yes
Call by Reference: Yes

I_SRC_GROUP -

Data type: SRC_GROUP_KK
Optional: Yes
Call by Reference: Yes

IT_SRCTATYPE_RANGES -

Data type: FKK_RT_SRCTATYPE
Optional: Yes
Call by Reference: Yes

IT_SRCTAID_RANGES -

Data type: FKK_RT_SRCTAID
Optional: Yes
Call by Reference: Yes

IT_BITCAT_RANGES -

Data type: FKK_RT_BITCAT
Optional: Yes
Call by Reference: Yes

IT_BITTYPE_RANGES -

Data type: FKK_RT_BITTYPE
Optional: Yes
Call by Reference: Yes

IT_SUBPROCESS_RANGES -

Data type: FKK_RT_SUBPROCESS
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FKK_BIX_BIT4_IT_SELECT

ET_BIT4_IT -

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

Copy and paste ABAP code example for FKK_BIX_BIT4_IT_SELECT 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_et_bit4_it  TYPE FKKBIXBIT4_IT_ALL_TAB, "   
lv_i_billdocno  TYPE BILLDOCNO_KK, "   
lv_it_bitdate_ranges  TYPE FKK_RT_BITDATE, "   
lv_it_bittime_ranges  TYPE FKK_RT_BITTIME, "   
lv_it_vtref_ranges  TYPE FKK_RT_VTREF, "   
lv_it_where  TYPE FKK_MAD_TWHEREL, "   
lv_i_max_num_bits  TYPE DDSHMAXREC, "   1000
lv_it_billdoc_srcitem  TYPE FKKINVBILL_S_TAB, "   
lv_i_bit_grpno  TYPE BIT_GRPNO_KK, "   
lv_i_src_group  TYPE SRC_GROUP_KK, "   
lv_it_srctatype_ranges  TYPE FKK_RT_SRCTATYPE, "   
lv_it_srctaid_ranges  TYPE FKK_RT_SRCTAID, "   
lv_it_bitcat_ranges  TYPE FKK_RT_BITCAT, "   
lv_it_bittype_ranges  TYPE FKK_RT_BITTYPE, "   
lv_it_subprocess_ranges  TYPE FKK_RT_SUBPROCESS. "   

  CALL FUNCTION 'FKK_BIX_BIT4_IT_SELECT'  "
    EXPORTING
         I_BILLDOCNO = lv_i_billdocno
         IT_BITDATE_RANGES = lv_it_bitdate_ranges
         IT_BITTIME_RANGES = lv_it_bittime_ranges
         IT_VTREF_RANGES = lv_it_vtref_ranges
         IT_WHERE = lv_it_where
         I_MAX_NUM_BITS = lv_i_max_num_bits
         IT_BILLDOC_SRCITEM = lv_it_billdoc_srcitem
         I_BIT_GRPNO = lv_i_bit_grpno
         I_SRC_GROUP = lv_i_src_group
         IT_SRCTATYPE_RANGES = lv_it_srctatype_ranges
         IT_SRCTAID_RANGES = lv_it_srctaid_ranges
         IT_BITCAT_RANGES = lv_it_bitcat_ranges
         IT_BITTYPE_RANGES = lv_it_bittype_ranges
         IT_SUBPROCESS_RANGES = lv_it_subprocess_ranges
    IMPORTING
         ET_BIT4_IT = lv_et_bit4_it
. " FKK_BIX_BIT4_IT_SELECT




ABAP code using 7.40 inline data declarations to call FM FKK_BIX_BIT4_IT_SELECT

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.

 
 
 
 
 
 
DATA(ld_i_max_num_bits) = 1000.
 
 
 
 
 
 
 
 
 


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!