SAP FKK_BIX_BIT_GET_FIELDS_FOR_MON Function Module for









FKK_BIX_BIT_GET_FIELDS_FOR_MON is a standard fkk bix bit get fields for mon 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 for mon FM, simply by entering the name FKK_BIX_BIT_GET_FIELDS_FOR_MON 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_FOR_MON 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_FOR_MON'"
EXPORTING
* IT_BITCAT = "
* IV_BITSTATUS = "
* IV_BITRECTYPE = "
* IV_STRUCNAME = "

IMPORTING
ET_FIELDS_EXC = "
ET_FIELDS_INC = "
ET_FIELDS_INVISIBLE = "
.



IMPORTING Parameters details for FKK_BIX_BIT_GET_FIELDS_FOR_MON

IT_BITCAT -

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

IV_BITSTATUS -

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

IV_BITRECTYPE -

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

IV_STRUCNAME -

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

EXPORTING Parameters details for FKK_BIX_BIT_GET_FIELDS_FOR_MON

ET_FIELDS_EXC -

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

ET_FIELDS_INC -

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

ET_FIELDS_INVISIBLE -

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

Copy and paste ABAP code example for FKK_BIX_BIT_GET_FIELDS_FOR_MON 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_bitcat  TYPE BITCAT_TAB, "   
lv_et_fields_exc  TYPE FIELDNAME_TAB, "   
lv_iv_bitstatus  TYPE BITSTATUS_KK, "   
lv_et_fields_inc  TYPE FIELDNAME_TAB, "   
lv_iv_bitrectype  TYPE BITRECTYPE_KK, "   
lv_et_fields_invisible  TYPE FIELDNAME_TAB, "   
lv_iv_strucname  TYPE DDOBJNAME. "   

  CALL FUNCTION 'FKK_BIX_BIT_GET_FIELDS_FOR_MON'  "
    EXPORTING
         IT_BITCAT = lv_it_bitcat
         IV_BITSTATUS = lv_iv_bitstatus
         IV_BITRECTYPE = lv_iv_bitrectype
         IV_STRUCNAME = lv_iv_strucname
    IMPORTING
         ET_FIELDS_EXC = lv_et_fields_exc
         ET_FIELDS_INC = lv_et_fields_inc
         ET_FIELDS_INVISIBLE = lv_et_fields_invisible
. " FKK_BIX_BIT_GET_FIELDS_FOR_MON




ABAP code using 7.40 inline data declarations to call FM FKK_BIX_BIT_GET_FIELDS_FOR_MON

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!