SAP GCFC_VALUE_INPUT Function Module for GBC: Value Entry









GCFC_VALUE_INPUT is a standard gcfc value input 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: Value Entry 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 value input FM, simply by entering the name GCFC_VALUE_INPUT 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_VALUE_INPUT 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_VALUE_INPUT'"GBC: Value Entry
EXPORTING
I_GCCGWA = "
I_TITLE = "
I_VALUE = "

IMPORTING
E_VALUE = "

EXCEPTIONS
ERROR = 1
.



IMPORTING Parameters details for GCFC_VALUE_INPUT

I_GCCGWA -

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

I_TITLE -

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

I_VALUE -

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

EXPORTING Parameters details for GCFC_VALUE_INPUT

E_VALUE -

Data type: GCTP1_VALUE_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_VALUE_INPUT 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_e_value  TYPE GCTP1_VALUE_TYPE, "   
lv_i_gccgwa  TYPE GCTP1_GCCGWA_TYPE, "   
lv_i_title  TYPE TEXT30, "   
lv_i_value  TYPE GCTP1_VALUE_TYPE. "   

  CALL FUNCTION 'GCFC_VALUE_INPUT'  "GBC: Value Entry
    EXPORTING
         I_GCCGWA = lv_i_gccgwa
         I_TITLE = lv_i_title
         I_VALUE = lv_i_value
    IMPORTING
         E_VALUE = lv_e_value
    EXCEPTIONS
        ERROR = 1
. " GCFC_VALUE_INPUT




ABAP code using 7.40 inline data declarations to call FM GCFC_VALUE_INPUT

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!