Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U (Application Component) SAP Utilities⤷
EE80 (Package) IS-U: Customizing
IMG Activity
| ID | _ISUBISFGA_000047 | Gas Date |
| Transaction Code | S_KK4_82000484 | (empty) |
| Created on | 20010111 | |
| Customizing Attributes | _ISUBISFGA_000047 | Gas Date |
| Customizing Activity |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | _ISUBISFGA_000047 |
Gas Date
You use the gas date, during billing or the billing simulation with billing order,to determine the first access time for reading the gas data.
The date is calculated from the scheduled meter reading date during the order creation. This date is contained in the schedule record for the meter reading unit, or is entered during the single entry of a meter reading result.
You determine the gas date from the scheduled meter reading date, in accordance with the rules you define in IMG activity Define Allocation Data for Gas for each billing class and billing transaction. A gas month is determined, beginning from the scheduled meter reading date. The last day of the month is proposed as the gas date. If the gas date determined and the scheduled meter reading date lie in the same month, the system adopts the scheduled meter reading date as the gas date.
If you defined in the IMG activity that an input dialog box for the gas data is displayed, then you can still change the gas date in the defined area.
If meter reading data for a billing class and a billing transaction should be processed as a batch job, this input dialog box cannot be displayed. In this case, create an entry in the activity Define Allocation Data for Gas, for which the field Background Processing is selected.
IMG activity Define Allocation Data for Gas is not important for move-outs. First the system copies the scheduled meter reading date directly as the gas date. You can later correct this in move-out processing.
You can use enhancement EDMMR002 to change the date in the meter reading data entry. You can, for example, set the gas date to the actual meter reading date. At the moment, only the month and year of the gas date are used to define the access time.
In billing, a gas date is always contained in the latest time slice within a coherent record. If the gas date cannot be determined from the scheduled meter reading date, because the time slice taken into account results from the prorations, the To-Date of this time slice is used as the replacement value.
Example
The gas procedure was changed on 4.25. This means that both time slices must be processed separately. The gas date is 9.30.
1.1.|-------------|
|--------------------------------------|12.31.
4.25.
The gas date for the time slice 4.25 - 12.31 is 9.30. The replacement value for the gas date of time slice 1.1. - 4.24 is 4.24.
The allocation date for gas billing that you specified in the portion, is not important in gas billing.
Note that the move-in meter reading does not contain a gas date.
Special cases by postponement of the gas date
The gas date is used if the actual calorific values do not exist at the time of billing.
Carefully consider how much you need to postpone the gas month. Here are a few examples to demonstrate the possible negative effects if you postpone the gas month too much.
Averaging for the billing period
Example 1
The customer wants an interim bill in February.
|----------|9.1999 ----------|2.2000 ----------|
The gas month of the previous meter reading result is 9.1999. The gas month is 2.2000 (month from the to-date). The billing period is from 10.1.1999 - 2.28.2000. If the gas month is postponed the following extreme case is possible:
The gas month is postponed by 5 months (to 9.1999). Averaging takes place for just month 9.1999. This means that this average value is copied. There is also a calorific value that has nothing to do with the actual billing period.
You obtain the same result if the new gas month is before the previous meter reading.
Example 2
In the installation, two tenants have each lived for three months during the period 1.1.2000 - 6.30.2000.
|1.1.---------- |3.31.---------- |----------6.30.|
The gas month for the move-out of the first tenant is 3.2000, and for the second tenant 6.2000. The gas month is postponed for both tenants by 3 months. Therefore, the following applies for the second tenant:
Gas month = postponed gas month 3.2000
Back reading month = gas month of the previous meter reading + 1 month (= 1.2000), because this gas month was also postponed by three months.
The second tenant is billed using the calorific value average, for the months 1.2000 to 3.2000. Therefore he is billed for a period during which he never actually lived there.
Annual billing, averaging of the calorific value for one year.
If the gas month is postponed by the allocation of an installation to another portion, for example, it is possible that averaging takes place for a postponed period.
The portion of the installation has changed for the year 2000. For this reason, the billing period is 7.01 - 6.30 for the following year. In the first year after the changeover, the period 1.1 - 6.30 is billed. The following applies in this case:
Reading month = gas month of the new portion (5.2000)
Back reading month = gas month - 11 months (6.1999)
The average value is created for the period 6.1999 - 5.2000. The determined calorific value is valid for the whole billing period (1.1.2000 6.30.2000).
Special cases for monthly calorific values
Overwriting the gas month
Monthly calorific values are used without averaging. The billing period is one year.
The gas month is copied as the reading month, in the time slices in the period, in which the month of the to-date is later than the gas allocation date.
Example:
|--------------- ... --------------- |------------------------ |
1.1. ... 30.9.(gas date). 12.31.
There is one time slice for each month that begins on the first day of the month and ends on the last day of the month. The months that are later than the month of the gas date, are grouped together in one time slice. The calorific value is that from the month of the gas date.
|------ |------|--- ... ---|------| ------|------ |------|------ |
1.1. 2.1. 9.1. 12.31.
For the time slice 9.1. to 12.31, the calorific value for September is valid. For the remaining time slices, the calorific value of the corresponding month is valid. This means for January, the calorific value from January, and so on.
Underwriting the backreading month
Monthly calorific values are used without averaging. The billing period is one year.
For the time slices where the from-date is earlier than the back reading month, the back reading month is copied as the reading month.
Example 1
The gas month of the previous meter reading is 2.2000.
|------ |------ |------ |--------------------------------------|
12.1. 1.1. 2.1.
The billing period begins on 12.1.1999. In this case the first time slice is extended to 12.1.1999 - 2.29.2000.
Example 1
The gas date of the previous meter reading is 12.31.1999.
The following applies:
Back reading month = gas month of the previous meter reading + 1 month, (= 1.2000). In this case, the time slice from Januar 2000 is extended to 12.15.1999 - 1.31.2000. The calorific value from January is valid. The calorific value of the corresponding month is valid for all other time slices.
Requirements
Standard settings
Recommendation
Activities
Further notes
Business Attributes
| ASAP Roadmap ID | 204 | Establish Functions and Processes |
| Mandatory / Optional | 2 | Optional activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | _ISUBISFGA_000047 | 0 | I110004845 | Gas Billing |
Maintenance Objects
| Maintenance object type |
History
| Last changed by/on | SAP | 20010417 |
| SAP Release Created in | 463 |
