SAP EDI_SEGMENT_ADD_NEXT Function Module for EDI interface: Sequential insertion of data record

Search SAP Function Modules

EDI_SEGMENT_ADD_NEXT is a standard edi segment add next SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for EDI interface: Sequential insertion of data record 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 edi segment add next FM, simply by entering the name EDI_SEGMENT_ADD_NEXT into the relevant SAP transaction such as SE37 or SE38.

Function Group: EDI1
Program Name: SAPLEDI1
Main Program: SAPLEDI1
Appliation area: S
Release date: 11-Dec-1995
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function EDI_SEGMENT_ADD_NEXT 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_SEGMENT_ADD_NEXT'"EDI interface: Sequential insertion of data record
  EXPORTING
   IDENTIFIER =  "IDoc identifier
   IDOC_CONTAINER =  "Data record to be added

 IMPORTING
   IDOC_CONTAINER_OUT =  "Data record which was added

EXCEPTIONS
   IDENTIFIER_INVALID = 1    PARAMETER_ERROR = 2    SEGMENT_NUMBER_NOT_SEQUENTIAL = 3 

.

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_SAPLEDI1_001 Customer Function for Open_for_create

IMPORTING Parameters details for EDI_SEGMENT_ADD_NEXT

IDENTIFIER - IDoc identifier

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

IDOC_CONTAINER - Data record to be added

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

EXPORTING Parameters details for EDI_SEGMENT_ADD_NEXT

IDOC_CONTAINER_OUT - Data record which was added

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

EXCEPTIONS details

IDENTIFIER_INVALID - IDoc ID is invalid

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

PARAMETER_ERROR - Administration section of data record is incomplete

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

SEGMENT_NUMBER_NOT_SEQUENTIAL - Data record number is not sequential

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

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

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