Page Comparison

• Via this setting

• possible languages / language combinations can be assigned to a document type / identification (language codes)

• . The possible language codes ones must be

• entered first.

• 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.

• 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.|

In this setting, actions and checks

can be set for specific 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.

• 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.|

In standard SAP DMS

, a new document

version can be created without restriction

from any document status.

About this setting this can be restricted, so that the creation of a new version

is only possible if the highest/current document version

is in a given status.

If no entry is made here for a document type / identification, then the versioning is not controlled by ProOBJ.

Controls the status handling of

previous versions when a target status of the current version

is reached. For example, setting an invalid status when the current version reaches

a release status.

This setting in this view disables a corresponding ProConfiguration setting. The old ProConfiguration settings are only handled by ProConfiguration for compatibility reasons. For details see ProConfiguration

customizing manual.

so that

the use as template for a new document is only possible if the template document

is in a

given status. If no entry is made here for a document type / identification

, the use as a template is not controlled by

ProOBJ.