Storing Outgoing Documents
Use
Outgoing documents are stored synchronously. Outgoing documents created in SAPscript or SAP Smart Forms are stored using transactional RFC.
Outgoing documents are only in PDF format. Outgoing documents are no longer created in OTF Format.
Advantages of synchronous storing
-
Outgoing documents are stored synchronously, that is, as soon as the storage request is made.
-
When using transactional RFC, no update termination is initialized if an error occurs during storing.
-
Unsuccessful storage requests can be monitored using the monitor. Storage requests containing errors can be repeated individually. To do this, select
Environment 
Transactional RFC 
in the monitor.
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 in the import parameter ARCHIVE_INDEX-RESERVE(6). If this value is set, a COMMIT WORK is triggered by an ArchiveLink function module.
COMMIT WORK is not allowed within the update. 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.