IS-U = Industry Specific Solutions for Utilities Industry
IS-U = Industry Solutions –Utilities.
We love the below IS-U House. This one diagram works betterthan 1000 words.
BP -> CA -> CO -> Installation -> Premise -> Connection Object -> Device
BP -> CA => 1:N; CA -> CO => 1:N
where BP = Business Partner; CA = Contact Account; CO = Contract
Business Partner can be GOI. No not Government Of India but Group, Organization or Individual. ? They are BP types based on Attributes.
Also, BP can be CICP i.e Contract Partner, Installer, Contact Person or Prospect based on Role.
A Business Partner can have multiple Contracts (one for electricity,one for water, one for solar electricity, one for home security etc). All thesecontracts can be grouped together in a Contract Account provided all theContracts have the SAME Payment and Dunning data.
1:N => BP:CA
1:N => CA:CO
Items with the SAME due date and origin can be grouped together in a Collective Bill.
So, what is a Collective Bill Account?
Collective Bill Account is a special Contract Account which has a check box for collective bill account marked. P A contract account that is created in the business master data of the utilities industry and is marked as collective bill account becomes a Collective Bill Account.
All Collective Bill Accounts are Contract Account. But allContract Accounts are NOT Collective Bill Accounts.
Contract is that granular master data which the customerwith the service provider. Hierarchy is BP->CA->CO.
Also Read: End to End Free ABAP on HANA Training
Connection Object in SAP IS-U is the cousin of Functional Location in SAP ECC (Plant Maintenance). Connection Object is usually the building, but it can also be a plot of land, building site or a sprinkler/fountain.
Premise is the apartment, house, factory floor or the guard’s room in the apartment complex that has to be supplied with the service (electricity, water, waste management etc). In other terms, Premise is a spatially enclosed unit that has to be supplied.
It is important to note that the Premise is allocated to aConnection Object.
One Installation is linked to ONLY one Contract. But one Contract can have multiple Installations. Installation groups together devices, registers etc which are allocated to the premise and are billed jointly.
Point of Delivery (POD)
As the term suggests, Point of delivery is the point where the service is supplied and the utility service can be identified uniquely for the customer.
Point of Delivery is identified by a unique key which is called Point of Delivery Id. This Id helps the service company to communicate with external systems. External systems can be competitors or distributor or the services transmission company. Have you heard the work ESID? Spelled it as Easy Id. ?
Usually the Point of Delivery Id remains the same even ifyou change your Service Provider.
Whenever a customer contacts the customer care of the service provider, the communication has to be logged. The historical data helps and is needed for the service provider to be compliant in case of any litigation. Also, these logs help the customer case agent to provide the change history requested by the customer.
To track the Contact Logs, Contact Class and Activities are configured. Contact Class can be for Information, Billing, Budget Billing etc. While Contact Activities describes the action like Rate Information, Account Information, CC change, Opt-In, Opt-Out of any service.
In subsequent articles, we would share the custom code to create Contact Logs in SAP IS-U system. Please stay tuned.
All Business Objects used in SAP IS-U and CCS (Customer Care& Service)
Below image gives a high level overview of almost allbusiness objects needed in SAP IS-U projects.
Try to check the color coding to identify which object belongs to which area. For example Contract Account belongs to FI-CA.
Say a new customer is requesting to avail the service of an Energy Company. So, what are the sequences of events?
Create BP, CA, CO and Installation. Before the move-in, Connection Object, Premise and Installation must be entered. Device can also be installed before move-in but it is not necessary.
High Level Move-In Process
Whenever the customer calls the call center or visits the physical office for Move-In, we need to identify the premise and business partner (customer). If the customer is not found, create a new bp/customer. Look for existing contract account and edit it if found. If the customer is first timer, create a new Contract Account. Finally create a Contract. These are mandatory steps.
Apart from above mandatory steps, agents should (optionalduring move-in but ultimately needed) add contact data (contact log history),prepare/carry out move-in meter reading, maintain rate data, check billingstructure, check credit history, request for deposit (if needed), create billingplan and offer the welcome letter.
High Level Move-Out Process
Mandatory steps for Move-Out are to identify and choose the BP, CA and CO. Provide Move-Out Date and Final Meter Reading.
In addition to above essential steps, the agents can addcontact log, edit the contract account, prepare the final meter reading, finalbilling, print and issue final invoice and create Move-Out confirmation.
The IS-U SAP System would automatically terminate the Contract, stop the budget billing collection (if any), suspend any dunning procedure and modify any dunning procedures which may affect the open items.
Installation Data do not change with new customers
When I first started working in SAP IS-U, I was surprised to know that certain data do not change even though the customers change. One of them is Installation Data. Check the below figure where one customer moves out of a facility and another customer moves into the same facility. Look, the installation data remains the same for both the customers.
Installation Data does not change with Customers.Installation gets delimited with expiry/termination date and then new dates getactive for new customer.
Also Read – How I created my first SAP OData Service
In this article we tried to touch the tip of the iceberg. We wanted to make you familiar with some commonly used terminologies in SAP IS-U. In the next article we will create some IS-U Master Data in SAP IS-U System hands-on (exercise).
IS-U Master data can be divided into two types:
- IS-U Business Master Data
- IS-U Technical Master Data
Business Partner, Contract Account and Contract fall into IS-U Business Master Data.
Installation, Premise, Connection Object and Device fall into IS-U Technical Master Data.
In the next articles, we will learn how to create the BP, CA and CO using transaction code FPP1, CAA1 and ES20 respectively. We will also learn how to use t-code IQ01, ES55, ES60 and ES30 to create Device, Connection Object, Premise and Installation respectively.
So, please stay tuned, we are slowly exploring SAP IS-U and you should be part of this learning journey.
Comments and Feedback Please!!
We have a very active Telegram (App) SAP Technical Group with more than 5020+ SAP Technical Practitioners from 6 Continents of the SAP World. Please join it using below link.
Telegram SAP Technical Discuss Group. You need to install the Telegram App first on your mobile device. Once you have it on your mobile, you can join the group and also access it from the Web on your computer and laptop.