SAP FKK_BIX_BIT_MD_REPLACE Function Module for









FKK_BIX_BIT_MD_REPLACE is a standard fkk bix bit md replace 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 md replace FM, simply by entering the name FKK_BIX_BIT_MD_REPLACE into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_BIX_BIT_MD_REPLACE 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_MD_REPLACE'"
EXPORTING
I_GPART = "
I_VKONT = "
I_VTREF = "

IMPORTING
E_GPART = "
E_VKONT = "
E_VTREF = "
E_REPLACED = "

EXCEPTIONS
NOT_REPLACED = 1
.



IMPORTING Parameters details for FKK_BIX_BIT_MD_REPLACE

I_GPART -

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

I_VKONT -

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

I_VTREF -

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

EXPORTING Parameters details for FKK_BIX_BIT_MD_REPLACE

E_GPART -

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

E_VKONT -

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

E_VTREF -

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

E_REPLACED -

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

EXCEPTIONS details

NOT_REPLACED -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_BIX_BIT_MD_REPLACE 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_e_gpart  TYPE GPART_KK, "   
lv_i_gpart  TYPE GPART_KK, "   
lv_not_replaced  TYPE GPART_KK, "   
lv_e_vkont  TYPE VKONT_KK, "   
lv_i_vkont  TYPE VKONT_KK, "   
lv_e_vtref  TYPE VTREF_KK, "   
lv_i_vtref  TYPE VTREF_KK, "   
lv_e_replaced  TYPE XFELD. "   

  CALL FUNCTION 'FKK_BIX_BIT_MD_REPLACE'  "
    EXPORTING
         I_GPART = lv_i_gpart
         I_VKONT = lv_i_vkont
         I_VTREF = lv_i_vtref
    IMPORTING
         E_GPART = lv_e_gpart
         E_VKONT = lv_e_vkont
         E_VTREF = lv_e_vtref
         E_REPLACED = lv_e_replaced
    EXCEPTIONS
        NOT_REPLACED = 1
. " FKK_BIX_BIT_MD_REPLACE




ABAP code using 7.40 inline data declarations to call FM FKK_BIX_BIT_MD_REPLACE

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!