SAP EDI_STATUS_ADD_BLOCK Function Module for EDI interface: Insert block of status records

Search SAP Function Modules

EDI_STATUS_ADD_BLOCK is a standard edi status add block 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: Insert block of status records 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 status add block FM, simply by entering the name EDI_STATUS_ADD_BLOCK 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_STATUS_ADD_BLOCK 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_STATUS_ADD_BLOCK'"EDI interface: Insert block of status records
  EXPORTING
   DOCUMENT_NUMBER =  "IDoc number

 IMPORTING
   IDOC_CONTROL =  "Control Record

TABLES
   IDOC_STATUS_RECORDS =  "Block of status records

EXCEPTIONS
   DOCUMENT_NUMBER_INVALID = 1    IDOC_STATUS_RECORDS_EMPTY = 2    OTHER_FIELDS_INVALID = 3    STATUS_INVALID = 4 

.

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_STATUS_ADD_BLOCK

DOCUMENT_NUMBER - IDoc number

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

EXPORTING Parameters details for EDI_STATUS_ADD_BLOCK

IDOC_CONTROL - Control Record

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

TABLES Parameters details for EDI_STATUS_ADD_BLOCK

IDOC_STATUS_RECORDS - Block of status records

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

EXCEPTIONS details

DOCUMENT_NUMBER_INVALID - IDoc number is invalid

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

IDOC_STATUS_RECORDS_EMPTY - Table IDOC_STATUS_RECORDS is empty

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

OTHER_FIELDS_INVALID - One field in status record is invalid

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

STATUS_INVALID - Status value is invalid

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

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

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