0 évaluation0% ont trouvé ce document utile (0 vote)
367 vues21 pages
The document provides an overview of SAP IS-Utilities (IS-U) including its key master data objects, functions, and tables. It describes the business benefits of SAP for utilities companies including enhanced efficiency, increased asset usage, and improved customer relationship management. Technical master data objects in IS-U include connection objects, premises, installations, device locations, and devices. Billing and invoicing in IS-U is organized by portions, meter reading units, meter reading orders, and billing orders.
The document provides an overview of SAP IS-Utilities (IS-U) including its key master data objects, functions, and tables. It describes the business benefits of SAP for utilities companies including enhanced efficiency, increased asset usage, and improved customer relationship management. Technical master data objects in IS-U include connection objects, premises, installations, device locations, and devices. Billing and invoicing in IS-U is organized by portions, meter reading units, meter reading orders, and billing orders.
The document provides an overview of SAP IS-Utilities (IS-U) including its key master data objects, functions, and tables. It describes the business benefits of SAP for utilities companies including enhanced efficiency, increased asset usage, and improved customer relationship management. Technical master data objects in IS-U include connection objects, premises, installations, device locations, and devices. Billing and invoicing in IS-U is organized by portions, meter reading units, meter reading orders, and billing orders.
Contract Account FKKVKP Contract EVER Move In Document EEIN Connection Object EHAUISU Premise EVBS Installaion EANL Device Info Rec. EGERR *FKK* -> FI-CA related tables *EABL* -> Meter reading *ERDK/ERCH* -> Billing/Invoicing
DBERD** DBERDL* FKKVK* EAB* https://sites.google.com/site/kkrumi/sapis-u IS-Utilities SAP IS-U SAP IS-Utilities SAP for Utilities SAP Industry Specific Solution for Utilities
Contents 1. 1 SAP IS-U 1. 1.1 Introduction 2. 1.2 Business benefits of SAP for Utilities 3. 1.3 Useful Documents 4. 1.4 Useful Transactions 5. 1.5 Master Data - remains unchanged over a long period of time 6. 1.6 Business Master Data 7. 1.7 Technical Master Data 8. 1.8 Intercompany Data Exchange (IDE) 9. 1.9 Useful Tables 10. 1.10 Function Modules 11. 1.11 Device Management 12. 1.12 Billing and Invoicing 13. 1.13 Billing Procedure 14. 1.14 Billing Master Data 15. 1.15 FICA
Introduction A public utility (usually just utility) is an organization that maintains theinfrastructure for a public service. State provision of utility services (like electricity, gas, water, district heating, waste management etc.) often resulted in inefficiency and poor service quality. Trend towards liberalization, deregulation and privatization of public utilities encouraging competition among private players.
Business benefits of SAP for Utilities Enhances Efficiency of business processes o mass processing of consumption and customer-related financial data o efficient and automated exchange of data (deregulation processes) with market participants, enabling supplier switching as well as payment and settlement processes
Increased Asset Usage and Reliability o integrates information and processes from finance, procurement, maintenance, operational safety, and workforce management o integrates SAP solutions, legacy systems, plant and geographic information systems, outage management systems, and automated meter-reading systems o Optimized procurement reduced material inventory and efficientcollaboration with contractors and suppliers
Improved Customer Relationship Management o delivers personalized services o effective tools for designing and executing marketing campaigns
Useful Documents
ISU Transaction list [xls]
IS-U Transactions [xls]
ISU Data Creation [doc]
ISU Tables [ppt]
SAP Utilities [pdf]
Important Transactions in Workflow [xls]
Useful Transactions
EASY - Searches Transaction Codes in IS-U. EC20 - Front Office EC25 - Data Environment EPRODCUST - Master Data Template ECRMREPL - IS-U Contract Error Monitor EMMACL - Clarification Case List (EMMA Case) EMIGALL - IS-U Migration: Workbench (Data Migration Tool; Conversion) EQ81 - IS-U Migration Workbench: User Handbook
=DBUG - Debugging for 'Mass' Transactions FB* - IS-U FIGL (General Ledger) FP* - IS-U FICA EA* - Billing EL* - Meter Reading EG* - Device IQ01,2,3 - Create, Change, Display Material Serial No.
Master Data - remains unchanged over a long period of time
Business Master Data
Business Partner
Business Partner can be a person, group or organisation with whom the utility company has a business relationship. T-codes: BP - Maintain Business Partner FPP1/2/3 - Create/Change/Display Contract Partner Tables: BUT000 Fields: PARTNER(10)
Contract Account
A contract account groups together all of a business partners contracts to which the same payment and dunning data applies. It is an account through which the financial transactions between a customer and a utility company are managed (stores payment transaction data). T-codes: CAA1/2/3 - Create/Change/Display Tables: FKKVK, FKKVKP Fields: VKONT(12)
Contract
A contract is an agreement between a utility company and a business partner relating to a utility service. It forms the basis for billing. Created during move-in process. It is specific to one Division. T-codes: ES20/21/22 - Create/Change/Display ES27/8 - Change/Display Contracts for Contract Account Tables: EVER Fields: VERTRAG(10)
Move-in
A contract is created and allocated to an installation T-codes: EC50/1/2E (Create, Change, Display), EC53E (Reverse) Tables: EEIN (Cont. Acc.), EEINV (Contract)
Move-out
A contract with a customer is terminated T-codes: EC55/6/7E (Create, Change, Display), EC58E (Reverse) Tables: EAUS (Cont. Acc.), EAUSV (Contract)
Technical Master Data
Connection Object
Connection Object is a building, piece of property or other facility that is connected to the supply grid. A connection object is allocated an address. It links premises, device locations etc. to a postal regional structure. T-codes: ES55/6/7 - Create/Change/Display Tables: EHAUISU Fields: HAUS(30)
Premise
A premise is an enclosed spatial unit (such as an apartment or a factory) to which a utility service is supplied. It is allocated to a Connection Object. T-codes: ES60/1/2 - Create/Change/Display Tables: EVBS Fields: VSTELLE(10)
Installation
The connection between premise, devices, and contract is referred to as an installation. An installation is allocated to a single contract. Used to group together all devices that are allocated to same premise, belong to same division and are to be billed together. Several utility installations can be allocated to one premise (for different divisions, for example). The premise is therefore not related to one specific division. A deregulated scenario exists if more than one utility installation of the same division is allocated to a premise. The installation stores the billing properties for one or more devices at a premise T-codes: ES30/1/2 - Create/Change/Display Tables: EANLH(time slice), EANL Fields: ANLAGE(10)
Device Location
Device Location is a location in a Connection Object where any number of devices (across divisions) is installed. The device location provides information on the physical location of the device T-codes: ES65/6/7 - Create/Change/Display Tables: EGPLT, EGPLTX Fields: DEVLOC(30)
Device
Devices are physical objects. E.g. Counting Device (meter), controlling device (ripple control receiver), data processing device (converter), device with protective or adjustive functions (pressure controller) etc. T-codes: EG41,2/3/4 - Device Modification/Display /Create Tables: EGERS Fields: GERAET(18)
Point of Delivery T-codes: EEDM09/10/11 - Point of Delivery Create/Change/Display Tables: EUITRANS, EUIINSTLN Fields: INT_UI(22), EXT_UI(50) - POD ID
Intercompany Data Exchange (IDE)
Caters to needs of deregulated markets T-codes: EEDMIDESERVPROV01/2/3 - Service Provider Create/Change/Display IW52/3/4 - Service Notification Change/Display/Create EDATEXMON01 - Monitoring of Data Exchange Tasks ESWTMON01 - Monitoring of Switch Documents WEDI - SAP Easy Access IDoc and EDI Basis
Data Exchange Process Classes: CL_ISU_DATEX_PROCESS - ISU Data Exchange Process (Abstract) CL_ISU_DATEX_CONTROLLER - Connection and Control of Data Exchange Processes
DATEX Task EDEXTASK*
Service ESERVICE*
Service Provider ESERVPROV* EDEXDEFSERVPROV - Data Exchange Definition for Service Provider
Function Modules ISU_DB_EVER_SINGLE - Read Contract data ISU_DB_EANLS_SINGLE - Read installation data ISU_INT_UI_DETERMINE - Read Contract, Installation, Internal and External PoD ISU_S_NBSERVICE_CREATE - Create a non-billable service ISU_DB_ESERVICE_FORALL_POD - Read services associated with a POD ISU_DB_TECDE_SINGLE - Get Division for service Type
Device Management
Device Category Device Category corresponds to material in the Materials Management (MM) application component. T-codes: EG01/2/3 (Create, Change, Display) Tables: ETYP-MATNR
Register Group T-codes: EG04/5/6 (Create, Change, Display) Tables:
Device
Device Corresponds to equipment in the Plant Maintenance (PM) application component. The device is identified by a unique material and serial number combination to distinguish it from other pieces of material that may have the same serial number. The equipment number is the same throughout the whole system. Each combination of Material and Serial Number is unique. T-codes: IQ01/2/3 (Create, Change, Display Device) EG44, EG34 (Billing related installation), EASTL, EASTS Tables: EGERS, EGERH, EGERR Fields: EQUNR - Equipment Number Equipment number = internal device no. that is different in every client. MATNR - Material Number (Device Category) GERAET - Serial Number (Device)
Register T-codes: Tables: ETDZ-ZWNUMMER (3)
Billing and Invoicing
Portion T-codes: E41A - Display Portion E41B - Create Portion E41C - Change Portion E41E - Delete Portion E41J - Maint. Portion E43B - Generate SRs of all MRUs of Portion E43D - List of all MRUs of a Portion EA65 - Portion Change Tables: TE420
Meter Reading Unit (MRU) T-codes: E41L - List of MRUs Alloc. to Main MRU E43B - Generate SRs of all MRUs of Portion E41H - Create Meter Reading Unit E43E - Activate Meter Reading Units E43D - List of all MRUs of a Portion Tables: TE422
Meter Reading Order T-codes: EL01, EL31 Tables:
Billing Order T-codes: EL01, EL31 Tables: ETRG
Meter Reading Results T-codes: EL27 - Execute Correct Implausible MRR EL28 - Execute Single Entry EL29 - Execute Correct Plausible MRR EL30 - Estimate MRR EL31 - Monitoring of MR Data EL32 - Automatic Monitoring of MRR Tables: EABL (Meter Reading Documents)
Billing and Invoicing Billing vs. Invoicing Billing: Consumption and bill amount calculation process Performed at Contract level Determine billing periods Determine tariff (rate) data Invoicing: Process contract billing to contract account receivable and prepare printout Performed at Contract Account level Consolidate energy and non-energy charges, e.g. late payment fee Consolidate all items from different contracts to be invoiced under the same contract account