SAP Function Modules

DB_DROP_VIEW SAP Function module







DB_DROP_VIEW is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name DB_DROP_VIEW into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SDB2
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM DB_DROP_VIEW - DB DROP VIEW





CALL FUNCTION 'DB_DROP_VIEW' "
  EXPORTING
*   dbsys = SY-DBSYS            " sy-dbsys      DBS for which program is generated
*   no_exec = SPACE             "               X: Do not execute generated program
*   prid = 0                    " sy-tabix
*   progname = SPACE            " trdir-name    Name of generated program
    viewname =                  " dd25v-viewname  View name
*   db_check_flag = SPACE       "
*   ignore_sql_error = SPACE    "
  IMPORTING
    genprog =                   " trdir-name    Real name of the generated program
    subrc =                     " sy-subrc      0: deleted; 4: view does not exist
  EXCEPTIONS
    PROGRAM_NOT_GENERATED = 1   "               Program could not be generated
    PROGRAM_NOT_WRITTEN = 2     "               Program could not be written
    VIEW_NOT_DROPPED = 3        "               Error when deleting the view
    .  "  DB_DROP_VIEW

ABAP code example for Function Module DB_DROP_VIEW





The ABAP code below is a full code listing to execute function module DB_DROP_VIEW including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_genprog  TYPE TRDIR-NAME ,
ld_subrc  TYPE SY-SUBRC .

DATA(ld_dbsys) = 'some text here'.
DATA(ld_no_exec) = 'some text here'.
DATA(ld_prid) = '123 '.

SELECT single NAME
FROM TRDIR
INTO @DATA(ld_progname).


SELECT single VIEWNAME
FROM DD25V
INTO @DATA(ld_viewname).

DATA(ld_db_check_flag) = 'some text here'.
DATA(ld_ignore_sql_error) = 'some text here'. . CALL FUNCTION 'DB_DROP_VIEW' EXPORTING * dbsys = ld_dbsys * no_exec = ld_no_exec * prid = ld_prid * progname = ld_progname viewname = ld_viewname * db_check_flag = ld_db_check_flag * ignore_sql_error = ld_ignore_sql_error IMPORTING genprog = ld_genprog subrc = ld_subrc EXCEPTIONS PROGRAM_NOT_GENERATED = 1 PROGRAM_NOT_WRITTEN = 2 VIEW_NOT_DROPPED = 3 . " DB_DROP_VIEW
IF SY-SUBRC EQ 0. "All OK ELSEIF SY-SUBRC EQ 1. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 2. "Exception "Add code for exception here ELSEIF SY-SUBRC EQ 3. "Exception "Add code for exception here ENDIF.







ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:
ld_genprog  TYPE TRDIR-NAME ,
ld_dbsys  TYPE SY-DBSYS ,
ld_subrc  TYPE SY-SUBRC ,
ld_no_exec  TYPE STRING ,
ld_prid  TYPE SY-TABIX ,
ld_progname  TYPE TRDIR-NAME ,
ld_viewname  TYPE DD25V-VIEWNAME ,
ld_db_check_flag  TYPE STRING ,
ld_ignore_sql_error  TYPE STRING .

ld_dbsys = 'some text here'.
ld_no_exec = 'some text here'.
ld_prid = '123 '.

SELECT single NAME
FROM TRDIR
INTO ld_progname.


SELECT single VIEWNAME
FROM DD25V
INTO ld_viewname.

ld_db_check_flag = 'some text here'.
ld_ignore_sql_error = 'some text here'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name DB_DROP_VIEW or its description.