SAP C_GET_DB_ORA_SPF Function Module for Data collection function for the monitor Database Parameters.
C_GET_DB_ORA_SPF is a standard c get db ora spf SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Data collection function for the monitor Database Parameters. 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 spf FM, simply by entering the name C_GET_DB_ORA_SPF 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_SPF 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_SPF'"Data collection function for the monitor Database Parameters..
EXPORTING
I_INST_ID = "Oracle monitor: Instance ID
I_REMOTE_SYSTEM = "Logical name for a database connection
TABLES
* DBPARAMETER = "Oracle monitoring: structure for GV$PARAMETER.
* INIT_PARAMS = "History of a DB, OS or SAP profile
* PARAMS_DIFF = "ORACLE Database Parameters structure.
* SPPARAMS = "ORACLE Database Parameters structure.
IMPORTING Parameters details for C_GET_DB_ORA_SPF
I_INST_ID - Oracle monitor: Instance ID
Data type: ORA_INST_IDOptional: No
Call by Reference: No ( called with pass by value option)
I_REMOTE_SYSTEM - Logical name for a database connection
Data type: DBCON_NAMEOptional: No
Call by Reference: Yes
TABLES Parameters details for C_GET_DB_ORA_SPF
DBPARAMETER - Oracle monitoring: structure for GV$PARAMETER.
Data type: COMPARAMOptional: Yes
Call by Reference: Yes
INIT_PARAMS - History of a DB, OS or SAP profile
Data type: PROF_HISTOptional: Yes
Call by Reference: Yes
PARAMS_DIFF - ORACLE Database Parameters structure.
Data type: COMPARAMOptional: Yes
Call by Reference: Yes
SPPARAMS - ORACLE Database Parameters structure.
Data type: COMPARAMOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for C_GET_DB_ORA_SPF 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_i_inst_id | TYPE ORA_INST_ID, " | |||
| lt_dbparameter | TYPE STANDARD TABLE OF COMPARAM, " | |||
| lt_init_params | TYPE STANDARD TABLE OF PROF_HIST, " | |||
| lv_i_remote_system | TYPE DBCON_NAME, " | |||
| lt_params_diff | TYPE STANDARD TABLE OF COMPARAM, " | |||
| lt_spparams | TYPE STANDARD TABLE OF COMPARAM. " |
|   CALL FUNCTION 'C_GET_DB_ORA_SPF' "Data collection function for the monitor Database Parameters. |
| EXPORTING | ||
| I_INST_ID | = lv_i_inst_id | |
| I_REMOTE_SYSTEM | = lv_i_remote_system | |
| TABLES | ||
| DBPARAMETER | = lt_dbparameter | |
| INIT_PARAMS | = lt_init_params | |
| PARAMS_DIFF | = lt_params_diff | |
| SPPARAMS | = lt_spparams | |
| . " C_GET_DB_ORA_SPF | ||
ABAP code using 7.40 inline data declarations to call FM C_GET_DB_ORA_SPF
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