on 06-22-2010 11:31 AM
Hi Gurus,
Working on APO Consolidation/Version Upgradation...
1. Upgrade SCM 4.1 to SCM 7.0 -- >>
For upgradation what are ithe mportant Functional/Technical parameters required?? and the total Step by Step process??
2. We are having 7 APO(DP/SNP/SNC) and 7 R/3 System for allover the world , want to consolidate to One APO System -- >>
How we can accompliish the above task ?? What are the challenges while doing the same?
If any body having the solution/Step by step Process to do the task plz leyt me know
Thanks in advance..
Regards,
Rajesh patil
Hi Rajesh Patil,
1) For upgradation what are ithe mportant Functional/Technical parameters required?
Technical:-
a) Integration areas
b) Server sizing
c) RFC connections
d) Business system groups
e) Logical systems
f) Core Interface settings
Functional:-
a) Gather business requirements
b) Understand business process flow
c) Areas where improvement required
d) Required scenarios
2) Challenges during consolidation?
a) If the 7 R/3 systems have unique material codes,
then problems during integration with single apo system
b) Creation of Integration Models
c) Creation of RFC connections
d) Generation of Logical systems
e) Material master fields data population
Regards
R. Senthil Mareeswaran.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Rajesh,
Apart from valueable points Senthil has shared, I have few things for point 2
I am giving below business process perspective
How to consolidate 7 APO systems and 7 SAP R/3 systems
A. This is a big stretegic intiatives. There are many activities and this can be a big program with projects in it,
1. Process review and exercise to standardize, harmonize the processes and other third party tools, applciations apart from SAP R/3, APO
2. Design a global template of business processes with allowance for localization to say 10-20%.
For this exercise business process owners from all the regions/ areas need to get together, discuss and finalize.
3. If necessary implement a pilot to prove that the design works
4. Build and test the global template, build interfaces, perform unit, integration testing
5.Migrate data, train the users, Perform User Acceptance Testing, Roll out to the first region and continue support
6. Revaliidate the design and localize and roll out to different regions
B System point of view: Build a landscape: development, quality, Production, If necessary training system
Build objects, authorizations roles
C. Change management, Training
Hope this giives important points
Regards
Datta
User | Count |
---|---|
9 | |
4 | |
3 | |
3 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.