My client is doing the technical upgrade from 4.7 to ECC 6.0 and also wants to do the new GL implementation at the same time and that too in the middle of fiscal year.
I know SAP recommends that new GL migration and implementation should be done after upgrade and migration on the 1st day of new fiscal year.
If any of you have come across such situation please share your experience with me.
I know SAP recommends that new GL migration and implementation should be done after upgrade and migration on the 1st day of new fiscal year.
If any of you have come across such situation please share your experience with me.
For New GL, this is always good that you will start from scratch in new Client, so that there will be no major business risk.
The main risks for a migration project are related to a lack of understanding of the new G/L functionality. Members of the migration project team (client) may continue to think in classic G/L terms which can lead to new functionality such as document splitting for example either being excluded from the migration when it would be beneficial, or the document splitting producing inaccurate results. Also, without a full understanding of the new G/L functionality existing functionality such as special ledgers for example may be set up in the new G/L when they are no longer needed. This can lead to issues with data and decreased performance. Other potential problems that can be caused by a lack of understanding of the new G/L functionality include:
• Unsure what to use for segments
• Confusion about parallel ledgers
• Creating too many nonleading ledgers
• Not fully understanding document splitting (need or not)
Another significant risk is the amount of data cleansing that is required before the existing data can be migrated. For a migration with document splitting, open items on G/L accounts are time consuming to migrate and the more that can be cleared before, the better.
Other risks include the time required to test and also the time required to ensure that existing interfaces still work as expected. Many migration projects underestimate the time required for these, which can lead to problems in meeting project deadlines.
Therefore: Due to the many influencing factor, there is no general answer to the question of how successful & how long a New GL Migration Project should last. Migrating to the new G/L is complex and the data is highly sensitive, so a full project is necessary. Data cleansing is a significant part of G/L migration or conversion. Deleting G/L accounts that are not required, consolidating accounts, and clearing open items on open item managed accounts are all good examples of tasks that can be started well in advance of a future migration.
The main risks for a migration project are related to a lack of understanding of the new G/L functionality. Members of the migration project team (client) may continue to think in classic G/L terms which can lead to new functionality such as document splitting for example either being excluded from the migration when it would be beneficial, or the document splitting producing inaccurate results. Also, without a full understanding of the new G/L functionality existing functionality such as special ledgers for example may be set up in the new G/L when they are no longer needed. This can lead to issues with data and decreased performance. Other potential problems that can be caused by a lack of understanding of the new G/L functionality include:
• Unsure what to use for segments
• Confusion about parallel ledgers
• Creating too many nonleading ledgers
• Not fully understanding document splitting (need or not)
Another significant risk is the amount of data cleansing that is required before the existing data can be migrated. For a migration with document splitting, open items on G/L accounts are time consuming to migrate and the more that can be cleared before, the better.
Other risks include the time required to test and also the time required to ensure that existing interfaces still work as expected. Many migration projects underestimate the time required for these, which can lead to problems in meeting project deadlines.
Therefore: Due to the many influencing factor, there is no general answer to the question of how successful & how long a New GL Migration Project should last. Migrating to the new G/L is complex and the data is highly sensitive, so a full project is necessary. Data cleansing is a significant part of G/L migration or conversion. Deleting G/L accounts that are not required, consolidating accounts, and clearing open items on open item managed accounts are all good examples of tasks that can be started well in advance of a future migration.
No comments:
Post a Comment