Tips and Tricks for Your Treasury Migration in SAP ECC 6.0

  • by Susanne Finke, SAP Consultant, ZANN Consulting, LLC
  • March 30, 2009
There is more to an upgrade for Treasury than just technical steps. See how to handle some pitfalls during the preparation stage of a Treasury migration, including Transaction Manager migration, to SAP ECC 6.0.
Key Concept

One of the structural changes in SAP ECC 6.0 is the requirement of parallel valuation areas. SAP has moved from the use of operational valuation areas to parallel valuation areas. Parallel valuation areas represent the different views of accounting principles within Position Management. Position Management is a new concept that is used to manage views on positions. The other structural change is that you have to implement Position Management procedures. The old operative valuation area functions have been integrated into Position Management. You use the procedures within Position Management in valuation or to generate derived business transactions and their execution sequence.

You may think that a technical upgrade to mySAP ERP 2004 or SAP ERP Central Component (SAP ECC) 6.0 is just that — a technical upgrade. However, if Transaction Manager components are implemented in the existing system, then these components have to be upgraded during the technical upgrade. The Transaction Manager is a component of Treasury and Risk Management. It contains tools that allow you to manage financial transactions and positions. The Transaction Manager upgrade involves the configuration migration from the prior version to the new functionality, as well as some manual configuration requirements, data (document level) migration, and updates to existing Treasury documents.

There is new functionality in the latest Treasury and Risk Management releases, but SAP has added items that have to be implemented structurally. As such, the configuration must be migrated to these new structures and existing documents have to be updated with these newly defined fields. Some of the configuration changes can’t be derived, so you have to configure them. You also have to move documents and configurations to new table structures.

I’ll highlight the initial steps and potential hurdles to look out for in the migration of Transaction Manager and its associated components in previous releases to the Transaction Manager in SAP ECC 6.0. I’ll use over-the-counter (OTC) transactions as the example. The Securities module (which handles stocks, bonds, or ownership investment transactions) involves much more discussion and is beyond the scope of this article. Additionally, there are various conversion types, but only one is selected for your specific migration. Each type has unique migration steps associated with it. For this article, I’m covering type 4: Conversion from <= Rel. CFM1.0/CFM2.0 to Enterprise 2.00/ERP2004/ERP2005. This covers the core migration steps not associated with Securities.

Susanne Finke

Susanne Finke has 26 years of business experience and more than 15 years of consulting experience in SAP Financials modules (FI, CO, TR, and AA), with R/3 versions 2.2e through SAP ECC 6.0. She is the author of the book, SAP Foreign Currency Revaluation: FAS 52 and GAAP Requirements (Susanne Finke; Copyright © 2006, ZANN Consulting, LLC., published by John Wiley & Sons, Inc.). She also wrote “Is Your Foreign Currency Revaluation FASB 52 Compliant?”, which was posted to the Financials Expert knowledgebase in October 2006.

See more by this author


Comments

No comments have been submitted on this article. 


Please log in to post a comment.

To learn more about subscription access to premium content, click here.