Control groups are used to reduce Customizing efforts. Instead of Customizing having to be carried out for each document type that is handled, this is done for control groups. Afterwards, the document types, which are to be equipped with the corresponding settings, can be assigned to a control group.
Assignment of PC-applications
Definition, which PC application will be activated to a control group and how the data will be filled according to the settings. |
Control of the automatic value assignment
Controls, which status changes will trigger a new data filling of the document master original. (Typically before the conversion to a digital paper, at the last on release.) It is possible either to set the „Status from" (unique From-To-Definition) or to leave the field empty (any From – to unique To).
In the above indicated control group TECH, the values will be automatically assigned when status „FR" (Rejected) has been reached, in case of „ZP" (Validation), but only predecessor has „IA" (in work).
Fields Dest.Status, Convert.Status and Info/Parameter are only used for CAD conversion extensions of ProNovia SAP DMS FrameWork and are described in the relevant Manuals. |
Definition status ID
In order to assign the document master originals with the status and the relevant data (user, date etc.), but without using the status in the template directly, special Status-IDs will be used.
This way the ID's can be used for types of status (e.g. "Initial", "Check" and „Released"). On the document master original, the field name will be referenced with this ID.
In SAP DMS different statuses can have this meaning and in case of an automatic data assignment it may be necessary to select these statuses with a certain priority. For example "Initial" could be intepreted by „AA" (Initial), „IA" (Work) and last "ZP" (to check). If present, "TC" hast to be used for the data to print, else "IW" and last "CR".
This customizing view allows setting these IDs. They are freely selectable, e.g.: „1", „2", „3" or „A", „P", „F" as shown in the following example:
|
Rejected status
If the status network of a document allows a "Rejected" status, certain statuses that have already been set may not be filled during a new processing or automatic value assignment (for example, the check status before the rejection) after such a rejection.
For example, if a document passes through the following statuses:
AA (start of work) > IA (in progress) > IP (under examination) > PR (tested) > ZG (rejected) à IA
the statuses IP and PR must not be used before the ZG status when reassembling.
In this Customizing step, you can define which rejected statuses fall back to which active status for a tax group. ProObjectLib always ignores all statuses between the rejected status and the back-to-status.
If the status net of a document allows a "rejected" status, some already processed status may not be used for automatic data assignment after such a rejection.
As an example, a document runs through the following status:
AA (Initial) > IA (in work) > IP (in check) > PR (checked) > ZG (rejected) > IA
In case of a repeated automatic value assignment, status IP and PR processed before ZG must not be used.
|