SAP C_GET_DB_ORA_MSYS_DATES Function Module for Database Metrics: Dates for SysMetrics

Search SAP Function Modules

C_GET_DB_ORA_MSYS_DATES is a standard c get db ora msys dates SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Database Metrics: Dates for SysMetrics 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 msys dates FM, simply by entering the name C_GET_DB_ORA_MSYS_DATES 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_1
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function C_GET_DB_ORA_MSYS_DATES 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_MSYS_DATES'"Database Metrics: Dates for SysMetrics
  EXPORTING
   I_REMOTE_SYSTEM =  "Logical name for a database connection

 IMPORTING
   E_GV_MIN_BEGIN_TIME =  "Oracle mon: Time at the beginning of the snapshot interval
   E_GV_MAX_END_TIME =  "Oracle mon.: Time at the end of the snapshot interval
   E_DBA_MIN_BEGIN_TIME =  "Oracle mon: Time at the beginning of the snapshot interval
   E_DBA_MAX_END_TIME =  "Oracle mon.: Time at the end of the snapshot interval

.

IMPORTING Parameters details for C_GET_DB_ORA_MSYS_DATES

I_REMOTE_SYSTEM - Logical name for a database connection

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

EXPORTING Parameters details for C_GET_DB_ORA_MSYS_DATES

E_GV_MIN_BEGIN_TIME - Oracle mon: Time at the beginning of the snapshot interval

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

E_GV_MAX_END_TIME - Oracle mon.: Time at the end of the snapshot interval

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

E_DBA_MIN_BEGIN_TIME - Oracle mon: Time at the beginning of the snapshot interval

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

E_DBA_MAX_END_TIME - Oracle mon.: Time at the end of the snapshot interval

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

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

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