Below are some important basic terminology for SAP ISU Billing and it needs to be configured first.
Billing schema
Rate
Facts
Rate facts group
Price key
Operand
Rate category
Rate type
Rate determination
Master data creation (BMD + TMD )
Business master data.
1) Business partner: A person or legal entity with whom the organization has business relationship. It can be a customer, a vendor, an employee.
Transaction code: FPP1
2) Contract Account: Customer's account that has information about billing method, payment method,collection method and more.
Transaction code: CAA1
3) Contract: It is an agreement between business partner and the utility company.
Transaction code: ES30 (Contract is automatically created when customer is moved in to a premise)
Technical Master data:
1) Connection Object: It's a building, piece of property or other facility that is connected to the supply grid.
Transaction code: ES55
2) Premise: It is an enclosed spatial unit that is supplied with energy such as an apartment or a factory.
Transaction code: ES60
3) Device location: It provides the physical location of device (meter)
Transaction code: ES65
4) Installation: It stores billing properties for one or more devices at the premise.
Transaction code: ES30
Billing configuration:
1) Billing schema: Structure that defines the order in which variant programs for rates to be billed must be executed.
Transaction code: EA35
2) Billing class: It classifies installation for billing (example: residential, non-residential, non metered etc). Change in billing class also requires change in rate category. Final billing is not necessary upon changes. It can be valid for several rate categories. It serves the purpose of validation and statistical criterion. It controls the determination of the MRU in in the regional structure.
3) Variant program: It is a functional module in rates or schemas that contains a billing rule.
For example, one of the billing rule is consumption quantity(KWH)Xprice ($)= Total charge amount ($) is accomplished by variant program QUANTI01
4) Rate: It stores billing rules which are executed during billing run. It consists of steps and values of how to calculate billing quantity and amount. Each step is executed with variant program. Values of input and output parameters of rate steps (quantity, price, factor, amount etc) are determined historically at run time.
5) Facts: They are concrete values (such as 100 KW) or keys (for prices etc) that are allocated to operands and are valid for a specific period. According to the level on which facts are allocated, they can refer to installation facts, rate category facts or rate facts.
Installation facts have precedence over rate category facts and rate category facts have precedence over rate facts.
6) Rate fact group: Grouping of individual facts that are allocated to a rate. Several rate fact groups can be allocated to one rate. Rate fact groups enable you to use the same rate
Billing schema
Rate
Facts
Rate facts group
Price key
Operand
Rate category
Rate type
Rate determination
Master data creation (BMD + TMD )
Business master data.
1) Business partner: A person or legal entity with whom the organization has business relationship. It can be a customer, a vendor, an employee.
Transaction code: FPP1
2) Contract Account: Customer's account that has information about billing method, payment method,collection method and more.
Transaction code: CAA1
3) Contract: It is an agreement between business partner and the utility company.
Transaction code: ES30 (Contract is automatically created when customer is moved in to a premise)
Technical Master data:
1) Connection Object: It's a building, piece of property or other facility that is connected to the supply grid.
Transaction code: ES55
2) Premise: It is an enclosed spatial unit that is supplied with energy such as an apartment or a factory.
Transaction code: ES60
3) Device location: It provides the physical location of device (meter)
Transaction code: ES65
4) Installation: It stores billing properties for one or more devices at the premise.
Transaction code: ES30
Billing configuration:
1) Billing schema: Structure that defines the order in which variant programs for rates to be billed must be executed.
Transaction code: EA35
2) Billing class: It classifies installation for billing (example: residential, non-residential, non metered etc). Change in billing class also requires change in rate category. Final billing is not necessary upon changes. It can be valid for several rate categories. It serves the purpose of validation and statistical criterion. It controls the determination of the MRU in in the regional structure.
3) Variant program: It is a functional module in rates or schemas that contains a billing rule.
For example, one of the billing rule is consumption quantity(KWH)Xprice ($)= Total charge amount ($) is accomplished by variant program QUANTI01
4) Rate: It stores billing rules which are executed during billing run. It consists of steps and values of how to calculate billing quantity and amount. Each step is executed with variant program. Values of input and output parameters of rate steps (quantity, price, factor, amount etc) are determined historically at run time.
5) Facts: They are concrete values (such as 100 KW) or keys (for prices etc) that are allocated to operands and are valid for a specific period. According to the level on which facts are allocated, they can refer to installation facts, rate category facts or rate facts.
Installation facts have precedence over rate category facts and rate category facts have precedence over rate facts.
6) Rate fact group: Grouping of individual facts that are allocated to a rate. Several rate fact groups can be allocated to one rate. Rate fact groups enable you to use the same rate
but apply different operand values.
Example: Different prices for Victoria North
& Victoria South for SOLARIS & UNITED respectively
7) Price key:
8) Operand: Individually determined symbolic name for the assigned values that are used as input/output parameters in variant programs. One or more operands are allocated to an operand category.
Transaction code: EA50
9) Rate Category: It is classification of an installation for billing purposes. It contains one valid billing schema. It determines which outsorting billing checks occur during billing. In conjunction with rate type, it determines rates to be applied during rate determination process.
Transaction code: EA53
10) Rate type: It is classification of register, flat rate or reference value for billing purposes. Rate type is commonly allocated to register to classify the register type such as on peak, off peak, mid peak etc. It could also be allocated to device or installation level for use as a classification of flat rate or be a classification of reference value. In conjunction with rate category, it determines rates to be applied during rate determination.
11) Rate determination: In conjunction with rate category, rate type is used to determine the rate.
Transaction code: EA87
No comments:
Post a Comment