Terms & Conditions
By clicking "Accept" or “Agree,” you agree to all of the terms and conditions stated in this Agreement. If you do not agree to these terms, do not click "Accept" or “Agree.” By clicking “Accept” or “Agree” you hereby represent and warrant that you have been given the power of attorney by your employer (“Customer”) to carry out this transaction and conclude the respective contracts with SAP on behalf of your employer. If you do not have the appropriate power of attorney, we kindly ask you to not continue with this transaction.
Once completed, this agreement (defined below) is a legally binding agreement for SAP Services between Customer and the SAP affiliate or subsidiary company in the country in which Customer is located and from whom Customer is ordering the Services displayed in the Purchase Review and Order Confirmation (both defined below) (“SAP”).
Please note, that the transaction will only be completed, and the contract formed, when SAP accepts Company’s offer by either SAP sending an order confirmation e-mail to Customer, or the Services have been made available to Customer by SAP. Until then, if any issue arises regarding the processing of the order, SAP reserves the right to cancel the transaction and Customer will be notified accordingly
This order document (Order Form) is governed by and incorporates the following documents in effect as of the effective date. All documents are listed in order of precedence, and collectively referred to as the “Agreement”:
Customer has had the opportunity to review the Agreement, including without limitation the Scope Document, the GTC, the DPA and terms and conditions mentioned above, prior to accepting this Agreement. For purposes of this Agreement, the following provisions of the GTC shall not apply: Change Request Procedures (generally section 4) and Satisfaction with Personnel (generally section 5).
SAP recommends Customer prints copies of this Order Form, the applicable DPA and GTC for Customer’s own records.
1 SERVICES FEES AND PAYMENTS
The applicable Service fees (“Service Fees”) for the Services are identified in the purchase review displayed on the SAP Store (“Purchase Review”) as well as in the corresponding order confirmation email Customer receives from SAP (“Order Confirmation”). The Service Fees are payable by Customer as follows.
(a) If Customer is registered as an authorized buyer of SAP products, Customer may choose to pay the Service Fees via invoice. SAP will invoice Customer and payment is due 14 days after the invoice date.
(b) If Customer is not registered as an authorized buyer, Customer must use a valid credit card to complete this order. Service Fees will be billed to Customer’s credit card upon Order Confirmation.
2 SERVICE LOCATION AND TAXES
Customer acknowledges that the “Ship-to” address entered by Customer in the SAP Store site is the primary location of receipt of the Service(s) (“Service Location”) and should be in the same country in which Customer is located and has its billing address. It is the obligation of the Customer to consider if withholding tax is applicable. In case of any applicable local taxes, these are to be borne by Customer. Applicable taxes have to be declared and paid to the respective tax authority by Customer. Customer’s failure to provide SAP with its VAT and/or GST number may have sales tax implications. Services Fees do not include Taxes.
3 SCHEDULING OF THE SERVICE DELIVERY
Unless otherwise stated in Exhibit 1, SAP shall contact Customer within 5 business days after Order Confirmation to schedule the start of the Service.
EXHIBIT 1: SCOPE DOCUMENT
Prior to accepting this Agreement, Customer has had the opportunity to review the terms and conditions mentioned above, including without limitation the GTC and Service Descriptions. For purposes of this Order Form, the following provisions of the GTC shall not apply: Change Request Procedures (generally section 4) and Satisfaction with Personnel (generally section 5). SAP recommends Customer prints copies of the applicable GTC, Service Descriptions and Scope Documents for Customer’s own records.
SAP recommends Customer prints copies of the applicable GTC, Service Descriptions and Scope Documents for Customer’s own records.
1. Scope of Services
SAP will provide the Engineered Service SAP Analytics Cloud connectivity setup for HANA database (“the Service”) to assist Customer with the setup of a connection to a single SAP HANA environment.
1.1 Functional Scope
The following forms the functional scope of the Service:
Assist Customer to set up SAP Analytics Cloud connectivity to a single instance of the SAP HANA database (on-premise or cloud edition):
a) Check if the Pre-Requisites are accomplished by the Customer:
• Verify Customer’s HANA version
• Verify SAP Analytics Cloud version
• Verify user rights depending on the purpose
• Verify Reverse Proxy configuration
• Verify SAP HANA Info Access Service (InA)
• Verify SAML 2.0 Identify Provider to be fully configured
(b) Assist Customer to configure the connection to a single SAP HANA environment (On-premise or Cloud edition).
(c) Step by step configuration of the connection for a single environment of SAP HANA
Scope will be confirmed during a validation workshop. No changes to the scope will be permitted for this service. If Customer requires additional services a separate agreement for such services needs to be executed.
1.1.1 Functional and Technical Pre-requisites
The Customer must have the following pre-requisites accomplished, before the start of the Service:
Must be using SAP Business Objects Cloud version 2017.02 or above
Must use a supported SAP HANA version (SAP HANA 1.0 SPS10, revision 102.2, an SAP Cloud Platform (SAPCP) system running on SAP HANA SPS10, revision 1.02.2, or SAP HANA 2.0 SP01 or newer)
Provide required information to setup the connection (user, password, HANA server details)
Has to have installed and configured an HTTP server in the same network as the on-premise HANA system. For example, Apache HTTP server (Reverse Proxy)
Must have set up and activated the SAP HANA Info Access Service (InA), version 4.10.0 or above, on the SAP HANA system
For SSO, SAML 2.0 Identify Provider needs to be fully configured. For example, SAP NetWeaver SSO.
A user account has to be created in the SAP HANA database by the Customer and configured in the specific roles (Ina_User) before the start of this Service. This user account will be used in the connection configuration.
The SAC environment is on the Public Cloud
1.1.2 Functional Scope Details
The following applies to the functional scope.
Only one (1) connection to one HANA environment, in one (1) SAP Analytics Cloud environment will be implemented.
The system language will be English only.
1.2 Integration Scope
No integration points are in scope for this Service.
1.3 Workflows, Reports, Interfaces, Conversions, Enhancements and Forms
No Workflows, Reports, Interfaces, Conversions, Enhancements and Forms have been identified as part of the scope of the Service.
1.4 Software Installation
No Software installation is in scope for this Service.
2. Approach and RACI
SAP will follow the applicable parts of the SAP Activate methodology which has the following phases.
Prepare: The Services are formally initiated and the schedule, project plans and resources are agreed. The SAP Development Environment is created.
Explore: Workshops are conducted to design how the Software will be configured and confirming the scope including identifying and confirming the delta scope based on Customer’s requirements.
Realize: The Customer-specific configuration is performed and confirmed by the Customer.
Deploy: Final checks are made before the cutover to Production Environment and end users are trained. Ongoing support is put in place by the Customer and the Services are closed.
3. Schedule
The current estimated schedule provides provisional durations per phase as follows.
|
Estimated Schedule for Phase
|
Estimated Duration (Weeks)
|
Planned Start Date
|
|
Prepare
|
0,5 days
|
To be planned with the Customer
|
|
Explore
|
0,5 days
|
|
|
Realize
|
1 days
|
|
|
Deploy
|
0,5 days
|
|
4. Organization
4.1 SAP Team
The key SAP roles are as follows:
|
SAP Team
|
Level of Involvement
|
|
Service Responsible
|
Single resource. Part-time. Offsite.
|
|
ITTS Consultant
|
Single resource. Full-time. Offsite.
|
4.2 Customer Team
The Customer team will include the following roles. Customer team is assumed to be available to complete Customer activities.
|
Customer Team
|
Description
|
Level of Involvement
|
|
Service Responsible
|
Management of resources, resolving issues, project plan, project status and decision-making process.
|
Single resource. Full-time. Onsite.
|
|
IT Development and Reporting
|
Undertakes to take care of the technical subjects and configuration.
|
|
4.3 Governance
Not applicable due to the short term of the Service.
5. SAP Deliverables
The following table lists the SAP Deliverables.
|
Deliverable
|
Deliverable Description
|
Completion Criteria
|
|
Connection of SAC to single HANA environment
|
Configuration of the connection to a single HANA environment (Cloud or on-premise)
|
Unit test completed
|
6. General Customer responsibilities
Customer has the following general responsibilities:
Ensure that Customer team members are knowledgeable about the Service being implemented and define their training approach and schedule. Ensure that key users are available for all workshops and activities as needed.
Minimize the change in personnel throughout the duration of the Service.
Manage the Customer’s third party service providers.
Supply SAP with the names and contact information of key Customer and third party resources.
Organizational change management activities, training and knowledge transition activities which include, but are not limited to the following: communication plan, organizational transition plan, business readiness for go live, design and roll-out of end-user training, coordination with remote sites, and project communication to the company.
Provide SAP (and Customer team members) with adequate work space as necessary for the duration of the Services. Necessary identification material (badges, passes, cards, etc.) need to be provided. The meeting rooms should include - if needed – projectors, printers, scanners, copiers, file storage and miscellaneous office supplies. Sufficient temporary desks, or “hot desks”, must be made available to enable each on-site SAP resource to have a desk. This includes necessary access to such buildings and systems during and after normal business hours, on weekends, and on holidays. Limitation of SAP access during these times may reduce SAP’s ability to maintain the proposed schedule. No SAP employees will have an office on the Customer’s premises with keys that provide exclusive use of the office to SAP.
Be fully responsible for technology infrastructure that is on premise or hosted by a third party. This includes but is not limited to SAP infrastructure, network and system administration, security, periodic backup and restore activities as required, and server and storage hardware. These systems shall be available throughout the Service according to the project schedule.
Ensure that a consistent, stable, and fast SAP remote support connection/service connection is available between SAP and the Customer at the required times.
Provide SAP with the necessary authorizations for onsite and remote access to Customer’s systems.
Allow the use of SAP laptops and mobile devices on Customer’s network to SAP’s network via SAP’s Virtual Private Network (VPN) protocols; otherwise, Customer will provide PCs and/or laptops with the Microsoft Office Suite and e-mail capability for the SAP team. Laptops and/or PCs provided by Customer must have the latest virus protection software.
Provide technical advice regarding any third-party systems to which the team will have access.
Customer is responsible for the acts, omissions, and defects of parties that Customer contracts or instructs to perform Customer’s duties (notably other third parties not engaged by SAP) as if they were Customer’s own acts, omissions, and defects. As between SAP and Customer’s other, third-party contractors, such other contractors are therefore parties performing duties on Customer’s behalf.
Performance by Customer of its collaborative duties in this contract is a primary contractual duty and is a necessary precondition for the proper performance of SAP’s duties.
Customer acknowledges and agrees that failure on the part of Customer to meet or fulfil any of the specified Customer responsibilities or requirements in this document might result in a delay in the estimated schedule and/or an increase in fees.
SAP and Customer agree the following responsibility matrix of activities per phase.
Responsible (R): Charged with performing the activities. A mutually agreed project plan may define further details at the work unit level.
Accountable (A): The Customer has overall accountability for its implementation and all the activities identified below. Hence, Accountable (A) does not appear for the activities below.
Consulted (C): Provides input on how to perform the activity and supports the execution of the activity.
Informed (I): Provided with information.
All interfaces will be in English language only.
7. Assumptions
The following assumptions apply:
If SAP and the customer do not agree on a service delivery start date within four (4) weeks after successful order processing, SAP will cancel the order, without any reimbursement of payments made and without any liability to SAP.
SAP may require up to 3 business days to contact the customer after successfully processing the order to mutually agree the start date for Service delivery.
The service delivery should not span more than 1.5 days in total, starting from the agreed starting date.
SAP will assist Customer with the move to the Production environment for up to 1 (one) continuous business day which will not exceed 0,5 (half-day) SAP person days.
The project language is English and all documentation will be prepared in English.
Prior to Service closure, Customer is not permitted to change any customizing settings since this may interfere with the implementation of the Service.
The approach is based on using Engineered Service content. These solution scenarios are delivered using only the accelerators and content that are part of the Engineered Service.
SAP may use certain software and tools (all referred to as Tools herein) for its work, for which the rights are not already regulated through a software license agreement. All title to and rights in Tools, including without limitation copyright and rights of authorship, remain with SAP or SAP SE. These Tools may be copied to Customer’s system and Customer is granted non-exclusive rights to use Tools for the term of and solely for the purposes related to the Service. No other use, including the creation of further copies or use on another system, is permitted. Tools and all permitted copies of Tools must be deleted at the end of the Service. If at SAP’s sole discretion Tools are left on the system for documentation purposes, Customer is not permitted to use Tools for any other remaining purpose except documentation. Such Tools are on an as-is basis with no warranty. SAP will not support or enhance the Tools beyond what is provided during the term of the Service.
All supporting documentation will be developed using industry standard personal computers/laptops using Microsoft Office applications (Word, Excel, MS Project, Visio and PowerPoint) or other mutually agreed documentation tools.
For the avoidance of doubt, Customer will primarily be responsible for correcting non-conforming results, which are related to Customer responsibilities, and SAP will primarily be responsible for correcting Material Defects, which are related to the agreed SAP scope and activities performed by SAP, provided that the other party will support when needed.
|
Activity
|
SAP
|
Customer
|
|
Prepare Phase
|
|
|
|
Prepare SAP’s schedule.
|
R
|
I
|
|
Prepare Customer’s overall project schedule and structure and confirm, in writing, completion of pre-requisites (see section 1.1.1).
|
I
|
R
|
|
Prepare the Sandbox and/or Development Environment and provide SAP with access to the environment.
|
C
|
R
|
|
Explore Phase
|
|
|
|
Demonstrate and validate the Service scope in the validation workshop.
Compare with Customer requirements during the validation workshop. Any delta scope identified will be documented and sent to Customer. No further action will be taken by SAP for the identified delta scope.
|
R
|
C
|
|
Realize Phase
|
|
|
|
Configure and unit test the service.
|
R
|
C
|
|
Confirm in writing, that testing is complete. Work will not start on the Deploy phase until the Customer confirms with an email stating “the connection to the HANA system has been setup and returns data in SAP Analytics Cloud”.
|
C
|
R
|
|
Deploy Phase
|
|
|
|
Assist Customer with the configuration and validation of the Production environment
|
C
|
R
|
|
Go-live.
|
C
|
R
|
8. Exclusions
Any items or Services not defined as in scope for this Service are deemed out of scope, including, but not limited to the following exclusions:
Deliverables not explicitly described in this Scope Document.
Procurement of software licenses (SAP and non-SAP licenses).
Developments that modify the standard SAP Software source code.
9. Definitions
SAP Best Practices: SAP’s predefined business processes, configuration content and documentation for SAP Software. SAP Best Practices may be used as the basis for SAP implementation activities.
Engineered Service: a service delivered by SAP that has a predefined scope, delivery approach and accelerators.
SAP Activate: a standard SAP methodology used for SAP implementation projects.
Workflows: a workflow is a sequence of connected steps triggered by an event to automate a process such as a document approval. Examples include SAP Business Workflows.
Reports: technical objects designed to deliver business figures or reports with no change to application data.
Interfaces: technical objects to transfer information from one system to another, usually referring to objects that are not part of the SAP licensed Software. Examples of technology include SAP Process Orchestration and Intermediate Documents (IDocs).
Conversions: technical objects used to migrate data to SAP systems during the Service. Examples of technology include data migration programs, SAP Data Services and Legacy System Migration Workbench (LSMW).
Enhancements: changes and additions to SAP functionality using development objects specifically provided for Customer changes. Examples include the use of user exits and business add-ins (Exits).
Forms: printed or electronic forms containing formatted information from SAP applications. Examples of technology include SAPscripts, Smart Forms and SAP Interactive Forms by Adobe.
Sandbox Environment: a temporary SAP system environment used to demonstrate processes and example prototypes. Implementation work undertaken in a Sandbox Environment is typically not transported to other environments.
Development Environment: a SAP system environment in which initial configuration and build activities are completed. Implementation work undertaken in a Development Environment would be transported to a Quality Assurance Environment or Production Environment.
Production Environment: a SAP system environment used to execute operational business processes.
User Acceptance Test: test undertaken by end users to acknowledge that the system operates according to the agreed design.
