Bookshelf Home | Contents | Index | PDF     

Application Guide for Oracle Self-Service E-Billing (Business Edition) > Versioning Hierarchies >

Versioning Billing Hierarchies

Oracle Self-Service E-Billing saves the current form of the billing hierarchy. Table 80 lists and describes the use case functions.

Table 80. Versioning Billing Hierarchies
Function
Description

Name

Versioning Billing Hierarchies

Users

Oracle Self-Service E-Billing

Business Rules
  • The effective date is based upon the provider's reporting period. Reporting period is defaulted to one month. Service providers bill monthly and in rare cases the bills are cut on a frequency other than monthly, so the reporting period and effective dated hierarchies might be configured to match the provider's billing frequency.
  • The effective date is 12:00 AM from the first of the month until 12:00 AM on the first of the next month.

Main Path for Versioning a Billing Hierarchy

The following path describes the Versioning a Billing Hierarchy use case:

  1. Oracle Self-Service E-Billing stores the current version and effective date of all billing hierarchies on the first day of the month at 12:00 AM.
  2. Oracle Self-Service E-Billing carries over the current version of all billing hierarchies to the new month.

Alternate Paths for Versioning Billing Hierarchy

Alternate paths can occur in this use case.

Versioned Hierarchy is Purged

Oracle Self-Service E-Billing invokes the Purge use case.

Exceptions for Versioning a Billing Hierarchy

Exceptions can occur in this use case.

Oracle Self-Service E-Billing encounters an error during versioning

Oracle Self-Service E-Billing logs the error in the log file.

    
Application Guide for Oracle Self-Service E-Billing (Business Edition) Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.