SAP FT_UPLOAD_PROCESS_DD_INFO_GET Function Module for NOTRANSL: Außenhandel: Kommunikation: Ermittlung aller relevanten DDIC-Inf
FT_UPLOAD_PROCESS_DD_INFO_GET is a standard ft upload process dd info get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Außenhandel: Kommunikation: Ermittlung aller relevanten DDIC-Inf 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 ft upload process dd info get FM, simply by entering the name FT_UPLOAD_PROCESS_DD_INFO_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: VFUP
Program Name: SAPLVFUP
Main Program: SAPLVFUP
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FT_UPLOAD_PROCESS_DD_INFO_GET 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 'FT_UPLOAD_PROCESS_DD_INFO_GET'"NOTRANSL: Außenhandel: Kommunikation: Ermittlung aller relevanten DDIC-Inf.
EXPORTING
I_NAME_OBJECT = "
* I_OBJECT_TYPE = ' ' "
* I_OBJECT_TYPE_TEXT = ' ' "
* I_OBJECT_EDI_SEGMENT = ' ' "
IMPORTING
E_DDIC_INFO = "
EXCEPTIONS
OBJECT_KEY_TOO_LONG = 1 OBJECT_DATA_TOO_LONG = 2 OBJECT_NOT_FOUND = 3
IMPORTING Parameters details for FT_UPLOAD_PROCESS_DD_INFO_GET
I_NAME_OBJECT -
Data type: DD02D-TABNAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJECT_TYPE -
Data type: VFUL_R_OBJCT_ATOM-CONV_OBJCTDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJECT_TYPE_TEXT -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJECT_EDI_SEGMENT -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for FT_UPLOAD_PROCESS_DD_INFO_GET
E_DDIC_INFO -
Data type: VFUL_R_DDIC_INFOOptional: No
Call by Reference: Yes
EXCEPTIONS details
OBJECT_KEY_TOO_LONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_DATA_TOO_LONG -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for FT_UPLOAD_PROCESS_DD_INFO_GET 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_e_ddic_info | TYPE VFUL_R_DDIC_INFO, " | |||
| lv_i_name_object | TYPE DD02D-TABNAME, " | |||
| lv_object_key_too_long | TYPE DD02D, " | |||
| lv_i_object_type | TYPE VFUL_R_OBJCT_ATOM-CONV_OBJCT, " SPACE | |||
| lv_object_data_too_long | TYPE VFUL_R_OBJCT_ATOM, " | |||
| lv_object_not_found | TYPE VFUL_R_OBJCT_ATOM, " | |||
| lv_i_object_type_text | TYPE C, " SPACE | |||
| lv_i_object_edi_segment | TYPE C. " SPACE |
|   CALL FUNCTION 'FT_UPLOAD_PROCESS_DD_INFO_GET' "NOTRANSL: Außenhandel: Kommunikation: Ermittlung aller relevanten DDIC-Inf |
| EXPORTING | ||
| I_NAME_OBJECT | = lv_i_name_object | |
| I_OBJECT_TYPE | = lv_i_object_type | |
| I_OBJECT_TYPE_TEXT | = lv_i_object_type_text | |
| I_OBJECT_EDI_SEGMENT | = lv_i_object_edi_segment | |
| IMPORTING | ||
| E_DDIC_INFO | = lv_e_ddic_info | |
| EXCEPTIONS | ||
| OBJECT_KEY_TOO_LONG = 1 | ||
| OBJECT_DATA_TOO_LONG = 2 | ||
| OBJECT_NOT_FOUND = 3 | ||
| . " FT_UPLOAD_PROCESS_DD_INFO_GET | ||
ABAP code using 7.40 inline data declarations to call FM FT_UPLOAD_PROCESS_DD_INFO_GET
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 TABNAME FROM DD02D INTO @DATA(ld_i_name_object). | ||||
| "SELECT single CONV_OBJCT FROM VFUL_R_OBJCT_ATOM INTO @DATA(ld_i_object_type). | ||||
| DATA(ld_i_object_type) | = ' '. | |||
| DATA(ld_i_object_type_text) | = ' '. | |||
| DATA(ld_i_object_edi_segment) | = ' '. | |||
Search for further information about these or an SAP related objects