Skip to main content

S4HANA : PM/CS - Enable E- signature at Operations


This blog is about a E- signature Functionality at service Order or Maintenance Order Operation Level.

We use Maintenance or service Order Operations to perform certain tasks on the Equipment and once the task is executed, this operation can be confirmed.

During Confirmation, we can do Digital signature, it is confirmation from Customer or particular Work Center


Configurtion:

SPRO-->PLANT MAINTENANCE & CUSTOMER SERVICE--.>MAINTENANCE & SERVICE ORDERS-->FUNCTIONS AND SETTINGS OF ORDER TYPES--.>DEFINE DIGITAL SIGNATURES FOR ORDER TYPES.

You need to define signature strategy for Order type and Plant

signature strategy:-

                  This determines individual signature to be assigned for operation

Digital signature Flag:-

               This controls if a Digital signature is mandatory, optional or not required to be assigned at Operational Level

signature type:

         here, we have option to perform Digital signatures with SAP user and password

Create a service Order with Operation in IW32 or IW21


confirm the operation in IW41


at operation level, upon configuration of Digital signature, you can see Digital Operation level


once the Digital signature is set, you can see status as DSIG with log



We can view the Digital signatures using DSAL transaction for particular application

You can  Generate Digital Signatures using Adobe forms and upload to SSF admin portal


let me know if you have any further questions or clarifications





Comments

  1. Informative.Will try out and update.
    Keep going.

    ReplyDelete

Post a Comment

Popular posts from this blog

SAP SD/CS/PS /PM : System status and User Status a differentiation

In SAP, Master Data and Transaction data is controlled by system status.  But there are certain limitation where system status cannot be used, In such instances a User status can be used. We will see how a system status and User status functions in a particular transaction. Let's understand what is "SYSTEM STATUS" and  "USER STATUS" from system perspective. SYSTEM STATUS:-                                                       A system status is set by the system automatically upon executing a function. It                            Specifies that a particular function was carried out on an Object, be it a                            Transaction ( like Service Order) or a master Data ( serial Nu...

S4HANA : How to activate Quick Cut and Paste in S4HANA

We are used to "quick cut and paste" option in ECC system to cut and paste. Let us see how this has to be activated in S4HANA In S4HANA, this indicator is not available by default for all Themes. You need to activate it. To activate it in S4HANA, first check the Option from  In the Options menu, choose Theme other than " Belize: such as Corbu or something other than Belize. This will take you to a screen Them and here you can select the Option for Quick Cut and Copy In this way it should be activated in S4HANA system. please try and let me know if you still find difficult in S4HANA

S/4HANA : Sales -- How to check the list of Incomplete Sales Orders

in General, while Creating a sales Order there are certain fields which would be considered important for further processing of Sales order. Although these fields are not marked as Mandatory , but considered to be equally important to Mandatory fields Such fields are controlled by Incompletion  Procedure Functionality in Sales and Distribution. We will see how to Find Incomplete list of Sales Orders in S4HANA Steps:-- 1. Create a sales Order in VA01 ---( Create Sales order App in S4HANA) 2. For testing, I have not maintained Purchase Order field in the Sales Order- Overview Screen. In S4HANA this field is termed as CUSTOMER REFERENCE . While Saving the sales Order, system prompts to enter this field ( based on the Configuration of Incompletion Procedure) 3. In ECC, we can either go to Sales order-->Edit-->Incompletion documents and check what fields are missing 4. In case, if you want to look collectively for multiple documents, we use V.02  ...