User status profiles in SAP provide granular control over the lifecycle of business objects. A key function is the ability to assign authorization keys to specific user statuses. This restricts the ability to set or delete a particular status to only those users with the corresponding authorization (authorization object BUSERSTAT). Furthermore, status profiles allow for the definition of a processing sequence by assigning a status number to each status. By specifying a range of required preceding status numbers, the system enforces a priority, ensuring that statuses are set in a logical and predefined order.

A. Ensure user status must always be set manually

This is incorrect because a status profile can be configured to set a user status automatically when a specific business transaction is executed.

B. Allow business processes forbidden by SAP system status

This is incorrect. The system status always has precedence. A user status can only add further restrictions; it can never permit a business transaction that is forbidden by the system status.

1. SAP Help Portal for SAP S/4HANA 2021, "Defining Authorization Keys for User Statuses": This document confirms option C, stating, "You can define an authorization key for a user status. This allows you to make sure that only certain users can set or delete this status." The system checks against authorization object BUSERSTAT.

2. SAP Help Portal for SAP S/4HANA 2021, "Defining a Status Profile": This source supports option D. It describes the configuration fields "Status number," "Lowest stat.no.," and "Highest stat.no." which are used to "define a sequence for the user statuses." This effectively creates a priority system.

3. SAP Help Portal for SAP S/4HANA 2021, "System Status and User Status": This document invalidates option B. It explicitly states, "A user status cannot influence a business transaction that is disallowed by a system status. It can only further restrict the business transactions that are allowed by the system status."