Legacy System Retirement (SAP release 3.1I)

We specialize in all aspects of legacy system retirement – from requirements gathering, to actual sun-setting of the system. Our philosophy is clear – retire legacy systems – not necessarily data. We recently retired a SAP 3.1I legacy system based off Asia Pacific region. The system size was around 390 GB on a non-Unicode stack. We have identified the categories of the data as below:

  • Customizing data – high importance
  • Master data – high importance
  • Transactional data – high importance
  • Application logs – medium importance
  • System logs – low importance

What we did

As a part of our practice, we have distributed a detailed questionnaire to identify business/legal/tax/audit requirement, and technical information about legacy hardware/software. Based on the questionnaire supplemented with our detailed internal research, we have identified the reporting requirements and data taxonomy. We have also gathered statistics of attachments/documents, and any active interfaces. Additionally, our analysis also included corporate retention schedule to ensure safe deletion of the data that is no longer required.

Based on major evaluation criteria, such as, cost, ongoing maintenance efforts, reporting flexibility – ease of use, ease of tagging & retirement, future availability of support talent, and presence of the toolset in company’s IT systems portfolio, we have determined to use our unique retirement model that is a balanced solution between cost, resources, and reporting requirements. We provide objective advise for the selection of the retirement tool that is in the best interest of client. In the first phase, we have migrated legacy data (transparent, blob, pooled, and de-clustered) into a standalone data base through our extraction tools. The data was made retrievable through 20 pseudo T. codes on an existing ECC/ERP system without loading the data into ERP database.

There are four major benefits of this approach:

  • Ease of tagging & deletion when the record is not required under corporate retention policy
  • Very cost effective since the data resides in a standalone database (can also be housed on Cloud based on data sensitivity)
  • Development of a repeatable business-friendly model useful during HANA upgrade.
  • Flexible to meet future reporting requirements with in-house skillset

Final Results

The project was completed in less than four months with two 50% allocated resources and one part time DBA. The business training and sign off was much faster since the pseudo code have a same look and feel of the T. codes that business is familiar with.