SAP IUUC_WRITE_AND_CALL_DBPROG Function Module for Writes a program generated in Fgrp SDB2 and executes it









IUUC_WRITE_AND_CALL_DBPROG is a standard iuuc write and call dbprog SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Writes a program generated in Fgrp SDB2 and executes it 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 iuuc write and call dbprog FM, simply by entering the name IUUC_WRITE_AND_CALL_DBPROG into the relevant SAP transaction such as SE37 or SE38.

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



Function IUUC_WRITE_AND_CALL_DBPROG 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 'IUUC_WRITE_AND_CALL_DBPROG'"Writes a program generated in Fgrp SDB2 and executes it
EXPORTING
* NO_EXEC = ' ' "Only write, do not execute
* PRID = 0 "
* PROGNAME = ' ' "Required name of the program
* MAX_SEVERITY = 'E' "
* ABAP_FLAG = ' ' "Execute generated code from ABAP (EXEC-SQL)
* DBCON_NAME = ' ' "Logischer Name einer Datenbankverbindung

IMPORTING
GENPROG = "Actual name of program
RC = "Return code of called form

TABLES
STATEMENTS = "Table with statements

EXCEPTIONS
PROGRAM_NOT_WRITTEN = 1 SQL_ERROR_OCCURED = 2 OP_FAILURE = 3
.



IMPORTING Parameters details for IUUC_WRITE_AND_CALL_DBPROG

NO_EXEC - Only write, do not execute

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

PRID -

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

PROGNAME - Required name of the program

Data type: TRDIR-NAME
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

MAX_SEVERITY -

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

ABAP_FLAG - Execute generated code from ABAP (EXEC-SQL)

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

DBCON_NAME - Logischer Name einer Datenbankverbindung

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

EXPORTING Parameters details for IUUC_WRITE_AND_CALL_DBPROG

GENPROG - Actual name of program

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

RC - Return code of called form

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

TABLES Parameters details for IUUC_WRITE_AND_CALL_DBPROG

STATEMENTS - Table with statements

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

EXCEPTIONS details

PROGRAM_NOT_WRITTEN - Program could not be written

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

SQL_ERROR_OCCURED -

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

OP_FAILURE -

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

Copy and paste ABAP code example for IUUC_WRITE_AND_CALL_DBPROG 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_genprog  TYPE TRDIR-NAME, "   
lv_no_exec  TYPE TRDIR, "   SPACE
lt_statements  TYPE STANDARD TABLE OF TRDIR, "   
lv_program_not_written  TYPE TRDIR, "   
lv_rc  TYPE SY-SUBRC, "   
lv_prid  TYPE SY-TABIX, "   0
lv_sql_error_occured  TYPE SY, "   
lv_progname  TYPE TRDIR-NAME, "   SPACE
lv_op_failure  TYPE TRDIR, "   
lv_max_severity  TYPE TRDIR, "   'E'
lv_abap_flag  TYPE TRDIR, "   SPACE
lv_dbcon_name  TYPE DBCON_NAME. "   SPACE

  CALL FUNCTION 'IUUC_WRITE_AND_CALL_DBPROG'  "Writes a program generated in Fgrp SDB2 and executes it
    EXPORTING
         NO_EXEC = lv_no_exec
         PRID = lv_prid
         PROGNAME = lv_progname
         MAX_SEVERITY = lv_max_severity
         ABAP_FLAG = lv_abap_flag
         DBCON_NAME = lv_dbcon_name
    IMPORTING
         GENPROG = lv_genprog
         RC = lv_rc
    TABLES
         STATEMENTS = lt_statements
    EXCEPTIONS
        PROGRAM_NOT_WRITTEN = 1
        SQL_ERROR_OCCURED = 2
        OP_FAILURE = 3
. " IUUC_WRITE_AND_CALL_DBPROG




ABAP code using 7.40 inline data declarations to call FM IUUC_WRITE_AND_CALL_DBPROG

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 NAME FROM TRDIR INTO @DATA(ld_genprog).
 
DATA(ld_no_exec) = ' '.
 
 
 
"SELECT single SUBRC FROM SY INTO @DATA(ld_rc).
 
"SELECT single TABIX FROM SY INTO @DATA(ld_prid).
 
 
"SELECT single NAME FROM TRDIR INTO @DATA(ld_progname).
DATA(ld_progname) = ' '.
 
 
DATA(ld_max_severity) = 'E'.
 
DATA(ld_abap_flag) = ' '.
 
DATA(ld_dbcon_name) = ' '.
 


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!