SAP DTL_DEFINE_CONV_OBJ_FROM_TABLE Function Module for create a conversion object for a certain DB table
DTL_DEFINE_CONV_OBJ_FROM_TABLE is a standard dtl define conv obj from table 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 a conversion object for a certain DB 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 dtl define conv obj from table FM, simply by entering the name DTL_DEFINE_CONV_OBJ_FROM_TABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: DMC_DTL
Program Name: SAPLDMC_DTL
Main Program: SAPLDMC_DTL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function DTL_DEFINE_CONV_OBJ_FROM_TABLE 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 'DTL_DEFINE_CONV_OBJ_FROM_TABLE'"create a conversion object for a certain DB table.
EXPORTING
I_MT_ID = "DMC: Indicator for Mass Transfer
I_TABNAME = "Name of an ABAP Dictionary object
* I_GENERATE_RTO = 'X' "also generate runtime objects?
* I_BOPRULE = "Rule ID
* I_EOPRULE = "Rule ID
* I_BOTRULE = "Rule ID
* I_EOTRULE = "Rule ID
* IT_RSREL = "table type for structure relationships
* IT_RCALLS = "DTL: rule calls
IMPORTING
E_SUCCESS = "Conversion object creation successful?
ET_MESSAGES = "Application Log: Table with Messages
IMPORTING Parameters details for DTL_DEFINE_CONV_OBJ_FROM_TABLE
I_MT_ID - DMC: Indicator for Mass Transfer
Data type: DMC_MT_IDENTIFIEROptional: No
Call by Reference: No ( called with pass by value option)
I_TABNAME - Name of an ABAP Dictionary object
Data type: DDNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_GENERATE_RTO - also generate runtime objects?
Data type: BOOLEANDefault: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_BOPRULE - Rule ID
Data type: DMC_RIDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EOPRULE - Rule ID
Data type: DMC_RIDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_BOTRULE - Rule ID
Data type: DMC_RIDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
I_EOTRULE - Rule ID
Data type: DMC_RIDENTOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_RSREL - table type for structure relationships
Data type: DMC_RSREL_STRUC_TABOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_RCALLS - DTL: rule calls
Data type: DMCDTLRCALLS_TOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DTL_DEFINE_CONV_OBJ_FROM_TABLE
E_SUCCESS - Conversion object creation successful?
Data type: BOOLEANOptional: No
Call by Reference: No ( called with pass by value option)
ET_MESSAGES - Application Log: Table with Messages
Data type: DMC_BAL_T_MSGOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for DTL_DEFINE_CONV_OBJ_FROM_TABLE 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_IDENTIFIER, " | |||
| lv_e_success | TYPE BOOLEAN, " | |||
| lv_i_tabname | TYPE DDNAME, " | |||
| lv_et_messages | TYPE DMC_BAL_T_MSG, " | |||
| lv_i_generate_rto | TYPE BOOLEAN, " 'X' | |||
| lv_i_boprule | TYPE DMC_RIDENT, " | |||
| lv_i_eoprule | TYPE DMC_RIDENT, " | |||
| lv_i_botrule | TYPE DMC_RIDENT, " | |||
| lv_i_eotrule | TYPE DMC_RIDENT, " | |||
| lv_it_rsrel | TYPE DMC_RSREL_STRUC_TAB, " | |||
| lv_it_rcalls | TYPE DMCDTLRCALLS_T. " |
|   CALL FUNCTION 'DTL_DEFINE_CONV_OBJ_FROM_TABLE' "create a conversion object for a certain DB table |
| EXPORTING | ||
| I_MT_ID | = lv_i_mt_id | |
| I_TABNAME | = lv_i_tabname | |
| I_GENERATE_RTO | = lv_i_generate_rto | |
| I_BOPRULE | = lv_i_boprule | |
| I_EOPRULE | = lv_i_eoprule | |
| I_BOTRULE | = lv_i_botrule | |
| I_EOTRULE | = lv_i_eotrule | |
| IT_RSREL | = lv_it_rsrel | |
| IT_RCALLS | = lv_it_rcalls | |
| IMPORTING | ||
| E_SUCCESS | = lv_e_success | |
| ET_MESSAGES | = lv_et_messages | |
| . " DTL_DEFINE_CONV_OBJ_FROM_TABLE | ||
ABAP code using 7.40 inline data declarations to call FM DTL_DEFINE_CONV_OBJ_FROM_TABLE
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.| DATA(ld_i_generate_rto) | = 'X'. | |||
Search for further information about these or an SAP related objects