Define single signature

In this work step, you define the signatures that users in a specific authorization group must make.

You can then use these single signatures as individual steps in a signature strategy when a status in the ECR/ECO is approved.
If a single signature suffices to approve the status that is set in the ECR/ECO and no signature strategy is required, you do not have to define the single signatures.

Example

In your company, release of the ECR/ECO must be approved by the production manager, the release of object changes (for example, BOM changes) by the engineering/design manager.

You define the following single signatures:

• SM with the authorization group Release change master record

• SO with the authorization group Release object

Preconditions

Define authorization group

Activities

Define the single signatures that must be entered when your ECR/ECOs are approved.

Further notes

Single signatures also apply in other areas that use the digital signature. Before you change the individual signatures available or use them for your own purposes, please check that no conflicts arise with other areas.