SAP- ISU

INDUSTRIAL SERVICE UTILITIES     IS-U:


    
     difference between   ISU          /     R3.


                ISU deals with    cs -----> bp customer,
                                           dm-----> devices,
                                           bi-------> billing,
                                           fi--------> finance.


               R3 deals with      sd , mm ,  n some other .......

                 The SAP Utilities (IS-U) component is a sales and information system that supports all business processes and utility services of a utility company. You can use IS-U for managing and billing residential, commercial and industrial, and prospective customers. This component also allows you to manage and bill customers who receive services, purchase goods, or pay fees and taxes.

IS-U comprises the following modules:

Master Data and Basic Functions
Customer Services
Work Management
Device Management
Billing & Invocing
Energy Data Management
Contract Accounts

The IS-U master data model can be categorized in to two main groups

1. Business master Data, BMD
2. Technical master Data. TMD.

flow of isu ;-  

          BP-->CA--> CONTRACTS--->INSTALLATION-->PREMISE---->CONNECTION BOJECT-->DEVICE LOCATION.

        BP                                    FPP1,FPP2,FPP3          ----->        BUT020----->    GPART  or PARTNER,
                              
                                 BUT000_PARTNER_READ.

        CA                                    CAA1,CAA2,CAA3       ----->        FKKVKP--->   VKONT,
                               
                                  FKK_ACCOUNT_READ.

         CONTRACTS                CA20,CA21,CA22           --->         EVER      -->    VERTRAG,

         INSTALLATION          ES30,ES31,ES32          -->              EANL     -->     INSTALLATION [ANLAGE],

         PREMISE                              ES60,ES61,ES62         --->              EVBS    --->     VSTELLE,

         CONNECTION OBJECT      ES55,ES56,ES57         -->               IFLOT   --->    TPLNR.

              

         DEVICE  LOCATION --        ES65,ES66,ES67.

1.Business Data: Any master data that is used for billing a customer for the services provided is grouped under Business data. For e.g., a business partner who is a person or an organization.
  

As you can see real life objects has been modeled as IS-U Master Data.
Connection Object = building
Premise = Apartment
Device Location = The location where a device is installed (e.g. Hall, Basement)
Meters = Meters
Installation = this is an object without real life correspondence and it is used for billing purposes
Contract = a contract for a specific type of utility
Contract Account = grouping of one or more contracts under the same umbrella for financial transactions
Business Partner = the customer


Let’s see what kind of data are stored at each master data level.

Business Partner      ISU_ADDRESS_PROVIDE
A business partner can have multiple roles within the SAP IS-U:
- Contract partner
- Installer
- Prospect
- Contact person

At the Business Partner Level we can store the following data:
General:
- Name
- Address
- Legal Form
- Group
- Search Term


Addresses
- Standard addresses
- P.O Box addresses
- Other addresses

Communication
- Telephone
- Fax
- Extension
- Internet
- E-mail

Payment Transaction
- Bank
- Bank Account

Biller Direct

Relationships
- Hierarchical
- Equal
- Connected

Additional Data
- Status
- Identification Number
- Register entry

..........ISU_FINDER --->  TOJTB is the table name for object type.   for 
      
                       bp ---> ISUPARTNER
                       CA ---> ISU ACCOUNT
                      CONTRACT --> ISU CONTRACT
                      ADDRESS ---> ISU ADDRESS.

          a.BUSINESS PARTNER: FPP1,FPP2,FPP3.

                               TABLES FOR BUSINESS PARTNER: BUT000,BUT020,BUT*

          b.CONTACT ACCOUNT:CAA1,CAA2,CAA3.

                               TABLES FOR CONTRACT ACCOUNT: FKKVKP,FKKVK

                                BP+CA=FKKVKP,

                                BP-->CA[n]-->c[n].

                                      

          c.CONTRACT:CA20,CA21,CA22

                            TABLES FOR CONTRACT : EVER.

FIELD NAMES FOR THE BMD:

BP-->GPART or PARTNER,

CA-->VKONT,

CONTRACT--> VERTRAG.

2.Technical Data: Any master data that is used for actually providing the services are grouped under Technical Data. For e.g., a device or a meter that is installed in a customer location.

                                                                                          FIELD NAME                      TABLENAME

           a.PREMISE                                                                VSTELLE                           EVBS

                     ES60,ES61,ES62.

            b.CONNECTION OBJECT                                           ANLAGE                             EANL

                     ES55,ES56,ES57.

             c.UTILITY INSTALLATION                                      TPLNR                               IFLOT

                    ES30,ES31,ES32.

             d.DEVICE LOCATION                                            DEVLOC                               IFLOT

                    ES65,ES66,ES67.

                                 FIELD NAMES FOR THE TMD :    GIVEN ...as FIELD NAME and TABLE NAME......

3.

             a.MOVE -IN PROCESS --------> move in date [EVER]
                     METER READING , MOVE IN DOCUMENT

              b.MOVE-OUT PROCESS-------> move out date
                     METER READING, MOVE OUT DOCUMENT

              c.DISCONNECTION PROCESS-> EDISCOBJ

              d.RECONNECTION PROCESS->  EDISCACT.

4. 

            a.SERVICE ORDER  [MRO meter reading order, billing order,invoicing],   -->  IW31.

            b.SERVICE NOTIFICATION --->IW58.

5.DEVICE MANAGEMENT:-

         a. device category,

         b. device.

           1. Technical installation, and    Billing installation, and      Full installation.

           2. Technical removal and Full removal.

           3. Technical replacement  or Full replacement,

           4. Reversal.

6.SCHEDULING and PORTION : -

   a. MRU METER READING UNIT  : ABLEINH {Ttable name}----> EABL {FIELD NAME}

       

           EABL----> METER RESULTS

           V_ZWSTAND [PREVIOUS READING]

            N_ZWSTAND [PRESENT READING]

           MRU  generates the dates for taking meter results [periodic or inter meter reading]

           MRO ----> EL28 

           ELO1------>  UPLOADING SINGLE ENTRY METER RESULT,

         FUNCTIONAL MODULE  FOR--->    MASS DATA ENTRY,

  b.PORTION genarates dates for billing    ---->   EASIBI

            EASIBI ----> BILLING DOCUMENT ----->  ERCH ,  ERDK

  C. REVERSAL OF BILLING DOCUMENT :   reversal date      erch,erdk  

                    EA13, EA14,EA15,

     PRINT DOCUMENTS ---> EA20, EA21. 

      EA22---> DISPLAY OF BILLING DOCUMENTS, 

7. ESTIMATE METER READING RESULTS :-

8. PERIODIC METER REPLACEMENT :-

         DEVICE MANAGEMENT :

                                      REGISTERS  and REGISTER GROUP,

                                      COMMAND GROUP,

                                      WINDING GROUP.

          BILLING MASTER DATA :-

               

                                       BILLING CLASS

                                       

                                       DATE CATEGORY,

                             

                                       DATE,

                                        PRICE,

                                       AMOUNT .

                






http://help.sap.com/saphelp_utilities472/helpdata/en/c6/4dc622eafc11d18a030000e829fbbd/frameset.htm

   

SCHEDULE MASTER RECORDES :-

   

       PARAMETER READING 

       MRU [METER READING UNIT]  -------> ABLEINH     [GENERATES THE DATES FOR ]

       PORTION.  [GENERATS THE BILLING DATE FOR THE ]

                        connection object :   as  b

                        premise                : 000002

                                             premise type ---may be   apartment ,  r   groups   r   individual r ...etc.

                               installation 

    

                     billing data ----> billing class , rate category.

 ES 32 -------> DISPLAYS INSTALLATION DATA.{premise, contract,billing class, mru,rate category}

GENERATE SCHEDULE RECORDS :-

          PORTION and MRU

          PORTION

          MRU

                               [before creation of MRU, schedule records must be generated].

INSTALLATION:  0000008

TECHNICAL MASTER DATA

   DEVICE LOCATION:  ANN

   DEVICE MANAGEMENT

   DEVICE CATEGORY

   REGISTER GROUP

BUSINESS PARTNER :
    TYPES OF BUSINESS PARTNER --->  PERSON, GROUP, ORGANIZATION.
  CONTRACT ACCOUNT---->   CAA1


FULL INSTALLATION.

   

          EL01  ---->  CREATE MRU AND UPLOADING SINGLE ENTRY    [MEATER READING ORDER]

          EL06 ------> METER READING ENTRIES

          EL28 ------> MASS DATA ENRY

          EL31 -------> MONITORING  OF METER READING

          EASIBI ----->  SINGLE DATA ENTRY   and  

                             BILLING [ERCH]      AND         INVOICING [ERDK],

          EAMABI ---->  FOR  MASS BILLING

  
SERVICE ORDER :-  AUFK            

           IW31 ---->  CREATION OF SERVICE ORDER,
           IW32 -----> CHANGE SERVICE ORDER,
           IW33 -----> FOR DISPLAY.

                 ALM_ME_ORDER_HEADER_GET_DETAIL   ---->  TO GET DETAILS OF PERTICULAR CREATED ORDER.
 REVERSALS  :-

           EA13, EA14, EA15 ---->  BILLING DOCUMENT

          EA20 , EA 21.-------->    PRINT DOCUMENT

DISPLAY OF BILLING DOCUMENT --> EA22.


ACCOUNT BALANCE DISPLAY ---> FPL9.
            FKK_COMPUTE_BALANCE.