SAP C_MONITOR_PG_INIT_V10 Function Module for Initialization Module for PGA Monitor









C_MONITOR_PG_INIT_V10 is a standard c monitor pg init v10 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Initialization Module for PGA Monitor 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 c monitor pg init v10 FM, simply by entering the name C_MONITOR_PG_INIT_V10 into the relevant SAP transaction such as SE37 or SE38.

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



Function C_MONITOR_PG_INIT_V10 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 'C_MONITOR_PG_INIT_V10'"Initialization Module for PGA Monitor
  EXPORTING
*  I_REMOTE_SYSTEM =  "Logical name for a database connection
   I_DBID =  "Oracle monitoring: database id
   I_DB_REL =  "Oracle release number
   I_INST_ID =  "Oracle monitor: Instance ID
   I_SNAPSHOT_FROM =  "Oracle monitor: snapshot ID
   I_SNAPSHOT_TO =  "Oracle monitor: snapshot ID
   I_SNAPDATE_FROM =  "Oracle: snapshot time
   I_SNAPDATE_TO =  "Oracle: snapshot time
   IS_RAC =  "Is it a RAC DB

TABLES
   PGASTA =  "PGA Monitoring: (g)v$SGA table
   WOAEXE =  "PGA Monitoring: (g)v$SQL (g)v$YSSTAT  table
   SQLTXT =  "PGA Monitoring: (g)v$SQLTEXT table
   PEROPT =  "PGA Monitoring: (g)v$SQL (g)v$SQL_WORKAREA_HISTOGRAM  table
   PGAADV =  "PGA Monitoring: (g)v$PGA_TARGET_ADVICE  table
   PGAHIS =  "PGA Monitoring: (g)v$PGA_TARGET_ADVICE_HISTOGRAM  table
   PROCES =  "PGA Monitoring: (g)v$PROCESS  table
   SQLHIS =  "PGA Monitoring: (g)v$SQL (g)v$SQL_WORKAREA_HISTOGRAM  table
   SQLOMP =  "PGA Monitoring: (g)v$SQL_WORKAREA  table
   SQLWOA =  "PGA Monitoring: (g)v$SQL_WORKAREA table
   WOAACT =  "PGA Monitoring: (g)v$SQL_WORKAREA_ACTIVE  table
.



IMPORTING Parameters details for C_MONITOR_PG_INIT_V10

I_REMOTE_SYSTEM - Logical name for a database connection

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

I_DBID - Oracle monitoring: database id

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

I_DB_REL - Oracle release number

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

I_INST_ID - Oracle monitor: Instance ID

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

I_SNAPSHOT_FROM - Oracle monitor: snapshot ID

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

I_SNAPSHOT_TO - Oracle monitor: snapshot ID

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

I_SNAPDATE_FROM - Oracle: snapshot time

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

I_SNAPDATE_TO - Oracle: snapshot time

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

IS_RAC - Is it a RAC DB

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

TABLES Parameters details for C_MONITOR_PG_INIT_V10

PGASTA - PGA Monitoring: (g)v$SGA table

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

WOAEXE - PGA Monitoring: (g)v$SQL (g)v$YSSTAT table

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

SQLTXT - PGA Monitoring: (g)v$SQLTEXT table

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

PEROPT - PGA Monitoring: (g)v$SQL (g)v$SQL_WORKAREA_HISTOGRAM table

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

PGAADV - PGA Monitoring: (g)v$PGA_TARGET_ADVICE table

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

PGAHIS - PGA Monitoring: (g)v$PGA_TARGET_ADVICE_HISTOGRAM table

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

PROCES - PGA Monitoring: (g)v$PROCESS table

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

SQLHIS - PGA Monitoring: (g)v$SQL (g)v$SQL_WORKAREA_HISTOGRAM table

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

SQLOMP - PGA Monitoring: (g)v$SQL_WORKAREA table

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

SQLWOA - PGA Monitoring: (g)v$SQL_WORKAREA table

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

WOAACT - PGA Monitoring: (g)v$SQL_WORKAREA_ACTIVE table

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

Copy and paste ABAP code example for C_MONITOR_PG_INIT_V10 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:
lt_pgasta  TYPE STANDARD TABLE OF GPG_TR_PGASTA, "   
lv_i_remote_system  TYPE DBCON_NAME, "   
lt_woaexe  TYPE STANDARD TABLE OF GPG_TR_WOAEXE, "   
lt_sqltxt  TYPE STANDARD TABLE OF GPG_TR_SQLTEXT, "   
lv_i_dbid  TYPE ORA_DBID, "   
lt_peropt  TYPE STANDARD TABLE OF GPG_TR_PEROPT, "   
lt_pgaadv  TYPE STANDARD TABLE OF GPG_TR_PGAADV, "   
lv_i_db_rel  TYPE ORA_REL_NUMBER, "   
lt_pgahis  TYPE STANDARD TABLE OF GPG_TR_PGAHIS, "   
lv_i_inst_id  TYPE ORA_INST_ID, "   
lt_proces  TYPE STANDARD TABLE OF GPG_TR_PROCES, "   
lv_i_snapshot_from  TYPE ORA_SNAPSHOT_ID, "   
lt_sqlhis  TYPE STANDARD TABLE OF GPG_TR_SQLHIS, "   
lv_i_snapshot_to  TYPE ORA_SNAPSHOT_ID, "   
lt_sqlomp  TYPE STANDARD TABLE OF GPG_TR_SQLOMP, "   
lv_i_snapdate_from  TYPE ORA_SNAPSHOT_TIME, "   
lt_sqlwoa  TYPE STANDARD TABLE OF GPG_TR_SQLWOA, "   
lv_i_snapdate_to  TYPE ORA_SNAPSHOT_TIME, "   
lv_is_rac  TYPE C, "   
lt_woaact  TYPE STANDARD TABLE OF GPG_TR_WOAACT. "   

  CALL FUNCTION 'C_MONITOR_PG_INIT_V10'  "Initialization Module for PGA Monitor
    EXPORTING
         I_REMOTE_SYSTEM = lv_i_remote_system
         I_DBID = lv_i_dbid
         I_DB_REL = lv_i_db_rel
         I_INST_ID = lv_i_inst_id
         I_SNAPSHOT_FROM = lv_i_snapshot_from
         I_SNAPSHOT_TO = lv_i_snapshot_to
         I_SNAPDATE_FROM = lv_i_snapdate_from
         I_SNAPDATE_TO = lv_i_snapdate_to
         IS_RAC = lv_is_rac
    TABLES
         PGASTA = lt_pgasta
         WOAEXE = lt_woaexe
         SQLTXT = lt_sqltxt
         PEROPT = lt_peropt
         PGAADV = lt_pgaadv
         PGAHIS = lt_pgahis
         PROCES = lt_proces
         SQLHIS = lt_sqlhis
         SQLOMP = lt_sqlomp
         SQLWOA = lt_sqlwoa
         WOAACT = lt_woaact
. " C_MONITOR_PG_INIT_V10




ABAP code using 7.40 inline data declarations to call FM C_MONITOR_PG_INIT_V10

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!