SAP EDI_DOCUMENT_CLOSE_PROCESS Function Module for EDI interface: Close IDoc after processing

Search SAP Function Modules

EDI_DOCUMENT_CLOSE_PROCESS is a standard edi document close process 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: Close IDoc after processing 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 document close process FM, simply by entering the name EDI_DOCUMENT_CLOSE_PROCESS into the relevant SAP transaction such as SE37 or SE38.

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

Function EDI_DOCUMENT_CLOSE_PROCESS 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_DOCUMENT_CLOSE_PROCESS'"EDI interface: Close IDoc after processing
  EXPORTING
   DOCUMENT_NUMBER =  "IDoc number
*  BACKGROUND = NO_BACKGROUND "Database accesses in update task
*  NO_DEQUEUE = ' ' "Do not unlock IDoc yet
*  STATUS_CHECK = ' ' "Check Current Status
*  QRFC_STATE = 'U' "qRFC Status (Values U, Q, T)

 IMPORTING
   IDOC_CONTROL =  "Control Record

EXCEPTIONS
   DOCUMENT_NOT_OPEN = 1    FAILURE_IN_DB_WRITE = 2    PARAMETER_ERROR = 3    STATUS_SET_MISSING = 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_DOCUMENT_CLOSE_PROCESS

DOCUMENT_NUMBER - IDoc number

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

BACKGROUND - Database accesses in update task

Data type: EDI_HELP-BAG_OPTION
Default: NO_BACKGROUND
Optional: Yes
Call by Reference: No ( called with pass by value option)

NO_DEQUEUE - Do not unlock IDoc yet

Data type: EDI_HELP-UNLOCK
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

STATUS_CHECK - Check Current Status

Data type: EDI_HELP-FUNKTION
Default: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)

QRFC_STATE - qRFC Status (Values U, Q, T)

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

EXPORTING Parameters details for EDI_DOCUMENT_CLOSE_PROCESS

IDOC_CONTROL - Control Record

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

EXCEPTIONS details

DOCUMENT_NOT_OPEN - IDoc is not open for process

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

FAILURE_IN_DB_WRITE - Error during database insert or update

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

PARAMETER_ERROR - Parameter combination is invalid

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

STATUS_SET_MISSING - No status set

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

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

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