Digital Signature for Status Changes (SAP S/4HANA 2023)

Overview

Some status changes of a Change Record must be confirmed with a digital signature, for example the release of a product. SAP standard supports this: when a status action requires a signature, the status change is held back until a user signs. In a process controlled by XCM, however, the status change is often carried out by the process route itself, and without this feature the route would simply stop.
With Digital Signature for Status Changes, XCM recognizes that a status change is waiting for a signature and creates a signature task for the responsible users. They sign the Change Record, the status change is carried out, and the process continues with the next status.
Note: This feature is only available in XCM for SAP S/4HANA 2023. In SAP S/4HANA 2025 the signature can be requested during the approval of a task in the process route, so this feature is not needed there.

How it works

  1. The Change Record reaches a status change whose status action requires a digital signature. SAP holds the status change back: the Change Record shows the digital signature status Initial and the status action under Pending Status Change.
  2. XCM raises a process exception of type DS (Digital Signature) and creates the signature task for the agents determined in BRF+. The task appears in My Inbox.
  3. The agent opens the Change Record and signs it with the Sign button, by entering their SAP user and password.
  4. After the signature, SAP carries out the pending status change, and the process continues with the next status.

As long as the Change Record is waiting for a signature, no decision can be taken on its tasks in My Inbox. The approver gets the message Sign the Change Record before you take a decision on this task.
If the signature is cancelled, the signature task stays open and the process waits. The Change Record can be signed later, or an administrator ends the process.

Steps to configure

1. Define the signature in the SAP standard Customizing for digital signatures:

  • Define Individual Signatures – create the signature (for example S1) and assign it to an authorization group.
  • Define Signature Strategies – create a signature strategy (for example XCM03) and assign the signature to it. Use the signature method System Signature with Authorization by SAP User ID/Password if no external security product is used.

[Screenshot to be added: signature strategy with its individual signature]

2. Assign the signature strategy to the status action of the Change Record type. Maintain the view /PLMI/V_CR_H_DS with transaction SM30:

  • Change Record Type and Status Action – the status change that must be signed.
  • Signature Strategy – the strategy from step 1.
  • Signature Type – for example Asynchronous Signature Process. The signature is only requested when both the strategy and the type are filled.

[Screenshot to be added: digital signature for a status action]

3. Maintain the exception rule in the Process Control BRF+ application of the Change Record type: for exception type DS and exception scenario 02, enter the task XCM_DIGITAL_SIGN and the agents who must sign. For details on exception rules, see Exception Handling in Process Control.
[Screenshot to be added: BRF+ exception rule for DS / 02]

4. Grant the signers the authorizations to sign a Change Record header:

  • C_SIGN with signature application PLM_CR, signature object CR_HDR and activity 73.
  • C_SIGN_BGR for the authorization group of the signature from step 1.

Without both authorizations the Sign button stays disabled.

5. Activate the switch XCM_DIGI_SIGN_PROCESS_STAT_CHG (XCM Support on Digital Signature on Process Status Change) in the XCM Switch Framework. Activate it only after the BRF+ rule from step 3 exists. While the switch is inactive, status changes behave exactly as before.

6. Test the scenario: set a Change Record to the status that requires a signature, sign the Change Record from the signature task in My Inbox, and check that the process continues with the next status.

Note:

  • The task XCM_DIGITAL_SIGN is delivered without decisions on purpose. A decision would close the task without anybody signing.
  • If no BRF+ rule is maintained for DS / 02 while the switch is active, the status change step ends in error so that the missing configuration becomes visible.
  • Known limitation: after signing, the signature task is shown as Cancelled instead of Completed, and loading the next task can take a moment. This is being worked on.

XCM BAdI Usage

The check that refuses decisions while a signature is pending is delivered as implementation /XCM/PR_EI_DIGITAL_SIGN_CHECK of the BAdI /XCM/PR_EX_VALIDATE_DECISION. No own implementation is needed. For the BAdI itself, see Validate Decisions in My Inbox.

See Also

Exception Handling in Process Control
Change Record Status net
Validate Decisions in My Inbox
Advanced Process Control Framework

Keywords

Digital Signature, Electronic Signature, Status Change, Status Action, Sign, Signature Strategy, Exception Type DS, XCM_DIGITAL_SIGN, SAP S/4HANA 2023

Prerequisites

  1. XCM for SAP S/4HANA 2023, release 2026.3.4 or later.
  2. The Change Record type is controlled by XCM Process Control. For details, see Process Control - Task Configuration.