Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CA-DMS (Application Component) Document Management System⤷
CV (Package) Application Development: R/3 Document Management
Basic Data
| Data Element | AUDIT |
| Short Description | Content version |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | XFELD | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | AUDITFLAG | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Cont.Vers. |
| Medium | 15 | Content Version |
| Long | 20 | Content version |
| Heading | 1 | C |
Documentation
Definition
The indicator controls that a new content version is created when the next time original files (File 1, 2 and so on) are stored
Note:
When the document type does not support storage using the Knowledge Provider the original application files must be one of the following secure storage areas: archive, vault, or SAP Database.
Use
Content versions allow you to reproduce processing statuses of the original application files. In this way the work step Create new version is no longer required in this case.
Procedure
Examples
Dependencies
The processing statuses that are saved automatically by the audit function are marked in the status log and can be called during processing of the document info record in the following ways: The structure of the original file is shown on the tab page Originals when storage was done using the Knowledge Provider. When the Knowledge Provider was not used you display the status log.
History
| Last changed by/on | SAP | 20020828 |
| SAP Release Created in |
