| View file | ||
|---|---|---|
|
...
Each customizing entry consists of four fields:
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/”).
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).
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).
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
...
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).
Document type: Name of the ArchiveLink document type defined in transaction OAC2.
L: Status flag for the link. OAC3 entries are only taken into account if this flag has the value “X”.
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”).
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).
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
...
To create a category, four fields must be filled in:
Category: Name of the storage category. Assignment of the repository on the physical level to the category on the logical level.
Description: Short description of the category used when displaying this category.
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".
Content Repository: Name of a content repository in which documents can be stored on a content server.
...
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.
...
.
ZADOC-Customizing
The behavior of tia ZADOC archiving and retrieval transactions can be defined by a set of customizing options. These options include transactions for
maintaining the tia ZADOC document types (for example, raw material specifications are used by procurement, additional inspection plans by QA and technical specifications by design),
defining a set of attributes used by the respective ZADOC document types,
specifying specific default values for various attributes, as well as for
maintaining storage categories to be used in conjunction with DVS document info records.
The following chapters describe how to use these transactions.
Maintenance of the ZADOC link tables (/KGS1/ZADOC_MAINT_M3)
...
The tia ZADOC software package already contains five link tables (/KGS1/ZADOC_LNK1, ..., /KGS1/ZADOC_LNK5) as standard. If required, these tables can be supplemented with customer-specific tables.
Assignment of ZADOC document types to link tables (/KGS1/ZADOC_MAINT_MT)
...
Links the specified ZADOC document types with a dedicated ZADOC link table. For ZADOC document types that are not listed in this table, the default value /KGS1/ZADOC_LNK1 applies.
Maintenance of ZADOC document types (/KGS1/ZADOC_MAINT_DO)
The structural element most commonly used by tia ZADOC software is called “ZADOC document type”. While ZADOC is executing archiving or retrieval transactions, the ZADOC document type is the first piece of information to be specified.
Example: When using the ZADOC retrieval transaction to search for “raw material specifications”, one can select the previously defined document type MATERIAL.
...
Meaning of the table columns shown:
# | Column | Description | Possible values |
|---|---|---|---|
1 | ZADOC document type | Unique identifier for each ZADOC document type | Any unique name consisting of up to 10 characters. |
2 | Shortcut | Shortcut for the document type name | Two freely selectable letters (e.g. “MA”) |
3 | Technical Document type | Contains either the name of an existing ArchiveLink document type (see transaction OAC2) or the name of an existing DVS document type (see transaction DC10). | For valid ArchiveLink document types, see column AR_OBJECT in table TODV. |
4 | Document type is used in DVS | Flag: If set, ZADOC creates and maintains DMS document info records and links stored documents to SAP business objects. | Check box: either set or empty. |
5 | Cross-Plant document type | Flag: If set, ZADOC documents are saved across plants. Subsequent access to such documents is then possible regardless of the plant to which a user belongs. | Check box: either set or empty. |
6 | Sales Org.related | If this flag is set, a connection to a sales organization is saved. This connection must be set during the archiving process. | Check box: either set or empty. |
7 | ZADOC document type description | Standard text used to identify the ZADOC document type. | Any description text. |
8 | Main SAP business object type | Most important object type used to create ArchiveLink or DVS links between stored documents and SAP business objects. | For valid SAP object types, see table TOJTB. |
9 | Search Help | Search Help for main SAP object type | Standard SAP Search help |
10-17 | SAP object type 2 … 9 (optional) | Additional business object types that are linked to a document. If the DVS flag is set in column 4, this field may only contain a DVS-compatible DVS object type. | For valid SAP object types, see table TOJTB. |
18 | Download Date | ||
19 | Download Time | ||
20 | Download DT first | ||
21 | Save attributes | ||
22 | Delete Document | ||
23 | Connection Table V2 | Obsolete: ZADOC link table – only needs to be specified if using ZADOC version 2.x. | /KGS1/ZADOC_NEXxx= 1,2,3,4 or 5 |