SAP ABAP Data Element BILL_SIMPER_TO (Only Simulate to End of Simulation Period)
Hierarchy
IS-UT (Software Component) SAP Utilities/Telecommunication
   IS-U-BI (Application Component) Contract Billing
     EE20 (Package) IS-U: Billing
Basic Data
Data Element BILL_SIMPER_TO
Short Description Only Simulate to End of Simulation Period  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type KENNZX    
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 End Sim.P. 
Medium 15 Sim. to end of 
Long 20 Simul. to End of SP. 
Heading SE 
Documentation

Definition

If this field is selected, the billing simulation is run up to the end of simulation period (maximum).

Example

  • You define period 01/01/2001 to 12/31/2001 as the simulation period.
  • You run the mass simulation for contract 1000. Contract 1000 has already been billed up to and including 09/30/2001. The next periodic meter reading takes place on 09/30/2002 according to scheduling.
  • If you do not select the field, the contract is simulated internally during mass simulation for the following period: 10/01/2001 to 30/09/2002.
  • If you select the field, the contract is simulated internally during mass simulation for the following period: 10/01/2001 to 12/31/2001.

Note that during the update of simulation data for contract 1000 to CO-PA or to the UIS, only the period 10/01/2001 to 12/31/2001 is taken into account. The value in the field is irrelevent.

Field not selected:

If you do note select the field, each contract is generally simulated for one period in mass simulation. The period more or less corresponds to the periodic period. The billing is similar to the periodic billing. This has two advantages:

  • During best-rate billing and nonlinear weighting it is conceivable that another rate is used for the simulation of the whole year, than is used to simulate the summer months, for example. If you always run the mass simulation for a whole year, this increases accuracy.
  • During mass simulation, the outsorting checks for billing are run for the periodic billing transaction. The minimum and maximum amounts in the outsorting checks relate to a periodic billing. It is appropriate if a billing document that covers the entire periodic period is transferred to the outsorting checks.

We recommend that you use a simulation type in productive runs, where you do not select the field.

Field selected:

In the following cases we recommend that you use a simulation type, where you select the field:

  • You want to check the update to CO-PA or to the UIS in the test phase. Because the simulation documents no longer stand out from the simulation period if you have selected the field, your data is always completely transferred to CO-PA or to the UIS without prorations. This facilitates the comparison between simulation document data and the CO-PA or UIS data.
  • For technical reasons, it is not possible to simulate the simulation period (for example, missing Customizing for future periods).
  • You want to save and evaluate the simulation documents yourself. However, you do not want to prorate the end of the simulation period yourself.

Further information

  • The period for which a contract can be simulated in mass simulation, can also be changed by method SIM_METHOD_DETERMINE of business add-in ISU_BI_MASS_SIMUL. You can decide individually for each contract in this business add-in, which period should be simulated. See the documentation for the business add-in.
  • The simulation period of a contract always starts with its current start of billing period. The simulation period can start before the start of simulation period. This also applies if you have selected the field.

History
Last changed by/on SAP  20050224 
SAP Release Created in 464