Skip to Content

SAP Consolidation Process

  At the beginning of SAP rollout in the corporation, in each country because these locations at separate cities had so many different requirements and situation, for making SAP rollout successfully as soon as possible we defined many different local customizing and process in SAP system, the component versions of SAP system were not same among these locations as well. At last it directly resulted in the actual situation as follows:

  • High Efforts in operational costs
  • High Complexity
  • High efforts in maintenance
  • Big efforts for release changes

  SAP system background before SAP consolidation:

Actual Situation

  In order to consolidate all SAP R/3 systems and achieve the following targets:

  • Savings in operational costs
  • Complexity Reduction
  • Synergies in global projects
  • Harmonized processes
  • Keep processes together

  We initiated a project of SAP consolidation process. The project aims to reduce the operative costs and promote the general untangling of complexity, increase the synergies in global projects, introduce standardized global processes and ultimately simplify the integration of new plants into SAP. Furthermore the “local systems” concepts were integrated for standardizing the financial and controlling structures. Moreover there were process changes or introductions of new software such as the SAP series production, and upgraded the SAP systems to the same version.

  So SAP system background after SAP consolidation:


  The project of SAP consolidation process is very necessary and feasible for the business operation in the corporation, along with more and more SAP solutions implementing in the corporation, the consolidation is unavoidable, it must have made the corporation more standard and flexible than before!

You must be Logged on to comment or reply to a post.
  • It is better to have the sandbox client in a seperate logical instance. Also you can try to introduce TDMS server for Quality and test instances. Virtual machines(For sandbox,development & Test instances) can be introduced to limit the hardware and effective utilizations of resources(CPU, Memory)
    warm regards,
    • Hi Makesh:

      Thanks for your comment, I would prepare some information about your concern, maybe I’ll post a new blog in the future. I’m very glad that you are intereting in my blog.

      Have a good day and best regards

  • Hello Tao,
    congratulations on this very interesting and descriptive blog post.

    As I see it, the biggest challenges facing SAP system environment consolidation projects in the medium term aren’t so much the need to meet company requirements (namely the actual consolidation of the SAP systems) but the need to implement all the measures that will ensure the successful operation and further development of a consolidated system. In other words, it becomes critical to establish processes that will institutionalize the system’s continuous development. Otherwise, the projects and system adaptations carried out after consolidation will be subject to paralysis and failure.

    The article doesn’t disclose how SAP Change and Transport Management is supposed to function after consolidation. However, the problems associated with having to make competing changes on system components due to simultaneous projects or a company’s change requirements are substantially exacerbated by such a project. This is particularly true in customer environments where, typically, configuration management of the SAP customer landscape is not practiced.

    Initially at least, simple protective measures can achieve a certain effect. This is one way to protect company templates and achieve a reasonable degree of harmony among the business processes implemented in SAP environments.
    Configuration Management, Impact Management, and Change and Transport Management

    However, to ultimately protect investments made in consolidated systems and harmonized business processes, one must address the need for suitable change and transport management processes and consistent comprehensive SAP configuration management. Moreover, the latter should include the objects related to process documentation, the documentation in general, and test management.

    SAP, in order to satisfy such requirements, normally refers one to the Solution Manager. Based on my experience in the aforementioned SAP system environments, Solution Manager will be overwhelmed by the complexity of competing, simultaneous demands associated with company requirements related to change and multiple-project management. Instead what it needs are additional approaches that incorporate institutionalized change and transport management, configuration management and impact analysis, which should occur as early as possible in the development cycle.

    Dieter, CEO,

    • Dear Dieter:

      Thanks for your wonderful comment, you spoke out the words in my heart, I’m highly appreciated that you shared your experience in my blog. Hope I can consult some difficulty with you in the future.

      Have a good day and best regards

  • I appreciate the insight provided by Mr Zhang and Mr Dieter; while both of them highlight benefits as well as the challenges in the SAP Consolidation projects  I am most interested in what has worked a what hasn’t. SAP directs to Solution Manager and while I agree it maybe the tool, the approach or methodology is key to make this project a success.