Utility billing invoice types
By servicing type: residential, commercial, industries (generate service, large customer, congeneration) and miscellaneous
By utility type: electricity, water, heat and miscellaneous
By metering configration: aggregated, submetering, bulk unmetered, net metering/billing
Invoice Layouts are generated either for a batch run with a batch id (i.e. scheduled utility billing for entire building or region) or for a particular request with an invoice id (i.e. on-demand move-out invoice, interactive invoice request/generated by CSR).
Batch Invoice Report
Based on the input customer ID, the system looks up its corresponding layout configuration from the configuration database and invoice parameters and metering data from the meter database. Then the system will retrieve the count of invoices in the batch, as long as it is greater than 0, the system starts invoice generation job. In the SAP and Oracle setting, SAP will trigger the Oracle batch job to process XML data and generate invoice layouts.
On-demand Invoice Report
CSR selects the suitable print layout and set data prameters. The system validates the setting and data availability. An invoice id and specific url is generated. The invoice will be present on the customer portal under special report.
Invoice generation key parameters
The Oracle report package will check Sort_type, batch_mode, and invoice_number. The batch mode has a boolean value, and it is used for proper error handling determination; whereas invoice_number is used for on-demand invoice reporting only.
OCR checking for a paper invoice
The OCR marks at the button of the bill can be defined in various formats to help check bill printing integrity and invoice packaging and delivery.
The Print Workbench is the central development environment for creating standardized outgoing correspondence. It is used for printing in IS-Utilities. It is an easy way of creating forms and data retrieval for bill other data printing.
To configure the correspondence forms, the Print Workbench uses the SAP standard components for configuring forms – SAPscript or Smart Forms. It is a component of the Web Application Server.
The PWB has 2 subobjects:
- Form classes: form classes contain modeling and access instruction for all of the data that belongs to an application. Use can use the form classes to create application forms where you access the data defined in the form classes, such as invoices, dunning notices, and account statements.
- Application forms: use can define several application forms for each form class, such as different invoices for different business partners.
Application forms are configuration objects used for the application and integration of data structure defined in Form Class, and it can be integrated with different form layouts.