Enerjisa was one of my first enterprise projects. Between 2016 and 2018, I worked on the separation of its SAP systems. The company used SAP IS-U, SAP’s platform built specifically for utilities, and SAP IDEX was used for the separation and the data exchange between the two systems.
FI-CA, Billing, DM and WM were all actively used in the environment. My responsibility was to analyse all transfers between the two systems, investigate errors and route each issue to the right team. That meant understanding the process behind a transfer as well as the data being passed, so the technical team had a clear problem to work on.
- Analyse the transfer
- Investigate the error
- Route it to the right team
- Follow up on the defect
My responsibilities during the SAP separation, across an eight-person team and a wider technical group of more than 50.
The systems synchronised through overnight jobs. During one night shift, I noticed that a FI-CA error had brought the synchronisation to a halt across the systems. I called and woke the relevant team members so we could investigate together before the sales and payment channels opened in the morning. It was a case where spotting the failure and getting the right people involved quickly mattered as much as documenting the error.
My immediate team had eight people, and the wider technical team had more than 50. I worked across those teams to clarify transfer issues and follow up on defects during the separation. Enerjisa’s 2017 annual report gives some context on the wider system separation and data clean-up work from that period.
The screenshots show Enerjisa’s current Online Services Center, the public-facing side of the business. My role covered the SAP systems and their integration during the unbundling project.
