Digitale signature
The use of a digital signature is optional and can be enabled for any task within a ProProcess process.
The digital signature is a standard SAP component that is not only used by ProProcess. In the following, only the Customizing relevant for ProProcess is described. For further information, please consult the SAP manuals.
The descriptions in the following subchapters may vary depending on the system release, as these are also defined by SAP.
BPF Applications
For the digital signature, one (1) application must be created in the customer namespace (for example, Z_BPF). The name can be freely chosen (e.g. ProNovia ProProcess).
The defined application must be maintained in the BPF Global settings in the field Application.
Application-log objects
SAP provides its own application log object CDSG1 for storing logs. A customer-specific sub-object must be created for this in the customer namespace.
The name can be freely chosen (for example, digital signature ProNovia ProProcess).
BPF Objects for the Digital Signature
For the digital signature, one (1) object must be created in the previously defined application.
-
The entry must be maintained as follows:
Field | Value |
|---|---|
Application | Previously defined Digitale signature | [hardBreak]BPF Applications |
Object | Freely selectable name from the customer name space |
Meta Table | /PCH/BPF_SIGNOBJ |
LogStruct | /PCH/BPF_SIGN_PROT |
Subobject | Previously defined sub-object for the Digitale signature | Application log objects |
Comment | Possible |
Renark | Possible |
ObjectDesc. | Yes |
Document | Possible |
Desc. | Freely selectable (e.g. ProNovia ProProcess) |
The defined object must be registered in Digitale signature | BPF Basic Settings for Digital Signature.
Single signatures
For the digital signature, one (1) individual signature must be generated in the customer namespace (for example, Z_BPF). The name can be freely chosen (e.g. ProNovia ProProcess).----
The authorization group can be used to control who can execute a signature for an individual signature. However, in ProProcess the restriction via authorizations can lead to problems, because ProProcess itself implements a logic, which users are allowed to complete tasks at which time and then must also have the authorizations in order to perform a digital signature, if necessary.
We recommend that no an authorization group is defined.
Signature strategy
For the digital signature, one (1) signature strategy must be generated in the customer namespace (for example, Z_BPF). The name can be freely chosen (e.g. ProNovia ProProcess). _
The other information must be maintained as follows:
Field | Value |
|---|---|
Signature method | Systemsign. mittels Autorisierung durch SAP-USERID/Passwort |
Display comment | Possible |
Remark | Possible |
Display document | Possible |
Verification | No |
The previously defined https://pronovia.atlassian.net/wiki/spaces/CUSTEN/pages/583306219 must then be assigned to the signature strategy.
The defined signature strategy must be registered in Digitale signature | BPF Basic Settings for Digital Signature .
BPF Basic Settings for Digital Signature
To use a digital signature in BPF, the following values needs to be registered in BPF Global settings :
Data according Digitale signature | BPF Objects for the Digital Signature
Data according Digitale signature | Signature strategy
© ProNovia AG | Imprint | Data Protection