oracle project analysis collection pack implementation guide · iv oracle project analysis...

Oracle � Project AnalysisCollection PackImplementation GuideRELEASE 11

March 1998

Enabling the Information Age

Part number A59356–01

Copyright � 1998

All rights reserved. Printed in the U.S.A.

Major Contributors: Vinod Bansal, Constance Kim, Debabrata Roy, Ashwani Shahi

The Programs (which include both the software and documentation) contain proprietaryinformation of Oracle Corporation; they are provided under a license agreement containingrestrictions on use and disclosure and are also protected by copyright, patent and other intellectualproperty law. Reverse engineering of the Programs is prohibited. The information contained in this document is subject to change without notice. If you find anyproblems in the documentation, please report them to us in writing. Oracle Corporation does notwarrant that this document is error free. RESTRICTED RIGHTS LEGEND Programs delivered subject to the DOD FAR Supplement are ’commercial computer software’ and use,duplication and disclosure of the Programs shall be subject to the licensing restrictions set forth in theapplicable Oracle license agreement. Otherwise, Programs delivered subject to the Federal AcquisitionRegulations are ’restricted computer software’ and use, duplication and disclosure of the Programsshall be subject to the restrictions in FAR 52.227–14, Rights in Data –– General, including Alternate III(June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood City, CA 94065.” The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or otherinherently dangerous applications. It shall be licensee’s responsibility to take all appropriate fail–safe,back up, redundancy and other measures to ensure the safe use of such applications if the Programsare used for such purposes, and Oracle disclaims liability for any damages caused by such use of thePrograms.

Oracle is a registered trademark, and Context, Financial Analyzer, Oracle7, Oracle8, Oracle Alert,Oracle Applications, Oracle Discoverer, Oracle Financials, Object Library, Oracle Work in Process,Oracle Workflow, SmartClient, PL/SQL, SQL*Calc, SQL*Forms, SQL*Loader, SQL*Menu, SQL*Net,SQL*Plus, SQL*Report, SQL*ReportWriter, Oracle Web Employees, and SQL*QMX are trademarks orregistered trademarks of Oracle Corporation. All other company or product names are mentioned for identification purposes only, and may betrademarks of their respective owners.

iContents

Contents

Preface i. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 1 Introduction 1 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview of Oracle Project Analysis Collection Pack 1 – 2. . . . . . . . .

Operational Project Performance 1 – 2. . . . . . . . . . . . . . . . . . . . . . . Flexible Configuration 1 – 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Data Warehouse Uses 1 – 5. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 2 System Requirements 2 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . System Requirements 2 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Profile Options 2 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 3 Standard Architecture 3 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Oracle Project Analysis Collection Pack Architecture 3 – 2. . . . . . . . . .

Standard Dimensions, Hierarchy Levels, and Measures 3 – 3. . . . Interface Tables 3 – 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collection Views 3 – 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Collecting Dimension and Fact Tables 3 – 10. . . . . . . . . . . . . . . . . . . Database Triggers 3 – 11. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 4 Implementation Considerations 4 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . Implementing Oracle Project Analysis Collection Pack 4 – 2. . . . . . . .

ii Oracle Project Analysis Collection Pack Implementation Guide

Chapter 5 Customizations 5 – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customizing Your Integration 5 – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Disabling Standard Metadata 5 – 3. . . . . . . . . . . . . . . . . . . . . . . . . . Creating New Metadata 5 – 4. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Chapter 6 Generating and Installing Your Data Warehouse 6 – 1. . . . . . . . . . . . Generating and Installing Your Data Warehouse 6 – 2. . . . . . . . . . . . .

Chapter 7 Collecting Data and Maintaining the Data Warehouse 7 – 1. . . . . . . Overview of Collecting Data and Maintaining Your Warehouse 7 – 2

Appendix A Modifying Fact Collection Views A – 1. . . . . . . . . . . . . . . . . . . . . . . . . . Modifying Collection Views to Disable or Create a Measure A – 2. . .

Disabling a Standard Measure A – 2. . . . . . . . . . . . . . . . . . . . . . . . . Creating a Measure A – 7. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix B Sample Reports B – 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Report Listing B – 2. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Project Organization View B– 3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Project View by Activity (Service Type) B– 4. . . . . . . . . . . . . . . . . . . . . Project Organization View by Activity (Service Type) B– 5. . . . . . . . . Top 3 Projects with Best Budgeted Cost to Actual Cost Variances B– 6. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Bottom 2 Projects with Lowest Revenue B– 7. . . . . . . . . . . . . . . . . . . . . Top 2 Projects with Highest Revenue B– 8. . . . . . . . . . . . . . . . . . . . . . . Margin View B– 9. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Glossary

Index

iPreface

Preface

Welcome to Release 11 of the Oracle Project Analysis Collection PackImplementation Guide.

This implementation guide includes the information you need to workwith Oracle Project Analysis Collection Pack effectively. It containsdetailed information about the following:

• Overview and reference information

• System requirements

• Description of standard implementation steps

• Description of customizations that you can perform, includingsample view changes

• Specific types of analysis that you can perform using OracleProject Analysis Collection Pack

• Oracle Project Analysis Collection Pack functions and features

• Sample reports

This preface explains how this implementation guide is organized andintroduces other sources of information that can help you.

ii Oracle Project Analysis Collection Pack Implementation Guide

About This Implementation Guide

This guide is the primary source of information about Oracle ProjectAnalysis Collection Pack. It contains overviews as well as task andreference information. This guide includes the following chapters:

• Chapter 1 provides a brief introduction to Oracle ProjectAnalysis Collection Pack.

• Chapter 2 describes the server requirements you need to fulfill touse Oracle Project Analysis Collection Pack.

• Chapter 3 describes the standard architecture of Oracle ProjectAnalysis Collection Pack and provides a list of all of the standarddimensions, hierarchy levels, and measures that Oracle ProjectAnalysis Collection Pack predefines.

• Chapter 4 walks you through the factors you must consider inyour decision to implement and customize, if necessary, OracleProject Analysis Collection Pack.

• Chapter 5 provides detailed information about customizingdimensions, hierarchy levels, measures, and fact tables andmodifying the collection processes.

• Chapter 6 describes how to generate and install the datawarehouse.

• Chapter 7 tells you how to run the collection process to populateyour data warehouse and use tools to query, analyze, andgenerate reports based on your project information.

• Appendix A provides sample view changes that you can use tomodify collection views to disable a standard measure or tocreate a new measure.

• Appendix B includes a list of sample reports that you cangenerate using the standard dimensions, hierarchy levels, andmeasures predefined by Oracle Project Analysis Collection Pack.

This implementation guide is available online

All Oracle Applications user’s guides are available online in AdobeAcrobat format. Most other Oracle Applications documentation, suchas this implementation guide, is available in Adobe Acrobat format.

The paper and online versions of this manual have identical content;use whichever format is most convenient.

You can order an Oracle Applications Documentation Library CDcontaining Adobe Acrobat versions of each manual in the Oracle

iiiPreface

Applications documentation set. Using this CD, you can search forinformation, read it on–screen, and print individual pages, sections, orentire books. When you print from Adobe Acrobat, the resultingprintouts look just like pages from an Oracle Applications hardcopymanual.

Note: The Oracle Applications Documentation Library CDdoes not include documentation for Oracle Applications DataWarehouse, Oracle Express Analyzer, and Oracle SalesAnalyzer. You must order these reference materials separately.

Assumptions

This guide assumes you have a working knowledge of the principlesand customary practices of your business area. It also assumes you arefamiliar with Oracle Projects and Oracle Applications Data Warehouse.If you have never used Oracle Projects and Oracle Applications DataWarehouse, we suggest you attend one or more of the Oracle Projectsand Oracle Applications Data Warehouse training classes availablethrough Oracle Education. (See Other Information Sources for moreinformation about Oracle Projects, Oracle Applications DataWarehouse, and Oracle training.)

This guide also assumes that you are familiar with the OracleApplications graphical user interface. To learn more about the OracleApplications graphical user interface, read the Oracle Applications User’sGuide.

iv Oracle Project Analysis Collection Pack Implementation Guide

Do Not Use Database Tools to Modify Oracle Applications Data

Oracle provides powerful tools you can use to create, store, change,retrieve and maintain information in an Oracle database. But if you useOracle tools like SQL*Plus to modify Oracle Applications data, you riskdestroying the integrity of your data and you lose the ability to auditchanges to your data.

Because Oracle Applications tables are interrelated, any change youmake using an Oracle Applications form can update many tables atonce. But when you modify Oracle Applications data using anythingother than Oracle Applications forms, you may change a row in onetable without making corresponding changes in related tables. If yourtables get out of synchronization with each other, you risk retrievingerroneous information and you risk unpredictable results throughoutOracle Applications.

When you use Oracle Applications forms to modify your data, OracleApplications automatically checks that your changes are valid. OracleApplications also keeps track of who changes information. But, if youenter information into database tables using database tools, you maystore invalid information. You also lose the ability to track who haschanged your information because SQL*Plus and other database toolsdo not keep a record of changes.

Consequently, we STRONGLY RECOMMEND that you never useSQL*Plus, Oracle Data Browser, database triggers, or any other tool tomodify Oracle Applications tables, unless we tell you to do so in ourmanuals.

Other Information Sources

You can choose from many sources of information, includingdocumentation, training, and support services, to increase yourknowledge and understanding of Oracle Project Analysis CollectionPack, Oracle Projects, and Oracle Applications Data Warehouse.

Most Oracle Applications documentation is available in Adobe Acrobatformat on the Oracle Applications Documentation Library CD. We supplythis CD with every software shipment.

If this manual refers you to other Oracle Applications documentation,use only the Release 11 versions of those manuals unless we specifyotherwise.

vPreface

Oracle Applications User’s Guide

This guide explains how to navigate, enter data, query, run reports, andintroduces other basic features of the graphical user interface (GUI)available with this release of Oracle Project Analysis Collection Pack(and any other Oracle Applications product). This guide also includesinformation on setting user profiles, as well as running and reviewingreports and concurrent requests.

You can also access this user’s guide online by choosing ”GettingStarted with Oracle Applications” from any Oracle Applications helpfile.

Related User’s Guides

You may want to consult other reference materials when you set upand use Oracle Project Analysis Collection Pack to integrate OracleProjects with Oracle Applications Data Warehouse.

Oracle Projects User’s Guide

This user’s guide provides you with all the information you need touse your Oracle Projects application with a function– and task–orientedorganization.

Oracle Applications Data Warehouse User’s Guide

Use this user’s guide to understand and learn how to use OracleApplications Data Warehouse (OADW). This manual providesstep–by–step guidance on topics from setting up the warehouse, tomodeling your business data, and using the OADW in the mostefficient way possible.

Oracle Applications Data Warehouse Reference Manual

This guide provides detailed descriptions of each of the windowsprovided by Oracle Applications Data Warehouse.

Oracle Applications Developer’s Guide

This guide contains the coding standards followed by the OracleApplications development staff. It describes the Oracle ApplicationObject Library components needed to implement the OracleApplications user interface described in the Oracle Applications UserInterface Standards. It also provides information to help you build your

vi Oracle Project Analysis Collection Pack Implementation Guide

custom Developer/2000 forms so that they integrate with OracleApplications.

Oracle Applications User Interface Standards

This manual contains the user interface (UI) standards followed by theOracle Applications development staff. It describes the UI for theOracle Applications products and how to apply this UI to the design ofan application built by using Oracle Forms 4.5.

Oracle Applications Demonstration User’s Guide

This manual documents the functional storyline and product flows forGlobal Computers, a fictional manufacturer of personal computerproducts and services. As well as including product overviews, thebook contains detailed discussions and examples, across each of themajor product flows. Tables, illustrations, and charts summarize keyflows and data elements.

Installation and System Administration

Oracle Applications Installation Manual

This manual and the accompanying release notes provide informationyou need to successfully install Oracle Financials, Oracle Public SectorFinancials, Oracle Manufacturing, or Oracle Human Resources in yourspecific hardware and operating system software environment.

Oracle Applications Data Warehouse Installation Manual

This manual provides step–by–step instructions to install OracleApplications Data Warehouse.

Oracle Applications Upgrade Manual

This manual explains how to prepare your Oracle Applicationsproducts for an upgrade. It also contains information on finishing theupgrade procedure for each product. Refer to this manual and theOracle Applications Installation Manual when you plan to upgrade yourproducts.

viiPreface

Oracle Applications System Administrator’s Guide

This manual provides planning and reference information for theOracle Applications System Administrator. It contains information onhow to define security, customize menus and online help, and manageprocessing.

Oracle Projects Applications Technical Reference Manual

The Oracle Projects Applications Technical Reference Manual containsdatabase diagrams and a detailed description of Oracle Projects andrelated applications database tables, forms, reports, and programs.This information helps you convert data from your existingapplications, integrate Oracle Projects with non–Oracle applications,and write custom reports for Oracle Projects.

You can order a technical reference manual for any product you havelicensed. Technical reference manuals are available in paper formatonly.

Other Information

Training

Oracle Education offers a complete set of training courses to help youand your staff master Oracle Applications. We can help you develop atraining plan that provides thorough training for both your projectteam and your end users. We will work with you to organize coursesappropriate to your job or area of responsibility.

Training professionals can show you how to plan your trainingthroughout the implementation process so that the right amount ofinformation is delivered to key people when they need it the most. Youcan attend courses at any one of our many Educational Centers, or youcan arrange for our trainers to teach at your facility. In addition, wecan tailor standard courses or develop custom courses to meet yourneeds.

Support

From on–site support to central support, our team of experiencedprofessionals provides the help and information you need to keepOracle Project Analysis Collection Pack working for you. This teamincludes your Technical Representative, Account Manager, and Oracle’slarge staff of consultants and support specialists with expertise in your

viii Oracle Project Analysis Collection Pack Implementation Guide

business area, managing an Oracle server, and your hardware andsoftware environment.

About Oracle

Oracle develops and markets an integrated line of software productsfor database management, applications development, decision support,and office automation, as well as a complete family of financial,manufacturing, and human resource applications.

Oracle products are available for mainframes, minicomputers, personalcomputers, network computers, and personal digital assistants,allowing organizations to integrate different computers, differentoperating systems, different networks, and even different databasemanagement systems, into a single, unified computing and informationresource.

Oracle offers its products, along with related consulting, education, andsupport services, in over 140 countries around the world. OracleCorporation is the world’s leading supplier of software for informationmanagement, and is the world’s second largest software company.

Thank You

Thank you for using Oracle Project Analysis Collection Pack and thisimplementation guide.

We value your comments and feedback. At the end of this manual is aReader’s Comment Form you can use to explain what you like ordislike about Oracle Project Analysis Collection Pack or thisimplementation guide. Mail your comments to the following addressor call us directly at (650) 506–7000.

Oracle Applications Documentation ManagerOracle Corporation500 Oracle ParkwayRedwood Shores, CA 94065U.S.A.

Or, send electronic mail to [email protected].

C H A P T E R

1T

1 – 1Introduction

Introduction

his chapter provides a general introduction to the businessapplications of Oracle Project Analysis Collection Pack. It providesseveral examples of the query, analysis, and reporting capabilities ofOracle Project Analysis Collection Pack.

1 – 2 Oracle Project Analysis Collection Pack Implementation Guide

Overview of Oracle Project Analysis Collection Pack

Warning: Oracle Project Analysis Collection Pack enables youto integrate Oracle Projects and Oracle Applications DataWarehouse (OADW). This application is not included in, but isadditional to, the Oracle Projects product. You cannot use anyof the features described in this manual unless you havepurchased and are a licensed user of Oracle Project AnalysisCollection Pack.

Oracle Project Analysis Collection Pack enables you to collectcorporate–wide project information in a central repository and analyzethe data using standard or user–defined parameters (dimensions,hierarchy levels, and measures). This tool is a business solution thatallows high–level corporate managers to view data across theirenterprise in a wide variety of ways.

For example, you can use some of the standard parameters to analyzecost, revenue, and budget data across:

• Projects

• Time periods

• Organizations

Alternately, you can freely disable parameters or create your own to fitthe analysis and reporting needs of your company. Oracle ProjectAnalysis Collection Pack offers flexible and extensible analysiscapabilities limited only by the information that your company records.

Operational Project Performance

Oracle Projects remains the tool for collecting project information aswell as for monitoring actual transactions. The project status inquiry(PSI) feature in Oracle Projects enables you to track project status interms of actual and budgeted amounts and commitments at any WBSlevel. However, you can perform PSI queries on only one project at atime for four time periods:

• Period–to–date

• Prior period

• Year–to–date

• Inception–to–date

☞

1 – 3Introduction

By contrast, Oracle Project Analysis Collection Pack enables you toanalyze project information across projects and organizations. Forexample, you can use Oracle Project Analysis Collection Pack toanalyze project information by financial year, financial quarter, GLperiod, or PA period. Depending on your analysis tool, you canrepresent your analysis results graphically to create easy–to–readpresentations.

Analyze project information across dimensions that represent themetrics for success in your company. Once you identify patterns inprojects or organizations that lead to success or failure, you can modifyyour business practices to optimize your company’s performance.

Flexible Configuration

You can use Oracle Project Analysis Collection Pack to providemultidimensional analysis capabilities in several ways:

• Integrate information in the interface tables provided by OracleProjects with Oracle Applications Data Warehouse (OADW).OADW automates the design, implementation, and ongoingadministration of an enterprise–wide data warehouse or aline–of–business, subject–oriented data mart.

Attention: This guide discusses only this implementationoption.

• Access project data warehouse information directly from the starschema tables using OLAP tools, such as Oracle Relation AccessAdministrator, Oracle Relation Access Manager, Oracle SalesAnalyzer, and Oracle Express Analyzer

• Build a custom data warehouse by extracting project informationfrom interface tables into flat files and uploading the informationinto the data warehouse. You can then analyze the informationusing OLAP tools, such as Oracle Express Objects and OracleExpress Analyzer.

Figure 1 – 1


Information flow in Oracle Project Analysis Collection Pack

OADWOracle Discoverer

Oracle Data Mart SuiteSummarization

Tables

Oracle Projects Project Star Schema

InterfaceTables

OADW integration enables you to perform the following types ofanalysis:

If your company does not require the online analysis of projectinformation, you do not need to integrate with OADW. The coreOracle Projects product provides a project status inquiry feature thatallows you to track and report on actual costs and budgeted amountsat the project level. For more information about this tracking capability,see: Project Status Inquiry (Oracle Projects User’s Guide).

Oracle Projects predefines the following standard dimensions, whichserve as categories by which you can analyze your project data:

• Project

• Resource

• Project organization

• Expenditure organization

• Service type

• Time

• Budget type

• Expenditure type

• Operating unit (for multiple organization support)

Oracle Projects also predefines levels, which serve as subcategories forthese dimensions, and hierarchies, which store the relationshipsbetween each dimension and its levels. If the standard dimensions,levels, and hierarchies do not suit your business needs, you can createnew dimensions, levels, and hierarchies.

You can disable standard Oracle Projects dimensions that do not suityour company’s business requirements. For detailed information about

1 – 5Introduction

customizing your data warehouse data and metadata, see: CustomizingYour Integration: page 5 – 2.

See Also


Oracle Projects User’s Guide

Data Warehouse Uses

The following list provides just a few examples of applications for yourdata warehouse solution:

• Business analysis

• Product line analysis

• Service type analysis

• Project classification analysis

• Organization and budget type analysis

Business Analysis

You can analyze project performance and other details across variousdimensions, such as projects and organizations. In addition, you cancreate variance reports to compare actual costs to budgeted amounts,as illustrated in the following figure.

Figure 1 – 2


Use Oracle Sales Analyzer to compare the variance between actual costs and budgeted

raw costs for selected projects

Product Line Analysis

Monitor profitability and identify trends using project classes andcategories to distinguish your different product lines.

Service Type Analysis

You can compare cost, revenue, and budget data by type of activity orwork across all projects and organizations in your enterprise using theService Type dimension.

For example, you can establish standard service types to identify broadcategories of work, such as Field, Work, R&D, or Estimating. Then, byassigning these service types to your projects’ tasks, you can comparebudgeted costs with commitments and actual costs for these categoriesacross organizations or across project types. With this type of analysis,you can identify which types of activities consume resources and whichactivities generate revenue.

1 – 7Introduction

Project Classification Analysis

You can look across the enterprise at all projects by project classificationand time period to determine which lines of business are moreprofitable than others or whether the profitability of certain kinds ofprojects reflects seasonal variations.

Organization and Budget Type Analysis

You can analyze cost, revenue, and budget data across all projects byorganization and by budget type to compare both original and currentbudgets to actual costs to determine whether some organizations inyour enterprise are better than others at estimating costs at completion.

Benefits of Multiple Dimensions

With multidimensional analysis capabilities, you can generate a varietyof reports to view the information that is most important to yourcompany. For example, you can perform the types of analysis listedbelow:

• Top/Bottom Ranking. Identify your 10 best and 10 worstprojects in terms of margin.

• Exception. Display job grades for each consultant who hasgenerated monthly revenues of less than $10,000.

• Trend. Identify how business has changed over the past 52weeks in a particular industry sector.

You can also combine different types of analysis in a single report. Forexample, you can search for values based on exception criteria and thengenerate a report that ranks the results.

The following figures illustrate how the Ranking and Exception Setupwindow of Oracle Sales Analyzer enables the quick and easy creationof ranking reports.

Figure 1 – 3


Oracle Sales Analyzer enables you to create and format ranking reports

You can use your analysis tool to search for projects based on theiractual raw costs and rank the top five results, as illustrated above.

Figure 1 – 4

1 – 9Introduction

The resulting ranking report

The resulting report displays, in descending order, the projects thathave incurred the five highest actual raw cost amounts.

In addition, you can easily modify your analysis by changing one ormore dimensions in your query. You can analyze your projectinformation by selecting any of the standard dimensions available in alist of values (as illustrated in the following figure), or you can createyour own.

Figure 1 – 5


Use the Selector window to choose and organize the dimensions of your query

Other Applications and Benefits

Oracle Project Analysis Collection Pack also enables you to:

• Download information from the central repository to yourlaptop for disconnected analysis

• Empower executives with the project and resource data theyneed to make informed decisions faster

• Quickly generate quotes for customers based on historicalproject information

• Profitability analysis on resources across projects

• Rank the top or bottom projects across all organizations in yourcompany in terms of how actual costs and commitmentscompare to budgeted costs

• Analyze groups of projects (class categories and codes) over time

1 – 11Introduction

• Compare costs for each project organization by expenditureorganization

• Extend historical profitability figures into the future to estimatefuture revenue for budget planning and analysis

C H A P T E R

2T

2 – 1System Requirements

System Requirements

his chapter describes the requirements that you need to fulfill toinstall and implement Oracle Project Analysis Collection Pack,regardless of whether you customize your implementation of theproduct.


System Requirements

You must fulfill the following server requirements to integrate OracleProjects with OADW:

• Server requirements

– Oracle Applications Release 11 or higher

– Oracle Applications Data Warehouse Release 1.1 or higher

Note: You must install the OADW software before you installOracle Project Analysis Collection Pack.

For detailed steps on installing Oracle Project Analysis Collection Pack,see: Installing the Oracle Project Analysis Collection Pack OracleApplications Data Warehouse Installation Manual.

Profile Options

After you install Oracle Project Analysis Collection Pack, you must setyour Oracle Projects profile options to reflect how you will implementyour integration with OADW. For more information about OracleProjects profile options, see: Appendix B: Profile Options (OracleProjects User’s Guide).

PA: ADW Installed

Indicates whether Oracle Project Analysis Collection Pack is installed.This profile is automatically set to Yes when you install Oracle ProjectAnalysis Collection Pack. Oracle Projects does not use this profileoption; Oracle Applications Data Warehouse uses it only for integrationwith Oracle Projects.

Available values are listed below:

Oracle Project Analysis Collection Pack is installed,and related functionality will be available.

Only the core Oracle Projects product (eitherOracle Project Billing or Oracle Project Costing) isinstalled. Oracle Project Analysis Collection Packis not installed, and related functions will not beavailable.

Equivalent to No

Yes

No

(No value)

☞

2 – 3System Requirements

This profile option is visible to the System Administrator at theapplication level for Oracle Projects. You cannot update this profileoption.

The internal name for this profile option is PA_ADW_INSTALLED.

PA: Collection Pack Licensed

Indicates whether you have purchased and are a licensed user ofOracle Project Analysis Collection Pack.

Available values are listed below:

Oracle Project Analysis Collection Pack has beenpurchased and licensed. Entitles the user to relatedfeatures and support. You must enable this profileoption to use any features of Oracle ProjectAnalysis Collection Pack.

Default value is No, meaning that user does nothave access to Oracle Project Analysis CollectionPack features or support.

Equivalent to No

This profile option is visible to the System Administrator at theapplication level for Oracle Projects. You cannot update this profileoption.

The internal name for this profile option is PA_ADW_LICENSED.

PA: ADW Collect Top Tasks (for future use)

Indicates whether the collection program collects dimension and facttable information at the top task level. By default, this profile option isset to No.

Note: You cannot currently collect task–level information ifyou integrate Oracle Projects with Oracle Applications DataWarehouse. If you set this option to Yes, the Collection Packwill collect information at the top task level, but you cannotanalyze this information using OADW. You can, however,analyze task–level information using the Collection Pack withother tools.

Attention: You should set this profile before you startcollecting information for the interface tables. If you changethis profile option after you have run the collection process,then you must reload the interface tables using the RefreshDimension and Fact Tables process.

Yes

No

(No value)


This profile option is visible to the System Administrator andupdatable at the application level for Oracle Projects.

The internal name for this profile option isPA_ADW_COLLECT_TOP_TASKS.

C H A P T E R

3T

3 – 1Standard Architecture

Standard Architecture

his chapter describes the standard architecture of Oracle ProjectAnalysis Collection Pack. This chapter provides lists and descriptionsof all the standard dimensions, dimension hierarchies, and measuresthat Oracle Project Analysis Collection Pack predefines as well ascollection processes and views.

Figure 3 – 1


Oracle Project Analysis Collection Pack Architecture

Oracle Project Analysis Collection Pack provides the flexibility todisable standard dimensions for integration with OADW to suit yourcompany’s business requirements.

The following figure illustrates the information flow for Oracle ProjectAnalysis Collection Pack:

Information flow from Oracle Projects to OADW

CollectionProcess

OADW Server

Integrate withOADW

CustomDimension

and Fact

External Systems

ProductionSystemTables

Oracle Projects

Interface Tables(dimension and

fact)

Project Star SchemaInformation

Tables

The integration starts with the Oracle Projects summarization tables.After you run the Update Project Summary Amounts process topopulate the summarization tables, you submit the Collect Dimensionand Fact Tables process to load information from summarization tablesinto the project star schema interface tables. These interface tables arethe source tables for integration with OADW and act as a temporaryholding place for information to be integrated with OADW. You canmodify the collection process to load data from other Oracle Projectstables into the project star schema interface tables.

Note: The project star schema interface tables are differentfrom the OADW interface tables.

After you populate the project star schema interface tables, you loadthe information into OADW tables using the OADW collection process.From the OADW tables, you can access and analyze your data using avariety of client applications. After you transfer the information to theOADW tables, you can purge the project star schema interface tables.

☞


See Also

Collect Dimension and Fact Tables (Oracle Projects User’s Guide)

Refresh Dimension and Fact Tables (Oracle Projects User’s Guide)

Generate Collection Views (Oracle Projects User’s Guide)


Oracle Express Analyzer User’s Guide

Oracle Sales Analyzer User’s Guide

Standard Dimensions, Hierarchy Levels, and Measures

Refer to the lists of standard dimensions, dimension hierarchies, andmeasures in this section to determine whether you need to customizeyour integration with OADW. For more information about revising themetadata and data predefined by Oracle Project Analysis CollectionPack, see: Customizing Your Integration: page 5 – 2.

Attention: Oracle Project Analysis Collection Pack predefinesthe dimension, hierarchy level, and measure related metadatafor Oracle Projects in the OADW repository.

Dimensions

Oracle Project Analysis Collection Pack predefines the followingstandard dimensions, all of which are enabled by default. If you do notplan to use all the dimensions to analyze your project data, you candisable any dimension below that is marked with an asterisk (*).

• Project

• Resource

• Project organization*

• Expenditure organization*

• Service type*

• Time

• Budget type


• Expenditure type*

• Operating unit (for multi–organization support)*

You can define up to five additional dimensions in each standard facttable to store actuals, commitments, and budgeted costs.

Dimension Hierarchy Levels

Oracle Project Analysis Collection Pack predefines one hierarchy foreach of the dimensions listed above. The standard hierarchy levels foreach dimension are listed below:

• Project

All project types (none specified) Project type Project

• Resource

Resource list Resource group Resource member (lowest–level resource)

Note: Before you can analyze information using a particularresource list, you must first assign it to the project and run theUpdate Project Summary Amounts process for each project youwant to include in your analysis. This process summarizesinformation for all resource lists assigned to a project.

• Project organization

Business group Project organization

• Expenditure organization

Business group Expenditure organization

• Service type

All service types (none specified) Service type

Note: By default, service type information is collected at thetop task level. You can change the collection process to loadservice type information at different levels of the WBS. If youuse this dimension to analyze task information, make sure thatyour data originates from the same level of the WBS. For


example, you cannot use the service type dimension to analyzetop task budget amounts and lowest task actuals.

• Time

All financial years (none specified) Financial year Financial quarter GL period PA period

• Budget type

Budget type

• Expenditure type

All expenditure types (none specified) Expenditure type

• Operating unit

Set of books Legal entity Operating unit

The operating unit dimension allows you to analyze informationfor projects of all operating units that use the same functionalcurrency. If multiple sets of books use the same currency, youcan add another level to this hierarchy, such as All sets of books, toanalyze projects that are owned by operating units that usedifferent sets of books. For information on adding a hierarchylevel, see: Creating Hierarchies or Hierarchy Levels: page 5 – 5.

Measures

Oracle Project Analysis Collection Pack predefines the followingstandard measures, all of which are enabled by default. If thesemeasures do not suit your business needs, you can modify yourinterface views so that the collection process loads differentinformation into the fact interface tables.

• Actuals

– Raw cost

– Burdened cost

– Quantity

– Labor hours


– Billable/Capitalizable raw cost

– Billable/Capitalizable burdened cost

– Billable/Capitalizable quantity

– Billable/Capitalizable labor hours

– Revenue

• Commitments

– Raw cost

– Burdened cost

• Budgets

– Raw cost

– Burdened cost

– Quantity

– Labor hours

– Revenue

You can define up to five additional measures in each standard facttable to store actuals and commitments.

Interface Tables

There are two types of interface tables: fact tables and dimensiontables. Fact tables contain numeric information, while dimensiontables store descriptive information that you can use to provide contextfor the fact table information.

Fact tables consist of two types of columns:

• Keys, which link to the descriptive information represented bydimension attributes, as described below

• Measures, which identify what a specific number represents.

Figure 3 – 2


Illustration of dimension tables and a fact table

PROJECT KEYTIME KEYRESOURCE KEYEXPENDITURE ORG. KEY Dollars Hours Worked Resource Usage

PROJECT KEY All project types Project type Project

RESOURCE KEY Resource list Resource group Resource member

Project Dimension

Resource Dimension

EXPENDITURE ORG. KEY

Expenditure Org. Dimension

Business group Expenditure org.

TIME KEY

Time Dimension

All financial years Financial year Financial quarter GL period PA period

Fact Table

Dimension tables consist of separate columns for each hierarchy level,which represent additional categories for each dimension. Mostdimensions have multiple hierarchy levels at which you can captureand analyze information.

Oracle Project Analysis Collection Pack provides one interface databaseview for each interface table, and the data read by an interface view(via the collection program) populates its corresponding interface table.

You can use all of the standard measures, dimensions, and dimensionhierarchies that Oracle Project Analysis Collection Pack predefines, oryou can create your own. For more information about customizing thedata warehouse, see: Customizing Your Integration: page 5 – 2.

Dimension Interface Tables

Oracle Project Analysis Collection Pack provides interface tables foreach hierarchy level on standard dimensions, as illustrated in thefollowing table:


Interface Table Name Dimension Level

PA_ALL_PRJ_TYPES_IT Project All Project Types

PA_PRJ_TYPES_IT_ALL Project Project Type

PA_PROJECTS_IT_ALL Project Project

PA_TOP_TASKS_IT* Project Top Task

PA_ALL_EXP_TYPES_IT Expenditure Type All Expenditure Types

PA_EXP_TYPES_IT Expenditure Type Expenditure Type

PA_RES_LISTS_IT_ALL_BG Resource Resource List

PA_TOP_RLMEM_IT Resource Resource Group

PA_LOWEST_RLMEM_IT Resource Resource Member(lowest–level resource)

PA_ALL_SRVC_TYPES_IT Service Type All Service Types

PA_SRVC_TYPES_IT Service Type Service Types

PA_ALL_FINANCIAL_YRS_IT Time All Financial Years

PA_FINANCIAL_YRS_IT Time Financial Year

PA_FINANCIAL_QTRS_IT Time Financial Quarter

PA_GL_PERIODS_IT Time GL Period

PA_PERIODS_IT Time PA Period

PA_BGT_TYPES_IT Budget Type Budget Type

PA_PRJ_BUSINESS_GRPS_IT Project Organization Business Group

PA_PRJ_ORGS_IT Project Organization Project Organization

PA_EXP_BUSINESS_GRPS_IT ExpenditureOrganization

Business Group

PA_EXP_ORGS_IT ExpenditureOrganization

Expenditure Organization

PA_SET_OF_BOOKS_IT Operating Unit Set Of Books

PA_LEGAL_ENTITY_IT Operating Unit Legal Entity

PA_OPER_UNITS_IT Operating Unit Operating Unit

* Not currently supported for integration with OADW

Table 3 – 1 Standard dimension interface tables

Fact Interface Tables

Oracle Project Analysis Collection Pack provides the followingstandard fact interface tables:


Interface Table Name Fact Table

PA_TSK_ACT_CMT_IT_ALL* Task Level Actuals and Commitments

PA_PRJ_ACT_CMT_IT_ALL Project Level Actuals and Commitments

PA_TSK_BGT_LINES_IT_ALL* Task Level Budgets

PA_PRJ_BGT_LINES_IT_ALL Project Level Budgets


Table 3 – 2 Standard fact interface tables

Collection Views

Oracle Project Analysis Collection Pack uses two levels of collectionviews: base views and second–level views.

To preserve the integrity of the base views in case of a databaseupgrade, you cannot modify these views. These base views readinformation directly from the Oracle Projects summarization tables.The second–level views read information from these base views andcontain 10 columns that you can customize after disabling unnecessarydimensions to bring additional data into your data warehouse.Collection programs are based upon these second–level views.

Dimension Table Collection Views

Oracle Project Analysis Collection Pack provides the following baseand second–level collection views for dimension tables:

Second–Level View Name Base View Dimension Level

PA_ADW_PRJ_TYPES_V PA_ADW_PRJ_TYPES_B_V Project All ProjectTypes/ProjectType

PA_ADW_PROJECTS_V PA_ADW_PROJECTS_B_V Project Project

PA_ADW_TOP_TASKS_V* PA_ADW_TOP_TASKS_B_V* Project Top Task

PA_ADW_EXP_TYPES_V PA_ADW_EXP_TYPES_B_V Expenditure Type All levels

PA_ADW_RES_LISTS_V PA_ADW_RES_LISTS_B_V Resource Resource List

PA_ADW_TOP_RLMEM_V PA_ADW_TOP_RLMEM_B_V Resource Resource Group

PA_ADW_LOWEST_RLMEM_V

PA_ADW_LOWEST_RLMEM_B_V

Resource ResourceMember(lowest–levelresource)

Table 3 – 3 Standard dimension table collection views


Second–Level View Name LevelDimensionBase View

PA_ADW_SRVC_TYPES_V PA_ADW_SRVC_TYPES_B_V Service Type All levels

PA_ADW_PERIODS_V PA_ADW_PERIODS_B_V Time All levels

PA_ADW_ORGS_V PA_ADW_ORGS_B_V ProjectOrganization/ExpenditureOrganization

All levels

PA_ADW_OPER_UNITS_V PA_ADW_OPER_UNITS_B_V Operating Unit All levels

PA_ADW_BGT_TYPES_V PA_ADW_BGT_TYPES_B_V Budget Type Budget Type


Table 3 – 3 Standard dimension table collection views

Fact Table Collection Views

Oracle Project Analysis Collection Pack also provides the followingbase and second–level collection views for fact tables:

Second–Level View Name Base View Related Measure

PA_ADW_ACT_CMT_V PA_ADW_ACT_CMT_B_V Actuals and Commitments

PA_ADW_R_ACT_CMT_V PA_ADW_R_ACT_CMT_B_V Actuals and Commitments

PA_ADW_R_ST_ACT_CMT_V PA_ADW_R_ST_ACT_CMT_B_V Actuals and Commitments

PA_ADW_BGT_LINES_V PA_ADW_BGT_LINES_B_V Budget Amounts

PA_ADW_R_BGT_LINES_V PA_ADW_R_BGT_LINES_B_V Budget Amounts

Table 3 – 4 Standard fact table collection views

Collecting Dimension and Fact Tables

You submit the PRC: Collect Dimension and Fact Tables process fromthe Submit Request window to load information into either dimensionor fact interface tables. See: Collect Dimension and Fact Tables (OracleProjects User’s Guide).

The collection program populates separate interface tables to storeinformation about actual transactions and budgets. ThisPL/SQL–based process selects data from the Oracle Projectssummarization tables based on the dimensions that your companyuses. The collection program maintains the interface tables. Thecollection program is modular, which means that a separate programloads each interface table. In addition, you can customize the processto collect information from custom dimension and fact tables.

Figure 3 – 3

☞


Update information in the interface tables as often as required by yourcompany’s business needs. The collection program provided by OracleProjects performs incremental uploads of information, which meansthat the process updates only the information that has changed sincethe last upload. This strategy minimizes the length of your uploadprocess.

The collection program retrieves project information based on theoperating unit of the user submitting the request. If you want to collectproject information for multiple operating units, you must run thecollection process separately for each operating unit.

By default, each operating unit must run its own collection process

Project Star Schema

InterfaceTables

OperatingUnit 1

OperatingUnit 2

OperatingUnit X.............

Collection Process Collection Process Collection Process

Attention: Before you load project information into theinterface tables, you must run the Update Project SummaryAmounts process for all projects you want to analyze.

Database Triggers

Oracle Projects tables contain database triggers that indicate whichrows of information that the collection process reads. If theADW_NOTIFY_FLAG parameter of a source table row equals ’Y’, thenthe collection program copies the row into the appropriate interface


table. You must add triggers to or modify them in related source tablesif you create or delete measures, respectively. If you create new facttables, you can use database triggers in the related source tables toidentify the changed rows for the collection process. The followingtable provides names of the triggers and affected Oracle Projects tables:

Table Name Trigger Name

PA_TASKS PA_ADW_TASKS_T1

PA_TASKS PA_ADW_TASKS_T2

PA_PROJECTS_ALL PA_ADW_PROJECTS_T1

PA_PROJECT_TYPES_ALL PA_ADW_PROJECT_TYPES_T1

PA_EXPENDITURE_TYPES PA_ADW_EXPENDITURE_TYPES_T1

PA_PROJECT_CLASSES PA_ADW_PROJECT_CLASSES_T1

PA_CLASS_CATEGORIES PA_ADW_CLASS_CATEGORIES_T1

PA_CLASS_CODE PA_ADW_CLASS_CODES_T1

PA_RESOURCE_LIST_MEMBERS PA_ADW_RESOURCES_T1

PA_RESOURCES PA_ADW_RESOURCES_T2

PA_RESOURCE_LIST_ALL_BG PA_ADW_RESOURCE_LISTS_T1

PA_BUDGET_TYPES PA_ADW_BUDGET_TYPES_T1

PA_TXN_ACCUM PA_ADW_TXN_ACCUM_T1

PA_RESOURCE_ACCUM_DETAILS PA_ADW_RES_ACCUM_DET_T1

Table 3 – 5 Trigger names and related Oracle Projects tables

C H A P T E R

4T

4 – 1Implementation Considerations

ImplementationConsiderations

his chapter describes the factors that you need to consider in yourdecision to implement Oracle Project Analysis Collection Pack andwhether you need to customize the standard configuration.

Figure 4 – 1


Implementing Oracle Project Analysis Collection Pack

You must consider many factors when deciding whether to integrateOracle Projects with OADW and how to implement the integration.The flow chart below illustrates the questions you should ask yourselfduring this decision–making process. The rest of this section providesa detailed discussion of each decision point represented in the flowchart and the consequences of your decisions.

Flow chart illustrating implementation decisions and warehouse creation/maintenance

Do thestandard dimensionsand measures meet

my businessneeds?

Unfreezethe OADWrepository

Implement thestandard OracleProject AnalysisCollection Pack

features

Do I need todisable standard

dimensions?

Disable dimensionsusing the

Dimensions window

Do I need todisable standard

measures?

Disable measuresby modifying

collection views

Do I needto add custom

dimensions, hierarchies,or fact tables?

Performcustomizations

FreezeOADW

metadataGenerate

warehouseMaintain

warehouse

Yes

No

Yes

Yes

No

No

Yes

No

Implementation

4 – 3Implementation Considerations

Do the standard dimensions and measures fulfill my businessneeds?

To answer this question, you must identify the goal or goals of youranalysis. For example, you may want to compare actuals, budgets, andcommitments or perform product line analysis. For each goal, youmust decide what formula best represents the end result you want toachieve. You include both descriptive and numeric variables in yourformula.

Compare the descriptive and numeric variables you identified with thelist of standard dimensions and measures. Depending on the type ofreporting and analysis your company performs, you may need tocustomize your data warehouse integration by adding or deletingdimensions and measures. For a list of the standard dimensions andmeasures provided by Oracle Projects, see: Standard Dimensions,Hierarchy Levels, and Measures: page 3 – 3.

Do I need to disable standard dimensions?

As previously mentioned, the standard dimensions delivered withOracle Projects may not completely meet your reporting and analysisneeds. If you need only a subset of the standard dimensions, you candisable one or more dimensions using the Dimensions window. See:Disabling Standard Dimensions: page 5 – 3.

Note: Disabling unnecessary dimensions reduces the size ofyour data warehouse and speeds the collection process.

Do I need to disable standard measures?

As previously mentioned, the standard measures delivered with OracleProjects may not completely meet your reporting and analysis needs. Ifyou need only a subset of the standard measures, you can modify yourinterface views to read only the numeric information you need. See:Disabling Standard Measures: page 5 – 4.

Note: Disabling unnecessary measures reduces the size of yourdata warehouse and speeds the collection process.

Do I need to add custom dimensions, hierarchs, or fact tables?

If you need to report or analyze your corporate information by acategory that is not represented by a standard dimension or hierarchylevel, you must create a new dimension or hierarchy level to capturethis additional information.

☞


Attention: Creating new dimensions after you have set upand used your data warehouse is labor–intensive andtime–consuming. Carefully assess your company’s current andfuture needs and try to identify all the customizations that youwill need before you start to use your data warehouse.

For detailed information about creating a new dimension, see: CreatingDimensions: page 5 – 4. For detailed information about creating a newhierarchy level, see: Creating Hierarchies or Hierarchy Levels: page5 – 5.

If your data warehouse does not include all the numeric informationthat you need to analyze, you can modify your interface views tocapture additional information. For more information about addingmeasures and fact tables, see: Creating Measures: page 5 – 5 andCreating Fact Tables: page 5 – 6.

C H A P T E R

5T

5 – 1Customizations

Customizations

his chapter describes the steps you perform to customize yourimplementation of Oracle Project Analysis Collection Pack. Thisincludes disabling standard dimensions, hierarchy levels, andmeasures; creating new dimensions, hierarchy levels, measures, andfact tables; and modifying the collection processes.

☞


Customizing Your Integration

You may require only a subset of the standard dimensions, hierarchylevels, and measures provided by Oracle Project Analysis CollectionPack, or you may require additional dimensions, hierarchy levels, andmeasures. If this is the case, you can customize your integration withOADW by altering the 10 customizable columns for each standarddimension table and each standard fact table. In addition, you cancreate new dimensions and measures or disable existing ones if theinformation predefined by Oracle Project Analysis Collection Pack doesnot suit your business needs. Alternately, you can create new facttables that you can analyze in conjunction with your customizeddimension tables.

Warning: Plan and execute all of your customizations beforeyou load information into the interface tables and generateyour data warehouse. If you perform customizations after youimplement and use the data warehouse, you must regeneratethe data warehouse, which can be very time–consuming.

You can perform the following customizations to Oracle ProjectAnalysis Collection Pack:

• Disabling standard metadata

– dimensions

– measures

– hierarchies

• Creating new metadata

– dimensions

– measures

– hierarchies

– fact tables

– building hierarchies of class categories

Attention: You perform some customization steps in yourOracle Projects environment and others in OADW, as noted onthe following pages.

☞


Disabling Standard Metadata

Disable standard metadata that your company does not need foranalysis or reporting purposes. Disabling unnecessary metadataimproves the performance of the collection processes and reduces thesize requirements for your data warehouse.

Disabling Standard Dimensions

You can disable some of the Oracle Projects standard dimensions byusing the Oracle Projects Dimensions window. When you use thiswindow to disable a dimension, the metadata about the dimension isautomatically deleted from the OADW repository database. You mustregenerate the collection views after disabling any standard dimension.For more information regarding this window, see: Implementing OracleProject Analysis Collection Pack for Oracle Projects Integration (OracleProjects User’s Guide).

� To enable or disable a standard dimension using the Dimensionswindow:

Attention: You must disable dimensions before freezing thedata warehouse metadata in the OADW repository and beforecustomizing your collection views. If you subsequently enableor disable a dimension after you have generated the OADWruntime warehouse, you must regenerate the runtimewarehouse to collect data based on the new set of dimensions.

1. From the Navigator window, choose Setup > Collection Pack >Dimensions.

2. Check the Enable check box next to the dimension you want toenable, or uncheck it if you want to disable the dimension.

3. Save your changes.

4. Choose Regenerate Views to regenerate the collection views basedon the new set of dimensions.

The view generation process recreates the database views andcreates a view definition file in the concurrent manager’s logdirectory. After the generation process has executed successfully,you can use the concurrent request log file to extract the script tocustomize the view definition file . You must apply the customizedview definitions after the view generation process executessuccessfully.

☞


Disabling a dimension replaces the column representing thedimension with –1 or UNKNOWN, depending on the datatype ofthe column.

Attention: If you ran either collection process before enablingor disabling standard dimensions, you must submit the PRC:Refresh Dimension and Fact Tables process after youregenerate your views to update information based on yourchanges.

Disabling Standard Measures

You disable a measure by modifying each collection view that containsthe measure and modifying database triggers in the related sourcetables. For sample view changes that you can use to disable a measure,see: Modifying Collection Views to Disable or Create a Measure: pageA – 2.

Note: Collection views reside in the Oracle Projects productiondatabase.

In addition, you must delete the metadata information related to thedeleted measure from the OADW repository using OADW windows.For more information about these windows, see: Defining the OADWMetadata (Oracle Applications Data Warehouse User’s Guide).

Disabling Hierarchies or Hierarchy Levels

You disable hierarchies and hierarchy levels by deleting the relatedOADW metadata using OADW windows. For more information aboutthese windows, see: Using the Hierarchy Editor (Oracle ApplicationsData Warehouse User’s Guide).

Creating New Metadata

If the standard metadata provided by Oracle Project AnalysisCollection Pack does not fulfill your company’s reporting and analysisrequirements, you can create customized metadata to populate yourdata warehouse with the additional information you need.

Creating Dimensions

You must define a new interface table for any new dimension andrelated hierarchy levels that you create. You can use an architecture


similar to the architecture used to collect standard dimensions andhierarchy levels. Perform the following steps to create newdimensions:

1. Write a collection procedure to retrieve information from thedesired source table (from Oracle Projects or an external system)and load it into the interface table

2. Add the procedure to the custom collection packagePA_ADW_CUSTOM_COLLECT so that the collection process willload information related to the new dimension along with thestandard dimension and fact tables. This package contains twofiles:

• PAADWCCS.pls

• PAADWCCB.pls

To include the new dimension in an existing fact table, you mustchange the collection views for the fact table.

You use OADW windows to create new dimension related metadata inthe OADW repository. For more information about the windowsprovided by OADW, see: Defining Dimensions (Oracle Applications DataWarehouse User’s Guide).

Creating Measures

You create new measures by changing the related fact table collectionviews and adding database triggers to the new source tables. Forsample view changes that you can use to create a measure, see:Modifying Collection Views to Disable or Create a Measure: page A – 2.

Note: Collection views reside in the Oracle Projects productiondatabase.

After changing the views, use OADW windows to add metadatarelated to the new measure in the OADW repository. For moreinformation about the windows provided by OADW, see: CreatingCube Attributes (Oracle Applications Data Warehouse User’s Guide).

Creating Hierarchies or Hierarchy Levels

You can create new hierarchies based on standard hierarchies. Youpopulate the level information either in the standard dimension table, ifyou are adding new hierarchies on the standard dimensions, or createnew level tables similar to the standard level tables. An example of thestandard hierarchies on the project dimension is given below. After the

Figure 5 – 1


level information is populated, then you create OADW metadata in theOADW repository database using OADW forms for the newhierarchies.

Example of building a hierarchy upon the projects dimension

All Project Types Level

All Project Types

Project Type Level

Project Type Description All Project Types

Project Level

Name Number Project Type

Table PA_ALL_PRJ_TYPES_IT

Table PA_PRJ_TYPES_IT_ALL

Table PA_PROJECTS_IT_ALL

Creating Fact Tables

To analyze additional information, you must build one or more newfact tables, similar to the fact tables for Actuals and Budgets forstandard measures. Perform the following steps to create new facttables:

1. Define a collection procedure similar to the procedure used tocollect standard fact tables. You can use database triggers in thesource table to identify the changed rows.

2. Add the procedure to the custom collection packagePA_ADW_CUSTOM_COLLECT so that the collection process willload information into the new fact table when the standarddimension and fact tables are collected. This package contains twofiles:

• PAADWCCS.pls

• PAADWCCB.pls


3. Use OADW windows to define the OADW repository metadatanecessary for the custom fact tables. For more information aboutthe windows provided by OADW, see: Defining Cubes (OracleApplications Data Warehouse User’s Guide).

Building Hierarchies on Class Categories

Oracle Project Analysis Collection Pack does not support the classcategory hierarchy as a standard hierarchy, since you can categorize aproject for multiple class codes within a class category. The followingtable provides hierarchy level and interface table information for classcategory and class code information related to each project:

Interface Table Name Collection View Level

PA_PRJ_CLASSES_IT PA_ADW_PRJ_CLASSES_V Project Class Code

PA_CLASS_CATGS_IT PA_ADW_CLASS_CATGS_V Class Category

PA_CLASS_CODES_IT PA_ADW_CLASS_CODES_V Class Code

Table 5 – 1 Interface table and collection views for class code and category levels

Perform the following steps to create a hierarchy for a given classcategory. You must perform these steps separately for each classcategory for which you want to define hierarchy levels.

1. Use the Oracle Projects Class Code setup windows to identify theclass codes for which you want to build hierarchies for analysis.

2. Use the Project dimension to create new levels and hierarchies inOADW.

Create a project class level for each class within a given classcategory for the project dimension. You can use this level toanalyze information for each class code within a class category.

Create one project class level for the project dimension. You canuse this level to analyze information across all class codes within aclass category.

Create separate hierarchies for each class with the class level as theroot level. Create a project class level and project level below theroot level.

3. Create an OADW interface table for each project class level.

4. Create an OADW interface table for the class level.

5. Customize the collection process for the PA_PRJ_CLASSES_IT tableto include the Segment1 column from the PA_PROJECTS_ALLtables and the class_code and class_category columns from the

Figure 5 – 2


PA_PROJECT_CLASSES table into the USER_COL1 column. Youcan use the USER_COL1 column as a description for the projectclass level.

6. Define the collection for each of the new interface tables. UsePA_CLASS_CATEGS_IT as the source table for the class level table,and the PA_PRJ_CLASSES_IT source table for the project classlevel. Specify the WHERE clause for the class_code andclass_category columns.

Example of building a hierarchy upon the class category

Class Level

Project Class Level

Project Level

C H A P T E R

6

T

6 – 1Generating and Installing Your Data Warehouse

Generating andInstalling Your DataWarehouse

his chapter describes how to generate and install the datawarehouse based on the information you load into the Oracle ProjectAnalysis Collection Pack interface tables.


Generating and Installing Your Data Warehouse

After you have performed your customizations, such as creating newor disabling existing dimensions, hierarchy levels, and measures, youare ready to generate and install your data warehouse.

For detailed instructions on generating and installing your datawarehouse, see: Generating and Installing the OADW Warehouse(Oracle Applications Data Warehouse User’s Guide). This manual providescomplete instructions on performing the following steps:

1. Freezing OADW metadata. As a prerequisite to generating andinstalling the OADW warehouse, you must freeze your metadatadefinitions. As part of this process, OADW revalidates themetadata to verify that the definitions are correct and gives you afinal opportunity to correct errors.

2. Generating the installation script. During the generation process,you generate OADW warehouse internal metadata, createinstallation scripts for each installed module and the OADWwarehouse, and optionally create custom collection scripts.

3. Installing the warehouse. During the installation process, you runthe installation scripts and create the OADW warehouse.

C H A P T E R

7

T

7 – 1Collecting Data and Maintaining the Data Warehouse

Collecting Data andMaintaining the DataWarehouse

his chapter describes how to run the collection process to populateyour data warehouse and use end–user tools, such as Oracle ExpressAnalyzer and Oracle Sales Analyzer, to analyze and generate reportsbased on your project–related information.

☞

Figure 7 – 1

Step 1


Overview of Collecting Data and Maintaining Your Warehouse

After you generate and install your warehouse, you must performmaintenance steps as your company continues to collect projectinformation or as your company’s reporting and analysis needs change.These steps are identified in the diagram below.

Attention: If you want to collect information based on newdimensions, hierarchy levels, or measures, you must performyour customizations and regenerate your data warehouse.

Data warehouse maintenance steps

Run OracleProjects

collectionprocesses

Run OADWcollection, update,and synchronize

processes

GenerateRelational

AccessManager (RAM)

Publishwarehouse

FreezeOADW

metadataGenerate

warehouseMaintain

warehouse

Excerpt from illustration on page 4 – 2

To update your warehouse to include the latest data from projectactivity, you must perform the steps described in this section.

Run the Update Project Summary Amounts process in OracleProjects

You can run this process as many times as you want for one or moreprojects.

Step 2

Step 3

Step 4

7 – 3Collecting Data and Maintaining the Data Warehouse

Run the Collect Dimension and Fact Tables process in OracleProjects

This process collects information from the Oracle Projects productionsummarization tables and loads it into dimension and fact interfacetables. The process selects data based on the dimensions and measuresthat you define when you implement Oracle Project Analysis CollectionPack. This collection process is incremental, which means it loads onlyinformation that changed since the last collection process was run.

This process collects dimension and fact table information from theoperating unit of the employee submitting the process. To collect andanalyze information from multiple operating units, you must run thecollection process separately for each operating unit.

Run the OADW collection, update, and synchronize processes

For detailed information about these OADW process, see:Administering the OADW Warehouse (Oracle Applications DataWarehouse User’s Guide).

Generate Express/RAM (Relation Access Manager)

Perform this step to prepare your information to be accessed by OracleExpress Analyzer or Oracle Sales Analyzer. For detailed informationabout this build process, refer to the Express/RAM user manual andAdministering the OADW Warehouse (Oracle Applications DataWarehouse User’s Guide). For detailed information about using theAnalyzer tools, refer to the manuals entitled Oracle Express AnalyzerUser’s Guide and Oracle Sales Analyzer User’s Guide.

See Also

Processes (Oracle Projects User’s Guide)

A P P E N D I X

AT

A – 1Modifying Fact Collection Views

Modifying FactCollection Views

his appendix provides sample view changes that you can use tomodify the collection views to disable a standard measure or to create anew measure.

A – 2 Oracle Project Analysis Collection Pack Implementation Guide

Modifying Collection Views to Disable or Create a Measure

You must modify the related collection views to disable a standardmeasure or to create a new measure. This appendix provides sampleview changes that you would use to disable the measureACTUAL_LABOR_HOURS and add the measureACCUME_BURDENED_COST – ACCUME_RAW_COST. Modify thesample view changes as necessary to satisfy your company’s analysisand reporting requirements.

Note: You must add triggers to or modify them in the relatedsource tables if you create or delete measures, respectively.

Disabling a Standard Measure

To disable a measure, you must modify the related fact table collectionviews. For example, to disable the measureACTUAL_LABOR_HOURS, you would make the following changes tothe collection views listed below.

• PA_ADW_ACT_CMT_V

• PA_ADW_R_ACT_CMT_V

• PA_ADW_R_ST_ACT_CMT_V

Note: In addition to modifying the related collection views,use OADW windows to delete the related metadata from theOADW repository. For more information about the windowsprovided by OADW, refer to the Oracle Applications DataWarehouse User’s Guide.

CREATE OR REPLACE VIEW PA_ADW_ACT_CMT_V

(

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,

EXPENSE_ORGANIZATION_ID,

OWNER_ORGANIZATION_ID,

RESOURCE_LIST_MEMBER_ID,

SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,


USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,

ACCUME_BURDENED_COST,

ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,

ACCUME_BILLABLE_RAW_COST,

ACCUME_BILLABLE_BURDENED_COST,

ACCUME_BILLABLE_QUANTITY,

ACCUME_BILLABLE_LABOR_HOURS,

ACCUME_CMT_RAW_COST,

ACCUME_CMT_BURDENED_COST,

ACCUME_CMT_QUANTITY,

UNIT_OF_MEASURE,

RES_ADW_NOTIFY_FLAG,

TXN_ADW_NOTIFY_FLAG

) AS

SELECT

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,


ACCUME_RAW_COST,


ACCUME_QUANTITY,

NULL, /* Disabled Measure ACCUME_LABOR_HOURS, */








UNIT_OF_MEASURE,


TXN_ADW_NOTIFY_FLAG

FROM

PA_ADW_ACT_CMT_B_V;

CREATE OR REPLACE VIEW PA_ADW_R_ACT_CMT_V

(

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,









UNIT_OF_MEASURE,


TXN_ADW_NOTIFY_FLAG,

TSK_ADW_NOTIFY_FLAG

) AS

SELECT

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,









UNIT_OF_MEASURE,




TSK_ADW_NOTIFY_FLAG

FROM

PA_ADW_R_ACT_CMT_B_V;

CREATE OR REPLACE VIEW PA_ADW_R_ST_ACT_CMT_V

(

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,








UNIT_OF_MEASURE,



TSK_ADW_NOTIFY_FLAG

) AS

SELECT

PROJECT_ID,


TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,









UNIT_OF_MEASURE,



TSK_ADW_NOTIFY_FLAG

FROM

PA_ADW_R_ST_ACT_CMT_B_V;

Creating a Measure

To create a measure, you must modify the related fact table collectionviews. For example, to create the measure


ACCUME_BURDENED_COST–ACCUME_RAW_COST, you wouldmake the following changes to the collection views listed below.

• PA_ADW_ACT_CMT_V

• PA_ADW_R_ACT_CMT_V

• PA_ADW_R_ST_ACT_CMT_V

Note: In addition to modifying the related collection views,use OADW windows to add related metadata to the OADWrepository. For more information about the windows providedby OADW, refer to the Oracle Applications Data Warehouse User’sGuide.

CREATE OR REPLACE VIEW PA_ADW_ACT_CMT_V

(

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,









UNIT_OF_MEASURE,


TXN_ADW_NOTIFY_FLAG

) AS

SELECT

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

ACCUME_BURDENED_COST – ACCUME_RAW_COST, /* New measure

USER_COL6, */

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,








UNIT_OF_MEASURE,


TXN_ADW_NOTIFY_FLAG

FROM

PA_ADW_ACT_CMT_B_V;


CREATE OR REPLACE VIEW PA_ADW_R_ACT_CMT_V

(

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,








UNIT_OF_MEASURE,



TSK_ADW_NOTIFY_FLAG

) AS

SELECT

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,





SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,


USER_COL6, */

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,








UNIT_OF_MEASURE,



TSK_ADW_NOTIFY_FLAG

FROM

PA_ADW_R_ACT_CMT_B_V;

CREATE OR REPLACE VIEW PA_ADW_R_ST_ACT_CMT_V

(

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,


USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,

USER_COL6,

USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,








UNIT_OF_MEASURE,



TSK_ADW_NOTIFY_FLAG

) AS

SELECT

PROJECT_ID,

TOP_TASK_ID,

TASK_ID,

PA_PERIOD_KEY,




SERVICE_TYPE_CODE,

EXPENDITURE_TYPE,

USER_COL1,

USER_COL2,

USER_COL3,

USER_COL4,

USER_COL5,


USER_COL6, */


USER_COL7,

USER_COL8,

USER_COL9,

USER_COL10,

ACCUME_REVENUE,

ACCUME_RAW_COST,


ACCUME_QUANTITY,

ACCUME_LABOR_HOURS,

ACCUME_LABOR_HOURS,








UNIT_OF_MEASURE,



TSK_ADW_NOTIFY_FLAG

FROM

PA_ADW_R_ST_ACT_CMT_B_V;

A P P E N D I X

BT

B – 1Sample Reports

Sample Reports

his appendix provides a listing of reports that you can createusing the standard dimensions, hierarchy levels, and measurespredefined by Oracle Project Analysis Collection Pack. You cangenerate these reports using such tools as Oracle Sales Analyzer andOracle Express Analyzer. You can also present some of the reports inthis chapter as graphs.

B – 2 Oracle Project Analysis Collection Pack Implementation Guide

Report Listing

The following list includes reports that you can generate using thestandard dimensions, hierarchy levels, and measures provided byOracle Project Analysis Collection Pack. This chapter also providessample reports, which are included for illustrative purposes only. Youmay generate a completely different set of reports, depending on yourcompany’s reporting and analysis requirements.

• Project Organization View: page B– 3

• Project View by Activity (Service Type): page B– 4

• Project Organization View by Activity (Service Type): page B– 5

• Top 3 Projects with Best Budgeted Cost to Actual Cost Variances:page B– 6

• Bottom 2 Projects with Lowest Revenue: page B– 7

• Top 2 Projects with Highest Revenue: page B– 8

• Margin View: page B– 9

Sample Reports B – 3

Pro

ject

Org

aniz

atio

n V

iew

Thi

s re

port

pro

vid

es th

e ac

tual

raw

cos

t am

ount

s, b

udge

ted

raw

cos

t am

ount

s, a

ndva

rian

ces

for

proj

ect o

rgan

izat

ions

wit

hin

Vis

ion

Cor

pora

tion

. T

his

repo

rt d

ispl

ays

info

rmat

ion

for

all f

inan

cial

yea

rs a

nd fo

r 19

97 b

ased

on

the

appr

oved

cos

t bud

get.

Vis

ion

Ser

vice

s (U

SA

)

All

Fin

anci

al Y

ears

1997

Act

ual

Raw

Cos

tB

udge

ted

Raw

Cos

tB

udge

ted

Cos

t–

Act

ual C

ost

Act

ual

Raw

Cos

tB

udge

ted

Raw

Cos

tB

udge

ted

Cos

t–

Act

ual C

ost

Vis

ion

Cor

pora

tion

577,

733.

2365

9,27

6.96

81,5

43.7

354

7,96

9.69

658,

986.

6411

1,01

6.95

C

onsu

lting

–Eas

t29

6,83

5.40

502,

200.

0020

5,36

4.60

296,

835.

4050

2,20

0.00

205,

364.

60

C

onsu

lting

–Wes

t40

,080

.00

31,0

77.0

0(9

,003

.00)

40,0

80.0

031

,077

.00

(9,0

03.0

0)

E

xecu

tive

Offi

ce22

0,24

9.94

36,0

00.0

2(1

84,2

49.9

2)19

0,48

6.40

35,7

09.7

0(1

54,7

76.7

0)

In

form

atio

n S

ervi

ces

20,5

67.8

989

,999

.94

69,4

32.0

520

,567

.89

89,9

99.9

469

,432

.05

Oracle Project Analysis Collection Pack Implementation GuideB – 4

Pro

ject

Vie

w b

y A

ctiv

ity

(Ser

vice

Typ

e)

Thi

s re

port

pro

vid

es th

e to

tal c

umul

ativ

e ac

tual

raw

cos

t am

ount

s, b

udge

ted

raw

cos

tam

ount

s, a

nd v

aria

nces

for

proj

ects

of V

isio

n Se

rvic

es (U

.S. o

pera

tion

s).

Thi

s re

port

dis

play

s in

form

atio

n fo

r tr

aini

ng a

ctiv

itie

s ba

sed

on

the

appr

oved

cos

t bud

get.

Vis

ion

Ser

vice

s (U

SA

)

Trai

ning

Act

ual R

aw C

ost

Bud

gete

d R

aw C

ost

Bud

gete

d C

ost

– A

ctua

l Cos

t

All

Pro

ject

Typ

es12

5,87

3.00

240,

677.

0011

4,80

4.00

C

ost P

lus

125,

873.

0024

0,67

7.00

114,

804.

00

Pro

ject

Mar

s40

,080

.00

31,0

77.0

0(9

,003

.00)

Pro

ject

Ven

us85

,793

.00

209,

600.

0012

3,80

7.00


Pro

ject

Org

aniz

atio

n V

iew

by

Act

ivit

y (S

ervi

ce T

ype)

Thi

s re

port

pro

vid

es th

e to

tal c

umul

ativ

e ac

tual

raw

cos

t am

ount

s, b

udge

ted

raw

cos

tam

ount

s, a

nd v

aria

nces

for

proj

ect o

rgan

izat

ions

wit

hin

Vis

ion

Serv

ices

(U.S

. ope

rati

ons)

.T

his

repo

rt d

ispl

ays

info

rmat

ion

for

trai

ning

act

ivit

ies

base

d o

n th

e ap

prov

ed c

ost b

udge

t

Vis

ion

Ser

vice

s (U

SA

)

Trai

ning

Act

ual R

aw C

ost

Bud

gete

d R

aw C

ost

Bud

gete

d C

ost

– A

ctua

l Cos

t

Vis

ion

Cor

pora

tion

125,

873.

0024

0,67

7.00

114,

804.

00

C

onsu

lting

–Eas

t85

,793

.00

209,

600.

00 1

23,8

07.0

0

C

onsu

lting

–Wes

t40

,080

.00

31,

077.

00(9

,003

.00)


Top

3 P

roje

cts

wit

h B

est B

ud

gete

d C

ost t

o A

ctu

al C

ost V

aria

nce

s

Thi

s re

port

iden

tifi

es th

e th

ree

best

per

form

ing

proj

ects

ow

ned

by

Vis

ion

Serv

ices

(U.S

.op

erat

ions

) in

term

s of

the

tota

l cum

ulat

ive

vari

ance

bet

wee

n bu

dge

ted

raw

cos

ts a

nd a

ctua

lra

w c

osts

bas

ed o

n th

e ap

prov

ed c

ost b

udge

t.

Vis

ion

Ser

vice

s (U

SA

)

All

Fin

anci

al Y

ears

Bud

gete

d C

ost –

Act

ual C

ost

Pro

ject

Ven

us12

3,80

7.00

Pro

ject

Atla

nta

81,5

57.6

0

Pro

ject

San

Fra

ncis

co69

,432

.05


Bot

tom

2 P

roje

cts

wit

h L

owes

t Rev

enu

e

Thi

s re

port

iden

tifi

es th

e tw

o w

orst

per

form

ing

proj

ects

ow

ned

by

Vis

ion

Serv

ices

(U.S

.op

erat

ions

) in

term

s of

tota

l cum

ulat

ive

reve

nue.

Vis

ion

Ser

vice

s (U

SA

)

All

Fin

anci

al Y

ears

Rev

enue

Pro

ject

Sea

ttle

22,5

93.0

3

Pro

ject

Los

Ang

eles

16,8

40.1

5


Top

2 P

roje

cts

wit

h H

igh

est R

even

ue

Thi

s re

port

iden

tifi

es th

e tw

o be

st p

erfo

rmin

g pr

ojec

ts o

wne

d b

y V

isio

n Se

rvic

es (U

.S.

oper

atio

ns) i

n te

rms

of to

tal c

umul

ativ

e re

venu

e.

Vis

ion

Ser

vice

s (U

SA

)

All

Fin

anci

al Y

ears

Rev

enue

Pro

ject

Ven

us10

4,44

2.80

Pro

ject

Mar

s76

,082

.75


Mar

gin

Vie

w

Thi

s re

port

pro

vid

es th

e ac

tual

raw

cos

t am

ount

s ve

rsus

rev

enue

am

ount

s fo

r pr

ojec

t typ

esow

ned

by

Vis

ion

Serv

ices

(U.S

. ope

rati

ons)

. T

his

repo

rt d

ispl

ays

info

rmat

ion

for

all

fina

ncia

l yea

rs to

dat

e an

d fo

r 19

97.

Vis

ion

Ser

vice

s (U

SA

)

All

Fin

anci

al Y

ears

1997

Act

ual

Raw

Cos

tR

even

ueR

even

ue v

s.C

ost

Act

ual

Raw

Cos

tR

even

ueR

even

ue v

s.C

ost

All

Pro

ject

Typ

es57

7,73

3.23

180,

525.

55(3

97,2

07.6

8)54

7,96

9.69

180,

525.

55(3

67,4

44.1

4)

C

onst

ruct

ion

208,

049.

940.

00(2

08,0

49.9

4)18

4,68

6.40

0.00

(184

,686

.40)

Pro

ject

Chi

cago

208,

049.

940.

00(2

08,0

49.9

4)18

4,68

6.40

0.00

(184

,686

.40)

C

ost P

lus

125,

873.

0018

0,52

5.55

54,6

52.5

512

5,87

3.00

180,

525.

5554

,652

.55

Pro

ject

Mar

s40

,080

.00

76,0

82.7

536

,002

.75

40,0

80.0

076

,082

.75

36,0

02.7

5

Pro

ject

Ven

us85

,793

.00

104,

442.

8018

,649

.80

85,7

93.0

010

4,44

2.80

18,6

49.8

0

O

verh

ead

12,2

00.0

00.

00(1

2,20

0.00

)5,

800.

000.

00(5

,800

.00)

Pro

ject

New

Yor

k12

,200

.00

0.00

(12,

200.

00)

5,80

0.00

0.00

(5,8

00.0

0)

R

& D

211,

042.

400.

00(2

11,0

42.4

0)21

1,04

2.40

0.00

(211

,042

.40)

Pro

ject

Atla

nta

211,

042.

400.

00(2

11,0

42.4

0)21

1,04

2.40

0.00

(211

,042

.40)

S

ervi

ce C

ente

r20

,567

.89

0.00

(20,

567.

89)

20,5

67.8

90.

00(2

0,56

7.89

)

Pro

ject

San

Fra

ncis

co20

,567

.89

0.00

(20,

567.

89)

20,5

67.8

90.

00(2

0,56

7.89

)

Glossary – 1

Glossary

activity type See service type.

ad hoc Concerned with or formed for aparticular purpose. For example, ad hoctax codes or an ad hoc database query.

baseline budget The authorized budget for aproject or task which is used forperformance reporting and revenuecalculation.

business group The highest level oforganization and the largest grouping ofemployees across which a company canreport. A business group can correspond toan entire company, or to a specific divisionwithin the company. Each installation ofOracle Projects uses one business groupwith one hierarchy.

class category An implementation–definedcategory for classifying projects. Forexample, if you want to know the marketsector to which a project belongs, you candefine a class category with a name such asMarket Sector. Each class category has a setof values (class codes) that can be chosenfor a project. See class code.

class code An implementation–defined valuewithin a class category that can be used toclassify a project. See class category.

collection Method to gather data from sourcesystem.

collection definition Used to generate thecollection program for each source, definesobjects and attributes to collect, events tocause collection, and filters on objectscollected.

collection mapping Defines the relationshipfrom source tables and columns to interfacetables and columns.

collection package Populates OADWinterface cubes from source data.Collection packages may be generated byOADW through maps defined in theOADW Repository metadata, or may behard–coded programs that you develop.

cube Logical unit of storage in the DataWarehouse, manifested as tables in thedatabase, has measures, keys, and foreignkeys. Cube properties are dimensions,measures, and attributes. Dimensions arethe equivalents of keys to a table, andmeasures and attributes are the equivalentsof columns to a table.

cube mapping Used to specify how a logicalcube is physically stored in tables.

data warehouse A copy of transaction dataspecifically structured for query andanalysis. A data warehouse collects datafrom core operational applications,summarizes, compiles, or translates the

Glossary – 2 Oracle Project Analysis Collection Pack Implementation Guide

collected data, and makes the data availablefrom a central store.

denormalize Allows redundancy in a table sothat the table can remain flat.

derived measures Measures collected fromthe sources are used to derive othermeasures. An example is discount, whichis derived from the difference between listprice and selling price.

dimension One of the edges of amultidimensional cube, an independententity in the model that serves as an entrypoint or as a mechanism for slicing additivemeasures.

dimension value cube Physically, the set ofvalues for a dimension and the parentageinformation for hierarchies is stored in thedimension value cube.

drilldown A software feature that allows youto view the details of an item in the currentwindow via a window in a differentapplication.

expenditure category Animplementation–defined grouping ofexpenditure types by type of cost. Forexample, an expenditure category with aname such as Labor refers to the cost oflabor.

expenditure organization For timecards andexpense reports, the organization to whichthe incurring employee is assigned, unlessoverridden by organization overrides. Forusage, supplier invoices, and purchasingcommitments, the incurring organizationentered on the expenditure.

expenditure type An implementation–definedclassification of cost that you assign to eachexpenditure item. Expenditure types aregrouped into cost groups (expenditurecategories) and revenue groups (revenuecategories).

filter Conditions and parameters used toselectively collect data from the source.OADW will pre–define some filters for eachOracle application.

foreign key A field in a relational databasetable whose values are drawn from thevalues of a primary key in another table.

GL Date The end date of the GL Period inwhich costs or revenue are transferred toOracle General Ledger. This date isdetermined from the open or future GLPeriod on or after the PA Date of a costdistribution line or revenue. For invoices,the GL Date is the date within the GLPeriod on which an invoice is transferred toOracle Receivables, and is based on theinvoice date.

hierarchy Rules to navigate or roll up databetween levels of a dimension, represents alogical view into the data.

installed module An application whichidentifies the location information, databaseschema, and database link. An installedmodule is a source application, aDesigner/2000 repository, the OADWRepository, or the OADW Warehouse. Allinstalled modules reside in a particulardatabase system. Installed modules shouldbe accessible by both the OADW

Glossary – 3

Repository and OADW Warehouse througha database link.

interface table Point of entry of all sourcedata into OADW. Interface tables can be fedfrom multiple sources including OracleApplications, legacy data, and user–defineddata. Interface tables feed OADW datacubes, and may be purged after data hasbeen moved.

legal entity An organization that represents alegal company for which you prepare fiscalor tax reports. You assign tax identifiersand other relevant information to thisentity.

measure Equivalent to all non–key elementsof a cube.

measure type Named measures defined bydata type, length, and decimal places.

metadata Data about data, maintained tosupport the operations or use of the datawarehouse. Types of metadata are sourcesystem metadata, collection metadata,analysis metadata, security metadata, andreporting metadata.

normalize The process of removingredundancy in data by separating the datainto multiple tables.

OADW repository Stores the metadata,logical warehouse design, level cubes, anddimension value cubes.

OADW warehouse Stores data cubes anddimension value cubes.

OLAP On line analytical processing. OLAP isa loosely defined set of principles that

provide a dimensional framework fordecision support.

OLTP On line transaction processing. Theoriginal description for all the activities andsystems associated with entering datareliably into a database.

operating unit An organization that partitionsdata for subledger products (AP, AR, PA,PO, OE). It is roughly equivalent to a singlepre–Multi–Org installation.

organization Internal organizations aredivisions, groups, cost centers or otherorganizational units in a company. Externalorganizations can include the contractorsyour company employs. Organizations canbe used to demonstrate ownership ormanagement of functions such as projectsand tasks, non–labor resources, and bill rateschedules.

organization hierarchy An organizationalhierarchy illustrates the relationshipsbetween your organizations. A hierarchydetermines which organizations aresubordinate to other organizations. Thetopmost organization of an organizationhierarchy is generally the business group.

organization structure See organizationhierarchy.


PA Date The end date of the PA Period inwhich costs are distributed, revenue iscreated, or an invoice is generated. Thisdate is determined from the open or futurePA Period on or after the latest date ofexpenditure item dates and eventcompletion dates included in a costdistribution line, revenue, or an invoice.

PA Period See Project Accounting Period.

PA Period Type The Period Type as specifiedin the PA implementation options forOracle Projects to copy project accountingperiods. Oracle Projects uses the periods inthe PA Period Type to populate eachOperating Unit’s PA periods. PA periodsare mapped to GL periods which are usedwhen generating accounting transactions.PA periods drive the project summary forProject Status Inquiry. You define youraccounting periods in the Operating Unit’sSet of Books Calendar.

primary key A field in the table that is uniquefor each record in the table.

process responsibility type Animplementation–defined name to which agroup of reports and processes areassigned. This group of reports andprocesses is then assigned to an OracleProjects responsibility. A processresponsibility type gives a user access toOracle Projects reports and programsappropriate to that user’s job. For example,the process responsibility type Data Entrycould be a set of reports used by data entryclerks. See responsibility.

project A unit of work that can be brokendown into one or more tasks. A project isthe unit of work for which you specifyrevenue and billing methods, invoiceformats, a managing organization andproject manager, and bill rate schedules.You can charge costs to a project, and youcan generate and maintain revenue, invoice,unbilled receivable, and unearned revenueinformation for a project.

Project Accounting Period Animplementation–defined period againstwhich project performance may bemeasured. Also referred to as PA Periods.You define project accounting periods totrack project accounting data on a periodicbasis by assigning a start date, end date,and closing status to each period. Typically,you define project accounting periods on aweekly basis, and your general ledgerperiods on a monthly basis.

project operating unit The operating unitwithin which the project is created.

project/task organization The Organizationthat owns the project or task. This can beany organization in the LOV (list of values)for the project setup. The Project/TaskOrganization LOV contains organizationsof the Project/Task Organization Type inthe Organization Hierarchy and Versionbelow the Start Organization. You specifyyour Start Organization and Version in theImplementation Options window.

Glossary – 5

project type An implementation–definedtemplate that consists of essential projectattributes such as whether a project is director indirect, a project’s default revenuedistribution rule and bill rate schedules,and whether a project burdens costs. Forexample, you can define a project type witha name such as Time and Materials for allprojects that are based on time andmaterials contracts.

Project/Task Organization The Organizationthat owns the project or task.

report An organized display of OracleApplications information. A report can beviewed online or sent to a printer. Thecontent of information in a report can rangefrom a summary to a complete listing ofvalues.

reporting metadata Data relating to reporting,such as report definitions.

resource A user–defined group of employees,organizations, jobs, suppliers, expenditurecategories, revenue categories, expendituretypes, or event types for purposes ofdefining budgets or summarizing actuals.

responsibility A level of authority in anapplication. Each responsibility lets youaccess a specific set of Oracle Applicationswindows, menus, reports, and data to fulfillyour role in an organization. Several userscan share the same responsibility, and asingle user can have multipleresponsibilities.

responsibility type See process responsibilitytype.

revenue In Oracle Projects, the amountsrecognized as income or expected billing tobe received for work on a project.

rollup cube Computes rollups beyond thefirst level across all hierarchies of alldimensions of the cube.

rollup transform Specifies how rollups arecomputed to summarize the source datainto a parent hierarchy level, can beintra–cube or inter–cube.

row One occurrence of the informationdisplayed in the fields of a block. A blockmay show only one row of information at atime, or it may display several rows ofinformation at once, depending on itslayout. The term “row” is synonymouswith the term “record”.

service type An implementation–definedclassification of the type of work performedon a task.

set of books A financial reporting entity thatuses a particular chart of accounts,functional currency and accountingcalendar. You must define at least one setof books for each business location.

short name A unique identifier that is used asthe root name for all related objects createdin OADW. For example, the dimensionshort name CUST is the root name forrelated objects such as cubes and interfacetables and must be unique. Short names arenot translated, cannot include blank spaces,can contain only alphanumeric characters(a–z and 0–9), the dollar sign ($), the poundsign (#), and the underscore character (_),and are limited to a maximum of 17–22characters depending on the object type.

simple mapping Mapping one cube to onetable, cube keys and measures are mappedto table columns.

slice and dice The standard description of theability to access a data warehouse throughany of its dimensions equally.

star schema A specific organization of adatabase in which a central fact table hasmultiple joins connecting it to otherdimension tables, each with a single join


connected to the central fact table. Alsocalled a ”star join schema”.

subtask A hierarchical unit of work. Subtasksare any tasks that you create under a parenttask. Child subtasks constitute the lowestlevel of your work breakdown structure;where Oracle Projects looks whenprocessing task charges and fordetermining task revenue accrual amounts.See task.

summarization Processing a project’s cost,revenue, commitment, and budgetinformation to be displayed in the Project,Task, and Resource Project Status windows.You must distribute costs for anyexpenditure items, accrue and release anyrevenue, create any commitments, andbaseline a budget for your project beforeyou can view summary project amounts.Formerly known as accumulation.

task A subdivision of project work. Eachproject can have a set of top level tasks anda hierarchy of subtasks below each top leveltask. See also work breakdown structure,subtask.

task organization The organization that isassigned to manage the work on a task.

task service type See service type.

unit of measure A unit of measure recordsquantities or amounts of an expenditureitem. For example, if you specify the unitMiles when you define an expenditure typefor personal car use, Oracle Projectscalculates the cost of using a personal carby mileage.

window A box around a set of relatedinformation on your screen. Manywindows can appear on your screensimultaneously and can overlap or appearadjacent to each other. Windows can alsoappear embedded in other windows. Youcan move a window to a different locationon your screen.

work breakdown structure (WBS) Thebreakdown of project work into tasks.These tasks can be broken down furtherinto subtasks, or hierarchical units of work.

Index – 1

Index

AADW_NOTIFY_FLAG parameter, 3 – 11

Ccollection views, 3 – 9

dimension tables, 3 – 9fact tables, 3 – 10

creating dimensions, 5 – 4creating fact tables, 5 – 6creating measures, 5 – 5creating new hierarchies or hierarchy levels,

5 – 5

Ddatabase triggers, 3 – 11dimension interface tables, 3 – 7dimension table collection views, 3 – 9dimensions

creating, 5 – 4standard, 3 – 3

Dimensions window, 5 – 3disabling standard dimensions, 5 – 3disabling standard hierarchies or hierarchy

levels, 5 – 4disabling standard measures, 5 – 4

EExpress/RAM (Relation Access Manager),

7 – 3

Ffact interface tables, 3 – 8fact table collection views, 3 – 10fact tables, creating, 5 – 6

Hhierarchies


hierarchy levelscreating, 5 – 5standard, 3 – 4

Iinterface tables, 3 – 6

definition, 3 – 6dimension tables, 3 – 6fact tables, 3 – 6

Mmeasures


OOracle Applications Data Warehouse, uses,

1 – 5

Index – 2 Oracle Project Analysis Collection Pack Implementation Guide

Oracle Express Analyzer, 7 – 3Oracle Project Analysis Collection Pack,

overview, 1 – 2Oracle Projects profile options, 2 – 2Oracle Sales Analyzer, 7 – 3

Pparameters, ADW_NOTIFY_FLAG, 3 – 11profile options

PA: ADW Collect Top Tasks, 2 – 3PA: ADW Installed, 2 – 2PA: Collection Pack Licensed, 2 – 3

Rreports

Bottom 2 Projects with Lowest Revenue, B– 7

Margin View, B– 9Project Organization View, B– 3Project Organization View by Activity

(Service Type), B– 5Project View by Activity (Service Type), B– 4Top 2 Projects with Highest Revenue, B– 8Top 3 Projects with Best Budgeted Cost to

Actual Cost Variances, B– 6

Sstandard dimensions, disabling, 5 – 3standard hierarchies, disabling, 5 – 4standard hierarchy levels, disabling, 5 – 4standard measures, disabling, 5 – 4standard metadata

dimensions, 3 – 3hierarchies, 3 – 4hierarchy levels, 3 – 4measures, 3 – 5

Reader’s Comment Form

Oracle Project Analysis Collection Pack Implementation Guide Release 11A59356–01

Oracle Corporation welcomes your comments and suggestions on the quality and usefulnessof this publication. Your input is an important part of the information we use for revision.

• Did you find any errors?

• Is the information clearly presented?

• Do you need more information? If so, where?

• Are the examples correct? Do you need more examples?

• What features did you like most about this manual? What did you like least about it?

If you find any errors or have any other suggestions for improvement, please indicate the topic, chapter,and page number below:

Please send your comments to:

Oracle Applications Documentation ManagerOracle Corporation500 Oracle ParkwayRedwood Shores, CA 94065 USAPhone: (650) 506–7000 Fax: (650) 506–7200

If you would like a reply, please give your name, address, and telephone number below:

Thank you for helping us improve our documentation.

oracle project analysis collection pack implementation guide · iv oracle project analysis...

Documents