SAP Knowledge Base Article - Public

1922087 - How to Create a Change Project and Its Lifecycle

Symptom

The creation of a Change Project is required.

Environment

  • SAP Cloud for Customer
  • SAP Business ByDesign

Resolution

  • Change Projects and its Purpose:

The sole purpose of a change project is to make configuration changes to the solution once the First Implementation project is completed, meaning the system has gone live. These changes can be made by adding/modifying Business Configuration activities.

  • When to create a Change Project?

The Change Project is required in a case where the user desires to make changes or add activities that are not marked for Immediate Change Possible.

  • How to create a Change Project?

Below are the steps to create a new Change Project. The prerequisites would be that the First Implementation project is completed (Status: Live or Closed), meaning the production system has gone live. 

  1. Go to Business Configuration Work Center
  2. Access Implementation Projects View
  3. Click on New Button

Note: The New button will be disabled (grayed out) if the First Implementation project is still ongoing (status: In Preparation or Started or Tested).

  • Change Immediately:

For certain activities that are enabled for Immediate Change, the modification or inclusion can be done on the go, in the production environment itself. Activities enabled for immediate change will be marked "Yes" under the Immediate Change Possible field in the activity list and can be changed through the button Change Immediately. However, for the rest of the activities, change is possible only through a change project.

  • Options to implement the created Change Project:

There are two possibilities to implement a change project:

Implement Change Project into Production system

In this case, the necessary scoping and fine-tuning changes can be made in the production system itself. This is advisable in a situation where there are minor changes being made and there is no need for testing scenarios to check the behavior of the change.

Implement Change Project into Test System

If a test system exists already: The solution profile of the change project can be copied into the test system using the Copy Solution Profile button in the Systems view in Service Control Center work center. In the displayed pop-up the user is able to specify the Source Solution Profile ID by using the value help and searching the description with the name of the change project. Note: It is also necessary to specify the Target System in this case. 

Once the necessary changes and tests are completed, the change project can be merged back to the production system, and the test system will not be automatically terminated once the project is merged and closed.

If a test system does not exist already: The user can mark the change project in the Implementation Projects view and choose "Request System" button. This will redirect to the "Systems" views on "Service Control Center" work center to create a new system.
Upon being redirected, the user is able to either use the option to "Copy the Source System", or "Copy Solution Profile" into the new system. 

Note: The customer will first be given an initial implementation test system. Once the scoping and test are confirmed, they must request the production tenant based on the solution profile of the test tenant.

  • How to Cancel/Delete a Change project?

Note: The following applies for change project with/without a test system:

In case the user decides to scrap a "Change Project", it must be "Deleted" or "Canceled". 

  • If the current status of a Change Project is "In Preparation" the user is able to delete it. 
  • If the current status of a Change Project is "Started" or beyond, the user has to cancel it.

To know how to cancel or deleted a change project help documents titled Cancel A Change Project and Delete a Change Project can be referred.

The following are the different status changes that can be observed for the projects:

ProjectStatusStage /systemAction /ActivityRemarks
Implementation ProjectIn PreparationInitial System 
  • Only Edit Project Scoping is accessible
  • Accessible only by Initial User
Implementation ProjectStarted Confirm Design Acceptance
  • Initial user will be authorized to create Service Agent
Implementation ProjectTested Go Live Readiness Acceptance
  • Edit Project Scope is not possible instead it will be view Project Scope
  • It is possible to revert the status by revoking this milestone activity
Implementation ProjectLive Confirm Go Live
  • Only closure of project is possible after this status
Change ProjectMergedTest and productionMerge Changes 
Change ProjectActivatedProductionActivate Solution Capabilities 
Change ProjectClosedTest and ProductionClose Project
  • In case of Merging changes from Test to Production, the change project should be closed in respective systems. Closing the project in production will not close the project in test system

Repetition Required:

Some activities (for example, Data Migration activities) in the Activity List have to be repeated in other systems, due to the data in these activities not being able to be copied automatically to another system. For example, if a Activity is maintained in the Test tenant, it is required to repeat the same Activity in the Productive environment. The Activity List, will display which activities have to be repeated in the "Repetition Required" column.

Data Migration in Change Projects:

All data migration related activities are marked for Repetition Required in the activity list. Irrespective of whether the change project is implemented in a test system or not, all data migration related activities will re-open once the change project is merged and have to be closed again manually, after the data is migrated to the productive workspace.

See Also

Keywords

change project, implementation project, business configuration, lifecycle, status, create, delete, cancel , KBA , AP-RC-BCT , Business Config. Tools (SAP Business ByDesign , How To

Product

SAP Business ByDesign all versions ; SAP Cloud for Customer add-ins all versions ; SAP Cloud for Customer core applications all versions