Hierarchy
⤷ IS-U-BI (Application Component) Contract Billing
⤷ EE20 (Package) IS-U: Billing
Basic Data
Data Element | SAISON_SCHEMA |
Short Description | Season reference for rate step |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | E_OPERAND | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | TE221 |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Season |
Medium | 15 | Season |
Long | 20 | Season |
Heading | 10 | Season |
Documentation
Definition
You can enter an operand of the SEASON category in this field. By doing so, the entire rate step is allocated to a season. In billing, this rate step is restricted to the corresponding season period.
In the case of season-based billing, it is often sufficient to use season-based operand values in the facts. For example, you can then use different prices according to the season. In some cases, however, it might be necessary to apply entire rate steps to one season, for example, if you wish to:
- Execute different rate steps according to the season period, or
- Update different results for each season period
Restricting a rate step to a season can have different results according to the billing period:
Example:
You define the summer period from 4/1 to 9/30 and the winter period from 10/1 to 3/31. This can result in the following scenarios for a step that is allocated to the winter season:
- Billing period from 1/1 to 1/31: the winter step is executed completely (1/1 to 1/31).
- Billing period from 1/1 to 6/30: the winter step is executed partially (1/1 to 3/30).
- Billing period from 6/1 to 6/30: the winter step is not executed.
In addition, a season split could occur:
- Billing period from 1/1 to 12/31: the winter step is executed twice (1/1 to 3/30 and 10/1 to 12/31).
The season split, which results in the rate step being executed twice, is not possible for a few variant programs for technical reasons. For this reason, the rate step cannot be allocated to a season for rate steps with logic variants (IF, ELSE, ENDIF) and for deletion variants (UTILIT01, etc.). However, you can use these variants in season rates. When you structure the rate, you must note that the update to deletion variants occurs based on the season. This means you require different operands for each season.
Example:
You wish to create a rate that is valuated with different prices in the summer and winter seasons. In addition, best-rate billing is to be executed. Best-rate billing is to occur independently of one another in both seasons.
Diagram of the rate:
No. Program InpOp1 InpOp2 OutOp1 Season DeletOp
001 QUANTI01 ARBEIT WPREIS1 WBETRAG1 WINTER WBETRAG1
002 LUMSUM01 PAUSCH FAKTOR WBETRAG1 WINTER WBETRAG1
003 QUANTI01 ARBEIT WPREIS2 WBETRAG2 WINTER WBETRAG2
004 UTILIT02 WBETRAG1 WBETRAG2 WBETRAG
005 QUANTI01 ARBEIT SPREIS1 SBETRAG1 SOMMER SBETRAG1
006 LUMSUM01 PAUSCH FAKTOR SBETRAG1 SOMMER SBETRAG1
007 QUANTI01 ARBEIT SPREIS2 SBETRAG2 SOMMER SBETRAG2
008 UTILIT02 SBETRAG1 SBETRAG2 SBETRAG
Notes about the steps:
- In steps 001 and 002 the winter consumption is valuated with a price and a flat rate is charged.
- Alternatively the winter consumption is valuated with a higher price in step 003.
- The deletion variant in step 004 compares the winter amounts and deletes the billing line items that are not required.
- The deletion variant in step 008 compares the summer amounts that were calculated in the same way. Although step 008 is executed for the entire billing period, there is no update of winter amounts in this step.
The steps 001, 003, 005 and 007 use the same register operand ARBEIT. However, they are filled with different consumption values since the consumption is prorated in billing according to the validity period of the rate step.
Example:
You bill a contract from 1/1/1998 to 12/31/1998 with the rate illustrated above:
Billing period: I--------------------------------------I
1/1/98 12/31/98
You have maintained the season operand WINTER in the facts for the rate category. The winter season starts on 10/1 and ends on 3/31, which results in the following winter period for billing in 1998:
Winter season: I--------I I--------I
1/1/98 3/31/98 10/1/98 12/31/98
No rate change occurs in the billing period. The rate is therefore valid for the entire year:
Rate period: I--------------------------------------I
Rate steps 001 and 003 valuate consumption and are allocated to the season WINTER. In billing, the rate steps are limited to the winter season. Since there are two winter season periods in the billing period, the rate step is executed internally for two periods (season split):
Rate step 001: I--------I I--------I
Rate step 003: I--------I I--------I
Consumption totals 10,000 kWh for 1998. The consumption is prorated internally:
2500kWh 4500kWh 3000kWh
Consumption prorated: I--------I--------------------I--------I
Rate steps 001 and 003 are therefore provided internally with the consumption values 2500 kWh and 3000kWh, and each of them generate two billing line items. Rate steps 005 and 007 valuate the consumption 4500 kWh.
Note the following: best-rate billing in the winter season occurs only once in the case of a season split. The amounts for the billing line items from 1/1 to 3/31 and those for billing line items from 10/1 to 12/31 are added in step 004 for each operand. Following this addition the amounts are compared and one decision is made for both halves of the winter season.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |