Content Comparison

...

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 = “-“).

...

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:

or

...

or

...

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

...

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 Added

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.