SAP GET_DB_ORA_RELEASE Function Module for Read oracle release









GET_DB_ORA_RELEASE is a standard get db ora release SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read oracle release 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 get db ora release FM, simply by entering the name GET_DB_ORA_RELEASE into the relevant SAP transaction such as SE37 or SE38.

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



Function GET_DB_ORA_RELEASE 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 'GET_DB_ORA_RELEASE'"Read oracle release
EXPORTING
* CON_NAME = 'DEFAULT' "Oracle monitoring: connection name

IMPORTING
ORACLE_RELEASE = "Oracle release

EXCEPTIONS
DB_RELEASE_UNKNOWN = 1 DB_CONNECTION_ERROR = 2
.



IMPORTING Parameters details for GET_DB_ORA_RELEASE

CON_NAME - Oracle monitoring: connection name

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

EXPORTING Parameters details for GET_DB_ORA_RELEASE

ORACLE_RELEASE - Oracle release

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

EXCEPTIONS details

DB_RELEASE_UNKNOWN - Database release unknown

Data type:
Optional: No
Call by Reference: Yes

DB_CONNECTION_ERROR - Database connection error

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for GET_DB_ORA_RELEASE 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_con_name  TYPE DBCON_NAME, "   'DEFAULT'
lv_oracle_release  TYPE ORACLE_RELEASE, "   
lv_db_release_unknown  TYPE ORACLE_RELEASE, "   
lv_db_connection_error  TYPE ORACLE_RELEASE. "   

  CALL FUNCTION 'GET_DB_ORA_RELEASE'  "Read oracle release
    EXPORTING
         CON_NAME = lv_con_name
    IMPORTING
         ORACLE_RELEASE = lv_oracle_release
    EXCEPTIONS
        DB_RELEASE_UNKNOWN = 1
        DB_CONNECTION_ERROR = 2
. " GET_DB_ORA_RELEASE




ABAP code using 7.40 inline data declarations to call FM GET_DB_ORA_RELEASE

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.

DATA(ld_con_name) = 'DEFAULT'.
 
 
 
 


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!