SAP IUUC_TABLE_DDIC_CREATE Function Module for Create DDIC Table
IUUC_TABLE_DDIC_CREATE is a standard iuuc table ddic create SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Create DDIC Table 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 table ddic create FM, simply by entering the name IUUC_TABLE_DDIC_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: IUUC_REPLICATION_ENCAPS
Program Name: SAPLIUUC_REPLICATION_ENCAPS
Main Program: SAPLIUUC_REPLICATION_ENCAPS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function IUUC_TABLE_DDIC_CREATE 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_TABLE_DDIC_CREATE'"Create DDIC Table.
EXPORTING
I_MT_ID = "DMC: Indicator for Mass Transfer
I_CL_DMC_LOG_HANDLER = "Log handler for MWB/DTL
I_TABLES = "tables to be processed by IUUC
I_RFCDEST = "Logical Destination (Specified in Function Call)
I_SHADOWTAB_NAME = "Name of an ABAP Dictionary object
I_TABNAME = "Table Name
I_ORIGTAB_NAME = "Name of an ABAP Dictionary object
I_SECIND_FIELD = "Field Name
I_ORA_HASH = "Number of Oracle Hash Partitions
IS_DD02V = "Generated Table for View DD02V
IS_DD09L = "DD: Technical settings of tables
IT_DD03P = "DMC: Table type for the field list of a structure
IMPORTING
E_TABLES = "tables to be processed by IUUC
E_ERRTEXT = "Text (80 Characters)
IMPORTING Parameters details for IUUC_TABLE_DDIC_CREATE
I_MT_ID - DMC: Indicator for Mass Transfer
Data type: DMC_MT_HEADER-IDOptional: No
Call by Reference: Yes
I_CL_DMC_LOG_HANDLER - Log handler for MWB/DTL
Data type: CL_DMC_LOG_HANDLEROptional: No
Call by Reference: Yes
I_TABLES - tables to be processed by IUUC
Data type: IUUC_TABLESOptional: No
Call by Reference: Yes
I_RFCDEST - Logical Destination (Specified in Function Call)
Data type: RFCDESTOptional: No
Call by Reference: Yes
I_SHADOWTAB_NAME - Name of an ABAP Dictionary object
Data type: DDOBJNAMEOptional: No
Call by Reference: Yes
I_TABNAME - Table Name
Data type: TABNAMEOptional: No
Call by Reference: Yes
I_ORIGTAB_NAME - Name of an ABAP Dictionary object
Data type: DDOBJNAMEOptional: No
Call by Reference: Yes
I_SECIND_FIELD - Field Name
Data type: FIELDNAMEOptional: No
Call by Reference: Yes
I_ORA_HASH - Number of Oracle Hash Partitions
Data type: IUUC_NUM_ORA_HASH_PARTITIONSOptional: No
Call by Reference: Yes
IS_DD02V - Generated Table for View DD02V
Data type: DD02VOptional: No
Call by Reference: Yes
IS_DD09L - DD: Technical settings of tables
Data type: DD09LOptional: No
Call by Reference: Yes
IT_DD03P - DMC: Table type for the field list of a structure
Data type: DMC_DD03P_TABOptional: No
Call by Reference: Yes
EXPORTING Parameters details for IUUC_TABLE_DDIC_CREATE
E_TABLES - tables to be processed by IUUC
Data type: IUUC_TABLESOptional: No
Call by Reference: Yes
E_ERRTEXT - Text (80 Characters)
Data type: TEXT80Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for IUUC_TABLE_DDIC_CREATE 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_i_mt_id | TYPE DMC_MT_HEADER-ID, " | |||
| lv_e_tables | TYPE IUUC_TABLES, " | |||
| lv_i_cl_dmc_log_handler | TYPE CL_DMC_LOG_HANDLER, " | |||
| lv_i_tables | TYPE IUUC_TABLES, " | |||
| lv_i_rfcdest | TYPE RFCDEST, " | |||
| lv_e_errtext | TYPE TEXT80, " | |||
| lv_i_shadowtab_name | TYPE DDOBJNAME, " | |||
| lv_i_tabname | TYPE TABNAME, " | |||
| lv_i_origtab_name | TYPE DDOBJNAME, " | |||
| lv_i_secind_field | TYPE FIELDNAME, " | |||
| lv_i_ora_hash | TYPE IUUC_NUM_ORA_HASH_PARTITIONS, " | |||
| lv_is_dd02v | TYPE DD02V, " | |||
| lv_is_dd09l | TYPE DD09L, " | |||
| lv_it_dd03p | TYPE DMC_DD03P_TAB. " |
|   CALL FUNCTION 'IUUC_TABLE_DDIC_CREATE' "Create DDIC Table |
| EXPORTING | ||
| I_MT_ID | = lv_i_mt_id | |
| I_CL_DMC_LOG_HANDLER | = lv_i_cl_dmc_log_handler | |
| I_TABLES | = lv_i_tables | |
| I_RFCDEST | = lv_i_rfcdest | |
| I_SHADOWTAB_NAME | = lv_i_shadowtab_name | |
| I_TABNAME | = lv_i_tabname | |
| I_ORIGTAB_NAME | = lv_i_origtab_name | |
| I_SECIND_FIELD | = lv_i_secind_field | |
| I_ORA_HASH | = lv_i_ora_hash | |
| IS_DD02V | = lv_is_dd02v | |
| IS_DD09L | = lv_is_dd09l | |
| IT_DD03P | = lv_it_dd03p | |
| IMPORTING | ||
| E_TABLES | = lv_e_tables | |
| E_ERRTEXT | = lv_e_errtext | |
| . " IUUC_TABLE_DDIC_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM IUUC_TABLE_DDIC_CREATE
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 ID FROM DMC_MT_HEADER INTO @DATA(ld_i_mt_id). | ||||
Search for further information about these or an SAP related objects