SAP FCOM_OBJECT_WHERE_USED Function Module for









FCOM_OBJECT_WHERE_USED is a standard fcom object where used 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 fcom object where used FM, simply by entering the name FCOM_OBJECT_WHERE_USED into the relevant SAP transaction such as SE37 or SE38.

Function Group: FCOM_MD_GENERAL
Program Name: SAPLFCOM_MD_GENERAL
Main Program: SAPLFCOM_MD_GENERAL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function FCOM_OBJECT_WHERE_USED 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 'FCOM_OBJECT_WHERE_USED'"
  EXPORTING
*  ID_OBJECTID =  "
*  IB_CYCLES_OM =  "
*  IB_CYCLES_PA =  "
*  IB_CATS_TRANSFER =  "
*  IB_SETTLEMENT_RULES =  "
*  IB_ORDERS =  "
*  IB_FIXED_ASSETS =  "
*  IB_PROJECTS =  "
*  IB_COSTCENTERS =  "
*  IB_COSTOBJECTS =  "
*  IB_MATERIALS =  "
*  ID_OBJECTTYPE =  "
*  IB_GROUPS =  "
*  ID_COSTCENTER =  "
*  ID_PROFITCENTER =  "
*  ID_INTERNAL_ORDER =  "
*  ID_CONTROLLING_AREA =  "
*  ID_DATE = SY-DATUM "
*  IB_SPLITTING_STRUCTURES =  "
*  IB_ACTIVITY_TYPES =  "

 IMPORTING
   ES_RETURN =  "

TABLES
   ET_RESULT =  "
.



IMPORTING Parameters details for FCOM_OBJECT_WHERE_USED

ID_OBJECTID -

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

IB_CYCLES_OM -

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

IB_CYCLES_PA -

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

IB_CATS_TRANSFER -

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

IB_SETTLEMENT_RULES -

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

IB_ORDERS -

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

IB_FIXED_ASSETS -

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

IB_PROJECTS -

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

IB_COSTCENTERS -

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

IB_COSTOBJECTS -

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

IB_MATERIALS -

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

ID_OBJECTTYPE -

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

IB_GROUPS -

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

ID_COSTCENTER -

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

ID_PROFITCENTER -

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

ID_INTERNAL_ORDER -

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

ID_CONTROLLING_AREA -

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

ID_DATE -

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

IB_SPLITTING_STRUCTURES -

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

IB_ACTIVITY_TYPES -

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

EXPORTING Parameters details for FCOM_OBJECT_WHERE_USED

ES_RETURN -

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

TABLES Parameters details for FCOM_OBJECT_WHERE_USED

ET_RESULT -

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

Copy and paste ABAP code example for FCOM_OBJECT_WHERE_USED 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_es_return  TYPE BAPIRET2, "   
lt_et_result  TYPE STANDARD TABLE OF FCOM_S_WHERE_USED, "   
lv_id_objectid  TYPE STRING, "   
lv_ib_cycles_om  TYPE BOOLEAN, "   
lv_ib_cycles_pa  TYPE BOOLEAN, "   
lv_ib_cats_transfer  TYPE BOOLEAN, "   
lv_ib_settlement_rules  TYPE BOOLEAN, "   
lv_ib_orders  TYPE BOOLEAN, "   
lv_ib_fixed_assets  TYPE BOOLEAN, "   
lv_ib_projects  TYPE BOOLEAN, "   
lv_ib_costcenters  TYPE BOOLEAN, "   
lv_ib_costobjects  TYPE BOOLEAN, "   
lv_ib_materials  TYPE BOOLEAN, "   
lv_id_objecttype  TYPE FPB_OBJTYPE, "   
lv_ib_groups  TYPE BOOLEAN, "   
lv_id_costcenter  TYPE KOSTL, "   
lv_id_profitcenter  TYPE PRCTR, "   
lv_id_internal_order  TYPE AUFNR, "   
lv_id_controlling_area  TYPE KOKRS, "   
lv_id_date  TYPE DATUM, "   SY-DATUM
lv_ib_splitting_structures  TYPE BOOLEAN, "   
lv_ib_activity_types  TYPE BOOLEAN. "   

  CALL FUNCTION 'FCOM_OBJECT_WHERE_USED'  "
    EXPORTING
         ID_OBJECTID = lv_id_objectid
         IB_CYCLES_OM = lv_ib_cycles_om
         IB_CYCLES_PA = lv_ib_cycles_pa
         IB_CATS_TRANSFER = lv_ib_cats_transfer
         IB_SETTLEMENT_RULES = lv_ib_settlement_rules
         IB_ORDERS = lv_ib_orders
         IB_FIXED_ASSETS = lv_ib_fixed_assets
         IB_PROJECTS = lv_ib_projects
         IB_COSTCENTERS = lv_ib_costcenters
         IB_COSTOBJECTS = lv_ib_costobjects
         IB_MATERIALS = lv_ib_materials
         ID_OBJECTTYPE = lv_id_objecttype
         IB_GROUPS = lv_ib_groups
         ID_COSTCENTER = lv_id_costcenter
         ID_PROFITCENTER = lv_id_profitcenter
         ID_INTERNAL_ORDER = lv_id_internal_order
         ID_CONTROLLING_AREA = lv_id_controlling_area
         ID_DATE = lv_id_date
         IB_SPLITTING_STRUCTURES = lv_ib_splitting_structures
         IB_ACTIVITY_TYPES = lv_ib_activity_types
    IMPORTING
         ES_RETURN = lv_es_return
    TABLES
         ET_RESULT = lt_et_result
. " FCOM_OBJECT_WHERE_USED




ABAP code using 7.40 inline data declarations to call FM FCOM_OBJECT_WHERE_USED

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.

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_id_date) = SY-DATUM.
 
 
 


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!