SAP UMM_API_GET_MULTI_FRAMEDATA_SR Function Module for









UMM_API_GET_MULTI_FRAMEDATA_SR is a standard umm api get multi framedata sr 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 umm api get multi framedata sr FM, simply by entering the name UMM_API_GET_MULTI_FRAMEDATA_SR into the relevant SAP transaction such as SE37 or SE38.

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



Function UMM_API_GET_MULTI_FRAMEDATA_SR 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 'UMM_API_GET_MULTI_FRAMEDATA_SR'"
  EXPORTING
   I_CONAME =  "Technical Name of a Management Cockpit
*  I_IGNORE_DB_BUFFER = ' ' "Flag (X or Blank)
   I_WANO =  "Number of a Wall in the Management Cockpit
   I_LVNO =  "Number of a Logical View in the Wall
   I_FRNO =  "Number of a Frame in a Logical View
   IR_BW =  "MC: Access to BW Transaction Data for Frames
   IR_BIC =  "MC : BIC - Interface
   IR_COCKPIT =  "MC Cockpit Class
*  I_GRA_DATA = 'X' "Flag (X or Blank)
*  I_BIC_DATA = 'X' "Flag (X or Blank)

 IMPORTING
   E_SUBRC =  "Return Value, Return Value after ABAP Statements
   ET_FRAME_ERRMSG =  "Table Type: Error Message for Frame
   ET_TEXTS =  "Long Descriptions for Internet Graphics Server
   ED_TIMESTAMP =  "UTC Time Stamp in Short Form (YYYYMMDDhhmmss)
   E_T_FRS_GRATEXTS =  "Structure: Frame Graphics Text

TABLES
*  E_T_FRS_CHARTDATA =  "Data for Multi-Frames
*  E_T_FRS_LEGDATA =  "Legend Data for Multi-Frames
*  IT_RUNTIME_VAR =  "Runtime Variable and Value Structure
*  ET_BIC_FRAME_DATA =  "
*  E_T_FRS_LEGSTRUCT =  "
*  E_T_FRS_CHARTUNITS =  "Structure: Frame Graphics Axis Unit
*  E_T_FRS_TACHORANGE =  "Structure: Value Ranges for Tachometer Type of Frame
*  E_T_FRS_QUADRANGE =  "Structure: Grahpics Value Range for 4 Quadrants Frames
.



IMPORTING Parameters details for UMM_API_GET_MULTI_FRAMEDATA_SR

I_CONAME - Technical Name of a Management Cockpit

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

I_IGNORE_DB_BUFFER - Flag (X or Blank)

Data type: AS4FLAG
Default: ' '
Optional: No
Call by Reference: Yes

I_WANO - Number of a Wall in the Management Cockpit

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

I_LVNO - Number of a Logical View in the Wall

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

I_FRNO - Number of a Frame in a Logical View

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

IR_BW - MC: Access to BW Transaction Data for Frames

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

IR_BIC - MC : BIC - Interface

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

IR_COCKPIT - MC Cockpit Class

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

I_GRA_DATA - Flag (X or Blank)

Data type: AS4FLAG
Default: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)

I_BIC_DATA - Flag (X or Blank)

Data type: AS4FLAG
Default: 'X'
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for UMM_API_GET_MULTI_FRAMEDATA_SR

E_SUBRC - Return Value, Return Value after ABAP Statements

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

ET_FRAME_ERRMSG - Table Type: Error Message for Frame

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

ET_TEXTS - Long Descriptions for Internet Graphics Server

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

ED_TIMESTAMP - UTC Time Stamp in Short Form (YYYYMMDDhhmmss)

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

E_T_FRS_GRATEXTS - Structure: Frame Graphics Text

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

TABLES Parameters details for UMM_API_GET_MULTI_FRAMEDATA_SR

E_T_FRS_CHARTDATA - Data for Multi-Frames

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

E_T_FRS_LEGDATA - Legend Data for Multi-Frames

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

IT_RUNTIME_VAR - Runtime Variable and Value Structure

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

ET_BIC_FRAME_DATA -

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

E_T_FRS_LEGSTRUCT -

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

E_T_FRS_CHARTUNITS - Structure: Frame Graphics Axis Unit

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

E_T_FRS_TACHORANGE - Structure: Value Ranges for Tachometer Type of Frame

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

E_T_FRS_QUADRANGE - Structure: Grahpics Value Range for 4 Quadrants Frames

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

Copy and paste ABAP code example for UMM_API_GET_MULTI_FRAMEDATA_SR 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_e_subrc  TYPE SY-SUBRC, "   
lv_i_coname  TYPE UMM_Y_CONAME, "   
lt_e_t_frs_chartdata  TYPE STANDARD TABLE OF UMM_YS_FRS_CHARTDATA, "   
lv_i_ignore_db_buffer  TYPE AS4FLAG, "   ' '
lv_i_wano  TYPE UMM_Y_WANO, "   
lv_et_frame_errmsg  TYPE UMM_YT_FRAME_ERROR_MESSAGE, "   
lt_e_t_frs_legdata  TYPE STANDARD TABLE OF UMM_YS_FRS_LEGDATA, "   
lv_i_lvno  TYPE UMM_Y_LVNO, "   
lv_et_texts  TYPE IGS_LABEL_TAB, "   
lt_it_runtime_var  TYPE STANDARD TABLE OF UMM_YS_RUNTIME_VAR, "   
lv_i_frno  TYPE UMM_Y_FRNO, "   
lv_ed_timestamp  TYPE RSTIMESTMP, "   
lt_et_bic_frame_data  TYPE STANDARD TABLE OF UMM_YS_FR_BICDATA, "   
lv_ir_bw  TYPE CL_UMM_BW_FRAMES_MC, "   
lv_e_t_frs_gratexts  TYPE UMM_YT_GRATEXT, "   
lt_e_t_frs_legstruct  TYPE STANDARD TABLE OF UMM_YS_LEGSTRUCT, "   
lv_ir_bic  TYPE CL_UMM_BIC, "   
lt_e_t_frs_chartunits  TYPE STANDARD TABLE OF UMM_YS_FRS_CHART_UNITS, "   
lv_ir_cockpit  TYPE CL_UMM_COCKPIT, "   
lt_e_t_frs_tachorange  TYPE STANDARD TABLE OF UMM_YS_FRS_CHARTRANGES, "   
lv_i_gra_data  TYPE AS4FLAG, "   'X'
lt_e_t_frs_quadrange  TYPE STANDARD TABLE OF UMM_YS_FRS_CHARTRANGES_QUAD, "   
lv_i_bic_data  TYPE AS4FLAG. "   'X'

  CALL FUNCTION 'UMM_API_GET_MULTI_FRAMEDATA_SR'  "
    EXPORTING
         I_CONAME = lv_i_coname
         I_IGNORE_DB_BUFFER = lv_i_ignore_db_buffer
         I_WANO = lv_i_wano
         I_LVNO = lv_i_lvno
         I_FRNO = lv_i_frno
         IR_BW = lv_ir_bw
         IR_BIC = lv_ir_bic
         IR_COCKPIT = lv_ir_cockpit
         I_GRA_DATA = lv_i_gra_data
         I_BIC_DATA = lv_i_bic_data
    IMPORTING
         E_SUBRC = lv_e_subrc
         ET_FRAME_ERRMSG = lv_et_frame_errmsg
         ET_TEXTS = lv_et_texts
         ED_TIMESTAMP = lv_ed_timestamp
         E_T_FRS_GRATEXTS = lv_e_t_frs_gratexts
    TABLES
         E_T_FRS_CHARTDATA = lt_e_t_frs_chartdata
         E_T_FRS_LEGDATA = lt_e_t_frs_legdata
         IT_RUNTIME_VAR = lt_it_runtime_var
         ET_BIC_FRAME_DATA = lt_et_bic_frame_data
         E_T_FRS_LEGSTRUCT = lt_e_t_frs_legstruct
         E_T_FRS_CHARTUNITS = lt_e_t_frs_chartunits
         E_T_FRS_TACHORANGE = lt_e_t_frs_tachorange
         E_T_FRS_QUADRANGE = lt_e_t_frs_quadrange
. " UMM_API_GET_MULTI_FRAMEDATA_SR




ABAP code using 7.40 inline data declarations to call FM UMM_API_GET_MULTI_FRAMEDATA_SR

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 SUBRC FROM SY INTO @DATA(ld_e_subrc).
 
 
 
DATA(ld_i_ignore_db_buffer) = ' '.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
DATA(ld_i_gra_data) = 'X'.
 
 
DATA(ld_i_bic_data) = 'X'.
 


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!