SAP FTR_IDOC_READ Function Module for Read an IDoc via EDI Interface (OPEN, READ, CLOSE)









FTR_IDOC_READ is a standard ftr idoc read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read an IDoc via EDI Interface (OPEN, READ, CLOSE) 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 ftr idoc read FM, simply by entering the name FTR_IDOC_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: FTR_CORR_IDOC
Program Name: SAPLFTR_CORR_IDOC
Main Program: SAPLFTR_CORR_IDOC
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FTR_IDOC_READ 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 'FTR_IDOC_READ'"Read an IDoc via EDI Interface (OPEN, READ, CLOSE)
EXPORTING
PI_DOCNUM = "

IMPORTING
PE_IDOC_CNTRL = "Control Record (IDoc)
PE_IDOC_STATUS = "Letzter Statussatz (IDoc)
PE_IDOC_DATA = "Table Type for EDIDD (IDoc Data Records)

EXCEPTIONS
OPEN_ERROR = 1 READ_ERROR = 2 CLOSE_ERROR = 3
.



IMPORTING Parameters details for FTR_IDOC_READ

PI_DOCNUM -

Data type: VTBKORES-DOCNUM
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for FTR_IDOC_READ

PE_IDOC_CNTRL - Control Record (IDoc)

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

PE_IDOC_STATUS - Letzter Statussatz (IDoc)

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

PE_IDOC_DATA - Table Type for EDIDD (IDoc Data Records)

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

EXCEPTIONS details

OPEN_ERROR -

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

READ_ERROR -

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

CLOSE_ERROR -

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

Copy and paste ABAP code example for FTR_IDOC_READ 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_pi_docnum  TYPE VTBKORES-DOCNUM, "   
lv_open_error  TYPE VTBKORES, "   
lv_pe_idoc_cntrl  TYPE EDIDC, "   
lv_read_error  TYPE EDIDC, "   
lv_pe_idoc_status  TYPE EDIDS, "   
lv_close_error  TYPE EDIDS, "   
lv_pe_idoc_data  TYPE EDIDD_TT. "   

  CALL FUNCTION 'FTR_IDOC_READ'  "Read an IDoc via EDI Interface (OPEN, READ, CLOSE)
    EXPORTING
         PI_DOCNUM = lv_pi_docnum
    IMPORTING
         PE_IDOC_CNTRL = lv_pe_idoc_cntrl
         PE_IDOC_STATUS = lv_pe_idoc_status
         PE_IDOC_DATA = lv_pe_idoc_data
    EXCEPTIONS
        OPEN_ERROR = 1
        READ_ERROR = 2
        CLOSE_ERROR = 3
. " FTR_IDOC_READ




ABAP code using 7.40 inline data declarations to call FM FTR_IDOC_READ

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 DOCNUM FROM VTBKORES INTO @DATA(ld_pi_docnum).
 
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!