EDI_DOCUMENT_OPEN_FOR_EDIT SAP Function module

EDI_DOCUMENT_OPEN_FOR_EDIT is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name EDI_DOCUMENT_OPEN_FOR_EDIT into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: EDI1
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM EDI_DOCUMENT_OPEN_FOR_EDIT - EDI DOCUMENT OPEN FOR EDIT

CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT' "
  EXPORTING
    document_number =           " edidc-docnum  IDoc Number
*   already_open = 'N'          "
  IMPORTING
    idoc_control =              " edidc
  TABLES
    idoc_data =                 " edidd
  EXCEPTIONS
    DOCUMENT_FOREIGN_LOCK = 1   "
    DOCUMENT_NOT_EXIST = 2      "
    DOCUMENT_NOT_OPEN = 3       "
    STATUS_IS_UNABLE_FOR_CHANGING = 4  "
    .  "  EDI_DOCUMENT_OPEN_FOR_EDIT

ABAP code example for Function Module EDI_DOCUMENT_OPEN_FOR_EDIT

The ABAP code below is a full code listing to execute function module EDI_DOCUMENT_OPEN_FOR_EDIT including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_idoc_control  
 
 TYPE EDIDC
,
it_idoc_data  
 
 TYPE STANDARD TABLE OF EDIDD,"TABLES PARAM
wa_idoc_data
 
 LIKE LINE OF it_idoc_data
.

 

SELECT single DOCNUM 
  FROM EDIDC 
  INTO @DATA(ld_document_number).


DATA(ld_already_open) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
.

CALL FUNCTION 'EDI_DOCUMENT_OPEN_FOR_EDIT'
  EXPORTING
    document_number =            ld_document_number
*   already_open =               ld_already_open
  IMPORTING
    idoc_control =               ld_idoc_control
  TABLES
    idoc_data =                  it_idoc_data
  EXCEPTIONS
    DOCUMENT_FOREIGN_LOCK =      1
    DOCUMENT_NOT_EXIST =         2
    DOCUMENT_NOT_OPEN =          3
    STATUS_IS_UNABLE_FOR_CHANGING =    4
    .  "  EDI_DOCUMENT_OPEN_FOR_EDIT

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_idoc_control
 
 TYPE EDIDC ,
ld_document_number
 
 TYPE EDIDC-DOCNUM ,
it_idoc_data
 
 TYPE STANDARD TABLE OF EDIDD ,
wa_idoc_data
 
 LIKE LINE OF it_idoc_data,
ld_already_open
 
 TYPE STRING .



SELECT single DOCNUM 
  FROM EDIDC 
  INTO ld_document_number.
 

"populate fields of struture and append to itab
append wa_idoc_data to it_idoc_data.
ld_already_open = 'some text here'.