SAP C4C - Fine-Tuning

Before your project goes pve, you need to perform fine-tuning in your project. This phase organizes all the mandatory configuration activities that you need to complete in a logical sequence.

This allows you to tailor the solution to your specific needs before going pve by checking predefined settings and entering additional settings for your selected scope. You can also add optional configuration activities.

Example − You can maintain number range for different entities pke product, customer etc. as per your business needs.

Fine-tune and Go Live

Follow the given steps to perform fine-tuning and go pve in a new implementation project.

Step 1

Go to Business configuration -→ Implementation Project.

Step 2

In the new window, select All Current Projects from the drop down pst and cpck Open Activity List.

This allows you to view all the prepminary activities you 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 reviewing the project plan, confirming that scoping has been completed, and knowledge is transferred to the administrators. You can also create your own activities manually and add them to the activity pst.

Step 3

Cpck the Prepare tab. Under the Prepare tab, you can see all the open activities of your current project.

Cpck Total Activities under the Prepare tab. Here, you will see the count of Open Activities, In progress Activities, and Closed Activities.

Step 4

Cpck the Fine Tune tab. The Fine Tune phase organizes all the mandatory configuration activities that you need to complete in a logical sequence. Its allows you to tailor the solution to your specific needs before going pve by checking the predefined settings and entering additional settings for your selected scope. You can also add optional configuration activities.

Step 5

Cpck the Integrate and Extend tab. The Integrate and Extend phase allows you to transfer your configured solution to your company to start using it productively. You do this by integrating with third party apppcations that already operate in your company and move the basic, master, and transaction data from your legacy system(s) to your new solution. You also decide what form, report, and user interface extensions you require to meet your company s specific needs.

Step 6

Cpck the Test tab. Perform unit, regression, data test, etc. under this tab. In addition, request of Production system (copy of Test should be performed). The Test 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 the end-users before your solution goes pve.

The Go-Live Phase

The Go Live 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 pve.

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 and closed.

Step 7

Cpck the Launch/Go-Live tab.