Entering content frameFunction documentation Storing Outgoing Documents Locate the document in its SAP Library structure

Use

Outgoing documents are stored synchronously. Outgoing documents created in SAPscript or SAP Smart Forms are stored using transactional RFC.

Note

Outgoing documents are only in PDF format; they are no longer created in OTF Format.

Advantages of synchronous storing

Prerequisites

All transactional RFC calls are stored with the ABAP language element COMMIT WORK in the database. These RFC calls thus constitute a Logical Unit of Work (LUW).

It is assumed that a COMMIT WORK usually ensues after calling the SAPscript/SAP Smart Forms function module in the relevant SAP application. If this is not the case, it is possible to transfer the value "Commit" when calling the function module (for example, OPEN_FORM) in the import parameter ARCHIVE_INDEX-RESERVE(6). If this value is set, a COMMIT WORK is triggered by an ArchiveLink function module.

Note

COMMIT WORK is not allowed during posting. If the value "Commit" is set in the import parameter ARCHIVE_INDEX-RESERVE(6) to trigger a COMMIT WORK in the ArchiveLink function module, there must be no posting active. Otherwise there is a runtime error COMMIT_IN_POSTING.

Note

For more information, see Storing Outgoing Documents and Form Overlay.

Leaving content frame