SAP ORA_BW_GET_DATA Function Module for Get the data from gv$waitstat or its snapshot copy

Search SAP Function Modules

ORA_BW_GET_DATA is a standard ora bw get data SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get the data from gv$waitstat or its snapshot copy 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 ora bw get data FM, simply by entering the name ORA_BW_GET_DATA into the relevant SAP transaction such as SE37 or SE38.

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

Function ORA_BW_GET_DATA 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 'ORA_BW_GET_DATA'"Get the data from gv$waitstat or its snapshot copy
  EXPORTING
*  I_INST_ID =  "Oracle monitor: Instance ID
   I_SNAPSHOT_FROM =  "Snapshot ID (From)
   I_SNAPSHOT_TO =  "Snapshot ID (To)

 IMPORTING
   E_IS_RAC =  "Is RAC, Y/N?
   E_DB_UPTIME =  "Total Time the DB has been up
   E_CURR_TIME =  "Date and Time, Current Application Server Time
   E_CURR_DATE =  "Date and time, current (application server) date
   E_CURR_SYSTEM =  "Name of SAP R/3 System

TABLES
   T_BBW =  "Structure for use in the Buffer Busy Wait Monitor
   T_BBW_TOT =  "Structure for use in the Buffer Busy Wait Monitor

EXCEPTIONS
   WRONG_DATABASE = 1    WRONG_ORACLE_RELEASE = 2    DB_RELEASE_UNKNOWN = 3    WRONG_INSTANCE = 4 

.

IMPORTING Parameters details for ORA_BW_GET_DATA

I_INST_ID - Oracle monitor: Instance ID

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

I_SNAPSHOT_FROM - Snapshot ID (From)

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

I_SNAPSHOT_TO - Snapshot ID (To)

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

EXPORTING Parameters details for ORA_BW_GET_DATA

E_IS_RAC - Is RAC, Y/N?

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

E_DB_UPTIME - Total Time the DB has been up

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

E_CURR_TIME - Date and Time, Current Application Server Time

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

E_CURR_DATE - Date and time, current (application server) date

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

E_CURR_SYSTEM - Name of SAP R/3 System

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

TABLES Parameters details for ORA_BW_GET_DATA

T_BBW - Structure for use in the Buffer Busy Wait Monitor

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

T_BBW_TOT - Structure for use in the Buffer Busy Wait Monitor

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

EXCEPTIONS details

WRONG_DATABASE - non Oracle DB.

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

WRONG_ORACLE_RELEASE - wrong oracle release.

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

DB_RELEASE_UNKNOWN - unknown database release.

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

WRONG_INSTANCE - specified instance is not available.

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

Copy and paste ABAP code example for ORA_BW_GET_DATA 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.

ABAP code using 7.40 inline data declarations to call FM ORA_BW_GET_DATA

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