SAP C_GET_DB_ORA_TABLE_ACCESS Function Module for Get data for the table access monitor









C_GET_DB_ORA_TABLE_ACCESS is a standard c get db ora table access 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 data for the table access 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 get db ora table access FM, simply by entering the name C_GET_DB_ORA_TABLE_ACCESS into the relevant SAP transaction such as SE37 or SE38.

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



Function C_GET_DB_ORA_TABLE_ACCESS 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_GET_DB_ORA_TABLE_ACCESS'"Get data for the table access monitor
  EXPORTING
   REM_SYS =  "Logical name for a database connection
*  I_INST_ID =  "Oracle monitor: Instance ID

 IMPORTING
   IS_RAC =  "Is RAC, Y/N?

TABLES
   T_STATEMENTS =  "Oracle Table Access Monitor Structure
   T_OPERATIONS =  "Oracle Table Access Monitor Structure
   T_TABLES =  "Oracle Table Access Monitor Structure

EXCEPTIONS
   WRONG_DATABASE = 1    WRONG_ORACLE_RELEASE = 2    DB_RELEASE_UNKNOWN = 3
.



IMPORTING Parameters details for C_GET_DB_ORA_TABLE_ACCESS

REM_SYS - Logical name for a database connection

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

I_INST_ID - Oracle monitor: Instance ID

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

EXPORTING Parameters details for C_GET_DB_ORA_TABLE_ACCESS

IS_RAC - Is RAC, Y/N?

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

TABLES Parameters details for C_GET_DB_ORA_TABLE_ACCESS

T_STATEMENTS - Oracle Table Access Monitor Structure

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

T_OPERATIONS - Oracle Table Access Monitor Structure

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

T_TABLES - Oracle Table Access Monitor Structure

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

EXCEPTIONS details

WRONG_DATABASE - Non-Oracle Database

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

WRONG_ORACLE_RELEASE - Oracle Release < 9

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

DB_RELEASE_UNKNOWN - Oracle release unknown

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

Copy and paste ABAP code example for C_GET_DB_ORA_TABLE_ACCESS 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_is_rac  TYPE CHAR1, "   
lv_rem_sys  TYPE DBCON_NAME, "   
lt_t_statements  TYPE STANDARD TABLE OF ORA_TABLE_ACCESS, "   
lv_wrong_database  TYPE ORA_TABLE_ACCESS, "   
lv_i_inst_id  TYPE ORA_INST_ID, "   
lt_t_operations  TYPE STANDARD TABLE OF ORA_TABLE_ACCESS, "   
lv_wrong_oracle_release  TYPE ORA_TABLE_ACCESS, "   
lt_t_tables  TYPE STANDARD TABLE OF ORA_TABLE_ACCESS, "   
lv_db_release_unknown  TYPE ORA_TABLE_ACCESS. "   

  CALL FUNCTION 'C_GET_DB_ORA_TABLE_ACCESS'  "Get data for the table access monitor
    EXPORTING
         REM_SYS = lv_rem_sys
         I_INST_ID = lv_i_inst_id
    IMPORTING
         IS_RAC = lv_is_rac
    TABLES
         T_STATEMENTS = lt_t_statements
         T_OPERATIONS = lt_t_operations
         T_TABLES = lt_t_tables
    EXCEPTIONS
        WRONG_DATABASE = 1
        WRONG_ORACLE_RELEASE = 2
        DB_RELEASE_UNKNOWN = 3
. " C_GET_DB_ORA_TABLE_ACCESS




ABAP code using 7.40 inline data declarations to call FM C_GET_DB_ORA_TABLE_ACCESS

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!