SAP GET_DB_RELEASE_ORA Function Module for Get Oracle Version









GET_DB_RELEASE_ORA is a standard get db release ora 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 Oracle Version 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 release ora FM, simply by entering the name GET_DB_RELEASE_ORA into the relevant SAP transaction such as SE37 or SE38.

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



Function GET_DB_RELEASE_ORA 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_RELEASE_ORA'"Get Oracle Version
IMPORTING
ORA_RELEASE = "

EXCEPTIONS
DB_RELEASE_UNKNOWN = 1
.



EXPORTING Parameters details for GET_DB_RELEASE_ORA

ORA_RELEASE -

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

EXCEPTIONS details

DB_RELEASE_UNKNOWN -

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

Copy and paste ABAP code example for GET_DB_RELEASE_ORA 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_ora_release  TYPE DBRELEASE-DBRELEASE, "   
lv_db_release_unknown  TYPE DBRELEASE. "   

  CALL FUNCTION 'GET_DB_RELEASE_ORA'  "Get Oracle Version
    IMPORTING
         ORA_RELEASE = lv_ora_release
    EXCEPTIONS
        DB_RELEASE_UNKNOWN = 1
. " GET_DB_RELEASE_ORA




ABAP code using 7.40 inline data declarations to call FM GET_DB_RELEASE_ORA

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.

"SELECT single DBRELEASE FROM DBRELEASE INTO @DATA(ld_ora_release).
 
 


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!