Reg Roll Out

[Former Member]

Dear all

What is role of ABAPer in Roll Out Project?

Any documents

Regards

Karthik

[Former Member]

Dear all

What is role of ABAPer in Roll Out Project?

Any documents

Regards

Karthik

[Former Member]

Hi,

Rollout process typically follows the following steps -

The first step is to decide upon the Organization structure for the whole entity

Form a Global Design Team - The global design team should consist of the people who have a detailed understanding the currently implemented functionality as well as an overview of the various region requirements

The next important task is to classify the IMG activities as Global/Non-Global. This is important because any changes to the configuration activities for implementing a project in SAP may have impact on the existing set of business rules and processes already set up in SAP

Create a Repository of all Custom Components - To keep track of simultaneous development changes in the two development environments, a repository of all custom objects / systems modification, need to be maintained separately. This would ease conflict resolution at the time of porting global template objects into the development system for live site, for subsequent rollouts

Create a change database to track all the changes - To track changes to objects / resolve conflicts between transports related to same object, a custom module can be developed within SAP. This module essentially consists of a database consisting of details of all objects, details of transports, a utility to look for potential conflicts and reporting

Roll-Out - After classifying the activities as Global/Non-Global, creating the object repository and the change database, the activities for roll-out can be started. This may include:Creation of a project in IMG that includes all Global activities. Creation of a project in IMG that includes all other activities. Revisiting all custom objects that are classified as Global and analyzing them so that future changes can be made without much impact to dependent regions and processes. For example, activating a user exit for a specific sales organization. Development/configuration to support region specific requirements. Update the object repository with new objects and any changes to the existing objects. Refining the roll-out methodology to include the learning from the current implementation.

Regards

Kannaiah

[Former Member]

Hi,

Rollout project means it was like a semi-implementaion. Rollout project Should be followed by the Company code dependent. Ex:- We are implementated 2 comapny codes i. e is 1000 and 2000. Both the comapny codes are using same global parameters. So that First we had done the implmentation for the one company code (1000). After that we will start the implementastion for the remaining cmpany code (2000) .Here we can copy the all the settings for the exisiting conapny code(1000)to new company code (2000). After that we has been maintain remaining company code settings. No need of maintain the Global paramenter in Rollout Project.

This is a sizing thing - usually, at the start of a project, you do an official sizing with SAP and your hardware vendor (http://service.sap.com/sizing and http://service.sap.com/quicksizer). What comes out is a number of "SAPS", that number is given to you selected hardware vendor and they offer you an appropriate machine that can handle the expected load (or more than one).

Global rollout will have development of objects which are specific to countries.

There would be few developments, which are common across countries & then few of them would be country specific.

Responsibilites of Developer:

1. Understand Functional specification & if any queries, get it clarified

2. Prepare the Technical Spec based on Functional spec

3. Get the Technical spec reviewed & do rework if any

4. Start with the development of objects

5. Follow all Development/coding guidelines & processes

6. Develop the code

7. Unit testing

8. Send it for review

9. Rework to be done, if any

10. Give the object to functional consultant for testing

Additional responsiblities could be:

1. Review Technical spec of peers

2. Review code of peers

3. Log Defects

Regards,

Raj.

[Former Member]

Thnx