Data Sources in the Utilities Industry

ADDON.NDBW_IS_UT

DataSources in the Utilities Industry

Release 330

SAP Online Help

28.01.2004

Copyright © Copyright 2004 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of Microsoft Corporation. IBM®, DB2®, DB2 Universal Database, OS/2®, Parallel Sysplex®, MVS/ESA, AIX®, S/390®, AS/400®, OS/390®, OS/400®, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere®, Netfinity®, Tivoli®, Informix and Informix® Dynamic ServerTM are trademarks of IBM Corporation in USA and/or other countries. ORACLE® is a registered trademark of ORACLE Corporation. UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group. Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other Citrix product names referenced herein are trademarks of Citrix Systems, Inc. HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. JAVA® is a registered trademark of Sun Microsystems, Inc. JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MarketSet and Enterprise Buyer are jointly owned trademarks of SAP AG and Commerce One. SAP, SAP Logo, R/2, R/3, mySAP, mySAP.com and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are trademarks of their respective companies.


320

2

SAP Online Help

28.01.2004

Icons in Body Text Icon

Meaning Caution Example Note Recommendation Syntax

Additional icons are used in SAP Library documentation to help you identify different types of information at a glance. For more information, see Help on Help → General Information Classes and Information Classes for Business Information Warehouse on the first page of any version of SAP Library.

Typographic Conventions Type Style

Description

Example text

Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Cross-references to other documentation.

Example text

Emphasized words or phrases in body text, graphic titles, and table titles.

EXAMPLE TEXT

Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE.

Example text

Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text

Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation.

Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT

Keys on the keyboard, for example, F2 or ENTER.


320

3

SAP Online Help

28.01.2004

DataSources in the Utilities Industry.......................................................................................... 7 DataSources in the Utilities Industry...................................................................................... 7 Stock Statistics for Installation ............................................................................................... 7 Stock Statistics for Installation ............................................................................................... 7 Stock Statistics for Connection Objects................................................................................. 8 Stock Statistics for Connection Objects................................................................................. 8 Stock Statistics for Reference Values.................................................................................. 10 Stock Statistics for Reference Values.................................................................................. 10 Stock Statistics for Devices.................................................................................................. 11 Stock Statistics for Devices.................................................................................................. 11 Stock Statistics for Device Locations ................................................................................... 13 Stock Statistics for Device Locations ................................................................................... 13 Stock Statistics for Business Partners ................................................................................. 15 Stock Statistics for Business Partners ................................................................................. 15 Stock Statistics for Partner Contacts ................................................................................... 16 Stock Statistics for Partner Contacts ................................................................................... 16 Stock Statistics for Premises ............................................................................................... 18 Stock Statistics for Premises ............................................................................................... 18 Stock Statistics for Contracts ............................................................................................... 20 Stock Statistics for Contracts ............................................................................................... 20 Stock Statistics for Contract Accounts................................................................................. 23 Stock Statistics for Contract Accounts................................................................................. 23 Sales Statistics..................................................................................................................... 24 Sales Statistics..................................................................................................................... 24 Parallel Extraction of Sales Statistics .................................................................................. 30 Transaction Statistics: Billing ............................................................................................... 31 Transaction Statistics: Billing ............................................................................................... 31 Transaction Statistics: Certifications .................................................................................... 33 Transaction Statistics: Certifications .................................................................................... 33 Transaction Statistics: Billing-Related Installation/ Removal............................................... 34 Transaction Statistics: Billing-Related Installation/ Removal............................................... 34 Transaction Statistics: Move-in/out...................................................................................... 35 Transaction Statistics: Move-in/out...................................................................................... 35 Transaction Statistics: Invoicing........................................................................................... 37 Transaction Statistics: Invoicing........................................................................................... 37 Transaction Statistics: Devices ............................................................................................ 39 Transaction Statistics: Devices ............................................................................................ 39 Transaction Statistics for Sample Lot Procedure................................................................. 41 Transaction Statistics for Sample Lot Procedure................................................................. 41 DataSources in the Utilities Industry

320

4

SAP Online Help

28.01.2004

Transaction Statistics: Installation Disconnection................................................................ 42 Transaction Statistics: Supply Disconnection ...................................................................... 42 Transaction Statistics: Rate Maintenance ........................................................................... 43 Transaction Statistics: Rate Maintenance ........................................................................... 43 IS-U Disconnection Document Data .................................................................................... 45 IS-U Disconnection Document Data .................................................................................... 45 IS-U Contract: Non-Time-Based Part .................................................................................. 47 IS-U Contract: Non-Time-Based Part .................................................................................. 47 IS-U Contract: Time-Based Part .......................................................................................... 47 IS-U Contract: Time-Based Part .......................................................................................... 47 IS-U Installation: Non-Time-Based Part............................................................................... 48 IS-U Installation: Non-Time-Based Part............................................................................... 48 IS-U Installation: Time-Based Part....................................................................................... 49 IS-U Installation: Time-Based Part....................................................................................... 49 IS-U: Premise....................................................................................................................... 50 IS-U: Premise....................................................................................................................... 50 IS-U Connection Object (with service address) ................................................................... 50 IS-U Connection Object (with service address) ................................................................... 50 IS-U Partner-Based Data of Contract Accounts .................................................................. 51 IS-U Partner-Based Data of Contract Accounts .................................................................. 51 IS-U: Business Partner ........................................................................................................ 52 IS-U: Business Partner ........................................................................................................ 52 IS-U Historical Consumption Values.................................................................................... 52 IS-U Historical Consumption Values.................................................................................... 52 IS-U Historical Consumption (Delta by Mass Activity) ......................................................... 55 IS-U Historical Consumption (Delta by Mass Activity) ......................................................... 55 Partner-Independent Contract Account Data....................................................................... 57 Partner-Independent Contract Account Data....................................................................... 57 Partner-Independent Contract Account Data....................................................................... 57 Partner-Independent Contract Account Data....................................................................... 57 Payment Scheme................................................................................................................. 58 Payment Scheme................................................................................................................. 58 Point of Delivery Header Data ............................................................................................. 59 Point of Delivery Header Data ............................................................................................. 59 External Point of Delivery ID ................................................................................................ 60 External Point of Delivery ID ................................................................................................ 60 Allocate Point of Delivery to Installtion................................................................................. 61 Allocate Point of Delivery to Installtion................................................................................. 61 Prepayment Meter ............................................................................................................... 62 Prepayment Meter ............................................................................................................... 62


320

5

SAP Online Help

28.01.2004

Prepayment Meter Master Data........................................................................................... 63 Prepayment Meter Master Data........................................................................................... 63 IS-U Mass Simulation of Billing............................................................................................ 64 IS-U Mass Simulation of Billing............................................................................................ 64 IS-U Mass Simulation (Forecast C&I Customers) ............................................................... 66 IS-U Mass Simulation (Forecast C&I Customers) ............................................................... 66 IS-U Item Type (CRM) ......................................................................................................... 68 IS-U Item Type (CRM) ......................................................................................................... 68 Service Quotation for the Utilities Industry (Item) ................................................................ 69 Service Quotation for the Utilities Industry (Item) ................................................................ 69 Service Contract for the Utilities Industry (Item) .................................................................. 71 Service Contract for the Utilities Industry (Item) .................................................................. 71 Point of Delivery (CRM) ....................................................................................................... 73 Point of Delivery (CRM) ....................................................................................................... 73 Remote Extractor: Profile Values......................................................................................... 74 Remote Extractor: Profile Values......................................................................................... 74 IS-U: CRM Hierarchical Outline Contracts........................................................................... 75 Texts for Outline Contracts .................................................................................................. 77


320

6

SAP Online Help

28.01.2004

DataSources in the Utilities Industry Stock Statistics for Installation Technical name: 0UC_ISU_25

Technical Data Type of DataSource

Transaction data (movement data)

Application Component

Utilities Industry 0IS_UC

Available from OLTP Release

mySAP Utilities 4.61 (4.6B)

RemoteCube-Compatible

No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the installation stocks to the InfoSource 0UC_ISU_25 (stock statistics for installation). The statistics are written when the installation is created or changed. View V_EANL is read. The regional structure data (ADRC, ISU_REG0) is determined using the address of the connection object that belongs to the installation. A trigger is written for future changes to the historical data of the installation (EANLH). Once the future date is reached, the program REUSTACT processes the trigger and executes the changes. REUSTACT adds the updated changes to the statistics.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require. If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure in the installation. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields from view V_EANL to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all installations according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields in the extraction structure are changed.

We recommend the initialization of all installations, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.

Origin Fields in the Extract Structure Field in Extract St t

Description of Field in Extract St t


Table of Origin

320

Field in Table of Origin

Changed as of:

Type of Change

7

SAP Online Help

28.01.2004

Structure

Structure

AB

Date from which a time slice is valid

SYST

DATUM

ANLAGE

Installation

EANL

ANLAGE

VSTELLE

Premise

EANL

VSTELLE

LOEVM

Deletion indicator

EANL

LOEVM

SPARTE

Division

EANL

SPARTE

BEZUG

Reference

EANL

BEZUG

ANLSTAT

Installation status

EANLH

ANLSTAT

AKLASSE

Billing class

EANLH

AKLASSE

ABLEINH

Meter reading unit

EANLH

ABLEINH

TARIFTYP

Rate category

EANLH

TARIFTYP

BRANCHE

Industry

EANLH

BRANCHE

TEMP_AREA

Temperature area

EANLH

TEMP_AREA

ABLSPERR

Meter reading blocking reason

EANL

ABLSPERR

ANLART

Installation type

EANL

ANLART

SPEBENE

Voltage level

EANL

SPEBENE

CITY_CODE

City code for city and street file

ADRC

CITY_CODE

CITYP_CODE

City district code for ADRC city and street file

CITYP_CODE

STREETCODE Street code for city and street file

ADRC

STREETCODE

COUNTRY

Country key

ADRC

COUNTRY

REGION

Region (state, province, county)

ADRC

REGION

REGPOLIT

Element of the political regional structure

ISU_REG0

REGPOLIT

STATANZ

Number in the statistics

ERDAT

Date the record was EANL created

ERDAT

AEDAT

Last change date

EANL

AEDAT

IS-U/CCS 4.71

Field added

OUCONT

FlagOutline contracts

EANL

OUCONT

IS-U/CCS 4.71

Field added

Stock Statistics for Connection Objects Technical name: 0UC_ISU_26


320

8

SAP Online Help

28.01.2004








No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers regional information on the connection object to the InfoSource 0UC_ISU_26 (stock statistics for connection object). The statistics are written when the connection object is created or changed. View V_EHAU is read. The regional structure data (ADRC, ISU_REG0) is determined using the address of the connection object. Address data in the extractor can only be transferred when the it has been entered in the IS-U system together with the regional structure. Future data is not processed directly.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require. If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure in the installation. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields in view V_EHAU to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all connection objects according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields are changed in the extraction structure.

We recommend the initialization of all connection objects, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.

Origin Fields in the Extract Structure Field in Extract Structure

Description of Field in Extract Structure

Table of Field in Table Origin of Origin

AB


SYST

DATUM

HAUS

Connection object

ILOA

TPLNR

LVORM

Deletion indicator

CITY_CODE


ADRC

CITY_CODE


320

Changed as of:

Type of Change

9

SAP Online Help

CITYP_CODE

28.01.2004

City district code for city and street file

ADRC

CITYP_CODE


ADRC

STREETCODE

COUNTRY

BSI: Country code

ADRC

COUNTRY

REGION


ADRC

REGION

REGPOLIT


ISU_RE G0

REGPOLIT

STATANZ


ERDAT

Date the record was created

EHAU

ERDAT

AEDAT

Last change date

EANL

AEDAT

IS-U/CCS 4.71

Field added

Stock Statistics for Reference Values Technical name: 0UC_ISU_31








No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the reference values to the InfoSource 0UC_ISU_31 via a function module (stock statistics for reference values). During this process, only installation facts from the reference value category are processed. The statistics are written when the installation facts are created or changed. Table ETTIFB is read.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require. A trigger is written for future changes to the reference value (ETTIFB) data. Once the future date is reached, program REUESTEACT processes the trigger and executes the changes. The program adds the updated changes to the statistics. If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the extraction structure. This also applies to user-defined fields. When it has the same name as an existing field it is automatically assigned the value of that


320

10

SAP Online Help

28.01.2004

field. You can add the fields from table ETTIFB to the extract structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all reference values according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields are changed in the extraction structure.

We recommend the initialization of all reference values, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.



Table of Origin


AB


SYST

DATUM

ANLAGE

Installation

ETTIFB

ANLAGE

OPERAND

Operand

ETTIFB

OPERAND

TARIFART

Pay scale type

ETTIFB

TARIFART

KONDIGR

Rate fact group

ETTIFB

KONDIGR

ABRECH

Not relevant for billing

ETTIFB

ABRECH

VTYP

Processing type

ETTIFB

VTYP

HZBAUFRM

Device category description of a heating installation

ETTIFB

HZBAUFRM

AUFLDSTG

Heating installation charging control

ETTIFB

AUFLDSTG

BSSTATUS

Lighting belongs to utilities company

ETTIFB

BSSTATUS

WERT1

Entry value (installed value) of a device

ETTIFB

WERT1

WERT2

Value to be billed

ETTIFB

WERT2

STATANZ


ERDAT

Date the record was added

ETTIFB

ERDAT

Stock Statistics for Devices Technical name: 0UC_ISU_30


320

11

SAP Online Help

28.01.2004


Transaction data




IS-U 4.61 (4.6B)

RemoteCube Compatibility

No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the technical and regional nature of the devices to the InfoSource 0UC_ISU_30 (stock statistics devices). The statistics are written when the device is created or changed. View V_EGER is read. View V_EGER consists of tables EGERS, EQUI, and EGERH. The regional structure data (ADRC, ISU_REG0) is determined using the address of the device location that belongs to the device. Future data is not processed directly. Data in the extractor can only be transferred when the address data of installed devices (address data of the connection object) has been entered in the IS-U system together with the regional structure.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require. If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the extraction structure. This also applies to user-defined fields. When it has the same name as an existing field it is automatically assigned the value of that field. You can add the fields from view V_EGER to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all devices according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields in the extraction structure are changed.

We recommend the initialization of all devices, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.

Fields of Origin in the Extract Structure Field in Extract Structure

Description of Field in the Extract Structure

Table of Origin


BAUJJ

Construction year

EQUI

BAUJJ

BGLBIS

Next replacement year

BGLKENN

Determination of requirements planning/replacement year from certification


320

12

SAP Online Help

28.01.2004

CITY_CODE


ADRC

CITYP_CODE

City district code for city ADRC and street file

CITYP_CODE

COUNTRY

Country key

ADRC

COUNTRY

LAGER

Storage location

EQUI

LAGER

MATNR

Material number

EQUI

MATNR

REGION

Region (state, province, ADRC county)

REGION

REGPOLIT


REGPOLIT

STATANZ


STREETCODE

Street code for city and street file

ADRC

STREETCODE

WERK

Plant

EQUI

WERK

.INCLUDE EGERS

Part of the BW extraction view for IS-U devices (EGERS)

MANDT

Client

EGERS

MANDT

EQUNR

Equipment number

EGERS

EQUNR

LOS

Sample lot

EGERS

LOS

BESITZ

Inspection relevance of a device

EGERS

BESITZ

BGLJAHR

Certification year

EGERS

BGLJAHR

WECHSEL

Advance replacement year

EGERS

WECHSEL

BGLSTAT

Certification status

EGERS

BGLSTAT

KZSTICH

Sample device status

EGERS

KZSTICH

BGLNETZ

Certify installed devices EGERS

BGLNETZ

AB


AB

EHAUISU / ADRSTRTISU / ADRCITY

CITY_CODE

Fixed value

EGERH

Stock Statistics for Device Locations Technical name: 0UC_ISU_28








No


320

13

SAP Online Help

28.01.2004

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the device locations with attributes from PM to the InfoSource 0UC_ISU_28 (stock statistics for device locations). The statistics are written when the device location is created or changed. View V_EGPL is read. View V_EGPL contains the technical location table (IFLOT) and the location and account assignment for the IH object (ILOA). Future data is not processed directly.

If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure of the device location. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields from view E_EGPL to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all device locations according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields in the extraction structure are changed.

We recommend the initialization of all device locations, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.



AB


SWERK

Maintenance plant

ILOA

SWERK

DEVLOC

Device location

IFLOT

TPLNR

LVORM

Deletion indicator

IFLOT

LVORM

STORT

Location of the maintenance object

ILOA

STORT

STATANZ


ERDAT


IFLOT

ERDAT

AEDAT

Last change date

IFLOT

AEDAT


Table of Field in Table Origin of Origin

Changed as of:

Type of Change

IS-U/CCS 4.71

Field added

Is not assigned a value

320

14

SAP Online Help

28.01.2004

Stock Statistics for Business Partners Technical name: 0UC_ISU_22








No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the business partner to the InfoSource 0UC_ISU_22 (stock statistics business partner) via a function module. Only the IS-U Business Partner role is transferred, whereby the table containing IS-U business partner data is processed in the extractor. Central business partner data is not processed and can only be enhanced via the standard user exit for data sources. Note the data sources of the central business partner. An accurate processing of future data does not occur via the trigger. The changes are made by running report BUSPCDACT.

If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure of the IS-U contract partner. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields from table BP: General Data (BUT000) and table IS-U Specific Fields for Business Partner (EKUN) to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all contract partners according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields in the extraction structure are changed.

We recommend the initialization of all contract partners, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.



Table of Origin

Field in Table Changed of Origin as of:

PARTNER

Business partner key

EKUN

BU_PARTNE R

AB


SYST

DATUM


320

Type of Change

15

SAP Online Help

28.01.2004

KTOKLASSE_ GP

Account class

EKUN

KTOKLASSE

TYPE

Business partner category

Dynamic determinatio n

Dynamic determination

KZ_VKONT

Business partner is Dynamic allocated to a contract determinatio account n


RLTYP_CP

Business partner is created as contract partner

Dynamic determinatio n


RLTYP_INST

Business partner is created as installer

BUT000

RLTYP_INST

XSEXM

Selection: Business partner is male

BUT000

XSEXM

XSEXF

Selection: Business partner is female

BUT000

XSEXF

XSEXU

Selection: Gender of business partner not known

BUT000

XSEXU

MARST

Marital status of business partner

BUT000

MARST

JOBGR

Occupation of business partner

BUT000

JOBGR

WAKLASS

Employee classification

EKUN

WAKLASS

NATIO

Name of nationality

BUT000

NATIO

STATANZ


ERDAT


EKUN

ERDAT

AEDAT

Last change date

EKUN

AEDAT

IS-U/CCS 4.71

Field added

Stock Statistics for Partner Contacts Technical name: 0UC_ISU_29








No


320

16

SAP Online Help

28.01.2004

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the business partner contacts to the InfoSource 0UC_ISU_29 (stock statistics for partner contact). As a result, contact classes (information, meter reading, complaints, and so on), contact types (e-mail, letter, telephone, and so on) and further contact attributes can be analyzed. The data source can be used for the Infocube and also for the ODS. This enables you, for example, to analyze individual contacts specifically in BW, though the aggregated data exists in the Infocube. The statistics are written when the contact is created or changed. Table BCONT is read. Future data is not processed directly.

If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure of the contact. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields from table BCONT to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all partner contacts according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs if the contents of one or more fields in the extraction structure are changed.

We recommend the initialization of all partner contacts, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.


Description of Field Table of in Extract Structure Origin


BPCONTACT

Business partner contact

BCONT

BPCONTACT

AB


SYST

DATUM

PCATEGORY

Business partner category of the SAP R/3 System

BCONT

PCATEGORY

RLTYP

BDT: Objects section BCONT

RLTYP

CTYPE

Contact type

BCONT

CTYPE

CCLASS

Contact class

BCONT

CCLASS

ACTIVITY

Contact action

BCONT

ACTIVITY

F_COMING

Contact origin (outbound or inbound)

BCONT

F_COMING

ORIGIN

Technical origin of the business partner

BCONT

ORIGIN


320

Changed as of:

Type of change

17

SAP Online Help

28.01.2004 contact

ADDINFO

Further information

BCONT

ADDINFO

PRIORITY

Contact priority

BCONT

PRIORITY

CUSTINFO

Customer Information

BCONT

CUSTINFO

SPARTE

Division

BCONT

SPARTE

CTDATE

Contact date

BCONT

DATUM

BUKRS

Company code

BCONT

BUKRS

STATANZ

Number in the statistics BCONT

CTDATE_MONTH

CTDATE_MONTH Month in which partner contact took place UPDMOD

BW delta process: Update mode

RODMUPDMOD

ERDAT


BCONT

ERDAT

IS-U/CCS 4.71

Field added

AEDAT

Last change date

BCONT

AEDAT

IS-U/CCS 4.71

Field added

Features of the Extractor The DataSource can not only be used for the cube, but also for an ODS.

Stock Statistics for Premises Technical name: 0UC_ISU_27








No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information and regional data on the premise to the InfoSource 0UC_ISU_27 (stock statistics premise) via a function module. Address data in the extractor can only be transferred when it has been entered in the IS-U system together with the regional structure.


320

18

SAP Online Help

28.01.2004

If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure of the premise. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all premises according to the selection criteria, whereby it only takes into account the current status of the master data.

We recommend the initialization of all premises, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.


Description of Field Table of in Extract Structure Origin


AB


SYST

DATUM

VSTELLE

Premise

EVBS

VSTELLE

LOEVM

Deletion indicator

EVBS

LOEVM

VBSART

Premise type

EVBS

VBSART

ANZPERS

Number of persons

EVBS

ANZPERS

HPTWHNSITZ

Main place of residence

EVBS

HPTWHNSITZ

CITY_CODE

City code for city and ADRL street file

CITY_CODE

CITYP_CODE

City district code for city and street file

ADRL

CITYP_CODE


ADRL

STREETCODE

COUNTRY

Country key

ADRL

COUNTRY

REGION


ADRL

REGION

REGPOLIT


ISU_REG0

REGPOLIT

STATANZ


ERDAT


EVBS

ERDAT

AEDAT

Last change date

EVBS

AEDAT


320

Changed as of:

Type of change

IS-U/CCS 4.71

Field added

19

SAP Online Help

28.01.2004

Stock Statistics for Contracts Technical name: 0UC_ISU_24


Transaction data




IS-U 4.61 (4.6B)


No

Prerequisites The new marketing relevant fields are only available in this DataSource from Release IS-U 4.63 (4.6C) upwards.

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers contract-related information (for example, dunning procedures, installations, rate category) to the InfoSource 0UC_ISU_24 (stock statistics contract). The data from this DataSource is not only read from the master data of the contract (EVER) but also to each utility installation. The utility installation (EANLH) contains mainly information pertaining to settlement methods, for example, rate category, meter reading unit, but also contains voltage level and temperature area. If no installation exists, the installation fields are not filled. The historical data for the installation (EANLH) is determined on the current date, even if the contract has already ended. The address fields (ADRC) are determined from the connection object that belongs to the installation. A trigger is written for future changes to the installation’s historical data. Once the future date is reached, program REUSTACT processes the trigger and makes the changes. The program adds the updated changes to the statistics. If the contract account data changes, all records for the contracts that belong to this contract account are processed. Address data in the extractor can only be transferred when it has been entered in the IS-U system together with the regional structure. The statistics can be used to compare campaigns from Release IS-U 4.63 and CRM 3.0 onwards. The campaign that resulted in the contract is extracted into BW. This enables the analysis, for example, of the number of new contracts to this campaign, enhanced with further attributes from contract, installation and regional structure.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require. If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields into the structure of the contract. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields from the Contract (EVER), Create Historical Part (EANLH), and Contract Account tables to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all contracts according to the selection criteria, whereby it


320

20

SAP Online Help

28.01.2004

only takes into account the current status of the master data. The delta update occurs when one or more of the fields in the extraction structure are changed.

We recommend the initialization of all contracts, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.



Table of Origin


AB


SYST

DATUM

ABLEINH

Meter reading unit

EANLH

ABLEINH

ABLSPERR

Meter reading blocking reason

EANL

ABLSPERR

ABRFREIG

Reason for releasing billing

EVER

ABRFREIG

ABRSPERR

Reason for blocking billing

EVER

ABRSPERR

AKLASSE

Billing class

EANLH

AKLASSE

ANLAGE

Installation

EVER

ANLAGE

ANLART

Installation type

EANL

ANLART

ANLSTAT

Installation status

EANLH

ANLSTAT

AUSZDAT

Move-out date

EVER

AUSZDAT

BEZUG

Reference

EANL

BEZUG

BILLMETHOD

Billing method

EVER

BILLMETHOD

BRANCHE

Industry

EANLH

BRANCHE

BUKRS

Company code

FKKVKP

BUKRS

CAMPAIGN

IS-U: Marketing campaign

EVERH

ISU_MARKETING_CA MPAIGN

CANCREASON_NEW

Reason for cancelling contract

EVER

ECRMT_SRV_CANCEL _REASON

CITY_CODE


ADRC

CITY_CODE

CITYP_CODE


CITYP_CODE

CONTRACTCLASS

Contract class

EVER

CONTRACTCLASS

COUNTRY

Country key

ADRC

COUNTRY

EIGENVERBR

Plant or company consumption

EVER

EIGENVERBR

EINZDAT

Move-in date

EVER

EINZDAT

ERDAT

Month in which the SYST record of the transaction statistics was generated

DATUM (6)

FDGRP

Planning group

FDGRP


FKKVKP

320

21

SAP Online Help

28.01.2004

IKEY

Interest key

FKKVKP

IKEY

KOFIZ

Account determination ID for utilities industry contracts

FKKVKP

KOFIZ

KOFIZ_SD

Account determination FKKVKP ID for contract accounts

KOFIZ_SD

KTOKLASSE

Account class

FKKVKP

KTOKLASSE

KZ_ABVTY

Outgoing bank details available

dynamic determination


KZ_ACT

Indicator for budget billing plan control FM



KZ_EBVTY

Ingoing bank details available



KZ_PERSNR

Personnel number allocated



LOEVM

Deletion indicator

FKKVKP

LOEVM

MAHNV

Dunning procedure

FKKVKP

MAHNV

MANABR

Manually bill contract

FKKVKP

MANABR

MANSP

Dunning block reason

DFKKLOCKS

MANSP

MGRUP

Dunning grouping type

FKKVKP

MGRUP

OPBUK

Responsible company code for open item accounting processing

FKKVKP

OPBUK

PORTION

Portion

EVER / TE422

PORTION

REGION

Region (state, province, EVER county)

REGION

REGPOLIT


ISU_REG0

REGPOLIT

SALESDOCUMENT

Sales and distribution document number

EVER

SALESDOCUMENT

SALESEMPLOYEE

Sales employee

EVER

SALESEMPLOYEE

SALESPARTNER

Sales partner

EVER

SALESPARTNER

SERVICEID

Service provider (old)

EVER

SERVICEID

SPARTE

Division

EANL

SPARTE

SPEBENE

Voltage level

EANL

SPEBENE

SRVPRVREF

Reference number of service provider

EVER

SRVPRVREF

STATANZ


STREETCODE


ADRC

STREETCODE

TARIFTYP

Rate category

EANLH

TARIFTYP

TEMP_AREA

Temperature area

EANLH

TEMP_AREA

VERTRAG

Contract

EVER

VERTRAG


320

22

SAP Online Help

28.01.2004

VERTYP

Sales agent type for clearing entry

FKKVKP

VERTYP

VKONT

Contract account number

FKKVKP

VKONT

VKTYP

Contract account category

FKKVK

VKTYP

ZAHLKOND

Payment term

FKKVKP

ZAHLKOND

Stock Statistics for Contract Accounts Technical name: 0UC_ISU_23








No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the contract account to the InfoSource 0UC_ISU_23 (stock statistics for contract account). The statistics are written when the contract account is created or changed. Table FKKVKP is read.

If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields into the structure of the contract account. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. You can add the fields from table FKKVKP to the extraction structure without making any modifications.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run reads all contract accounts according to the selection criteria, whereby it only takes into account the current status of the master data. The delta update occurs when one or more of the fields in the extraction structure are changed.

We recommend the initialization of all contract accounts, even if the enhanced selection area does not yet contain any stock. The new stock is automatically entered by delta processing.


320

23

SAP Online Help

28.01.2004

Origin Fields in the Extract Structure Field in Extract Description of Field Structure in Extract Structure

Table of Origin

Field in Table Valid from: of Origin

FKKVKP

VKONT

AB


VKONT


OPBUK

Responsible company code for open item accounting processing

VKTYP


FKKVK

VKTYP

VKBBZ

Relationship of business partner to contract account

FKKVKP

VKBBZ

KTOKLASSE

Account class

FKKVKP

KTOKLASSE

FDGRP

Planning group

FKKVKP

FDGRP

VERTYP


FKKVKP

VERTYP

KOFIZ_SD

Account determination FKKVKP ID for contract accounts

KOFIZ_SD

ZAHLKOND

Payment term

FKKVKP

ZAHLKOND

IKEY

Interest key

FKKVKP

IKEY

MGRUP

Dunning grouping type FKKVKP

MGRUP

MAHNV

Dunning procedure

FKKVKP

MAHNV

MANSP

Dunning block reason

DFKKLOCK MANSP S

KZ_EBVTY

Ingoing bank details available

dynamische dynamische Ermittlung Ermittlung

KZ_ABVTY

Outgoing bank details available

dynamische dynamische Ermittlung Ermittlung

LOEVM

Indicator: Set contract account for deletion

FKKVKP

LOEVM

STATANZ


ERDAT


FKKVKP

ERDAT

AEDAT

Last change date

FKKVKP

AEDAT

Type of change

IS-U/CCS 4.71

Field added

IS-U/CCS 4.71

Field added

Sales Statistics Technical name: 0UC_SALES_STATS_01


320

24

SAP Online Help

28.01.2004








No

Prerequisites For optimal use of the DataSource, we recommend you check the IMG for BW from Plug-in PI2001.1 and mySAP Utilities 4.63 upwards. Using application-specific settings, you can find notes on the Utilities Industry and Sales Statistics. You can find further information releases prior to mySAP Utilities 4.63 and Plug-in P12001.1 in SAPNet under the alias Utilities. Due to the large amounts of data involved, it is important that OLTP Customizing for the sales statistics is completed before the first productive loading process takes place and that the changes are directly implemented.

In addition to this, the DataSource 0UC_SALES_STATS_02 is available from mySAP Utilities IS-U 4.62 upwards. You can only use one of the two DataSources in productive operation. Please see the documentation for the DataSource 0UC_SALES_STATS_02. As a rule, the other DataSource should only be implemented if you experience problems with the load time. It is not as user friendly but produces the same results.

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information to the InfoSource 0UC_ISU_01 (sales statistics). This applies to regional information (for example, country, city), contract data (for example, division, business partner) and invoicing data entered in the document line items (for example, rate). Address data in the extractor can only be transferred when it has been entered in the IS-U system together with the regional structure.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require. If the fields of the DataSource are not sufficient, you can use the customer append structure to insert additional fields in the structure of the installation, the installation contract and the billing documents. This also applies to a user-defined field. When it has the same name as an existing field it is automatically assigned the value of the field. Additionally, you are able to access the Exit BWESTA01 that enables you to carry out modifications whilst data records are being formatted. This is a more high-performance enhancement than the standard function module for data sources.

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The Full update is supported. You must only use the full update, however, to extract documents that contain one or more of the following characteristics:


320

25

SAP Online Help •

28.01.2004

The documents were created prior to mySAP Utilities IS-U 4.61

•

The documents were created prior to connection to a BW system.

•

The documents have already been unloaded into BW. The user is responsible for any inconsistencies

When you extract the documents for the first time, select the complete posting period. We recommend that you carry out initialization and Full upload in a number of steps in order to create smaller packages. In order to improve the performance, select an update via the PSA. The data is extracted in accordance with the selection criteria. In this case, the posting date of the documents is used as the selection criteria. Initialize all future posting dates, even if the enhanced selection area does not yet contain any documents. The new documents are automatically entered by delta processing. Carry out delta processing at regular intervals. We recommend that large utilities companies carry out delta processing on a daily basis. Only documents with closed reconciliation keys can be processed. Upload Transactions in Detail Full Upload: All documents with a closed a reconciliation key are extracted in accordance with the selection. Use the full upload to extract all existing documents after connection of the DataSource. Documents with an open reconciliation key are saved in index table DBESTA_BWPROT for later processing. Initial Upload: All closed reconciliation keys in index table DBESTA_BWPROT are processed according to the initial selection and the associated documents are extracted. You should perform the initialization after the full upload, using the same selection. The initial run only extracts data if in the mean time associated reconciliation keys were closed between the full and initial upload, or if there are new documents. Delta Upload: All closed reconciliation keys are processed in accordance with the initial selections and the corresponding documents are extracted. This normally concerns new documents in productive operation.

Origin Fields in the Extract Structure The Includes BWESTA_ERCH for the document header, BWESTA_ERCHZ for the document line items and BWESTA_ADD for additional information have been drawn out of the source system to provide extra information. Field in Extract Structure

Description of Field in Table of Field in Table of Extract Structure Origin Origin

BUDAT

Posting date in the document

ERDK

BUDAT

FIKEY

Reconciliation key for general ledger accounting

ERDK

FIKEY

XCANC

Reversal transaction: ERDK document was reversed

.INCLUDE BWESTA ERCH

BW-IS-U S l t ti ti


320

Changed as of:

Type of Change

STOKZ

26

SAP Online Help

28.01.2004

BWESTA_ERCH

Sales statistics: Document header transfer structure

BUKRS

Company code

ERCH

BUKRS

SPARTE

Division

ERCH

SPARTE

GPARTNER

Business partner number

ERCH

GPARTNER

VKONT


ERCH

VKONT

VERTRAG

Contract

ERCH

VERTRAG

ABWVK

Different contract account for collective bills

ERCH

ABWVK

ABRVORG

Billing procedure

ERCH

ABRVORG

APPLK

Application area

HVORG

Main transaction of line item

ERCH

HVORG

KOFIZ


ERCH

KOFIZ

PORTION

Portion

ERCH

PORTION

KONZVER

Franchise contract

ERCH

KONZVER

ABLEINH

Meter reading unit

ERCH

ABLEINH

KTOKLASSE

Account class

ERCH

KTOKLASSE

ZUORDDAA

Allocation date for billing

ERCH

ZUORDDAA

THGDAT

Allocation date for gas billing

ERCH

THGDAT

ANZTAGE

Number of billed contract days

ANZVERTR

Number of billed contracts (proportionatly per month)

CNTINVDOC

Number of billing documents

IS-U/CCS 4.71

Field added

CNTBILLDOC

Number of settlement documents

IS-U/CCS 4.71

Field added

BUPLA

Business place

.INCLUDE BWESTA_ERCHZ

BW-IS-U Sales statistics: Document line items transfer structure

BELZART

Fixed value R

ERCHZ

BUPLA

Line item type

ERCHZ

BELZART

AKLASSE

Billing class

ERCHZ

AKLASSE

BRANCHE

Industry

ERCHZ

BRANCHE


320

27

SAP Online Help

28.01.2004

TVORG

Subtransaction of line item

ERCHZ

TVORG

SAISON

Season

ERCHZ

SAISON

FRAN_TYPE

Franchise fee category

ERCHZ

FRAN_TYPE

KONZIGR

Franchise fee group

ERCHZ

KONZIGR

OUCONTRACT

Outline contract for individual contract

ERCHZ

OUCONTRACT

TARIFTYP

Rate category

ERCHZ

TARIFTYP

STATTART

Rate type for statistical analysis

ERCHZ

STATTART

TARIFNR

Rate key

ERCHZ

TARIFNR

KONDIGR

Rate fact group

ERCHZ

KONDIGR

STTARIF

Statistical rate

ERCHZ

STTARIF

TEMP_AREA

Temperature area

ERCHZ

TEMP_AREA

DRCKSTUF

Gas pressure level

ERCHZ

DRCKSTUF

VBRMONAT

Consumption month

ERCHZ

VBRMONAT

AB



BIS

Date until which a time slice is valid


DIFFKZ

Indicator: Difference line item for discount statistics

ERCHZ

DIFFKZ

STGRQNT

Statistics group: quantity

ERCHZ

STGRQNT

STGRAMT

Statistics group: amount ERCHZ

STGRAMT

ARTMENGE

Classification of billed quantities for statistics

ERCHZ

ARTMENGE

GSBER

Business area

ERCHZ

GSBER

KOSTL

Cost center

ERCHZ

KOSTL

KOKRS

Controlling area

ERCHZ

KOKRS

PRCTR

Profit center

ERCHZ

PRCTR

PS_PSP_PNR

Project structure plan element (PSP element)

ERCHZ

PS_PSP_PNR

AUFNR

Order number

ERCHZ

AUFNR

WAERS

Currency key

ERCHZ

TWAERS

MASSBILL

Billing unit of measurement

ERCHZ

MASSBILL

BETRAG

Net amount Bill line

ERCHZ

NETTOBTR

MENGE

Billing quantity: energy

ERCHZ

I_ABRMENGE

.INCLUDE BWESTA_ADD

BW-IS-U Sales statistics: transfer structure of


320

IS-U/CCS 4.71

Field added

28

SAP Online Help

28.01.2004 additional field

ANLAGE

Installation

EANL

ANLAGE

ANLART

Installation type

EANL

ANLART

SPEBENE

Voltage level

EANL

SPEBENE

EIGENVERBR


EANL

EIGENVERBR

STAGRUVER

Statistics group for the contract

EVER

STAGRUVER

STAFO

Update group for statistics update

ERCHZ

STAFO

CITY_CODE


ADRC

CITY_CODE

CITYP_CODE


CITYP_CODE

STREETCODE


ADRC

STREETCODE

COUNTRY

Country key

ADRC

COUNTRY

REGION


REGION

REGPOLIT


ADRC

REGPOLIT

REGIOGROUP

Regional structure grouping

EHAU

REGIOGROUP

SALESEMPLOYEE Sales employee

EVER

SALESEMPLOYEE

SALESPARTNER

EVER

SALESPARTNER

SALESDOCUMENT Sales and distribution document number

EVER

SALESDOCUMENT

CONTRACTCLASS Contract class

EVER

CONTRACTCLASS

RULEGR

Rule group for outline contracts

EVER

RULEGR

INCLUDE BWESTA_ERDL

BW-IS-U Sales statistics: Print document line items transfer structure

TXJCD

Jurisdiction for tax calculation – tax jurisdiction code

ERDZ

TXJCD

MWSKZ

Tax code

ERDZ

MWSKZ

STPRZ

Tax rate in output format

ERDZ

STPRZ

SBASW

Steuerpfl. Amount subject to tax in transaction currency (tax base amount)

ERDZ

SBASW

SBETW

Tax amount in transaction currency

ERDZ

SBETW

Sales partner


320

IS-U/CCS 4.71

Field added

29

SAP Online Help

28.01.2004 (+/-)

TXDAT

Date for defining tax rates

ERDZ

TAXDATE

PERIOD

Fiscal year/period


PERIV

Fiscal year variant


Features of the Extractor As of Release IS-U/CCS 4.71, the DataSource can also be used for the ODS. However, given the large amounts of data that result, only one ODS should be created with definition INSERT (no updating of existing records).

Parallel Extraction of Sales Statistics Technical name: 0UC_SALES_STATS_02 also available from mySAP Utilities 4.61 upwards.








No

Prerequisites Please read the documentation on DataSource 0UC_SALES_STATS_01. The following text only describes the loading process and the changes in operation. The fields of DataSource 0UC_SALES_STATS_01 remain the same. Only one of the DataSources can be used. A conversion of the DataSource is supported.

Use This DataSource transfers information to the InfoSource 0UC_ISU_01 (sales statistics).

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. Full Upload: Use the full update to extract documents that:

•

•

were created prior to mySAP Utilities 4.61

•

were created before a BW system was connected have already been unloaded into BW. The user is responsible for any inconsistencies

When you extract the documents for the first time, select the complete period. The new processing is relevant as of 4.61 AOSP26; 4.62 AOSP 16; 4.63 AOSP 6. Upload Transactions in Detail Full Upload:


320

30

SAP Online Help

28.01.2004

All documents are saved in accordance with the selection in index table DBWESTA_BWPROT to be later processed in parallel. Note that no data is extracted to BW. You can use the full upload to process all documents since connection of the DataSource. Initial Upload: Initialization takes place once in accordance with the selection. Note that no data is extracted to BW. Execute the full upload and initial upload concurrently and over the same period (including future). Delta Upload: The data from the delta queue is transferred. See OSS note 420008 for further information. You must start a mass run in OLTP, before carrying out the Delta upload. ...

1. Start the transaction EBW_DQ_SS (in the menu from mySAP Utilities 4.64 upwards) 2. Enter the required identification dates in this transaction. 3. Start the mass runs or use the planning options. We recommend that large utility companies carry out daily processing after mass runs for invoicing. This transaction processes all new documents in parallel and writes data records in the delta queue. 4. Initiate the delta upload from BW when the last job has been completed. The delta upload can also be initiated before the next mass run starts. Only documents with closed reconciliation keys are processed.

Transaction Statistics: Billing Technical name: 0UC_ISU_17


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the manual billing transaction to the InfoSource 0UC_ISU_17 (transaction statistics billing). Manual billing cannot be replaced by automatic transactions and represents the work of qualified employees. The statistics are written when the manual billing documents are released. The billing documents all have billing transaction “06”. The extraction structure fields are provided from the billing document header (ERCH). The address data in the extractor can only be transferred when the address data of each connection object has been entered in the IS-U system together with the regional structure.

It is not possible to add other fields to the statistics using user exits.


320

31

SAP Online Help

28.01.2004

Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run does not transfer any data because transactions and processes are not available as master data. Initialization, therefore, only records relevant transactions.

We recommend you carry out initialization as early as possible - even when the delta upload is going to be carried out at a later date. In general, transaction statistics are manual transactions that do not monitor mass runs. As a result, there will be few records for the delta upload.



Table of Origin


BUKRS*

Company code

EVER

BUKRS

SPARTE*

Division

EVER

SPARTE

EIGENVERBR*


EVER

EIGENVERBR

PORTION*

Portion

TE422

PORTION

TARIFTYP*

Rate category

ETTA

TARIFTYP

AKLASSE*

Billing class

ETRF

AKLASSE

KOFIZ*


EVER

KOFIZ

ABRVORG*

Billing procedure

ETRG

ABRVORG

MANOUTSORT

Reason for manual outsorting in billing

EVER

MANOUTSORT

VALIDATION

Name of billing validation

ERCHO

VALIDATION

ACTORID

Agent ID in organizational management

HRS1203

OBJECTID

CITY_CODE


ARDC

CITY_CODE

CITYP_CODE

City district code for city ARDC and street file

CITYP_CODE

STREETCODE


ARDC

STREETCODE

COUNTRY

Country key

ARDC

COUNTRY

REGION

Region (state, province, ARDC county)

REGION

REGPOLIT


REGPOLIT

ANZ_CRE

Number of credit memos

ANZ_DEB

Number of receivables


320

ARDC

32

SAP Online Help

28.01.2004

ANZ_REV

Number of reversals

ANZ_REL

Number of releases

ERDAT

Month in which the record of the transaction statistics was generated

* From billing document header (ERCH)

Transaction Statistics: Certifications Technical name: 0UC_ISU_19


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on certification to the InfoSource 0UC_ISU_19 (stock statistics for certification). The number of certifications executed using transaction EG97 is included in the statistics.


We recommend you carry out initialization as early as possible - even when the delta upload is going to be carried out at a later date. In general, transaction statistics are manual transactions that do not monitor mass runs. As a result, there will be few records for the delta upload. It is not possible to add other fields to the statistics using user exits.



BGLJAHR

Certification year

GERTYP

Device category

STATANZ


ERDAT



Table of Origin

Field in Table of Origin Entry on screen

EQUI

320

MATRN DATUM (6)

33

SAP Online Help

28.01.2004

Transaction Statistics: Billing-Related Installation/ Removal Technical name: 0UC_ISU_15


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. The DataSource transfers information on billing related device installation and removal to the InfoSource 0UC_ISU_15 (transaction statistics: billing related device installation EG34 and removal EG35). During billing related device installation, the device and rate information is allocated to a utility installation and can be used in corresponding calculation rules. . It is possible to evaluate the number of device installations and removals for a specific device. Address data can only be transferred when it has been entered in the IS-U system together with the regional structure.

In order to avoid unnecessary data import and extraction, you can hide any fields in the DataSource that you do not require.






AB

Date from which a time li i lid


320

Table of Origin


34

SAP Online Help

28.01.2004 slice is valid

ACTORID


ANZ_AUSB

Number of device removals

ANZ_EINB

Number of device installations

BAUJJ

HRS1203

OBJECTID

Construction year

EQUI

BAUJJ

BAUKLAS

Construction class

ETYP

BAUKLAS

BGLJAHR

Certification year

EGERS

BGLJAHR

CITY_CODE


ADRC

CITY_CODE

CITYP_CODE


CITYP_CODE

COUNTRY

Country key

ADRC

COUNTRY

EQUNR

Equipment number

V_EGER

EQUNR

ERDAT


DATUM (6)

FUNKLAS

Function class

ETYP

FUNKLAS

MATNR

Material number

V_EGER

MATNR

REGION


REGION

REGPOLIT



REGPOLIT

STATANZ


STREETCODE


ADRC

STREETCODE

Transaction Statistics: Move-in/out Technical name: 0UC_ISU_12








No


320

35

SAP Online Help

28.01.2004

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. The DataSource transfers move-in/out information to the InfoSource 0UC_ISU_12 (sales statistics: move-in/out). This covers both move-ins and move-outs. For the move-in transaction, you execute the activities required for registering and supplying the customer with utilities services. You create business master data or change data that is already available. For the move-out transaction, you execute the activities required for cancelling the customer’s supply of utilities services. You make changes to the business partner master data that result from a move-out. A record is written in the statistics each time a move-in is created or reversed and each time a move-out is created or reversed. If the move-in date changes, the move-in record is cancelled by a reversal record and a new movein record with the new date is written.


Delta Update After the initial run and initialization of the delta method, you can use this DataSource for the delta upload. The initial run does not transfer any data because transactions and processes are not available as master data. Initialization, therefore, only records relevant transactions. The transaction statistic is posted when the move-in date is created, changed or reversed. If only attributes of the move-in are chnaged, no data is posted to SAP BW. The historical installation data is determined on the move-in or move-out date. The transaction statistic is also posted if the move-in is created in the backgroiund (by BAPI, for example), but not during migration. In this case, a statistic updated must be activated separately in the migration workbench.




Table of Origin


SPARTE**

Division

EANL

SPARTE

EIGENVERBR**


EVER

EIGENVERBR

TARIFTYP**

Rate category

EANLH

TARIFTYP

AKLASSE**

Billing class

EANLH

AKLASSE

KOFIZ**


EVER

KOFIZ

ACTORID


SWHACTOR

OBJID


320

36

SAP Online Help

28.01.2004

CITY_CODE


ADRC

CITYP_CODE


CITYP_CODE

STREETCODE


ADRC

STREETCODE

COUNTRY

Country key

ADRC

COUNTRY

REGION


REGION

REGPOLIT


REGPOLIT

ANZ_EINZ*

Number of move-ins

ANZ_AUSZ*

Number of move-outs

ANZ_EINZ_STO*

Number of reversed move-ins

ANZ_AUSZ_STO*

Number of reversed move-outs

ERDAT


ISU_REG0

CITY_CODE

DATUM

* One of these four fields has the value 1, all others have the value 0. ** From the move-in document

Transaction Statistics: Invoicing Technical name: 0UC_ISU_16


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on single invoicing to the InfoSource 0UC_ISU_16 (transaction statistics single invoicing). Single invoicing is a manual transaction and cannot be created in mass runs. The transactions statistics count the documents.All tables of origin are available for update via invoicing.You must use the sales statistics if you also want to determine the documents of the mass runs. Address data can only be transferred when it has been entered in the IS-U system together with the regional structure.


320

37

SAP Online Help

28.01.2004

The customer comes to the customer office with a meter reading result and asks for a bill. The bill is cancelled due to incorrect values and is created again with the correct values. In this scenario, two records are transferred to the extractor. The first contains the cancellation information and the second the new invoicing.






Table of Origin


ACTORID


HRS1203

OBJECTID

VKTYP


FKKVK

VKTYP

KTOKLASSE

Account class

FKKVKP

KTOKL

ERGRD

Reason for creating the print document

ERDK

ERGRD

VERART

Settlement type for clearing entry

ERDK

VERART

VERTYP


FKKVKP

VERTYP

MANOUTSORT

Reason for manual outsorting in billing

ERDO

MANOUTS_IN

VALIDATION

Name of billing validation

ERDO

VALIDAT_IN

CITY_CODE


ADRC

CITY_CODE

CITYP_CODE


CITYP_CODE

STREETCODE


ADRC

STREETCODE

COUNTRY

Country key

ADRC

COUNTRY

REGION



320

REGION

38

SAP Online Help

28.01.2004

REGPOLIT


ADRC

ANZ_CRE

Number of credit memos

ANZ_DEB

Number of receivables

ANZ_REV

Number of reversals

ANZ_OUT

Number of outsortings

ANZ_REL

Number of releases

ERDAT

Month in which the ERDK record of the transaction statistics was generated

REGPOLIT

ERDAT

Transaction Statistics: Devices Technical name: 0UC_ISU_18


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on device transactions to the InfoSource 0UC_ISU_18 (transaction statistics: device transactions). Typical transactions include device replacement, installation, removal, and the reversal of incorrect transactions. The equipment number is not part of the extraction structure. Address data can only be transferred when it has been entered in the IS-U system together with the regional structure.




320

39

SAP Online Help

28.01.2004




Table of Origin


ACTORID


HRS1203

OBJECTID

ANZ_AUSB

Number of device removals

ANZ_EINB

Number of device installations

ANZ_STO

Number of reversals

ANZ_UMB

Number of device modifications in the network

ANZ_WCHS_AUSB

Number of removed device replacements

ANZ_WCHS_EINB

Number of replacements: installed devices

BAUKLAS

Construction class

ETYP

BAUKLAS

CITY_CODE


ADRC

CITY_CODE

CITYP_CODE


CITYP_CODE

COUNTRY

Country key

ADRC

COUNTRY

ERDAT


DATUM (6)

FUNKLAS

Function class

ETYP

FUNKLAS

GERTYP

Device category

EQUI

MATNR

GERWECHS

Activity reason

EGERS

UMBAUGR

REGION


REGION

REGPOLIT



REGPOLIT

SPARTE

Division

EQUI

SPARTE

STREETCODE


ADRC

STREETCODE

ZWGRUPPE

Register group

EGERH

ZWGRUPPE


320

40

SAP Online Help

28.01.2004

Transaction Statistics for Sample Lot Procedure Technical name: 0UC_ISU_20


Transaction data






No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of the data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on the sample lot procedure and the resulting samples to the InfoSource 0UC_ISU_20 (transaction statistics for sample lot procedure). data is only saved by transaction EG81 (Change Lot).






Table of Origin


SPARTE

Division

TE271

SPARTE

LOSAMT

Lot category

TE271

LOSAMT

LOSANZG

Size of sample lot

TE271

LOSANZG

LOSFAELL

Next due year of sample lot

TE271

LOSFAELL

VERFAHREN

Single sample drawing

TE271

VERFAHREN

EMESSWERK

Meters with electronic registers only

TE271

EMESSWERK

STATANZ


ERDAT

Month in which the SYST record of the transaction


320

DATUM (6)

41

SAP Online Help

28.01.2004 statistics was generated

Transaction Statistics: Supply Disconnection Technical name: 0UC_ISU_14


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on installation disconnections to the InfoSource 0UC_ISU_14 (transaction statistics: installation disconnection). Each time the installation is changed (ES31), the system checks whether the status of the installation has changed to “Disconnected”. In this case, the statistics are changed. The address of the connection object is determined. A disconnection is a temporary interruption in the customer’s supply. A meter removal does not take place. This is due to the following reasons, for example: •

Introduction of a collection procedure for outstanding payment

•

Technical disconnection due to request of utilities company or customer

Data in the extractor can only be transferred when the address data has been entered in the IS-U system together with the regional structure.






Table of Origin


ERDAT

Month in which the d f th t ti

SYST

DATUM (6)


320

42

SAP Online Help

28.01.2004 record of the transaction statistics was generated

SPGRUND

Reason for disconnection

EDISCDDC

DISCREASON

ACTORID


HRS1203

OBJECTID

CITY_CODE


ADRC

CITY_CODE

CITYP_CODE


CITYP_CODE

STREETCODE


ADRC

STREETCODE

COUNTRY

Country key

ADRC

COUNTRY

REGION


STATANZ


REGPOLIT


ISU_REG0

REGION

REGPOLIT

Transaction Statistics: Rate Maintenance Technical name: 0UC_ISU_13


Transaction data




IS-U 4.61 (4.6B)


No

Use You can select the individual InfoObjects to be used from the characteristics and key figures in the DataSource. As a result, the DataSource provides a pool from which you can compose the InfoSources. Therefore, the DataSource has a far more wide ranging content than the InfoSources. You can determine the level of detail of data in the InfoCube and control performance by defining an InfoSource. This DataSource transfers information on rate maintenance to the InfoSource 0UC_ISU_13 (transaction statistics: rate maintenance). Rate maintenance enables you change settlement relevant data of an individual utility installation or of customer installations grouped together in one contract account. The statistics are written when the data from the rate maintenance is changed using transaction EC30. Address data in the extractor can only be transferred when it has been entered in the IS-U system together with the regional structure.


320

43

SAP Online Help

28.01.2004






Table of Origin


SPARTE*

Division

EVER

SPARTE

EIGENVERBR*


EVER

EIGENVERBR

TARIFTYP*

Rate category

ETTA

TARIFTYP

AKLASSE*

Billing class

ETRF

AKLASSE

KOFIZ*


EVER

KOFIZ

ACTORID


HRS1203

OBJECTID

CITY_CODE


DARC

CITY_CODE

CITYP_CODE

City district code for city DARC and street file

CITYP_CODE

STREETCODE


DARC

STREETCODE

COUNTRY

Country key

DARC

COUNTRY

REGION

Region (state, province, DARC county)

REGION

REGPOLIT


REGPOLIT

STATANZ


ERDAT

Month in which the record of the transaction statistics was generated

DARC

* Data from rate maintenance


320

44

SAP Online Help

28.01.2004

IS-U Disconnection Document Data Technical name: 0UC_ISU_32


Transaction data




IS-U 4.64 (4.6C)

Available from Plug-In Release

DataSource is shipped with the OLTP release


No

Prerequisites This DataSource can be used at any time in productive operations. However, we recommend that you use the full load for test purposes only. In productive operations, use the initial and delta loads. The DataSource cannot be used for InfoCube updates- it can only be used for the ODS object.

Use This DataSource transfers information to the Disconnection/Reconnection InfoSource (0UC_ISU_32). Information on Disconnections in the Utilities Industry (IS-U) Disconnection documents can be created in IS-U without being immediately followed by a disconnection. However, after a disconnection document is created a disconnection usually follows. This is generally followed by a reconnection. The extractor transfers disconnection document header and item data. Only document that have the status Disconnected are extracted. Reconnections are always extracted together with the disconnection date and reconnection. During the initial download, historical changes are not extracted. Instead, the current status at the point of initialization is extracted. Information on the Extractor The COUNTER field is a meter for the number of disconnection objects (business partner, installations, devices and so on) contained in a disconnection action of the respective disconnection document. From a business view, several disconnections in one disconnection action should count as one disconnection. Therefore, the meter can ahve values between 0.0 <= COUNTER <= 1.0. Rounding differences are settled in the first entry for the disconnection action.

Delta Update Changes in the disconnection documents (including reversals) are- if they are in the initial selection- written to the delta queue. The changes are extracted to BW using a delta request.



320

45

SAP Online Help

28.01.2004



Table of Origin


DISCNO*

Disconnection document number

EDISCOBJH

DISCNO

DISCACT_BEGIN*

Disconnection action that led to the creation of the period

EDISCOBJH

DISCACT_BEGIN

DISCOBJ*

Disconnection object number

EDISCOBJH

DISCOBJ

AB*

Date from which a disconnection is valid

EDISCOBJH

AB

BIS*

Date until which a disconnection is valid

EDISCOBJH

BIS

ANLAGE**

Installation

EDISCOBJ

ANLAGE

EQUINR**

Equipment number

EGER

EQUNR

DISCOBJTYP**

Disconnection object category

EDISCOBJ

DISCOBJTYP

DISCREASON**

Reason for disconnection

EDISCDOC

DISCREASON

DISCPROCV**

Processing variant for EDISCDOC disconnection/reconnect ion

DISCPROCV

REFOBJTYPE**

Reference object for disconnection document: category

EDISCDOC

REFOBJTYPE

PARTNER


FKKVKP

GPART

VKONT


FKKVKP

VKONT

CONTRACT

Current contact for installation

EVER

VERTRAG

CONNOBJ

Connection object

EHAU

HAUS

PREMISE

Premise

EVBS

VSTELLE

INSTLN

Installation

EANL

ANLAGE

DEVICE

Device

EGER

EQUNR

LADEMODUS

Indicator

COUNTER


RECORDMODE

Indicator

* Disconnection header ** Disconnection item

Features of Extractor The extractor can not be used to directly update data to the InfoCube.


320

46

SAP Online Help

28.01.2004

IS-U Contract: Non-Time-Based Part Technical name: 0UCCONTRACT_ATTR


Attributes (Master Data)




IS-U 4.63 (4.6C)


No

Use This DataSource extracts the non-time-based data of the IS-U utility contract This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.

Delta Update ALE update pointer



Table of Origin


VERTRAG

Contract

EVER

VERTRAG

VKONTO


EVER

VKONTO

ANLAGE

Installation number

EVER

ANLAGE

AUSZDAT

Move-out date

EVER

AUSZDAT

EINZDAT

Move-in date

EVER

EINZDAT

BUKRS

Company code

EVER

BUKRS

SPARTE

Division

EVER

SPARTE

BEZUG

Reference

EVER

BEZUG

EIGENVERBR


EVER

EIGENVERBR

ABRFREIG

Billing release reason

EVER

ABRFREIG

ABRSPERR

Billing blocking reason

EVER

ABRSPERR

CONTRACTCLASS

Contract class

EVER

CONTRACTCLASS

LOEVM

Deletion indicator

EVER

LOEVM

IS-U Contract: Time-Based Part Technical name: 0UCCONTRACTH_ATTR




320

47

SAP Online Help

28.01.2004




IS-U 4.63 (4.6C)


No

Use This DataSource extracts the time-based data of the IS-U utility contract. This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


VERTRAG

Contract

EVERH

VERTRAG

NUM

Sequence number

EVERH

NUM

BIS


EVERH

BIS

AB


EVERH

AB

ANLAGE

Installation number

EVERH

ANLAGE

CAMPAIGN

CRM marketing element EVERH

CAMPAIGN

CAMPAIGN_TO

Individual to-date for the EVERH valuation period of the CRM marketing element

CAMPAIGN_TO

PRODUCT_GUID

GUID of CRM product

EVERH

PRODUCT_GUID

PRODUCT

CRM Product ID

EVERH

PRODUCT

CONTRACTHEAD

GUID of CRM product (head)

EVERH

CONTRACTHEAD

CONTRACTPOS

GUID of CRM contract (position)

EVERH

CONTRACTPOS

LOEVM

Deletion indicator

EVERH

LOEVM

IS-U Installation: Non-Time-Based Part Technical name: 0UCINSTALLA_ATTR




Utilities Industry


IS-U 4.63 (4.6C)


No


320

48

SAP Online Help

28.01.2004

Use This DataSource extracts the non-time-based data of the IS-U utility installation. This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


ANLAGE

Installation number

EANL

ANLAGE

SPARTE

Division

EANL

SPARTE

ANLART

Installation type

EANL

ANLART

VSTELLE

Premise

EANL

VSTELLE

BEZUG

Reference

EANL

BEZUG

LOEVM

Deletion indicator

EANL

LOEVM

IS-U Installation: Time-Based Part Technical name: 0UCINSTALLAH_ATTR






IS-U 4.63 (4.6C)


No

Use This DataSource extracts the time-based data of the IS-U utility installation. This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


ANLAGE

Installation number

EANLH

ANLAGE

BIS


EANLH

BIS

AB


EANLH

AB


320

49

SAP Online Help

28.01.2004

BRANCHE

Industry

EANLH

BRANCHE

AKLASSE

Billing class

EANLH

AKLASSE

TARIFTYP

Rate category

EANLH

TARIFTYP

IS-U: Premise Technical name: 0UCPREMISE_ATTR






IS-U 4.63 (4.6C)


No

Use This DataSource extracts the data of IS-U premise. This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


VSTELLE

Premise

EVBS

VSTELLE

ANZPERS

Number of people

EVBS

ANZPERS

VBSART

Premise type

EVBS

VBSART

HAUS

Connection object

EVBS

HAUS

LOEVM

Deletion indicator

EVBS

LOEVM

IS-U Connection Object (with service address) Technical name: 0UC_CONNOBJ_ATTR






IS-U 4.63 (4.6C)


No


320

50

SAP Online Help

28.01.2004

Use This DataSource extracts the data and addresses of the IS-U connection object. This data will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


HAUS

Connection object

EHAUISU

HAUS

CITY_CODE


ADRC

CITY_CODE

COUNTRY

Country key

ADRC

COUNTRY

STREETCODE


ADRC

STREETCODE

POSTALCODE

Postal code

ADRC

POSTALCODE

REGION


REGION

REGIO_GRP


EHAUISU

REGIO_GRP

REGPOLIT


EHAUISU

REGPOLIT

CRM_GUID

CRM GUID of connection object

EHAUISU

CRM_GUID

IS-U Partner-Based Data of Contract Accounts Technical name: 0UC_ACCNTBP_ATTR






IS-U 4.63 (4.6C)


No

Use This DataSource only extracts partner-based information on contract accounts that is specifically related to the Utilities Industry (IS-U). This data will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.



320

51

SAP Online Help

28.01.2004



Table of Origin


VKONT


FKKVKP

VKONT

GPART


FKKVKP

GPART

KTOKL

Account class

FKKVKP

KTOKL

KZABSVER

Budget billing procedure FKKVKP

KZABSVER

ZAHLKOND

Payment term

ZAHLKOND

FKKVKP

IS-U: Business Partner Technical name: 0UCBU_PART_ATTR




Utilities Industry 0IS-UC


IS-U 4.63 (4.6C)


No

Use This DataSource only extracts information on the business partner that is specifically related to the Utilities Industry (IS-U). This data will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


PARTNER


EKUN

PARTNER

WAKLASS

Employee classification

EKUN

WAKLASSE

KTOKLASSE

Account class

EKUN

KTOKLASSE

IS-U Historical Consumption Values Technical name: 0UC_ISU_CONSUMPTION Technical data


320

52

SAP Online Help

28.01.2004

Type of DataSource

Transaction data




IS-U 4.63 (4.6C)


No

Prerequisites In order to use the DataSource in the best way possible way, we recommend that you read the information in SAP Service Market Place (http:\\service.sap.com) under Solutions in Detail → Industry Solutions → mySAP Utilities → mySAP Utilities & Cross-Industry Solutions → mySAP CRM for Utilities → Implementation/Cookbooks → IS-U/CRM-Integration Marketing Process. Due to the large amounts of data involved, it is important that you execute the activity “Settings for the extraction of marketing-relevant data” in the IMG for BW before the first productive loading process is carried out. We recommend that you first of all activate the consumption history in OLTP via the IS-U billing program (billing variant QUANTI23 or QUANTI22).

Use This DataSource transfers information about historical consumption values and turnover to InfoSource 0UC_ISU_CONSUMPTION [Extern] (consumption values and turnover). If you require criteria from the master data for target group selection in BW, check that they already exist in BW as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption values). This is the case for many attributes of the master data characteristics contained in the InfoCube. These attributes can then be selected during the query definition for the navigation. This saves you having to re-read master data via the customer enhancement of the extractor and provides you with the most up-to-date version of BW data from the last master data upload.

The DataSource only contains the key master data characteristics (business partner, contract account, contract, installation) from the characteristics required in BW for evaluating historical consumption values and turnover. Hiding fields does, therefore, not improve performance.

Delta Update After initializing the delta method, you can use this DataSource for the delta upload. The extraction date is the selection criteria for initializing the delta method. The extraction date has two meanings. •

All billing documents that were created or cancelled until two days prior to the extraction date are processed.

•

All consumption months, including two days prior to the extraction date are updated with consumption values.

The analysis is executed for every contract. If the consumption months are not completely covered by the billing periods of the billing documents, the missing periods are projected as far as this is accounted for in “Settings for the extraction of marketing-relevant data”. The system date is used as the extraction date during the Delta update. All billing documents that were created or cancelled between the (logged) extraction date of the initialization of the delta method or between the last delta update and two days prior to the actual extraction date are processed. Additionally, all consumption months since the last logged extraction date up to the last two days of the current extraction date are updated.


320

53

SAP Online Help

28.01.2004

The extraction date for the initialization of the delta method cannot be a date in the future. The initialization of the delta method behaves like a full upload with regards to the scope of the selected data. We recommend that large utility companies do not use the full upload and, in order increase performance, select an update using the PSA. We recommend that you execute the delta update once a month.

Fields of Origin in the Extraction Structure Field in extract structure

Description of Field in the Extraction Structure

Table of Origin


SPARTE

Division

ERCH

SPARTE

GPARTNER


ERCH

GPARTNER

VKONT


ERCH

VKONT

VERTRAG

Contract

ERCH

VERTRAG

ANLAGE

Installation

ERCH

ANLAGE

NETTOBTR

Net amount bill line

DBERCHV

NETTOBTR

ADDITIONAL_AMNT


DBERCHV

TWAERS

Transaction currency

DBERCHV

TWAERS

ABRMENGE

Billing quantity internal format for billing

DBERCHV

EZ_ABRMENGE

MASSBILL

Billing unit

DBERCHV

MASSBILL

CONSUMPTIONMON TH

Field from category DATS

DBERCHV

BILLEDDAYS

Number of days

PROJECTIONDAYS

Number of days (extrapolation)

DATATYPE

Category of consumption data

EXTRACT_DATE


Features of Extractor As of release IS-U 4.64, the DataSource can also be used for the ODS. See the documentation for the ODS object 0UCM_DS01. The extraction structure is completed using function module ISU_BW_CONSUMPTION_STATISTICS. The two fields BEGABRPE and ENDABRPE/ABRDATS were used to calculate the number days billed/extrapolated in the function module. The extractor cannot be used for a parallel upload in PSA.


320

54

SAP Online Help

28.01.2004

IS-U Historical Consumption (Delta by Mass Activity) Technical name: 0UC_ISU_CONSUMPT_02


Transaction data




IS-U 4.64 (4.6C)

Available from Plug-In Release

DataSource is shipped with the OLTP release


No

Prerequisites In the OLTP, the consumption history must have been completely built before you can use the DataSource. For more information on building the consumption history (either in system migration or in the current IS-U system), see the SAP Service Market Place (http:\\service.sap.com) under Solutions in Detail → Industry Solutions → mySAP Utilities → mySAP Utilities & Cross-Industry Solutions → mySAP CRM for Utilities → Implementation/Cookbooks → IS-U/CRM-Integration Marketing Process. To have the IS-U Billing program permanently update the consumption and demand histories in the OLTP, you must include the billing variants QUANTI23 and DEMAND23 in your rates. You do this in Customizing. Due to the large amounts of data involved, it is important that you execute the Settings for the extraction of marketing-relevant data activity in Customizing for BW before the first productive loading process is carried out.

Use This DataSource transfers information to the Conumption and Revenue for Target Group Selection (Delta by Mass Activity) InfoSource (0UC_ISU_CONSUMPT_02). You can use this DataSource as an alternative to the IS-U Historical Consumption DataSource 0UC_ISU_CONSUMPTION) to enable parallel processing of the selection from the OLTP database. This enables to maintain the delta queue using a mass activity. Furthermore additional development affecting the extraction of the consumption history to BW only apply to this DataSource. As such, this DataSource contains additional fields for evaluation demand quantities and amounts. Only one of the DataSources can be used. You cannot switch from the 0UC_ISU_CONSUMPTION DataSource to 0UC_ISU_CONSUMPT_02 during productive operation.

Delta Update The delta, especially the extrapolation date, is managed via the EMKT_ESTM_CONS_P index table. This table must first be built. In the OLTP, choose Utilities Industry → Information System → Business Information Warehouse (BW) → Prepare Indexes for Historical Consumption. If you previously worked with the 0UC_ISU_CONSUMPTION DataSource, you can copy any existing indexes instead of having to completely re-determine them. When you have prepared the indexes, you can initialize the delta procedure. You can then use this DataSource for the delta upload. Upload Transactions in Detail Full Upload: The full upload modes has no affect on this DataSource. Initial Upload: Initialization takes place once. Note that no data is extracted to BW.


320

55

SAP Online Help

28.01.2004

Delta Upload: The data from the delta queue is transferred. Before carrying out the Delta upload, you must start a mass run in the OLTP. ...

1. Start the transaction EBW_DQ_CS or go to the OLTP menu and choose Utilities Industry → Information System → Business Information System (BW) → Update Historical Consumption to Delta Queue. 2. In this transaction, maintain a variant for dividing the contract number stocks into intervals. 3. Start the mass runs or use the planning options. 4. Use the Environment menu option to check the application log or go to the OLTP menu and choose Utilities Industry → Tools → Monitoring of Mass Runs. Then enter mass activity BWCS.

In large utility companies, we recommend that this be preformed monthly. You can do this more often, however this does not reduce runtimes significantly. This transaction processes all contracts in parallel, according to load distribution and interval division, and writes all the data records to the delta queue. 5. Initiate the delta upload from BW when the last job has been completed. The delta upload can also be initiated before the next mass run starts.



Table of Origin


SPARTE

Division

ERCH

SPARTE

GPARTNER


ERCH

GPARTNER

VKONT


ERCH

VKONT

VERTRAG

Contract

ERCH

VERTRAG

ANLAGE

Installation

ERCH

ANLAGE

NETTOBTR


DBERCHV

NETTOBTR

ADDITIONAL_AMNT


DBERCHV

TWAERS


DBERCHV

TWAERS

ABRMENGE

Billing quantity internal format for billing

DBERCHV

EZ_ABRMENGE

MASSBILL

Billing unit

DBERCHV

MASSBILL

CONSUMPTIONMONT H


DBERCHV

BILLEDDAYS

Number of days

PROJECTIONDAYS

Number of days (extrapolation)

DATATYPE

Category of consumption data

EXTRACT_DATE


DEMAND_FROM

From-date for time slice

DBERCHV

AB

DEMAND_TAG

Data record describes demand

DBERCHV

ARTMENGE


320

56

SAP Online Help

DEMAND_FROM

28.01.2004

From-date for time slice

DBERCHV

BIS

Features of Extractor The DataSource can also be used for the ODS. See the documentation for the ODS object 0UCM_DS01.

Partner-Independent Contract Account Data Technical name: 0CACONT_ACC_ATTR




Contract Accounts Receivable and Payable (FI-CAIO)


IS-U 4.63 (4.6C)


No

Use This DataSource extracts information not based on the partner for contract accounts. This will be primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.


Fields of Origin in the Extraction Structure Field in Extraction Structure


Table of Origin


VKONT


FKKVK

VKONT

VKTYP


FKKVK

VKTYP

APPLK

Application area

FKKVK

APPLK

LOEVM

Indicator: Set contract account for deletion

FKKVK

LOEVM

MANDT

Client

FKKVK

MANDT

Partner-Independent Contract Account Data Technical name: 0FC_ACCNTBP_ATTR Technical Data Attributes (Master Data)

Type of DataSource


320

57

SAP Online Help

28.01.2004


Contract Accounts Receivable and Payable (FI-CA-IO)


IS-U 4.63 (4.6C)


No

Use This DataSource extracts partner-dependent information for contract accounts. This data is primarily used as navigation attributes of the InfoCube 0UCMA_C01 (target group selection according to turnover and consumption) in BW.




Table of Origin


VKONT


FKKVKP

VKONT

GPART


FKKVKP

GPART

VKBEZ


FKKVKP

VKBEZ

EBVTY

Bank details ID for incoming payments

FKKVKP

EBVTY

LOEVM

Select contract account for deletion

FKKVKP

LOEVM

VKPBZ


FKKVKP

VKPBZ

FDGRP

Planning group

FKKVKP

FDGRP

MANDT

Client

FKKVKP

MANDT

Payment Scheme Technical name: 0UC_PAYSCHEME


Transactional data (movement data)




IS-U 4.64 (4.6C)


No

Use This DataSource extracts information regarding budget billing plans that refer to a payment scheme.


320

58

SAP Online Help

28.01.2004

Delta Update The DataSource supports the delta processing after initialization. The initialization reads all payment schemes in accordance with the selection, whereby the VTREF selection field represents the contract in IS-U. This means that you can only enter a maximum of 10 digits. We recommend that you carry out initialization for all contracts, even if there is not yet any contract data in the selection area. Payment schemes for new contracts are entered automatically during delta processing.



Table of Origin


BEGDAT

Start of sample line validity

EABPL

BEGDAT

BETRW

Payment scheme amount in transaction currency

EABPL

BETRW

ENDDAT

Validity end date of budget billing sample lines

EABPL

ENDDAT

PAYDATE

Payment date in payment scheme

EABPL

PAYDATE

PAYFREQ

Payment frequency of payment scheme

EABPL

PAYFREQ

UPDMOD

BW Delta procedure: Update mode

VTREF

Reference data from contract

EABPL

VTREF

WAERS


EABPL

WAERS

Point of Delivery Header Data Technical name: 0UC_POD_ATTR


Texts (Master Data)


Utilities Industry 0IS_UC-IO


IS-U 4.71 (6.20)


No

Prerequisites Since this DataSource is not able to select the points of delivery to be extracted, you must first carry out the initial load in the persistent staging area (PSA). Some databases are not capable of handling large amounts of initial data. This may result in termination of the loading procedure.


320

59

SAP Online Help

28.01.2004

It is not possible to select the points of delivery as they are saved internally as GUIDs, which are not suitable to use as selection criteria.

Use This DataSource extracts the header data of the IS-U point of delivery. This header data is primarily used as selection characteristics in InfoSets.

Delta Update This DataSource supports the delta process AIM. That is, changes to the point of delivery are written to the delta queue.



Table of Origin


UITYPE

Point of delivery type

EUIHEAD

UITYPE

EUIROLE_TECH

Technical point of delivery

EUIHEAD

EUIROLE_TECH

EUIROLE_DEREG

Deregulation point of delivery

EUIHEAD

EUIROLE_DEREG

LOEVM

Deletion indicator

EUIHEAD

LOEVM

VSTELLE

Premise

EUIHEAD

VSTELLE

UPDMOD

BW Delta process: Update mode

OUCONT

Outline contract

EUIHEAD

OUCONT

INT_UI_BW

Internal point of delivery Conversion routine ID for BW

Features of the Extractor This DataSource does not support the selection of the points of delivery to be extracted.

External Point of Delivery ID Technical name: 0UC_POD_EXT_ATTR


Texts (Master Data)




IS-U 4.71 (6.20)


No



320

60

SAP Online Help

28.01.2004


Use This DataSource extracts the external point of delivery ID. The point of delivery can always be identified by means of the external ID.

Delta Update This DataSource supports the delta process AIM. That is, changes to the point of delivery are written to the delta queue.



Table of Origin


DATETO

To-Date

EUITRANS

DATETO

TIMETO

To-Time

EUITRANS

TIMETO

DATEFROM

From-Date

EUITRANS

DATEFROM

TIMEFROM

From-Time

EUITRANS

TIMEFROM

UISTRUTYP

Structure type of point of delivery ID

EUITRANS

EUIROLE_TECH

LOEVM

Deletion indicator

EUITRANS

LOEVM

UPDMOD


INT_UI_BW


EXT_UI_BW

Point of delivery ID BW

Conversion routine


Allocate Point of Delivery to Installtion Technical name: 0UC_PODINST_ATTR


Texts (Master Data)




IS-U 4.71 (6.20)


No



320

61

SAP Online Help

28.01.2004


Use This DataSource extracts the allocation of the points of delivery to the corresponding utility installment. A point of delivery can be allocated to several installations at the same time.

Delta Update This DataSource supports the delta process AIM. That is, changes to the allocation are written to the delta queue.



Table of Origin


ANLAGE

Installation

EUIINSTLN

ANLAGE

DATETO

To-Date

EUIINSTLN

DATETO

TIMETO

To-Time

EUIINSTLN

TIMETO

DATEFROM

From-Date

EUIINSTLN

DATEFROM

TIMEFROM

From-Time

EUIINSTLN

TIMEFROM

EUIROLE_TECH


EUIINSTLN

EUIROLE_TECH

EUIROLE_DEREG


EUIINSTLN

EUIROLE_DEREG

LOEVM

Deletion indicator

EUIINSTLN

LOEVM

UPDMOD


INT_UI_BW



Prepayment Meter Technical name: 0UC_ISU_PPM_1






IS-U 4.64 (4.6C)

Use This DataSource extracts the movement data for contracts with prepayment meters (PPM).


320

62

SAP Online Help

28.01.2004

Delta Update The DataSource supports the delta processing after initialization. The initialization reads all PPMs in accordance with the selection. We recommend that you carry out initialization for all PPMs, even if there is not yet any PPM data in the selection area. New contracts with PPMs are entered automatically during delta processing.



Table of Origin


PP_NR

Prepayment document number

PPMHEADER

PP_NR

DEBT_CONS

Consumption debts

PPMDEBT

DEBT_CONS

DEBT_NON_CONS

Other debts

PPMDEBT

DEBT_NON_CONS

RR_CONS

Recovery rate for consumption debts

PPMRR

RR_CONS

RR_NON_CONS

Recovery rate for other debts

PPMRR

RR_NON_CONS

PP_TO

End of validity of entry

PPMDEBT

PP_TO

PP_FROM

Start of validity of entry

PPMDEBT

PP_FROM

TWAERS


PPMDEBT

TWAERS

UPDMOD

BW delta process: Update mode

UPDMOD

Prepayment Meter Master Data Technical name: 0UC_ISU_PPM_2






IS-U 4.64 (4.6C)

Use This DataSource extracts the master data for contracts with prepayment meters (PPM).

Delta Update The DataSource supports the delta processing after initialization. The initialization reads all PPMs in accordance with the selection. The data is primarily used as navigation attributes for the PPM movement data.


Description of Field in the Extraction


320

Table of Origin


63

SAP Online Help

28.01.2004

Structure

Structure

Origin

PP_NR

Prepayment document number

PPMHEADER

PP_NR

PP_TO

End of validity of entry

PPMDEBT

PP_TO

PP_FROM

Start of validity of entry

PPMDEBT

PP_FROM

SPARTE

Division

PPMHEADER

SPARTE

VERTRAG

Contract

PPMHEADER

VERTRAG

ACTION

Process description

PPMHEADER

ACTION

IS-U Mass Simulation of Billing Technical name: 0UC_SALES_SIMU_01






IS-U 4.71


No

Prerequisites A prerequisite for this DataSource is that you use mass simulation in the IS-U system with integration to BW. You can use mass simulation to extract contract-specific, extrapolated billing data (billing amounts and revenues) to BW. A simulation type must be defined in IS-U. This is used to update the mass simulation documents in BW. DataSource 0UC_SALES_SIMU_01 must be registered for this simulation type. You maintain the simulation type in the OLTP IMG under Utilities Industry → Contract Billing → Integration Reporting → Integration Mass Simulation → Define Simulation Types.

Use The DataSource transfers information to InfoSource 0UC_SALES_SIMU_01 (Unbilled Revenue Reporting (Extrapolated Data)) in BW. This information forms the basis for executing unbilled revenue reporting in BW. The accrual/deferral amount can be determined along with the sales statistics data.

Delta Update Once the delta method has been initialized, this DataSource must be used for the delta update. This takes place within mass simulation. You can find more information on unbilled revenue reporting in the SAP Service Marketplace (http:\\www.service.sap.com) under Solutions Details → Industry Solutions → mySAP Utilities → Product Information → ISU/CCS → Billing & Invoicing → Cookbooks&Guidelines → Unbilled Revenue Reporting 4.64. The Full Upload function is not supported and should not be used. Uploading Processes in Detail Initial Upload:


320

64

SAP Online Help

28.01.2004

Initialization takes place once in accordance with the selection. Note that no data is extracted to BW. Delta Upload: The data from the delta queue is transferred. Before carrying out the Delta upload, you must create simulation indexes and bill them using a mass activity in OLTP. ...

1. Start transaction EAMS10 (in the SAP Menu under Utilities Industry → Billing → Mass Simulation → Preparation → Create Simulation Indexes). 2. Start transaction EAMS01 (in the SAP Menu under Utilities Industry → Billing → Mass Simulation → Execution → Parallel Processing. Billing Simulation Indexes). 3. Enter the required identification dates in this transaction. 4. Start the mass runs or use the planning options. 5. Initiate the delta upload from BW when the last job has been completed. The delta upload can also be initiated before the next mass run starts. You can update the delta queues of different DataSources in one run for the billing of simulation indexes. You must register the DataSources under the simulation type to which the simulation period refers. Ensure to take into account the prerequisites for execution. In this way you can use the extrapolation data for unbilled revenue reporting as well as for CRM quotation analysis in BW without suffering from reduced performance.



Table of Origin


AKLASSE

Billing class

ERCHZ

AKLASSE

ARTMENGE

Classification of billing amount for statistics

ERCHZ

ARTMENGE

BETRAG

Net amount

ERCHZ

BETRAG

BUCHREL

Bill line item relevant to posting

ERCHZ

BUCHREL

BUKRS

Company Code

ERCH

BURKS

CITY_CODE

City code

ADRC

CITY_CODE

COUNTRY

Country

ADRC

COUNTRY

DIFFKZ

Indicator: Difference line item for discount statistics

ERCHZ

DIFFKZ

KOFIZ

Account determination characteristic for contracts

ERCH

GPARTNER

KONZIGR

Franchise fee group

ERCHZ

KONZIGR

KONZVER

Franchise contract

ERCHZ

KONZVER

MASSBILL

Unit of measurement

ERCHZ

MASSBILL

MENGE

Billing quantity

ERCHZ

I_ABRMENGE

PORTION

Portion

ERCH

PORTION

REGION

Region

ADRC

REGION

SIMRUNID

Simulation period ID

ERCH

SIMRUNID


320

65

SAP Online Help

28.01.2004

SPARTE

Division

ERCH

SPARTE

SPEBENE

Voltage level

EANL

SPEBENE

STGRQNT


ERCHZ

STGRQNT

STGRAMT


STGRAMT

STTARIF

Statistical rate

ERCHZ

STTARIF

TARIFTYP

Rate category

ERCHZ

TARIFTYP

UPDMOD

BW delta procedure: update session

Fixed value = SPACE

VBRMONAT

Consumption month


WAERS

Currency key

Dynamic determination (from BUKRS)

XCANC

Cancellation/reversal indicator


IS-U Mass Simulation (Forecast C&I Customers) Technical name: 0UC_SALES_SIMU_02






IS-U 4.71


No

Prerequisites This DataSource is only relevant if you have the IS-U/CRM Integration component for commercial and industrial (C&I) customers, which is available as of CRM 4.0. A further prerequisite is that you use mass simulation in the IS-U system with integration to BW. You can use mass simulation to extract contract-specific, extrapolated billing data (billing amounts and revenues) to BW. A simulation type must be defined in IS-U. This is used to update the mass simulation documents in BW. DataSource 0UC_SALES_SIMU_02 must be registered for this simulation type. You maintain the simulation type in the OLTP IMG under Utilities Industry -> Contract Billing -> Integration Reporting -> Integration Mass Simulation -> Define Simulation Types. In addition, the settings for the update group determination in IS-U must be made so that only data relating to commercial and industrial contracts is extracted by means of this DataSource. You maintain the update group SNRES (C&I customers) in the OLTP IMG under Settings for Application-Specific DataSources -> Utilities Industry -> Sales Statistics -> Update Control -> Define Update Group Determination for all Commercial and Industrial Contract Rate Types. If you use the initial Customizing provided by SAP for table TE755 (Determination of Update Group), these settings are made automatically.


320

66

SAP Online Help

28.01.2004

Use The DataSource transfers information to InfoSource 0UC_SALES_SIMU_02 (Forecast for C&I Customers (CRM)) in BW. This information forms the basis for a comparison of the forecast-actual data with the plan data, which is updated during the creation of utility quotations in CRM. In connection with a cost analysis, you can carry out a profitability analysis of utility quotations.

Delta Update Once the delta method has been initialized, this DataSource can be used for the delta update. This takes place within mass simulation. The full upload has no effect and should not be used. Uploading Processes in Detail Initial Upload: Initialization takes place once in accordance with the selection. Note that no data is extracted to BW. Delta Upload: The data from the delta queue is transferred. Before carrying out the Delta upload, you must create simulation indexes and bill them using a mass activity in OLTP. ...

1. Start transaction EAMS10 (in the SAP Menu under Utilities Industry -> Billing -> Mass Simulation -> Preparation -> Create Simulation Indexes). 2. Start transaction EAMS10 (in the SAP Menu under Utilities Industry -> Billing -> Mass Simulation -> Execution -> Parallel Processing: Billing Simulation Indexes). 3. Enter the required identification dates in this transaction. 4. Start the mass runs or use the planning options. 5. Initiate the delta upload from BW when the last job has been completed. The delta upload can also be initiated before the next mass run starts. You can update the delta queues of different DataSources in one run for the billing of simulation indexes. You must register the DataSources under the simulation type to which the simulation period refers. Ensure to take into account the prerequisites for execution. In this way you can use the extrapolation data for unbilled revenue reporting as well as for CRM quotation analysis in BW without suffering from reduced performance.



AB

From date of time slice

ANLAGE

Installation

EANL

ANLAGE

ARTMENGE

Classification of billing amount for statistics

ERCHZ

ARTMENGE

AUFNR

Order number

ERCHZ

AUFNR

BETRAG

Net amount

ERCHZ

BETRAG

BIS

To-date of time slice

BUCHREL

Bill line item relevant to posting

ERCHZ

BUCHREL

CITY_CODE

City code

ADRC

CITY_CODE

COUNTRY

Country

ADRC

COUNTRY


320

Table of Origin

Field in Table of Origin Dynamic determination


67

SAP Online Help

28.01.2004

DIFFKZ

Indicator: Difference line ERCHZ item for discount statistics

DIFFKZ

FRAN_TYPE

Franchise fee category

ERCHZ

FRAN_TYPE

GPARTNER

Business partner

ERCH

GPARTNER

KOKRS

Controlling area

KONZVER

Franchise contract

ERCHZ

KONZVER

KOSTL

Cost center

ERCHZ

KOSTL

MASSBILL

Unit of measurement

ERCHZ

MASSBILL

MENGE

Billing quantity

ERCHZ

I_ABRMENGE

PRCTR

Profit center

ERCHZ

PRCTR

REGIOGROUP


ADRC

REGIOGROUP

REGION

Region

ADRC

REGION

SERVICEID

Service provider

EVER

SERVICEID

SIMRUNID

Simulation period ID

ERCH

SIMRUNID

SPARTE

Division

ERCH

SPARTE

SPEBENE

Voltage level

EANL

SPEBENE

STAFO

Update group for statistics

ERCHZ

STAFO

STGRQNT


ERCHZ

STGRQNT

STGRAMT


STGRAMT

UPDMOD

BW Delta procedure: Update mode

Fixed value = SPACE

VBRMONAT

Consumption month

Dynamic determination (from AB and BIS)

VERTRAG

Contract

ERCH

VERTRAG

VKONT

Contract account

ERCH

VKONT

WAERS

Currency

Dynamic determination from company code

Dynamic determination (from BUKRS)

IS-U Item Type (CRM) Technical name: 0CRM_UT_ITMTYP_ATTR




CRM Service Master Data 0CRM_SERVICE-IO


CRM 4.0


320

68

SAP Online Help

28.01.2004


No

Prerequisites This DataSource is only relevant if you have the IS-U/CRM Integration component for nonresidential customers, which is available as of CRM 4.0.

Use The DataSource transfers information to InfoSource 0UCC_ITMTYP (IS-U item type) in BW. This information forms the basis for differentiating between CRM utility contract items in BW according to residential and non-residential customers as well as distributor and supplier items.

Delta Update A delta update is neither possible nor necessary as there is only a small amount of Customizing data.



Table of Origin


ISU_DISTRIBUTOR

Indicator: Distributor item

ECRM_ISU_ITMTYP

ISU_DISTRIBUTOR

ISU_QUOTATION

Indicator: Quotation item

ECRM_ISU_ITMTYP

ISU_QUOTATION

ISU_SC_ITMT

Indicator: Nonresidential contract

ECRM_ISU_ITMTYP

ISU_SC_ITMT

ISU_SUPPLIER

Indicator: Supplier item

ECRM_ISU_ITMTYP

ISU_SUPPLIER

ITM_TYPE

IS-U Item type

ECRM_ISU_ITMTYP

ITM_TYPE

Service Quotation for the Utilities Industry (Item) Technical name: 0CRM_UT_QUOTATION_I




CRM Service 0CRM_SERVICE


CRM 4.0


No

Prerequisites This DataSource is only relevant if you have the IS-U/CRM Integration component for nonresidential customers, which is available as of CRM 4.0. The DataSource extracts data from CRM by means of the BW adapter. You must activate the BW adapter metadata for the DataSource. You do this is the OLTP IMG for CRM under Settings for SAP Business Warehouse → Activate BW Adapter Metadata.


320

69

SAP Online Help

28.01.2004

Use The DataSource transfers information to InfoSource 0UCCRM_QUOTATION_I (Item for Utility Quotation (CRM)) in BW. The information contains the attributes of the utility quotation from CRM.

Delta Update AIMD: After Images with deletion indicators using delta queue.



Table of Origin


BWSTONESYS2

CRM status: Quotation accepted

STATUS

STATUS

BWSTTECSYS2

CRM status: Incorrect

STATUS

STATUS

DIS_CHANNEL

Distribution channel

ORGMAN

DIS_CHANNEL

DIVISION

Division

ORGMAN

DIVISION

GUID

GUID of quotation header (CRM)

ORDERADM_H

ORDERADM_H_GUID

IB_IOBJ_GUID

GUID of point of delivery (CRM)

ORDPRP_OBJL_I_D

IBASE_COMPONENT_ GUID

ITEM_GUID

GUID of quotation item (CRM)

ORDERADM_I

GUID

ITM_TYPE

IS-U Item Type (CRM)

ORDERADM_I

ITM_TYPE

LOGICAL_SYSTEM

Source system

ORDERADM_H

LOGICAL_SYSTEM

MKT_ELEMENT

CRM campaign

ORDERADM_H

ORDERADM_H_GUID

OBJECT_ID

Transaction number

ORDERADM_H

OBJECT_ID

OBJECT_TYPE

Business transaction object type

ORDERADM_H

OBJECT_TYPE

PERSON_RESP

Employee responsible

PARTNER

PARTNER_NO

PRODUCT_GUID

GUID of CRM product

ORDERADM_I

PRODUCT

SALESPARTNER

Sales partner

PARTNER

PARTNER_NO

SALES_EMPLOYEE


PARTNER

PARTNER_NO

SALES_GROUP

Sales group CRM

ORGMAN

SALES_GROUP

SALES_OFFICE

Sales office CRM

ORGMAN

SALES_OFFICE

SALES_ORG

Sales organization CRM ORGMAN

SALES_ORG

SALES_ORG_RESP

Responsible organizational unit in sales

ORGMAN

SALES_ORG_RESP

SERVICE_ORG

Service organization CRM

ORGMAN

SERVICE_ORG

SERVICE_ORG_RESP

Responsible organizational unit (service)

ORGMAN

SERVICE_ORG_RESP


320

70

SAP Online Help

28.01.2004

SHIP_TO_PARTY

Ship-to party

PARTNER

PARTNER_NO

SOLD_TO_PARTY

Sold-to party

PARTNER

PARTNER_NO

STATUS_EXPIRED

CRM status: expired (quotation)

STATUS

STATUS

VALID_FROM_DATE

Valid-from date for quotation

APPOINTMENT

TIMESTAMP_FROM

VALID_TO_DATE

Valid-to date

APPOINTMENT

TIMESTAMP_TO

Service Contract for the Utilities Industry (Item) Technical name: 0CRM_UT_SRV_CONT_I




CRM Service 0CRM_SERVICE


CRM 4.0


No

Prerequisites This DataSource is only relevant if you have the IS-U/CRM integration component for commercial and industrial customers, which is available as of CRM 4.0. The DataSource extracts data from CRM by means of the BW adapter. You must activate the BW adapter metadata for the DataSource You do this is the OLTP IMG for CRM under Settings for SAP Business Warehouse → Activate BW Adapter Metadata.

Use The DataSource transfers information to InfoSource 0UCCRM_SRV_CONT_I (Item for Utility Contract (CRM)) in BW. The information contains the attributes of the utility contract from CRM.

Delta Update AIMD: After Images with deletion indicators using delta queue.



Table of Origin


BEGIN_DATE

Valid-from date for contract

APPOINTMENT

TIMESTAMP_FROM

BWSTONESYS2

CRM status: Quotation accepted

STATUS

STATUS

CANC_REASON

Reason for canceling contract

CANCEL

CANC_REASON

DIS_CHANNEL

Distribution channel

ORGMAN

DIS_CHANNEL


320

71

SAP Online Help

28.01.2004

DIVISION

Division

ORGMAN

DIVISION

ENDING_DATE

Valid-to date for contract

APPOINTMENT

TIMESTAMP_TO

GUID

GUID of contract header (CRM)

ORDERADM_H

ORDERADM_H_GUID

IB_IOBJ_GUID

GUID of point of delivery (CRM)

ORDPRP_OBJL_I_D

IBASE_COMPONENT_ GUID

ITEM_CREATED_AT

Date on which the contract was created

APPOINTMENT

TIMESTAMP_FROM

ITEM_GUID

GUID of contract item (CRM)

ORDERADM_I

GUID

ITM_TYPE

IS-U item type (CRM)

ORDERADM_I

ITM_TYPE

LOGICAL_SYSTEM

Source system

ORDERADM_H

LOGICAL_SYSTEM

MKT_ELEMENT

CRM campaign

ORDERADM_H

ORDERADM_H_GUID

OBJECT_ID

Transaction number

ORDERADM_H

OBJECT_ID

OBJECT_TYPE

Business transaction object type

ORDERADM_H

OBJECT_TYPE

PERSON_RESP


PARTNER

PARTNER_NO

PLANNED_END_DATE Planned valid-to date for contract

APPOINTMENT

TIMESTAMP_TO

PRODUCT_GUID

GUID of CRM product

ORDERADM_I

PRODUCT

PRODUCT_ID

CRM product

ORDERADM_I

PRODUCT

QUOTATION_GUID

GUID of quotation item (CRM)

DOC_FLOW

OBJKEY_A

SALESPARTNER

Sales partner

PARTNER

PARTNER_NO

SALES_EMPLOYEE


PARTNER

PARTNER_NO

SALES_GROUP

Sales group CRM

ORGMAN

SALES_GROUP

SALES_OFFICE

Sales office CRM

ORGMAN

SALES_OFFICE

SALES_ORG

Sales organization CRM ORGMAN

SALES_ORG

SALES_ORG_RESP

Responsible organizational unit in sales

ORGMAN

SALES_ORG_RESP

SERVICE_ORG

Service organization CRM

ORGMAN

SERVICE_ORG

SERVICE_ORG_RESP

Responsible organizational unit (service)

ORGMAN

SERVICE_ORG_RESP

SHIP_TO_PARTY

Ship-to party

PARTNER

PARTNER_NO

SOLD_TO_PARTY

Sold-to party

PARTNER

PARTNER_NO

STATUS_ERROR

CRM status: Incorrect

STATUS

STATUS


320

72

SAP Online Help

28.01.2004

Point of Delivery (CRM) Technical name: 0CRM_UT_POD_ATTR




Master data (CRM) 0CRM_IO


CRM 4.0 (6.20)


No

Prerequisites As a prerequisite, you must have the IS-U/CRM integration component.

Use This DataSource extracts the point of delivery and its attributes from CRM to BW. Some of these attributes are required for quotation planning. The point of delivery is also important for marketing with individual objects. For the initial upload, we recommend that you make the selection by point of delivery ID.

Delta Update The delta update is supported. The delta queue us updated online when you create or change a point of delivery in CRM.



Table of Origin


EUIROLED


ISU_POD

EUIROLED

EUIROLET


ISU_POD

EUIROLET

EXT_UI_BW

Point of delivery ID (uppercase letters)

ISU_POD

EXT_UI

GRID_ID

Grid

ISU_POD

GRID_ID

GRID_LEVL

Grid level

ISU_POD

GRID_LEVL

GRID_LTYP

Grid level type

ISU_POD

GRID_LTYP

INT_UI_BW

Point of delivery (uppercase letters)

ISU_POD

INT_UI

LOEVM

Deletion indicator

ISU_POD

LOEVM

LOGSYS

Original system

COMM_PRODUCT

LOGSYS

OBJECT_FAMILY

Object family

COMM_PRODUCT

OBJECT_FAMILY

OUTL_CONT

Indicator: Outline contract

ISU_POD

OUTL_CONT

PRODUCT_GUID

Internal, unique product ID

COMM_PRODUCT

PRODUCT_GUID

PRODUCT_ID

Product ID

COMM_PRODUCT

PRODUCT_ID


320

73

SAP Online Help

28.01.2004

PRODUCT_TYPE

Product category

COMM_PRODUCT

PRODUCT_TYPE

SPARTE

Division

ISU_POD

SPARTE

STATUS

Status

ISU_POD

STATUS

UICAT

Point of delivery category

ISU_POD

UICAT

UITYPE

Point of delivery type

ISU_POD

UITYPE

Remote Extractor: Profile Values Technical name: 0UC_EDM_01






IS-U 4.71 (6.20)


Yes

Use This DataSource extracts the profile values in accordance with the selection criteria. The extractor carries out a pre-aggregation of the profile values, that is, if the combinations of characteristics for the selected profile values are identical, they are aggregated. This, however, also depends on the profile category, as not all profiles can be aggregated. It is necessary to aggregate the profile values in order to avoid having to transfer large quantities of data to BW, which can have a negative effect on system performance. Some selections are absolutely necessary and should not be deactivated. Examples of these selections are as follows: •

Internal point of delivery ID for BW The extractor reads all of the profile data for the selected points of delivery. Due to the quantity of data, always select at least one point of delivery.

•

Division It does not make sense to mix and aggregate profile values from different divisions. Therefore it is important to limit the selection to one division only. If all of the points of delivery belong to one division, the selection of a division is irrelevant.

•

Create replacement values This allows you to control whether or not profile values are interpolated/extrapolated.

•

Selecting more criteria will further limit the profile values and, as a result, speed up the analysis.

The profile values are transferred with decimal and predecimal places. Set a suitable rounding number in the query.

Delta Update This DataSource does not support a delta method.


Description of Field in the Extraction St t


320

Table of Origin


74

SAP Online Help

28.01.2004 Structure

INT_UI_BW


SERVICE

Service type

PROFROLE

Role of profile allocation

PROFILE

Number of EDM profile

SPARTE

Division

PROFVALCAT

Profile value category

INTSIZEID

Interval length ID

MASS

Unit of measurement

DAY_OFFSET

Day offset

TIME_ZONE

Time zone for EDM objects

CREATE_VAL

Create replacement values

PROF_DATE

Date of profile values

PROF_TIME

Period range

PROF_VALUE

Profile value at application level

STAT

Individual status of an object

VALUE_ORIGIN

Origin of profile values

SEL_START

Start of selection period

SEL_END

End of selection period

Features of the Extractor You cannot deactivate the selection criteria that are predefined by SAP as the extractor requires these fields to contain a value.

IS-U: CRM Hierarchical Outline Contracts Technical name: 0UCCONTRACT_OUTL_HIER


Hierarchies


0IS_UC-IO (Master data: Utilities industry)


IS-U 4.71 SP06


No

Prerequisites As a prerequisite for this DataSource, you must have the IS-U/CRM Integration component for commercial and industrial customers based on CRM 4.0.


320

75

SAP Online Help

28.01.2004

Use If you create outline contracts in CRM, they are replicated as utility contracts in IS-U. From there, you can extract the allocation of the individual contracts to the outline contracts in the form of a hierarchy. This allows you to valuate the outline contract’s cumulated revenues and credit memos. In the bonus calculation procedure, for example, you can post some of these to the individual contracts and others to the outline contract.

Delta Update A Delta update is not supported.

Fields of Origin in the Extraction Structure Hierarchy Segment (Structure EOUTLHIENODE): Field in Extract Structure


NODEID

Hierarchy node ID

FIELDNM

VERTRAG (for individual contract) or OUCONTRACT (for outline contract), depending on the hierarchy level

NODENAME

Contract number

TLEVEL

Hierarchy level

PARENTID

ID of higher-level node

CHILDID

ID of lower-level node

NEXTID

ID of same-level node

DATEFROM

From-date of a time slice from the timedependent hierarchy structure

Table of Origin


EVERH

AB

DATETO

To-date of a time slice EVERH from the timedependent hierarchy structure

BIS

VERTRAG

Utility contract

EVER

VERTRAG

OUCONTRACT

Outline contract

EVERH

OUCONTRACT

BPARTNER

Business partner of outline contract

FKKVKP

GPART

DESCRIPTION

Description of hierarchy node

Features of the Extractor The hierarchy structure is time-dependent. Only outline contracts, to which individual contracts are allocated, are extracted.


320

76

SAP Online Help

28.01.2004

Individual contracts that are not allocated to an outline contract are not extracted.

Texts for Outline Contracts Technical name: 0UCCONTRACT_OUTL_TEXT


Texts


0IS_UC-IO (Master data: Utilities industry)


IS-U 4.71 SP06


No

Prerequisites As a prerequisite for this DataSource, you must have the IS-U/CRM Integration component for commercial and industrial customers based on CRM 4.0.

Use This DataSource provides the texts for the outline contracts extracted with DataSource 0UCCONTRACT_OUTL_HIER (IS-U: CRM Hierarchical Outline Contracts). There are different scenarios: 1. The contract creates a node at hierarchy level 01 (outline contracts) within the hierarchy extracted with DataSource 0UCCONTRACT_OUTL_HIER. In this case, the text of the business partner of the outline contract is provided (name, or name and address of business partner). 2. The contract creates a node at hierarchy level 02 (individual contracts) within the hierarchy extracted with DataSource 0UCCONTRACT_OUTL_HIER. In this case contract ID is provided. Generally, this is the text for the address of the premise.

Delta Update A Delta update is not supported.

Fields of Origin in the Extraction Structure Field in Extract Structure


VERTRAG

Contract

TXTSH

Short text (20 characters)

TXTMD

Medium text (40 characters)

TXTLG

Long text (60 characters)


320

Table of Origin


77

SAP Online Help


28.01.2004

320

78

Data Sources in the Utilities Industry

Recommend Documents