Data Archiving

LAZAR provides the infrastructure to make document based information available anywhere and at the right time.

The correct processing and valuation of enterprise-relevant business transactions depends on up-to-date knowledge of the content of business documents, and how this content is to be further processed. Whether it is approval and release procedures, purchasing, sales, or application procedures, or the decision process, all require business information to be available, transparent, and legally secure, and therefore also require the integration of original documents. Documents are exchanged between enterprises and automatically controlled transactions are initiated, therefore creating transaction content and values.

Immediately after arrival in the enterprise faxes, emails or post items can be stored and then distributed and assigned to an existing business object, or to a business object that is to be created - as a part of the processing. Using this procedure, time-consuming work processes such as photocopying and distribution of originals, searching of information and core activities within paper based archives can be avoided. Documents are available and can be displayed and executed at anytime and anywhere. Integrated documents provide the necessary business information for a process from an early stage. LAZAR provides the technology for integrating business documents into business processes and search procedures in digital and unchangeable formats.

LAZAR standard scenarios are fundamental to the easy implementation of document integration.

  • Automated storage and management of incoming documents based on WebFlow.
  • Automated linkage and storage of incoming documents using bar codes.
  • Ad hoc processing of incoming documents.

Storage of outgoing documents: If SmartForms based documents are printed, faxed, or e-mailed, these can be automatically stored and assigned to a business object.
Print lists (reports) can contain, for example, data selected from a database for later revision, and can stored either alongside the printed versions or instead of them. Examples of print lists are account update logs in finance, warehouse stock, and logs.

LAZAR Archiving Example
With only a few Customizing settings, for example in SAP Customer Relationship Management, the standard scenarios can enable an incoming scanned request for a product to automatically initiate a sales transaction. In further transaction processing of the transaction, the responses or further incoming memos are stored along with the request.