SAP GCFC_OBJKEY_CHECK Function Module for GBC: Checks Whether Key Fields Exist for an Object









GCFC_OBJKEY_CHECK is a standard gcfc objkey check SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for GBC: Checks Whether Key Fields Exist for an 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 gcfc objkey check FM, simply by entering the name GCFC_OBJKEY_CHECK into the relevant SAP transaction such as SE37 or SE38.

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



Function GCFC_OBJKEY_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 'GCFC_OBJKEY_CHECK'"GBC: Checks Whether Key Fields Exist for an Object
EXPORTING
I_HOME = "
I_OBJART = "
* I_METHOD = "

IMPORTING
E_KEY_EXIST = "

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for GCFC_OBJKEY_CHECK

I_HOME -

Data type: GCTP1_HOME_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_OBJART -

Data type: GCTP1_OBJART_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

I_METHOD -

Data type: GCTP1_METHOD_TYPE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for GCFC_OBJKEY_CHECK

E_KEY_EXIST -

Data type: GCTP1_FLG_TYPE
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GCFC_OBJKEY_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_error  TYPE STRING, "   
lv_i_home  TYPE GCTP1_HOME_TYPE, "   
lv_e_key_exist  TYPE GCTP1_FLG_TYPE, "   
lv_i_objart  TYPE GCTP1_OBJART_TYPE, "   
lv_i_method  TYPE GCTP1_METHOD_TYPE. "   

  CALL FUNCTION 'GCFC_OBJKEY_CHECK'  "GBC: Checks Whether Key Fields Exist for an Object
    EXPORTING
         I_HOME = lv_i_home
         I_OBJART = lv_i_objart
         I_METHOD = lv_i_method
    IMPORTING
         E_KEY_EXIST = lv_e_key_exist
    EXCEPTIONS
        ERROR = 1
. " GCFC_OBJKEY_CHECK




ABAP code using 7.40 inline data declarations to call FM GCFC_OBJKEY_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



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!