Enhanced approval states in Requirement Management – SAP Cloud ALM

In this blog post, I would like to explain

  • What is approval state
  • How does it work
  • How to work in case you don’t need approvals

In SAP Cloud ALM, Requirement management supports the approval process via the attribute “Approval”. This denotes the approval state of a Requirement. Please note this is separate from Requirement status and has no impact on Requirement status at the moment.

The values in the Approval state are

  • Initial
  • Ready for Approval
  • Approval not Required
  • Approved
  • Rejected

Submitter

The person submitting the Requirement has to make an informed decision if the Requirement needs approval and if there is enough information for the approver to take a decision

Approver

The approver should know that Approved and Rejected are final states and can not be changed. In case the approver wants to give room for resubmission then he or she should not use Rejected approval state but use comments

Resubmission after Rejection

If the submitter wants to modify a Rejected Requirement for fresh approval, we recommend using Requirement Copy and submitting a new one.

Approval Flow

This is visible in the Requirement list as filter criteria. It is shown in Requirement details as well. It is also a filter criterion in Traceability Reports

In case you do not need approvals, you have multiple options

  • Set the approval state for Approval not Required
  • Directly move a Requirement from In Refinement to In Realization

Currently, any Project member can approve or reject but its tracked in the history

As we publish more and more blog posts, it’s easy to get lost. Please visit the Master Blog post and bookmark it.

To understand an end-to-end picture, please visit

Expert Portal for Implementation and stay connected