Enhancement Service for SAP Product Lifecycle Management

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 are the contracting party intending to be legally bound (“Customer”) or an agent of the Customer with the authority to carry out this transaction and conclude the respective contracts with SAP on behalf of the Customer. If you do not have the appropriate authorization to carry out and conclude this transaction, you should not continue with this transaction.

This Agreement (defined below) is a legally binding agreement for SAP Services between Customer and the SAP affiliate or subsidiary company (both defined below; “SAP”) in the country in which Customer is located and in which Customer intends to accept receipt of the Service(s).

This order document 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”.  The Agreement shall be effective as of the date appearing on the Order Confirmation (“Effective Date”) and shall continue until the Services under this Order Form are completed or terminated (“Term”). 

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.

SAP recommends Customer prints copies of the applicable GTC, Service Descriptions and Scope Documents for Customer’s own records.

Service Fees

The Service fees (“Service Fees”) are payable for the specified Service(s) consisting of the component(s) identified in the purchase review displayed on the SAP Store (“Purchase Review”) as well as in the corresponding order confirmation email Customer receives from the SAP Store (“Order Confirmation”)

Payments

(a)   The fees for the Service are as provided in the ordering page(s) of the SAP Store.

(b)   If Customer is a previously authorized buyer of SAP products, SAP will invoice customer and payment is due in accordance with the GTC.

(c)   If Customer is not a previously authorized buyer, Customer must use a valid credit card to complete this order.  If Customer uses a credit card for purchases, fees will be billed to Customer’s credit card upon Customer confirmation of this order.

(d)   Unless otherwise identified for a previoulsy authorized buyer, Customer bill address will be considered the location of Licensee’s receipt of Services provided hereunder.  The calculation of taxes may be determined by this receipt of Service Location.

Data Processing

SAP and Customer agree on the provisions of the “Data Processing Agreement for SAP Cloud Services” as incorporated into the Agreement by reference. 

Scope Document

Scope Document for SAP Product Lifecycle Costing (PLC) Enhancement – Side-Panel Browser

This Scope Document forms part of the Order Form.

Capitalized terms that are not defined in this document (section ‎9) have their meaning defined in the General Terms and Conditions (or alternatively the governing terms and conditions or agreements as set forth in the Order Form).

ContentS

1    Scope of Services

1.1    Functional Scope

1.2    Workflows, Reports, Interfaces, Conversions, Enhancements and Forms

2    Approach and RACI

3    Schedule

4    Organization

4.1    SAP Team

4.2    Customer Team

5    SAP Deliverables

6    General Customer responsibilities

7    Assumptions

8    Exclusions

9    Definitions

1. Scope of Services

SAP will provide an Engineered Service Side-Panel Browser for SAP Product Lifecycle Management (Services) to enable Customer to show web applications in the SAP Product Lifecycle Costing Side-Panel. The Side-Panel Browser is a Tool within the meaning as described in the Assumptions section below.

1. Functional Scope

The following forms the functional scope of the Engineered Service to be provided by SAP.

1. Functional and Technical Pre-requisites

The Customer will have the following SAP Software version fully functional before the Services starts:

SAP Product Lifecycle Costing 4.0 Support Package 01 (or higher)

or

SAP Product Lifecycle Costing 3.0 Support Package 02 (or higher)

2. Functional Scope Details

The following applies to the functional scope.

• The system language will be English only.
• All business data in the system will be in English language only.
  2. Workflows, Reports, Interfaces, Conversions, Enhancements and Forms

No Workflows, Reports, Interfaces, Conversions, Enhancements or Forms will be created or delivered within the scope of this Service. Standard SAP code will be neither modified nor extended.

2. Approach and RACI

SAP will follow the applicable parts of the SAP Activate methodology which has the following phases.

1. Prepare: The Services are formally initiated and the schedule, project plans and resources are agreed. The SAP Development Environment is created.
2. Explore: Workshops are conducted to design how the Software will be configured and confirming the scope.
3. Realize: The Customer-specific configuration is undertaken. The test approach and any knowledge transfer are executed. The Customer testing is completed.
4. 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.

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.

3. Schedule

Within (5) five business days after Order Confirmation the Customer will be contacted by SAP to schedule the start of the Service.

The period during which the Services will be provided will be mutually agreed between the parties.

The estimated duration for the Service is four (4) weeks.

4. Organization
   1. SAP Team

The key SAP roles are as follows:

2. Customer Team

The Customer team will include the following roles. Customer team is assumed to be available to complete Customer activities.

5. SAP Deliverables

The following table lists the SAP Deliverables.

SAP Deliverables shall be deemed accepted when the above completion criteria have been met.

6. General Customer responsibilities

Customer has in particular the following general responsibilities:

• Ensure that Customer team members are knowledgeable about the Engineered 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.
• 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 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.
• If 3rd parties on Customer side are involved 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.
• Ensure Customer compliance with any relevant governmental and regulatory requirements.

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 Agreement might result in a delay of the provision of the service and/or in the estimated schedule.

7. Assumptions

The following assumptions apply: 

• If the Services have not started within two (2) months of the estimated start date as mutually agreed SAP has the right to terminate the Services without liability.
• SAP may require up to two (2) weeks to assemble a team. SAP reserves the right not to start the Services until SAP has assembled a team.
• Services are delivered remotely
• SAP will provide up to two (2) continuous business days of knowledge transfer to project team members to a maximum of one (1) SAP person days.
• SAP will, remotely, provide a maximum of three (3) SAP person days of go live support and post go live support within a period of fourteen (14) continuous business days. Go live support will begin when the technical cutover has been executed by Customer. Cutover to Production is expected to be executed by Customer within six (6) months after knowledge transfer has been completed. Production validation by Customer is considered part of the period of go live support.
• 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 or provide 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. 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 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.

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).
• An analysis of as-is business processes.
• Programs or content to migrate data. Data cleansing of migrated data from Customer systems.
• Content for end user training.
• Upgrade to the SAP solution components, operating systems or database systems.
• Effort for the use of verification and validation testing processes which may be required by regulatory, industry or governmental requirements.
• Developments that modify the standard SAP Software source code.

9. Definitions

1. Engineered Service: a service delivered by SAP that has a predefined scope, delivery approach and accelerators.  
2. SAP Activate: a standard SAP methodology used for SAP implementation projects.
3. 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.
4. Reports: technical objects designed to deliver business figures or reports with no change to application data.
5. 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).
6. 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).
7. 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).
8. Forms: printed or electronic forms containing formatted information from SAP applications.  Examples of technology include SAPscripts, Smart Forms and SAP Interactive Forms by Adobe.
9. 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.
10. 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.
11. Quality Assurance Environment: a SAP system environment used for testing transported content from the Development Environment prior to transporting it to the Production Environment.
12. 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.