SAP IS-U Overview I
Overview of SAP IS-U CCS modules The IS-U CCS is a Industry Solution from SAP which address the needs of a customer oriented utility company. In the next pages we’ll refer to SAP for Utilities Industry Solution simply as IS-U or CCS. IS-U comprises the following modules: Master Data and Basic Functions Customer Services Work Management Device Management Billing & Invocing Energy Data Management Contract Accounts A complete SAP for Utilities solution should also contain the following SAP products: CRM – Customer Relationship Management BW – Business Warehouse. The CRM solution is design to cover all the marketing, customer acquisition, sales and customer services processes of a utility company. It is fully integrated with the IS-U: CRM works as a front end (contracts, customer services, market campaigns and IS-U as a backend (billing, payment processing, work management, etc). For example when using a CRM as a front end system, a contact created in CRM is replicated automatically in ISU where the necessary master data is created automatically using Master Data Templates. The Business Warehouse solution is used for reporting. Is comes with a Business Content which already contains a lot of predefined Info Cubs and reports. Where can IS-U be implemented? The traditional value chain in the energy industry is: Generation, transmission, Distribution, Supply and Customer Services and Billing. The IS-U has been successfully implemented and design for the Distribution, Supply and Customer Services and Billing. However IS-U (mostly EDM) has
. Implementing SAP IS-U and SAP R/3 in the same client: This is the best solution as the interfaces between SAP R/3 and SAP IS-U is native. Examples: .
. In R/3 a device category is a material in the Logistics Material Master.been implemented in Transmission companies as well. Typical landscape for a SAP for Utility Solution
SAP IS-U Overview II
SAP R/3 and IS-U can be implemented under the SAP IS-U Client or in different clients.a device location and connection object is a functional location in PM . IS-U practically extend some of the R/3 functionalities.FI-CA posts closed reconciliation keys in the General Ledger.a work management order is a PM order.an IS-U device is a serial number of a device category. Of course with a few/a lot of developments depending on which of the business processes were covered in IS-U. .
Contract Account.: meter. Connection Object. transformer) is a serial number of a device category and in the same time a piece of equipment. Billing & Invoicing is fully integrated with SD. But of course other functionalities were newly developed. The interfaces are kept at minimum. the IS-U is sometimes extending existing R/3 functionalities to cover the need of the utility business. The utility company buys new meters.g. Work Management is fully integrated with MM. The device category is defined as a material in the material master. For example we can implement a process where some services are billed in SD and Invoiced in
. But in the same time a interface (manual / automatic) needs to be established to make the meters available in IS-U for the device installation process. Device Management is fully integrated with the PM and MM and AM modules. SD. goods receipt and invoice. For example a work management order is an extension of a PM/CS order and can be linked to ISU objects such as Business Partner. As I already told you. Here the utility company can implement a broad range of billed or non-billed services offered to the customers. PM/CS and Controlling modules. Then the posting in the local General Ledger needs to be transferred in the R/3 General Ledger using an interface usually ALE. This are managed in SAP R/3 from the logistic and accounting point of view: purchase order.Implementing SAP IS-U in a different client than SAP R/3: This is a solution suitable for large implementations with large number of customers. A device (e. For example: FI-CA posts reconciliation keys in the local General Ledger. IS-U and R/3 Integration. There could be other examples as well but these are the ones are most common. Let’s see the integration of IS-U and R/3 in depth detail.
The deregulation market model leaded to a lots of changed in a utility company processes. distribution and supply. IS-U in deregulation markets. Meter Readings. CA is a sub-ledger of General Ledger. That is the unbundling of a classic utility company into: generation. other CRM Systems. Distribution and Supply . transmission. In the last 10 years the European market but other markets as well has adopted a new business model.IS-U. Automatic Meter Reading Systems. Because a customer has the right to change it’s utility supplier lead to a process called “Change of Supplier” where the suppliers and distributor need to exchange data about that customer such as: Billing Tariffs. External Billing Systems. transmission. The most important change was about the data exchange process between the utility companies.
IS-U and external applications integration. IS-U has evolved along with the utility market. IS-U can be integrated with external applications such as: GIS. distribution and supply. Contract Accounts is fully integrated with Financial Accounting. In order to support such processes SAP developed a new module for this called SAP IDE which supports the following processes: Change of supplier Billing of Distribution Services to Supplier
. Unpaid bills. SCADA. The unbundled utility market had several stages such as: .legal unbundling – splitting of the utility company in separated legal entities responsible with generation. Transmission.accounting unbundling – the utility company would present different P&L accounts for Generation.informational unbundling – accounting unbundling + the prevention of sales (supply) users to access the distribution data of customers supplied by other supplier .
Basic Functions & Master Data
. Waste Disposal can be handled by SAP IS-U. e. Electricity. These are called Industry Specific solutions.
SAP IS-U / CCS . Billing is probably the most challenging and important area for any ERP system considering the processing required for millions of customers every month-end. SAP has provided solutions that cater to the special demands of a particular Industry and are seamlessly integrated with the components of standard SAP. Processes related with divisions of a Utility Company e.Customer Care & Service SAP IS-U/CCS component is a Sales & Information system that supports all business processes and utility services of a utility company. Water.
SAP IS-U/CCS stands for the Industry Specific Solution for Utilities .g.Sending Meter Readings to Distributor / Supplier
SAP IS-U / CCS Overview Along with standard SAP R/3. A equipment defined in standard SAP R/3 PM can be used while creating a device in SAP IS-U. In a utility company. given the size of data processing.g. The core IS-U/CCS application is a consumption billing system that valuates measured and flat rate consumption and services. Heating.Features . Gas. Though Services ( but not consumption ) can also be billed and invoiced using standard Sales & Distribution (SD).
water / waste water. and multimedia services( e.
. Accounts Receivable & Payable and it manages postings from billing and budget billing requests. PoD . bills can be grouped into one invoice. Just for understanding. Devices are identified using material and srl number and are managed in PM as pieces of equipment with serial numbers. this data includes:
Business Master Data: as Business Partners. To make a perception. it handles extra fee / tax charging requirements. installations and device locations contained within connection object. Technical Master Data: as Connection Objects ( Buildings & Real estate ) and the premises. Billing: This component is used for billing the standard divisions like electricity. delivery point. Cable TV ) SAP IS-U billing is integrated with FI-CA. A Contract gets created at the time of customer Move-in (joining) and it also links Business and Technical Master Data.g.Features .Point of Delivery is the location where utility services are rendered and PoD id is used to identify it uniquely. organisations and agreements (contract) can be classified as Business Master Data.A high level overview of SAP IS-U components is as below:
Basic Functions: This component is used to manage addresses and regional structures along with generating dates and schedule for meter readings.Billing & Device Management
Device Management: This component manages the installations.g. processing data or controlling and protecting other instruments. and the certification of all devices for a utility company. Contract Accounts & Contracts. Customers ).
SAP IS-U / CCS . district heating. Also. devices and its installation. If one customer is taking services from both the divisions. a over simplified example of regional structure is Country->State-->District--> City in the context of India or Country --> County --> City for UK. Devices can be a electric meter or Gas meter etc.g. billing and budget billings. Master Data: In order to manage data that remains fixed for long period of time and is referenced by related transactions. gas. then as per the requirement. master data that is related with participating people ( e. Device is an instrument to measure consumption. Technical master data is related with identification of the building. e. meter reading. In SAP IS-U. Device Management of SAP IS-U is integrated with SAP PM ( Plant Maintenance ). Invoicing: SAP IS-U Invoicing enables grouping of bills before sending it to customer. electricity as well Gas or has multiple contracts.
Further.SAP IS-U / CCS . and supply.IDE
IDE .Features . an add-on to SAP IS-U/CCS provides a mechanism to effectively exchange and control data between service providers' systems. A request by the customer for a new connection will require a series of steps like creation of business & technical master data and then execution of move-in to create a contract. Customer service operator can also start the frequently used business processes at the request of customer. IDE covers the areas below:
Administration of deregulation data: It includes PoD.Communication Control To send and receive data for certain events.Features . the companies were used to be vertically Integrated having ï¿½bundledï¿½ businesses (i. transmission. data that was previously contained in a single system is now distributed amongst the different operating units in the value chain. Hence all data from all parts of the value chain were accessible to all parts of the company. But after deregulation. IDE. e.Customer Service
Customer Service: This component provides centralized and easy access to customer data. These processes. this will be a lot more complex in case of a change of supplier ( not a new connection ) as a lot of data exchange between the service providers ( winner & looser suppliers) and Transmission Company is required. through one screen. Generation. self accounting units for generation.g. companies are now split into individually operating. It uses PoD to determine the sender.
.e. and Distribution) under a tightly integrated holding company/operating company model.Intercompany Data Exchange: Before deregulation of utilities sector. By using CIC / Front Office. Process Execution . called Customer Interaction Center(CIC) or Front Office. Transmission. Point of delivery Services and Service Providers.
SAP IS-U . Actual transfer of data is done through Standard SAP's EDI / IDOC communication and hence in a sense IDE is a layer above EDI/IDoc functionality. So. companies must share data between systems. called a workflow. distribution. are generally a sequence of activities with dependencies and are performed by several people. In order to obtain all data needed to complete processing. Grids.
XI file adapter picks the files and validates the file through java mapping and passes it to Idoc adapter if the file is valid or passes it to RFC adapter.receiver and the information to be sent along with the required format. GA 4-6 months Start is ASAP Description • Gather. ○ Management of Data Exchange Processes
SAP-IS-Utilities Applications Specialist Atlanta. mainly Materials Management. Let me depict the scenario graphically:
. Plant Maintenance. • This position will work with other ISU Consultants and be responsible for the maintenance and support of the SAPISU production system with a CRM Winclient as the front-end. and configure the SAP-ISU system.I will provide the configuration to achieve the same. • Water utility experience required. • Document configuration. Funds Management. • Mastery of the IS-U data model and standard industry processes • Strong understanding of the Billing and Invoicing. with system configuration experience • Experience in the areas of integration of IS-U with other SAP systems. Finance and CRM • Ability to readily comprehend the configuration and design of the production system • Experience integrating all processes within the Customer Interaction Center and with CRM
In our current project. • Assist in the training of IT support personnel and end users. Desired Skills • Minimum of 3 years experience in production environment similar to government and public sector. Device Management. analyze. we have to trigger e-mails to shared folder of IS-U inbox in case the files that are pumped in for posting Idocs are invalid. which will trigger mails to IS-U by calling RFC SO_OBJECT_INSERT. and FI-CA components.
Configuration Steps in SAP IS-U: 1.
.Goto tcode SO01 and create folder XIWEBLOG from the menu as shown below.I will explain the steps involved for triggering an e-mail when the validation mapping produces the XML file with rejection details of the invalid file that is pumped into XI.
Folder Name and Year for the folder XIWEBLOG created.Goto tcode SE16 and give the table name SOFD and take a note of 3 attributes Folder Type. Configuration Steps in SAP XI: 1.2. 2.Import the RFC SO_OBJECT_INSERT into XI.
.We are going to send the e-mail asynchronously to SAP IS-U so we are going to use only the the request structure of the imported RFC. These details are required in RFC structure of SO_OBJECT_INSERT for triggering mails to the appropriate folders.
With this SAP IS-U is ready to receive mails in the XIWEBLOG shared folder.
"STATUS" corresponds to the result of file validation. Folder Details: 1.The output of Java validation mapping is an XML with the following XSD structure. 4.OBJYR-Year retrieved from SOFD. "ERR_RECORD" corresponds to error records in the file. 3.3. "FILE_TYPE" corresponds to the file type of a file (Ex: MRI.OBJNR-Folder Number retrieved from SOFD.
"ROW" corresponds to each record in the file.
. 2.I listed down the parameters that have to be passed to SO_OBJECT_INSERT in order to trigger emails to SAP IS-U inbox.OBJTP-Folder Type retrieved from SOFD. MIO).
special service function modules have been created in IS-U for the business objects of this application.LINE-Mail Content ("ROW"+"ERR_RECORD")
I have not detailed the required mapping. This means that the data model. They make an object-orientated transfer possible. The outflow is orientated around the target system IS-U.
. mails can be triggered to SAP IS-U XIWEBLOG folder. as the scope of the blog doesn’t pertain to that. The migration procedure cannot run based on tables. At the same time. In these units the data is transfered into the SAP system. or the function of the legacy system for migration is neither required nor used.An IS-Utility Data Migration Workbench
Migration is an open interface for transferring master data and transaction data to IS-U. We can check the mails in XIWEBLOG folder using SO01 once the message has been successfully delivered to RFC adapter.OBJDES-Subject of the Mail (Rejected file name: <Filename>)
Data Format: OBJECT_TYPE-RAW Mail Content: 1. Instead it has to compile related data in such a way as to guarantee consistency in the data after the transfer.Mail Subject: 1. The data is compiled into migration objects for the migration into the SAP application.
EMIGALL . because of the relational SAP system data model and the considerable complexities it contains. We are able to successfully send file level rejections as emails to our SAP IS-U inbox by using the above approach. Once we designed the appropriate mapping and required configuration is done in the ID and IR. These modules operate in direct input mode and can thus avoid the performance disadvantages of batch input processes.
It can consist of several SAP structures..Migration 2. a must learn for ABAP mainly IS-Utility as currently many IS-U implementation are going on all over the world. The Technology 4. Data sets that have been generated in this way. So. Data can be extracted from the legacy system using user-defined extraction programs. The exact record structure is determined per table settings in the Migration Workbench (transaction EMIGALL). You can find all the structures connected with a migration object in the dictionary.
. EMIGALL Step-By-Step Guide Purpose of this document is to provide a complete step-by step guidance for T-code EMIGALL for configuring the ISU – Migration Work bench & use it as a tool.The structure of a migration object is defined in controlling tables delivered by SAP. The Customizing & execution of ISU – Migration Work bench using T-code EMIGALL includes the following process steps 1. The Concept of Migration Object 3. which is generated by the customer system. for loading IS-U master and transactional data from one or more legacy system(s)..and SAP has given a very good functionality for IS-Utility Data migration which is famously called EMIGALL. it is Is-Utility data migration workbench. Using the IS-U Migration Workbench 6. The Scope of ISU . I got a book from following location . The code conversion (EBCDID to ASCII) is carried out at the same time. Migration Objects I m currently working on Is-Utility implementation project. and transfered to your target computer by file transfer. Migration Project 7. are read and processed in the SAP system by the import program. The data is then formatted and transfered to the direct input module. Migration Customizing 5. User-defined enhancements (fields) are taken into account at the same time. IS-U Migration work bench represents an open interface & works with the business objects instead of database tables and with direct input instead of batch input.
The outflow is orientated around the target system IS-U. The Scope of ISU . The migration procedure cannot run based on tables. special service function modules have been created in IS-U for the business objects of this application. The structure of a migration object is defined in controling tables delivered by SAP.Migration 2. So. IS-U Migration work bench represents an open interface & works with the business objects instead of database tables and with direct input instead of batch input. The code conversion (EBCDID to ASCII) is carried out at the same time. It can consist of several SAP structures. Data can be extracted from the legacy system using user-defined extraction programs. They make an object-orientated transfer possible. The Customizing & execution of ISU – Migration Work bench using T-code EMIGALL includes the following process steps 1. or the function of the legacy system for migration is neither required nor used. In these units the data is transfered into the SAP system. You can find all the structures connected with a migration object in the dictionary. The data is compiled into migration objects for the migration into the SAP application. User-defined enhancements (fields) are taken into account at the same time. Instead it has to compile related data in such a way as to guarantee consistency in the data after the transfer. Migration Objects
. Using the IS-U Migration Workbench 6. The data is then formatted and transfered to the direct input module. and transfered to your target computer by file transfer. The Concept of Migration Object 3. At the same time. The exact record structure is determined per table settings in the Migration Workbench (transaction EMIGALL). The Technology 4. are read and processed in the SAP system by the import program. which is generated by the customer system.Migration is an open interface for transfering master data and transaction data to IS-U. Migration Customizing 5. This means that the data model. because of the relational SAP system data model and the considerable complexities it contains. Migration Project 7. These modules operate in direct input mode and can thus avoid the perfomance disadvantages of batch input processes. Data sets that have been generated in this way.