SAP EDI_IDOC_PARSER Function Module for

Search SAP Function Modules

EDI_IDOC_PARSER is a standard edi idoc parser SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 edi idoc parser FM, simply by entering the name EDI_IDOC_PARSER into the relevant SAP transaction such as SE37 or SE38.

Function Group: EDIT
Program Name: SAPLEDIT
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function EDI_IDOC_PARSER 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 'EDI_IDOC_PARSER'"
  EXPORTING
   OBJECT =  "
   OBJECT_TYPE =  "
*  OBJECT_RELEASE = SY-SAPRL "
*  OBJECT_APPLREL =  "Application Release of IDoc Segments in Documentation Tools
*  VERSION = '3' "
*  WITH_CONTROL_RECORD = 'X' "
*  WITH_DATA_RECORD = 'X' "
*  WITH_STATUS_RECORD = 'X' "

 IMPORTING
   PARSER_DOCU =  "

EXCEPTIONS
   DEFINITION_READ_ERROR = 1 

.

Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLEDITOR_001 User Exit for $$ Editor (Dynamic Pattern)
EXIT_SAPLEDITOR_002 User's Own Function Codes for $$ Editor: Special Case for ABAP Editor

IMPORTING Parameters details for EDI_IDOC_PARSER

OBJECT -

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

OBJECT_TYPE -

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

OBJECT_RELEASE -

Data type: SY-SAPRL
Default: SY-SAPRL
Optional: Yes
Call by Reference: No ( called with pass by value option)

OBJECT_APPLREL - Application Release of IDoc Segments in Documentation Tools

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

VERSION -

Data type: EDI_VERREC-VERSION
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITH_CONTROL_RECORD -

Data type: LEDID_FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITH_DATA_RECORD -

Data type: LEDID_FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

WITH_STATUS_RECORD -

Data type: LEDID_FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for EDI_IDOC_PARSER

PARSER_DOCU -

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

EXCEPTIONS details

DEFINITION_READ_ERROR -

Data type:
Optional: No
Call by Reference: Yes

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

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