SAP FKK_OPBUK_CHANGE_CHECK Function Module for
FKK_OPBUK_CHANGE_CHECK is a standard fkk opbuk change check 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 opbuk change check FM, simply by entering the name FKK_OPBUK_CHANGE_CHECK into the relevant SAP transaction such as SE37 or SE38.
Function Group: FKS0
Program Name: SAPLFKS0
Main Program: SAPLFKS0
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FKK_OPBUK_CHANGE_CHECK 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_OPBUK_CHANGE_CHECK'".
EXPORTING
I_VKONT = "Contract Account Number
I_GPART = "Business Partner Number
I_OPBUK_OLD = "
I_OPBUK_NEW = "
EXCEPTIONS
CHANGE_NOT_ALLOWED = 1
IMPORTING Parameters details for FKK_OPBUK_CHANGE_CHECK
I_VKONT - Contract Account Number
Data type: VKONT_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_GPART - Business Partner Number
Data type: GPART_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_OPBUK_OLD -
Data type: OPBUK_KKOptional: No
Call by Reference: No ( called with pass by value option)
I_OPBUK_NEW -
Data type: OPBUK_KKOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
CHANGE_NOT_ALLOWED - Change Is Not Allowed
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FKK_OPBUK_CHANGE_CHECK 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_vkont | TYPE VKONT_KK, " | |||
| lv_change_not_allowed | TYPE VKONT_KK, " | |||
| lv_i_gpart | TYPE GPART_KK, " | |||
| lv_i_opbuk_old | TYPE OPBUK_KK, " | |||
| lv_i_opbuk_new | TYPE OPBUK_KK. " |
|   CALL FUNCTION 'FKK_OPBUK_CHANGE_CHECK' " |
| EXPORTING | ||
| I_VKONT | = lv_i_vkont | |
| I_GPART | = lv_i_gpart | |
| I_OPBUK_OLD | = lv_i_opbuk_old | |
| I_OPBUK_NEW | = lv_i_opbuk_new | |
| EXCEPTIONS | ||
| CHANGE_NOT_ALLOWED = 1 | ||
| . " FKK_OPBUK_CHANGE_CHECK | ||
ABAP code using 7.40 inline data declarations to call FM FKK_OPBUK_CHANGE_CHECK
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