SAP FKK_BIX_BIT4_TAB_DELETE Function Module for









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

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



Function FKK_BIX_BIT4_TAB_DELETE 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_TAB_DELETE'"
  EXPORTING
   I_BITCAT =  "Billable Item Class
*  I_BIT4_SUFFIX =  "Sequence Number for Tables with Status Billed
*  IT_BIT4_SUFFIX_RANGES =  "Range Table for BIT4_TAB_SUFFIX_KK
*  I_BIT4_SIMULATED =  "Billing Document Is Simulated
*  I_BILL_CHECK_DATE =  "Billing-To Date for Check of Retention Period
*  I_INV_CHECK_DATE =  "Invoicing To-Date for Check of Retention Period
*  I_WITHOUT_DIALOG =  "
*  I_TESTRUN =  "
*  I_CHECKRUN =  "

 IMPORTING
   ET_BIT4_DEL =  "Analysis of Billed Items for Deletion

EXCEPTIONS
   USER_ABORT = 1
.



IMPORTING Parameters details for FKK_BIX_BIT4_TAB_DELETE

I_BITCAT - Billable Item Class

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

I_BIT4_SUFFIX - Sequence Number for Tables with Status Billed

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

IT_BIT4_SUFFIX_RANGES - Range Table for BIT4_TAB_SUFFIX_KK

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

I_BIT4_SIMULATED - Billing Document Is Simulated

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

I_BILL_CHECK_DATE - Billing-To Date for Check of Retention Period

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

I_INV_CHECK_DATE - Invoicing To-Date for Check of Retention Period

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

I_WITHOUT_DIALOG -

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

I_TESTRUN -

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

I_CHECKRUN -

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

EXPORTING Parameters details for FKK_BIX_BIT4_TAB_DELETE

ET_BIT4_DEL - Analysis of Billed Items for Deletion

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

EXCEPTIONS details

USER_ABORT - Activity cancelled

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_BIX_BIT4_TAB_DELETE 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_i_bitcat  TYPE BITCAT_KK, "   
lv_user_abort  TYPE BITCAT_KK, "   
lv_et_bit4_del  TYPE FKKBIX_BIT4_DEL_CHECK_TAB, "   
lv_i_bit4_suffix  TYPE BIT4_TAB_SUFFIX_KK, "   
lv_it_bit4_suffix_ranges  TYPE FKK_RT_BIT4_TAB_SUFFIX, "   
lv_i_bit4_simulated  TYPE SIMULATED_KK, "   
lv_i_bill_check_date  TYPE BILLCRDATE_TO_KK, "   
lv_i_inv_check_date  TYPE INVCRDATE_TO_KK, "   
lv_i_without_dialog  TYPE XFELD, "   
lv_i_testrun  TYPE XFELD, "   
lv_i_checkrun  TYPE XFELD. "   

  CALL FUNCTION 'FKK_BIX_BIT4_TAB_DELETE'  "
    EXPORTING
         I_BITCAT = lv_i_bitcat
         I_BIT4_SUFFIX = lv_i_bit4_suffix
         IT_BIT4_SUFFIX_RANGES = lv_it_bit4_suffix_ranges
         I_BIT4_SIMULATED = lv_i_bit4_simulated
         I_BILL_CHECK_DATE = lv_i_bill_check_date
         I_INV_CHECK_DATE = lv_i_inv_check_date
         I_WITHOUT_DIALOG = lv_i_without_dialog
         I_TESTRUN = lv_i_testrun
         I_CHECKRUN = lv_i_checkrun
    IMPORTING
         ET_BIT4_DEL = lv_et_bit4_del
    EXCEPTIONS
        USER_ABORT = 1
. " FKK_BIX_BIT4_TAB_DELETE




ABAP code using 7.40 inline data declarations to call FM FKK_BIX_BIT4_TAB_DELETE

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!