In this area following settings can be maintained:
- for data elements and revisions
- for language dependent documents
- automatic exchange of responsible user
During object handling with ProConfiguration, the settings for validity and revision, as well as the version control will never become active.
In general, documents should either exceptionally be created and versionized within ProConfiguration or outside. However if handled outside ProConfiguration, they can be linked to ProConfiguration. A mixed use is not recommended. Only exception: document version status handling, which is maintained here, also for ProConfiguration.A document created or changed by ProChangeDoc will be generally ignored by this settings. Except any filling of the characteristic "LangCode char." is supported. For this the ProChangeDoc document type and identification must be assigned to a control group with corresponding language codes.
Possible language codes
This setting allows assigning possible languages / language combinations (language codes) to document types / identifications. The language codes must be defined first.
The following checks and actions will be performed, dependent on the settings: - A document must be recorded with a part document number identical to the assigned language code. The language code will be part of the part document number.
- It is possible to define, that descriptions in user language and long text will be copied to the assigned description language.
- It is also possible to define, that the description must be available in all description languages when a certain status is reached.|
The description language controls two functions:
- With active option Copy description to all languages the language entered will be used as target languages.
- If a status as defined as described below is reached and option Requires maintenance of all description languages has been activated, then it will be checked that for all here registered languages a description is maintained.|
Definition of actions and checks to status changes of a document type / identification.
- Revision:
- In standard SAP DMS, the revision level will not be assigned before releasing the document info record. This way, the revision will not be known until release. Changes with the same revision (simple change) is also not allowed.
- With option Revision, it is possible to change this behaviour.
- In standard SAP DMS, the revision level will not be assigned before releasing the document info record. This way, the revision will not be known until release. Changes with the same revision (simple change) is also not allowed.
- For language dependent documents it is possible to define, that all descriptions must be maintained in all system languages (option All description languages must be defined).
- If option Requires maintenance of binding language is set, all languages with active option Binding language must be maintained.
- If option Requires language maintenance acc. code is set, all languages assigned to a certain language code must be maintained. The possible codes must be registered first.|
Standard SAP DMS allows creating new document versions without restriction on the document status. This option allows restrictions, e.g. a new version can only be created, when the highest/current document version corresponds the defined status. Without entry versioning will not be controlled by ProObjectLib.
Control of status handling of former versions in case the current version reaches a target version. Example: Set Invalid status when current version reaches Released status.
Please regard, this setting will deactivate any setting in ProConfiguration. Any ProConfiguration setting will only be handled for reasons of compatibility. For details see ProConfiguration Customizing Manual.
In standard SAP DMS, a document with any status can be used as a template for a new document. This setting can be used to restrict this, so that it can only be used as a template for a new document if the template document has a predefined status. If a document type / identification does not have a entry, the use as a template is not controlled by OBJ.