Contents.
(abap isu) / Tables
1) IS-U Process with Technical Details .
2) Print workbench.
3) FQ Events.
[Link]
[Link]
[Link]
[Link]
--------------------------------------------------------------------------------------------------------------------------------------
IS-U Process with Technical Detail
In IS-U there are mainly two types of data.
Business Master Data (BMD) , Technical Master Data (TMD) .
1) Very First Process of IS-U is the registration of the Clients or Customers aka
business partners. Clients Fill their registration form and pays Sec. Deposit to the
organization.
Here the Business Partner and Contract Account Number gets created in BMD.
And Premise , Connection Object , [Link] gets created.
Business Partner can be a person, group or organisation with whom the utility
company has a business relationship. Company has a business relationship.
BP - Maintain Business Partner.
FPP1/2/3 - Create/Change/Display Contract Partner
Tables:
BUT000 Field PARTNER(10)
A contract account groups together all of a business partner’s contracts to which the
same payment and dunning data applies. It is an account through which the financial
transactions between a customer and a utility company are managed (stores payment
transaction data).
T-codes:
CAA1/2/3 - Create/Change/Display
Tables:
FKKVK, FKKVKP
Fields:
VKONT(12)
Connection Object is a building, piece of property or other facility that is connected to
the supply grid.
A connection object is allocated an address. It links premises, device locations etc. to a
postal regional structure.
T-codes:
ES55/6/7 - Create/Change/Display
Tables:
EHAUISU
Fields:
HAUS(30)
A premise is an enclosed spatial unit (such as an apartment or a factory) to which a
utility service is supplied. It is allocated to a Connection Object.
T-codes:
ES60/1/2 - Create/Change/Display
Tables:
EVBS
Fields:
VSTELLE(10)
Point Of Delivery.
POD Point to which a utility service is supplied, or for which a utility service can be determined.
T-codes:
EEDM09/10/11 - Point of Delivery Create/Change/Display
Tables:
EUITRANS, EUIINSTLN
Fields:
INT_UI(22), EXT_UI(50) - POD ID
2) After getting the Security Deposit the Service Notification to the THIRD Party Gets
created . For fitting the pipe lines to the customers.
3) After Service Notification Service Order gets generated.
In this process after closing conformation if Customer has used more length of pipes
then mentioned. He needs to pay extra so SALES Order also gets generated.
4) Technical Intsallation : All TMD data gets created.
The connection between premise, devices, and contract is referred to as an
installation.
An installation is allocated to a single contract.
Used to group together all devices that are allocated to same premise, belong to same
division and are to be billed together.
Several utility installations can be allocated to one premise (for different divisions, for
example). The premise is therefore not related to one specific division. A deregulated
scenario exists if more than one utility installation of the same division is allocated to a
premise.
The installation stores the billing properties for one or more devices at a premise
T-codes:
ES30/1/2 - Create/Change/Display
Tables:
EANLH(time slice), EANL
Fields:
ANLAGE(10)
Device Location is a location in a Connection Object where any number of
devices (across divisions) is installed. The device location provides information on the
physical location of the device
T-codes:
ES65/6/7 - Create/Change/Display
Tables:
EGPLT, EGPLTX
Fields:
DEVLOC(30)
Devices are physical objects. E.g. Counting Device (meter), controlling device (ripple
control receiver), data processing device (converter), device with protective or adjustive
functions (pressure controller) etc.
T-codes:
EG41,2/3/4 - Device Modification/Display /Create
Tables:
EGERS
Fields:
GERAET(18)
5) Full installation : BMD / TMD gets linked.
6) Official Customer Move in.
7) Creation Of Contract (Also in Move In Process).
A contract is an agreement between a utility company and a business partner
relating to a utility service. It forms the basis for billing. Created during move-
in process. It is specific to one Division.
T-codes:
ES20/21/22 - Create/Change/Display
ES27/8 - Change/Display Contracts for Contract Account
Tables:
EVER
Fields:
VERTRAG(10)
8) Meter Reading Order Gets Generated for MRU (Meter Reading Unit)
M.R Order gets generated which is given to the third party.
Meter Reading Upload.
9) Bill / Invoice Generation.
Billing Process.
10) Dunning Process
Notification
11) Disconnection Process
Service Order
Reconnection
Checklist payment
Service Order.
Other Terms
Move-in
A contract is created and allocated to an installation
T-codes:
EC50/1/2E (Create, Change, Display), EC53E (Reverse)
Tables:
EEIN (Cont. Acc.), EEINV (Contract)
Move-out
A contract with a customer is terminated
T-codes:
EC55/6/7E (Create, Change, Display), EC58E (Reverse)
Tables:
EAUS (Cont. Acc.), EAUSV (Contract)
Billing vs. Invoicing
Billing:
Consumption and bill amount calculation process
Performed at Contract level
Determine billing periods
Determine tariff (rate) data
Invoicing:
Process contract billing to contract account receivable and prepare printout
Performed at Contract Account level
Consolidate energy and non-energy charges, e.g. late payment fee
Consolidate all items from different contracts to be invoiced under the same contract
account
T-codes:
EASIBI
EAMABI
Tables:
Billing Document
T-codes:
EA22
Tables:
ERCH-BELNR(12)
Print Document
T-codes:
EA40
Tables:
ERDK-OPBEL(12)
Simulation
T-codes:
EASISI - Individual Simulation
EAMASI - Mass Simulation via Installation Intervals
-------------------