SAP FC_PROP_DECIDE Function Module for









FC_PROP_DECIDE is a standard fc prop decide 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 fc prop decide FM, simply by entering the name FC_PROP_DECIDE into the relevant SAP transaction such as SE37 or SE38.

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



Function FC_PROP_DECIDE 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 'FC_PROP_DECIDE'"
  EXPORTING
*  E_ITCLG =  "
*  ET_KFIG_CP =  "
*  ET_KFIG_DEL =  "
*  ET_KFIG_NIPCP =  "
*  ES_KEY =  "
*  E_RVERS =  "
*  E_DIMEN =  "
*  E_RYEAR =  "
*  E_PLEVL =  "
*  EST_CU_PROP =  "
*  E_FIELD_CLEAR =  "
*  ET_FIELDS =  "
*  ET_KFIG =  "

 IMPORTING
   IT_NIPCP =  "
   IT_MESSAGE_GEN =  "
   IT_MESSAGE =  "

CHANGING
*  CT_DATA =  "

EXCEPTIONS
   FIELDNAME_WRONG = 1    FIELDNAME_MISSING = 2    VALUE_MISSING = 3
.



IMPORTING Parameters details for FC_PROP_DECIDE

E_ITCLG -

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

ET_KFIG_CP -

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

ET_KFIG_DEL -

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

ET_KFIG_NIPCP -

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

ES_KEY -

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

E_RVERS -

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

E_DIMEN -

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

E_RYEAR -

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

E_PLEVL -

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

EST_CU_PROP -

Data type:
Optional: Yes
Call by Reference: Yes

E_FIELD_CLEAR -

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

ET_FIELDS -

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

ET_KFIG -

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

EXPORTING Parameters details for FC_PROP_DECIDE

IT_NIPCP -

Data type: ANY TABLE
Optional: No
Call by Reference: Yes

IT_MESSAGE_GEN -

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

IT_MESSAGE -

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

CHANGING Parameters details for FC_PROP_DECIDE

CT_DATA -

Data type: ANY TABLE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

FIELDNAME_WRONG -

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

FIELDNAME_MISSING -

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

VALUE_MISSING -

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

Copy and paste ABAP code example for FC_PROP_DECIDE 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_ct_data  TYPE ANY TABLE, "   
lv_e_itclg  TYPE FC_ITCLG, "   
lv_it_nipcp  TYPE ANY TABLE, "   
lv_fieldname_wrong  TYPE ANY TABLE, "   
lv_et_kfig_cp  TYPE FC00_T_FIELDS, "   
lv_et_kfig_del  TYPE FC00_T_FIELDS, "   
lv_et_kfig_nipcp  TYPE FC00_T_FIELDS, "   
lv_es_key  TYPE FC00_T_FIELDS, "   
lv_e_rvers  TYPE FC_RVERS, "   
lv_it_message_gen  TYPE FC00_T_MESSAGE, "   
lv_fieldname_missing  TYPE FC00_T_MESSAGE, "   
lv_e_dimen  TYPE FC_DIMEN, "   
lv_it_message  TYPE FC00_T_MESSAGE, "   
lv_value_missing  TYPE FC00_T_MESSAGE, "   
lv_e_ryear  TYPE FC_RYEAR, "   
lv_e_plevl  TYPE FC_PLEVL, "   
lv_est_cu_prop  TYPE FC_PLEVL, "   
lv_e_field_clear  TYPE FC_FIELDNAME, "   
lv_et_fields  TYPE FC00_T_FIELDS, "   
lv_et_kfig  TYPE FC00_T_FIELDS. "   

  CALL FUNCTION 'FC_PROP_DECIDE'  "
    EXPORTING
         E_ITCLG = lv_e_itclg
         ET_KFIG_CP = lv_et_kfig_cp
         ET_KFIG_DEL = lv_et_kfig_del
         ET_KFIG_NIPCP = lv_et_kfig_nipcp
         ES_KEY = lv_es_key
         E_RVERS = lv_e_rvers
         E_DIMEN = lv_e_dimen
         E_RYEAR = lv_e_ryear
         E_PLEVL = lv_e_plevl
         EST_CU_PROP = lv_est_cu_prop
         E_FIELD_CLEAR = lv_e_field_clear
         ET_FIELDS = lv_et_fields
         ET_KFIG = lv_et_kfig
    IMPORTING
         IT_NIPCP = lv_it_nipcp
         IT_MESSAGE_GEN = lv_it_message_gen
         IT_MESSAGE = lv_it_message
    CHANGING
         CT_DATA = lv_ct_data
    EXCEPTIONS
        FIELDNAME_WRONG = 1
        FIELDNAME_MISSING = 2
        VALUE_MISSING = 3
. " FC_PROP_DECIDE




ABAP code using 7.40 inline data declarations to call FM FC_PROP_DECIDE

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!