SAP DTL_GET_CONVERSION_OBJECT_LIST Function Module for get list of conversion objects
DTL_GET_CONVERSION_OBJECT_LIST is a standard dtl get conversion object list SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for get list of conversion objects 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 get conversion object list FM, simply by entering the name DTL_GET_CONVERSION_OBJECT_LIST 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_GET_CONVERSION_OBJECT_LIST 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_GET_CONVERSION_OBJECT_LIST'"get list of conversion objects.
EXPORTING
I_MT_ID = "DMC: Indicator of a Mass Transfer
IMPORTING
ET_CONVOBJECTS = "MWB: Conv. Object Information for a Mass Transfer
TABLES
* IT_READING_TYPE = "Ranges Table for reading type
* IT_TABLES = "Ranges Table for Table Name
EXCEPTIONS
MASS_TRANSFER_NOT_FOUND = 1
IMPORTING Parameters details for DTL_GET_CONVERSION_OBJECT_LIST
I_MT_ID - DMC: Indicator of a Mass Transfer
Data type: DMC_MT_IDENTIFIEROptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for DTL_GET_CONVERSION_OBJECT_LIST
ET_CONVOBJECTS - MWB: Conv. Object Information for a Mass Transfer
Data type: DMC_MT_CONVOBJ_TABOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for DTL_GET_CONVERSION_OBJECT_LIST
IT_READING_TYPE - Ranges Table for reading type
Data type: DMC_RANGES_READING_TYPEOptional: Yes
Call by Reference: Yes
IT_TABLES - Ranges Table for Table Name
Data type: DMC_RANGES_TABNAMEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
MASS_TRANSFER_NOT_FOUND - mass transfer not found
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for DTL_GET_CONVERSION_OBJECT_LIST 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_et_convobjects | TYPE DMC_MT_CONVOBJ_TAB, " | |||
| lt_it_reading_type | TYPE STANDARD TABLE OF DMC_RANGES_READING_TYPE, " | |||
| lv_mass_transfer_not_found | TYPE DMC_RANGES_READING_TYPE, " | |||
| lt_it_tables | TYPE STANDARD TABLE OF DMC_RANGES_TABNAME. " |
|   CALL FUNCTION 'DTL_GET_CONVERSION_OBJECT_LIST' "get list of conversion objects |
| EXPORTING | ||
| I_MT_ID | = lv_i_mt_id | |
| IMPORTING | ||
| ET_CONVOBJECTS | = lv_et_convobjects | |
| TABLES | ||
| IT_READING_TYPE | = lt_it_reading_type | |
| IT_TABLES | = lt_it_tables | |
| EXCEPTIONS | ||
| MASS_TRANSFER_NOT_FOUND = 1 | ||
| . " DTL_GET_CONVERSION_OBJECT_LIST | ||
ABAP code using 7.40 inline data declarations to call FM DTL_GET_CONVERSION_OBJECT_LIST
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.Search for further information about these or an SAP related objects