Roll out project details

[Former Member]

Hi Guru's

Iam going to assign rollout project could u please tell me the details, Roles and responsibilities being a sd consultant

Thanks and Regards

Srinivas Kapuganti

[Former Member]

Answered

[Former Member]

Hi Srinivas,

In Simple the Roolout Project is like,

Client had already implemented and using SAP.

Ex:- Client is having 6 Plant and purchased / Established New

Plant.It could be at Locally or Globally.

In the New Plant they want to Use / Implement SAP.

This is Called Rollout Project.

The Difference between Implementation and Rollout Project is

Implementation: As a Funtional Consultant, we have to study the Business of the client and have to do from the Scrath and even if you are creating any New Sales Organisation, We could advise a Code ( Four Digit Code) and Discription to the client.

But In Rollout Project you no need to do all these things.The client will be givng the codes and discriptions etc.,

Means you are doing a new Addition or Extension to the Existing One.

Hope this is Clear and Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

Hi,

Rollout Means existing business you have to do some enhancements and changes .

If it is useful reward points

Regards,

srinivasa Reddy

[Former Member]

Hi

Global Rollout with a Template

Purpose

In a global rollout you define one or more templates containing scenarios, Blueprint documents and configuration, at head office.

You can decide which parts of the template are relevant to the subsidiaries, and whether, or to what extent, they can change the template in their rollout projects.

You transport the centrally-defined template to the subsidiaries. They use the template in an implementation project to implement solutions, following your guidelines.

Prerequisites

You have created a template project in the Project Administration.

You have assigned a transportable package and a transport request of type 'Workbench Request' to this template project.

Process Flow

Defining a template in the company headquarters

1. You create one or more templates in your template project, in the company headquarters Project Administration.

2. Set the Global Rollout Functionality is Active flag in the Templates tab in the Project Administration.

This means that the subsidiaries can change structures and business content from this template, within limits, in their local rollout project.

3. Assign values in the structure element Global Attribute column, in the Structure tab in the Business Blueprint, to specify whether each structure element is to be obligatory, changeable, or not changeable for the subsidiaries.

For further information about the effects of the attribute value on a structure element at the subsidiaries, see The Global Attribute in Global Rollout.

4. To pass on the Global attribute to the subnodes of a structure element, select it in the Structure tab in the Business Blueprint, and choose Pass On Global Attribute.

To prevent inheritance of the Global attribute, choose the empty row from the possible entries help for the Global Attribute column, at scenario level.

5. Perform the activities required in the Business Blueprint phase, e.g. assign transactions and general documentation.

6. Perform the activities required in the Configuration phase, e.g. assign Business Configuration Sets.

7. If you want to implement the template in subsidiaries which have a different project language from that in the headquarters template project, translate the template.

8. Deliver the template.

Import the template into the subsidiaries

...

1. Send the objects which you have created in the company headquarters component systems in the Solution Manager, to the subsidiariesu2019 component systems (see Transport a Template to Another System Landscape in Using a Template).

2. Send the template to the subsidiaries.

3. Import the template in the subsidiaries (see Importing the Template into the Target Systems in Using a Template).

4. If the template has changed, compare the new version of the template with the project structure and the assigned objects of your target system, and copy the changes if required.

Apart from the points mentioned above you have to look for the localisation part like

1.Taxation

2.Org Structure

3.Out put Forms

4.Legal and Local business requirments.

Thanks

Manoranjan

[Former Member]

Thank you Mr.Rajesh

Could u please tell me what are the questionire we have to prepare for this

Thanks and Regards

Srinivas Kapuganti

[Former Member]

Hello,

The rollout project usually means upgradation from previous sap system to newer version of sap.Most of the times the business processes remains the same and organisation structure also remain the same.You can tell it is a copy paste job from previous system to new system.But my rollout was more like a implementation with lot of new requirements. My

rollout project started with Business Blue Print or template as it is called. Then once that BBP is signed by the client then you prepare the Config plan document which will combine the organisation structure of all the modules and once it is signed by the client then you start your configuration in development client.The same is moved to quality client later.Then you will unit testing after all the configuration is over for all the relevant business cycles.Then we will have Power User Training with all the documents we have to prepare.You prepare the FS for all the output forms and sometimes you may migrate the old output programs. Then we will have Integration Test 1 & 2.Then from clients side User Acceptance Testing will be there. Once we get the sign off then we plan for data migration activities.

[Former Member]

http://help.sap.com/saphelp_sm40/helpdata/en/6a/bf1603d4f0944c81366cef7427bd12/content.htm

Roll out is kind of implementation in the sense that, if an implementation is already done for a country the same settings would be setup for the new country for which the roll out is being carried out. Some minor settings specific to that new country are anyway setup again. Major part of the already carried out settings are implemented for the new country based on the previously carried out implementation.

A roll-out project takes the main customizing/programs done for a company an adapts it to the new company, working only on the small differences between the companies: eg: printouts, logos, company code...

Incase of India additionally you will have to do CIN Settings.