Ansicht
Dokumentation
ISU_DEMAND40 - Season-Dependent Transfer of Register Operands
Fill RESBD Structure from EBP Component Structure General Data in Customer MasterThis documentation is copyright by SAP AG.
Operands and their Meaning
Input operands
DEMAND Measured demand
Output operands
DEMAND Name of demand of corresponding season period
DEMAND Name of demand of corresponding season period
DEMAND Name of demand of corresponding season period
DEMAND Name of demand of corresponding season period
FACTOR Number of relevant seasons
Functionality
The demand values symbolized by the input operands are allocated to the corresponding season periods by the allocation date of the meter reading. The calculation of average for the demand value takes place separately for each season period. The demand average is updated for the individual periods by the corresponding output operands. The season is allocated to the output operand as follows: The first season period in an alphanumeric sorting of season periods is allocated to the first output operand, the second season period to the second output operand and so on (->operand update)
The number of relevant seasons is also determined and forwarded by the FACTOR output operand. A season period is relevant if demand values were measured in the season period, and at least one demand value is marked as ACTIVE or ACTIVE IN CURRENT PERIOD deactivate demand value.
Note the following:
- Defining the season
- Define the season in the rate category facts or in the installation facts. Note that the number of season periods does not exceed the number of demand output operands.
- Properties of register operands
- You may not select the 'Demand per month' field.
- Using variants
- The variant is called up in a rate that is not affected by a rate change. This means that the rate must cover the entire billing period.
- Fewer season periods than output operands
- If you have defined fewer season periods than the number of existing output operands for demand, you must enter operands from category DEMAND in the remaining blank fields of the demand output operands. Note that these operands are not used further (dummy operands). If you have defined two seasons (for example SUMMER and WINTER), you must also supply data for the fields InpOp3 and InpOp4 with dummy operands.
- Number of relevant seasons
- Note that the number of relevant seasons in your schema structure can be zero. This situation is possible if using an IF construction.
Info Lines and Control Options
An info line is written about the number of relevant season periods. The data is entered in the following field:
ZAHL1 = number of relevant season periods
Example
A 3-peak average must first be calculated from the measured demand values depending on the season. The peak averages of the seaons are added together and divided by the number of season periods. The resulting demand is valuated with a price.
The following operands of category SEASON are stored in the facts:
SUMMER 04/01 - 09/30
WINTER 10/01 - 03/31
The schema can be structured as follows, for example:
Variant InpOp1 InpnOp2 OutOp1 OutOp2 OutOp3 OutOp4 OutOp5
DEMAND40 DEM_REG DEM_SOM DEM_WIN DEM_DUM1 DEM_DUM2 NUM_SAIS
DEMAND10 DEM_SOM DEM_WIN DEM_TOT
DEMAND09 DEM_TOT NUM_SAIS DEM_BILL
DEMAND01 DEM_BILL PRICE AMOUNT
The following demand values are available for billing:
Measured demand values Allocation date of meter reading
|----------------7 kW-----------------| 01/21/2000
|---------------10 kW-----------------| 02/25/2000
|---------------11 kW-----------------| 03/17/2000
|---------------12 kW-----------------| 04/14/2000
|---------------17 kW-----------------| 05/19/2000
|---------------16 kW-----------------| 06/28/2000
|---------------15 kW-----------------| 07/25/2000
|---------------12 kW-----------------| 08/08/2000
|---------------13 kW-----------------| 09/30/2000
|----------------9 kW-----------------| 10/12/2000
|----------------8 kW-----------------| 11/14/2000
|----------------9 kW-----------------| 12/25/2000
The DEMAND40 variant allocates the corresponding season to the demand values based on the allocation date of the meter reading. This means that the demand values for January, February, March, October, November and December are allocated to the WINTER season. The remaining demand values are allocated to the SUMMER season. The 3-peak average is calculated for each season. A demand average of 10kW is calculated for WINTER, and 16kW for SUMMER. The SUMMER demand (16kW) is updated by the first output operand DEM_SOM. The WINTER demand (10kW)is updated by the second output operand (DEM_WIN). The information about the number of relevant seasons is found in the output operand NUM_SAIS. Variant DEMAND10 adds together both season demands and makes the results available using operand DEM_TOT of variant DEMAND09. This determines the demand to be valuated from the total of season demands, and the number of relevant seasons (operand: NUM_SAIS), and updates a demand value of 13kW using operand DEM_BILL. Variant DEMAND01 valuates this demand with a price.
Parameters
XY_OBJXY_SOBJ
X_OP
X_RED
X_SS
Exceptions
GENERAL_FAULTREGULAR_ERROR
Function Group
EV05Vendor Master (General Section) TXBHW - Original Tax Base Amount in Local Currency
This documentation is copyright by SAP AG.
Length: 6192 Date: 20240523 Time: 130545 sap01-206 ( 123 ms )
