Digital signature allows documents like notifications, work order operations to be signed and approved in SAP. Asset Manager starting with version 2105, supports digital signature but standard EAM backend configuration doesn’t include an option to enable digital signature for Work Order Headers and in this blog post, you'll learn about a customization approach to enable digital signature feature for WO headers.
This process has a few steps which are explained below:
- Register application
Launch transaction ‘SIGNA’ and provide an application name or a grouping element for signature objects to link to the digital signature. Save the entries and this registers the application for digital signature.
Example:
SIGNA-Register application
- Create an entry for application object in SLG0
Go to transaction ‘SLG0’ to register the log object under CDSG1. This is to capture digital signature logs related to your application and this log object is mapped to your application/signature object in the later steps.
Search for the entry ‘CDSG1’ and double-click the sub-objects folder. Create a new entry with following values:
Field |
Description |
Sub-object |
Specify the object to associate log entries. |
Sub-object text |
Description |
Example:
SLG0-Add Sub-Object
- Define Signature Object
Launch transaction ‘SIGNO’ to define a signature object for your application to which you want to link the digital signature.
Below table shows fields to be populated on this screen:
Field |
Description |
Application |
Specify the application that you registered using SIGNA transaction in the previous step. |
Object |
Specify the signature object that is to be signed later. |
Metadata table |
Specify the metadata table that is defined for digital signature applications. Standard table for Order Operation ‘AFVC_DS’ can be used. This table contains digital signature data for the work order header/operation objects. |
Log structure |
Specify the log structure defined for digital signature applications. Standard structure for Order Operation ‘AFVC_DS_LOG’ can be used. |
Subobject |
Specify the sub-object for the application log that you created in the transaction SLG0 |
Comment |
If it’s set, it’s mandatory to specify a free text comment to execute digital signature. Set the configuration you require. |
Remark |
If it’s set, it’s mandatory to select a remark from a list of predefined remarks and add it to the signature provided. Only then user will be able to execute digital signature. Whether remarks are available depends on the respective application. The individual remark texts are made available by the application. Set the configuration you require. |
Object description |
If the indicator is set, the description of the signature object is displayed in the title bar of the signature dialog box during the signing process. Set the configuration you require. |
Document |
Specify whether the signatory is permitted to view the document to be signed. Set the configuration you require. |
Description |
Specify description of the signature object or application for which a digital signature is provided. This object description is displayed in the dialog box in which you provide the signature. Depending on the application, it may be extended by an addition that describes the signed object more exactly. This description is then part of the signed document. It is added to the document in the language in which the signature was provided. Set the configuration you require. |
Example:
SIGNO-Register Signature Object
If you selected the setting ‘Disallowed’ for a signature object in the fields Comment/Remark/Document, this setting overrides all other settings that you make for the signature strategy in Customizing for the digital signature.
- Ensure customizing settings for TOTP strategy are provided in Implementation Guide (IMG) under Cross-Application Components -> General Application Functions -> Digital Signature -> Signature strategy
Once above steps are completed, navigate to configuration panel using transaction code '/n/SYCLO/CONFIGPANEL'. Click on 'oData Mobile Data Object Configuration' under oData Channel Settings. Choose the filter at the top of the screen for the application which you want to modify - SAP Asset Manager 2105 or later
- Select oMDO SAM2105_DIGITAL_SIGNATURE_LINK -> Data Filter -> Read -> Data distribution -> Signature Config.
Add a static table entry in this step that matches with SIGNO data and link to metadata table via field ‘OBJNR’. Specify object_type as ‘OR’ (for Work Order Header). Please see the example below
Signature Config Filter
- Next select SAM2105_DSIG_CONFIGURATION from oMDOs -> Data Filter -> Read -> Standard Filter
- Signature_app -> Add a static table entry for application created in SIGNA and set it to Active.
Signature App Filter
- Signature_object -> Add a static table entry for signature object created in SIGNO and set it to active.
Signature Object Filter
Please ensure that the above filters match with SIGNA and SIGNO data.
Navigate to configuration panel home using the link in the upper left corner. Next click on ‘Mobile Application Configuration’. Choose your mobile app and click on the ‘Parameters’ tab.
Enable mobile application parameter under group ‘DIGITALSIGNATURE’ to be able to sign a WO header document. Parameter WO.Complete should be set to ‘Y’.
Mobile App Parameters
This completes the configuration to digitally sign a WO Header document from SAP Asset Manager app.
For additional information on Digital Signature:
https://help.sap.com/viewer/70761bba72014fb48199b9232d0d8409/7.51.13/en-US/a775745b9bc84d86ad83edbd6...