Implementing a Project —

First Implementation
Overview

The implementation of your SAP solution includes all steps required for getting the system, the data,
and the people in your company ready for Go Live. The Activity List is derived from the agreed
solution scope and includes all activities the project team has to complete. The activities are
structured by different project phases. Simple status and progress reporting per activity and phase
enable you to easily track the progress of your project as you work through the activity list.

Once you have finished scoping, you can begin to work with the Activity List in the Business
Configuration work center. The Activity List is automatically generated by the system based on
your scoping decisions, and it is divided into separate phases. It includes all mandatory
implementation and project management activities that you need to complete before your solution
can go live for the first time and be used in your production system

You have to complete the activities in each phase of the Activity List - instructional activities
describe how you can complete them and what has to be done. In general you have to complete the
phases in sequence, and within each phase you have to complete the activities in sequence.

Activities

When you open an activity, you can potentially be brought to a number of different places that
support you in completing the associated task. This includes:

 Documentation – instructional activities and most project management activities display

documentation to explain what you need to do to complete the selected activity. These activities
often involve completing tasks outside of the solution itself, for example, creating the project plan in
SAP Go-Live Navigator or preparing for data migration. This style of activity can be found in each
phase of the Activity List.
 A single screen with settings that are associated with one or more options and that can be
configured for your solution.

 A guided activity that consists of multiple screens, each with settings that are associated with one or
more options and that can be configured for your solution.

 A direct link to an application screen associated with a work center that is specific to the selected
activity.

 An activity details screen – this is a screen that displays a list of links. These links can bring you to
documentation, fine-tuning screens, or application screens. It may not always be necessary to open
each link and complete each task. On-screen explanations explain clearly where alternatives exist,
for example, you can either migrate your legacy data using data entry or using a built-in migration
tool.

Milestones

Various milestones are integrated in the activity list. These milestones are project activities that have
to be checked and confirmed, as they provide you with guidance and allow you to track the status of
your implementation.

Prerequisites Exist

Some activities are dependent on the completion of other activities. In some cases, you cannot
proceed with an activity until another activity has been completed. In other cases, it is simply
recommended that you complete an activity before proceeding with another activity. In the Activity
List, you can see which activities are dependent in the Prerequisites Exist column.

Repetition Required

Some activities in the Activity List have to be repeated in other systems because the data in these
activities cannot be copied automatically to another system. For example, if you maintain an activity
in your test system, you must also repeat this activity in your production system. In the Activity List,
you can see which activities have to be repeated in the Repetition Required column
 Prerequisites

You have finished preparing your first implementation project.

Process Flow

1. Prepare Phase

The Prepare phase contains the entire preliminary activities project managers need to carry out to
get your company ready to use the solution productively. The activities in this phase are mainly
related to project management and include activities like reviewing the project plan, confirming the
milestone that the design has been accepted and scoping has been completed, preparing for data
migration, maintaining your administrators, and transferring knowledge to administrators. You can
also create your own activities manually and add them to the Activity List. Confirming the milestone
that the design has been accepted deploys the relevant business content based on the scoping
decisions, opens the other phases in the Activity List, and changes the status of the
implementation project to Started.

In this phase, the process is as follows:

a. You prepare the project.

The project manager sets up a project team for the targeted solution and ensures that adequate on-
site facilities are available to them.

The foundation of the SAP Solution Go Live project is established during the Prepare
Project activity. By using complementary tools and accelerators that are related to project
management, you can save significant time in setting up the project.

At this stage in the project, the project manager has to set up the project organization and define the
project schedule. To do this, you can use the Go-Live Navigator to accommodate the specific
activities, owners, and project timeline. In addition, you can review and adapt other accelerators,
such as a risk log, change management guide, and communication plan. At the end of the project
preparation phase, project managers schedule and conduct a project kick-off workshop with key
stakeholders and the entire project team.
b. You verify scoping and confirm the milestone that the design has been accepted.

You verify that the scoping that you completed before starting the project accurately reflects the full
scope of the project. Any business decisions that are made drive the fine-tuning of your solution.
After verifying scoping, you confirm the milestone that the design is accepted, indicating that you
have finished defining your scope and preparing your project. Confirmation of the milestone triggers
the deployment of the relevant business content to your test system and opens up the next phases
of the Activity List.

Tip
Before you confirm this milestone, we recommend that you complete the Verify Scoping activity
and set it to Closed.

You can confirm this milestone only once and you cannot reverse the confirmation. However, even
after confirming this milestone, you can still edit the scope of your project. Confirmation of this
milestone:

 Assumes a signed contract exists that provides the initial user (that is, the project manager) with the
deployment authorization.

 Changes the status of the project to Started.

 Automatically sets the status of the milestone to Closed.

 Grants additional authorizations to the initial user, allowing him/her to define the administrators for
the project team.

c. You define the administrators for the project team.

In addition to defining the administrators, the initial user (usually the project manager) also maintains
the administrators as service agents in the system and provides them with the authorizations for the
work centers and work center views that they need to use to perform their project tasks. The initial
user also must create an administrator for himself or herself. For compliance reasons, you have to
lock the initial user after defining and maintaining the administrators. You can continue working in
the project by using your administrator details.

Caution
 The service agent administrators should only be used for implementing the project. If the service
agents are also employees in your company, you need to create additional users for them during
migration and lock the service agent administrators after you go live.

Ensure that at least one employee has unrestricted write access to the Business Users view in
the Application and User Management work center.

To define and maintain the administrators, follow the steps in the activity documentation, which
appears when you click on the Define Administrators for Project Team activity in the Activity
List.

Caution
Before you start this activity, you have to confirm the milestone Design Accepted.

d. You prepare your organizational structure setup.

The preparation of the organizational structure setup is also part of the Prepare phase.
Organizational Management (OM) is the central source of a company’s organizational structure
within the SAP solution. The OM contains the organizational structure for one or more companies
and comprises organizational units or departments.

Each organizational structure contains information on the legal, financial, reporting line (people
management), and functional responsibilities in the company and provides a unified, graphical
representation in the style of an organizational chart. The SAP solution references the organizational
structure in all business processes, such as determining responsible approvers, available cost
centers, and invoicing addresses. Therefore, establishing the organizational structure is mandatory
and a prerequisite for all subsequent implementation activities related to fine-tuning, master data
migration, and user management. All objects of the structure are time-dependent, meaning each
organizational unit exists in the structure for a specified duration only.

To prepare for the actual maintenance of your organizational setup in the Fine-Tune phase, you
have to gather information about your company’s organizational structure, including:

 Companies (legal entities)

 Business residences
 Departments located at business residences

 Departmental responsibilities for the scoped functionality

 Financial reporting structure, such as segment, cost centers, and profit centers

 Reporting lines including departmental managers

e. You prepare data migration.

During the Prepare phase, the project manager also starts to prepare for the Integrate and
Extend phase by setting up the migration project team and giving authorizations for data migration
to each user. The project manager also sets up the project schedule for data migration.

Data migration allows you to prepare and move all data from existing legacy system(s) to your SAP
solution. For example, this includes migration objects like products, services, and business partners,
as well as transaction data specific to individual sales orders or financial postings. Some of these
objects have dependencies and need to be imported in a defined sequence.

The SAP solution provides a tool-supported migration approach that is based on migration
templates. You need to extract the required data from your legacy system(s) into the migration
templates provided by SAP.

To prepare for the actual data extraction in the Fine-Tune phase, you can download migration
templates and a migration schedule template directly from the Activity List. You can use the
migration templates to understand which information can be migrated with the templates and which
data structure is mandatory for data migration.

The project schedule contains information on when to perform which migration activity in the overall
migration process. To achieve a realistic timeframe for the overall migration process, you can adjust
the predefined schedule according to your situation, resources, and data quality.

In addition, you can also use a manual data entry option to enter test data or, if required, migration
data.

f. You transfer knowledge to administrators.

 Administrators learn about the solution by using the material in the solution. The content covers all of
the features and functions the project team decided were relevant. In addition to learning,
administrators plan how to train or transfer knowledge to the end users within the company.

2. Fine-Tune Phase

This phase organizes all mandatory configuration activities that you need to complete in a logical
sequence. It allows you to tailor the solution to your specific needs before going live by checking
predefined settings and entering additional settings for your selected scope. You can also add
optional configuration activities to the Activity List. In this phase, you need to complete your
company's organizational management structure and confirm the milestone that the solution is
accepted, indicating the completion of the Fine-Tune phase.

In this phase, the process is as follows:

a. You prepare fine-tuning.

While preparing for fine-tuning, all administrators review the learning module related to
the Business Configuration work center, you assign all fine-tuning activities to the responsible
administrators, and you include any optional activities that you also require in the Activity List.

b. You perform the organizational structure setup for your company.

You maintain the organizational structure of your company in the system in alignment with your
preparation during the Prepare phase. You can create the organizational structure by dragging and
dropping organizational units from the Org Unit pane into the Planning Area. Afterwards, to
document the meaning of each organizational unit in your company, for each organizational unit you
have to maintain:

 Operational properties

These properties describe which function an organizational unit has in your company’s business
processes from a functional perspective. For example, an organizational unit represents the
functional unit Customer Service.

 Structural properties
 These properties describe what the organizational unit represents in the structure of your company.
For example, the organizational unit Procurement represents also a cost center and a reporting
unit.

Along with the organizational structure setup, you check and adapt the departmental responsibilities.
For example, Purchasing Department A is responsible for direct materials purchasing,
and Purchasing Department B processes only purchase requests related to indirect materials.

By completing the Perform Organizational Structure Setup activity, you confirm that you have
finished setting up your organizational structure. This is important for determining reporting lines, as
well as the legal and financial aspects within your company. You can adjust your organizational
structure as often as necessary until you complete the Confirm Go Liveactivity in the Go
Live phase, as it simply helps you to track the progress of your project.

c. You perform fine-tuning for each business area, and you confirm the milestone that the solution is
accepted, indicating that fine-tuning is completed.

Fine-tuning is the most important step in the Fine-Tune phase and it spans all mandatory
configuration activities that have to be completed. Before going live, fine-tuning allows you to tailor
the solution to the specific needs of your company by checking and adjusting the predefined settings
of the elements selected during scoping — this is known as performing mandatory checks. Fine-
tuning also allows you to enter your own settings in cases where no predefined settings exist — this
is known as performing mandatory maintenance. Typical activities include setting up payment
strategies in Sales and maintaining charts of accounts in Financial Management.

By default, this phase only contains mandatory activities that must be completed before the solution
can go live. However, you can add activities to your project by selecting a different option in
the Show filter, selecting any activity not yet included in your project, and clicking Add to Project.

By confirming the milestone Solution Accepted, you confirm that your fine-tuning settings have
been tested properly and meet your business requirements. During your implementation project, you
can adjust your fine-tuning settings as often as necessary, so you can cancel and reconfirm this
milestone until you confirm the Confirm Go Live activity in the Go Livephase, as it simply helps you
to track the progress of your project.

d. You finalize forms, reports, user interfaces, and third-party integration requirements.
 If this is within the scope of your project, you review the requirements that have been documented in
the Service Assessment Documents (SAD), complete the necessary specifications, provide SAP
with the updated SAD together with any required clarification, and confirm the delivery date of the
content with SAP.

e. You perform data extraction.

After completing all other mandatory activities in the Fine-Tune phase, you can trigger data
extraction. As a first step, you have to complete development and test of the data extraction
programs.

Depending on whether you use the migration templates for tool-supported migration, you can
perform data extraction as follows

 Tool-Supported Migration Based on Migration Templates

The required data from your legacy system(s) is extracted in the migration templates provided by
SAP. (See the substep You prepare data migration in the step for the Prepare phase above.)

 Tool-Supported Migration Without Migration Templates

You provide the SAP Service Center with a full extract of the required data from your legacy
system(s) together with source data field descriptions. The descriptions allow the SAP Service
Center to implement customized mapping rules that fit your specific legacy data structures.

3. Integrate and Extend Phase

This phase allows you to transfer your configured solution to your company to start using it
productively. You do this by integrating with third party applications that already operate in your
company, and moving your basic, master, and transaction data from your legacy system(s) to your
new solution. You also decide which form, report, and user interface extensions you require to meet
your company's specific needs.

In this phase, the process is as follows:

a. You migrate master data and maintain basic data.

 You migrate your data using the inherent migration tool (data migration self-service), or you decide
on migration object level whether you want to enter the data manually instead.

Tip
We recommend you use the inherent migration tool regardless of the size of the data volume that
needs to be migrated.

Before migrating all master data, you have to create all mandatory basic data in the new system.
This data is required by different master data objects and comprises, for example, the bank
directory, transport lanes, or tax authorities.

Caution
After migrating the data, you cannot delete it from your SAP solution. Therefore you can perform any
migration tests on a separate test system.

For more information, see Request an Additional System.

b. You adapt forms, reports, user interfaces, and third-party connectivity.

You also have to decide on the extensions that you require for your company’s specific needs.
These extensions include form adaptation or creation, report modification or development, field
extension and user interface adjustments, as well as adaptation of the built-in learning environment.
During this activity, after mutually agreeing on the SAD:

 SAP performs the development or adaptation work required.

 Upon completion of this, the project manager is notified that the new content is ready to be deployed
into the system.

 The project manager confirms this notification and the new content is deployed into the system.

 The administrators perform acceptance tests.

 Depending on the acceptance test results, the new content is accepted or test incidents are provided
to SAP. Any test incidents are reviewed and resolved, the updated content is deployed again, and
you perform a final acceptance test.

4. Test Phase
 This phase contains activities that allow you to define test scenarios and guides, verify that your core
business processes are running as desired, and transfer knowledge to end users before your
solution goes live. You also need to confirm the milestone that go-live readiness is accepted,
indicating that testing is completed, which changes the status of the implementation project
to Tested.

In this phase, the process is as follows:

a. You prepare integration tests.

Before performing any integration tests, you create the required documents, guidelines, and test
plan. This includes scenario documents containing all processes, roles, and data required to test an
end-to-end business scenario according to your business requirements, test documents containing
guidelines for specific business processes, and a finalized test plan incorporating project-specific
information, assigned testers, and a plan for test execution.

b. You transfer knowledge to end users.

You have to ensure that all end users are properly trained before the solution goes live. In this
activity, you provide clear instructions on accessing embedded learning, ensure learning materials
are available for the core business processes, and upload any company-specific learning materials
to the system.

Tip
You can also allow end users to execute test guides during integration testing under the supervision
of administrators. This enables end users to get hands-on experience of the system prior to Go Live.

c. You perform integration tests.

After the test plan is finalized and the test cases have been distributed, you perform the integration
test according to the test schedule, and based on the scenario documents and guidelines.

If the test results do not match the expected results, you document any deviations as incidents.
Once all incidents have been reviewed and resolved or acceptable workarounds identified, and all
test steps have been completed, you sign off the test document and change the status of this activity
to Closed.
d. You finalize the integration tests and confirm the milestone that go-live readiness is accepted,
indicating that testing is completed.

To finalize the integration tests, you verify that all test guides have been successfully completed, the
test plan has been updated, and changes made in the test system have been merged into the
production system.

By confirming the milestone Go-Live Readiness Accepted, you confirm that your integration test
has been completed successfully and you indicate you are ready to go live with your solution. During
your project, you can continue testing, so you can also cancel and reconfirm this milestone as
necessary, as it simply helps you to track the progress of your project. On confirming the milestone,
the project status is set to Tested.

Tip
Before confirming this milestone, we recommend that you confirm the milestone Solution
Accepted and set it to Closed in the Fine-Tune phase.

5. Go Live Phase

This phase includes the final activities that you must complete to enable your solution to be used
productively in your company. Typical activities include preparing and performing cutover, setting up
internal support teams, and confirming that you are ready to go live. At the end of this phase, all
mandatory and outstanding configuration issues are resolved, legacy data is migrated to the
production system, knowledge transfer is complete, and the project is signed off. The final activity
confirms the implementation project is officially closed. The project status is set to Closed and the
implementation project is set to read-only.

In this phase, the process is as follows:

a. You prepare cutover.

The Go Live phase starts with the preparation for the execution of the cutover activity. This includes
steps related to the creation of the cutover plan and cutover schedule, while ensuring system, data,
and people readiness.

b. You request Go Live.

 By requesting Go Live and closing this activity, you trigger the Go Live Health Check service. This is
a prerequisite for using the solution productively. The SAP support team verifies that you are ready
to go live in terms of organization, business solution, technical infrastructure, and supportability.

c. You perform cutover and Go Live.

After setting up the internal support team and their responsibilities, you perform the cutover following
all tasks outlined in the cutover schedule. Usually the cutover starts with the performance of the final
operational transactions in your legacy system(s), the extraction of your latest master and
transaction data, and the migration to the production system, and ends with the release of the
production system to all administrators.

d. You complete the activity for Go Live.

In the activity for the Go Live confirmation, the activity guides you through setting your SAP solution
live. During this activity, you check and verify that all activities in all five phases have the
status Closed. You also verify that all mandatory activities in the Fine-Tune phase are fine-tuned
and deployed.

After completing this activity, your solution is live and ready for use. Completing this activity also
informs SAP that you want to use your solution productively. You can still view all previous phases
and activities, but you cannot make changes to them. You can complete this activity only once, and
it cannot be revoked for the project.

The project status is set to Completed and the phases Prepare, Fine-Tune, Integrate and Extend,
and Test are set to read-only in the Activity List. At the end of the Go Live phase, you have
resolved all mandatory and outstanding configuration issues, migrated all legacy data, and
completed knowledge transfer.

NoteAfter going live with your first implementation project, there are two ways to change your
solution. You can make small changes to a selection of configuration elements, or, for more complex
changes, you can create change projects. For more information, see Make Changes to Your SAP
Solution and Prepare a Change Project.

e. You complete the activity to close the project.

 By completing this activity, you confirm that your project is officially closed. The status of the project
is changed to Closed, and you cannot make any further changes to the project. You can complete
this activity only once, and it cannot be revoked for the project.

Caution
Before you complete this activity, you have to complete the activity Confirm Go Live and set it
to Closed.

After confirming this milestone, the Go Live phase is set to read only, and the entire project remains
in read only mode in the Activity List.

Tip
Before closing your project, you should consider executing the following activities:

 Issue internal and external go live announcements

 Inform your support team about open issues, the process for handling incidents, and the main
contacts for important topics

 Receive official acceptance of the solution

Implementing a Project —
Change Projects
Overview

The implementation of your SAP solution includes all steps required for getting the system, the data,
and the people in your company ready for Go Live. The Activity List is derived from the agreed
solution scope and includes all activities the project team has to complete. The activities are
structured by different project phases. Simple status and progress reporting per activity and phase
enable you to easily track the progress of your project as you work through the activity list.

Change projects allow you to prepare and implement a collection of detailed changes to your
solution by using the Activity List. Change projects are mostly business-triggered with a project
 approach. The changes are made in a separate environment, allowing you to simulate the changes
and activate them only when you are sure your changes do not contradict decisions made in the
production system. When using a change project, a copy of your production system profile is made
and the system generates a delta Activity Listbased on your changes in scoping.

You have to complete the activities in the Activity List - instructional activities, if included in your
change project, describe how you can complete them and what has to be done. In general you have
to complete the activities in sequence.

Activities

When you open an activity, you can potentially be brought to a number of different places that
support you in completing the associated task. This includes:

 Documentation – instructional activities and most project management activities display

documentation to explain what you need to do to complete the selected activity. These activities
often involve completing tasks outside of the solution itself, for example, creating the project plan in
SAP Go-Live Navigator or preparing for data migration. This style of activity can be found in each
phase of the Activity List.

 A single screen with settings that are associated with one or more options and that can be
configured for your solution.

 A guided activity that consists of multiple screens, each with settings that are associated with one or
more options and that can be configured for your solution.

 A direct link to an application screen associated with a work center that is specific to the selected
activity.

 An activity details screen – this is a screen that displays a list of links. These links can bring you to
documentation, fine-tuning screens, or application screens. It may not always be necessary to open
each link and complete each task. On-screen explanations explain clearly where alternatives exist,
for example, you can either migrate your legacy data using data entry or using a built-in migration
tool.
 Milestones

You can decide to add milestones to the activity list for your change project. These provide you with
guidance and allow you to track the status of your implementation, but they are not mandatory for
your change project. However, if you decide to include the milestones to your change project,
you have to close them.

Prerequisites Exist

Some activities are dependent on the completion of other activities. In some cases, you cannot
proceed with an activity until another activity has been completed. In other cases, it is simply
recommended that you complete an activity before proceeding with another activity. In the Activity
List, you can see which activities are dependent in the Prerequisites Exist column.

Repetition Required

Some activities in the Activity List have to be repeated in other systems because the data in these
activities cannot be copied automatically to another system. For example, if you maintain an activity
in your test system, you must also repeat this activity in your production systems. In the Activity
List, you can see which activities have to be repeated in the Repetition Required column

Prerequisites

You have finished preparing a change project.

Process Flow
NoteIn a change project the activity list opens as a flat list. All the activities are displayed in one list
and the Phase column indicates which phase the activity belongs to. If you prefer, you can change
the way the activities are displayed. If you click Show Phased List, the activities are displayed per
phase as in the first implementation project. You can swap between the two displays at any stage
while working in the activity list.

1. Activities Grouped in the Prepare Phase

The process is as follows:

 You confirm scoping changes in each affected business areas.

NoteIf all scoping changes also have manual activities, the Confirm Changes in the <Name of
Business Area> activities do not appear in the Activity List.

The system generates Confirm Changes in the <Name of Business Area> activities for each
business area in which scoping has changed and for which no manual activities exist, meaning there
are no activities related to the actual change in the Activity List. The purpose of confirming these
changes is to ensure you are aware of what has been changed in scoping. You check what has
changed in scoping and then confirm and close these activities.

Tip
Before proceeding you can simulate your changes to check whether there are any problems before
you actually merge your changes back to your production system. For more information,
see Simulate Merging a Change Project with Production.

2. Activities Grouped in the Fine-Tune Phase

In change projects this is very similar to your first implementation. However, it contains only those
activities related to your scoping changes. As with your first implementation, the Activity
List contains mandatory activities that you need to complete in a logical sequence. It allows you to
tailor your changes to your specific needs before going live by checking predefined settings and
entering additional settings for your selected scope. You can also add optional configuration
activities to the Activity List.

The process is as follows.

a. You perform the organizational structure setup for your company.

NoteThe activities to perform the organizational structure setup are only included in the Activity
List if they were selected when scoping your change project.

You check and adapt the organizational structure of your company in the system. You can adapt the
organizational structure by dragging and dropping organizational units from the Org Unit pane into
the Planning Area. Afterwards, you document the meaning of each new or changed organizational
unit in your company by maintaining the operational and structural properties. Along with adapting
the organizational structure setup, you check and adapt the departmental responsibilities.
b. You perform fine-tuning for each business area.

You check and adjust the predefined settings of the elements selected during scoping of your
change project, or you enter or adjust your own settings in cases where no predefined settings exist.

By default, this phase only contains mandatory activities that must be completed before your
changes can go live. However, you can add activities to your project by selecting a different option in
the Show filter, selecting any activity not yet included in your project, and clicking Add to Project.

c. You perform data extraction.

If required in your change project, after completing all other mandatory activities grouped in
the Fine-Tune phase, you can trigger data extraction. This is only necessary if you want to extract
data from additional legacy system(s) or test extracted data. As in your first implementation,
depending on whether you use the migration templates for tool-supported migration, you can
perform data extraction as follows:

 Tool- Supported Migration based on Migration Templates

The required data from your legacy system(s) is extracted in the migration templates provided by
SAP.

 Tool- Supported Migration Without Migration Templates

You provide the SAP Service Center with a full extract of the required data from your legacy
system(s) together with source data field descriptions. The descriptions allow the SAP Service
Center to implement customized mapping rules that fit your specific legacy data structures.

3. Activities Grouped in the Integrate and Extend Phase

As in your first implementation, these activities allow you to connect the configured SAP solution with
your company by integrating the solution with any third-party applications that you already operate,
and moving your master data from your legacy system(s) to the SAP solution if you did not do this
during your first implementation.

In change projects, the process is very similar to your first implementation:

a. You migrate master data and maintain basic data.

 You migrate your data using the inherent migration tool (data migration self-service), or you decide
on migration object level whether you want to enter the data manually instead.

Tip
We recommend you use the inherent migration tool regardless of the size of the data volume that
needs to be migrated.

Before migrating all master data, you have to create all mandatory basic data in the new system.
This data is required by different master data objects and comprises, for example, the bank
directory, transport lanes, or tax authorities.

Caution
After migrating the data, you cannot delete it from the SAP solution. Therefore you can perform any
migration tests on a separate test system.

For more information on how to request the additional system, see Request an Additional System.

b. You activate your solution capabilities for the complete solution.

As part of your change project, you have changed the scope of your solution. These changes are
now merged into your production system and have to be activated.

Caution
Before completing this activity, you have to complete the activity Merge Changes with Production
System and set it to Closed.

By activating your changes, the system adapts and expands your business processes to include
your changes. After activation, all process-relevant transaction data is distributed automatically
throughout your production system.

4. Activities Grouped in the Test Phase

These activities that allow you to verify that all your core business processes are running as desired
and expected before merging your changes with the production system.

In this phase, the process is as follows:

Optional: You define your own test activities and perform tests.
 Before performing any integration tests, you create the required documents, guidelines, and test
plan. This includes scenario documents containing all processes, roles, and data required to test an
end-to-end business scenario according to your changed business requirements, test documents
containing guidelines for specific business processes, and a finalized test plan incorporating project-
specific information, assigned testers, and a plan for test execution.

After the test plan is finalized and the test cases have been distributed, you perform the integration
test according to the test schedule, and based on the scenario documents and guidelines. If the test
results do not match the expected results, you document any deviations as incidents. Once all
incidents have been reviewed and resolved or acceptable workarounds identified, and all test steps
have been completed, you sign off the test document and change the status of this activity
to Closed.

5. Activities Grouped in the Go Live Phase

This phase includes the final activities that must be completed to enable you to use the changes in
your production system.

In this phase, the process is as follows:

a. You simulate merge of your changes with the production system.

By simulating the merge of your changes with the production system, you can check whether there
are any problems with your changes, and if so, resolve them before you transfer the changes to your
production system. You can use the available reports to view your changes.

For more information, see Simulate Merging a Change Project with Production.

b. You update your change project from your production system, if necessary.

If you are using a test system, by updating your change project from your production system, you
can add small changes made in your production system to your test system.

For more information, see Update a Change Project from Production.

c. You merge your changes with the production system.

 If your tests and your simulated merge were successful, you merge your changes with your
production system. As this can be critical, you have to confirm that you want to start the merge
before the changes are transferred to the production system.

If any conflict arises between your test and production systems due to contradictory changes, the
system warns you of these, and you have to decide whether you want to keep the project settings or
cancel the merge process.

d. You complete the activity to close the project.

By completing this activity, you confirm that your project is officially closed. The status of the project
is changed to Closed, and you cannot make any further changes to the project. You can complete
this milestone only once, and it cannot be revoked for the project.

After completing this activity, the entire project remains in read only mode in the Activity List.

Tip
Before closing your project, consider issuing internal and external change announcements.

Request an Additional
System
Overview

Although you are provided with a test or production system for your SAP solution, changes in your
requirements and scope can lead to the need for an additional system. For example, you may
expand the solution to include another country and want to test the respective major change in your
solution scope with minimal impact on your daily business.

Caution
As of August 2013, there is a new procedure for requesting systems.

For existing customers, you can retain the test systems that you are already using, these test
systems will also be upgraded. However if you want to request for a new system, you will have to
 delete all your existing test systems. For new customers, you are provided a test system first and
can request a productive system on the basis of the test system. You will have only one test system,
and if you want a new test system, you have to delete you existing test system.

For more information on system packages and additional services, please contact your SAP sales
representative.

Procedure

1. On the Systems view of the Service Control Center work center, select the project for which you
want to request a system.

Click Request Creation.

NoteIn the Business Configuration work center, Implementation Projects view,

clicking Request System, will also open the Create New System pop-up.

2. In the Create New System pop-up, you can review the following systems.

Before Go Live:

o Test System

This is an exact copy of your production system and can be used for testing or training purposes

Caution
This option is available for your first implementation project that does not have a status
of Live or Closed.

o Productive System

This is an empty system containing only specific configuration data copied from your production
system.

Caution
This system is only available for your first implementation project that does not have a status
of Live or Closed.

After Go Live:
o Test System

This is an exact copy of your production system and can be used for testing or training purposes

Caution
This option is available for change projects that have the status of Started.

3. In order for a copy of your production system to be created, a downtime of your system is necessary.
Select your preferred downtime date.

Tip
Inform your users of the downtime, as changes are not possible in the system during this time.

4. Click OK.

5. You can request a copy of a solution profile from one system to another by clicking Copy Solution
Profile and entering the source and target systems.

For more information, see .

6. If you want to terminate an existing system, select the system and click Request Termination.

Result

Your system request is complete. You can see the status of your request in the System
Status column in the table on the Implementation Projects view.

If you have requested several systems, you can see the status for each when you click on the
system status link. The Additional Systems screen gives you an overview of the status, the
downtime date, and the type of system you requested.

In the title bar you can see the nature of the system you are working in. For more information,
see Watermark.
 Configuration: Understand
the Overall Migration
Process
To find this activity, go to the Business Configuration work center and choose the Implementation
Projects view. Select your implementation project and click Open Activity List. Select
the Prepare phase, then select the Prepare for Data Migration activity from the activity list.

You need to understand the migration-related steps in the activity list and you must be able to plan
the migration project in detail. This is a brief overview:

Tasks

1. Prepare Phase

The Prepare for Data Migration activity (including Prepare for Data Migration in a First
Implementation and Prepare for Data Migration in a Change Project) contains the following initial
tasks:

o Set up user accounts for migration administrators and assign the Business Configuration work
center including the Data Migration view to each migration administrator.

o Create a project schedule for data migration, using the Data Migration Scope and Planning
Template.

o Download Migration Templates. All legacy data you want to migrate with tool-support must be
filled in the migration templates.

2. Fine-Tune Phase

Extract your legacy data from your legacy system and fill it into the migration templates. For more
information, see the Perform Data Extraction activity.
3. Integrate and Extend Phase

This phase contains the major part of the migration activities. Each migration activity serves as a
starting point for tool-supported migration. In the migration tool you perform the following steps:

a. Upload your filled migration template. The system checks the formal consistency of the
source file.

b. Validate the source file. This step enables you to verify whether the migration template was
filled correctly.

c. Convert source values to solution values. During this step, the system automatically
proposes new target values, based on the business configuration of your solution.

d. Simulate the data import. This step allows you to correct any issues before data is actually
written to the solution.

e. Import your legacy data into the solution.

Check the imported data for quality and integrity (acceptance test, integration test). For more
information, see the Validate Data Quality and Integrity activity.

4. Migration Phases and System Environments

During the implementation project, you can perform the described steps in two different
environments:

o Test System

The first system that you are provided with is your test system.

In the test system you can:

a. Start fine-tuning your business processes and execute the first business process tests.

b. Perform early migration tests. The goal of the early migration tests is that you familiarize yourself
with the migration templates and the overall migration process. For example, you can migrate small
sample files and use the results to improve data extraction from your legacy system.
c. Test the migration process with a complete set of data. The goal of the migration tests in the test
system is to elaborate the right settings for successful migration. After you complete migration in the
test system, you can test your business processes using the migrated data.

For more information, see the Validate Data Quality and Integrity activity.

After you completed your migration tests, you can download the value conversion from the migration
tool for reuse in the production system.

For more information, see the Perform Migration in Test System activity.

o Final Migration in Production System

You can upload the value conversion (you downloaded from your migration test system) to import
your complete set of data into your production system. Follow your cutover plan to import the data
into your SAP solution. Focus on the data import sequence including manual tasks.

For more information, see the Perform Migration in Production System activity.

You can also request a restore point before you start your migration. This will allow you to restore
your data to the status before the data migration.

For more information, see Restore Point.

View the Scope of the Current

Solution
Overview

After the solution has gone live for the first time, administrators can view the selected countries,
types of business, and scoping elements that determine the scope and capabilities of the current
solution.

Prerequisites
 The Confirm Go Live activity has been completed for the First Implementation project.

Procedure

1. On the Overview view of the Business Configuration work center, click View Current Scope.

The View Project Scope guided activity is displayed. The guided activity allows you to view but not
change the scope of your current solution. For information about changing the scope of your
solution, see Prepare a Change Project.

NoteThe View Current Scope button is available only after the solution has gone live for the first
time.

2. On the Country and Type of Business step, review the countries and types of business for your
solution and then click Next.

3. On the Implementation Focus step, learn about the implementation focus, and then click Next.

4. On the Scoping step, review the capabilities that are included and not included in the current
solution and then click Next.

The solution capabilities are structured as a hierarchy of scoping elements: Business areas contain
business packages, and business packages contain business topics. If an element is included in the
current solution, the checkbox in the Select column is selected.

o For each business area, you can review the information

on Overview, Relevance, Benefits, Dependency, and Your Notes.

o For each business package and topic, you can review the information
on Overview, Relevance, Dependency, and Your Notes.

NoteThe information on Dependency changes based on the state of the scoping element. If it is
possible to change the selection of the element, the tab lists a simulation of the system selections
that would result. If it is not possible to change the selection of the element, the tab lists the
elements that caused its current state. If the element is in conflict with other selections, the tab lists
them.

5. On the Questions step, review the answers to the scoping questions for the current solution and
then click Next.
 You will find scoping questions at the business topic level.

NoteBy default, the Show list is set to Decision-Relevant Elements; only scoping questions that
you were allowed to answer during scoping are displayed. To filter the scoping questions differently,
select another option from the Show list.

o When you select a business topic, the related group of scoping questions are displayed to the right.

o To learn more about a question, click Details and review the information on Overview, Relevance,
and Dependency.

NoteThe information on Dependency changes based on the state of the scoping element. If it is
possible to change the selection of the element, the tab lists a simulation of the system selections
that would result. If it is not possible to change the selection of the element, the tab lists the
elements that caused its current state. If the element is in conflict with other selections, the tab lists
them.

6. On the Review step, you can click the links under Scoping Results to view the results of your
scoping decisions.

7. When you are finished reviewing the scope of your current solution, click Close.

Previous

Make Changes to Your SAP

Solution
Overview

After the solution has gone live for the first time, administrators can search for specific configuration
elements to change or add to the scope. If the configuration elements are too complex or critical to
be changed immediately, administrators can add them to a new change project and implement them
through a dedicated activity list.

The live solution is not affected by the changes until they are merged with the production system.

Prerequisites
 The Confirm Go Live activity has been completed for the First Implementation project.

Procedure

1. On the Overview view of the Business Configuration work center, search for business
configuration elements to change or add to the scope.

a. In the Show list, select a type of configuration element.

b. To narrow your search further, enter a specific keyword in the Find field.

c. Click Go.

The configuration elements that match your search criteria are listed in the Business Configuration
Search table. The Status column shows whether an element is In Scope or Not In Scope for the
live solution.

The Change column indicates whether the configuration element can be changed immediately
(Immediate Change Possible) or whether it needs to be added as part of a change project (Add to
Shortlist).

2. Select the configuration element that you want to change or add to your scope.

a. If an immediate change is possible, you can click Change Immediately.

i. Edit the associated configuration settings.

ii. To save and immediately apply your changes to the live solution, click Save and Close.

To close the activity without applying your changes, click Close.

b. If configuration elements cannot be changed immediately or you want to make a larger number of
small changes and prefer to create a change project, you can select the elements you want to add to
your scope and add them to a shortlist.

NoteParent elements, which are not in scope and which belong to elements you add to the
shortlist, are automatically added to the shortlist.

i. When you have added all the elements you require to the shortlist, click Add to Change Project.
 The New Change Project guided activity is displayed.

NoteThe system automatically brings you to the next logical step in the process based on your
shortlist, thus offering the quickest and shortest way to implement your changes. However, you can
always go back in this process by clicking Previous.Tip
At any step of the guided activity, you can click Project Details to view either
a Basic or Complete overview of your change project.

ii. On the Adjust Scoping step, edit the scoping elements in your shortlist.

The scoping elements are structured as a hierarchy: Business areas contain business packages,
and business packages contain business topics.

NoteThe hierarchy has built-in rules to ensure that all selections you make are logical and
consistent, from a business and technical point of view. Thus, when you make a selection, the
system makes the necessary additional selections automatically. Also, when you make a selection
that goes against the rules, a warning icon will display in the Conflict column next to each affected
scoping element. For guidance on how to resolve the issue, you can select an element and
review Dependency. To quickly identify all elements with conflicts, you can select Elements with
Conflicts from the Show list.

1. In the Show list, Elements in Shortlist is the default selection.

The business areas containing the scoping elements in your shortlist are displayed. The business
packages and topics in your shortlist are highlighted green.

2. Within the listed business area, review and edit the business packages and topics in your shortlist.

 To select or deselect a business package or topic, select the corresponding checkbox in

the Selectcolumn. You must select a package before you can select any of its topics.

 For each business package and topic, review the information on Overview, Relevance,
and Dependency.

NoteThe information on Dependency changes based on the state of the scoping element. If it is
possible to change the selection of the element, the tab lists a simulation of the system selections
that would result. If it is not possible to change the selection of the element, the tab lists the
elements that caused its current state. If the element is in conflict with other selections, the tab lists
them so that you can decide which selections to reverse.

 To add notes or additional requirements for a business package or topic, use Your Notes.
 3. Review the changes you made in this step of the guided activity as well as the changes made
automatically by the system. The history of changes is cleared once you proceed to the next step.

 Click Display Scope Changes.

The recent changes are listed in descending order.

 To undo the last change, click Undo Last Scope Change.

 To redo the last change, click Redo Last Scope Change.

4. Click Next to continue.

iii. On the Review Questions step, answer the scoping questions in your shortlist.

You will find scoping questions at the business topic level. Some answers are mandatory for your
scope and thus cannot be changed.

1. In the Show list, Elements in Shortlist is the default selection.

The business areas containing the scoping elements in your shortlist are displayed.

NoteIf you added a business package to your shortlist, you need to select All Elements in
the Show list to display the relevant topics.

2. Review the questions and, if necessary, change the preselected Yes or No answers.

 When you change an answer, the status of the question group is automatically changed
to Reviewed. If you don't change any preselected answers within a group, you can manually set the
status of the group to Reviewed.

 To learn more about a question, click Details and review the information on Overview, Relevance,
and Dependency.

NoteThe information on Dependency changes based on the state of the scoping element. If it is
possible to change the selection of the element, the tab lists a simulation of the system selections
that would result. If it is not possible to change the selection of the element, the tab lists the
elements that caused its current state. If the element is in conflict with other selections, the tab lists
them so that you can decide which selections to reverse.

 To add notes or additional requirements for a business topic, use Your Notes.
 3. Review the changes you made in this step of the guided activity as well as the changes made
automatically by the system. The history of changes is cleared once you proceed to the next step.

 Click Display Scope Changes.

The recent changes are listed in descending order.

 To undo the last change, click Undo Last Scope Change.

 To redo the last change, click Redo Last Scope Change.

4. Click Next to continue.

NoteIf you have not reviewed all decision-relevant questions, a window appears asking you to
accept the preselected answers or to return to the questions that are not yet reviewed.

iv. On the Complete Project Setup step, review the summary of changes and provide additional
information about your change project.

1. Review the Summary of Changed Elements and, if necessary, click an element type to go back to
the corresponding step in the guided activity. For example, click Scoping to go back to the Adjust
Scoping step.

2. Under General Information, enter the Title and Description for your change project.

3. In some cases, it is possible to publish your changes without generating an activity list. If you choose
this option, your change project will be closed and changes are effective immediately.

However, in most cases an activity list is generated and the appropriate checkbox is preselected.
You have the possibility to include milestones and/or instructional activities to the activity list (these
are not added by default to a change project).

4. Under Planned Implementation Timeline, select the Start Date and End Date for your change
project.

5. Click Finish.

Result
 Based on your decisions, the system generates the activity list for your change project.

 To view a basic or detailed summary of your change project, click Display Project Details
(Basic) or Display Project Details (Complete).

 To start working on the activities in your activity list, click Open Activity List to Implement
Changes.

For more information, see Complete the Activity List.

NoteAny scoping changes you make may affect the organizational structure. Therefore, you should
always check the consistency of the organizational structure, which you can access from
the Perform Organizational Structure Setup activity in the activity list or from the Organizational
Management work center. To check the consistency after making scoping changes, go
into Edit mode (the Planning Area), and then click Activate All. Any inconsistencies will appear as
messages, which you then have to resolve.
Related Information