m6 operational reports

8/6/2019 M6 Operational Reports

1/140

Operational Reports

Release M/6.0 OR1First Edition

March 2004

MetaSolv Solution M/6.0


2/140

Copyright and Trademark Information

2004 MetaSolv Software, Inc. All rights reserved. MetaSolv is a trademark registered in the United States of

America by MetaSolv Software, Inc. CoManage, its associated logo, and Network-Driven are registered trade-

marks of CoManage Corporation. All other trademarks contained herein are property of their respective owners.Any rights not expressly granted herein are reserved. Information contained herein is subject to change without

notice.

DisclaimerAll references to future incorporation of new or enhanced product functionality, or to future release dates, are

estimates only, and MetaSolv may change them at any time, without notice. Information in this document is sub-

ject to change without notice and does not represent a commitment on the part of MetaSolv Software, Inc. All

references to new or enhanced product functionality, or to future release dates, are estimates only, and MetaSolv

may change them at any time, without notice.

The software and/or databases described in this document are furnished under a written license agreement or

nondisclosure agreement. No part of this document, the software and/or databases may be used, reproduced or

transmitted in any form or by any means, electronic or mechanical, including copying, photocopying, recording,

or information storage or retrieval systems, for any purpose without the written permission of MetaSolv Soft-

ware, Inc., except as specifically allowed in the written license or nondisclosure agreement. It is against the law

to copy the software on any medium except as specifically allowed in the license or nondisclosure agreement.

MetaSolv Software, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in

this manual.

Use of any of this Softwares functionality in a manner inconsistent with your license grant, whether or not pro-

tected by the Product ID, is a breach of the license agreement between your company and MetaSolv. A listing of

the software options for which you possess a license may be viewed by navigating to Options>Software Options.

This Software contains sample network system templates (Templates). MetaSolv does not provide, and is not

obligated to provide, Standard Maintenance and Support for the Templates or any modifications made thereto.

The Templates are delivered as is and without warranty of any kind.

Printed in U.S.A.

MetaSolv Software, Inc.

5560 Tennyson Parkway

Plano, TX 75024 U.S.A


3/140

Contents

Operational Reports Release M/6.0 OR1 1

Contents

About this guide .......................................................................................... i

Audience ................................................................................................................................iiBefore you begin ....................................................................................................................ii

How this document is organized ........................................................................................... iiiDocument Conventions .........................................................................................................iv

1. Whats New in Release M/6.0 OR1 .............................................................. 1

Universal Changes M/5.2 OR3 to M/6.0 OR1 ....................................................................... 1

Customer Universe ......................................................................................................... 1Ordering Universe .......................................................................................................... 1

Engineering Universe ..................................................................................................... 3Universal Changes M/5.2 OR2 to M/5.2 OR3 ....................................................................... 3

Customer Universe ......................................................................................................... 3Ordering Universe .......................................................................................................... 6Engineering Universe ..................................................................................................... 7

Universal Changes M/5.1 OR3 to M/5.1 OR4 ....................................................................... 8Customer Universe ......................................................................................................... 8

Ordering Universe ........................................................................................................ 10Engineering Universe ................................................................................................... 10

Universal Changes M/5.1 OR3 to M/5.2 OR2 ..................................................................... 11

Data Model Changes .................................................................................................... 11Engineering Universe ................................................................................................... 12

Ordering Universe ........................................................................................................ 16Universal Changes M/5.2 OR1 to M/5.2 OR2 ..................................................................... 17

CONVERT_GMT_TO_LOCALDB Stored Function ...................................................... 17

Data Model Changes .................................................................................................... 20Customer Universe ....................................................................................................... 20

Ordering Universe ........................................................................................................ 24Engineering Universe ................................................................................................... 26

Universal Changes M/4.3/4.5 OR1 to M/5.2 OR2 ............................................................... 30Data Model Changes .................................................................................................... 30

Customer Universe ....................................................................................................... 30Ordering Universe ........................................................................................................ 32

Engineering Universe ................................................................................................... 33Universal Changes M/5.0 OR1 to M/5.2 OR2 ..................................................................... 36

Data model ................................................................................................................... 36

Customer universe ....................................................................................................... 36Ordering universe ......................................................................................................... 38

Engineering Universe ................................................................................................... 38Integrity Results of Objects and Conditions ........................................................................ 42

Customer Universe ....................................................................................................... 42Engineering Universe ................................................................................................... 43Ordering Universe ........................................................................................................ 44


4/140

Contents

2 MetaSolv Software, Inc.

2. What is Operational Reports? ................................................................... 45

What is Business Objects? ................................................................................................. 45How is Business Objects structured? ........................................................................... 46

Solution structure .......................................................................................................... 46Installation .................................................................................................................... 47

Ongoing support and maintenance ..................................................................................... 48Other Business Object products ......................................................................................... 49

3. Using Operational Reports ........................................................................ 51

Versions .............................................................................................................................. 51

Procedures List ................................................................................................................... 52Business Object windows ............................................................................................. 54

Database connections .................................................................................................. 57Connections versus Repository Domains ..................................................................... 63

Installing a new MetaSolv Solution universe ................................................................ 65Creating a sandbox ...................................................................................................... 66

Creating categories for report kits ................................................................................ 67Installing a reporting kit ................................................................................................. 69Customizations ............................................................................................................. 72

Transfering customized universes and reports ............................................................. 75Moving repositories using an Oracle export ................................................................. 88

Upgrading universes ..................................................................................................... 96Upgrading reports ......................................................................................................... 98Known integrity issues ................................................................................................ 102

Downloading and compiling the CONVERT_GMT_TO_LOCALDB function .............. 103Optimizing report performance ................................................................................... 104

4. Universes, Kits, and Reports .................................................................. 105

Universe and report list ..................................................................................................... 105

Ordering universe ....................................................................................................... 105Customer universe ..................................................................................................... 105

Engineering universe .................................................................................................. 105Ordering Universe ............................................................................................................. 106

Service Request Reporting Kit ................................................................................... 106Work Management Reporting Kit ............................................................................... 108Provisioning Reporting Kit .......................................................................................... 109

Customer Universe ........................................................................................................... 111Customer/Security Reporting Kit ................................................................................ 111

Sales / Telephone Number Inventory Reporting Kit ................................................... 112Engineering Universe ........................................................................................................ 116

Navigating the Engineering Universe ......................................................................... 116Equipment Reporting Kit ............................................................................................. 118

Trouble Management Reporting Kit ............................................................................ 121

5. Frequently Asked Questions (FAQs) ..................................................... 125

General ............................................................................................................................. 125Universe ............................................................................................................................ 126

Reports .............................................................................................................................. 127


5/140

Contents


Security ............................................................................................................................. 128

Glossary .................................................................................................. 129


6/140

Contents



7/140

Operational Reports Release M/6.0 OR1 i

About this guide

This guide provides an overview on using Operational Reports and Business Objects within

the MetaSolv Solution. If you want to familiarize yourself with the features, processes, or

available reports before you use Operational Reports, or just learn about the new features or

functionality, then this book is for you. The information presented includes:

A Whats New document that details the latest updates and changes for the current release

An overview of how Operational Reports and Business Objects work together

Procedures for running reports, updating universes, and simple maintenance

A detailed description of the purpose and functionality of each report available in

Operational Reports

A Frequently Asked Questions (FAQ) section that addresses key questions regarding the

software


8/140

ii MetaSolv Software, Inc.

Audience

This guide is intended for three different types of groups who may use or maintain Operational

Reports.

Report writersincludes programmers, program analysts or system analysts who are

familiar with SQL and gather requirements for reports.

Technical staffincludes database administrators or system analysts who design, build,

and customize reports.

End-usersincludes management or administrative staff that generate or receive reports.

Before you begin

Before you can generate reports using Operational Reports, you must complete the following

items:

MetaSolv Solution must be installed. See the System Guide for your version of MetaSolv

Solution for information on database installation and upgrade. See online help for

information on client and server installation.

You have purchased the following products from Business Objects:

Designer

BusinessObjects (Reporter)

Supervisor

Please visit www.businessobjects.com/publications for a complete breakdown of software

and hardware requirements for each Business Objects product.

The Business Objects tools have been installed, configured, and are operational in your

companys environment.

One or more employees have completed Business Objects training and are familiar with

the installation, configuration, and operation of Business Objects in their companys

environment.

An Operational Reports reporting kit(s) has been installed, and an orientation with

MetaSolv Professional Services has been completed.


9/140

How this document is organized

Operational Reports Release M/6.0 OR1 iii

How this document is organized

This book is organized into five chapters. Use the following table to identify the chapter that

focuses on the information you need.

To learn about... See the following chapter...

Data model changes, new and deleted tables,

updated or new reports, new classes, objects, and

filters, or updated integrity results for objects and

conditions

"Whats New"

How Operational Reports and Business Objects

work together

"What is Operational Reports?"

Basic procedures and day-to-day maintenance "Using Operational Reports"

All the reports offered in Operational Reports and

their functionality

"Reports"

Quick answers or solutions regarding the reporting

application

"Frequently Asked Questions"


10/140

iv MetaSolv Software, Inc.

Document Conventions

The following conventions are used throughout this document to help you better identify

important items.

Convention Description Example

Bold Text Items you can click in the

software, such as buttons, menu

items, and fields

Click the New button.

Select List>Location from the main

menu.

Italics Places where you input

information or select an item from

a drop-down.

Enter your name in the Name field.

Select TXfrom the State drop-down.

Quotes Status The circuit is "In Progress" status.

Note

Warning


11/140


1

Whats New in Release M/6.0 OR1

Read this chapter to discover new features and changes in Operational Reports M/6.0 OR1.

Updates are grouped by release, then by universe. Each section contains the following

information (if applicable).

A brief overview of data model changes

A list of new and deleted tables

A list of updated or new reports

A list of new classes, objects, and filters

Updated integrity results for objects and conditions

Universal Changes M/5.2 OR3 to M/6.0 OR1

The following sections of the Operational Reporting Solution have undergone modifications

from release M/5.2 OR3 to M/6.0 OR1:

Customer Universe

Ordering Universe

Engineering Universe

Customer Universe

Class, object, and filter changes

Filters

Latest Tel Number Suffixlocated in Telephone/Telephone # Inventory. Identifies the latest

suffix for an NPA, NXX and Line Range.

Ordering UniverseThis section addresses design modifications and enhancements made to the Ordering universe.

To take advantage of the changes applied to the Ordering universe, you must upgrade the

universe. For more information, see "Upgrading Universes" on page 96.


12/140


13/140


14/140

Chapter 1: Whats New in Release M/6.0 OR1


SR_SALESPERSON_ROLE (Alias for SALESPERSON_ROLE )

SR_SALESPERSON (Alias for SALESPERSON )


Objects

Countlocated in the Telephone class/Telephone # Reservation subclass. Counts the total

number of rows for a defined group in a query. For example, it counts the number of reserved

telephone numbers in the Reservation report.

Serv Req Salesmodule Numberlocated in the Sales class/Sales Module subclass. ID that

relates an order to a sales module.

Serv Req Salesmodule Descriptionlocated in the Sales class/Sales Module subclass.

Identifies the Service Request sales module or sales group to be selected.

Serv Req Salesperson Full Namelocated in the Sales class/Sales Module subclass. The

salespersons complete name.

Filters

Prompt for Serv Req Salespersonlocated in the Sales class/Price subclass. Prompts for the

salespersons name.

Reports

To take advantage of the changes applied to the reports, you must install the upgraded or new

reports. For more information, see "Upgrading Reports" on page 98.

SQL Generator Checkbox

The Do not generate SQL before running checkbox needs to remain checked when running

reports against the MetaSolv universes. If the checkbox is unchecked and a report is refreshed

or rerun, Business Objects tries to rebuild the SQL based on the building blocks. The SQL

used by Business Objects is not the same as the SQL used in the report.

If the report has been run with the checkbox unchecked, you need to reimport the original

report from the product packaging.

Note: SR_SALES_MOD is the o riginal n ame of th e table. The oth ers are aliasessince a un iverse cannot h ave dup licate table names. Alias tables are used for

this relationship to prevent loops in the Customer un iverse.


15/140



This checkbox is found in the following reports in the Sales/Telephone Number Reporting Kit:

TN Aging of Disconnected Numbers

TN Capacity with Rate Center Report

TN Capacity Report

TN Thousands Group



Date Prompts

Date prompts must be entered manually for all reports. Any format can be used. Business

Objects converts the date to collect the correct information


16/140



Ordering Universe

This section addresses design modifications and enhancements made to the Ordering universe.



Tables

New

These new tables define the Order>Sales relationship.

LSR_PROVIDER_SERVICE_CENTER (alias for ACCESS_SERVICE_CENTER).


Filters

Complete > Revised-Potential Latelocated in the Work Management class/Task subclass.Compates the Completion Date on the task with the Revised Completion Date (the date the

task was scheduled for completion minus the Potentially Late Days. If the Actual

Completion Date is later than the Revised Completion Date minus the Potentially Late

Days, then the task is said to be late or potentially late.

Task Late # of Dayslocated in the Work Management class/Task subclass. Number of days

a task is late. If there is no actual completion date, the Revised Completion Date is subtracted

from todays date. If there is a completion date, the Revised Completion Date is subtracted

from the Actual Completion Date.

Task Late w/PL # of Dayslocated in the Work Management class/Task subclass. Task Late

with Potential Number of days a task is late. If there is no actual completion date, the Revised

Completion Date is subtracted from todays date. If there is a completion date, the RevisedCompletion Date is subtracted from the Actual Completion Date.

Reports



Date Prompts


Objects converts the date to collect the correct information


17/140




This section addresses design modifications and enhancements made to the Engineering

universe. To take advantage of the changes applied to the Engineering universe, you mustupgrade the universe. For more information, see "Upgrading Universes" on page 96.


Filters

Latest Tel Number Suffixlocated in the class/ subclass/ subclass. Returns the latest suffix

for a NPA, NXX, or Line range. This condition needs at least one columnn on the report

selected from the TEL_NUM_INV table.

Reports

To take advantage of the changes applied to the reports, you must install the upgraded or newreports. For more information, see "Upgrading Reports" on page 98.

Date Prompts


Objects converts the date to collect the correct information.


18/140






Customer Universe

Ordering Universe


Customer Universe

Tables

New

These new tables define the Order>Sales relationship. SR_SALES_MOD

SR_SALES_MODULE (Alias for SALES_MODULE )

SR_SALES_MOD_ROLE (Alias for SALES_MOD_ROLE )

SR_SALESPERSON_SALES_MOD_ROLE (Alias for

SALESPERSON_SALES_MOD_ROLE )

SR_SALESPERSON_ROLE (Alias for SALESPERSON_ROLE )

SR_SALESPERSON (Alias for SALESPERSON )


Objects

Countlocated in the Telephone class/Telephone # Reservation subclass. Counts the total

number of rows for a defined group in a query. For example, it counts the number of reserved

telephone numbers in the Reservation report.

Serv Req Salesmodule Numberlocated in the Sales class/Sales Module subclass. ID that

relates an order to a sales module.

Serv Req Salesmodule Descriptionlocated in the Sales class/Sales Module subclass.

Identifies the Service Request sales module or sales group to be selected.

Serv Req Salesperson Full Namelocated in the Sales class/Sales Module subclass. The

salespersons complete name.

Note: SR_SALES_MOD is the o riginal n ame of th e table. The oth ers are aliases

since a un iverse cannot h ave dup licate table names. Alias tables are used for

this relationship to prevent loops in the Customer un iverse.


19/140


20/140


21/140






Data Model


Ordering Universe

Data Model Changes

Changes are made to the data model with new releases of the MetaSolv Solution. The changes

include adding, dropping, and changing entities within the MetaSolv database. These changes

can be found in theDatabase Change Report (DBChange52.pdf) that is included with

MetaSolv Solution 5.2.


22/140





universe. To take advantage of the changes applied to the Engineering universe, you must

upgrade the universe. For more information, see "Upgrading Universes" on page 96.

Tables

New BANDWIDTH_ALLOCATION

NS_CON_REL

BANDWIDTH_CKT_BIT_RATE


Classes

Virtual Circuitscontains subclasses and objects with information pertinent to only virtual

circuits.

Subclasses

Bandwidth Allocationlocated in the Virtual Circuits class. Any virtual circuit not designed

in a template-based module.

Bandwidth Customerlocated in the Virtual Circuits class/Bandwidth subclass. Customer

information that pertains to virtual circuits not designed in a template-based module.

Customerlocated in the Circuit 1 class. Customer information specific to circuits.

Network Systemslocated in the Virtual Circuits class. Any virtual circuit designed or

modified in a template-based module.

Network Systems Customerlocated in the Virtual Circuits class/Network Systems

subclass. Customer information that pertains to virtual circuits designed or modified in a

template-based module.

Objects

Bandwidth Bit Ratelocated in the Virtual Circuits class/Bandwidth subclass. Bit rate of a

virtual circuit not designed in a template-based module.

Bandwidth Circuit Typelocated in the Virtual Circuits class/Bandwidth subclass. Circuit

type is populated when a virtual circuit is created. Values include Circuit or Virtual for a

circuit not designed in a template-based module.

Bandwidth Contact Namelocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. Contact information associated with a customer who has

ordered a virtual circuit not designed in a template-based module.


23/140



Bandwidth Customer Addresslocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. Customer address associated with a customer who has ordered

a virtual circuit not designed in a template-based module.

Bandwidth Customer Emaillocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. The email address associated with a customer who has ordered

a virtual circuit not designed in a template-based module.

Bandwidth Customer Namelocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. The Company name associated with a customer who has

ordered a virtual circuit not designed in a template-based module. An individual name is

returned if no company name is available.

Bandwidth Customer Tel Nbrlocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. The telephone number associated with a customer who has


Bandwidth Statuslocated in the Virtual Circuits class/Bandwidth subclass. Status of avirtual circuit not designed in a template-based module. Values include CLR-issued, In

Service, and Pending.

Circuit Location IDlocated in the Circuit 1 class/Circuit subclass. The originating network

location of a circuit.

Contact Namelocated in the Circuit 1 class/Customer subclass. The contact name

associated with a customer who has ordered a circuit.

CP Child Physi cal IDlocated in the Circuit 1 class/Circuit subclass. An Oracle sequence ID

that associates the child circuit position to the parent circuit position for a physical circuit. This

object is used to build the physical circuit hierarchy in advanced reporting.

CP Parent Physical IDlocated in the Circuit 1 class/Circuit subclass. An Oracle sequenceID that associates a parent circuit position to the child circuit position for a physical circuit.

This object is used to build the physical circuit hierarchy in advanced reporting.

Customer Addresslocated in the Circuit 1 class/Customer subclass. Customer address


Customer Namelocated in the Circuit 1 class/Customer subclass. Customer name


Customer Tel Nbrlocated in the Circuit 1 class/Customer subclass.Customer telephone

number associated with a customer who has ordered a circuit.

Equipment 5 CLLI Code Namelocated in the Equipment Level 5 class/Equipment 5

subclass. An eleven byte equipment CLLI code within a Network Location often used as thename of a piece of installed equipment.

Equipment 6 CLLI Code Namelocated in the Equipment Level 6 class/Equipment 6

subclass. An eleven byte equipment CLLI code within a Network Location often used as the

name of a piece of installed equipment.


24/140



Equipment Location IDlocated in the Equipment Level 7 class/Equipment 7 subclass. The

network location for an installed piece of equipment.

Net Sys Circuit Typelocated in the Virtual Circuits class/Network Systems subclass.

Circuit type is populated when a virtual circuit is created. Values include Circuit or Virtual

when the circuit is designed in a template-based module.

Net Sys Contact Namelocated in the Virtual Circuits class/Network Systems subclass/

Network Systems Customer subclass. Contact information associated with a customer who has

ordered a virtual circuit designed in a template-based module.

Net Sys Customer Addresslocated in the Virtual Circuits class/Network Systems subclass/

Network Systems Customer subclass. Customer address associated with a customer who has

ordered a virtual circuit designed in a template-based module.

Net Sys Customer Emaillocated in the Virtual Circuits class/Network Systems subclass/

Network Systems Customer subclass. The email address associated with a customer who has


Net Sys Customer Namelocated in the Virtual Circuits class/Network Systems subclass/

Network Systems Customer subclass. The company name associated with a customer who has

ordered a virtual circuit designed in a template-based module. An individual name is returned

if no company name is available.

Net Sys Customer Tel Nbrlocated in the Virtual Circuits class/Network Systems subclass/

Network Systems Customer subclass.The telephone number associated with a customer who

has ordered a virtual circuit designed in a template-based module.

Net Sys Statuslocated in the Virtual Circuits class/Network Systems subclass. Status of a

virtual circuit designed in a template-based module. Values include CLR-issued, In Service,

and Pending.Filters

Band Order Contacts Onlylocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. Returns only contacts associated to virtual circuits not

designed in a template-based module with a Contact Type ofOrder. The Contact Type field

is populated in the Customer Care module.

Band Primary Billing Contacts Onlylocated in the Virtual Circuits class/Bandwidth

subclass/Bandwidth Customer subclass. Returns only contacts associated to virtual circuits not

designed in a template-based module with a Contact Type ofPrimary Billing. The Contact

Type field is populated in the Customer Care module.

Band Primary Contacts Onlylocated in the Virtual Circuits class/Bandwidth subclass/

Bandwidth Customer subclass. Returns only contacts associated to virtual circuits not

designed in a template-based module with a Contact Type ofPrimary. The Contact Type

field is populated in the Customer Care module.


25/140



Equipment Loc ID = Circuit Loc IDlocated in the Equipment Level 7 class/Equipment 7

subclass. Returns only rows where the equipment ID and the circuit ID are the same. Circuits

can be associated with multiple locations, but equipment is associated with only one location.

Net Sys Order Contacts Onlylocated in the Virtual Circuits class/Network Systems

subclass/Network Systems Customer subclass. Returns only contacts associated to virtual

circuits designed in a template-based module with a Contact Type ofOrder. The Contact


Net Sys Primary Bill Contacts Onlylocated in the Virtual Circuits class/Network Systems


circuits designed in a template-based module with a Contact Type ofPrimary Billing. The

Contact Type field is populated in the Customer Care module.

Net Sys Primary Contacts Onlylocated in the Virtual Circuits class/Network Systems


circuits designed in a template-based module with a Contact Type ofPrimary. The Contact


Order Contacts Onlylocated in the Circuit 1class/Customer subclass. Returns only

customers associated to an ordered circuit with a Contact Type ofOrder. The Contact Type

field is populated in the Customer Care module.

Primary Billing Contact Onlylocated in the Circuit 1class/Customer subclass. Returns only

customers associated to an ordered circuit with a Contact Type ofPrimary Billing. The

Contact Type field is populated in the Customer Care module.

Primary Contact Onlylocated in the Circuit 1class/Customer subclass. Returns only

customers associated to an ordered circuit with a Contact Type ofPrimary. The Contact


Prompt for Eccktlocated in the Circuit 1 class/Circuit subclass. Prompts the user for a

circuit ID.

Reports



New

Equipment Assignments on Selected Circuit Reportlocated in the Equipment kit. Based

on a circuit ID, the report displays all equipment associated to the circuit by location.

Equipment with Circuit Assignments by Location Reportlocated in the Equipment kit.Lists all equipment in your network that have circuit assignments and their associations in all

locations.


26/140



Ordering Universe





Objects

Jeopardy Intervallocated in the Work Management class/Jeopardy subclass. Amount of

time a task was in jeopardy from creation to close. This object can only be applied to a

jeopardy task created after the MetaSolv Solution 5.2.1 Production Fix has been installed. This

object must be used in conjunction with the Closed Jeopardies in Audit Notes filter.

Jeopardy Interval DHMlocated in the Work Management class/Jeopardy subclass.

Amount of time a task was in jeopardy from creation to close. This object can only be applied

to a jeopardy task created after the MetaSolv Solution 5.2.1 Production Fix has been installed.The results are reported in the day-hour-minute format.

Jeopardy Interval Dayslocated in the Work Management class/Jeopardy subclass. Amount

of time a task was in jeopardy from creation to close. This object can only be applied to a

jeopardy task created after the MetaSolv Solution 5.2.1 Production Fix has been installed. The

results are reported in a day format.

Jeopardy Interval Hourslocated in the Work Management class/Jeopardy subclass.

Amount of time a task was in jeopardy from creation to close. This object can only be applied

to jeopardy task created after the MetaSolv Solution 5.2.1 Production Fix has been installed.

The results are reported in a hour format.

Jeopardy Interval Minuteslocated in the Work Management class/Jeopardy subclass.Amount of time a task was in jeopardy from creation to close. This object can only be applied

to jeopardy task created after the MetaSolv Solution 5.2.1 Production Fix has been installed.

The results are reported in a minutes format.

Filters

Closed Jeopardies in Audit Noteslocated in the Work Management class/Jeopardy

subclass. Limits the data returned to only jeopardies that have been closed and were created

after the MetaSolv Solution 5.2.1 Production Fix was installed.

Jeopardies in Audit Noteslocated in the Work Management class/Jeopardy subclass.

Limits the data returned to only jeopardies that were created after the MetaSolv Solution 5.2.1

Production Fix was installed.


27/140






Convert_GMT_TO_LOCALDB Stored Function

Data Model

Customer Universe

Ordering Universe


For the complete list of updates, please refer to "Universal Changes M/5.1 OR3 to M/5.2

OR2" on page 11, and the items listed below.

CONVERT_GMT_TO_LOCALDB Stored FunctionMany dates and times that are stored in the MetaSolv Solution database are stored at

Greenwich Meantime. Using these dates or times in reports can be misleading, since the date-

time reported may not be the time in your area. To make these date columns more accurate in

reporting, the date objects have been duplicated in the universes that use them. One version of

the date object remains as the GMT date and the object name has been appended with "GMT."

A duplicate date object was created, but without the GMT extension.

This version of the object has been defined using a new stored function,

CONVERT_GMT_TO_LOCALDB, that must be compiled to the target database before using

these objects in reports. This function applied to the GMT date objects in the database converts

the GMT date to the date of the time zone that the database is located in.

The date-time objects impacted by this new stored function are listed below:

Universe Name Class/Subclass Name Object Name

Engineering Trouble/Trouble Tickets/Trouble

Ticket

Ckt In Service Dt


Ticket

Close Dt (MM-DD-YYYY)


Ticket

Close Dt (YYYY)


Ticket

Status Last Modified Dt


Ticket

State Last Modified Dt


28/140




Ticket

Restore Dt


Ticket

Open Dt (MM-DD-YYYY)


Ticket

Open Dt


Ticket

Next Cust Status Dt


Ticket

Next Activity Dt


Ticket

Defer Until Dt


Ticket

Close Dt (MM-YYYY)


Ticket

Close Dt


Ticket

Cleared Dt


Ticket

Trbl Detect Dt

Engineering Trouble/Trouble Tickets/Trbl

Task

Create Date


Task

Actual Start Date


Task

Actual Completion Date


Task

Last Modified Date

Ordering Work Mgmnt/Task Task Scheduled Completion Dt

Ordering Work Mgmnt/Task Task Revised Completion Dt

Ordering Work Mgmnt/Task Task Estimated Completion Dt



29/140



In addition to the new date objects, all of the conditions (filters) in the reporting universes that

refer to any of the GMT dates have been altered to refer to the converted dates. The condition

objects that have been modified are listed below.

The stored function is SQL code that must be loaded into SQL*Plus (or any stored procedure

editor that can compile procedures to the Oracle database), and compiled to the target

database. For existing customers, the installation is done by a DBA. The stored function is

delivered with both the Engineering and the Ordering universe, so the compilation procedure

Ordering Work Mgmnt/Task Task Actual Release Date

Ordering Work Mgmnt/Task Task Actual Completion Date

Ordering Work Mgmnt/Jeopardy Jeopardy Esc Date Entered

Ordering Work Mgmnt/Jeopardy Jeopardy Date Closed

Ordering Work Mgmnt/Jeopardy Jeopardy Follow up Date

Universe Name Class Name Condition Name


Ticket

Prompt for Open Date Range


Ticket

Prompt for Close Date Range

Ordering Work Mgmnt/Task Prompt Task Actual Comp Date

Range

Ordering Work Mgmnt/Task Prompt Task Sched Comp Date

Range

Ordering Work Mgmnt/Task Task Completion Date < Today's

Date

Ordering Work Mgmnt/Task Prompt Task Revised Comp Date

Range

Ordering Work Mgmnt/Jeopardy Prompt Jeopardy Closed Date

Range

The dates above only occur in the Ordering and the Engineering universes. If you are only using

the Customer universe, you do not have to make any modifications.



30/140



only has to be executed one time. For step-by-step instructions on how to download and

compile the function, see page 103.

Data Model ChangesChanges are made to the data model with new releases of the MetaSolv Solution. The changes




Customer Universe

This section addresses design modifications and enhancements made to the Customer

universe. To take advantage of the changes applied to the Customer universe, you must


Tables

New COMPANY

SERV_ITEM_VALUE


Subclasses

Service Itemslocated in the Service class. A service item is any item that can be ordered by

a customer. The subclass was created to group all service item objects.

Objects# of Reserved Dayslocated in the Telephone class/Telephone # Pooling subclass. The SQL

was changed to subtract the Date Received from the Reserve Until Date.

% Utilization of Blocklocated in the Telephone class/Telephone # Pooling subclass. The

percentage of telephone numbers that have been used (do not have a status of Unassigned or

Disconnected) in a telephone block of 1000 numbers.

% Utilization of Inventorylocated in the Telephone class/Telephone # Pooling subclass.

The percentage of telephone numbers that have been used (do not have a status of

Unassigned or Disconnected) in the telephone number inventory.

Available TN Statuslocated in the Telephone class/Telephone # Pooling subclass. The

object now excludes the Disconnected status.

Block Holderlocated in the Telephone class/Telephone # Pooling subclass. The Operating

Company Number (OCN) that owns a thousand block line range.

Code Holderlocated in the Telephone class/Telephone # Pooling subclass. The OCN that

owns a ten thousand block line range.


31/140



End Office IDlocated in the Telephone class/Telephone # Pooling subclass. The object is

used in conjunction with the End Offices Only object to build subqueries to retrieve only End

Offices.

End Office Namelocated in the Telephone class/Telephone # Pooling subclass. The object

name was changed to Central Office Exchange Area anywhere the object currently appears

because the object is pulling central office information. If you want to pull end office name

information, use the new object, End Office Name.

End Offices Onlylocated in the Telephone class/Telephone # Pooling subclass. The object

is used in conjunction with the End Office ID object to build subqueries to retrieve only end

offices.

Rate Centerlocated in the Telephone class/Telephone # Pooling subclass. The object

returns the Rate Center Name instead of the Network Area Name.

Responsible Org for TN Poolinglocated in the Telephone class/Telephone # Pooling

subclass. The OCN, code holder, or block holder that owns the line range.

Serv Item Label Codelocated in the Service class/Service Items subclass. This object

represents the code given to any item that can be ordered from the product catalog. A value

label is associated with each label code. The service request associated with this service item

has been completed.

Serv Item Valid Valuelocated in the Service class/Service Items subclass. The value

associated with the Serv Item Value Code in the product catalog. A value code may have

more than one valid value. The service request associated with this service item has been

completed.

Serv Item Value Codelocated in the Service class/Service Items subclass. The user-defined

identifier that describes the value. This object is used in conjunction with theServ Item Valid

Value. The service request associated with this service item has been completed.

Serv Item Value Labellocated in the Service class/Service Items subclass. The label used to

collect values for a service item during the ordering process. This label is used in conjunction

with the Serv Item Label Code . The service request associated with this service item has been

completed.

Serv Req SI Label Cdlocated in the Service class/Service Item subclass. This object

represents the code given to any item that can be ordered from the product catalog. A value

label is associated with each label code. The service request associated with this service item

has not been completed.

Serv Req SI Valid Valuelocated in the Service class/Service Item subclass. The value that

is associated with the Serv Item Value Code in the product catalog. A value code may havemore than one valid value. The service request associated with this service item has not been

completed.


32/140



Serv Req SI Value Cdlocated in the Service class/Service Item subclass. The user-defined

identifier that describes the value. This object is used in conjunction with the Serv Item Valid

Value. The service request associated with this service item has not been completed.

Serv Req SI Value Labellocated in the Service class/Service Item subclass. The label used

to collect values for a service item during the ordering process. This label is used in

conjunction with the Serv Item Label Code. The service request associated with this service

item has not been completed.

Telephone N umber Statuslocated in the Telephone class/Telephone # Inventory subclass.

Changed the decode status from 2 to 7 for pending disconnect.

Telephone Number Status Countlocated in the Telephone class/Telephone # Inventory

subclass. Changed the decode status from 2 to 7 for pending disconnect.

TN Block Sizelocated in the Telephone class/ Telephone # Pooling subclass. Calculates the

size of the telephone number block owned by a block holder. This object uses the TNI Line

Range Low and the TNI Line Range High objects.

TNI Line Range Highlocated in the Telephone class/Telephone # Pooling subclass. The

object name was changed to TNI Actual Line Range High anywhere the object currently

appears because the object is pulling the actual highest telephone number in a block that has

been inventoried. TNI Line Range High now calculates the size of the telephone number

block owned by a block holder. This object uses the TNI Line Range Low and the TNI Line

Range High objects.

TNI Line Range Low located in the Telephone class/Telephone # Pooling subclass. The

object name was changed to TNI Actual Line Range Low anywhere the object currently

appears because the object is pulling the actual lowest telephone number in a block that has

been inventoried. TNI Line Range Low now pulls the lowest telephone number in an entire

block range regardless if the numbers have been inventoried.

Used TN Statuslocated in the Telephone class/Telephone # Pooling subclass. This object

pulls all telephone numbers that dont have a status of Unassigned or Disconnected.

Filters

Customer Not Null for Requestlocated in the Telephone class/Telephone # Request

subclass. Prompts the user that the customer information must be completed on the service

request to be included in the report.

Date Received is Not Nulllocated in the Telephone class/Telephone # Request subclass.

Prompts the user that the date received information must be completed in the telephone

number reservation to be included in the report.

Prompt Block Holderlocated in the Telephone class/Telephone # Pooling subclass.

Prompts the user for the name of the block holder, responsible organization, or OCN that owns

the telephone number block. You can select one or multiple OCNs.


33/140



Prompt End Office Namelocated in the Telephone class/Telephone # Pooling subclass. The

filter name was changed to Prompt for CO Exchange Area Name anywhere the filter

currently appears. Prompts the user for the end office name.

Prompt Resp Org for TN Poolinglocated in the Telephone class/Telephone # Pooling

subclass. Prompts the user for the name of the code holder or block holder for a telephone

number block. You can select one or multiple code or block holders.

Reports



New

Customer Price Info by Product Reportlocated in the Customer & Security kit. Pulls

customer information, service items ordered by a customer, and pricing information for those

service items. Used to track product changes in order to notify customers of pricing changes orproduct cancellations.

Updates

LIDB/CNAM Database Service Provider Ported NXX Notification Reportlocated in the

Sales/Telephone Number Inventory Reporting kit. The Central Office Exchange Area field

was changed to End Office Name. The OCN field was replaced with the Block Holder field.

LIDB/CNAM Database Service Provider Ported NXX Notification with Rate Center

Reportlocated in the Sales/Telephone Number Inventory Reporting kit. The Central Office

Exchange Area field was changed to End Office Name andthe OCN field was replaced with

the Block Holder field.

TN Aging of Disconnected Numbers Reportlocated in the Sales & Telephone Number kit.The Central Office Exchange Area field was changed to End Office Name andthe Block

Holder field was added.

TN Capacity Reportlocated in the Sales & Telephone Number kit. The Block Holder field

has been added to the report and the Central Office Exchange A rea field was changed to End

Office Name.

TN Capacity with Rate Center Reportlocated in the Sales & Telephone Number kit. The

Block Holder field has been added to the report and the Central Office Exchange Area field

was changed to End Office Name.

TN Reservation Aging Reportlocated in the Sales & Telephone Number kit. The Block

Holder field has been added to the report and the Central Office Exchange Area field was

changed to End Office Name .

TN Thousands Group Reportlocated in the Sales & Telephone Number kit. The Block

Holder field has been added to the report and the Central Office Exchange Area field was

changed to End Office Name .


34/140



Ordering Universe




Tables

New SERV_ITEM_VALUE

SERV_REQ_SI_VALUE

SI_CA_MULTI_VALUE

SI_CA_VALUE

Class, object, filter, and hierarchy changes

Subclasses

Service Itemslocated in the Service Request class. A service item is any item that can be

ordered by a customer. The subclass was created to group all service item objects.

Objects

Serv Item Value Labellocated in the Service class/Service Items subclass. The object is

used to collect values for a service item during the ordering process. This label is used in

conjunction with the Serv Item Label Code. The service request associated with this service

item has been completed.

Serv Item Valid Valuelocated in the Service class/Service Items subclass. The value

associated with the Serv Item Value Code in the product catalog. A value code may have

more than one valid value. The service request associated with this service item has beencompleted.

Serv Req On Time Order Countlocated in the Service Request class. Counts all service

requests that were completed on or before the desired due date.

Serv Req Service Itemslocated in the Service Request class/Service Items subclass. The

object name was changed to Serv Item Name and was moved to the Service Items subclass.

Serv Req Level 1 Itemslocated in the Service Request class/Service Items subclass. The

object name was changed to Serv Item Level 1 Items and was moved to the Service Items

subclass.

Task Actual Completion Intervallocated in the Work Management class/Task subclass.

The number of days it took to complete the task. Calculated by subtracting the actual

completion date of a task from the actual date a task went into "Ready" status.


35/140



Task Schedul ed Completion Intervallocated in the Work Management class/Task

subclass. The number of days calculated by subtracting the revised completion date from the

scheduled date a task is scheduled to go into "Ready" status plus the revised completion date

minus the scheduled completion date.

Filters

Exclude On Time Completed Taskslocated in the Work Management class/Task subclass.

Excludes tasks that were completed on or before the revised completion date.

Prompt for Amount of Dayslocated in the Work Management class/Task subclass. Prompts

user for the number of days to query for tasks that are late or potentially late.

Prompt for Amount of Days Latelocated in the Work Management class/Task subclass.

Prompts the user for the number of days a task is late. This filter allows for a more refined

search of late task information.

Hierarchy

Work QueueProvides drill-down capability from Work Queue to Employee.

Reports



New

Late & Potentially Late Incomplete Tasks Reportlocated in the Provisioning kit. Displays

scheduled completion intervals, actual completion intervals, and number of days late for tasks

and work queues. Used to see which tasks or work queues are late or will be late.

Service Request Tracking Summarylocated in the Service Request kit. Calculates thecompletion time for a service request. It displays the actual completion interval or the current

duration if the service request is not complete. Used to calculate average process time for a

service request.

Updates

Work Queue Productivity Reportlocated in the Provisioning kit. The title was changed to

Work Queue Productivity Summary . Drill-down functionality was added from Work Queue

to Employee Full Name and from Work Queue ID to Employee Full Name .


36/140








Subclasses

Affected Customerslocated in the Trouble class. Objects and relationships that collect

customer information associated to a circuit for which trouble issues exist.

Child Ticketslocated in the Trouble class. Child circuits associated to a parent circuit for

which trouble issues exist.

Orderslocated in the Trouble class. Order information for related service items for which

trouble issues exist.

Serv Req Orderlocated in the Trouble class/Orders subclass. Information related to service

requests that are associated with a trouble ticket.

Serv Req SI Orderlocated in the Trouble class/Orders subclass. Contains information

related to service items for which trouble issues exist.

Trouble Circuitlocated in the Trouble class. Contains objects that are related to circuits that

have trouble issues associated with them.

Trouble Ticket Linkedlocated in the Trouble class/Child Tickets subclass. Information

regarding child trouble tickets associated with a parent trouble ticket. The child tickets are

linked to their parent ticket via the SR_RELATIONSHIP table.

ObjectsActivity Indlocated in the Trouble class/Orders subclass/Serv Req Order subclass. The

activity for an order, such as "New", "Disconnect", or "Change."

Avg Creation-Restoration DHMlocated in the Trouble class/Trouble Tickets subclass/

Trouble Ticket subclass/Trouble Time Objects subclass. Average amount of time from the

creation date of a trouble ticket until the time until it is cleared. The results are reported in the

day-hour-minute format.

Avg Creation-Restoration Minuteslocated in the Trouble class/Trouble Tickets subclass/

Trouble Ticket subclass/Trouble Time Objects subclass. Average amount of time from the

creation date of a trouble ticket until the time it is cleared. The results are reported in the

minutes.

Circuit Node Statuslocated in the Circuit 2 class/Circuit Position subclass. Describes the

current status of the circuit position or node. For example, "In Service" or "Trouble."

Count of Status for Assignedlocated in the Circuit 2 class/Circuit_A subclass. The number

of circuits without an "Unassigned" status.


37/140


38/140



Creation-Restoration Minuteslocated in the Trouble class/Trouble Tickets subclass/

Trouble Ticket subclass/Trouble Time Objects subclass. Actual amount of time from the

creation date of a trouble ticket until the time it is cleared. The results are reported in the

minutes format.

Exchange Carrier Circuit IDlocated in the Trouble class/Trouble Circuit subclass. The

ECCKT or circuit ID issued for a circuit by the Other Exchange Carrier (OEC).

Order Numberlocated in the Trouble class/Orders subclass/Serv Req Order subclass. The

order number of the service request that originally ordered the circuit that is now in trouble.

Restore to Close DHMlocated in the Trouble class/Trouble Tickets subclass/Trouble Ticket

subclass/Trouble Time Objects subclass. Amount of time a trouble ticket takes from a

"Cleared" to a "Closed" status. The results are reported in the day-hour-minute format.

Restore to Close Minuteslocated in the Trouble class/Trouble Tickets subclass/Trouble

Ticket subclass/Trouble Time Objects subclass. Amount of time a trouble ticket takes from a

"Cleared" to a "Closed" status. The results are reported in minutes.

Sum Creation-Restoration DHMlocated in the Trouble class/Trouble Tickets subclass/

Trouble Ticket subclass/Trouble Time Objects subclass. The total time from "Cleared" to

"Close" status for all trouble tickets on the report. The results are reported in the day-hour-

minute format.

Sum Creation-Restoration Minuteslocated in the Trouble class/Trouble Tickets subclass/

Trouble Ticket subclass/Trouble Time Objects subclass. The total time from "Cleared" to

"Close" status for all trouble tickets on the report. The results are reported in minutes.

Sum of Facility Channels (Fac)located in the Circuit 2 class/Circuit_A subclass. The total

number of channels that are facilities on the report.

Sum of Specia l Channels (Fac)located in the Circuit 2 class/Circuit_A subclass. The totalnumber of special channels on the report.

Sum of Trunk Channels (Fac)located in the Circuit 2 class/Circuit_A subclass. The total

number of trunk channels on the report.

Filters

Prompt A or Z CLLI Codelocated in the Circuit 2 class/Network Location A Loc subclass.

Prompts user for an originating or terminating CLLI code.

Prompt A or Z CLLI Codelocated in the Circuit 2 class/Network Location Z Loc subclass.

Prompts user for an originating or terminating CLLI code.

Prompt for Circuit Rate Codelocated in the Circuit 1 class/Circuit subclass. Prompts the

user for the rate code associated with the circuit.

Prompt for CP Rate Codelocated in the Circuit 2 class/Circuit Position subclass. Prompts

the user for the rate code of the circuit with a parent/child relationship.


39/140



Reports



New

Capacity by Vendor and CLLI Reportlocated in the Equipment Reporting Kit. Based on a

selected vendor, the report returns vendor, CLLI, and capacity information. Used to view

equipment capacity.

Circuit Capacity Reportlocated in the Equipment Reporting Kit. Graphically represents

originating and terminating locations, and how many facilities are inventoried and vacant.

Used to track capacity between locations.

Facility Circuit Position Status Reportlocated in the Equipment Reporting Kit. Shows

vacant circuit positions on facility circuits and provides a summary of all CP statuses based on

user prompted CLLI codes.

SONET Capacity Reportlocated in the Equipment Reporting Kit. Shows total and vacant

positions and percentage assigned on SONET facility circuits by CLLI code.

Trouble Ticket Organizations Summary Reportlocated in the Trouble kit. Displays

administrative organization information. Used to determine which administrative

organizations own a specific trouble ticket.

Updates

Location Facility Reportlocated in the Equipment Reporting kit. The report now shows

vacant positions on facility circuits and provides a summary of all circuit types on the facility

based on user-prompted CLLI codes and rate codes.

NPA/NXX Utilization Reportlocated in the Equipment Reporting kit. The title waschanged to NPA/NXX Threshold Utilization Report. The % of Unassigned Status prompt

was added for more accurate reporting.


40/140



Universal Changes M/4.3/4.5 OR1 to M/5.2 OR2


from release M/4.3/4.5 OR1 to M/5.2 OR2:

Data Model

Customer Universe

Ordering Universe



OR2" on page 11, "Universal Changes M/5.2 OR1 to M/5.2 OR2" on page 17, and the items

listed below.

Data Model ChangesChanges are made to the data model with new releases of the MetaSolv Solution. The changes




Customer Universe




Tables

New ADDRESS

GA_INSTANCE

NA_ITEM_SPEC

NA_NETWORK_AREA_ITEM_SPEC

NA_USER_DATA

NET_LOC_ADDR

NETWORK_LOCATION_TYPE

NOTES

REMARK

SF_COMP

SF_GA_INSTANCE

SF_STRUC_FORMAT


41/140


42/140



Reports



Reservation Reportlocated in the Sales/Telephone Number Inventory reporting kit. The

Customer Accou nt Nbr object was replaced by the Request Customer Account Nbr. This

allowed the data returned to reflect the customer information with the reservation information.

Customer Activity Reportlocated in the Customer/Security reporting kit. Modified to add

the Prompt for Customer Account # to part two of the union. Also, TNI Service ItemAlias

was removed and Service Item Name was added. This resolved the issue of product

duplication with different statuses.

User Window Listlocated in the Customer/Security reporting kit. The title on the actual

report was modified to duplicate the saved filename of the report.

Ordering UniverseThis section addresses design modifications and enhancements made to the Ordering universe.



Tables

New ADDRESS

GA_INSTANCE

NET_LOC_ADDR

SF_COMP

SF_COMP_COLUMN

SF_STRUC_FORMAT

SF_STRUC_TYPE

SI_LOC

TG_USER_DATA

Deleted CUR_EUL_EULU

SR_EUL


43/140




The descriptions for the objects and filters have been cleaned up, and additional information

has been added as needed.

Filters

Closed Jeopardy Codeslocated in the Work Management class/Jeopardy subclass.

Modified from requiring that the Date Closed be null to requiring that the Date Closed not be

null. This change allowed the Closed Jeopardy Report to return data.





Tables

New

ADDRESS

ADMIN_ORG

ADMIN_ORG_ASSIGN

GA_INSTANCE

NET_LOC_ADDR


RESP_ORG

RESP_ORG_ASSIGN


Objects

Object Location of Object Added or Deleted

Last Week Year Date Objects Deleted

Same Week Last Year Date Objects Deleted

Next Month Last Year Date Objects Added

Node Address Equipment Level 4/ Mounting

Position 4

Added


44/140



Node Address Equipment Level 4/ Network

Location4

Added

All Tel Billing Number Circuit 1/Circuit Added

Location ID 2 Equipment Level X/Equipment X

*

Added

Software Release Identifier Equipment Level X/Equipment X Added

Node Address Equipment Level 4/Mounting

Position 4

Added

Zip Code Equipment Level 7/Network

Location

Added

In Statement for TFC

Network ID

Circuit 1/Tfc Network Added

Location Type Circuit 1/Network Location NN

SONET

Added

Address Equipment Level X/Network

Location X

Added

City Equipment Level X/Network

Location X

Added

Location Type Equipment Level X/Network Location X

Added

State Code Equipment Level X/Network

Location X

Added

Zip Code Equipment Level X/Network

Location X

Added

Network Type Equipment Level 1/Network

Location 1

Added

Location Name Equipment Level 2/Network

Location 2

Added



45/140



Filters

User Prompt for CLLI Code Equip 7located in Equipment Level 7 class/Network Location

7 subclass. Modified from being a filter for a CLLI Code not being a TEMPLATE to a prompt

for the CLLI Code.

Cards Only Equipment Level 7located in the Equipment Level 7 class/Equipment Spec 7

subclass. Added to the Port Usage on DTC-DTCI report.

Reports



Port Usage on DTC-DTCI Reportlocated in the Equipment reporting kit. The Cards Only

Equipment Level 7 filter was added to the report to ensure that the correct hierarchy was

displayed in the data.

Report file names have been altered in order to reflect the titles of the reports. Below is a table

indicating the changes.

The X in the class name references that this was added to all levels. For example, an object

added to Equipment Level X/Equipment X can be found in Equipment Level 1/Equipment 1,

Equipment Level 2/Equipment 2, etc.

Category Old Report Name New Report Name

Equipment-Utilization Kit card inv rpt Card Inventory Report

dacs equipment report DACS Equipment Report

equipment specifications Equipment Specifications

rr_wo_8_char_names Relay Rack with Invalid

Equip Names

RrAndShelfWO11CLLI Relay Racks without 11 Char

CLLI Codes

Shelf fill Shelf Fill

sonet ring host rr Sonet Ring Host Relay Rack


46/140






Data Model

Customer Universe

Ordering Universe



OR2", on page 11, "Universal Changes M/5.2 OR1 to M/5.2 OR2" on page 17, and the items

listed below.

Data modelChanges are made to the data model with new releases of the MetaSolv Solution. The changes




Customer universe




Tables

New NETWORK_LOCATION_TYPE




Classes

Service Requesthas been deleted and all of the objects have been moved to the Service

Order class.

Objects

Order Countlocated in the Service class/Service Order subclass. Total number of orders in

the report.


47/140



PSR Product Activity Codelocated in the Service class/Service Order subclass. The action

taking place against a service request. For example, N (new), C (change), D (disconnect), I (in

service), or R (reported).

Request Customer Acct Nbrlocated in the Telephone class/ Telephone # Request subclass.

This object was added to resolve an issue with the Reservation report.

Request Customer Namelocated in the Telephone class/Telephone # Request subclass. The

full customer name.

Serv Req Billing Acct Datelocated in the Service class/Service Order subclass. Date when

the charges begin for a customer. This date can be set during the creation of an order, or at due

date time.

Serv Item Statuslocated in the Service class/Service Item subclass. Current status of a

service item after the service request has been completed.

Serv Req SI Statuslocated in the Service class/Service Item subclass. Status of a service

item once the service request has been entered, but not completed.

Serv Req Statuslocated in the Service class/Service Order subclass. Status of the entire

service request.

Reports



Reservation Reportlocated in the Sales/Telephone Number Inventory reporting kit. The

Customer Accou nt Nbr object was replaced by the Request Customer Account Nbr. This

allowed the data returned to reflect the customer information with the reservation information.

Customer Activity Reportlocated in the Customer/Security reporting kit. Modified to add

the Prompt for Customer Account # to part two of the union. Also, TNI Service ItemAlias

was removed and Service Item Name was added. This resolved the issue of product

duplication with different statuses.

User Window Listlocated in the Customer/Security reporting kit. The title on the actual

report was modified to duplicate the saved filename of the report.


48/140



Ordering universe







Filters

Closed Jeopardy Codeslocated in the Work Management class/Jeopardy subclass.

Modified from requiring that the Date Closed be null to requiring that the Date Closed not be

null. This change allowed the Closed Jeopardy Report to return data.

Engineering UniverseThis section addresses design modifications and enhancements made to the Engineering



Tables

New ADDRESS

ADMIN_ORG

ADMIN_ORG_ASSIGN

GA_INSTANCE

NET_LOC_ADDR


RESP_ORG

RESP_ORG_ASSIGN


49/140




Objects


Last Week Year Date Objects Deleted

Same Week Last Year Date Objects Deleted

Next Month Last Year Date Objects Added

Node Address Equipment Level 4/ Mounting

Position 4

Added

Node Address Equipment Level 4/ Network Location4

Added

Alltel Billing Number Circuit 1/Circuit Added

Location ID 2 Equipment Level X/Equipment

X*

Added

Software Release Identifier Equipment Level X/Equipment X Added

Node Address Equipment Level 4/Mounting

Position 4

Added

Zip Code Equipment Level 7/Network

Location

Added

In Statement for TFC

Network ID

Circuit 1/Tfc Network Added

Location Type Circuit 1/Network Location NN

SONET

Added

Address Equipment Level X/Network

Location X

Added

City Equipment Level X/Network

Location X

Added

Location Type Equipment Level X/Network

Location X

Added

State Code Equipment Level X/Network

Location X

Added


50/140



Filters

User Prompt for CLLI Code Equip 7located in Equipment Level 7 class/Network Location

7 subclass. Modified from being a filter for a CLLI Code not being a TEMPLATE to a prompt

for the CLLI Code.

Cards Only Equipment Level 7located in the Equipment Level 7 class/Equipment Spec 7

subclass. Added to the Port Usage on DTC-DTCI report.

Reports



Port Usage on DTC-DTCI Reportlocated in the Equipment reporting kit. The Cards Only

Equipment Level 7 filter was added to the report to ensure that the correct hierarchy was

displayed in the data.

Report file names have been altered in order to reflect the titles of the reports. Below is a table

indicating the changes.

Zip Code Equipment Level X/Network

Location X

Added

Network Type Equipment Level 1/Network

Location 1

Added

Location Name Equipment Level 2/Network

Location 2

Added

The X in the class name references that this was added to all levels. For example, an object

added to Equipment Level X/Equipment X can be found in Equipment Level 1/Equipment 1,

Equipment Level 2/Equipment 2, etc.


Equipment-Utilization Kit card inv rpt Card Inventory Report

dacs equipment report DACS Equipment Report

equipment specifications Equipment Specifications

rr_wo_8_char_names Relay Rack with Invalid

Equip Names



51/140



RrAndShelfWO11CLLI Relay Racks without 11 Char

CLLI Codes

Shelf fill Shelf Fill

sonet ring host rr Sonet Ring Host Relay Rack



52/140



Integrity Results of Objects and Conditions

The following section contains screen shots of known integrity results from each of the

universes contained in Operational Reports Release OR5.2 R3. These are recognized parsing

violations in Business Objects. Even though these objects and conditions do not parse,

Business Objects is still able to generate the reports and run them against an Oracle database

successfully.

Customer Universe All objects in the Date Objects class do not parse, but runs in Business Objects because

the SQL is correct.

The Telephone Number Latest object does not parse because of the included MAX SQL

function. This object is used to find the telephone number with the greatest suffix

associated to it.To use the object:

1. Navigate

m6 operational reports

Documents