SAP DB_ORA_DBSERVER_OS Function Module for









DB_ORA_DBSERVER_OS is a standard db ora dbserver os SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 db ora dbserver os FM, simply by entering the name DB_ORA_DBSERVER_OS into the relevant SAP transaction such as SE37 or SE38.

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



Function DB_ORA_DBSERVER_OS 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 'DB_ORA_DBSERVER_OS'"
EXPORTING
* CON_REF = "Database Connection

IMPORTING
DBSERVER_OS = "

EXCEPTIONS
OPSYS_NOT_FOUND = 1 SQL_ERROR = 2
.



IMPORTING Parameters details for DB_ORA_DBSERVER_OS

CON_REF - Database Connection

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

EXPORTING Parameters details for DB_ORA_DBSERVER_OS

DBSERVER_OS -

Data type: SY-OPSYS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

OPSYS_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

SQL_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for DB_ORA_DBSERVER_OS 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_ref  TYPE CL_SQL_CONNECTION, "   
lv_dbserver_os  TYPE SY-OPSYS, "   
lv_opsys_not_found  TYPE SY, "   
lv_sql_error  TYPE SY. "   

  CALL FUNCTION 'DB_ORA_DBSERVER_OS'  "
    EXPORTING
         CON_REF = lv_con_ref
    IMPORTING
         DBSERVER_OS = lv_dbserver_os
    EXCEPTIONS
        OPSYS_NOT_FOUND = 1
        SQL_ERROR = 2
. " DB_ORA_DBSERVER_OS




ABAP code using 7.40 inline data declarations to call FM DB_ORA_DBSERVER_OS

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 OPSYS FROM SY INTO @DATA(ld_dbserver_os).
 
 
 


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!