| 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
...
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.
...
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 document type
The behavior of tia ZADOC archiving and retrieval transactions can be defined by a set of customizing options. These options include transactions for
...
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.
...
# | 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 |
Maintenance of ZADOC attributes (/KGS1/ZADOC_MAINT_AT)
The attributes available for ZADOC can be maintained using the transaction /KGS1/ZADOC_MAINT_AT. Just like /KGS1/ZADOC_MAINT_DO, this transaction uses an SAP table maintenance dialog to insert, modify or delete document type-related attribute entries. After starting the transaction, the following screen is displayed (example):
...
Each attribute definition consists of the following fields:
ZADOC Doc. Type: This field refers to the ZADOC document type for which this attribute is to be made available.
Attribute Name: This field must contain an attribute name (uppercase only, up to 16 characters) that is used to identify the attribute.
Attribute Text: This field can contain a descriptive text for the attribute (up to 32 characters long) that is used for identification purposes (see the ZADOC archiving and retrieval transactions).
Seq. No.: This field determines the order in which the ZADOC attributes are displayed on the screen. The smaller the value, the higher the attribute is displayed in the attribute input areas of the pop-up windows and the selection screens.
ABAP type: Select specific ABAP type: Possible ABAP types for correct storage in the tia ZADOC tables
Mandatory: This check box contains a check mark if the corresponding attribute is to be treated as a mandatory attribute, i.e. if the attribute field must be filled with a non-empty value. Please note: Within the ZADOC transactions, mandatory fields are marked with a symbol (see file name and status attributes in the screenshot below).
Restricted: Only predefined values may be used. These values are offered by the field input search help.
R/O during Upload: If this flag is set, the attribute field cannot be changed when the document is saved.
Use in GOS Title: If the flag is set, the attribute is used as part of the title in the GOS and is therefore visible in the ArchiveLink hit lists (requirement: SAP Note 1560955 "Additional attributes for GOS attachment list" has been imported into the relevant SAP system).
Note: The "Use in GOS Title" function is currently only available for the FILENAME and XVERSION attributes. GOS = Generic Object ServicesLength check:
Upper case:
Auto fill:
Search Help Name: Contains the ABAP object name of the search help to be offered in the attribute entry and selection screens (e.g. company code: C_T001).
Check Table: Contains the name of the database table against which the entered attribute values are checked (example for company code: table is T001; in combination with the field name BUKRS specified as "Check Field", only company codes from table T001 are accepted as valid field values in this example).
Check Field: Name of the check field that is to be used to carry out the validity checks described above (example for company code: BUKRS).
Default value:
Filename:
Special predefined attribute values (/KGS1/ZADOC_MAINT_AV)
Predefined attribute values can be defined per ZADOC document type after starting the transaction /KGS1/ZADOC_MAINT_AV. This transaction uses a table maintenance dialog to insert, change or delete attribute values. After starting, the transaction displays the following screen (example):
...
Each attribute definition consists of four fields:
ZADOC Document Type: This field contains the name of the tia ZADOC document type for which predefined attribute values are to be made available.
Attribute Name: This field must contain one of the attribute names maintained in transaction /KGS1/ZADOC_MAINT_AT (uppercase letters only, up to 16 characters) with which the attribute is identified.
Sequence Number: This field determines the order that is to be used to display ZADOC predefined attribute values.
Attribute Value: This field can contain any attribute value (length: up to 64 characters).