Hierarchy
⤷ IS-U-BI (Application Component) Contract Billing
⤷ EE20 (Package) IS-U: Billing
Basic Data
Data Element | OUT_MSIM |
Short Description | Meaning of Outsorting Check for Mass Simulation |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | OUT_MSIM | |
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 | Mass Sim. |
Medium | 15 | Mass Simulation |
Long | 20 | Mass Simulation |
Heading | 2 | MS |
Documentation
Definition
Enables you to define when an outsorting check occurs.
Use
The following values are permitted:
- ' ': The outsorting check applies without restriction. It is executed;
- During billing
- During mass simulations
- During other types of simulation
- 1: The check is not executed during mass simulations. It is executed during billing and other simulation types.
- 2: The check is only executed during mass simulations. It is not executed during billing and other simulation types.
Dependencies
During mass simulations, the system always uses the periodic billing transaction. Therefore, only use value 2 in the case of checks
relating to periodic billing transaction.
Example
Mass simulation is frequently used to simulate all the existing contracts and transfer the results to the statistics. It is essential to execute an outsorting check during a mass simulation, since an incorrect meter reading result can easily lead to a meter overflow. If a contract with a meter overflow is simulated, and an outsortung check is not executed, a very high, incorrect consumption (and therefore a very high incorrect revenue) is copied to the statistics.
You must also ensure that mass simulations do not use tolerance limits that are too strict, because the check may outsort very large numbers of contracts. We recommend that you use larger tolerances for the mass simulation than for billing. This control field enables you to do so. A possible configuration for the outsorting checks is shown below:
- You use outsorting check group 0001
- You create an automatic outsorting check for billing with
- Outsorting check group 0001
- Billing transaction periodic billing
- Mass simulation'1'
- Plausibility check with strict tolerances
- You create an additional automatic outsorting check for billing with
- Outsorting check group 0001
- Billing transaction periodic billing
- Mass simulation '2'
- Plausibility check with broad tolerances
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in | 471 |