SAP OM_GM_CALL_STATUS_FUNCTION Function Module for









OM_GM_CALL_STATUS_FUNCTION is a standard om gm call status function 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 om gm call status function FM, simply by entering the name OM_GM_CALL_STATUS_FUNCTION into the relevant SAP transaction such as SE37 or SE38.

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



Function OM_GM_CALL_STATUS_FUNCTION 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 'OM_GM_CALL_STATUS_FUNCTION'"
  EXPORTING
   STATUS_OBJECT =  "
   CALL_FUNCTION =  "
   STATUS_INTERFACE =  "
*  SCENARIO =  "
*  PLANVERSION =  "
*  DATE =  "
*  FUZZY_BEGDA =  "
*  FUZZY_ENDDA =  "
*  CHANGEMODE =  "

CHANGING
*  FCODE =  "

TABLES
*  INCLUDING_CODES =  "
.



IMPORTING Parameters details for OM_GM_CALL_STATUS_FUNCTION

STATUS_OBJECT -

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

CALL_FUNCTION -

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

STATUS_INTERFACE -

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

SCENARIO -

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

PLANVERSION -

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

DATE -

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

FUZZY_BEGDA -

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

FUZZY_ENDDA -

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

CHANGEMODE -

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

CHANGING Parameters details for OM_GM_CALL_STATUS_FUNCTION

FCODE -

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

TABLES Parameters details for OM_GM_CALL_STATUS_FUNCTION

INCLUDING_CODES -

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

Copy and paste ABAP code example for OM_GM_CALL_STATUS_FUNCTION 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_fcode  TYPE SYUCOMM, "   
lv_status_object  TYPE OMCLASSKEY, "   
lt_including_codes  TYPE STANDARD TABLE OF OMSTAFCODE, "   
lv_call_function  TYPE CHAR40, "   
lv_status_interface  TYPE OMSTATINT, "   
lv_scenario  TYPE HROMSCEN, "   
lv_planversion  TYPE PLVAR, "   
lv_date  TYPE SY-DATUM, "   
lv_fuzzy_begda  TYPE SY-DATUM, "   
lv_fuzzy_endda  TYPE SY-DATUM, "   
lv_changemode  TYPE OMACTMODE. "   

  CALL FUNCTION 'OM_GM_CALL_STATUS_FUNCTION'  "
    EXPORTING
         STATUS_OBJECT = lv_status_object
         CALL_FUNCTION = lv_call_function
         STATUS_INTERFACE = lv_status_interface
         SCENARIO = lv_scenario
         PLANVERSION = lv_planversion
         DATE = lv_date
         FUZZY_BEGDA = lv_fuzzy_begda
         FUZZY_ENDDA = lv_fuzzy_endda
         CHANGEMODE = lv_changemode
    CHANGING
         FCODE = lv_fcode
    TABLES
         INCLUDING_CODES = lt_including_codes
. " OM_GM_CALL_STATUS_FUNCTION




ABAP code using 7.40 inline data declarations to call FM OM_GM_CALL_STATUS_FUNCTION

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.

 
 
 
 
 
 
 
"SELECT single DATUM FROM SY INTO @DATA(ld_date).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_begda).
 
"SELECT single DATUM FROM SY INTO @DATA(ld_fuzzy_endda).
 
 


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!