This is a solution suitable for large implementations with large number of customers. The interfaces are kept at minimum.For example:FI-CA posts reconciliation keys in the local General Ledger. Then the posting in thelocal General Ledger needs to be transferred in the R/3 General Ledger using aninterface usually ALE.The utility company buys new meters. This are managed in SAP R/3 from thelogistic and accounting point of view: purchase order, goods receipt and invoice. Butin the same time a interface (manual / automatic) needs to be established to makethe meters available in IS-U for the device installation process.There could be other examples as well but these are the ones are most common.
IS-U and R/3 Integration.
Let’s see the integration of IS-U and R/3 in depth detail.As I already told you, the IS-U is sometimes extending existing R/3 functionalitiesto cover the need of the utility business. But of course other functionalities werenewly developed.
is fully integrated with the PM and MM and AM modules. Adevice (e.g.: meter, transformer) is a serial number of a device category and in thesame time a piece of equipment. The device category is defined as a material in thematerial master.
is fully integrated with MM, SD, PM/CS and Controllingmodules. Here the utility company can implement a broad range of billed or non-billed services offered to the customers. For example a work management order isan extension of a PM/CS order and can be linked to IS-U objects such as BusinessPartner, Contract Account, Connection Object.
Billing & Invoicing
is fully integrated with SD. For example we can implement aprocess where some services are billed in SD and Invoiced in IS-U.
is fully integrated with Financial Accounting. CA is a sub-ledgerof General Ledger.
IS-U and external applications integration.