Access to a customer's Provisioning system is a highly privileged and secure process. For an external consultant or implementation partner to gain access, the customer must provide explicit, formal approval. This is a critical security and data privacy measure, ensuring that the customer retains full control over who can access their backend configuration environment. The request is typically initiated by the partner, and the customer's designated administrator must approve it before SAP will grant the access.

A. Have access to the customer's signed contract.

A contract establishes the business engagement but does not serve as a direct authorization for technical system access, which requires a separate, explicit approval process.

C. Assign the customer to your Provisioning ID.

This is a technical step that SAP performs to grant access after the customer has formally approved the partner's request. It is a result of approval, not a prerequisite.

D. Enable Company Settings in Provisioning for the customer.

This is an action performed inside the Provisioning system. Therefore, you must already have access to perform this task, making it impossible to be a prerequisite for requesting access.

---

1. SAP Knowledge Base Article (KBA) 2116056 - Partner Provisioning Access for SAP SuccessFactors HXM Suite: This KBA details the process for partners to request Provisioning access. It explicitly states

"The customer must provide authorization for the partner S-user ID to be granted access to their instance." This confirms that customer approval is a mandatory step. (Access requires an S-User ID for SAP for Me portal).

2. SAP Help Portal - SAP SuccessFactors HXM Suite | Provisioning Access and Settings: The documentation on Provisioning consistently emphasizes the separation of duties and security protocols. It outlines that access for non-customer personnel (like partners) is strictly controlled and requires customer consent as part of the standard operating procedure managed via SAP's support infrastructure. (Refer to sections on partner enablement and system access).