SAP FKK_SAMPLE_1806 Function Module for Processing Locks: Determine Contract from Contract Lock Object









FKK_SAMPLE_1806 is a standard fkk sample 1806 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Processing Locks: Determine Contract from Contract Lock Object processing and below is the pattern details for this FM, 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 sample 1806 FM, simply by entering the name FKK_SAMPLE_1806 into the relevant SAP transaction such as SE37 or SE38.

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



Function FKK_SAMPLE_1806 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_SAMPLE_1806'"Processing Locks: Determine Contract from Contract Lock Object
EXPORTING
IV_LOOBJ1 = "Lock Object
* IV_LOTYP = "

IMPORTING
EV_VTREF = "Reference Specifications from Contract
EV_GPART = "Business Partner Number
EV_SUBAP = "Subapplication in Contract Accounts Receivable and Payable

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for FKK_SAMPLE_1806

IV_LOOBJ1 - Lock Object

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

IV_LOTYP -

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

EXPORTING Parameters details for FKK_SAMPLE_1806

EV_VTREF - Reference Specifications from Contract

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

EV_GPART - Business Partner Number

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

EV_SUBAP - Subapplication in Contract Accounts Receivable and Payable

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

EXCEPTIONS details

ERROR - Errors have occurred

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for FKK_SAMPLE_1806 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_error  TYPE STRING, "   
lv_ev_vtref  TYPE VTREF_KK, "   
lv_iv_loobj1  TYPE LOOBJ_KK, "   
lv_ev_gpart  TYPE GPART_KK, "   
lv_iv_lotyp  TYPE LOTYP_KK, "   
lv_ev_subap  TYPE SUBAP_KK. "   

  CALL FUNCTION 'FKK_SAMPLE_1806'  "Processing Locks: Determine Contract from Contract Lock Object
    EXPORTING
         IV_LOOBJ1 = lv_iv_loobj1
         IV_LOTYP = lv_iv_lotyp
    IMPORTING
         EV_VTREF = lv_ev_vtref
         EV_GPART = lv_ev_gpart
         EV_SUBAP = lv_ev_subap
    EXCEPTIONS
        ERROR = 1
. " FKK_SAMPLE_1806




ABAP code using 7.40 inline data declarations to call FM FKK_SAMPLE_1806

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!