Ansicht
Dokumentation
ISU_COMPUT50 - Read Flat-Rate Price from Master Agreement with Pricing Quantity
CPI1466 during Backup ABAP Short ReferenceThis documentation is copyright by SAP AG.
Operands and Their Meaning
Input operands
- LPRICE Flat-rate price
- QUANT Pricing quantity
Output operands
FACTOR Factor determined
Functionality
A quantity is valuated with a price. In contrast to variant QUANTI01, a pricing quantity is also included. For block or scale prices, this pricing quantity is used, together with the amount tobe billed to determine the corresponding scale or block.The pricing quantity itself is not billed.
It is only advisable to use this variant if the price determination quantity in the billing period is not prorated. This is because in the case of a proration, only the most current value is considered. For a price proration, the pricing quantity acts as an entry point in the first period, and is then increased by the quantity to be billed. If the price determination quantity is prorated, the current value is then correct if the proration results from the price determination operand, and is not caused by dependencies in the schema. If a prorationoccurs as a consequence of a dependency in the schema, the block determination is accessed with a price determination quantity that is too low.
In this case, you can create variant ZQUANT11, which also calls the ISU_QUANTI11 function module and only differs in the properties in EA88 through the indicator Do not prorate (PRORATE2). Note that the indicator PRORATE2 can cause a termination in the operand update. This termination occurs when the unprorated output operand AMOUNT is updated in schema steps that require a proration. You can avoid this error by modifying the schema and selecting new operand names.
This customer variant is used for the following calculation:
Example
A block price has the following blocking and proration:
Prorated block price from price transaction.
01/01/2000 to 12/31/2000
Quanity Base Price Amount From Zone To Zone Zone Number
1.00 0.00000000 0 800 001
1.00 0.08200000 800 10000 002
1.00 0.03540000 10000 50000 003
1.00 0.00480000 50000 10000000 004
1.00 0.00000000 10000000 9999999999 005
01/01/2000 to 12/31/9999
1.00 0.12850000 0 10000 001
1.00 0.04270000 10000 50000 002
1.00 0.01310000 50000 10000000 003
1.00 0.00000000 10000000 9999999999 004
In a billing period from 08/01/2000 to 06/01/2001, the following adjusted blocking arises:
01/01/2000 to 12/31/2000
Quantity Base Price Amount From Zone To Zone Zone Number
1.00 0.00000000 0 353 001
1.00 0.08200000 353 4192 002
1.00 0.03540000 4192 20959 003
1.00 0.00480000 20959 4191781 004
1.00 0.00000000 4191781 9999999999 005
01/01/2001 to 12/31/9999
1.00 0.12850000 0 4164 001
1.00 0.04270000 4164 20822 002
1.00 0.01310000 20822 4164384 003
1.00 0.00000000 4164384 9999999999 004
The unprorated price determination quantity is 2425 kWh. The prorated consumption to be billed is 2807 kWh
(08/01/2000 to 12/31/2000) and 3124 kWh (01/01/2001 to 06/01/2001).
The following billing lines arise:
Quant. PriceAm. ,,Net Am.,,Zone Number
1767 * 0.0820 =,,144,89,,002
1040 * 0.0354 =,,36,82,,003
3124 * 0.0131 =,,133,39,,003
Info lines and control possibilities
ZAHL1 = Pricing quantity
MASS1 = Unit of measurement for pricing quantity
Example
With this variant you can use a contractually-agreed installation-specific quantity to determine a price.
Note for Price Block Adjustment
Price block adjustment
When you use price block adjustment (see price transaction EA89/90/91) the pricing quantity is accumulated over related price groups. This is a significant difference to QUANTI01. Here, the accumulated consumption is always initialized in the case of price zone adjustment at the start of a new price group.
Example of proration through changes to rate code:
P1 and P2 are two rate codes with the following prorated time slices in the billing period
|---------P1---------| |---------P2---------|
01/01 06/30 07.01 12/31
Consumption: 300 kWh Consumption : 400 kWh
and the following blocks
P1: 0 - 1200 : $1 P2: 0 - 1500 : $3
1200 - Infinite : $2 1500 - Infinite : $4
Price zone adjustment '1' is selected.
The following new blocks result from the block adjustment
P1: 0 - 600 : $1 P2: 0 - 750 : $3
600 - Infinite : $2 750 - Infinite : $4
If the pricing quantity from the current period (07/01 to 12/31) is 700 kWh, the following calculation is made in QUANTI11:
300 kWh * $2 (as 700 + 300 = 1000 lies in the second block of P1)
400 KWh * $4 (as 1000 +400 = 1400 lies in the second block of P2)
The accumulated 1000 kWh is considered as the price determination quantity over the price group limit P1 -> P2.
In contrast, in variant QUANTI01, the pricing quantity is initialized at the start of the new price group.
Because the initial pricing quantity is ALWAYS zero, the following calculations are made:
300 kWh * $1 (as 0 + 300 = 300 lies in the first block of P1)
400 kWh * $3 (as 0 + 400 = 400 lies in the first block of P2)
Example of proration through a price change with the same rate code:
P1 is a rate code with the following prorated time slices in the
billing period
|---------P1---------| |---------P1---------|
01/01 06/30 07/01 12/31
Consumption: 300 kWh Consumption: 400 kWh
P1: 0 - 1200 : $1 P1: 0 - 1500 : $3
1200 - Infinite : $2 1500 - Infinite : $4
Price block adjustment '1' is selected.
The period under review is one year. Therefore, the block limits are not changed.
When processing in QUANTI11 the following bill lines arise:
300 kWh * $1 (since 700 + 300 = 1000 < 1200 falls in the first block)
400 kWh * $3 (since 1000 + 400 = 1400 < 1500 falls in the first block)
The processing in QUANTI01 is the same, but without the pricing quantity
300 kWh * $1 (as 0 + 300 = 300 < 1200 falls in the first block)
400 kWh * $3 (as 300 + 400 = 700 < 1500 falls in the first block)
Parameters
XY_OBJXY_SOBJ
X_OP
X_RED
X_SS
Exceptions
GENERAL_FAULTREGULAR_ERROR
Function Group
EV35BAL Application Log Documentation ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 7868 Date: 20240523 Time: 102409 sap01-206 ( 84 ms )
