2 Using MSS Operational Reports

Before using Oracle Communications MetaSolv Solution (MSS) Operational Reports, you are required to complete training on SAP Business Objects 4.0 Central Management Console, Universe Design Tool, and Web Intelligence.

This chapter outlines the common procedures used in MSS Operational Reports. This chapter does not replace Business Objects 4.0 training and should be used as a supplement to additional information specific to MSS Operational Reports.

Database Connections

Ensure that you are using the correct database connection when generating reports. This connection directs the universe to the database from which to retrieve information.

Connecting to the Database

To connect to a database:

1. Open the Universe Design Tool.

2. From the Tools menu, select Connections.

   The Connection Panel is displayed.

3. Select a connection and click Close.

Adding a Connection

To add a connection:

1. Open the Universe Design Tool.

2. From the Tools menu, select Connections.

   The Connection Panel is displayed.

   
   

3. Click the Add icon.

   The Define a new connection - Welcome to the New Connection Wizard [1/2] window is displayed.

   
   

4. From the Connection Type list, select one of the following:

   • Personal: A personal connection is only available on the machine that you are working on.

   • Secured: A secured connection is necessary to import and export from the repository. This is the default connection type.

   • Shared: A shared connection is necessary to transfer a universe to another repository.

5. In the Connection Name field, specify a name for your connection.

6. In the Connection Folder field, browse and choose your connection folder.

7. (Optional) In the Connection Description area, provide a description for your connection.

8. Click Next.

   The Define a new connection - Database Middleware Selection [2/2] window is displayed.

   
   

9. Expand the Oracle node, then expand the Oracle 11 node, and then select JDBC Drivers or Oracle Client.

10. Click Next.

    The Define a new connection - Login parameters [3/5] window is displayed.

    
    

11. From the Authentication Mode list, select Use specified username and password.

12. In the User Name field, enter ASAP or an Oracle user name that has access to all the ASAP tables.

13. In the Password field, enter your password.

14. In the Server(s) (host:port{,host:port}) field, enter the server name and port. This connection should point to where the data for the reports is stored. For example, the MetaSolv Solution database.

15. In the Net Service field, enter the SID.

16. Click Test Connection.

    The Test the connection window is displayed and informs you that the server is responding.

    
    

17. Click OK.

18. Click Next.

    The Define a new connection - Configuration Parameters [4/5] window is displayed.

    
    

19. From the Connection Pool Mode list, select Keep the connection active for.

20. In the Pool Timeout field, enter 10.

21. In the Array Fetch Size field, retain the default value of 250.

22. In the Array Bind Size field, enter a value.

23. In the Login Timeout field, enter a value. This field considers the unit of time in seconds.

24. (Optional) In the JDBC Driver Properties (key=value,key=value) field, enter a value.

25. Click Next.

    The Define a new connection - Custom Parameters [5/5] window is displayed.

    
    

26. Click Finish.

Editing a Connection

To edit a connection:

1. Open the Universe Design Tool.

2. From the Tools menu, select Connections.

   The Connection Panel is displayed.

3. Select the connection you want to edit.

4. Click the Edit icon.

5. Make your changes and click Next to navigate through the Edit connection - Login parameters, Configuration Parameters, and Custom Parameters windows.

6. Click Finish.

7. Click Close.

Removing a Connection

To remove a connection:

1. Open the Universe Design Tool.

2. From the Tools menu, select Connections.

   The Connection Panel is displayed.

3. Select the connection you want to remove.

4. Click the Remove icon.

   A confirmation message is displayed.

5. Click Yes.

6. Click Close.

Installing a New MetaSolv Solution Universe

When installing a new MetaSolv Solution universe, do the following:

• Download the new MetaSolv Solution universe

• Export the universe to a repository

• Create a sandbox

The repository should already be created.

To download a new MetaSolv Solution universe:

1. Download the newest versions of the MetaSolv Solution universes from the Oracle software delivery Web site:

   https://edelivery.oracle.com

To export a universe to a repository:

1. Open the Universe Design Tool.

2. From the File menu, select Open.

   The Open window is displayed.

3. Open the universe file.

4. From the File menu, select Parameters.

   The Universe Parameters window is displayed.

5. From the Connection list, select a secure connection.

6. Click OK.

7. From the File menu, click Save.

8. Repeat steps 2 through 7 for each new universe.

9. From the File menu, select Export.

   The Export Universe window is displayed. Verify that all the universes are displayed in the Export Universe window.

10. Do one of the following:

    • If all the universes appear in the Export Universe window, click OK.

    • If a universe is missing, click the Add button, and navigate to the location where you saved the universes. Select the missing universe and click OK.

11. Close the universes.

You can now associate a connection to the universe. See "Associating a Connection to the Universe" for more information.

Associating a Connection to the Universe

To associate the connection to the universe:

1. Open the Universe Design Tool.

2. From the File menu, select Open.

   The Open window is displayed.

3. Open the universe file.

4. From the File menu, select Parameters.

   The Universe Parameters window is displayed.

5. From the Connection list, select a secure connection.

6. Click OK.

7. From the File menu, click Save.

8. Repeat steps 2 through 7 for each new universe.

9. From the File menu, select Export to make it available to all users of the repository.

   The Export Universe window is displayed. Verify that all the universes are displayed in the Export Universe window.

10. Do one of the following:

    • If all the universes appear in the Export Universe window, click OK.

    • If a universe is missing, click the Add button, and navigate to the location where you saved the universes. Select the missing universe and click OK.

Connections

Connections in Business Objects 4.0 refer to creating a connection to the database that contains the data used to generate reports. In a single repository, you can create numerous connections to many databases.

You can create new connections using the Universe Design Tool. The security information is stored in the Central Management Console.

The types of information are as follows:

• Security

• Document

• Universe

Table 2-1 describes the repository connections.

Table 2-1 Definition of Repository Connections

Repository Connections (Domain)	Description
Security	Defined when setting up access to the repository through Central Management Console. This cannot be modified.
Document	Defines the location of documents within the repository. Multiple document domains can be used.
Universe	Defines the location of universes within the repository. Multiple universes can be used.

The connections are defined by the universes. Therefore, while developing a document, it is created from the custom universe. The universe controls the connection to the database. See the scenario in Figure 2-1 for an overview of the connection relationships.

Figure 2-1 Overview of Connection Relationships

Description of "Figure 2-1 Overview of Connection Relationships"

The SQL behind an object/filter can change in the universe without the report needing to be updated, because Web Intelligence refers to the universe before dynamically creating the SQL to run the report.

Creating a Sandbox

You must create and customize sandbox universes. When you upgrade MetaSolv Solution, you can download the universes that pertain to the upgraded version from the Oracle software delivery Web site:

Any new universes that are downloaded overwrite the existing MetaSolv Solution universes.

To create a sandbox:

1. Open the Universe Design Tool.

2. From the File menu, select New.

   The Universe Parameters window is displayed.

3. On the Definition tab, do the following:

   • In the Name field, enter a name for the universe.

   • From the Connection list, select a secure connection.

4. On the Links tab, click Add Link.

5. Navigate to the folder named after the repository, select the appropriate universe.

6. Click OK.

7. From the File menu, click Save.

8. Repeat steps 2 through 7 for each new universe.

9. From the File menu, select Export.

   The Export Universe window is displayed. Verify that all the universes are displayed in the Export Universe window.

10. Do one of the following:

    • If all the universes appear in the Export Universe window, click OK.

    • If a universe is missing, click the Add button, and navigate to the location where you saved the universes. Select the missing universe and click OK.

Creating, Modifying, and Deleting Categories for Report Kits

Creating categories allows you to organize reports into specific into smaller or functional groups. Security can be applied to categories to give access to specified users. Oracle recommends creating your categories before installing the report kits.

To create a category:

1. Open the Central Management Console by entering the following in a Web browser:

   http://localhost:port/BOE/CMC

   where:

   localhost is the server on which the Business Objects 4.0 is installed.

   port is the server's HTTP port number.

2. Click Categories.

3. Right-click the Categories folder and select New.

   The Create Category window is displayed.

4. In the Enter a new category name field, enter a name for the category.

5. Click OK.

To modify a category:

1. Open the Central Management Console.

2. Click Categories.

3. Right-click the category you want to modify and select Properties.

   
   

   The Properties window is displayed.

   
   

4. In the Category Name field, modify the category name.

5. Click Save & Close.

To delete a category:

1. Open the Central Management Console.

2. Click Categories.

3. Right-click the category you want to delete and select Delete.

   A confirmation message is displayed.

4. Click OK.

Installing a Reporting Kit

To install a reporting kit:

1. Download the reporting zip file from the Oracle software delivery Web site.

2. Extract the zip files to any folder.

3. Open the Web Intelligence Client.

   
   

4. Under the Open Document section, click browse.

5. Open all the reports in a reporting kit.

6. From the File menu, select Save to Enterprise.

   
   

   The Save Document window is displayed.

   
   

7. On the Folders tab or Categories tab, select a folder or a category in which you want to save the report.

8. Click Save.

9. Repeat this procedure for each report in the kit.

Customizations

This section provides an overview of guidelines for customization, report customization, using sandbox universes for customization, and linking universes best practices.

Guidelines for Customization

All of the universe customizations occur originally in sandbox universes. You must follow the procedures to create sandbox universes and customize those universes so that you do not lose your customizations. When you upgrade MetaSolv Solution, you can download the universes that pertain to that upgraded version from the Oracle software delivery Web site. Any new universes that you download will overwrite the existing MetaSolv Solution universes.

The following general rules enable you to receive requirements from a user:

• Determine if an existing report can meet at least some of the needs.

• Determine how many of the requirements exist among the list of current objects, measures, and filters.

• Determine which universe is the closest to meeting your needs.

• Determine what you have to map into a Sandbox universe linked to the universe you have chosen.

• Determine if the tables that you need exist in the universe.

• Determine if you need to create an alias in order for the report to run correctly.

• Determine if you can reuse an existing object as a base to what you need to create.

The changes that you make in the sandbox are available for reporting but are not affected by universe updates.

Report Customization

You can customize your reports in two ways. You may need to create a new report or alter an existing report, but do not require any new or modified objects in the reporting universe. These customizations can be made in the Web Intelligence Query Panel. Figure 2-2 displays the Web Intelligence Query Panel.

Figure 2-2 Web Intelligence Query Panel

Description of "Figure 2-2 Web Intelligence Query Panel"

When creating custom reports from MetaSolv Solution reports, name the customized report differently from the MetaSolv Solution report. This allows the original MetaSolv Solution reports to be used multiple times in custom report creation.

When forwarding this report to others or if other Business Objects 4.0 users want to access this report without first exporting the report to the repository, select the Save for all users check box in the Save Document window before saving the report.

When importing the report into another repository, select the Remove document security check box in the Save Document window before saving the report.

Figure 2-3 shows the Save Document window.

Figure 2-3 Save Document Window

You may need reporting requirements that are not presently satisfied by existing reporting objects in the reporting universe. This type of customization is more complex, because it requires making modifications to the reporting universes and is done by the universe designer.

Sandbox Universes for Customization

When MSS Operational Reports is installed at a customer site, each reporting universe is locked and then linked to a Sandbox universe which contains each universe. This sandbox environment allows for the augmentation of a baseline reporting universe without requiring the baseline itself to be modified. This design approach allows for upgrades of the MSS Operational Reports product, and the baseline universes without affecting any customizations made by the customer. When the baseline universes are updated, the sandbox universe merely needs to be re-linked to the baseline which preserves any prior customizations.

Figure 2-4 illustrates where the updates occur.

Figure 2-4 Overview of Customer Data Security During Updates

Description of "Figure 2-4 Overview of Customer Data Security During Updates"

When you need to report on data that is not defined as objects in the baseline reporting universes, you must create those objects in the sandbox environment associated with the respective universe and not in the baseline universe itself. Reports can be created or modified with the newly defined objects once the objects have been created and defined in the sandbox universe, and the sandbox universe has been saved and exported.

Linking Universes Best Practices

Do not use the Include option when linking the baseline and sandbox universe to remain compliant with MetaSolv Solution's maintenance protocol. This option merges the two universes, thereby making them appear as one. This complicates further updates to the product. Linking the universes allows you to see everything, use everything, and add customizations without losing any customizations when you must update the baseline universes.

You must avoid creating links between the universes that MetaSolv Solution provides, or between custom universes and the MetaSolv Solution universes. This can create additional or redundant relationships or joins between the tables in the database, thus confusing the Business Objects 4.0 SQL generator. You cannot use the resulting universe until you resolve the redundant relationships or loops.

Transferring Customized Universes and Reports

If you are maintaining multiple repositories, such as a development, testing, and production repositories, a different set of procedures is used to determine what items need to be transferred when moving universes or reports between repositories.

When transferring customized universes and reports, you need to complete the following:

• Determine what to transfer

• Prepare the universe for transfer between repositories

• Transfer the document between repositories

• Prepare the production repository for the transfer of the universe

• Prepare the production repository for the transfer of the documents

• Move the universe from one repository to another

• Move documents from one repository to another

Transferring Universes and Documents Between Repositories

Customized documents are created in the sandbox universe. The universe controls the connection to the database. Figure 2-5 shows the overall hierarchy.

Figure 2-5 Overview of Connection Relationships

Description of "Figure 2-5 Overview of Connection Relationships"

The SQL behind an object/filter can change in the universe without the report needing to be updated, because Web Intelligence refers to the universe before dynamically creating the SQL to run the report. Therefore, if the changes have been made only in the custom universe, you must transfer only the universe.

If the only changes that have occurred are in a document, whether it is a new or modified report, then only the report needs to be transferred. This assumes that the report is not using any new objects created in the custom universe to support this report.

If the custom universe has changed and the document is new or modified, then you must transfer both the universe and the document.

To prepare a universe for transfer between repositories:

1. Open the Universe Design Tool in the repository you want to move the universe from.

2. From the File menu, select Import.

   The Import Universe window is displayed.

3. Select the universe that you want to transfer and click OK.

   The universe is imported.

4. From the File menu, select Parameters.

   The Universe Parameters window is displayed.

   
   

5. On the Definition tab, from the Connection list, select a shared connection.

6. To add a new connection, click New. When creating a connection ensure that you select Shared from the Connection Type list. See "Adding a Connection" for more information.

7. From the File menu, select Save As.

   The Save As window is displayed.

   
   

8. Select the Save for all users check box.

   You can change the name of the universe if you want. The name of the file should not be more than eight characters. For example, create a folder named Shared.

9. Navigate to the new folder.

10. Click Save.

    This universe is ready to be transferred.

11. Repeat steps 2 through 10 for all the universes that you want to transfer.

To transfer a document between repositories:

1. Open the Web Intelligence Client.

   
   

2. Under the Open Document section, click browse.

   The Open a document from server window is displayed.

   
   

3. Click My Enterprise, log on to the server and select your category, and then select the report and click Open. To search for reports, enter the report name in the Search title field and click the Search icon.

4. Click Title to sort by the name of the report.

5. Select the report you want to move and click Open.

6. From the File menu, select Save As.

   The Save Document window is displayed.

   
   

7. Select the Save for all users and Remove document security check boxes and change the name of the report, if required.

8. Click Save.

To prepare the production repository for the transfer of universes:

1. Open the Central Management Console by entering the following in a Web browser:

   http://localhost:port/BOE/CMC

   where:

   localhost is the server on which the Business Objects 4.0 is installed.

   port is the server's HTTP port number.

2. Click Universes.

   The list of universes is displayed.

   
   

3. From the list of universes, right click the universe and select Delete.

   You do not have to delete the universe, you can overwrite it.

4. Repeat this procedure for each universe you want to delete.

To move a universe from one repository to another:

1. Open the Universe Design Tool and ensure that it is connected to the destination repository.

2. From the File menu, select Open.

3. Navigate to the folder where the shared universes are saved, select the file, and then click Open.

   The universe opens.

4. From the File menu, select Parameters.

   The Universe Parameters window is displayed.

5. From the Connection list, select a secured connection.

6. Click OK.

7. From the File menu, click Save.

8. From the File menu, select Export.

   The Export Universe window is displayed.

9. Click OK.

   You receive a message that informs you that the universe was successfully exported when you transfer your universe from one repository to another.

10. Repeat steps 2 through 9 for all the universes that you want to move.

To move documents from one repository to another:

1. Open the Web Intelligence Client and ensure that it is connected to the destination repository.

2. Under the Open Document section, click browse.

3. Navigate to the document/report you want to move and click Open.

4. Click the Data button on the top right corner.

5. Under Data, right-click the universe and select Change Source.

   
   

   The Change Source Wizard is displayed.

   
   

6. To change the universe that the report is associated to, select the Specify a new data source option.

7. From the Select a data source list, select Universe.

   The Universe window is displayed.

   
   

8. Select a universe to which you want to associate the report and click Select.

   The selected universe is displayed under the Specify a new data source option.

   
   

9. Click Next.

   The Change Source Wizard - Object Mapping window is displayed.

   
   

10. Click Finish.

11. From the File menu, click Save to Enterprise.

    
    

    The Save Document window is displayed.

12. On the Folders tab or Categories tab, select a folder or a category in which you want to save the report.

    
    

13. Click Save.

14. Repeat this procedure for all the reports that you want to put into this repository.

Moving Repositories

You can move repositories using the Promotion Management feature in the Central Management Console.

See the SAP Web site for more information about moving repositories.

Figure 2-6 Promotion Management in Central Management Console

Description of "Figure 2-6 Promotion Management in Central Management Console"

Upgrading Universes

Universe upgrades are required if you:

• Upgrade to a newer version of MSS Operational Reports.

• Want the latest universe or reporting enhancements.

Upgrading a MetaSolv Solution universe involves the following tasks:

• Delete existing copies of MetaSolv Solution universes.

• Download and export the new MetaSolv Solution universes.

• Import the sandbox and associate the new universe.

To delete a universe:

1. Open the Central Management Console by entering the following in a Web browser:

   http://localhost:port/BOE/CMC

   where:

   localhost is the server on which the Business Objects 4.0 is installed.

   port is the server's HTTP port number.

2. Click Universes.

   The list of universes is displayed.

3. From the list of universes, right click the universe and select Delete.

   You do not have to delete the universe, you can overwrite it.

4. Repeat this procedure for each universe you want to delete.

To download and export a new MetaSolv Solution universe:

1. Download the latest versions of the MetaSolv Solution universes from the Oracle software delivery Web site.

2. Open the Universe Design Tool.

3. From the File menu, select Open.

4. Open the universe files that you downloaded.

5. From the File menu, select Parameters.

   The Universe Parameters window is displayed.

6. On the Definition tab, from the Connection list, select a secure connection.

7. Click OK.

8. From the File menu, select Save.

9. Repeat steps 3 through 8 for each universe.

10. From the File menu, select Export.

    The Export Universe window is displayed. Verify that all the universes are displayed in the Export Universe window.

11. Do one of the following:

    • If all the universes appear in the Export Universe window, click OK.

    • If a universe is missing, click the Add button, and navigate to the location where you saved the universes. Select the missing universe and click OK.

12. Close the universes.

To update a sandbox:

1. Open the Universe Design Tool.

2. From the File menu, select Import.

   The Import Universe window is displayed.

3. Select the universe.

4. Click OK.

5. From the File menu, select Parameters.

   The Universe Parameters window is displayed.

   
   

6. On the Links tab, select the universe and click Change Source.

   The Universe To Link window is displayed.

7. Navigate to the folder named after the repository and select the appropriate universe and click Open.

8. Click OK.

9. From the File menu, click Save.

10. Close the universe.

11. Reopen the universe to verify the changes.

12. Repeat steps 2 through 11 for each universe.

13. From the File menu, select Export.

    The Export Universe window is displayed. Verify that all the universes are displayed in the Export Universe window.

14. Do one of the following:

    • If all the universes appear in the Export Universe window, click OK.

    • If a universe is missing, click the Add button, and navigate to the location where you saved the universes. Select the missing universe and click OK.

15. Close the universes.

Upgrading Reports

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

To install new or upgraded reports:

1. Open the Web Intelligence Client.

2. Under the Open Document section, click browse.

3. Navigate to the document/report you want to move and click Open.

4. Click the Data button on the top right corner.

5. Under Data, right-click the universe and select Change Source.

   The Change Source Wizard is displayed.

6. To change the universe that the report is associated to, select the Specify a new data source option.

7. From the Select a data source list, select Universe.

   The Universe window is displayed.

8. Select a universe to which you want to associate the report and click Select.

   The selected universe is displayed under the Specify a new data source option.

9. Click Next.

   The Change Source Wizard - Object Mapping window is displayed.

10. Click Finish.

11. From the File menu, click Save to Enterprise.

    The Save Document window is displayed.

12. On the Folders tab or Categories tab, select a folder or a category in which you want to save the report.

13. Click Save.

14. Repeat this procedure for all the reports that you want to upgrade.

Optimizing Report Performance

If you observe performance issues with your reports, there are Oracle options that can be hard-coded into the SQL Editor window of the reports. By default, Oracle uses the Cost Based method versus the Rule Based method. To maintain optimal performance using either method, you must analyze and estimate all the MetaSolv Solution schemas. Performance is improved when the indexes are updated and are current. Contact your database administrator to run this procedure.

CONVERT_GMT_TO_LOCALDB Stored Function

The 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, because 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.

Table 2-2 lists the date-time objects impacted by this new stored function:

Table 2-2 Date-time Objects Impacted by CONVERT _GMT_TO_LOCALDB Stored Function

Universe Name	Class/Subclass Name	Object Name
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Ckt In Service Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Close Dt (MM-DD-YYYY)
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Close Dt (YYYY)
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Status Last Modified Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	State Last Modified Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Restore Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Open Dt (MM-DD-YYYY)
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Open Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Next Cust Status Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Next Activity Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Defer Until Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Close Dt (MM-YYYY)
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Close Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Cleared Dt
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Trbl Detect Dt
Engineering	Trouble/Trouble Tickets/Trbl Task	Create Date
Engineering	Trouble/Trouble Tickets/Trbl Task	Actual Start Date
Engineering	Trouble/Trouble Tickets/Trbl Task	Actual Completion Date
Engineering	Trouble/Trouble Tickets/Trbl 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
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

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. Table 2-3 lists the condition objects that have been modified.

Table 2-3 Condition Objects Modified by CONVERT_GMT_TO_LOCALDB Stored Function

Universe Name	Class Name	Condition Name
Engineering	Trouble/Trouble Tickets/Trouble Ticket	Prompt for Open Date Range
Engineering	Trouble/Trouble Tickets/Trouble 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

Note:

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.

The stored function is SQL code that must be loaded into SQL*Plus (or any storedprocedure 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 only has to be executed one time.

Downloading and Compiling the CONVERT_GMT_TO_LOCALDB Function

You must run this procedure to ensure that the date objects or filters in the Ordering or Engineering Reporting Universes that use this function parse successfully so that you can use them in a report.

To download and compile the CONVERT_GMT_TO_LOCALDB function:

1. Copy the CONVERT_GMT_TO_LOCALDB.sql to a local directory.

   The CONVERT_GMT_TO_LOCALDB.sql file is included in each Universe zip file.

2. Open SQL*Plus.

3. Log in to the database with ASAP authorization and do the following:

   • At the SQL*Plus prompt, enter the following:

     "@drive:\path\CONVERT_GMT_TO_LOCALDB.sql"
     

   • Press Enter.

SQL*Plus displays a message informing you that the function is created.

To verify that the function was successfully compiled, open any of the GMT-related objects in the Business Objects 4.0 Universe Design Tool and parse the object. If the function was successfully compiled, the object parses without any errors.

Integrity Results of Objects and Conditions

Business Objects 4.0 has an option in the Universe Design Tool that runs an integrity check on a universe. The integrity check parses every object and verifies the object in the universe. The integrity check returns errors in all the three MetaSolv Solution universes because Business Objects 4.0 does not support certain SQL statements. However, the objects function correctly in the Web Intelligence Client.

These are recognized parsing violations in Business Objects 4.0. Even though these objects and conditions do not parse, Business Objects 4.0 is still able to generate the reports and run them against an Oracle database successfully.

To run an integrity check:

1. Open the Universe Design Tool.

2. Open the universe.

3. From the Tools menu, select Check Integrity.

   The Integrity Check window is displayed.

   
   

4. Click OK.

   The integrity check results are displayed.

The following sections contains screen shots of known integrity check results from each of the universes contained in MSS Operational Reports.

Customer Universe

All the objects in the Date Objects class do not parse but run in Business Objects 4.0 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.

The first four conditions (Neither an agent or salesperson, Salesperson & Agent, More than one agent to customer, and More than one Salesperson to cust) do not parse because the SQL for these conditions has been hard-coded into the objects for a specific Sales/Telephone Kit report.

The last condition (No Active Service Items) does not parse because it uses the Not Exists SQL clause, which Business Objects 4.0 does not recognize.

The Price/Offer Price does not parse but runs in Business Objects 4.0. The SQL is correct.

The count for telephone number reservations is currently used as a counting object for the Reservation Report.

Figure 2-7 shows an example of integrity results for the Customer universe.

Figure 2-7 An Example of Integrity Results for the Customer Universe

Description of "Figure 2-7 An Example of Integrity Results for the Customer Universe"

Engineering Universe

All the objects in the Current Date Objects class do not parse but run in Business Objects 4.0 because the SQL is correct.

Figure 2-8 shows an example of integrity results for the Engineering universe.

Figure 2-8 An Example of Integrity Results for the Engineering Universe

Description of "Figure 2-8 An Example of Integrity Results for the Engineering Universe"

Ordering Universe

All the objects in the Date Objects class do not parse but run in Business Objects 4.0 because the SQL is correct.

The Missing Due Date Task condition does not parse because it uses the Not Exists SQL clause, which Business Objects 4.0 does not recognize.

Figure 2-9 shows an example of integrity results for the Ordering universe.

Figure 2-9 An Example of Integrity Results for the Ordering Universe

Description of "Figure 2-9 An Example of Integrity Results for the Ordering Universe"