Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

what will be role of an abaper in global roll-out project ?

Former Member
0 Kudos

Hi Experts ,

I would like to know the role of an abaper in a gloabl roll-out project .I would like to know what are all tasks will be assigned to us?

If any one come across in a global roll-out project please let me know.

Thanks in advance.

Devika.

1 ACCEPTED SOLUTION

Former Member
0 Kudos

IMPLEMENTATION :This is project in which we implement sap for a company from scratch right from creating tables and data for the first time..writing code for the first time etc.

SUPPORT : this is the kind of project where SAP has been already implemented but due to some additional business requirement or any thing like small problems in general they hire a team who work for them to solve the small issues.its also called issue based project.

It depends on the Volume of the company and how many company codes and Plants it have and for how many it has to be implemented

There are different types of Projects in SAP:

1. Implementation

Customer wants to install SAP/Include different modules of SAP viz. MM/SD/FI/CO/PP etc for the first time.Previously he might be using some legacy system in his orgn. This is implementation project. Here one needs to integrate several modules, migrate data from Legacy system to SAP system. Need to prepare interfaces/RFC's to interact with 3rd party systems.

Most of the company's follow ASAP methodology for the Implementation projects

there are 5 stages in the ASAP methodology

they are

1. Project Initial Preparation

2.Business Blueprint

3.Realization

4/ Final Preparation

5.Golive And Support

ABAP work mostly starts in the Blue print ending stage or in the realization stage

2. Support

Customer has already installed SAP & wants to give the work of maintaining those systems. This is support project

There is no phases in it. Just receive the tickets, solve and send back to client.

3. Upgrade

Customer has SAP Version 4.6b and wants to update his version i.e. wants to go to Version 4.7. This is upgrade project

4. Rollouts

Customer has upgraded his version & wants to rollout country specific changes.

This is rollout project

Say a company is having branches in 3 to 4 countries.

In One country they have already implemented SAP

IF they wants to implement the same SAP in other countries of their branches they will simply follow the same SAP implementation policy (Rollout) how they have done for the first country just by changing the country specific settings and configurations.

ABAPER work starts with by receiving technical specifications. It needs to be reviewed with functional team. If there are no issues, abaper will start development. He will ocmplete development and unit testing. Then it needs to be tested by functional team and at last user. If program works as per the requirement, the object gets signed off. ABAPer also needs to fix the errors in the programs and also do suggested enhancements.

ashish

3 REPLIES 3

former_member223537
Active Contributor
0 Kudos

Hi Devika,

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

etc

Best regards,

Prashant

Former Member
0 Kudos

IMPLEMENTATION :This is project in which we implement sap for a company from scratch right from creating tables and data for the first time..writing code for the first time etc.

SUPPORT : this is the kind of project where SAP has been already implemented but due to some additional business requirement or any thing like small problems in general they hire a team who work for them to solve the small issues.its also called issue based project.

It depends on the Volume of the company and how many company codes and Plants it have and for how many it has to be implemented

There are different types of Projects in SAP:

1. Implementation

Customer wants to install SAP/Include different modules of SAP viz. MM/SD/FI/CO/PP etc for the first time.Previously he might be using some legacy system in his orgn. This is implementation project. Here one needs to integrate several modules, migrate data from Legacy system to SAP system. Need to prepare interfaces/RFC's to interact with 3rd party systems.

Most of the company's follow ASAP methodology for the Implementation projects

there are 5 stages in the ASAP methodology

they are

1. Project Initial Preparation

2.Business Blueprint

3.Realization

4/ Final Preparation

5.Golive And Support

ABAP work mostly starts in the Blue print ending stage or in the realization stage

2. Support

Customer has already installed SAP & wants to give the work of maintaining those systems. This is support project

There is no phases in it. Just receive the tickets, solve and send back to client.

3. Upgrade

Customer has SAP Version 4.6b and wants to update his version i.e. wants to go to Version 4.7. This is upgrade project

4. Rollouts

Customer has upgraded his version & wants to rollout country specific changes.

This is rollout project

Say a company is having branches in 3 to 4 countries.

In One country they have already implemented SAP

IF they wants to implement the same SAP in other countries of their branches they will simply follow the same SAP implementation policy (Rollout) how they have done for the first country just by changing the country specific settings and configurations.

ABAPER work starts with by receiving technical specifications. It needs to be reviewed with functional team. If there are no issues, abaper will start development. He will ocmplete development and unit testing. Then it needs to be tested by functional team and at last user. If program works as per the requirement, the object gets signed off. ABAPer also needs to fix the errors in the programs and also do suggested enhancements.

ashish

Former Member
0 Kudos

hi

good

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).

reward point if helpful.

thanks

mrutyun^