SAP IS-U provides two different alternative means of applying the time-of-use interface in IS-U billing: 1) TOU-MDUS: Interval data is not uploaded to IS-U/EDM; instead, billing determinations are requested by IS-U from MDUS prior to the billing run, meaning that MDUS is used as a calculation engine) and 2) TOU-EDM (interval data is uploaded to IS-U/EDM and processed in calculations within IS-U billing) Advantages and disadvantages of these two alternatives are shown in the following:
This is the best choice regarding business processes, billing capabilities and user productivity
Interval data is stored twice, in MDUS and IS-U/EDM
MDUS is capable of running the straightforward processes. Further improvements for overcoming the disadvantages in poor business process integration are not planned by SAP. Instead, SAP recommends uploading interval data to SAP IS-U/EDM and using TOU-EDM as the more suitable and user-friendly approach. Furthermore, load tests conducted at SAP showed that TOU-EDM is capable of dealing with high interval data volumes.