What happens when you decide to change your Data Model in IS-U
Well, there are more number of on-line resources about Master Data in SAP IS-U, thanks to those authors.
SAP IS-U data model – Business and Technical Master Data
How to Create Technical Master Data – Utilities Industry – SCN Wiki
But, what happens when you decide to change your basic Data Model in your IS-U? wait, why do you want to do this? To give you a scenario, in one of my previous project the data model was not standard in first place, and we have to change this to standard best practise, and now you got why this blog!
By not standard I mean, initially, for each divisions i.e. for Electricity service and for Gas service, users were using individual Contract Accounts and also individual technical master data. This means duplicate of data and business processes. Now in this case we have to change the data model towards as standard SAP IS-U approach as possible with minimum impact to the current business process.
There could be many ways to change this Data Model, but I am not going into detail of each, as it depends on specific client/project situation/scale/time/money…etc, few methods are below:
A) Having a custom migration process (initially thought of one-off process) where we did updates to the master data tables.
B) For affected scenario, perform Move-out of one fuel and perform move-in (no need of much custom developments compared to A).
Each method will have its own pros and cons, needs further custom enhancements and logic to be implemented at various process within IS-U.
For the first method (A) we do need to consider all the business processes currently being used by the customer and design an improved process by suggesting the standard. Following are the processes which I could think of immediately:
3) Change of Tenancy
4) Billing of Contracts (no major change here…)
6) Invoice printing (this is the big one)
7) Scheduling and Management of Meter Reading Process (no major change here as well)
8) Changes in Payment Schemes (next big one)
9) Payments and Returns
10) Collections and Dunning
Now coming to the technical part, yes, you got it right, most of the Technical and Business Master Data tables needs to be updated, to name few (and not restricted only to:) EANL, EUIHEAD, EVBS, EVER and other tables like EEINV, EAUSV, EBP_ADDR_SERVICE…etc.