Background

The customer is a company in the public sector with highly complex operations and stringent confidentiality requirements.

The customer faced a significant challenge following the completion of an extensive SAP implementation spanning several years and costing billions of kronor. After the lengthy implementation, the management organization discovered unexpected challenges with a table that was growing exponentially.

The problem was not urgent, but the trend was unsustainable and would lead to SAP disclaiming responsibility for the system solution when the table exceeded a certain size. The customer was on track to reach the critical point.

Mission

The customer's partner implementing the solution was at a loss and suggested that the only way forward was to rebuild the entire system. "Do it again, do it right" was the advice given. A meeting was booked to discuss if there was any other solution as it would be very costly to rebuild.

Implema Business Solutions was invited to the meeting as an advisor. Quite quickly, our senior solution architect with many years of experience from SAP's solutions and logic realized that this was not the right way to go. SAP was unlikely to build a solution that required them to duplicate data in another part of the system in order to solve the customer's needs, which were basically relatively simple and standardized in terms of objects.

What should be done?