BusinessObjects Projects Rapid Mart for Oracle ...s3.amazonaws.com/zanran_storage/help.sap.com/ContentPages/...Contents 4 BusinessObjects Projects Rapid Mart for Oracle Applications

BusinessObjects Projects Rapid Mart for Oracle Applications User’s Guide

Version 11.5.2.0

Patents Business Objects owns the following U.S. patents, which may cover products that are offered and sold by Business Objects: 5,555,403, 6,247,008 B1, 6,578,027 B2, 6,490,593 and 6,289,352.

Trademarks Business Objects, the Business Objects logo, Crystal Reports, and Crystal Enterprise are trademarks or registered trademarks of Business Objects SA or its affiliated companies in the United States and other countries. All other names mentioned herein may be trademarks of their respective owners.

Copyright Copyright © 2006 Business Objects. All rights reserved.

ContentsChapter 1 Introduction 11

What is a Rapid Mart? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Rapid Marts Accelerate Time to Value . . . . . . . . . . . . . . . . . . . . . . . . 12BusinessObjects Rapid Mart architecture . . . . . . . . . . . . . . . . . . . . . . 13

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Overview 15What you can do with this Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Related Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Sharing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Rapid Mart schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Chapter 3 Subject Areas 23Budget Line Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Fact table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Draft Revenue Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Fact table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

BusinessObjects Projects Rapid Mart for Oracle Applications User’s Guide 3

Contents

Draft Invoice Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Fact table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Expenditure Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46


Event Distribution Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64


Project Asset Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70


Budget Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Project Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

4 BusinessObjects Projects Rapid Mart for Oracle Applications User’s Guide

Contents

Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Fact table columns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Project Transaction Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Oracle Applications processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87


Chapter 4 Reports 93Budget Line Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Budget Line Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Budget Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Budget Summary Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Expenditure Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Expenditure Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Expenditure Cost Trend Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 107Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Expenditure Revenue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Expenditure Revenue Trend Analysis . . . . . . . . . . . . . . . . . . . . . 115Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

Event Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Event Distribution Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Project Asset Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Project Asset Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Project Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Sample reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Project Summary Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137


Contents

Project Summary Cumulative Trend . . . . . . . . . . . . . . . . . . . . . . 140Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

Project Transaction Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Sample reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Project Txn Summary Trend . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Project Txn Summary Top 10 Analysis . . . . . . . . . . . . . . . . . . . . 147

Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Hierarchy Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

Account Hierarchy Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . 155Cost Center Hierarchy Data Discovery . . . . . . . . . . . . . . . . . . . . 157Company Hierarchy Data Discovery . . . . . . . . . . . . . . . . . . . . . . 159Project Hierarchy Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . 161Product Hierarchy Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . 163

Account Segment Dimensions - Recommended Joins . . . . . . . . . . . . . . . 165

Chapter 5 Universe 169Universe Design Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Universe Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Universe Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Join Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

Common Dimensions Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Currency Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Budget Line Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Budget Line Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Budget Line Details Class and Objects . . . . . . . . . . . . . . . . . . . . . . . . 186Budget Line Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Budget Line Star Schema Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Budget Summary Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Budget Summary Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Budget Summary Details Class and Objects . . . . . . . . . . . . . . . . . . . 189Budget Summary Star Schema Layout . . . . . . . . . . . . . . . . . . . . . . . . 190

Project Summary Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191


Contents

Project Summary Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Project Summary Details Class and Objects . . . . . . . . . . . . . . . . . . . 192Project Summary Star Schema Layout . . . . . . . . . . . . . . . . . . . . . . . . 193

Project Transaction Summary Subject Area . . . . . . . . . . . . . . . . . . . . . . . 194Project Transaction Summary Measures . . . . . . . . . . . . . . . . . . . . . . 194Project Transaction Summary Details Class and Objects . . . . . . . . . . 195Project Transaction Summary Star Schema Layout . . . . . . . . . . . . . . 196

Project Asset Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Project Asset Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Project Asset Details Class and Objects . . . . . . . . . . . . . . . . . . . . . . . 198Project Asset Star Schema Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

Event Distribution Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Event Distribution Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Event Distribution Details Class and Objects . . . . . . . . . . . . . . . . . . . 201Event Distribution Star Schema Layout . . . . . . . . . . . . . . . . . . . . . . . 202

Expenditure Cost Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Expenditure Cost Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Expenditure Cost Details Class and Objects . . . . . . . . . . . . . . . . . . . 204Expenditure Cost Star Schema Layout . . . . . . . . . . . . . . . . . . . . . . . . 205

Expenditure Revenue Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Expenditure Revenue Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Expenditure Revenue Details Class and Objects . . . . . . . . . . . . . . . . 207Expenditure Revenue Star Schema Layout . . . . . . . . . . . . . . . . . . . . 208

Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Hierarchies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Time Dimension and Period Hierarchies . . . . . . . . . . . . . . . . . . . . . . . 210Task Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Vendor Geography Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Organization Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Accounting Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Horizontal Hierarchy Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Vertical Hierarchy Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Accounting Flexfield Hierarchy Filters . . . . . . . . . . . . . . . . . . . . . 215


Contents

Report Generation - Vertical Hierarchy . . . . . . . . . . . . . . . . . . . . 216Customizing the Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

Splitting the Universe: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Additional Common Dimensions: . . . . . . . . . . . . . . . . . . . . . . . . . 217Linking the Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Modify Derived Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Divergences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219Objects and Conditions Parsing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Chapter 6 Installing the Rapid Mart 221System prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Rapid Mart product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Preparing your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Installation overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Installation procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Completing the installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Adjusting Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Installing Rapid Mart Reporting Content . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Chapter 7 Using the Rapid Mart 233Recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

Data Integrator automatic recovery feature . . . . . . . . . . . . . . . . . . . . . 234Rapid Mart recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Execution status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236The execution status table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

How job status is maintained . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236The execution status API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Executing a job with the reset option . . . . . . . . . . . . . . . . . . . . . . . . . 238

Extraction, transformation and loading process . . . . . . . . . . . . . . . . . . . . 238Batch configuration variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Local Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245


Contents

Global variables for Accounting Flexfield-related Dimensions . . . 245Executing the jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Customizing the Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Chapter 8 Technical Implementation 251Budget Line Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Draft Revenue Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Draft Invoice Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 268

Expenditure Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Relevant Sections Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Expenditure Fact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Expenditure Cost Fact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275Expenditure Rev Fact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Event Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Relevant Sections Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Project Asset Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Budget Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

Project Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288


Contents

Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Project Transaction Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Flexfields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Accounting Flexfield . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Dealing with NULL values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Fact table stored procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297Compatibility with Oracle Applications R12 . . . . . . . . . . . . . . . . . . . . . . . . 298

Appendix A Rapid Mart and Oracle Applications Accounting Flexfield 301Oracle Applications Reporting Challenges . . . . . . . . . . . . . . . . . . . . . . . . 302Data Integrator Interface for Oracle Applications . . . . . . . . . . . . . . . . . . . 303Data Integrator Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304Rapid Mart Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Implementing Accounting Flexfield with Rapid Marts . . . . . . . . . . . . . . . . 310

Before Rapid Mart Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311Flexfield User-Defined Names Discovery . . . . . . . . . . . . . . . . . . . 312Customization Reference Table . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Rapid Mart Customization - Data Model Changes . . . . . . . . . . . . . . . 314Rapid Mart Customization - Data Integrator Job Changes . . . . . . . . . 317

Creating Copies of Original Job Objects . . . . . . . . . . . . . . . . . . . 317Modifying WF_AccountingFlexField_OA Workflow . . . . . . . . . . . 318Completing Data Integrator Job Customization . . . . . . . . . . . . . . 338

Customizing Rapid Mart Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339Customizing Rapid Mart Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Appendix B Rapid Mart Data Schema 343


Introduction

chapter

IntroductionWhat is a Rapid Mart?1
What is a Rapid Mart?
BusinessObjects™ Rapid Marts provide packaged extraction of operational data to accelerate the deployment of business intelligence (BI). They are add-on products to BusinessObjects™ Data Integrator that combine domain knowledge with data integration best practices to deliver pre-built data models, transformation logic, and data flows for extracting data from enterprise applications from SAP, PeopleSoft, Oracle, J. D. Edwards, Siebel and Salesforce.com.Rapid Marts deliver pre-packaged business content and data flows in a single data platform optimized for BI and analytic applications. Rapid Marts enable business users to report on and gain insight into their enterprise information. Most include prebuilt Business Objects reports and universes that deliver domain knowledge on operational systems.BI tools and analytic tools can access Rapid Mart data directly through SQL queries or indirectly through a Data Integrator RealTime request-response system. Rapid Marts can be implemented individually, or in any combination, to form a single platform that delivers the infrastructure for your company’s internal and external information needs. They can also serve as a staging area for enterprise analytic applications.Rapid Marts provide IT with an accelerated time to value through rapid BI deployments because you can implement them quickly and easily customize them to meet specific analytic requirement.

Rapid Marts Accelerate Time to ValueRapid Marts are packaged data solutions that you can quickly deploy to address specific areas of business analysis. Available Rapid Marts include:• BusinessObjects Sales Rapid Mart• BusinessObjects Cost Center Rapid Mart• BusinessObjects Profitability Rapid Mart• BusinessObjects General Ledger Rapid Mart• BusinessObjects Accounts Receivable Rapid Mart• BusinessObjects Accounts Payable Rapid Mart• BusinessObjects Federal Financials Rapid Mart• BusinessObjects Fixed Assets Rapid Mart• BusinessObjects Purchasing Rapid Mart• BusinessObjects Inventory Rapid Mart


IntroductionAbout this document 1

• BusinessObjects Plant Maintenance Rapid Mart• BusinessObjects HR Rapid Mart• BusinessObjects Production Planning Rapid Mart• BusinessObjects Project Systems Rapid Mart• BusinessObjects Pipeline Rapid Mart• BusinessObjects Call Center Rapid Mart• BusinessObjects Campaign Rapid MartYou can combine multiple Rapid Marts into a single environment to build the foundation for your data warehouse or use them as a staging area for BusinessObjects Analytic Applications.

BusinessObjects Rapid Mart architectureRapid Marts provide a powerful jumpstart for building source-specific data marts for operational reporting and packaged data integration for enterprise analytic applications. The following diagram shows where Rapid Marts fit in the deployemt of business intelligence process:

About this documentThis document describes the BusinessObjects Projects Rapid Mart for Oracle Applications. This document contains information for a variety of users—information that helps you understand the use of the Rapid Mart, the data in the Rapid Mart, the queries you can answer with the Rapid Mart, and how to run, update, and maintain the Rapid Mart.


IntroductionAbout this document1

This document contains the following chapters:• Chapter 2: Overview — Describes the business problems you can solve

and the types of analyses you can do with this Rapid Mart• Chapter 3: Subject Areas — Contains detailed information about each

section that is part of the batch extraction in theRapid Mart, including the processes each section captures

• Chapter 4: Reports — Provides examples of reports you can produce• Chapter 5: Universe — Describes Business Objects Universe upon which

the reports are based• Chapter 6: Installing the Rapid Mart — Contains the information you need

to install the Rapid Mart• Chapter 7: Using the Rapid Mart —Describes how to execute the Rapid

Mart, including information about initializing variables and what you need to consider when customizing the Rapid Mart

• Chapter 8: Technical Implementation —Describes each section and the work flows that run to load that section

• Appendix A: Rapid Mart and Oracle Applications Accounting Flexfield — Contains a detailed list of the tables and views in the Rapid Mart

• Appendix B: Rapid Mart Data Schema — Contains a detailed list of the tables and views in the Rapid Mart


Overview

chapter

OverviewOverview2
Overview
This chapter describes the business problems you can solve with the BusinessObjects Projects Rapid Mart for Oracle Applications, and the types of analyses you can do with this Rapid Mart. The information in this chapter is useful for those who want a business-level overview of the Rapid Mart and its benefits. This chapter contains the following sections:• What you can do with this Rapid Mart• Supported analyses• Related Rapid Marts• Rapid Mart schema

What you can do with this Rapid MartThe BusinessObjects Projects Rapid Mart for Oracle Applications supports analysis of data in the Projects module of Oracle Applications.Oracle Projects suite provides a complete enterprise project management solution including separate submodules for Project Management, Costing, Billing, and Resource Management.The BusinessObjects Projects Rapid Mart for Oracle Applications provides a framework to support operational and statistical analysis of project-related information. It helps companies manage their projects and the resources, schedules, deliverables and finances associated with them, and gives the ability to quickly show how projects are performing across the enterprise. Potential problems can be readily identified and action taken to ensure the projects are on schedule, adequately resourced, and within budget.The BusinessObjects Projects Rapid Mart for Oracle Applications is made up of several componentized sections. Each section supports a subject related to analysis of project management:• Budget Line Section - stores estimated cost, revenue, labor hours and

other quantities for a project and task categorized by a resource. • Draft Revenue Section - holds draft project revenue transactions prior to

being transferred to other modules in Oracle applications.• Draft Invoice Section - holds potential project invoices that require

approval before they are officially accounted for in other Oracle applications.


OverviewSupported analyses 2

• Expenditure Section - contains details of expenditure items (costs and revenues) incurred by an employee or organization.

• Event Section - contains summary level transactions generating revenue and/or billing activity that are not directly related to any expenditure items.

• Project Asset Section - includes capital and retirement adjustment assets for capital projects.

• Budget Summary Section - holds summarized inception-to-date, year-to-date, period-to-date and prior period budget data.

• Project Summary Section - stores summarized inception-to-date, year-to-date, period-to-date and prior period project data.

• Project Transaction Summary Section - contains summarized project data at the lowest level of detail.

Chapter 3: Subject Areas discusses these sections and the data extracted in more detail.

Supported analyses The BusinessObjects Projects Rapid Mart for Oracle Applications supports several types of analyses, including:-

Business function Types of analysis Measures available in the Rapid Mart

Project costs Variance analysis • Breakdown of raw and burden costs by all elements of a project.

Trend analysis • Inception-to-date, Year-to-date, Period-to-date and prior period cost totals by all elements of a project

Detailed costs analysis • Costs attributed to expenditure items and events

• Cost trending over time• Analyze cost against GL accounts

Project Revenue Progress analysis • Inception-to-date, Year-to-date, Period-to-date and prior period revenue totals including billable quantities and labor hours by all elements of a project


OverviewSupported analyses2

Detailed revenue analysis

• Revenue attributed to expenditure items and events

• Revenue trending over time• Analyze revenue against

Accounting flexfield segmentsProject Profitability Actual Profitability • Actual margin for selected periods

and comparison against budget and previous periods by all elements of a project

Forecast Profitability • Forecast margin for selected periods and comparison against budget and previous periods

Profitability Trend • Revenue trend and margin growth over time

Detailed profitability analysis

• Breakdown to show most profitable elements of a project

Billing review Draft invoice review • Review of unearned revenue and unbilled receivables prior to approving and releasing to Oracle Receivables

Expenditure Reports Detailed view of cost, revenue, and invoice activities

• Quantities, raw and burden costs, revenue, billable amounts by all elements of a project

Trend analysis • Expenditure trend and margin over time

Audit and Control • Reviewing distribution by Accounting flexfield segments before posting to GL. Analysis of unposted transactions.

Event Analysis Audit and Control • Analyze event distributions by Accounting flexfield segments

Asset Listing Show capital project amounts

• Original and current asset costs, capitalized costs by project, category, and location

Business function Types of analysis Measures available in the Rapid Mart


OverviewRelated Rapid Marts 2

Related Rapid MartsEach Rapid Mart is composed of multiple components. A component is a stand-alone workflow that completes a particular task, such as loading a specific dimension table. Components can contain other components. A section is a set of components that address a particular business problem or subject area. A section is itself a component.The BusinessObjects Projects Rapid Mart for Oracle Applications shares a few components as well as some transactional data with other Rapid Marts including General Ledger, Accounts Payable, and Accounts Receivable:• Several dimensions are used by multiple Rapid Marts. For instance,

organization and project components are part of Accounts Payable Rapid Mart.

• Invoices related to projects are included in the Accounts Receivable Rapid Mart.

• Invoices arising from project expense reports are stored in the Accounts Payable Rapid Mart.

• Accounting entries for Project Transactions are included in the General Ledger Rapid Mart.

Sharing components The same components can be used in multiple Rapid Marts. For example, a component that extracts information about materials bought, produced, and sold is needed for a Rapid Mart that supports sales analysis and also for a Rapid Mart that supports inventory analysis. Work flows that extract star schema “dimensions” are components. You can add a component to any Rapid Mart using a simple import procedure. A Data Integrator job can include multiple instances of a component. For example, each section includes all the required dimension components. Therefore, a job with several sections may include several instances of a particular dimension component. Components are set to execute only once within a job. This “execute once” feature ensures that shared components do not cause duplicate data extraction from Oracle Applications. For more information about the “execute once” feature, see the Data Integrator Designer Guide.


OverviewRelated Rapid Marts2

Each of the sections listed in “What you can do with this Rapid Mart” on page 16 is considered a component. You can identify a component within a Data Integrator job by a “C_” prefix before its name. For example, the component that contains expenditure information and the associated reporting dimensions is named C_Expenditure_Section_OA.


OverviewRapid Mart schema 2

Rapid Mart schemaThe following diagram shows the tables in the BusinessObjects Projects Rapid Mart for Oracle Applications. The larger boxes contain the fact tables corresponding to componentized sections; the smaller boxes indicate dimensional components that may apply to multiple sections.


OverviewRapid Mart schema2


Subject Areas

chapter

Subject AreasOverview3
Overview
Each section in the BusinessObjects Projects Rapid Mart for Oracle Applications pertains to a particular subject area. This chapter describes each section and the processes each section captures. The information in this chapter is useful for readers who use the Rapid Mart and need to understand the data in the Rapid Mart and how it relates to Oracle Applications.This chapter discusses: • Budget Line Section• Draft Revenue Section• Draft Invoice Section• Expenditure Section• Event Distribution Section• Project Asset Section• Budget Summary Section• Project Summary Section• Project Transaction Summary Section

Budget Line SectionThe Budget Line section of this Rapid Mart stores estimated cost, revenue, labor hours and other quantities for a project and task categorized by a resource.

Oracle Applications processingIn Oracle Applications a budget is defined as the estimated cost, revenue and labor hours or other quantities for a project or task. Different budgets may be set up to classify budgets for different purposes identified by a budge type.Budget types can include:• Approved Cost Budget• Forecast Cost Budget• Approved Revenue Budget• Forecast Revenue Budget• Capital Cost Budget


Subject AreasBudget Line Section 3

In all cases, Oracle Applications stores historical versions of the budgets as well as the current version. The current version is identified by the CURRENT_FLAG field.This further allows detailed analysis of changes in budgets between versions but also means that the budget version must be constrained to avoid duplicate counting.Oracle Applications holds details of the budget versions in the table, PA_BUDGET_VERSIONS and details of the lines comprising the budget in the table, PA_BUDGET_LINES.Additionally, the resource assignments for work in the budgeted project are stored in table, PA_RESOURCE_ASSIGNMENTS with the actual resources held in table, PA_RESOURCE_LIST_MEMBERS.

Rapid Mart processingThe Rapid Mart selects all budget data from the source tables specified above and loads them into the BUDGET_LINE_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, budget line entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.


Subject AreasBudget Line Section3
Rapid Mart data
The following diagram shows the tables that the Budget Line section extracts.

Fact table columnsThe budget line fact table contains measures and attributes. The columns in the table are described below.• BUDGET_LINE_ID

Unique identifier of budget line - primary key• BUDGET_TYPE_CODE

The type of budget - foreign key to BUDGET_TYPE dimension• BUDGET_STATUS



The status of a budget• VERSION_NAME

The name of the budget version• VERSION_NUMBER

The version number of the budget. For draft budget, the version number is always 1, for baselined budget this number is increased sequentially

• VERSION_DESCRIPTIONThe description of the budget version

• LINE_DESCRIPTIONThe description of the budget line

• ORG_IDHolds the identifier of the Organization - foreign key to ORGANIZATION dimension

• PROJECT_IDThe identifier of the project for which the budget is entered - foreign key to PROJECT dimension - foreign key to PROJECT dimension

• TASK_IDThe identifier of the task that the resource is assigned to. This is set to 0 if the budget is entered at the project level - foreign key to TASK dimension

• RESOURCE_IDThe identifier of the resource that is being used as a member of the resource list - foreign key to PROJECT_RESOURCE dimension

• PERSON_IDHolds the identifier of the employee - foreign key to CURRENT_PEOPLE dimension.

• JOB_IDHolds the identifier of the Job - foreign key to JOB dimension - foreign key to JOB dimension.

• VENDOR_IDHolds the identifier of the Supplier - foreign key to VENDOR dimension.

• EXPENDITURE_TYPE_IDHolds the identifier of the Expenditure Type - foreign key to EXPENDITURE_TYPE dimension

• EVENT_TYPE_IDHolds the identifier of the Event Type - foreign key to EVENT_TYPE dimension



• NON_LABOR_RESOURCEHolds the identifier of the Non Labor Resource.

• EXPENDITURE_CATEGORYHolds the identifier of the Expenditure Category.

• REVENUE_CATEGORYHolds the identifier of the Revenue Category

• NON_LABOR_RESOURCE_ORG_IDHolds the identifier of the Non Labor Resources Organization - foreign key to ORGANIZATION dimension.

• EVENT_TYPE_CLASSIFICATIONHolds the identifier of the Event Type Classification.

• CODE_COMBINATION_IDA foreign key to identify a combination of codes that the organization uses to identify general ledger accounts. Oracle Applications represent these codes using a particular key flexfield called the Accounting Flexfield. One organization might choose to customize the Accounting Flexfield to include five segments: company, division, department, account, and project. Another organization, however, might structure their general ledger account segments differently, perhaps using twelve segments instead of five. The Accounting Flexfield lets the Oracle Payables application accommodate the needs of different organizations by allowing them to customize that key flexfield to their particular business usage. The code combination dimension contains concatenated codes, account type definition (Asset, Expense, Liability, Equity, Revenue) as well as grouping the codes by the eight most common fixed segments: Company, Account, Product, Cost Center, District, Project, Fund and Intercompany.

• BASELINED_BY_PERSON_IDThe identifier of the person who baselined the budget - foreign key to CURRENT_PEOPLE dimension

• BASELINED_DATEThe baselined date of the budget version

• PERIOD_SET_NAME, GL_PERIOD_NAMEPeriod of the budget line - foreign key to PERIOD_CALENDAR dimension

• PERIOD_NAME, ORG_ID



Project period name of the budget line - foreign key to PROJECT_PERIOD dimension

• START_DATEThe start date of the budget line

• END_DATEThe end date of the budget line

• CURRENCY_CODE_PRJThe project currency code - foreign key to CURRENCY dimension

• CHANGE_REASON_CODEThe reason to create the budget line

• CURRENT_FLAGFlag that indicates whether the budget version is the current baselined budget

• REVENUEThe revenue of the budget line

• RAW_COSTThe raw cost of the budget line

• BURDENED_COSTThe burdened cost of the budget line

• QUANTITYThe quantity of the budget line

• BORROWED_REVENUEThe borrowed revenue of budget line

• TP_REVENUE_INThe transfer-price revenue in of budget line

• TP_REVENUE_OUTThe transfer-price revenue out of budget line

• REVENUE_ADJThe revenue adjustment of budget line

• LENT_RESOURCE_COSTThe lent resource cost of budget line

• TP_COST_INThe transfer-price cost in of budget line

• TP_COST_OUT



The transfer-price cost out of budget line• COST_ADJ

The cost adjustment of budget line• UNASSIGNED_TIME_COST

The unassigned time cost of budget line• UTILIZATION_PERCENT

The utilization percent of budget line• UTILIZATION_HOURS

The utilization hours of budget line• UTILIZATION_ADJ

The utilization percent adjustment of budget line• CAPACITY

The capacity of budget line• HEAD_COUNT

The head count of budget line• HEAD_COUNT_ADJ

The head count adjustment of budget line• AGREEMENT_ID

Unique identifier of the agreement that is impacted by the control item• SET_OF_BOOKS_ID

The identifier of the General Ledger set of books used by Oracle Projects. It represents Set Of Books in release 11i and Ledgers in R12 - foreign key to SET_OF_BOOKS dimension

• ORGANIZATION_STRUCTURE_ID,ORG_STRUCTURE_VERSION_ID,START_ORGANIZATION_IDidentifier of the default organization hierarchy used for reporting; Identifier of the default organization hierarchy version used for reporting; Identifier of the highest organization used in default reporting organization hierarchy version - foreign key to ORG_STRUCTURE dimension

• CREATION_DATEBudget line creation date - foreign key to TIME_DIM dimension

• LOAD_DATE and LOAD_TIMEThe Rapid Mart populates these fields with the date and time of the start of the data extraction from Oracle Applications. For Oracle, the Rapid Mart stores the date as a string in the format: 'YYYY.MM.DD HH24:MI:SS'. For other target databases, the Rapid Mart stores the date



as a string in the format: 'YYYY.MM.DD'. Similarly, the Rapid Mart stores the time in an 8-character string appropriate for your target database. LOAD_DATE and LOAD_TIME can be helpful when using the fact tables in other applications for further data manipulation.

AnalysisWith the tables in this section, you can analyze budget line data along several dimensions including:• By organization• By project• By task• By resource• By job• By vendor• By budget type• By event type• By expenditure type• By date and period (fiscal and project-specific)• By set of books/Ledger• By project agreement• By organization structure• By fixed segment dimensions (Company, Account, Cost Center, Project,

Fund, Intercompany, Product, District) and associated hierarchiesYou can combine the budget line table, BUDGET_LINE_FACT, with other components in this Rapid Mart:• Link budget data to actual dataTypical queries include:• What is the forecast profitability of different project types?• How does the actual profitability of each project compare with its

budgeted profitability?


Subject AreasDraft Revenue Section3
Draft Revenue Section
The Draft Revenue section holds draft project revenue transactions prior to being transferred to other modules in Oracle applications.

Oracle Applications processingIn Oracle Applications, revenue generation creates draft revenues from expenditure item and event data.Specifically revenue distribution lines are created which are then grouped together (by top task and revenue category) to create draft revenue items and the draft revenues.Draft revenues hold summarized data including unbilled receivable and unearned revenue amounts as well as realized gains and losses.The draft revenue entries are held in the PA_DRAFT_REVENUES_ALL table, and PA_DRAFT_REVENUE_ITEMS stores the lines of a draft revenue.

Rapid Mart processingDetailed draft revenue distribution data is handled in the Expenditure and Event sections, therefore this section is concerned with summarized draft revenue data only.The Rapid Mart selects all draft revenue entries from PA_DRAFT_REVENUES_ALL and PA_DRAFT_REVENUE_ITEMS, and loads them into the DRAFT_REVENUE_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, draft revenue entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.


Subject AreasDraft Revenue Section 3

Rapid Mart dataThe following diagram shows the tables that the Draft Revenue section extracts.

Fact table columnsThe draft revenue fact table contains transaction measures and attributes. The columns in the table are described below.• PROJECT_ID

The identifier of the project for which the revenue is generated - foreign key to PROJECT dimension



• DRAFT_REVENUE_NUMThe sequential number that identifies the draft revenue within a project

• LINE_NUMThe sequential number that identifies and orders the draft revenue item for a draft revenue

• ORG_IDOperating unit identifier for multi-organization installations - foreign key to ORGANIZATION dimension

• CREATION_DATEStandard date column - foreign key to TIME_DIM dimension

• ACCRUE_THROUGH_DATEThe date through which to accrue revenue for the project. Expenditure items with item date and events with completion date on or before the accrue through date are included on a revenue. For cost-to-cost accrual, the item PA date is used.

• CUSTOMER_BILL_SPLITThe percentage of the total project revenue that the customer is funding on the draft revenue

• DRAFT_REVENUE_NUM_CREDITEDThe draft revenue number that is credited by this draft revenue

• PERIOD_SET_NAME, GL_PERIOD_NAMEAccounting calendar name. The GL period in which the revenue is posted - foreign key to PERIOD_CALENDAR dimension.

• PERIOD_NAME, ORG_IDThe project period in which the revenue is posted - foreign key to PROJECT_PERIOD dimension.

• RELEASED_DATEThe date on which the draft revenue is released

• TRANSFERRED_DATEThe date that the draft revenue was transferred to General Ledger

• UNBILLED_CODE_COMBINATION_IDThe identifier of the gl account to which the unbilled receivables amount of this draft revenue is charged - foreign key to CODE_COMBINATION dimension

• UNEARNED_CODE_COMBINATION_ID



The identifier of the gl account to which the unearned revenue amount of this draft revenue is charged - foreign key to CODE_COMBINATION dimension

• REALIZED_GAINS_CC_IDThe identifier of the GL account to which the realized gains amount of this draft revenue is charged. This will be populated by Interface revenue to GL process - foreign key to CODE_COMBINATION dimension.

• REALIZED_LOSSES_CC_IDThe identifier of the GL account to which the realized losses amount of this draft revenue is charged. This will be populated by Interface revenue to GL process - foreign key to CODE_COMBINATION dimension.

• UNBILLED_RECEIVABLE_DRThe amount of unbilled receivables debit by the draft revenue

• UNEARNED_REVENUE_CRThe amount of unearned revenue credited by this draft revenue

• REALIZED_GAINS_AMOUNTThe amount realized gains debit by the draft revenue

• REALIZED_LOSSES_AMOUNTThe amount realized losses credited by the draft revenue

• AGREEMENT_IDThe identifier of the agreement that funds the revenue - foreign key to PROJECT_AGREEMENT dimension

• SET_OF_BOOKS_IDThe identifier of the General Ledger set of books used by Oracle Projects. It represents Set Of Books in release 11i and Ledgers in R12 - foreign key to SET_OF_BOOKS dimension


• TASK_IDThe identifier of the task of the revenue line. For a line that accrues event revenue, this is the event task_id. For a line that accrues expenditure item revenue, this is the top_task_id of the tasks to which the items are charged - foreign key to TASK dimension.



• REV_SOURCE_CODE - foreign key to REVENUE_SOURCE dimensionThe source from which the revenue for the revenue line is generated

• REV_CATEGORY_CODE - foreign key to REVENUE_CATEGORY dimensionThe revenue category of the expenditure items grouped into the revenue line

• CURRENCY_CODE_TRXRevenue processing currency - foreign key to CURRENCY dimension.

• CURRENCY_CODE_FNCProject functional currency - foreign key to CURRENCY dimension.

• CURRENCY_CODE_PRJProject currency code - foreign key to CURRENCY dimension.

• CURRENCY_CODE_FUNDFunding currency code - foreign key to CURRENCY dimension.

• LINE_REV_AMOUNT_TRXThe revenue amount accrued for the draft revenue item

• LINE_REV_AMOUNT_FNCRevenue amount in the project functional currency. This is calculated by applying the conversion rules set up for project functional currency during invoice generation

• LINE_REV_AMOUNT_PRJRevenue amount in the project currency. This is calculated by applying the conversion rules set up for project currency during revenue generation.

• LINE_REV_AMOUNT_FUNDRevenue amount in the funding currency. This is calculated by applying the conversion rules set up for funding currency during revenue generation.

• TRANSFER_STATUS_CODEThe status of the revenue as it is transferred to General Ledger - foreign key to TRANSFER_STATUS dimension

• LOAD_DATE and LOAD_TIMEThe Rapid Mart populates these fields with the date and time of the start of the data extraction from Oracle Applications. For Oracle, the Rapid Mart stores the date as a string in the format: 'YYYY.MM.DD HH24:MI:SS'. For other target databases, the Rapid Mart stores the date



as a string in the format: 'YYYY.MM.DD'. Similarly, the Rapid Mart stores the time in an 8-character string appropriate for your target database. LOAD_DATE and LOAD_TIME can be helpful when using the fact tables in other applications for further data manipulation.

AnalysisWith the tables in this section, you can analyze draft revenue data along several dimensions including:• By organization• By project• By date and period (fiscal and project-specific)• By set of books/Ledger• By project agreement• By organization structure• By fixed segment dimensions (Company, Account, Cost Center, Project,

Fund, Intercompany, Product, District) and associated hierarchies


Subject AreasDraft Invoice Section3

You can combine the draft revenue table, DRAFT_REVENUE_FACT, with other components in this Rapid Mart:• Link to revenue distribution data held in EXPENDITURE_REV_FACT and

EVENT_DIST_FACT• Link to the corresponding draft invoice in DRAFT_INVOICE_FACT via

the revenue distribution data.Typical queries include:• List the draft revenues requiring approval• Review the flow of draft revenues through Oracle Projects

Draft Invoice SectionThe Draft Invoice section of this Rapid Mart holds potential project invoices that require approval before they are officially accounted for in other Oracle applications.

Oracle Applications processingIn Oracle Applications, invoice generation creates draft invoices from revenue distribution lines which have not yet been billed.Draft invoices hold summarized data (at line item level) including unbilled receivable and unearned revenue amounts.The draft revenue entries are held in the PA_DRAFT_INVOICES_ALL table, and PA_DRAFT_INVOICE_ITEMS stores the draft invoice lines.

Rapid Mart processingDetailed draft invoice distribution data is handled in the Expenditure and Event sections, therefore this section is concerned with summarized draft invoice data only.The Rapid Mart selects all draft invoice entries from PA_DRAFT_INVOICES_ALL (and the corresponding line items from PA_DRAFT_INVOICE_ITEMS) and loads them into the DRAFT_INVOICE_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, draft revenue entries are first


Subject AreasDraft Invoice Section 3

checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.

Rapid Mart dataThe following diagram shows the tables that the Draft Invoice section extracts.


Fact table columns
The draft invoice fact table contains transaction measures and attributes. The columns in the table are described below.• PROJECT_ID

The identifier of the project for which the invoice is generated - foreign key to PROJECT dimension

• DRAFT_INVOICE_NUMThe draft invoice number to which the invoice line belongs

• LINE_NUMThe sequential number that identifies and orders the draft invoice item for a draft invoice

• PERIOD_NAME, ORG_IDProject period. Operating unit identifier for multi-organization installations - foreign key to PROJECT_PERIOD dimension

• PERIOD_SET_NAME, GL_PERIOD_NAMEAccounting calendar name. Bill Amount in the project functional currency. This is calculated by applying the conversion rules set up for project functional currency during invoice generation - foreign key to PERIOD_CALENDAR dimension.

• APPROVED_BY_PERSON_IDThe identifier of the employee that approved the invoice - foreign key to CURRENT_PEOPLE dimension

• RELEASED_BY_PERSON_IDThe identifier of the employee that released the invoice - foreign key to CURRENT_PEOPLE dimension

• CREATION_DATEDate and Time when the record was created in the source system. Foreign key to TIME_DIM - foreign key to TIME_DIM dimension.

• APPROVED_DATEThe date on which the draft invoice is approved

• INVOICE_DATEThe invoice date passed to Oracle Receivables which is used to calculate the invoice due date. Upon release of the invoice, this date is defaulted from the released date. The user can override the invoice date at the time of release

• RELEASED_DATE



The date that the draft invoice was released for transfer• TRANSFERRED_DATE

The date that the draft invoice was transferred to the Oracle Receivables interface tables

• BILL_THROUGH_DATEThe date through which to invoice the project. Expenditure items with the expenditure item date on or before the bill through date and events with completion dates on or before the bill through date may be included on an invoice.

• CANCELED_FLAGFlag that indicates that the draft invoice was credited by another draft invoice, a credit memo

• CANCEL_CREDIT_MEMO_FLAGFlag that indicates that the draft invoice is a credit memo, crediting or canceling another draft invoice

• CONVERTED_FLAGFlag indicating if the invoice is converted. Y denotes a converted invoice with no detail in AR as PA expects. A value of N or null denotes a non-converted invoice. A converted invoice cannot be cancelled or written off.

• WRITE_OFF_FLAGFlag that indicates that a draft invoice writes off another draft invoice

• CUSTOMER_BILL_SPLITThe percentage of the total project invoice amount that the customer is billed on the draft invoice

• DRAFT_INVOICE_NUM_CREDITEDThe draft invoice number that is credited by this draft invoice. The crediting invoice may be a credit memo or a write-off

• RA_INVOICE_NUMBERThe Oracle Receivables invoice number that is determined upon release of the draft invoice and passed to Oracle Receivables upon transfer. This number can be user-entered or system-generated as defined in the implementation options.

• INV_CURRENCY_CODEInvoice currency code for the draft invoice that is transferred to Oracle Receivables - foreign key to CURRENCY dimension.

• UNBILLED_CODE_COMBINATION_ID



The identifier of the GL account to which the unbilled receivable amount is charged This column is populated by the Transfer Invoices to Receivables process - foreign key to CODE_COMBINATION dimension

• UNEARNED_CODE_COMBINATION_IDThe identifier of the GL account to which the unearned revenue amount is charged This column is populated in Transfer Invoice to Receivable program from Release 11i - foreign key to CODE_COMBINATION dimension

• UNBILLED_RECEIVABLE_DRThe amount of unbilled receivables debited by the draft invoice. This amount is determined by the Transfer Invoice program

• UNEARNED_REVENUE_CRThe amount of unearned revenue credited by the draft invoice. This amount is determined by the Transfer Invoice program

• AGREEMENT_ID The identifier of the agreement that funds the invoice - foreign key to PROJECT_AGREEMENT dimension



• TASK_IDThe identifier of the top task. This column is populated if: the project is funded at top task level, or for expenditure item lines, the invoice format groups by Top Task, or for event lines, both invoice formats group by Top Task - foreign key to TASK dimension

• INV_LINE_DESCThe invoice line description. For a line billing an event, this description is the event description. For a line billing expenditure items, this description is formatted according to the project invoice formats

• INV_LINE_TYPEThe type of draft invoice line



• DRAFT_INV_LINE_NUM_CREDITEDThe draft invoice line number that is credited by this invoice line

• CURRENCY_CODE_TRXTransaction currency code - foreign key to CURRENCY dimension.

• CURRENCY_CODE_FNCProject functional currency code - foreign key to CURRENCY dimension.

• CURRENCY_CODE_PRJProject currency code - foreign key to CURRENCY dimension.

• CURRENCY_CODE_FUNDFunding currency code - foreign key to CURRENCY dimension.

• CURRENCY_CODE_INVInvoice processing currency code - foreign key to CURRENCY dimension.

• LINE_AMOUNT_INVThe amount to be billed in the invoicing currency code for the draft invoice item.

• LINE_AMOUNT_TRXThe amount to be billed for the draft invoice item

• LINE_BILL_AMOUNT_TRXBill Amount in the transaction currency. This is calculated by applying the conversion rules set up for transaction currency during invoice generation.

• LINE_BILL_AMOUNT_FNCBill Amount in the project functional currency. This is calculated by applying the conversion rules set up for project functional currency during invoice generation.

• LINE_BILL_AMOUNT_PRJBill Amount in the project currency. This is calculated by applying the conversion rules set up for project currency during invoice generation.

• LINE_BILL_AMOUNT_FUNDBill Amount in the funding currency. This is calculated by applying the conversion rules set up for funding currency during invoice generation.

• LINE_ACCT_AMOUNT_FNCThe Functional Currency amount of that has been accounted in Oracle ReceivablesThis column is populated in the Transfer Invoice to Oracle Receivables process



• TRANSFER_STATUS_CODEThe status of the invoice as it is transferred to Oracle Receivables - foreign key to TRANSFER_STATUS dimension

• LOAD_DATE and LOAD_TIMEThe Rapid Mart populates these fields with the date and time of the start of the data extraction from Oracle Applications. For Oracle, the Rapid Mart stores the date as a string in the format: 'YYYY.MM.DD HH24:MI:SS'. For other target databases, the Rapid Mart stores the date as a string in the format: 'YYYY.MM.DD'. Similarly, the Rapid Mart stores the time in an 8-character string appropriate for your target database. LOAD_DATE and LOAD_TIME can be helpful when using the fact tables in other applications for further data manipulation.

AnalysisWith the tables in this section, you can analyze draft invoice data along several dimensions including:• By organization• By project• By date and period (fiscal and project-specific)• By fixed segment dimensions (Company, Account, Cost Center, Project,

Fund, Intercompany, Product, District) and associated hierarchiesYou can combine the draft invoice table, DRAFT_INVOICE_FACT, with other components in this Rapid Mart:• Link to revenue distribution data in EXPENDITURE_REV_FACT and

EVENT_DIST_FACTTypical queries include:• List draft invoices for verification before approving and releasing them for

interface to Oracle Receivables• Review the billing status of projects


Subject AreasExpenditure Section 3

Expenditure SectionThe Expenditure section of this Rapid Mart contains details of expenditure items incurred by an employee or organization. Details include expenditure cost and revenue distributions by accounting flexfield segments.

Oracle Applications processingIn Oracle Applications, expenditure transactions are created whenever any expenditure is entered into the system such as timecard, usage, expense report, or vendor invoice. These expenditure items are created in the PA_EXPENDITURE_ITEMS_ALL table and this is the core transaction table used as a basis by many of the batch processes.The raw cost, burden cost, accrued revenue and bill amount are subsequently populated by the various batch processes.Expenditure items are generally grouped by a week ending date and an incurring employee/organization into the expenditures table, PA_EXPENDITURES. During draft revenue generation, draft revenue distribution lines are created and stored in the table, PA_CUST_REV_DIST_LINES_ALL. During cost distribution processing, expenditure items are created as lines in PA_COST_DISTRIBUTION_LINES_ALL to contain cost amounts and their corresponding GL account information.

Rapid Mart processingThis section includes three fact tables, EXPENDITURE_FACT holding summarized expenditure data (at transaction item level), EXPENDITURE_REV_FACT which holds detailed revenue data distributed against the account segment, and EXPENDITURE_COST_FACT which holds detailed revenue data distributed against the account segment.First, the Rapid Mart selects all expenditure items from PA_EXPENDITURES and PA_EXPENDITURE_ITEMS_ALL and loads them into the EXPENDITURE_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, expenditure item entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.


Subject AreasExpenditure Section3

Next the Rapid Mart selects all expenditure item revenue distribution entries from PA_CUST_REV_DIST_LINES_ALL and loads them into the EXPENDITURE_REV_FACT target table. Finally, the Rapid Mart selects all expenditure item cost distribution entries from PA_COST_DISTRIBUTION_LINES_ALL and loads them into the EXPENDITURE_COST_FACT target table. In these cases, the source tables do not include timestamps, thus there is no incremental load, data is always deleted from the target table prior to loading and fully reloaded.

Rapid Mart dataThe following diagram shows the tables that the Expenditure section extracts.



Fact table columnsEXPENDITURE_FACTThe expenditure fact table contains transaction measures and attributes. The columns in the table are described below.• EXPENDITURE_ITEM_ID

The system-generated number that uniquely identifies the expenditure item

• EXPENDITURE_IDThe system-generated number that uniquely identifies the expenditure

• EXPENDITURE_STATUS_CODEThe status of the expenditure as it is entered and approved

• EXPENDITURE_ENDING_DATEThe last day of the expenditure week period. All expenditure items for the expenditure must be on or before this expenditure ending date. All timecard items must be within this expenditure ending date period

• EXPENDITURE_GROUP_CODEThe expenditure group to which expenditure belongs. This is only applicable for pre-approved expenditures. This column is blank for online expenditures - foreign key to EXPENDITURE_GROUP dimension

• EXPENDITURE_CLASSThe classification of the expenditure, indicating the type of items grouped into it

• EXPENDITURE_TYPE_IDThe expenditure type that classifies the type of work performed - foreign key to EXPENDITURE_TYPE dimension

• EXPENDITURE_ITEM_DATEThe date on which the work occurred

• CREATION_DATEDate and time when expenditure transaction line was created in the source system


• PROJECT_IDThe project_id of the event that the expenditure item is FIFO marked by - foreign key to PROJECT dimension



• TASK_IDThe identifier of the task to which the expenditure item is charged - foreign key to TASK dimension

• JOB_IDThe identifier of the job of an employee as of the expenditure item date. Required for all items incurred by an employee. This may be used in the mapping of the transaction to a resource for project summary amounts - foreign key to JOB dimension.

• VENDOR_IDIdentifier of the supplier - foreign key to VENDOR dimension

• INCURRED_BY_ORG_IDThe identifier of the organization that incurred the charges. Column is populated for all charges except supplier invoices, where the organization is held at the expenditure item level, as each inv distribution may have different org - foreign key to ORGANIZATION dimension

• INCURRED_BY_PERSON_IDThe identifier of the employee who incurred the charges. This column is always populated for labor and expense report charges and is not populated for supplier invoices. For usages, specifying employees who incurred the charges is optional - foreign key to CURRENT_PEOPLE dimension

• ENTERED_BY_PERSON_IDThe identifier of the person who entered the expenditure. This value is not populated for supplier invoice expenditures - foreign key to CURRENT_PEOPLE dimension

• COST_DISTRIBUTED_FLAGFlag that indicates whether the item has been cost distributed. When N the item is marked for cost distribution. When the item is cost distributed, the flag is set to Y.

• REVENUE_DISTRIBUTED_FLAGFlag that indicates whether the item is revenue distributed. Upon entry, this flag is set to N. When the item is revenue distributed, the flag is set to Y or P

• BILLABLE_FLAGFlag that indicates if the item can accrue revenue. Upon entry, this flag is defaulted from the task to which the item is charged, or is based on transaction controls.

• BILL_HOLD_FLAG



Flag that indicates if the item is held from invoicing. Upon entry, this flag is defaulted to N.

• NON_LABOR_RESOURCEThe non-labor resource utilized as the work was performed. This column is only populated for usage items

• NON_LABOR_RESOURCE_ORG_IDThe identifier of the organization that owns the non-labor resource that was utilized as the work was performed. This column is only populated for usage items - foreign key to ORGANIZATION dimension

• OVERRIDE_TO_ORG_IDThe identifier of the organization that the cost and revenue for this item are charged to by a cost distribution override entered for the project. For supplier invoices, the expenditure organization entered in Oracle Payables - foreign key to ORGANIZATION dimension

• RECEIPT_CURRENCY_CODEReceipt currency code of the transaction - foreign key to CURRENCY dimension

• DENOM_CURRENCY_CODETransaction Currency code of the transaction - foreign key to CURRENCY dimension

• ACCT_CURRENCY_CODEAccount currency code of the transaction - foreign key to CURRENCY dimension

• PROJECT_CURRENCY_CODEProject Currency Code of the Transaction - foreign key to CURRENCY dimension

• PROJFUNC_CURRENCY_CODEProject functional currency code - foreign key to CURRENCY dimension.

• BILL_TRANS_CURRENCY_CODEBill transaction currency code for the expenditure item for accrued revenue and bill amounts - foreign key to CURRENCY dimension

• REVPROC_CURRENCY_CODERevenue Processing Currency Code - foreign key to CURRENCY dimension

• INVPROC_CURRENCY_CODEInvoice Processing Currency - foreign key to CURRENCY dimension

• RAW_COST_RATE



The raw cost rate used to cost the item• BURDEN_COST_RATE

The burdened cost rate of the item. Burdened cost rate = (burden cost / quantity).

• BILL_RATEThe bill rate for the expenditure item. This column is not populated if (1) a markup percentage or labor multiplier was used to calculate T&M revenue or (2) if revenue is accrued under a Cost/Cost or Cost/Event distribution rule

• QUANTITYThe number of units of the work performed

• RAW_COSTRaw cost in project Currency

• BURDEN_COSTThe burden cost in project currency

• RAW_REVENUEThe potential revenue of the item. With T&M revenue accrual, raw revenue = (quantity * bill rate) or (raw cost * (markup/100) or (raw cost * labor multiplier). With COST revenue accrual, raw revenue = items portion of the total revenue

• BILL_AMOUNTThe amount to be billed for the item. This must always equal the sum of the bill amount on the revenue distribution lines. This amount may differ from the revenue amount if using Cost/Work or if the project hit hard funding limit.

• ACCRUED_REVENUEThe total amount of revenue that the item accrued. This amount should always equal the sum of the revenue amount in the revenue distribution lines. This amount is different from raw revenue if the project hit a hard funding limit

• ADJUSTED_REVENUEThe discounted revenue amount of the item based on the bill rate schedule discount. Adjusted revenue = (raw revenue * (100-schedule discount)/100)

• FORECAST_REVENUE



The forecast revenue amount of a labor item based on T&M bill rates and markups and labor multipliers. This column is populated by the Compute Forecast Revenue process. Once the item is revenue distributed, this column is cleared

• RECEIPT_CURRENCY_AMOUNTReceipt currency amount of the transaction

• DENOM_RAW_COSTThe total raw cost of the expenditure item in transaction currency Raw cost = (quantity * cost rate) This value should always equal the sum of the items raw cost distribution lines

• DENOM_BURDENED_COSTTotal burdened cost of the expenditure item in transaction currency Burdened cost = (raw cost * (1 + burden cost multiplier)) This must equal the sum of the items burden debit cost distribution lines For non-burdened items, burdened cost

• ACCT_RAW_COSTRaw cost in Functional Currency

• ACCT_BURDENED_COSTBurdened Cost in Functional Currency

• PROJECT_RAW_COSTRaw cost in project currency.

• PROJECT_BURDENED_COSTBurdened cost in project currency.

• PROJECT_RAW_REVENUERevenue Amount in Project

• PROJECT_BILL_AMOUNTBill Amount in Project

• PROJFUNC_RAW_REVENUERevenue Amount in Project Functional

• PROJFUNC_BILL_AMOUNTBill Amount in Project Functional

• BILL_TRANS_RAW_REVENUEThe raw revenue of the item in bill transaction currency

• BILL_TRANS_BILL_AMOUNTBill amount in bill transaction currency.



• BILL_TRANS_ADJUSTED_REVENUEThe adjusted revenue of the item in bill transaction currency. For Work revenue accrual or invoicing method adjusted revenue = (quantity * bill rate) or (project currency raw cost * (markup/100) or (project currency raw cost * labor

• POSTED_DENOM_BURDENED_COSTAccounted burden amount in transaction currency.

• POSTED_PROJECT_BURDENED_COSTAccounted burden amount in project currency.

• POSTED_PROJFUNC_BURDENED_COSTAccounted burden amount in project functional currency.

• POSTED_ACCT_BURDENED_COSTAccounted burden amount in expenditure functional currency.

• EXPENDITURE_COMMENTExpenditure Item comment; limited to the first line up to 240 characters.



• PERIOD_SET_NAME, GL_PERIOD_NAMESystem generated accounting period - foreign key to PERIOD_CALENDAR




EXPENDITURE_REV_FACTThe expenditure revenue fact table contains transaction measures and attributes. The columns in the table are described below.• EXPENDITURE_ITEM_ID

The identifier of the expenditure item that is revenue distributed by the distribution line

• LINE_NUMThe sequential number that identifies the revenue distribution line for the expenditure item


• PROJECT_IDThe identifier of the project for which the invoice is generated - foreign key to PROJECT dimension


• CREATION_DATEDate and time when the expenditure distribution line was created in the source system - foreign key to TIME_DIM dimension

• DRAFT_REVENUE_NUMThe draft revenue number for which the revenue distribution line is generated

• DRAFT_REVENUE_ITEM_LINE_NUMThe draft revenue item line number under which the revenue distribution line is generated

• DRAFT_INVOICE_NUMThe draft invoice number to which the invoice line belongs

• DRAFT_INVOICE_ITEM_LINE_NUMThe sequential number that identifies and orders the draft invoice item for a draft invoice

• BATCH_NAME



The reference to the GL je line in which the revenue was included when posted to GL. This value is a concatenation of ccid, draft revenue gl date, and transfer request id separated by hyphens. Joins to GL_JE_LINES.REFERENCE1

• ADDITIONAL_REVENUE_FLAGFlag that indicates if the distribution line is adding additional revenue for an item so that the item will accrue its full potential revenue. This distribution line is used to increment revenue and will never be billed.

• CODE_COMBINATION_IDA foreign key to identify a combination of codes that the organization uses to identify general ledger accounts. Oracle Applications represent these codes using a particular key flexfield called the Accounting Flexfield. One organization might choose to customize the Accounting Flexfield to include five segments: company, division, department, account, and project. Another organization, however, might structure their general ledger account segments differently, perhaps using twelve segments instead of five. The Accounting Flexfield lets the Oracle Payables application accommodate the needs of different organizations by allowing them to customize that key flexfield to their particular business usage. The code combination dimension contains concatenated codes, account type definition (Asset, Expense, Liability, Equity, Revenue) as well as grouping the codes by the eight most common fixed segments: Company, Account, Product, Cost Center, District, Project, Fund and Intercompany.

• BILL_TRANS_CURRENCY_CODEBill transaction currency code for the expenditure item - foreign key to CURRENCY dimension.

• REVPROC_CURRENCY_CODERevenue processing currency code - foreign key to CURRENCY dimension

• INVPROC_CURRENCY_CODEInvoice processing currency - foreign key to CURRENCY dimension.

• PROJECT_CURRENCY_CODEProject currency code - foreign key to CURRENCY dimension.


• FUNDING_CURRENCY_CODE



Funding currency code - foreign key to CURRENCY dimension.• AMOUNT

The Revenue amount of the expenditure item to be charged to the GL account in the revenue processing currency. The amount is stored as debit, so the lent transaction amounts and adjustment amounts are negative.

• BILL_AMOUNTThe amount to be billed for the distribution line in invoice processing currency.

• RAW_COSTraw_cost column will have the value of burden_cost for BURDEN TRANSACTIONS

• BILL_TRANS_AMOUNTThe billing amount of the item in the bill transaction currency.

• BILL_TRANS_BILL_AMOUNTBase bill amount in the bill transaction currency.

• PROJECT_REVENUE_AMOUNTRevenue Amount in the project currency.

• PROJECT_BILL_AMOUNTBill amount in the project currency. This is calculated by applying the conversion rules set up for project currency during invoice generation

• PROJFUNC_REVENUE_AMOUNTRevenue amount in the project functional currency.

• PROJFUNC_BILL_AMOUNTBill Amount in the project functional currency. This is calculated by applying the conversion rules set up for project functional currency during invoice generation.

• FUNDING_REVENUE_AMOUNTRevenue amount in the funding currency

• FUNDING_BILL_AMOUNTBill amount in funding currency.

• RETAINED_AMOUNTRetained amount. This amount is in the invoice processing currency.

• SET_OF_BOOKS_ID





• PERIOD_SET_NAME, GL_PERIOD_NAMESystem generated accounting period - foreign key to PERIOD_CALENDAR




EXPENDITURE_COST_FACTThe expenditure cost fact table contains transaction measures and attributes. The columns in the table are described below.• EXPENDITURE_ITEM_ID

The identifier of the expenditure item that is revenue distributed by the distribution line

• LINE_NUMThe sequential number that identifies the revenue distribution line for the expenditure item


• PROJECT_IDThe identifier of the project for which the invoice is generated - foreign key to PROJECT dimension


• CREATION_DATEDate and time when the expenditure distribution line was created in the source system - foreign key to TIME_DIM dimension

• BATCH_NAMEThe reference to a batch of lines transferred together. For expense reports, this is an expenditure batch. For cost transferred to GL, this is a concatenation of liability ccid, gl date, and transfer request id separated by hyphens.

• AMOUNTAmount in project currency Derrived by converting raw cost in transaction currency to project currency

• QUANTITYThe number of units that are costed in the distribution line cost. The quantity is set from the expenditure item quantity when the distribution line is created and is used for populating the quantities in the accumulation tables

• BILLABLE_FLAG



Flag that indicates whether the cost amount is billable. The flag is set from the expenditure item billable flag when the distribution line is created and is used for determining billable/non-billable costs in the accumulation tables

• COST_DIST_LINE_TYPEThe type of the cost distribution line - foreign key to COST_DISTRIBUTION_TYPE dimension

• PARENT_LINE_NUMLine Number for the raw cost distribution line. Valid for I line types only.

• DR_CODE_COMBINATION_IDThe identifier of the GL account to which the cost is charged

• CR_CODE_COMBINATION_IDThe identifier of the GL liability account

• CODE_COMBINATION_IDA foreign key to identify a combination of codes that the organization uses to identify general ledger accounts. Oracle Applications represent these codes using a particular key flexfield called the Accounting Flexfield. One organization might choose to customize the Accounting Flexfield to include five segments: company, division, department, account, and project. Another organization, however, might structure their general ledger account segments differently, perhaps using twelve segments instead of five. The Accounting Flexfield lets the Oracle Payables application accommodate the needs of different organizations by allowing them to customize that key flexfield to their particular business usage. The code combination dimension contains concatenated codes, account type definition (Asset, Expense, Liability, Equity, Revenue) as well as grouping the codes by the eight most common fixed segments: Company, Account, Product, Cost Center, District, Project, Fund and Intercompany.Calculated Code Combination ID. If it 'C'' or ''D'' line type, then it is one of DR_CODE_COMBINATION_ID or CR_CODE_COMBINATION_ID (exclusive). If it is any other, we pick DR_CODE_COMBINATION_ID because CR_CODE_COMBINATION_ID will represent Liability (or total CR when posting to GL) - foreign key to CODE_COMBINATION dimension

• ENCUMBRANCE_BATCH_NAMEThe batch name used which creating encumbrance liquidation.

• ENCUMBRANCE_TYPE_ID



Commitment encumbrance type identifier used during processing.• WORK_TYPE_ID

Identifier for a work type assigned to the transaction.• DENOM_CURRENCY_CODE

Transaction Currency code of the transaction - foreign key to CURRENCY dimension

• ACCT_CURRENCY_CODEFunctional Currency Code - foreign key to CURRENCY dimension

• PROJECT_CURRENCY_CODEProject currency code of the transaction - foreign key to CURRENCY dimension

• PROJFUNC_CURRENCY_CODEProject functional currency code - foreign key to CURRENCY dimension

• PA_DATEDate used to determine the correct project accounting period in the provider operating unit. The PA date is determined by the Distribution programs from the open or future PA period on or after the transaction date

• GL_DATEDate used to determine the correct general ledger accounting period in the provider operating unit. The GL date is determined by the Distribution programs from the open or future GL period on or after the transaction date. For supplier in

• RECVR_PA_DATEDate used to determine the correct project accounting period in the receiver operating unit. The PA date is determined by the Distribution programs from the open or future PA period on or after the transaction date

• RECVR_GL_DATEDate used to determine the correct general ledgert accounting period in the receiver operating unit. The GL date is determined by the Distribution programs from the open or future GL period on or after the transaction date

• PERIOD_NAME, ORG_IDThe PA period in which the transaction is posted - foreign key to PROJECT_PERIOD dimension

• RECVR_PA_PERIOD_NAME



The PA period in which the transaction is posted on the receiving ledger.• ENCUMBRANCE_AMOUNT

The amount encumbered when the encumbrance liquidation is created.• BURDENED_COST

Amount of the burdened cost in project currency• DENOM_BURDENED_COST

The amount of the burdened cost in transaction currency It is only populated for raw cost distribution lines

• ACCT_BURDENED_COSTBurdened cost in functional currency

• PROJECT_BURDENED_COSTBurdened cost in project currency.

• DENOM_RAW_COSTThe raw cost in transaction currency

• ACCT_RAW_COSTThe amount in functional currency to be charged to the gl account for the expenditure item The amount is stored as a debit, so the burden credit amounts and adjustment amounts are negative

• PROJECT_RAW_COSTRaw cost in project currency.

• DENOM_BURDENED_CHANGEChange in burdened cost since last time distribution lines were created. Stored in transaction currency.

• PROJECT_BURDENED_CHANGEChange in burdened cost since last time the distribution lines were created. Stored in project currency.

• PROJFUNC_BURDENED_CHANGEChange in burdened cost since last time distribution lines were created. Stored in project functional currency.

• ACCT_BURDENED_CHANGEChange in burdened cost since last time distribution lines were created. Stored in functional currency.

• SET_OF_BOOKS_IDThe identifier of the General Ledger set of books used by Oracle Projects. It represents Set Of Books in release 11i and Ledgers in R12 - foreign key to SET_OF_BOOKS dimension.



• ORGANIZATION_STRUCTURE_ID,ORG_STRUCTURE_VERSION_ID,START_ORGANIZATION_IDidentifier of the default organization hierarchy used for reporting; Identifier of the default organization hierarchy version used for reporting; Identifier of the highest organization used in default reporting organization hierarchy version - foreign key to ORG_STRUCTURE dimension.

• PERIOD_SET_NAME, GL_PERIOD_NAMECalendar name. The GL period in which the transaction is posted - foreign key to PERIOD_CALENDAR dimension

• SYSTEM_REFERENCE1The reference to the record in another application when the line is transferred. For supplier invoices, this holds AP_INVOICES.VENDOR_ID. This is not used for other adjustment lines.

• SYSTEM_REFERENCE2The reference to the record in another application when the line is transferred For supplier invoices and expense reports, this holds the AP_INVOICESINVOICE_ID Not used for labor and usages

• SYSTEM_REFERENCE3The reference to the record in another application when the line related to supplier invoice or expense report is transferred. It holds AP_INVOICE_DISTRIBUTIONS.DISTRIBUTION_LINE_NUMBER.

• SYSTEM_REFERENCE4The reference to the record in another application when the line related to supplier invoice or expense report is transferred. It holds AP_INVOICE_PAYMENTS_ALL. INVOICE_PAYMENT_ID

• TRANSFER_STATUS_CODEThe status of the distribution line as the cost information is transferred to another application - foreign key to TRANSFER_STATUS dimension



Subject AreasEvent Distribution Section3
Analysis
With the tables in this section, you can analyze expenditure item transactions along several dimensions including:• By organization• By project• By project class category• By task• By job• By vendor• By expenditure group• By expenditure type• By date and period (fiscal and project-specific)• By fixed segment dimensions (Company, Account, Cost Center, Project,

Fund, Intercompany, Product, District) and associated hierarchiesYou can combine the expenditure revenue distribution table, EXPENDITURE_REV_FACT, with other components in this Rapid Mart:• Show the related draft revenue entries in DRAFT_REVENUE_FACT• Link to the related draft involves entries in DRAFT_INVOICE_FACTTypical queries include:• Show an overview of expenditures for one project or many projects

belonging to a specified organization or project manager.• List each expenditure item’s revenue amount, burdened cost amount,

and billing status for a particular project.

Event Distribution SectionThe Event section of this Rapid Mart contains summary level transactions generating revenue and/or billing activity that are not directly related to any expenditure items.

Oracle Applications processingIn Oracle Applications, event entries are created whenever any event that is entered into the system that is not directly related to any expenditure item such as bonus received for completing a project or task ahead of schedule.Events are usually created under one of the following classifications• Write-On


Subject AreasEvent Distribution Section 3

• Write-Off• Deferred Revenue• Invoice Reduction• Manual• AutomaticWrite-on events have positive revenue and invoice amounts. Write-Off events have only a revenue amount and it is processed as a negative.Deferred Revenue events have a positive invoice amount and no revenue amountInvoice Reduction events have only an invoice amount which though entered as a positive value, gets processed as a negative, i.e. reduces invoice amountManual events can be both positive and negative, and can have a revenue and invoice amountAutomatic events can also be both positive and negative with either a revenue or invoice amount, or both, and get processed as such.Events are created in the PA_EVENTS table. During draft revenue generation, draft revenue distribution lines are created and stored in the table, PA_CUST_EVENT_RDL_ALL.

Rapid Mart processingThis section includes one fact table, EVENT_DIST_FACT which holds detailed data distributed against the account segment.First, the Rapid Mart selects all events from PA_EVENTS and loads event distribution entries from PA_CUST_EVENT_RDL_ALL into the EVENT_DIST_FACT target table. In this case, since the source table does not include timestamps, there is no incremental load, data is always deleted from the target table prior to loading and fully reloaded.


Rapid Mart data
The following diagram shows the tables that the Event section extracts.

Fact table columnsEVENT_DIST_FACTThe event distribution fact table contains transaction measures and attributes. The columns in the table are described below.• PROJECT_ID

The identifier of the project for which the revenue distribution line is generated. This project is the project for which the event is entered - foreign key to PROJECT dimension

• TASK_ID



The identifier of the task that the event is assigned to - foreign key to TASK dimension

• EVENT_NUMThe event number of the event that is revenue distributed by the distribution line

• LINE_NUMThe sequential number that identifies the revenue distribution line for an event


• CREATION_DATEDate and time when the record was created in the application - foreign key to the TIME_DIM dimension

• EVENT_IDPrimary key for table - foreign key to EVENT dimension

• DRAFT_REVENUE_NUMThe draft revenue number for which the revenue distribution line is generated

• DRAFT_REVENUE_ITEM_LINE_NUMThe draft revenue item line number under which the revenue distribution line is generated

• DRAFT_INVOICE_NUMThe draft invoice number on which the event distribution line is invoiced

• DRAFT_INVOICE_ITEM_LINE_NUMThe draft invoice item line number on which the event distribution line is invoiced

• CODE_COMBINATION_IDA foreign key to identify a combination of codes that the organization uses to identify general ledger accounts. Oracle Applications represent these codes using a particular key flexfield called the Accounting Flexfield. One organization might choose to customize the Accounting Flexfield to include five segments: company, division, department, account, and project. Another organization, however, might structure their general ledger account segments differently, perhaps using twelve segments instead of five. The Accounting Flexfield lets the Oracle



Payables application accommodate the needs of different organizations by allowing them to customize that key flexfield to their particular business usage. The code combination dimension contains concatenated codes, account type definition (Asset, Expense, Liability, Equity, Revenue) as well as grouping the codes by the eight most common fixed segments: Company, Account, Product, Cost Center, District, Project, Fund and Intercompany.

• BILL_TRANS_CURRENCY_CODEBill transaction currency code for the expenditure item - foreign key to CURRENCY dimension.

• REVPROC_CURRENCY_CODERevenue processing currency - foreign key to CURRENCY dimension.

• INVPROC_CURRENCY_CODEInvoice processing currency - foreign key to CURRENCY dimension.

• PROJECT_CURRENCY_CODEProject currency code - foreign key to CURRENCY dimension.


• FUNDING_CURRENCY_CODEFunding currency code - foreign key to CURRENCY dimension.

• AMOUNTThe Revenue amount to be charged to the GL account for the event on a draft revenue in the revenue processing currency.

• BILL_TRANS_AMOUNTThe billing amount of the item in the bill transaction currency.

• PROJECT_REVENUE_AMOUNTRevenue Amount in the project functional currency.

• PROJECT_BILL_AMOUNTBill amount in the project currency. This is calculated by applying the conversion rules set up for project currency during invoice generation.

• PROJFUNC_REVENUE_AMOUNTRevenue amount in the project functional

• PROJFUNC_BILL_AMOUNT



Bill Amount in the project functional currency. This is calculated by applying the conversion rules set up for project functional currency during invoice generation.

• FUNDING_REVENUE_AMOUNTRevenue amount in the funding currency.

• FUNDING_BILL_AMOUNTBill amount in funding currency.

• RETAINED_AMOUNTRetained amount. This amount is in the invoice processing currency



• PERIOD_SET_NAME, GL_PERIOD_NAMECalendar name. - foreign key to PERIOD_CALENDAR dimension

• EVENT_TYPE_IDThe event type ID that classifies the event


AnalysisWith the tables in this section, you can analyze event data along several dimensions including:• By organization• By project



• By project class category• By event type• By date and period (fiscal and project specific)• By fixed segment dimensions (Company, Account, Cost Center, Project,

Fund, Intercompany, Product, District) and associated hierarchiesYou can combine the event distribution table, EVENT_DIST_FACT, with other components in this Rapid Mart:• Show the related draft revenue entries in DRAFT_REVENUE_FACT• Link to the related draft invoice entries in DRAFT_INVOICE_FACTTypical queries include:• Show all events that have been held from invoicing• List the billing events that have not yet been billed for the project


Subject AreasProject Asset Section 3

Project Asset SectionThe Project Asset section of this Rapid Mart holds capital and retirement adjustment assets for capital projects.

Oracle Applications processingOracle Applications supports different project types that have different characteristics.Indirect projects collect and track expenditure item costs and labor hours for overhead activities, such as administrative and overhead work, marketing, and bid & proposal preparation. Indirect projects can also track time off including sick leave, vacation, and holidays.Contract projects collect and track costs, labor hours, revenue, and billing for services performed for and reimbursed by a client.Whereas capital projects collect and track costs and labor hours for asset development activities that are capitalized as one or more assets.Assets associated with capital projects are stored in the PA_PROJECT_ASSETS_ALL and PA_PROJECT_ASSET_LINES_ALL tables.

Rapid Mart processingThe Rapid Mart selects all project asset data from the source tables specified above and loads them into the PROJECT_ASSET_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, project asset entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.


Subject AreasProject Asset Section3
Rapid Mart data
The following diagram shows the tables that the Project Asset section extracts.

Fact table columnsThe project asset fact table contains transaction measures and attributes. The columns in the table are described below.• PROJECT_ASSET_LINE_ID

The system-generated number that uniquely identifies the asset line• PROJECT_ASSET_ID

The system-generated number that uniquely identifies the asset• ASSET_NUMBER

Unique asset identifier; can be user-entered or system-generated by Oracle Assets

• ASSET_NAMEUser-defined name that uniquely identifies an asset within a project

• ASSET_DESCRIPTIONDescription; placed on parent mass additions line upon transfer to Oracle Assets

• ASSET_LINE_DESCRIPTIONDescription of the asset line, derived from the CIP grouping method



• ASSET_UNITSThe number of asset units

• BOOK_TYPE_IDThe corporate book to which the asset is assigned - foreign key to BOOK_TYPE dimension


• PROJECT_IDThe identifier of the project to which this asset belongs - foreign key to PROJECT dimension

• LOCATION_IDThe identifier of the location to which the asset is assigned - foreign key to ASSET_LOCATION dimension

• ASSET_CATEGORY_IDThe identifier of the asset category to which the asset is assigned - foreign key to ASSET_CATEGORY dimension

• ASSIGNED_TO_PERSON_IDThe identifier of the employee to whom the asset is assigned - foreign key to CURRENT_PEOPLE dimension

• CAPITALIZED_DATEThe last date non-reversing cost adjustments were interfaced to Oracle Assets

• CREATION_DATEStandard Date Column - foreign key to TIME_DIM dimension

• DATE_PLACED_IN_SERVICEDate placed in service of the asset

• ESTIMATED_IN_SERVICE_DATEThe assets estimated date placed in service

• CAPITALIZED_FLAGIndicates whether or not the asset has been interfaced to Oracle Assets

• AMORTIZE_FLAGIndicates whether or not cost adjustments should be amortized in Oracle Assets

• DEPRECIATE_FLAG


Subject AreasProject Asset Section3

Indicates whether or not the asset should be depreciated in Oracle Assets

• CAPITALIZED_COSTThe cost amount which has been interfaced to Oracle Assets for capitalization.

• GROUPED_CIP_COSTThe assets cost amount which has been grouped into asset lines.

• ORIGINAL_ASSET_COSTThe cost amount of the line at the time the line was originally created

• CURRENT_ASSET_COSTThe lines current cost amount; split lines have a current cost <> original cost



• PERIOD_SET_NAME, GL_PERIOD_NAMECalendar name. - foreign key to PERIOD_CALENDAR dimension

• CURRENCY_CODE_PRJ Currency code of the project - foreign key to CURRENCY dimension




AnalysisWith the tables in this section, you can analyze project assets along several dimensions including:• By organization• By project• By location• By asset category• By date and fiscal periodYou can combine the project asset table, PROJECT_ASSET_FACT, with other components in this Rapid Mart:• Compare with budget and forecast values held in BUDGET_LINE_FACT.Typical queries include:• Show capital project amounts by project, event, and asset• Compare current asset costs against original costs


Subject AreasBudget Summary Section3
Budget Summary Section
The Budget Summary section of this Rapid Mart contains summarized inception-to-date, year-to-date, period-to-date and prior period budget data.

Oracle Applications processingOracle Applications provides a number of summary tables that hold accumulated data to simplify reporting and analysis especially when comparing against previous periods.This includes a table containing accumulated budget data, PA_PROJECT_ACCUM_BUDGETS along with a header table PA_PROJECT_ACCUM_HEADERS.These tables are not maintained automatically. Instead a batch process (PRC: Refresh Project Summary Amounts) must be run to populate these tables.

Rapid Mart processingThe Rapid Mart selects all accumulated budget data from the source tables specified above and loads them into the BUDGET_SUMMARY_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, accumulated budget entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.


Subject AreasBudget Summary Section 3

Rapid Mart dataThe following diagram shows the tables that the Budget Summary section extracts.

Fact table columnsThe reservation fact table contains transaction measures and attributes. The columns in the table are described below.• PROJECT_ACCUM_ID

The identifier which uniquely defines this line• BUDGET_TYPE_CODE

The identifier of budget type for which this line was created - foreign key to BUDGET_TYPE dimension


• PROJECT_IDThe identifier of project for which the header was created - foreign key to PROJECT dimension



• TASK_IDThe identifier of task for which the header was created - foreign key to TASK dimension

• PERIOD_SET_NAME, GL_PERIOD_NAMEAccounting calendar name. Last accumulation GL Period - foreign key to PERIOD_CALENDAR

• PERIOD_NAME, ORG_IDLast accumulation GL or PA period, depending on the imp. option - foreign key to PERIOD_CALENDAR or PROJECT_PERIOD dimension

• RESOURCE_IDThe identifier of resource for which the header was created - foreign key to PROJECT_RESOURCE dimension

• BASE_UNIT_OF_MEASUREBase unit of measurement

• BASE_RAW_COST_ITDInception to date base raw cost for project

• BASE_RAW_COST_YTDYear to date base raw cost for project

• BASE_RAW_COST_PPBase raw cost for prior GL or PA period

• BASE_RAW_COST_PTDPeriod to date base raw cost for PA or GL period

• BASE_BURDENED_COST_ITDInception to date base burdened cost for project

• BASE_BURDENED_COST_YTDYear to date base burdened cost for project

• BASE_BURDENED_COST_PPBase burdened cost for prior GL or PA period

• BASE_BURDENED_COST_PTDPeriod to date base burdened cost for PA or GL period

• ORIG_RAW_COST_ITDInception to date original raw cost for project

• ORIG_RAW_COST_YTDYear to date original raw cost for project



• ORIG_RAW_COST_PPOriginal raw cost for prior GL or PA period

• ORIG_RAW_COST_PTDPeriod to date original raw cost for PA or GL period

• ORIG_BURDENED_COST_ITDInception to date original burdened cost for project

• ORIG_BURDENED_COST_YTDYear to date original burdened cost project

• ORIG_BURDENED_COST_PPOriginal burdened cost for prior GL or PA period

• ORIG_BURDENED_COST_PTDPeriod to date original burdened cost for PA or GL period

• BASE_REVENUE_ITDInception to date base revenue for project

• BASE_REVENUE_YTDYear to date base revenue project

• BASE_REVENUE_PPBase revenue for prior GL or PA period

• BASE_REVENUE_PTDPeriod to date base revenue for PA or GL period

• ORIG_REVENUE_ITDInception to date original revenue for project

• ORIG_REVENUE_YTDYear to date original revenue for project

• ORIG_REVENUE_PPOriginal revenue for prior GL or PA period

• ORIG_REVENUE_PTDPeriod to date original revenue for PA or GL period

• ORIG_LABOR_HOURS_ITDInception to date original labor hours for project

• ORIG_LABOR_HOURS_YTDYear to date original labor hours for project

• ORIG_LABOR_HOURS_PP



Original labor hours for prior GL or PA period• ORIG_LABOR_HOURS_PTD

Period to date original labor hours for PA or GL period• BASE_LABOR_HOURS_ITD

Inception to date base labor hours for project• BASE_LABOR_HOURS_YTD

Year to date base labor hours for project• BASE_LABOR_HOURS_PP

Base labor hours for prior GL or PA period• BASE_LABOR_HOURS_PTD

Period to date base labor hours for PA or GL period• ORIG_QUANTITY_YTD

Year to date original quantity for project• ORIG_QUANTITY_ITD

Inception to date original quantity for project• ORIG_QUANTITY_PP

Original quantity for prior GL or PA period• ORIG_QUANTITY_PTD

Period to date original quantity for PA or GL period• BASE_QUANTITY_YTD

Year to date base quantity for project• BASE_QUANTITY_ITD

Inception to date base quantity for project• BASE_QUANTITY_PP

Base quantity for prior GL or PA period• BASE_QUANTITY_PTD

Period to date base quantity for PA or GL period• ORIG_LABOR_HOURS_TOT

Total original labor hours• BASE_LABOR_HOURS_TOT

Total base labor hours• ORIG_QUANTITY_TOT

Total original quantity• BASE_QUANTITY_TOT



Total base quantity• BASE_RAW_COST_TOT

Total base raw cost• BASE_BURDENED_COST_TOT

Total base burdened cost• ORIG_RAW_COST_TOT

Total original raw cost• ORIG_BURDENED_COST_TOT

Total original burdened cost• BASE_REVENUE_TOT

Total base revenue• ORIG_REVENUE_TOT

Total original revenue• SET_OF_BOOKS_ID

The identifier of the General Ledger set of books used by Oracle Projects. It represents Set Of Books in release 11i and Ledgers in R12 - foreign key to SET_OF_BOOKS dimension.



• CREATION_DATECreation date and time from PA_PROJECT_ACCUM_HEADERS - foreign key to TIME_DIM dimension



Subject AreasProject Summary Section3
Analysis
With the tables in this section, you can analyze budget summary data along several dimensions including:• By organization• By project• By task• By resource• By budget type• By date and period (fiscal and project-specific)You can combine the budget summary table, BUDGET_SUMMARY_FACT, with other components in this Rapid Mart:• Compare with actual values in PROJECT_SUMMARY_FACTTypical queries include:• What are the revenue, cost, and margin on projects compared to the

budget?• How does forecast project profitability compare to the budget?• What is the forecast profitability of projects in my organizations?

Project Summary SectionThe Project Summary section of this Rapid Mart contains summarized inception-to-date, year-to-date, period-to-date and prior period project data.

Oracle Applications processingOracle Applications provides a number of summary tables that hold accumulated data to simplify reporting and analysis especially when comparing against previous periods.This includes a table containing accumulated project data, PA_PROJECT_ACCUM_ACTUALS along with a header table PA_PROJECT_ACCUM_HEADERS.These tables are not maintained automatically. Instead a batch process (PRC: Refresh Project Summary Amounts) must be run to populate these tables.


Subject AreasProject Summary Section 3

Rapid Mart processingThe Rapid Mart selects all accumulated project data from the source tables specified above and loads them into the PROJECT_SUMMARY_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, accumulated project entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.

Rapid Mart dataThe following diagram shows the tables that the Project Summary section extracts.

Fact table columnsThe project summary fact table contains transaction measures and attributes. The columns in the table are described below.• PROJECT_ACCUM_ID

The identifier of accumulation header for which this line was created• ORG_ID

Operating unit identifier for multi-organization installations - foreign key to ORGANIZATION dimension



• PROJECT_IDThe identifier of project for which the header was created - foreign key to PROJECT dimension

• TASK_IDThe identifier of task for which the header was created - foreign key to TASK dimension

• PERIOD_SET_NAME, GL_PERIOD_NAMEAccounting calendar name. Last accumulation GL Period - foreign key to PERIOD_CALENDAR

• PERIOD_NAME, ORG_IDLast accumulation GL or PA period, depending on the imp. option - foreign key to PERIOD_CALENDAR or PROJECT_PERIOD dimension

• RESOURCE_IDThe identifier of resource for which the header was created - foreign key to PROJECT_RESOURCE dimension

• RAW_COST_ITDInception to date raw cost for project

• RAW_COST_YTDYear to date raw cost for project

• RAW_COST_PPRaw cost for prior GL or PA period

• RAW_COST_PTDPeriod to date raw cost for PA or GL period

• BILLABLE_RAW_COST_ITDInception to date billable raw cost for project

• BILLABLE_RAW_COST_YTDYear to date billable raw cost for project

• BILLABLE_RAW_COST_PPBillable raw cost for prior GL or PA period

• BILLABLE_RAW_COST_PTDPeriod to date billable raw cost for PA or GL period

• BURDENED_COST_ITDInception to date burdened cost for project

• BURDENED_COST_YTDYear to date burdened cost for project



• BURDENED_COST_PPBurdened cost for prior GL or PA period

• BURDENED_COST_PTDPeriod to date burdened cost for PA or GL period

• BILLABLE_BURDENED_COST_ITDInception to date billable burdened cost for project

• BILLABLE_BURDENED_COST_YTDYear to date billable burdened cost for project

• BILLABLE_BURDENED_COST_PPBillable burdened cost for prior GL or PA period

• BILLABLE_BURDENED_COST_PTDPeriod to date billable burdened cost for PA or GL period

• QUANTITY_ITDInception to date quantity for project

• QUANTITY_YTDYear to date quantity for project

• QUANTITY_PPQuantity for prior GL or PA period

• QUANTITY_PTDPeriod to date quantity for PA or GL period

• LABOR_HOURS_ITDInception to date labor hours for project

• LABOR_HOURS_YTDYear to date labor hours for project

• LABOR_HOURS_PPLabor hours for prior GL or PA period

• LABOR_HOURS_PTDPeriod to date labor hours for PA or GL period

• BILLABLE_QUANTITY_ITDInception to date billable quantity for project

• BILLABLE_QUANTITY_YTDYear to date billable quantity for project

• BILLABLE_QUANTITY_PP



Billable quantity for prior GL or PA period• BILLABLE_QUANTITY_PTD

Period to date billable quantity for PA or GL period• BILLABLE_LABOR_HOURS_ITD

Inception to date billable labor hours for project• BILLABLE_LABOR_HOURS_YTD

Year to date billable labor hours for project• BILLABLE_LABOR_HOURS_PP

Billable labor hours for prior GL or PA period• BILLABLE_LABOR_HOURS_PTD

Period to date billable labor hours for PA or GL period• REVENUE_ITD

Inception to date revenue for the project• REVENUE_YTD

Year to date revenue for project• REVENUE_PP

Prior GL or PA period revenue for the project• REVENUE_PTD

Period to date revenue for the project• SET_OF_BOOKS_ID




• CREATION_DATEProject Actuals Accum Creation Date - foreign key to TIME_DIM dimension

• LOAD_DATE and LOAD_TIME



The Rapid Mart populates these fields with the date and time of the start of the data extraction from Oracle Applications. For Oracle, the Rapid Mart stores the date as a string in the format: 'YYYY.MM.DD HH24:MI:SS'. For other target databases, the Rapid Mart stores the date as a string in the format: 'YYYY.MM.DD'. Similarly, the Rapid Mart stores the time in an 8-character string appropriate for your target database. LOAD_DATE and LOAD_TIME can be helpful when using the fact tables in other applications for further data manipulation.

AnalysisWith the tables in this section, you can analyze summarized project data along several dimensions including:• By organization• By project• By task• By resource• By date and period (fiscal and project-specific)You can combine the project summary table, PROJECT_SUMMARY_FACT, with other components in this Rapid Mart:• Compare against budget and/or forecast data in

BUDGET_SUMMARY_FACT.Typical queries include:• How profitable are the projects in my organizations?• How does project profitability compare to the budget?• How does project profitability compare to last year or the previous

period?• What is the growth trend in revenue and margin compared to last year?


Subject AreasProject Transaction Summary Section3
Project Transaction Summary Section
The Project Transaction Summary section of this Rapid Mart contains summarized project data at the lowest level of detail.

Oracle Applications processingOracle Applications provides a number of summary tables that hold accumulated data to simplify reporting and analysis especially when comparing against previous periods.This includes a table containing accumulated project data at the lowest level of detail, PA_TXN_ACCUM.This table is not maintained automatically. Instead a batch process (PRC: Refresh Transaction Summary Amounts) must be run to populate these tables.

Rapid Mart processingThe Rapid Mart selects all accumulated project transaction data from PA_TXN_ACCUM and loads it into the PROJECT_TXN_SUMMARY_FACT target table.The extraction process is the same for both initial and incremental loads and the last updated date field is used to filter the records. During incremental loads, using the table comparison feature, accumulated project transaction entries are first checked against the target table to determine if they exist and have changed in which case the record is updated in the target table. All new entries, as for the initial load, are simply inserted into the target table.


Subject AreasProject Transaction Summary Section 3

Rapid Mart dataThe following diagram shows the tables that the Project Transaction Summary section extracts.

Fact table columnsThe project transaction summary fact table contains transaction measures and attributes. The columns in the table are described below.• TXN_ACCUM_ID

The identifier uniquely identifies txns that were groups of accumulated txns

• ORG_IDThe identifier of the organization for which accumulation is done - foreign key to ORGANIZATION dimension

• PROJECT_IDIdentifier of project for the accumulated txn - foreign key to PROJECT dimension

• TASK_IDIdentifier of task for the accumulated txn - foreign key to TASK dimension

• PERSON_ID



The identifier of the person for which accumulation is done - foreign key to CURRENT_PEOPLE dimension

• JOB_IDThe identifier of the job for which accumulation is done - foreign key to JOB dimension.

• VENDOR_IDThe identifier of the supplier for which accumulation is done - foreign key to VENDOR dimension

• NON_LABOR_RESOURCE_ORG_IDNon labor resource organization id of the accumulated txn - foreign key to ORGANIZATION dimension

• PERIOD_NAME, ORG_IDPA period name of the accumulated txn - foreign key to PROJECT_PERIOD dimension

• PERIOD_SET_NAME, GL_PERIOD_NAMEAccounting calendar name; GL period name of the accumulated txn - foreign key to PERIOD_CALENDAR dimension

• MONTH_ENDING_DATEMonth ending date for the accumulated transaction

• WEEK_ENDING_DATEWeek ending date for the accumulated transaction

• EXPENDITURE_TYPE_IDExpenditure type ID of the accumulated txn - foreign key to EXPENDITURE_TYPE dimension

• EVENT_TYPE_ID - foreign key to EVENT_TYPE dimensionEvent type ID of the accumulated txn

• NON_LABOR_RESOURCEExpenditure category of the accumulated txn

• EXPENDITURE_CATEGORYExpenditure category of the accumulated txn

• REVENUE_CATEGORYRevenue category of the accumulated txn

• EVENT_TYPE_CLASSIFICATIONEvent type classification of the accumulated txn

• ACTUAL_COST_ROLLUP_FLAG



Indicates if the actual cost is rolled up to pa_project_accum_actuals• REVENUE_ROLLUP_FLAG

Indicates if the revenue is rolled up to pa_project_accum_actuals• CMT_ROLLUP_FLAG

Indicates if the commitment are rolled up to pa_project_accum_commitments

• UNIT_OF_MEASUREUnit of measure for commitments or actual cost

• TOT_REVENUETotal revenue amount

• TOT_RAW_COSTTotal Raw cost amount

• TOT_BURDENED_COSTTotal Burdened cost amount

• TOT_QUANTITYTotal quantity amount

• TOT_LABOR_HOURSTotal labor hours amount

• TOT_BILLABLE_RAW_COSTTotal billable raw cost amount

• TOT_BILLABLE_BURDENED_COSTTotal billable burdened cost amount

• TOT_BILLABLE_QUANTITYTotal billable quantity amount

• TOT_BILLABLE_LABOR_HOURSTotal billable labor hours amount

• TOT_CMT_RAW_COSTTotal commitment raw cost amount

• TOT_CMT_BURDENED_COSTTotal commitment burdened cost amount

• TOT_CMT_QUANTITYTotal commitment quantity amount

• I_TOT_REVENUEAlso stores future period revenue amount



• I_TOT_RAW_COSTAlso stores future period raw cost amount

• I_TOT_BURDENED_COSTAlso stores future period burdened cost amount

• I_TOT_QUANTITYAlso stores future period quantity

• I_TOT_LABOR_HOURSAlso stores future period labor hours

• I_TOT_BILLABLE_RAW_COSTAlso stores future period billable raw cost

• I_TOT_BILLABLE_BURDENED_COSTAlso stores future period billable burdened cost

• I_TOT_BILLABLE_QUANTITYAlso stores future period billable quantity

• I_TOT_BILLABLE_LABOR_HOURSAlso stores future period billable labor hours

• COST_IND_COMPILED_SET_IDIndirect compiled set id used for calculating burdened cost

• REV_IND_COMPILED_SET_IDIndirect compiled set id used for calculating revenue

• INV_IND_COMPILED_SET_IDIndirect compiled set id used for calculating invoice

• CMT_IND_COMPILED_SET_IDIndirect compiled set used for calculating burdened cost for commitments



• CURRENCY_CODE_PRJ



Currency code of the project - foreign key to CURRENCY dimension• CREATION_DATE

Project Txn summary creation date and time - foreign key to TIME_DIM dimension


AnalysisWith the tables in this section, you can analyze summarized project transaction data along several dimensions including:• By organization• By project• By task• By job• By person• By vendor• By expenditure type• By event type• By date and period (fiscal and project-specific)You can combine the reservation table, PROJECT_TXN_SUMMARY_FACT, with other components in this Rapid Mart:• Verify the integrity of the data by checking against totals held in the

detailed tables such as EXPENDITURE_FACT.Typical queries include:• What are the detailed costs on projects for the period?• Analyze total labor hours by resource




Reports

chapter

ReportsOverview4
Overview
You can use the BusinessObjects Projects Rapid Mart for Oracle Applications to perform ad hoc analysis and produce many kinds of reports. This chapter provides examples of reports you could generate using the Oracle Apps Projects universe. The information in this chapter is useful for those who design reporting solutions for analysis of data in the Projects module of Oracle Applications.

This chapter shows some sample reports and the recommended joins for each section in the Rapid Mart, including:• Budget Line Section• Expenditure Section• Event Section• Project Asset Section• Budget Summary Section• Project Summary Section• Project Transaction Summary SectionView additional details on the Rapid Mart Code Combination Account Hierarchies, including:• Hierarchy Data Discovery• Account Segment Dimensions - Recommended JoinsNote that all report SQL is located in the Rapid Mart installation directory under "\Sample\DDL".


ReportsBudget Line Section 4

Budget Line SectionThe Budget Line section of this Rapid Mart stores estimated cost, revenue, labor hours and other quantities for a project and task categorized by a resource.

Budget Line AnalysisDisplays overall budget revenue and costs (burden and raw) for a specific Organization, budget version and list of year periods.

Budget Revenue AnalaysisView budget revenue amounts for all projects within an Organization grouped by Project Class Category.


ReportsBudget Line Section4

Budget Cost AnalysisView budget revenue amounts for all projects within an Organization grouped by Project Class Category.

Report SQLSELECT DISTINCT MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, sum(BUDGET_LINE_FACT.REVENUE), sum(BUDGET_LINE_FACT.BURDENED_COST), BUDGET_LINE_FACT.LINE_DESCRIPTION, BUDGET_LINE_FACT.CURRENCY_CODE_PRJ, BUDGET_TYPE.BUDGET_TYPE, BUDGET_LINE_FACT.VERSION_NAME, BUDGET_LINE_FACT.REVENUE_CATEGORY, sum(BUDGET_LINE_FACT.BORROWED_REVENUE),



sum(BUDGET_LINE_FACT.REVENUE_ADJ), sum(BUDGET_LINE_FACT.RAW_COST), sum(BUDGET_LINE_FACT.COST_ADJ), sum(BUDGET_LINE_FACT.LENT_RESOURCE_COST), CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN

PERIOD_CALENDAR.PERIOD_YEAR || ' - 0' || PERIOD_CALENDAR.PERIOD_NUMBER ELSE PERIOD_CALENDAR.PERIOD_YEAR || ' - ' || PERIOD_CALENDAR.PERIOD_NUMBER END,

PROJECT.PROJ_TYPE_CODE, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORYFROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, BUDGET_LINE_FACT, BUDGET_TYPE, PERIOD_CALENDAR, PROJECT_CLASS_CATEGORYWHERE (

BUDGET_LINE_FACT.BUDGET_TYPE_CODE=BUDGET_TYPE.BUDGET_TYPE_CODE )

AND ( MAIN_ORGANIZATION.ORG_ID=BUDGET_LINE_FACT.ORG_ID ) AND (

PERIOD_CALENDAR.PERIOD_SET_NAME=BUDGET_LINE_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=BUDGET_LINE_FACT.GL_PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=BUDGET_LINE_FACT.PROJECT_ID ) AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID ) AND ( BUDGET_TYPE.BUDGET_TYPE In ( 'Approved Revenue Budget','Approved Cost

Budget' ) AND MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization

Name:','A','Organization\Organization Name',Mono,Free,Persistent,,User:0) AND BUDGET_LINE_FACT.VERSION_NAME = @prompt('Version

Name:','A','BUDGET LINE FACT\Version Name',Mono,Free,Persistent,,User:1) AND CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN

PERIOD_CALENDAR.PERIOD_YEAR || ' - 0' || PERIOD_CALENDAR.PERIOD_NUMBER ELSE PERIOD_CALENDAR.PERIOD_YEAR || ' - ' || PERIOD_CALENDAR.PERIOD_NUMBER END In @prompt('Year Period(s):','A','PERIOD CALENDAR\Year Period',Multi,Free,Persistent,,User:2)

)GROUP BY MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME,



PROJECT.PROJECT_DESC, BUDGET_LINE_FACT.LINE_DESCRIPTION, BUDGET_LINE_FACT.CURRENCY_CODE_PRJ, BUDGET_TYPE.BUDGET_TYPE, BUDGET_LINE_FACT.VERSION_NAME, BUDGET_LINE_FACT.REVENUE_CATEGORY, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PROJECT.PROJ_TYPE_CODE, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY

Recommended table joins When analyzing data from the budget line section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the BUDGET_LINE_FACT table and other dimension tables in the Rapid Mart.

Fact Table Dimension Table Join Condition

BUDGET_LINE_FACT BUDGET_TYPE BUDGET_LINE_FACT.BUDGET_TYPE_CODE=BUDGET_TYPE.BUDGET_TYPE_CODE

BUDGET_LINE_FACT CODE_COMBINATION BUDGET_LINE_FACT.CODE_COMBINATION_ID=CODE_COMBINATION.CODE_COMBINATION_ID

BUDGET_LINE_FACT CURRENCY BUDGET_LINE_FACT.CURRENCY_CODE_PRJ = CURRENCY.CURRENCY_CODE

BUDGET_LINE_FACT CURRENT_PEOPLE BUDGET_LINE_FACT.BASELINED_BY_PERSON_ID = CURRENT_PEOPLE.PERSON_ID

BUDGET_LINE_FACT EVENT_TYPE BUDGET_LINE_FACT.EVENT_TYPE_ID=EVENT_TYPE.EVENT_TYPE_ID

BUDGET_LINE_FACT EXPENDITURE_TYPE BUDGET_LINE_FACT.EXPENDITURE_TYPE_ID=EXPENDITURE_TYPE.EXPENDITURE_TYPE_ID

BUDGET_LINE_FACT JOB BUDGET_LINE_FACT.JOB_ID=JOB.JOB_ID



BUDGET_LINE_FACT ORG_PRIMARY_HIER_HZ

BUDGET_LINE_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and BUDGET_LINE_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER

BUDGET_LINE_FACT ORG_PRIMARY_HIER_VR

BUDGET_LINE_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and BUDGET_LINE_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER

BUDGET_LINE_FACT ORG_STRUCTURE BUDGET_LINE_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and BUDGET_LINE_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and BUDGET_LINE_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID

BUDGET_LINE_FACT ORGANIZATION BUDGET_LINE_FACT.NON_LABOR_RESOURCE_ORG_ID = ORGANIZATION.ORG_ID

BUDGET_LINE_FACT ORGANIZATION BUDGET_LINE_FACT.ORG_ID = ORGANIZATION.ORG_ID

BUDGET_LINE_FACT PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=BUDGET_LINE_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=BUDGET_LINE_FACT.GL_PERIOD_NAME

BUDGET_LINE_FACT PROJECT PROJECT.PROJECT_ID=BUDGET_LINE_FACT.PROJECT_ID

BUDGET_LINE_FACT PROJECT_AGREEMENT

PROJECT_AGREEMENT.AGREEMENT_ID=BUDGET_LINE_FACT.AGREEMENT_ID

BUDGET_LINE_FACT PROJECT_CLASS_CATEGORY

PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID




BUDGET_LINE_FACT PROJECT_PERIOD PROJECT_PERIOD.ORG_ID=BUDGET_LINE_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=BUDGET_LINE_FACT.PERIOD_NAME

BUDGET_LINE_FACT REVENUE_CATEGORY

BUDGET_LINE_FACT.REVENUE_CATEGORY=REVENUE_CATEGORY.REV_CATEGORY_CODE

BUDGET_LINE_FACT SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=BUDGET_LINE_FACT.SET_OF_BOOKS_ID

BUDGET_LINE_FACT TASK BUDGET_LINE_FACT.TASK_ID=TASK.TASK_ID

BUDGET_LINE_FACT TASK_HIER_HZ BUDGET_LINE_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID

BUDGET_LINE_FACT TASK_HIER_VR BUDGET_LINE_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID

BUDGET_LINE_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=BUDGET_LINE_FACT.CREATION_DATE

BUDGET_LINE_FACT VENDOR BUDGET_LINE_FACT.VENDOR_ID=VENDOR.VENDOR_ID



ReportsBudget Summary Section 4

Budget Summary SectionThe Budget Summary section of this Rapid Mart contains summarized inception-to-date, year-to-date, period-to-date and prior period budget data.

Budget Summary AnalysisBudget Summary analyis of an organization for a specified (Project Period) Calendar Year. View YTD budget data by Project Class Category, Resource, or Task.

by Project Class CategoryAnalyze project budget YTD amounts by Project Class Category.


ReportsBudget Summary Section4

by Project ResourceAnalyze project budget YTD amounts by Project Resource.



by Project TaskAnalyze project budget YTD amounts by Task.

Calculations• % Mix Base Burdened Cost YTD = Percentage([Base Burdened Cost Ytd

PRJ])• % Mix Base Revenue Ytd PRJ = Percentage([Base Revenue Ytd PRJ])


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, sum(BUDGET_SUMMARY_FACT.BASE_RAW_COST_YTD), sum(BUDGET_SUMMARY_FACT.BASE_BURDENED_COST_YTD), BUDGET_TYPE.BUDGET_TYPE, PROJECT_PERIOD.PERIOD_NAME, PROJECT_PERIOD.START_DATE, PROJECT_RESOURCE.PROJECT_RESOURCE, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY,



sum(BUDGET_SUMMARY_FACT.BASE_REVENUE_YTD), sum(BUDGET_SUMMARY_FACT.BASE_LABOR_HOURS_YTD), BUDGET_SUMMARY_FACT.CURRENCY_CODE_PRJ, TASK.TASK_NAME, PROJECT_PERIOD.CALENDAR_YEARFROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, BUDGET_SUMMARY_FACT, BUDGET_TYPE, PROJECT_PERIOD, PROJECT_RESOURCE, PROJECT_CLASS_CATEGORY, TASKWHERE ( MAIN_ORGANIZATION.ORG_ID=BUDGET_SUMMARY_FACT.ORG_ID ) AND ( PROJECT.PROJECT_ID=BUDGET_SUMMARY_FACT.PROJECT_ID ) AND (

BUDGET_TYPE.BUDGET_TYPE_CODE=BUDGET_SUMMARY_FACT.BUDGET_TYPE_CODE )

AND ( PROJECT_RESOURCE.RESOURCE_ID=BUDGET_SUMMARY_FACT.RESOURCE_ID )

AND ( TASK.TASK_ID=BUDGET_SUMMARY_FACT.TASK_ID ) AND ( PROJECT_PERIOD.ORG_ID=BUDGET_SUMMARY_FACT.ORG_ID and

PROJECT_PERIOD.PERIOD_NAME=BUDGET_SUMMARY_FACT.PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID ) AND ( MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization

Name:','A','Organization\Organization Name',Mono,Free,Persistent,,User:0) AND BUDGET_TYPE.BUDGET_TYPE In ( 'Approved Revenue Budget','Approved Cost

Budget' ) AND PROJECT_PERIOD.CALENDAR_YEAR = @prompt('Calendar Year:','N','PROJECT

PERIOD\Calendar Year',Mono,Free,Persistent,,User:1) )GROUP BY MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, BUDGET_TYPE.BUDGET_TYPE, PROJECT_PERIOD.PERIOD_NAME, PROJECT_PERIOD.START_DATE, PROJECT_RESOURCE.PROJECT_RESOURCE, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, BUDGET_SUMMARY_FACT.CURRENCY_CODE_PRJ, TASK.TASK_NAME, PROJECT_PERIOD.CALENDAR_YEAR



Recommended table joinsWhen analyzing data from the budget summary section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the BUDGET_SUMMARY_FACT table and other dimension tables in the Rapid Mart.


BUDGET_SUMMARY_FACT

BUDGET_TYPE BUDGET_TYPE.BUDGET_TYPE_CODE=BUDGET_SUMMARY_FACT.BUDGET_TYPE_CODE

BUDGET_SUMMARY_FACT

ORG_PRIMARY_HIER_HZ

BUDGET_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and BUDGET_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER

BUDGET_SUMMARY_FACT

ORG_PRIMARY_HIER_VR

BUDGET_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and BUDGET_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER

BUDGET_SUMMARY_FACT

ORG_STRUCTURE BUDGET_SUMMARY_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and BUDGET_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and BUDGET_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID

BUDGET_SUMMARY_FACT

TASK_HIER_HZ BUDGET_SUMMARY_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID

BUDGET_SUMMARY_FACT

TASK_HIER_VR BUDGET_SUMMARY_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID

BUDGET_SUMMARY_FACT

CURRENCY CURRENCY_PRJ.CURRENCY_CODE=BUDGET_SUMMARY_FACT.CURRENCY_CODE_PRJ

BUDGET_SUMMARY_FACT

ORGANIZATION ORGANIZATION.ORG_ID=BUDGET_SUMMARY_FACT.ORG_ID



BUDGET_SUMMARY_FACT

PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=BUDGET_SUMMARY_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=BUDGET_SUMMARY_FACT.GL_PERIOD_NAME

BUDGET_SUMMARY_FACT

PROJECT PROJECT.PROJECT_ID=BUDGET_SUMMARY_FACT.PROJECT_ID

BUDGET_SUMMARY_FACT

PROJECT_CLASS_CATEGORY


BUDGET_SUMMARY_FACT

PROJECT_PERIOD PROJECT_PERIOD.ORG_ID=BUDGET_SUMMARY_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=BUDGET_SUMMARY_FACT.PERIOD_NAME

BUDGET_SUMMARY_FACT

PROJECT_RESOURCE

PROJECT_RESOURCE.RESOURCE_ID=BUDGET_SUMMARY_FACT.RESOURCE_ID

BUDGET_SUMMARY_FACT

SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=BUDGET_SUMMARY_FACT.SET_OF_BOOKS_ID

BUDGET_SUMMARY_FACT

TASK TASK.TASK_ID=BUDGET_SUMMARY_FACT.TASK_ID

BUDGET_SUMMARY_FACT

TIME_DIM TIME_DIM.CALENDAR_DATE=BUDGET_SUMMARY_FACT.CREATION_DATE



ReportsExpenditure Section 4

Expenditure SectionThe Expenditure section of this Rapid Mart contains summary and details of expenditure items incurred by an employee or organization. The Rapid Mart captures project expenditure distributions for Cost and Revenue separately for analysis.

Expenditure CostExpenditure cost contains only project cost distributions (raw cost, burden cost, and labor hours). Many types of analysis can be performed using this data. This Rapid Mart provides one sample report

Expenditure Cost Trend AnalysisView trend analysis of project expenditure costs over a desired Year-Period range by Project, Project Class Category, and GL Distribution Account for the selected parent account.

Expenditure Cost SummaryView mix of expenditure costs by project and task.


ReportsExpenditure Section4

Expenditure Cost TrendsView cost trends for the selected period by Project Class and Project.



Account Dist TrendView cost trends for the selected period by account distribution and project (level 0 and leve 1 accounts shown).

Calculations• % Mix = If([Project Burdened Cost PRJ]<> 0; [Project Raw Cost PRJ]/

[Project Burdened Cost PRJ]; 0)• Burdened Cost = [Project Burdened Cost PRJ]*[Numeric Scaling Factor]



• Raw Cost =[Project Raw Cost PRJ]*[Numeric Scaling Factor]• Sum Burdened Cost = Sum([Project Burdened Cost PRJ]*[Numeric

Scaling Factor])


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, TASK.TASK_NAME, TIME_DIM.CALENDAR_YEAR, sum(EXPENDITURE_COST_FACT.PROJECT_BURDENED_COST), sum(EXPENDITURE_COST_FACT.PROJECT_RAW_COST), COST_DISTRIBUTION_TYPE.COST_DIST_TYPE_NAME, TRANSFER_STATUS.TRANSFER_STATUS_NAME, EXPENDITURE_COST_FACT.PROJECT_CURRENCY_CODE, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


COA_ACCOUNT_HZ.LVL_0_ACCOUNT_CODE || ' - ' || COA_ACCOUNT_HZ.LVL_0_ACCOUNT_DESC,


COA_ACCOUNT_HZ.LVL_2_ACCOUNT_CODE || ' - ' || COA_ACCOUNT_HZ.LVL_2_ACCOUNT_DESC

FROM PERIOD_CALENDAR, EXPENDITURE_COST_FACT, TIME_DIM, ORGANIZATION MAIN_ORGANIZATION, PROJECT, TASK, PROJECT_CLASS_CATEGORY, CODE_COMBINATION, TRANSFER_STATUS, COST_DISTRIBUTION_TYPE, COA_ACCOUNT_HZWHERE (

PERIOD_CALENDAR.PERIOD_SET_NAME=EXPENDITURE_COST_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=EXPENDITURE_COST_FACT.GL_PERIOD_NAME )

AND ( TIME_DIM.CALENDAR_DATE=EXPENDITURE_COST_FACT.CREATION_DATE )



AND ( MAIN_ORGANIZATION.ORG_ID=EXPENDITURE_COST_FACT.ORG_ID )

AND ( PROJECT.PROJECT_ID=EXPENDITURE_COST_FACT.PROJECT_ID ) AND ( EXPENDITURE_COST_FACT.TASK_ID=TASK.TASK_ID ) AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID ) AND (

EXPENDITURE_COST_FACT.CODE_COMBINATION_ID=CODE_COMBINATION.CODE_COMBINATION_ID )

AND ( EXPENDITURE_COST_FACT.TRANSFER_STATUS_CODE=TRANSFER_STATUS.TRANSFER_STATUS_CODE )

AND ( EXPENDITURE_COST_FACT.COST_DIST_LINE_TYPE=COST_DISTRIBUTION_TYPE.COST_DIST_LINE_TYPE )

AND ( CODE_COMBINATION.CHART_OF_ACCT_ID=COA_ACCOUNT_HZ.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_ACCOUNT_HZ.ACCOUNT_CODE )

AND ( ( COA_ACCOUNT_HZ.LVL_0_ACCOUNT_CODE in @Prompt('Select Multiple

Parent Accounts for Group','A','Coa Account Hz\Account Level 0 Code',multi,free) ) AND MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization

Name:','A','Organization\Organization Name',Mono,Free,Persistent,,User:0) AND CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN

PERIOD_CALENDAR.PERIOD_YEAR || ' - 0' || PERIOD_CALENDAR.PERIOD_NUMBER ELSE PERIOD_CALENDAR.PERIOD_YEAR || ' - ' || PERIOD_CALENDAR.PERIOD_NUMBER END BETWEEN @prompt('Year Period (Start):','A','PERIOD CALENDAR\Year Period',Mono,Free,Persistent,,User:1) AND @prompt('Year Period (End):','A','PERIOD CALENDAR\Year Period',Mono,Free,Persistent,,User:2)


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, TASK.TASK_NAME, TIME_DIM.CALENDAR_YEAR, COST_DISTRIBUTION_TYPE.COST_DIST_TYPE_NAME, TRANSFER_STATUS.TRANSFER_STATUS_NAME, EXPENDITURE_COST_FACT.PROJECT_CURRENCY_CODE, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN






COA_ACCOUNT_HZ.LVL_2_ACCOUNT_CODE || ' - ' || COA_ACCOUNT_HZ.LVL_2_ACCOUNT_DESC

Recommended table joins When analyzing data from the budget line section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the EXPENDITURE_COST_FACT table and other dimension tables in the Rapid Mart.


EXPENDITURE_COST_FACT

CURRENCY CURRENCY.CURRENCY_CODE=EXEPENDITURE_COST_FACT.PROJECT_CURRENCY_CODE


CURRENCY CURRENCY.CURRENCY_CODE=EXPENDITURE_COST_FACT.ACCT_CURRENCY_CODE


CURRENCY CURRENCY.CURRENCY_CODE=EXPENDITURE_COST_FACT.DENOM_CURRENCY_CODE


CURRENCY CURRENCY.CURRENCY_CODE=EXPENDITURE_COST_FACT.PROJFUNC_CURRENCY_CODE


CODE_COMBINATION EXPENDITURE_COST_FACT.CODE_COMBINATION_ID=CODE_COMBINATION.CODE_COMBINATION_ID


COST_DISTRIBUTION_TYPE

EXPENDITURE_COST_FACT.COST_DIST_LINE_TYPE=COST_DISTRIBUTION_TYPE.COST_DIST_LINE_TYPE


ORG_PRIMARY_HIER_HZ

EXPENDITURE_COST_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and EXPENDITURE_COST_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER




ORG_PRIMARY_HIER_VR

EXPENDITURE_COST_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and EXPENDITURE_COST_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER


ORG_STRUCTURE EXPENDITURE_COST_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and EXPENDITURE_COST_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and EXPENDITURE_COST_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID


TASK EXPENDITURE_COST_FACT.TASK_ID=TASK.TASK_ID


TASK_HIER_HZ EXPENDITURE_COST_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID


TASK_HIER_VR EXPENDITURE_COST_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID


TRANSFER_STATUS EXPENDITURE_COST_FACT.TRANSFER_STATUS_CODE=TRANSFER_STATUS.TRANSFER_STATUS_CODE


ORGANIZATION ORGANIZATION.ORG_ID=EXPENDITURE_COST_FACT.ORG_ID


PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=EXPENDITURE_COST_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=EXPENDITURE_COST_FACT.GL_PERIOD_NAME


PROJECT PROJECT.PROJECT_ID=EXPENDITURE_COST_FACT.PROJECT_ID








PROJECT_PERIOD PROJECT_PERIOD.ORG_ID=EXPENDITURE_COST_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=EXPENDITURE_COST_FACT.PERIOD_NAME


PROJECT_PERIOD PROJECT_PERIOD.ORG_ID=EXPENDITURE_COST_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=EXPENDITURE_COST_FACT.RECVR_PA_PERIOD_NAME


SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=EXPENDITURE_COST_FACT.SET_OF_BOOKS_ID


TIME_DIM TIME_DIM.CALENDAR_DATE=EXPENDITURE_COST_FACT.CREATION_DATE




Expenditure RevenueExpenditure revenue contains project revenue and associated cost distributions for profit margin analysis.

Expenditure Revenue Trend AnalysisView trend analysis of project expenditure revenue and margin over a desired Year-Period range by Project, Project Class Category, and GL Distribution Account for the selected parent account

Expenditure Revenue SummaryView mix of expenditure revenue by project and task.



Expenditure Revenue TrendsView revenue trends for the selected period by Project Class and Project. View graphical top 10 projects by Revenue and Raw Cost.



Account Dist TrendView revenue trends for the selected period by account distribution and project (level 0 and leve 1 accounts shown).

Calculations• Margin Amount = ([Revenue Amount PRJ]-[Raw Cost Amount

PRJ])*[Numeric Scaling Factor]• Margin % = If([Revenue Amount PRJ] <> 0; ([Revenue Amount PRJ]-

[Raw Cost Amount PRJ])/[Revenue Amount PRJ]; 0)

Report SQLSELECT DISTINCT MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME,



'../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, sum(EXPENDITURE_REV_FACT.PROJECT_REVENUE_AMOUNT), sum(EXPENDITURE_REV_FACT.RAW_COST), EXPENDITURE_REV_FACT.PROJECT_CURRENCY_CODE, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, TASK.TASK_NAME, TIME_DIM.CALENDAR_YEAR, COA_ACCOUNT_HZ.LVL_0_ACCOUNT_CODE || ' - ' ||

COA_ACCOUNT_HZ.LVL_0_ACCOUNT_DESC,COA_ACCOUNT_HZ.LVL_1_ACCOUNT_CODE || ' - ' ||

COA_ACCOUNT_HZ.LVL_1_ACCOUNT_DESC, COA_ACCOUNT_HZ.LVL_2_ACCOUNT_CODE || ' - ' ||

COA_ACCOUNT_HZ.LVL_2_ACCOUNT_DESC, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PROJECT.PROJ_TYPE_CODE, COA_ACCOUNT_HZ.LVL_3_ACCOUNT_CODE || ' - ' ||


COA_ACCOUNT_HZ.LVL_4_ACCOUNT_DESCFROM EXPENDITURE_REV_FACT, CODE_COMBINATION, PROJECT, ORGANIZATION MAIN_ORGANIZATION, TASK, PERIOD_CALENDAR, TIME_DIM, PROJECT_CLASS_CATEGORY, COA_ACCOUNT_HZWHERE (

EXPENDITURE_REV_FACT.CODE_COMBINATION_ID=CODE_COMBINATION.CODE_COMBINATION_ID )

AND ( PROJECT.PROJECT_ID=EXPENDITURE_REV_FACT.PROJECT_ID ) AND ( MAIN_ORGANIZATION.ORG_ID=EXPENDITURE_REV_FACT.ORG_ID ) AND ( EXPENDITURE_REV_FACT.TASK_ID=TASK.TASK_ID ) AND (

PERIOD_CALENDAR.PERIOD_SET_NAME=EXPENDITURE_REV_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=EXPENDITURE_REV_FACT.GL_PERIOD_NAME )

AND ( TIME_DIM.CALENDAR_DATE=EXPENDITURE_REV_FACT.CREATION_DATE )

AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID )



AND ( CODE_COMBINATION.CHART_OF_ACCT_ID=COA_ACCOUNT_HZ.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_ACCOUNT_HZ.ACCOUNT_CODE )

AND ( ( COA_ACCOUNT_HZ.LVL_0_ACCOUNT_CODE in @Prompt('Select Multiple

Parent Accounts for Group','A','Coa Account Hz\Account Level 0 Code',multi,free) ) AND MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization




Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, EXPENDITURE_REV_FACT.PROJECT_CURRENCY_CODE, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, TASK.TASK_NAME, TIME_DIM.CALENDAR_YEAR, COA_ACCOUNT_HZ.LVL_0_ACCOUNT_CODE || ' - ' ||



COA_ACCOUNT_HZ.LVL_2_ACCOUNT_DESC, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PROJECT.PROJ_TYPE_CODE, COA_ACCOUNT_HZ.LVL_3_ACCOUNT_CODE || ' - ' ||


COA_ACCOUNT_HZ.LVL_4_ACCOUNT_DESC


Recommended table joins
When analyzing data from the budget line section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the EXPENDITURE_REV_FACT table and other dimension tables in the Rapid Mart.


EXPENDITURE_REV_FACT

CODE_COMBINATION EXPENDITURE_REV_FACT.CODE_COMBINATION_ID=CODE_COMBINATION.CODE_COMBINATION_ID


CURRENCY CURRENCY.CURRENCY_CODE=EXPENDITURE_REV_FACT.BILL_TRANS_CURRENCY_CODE


CURRENCY CURRENCY.CURRENCY_CODE=EXPENDITURE_REV_FACT.PROJECT_CURRENCY_CODE


CURRENCY CURRENCY.CURRENCY_CODE=EXPENDITURE_REV_FACT.PROJFUNC_CURRENCY_CODE


DRAFT_INVOICE "EXPENDITURE_REV_FACT.PROJECT_ID=DRAFT_INVOICE.PROJECT_ID and EXPENDITURE_REV_FACT.DRAFT_INVOICE_NUM=DRAFT_INVOICE.DRAFT_INVOICE_NUM and EXPENDITURE_REV_FACT.DRAFT_INVOICE_ITEM_LINE_NUM=DRAFT_INVOICE.LINE_NUM

NOTE: DRAFT_INVOICE is a derived table in the Universe. See the Universe chapter for details.




DRAFT_REVENUE "EXPENDITURE_REV_FACT.PROJECT_ID=DRAFT_REVENUE.PROJECT_ID and EXPENDITURE_REV_FACT.DRAFT_REVENUE_NUM=DRAFT_REVENUE.DRAFT_REVENUE_NUM and EXPENDITURE_REV_FACT.DRAFT_REVENUE_ITEM_LINE_NUM=DRAFT_REVENUE.LINE_NUM

NOTE: DRAFT_REVENUE is a derived table in the Universe. See the Universe chapter for details."


EXPENDITURE EXPENDITURE_REV_FACT.EXPENDITURE_ITEM_ID=EXPENDITURE.EXPENDITURE_ITEM_IDNOTE: EXPENDITURE is a derived table in the Universe. See the Universe chapter for details.


ORG_PRIMARY_HIER_HZ

EXPENDITURE_REV_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and EXPENDITURE_REV_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER


ORG_PRIMARY_HIER_VR

EXPENDITURE_REV_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and EXPENDITURE_REV_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER


ORG_STRUCTURE EXPENDITURE_REV_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and EXPENDITURE_REV_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and EXPENDITURE_REV_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID





ORGANIZATION ORGANIZATION.ORG_ID=EXPENDITURE_REV_FACT.ORG_ID


PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=EXPENDITURE_REV_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=EXPENDITURE_REV_FACT.GL_PERIOD_NAME


PROJECT PROJECT.PROJECT_ID=EXPENDITURE_REV_FACT.PROJECT_ID





SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=EXPENDITURE_REV_FACT.SET_OF_BOOKS_ID


TASK EXPENDITURE_REV_FACT.TASK_ID=TASK.TASK_ID


TASK_HIER_HZ EXPENDITURE_REV_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID


TASK_HIER_VR EXPENDITURE_REV_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID


TIME_DIM TIME_DIM.CALENDAR_DATE=EXPENDITURE_REV_FACT.CREATION_DATE



ReportsEvent Section 4

Event SectionThe Event section of this Rapid Mart contains summary level (or balance) transactions generating revenue and/or billing activity that are not directly related to any expenditure items.

Event Distribution AnalysisView summary and details of event distribution for the selected Organization and Year-Period Range.

Event Dist SummaryView event distribution summary by Event Type and Event Classification.


ReportsEvent Section4

Event Dist by ProjectView Event distribution listing details by Project.



Draft Revenue by ProjectView draft revenue listing details by Project.

Calculations• Revenue % Mix = [Revenue Amount PRJ]/Sum([Revenue Amount PRJ])


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, EVENT_DIST_FACT.EVENT_NUM, sum(EVENT_DIST_FACT.PROJECT_BILL_AMOUNT), sum(EVENT_DIST_FACT.PROJECT_REVENUE_AMOUNT), CURRENCY_PRJ.CURRENCY_NAME, SET_OF_BOOKS.SET_OF_BOOKS_NAME, DRAFT_REVENUE.PERIOD_NAME, DRAFT_REVENUE.DRAFT_REVENUE_NUM,



DRAFT_REVENUE.CREATION_DATE, DRAFT_REVENUE.LINE_NUM, DRAFT_REVENUE.CURRENCY_CODE_PRJ, DRAFT_REVENUE.REV_CATEGORY_NAME, DRAFT_REVENUE.REV_SOURCE_NAME, sum(DRAFT_REVENUE.LINE_REV_AMOUNT_FNC), EVENT.DESCRIPTION, EVENT.CREATION_DATE, EVENT.COMPLETION_DATE, EVENT.TASK_NAME, EVENT_TYPE.EVENT_TYPE, EVENT_TYPE.EVENT_TYPE_CLASSIFICATION, EVENT_DIST_FACT.LINE_NUM, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN

PERIOD_CALENDAR.PERIOD_YEAR || ' - 0' || PERIOD_CALENDAR.PERIOD_NUMBER ELSE PERIOD_CALENDAR.PERIOD_YEAR || ' - ' || PERIOD_CALENDAR.PERIOD_NUMBER END

FROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, EVENT_DIST_FACT, CURRENCY CURRENCY_PRJ, SET_OF_BOOKS, ( SELECT DR.PROJECT_ID, DR.DRAFT_REVENUE_NUM, DR.LINE_NUM, DR.ORG_ID, DR.CREATION_DATE, DR.ACCRUE_THROUGH_DATE, DR.CUSTOMER_BILL_SPLIT, DR.DRAFT_REVENUE_NUM_CREDITED, DR.PERIOD_SET_NAME, DR.GL_PERIOD_NAME, DR.PERIOD_NAME, DR.RELEASED_DATE, DR.TRANSFERRED_DATE, DR.UNBILLED_CODE_COMBINATION_ID, DR.UNEARNED_CODE_COMBINATION_ID, DR.REALIZED_GAINS_CC_ID, DR.REALIZED_LOSSES_CC_ID, DR.UNBILLED_RECEIVABLE_DR, DR.UNEARNED_REVENUE_CR, DR.REALIZED_GAINS_AMOUNT, DR.REALIZED_LOSSES_AMOUNT, DR.AGREEMENT_ID, DR.SET_OF_BOOKS_ID, DR.ORG_STRUCTURE_ID, DR.ORG_STRUCTURE_VERSION_ID, DR.START_ORG_ID, DR.TASK_ID, DR.REV_SOURCE_CODE, DR.REV_CATEGORY_CODE, DR.CURRENCY_CODE_TRX,



DR.CURRENCY_CODE_FNC, DR.CURRENCY_CODE_PRJ, DR.CURRENCY_CODE_FUND, DR.LINE_REV_AMOUNT_TRX, DR.LINE_REV_AMOUNT_FNC, DR.LINE_REV_AMOUNT_PRJ, DR.LINE_REV_AMOUNT_FUND, DR.TRANSFER_STATUS_CODE, O.ORG_NAME, P.PROJECT_NAME, P.PROJECT_NUM, P.PROJ_STATUS_NAME, P.PROJ_CLASS_NAME, T.TASK_NUMBER, T.TASK_NAME, PA.AGREEMENT_NUM, PA.AGREEMENT_TYPE, PA.AGREEMENT_DESC, PA.AGREEMENT_TYPE_DESC, SB.SET_OF_BOOKS_NAME, SB.SHORT_NAME AS SET_OF_BOOKS_SHORT_NAME, SB.SET_OF_BOOKS_DESC, REV_CATEGORY_NAME, REV_CATEGORY_DESC, REV_SOURCE_NAME, REV_SOURCE_DESC, DR.LOAD_DATE, DR.LOAD_TIMEFROM DRAFT_REVENUE_FACT DR, PROJECT P, ORGANIZATION O, TASK T, SET_OF_BOOKS SB, PROJECT_AGREEMENT PA, REVENUE_SOURCE RS, REVENUE_CATEGORY RCWHERE DR.PROJECT_ID = P.PROJECT_ID AND DR.TASK_ID = T.TASK_ID AND DR.ORG_ID = O.ORG_ID AND DR.AGREEMENT_ID = PA.AGREEMENT_ID AND DR.REV_SOURCE_CODE = RS.REV_SOURCE_CODE AND DR.REV_CATEGORY_CODE = RC.REV_CATEGORY_CODE AND DR.SET_OF_BOOKS_ID = SB.SET_OF_BOOKS_ID ) DRAFT_REVENUE, EVENT, EVENT_TYPE, PERIOD_CALENDARWHERE ( EVENT_DIST_FACT.EVENT_ID=EVENT.EVENT_ID ) AND ( EVENT_DIST_FACT.EVENT_TYPE_ID=EVENT_TYPE.EVENT_TYPE_ID

) AND ( MAIN_ORGANIZATION.ORG_ID=EVENT_DIST_FACT.ORG_ID ) AND ( PROJECT.PROJECT_ID=EVENT_DIST_FACT.PROJECT_ID )



AND ( EVENT_DIST_FACT.PROJECT_ID=DRAFT_REVENUE.PROJECT_ID and EVENT_DIST_FACT.DRAFT_REVENUE_NUM=DRAFT_REVENUE.DRAFT_REVENUE_NUM and EVENT_DIST_FACT.DRAFT_REVENUE_ITEM_LINE_NUM=DRAFT_REVENUE.LINE_NUM )

AND ( PERIOD_CALENDAR.PERIOD_SET_NAME=EVENT_DIST_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=EVENT_DIST_FACT.GL_PERIOD_NAME )

AND ( CURRENCY_PRJ.CURRENCY_CODE=EVENT_DIST_FACT.PROJECT_CURRENCY_CODE )

AND ( SET_OF_BOOKS.SET_OF_BOOKS_ID=EVENT_DIST_FACT.SET_OF_BOOKS_ID )

AND ( MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization




Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, EVENT_DIST_FACT.EVENT_NUM, CURRENCY_PRJ.CURRENCY_NAME, SET_OF_BOOKS.SET_OF_BOOKS_NAME, DRAFT_REVENUE.PERIOD_NAME, DRAFT_REVENUE.DRAFT_REVENUE_NUM, DRAFT_REVENUE.CREATION_DATE, DRAFT_REVENUE.LINE_NUM, DRAFT_REVENUE.CURRENCY_CODE_PRJ, DRAFT_REVENUE.REV_CATEGORY_NAME, DRAFT_REVENUE.REV_SOURCE_NAME, EVENT.DESCRIPTION, EVENT.CREATION_DATE, EVENT.COMPLETION_DATE, EVENT.TASK_NAME, EVENT_TYPE.EVENT_TYPE, EVENT_TYPE.EVENT_TYPE_CLASSIFICATION, EVENT_DIST_FACT.LINE_NUM,



CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN PERIOD_CALENDAR.PERIOD_YEAR || ' - 0' || PERIOD_CALENDAR.PERIOD_NUMBER ELSE PERIOD_CALENDAR.PERIOD_YEAR || ' - ' || PERIOD_CALENDAR.PERIOD_NUMBER END


When analyzing data from the event section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the EVENT_DIST_FACT table and other dimension tables in the Rapid Mart.


EVENT_DIST_FACT CODE_COMBINATION EVENT_DIST_FACT.CODE_COMBINATION_ID=CODE_COMBINATION.CODE_COMBINATION_ID

EVENT_DIST_FACT CURRENCY CURRENCY.CURRENCY_CODE=EVENT_DIST_FACT.BILL_TRANS_CURRENCY_CODE

EVENT_DIST_FACT CURRENCY CURRENCY.CURRENCY_CODE=EVENT_DIST_FACT.PROJECT_CURRENCY_CODE

EVENT_DIST_FACT CURRENCY CURRENCY.CURRENCY_CODE=EVENT_DIST_FACT.PROJFUNC_CURRENCY_CODE

EVENT_DIST_FACT DRAFT_INVOICE EVENT_DIST_FACT.PROJECT_ID=DRAFT_INVOICE.PROJECT_ID and EVENT_DIST_FACT.DRAFT_INVOICE_NUM=DRAFT_INVOICE.DRAFT_INVOICE_NUM and EVENT_DIST_FACT.DRAFT_INVOICE_ITE M_LINE_NUM=DRAFT_INVOICE.LINE_NUM

NOTE: DRAFT_INVOICE is a derived table in the Universe. See the Universe chapter for details.



EVENT_DIST_FACT DRAFT_REVENUE EVENT_DIST_FACT.PROJECT_ID=DRAFT_REVENUE.PROJECT_ID and EVENT_DIST_FACT.DRAFT_REVENUE_NUM=DRAFT_REVENUE.DRAFT_REVENUE_NUM and EVENT_DIST_FACT.DRAFT_REVENUE_ITEM_LINE_NUM=DRAFT_REVENUE.LINE_NUM

NOTE: DRAFT_REVENUE is a derived table in the Universe. See the Universe chapter for details.

EVENT_DIST_FACT EVENT EVENT_DIST_FACT.EVENT_ID=EVENT.EVENT_ID

EVENT_DIST_FACT EVENT_TYPE EVENT_DIST_FACT.EVENT_TYPE_ID=EVENT_TYPE.EVENT_TYPE_ID

EVENT_DIST_FACT ORG_PRIMARY_HZ EVENT_DIST_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and EVENT_DIST_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER

EVENT_DIST_FACT ORG_PRIMARY_VR EVENT_DIST_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and EVENT_DIST_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER

EVENT_DIST_FACT ORG_STRUCTURE EVENT_DIST_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and EVENT_DIST_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and EVENT_DIST_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID

EVENT_DIST_FACT ORGANIZATION ORGANIZATION.ORG_ID=EVENT_DIST_FACT.ORG_ID




EVENT_DIST_FACT PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=EVENT_DIST_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=EVENT_DIST_FACT.GL_PERIOD_NAME

EVENT_DIST_FACT PROJECT PROJECT.PROJECT_ID=EVENT_DIST_FACT.PROJECT_ID

EVENT_DIST_FACT PROJECT_CLASS_CATEGORY


EVENT_DIST_FACT SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=EVENT_DIST_FACT.SET_OF_BOOKS_ID

EVENT_DIST_FACT TASK EVENT_DIST_FACT.TASK_ID=TASK.TASK_ID

EVENT_DIST_FACT TASK_HIER_HZ EVENT_DIST_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID

EVENT_DIST_FACT TASK_HIER_VR EVENT_DIST_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID

EVENT_DIST_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=EVENT_DIST_FACT.CREATION_DATE



ReportsProject Asset Section 4

Project Asset SectionThe Project Asset section of this Rapid Mart holds capital and retirement adjustment assets for capital projects.Using the asset data, you can complete numerous operational analyses and generate different reports.

Project Asset ListingView project asset listing for selected projects. Listing details include current cost, original cost, and asset location.

Report SQLSELECT DISTINCT '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT_ASSET_FACT.ASSET_NAME, PROJECT_ASSET_FACT.DATE_PLACED_IN_SERVICE, PROJECT_ASSET_FACT.ASSET_DESCRIPTION, PROJECT_ASSET_FACT.ASSET_LINE_DESCRIPTION, ASSET_CATEGORY.CATEGORY_DESC, ASSET_CATEGORY.CATEGORY_TYPE_NAME,


ReportsProject Asset Section4

ASSET_LOCATION.LOCATION_SEGMENT1, ASSET_LOCATION.LOCATION_SEGMENT2, ASSET_LOCATION.LOCATION_SEGMENT3, sum(PROJECT_ASSET_FACT.CURRENT_ASSET_COST), sum(PROJECT_ASSET_FACT.ORIGINAL_ASSET_COST), PROJECT_ASSET_FACT.PROJECT_ASSET_LINE_ID, PROJECT_ASSET_FACT.CURRENCY_CODE_PRJFROM PROJECT, PROJECT_ASSET_FACT, ASSET_CATEGORY, ASSET_LOCATIONWHERE (

PROJECT_ASSET_FACT.ASSET_CATEGORY_ID=ASSET_CATEGORY.CATEGORY_ID )

AND ( PROJECT_ASSET_FACT.LOCATION_ID=ASSET_LOCATION.LOCATION_ID )

AND ( PROJECT.PROJECT_ID=PROJECT_ASSET_FACT.PROJECT_ID ) AND PROJECT.PROJECT_NAME In @prompt('Project Name(s):','A','PROJECT\Project

Name',Multi,Free,Persistent,,User:0)GROUP BY '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT_ASSET_FACT.ASSET_NAME, PROJECT_ASSET_FACT.DATE_PLACED_IN_SERVICE, PROJECT_ASSET_FACT.ASSET_DESCRIPTION, PROJECT_ASSET_FACT.ASSET_LINE_DESCRIPTION, ASSET_CATEGORY.CATEGORY_DESC, ASSET_CATEGORY.CATEGORY_TYPE_NAME, ASSET_LOCATION.LOCATION_SEGMENT1, ASSET_LOCATION.LOCATION_SEGMENT2, ASSET_LOCATION.LOCATION_SEGMENT3, PROJECT_ASSET_FACT.PROJECT_ASSET_LINE_ID, PROJECT_ASSET_FACT.CURRENCY_CODE_PRJ


ReportsProject Asset Section 4

Recommended table joins When analyzing data from the project asset section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the PROJECT_ASSET_FACT table and other dimension tables in the Rapid Mart.


PROJECT_ASSET_FACT

ASSET_CATEGORY PROJECT_ASSET_FACT.ASSET_CATEGORY_ID=ASSET_CATEGORY.CATEGORY_ID

PROJECT_ASSET_FACT

ASSET_LOCATION PROJECT_ASSET_FACT.LOCATION_ID=ASSET_LOCATION.LOCATION_ID

PROJECT_ASSET_FACT

BOOK_TYPE PROJECT_ASSET_FACT.BOOK_TYPE_ID=BOOK_TYPE.BOOK_TYPE_ID

PROJECT_ASSET_FACT

CURRENCY CURRENCY.CURRENCY_CODE=PROJECT_ASSET_FACT.CURRENCY_CODE_PRJ

PROJECT_ASSET_FACT

CURRENT_PEOPLE CURRENT_PEOPLE.PERSON_ID=PROJECT_ASSET_FACT.ASSIGNED_TO_PERSON_ID

PROJECT_ASSET_FACT

ORG_PRIMARY_HIER_HZ

PROJECT_ASSET_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and PROJECT_ASSET_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER

PROJECT_ASSET_FACT

ORG_PRIMARY_HIER_VR

PROJECT_ASSET_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and PROJECT_ASSET_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER

PROJECT_ASSET_FACT

ORG_STRUCTURE PROJECT_ASSET_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and PROJECT_ASSET_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and PROJECT_ASSET_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID


ReportsProject Asset Section4

PROJECT_ASSET_FACT

PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=PROJECT_ASSET_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=PROJECT_ASSET_FACT.GL_PERIOD_NAME

PROJECT_ASSET_FACT

PROJECT PROJECT.PROJECT_ID=PROJECT_ASSET_FACT.PROJECT_ID

PROJECT_ASSET_FACT



PROJECT_ASSET_FACT

SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=PROJECT_ASSET_FACT.SET_OF_BOOKS_ID

PROJECT_ASSET_FACT

TIME_DIM TIME_DIM.CALENDAR_DATE=PROJECT_ASSET_FACT.CREATION_DATE



ReportsProject Summary Section 4

Project Summary SectionThe Project Summary section of this Rapid Mart contains summarized inception-to-date, year-to-date, period-to-date, and prior period project data.

Sample reportsUsing the project summary information, you can complete numerous operational analyses and generate different reports. For example, reports you can generate include:• Project Summary Analysis• Project Summary Cumulative Trend

Project Summary AnalysisAnalysis of Project Summary totals for a specific Project Period and Organization

OverviewView project summary totals for the selected Organization and Project Period by Project Class Category and Project Class Code.


ReportsProject Summary Section4

Project Summary AnalysisAnalyze project summary detail for the selected Organization and Project Period. Results are grouped by Project, Project Class Category, and Project Resource.

Calculations• % Mix = If([Revenue Itd PRJ] <> 0; ([Revenue Itd PRJ]-[Burdened Cost

Itd PRJ])/[Revenue Itd PRJ]; 0)• Project Value Scaled = [Project Value]*[Numeric Scaling Factor]


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_RESOURCE.PROJECT_RESOURCE, PROJECT_RESOURCE.RESOURCE_DESCRIPTION, TASK.TASK_NAME,



sum(PROJECT_SUMMARY_FACT.BILLABLE_BURDENED_COST_ITD), sum(PROJECT_SUMMARY_FACT.BURDENED_COST_ITD), PROJECT_PERIOD.PERIOD_NAME, PROJECT.PROJ_TYPE_DESC, PROJECT.PROJECT_NUM, PROJECT.PROJECT_ID, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_DESC, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, PROJECT_CLASS_CATEGORY.CATEGORY_DESC, PROJECT.PROJ_TYPE_CODE, PROJECT.START_DATE, PROJECT.COMPLETION_DATE, PROJECT.CLOSED_DATE, PROJECT.PROJ_STATUS_CODE, PROJECT.PROJECT_VALUE, PROJECT.CURRENCY_CODE_PRJ, PROJECT_RESOURCE.RESOURCE_TYPE, sum(PROJECT_SUMMARY_FACT.REVENUE_ITD)FROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, PROJECT_RESOURCE, TASK, PROJECT_SUMMARY_FACT, PROJECT_PERIOD, PROJECT_CLASS_CATEGORYWHERE ( MAIN_ORGANIZATION.ORG_ID=PROJECT_SUMMARY_FACT.ORG_ID ) AND (

PROJECT_SUMMARY_FACT.RESOURCE_ID=PROJECT_RESOURCE.RESOURCE_ID )

AND ( PROJECT.PROJECT_ID=PROJECT_SUMMARY_FACT.PROJECT_ID ) AND ( PROJECT_SUMMARY_FACT.TASK_ID=TASK.TASK_ID ) AND ( PROJECT_PERIOD.ORG_ID=PROJECT_SUMMARY_FACT.ORG_ID and

PROJECT_PERIOD.PERIOD_NAME=PROJECT_SUMMARY_FACT.PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID ) AND (MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization

Name:','A','Organization\Organization Name',Mono,Free,Persistent,,User:0) AND PROJECT_PERIOD.PERIOD_NAME = @prompt('Project Period:','A','PROJECT

PERIOD\Period Name',Mono,Free,Persistent,,User:1) )GROUP BY MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_RESOURCE.PROJECT_RESOURCE, PROJECT_RESOURCE.RESOURCE_DESCRIPTION, TASK.TASK_NAME,



PROJECT_PERIOD.PERIOD_NAME, PROJECT.PROJ_TYPE_DESC, PROJECT.PROJECT_NUM, PROJECT.PROJECT_ID, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_DESC, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, PROJECT_CLASS_CATEGORY.CATEGORY_DESC, PROJECT.PROJ_TYPE_CODE, PROJECT.START_DATE, PROJECT.COMPLETION_DATE, PROJECT.CLOSED_DATE, PROJECT.PROJ_STATUS_CODE, PROJECT.PROJECT_VALUE, PROJECT.CURRENCY_CODE_PRJ, PROJECT_RESOURCE.RESOURCE_TYPE

Project Summary Cumulative TrendView project summary cumulative trends by Organization and Year-Period range (based on fiscal year period calendar).



Calculations• % Margin = If([Revenue Ytd PRJ] <> 0; ([Revenue Ytd PRJ]-[Burdened

Cost Ytd PRJ])/[Revenue Ytd PRJ]; 0)


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_RESOURCE.PROJECT_RESOURCE, PROJECT_RESOURCE.RESOURCE_DESCRIPTION, TASK.TASK_NAME, PROJECT_PERIOD.PERIOD_NAME, PROJECT.PROJ_TYPE_DESC, PROJECT.PROJECT_NUM, PROJECT.PROJECT_ID, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_DESC, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, PROJECT_CLASS_CATEGORY.CATEGORY_DESC, PROJECT.PROJ_TYPE_CODE, PROJECT.START_DATE, PROJECT.COMPLETION_DATE, PROJECT.CLOSED_DATE, PROJECT.PROJ_STATUS_CODE, PROJECT.PROJECT_VALUE, PROJECT.CURRENCY_CODE_PRJ, PROJECT_RESOURCE.RESOURCE_TYPE, sum(PROJECT_SUMMARY_FACT.REVENUE_YTD), sum(PROJECT_SUMMARY_FACT.BURDENED_COST_YTD), CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PERIOD_CALENDAR.PERIOD_YEAR, PERIOD_CALENDAR.PERIOD_NUMBER, PERIOD_CALENDAR.PERIOD_QUARTERFROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, PROJECT_RESOURCE, TASK, PROJECT_PERIOD, PROJECT_CLASS_CATEGORY, PROJECT_SUMMARY_FACT, PERIOD_CALENDARWHERE ( MAIN_ORGANIZATION.ORG_ID=PROJECT_SUMMARY_FACT.ORG_ID )



AND ( PROJECT_SUMMARY_FACT.RESOURCE_ID=PROJECT_RESOURCE.RESOURCE_ID )

AND ( PERIOD_CALENDAR.PERIOD_SET_NAME=PROJECT_SUMMARY_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=PROJECT_SUMMARY_FACT.GL_PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=PROJECT_SUMMARY_FACT.PROJECT_ID ) AND ( PROJECT_SUMMARY_FACT.TASK_ID=TASK.TASK_ID ) AND ( PROJECT_PERIOD.ORG_ID=PROJECT_SUMMARY_FACT.ORG_ID and

PROJECT_PERIOD.PERIOD_NAME=PROJECT_SUMMARY_FACT.PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID ) AND ( MAIN_ORGANIZATION.ORG_NAME = @prompt('Organization

Name:','A','Organization\Organization Name',Mono,Free,Persistent,,User:0) AND PERIOD_CALENDAR.PERIOD_YEAR = @prompt('Year:','N','PERIOD

CALENDAR\Year',Mono,Free,Persistent,,User:1) )GROUP BY MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_RESOURCE.PROJECT_RESOURCE, PROJECT_RESOURCE.RESOURCE_DESCRIPTION, TASK.TASK_NAME, PROJECT_PERIOD.PERIOD_NAME, PROJECT.PROJ_TYPE_DESC, PROJECT.PROJECT_NUM, PROJECT.PROJECT_ID, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_DESC, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, PROJECT_CLASS_CATEGORY.CATEGORY_DESC, PROJECT.PROJ_TYPE_CODE, PROJECT.START_DATE, PROJECT.COMPLETION_DATE, PROJECT.CLOSED_DATE, PROJECT.PROJ_STATUS_CODE, PROJECT.PROJECT_VALUE, PROJECT.CURRENCY_CODE_PRJ, PROJECT_RESOURCE.RESOURCE_TYPE, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PERIOD_CALENDAR.PERIOD_YEAR, PERIOD_CALENDAR.PERIOD_NUMBER, PERIOD_CALENDAR.PERIOD_QUARTER



Recommended table joins When analyzing data from the project summary section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the PROJECT_SUMMARY_FACT table and other dimension tables in the Rapid Mart.


PROJECT_SUMMARY_FACT

CURRENCY CURRENCY.CURRENCY_CODE=PROJECT_SUMMARY_FACT.CURRENCY_CODE_PRJ


ORG_PRIMARY_HIER_HZ

PROJECT_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and PROJECT_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER


ORG_PRIMARY_HIER_VR

PROJECT_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and PROJECT_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER


ORG_STRUCTURE PROJECT_SUMMARY_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and PROJECT_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and PROJECT_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID


ORGANIZATION ORGANIZATION.ORG_ID=PROJECT_SUMMARY_FACT.ORG_ID


PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=PROJECT_SUMMARY_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=PROJECT_SUMMARY_FACT.GL_PERIOD_NAME







PROJECT_PERIOD PROJECT_PERIOD.ORG_ID=PROJECT_SUMMARY_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=PROJECT_SUMMARY_FACT.PERIOD_NAME


PROJECT_RESOURCE

PROJECT.PROJECT_ID=PROJECT_SUMMARY_FACT.PROJECT_ID and PROJECT_SUMMARY_FACT.RESOURCE_ID=PROJECT_RESOURCE.RESOURCE_ID


SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=PROJECT_SUMMARY_FACT.SET_OF_BOOKS_ID


TASK PROJECT_SUMMARY_FACT.TASK_ID=TASK.TASK_ID


TASK_HIER_HZ PROJECT_SUMMARY_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID


TASK_HIER_VR PROJECT_SUMMARY_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID


TIME_DIM TIME_DIM.CALENDAR_DATE=PROJECT_SUMMARY_FACT.CREATION_DATE



ReportsProject Transaction Summary Section 4

Project Transaction Summary SectionThe Project Transaction Summary section of this Rapid Mart contains summarized project data at the lowest level of detail.

Sample reportsUsing the project transaction summary information, you can complete numerous operational analyses and generate different reports. For example, reports you can generate include:• Project Txn Summary Trend• Project Txn Summary Top 10 Analysis

Project Txn Summary TrendProject Txn Summary trend analysis for selected Organization and Year-Period range.


ReportsProject Transaction Summary Section4


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, sum(PROJECT_TXN_SUMMARY_FACT.TOT_BURDENED_COST), sum(PROJECT_TXN_SUMMARY_FACT.TOT_RAW_COST), sum(PROJECT_TXN_SUMMARY_FACT.TOT_REVENUE), PROJECT_TXN_SUMMARY_FACT.EXPENDITURE_CATEGORY, PROJECT_TXN_SUMMARY_FACT.REVENUE_CATEGORY, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PROJECT_TXN_SUMMARY_FACT.CURRENCY_CODE_PRJFROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, PROJECT_TXN_SUMMARY_FACT, PERIOD_CALENDARWHERE (

PERIOD_CALENDAR.PERIOD_SET_NAME=PROJECT_TXN_SUMMARY_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=PROJECT_TXN_SUMMARY_FACT.GL_PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=PROJECT_TXN_SUMMARY_FACT.PROJECT_ID )

AND ( MAIN_ORGANIZATION.ORG_ID=PROJECT_TXN_SUMMARY_FACT.ORG_ID )




)GROUP BY MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?',



@Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In Millions',mono,constrained),

PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, PROJECT_TXN_SUMMARY_FACT.EXPENDITURE_CATEGORY, PROJECT_TXN_SUMMARY_FACT.REVENUE_CATEGORY, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PROJECT_TXN_SUMMARY_FACT.CURRENCY_CODE_PRJ

Project Txn Summary Top 10 AnalysisTop 10 analysis of revenue, burdened cost, and Organization and calendar years. This report uses the Webi report ranking feature to determine Top 10 results defined in each report tab.

Top 10 by RevenueView top 10 revenue projects.



Top 10 by Burdened CostView top 10 burdened cost projects.



Top 10 by MarginView top 10 projects by margin amount (highest margin between revenue and burdened cost projects).

CalculationsMargin Amount =[Total Revenue PRJ] - [Total Burdened Cost PRJ]Margin % = If([Total Revenue PRJ] <>0 ; ([Total Revenue PRJ] - [Total Burdened Cost PRJ])/[Total Revenue PRJ]; 0)


Millions',mono,constrained), PROJECT.PROJECT_NAME, PROJECT.PROJECT_DESC, sum(PROJECT_TXN_SUMMARY_FACT.TOT_BURDENED_COST), sum(PROJECT_TXN_SUMMARY_FACT.TOT_RAW_COST), sum(PROJECT_TXN_SUMMARY_FACT.TOT_REVENUE), PROJECT_TXN_SUMMARY_FACT.EXPENDITURE_CATEGORY, PROJECT_TXN_SUMMARY_FACT.REVENUE_CATEGORY,



CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN PERIOD_CALENDAR.PERIOD_YEAR || ' - 0' || PERIOD_CALENDAR.PERIOD_NUMBER ELSE PERIOD_CALENDAR.PERIOD_YEAR || ' - ' || PERIOD_CALENDAR.PERIOD_NUMBER END,

PROJECT_PERIOD.PERIOD_NAME, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, PROJECT_TXN_SUMMARY_FACT.NON_LABOR_RESOURCE, PROJECT_PERIOD.PA_PERIOD_TYPE, PROJECT_PERIOD.ALT_PERIOD_NAME, PROJECT.PROJ_TYPE_CODE, PROJECT_PERIOD.CALENDAR_YEAR, PROJECT_PERIOD.CALENDAR_QTR, PROJECT.START_DATE, PROJECT.COMPLETION_DATE, PROJECT.SERVICE_TYPE_CODE, PROJECT_TXN_SUMMARY_FACT.CURRENCY_CODE_PRJFROM ORGANIZATION MAIN_ORGANIZATION, PROJECT, PROJECT_TXN_SUMMARY_FACT, PERIOD_CALENDAR, PROJECT_PERIOD, PROJECT_CLASS_CATEGORYWHERE (

PERIOD_CALENDAR.PERIOD_SET_NAME=PROJECT_TXN_SUMMARY_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=PROJECT_TXN_SUMMARY_FACT.GL_PERIOD_NAME )

AND ( PROJECT_PERIOD.ORG_ID=PROJECT_TXN_SUMMARY_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=PROJECT_TXN_SUMMARY_FACT.PERIOD_NAME )

AND ( PROJECT.PROJECT_ID=PROJECT_TXN_SUMMARY_FACT.PROJECT_ID )

AND ( PROJECT.PROJECT_ID=PROJECT_CLASS_CATEGORY.PROJECT_ID ) AND (

MAIN_ORGANIZATION.ORG_ID=PROJECT_TXN_SUMMARY_FACT.ORG_ID )


Name:','A','Organization\Organization Name',Mono,Free,Persistent,,User:0) AND PROJECT_PERIOD.CALENDAR_YEAR In @prompt('Calendar

Year(s):','N','PROJECT PERIOD\Calendar Year',Multi,Free,Persistent,,User:1) )GROUP BY MAIN_ORGANIZATION.ORGANIZATION_CODE, MAIN_ORGANIZATION.ORG_NAME, '../../opendoc/openDocument.jsp?', @Prompt('Choose a Scaling factor','A','No Scaling factor','In Thousands','In

Millions',mono,constrained), PROJECT.PROJECT_NAME,



PROJECT.PROJECT_DESC, PROJECT_TXN_SUMMARY_FACT.EXPENDITURE_CATEGORY, PROJECT_TXN_SUMMARY_FACT.REVENUE_CATEGORY, CASE WHEN PERIOD_CALENDAR.PERIOD_NUMBER < 10 THEN


PROJECT_PERIOD.PERIOD_NAME, PROJECT_CLASS_CATEGORY.CLASS_CODE, PROJECT_CLASS_CATEGORY.CLASS_CATEGORY, PROJECT_TXN_SUMMARY_FACT.NON_LABOR_RESOURCE, PROJECT_PERIOD.PA_PERIOD_TYPE, PROJECT_PERIOD.ALT_PERIOD_NAME, PROJECT.PROJ_TYPE_CODE, PROJECT_PERIOD.CALENDAR_YEAR, PROJECT_PERIOD.CALENDAR_QTR, PROJECT.START_DATE, PROJECT.COMPLETION_DATE, PROJECT.SERVICE_TYPE_CODE, PROJECT_TXN_SUMMARY_FACT.CURRENCY_CODE_PRJ


When analyzing data from the project transaction summary section, you need to create joins between fact and dimension tables. Specifically, you need to create joins between the PROJECT_TXN_SUMMARY_FACT table and other dimension tables in the Rapid Mart.


PROJECT_TXN_SUMMARY_FACT

CURRENCY CURRENCY.CURRENCY_CODE=PROJECT_TXN_SUMMARY_FACT.CURRENCY_CODE_PRJ


CURRENT_PERSON CURRENT_PEOPLE.PERSON_ID=PROJECT_TXN_SUMMARY_FACT.PERSON_ID


EVENT_TYPE PROJECT_TXN_SUMMARY_FACT.EVENT_TYPE_ID=EVENT_TYPE.EVENT_TYPE_ID


EXPENDITURE_TYPE PROJECT_TXN_SUMMARY_FACT.EXPENDITURE_TYPE_ID=EXPENDITURE_TYPE.EXPENDITURE_TYPE_ID


JOB PROJECT_TXN_SUMMARY_FACT.JOB_ID=JOB.JOB_ID


ORG_PRIMARY_HIER_HZ

PROJECT_TXN_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_HZ.ORGANIZATION_ID and PROJECT_TXN_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_HZ.VERSION_NUMBER


ORG_PRIMARY_HIER_VR

PROJECT_TXN_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_PRIMARY_HIER_VR.DESCENDENT_ID and PROJECT_TXN_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_PRIMARY_HIER_VR.VERSION_NUMBER


ORGANIZATION ORGANIZATION.ORG.ORG_ID=PROJECT_TXN_SUMMARY_FACT.NON_LABOR_RESOURCE_ORG_ID


ORGANIZATION ORGANIZATION.ORG_ID=PROJECT_TXN_SUMMARY_FACT.ORG_ID




ORG_STRUCTURE PROJECT_TXN_SUMMARY_FACT.ORGANIZATION_STRUCTURE_ID=ORG_STRUCTURE.ORG_STRUCTURE_ID and PROJECT_TXN_SUMMARY_FACT.ORG_STRUCTURE_VERSION_ID=ORG_STRUCTURE.VERSION_NUMBER and PROJECT_TXN_SUMMARY_FACT.START_ORGANIZATION_ID=ORG_STRUCTURE.ORGANIZATION_ID


PERIOD_CALENDAR PERIOD_CALENDAR.PERIOD_SET_NAME=PROJECT_TXN_SUMMARY_FACT.PERIOD_SET_NAME and PERIOD_CALENDAR.PERIOD_NAME=PROJECT_TXN_SUMMARY_FACT.GL_PERIOD_NAME


PROJECT PROJECT.PROJECT_ID=PROJECT_TXN_SUMMARY_FACT.PROJECT_ID





PROJECT_PERIOD PROJECT_PERIOD.ORG_ID=PROJECT_TXN_SUMMARY_FACT.ORG_ID and PROJECT_PERIOD.PERIOD_NAME=PROJECT_TXN_SUMMARY_FACT.PERIOD_NAME


SET_OF_BOOKS SET_OF_BOOKS.SET_OF_BOOKS_ID=PROJECT_TXN_SUMMARY_FACT.SET_OF_BOOKS_ID


TASK PROJECT_TXN_SUMMARY_FACT.TASK_ID=TASK.TASK_ID


TASK_HIER_HZ PROJECT_TXN_SUMMARY_FACT.TASK_ID=TASK_HIER_HZ.TASK_ID


TASK_HIER_VR PROJECT_TXN_SUMMARY_FACT.TASK_ID=TASK_HIER_VR.DESCENDENT_TASK_ID


TIME_DIM TIME_DIM.CALENDAR_DATE=PROJECT_TXN_SUMMARY_FACT.CREATION_DATE


VENDOR PROJECT_TXN_SUMMARY_FACT.VENDOR_ID=VENDOR.VENDOR_ID



ReportsHierarchy Data Discovery4
Hierarchy Data Discovery
Horizontal and Vertical Hierarchy information is available in the Universe for all relevant common dimensions. You can use horizontal hierarchies to view information about all hierarchy levels. Whereas, the vertical hierarchy data is used to restrict to only a subset of the hierarchy based on a selected parent node.For more details on horizontal and vertical hierarchies, see Chapter 5: Hierarchies.The reports listed in this chapter allow users to browse hierarchical master data. It can be helpful to understand data relationship to produce reports where a subset of hierarchical data needs to be analyzed. Each report displays the horizontal hierarchy data for a prompted parent hierarchy value. A data discovery report is included for each of the following hierarchies:• Account Hierarchy Data Discovery• Cost Center Hierarchy Data Discovery• Company Hierarchy Data Discovery• Project Hierarchy Data Discovery• Product Hierarchy Data Discovery


ReportsHierarchy Data Discovery 4

Account Hierarchy Data DiscoveryView Activity Hierarchies for a specified Parent Account and Chart of Accounts Name (as defined in Oracle).

Report SQLSELECTCOA_ACCOUNT_HZ.LVL_0_ACCOUNT_CODE || ' - ' || COA_ACCOUNT_HZ.LVL_0_ACCOUNT_DESC,COA_ACCOUNT_HZ.LVL_1_ACC

OUNT_CODE || ' - ' || COA_ACCOUNT_HZ.LVL_1_ACCOUNT_DESC,COA_ACCOUNT_HZ.LVL_2_ACC






OUNT_CODE || ' - ' ||




COA_ACCOUNT_HZ.LVL_8_ACCOUNT_DESC, COA_ACCOUNT_HZ.LEAF_LEVEL, COA_ACCOUNT_HZ.ACCOUNT_CODE, COA_ACCOUNT_VR.ACCNT_ANCESTORFROM COA_ACCOUNT_HZ, COA_ACCOUNT_VR, COA_ACCOUNT HIER_COA_ACCOUNTWHERE (

HIER_COA_ACCOUNT.CHART_OF_ACCT_ID=COA_ACCOUNT_VR.CHART_OF_ACCT_ID and

HIER_COA_ACCOUNT.ACCOUNT_CODE=COA_ACCOUNT_VR.ACCNT_DESCENDENT )

AND ( HIER_COA_ACCOUNT.CHART_OF_ACCT_ID=COA_ACCOUNT_HZ.CHART_OF_ACCT_ID and

HIER_COA_ACCOUNT.ACCOUNT_CODE=COA_ACCOUNT_HZ.ACCOUNT_CODE )

AND ( HIER_COA_ACCOUNT.CHART_OF_ACCT_NAME = @prompt('Chart Of Account

Name:','A','Coa Account\Chart Of Account Name',Mono,Free,Persistent,,User:0) AND ( COA_ACCOUNT_VR.ACCNT_ANCESTOR in @Prompt('Select Multiple Parent

Accounts for Group','A','Coa Account Vr\Account Ancestor',multi,free) ) )



Cost Center Hierarchy Data DiscoveryView Cost Center Hierarchies for a specified Parent Cost Center and Chart of Accounts Name (as defined in Oracle).

Report SQLSELECTCOA_COST_CENTER_HZ.LVL_0_CST_CTR_CODE || ' - ' || COA_COST_CENTER_HZ.LVL_0_CST_CTR_DESC,COA_COST_CENTER_HZ.LV

L_1_CST_CTR_CODE || ' - ' || COA_COST_CENTER_HZ.LVL_1_CST_CTR_DESC,COA_COST_CENTER_HZ.LV






L_7_CST_CTR_CODE || ' - ' ||



COA_COST_CENTER_HZ.LVL_7_CST_CTR_DESC,COA_COST_CENTER_HZ.LVL_8_CST_CTR_CODE || ' - ' ||

COA_COST_CENTER_HZ.LVL_8_CST_CTR_DESC, COA_COST_CENTER_HZ.COST_CENTER_CODE, COA_COST_CENTER_HZ.LEAF_LEVEL, COA_COST_CENTER_VR.CST_CTR_ANCESTOR, HIER_COA_ACCOUNT.CHART_OF_ACCT_NAMEFROM COA_COST_CENTER_HZ, COA_COST_CENTER_VR, COA_ACCOUNT HIER_COA_ACCOUNT, COA_COST_CENTER, CODE_COMBINATIONWHERE (

CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER.CHART_OF_ACCT_ID and CODE_COMBINATION.COST_CENTER_CODE=COA_COST_CENTER.COST_CENTER_CODE )

AND ( CODE_COMBINATION.CHART_OF_ACCT_ID=HIER_COA_ACCOUNT.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=HIER_COA_ACCOUNT.ACCOUNT_CODE )

AND ( COA_COST_CENTER.CHART_OF_ACCT_ID=COA_COST_CENTER_HZ.CHART_OF_ACCT_ID and

COA_COST_CENTER.COST_CENTER_CODE=COA_COST_CENTER_HZ.COST_CENTER_CODE )

AND ( COA_COST_CENTER.CHART_OF_ACCT_ID=COA_COST_CENTER_VR.CHART_OF_ACCT_ID and

COA_COST_CENTER.COST_CENTER_CODE=COA_COST_CENTER_VR.CST_CTR_DESCENDENT )

AND ( ( COA_COST_CENTER_VR.CST_CTR_ANCESTOR in @Prompt('Select Multiple

Parent Cost Center for Group','A','Coa Cost Center Vr\Cost Center Ancestor ID',multi,free) ) AND HIER_COA_ACCOUNT.CHART_OF_ACCT_NAME = @prompt('Chart Of

Accounts Name:','A','Coa Account\Chart Of Account Name',Mono,Free,Persistent,,User:0) )



Company Hierarchy Data DiscoveryView Company Hierarchies for a specified Parent Company and Chart of Accounts Name (as defined in Oracle).

Report SQLSELECTCOA_COMPANY_HZ.LVL_0_COMPANY_CODE || ' - ' ||

COA_COMPANY_HZ.LVL_0_COMPANY_DESC,COA_COMPANY_HZ.LVL_1_COMPANY_CODE || ' - ' ||








COA_COMPANY_HZ.LVL_8_COMPANY_DESC, COA_COMPANY_VR.COMPANY_ANCESTOR, HIER_COA_ACCOUNT.CHART_OF_ACCT_NAMEFROM COA_COMPANY_HZ, COA_COMPANY_VR, COA_ACCOUNT HIER_COA_ACCOUNT, COA_COMPANY HIER_COA_COMPANY, CODE_COMBINATIONWHERE (

CODE_COMBINATION.CHART_OF_ACCT_ID=HIER_COA_COMPANY.CHART_OF_ACCT_ID and CODE_COMBINATION.COMPANY_CODE=HIER_COA_COMPANY.COMPANY_CODE )



AND ( CODE_COMBINATION.CHART_OF_ACCT_ID=HIER_COA_ACCOUNT.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=HIER_COA_ACCOUNT.ACCOUNT_CODE )

AND ( HIER_COA_COMPANY.CHART_OF_ACCT_ID=COA_COMPANY_HZ.CHART_OF_ACCT_ID and HIER_COA_COMPANY.COMPANY_CODE=COA_COMPANY_HZ.COMPANY_CODE )

AND ( HIER_COA_COMPANY.CHART_OF_ACCT_ID=COA_COMPANY_VR.CHART_OF_ACCT_ID and HIER_COA_COMPANY.COMPANY_CODE=COA_COMPANY_VR.COMPANY_DESCENDENT )

AND ( ( COA_COMPANY_VR.COMPANY_ANCESTOR in @Prompt('Select Multiple

Parent Company for Group','A','Coa Company Vr\Company Ancestor',multi,free) ) AND HIER_COA_ACCOUNT.CHART_OF_ACCT_NAME = @prompt('Chart Of Account

Name:','A','Coa Account\Chart Of Account Name',Mono,Free,Persistent,,User:0) )



Project Hierarchy Data DiscoveryView Project Hierarchies for a specified Parent Project and Chart of Accounts Name (as defined in Oracle).

Report SQLSELECTCOA_PROJECT_HZ.LVL_0_PROJECT_CODE || ' - ' || COA_PROJECT_HZ.LVL_0_PROJECT_DESC,COA_PROJECT_HZ.LVL_1_PROJEC

T_CODE || ' - ' || COA_PROJECT_HZ.LVL_1_PROJECT_DESC,COA_PROJECT_HZ.LVL_2_PROJEC







T_CODE || ' - ' || COA_PROJECT_HZ.LVL_8_PROJECT_DESC, COA_PROJECT_VR.PROJECT_ANCESTOR, HIER_COA_ACCOUNT.CHART_OF_ACCT_NAMEFROM COA_PROJECT_HZ, COA_PROJECT_VR, COA_ACCOUNT HIER_COA_ACCOUNT, COA_PROJECT, CODE_COMBINATION CODE_COMBINATIONWHERE (

CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PROJECT.CHART_OF_ACCT_ID and

CODE_COMBINATION.PROJECT_CODE=COA_PROJECT.PROJECT_CODE ) AND (

CODE_COMBINATION.CHART_OF_ACCT_ID=HIER_COA_ACCOUNT.CHART_OF_ACCT_ID and



CODE_COMBINATION.ACCOUNT_CODE=HIER_COA_ACCOUNT.ACCOUNT_CODE )

AND ( COA_PROJECT.CHART_OF_ACCT_ID=COA_PROJECT_VR.CHART_OF_ACCT_ID and

COA_PROJECT.PROJECT_CODE=COA_PROJECT_VR.PROJECT_DESCENDENT )

AND ( COA_PROJECT.CHART_OF_ACCT_ID=COA_PROJECT_HZ.CHART_OF_ACCT_ID and

COA_PROJECT.PROJECT_CODE=COA_PROJECT_HZ.PROJECT_CODE ) AND ( ( COA_PROJECT_VR.PROJECT_ANCESTOR in @Prompt('Select Multiple Parent

Projects for Group','A','Coa Project Vr\Project Ancestor',multi,free) ) AND COA_PROJECT.CHART_OF_ACCT_NAME = @prompt('Chart Of Account

Name:','A','Coa Project\Chart Of Account Name',Mono,Free,Persistent,,User:0) )



Product Hierarchy Data DiscoveryView Product Hierarchies for a specified Parent Product and Chart of Accounts Name (as defined in Oracle).

Report SQLSELECTCOA_PRODUCT_HZ.LVL_0_PRODUCT_CODE || ' - ' ||

COA_PRODUCT_HZ.LVL_0_PRODUCT_DESC, COA_PRODUCT_HZ.LVL_1_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_1_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_2_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_2_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_3_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_3_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_4_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_4_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_5_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_5_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_6_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_6_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_7_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_7_PRODUCT_DESC,COA_PRODUCT_HZ.LVL_8_PRODUCT_CODE || ' - ' || COA_PRODUCT_HZ.LVL_8_PRODUCT_DESC,



COA_PRODUCT_VR.PRODUCT_ANCESTOR, COA_PRODUCT.CHART_OF_ACCT_NAMEFROM COA_PRODUCT_HZ, COA_PRODUCT_VR, COA_PRODUCTWHERE (

COA_PRODUCT.CHART_OF_ACCT_ID=COA_PRODUCT_VR.CHART_OF_ACCT_ID and

COA_PRODUCT.PRODUCT_CODE=COA_PRODUCT_VR.PRODUCT_DESCENDENT )

AND ( COA_PRODUCT.CHART_OF_ACCT_ID=COA_PRODUCT_HZ.CHART_OF_ACCT_ID and

COA_PRODUCT.PRODUCT_CODE=COA_PRODUCT_HZ.PRODUCT_CODE ) AND ( COA_PRODUCT.CHART_OF_ACCT_NAME = @prompt('Chart Of Account

Name:','A','Coa Product\Chart Of Acct Name',Mono,Free,Persistent,,User:0) AND ( COA_PRODUCT_VR.PRODUCT_ANCESTOR in @Prompt('Select Multiple Parent

Products for Group','A','Coa Product Vr\Product Ancestor',multi,free) )


ReportsAccount Segment Dimensions - Recommended Joins 4

Account Segment Dimensions - Recommended Joins

Four of the fact tables (EXPENDITURE_REV_FACT, EXPENDITURE_COST_FACT, EVENT_DIST_FACT, BUDGET_LINE_FACT) are joined with account segment dimensions through CODE_COMBINATION. This section shows how to join CODE_COMBINATION to the account segment fact tables.

Fact Table Dimension Table Join

CODE_COMBINATION COA_COST_CENTER_HZ

CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER_HZ.CHART_OF_ACCT_ID and CODE_COMBINATION.COST_CENTER_CODE=COA_COST_CENTER_HZ.COST_CENTER_CODE

CODE_COMBINATION COA_COST_CENTER_VR

CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.COST_CENTER_CODE=COA_COST_CENTER_VR.CST_CTR_DESCENDENT

CODE_COMBINATION COA_COST_CENTER_VR

CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.COST_CENTER_CODE=COA_COST_CENTER_VR.CST_CTR_ANCESTOR

CODE_COMBINATION COA_COST_CENTER CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER.CHART_OF_ACCT_ID and CODE_COMBINATION.COST_CENTER_CODE=COA_COST_CENTER.COST_CENTER_CODE

CODE_COMBINATION COA_ACCOUNT CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_ACCOUNT.ACCOUNT_CODE


ReportsAccount Segment Dimensions - Recommended Joins4

CODE_COMBINATION COA_ACCOUNT_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_ACCOUNT_VR.ACCNT_DESCENDENT

CODE_COMBINATION COA_ACCOUNT_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COST_CENTER_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_ACCOUNT_VR.ACCNT_ANCESTOR

CODE_COMBINATION COA_ACCOUNT CODE_COMBINATION.CHART_OF_ACCT_ID=COA_ACCOUNT.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_ACCOUNT.ACCOUNT_CODE

CODE_COMBINATION ACCOUNT_TYPE CODE_COMBINATION.ACCOUNT_TYPE_CODE=ACCOUNT_TYPE.ACCOUNT_TYPE_CODE

CODE_COMBINATION COA_COMPANY_HZ CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COMPANY_HZ.CHART_OF_ACCT_ID and CODE_COMBINATION.COMPANY_CODE=COA_COMPANY_COMPANY_CODE

CODE_COMBINATION COA_COMPANY_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COMPANY_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_COMPANY_VR.COMPANY_DESCENDENT

CODE_COMBINATION COA_COMPANY_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COMPANY_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.ACCOUNT_CODE=COA_COMPANY_VR.COMPANY_ANCESTOR



ReportsAccount Segment Dimensions - Recommended Joins 4

CODE_COMBINATION COA_COMPANY CODE_COMBINATION.CHART_OF_ACCT_ID=COA_COMPANY.CHART_OF_ACCT_ID and CODE_COMBINATION.COMPANY_CODE=COA_COMPANY.COMPANY_CODE

CODE_COMBINATION COA_PROJECT_HZ CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PROJECT_HZ.CHART_OF_ACCT_ID and CODE_COMBINATION.PROJECT_CODE = COA_PROJECT.PROJECT_CODE

CODE_COMBINATION COA_PROJECT_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PROJECT_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.PROJECT_CODE=COA_PROJECT_VR.PROJECT_DESCENDENT

CODE_COMBINATION COA_PROJECT_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PROJECT_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.PROJECT_CODE=COA_PROJECT_VR.PROJECT_ANCESTOR

CODE_COMBINATION COA_PROJECT CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PROJECT.CHART_OF_ACCT_ID and CODE_COMBINATION.PROJECT_CODE=COA_PROJECT.PROJECT_CODE

CODE_COMBINATION COA_PRODUCT_HZ CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PRODUCT_HZ.CHART_OF_ACCT_ID and CODE_COMBINATION.PRODUCT_CODE = COA_PRODUCT.PRODUCT_CODE

CODE_COMBINATION COA_PRODUCT_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PRODUCT_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.PRODUCT_CODE=COA_PRODUCT_VR.PRODUCT_DESCENDENT



ReportsAccount Segment Dimensions - Recommended Joins4

CODE_COMBINATION COA_PRODUCT_VR CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PRODUCT_VR.CHART_OF_ACCT_ID and CODE_COMBINATION.PRODUCT_CODE=COA_PRODUCT_VR.PRODUCT_ANCESTOR

CODE_COMBINATION COA_PRODUCT CODE_COMBINATION.CHART_OF_ACCT_ID=COA_PRODUCT.CHART_OF_ACCT_ID and CODE_COMBINATION.PRODUCT_CODE=COA_PRODUCT.PRODUCT_CODE

CODE_COMBINATION COA_FUND CODE_COMBINATION.CHART_OF_ACCT_ID=COA_FUND.CHART_OF_ACCT_ID and CODE_COMBINATION.FUND_CODE=COA_FUND.FUND_CODE

CODE_COMBINATION COA_INTERCOMPANY CODE_COMBINATION.CHART_OF_ACCT_ID=COA_INTERCOMPANY.CHART_OF_ACCT_ID and CODE_COMBINATION.INTERCOMPANY_CODE=COA_INTERCOMPANY.INTERCOMPANY_CODE

CODE_COMBINATION COA_DISTRICT CODE_COMBINATION.CHART_OF_ACCT_ID=COA_DISTRICT.CHART_OF_ACCT_ID and CODE_COMBINATION.DISTRICT_CODE=COA_DISTRICT.DISTRICT_CODE



BusinessObjects Projects Rapid Mart for Oracle Applications User’s Guide

Universe

chapter

UniverseOverview5
Overview
The BusinessObjects Oracle Projects Rapid Mart comes with a single universe called Oracle Apps Projects. It is a union of the Rapid Mart subject areas. This chapter describes overall universe design principles, and details of each subject area as well as common dimensions. The BusinessObjects Projects Rapid Mart for Oracle Applications supports analysis of data in the Projects module of Oracle Applications. Oracle Projects module provides a complete enterprise project management solution including separate submodules for Project Management, Costing, Billing, and Resource Management.To support these processes Oracle Applications uses shared project and project task definition, Accounting Flexfield segments, set of books, currency, other master data, and numerous reference data. Projects module is a sub-ledger of Oracle Financials General Ledger. Project transactions entered in the Projects module are associated with Accounting flexfields segments. The Accounting Flexfield segments are user-defined financial dimensions, such as Account, Cost Center, Company, Product, etc. They are configured during Oracle Applications implementation and cannot be changed once Oracle Applications are rolled-out.Organizations, Tasks, and accounting dimensions, or Accounting Flexfield segments, can be organized into hierarchy (or tree) structures to support various financial analysis. The hierarchies are available in the universe in both horizontal and vertical formats to facilitate multiple forms of analysisThe Oracle Apps Projects universe is a reflection of these processes. At this writing, it has:

• 175 Classes• 1803 Objects• 68 Tables• 10 Aliases• 176 Joins• 8 Contexts• 10 Hierarchies• 78 Conditions

The universe is well documented and logically organized to help universe users easily navigate to a specific object.The information in this chapter is useful to understand the data in the Rapid Mart and how to build reports using the data. The universe, and this chapter are logically grouped into subject area groups. They are:


UniverseOverview 5

• Common Dimensions• Budget Line Subject Area• Budget Summary Subject Area• Project Summary Subject Area• Project Transaction Summary Subject Area• Project Asset Subject Area• Event Distribution Subject Area• Expenditure Cost Subject Area• Expenditure Revenue Subject AreaAdditionally, you find sections on:Hierarchies Customizing the UniverseUniverse Validation

Universe Design PrinciplesThe Oracle Applications Projects universe design principles presented below are designed to help you better understand the universe content and how to use it.

Universe TerminologyStar Schema: also called Subject Area. The dimensional data modeling approach. A star schema has one large central table (fact table) and a set of smaller attendant tables (dimension tables) displayed in a radial pattern around the central table.Dimension Table: a table where the textual descriptions are stored.Fact Table: a table where the numerical measurements of the business are stored. Each of these measurements is taken at the intersection of all the dimensions. The fact table, if it represents a transactional table, might also store some transaction descriptive attributes if there is no a proper dimension for this attribute. Measure: numeric additive or semi-additive quantities or amounts like Burdened Cost TRX, Raw Cost TRX, Burdened Change TRX, etc.Summary Measure: numeric additive or semi-additive quantities or amounts calculated from dimension table quantities or amounts.


UniverseOverview5

Objects: descriptive non-additive attributes used to describe the measure, and master data such as Vendor Name, Currency Name, Set of Books Name, Event Type.Additive Measure: a measure that can be summarized across all attributes; such as Approved Amt in transactional currency for each set of books.Semi-Additive Measure: measure that can be summarized only across selected dimensions, such as Total Line Rev Amount PRJ (in project currency).Non-Additive Measure: measures that cannot be summarized, such as Utilization Percent in Budget Line Fact measures.Attribute: descriptive information; cannot be aggregated, such as account number, cost center code, etc.Detail: a transaction attribute, such as Event Num , Budget Status, Draft Revenue Num, etcSubject: in most cases associated with the fact table name. Subjects include: Budget Line, Budget Summary, Event, Expenditure Cost, Expenditure Revenue, Project Asset, Project Summary, Project Transaction Summary.Business Function/Process: processes and functions in ERP applications that are captured when entering a transaction (for example, Event Distribution). In the Universe, it is a logical grouping of attributes by function or processes related to the subject. Examples are Event Id, Event Num, Event Dist Line Num, Draft Revenue Num, Draft Invoice Num, Creation Date, Event Type Id, etc.Common Dimension: a dimension table that is associated with multiple fact tables; such as Event Type, Currency, Set of Books, segments of the Accounting Flexfield (Account, Cost Center, etc.).

Universe Table LayoutThe Rapid Mart data model uses star design principle. Fact tables are used to store measures and dimension tables to store attributes. An exception is dimensions that represent segments of Accounting Flexfield. There is an additional dimension, Code Combination, that connects measures to segment attributes. This snow flake principle is used to simplify ETL loading process. The universe table layout follows the Rapid Mart data model. Fact tables are placed vertically in the middle of the universe between two parallel rows of dimension tables.Dimensions are grouped logically by business function or process. These groups are documented in the universe graphical layout. There are screen shots of the graphical layout for each subject area in this chapter.


UniverseOverview 5

Example: “Budget Line Filters” on page 187.

Join StrategyContexts: Dimensions that relate to multiple fact tables (common dimensions) are joined to each of those fact tables. No aliasing of the dimensions is used. Instead, a context for each fact table has been created and all dimensional joins for that fact table are included in the context.Aliases: Aliases are used when the same dimension describes different business processes. For example, the Currency dimension needs to be associated with different processes – Transactional currency code, Project currency code, Project Functional currency code, and GL Functional currency code. All of these may be in the same subject area (fact table). In this case, there will be a Currency Dimension alias for each process.Facts to Fact Joins: Fact tables are not joined with each other unless they represent the same subject and have similar granularity. Facts as Dimensions: In some cases a fact is a dimension to another fact. For example, DRAFT_REVENUE_FACT is a dimension to EVENT_DIST_FACT. In this case, however, we do not join DRAFT_REVENUE_FACT directly. Instead we use a derived table to join these facts as dimensions. See Derived Tables below for more details.Derived Tables: Derived tables are viewed defined within the Universe.This universe contains three derived tables DRAFT_INVOICE, DRAFT_REVENUE, and EXPENDITURE (based on DRAFT_INVOICE_FACT, DRAFT_REVENUE_FACT, and EXPENDITURE_FACT respectively). These derived tables can then be joined to other relevant fact tables (for example, DRAFT_REVENUE is joined to EVENT_DIST_FACT) instead of creating aliases.Inner Joins Only: The universe uses inner joins only. The Data Integrator job loads a default row in each dimension table. The row is populated with the default text (defined by a Data Integrator global variable) as primary key. Example: We load a row with default text in the Event Type dimension. When an event has no Event Type, we load that same default text as the foreign key from the event type status to the Event Distribution table. In this way we can avoid outer joins that can slow database performance. Short Cut Joins: When a dimension is both joined to a fact table and also to another dimension table we use a “short cut” join for the fact table join. Example: Table COA_ACCOUNT_VR is joined to both the COA_ACCOUNT table and CODE_COMBINATION table. The join to the CODE_COMBINATION is a “short cut” join.


UniverseOverview5

Complex Joins: Conditions include usage of the @prompt() function to allow users selecting appropriate constraints during report design.

Universe Objects & ClassesAll Rapid Mart dimension and fact table columns are exposed as objects. Universe objects are grouped in folders and sub-folders. These folders and sub-folders are also called classes. The top level classes are shown below:Oracle Application Projects Top Level Classes:


UniverseOverview 5

Measures: The first Top Level class represents the Measures as described in “Universe Terminology” on page 171. Measures are grouped into sub-folders that represent the various star schemas (or subject areas) in the universe. Each subject area is further divided into classes by types of measure specific to the subject area. For example, Project Summary measures includes separate classes for PTD Project Summary Measures (Period to date amounts, quantities, and labor hours are stored here), ITD Project Summary Measures (Inception to date amounts, quantities, and labor hours are stored here), and PTD Project Summary Measures (Year to date amounts, quantities, and labor hours are stored here), and Prior Period Project Summary Measures (Prior period amounts, quantities, and labor hours are stored here).Summary Measures: These measures are grouped into sub-folders that represent the various dimensions in the universe that contain amounts or quatities are additive or semi-additive. For example, DRAFT_REVENUE contains amounts that can be aggregated, including Total Line Rev Amount PRJ, Avg Unbilled Receivable Debit PRJ, Avg Unearned Revenue Credit PRJ, etc.Common Dimensions: These top level classes appear after the Measures. They start with Chart of Accounts Dimensions and end with Accounting Distribution Related Dims. These are the dimensions used in common by more than one subject areas. These are sub-divided into classes for each specific dimension table. For example, the Budget Line Fact Dims class has sub-classes for Baselined by Person, Project Agreement, and Revenue Category. Each of these represents a specific dimension table or alias of a dimension table. The Common Dimensions Matrix (presented later in this chapter) details which subject areas can be used with which common dimensions.Subject Areas: Following the Common Dimensions are group of Top Level classes, one for each subject area (or star schema) in the universe. The first of these is the “Budget Line Fact” subject area, the last “Project Txn Summary Fact”.Filters: This top level folder represents pre-defined conditions that can be included in any report. Again, they are organized by subject area.Techniques: These are advanced technique objects that have developed for the Web Intelligence reports.• Indexes: The index technique enables multiple measures to be returned

in a single data provider while providing different conditions for different groups of measures.


UniverseOverview5

For example, using indexes it is possible to return the total revenue, revenue lost for returned items, and last year’s revenue all in a single data provider, and using a single revenue object. Without this technique multiple synchronized queries would be needed.Think of indexes as providing vertical breaks in a single data provider. Local variables can then be created using the index values.

• Zeros: These perform a similar function to indexes, namely they provide a means to return filtered information in a single data provider. Just as Indexes provide vertical breaks for measures, Zeros provide horizontal breaks. This is often requires when comparing two time periods.For example, you want to compare balances for certain account for each quarter this year. However, the account had no balances in third quarter. Without use of the Zeros technique the data for 3rd quarter would be missing in the report. With Zeros, a placeholder value (with zero value) is shown.

• Blanks & Labels: Their purpose is to provide an additional object that can be used in a display block. An example is a label that returns total GL balances, where a normal query would only provide breakdowns by some category.Blanks return the max(‘ ‘) function (a space) and labels return a hard coded text. Normally, this text is the same as the name of the object.


UniverseCommon Dimensions 5

Common DimensionsCommon Dimensions are those that are shared by more than one subject area (or fact table). They appear as shown below in the universe.Common Dimension Classes:


UniverseCommon Dimensions5

Chart of Accounts: All sub-classes and objects within Chart Of Accounts class represent Accounting Flexfield segments. Segments are user-defined and can their meaning varies between Oracle Applications implementations. Out-of-the-box Rapid Mart comes with pre-defined eight most common entities that many organizations define for the flexfield segments to represent General Ledger dimensions:• Company - a segment that indicates legal entities for commercial

organizations;• Fund - a segment that indicates a fiscal and accounting entity with a self-

balancing set of accounts for non-profit or governmental organizations;• Cost Center (Department) - a segment that indicates functional areas;• Account - a segment that represents natural account;• Product - a segment that indicates products or product groups

manufactured by a commercial organization;• Project - a segment that indicates projects for which revenue and

expenses need to be tracked;• District - a segment that represents geographical locations;• Intercompany - a segment to represent subsidiaries in a multi-company

environment. See “Accounting Flexfield” on page 294 of the Chapter 8: Technical Implementation for more details on the Accounting Flexfield and Rapid Mart customizing.The flexfield segment dimensions are common to all the fact tables in the Rapid Mart and have similar structure.Coa Account: Contains natural account id along with the descriptions. There is one object Full Account Name, which contains the combined account code and account description. The sub-class is a parent for Coa Account Hz and Coa Account Vr sub-classes that contain account hierarchy objects. For horizontal hierarchy, it contains level 0 account code to level 8 account code along with description and full account name. For vertical hierarchy, it contains, account ancestor, descendent along with depth, leaf and root flag.Coa Cost Center: This dimension class is cost center specific which contains cost center id along with the descriptions. There is one another object called Full Center Name, which contains the combined cost center code and description. The sub-class is a parent for Coa Cost Center Hz and Coa Cost Center Vr sub-classes that contain cost center hierarchy objects. For horizontal hierarchy, it contains level 0 cost center code to level 8 cost center code along with description and full cost center name. For vertical hierarchy, it contains, cost center ancestor, descendent along with depth, leaf and root flag.



Coa Company: The sub-class contains company id along with the descriptions. There is one another object called Full company Name, which contains the combined company code and description. The sub-class is a parent for Coa Company Hz and Coa Company Vr sub-classes that contain cost center hierarchy objects. For horizontal hierarchy, it contains level 0 company code to level 8 company code along with description and full company name. For vertical hierarchy, it contains, company ancestor, descendent along with depth, leaf and root flag.Coa Project: This dimension sub-class is project specific which contains project id along with the descriptions. There is one another object called Full project Name, which contains the combined project code and description. The sub-class is a parent for Coa Project Hz and Coa Project Vr sub-classes that contain project hierarchy objects. For horizontal hierarchy, it contains level 0 project code to level 8 project code along with description and full project name. For vertical hierarchy, it contains, project ancestor, descendent along with depth, leaf and root flag.Coa Product: This dimension sub-class is product specific which contains product id along with the descriptions. There is one another object called Full product Name, which contains the combined product code and description. The sub-class is a parent for Coa Product Hz and Coa Product Vr sub-classes that contain cost center hierarchy objects. For horizontal hierarchy, it contains level 0 product code to level 8 product code along with description and full product name. For vertical hierarchy, it contains, product ancestor, descendent along with depth, leaf and root flag.Coa Fund: The sub-class is fund specific with fund id along with the description objects. Coa District: The sub-class is geography (district) specific with district id along with the description objects. Coa Intercompany: The sub-class is intercompany specific with inter-company id along with the description objects. Coa Segment: When Oracle Applications installations are configured with multiple chart of accounts, the same entity (such as Cost Center) can correspond to different segments with different user-defined names (such as ‘COST CENTER’, ‘Cost Centre’, ‘CC’, etc.). This sub-class allows viewing segment name assignment to the Rapid Mart dimensions.Code Combination Details: Groups details for Oracle Applications Accounting Flexfield. Currency: This Rapid Mart carries measures in four currencies: transactional, project, project functional, and GL functional. All these currencies are maintained in Oracle Applications.



Set of Books: This dimension represents the set of books information. Set of books id, name associated chart of account information, currency code and period information.Organization Structure: Represents the various groupings and business entities within the company that are associated with the business process. Oracle Applications allow creating more than one organization grouping (or structure) and multiple versions for each grouping. This dimension class also includes organization specific which contains Org id along with the descriptions. Organization address and related informations are stored under organization geography sub-class. The Organization sub-class is a parent for Org Primary Hier Hz and Org Primary Hier Vr sub-classes that contain organization hierarchy objects. For horizontal hierarchy, it contains level 0 org level code to level 9 org level code along with description and full organization level name. For vertical hierarchy, it contains, org ancestor, descendent along with depth, leaf and root flag.Period Calendar: This dimension is used to segregate the data into groupings by fiscal periods. The calendar can have multiple period sets. Time Dimensions: These are used to segregate the data into groupings by calendar periods such as month or year, and by Fiscal Periods & Fiscal Year. The dates segregated by time dimensions include document creation date, transaction date, posting date, etc.Project Period: This dimension is used to segregate the data into groupings by project periods and calendar periods based on project periods. Each project period has association with a fiscal period.Project: This dimension contains information about the Project (highest units of work) defined in Oracle Projects Application.Common Dimensions: Other common dimensions are grouped under this class.

Budget Type: Information on budget types for indicating whichDraft Revenue Summary: Project Draft Revenue fact table at revenue grain containing summarized dataDraft Invoice Summary: Project Draft Invoice fact table at invoice grain containing summarized dataExpenditure Summary: Project Expenditure fact table containing summarized expenditure dataEvent Type: Information on event type for classifying events (Cost Accrual, Invoice Reduction, Payment, etc.)



Expenditure Type: Information on expenditure type (Telecommunications, Consulting, Supplies, etc) and category (Labor, Expenses, etc.) for classifying expenditures .Job: Jobs defined per Business GroupProject Class Category: Categorization of project by class category and class code.Project Resource: Identifies project resources and resource typeNon-Labor Resource Organization: Organization information for a non-labor resource organization.Task: Stores project task information (user-defined subdivisions of project work)Vendor: They are the companies and individuals your company buys good and raw materials from. Those vendor related dimensions are grouped here. First one deals with generic vendor. All individual vendor related informations (such as vendor number, vendor name, vendor type code, etc.) are grouped here. Then comes vendor geography that deals with where vendor is located (like address, city, state and country information). Various vendor site related information are stored in vendor site dimension grouping.

Budget Line Fact Dims: As the name implies these dimensions relate only to Budget Line Fact. This class includes Baselined by Person, Project Agreement, and Revenue Category.Project Txn Summary Fact Dims: As the name implies these dimensions relate only to Project Txn Summary Fact. This class includes Accum for Person.Expenditure Cost Fact Dims: As the name implies these dimensions relate only by Expenditure Cost Fact. This class includes Cost Distribution Type, Receiver Project Period, and Transfer Status.Project Asset Fact Dims: As the name implies these dimensions relate only to Project Asset Fact. This class includes Asset Category, Asset Location, Assigned to Person, and Asset Book type.Event Dist Fact Dims: As the name implies these dimensions relate only to Event Dist Fact. This class includes the Event dimension.


Common Dimensions Matrix
Because the common dimensions are shown in their own top level classes, it can be difficult to tell which dimensions to use with each subject area. The two tables below are a cross-reference matrix of common dimensions and subject areas showing exactly which common dimensions to use with each subject area.Dimensions Matrix Part 1



Dimensions Matrix Part 2

Below is a brief description of each of the subject areas, its objects, common dimensions, measures, and filters. Use this section to you familiarize yourself with the universe structure.

Currency MatrixThe eight fact tables included in the universe use a combined nine different currencies. In order to simplify universe design, the universe includes only four major currencies (Transactional, Project, Project Functional, and GL Functional. This currency matrix identifies currency mappings between Oracle and the Rapid Mart Fact tables.



Currency Matrix


UniverseBudget Line Subject Area 5

Budget Line Subject AreaThe Budget Line section is a comprehensive source of information about organization budget information at the budget line level. The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications projects budget line tables.

Budget Line MeasuresThe budget line measures contains all the measures used with budget line fact. They appear as shown below in the universe.

This class contains several measures relating to quantities and also contains one sub-class with all budget line amounts in project currency.


UniverseBudget Line Subject Area5
Budget Line Details Class and Objects
The Budget Line Details class contains all remaining objects for budget line. They appear as shown below in the universe:

This class contains all the information about budget line attributes and measures (as non-additive attributes). All the budget line columns are exposed as objects here. It includes Budget Line ID, Budget Type, Budget Status, Version Name, and Version Number (among others). This class contains three sub-classes to further organize budget line details, including:• Budget Line - Amounts and Quantities (amounts and quantities)• Budget Line - Dates (related dates)• Budget Line - Detail & IDs (typically foreign keys to dimension tables)


UniverseBudget Line Subject Area 5

Budget Line FiltersThere are two filters provided in this universe to use against Budget Line data, as shown below:

Budget Line Star Schema Layout


UniverseBudget Summary Subject Area5
Budget Summary Subject Area
The Budget Summary section is a comprehensive source of summarized budget information.The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications projects budget accumulation tables. It contains summarized inception-to-date, year-to-date, period-to-date, and prior period budget data.

Budget Summary MeasuresThe budget summary measures contains all the measures used with budget summary fact. They appear as shown below in the universe:

This class contains five sub-classes that contain Budget Summary amounts in project currency. The classes are grouped by summarazation type: PTD (period to date measures), ITD (inception to date measures), YTD (year to date measures), Prior Period, and Total (not summarized by period).


UniverseBudget Summary Subject Area 5

Budget Summary Details Class and ObjectsThe Budget Summary Details class contains all remaining objects for budget summary. They appear as shown below in the universe.


UniverseBudget Summary Subject Area5

This class contains all the information about budget summary attributes and measures (as non-additive attributes). All the budget summary columns are exposed as objects here. It includes Project Accum Id, Budget Type Code, and Project Id (among others). This class contains the following sub-classes to further organize budget summary details:• Budget Sumary - Amts & Qty

• Budget Summary ITD• Budget Summary YTD• Budget Summary PTD• Budget Summary PP

Budget Summary Star Schema Layout


UniverseProject Summary Subject Area 5

Project Summary Subject AreaThe Project Summary section is a comprehensive source of summarized project costing and revenue information.The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications projects accumulation tables. It contains summarized inception-to-date, year-to-date, period-to-date, and prior period project summary data.

Project Summary MeasuresThe project summary measures contains all the measures used with project summary fact. They appear as shown below in the universe:

This class contains four sub-classes that contain Project Summary amounts in project currency. The classes are grouped by summarazation type: PTD (period to date measures), ITD (inception to date measures), YTD (year to date measures), and Prior Period.


UniverseProject Summary Subject Area5
Project Summary Details Class and Objects
The Project Summary Details class contains all remaining objects for project summary. They appear as shown below in the universe.

This class contains all the information about project summary attributes and measures (as non-additive attributes). All the project summary columns are exposed as objects here. It includes Project Accum Id, Org Id, and Period Name (among others).This class contains the follwing sub-classes to further organize project summary details, including:• Project Summary - Amts & Qty (amounts and quantities)

• Project Summary ITD• Project Summary PTD• Project Summary PP


UniverseProject Summary Subject Area 5

• Project Summary YTD

Project Summary Star Schema Layout


UniverseProject Transaction Summary Subject Area5
Project Transaction Summary Subject Area
The Project Transaction Summary section is a comprehensive source of summarized project costing and revenue transaction information.The BusinessObjects Oracle Projects Rapid Mart extracts records from Oracle Applications projects accumulation tables. It contains contains summarized project data at the lowest level of detail.

Project Transaction Summary MeasuresThe project transaction summary measures contains all the measures used with project transaction summary fact. They appear as shown below in the universe:

This class contains several measures relating to quantities and contains all amounts in project currency.


UniverseProject Transaction Summary Subject Area 5

Project Transaction Summary Details Class and ObjectsThe Project Transaction Summary Details class contains all remaining objects for project transaction summary. They appear as shown below in the universe.

This class contains all the information about project transaction summary attributes and measures (as non-additive attributes). All the project transaction summary columns are exposed as objects here. It includes Txn Accum Id, Creation Date, Expenditure Category, Event Type Classification, and Week Ending Date (among others).This class contains two sub-classes to further organize project transaction summary details, including:• Project Txn Summary - Details & IDs• Project Txn Summary - Amts & Qty


UniverseProject Transaction Summary Subject Area5
Project Transaction Summary Star Schema Layout

UniverseProject Asset Subject Area 5

Project Asset Subject AreaThe Project Asset section of this Rapid Mart holds capital and retirement adjustment assets for capital projects.The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications projects asset tables at the asset line level of detail.

Project Asset MeasuresThe project asset measures contains all the measures used with project asset fact. They appear as shown below in the universe:

This class contains four project asset amounts in project currency.


UniverseProject Asset Subject Area5
Project Asset Details Class and Objects
The Project Asset class contains all remaining objects for project asset fact. They appear as shown below in the universe.

This class contains all the information about project asset attributes and measures (as non-additive attributes). All the project asset columns are exposed as objects here. It includes Asset Name, Asset Number, Project Asset Id, and Original Asset Cost (among others).This class contains two sub-classes to further organize project asset details, including:• Project Asset - Details & IDs (contains foreign keys to dimension tables)• Project Asset - Dates (related dates)


UniverseProject Asset Subject Area 5

Project Asset Star Schema Layout


UniverseEvent Distribution Subject Area5
Event Distribution Subject Area
The Event Distribution section of this Rapid Mart contains summary level transactions generating revenue and/or billing activity that are not directly related to any expenditure items.The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications event tables and holds detailed data distributed against the account segment.

Event Distribution MeasuresThe event distribution measures contains all the measures used with event distribution fact. They appear as shown below in the universe:

This class contains event distribution measures project currency and project functional currency.


UniverseEvent Distribution Subject Area 5

Event Distribution Details Class and ObjectsThe Event Distribution class contains all remaining objects for event distribution fact. They appear as shown below in the universe.

This class contains all the information about event distribution attributes and measures (as non-additive attributes). All the event distribution columns are exposed as objects here. It includes Event Num, Event Dist Line Num, Draft Revenue Num, and Draft Invoice Num (among others)This class contains three sub-classes to further organize event distribution details, including:• Event Dist - Amt & Qty (amounts and quantities)• Event Dist - Currency• Event Dist - Details & IDs (contains foreign keys to dimension tables


UniverseEvent Distribution Subject Area5

Note: Event distribution fact carries many currencies,however, in the universe this fact table only joins to the Currency dimension through aliases for Project and Project Functional currencies.

Event Distribution Star Schema Layout


UniverseExpenditure Cost Subject Area 5

Expenditure Cost Subject AreaThe Expenditure Cost section of this Rapid Mart contains details of expenditure item costs incurred by an employee or organization and project cost distributions across accounting flexfield segments.The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications expenditure cost tables and holds detailed data distributed against the account segment.

Expenditure Cost MeasuresThe expenditure cost measures contains all the measures used with expenditure cost fact. They appear as shown below in the universe:

This class contains quantity measures and also contains two sub-class for expenditure cost amounts. These sub-classes group amounts into Transactional (TRX) and Project (PRJ) currencies.


UniverseExpenditure Cost Subject Area5
Expenditure Cost Details Class and Objects
The Expenditure Cost class contains all remaining objects for expenditure cost fact. They appear as shown below in the universe.

This class contains all the information about expenditure cost attributes and measures (as non-additive attributes). All the expenditure cost columns are exposed as objects here. It includes Expenditure Item Id, Line Num, Line Type, and Period Name (among others).This class contains four sub-classes to further organize expenditure cost details, including:• Expenditure Cost - Amounts & Qty (amounts and quantities)• Expenditure Cost - Dates (related dates)• Expenditure Cost - Detail & IDs (contains foreign keys to dimension

tables)


UniverseExpenditure Cost Subject Area 5

• Expenditure Cost - CurrencyNote: Expenditure cost fact carries many currencies,however, in the universe this fact table only joins to the Currency dimension through aliases for Project and Transactional currencies.

Expenditure Cost Star Schema Layout


UniverseExpenditure Revenue Subject Area5
Expenditure Revenue Subject Area
The Expenditure Revenue section of this Rapid Mart contains details of expenditure item revenues incurred by an employee or organization and project revenue distribution across accounting flexfield segments.The BusinessObjects Oracle Projects Rapid Mart extracts all records from Oracle Applications expenditure revenue tables and holds detailed data distributed against the account segment

Expenditure Revenue MeasuresThe expenditure revenue measures contains all the measures used with expenditure revenue fact. They appear as shown below in the universe:

This class contains expenditure revenue amounts in project and project functional currencies.


UniverseExpenditure Revenue Subject Area 5

Expenditure Revenue Details Class and ObjectsThe Expenditure Revenue class contains all remaining objects for expenditure revenue fact. They appear as shown below in the universe.

This class contains all the information about expenditure revenue attributes and measures (as non-additive attributes). All the expenditure revenue columns are exposed as objects here. It includes Expenditure Item Id, Draft Revenue Num, Draft Invoice Num, GL Period Name, and Additional Revenue Flag (among others).• Expenditure Rev - Amounts & Qty (amounts and quantities)• Expenditure Rev - Dates (related dates)• Expenditure Rev - Detail & IDs (contains foreign keys to dimension

tables)


UniverseExpenditure Revenue Subject Area5

• Expenditure Rev - CurrencyNote: Expenditure revenue fact carries many currencies,however, in the universe this fact table only joins to the Currency dimension through aliases for Project and Project Functional currencies.

Expenditure Revenue Star Schema Layout


UniverseHierarchies 5

Hierarchies

Hierarchies OverviewIn general, hierarchies allow users to perform multi-dimensional analysis. Multi-dimensional analysis uses dimension objects organized in a meaningful order. Multi-dimensional analysis allows users to observe data from various viewpoints. This enables them to spot trends or exceptions in the data.A hierarchy is an ordered series of related objects. An example of a hierarchy is time, or “date”, which may group objects as Year, Quarter, and Month. You can use drill up or down to perform multi dimensional analysis with a hierarchy. Time is an example of a horizontal hierarchy where each level in the hierarchy is presented as a column in a database table. Thus, Year, Quarter, Month, and Date are all column names.You can use this hierarchy in a report to drill down from a higher level of aggregation (year) to a more detailed level (quarter). You can also drill up from quarter to year.The hierarchies appear both as sub-classes in the common dimensions of the universe and in their own display screen in Web Intelligence (as shown below). The universe contains 12 hierarchies.


UniverseHierarchies5
Time Dimension and Period Hierarchies
Time dimensions allow you to organize reports by calendar attributes such as calendar year, calendar month and calendar quarter. Fiscal Period Calendar dimensions allow you to organize reports by the fiscal calendar periods, fiscal quarters, fiscal years, etc. the Project Period dimension allows organizing reports by calendar year, month, and quarter (corresponding to the project period). The hierarchies in this category are:

• Time Dimension• Period Calendar Dimension• Project Period

Task HierarchyTask dimension allows you to organize reports by tasks (or task levels) identified in a project. The hierarchies in this category are:

• Task Hier Hz

Vendor Geography HierarchyVendor dimension allows you to organize reports by vendor geography attributes like country, state, city, etc. The hierarchies in this category are:

• Vendor Geography Dimension

Organization HierarchyOrganization dimensions allow you to organize reports by various defined organization levels. For this hierarchy, two sub-classes within in the dimension represent the vertical and horizontal hierarchies. The vertical and horizontal hierarchies are explained in detail in the next section. This organization hierarchy has Full Org level 0 Name, Full Org level 1 Name, etc. while the organization geography has attributes like City, State, Country, etc. So, the The hierarchies in this category are:

• Organization Dimension• Organization Geography



Accounting HierarchiesThe BusinessObjects Oracle Projects Rapid Mart has 5 hierarchy dimensions associated with the Accounting Flexfield segments. These hierarchies are organized in both horizontal and vertical format. They are:

• Coa Account• Coa Cost Center• Coa Product• Coa Project • Coa Company

For each of the 5 hierarchies, two sub-classes within in each dimension represent the vertical and horizontal hierarchies. These are shown earlier in this chapter under “Common Dimensions” on page 177. Example: The Account Hierarchy. We will use Account as an example to illustrate how vertical and horizontal hierarchies work together.The illustration below shows a sample set of Accounts organized into a three level hierarchy:

Note: The hierarchy contains a “ragged” node. This happens when a node reports to more than one ancestor (or parent) node. In our example, the node 1421 has two ancestors. This legal and acceptable in Oracle Applications.


Horizontal Hierarchy Structure
Horizontal hierarchies are organized so that all levels (or nodes) appear as columns on a single row of data. Vertical hierarchies represent each level or node with an individual row of data.The horizontal hierarchies for these dimensions are included in the 7 “Accounting Hierarchies” on page 211. The vertical hierarchies for these dimensions are not included because they are primarily used as conditions (or filters) on a report.The horizontal structure for Accounts is the Account Hierarchy Hz class, and the corresponding COA_ACCOUNT_HZ table. Within this table and class, the hierarchy is represented as shown below.Horizontal Hierarchy Structure:

In the horizontal representation, one row shows the entire hierarchy for each node in the hierarchy. However, be careful of the ragged hierarchy nodes. If your query simply selects for Account Code = 1421, you will get two rows returned because Activity 1421 reports to two different sets of ancestors or parents. You must also specify the Level 2 ID (PT or D1000) to uniquely identify the hierarchy.In this case, you could also specify the Level 1 ID (PT or DBI1) to uniquely identify the hierarchy.Optional Propagation of Child (Leaf) Nodes:



Also note that child (leaf) nodes that belong to other than the last hierarchy level (Leaf Level 1 and Leaf Level 2) could be propagated to the lowest Level ID of the hierarchy starting with the Level 1 ID. Leaf level 2 nodes could be propagated out from level 2 ID to the lowest Level ID. Leaf level 3 nodes are propagated out from level 3 ID to the lowest level, etc.

Note propagation is not implemented with the current version of BusinessObjects General Ledger Rapid Mart. Extra levels of hierarchy are set to NULL.

Child (leaf) node propagation allows creating reports with indented listings of Accounts, Cost Centers, and other hierarchical master data where depth of indention depends on the node position (Leaf Level).

Vertical Hierarchy StructureThe vertical structure for the Activities hierarchy is the Account Hierarchy Vr class, and the corresponding COA_ACCOUNT_VR table. The vertical hierarchy uses many more rows to represent the same hierarchy. Each row is



an ancestor / descendant combination showing only a single relationship in the hierarchy. For simplicity, only the “PT” hierarchy is shown in the diagram below:Vertical Hierarchy Structure:

In this representation the Level (or leaf level) indicates how many generations exist between ancestor and descendant. Level 0 indicates no generations (ancestor and descendant the same). Level 1 indicates parent to child, level 2 grandparent to child, level 3 great-grandparent to child, etc.You can find more information on how hierarchies are created in the Data Integrator documentation for the Hierarchy Flattening Transform, Pivot Transform, and Reverse Pivot Transform.



Accounting Flexfield Hierarchy FiltersEach Accounting Flexfield hierarchy class comes with a set of pre-defined filters. Below is detailed description for Account hierarchy filters. The same apply to other four pre-defined Accounting Flexfield hierarchy classes - Cost Center, Product, Project, and Company.

Select Single Parent Account for Group (Vertical Hierarchy): prompts for a single Ancestor Account node to return a group of all Decsendent nodes that belong to the parent.



Select Multiple Parent Accounts for Groups (Vertical Hierarchy): prompts for a multiple Ancestor Account nodes (within the same hierarchy level) to return a group of all Decsendent nodes that belong to the parents. Select Single Account Lvl 0 + (Display): This filter needs be selected in combination with 'Select Single Parent Account for Group (Vertical)' prompt. Use it when you select Ancestors Level 0 parent nodes. It deals with ragged hierarchies and ensures that no duplicate records are returned when the same child node belongs to multiple parents.Select Single Account Lvl 1 + (Display) through Select Single Account Lvl 4 + (Display): Same as above; use this filter when you select Ancestors Level 1 through 4 parent nodes. For additional hierarchy levels, add additional filters.Select Multiple Account Lvl 0 + (Display): This filter needs be selected in combination with 'Select Multiple Parent Accounts for Groups (Vertical)' prompt. Use it when you select Ancestors Level 0 parent nodes. It deals with ragged hierarchies and ensures that no duplicate records are returned when the same child node belongs to multiple parents.Select Multiple Account Lvl 1 + (Display) through Select Multiple Account Lvl 4 + (Display): Same as above; use this filter when you select Ancestors Level 1 through 4 parent nodes. For additional hierarchy levels, add additional filters.

Report Generation - Vertical HierarchyWhen you choose the “Select Single Parent Account for Group (Vertical Hierarchy)” filter in a report, you are prompted to “Select a Single Parent Account for Group” at run time. Entering “PT” selects this subset of data from the Vertical Hierarchy Structure:

This subset contains all relationships in the hierarchy, no matter how many generations are between the ancestor (or parent) chosen and its descendant nodes.



When you include objects from the horizontal “Account Hierarchy Hz” class in the same query, the results will show the entire “family” structure for the selected Account Hierarchy Group. Thus, the vertical hierarchy gives us the selection criteria (via the filter) and the horizontal hierarchy gives us the report contents.As described earlier, the horizontal hierarchy can be used to create an indented report where the each lower level (leaf level) is more indented than the previous level.

Customizing the UniverseWhen implementing BusinessObjects Projects Rapid Mart, the universe needs to be customized to accommodate user-defined Accounting Flexfield segments if they are different from the Rapid Mart out-of-the-box 8 pre-defined dimensions. Once implemented, the universe can be modified easily to suit your specific needs.

Splitting the Universe: The universe was designed to be all inclusive of the subject areas in the Oracle Applications Projects module. This is because it is easier to remove subject areas (and simply the universe) than to add subject areas (and make it more complex).

Example: If you want to keep certain users from seeing expenditure revenue data you can create a copy of the universe and strip out the expenditure revenue Subject Area. (You simply remove the expenditure revenue only tables and objects from the universe).

Additional Common Dimensions: Another modification that is relatively easy is to include additional common dimensions.

Linking the UniverseBusinessObjects Oracle Projects Rapid Mart is designed to be integrated with other Rapid Marts: Purchasing, General Ledger, Fixed Assets, and Accounts Payable. • Expenditure Cost Fact and Expenditure Revenue Fact and Project Asset

Fact can be joined with other fact tables (GL Journal Entry Fact, Invoice Line Fact) to allow drilling across analysis.

• Project Asset Fact can be joined with (Asset Invoice Fact)


UniverseUniverse Validation5
Modify Derived Tables
The universe uses three derived tables (EXPENDITURE, DRAFT_REVENUE, and DRAFT_INVOICE) in order to use additional fact tables as dimensions. These derived table definitions can be customized to suit customer needs.These fact tables (EXPENDITURE_FACT, DRAFT_REVENUE_FACT, and DRAFT_INVOICE_FACT) can also be joined to relevant dimension tables, and built into another subject area in the universe in addition to being used in the derived table definitions.

Universe ValidationWhen validating the universe within the Universe Designer, some errors are expected and acceptable. They do not harm universe performance in any way. They are detailed below.


UniverseUniverse Validation 5

DivergencesThere are 11 tables that are not joined to other tables. This is because we use only aliases of those tables in the universe. However, the original table must remain as a placeholder for the original table name. The screen-shot below details these divergences.

Objects and Conditions ParsingThere are around 119 objects that will fail validation. They can be grouped as:• “@database” function related: “Must declare the variable ‘@database’>

State:42000”. Universe Designer raises an error each time this function is used. It will execute correctly in reports;

• Advanced Technique related: “Line 1: Incorrect syntax near ‘From’. Stage: 42000”. The objects are all template objects that must be customized to your specific needs. These objects execute correctly in reports;


UniverseUniverse Validation5

• Count(*) related warning: “Count definition contains a count without a distinct. Duplicate rows are possible”. Objects with count(*) are executed properly in reports.

Also, note that the error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.The screen-shot below shows the object parsing failures in an Oracle environment.


Installing the Rapid Mart

chapter

Installing the Rapid MartOverview6
Overview
This chapter contains the information you need to install the Projects. The information in this chapter is useful for system administrators or others who install the Rapid Mart.This chapter contains the following sections:• System prerequisites• Rapid Mart product components• Preparing your environment• Installation overview• Installation procedure• Completing the installation• Installing Rapid Mart Reporting Content

System prerequisitesTo run the BusinessObjects Projects Rapid Mart, your system requires:• Data Integrator version 11.5.2 or higher compatible version• An Oracle 9i database or Microsoft SQL Server or IBM DB2 UDB 8

database or compatible version. • Oracle Applications release 11i or higher compatible version• BusinessObjects Enterprise XIR2 if you want to install Rapid Mart

Reporting Content.If you have questions about system prerequisites, contact Business Objects Technical Support.

Rapid Mart product componentsThe Rapid Mart includes several major product components:• A SQL script for defining the Rapid Mart tables• A SQL script for dropping the Rapid Mart tables• An Data Integrator metadata repository that specifies the full load and

incremental update jobs for the following:• Data extract from Oracle Applications • Data load into the Rapid Mart

• SQL scripts to drop and re-create indexes after loading the Rapid Mart


Installing the Rapid MartPreparing your environment 6

• SQL scripts to create database stored procedures. Dummy procedures are created during installation and procedure samples (for oracle only) are available in Sample\DDL directory.

• An ERWin diagram of the data schema• Set of documents which includes business guide, user guide and release

notes • An option to install rapid mart reporting contents that includes

BusinessObjects Enterprise XIR2 WebIntelligence reports and a universe. See “Installing Rapid Mart Reporting Content” on page 229 for details.

Preparing your environmentFollow these steps to prepare your environment for the Rapid Mart installation:1. Install Data Integrator, if it is not already installed.

Refer to the Data Integrator Getting Started Guide for detailed installation instructions.Make sure that you install the Data Integrator Designer and that you install and configure a Job Server and an Access Server.The default Data Integrator installation creates a repository that you can use for your Rapid Mart. You can also create a separate repository for Rapid Mart after the Data Integrator installation using the Repository Manager.Though you need Data Integrator job server to run Rapid Mart jobs, you need just Data Integrator Designer to install Rapid Mart. This designer can connect to any other job server to process jobs.

2. Start Data Integrator and log on to the repository where you are going to install the Rapid Mart.This step ensures that your default connection is set appropriately.

3. Exit Data Integrator.4. Prepare your target data warehouse environment. Currently the Rapid

Mart supports Oracle, MS SQL Server and DB2 as target databases. You have to supply target database connection informations including username and password if you want to create target schema.

5. Confirm your source application version. Some of the Rapid Mart does special processing depending upon the source application version. You are now ready to install the Rapid Mart.


Installing the Rapid MartInstallation overview6

Follow these steps to prepare your environment for the Rapid Mart Reporting Content installation:1. You need to define an environment variable JAVA_HOME to point to

where java.exe exists. Otherwise you will get error message like “Either JAVA_HOME is not defined or the Installer could not find JAVA_HOME. Please define JAVA_HOME upto /bin dir and try again.” For example if you have Business Objects installed in your machine, it generally puts java executable in C:\Program Files\Business Objects\j2sdk1.4.2_08\bin directory. In this case, the JAVA_HOME should be C:\Program Files\Business Objects\j2sdk1.4.2_08

Installation overviewThe installation program:• Ensures that a compatible version of Data Integrator is installed.• Prompts you for information about your system and Rapid Mart

environment.The installation program uses this information to customize the Rapid Mart to conform to your environment before loading the Rapid Mart into the repository.

• Creates the files in the RapidMart\OracleProjects sub-directory of your installation directory, including:• SQL files to create and drop tables, indexes and stored procedures.• Source atl files to import into Data Integrator• Files containing messages and warnings.

• Drops and creates the tables in the target database, if requested.This includes the data tables, staging tables, and a Rapid Mart system table, called AW_JOBEXECUTION, which maintains execution status information.

• Loads and customizes the repository.After the installation program completes, follow the post installation instructions available in the log file (inslog.txt) found in installation directory.

Installation procedureFollow these steps to install the Rapid Mart:


Installing the Rapid MartInstallation procedure 6

1. Put the Rapid Mart CD in your CD drive (on the computer where the Data Integrator Designer is installed). Generally CD pops up the Autorun screen. Otherwise use Windows explorer to go to your CD drive, and then double-click Autorun.exe.

2. This opens up the autorun screen. Select “Install Rapid Mart” option to install Rapid Mart.

3. The Welcome window opens. Read its contents to double confirm the name and version of the Rapid Mart that you are installing and then click Next.

4. The License Agreement window opens. Read its contents and click Yes to indicate that you agree to the product terms and conditions.

5. The Rapid Mart Destination Folder window opens. Verify that the window lists your preferred installation location. To install in the indicated directory, click Next.To install in a different directory, click Browse and select the desired directory.

6. The Repository Logon window opens.Fields vary by the type of database that stores the repository. For information about repository logon fields, see the Data Integrator Designer Guide.Enter the information needed to connect and log on to your Data Integrator repository. You can also “Test” the repository connection. This test will make sure that the connection parameters are correct and a valid Data Integrator repository exists in that connection. Once you are satisfied with the connection parameters click Next.

7. The Rapid Mart Configuration Information window opens.


Installing the Rapid MartInstallation procedure6

Enter or select the configuration for the source datastore, target datastore.

Prompt Description

Source DatastoreName Select or enter the name of the source

datastore from which the Rapid Mart extracts data. For BusinessObjects Projects Rapid Mart, the default value is PS_DS. Installer will create this data store even if the datastore does not exist in the repository.

Application Type Select the type and version of the application server to which you will be connecting. BusinessObjects Projects Rapid Mart decides about further processing based on this input.

Target DatastoreName Select or enter the name of the target

datastore into which the Rapid Mart loads data. For BusinessObjects Projects Rapid Mart, the default value is RM_DS. Installer will create this data store even if the datastore does not exist in the repository.

Target Database InformationDrop and Create DB Objects.

This option will drop (if exists) and create all database objects - tables, indexes and procedures - required for target database schema during the installation process.

Database Type Select the target database type from one of the available types. Depending upon the selected type other options change.

Database connection Name Appears in the case of oracle database type. Enter the tns connection name to connect to target database.

Database Server Name Appears in the case of MS SQL Server database type. Enter the server name on which the SQL server database runs. In case of named instances you may need to add the instance names properly.

Database Name Appears in the case of MS SQL Server database type. Enter the target database name in the SQL Server database.


Installing the Rapid MartInstallation procedure 6

8. If the source or target datastore that you entered does not currently exist in the repository, the Installation process will create these datastores for you.

9. If you select the available source and/or target datastores from the drop down list, the installation process will add the repository objects to these data stores but the existing datastore connection parameters would be lost. In other words, the installation process will overwrite the connection parameters if you select existing datastores.

10. You need to check box on Drop and Create DB Objects in case you want to create target database objects (tables, indexes and procedures) to load the data from the source.

11. If you check the Drop and Create DB Object, then you have to enter target database Information. Test the connection parameters and then click Next.

12. Now the “Review” screen appears. You can verify all the parameters - the repository information, the source and target datastore information and the target data warehouse database information. If you want to modify any of the parameters, you can browse Back, or if you are satisfied click Next.

13. The Setup Status window shows the progress of the installation program, displaying messages as the program prepares files, creates tables, and loads the repository.

14. The Final Instructions window lists steps you must consider before running and using the Rapid Mart in your environment. Read these steps, then click Next.

15. The Installation Succeeded window opens.To see the installation log, click the check box and click Finish.

DB2 Datasource Appears in the case of DB2 database type. Enter the DB2 data source information.

Username Database connection Username. Make sure that the user got privileges to create/drop table, indexes and procedures

Password Database connection Password.

Prompt Description


Installing the Rapid MartCompleting the installation6

The installation log (inslog.txt) is stored in the Rapid Mart installation directory that you have selected during the installation process. The file lists the steps that the installation program completed. Scroll to the bottom of the file to see information about the latest install.

Completing the installationTo complete the installation, start Data Integrator and log in to the Rapid Mart repository. Before using and running the Rapid Mart in your environment, you must complete several steps:• Make sure that you have completed all the steps in the install instructions

(found in the inslog.txt in Rapid Mart installation directory).• If your Job Server runs on a UNIX system, adjust the directory paths in all

Rapid Mart file format definitions to follow the UNIX convention (that is, change “/” to “\”).

• Adjust the properties of your Application Datastore and target datastore using the Data Integrator Designer:• using Datastore Configurations, select the appropriate Database

Type as Default Configuration• adjust the Connection properties, such as database name, user

name, password • Set up local and global variables as required using the Data Integrator

Designer as described in Chapter 7: Using the Rapid Mart.The Projects tab in the object library shows the defined projects.The OracleApps_Projects_Rapid_Mart project contains the job for loading the Rapid Mart—both the initial load and the incremental load. Before running the job that loads the Rapid Mart, you must initialize some variables. For information about executing the Rapid Mart, see Chapter 7: Using the Rapid Mart.

Adjusting Rapid MartRapid Marts are developed against standard out-of-the-box Oracle Applications installation. It is important that during the Rapid Mart implementation you:• Re-import all Rapid Mart source objects (tables, hierarchies, functions,

etc.) to have object customization captured;


Installing the Rapid MartInstalling Rapid Mart Reporting Content 6

• Review each Rapid Mart dataflow to make sure that its Query transform(s) contain(s) proper constraints when extracting data from the source tables. Adjust WHERE condition if necessary. Look for hard-coded constraints and other conditions that need to be customized.

Installing Rapid Mart Reporting ContentRapid Marts come with its own Reporting Content. In order to use these Reporting Content (i.e. supplied WebIntelligence reports and a universe), you must first install them to your BusinessObjects Enterprise XI R2 system and configure a connection to your Rapid Mart target database.If the BusinessObjects Enterprise XI R2 server is located on a different machine, you need to have BusinessObjects Enterprise XI R2 client installed.1. Put the Rapid Mart CD in your CD drive. Generally CD pops up the

Autorun screen. Otherwise use Windows explorer to go to your CD drive, and then double-click Autorun.exe.

2. This opens up the autorun screen. Select “Install Reporting Content” option to install the Reporting Content.

3. The Welcome window opens. Read its contents to double confirm the name and version of the Rapid Mart Reporting Content that you are installing and then click Next.

4. Select the directory to use in which the Rapid Mart Reporting Content will be installed. By default this is set to <PROGRAM FILES>\Business Objects\Rapid Marts\Projects. Click Next.Note: The folder specified is used only as temporary storage during installation. Once the installation is complete, this folder can be removed by re-running the setup program, Setup.exe.

5. Enter a valid login for the BusinessObjects Enterprise XI R2 system to which you wish to publish the Rapid Mart Reporting Content. Click Next.Note: The user name is set to ‘Administrator’ and cannot be changed. The authentication mode is set to ‘secEnterprise’ and cannot be changed.

6. Click Next at the confirmation screen to start installation.7. Now the installer will unpack and release the reporting contents into your

BusinessObjects Enterprise system.8. Click Finish to complete the installation. Remember, you must configure

the universe connection before attempting to run any of the reports.


Installing the Rapid MartInstalling Rapid Mart Reporting Content6

9. You can see any installation issues in the installation log (visuals_inslog.txt) found in the installation directory. Note: Please make sure that the BIAR files are installed successfully by confirming the line “[InstallEntSdkWrapper.main] BIAR File Imported successfully“ in the log file. Note: Also if you re-installing the Reporting Content, make sure that you removed the Rapid Mart Reporting Content supplied objects and universes before re-installing. Note: You can also import the BIAR file manually using BusinessObjects Enterprise XI R2 Import Wizard. The BIAR file can be found in the specified installation directory.

10. Rapid Mart Reporting Content are published to a folder called ‘Rapid Mart Reporting Content’ in your BusinessObjects Enterprise XI R2 system. In this folder you will find a sub-folder with a name that corresponds to the Rapid Mart you have installed. In this sub-folder you will find the reports.


Installing the Rapid Mart 6


Installing the Rapid Mart6


Using the Rapid Mart

chapter

Using the Rapid MartOverview7
Overview
This chapter describes how to execute the Rapid Mart, including information about the variables that the Rapid Mart uses. This chapter also discusses considerations you need to make when customizing the Rapid Mart. The information in this chapter is useful for administrators and others who run or modify the Rapid Mart.Specific topics include:• Recovery framework• Execution status framework• Extraction, transformation and loading process• Batch configuration variables• Customizing the Rapid Mart

Recovery frameworkWhen executing the Rapid Mart, it is important that you do not load any duplicate data and that you do not extract data redundantly, even in cases of failure. There are two mechanisms to ensure that you do not load duplicate data:• Data Integrator automatic recovery feature• Rapid Mart recovery framework

Data Integrator automatic recovery featureWith automatic recovery, Data Integrator records the result of each successfully completed step in a job. If a job fails, you can choose to run the job again in recovery mode. During recovery mode, Data Integrator retrieves the results for successfully completed steps and reruns uncompleted or failed steps under the same conditions as the original job. For recovery purposes, Data Integrator considers steps that raise exceptions as failed steps, even if the step is caught in a try/catch block.To use the automatic recovery feature, you must enable the feature during the initial execution of a job. In the Execution Properties window, select the Enable Recovery check box. The automatic recovery option is useful during testing and development phases. However, use caution with this feature during a production run because the data may lose its integrity if significant changes in Oracle Applications source tables occur between the failed run and the recovery run.


Using the Rapid MartRecovery framework 7

For example, suppose two tables contain related data but are loaded in separate work flows. In this case, the job can fail after successfully completing the work flow that loads the first table but before completing the work flow that loads the second table. During recovery, Data Integrator does not re-run a successfully completed work flow; therefore, the first table is not loaded again. However, Data Integrator will run the work flow that loads the second table during the recovery job. If the work flow loads the entire table regardless of dates, the second table will contain data added to Oracle Applications between the initial run and the recovery run, but the first table will not contain this data. As a result, the two tables will be inconsistent.

Rapid Mart recovery frameworkThe Rapid Mart contains an external execution status table (AW_JOBEXECUTION) that tracks the status of a job’s execution and the time data was extracted. By using the execution status table, the Rapid Mart ensures that data for the proper dates is extracted from the source datastore.With each execution, the Rapid Mart job extracts data between a start date and an end date. If the job fails and is rerun on the same or a subsequent day, the new job uses the failed job’s start date to ensure that all the data is extracted contiguously.Upon execution, a job first checks the status of the last execution of the job. If the last execution failed, the job determines the ending date of the last successful execution. This date becomes the starting date of the next execution of the job. All work flows are re-executed using the same starting date to ensure consistency. For example, if a failed job is restarted on the same day (without using the automatic recovery feature), the restarted job refreshes all tables because the last execution of the job on that day was not successful. If a job continues to fail over several days, the job would continue using the same start date used on the first failed attempt. This ensures that when the job is eventually successful, it extracts the complete set of data that changed since the start date.To maintain consistency with data flowing to Oracle Applications, the Rapid Mart always overlaps one day’s worth of data in incremental loads. For example, if the end date is June 3, the incremental load job extracts data entered or changed on June 3. The next incremental load job extracts data starting with the June 3 date. Up to one day’s worth of duplicate data may be extracted each time the job runs; however, work flows are designed to detect and delete duplicate data from the target data table before reloading the refreshed data. To do this,


Using the Rapid MartExecution status framework7

many work flows use the auto correct load option. The auto correct load option checks for an existing row with the same key as each row flagged as an insert or update activity. If the row exists, this option updates the row. If the row does not exist, this option inserts the row.

Execution status framework The Rapid Mart uses two mechanisms to check the job execution status and control execution: • An execution status table that stores one record for each job. That record

contains:• Status of previous job execution• Starting and ending times of the last attempted execution of the job

• An application programming interface (API) that updates the status table and supports the implementation of restartable jobs and flows

The execution status tableThe Rapid Mart installation procedure creates a table named AW_JOBEXECUTION in the target database.The execution status table has four columns.

How job status is maintainedThe Rapid Mart records a job status for each invocation of a particular job. There are three possible values for job status: • None — The job status is none when the job has never been executed.• Started — Job status is set to started when a new invocation of a job

starts.• Done — Job status is set to done when a job completes successfully.

Table column Description

NAME The name of the job being executed. If the same target datastore is used for more than one repository, you must ensure that all job names are unique.

STATUS The status of this job after the last execution. Possible status values are: started, done, or none.

EXTRACTLOW Last attempted start date of data retrieval. This date is also the ending date of the last successful run of the job.

EXTRACTHIGH Last attempted end date of data retrieval.


Using the Rapid MartExecution status framework 7

When a job is started, the Rapid Mart checks the job’s existing status. If the previous execution of the job did not complete successfully—that is, the job status is not done—the Rapid Mart resets the starting date for data extraction ($G_SDATE) from the value specified in the job initialization script to the ending date of the last successful run (EXTRACTHIGH). You can override the reassignment of the starting date by forcing the starting date to be reset. See “Executing a job with the reset option” on page 238. The Rapid Mart never changes the ending value ($G_EDATE) from the value specified in the initialization script.After checking the job’s existing status, the Rapid Mart sets the status of the job to started, and starts a new execution of the job.When a job successfully completes, the Rapid Mart sets the job’s status to done. If the job does not complete successfully, the job’s status remains set to started. The EXTRACTLOW and EXTRACTHIGH dates remain set to the current values.

The execution status APIThe execution status API updates the execution status table to control gaps in the time sequence of data extraction.The API contains two external functions. These functions mark the start and termination of jobs.• AW_StartJob ($jobname input, $run_mode input, $load_type input, extractlow input/

output, extracthigh date input/output) The InitializeJob script calls this function to initialize a job and check the last execution status. When called for a new job execution, the function inserts a new row into table AW_JOBEXECUTION. When called for a restarted job execution, the function: • Checks the run mode to see if you set the reset option.

If $G_RUN_MODE is RESET, the function resets EXTRACTLOW and EXTRACTHIGH to the $G_SDATE and $G_EDATE values specified in the initialization script.

• Checks the last execution status of the job. If the job status is done, the function sets EXTRACTLOW to the previous value of EXTRACTHIGH, the last successful end date; next, the function sets EXTRACTHIGH to the value of $G_EDATE,


Using the Rapid MartExtraction, transformation and loading process7

which you set in the initialization script. The function returns the values in EXTRACTLOW and EXTRACTHIGH and the Rapid Mart uses these values to update $G_SDATE and $G_EDATE.If the job status is started, the function does not change the value of EXTRACTLOW. Instead, this value remains the end date of the last successful execution. The function does change EXTRACTHIGH to the new value set in $G_EDATE. The function returns the EXTRACTLOW and EXTRACTHIGH values, and the Rapid Mart uses these values to update $G_SDATE and $G_EDATE.

• AW_EndJob(job name) The EndJob script calls this function to change the job status value in the AW_JOBEXECUTION table to done when the job executes successfully.

Executing a job with the reset optionYou can use the reset mode to force the Rapid Mart to assign a new starting extract time for data extracts. Use reset mode to force the starting and ending dates to remain the same as the values set in the initialization script. Note: Using this option may cause gaps in the time sequence of data loaded into target tables. To specify reset mode, edit the job’s initialization script and uncomment the line that sets $G_RUN_MODE to RESET. When using reset mode, be sure that the variable $G_SDATE is set to the appropriate starting date so that no gaps occur.

Extraction, transformation and loading process

The job OracleApps_Projects_Load executes objects that load the BusinessObjects Projects Rapid Mart for Oracle Applications. This job contains:


Using the Rapid MartExtraction, transformation and loading process 7

• Job global variable properties. This window can be accessed by right-clicking on the OracleApps_Projects_Load job and selecting the Properties command from the drop-down list. Most of the Projects Rapid Mart global variables are initialized here.

• An initialization script. The script contains description of each global variable set in the job Properties window. It also completes several steps: • Sets the initial values of the Rapid Mart framework variables that the

job uses• Initiates the execution status framework

• Sections that load a set of tables you can use to analyze and report on a particular subject area in the Rapid Mart. A section consists of: • A work flow that loads the reporting dimensions applicable to the

subject area.• Work flows that load holding tables, intermediate tables, and auxiliary

tables that support loading the main subject area tables. Some of these flows might be reusable components, which can be incorporated into multiple sections of Rapid Marts. Components have the “execute once” feature enabled.


Using the Rapid MartBatch configuration variables7

• A conditional object that determines whether the job executes the initial or incremental loading logic.

• Work flows that load the main tables for the subject area. These tables are generally called “fact” tables in relational modeling terminology. A section loads a single fact table and any additional fact tables that depend on it. For example, an order analysis section might load an order table and an order summary table.

• A script that updates the job execution status table

Batch configuration variablesThe job that load the BusinessObjects Projects Rapid Mart for Oracle Applications uses several variables:• Global Variables• Local Variables• Global variables for Accounting Flexfield-related Dimensions

Global VariablesGlobal variables are commonly used in other Rapid Marts. You can identify global variables by a “G_” prefix in their names. The InitializeJob script initializes these variables.

Variable name Format Description

$G_LOAD_TYPE char(7) Controls initial versus incremental loading. Each component includes a conditional that checks the $G_LOAD_TYPE value. If $G_LOAD_TYPE is set to FIRST, the initial load logic is executed. If $G_LOAD_TYPE is DELTA, the incremental load logic is executed. To change from initial load value to incremental load, remove the comment delimiter (#) from statement #$G_LOAD_TYPE = 'DELTA' and add a comment delimiter to statement $G_LOAD_TYPE= 'FIRST'

$G_RUN_MODE char(5) When set to RESET, this parameter forces the Rapid Mart to assign a new starting extract time ($G_SDATE) for data extracts instead of deriving the starting date from the previous load.


Using the Rapid MartBatch configuration variables 7

$G_CDATE datetime The current date and time. This date is used as a constant in query constraining conditions.

$G_ABSOLUTE_START_DATE

date The start date for time-dependent data extraction. Data created prior to this date is not extracted even if the data has been changed more recently as indicated by the LAST_UPDATED_DATE field. Only used in the BusinessObjects HR Rapid Mart for Oracle Applications.

$G_AS_OF_DATE date Effective date for selecting date tracked valid benefit objects records. The variable is used to create snapshots of benefits hierarchical structure. Only used in the BusinessObjects HR Rapid Mart for Oracle Applications

$G_SDATE date The starting date for time-dependent data extraction. The job only extracts data modified or entered on or after this date. Normally this variable is derived from the AW_JOBEXECUTION table based on the previous load. The incremental load job only uses the assigned value when one of these conditions is true:• Execution status table

AW_JOBEXECUTION has no rows that correspond to the current job. See “The execution status table” on page 236.

• The variable $G_RUN_MODE is set to RESET in the initialization script for the job. See “Executing a job with the reset option” on page 238.

$G_EDATE date The ending date for time-dependent data extraction. The default value for an incremental load is today (sysdate).

$G_DELTA_START_DATE date The start date for incremental loads into BEN_ENROLLMENT_FACT. Only used in the BusinessObjects HR Rapid Mart for Oracle Applications




$G_DELTA_MIN_START_DATE

date For internal use only. The earliest date of changed data based on $G_SDATE, this is the actual start date for incremental loads. Only used in the BusinessObjects HR Rapid Mart for Oracle Applications and is determined during execution.

$G_LOAD_DATE date Set to current system date and is used to store the date the data was loaded

$G_LOAD_TIME char(8) Set to character representation of current system time and is used to store the time the data was loaded

$G_REBUILD_INDEXES char(1) The flag is used by stored procedures called in the pre- and post-processing scripts when loading fact tables. The procedures installed with the Rapid Mart are only placeholders. Recommended procedure definitions are located in ../Rapid Mart/OracleAP/Sample/DDL/Create_Sample_Maintenance_SP.sql script. If implemented, the procedures will always rebuild indexes after the initial load and only on weekends during incremental loads. See “Fact table stored procedures” on page 297 and the Rapid Mart Deployment Guide for details.

$G_DEFAULT_TEXT char(1) Default value for a character field when it is NULL and when it is not a foreign key. The default value is ‘?’

$G_DEFAULT_NUMBER int Default value for a number field when it is NULL or when it is a foreign key. The default value is -1

$G_DEFAULT_DATE date Default value for a date field when it is NULL. The default value is ‘9999.12.31’




$G_ORA_APPS_VERSION char(30) The Contract Rapid Mart is compatible with Oracle Applications versions 11.5.4-11.5.10. If set to ‘11.5.9’, the Rapid Mart will access source tables available in 11.5.4-11.5.9. Otherwise it will extract data from tables, available in Oracle Applications version 11.5.10. Oracle Applications have introduced significant changes its Service Contract module underlying data model. For details, see Oracle white paper “Service Contracts 11.5.10 Rules Migration” (Metalink search keyword: Note:265048.1)

$G_DB_TYPE char(60) For internal use only. Holds the target database type so that platform specific SQL can be generated.

$G_LANGUAGE char(30) Language to be Used throughout the Rapid Mart

$G_PERIOD_SET_NAME char(15) Name of the Period Set to be used to populate TIME_DIM only. The default value is ‘Accounting’

$G_PERIOD_TYPE char(15) Type of the Period Set to be used to populate TIME_DIM only. Default is ‘Month’.

$G_ITEM_CATEG_SET_NAME

char(80) Item categories in Oracle Applications are uniquely identified not only by category ID but also by a set they belong to. The same category ID can be long to multiple sets. The default value is ‘Inv. Items’

$G_EXCHANGE_TYPE char(80) Default conversion rate type to use during extraction. The default value is ‘Corporate’. Used in the BusinessObjects Sales Rapid Mart for Oracle Applications

$G_PERIOD_AGE_A int Number of days in the first aging period. The default value is 30. Used to define a 0-30 days bucket. Used in the BusinessObjects Accounts Payables and Accounts Receivable Rapid Marts for Oracle Applications

$G_PERIOD_AGE_B int Number of days in the second aging period. The default value is 60. Used to define a 31-60 days bucket. Used in the BusinessObjects Accounts Payables and Accounts Receivable Rapid Marts for Oracle Applications




$G_PERIOD_AGE_C int Number of days in the third aging period. The default value is 90. Used to define a 61-90 days bucket. Used in the BusinessObjects Accounts Payables and Accounts Receivable Rapid Marts for Oracle Applications

$G_PERIOD_AGE_D int Number of days in the forth aging period. The default value is 120. Used to define a 91-120 days bucket and a 120+ days bucket. Used in the BusinessObjects Accounts Receivable Rapid Mart for Oracle Applications

$G_DEL_PERIOD int Number of days to go back to calculate deleted invoices. The default value is 30. Used in the BusinessObjects Accounts Payable Rapid Mart for Oracle Applications

$G_SINGLE_COA char(1) A flag that is used by the jobs to process the accounting key flexfield. If the source system is configured with a single chart of accounts (or accounting key flexfield structure) or the user choose to report on a single chart of accounts then it should be set to ‘Y’. Used in the BusinessObjects Federal Financials Rapid Mart for Oracle Applications

$G_SET_OF_BOOKS char(30) Set of books name. If $G_SINGLE_COA is set to ’N’ this variable is not used. Used in the BusinessObjects Federal Financials Rapid Mart for Oracle Applications

$G_LOOP int Used to specify the loop interval when loading in chunks. Only implemented in work flows that load large tables such as CODE_COMBINATION and some fact tables.

$G_MIN_ID int For internal use only. Specifies the ID of the first record to be loaded in a chunk.

$G_MAX_ID int For internal use only. Specifies the ID of the last record to be loaded in a chunk.

$G_COST_TYPE char3(0) $G_COST_TYPE indicates the cost type of an item. For standard costing organizations use $G_COST_TYPE = Frozen. All costs reference a cost type. For true initialization of this variable, see C_Item_OA for GetCategorySetID script.




Local VariablesLocal variables are also used in other Rapid Marts. They do not have a specific prefix in their names as global variables have. The InitializeJob script initializes these variables.

Global variables for Accounting Flexfield-related DimensionsC_COASegment_OA needs to be executed only once to populate an auxiliary table COA_SEAGMENT. The component reads Oracle Applications key flexfield segment definition tables to extract segment names related to eight common fixed segment dimensions. The Oracle Applications accounting flexfield can have multiple structures (also called chart of accounts) defined. Each structure can have different segments that represent Company, Cost Center, Account, etc. entities. Accounting flexfield related global variables are initialized in the Initialize_Script as all other variables:


$P_FAILURES int Number of errors returned by the Post-Processing procedure for fact tables


$G_COMPANY char(30) A string to be used to search for all segment names related to Company definition within the Oracle Applications General Ledger

$G_PRODUCT char(30) A string to be used to search for all segment names related to Product definition within the Oracle Applications General Ledger

$G_PROJECT char(30) A string to be used to search for all segment names related to Project definition within the Oracle Applications General Ledger

$G_ACCOUNT char(30) A string to be used to search for all segment names related to natural account definition within the Oracle Applications General Ledger

$G_INTERCOMPANY

char(30) A string to be used to search for all segment names related to Intercompany definition within the Oracle Applications General Ledger

$G_DISTIRCT char(30) A string to be used to search for all segment names related to Territory definition within the Oracle Applications General Ledger



Note: See Appendix A for details on how to setup Accounting Flexfield-related variables and how to customize out-of-the-box Rapid Mart solution.

Executing the jobsBusinessObjects Projects Rapid Mart for Oracle Applications has two jobs:• OracleApps_FlexFields_Load - generates dynamic views for Rapid Mart

dimensions and fact tables that have key or descriptive flexfields. It needs to be run only once as part of post-installation and configuration steps and not on an ongoing basis. See Chapter 8: Technical Implementation for details.

• OracleApps_Projects_Load - populates Rapid Mart dimensions and fact tables during initial and incremental loads.

The steps you complete when executing the OracleApps_Projects_Load job depend on the type of job:• Initial extraction • Incremental extraction

To execute the initial extraction and load1. In the project area right-click in the OracleApps_Projects_Load job to

access the Properties window.2. Edit the job Global Variable properties:

a. Make sure that the value for the $G_LOAD_TYPE variable is set to ‘FIRST’.

b. Set the starting and ending time periods for the initial load. c. Set the starting date (the value for $G_SDATE) low enough to select

the earliest data desired for all target tables. Set the ending date (the value for $G_EDATE) to the current date.

d. Set values for the rest of global variables in the Properties window and click OK to accept the set properties and to close the window.

You can also set global variable values after you select Execute command from the drop-down menu in the project area.

$G_COST_CENTER

char(30) A string to be used to search for all segment names related to Cost Center definition within the Oracle Applications General Ledger

$G_FUND char(30) A string to be used to search for all segment names related to Fund definition within the Oracle Applications General Ledger




For more information about the variables see “Batch configuration variables” on page 240.

3. Run the job.a. In the project area, right-click the job and choose Execute.

Data Integrator opens the Execution Properties window.b. Select the desired execution properties.

At this point, you must decide whether or not to enable automatic recovery. See Data Integrator User Guide for more information.If you enabled automatic recovery and a job failed, you can recover from the failed job at this time.

c. Click OK to accept the selected properties and start the job.The job completes several steps:• Initializes the variables to the values you set in the initialization

script.• Calls components to load the tables. Generally, the job truncates

the tables before loading them during the initial job.Some components, such as work flows that load dimension tables, are repeated. The job only executes these components the first time because these work flows and data flows are set to “execute only once.”

4. Check the error log and the execution status table to make sure the job ran successfully.

To execute the incremental extraction and load1. Open the Properties window for job OracleApps_Projects_Load by right-

clicking on the job in the project area and selecting Properties command. Edit the job Global Variable properties:a. Make sure that the value for the $G_LOAD_TYPE variable is set to

‘DELTA’.b. Set the starting and ending time periods for the initial load. The

standard setting is the current date for both the starting and ending date.

c. Set values for the rest of global variables in the Properties window. d. Click OK to accept the set properties and to close the window.

2. Run the job.a. In the project area, right-click the job and choose Execute.

Data Integrator opens the Execution Properties window.


Using the Rapid MartCustomizing the Rapid Mart7

b. Select the desired execution properties.At this point, you must decide whether or not to enable automatic recovery. See Data Integrator User Guide for more information about automatic recovery. If you enabled automatic recovery and a job failed, you can recover from the failed job at this time.

c. Click OK to accept the selected properties and start the job.The job completes several steps:• Initializes the variables to the values you set in the initialization

script.• Calls components to load the tables incrementally, inserting new

and changed data since the last job execution. The job deletes outdated data from the target tables, and reloads the target tables with new and changed data. The incremental load uses the append option to load most tables.Some components, such as work flows that load dimension tables, are repeated. The job only executes these components the first time because these work flows and data flows are set to “execute only once.”

3. Check the error log and the execution status table to make sure the job ran successfully.

Customizing the Rapid MartRapid Marts are easy to customize. You can easily:• Customize the Rapid Mart data schema to meet your specific needs.• Expand the Rapid Mart to be used with various integrated query,

reporting, and data analysis applications.• Transport Rapid Mart components and sections to different Rapid Marts

using the Data Integrator export and import facilities.For example, to customize the Rapid Mart, you might:• Change column names to be more meaningful in your business

environment.• Remove columns or tables you do not need in your business

environment.• Add:

• Columns from tables already sourced


Using the Rapid MartCustomizing the Rapid Mart 7

• New columns from tables not extracted • Aggregates• Calculated or scrubbed data

You change your Rapid Mart in exactly the same way you would change any Data Integrator application. For information about how to make such changes, see the Data Integrator product documentation.Note: In general, whenever you make a change, you need to perform impact analysis. Impacts to consider include: • Initial load• Incremental load• Target tables• Integrity of existing Rapid Mart data• Integrity between batch extraction and real time jobs• Downstream analysis and reporting and Web applications• Variable settings used by imported components and sections• Other Rapid Mart (in a multi-Rapid Mart environment) If you are implementing the Rapid Mart on Oracle 9i or higher Oracle versions, you can take advantage of pre-processing and post-processing performance tuning stored procedures described in “Technical Implementation” on page 93 and in the Rapid Mart Deployment Guide.


Using the Rapid MartCustomizing the Rapid Mart7


Technical Implementation

chapter

Technical ImplementationOverview8
Overview
This chapter provides technical details about how the BusinessObjects Projects Rapid Mart for Oracle Applications is implemented. This chapter describes each section and the work flows that run to load that section. The information in this chapter is particularly useful for readers who customize the Projects Rapid Mart for their use.This chapter discusses: • Budget Line Section• Draft Revenue Section• Draft Invoice Section• Expenditure Section • Event Section• Project Asset Section• Budget Summary Section• Project Summary Section• Project Transaction Summary Section• Flexfields• Dealing with NULL values• Fact table stored procedures• Compatibility with Oracle Applications R12


Technical ImplementationBudget Line Section 8

Budget Line SectionThe Budget Line section of this Rapid Mart stores estimated cost, revenue, labor hours and other quantities for a project and task categorized by a resource.The Rapid Mart calls the C_BudgetLine_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.

Most dimensions are fully re-loaded during initial and incremental loads. For the fact table and larger dimension tables such as PEOPLE, the initial and incremental load algorithms are different.


Technical ImplementationBudget Line Section8

The Rapid Mart runs the initial load when a variable $G_LOAD_TYPE is set to ‘FIRST’. When $G_LOAD_TYPE is set to ‘DELTA’, the incremental load will be executed. (See “Batch configuration variables” on page 240 for descriptions of variables used to initialize jobs.)



Dimension Table LoadFirst, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them.The section uses work flow components to load dimension tables.

Work flow Description Tables loaded

C_TimeDim_OA Generated time periods with Oracle Applications calendar parameters with a granularity of a calendar day.

TIME_DIM

C_Organization_OA Organizational Units set up in the system and its hierarchy.

ORGANIZATION,ORG_STRUCTURE, ORG_PRIMARY_HIER_HZ, ORG_PRIMARY_HIER_VR

C_CurrentPeople_OA Employee master data PEOPLE, CURRENT_PEOPLE

C_Project_OA Project master data PROJECTC_Task_OA Project task master data TASK,TASK_HIER_HZ,

TASK_HIER_VRC_ProjectResource_OA Resource master data PROJECT_RESOURCEC_Job_OA Job master data JOBC_PeriodCalendar_OA Oracle Applications periods

attributes with a granularity of a period.

PERIOD_CALENDAR

C_BudgetType_OA Budget type data BUDGET_TYPEC_Vendor_OA Vendors master data VENDORC_VendorSite_OA Vendors master site data VENDOR_SITEC_VendorContact_OA Vendors master contact data VENDOR_CONTACTC_Currency_OA Currency abbreviations and

texts. CURRENCY

C_COASegment_OA Auxiliary table that maps accounting flexfield segment (set) names to the Projects Rapid Mart fixed segment dimensions.

COA_SEGMENT



C_CodeCombination_OA Translation dimension to store code combinations with translated segments (to 8 fixed dimensions) and their attributes. Up to 10 segments are decoded in the Account (code combination) descritpion.

CODE_COMBINATION

C_AccountSegment_OA Natural account attributes (mandatory code combination segment).

COA_ACCOUNT

C_CostCenterSegment_OA Cost Center attributes (one of code combination segments; mandatory in some Oracle Applications subledgers).

COA_COST_CENTER

C_CompanySegment_OA Company attributes (one of code combination segments).

COA_COMPANY

C_DistrictSegment_OA Territory attributes (one of code combination segments).

COA_DISTRICT

C_FundSegment_OA Fund attributes (one of code combination segments).

COA_FUND

C_IntercompSegment_OA Intercompany attributes (one of code combination segments).

COA_INTERCOMPANY

C_ProdutSegment_OA Product attributes (one of code combination segments). Note that Product entity defined in the General Ledger is not the same as Item entity (master data).

COA_PRODUCT

C_ProjectSegment_OA Project attributes (one of code combination segments).

COA_PROJECT

C_AccountType_OA General Ledger account category (Revenue, Expense, Liability, Asset, Equity).

ACCOUNT_TYPE




The Projects Rapid Mart comes with eight hard-coded common entities as dimensions that many organizations define as accounting flexfield segments:• COA_COMAPNY• COA_FUND• COA_COST_CENTER• COA_ACCOUNT• COA_PRODUCT• COA_DISTRICT• COA_INTERCOMPANY• COA_PROJECTThese reference dimensions are linked through primary-foreign key relationship to the CODE_COMBINATION dimension which originates from the GL_CODE_COMBINATIONS Oracle Applications source table. See “Accounting Flexfield” on page 294 for details on Oracle Applications Accounting flexfield.

C_COASegmentHierarchy_OA Vertically and horizontally flattened hierarchy for Account, Company, Cost Center, and Product General Ledger account segments.

COA_ACCOUNT_HZ, COA_ACCOUNT_VR, COA_COMPANY_HZ, COA_COMPANY_VR, COA_COST_CENTER_HZ, COA_COST_CENTER_VR,COA_PRODUCT_HZ, COA_PRODUCT_VR, COA_PROJECT_HZ, COA_PROJECTT_VR

C_ExpenditureType_OA Project expenditure type data EXPENDITURE_TYPEC_EventType_OA Project event type data EVENT_TYPEC_ProjectAgreement_OA Project Agreement data PROJECT_AGREEMENTC_ProjectClass_OA Project class category and

class code informationPROJECT_CLASS_CATEGORY

C_SetOfBooks_OA An organization or group of organizations that share a common chart of accounts, calendar, and currency.

SET_OF_BOOKS

C_ProjectPeriod_OA Project accounting period data PROJECT_PERIOD




The Rapid Mart extracts parent-child relationship for Account, Cost Center, Product, and Company flexfield segments stored in the FND_FLEX_VALUE_NORM_HIERARCHY Oracle Applications table and presents it in horizontal and vertical formats:• COA_ACCOUNT_HZ, COA_ACCOUNT_VR• COA_COST_CENTER_HZ, COA_COST_CENTER_VR• COA_PRODUCT_HZ, COA_PRODUCT_VR• COA_PROJECT_HZ, COA_PROJECT_VR• COA_COMPANY_HZ, COA_COMPANY_VRNote: Oracle Applications hierarchies allow for a single child node to have multiple parent nodes. When horizontally flattened, they can produce as many similar Current Leaf record identifiers as many parents the child node has. When using COA_ACCOUNT_HZ, COA_COST_CENTER_HZ, COA_PRODUCT_HZ, COA_PROJECT_HZ and COA_COMPANY_HZ for reporting, make sure you select the correct relationship.For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_BudgetLine_Dims_OA workflow.

Fact Table LoadAfter loading the dimensions, the work flow determines whether you are loading the budget line fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the BUDGET_LINE_FACT table is first truncated and the DF_BudgetLineFact_OA dataflow uses an embedded dataflow EDF_BudgetLineFact_OA to load the results into BUDGET_LINE_FACT.During incremental loads the DF_DeltaBudgetLine_OA dataflow uses the same embedded dataflow EDF_BudgetLineFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into BUDGET_LINE_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_BudgetLineFact_OA workflow.


Technical ImplementationDraft Revenue Section 8

Draft Revenue SectionThe Draft Revenue section holds draft project revenue transactions at line item level prior to being transferred to other modules in Oracle applications.The Rapid Mart calls the C_DraftRevenue_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.



Technical ImplementationDraft Revenue Section8





TIME_DIM


ORGANIZATION, ORG_STRUCTURE, ORG_PRIMARY_HIER_HZ, ORG_PRIMARY_HIER_VR

C_Project_OA Project master data PROJECTC_ProjectPeriod_OA Project accounting period data. PROJECT_PERIODC_PeriodCalendar_OA Oracle Applications periods


PERIOD_CALENDAR

C_ProjectAgreement_OA Project Agreement data PROJECT_AGREEMENTC_ProjectClass_OA Project class category and


C_RevenueSource_OA Project revenue source data REVENUE_SOURCEC_RevenueCategory_OA Project revenue category data REVENUE_CATEGORYC_COASegment_OA Auxiliary table that maps

accounting flexfield segment (set) names to the Projects Rapid Mart fixed segment dimensions.

COA_SEGMENT

C_CodeCombination_OA Sales order type attributes. CODE_COMBINATIONC_AccountSegment_OA Natural account attributes

(mandatory code combination segment).

COA_ACCOUNT




COA_COST_CENTER


COA_COMPANY


COA_DISTRICT


COA_FUND

C_IntercompanySegment_OA Intercompany attributes (one of code combination segments).

COA_INTERCOMPANY


COA_PRODUCT


COA_PROJECT


ACCOUNT_TYPE




SET_OF_BOOKS

C_Currency_OA Currency abbreviations and texts.

CURRENCY



Technical ImplementationDraft Revenue Section8

The Projects Rapid Mart comes with eight hard-coded common entities as dimensions that many organizations define as accounting flexfield segments:• COA_COMAPNY• COA_FUND• COA_COST_CENTER• COA_ACCOUNT• COA_PRODUCT• COA_DISTRICT• COA_INTERCOMPANY• COA_PROJECTThese reference dimensions are linked through primary-foreign key relationship to the CODE_COMBINATION dimension which originates from the GL_CODE_COMBINATIONS Oracle Applications source table. See “Accounting Flexfield” on page 294 for details on Oracle Applications Accounting flexfield.The Rapid Mart extracts parent-child relationship for Account, Cost Center, Product, and Company flexfield segments stored in the FND_FLEX_VALUE_NORM_HIERARCHY Oracle Applications table and presents it in horizontal and vertical formats:• COA_ACCOUNT_HZ, COA_ACCOUNT_VR• COA_COST_CENTER_HZ, COA_COST_CENTER_VR• COA_PRODUCT_HZ, COA_PRODUCT_VR• COA_PROJECT_HZ, COA_PROJECT_VR• COA_COMPANY_HZ, COA_COMPANY_VRNote: Oracle Applications hierarchies allow for a single child node to have multiple parent nodes. When horizontally flattened, they can produce as many similar Current Leaf record identifiers as many parents the child node has. When using COA_ACCOUNT_HZ, COA_COST_CENTER_HZ, COA_PRODUCT_HZ, COA_PROJECT_HZ and COA_COMPANY_HZ for reporting, make sure you select the correct relationship.For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_DraftRevenue_Dims_OA workflow.



Fact Table LoadAfter loading the dimensions, the work flow determines whether you are loading the draft revenue fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the DRAFT_REVENUE_FACT table is first truncated and the DF_DraftRevenueFact_OA dataflow uses an embedded dataflow EDF_DraftRevenueFact_OA to load the results into DRAFT_REVENUE_FACT.During incremental loads the DF_DeltaDraftRevenue_OA dataflow uses the same embedded dataflow EDF_DraftRevenueFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into DRAFT_REVENUE_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_DraftRevenueFact_OA workflow.


Technical ImplementationDraft Invoice Section8
Draft Invoice Section
The Draft Invoice section of this Rapid Mart holds potential project invoices that require approval before they are officially accounted for in other Oracle applications. Information is stored at invoice line item level to allow viewing invoice line details.The Rapid Mart calls the C_DraftInvoice_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.



Technical ImplementationDraft Invoice Section 8





TIME_DIM



C_Project_OA Project master data PROJECTC_ProjectPeriod_OA Project accounting period data. PROJECT_PERIODC_PeriodCalendar_OA Oracle Applications periods


PERIOD_CALENDAR



CURRENCY

C_ProjectAgreement_OA Project Agreement data PROJECT_AGREEMENTC_ProjectClass_OA Project class category and



SET_OF_BOOKS




COA_SEGMENT


CODE_COMBINATION


COA_ACCOUNT


COA_COST_CENTER


COA_COMPANY


COA_DISTRICT


COA_FUND


COA_INTERCOMPANY


COA_PRODUCT


COA_PROJECT



Technical ImplementationDraft Invoice Section 8



ACCOUNT_TYPE






The Rapid Mart extracts parent-child relationship for Account, Cost Center, Product, and Company flexfield segments stored in the FND_FLEX_VALUE_NORM_HIERARCHY Oracle Applications table and presents it in horizontal and vertical formats:• COA_ACCOUNT_HZ, COA_ACCOUNT_VR• COA_COST_CENTER_HZ, COA_COST_CENTER_VR• COA_PRODUCT_HZ, COA_PRODUCT_VR• COA_PROJECT_HZ, COA_PROJECT_VR• COA_COMPANY_HZ, COA_COMPANY_VRNote: Oracle Applications hierarchies allow for a single child node to have multiple parent nodes. When horizontally flattened, they can produce as many similar Current Leaf record identifiers as many parents the child node has. When using COA_ACCOUNT_HZ, COA_COST_CENTER_HZ, COA_PRODUCT_HZ, COA_PROJECT_HZ and COA_COMPANY_HZ for reporting, make sure you select the correct relationship.For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_DraftInvoice_Dims_OA workflow.

Fact Table LoadAfter loading the dimensions, the work flow determines whether you are loading the draft invoice fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the DRAFT_INVOICE_FACT table is first truncated and the DF_DraftInvoiceFact_OA dataflow uses an embedded dataflow EDF_DraftInvoiceFact_OA to load the results into DRAFT_INVOICE_FACT.During incremental loads the DF_DeltaDraftInvoice_OA dataflow uses the same embedded dataflow EDF_DraftInvoiceFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into DRAFT_INVOICE_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_DraftInvoiceFact_OA workflow.


Technical ImplementationExpenditure Section 8

Expenditure SectionThe Expenditure section of this Rapid Mart contains details of expenditure items incurred by an employee or organization .It allows reporting on detailed distribution of expenditure costs and expenditure revenues. This section loads three separate fact tables: • EXPENDITURE_FACT• EXPENDITURE_REV_FACT• and EXPENDITURE_COST_FACTThe Rapid Mart calls the C_Expenditure_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.


Technical ImplementationExpenditure Section8

Most dimensions are fully re-loaded during initial and incremental loads. For the event fact table and larger dimension tables such as PEOPLE, the initial and incremental load algorithms are different.The Rapid Mart runs the initial load when a variable $G_LOAD_TYPE is set to ‘FIRST’. When $G_LOAD_TYPE is set to ‘DELTA’, the incremental load will be executed. (See “Batch configuration variables” on page 240 for descriptions of variables used to initialize jobs.)

Relevant Sections LoadThe C_DraftRevenue_OA and C_DraftInvoice_OA component workflows are executed to load the draft revenue and draft invoice fact tables respectively, if these have not already been run during the current load. This step is necessary to ensure these tables are loaded as they are related to the expenditure cost and expenditure revenue fact tables. DRAFT_REVENUE_FACT and DRAFT_INVOICE_FACT behave as dimensions for the expenditure-related fact tables.




TIME_DIM




C_Project_OA Project master data PROJECTC_Task_OA Project task master data TASK, TASK_HIER_HZ,

TASK_HIER_VRC_Job_OA Job master data JOBC_Vendor_OA Vendors master data VENDOR



C_VendorSite_OA Vendors master site data VENDOR_SITEC_VendorContact_OA Vendors master contact data VENDOR_CONTACTC_ExpenditureGroup_OA Project expenditure group data EXPENDITURE_GROUPC_ExpenditureType_OA Project expenditure type data EXPENDITURE_TYPEC_Currency_OA Currency abbreviations and

texts. CURRENCY

C_ProjectClass_OA Project class category and class code information



SET_OF_BOOKS

C_ProjectPeriod_OA Project accounting period data. PROJECT_PERIODC_PeriodCalendar_OA Oracle Applications periods


PERIOD_CALENDAR

C_CostDistType_OA Expenditure cost distribution type data


C_TransferStatus_OA Project transfer status data (relating to other Oracle Applications)

TRANSFER_STATUS


COA_SEGMENT


CODE_COMBINATION


COA_ACCOUNT




The Projects Rapid Mart comes with eight hard-coded common entities as dimensions that many organizations define as accounting flexfield segments:• COA_COMAPNY• COA_FUND• COA_COST_CENTER


COA_COST_CENTER


COA_COMPANY


COA_DISTRICT


COA_FUND


COA_INTERCOMPANY


COA_PRODUCT


COA_PROJECT


ACCOUNT_TYPE






• COA_ACCOUNT• COA_PRODUCT• COA_DISTRICT• COA_INTERCOMPANY• COA_PROJECTThese reference dimensions are linked through primary-foreign key relationship to the CODE_COMBINATION dimension which originates from the GL_CODE_COMBINATIONS Oracle Applications source table. See “Accounting Flexfield” on page 294 for details on Oracle Applications Accounting flexfield.



The Rapid Mart extracts parent-child relationship for Account, Cost Center, Product, and Company flexfield segments stored in the FND_FLEX_VALUE_NORM_HIERARCHY Oracle Applications table and presents it in horizontal and vertical formats:• COA_ACCOUNT_HZ, COA_ACCOUNT_VR• COA_COST_CENTER_HZ, COA_COST_CENTER_VR• COA_PRODUCT_HZ, COA_PRODUCT_VR• COA_PROJECT_HZ, COA_PROJECT_VR• COA_COMPANY_HZ, COA_COMPANY_VRNote: Oracle Applications hierarchies allow for a single child node to have multiple parent nodes. When horizontally flattened, they can produce as many similar Current Leaf record identifiers as many parents the child node has. When using COA_ACCOUNT_HZ, COA_COST_CENTER_HZ, COA_PRODUCT_HZ, COA_PROJECT_HZ and COA_COMPANY_HZ for reporting, make sure you select the correct relationship.For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_Expenditure_Dims_OA workflow.

Fact Table LoadThere are three tables comprising the expenditure section of the Rapid Mart:• EXPENDITURE_FACT• EXPENDITURE_COST_FACT• and EXPENDITURE_REV_FACTAfter loading the dimensions, the work flow determines whether you are loading the expenditure fact tables for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. See details below for how each expenditure fact table is loaded.

Expenditure FactDuring the initial load, the EXPENDITURE_FACT table is first truncated and the DF_ExpenditureFact_OA dataflow uses an embedded dataflow EDF_ExpenditureFact_OA to load the results into EXPENDITURE_FACT.During incremental loads the DF_DeltaExpenditure_OA dataflow uses the same embedded dataflow EDF_ExpenditureFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into EXPENDITURE_FACT.



In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the expenditure fact table, see annotations and object descriptions in the Rapid Mart C_ExpenditureFact_OA workflow.

Expenditure Cost FactThe workflow executes the DF_ExpenditureCostFact_OA dataflow to load the expenditure cost fact table. As the source tables do not include timestamps, the fact table has to be fully reloaded each time, therefore the logic is exactly the same for both initial and incremental loads.The EXPENDITURE_COST_FACT table is first truncated and then the DF_ExpenditureRevFact_OA dataflow loads the results into EXPENDITURE_COST_FACTFor more details on extraction logic for the expenditure distribution fact table, see annotations and object descriptions in the Rapid Mart C_ExpenditureCostFact_OA workflow.

Expenditure Rev FactThe workflow executes the DF_ExpenditureRevFact_OA dataflow to load the expenditure revenue fact table. As the source tables do not include timestamps, the fact table has to be fully reloaded each time, therefore the logic is exactly the same for both initial and incremental loads.The EXPENDITURE_REV_FACT table is first truncated and then the DF_ExpenditureRevFact_OA dataflow loads the results into EXPENDITURE_REV_FACTFor more details on extraction logic for the expenditure distribution fact table, see annotations and object descriptions in the Rapid Mart C_ExpenditureRevFact_OA workflow.


Technical ImplementationEvent Section8
Event Section
The Event section of this Rapid Mart contains summary level transactions generating revenue and/or billing activity that are not directly related to any expenditure items.The Rapid Mart calls the C_Event_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.

All the dimensions are fully re-loaded during initial and incremental loads. For the event fact table, the initial and incremental load algorithms are different.


Technical ImplementationEvent Section 8


Relevant Sections LoadNext the C_DraftRevenue_OA and C_DraftInvoice_OA component workflows are executed to load the draft revenue and draft invoice fact tables respectively, if these have not already been run during the current load. This step is necessary to ensure these tables are loaded as they are related to the event distribution fact table. DRAFT_REVENUE_FACT and DRAFT_INVOICE_FACT behave as dimensions for the expenditure-related fact tables.




TIME_DIM




TASK_HIER_VRC_Currency_OA Currency abbreviations and

texts. CURRENCY


COA_SEGMENT




CODE_COMBINATION


COA_ACCOUNT


COA_COST_CENTER


COA_COMPANY


COA_DISTRICT


COA_FUND


COA_INTERCOMPANY


COA_PRODUCT


COA_PROJECT


ACCOUNT_TYPE



Technical ImplementationEvent Section 8




C_EventType_OA Project event type data EVENT_TYPEC_ProjectClass_OA Project class category and



SET_OF_BOOKS

C_PeriodCalendar_OA Oracle Applications periods attributes with a granularity of a period.

PERIOD_CALENDAR

C_Event_OA Project event dimension EVENT




The Rapid Mart extracts parent-child relationship for Account, Cost Center, Product, and Company flexfield segments stored in the FND_FLEX_VALUE_NORM_HIERARCHY Oracle Applications table and presents it in horizontal and vertical formats:• COA_ACCOUNT_HZ, COA_ACCOUNT_VR• COA_COST_CENTER_HZ, COA_COST_CENTER_VR• COA_PRODUCT_HZ, COA_PRODUCT_VR• COA_PROJECT_HZ, COA_PROJECT_VR• COA_COMPANY_HZ, COA_COMPANY_VRNote: Oracle Applications hierarchies allow for a single child node to have multiple parent nodes. When horizontally flattened, they can produce as many similar Current Leaf record identifiers as many parents the child node has. When using COA_ACCOUNT_HZ, COA_COST_CENTER_HZ, COA_PRODUCT_HZ, COA_PROJECT_HZ and COA_COMPANY_HZ for reporting, make sure you select the correct relationship.For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_Event_Dims_OA workflow.

Fact Table LoadFinally the workflow executes the DF_EventDistFact_OA dataflow to load the event distribution fact table. As the source tables do not include timestamps, the fact table has to be fully reloaded each time, therefore the logic is exactly the same for both initial and incremental loads.The EVENT_DIST_FACT table is first truncated and then the DF_EventDistFact_OA dataflow loads the results into EVENT_FACTFor more details on extraction logic for the event distribution fact table, see annotations and object descriptions in the Rapid Mart C_EventDistFact_OA workflow.


Technical ImplementationProject Asset Section 8

Project Asset SectionThe Project Asset section of this Rapid Mart holds capital and retirement adjustment assets for capital projects.The Rapid Mart calls the C_ProjectAsset_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.

Most dimensions are fully re-loaded during initial and incremental loads. For the fact table and larger dimension tables such as PEOPLE, the initial and incremental load algorithms are different.The Rapid Mart runs the initial load when a variable $G_LOAD_TYPE is set to ‘FIRST’. When $G_LOAD_TYPE is set to ‘DELTA’, the incremental load will be executed. (See “Batch configuration variables” on page 240 for descriptions of variables used to initialize jobs.)

Dimension Table LoadFirst, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them.


Technical ImplementationProject Asset Section8

The section uses work flow components to load dimension tables.

For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_ProjectAsset_Dims_OA workflow.

Fact Table LoadAfter loading the dimensions, the work flow determines whether you are loading the project asset fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the PROJECT_ASSET_FACT table is first truncated and the DF_ProjectAssetFact_OA dataflow uses an embedded dataflow EDF_ProjectAssetFact_OA to load the results into PROJECT_ASSET_FACT.



TIME_DIM



C_BookType_OA Asset Book control information BOOK_TYPEC_AssetLocation_OA Asset location data ASSET_LOCATIONC_AssetCategory_OA Asset category data ASSET_CATEGORYC_Project_OA Project master data PROJECTC_CurrentPeople_OA Employee master data PEOPLE,

CURRENT_PEOPLEC_ProjectClass_OA Project class category and



SET_OF_BOOKS


PERIOD_CALENDAR


CURRENCY


Technical ImplementationProject Asset Section 8

During incremental loads the DF_DeltaProjectAsset_OA dataflow uses the same embedded dataflow EDF_ProjectAssetFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into PROJECT_ASSET_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_ProjectAssetFact_OA workflow.


Technical ImplementationBudget Summary Section8
Budget Summary Section
The Budget Summary section of this Rapid Mart contains summarized inception-to-date, year-to-date, period-to-date and prior period budget data.The Rapid Mart calls the C_BudgetSummary_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.

All the dimensions are fully re-loaded during initial and incremental loads. For the fact table, the initial and incremental load algorithms are different.The Rapid Mart runs the initial load when a variable $G_LOAD_TYPE is set to ‘FIRST’. When $G_LOAD_TYPE is set to ‘DELTA’, the incremental load will be executed. (See “Batch configuration variables” on page 240 for descriptions of variables used to initialize jobs.)


Technical ImplementationBudget Summary Section 8

Dimension Table LoadFirst, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them.The section uses work flowcomponents to load dimension tables.

For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_BudgetSummary_Dims_OA workflow.



PERIOD_CALENDAR




TASK_HIER_VRC_ProjectPeriod_OA Project accounting period data. PROJECT_PERIODC_ProjectResource_OA Resource master data PROJECT_RESOURCEC_BudgetType_OA Budget type data BUDGET_TYPEC_ProjectClass_OA Project class category and



SET_OF_BOOKS


TIME_DIM


CURRENCY


Technical ImplementationBudget Summary Section8
Fact Table Load
After loading the dimensions, the work flow determines whether you are loading the budget line fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the BUDGET_SUMMARY_FACT table is first truncated and the DF_BudgetSummaryFact_OA dataflow uses an embedded dataflow EDF_BudgetSummaryFact_OA to load the results into BUDGET_SUMMARY_FACT.During incremental loads the DF_DeltaBudgetSummary_OA dataflow uses the same embedded dataflow EDF_BudgetSummaryFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into BUDGET_SUMMARY_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_BudgetSummaryFact_OA workflow.


Technical ImplementationProject Summary Section 8

Project Summary SectionThe Project Summary section of this Rapid Mart contains summarized inception-to-date, year-to-date, period-to-date and prior period project data.The Rapid Mart calls the C_ProjectSummary_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.

All the dimensions are fully re-loaded during initial and incremental loads. For the fact table, the initial and incremental load algorithms are different.The Rapid Mart runs the initial load when a variable $G_LOAD_TYPE is set to ‘FIRST’. When $G_LOAD_TYPE is set to ‘DELTA’, the incremental load will be executed. (See “Batch configuration variables” on page 240 for descriptions of variables used to initialize jobs.)


Technical ImplementationProject Summary Section8
Dimension Table Load
First, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them.The section uses work flow components to load dimension tables.

For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_ProjectSummary_Dims_OA workflow.



PERIOD_CALENDAR




TASK_HIER_VRC_ProjectPeriod_OA Project accounting period data. PROJECT_PERIODC_ProjectResource_OA Resource master data PROJECT_RESOURCEC_ProjectClass_OA Project class category and



SET_OF_BOOKS


TIME_DIM


CURRENCY


Technical ImplementationProject Summary Section 8

Fact Table LoadAfter loading the dimensions, the work flow determines whether you are loading the project summary fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the PROJECT_SUMMARY_FACT table is first truncated and the DF_ProjectSummaryFact_OA dataflow uses an embedded dataflow EDF_ProjectSummaryFact_OA to load the results into PROJECT_SUMMARY_FACT.During incremental loads the DF_DeltaProjectSummary_OA dataflow uses the same embedded dataflow EDF_ProjectSummaryFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into PROJECT_SUMMARY_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_ProjectSummaryFact_OA workflow.


Technical ImplementationProject Transaction Summary Section8
Project Transaction Summary Section
The Project Transaction Summary section of this Rapid Mart contains summarized project data at the lowest level of detail available in Oracle Applications Projects module.The Rapid Mart calls the C_ProjectTxnSummary_Section_OA work flow to load dimension and fact tables from Oracle Applications. The following diagram shows the tables that this section loads.

Most dimensions are fully re-loaded during initial and incremental loads. For the fact table and larger dimension tables such as PEOPLE, the initial and incremental load algorithms are different.The Rapid Mart runs the initial load when a variable $G_LOAD_TYPE is set to ‘FIRST’. When $G_LOAD_TYPE is set to ‘DELTA’, the incremental load will be executed. (See “Batch configuration variables” on page 240 for descriptions of variables used to initialize jobs.)


Technical ImplementationProject Transaction Summary Section 8




TIME_DIM





TASK_HIER_VRC_Job_OA Job master data JOBC_Vendor_OA Vendors master data VENDORC_VendorSite_OA Vendors master site data VENDOR_SITEC_VendorContact_OA Vendors master contact data VENDOR_CONTACTC_PeriodCalendar_OA Oracle Applications periods


PERIOD_CALENDAR

C_ProjectPeriod_OA Project accounting period data. PROJECT_PERIODC_ExpenditureType_OA Project expenditure type data EXPENDITURE_TYPEC_EventType_OA Project event type data EVENT_TYPEC_ProjectClass_OA Project class category and



SET_OF_BOOKS


CURRENCY


Technical ImplementationProject Transaction Summary Section8

For more details on extraction logic for dimensions, see annotations and object descriptions in the Rapid Mart WF_ProjectTxnSummary_Dims_OA workflow.

Fact Table LoadAfter loading the dimensions, the work flow determines whether you are loading the project transaction summary fact table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. During the initial load, the PROJECT_TXN_SUMMARY_FACT table is first truncated and the DF_ProjectTxnSummaryFact_OA dataflow uses an embedded dataflow EDF_ProjectTxnSummaryFact_OA to load the results into PROJECT_TXN_SUMMARY_FACT.During incremental loads the DF_DeltaProjectTxnSummary_OA dataflow uses the same embedded dataflow EDF_ProjectTxnSummaryFact_OA and the table comparison transform to identify changed and new records. These records are respectively updated and inserted into PROJECT_TXN_SUMMARY_FACT.In the embedded data flow, the source tables are constrained on the LAST_UPDATE_DATE to limit the records accordingly :

LAST_UPDATE_DATE >= $G_SDATEFor more details on extraction logic for the fact table, see annotations and object descriptions in the Rapid Mart C_ProjectTxnSummaryFact_OA workflow.


Technical ImplementationFlexfields 8

FlexfieldsOracle Applications provides a way of extending the system and also to enable custom implementations, without the need for additional programming. This is achieved using what are known as flexfields. There are two types of flexfields: descriptive flexfields and key flexfields.Descriptive flexfields enable you to capture additional information about an entity. For example, Oracle Applications provide a descriptive flexfield at order header level. If the application does not cover all the attributes specific to your business, you can capture them in the descriptive flexfield, which may consist of many segments. A segment may be used to describe an attribute or a set of segments may be used to describe one attribute.Key FlexFields are used when the key information of an entity needs to be customized. For example, the part number of an item is crucial to deal with the product in any business. Yet, the structure of the part number may be very different from business to business. This problem can be eased using key FlexField. FlexFields are a good way of dealing with these situations. However, the data is stored in underlying tables in uninformative columns named as segment1, segment2, attribute1, attribute2, etc. Interpreting these columns outside of Oracle Applications can be difficult, especially when you need to put these columns together to make a meaningful attribute.The Rapid Mart provides a job OracleApps_FlexFields_Load to create dynamic views to translate flexfields (excluding Accounting flexfield) into more meaningful names. This job is a tool for the Rapid Mart customization when you need to add flexfield columns to the target tables. Below are the details of the view generation algorithm:1. AW_DESCR_FLEX_FIELD_MAP metadata table is populated with

Oracle Applications descriptive flexfields names and their mapping to the Rapid Mart target tables (DF_DescrFlexFieldMap_OA).

2. AW_DESCR_FLEX_FIELD_NAME metadata table is populated with Oracle Applications descriptive flexfields segments definition (DF_DescriptiveFlexField_OA).

3. AW_FLEX_FIELD_MAP metadata table is populated with Oracle Applications key flexfields names and their mapping to the Rapid Mart target tables (DF_KeyFlexFieldMap_OA).

4. AW_FLEX_FIELD_NAME metadata table is populated with Oracle Applications key flexfields segments definition (DF_KeyFlexField_OA).


Technical ImplementationFlexfields8

5. The Rapid Mart calls a database stored procedure SP_CREATE_FLEX_VIEWS to create views for the fact tables in the same database where the Rapid Mart tables reside. Created views have flexfield user-defined column names with the following extensions:• ‘_FLEXK’ for key flexfield segments;• ‘_FLEXG’ for global descriptive flexfield segments;• ‘_FLEXD’ for context-sensitive descriptive flexfield segments.

The Oracle Projects Rapid Mart does not extract data from descriptive flexfield columns and does not interpret descriptive flexfield structure field names because almost every Oracle Applications source table contains descriptive flexfields.However you can add descriptive flexfields to the Oracle Projects Rapid Mart in two ways:1. You can extend the above algorithm to include other tables. It will be

necessary to add the attribute columns to the target table, populate these fields in the relevant job and finally add a mapping to DF_DescrFlexFieldMap_OA data flow.

2. Or you can simply add those columns with meaningful names to the Projects Rapid Mart target schema and modify OracleApps_Projects_Load job appropriately selecting attribute columns from source tables and re-naming them to match target schema names.

Accounting Flexfield Accounting Flexfield is a key flexfield used to define the account structure to fit the specific needs of the enterprise. During set-up process the number of segments is chosen (up to 30 segments), as well as the length, name, and order of each segment in the Accounting Flexfield structure. Multiple structures can be defined for the accounting flexfield (‘GL#’).Accounting Flexfields allow:• define an account structure large enough to reflect the important aspects

of the enterprise, but small enough so that it is manageable and meaningful;

• define an account structure that accommodates and properly classifies information from your other financial information sources;

• create an account structure that provides a logical ordering of values by grouping related accounts in the same range of values.


Technical ImplementationFlexfields 8

However, the data is stored in underlying tables in uninformative columns named SEGMENT1 through SEGMENT30. Interpreting these columns outside of Oracle Applications can be difficult, especially when you need put these segments together to make a meaningful attribute.The Rapid Mart chose eight common entities that many organizations define with separate account segments to represent general ledger dimensions:• Company - a segment that indicates legal entities for commercial

organizations;• Fund - a segment that indicates a fiscal and accounting entity with a self-

balancing set of accounts for non-profit or governmental organizations;• Cost Center (Department) - a segment that indicates functional areas;• Account - a segment that represents natural account;• Product - a segment that indicates products or product groups

manufactured by a commercial organization;• Project - a segment that indicates projects for which revenue and

expenses need to be tracked;• District - a segment that represents geographical locations;• Intercompany - a segment to represent subsidiaries in a multi-company

environment. Each financial transaction loaded in the General Ledger Rapid Mart fact tables can be classified by any or all of these dimensions. Below are the details of the accounting flexfield decoding algorithm:1. A Rapid Mart auxiliary table COA_SEGMENT is loaded by the

C_COASegment_OA component with Oracle Applications segment names that correspond to each of eight common entities. See “Global variables for Accounting Flexfield-related Dimensions” on page 87 for details.

2. The C_CodeCombination_OA component performs few tasks for each record extracted from the Oracle Applications GL_CODE_COMBINATIONS source table:1. builds CONCAT_ACCOUNT and ACCOUNT_DESC attributes as a

concatenation of SEGMENT1 through SEGMENT10 source segment codes segment names. If your Oracle Applications installation has more than 10 segments defined for any of chart of accounts, you can easily customize these fields by adding concatenation of additional segments. When you execute the OracleApps_Projects_Load job, the WF_PrintMaxSegmNum work flow will output on the Data Integrator monitor screen the highest number of segments configured in the Oracle Applications system;


Technical ImplementationFlexfields8

2. pivots all thirty segments of each code combination record into 30 rows and then decodes each segment names by eight fixed segments (COMPANY_CODE, FUND_CODE, COST_CENTER_CODE, PRODUCT_CODE, ACCOUNT_CODE, PROJECT_CODE, INTERCOMPANY_CODE, DISTRICT_CODE).

The initial load for Code Combination table incorporates logic to allow the data to be loaded in chunks to allow control over the size of data to be process with a single statement in Oracle Applications database. It helps to avoid limitation of TEMP tablespace set in the Oracle Applications database.The chunk size can be configured by setting the $G_LOOP global variable in the WF_CodeCombination_OA workflow InitializeVariables script. The Rapid Mart uses Data Integrator Loop object to execute DF_CodeCombination_OA dataflow several times instead of once. Number of executions is controlled by $G_MIN_ID, $G_MAX_ID, and $G_LOOP variables.$G_MIN_ID = sql('OA_DS', 'select min(CODE_COMBINATION_ID) from

GL.GL_CODE_COMBINATIONS');$G_MAX_ID = sql('OA_DS', 'select max(CODE_COMBINATION_ID) from

GL.GL_CODE_COMBINATIONS');$G_LOOP = 100000;After every dataflow execution $G_MIN_ID gets incremented by $G_LOOP value (IncremenMIN_ID script):$G_MIN_ID = $G_MIN_ID + $G_LOOP;The initial load job extracts all records found in GL_CODE_COMTINATIONS source table:FND_ID_FLEX_STRUCTURES.ID_FLEX_NUM =

GL_CODE_COMBINATIONS.CHART_OF_ACCOUNTS_IDAND FND_ID_FLEX_STRUCTURES.APPLICATION_ID = 101and FND_ID_FLEX_STRUCTURES.ID_FLEX_CODE = 'GL#'and (($G_LOAD_TYPE = 'FIRST'

and GL_CODE_COMBINATIONS.CODE_COMBINATION_ID >= $G_MIN_IDand GL_CODE_COMBINATIONS.CODE_COMBINATION_ID < $G_MIN_ID + $G_LOOP)

or ( $G_LOAD_TYPE = 'DELTA'and GL_CODE_COMBINATIONS.LAST_UPDATE_DATE >= $G_SDATEand GL_CODE_COMBINATIONS.LAST_UPDATE_DATE <= $G_EDATE))

Note: Both initial and incremental loads use the same embedded dataflow (EDF_CodeCombination_OA) to load the GL Balance Fact table. The Code Combination table is loaded in TRUNCATE mode during the initial load and in AUTO-CORRECT mode during incremental mode.


Technical ImplementationDealing with NULL values 8

If you need to add additional segment dimensions of remove existing ones, you will need to modify not only the C_COASegment_OA and C_CodeCombination_OA components but also the underlying Rapid Mart target schema (CODE_COMBINTATION table specifically).Note: See Appendix A of the User Guide on detailed instructions how to customize the Rapid Mart for Accounting Flexfield.

Dealing with NULL valuesAs the first step in data cleansing, the BusinessObjects Projects Rapid Mart for Oracle Applications allows replacing NULL values found in the source system with configurable default ‘not-null’ values.The Projects Rapid Mart provides three category of default values to treat NULLs:• For columns that behave as a foreign key the Projects Rapid Mart

replaces NULL value with a global variable $G_DEFAULT_NUMBER of data type integer;

• For columns that store descriptions NULLs are replaced with $G_DEFAULT_TEXT of data type char(1);

• For columns that store dates NULLs are replaced with $G_DEFAULT_DATE of data type DATE.

Dimensions whose corresponding foreign keys in the fact tables can have value NULL are loaded with an additional ‘dummy’ row to represent NULL. The value of $G_DEFAULT_NUMBER global variable gets inserted into each dimension primary key column.

Fact table stored proceduresWhen loading each fact table the Rapid Mart calls two stored procedures. A PREPROCESSING_FACT_TABLE procedure is called before loading the fact table and a POSTPROCESSING_FACT_TABLE procedure is called when the load is finished. The procedures are automatically installed by the Rapid Mart only as placeholders:CREATE OR REPLACE PROCEDURE postprocessing_fact_table(pLoadType IN VARCHAR2, pDropCreateIndex IN VARCHAR2, pFactTable IN VARCHAR2, pMView_Failures OUT BINARY_INTEGER) ISBEGIN NULL;


Technical ImplementationCompatibility with Oracle Applications R128

END postprocessing_fact_table;CREATE OR REPLACE PROCEDURE preprocessing_fact_table(pLoadType IN VARCHAR2, pDropCreateIndex IN VARCHAR2, pFactTable IN VARCHAR2) ISBEGIN NULL;END preprocessing_fact_table;In order to use these procedures as a performance tuning tool, you need to customize them. The Rapid Mart provides a sample script Create_Sample_Maintenance_SP.sql with necessary modifications. The PREPROCESSING_FACT_TABLE Oracle stored procedure defined in the sample script will drop all indexes and all materialized view logs enabled and POSTPROCESSING_FACT_TABLE will recreate them. See the Rapid Mart Deployment Guide for details.

Compatibility with Oracle Applications R12Data model of Oracle Applications R12 is different from 11i and it affects the Projects Rapid Mart. Specifically, in Oracle Applications R12 the following tables have undergone changes:• GL.GL_SET_OF_BOOKS tables has been replaced with

GL.GL_LEDGERS and GL_SETS_OF_BOOKS_11i tables• PO.PO_VENDORS table is replaced with AP.AP_SUPPLIERS• PO.PO_VENDOR_SITES is replaced with

AP.AP_SUPPLIER_SITES_ALL• PO.PO_VENDOR_CONTACTS is replaced with

AP.AP_SUPPLIER_CONTACTSWhen choosing to install Accounts Payable Rapid Mart for R12, the Rapid Mart job:

1. Replaces PO.PO_VENDORS with AP.AP_SUPPLIERS table in the following dataflows

EDF_Vendor_OAEDF_VendorSite_OA

2. Replaces PO.PO_VENDOR_SITES with AP.AP_SUPPLIER_SITES_ALL table in the following dataflows

EDF_VendorSite_OADF_VendorContact_OA


Technical ImplementationCompatibility with Oracle Applications R12 8

3. Replaces PO.PO_VENDOR_CONTACTS with AP.AP_SUPPLIER_CONTACTS table in the following dataflows

DF_VendorContact_OA4. Replaces GL.GL_SETS_OF_BOOKS with GL.GL_LEDGERS table

in the following dataflows:• DF_SetOfBooks_OA• DF_Organization_OA• DF_BookType_OA


Technical ImplementationCompatibility with Oracle Applications R128


Rapid Mart and Oracle Applications Accounting Flexfield

appendix

OverviewA
Overview
This appendix briefly describes Oracle Applications Accounting flexfield and reporting challenges it creates. It gives an overview of how Data Integrator processes Oracle Applications Flexfields. It also provides step-by-step instruction on how to implement Accounting Flexfield in Rapid Marts for Oracle Applications. This appendix contains the following sections:• Oracle Applications Reporting Challenges • Data Integrator Interface for Oracle Applications • Data Integrator Limitations • Implementing Accounting Flexfield with Rapid Marts

Oracle Applications Reporting ChallengesOracle Applications version 11i and 12 come with an extensive list of pre-built reports for each module. They are well-documented and targeted to satisfy statutory, auditing, and basic analytical customer requirements.Challenges come when Oracle Applications users need to extend the existing reporting functionality. Modifying Oracle Applications out-of-the-box reports and creating new ones requires development skills and a good understanding of the underlying data model as well as Oracle Applications design concepts (for example, such as Flexfields). Other challenges arise when the reporting solution is based directly on Oracle Applications transactional database:• Impact on performance of transaction processing ("killer queries");• Impact on report query response performance;• Custom-built reports can not work after the Oracle Applications instance

has been upgraded;• Complexity of handling Flexfields that are configured to have multiple

structures (such as Accounting or Item Category Flexfields, multiple context Descriptive Flexfields).


Data Integrator Interface for Oracle Applications A
Data Integrator Interface for Oracle Applications
Data Integrator Interface for Oracle Applications, or Oracle Applications datastore, accesses source table metadata from Oracle Applications object library (FND_<> tables). With Oracle Applications datastore you can:• View objects such as tables, functions, and procedures in a database

instance under a specified Oracle Apps environment;• Import metadata for Oracle Applications objects into Data Integrator with

user-defined names for flexfield segment columns or original column names;


Data Integrator LimitationsA
• Create data flows that use Oracle Applications objects (such as tables)
as sources and targets.

Data Integrator LimitationsWhen importing Oracle Applications tables that contain Key or Descriptive Flexfields defined as multiple structures (such as Accounting Flexfield with multiple Chart of Accounts), Data Integrator translates each Flexfield segment to the a user-defined name that belongs to the first structure found in the


Data Integrator Limitations A
Oracle Applications object library. For example, in an Oracle Applications instance the Accounting Flexfield (GL#) can be configured differently for various charts of accounts.
In the example above, each Structure (Norway Accounting Flex, OPM Accounting Flex, etc.) can have different Segment Name defined for each Column (SEGMENT1 up to SEGMENT30).


Data Integrator LimitationsA
The Column field values (SEGMENT1 through SEGMENT30) belong to Oracle Applications GL.GL_CODE_COMBINATIONS table. The table structure:

Data Integrator Limitations A
With Data Integrator, when GL.GL_CODE_COMBINATIONS table gets imported with ‘Process flexfield names’ option set to ‘Yes’, it is interpreted inconsistently across multiple Flexfield structures:
A list of Key Flexfields that can be configured with multiple structures includes:• Accounting Key flexfield (GL#);• Key flexfields in HR module:

• CMP - Competence flexfield;• JOB - Job flexfield;• POS - Position flexfield;• PEA - Personal Analysis flexfield;• GRD - Grade flexfield;

• Item Category key flexfield (MCAT).


Rapid Mart SolutionsA
In Oracle Applications, most of Descriptive Flexfields are allowed to have multiple context (or structures). Data Integrator behavior when importing Oracle Applications tables with configured Descriptive Flexfields is similar: it will assign a user-defined name for the flexfield attribute (such as ATTRIBUTE1) of the first context found in the Oracle Applications library.
Rapid Mart SolutionsRapid Marts provide workarounds for Data Integrator Oracle Applications interface limitations and for complexity of handling Oracle Applications Flexfields, both Key and Descriptive:• Come with built-in stored procedures for generating dynamic views to

translate key and descriptive flexfield segments using Rapid Mart target tables. The procedures are compatible with Oracle, SQL Server, and DB2 platforms. Each Rapid Mart for Oracle Applications has a job OracleApps_FlexFields_Load to execute the stored procedure(s) as part of post-installation process:

• Use 'decoding' technique for multiple user-defined names for a single Descriptive Flexfield attribute or Key Flexfield segment (flexfields with multiple contexts and multiple structures). The Rapid Mart creates a


Rapid Mart Solutions A
dynamic view where each user-defined name is represented by its own column. For example, JOB Key Flexfield could have the following definition:
The Rapid Mart will generate a dynamic view for JOB dimension that contains multiple user-defined names for SEGMENT1 JOB Key Flexfield:

In this example, there will be only one value per a record in one of the four _FLEXK columns; they are mutually exclusive.

• Provide special treatment, 'Bucketing', of Accounting (GL#) flexfield to allow reporting on multiple charts of accounts. For the Accounting Key Flexfield, Rapid Marts have pre-defined dimensions that correspond to mostly used accounting reporting entities, such as Natural Account, Cost Center, Company, Product, etc.


Implementing Accounting Flexfield with Rapid MartsA

Out-of-the-box Rapid Marts group all user-defined accounting segments into 8 logical dimensions: Account, Cost Center, Product, Project, Company, Fund, Intercompany, District regardless of the Flexfield segment number and the Flexfield structure (chart of accounts).

Implementing Accounting Flexfield with Rapid Marts

This chapter describes how to customize Rapid Marts that deal with Oracle Applications Accounting Flexfield when out-of-the-box pre-defined accounting dimensions (or logical groups) are different from the Oracle Applications user-defined Accounting Flexfield segments.There are two options for customization of the back-end (Rapid Mart data model and ETL routine): physical and logical.• Physical customization requires changing Rapid Mart table names, ETL

routine objects, and the Universe structure update. It is more time consuming but the end result will provide better code readability for the future maintenance. It is recommended when implementing Rapid Marts at customer sites.

• Logical customization requires changes at Universe level only. You will create logical mapping (in form of a reference document) between Rapid Mart out-of-the-box accounting entities and custom entities to load correctly the Rapid Mart target tables. Then you will re-name universe classes and objects to reflect this logical mapping between Rapid Mart COA_<> tables and custom accounting entities. Logical customization


Implementing Accounting Flexfield with Rapid Marts A
can be used during POCs and when customization time is limited. Proper documenting of the logical mapping is important to avoid confusion between physical table names and the Universe object names.
Below we describe in detail the physical customization of Rapid Mart Accounting Flexfield solution.

Before Rapid Mart CustomizationBefore you start the Rapid Mart customization, follow Rapid Mart installation instructions described in Installing the Rapid Mart chapter of this document.You also need to set up global variables as described in Using the Rapid Mart chapter of this document in order to execute the Rapid Mart that loads information about Flexfields (OracleApps_FlexFields_Load job). This job will load AW_FLEX_FIELD_NAME Rapid Mart auxiliary table with metadata about Accounting Flexfields segments. Once the OracleApps_FlexFields_Load job ends successfully, identify what user names are defined for the Accounting Flexfield segments. Run the following query:SELECT a.FLEX_STRUCTURE_NAME, a.APPLICATION_COLUMN_NAME,

a.END_USER_COLUMN_NAME from AW_FLEX_FIELD_NAME a where a.FLEX_FILED_NAME = Accounting Flexfield' order by a.FLEX_FIELD_NAME, APPLICATION_COLUMN_NAMEWrite down associations of Accounting Flexfield Segments to their User-Defined names for each chart of Accounts (FLEX_STRUCTURE_NAME) as shown below.


Flexfield User-Defined Names Discovery
Decide which custom accounting dimensions you need to add/remove/edit in the Rapid Mart in addition to existing out-of-the-box 8 dimensions. Enter your findings in the table below. Consider re-using the existing dimensions by editing their names and ETL mappings.

FLEX_STRUCTURE_NAME

APPLICATION_COLUMN_NAME

END_USER_COLUMN_NAME

Logical Group (COA_<dimensions>)

ADB Accounting Flex SEGMENT1 Account ACCOUNTADB Accounting Flex SEGMENT2 Cost Center COST_CENTERADB Accounting Flex SEGMENT3 Product PRODUCTADB Accounting Flex SEGMENT12 Company COMPANYADB Accounting Flex SEGMENT13 Department DISTRICTADB Accounting Flex SEGMENT14 Alt Account ALT_ACCOUNTOPM Accounting Flex SEGMENT1 Alternative Account ALT_ACCOUNTOPM Accounting Flex SEBMENT2 ACCOUNT ACCOUNTOPM Accounting Flex SEBMENT10 Fund FUNDOPM Accounting Flex SEGMENT11 Project PROJECTOPM Accounting Flex SEGMENT20 COST CENTRE COST_CENTER


Customization Reference Table
Out-Of-The-Box Dimension

Out-of-the-box Hierarchy

Required Dimensions

Required Hierarchy

Add/Remove/Keep Flag

Hierarchy Flag (Keep/Add/Remove)

COA_ACCOUNT

COA_ACCOUNT_HZ, COA_ACCOUNT_VR

COA_ACCOUNT

COA_ACCOUNT_HZ, COA_ACCOUNT_VR

Keep Keep

COA_COST_CENTER

COA_COST_CENTER_HZ, COA_COST_CENTER_VR

COA_COST_CENTER

COA_COST_CENTER_HZ, COA_COST_CENTER_VR

Keep Keep

COA_COMPANY

COA_COMPANY_HZ, COA_COMPANY_VR

COA_COMPANY

COA_COMPANY_HZ, COA_COMPANY_VR

Keep Keep

COA_PRODUCT

COA_PRODUCT_HZ, COA_PRODUCT_VR

COA_PRODUCT

COA_PRODUCT_HZ, COA_PRODUCT_VR

Keep Remove

COA_PROJECT

COA_PROJECT_HZ, COA_PROJECT_VR

COA_PROJECT

COA_PROJECT_HZ, COA_PROJECT_VR

Keep Remove

COA_FUND N/A COA_FUND N/A Keep N/ACOA_DISTRICT

N/A COA_DISTRICT

COA_DISTRICT_HZ, COA_DISTRIC_VR

Keep Add

COA_INTERCOMPANY

N/A Remove N/A

COA_ALT_ACCOUNT

COA_ALT_ACCOUNT_HZ, COA_ALT_ACCOUNT_VR

Add Add


Rapid Mart Customization - Data Model Changes
For new accounting entities and corresponding dimension hierarchies, add new tables to the Rapid Mart target database. You can use the Rapid Mart Erwin diagram if you have a proper version of CA Data Modeler application or simply use the Rapid Mart ‘Create Tables’ SQL script to be create additional tables.All COA_<accounting_entity> dimensions have a similar structure. For Oracle platform:

The same applies to the dimension hierarchies. Horizontal hierarchy tables have 8-pre-defined levels with the following structure (for Oracle platform):

Column name Key Data type Column description

CHART_OF_ACCT_ID PK NUMBER(15) Key Flexfield structure identifier<accounting_entity>_CODE

PK VARCHAR2(150) Flexfield segment value for <accounting_entity> related sets

<accounting_entity>_DESC

VARCHAR2(240) Description of <accounting_entity> related set values

CHART_OF_ACCT_NAME VARCHAR2(30) GL# Key flexfield structure nameCHART_OF_ACCT_DESC VARCHAR2(240) GL# Key flexfield structure

description in selected languageLOAD_DATE DATETIME Date when the record was loadedLOAD_TIME VARCHAR2(8) Time when the record was loaded


CHART_OF_ACCT_ID NUMBER(15) Key flexfield structure identifierSEGMENT_NAME VARCHAR2(30) Set name that corresponds to the

chart of accounts segment<accounting_entity>_CODE

VARCHAR2(60) Current Leaf <accounting_entity> set value

LVL_0_<accounting_entity>_CODE

VARCHAR2(60) Level0 (root) for the current leaf of <accounting_entity> value

LEVEL_0_<accounting_entity>_DESC

VARCHAR2(240) Level 0 (root) for the current leaf of <accounting_entity> value description

LEAF_LEVEL INTEGER Leaf level in horizontal flatteningLVL_1_<accounting_entity>_CODE

VARCHAR2(60) Level 1 for the current leaf of <accounting_entity> value



LVL_1_<accounting_entity>_DESC

VARCHAR2(240) Level 1 for the current leaf of <accounting_entity> value description




























Accounting dimensions vertical hierarchy tables structure (for Oracle platform) is:





LOAD_DATE DATETIME Date when the record was loadedLOAD_TIME VARCHAR2(8) Time in a string format when the

record was loaded



CHART_OF_ACCT_ID PK NUMBER(15) Key flexfield structure identifierSEGMENT_NAME PK VARCHAR2(30) Set name that corresponds to the

chart of accounts segment<accounting_entity>_ANCESTOR

PK VARCHAR2(200) Ancestor <accounting_entity> code

<accounting_entity>_DESCENDENT

PK VARCHAR2(200) Descendent <accounting_entity> code

DEPTH INTEGER Depth of the decsendentROOT_FLAG INTEGER Root flag (1means this is a root)LEAF_FLAG INTEGER Leaf flag (1 means this is a leaf)<accounting_entity>_ANCESTR_DESC

VARCHAR2(240) Ancestor Company description

<accounting_entity>_DESCNDT_DESC

VARCHAR2(240) Descendent <accounting_entity> description

LOAD_DATE DATETIME Date when the record was loadedLOAD_TIME VARCHAR2(8) Time when the record was loaded


Modify CODE_COMBINATION table to include new columns (<accounting_entity>_CODE) that represent foreign keys to the new accounting dimensions and to remove columns that represent foreign keys for out-of-the-box accounting dimensions not to be used. The out-of-the-box CODE_COMBINATION table structure:
Rapid Mart Customization - Data Integrator Job ChangesOnce you have created new (or modified existing) custom accounting dimensions and corresponding hierarchy tables, you need to edit the OracleApps_Projects_Rapid_Mart job. During this customization step you will set up the Accounting Flexfield-related global variables and modify the job to load custom tables marked as ‘Add’ and remove the code that loads the dimensions marked as ‘Remove’ in the “Customization Reference Table” on page 313.

Creating Copies of Original Job ObjectsBefore you start customization, it is a good practice to replicate original ETL objects you will be modifying. With Data Integrator Designer, create a copy of the OracleApps_Projects_Rapid_Mart job you will be using to test the Accounting Flexfield customization and WF_AccountingFlexField_OA workflow that groups logic to load the Accounting Flexfield dimensions and


their hierarchies. You will also be modifying C_COASegment_OA, C_CodeCombination_OA, and C_COASegmentHierWithStaging_O A workflows:
Modifying WF_AccountingFlexField_OA WorkflowThe WF_AccountingFlexField_OA workflow includes all ETL objects related to loading CODE_COMBINATION, COA_<> dimensions, and COA_<> dimension hierarchies.


Customizing Global VariablesBefore editing the workflow, edit Initialize_Script script object and global variables associates with the Accounting Flexfield:
Delete global variables you will not use and create new ones to represent custom accounting entities. You can edit existing global variables that you will not be using instead of deleting/creating global variables.


When you have multiple charts of accounts defined in the Oracle Applications installation, the same accounting entity can be represented by different user-defined names (such as ‘COST CENTRE’ and ‘Cost Center’ in the example “Flexfield User-Defined Names Discovery” on page 312). If this is the case, you need to have as many global variables as many user-defined names exist for that accounting entity. These values are used to group the Accounting Flexfield segments together.
Customizing COA_<> DimensionsIn the Copy_1_WF_AccountingFlexField_OA workflow, keep C_<accounting_entity>Segment_OA workflow as-is for the accounting dimensions marked as ‘Keep’ (see “Customization Reference Table” on page 313). Edit/delete other C_<accounting_entity>Segment_OA workflows to match the list of accounting dimensions. If you have total more than 8 accounting dimension, replicate any existing one and edit.When editing C_<accounting_entity>Segment_OA workflows, modify both DF_<accounting_entity>Segment_OA and DF_<accounting_entity>SegmentDefault_OA dataflows. All DF_<accounting_entity>Segment_OA dataflows have similar structure:


ln each DF_<accounting_entity>Segment_OA dataflow:• modify InnerJoinQuery Query transform Where tab to match
<accounting_entity> with its corresponding global variable and the Schema Out <accounting_entity>_CODE column name as shown below


• In the DescriptionQuery Query Transform change
<accounting_entity>_CODE and <accounting_entity>_DESC column names to match the corresponding accounting dimension and the mapping for <accounting_entity>_CODE


• Import the corresponding COA_<accounting_entity> table you created
using Rapid Mart target datastore and use it as a target in the DF_<accounting_entity>Segment_OA. The table needs to have ‘Delete data from table before loading’ option turned ON.


When modifying DF_<accounting_entity>SegmentDefault_OA dataflows (they also have similar structure), you need to change <accounting_entity>_CODE and <accounting_entity>_DESC column names in ChartOfAccoutQuery, Query (Query transforms) and replace source and target tables with the corresponding COA_<accounting_entity> custom table.

Customizing C_COASegment_OAThe C_COASegment_OA workflow loads a Rapid Mart auxiliary table COA_SEGMENT used to properly populate CODE_COMBINATION and hierarchy dimensions. You need to edit DF_COASegment_OA to include all accounting entities, existing and custom:
Edit <accounting_entity>Query that you are not using; add additional query transforms if you have more than 8 accounting entities (COA_<accounting_entity> dimensions). In each query, modify DIMENSION_NAME mapping to have the corresponding global variable. If


you have several variables for the accounting entity to represent user-defined names (such as $G_COST_CENTER, $G_COST_CENTER_1), use the one without numbers ($G_COST_CENTER)
The Where text needs to be modified to match the global variable:


To match multiple global variables (such as $G_COST_CENTER, $G_COST_CENTER_1):.
Customizing C_CodeCombination_OARe-import CODE_COMBINATION table after you customized it as described in section “Rapid Mart Customization - Data Model Changes” on page 314.Create a copy of EDF_CodeCombination_OA and DF_CodeCombinationDefault_OA dataflows. These are the dataflows you will be customizing.The EDF_CodeCombination_OA dataflow assigns (“buckets”) Accounting Flexfield segments into 8 logical groups (accounting entity groups). By default they are: Account, Company, Cost Center, Product, Project, Fund, Intercompany, and District.


.
You need to edit DecodeSegmentName and MaxSelect query transforms to match CODE_COMBINATION customized table structure. For each <accounting_entity>_CODE column, modify the column name and its mapping to include the corresponding global variable:


.
The DF_CodeCombination_OA simply connects the embedded dataflow EDF_CodeCombination_OA with CODE_COMBINATION target table. In the dataflow copy you created, replace the original EDF_CodeCombination_OA embedded dataflow with the modified copy of it.


Customizing <accounting_entity> Hierarchy DimensionsThe Rapid Mart uses a staging table (COA_SEG_HIER_STAGE) to store Accounting Flexfield hierarchy information extracted from Oracle Applications FND_<> tables. COA_<accounting_entity>_HZ, COA_<accounting_entity>_VR hierarchy dimensions are loaded by a DF_COASegmentHier_OA dataflow.
Note: For performance reasons, you might want to split this dataflow in several dataflows when each dataflow loads a single set of COA_<accounting_entity>_HZ, COA_<accounting_entity>_VR hierarchy tables.Import custom hierarchy tables if necessary (see “Customization Reference Table” on page 313).


If you have total 5 sets of hierarchy tables, edit existing branches of the dataflow; create additional branches for additional hierarchy sets.Customize InnerJoin query transform’s Where text to include global variables that reference the accounting entities to load hierarchies for:
In each <accounting_entity>Select query transform that represents a custom accounting entity, modify the Schema Output column names <accounting_enttiy>_VALUE, <accounting_entity>_DESC and the query Where text to refer to the accounting entity:



Edit each Hierarchy transform (Horizontal and Vertical flattening) that represent the custom accounting entity. Select <accounting_entity>_VALUE as Child column, <accounting_entity>_DESC as Child attribute list, PAR_<accounting_entity>_VALUE as Parent column, and PAR_<accounting_entity>_DESC as Parent attribute list.



In each custom <accounting_entity>HorizRenameQuery query transform, rename <accounting_entity>_CODE, LVL_<>_<accounting_entity>_CODE, LVL_<>_<accounting_entity>_DESC Schema output column names and edit LVL_<>_<accounting_entity>_DESC columns mapping:




Modify each custom <accounting_entity>VerticRenameQuery. Edit <accounting_entity>_ANCESTOR, <accounting_entity>_DESCENDENT, <accounting_entity>_ANCTR_DESC, <accounting_entity>DESCD_DESC column names and <accounting_entity>_DESC column mappings:
In each TrimBlank<accounting_entity>HzQuery custom query transform, modify Schema Out column names and their mapping: <accounting_entity>_CODE, LVL_<>_<accounting_entity>_CODE, LVL_<>_<accounting_entity>_DESC to match the custom accounting entity:



In each TrimBlank<accounting_entity>HzQuery custom query transform, modify Schema Out column names and their mapping: <accounting_entity>_ANCESTOR, <accounting_entity>_DESCENDENT, <accounting_entity>_ANCTR_DESC, <accounting_entity>_DESCD_DESC to match the custom accounting entity:



At last, import into Data Integrator Object Library custom hierarchy tables (COA_<accounting_entity>_HZ, COA_<accounting_entity>_VR) and add them as table-loaders to the dataflow. All the loaders need to have 'Delete Data Before Loading' option turned on:



Completing Data Integrator Job CustomizationValidate the Test job and execute it. Verify that CODE_COMBINATION and all COA_<> tables get populated properly.After the testing is completed, incorporate the changes into OracleApps_Projects_Rapid_Mart job. You will need to edit global variable the same way in the OracleApps_Projects_Rapid_Mart job and replace the original WF_AccountingFlexField_OA workflow with its customized version.


Customizing Rapid Mart Universe
The Rapid Mart universe needs to be refreshed and updated to incorporate new/changed COA_<accounting_entity> tables. Accounting Flexfield related tables are located on the right side in the Universe Designer space:


Accounting Flexfield related universe classes, objects, and filters are grouped together:
These are the tasks to complete when customizing Accounting Flexfield related dimensions and objects in the universe.• Add custom COA_<accounting_entitty> dimensions;• Join new dimensions properly with refreshed CODE_COMBINATION

dimension;


• Join new COA_<accounting_entitty>_HZ, COA_
COA_<accounting_entitty>_VR hierarchy dimensions with corresponding COA_ COA_<accounting_entitty> and CODE_COMBINATION;

• Delete the joins for out-of-the-box COA_<> dimension that will not be used;

• Edit universe Contexts to include new joins in each context;• Edit Accounting Flexfield related classes, objects, and filters to

incorporate custom Accounting Flexfield segments and their hierarchies.Note: Re-use existing objects and classes to ensure that the Rapid Mart out-of-the-box reports will not fail.

• Validate the universe once you complete its modifications. See Universe chapter of this document for the list of acceptable validation errors.

• Test the changes by creating reports with customized objects.

Customizing Rapid Mart ReportsThe Rapid Mart out-of-the-box reports use Account, Cost Center, Company, and Product pre-defined accounting entities. Use the reports as templates to create custom reports to include custom Accounting Flexfield segments.


A


Rapid Mart Data Schema

appendix

B


Appendix BTable Summary

Rapid Mart Data Schema

This appendix provides detailed information about the tables and views in the BusinessObjects Projects Rapid Mart forOracle Applications. This information applies to an Oracle target datastore.

Auxiliary Tables AW_DESCR_FLEX_FIELD_MAP

AW_DESCR_FLEX_FIELD_NAME

AW_FLEX_FIELD_MAP

AW_FLEX_FIELD_NAME

AW_JOBEXECUTION

COA_SEG_HIER_STAGE

COA_SEGMENT

DATE_DRIVER

DATE_DRIVER_STAGE

DATE_HOLDER

LOOKUP_INDEXES

PEOPLE

PEOPLE_HOLD

PO_AGENT_STAGE

SERVICE_PERIOD_HOLD

Dimension Tables ACCOUNT_TYPE

ASSET_CATEGORY

ASSET_LOCATION

BOOK_TYPE

BUDGET_TYPE

COA_ACCOUNT

COA_ACCOUNT_HZ

COA_ACCOUNT_VR

COA_COMPANY

COA_COMPANY_HZ

COA_COMPANY_VR

COA_COST_CENTER

COA_COST_CENTER_HZ

COA_COST_CENTER_VR

COA_DISTRICT

COA_FUND

COA_INTERCOMPANY

COA_PRODUCT

COA_PRODUCT_HZ

COA_PRODUCT_VR

COA_PROJECT

1Rapid Mart Data Schema


COA_PROJECT_HZ

COA_PROJECT_VR

CODE_COMBINATION


CURRENCY

CURRENT_PEOPLE

DRAFT_REVENUE_FACT

EVENT

EVENT_TYPE

EXPENDITURE_GROUP

EXPENDITURE_TYPE

FLEX_VALUE_CHILD_TEMP

FLEX_VALUE_TEMP

JOB

ORGANIZATION

ORG_PRIMARY_HIER_HZ

ORG_PRIMARY_HIER_VR

ORG_STRUCTURE

PERIOD_CALENDAR

PROJECT

PROJECT_AGREEMENT


PROJECT_PERIOD

PROJECT_RESOURCE

REVENUE_CATEGORY

REVENUE_SOURCE

SET_OF_BOOKS

TASK

TASK_HIER_HZ

TASK_HIER_VR

TIME_DIM

TRANSFER_STATUS

VENDOR

VENDOR_CONTACT

VENDOR_SITE

Fact Tables BUDGET_LINE_FACT

BUDGET_SUMMARY_FACT

DRAFT_INVOICE_FACT

EVENT_DIST_FACT


EXPENDITURE_FACT


PROJECT_ASSET_FACT






AppendixTable Column Details B

ACCOUNT_TYPE

GL Code combination Account Type reference dimension

# Column Name Key Column Desc ColumnDatatype

DtypeLength Precision Scale Is

Nullable

1 ACCOUNT_TYPE_CODE PK Key flexfield combination type (Asset, Liability, etc) VARCSTR 30 0 0 no

2 ACCOUNT_TYPE_DESC Account Type value Description VARCSTR 240 0 0 yes

3 ACCOUNT_TYPE_NAME QuickCode meaning (name) for ACCOUNT TYPElookup type VARCSTR 80 0 0 no

4 END_DATE_ACTIVE The date when the QuickCode becomes inactive DATE 24 0 9 yes

5 LOAD_DATE Date when the record was loaded DATE 24 0 9 yes

6 LOAD_TIME Time in a string format when the record was loadedinto the target table VARCSTR 8 0 0 yes

7 START_DATE_ACTIVE The date when the QuickCode becomes active DATE 24 0 9 yes



ASSET_CATEGORY

Asset Category dimenison (represents CAT# key flexfield and dynamically generated ASSET_CATEGORY_VIEW view)



Nullable

1 CATEGORY_DESC Translated Description of an asset category VARCSTR 40 0 0 yes

2 CATEGORY_ID PK Unique identification number for each asset categoryyou defined DECIMAL 48 15 0 no

3 CATEGORY_SEGMENT1 Asset category key flexfield segment column VARCSTR 30 0 0 yes







10 CATEGORY_TYPE_NAME

Meaning of the lookup code of type = CATEGORYTYPE; translatable VARCSTR 80 0 0 yes

11 CREATED_BY_NAMEApplication username (what a user types in at theOracle Applications signon screen) who created therecord in the source system

VARCSTR 100 0 0 yes

12 CREATION_DATE Date when the record was created in the applicationsystem DATE 24 0 9 yes

13 IS_CAPITALIZED_FLAG 'Y' if assets in this category are capitalized assets;otherwise it is 'N' VARCSTR 1 0 0 yes

14 IS_INVENTORIAL Indicates whether the asset should be included inphysical inventory (Y/N) VARCSTR 1 0 0 yes

15 IS_LEASED_FLAG Set to Y if category is for lease; otherwise it is set toN VARCSTR 1 0 0 yes






Nullable

17 LOAD_TIME Time in a string format (HH24:MI:SS) when therecord was loaded VARCSTR 20 0 0 yes

18 OWNED_LEASED Indicates whether the assets in this category areowned or leased VARCSTR 6 0 0 yes

19 PROPERTY_1245_1250 Indicates whether assets in this category are 1245property class or 1250 property class VARCSTR 4 0 0 yes

20 PROPERTY_TYPE_NAME

Meaning of the lookup code of type PROPERTYTYPE; translatable VARCSTR 80 0 0 yes

ASSET_LOCATION

Asset Location dimension (corresponds to LOC# key flexfield and dynamically generated ASSET_LOCATION_VIEW view)



Nullable


2 LOAD_TIME Time when the record was loaded VARCSTR 8 0 0 yes

3 LOCATION_ID PK Unique identification number for each locationdefined in the table DECIMAL 48 15 0 no

4 LOCATION_SEGMENT1 Key flexfield segment VARCSTR 30 0 0 yes









AW_DESCR_FLEX_FIELD_MAP

Table containing descriptive flex field mappings



Nullable

1 COLUMN_PREFIX Optional prefix used in target table column name VARCSTR 30 0 0 yes

2 DESCRIPTIVE_FLEXFIELD_NAME PK Application table name VARCSTR 40 0 0 no

3 LOAD_DATE Date when the record was loaded DATE 24 0 9 no

4 LOAD_TIME Time when the record was loaded VARCSTR 20 0 0 no

5 TABLE_NAME PK Target table name VARCSTR 30 0 0 no

AW_DESCR_FLEX_FIELD_NAME

Table containing descriptive flex field names



Nullable

1 APPLICATION_COLUMN_NAME PK Application column name VARCSTR 30 0 0 no

2 APPLICATION_ID PK Application identifier DECIMAL 48 10 0 no

3 CONTEXT_COLUMN_NAME

The name of the structure defining column for theflexfield VARCSTR 30 0 0 yes

4 DESCRIPTIVE_FLEXFIELD_NAME PK Application table name VARCSTR 40 0 0 no

5 DESCRIPTIVE_FLEX_CONTEXT_CODE PK Descriptive flexfield structure name VARCSTR 30 0 0 no

6 END_USER_COLUMN_NAME End user column name VARCSTR 32 0 0 yes

7 GLOBAL_FLAG Flag to indicate whether the context field valueidentifies a global segment structure VARCSTR 1 0 0 yes





AW_FLEX_FIELD_MAP

Table containing key flex field mappings



Nullable

1 APPLICATION_TABLE_NAME PK Application table name VARCSTR 30 0 0 no

2 COLUMN_PREFIX Optional prefix used in target table column name VARCSTR 30 0 0 yes

3 FLEX_FIELD_NAME Key flexfield structure identifier, only needed touniquely identify if there are duplicates VARCSTR 30 0 0 yes

4 FLEX_STRUCTURE_NAME

Key flexfield structure name, only needed to uniquelyidentify if there are duplicates VARCSTR 30 0 0 yes



7 TABLE_NAME PK Target table name VARCSTR 30 0 0 no



AW_FLEX_FIELD_NAME

Table containing key flex field names



Nullable

1 APPLICATION_COLUMN_NAME PK Application column name VARCSTR 30 0 0 no

2 APPLICATION_TABLE_NAME PK Application table name VARCSTR 30 0 0 no

3 COLUMN_SEQ_NUM Segment number DECIMAL 48 15 0 yes

4 END_USER_COLUMN_NAME End user column name VARCSTR 32 0 0 yes

5 FLEX_FIELD_NAME PK Key flexfield structure identifier VARCSTR 40 0 0 no

6 FLEX_STRUCTURE_NAME PK Key flexfield structure name VARCSTR 30 0 0 no



AW_JOBEXECUTION

AW internal table to trace job execution status



Nullable

1 EXTRACTHIGH Extract run date VARCSTR 20 0 0 yes

2 EXTRACTLOW Extract start date VARCSTR 20 0 0 yes

3 LOAD_DATE Date and time when the record was loaded VARCSTR 20 0 0 yes

4 NAME PK Job name VARCSTR 64 0 0 no

5 STATUS Job run status VARCSTR 12 0 0 yes



BOOK_TYPE

Depreciation book dimension with control information



Nullable

1 BOOK_CLASS_NAME Meaning of the lookup code; translatable VARCSTR 80 0 0 yes

2 BOOK_TYPE_ID PK Book name code (unique identifier) VARCSTR 15 0 0 no

3 BOOK_TYPE_NAME Description of the book VARCSTR 30 0 0 yes


5 CURRENCY_CODE_FNC Functional Currency Code VARCSTR 15 0 0 yes

6 CURRENT_FISCAL_YEAR Current fiscal year for the book DECIMAL 48 4 0 yes

7 DATE_INEFFECTIVE Date that the book is no longer active DATE 24 0 9 yes

8 DEPRN_CALENDAR_NAME Name of depreciation calendar VARCSTR 15 0 0 yes

9 FISCAL_YEAR_NAME Name of fiscal year for which the book is defined VARCSTR 30 0 0 yes

10 INITIAL_DATE Date the last time depreciation was run for this bookon the previous asset system DATE 24 0 9 yes

11 LAST_DEPRN_RUN_DATE Date of the last depreciation DATE 24 0 9 yes



14 PAR_BOOK_TYPE_ID Associated corporate book used for trackingdistributions VARCSTR 15 0 0 yes

15 SET_OF_BOOKS_NAME Accounting books name VARCSTR 30 0 0 yes



BUDGET_LINE_FACT

Project Budget fact table at budget line grain



Nullable

1 AGREEMENT_ID Unique identifier of the agreement that is impacted bythe control item DECIMAL 48 15 0 no

2 BASELINED_BY_PERSON_ID The identifier of the person who baselined the budget DECIMAL 48 10 0 no

3 BASELINED_DATE PK The baselined date of the budget version DATETIME 24 0 9 no

4 BORROWED_REVENUE The borrowed revenue of budget line DECIMAL 48 28 7 yes

5 BUDGET_LINE_ID PK Unique identifier of budget line DECIMAL 48 15 0 no

6 BUDGET_STATUS The status of a budget NVARCSTR 80 0 0 no

7 BUDGET_TYPE_CODE PK The type of budget NVARCSTR 30 0 0 no

8 BURDENED_COST The burdened cost of the budget line DECIMAL 48 28 7 yes

9 CAPACITY The capacity of budget line DECIMAL 48 28 7 yes

10 CHANGE_REASON_CODE The reason to create the budget line NVARCSTR 30 0 0 no

11 CODE_COMBINATION_ID Accounting code identifier for the budget line DECIMAL 48 15 0 no

12 COST_ADJ The cost adjustment of budget line DECIMAL 48 28 7 yes

13 CREATION_DATE Budget line creation date. DATETIME 24 0 9 yes

14 CURRENCY_CODE_PRJ The project currency code NVARCSTR 15 0 0 no

15 CURRENT_FLAG Flag that indicates whether the budget version is thecurrent baselined budget NVARCSTR 1 0 0 no

16 END_DATE The end date of the budget line DATETIME 24 0 9 no





Nullable

17 EVENT_TYPE_CLASSIFICATION Holds the identifier of the Event Type Classification. NVARCSTR 30 0 0 no

18 EVENT_TYPE_ID Holds the identifier of the Event Type DECIMAL 48 15 0 no

19 EXPENDITURE_CATEGORY Holds the identifier of the Expenditure Category. NVARCSTR 30 0 0 no

20 EXPENDITURE_TYPE_ID Holds the identifier of the Expenditure Type DECIMAL 48 15 0 no

21 GL_PERIOD_NAME GL period of the budget line NVARCSTR 15 0 0 yes

22 HEAD_COUNT The head count of budget line DECIMAL 48 28 7 yes

23 HEAD_COUNT_ADJ The head count adjustment of budget line DECIMAL 48 28 7 yes

24 JOB_ID PK Holds the identifier of the Job. DECIMAL 48 15 0 no

25 LENT_RESOURCE_COST The lent resource cost of budget line DECIMAL 48 28 7 yes

26 LINE_DESCRIPTION The description of the budget line NVARCSTR 255 0 0 no

27 LOAD_DATE Date when the record was loaded DATETIME 24 0 9 no

28 LOAD_TIME Time when the record was loaded NVARCSTR 8 0 0 no

29 NON_LABOR_RESOURCE Holds the identifier of the Non Labor Resource. NVARCSTR 20 0 0 no

30 NON_LABOR_RESOURCE_ORG_ID

Holds the identifier of the Non Labor ResourcesOrganization. DECIMAL 48 15 0 no

31 ORGANIZATION_STRUCTURE_ID

Identifier of the default organization hierarchy usedfor reporting DECIMAL 48 15 0 yes

32 ORG_ID Holds the identifier of the Organization. DECIMAL 48 15 0 no

33 ORG_STRUCTURE_VERSION_ID

Identifier of the default organization hierarchy versionused for reporting DECIMAL 48 15 0 yes





Nullable

34 PERIOD_NAME The period of the budget line NVARCSTR 15 0 0 no

35 PERIOD_SET_NAME Accounting calendar name NVARCSTR 15 0 0 no

36 PERSON_ID Holds the identifier of the employee. DECIMAL 48 10 0 no

37 PROJECT_ID PK The identifier of the project for which the budget isentered DECIMAL 48 15 0 no

38 QUANTITY The quantity of the budget line DECIMAL 48 28 7 yes

39 RAW_COST The raw cost of the budget line DECIMAL 48 28 7 yes

40 RESOURCE_ID PK The identifier of the resource that is being used as amember of the resource list DECIMAL 48 15 0 no

41 REVENUE The revenue of the budget line DECIMAL 48 28 7 yes

42 REVENUE_ADJ The revenue adjustment of budget line DECIMAL 48 28 7 yes

43 REVENUE_CATEGORY Holds the identifier of the Revenue Category NVARCSTR 30 0 0 no

44 SET_OF_BOOKS_ID The identifier of the General Ledger set of booksused by Oracle Projects DECIMAL 48 15 0 yes

45 START_DATE The start date of the budget line DATETIME 24 0 9 no

46 START_ORGANIZATION_ID

Identifier of the highest organization used in defaultreporting organization hierarchy version DECIMAL 48 15 0 yes

47 TASK_ID PKThe identifier of the task that the resource isassigned to. This is set to 0 if the budget is entered atthe project level

DECIMAL 48 15 0 no

48 TP_COST_IN The transferprice cost in of budget line DECIMAL 48 28 7 yes

49 TP_COST_OUT The transferprice cost out of budget line DECIMAL 48 28 7 yes

50 TP_REVENUE_IN The transferprice revenue in of budget line DECIMAL 48 28 7 yes





Nullable

51 TP_REVENUE_OUT The transferprice revenue out of budget line DECIMAL 48 28 7 yes

52 UNASSIGNED_TIME_COST The unassigned time cost of budget line DECIMAL 48 28 7 yes

53 UTILIZATION_ADJ The utilization percent adjustment of budget line DECIMAL 48 28 7 yes

54 UTILIZATION_HOURS The utilization hours of budget line DECIMAL 48 28 7 yes

55 UTILIZATION_PERCENT The utilization percent of budget line DECIMAL 48 28 7 yes

56 VENDOR_ID Holds the identifier of the Supplier. DECIMAL 48 28 7 no

57 VERSION_DESCRIPTION The description of the budget version NVARCSTR 255 0 0 no

58 VERSION_NAME The name of the budget version NVARCSTR 60 0 0 no

59 VERSION_NUMBERThe version number of the budget. For draft budget,the version number is always 1, for baselined budgetthis number is increased sequentially

DECIMAL 48 15 0 no



BUDGET_SUMMARY_FACT

Project Budget Summary fact table containing summarized budget data



Nullable

1 BASE_BURDENED_COST_ITD Inception to date base burdened cost for project DECIMAL 48 28 7 yes

2 BASE_BURDENED_COST_PP Base burdened cost for prior GL or PA period DECIMAL 48 28 7 yes

3 BASE_BURDENED_COST_PTD

Period to date base burdened cost for PA or GLperiod DECIMAL 48 28 7 yes

4 BASE_BURDENED_COST_TOT Total base burdened cost DECIMAL 48 28 7 yes

5 BASE_BURDENED_COST_YTD Year to date base burdened cost for project DECIMAL 48 28 7 yes

6 BASE_LABOR_HOURS_ITD Inception to date base labor hours for project DECIMAL 48 28 7 yes

7 BASE_LABOR_HOURS_PP Base labor hours for prior GL or PA period DECIMAL 48 28 7 yes

8 BASE_LABOR_HOURS_PTD Period to date base labor hours for PA or GL period DECIMAL 48 28 7 yes

9 BASE_LABOR_HOURS_TOT Total base labor hours DECIMAL 48 28 7 yes

10 BASE_LABOR_HOURS_YTD Year to date base labor hours for project DECIMAL 48 28 7 yes

11 BASE_QUANTITY_ITD Inception to date base quantity for project DECIMAL 48 28 7 yes

12 BASE_QUANTITY_PP Base quantity for prior GL or PA period DECIMAL 48 28 7 yes

13 BASE_QUANTITY_PTD Period to date base quantity for PA or GL period DECIMAL 48 28 7 yes

14 BASE_QUANTITY_TOT Total base quantity DECIMAL 48 28 7 yes

15 BASE_QUANTITY_YTD Year to date base quantity for project DECIMAL 48 28 7 yes

16 BASE_RAW_COST_ITD Inception to date base raw cost for project DECIMAL 48 28 7 yes





Nullable

17 BASE_RAW_COST_PP Base raw cost for prior GL or PA period DECIMAL 48 28 7 yes

18 BASE_RAW_COST_PTD Period to date base raw cost for PA or GL period DECIMAL 48 28 7 yes

19 BASE_RAW_COST_TOT Total base raw cost DECIMAL 48 28 7 yes

20 BASE_RAW_COST_YTD Year to date base raw cost for project DECIMAL 48 28 7 yes

21 BASE_REVENUE_ITD Inception to date base revenue for project DECIMAL 48 28 7 yes

22 BASE_REVENUE_PP Base revenue for prior GL or PA period DECIMAL 48 28 7 yes

23 BASE_REVENUE_PTD Period to date base revenue for PA or GL period DECIMAL 48 28 7 yes

24 BASE_REVENUE_TOT Total base revenue DECIMAL 48 28 7 yes

25 BASE_REVENUE_YTD Year to date base revenue project DECIMAL 48 28 7 yes

26 BASE_UNIT_OF_MEASURE Base unit of measurement NVARCSTR 30 0 0 no

27 BUDGET_TYPE_CODE PK The identifier of budget type for which this line wascreated NVARCSTR 30 0 0 no

28 CREATION_DATE Creation date fromPA_PROJECT_ACCUM_HEADERS. DATETIME 24 0 9 yes

29 CURRENCY_CODE_PRJ Currency code of the project NVARCSTR 15 0 0 yes

30 GL_PERIOD_NAME Last accumulation GL Period NVARCSTR 15 0 0 yes









Nullable

34 ORG_ID Operating unit identifier for multiorganizationinstallations DECIMAL 48 15 0 no



36 ORIG_BURDENED_COST_ITD Inception to date original burdened cost for project DECIMAL 48 28 7 yes

37 ORIG_BURDENED_COST_PP Original burdened cost for prior GL or PA period DECIMAL 48 28 7 yes

38 ORIG_BURDENED_COST_PTD

Period to date original burdened cost for PA or GLperiod DECIMAL 48 28 7 yes

39 ORIG_BURDENED_COST_TOT Total original burdened cost DECIMAL 48 28 7 yes

40 ORIG_BURDENED_COST_YTD Year to date original burdened cost project DECIMAL 48 28 7 yes

41 ORIG_LABOR_HOURS_ITD Inception to date original labor hours for project DECIMAL 48 28 7 yes

42 ORIG_LABOR_HOURS_PP Original labor hours for prior GL or PA period DECIMAL 48 28 7 yes

43 ORIG_LABOR_HOURS_PTD

Period to date original labor hours for PA or GLperiod DECIMAL 48 28 7 yes

44 ORIG_LABOR_HOURS_TOT Total original labor hours DECIMAL 48 28 7 yes

45 ORIG_LABOR_HOURS_YTD Year to date original labor hours for project DECIMAL 48 28 7 yes

46 ORIG_QUANTITY_ITD Inception to date original quantity for project DECIMAL 48 28 7 yes

47 ORIG_QUANTITY_PP Original quantity for prior GL or PA period DECIMAL 48 28 7 yes

48 ORIG_QUANTITY_PTD Period to date original quantity for PA or GL period DECIMAL 48 28 7 yes

49 ORIG_QUANTITY_TOT Total original quantity DECIMAL 48 28 7 yes

50 ORIG_QUANTITY_YTD Year to date original quantity for project DECIMAL 48 28 7 yes





Nullable

51 ORIG_RAW_COST_ITD Inception to date original raw cost for project DECIMAL 48 28 7 yes

52 ORIG_RAW_COST_PP Original raw cost for prior GL or PA period DECIMAL 48 28 7 yes

53 ORIG_RAW_COST_PTD Period to date original raw cost for PA or GL period DECIMAL 48 28 7 yes

54 ORIG_RAW_COST_TOT Total original raw cost DECIMAL 48 28 7 yes

55 ORIG_RAW_COST_YTD Year to date original raw cost for project DECIMAL 48 28 7 yes

56 ORIG_REVENUE_ITD Inception to date original revenue for project DECIMAL 48 28 7 yes

57 ORIG_REVENUE_PP Original revenue for prior GL or PA period DECIMAL 48 28 7 yes

58 ORIG_REVENUE_PTD Period to date original revenue for PA or GL period DECIMAL 48 28 7 yes

59 ORIG_REVENUE_TOT Total original revenue DECIMAL 48 28 7 yes

60 ORIG_REVENUE_YTD Year to date original revenue for project DECIMAL 48 28 7 yes

61 PERIOD_NAME Last accumulation GL or PA period, depending onthe imp. option NVARCSTR 20 0 0 no


63 PROJECT_ACCUM_ID PK The identifier which uniquely defines this line DECIMAL 48 15 0 no

64 PROJECT_ID PK The identifier of project for which the header wascreated DECIMAL 48 15 0 no

65 RESOURCE_ID PK The identifier of resource for which the header wascreated DECIMAL 48 15 0 no








Nullable

68 TASK_ID PK The identifier of task for which the header wascreated DECIMAL 48 15 0 no

BUDGET_TYPE

Budget Type dimension



Nullable

1 BUDGET_TYPE The short, userfriendly name of the budget type VARCSTR 30 0 0 yes

2 BUDGET_TYPE_CODE PK The unique identifier of budget type VARCSTR 30 0 0 no

3 BUDGET_TYPE_DESCRIPTION The description of the budget type VARCSTR 255 0 0 yes





COA_ACCOUNT

Chart of accounts Account dimension that corresponds to segments (sets) that represent a natural account



Nullable

1 ACCOUNT_CODE PK Flexfield segment value for Account related sets VARCSTR 150 0 0 no

2 ACCOUNT_DESC Description of Company related set values VARCSTR 240 0 0 yes

3 CHART_OF_ACCT_DESC GL# Key flexfield structure description in selectedlanguage VARCSTR 240 0 0 yes

4 CHART_OF_ACCT_ID PK Key Flexfield structure identifier DECIMAL 48 15 0 no

5 CHART_OF_ACCT_NAME GL# Key flexfield structure name VARCSTR 30 0 0 yes





COA_ACCOUNT_HZ

Natural Account horizonally flattenned hierarchy. A child value can belong to more than one parent value



Nullable

1 ACCOUNT_CODE PK Current Leaf Account set value VARCSTR 60 0 0 yes

2 CHART_OF_ACCT_ID Key flexfield structure identifier DECIMAL 48 15 0 yes

3 LEAF_LEVEL Current Leaf level number (08) in the horizontalhierarchy INTEGER 4 0 0 yes



6 LVL_0_ACCOUNT_CODE PK Level 0 for the current leaf of Account value VARCSTR 60 0 0 yes

7 LVL_0_ACCOUNT_DESC Level 0 for the current leaf of Account valuedescription VARCSTR 240 0 0 yes

8 LVL_1_ACCOUNT_CODE Level 1 for the current leaf of Account value VARCSTR 60 0 0 yes













Nullable








24 SEGMENT_NAME PK Set name that corresponds to the chart of accountssegment VARCSTR 30 0 0 yes



COA_ACCOUNT_VR

Natural Account vertically flattenned hierarchy. A child value can belong to more than one parent value



Nullable

1 ACCNT_ANCESTOR PK Ancestor Account code VARCSTR 60 0 0 no

2 ACCNT_ANCESTR_DESC Ascestor Account description VARCSTR 240 0 0 yes

3 ACCNT_DESCENDENT PK Descendent Account code VARCSTR 150 0 0 no

4 ACCNT_DESCNDT_DESC Descendent Account description VARCSTR 240 0 0 yes

5 CHART_OF_ACCT_ID PK Key flexfield structure identifier DECIMAL 48 15 0 no

6 DEPTH Depth of the decsendent INTEGER 4 0 0 yes

7 LEAF_FLAG Leaf flag (1 means this is a leaf) INTEGER 4 0 0 yes



10 ROOT_FLAG Root flag (1means this is a root) INTEGER 4 0 0 yes

11 SEGMENT_NAME PK Set name that corresponds to the chart of accountssegment VARCSTR 30 0 0 no



COA_COMPANY

Chart of accounts company dimension that corresponds to segments (sets) that represent legal enties



Nullable


2 CHART_OF_ACCT_ID PK Key flexfield structure identifier DECIMAL 48 15 0 no


4 COMPANY_CODE PK Flexfield segment value for Company related sets VARCSTR 150 0 0 no

5 COMPANY_DESC Description of Company related set values VARCSTR 240 0 0 yes





COA_COMPANY_HZ

Company related segment values horizonally flattenned hierarchy. A child value can belong to more than one parent value



Nullable

1 CHART_OF_ACCT_ID PK Key flexfield structure number DECIMAL 48 15 0 yes

2 COMPANY_CODE PK Current Leaf Company set value VARCSTR 60 0 0 yes




6 LVL_0_COMPANY_CODE Level 0 for the current leaf of Company value VARCSTR 60 0 0 yes

7 LVL_0_COMPANY_DESC Level 0 for the current leaf of Company valuedescription VARCSTR 240 0 0 yes














Nullable











COA_COMPANY_VR

Company releated segment values vertically flattenned hierarchy. A child value can belong to more than one parent value



Nullable

1 CHART_OF_ACCT_ID PK Key flexfield structure number VARCSTR 15 0 0 no

2 CMPNY_ANCESTR_DESC Ascestor Company description VARCSTR 240 0 0 yes

3 CMPNY_DESCNDT_DESC Descendent Company description VARCSTR 240 0 0 yes

4 COMPANY_ANCESTOR PK Ancestor Company code VARCSTR 200 0 0 no

5 COMPANY_DESCENDENT PK Descendent Company code VARCSTR 200 0 0 no









COA_COST_CENTER

Chart of accounts Cost Center dimension that corresponds to segments (sets) that represent functional areas of business



Nullable




4 COST_CENTER_CODE PK Flexfield segment value for Cost Center related sets VARCSTR 150 0 0 no

5 COST_CENTER_DESC Description of Cost Center related set values VARCSTR 240 0 0 yes





COA_COST_CENTER_HZ

Cost Center related segment values horizonally flattenned hierarchy. A child value can belong to more than one parent value



Nullable


2 COST_CENTER_CODE PK Current Leaf Cost Center set value VARCSTR 60 0 0 yes




6 LVL_0_CST_CTR_CODE Level 0 for the current leaf of Cost Center value VARCSTR 60 0 0 yes

7 LVL_0_CST_CTR_DESC Level 0 for the current leaf of Cost Center valuedescription VARCSTR 240 0 0 yes














Nullable











COA_COST_CENTER_VR

Cost Center releated segment values vertically flattenned hierarchy. A child value can belong to more than one parent value



Nullable


2 CST_CTR_ANCESTOR PK Ancestor Cost Center code VARCSTR 200 0 0 no

3 CST_CTR_ANCTR_DESC Ascestor Cost Center description VARCSTR 240 0 0 yes

4 CST_CTR_DESCD_DESC Descendent Cost Center description VARCSTR 240 0 0 yes

5 CST_CTR_DESCENDENT PK Descendent Cost Center code VARCSTR 200 0 0 no









COA_DISTRICT

Chart of accounts District dimension that corresponds to segments (sets) that represent geographical locations



Nullable




4 DISTRICT_CODE PK Flexfield segment value for Location related sets VARCSTR 150 0 0 no

5 DISTRICT_DESC Description of Location related set values VARCSTR 240 0 0 yes



COA_FUNDChart of accounts Fund dimension that corresponds to segments (sets) that represent fiscal and accounting entities with a selfbalancing setof accounts for governmental



Nullable




4 FUND_CODE PK Flexfield segment value for Fund related sets VARCSTR 150 0 0 no

5 FUND_DESC Description of Fund related set values VARCSTR 240 0 0 yes





COA_INTERCOMPANY

Chart of accounts Inercompany dimension that corresponds to segments (sets) that represent intercompany entites



Nullable




4 INTERCOMPANY_CODE PK Flexfield segment value for InterCompany relatedsets VARCSTR 150 0 0 no

5 INTERCOMPANY_DESC Description of InterCompany related set values VARCSTR 240 0 0 yes



COA_PRODUCTChart of accounts Product dimension that corresponds to segments (sets) that represent products. It is different from ITEM dimension thatrepresents product master



Nullable






6 PRODUCT_CODE PK Flexfield segment value for Product related sets VARCSTR 150 0 0 no

7 PRODUCT_DESC Description of Product related set values VARCSTR 240 0 0 yes



COA_PRODUCT_HZ

Product related segment values horizonally flattenned hierarchy. A child value can belong to more than one parent value



Nullable





5 LVL_0_PRODUCT_CODE Level 0 for the current leaf of Product value VARCSTR 60 0 0 yes

6 LVL_0_PRODUCT_DESC Level 0 for the current leaf of Product valuedescription VARCSTR 240 0 0 yes















Nullable







23 PRODUCT_CODE PK Current Leaf Product set value VARCSTR 60 0 0 yes




COA_PRODUCT_VR

Product releated segment values vertically flattenned hierarchy. A child value can belong to more than one parent value



Nullable






6 PRODUCT_ANCESTOR PK Ancestor Product code VARCSTR 200 0 0 no

7 PRODUCT_DESCENDENT PK Descendent Product code VARCSTR 200 0 0 no

8 PROD_ANCESTR_DESC Ascestor Product description VARCSTR 240 0 0 yes

9 PROD_DESCNDT_DESC Descendent Product description VARCSTR 240 0 0 yes





COA_PROJECTChart of accounts Project dimension that corresponds to segments (sets) that represent products for which revenue and expense can betracked



Nullable






6 PROJECT_CODE PK Flexfield segment value for Project related sets VARCSTR 150 0 0 no

7 PROJECT_DESC Description of Project related set values VARCSTR 240 0 0 yes



COA_PROJECT_HZ

Project related segment values horizonally flattenned hierarchy. A child value can belong to more than one parent value



Nullable

1 CHART_OF_ACCT_ID Key flexfield structure number DECIMAL 48 15 0 yes




5 LVL_0_PROJECT_CODE Level 0 for the current leaf of Project value VARCSTR 60 0 0 yes

6 LVL_0_PROJECT_DESC Level 0 for the current leaf of Project valuedescription VARCSTR 240 0 0 yes















Nullable







23 PROJECT_CODE Current Leaf Project set value VARCSTR 60 0 0 yes

24 SEGMENT_NAME Set name that corresponds to the chart of accountssegment VARCSTR 30 0 0 yes



COA_PROJECT_VR

Project releated segment values vertically flattenned hierarchy. A child value can belong to more than one parent value



Nullable






6 PROJECT_ANCESTOR PK Ancestor Project code VARCSTR 200 0 0 no

7 PROJECT_ANCESTR_DESC Ascestor Project description VARCSTR 240 0 0 yes

8 PROJECT_DESCENDENT PK Descendent Project code VARCSTR 200 0 0 no

9 PROJECT_DESCNDT_DESC Descendent Project description VARCSTR 240 0 0 yes





COA_SEG_HIER_STAGE

Temporary table to store Oracle Application Key flexfield hierarchy information



Nullable

1 APPLICATION_COLUMN_NAME Flexfield column name VARCSTR 30 0 0 yes

2 CHART_OF_ACCT_ID PK Key flexfield structure number DECIMAL 48 15 0 no

3 ID_FLEX_NUMBER Key flexfield structure number DECIMAL 48 15 0 yes



6 PAR_SEGMENT_DESC Parent value description VARCSTR 240 0 0 yes

7 PAR_SEGMENT_VALUE PK Concatenated fields of composite PK for the parentvalue VARCSTR 60 0 0 no

8 SEGMENT_DESC Child value description VARCSTR 240 0 0 yes


10 SEGMENT_VALUE PK Concatenated fields of composite PK for the childvalue VARCSTR 150 0 0 no

COA_SEGMENT

Rapid Mart auxiliary table that mapps segment (set) names to fixed dimensions



Nullable

1 DIMENSION_NAME PK Chart of Accounts dimension (fixed name) VARCSTR 50 0 0 no






CODE_COMBINATION

Translation dimension to store code combinations with translated segments (to 8 fixed dimensions) and their attributes



Nullable

1 ACCOUNT_CODE Max Segment value that correspon toAccountrelated sets NVARCSTR 150 0 0 yes

2 ACCOUNT_DESC Concatenated segment names that represent thecode combination NVARCSTR 2000 0 0 yes

3 ACCOUNT_TYPE_CODE Key flexfield combination type (Asset, Liability, etc) NVARCSTR 30 0 0 yes

4 CHART_OF_ACCT_ID Key flexfield structure identifier DECIMAL 48 15 0 yes

5 CODE_COMBINATION_ID PK Key flexfield combination defining column DECIMAL 48 15 0 no

6 COMPANY_CODE Max Segment value that correspon toCompanyrelated sets NVARCSTR 150 0 0 yes

7 CONCAT_ACCOUNT Concatenated segments NVARCSTR 256 0 0 yes

8 COST_CENTER_CODE Max Segment value that correspon to CostCenterrelated sets NVARCSTR 150 0 0 yes

9 DISTRICT_CODE Max Segment value that correspon toLocationrelated sets NVARCSTR 150 0 0 yes

10 FUND_CODE Max Segment value that correspon to Fundrelatedsets NVARCSTR 150 0 0 yes

11 INTERCOMPANY_CODE Max Segment value that correspon toIntercompanyrelated sets NVARCSTR 150 0 0 yes

12 LOAD_DATE Date when the record was loaded DATETIME 24 0 9 yes

13 LOAD_TIME Time in a string format when the record was loadedinto the target table NVARCSTR 8 0 0 yes

14 PRODUCT_CODE Max Segment value that correspon toProductrelated sets NVARCSTR 150 0 0 yes

15 PROJECT_CODE Max Segment value that correspon to Projectrelatedsets NVARCSTR 150 0 0 yes

16 SUMMARY_FLAG Summary account flag NVARCSTR 1 0 0 yes





Nullable

17 TEMPLATE_ID Summary template defining column DECIMAL 48 15 0 yes


Cost Distribution Line Type reference dimension



Nullable

1 COST_DIST_LINE_TYPE PK Cost distribution line type code NVARCSTR 30 0 0 no

2 COST_DIST_TYPE_DESC Cost Distribution Line Type value Description NVARCSTR 240 0 0 yes

3 COST_DIST_TYPE_NAME

QuickCode meaning (name) for COSTDISTRIBUTION LINE TYPE lookup type NVARCSTR 80 0 0 no

4 END_DATE_ACTIVE The date when the QuickCode becomes inactive DATETIME 24 0 9 yes



7 START_DATE_ACTIVE The date when the QuickCode becomes active DATETIME 24 0 9 yes



CURRENCY

Currencies enabled for use in Oracle Applications



Nullable

1 CURRENCY_CODE PK Currency code VARCSTR 15 0 0 no

2 CURRENCY_DESC Description VARCSTR 240 0 0 yes

3 CURRENCY_NAME Currency name VARCSTR 80 0 0 yes

4 CURRENCY_PRECISION Maximum number of digits to the right of decimalpoint DECIMAL 48 1 0 yes

5 END_DATE_ACTIVE The date the currency code expires DATE 24 0 9 yes

6 EXTENDED_PRECISION Extended precision DECIMAL 48 2 0 yes

7 LOAD_DATE Date record is loaded DATE 24 0 9 yes

8 LOAD_TIME Time record is loaded VARCSTR 8 0 0 yes

9 START_DATE_ACTIVE The date when the currency code becomes active DATE 24 0 9 yes

10 STATISTICAL_FLAG If set to Y to indicate if the currency is a statisticalunit, otherwise is set to N VARCSTR 1 0 0 yes

11 SYMBOL The symbol denoting the currency VARCSTR 4 0 0 yes



CURRENT_PEOPLE

Employee and applicant current data loaded from PEOPLE dimension



Nullable

1 ACTUAL_TERMIN_DATE Actual date of termination of employment DATE 24 0 9 yes

2 ADJUSTED_SVC_DATE Previous date of hire DATE 24 0 9 yes

3 BENEFIT_GROUP_ID Benefits Group ID DECIMAL 48 15 0 yes

4 BENEFIT_GROUP_NAME Benefits Group Name VARCSTR 60 0 0 yes

5 BUSINESS_GROUP_ID Foreign key to HR_ORGANIZATION_UNITS. DECIMAL 48 15 0 yes

6 BUSINESS_GROUP_NAME Translated name of the organization VARCSTR 60 0 0 yes

7 BUYER_AUTHORIZATION_LIMIT

Maximum purchase order authorization limit for thebuyer DECIMAL 48 28 7 yes

8 BUYER_END_DATE_ACTIVE Date buyer active to DATE 24 0 9 yes

9 BUYER_FLAG Indicates whether user is a buyer VARCSTR 1 0 0 yes

10 BUYER_START_DATE_ACTIVE Date buyer active from DATE 24 0 9 yes

11 COUNTRY_OF_BIRTH Country of Birth VARCSTR 60 0 0 yes

12 CREATION_DATE Date when the record was created in the sourcesystem DATE 24 0 9 yes

13 CURRENT_APPLICANT_FLAG Y/N VARCSTR 30 0 0 yes

14 CURRENT_EMPLOYEE_FLAG Y/N VARCSTR 30 0 0 yes

15 CURRENT_EMP_OR_APL_FLAG Y/N VARCSTR 30 0 0 yes

16 DATE_OF_BIRTH Date of birth. DATE 24 0 9 yes





Nullable

17 DATE_OF_DEATH Date of death. DATE 24 0 9 yes

18 EMAIL_ADDRESS Holds actual email identifier. VARCSTR 240 0 0 yes

19 EMPLOYEE_NUMBER Number assigned to a person if they have been anemployee. VARCSTR 30 0 0 yes

20 ETHNIC_ORIGIN_CODE Developer descriptive flexfield PER_INFORMATION1 segment VARCSTR 150 0 0 yes

21 ETHNIC_ORIGIN_NAME Translated ethnic origin name (lookup type =US_ETHNIC_GROUP) VARCSTR 80 0 0 yes

22 FINAL_PROCESS_DATE Final date for all payroll processing of this person DATE 24 0 9 yes

23 FIRST_NAME First name of person. VARCSTR 20 0 0 yes

24 FULL_NAME Concatenation of last name, title, first name, middlenames and the name the person is known by. VARCSTR 240 0 0 yes

25 GENDER_CODE Legal gender code (M/F) VARCSTR 30 0 0 yes

26 GENDER_NAME Translated gender name VARCSTR 80 0 0 yes

27 INTERNAL_LOCATION Internal location. VARCSTR 30 0 0 yes

28 I_9 Developer descriptive flexfield column. VARCSTR 150 0 0 yes

29 I_9_EXPIRE_DATE Developer descriptive flexfield column. DATE 24 0 9 yes

30 LAST_NAME Last name of the person, (surname, family name). VARCSTR 40 0 0 yes

31 LEAVING_REASON_CODE Reason for termination of employment code VARCSTR 30 0 0 yes

32 LEAVING_REASON_NAME

Reason for termination of employment translatedname VARCSTR 80 0 0 yes






Nullable


35 MARITAL_STATUS_CODE Marital status. VARCSTR 30 0 0 yes

36 MARITAL_STATUS_NAME Translated marital status name VARCSTR 80 0 0 yes

37 NATIONALITY_CODE Nationality. VARCSTR 30 0 0 yes

38 NATIONALITY_NAME Nationality name (lookup type NATIONALITY) VARCSTR 80 0 0 yes

39 NATIONAL_IDENTIFIER Number by which a person is identified in a givenlegislation. VARCSTR 30 0 0 yes

40 NEW_HIRE_STATUS_CODE

New hire status code (PER_INFORMATION7 forcategory US) VARCSTR 150 0 0 yes

41 NEW_HIRE_STATUS_NAME Translated New Hire status name VARCSTR 80 0 0 yes

42 NUM_HIRES If New Hire status is INCL the value is 1, otherwise itis set to 0 DECIMAL 48 15 0 yes

43 NUM_TERMINATES If Actual Termination date is NOT NULL, the value is1; otherwise it is set to 0 DECIMAL 48 15 0 yes

44 PERSON_ID PK System generated person primary key fromPER_PEOPLE_S DECIMAL 48 10 0 no

45 PERSON_TYPE_NAME Translated user name for the person type VARCSTR 80 0 0 yes

46 PREVIOUS_LAST_NAME Previous last name of person (if applicable). VARCSTR 40 0 0 yes

47 PRIMARY_CONTACT_ID Lookup for Primary Contact ID DECIMAL 48 10 0 yes

48 REGION_OF_BIRTH State of Birth VARCSTR 60 0 0 yes

49 REGISTERED_DISABLED_FLAG

Flag indicating whether person is classified asdisabled. VARCSTR 30 0 0 yes

50 START_DATE Employment/Application Start date for the person(not the DateTrack attribute). DATE 24 0 9 yes





Nullable

51 TITLE_NAME Title e.g. Mr, Mrs, Dr. VARCSTR 30 0 0 yes

52 TOWN_OF_BIRTH City of Birth VARCSTR 60 0 0 yes

53 USES_TOBACCO_FLAG_CODE

Uses tabacco flag code. Lookup type =TOBACCO_USER_TYPE VARCSTR 30 0 0 yes

54 USES_TOBACCO_FLAG_NAME

Uses tobacco flag translated name (lookup type =TOBACCO_USER_TYPE) VARCSTR 80 0 0 yes

55 WORK_SCHEDULE Work schedule. VARCSTR 30 0 0 yes

DATE_DRIVER

Auxiliary table to store calculated datetracked composite primary key (merge from datetracked source tables to be joined)



Nullable

1 CURRENT_FLAG Y indicates record in effect on extract date VARCSTR 1 0 0 yes

2 EFF_END_DATE Date until which this record is effective. Automaticallygenerated by the Effective_Date transform DATE 24 0 9 yes

3 EFF_START_DATE PK Effective start date. DATE 24 0 9 no

4 FOREIGN_KEY_1 Foreign key 1 to a datetraked table 1 to be joined DECIMAL 48 10 0 yes




8 MERGE_KEY PK Primary key of source tables to be joined DECIMAL 48 10 0 no



DATE_DRIVER_STAGE

Auxiliary table to store calculated datetracked composite primary key (merge from datetracked source tables to be joined)



Nullable

1 EFF_START_DATE Effective start date. DATE 24 0 9 no




5 MERGE_KEY Primary key of source tables to be joined DECIMAL 48 10 0 no

DATE_HOLDER

Auxiliary table to store primary/foreign keys of datetracked source tables that need to be joined to populate datetracked dimensions



Nullable

1 EFF_END_DATE PK Effective end date DATE 24 0 9 yes

2 EFF_START_DATE PK Effective start date DATE 24 0 9 yes




6 MERGE_KEY PK Systemgenerated primary key column. DECIMAL 48 10 0 yes

7 SOURCE_TABLE Oracle Apps source table name VARCSTR 100 0 0 yes



DRAFT_INVOICE_FACT

Project Draft Invoice fact table at invoice grain containing summarized data



Nullable

1 AGREEMENT_ID The identifier of the agreement that funds the invoice. DECIMAL 48 15 0 yes

2 APPROVED_BY_PERSON_ID

The identifier of the employee that approved theinvoice DECIMAL 48 10 0 no

3 APPROVED_DATE The date on which the draft invoice is approved DATETIME 24 0 9 no

4 BILL_THROUGH_DATEThe date through which to invoice the project.Expenditure items with the expenditure item date onor before the bill through date and events withcompletion dates on or

DATETIME 24 0 9 no

5 CANCELED_FLAG Flag that indicates that the draft invoice was creditedby another draft invoice, a credit memo NVARCSTR 1 0 0 no

6 CANCEL_CREDIT_MEMO_FLAG

Flag that indicates that the draft invoice is a creditmemo, crediting or canceling another draft invoice NVARCSTR 1 0 0 no

7 CONVERTED_FLAGFlag indicating if the invoice is converted. Y denotesa converted invoice with no detail in AR as PAexpects. A value of N or null denotes anonconverted invoice. A con

NVARCSTR 1 0 0 no

8 CREATION_DATE Date when the record was created in the applicationsystem DATETIME 24 0 9 no

9 CURRENCY_CODE_FNC Project functional currency code NVARCSTR 15 0 0 yes

10 CURRENCY_CODE_FUND Funding currency code NVARCSTR 15 0 0 yes

11 CURRENCY_CODE_INV Invoice processing currency code NVARCSTR 15 0 0 yes

12 CURRENCY_CODE_PRJ Project currency code. NVARCSTR 15 0 0 yes

13 CURRENCY_CODE_TRX Transaction currency code NVARCSTR 15 0 0 yes

14 CUSTOMER_BILL_SPLIT The percentage of the total project invoice amountthat the customer is billed on the draft invoice DECIMAL 48 7 4 yes

15 DRAFT_INVOICE_NUM PK The draft invoice number to which the invoice linebelongs DECIMAL 48 15 0 no

16 DRAFT_INVOICE_NUM_CREDITED

The draft invoice number that is credited by this draftinvoice. The crediting invoice may be a credit memoor a writeoff

DECIMAL 48 15 0 yes





Nullable

17 DRAFT_INV_LINE_NUM_CREDITED

The draft invoice line number that is credited by thisinvoice line DECIMAL 48 15 0 yes

18 GL_PERIOD_NAME GL Period of the draft invoice NVARCSTR 15 0 0 no

19 INVOICE_DATE PKThe invoice date passed to Oracle Receivableswhich is used to calculate the invoice due date.Upon release of the invoice, this date is defaultedfrom the released date

DATETIME 24 0 9 no

20 INV_CURRENCY_CODE Invoice currency code for the draft invoice that istransferred to Oracle Receivables. NVARCSTR 15 0 0 no

21 INV_LINE_DESCThe invoice line description. For a line billing anevent, this description is the event description. For aline billing expenditure items, this description isformatte

NVARCSTR 240 0 0 yes

22 INV_LINE_TYPE The type of draft invoice line NVARCSTR 30 0 0 yes

23 LINE_ACCT_AMOUNT_FNC

The Functional Currency amount of that has beenaccounted in Oracle ReceivablesThis column ispopulated in the Transfer Invoice to OracleReceivables process

DECIMAL 48 28 7 yes

24 LINE_AMOUNT_INV The amount to be billed in the invoicing currencycode for the draft invoice item. DECIMAL 48 28 7 yes

25 LINE_AMOUNT_TRX The amount to be billed for the draft invoice item DECIMAL 48 22 5 yes

26 LINE_BILL_AMOUNT_FNC

Bill Amount in the project functional currency. This iscalculated by applying the conversion rules set up forproject functional currency during invoice generation.

DECIMAL 48 28 7 yes

27 LINE_BILL_AMOUNT_FUND

Bill Amount in the funding currency. This iscalculated by applying the conversion rules set up forfunding currency during invoice generation.

DECIMAL 48 28 7 yes

28 LINE_BILL_AMOUNT_PRJ

Bill Amount in the project currency. This is calculatedby applying the conversion rules set up for projectcurrency during invoice generation.

DECIMAL 48 28 7 yes

29 LINE_BILL_AMOUNT_TRX

Bill Amount in the transaction currency. This iscalculated by applying the conversion rules set up fortransaction currency during invoice generation.

DECIMAL 48 28 7 yes

30 LINE_NUM PK The sequential number that identifies and orders thedraft invoice item for a draft invoice DECIMAL 48 15 0 no








Nullable

34 ORG_STRUCTURE_ID Identifier of the default organization hierarchy usedfor reporting DECIMAL 48 15 0 yes



36 PERIOD_NAME Project Period of the draft invoice NVARCSTR 15 0 0 yes


38 PROJECT_ID PK The identifier of the project for which the invoice isgenerated DECIMAL 48 15 0 no

39 RA_INVOICE_NUMBERThe Oracle Receivables invoice number that isdetermined upon release of the draft invoice andpassed to Oracle Receivables upon transfer. Thisnumber can be userentered

NVARCSTR 20 0 0 no

40 RELEASED_BY_PERSON_ID

The identifier of the employee that released theinvoice DECIMAL 48 10 0 no

41 RELEASED_DATE The date that the draft invoice was released fortransfer DATETIME 24 0 9 no


43 START_ORG_ID Identifier of the highest organization used in defaultreporting organization hierarchy version DECIMAL 48 15 0 yes

44 TASK_IDThe identifier of the top task. This column ispopulated if: the project is funded at top task level, orfor expenditure item lines, the invoice format groupsby Top Tas

DECIMAL 48 15 0 yes

45 TRANSFERRED_DATE The date that the draft invoice was transferred to theOracle Receivables interface tables DATETIME 24 0 9 no

46 TRANSFER_STATUS_CODE

The status of the invoice as it is transferred to OracleReceivables NVARCSTR 30 0 0 yes

47 UNBILLED_CODE_COMBINATION_ID

The identifier of the GL account to which the unbilledreceivable amount is charged This column ispopulated by the Transfer Invoices to Receivablesprocess

DECIMAL 48 15 0 no

48 UNBILLED_RECEIVABLE_DR

The amount of unbilled receivables debited by thedraft invoice. This amount is determined by theTransfer Invoice program

DECIMAL 48 22 5 yes

49 UNEARNED_CODE_COMBINATION_ID

The identifier of the GL account to which theunearned revenue amount is chargedThis column ispopulated in Transfer Invoice to Receivable programfrom Release 115

DECIMAL 48 15 0 no

50 UNEARNED_REVENUE_CR

The amount of unearned revenue credited by thedraft invoice. This amount is determined by theTransfer Invoice program

DECIMAL 48 22 5 yes





Nullable

51 WRITE_OFF_FLAG Flag that indicates that a draft invoice writes offanother draft invoice NVARCSTR 1 0 0 no



DRAFT_REVENUE_FACT

Project Draft Revenue fact table at revenue grain containing summarized data



Nullable

1 ACCRUE_THROUGH_DATE

The date through which to accrue revenue for theproject. Expenditure items with item date and eventswith completion date on or before the accrue throughdate are includ

DATETIME 24 0 9 no

2 AGREEMENT_ID The identifier of the agreement that funds therevenue DECIMAL 48 15 0 yes

3 CREATION_DATE PK Date when the record was created in the applicationsystem DATETIME 24 0 9 no

4 CURRENCY_CODE_FNC Project functional currency. NVARCSTR 15 0 0 yes

5 CURRENCY_CODE_FUND Funding currency code. NVARCSTR 15 0 0 yes

6 CURRENCY_CODE_PRJ Project currency code. NVARCSTR 15 0 0 yes

7 CURRENCY_CODE_TRX Revenue processing currency. NVARCSTR 15 0 0 yes

8 CUSTOMER_BILL_SPLIT The percentage of the total project revenue that thecustomer is funding on the draft revenue DECIMAL 48 7 4 yes

9 DRAFT_REVENUE_NUM PK The sequential number that identifies the draftrevenue within a project DECIMAL 48 15 0 no

10 DRAFT_REVENUE_NUM_CREDITED

The draft revenue number that is credited by thisdraft revenue DECIMAL 48 15 0 yes

11 GL_PERIOD_NAME The GL period in which the revenue is posted. NVARCSTR 15 0 0 no

12 LINE_NUM PK The sequential number that identifies and orders thedraft revenue item for a draft revenue DECIMAL 48 15 0 no

13 LINE_REV_AMOUNT_FNC

Revenue amount in the project functional currency.This is calculated by applying the conversion rulesset up for project functional currency during invoicegeneration

DECIMAL 48 22 5 yes

14 LINE_REV_AMOUNT_FUND

Revenue amount in the funding currency. This iscalculated by applying the conversion rules set up forfunding currency during revenue generation.

DECIMAL 48 22 5 yes

15 LINE_REV_AMOUNT_PRJ

Revenue amount in the project currency. This iscalculated by applying the conversion rules set up forproject currency during revenue generation.

DECIMAL 48 22 5 yes

16 LINE_REV_AMOUNT_TRX

The revenue amount accrued for the draft revenueitem DECIMAL 48 22 5 yes





Nullable




20 ORG_STRUCTURE_ID Identifier of the default organization hierarchy usedfor reporting DECIMAL 48 15 0 no



22 PERIOD_NAME The project period in which the revenue is posted. NVARCSTR 15 0 0 yes


24 PROJECT_ID PK The identifier of the project for which the revenue isgenerated DECIMAL 48 15 0 no

25 REALIZED_GAINS_AMOUNT The amount realized gains debit by the draft revenue DECIMAL 48 28 7 yes

26 REALIZED_GAINS_CC_ID

The identifier of the GL account to which the realizedgains amount of this draft revenue is charged. Thiswill be populated by Interface revenue to GL process.

DECIMAL 48 15 0 no

27 REALIZED_LOSSES_AMOUNT

The amount realized losses credited by the draftrevenue DECIMAL 48 28 7 yes

28 REALIZED_LOSSES_CC_ID

The identifier of the GL account to which the realizedlosses amount of this draft revenue is charged. Thiswill be populated by Interface revenue to GL process.

DECIMAL 48 15 0 no

29 RELEASED_DATE The date on which the draft revenue is released DATETIME 24 0 9 no

30 REV_CATEGORY_CODE The revenue category of the expenditure itemsgrouped into the revenue line NVARCSTR 30 0 0 yes

31 REV_SOURCE_CODE The source from which the revenue for the revenueline is generated NVARCSTR 30 0 0 yes

32 SET_OF_BOOKS_ID The identifier of the General Ledger set of booksused by Oracle Projects DECIMAL 48 15 0 no

33 START_ORG_ID Identifier of the highest organization used in defaultreporting organization hierarchy version DECIMAL 48 15 0 yes





Nullable

34 TASK_IDThe identifier of the task of the revenue line. For aline that accrues event revenue, this is the eventtask_id. For a line that accrues expenditure itemrevenue, this i

DECIMAL 48 15 0 yes

35 TRANSFERRED_DATE The date that the draft revenue was transferred toGeneral Ledger DATETIME 24 0 9 no


The status of the revenue as it is transferred toGeneral Ledger NVARCSTR 30 0 0 yes

37 UNBILLED_CODE_COMBINATION_ID

The identifier of the gl account to which the unbilledreceivables amount of this draft revenue is charged DECIMAL 48 15 0 no

38 UNBILLED_RECEIVABLE_DR

The amount of unbilled receivables debit by the draftrevenue DECIMAL 48 22 5 yes

39 UNEARNED_CODE_COMBINATION_ID

The identifier of the gl account to which the unearnedrevenue amount of this draft revenue is charged DECIMAL 48 15 0 no

40 UNEARNED_REVENUE_CR

The amount of unearned revenue credited by thisdraft revenue DECIMAL 48 22 5 yes



EVENT

Project Event reference dimension table



Nullable

1 BILLED_FLAG Indicates if a particular event has been billedcompletely (Y) or not (N). NVARCSTR 1 0 0 no

2 BILL_AMOUNT The amount to be billed for the event on an invoiceupon the events completion date DECIMAL 48 22 5 yes

3 BILL_HOLD_FLAG Flag that indicates that the event is held frominvoicing NVARCSTR 1 0 0 no

4 BILL_TRANS_BILL_AMOUNT Bill amount in the event transaction. DECIMAL 48 28 7 yes

5 BILL_TRANS_CURRENCY_CODE Transaction currency code of the event. NVARCSTR 15 0 0 no

6 BILL_TRANS_REV_AMOUNT Revenue Amount in the Event Transaction. DECIMAL 48 28 7 yes

7 COMPLETION_DATEThe date on which the event is complete and on orafter which the event is processed for revenueaccrual and/or invoicing

DATETIME 24 0 9 no


9 DESCRIPTIONThe free text description of the event. For billingevents, the description is displayed as the invoiceline description.

NVARCSTR 240 0 0 no

10 EVENT_ID PK Primary key for table. DECIMAL 48 28 7 no

11 EVENT_NUM The sequential number that identifies the event. DECIMAL 48 15 0 no

12 EVENT_TYPE_ID PK Unique identifier for the event type DECIMAL 48 15 0 no

13 INVPROC_CURRENCY_CODE Invoice Processing Currency. NVARCSTR 15 0 0 no



16 ORG_IDThe unique identifier of the organization for the event.For example, this may be used to credit revenue todifferent organization.

DECIMAL 48 15 0 no





Nullable

17 ORG_NAME Translated name of the organization NVARCSTR 60 0 0 yes

18 PROJECT_BILL_AMOUNT

Bill amount in Project Currency. This is calculated byapplying the Project Currency setup conversion rulesto the bill transaction base bill amount during invoicegene

DECIMAL 48 28 7 yes

19 PROJECT_CURRENCY_CODE Project currency code. NVARCSTR 15 0 0 no

20 PROJECT_ID PK The identifier of the project to which event isassigned. DECIMAL 48 15 0 no

21 PROJECT_NAME Userdefined name that uniquely identifies the project NVARCSTR 30 0 0 yes

22 PROJECT_NUMThe project number that uniquely identifies theproject. The project number can be userentered orsystemgenerated as defined in the implementationoptions

NVARCSTR 25 0 0 yes

23 PROJECT_REVENUE_AMOUNT

Revenue Amount in Project Currency. This iscalculated by applying the Project Currency setupconversion rules to the bill transaction base revenueamount during reven

DECIMAL 48 28 7 yes

24 PROJECT_STATUS_CODE The status of the project. NVARCSTR 30 0 0 yes

25 PROJECT_TYPE The project type that classifies the project anddefaults project information upon project entry NVARCSTR 20 0 0 yes

26 PROJFUNC_BILL_AMOUNT

Bill amount in the project functional currency. This iscalculated by applying the Project functionalcurrency setup conversion rules to the billtransaction base bill

DECIMAL 48 28 7 yes

27 PROJFUNC_CURRENCY_CODE Project functional currency. NVARCSTR 15 0 0 no

28 PROJFUNC_REVENUE_AMOUNT

Revenue amount in the project functional currency.This is calculated by applying the project functionalcurrency setup conversion rules to the bill ransactionbase re

DECIMAL 48 28 7 yes

29 PROJ_CLASS_CODE Indicates the class of project type NVARCSTR 30 0 0 yes

30 REVENUE_AMOUNT The amount of revenue to accrue for the event uponthe events completion date DECIMAL 48 22 5 yes

31 REVENUE_DISTRIBUTED_FLAG

Flag that indicates whether the events revenue hasbeen distributed. (An event is either distributed ornot. It cannot be partially accrued.)

NVARCSTR 1 0 0 no

32 REVPROC_CURRENCY_CODE Revenue Processing Currency. NVARCSTR 15 0 0 no

33 TASK_ID PK The identifier of the top level task to which the eventis assigned DECIMAL 48 15 0 no





Nullable

34 TASK_NAME Userdefined short name of the task NVARCSTR 20 0 0 yes

35 TASK_NUMBERUserdefined number that uniquely identifies the taskwithin a project. It is recommended to number tasksbased on the wbs since that is how tasks are orderedin some re

NVARCSTR 25 0 0 yes



EVENT_DIST_FACT

Project Event Distribution fact table at detailed data at grain of event distribution line



Nullable

1 AMOUNTThe Revenue amount to be charged to the GLaccount for the event on a draft revenue in therevenue processing currency.

DECIMAL 48 22 5 yes

2 BILL_TRANS_AMOUNT The billing amount of the item in the bill transactioncurrency. DECIMAL 48 28 7 yes

3 BILL_TRANS_CURRENCY_CODE

Bill transaction currency code for the expenditureitem. NVARCSTR 15 0 0 no

4 CODE_COMBINATION_ID The identifier of the gl account to which the revenueis charged DECIMAL 48 15 0 no


6 DRAFT_INVOICE_ITEM_LINE_NUM

The draft invoice item line number on which the eventdistribution line is invoiced DECIMAL 48 15 0 no

7 DRAFT_INVOICE_NUM The draft invoice number on which the eventdistribution line is invoiced DECIMAL 48 15 0 no

8 DRAFT_REVENUE_ITEM_LINE_NUM

The draft revenue item line number under which therevenue distribution line is generated DECIMAL 48 15 0 no

9 DRAFT_REVENUE_NUM The draft revenue number for which the revenuedistribution line is generated DECIMAL 48 15 0 no

10 EVENT_ID Primary key for table. DECIMAL 48 28 7 no

11 EVENT_NUM PK The event number of the event that is revenuedistributed by the distribution line DECIMAL 48 15 0 no

12 EVENT_TYPE_ID The event type ID that classifies the event DECIMAL 48 15 0 yes

13 FUNDING_BILL_AMOUNT Bill amount in funding currency. DECIMAL 48 28 7 yes

14 FUNDING_CURRENCY_CODE Funding currency code. NVARCSTR 15 0 0 no

15 FUNDING_REVENUE_AMOUNT Revenue amount in the funding currency. DECIMAL 48 28 7 yes

16 GL_PERIOD_NAME System generated accounting period NVARCSTR 15 0 0 yes





Nullable

17 INVPROC_CURRENCY_CODE Invoice processing currency. NVARCSTR 15 0 0 no

18 LINE_NUM PK The sequential number that identifies the revenuedistribution line for an event DECIMAL 48 15 0 no








24 PERIOD_SET_NAME Calendar name.. NVARCSTR 15 0 0 yes


Bill amount in the project currency. This is calculatedby applying the conversion rules set up for projectcurrency during invoice generation.

DECIMAL 48 28 7 yes


27 PROJECT_ID PKThe identifier of the project for which the revenuedistribution line is generated. This project is theproject for which the event is entered

DECIMAL 48 15 0 no

28 PROJECT_REVENUE_AMOUNT Revenue Amount in the project functional currency. DECIMAL 48 28 7 yes



DECIMAL 48 28 7 yes

30 PROJFUNC_CURRENCY_CODE Project functional currency code. NVARCSTR 15 0 0 no

31 PROJFUNC_REVENUE_AMOUNT Revenue amount in the project functional DECIMAL 48 28 7 yes

32 RETAINED_AMOUNT Retained amount. This amount is in the invoiceprocessing currency DECIMAL 48 28 7 yes

33 REVPROC_CURRENCY_CODE Base bill amount in the bill transaction currency. NVARCSTR 15 0 0 no





Nullable




36 TASK_ID PK The identifier of the task that the event is assigned to DECIMAL 48 15 0 no

EVENT_TYPE

Project Event Type dimension



Nullable

1 DESCRIPTION Explanation of event type VARCSTR 250 0 0 yes

2 EVENT_TYPE Implementationdefined name that uniquely identifiesthe event type VARCSTR 30 0 0 yes

3 EVENT_TYPE_CLASSIFICATION

The classification of the event type to drive systemprocessing of events of the event type VARCSTR 30 0 0 yes

4 EVENT_TYPE_ID PK Unique identifier for the event type DECIMAL 48 15 0 no



7 REVENUE_CATEGORY The revenue category to which event type belongs. VARCSTR 30 0 0 yes




Project Expenditure Cost fact table detailed data at grain of expenditure distribution line



Nullable

1 ACCT_BURDENED_CHANGE

Change in burdened cost since last time distributionlines were created. Stored in functional currency. DECIMAL 48 28 7 yes

2 ACCT_BURDENED_COST Burdened cost in functional currency DECIMAL 48 28 7 yes

3 ACCT_CURRENCY_CODE Functional Currency Code NVARCSTR 15 0 0 yes

4 ACCT_RAW_COSTThe amount in functional currency to be charged tothe gl account for the expenditure item The amountis stored as a debit, so the burden credit amountsand adjustment a

DECIMAL 48 28 7 yes

5 AMOUNT Amount in project currency Derrived by convertingraw cost in transaction currency to project currency DECIMAL 48 22 5 yes

6 BATCH_NAMEThe reference to a batch of lines transferred together.For expense reports, this is an expenditure batch.For cost transferred to GL, this is a concatenation ofliabilit

VARCSTR 30 0 0 yes

7 BILLABLE_FLAGFlag that indicates whether the cost amount isbillable. The flag is set from the expenditure itembillable flag when the distribution line is created andis used for de

VARCSTR 1 0 0 yes

8 BURDENED_COST Amount of the burdened cost in project currency DECIMAL 48 22 5 yes

9 CODE_COMBINATION_IDCalculated Code Combination ID. If it is 'C' or 'D' linetype, then it is one of DR_CODE_COMBINATION_IDor CR_CODE_COMBINATION_ID (exclusive). If it isany other, we pick

DECIMAL 48 15 0 yes

10 COST_DIST_LINE_TYPE The type of the cost distribution line VARCSTR 1 0 0 yes

11 CREATION_DATE Standard Who Column DATETIME 24 0 9 yes

12 CR_CODE_COMBINATION_ID The identifier of the GL liability account DECIMAL 48 15 0 yes

13 DENOM_BURDENED_CHANGE

Change in burdened cost since last time distributionlines were created. Stored in transaction currency. DECIMAL 48 28 7 yes

14 DENOM_BURDENED_COST

The amount of the burdened cost in transactioncurrency It is only populated for raw cost distributionlines

DECIMAL 48 28 7 yes

15 DENOM_CURRENCY_CODE Transaction Currency code of the transaction NVARCSTR 15 0 0 yes

16 DENOM_RAW_COST The raw cost in transaction currency DECIMAL 48 28 7 yes





Nullable

17 DR_CODE_COMBINATION_ID

The identifier of the GL account to which the cost ischarged DECIMAL 48 15 0 yes

18 ENCUMBRANCE_AMOUNT

The amount encumbered when the encumbranceliquidation is created. DECIMAL 48 28 7 yes

19 ENCUMBRANCE_BATCH_NAME

The batch name used which creating encumbranceliquidation. VARCSTR 240 0 0 yes

20 ENCUMBRANCE_TYPE_ID

Commitment encumbrance type identifier usedduring processing. DECIMAL 48 15 0 yes

21 EXPENDITURE_ITEM_ID PK The identifier of the expenditure item that is revenuedistributed by the distribution line DECIMAL 48 15 0 no

22 GL_DATEDate used to determine the correct general ledgeraccounting period in the provider operating unit. TheGL date is determined by the Distribution programsfrom the open

DATETIME 24 0 9 yes

23 GL_PERIOD_NAME The GL period in which the transaction is posted. VARCSTR 15 0 0 yes

24 LINE_NUM PK The sequential number that identifies the revenuedistribution line for the expenditure item DECIMAL 48 15 0 no





28 ORG_ID Operating unit identifier for multiorganizationinstallations DECIMAL 48 15 0 yes



30 PARENT_LINE_NUM Line Number for the raw cost distribution line. Validfor I line types only. DECIMAL 48 15 0 yes

31 PA_DATEDate used to determine the correct projectaccounting period in the provider operating unit. ThePA date is determined by the Distribution programsfrom the open or futur

DATETIME 24 0 9 yes

32 PERIOD_NAME The PA period in which the transaction is posted. VARCSTR 15 0 0 yes






Nullable

34 PROJECT_BURDENED_CHANGE

Change in burdened cost since last time thedistribution lines were created. Stored in projectcurrency.

DECIMAL 48 28 7 yes

35 PROJECT_BURDENED_COST Burdened cost in project currency. DECIMAL 48 28 7 yes

36 PROJECT_CURRENCY_CODE Project currency code of the transaction NVARCSTR 15 0 0 yes

37 PROJECT_ID The identifier of the project for which the invoice isgenerated DECIMAL 48 15 0 yes

38 PROJECT_RAW_COST Raw cost in project currency. DECIMAL 48 28 7 yes

39 PROJFUNC_BURDENED_CHANGE

Change in burdened cost since last time distributionlines were created. Stored in project functionalcurrency.

DECIMAL 48 28 7 yes

40 PROJFUNC_CURRENCY_CODE Project functional currency code. NVARCSTR 15 0 0 yes

41 QUANTITYThe number of units that are costed in the distributionline cost. The quantity is set from the expenditureitem quantity when the distribution line is created andis use

DECIMAL 48 22 5 yes

42 RECVR_GL_DATEDate used to determine the correct general ledgertaccounting period in the receiver operating unit. TheGL date is determined by the Distribution programsfrom the open

DATETIME 24 0 9 yes

43 RECVR_PA_DATEDate used to determine the correct projectaccounting period in the receiver operating unit. ThePA date is determined by the Distribution programsfrom the open or futur

DATETIME 24 0 9 yes

44 RECVR_PA_PERIOD_NAME

The PA period in which the transaction is posted onthe receiving ledger. VARCSTR 15 0 0 yes




47 SYSTEM_REFERENCE1The reference to the record in another applicationwhen the line is transferred. For supplier invoices,this holds AP_INVOICES.VENDOR_ID. This is notused for other adj

NVARCSTR 30 0 0 yes

48 SYSTEM_REFERENCE2The reference to the record in another applicationwhen the line is transferred For supplier invoices andexpense reports, this holds theAP_INVOICESINVOICE_ID Not used

NVARCSTR 30 0 0 yes

49 SYSTEM_REFERENCE3The reference to the record in another applicationwhen the line related to supplier invoice or expensereport is transferred. It holdsAP_INVOICE_DISTRIBUTIONS.DISTRIBUT

NVARCSTR 30 0 0 yes

50 SYSTEM_REFERENCE4The reference to the record in another applicationwhen the line related to supplier invoice or expensereport is transferred. It holdsAP_INVOICE_PAYMENTS_ALL. INVO

NVARCSTR 30 0 0 yes





Nullable

51 TASK_ID The identifier of the task to which the expenditureitem is charged DECIMAL 48 15 0 yes


The status of the distribution line as the costinformation is transferred to another application NVARCSTR 1 0 0 yes

53 WORK_TYPE_ID Identifier for a work type assigned to the transaction. DECIMAL 48 15 0 yes



EXPENDITURE_FACT

Project Expenditure fact table containing summarized expenditure data



Nullable

1 ACCRUED_REVENUEThe total amount of revenue that the item accrued.This amount should always equal the sum of therevenue amount in the revenue distribution lines.This amount is diffe

DECIMAL 48 22 5 yes

2 ACCT_BURDENED_COST Burdened Cost in Functional Currency DECIMAL 48 28 7 yes

3 ACCT_CURRENCY_CODE Account currency code of the transaction NVARCSTR 15 0 0 no

4 ACCT_RAW_COST Raw cost in Functional Currency DECIMAL 48 28 7 yes

5 ADJUSTED_REVENUEThe discounted revenue amount of the item based onthe bill rate schedule discount. Adjusted revenue =(raw revenue * (100schedule discount)/100 )

DECIMAL 48 22 5 yes

6 BILLABLE_FLAGFlag that indicates if the item can accrue revenue.Upon entry, this flag is defaulted from the task towhich the item is charged, or is based on transactioncontrols.

NVARCSTR 1 0 0 no

7 BILL_AMOUNTThe amount to be billed for the item. This mustalways equal the sum of the bill amount on therevenue distribution lines. This amount may differfrom the revenue amount

DECIMAL 48 22 5 yes

8 BILL_HOLD_FLAG Flag that indicates if the item is held from invoicing.Upon entry, this flag is defaulted to N. NVARCSTR 1 0 0 no

9 BILL_RATEThe bill rate for the expenditure item. This column isnot populated if (1) a markup percentage or labormultiplier was used to calculate T and M revenue or(2) if reven

DECIMAL 48 22 5 yes

10 BILL_TRANS_ADJUSTED_REVENUE

The adjusted revenue of the item in bill transactioncurrency. For Work revenue accrual or invoicingmethod adjusted revenue = (quantity * bill rate) or(project cur

DECIMAL 48 28 7 yes

11 BILL_TRANS_BILL_AMOUNT Bill amount in bill transaction currency. DECIMAL 48 28 7 yes


Bill transaction currency code for the expenditureitem for accrued revenue and bill amounts NVARCSTR 15 0 0 no

13 BILL_TRANS_RAW_REVENUE

The raw revenue of the item in bill transactioncurrency DECIMAL 48 28 7 yes

14 BURDEN_COST The burden cost in project currency DECIMAL 48 22 5 yes

15 BURDEN_COST_RATE The burdened cost rate of the item. Burdened costrate = (burden cost / quantity ). DECIMAL 48 22 5 yes

16 COST_DISTRIBUTED_FLAG

Flag that indicates whether the item has been costdistributed. When N the item is marked for costdistribution. When the item is cost distributed, theflag is set to Y

NVARCSTR 1 0 0 no





Nullable

17 CREATION_DATE Date the expenditure item was created DATETIME 24 0 9 no

18 DENOM_BURDENED_COST

Total burdened cost of the expenditure item intransaction currency Burdened cost = (raw cost * (1+ burden cost multiplier)) This must equal the sum ofthe items burde

DECIMAL 48 28 7 yes

19 DENOM_CURRENCY_CODE Transaction Currency code of the transaction NVARCSTR 15 0 0 no

20 DENOM_RAW_COSTThe total raw cost of the expenditure item intransaction currency Raw cost = (quantity * costrate) This value should always equal the sum of theitems raw cost distri

DECIMAL 48 28 7 yes

21 ENTERED_BY_PERSON_ID

The identifier of the person who entered theexpenditure. This value is not populated for supplierinvoice expenditures

DECIMAL 48 10 0 no

22 EXPENDITURE_CLASS The classification of the expenditure, indicating thetype of items grouped into it NVARCSTR 80 0 0 no

23 EXPENDITURE_COMMENT

Expenditure Item comment; limited to the first line upto 240 characters. NVARCSTR 240 0 0 yes

24 EXPENDITURE_ENDING_DATE

The last day of the expenditure week period. Allexpenditure items for the expenditure must be on orbefore this expenditure ending date. All timecarditems must be wit

DATETIME 24 0 9 no

25 EXPENDITURE_GROUP_CODE

The expenditure group to which expenditure belongs.This is only applicable for preapprovedexpenditures. This column is blank for onlineexpenditures

NVARCSTR 240 0 0 no

26 EXPENDITURE_ID The systemgenerated number that uniquelyidentifies the expenditure DECIMAL 48 15 0 no

27 EXPENDITURE_ITEM_DATE PK The date on which the work occurred DATETIME 24 0 9 no

28 EXPENDITURE_ITEM_ID PK The systemgenerated number that uniquelyidentifies the expenditure item DECIMAL 48 15 0 no

29 EXPENDITURE_STATUS_CODE

The status of the expenditure as it is entered andapproved NVARCSTR 30 0 0 no

30 EXPENDITURE_TYPE_ID PK The expenditure type that classifies the type of workperformed DECIMAL 48 15 0 no

31 FORECAST_REVENUEThe forecast revenue amount of a labor item basedon T and M bill rates and markups and labormultipliers. This column is populated by theCompute Forecast Revenue proce

DECIMAL 48 22 5 yes


33 INCURRED_BY_ORG_IDThe identifier of the organization that incurred thecharges. Column is populated for all charges exceptsupplier invoices, where the organization is held atthe expend

DECIMAL 48 15 0 no





Nullable

34 INCURRED_BY_PERSON_ID PK

The identifier of the employee who incurred thecharges. This column is always populated for laborand expense report charges and is not populated forsupplier invoices.

DECIMAL 48 10 0 no

35 INVPROC_CURRENCY_CODE Invoice Processing Currency NVARCSTR 15 0 0 no

36 JOB_ID PKThe identifier of the job of an employee as of theexpenditure item date. Required for all items incurredby an employee. This may be used in the mapping ofthe transacti

DECIMAL 48 15 0 no



39 NON_LABOR_RESOURCE

The nonlabor resource utilized as the work wasperformed. This column is only populated for usageitems

NVARCSTR 20 0 0 no


The identifier of the organization that owns thenonlabor resource that was utilized as the work wasperformed. This column is only populated for usageitems

DECIMAL 48 15 0 no






44 OVERRIDE_TO_ORG_IDThe identifier of the organization that the cost andrevenue for this item are charged to by a costdistribution override entered for the project. Forsupplier invoices,

DECIMAL 48 15 0 no


46 POSTED_ACCT_BURDENED_COST

Accounted burden amount in expenditure functionalcurrency. DECIMAL 48 28 7 yes

47 POSTED_DENOM_BURDENED_COST Accounted burden amount in transaction currency. DECIMAL 48 28 7 yes

48 POSTED_PROJECT_BURDENED_COST Accounted burden amount in project currency. DECIMAL 48 28 7 yes

49 POSTED_PROJFUNC_BURDENED_COST

Accounted burden amount in project functionalcurrency. DECIMAL 48 28 7 yes

50 PROJECT_BILL_AMOUNT Bill Amount in Project DECIMAL 48 28 7 yes





Nullable

51 PROJECT_BURDENED_COST Burdened cost in project currency. DECIMAL 48 28 7 yes

52 PROJECT_CURRENCY_CODE Project Currency Code of the Transaction NVARCSTR 15 0 0 no

53 PROJECT_ID PK The project_id of the event that the expenditure itemis FIFO marked by DECIMAL 48 15 0 no

54 PROJECT_RAW_COST Raw cost in project currency. DECIMAL 48 28 7 yes

55 PROJECT_RAW_REVENUE Revenue Amount in Project DECIMAL 48 28 7 yes

56 PROJFUNC_BILL_AMOUNT Bill Amount in Project Functional DECIMAL 48 28 7 yes


58 PROJFUNC_RAW_REVENUE Revenue Amount in Project Functional DECIMAL 48 28 7 yes

59 QUANTITY The number of units of the work performed DECIMAL 48 22 5 yes

60 RAW_COST Raw cost in project Currency DECIMAL 48 22 5 yes

61 RAW_COST_RATE The raw cost rate used to cost the item DECIMAL 48 22 5 yes

62 RAW_REVENUEThe potential revenue of the item. With T and Mrevenue accrual, raw revenue = (quantity * bill rate)or (raw cost * (markup/100) or (raw cost * labormultiplier). With C

DECIMAL 48 22 5 yes

63 RECEIPT_CURRENCY_AMOUNT Receipt currency amount of the transaction DECIMAL 48 28 7 yes

64 RECEIPT_CURRENCY_CODE Receipt currency code of the transaction NVARCSTR 15 0 0 no

65 REVENUE_DISTRIBUTED_FLAG

Flag that indicates whether the item is revenuedistributed. Upon entry, this flag is set to N. Whenthe item is revenue distributed, the flag is set to Y orP

NVARCSTR 1 0 0 no

66 REVPROC_CURRENCY_CODE Revenue Processing Currency Code NVARCSTR 15 0 0 no






Nullable



69 TASK_ID PK The identifier of the task to which the expenditureitem is charged DECIMAL 48 15 0 no

70 VENDOR_ID Identifier of the supplier DECIMAL 48 28 7 no

EXPENDITURE_GROUP

Project Expenditure Group dimension



Nullable

1 EXPENDITURE_DESCRIPTION

The description of the expenditure group. Upon entryof the expenditure group, the description is defaultedto the type of expenditures entered (Timecards,Expense Repor

VARCSTR 250 0 0 yes

2 EXPENDITURE_ENDING_DATE The last day of the expenditure week period. DATE 24 0 9 yes

3 EXPENDITURE_GROUP_CODE PK The userdefined name that uniquely identifies the

expenditure group VARCSTR 240 0 0 no

4 EXPENDITURE_GROUP_STATUS

The status of the expenditure group as it is entered,approved, and released for costing VARCSTR 30 0 0 yes



7 ORG_ID PK Operating unit identifier for multiorganizationinstallations DECIMAL 48 15 0 no




Project Expenditure Revenue fact table at detailed data at grain of expenditure distribution line



Nullable

1 ADDITIONAL_REVENUE_FLAG

Flag that indicates if the distribution line is addingadditional revenue for an item so that the item willaccrue its full potential revenue. This distribution lineis u

NVARCSTR 1 0 0 no

2 AMOUNTThe Revenue amount of the expenditure item to becharged to the GL account in the revenue processingcurrency. The amount is stored as debit, so the lenttransaction amou

DECIMAL 48 22 5 yes

3 BATCH_NAMEThe reference to the GL je line in which the revenuewas included when posted to GL. This value is aconcatenation of ccid, draft revenue gl date, andtransfer request id

NVARCSTR 30 0 0 no

4 BILL_AMOUNT The amount to be billed for the distribution line ininvoice processing currency. DECIMAL 48 22 5 yes

5 BILL_TRANS_AMOUNT The billing amount of the item in the bill transactioncurrency. DECIMAL 48 28 7 yes

6 BILL_TRANS_BILL_AMOUNT Base bill amount in the bill transaction currency. DECIMAL 48 28 7 yes


Bill transaction currency code for the expenditureitem. NVARCSTR 15 0 0 no

8 CODE_COMBINATION_ID The identifier of the gl account to which the revenueis charged DECIMAL 48 15 0 no


10 DRAFT_INVOICE_ITEM_LINE_NUM

The sequential number that identifies and orders thedraft invoice item for a draft invoice DECIMAL 48 15 0 no

11 DRAFT_INVOICE_NUM The draft invoice number to which the invoice linebelongs DECIMAL 48 15 0 no

12 DRAFT_REVENUE_ITEM_LINE_NUM

The draft revenue item line number under which therevenue distribution line is generated DECIMAL 48 15 0 no

13 DRAFT_REVENUE_NUM The draft revenue number for which the revenuedistribution line is generated DECIMAL 48 15 0 no

14 EXPENDITURE_ITEM_ID PK The identifier of the expenditure item that is revenuedistributed by the distribution line DECIMAL 48 15 0 no

15 FUNDING_BILL_AMOUNT Bill amount in funding currency. DECIMAL 48 28 7 yes

16 FUNDING_CURRENCY_CODE Funding currency code. NVARCSTR 15 0 0 no





Nullable

17 FUNDING_REVENUE_AMOUNT Revenue amount in the funding currency DECIMAL 48 28 7 yes


19 INVPROC_CURRENCY_CODE Invoice processing currency. NVARCSTR 15 0 0 no

20 LINE_NUM PK The sequential number that identifies the revenuedistribution line for the expenditure item DECIMAL 48 15 0 no










Bill amount in the project currency. This is calculatedby applying the conversion rules set up for projectcurrency during invoice generation

DECIMAL 48 28 7 yes


29 PROJECT_ID PK The identifier of the project for which the invoice isgenerated DECIMAL 48 15 0 no

30 PROJECT_REVENUE_AMOUNT Revenue Amount in the project currency. DECIMAL 48 28 7 yes



DECIMAL 48 28 7 yes


33 PROJFUNC_REVENUE_AMOUNT Revenue amount in the project functional currency. DECIMAL 48 28 7 yes





Nullable

34 RAW_COST raw_cost column will have the value of burden_costfor BURDEN TRANSACTIONS DECIMAL 48 22 5 yes

35 RETAINED_AMOUNT Retained amount. This amount is in the invoiceprocessing currency. DECIMAL 48 28 7 yes

36 REVPROC_CURRENCY_CODE Revenue processing currency code NVARCSTR 15 0 0 no




39 TASK_ID PK The identifier of the task to which the expenditureitem is charged DECIMAL 48 15 0 no

EXPENDITURE_TYPE

Project Expenditure Type dimension



Nullable

1 DESCRIPTION The description of the expenditure type VARCSTR 250 0 0 yes

2 EXPENDITURE_CATEGORY

The expenditure category that classifies theexpenditure type into a cost group VARCSTR 30 0 0 yes

3 EXPENDITURE_TYPE The expenditure for which the alias is created VARCSTR 30 0 0 yes

4 EXPENDITURE_TYPE_ID PK Unique Identifier for the Expenditure Types DECIMAL 48 15 0 no



7 REVENUE_CATEGORY The revenue category that classifies the expendituretype into a revenue group VARCSTR 30 0 0 yes

8 UNIT_OF_MEASURE The unit by which to measure amounts entered forthe expenditure type VARCSTR 30 0 0 yes



FLEX_VALUE_CHILD_TEMPTemporary table to stage APPS.FND_FLEX_VALUE_CHILDREN_V. The staging removes constraint on USERNV('LANG') used by OracleApps views



Nullable

1 DESCRIPTION Child value description VARCSTR 240 0 0 yes

2 FLEX_VALUE Concatenated fields of composite PK for the childvalue VARCSTR 150 0 0 yes

3 FLEX_VALUE_SET_ID Flexfield value set identifier DECIMAL 48 10 0 yes

4 PARENT_FLEX_VALUE Concatenated fields of composite PK for the parentvalue VARCSTR 60 0 0 yes

5 PAR_SEGMENT_DESC Parent value translated description VARCSTR 240 0 0 yes

6 SUMMARY_FLAG Flag to indicate if the value is a parent value withchild values VARCSTR 1 0 0 yes



FLEX_VALUE_TEMPTemporary table to stage source data from APPLSYS.FND_FLEX_VALUES. Used to populate staging hierarchy tableCOA_SEG_HIER_STAGE



Nullable

1 ACCOUNT_TYPE_CODE Account Type code VARCSTR 1 0 0 yes

2 APPLICATION_COLUMN_NAME Flexfield column name VARCSTR 30 0 0 yes

3 ID_FLEX_NUMBER PK Key flexfield structure number DECIMAL 48 15 0 no



6 PARENT_SEG_VALUE PK Independent value that is depended upon by thedependent segment value VARCSTR 60 0 0 no

7 SEGMENT_DESC Segment value description VARCSTR 240 0 0 yes


9 SEGMENT_VALUE PK Flexfield segment value VARCSTR 150 0 0 no

10 SEGMENT_VALUE_SET_ID PK Flexfield value set identifier DECIMAL 48 10 0 no



JOB

Jobs defined per Business Group



Nullable

1 ATTRIBUTE1 Descriptive Flexfield segment column VARCSTR 150 0 0 yes




















Nullable





21 ATTRIBUTE_CATEGORY Descriptive Flexfield structure defining column VARCSTR 30 0 0 yes



24 CREATION_DATE Date when the record was created in the applicationsystem. DATE 24 0 9 yes

25 DATE_FROM Date from which an employee or applicant may beassigned to this job. DATE 24 0 9 yes

26 DATE_TO Date after which employees and applicants may nolonger be assigned to this job. DATE 24 0 9 yes

27 EEOG_NAME Job Information 1 for CA information category VARCSTR 150 0 0 yes

28 EEO_CODE Job Information 1 for US information category VARCSTR 150 0 0 yes

29 FLEX_STRUCTURE_NAME VARCSTR 30 0 0 yes

30 FLSA_CODE Job Information 3 for US information category VARCSTR 150 0 0 yes

31 JOB_CONCAT_NAME Job name, concatenated from the keyflex structure. VARCSTR 240 0 0 yes

32 JOB_GROUP_NAME Group Internal name VARCSTR 30 0 0 yes

33 JOB_ID PK Systemgenerated primary key column. DECIMAL 48 15 0 no





Nullable

34 JOB_SEGMENT1 Key flexfield segment column. VARCSTR 60 0 0 yes





















Nullable




54 LINE_OF_PROGRESSION

Job Information 5 for US and CA informationcategory VARCSTR 150 0 0 yes



57 OVERTIME_EXEMPT Job Information 3 for CA information category VARCSTR 150 0 0 yes

58 SALARY_CODE Job Information 6 for US and CA informationcategory VARCSTR 150 0 0 yes

LOOKUP_INDEXES

Auxiliary table for stored procedures to store information about indexes



Nullable

1 ADDITIONAL_TEXT Comments VARCSTR 64 0 0 yes

2 COLUMN_NAME1 First column name which is a member of the index VARCSTR 64 0 0 yes

3 COLUMN_NAME2 Second column name which is a member of theindex VARCSTR 64 0 0 yes

4 COLUMN_NAME3 Thrid column name which is a member of the index VARCSTR 64 0 0 yes

5 INDEX_NAME Index name VARCSTR 64 0 0 yes

6 TABLE_NAME Table name index applicable to VARCSTR 64 0 0 yes



ORGANIZATION

Organizational Units in Oracle Applications



Nullable

1 ADDRESS1 Address line 1 VARCSTR 60 0 0 yes



4 BUSINESS_GROUP_ID Business Group (Parent organization) ID DECIMAL 48 15 0 yes

5 BUSINESS_GRP_NAME Business Group (Parent organization) name VARCSTR 60 0 0 yes

6 CITY City (town) name VARCSTR 30 0 0 yes

7 COUNTRY Country name VARCSTR 60 0 0 yes

8 DEFAULT_CURR_CODE Default business group currency code VARCSTR 150 0 0 yes

9 FUNC_CURRENCY_CODE

Currency set by the set of books assigned to thebusiness unit VARCSTR 15 0 0 yes

10 INTERNAL_FLAG If set to Y, organization is Internal, otherwise it isexternal VARCSTR 1 0 0 yes

11 LOAD_DATE Date record is loaded DATE 24 0 9 yes

12 LOAD_TIME Time record is loaded VARCSTR 8 0 0 yes

13 LOCATION_CODE Primary location code for the organization VARCSTR 20 0 0 yes

14 LOCATION_DESC Location desctription in selected language VARCSTR 50 0 0 yes

15 ORGANIZATION_CODE Organization code VARCSTR 3 0 0 yes

16 ORG_ID PK Systemgenerated primary key column. DECIMAL 48 15 0 no





Nullable

17 ORG_NAME Name of the organization. VARCSTR 60 0 0 yes

18 ORG_TYPE_DESC Userdefined organization types, for example Region,Division, Department. VARCSTR 80 0 0 yes

19 POSTAL_CODE Postal (ZIP) code VARCSTR 30 0 0 yes

20 REGION_1 Geographical region (for example state), child ofCountry VARCSTR 70 0 0 yes

21 REGION_2 Geographic region (for example, county), child ofRegion 1 VARCSTR 70 0 0 yes



ORG_PRIMARY_HIER_HZ

Organization primary datetracked hierarchy horizontall flattened



Nullable

1 CURRENT_FLAG If set to Y, the record contains the most currentinformation (Y/N) VARCSTR 1 0 0 yes

2 LEAF_LEVEL Leaf level in horizontal flattening INTEGER 4 0 0 yes

3 LEVEL_0_ID Root Organization id for the current node DECIMAL 48 15 0 yes

4 LEVEL_0_NAME Root Organization name for the current node VARCSTR 240 0 0 yes

5 LEVEL_1_ID Level 1 Organization node ID DECIMAL 48 15 0 yes

6 LEVEL_1_NAME Level 1 Organization node name VARCSTR 240 0 0 yes















Nullable









25 ORGANIZATION_ID PK Systemgenerated primary key column. DECIMAL 48 15 0 no

26 VERSION_NUMBER PK Org hierarchy version number. Only one version iscurrent at a time INTEGER 4 0 0 no



ORG_PRIMARY_HIER_VR

Primary Organization hierarchy vertical dimension



Nullable

1 ANCESTOR_ID PK Ancestor Organization node ID DECIMAL 48 15 0 no

2 ANCESTOR_NAME Ancestor Organization node name VARCSTR 60 0 0 yes

3 CURRENT_FLAG Set to 'Y' if the record is current, otherwise it is 'N' VARCSTR 1 0 0 yes

4 DEPTH Depth of the decendant DECIMAL 48 15 0 yes

5 DESCENDENT_ID PK Systemgenerated primary key column. DECIMAL 48 15 0 no

6 DESCENDENT_NAME Descendent Organization node name VARCSTR 60 0 0 yes

7 LEAF_FLAG Leaf flag (1 means this is a leaf) DECIMAL 48 15 0 yes


9 LOAD_TIME Time in a string format when the record was loaded VARCSTR 8 0 0 yes

10 ROOT_FLAG Root flag (1means this is a root) DECIMAL 48 15 0 yes

11 VERSION_NUMBER PK Version number of the hierarchy (datetracked) DECIMAL 48 15 0 no



ORG_STRUCTURE

Organization hierarchies definition (structure version level)



Nullable




4 DATE_FROM Start date for this version of hierarchy DATE 24 0 9 yes

5 DATE_TO Date date for this version of hierarchy DATE 24 0 9 yes



8 ORGANIZATION_ID PK Systemgenerated primary key column. DECIMAL 48 15 0 no

9 ORG_STRUCTURE_ID PK System generated organization structure primary keyfrom PER_ORGANIZATION_STRUCTURES_S. DECIMAL 48 15 0 no

10 ORG_STRUCTURE_NAME Name of organization hierarchy. VARCSTR 30 0 0 yes

11 PARENT_ORG_ID Foreign key to HR_ORGANIZATION_UNITS.Identifies the parent organization. DECIMAL 48 15 0 yes

12 PRIMARY_HIERARCHY_FLAG

Is this primary organization hierarchy for the businessgroup (Y/N). VARCSTR 30 0 0 yes

13 VERSION_NUMBER PK User enterable version number, not necessarilycontiguous. DECIMAL 48 28 7 no



PEOPLE

Datetracked dimension with employee/applicant personal infomration loaded from PER_ALL_PEOPLE_F



Nullable

1 ACTUAL_TERMIN_DATE Actual date of termination of employment DATETIME 24 0 9 yes

2 ADJUSTED_SVC_DATE Previous date of hire DATETIME 24 0 9 yes

3 APPLICANT_NUMBER Number assigned to person if ever classed as anapplicant. VARCSTR 30 0 0 yes


















Nullable






















Nullable

34 ATTRIBUTE_CATEGORY Descriptive Flexfield structure defining column VARCSTR 30 0 0 yes

35 BENEFIT_GROUP_ID Benefits Group ID DECIMAL 48 15 0 yes

36 BENEFIT_GROUP_NAME Benefits Group Name VARCSTR 60 0 0 yes




40 CREATION_DATE Date when the record was created in the sourcesystem DATETIME 24 0 9 yes





45 DATE_OF_BIRTH Date of birth. DATETIME 24 0 9 yes

46 DATE_OF_DEATH Date of death. DATETIME 24 0 9 yes

47 EFF_END_DATERapid Mart effective end date. UsePEOPLE_END_DATE forPER_ALL_PEOPLE_F.EFF_END_DATE values

DATETIME 24 0 9 no

48 EFF_START_DATERapid Mart effective start date. UsePEOPLE_START_DATE forPER_ALL_PEOPLE_F.EFF_START_DATE values

DATETIME 24 0 9 no







Nullable

51 ETHNIC_ORIGIN_CODE Developer descriptive flexfield PER_INFORMATION1 segment VARCSTR 150 0 0 yes

52 ETHNIC_ORIGIN_NAME Translated ethnic origin name (lookup type =US_ETHNIC_GROUP) VARCSTR 80 0 0 yes

53 FINAL_PROCESS_DATE Final date for all payroll processing of this person DATETIME 24 0 9 yes



56 GENDER_CODE Legal gender code (M/F) VARCSTR 30 0 0 yes

57 GENDER_NAME Translated gender name VARCSTR 80 0 0 yes



60 I_9_EXPIRE_DATE Developer descriptive flexfield column. DATETIME 24 0 9 yes


62 LEAVING_REASON_CODE Reason for termination of employment code VARCSTR 30 0 0 yes

63 LEAVING_REASON_NAME

Reason for termination of employment translatedname VARCSTR 80 0 0 yes




67 MARITAL_STATUS_NAME Translated marital status name VARCSTR 80 0 0 yes





Nullable





New hire status code (PER_INFORMATION7 forcategory US) VARCSTR 150 0 0 yes


73 NUM_HIRES If New Hire status is 'INCL' the value is 1, otherwiseit is set to 0 DECIMAL 48 15 0 yes

74 NUM_TERMINATES If Actual Termination date is NOT NULL, the value is1; otherwise it is set to 0 DECIMAL 48 15 0 yes

75 PEOPLE_END_DATE PER_ALL_PEOPLE_F.EFF_END_DATE values DATETIME 24 0 9 yes

76 PEOPLE_START_DATE PER_ALL_PEOPLE_F.EFF_START_DATE values DATETIME 24 0 9 yes

77 PERIOD_START_DATE Start date of the period of employment. DATETIME 24 0 9 yes

78 PERSON_ID System generated person primary key fromPER_PEOPLE_S DECIMAL 48 10 0 no

79 PERSON_KEY PK Generated surrogate key DECIMAL 48 15 0 no











Nullable

85 SERVICE_ATTRIBUTE1 Descriptive Flexfield segment column VARCSTR 150 0 0 yes





















Nullable




105 SERVICE_ATTRIBUTE_CATEGORY Descriptive Flexfield structure defining column VARCSTR 30 0 0 yes

106 START_DATE Employment/Application Start date for the person(not the DateTrack attribute). DATETIME 24 0 9 yes

107 SUPERVISOR_ID NOT MAPPED! UserEMPLOYEE_ASSIGNMENT_FACT instead DECIMAL 48 10 0 yes










PEOPLE_HOLD

Lookup for Primary contact Persion ID



Nullable

1 APPLICANT_NUMBER Number assigned to person if ever classed as anapplicant. VARCSTR 30 0 0 yes

2 ATTRIBUTE1 Descriptive flexfield column. VARCSTR 150 0 0 yes



















Nullable
















32 ATTRIBUTE_CATEGORY Descriptive flexfield structure defining column. VARCSTR 30 0 0 yes

33 BENEFIT_GROUP_ID Foreign key to benefits group table. DECIMAL 48 15 0 yes





Nullable

34 BENEFIT_GROUP_NAME Benefits group name VARCSTR 60 0 0 yes




38 CREATION_DATE Date when the record was created in the sourcesystem DATETIME 24 0 9 yes




42 DATE_OF_BIRTH Date of birth. DATETIME 24 0 9 yes

43 DATE_OF_DEATH Date of death. DATETIME 24 0 9 yes

44 EFF_END_DATE Effective end date. DATETIME 24 0 9 yes

45 EFF_START_DATE Effective start date. DATETIME 24 0 9 yes



48 ETHNIC_ORIGIN_CODE Developer descriptive flexfield column Segment 1for context = 'US' VARCSTR 150 0 0 yes

49 ETHNIC_ORIGIN_NAME Lookup Meaning for US_ETHNIC_GROUP lookuptype VARCSTR 80 0 0 yes






Nullable


52 GENDER_CODE Legal gender code. Lookup type = SEX VARCSTR 30 0 0 yes

53 GENDER_NAME Gender translated name VARCSTR 80 0 0 yes



56 I_9_EXPIRE_DATE Developer descriptive flexfield column. DATE 24 0 9 yes





61 MARITAL_STATUS_NAME VARCSTR 80 0 0 yes





New hire status code (PER_INFORMATION7 forcategory 'US') VARCSTR 150 0 0 yes


67 PERSON_ID System generated person primary key fromPER_PEOPLE_S. DECIMAL 48 10 0 yes





Nullable







73 START_DATE Start date for the person (not the DateTrackattribute). DATETIME 24 0 9 yes










PERIOD_CALENDAR

Calendar and Fiscal periods dimension



Nullable

1 CALENDAR_OR_FISCAL If set to C, period belongs to a calendar year, if it isset to F, it is a fiscal period VARCSTR 1 0 0 yes



4 NUM_PER_FISCAL_YR Number of periods per fiscal year DECIMAL 48 15 0 yes

5 PERIOD_END_DATE Date on which accounting period ends DATE 24 0 9 yes

6 PERIOD_FULL_NAME Concatenation of Period Set Name and Period Name VARCSTR 35 0 0 yes

7 PERIOD_HALF_YEAR Calculated half year number (1 or 2) VARCSTR 12 0 0 yes

8 PERIOD_NAME PK System generated accounting period name VARCSTR 15 0 0 no

9 PERIOD_NUMBER Accounting period number DECIMAL 48 15 0 yes

10 PERIOD_QUARTER Quarter number of accounting period DECIMAL 48 15 0 yes

11 PERIOD_SET_NAME PK Accounting calendar name VARCSTR 15 0 0 no

12 PERIOD_START_DATE Date on which accounting period begins DATE 24 0 9 yes

13 PERIOD_TYPE_NAME Calendar Period type user defined name VARCSTR 15 0 0 yes

14 PERIOD_YEAR Accounting period year DECIMAL 48 15 0 yes

15 YEAR_PERIOD Concatenated year and peirod number VARCSTR 12 0 0 yes

16 YEAR_QUARTER Concatenated year and quarter number VARCSTR 12 0 0 yes



PO_AGENT_STAGE

Staging table holding buyer information



Nullable

1 AGENT_ID PK Buyer unique identifier DECIMAL 48 9 0 no

2 BUYER_AUTHORIZATION_LIMIT

Maximum purchase order authorization limit for thebuyer DECIMAL 48 28 7 yes

3 BUYER_END_DATE_ACTIVE Date buyer active to DATE 24 0 9 yes

4 BUYER_START_DATE_ACTIVE Date buyer active from DATE 24 0 9 yes





PROJECT

Descriptive information about the highest units of work (project) defined in Oracle Projects Application



Nullable

1 CARRYING_ORG_ID The identifier of the organization that is responsiblefor the project work DECIMAL 48 15 0 yes

2 CARRYING_ORG_NAME Translated name of the organization VARCSTR 60 0 0 yes

3 CLOSED_DATE The date that the project was closed by changing theproject status to Closed DATE 24 0 9 yes

4 COMPLETION_DATEThe date on which the project is completed;expenditure items with item dates after thecompletion date cannot be entered for the project

DATE 24 0 9 yes

5 CREATED_BYApplication username (what a user types in at theOracle Applications signon screen) who createdthe record

VARCSTR 100 0 0 yes


7 CURRENCY_CODE_PRJ Currency code of the project VARCSTR 15 0 0 yes

8 EXPECT_APPROV_DATE The expected date of the project approval. This isused for information purposes only. DATE 24 0 9 yes




12 ORG_NAME Business unit translated name VARCSTR 60 0 0 yes

13 PROJECT_DESC The description of the project VARCSTR 250 0 0 yes

14 PROJECT_ID PK The systemgenerated number that uniquelyidentifies the project DECIMAL 48 15 0 no

15 PROJECT_NAME Userdefined name that uniquely identifies the project VARCSTR 30 0 0 yes

16 PROJECT_NUMThe project number that uniquely identifies theproject. The project number can be userentered orsystemgenerated as defined in the implementationoptions

VARCSTR 25 0 0 yes





Nullable

17 PROJECT_VALUEProject value is used in reporting. For contractprojects, it is the revenue amount. For capital andindirect projects, it is the cost amount. It is notassumed that thec

DECIMAL 48 28 7 yes

18 PROJ_CLASS_CODE Indicates the class of project type VARCSTR 30 0 0 yes

19 PROJ_CLASS_NAME Project Type Class descritpion (meaning for LookupType PROJECT TYPE CLASS VARCSTR 80 0 0 yes

20 PROJ_STATUS_CODE The status of the project VARCSTR 30 0 0 yes

21 PROJ_STATUS_NAME Project Status translated name (meaning for lookuptype = PROJECT STATUS VARCSTR 80 0 0 yes

22 PROJ_TYPE_CODE The project type that classifies the project anddefaults project information upon project entry VARCSTR 20 0 0 yes

23 PROJ_TYPE_DESC Description of the project type VARCSTR 250 0 0 yes

24 PUBLIC_SECT_FLAG Flag that indicates whether the project is in the publicsector or the private sector VARCSTR 1 0 0 yes

25 SERVICE_TYPE_CODE The service type that defaults the task service type ofprojects with this project type VARCSTR 30 0 0 yes

26 SERVICE_TYPE_NAME Project Service Type name (meaning for LookupType SERVICE TYPE) VARCSTR 80 0 0 yes

27 START_DATEThe date on which the project starts; expenditureitems with item dates before the start date cannot beentered for the project

DATE 24 0 9 yes

28 UNBILLED_AR_DRThe unbilled receivables balance for the project thatis posted to Oracle General Ledger or OracleReceivables. This value is maintained by theTransfer Revenue and Tran

DECIMAL 48 22 5 yes

29 UNEARNED_REVN_CRThe unearned revenue balance for the project that isposted to Oracle General Ledger or OracleReceivables. This value is maintained by theTransfer Revenue and Transfer

DECIMAL 48 22 5 yes



PROJECT_AGREEMENT

Project Agreement dimension



Nullable

1 AGREEMENT_CURRENCY_CODE Agreement currency code of the agreement NVARCSTR 15 0 0 yes

2 AGREEMENT_DESC The free text description to describe the agreement NVARCSTR 240 0 0 yes

3 AGREEMENT_ID PK The systemgenerated number that uniquelyidentifies the agreement DECIMAL 48 15 0 no

4 AGREEMENT_NUM The userentered number that identifies theagreement NVARCSTR 50 0 0 no

5 AGREEMENT_TYPE The agreement type that classifies the agreement NVARCSTR 30 0 0 no

6 AGREEMENT_TYPE_DESC Explanation of the agreement type NVARCSTR 250 0 0 yes

7 AMOUNT The amount of revenue authorized for the agreement DECIMAL 48 22 5 yes


9 CUSTOMER_ID The identifier of the customer who is authorizing theagreement DECIMAL 48 15 0 yes

10 CUSTOMER_NAME Customer name NVARCSTR 50 0 0 yes

11 EXPIRATION_DATE Date on which the agreement expires DATETIME 24 0 9 yes


13 LOAD_TIME Time when the record was loaded NVARCSTR 8 0 0 yes


15 REVENUE_LIMIT_FLAGFlag indicating whether revenue for projects fundedby this agreement can exceed the allocated fundingamount

NVARCSTR 1 0 0 yes



PROJECT_ASSET_FACT

Project Asset fact table containing details of assets for capital projects



Nullable

1 AMORTIZE_FLAG Indicates whether or not cost adjustments should beamortized in Oracle Assets NVARCSTR 1 0 0 no

2 ASSET_CATEGORY_ID PK The identifier of the asset category to which the assetis assigned DECIMAL 48 15 0 no

3 ASSET_DESCRIPTION Description; placed on parent mass additions lineupon transfer to Oracle Assets NVARCSTR 80 0 0 no

4 ASSET_LINE_DESCRIPTION

Description of the asset line, derived from the CIPgrouping method NVARCSTR 255 0 0 no

5 ASSET_NAME Userdefined name that uniquely identifies an assetwithin a project NVARCSTR 240 0 0 no

6 ASSET_NUMBER Unique asset identifier; can be userentered orsystemgenerated by Oracle Assets NVARCSTR 15 0 0 no

7 ASSET_UNITS The number of asset units DECIMAL 48 28 7 yes

8 ASSIGNED_TO_PERSON_ID

The identifier of the employee to whom the asset isassigned DECIMAL 48 10 0 no

9 BOOK_TYPE_ID The corporate book to which the asset is assigned NVARCSTR 15 0 0 no

10 CAPITALIZED_COST The cost amount which has been interfaced to OracleAssets for capitalization. DECIMAL 48 22 5 yes

11 CAPITALIZED_DATE The last date nonreversing cost adjustments wereinterfaced to Oracle Assets DATETIME 24 0 9 no

12 CAPITALIZED_FLAG Indicates whether or not the asset has beeninterfaced to Oracle Assets NVARCSTR 1 0 0 no

13 CREATION_DATE Date when the record was created in the applicationsystem DATETIME 24 0 9 no


15 CURRENT_ASSET_COST The lines current cost amount; split lines have acurrent cost <> original cost DECIMAL 48 22 5 yes

16 DATE_PLACED_IN_SERVICE PK Date placed in service of the asset DATETIME 24 0 9 no





Nullable

17 DEPRECIATE_FLAG Indicates whether or not the asset should bedepreciated in Oracle Assets NVARCSTR 1 0 0 no

18 ESTIMATED_IN_SERVICE_DATE The assets estimated date placed in service DATETIME 24 0 9 no


20 GROUPED_CIP_COST The assets cost amount which has been grouped intoasset lines. DECIMAL 48 22 5 yes



23 LOCATION_ID PK The identifier of the location to which the asset isassigned DECIMAL 48 15 0 no






27 ORIGINAL_ASSET_COST The cost amount of the line at the time the line wasoriginally created DECIMAL 48 22 5 yes


29 PROJECT_ASSET_ID The systemgenerated number that uniquelyidentifies the asset DECIMAL 48 15 0 no

30 PROJECT_ASSET_LINE_ID PK The systemgenerated number that uniquely

identifies the asset line DECIMAL 48 15 0 no

31 PROJECT_ID PK The identifier of the project to which this assetbelongs DECIMAL 48 15 0 no







Populates PROJECT_CLASS_CATEGORY dimension (categorization of project by class category and class code)



Nullable

1 CATEGORY_DESC Explanation of the class category NVARCSTR 80 0 0 yes

2 CLASS_CATEGORY PK The class category by which the project is classified NVARCSTR 30 0 0 no

3 CLASS_CODE PK The class code that classifies the project NVARCSTR 30 0 0 no

4 CLASS_DESC Explanation of the class code NVARCSTR 250 0 0 yes


6 LOAD_DATE No Description is available for this object DATETIME 24 0 9 yes

7 LOAD_TIME No Description is available for this object NVARCSTR 8 0 0 yes

8 PROJECT_ID PK The identifier of the object this classification belongsto (restricted to Projects) DECIMAL 48 15 0 no



PROJECT_PERIOD

Project Period dimension



Nullable

1 ALT_PERIOD_NAMECalculated Period Name based on its associationwith calendar period; used in conjunction with PeriodType.

NVARCSTR 60 0 0 yes

2 CALENDAR_HALFYEAR Integer that represent Calendar HalfYear (1 or 2) forHalfYear Period Type. Based on Period Start Date DECIMAL 48 28 0 yes

3 CALENDAR_MONTH Integer that represent Calendar Month for MonthPeriod Type. Based on Period Start Date DECIMAL 48 28 0 yes

4 CALENDAR_QTR Integer that represent Calendar Qtr for Qtr PeriodType. Based on Period Start Date DECIMAL 48 28 0 yes

5 CALENDAR_YEAR Integer that represent CalendarYear for Year PeriodType. Based on Period Start Date DECIMAL 48 28 0 yes

6 CURRENT_PERIOD_FLAG

Indicates the current period used for reporting andaccumulation NVARCSTR 1 0 0 yes

7 DAY_IN_YEAR Integer that represent Calendar Day (1366) for DayPeriod Type. Based on Period Start Date DECIMAL 48 28 0 yes

8 END_DATE The end date of the project period DATETIME 24 0 9 yes

9 GL_PERIOD_NAME The GL period that matches the project period NVARCSTR 15 0 0 yes


11 LOAD_TIME Time when the record was loaded NVARCSTR 8 0 0 yes

12 ORG_ID PK Operating unit identifier for multiorganizationinstallations DECIMAL 48 15 0 no

13 PA_PERIOD_TYPE Calculated Period type. Values are: Year, HalfYear,Qtr, Month, Week, Day, Other NVARCSTR 30 0 0 yes

14 PERIOD_NAME PK The implementationdefined name that uniquelyidentifies the period NVARCSTR 20 0 0 no

15 PERIOD_NUM_DAYS Number of days in Project Period DECIMAL 48 28 0 yes

16 START_DATE The start date of the project period DATETIME 24 0 9 yes





Nullable

17 WEEK_IN_YEAR Integer that represent Calendar Week (152) forWeek Period Type. Based on Period Start Date DECIMAL 48 28 0 yes

PROJECT_RESOURCE

Project Resource dimension



Nullable

1 END_DATE_ACTIVE Last effective date of the resource DATE 24 0 9 yes



4 PROJECT_RESOURCE Name of the project resource. VARCSTR 100 0 0 yes

5 RESOURCE_CLASS_CODE

Indicates the resource type class. At present the validvalues arePRE_DEFINED,USER_DEFINED,UNCATEGORIZED, andUNCLASSIFIED

VARCSTR 30 0 0 yes

6 RESOURCE_DESCRIPTION Description for the resource VARCSTR 255 0 0 yes

7 RESOURCE_ID PK The system generated number that uniquelyidentifies the resource DECIMAL 48 15 0 no

8 RESOURCE_TYPE The name of the resource type VARCSTR 60 0 0 yes

9 RESOURCE_TYPE_CODE

Holds the code used to identify the resource type.The supported resource type codes are EMPLOYEE,JOB, EXPENDITURE_TYPE, ORGANIZATION,EVENT TYPE, EXPENDITURE CATEGORY,

VARCSTR 30 0 0 yes

10 RESOURCE_TYPE_DESCRIPTION The Description of the resource type VARCSTR 255 0 0 yes

11 RESOURCE_TYPE_ID The identifier of the type of resource, such asEmployee, Job,or Expenditure Type. DECIMAL 48 15 0 yes

12 START_DATE_ACTIVE Effective start date of the resource DATE 24 0 9 yes

13 UNIT_OF_MEASURE Holds the unit of measure of the resource, such asHours, Miles, or Dollars. VARCSTR 30 0 0 yes




Project Summary fact table containing summarized data



Nullable

1 BILLABLE_BURDENED_COST_ITD Inception to date billable burdened cost for project DECIMAL 48 28 7 yes

2 BILLABLE_BURDENED_COST_PP Billable burdened cost for prior GL or PA period DECIMAL 48 28 7 yes

3 BILLABLE_BURDENED_COST_PTD

Period to date billable burdened cost for PA or GLperiod DECIMAL 48 28 7 yes

4 BILLABLE_BURDENED_COST_YTD Year to date billable burdened cost for project DECIMAL 48 28 7 yes

5 BILLABLE_LABOR_HOURS_ITD Inception to date billable labor hours for project DECIMAL 48 28 7 yes

6 BILLABLE_LABOR_HOURS_PP Billable labor hours for prior GL or PA period DECIMAL 48 28 7 yes

7 BILLABLE_LABOR_HOURS_PTD

Period to date billable labor hours for PA or GLperiod DECIMAL 48 28 7 yes

8 BILLABLE_LABOR_HOURS_YTD Year to date billable labor hours for project DECIMAL 48 28 7 yes

9 BILLABLE_QUANTITY_ITD Inception to date billable quantity for project DECIMAL 48 28 7 yes

10 BILLABLE_QUANTITY_PP Billable quantity for prior GL or PA period DECIMAL 48 28 7 yes

11 BILLABLE_QUANTITY_PTD Period to date billable quantity for PA or GL period DECIMAL 48 28 7 yes

12 BILLABLE_QUANTITY_YTD Year to date billable quantity for project DECIMAL 48 28 7 yes

13 BILLABLE_RAW_COST_ITD Inception to date billable raw cost for project DECIMAL 48 28 7 yes

14 BILLABLE_RAW_COST_PP Billable raw cost for prior GL or PA period DECIMAL 48 28 7 yes

15 BILLABLE_RAW_COST_PTD Period to date billable raw cost for PA or GL period DECIMAL 48 28 7 yes

16 BILLABLE_RAW_COST_YTD Year to date billable raw cost for project DECIMAL 48 28 7 yes





Nullable

17 BURDENED_COST_ITD Inception to date burdened cost for project DECIMAL 48 28 7 yes

18 BURDENED_COST_PP Burdened cost for prior GL or PA period DECIMAL 48 28 7 yes

19 BURDENED_COST_PTD Period to date burdened cost for PA or GL period DECIMAL 48 28 7 yes

20 BURDENED_COST_YTD Year to date burdened cost for project DECIMAL 48 28 7 yes

21 CREATION_DATE Project Actuals Accum Creation Date DATETIME 24 0 9 yes


23 GL_PERIOD_NAME Last accumulation GL period NVARCSTR 15 0 0 yes

24 LABOR_HOURS_ITD Inception to date labor hours for project DECIMAL 48 28 7 yes

25 LABOR_HOURS_PP Labor hours for prior GL or PA period DECIMAL 48 28 7 yes

26 LABOR_HOURS_PTD Period to date labor hours for PA or GL period DECIMAL 48 28 7 yes

27 LABOR_HOURS_YTD Year to date labor hours for project DECIMAL 48 28 7 yes








33 PERIOD_NAME Last accumulation GL or PA period, depending onthe imp. option NVARCSTR 20 0 0 no





Nullable


35 PROJECT_ACCUM_ID PK The identifier of accumulation header for which thisline was created DECIMAL 48 15 0 no

36 PROJECT_ID PK The identifier of project for which the header wascreated DECIMAL 48 15 0 no

37 QUANTITY_ITD Inception to date quantity for project DECIMAL 48 28 7 yes

38 QUANTITY_PP Quantity for prior GL or PA period DECIMAL 48 28 7 yes

39 QUANTITY_PTD Period to date quantity for PA or GL period DECIMAL 48 28 7 yes

40 QUANTITY_YTD Year to date quantity for project DECIMAL 48 28 7 yes

41 RAW_COST_ITD Inception to date raw cost for project DECIMAL 48 28 7 yes

42 RAW_COST_PP Raw cost for prior GL or PA period DECIMAL 48 28 7 yes

43 RAW_COST_PTD Period to date raw cost for PA or GL period DECIMAL 48 28 7 yes

44 RAW_COST_YTD Year to date raw cost for project DECIMAL 48 28 7 yes

45 RESOURCE_ID PK The identifier of resource for which the header wascreated DECIMAL 48 15 0 no

46 REVENUE_ITD Inception to date revenue for the project DECIMAL 48 28 7 yes

47 REVENUE_PP Prior GL or PA period revenue for the project DECIMAL 48 28 7 yes

48 REVENUE_PTD Period to date revenue for the project DECIMAL 48 28 7 yes

49 REVENUE_YTD Year to date revenue for project DECIMAL 48 28 7 yes






Nullable



52 TASK_ID PK The identifier of task for which the header wascreated DECIMAL 48 15 0 no




Project transaction Summary fact table containing summarized transaction data



Nullable

1 ACTUAL_COST_ROLLUP_FLAG

Indicates if the actual cost is rolled up topa_project_accum_actuals NVARCSTR 1 0 0 no

2 CMT_IND_COMPILED_SET_ID

Indirect compiled set used for calculating burdenedcost for commitments DECIMAL 48 15 0 yes

3 CMT_ROLLUP_FLAG Indicates if the commitment are rolled up topa_project_accum_commitments NVARCSTR 1 0 0 no

4 COST_IND_COMPILED_SET_ID

Indirect compiled set id used for calculating burdenedcost DECIMAL 48 15 0 yes



7 EVENT_TYPE_CLASSIFICATION Event type classification of the accumulated txn NVARCSTR 30 0 0 no

8 EVENT_TYPE_ID Event type ID of the accumulated txn DECIMAL 48 15 0 no

9 EXPENDITURE_CATEGORY Expenditure category of the accumulated txn NVARCSTR 30 0 0 no

10 EXPENDITURE_TYPE_ID PK Expenditure type ID of the accumulated txn DECIMAL 48 15 0 no

11 GL_PERIOD_NAME GL period name of the accumulated txn NVARCSTR 15 0 0 no

12 INV_IND_COMPILED_SET_ID Indirect compiled set id used for calculating invoice DECIMAL 48 15 0 yes

13 I_TOT_BILLABLE_BURDENED_COST Also stores future period billable burdened cost DECIMAL 48 28 7 yes

14 I_TOT_BILLABLE_LABOR_HOURS Also stores future period billable labor hours DECIMAL 48 28 7 yes

15 I_TOT_BILLABLE_QUANTITY Also stores future period billable quantity DECIMAL 48 28 7 yes

16 I_TOT_BILLABLE_RAW_COST Also stores future period billable raw cost DECIMAL 48 28 7 yes





Nullable

17 I_TOT_BURDENED_COST Also stores future period burdened cost amount DECIMAL 48 28 7 yes

18 I_TOT_LABOR_HOURS Also stores future period labor hours DECIMAL 48 28 7 yes

19 I_TOT_QUANTITY Also stores future period quantity DECIMAL 48 28 7 yes

20 I_TOT_RAW_COST Also stores future period raw cost amount DECIMAL 48 28 7 yes

21 I_TOT_REVENUE Also stores future period revenue amount DECIMAL 48 28 7 yes

22 JOB_ID PK The identifier of the job for which accumulation isdone DECIMAL 48 15 0 no



25 MONTH_ENDING_DATE Month ending date for the accumulated transaction DATETIME 24 0 9 no

26 NON_LABOR_RESOURCE Expenditure category of the accumulated txn NVARCSTR 20 0 0 no


Non labor resource organization id of theaccumulated txn DECIMAL 48 28 7 no



29 ORG_ID The identifier of the organization for whichaccumulation is done DECIMAL 48 15 0 no



31 PERIOD_NAME PA period name of the accumulated txn NVARCSTR 20 0 0 no


33 PERSON_ID PK The identifier of the person for which accumulation isdone DECIMAL 48 10 0 no





Nullable

34 PROJECT_ID PK Identifier of project for the accumulated txn DECIMAL 48 15 0 no

35 REVENUE_CATEGORY Revenue category of the accumulated txn NVARCSTR 30 0 0 no

36 REVENUE_ROLLUP_FLAG

Indicates if the revenue is rolled up topa_project_accum_actuals NVARCSTR 1 0 0 no

37 REV_IND_COMPILED_SET_ID Indirect compiled set id used for calculating revenue DECIMAL 48 15 0 yes




40 TASK_ID PK Identifier of task for the accumulated txn DECIMAL 48 15 0 no

41 TOT_BILLABLE_BURDENED_COST Total billable burdened cost amount DECIMAL 48 28 7 yes

42 TOT_BILLABLE_LABOR_HOURS Total billable labor hours amount DECIMAL 48 28 7 yes

43 TOT_BILLABLE_QUANTITY Total billable quantity amount DECIMAL 48 28 7 yes

44 TOT_BILLABLE_RAW_COST Total billable raw cost amount DECIMAL 48 28 7 yes

45 TOT_BURDENED_COST Total Burdened cost amount DECIMAL 48 28 7 yes

46 TOT_CMT_BURDENED_COST Total commitment burdened cost amount DECIMAL 48 28 7 yes

47 TOT_CMT_QUANTITY Total commitment quantity amount DECIMAL 48 28 7 yes

48 TOT_CMT_RAW_COST Total commitment raw cost amount DECIMAL 48 28 7 yes

49 TOT_LABOR_HOURS Total labor hours amount DECIMAL 48 28 7 yes

50 TOT_QUANTITY Total quantity amount DECIMAL 48 28 7 yes





Nullable

51 TOT_RAW_COST Total Raw cost amount DECIMAL 48 28 7 yes

52 TOT_REVENUE Total revenue amount DECIMAL 48 28 7 yes

53 TXN_ACCUM_ID PK The identifier uniquely identifies txns that weregroups of accumulated txns DECIMAL 48 15 0 no

54 UNIT_OF_MEASURE Unit of measure for commitments or actual cost NVARCSTR 30 0 0 no

55 VENDOR_ID The identifier of the supplier for which accumulationis done DECIMAL 48 28 7 no

56 WEEK_ENDING_DATE Week ending date for the accumulated transaction DATETIME 24 0 9 no

REVENUE_CATEGORY

Revenue Category reference dimension



Nullable




4 REV_CATEGORY_CODE PK The revenue category of the expenditure itemsgrouped into the revenue line. NVARCSTR 30 0 0 no

5 REV_CATEGORY_DESC Revenue Category value Description NVARCSTR 240 0 0 yes

6 REV_CATEGORY_NAME QuickCode meaning (name) for REVENUECATEGORY lookup type NVARCSTR 80 0 0 no




REVENUE_SOURCE

Revenue Source reference dimension



Nullable




4 REV_SOURCE_CODE PK The source from which the revenue for the revenueline is generated. NVARCSTR 30 0 0 no

5 REV_SOURCE_DESC Revenue Source value Description NVARCSTR 240 0 0 yes

6 REV_SOURCE_NAME QuickCode meaning (name) for REVENUE SOURCElookup type NVARCSTR 80 0 0 no




SERVICE_PERIOD_HOLD



Nullable

1 ACTUAL_TERMINATION_DATE Actual date of termination of employment. DATETIME 24 0 9 yes

2 ADJUSTED_SVC_DATE Previous date of hire. DATETIME 24 0 9 yes


4 EFF_END_DATEThe date until which this record is effective. It isautomatically generated by the Effective_Datetransform

DATE 24 0 9 yes

5 EFF_START_DATE Effective start date. DATETIME 24 0 9 yes

6 FINAL_PROCESS_DATE Final date for all payroll processing of this person. DATETIME 24 0 9 yes

7 LEAVING_REASON_CODE Reason for termination of employment. VARCSTR 30 0 0 yes

8 LEAVING_REASON_NAME Translated name for Leaving Reason VARCSTR 80 0 0 yes



11 PERIOD_OF_SERVICE_ID

System generated period of service primary key fromPER_PERIODS_OF_SERVICE_S. DECIMAL 48 9 0 yes

12 PERIOD_START_DATE Start date of the period of employment. DATETIME 24 0 9 yes

13 PERSON_ID System generated person primary key fromPER_PEOPLE_S. DECIMAL 48 10 0 yes

14 SERVICE_ATTRIBUTE1 Descriptive flexfield column. VARCSTR 150 0 0 yes







Nullable






















Nullable

34 SERVICE_ATTRIBUTE_CATEGORY Descriptive flexfield structure defining column. VARCSTR 30 0 0 yes

SET_OF_BOOKS

Set of Books dimension



Nullable

1 CHART_OF_ACCNTS_ID Key flexfield structure defining column DECIMAL 48 15 0 yes

2 CHART_OF_ACCTS_NAME Key flexfield structure name for the chart of accounts VARCSTR 30 0 0 yes

3 CURRENCY_CODE Currency Code (Functional currency) VARCSTR 15 0 0 yes



6 NUM_PER_FYEAR Number of periods per fiscal year DECIMAL 48 15 0 yes

7 PERIOD_SET_NAME Accounting calendar name VARCSTR 15 0 0 yes

8 PERIOD_TYPE_NAME Calendar period type user defined name VARCSTR 15 0 0 yes

9 SET_OF_BOOKS_DESC Accounting books description VARCSTR 240 0 0 yes

10 SET_OF_BOOKS_ID PK Accounting books defining column DECIMAL 48 15 0 no

11 SET_OF_BOOKS_NAME Accounting books name VARCSTR 30 0 0 yes

12 SHORT_NAME Accounting books short name VARCSTR 20 0 0 yes

13 YEAR_TYPE_NAME QuickCode meaning for YEAR_TYPE_IN_NAME Year type (Fiscal or Calendar) VARCSTR 80 0 0 yes



TASK

Project Task dimension



Nullable

1 BILLABLE_FLAGDefault flag for items charged to the task thatindicates if the item can accrue revenue (Y or N).For capital projects this flag is used ascapitalizable_flag. For ind

VARCSTR 1 0 0 yes

2 CHARGEABLE_FLAGFlag that indicates if expenditure items can becharged to the task. Only lowest level tasks can bechargeable

VARCSTR 1 0 0 yes

3 COMPLETION_DATEThe date on which the task is completed;expenditure items with item dates after the taskcompletion date cannot be entered for the task. Youmust enter a start date to

DATE 24 0 9 yes

4 CREATION_DATE Date task created DATE 24 0 9 yes

5 DESCRIPTION Description of the task VARCSTR 250 0 0 yes



8 LONG_TASK_NAME Task Long Name VARCSTR 240 0 0 yes

9 PARENT_TASK_ID The identifier of the task that is the parent of the taskin the project work breakdown structure DECIMAL 48 15 0 yes

10 PROJECT_ID The identifier of the project for which the task is a unitof work DECIMAL 48 15 0 yes

11 READY_TO_BILL_FLAGFlag that indicates whether the task is authorized tobe invoiced. The flag is set only for top tasks,defaults to Y upon creation of the task and is set to Yor N in t

VARCSTR 1 0 0 yes

12 READY_TO_DISTRIBUTE_FLAG

Flag that indicates whether the task is authorized forrevenue accrual. The flag is set only for top tasks,defaults to Y upon creation of the task, and is set to Yor N

VARCSTR 1 0 0 yes

13 SERVICE_TYPE_CODE The type of work performed on the task VARCSTR 30 0 0 yes

14 START_DATEThe date on which the task starts; expenditure itemswith item dates before the start date cannot beentered for the task

DATE 24 0 9 yes

15 TASK_CARRYING_OUT_ORG_ID

The identifier of the organization that is responsiblefor the task work. The project organization isdefaulted to the task organization upon creation ofthe task

DECIMAL 48 15 0 yes

16 TASK_CARRYING_OUT_ORG_NAME Name of the organization carrying out the task VARCSTR 60 0 0 yes





Nullable

17 TASK_ID PK The systemgenerated number that uniquelyidentifies the task DECIMAL 48 15 0 no

18 TASK_MANAGER Task manager full name VARCSTR 240 0 0 yes

19 TASK_MANAGER_PERSON_ID The identifier of the employee that manages the task. DECIMAL 48 10 0 yes

20 TASK_NAME Userdefined short name of the task VARCSTR 20 0 0 yes

21 TASK_NUMBERUserdefined number that uniquely identifies the taskwithin a project. It is recommended to number tasksbased on the wbs since that is how tasks are orderedin some re

VARCSTR 25 0 0 yes



TASK_HIER_HZ

Task horizontal hierarchy



Nullable

1 LEAF_LEVEL Leaf level in horizontal flattening INTEGER 4 0 0 yes

2 LEVEL_0_TASK_ID Root Task ID for the current node DECIMAL 48 15 0 yes

3 LEVEL_0_TASK_NAME Root task name for the current node VARCSTR 240 0 0 yes

4 LEVEL_10_TASK_ID Level 10 Task ID DECIMAL 48 15 0 yes

5 LEVEL_10_TASK_NAME Level 10 task name VARCSTR 240 0 0 yes
















Nullable














30 TASK_ID PK Task Identifier DECIMAL 48 15 0 no



TASK_HIER_VR

Task vertical hierarchy



Nullable

1 ANCESTOR_TASK_ID PK Ancestor Task ID to TASK dimension DECIMAL 48 15 0 no

2 ANCESTOR_TASK_NAME Taskl name of the ancestor VARCSTR 240 0 0 yes

3 DEPTH Depth of the descendent INTEGER 4 0 0 yes

4 DESCENDENT_TASK_ID PK DescendentTask ID to TASK dimension DECIMAL 48 15 0 no

5 DESCENDENT_TASK_NAME Task name of the descendent VARCSTR 240 0 0 yes

6 LEAF_FLAG Leaf Flag (1 means leaf) INTEGER 4 0 0 yes


8 LOAD_TIME Time in a string format when the record was loaded VARCSTR 8 0 0 yes

9 ROOT_FLAG Root Flag (1 means root) INTEGER 4 0 0 yes



TIME_DIM

Time Dimension



Nullable

1 CALENDAR_DATE PK Calendar Date DATE 24 0 9 no

2 CALENDAR_MONTH Calendar Month INTEGER 4 0 0 yes

3 CALENDAR_QTR Calendar Year INTEGER 4 0 0 yes

4 CALENDAR_YEAR Calendar Year INTEGER 4 0 0 yes

5 DAY_IN_WEEK Day in Week INTEGER 4 0 0 yes

6 FISCAL_PERIOD Accounting period number INTEGER 4 0 0 yes

7 FISCAL_PERIOD_NAME Accounting period name VARCSTR 15 0 0 yes

8 FISCAL_YEAR Accounting period year INTEGER 4 0 0 yes

9 IS_WEEKEND Weekend Indicator VARCSTR 1 0 0 yes



12 MONTH_YEAR Month and year of the day VARCSTR 10 0 0 yes

13 WEEK_IN_YEAR Week in Year INTEGER 4 0 0 yes



TRANSFER_STATUS

Transfer Status reference dimension



Nullable





5 TRANSFER_STATUS_CODE PK Transfer status code NVARCSTR 30 0 0 no

6 TRANSFER_STATUS_DESC Transfer status value Description NVARCSTR 240 0 0 yes

7 TRANSFER_STATUS_NAME

QuickCode meaning (name) for TRANSFERSTATUS lookup type NVARCSTR 80 0 0 no



VENDOR

Vendor Master information (business unit independent)



Nullable

1 CREATED_BY Application username who created vendor site record VARCSTR 100 0 0 yes


3 END_DATE_ACTIVE Date when supplier becomes inactive DATE 24 0 9 yes

4 FEDERAL_REPORTABLE_FLAG Federal reportable flag VARCSTR 1 0 0 yes

5 FREIGHT_TERMS_CODE Default freight terms type VARCSTR 25 0 0 yes

6 HOLD_REASON Reason for placing the supplier on payment hold VARCSTR 240 0 0 yes



9 MINORITY_GROUP_CODE Type of minorityowned business VARCSTR 25 0 0 yes

10 NUM_1099 Tax identification number VARCSTR 30 0 0 yes

11 ORGANIZATION_TYPE_CODE IRS organization type VARCSTR 25 0 0 yes

12 PARENT_VENDOR_ID Unique identifier of the parent supplier DECIMAL 48 28 7 yes

13 PARENT_VENDOR_NAME Parent vendor name VARCSTR 80 0 0 yes

14 PAR_VENDOR_NUMBER Parent vendor number VARCSTR 30 0 0 yes

15 PAYMENT_PRIORITY Payment priority DECIMAL 48 28 7 yes

16 PAYMENT_TERM_ID Payment terms unique identifier DECIMAL 48 28 7 yes





Nullable

17 PAYMENT_TERM_NAME Name of payment term VARCSTR 50 0 0 yes

18 PAY_GROUP_CODE Payment group type (PAY GROUP LOV type) VARCSTR 25 0 0 yes

19 PAY_GROUP_NAME Values for PAY GROUP LOV type (Payment groupthe supplier belongs to) VARCSTR 80 0 0 yes

20 SDRD_INDUSTRY_CLASS Standard industry classification number VARCSTR 25 0 0 yes

21 SMALL_BUSINESS_FLAG Indicates that the supplier is a small business VARCSTR 1 0 0 yes

22 START_DATE_ACTIVE Date supplier becomes active DATE 24 0 9 yes

23 STATE_REPORTABLE_FLAG State reportable flag VARCSTR 1 0 0 yes

24 TAX_REPORTING_NAME Tax reporting method name VARCSTR 80 0 0 yes

25 TAX_VERIFICATION_DATE Tax verification date DATE 24 0 9 yes

26 TYPE_1099 Type of 1099 VARCSTR 10 0 0 yes

27 VENDOR_ACTIVE_FLAG Indicates whether vendor is current VARCSTR 1 0 0 yes

28 VENDOR_ID PK Supplier unique identifier DECIMAL 48 28 7 no

29 VENDOR_NAME Supplier name VARCSTR 80 0 0 yes

30 VENDOR_NUMBER Supplier number VARCSTR 30 0 0 yes

31 VENDOR_TYPE_CODE Supplier type code (VENDOR TYPE LOV type) VARCSTR 25 0 0 yes

32 VENDOR_TYPE_NAME Values for VENDOR TYPE LOV type (supplier type) VARCSTR 80 0 0 yes

33 WOMEN_OWNED_FLAG Indicates whether the supplier is a womanownedbusiness VARCSTR 1 0 0 yes



VENDOR_CONTACT

Vendor contact information



Nullable

1 AREA_CODE Area code VARCSTR 10 0 0 yes

2 CREATED_BY Application username who created vendor contactrecord VARCSTR 100 0 0 yes

3 CREATION_DATE Date record created DATE 24 0 9 yes

4 FIRST_NAME First name VARCSTR 15 0 0 yes

5 INACTIVE_DATE Inactive date for record DATE 24 0 9 yes

6 LAST_NAME Last name VARCSTR 20 0 0 yes

7 LAST_UPDATED_BY Application username who last updated vendorcontact record VARCSTR 100 0 0 yes

8 LAST_UPDATED_DATE Date when the record was last updated in the sourcesystem DATE 24 0 9 yes



11 MAIL_STOP Email address VARCSTR 35 0 0 yes

12 MIDDLE_NAME Middle name VARCSTR 15 0 0 yes

13 PHONE Phone number VARCSTR 15 0 0 yes

14 PREFIX Prefix VARCSTR 5 0 0 yes

15 TITLE Title VARCSTR 30 0 0 yes

16 VENDOR_CONTACT_ID PK Supplier contact unique identifier DECIMAL 48 28 7 no





Nullable

17 VENDOR_ID Supplier unique identifier DECIMAL 48 28 7 yes

18 VENDOR_SITE_ID Supplier site unique identification DECIMAL 48 28 7 yes



VENDOR_SITE

Vendor Site information (business unit dependent)



Nullable

1 ADDRESS_1 First line of supplier address VARCSTR 240 0 0 yes

2 ADDRESS_2 Second line of supplier address VARCSTR 240 0 0 yes

3 ADDRESS_3 Third line of supplier address VARCSTR 240 0 0 yes

4 AREA_CODE Area code VARCSTR 10 0 0 yes

5 CITY City name VARCSTR 25 0 0 yes

6 COUNTRY Country name VARCSTR 25 0 0 yes

7 CREATED_BY Application username who created vendor site record VARCSTR 100 0 0 yes


9 FREIGHT_TERMS_CODE Default freight terms type VARCSTR 25 0 0 yes

10 HOLD_ALL_PAYMENTS_FLAG

Indicates whether Oracle Payables should place allpayments for this supplier on hold VARCSTR 1 0 0 yes

11 INACTIVE_DATE Inactive date for record DATE 24 0 9 yes



14 ORG_ID Operating unit unique identifier DECIMAL 48 15 0 yes

15 ORG_NAME Translated name of the organization VARCSTR 60 0 0 yes

16 PAYMENT_TERM_ID Payment terms unique identifier DECIMAL 48 28 7 yes





Nullable

17 PAYMENT_TERM_NAME Name of payment term VARCSTR 50 0 0 yes

18 PAY_ON_CODE When to create an invoice VARCSTR 25 0 0 yes

19 PAY_SITE_FLAG Indicates whether you can send payments to this site(Y/N) VARCSTR 1 0 0 yes

20 PHONE Phone number VARCSTR 15 0 0 yes

21 PROVINCE Province VARCSTR 150 0 0 yes

22 PURCH_SITE_FLAG Indicates whether you can purchase from this site(Y/N) VARCSTR 1 0 0 yes

23 RFQ_ONLY_SITE_FLAG Indicates whether you can only send RFQs to thissite VARCSTR 1 0 0 yes

24 SITE_PAY_GRP_CODE Payment group type (PAY GROUP LOV type) VARCSTR 25 0 0 yes

25 SITE_PAY_GRP_NAME Values for PAY GROUP LOV type (Payment groupthe supplier belongs to) VARCSTR 80 0 0 yes

26 SITE_PAY_PRIORITY Payment priority for Supplier Site DECIMAL 48 28 7 yes

27 STATE State name or abbreviation VARCSTR 150 0 0 yes

28 VENDOR_ID Supplier unique identifier DECIMAL 48 28 7 yes

29 VENDOR_NAME Supplier name VARCSTR 80 0 0 yes

30 VENDOR_NUMBER Supplier number VARCSTR 30 0 0 yes

31 VENDOR_SITE_CODE Site code name VARCSTR 15 0 0 yes

32 VENDOR_SITE_ID PK Supplier site unique identifier DECIMAL 48 28 7 no

33 VENDOR_SITE_NAME Concatenated from Vendor Name and Vendor SiteCode VARCSTR 200 0 0 yes





Nullable

34 ZIP Postal code VARCSTR 20 0 0 yes


Documents

BusinessObjects Projects Rapid Mart for Oracle ...s3.amazonaws.com/zanran_storage/help.sap.com/ContentPages/...Contents 4 BusinessObjects Projects Rapid Mart for Oracle Applications