Application Guide for Oracle Self-Service E-Billing (Business Edition) > Hierarchy Administration >

Importing a Hierarchy


The purpose of this use case is to import a hierarchy. Table 77 lists and describes the use case functions.

Table 77. Importing a Hierarchy
Value
Description

Name

Importing a Hierarchy

Users

Business administrator user and manager user

Trigger

The user selects the Administration tab, and then the Import subtab.

Form Elements

Import Non-Billing Hierarchy form:

  • Select File (Required: XML file type only)

Business Rules

  • You can import non-billing hierarchies only. This includes both organization and consolidation hierarchy types.
  • Only XML file types can be imported that comply with the hierarchy load data format specification.
  • The name, type, and description of the hierarchy information must be contained with the imported file.
  • Validation of the XML source compliance with the definition of the hierarchy type specified within the file.
  • The user who initiates the hierarchy import is automatically assigned to the root node of the hierarchy if user's role is not and administrator.

Main Path for Importing a Hierarchy

The following path describes the Importing a Hierarchy use case:

1 The user selects the Administration tab.
  1. The user selects the Import subtab.
  2. Oracle Self-Service E-Billing displays the Import Hierarchy form.
  3. The user specifies the file to be imported, selects the periods, and then clicks Submit.
  4. Oracle Self-Service E-Billing reads the hierarchy metadata including hierarchy type, hierarchy name, and description data (if available) contained in the specified file.
  5. Oracle Self-Service E-Billing checks to confirm that the hierarchy name does not already exist.

    Oracle Self-Service E-Billing hierarchy validation passes.

  6. Oracle Self-Service E-Billing refreshes page with the graphical view of the hierarchy on the left pane and the hierarchy attributes on the right pane with the confirmation message stating Performing this operation will import the Hierarchy.
  7. The user clicks Submit.
  8. Oracle Self-Service E-Billing creates a new hierarchy from the imported data in an Unpublished status if no period is selected.
  9. Oracle Self-Service E-Billing indicates that it has successfully imported the hierarchy. It also displays the following information:
    • Hierarchy import criteria prepopulated with information read-in or entered by the user to create the imported hierarchy with the start and end periods.
    • Import status; the new name of the imported hierarchy along with the folder information and service agreements.
  10. The user confirms the imported hierarchy at the Manage tab.

Exceptions for Copying a Hierarchy

Exceptions can occur in this use case.

The User Encounters a Validation Error

Oracle Self-Service E-Billing invokes the validation error message use case.

The User or CSR Encounters a Server System Error

Oracle Self-Service E-Billing invokes the error message use case.

Alternate Paths for Copying a Hierarchy

Alternate paths can occur in this use case.

User Imports a Hierarchy that Already Exists in Oracle Self-Service E-Billing

Oracle Self-Service E-Billing displays a message A hierarchy of the same name already exists. Select submit to update the hierarchy.

The User Clicks Submit

Oracle Self-Service E-Billing updates and saves the hierarchy.

Oracle Self-Service E-Billing does not save the imported hierarchy.

The User Clicks Reset

Oracle Self-Service E-Billing runs the Reset use case.

The User Clicks Start Over
Application Guide for Oracle Self-Service E-Billing (Business Edition) Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.