Accessing Your System

Objective

After completing this lesson, you will be able to identify all the activities that are required to be completed before and after signing the contract to build your system.

Contract Signature

Road map with the customer onboarding journey with Key Milestones: Contract Signing, SAP Provisioning Activities, Customer Activities​.

In the weeks preceding or following the contract signature, a technical assessment is conducted by the Cloud Architect Advisor (CAA). Under the CAA's guidance, the customer completes the Customer Onboarding Form (COF) with all the technical details required for the system build. If your implementation is partner-led, then the Cloud Architect Advisor will be provided by the partner.

Upon the contract signature, a Technical Administrator, also known as the IT Contact, is designated from the customer side. This contact should not be the CIO, CTO, or CFO due to the nature and time required to perform these tasks.

After the contract signature, the IT Contact receives a Welcome E-Mail outlining the key next steps. These steps include ensuring the Customer Onboarding Form (COF) is completed accurately and with all the required information, as well as providing guidance on how to access the Onboarding Sessions and the Enterprise Cloud Services (ECS) Kick-off session.

Technical Support – SAP Provisioning Activities

SAP's Enterprise Cloud Services (ECS) team sets up customer systems for Private Cloud solutions. After contract signing, an ECS Kick-off meeting explains the provisioning process.

Network setup starts on the contract start date unless missing COF details cause delays.

Notification e-mails are sent to the IT contact specified in the contract, and only this contact can initiate provisioning.

Customer Activities

When the system build is completed, the IT Contact receives an e-mail with solution access details, including the URL for the SAP Extended Warehouse Management tenant.

Afterward, the IT Contact can log into the system and create additional users. Additionally, network setup from the customer’s side will be required to access the Private Cloud systems.

SAP will create only the Administrator user as specified in the contract. The Administrator user will then be responsible for creating all the necessary users who should have access to the system.

Once the system is delivered, the main technical contacts will validate the system access and ensure it aligns with the information provided in the Customer Onboarding Form. Ongoing collaboration with SAP Enterprise Cloud Services will continue throughout the process.

Additional Information

SAP EWM Provisioning Guide containing the steps to access your solution.

Conclusion

Now you are aware that the provisioning process requires the timely completion of several steps, such as the finalization of the Customer Onboarding Form with guidance from the ECS Team and the designation of the right person as the IT Contact. By completing these steps, your system will be provided within the expected timelines with the desired settings. Additionally, once the system is delivered, creating user accounts not only secures access but also empowers your team to hit the ground running in the Explore Phase of the project.

Log in to track your progress & complete quizzes