Procedure for New Billing
Documents 
To ensure that new billing documents including the Consumption History table are generated, you must insert a rate step in all the relevant rates for the variants, which update the Consumption History table. If you use dynamic period control, period-end billing or floating backbilling, ensure that you specify the IANCHO document line item type (ERCHZ-ERCHV anchor line) and the Reversable for Recalculation control for the variant. You can also exclude certain entries in the Consumption History table from the extraction to the BW system. You do this by setting the Not BW-Relevant indicator in the corresponding schema step.
Depending upon the SAP IS-U release status either all, or some, types of billing quantities (ARTMENGE field) are supported during the BW extraction. Up to SAP IS-U 4.63, the work quantity is extracted. As of SAP IS-U 4.64, the demand quantity is also extracted. As of SAP IS-U 4.71, all billing quantities are extracted to the BW system from the Consumption History table. You must install the following variants in all relevant rates:
· QUANTI23 (write consumption and amount in consumption history)
· DEMAND23 (write demand and amount in consumption history)
· LUMSUM22 (write amount from lump sum in DBERCHV)
· LUMSUM23 (write price independent amount in DBERCHV)
· SETTLE22 (write amount from rental price in DBERCHV)
See the documentation for these variants. You can display this by selecting the variant in the variant list (transaction EA99), and then branching to the information.
Once you have changed your rates, unlock the billing schemas in which you want to use these rates.
If you only have a small volume of data in your system, and do not (yet) want to write a program for building the Consumption History table, you can restrict yourself to this procedure. If this is the case (and provided the system has been configured accordingly), the extraction program performs a billing simulation for the consumption history. Billing is simulated for all contracts not yet billed using IS-U 4.63. The consumption history is created in the main memory but is not written to the database. You must therefore be prepared for long runtimes during data extraction.