Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 9 Next »

Overview

tia ZADOC is a software package that enables SAP-based document storage and research processes in a uniform user interface.
A special feature of this SAP add-on application is that archived documents do not necessarily need a reference to SAP standard objects (such as BKPF or VBAK). For example, documents for leasing vehicles or measuring equipment protocols can be managed with little effort.

The attribute values ​​that are to be used to describe the archived documents can be freely selected.

The settings are made via a few customizing steps.


Other tia ZADOC features:
• Any document type (PDF, TIFF, etc.) can be stored in an ArchiveLink™-capable archive system connected to the respective SAP system in dialog or via batch scenarios.

• In addition to the comprehensive search functions, there are extended storage scenarios available that can be used to easily and conveniently implement interactive archiving in dialog and mass storage of documents in batch mode.

• ZADOC supports the use of SAP ArchiveLink and SAP DVS document types.

• As long as the OLE-Interface is supported by Microsoft the storage of emails directly from Microsoft Outlook can be easily integrated.

• The SAP authorization system is integrated in KGS ZADOC.

• Archived documents can be displayed in a hierarchical structure using the tia ZADOC file manager.

Prerequisites for the installation of the software

To install tia ZADOC in the SAP system, the SAP transport container tia E75K900370 - ZADOC Version 3.6.3 Full Install ECC6.0 EhP8 - 7.50 04.24.zip, which is provided by KGS, must be imported into the SAP system.
Please note: For a successful import of the ZADOC transport, SAP Note 1560955 must be installed.

SAP ArchiveLink settings

The customer-specific settings that are necessary to archive and display tia ZADOC documents are encapsulated in the SAP ArchiveLink® interface. This interface has its own customer-specific settings.


The prerequisite for the tia ZADOC software system to function fully is that the ArchiveLink basic customizing has been fully implemented in the SAP system.

Transaction OAC0

At least one content repository must be configured in transaction OAC0.

The configuration of the repository should look similar to the one shown in the following image:

image-20240618-093815.png

Transaction OAC2

For each tia ZADOC document type, a reference is made to an ArchiveLink document type in SAP. This ArchiveLink document type can be created using transaction OAC2.
Example:

image-20240618-094404.png

or

image-20240618-094618.png

Each customizing entry consists of four fields:

  1. Document type: Unique technical name of an ArchiveLink document type (length: up to 10 characters, starting with “Z”, “Y” or the customer-specific namespace such as “/KGS1/”).

  2. Description: Language-dependent name of the document type. The name is displayed in all SAP standard transactions. It describes the document type and helps to identify documents that are linked to a specific SAP business object. Normally only this description is visible to the user (length: up to 40 characters).

  3. Document class: Technical document type. The document type is used to identify the archive format (file type) for documents in the content server. Possible values: “PDF”, “TIF”, “DOC” etc., plus “*” wildcard character (“*” stands for any technical document type).

  4. Status: Status flag: This indicator field has no influence on ArchiveLink itself. The status flag is used to determine whether a document type is displayed in the “Business Document Navigator” as a standard document type (status “X”) or a non-standard document type (status = “-“).

Transaction OAC3

In transaction OAC3, the creation of a link between the previously defined ArchiveLink document type and a suitable SAP business object must be specified.
If tia ZADOC is used for NON-SAP documents, the business object ZDOCUMENT or BUS0815 can be used.
Examples:

image-20240618-095119.png

or

image-20240618-095223.png

or

image-20240618-095402.png

  1. Object type: SAP business object types are linked to a special processing program tailored to this object type using certain basic data, key fields, attributes, methods with parameters, and events. Each object type encapsulates a basic business object logic (for example, the creation of a sales order) together with key field definitions to uniquely identify these objects (for example, an order number).

  2. Document type: Name of the ArchiveLink document type defined in transaction OAC2.

  3. L: Status flag for the link. OAC3 entries are only taken into account if this flag has the value “X”.

  4. Cont. Rep. ID: ID for establishing a connection to a content repository via which documents can be stored in a content server. Content repositories are defined in transaction OAC0. “Content Repository IDs” consist of two letters (e.g. “FI” or “T1”).

  5. Link: Name of the ArchiveLink link table. The relationships between SAP business objects and archived documents are managed in these link tables. SAP supplies four predefined tables in its standard systems (TOA01, TOA02, TOA03, TOAHR). These tables are often also called "TOA tables". In addition to the tables included in the standard SAP delivery, customer-specific tables can be created if required and then used to store ArchiveLink links (see the SAP customizing transaction OAD3).

  6. Retent. Period: Retention period. Number of months after which a link entry of a stored document can be deleted from the respective link table. This value is required for data archiving and for the SAP standard software component ILM. If the value is not used, it can also be left empty (value = “0”).
    ILM = Information Life-Cycle Management

DVS Customizing

DVS = SAP Document Management System. SAP DVS is often used to manage documents that are not only to be stored in a content repository, but are also subject to a change cycle as "living documents". To manage the change cycle, DVS allows the assignment of version numbers, status values ​​and other characteristics to the documents. The descriptive information is stored in so-called document info records. See also the application transactions CV01N, CV02N, CV03N and CV04N.

Transaction OACT

If you want to use tia ZADOC for archiving and retrieving DVS documents, you must create a storage category and assign it to the relevant tia ZADOC document type. The standard transaction OACT is used to create and maintain storage categories.

image-20240618-101434.png

To create a category, four fields must be filled in:

  1. Category: Name of the storage category. Assignment of the repository on the physical level to the category on the logical level.

  2. Description: Short description of the category used when displaying this category.

  3. Document Area: Application used in the SAP component KPro to store documents. Document areas are the topmost layer in the content model and form the context for document processing. In applications in which documents are important, different application areas can be separated from one another by "document areas".

  4. Content Repository: Name of a content repository in which documents can be stored on a content server.

Transaction DC10

The DVS document type is set up in transaction DC10. Example:

image-20240618-125145.png

To use DVS document types in conjunction with ti ZADOC, the basic settings of the DVS document types should be adjusted as shown in the previous screenshot.

image-20240618-125437.png

Important: The ZADOC transaction /KGS1/ZADOC_AR (used to archive ZADOC documents with DVS) sets the status of a document in a new DIS to the value FR. Therefore, the status FR must be set in the "Document Type" and the "predecessor status (Prev. 1)" must be left empty.

Using the tia ZADOC WebClient

  • No labels