Loading Historical Consumption Values from SAP IS-U 

DataSource 0UC_ISU_CONSUMPTION

The extraction date is the selection criteria for initializing the delta procedure. Instead of an individual value you can specify an interval. The upper limit of the interval is then interpreted as the extraction date. The extraction date has two meanings:

• All billing documents created or reversed two days before the extraction date are processed.

• All consumption months, up to and including the day before extraction are updated with consumption.

The analysis is executed for every contract. If the consumption months are not completely covered by the billing periods of the billing documents, the missing periods are extrapolated (provided you have selected this option in the settings for the extraction of marketing-relevant data). In order to enhance performance, the system only simulates billing for contracts that do not have a billing document containing consumption history. If not, the system uses the pre-consumption as a basis for the simulation. Key figure values extrapolated in this way are recorded in the OLTP and are given a minus sign during the next delta update to BW. This prevents new billed or extrapolated key figure values being determined. During the delta update, the extraction date remains the initialization selection criterion. However, internally, the system substitutes the extraction date for the system date. The actual extraction date of the delta update is recorded in the OLTP. During each delta update, the system processes all print documents that were created or reversed between either:

1) The (recorded) extraction date or

2) The previous delta update, and the day before the actual extraction date of the current delta update.

From the key date of the previous extraction run, the time passed is processed and assigned key figure values. All consumption months that either cover or overlap with this interval are updated.

Both the delta upload and the initialization of the delta upload generally provide key figure values for each contract.

The extraction date for the initialization of the delta update cannot be a date in the future. The initialization of the delta update behaves like a full upload with regards to the scope of the selected data. We recommend you perform a delta update once a month. This means you do not have to repeat the update and reversal of extrapolated key figure values for contracts and consumption months.

DataSource 0UC_ISU_CONSUMPT_02

In comparison to 0UC_ISU_CONSUMPTION, this DataSource has the advantage that data selection in SAP IS-U can be parallelized using a mass activity.

In this procedure, you build the extrapolation indexes before the data extraction. You do this by selecting the following menu path from the IS-U menu: Utilities Industry ® Information System ® Business Information Warehouse ® Mass Processing ® Prepare Indicies for Historical Consumption. No data is transferred when initializing the DataSource. For this reason, the extraction date is not intended for the selection in the scheduler in the BW system. The extraction is automatically set to the system date for each delta upload. (For a definition of an extraction date, see above).

A delta upload of this type occurs in two steps. First the delta is transferred to the delta queue, using a mass activity. You can find this in the IS-U menu, under Utiities Industry ®Information System ® Business Information Warehouse (BW) ® Mass Processing ® Update Historical Consumption in Delta Queue. Here, you can parallelize the processing by contract numbers. You can analyze the result of this mass activity, under Accounting → Financial Accounting → Contract Accounts Receivable and Payable → Periodic Processing → Administration of Mass Processing → Enhanced Message Management → Monitoring Mass Runs. Enter EBW_DQ_CS as the transaction code and select Prepared Jobs and Jobs Not Yet Prepared.

In a second step, the delta upload is triggered from the BW system.

For more details on this DataSource, see the documentation from the Business Content in SAP BW.