SAP FT_IDOC_FTULO_DETERMINE Function Module for NOTRANSL: Außenhandel: Kommunikation: Ermitteln der betroffenen FTULO-Date

Search SAP Function Modules

FT_IDOC_FTULO_DETERMINE is a standard ft idoc ftulo determine 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: Ermitteln der betroffenen FTULO-Date 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 idoc ftulo determine FM, simply by entering the name FT_IDOC_FTULO_DETERMINE into the relevant SAP transaction such as SE37 or SE38.

Function Group: VFUD
Program Name: SAPLVFUD
Main Program:
Appliation area: V
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FT_IDOC_FTULO_DETERMINE 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_IDOC_FTULO_DETERMINE'"NOTRANSL: Außenhandel: Kommunikation: Ermitteln der betroffenen FTULO-Date
  EXPORTING
*  I_T_RANGE_IDDPR =  "Data provider
*  I_T_RANGE_CREDAT =  "Date IDoc created
*  I_T_RANGE_CRETIM =  "Time IDoc created
*  I_T_RANGE_MESTYP =  "Logical Message Type
*  I_T_RANGE_DOCNUM =  "IDoc Number
*  I_T_RANGE_STATUS =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_T_RANGE_IDOCTP =  "Basic Type

 IMPORTING
   E_T_IDOC_NUMBERS =  "

EXCEPTIONS
   NO_DATA_DETERMINED = 1 

.

IMPORTING Parameters details for FT_IDOC_FTULO_DETERMINE

I_T_RANGE_IDDPR - Data provider

Data type: VFUL_RANGE_IDDPR
Optional: Yes
Call by Reference: Yes

I_T_RANGE_CREDAT - Date IDoc created

Data type: VFUL_RANGE_CREDAT
Optional: Yes
Call by Reference: Yes

I_T_RANGE_CRETIM - Time IDoc created

Data type: VFUL_RANGE_CRETIM
Optional: Yes
Call by Reference: Yes

I_T_RANGE_MESTYP - Logical Message Type

Data type: VFUL_RANGE_MESTYP
Optional: Yes
Call by Reference: Yes

I_T_RANGE_DOCNUM - IDoc Number

Data type: VFUL_RANGE_DOCNUM
Optional: Yes
Call by Reference: Yes

I_T_RANGE_STATUS - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: VFUL_RANGE_STATUS
Optional: Yes
Call by Reference: Yes

I_T_RANGE_IDOCTP - Basic Type

Data type: VFUL_RANGE_IDOCTP
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for FT_IDOC_FTULO_DETERMINE

E_T_IDOC_NUMBERS -

Data type: VFUL_T_IDOC_NUMBERS
Optional: No
Call by Reference: Yes

EXCEPTIONS details

NO_DATA_DETERMINED -

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

Copy and paste ABAP code example for FT_IDOC_FTULO_DETERMINE 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.

ABAP code using 7.40 inline data declarations to call FM FT_IDOC_FTULO_DETERMINE

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