By Category

Data migration for a medical device and diagnostics company

Engagement: The client was one of the world’s largest and most diverse medical devices and diagnostics companies based in the US. The corporate structure comprised a web of companies, depending on the nature of the product/service being provided to its customers. The parent company decided to have a common platform for transaction processing and reporting, replacing various legacy systems. This involved having a comprehensive process for data migration, including historical and transactional data. The expected benefit from migration was in the form of saving time, reducing effort and eliminating risk. The action plan was prepared by the client and shared with the respective Process Owners on the client side.  The Process Owners identified the key people who would work in collecting the data and coordinating with the functional teams. User awareness training sessions were conducted for Process Owners and key people working on the project.

SKP deputed key resources from the Accounts Payable and General Ledger (GL) teams, who would work closely with the client and the functional team. The following responsibilities were assigned to key resources:

  • Clean-up of Vendor Master data before migration
  • Compiling the Master database and providing it in the required format for upload
  • Mapping of GL Account codes, profit centres and cost centres
  • Rectification of mapping errors before migrating to the new system for correct reporting
  • Maintaining control over balances uploaded through sub-ledger and GL
  • Ensure Data Migration Clearing Accounts are zero (a check for accurate data migration).
  • Reconcile the Trial balance as per the new ERP system and from the existing ERP system
  • Performing User Acceptance Testing (UAT) with various scenarios as per prevailing practice
  • Resolving errors with the functional team identified during UAT
  • Providing requirements for various types of reports
  • UAT for year-end closure and performing the same in production

The ongoing scope of work
After the project went live, there were a lot of system issues that involved having calls with the client and the functional team.  Apart from the existing scope, the following activities were added:

  • Resolving GL coding queries from various requests made from the client side
  • Helping those requesting in preparation of journal entries, using templates
  • Providing resolutions for SAP errors while passing the journal entries
  • Running depreciation every month and cross checking it with Excel working
  • Ensure that the balance as per Fixed Asset Module matches General Ledger balance
  • Generating Edit reports to track changes/modifications in the Master database

Value Delivered

  • Enhanced the client’s confidence by adhering to the timeline
  • Managed a complex project