Accessing Your System

Objective

After completing this lesson, you will be able to finalize the system provisioning process to ensure the system is fully operational and ready for a successful project implementation.

Contract Signing

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

Before or during the signing of an SAP contract, a technical assessment is conducted with the assistance of a Cloud Architect. During this assessment, customers are required to complete the Customer Onboarding Form (COF), providing all necessary details. If the implementation is handled by a partner, the Cloud Architect will be from the respective partner organization.

Once the SAP contract is signed, a Technical Administrator, also known as the IT Contact, is nominated from the customer's side.

After the contract is signed, the IT Contact will receive a welcome e-mail outlining key next steps. These include ensuring the COF is completed accurately with all required information, as well as guidance on how to access the Onboarding Sessions and the Enterprise Cloud Services (ECS) Kick-off session.

SAP Provisioning Activities

SAP has an Enterprise Cloud Services (ECS) team responsible for building our customers' systems for Private Cloud solutions. Once the contract is signed, an ECS Kick-off meeting is held, during which the SAP ECS team outlines the provisioning process.

Network setup is essential to enable system access, and provisioning begins on the contract start date, unless there are delays due to missing details in the COF.

Notification e-mails are sent to the IT contact specified in the contract. It is important to note that only the IT contact listed in the SAP contract has the authority to initiate the provisioning process.

Customer Activities

The IT Contact, upon receiving the notifications, will also receive an e-mail with solution access details, including the URL for the SAP Transportation 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.

It is important to note that SAP will only create the Administrator user specified in the contract. The Administrator user will then be responsible for creating all other users in the system.

Once the system is delivered, the Main Technical Contacts will validate the system access and ensure it aligns with the COF document. Ongoing collaboration with SAP Enterprise Cloud Services will continue throughout the process.

Additional Information

Provisioning Guidewith steps and guidelines on how to access your system.

Conclusion

Understanding the system provisioning process, along with the various roles and requirements involved, is crucial. This knowledge will help ensure a smoother experience, allowing you to get your system up and running faster and proceed with the implementation to support your business.

Log in to track your progress & complete quizzes