Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication⤷
IS-U-BI (Application Component) Contract Billing⤷
EE20 (Package) IS-U: Billing
Basic Data
| Data Element | SIMRUNSTATE |
| Short Description | Status of mass simulation run |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SIMRUNSTATE | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
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 | SimRunStat |
| Medium | 15 | Sim. run status |
| Long | 20 | Sim. run status |
| Heading | 2 | St |
Documentation
Definition
For actual (not simulated) billing, the analysis of billing documents ensures that each utility contract is completely billed. This prevents gaps in the billing period, or billed periods from being duplicated.
For mass simulation of installations and contracts, the same requirement exists, so that the data copied to the statistics can be interpreted. In contrast to actual billing, the analysis of billing documents cannot guarantee the consistency of billing periods.
Example:
- You create a contract with move-in date 7.1.1999.
- You bill the contract from 7.1.1999 to 6.30.2000. A further actual billing is not possible for this period without reversing the first billing.
- In mass simulation for 2000, you bill the contract from 07.01.2000 to 12.31.2000. You can repeat this simulation as often as you want, because simulated billing documents are not taken into account for the analysis of billing documents.
It is permissible to simulate a contract several times for the same period. To do this, IDs are used to identify mass simulation runs.
Example:
- You execute an unbilled revenue reporting for the year 2000 using ID 00000001. You create simulation indexes, one with key ID 00000001 and installation 0000200000. When this simulation index is billed, the results are copied to CO-PA version 01.
- You perform a further simulation with ID 00000002. You create a simulation index with key ID 00000002 and installation 0000200000. When this simulation index is billed, the results are copied to CO-PA version 02.
The following two procedures would cause errors:
- You perform unbilled revenue reporting for the year 2000 with ID 00000001. You create a simulation index with key ID 00000001 and installation 0000200000, and bill it. In doing so, the simulation index is deleted.
- You regenerate the simulation index with key ID 00000001 and installation 0000200000, and rebill it. The data for installation 0000200000 is copied twice to CO-PA in this case.
To avoid this operating error, each simulation index has a status field. Only the following actions are permissible, based on the status:
- Status 0 Create mass simulation indexes:
You may create simulation indexes using this status. You are not permitted to bill or delete the simulation indexes.
- Status 1 Bill mass simulation indexes
You may bill simulation indexes using this status. You are not permitted to create or manually delete the simulation indexes.
- Status 2 Inactive, delete mass simulation indexes
This status belongs to completed mass simulations. You may delete mass simulation indexes.
You must specify the mass simulation status. If you raise the status from 0 to 2 (bypassing 1), you can avoid the above mentioned problems.
Important: You must not change the status afterwards from 1 to 0.
Important: You must not change the status afterwards from 2 to 1, or from 2 to 0.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 463 |
