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

Function FKK_BIX_BIT_GET_FIELDS_ACTIVE 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_BIT_GET_FIELDS_ACTIVE'".
EXPORTING
* IV_BITCAT = "
* IRT_BITCAT = "
* IV_BITSTATUS = "
* IRT_BITSTATUS = "
* IV_BITRECTYPE = "
* IRT_BITRECTYPE = "
IMPORTING
ET_FIELDS_ACTIVE = "
EXCEPTIONS
NOT_FOUND = 1
IMPORTING Parameters details for FKK_BIX_BIT_GET_FIELDS_ACTIVE
IV_BITCAT -
Data type: BITCAT_KKOptional: Yes
Call by Reference: Yes
IRT_BITCAT -
Data type: FKK_RT_BITCATOptional: Yes
Call by Reference: Yes
IV_BITSTATUS -
Data type: BITSTATUS_KKOptional: Yes
Call by Reference: Yes
IRT_BITSTATUS -
Data type: FKK_RT_BITSTATUSOptional: Yes
Call by Reference: Yes
IV_BITRECTYPE -
Data type: BITRECTYPE_KKOptional: Yes
Call by Reference: Yes
IRT_BITRECTYPE -
Data type: FKK_RT_BITRECTYPEOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for FKK_BIX_BIT_GET_FIELDS_ACTIVE
ET_FIELDS_ACTIVE -
Data type: FIELDNAME_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_BIX_BIT_GET_FIELDS_ACTIVE 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_not_found | TYPE BITCAT_KK, " | |||
| lv_et_fields_active | TYPE FIELDNAME_TAB, " | |||
| lv_irt_bitcat | TYPE FKK_RT_BITCAT, " | |||
| lv_iv_bitstatus | TYPE BITSTATUS_KK, " | |||
| lv_irt_bitstatus | TYPE FKK_RT_BITSTATUS, " | |||
| lv_iv_bitrectype | TYPE BITRECTYPE_KK, " | |||
| lv_irt_bitrectype | TYPE FKK_RT_BITRECTYPE. " |
|   CALL FUNCTION 'FKK_BIX_BIT_GET_FIELDS_ACTIVE' " |
| EXPORTING | ||
| IV_BITCAT | = lv_iv_bitcat | |
| IRT_BITCAT | = lv_irt_bitcat | |
| IV_BITSTATUS | = lv_iv_bitstatus | |
| IRT_BITSTATUS | = lv_irt_bitstatus | |
| IV_BITRECTYPE | = lv_iv_bitrectype | |
| IRT_BITRECTYPE | = lv_irt_bitrectype | |
| IMPORTING | ||
| ET_FIELDS_ACTIVE | = lv_et_fields_active | |
| EXCEPTIONS | ||
| NOT_FOUND = 1 | ||
| . " FKK_BIX_BIT_GET_FIELDS_ACTIVE | ||
ABAP code using 7.40 inline data declarations to call FM FKK_BIX_BIT_GET_FIELDS_ACTIVE
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