Ansicht
Dokumentation

EDI_DOCUMENT_CLOSE_FORCE - EDI interface: Close IDoc after open for force

EDI_DOCUMENT_CLOSE_FORCE - EDI interface: Close IDoc after open for force

BAL_S_LOG - Application Log: Log header data   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.
SAP E-Book

Functionality

An IDoc is to be generated.

During the creation, it was found that the IDoc was incorrect and can only therefore be stored with the status 'Created incorrectly'. Closing an IDoc ; the IDoc number is obtained via number assignment. The entire IDoc is written to the database under this number.

Data records in EDID2; Status record in EDIDS; Control record in EDIDC

Example

After an IDoc was opened using the function modules: EDI_DOCUMENT_OPEN_FOR_CREATE or EDI_DOCUMENT_OPEN_FOR_FORCE and EDI_SEGMENT_ADD_NEXT or EDI_SEGMENTS_ADD_BLOCK and filled with data stored in internal tables, the function module should close this Idoc and store it in the database.

The IDoc should be stored with the status 'Created incorrectly'.

* Ident - identification from the open function module

data: mess like edimessage.

= 'E'. mess-msgty ='999'.

= '99'. mess-msgno ='Error identification'.

mess-msgid

mess-msgv1

call function 'EDI_DOCUMENT_CLOSE_FORCE'

exporting

identifier = help_ident

mess = mess

importing

idoc_control = edidc.

exceptions

others = 01.

Notes

Further information





Parameters

IDENTIFIER
IDOC_CONTROL
LOCATION
MESS

Exceptions

DOCUMENT_NOT_OPEN
DOCUMENT_NO_KEY
FAILURE_IN_DB_WRITE
PARAMETER_ERROR

Function Group

EDI1

ROGBILLS - Synchronize billing plans   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 2158 Date: 20240523 Time: 120351     sap01-206 ( 33 ms )