on 11-30-2010 6:47 AM
Dear NewGL gurus.
Currently, our customer who uses SAP Enterprise version is
considering to do the upgrade from Enterprise to 6.0
and migration to New-GL at the same time with migration scenario 4.
I knew that "SAP strongly recommends the migration as independent project".
But, as long as I read the documents, it seems possible technically.
So, my questions are
1. If this customer does the upgrade and migration at the same time,
can they take SAP Migration Service from SAP AG properly?
2. SAP mentioned the reasons for this strong recommendation
such as
- 'migration is not only technical transfer'
- 'migration is conceptual change'.
However, I think the same thing can be said for upgrade project as well.
So, is there any other reasons for this recommendation?
BR
Yoshitada Kaneko
Dear Yoshitada Kaneko
Please also go through with below notes for more information.
Please also refer the FAQ note and below links
1070629
812919 SAP ERP new general ledger: Migration
1337521 safety delta in incremental work list update for phase 1
1171402 Compatibility IS-M/SD with General Ledger Accounting (new)
1072121 New general ledger migration: What is covered by Support?
1039752 New G/L migration: Restrictions and important information
1014369 NewGL migration: Availability of Development Support
1014364 New G/L migration: Information, prerequisites, performance
824995 LCC: Gen. questions/answers about local currency changeover
Please refer the more information at "/glmig" at service market place
http://wiki.sdn.sap.com/wiki/x/JghNCw
Reg
Madhu M
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Technically, it's possible. But, functionally, it should not be done together. These are two different projects and should be treated as such.
Regards,
Eli
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
First of all, these two projects involve basically different consultants efforts and therefore it will be difficult to manage/coordinate the work. Secondly, if something goes wrong with your system (especially, if you have non-standard programs and other developments), you won't be able to establish whether it was caused by the upgrade or by the migration. It's all about internal logistics and organization in your project... If you have top-level consultants and good coordination manager, you can take this risk. But, if you don't - and in 85% of projects this is the case - you'd better not.
Regards,
Eli
User | Count |
---|---|
110 | |
12 | |
11 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.