Ansicht
Dokumentation

ELSIG_03 - Specify Signature Method for Approval Using Simple Signature

ELSIG_03 - Specify Signature Method for Approval Using Simple Signature

General Material Data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.
SAP E-Book

In this IMG activity, you define the settings for approval using simple signature. For a simple signature, the signature process comprises one signature only, that is, only one person needs to sign. The signature process is completed when the authorized person has signed the document.

If no signature strategy is required to sign a document, but only the signature of one person, you must specify the signature method for the signature object in this Customizing activity and also specify other options. This signature method is then automatically valid for all processors of the application to which you have not assigned a signature strategy

In the transaction SIGNO, you have defined a signature object for your application that you want to link to the digital signature.

Make the following settings:

  • Signature object
You specify the signature object for your application. All the following settings then apply only for this signature object.
  • Signature method
Here, you select the signature method. This signature method is then valid for all signatories of the application to which you have not assigned a signature strategy You have the following options:
  • System signature after verification of the SAP user’s local password

Here, you do not require an external security product. With this signature method, the signatory identifies himself or herself with his or her SAP user ID and password, just as when logging on to a system.
Following a successful identity check, the system provides the digital signature, whereby the user’s name and ID are part of the signed document.
  • System signature after verification of the SAP user’s external password

With this signature method, the signatory identifies himself or herself with his or her SAP user ID and external password. Following a successful identity check, the system provides a digital signature, whereby the name and user ID of the signatory are part of the signed document.
  • System signature after verification of the SAP user’s TOTP password and TOTP passphrase

With this signature method, the signatory uses a process to generate time-based one-time passwords (TOTP). The signatory identifies himself or herself using a TOTP password and TOTP passphrase. Following a successful identity check, the system provides a digital signature, whereby the name and user ID of the signatory are part of the signed document.
  • User signature with verification

Here, you do require an external security product. The user provides the digital signature using his or her own private key and the signature provided is checked immediately to verify its authenticity.
  • User signature without verification

Here, you do require an external security product. You can use this signature method for test purposes only and not in a production system. The user provides his or her signature as described in the previous method, however, the automatic verification is deactivated.
  • Comment
You specify if the user has the option of entering a text comment when signing the application. You have the following options: Disallowed (no comment field is provided), Possible (comment field can be called up), and Required (signature is only possible after a comment has been entered).
  • Remark
You enable the user to select a remark from a list of predefined remarks and to add this to the signature. The availability of remarks depends on the respective application. You have the following options: Disallowed, Possible, and Required.
  • Document
Here, you configure whether the digital data to be signed is to be displayed for the signatory as well in the user dialog for entering the signature. You have the following options: Disallowed, Possible, and Required. However, the system only supports the display of data that has been transferred in text format.
  • Verification
You can verify previously executed signatures. A check is run in the background to determine if this document is still identical to the original document and if the previously executed signatures have been stored correctly in the system. If you use the user signature, you always work with verification in the production system. The validity of the user certificate is not checked for signatures without verification. This signature method should therefore only be used for test purposes.

The settings for Comment, Remark, and Document are overridden if you set the option Disallowed for each of these points in the system table for the application (transaction SIGNO).






General Material Data   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Length: 6007 Date: 20240523 Time: 194144     sap01-206 ( 109 ms )