xi3 rm sap pm ug en

SAP BusinessObjects Plant Maintenance Rapid Mart XI 3.2, version for SAP solutions - User Guide

Version 12.2.0.0

October 2009

Copyright © Copyright 2009 SAP AG. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Trademarks All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries. Business Objects is an SAP company.All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

ContentsChapter 1 Introduction 11

What is a Rapid Mart? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Rapid Marts packages accelerate Time to Value . . . . . . . . . . . . . . . . 13SAP BusinessObjects Rapid Marts packages architecture . . . . . . . . . 14

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

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

Sharing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Where the Rapid Mart fits in the maintenance process . . . . . . . . . . . . . . . 25

Chapter 3 Subject Areas 27Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Plant Maintenance Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Technical Objects & Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Classification & Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Maintenance Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Service Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Service Order Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Service Notification Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

SAP BusinessObjects Plant Maintenance Rapid Mart XI 3.2 for SAP solutions User Guide 3

Contents

Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Service Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Service Operation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Service Confirmation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Service Order Cost Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Service Master Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Chapter 4 Reports 81Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Service Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

MTBR MTTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Service Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Service Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Service Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

4 SAP BusinessObjects Plant Maintenance Rapid Mart XI 3.2 for SAP solutions User Guide

Contents

Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Service Order Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Service Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

SAP Master Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Chapter 5 Universe 165Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Universe Design Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Universe Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Universe Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Join Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Hierarchies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Geographic Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Time Dimension and Fiscal Period Hierarchies . . . . . . . . . . . . . . . . . 173Material Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Horizontal & Vertical Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Hierarchy Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

Plant Maintenance Specific Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . 185Accounting Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Additional Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

SAP Plant Maintenance Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Common Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Service Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203


Contents

Service Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Service Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Service Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Service Cost Summary (Horizontal) . . . . . . . . . . . . . . . . . . . . . . . . . . 216Service Cost Summary (Vertical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219MTBR and MTTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Filters & Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

SAP Service Master Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229SAP Service Master Universe Objects & Classes . . . . . . . . . . . . . . . 230SAP Service Master Common Dimensions . . . . . . . . . . . . . . . . . . . . . 231Equipment Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Functional Location Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 239SAP Service Master Filters & Techniques . . . . . . . . . . . . . . . . . . . . . 241SAP Service Master Universe Validation . . . . . . . . . . . . . . . . . . . . . . 242

SAP Master Data Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Universe Objects & Classes - Master Data . . . . . . . . . . . . . . . . . . . . . 244Universe Validation - Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Customizing the Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281Splitting the SAP Plant Maintenance Universe . . . . . . . . . . . . . . . . . . 281

Chapter 6 Installing the Rapid Mart 283Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285Personnel Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286Rapid Mart product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287Preparing your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

Preparing Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289Preparing Target Database Environment . . . . . . . . . . . . . . . . . . . . . . 289Preparing Source Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290Preparing BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . 290


Contents

Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290The Rapid Mart Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292Install the Rapid Mart Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

Create Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293Install the Data Services Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

Renaming the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296Import ATL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298Adjusting the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300Using Auxiliary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307Using ABAP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Installing Rapid Mart Reporting Content . . . . . . . . . . . . . . . . . . . . . . . . . 314Import Wizard for Reporting Content BIAR File . . . . . . . . . . . . . . . . . 314Creating Universe Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

Chapter 7 Using the Rapid Mart 333Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334Recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Data Services automatic recovery feature . . . . . . . . . . . . . . . . . . . . . 334Rapid Mart recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

Execution status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336The execution status table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336The execution status API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337Executing a job with the Reset option . . . . . . . . . . . . . . . . . . . . . . . . 338

Extraction, transformation and loading process . . . . . . . . . . . . . . . . . . . . 338Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

Global Variable Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 340Used in All Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344Used in 2 to 10 Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347Used in Only 1 Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353Setting Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

Executing the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371Initial (First) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371


Contents

Incremental (Delta) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . 372Customizing the Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

Chapter 8 Technical Implementation 377Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378Service Notification Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

Initial load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381Incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

Service Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

Service Operation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

Service Confirmation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Service Order Cost Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

Service Master Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402Characteristics Stage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Dimensions with Incremental Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Functional Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Rolling Totals Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406Optimization Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

Table Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416Data Transfer Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418Hierarchy Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419


Contents

Dealing with NULL values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422Fact Table Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Fiscal Periods & Time Dim Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

Chapter 9 Documentation References 427Data Services Documentation References . . . . . . . . . . . . . . . . . . . . . . . 428BusinessObjects Enterprise Documentation References . . . . . . . . . . . . 428

Appendix A Rapid Mart Data Schema 431


Contents


Introduction

chapter

IntroductionWhat is a Rapid Mart?1
What is a Rapid Mart?
SAP BusinessObjects Rapid Marts packages are blueprints for building data marts with SAP BusinessObjects technology: • Data Services• Universe Designer• Web Intelligence. Rapid Marts packages deliver jump-start ETL (extract, transform & load) mappings, schema, and initial reporting content, accelerating the deployment of BI (business intelligence) for enterprise applications from SAP, PeopleSoft, Oracle, and Siebel. Each Rapid Mart is designed to address the reporting needs of a specific business area (or department) like accounting, sales, or purchasing. A component-based framework allows conducting analysis across these selected business areas by combining different packages within the same source application suite.Rapid Marts focus on basic standard configuration of the enterprise applications. They are country and industry neutral templates meant to be easily modified and extended to suit customer specific application implementation and reporting needs.Rapid Marts incorporate best practices, and provide easily modifiable templates. With Rapid Marts total development time of a data mart solution is greatly reduced.Each customer situation is different. You will probably encounter one or more of these:• Customizations you have made to SAP solutions the Rapid Mart does not

cover. • Standard SAP solutions data fields important for your specific business,

but not included in the Rapid Mart templates.• Optimization and performance challenges unique to your environment. • Reporting requirements not covered within the Rapid Mart template

reports.Rapid Marts are flexible templates that you can adjust to account for these unique situations. It is expected that some customization and optimization will be needed to suit your individual environment. Rapid Marts are not an out-of-the-box solution.


IntroductionWhat is a Rapid Mart? 1

BI tools and analytic tools can access Rapid Mart data through SQL queries. 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 your business with an accelerated time to value through rapid BI deployments because you can implement them quickly and easily customize them to meet specific analytic requirements.

Rapid Marts packages accelerate Time to ValueRapid Marts are packaged data solutions that you can quickly deploy to address specific areas of business analysis. Available Rapid Marts packages for SAP solutions include:Financial Suite:• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP

solutions• SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP

solutions• SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutionsOperational Suite:• SAP BusinessObjects Inventory Rapid Mart, version for SAP solutions • SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions• SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsManufacturing Suite:• SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP

solutions • SAP BusinessObjects Production Planning Rapid Mart, version for SAP

solutions • SAP BusinessObjects Project Systems Rapid Mart, version for SAP

solutionsHuman Capital Management (HCM) Suite:• SAP BusinessObjects Human Resources Rapid Mart, version for SAP

solutions


IntroductionWhat is a Rapid Mart?1

You can combine multiple Rapid Marts packages into a single environment to build the foundation for your data warehouse or use them as a staging area for business intelligence applications.

SAP BusinessObjects Rapid Marts packages architectureRapid Marts architecture is driven by SAP BusinessObjects technology.Rapid Mart Architecture:

Rapid Marts packages include the following components:


IntroductionWhat is a Rapid Mart? 1

• Data Movement Jobs - packaged source-to-target mappings and data transformations. Each job is designed to perform initial and incremental data movement;

• Data Model & Schema - set of data mart database objects designed with dimensional data modeling approach. Rapid Marts packages for SAP solutions has a single integrated data model. The schema are available for Oracle, SQL Server IBM DB2, and Teradata;

• Semantic Layer (Universes) - SAP BusinessObjects metadata packages for efficient query generation. There can be one or more universes per Rapid Mart. Each universe is developed using Rapid Marts design principles to ensure compatibility, code readability, and component re-use. In addition, there is one Master universe for development/maintenance of multiple use objects (like Customer, Material, Currency, etc.);

• Reports (Samples) - set of 15-20 Web Intelligence reports per Rapid Mart. They represent answers to mostly asked business questions (for example, in the SAP BusinessObjects Sales Rapid Mart, version for SAP solutions - 'What is the monthly Revenue trend by Division for this year?'). The reports are developed using Rapid Mart color/layout templates. Reports are examples of Web Intelligence best practice development (trends, listing, guided analysis, roll ups and downs, etc.).


IntroductionAbout this document1
About this document
This document describes the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions. 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 reports you can create with the Rapid Mart, and how to use and update the Rapid Mart.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 the Rapid Mart, including the processes each section captures

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

which the reports are built.• 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 considerations you need to make when customizing the Rapid Mart

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

• Chapter 9: Documentation References — Information about where to find related to the Rapid Mart technical documentation on Data Services and BusinessObjects Enterprise

• Appendix A: 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 SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions 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• SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP

solutions schema• Where the Rapid Mart fits in the maintenance process

What you can do with this Rapid MartThe SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions extracts data from the plant maintenance (PM) module of SAP solutions. You can use this data to analyze, manage, and plan issues related to plant maintenance. The SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions is made up of several components or sections. Each section supports a subject related to analysis of plant maintenance: • Notification — Stores data about maintenance notifications. Used for

planning, notifications inform the maintenance department about required tasks. Stored data includes information about maintenance tasks requested and completed at a plant, including damage, causes of damage, related actions, and system availability. This section includes mean-time-to-repair data and mean-time-between-repair data. Using the notification section, you can analyze the history of a piece of equipment or you can analyze functional location failures.

• Service Order — Stores data about maintenance Service Orders. This data includes information about the type of Service Order, the scope and deadlines, the required resources, and the accounting requirements. Using the Service Order section, you can analyze the backlog of work at each functional location.


OverviewSupported analyses 2

• Service Operation — Stores data about operations, the items or activities required by Service Orders. Using the operation section, you can analyze the backlog of work and the effectiveness of planning efforts.

• Service Confirmation — Stores data about confirmations, which document the actual time to complete maintenance on an item. Using the confirmation section, you can analyze employee performance, comparing estimated to actual time.

• Service Order Cost — Stores data about the cost (estimated, planned, and actual) to complete Service Orders. Using the Service Order cost section, you can analyze maintenance costs by functional location.

• Service Master — Allows you to explore the “characteristics” (configuration) associated with both Equipment and Functional Locations. Allows analysis where and how these characteristics are used.

Chapter 3: Subject Areas discusses each of these sections in more detail and how to link them together for complete analysis of plant maintenance.

Supported analyses The SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions supports several types of analyses.

Business function Type of analysis Measures available in the Rapid Mart

Technical Objects (Equipment or Functional Location)

Equipment Reliability • Equipment and components that require most frequent maintenance work

• Maintenance ranking by manufacturer, vendor, or year of production

Classification • Technical object analysis by selected characteristics and their values

• Grouping by functional location and equipment class

Object history • Life time performance of a piece of equipment

Service Orders Maintenance hours • Straight time versus overtime ratio• Internal versus external labor analysis• Backlog maintenance hours by order

Operational Analysis • Operational analysis by company, plant, material group, etc.


OverviewSupported analyses2

To support these analyses, the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions includes a number of dimension tables. Tables extracted from SAP solutions master data and customizable tables include enterprise entities, such as plant, work center, vendor, material, currency, country, activity type, and material movement type data. Tables extracted from the PM module include functional location and equipment, their classification and hierarchies, organizational elements (for example, planner group or personnel), notification catalogs, and notification and order types.

Confirmations • confirmation performance by Activity, Company Code, fiscal year, etc.

Planning efficiency • Variance between actual and forecast work by planning group

• Ratio of scheduled versus completed orders

• Order execution by priorityMaintenance costs • Yearly cost trends by category

• Detailed estimated/planned/actual costs by technical objects

• Total actual revenue• Planned versus actual costs by labor and

materialNotifications Failures • Damage analysis by technical object

• Downtime by functional location and responsible party

• System conditionsMTBR and MTTR • Time between repairs

• Average time between repair• Time to repair• Average time to repair

Business function Type 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 work flow 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.Components of the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions are related to other SAP BusinessObjects Rapid Mart components. For example: • Material movements are found in the SAP BusinessObjects Inventory

Rapid Mart, version for SAP solutions.• Reservations, and Production Orders are found in the SAP

BusinessObjects Production Planning Rapid Mart, version for SAP solutions.

• Common dimensions are shared across all Rapid Marts.

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 Services 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 SAP solutions. For more information about the “execute once” feature, see the Data Integrator/Data Services Designer Guide.Each of the sections listed in “What you can do with this Rapid Mart” on page 18 are considered components. You can identify a component within a Data Services job by a “C_” prefix before its name. For example, the component that contains Service Orders and the associated reporting dimensions is named C_ServiceOrder_Section.


OverviewSAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema2
SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema
The following diagrams show an overview of the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions components and their relationships. The first diagram shows the Fact Tables and Dimensions in a Star Schema Format.Plant Maintenance Rapid Mart Schema (1 of 3):


OverviewSAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema 2

The second diagram shows the associated hierarchies for the Plant Maintenance Rapid Mart:Plant Maintenance Rapid Mart Schema (2 of 3):

The third and final diagram shows the Auxiliary and Staging tables used by the Rapid Mart.


OverviewSAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema2

Plant Maintenance Rapid Mart Schema (3 of 3):


OverviewWhere the Rapid Mart fits in the maintenance process 2

Where the Rapid Mart fits in the maintenance process

In SAP solutions, the maintenance process cycle has five steps: • Notification — Notifies the factory of periodic maintenance, upgrade,

damage, malfunction, problem etc. in a Functional Location or Equipment. This is the maintenance request.

• Service Order — A Service (maintenance) Order is created on the basis of the maintenance request

• Service Operation — The work is planned (operations specified, routing determined, materials reserved or ordered, work hours and personnel determined).

• Service Confirmation — The Service Order captures actual time duration for maintenance performed vs. planned (forecast). Technical information is entered to document the repair and to record the condition of the Equipment or Functional Location.

• Service Costs — The results of settling the Service Order in the controlling module (CO). Captures material and labor costs vs. forecast for the Service Order.

• Master Data — (The Equipment and Functional Location Characteristics) Technical information about the various Equipment and Functional Locations. This includes such items as configuration, options, and versions (revisions levels) installed on an equipment or in a functional location. These are used as reference data throughout the Plant Maintenance process.

The SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions captures this entire process, as shown in the diagram below.


OverviewWhere the Rapid Mart fits in the maintenance process2

Plant Maintenance Process:.


Subject Areas

chapter

Subject AreasOverview3
Overview
Each section in the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions 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 to design and support a real-time system, such as a Web application, and need to understand the data in the Rapid Mart and how it relates to SAP solutions. This chapter discusses: • Plant Maintenance Process Overview• Service Notification Section• Service Order Section• Service Operation Section• Service Confirmation Section• Service Order Cost Section• Service Master Section


Subject AreasPlant Maintenance Process Overview 3

Plant Maintenance Process OverviewPlant Maintenance comprises the following activities:• Preventive maintenance - All measures which maintain the ideal

condition of a technical system• Repair - All measures which restore the ideal condition of a technical

system• Other measures - Taken using the maintenance organization, such as

upgrades or implementation of special features on the technical system. These are often optional components on the technical objects.

IntegrationThrough integration with other modules (for example, Materials Management, Production, Sales and Distribution, Personnel Management, and Controlling) the data is always kept current and processes that are necessary for Plant Maintenance and Customer Service are automatically triggered in other areas (for example, a purchase requisition for non-stock material in the Materials Management/Purchasing area).

Technical Objects & SystemsTechnical Objects are the subjects of maintenance activities. They are composed of two separate types:Functional Location - A component in a technical system on which a maintenance task is performed.Equipment - A physical object that is maintained as an autonomous unit.Technical objects are maintained in SAP solutions with separate master records.A Technical System is composed of these two types of technical objects. If you want to represent part of a technical system as a technical object, you can set up hierarchies of both functional locations and equipment. Equipment can be assigned to a functional location, thus merging the two hierarchies.Example: A Water Filtration Company.The company itself represents the top level of a functional location hierarchy.Subsidiary functional locations in the company can be the various filtration plants it owns or operates. Pumping stations in a filtration plant form the next level down in the functional location hierarchy.


Subject AreasPlant Maintenance Process Overview3

Individual pumps (installed as equipment) form the next level down. Finally, a pump may be composed of individual components forming an equipment hierarchy.Here’s how the structure would look:Filtration Company (Top Level, Functional Location Hierarchy)• Plant 1

• Pump Station 1• Pump 1 (equipment)• Pump 2 (equipment)

• Pump Station 2• Pump 3 (equipment)• Pump 4 (equipment)

• Plant 2, etc...Pump 1 (Top Level, Equipment Hierarchy)• Pump Housing

• Motor• Power supply• Gear box

• Piping• Filters

• Holding tank• Inlet valve• Outlet valve

Pump 2 (Top Level, Equipment Hierarchy), etc...In the Rapid Mart, both the Equipment and Functional Location Hierarchies are fully represented as dimensions to the various fact tables and subject areas.

Classification & CharacteristicsWhen you are managing a large number of technical objects, you must be able to group these objects according to particular features. In this way, you can logically organize them according to various criteria, find them easily, and group them together when performing analyses.Using the Classification System you can create a hierarchically structured classification system for your company. Then you can assign Characteristics to the classification, and to the various technical objects.



This is particularly useful in tracking features that can cut across the equipment and functional location hierarchies.For example, the revision level of certain firmware on a common mother board. The mother board is used on several different computer lines your company uses. Thus, the boards and computers purchased at different times would have different revision levels of the firmware. Furthermore, as computers are upgraded the revision level can change again.A classification and characteristic hierarchy could be used to track the different revision levels, firmware, firmware families, etc. This is independent of which equipment or functional locations (or their hierarchies) they may be associated with. The end result is that an equipment or functional location can have associated Classification and Characteristics that describe certain attributes that may be shared with other similar equipment or functional locations. The Rapid Mart this allows you to analyze characteristic master data in the Equipment Characteristics and Functional Location Characteristics subject areas. See “Service Master Section” on page 74 for more details.

Maintenance NotificationsThese are called Service Notifications in the Rapid Mart. Notifications are created in the event of a malfunction or exceptional situation encountered in plant maintenance. They • Describe the exceptional technical condition at an object, such as the

symptoms of a malfunction.• Request the maintenance department to perform a necessary task, such

as an upgrade on certain equipment.• Document work that has been performed, such as troubleshooting the

malfunction.Maintenance notifications document maintenance tasks completely, and make them available for analysis in the long term. You can use them for preliminary planning and execution of tasks.The notification serves as the first step in the maintenance process. A notification is often linked with a Maintenance Order (called Service Order in the Rapid Mart).


Malfunction Catalogs
You use catalogs to manage, uniformly define, and standardize information (for example, defect types, follow-up actions, tasks) on a client-wide or plant-wide basis. The catalogs can help you to record and subsequently evaluate qualitative data, and to describe problems.In the catalogs, you assign each unit of information a unique alphanumeric code and an explanatory text.You can use the catalogs to describe defect items, tasks, activities, and causes in maintenance notifications, or service notifications.SAP solutions compiles all the code groups for malfunction descriptions under one catalog type and all the code groups for causes of malfunction under another.Using catalog types ensures that only the relevant codes can be entered at particular stages in the maintenance notification:In the Rapid Mart, we’ve implemented three catalog types as distinct dimensions that are associated with the notifications.

In the Rapid Mart, Service Notification Section is the implementation of Maintenance Notifications. The section also contains a summary table designed to support calculation of:• MTBR = Mean (or Average) Time Between Repairs (also called up time)• MTTR = Mean (or Average) Time To Repair (also called down time)

Service OrdersMaintenance Orders (called Service Orders in the Rapid Mart) document the necessary steps to repair the malfunction, or to complete the tasks requested in the notification. They serve as a cost collector for material and labor charges. They also record the time spent in the maintenance activities.A technician on site must execute tasks at a technical object to satisfy the requests for repair or maintenance. For this, materials, utilities and staff must be planned and costs estimated. The service order supports you with these tasks, since it primarily contains data for planning and executing tasks, which must be performed at the technical object in question.

Catalog Type

Description Rapid Mart Dimension

5 Causes Malfunction CauseB Object parts Malfunction Object PartC Overview of damage Malfunction Damage



A service order is subdivided into operations and confirmations.

Service OperationsYou use operations to describe the individual maintenance tasks to be performed. The operation includes the time, the work center, and other controlling information for an individual maintenance task. In the operation text you can describe how the work should be done.In Plant Maintenance, the operation has the following tasks:• Determination of the capacity requirement• Specifying whether a task is performed by the company’s own staff

(internal processing) or by the staff of another company (external processing)

• Maintaining the status• Definition of deadlines at operation level• Specification of required spare parts and utilities (such as special tools)• Determination of the process flow (or order of work) when processing

multiple operations.

Service ConfirmationsA confirmation documents the status of the processing of operations for a maintenance or service order. It is a part of order monitoring. You use confirmations to document:• From which work center the operation was performed • Who performed the operation • That operations or sub-operations were started or executed • When the work was started and when it was completed • How the work is progressing • How high are the costs for internal processing • What materials were used • Which services were executed internally • What measurement or counter readings were entered for the technical

objects during or after execution • Whether and where pieces of equipment were dismantled from, or

installed at functional locations • The extent to which the order has been processed • Where additional capacity is needed and where surplus capacity can be

reduced



• Which technical data should be retainedConfirmations can also be used to track various time related activities in maintenance order processing, for example:• How long the work took and the period in which it occurred• How much longer work must continue• How much of the operation time was used (duration)• When is the operation expected to be completedConfirmations can be partial or final:Partial Confirmation

If confirmations have been entered for the operations/sub-operations of an order, but the processing has not yet been completed, the operations/sub-operations automatically receive the status "partially confirmed" from the system.

Final ConfirmationAs soon as all order operations/sub-operations, which are planned for a confirmation (the control key is the decisive factor), have been finally confirmed, the order itself also receives the status "finally confirmed".In the Rapid Mart,

• Service Order Section• Service Operation Section• Service Confirmation Section

are used to implement Service Orders fully.

Service Order CostsSAP solutions calculate planned costs after the resources and capacities are planned for that Service Order. As soon as service or maintenance work has begun and the first completion confirmations (for example, time confirmations, material withdrawals, and so on) have been entered, the order will begin to incur actual costs.The planned and actual costs are updated in the database table PMCO. The table is the link between Plant Maintenance and Controlling functions in SAP solutions. The data in this table is the basis of the Service Order Cost Section of the Rapid Mart.


Subject AreasService Notification Section 3

Service Notification SectionThe notification section extracts data about maintenance notifications. A maintenance notification informs the maintenance department that a task needs to be performed. Maintenance notifications store technical and statistical information about a maintenance object, such as:• Damage• Causes of damage• Actions carried out• Follow-up activities• System availability before, during, and after the malfunctionMaintenance departments might combine multiple notifications to form one Service Order. Maintenance departments use notifications for planning purposes.The SAP solutions system broadly categorizes notifications by Notification Category. The Rapid Mart includes all notifications with category = “01” (Plant Maintenance). You can easily customize the Rapid Mart to include other notification categories. Notification categories are predefined within SAP solutions.Each of the categories is subdivided into Notification Types. The Rapid Mart includes all notification types for category “01”. You can use the IMG (SAP solutions Implementation Guide) to configure notification types. Each notification can also have several line items that describe in greater detail the specifics of the notification.SAP solutions maintains notification catalogs that store information about damage, cause, and location (see “Malfunction Catalogs” on page 32). If data entry for these is timely and correct in SAP solutions, this information can be useful for failure analysis. However, missing information in these source tables can cause discrepancies in your analyses and reports.The notification section extracts data from the SAP solutions header and line item levels for each notification. The corresponding SAP solutions tables are:• QMIH - Quality Notification - maintenance header• QMEL - Quality Notification - general header• QMFE - Quality Notification - itemsThe target table in the Rapid Mart schema is NOTIFICATION_FACT.


Subject AreasService Notification Section3

The section also extracts data from SAP solutions to indicate status, such as in-progress, postponed, completed, or deleted. The notification section does not store the history of changes to the data and it does not extract information about activities and tasks.To support plant maintenance analysis, the section allows you to classify equipment and functional locations, and their hierarchies. Though notification items can be part of the classification system, the section does not extract class allocation data for notification items. Therefore, this version of the Rapid Mart does not allow you to classify notification items. However, the NOTIFICATION_FACT table does contain a field, OBJ_ID_CLASS, that captures the assignment of a notification item to classes and characteristics. You can use this as a link to classifications at the line item level when customizing the Rapid Mart.The section also contains a second fact table MTBR_MTTR_FACT that calculates:• MTBR = Mean (or Average) Time Between Repairs (also called up time)• MTTR = Mean (or Average) Time To Repair (also called down time)The NOTIFICATION_FACT table is extracted and populated from SAP solutions first. Then, NOTIFICATION_FACT serves as the source for MTBR_MTTR_FACT.The SAP solutions Plant Maintenance Information System (PMIS) only calculates MTBR and MTTR on a monthly basis. However, you can use data from the notification section to analyze MTBR and MTTR for any duration.

Rapid Mart processingThe section captures the following dimensional attributes and their associated dimension tables:

Attribute Name Dimension Tables

Business Area BUSINESS_AREAClassification Hierarchy CLASSIFICATION_HIER,

CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR

Company Code COMPANY_CODEControlling Area CONTROLLING_AREA



Cost Center & Hierarchy COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD

Equipment & Hierarchy EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR

Functional Location & Hierarchy FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER, FUNCTIONAL_LOCATION_HIER_HZ, FUNCTIONAL_LOCATION_HIER_VR

Internal Order & Hierarchy INTERNAL_ORDER, INTERNAL_ORDER_HIER, INTERNAL_ORDER_HIER_HZ, INTERNAL_ORDER_HIER_VR, INTERNAL_ORDER_HIER_BAD

Maintenance Priority MAINTENANCE_PRIORITYMalfunction Catalogs MALFUNCTION_CAUSE,

MALFUNCTION_DAMAGE, MALFUNCTION_OBJ_PART

Malfunction Effect MALFUNCTION_EFFECTMaterial & Product Hierarchy MATERIAL, PRODUCT_HIERARCHYMaterial By Plant MATERIAL_BY_PLANTNotification NOTIFICATIONNotification Category DOCUMENT_CATEGORYNotification Type DOCUMENT_TYPE &

DOCUMENT_CATEGORYPlanning Group PLANNING_GROUPPlant PLANTPlant Location PLANT_LOCATIONService Person SERVICE_PERSONTime Dimension TIME_DIM




Fact Table FieldsThe section contains the following measures. Note: The focus is on reporting durations, therefore most measures are in time units rather than monetary currency or quantities:

Unit Of Measure UNIT_OF_MEASUREWork Center & Hierarchy WORK_CENTER,

WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD


Fact Table Name Column Name Description

MTBR_MTTR_FACT DAYS_DOWNTIME Calculated Days of downtime (as Malfunction end - Malfunction start)

DAYS_UPTIME Calculated Days of uptime: Prev Malfunction end date - Malfunction start date

HOURS_DOWNTIME Calculated hours of downtime (as Malfunction end - Malfunction start)

HOURS_UPTIME Calculated hours of uptime: Prev Malfunction end date - Malfunction start date

MINS_DOWNTIME Calculated minutes of downtime (as Malfunction end - Malfunction start)

MINS_UPTIME Calculated minutes of uptime: Prev Malfunction end date - Malfunction start date

NOTIFICATION_FACT DAYS_COMPLT Number of Days to eliminate malfunction (calculated)

DAYS_DOWNTIME Number of malfunction days (calculated)

DAYS_REQ Number of Required days to fix malfunction (calculated)

HOURS_COMPLT Number of Hours to eliminate malfunction (calculated)

HOURS_DOWNTIME Number of malfunction Hours (calculated)

HOURS_REQ Number of Required Hours to fix malfunction (calculated)

MINS_COMPLT Number of Hours to eliminate malfunction (calculated)

MINS_DOWNTIME Number of malfunction Minutes (calculated)

MINS_REQ Number of Required Minutes to fix malfunction (calculated)

QTY_DOWNTIME QMIH-AUSZT - Downtime



Additionally, several “flags” are employed to capture notification status on the NOTIFICATION_FACT table:

Column Name Description

BREAKDOWN_FLAG EQIH-MSAUS - Breakdown indicator. Set to 1 if there is a breakdown

COMPLT_FLAG JEST-STAT (lookup) - NOCO notification completed status is active (1 is active, 0 is inactive)

IN_PROGRESS_FLAG JEST-STAT (lookup) - NOPR notification is progress status is active (1 is active, 0 is inactive)

OUTSTANDNG_FLAG JEST-STAT (lookup) - OSNO outstanding notification status is active (1 is active, 0 is inactive)

POSTPONE_FLAG JEST-STAT (lookup) - NOPO notification postponed status is active (1 is active, 0 is inactive)

ITEM_DELETE_FLAG QMFE-KZLOESCH - Indicator: delete data record. Set to 1 if an item is deleted

NOTIFICTN_DELETE_FLAG JEST-STAT (lookup) - DLFL notification completed status is active (1 is active, 0 is inactive)


Rapid Mart data
The following diagrams shows the tables in the notification section organized as a Star Schema:Notification Fact (1 of 2):



MTTR / MTBR Fact (2 of 2):

With the tables in this section, you can analyze maintenance notifications along several dimensions:• Business Area• Classification Hierarchy• Company Code• Controlling Area• Cost Center & Hierarchy• Document Category (Notification Category)• Document Type (Notification Type)• Equipment & Hierarchy



• Functional Location & Hierarchy• Internal Order & Hierarchy (Service Order & Hierarchy)• Maintenance Priority• Malfunction Catalogs (Cause, Damage, and Object Part)• Malfunction Effect• Material & Product Hierarchy• Material By Plant• Notification• Planning Group• Plant• Plant Location• Service Person• Time Dim• Unit Of Measure• Work Center & HierarchyYou can use this section to answer questions such as:• What is the maintenance history of this piece of equipment?• What is the mean time to repair (MTTR) and the mean time between

repairs (MTBR) for this functional location for the last 5 years by quarter?• How often was this equipment down during this year?• What kind of damage does this equipment suffer from most often?• How efficiently does the planner group work?• What are current breakdowns?• Are there any trends in malfunctions across a particular functional

location and associated hierarchy?• Do certain characteristics in the Classification Hierarchy cause more

breakdowns than others?• Are certain functional locations quicker to repair malfunctions than

others?• Which upgrades of technical objects generated the most subsequent

malfunctions?


Subject AreasService Order Section 3

Service Order SectionThe Service Order section extracts information about maintenance Service Orders. A maintenance Service Order includes information about its type, scope, deadlines, and the resources needed to fulfill a request for maintenance. Service Orders also include the accounting information needed to assign and settle the order. Service Orders are tools for planning work that needs to be done. Typical planning tasks include specifying operations, reserving spare parts, and determining work hours.In SAP solutions, Service Orders contain detailed planning information, including deadlines, costs, and technical facts. Maintenance Service Orders are created by:• Scheduling preventive maintenance• Converting maintenance notifications into a maintenance orders• Direct opening (without referring to a notification)Service Orders are also created to maintain elements of the equipment structure that are not yet detailed.The SAP solutions system broadly categorizes service orders by Order Category. The Rapid Mart includes all service orders with category = “30” (Maintenance order). You can easily customize the Rapid Mart to include other Order categories. Order categories are predefined within SAP solutions.However, keep in mind that the Service Order is a type of Internal Order. Internal Orders also include production orders, personnel orders, controlling orders, etc. These may not be appropriate for inclusion in the Plant Maintenance Rapid Mart. Each of the order categories is subdivided into Order Types. The Rapid Mart includes all order types for category “30”. You can use the IMG (SAP solutions Implementation Guide) to configure order types. Service Orders are identified by There are three basic types of maintenance Service Orders:• Maintenance order — An order created from a notification. Typically, a

maintenance order results in the creation of operations, reservations of spare parts, and the planning of work times.

• Preventive maintenance order — An order generated automatically according to a schedule.

• Refurbishment order (supported only in SAP solutions version 4.0 and higher) — An order to repair a technical object. A refurbishment order changes the object’s status from defective to refurbished. The refurbishment process changes the value of the technical object.


Subject AreasService Order Section3

The SAP solutions source tables for Service Orders are: • AFIH - Maintenance order header• AFKO - Order header data PP orders• AUFK - Order master data (general header data)The Service Order section extracts maintenance Service Order information from SAP solutions. The section stores header level data in the fact table SERVICE_ORDER_FACT. This fact table also indicates the status of the Service Order, such as released, partially confirmed, finally confirmed, technically completed, deleted, closed, or locked.SERVICE_ORDER_FACT includes only header level data. Additional information (at finer levels of detail) about Service Orders is captured in subsequent sections of this chapter: • Service Operation Section• Service Confirmation Section• Service Order Cost Section

Rapid Mart processingThis section captures the following dimensional attributes and their associated dimension tables:




Company Code COMPANY_CODEControlling Area CONTROLLING_AREACost Center & Hierarchy COST_CENTER,

COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD

Customer CUSTOMERDocument Category DOCUMENT_CATEGORYDocument Type DOCUMENT_TYPE &

DOCUMENT_CATEGORY




Functional Area & Hierarchy FUNCTIONAL_AREA, FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BAD,

Functional Location & Hierarchy

FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER, FUNCTIONAL_LOCATION_HIER_HZ, FUNCTIONAL_LOCATION_HIER_VR


Internal Order Status INTERNAL_ORDER_STATUSMaintenance Activity Type MAINTENANCE_ACTIVITY_TYPEMaintenance Priority MAINTENANCE_PRIORITYMaterial & Product Hierarchy MATERIAL, PRODUCT_HIERARCHYMaterial By Plant MATERIAL_BY_PLANTMonetary Currency CURRENCYNotification NOTIFICATIONPlanning Group PLANNING_GROUPPlant PLANTPlant Location PLANT_LOCATIONProfit Center & Hierarchy PROFIT_CENTER,

PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD

Project Element & Hierarchy PROJECT_ELEMENT, PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ, PROJECT_ELEMENT_HIER_VR, PROJECT_ELEMENT_HIER_BAD

Service Person SERVICE_PERSON




Fact Table FieldsThe SERVICE_ORDER_FACT table contains the following measures.Note: The focus is on reporting durations, therefore measures are in time units rather than monetary currency or quantities:

System Condition SYSTEM_CONDITIONTime Dimension TIME_DIMWork Center & Hierarchy WORK_CENTER,




DAYS_COMPLT_ACTL Number of Days to actually complete a service order (calculated)

DAYS_COMPLT_BASIC Number of Days to Basic complete a service order (calculated)

DAYS_COMPLT_FCST Number of Forecast Days to complete a service order (calculated)

DAYS_COMPLT_SCHED Number of Days scheduled to complete a service order (calculated)

DAYS_RELEASE_ACTL Number of Days to actually release a service order (calculated)

DAYS_RELEASE_SCHED Number of Days scheduled to release a service order (calculated)

HOURS_COMPLT_ACTL Number of Hours to actually complete a service order (calculated)

HOURS_COMPLT_BASIC Number of Hours to Basic complete a service order (calculated)

HOURS_COMPLT_FCST Number of Forecast Hours to complete a service order (calculated)

HOURS_COMPLT_SCHED Number of Hours scheduled to complete a service order (calculated)

MINS_COMPLT_ACTL Number of Minutes to actually complete a service order (calculated)



The measures are based on different calculations between date fields on the SERVICE_ORDER_FACT table:

Additionally, several “flags” are employed to capture status on the SERVICE_ORDER_FACT table:

MINS_COMPLT_BASIC Number of Minutes to Basic complete a service order (calculated)

MINS_COMPLT_FCST Number of Forecast Minutes to complete a service order (calculated)

MINS_COMPLT_SCHED Number of Minutes scheduled to complete a service order (calculated)


ACTL_END_DATE AFKO.GETRI - Confirmed order finish dateACTL_RELEASE_DATE AFKO-FTRMI - Actual release date (Last

Operation is Released)ACTL_START_DATE AFKO-GSTRI - Actual start date (First

Operation is Started)BASIC_END_DATE AFKO-GLTRP - Finish (basic) dateBASIC_START_DATE AFKO-GSTRP - Order (basic) start dateFCST_END_DATE AFKO.GLTPP - Finish date (forecast)FCST_SCHED_END_DATE AFKO.GLTPS - Scheduled forecast finishFCST_SCHED_START_DATE AFKO.GSTPS - Scheduled forecast startFCST_START_DATE AFKO.GSTPP - Forecast start dateSCHED_END_DATE AFKO-GLTRS - Scheduled finishSCHED_RELEASE_DATE AFKO-FTRMS - Scheduled release dateSCHED_START_DATE AFKO-GSTRS - Scheduled start


BLOCK_FLAG JEST-STAT (lookup) - LKD order is locked status is active (1 is active, 0 is inactive)

CLOSE_FLAG JEST-STAT (lookup) - CLSD order is closed status is active (1 is active, 0 is inactive)

DELETE_FLAG JEST-STAT (lookup) - DLFL order is deleted status is active (1 is active, 0 is inactive)




Rapid Mart dataThe following diagram shows the tables in the Service Order section organized as a Star Schema.

FINAL_CONFIRM_FLAG JEST-STAT (lookup) - CNF order is finally confirmed status is active (1 is active, 0 is inactive)

PARTL_CONFIRM_FLAG JEST-STAT (lookup) - PCNF order is partially confirmed status is active (1 is active, 0 is inactive)

RELEASE_FLAG JEST-STAT (lookup) - REL order is released status is active (1 is active, 0 is inactive)

TECHN_COMPLT_FLAG JEST-STAT (lookup) - TECO order is technically completed status is active (1 is active, 0 is inactive)




Service Orders:.


Analysis
With the tables in this section, you can analyze Service Orders along several dimensions:• Business Area• Classification Hierarchy• Company Code• Controlling Area• Cost Center & Hierarchy• Customer• Document Category• Document Type• Equipment & Hierarchy• Functional Area & Hierarchy• Functional Location & Hierarchy• Internal Order & Hierarchy• Internal Order Status• Maintenance Activity Type• Maintenance Priority• Material & Product Hierarchy• Material By Plant• Monetary Currency• Notification• Planning Group• Plant• Plant Location• Profit Center & Hierarchy• Project Element & Hierarchy• Service Person• System Condition• Time Dimension• Work Center & Hierarchy


Subject AreasService Operation Section 3

You can use this section to answer questions such as:• What is the ratio between preventive and emergency orders or preventive

and predictive orders?• What is the mean time between repair for this equipment type for the last

5 years?• What is a scheduling efficiency on the plant maintenance department?• What is the most frequent type of malfunction to this system?• How efficiently does the planner group work?• How may Service Orders are blocked from completion?• Are there any trends in malfunctions across a particular functional

location and associated hierarchy?• Do certain characteristics in the Classification Hierarchy cause more

breakdowns than others?• Are certain functional locations quicker to repair malfunctions than

others?• Which upgrades of technical objects generated the most subsequent

malfunctions?• Which service orders are only partially confirmed and more than 6

months old?• Is there a trend by functional location on partially confirmed orders more

than 6 months old?

Service Operation SectionThe Service Operation section extracts information about operations. An operation is an activity in a work-step of the Service Order. Operations are items in a Service Order. The operation section extracts operation level data from these SAP solutions tables:• AFVC - Operation within an order• AFVV - DB structure of the quantities/dates/values in the operationThe section stores the data in the fact table SERVICE_OPERATION_FACT. This fact table also indicates the status of the Service Order, such as released, partially confirmed, finally confirmed, technically completed, deleted.Note: The SERVICE_OPERATION_FACT table also includes several attributes also found in the Service Order section. You can use these header level attributes in operation level analysis and reporting. Additionally, just like Service Orders, only operations with Order Category = “30” are included.


Subject AreasService Operation Section3
Rapid Mart processing
This section captures the following dimensional attributes and their associated dimension tables:


Activity & Hierarchy ACTIVITY, ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD

Business Area BUSINESS_AREAChart Of Accounts CHART_OF_ACCOUNTSClassification Hierarchy CLASSIFICATION_HIER,


Company Code COMPANY_CODEControl Key CONTROL_KEYControlling Area CONTROLLING_AREACost Center & Hierarchy COST_CENTER,


Cost Element & Hierarchy COST_ELEMENT, COST_ELEMENT_HIER, COST_ELEMENT_HIER_HZ, COST_ELEMENT_HIER_VR, COST_ELEMENT_HIER_BAD

Customer CUSTOMEREquipment & Hierarchy EQUIPMENT, EQUIPMENT_HIER,

EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR


Functional Location & Hierarchy FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER, FUNCTIONAL_LOCATION_HIER_HZ, FUNCTIONAL_LOCATION_HIER_VR




Maintenance Activity Type MAINTENANCE_ACTIVITY_TYPEMaintenance Priority MAINTENANCE_PRIORITYMaterial & Product Hierarchy MATERIAL, PRODUCT_HIERARCHYMaterial By Plant MATERIAL_BY_PLANTMonetary Currency CURRENCYNotification NOTIFICATIONObject Class OBJECT_CLASSObject Type OBJECT_TYPEOperation Suitability OPERATION_SUITABILITYPlanning Group PLANNING_GROUPPlant PLANTPlant Location PLANT_LOCATIONProfit Center & Hierarchy PROFIT_CENTER,



Service Order Category DOCUMENT_CATEGORYService Order Type DOCUMENT_TYPE &

DOCUMENT_CATEGORYSystem Condition SYSTEM_CONDITIONTime Dimension TIME_DIMUnit Of Measure UNIT_OF_MEASUREVendor VENDOR




Fact Table FieldsThe section contains the following measures.Note: To report durations, measures are in time units rather than monetary currency or quantities:

Vendor By Company VENDOR_BY_COMPANYWork Center & Hierarchy WORK_CENTER,



AMT_COST_MTRL AFVC.MAT_PRKST - Material planning in networks: primary costs

AMT_COST_TTL AFVC.PRKST - Total Costs in the activity - Planned

DAYS_EXECUTN_ACTL Calculated Days of Operation execution/startup time (as Actual Start and Actual End datetime)

DAYS_EXECUTN_SCHED Calculated Days of Operation execution/startup time (as Sched Start and Sched End datetime)

HOURS_EXECUTN_ACTL Calculated Hours of Operation execution/startup time (as Actual Start and Actl End datetime)

HOURS_EXECUTN_SCHED Calculated Hours of Operation execution/startup time (as Sched Start and Sched End datetime)

MINS_EXECUTN_ACTL Calculated minutes of Operation execution/startup time (as Actual Start and Actual End datetime)

MINS_EXECUTN_SCHED Calculated minutes of Operation execution/startup time (as Sched Start and Sched End datetime)

QTY_DURTN AFVV.DAUNO - Normal duration of the activity

QTY_WORK_ACTL AFVV-ISMNW - Actual work




The following dates are used for duration calculations:

Additionally, several “flags” are employed to capture status on the SERVICE_OPERATION_FACT table:

QTY_WORK_FCST AFVV-ORMNW - Forecasted work (actual + remaining)

QTY_WORK_SCHED AFVV-ARBEI - Work involved in the activity


ACTL_END_DATE AFVV-IEDD - Actual finish: Execution (date) + AFVV-ISDZ - AFVV-IEDZ - Actual finish: Execution (time)

ACTL_START_DATE AFVV-ISDD - Actual start: Execution (date) + AFVV-ISDZ - Actual start: Execution/setup (time)

SCHED_END_DATE AFVV.FSEDD - Earliest scheduled finish: Execution (date) + AFVV.FSEDZ - Earliest scheduled finish: Execution (time)

SCHED_START_DATE AFVV.FSAVD - Earliest scheduled start: Execution (date) + AFVV.FSAVZ - Earliest scheduled start: Execution (time)


COMPLT_FLAG AFVC-LEKNW - Indicator showing no remaining work expected if set to 1

COSTNG_FLAG AFVC.SELKZ - Selection indicator for costing line items

DELETE_FLAG JEST-STAT (lookup) - DEL operation is deleted status is active (1 is active, 0 is inactive)

FINAL_CONFIRM_FLAG JEST-STAT (lookup) - CNF operation is finally confirmed status is active (1 is active, 0 is inactive)

PARTL_CONFIRM_FLAG JEST-STAT (lookup) -PCNF operation is partially confirmed status is active (1 is active, 0 is inactive)




RELEASE_FLAG JEST-STAT (lookup) - REL operation is released status is active (1 is active, 0 is inactive)

TECHN_COMPLT_FLAG JEST-STAT (lookup) - TECO operation is technically completed status is active (1 is active, 0 is inactive)




Rapid Mart dataThe following diagram shows the tables in the Service Operations section organized as a star schemaService Operations:


Analysis
With the tables in this section, you can analyze maintenance Service Orders along several dimensions:• Activity & Hierarchy• Business Area• Chart Of Accounts• Classification Hierarchy• Company Code• Control Key• Controlling Area• Cost Center & Hierarchy• Cost Element & Hierarchy• Customer• Equipment & Hierarchy• Functional Area & Hierarchy• Functional Location & Hierarchy• Internal Order & Hierarchy• Maintenance Activity Type• Maintenance Priority• Material & Product Hierarchy• Material By Plant• Monetary Currency• Notification• Object Class• Object Type• Operation Suitability• Planning Group• Plant• Plant Location• Profit Center & Hierarchy• Project Element & Hierarchy• Service Order Category• Service Order Type• System Condition• Time Dimension


Subject AreasService Confirmation Section 3

• Unit Of Measure• Vendor• Vendor By Company• Work Center & HierarchyYou can use this section to answer questions such as:• What is the ratio between preventive and emergency orders or preventive

and predictive orders?• What is the mean time between repair for this equipment type for the last

five years?• What is a scheduling efficiency on the plant maintenance department?• What is the most frequent type of malfunction to this system?• How efficiently does the planner group work?• What is the ratio between internal and external order processing?• What is the backlog in hours by order priority?• How may Service Operations are un-released?• Are there any trends in operations taking more than 10 days to complete

across a particular functional location and associated hierarchy?• Do operations for certain characteristics in the Classification Hierarchy

take longer than others?• Which upgrades of technical objects have the most steps (operations)?• Which service operations are only partially confirmed and more than 6

months old?• Is there a trend by functional location on partially confirmed operations

more than 6 months old?

Service Confirmation SectionThe confirmation section extracts information about Service Order Confirmations. A confirmation documents the actual time used to complete the maintenance cycle.In SAP solutions, there are three ways to confirm the time worked on a maintenance order:• Single-entry of times in a confirmation document for each operation• Multiple-entry by direct entry or by means of a list of operations• Cross-application time sheet (CATS)


Subject AreasService Confirmation Section3

SAP solutions sets a Service Order’s status to partially confirmed when at least one confirmation has been entered for an operation in that Service Order. SAP solutions sets a Service Order’s status to completely confirmed when all operations and sub operations in that Service Order have been confirmed.A confirmation cannot be changed, but can be cancelled or reversed if it contains wrong data.The confirmation section extracts confirmation information from the transactional confirmation table in SAP solutions:• AFRU - Order completion confirmationsNote that the section does not extract CATS data since SAP solutions does not store data for CATS. The section stores the extracted information in the fact table SERVICE_CONFIRMATION_FACT.Note: The SERVICE_CONFIRMATION_FACT table also includes several attributes also found in the Service Order section. You can use these header level attributes in confirmation level analysis and reporting. Additionally, just like Service Orders, only confirmations with Order Category = “30” are included.The section stores reversed confirmation work amounts as negative numbers to allow you to aggregate correctly on measures.

Rapid Mart processingThe section captures the following dimensional attributes and their associated dimension tables:


Activity & Hierarchy ACTIVITY, ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD

Business Area BUSINESS_AREACapacity CAPACITYClassification Hierarchy CLASSIFICATION_HIER,


Company Code COMPANY_CODEControlling Area CONTROLLING_AREA



Cost Center & Hierarchy COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD

Customer CUSTOMEREquipment & Hierarchy EQUIPMENT, EQUIPMENT_HIER,

EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR





Internal Order Status INTERNAL_ORDER_STATUSMaintenance Activity Type MAINTENANCE_ACTIVITY_TYPEMaintenance Priority MAINTENANCE_PRIORITYMaterial By Plant MATERIAL_BY_PLANTMaterial, Product Hierarchy MATERIAL, PRODUCT_HIERARCHYMonetary Currency CURRENCYNotification NOTIFICATIONOperation Suitability OPERATION_SUITABILITYPlanning Group PLANNING_GROUPPlant PLANTPlant Location PLANT_LOCATION




Fact Table FieldsThe SERVICE_CONFIRMATION_FACT table contains the following measures:

Profit Center & Hierarchy PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD



DOCUMENT_CATEGORYService Person SERVICE_PERSONSystem Condition SYSTEM_CONDITIONTime Dimension TIME_DIMUnit Of Measure UNIT_OF_MEASUREWork Center & Hierarchy WORK_CENTER,




DAYS_COMPLT_FCST Calculated Days to complete the operation (as Forecast end - Forecast start)

DAYS_EXECUTN Calculated days of execution (as Execution Start end - Execution start)

HOURS_COMPLT_FCST Calculated hours to complete the operation (as Forecast end - Forecast start)

HOURS_EXECUTN Calculated hours of execution (as Execution Start end - Execution start)

MINS_COMPLT_FCST Calculated minutes to complete the operation (as Forecast end - Forecast start)



The following dates are used for duration calculations:

Additionally, several “flags” are employed to capture status on the SERVICE_CONFIRMATION_FACT table:

MINS_EXECUTN Calculated minutes of execution (as Execution Start end - Execution start)

QTY_DURTN_ACTL AFRU.IDAUR - Actual duration for confirmation

QTY_WORK_ACTL AFRU-ISMNW - Actual work (ifthenelse function call)

QTY_WORK_REMAIN AFRU-OFMNW - Remaining work


EXECUTN_END_DATE AFRU-IEDD - Confirmed date for execution finish + AFRU-IEDZ - Confirmed time for Execution finish

EXECUTN_START_DATE AFRU-ISDD - Confirmed date for start of execution) + AFRU-ISDZ - Confirmed time for Execution start

FCST_END_DATE AFRU.PEDD - Forecast finish date of operation from confirmation) + AFRU.PEDZ - Forecast finish time of operation from confirmation


FINAL_CONFIRMATN_FLAG AFRU-AUERU - Indicator: Partial/final confirmation

NO_REMAIN_WORK_FLAG AFRU-LEKNW - Indicator showing no remaining work expected

POST_OPEN_RESERVATN_FLAG

AFRU.AUSOR - Post open reservations



Rapid Mart data
The following diagram shows some of the tables in the Service Confirmation section represented in Star Schema format.Service Confirmations:



AnalysisWith the tables in this section, you can analyze confirmations along several dimensions:• Activity & Hierarchy• Business Area• Capacity• Classification Hierarchy• Company Code• Controlling Area• Cost Center & Hierarchy• Customer• Equipment & Hierarchy• Functional Area & Hierarchy• Functional Location & Hierarchy• Internal Order & Hierarchy• Internal Order Status• Maintenance Activity Type• Maintenance Priority• Material By Plant• Material, Product Hierarchy• Monetary Currency• Notification• Operation Suitability• Planning Group• Plant• Plant Location• Profit Center & Hierarchy• Project Element & Hierarchy• Service Order Category• Service Order Type• Service Person• System Condition• Time Dimension• Unit Of Measure• Work Center & Hierarchy


Subject AreasService Order Cost Section3

You can use this section to answer questions such as:• What is the overtime expressed as a percentage of straight time?• How effectively do we use maintenance work centers?• What is the work load of our maintenance employees?•• Are there any trends in confirmations taking more than 10 days to

complete across a particular functional location and associated hierarchy?

• Do confirmations for certain characteristics in the Classification Hierarchy take longer than others?

• Which upgrades of technical objects have not been completed?• Which service confirmations are only partially confirmed and more than 6

months old?• Is there a trend by functional location on partially confirmed confirmations

more than 6 months old?

Service Order Cost SectionThe Service Order cost section extracts information about the cost (planned, and actual) to complete Service Orders. Each maintenance Service Order can include actual cost and an estimate of the cost to complete the Service Order. SAP solutions calculate planned costs after the resources and capacities are planned for that Service Order. Actual costs are posted at confirmation time, and can be analyzed after work is completed. SAP solutions supports cost analysis of plant maintenance at two levels:• Cost element level, through the controlling (CO) module• Value category level, through the plant maintenance (PM) moduleSAP solutions maintains a separate transactional table (PMCO) for posting plant maintenance costs. SAP solutions posts costs by value categories for the PM module and by cost elements for the CO module. Note: because the PM cost transactional table does not contain the data from the finance (FI) module journals, cost figures can differ for the same order if pooled from different cost transactional tables.The Service Order cost section extracts plant maintenance costs from SAP solutions table:

PMCO - Cost structure of maintenance order.


Subject AreasService Order Cost Section 3

In the target schema, the section stores these costs in • SERVICE_COST_SUMMARY_FACT_HZ - Costs in Horizontal Format• SERVICE_COST_SUMMARY_FACT_VR - Costs in Vertical FormatThe horizontal table carries one row per fiscal year with separate fields (columns) for values in each fiscal period in the year upto 16 periods.The vertical tables carries one row per fiscal period and fiscal year. Each row carries only the values for that fiscal year / period combination. The vertical table also computes rolling 16 period totals for plant maintenance costs.Each table facilitates a different form of analysis in the Rapid Mart.Note: The SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions only supports analysis of plant maintenance costs at the value category level. Use the SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions to analyze plant maintenance costs by cost elements and other cost characteristics.Note: The Service Cost section also includes several attributes also found in the Service Order section. You can use these header level attributes in cost analysis and reporting. Additionally, just like Service Orders, only cost records with Order Category = “30” are included.

Rapid Mart processingThis section captures the following dimensional attributes and their associated dimension tables:


Business Activity BUSINESS_ACTIVITYBusiness Area BUSINESS_AREAClassification Hierarchy CLASSIFICATION_HIER,


Company Code COMPANY_CODEControlling Area CONTROLLING_AREACost Center & Hierarchy COST_CENTER, COST_CENTER_HIER,

COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD

Equipment & hierarchy EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR



Financial Record Category FINANCIAL_RECORD_CATEGORYFinancial Record Type FINANCIAL_RECORD_TYPEFiscal Period FISC_PERIOD, FISC_PERIOD_STAGEFunctional Area & Hierarchy FUNCTIONAL_AREA,

FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BAD,




Maintenance Activity Type MAINTENANCE_ACTIVITY_TYPEMaintenance Priority MAINTENANCE_PRIORITYMaterial & Product Hierarchy MATERIAL, PRODUCT_HIERARCHYMaterial By Plant MATERIAL_BY_PLANTMonetary Currency CURRENCYPlant PLANTPlant Location PLANT_LOCATIONProfit Center & Hierarchy PROFIT_CENTER,




DOCUMENT_CATEGORY




Fact Table FieldsThe section contains the following measures:SERVICE_COST_SUMMARY_FACT_HZ:

System Condition SYSTEM_CONDITIONVariance Category VARIANCE_CATEGORYWork Center & Hierarchy WORK_CENTER,



Column Name SERVICE_COST_SUMMARY_HZ Description

AMT_CR_PER00_TRX PMCO-WRT00 - Period Credit value in ledger currency















AMT_CR_PER15_TRX PMCO-WRT15- Period Credit value in ledger currency


AMT_CR_QTR01_TRX PMCO-WRT00 through 03 - Quarter Credit value in ledger currency





SERVICE_COST_SUMMARY_FACT_VR


AMT_CR_YTD_TRX PMCO-WRT01 through 16 - Year Credit value in ledger currency

AMT_DR_PER00_TRX PMCO-WRT00 - Period Debit value in ledger currency

















AMT_DR_QTR01_TRX PMCO-WRT00 through 03 - Quarter Debit value in ledger currency




AMT_DR_YTD_TRX PMCO-WRT01 through 16 - Year Debit value in ledger currency

Column Name SERVICE_COST_SUMMARY_FACT_VR Description

AMT_CR_QTD_TRX PMCO-WRT01 through 16 - QTD Credit value in ledger currency

AMT_CR_TRX PMCO-WRT00 through WRT16 - Period Credit value in ledger currency. For Period 01 - cumulative of Per 00 and Per 01; for Per 12 - cumulative of Per 12 through Per 16

Column Name SERVICE_COST_SUMMARY_HZ Description



Rapid Mart dataThe following diagrams shows some of the tables in the Service Order cost section as Star Schemas.

AMT_CR_YTD_TRX PMCO-WRT01 through 16 - YTD Credit value in ledger currency

AMT_DR_QTD_TRX PMCO-WRT01 through 16 - QTD Debit value in ledger currency

AMT_DR_TRX PMCO-WRT00 through WRT16 - Period Debit value in ledger currency. For Period 01 - cumulative of Per 00 and Per 01; for Per 12 - cumulative of Per 12 through Per 16

AMT_DR_YTD_TRX PMCO-WRT01 through 16 - YTD Debit value in ledger currency

AMT_PER_BEGIN_TRX PMCO-WRT01 through 16 - Period begin balance value in ledger currency

AMT_PER_ROLLING_TRX Rolling Total Balance - Transaction Currency

AMT_PTD_TRX Period Beginning Balance - Transaction Currency

Column Name SERVICE_COST_SUMMARY_FACT_VR Description



Service Cost Section - Horizontal (1 of 2):



Service Cost Section - Vertical (2 of 2):

AnalysisWith the tables in this section, you can analyze Service Order costs along several dimensions:• Business Activity• Business Area• Classification Hierarchy• Company Code• Controlling Area• Cost Center & Hierarchy• Equipment & Hierarchy• Financial Record Category• Financial Record Type• Fiscal Period


Subject AreasService Master Section3

• Functional Area & Hierarchy• Functional Location & Hierarchy• Internal Order & Hierarchy• Maintenance Activity Type• Maintenance Priority• Material & Product Hierarchy• Material By Plant• Monetary Currency• Plant• Plant Location• Profit Center & Hierarchy• Project Element & Hierarchy• Service Order Category• Service Order Type• System Condition• Variance Category• Work Center & HierarchyYou can use this section to answer questions such as:• What is the ratio between estimated and actual costs by equipment class

for the last five years?• What is the percentage of internal labor cost in the overall cost for

maintenance of the technical system?• What is the curve of our plant maintenance cost for the last decade?

Service Master SectionThis section shows the two Technical Objects (Functional Location and Equipment) as master data joined to their Classification & Characteristic attributes as shown on page 30.This allows you to analyze the technical objects by the various characteristics assigned to them. It facilitates reporting across hierarchy and dimensional boundaries. You can use the information in this section to identify characteristic attributes that require special attention.Example: you can identify all equipment with a certain level of software revision (as captured by the characteristics) and plan for a mass upgrade of the software to a newer version.


Subject AreasService Master Section 3

The section contains two fact tables:• FUNCTIONAL_LOCATION_CHAR_FACT• EQUIPMENT_CHAR_FACTThese are populated by joining characteristics with either the functional location or equipment.The source tables in SAP solutions are• FUNCTIONAL_LOCATION_CHAR_FACT -

• IFLOT - Functional Location (Table)• ILOA - PM Object Location and Account Assignment• AUSP - Characteristic Values• CABN - Characteristics• TCLA - Class Types

• EQUIPMENT_CHAR_FACT - • EQUI - Equipment master data• ILOA - PM Object Location and Account Assignment• EQUZ - Equipment time segment• AUSP - Characteristic Values• CABN - Characteristics• TCLA - Class Types

The section runs these steps:1. Runs the components to load the Equipment and Functional Location

dimension tables (EQUIPMENT, FUNCTIONAL_LOCATION).2. The three characteristic tables (AUSP, CABN, and TCLA) are joined to

populate CHARACTERISTIC_STAGE table. The three characteristics tables are common to both fact tables.

3. The CHARACTERISTIC_STAGE table is joined with the EQUIPMENT table to produce EQUIPMENT_CHAR_FACT.

4. The CHARACTERISTIC_STAGE table is joined with the FUNCTIONAL_LOCATION table to produce FUNCTIONAL_LOCATION_CHAR_FACT.


Rapid Mart processing
This section also captures these dimensional attributes and their associated dimensions:




Company Code COMPANY_CODEControlling Area CONTROLLING_AREACost Center & Hierarchy COST_CENTER, COST_CENTER_HIER,

COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD




Material & Product Hierarchy MATERIAL, PRODUCT_HIERARCHYMaterial By Plant MATERIAL_BY_PLANTPlanning Group PLANNING_GROUPPlant PLANTPlant Location PLANT_LOCATIONService Person SERVICE_PERSONTime Dimension TIME_DIMUnit Of Measure UNIT_OF_MEASUREVendor VENDORVendor By Company VENDOR_BY_COMPANY



Fact Table FieldsThe section contains no measures of monetary amounts or quantities. However these fields are key for characteristic analysis, and are available in both fact tables:

Rapid Mart dataThe following diagrams show both fact tables and associated dimensions in Star Schema format:


CHARACTSTC_DESCR CABNT-ATBEZ (lookup) - Characteristic description

CHARACTSTC_FORMAT CABN-ATFOR - Characteristic data typeCHARACTSTC_ID AUSP-ATINN - Internal characteristicCHARACTSTC_NAME CABN-ATNAM (lookup) - Characteristic unique

nameCHARACTSTC_VALUE AUSP-ATWRT- Characteristic valueCLASS_TYPE_ID AUSP-KLART - Characteristic Class typeVALID_FROM_DATE AUSP.ATFLV - Derived Date from and Time

From bucketVALID_FROM_VALUE AUSP-ATFLV - Tolerance fromVALID_TO_DATE AUSP.ATFLB - Derive Date To and Time To

bucketVALID_TO_VALUE AUSP-ATFLB - Tolerance toVALUE_SCALE CABN-AMZDZ - Number of decimal places



Equipment Characteristics (1 of 2):

Functional Location Characteristics (2 of 2):



AnalysisYou can analyze Service Master data along several dimensions:• Business Area• Classification Hierarchy• Company Code• Controlling Area• Cost Center & Hierarchy• Equipment & Hierarchy• Functional Location & Hierarchy• Material & Product Hierarchy• Material By Plant• Planning Group• Plant• Plant Location• Service Person• Time Dimension• Unit Of Measure• Vendor• Vendor By CompanyTypical queries for this section include:• How many equipment have a certain characteristic with a certain value?• How many characteristic values have expired and need renewal in my

functional locations?• Which equipment are missing an important upgrade?• How often are we out of tolerance range for equipment characteristics?• Which plants are best /worst at keeping their equipment up to date


Reports

chapter

ReportsOverview4
Overview
You can use the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions to produce many kinds of reports. This chapter provides examples of reports you could produce. The information in this chapter is useful for those who analyze and produce reports with the Rapid Mart data.This chapter provides a sample report and the recommended joins for each componentized section in the Rapid Mart:• Service Notification• MTBR MTTR• Service Order• Service Operation• Service Confirmation• Service Order Cost• Service MasterSAP Master Data Reports are also described at the end of this chapter. These reports are common across all Rapid Marts and are intended for hierarchy discovery and record validation.

Service NotificationThe notification section extracts data about maintenance notifications. Notifications are created in the event of a malfunction or exceptional situation encountered in plant maintenance. They:• Describe the exceptional technical condition at an object, such as the

symptoms of a malfunction.• Request the maintenance department to perform a necessary task, such

as an upgrade on certain equipment.• Document work that has been performed, such as troubleshooting the

malfunction.

ReportsSample Reports for the Notifications include:• Notification Listing• Notification Details


ReportsService Notification 4

• Notification Statistics• Equipment Failures Analysis

Notification ListingView Notification Listing and detail information for the selected Company Code, Calendar Year, and Calendar Month(s) of the Notifications. Includes a hyperlink on Notification Id to Notification Details report.

ListingView notification listing. Notification Id is a hyperlink to the Notification Details report.


ReportsService Notification4

DetailsView notification details for all notifications in the result set.

Report SQLSELECT DISTINCT COMPANY_CODE.CMPNY_CODE_NAME, TIME_DIM_NOTIFICTN.CALENDAR_YEAR, TIME_DIM_NOTIFICTN.CALENDAR_MONTH, NOTIFICATION_FACT.NOTIFICTN_ID, NOTIFICATION_FACT.NOTIFICTN_LINE_ITEM_ID, NOTIFICATION_FACT.COMPLT_FLAG, NOTIFICATION_FACT.BREAKDOWN_FLAG, NOTIFICATION_FACT.CREATE_BY_LOGIN, NOTIFICATION_FACT.IN_PROGRESS_FLAG, NOTIFICATION_FACT.NOTIFICTN_DESCR, NOTIFICATION_FACT.NOTIFICTN_LINE_DESCR, NOTIFICATION_FACT.ITEM_DELETE_FLAG, NOTIFICATION_FACT.OUTSTANDNG_FLAG, NOTIFICATION_FACT.POSTPONE_FLAG, NOTIFICATION_FACT.REPORTED_BY_LOGIN, COUNT(DISTINCT NOTIFICATION_FACT.NOTIFICTN_ID),



NOTIFICATION_FACT.NOTIFICTN_DATE, NOTIFICATION_FACT.REQ_END_DATE, NOTIFICATION_FACT.REQ_START_DATE, SERVICE_PERSON.FULL_NAME, NOTIFICTN_DOC_TYPE.DOC_TYPE_DESCR, EQUIPMENT.EQUIPMNT_CATEG_DESCR, EQUIPMENT.EQUIPMNT_TYPE_DESCR, EQUIPMENT.EQUIPMNT_IDFROM COMPANY_CODE, TIME_DIM TIME_DIM_NOTIFICTN, NOTIFICATION_FACT, SERVICE_PERSON, DOCUMENT_TYPE NOTIFICTN_DOC_TYPE, EQUIPMENTWHERE (

TIME_DIM_NOTIFICTN.CALENDAR_DATE=NOTIFICATION_FACT.NOTIFICTN_DATE )

AND ( COMPANY_CODE.CMPNY_CODE_ID=NOTIFICATION_FACT.CMPNY_CODE_ID )

AND ( SERVICE_PERSON.PERSON_ID=NOTIFICATION_FACT.PERSON_ID_RESP )

AND ( NOTIFICTN_DOC_TYPE.DOC_CATEG_ID=NOTIFICATION_FACT.DOC_CATEG_ID AND

NOTIFICTN_DOC_TYPE.DOC_TYPE_ID=NOTIFICATION_FACT.DOC_TYPE_ID AND

NOTIFICTN_DOC_TYPE.DIM_SRC_ID = 'NOTIFICTN' ) AND ( NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID

) AND ( ( COMPANY_CODE.CMPNY_CODE_NAME = 'IDES US INC' ) AND TIME_DIM_NOTIFICTN.CALENDAR_YEAR = 2000 AND TIME_DIM_NOTIFICTN.CALENDAR_MONTH In (1,2,4) )GROUP BY COMPANY_CODE.CMPNY_CODE_NAME, TIME_DIM_NOTIFICTN.CALENDAR_YEAR, TIME_DIM_NOTIFICTN.CALENDAR_MONTH, NOTIFICATION_FACT.NOTIFICTN_ID, NOTIFICATION_FACT.NOTIFICTN_LINE_ITEM_ID, NOTIFICATION_FACT.COMPLT_FLAG, NOTIFICATION_FACT.BREAKDOWN_FLAG,



NOTIFICATION_FACT.CREATE_BY_LOGIN, NOTIFICATION_FACT.IN_PROGRESS_FLAG, NOTIFICATION_FACT.NOTIFICTN_DESCR, NOTIFICATION_FACT.NOTIFICTN_LINE_DESCR, NOTIFICATION_FACT.ITEM_DELETE_FLAG, NOTIFICATION_FACT.OUTSTANDNG_FLAG, NOTIFICATION_FACT.POSTPONE_FLAG, NOTIFICATION_FACT.REPORTED_BY_LOGIN, NOTIFICATION_FACT.NOTIFICTN_DATE, NOTIFICATION_FACT.REQ_END_DATE, NOTIFICATION_FACT.REQ_START_DATE, SERVICE_PERSON.FULL_NAME, NOTIFICTN_DOC_TYPE.DOC_TYPE_DESCR, EQUIPMENT.EQUIPMNT_CATEG_DESCR, EQUIPMENT.EQUIPMNT_TYPE_DESCR, EQUIPMENT.EQUIPMNT_ID

Notification DetailsView Notification detail information for the selected Notification Id.

Report SQLAll report SQL is located in the Rapid Mart installation directory under “\Sample\DML”.



Notification StatisticsView Notification statistics and trend information by Functional Location for the selected Company Code and Calendar Year.

SummaryView notification days complete and days downtime statistics by functional location.



Trend by Functional LocationView statistics as a trend by functional location.

Calculations• Days Complete % Mix = Percentage([NOTIFCTN - Days Complete])• Days Downtime % Mix = Percentage([NOTIFCTN - Days Downtime])


Equipment Failures AnalysisView summary of equipment failures for each functional location by Plant for a selected Company Code and Calendar Year.



StatisticsView equipment failure statistics by plant.



ListingView equipment failure notifications by plant.


Recommended Table JoinsTo analyze Service Notification data you will need to create joins between the fact and dimension tables as follows:

Note: Additional joins between dimension and hierarchy tables are shown in “Recommended table joins” on page 27 for master reports.

Fact Table Dimension Table Join Expression

NOTIFICATION_FACT BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=NOTIFICATION_FACT.BUS_AREA_ID

NOTIFICATION_FACT CLASSIFICATION_HIER_HZ

NOTIFICATION_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'

NOTIFICATION_FACT CLASSIFICATION_HIER_HZ

NOTIFICATION_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'



NOTIFICATION_FACT CLASSIFICATION_HIER_VR

NOTIFICATION_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'

NOTIFICATION_FACT CLASSIFICATION_HIER_VR

NOTIFICATION_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'

NOTIFICATION_FACT COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=NOTIFICATION_FACT.CMPNY_CODE_ID

NOTIFICATION_FACT CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=NOTIFICATION_FACT.CTRL_AREA_ID

NOTIFICATION_FACT COST_CENTER NOTIFICATION_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and NOTIFICATION_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID

NOTIFICATION_FACT COST_CENTER_HIER_HZ

NOTIFICATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and NOTIFICATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID

NOTIFICATION_FACT COST_CENTER_HIER_VR

NOTIFICATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and NOTIFICATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

NOTIFICATION_FACT DOCUMENT_CATEGORY DOCUMENT_CATEGORY.DOC_CATEG_ID = NOTIFICATION_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'NOTIFICTN'

NOTIFICATION_FACT DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=NOTIFICATION_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=NOTIFICATION_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'NOTIFICTN'

NOTIFICATION_FACT EQUIPMENT NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID

NOTIFICATION_FACT EQUIPMENT_HIER_HZ NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID

NOTIFICATION_FACT EQUIPMENT_HIER_VR NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID

NOTIFICATION_FACT FUNCTIONAL_LOCATION

NOTIFICATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID

NOTIFICATION_FACT FUNCTIONAL_LOCATION_HIER_HZ

NOTIFICATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID

NOTIFICATION_FACT FUNCTIONAL_LOCATION_HIER_VR

NOTIFICATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID

NOTIFICATION_FACT INTERNAL_ORDER NOTIFICATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID




NOTIFICATION_FACT INTERNAL_ORDER_HIER_HZ

NOTIFICATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID

NOTIFICATION_FACT INTERNAL_ORDER_HIER_VR

NOTIFICATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID

NOTIFICATION_FACT MAINTENANCE_PRIORITY

MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID=NOTIFICATION_FACT.PRIORITY_TYPE_ID and MAINTENANCE_PRIORITY.PRIORITY_ID=NOTIFICATION_FACT.PRIORITY_ID

NOTIFICATION_FACT MALFUNCTION_CAUSE NOTIFICATION_FACT.CAUSE_ID=MALFUNCTION_CAUSE.CAUSE_ID and NOTIFICATION_FACT.CAUSE_GRP_ID=MALFUNCTION_CAUSE.CAUSE_GRP_ID

NOTIFICATION_FACT MALFUNCTION_DAMAGE

NOTIFICATION_FACT.DAMAGE_ID=MALFUNCTION_DAMAGE.DAMAGE_ID and NOTIFICATION_FACT.DAMAGE_GRP_ID=MALFUNCTION_DAMAGE.DAMAGE_GRP_ID

NOTIFICATION_FACT MALFUNCTION_EFFECT NOTIFICATION_FACT.EFFECT_ID=MALFUNCTION_EFFECT.EFFECT_ID

NOTIFICATION_FACT MALFUNCTION_OBJ_PART

NOTIFICATION_FACT.OBJ_PART_ID=MALFUNCTION_OBJ_PART.OBJ_PART_ID and NOTIFICATION_FACT.OBJ_PART_GRP_ID=MALFUNCTION_OBJ_PART.OBJ_PART_GRP_ID

NOTIFICATION_FACT MATERIAL NOTIFICATION_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID

NOTIFICATION_FACT MATERIAL_BY_PLANT NOTIFICATION_FACT.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and NOTIFICATION_FACT.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID

NOTIFICATION_FACT PLANNING_GROUP PLANNING_GROUP.PLANT_ID=NOTIFICATION_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=NOTIFICATION_FACT.PLANNG_GRP_ID

NOTIFICATION_FACT PLANT PLANT.PLANT_ID=NOTIFICATION_FACT.PLANT_ID

NOTIFICATION_FACT PLANT_LOCATION PLANT_LOCATION.PLANT_ID=NOTIFICATION_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=NOTIFICATION_FACT.LOCATN_ID

NOTIFICATION_FACT SERVICE_PERSON SERVICE_PERSON.PERSON_ID=NOTIFICATION_FACT.PERSON_ID_RESP

NOTIFICATION_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=NOTIFICATION_FACT.CREATE_DATE

NOTIFICATION_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=NOTIFICATION_FACT.NOTIFICTN_DATE

NOTIFICATION_FACT UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=NOTIFICATION_FACT.UOM_ID_DOWNTIME



ReportsMTBR MTTR 4

MTBR MTTRMTBR and MTTR data is related to service notifications.• MTBR = Mean (or Average) Time Between Repairs (also called up time)• MTTR = Mean (or Average) Time To Repair (also called down time)These are calculated from the notifications within the Rapid Mart load job.

ReportsSample Reports for the MTBR MTTR include:• MTBR MTTR Analysis• MTBR MTTR Listing

MTBR MTTR AnalysisView MTBR MTTR for all Companies by Plant and Equipment type for the selected Calendar Year.

NOTIFICATION_FACT WORK_CENTER NOTIFICATION_FACT.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID AND NOTIFICATION_FACT.PLANT_ID = WORK_CENTER.PLANT_ID

NOTIFICATION_FACT WORK_CENTER_HIER_HZ

NOTIFICATION_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND NOTIFICATION_FACT.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID

NOTIFICATION_FACT WORK_CENTER_HIER_VR

NOTIFICATION_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND NOTIFICATION_FACT.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



ReportsMTBR MTTR4

SummaryView summary statistics including days uptime, days downtime, % mix and averages.


ReportsMTBR MTTR 4

TrendView MTBR MTTR data as a trend by equipment type.

Calculations• % Mix Days Uptime = Percentage([MTBR MTTR - Days Uptime])



ReportsMTBR MTTR4
MTBR MTTR Listing
View MTBR MTTR Listing for the selected Company Code and Calendar Year.


Recommended Table JoinsTo analyze MTBR MTTR data you will need to create joins between the fact and dimension tables as follows:


ReportsMTBR MTTR 4



MTBR_MTTR_FACT BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=MTBR_MTTR_FACT.BUS_AREA_ID

MTBR_MTTR_FACT CLASSIFICATION_HIER_HZ

MTBR_MTTR_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'

MTBR_MTTR_FACT CLASSIFICATION_HIER_HZ

MTBR_MTTR_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'

MTBR_MTTR_FACT CLASSIFICATION_HIER_VR

MTBR_MTTR_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'

MTBR_MTTR_FACT CLASSIFICATION_HIER_VR

MTBR_MTTR_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'

MTBR_MTTR_FACT COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=MTBR_MTTR_FACT.CMPNY_CODE_ID

MTBR_MTTR_FACT CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=MTBR_MTTR_FACT.CTRL_AREA_ID

MTBR_MTTR_FACT COST_CENTER MTBR_MTTR_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and MTBR_MTTR_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID

MTBR_MTTR_FACT COST_CENTER_HIER_HZ

MTBR_MTTR_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and MTBR_MTTR_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


ReportsMTBR MTTR4

MTBR_MTTR_FACT COST_CENTER_HIER_VR

MTBR_MTTR_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and MTBR_MTTR_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

MTBR_MTTR_FACT DOCUMENT_CATEGORY

DOCUMENT_CATEGORY.DOC_CATEG_ID = MTBR_MTTR_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'NOTIFICTN'

MTBR_MTTR_FACT DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=MTBR_MTTR_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=MTBR_MTTR_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'NOTIFICTN'

MTBR_MTTR_FACT EQUIPMENT MTBR_MTTR_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID

MTBR_MTTR_FACT EQUIPMENT_HIER_HZ MTBR_MTTR_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID

MTBR_MTTR_FACT EQUIPMENT_HIER_VR

MTBR_MTTR_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID

MTBR_MTTR_FACT FUNCTIONAL_LOCATION

MTBR_MTTR_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID

MTBR_MTTR_FACT FUNCTIONAL_LOCATION_HIER_HZ

MTBR_MTTR_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID

MTBR_MTTR_FACT FUNCTIONAL_LOCATION_HIER_VR

MTBR_MTTR_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID

MTBR_MTTR_FACT INTERNAL_ORDER MTBR_MTTR_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID

MTBR_MTTR_FACT INTERNAL_ORDER_HIER_HZ

MTBR_MTTR_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID



ReportsMTBR MTTR 4

MTBR_MTTR_FACT INTERNAL_ORDER_HIER_VR

MTBR_MTTR_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID

MTBR_MTTR_FACT MAINTENANCE_PRIORITY

MTBR_MTTR_FACT.PRIORITY_ID=MAINTENANCE_PRIORITY.PRIORITY_ID and MTBR_MTTR_FACT.PRIORITY_TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID

MTBR_MTTR_FACT MALFUNCTION_EFFECT

MTBR_MTTR_FACT.EFFECT_ID=MALFUNCTION_EFFECT.EFFECT_ID

MTBR_MTTR_FACT MATERIAL MTBR_MTTR_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID

MTBR_MTTR_FACT MATERIAL_BY_PLANT MTBR_MTTR_FACT.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and MTBR_MTTR_FACT.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID

MTBR_MTTR_FACT NOTIFICATION MTBR_MTTR_FACT.NOTIFICTN_ID=NOTIFICATION.NOTIFICTN_ID

MTBR_MTTR_FACT PLANNING_GROUP PLANNING_GROUP.PLANT_ID=MTBR_MTTR_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=MTBR_MTTR_FACT.PLANNG_GRP_ID

MTBR_MTTR_FACT PLANT PLANT.PLANT_ID=MTBR_MTTR_FACT.PLANT_ID

MTBR_MTTR_FACT SERVICE_PERSON SERVICE_PERSON.PERSON_ID=MTBR_MTTR_FACT.PERSON_ID_RESP

MTBR_MTTR_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=MTBR_MTTR_FACT.NOTIFICTN_DATE

MTBR_MTTR_FACT WORK_CENTER MTBR_MTTR_FACT.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID and MTBR_MTTR_FACT.PLANT_ID=WORK_CENTER.PLANT_ID



ReportsService Order4

Service OrderService Orders document the necessary steps to repair the malfunction, or to complete the tasks requested in the notification. They serve as a cost collector for material and labor charges. They also record the time spent in the maintenance activities.

ReportsSample Reports for this section include:• Service Order Analysis• Service Order Listing

Service Order AnalysisView service order statistics by Plant, Service Technician, and Service Order for the selected Company Code, Calendar Year, and Service Order Status (open or closed orders).

MTBR_MTTR_FACT WORK_CENTER_HIER_HZ

MTBR_MTTR_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND MTBR_MTTR_FACT.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID

MTBR_MTTR_FACT WORK_CENTER_HIER_VR

MTBR_MTTR_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND MTBR_MTTR_FACT.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



ReportsService Order 4

By Plant and Functional LocView service order statistics by Plant and Functional Location.



By Service TechnicianView service order statistics for each Service Technician.



Order Details by PlantView service order details for each plant.

Calculations• TTL Variance % (ACTL vs SCHED) = If(Sum([SVC ORDR - Days

Complete Actual]) <> 0; Sum([SVC ORDR - Days Variance (ACTL vs SCHED)])/Sum([SVC ORDR - Days Complete Actual]); If([SVC ORDR - Days Complete Scheduled] = 0;0;1))

• Variance % (ACTL vs SCHED) = If([SVC ORDR - Days Complete Actual] <> 0; [SVC ORDR - Days Variance (ACTL vs SCHED)]/[SVC ORDR - Days Complete Actual]; If([SVC ORDR - Days Complete Scheduled] = 0;0;1))


Service Order ListingView Completed and Open service orders for the selected Company Code and Calendar Year.



Completed OrdersView service order listing for completed orders.



Open OrdersView service order listing for open orders.

Calculations• TTL Variance % (ACTL vs SCHED) = If(Sum([SVC ORDR - Days

Complete Actual]) <> 0; Sum([SVC ORDR - Days Variance (ACTL vs SCHED)])/Sum([SVC ORDR - Days Complete Actual]); If([SVC ORDR - Days Complete Scheduled] = 0;0;1))

• Variance % (ACTL vs SCHED) = If([SVC ORDR - Days Complete Actual] <> 0; [SVC ORDR - Days Variance (ACTL vs SCHED)]/[SVC ORDR - Days Complete Actual]; If([SVC ORDR - Days Complete Scheduled] = 0;0;1))



Recommended Table Joins
To analyze Service Order data you will need to create joins between the fact and dimension tables as follows:



SERVICE_ORDER_FACT BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=SERVICE_ORDER_FACT.BUS_AREA_ID

SERVICE_ORDER_FACT CLASSIFICATION_HIER_HZ

SERVICE_ORDER_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'

SERVICE_ORDER_FACT CLASSIFICATION_HIER_HZ

SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'

SERVICE_ORDER_FACT CLASSIFICATION_HIER_VR

SERVICE_ORDER_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'

SERVICE_ORDER_FACT CLASSIFICATION_HIER_VR

SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'

SERVICE_ORDER_FACT COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=SERVICE_ORDER_FACT.CMPNY_CODE_ID

SERVICE_ORDER_FACT CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_ORDER_FACT.CTRL_AREA_ID

SERVICE_ORDER_FACT COST_CENTER SERVICE_ORDER_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_ORDER_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID

SERVICE_ORDER_FACT COST_CENTER_HIER_HZ

SERVICE_ORDER_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID and SERVICE_ORDER_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID

SERVICE_ORDER_FACT COST_CENTER_HIER_VR

SERVICE_ORDER_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_ORDER_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT CURRENCY CURRENCY.CURR_ID=SERVICE_ORDER_FACT.CURR_ID

SERVICE_ORDER_FACT CUSTOMER CUSTOMER.CUSTOMER_ID=SERVICE_ORDER_FACT.CUSTOMER_ID



SERVICE_ORDER_FACT DOCUMENT_CATEGORY

DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_ORDER_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER'

SERVICE_ORDER_FACT DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_ORDER_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_ORDER_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER'

SERVICE_ORDER_FACT EQUIPMENT SERVICE_ORDER_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID

SERVICE_ORDER_FACT EQUIPMENT_HIER_HZ SERVICE_ORDER_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID

SERVICE_ORDER_FACT EQUIPMENT_HIER_VR SERVICE_ORDER_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT FUNCTIONAL_AREA SERVICE_ORDER_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_ID

SERVICE_ORDER_FACT FUNCTIONAL_AREA_HIER_HZ

SERVICE_ORDER_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID

SERVICE_ORDER_FACT FUNCTIONAL_AREA_HIER_VR

SERVICE_ORDER_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT FUNCTIONAL_LOCATION

SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID

SERVICE_ORDER_FACT FUNCTIONAL_LOCATION_HIER_HZ

SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID

SERVICE_ORDER_FACT FUNCTIONAL_LOCATION_HIER_VR

SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT INTERNAL_ORDER SERVICE_ORDER_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID

SERVICE_ORDER_FACT INTERNAL_ORDER_HIER_HZ

SERVICE_ORDER_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID

SERVICE_ORDER_FACT INTERNAL_ORDER_HIER_VR

SERVICE_ORDER_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT INTERNAL_ORDER_STATUS

INTERNAL_ORDER_STATUS.DOC_TYPE_ID=SERVICE_ORDER_FACT.DOC_TYPE_ID and INTERNAL_ORDER_STATUS.ORDER_STATUS_ID=SERVICE_ORDER_FACT.ORDER_STATUS_ID

SERVICE_ORDER_FACT MAINTENANCE_ACTIVITY_TYPE

SERVICE_ORDER_FACT.MAINT_ACTIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ACTIVITY_TYPE_ID

SERVICE_ORDER_FACT MAINTENANCE_PRIORITY

SERVICE_ORDER_FACT.PRIORITY_ID=MAINTENANCE_PRIORITY.PRIORITY_ID and SERVICE_ORDER_FACT.PRIORITY_TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID




SERVICE_ORDER_FACT MATERIAL SERVICE_ORDER_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID

SERVICE_ORDER_FACT MATERIAL_BY_PLANT SERVICE_ORDER_FACT.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and SERVICE_ORDER_FACT.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID

SERVICE_ORDER_FACT NOTIFICATION SERVICE_ORDER_FACT.NOTIFICTN_ID=NOTIFICATION.NOTIFICTN_ID

SERVICE_ORDER_FACT PLANNING_GROUP PLANNING_GROUP.PLANT_ID=SERVICE_ORDER_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=SERVICE_ORDER_FACT.PLANNG_GRP_ID

SERVICE_ORDER_FACT PLANT PLANT.PLANT_ID=SERVICE_ORDER_FACT.PLANT_ID

SERVICE_ORDER_FACT PLANT_LOCATION PLANT_LOCATION.PLANT_ID=SERVICE_ORDER_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_ORDER_FACT.LOCATN_ID

SERVICE_ORDER_FACT PRODUCT_HIERARCHY SERVICE_ORDER_FACT.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID

SERVICE_ORDER_FACT PROFIT_CENTER SERVICE_ORDER_FACT.CTRL_AREA_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_ORDER_FACT.PROFIT_CNTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID

SERVICE_ORDER_FACT PROFIT_CENTER_HIER_HZ

SERVICE_ORDER_FACT.CTRL_AREA_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_ORDER_FACT.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID

SERVICE_ORDER_FACT PROFIT_CENTER_HIER_VR

SERVICE_ORDER_FACT.CTRL_AREA_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_ORDER_FACT.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT PROJECT_ELEMENT SERVICE_ORDER_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT.PROJ_ELEM_ID

SERVICE_ORDER_FACT PROJECT_ELEMENT_HIER_HZ

SERVICE_ORDER_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID

SERVICE_ORDER_FACT PROJECT_ELEMENT_HIER_VR

SERVICE_ORDER_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID

SERVICE_ORDER_FACT SERVICE_PERSON SERVICE_PERSON.PERSON_ID=SERVICE_ORDER_FACT.PERSON_ID_RESP

SERVICE_ORDER_FACT SYSTEM_CONDITION SERVICE_ORDER_FACT.SYSTEM_CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ID

SERVICE_ORDER_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=SERVICE_ORDER_FACT.CREATE_DATE

SERVICE_ORDER_FACT WORK_CENTER SERVICE_ORDER_FACT.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID AND SERVICE_ORDER_FACT.PLANT_ID=WORK_CENTER.PLANT_ID



ReportsService Operation 4

Service OperationYou use operations to describe the individual maintenance tasks to be performed. The operation includes the time, the work center, and other controlling information for an individual maintenance task.

ReportsSample Reports for this section include:• Service Operation Detail• Service Operation Analysis• Service Operation Listing

SERVICE_ORDER_FACT WORK_CENTER_HIER_HZ

SERVICE_ORDER_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_ORDER_FACT.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID

SERVICE_ORDER_FACT WORK_CENTER_HIER_VR

SERVICE_ORDER_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_ORDER_FACT.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



ReportsService Operation4
Service Operation Detail
View service operation details for the selected Company Code and service Operation Routing Id.


Service Operation AnalysisView service operation summary and listing for the selected Company Code and Calendar Year.



SummaryView service operation summary statistics by maintenance activity and functional location.



TrendView service operation statistics trend by functional location.

Calculations• Avg Hours Variance (ACTL vs SCHED) = [SVC OP - Hours Variance

(ACTL vs SCHED)]/[SVC OP - Document Count]




Service Operation ListingView service operation summary and listing for the selected Company Code, Calendar Year, and Calendar Month. Includes a hyperlink by Operation Routing ID to Service Operation Detail.

Calculations• Avg Hours Variance (ACTL vs SCHED) = [SVC OP - Hours Variance

(ACTL vs SCHED)]/[SVC OP - Document Count]


Recommended Table JoinsTo analyze Service Operation data you will need to create joins between the fact and dimension tables as follows:





SERVICE_OPERATION_FACT

ACTIVITY SERVICE_OPERATION_FACT.ACTIVITY_ID=ACTIVITY.ACTIVITY_ID and SERVICE_OPERATION_FACT.CTRL_AREA_ID=ACTIVITY.CTRL_AREA_ID


ACTIVITY_HIER_HZ SERVICE_OPERATION_FACT.CTRL_AREA_ID=ACTIVITY_HIER_HZ.CTRL_AREA_ID and SERVICE_OPERATION_FACT.ACTIVITY_ID=ACTIVITY_HIER_HZ.ACTIVITY_ID


ACTIVITY_HIER_VR SERVICE_OPERATION_FACT.CTRL_AREA_ID = ACTIVITY_HIER_VR.CTRL_AREA_ID and SERVICE_OPERATION_FACT.ACTIVITY_ID = ACTIVITY_HIER_VR.CHILD_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=SERVICE_OPERATION_FACT.BUS_AREA_ID


CHART_OF_ACCOUNTS CHART_OF_ACCOUNTS.CHART_OF_ACCT_ID=SERVICE_OPERATION_FACT.CHART_OF_ACCT_ID


CLASSIFICATION_HIER_HZ

SERVICE_OPERATION_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'



SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'


CLASSIFICATION_HIER_VR

SERVICE_OPERATION_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'



SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=SERVICE_OPERATION_FACT.CMPNY_CODE_ID


CONTROL_KEY CONTROL_KEY.CTRL_KEY_ID=SERVICE_OPERATION_FACT.CTRL_KEY_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_OPERATION_FACT.CTRL_AREA_ID


COST_CENTER SERVICE_OPERATION_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_OPERATION_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID




COST_CENTER_HIER_HZ

SERVICE_OPERATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_OPERATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

SERVICE_OPERATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_OPERATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


COST_ELEMENT SERVICE_OPERATION_FACT.CHART_OF_ACCT_ID=COST_ELEMENT.CHART_OF_ACCT_ID and SERVICE_OPERATION_FACT.COST_ELEM_ID=COST_ELEMENT.COST_ELEM_ID


COST_ELEMENT_HIER_HZ

SERVICE_OPERATION_FACT.COST_ELEM_ID=COST_ELEMENT_HIER_HZ.COST_ELEM_ID and SERVICE_OPERATION_FACT.CHART_OF_ACCT_ID=COST_ELEMENT_HIER_HZ.CHART_OF_ACCT_ID


COST_ELEMENT_HIER_VR

SERVICE_OPERATION_FACT.CHART_OF_ACCT_ID=COST_ELEMENT_HIER_VR.CHART_OF_ACCT_ID and SERVICE_OPERATION_FACT.COST_ELEM_ID=COST_ELEMENT_HIER_VR.CHILD_ID


CURRENCY CURRENCY.CURR_ID=SERVICE_OPERATION_FACT.CURR_ID


CUSTOMER CUSTOMER.CUSTOMER_ID=SERVICE_OPERATION_FACT.CUSTOMER_ID


DOCUMENT_CATEGORY

DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_OPERATION_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER'


DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_OPERATION_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_OPERATION_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER'


EQUIPMENT SERVICE_OPERATION_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID


EQUIPMENT_HIER_HZ SERVICE_OPERATION_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID


EQUIPMENT_HIER_VR SERVICE_OPERATION_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID


FUNCTIONAL_AREA SERVICE_OPERATION_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_ID


FUNCTIONAL_AREA_HIER_HZ

SERVICE_OPERATION_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID


FUNCTIONAL_AREA_HIER_VR

SERVICE_OPERATION_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID





FUNCTIONAL_LOCATION

SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID


FUNCTIONAL_LOCATION_HIER_HZ

SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID


FUNCTIONAL_LOCATION_HIER_VR

SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID


INTERNAL_ORDER SERVICE_OPERATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID


INTERNAL_ORDER_HIER_HZ

SERVICE_OPERATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID


INTERNAL_ORDER_HIER_VR

SERVICE_OPERATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID


MAINTENANCE_ACTIVITY_TYPE

SERVICE_OPERATION_FACT.MAINT_ACTIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ACTIVITY_TYPE_ID


MAINTENANCE_PRIORITY

SERVICE_OPERATION_FACT.PRIORITY_ID=MAINTENANCE_PRIORITY.PRIORITY_ID and SERVICE_OPERATION_FACT.PRIORITY_TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID


MATERIAL SERVICE_OPERATION_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID


MATERIAL_BY_PLANT SERVICE_OPERATION_FACT.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and SERVICE_OPERATION_FACT.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID


NOTIFICATION SERVICE_OPERATION_FACT.NOTIFICTN_ID=NOTIFICATION.NOTIFICTN_ID


OBJECT_CLASS OBJECT_CLASS.OBJ_CLASS_ID=SERVICE_OPERATION_FACT.OBJ_CLASS_ID


OBJECT_TYPE OBJECT_TYPE.OBJ_TYPE_ID=SERVICE_OPERATION_FACT.OBJ_TYPE_ID and OBJECT_TYPE.DIM_SRC_ID = 'ORDER'


OPERATION_SUITABILITY

OPERATION_SUITABILITY.PLANT_ID=SERVICE_OPERATION_FACT.PLANT_ID and OPERATION_SUITABILITY.SUITABILITY_ID=SERVICE_OPERATION_FACT.SUITABILITY_ID


PLANNING_GROUP PLANNING_GROUP.PLANT_ID=SERVICE_OPERATION_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=SERVICE_OPERATION_FACT.PLANNG_GRP_ID


PLANT PLANT.PLANT_ID=SERVICE_OPERATION_FACT.PLANT_ID





PLANT_LOCATION PLANT_LOCATION.PLANT_ID=SERVICE_OPERATION_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_OPERATION_FACT.LOCATN_ID


PRODUCT_HIERARCHY SERVICE_OPERATION_FACT.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID


PROFIT_CENTER SERVICE_OPERATION_FACT.CTRL_AREA_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_OPERATION_FACT.PROFIT_CNTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID


PROFIT_CENTER_HIER_HZ

SERVICE_OPERATION_FACT.CTRL_AREA_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_OPERATION_FACT.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID


PROFIT_CENTER_HIER_VR

SERVICE_OPERATION_FACT.CTRL_AREA_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_OPERATION_FACT.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID


PROJECT_ELEMENT SERVICE_OPERATION_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT.PROJ_ELEM_ID


PROJECT_ELEMENT_HIER_HZ

SERVICE_OPERATION_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID


PROJECT_ELEMENT_HIER_VR

SERVICE_OPERATION_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID


SYSTEM_CONDITION SERVICE_OPERATION_FACT.SYSTEM_CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ID


TIME_DIM TIME_DIM.CALENDAR_DATE=SERVICE_OPERATION_FACT.CREATE_DATE


UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=SERVICE_OPERATION_FACT.UOM_ID_DURTN


UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=SERVICE_OPERATION_FACT.UOM_ID_WORK


VENDOR VENDOR.VENDOR_ID=SERVICE_OPERATION_FACT.VENDOR_ID


VENDOR_BY_COMPANY VENDOR_BY_COMPANY.VENDOR_ID=SERVICE_OPERATION_FACT.VENDOR_ID and VENDOR_BY_COMPANY.CMPNY_CODE_ID=SERVICE_OPERATION_FACT.CMPNY_CODE_ID


WORK_CENTER SERVICE_OPERATION_FACT.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID and SERVICE_OPERATION_FACT.PLANT_ID=WORK_CENTER.PLANT_ID



ReportsService Confirmation4

Service ConfirmationThe confirmation section extracts data about confirmations, which document the actual time to complete maintenance on an item.

ReportsSample Reports for this section include:• Service Confirmation Listing• Service Confirmation Details• Service Confirmation Performance

Service Confirmation ListingView service confirmation listing for the selected Company Code, Calendar Year, and Calendar Month. Includes a hyperlink by Confirmation ID to Service Confirmation Details.


WORK_CENTER_HIER_HZ

SERVICE_OPERATION_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_OPERATION_FACT.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID


WORK_CENTER_HIER_VR

SERVICE_OPERATION_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_OPERATION_FACT.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



ReportsService Confirmation 4

By PlantView service confirmation listing organized by plant.



By Service OrderView service confirmations for each service order.

Calculations• Hours Variance % (EXECTN vs FCST) = If([SVC CONF - Hours

Execution] <> 0; ([SVC CONF - Hours Execution]-[SVC CONF - Hours Complete Forecast])/[SVC CONF - Hours Execution]; 0)




Service Confirmation DetailsView service confirmation details for the selected Confirmation Id.


Execution] <> 0; ([SVC CONF - Hours Execution]-[SVC CONF - Hours Complete Forecast])/[SVC CONF - Hours Execution]; 0)


Service Confirmation PerformanceView service confirmation performance by Activity for the selected Company Code and Calendar Year.



Summary by ActivityView service confirmation summary statistics by activity.



Trend by ActivityView trend of service confirmation measures by activity.


Execution] <> 0; ([SVC CONF - Hours Variance (EXECTN vs FCST)])/[SVC CONF - Hours Execution]; 0)


Recommended Table JoinsTo analyze Service Confirmation data you will need to create joins between the fact and dimension tables as follows:





SERVICE_CONFIRMATION_FACT

ACTIVITY SERVICE_CONFIRMATION_FACT.ACTIVITY_ID=ACTIVITY.ACTIVITY_ID and SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=ACTIVITY.CTRL_AREA_ID


ACTIVITY_HIER_HZ SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=ACTIVITY_HIER_HZ.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.ACTIVITY_ID=ACTIVITY_HIER_HZ.ACTIVITY_ID


ACTIVITY_HIER_VR SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID = ACTIVITY_HIER_VR.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.ACTIVITY_ID = ACTIVITY_HIER_VR.CHILD_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=SERVICE_CONFIRMATION_FACT.BUS_AREA_ID


CAPACITY CAPACITY.CAPACITY_ID=SERVICE_CONFIRMATION_FACT.CAPACITY_ID



SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'



SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'



SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'



SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=SERVICE_CONFIRMATION_FACT.CMPNY_CODE_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID


COST_CENTER SERVICE_CONFIRMATION_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID


COST_CENTER_HIER_HZ

SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID




COST_CENTER_HIER_VR

SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


CURRENCY CURRENCY.CURR_ID=SERVICE_CONFIRMATION_FACT.CURR_ID


CUSTOMER CUSTOMER.CUSTOMER_ID=SERVICE_CONFIRMATION_FACT.CUSTOMER_ID


DOCUMENT_CATEGORY

DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_CONFIRMATION_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER'


DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_CONFIRMATION_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_CONFIRMATION_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER'


EQUIPMENT SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID


EQUIPMENT_HIER_HZ SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID


EQUIPMENT_HIER_VR SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID


FUNCTIONAL_AREA SERVICE_CONFIRMATION_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_ID



SERVICE_CONFIRMATION_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID



SERVICE_CONFIRMATION_FACT.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID


FUNCTIONAL_LOCATION

SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID



SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID



SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID


INTERNAL_ORDER SERVICE_CONFIRMATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID



SERVICE_CONFIRMATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID



SERVICE_CONFIRMATION_FACT.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID





INTERNAL_ORDER_STATUS

INTERNAL_ORDER_STATUS.DOC_TYPE_ID=SERVICE_CONFIRMATION_FACT.DOC_TYPE_ID and INTERNAL_ORDER_STATUS.ORDER_STATUS_ID=SERVICE_CONFIRMATION_FACT.ORDER_STATUS_ID



SERVICE_CONFIRMATION_FACT.MAINT_ACTIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ACTIVITY_TYPE_ID



SERVICE_CONFIRMATION_FACT.PRIORITY_ID=MAINTENANCE_PRIORITY.PRIORITY_ID and SERVICE_CONFIRMATION_FACT.PRIORITY_TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID


MATERIAL SERVICE_CONFIRMATION_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID


MATERIAL_BY_PLANT SERVICE_CONFIRMATION_FACT.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and SERVICE_CONFIRMATION_FACT.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID


NOTIFICATION SERVICE_CONFIRMATION_FACT.NOTIFICTN_ID=NOTIFICATION.NOTIFICTN_ID



OPERATION_SUITABILITY.PLANT_ID=SERVICE_CONFIRMATION_FACT.PLANT_ID and OPERATION_SUITABILITY.SUITABILITY_ID=SERVICE_CONFIRMATION_FACT.SUITABILITY_ID


PLANNING_GROUP PLANNING_GROUP.PLANT_ID=SERVICE_CONFIRMATION_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=SERVICE_CONFIRMATION_FACT.PLANNG_GRP_ID


PLANT PLANT.PLANT_ID=SERVICE_CONFIRMATION_FACT.PLANT_ID


PLANT_LOCATION PLANT_LOCATION.PLANT_ID=SERVICE_CONFIRMATION_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_CONFIRMATION_FACT.LOCATN_ID


PRODUCT_HIERARCHY SERVICE_CONFIRMATION_FACT.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID


PROFIT_CENTER SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.PROFIT_CNTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID



SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID



SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID



ReportsService Order Cost 4

Service Order CostThe Service Order cost section extracts data about the costs associated with maintenance Service Orders. Each maintenance Service Order can include actual cost and an estimate of the cost to complete the Service Order. SAP solutions calculate planned costs after the resources and capacities are planned for that Service Order. Actual costs are posted at confirmation time, and can be analyzed after work is completed.

ReportsSample Reports for this section include:• Service Cost Balance Trend Comparison


PROJECT_ELEMENT SERVICE_CONFIRMATION_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT.PROJ_ELEM_ID



SERVICE_CONFIRMATION_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID



SERVICE_CONFIRMATION_FACT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID


SERVICE_PERSON SERVICE_PERSON.PERSON_ID=SERVICE_CONFIRMATION_FACT.PERSON_ID_RESP


SYSTEM_CONDITION SERVICE_CONFIRMATION_FACT.SYSTEM_CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ID


TIME_DIM TIME_DIM.CALENDAR_DATE=SERVICE_CONFIRMATION_FACT.CREATE_DATE


UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=SERVICE_CONFIRMATION_FACT.UOM_ID_DURTN_ACTL


UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=SERVICE_CONFIRMATION_FACT.UOM_ID_WORK_ACTL


WORK_CENTER SERVICE_CONFIRMATION_FACT.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID AND SERVICE_CONFIRMATION_FACT.PLANT_ID = WORK_CENTER.PLANT_ID


WORK_CENTER_HIER_HZ

SERVICE_CONFIRMATION_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_CONFIRMATION_FACT.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID


WORK_CENTER_HIER_VR

SERVICE_CONFIRMATION_FACT.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_CONFIRMATION_FACT.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



ReportsService Order Cost4

• Service Cost Balance Variance Trend• Service Cost YTD Trend Analysis

Service Cost Balance Trend ComparisonDisplays the service cost balance trend data for the selected Company Code, Fiscal Years, and Equipment hierarchy.

Actual Balance TrendView actual service cost balance trend by equipment hierarchy.



Variance Previous PeriodView actual service cost variance vs. previous period trend by equipment hierarchy.

Calculations• Section Hierarchy Lvl 1 = [Equipment Level 1 Full Name]• Balance Variance vs. Previous Period (ex: Period 2) = [SVC CST SUM

Hz Actual PTD Balance Per 02 TRX]-[SVC CST SUM Hz Actual PTD Balance Per 01 TRX]

Note: All other Variance vs. Previous Period calculations are done the same way with the appropriate period values.



Service Cost Balance Variance Trend
View Actual, Planned (or Budget), Variance, and Variance % period service cost trends for a specific Company Code, Functional Location, and Fiscal Year.

Calculations• Actual = [SVC CST SUM Vr - Actual PTD Balance TRX]• Budget = [SVC CST SUM Vr - Budget PTD Balance TRX]• Variance = [SVC CST SUM Vr - Actual PTD Balance TRX]-[SVC CST

SUM Vr - Budget PTD Balance TRX]• Variance % = If([Actual] <> 0; [Variance]/[Actual]; If([Actual]<> 0 And

[Variance]=0; 0;1))




Service Cost YTD Trend AnalysisView Actual YTD trends for a specific Company Code, Parent GL Account, Fiscal Year, and Ledger Version.

Calculations• Actual YTD Balance = [SVC CST SUM Vr - Actual PTD Balance TRX]• Balance Variance = [SVC CST SUM Vr - Actual PTD Balance

TRX]-[SVC CST SUM Vr - Budget PTD Balance TRX]• Budget YTD Balance = [SVC CST SUM Vr - Budget PTD Balance TRX]• Variance % = If([SVC CST SUM Vr - Actual PTD Balance TRX] <> 0;

[Balance Variance]/[SVC CST SUM Vr - Actual PTD Balance TRX]; If([SVC CST SUM Vr - Actual PTD Balance TRX]=0 And [Balance Variance]<>0; 1; 0))


Recommended Table JoinsTo analyze Service Order Cost data you will need to create joins between the fact and dimension tables as follows:





SERVICE_COST_SUMMARY_FACT_HZ

BUSINESS_ACTIVITY BUSINESS_ACTIVITY.BUS_ACTIVITY_ID=SERVICE_COST_SUMMARY_FACT_HZ.BUS_ACTIVITY_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=SERVICE_COST_SUMMARY_FACT_HZ.BUS_AREA_ID



SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'



SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'



SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'



SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=SERVICE_COST_SUMMARY_FACT_HZ.CMPNY_CODE_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID


COST_CENTER SERVICE_COST_SUMMARY_FACT_HZ.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID


COST_CENTER_HIER_HZ

SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMARY_FACT_HZ.CURR_ID_CTRL_AREA


CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMARY_FACT_HZ.CURR_ID_LOC




CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMARY_FACT_HZ.CURR_ID_TRX


DOCUMENT_CATEGORY

DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_COST_SUMMARY_FACT_HZ.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER'


DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_COST_SUMMARY_FACT_HZ.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_COST_SUMMARY_FACT_HZ.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER'


EQUIPMENT SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID


EQUIPMENT_HIER_HZ SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID


EQUIPMENT_HIER_VR SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID


FINANCIAL_RECORD_CATEGORY

SERVICE_COST_SUMMARY_FACT_HZ.RECORD_CATEG_ID=FINANCIAL_RECORD_CATEGORY.RECORD_CATEG_ID


FINANCIAL_RECORD_TYPE

SERVICE_COST_SUMMARY_FACT_HZ.RECORD_TYPE_ID=FINANCIAL_RECORD_TYPE.RECORD_TYPE_ID and FINANCIAL_RECORD_TYPE.RECORD_TYPE_ID = 'COST'


FUNCTIONAL_AREA SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_ID



SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID



SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID


FUNCTIONAL_LOCATION

SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID



SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID



SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID


INTERNAL_ORDER SERVICE_COST_SUMMARY_FACT_HZ.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID



SERVICE_COST_SUMMARY_FACT_HZ.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID






SERVICE_COST_SUMMARY_FACT_HZ.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID



SERVICE_COST_SUMMARY_FACT_HZ.MAINT_ACTIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ACTIVITY_TYPE_ID



SERVICE_COST_SUMMARY_FACT_HZ.PRIORITY_TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID and SERVICE_COST_SUMMARY_FACT_HZ.PRIORITY_ID=MAINTENANCE_PRIORITY.PRIORITY_ID


MATERIAL SERVICE_COST_SUMMARY_FACT_HZ.MATERIAL_ID=MATERIAL.MATERIAL_ID


MATERIAL_BY_PLANT SERVICE_COST_SUMMARY_FACT_HZ.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID


PLANT PLANT.PLANT_ID=SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID


PLANT_LOCATION PLANT_LOCATION.PLANT_ID=SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_COST_SUMMARY_FACT_HZ.LOCATN_ID


PRODUCT_HIERARCHY SERVICE_COST_SUMMARY_FACT_HZ.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID


PROFIT_CENTER SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.PROFIT_CNTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID



SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID



SERVICE_COST_SUMMARY_FACT_HZ.CTRL_AREA_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID


PROJECT_ELEMENT SERVICE_COST_SUMMARY_FACT_HZ.PROJ_ELEM_ID=PROJECT_ELEMENT.PROJ_ELEM_ID



SERVICE_COST_SUMMARY_FACT_HZ.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID



SERVICE_COST_SUMMARY_FACT_HZ.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID






SERVICE_COST_SUMMARY_FACT_HZ.FISC_YEAR = SERVICE_COST_SUMMARY_FACT_HZ.PARTITION_YEAR


SYSTEM_CONDITION SERVICE_COST_SUMMARY_FACT_HZ.SYSTEM_CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ID


VARIANCE_CATEGORY VARIANCE_CATEGORY.VARIANCE_CATEG_ID=SERVICE_COST_SUMMARY_FACT_HZ.VARIANCE_CATEG_ID


WORK_CENTER SERVICE_COST_SUMMARY_FACT_HZ.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID AND SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID = WORK_CENTER.PLANT_ID


WORK_CENTER_HIER_HZ

SERVICE_COST_SUMMARY_FACT_HZ.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID


WORK_CENTER_HIER_VR

SERVICE_COST_SUMMARY_FACT_HZ.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID


BUSINESS_ACTIVITY BUSINESS_ACTIVITY.BUS_ACTIVITY_ID=SERVICE_COST_SUMMARY_FACT_VR.BUS_ACTIVITY_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=SERVICE_COST_SUMMARY_FACT_VR.BUS_AREA_ID



SERVICE_COST_SUMMARY_FACT_VR.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'



SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'



SERVICE_COST_SUMMARY_FACT_VR.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'



SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=SERVICE_COST_SUMMARY_FACT_VR.CMPNY_CODE_ID





CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID


COST_CENTER SERVICE_COST_SUMMARY_FACT_VR.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID


COST_CENTER_HIER_HZ

SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMARY_FACT_VR.CURR_ID_CTRL_AREA


CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMARY_FACT_VR.CURR_ID_LOC


CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMARY_FACT_VR.CURR_ID_TRX


DOCUMENT_CATEGORY

DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_COST_SUMMARY_FACT_VR.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER'


DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_COST_SUMMARY_FACT_VR.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_COST_SUMMARY_FACT_VR.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER'


EQUIPMENT SERVICE_COST_SUMMARY_FACT_VR.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID


EQUIPMENT_HIER_HZ SERVICE_COST_SUMMARY_FACT_VR.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID


EQUIPMENT_HIER_VR SERVICE_COST_SUMMARY_FACT_VR.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID



SERVICE_COST_SUMMARY_FACT_VR.RECORD_CATEG_ID=FINANCIAL_RECORD_CATEGORY.RECORD_CATEG_ID



SERVICE_COST_SUMMARY_FACT_VR.RECORD_TYPE_ID=FINANCIAL_RECORD_TYPE.RECORD_TYPE_ID and FINANCIAL_RECORD_TYPE.RECORD_TYPE_ID = 'COST'





FISC_PERIOD FISC_PERIOD.FISC_YEAR=SERVICE_COST_SUMMARY_FACT_VR.FISC_YEAR and FISC_PERIOD.FISC_PERIOD=SERVICE_COST_SUMMARY_FACT_VR.FISC_PERIOD and FISC_PERIOD.FISC_YR_VARIANT_ID=SERVICE_COST_SUMMARY_FACT_VR.FISC_YR_VARIANT_ID


FUNCTIONAL_AREA SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_ID



SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID



SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID


FUNCTIONAL_LOCATION

SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID



SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID



SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID


INTERNAL_ORDER SERVICE_COST_SUMMARY_FACT_VR.INTERNAL_ORDER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID



SERVICE_COST_SUMMARY_FACT_VR.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID



SERVICE_COST_SUMMARY_FACT_VR.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID



SERVICE_COST_SUMMARY_FACT_VR.MAINT_ACTIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ACTIVITY_TYPE_ID



SERVICE_COST_SUMMARY_FACT_VR.PRIORITY_TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID and SERVICE_COST_SUMMARY_FACT_VR.PRIORITY_ID=MAINTENANCE_PRIORITY.PRIORITY_ID


MATERIAL SERVICE_COST_SUMMARY_FACT_VR.MATERIAL_ID=MATERIAL.MATERIAL_ID


MATERIAL_BY_PLANT SERVICE_COST_SUMMARY_FACT_VR.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID


PLANT PLANT.PLANT_ID=SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID





PLANT_LOCATION PLANT_LOCATION.PLANT_ID=SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_COST_SUMMARY_FACT_VR.LOCATN_ID


PRODUCT_HIERARCHY SERVICE_COST_SUMMARY_FACT_VR.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID


PROFIT_CENTER SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.PROFIT_CNTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID



SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID



SERVICE_COST_SUMMARY_FACT_VR.CTRL_AREA_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID


PROJECT_ELEMENT SERVICE_COST_SUMMARY_FACT_VR.PROJ_ELEM_ID=PROJECT_ELEMENT.PROJ_ELEM_ID



SERVICE_COST_SUMMARY_FACT_VR.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID



SERVICE_COST_SUMMARY_FACT_VR.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID



SERVICE_COST_SUMMARY_FACT_VR.FISC_YEAR = SERVICE_COST_SUMMARY_FACT_VR.PARTITION_YEAR


SYSTEM_CONDITION SERVICE_COST_SUMMARY_FACT_VR.SYSTEM_CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ID


VARIANCE_CATEGORY VARIANCE_CATEGORY.VARIANCE_CATEG_ID=SERVICE_COST_SUMMARY_FACT_VR.VARIANCE_CATEG_ID


WORK_CENTER SERVICE_COST_SUMMARY_FACT_VR.WORK_CNTR_ID=WORK_CENTER.WORK_CNTR_ID AND SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID = WORK_CENTER.PLANT_ID



ReportsService Master 4

Service MasterThis section shows the two Technical Objects (Functional Location and Equipment) as master data joined to their Classification & Characteristic attributes as shown on page 30.This allows you to analyze the technical objects by the various characteristics assigned to them. It facilitates reporting across hierarchy and dimensional boundaries. You can use the information in this section to identify characteristic attributes that require special attention.Note: The Service Master Section reports are based on the SAP Service Master universe (semantic layer). All previous reports are based on the SAP Plant Maintenance universe.

ReportsSample Reports for this section include:• Functional Location Characteristics• Equipment Characteristics


WORK_CENTER_HIER_HZ

SERVICE_COST_SUMMARY_FACT_VR.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID


WORK_CENTER_HIER_VR

SERVICE_COST_SUMMARY_FACT_VR.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



ReportsService Master4
Functional Location Characteristics
View Functional Location Characteristics summary for the selected Company Code.


Equipment CharacteristicsView Equipment Characteristics summary for the selected Company Code and Characteristic Name.



Equipment Characteristics by PlantView equipment characteristics organized by plant name.



Equipment Characteristics by ClassView equipment characteristics organized by equipment hierarchy.


Recommended Table JoinsTo analyze Service Master data you will need to create joins between the fact and dimension tables as follows:





EQUIPMENT_CHAR_FACT

BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=EQUIPMENT_CHAR_FACT.BUS_AREA_ID

EQUIPMENT_CHAR_FACT


EQUIPMENT_CHAR_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002'

EQUIPMENT_CHAR_FACT


EQUIPMENT_CHAR_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002'

EQUIPMENT_CHAR_FACT

COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=EQUIPMENT_CHAR_FACT.CMPNY_CODE_ID

EQUIPMENT_CHAR_FACT

CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=EQUIPMENT_CHAR_FACT.CTRL_AREA_ID

EQUIPMENT_CHAR_FACT

COST_CENTER EQUIPMENT_CHAR_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and EQUIPMENT_CHAR_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID

EQUIPMENT_CHAR_FACT

COST_CENTER_HIER_HZ

EQUIPMENT_CHAR_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and EQUIPMENT_CHAR_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID

EQUIPMENT_CHAR_FACT

COST_CENTER_HIER_VR

EQUIPMENT_CHAR_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and EQUIPMENT_CHAR_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

EQUIPMENT_CHAR_FACT

EQUIPMENT EQUIPMENT_CHAR_FACT.EQUIPMNT_ID=EQUIPMENT.EQUIPMNT_ID

EQUIPMENT_CHAR_FACT

EQUIPMENT_HIER_HZ EQUIPMENT_CHAR_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID

EQUIPMENT_CHAR_FACT

EQUIPMENT_HIER_VR EQUIPMENT_CHAR_FACT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID

EQUIPMENT_CHAR_FACT

FUNCTIONAL_LOCATION

EQUIPMENT_CHAR_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID

EQUIPMENT_CHAR_FACT


EQUIPMENT_CHAR_FACT.FUNCTNL_LOCATN_ID = FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID

EQUIPMENT_CHAR_FACT


EQUIPMENT_CHAR_FACT.FUNCTNL_LOCATN_ID = FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID

EQUIPMENT_CHAR_FACT

MATERIAL EQUIPMENT_CHAR_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID



EQUIPMENT_CHAR_FACT

MATERIAL_BY_PLANT EQUIPMENT_CHAR_FACT.MATERIAL_ID=MATERIAL_BY_PLANT.MATERIAL_ID and EQUIPMENT_CHAR_FACT.PLANT_ID=MATERIAL_BY_PLANT.PLANT_ID

EQUIPMENT_CHAR_FACT

PLANT PLANT.PLANT_ID=EQUIPMENT_CHAR_FACT.PLANT_ID

EQUIPMENT_CHAR_FACT

PLANT_LOCATION PLANT_LOCATION.PLANT_ID=EQUIPMENT_CHAR_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=EQUIPMENT_CHAR_FACT.LOCATN_ID

EQUIPMENT_CHAR_FACT

SERVICE_PERSON SERVICE_PERSON.PERSON_ID=EQUIPMENT_CHAR_FACT.PERSON_ID_RESP

EQUIPMENT_CHAR_FACT

TIME_DIM TIME_DIM.CALENDAR_DATE=EQUIPMENT_CHAR_FACT.VALID_FROM_DATE

EQUIPMENT_CHAR_FACT

UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=EQUIPMENT_CHAR_FACT.UOM_ID_VALUE

EQUIPMENT_CHAR_FACT

VENDOR VENDOR.VENDOR_ID=EQUIPMENT_CHAR_FACT.VENDOR_ID

EQUIPMENT_CHAR_FACT

VENDOR_BY_COMPANY VENDOR_BY_COMPANY.VENDOR_ID=EQUIPMENT_CHAR_FACT.VENDOR_ID and VENDOR_BY_COMPANY.CMPNY_CODE_ID=EQUIPMENT_CHAR_FACT.CMPNY_CODE_ID

FUNCTIONAL_LOCATION_CHAR_FACT

BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=FUNCTIONAL_LOCATION_CHAR_FACT.BUS_AREA_ID



FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'



FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003'


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=FUNCTIONAL_LOCATION_CHAR_FACT.CMPNY_CODE_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID=FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_AREA_ID


COST_CENTER FUNCTIONAL_LOCATION_CHAR_FACT.COST_CNTR_ID=COST_CENTER.COST_CNTR_ID and FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_AREA_ID=COST_CENTER.CTRL_AREA_ID


COST_CENTER_HIER_HZ

FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and FUNCTIONAL_LOCATION_CHAR_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID



ReportsSAP Master Data Reports 4

SAP Master Data ReportsSAP Master Data reports provide a tool for Data Discovery and Data Auditing. These reports are used by all Rapid Marts in the SAP BusinessObjects Rapid Mart Suite for SAP. Note: This universe only includes joins for hierarchy dimensions. No other joins are provided as they are specific to each Rapid Mart. Recommended table joins contains a complete list of joins provided in the SAP Master Data universe.


COST_CENTER_HIER_VR

FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and FUNCTIONAL_LOCATION_CHAR_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


FUNCTIONAL_LOCATION

FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID



FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_LOCATN_ID = FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID



FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_LOCATN_ID = FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID


PLANNING_GROUP PLANNING_GROUP.PLANT_ID=FUNCTIONAL_LOCATION_CHAR_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=FUNCTIONAL_LOCATION_CHAR_FACT.PLANNG_GRP_ID


PLANT PLANT.PLANT_ID=FUNCTIONAL_LOCATION_CHAR_FACT.PLANT_ID


PLANT_LOCATION PLANT_LOCATION.PLANT_ID=FUNCTIONAL_LOCATION_CHAR_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=FUNCTIONAL_LOCATION_CHAR_FACT.LOCATN_ID


SERVICE_PERSON SERVICE_PERSON.PERSON_ID=FUNCTIONAL_LOCATION_CHAR_FACT.PERSON_ID_RESP


TIME_DIM TIME_DIM.CALENDAR_DATE = FUNCTIONAL_LOCATION_CHAR_FACT.VALID_FROM_DATE


UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=FUNCTIONAL_LOCATION_CHAR_FACT.UOM_ID_VALUE



ReportsSAP Master Data Reports4
Data Discovery
These reports allow users to view hierarchy data. The full breadth of the data can be ascertained and used to make informed decisions when designing a report for any given subject area. The reports are:• Activity Hierarchy Data Discovery• Cost Center Hierarchy Data Discovery• Profit Center Hierarchy Data Discovery• Cost Element Hierarchy Data Discovery• Internal Order Hierarchy Data Discovery• Functional Area Hierarchy Data Discovery• GL Account Hierarchy Data Discovery• FS Account Hierarchy Data Discovery• Project Element Hierarchy Data Discovery • Equipment Hierarchy Data Discovery• Functional Location Hierarchy Data Discovery• Work Center Hierarchy Data Discovery• BOM Hierarchy Data Discovery• Organization Unit Data Discovery• Position Data Discovery



Activity Hierarchy Data DiscoveryView Activity Hierarchies for a specified Controlling Area, Parent Activity, and Activity Hierarchy.

Report SQLSELECT DISTINCT ACTIVITY_HIER_HR.ACTIVITY_ID, ACTIVITY_HIER_HR.CTRL_AREA_ID, ACTIVITY_HIER_HR.LEAF_LEVEL, ACTIVITY_HIER_HR.LEVEL_0_FULLNAME, ACTIVITY_HIER_HR.LEVEL_1_FULLNAME, ACTIVITY_HIER_HR.LEVEL_2_FULLNAME, ACTIVITY_HIER_HR.LEVEL_3_FULLNAME, ACTIVITY_HIER_HR.LEVEL_4_FULLNAME, ACTIVITY_HIER_HR.LEVEL_5_FULLNAME, ACTIVITY_HIER_HR.LEVEL_6_FULLNAME, ACTIVITY_HIER_HR.LEVEL_7_FULLNAMEFROM ACTIVITY_HIER_HR, ACTIVITY_HIER_VR, ACTIVITYWHERE ( ACTIVITY.CTRL_AREA_ID = ACTIVITY_HIER_VR.CTRL_AREA_ID and ACTIVITY.ACTIVITY_ID = ACTIVITY_HIER_VR.DESCENDANT_ID ) AND ( ACTIVITY.CTRL_AREA_ID=ACTIVITY_HIER_HR.CTRL_AREA_ID and

ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HR.ACTIVITY_ID ) AND



( ( ACTIVITY_HIER_VR.ANCESTOR_ID in ('A1') AND

ACTIVITY_HIER_HR.LEVEL_0_ID in ('A1') ) AND ACTIVITY_HIER_HR.CTRL_AREA_ID = '1000' AND ACTIVITY_HIER_HR.CTRL_AREA_ID <> '?' AND ACTIVITY_HIER_HR.LEVEL_0_ID <> '?' )

Cost Center Hierarchy Data Discovery View Cost Center Hierarchies for a specified Controlling Area, Parent Cost Center, and Cost Center Hierarchy.

Report SQLAll report SQL is located in the Rapid Mart installation directory under "\Sample\DDL".



Profit Center Hierarchy Data DiscoveryView Profit Center Hierarchies for a specified Controlling Area, Parent Profit Center(s), and Profit Center Hierarchy (or Hierarchies).


Cost Element Hierarchy Data DiscoveryView Cost Element Hierarchies for a specified Chart of Accounts, Parent Cost Element, and Cost Element Hierarchy.



Internal Order Hierarchy Data Discovery
View Internal Order Hierarchies for a specified Controlling Area, Parent Internal Order, and Internal Order Hierarchy.




Functional Area Hierarchy Data DiscoveryView Functional Area Hierarchies for a specified Parent Functional Area and Functional Area Hierarchy.



GL Account Hierarchy Data Discovery
View GL Account, Profit Center GL Account, and Financial Statement (FS) Hierarchies for a specified Chart of Accounts, Parent GL Account, and GL Account Hierarchy.This report uses a prompt to indicate which type of financial hierarchy should be analyzed: • GL Account Hierarchy = @GL• Profit Center GL Account Hierarchy = @PC• FS Hierarchy = code of the financial statement (ex: CAUS)




FS Account Hierarchy Data DiscoveryView account information for a specified Chart of Accounts and FS Account hierarchy, along with account ranges, credit and debit flags, and account full names.

Report SQLSELECT DISTINCT GL_ACCOUNT_HIER_HZ.LEVEL_0_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_1_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_2_FULLNAME,



GL_ACCOUNT_HIER_HZ.LEVEL_3_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_4_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_5_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_6_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_7_FULLNAME, FS_HIERARCHY_DISCOVERY_HZ.CREDIT_FLAG, FS_HIERARCHY_DISCOVERY_HZ.DEBIT_FLAG, FS_HIERARCHY_DISCOVERY_HZ.LOWER_ACCT_LIMIT, FS_HIERARCHY_DISCOVERY_HZ.UPPER_ACCT_LIMIT, GL_ACCOUNT_DISCOVERY_HZ.LEAF_FLAG, GL_ACCOUNT_DISCOVERY_HZ.HIERARCHY_NAMEFROM GL_ACCOUNT_HIER_HZ, FS_HIERARCHY FS_HIERARCHY_DISCOVERY_HZ, GL_ACCOUNT_HIER GL_ACCOUNT_DISCOVERY_HZ, GL_ACCOUNT_MASTERWHERE (

GL_ACCOUNT_MASTER.CHART_OF_ACCTS_ID=GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID and GL_ACCOUNT_MASTER.GL_ACCOUNT_ID=GL_ACCOUNT_HIER_HZ.CURRENT_LEAF AND

GL_ACCOUNT_MASTER.HIERARCHY_NAME in ('ACCOUNT','CAUS')AND GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME = 'CAUS' ) AND (

GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=GL_ACCOUNT_DISCOVERY_HZ.HIERARCHY_NAME and GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=GL_ACCOUNT_DISCOVERY_HZ.CHART_OF_ACCTS_ID and GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=GL_ACCOUNT_DISCOVERY_HZ.CHILD_ID )

AND ( GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=FS_HIERARCHY_DISCOVERY_HZ.CHART_OF_ACCTS_ID and GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=FS_HIERARCHY_DISCOVERY_HZ.FS_VERSION_ID and GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=FS_HIERARCHY_DISCOVERY_HZ.CHILD_ID )

AND ( GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID = 'CAUS' AND ( GL_ACCOUNT_MASTER.HIERARCHY_NAME NOT IN ( '@PC', '@GL') ) AND GL_ACCOUNT_HIER_HZ.LEVEL_2_ID <>

GL_ACCOUNT_HIER_HZ.LEVEL_1_ID AND GL_ACCOUNT_HIER_HZ.LEVEL_3_ID <>



GL_ACCOUNT_HIER_HZ.LEVEL_4_ID )



Project Element Hierarchy Data DiscoveryView Project Element Hierarchies for a specified Parent Project Element and Project Element Hierarchy.


Equipment Hierarchy Data DiscoveryView Equipment Hierarchies for a specified Parent Equipment and Equipment Hierarchy.



Functional Location Hierarchy Data Discovery
View Functional Location Hierarchies for a specified Parent Functional Location and Functional Location Hierarchy.


Work Center Hierarchy Data DiscoveryView Work Center Hierarchies for a specified Parent Work Center and Work Center Hierarchy.




BOM Hierarchy Data DiscoveryView BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.



Organization Unit Data Discovery
View Organization Unit Hierarchies for a specified Parent Organization Unit(s).


Position Data DiscoveryView Position Hierarchies for the specified Parent Position(s).




Data AuditingThese reports allow users to view hierarchy data records that have failed validation in Data Services. This enables correction of the data in the SAP solutions source system. Nine data auditing reports are included with the SAP Master Data universe. These reports display data in validation tables as follows:

All data auditing reports are all similar in structure. Invalid Cost Center Hierarchy is show below as an example of the hierarchy data auditing reports.

Invalid Cost Center HierarchyShow Cost Center Hierarchy records that have failed validation in Data Services.

Report SQLSELECT DISTINCT COST_CNTR_HIER_BAD.PARENT_ID, COST_CNTR_HIER_BAD.PARENT_DESC, COST_CNTR_HIER_BAD.CTRL_AREA_ID, COST_CNTR_HIER_BAD.CHILD_ID,

Report Name Invalid Data Table

Invalid Cost Center Hierarchy COST_CENTER_HIER_BADInvalid Activity Hierarchy ACTIVITY_HIER_BADInvalid Cost Element Hierarchy COST_ELEMENT_HIER_BADInvalid Functional Area Hierarchy FUNCTIONAL_AREA_HIER_BADInvalid GL Account Hierarchy GL_ACCOUNT_HIER_BADInvalid Internal Order Hierarchy INTERNAL_ORDER_HIER_BADInvalid Profit Center Hierarchy PROFIT_CENTER_HIER_BADInvalid Project Element Hierarchy PROJECT_ELEMENT_HIER_BADInvalid Work Center Hierarchy WORK_CENTER_HIER_BAD



COST_CNTR_HIER_BAD.CHILD_DESC, COST_CNTR_HIER_BAD.DI_ERRORACTION, COST_CNTR_HIER_BAD.DI_ERRORCOLUMNS, COST_CNTR_HIER_BAD.LEAF_FLAG, COST_CNTR_HIER_BAD.LOAD_DATE, COST_CNTR_HIER_BAD.LOAD_TIME, COST_CNTR_HIER_BAD.ROOT_FLAGFROM COST_CNTR_HIER_BAD

Recommended table joins When analyzing data hierarchy data, you need to create joins between the dimension table and the hierarchy tables in the Rapid Mart. The following shows joins provided in the SAP Master Data universe.

Dimension Table Hierarchy Table Join Text

ACTIVITY ACTIVITY_HIER_HZ ACTIVITY.CTRL_AREA_ID=ACTIVITY_HIER_HZ.CTRL_AREA_ID and ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HZ.ACTIVITY_ID

ACTIVITY ACTIVITY_HIER_VR ACTIVITY.CTRL_AREA_ID = ACTIVITY_HIER_VR.CTRL_AREA_ID and ACTIVITY.ACTIVITY_ID = ACTIVITY_HIER_VR.CHILD_ID

BILL_OF_MATERIALS BILL_OF_MATERIALS_HIER_HZ

BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_OF_MATERIALS_HIER_HZ.BOM_CATEG_ID and BILL_OF_MATERIALS.BOM_ID=BILL_OF_MATERIALS_HIER_HZ.BOM_ID and BILL_OF_MATERIALS.ALT_BOM_ID=BILL_OF_MATERIALS_HIER_HZ.ALT_BOM_ID and BILL_OF_MATERIALS.BOM_NODE_ID=BILL_OF_MATERIALS_HIER_HZ.BOM_NODE_ID

BILL_OF_MATERIALS BILL_OF_MATERIALS_HIER_VR

BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_OF_MATERIALS_HIER_VR.BOM_CATEG_ID and BILL_OF_MATERIALS.BOM_ID=BILL_OF_MATERIALS_HIER_VR.BOM_ID and BILL_OF_MATERIALS.ALT_BOM_ID=BILL_OF_MATERIALS_HIER_VR.ALT_BOM_ID and BILL_OF_MATERIALS.BOM_NODE_ID=BILL_OF_MATERIALS_HIER_VR.CHILD_ID

COST_CENTER COST_CENTER_HIER_HZ COST_CENTER.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and COST_CENTER.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID



COST_CENTER COST_CENTER_HIER_VR COST_CENTER.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and COST_CENTER.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

COST_ELEMENT COST_ELEMENT_HIER_HZ

COST_ELEMENT.COST_ELEM_ID=COST_ELEMENT_HIER_HZ.COST_ELEM_ID and COST_ELEMENT.CHART_OF_ACCT_ID=COST_ELEMENT_HIER_HZ.CHART_OF_ACCT_ID

COST_ELEMENT COST_ELEMENT_HIER_VR

COST_ELEMENT.CHART_OF_ACCT_ID=COST_ELEMENT_HIER_VR.CHART_OF_ACCT_ID and COST_ELEMENT.COST_ELEM_ID=COST_ELEMENT_HIER_VR.CHILD_ID

COUNTRY_GROUP COUNTRY_GROUP_STATUS

COUNTRY_GROUP.COUNTRY_GRP_ID = COUNTRY_GROUP_STATUS.COUNTRY_GRP_ID

EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID

EQUIPMENT EQUIPMENT_HIER_VR EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID

FS_HIERARCHY GL_ACCOUNT_HIER_HZ GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_ID=FS_HIERARCHY.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_HZ.HIER_ID=FS_HIERARCHY.FS_VERSION_ID and GL_ACCOUNT_HIER_HZ.GL_ACCT_ID=FS_HIERARCHY.CHILD_ID

FS_HIERARCHY GL_ACCOUNT_HIER_VR GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_ID=FS_HIERARCHY.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_VR.HIER_ID=FS_HIERARCHY.FS_VERSION_ID and GL_ACCOUNT_HIER_VR.CHILD_ID=FS_HIERARCHY.CHILD_ID

FUNCTIONAL_AREA FUNCTIONAL_AREA_HIER_HZ

FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID

FUNCTIONAL_AREA FUNCTIONAL_AREA_HIER_VR

FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID

FUNCTIONAL_LOCATION FUNCTIONAL_LOCATION_HIER_HZ

FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID

FUNCTIONAL_LOCATION FUNCTIONAL_LOCATION_HIER_VR

FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID

GL_ACCOUNT_HIER GL_ACCOUNT_HIER_HZ GL_ACCOUNT_HIER_HZ.HIER_ID=GL_ACCOUNT_HIER.HIER_ID and GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_ID=GL_ACCOUNT_HIER.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_HZ.GL_ACCT_ID=GL_ACCOUNT_HIER.CHILD_ID




GL_ACCOUNT_HIER GL_ACCOUNT_HIER_VR GL_ACCOUNT_HIER_VR.HIER_ID=GL_ACCOUNT_HIER.HIER_ID and GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_ID=GL_ACCOUNT_HIER.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_VR.CHILD_ID=GL_ACCOUNT_HIER.CHILD_ID

GL_ACCOUNT_MASTER GL_ACCOUNT_HIER_HZ GL_ACCOUNT_MASTER.CHART_OF_ACCT_ID=GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_ID and GL_ACCOUNT_MASTER.GL_ACCT_ID=GL_ACCOUNT_HIER_HZ.GL_ACCT_ID AND GL_ACCOUNT_MASTER.HIER_ID in ('ACCOUNT',@Prompt('Select GL Account Hierarchy Code','A','GL Account\Hierarchy Name',mono,free)) AND GL_ACCOUNT_HIER_HZ.HIER_ID = @Prompt('Select GL Account Hierarchy Code','A','GL Account Hierarchy Hz\Hierarchy Name',mono,free)

GL_ACCOUNT_MASTER GL_ACCOUNT_HIER_VR GL_ACCOUNT_MASTER.CHART_OF_ACCT_ID=GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_ID and GL_ACCOUNT_MASTER.GL_ACCT_ID=GL_ACCOUNT_HIER_VR.CHILD_ID AND GL_ACCOUNT_MASTER.HIER_ID in ('ACCOUNT',@Prompt('Select GL Account Hierarchy Code','A','GL Account\Hierarchy Name',mono,free)) AND GL_ACCOUNT_HIER_VR.HIER_ID = @Prompt('Select GL Account Hierarchy Code','A','GL Account Hierarchy Vr\Hierarchy Name',mono,free)

INTERNAL_ORDER INTERNAL_ORDER_HIER_HZ

INTERNAL_ORDER.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID

INTERNAL_ORDER INTERNAL_ORDER_HIER_VR

INTERNAL_ORDER.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID

MATERIAL PRODUCT_HIERARCHY MATERIAL.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID

OBJECT_STATUS_HZ OBJECT_STATUS OBJECT_STATUS_HZ.OBJ_ID=OBJECT_STATUS.OBJ_ID

ORGANIZATION_UNIT ORGANIZATION_UNIT_HIER_HZ

ORGANIZATION_UNIT.ORG_UNIT_KEY =ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY

ORGANIZATION_UNIT ORGANIZATION_UNIT_HIER_VR

ORGANIZATION_UNIT.ORG_UNIT_KEY=ORGANIZATION_UNIT_HIER_VR.CHILD_KEY

PAYROLL_PERIOD PAYROLL_PERIOD_PARAMETER

PAYROLL_PERIOD.PERIOD_PARAMETER_ID = PAYROLL_PERIOD_PARAMETER.PERIOD_PARAMETER_ID




POSITION POSITION_HIER_HZ POSITION.POSITION_ID=POSITION_HIER_HZ.POSITION_ID

POSITION POSITION_HIER_VR POSITION.POSITION_ID=POSITION_HIER_VR.CHILD_ID

PROFIT_CENTER PROFIT_CENTER_HIER_HZ

PROFIT_CENTER.CTRL_AREA_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and PROFIT_CENTER.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID

PROFIT_CENTER PROFIT_CENTER_HIER_VR

PROFIT_CENTER.CTRL_AREA_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and PROFIT_CENTER.PROFIT_CNTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID

PROJECT_ELEMENT PROJECT_ELEMENT_HIER_HZ

PROJECT_ELEMENT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID

PROJECT_ELEMENT PROJECT_ELEMENT_HIER_VR

PROJECT_ELEMENT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID

WORK_CENTER WORK_CENTER_HIER_HZ WORK_CENTER.WORK_CNTR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_ID and WORK_CENTER.PLANT_ID=WORK_CENTER_HIER_HZ.PLANT_ID

WORK_CENTER WORK_CENTER_HIER_VR WORK_CENTER.WORK_CNTR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND WORK_CENTER.PLANT_ID=WORK_CENTER_HIER_VR.PLANT_ID



Universe

chapter

UniverseOverview5
Overview
Before we begin a detailed discussion of the Plant Maintenance Universes it is important to understand certain concepts that are common to any Rapid Mart Universe.• Universe Design Principles• Hierarchies• Plant Maintenance Specific HierarchiesThen we can discuss the details of the Universes. The SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions contains three universes. The first two are Business Content Universes organized around fact tables and dimensions in a classic star schema layout.• SAP Plant Maintenance Universe• SAP Service Master UniverseThe other is an Auxiliary Universe designed to facilitate data discovery and auditing within SAP solutions. It does not follow a star schema approach.• SAP Master Data UniverseAn additional section on customizing the SAP Plant Maintenance universe is also presented.• Customizing the Universe

Universe Design PrinciplesThe universe design principles presented below are designed to help you better understand universe content and how to use it.All Rapid Mart universes use the same design principles to ensure ease of use, and rapid creation of reporting solutions.


UniverseUniverse Design Principles 5

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. Optionally, a hierarchy may be associated with a dimension table. See diagram below for details

Dimension Table (Dim 1 - Dim 6): a table where the textual descriptions are stored. Optionally, a Dimension may have an associated hierarchy - such as Dim 6 in the diagram.Hierarchy: 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. Hierarchies are described in great detail later in this chapter.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. Fact tables can be detailed or summarized. These represent different levels of granularity. A detailed fact table has a finer granularity, typically transaction level detail. A summarized table aggregates the transaction data with fewer


UniverseUniverse Design Principles5

dimensions, and uses a grouping function (sum, average, maximum, minimum) to aggregate the measures (typically money and quantity -- see section on Measures below) by those dimensions. Fact tables can also be pivoted vertically or horizontally. The pivot point is typically the Fiscal Period, but other dimensions can be used. Pivoted measures are expressed for each pivot point. Horizontal tables have one row for a logical group of pivot points. For example all the profit values for all fiscal periods in a year appear in one row of the fact table, with separate columns for each profit value / fiscal period combination.Vertical tables have one row per pivot point. For example, the profit value for each fiscal period has a separate row in the fact table.Measures: numeric additive or semi-additive quantities or monetary amounts like: • PC DTL Hz Line Credit Amt Period 03 TRX - Profit Center Detail Horiz. -

Line Credit Amount for Fisc Period 3 in Transaction Currency• Line Debit Amt LOC - Financial Document Fact Line Debit Amount in

Local Currency.Objects: descriptive non-additive attributes used to describe the measure, and master data such as Monetary Currency Name, Unit of Measure, or Material Name.Additive Measure: a measure that can be summarized across all attributes; such as sales order value in global currencySemi-Additive Measure: measure that can be summarized only across selected dimensions, such as sales order quantityNon-Additive Measure: measures that can’t be summarized, such as net price.Attribute: descriptive information; can’t be aggregated, such as internal order number, material number, etc.Detail: a transaction attribute, such as Currency code, or Functional Area ID.Subject: in most cases associated with the fact table name. Examples are FINANCIAL_DOCUMENT_FACT, PROFIT_CENTER_FACT_VR.Business Function/Process: processes and functions in ERP applications that are captured when entering a transaction (Costing, Profitability, etc.). For the Universe, it is logical grouping of attributes by function or processes related to the subject. Examples are Activity Hierarchy, and Project Element dates.Common Dimension: a dimension table that is associated with multiple fact tables; such as Internal Orders, Time Dim, Currency, and GL Account.


UniverseUniverse Design Principles 5

Universe Table LayoutThe Rapid Mart data model uses star design principle. Fact tables are used to store measures and dimension tables to store attributes. 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.In some cases, like the Metadata universe, a star schema is not possible due to the nature of the data. In these cases the layout is presented as simply and logically as possible.

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. as shown below:

Aliases: Aliases are used when the same dimension describes different business processes. For example, the Time Dimension needs to be associated with different processes – document creation, and posting. All of these may be in the same subject area (fact table). In this case, there will be a Time 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. Example: SALES_ORDERS_FACT and BACKLOG_FACT.


UniverseUniverse Design Principles5

BACKLOG_FACT records are a subset of records in SALES_ORDERS_FACT they share the same primary key (sales order number, and sales order line item) and therefore the same granularity.

Inner Joins Only: The universe uses inner joins only. The Data Services job loads a default row in each dimension table. The row is populated with the default text (defined by a Data Services global variable) as primary key. Example: We load a row with default text in the Material dimension. When a financial document has no Material, we load that same default text as the foreign key from the financial document to the Material 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: In the diagram above the horizontal and vertical hierarchies are joined both to the corresponding dimension (Dim 6) and the fact table. The joins between hierarchy and dimension are short-cuts.Complex Joins and Objects: In this scenario we use the @prompt() function to allow users selecting appropriate constraints ar report run time. Example: join between GL_ACCOUNT_MASTER and GL_ACCOUNT_HIER_VR tables:

GL_ACCOUNT_MASTER.CHART_OF_ACCT_ID = GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_ID and GL_ACCOUNT_MASTER.GL_ACCT_ID = GL_ACCOUNT_HIER_VR.CHILD_ID AND GL_ACCOUNT_MASTER.HIER_ID in ('ACCOUNT',@Prompt('Select GL Account Hierarchy Code','A','GL Account\Hierarchy Name',mono,free)) AND GL_ACCOUNT_HIER_VR.HIER_ID = @Prompt('Select GL Account Hierarchy Code','A','GL Account Hierarchy Vr\Hierarchy Name',mono,free)

Default Coded Joins and Objects: This occurs when an object or join needs to be restricted to certain values. A default code is introduced to restrict the object to appropriate values. Example: the “Line Debit Amt LOC” measure for Financial Documents. Here the Debit / Credit indicator is restricted to “S” to ensure selection of only “Debit” values:

SUM(Case when FINANCIAL_DOCUMENT_FACT.DR_CR_ID = 'S' then FINANCIAL_DOCUMENT_FACT.AMT_LOC else 0 end)


UniverseHierarchies 5

TechniquesThese are advanced technique objects 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. 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 sales in a certain product line for each quarter this year. However, the product line had no sales 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: Their purpose is to provide an additional object that can be used in a display block. An example is a label that returns total company sales, where a normal query would only provide breakdowns by some category.Blanks are coded to ‘ ‘ (a space). Normally, this text is the same as the name of the object.

• Hyperlink Start: provides a starting point for hyperlink jumps (for example to details in another report). Used in a Java environment.

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.


UniverseHierarchies5

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 dimensions of each universe and in their own display screen in Web Intelligence (as shown below).Web Intelligence- Location of Rapid Mart Hierarchies



Note: The screenshot above is an example from the SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions.

Geographic HierarchiesThese allow you to organize reports by the geographic location (or address) of a dimension. Examples are:

• Company Geography• Cost Center Geography• Profit Center Geography• Vendor Geography

Time Dimension and Fiscal Period Hierarchies

Time DimensionThe Time Dimension allows you to organize reports by calendar attributes and fiscal periods for a single Fiscal Year Variant. The Fiscal Year Variant is determined by the default Company Code (global variable $G_CCODE) in the Rapid Mart load job. Attributes such as calendar year, calendar month as well as fiscal year, and fiscal period are available. It is granular to the calendar date level. Examples are:

• Posting Date Time Dimension• Creation Date Time Dimension• Document Date Time Dimension

Fiscal Period DimensionThe Fiscal Period Dimension allows you to organize reports by the fiscal and calendar periods across multiple Fiscal Year Variants. Attributes such as calendar year, calendar month as well as fiscal year, and fiscal period are available. Granularity is at the Fiscal Year, Fiscal Period, and Fiscal Variant level. Examples are:

• Controlling Area Fiscal Periods• Company Code Fiscal Periods

Material Product HierarchyThis hierarchy organizes materials in reports by the SAP solutions Product Hierarchy.


Horizontal & Vertical Hierarchies
The remaining hierarchies used across Rapid Marts are organized into Vertical and Horizontal tables. They can be sourced from a variety of different tables and structures in SAP solutions. In general, Rapid Marts simplify this complexity by presenting a uniform view, regardless of the source or organization of that source in SAP solutions.

Activity Hierarchy ExampleWe will use Activity as an example to illustrate how vertical and horizontal hierarchies work together. The principles in this example holds true for any hierarchy, regardless of its source in SAP solutions.The illustration below shows a sample set of Activities 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 both SAP solutions and the Rapid Mart.



Horizontal Hierarchy StructureHorizontal 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 structure for Activities is the Activity Hierarchy Hz class, and the corresponding ACTIVITY_HIER_HR 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. Note: Be careful of the ragged hierarchy nodes. If your query simply selects for Activity ID = 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 (P1000 or P2000) to uniquely identify the hierarchy. In this case, you could also specify the Level 1 ID (A1000 or A3000) to uniquely identify the hierarchy.Note: Be careful of Primary Key violations. The Horizontal Hierarchy tables have an arbitrary limit of how may levels of hierarchy are extracted. If your data contains more levels than the limit, you can have a primary key violation when loading horizontal data.



The primary key for a horizontal hierarchy contains all the level id’s (LVL_00_ID to LVL_xx_ID). Where “xx” is the limit set in Data Services. In cases where there are more than “xx” levels in the hierarchy there are two choices• Change the primary key into a non-unique index.• Customize the hierarchy to include the missing levels; expanding the

horizontal table and its primary key accordingly.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) have their Activity ID propagated to the lowest Level ID of the hierarchy starting with the Level 1 ID. Leaf level 2 nodes are 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..

Child (leaf) node propagation allows creating reports with indented listings of Cost Elements, Cost and Profit 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 Activity Hierarchy Vr class, and the corresponding ACTIVITY_HIER_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 “A1000” 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 Services documentation for the Hierarchy Flattening Transform, Pivot Transform, and Reverse Pivot Transform.


Hierarchy Report Generation
When you choose the “Select Single Parent Activity for Group (Vertical Hierarchy)” filter in a report, you are prompted to “Select a Single Parent Activity for Group” at run time. Entering “A1000” 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 “Activity Hierarchy Hz” class in the same query, the results will show the entire “family” structure for the selected Activity Hierarchy Group. Thus, the vertical hierarchy gives us the selection criteria (via the filter) and the horizontal hierarchy gives us the report contents.Note: We recommend using “Select Single Parent Activity Group (Vertical Hierarchy)” filter only with hierarchy data discovery reports. See Hierarchy Data Discovery in Reports Chapter for more details.

VerticalHierarchySubset forA1000



Sample Report for Activity (Vertical Hierarchy):

Report Generation - Propagation of Leaf NodesAs 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.



Sample Report (Propagation of Leaf Nodes):

Hierarchy FiltersHierarchy filters allow you to restrict the results of your reports to subsets of the various hierarchies. They can also be used to filter ragged hierarchies by allowing you to select only one parent hierarchy chain.In this case, we’ll use the GL Account Hierarchy as an example. All hierarchies work in a similar method, but the GL Account Hierarchy has the added complexity of combining more than one hierarchy from SAP solutions. It has additional filters not found in the other hierarchies to deal with this situation.



The filters appear below the Fact Table Classes in any universe. Those for GL Account Hierarchy appear as shown below:

Unique GL Account Hierarchy FiltersThese filters, highlighted above, are unique to the GL Account Hierarchy. Because this hierarchy has multiple sources, these extra filters allow you to restrict data in your reports to one specific source hierarchy name. Values are:• @PC - identifies GLPCT-RACCT - The EC-PCA Profit Center GL

Account Hierarchy• @GL - identifies GLT0-RACCT - The FI Standard Ledger GL Account

Hierarchy • Any other value - identifies a FS (Financial Statements) Hierarchy.The names are configurable during setup of ETL loading process. If you customize the GL Account Hierarchy by adding additional hierarchy sources, you would add a new source hierarchy name.


Single Parent Filters
All hierarchies have a similar set of filters. The filters numbered from 0 to 4 limit to a single parent hierarchy, and they ensure ragged hierarchies return only one parent chain.The vertical filters choose a single parent hierarchy. They do not limit the level of the hierarchy, so they do not ensure ragged hierarchies return only parent chain. These filters are used only in hierarchy data discovery reports.

Multiple Parent FiltersAll hierarchies have a similar set of filters. The filters numbered from 0 to 4 select multiple parent hierarchies. Due to selection of multiple parents, you may get duplicate records for ragged hierarchies. To ensure the elimination of ragged hierarchies use the Single Parent Filters numbered 0 to 4 (above).The vertical filters choose a single parent hierarchy. They do not limit the level of the hierarchy, so they do not ensure ragged hierarchies return only parent chain. These filters are used only in hierarchy data discovery reports.

Invalid HierarchiesThe hierarchies loaded from SAP solutions could have invalid records. These records are allowed by SAP solutions, but cause errors when used in the Rapid Mart. Therefore, they are excluded from the normal hierarchy tables, and listed here.A record is invalid when a descendant (child) record is in a loop so that it is also its own ancestor (parent) record. SAP solutions allows this, but it is not possible to use these records in the Rapid Mart.If you correct these records in SAP solutions, they will load properly on the next execution of the Data Services load job.



Example: In the example below, “Activity 1" is both the parent and child of “Activity 2”.

Invalid Hierarchies have no measures or filters. They are not linked to any subject areas. They are represented as a way identifying the invalid records that cannot be loaded from SAP solutions.

Invalid Hierarchies Subject Area ClassesInvalid Hierarchy entries appear in their own set of classes within the universe as shown in the example below:Invalid Hierarchies Subject Area Classes:

Invalid Hierarchies LayoutThe Invalid Hierarchy tables are not part of any star schema. Instead, they are grouped with their corresponding dimension tables. The name of each table containing invalid records has the suffix “_BAD”. They appear as shown below in the universe graphical representation.

Activity1

Activity2 Activity3

Activity5Activity1 Activity4 Activity6

(as Parent)

(as Child)



Invalid Hierarchies Layout:

Note: The screenshot above is an example from the SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions.


UniversePlant Maintenance Specific Hierarchies 5

Plant Maintenance Specific Hierarchies

Accounting HierarchiesThe Plant Maintenance Rapid Mart has several Accounting Hierarchy dimensions that report financial breakdowns in the same manner as SAP solutions. These all appear as Set Hierarchies (SAP solutions transaction GS03).These hierarchies are organized in both horizontal and vertical format. They are listed here with their corresponding SAP solutions Table and Column. The Table and Column represent the lowest level (leaf level) in each hierarchy:

For each of the 6 hierarchies, two sub-classes within in each dimension represent the vertical and horizontal hierarchies. Each hierarchy also has a sub-class for invalid hierarchy records. See “Invalid Hierarchies” on page 182 for more details.

Additional HierarchiesThese additional hierarchies, for the Plant Maintenance Rapid Mart are also organized both horizontally and vertically, but not maintained by transaction GS03. Instead, they are associated with specific master data records, including the two technical objects (equipment and functional location):

Hierarchy Name Table and Column

Activity CCSS-LSTARCost Center CCSS-KOSTLCost Element CCSS-KSTARFunctional Area GLFUNCT-RFAREAInternal Orders CCSS-AUFNR

Hierarchy Name Source Tables

Classification KSSK, TCLAEquipment EQUI, EQUZFunctional Location IFLOT, ILOAProject Element PRHIWork Center CRHD, CRHH, CRHS


UniversePlant Maintenance Specific Hierarchies5

Of these hierarchies only Project Element can have invalid records in SAP solutions. See “Invalid Hierarchies” on page 182 for more details.


UniverseSAP Plant Maintenance Universe 5

SAP Plant Maintenance UniverseThe SAP Plant Maintenance Universe gathers information from the SAP solutions Plant Maintenance module.Maintenance in SAP solutions is performed on the technical objects (functional locations and equipment) throughout your enterprise.The maintenance process in SAP solutions is the fulfillment of service notifications, and service orders with their associated operations and confirmations. It also encompasses the maintenance of the technical objects as master data with their associated classification and characteristics. Finally, the module also captures costs related to service orders when confirmations are posted. To support these processes SAP solutions uses Company Code, Customers, Activity, Cost Center, Functional Area, Functional Location, Fiscal Periods, Defect Catalogs, other master data, and numerous reference data. In some cases these master data are organized into hierarchy (or tree) structures.The SAP Plant Maintenance universe is a reflection of this complexity. At this writing, it has:• 252 classes• 2326 objects• 151 conditions• 86 tables• 16 alias• 355 joins• 7 contexts• 16 hierarchiesThe 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 areas. They are:• Universe Objects & Classes• Common Dimensions• Service Notification• Service Order• Service Operation• Service Confirmation


UniverseSAP Plant Maintenance Universe5

• Service Cost Summary (Horizontal)• Service Cost Summary (Vertical)• MTBR and MTTR• Filters & Techniques• Universe Validation



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 classes, sub-classes and all objects they contain are organized alphabetically for ease of navigation. The top level classes are shown below:



Measures: The first Top Level class represents the Measures as described in “Universe Terminology” on page 167. Measures are grouped into sub-folders that represent the various monetary and quantity amounts of the fact tables in the star schemas. Each subject area is further divided into classes by types of measure specific to the subject area.Common Dimensions: These top level classes appear after the Measures. These are the dimensions used in common by more than one subject area. These are sub-divided into classes for each specific dimension table. For example, the Organization Structure class has sub-classes for Company Code, and Controlling Area. 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.Fact Tables: Following the Dimensions are group of Top Level classes, one for each subject area (also called fact table or star schema) in the universe.These subject area classes are further divided into classes that are logical groupings of fact table attributes. For example, the “Notification - Dates and Fiscal Periods” class under “NOTIFICATION” contains the dates that are important for tracking plant maintenance notifications.Filters & Techniques: Filters: This top level folder contains pre-defined conditions (organized by subject area) for use in any report. See details about specific “Hierarchy Filters” on page 22Techniques: These are advanced technique objects that have developed for the Web Intelligence reports. See “Techniques” on page 171 for details.

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



Plant Maintenance Common Dimension Classes (1 of 2)



Plant Maintenance Common Dimension Classes (2 of 2)



ACTIVITYPhysical measure of the activity output/production in a cost center. Examples of Controlling activities include:

• number of units produced • hours • machine times • production times

Activities in Controlling can be internal or external. Activity Hierarchies are presented stacked vertically and flattened horizontally.

CAPACITYThe ability of a work center to perform a task. Capacities are differentiated according to capacity category. They are arranged in a hierarchy under a work center.

CLASSIFICATIONSSystem that is used to describe objects on the basis of characteristics by grouping together into classes (i.e. classifying) objects according to freely definable criteria.Objects can be retrieved with the aid of classes and the characteristics defined in the classes, enabling objects that are identical or similar from a point of view of their characteristics to be retrieved as quickly as possible.In the Plant Maintenance Rapid Mart, the classes are restricted to Functional Location and Equipment. These are the two types of technical objects used in PM.

• Equipment Classification• Equipment Class Hier Hz• Equipment Class Hier Vr

• Functional Location Classification• Functional Location Class Hier Hz• Functional Location Class Hier Vr

COST CENTEROrganizational unit within a controlling area that represents a defined location of cost incurrence. The definition can be based on:

• Functional requirements • Allocation criteria • Physical location • Responsibility for costs



Cost center hierarchies presented stacked vertically and flattened horizontally. Cost center contact numbers, and geography are also included.

COST ELEMENTA cost element classifies the organization's valuated consumption of production factors within a controlling area. SAP solutions maintains both primary and secondary cost elements.

CUSTOMERCustomers are the companies and individuals to whom your company sells goods and services.

DOCUMENT ATTRIBUTESMaster data associated with the various “documents” found in SAP solutions. These include Document Categories, Document Types, and separate class groupings for Accounting Documents, Sales Documents and Purchasing Documents. Document Attributes subclasses include:

Document CategoryDocument Category combines all document categories in one table, including: Financial, Internal Order, Notification, Purchasing, and Sales. The following document category aliases are also included as classes under DOCUMENT ATTRIBUTES:

• Internal Order Document Category - A technical classification criterion for orders. The order category determines the SAP application to which an order belongs, and controls the functions by which an order can be processed.

• Notification Document Category - A key that identifies notification types in an application component. Notification categories include:- Quality notification in the Quality Management (QM) application component - Maintenance notification in the Plant Maintenance (PM) application component - Service notification in the Customer Service (CS) application component

Document TypeDocument Type combines all document categories in one table, including: Internal Order, Sales, Purchasing, Billing, Delivery, Financial, Special Ledger, and Notification document types. The following document type aliases are also included in the SAP Master Data universe:



• Internal Order Document Type - A tool that categorizes orders according to purpose. The order type contains information which is necessary for managing orders. Order types are client-specific. The same order type can be used in all controlling areas in one client. Examples: production orders, maintenance orders (Plant Maintenance Service Orders), capital investment orders, and marketing orders.

• Notification Document Type - A key that determines the origin, content, and other features of service, maintenance, and quality notifications. The following notification types exist in the standard SAP Applications system:- Maintenance notifications, including malfunction and activity reports and maintenance requests - Service notifications, including problem notifications, service requests, and activity reports - Quality notifications, including complaints against the vendor, customer complaints, and internal problems

ACCOUNTING DOCUMENT ATTRIBUTES• Financial Record Category - Categorization for a financial

document.• Financial Record Type - Special Ledger Record Types (Domain

RRCTY) from table DD07T and Cost/Plant Maintenance value types from CO_WRTTP domain of DD07T table

• EQUIPMENT - & Associated Hierarchy - An individual, physical object that is maintained as an autonomous unit.

• FUNCTIONAL LOCATION - & Associated Hierarchy - An organizational unit in Logistics that structures the maintenance objects of a company according to functional, process-oriented, or spatial criteria. A functional location represents the place at which a maintenance task is performed.

• INTERNAL ORDERS - & Associated Hierarchy - Production Orders, Service Orders, and associated hierarchy. Object used to monitor costs and, in some instances, revenues for an organization. Internal orders can be used to:1. Monitor the costs of short-term measures 2. Monitor the costs and revenues related to a specific service 3. Monitor ongoing costs Internal orders are divided into the following categories:1. Overhead orders



2. Capital investment orders 3. Accrual orders4. Orders with revenues.

• MATERIAL - The Materials Master in SAP solutions. Goods that are the subject of business activity. The material can be traded, used in manufacture, consumed, or produced. They can also be bought or sold.This class also contains Material by Plant, and Materials (Product) Hierarchy.

• MONETARY DIMENSIONS• Monetary Currencies - A medium of exchange in current use within a

particular country to valuate goods and services. For example the US Dollar, the Euro, the Japanese Yen, etc. The Rapid Mart includes:• Controlling Area Currency• Local (Company Code) Currency• Transaction (Document) Currency

OBJECTObject is a very generic term in SAP solutions. It can mean anything from an internal identifier for equipment in Plant Maintenance, to a way of categorizing cost in Controlling. The object class groups these various kinds of objects together for easy reference with these sub-classes:

Object ClassThe object class categorizes Controlling objects according to their business function and enables you to analyze cost flows within Controlling from different business perspectives. The following object classes are available: overhead, production, investment, profitability analysis and sales While certain object types automatically belong to a particular class (for example, cost centers belong to the "Overhead" class), others need to be explicitly assigned to an object class in their master record (this is the case with internal orders and work breakdown structure elements, for example).In addition to the functional area, the object class is required to determine or explain certain values in the external accounting components. Object Class (from Domain SCOPE_CV).



Object TypeA type of object that you process in the Engineering Workbench. An object can, for example, be a type of "task list type," "item," or "component assignment." Object Type (from Domain OBART).

ORGANIZATION STRUCTUREVarious components that classify transaction documents within your business enterprise. These include:

Business ActivityBusiness activity attributes from T022/T022T.

Business AreaAn organizational unit of financial accounting that represents a separate area of operations or responsibilities within an organization and to which value changes recorded in Financial Accounting can be allocated. Business areas are used in external segment reporting (over and above company codes) based on the significant areas of operation (for example, product lines) of a business enterprise. A segment is an isolated area of activity.

Chart Of AccountsA classification scheme consisting of a group of general ledger (G/L) accounts.A chart of accounts provides a framework for the recording of values to ensure an orderly rendering of accounting data. The G/L accounts it contains are used by one or more company codes.For each G/L account, the chart of accounts contains the account number, the account name, and technical information.A chart of accounts must be assigned to each company code. This chart of accounts is the operative chart of accounts and is used in both financial accounting and cost accounting.

Company CodeThe smallest organizational unit of Financial Accounting for which a complete self-contained set of accounts can be drawn up for purposes of external reporting. This includes recording of all relevant transactions and generating all supporting documents required for financial statements.

Controlling AreaAn organizational unit within a company, used to represent a closed system for cost accounting purposes. A controlling area may include single or multiple company codes that may use different currencies.



These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area.

Planning GroupThe customers and vendors in cash management and forecast are assigned to a planning group that reflects certain characteristics, risks or the type of business relationship in question, for example:• Customer - Bank collection • Customer - Crisis area • Vendor: - Member of a consolidation group

PlantIn Logistics a plant is an organizational unit for dividing an enterprise according to production, procurement, maintenance, and materials planning. A place where materials are produced, or goods and services are provided.

Plant LocationPlant location attributes.

PEOPLEPeople dimensions describing persons with specific job functions in an operational setting:

• Service Person - An employee who is actively involved in troubleshooting, maintenance, and repair activities.

PRODUCTION & PLANT MAINTENANCEAttributes associated Production Planning and Plant Maintenance functions. The sub-classes include:

Control KeyA key that specifies how an operation or a sub-operation is processed in functions such as orders, costing or capacity planning.The following are examples of processing types managed by a control key for operations and sub-operations:

• External processing • Completion confirmation • Printing • Scheduling • Costing



Maintenance Activity TypeA key for the type of maintenance activity provided. Activities are divided into repairs, shutdowns, regular activities, inspections and so on.In cost evaluations, for example, total costs or number of orders for each technical object, you can classify data according to maintenance activity type.

Maintenance PriorityThe relationship between the order priority from a maintenance order and the requirement urgency.

Malfunction CauseOne of 3 pre-defined notification catalog objects - Malfunction Cause. Describes the incident or circumstances responsible for a malfunction

Malfunction DamageOne of 3 pre-defined notification catalog objects - Malfunction Damage. Describes the breakage sustained by a technical object

Malfunction EffectDescribes the consequences of the malfunction in the technical object’s performance. Description of malfunction effects from T357A_T

Malfunction Object PartOne of 3 pre-defined notification catalog objects - Malfunctioning Object Part. Describes the physical location of the malfunction.

NotificationA data record with which a user informs the Plant Maintenance, Quality Management, or Customer Service department about an occurrence.The following notification categories are available:

• Maintenance notifications • Service notifications • Quality notifications

Operation SuitabilityKey suitability required for carrying out the operation (for example, welding certificate or NC programming course) - from T423T

System ConditionSystem Condition descriptive attributes from T253M_T.

Variance CategoryA classification of variances based on their cause.



You can calculate the following variance categories on the input side:• Scrap variances (only in Product Cost Controlling) • Input price variances • Resource usage variances • Input quantity variances • Remaining input variances

You can calculate the following variance categories on the output side:• Fixed cost variance (only in Overhead Cost Controlling) • Mixed price variance (only in Product Cost Controlling) • Output price variance • Output quantity variance (only in Overhead Cost Controlling) • Lot size variance (only in Product Cost Controlling) • Remaining variances

PROFIT CENTEROrganizational unit in Accounting that reflects a management-oriented structure of the organization for the purpose of internal control.Operating results for profit centers can be analyzed using either the cost-of-sales approach or the period accounting approach.By analyzing the fixed capital as well, you can expand your profit centers for use as investment centers.

PROJECT ELEMENT (WBS)Also called WBS (Work Breakdown Structure). Hierarchical outline of an undertaking described in the project definition. The work breakdown structure (WBS) forms the basis for the organization and coordination of a project. A WBS consists of various WBS elements. The WBS elements describe specific tasks or actions in the project to be carried out within a defined time period.

TIME RELATED DIMENSIONSTime related dimensions include relevant time dimensions, fiscal period dimensions, and Calendar dimensions. This class includes the

Time DimensionsAllow you group data in reports by standard time measurement units such as month, year, and quarter. The following aliases of time are included in this universe:

• Create Date Time Dim



• Notification Date Time Dim

FISCAL PERIOD DIMENSIONSFiscal periods within a fiscal year for which transaction figures are updated. Every transaction that is posted is assigned to a particular posting period. The transaction figures are then updated for this period. Fiscal years are divided into halves, quarters, periods, and months for reporting purposes. Fiscal years and fiscal calendars are defined by the fiscal year variant.There can be 12 regular fiscal periods, and 4 special processing periods. Fiscal periods are numbered 1 - 12 for regular periods, 13 -16 for special periods.

UNIT OF MEASURE (UOM)Unit that enables you to determine the size of a quantity of material. Examples: Each, Piece, Dozen, Kilogram, ounce, liter, centimeter, minute, hour, etc. It includes these sub-classes:

• Downtime Unit of Measure• Duration Unit of Measure• Work Unit of Measure

VENDORBusiness partner to whom amounts are payable for goods delivered or services performed. Examples of such services/goods include: Goods acquired, Business services received, The transfer of a right.VENDOR also contains the following subclasses:

• Vendor Categories• Vendor Contact Numbers• Vendor Geography• Vendor by Company

WORK CENTER An organizational unit that defines where and when an operation should be carried out. The work center has a particular available capacity. The activities performed at or by the work center are valuated by charge rates, which are determined by cost centers and activity types. Work centers can be:

• Machines • People • Production lines • Groups of craftsmen


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 table below is a cross-reference matrix of common dimensions and subject areas showing exactly which common dimensions to use with each subject area.

Dimension Table MTBR MTTR FACT

NOTIFI-CATION

FACT

SERVICE CONFIRM-

ATION FACT

SERVICE COST

SUMMARY FACT

SERVICE OPER-ATION FACT

SERVICE ORDER FACT

Activity & Hierarchy X X

Business Activity X

Business Area X X X X X X

Capacity X

Chart Of Accounts X

Classification Hierarchy X X X X X X

Company Code X X X X X X

Control Key X

Controlling Area X X X X X X

Cost Center & Hierarchy X X X X X X

Cost Element & Hierarchy X

Currency X X X X

Customer X X X

Document Category X X X X X X

Document Type X X X X X X

Equipment & Hierarchy X X X X X X

Financial Record Category X

Financial Record Type X

Fisc Period X - vertical only

Functional Area & Hierarchy X X X X


X X X X X X

Internal Order & Hierarchy X X X X X X

Internal Order Status X X

Maintenance Activity Type X X X X

Maintenance Priority X X X X X X

Malfunction Cause X



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.

Service NotificationA notification informs the Plant Maintenance, Quality Management, or Customer Service department about an occurrence warranting their attention. This may be notification of a malfunction, upgrade due, or other action needed to keep a technical object operational.

Malfunction Damage X

Malfunction Effect X X

Malfunction Object Part X

Material & Product Hierarchy

X X X X X X

Material By Plant X X X X X X

Notification X X X X

Object Class X

Object Type X

Operation Suitability X X

Planning Group X X X X X

Plant X X X X X X

Plant Location X X X X X

Profit Center & Hierarchy X X X X

Project Element & Hierarchy X X X X

Service Person X X X X

System Condition X X X X

Time Dim X X X X X

Unit Of Measure X X X

Variance Category X

Vendor X

Vendor By Company X

Work Center & Hierarchy X X X X X X

Dimension Table MTBR MTTR FACT

NOTIFI-CATION

FACT

SERVICE CONFIRM-

ATION FACT

SERVICE COST

SUMMARY FACT

SERVICE OPER-ATION FACT

SERVICE ORDER FACT


Service Notification Measures
The Service Notification measures contain all additive and semi-additive measures for Service Notification. They appear as shown below in the universe:Service Notification Measures

Notification MeasuresContains the notification related measures.• Notification - Qty Measures - Contains the downtime measure• Notification - Time Measures -

• Notification - Complete - Time to complete notification in Days, Hours, Minutes. Also contains Min, Max, and Average values for completion time

• Notification - Downtime - Time technical object was inoperative in Days, Hours, Minutes. Also contains Min, Max, and Average values for downtime.

• Notification - Required - Time required for repair in Days, Hours, Minutes. Also contains Min, Max, and Average values for repair time.

Service Notification Subject Area ClassesThe Notification subject area classes contain all remaining objects for Notification. They appear as shown below in the universe



Service Notification Subject Area Classes

NOTIFICATIONContains primary key elements for service notification and the following sub-classes:• Notification - Additional Details (Ids) - the foreign keys to the various

associated dimensions• Notification - Additional Details (Descriptive) - descriptive attributes

including the various “flags” associated with the notification.• Notification - Dates and Fiscal Periods - various “start” and “end” dates

associated with the notification• Notification - Values -

• Notification - Quantities - Raw quantity downtime in notification’s unit of measurement.

• Notification - Time - Un-aggregated values (not summed, averaged, etc.) for: • downtime• repair time• completion time

Service Notification Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designer



Service Notification Star Schema

Service OrderMaintenance Orders (called Service Orders in the Rapid Mart) document the necessary steps to repair the malfunction, or to complete the tasks requested in the notification. They serve as a cost collector for material and labor charges. They also record the time spent in the maintenance activities.

Service Order MeasuresThe Service Order measures contain all additive and semi-additive measures for Service Orders. They appear as shown below in the universe:



Service Order Measures

Service Order MeasuresContains the service order related measures.• Service Order - Time Measures - contains Variance (actual vs.

scheduled time) amounts in days, hours, and minutes• Service Order - Actual - Actual times to complete the service order in

days, hours, minutes. Also contains average, min and max values.• Service Order - Basic - The basic completion time is the planned time to

complete an order of an including any floating time. Basic completion times for the service order in days, hours, minutes. Also contains average, min and max values.

• Service Order - Forecast - Forecasted or planned times to complete the service order in days, hours, minutes. Also contains average, min and max values.

• Service Order - Scheduled - Scheduled times to complete the service order in days, hours, minutes. Also contains average, min and max values.

Service Order Subject Area ClassesThe Service Order subject area classes contain all remaining objects for service orders. They appear as shown below in the universe



Service Order Subject Area Classes

SERVICE ORDERContains primary key elements for the service order and the following sub-classes:• Service Order - Additional Details (Ids) - the foreign keys to the various

associated dimensions• Service Order - Additional Details (Descriptive) - descriptive attributes

including the various “flags” • Service Order - Dates and Fiscal Periods - various “start” and “end”

dates associated with the service order.• Service Order - Monetary Currency - the transaction currency identifier• Service Order - Values -

• Service Order - Time - Actual, basic, forecast, and scheduled completion times in days, hours, minutes (without aggregation).

Service Order Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designer



Service Order Star Schema

Service OperationService operations to describe the individual maintenance tasks to be performed. The operation includes the time, the work center, and other controlling information for an individual maintenance task. In the operation text you can describe how the work should be done.

Service Operation MeasuresThe Service Operation measures contain all additive and semi-additive measures for Service Operations. They appear as shown below in the universe:



Service Operation Measures

Service Operation MeasuresContains the service operation related measures.• Service Operatn - Qty Measures - Average quantities for duration,

actual, forecast, and scheduled work.• Service Operatn - Time Measures - contains the variance (actual vs.

scheduled) in days, hours, minutes.• Service Operatn - Actual - days, hours, and minutes for actual

execution of operation. Includes min, max, and average values.• Service Operatn - Scheduled - days, hours, and minutes for

scheduled execution of operation. Includes min, max, and average values.

• Service Operatn - TRX Currency Measures - total cost and material cost of the operation in transaction currency.

Service Operation Subject Area ClassesThe Service Operation subject area classes contain all remaining objects for service operations. They appear as shown below in the universe



Service Operation Subject Area Classes

SERVICE OPERATIONContains primary key elements for the service operation and the following sub-classes:• Service Operatn - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Service Operatn - Additional Details (Descriptive) - descriptive

attributes including the various “flags” • Service Operatn - Dates and Fiscal Periods - various “start” and “end”

dates associated with the service operation.• Service Operatn - Monetary Currency - the transaction currency

identifier• Service Operatn - Values -

• Service Operatn - Quantities - raw quantity values for duration, actual work, forecast work, and scheduled work

• Service Operatn - Time -actual and scheduled execution times in days, hours, minutes (without aggregation).

• Service Operatn Amts - Transaction Currency - total cost and material cost of the operation in transaction currency.

Service Operation Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designer



Service Operation Star Schema

Service ConfirmationA confirmation documents the status of the processing of operations for a maintenance or service order. It is a part of order monitoring. You use confirmations to document:• From which work center the operation was performed • Who performed the operation • That operations or sub-operations were started or executed • When the work was started and when it was completed • How the work is progressing



• How high are the costs for internal processing • What materials were used • Which services were executed internally • What measurement or counter readings were entered for the technical

objects during or after execution • Whether and where pieces of equipment were dismantled from, or

installed at functional locations • The extent to which the order has been processed • Where additional capacity is needed and where surplus capacity can be

reduced • Which technical data should be retainedConfirmations can also be used to track various time related activities in maintenance order processing, for example:• How long the work took and the period in which it occurred• How much longer work must continue• How much of the operation time was used (duration)• When is the operation expected to be completedConfirmations can be partial or final.

Service Confirmation MeasuresThe Service Confirmation measures contain all additive and semi-additive measures for Service Confirmations. They appear as shown below in the universe:Service Confirmations Measures

Service Confirmation MeasuresContains the confirmation related measures.



• Service Confirm - Qty Measures - Average quantities for duration, actual, remaining work

• Service Confirm - Time Measures - contains the variance (execution vs. forecast) in days, hours, minutes.• Service Confirm - Execution - days, hours, and minutes for actual

execution. Includes min, max, and average values.• Service Confirm - Forecast - days, hours, and minutes for forecast

execution. Includes min, max, and average values.

Service Confirmation Subject Area ClassesThe Service Confirmation subject area classes contain all remaining objects for service confirmations. They appear as shown below in the universeService Confirmation Subject Area Classes

SERVICE CONFIRMATIONContains primary key elements for the service confirmation and the following sub-classes:• Service Confirm - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Service Confirm - Additional Details (Descriptive) - descriptive

attributes including the various “flags”.• Service Confirm - Dates and Fiscal Periods - various “start” and “end”

dates associated with the service confirmation.• Service Confirm - Monetary Currency - the transaction currency

identifier



• Service Confirm - Values - • Service Confirm - Quantities - raw quantities for Actual Duration,

Actual Work, Work remaining• Service Confirm Amts - Time - Forecast completion, and execution

times in days, hours, minutes (without aggregation).

Service Confirmation Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designerService Confirmation Star Schema


Service Cost Summary (Horizontal)
The Service Order cost Summary extracts information about the cost (planned, and actual) to complete Service Orders. Each maintenance Service Order can include actual cost and an estimate of the cost to complete the Service Order. SAP solutions calculate planned costs after the resources and capacities are planned for that Service Order. Actual costs are posted at confirmation time, and can be analyzed after work is completed. SAP solutions supports cost analysis of plant maintenance at two levels:• Cost element level, through the controlling (CO) module• Value category level, through the plant maintenance (PM) moduleThe horizontal table carries one row per fiscal year with separate fields (columns) for values in each fiscal period in the year upto 16 periods.

Service Cost Summary Hz. MeasuresThe Service Cost horizontal measures contain all additive and semi-additive measures for horizontal service costs. They appear as shown below in the universe:Service Cost Summary Hz. Measures

Service Cost Summary HZ MeasuresContains measures related to service cost summary horizontal.• Service Cost Sum Hz - TRX Currency Measures - • Service Cost Sum Hz - Actual Measures - Actual costs

Beginning Balance for fiscal year.PTD balances (fiscal periods 1 - 16)QTD balances (quarters 1 - 4)YTD balance



• Service Cost Sum Hz - Budget Measures - Budget costsBeginning Balance for fiscal year.PTD balances (fiscal periods 1 - 16)QTD balances (quarters 1 - 4)YTD balance

Service Cost Summary Hz. Subject Area ClassesThe Service Cost horizontal subject area classes contain all remaining objects for Service Cost in horizontal representation. They appear as shown below in the universeService Cost Summary Hz. Subject Area Classes

SERVICE COST SUMMARY (Horizontal)Contains primary key elements for the service cost summary (in horizontal format) and the following sub-classes:• Service Cost Sum Hz - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Service Cost Sum Hz - Additional Details (Descriptive) - partition year

and serial number



• Service Cost Sum Hz - Dates and Fiscal Periods - fiscal year and max fiscal period

• Service Cost Sum Hz - Monetary Currency - identifiers for controlling area currency, local (company code) currency and transaction currency.

• Service Cost Sum Hz - Values• Service Cost Sum Hz Amts - Transaction Currency - raw debit and

credit values (no aggregation) for:• Period balances (fiscal periods 1 - 16)• Quarterly balances (quarters 1 - 4)• YTD balance

Service Cost Summary Hz. Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designerService Cost Summary Hz. Star Schema



Service Cost Summary (Vertical)The Service Order cost Summary extracts information about the cost (planned, and actual) to complete Service Orders. Each maintenance Service Order can include actual cost and an estimate of the cost to complete the Service Order. SAP solutions calculate planned costs after the resources and capacities are planned for that Service Order. Actual costs are posted at confirmation time, and can be analyzed after work is completed. SAP solutions supports cost analysis of plant maintenance at two levels:• Cost element level, through the controlling (CO) module• Value category level, through the plant maintenance (PM) moduleThe vertical tables carries one row per fiscal period and fiscal year. Each row carries only the values for that fiscal year / period combination. The vertical table also computes rolling 16 period totals for plant maintenance costs.

Service Cost Summary Vr. MeasuresThe Service Cost vertical measures contain all additive and semi-additive measures for horizontal vertical costs. They appear as shown below in the universe:Service Cost Summary Vr. Measures

Service Cost Summary VR Measures Contains measures related to service cost summary vertical.• Service Cost Sum Vr - TRX Currency Measures

• Service Cost Sum Vr - Actual Measures TRX - Actual costsPeriod Beginning BalancePTD BalanceCredit / Debit amounts for PTD, YTD, and QTDRolling 16 period totals



• Service Cost Sum Vr - Budget Measures TRX - Budget costsPeriod Beginning BalancePTD BalanceCredit / Debit amounts for PTD, YTD, and QTDRolling 16 period totals

Service Cost Summary Vr. Subject Area ClassesThe Service Cost vertical subject area classes contain all remaining objects for Service Cost in vertical representation. They appear as shown below in the universeService Cost Summary Vr. Subject Area Classes

SERVICE COST SUMMARY (Vertical)Contains primary key elements for the service cost summary (in vertical format) and the following sub-classes:• Service Cost Sum Vr - Additional Details (Ids) - the foreign keys to the

various associated dimensions.• Service Cost Sum Vr - Additional Details (Descriptive) - partition year,

serial number, and summary key



• Service Cost Sum Vr - Dates and Fiscal Periods - Load date and Load Time. Fiscal Year and Fiscal Period are first two objects in the primary key. They are found in class SERVICE COST SUMMARY (Vertical).

• Service Cost Sum Vr - Monetary Currency - identifiers for controlling area currency, local (company code) currency, and transaction currency.

• Service Cost Sum Vr - Values• Service Cost Sum Vr Amts - Local Currency - raw debit and credit

values (no aggregation) for:• Period balances• QTD balances • YTD balance• Rolling 16 period totals

Service Cost Summary Vr. Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designerService Cost Summary Vr. Star Schema


MTBR and MTTR
The section calculates:• MTBR = Mean (or Average) Time Between Repairs (also called up time)• MTTR = Mean (or Average) Time To Repair (also called down time)MTBR and MTTR are derived from notifications. In the Rapid Mart the NOTIFICATION_FACT table is extracted and populated from SAP solutions first. Then, NOTIFICATION_FACT serves as the source for MTBR_MTTR_FACT.The SAP solutions Plant Maintenance Information System (PMIS) only calculates MTBR and MTTR on a monthly basis. However, you can use data from the universe to analyze MTBR and MTTR for any duration.

MTBR and MTTR MeasuresThe MTBR & MTTR measures contain all additive and semi-additive measures for MTBR & MTTR. They appear as shown below in the universe:MTBR & MTTR Measures

MTBR and MTTR MeasuresContains measures related to MTBR and MTTR.• MTBR MTTR - Time Measures - Downtime divided by uptime (downtime

as a percentage of uptime) in days, hours, minutes• MTBR MTTR - Downtime - Average, min, and max downtime in

days, hours, minutes.• MTBR MTTR - Uptime - Average, min, and max uptime in days,

hours, minutes.

MTBR and MTTR Subject Area ClassesThe MTBR & MTTR subject area classes contain all remaining objects for MTBR & MTTR. They appear as shown below in the universe



MTBR & MTTR Subject Area Classes

MTBR and MTTRContains primary key elements for MTBR & MTTR and the following sub-classes:• MTBR MTTR - Additional Details (Ids) - foreign keys to the various

associated dimensions.• MTBR MTTR - Additional Details (Descriptive) - Object Flag and

Notification description• MTBR MTTR - Dates and Fiscal Periods - various dates associated

with the MTBR MTTR record. Includes Malfunction start and end date, notification date, etc.

• MTBR MTTR - Values• MTBR MTTR - Time - raw values (no aggregation) for uptime and

downtime in days, hours, minutes.

MTBR and MTTR Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designer



MTBR & MTTR Star Schema

Filters & Techniques

FiltersThe universe contains filters that allow you to restrict the results of your reports. The filters appear after the Fact Table Classes in the universe



SAP Plant Maintenance Universe Filters:



Each of the classes below contain filters that allow you to limit the dimensional and hierarchy attributes selected to certain values. Using these prompts in Web Intelligence prompts users to enter values at report run time for: a single value, a range of values, or a list of multiple values.

Service Cost summary Fact HZ FiltersIncludes filters allowing selection of budget or actual values (Actual: Record Type = 04; Budget: Record Type= 01), single or multiple fiscal years, and fiscal year range.Service Cost summary Fact VR FiltersIncludes filters allowing selection of budget or actual values (Actual: Record Type = 04; Budget: Record Type= 01).

Company Code FiltersConditions to limit result set to either a single or multiple Company Codes.

Hierarchy FiltersAll hierarchy filters provide two groups of conditions “Limit to Single Parent” and “Limit to Multiple Parent” sub-classes. Each of the conditions provided here allows the user to choose the level of the parent node (0 - 4)in the hierarchy tree. This universe provides the following hierarchy filters:• Activity Hierarchy - Limit result set to a single or multiple Activity

parent node(s)• Cost Center Filters - Limit result set to a single or multiple Cost

Center parent node(s)• Cost Element Hierarchy - Limit result set to a single or multiple

Cost Element parent node(s)• Equipment Hierarchy - Limit result set to a single or multiple

Equipment parent node(s)• Equipment Classification Hierarchy - Limit result set to a single or

multiple Equipment parent node(s)• Functional Area Hierarchy - Limit result set to a single or multiple

Functional Area parent node(s)• Functional Location Hierarchy - Limit result set to a single or

multiple Functional Location parent node(s)• Functional Location Classification Hierarchy - Limit result set to a

single or multiple Functional Location Classification parent node(s)



• Internal Orders Hierarchy - Limit result set to a single or multiple Internal Order parent node(s)

• Profit Center Filters - Limit result set to a single or multiple Profit Center parent node(s)

• Project Element Filters - Limit result set to a single or multiple Project Element parent node(s)

• Work Center Filters - Limit result set to a single or multiple Work Center parent node(s)

TechniquesTechniques are advanced technique objects developed for the Web Intelligence reports. They are described in “Techniques” on page 17.

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.


Integrity Check Results.
Structure DivergencesSome tables 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. Also, validation tables (those ending in “_BAD”) are not joined to other tables.

Object Parsing ErrorsThese objects are in the Techniques section and are represented by valid SQL. These objects are included in the universe to accommodate advanced reporting techniques primarily in Web Intelligence and will work properly when used with other objects in a query.

Cardinality DivergencesThese are caused by the use of the “@prompt” function in the join. Since this function requires user intervention to complete the SQL join condition, the Universe Designer cannot check the cardinality vs. the database.The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.


UniverseSAP Service Master Universe 5

SAP Service Master UniverseThe SAP Service Master Universe gathers information from the SAP solutions Plant Maintenance module.Maintenance in SAP solutions is performed on the technical objects (functional locations and equipment) throughout your enterprise.This universe focuses on these technical objects organizing them as fact tables. This allows master data analyses including the Classification and Characteristics assigned to the equipment and functional locations. To support these processes SAP solutions uses Company Code, Vendors, Material, Cost Center, Functional Location, Equipment, other master data, and numerous reference data. In some cases these master data are organized into hierarchy (or tree) structures.The SAP Service Master universe is a reflection of this complexity. At this writing, it has:• 86 classes• 794 objects• 62 conditions• 29 tables• 6 alias• 47 joins• 2 contexts• 9 hierarchiesThe 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 areas. They are:• SAP Service Master Universe Objects & Classes• SAP Service Master Common Dimensions• Equipment Characteristics• Functional Location Characteristics• SAP Service Master Filters & Techniques• SAP Service Master Universe Validation


UniverseSAP Service Master Universe5
SAP Service Master Universe Objects & Classes
All 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 classes, sub-classes and all objects they contain are organized alphabetically for ease of navigation. The top level classes are shown belowService Master Top Level Classes:

Measures: The first Top Level class represents the Measures as described in “Universe Terminology” on page 167. Measures are grouped into sub-folders that represent the various monetary and quantity amounts of the fact tables in the star schemas. Each subject area is further divided into classes by types of measure specific to the subject area.



Common Dimensions: These top level classes appear after the Measures. These are the dimensions used in common by more than one subject area. These are sub-divided into classes for each specific dimension table. For example, the Organization Structure class has sub-classes for Company Code, and Controlling Area. Each of these represents a specific dimension table or alias of a dimension table. The Service Master Common Dimensions Matrix (presented later in this chapter) details which subject areas can be used with which common dimensions.Fact Tables: Following the Dimensions are group of Top Level classes, one for each subject area (also called fact table or star schema) in the universe.These subject area classes are further divided into classes that are logical groupings of fact table attributes. For example, the “Equipment Char - Dates and Fiscal Periods” class under “EQUIPMENT CHAR” contains the dates that are important for tracking equipment records.Filters & Techniques: Filters: This top level folder contains pre-defined conditions (organized by subject area) for use in any report. See details about specific “Hierarchy Filters” on page 22Techniques: These are advanced technique objects that have developed for the Web Intelligence reports. See “Techniques” on page 17 for details.

SAP Service Master Common DimensionsCommon Dimensions are those dimensions shared by more than one subject area (or fact table). They appear as shown below in the universe.



Service Master Common Dimension Classes:

CLASSIFICATIONSSystem that is used to describe objects on the basis of characteristics by grouping together into classes (i.e. classifying) objects according to freely definable criteria.Objects can be retrieved with the aid of classes and the characteristics defined in the classes, enabling objects that are identical or similar from a point of view of their characteristics to be retrieved as quickly as possible.In the Plant Maintenance Rapid Mart, the classes are restricted to Functional Location and Equipment. These are the two types of technical objects used in PM.



• Equipment Classification• Equipment Class Hier Hz• Equipment Class Hier Vr

• Functional Location Classification• Functional Location Class Hier Hz• Functional Location Class Hier Vr




EQUIPMENTUsed in Plant Maintenance and Service modules of SAP. Individual, physical object that is to be maintained as an autonomous unit. Equipment can be internal, such as machinery in your factory used to manufacture goods for sale. Equipment can also be external, such as the machine that is manufactured and sold to your customer.

FUNCTIONAL LOCATIONOrganizational unit within Logistics that structures the maintenance objects of a company according to functional, process-oriented or spatial criteria. A functional location represents the place at which a maintenance task is to be performed.

MATERIALThe Materials Master in SAP R/3 and ERP. Goods that are the subject of business activity. The material can be traded, used in manufacture, consumed, or produced. They can also be bought or sold.This class also contains the following subclasses:

Material by PlantMARA and MARC Tables - Plant Level Material attributes.



Material (Product) HierarchyMaterials can be grouped into hierarchies. Every material (product) can be assigned to one material product hierarchy level.




Controlling AreaAn organizational unit within a company, used to represent a closed system for cost accounting purposes. A controlling area may include single or multiple company codes that may use different currencies. These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area.





Plant LocationA place in a maintenance plant at which a technical object is physically located.


• Service Person - An employee who is actively involved in troubleshooting, maintenance, and repair activities.



• Valid From Date Time Dim


• Downtime Unit of Measure• Duration Unit of Measure• Work Unit of Measure




Service Master 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 table below is a cross-reference matrix of common dimensions and subject areas showing exactly which common dimensions to use with each subject area

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.

Dimension Table Equipment Characteristics

Functional Location Characteristics

Business Area X XClassification Hierarchy X XCompany Code X XControlling Area X XCost Center & Hierarchy X XEquipment & Hierarchy XFunctional Location & Hierarchy

X X

Material & Product Hierarchy XMaterial By Plant XPlanning Group XPlant X XPlant Location X XService Person X XTime Dim X XUnit Of Measure X XVendor XVendor By Company X



Equipment CharacteristicsThis section allows you to analyze the Equipment by the various characteristics assigned to them. It facilitates reporting across hierarchy and dimensional boundaries. You can use the information in this section to identify characteristic attributes that require special attention.Example: you can identify all equipment with a certain level of software revision (as captured by the characteristics) and plan for a mass upgrade of the software to a newer version.

Equipment Characteristics MeasuresEquipment Characteristics has two measures that allow you count equipment and material by characteristics. They appear as shown below in the universe:Equipment Characteristic Measures

Equipment Characteristics Subject Area ClassesThe Equipment Characteristics subject area classes contain all remaining objects for Equipment Characteristics. They appear as shown below in the universeEquipment Characteristics Subject Area Classes



EQUIPMENT CHARContains the primary key elements for Equipment Characteristics and the following sub-classes:• Equipment Char - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Equipment Char - Additional Details (Descriptive) - descriptive

attributes not associated with dimensions. These include characteristic descriptions, name, precision, scale, etc.

• Equipment Char - Dates and Fiscal Periods - valid-from date and valid-to dates for the characteristics

• Equipment Char - Values - Numeric values of the characteristics, including “from” and “to” values for characteristic ranges.

Equipment Characteristics Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designerEquipment Characteristics Star Schema



Functional Location CharacteristicsThis section allows you to analyze the Functional Locations by the various characteristics assigned to them. It facilitates reporting across hierarchy and dimensional boundaries. You can use the information in this section to identify characteristic attributes that require special attention.Example: you can identify all functional locations with a certain type of architecture (as captured by the characteristics) and plan for a seismic retro-fits of the buildings.

Functional Location Characteristics MeasuresFunctional Location Characteristics has two measures that allow you count Functional Locations and Plant Locations by characteristics. They appear as shown below in the universe:Functional Location Characteristic Measures

Functional Location Characteristics Subject Area ClassesThe Functional Location Characteristics subject area classes contain all remaining objects for Functional Location Characteristics. They appear as shown below in the universeFunctional Location Characteristics Subject Area Classes



FUNCTIONAL LOCATION CHARContains the primary key elements for Functional Location Characteristics and the following sub-classes:• Func Loc Char - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Func Loc Char - Additional Details (Descriptive) - descriptive

attributes not associated with dimensions. These include characteristic descriptions, name, precision, scale, etc.

• Func Loc Char - Dates and Fiscal Periods - valid-from date and valid-to dates for the characteristics

• Func Loc Char - Values - Numeric values of the characteristics, including “from” and “to” values for characteristic ranges.

Functional Location Characteristics Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the universe designerFunctional Location Characteristics Star Schema



SAP Service Master Filters & Techniques

FiltersThe universe contains filters that allow you to restrict the results of your reports. The filters appear after the Fact Table Classes in the universeSAP Service Master Universe Filters:

Each of the classes below contain filters that allow you to limit the dimensional and hierarchy attributes selected to certain values. Using these prompts in Web Intelligence prompts users to enter values at report run time for: a single value, a range of values, or a list of multiple values.

Company Code FiltersConditions to limit result set to either a single or multiple Company Codes.

Hierarchy FiltersAll hierarchy filters provide two groups of conditions “Limit to Single Parent” and “Limit to Multiple Parent” sub-classes. Each of the conditions provided here allows the user to choose the level of the parent node (0 - 4)in the hierarchy tree. This universe provides the following hierarchy filters:• Cost Center Filters - Limit result set to a single or multiple Cost

Center parent node(s)• Equipment Hierarchy - Limit result set to a single or multiple

Equipment parent node(s)• Equipment Classification Hierarchy - Limit result set to a single or

multiple Equipment parent node(s)



• Functional Location Hierarchy - Limit result set to a single or multiple Functional Location parent node(s)

• Functional Location Classification Hierarchy - Limit result set to a single or multiple Functional Location Classification parent node(s)

TechniquesTechniques are advanced technique objects developed for the Web Intelligence reports. They are described in “Techniques” on page 17.

SAP Service Master 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.

Integrity Check Results.





Cardinality DivergencesThese are caused by the use of the “@prompt” function in the join. Since this function requires user intervention to complete the SQL join condition, the Universe Designer cannot check the cardinality vs. the database.The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.


UniverseSAP Master Data Universe5
SAP Master Data Universe
The SAP Master Data universe defines a common class structure and contains common master data dimension objects, techniques, and conditions used by all Rapid Mart universes in the SAP BusinessObjects Rapid Mart Suite for SAP.This universe is designed to facilitate Rapid mart universe integration and customization, master data discovery, and auditing hierarchy structures in SAP solutions.In the business content universes these hierarchies and master data are dimension tables joined to one or more fact tables. The SAP Master Data universe contains no fact tables. Therefore, it is not organized as a star schema.All hierarchies, except Material (Product) Hierarchy, are organized both horizontally and vertically. The SAP Master Data universe also provides reports to identify Invalid Hierarchies. These are hierarchy records that have failed validation in Data Services.The SAP Master Data universe, at this writing, has:• 394 classes• 4100 objects• 199 conditions• 261 tables• 44 alias• 36 joins• 0 contexts• 26 hierarchiesThe universe is well documented and logically organized to help universe users easily navigate to a specific object.

Universe Objects & Classes - Master DataAll Rapid Mart dimension columns are exposed as objects. Universe Objects are grouped in folders and sub-folders. These folders and sub-folders are also called classes. The classes, sub-classes and all objects they contain are organized alphabetically for ease of navigation. The top level classes are shown below


UniverseSAP Master Data Universe 5

Top Level Classes



ACTIVITYPhysical measure of the activity output/production in a cost center. Examples of Controlling activities include:

• number of units produced • hours • machine times • production times

Activities in Controlling can be internal or external. Activity Hierarchies are presented stacked vertically and flattened horizontally.

BENEFITSIn HR, these are the various employee benefits including health insurance and savings plans as well as the rules associated with the plans. The class carries the following sub-classes:

Benefit AreaThe highest-level subdivision of benefits data.Benefit areas enable different pools of benefit plans to be administered separately, for example, to reflect geographical location, departments, or production areas.Employees are sorted into benefit areas during processing, according to the corresponding feature.Example: The medical benefits offered by a company in the chemical industry are organized according to production areas. Employees in plastics production have different plans to employees in fertilizer production. Each production areas is represented by a benefit area.

Benefit PlanThe central element of the Benefit Administration component, representing a single benefit offered by the employer. A plan belongs to a plan category, and is defined by the following:• General plan data (for example, provider)• Any relevant plan options (for example, health plan coverage,

investments)• Rules determining the calculation of monetary amounts relating to

plans (for example, costs, contributions, coverage, credit)• Plan-specific checks (for example, evidence of insurability)



Benefit Program GroupA set of benefit plans offered to a specific group of employees.Benefit programs are defined for one, or a combination of two program groupings, and therefore control high-level eligibility. Low-level eligibility in controlled by the eligibility rules assigned to the individual plans within a program.

Benefit Spending AccountA benefit plan that allows employees to set aside tax-free dollars for anticipated medical care and dependent care expenses. Flexible spending accounts are available in North America only.

Dependent CoverageAn option for a health plan, chararacterized by the number of dependents that can be covered.

Enrollment TypeBenefit program enrollment type descriptive attributes from DD07T, BEN_ENRTYP domain. A -Automatic, D - Default, M - Manual.

Health PlanHealth Plan descriptive attributes from T5UCE

Insurance Coverage GroupBenefit insurance coverage rules and formulas from T74FB, T74FC, PA0168 (date-effective)

Insurance OptionThis is the insurance plan option, within the insurance plan.

Example: The Standard Life plan has 2 options, which the employee selects the desired coverage from: HIGH - $120,000 option; LOW - $80,000 option

Investment GroupA customer-defined group of investments that can be assigned to plans in the categories 'Savings' and 'Miscellaneous'.

Investment PlanA customer-defined option for plans in the categories Savings and Miscellaneous that lets employees choose how their contributions are invested.



BENEFIT RULESIdentifying rules for benefits participation and contribution. Sub-classes include: Benefit Termination Rule, Contribution Rule, Eligibility Rule, and Vesting Rule.

BILL OF MATERIALS (BOM)A formally structured list of the components that make up a product or assembly. The list contains the object number of each component, together with the quantity and unit of measure.BOMs are used in their different forms in various situations where a finished product is assembled from several component parts or materials. Depending on the industry sector, they can also be called recipes or lists of ingredients and so on.They contain important basic data for numerous areas of a company, for example:

• MRP• Material provisions for production• Product costing• Plant maintenance

Bill of Materials Item CategoryPart of a bill of material containing information about the quantity and unit of measure of a component. According to the object referred to (for example, material or document) and other criteria (such as inventory management criteria), BOM items are defined in different item categories that determine which item data is managed.

Bill of Materials StatusA tool used to control processing of a BOM in different application areas.

Bill of Materials UsageA tool that allows you to enter BOMs, for example, for material LAMP, for specific sections of your company. You can enter a separate BOM for each section in your company, for example, production, so that each section only processes the items relevant to that section. The usage is an important selection criterion in the BOM application, which controls the automatic explosion of BOMs.

CAPACITYThe ability of a work center to perform a task. Capacities are differentiated according to capacity category. They are arranged in a hierarchy under a work center.



Capacity by Work CenterStandard work center capacity information from CRCA/CRHD/KAKO.

Capacity CategoryA description that classifies a capacity at a work center. A capacity category can exist only once at each work center. However, capacities at different work centers can have the same capacity category. Capacity category descriptions from TC26T.

Capacity Object TypeCapacity Object Type (like Order, Task List) - from DD07T TYPKZ domain.

Capacity Planning GroupCapacity planner group descriptive attributes (from TC27T).

CENTRAL ADDRESSThis is the Central Address repository (table ADRC) in SAP. Currently, it is used to store Customer Ship-To addresses for sales orders and billings (Sales Rapid Mart). But, can be easily expanded to show addresses associated with purchase orders, vendors, etc.

CLASSIFICATIONSSystem that is used to describe objects on the basis of characteristics by grouping together into classes (i.e. classifying) objects according to freely definable criteria.Objects can be retrieved with the aid of classes and the characteristics defined in the classes, enabling objects that are identical or similar from a point of view of their characteristics to be retrieved as quickly as possible.We carry two sets of Classification data for:

• Equipment Classification• Functional Location Classification






COST ELEMENTA cost element classifies the organization's valuated consumption of production factors within a controlling area. SAP solutions maintains both primary and secondary cost elements.

CUSTOMERCustomers are the companies and individuals to whom your company sells goods and services.

Customer by CompanyIntersection of Company and Customer records. Used by both Customer Items and Customer Totals

DOCUMENT ATTRIBUTESMaster data associated with the various “documents” found in SAP solutions. These include Document Categories, Document Types, and separate class groupings for Accounting Documents, Sales Documents and Purchasing Documents. Document Attributes subclasses include:

Document CategoryDocument Category combines all document categories in one table, including: Financial, Internal Order, Notification, Purchasing, and Sales. The following document category aliases are also included as classes under DOCUMENT ATTRIBUTES:

• Accounting Document Category - Domain DOCCT in SAP solutions.

• Internal Order Document Category - A technical classification criterion for orders. The order category determines the SAP application to which an order belongs, and controls the functions by which an order can be processed.

• Notification Document Category - A key that identifies notification types in an application component. Notification categories include:- Quality notification in the Quality Management (QM) application component - Maintenance notification in the Plant Maintenance (PM) application component - Service notification in the Customer Service (CS) application component



• Purchase Document Category - Broadly categorizes purchase documents as “requisitions”, “purchase orders”, “contracts” etc.

• Sales Document Category - One of a set of classes used to control how the system processes a sales document in the sales and distribution component module. Sales document categories include:- Inquiries and quotations - Sales orders - Outline agreements

Document TypeDocument Type combines all document categories in one table, including: Internal Order, Sales, Purchasing, Billing, Delivery, Financial, Special Ledger, and Notification document types. The following document type aliases are also included in the SAP Master Data universe:

• Billing Document Type - indicates type of billing document• Delivery Document Type - indicates type of delivery document• Financial Document Type - Records what the posting was for.

Examples: Goods Issue, Goods Receipt, Asset posting, Vendor Payment, Customer Payment

• Internal Order Document Type - A tool that categorizes orders according to purpose. The order type contains information which is necessary for managing orders. Order types are client-specific. The same order type can be used in all controlling areas in one client. Examples: production orders, maintenance orders (Plant Maintenance Service Orders), capital investment orders, and marketing orders.

• Notification Document Type - A key that determines the origin, content, and other features of service, maintenance, and quality notifications. The following notification types exist in the standard SAP Applications system:- Maintenance notifications, including malfunction and activity reports and maintenance requests - Service notifications, including problem notifications, service requests, and activity reports - Quality notifications, including complaints against the vendor, customer complaints, and internal problems

• Purchase Document Type - A further subdivision of Purchase Document Categories.



• Sales Document Type - A categorization of a Sales Document as an invoice, credit memo, debit memo, pro forma invoice, or cancellation document.

• Special Ledger Document Type - Document Type (tables T889 and T889TE)

Reference Date KeyKey determining the reference date for various entities - Milestone, PRT - Domain MLST_SDDAT; TCA55

Special Stock IndicatorStock of materials that must be managed separately for reasons of ownership or location. An example is consignment stock from vendors.

Standard Text KeyStandard text Key descriptions for activities from T435T.

Standard Value KeyCapacity Standard Value Key descriptive attributes from TC21T.

Valuation TypeThe basic criterion for calculating the asset value. In a depreciation area, in addition to the acquisition and production costs and ordinary depreciation, the following special valuation types can be calculated: Revaluation, Investment support measures, Special depreciation, Unplanned depreciation, Transfer of reserves, and Interest.

ACCOUNTING DOCUMENT ATTRIBUTES• Bank Account Information - Bank account details defined by

account.• Controlling (Business) Transaction Type - Cost Accounting

(or business) transaction types. Examples: cost planning, invoice posting, or overhead calculation.

• Debit Credit Indicator - From Domain SHKZG. Values: H = Credit, S = Debit

• Financial Document Status - Status (from Domain BSTAT), indicates if a financial document is a normal, clearing or parked document.

• Financial Management Area - FM01T - Funds Management Area Texts.

• Financial Record Category - Categorization for a financial document.



• Financial Record Type - Special Ledger Record Types (Domain RRCTY) from table DD07T and Cost/Plant Maintenance value types from CO_WRTTP domain of DD07T table

• Financial Version - Special Ledger Version (T894T table in SAP solutions)

• Ledger Group - A combination of ledgers for the purpose of applying the functions and processes of general ledger accounting to the group as a whole.

• Payment Block - An indicator that allows you (by entering a payment block) to block an account or individual items for payment. The payment blocking indicator is placed in the customer or vendor's master record, or in the line item. from table T008T - indicates any Holds preventing payment to a vendor.

• Payment Reason - From table T053S - Classification of Payment Differences (Texts)

• Payment Term - Relevant only for Financial Documents, describes when payments to a vendor or from a customer are due. Also describes any discounts associated with early payment.

• Posting Key Type -The posting key defines if it is a debit or credit posting, and which account type (customer or vendor) is posted. The posting keys for special G/L transactions must be indicated as such.

• Reference Procedure - Object Type Names for Accounting (TTYPT).

• Segment - A division of a company that can create its own financial statements for external reporting. A segment can be entered in the master record of a profit center. The segment is then derived from the assigned profit center during posting. This is the business segment. It is available in New GL only (release ECC 5.0 or higher).

• Special GL Indicators - Special G/L transactions are special transactions in accounts receivable and accounts payable that are displayed separately in the general ledger and the subledger. This is achieved by posting to alternative reconciliation accounts, instead of posting to the reconciliation accounts for receivables and payables.

• Special Ledger Master - Identifies the Standard or Special Ledger used.



• Transaction Type - Transaction type of the Financial Document from table T856T.

PURCHASING DOCUMENT ATTRIBUTES• Account Assignment Category - A key indicating whether an

item is to be assigned to an auxiliary account (such as a cost center). The account assignment category determines which account assignment details are required for the item (for example, cost center or account number).

• Condition Type - Identification that defines characteristics, attributes, and business meaning of a condition. The system can, for example, contain different condition types for free-goods, sales-based rebate, or gross price discount. Every condition type has its own access sequences, condition tables, and condition records.

• Purchase Document Price History - A series of prices charged or quoted by a vendor for a material or service over a certain period up to the present.

• Purchase Document Source - Describes where the purchase document originated (BAPI, RFQ conversion, Third Party, Kanban, etc.)

• Purchase Item Category - An identifier indicating the characteristics of an item. The item category determines whether the following are mandatory or admissible for an item:- Material number - Additional account assignment - Inventory management in the SAP solutions system - Goods receipt - Invoice receipt

SALES DOCUMENT ATTRIBUTES• Billing Block - A block that prevents the release of billing

documents to financial accounting. • Delivery Block - A block that prevents the release of products

for documents to financial accounting.• Delivery Route - Delivery route details.• Sales Order Status - Status descriptions for sales orders



EMPLOYEEIn HR, the employee class tracks information about employees such as name,address, birth date, Gender, Marital status, number of dependents, etc.

EMPLOYEE ATTRIBUTESAdditional information about the employee such as Personnel Actions, Education, Job Qualifications, Work Permit status, etc. This area contains the following sub-classes:

• Certificate Type• Education Type• Ethnic Origin• Gender• Identification Type• Language• Marital Status• Military Status• Nationality• Personnel Action Reason• Personnel Action Status• Personnel Action Type• Personnel Date Type• Personnel Task Status• Personnel Task Type• Proficiency• Qualification• Religion• Residence Status• School Type• Study Branch• Time Management Status• Work Permit Type



EQUIPMENTUsed in Plant Maintenance and Service modules of SAP. Individual, physical object that is to be maintained as an autonomous unit. Equipment can be internal, such as machinery in your factory used to manufacture goods for sale. Equipment can also be external, such as the machine that is manufactured and sold to your customer.

FUNCTIONAL LOCATIONOrganizational unit within Logistics that structures the maintenance objects of a company according to functional, process-oriented or spatial criteria. A functional location represents the place at which a maintenance task is to be performed.

GL ACCOUNTS and HIERARCHIES General Ledger accounts are a structure that records value movements in a company code and represents the G/L account items in a chart of accounts. The Debit / Credit Flag indicates a debit or credit posting.The accounts can be organized into various hierarchies, such as those need to produce Profit & Loss or other Financial Statements. Use the Hierarchy Data Discovery Class to explore these hierarchies. Additionally these dimensions include sub-classes that facility data discovery of the GL Account Hierarchies and Financial Statement (FS) Hierarchies, without linking to any fact table.

• GL Account• Hierarchy Data Discovery

• GL Account Discovery Hz• GL Account Discovery Vr• FS Hierarchy Discovery Hz• FS Hierarchy Discovery Vr

INTERCOMPANY TERM01Describes when in the delivery process the receiver of goods takes physical ownerships of the those goods.

INTERNAL ORDERSProduction Orders, Service Orders, and associated hierarchies. Object used to monitor costs and, in some instances, revenues for an organization. Internal orders can be used to:

1. Monitor the costs of short-term measures 2. Monitor the costs and revenues related to a specific service



3. Monitor ongoing costs Internal orders are divided into the following categories:

1. Overhead orders2. Capital investment orders 3. Accrual orders4. Orders with revenues.

Internal Order StatusInternal Order status name and description from TKO04.

JOB An organizational object that serves as a template for creating positions when you create an organizational plan.Unlike Positions that can be occupied by holders, for example, secretary in the marketing department. Jobs are a classification of functions in an enterprise, for example, secretary, defined by the tasks and characteristics assigned to them. Job descriptions apply to different positions with similar tasks and characteristics. This includes Exempt/Non-Exempt Status, Payscale, etc.

LEAVE Information about the types of leave (vacation, sick leave, maternity leave, etc.) an employee may have.

Leave TypeJob leave type descriptive attributes from T533T

MATERIALThe Materials Master in SAP R/3 and ERP. Goods that are the subject of business activity. The material can be traded, used in manufacture, consumed, or produced. They can also be bought or sold.This class also contains the following subclasses:

Material BatchBatch material management - Material Master from MCHA

Material by PlantMARA and MARC Tables - Plant Level Material attributes.

Material GroupA grouping of materials and services according to their characteristics.



Material (Product) HierarchyMaterials can be grouped into hierarchies. Every material (product) can be assigned to one material product hierarchy level.

Material ProductionDefines production version information (from MKAL).

Material TypeA grouping together of materials with the same basic attributes such as raw materials, semi-finished products, or finished products.All materials must be assigned to a material type which determines:• Whether the material is intended for a specific purpose such as a

configurable material or process material • Whether the material number can be assigned internally or externally • The number range from which the material number is drawn • Which screens appear and in what sequence • Which user department data you may enter • What procurement type the material has; that is, whether it is

manufactured in-house or procured externally, or both

MONETARY DIMENSIONS A medium of exchange in current use within a particular country to valuate goods and services. For example the US Dollar, the Euro, the Japanese Yen, etc. Contains the following sub-classes related to the valuation of various monetary currencies:

Currency SourcesCurrency Sources for 2nd and 3rd Local Currencies. The Currency source indicates which currency was used as a source for the 2nd or 3rd Local currency. The exchange rate is determined from this source currency to the 2nd or 3rd local currency. Standard Values:

• 1 = Translation taking first local currency as basis, i.e., the main Local Currency or Company Code Currency was used as the currency source.

• 2 = Translation taking transaction (or document) currency as basis.

Currency TypesCurrency Types for 2nd and 3rd Local Currencies. Key identifying the role of a currency in the R/3 System. In addition to the local currency as house currency, you can manage parallel currencies with the following currency types:



• Group currency • Hard currency • Index currency • Global company currency

Monetary CurrenciesThe Rapid Marts maintain various currencies, including:

• Benefit Currency - The monetary currency associated with personnel administration.

• Controlling Area Currency - The monetary currency assigned to the controlling area

• Group Currency - Group currency is used in the consolidated financial statements. Before the consolidation process can be completed all values in the individual financial statements must be translated from the local or transaction currency into group currency.

• Local (Company Code) Currency - The monetary currency assigned to the company code

• Transaction (Document) Currency - The monetary currency of each individual transaction document.

• Update Currency - Used for Euro conversion in European Union: The update currency is the currency, in addition to the local (company) currency, in which the transaction figures are updated in the general ledger. You specify whether the document or account currencies should also be the update currency in the G/L account master record.

Monetary Exchange RatesThese are the conversion rates used to convert one currency to another. They are used to compute global currency amounts in the universe.

MRPMaterial Resource Planning - A term for procedures in requirements planning that take into account and plan every future requirement during the creation of order proposals such as independent requirements, and dependent requirements. Contains the following sub-classes:

Mrp ControllerThe person responsible for a group of materials in MRP in a plant or company. Material that takes part in material requirements planning must be assigned to an MRP controller.



Mrp Element TypeA term for all objects displayed as items in the MRP list or in the stock and requirements list. Such objects include planned orders, purchase orders, reservations, and sales orders.

Mrp GroupThe MRP group, groups material from the material requirements planning point of view to allocate them control parameters for planning.The control parameters include the strategy group, the planning horizon and the creation indicator for the planning run.

Mrp Lot SizeA key that defines which lot-sizing procedure the system uses for calculating the quantity to procure in the MRP run.

Mrp ProfileA collection of data required for updating the material master record for planning. The MRP profile contains the necessary MRP data for the material master.This simplifies updating the material master record. When creating or changing a material master, the data in the MRP profile is copied automatically to the material master. The MRP profile defines:• Which fields are mandatory when entering MRP data • Values of these fields • Which values can be overwritten (default values) or not (fixed values)

Mrp TypeA key that controls the MRP procedure (MRP or reorder point) used for planning a material. It contains additional control parameters, for example, for using the forecast for the materials planning, or for firming procurement proposals.

OBJECTObject is a very generic term in SAP solutions. It can mean anything from an internal identifier for equipment in Plant Maintenance, to a way of categorizing cost in Controlling. The object class groups these various kinds of objects together for easy reference with these sub-classes:

Object ClassThe object class categorizes Controlling objects according to their business function and enables you to analyze cost flows within Controlling from different business perspectives. The following object classes are available: overhead, production, investment, profitability analysis and sales



While certain object types automatically belong to a particular class (for example, cost centers belong to the "Overhead" class), others need to be explicitly assigned to an object class in their master record (this is the case with internal orders and work breakdown structure elements, for example).In addition to the functional area, the object class is required to determine or explain certain values in the external accounting components. Object Class (from Domain SCOPE_CV).

Object Number TypeThe object type is the first two characters of the object number (from TBO01), which is a unique object key per client (order, cost center, project, etc.).

Object StatusObject statuses from JEST.

Object Status HzDimensional component loading horizontally represented selected ERP Object status information from JEST for selected Statuses from OBJECT_STATUS.

Object TypeA type of object that you process in the Engineering Workbench. An object can, for example, be a type of "task list type," "item," or "component assignment." Object Type (from Domain OBART).


Account TypeA key that specifies the accounting area to which an account belongs. Examples of account types are:• Asset accounts • Customer accounts • Vendor accounts • G/L accounts The account type is required in addition to the account number to identify an account, because the same account number can be used for each account type.



Business ActivityBusiness activity attributes from T022/T022T.


Chart Of AccountsA classification scheme consisting of a group of general ledger (G/L) accounts.A chart of accounts provides a framework for the recording of values to ensure an orderly rendering of accounting data. The G/L accounts it contains are used by one or more company codes.For each G/L account, the chart of accounts contains the account number, the account name, and technical information.A chart of accounts must be assigned to each company code. This chart of accounts is the operative chart of accounts and is used in both financial accounting and cost accounting.


Controlling AreaAn organizational unit within a company, used to represent a closed system for cost accounting purposes. A controlling area may include single or multiple company codes that may use different currencies. These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area.

Country GroupA grouping of countries for which the political restrictions or AFS quota are equally valid (e.g. EU). The grouping of countries facilitates the entry and processing of country-specific restrictions and AFS quota.



Credit Control AreaAn organizational unit that represents an area responsible for granting and monitoring credit. This organizational unit is either a single company code or, if credit control is performed across several company codes, multiple company codes. Credit information can be made available per customer within a credit control area.

Distribution ChannelCA channel through which saleable materials or services reach customers.Distribution channels include wholesale, retail, and direct sales. You can assign a distribution channel to one or more sales organizations.

DivisionAn organizational unit based on responsibility for sales or profits from saleable materials or services.

Employee GroupThe employee group is an organizational entity which is governed by specific personnel regulations. An employee group is divided into several employee subgroups.

Employee SubgroupAn employee subgroup is an organizational entity within an employee group which is governed by specific personnel regulations.

Functional AreaAn organizational unit in Accounting that classifies the expenses of an organization by functions such as:• Administration • Sales and distribution • Marketing • Production • Research and development Classification takes place to meet the needs of cost-of-sales accounting.

Line Manager HierarchyA person who holds a managerial position in a company or department and who makes decisions in an area of responsibility. Line managers can act as the first person responsible for applicant correspondence.



Organization (Structure) KeyA hierarchy in which the organizational units in an enterprise are arranged according to tasks and functions.The organizational structure differs from the administrative enterprise or personnel structure, whose structural elements are relevant to payroll accounting and accounting.

Organization UnitAn object used to depict the basic structure of an organization.Organizational units are functional units of a company. Depending on how tasks are distributed at a company, organizational units can be departments, groups or project teams.Organizational units are different from other entities at a company such as personnel areas, company codes, and business areas. These are used to depict administrative or accounting structures in the corresponding components.

Payroll AreaA group of employees included in the same payroll run.A payroll area is used to group employees together who have the same payroll periodicity, for whom the payroll runs at the same time, who have the same payment date, and to whom the same earliest possible retroactive accounting period applies. Examples:

• Payroll area Salaried Employees (monthly payroll run on 25th of each month)

• Payroll area Retired Employee (monthly payroll run on 20th of each month)

• Payroll area Weekly Wage Earners (weekly payroll run on each Friday)

Personnel AdministratorPortal role that performs all tasks related to managing employees. He or she primarily performs personnel services, management and advising tasks for the specialist fields. Typical tasks in this area are:• Administrating/changing HR master data, (such as new hires, salary

changes, transfers, employess on leave, and so on) • Administrating personnel appraisals • Processing organizational data • Year-end closing work • Statements and providing information



• Creating diverse, sporadic required evaluations • Advising all employees, retired employees, and managers Other personnel management tasks such as anniversaries/birthdays, cooperating with the organization, or performing work's council and spokespersons' committee elections, cooperating with the mass creation of messages, and so on.

Personnel AreaA personnel area is an organizational entity representing an area within an enterprise defined by specific aspects of personnel administration, time management and payroll.Personnel areas are subdivided into personnel subareas.

Personnel SubareaAn organizational entity that represents part of a personnel area.It is delimited according to personnel administration, time management, and payroll accounting criteria.



Plant LocationPlant location attributes.

Purchase GroupA key for a buyer or group of buyers responsible for certain purchasing activities. The purchasing group is internally responsible for the procurement of a material or a class of materials The principal channel for a company's dealings with its vendors.



Purchase OrganizationAn organizational unit responsible for procuring materials or services for one or more plants and for negotiating general conditions of purchase with vendors. The purchasing organization assumes legal responsibility for all external purchase transactions.

Sales DistrictA geographical sales district or sales region. You can assign customers to a sales district and use the sales district to generate sales statistics.

Sales GroupOrganizational unit that performs and is responsible for sales transactions. Constituent component in a distribution chain (with a sales manager per sales group, for example). Sales groups can be used for reporting purposes. In its capacity as a customer, a store can have a sales group assigned to it; this sales group is then responsible for sales to this store.

Sales OfficeA organizational unit in a geographical area of a sales organization. A sales office establishes contact between the firm and the regional market.Constituent component in a distribution chain (with a sales manager per sales group, for example). Sales groups can be used for reporting purposes. In its capacity as a customer, a store can have a sales group assigned to it; this sales group is then responsible for sales to this store.

Sales Org HierarchyHierarchy associated with Sales Organizations

Sales OrganizationA organizational unit in Logistics that structures the company according to its sales requirements. A sales organization is responsible for selling materials and services.

Storage LocationAn organizational unit that allows the differentiation of material stocks within a plant. The storage location is hierarchically situated between the plant and the warehouse number.

Supply AreaThe production supply area exists directly in the production area. You stage the material in the production supply area in productions storage bins, so that it can be removed directly for production.



The production supply area groups together work centers near to production storage bins, taking the material staging type into consideration.

Valuation AreaAn organizational unit in Logistics subdividing an enterprise for the purpose of uniform and complete valuation of material stocks.

WarehouseAn organizational division of a plant for managing materials stored in different places.

Work ContractA contract under private law in which the employee undertakes to work directly for the employer, and the employer undertakes to remunerate the employee.

PAYROLL and WAGES Information about the compensation and other payments an employee receives. Includes the following sub-classes:

Pay Scale AreaThe physical area of validity of a collective agreement.

Pay Scale TypeThe economic area to which a collective agreement applies, for example metal industry or the chemical industry.

Payroll Cumulation TypeDescriptive attributes for calendar-associated cumulation types.

Payroll PeriodPeriod for which regular payroll is run. A payroll period is identified by a period number and payroll year.

Payroll Period ParameterPayroll Period Parameter descriptive attributes, defines periodicity of the payroll run.

Payroll StatusDescriptive attributes for Payroll Indicator for most recent update of results record.

Payroll TypeCharacteristic used by the system to recognize which type of payroll run is to be carried out.



Salary RangeDefines the minimum, midpoint and maximum reported for the job by organizations with a formal salary structure. The salary range reflects the market value of a job.

Wage TypeObject in Payroll and Personnel Administration in which the user or the system stores amounts and time units that are used, for example, for calculating pay or for determining statistics. Wage types separate amounts and time units for various business purposes. This also enables the system to process amounts and time units in different ways during the payroll run.


• Accounting Clerk - Person responsible for collections or payments.• Sales Person - Person responsible for selling goods to the customer.• Service Person - An employee who is actively involved in

troubleshooting, maintenance, and repair activities.

POSITIONAn organizational object used to distribute tasks to posts in an organizational plan and to model the reporting structure between posts. Positions are concrete posts in an enterprise, which can be occupied by holders (employees or contractors), for example purchasing administrator, European sales manager, or secretary in the marketing department. Positions are not the same as jobs. A job is not a concrete position in an enterprise. It is a construct that enables you to create a number of positions with similar tasks and features.

PRICING PROCEDURERule type for pricing. Defines the conditions which are permitted for a particular document and the sequence in which the system takes these conditions into account during pricing. The Standard Pricing Procedure contains the conditions most commonly used. These include material prices as well as various discounts and surcharges (freight, tax).

PRODUCTION & PLANT MAINTENANCEAttributes associated Production Planning and Plant Maintenance functions. The sub-classes include:



ComponentAn object used as part of a bill of material by entering the object number. Example: A material is entered as a component of a bill of material by entering the material number. A document is entered as a component of a bill of material by entering the document number, document type, document part, and document version.

Control KeyA key that specifies how an operation or a sub-operation is processed in functions such as orders, costing or capacity planning.The following are examples of processing types managed by a control key for operations and sub-operations:

• External processing • Completion confirmation • Printing • Scheduling • Costing

Exception TextText that describes an exception and is specified in an exception class. An exception text can be parameterized using the attributes of the exception class.

Maintenance Activity TypeA key for the type of maintenance activity provided. Activities are divided into repairs, shutdowns, regular activities, inspections and so on.In cost evaluations, for example, total costs or number of orders for each technical object, you can classify data according to maintenance activity type.

Maintenance PriorityThe relationship between the order priority from a maintenance order and the requirement urgency.

Malfunction CauseOne of 3 pre-defined notification catalog objects - Malfunction Cause. Describes the incident or circumstances responsible for a malfunction

Malfunction DamageOne of 3 pre-defined notification catalog objects - Malfunction Damage. Describes the breakage sustained by a technical object



Malfunction EffectDescribes the consequences of the malfunction in the technical object’s performance. Description of malfunction effects from T357A_T

Malfunction Object PartOne of 3 pre-defined notification catalog objects - Malfunctioning Object Part. Describes the physical location of the malfunction.

NotificationA data record with which a user informs the Plant Maintenance, Quality Management, or Customer Service department about an occurrence.The following notification categories are available:

• Maintenance notifications • Service notifications • Quality notifications

Operation SuitabilityKey suitability required for carrying out the operation (for example, welding certificate or NC programming course) - from T423T

Procurement TypeA classification indicating whether a material is produced internally, procured externally, or both.

Production SchedulerProduction scheduler descriptive attributes from T024F

Scheduling ErrorPlanned order scheduling error texts from DD07T, domain TRMER.

Spare Part IndicatorA material used to replace a defective part. This material may or may not be kept in stock. This table stores descriptions of these spare parts as defined in T413T.

Special Procurement TypeAn indicator in the material master record that defines external procurement or in-house production of the material precisely. Example:

• Consignment • Stock transfer • Production in another plant



System ConditionSystem Condition descriptive attributes from T253M_T.

Variance CategoryA classification of variances based on their cause.You can calculate the following variance categories on the input side:

• Scrap variances (only in Product Cost Controlling) • Input price variances • Resource usage variances • Input quantity variances • Remaining input variances

You can calculate the following variance categories on the output side:• Fixed cost variance (only in Overhead Cost Controlling) • Mixed price variance (only in Product Cost Controlling) • Output price variance • Output quantity variance (only in Overhead Cost Controlling) • Lot size variance (only in Product Cost Controlling) • Remaining variances

PROFIT CENTEROrganizational unit in Accounting that reflects a management-oriented structure of the organization for the purpose of internal control.Operating results for profit centers can be analyzed using either the cost-of-sales approach or the period accounting approach.By analyzing the fixed capital as well, you can expand your profit centers for use as investment centers.

PROJECTA complex structure of tasks within a controlling area. It is used to control and monitor the schedule, resources, capacities, cost, revenues, and funds availability.

PROJECT ELEMENT (WBS)Also called WBS (Work Breakdown Structure). Hierarchical outline of an undertaking described in the project definition. The work breakdown structure (WBS) forms the basis for the organization and coordination of a project. A WBS consists of various WBS elements. The WBS elements describe specific tasks or actions in the project to be carried out within a defined time period.



PRT(Production Resource Tool) A moveable operating resource used in production or plant maintenance. PRT includes the following sub-classes:

PRT CategoryDescriptive attributes from TCF03 of Production Resource/Tools categories

PRT Grouping KeyProduction Resource/Tools grouping key descriptive attributes from TCF1

PRT StatusDescriptive attributes for PRT status from TCF05

ROUTINGA description of the production process used to manufacture materials or provide services in the manufacturing industry. Routing includes the following sub-classes:

Order Operation Order Operation including Sequences from AFVC

Routing OperationRouting master data from PLPO.

Routing SequenceRouting (Task List) sequence definition from PLFL

Task List TypeA tool that classifies task lists according to function. In PP, the following task list types are used:

• Routing • Reference operation set • Rate routing • Standard rate routing

Task List UsageTask List Usage descriptive attributes from TC23T.





• Document Date Time Dim• Early Start Time Dim• Hire Date Time Dim• Notification Time Dim• Participation Time Dim• Payroll Run Date Time Dim• Planned Open Date Time Dim• Weekly Time Dim

FISCAL PERIOD DIMENSIONSFiscal periods within a fiscal year for which transaction figures are updated. Every transaction that is posted is assigned to a particular posting period. The transaction figures are then updated for this period. Fiscal years are divided into halves, quarters, periods, and months for reporting purposes. Fiscal years and fiscal calendars are defined by the fiscal year variant.There can be 12 regular fiscal periods, and 4 special processing periods. Fiscal periods are numbered 1 - 12 for regular periods, 13 -16 for special periods.SAP Master Data universe provides these aliases for Fiscal Period analysis:

• Company Code Fiscal Period• Controlling Area Fiscal Period

Calendar DimensionsCertain Rapid Marts carry calendars subject areas specific calendars. Included here are:

• Factory Calendar• Factory Calendar Period• Work Calendar




• Base Unit of Measure• Downtime Unit of Measure• Duration Unit of Measure• Offset Unit of Measure• Standard Unit of Measure• Time Interval Unit of Measure• Work Unit of Measure

UNIT OF TIME (UOT) Human Resources related unit of time descriptive attributes.



WORK CENTER An organizational unit that defines where and when an operation should be carried out. The work center has a particular available capacity. The activities performed at or by the work center are valuated by charge rates, which are determined by cost centers and activity types. Work centers can be:

• Machines • People • Production lines • Groups of craftsmen

Work Center CategoryWork Center Category Attributes from TC30T.

Work Center FormulaCapacity formulas from TC25; parameters are parsed from the formula equation text.



INVALID HIERARCHIESThis set of classes reports hierarchy records that have failed validation in the Data Services job. Use this information to correct the source records in SAP solutions. Corrected data will be reloaded into the proper tables with the next Data Services job run. The sub-classes are:

• Invalid Activity Hierarchy• Invalid Cost Center Hierarchy• Invalid Cost Element Hierarchy• Invalid Functional Area Hierarchy• Invalid GL Acct Hierarchy• Invalid Internal Order Hierarchy• Invalid Profit Center Hierarchy• Invalid Project Element Hierarchy• Invalid Work Center Hierarchy

FILTERSThis top level folder represents pre-defined conditions that can be included in any report (filters). They are organized by subject area, and include the following sub-classes:

• Benefits Filters• Company Code Filters• Employee Filters• Financial Document Type Filters• Fiscal Period Filters• Hierarchy Filters

• Activity Filters• Bill of Materials Filters• Cost Center Filters• Cost Element Filters• Equipment Filters• Functional Area Filters• Functional Location Filters• GL Account Hierarchy Filters• Internal Orders Hierarchy• Organization Unit Filters• Position Filters



• Profit Center Hierarchy Filters• Project Element Filters• Work Center Filters

• Personnel Area Filters• Personnel Subarea Filters• Project Filters

TECHNIQUESThese are advanced technique objects developed for the Web Intelligence reports.

Master Data Universe LayoutHere is a graphical representation of the Master Data Universe as it appears in the universe designer:



Master Data Universe (1 of 3)



Master Data Universe (2 of 3):



Master Data Universe (2 of 3):

Universe Validation - Master DataWhen 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.


Integrity Check Results


Cardinality DivergencesThese are caused by the use of the “@prompt” function in the join. Since this function requires user intervention to complete the SQL join condition, the Universe Designer cannot check the cardinality vs. the database.Note: The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.


UniverseCustomizing the Universe 5

Customizing the UniverseThe SAP Plant Maintenance Universe and the SAP Service Master Universe can be modified easily to suit your specific needs. Here is an example:

Splitting the SAP Plant Maintenance UniverseIn the SAP Plant Maintenance Universe, contains several subject areas. Your company wants a new universe with just Notifications and MTBR MTTR subject areas; keeping the original universe as is. This creates two distinct reporting environments, one focused on notification reporting, the other on both notification and service order reporting.You can follow these steps to create two universes:1. Create a copy of the SAP Plant Maintenance Universe with file name:

• SAP-PM-Notifications.unv2. In the Universe Parameters, Definition tab, change the name of the

universe to:• SAP Plant Maint - Notifications

3. Go to the graphic representation of the universe, right click on SERVICE_ORDER_FACT and choose view associated objects. This will highlight a number of objects in left hand pane of the Universe Designer. These object should be deleted from the universe. Also delete any empty top level classes that remain for the objects after deletion.

4. Repeat previous step for• SERVICE_OPERATION_FACT• SERVICE_CONFIRMATION_FACT• SERVICE_COST_SUMMARY_FACT_HZ• SERVICE_COST_SUMMARY_FACT_VR

5. Delete these tables from the graphic representation of the universe:• SERVICE_ORDER_FACT• SERVICE_OPERATION_FACT• SERVICE_CONFIRMATION_FACT• SERVICE_COST_SUMMARY_FACT_HZ• SERVICE_COST_SUMMARY_FACT_VR

6. All joins associated with these tables will be deleted as you delete the tables.


UniverseCustomizing the Universe5

7. In the graphic representation, find all dimension tables not joined to a fact table. For each of these tables, right click on the table and choose view associated objects. Delete these objects from the universe. Also delete any empty top level classes for the objects.

8. If the un-joined dimensions have associated hierarchy tables you should delete all associated hierarchy objects and empty top level classes as well.

9. In the graphic representation, delete all dimension tables not joined to a fact table. This includes their associated hierarchy tables. Any joins between dimensions and hierarchies will also be deleted automatically when you do this.

10. Delete the following contexts in the universe:• Service Order Fact• Service Operation Fact• Service Confirmation Fact• Service Cost Summary HZ• Service Cost Summary VR

11. Validate and test the universe


Installing the Rapid Mart

chapter

Installing the Rapid MartOverview6
Overview
This chapter contains the information you need to install the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions. The information in this chapter is useful for system administrators or others who install the Rapid Mart. See ‘Documentation References’ chapter for Data Services and BusinessObjects Enterprise installation and configuration documentation location.This chapter contains the following sections:• System Prerequisites• Personnel Prerequisites• Rapid Mart product components• Preparing your environment• The Rapid Mart Package• Install the Rapid Mart Target Schema• Install the Data Services Job(s)• Installing Rapid Mart Reporting Content


Installing the Rapid MartSystem Prerequisites 6

System PrerequisitesTo run the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions, you need the following:• SAP solutions release 4.6 or higher.• SAP BusinessObjects Enterprise XI Release 2 or higher (for reporting

content only)• SAP BusinessObjects Data Services XI 3.2, or higher• A “Target” database that is one of:

• Oracle• Microsoft SQL Server• IBM DB2 UDB• Teradata

Note: Using Teradata as a target requires additional customizations and modifications to the Rapid Mart. View xi3_rm_sap_td_suppl_en.pdf document for details. We recommend that your consulting or technical staff be well versed in both Teradata and Data Services functionality before proceeding.

Consult the Supported Platforms document for details on supported versions of:• SAP solutions• BusinessObjects Enterprise• Data Services• Target databasesIf you are installing the Rapid Mart over network, the system you are using needs to have at least:• SAP BusinessObjects Data Services XI 3.2 Designer or higher• SAP BusinessObjects Enterprise XI Release 2 Client or higherIf you have questions about system prerequisites, contact SAP BusinessObjects Technical Support.


Installing the Rapid MartPersonnel Prerequisites6
Personnel Prerequisites
The Rapid Mart installation procedure is completely manual. There are many intricacies. We recommend the team installing the Rapid Mart be fluent with these SAP BusinessObjects products:• Data Services

• Designer• Job Server• Web Administration

• BusinessObjects Enterprise• Universe Designer• Web Intelligence Query Designer

For additional support we recommend expertise in:• SAP solutions Administration (BASIS)• Target Database DBA (Database Administration)


Installing the Rapid MartRapid Mart product components 6

Rapid Mart product componentsThe Rapid Mart is delivered as a Zip file that includes all major product components. These are organized as directories and sub-directories within the zipped file. The main directories are:• Data Model for the target database: This is an Integrated ERWin Data

Model of the complete target schema for all Rapid Marts related to SAP solutions. The ERwin file is called: • SAP_Integrated_Model.erwinThe model is built with AllFusion ERwin Data Modeler Release: 7.2. If you have ERwin release 7.2 or higher available, you can load the file and use it to extend and customize the data model.The model is used to generate SQL scripts for:• Creating Rapid Mart tables and views• Dropping Rapid Mart tables and views• Creating Rapid Mart indexes• Dropping Rapid Mart indexes• Creating database stored procedures• Dropping database stored procedures

• Documentation for the Rapid Mart including:• Business Guide• User Guide • Release Notes• Deployment Guidelines for Oracle• Integrated Data Model User Guide• White Paper on Rapid Marts manual upgrade process• Customizing Rapid Marts for Teradata Supplement• Rapid Marts Word Utility User Guide.

• ETL (Extract Transformation Load) logic including:• SAP BusinessObjects Data Services XI 3.2 ATL file that specifies the

full (initial) load and incremental (delta) update jobs. These jobs perform the extract from SAP solutions and load to the Rapid Mart target tables

• Auxiliary Data Files used by the jobs• Source code for custom ABAP programs used by the jobs


Installing the Rapid MartRapid Mart product components6

• Sample reporting SQL (DML): This is the SQL source statements extracted from each of the sample Web Intelligence reports delivered with the Rapid Mart. It also includes sample SQL (DDL) for suggested database procedures.

• Utilities (Rapid Mart Word Utility and Metadata Discovery Utility.) Both Word Utility and Metadata Discovery Utility are metadata reporting solutions designed to help you with the manual upgrade process and to enforce pre-defined naming conventions when developing or customizing Rapid Mart data model(s). It also provides better exposure of the data model metadata details.

• Visuals contains the Rapid Mart BIAR file (reporting content). These are the sample Webi reports and universes (semantic layer) included with the Rapid Mart.


Installing the Rapid MartPreparing your environment 6

Preparing your environment

Preparing Data ServicesFollow these steps to prepare your environment for the Rapid Mart installation:• Install SAP BusinessObjects Data Services XI 3.2 or higher, if it is not

already installed.Refer to the Data Services Installation Guide for detailed installation instructions.Make sure that you install the Data Services Designer and that you install and configure a Job Server and an Access Server. Though you need Data Services job server to run Rapid Mart jobs, you need just Data Services Designer to install Rapid Mart.Create a separate repository for Rapid Mart(s) after the Data Services installation using the Repository Manager. A Data Services repository is required to install the Rapid Mart ETL job (ATL file). It is recommended to import the ATL file(s) into an empty Data Services repository. Multiple Rapid Marts can be installed in the same repository.Make sure that the Job Server is associated to the repository. The association sign in the right bottom corner of Data Services Designer should be on:

If the association is inactive, the sign will have a red cross:

• Start Data Services Designer 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.

• Exit Data Services Designer.

Preparing Target Database EnvironmentPrepare your target database environment. • Currently the Rapid Mart supports Oracle, MS SQL Server, Teradata, and

DB2 as target databases.


Installing the Rapid MartPreparing your environment6

• Ensure there is an empty database schema/user for use as target database. Create one if necessary.

• Be sure to have the target database connection information (user name, password, etc.) available. Target database connection information is required when setting up connectivity in Data Services Designer.

• If your target database is Microsoft SQL-Server, make sure the database uses Case Sensitive collation (like Latin1_General_BIN).

Preparing Source Application• Confirm your SAP solutions version. Minimum required version is SAP

solutions release 4.6 or higher.• Sometimes Rapid Marts process data differently, depending upon the

version. See ‘Data Service Supplement for SAP’ document for details on how to setup connectivity between Data Services and SAP.

Preparing BusinessObjects Enterprise Follow these steps to prepare your environment for the Rapid Mart Reporting Content installation:• Ensure the SAP BusinessObjects Enterprise XI Release 2 or higher

Client is available on your installation machine.• Ensure BusinessObjects Enterprise Client has correct connectivity to the

CMS you will use for the sample reporting content. • The CMS must also be SAP BusinessObjects Enterprise XI Release 2 or

higher.• Ensure the Import Wizard utility is available to import the BIAR file.

Performance TuningThe table and index creation scripts provided in the Rapid Mart are a guideline and starting point. As no two installation environments are the same, we recommend a performance tuning analysis of the target environment considering:• Volume of data to be loaded, including growth rates• Physical disk layout and requirements• Network bandwidth• Frequency and duration of loads


Installing the Rapid MartPreparing your environment 6

• Reporting query volumes and most frequently used subject areas• Hardware configuration and capacity for all servers involved:

• SAP solutions server(s)• Data Services Job Server(s)• Target Database Server(s)• BusinessObjects Enterprise Server(s)

From this analysis you will be able to implement proper database storage parameters and proper indexes for your environment. It is invaluable to have a qualified DBA and appropriately trained technical staff for this analysis.


Installing the Rapid MartThe Rapid Mart Package6
The Rapid Mart Package
Download the Rapid Mart package.Choose an appropriate location on your installation server and run unzip/extract program to install the package. We recommend creating a subdirectory called as the Rapid Mart name (example SAPPM_RapidMart) under the Data Services directory of the installation server.This process will create a standard set of sub directories described in “Rapid Mart product components” on page 287 and ReadMe.txt file.


Installing the Rapid MartInstall the Rapid Mart Target Schema 6

Install the Rapid Mart Target SchemaThis section deals with the installation of the Rapid Mart target schema.The schema installation is manual.

Create Target SchemaAfter you unzip the Rapid Mart package, to go the DataModel sub-directory. You will find directories for each of the target databases supported:• Oracle• DB2• SQL Server• TeradataCreate the target schema using the files from the sub-directory for your target database.Note: The integrated data model includes the tables, views, and indexes used by all Rapid Marts for SAP solutions. Thus, execute the set of scripts only once when installing multiple Rapid Marts. The set of scripts is identical in all Rapid Marts for SAP solutions.

Create Target TablesIn the appropriate target database directory locate the files:• SAP_Create_Tables.sql• SAP_Create_Comments.sqlAs a quick start, execute the scripts in your target database. It will create all database tables and views used by the Rapid Mart. Creating comments is optional. It will ensure that Data Services will store tables and views with descriptions in its repository after you re-import the tables and views.Note: Please read notes below, and apply as needed:1. Use the results of Performance Tuning analysis to guide you in the

process of allocating storage space and physical disk location for your tables You may want to modify the table create script to include these parameters before execution.

2. If your target database is DB2 without Code Set UTF-8 (without multi-byte character support), you will need to edit the SAP_Create_Tables.sql script. Change all occurrences of data type VARGRAPHIC to VARCHAR before creating tables.


Installing the Rapid MartInstall the Rapid Mart Target Schema6

3. If your target database is DB2 with Code Set UTF-8 (with multi-byte character support), you do not need to make changes to SAP_Create_Tables.sql script.

4. If your target database is DB2, regardless of Code Set, you must have at least one tablespace with page size = 8 Kilobytes to accommodate column size (table width) on some tables. The tables affected by this are:• COST_CENTER_HIER_HZ• FUNCTIONAL_AREA_HIER_HZ• GL_ACCOUNT_HIER_HZ• PROFIT_CENTER_HIER_HZ• PROJECT_ELEMENT_HIER_HZ

Create Target IndexesCreating indexes is optional. We highly recommend that the DBAs first review the indexes and decide which indexes should be created to ensure proper performance for both ETL process and reporting query responses.In the appropriate target database directory locate the files:• SAP_Create_Indexes_All.sql• SAP_Create_Indexes_Performance.sqlThe first script includes all indexes for all tables in the data model. These include indexes for each foreign key in the model.The second script is a subset of indexes (from SAP_Create_Indexes_All.sql) tuned for performance in our internal SAP BusinessObjects development environment. This includes optimization for both Data Services load performance and reporting performance.For a quick start, we suggest starting with the SAP_Create_Indexes_Performance.sql file, and then creating / dropping indexes as needed in your environment.Note: Use the results of Performance Tuning analysis to guide you in the process of:• selecting indexes to create• allocating storage space• allocating physical diskYou may want to modify the index creation scripts to include these parameters before execution.


Installing the Rapid MartInstall the Rapid Mart Target Schema 6

Create Dummy ProceduresThe Rapid Mart contains 2 templates or “dummy” database procedures. As delivered, they are place holders for custom performance tuning. See Rapid Mart Deployment Guideline.pdf for more details on how to use these procedures.One procedure is called before each fact table load in the Rapid Mart, and the other after the fact table is loaded. The procedures need to be installed for the Data Services jobs to run. Locate the file:• Create_Dummy_Maintenance_SP.sqlExecute this file in your target database environment to create the dummy procedures.You can modify these procedures to help load performance. For example, the first procedure could be modified to drop secondary (foreign key) indexes on the fact table before a load. The other, could be modified to re-create these indexes (for query performance) at the end of the load. The Rapid Mart contains an example (File Create_Sample_Maintenance_SP.sql in the Sample directory) of how to do this with an Oracle target database.

Dropping Tables, Procedures and IndexesUse these scripts as needed to drop tables, procedures, views, and indexes. When starting with an empty target database / schema, they are not required for installation. They are provided to ensure a complete DDL (Data Definition Language) package for each target database.• Drop_Dummy_Maintenance_SP.sql

Note: The Oracle version of Create_Dummy_Maintenance_SP.sql uses Oracle’s “create or replace” syntax. Thus, no drop script is provided for Oracle.

• SAP_Drop_Indexes_All.sql• SAP_Drop_Indexes_Performance.sql• SAP_Drop_Tables.sql


Installing the Rapid MartInstall the Data Services Job(s)6
Install the Data Services Job(s)
This section deals with the installation of the Rapid Mart jobs using Data Services Designer. Installation of reporting content is covered in “Installing Rapid Mart Reporting Content” on page 314.The Rapid Mart Job Installation is manual.The ETL subdirectory for the Rapid Mart package contains the ATL file. ATL files are specific to each Rapid Mart and follow the naming convention• (RM_ABBR)_Rapid_Mart.atlExample: The Plant Maintenance Rapid Mart ATL file is named:• SAPPM_Rapid_Mart.atl

Renaming the Data StoresThis step is optional. You can configure and customize the Rapid Mart with Data Services Designer, except for changing Data Store names. The default names for the data stores in the ATL are• R3_DS for the SAP solutions data store• RM_DS for the target database data storeIf you are satisfied with these names, proceed to the next step, Import ATL File.To rename the data stores proceed as shown below.Note: This step is prone to human error. We strongly urge you to make a backup copy of the ATL file before you start.Open the ATL file in a text editor such as Wordpad.Note: DO NOT use Notepad. Notepad does not handle text wrapping properly and will corrupt the ATL file. We suggest Wordpad instead.Use the “global replace” function or “replace all” function to change all occurrences of the default SAP solutions data store name with one of your choosing. Example: using Wordpad


Installing the Rapid MartInstall the Data Services Job(s) 6

Before Replace All



After Replace All

Repeat these steps for the RM_DS data storeSave the ATL file.Note: DO NOT use the same name for the R3_DS and the RM_DS data stores as this will corrupt the file.

Import ATL FileSee ‘Data Services Designer Guide’ for details on importing files.• Start Data Services Designer and log on to the local repository where you

are going to install the Rapid Mart.Note: The example below uses the ATL file for the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions. Be sure to use file SAPPM_Rapid_Mart.atl instead of the file name shown in the example.



• From the Tools Menu choose Import From File:

• Choose the ATL File



• Click “OK” to any warnings. You might get pop-up windows warning that the import may take a long time, or that the ATL file was created with a lower version of Data Services. Answer “OK” to any of these. This will start the import process.Data Services will import the ATL file, creating all the repository objects required to run Rapid Mart load jobs.

Adjusting the Data StoresAs imported, the Rapid Mart data stores point to “dummy” data sources for both SAP solutions and your target database. You will need to provide proper connectivity and login information for both. • R3_DS (SAP solutions Data Store):Navigate to the Data Store:



Edit the Data Store:



Open “Advanced” Edit Window



Edit Data Store Settings.

Click OK to close Edit WindowClick OK to Close Advanced WindowThe Data Store window should close without any warnings or errors, indicating successful connection and log-in to the SAP solutions server.Note: The local repository must be associated with the Data Services Job Server to complete the R/3 datastore configuration successfully.Re-import R/3 tables used by the Rapid Mart. Use R/3 datastore ‘Reimport All...’ command you can access by right-clicking on the R/3 datastore name.

• RM_DS (Target Database Data Store):



Edit the Data Store:



Open “Advanced” Edit Window



Edit Data Store Settings.

Example: If your target database is Oracle, you would only change settings in “Configuration1” column. For SQL-Server, change only “Configuration2” column, etc.Note: For “RM_USER” alias, enter the target database schema owner:• For SQL Server - “dbo”• For Oracle and DB2 UDB - database user name• For Teradata - the schema ownerClick OK to close Edit Window



Click OK to Close Advanced WindowThe Data Store window should close without any warnings or errors, indicating successful connection and log-in to the Target Database server.Re-import target tables used by the Rapid Mart. Use the target datastore (RM_DS) ‘Reimport All...’ command you can access by right-clicking on the target (RM_DS) datastore name.

Using Auxiliary FilesAll Rapid Marts come with an auxiliary file: • dates.datThis file is used to load the Fiscal Period and Time Dimensions. After unzipping, this file is located in the ETL subdirectories, the path is:• ...\ETL\Files\Data\Note: There may be additional Rapid Mart specific files in this directory.



All files in this directory must be moved to the working directory you specified when Adjusting the Data Stores, as shown below:

Using ABAP FilesRapid Marts may come with additional ABAP files. These are ABAP code snippets used by the Rapid Mart to assist in extracting data from SAP solutions. • ABAP files always end with the suffix .abaThey are used when regular Data Services transformations are insufficient to extract the data. For example, they are used to read from a clustered table in SAP solutions.



At this writing, only four Rapid Marts use ABAP files• SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects Human Resources Rapid Mart, version for SAP

solutions• SAP BusinessObjects Production Planning Rapid Mart, version for SAP

solutionsIf used, these files are located in:• ...\ETL\Files\ABAP\Some examples of the files found in the Cost Center and GL Rapid Marts are:• RF011F_NEW.aba• RF011F_OLD.aba• RF011P_NEW.aba• RF011P_OLD.aba• etc.Note: For SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Only: be sure to choose the correct files for your SAP solutions version:There are two versions of these files:• PA0167_ABAPXFORM.aba• PA0168_ABAPXFORM.abaIf you are running SAP solutions version 5.0 or newer, choose the files in directory:...\ETL\Files\ABAP\ABAP50If you are running SAP solutions version 4.6, choose the files in directory:...\ETL\Files\ABAP\ABAP46



All these files should be moved to the Generated ABAP directory you specified when Adjusting the Data Stores, as shown below:

Then, make sure the Data Services transforms using these files point to the Generated ABAP directory as shown below.



1. Open Data Services and navigate to the Transforms tab of the Local Object Library:

Note: This step applies only to:• SAP BusinessObjects Cost Center Rapid Mart, version for SAP

solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects Human Resources Rapid Mart, version for

SAP solutions• SAP BusinessObjects Production Planning Rapid Mart, version for

SAP solutionsFor the rest of Rapid Marts, you will not see Custom ABAP transforms in the Transforms tab.



2. Then, change path to be the same as where the ABAP files are installed

3. Repeat this step for all the other ABAP transforms in the Object Library4. Save the changes5. Validate the Data Services jobs to ensure they are working correctly.

Final Steps• If your Job Server runs on a UNIX system, using Data Services Designer

adjust the directory paths in all Rapid Mart file format definitions to follow the UNIX convention (that is, change from “/” to “\”).



• Before running the job, you must initialize some global variables. For information about executing the Rapid Mart job, see Chapter 7: Using the Rapid Mart.

• Rapid Marts are developed against standard out-of-the-box SAP solutions 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;• 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” conditions in Query Transforms if necessary. Look for hard-coded constraints and other conditions that need to be customized.


Installing the Rapid MartInstalling Rapid Mart Reporting Content6
Installing Rapid Mart Reporting Content
Rapid Marts come with their own Reporting Content, supplied as Web Intelligence reports and universes (semantic layer.) In order to use the Reporting Content you must first install them to your BusinessObjects Enterprise system and configure a connection to your Rapid Mart target database.If the BusinessObjects Enterprise server (CMS) is located on a different machine, you need to have BusinessObjects Enterprise client installed, with connectivity to that server.The Reporting Content is delivered as a BIAR file, located in the unzipped Visuals sub-directory:• Directory Path: ...\Visuals\• File Name: sappm_Rapid_Mart_Visuals.biarNote: We recommend that you start with a clean CMS, or by deleting any old versions of Rapid Mart reports or universes. This will avoid confusion with older versions.

Import Wizard for Reporting Content BIAR FileUse the BusinessObjects Enterprise Import Wizard to import the BIAR file. The Import Wizard can be identified by this icon:

Start the Import Wizard and follow these instructions. Note: The screen shots here are from SAP BusinessObjects Enterprise XI Release 3. Some screens do not appear in SAP BusinessObjects Enterprise XI Release 2. The missing screens are indicated below. If you are using SAP BusinessObjects Enterprise XI Release 2, simply ignore the missing screens.


Installing the Rapid MartInstalling Rapid Mart Reporting Content 6

On the first screen, click “Next”:



Choose BIAR File:

Note: The BIAR file for the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions is used in this illustration. You should use the proper file for the Plant Maintenance Rapid Mart located in Directory: ...\VisualsFile: sappm_Rapid_Mart_Visuals.biar



Choose CMS:



Select Object to Import - Check or Uncheck Boxes:

Note: The number of boxes to check on this screen may vary between BusinessObjects Enterprise releases. Regardless of release, just make sure only the “import folders and objects” box is checked.Do not click “Next” on this screen. Proceed to next page.



Select Object to Import - Check or Uncheck Boxes (continued):

Note: The number of boxes to check on this screen may vary between BusinessObjects Enterprise releases. Regardless of release, just make sure only the “import universes” box is checked.



Check Import Scenario Radio Buttons as shown

Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2



Incremental Import - Check or Uncheck Boxes:



Acknowledge Message, Click Next



“Select All” to import complete contents of BIAR file.



Universe & Connection Options- Check or Uncheck as shown



Ensure All Objects are Selected:

Write down universe names. There can be more than one universe per a Rapid Mart. You will need these names later when creating Universe connection.



Select Import Options for Publications:

Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2



Acknowledge message, Click “Next”:



Verify Correct List of Objects to Import, Click FINISH to start import:



Wait for Import to Finish. Then Click “View Detail Log”:

Click on each item imported. Make sure there are no errors:



Click Done to Exit the Import Wizard:

This completes the Import Wizard for Reporting Content.

Creating Universe ConnectionNow use the Universe Designer to change the connection in the imported universe(s).



Start the Universe Designer, and import the universe(s) by choosing File -> Import. Select universe(s) you wrote down when importing the BIAR file in the previous step and import all of them. Then, navigate to the Universe Parameters Screen:



For each universe, either choose an existing connection to Rapid Mart target database, or create a new one:

Note: This illustration uses the SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions as an example only. The Universe Designer will show the correct universe name for your Rapid Mart Note: Consult the SAP BusinessObjects Universe Designer Guide for details on how to assign or create a connection.When done, export the universe(s) back to the CMS by choosing File -> Export in the Universe Designer.This concludes Rapid Mart installation.


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• Global Variables• Executing the job• 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 Services automatic recovery feature• Rapid Mart recovery framework

Data Services automatic recovery featureWith automatic recovery, Data Services 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 Services 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 Services 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.


Using the Rapid MartRecovery framework 7

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 SAP solutions source tables occur between the failed run and the recovery run. 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 Services does not re-run a successfully completed work flow; therefore, the first table is not loaded again. However, Data Services 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 SAP solutions 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 incremental (or delta) execution, the Rapid Mart job extracts data between a start date and an end date. This is determined by setting the global variable $G_LOAD_TYPE = ‘DELTA’. 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. Note: There are exceptions to this, as certain subject areas may have delta loads that use a different methodology. Consult the Technical Implementation chapter for details on the delta loads for each subject area.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.


Using the Rapid MartExecution status framework7

To maintain consistency with data flowing to SAP solutions, 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, many work flows use the auto correct load option or the Table Comparison transform. Both of these check for an existing row with the same key as each row flagged as an insert or update activity. If the row exists, Data Services updates the row. If the row does not exist, Data Services 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.

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

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.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 338. 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.


Using the Rapid MartExtraction, transformation and loading process7

• 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, 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 (global variables $G_SDATE and $G_EDATE) to remain the same as the values you set set in the initialization script or job properties. 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 or execution properties and set global variable $G_RUN_MODE = ‘RESET’. When using reset mode, be sure that the global variables $G_SDATE and $G_EDATE are set so that no gaps in data occur.

Extraction, transformation and loading process

The job Plant_Maintenance_Load executes objects that load the load the data from SAP solutions to Rapid Mart target database. 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 Plant_Maintenance_Load job and selecting the Properties command from the drop-down list. Most of the Plant Maintenance 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 frameworkNote: If you plan to change global variable settings from the default “as shipped” values, we suggest you do so in the initialization script. The initialization script executes after the global variables are set in the


Using the Rapid MartGlobal Variables7

properties window. Thus, you can preserve the “as shipped” values for reference in the properties window, while still using your own values as set in the initialization script.

• 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.

• 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 final script that updates the job execution status table

Global VariablesAll Rapid Mart jobs use a standardized set of Global Variables. For completeness, and multiple Rapid Mart integration. They are included with each Rapid Mart job, regardless if they are used by the job.

Global Variable Cross-ReferenceA complete Cross-Reference Matrix of Global Variables is shown below. It is organized in three sections grouped by how many Rapid Marts use each Global Variable:• Used in All Rapid Marts• Used in 2 to 10 Rapid Marts• Used in Only 1 Rapid Mart


Using the Rapid MartGlobal Variables 7

The global variables in each of these sections are described in detail after the matrix.

Global Variable Name Data Type

AP AR CA GL HR IA PM PP PR PS SA

Used in all 11 Rapid Marts$G_CCODE varchar(4) X X X X X X X X X X X

$G_DEFAULT_DATE datetime X X X X X X X X X X X

$G_DEFAULT_NUMBER int X X X X X X X X X X X

$G_DEFAULT_TEXT varchar(1) X X X X X X X X X X X

$G_EDATE datetime X X X X X X X X X X X

$G_LANGUAGE varchar(1) X X X X X X X X X X X

$G_LOAD_DATE datetime X X X X X X X X X X X

$G_LOAD_TIME varchar(8) X X X X X X X X X X X

$G_LOAD_TYPE varchar(7) X X X X X X X X X X X

$G_MAX_DATE datetime X X X X X X X X X X X

$G_REBUILD_INDEXES varchar(1) X X X X X X X X X X X

$G_RUN_MODE varchar(10) X X X X X X X X X X X

$G_SDATE datetime X X X X X X X X X X X

Used in 2 to 10 Rapid Marts$A int X X

$B int X X

$C int X X

$D int X X

$E int X X

$F int X X

$G int X X

$G_ABSOLUTE_START_DATE

datetime X X X X X

$G_ENDFISCALYEAR int X X X X X X

$G_EXCHANGE_TYPE_ID varchar(4) X X X

$G_GLOBAL_CURRENCY varchar(5) X X X

$G_INT_ORDER_CATEG_PP

varchar(2) X X

$G_INT_ORDER_CATEG_PS

varchar(2) X X

$G_ORIG_SDATE datetime X X X

$G_STARTFISCALYEAR int X X X X X X



Used in Only 1 Rapid Mart$G_ADDRESS_VERSION varchar(1) X

$G_BUS_PARTN_SDATE datetime X

$G_BUS_PARTNER varchar(1) X

$G_COST_OF_SALES_LEDGER_ID

varchar(2) X

$G_COUNTRY_GRP varchar(2) X

$G_DEL_PERIOD datetime X

$G_DEL_REJECT_REASON varchar(2) X

$G_DROP_SHIP varchar(1) X

$G_GL_ACCOUNT_HIER_NAME

varchar(10) X

$G_GL_SUM_PLAN_LEDGER_ID

varchar(2) X

$G_GL_VERSION varchar(3) X

$G_HIRE_ACTION_01 varchar(2) X



$G_INIT_HIST_CHG varchar(1) X

$G_MALFUNCTION_CAUSE varchar(20) X

$G_MALFUNCTION_DAMAGE

varchar(20) X

$G_MALFUNCTION_OBJ_PART

varchar(20) X

$G_MRP_RESULTS_DELETE

varchar(1) X

$G_ONTIME_DELIV_WINDOW

int X

$G_PC_ACCOUNT_HIER_NAME

varchar(10) X

$G_PROFIT_CENTER_LEDGER_ID

varchar(2) X

$G_REHIRE_ACTION_01 varchar(2) X

$G_REHIRE_ACTION_02 varchar(2) X

$G_RETIRE_ACTION varchar(2) X

$G_SAP_VERSION int X

$G_SCHOOL_TYPE varchar(2) X





$G_SERVICE_INTERVAL_01 int X





$G_TABLE_EQUIPMENT varchar(20) X

$G_TABLE_FUNCTL_LOCATN

varchar(20) X

$G_TASK_TYPE_PROBATION_END

varchar(2) X

$G_TERMINATION_ACTION varchar(2) X

$G_VALID_DATE datetime X

$G_WAGE_TYPE_01 varchar(4) X




















$G_WORKDAY_EDATE datetime X

$G_WORKDAY_SDATE datetime X




Used in All Rapid Marts
$G_CCODE Data Type: varchar(4)Default Value: “0001”The SAP solutions Company Code used for Time Dimension extraction. The fiscal variant associated with this company code is used to determine the fiscal periods of the Time Dimension.Set this to the Company Code that carries the Fiscal Calendar (determined by the Fiscal Variant) that best suits your needs.

$G_DEFAULT_DATE Data Type: datetimeDefault Value: 31-Dec-9999The default date for missing dates.

$G_DEFAULT_NUMBER Data Type: intDefault Value: -1Default number for dimension default rows, foreign keys, and primary keys. Also used as a default for missing numbers.

$G_DEFAULT_TEXT Data Type: varchar(1)Default Value: “?”Default text for dimension default rows, foreign keys, and primary keys. Also used as a default for missing descriptions.

$G_EDATE Data Type: datetimeDefault Value: NULLThe ending date for data extraction.For first (initial) run or incremental (delta) runs, we recommend leaving this empty (null). The Initialize job script and function AW_StartJob will automatically determine the proper value.



if you set the variable, jobs will not extract data entered into your SAP solutions system after this date. For example, if your end date is June 4, 1999, the jobs will not extract data for June 5, 1999 or later.

$G_LANGUAGE Data Type: varchar(1)Default Value: “E” (English)The language in which jobs extract text descriptions. Use the SAP solutions standard language abbreviations if you require a different language.

$G_LOAD_DATE Data Type: datetimeDefault Value: System Date and TimeAlways set to current system date and time by the Job Initialization script. Do not change the setting of this variable.

$G_LOAD_TIME Data Type: varchar(8)Default Value: System TimeAlways set to current system time by the Job Initialization script. Do not change the setting of this variable.

$G_LOAD_TYPE Data Type: varchar(7)Default Value: “FIRST”Legal values:• FIRST - for the initial or first load• DELTA - for incremental or delta loadsSetting this variable to anything else will cause the job to fail.

$G_MAX_DATEData Type: datetimeDefault Value: 31-Dec-9999Used in date effective transforms to match SAP value for “infinite” date as end of validity period.


$G_REBUILD_INDEXES
Data Type: varchar(1)Default Value: “N” on Weekdays, “Y” on WeekendsLegal values:• Y - Run rebuild indexes script• N - Do not run rebuild indexes scriptAs delivered, this is a place holder for custom performance tuning. See Rapid Mart Deployment Guideline.pdf for more details on how to use this variable in conjunction with the stored procedures in file Create_Sample_Maintenance_SP.sql.These stored procedures drop indexes before a Fact Table load, and re-create the indexes when the load is complete.Use this variable to further restrict the drop and re-create to weekends only.

$G_RUN_MODE Data Type: varchar(10)Default Value: NULLLegal values:• RESET - Forces job to reload from value set in $G_SDATE. • NULL - Uses AW_JOBEXECUTION to determine $G_SDATE.When set to “RESET”, this variable forces the Rapid Mart to use the starting extract date you have set for variable $G_SDATE. Otherwise, the setting is determine by querying table AW_JOBEXECUTION, and using the EXTRACTHIGH value of the last successful run.

$G_SDATE Data Type: datetimeDefault Value: 01-Jan-1990The start date for data extraction. During an initial extract, the job does not extract data that was entered into your SAP solutions system prior to $G_SDATE. For example, if your start date is January 26, 2000, the initial extract job does not extract data that was entered on January 25, 2000 or earlier. During incremental (delta) extractions, the job only extracts data modified or entered on or after this date. The incremental load job only uses the $G_SDATE when one of these conditions is true:



• Execution status table AW_JOBEXECUTION has no rows that correspond to the current job.

• The variable $G_RUN_MODE is set to “RESET” in the initialization script for the job.

Otherwise, the incremental job determines $G_SDATE by querying table AW_JOBEXECUTION and using the EXTRACTHIGH of the last successfully executed job.If there was no previous successful execution, the EXTRACTLOW value is used.

Used in 2 to 10 Rapid Marts

$A Data Type: intDefault Value: 30Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for

SAP solutions• SAP BusinessObjects Accounts Receivable Rapid Mart, version for

SAP solutions1 of 4 configurable past time periods (in days) to use for aged receivables and payables and late payments.

$B Data Type: intDefault Value: 60Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions2 of 4 configurable past time periods (in days) to use for aged receivables and payables and late payments

$C Data Type: intDefault Value: 90



Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for



$D Data Type: intDefault Value: 120Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for



$E Data Type: intDefault Value: 14Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions1 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)

$F Data Type: intDefault Value: 30Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for

SAP solutions



• SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions

2 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)

$G Data Type: intDefault Value: 45Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions3 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)

$G_ABSOLUTE_START_DATEData Type: datetimeDefault Value: NULLWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP


SAP solutions• SAP BusinessObjects Inventory Rapid Mart, version for SAP

solutionsEarliest date to use for delta load of Financial Documents, (in AP, AR, and GL Rapid Marts). Closed documents created before this date WILL NOT be loaded to the Rapid Mart. It works in conjunction with variable $G_ORIG_SDATE for incremental loads that do not carry a “date of last change” in the SAP solutions tables.See the Technical Implementation chapter for each specific Rapid Mart for full details on how this variable is used.



In General: If you set Absolute Start Date in the initialization script, this is the value that will be used in the delta load. If Absolute Start Date is NOT set in the initialization script (the default value NULL), the date of the earliest OPEN Document will be used. We use the earliest OPEN date because the earliest open document may have been closed since your last load. So, to be sure it is re-loaded as a “closed” item, we need to use the earliest open date from the last load. This is stored as the MIN(ENTRY_DATE) in associated Fact Table for open documents

$G_ENDFISCALYEARData Type: intDefault Value: NULLWhere Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects Cost Center Rapid Mart, version for SAP

solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects Plant Maintenance Rapid Mart, version for

SAP solutions• SAP BusinessObjects Project Systems Rapid Mart, version for SAP

solutionsDetermines the last fiscal year to be extracted for certain incremental loads. This is used when a “date of last change” is not available in SAP solutions, but the fiscal year of a transaction is available. This is usually the year from global variable $G_EDATE.

$G_EXCHANGE_TYPE_IDData Type: varchar(4)Default Value: “M” - Standard Translation at Average RateWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions



• SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed for lookup of exchange rates to Global Currency

$G_GLOBAL_CURRENCYData Type: varchar(5)Default Value: “USD” - U.S. DollarWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsGlobal Currency Code. You assign a global currency for the Rapid Mart. Used to present a consolidated picture of monetary values in one universal currency.

$G_INT_ORDER_CATEG_PPData Type: varchar(2)Default Value: “10”Where Used: • SAP BusinessObjects Production Planning Rapid Mart, version for

SAP solutions• SAP BusinessObjects Project Systems Rapid Mart, version for SAP

solutionsPRODUCTION_ORDER_FACT is a common table in each of these Rapid Marts. However, we extract a different Order Category in each. The default values for Production Orders (PP Rapid Mart) is 10Note: If you have only the PP Rapid Mart set values for both $G_INT_ORDER_CATEG_PP and $G_INT_ORDER_CATEG_PS to 10.

$G_INT_ORDER_CATEG_PSData Type: varchar(2)Default Value: “20”Where Used: • SAP BusinessObjects Production Planning Rapid Mart, version for

SAP solutions



• SAP BusinessObjects Project Systems Rapid Mart, version for SAP solutions

PRODUCTION_ORDER_FACT is a common table in each of these Rapid Marts. However, we extract a different Order Category in each. The default values for Network Orders (PS Rapid Mart) is 20Note: If you have only the PS Rapid Mart set values for both $G_INT_ORDER_CATEG_PP and $G_INT_ORDER_CATEG_PS to 20.

$G_ORIG_SDATEData Type: datetimeDefault Value: NULLWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP


SAP solutions• SAP BusinessObjects Inventory Rapid Mart, version for SAP

solutionsThis is set on the first (initial) load. It is the value of $G_SDATE at the time of that first load. It is stored in database table AW_FIRST_RUN_DATE. During “DELTA” (incremental) loads, it is retrieved from that table. It is used in several Rapid Marts to determine the start date for the load of OPEN items. It works in conjunction with variable $G_ABSOLUTE_START_DATE for incremental loads that do not carry a “date of last change” in the SAP solutions tables.

$G_STARTFISCALYEARData Type: intDefault Value: NULLWhere Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions



• SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions

• SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions

• SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions

• SAP BusinessObjects Project Systems Rapid Mart, version for SAP solutions

Determines the first fiscal year to be extracted for certain incremental loads. This is used when a “date of last change” is not available in SAP solutions, but the fiscal year of a transaction is available. This is usually the year from global variable $G_SDATE.

Used in Only 1 Rapid Mart

$G_ADDRESS_VERSIONData Type: varchar(1)Default Value: “ “ A single spaceWhere Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed for Extraction of Central Address dimension from table ADRC. Default value is a single space.

$G_BUS_PARTN_SDATEData Type: datetimeDefault Value: System Date - 8Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed in data flow R3_SalesOrdVBPADelta. Tells how many days back in time we will check for changes in sales document partners (bill-to partner, ship-to partner, etc.) Used in conjunction with variable $G_BUS_PARTNER.

$G_BUS_PARTNERData Type: varchar(1)Default Value: Sunday = Yes, all other days = No



Actual ATL Language Code: “ifthenelse(day_in_week(sysdate())=7,'Y','N')”Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed in Component Work Flow C_SalesOrderNumberDelta_SAPIf “Y” (Sunday), the Rapid Mart will extract an incremental load of business partners going back the number of days set in variable $G_BUS_PARTN_DATE (see above).

$G_COST_OF_SALES_LEDGER_IDData Type: varchar(2)Default Value: “0L”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsIn New GL, identifies the subset of the New FI-SL Standard Ledger that is loaded into the Cost of Sales Detail and Summary Subject Areas. Choose the Ledger ID in your business that best captures the Cost of Sales functionality.

$G_COUNTRY_GRPData Type: varchar(2)Default Value: “10”Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsDefault Country Grouping Code for HR as determined in SAP solutions table T500L.

$G_DEL_PERIODData Type: datetimeDefault Value: System Date - 180Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed in Sales Order Incremental Load. Determines how far back (in days) the Rapid Mart checks for orders that have been deleted in SAP solutions.

$G_DEL_REJECT_REASONData Type: varchar(2)Default Value: “DD”



Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsIdentifier used in the REJECT_REASON_ID field of SALES_ORDERS_FACT when a sales order line has been deleted in SAP solutions. The code is also added to the dimension table REJECT_REASON with the description “Deleted”.

$G_DROP_SHIPData Type: varchar(1)Default Value: “Y” - Calculate backlog for third-party deliveryWhere Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsThird-party deliveries are those that are delivered by an outside (third-party) organization such as a fulfillment house. They can also be for an intangible material (such as a service) where no physical item is delivered.When set to “Y” (Yes) the Rapid Mart calculates backlog as:• Qty Ordered - Qty Invoiced (for third-party items)• Qty Ordered - Qty Delivered (for all other items).When set to “N” (No) the Rapid Mart calculates backlog as:• Qty Ordered - Qty Delivered (for all items).

$G_GL_ACCOUNT_HIER_NAMEData Type: varchar(10)Default Value: “@GL”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsThe GL Account Hierarchy tables in the Rapid Mart use field “HIER_ID” to identify the source of the hierarchy entry. Data from SAP solutions transaction GS03, source hierarchy GLT0-RACCT are assigned “@GL”You can change the assignment of this variable. However, this is not a requirement. See Technical Implementation Chapter in the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions User Guide for more information.


$G_GL_SUM_PLAN_LEDGER_ID
Data Type: varchar(2)Default Value: “L6”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsIn New GL, identifies the subset of the New FI-SL Standard Ledger that is loaded into the GL Plan and GL Summary Subject Areas. Choose the Ledger ID that best captures GL Summary and GL Plan functionality.

$G_GL_VERSIONData Type: varchar(3)Default Value: (see below)Legal Values: “OLD” or “NEW”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsTells which version of SAP solutions GL Module you use. Using “NEW” with SAP solutions releases older than ECC 5.0 is not possible as the New GL module did not exist in these earlier releases. In the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions, there are two jobs, one for OLD GL and one for NEW GL. The default value in the NEW GL job is “NEW”. The default value in the OLD GL job is “OLD”.

$G_HIRE_ACTION_01Data Type: varchar(2)Default Value: “01”Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsHiring Action Variable 01

$G_HIRE_ACTION_02Data Type: varchar(2)Default Value: “90”Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsHiring Action Variable 02



$G_HIRE_ACTION_03Data Type: varchar(2)Default Value: “K1”Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsHiring Action Variable 03

$G_INIT_HIST_CHGData Type: varchar(1)Default Value: “Z”Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed during the initial load of SALES_ORDER_HISTORY table.IF default value “Z”, then • SALES_ORDER_HISTORY.QTY_DELTA_ORDER_SLSUOM = 0• SALES_ORDER_HISTORY.AMT_DELTA_NET_VALUE_TRX = 0 If any other value, then • SALES_ORDER_HISTORY.QTY_DELTA_ORDER_SLSUOM =

SALES_ORDER_FACT.QTY_ORDER_SLSUOM• SALES_ORDER_HISTORY.AMT_DELTA_NET_VALUE_TRX =

SALES_ORDER_FACT.AMT_NET_VALUE_TRX

$G_MALFUNCTION_CAUSEData Type: varchar(20)Default Value: “5”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsCatalog type to use for Malfunction Cause on Notifications. Choose your system notification catalog group type for “Cause”.

$G_MALFUNCTION_DAMAGEData Type: varchar(20)Default Value: “C”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions



Catalog type to use for Malfunction Damage on Notifications. Choose your system notification catalog group type for “Damage”.

$G_MALFUNCTION_OBJ_PARTData Type: varchar(20)Default Value: “B”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsCatalog type to use for Malfunction Object Part on Notifications. Choose your system notification catalog group type for “Object Part”.

$G_MRP_RESULTS_DELETEData Type: varchar(1)Default Value: “N”Where Used: SAP BusinessObjects Production Planning Rapid Mart, version for SAP solutionsDetermines if MRP Results should be deleted before an Incremental Load. • Y = Delete before Incremental Load. • N = No Delete before Incremental Load

$G_ONTIME_DELIV_WINDOWData Type: intDefault Value: 15 daysWhere Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed by On Time Delivery Section. Tells the system to limit On Time Delivery loads to a date range based on the Sales Schedule Line’s Planned Goods Issue Date (SAP solutions field VBEP.WADAT). It means that the On Time Delivery will only process Sales orders scheduled to ship between 15 days in the past and 15 days in the future from system date.

$G_PC_ACCOUNT_HIER_NAMEData Type: varchar(10)Default Value: “@PC”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions



The GL Account Hierarchy tables in the Rapid Mart use field “HIER_ID” to identify the source of the hierarchy entry. Data from SAP solutions transaction GS03, source hierarchy GLPCT-RACCT are assigned “@PC”You can change the assignment of this variable. However, this is not a requirement. See Technical Implementation Chapter in the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions User Guide for more information.

$G_PROFIT_CENTER_LEDGER_IDData Type: varchar(2)Default Value: “L5”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsIn New GL, identifies the subset of the New FI-SL Standard Ledger that is loaded into the Profit Center Detail and Summary Subject Areas Choose the Ledger ID that best captures Profit Center Summary and Profit Center functionality.

$G_REHIRE_ACTION_01Data Type: varchar(2)Default Value: "JD"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsRehiring Action Variable 01

$G_REHIRE_ACTION_02Data Type: varchar(2)Default Value: "N7"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsRehiring Action Variable 02

$G_RETIRE_ACTIONData Type: varchar(2)Default Value: "ZP”



Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsRetirement Action

$G_SAP_VERSIONData Type: intDefault Value: System Determined - see belowWhere Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsAutomatically determined in the Rapid Mart jobs. The first digit of the SAP solutions system variable SY-SAPRL. See Work Flow C_SAPVersion for more details. This value is also stored in the one row target table SAP_VERSION.Attempting to run the “NEW” GL job with SAP solutions older than release ECC 5.0 will cause the job to fail.

$G_SCHOOL_TYPEData Type: varchar(2)Default Value: "50"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsSchool Type

$G_SERVICE_INTERVAL_01Data Type: INTDefault Value: 6 (1/2 year)Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of 5 Intervals for determining Employee Length of Service. Values are in Months.

$G_SERVICE_INTERVAL_02Data Type: INTDefault Value: 12 (1 year)Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions



One of 5 Intervals for determining Employee Length of Service. Values are in Months.

$G_SERVICE_INTERVAL_03Data Type: INTDefault Value: 36 (3 years)Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of 5 Intervals for determining Employee Length of Service. Values are in Months.



$G_TABLE_EQUIPMENTData Type: varchar(20)Default Value: “EQUI”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsInitialize according to your system class type for Equipment master table name

$G_TABLE_FUNCTL_LOCATNData Type: varchar(20)



Default Value: “IFLOT”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsInitialize according to your system class type for Functional Location master table name

$G_TASK_TYPE_PROBATION_ENDData Type: varchar(2)Default Value: “01”Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsProbation End Task Type

$G_TERMINATION_ACTIONData Type: varchar(2)Default Value: “10”Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsTermination Action

$G_VALID_DATEData Type: datetimeDefault Value: System Date (without Time)Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsThis is identical to variable $G_LOAD_DATE without the timestamp (midnight, beginning of the day). Used in the incremental load of Sales Organization Hierarchy for comparison to with the VALID_TO dates. Do not change the value in this variable.

$G_WAGE_TYPE_01Data Type: varchar(4)Default Value: "/101"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions



One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_02Data Type: varchar(4)Default Value: "/110" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.




$G_WAGE_TYPE_06Data Type: varchar(4)



Default Value: "/405" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_07Data Type: varchar(4)Default Value: "/406"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.







$G_WAGE_TYPE_12Data Type: varchar(4)Default Value: "/5U0"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_13Data Type: varchar(4)Default Value: "/5U1" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_14Data Type: varchar(4)Default Value: "MI10" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_15Data Type: varchar(4)Default Value: "/102"



Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_16Data Type: varchar(4)Default Value: "////"Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.







$G_WORKDAY_EDATEData Type: datetimeDefault Value: 01-Jan-1994Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsFirst date of date range to populated Working Days dimension

$G_WORKDAY_SDATEData Type: datetimeDefault Value: 31-Dec-2006Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutionsLast date of date range to populated Working Days dimension

Setting Global Variables

Job PropertiesThe default values for most Global Variables are set on the Job Properties window (shown below) of the Rapid Mart jobs. The exceptions are Global Variables that are conditional (an “IF” statement is required).The conditional Global Variables are set in the “InitializeJob” Script (see below). The script is a common component (identical across all Rapid Marts).



Job Properties:

“InitializeJob” ScriptThe script is divided into the same sections categorizing Global Variables as shown above:• Used in All Rapid Marts• Used in 2 to 10 Rapid Marts• Used in Only 1 Rapid MartEach of these sections in the script shows the same information as the sections above as comments.These are followed by a fourth section where the Conditional Global Variables are set.



Note: The “InitializeJob” script is the first executable in any Rapid Mart job. If you have set Global variables on the Job Properties window in Data Services and also in the “InitializeJob” script, the values in the script will be used. They will override any setting in the Job Properties window.Tip: We suggest that you not touch the settings in the Job Properties window. Make any changes to the Global Variable settings in the InitializeJob script, as shown below. Thus, you can preserve the original “as delivered” settings while still using your own.Custom Global Variable Settings:.

Next, the fourth section of the “InitializeJob” script sets the Conditional Global Variables.



Conditional Global Variables in InitializeJob Script:

The Conditional Settings section also determines that certain global variable settings are accurate and compatible:• $G_LOAD_TYPE - Is either “FIRST” or “DELTA”. Any other setting will

cause the job to abort• $G_GL_VERSION - Is either “OLD” or “NEW”. Any other setting will

cause the job to abort.This section also calls certain Rapid Mart functions to properly set up the job environment:• AW_StartJob - Stores the current job execution parameters in table

AW_JOBEXECUTION.• RM_PutFirstRunDate - Called in “FIRST” (initial) loads only. Stores the

contents of $G_SDATE and $G_EDATE for the “FIRST” (initial) load in table AW_FIRST_RUN_DATE. These dates are important in delta (or incremental) loads later on.


Using the Rapid MartExecuting the job 7

• RM_GetFirstRunDate - Called in “DELTA” (incremental) loads only. Retreives the value of $G_SDATE stored in table AW_FIRST_RUN_DATE. The value retreived is stored in global variable $G_ORIG_SDATE. Consult the Techinical Implementation Chapter for each individual Rapid Mart for more details on how this is used.Note: If you set your own value for $G_ORIG_DATE before the call to RM_GetFirstRunDate, the Rapid Mart will use your value and not retreive the value in AW_FIRST_RUN_DATE.

Executing the jobBefore executing the job, make sure that the configuration steps in "Data Services Supplement for SAP" have been completed and the connection to SAP server is established.The steps needed to execute a job, depend on the type of job:• Initial (First) Extraction and Load • Incremental (Delta) Extraction and Load

Initial (First) Extraction and Load1. In the project area right-click in the Plant_Maintenance_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. In either the Properties window, or the job initialization script, set the starting and ending dates 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 or the job initialization script, and click OK to accept the set properties and to close the window.

Note: We suggest setting global variables in the job initialization script. That way the Properties window will preserve the “as delivered” settings, while the initialization script will show your custom settings. The initialization script executes after the values in the Properties window are set, and overrides the setting in the Properties windows.


Using the Rapid MartExecuting the job7

You can also set global variable values after you select Execute command from the drop-down menu in the project area.For more information about the variables see “Global Variables” on page 340.

3. Run the job.a. In the project area, right-click the job and choose Execute.

Data Services 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 Services 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.

Incremental (Delta) Extraction and Load1. Open the Properties window for job Plant_Maintenance_Load by

right-clicking on the job in the project area and selecting Properties command. Edit the job Global Variable properties (remember, you can also set the values in the job initialization script instead of using the Properties window):a. Make sure that the value for the $G_LOAD_TYPE global variable is

set to ‘DELTA’.


Using the Rapid MartExecuting the job 7

b. Set the starting and ending time periods for the delta load. The standard setting is the yesterday’s date for the starting date ($G_SDATE) and today’s date for ending date ($G_EDATE). This assumes the Initial (First) load has already successfully loaded all data through yesterday.

c. Set values for the rest of global variables as needed. d. Click OK to accept the set properties and to close the window.Note: We suggest setting global variables in the job initialization script. That way the Properties window will preserve the “as delivered” settings, while the initialization script will show your custom settings. The initialization script executes after the values in the Properties window are set, and overrides the setting in the Properties windows.

2. Run the job.a. In the project area, right-click the job and choose Execute.

Data Services 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 Services 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.


Using the Rapid MartCustomizing the Rapid Mart7
Customizing the Rapid Mart
Rapid 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 Services 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• 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 Services application. For information about how to make such changes, see the Data Services 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) Note that the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions uses some global variables. (See “Global Variables” on page 340 for a list of variables.) Identical components from other Rapid Marts may use local variables. Because future releases of Rapid Marts will use global variables, SAP BusinessObjects recommends that you retain the version of the component that uses global variables.


Using the Rapid MartCustomizing the Rapid Mart 7

If you are implementing the Rapid Mart on Oracle 8i or Oracle 9i platforms, you can take advantage of pre-processing and post-processing performance tuning stored procedures described in “Fact Table Stored Procedures” on page 423 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 SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions 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 Rapid Mart for their use.This chapter discusses: • Service Notification Section• Service Order Section• Service Operation Section• Service Confirmation Section• Service Order Cost Section• Service Master Section• Dimensions with Incremental Loads• Rolling Totals Calculation• Optimization Techniques• Dealing with NULL values• Fact Table Stored Procedures• Fiscal Periods & Time Dim Load

Service Notification Section The notification section extracts data about service (or maintenance) notifications. The Rapid Mart calls the C_Notification_Section_SAP work flow to load tables from SAP solutions. First, the section loads the required dimension components with work flow WF_NotificationDims_SAP. 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

C_BusinessArea_SAP Dimensional component loading Business Area information from TGSB and TGSBT

BUSINESS_AREA

C_ClassificationHier_SAP Object Classification hierarchies for Equipment and Functional Locations

CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR


Technical ImplementationService Notification Section 8

C_CompanyCode_SAP Dimensional component loading Company Codes information from T001

COMPANY_CODE

C_ControllingArea_SAP Dimensional component loading Controlling Area information from TKA01

CONTROLLING_AREA

C_CostCenter_SAP Dimensional component loading Cost Center information from CSKS and CSKT

COST_CENTER

C_CostCenterHier_SAP Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS


C_DocumentCategory_SAP Combined Document Category Dimension

DOCUMENT_CATEGORY

C_DocumentType_SAP Combined Document Type Dimen-sion

DOCUMENT_TYPE & DOCUMENT_CATEGORY

C_Equipment_SAP Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy

EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR

C_FunctLocation_SAP Populate FUNCTIONAL_LOCATION master data dimension from IFLOT/ILOA and Functional Location Hierarchy


C_InternalOrder_SAP Load INTERNAL_ORDER dimen-sion

INTERNAL_ORDER

C_InternalOrderHier_SAP Dimensional component loading Internal Order Hierarchy information from CCSS-AUFNR and AUFK

INTERNAL_ORDER_HIER, INTERNAL_ORDER_HIER_HZ, INTERNAL_ORDER_HIER_VR, INTERNAL_ORDER_HIER_BAD

C_MaintenancePriority_SAP Load MAINTENANCE_PRIORITY dimension from T356, T356T (for service orders and notifications)


C_MalfunctionCatalog_SAP Load 3 pre-defined notification cata-log objects into MALFUNCTION_CAUSE MALFUNCTION_DAMAGE MALFUNCTION_OBJ_PART

MALFUNCTION_CAUSE, MALFUNCTION_DAMAGE, MALFUNCTION_OBJ_PART

C_MalfunctionEffect_SAP Load MALFUNCTION_EFFECT dimension from T357A_T

MALFUNCTION_EFFECT

C_Material_SAP Dimensional component loading consisting of a first and delta load for the materials table from MARA. Loads the sales product hierarchy table which is linked to the material

MATERIAL, PRODUCT_HIERARCHY



Technical ImplementationService Notification Section8

Next, the section executes workflow C_NotificationFact_SAP to load the NOTIFICATION_FACT table. This is followed by work flow C_MtbrMttrFact_SAP to load the MTBR_MTTR_FACT table.These two work flows use the $G_LOAD_TYPE variable to determine whether the job is running an initial load or incremental load.

C_MaterialByPlant_SAP Dimensional component loading plant-specific material information such as procurement type and pur-chasing group from MARC / MARA

MATERIAL_BY_PLANT

C_Notification_SAP Notification Dimension - Sourced from QMEL and QMIH in SAP.

NOTIFICATION

C_PlanningGroup_SAP Load descriptive attributes from T024I - Planner group into PLANNING_GROUP dimension

PLANNING_GROUP

C_Plant_SAP Dimensional component loading the plant table from T001W.

PLANT

C_PlantLocation_SAP Plant Location attributes from T499S - PLANT_LOCATION

PLANT_LOCATION

C_ServicePerson_SAP Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data

SERVICE_PERSON

C_TimeDim_SAP Dimensional component loading generated time periods with SAP fis-cal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are used

TIME_DIM

C_UnitOfMeasure_SAP Populates Units of Measure dimen-sion during first and delta loads from Table T006A in SAP

UNIT_OF_MEASURE

C_WorkCenter_SAP Load WORK_CENTER master data dimension

WORK_CENTER

C_WorkCenterHier_SAP Work Center Hierarchical relation-ship in Horizontal and Vertical for-mats from CRHH/CRHS; load WORK_CENTER_HIER, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_HZ




Technical ImplementationService Notification Section 8

Initial loadDuring the initial load, the section loads the NOTIFICATION_FACT table followed by the MTBR_MTTR_FACT.

NOTIFICATION_FACTAny existing data in NOTIFICATION_FACT is deleted before the initial load starts.For the NOTIFICATION_FACT table, the section extracts a snapshot of SAP solutions plant maintenance notifications. The source tables in SAP solutions are:• QMEL - Quality Notification• QMIH - Quality message - maintenance data excerpt• QMFE - Quality notification - items• TQ80 - Notification TypesTable TQ80 is used to restrict the data extracted to only Plant Maintenance Notifications by selecting only records where the Notification Category is “01” (Plant Maintenance):• TQ80.QMTYP = '01' Data extraction is further restricted by creation dates and change dates, with the Rapid Mart load job selecting only notifications created or modified within the date range defined by global variables $G_SDATE and $G_EDATE.The Rapid Mart load job also calculates:• Down Time - difference between Malfunction Start Date & Time and

Malfunction End Date & Time• Required Repair Time - difference between Required Start Date & Time

and Required End Date & Time• Completion Time - difference between the Notification Date & Time and

the Completion Date & TimeThese values are expressed in Days, Hours, and minutes.

MTBR_MTTR_FACTAny existing data in MTBR_MTTR_FACT is deleted before the initial load starts.For the MTBR_MTTR_FACT table, the section calculates • MTBR = Mean (or Average) Time Between Repairs (also called up time)• MTTR = Mean (or Average) Time To Repair (also called down time)


Technical ImplementationService Notification Section8

The NOTIFICATION_FACT table serves as the source table for these calculations. Thus, loading the NOTIFICATION_FACT table is a prerequisite for the MTBR / MTTR load.Notifications must meet the following criteria to be included in the MTBR / MTTR calculations:• Must have “complete” status in SAP solutions• Must not be marked for deletion• Must have a Malfunction Start Date and Malfunction End Date• Must have an assigned Functional Location or EquipmentData is first loaded to the MTBR_MTTR_STAGE table. In this table, the data is pivoted. The pivot segregates notifications for equipment from those for functional locations. The Equipment ID or Functional Location ID is stored in a new column OBJ_ID. Another new column OBJ_FLAG is set to 'EQ' for Equipment, or 'FL' for Functional Location. We also lookup the startup date of the equipment or functional location at this time.The data is ordered by OBJ_FLAG, OBJ_ID, and MALFNCTN_START_DATE and each row is assigned a sequential number (SEQ_NUM). This ensures the chronology of the notifications by malfunction date and either equipment or functional location.The next step is to read data from the MTBR_MTTR_STAGE table and use it to populate the final MTBR_MTTR_FACT table. Here, the chronological ordering of the stage table is crucial. We determine time between notifications by looking at the next or previous notification for an Object (equipment or functional location) based on the chronological order of the MTBR_MTT_STAGE table.• Malfunction End Date (Previous Notification) comes from the

notification for this Object with SEQ_NUM - 1.• Malfunction Start Date (Next Notification) comes from the notification

for this object with SEQ_NUM + 1.If there is no next or previous notification, • Malfunction End Date (Previous Notification) is the Startup Date of the

Object• Malfunction Start Date (Next Notification) is global variable

$G_LOAD_DATEThe final step is to calculate the Up Time and Down Time:• Up Time = Malfunction End Date Previous Notification - Malfunction Start

Date Current Notification• Down Time = Malfunction End Date Current Notification - Malfunction

Start Date Current Notification


Technical ImplementationService Order Section 8

Note: Equipment and Functional Location loads are prerequisites for the MTBR / MTTR load as we must determine the start up dates for the equipment or the functional location.

Incremental loadOnly the NOTIFICATION_FACT has an incremental load. We do a full (initial) load of MTBR_MTTR_FACT at all times.

NOTFICATION_FACTNo records in NOTIFICATION_FACT are deleted when the incremental load starts.The incremental load for Notifications selects records using the same criteria as the initial load. As in the initial load, notifications are restricted to those created or changed within the date range defined by global variables $G_SDATE and $G_EDATE. However, in the incremental load the range defined by these two variables is much smaller (typically one or two days). Whereas, an initial load typically loads several years worth of data. Thus an incremental load extracts far fewer records, and runs much faster.We then use the Table Comparison Transform to compare the extracted data with the data existing in the NOTIFICATION_FACT table. New records are added and existing records are updated with the newly extracted data.

MTBR_MTTR_FACTThe calculation of Up Time and Down Time runs across notifications that may or may not have been updated in the incremental load. For this reason it is not practical to do an incremental load for MTBR / MTTR. We do a full (initial) load of MTBR_MTTR_FACT.

Service Order SectionThe Service Order section extracts data about maintenance Service Orders. The Rapid Mart calls the C_ServiceOrder_Section_SAP work flow to load tables from SAP solutions.


Technical ImplementationService Order Section8
Dimension load
First, the section calls work flow WF_ServiceOrderDims_SAP to load the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses several work flow components to load dimension tables:



BUSINESS_AREA




COMPANY_CODE


CONTROLLING_AREA


COST_CENTER



C_Currency_SAP Dimensional component loading cur-rency abbreviations and texts from TCURT, TCURC

CURRENCY

C_Customer_SAP Dimensional component loading consisting of a first and delta load for the customer table from KNA1.

CUSTOMER


DOCUMENT_CATEGORY





C_FunctionalArea_SAP Dimensional component loading Functional Area information from TFKB and TFKBT

FUNCTIONAL_AREA

C_FunctionalAreaHier_SAP Functional Area Hierarchy from GLFUNCT-RFAREA







INTERNAL_ORDER



C_InternalOrderStatus_SAP Internal orders status reference dimension from TKO04


C_MaintenanceActivityType_SAP Maintenance Activity Type attributes from T353I/T353I_T. Populate MAINTENANCE_ACTIVITY_TYPE







MATERIAL_BY_PLANT


NOTIFICATION


PLANNING_GROUP


PLANT


PLANT_LOCATION

C_ProfitCenter_SAP Dimensional component loading Profit Center master data (Dimen-sion)

PROFIT_CENTER

C_ProfitCenterHier_SAP Dimensional component loading profit center hierarchy (EC-PCA Profit center hierarchy in SAP)


C_ProjectElement_SAP Dimensional component loading Project Element (WBS) master data

PROJECT_ELEMENT



Technical ImplementationService Order Section8

Fact table loadAfter loading the dimensions, the section calls work flow C_ServiceOrderFact_SAP to load the SERVICE_ORDER_FACT table. The Rapid Mart load job determines whether you are loading the Service Orders for the first time. If you are, the section executes the initial load work flow. If not, the section executes the incremental load work flow.

Initial LoadAny existing data in SERVICE_ORDER_FACT is deleted before the initial load starts. Service Orders are sourced from these tables in SAP solutions:• AFIH - Maintenance order header• AUFK - Order master data• AFKO - Order header data PP ordersRecords are restricted to those with Order Category = 30 • AUFK.AUTYP = 30

C_ProjectElementHier_SAP Dimensional component loading project element hierarchy informa-tion

PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ, PROJECT_ELEMENT_HIER_VR, PROJECT_ELEMENT_HIER_BAD


SERVICE_PERSON

C_SystemCondition_SAP System Condition descriptive attributes from T253M_T. Load SYSTEM_CONDITION dimension

SYSTEM_CONDITION


TIME_DIM


WORK_CENTER






This limits the selection to only Maintenance Orders. Data extraction is further restricted by creation dates and change dates, with the Rapid Mart load job selecting only service orders created or modified within the date range defined by global variables $G_SDATE and $G_EDATE. Service Orders marked for deletion are also excluded.Note: Creation and Change dates from the AUFK table (Order Master Data) are used for the Service Order load.The load calculates: • Time to Actually complete a service order

Actual End Date - Actual Start Date• Time to Basically complete a service order

Basic End Date - Basic Start Date• Time Forecast to complete a service order

Forecast End Date - Forecast Start Date• Time Scheduled to complete a service order

Scheduled End Date - Scheduled Start Date• Time to Actually release a service order

Actual Release Date - Actual Start Date• Time Scheduled to release a service order

Scheduled Release Date - Scheduled Start Date

Incremental LoadNo records in SERVICE_ORDER_FACT are deleted when the incremental load starts.The incremental load for Service Orders selects records using the same criteria as the initial load. As in the initial load, service orders are restricted to those created or changed within the date range defined by global variables $G_SDATE and $G_EDATE. However, in the incremental load the range defined by these two variables is much smaller (typically one or two days). Whereas, an initial load typically loads several years worth of data. Thus an incremental load extracts far fewer records, and runs much faster.We then use the Table Comparison Transform to compare the extracted data with the data existing in the SERVICE_ORDER_FACT table. New records are added and existing records are updated with the newly extracted data.


Technical ImplementationService Operation Section8
Service Operation Section
The operation section extracts data about operations required for Service Orders. The Rapid Mart calls the C_ServiceOperation_Section_SAP work flow to load tables from SAP solutions.

Dimension loadFirst, the section calls work flow WF_ServiceOperationsDims_SAP to load the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses several work flow components to load dimension tables:


C_Activity_SAP Dimensional component loading Activity information from CSLA and CSLT

ACTIVITY

C_ActivityHier_SAP Dimensional component loading Cost Activity Hierarchy information from CCSS-LSTAR and CSLA

ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD


BUSINESS_AREA

C_ChartofAccts_SAP Chart of Accts (T004 and T004T) in SAP

CHART_OF_ACCOUNTS




COMPANY_CODE

C_ControlKey_SAP Dimensional component loading control key information and descrip-tions from T430/T430T

CONTROL_KEY


CONTROLLING_AREA


COST_CENTER




Technical ImplementationService Operation Section 8

C_CostElement_SAP Dimensional component loading Cost Element information from CSKA and CSKU

COST_ELEMENT

C_CostElementHier_SAP Dimensional component loading Cost Element Hierarchy information from CCSS-KSTAR and CSK1

COST_ELEMENT_HIER, COST_ELEMENT_HIER_HZ, COST_ELEMENT_HIER_VR, COST_ELEMENT_HIER_BAD


CURRENCY


CUSTOMER


DOCUMENT_CATEGORY






FUNCTIONAL_AREA






INTERNAL_ORDER













MATERIAL_BY_PLANT


NOTIFICATION

C_ObjectClass_SAP Dimensional component loading Object Class information from DD07T

OBJECT_CLASS

C_ObjectType_SAP Dimensional component loading Object Type information from various modules -- This is a combined dimension.

OBJECT_TYPE

C_OperationSuitability_SAP Load OPERATION_SUTABILITY from T423T



PLANNING_GROUP


PLANT


PLANT_LOCATION


PROFIT_CENTER




PROJECT_ELEMENT




SYSTEM_CONDITION



Technical ImplementationService Operation Section 8

Fact table loadAfter loading the dimensions, the section calls work flow C_ServiceOperationFact_SAP to load the SERVICE_OPERATION_FACT table.The Rapid Mart load job determines whether you are loading the Service Operations for the first time. If you are, the section executes the initial load work flow. If not, the section executes the incremental load work flow.

Initial LoadAny existing data in SERVICE_OPERATION_FACT is deleted before the initial load starts. Service operations are sourced from these tables in SAP solutions:• AFIH - Maintenance order header• AUFK - Order master data• AFKO - Order header data PP orders• AFVC - Operation within an order• AFVV - DB structure of the quantities/dates/values in the operationRecords are restricted to those with Order Category = 30


TIME_DIM


UNIT_OF_MEASURE

C_Vendor_SAP Dimensional component loading vendor and supplier contact informa-tion from LFA1

VENDOR

C_VendorByCompany_SAP 1 - Extracts Vendor and associated financial information by company from LFA1 and LFB1.

VENDOR_BY_COMPANY


WORK_CENTER






• AUFK.AUTYP = 30This limits the selection to only Maintenance Orders. Data extraction is further restricted by creation dates and change dates, with the Rapid Mart load job selecting only service orders created or modified within the date range defined by global variables $G_SDATE and $G_EDATE. Service Orders marked for deletion are also excluded.Note: Creation and Change dates from the AUFK table (Order Master Data) are used for the Operations load. The AFVC and AFVV tables do not carry these dates. The load calculates: • Actual Execution Time for Operation

Actual End Date - Actual Start Date• Scheduled Execution Time for Operation

Scheduled End Date - Scheduled Start Date

Incremental LoadNo records in SERVICE_OPERATION_FACT are deleted when the incremental load starts.The incremental load for Service Operations selects records using the same criteria as the initial load. As in the initial load, service orders are restricted to those created or changed within the date range defined by global variables $G_SDATE and $G_EDATE. However, in the incremental load the range defined by these two variables is much smaller (typically one or two days). Whereas, an initial load typically loads several years worth of data. Thus an incremental load extracts far fewer records, and runs much faster.We then use the Table Comparison Transform to compare the extracted data with the data existing in the SERVICE_OPERATION_FACT table. New records are added and existing records are updated with the newly extracted data.


Technical ImplementationService Confirmation Section 8

Service Confirmation SectionThe confirmation section extracts data about confirmations assigned to Service Orders. The Rapid Mart calls the C_ServiceConfirmation_Section_SAP work flow to load tables from SAP solutions.

Dimension loadFirst, the section calls work flow WF_ServiceConfirmationDims_SAP to load the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses several work flow components to load dimension tables:


C_Activity_SAP Dimensional component loading Activity information from CSLA and CSLT

ACTIVITY

C_ActivityHier_SAP Dimensional component loading Cost Activity Hierarchy information from CCSS-LSTAR and CSLA

ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD


BUSINESS_AREA

C_Capacity_SAP Capacity Master from KAKO/KAKT - CAPACITY dimension

CAPACITY




COMPANY_CODE


CONTROLLING_AREA


COST_CENTER




CURRENCY


Technical ImplementationService Confirmation Section8


CUSTOMER


DOCUMENT_CATEGORY






FUNCTIONAL_AREA






INTERNAL_ORDER



C_InternalOrderStatus_SAP Internal orders status reference dimension from TKO04









MATERIAL_BY_PLANT



Technical ImplementationService Confirmation Section 8


NOTIFICATION

C_OperationSuitability_SAP Load OPERATION_SUTABILITY from T423T



PLANNING_GROUP


PLANT


PLANT_LOCATION


PROFIT_CENTER




PROJECT_ELEMENT




SERVICE_PERSON


SYSTEM_CONDITION


TIME_DIM


UNIT_OF_MEASURE



Technical ImplementationService Confirmation Section8

Fact table loadAfter loading the dimensions, the section calls work flow C_ServiceConfirmationFact_SAP to load the SERVICE_CONFIRMATION_FACT table.The Rapid Mart load job determines whether you are loading the Service Confirmations for the first time. If you are, the section executes the initial load work flow. If not, the section executes the incremental load work flow.

Initial LoadAny existing data in SERVICE_CONFIRMATION_FACT is deleted before the initial load starts. Service confirmations are sourced from these tables in SAP solutions:• AFIH - Maintenance order header• AUFK - Order master data• AFRU - Order completion confirmationsRecords are restricted to those with Order Category = 30 • AUFK.AUTYP = 30This limits the selection to only Maintenance Orders. Data extraction is further restricted by creation dates and change dates, with the Rapid Mart load job selecting only service order confirmations created or modified within the date range defined by global variables $G_SDATE and $G_EDATE. Note: Creation and Change dates from the AFRU table (Order completion confirmations) are used for the Confirmations load. The load calculates: • Execution Time for Confirmation

Execution End Date - Execution Start Date• Forecast Completion Time for Confirmation


WORK_CENTER





Technical ImplementationService Order Cost Section 8

Forecast End Date - Execution Start Date

Incremental LoadNo records in SERVICE_CONFIRMATION_FACT are deleted when the incremental load starts.The incremental load for Service Confirmations selects records using the same criteria as the initial load. As in the initial load, service confirmations are restricted to those created or changed within the date range defined by global variables $G_SDATE and $G_EDATE. However, in the incremental load the range defined by these two variables is much smaller (typically one or two days). Whereas, an initial load typically loads several years worth of data. Thus an incremental load extracts far fewer records, and runs much faster.We then use the Table Comparison Transform to compare the extracted data with the data existing in the SERVICE_CONFIRMATION_FACT table. New records are added and existing records are updated with the newly extracted data.

Service Order Cost SectionThe Service Order Cost section extracts data about costs of Service Orders. The Rapid Mart calls the C_ServiceOrderCost_Section_SAP work flow to load tables from SAP solutions.

Dimension loadFirst, the section calls work flow WF_ServiceOrderCostDims_SAP to load the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses several work flow components to load dimension tables.


C_BusinessActivity_SAP FK-SL Activity attributes from T022/T022T. Load BUSINESS_ACTIVITY dimension

BUSINESS_ACTIVITY


BUSINESS_AREA




COMPANY_CODE


Technical ImplementationService Order Cost Section8


CONTROLLING_AREA


COST_CENTER




CURRENCY


DOCUMENT_CATEGORY





C_FinRecordCategory_SAP Descriptive attributes for Accounting Summary table Value Category from TPIR1T. Load FINANCIAL_RECORD_CATEGORY dimension


C_FinRecordType_SAP Loads Special Ledger Record Types dimension (Domain RRCTY) from table DD07T and Cost/Plant Mainte-nance value types from CO_WRTTP domain of DD07T table - FINANCIAL_RECORD_


C_FiscalPeriod_SAP Dimensional component loading Fis-cal Year / Fiscal Period data

FISC_PERIOD, FISC_PERIOD_STAGE


FUNCTIONAL_AREA







Technical ImplementationService Order Cost Section 8


INTERNAL_ORDER










MATERIAL_BY_PLANT


PLANT


PLANT_LOCATION


PROFIT_CENTER




PROJECT_ELEMENT




SYSTEM_CONDITION

C_VarianceCategory_SAP Financial Variance Category descrip-tive attributes (ABKAT domain from DD07T). Load VARIANCE_CATEGORY dimension

VARIANCE_CATEGORY



Technical ImplementationService Order Cost Section8

Fact table loadAfter loading the dimensions, the work flow C_ServiceCostSumFact_SAP determines whether you are loading the target tables (SERVICE_COST_SUMMARY_FACT_VR, SERVICE_COST_SUMMARY_STAGE_VR, and SERVICE_COST_SUMMARY_FACT_HZ) for the first time, or if this an incremental (delta) load by querying the $G_LOAD_TYPE global variable. The range of years to load is determined by global variables $G_SDATE and $G_EDATE. The years stored in these variables are used to determine the first and last fiscal years respectively to be loaded. These variables are used in both first and incremental loads.If $G_LOAD_TYPE = “FIRST”, this is a first or initial load. The target tables are truncated (all data in them is deleted). If $G_LOAD_TYPE = “DELTA”, this an incremental or delta load. Table partitions for the range of fiscal years ($G_SDATE and $G_EDATE) are dropped and re-added to the target tables. This effectively deletes all data from the tables for the range of fiscal years. See Table Partitions later in this chapter for more details.Then common logic for both initial and incremental loads takes over:• Service Cost data is extracted from table PMCO (Cost structure of

maintenance order). The data extracted is restricted to the range of years specified by variables $G_SDATE and $G_EDATE. The output is loaded to SERVICE_COST_SUMMARY_FACT_HZ.

• The Pivot Transform converts SERVICE_COST_SUMMARY_FACT_HZ data into vertical format. This is loaded to SERVICE_COST_SUMMARY_STAGE_VR table.

A final set of transforms computes the “rolling 16 periods totals” on SERVICE_COST_SUMMARY_STAGE_VR. Output is loaded to SERVICE_COST_SUMMARY_FACT_VR. See Rolling Totals Calculation later in this chapter for more details.


WORK_CENTER





Technical ImplementationService Master Section 8

Service Master SectionThe Service Master section extracts data about the Characteristics and Classification attributes associated with technical objects (Equipment and Functional Location). The Rapid Mart calls the C_ServiceMaster_Section_SAP work flow to load tables from SAP solutions.

Dimension loadFirst, the section calls work flow WF_ServiceMasterDims_SAP to load the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses several work flow components to load dimension tables.



BUSINESS_AREA




COMPANY_CODE


CONTROLLING_AREA


COST_CENTER








Technical ImplementationService Master Section8

BackgroundThe Service Master section loads two fact tables, one for each type of technical object:• EQUIPMENT_CHAR_FACT - Equipment Characteristics Fact

• Fact table work flow: C_EquipmentCharactFact_SAP• Prerequisite dimension loads: Equipment and Material

• FUNCTIONAL_LOCATION_CHAR_FACT - Functional Location Characteristics Fact• Fact table work flow: C_FunctlLocationCharactFact_SAP




MATERIAL_BY_PLANT


PLANNING_GROUP


PLANT


PLANT_LOCATION


SERVICE_PERSON


TIME_DIM


UNIT_OF_MEASURE

C_Vendor_SAP Dimensional component loading vendor and supplier contact informa-tion from LFA1

VENDOR

C_VendorByCompany_SAP 1 - Extracts Vendor and associated financial information by company from LFA1 and LFB1.

VENDOR_BY_COMPANY



Technical ImplementationService Master Section 8

• Prerequisite dimension loads: Functional LocationEach of the two fact table work flows starts by loading the prerequisite dimensions listed above.

Characteristics Stage TableThen, each of the two fact table work flows loads the CHARACTERISTICS_STAGE table. CHARACTERISTICS_STAGE is sourced from these SAP solutions tables:• AUSP - Characteristic Values• CABN - Characteristics• TCLA - Class TypesThe load selects only the characteristics associated with either Equipment or Functional Locations by using two global variables. The variables determine the value for column TCLA.OBTAB (Object table name) used for either Equipment or Functional Location.

Note: If you use different values for TCLA.OTAB in your SAP solutions system you should change the default values in the Job Initialization script in Data Services.Only an initial load is possible for CHARACTERISTICS_STAGE.

Fact Table Load

Equipment CharacteristicsInitial LoadAny records in EQUIPMENT_CHAR_FACT are deleted at the start of this load. The load joins the EQUIPMENT table with the CHARACTERISTICS_STAGE table. Only records for equipment are select by using the $G_TABLE_EQUIPMENT global variable described above. The actual join is:

CHARACTERISTIC_STAGE.OBJ_TABLE_NAME =

Global Variable Default TCLA.OTAB Value

Description

$G_TABLE_EQUIPMENT EQUI Defines value for Equipment Characteristics

$G_TABLE_FUNCTL_LOCATN IFLOT Defines value for Functional Location Characteristics


Technical ImplementationService Master Section8

$G_TABLE_EQUIPMENT andCHARACTERISTIC_STAGE.OBJ_ID = EQUIPMENT.EQUIPMNT_ID

The Object ID (OBJ_ID) will contain the equipment or functional location ID, depending on the value Object Table (OBJ_TABLE_NAME).

Incremental LoadThe incremental load does not delete records from the EQUIPMENT_CHAR_FACT. Instead, it uses the Table Comparison transform to update or add records to EQUIPMENT_CHAR_FACT.The load determines which records are new or changed by checking the LOAD_DATE in the EQUIPMENT table. The actual join is:

EQUIPMENT.LOAD_DATE = $G_LOAD_DATE

Characteristics for any equipment refreshed in the current load job will be selected.

Functional Location CharacteristicsInitial LoadAny records in FUNCTIONAL_LOCATION_CHAR_FACT are deleted at the start of this load. The load joins the FUNTIONAL_LOCATION table with the CHARACTERISTICS_STAGE table. Only records for functional locations are select by using the $G_TABLE_FUNCTL_LOCATN global variable described above. The actual join is:

CHARACTERISTIC_STAGE.OBJ_TABLE_NAME = $G_TABLE_FUNCTL_LOCATN andCHARACTERISTIC_STAGE.OBJ_ID = FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID

The Object ID (OBJ_ID) will contain the equipment or functional location ID, depending on the value Object Table (OBJ_TABLE_NAME).

Incremental LoadThe incremental load does not delete records from the FUNCTIONAL_LOCATION_CHAR_FACT. Instead, it uses the Table Comparison transform to update or add records to FUNCTIONAL_LOCATION_CHAR_FACT.The load determines which records are new or changed by checking the LOAD_DATE in the FUNCTIONAL_LOCATION table. The actual join is:

FUNCTIONAL_LOCATION.LOAD_DATE = $G_LOAD_DATE


Technical ImplementationDimensions with Incremental Loads 8

Characteristics for any functional Location refreshed in the current load job will be selected.

Dimensions with Incremental LoadsMost dimensions are small enough that they can be reloaded in full during each job run. However, there are two dimensions, unique to the Plant Maintenance Rapid Mart, that have associated incremental loads.

EquipmentThe incremental load for EQUIPMENT table uses a text file stored on the SAP solutions server. The file name is EQUIPMENT.dat. It contains a single data field - the Equipment ID.The incremental load relies on the date range defined by global variables $G_SDATE and $G_EDATE. In an incremental load, this date range is typically very small (one or two days). In an initial load, several years is more typical. Thus, an incremental load will run much faster.

Incremental Load Steps1. Delete any data in the EQUIPMENT.dat table2. Read SAP solutions table EQUI, select Equipment ID’s (EQUI.EQUNR)

for all equipment created or changed in the date range defined by global variables $G_SDATE and $G_EDATE. Add the Equipment ID’s to table EQUIPMENT.dat

3. Read SAP solutions table EQUZ, select Equipment ID’s (EQUI.EQUNR) for all equipment created or changed in the date range defined by global variables $G_SDATE and $G_EDATE. Add the Equipment ID’s to table EQUIPMENT.dat

4. The result is that EQUIPMENT.dat contains a list of Equipment ID’s that have changed in either EQUI or EQUZ table. Note: Since an equipment may have changes in both EQUI and EQUZ tables it is possible for an Equipment ID to be listed twice in EQUIPMENT.dat.

5. Select unique Equipment ID’s (to eliminate duplicates) from EQUIPMENT.dat and join this to EQUI and EQUZ to extract required equipment attributes.

6. Use Table Comparison transform to update or add records in the EQUIPMENT table on the target database.


Technical ImplementationRolling Totals Calculation8
Functional Location
The incremental load for FUNCTIONAL_LOCATION table relies on the date range defined by global variables $G_SDATE and $G_EDATE. In an incremental load, this date range is typically very small (one or two days). In an initial load, several years is more typical. Thus, an incremental load will run much faster.

Incremental Load Steps1. Read SAP solutions tables IFLOT and ILOA, select required attributes for

functional locations created or changed in the date range defined by global variables $G_SDATE and $G_EDATE. Creation or Change dates from IFLOT table are compared to the global variables.

2. Use Table Comparison transform to update or add records in the FUNCTIONAL_LOCATION table on the target database.

Rolling Totals CalculationVertical summary tables in several Rapid Marts use Rolling 16 Fiscal Period Totals. These totals present the last 16 months of Period-To-Date values summed, for each set of primary keys in the table. The vertical summary tables with rolling totals are:

To implement Rolling Totals we use a custom function• RM_RollingSummary_Calculation.

Rapid Mart Vertical Summary Table

Accts. Payable VENDOR_SUMMARY_FACT_VRAccts. Receivable CUSTOMER_SUMMARY_FACT_VRCost COST_SUMMARY_FACT_VRGeneral Ledger COST_OF_SALES_SUMMARY_FACT_VRGeneral Ledger GL_SUMMARY_FACT_VRGeneral Ledger LEDGER_SUMMARY_FACT_VRGeneral Ledger & Cost

PROFIT_CENTER_SUMMARY_FACT_VR

Plant Maint. SERVICE_COST_SUMMARY_FACT_VRProject Systems PROJECT_COST_SUMMARY_FACT_VR


Technical ImplementationRolling Totals Calculation 8

The function keeps track of the Period-to-Date values from the previous row processed by Data Services. This is key for rolling totals.Rolling totals and the use of the function need to be carefully set up in Data Services as shown in the example below.Vertical Summary data is first populated to a “staging” table that has all values for the vertical summary except the PTD (Period-to-Date) and Rolling Totals values. Then, rolling totals are computed, and the results moved from the staging table to the vertical summary table. A rolling totals data flow typically looks like this...

Details for each query transform follow...



PTDBALQuery - 1. Calculate PTD Values:

“PTD” values are calculated by subtracting Credits from Debits.



PTDBALQuery - 2. Concatenate Summary Key:

The “Summary Key” is the concatenated Primary Key in one column. If the Fiscal Year and Fiscal Period are a part of the Primary Key, they are excluded from the Summary Key.



Ordering Query:

The Ordering Query will sort the data by the Summary Key, Fiscal Year, and Fiscal Period. This is important for Rolling Totals as the function will • Reset totals to zero when the Summary Key changes.• Keep tract of totals for the past 16 rows processed.None of this would work correctly without the proper sorting of the data.



Calc Rolling Totals Query:

This query calls the RM_RollingSummary_Calculation function. The call for AMT_PER_ROLLING_TRX is shown above. The call for AMT_PER_ROLLING_LOC is:

RM_RollingSummary_Calculation(SUMMARY_KEY, AMT_PTD_LOC,$c1, $c2, $c3, $c4, $c5, $c6, $c7, $c8, $c9, $c10, $c11, $c12, $c13, $c14, $c15, $c16, $rkey )

Rolling Summary Calculation uses the computed Summary Key and Period-To-Date total as input parameters. The function is called twice, once for each of the two Rolling Totals calculated. Each of the calls uses a set of 16 local variables • $t1 through $t16 for the AMT_PER_ROLLING_TRX call• $c1 through $c16 for the AMT_PER_ROLLING_LOC call



Should there be a third rolling total to calculate, we would use a third set of 16 variables.A final local variable $rkey is the value of the Summary Key on the previous row processed by Data Services. It is used in both calls.It is important to setup and initialize these local variables up correctly. They are defined as local variables at the Work Flow Level in Data Services:



They are defined as Parameters at the Data Flow level:



The “Call” values for the parameters are initialized at the Work Flow level as shown below.

The value of $RKEY is initialized to value that will never appear in the Summary Key. The remaining groups of 16 variables are all initialized to zero.



An example of the output generated by this type of data flow and the Rolling Totals Function are shown below.


Technical ImplementationOptimization Techniques8
Optimization Techniques
Within Data Services there are several optimization techniques available. Some of these are used extensively in the Plant Maintenance Rapid Mart. They are described belowHowever, every installation is unique. Other techiques may be applicable to your particular Rapid Mart installation. This depends on many variables such as data load volume, server configuration, network transfer rates, etc. Refer to Data Services™ technical manuals for more information on the varous tuning and optimizing techniques.

Table PartitionsSummary tables in SAP solutions present a particular challenge in terms of a incremental (or delta) load. They often do not carry a “date of last change” field in the source table. In most cases source table granularity is at the Fiscal Period / Fiscal Year level.Data Services performs incremental loads on these tables by fiscal year.Data for a range of fiscal years is deleted from the target tables before each incremental load. The range is determined by the fiscal years associated with the global variables $G_SDATE and $G_EDATE.Then the same range of years is re-loaded from the SAP solutions source tables.Deleting by fiscal year without partitions is resource intensive, and can take a very long time. To facilitate these deletions we have partitioned the target tables by fiscal year. Partitions based on fiscal year can be dropped and re-added to the table very quickly. Thus the delete of a range of fiscal years is much faster. with partitionsEach of the databases supported (Oracle, SQL-Server, DB2) handles partition logic differently. Separate cases for each have been coded into the Data Services jobs. Use of partitions is transparent to the end-user.

Note: We do not use partition logic for Teradata. Terdata optimizes the delete function in SQL so that partitions are not needed.Note: In a DB2 target environment, proper database tuning is required to handle detaching partitions properly. If not tuned, the database returns control to the Data Services job before the partition is physically detached. This will cause the job to fail.To prevent this, we query the DB2 metadata table:


Technical ImplementationOptimization Techniques 8

• SYSIBM.SYSDATAPARTITIONSin a “while” loop, upto 100 times, with a 10 second sleep in between each query. When this table shows that the partitions are truly detached, the job proceeds. However, in a poorly tuned system even this may not be enough time. Proper tuning is essential.

Tables and Rapid Marts that use partition logic are:

Rapid Mart Subject Area Tables

Accts. Payable VENDOR_SUMMARY_FACT_HZ, VENDOR_SUMMARY_FACT_VR, VENDOR_SUMMARY_STAGE_VR

Accts. Receivable CUSTOMER_SUMMARY_FACT_HZ, CUSTOMER_SUMMARY_FACT_VR, CUSTOMER_SUMMARY_STAGE_VR

Cost COST_SUMMARY_FACT_HZ, COST_SUMMARY_FACT_VR, COST_SUMMARY_STAGE_VR

General Ledger COST_OF_SALES_SUMMARY_FACT_HZ, COST_OF_SALES_SUMMARY_FACT_VR, COST_OF_SALES_SUMMARY_STAGE_VR

General Ledger GL_SUMMARY_FACT_HZ, GL_SUMMARY_FACT_VR, GL_SUMMARY_STAGE_VR

General Ledger LEDGER_SUMMARY_FACT_HZ, LEDGER_SUMMARY_FACT_VR, LEDGER_SUMMARY_STAGE_VR

General Ledger PROFIT_CENTER_SUMMARY_FACT_HZ, PROFIT_CENTER_SUMMARY_FACT_VR, PROFIT_CENTER_SUMMARY_STAGE_VR

Plant Maint. SERVICE_COST_SUMMARY_FACT_HZ, SERVICE_COST_SUMMARY_FACT_VR, SERVICE_COST_SUMMARY_STAGE_VR

Projects PROJECT_COST_SUMMARY_FACT_HZ, PROJECT_COST_SUMMARY_FACT_VR, PROJECT_COST_SUMMARY_STAGE_VR


Data Transfer Transform
Within Data Services we make extensive use of the “Data Transfer” transform to optimize operations. Data Transfer insures the operations are “pushed down”. That is, performed by the underlying database instead of Data Services.Data Transfer creates a temporary database table that is used as a staging table for the operation, thus insuring the “push down”. The temporary table is deleted once the data flow that uses it is complete.

Note: If your target database is DB2, you must provide the DB2 bulk loader log-in name and password in the Target Datastore.If you don't your job will finish with the red "X" across the traffic light indicating an error. But, no error log displayed in Data Services. To see the error, go to the log directory on the Data Services job server, you'll find and error log file indicating a warning about the DB2 bulkloader log-in and password.Providing the missing bulkloader log-in and password prevents this from happening.

Here is an example of how to use a Data Transfer::

Key TransformsCircled in RED.



In this example the 3 circled transforms are the key to this optimization.Within the Data Transfer:• “Enable Transfer” is checked• “Transfer Type” is Automatic• “Join Rank” is 0 Within the Ordering Query: • “Order by” all non-pivot columns used in the Reverse-Pivot• Make sure the columns in the “order by” clause appear in the same

sequence as the non-pivot columns in the Reverse-Pivot.Within the Reverse-Pivot:• “Input Data is Grouped” is checked• Make sure the non-pivot columns appear in the same sequence as the

“order by” clause of the Ordering Query

Hierarchy OptimizationsWe also use optimizations for Hierarchy Flattening Transforms. Hierarchy Flattening Transforms are set to run as “Separate Process” (in the properties window). The data flow that calls the Hierarchy Flattening Transform is set to 2 degrees of parallelism.This degree of parallelism is tied to number of CPUs on your server, and can require manual tuning. Refer to Data Services technical manuals for more details on Distributed Data Flows.Hierarchy flattening transforms are resource intensive. To prevent overtaxing system resources on the Data Services job server you can split the Vertical and Horizontal hierarchy flattening into two separate workflows. The diagrams below show an example:



Before Split (Single Data Flow):

After Split 1 of 2 Data Flows (Horizontal):



After Split 2 of 2 Data Flows (Vertical):

The 2 Split Data Flows in Context.


Technical ImplementationDealing with NULL values8
Dealing with NULL values
As the first step in data cleansing, the SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions allows replacing NULL values found in the source system with configurable default ‘not-null’ values.The Rapid Mart provides three categories of default values to treat NULLs:• For columns that behave as a foreign key the 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.


Technical ImplementationFact Table Stored Procedures 8

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, as delivered with the Rapid Mart, are only placeholders. The Oracle version of the placeholder procedures is shown below:

CREATE OR REPLACE PROCEDURE postprocessing_fact_table(pLoadType IN VARCHAR2, pDropCreateIndex IN VARCHAR2, pFactTable IN VARCHAR2, pMView_Failures OUT BINARY_INTEGER) IS

BEGIN NULL;END postprocessing_fact_table;

CREATE OR REPLACE PROCEDURE preprocessing_fact_table(pLoadType IN VARCHAR2, pDropCreateIndex IN VARCHAR2, pFactTable IN VARCHAR2) IS

BEGIN 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 (for Oracle only):• Create_Sample_Maintenance_SP.sql

The sample PREPROCESSING_FACT_TABLE procedure will drop all indexes and all materialized view logs enabled for the fact table. This should reduce load time for the fact table in Data Services.The POSTPROCESSING_FACT_TABLE procedure will recreate logs and indexes. See the Rapid Mart Deployment Guide for details.


Technical ImplementationFiscal Periods & Time Dim Load8
Fiscal Periods & Time Dim Load
These two dimensions use a text file named dates.dat to define the range of dates you load. The file must be located in the Working Directory you defined in your R/3 Data Store


Technical ImplementationFiscal Periods & Time Dim Load 8

By default, the file contains all dates from 01-Jan-1990 through 31-Dec.-2012 in “YYYYMMDD” format

You can easily change the contents of dates.dat to include a different date range that covers your specific needs.


Technical ImplementationFiscal Periods & Time Dim Load8


Documentation References

chapter

Documentation ReferencesData Services Documentation References9

The SAP BusinessObjects Plant Maintenance Rapid Mart XI 3.2 for SAP solutions User Guide requires familiarity with SAP BusinessObjects Enterprise and Data Services applications. Documentation for both applications can be found in http://help.sap.com.

Data Services Documentation ReferencesFrom the SAP help portal, Data Services documentation is accessed via SAP BusinessObjects -> All Products -> Data Services -> SAP BusinessObjects XI 3.2 <or higher version> path.Installing Data Services:

• Data Services Installation Guide• Data Services Getting Started Guide

Configuring Data Services for SAP solutions and security considerations:• Data Services Supplement for SAP

Extending/customizing Rapid Marts ETL:• Data Services Tutorial• Data Services Designer Guide• Data Services Reference Guide• Data Services Advanced Development Guide• Data Services Performance Optimization Guide

BusinessObjects Enterprise Documentation References

From the SAP help portal, BusinessObjects Enterprise documentation is accessed via SAP BusinessObjects -> All Products -> BusinessObjects Enterprise -> BusinessObjects XI Release 2 <or higher version> path.Installing BusinessObjects Enterprise:

• Installation GuideConfiguring BusinessObjects Enterprise and security considerations:

• Administration Guide• Deployment and Configuration Guide


Documentation ReferencesBusinessObjects Enterprise Documentation References 9

• Administrator’s Reference Guide• Recommended Settings Guide• Import Wizard Guide• InfoView User Guide

Extending/customizing Rapid Marts Reporting Content:• Designer’s Guide (BusinessObjects -> All Products -> Universe

Designer path)• Building queries with Web Intelligence (BusinessObjects -> All

Products -> Web Intelligence path)• Using Functions, Formulas and Calculations in Web Intelligence

(BusinessObjects -> All Products -> Web Intelligence path)


Documentation ReferencesBusinessObjects Enterprise Documentation References9


Rapid Mart Data Schema

appendix

Appendix ATable Summary

Rapid Mart Data Schema

This appendix provides detailed information about the tables and views in the SAP BusinessObjects Plant MaintenanceRapid Mart XI 3.2, version for SAP solutions. This information applies to an Oracle target datastore.

Auxiliary Tables

● AW_DIMENSION_SOURCE

● AW_FIRST_RUN_DATE

● AW_JOBEXECUTION

● AW_LOOKUP_INDEX

Dimension Tables

● ACTIVITY

● ACTIVITY_HIER

● ACTIVITY_HIER_HZ

● ACTIVITY_HIER_VR

● BUSINESS_ACTIVITY

● BUSINESS_AREA

● CAPACITY

● CHART_OF_ACCOUNTS

● CLASSIFICATION_HIER

● CLASSIFICATION_HIER_HZ

● CLASSIFICATION_HIER_VR

● COMPANY_CODE

● CONTROL_KEY

● CONTROLLING_AREA

● COST_CENTER

● COST_CENTER_HIER

● COST_CENTER_HIER_HZ

● COST_CENTER_HIER_VR

● COST_ELEMENT

● COST_ELEMENT_HIER

● COST_ELEMENT_HIER_HZ

● COST_ELEMENT_HIER_VR

● CURRENCY

● CUSTOMER

● DOCUMENT_CATEGORY

● DOCUMENT_TYPE

● EQUIPMENT

● EQUIPMENT_HIER

● EQUIPMENT_HIER_HZ

1Rapid Mart Data Schema

Appendix ATable Summary● EQUIPMENT_HIER_VR

● FINANCIAL_RECORD_CATEGORY

● FINANCIAL_RECORD_TYPE

● FISC_PERIOD

● FUNCTIONAL_AREA

● FUNCTIONAL_AREA_HIER

● FUNCTIONAL_AREA_HIER_HZ

● FUNCTIONAL_AREA_HIER_VR

● FUNCTIONAL_LOCATION

● FUNCTIONAL_LOCATION_HIER

● FUNCTIONAL_LOCATION_HIER_HZ

● FUNCTIONAL_LOCATION_HIER_VR

● INTERNAL_ORDER

● INTERNAL_ORDER_HIER

● INTERNAL_ORDER_HIER_HZ

● INTERNAL_ORDER_HIER_VR

● INTERNAL_ORDER_STATUS

● MAINTENANCE_ACTIVITY_TYPE

● MAINTENANCE_PRIORITY

● MALFUNCTION_CAUSE

● MALFUNCTION_DAMAGE

● MALFUNCTION_EFFECT

● MALFUNCTION_OBJ_PART

● MATERIAL

● MATERIAL_BY_PLANT

● NOTIFICATION

● OBJECT_CLASS

● OBJECT_TYPE

● OPERATION_SUITABILITY

● PLANNING_GROUP

● PLANT

● PLANT_LOCATION

● PRODUCT_HIERARCHY

● PROFIT_CENTER

● PROFIT_CENTER_HIER

● PROFIT_CENTER_HIER_HZ

● PROFIT_CENTER_HIER_VR

● PROJECT_ELEMENT

● PROJECT_ELEMENT_HIER

● PROJECT_ELEMENT_HIER_HZ

● PROJECT_ELEMENT_HIER_VR

● SERVICE_PERSON

● SYSTEM_CONDITION

● TIME_DIM

● TIME_DIM_WEEKLY


Appendix ATable Summary● UNIT_OF_MEASURE

● VARIANCE_CATEGORY

● VENDOR

● VENDOR_BY_COMPANY

● WORK_CENTER

● WORK_CENTER_HIER

● WORK_CENTER_HIER_HZ

● WORK_CENTER_HIER_VR

Fact Tables

● EQUIPMENT_CHAR_FACT

● FUNCTIONAL_LOCATION_CHAR_FACT

● MTBR_MTTR_FACT

● NOTIFICATION_FACT

● SERVICE_CONFIRMATION_FACT

● SERVICE_COST_SUMMARY_FACT_HZ

● SERVICE_COST_SUMMARY_FACT_VR

● SERVICE_OPERATION_FACT

● SERVICE_ORDER_FACT

Staging Tables

● CHARACTERISTIC_STAGE

● FISC_PERIOD_STAGE

● MTBR_MTTR_STAGE

● SERVICE_COST_SUMMARY_STAGE_VR

Validation Tables

● ACTIVITY_HIER_BAD

● COST_CENTER_HIER_BAD

● COST_ELEMENT_HIER_BAD

● FUNCTIONAL_AREA_HIER_BAD

● INTERNAL_ORDER_HIER_BAD

● PROFIT_CENTER_HIER_BAD

● PROJECT_ELEMENT_HIER_BAD

● WORK_CENTER_HIER_BAD


AppendixTable Column Details A

ACTIVITY

Activity Master (CSLA, CSLT)

# Column Name Key Column Desc ColumnDatatype

DtypeLength Precision Scale Is

Nullable

1 ACTIVITY_DESCR CSLT-LTEXT-Description NVARCSTR 40 0 0 yes

2 ACTIVITY_FULL_NAME Activity ID and Description NVARCSTR 120 0 0 yes

3 ACTIVITY_ID PK CSLA-LSTAR-Activity type NVARCSTR 6 0 0 no

4 ACTIVITY_NAME CSLT-KTEXT-Name NVARCSTR 20 0 0 yes

5 ACTIVITY_TYPE_CATEG_CODE CSLA-LATYPE-Activity type category NVARCSTR 1 0 0 yes

6 ALLOCTN_COST_ELEM_ID CSLA-VKSTA-Allocation cost element NVARCSTR 10 0 0 yes

7 CREATED_BY CSLA-USNAM-Created by NVARCSTR 12 0 0 yes

8 CREATE_DATE CSLA-ERSDA-Created on DATETIME 24 0 9 yes

9 CTRL_AREA_ID PK CSLA-KOKRS-Controlling area NVARCSTR 4 0 0 no

10 LOAD_DATE Date and time when the record was loaded intoRapid Mart DATETIME 24 0 9 yes

11 LOAD_TIME Time when the record was loaded into theRapidMart (string format HH24:MI:SS) NVARCSTR 8 0 0 yes

12 OUTPUT_FACTOR CSLA-AUSFK-Output factor DECIMAL 48 5 2 yes

13 UOM_ID CSLA-LEINH-Activity unit NVARCSTR 3 0 0 yes

14 UOM_ID_OUTPUT CSLA-AUSEH-Output unit NVARCSTR 3 0 0 yes

15 VALID_FROM_DATE CSLA-DATAB-Date valid from DATETIME 24 0 9 yes



16 VALID_TO_DATE CSLA-DATBI-Valid to date DATETIME 24 0 9 yes

ACTIVITY_HIER

Activity Hierarchy information - CCSS-LSTAR -- Note Does NOT Have a Primary Key due to duplication possible in SAP



Nullable

1 CHILD_DESCR CCSS-LSTAR-Activity Hierarchy Child IDDescription NVARCSTR 64 0 0 yes

2 CHILD_ID PK CCSS-LSTAR-Child Activity ID NVARCSTR 12 0 0 no

3 CTRL_AREA_ID PK CCSS-LSTAR-Controling Area NVARCSTR 4 0 0 no

4 LEAF_FLAG PK CCSS-LSTAR-Indicates if the Child ID doesn'thave any subordinate leaves NVARCSTR 1 0 0 no



7 PARENT_DESCR CCSS-LSTAR-Activity Hierarchy Parent IDDescription NVARCSTR 64 0 0 yes

8 PARENT_ID PK CCSS-LSTAR-Parent Activity ID NVARCSTR 12 0 0 no

9 ROOT_FLAG PK CCSS-LSTAR-Indicates if the Parent ID is aroot of an activity group hierarchy NVARCSTR 1 0 0 no



ACTIVITY_HIER_BAD

CCSS-LSTAR Activity Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR CCSS-LSTAR-Activity Hierarchy Child IDDescription NVARCSTR 64 0 0 yes

2 CHILD_ID PK CCSS-LSTAR-Child Activity ID NVARCSTR 12 0 0 no


4 ETL_ERROR_ACTN Data Integrator Action on Error NVARCSTR 1 0 0 yes

5 ETL_ERROR_COLUMN Data Integrator Error message NVARCSTR 500 0 0 yes

6 LEAF_FLAG PK CCSS-LSTAR-Indicates if the Child ID doesn'thave any subordinate leaves NVARCSTR 1 0 0 no



9 PARENT_DESCR CCSS-LSTAR-Activity Hierarchy Parent IDDescription NVARCSTR 64 0 0 yes

10 PARENT_ID PK CCSS-LSTAR-Parent Activity ID NVARCSTR 12 0 0 no

11 ROOT_FLAG PK CCSS-LSTAR-Indicates if the Parent ID is aroot of an activity group hierarchy NVARCSTR 1 0 0 no



ACTIVITY_HIER_HZ

Activity Hierarchy Horizontal Flattening - CCSS-LSTAR -- Cannot have a primary key due to duplication of entries possible in SAP



Nullable

1 ACTIVITY_ID PK CCSS-LSTAR-Leaf of the Activity GroupHierarchy NVARCSTR 12 0 0 no


3 LEAF_LVL CCSS-LSTAR-Depth of the leaf from theparent INTEGER 4 0 0 no



6 LVL_00_DESCR CCSS-LSTAR-Activity Hierarchy Level_0_IDDescription NVARCSTR 64 0 0 yes

7 LVL_00_FULL_NAME Activity ID and Descripiton for Root NVARCSTR 120 0 0 yes

8 LVL_00_ID PK CCSS-LSTAR-Root of the Activity GroupHierarchy NVARCSTR 12 0 0 no


10 LVL_01_FULL_NAME Activity ID and Descripiton for Level 1 NVARCSTR 120 0 0 yes

11 LVL_01_ID PKCCSS-LSTAR-A group or a Activity ID. It is nullwhen the hierarchy ended with a lowernumbered node.

NVARCSTR 12 0 0 no


13 LVL_02_FULL_NAME Activity ID and Descripiton for level 2 NVARCSTR 120 0 0 yes


NVARCSTR 12 0 0 no


16 LVL_03_FULL_NAME Activity ID and Description for Level 3 NVARCSTR 120 0 0 yes




NVARCSTR 12 0 0 no




NVARCSTR 12 0 0 no




NVARCSTR 12 0 0 no




NVARCSTR 12 0 0 no


28 LVL_07_FULL_NAME Activity ID and Description for level 7 NVARCSTR 120 0 0 yes


NVARCSTR 12 0 0 no



ACTIVITY_HIER_VR

Activity Hierarchy Vertical Flattening - CCSS-LSTAR - cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR CCSS-LSTAR-Description of the descendant NVARCSTR 64 0 0 yes

2 CHILD_FULL_NAME Child Activity ID and Description NVARCSTR 120 0 0 yes

3 CHILD_ID PK CCSS-LSTAR-Activity Hierarchy Child ID NVARCSTR 12 0 0 no


5 DEPTH CCSS-LSTAR-Depth of the descendant fromthe ancestor INTEGER 4 0 0 yes

6 LEAF_FLAG CCSS-LSTAR-Indicates if the Parent ID is aleaf of an activity group hierarchy INTEGER 4 0 0 yes



9 PARENT_DESCR CCSS-LSTAR-Description of the ancestor NVARCSTR 64 0 0 yes

10 PARENT_FULL_NAME Parent Activity ID and Description NVARCSTR 120 0 0 yes

11 PARENT_ID PK CCSS-LSTAR-Activity Hierarchy Parent ID NVARCSTR 12 0 0 no

12 ROOT_FLAG CCSS-LSTAR-Indicates if the Parent ID is aroot of an activity group hierarchy INTEGER 4 0 0 yes

AW_DIMENSION_SOURCE

Master list of values indicating sources of combined dimensions



Nullable

1 DIM_SRC_DESCR Description of Dimension Source NVARCSTR 60 0 0 yes

2 DIM_SRC_ID PKDimension Source. Used in combineddimension combining similar attributes fromdifferent sources in SAP.

NVARCSTR 30 0 0 no



AW_FIRST_RUN_DATE

First Run Dates records the values of the $G_SDATE and $G_EDATE global variable on the "FIRST" Run of a rapid mart.



Nullable

1 JOB_END_DATE $G_EDATE global variable setting at the timeof the "First" or "Delta" run. DATETIME 24 0 0 yes

2 JOB_LOAD_TYPE PK Will be FIRST or DELTA NVARCSTR 10 0 0 no

3 JOB_NAME PK Name of the Rapid Mart Load Job. NVARCSTR 100 0 0 no

4 JOB_START_DATE $G_SDATE global variable setting at the timeof the "First" or "Delta" run. DATETIME 24 0 0 yes



AW_JOBEXECUTION

Job Execution Status table



Nullable

1 EXTRACTHIGH End Date NVARCSTR 10 0 0 yes

2 EXTRACTLOW Start Date NVARCSTR 10 0 0 yes


4 NAME PK Job Name NVARCSTR 64 0 0 no

5 STATUS Job Status NVARCSTR 12 0 0 yes



AW_LOOKUP_INDEX

Auxilary table to store index information



Nullable

1 ADDTNL_TXT Notes NVARCSTR 64 0 0 yes

2 COLUMN_NAME_01 Index column 1 NVARCSTR 64 0 0 yes



5 INDEX_NAME Index Name NVARCSTR 64 0 0 yes

6 LOAD_DATE Load date in Rapid mart DATETIME 24 0 0 yes

7 LOAD_TIME Load time in Rapid mart NVARCSTR 8 0 0 yes

8 TBL_NAME Table name the index belong to NVARCSTR 64 0 0 yes



BUSINESS_ACTIVITY

FK-SL Activity attributes from T022/T022T



Nullable

1 BUS_ACTIVITY_DESCR T022T.TXT -Text (30 Characters) NVARCSTR 30 0 0 yes

2 BUS_ACTIVITY_ID PK T022.ACTIVITY -FI-SL Business Transaction NVARCSTR 4 0 0 no

3 BUS_ACTIVITY_TYPE_DESCR lookup on VORGTYP domain in DD07T NVARCSTR 60 0 0 yes

4 BUS_ACTIVITY_TYPE_ID

T022.VORGTYP -Activity type for FI-SLactivities NVARCSTR 1 0 0 yes

5 LOAD_DATE Date and Time loaded into Rapid mart DATETIME 24 0 9 yes

6 LOAD_TIME Time Loaded into Rapid mart NVARCSTR 8 0 0 yes

7 RECORD_TYPE_DESCR lookup on RRCTY domain in DD07T NVARCSTR 60 0 0 yes

8 RECORD_TYPE_ID T022.SATZTYP -Record Type NVARCSTR 1 0 0 yes

BUSINESS_AREA

Business Areas - TGSB, TSGBT



Nullable

1 BUS_AREA_DESCR TGSBT-GTEXT-Business area description NVARCSTR 30 0 0 yes

2 BUS_AREA_FULL_NAME Business Area ID and Descritpion NVARCSTR 120 0 0 yes

3 BUS_AREA_ID PK TGSB-GSBER-Business area NVARCSTR 4 0 0 no





CAPACITY

Capacity master data from KAKO/KAKT



Nullable

1 CALENDAR_DESCR TFACT.LTEXT - Factory Calendar descritpion NVARCSTR 60 0 0 yes

2 CALENDAR_ID KAKO.KALID - Factory calendar ID NVARCSTR 2 0 0 yes

3 CAPACITY_CATEG_DESCR

TC26T- TXT -Lookup capacity categorydescription NVARCSTR 20 0 0 yes

4 CAPACITY_CATEG_ID KAKO.KAPAR - Capacity category NVARCSTR 3 0 0 yes

5 CAPACITY_DESCR Lookup description of capacity ID NVARCSTR 40 0 0 yes

6 CAPACITY_FULL_NAME KAKO.NAME - Capacity name NVARCSTR 55 0 0 yes

7 CAPACITY_ID PK KAKO.KAPID - Capacity ID NVARCSTR 20 0 0 no

8 CAPACITY_NAME KAKO.NAME - Capacity name NVARCSTR 8 0 0 yes

9 CAPACITY_VERSION_NUM

KAKO.VERSA - Active version of availablecapacity NVARCSTR 2 0 0 yes

10 CMPNY_CODE_ID T001K -BUKRS -Company Code ID NVARCSTR 4 0 0 yes

11 CMPNY_CODE_NAME Lookup on Company Code Name NVARCSTR 25 0 0 yes

12 FINITE_SCHED_FLAG KAKO.KAPTER - Indicator: Capacity relevantto finite scheduling INTEGER 4 0 0 yes

13 LOAD_DATE Date and time loaded into Rapid Mart DATETIME 24 0 9 yes

14 LOAD_TIME Time when the record was loaded NVARCSTR 8 0 0 yes

15 MULTIPLE_USE_FLAG KOKO.KAPAVO - Indicator: Severaloperations can use capacity INTEGER 4 0 0 yes

16 PLANNG_GRP_ID KAKO.PLANR - Capacity planner group NVARCSTR 3 0 0 yes



17 PLANNG_GRP_NAME T024i-INNAM - Name of the maintenanceplanning group NVARCSTR 18 0 0 yes

18 PLANT_ID KAKO.WERKS - Plant NVARCSTR 4 0 0 yes

19 PLANT_NAME T001W.NAME1 Name - Lookup on Plantname for Planning Plant NVARCSTR 30 0 0 yes

20 POOL_CAPACITY_FLAG KAKO.POOLK - Indicator for pooled capacity INTEGER 4 0 0 yes

21 PRCNT_OVERLOAD_RATE KAKO.UEBERLAST - Percent Overload NVARCSTR 3 0 0 yes

22 PRCNT_UTILIZATION_RATE

KAKO.NGRAD - Capacity utilization rate(percent) INTEGER 4 0 0 yes

23 QTY_INDIVID_CAPACITY

KAKO.AZNOR - Number of individualcapacities DECIMAL 48 28 0 yes

24 SECS_CAPACITY_END

KAKO.ENDZT - Finish time in seconds(internal) DECIMAL 48 28 0 yes

25 SECS_CAPACITY_PAUSE

KAKO.PAUSE - Cumulative break time inseconds (internal) DECIMAL 48 28 0 yes

26 SECS_CAPACITY_START

KAKO.BEGZT - Start time in seconds(internal) DECIMAL 48 28 0 yes

27 SHORT_TERM_PLAN_FLAG

KAKO.KAPLPL - Indicator: Capacity excludedfrom long-term planning INTEGER 4 0 0 yes

28 UOM_ID_BASE KAKO.MEINS - Base unit of measure forcapacity NVARCSTR 3 0 0 yes

29 VALUATN_AREA_ID T001K.BWKEY -Valuation Area NVARCSTR 4 0 0 yes



CHARACTERISTIC_STAGE

Staging of characteristics master data fro AUSP/CABN for Equipment and Funcational location



Nullable

1 CHARACTSTC_DESCR

CABNT-ATBEZ(lookup) - Characteristicdescription NVARCSTR 30 0 0 yes

2 CHARACTSTC_FORMAT CABN-ATFOR - Characteristic data type NVARCSTR 4 0 0 yes

3 CHARACTSTC_HEADNG_01 CABNT-ATUE1 (lookup) - First heading line NVARCSTR 30 0 0 yes

4 CHARACTSTC_HEADNG_02 CABNT-ATUE2 (lookup) - Second heading line NVARCSTR 30 0 0 yes

5 CHARACTSTC_ID PK AUSP-ATINN - Internal characteristic NVARCSTR 10 0 0 no

6 CHARACTSTC_NAME CABN-ATNAM (lookup) - Characteristic uniquename NVARCSTR 30 0 0 yes

7 CHARACTSTC_VALUE AUSP-ATWRT- Characteristic value NVARCSTR 30 0 0 yes

8 CLASS_TYPE_ID PK AUSP-KLART - Characteristic Class type NVARCSTR 3 0 0 no

9 LOAD_DATE Date and Time Loaded into Rapid Mart DATETIME 24 0 9 yes

10 LOAD_TIME Time Loaded into Rapid Mart NVARCSTR 8 0 0 yes

11 OBJ_ID PK AUSP-OBJEK - Object number NVARCSTR 50 0 0 no

12 OBJ_TABLE_NAME TCLA.OBTAB - Name of database table forobject NVARCSTR 10 0 0 yes

13 UOM_ID_VALUE CABN--MSEHI - Unit of measurement NVARCSTR 3 0 0 yes

14 VALID_FROM_DATE AUSP.ATFLV - Derived Date from and TimeFrom bucket DATETIME 24 0 9 yes

15 VALID_FROM_NUMBER AUSP.ATFLV - Derived Number From bucket DECIMAL 48 28 10 yes

16 VALID_FROM_VALUE AUSP-ATFLV - Tolerance from DECIMAL 48 28 10 yes



17 VALID_TO_DATE AUSP.ATFLB - Derive Date To and Time Tobucket DATETIME 24 0 9 yes

18 VALID_TO_NUMBER AUSP.ATFLB - Derived Number To bucket DECIMAL 48 28 10 yes

19 VALID_TO_VALUE AUSP-ATFLB - Tolerance to DECIMAL 48 28 10 yes

20 VALUE_OPERATOR AUSP-ATCOD - Code (expression operatior)for value definition NVARCSTR 6 0 0 yes

21 VALUE_PRECISION CABN-ANZST - Number of characters NVARCSTR 5 0 0 yes

22 VALUE_SCALE CABN-AMZDZ - Number of decimal places NVARCSTR 5 0 0 yes

CHART_OF_ACCOUNTS

Chart of Accounts in SAP (T004 and T004T tables)



Nullable

1 CHART_OF_ACCT_FULL_NAME Chart of accounts full name NVARCSTR 120 0 0 yes

2 CHART_OF_ACCT_ID PK Chart of accounts NVARCSTR 4 0 0 no

3 CHART_OF_ACCT_NAME Chart of accounts description NVARCSTR 50 0 0 yes





CLASSIFICATION_HIER

Classification Hierarchy for the objects - KSSK/TCLA/KLAH



Nullable

1 CHILD_DESCR KLAT-TXTBZ (lookup) - Object descriptionlookup NVARCSTR 60 0 0 yes

2 CHILD_ID PK KSSK-OBJEK -Object number NVARCSTR 50 0 0 no

3 CHILD_NAME KLAH-CLASS (lookup) - Class name NVARCSTR 60 0 0 yes

4 CLASS_TYPE_DESCR TCLAT-KLART (lookup) - Class typedescription + KSSK-KLART - Class type ID NVARCSTR 50 0 0 yes

5 CLASS_TYPE_ID PK KSSK-KLART - Class type NVARCSTR 3 0 0 no



8 OBJ_CLASS_FLAG PK KSSK.MAFID - Indicator: object/class NVARCSTR 1 0 0 no

9 PARENT_DESCR KLAT-TXTBZ (lookup) - Class descriptionlookup NVARCSTR 60 0 0 yes

10 PARENT_ID PK KSSK-CLINT - Internal class number NVARCSTR 50 0 0 no

11 PARENT_NAME KLAH-CLASS (lookup) - Class number NVARCSTR 60 0 0 yes

12 TABLE_NAME TCLA.OBTAB - Name of database table forobject NVARCSTR 10 0 0 yes




Horizontal flattening of Equipment and Classification hierarchy relationships



Nullable

1 CLASS_TYPE_FULL_NAME PK TCLA-KLART (lookup) - Classific. type ID and

TCLAT-ARTXT Classific Type Description NVARCSTR 50 0 0 yes

2 CLASS_TYPE_ID PK TCLA-KLART- Classification type ID NVARCSTR 3 0 0 no

3 INTERNAL_CLASS_ID PK KSSK-CLINT/KSSK-OBJEK - Internalclass/Object number NVARCSTR 50 0 0 no

4 LEAF_LVL Cost Center Hierarchy Child ID DECIMAL 48 28 0 yes

5 LOAD_DATE Load date DATETIME 24 0 9 yes

6 LOAD_TIME Load time NVARCSTR 8 0 0 yes

7 LVL_00_DESCR KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) -Object description/name lookup NVARCSTR 60 0 0 yes

8 LVL_00_FULL_NAME Cost Center ID and Desc for Level 0 NVARCSTR 120 0 0 yes

9 LVL_00_ID PK KSSK-CLINT - Internal class number NVARCSTR 50 0 0 no


11 LVL_01_FULL_NAMEKSSK-CLINT/KSSK-OBJEK - Internalclass/Object number + KLAT-TXTBZ(lookup)/KLAH-CLASS (lookup) - Objectdescription/name lookup

NVARCSTR 120 0 0 yes

12 LVL_01_ID PK KSSK-CLINT/KSSK-OBJEK - Internalclass/Object number NVARCSTR 50 0 0 no









Vertical flattening of Equipment and Classification hierarchy relationships



Nullable

1 CHILD_DESCR KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) -Object description/name lookup NVARCSTR 60 0 0 yes

2 CHILD_FULL_NAMEKSSK-CLINT/KSSK-OBJEK - Internalclass/Object number + KLAT-TXTBZ(lookup)/KLAH-CLASS (lookup) - Objectdescription/name lookup


3 CHILD_ID PK KSSK-CLINT/KSSK-OBJEK - Internalclass/Object number NVARCSTR 50 0 0 no

4 CLASS_TYPE_FULL_NAME

TCLAT-KLART (lookup) - Class typedescription + KSSK-KLART - Class type ID NVARCSTR 50 0 0 no

5 CLASS_TYPE_ID PK TCLA-KLART- Classification type ID NVARCSTR 3 0 0 no

6 DEPTH Node depth in the hierarchy DECIMAL 48 28 0 yes

7 LEAF_FLAG 1- Leaf, 0 - parent DECIMAL 48 28 0 yes

8 LOAD_DATE Load date DATETIME 24 0 9 yes

9 LOAD_TIME Load time NVARCSTR 8 0 0 yes

10 PARENT_DESCR KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) -Object description/name lookup NVARCSTR 60 0 0 yes

11 PARENT_FULL_NAMEKSSK-CLINT/KSSK-OBJEK - Internalclass/Object number + KLAT-TXTBZ(lookup)/KLAH-CLASS (lookup) - Objectdescription/name lookup


12 PARENT_ID PK KSSK-CLINT/KSSK-OBJEK - Internalclass/Object number NVARCSTR 50 0 0 no

13 ROOT_FLAG 1 - Root, 0 - child DECIMAL 48 28 0 yes



COMPANY_CODE

T001 - Company Code master



Nullable

1 ADDRESS_ID Company default address identifier NVARCSTR 10 0 0 yes

2 CHART_OF_ACCT_ID Company Code chart of accounts NVARCSTR 4 0 0 yes

3 CHART_OF_ACCT_ID_COUNTRY

Chart of Accounts according to countrylegislation NVARCSTR 4 0 0 yes

4 CHART_OF_ACCT_NAME Chart of Accounts Name NVARCSTR 50 0 0 yes

5 CITY Company City Name NVARCSTR 40 0 0 yes

6 CMPNY_CODE_FULL_NAME Company Code and Name NVARCSTR 120 0 0 yes

7 CMPNY_CODE_ID PK T001-BURKS - Company Code ID NVARCSTR 4 0 0 no

8 CMPNY_CODE_ID_ORIGINAL Original Key of Company Code NVARCSTR 4 0 0 yes

9 CMPNY_CODE_NAME Company Code Name NVARCSTR 40 0 0 yes

10 CMPNY_CODE_NAME_01 Name of the Company - 1st description NVARCSTR 40 0 0 yes

11 CMPNY_CODE_NAME_02 Name of the Company - 2nd description NVARCSTR 40 0 0 yes

12 CMPNY_CODE_NAME_03 Name of the Company - 3rd description NVARCSTR 40 0 0 yes

13 CMPNY_CODE_NAME_04 Name of the Company - 4th description NVARCSTR 40 0 0 yes

14 COUNTRY_ID Country Identifier NVARCSTR 3 0 0 yes

15 COUNTRY_NAME Country Name (lookup) NVARCSTR 15 0 0 yes

16 CR_CTRL_AREA_DESCR Credit Controlling Area description NVARCSTR 35 0 0 yes



17 CR_CTRL_AREA_ID Credit Control area NVARCSTR 4 0 0 yes

18 CURR_ID Company Code Currency ID NVARCSTR 5 0 0 yes

19 DISTRICT District of the Company NVARCSTR 40 0 0 yes

20 FAX Fax no of the Company NVARCSTR 40 0 0 yes

21 FIN_MGMT_AREA_ID Financial Management Area NVARCSTR 4 0 0 yes

22 FISC_YR_VARIANT_ID Company code fiscal year variant NVARCSTR 2 0 0 yes

23 FISC_YR_VARIANT_NAME Company code fiscal year variant name NVARCSTR 30 0 0 yes

24 HOUSE_NUMBER Company code house number NVARCSTR 10 0 0 yes

25 LANG_DESCR Company code language Description NVARCSTR 16 0 0 yes

26 LANG_ID Company Code default language NVARCSTR 1 0 0 yes



29 PHONE Company code telephone number NVARCSTR 30 0 0 yes

30 REGION_ID Company code region NVARCSTR 3 0 0 yes

31 REGION_NAME Company code region name NVARCSTR 20 0 0 yes

32 STREET Company code street name NVARCSTR 60 0 0 yes

33 TAX_JURISDIC_NUM Jurisdiction fo tax calculation - tax jurisdictioncode NVARCSTR 15 0 0 yes

34 VAT_REGISTRTN_NUM VAT regulation number NVARCSTR 20 0 0 yes



35 ZIP Company code postal code NVARCSTR 10 0 0 yes

CONTROL_KEY

Business transactions should be executed for the object that belongs to the task list or order (from T430)



Nullable

1 AUTO_GR_FLAG T430.AUTWE - Indicator: automatic goodsreceipt NVARCSTR 1 0 0 yes

2 CAPACITY_PLAN_FLAG T430.KAPA - Indicator: Capacity planning NVARCSTR 1 0 0 yes

3 CONFIRMATN_FLAG_DESCR Lookup description of confirmation indicator NVARCSTR 60 0 0 yes

4 CONFIRMATN_FLAG_ID

T430.RUEK - Indicator: completionconfirmation NVARCSTR 1 0 0 yes

5 CTRL_KEY_DESCR Lookup description of control key NVARCSTR 40 0 0 yes

6 CTRL_KEY_ID PK T430.STEUS - Control key NVARCSTR 4 0 0 no

7 INSPECTN_FLAG T430.MRKKZ - Indicator: inspectioncharacteristics for operation require NVARCSTR 1 0 0 yes



10 REWORK_FLAG T430.REWORK - Indicator: Rework operation NVARCSTR 1 0 0 yes

11 SCHEDULE_FLAG T430.TERM - Indicator: Scheduling NVARCSTR 1 0 0 yes

12 SERVICE_FLAG T430.SERVICE - Indicator: Service NVARCSTR 1 0 0 yes



CONTROLLING_AREA

TKA01 - Controlling areas master



Nullable

1 CTRL_AREA_DESCR Controlling Area Name NVARCSTR 25 0 0 yes

2 CTRL_AREA_FULL_NAME Controlling Area DI and Desc NVARCSTR 120 0 0 yes

3 CTRL_AREA_ID PK TKA01-KORKS - Controlling Area ID NVARCSTR 4 0 0 no

4 CURR_ID Currency Code for Controlling Area NVARCSTR 5 0 0 yes

5 FISC_YR_VARIANT_ID Fiscal Year Variant NVARCSTR 2 0 0 yes

6 LEDGER_ID_PROFIT_CNTR Financial Ledger ID profit Center NVARCSTR 2 0 0 yes



9 OPERTNG_CONCERN_ID Operating Concern NVARCSTR 4 0 0 yes

10 PROFIT_CNTR_AREA Profit Center Group NVARCSTR 12 0 0 yes

11 STD_SET_HIER_CODE Standard Hierarchy for Cost Centers NVARCSTR 12 0 0 yes



COST_CENTER

CSKS - Cost Center Master



Nullable

1 ALT_FUNCTN CSKS.AFUNK - Alternative function of CostCenter NVARCSTR 3 0 0 yes

2 BUS_AREA_ID Business Area ID NVARCSTR 4 0 0 yes

3 CITY Cost Center City Name NVARCSTR 40 0 0 yes

4 CMPNY_CODE_ID Company Code ID NVARCSTR 4 0 0 yes

5 CMPNY_CODE_NAME Company code name associated with this CostCenter NVARCSTR 40 0 0 yes

6 COST_CNTR_DESCR Cost Center Descritpion NVARCSTR 60 0 0 yes

7 COST_CNTR_FULL_NAME Cost Center ID and Desc NVARCSTR 120 0 0 yes

8 COST_CNTR_ID PK CSKS-KOSTL - Cost Center ID NVARCSTR 10 0 0 no

9 COST_CNTR_ID_SUBSEQUENT CSKS.NKOST - Subsequent Cost Center ID NVARCSTR 10 0 0 yes

10 COST_CNTR_NAME Cost Center Default Name NVARCSTR 40 0 0 yes

11 COST_CNTR_NAME_01 Cost Center Name Line 1 NVARCSTR 40 0 0 yes




15 COUNTRY_ID Cost Center Country Code NVARCSTR 3 0 0 yes

16 COUNTRY_NAME Cost Center Country Name NVARCSTR 15 0 0 yes



17 CREATED_BY Person ID who created the record NVARCSTR 12 0 0 yes

18 CREATE_DATE Date when the record was created in thesource system DATETIME 24 0 9 yes

19 CTRL_AREA_DESCR Control Area description NVARCSTR 25 0 0 yes

20 CTRL_AREA_ID PK Controlling Area Identifier NVARCSTR 4 0 0 no

21 CURR_ID Cost Center Currency ID NVARCSTR 5 0 0 yes

22 DEPARTMENT CSKS.ABTEI - Department NVARCSTR 12 0 0 yes

23 DISTRICT Cost Center City District NVARCSTR 40 0 0 yes

24 EQUITY_TYPE_CODE CSKS.ETYPE - Equity type NVARCSTR 3 0 0 yes

25 FAX Cost Center fax number NVARCSTR 40 0 0 yes

26 FUNCTN_CODE CSKS.FUNKT - function of Cost Center NVARCSTR 3 0 0 yes



29 PERSON_IN_CHARGE CSKS.VERAK - Cost Center Manager NVARCSTR 20 0 0 yes

30 PHONE Cost Center phone # 1 NVARCSTR 30 0 0 yes

31 PROFIT_CNTR_DESCR Profit Center Description NVARCSTR 40 0 0 yes

32 PROFIT_CNTR_ID CSKS.PRCTR - Profit Center Code NVARCSTR 10 0 0 yes

33 REGION_ID Region ID NVARCSTR 3 0 0 yes

34 REGION_NAME Region name NVARCSTR 20 0 0 yes



35 STREET Cost Center Street name NVARCSTR 60 0 0 yes

36 TYPE_CODE Cost Center Type Identifier NVARCSTR 1 0 0 yes

37 VALID_FROM_DATE Record is valid to DATETIME 24 0 9 yes

38 VALID_TO_DATE Record Valid from DATETIME 24 0 9 yes

39 ZIP Cost Center ZIP code NVARCSTR 10 0 0 yes

COST_CENTER_HIER

Cost Center Hierarchy - CCSS-KOSTL - Cannot have a primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Cost Center Child description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no

3 CTRL_AREA_ID PK Controlling Area ID NVARCSTR 4 0 0 no

4 LEAF_FLAG PK Is Leaf NVARCSTR 1 0 0 no



7 PARENT_DESCR Cost Center parent descritpion NVARCSTR 64 0 0 yes

8 PARENT_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no

9 ROOT_FLAG PK Is Root NVARCSTR 1 0 0 no



COST_CENTER_HIER_BAD

CCSS-KOSTL Cost Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Cost Center Child description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no







9 PARENT_DESCR Cost Center parent descritpion NVARCSTR 64 0 0 yes

10 PARENT_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no




COST_CENTER_HIER_HZCCSS-KOSTL Cost Center hierarchy flattenned horizontally -- Cannot have a primary key on this table due to possible duplicate entries inSAP



Nullable

1 COST_CNTR_ID PK Cost Center ID (current node) NVARCSTR 12 0 0 no


3 LEAF_LVL Is Leaf Level INTEGER 4 0 0 no



6 LVL_00_DESCR Cost Center Root Node Description NVARCSTR 64 0 0 yes


8 LVL_00_ID PK Cost Center root node ID NVARCSTR 12 0 0 no

9 LVL_01_DESCR Cost Center level 1 Node Description NVARCSTR 64 0 0 yes


11 LVL_01_ID PK Cost Center level 1 Node ID NVARCSTR 12 0 0 no


13 LVL_02_FULL_NAME Cost Center Id and Desc for Level 2 NVARCSTR 120 0 0 yes

















28 LVL_07_FULL_NAME Cost Center Id and Dec for Level 7 NVARCSTR 120 0 0 yes













COST_CENTER_HIER_VR

CCSS-KOSTL - Cost Center Hierarchy vertically flattenned - cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Cost Center Child Node Description NVARCSTR 64 0 0 yes

2 CHILD_FULL_NAME Cost Center ID and Desc for the Child NVARCSTR 120 0 0 yes

3 CHILD_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no


5 DEPTH Node depth level INTEGER 4 0 0 yes

6 LEAF_FLAG Is Leaf INTEGER 4 0 0 yes



9 PARENT_DESCR Cost Center Child Node Descritpion NVARCSTR 64 0 0 yes

10 PARENT_FULL_NAME Cost Center Parent ID and Desc NVARCSTR 120 0 0 yes

11 PARENT_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no

12 ROOT_FLAG Is Root INTEGER 4 0 0 yes



COST_ELEMENT

CSKA - Cost Element (GL Accounts) Master



Nullable

1 CHART_OF_ACCT_ID PK Accounting Chart of accounts ID NVARCSTR 4 0 0 no

2 COST_ELEM_DESCR Cost center description in default language NVARCSTR 40 0 0 yes

3 COST_ELEM_FULL_NAME Cost Element ID and Description NVARCSTR 120 0 0 yes

4 COST_ELEM_ID PK Cost Element (GL Account) ID NVARCSTR 10 0 0 no

5 CREATE_DATE Date when the record was created in thesource system DATETIME 24 0 9 yes



8 PAYMNT_RELEVNT_FLAG

CSKA.ZAHKZ - Cost element ispayment-relevant NVARCSTR 1 0 0 yes

9 TAX_RELEVNT_FLAG CSKA.STEKZ - Cost Element is tax-relevant NVARCSTR 1 0 0 yes



COST_ELEMENT_HIER

CCSS-KSTAR Cost Element hierarchy - cannot have primary key due to data duplication possible in SAP



Nullable

1 CHART_OF_ACCT_ID PK Accounting Chart of Accounts ID NVARCSTR 4 0 0 no

2 CHILD_DESCR Cost Element Child Node Description NVARCSTR 64 0 0 yes

3 CHILD_ID PK Cost Element Child Node ID NVARCSTR 12 0 0 no




7 PARENT_DESCR Cost Element Parent Node Descritpion NVARCSTR 64 0 0 yes

8 PARENT_ID PK Cost Element Parent Node ID NVARCSTR 12 0 0 no




COST_ELEMENT_HIER_BAD

CCSS-KSTAR Cost ElementHierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP



Nullable


2 CHILD_DESCR Cost Element Child Node Description NVARCSTR 64 0 0 yes

3 CHILD_ID PK Cost Element Child Node ID NVARCSTR 12 0 0 no






9 PARENT_DESCR Cost Element Parent Node Descritpion NVARCSTR 64 0 0 yes

10 PARENT_ID PK Cost Element Parent Node ID NVARCSTR 12 0 0 no




COST_ELEMENT_HIER_HZ

CCSS-KSTAR - Cost Element Hierarchy- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHART_OF_ACCT_ID PK Accounting Chart Of Account ID NVARCSTR 4 0 0 no

2 COST_ELEM_ID PK Cost Element (GL Account) ID NVARCSTR 12 0 0 no

3 LEAF_LVL Cost Element Leaf level (depth) DECIMAL 48 28 0 no



6 LVL_00_DESCR Cost Element Root Node Description NVARCSTR 64 0 0 yes

7 LVL_00_FULL_NAME Cost Element ID and Descripion for level 0 NVARCSTR 120 0 0 yes

8 LVL_00_ID PK Cost Element Root Node ID NVARCSTR 12 0 0 no

9 LVL_01_DESCR Cost Element Level 1 Node Description NVARCSTR 64 0 0 yes

10 LVL_01_FULL_NAME Cost Element ID and Desc for Level 1 NVARCSTR 120 0 0 yes

11 LVL_01_ID PK Cost Element Level 1 Node ID NVARCSTR 12 0 0 no








COST_ELEMENT_HIER_VR

CCSS-KSTAR - Cost Element Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP



Nullable


2 CHILD_DESCR Cost Element Parent Node Descritpion NVARCSTR 64 0 0 yes

3 CHILD_FULL_NAME Cost Element Child ID and Desc NVARCSTR 120 0 0 yes

4 CHILD_ID PK Cost Element Parent Node ID NVARCSTR 12 0 0 no

5 DEPTH Cost Element node depth level DECIMAL 48 28 0 yes

6 LEAF_FLAG Is Leaf DECIMAL 48 28 0 yes



9 PARENT_DESCR Cost Element Child Node Description NVARCSTR 64 0 0 yes

10 PARENT_FULL_NAME Cost Element Parent ID and Desc NVARCSTR 120 0 0 yes

11 PARENT_ID PK Cost Element Child Node ID NVARCSTR 12 0 0 no

12 ROOT_FLAG Is Root DECIMAL 48 28 0 yes



CURRENCY

TCURC, TCURT



Nullable

1 CURR_DECIMAL Lookup TCURX.CURRDEC - Number ofdecimals to display amounts in this currency. DECIMAL 48 28 0 yes

2 CURR_DESCR TCURT-LTEXT - Long Text NVARCSTR 60 0 0 yes

3 CURR_ID PK TCURC-WAERS - Currency Key NVARCSTR 5 0 0 no

4 CURR_ID_ALT TCURC-ALTWR - Alternative Key ForCurrencies NVARCSTR 3 0 0 yes

5 CURR_ISO_CODE TCURC-ISOCD - ISO Currency Code NVARCSTR 3 0 0 yes

6 DISPLAY_FACTORMultiply currency amounts by this factor todisplay with correct number of decimals for thecurrency

DECIMAL 48 17 14 yes



9 VALID_TO_DATE TCURC-GDATU -Date Up Until Which TheCurrency Is Valid DATETIME 24 0 9 yes



CUSTOMER

General customer master data at the customer level (KNA1)



Nullable

1 ACCT_GRP_ID KNA1-KTOKD - Customer Group Account NVARCSTR 4 0 0 yes

2 ACCT_GRP_NAME Lookup of account group name fromT077X.TXT30 from KNA1.KTKOD NVARCSTR 30 0 0 yes

3 ADDRESS_ID Load date NVARCSTR 10 0 0 yes

4 AMT_ANNUAL_SALES KNA1-UMSAT - Annual sale DECIMAL 48 15 2 yes

5 AMT_ANNUAL_SALES_02 KNA1-UMSA1 - Annual Sales DECIMAL 48 15 2 yes

6 ANNUAL_SALES_YR KNA1-UMJAH - Year for which sales are given NVARCSTR 4 0 0 yes

7 CITY KNA1-ORT01 - City NVARCSTR 40 0 0 yes

8 CLASSIFCTN_CODE KNA1-KUKLA - Customer Classification NVARCSTR 2 0 0 yes

9 CLASSIFCTN_DESCRLookup of TKUKT.VTEXT for description ofcustomer classification (size by total sales)based on KNA1.KUKLA.

NVARCSTR 20 0 0 yes

10 COMPETITOR_FLAG KNA1-DEAR1 - Competitor ID NVARCSTR 1 0 0 yes

11 COUNTRY_ID KNA1-LAND1 - Country NVARCSTR 3 0 0 yes

12 COUNTRY_NAME Country Name NVARCSTR 15 0 0 yes

13 CUSTOMER_FULL_NAME Customer Full Name NVARCSTR 120 0 0 yes

14 CUSTOMER_GRP_KEY Customer Group Key NVARCSTR 10 0 0 yes

15 CUSTOMER_ID PK KNA1-KUNNR - Customer Number NVARCSTR 10 0 0 no

16 CUSTOMER_NAME Customer Name NVARCSTR 40 0 0 yes



17 CUSTOMER_NAME_01 KNA1-NAME1 - Customer Name 1 NVARCSTR 40 0 0 yes

18 CUSTOMER_NAME_02 KNA1-NAME2 - Customer Name 2 NVARCSTR 40 0 0 yes

19 CUSTOMER_NAME_03 Customer Name 3 NVARCSTR 40 0 0 yes

20 CUSTOMER_NAME_04 Customer Name 4 NVARCSTR 40 0 0 yes

21 DISTRICT KNA1-ORT02 - District NVARCSTR 40 0 0 yes

22 EMPL_COUNT KNA1-JMZAH - Number of employees for theyear DECIMAL 48 28 0 yes

23 FAX KNA1-TELFX - Fax Number NVARCSTR 40 0 0 yes

24 HOUSE_NUMBER Customer House Number NVARCSTR 10 0 0 yes

25 INDUSTRY_ID KNA1-BRSCH - Industry NVARCSTR 4 0 0 yes

26 INDUSTRY_NAMELookup of industry name in T016T.BRTXTwhere SPRAS=$G_LANGUAGE andKNA1.BRSCH=T016T.BRSCH.

NVARCSTR 20 0 0 yes

27 INITIAL_CONTACT KNA1-EKONT - Initial Contact NVARCSTR 10 0 0 yes

28 LANG_DESCR Description of the Language NVARCSTR 16 0 0 yes

29 LANG_ID KNA1-SPRAS -- Language NVARCSTR 1 0 0 yes



32 NIELSEN_CODE KNA1.NIELS - Nielsen ID NVARCSTR 2 0 0 yes

33 PHONE Telephone Number NVARCSTR 30 0 0 yes

34 REGIONAL_MARKET KNA1-RPMKR - Regional market NVARCSTR 10 0 0 yes



35 REGION_ID KNA1-REGIO - Region (State) NVARCSTR 3 0 0 yes

36 REGION_NAME Region Name (State Name) NVARCSTR 20 0 0 yes

37 SALES_PARTNER_FLAG KNA1-DEAR2 - Sales Partner Indicator NVARCSTR 1 0 0 yes

38 SALES_PROSPECT_FLAG KNA1-DEAR3 - Sales Prospect ID NVARCSTR 1 0 0 yes

39 STREET KNA1-STRAS - Street and House Number NVARCSTR 60 0 0 yes

40 VENDOR_ID KNA1.LIFNR -- Vendor (creditor) accountnumber NVARCSTR 10 0 0 yes

41 ZIP KNA1-PSTLZ - Postal Code NVARCSTR 10 0 0 yes

DOCUMENT_CATEGORY

Domain VBTYP (Table DD07T) - Sales Document Categ



Nullable

1 DIM_SRC_ID PK Dimension Source from tableAW_DIMENSION_SOURCE NVARCSTR 10 0 0 no

2 DOC_CATEG_DESCR Document Category Description from multiplesources in SAP NVARCSTR 100 0 0 yes

3 DOC_CATEG_ID PK Document Category ID from multiple sources inSAP NVARCSTR 10 0 0 no

4 LOAD_DATE Date and Time Loaded in Rapid Mart DATETIME 24 0 9 yes




DOCUMENT_TYPE

Internal Order Type attributes from T003O/T003P



Nullable

1 DIM_SRC_ID PK Dimension Source from tableAW_DIMENSION_SOURCE NVARCSTR 10 0 0 no

2 DOC_CATEG_DESCR Document Category Description NVARCSTR 100 0 0 yes

3 DOC_CATEG_ID PK Document Category from multiple Sources inSAP NVARCSTR 10 0 0 no

4 DOC_TYPE_DESCR Document Type Description NVARCSTR 100 0 0 yes

5 DOC_TYPE_ID PK Document Type from Multiple sources in SAP NVARCSTR 10 0 0 no





EQUIPMENT

EQUI, EQUZ, ILOA - Equipment dimension



Nullable

1 ABC_FLAG ILOA-ABCKZ - ABC indicator for technicalobject NVARCSTR 1 0 0 yes

2 ACQUISTN_DATE EQUI-ANSDT - Acquisition date DATETIME 24 0 9 yes

3 AMT_ACQUISTN EQUI-ANSWT - Equipment acquisition value DECIMAL 48 13 2 yes

4 ASSET_MAIN_ID ILOA.ANLNR - Main asset number NVARCSTR 12 0 0 yes

5 ASSET_SUB_ID ILOA.ANLUN - Asset sub-number NVARCSTR 4 0 0 yes

6 BUS_AREA_DESCR Lookup on TGSBT-GTEXT for Sales Org Descr NVARCSTR 30 0 0 yes

7 BUS_AREA_ID ILOA-GSBER - Business area NVARCSTR 4 0 0 yes

8 CHANGE_BY_LOGIN EQUI-AENAM - Name of accounting clerk whochanged record NVARCSTR 12 0 0 yes

9 CHANGE_DATE EQUI-AEDAT - Last changed on DATETIME 24 0 9 yes

10 CMPNY_CODE_ID ILOA-BUKRS - Company code NVARCSTR 4 0 0 yes

11 CMPNY_CODE_NAME T001.BUTXT -Lookup on Company CodeName NVARCSTR 25 0 0 yes

12 CONSTRUCTN_MONTH EQUI-BAUMM - Month of construction DECIMAL 48 28 0 yes

13 CONSTRUCTN_YEAR EQUI-BAUJJ - Year of construction DECIMAL 48 28 0 yes

14 COST_CNTR_ID ILOA.KOSTL - Cost center NVARCSTR 10 0 0 yes

15 COST_CNTR_NAME CSKT.KTEXT - Lookup on Cost Center Name NVARCSTR 40 0 0 yes

16 CREATE_BY_LOGIN EQUI-ERNAM - Name of person who createdobject NVARCSTR 12 0 0 yes



17 CREATE_DATE EQUI-ERDAT - Date on which the record wascreated DATETIME 24 0 9 yes

18 CTRL_AREA_ID ILOA.KOKRS - Controlling area NVARCSTR 4 0 0 yes

19 CTRL_AREA_NAME Lookup on TKA01 for controlling area name NVARCSTR 25 0 0 yes

20 CURR_ID EQUI-WAERS - Currency key NVARCSTR 5 0 0 yes

21 DAYS_DELIVER Number of days from Acquisiton till OriginalDelivery (calcualted) DECIMAL 48 28 0 yes

22 DAYS_INSTALL Number of days from Acquisiton till Originalstartup (calcualted) DECIMAL 48 28 0 yes

23 DAYS_IN_OPERATION

Total number of days since the original startupas of LOAD_DATE (calcualted) DECIMAL 48 28 0 yes

24 DAYS_WARRANTY Duration of the warranty (calcualted) DECIMAL 48 28 0 yes

25 DISTRIBTN_CHANNEL_DESCR Lookup on TVTWT-VTEXT for Sales Org Descr NVARCSTR 40 0 0 yes

26 DISTRIBTN_CHANNEL_ID ILOA.VTWEG - Distribution channel NVARCSTR 2 0 0 yes

27 DIVISION_DESCR Lookup on TVTWT-VTEXT for Sales Org Descr NVARCSTR 40 0 0 yes

28 DIVISION_ID ILOA.SPART - Division NVARCSTR 2 0 0 yes

29 EQUIPMNT_CATEG_DESCR

T370U-TYPTX (lookup) - Equipment categorydescription NVARCSTR 30 0 0 yes

30 EQUIPMNT_CATEG_ID EQUI-EQTYP - Equipment category NVARCSTR 1 0 0 yes

31 EQUIPMNT_DESCR EQKT-EQKTX (lookup) NVARCSTR 40 0 0 yes

32 EQUIPMNT_FULL_NAME

EQUI.EQUNR and EQKT-EQKTX - EquipmentNumber and Descr. NVARCSTR 65 0 0 yes

33 EQUIPMNT_ID PK EQUI-EQUNR - Equipment number NVARCSTR 18 0 0 no

34 EQUIPMNT_ID_PAR EQUZ-HEQUI - Superior equipment NVARCSTR 18 0 0 yes



35 EQUIPMNT_SIZE EQUI-GROES - Size/dimension NVARCSTR 18 0 0 yes

36 EQUIPMNT_TYPE_DESCR

T370K_T-EARTX (lookup) - Equipment Typedescription NVARCSTR 20 0 0 yes

37 EQUIPMNT_TYPE_ID EQUI-EQART - Equipment type NVARCSTR 10 0 0 yes

38 FUNCTNL_LOCATN_DESCR

IFLOTX-PLTXT (lookup) - Functional Loacationdescritpion NVARCSTR 40 0 0 yes

39 FUNCTNL_LOCATN_ID ILOA-TPLNR - Functional location NVARCSTR 30 0 0 yes



42 LOCATN_DESCR T499S-KTEXT (lookup) - Text (40 characters) NVARCSTR 40 0 0 yes

43 LOCATN_ID ILOA-STORT - Location of maintenance object NVARCSTR 10 0 0 yes

44 MANUFCTR_COUNTRY EQUI-HERLD - Country of manufacture NVARCSTR 3 0 0 yes

45 MANUFCTR_MODEL_NUM EQUI-TYPBZ - Manufacturer model number NVARCSTR 20 0 0 yes

46 MANUFCTR_NAME EQUI-HERST - Manufacturer of asset NVARCSTR 30 0 0 yes

47 MANUFCTR_SERIAL_NUM EQUI-SERGE - Manufacturer serial number NVARCSTR 30 0 0 yes

48 MATERIAL_DESCR MAKT.MAKTX - Material Description lookup NVARCSTR 40 0 0 yes

49 MATERIAL_ID EQUI.MATNR - Material number NVARCSTR 18 0 0 yes

50 OBJ_ID EQUI-OBJNR - Object number NVARCSTR 22 0 0 yes

51 PERSON_FULLNAME_RESP

PA0002.NACHN - Personnel Last Name +PA0002.VORNA - Personnel First Name NVARCSTR 85 0 0 yes

52 PERSON_ID_RESP IHPA-PARNR (lookup on VW function) NVARCSTR 12 0 0 yes



53 PLANT_ID ILOA-SWERK - Maintenance plant NVARCSTR 4 0 0 yes

54 PLANT_ID_PLAN EQUZ.IWERK - Planning plant NVARCSTR 4 0 0 yes

55 PLANT_NAME T001W.NAME1 Name - Lookup on Plantname NVARCSTR 30 0 0 yes

56 PLANT_NAME_PLAN T001W.NAME1 Name - Lookup on Plantname for Planning Plant NVARCSTR 30 0 0 yes

57 PROJ_ELEM_DESCR PRPS.POST1 - Lookup of Project (WBS)Element Description NVARCSTR 40 0 0 yes

58 PROJ_ELEM_ID ILOA-PROID - Work breakdown structureelement (WBS element) NVARCSTR 24 0 0 yes

59 ROOM ILOA-MSGRP - Plant Room NVARCSTR 8 0 0 yes

60 SALES_ORG_DESCR Lookup on TVKOT-VTEXT for Sales Org Descr NVARCSTR 60 0 0 yes

61 SALES_ORG_ID ILOA.VKORG Sales organization NVARCSTR 4 0 0 yes

62 SECTION_ID ILOA-BEBER - Plant section NVARCSTR 3 0 0 yes

63 SECTION_PERSON_RESP

T357-FING (lookup) - Person responsible forcompany area NVARCSTR 14 0 0 yes

64 SECTION_PHONE T357-TELE (lookup) - Phone number ofperson responsible for company area NVARCSTR 12 0 0 yes

65 SERIAL_NUM EQUI.SERNR - Serial number NVARCSTR 18 0 0 yes

66 STARTUP_DATE EQUI-INBDT - First start-up date of the pieceof equipment DATETIME 24 0 9 yes

67 TECHNICAL_NUM EQUZ-TIDNR - Technical identification number NVARCSTR 25 0 0 yes

68 UOM_ID_WEIGHT EQUI-GEWEI - Unit of weight NVARCSTR 3 0 0 yes

69 VALID_FROM_DATE EQUI-GWLDT - Guarantee start date DATETIME 24 0 9 yes

70 VALID_TO_DATE EQUI-GWLEN - Date on which the warrantyends DATETIME 24 0 9 yes



71 VENDOR_ID EQUI-ELIEF - Vendor number NVARCSTR 10 0 0 yes

72 WEIGHT EQUI-BRGEW - Gross weight DECIMAL 48 13 3 yes



EQUIPMENT_CHAR_FACT

Equipment Characteristic Details from AUSP/CABN/TCLA



Nullable



3 BUS_AREA_ID PK ILOA-GSBER - Business area NVARCSTR 4 0 0 yes

4 CHARACTSTC_DESCR









12 CMPNY_CODE_ID PK ILOA-BUKRS - Company code NVARCSTR 4 0 0 yes

13 COST_CNTR_ID PK ILOA.KOSTL - Cost center NVARCSTR 10 0 0 yes

14 CTRL_AREA_ID PK ILOA.KOKRS - Controlling area NVARCSTR 4 0 0 yes

15 DAYS_DIFF Calculated date difference for Date-relatedcaracteristics DECIMAL 48 22 7 yes

16 EQUIPMNT_ID PK AUSP-OBJEK - Object number NVARCSTR 18 0 0 no



17 FUNCTNL_LOCATN_ID PK ILOA-TPLNR - Functional location NVARCSTR 30 0 0 yes



20 LOCATN_ID PK ILOA-STORT - Location of maintenance object NVARCSTR 10 0 0 yes

21 MATERIAL_ID PK EQUI.MATNR - Material number NVARCSTR 18 0 0 yes

22 PERSON_ID_RESP PK IHPA-PARNR (lookup on VW function) NVARCSTR 12 0 0 yes

23 PLANT_ID PK ILOA-SWERK - Maintenance plant NVARCSTR 4 0 0 yes

24 PROD_HIER_ID MARA.PRDHA - Product Hierarchy ID - basedon EQUI.MATNR NVARCSTR 18 0 0 yes

25 UOM_ID_VALUE PK CABN--MSEHI - Unit of measurement NVARCSTR 3 0 0 yes

26 VALID_FROM_DATE PK AUSP.ATFLV - Derived Date from and TimeFrom bucket DATETIME 24 0 9 yes











35 VENDOR_ID PK EQUI-ELIEF - Vendor number NVARCSTR 10 0 0 yes

EQUIPMENT_HIER

Equipment Hierarchy Stage table (from EQUI, EQUZ, EQUT in SAP)



Nullable

1 CHILD_CATEG_DESCR


2 CHILD_CATEG_ID EQUI-EQTYP - Equipment category NVARCSTR 1 0 0 yes

3 CHILD_DESCR EQKT-EQKTX (lookup) NVARCSTR 40 0 0 yes

4 CHILD_FULL_NAME EQUI-EQUNRI - Equipment ID +EQUT-EQLTX- Equipment description NVARCSTR 65 0 0 yes

5 CHILD_ID PK EQUI-EQUNR - Equipment number NVARCSTR 18 0 0 no



8 PARENT_CATEG_DESCR


9 PARENT_CATEG_ID EQUI-EQTYP - Equipment category NVARCSTR 1 0 0 yes

10 PARENT_DESCR EQKT-EQKTX (lookup) NVARCSTR 40 0 0 yes

11 PARENT_FULL_NAME EQUI-EQUNRI - Equipment ID +EQUT-EQLTX- Equipment description NVARCSTR 65 0 0 yes

12 PARENT_ID PK EQUZ-HEQUI - Superior equipment NVARCSTR 18 0 0 no



EQUIPMENT_HIER_HZ

EQUI, EQUZ, EQUT - Equipment hierarchy horizontal dimension



Nullable

1 EQUIPMNT_ID PK EQUI-EQUNR - Equipment ID NVARCSTR 18 0 0 no

2 LEAF_LVL Leaf level DECIMAL 48 28 0 yes



5 LVL_00_DESCR EQUT-EQLTX - Equipment description NVARCSTR 40 0 0 yes

6 LVL_00_FULL_NAME EQUI-EQUNRI - Equipment ID +EQUT-EQLTX- Equipment description NVARCSTR 65 0 0 yes

7 LVL_00_ID EQUZ-HEQUI - Superior equipment ID NVARCSTR 18 0 0 yes



10 LVL_01_ID EQUI-EQUNRI - Equipment ID NVARCSTR 18 0 0 yes









EQUIPMENT_HIER_VR

EQUI, EQUZ, EQUT - Equipment hierarchy Vertical dimension



Nullable

1 CHILD_DESCR EQUT-EQLTX - Equipment text NVARCSTR 40 0 0 yes

2 CHILD_FULL_NAME EQUI-EQUNRI - Equipment ID +EQUT-EQLTX- Equipment description NVARCSTR 65 0 0 yes

3 CHILD_ID PK EQUI-EQUNR - Equipment number NVARCSTR 18 0 0 no

4 DEPTH Depth of the decendent DECIMAL 48 28 0 yes

5 LEAF_FLAG Leaf flag (1 - means this is a leaf, 0 - means itis not a leaf) DECIMAL 48 28 0 yes



8 PARENT_DESCR EQUT-EQLTX - Equipment description NVARCSTR 40 0 0 yes

9 PARENT_FULL_NAME EQUI-EQUNRI - Equipment ID +EQUT-EQLTX- Equipment description NVARCSTR 65 0 0 yes

10 PARENT_ID PK EQUZ-HEQUI - Superior equipment number NVARCSTR 18 0 0 no

11 ROOT_FLAG Root flag (1 - means this is a root, 0 - means itis not a root) DECIMAL 48 28 0 yes




Descriptive attributes for Accounting Summary table Value Category from TPIR1T



Nullable



3 RECORD_CATEG_DESCR TPIR1T-KTEXT - Text NVARCSTR 30 0 0 yes

4 RECORD_CATEG_ID PK TPIR1T-ACPOS - Value category NVARCSTR 14 0 0 no

FINANCIAL_RECORD_TYPELoads Special Ledger Record Types dimension (Domain RRCTY) from table DD07T and Cost/Plant Maintenance value types fromCO_WRTTP domain of DD07T table - FINANCIAL_RECORD_



Nullable

1 DIM_SRC_ID PKDimension Source. Used in combineddimension combining similar attributes fromdifferent sources in SAP.

NVARCSTR 10 0 0 no



4 RECORD_TYPE_DESCR Financial Record Type Desc. NVARCSTR 60 0 0 yes

5 RECORD_TYPE_ID PK Financial Record Type ID NVARCSTR 10 0 0 no



FISC_PERIOD

Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)



Nullable

1 CALENDAR_HALF Calendar Half Year for this Fiscal Period NVARCSTR 2 0 0 yes

2 CALENDAR_MONTH_LONG

Calendar Month (January - December) for thisFiscal Period NVARCSTR 14 0 0 yes

3 CALENDAR_MONTH_NUMERIC

Calendar Month (Numeric) for this FiscalPeriod NVARCSTR 2 0 0 yes

4 CALENDAR_MONTH_SHORT

Calendar Month (JAN - DEC) for this fiscalPeriod NVARCSTR 3 0 0 yes

5 CALENDAR_QUARTER Calendar Quarter for this Fiscal Period INTEGER 4 0 0 yes

6 CALENDAR_YEAR Calendar Year for this fiscal period INTEGER 4 0 0 yes

7 CALENDAR_YEAR_HALF Calendar Year and Half NVARCSTR 12 0 0 yes

8 CALENDAR_YEAR_MONTH Calendar Year and Month NVARCSTR 12 0 0 yes

9 CALENDAR_YEAR_QUARTER Calendar Year and Quarter NVARCSTR 12 0 0 yes

10 END_DATE End Date for Fiscal Period DATETIME 24 0 9 yes

11 FISC_HALF Fiscal Half Year NVARCSTR 2 0 0 yes

12 FISC_MONTH Fiscal Month In SAP NVARCSTR 2 0 0 yes

13 FISC_PERIOD PK Fiscal Period in SAP INTEGER 4 0 0 no

14 FISC_QUARTER Fiscal Quarter NVARCSTR 2 0 0 yes

15 FISC_YEAR PK Fiscal Year in SAP INTEGER 4 0 0 no

16 FISC_YEAR_HALF Fiscal Year and Half NVARCSTR 12 0 0 yes



17 FISC_YEAR_MONTH Fiscal Year and Month NVARCSTR 12 0 0 yes

18 FISC_YEAR_PERIOD Fiscal Year and Period NVARCSTR 12 0 0 yes

19 FISC_YEAR_QUARTER Fiscal Year and Quarter NVARCSTR 12 0 0 yes

20 FISC_YR_VARIANT_ID PK Fiscal Year Variant in SAP NVARCSTR 2 0 0 no

21 FISC_YR_VARIANT_NAME

Name of Fiscal Year Variant (Table T009T inSAP) NVARCSTR 30 0 0 yes



24 SPECL_PERIOD_FLAG

Y = This is a special period in SAP, N = This isNOT a special period in SAP NVARCSTR 1 0 0 yes

25 START_DATE Start Date for Fiscal Period DATETIME 24 0 9 yes



FISC_PERIOD_STAGE

Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)



Nullable

1 CALENDAR_DATE PK Calendar Date - range from 01-Jan-1990through 31-Dec-2049 DATETIME 24 0 9 no

2 FISC_MONTH Fiscal Month in range 1 to 12 NVARCSTR 2 0 0 yes

3 FISC_PERIOD PK Fiscal Period in range 1 to 16 INTEGER 4 0 0 no

4 FISC_YEAR Fiscal Year in SAP INTEGER 4 0 0 yes

5 FISC_YR_VARIANT_ID PK Fiscal Year Variant in SAP NVARCSTR 2 0 0 no

6 FISC_YR_VARIANT_NAME

Name of Fiscal Year Variant (Table T009T inSAP) NVARCSTR 30 0 0 yes



9 REGISTRTN_PERIOD_COUNT Number of Regular Acctng Periods INTEGER 4 0 0 yes

10 SPECL_PERIOD_COUNT Number of Special Acctng Periods INTEGER 4 0 0 yes



FUNCTIONAL_AREA

TFKB-FKBER - Functional Area reference table



Nullable

1 FUNCTNL_AREA_DESCR Functional Area Description NVARCSTR 30 0 0 yes

2 FUNCTNL_AREA_FULL_NAME ID and Description NVARCSTR 120 0 0 yes

3 FUNCTNL_AREA_ID PK TFKB-FKBER - Functional Area Code NVARCSTR 16 0 0 no



FUNCTIONAL_AREA_HIER

Functional Area Hierarchy



Nullable

1 CHILD_DESCR Child node description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Child node id NVARCSTR 30 0 0 no

3 LEAF_FLAG PK Leaf node indicator (child node is leaf) NVARCSTR 1 0 0 no



6 PARENT_DESCR Parent node description NVARCSTR 64 0 0 yes

7 PARENT_ID PK Parent node id NVARCSTR 30 0 0 no

8 ROOT_FLAG PK Root node indicator (parent node is root) NVARCSTR 1 0 0 no



FUNCTIONAL_AREA_HIER_BAD

Functional Area Hierarchy - Invalid Records with Circular Dependency.



Nullable

1 CHILD_DESCR Child node description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Child node id NVARCSTR 30 0 0 no



5 LEAF_FLAG PK Leaf node indicator (child node is leaf) NVARCSTR 1 0 0 no



8 PARENT_DESCR Parent node description NVARCSTR 64 0 0 yes

9 PARENT_ID PK Parent node id NVARCSTR 30 0 0 no

10 ROOT_FLAG PK Root node indicator (parent node is root) NVARCSTR 1 0 0 no




Functional Area Hierarchy - Horizontal



Nullable

1 FUNCTNL_AREA_ID PK Funct. Area ID (Current Leaf) NVARCSTR 30 0 0 no

2 LEAF_LVL Leaf Level INTEGER 4 0 0 no



5 LVL_00_DESCR Funct. Area Level 0 Description NVARCSTR 64 0 0 yes

6 LVL_00_FULL_NAME Funct. Area Level 0 ID and Description NVARCSTR 120 0 0 yes

7 LVL_00_ID PK Funct. Area Level 0 ID NVARCSTR 30 0 0 no
















Functional Area Hierarchy - Vertical



Nullable

1 CHILD_DESCR Child Funct. Area Description NVARCSTR 64 0 0 yes

2 CHILD_FULL_NAME Child Funct. Area ID and Description NVARCSTR 120 0 0 yes

3 CHILD_ID PK Child Funct. Area ID NVARCSTR 30 0 0 no

4 DEPTH Hierarchy Depth INTEGER 4 0 0 yes

5 LEAF_FLAG Leaf Flag INTEGER 4 0 0 yes



8 PARENT_DESCR Parent Funct. Area Description NVARCSTR 64 0 0 yes

9 PARENT_FULL_NAME Parent Funct. Area ID and Description NVARCSTR 120 0 0 yes

10 PARENT_ID PK Parent Funct. Area ID NVARCSTR 30 0 0 no

11 ROOT_FLAG Root Flag INTEGER 4 0 0 yes



FUNCTIONAL_LOCATION

Functional Location Master from IFLOT/ILOA



Nullable

1 ABC_FLAG ILOA - ABCKZ - ABC indicator for technicalobject NVARCSTR 1 0 0 yes

2 ALLOW_INSTALL_FLAG

IFLOT-IEQUI - Installation of equipmentallowed at the functional location NVARCSTR 1 0 0 yes



5 BUS_AREA_DESCR Lookup on TGSBT-GTEXT for Sales Org Descr NVARCSTR 30 0 0 yes

6 BUS_AREA_ID ILOA-GSBER - Business area NVARCSTR 4 0 0 yes

7 CHANGE_BY_LOGIN IFLOT-AENAM - Name of the user who lastchanged the object NVARCSTR 12 0 0 yes

8 CHANGE_DATE IFLOT-AEDAT - Date on which the object waslast changed DATETIME 24 0 9 yes

9 CMPNY_CODE_ID ILOA-BUKRS - Company code NVARCSTR 4 0 0 yes

10 CMPNY_CODE_NAME T001.BUTXT -Lookup on Company CodeName NVARCSTR 25 0 0 yes

11 COST_CNTR_ID ILOA.KOSTL - Cost center NVARCSTR 10 0 0 yes

12 COST_CNTR_NAME CSKT.KTEXT - Lookup on Cost Center Name NVARCSTR 40 0 0 yes

13 CREATE_BY_LOGIN IFLOT-ERNAM - Name of the user whocreated the object NVARCSTR 12 0 0 yes

14 CREATE_DATE IFLOT-ERDAT - Date on which the object wascreated DATETIME 24 0 9 yes

15 CTRL_AREA_ID ILOA.KOKRS - Controlling area NVARCSTR 4 0 0 yes

16 CTRL_AREA_NAME Lookup on TKA01 for controlling area name NVARCSTR 25 0 0 yes



17 DAYS_IN_OPERATN Total number of days since the original startupas of LOAD_DATE (calcualted) DECIMAL 48 28 0 yes

18 DISTRIBTN_CHANNEL_DESCR Lookup on TVTWT-VTEXT for Sales Org Descr NVARCSTR 40 0 0 yes

19 DISTRIBTN_CHANNEL_ID ILOA.VTWEG - Distribution channel NVARCSTR 2 0 0 yes

20 DIVISION_DESCR Lookup on TVTWT-VTEXT for Sales Org Descr NVARCSTR 40 0 0 yes

21 DIVISION_ID ILOA.SPART - Division NVARCSTR 2 0 0 yes

22 FUNCTNL_LOCATN_CATEG_DESCR

T370F_T-TYPTX (lookup) - Functional locationdescription NVARCSTR 30 0 0 yes

23 FUNCTNL_LOCATN_CATEG_ID IFLOT-FLTYP - Functional location category NVARCSTR 1 0 0 yes

24 FUNCTNL_LOCATN_DESCR IFLOTX-PLTXT (lookup) NVARCSTR 40 0 0 yes

25 FUNCTNL_LOCATN_FULL_NAME

IFLOT-TPLNR - Functional location andIFLOTX-PLTXT (lookup) NVARCSTR 100 0 0 yes

26 FUNCTNL_LOCATN_ID PK IFLOT-TPLNR - Functional location NVARCSTR 30 0 0 no

27 FUNCTNL_LOCATN_ID_PAR IFLOT-TPLMA - Superior functional location NVARCSTR 30 0 0 yes

28 FUNCTNL_LOCATN_ID_REF IFLOT-TRPNR - Reference functional location NVARCSTR 30 0 0 yes



31 LOCATN_DESCR T499S-KTEXT (lookup) - Text (40 characters) NVARCSTR 40 0 0 yes

32 LOCATN_ID ILOA-STORT - Location of maintenance object NVARCSTR 10 0 0 yes

33 OBJ_ID IFLOT-OBJNR - Object number NVARCSTR 22 0 0 yes

34 PERSON_FULLNAME_RESP

PA0002.NACHN - Personnel Last Name +PA0002.VORNA - Personnel First Name NVARCSTR 85 0 0 yes



35 PERSON_ID_RESP IHPA-PARNR (lookup on VW function) NVARCSTR 12 0 0 yes

36 PLANNG_GRP_ID IFLOT.INGRP Maintenance planner group NVARCSTR 3 0 0 yes

37 PLANNG_GRP_NAME T024i-INNAM - Lookup on Name of themaintenance planning group NVARCSTR 18 0 0 yes

38 PLANT_ID ILOA-SWERK - Maintenance plant NVARCSTR 4 0 0 yes

39 PLANT_ID_PLAN ILOA-SWERK - Maintenance plant NVARCSTR 4 0 0 yes

40 PLANT_NAME T001W.NAME1 Name - Lookup on Plantname NVARCSTR 30 0 0 yes

41 PLANT_NAME_PLAN T001W.NAME1 Name - Lookup on Plantname for Planning Plant NVARCSTR 30 0 0 yes

42 PROJ_ELEM_DESCR PRPS.POST1 - Project Element Shortdescription (1st text line) NVARCSTR 40 0 0 yes

43 PROJ_ELEM_ID PRPS.POSID - Project Element (WBS)External ID NVARCSTR 24 0 0 yes

44 ROOM ILOA-MSGRP - Plant Room NVARCSTR 8 0 0 yes

45 SALES_ORG_DESCR Lookup on TVKOT-VTEXT for Sales Org Descr NVARCSTR 60 0 0 yes

46 SALES_ORG_ID ILOA.VKORG Sales organization NVARCSTR 4 0 0 yes

47 SECTION_ID ILOA-BEBER - Plant section NVARCSTR 3 0 0 yes

48 SECTION_PERSON_RESP

T357-FING (lookup) - Person responsible forcompany area NVARCSTR 14 0 0 yes

49 SECTION_PHONE T357-TELE (lookup) - Phone number ofperson responsible for company area NVARCSTR 12 0 0 yes

50 SINGLE_INSTALL_FLAG

IFLOT-EINZL - Single equipment installation atfunctional location NVARCSTR 1 0 0 yes

51 STARTUP_DATE IFLOT-DATAB - Start-up date of functionallocation DATETIME 24 0 9 yes




Functional Location Characteristic details from AUSTP/CABN/TCLA



Nullable

1 BUS_AREA_ID PK ILOA-GSBER - Business area NVARCSTR 4 0 0 yes

2 CHARACTSTC_DESCR









10 CMPNY_CODE_ID PK ILOA-BUKRS - Company code NVARCSTR 4 0 0 yes

11 COST_CNTR_ID PK ILOA.KOSTL - Cost center NVARCSTR 10 0 0 yes

12 CTRL_AREA_ID PK ILOA.KOKRS - Controlling area NVARCSTR 4 0 0 yes

13 DAYS_DIFF Calculated date difference for Date-relatedcaracteristics DECIMAL 48 22 7 yes

14 FUNCTNL_LOCATN_ID PK AUSP-OBJEK - Object number NVARCSTR 30 0 0 no





17 LOCATN_ID PK ILOA-STORT - Location of maintenance object NVARCSTR 10 0 0 yes

18 PERSON_ID_RESP PK IHPA-PARNR (lookup on VW function) NVARCSTR 12 0 0 yes

19 PLANNG_GRP_ID PK IFLOT.INGRP Maintenance planner group NVARCSTR 3 0 0 yes

20 PLANT_ID PK ILOA-SWERK - Maintenance plant NVARCSTR 4 0 0 yes

21 PLANT_ID_PLAN ILOA-SWERK - Maintenance plant NVARCSTR 4 0 0 yes

22 UOM_ID_VALUE PK CABN--MSEHI - Unit of measurement NVARCSTR 3 0 0 yes

23 VALID_FROM_DATE AUSP.ATFLV - Derived Date from and TimeFrom bucket DATETIME 24 0 9 yes











FUNCTIONAL_LOCATION_HIER

Parent/Child relationship between Functional Locations (from IFLOT/ILOA)



Nullable

1 CHILD_CATEG_DESCR


2 CHILD_CATEG_ID IFLOT-FLTYP - Functional location category NVARCSTR 1 0 0 yes

3 CHILD_DESCR IFLOTX-PLTXT (lookup) - Func LocationDescription NVARCSTR 40 0 0 yes

4 CHILD_FULL_NAMEIFLOT-TPLMA - Functionallocation+IFLOTX-PLTXT (lookup) - FuncLocation Description

NVARCSTR 55 0 0 yes

5 CHILD_ID PK IFLOT-TPLMA - functional location NVARCSTR 30 0 0 no



8 PARENT_CATEG_DESCR


9 PARENT_CATEG_ID IFLOT-FLTYP - Functional location category NVARCSTR 1 0 0 yes

10 PARENT_DESCR IFLOTX-PLTXT (lookup) - Func LocationDescription NVARCSTR 40 0 0 yes

11 PARENT_FULL_NAMEIFLOT-TPLMA - Functionallocation+IFLOTX-PLTXT (lookup) - FuncLocation Description

NVARCSTR 75 0 0 yes

12 PARENT_ID PK IFLOT-TPLMA - Superior functional location NVARCSTR 30 0 0 no




Horizontal flattening of Equipment and Classification hierarchy relationships



Nullable

1 FUNCTNL_LOCATN_ID PK IFLOT-TPLMA - functional location NVARCSTR 30 0 0 no

2 LEAF_LVL Leaf level DECIMAL 48 28 0 yes



5 LVL_00_DESCR IFLOTX-PLTXT (lookup) - Func LocationDescription NVARCSTR 40 0 0 yes

6 LVL_00_FULL_NAMEIFLOT-TPLMA - Functionallocation+IFLOTX-PLTXT (lookup) - FuncLocation Description

NVARCSTR 75 0 0 yes

7 LVL_00_ID IFLOT-TPLMA - Superior functional location NVARCSTR 30 0 0 yes



NVARCSTR 75 0 0 yes

10 LVL_01_ID IFLOT-TPLMA - functional location NVARCSTR 30 0 0 yes



NVARCSTR 75 0 0 yes




NVARCSTR 75 0 0 yes






NVARCSTR 75 0 0 yes




NVARCSTR 65 0 0 yes





Vertical flattening of Equipment and Classification hierarchy relationships



Nullable

1 CHILD_DESCR IFLOTX-PLTXT (lookup) - Func LocationDescription NVARCSTR 40 0 0 yes

2 CHILD_FULL_NAMEIFLOT-TPLMA - Functionallocation+IFLOTX-PLTXT (lookup) - FuncLocation Description

NVARCSTR 55 0 0 yes

3 CHILD_ID PK IFLOT-TPLMA - functional location NVARCSTR 30 0 0 no

4 DEPTH Depth of the decendent DECIMAL 48 28 0 yes

5 LEAF_FLAG Leaf flag (1 - means this is a leaf, 0 - means itis not a leaf) DECIMAL 48 28 0 yes



8 PARENT_DESCR IFLOTX-PLTXT (lookup) - Func LocationDescription NVARCSTR 40 0 0 yes

9 PARENT_FULL_NAMEIFLOT-TPLMA - Functionallocation+IFLOTX-PLTXT (lookup) - FuncLocation Description

NVARCSTR 75 0 0 yes

10 PARENT_ID PK IFLOT-TPLMA - Superior functional location NVARCSTR 30 0 0 no

11 ROOT_FLAG Root flag (1 - means this is a root, 0 - means itis not a root) DECIMAL 48 28 0 yes



INTERNAL_ORDER

AUFK - Internal Order Master



Nullable

1 ALLOCTN_GRP_CODE Allocation Group Code NVARCSTR 2 0 0 yes

2 APPLICTN_DATE AUFK-USER5 DATETIME 24 0 9 yes

3 BUS_AREA_ID AUFK-GSBER NVARCSTR 4 0 0 yes

4 BUS_AREA_NAME Business area description NVARCSTR 30 0 0 yes

5 CHANGE_DATE AUFK-AEDAT DATETIME 24 0 9 yes

6 CLOSE_DATE AUFK-IDAT3 DATETIME 24 0 9 yes

7 CMPNY_CODE_ID AUFK-BUKRS NVARCSTR 4 0 0 yes

8 CMPNY_CODE_NAME Name of the company code or company NVARCSTR 25 0 0 yes

9 COMPLT_DATE AUFK-IDAT2 DATETIME 24 0 9 yes

10 COST_CNTR_ID_ALLOCTN AUFK-KOSTL NVARCSTR 10 0 0 yes

11 COST_CNTR_ID_RESP AUFK-KOSTV NVARCSTR 10 0 0 yes

12 COST_CNTR_ID_RQST AUFK-AKSTL NVARCSTR 10 0 0 yes

13 COST_COLLECTR_KEY AUFK-CCKEY NVARCSTR 23 0 0 yes

14 COST_ELEM_ID_SETTLMNT AUFK-KSTAR NVARCSTR 10 0 0 yes

15 CREATE_DATE AUFK-ERDAT DATETIME 24 0 9 yes

16 CTRL_AREA_ID AUFK-KOKRS NVARCSTR 4 0 0 yes



17 CTRL_AREA_NAME Name of the controlling area NVARCSTR 25 0 0 yes

18 CURR_ID AUFK-WAERS NVARCSTR 5 0 0 yes

19 DELETE_CODE AUFK-LOEKZ NVARCSTR 1 0 0 yes

20 DEPARTMENT AUFK-USER6 NVARCSTR 15 0 0 yes

21 DOC_CATEG_DESCR DD07T - DDTEXT(lookup) - Order categorydescription NVARCSTR 60 0 0 yes

22 DOC_CATEG_ID AUFK-AUTYP NVARCSTR 2 0 0 yes

23 DOC_TYPE_DESCR T003P-TXT(lookup) - Short text NVARCSTR 40 0 0 yes

24 DOC_TYPE_ID AUFK-AUART NVARCSTR 4 0 0 yes

25 EQUITY_TYPE_CODE AUFK-ETYPE NVARCSTR 3 0 0 yes

26 EST_TRX_COST_ORDER AUFK-USER4 DECIMAL 48 11 2 yes

27 EXTERNAL_ORDER_NUM AUFK-AUFEX NVARCSTR 20 0 0 yes

28 GL_ACCT_ID_ALLOCTN AUFK-SAKNR NVARCSTR 10 0 0 yes

29 INTERNAL_ORDER_ID PK AUFK-AUFNR NVARCSTR 12 0 0 no

30 INTERNAL_ORDER_ID_REF AUFK-REFNR NVARCSTR 12 0 0 yes

31 INTERNAL_ORDER_ID_STATS AUFK-ASTNR NVARCSTR 1 0 0 yes

32 JOINT_VENTURE_CODE AUFK-VNAME NVARCSTR 6 0 0 yes





35 LOCATN_ID AUFK-STORT NVARCSTR 10 0 0 yes

36 OBJ_ID AUFK-OBJNR NVARCSTR 22 0 0 yes

37 ORDER_DESCR AUFK-KTEXT NVARCSTR 40 0 0 yes

38 ORDER_STATUS_ID AUFK-ASTKZ NVARCSTR 2 0 0 yes

39 OVERHEAD_CODE AUFK-ZSCHL NVARCSTR 6 0 0 yes

40 PLANNED_CLOSE_DATE AUFK-PDAT3 DATETIME 24 0 9 yes

41 PLANNED_COMPLT_DATE AUFK-PDAT2 DATETIME 24 0 9 yes

42 PLANNED_REL_DATE AUFK-PDAT1 DATETIME 24 0 9 yes

43 PLANT_ID AUFK-WERKS NVARCSTR 4 0 0 yes

44 PLANT_ID_LOCATN AUFK-SOWRK NVARCSTR 4 0 0 yes

45 PLANT_NAME Name NVARCSTR 30 0 0 yes

46 PROFIT_CNTR_ID AUFK-PRCTR NVARCSTR 10 0 0 yes

47 PROJ_ELEM_DESCR PS: Short description (1st text line) NVARCSTR 40 0 0 yes

48 PROJ_ELEM_ID AUFK-PSPEL lookup to PRPS.POSID - WBSelement External ID NVARCSTR 24 0 0 yes

49 RECOVERY_CODE AUFK-RECID NVARCSTR 2 0 0 yes

50 RELEASE_DATE AUFK-IDAT1 DATETIME 24 0 9 yes

51 RESP_PERSON AUFK-USER2 NVARCSTR 20 0 0 yes

52 SALES_LINE_ITEM_ID AUFK-KDPOS NVARCSTR 6 0 0 yes



53 SALES_ORDER_ID AUFK-KDAUF NVARCSTR 10 0 0 yes

54 STATUS_UPDT_DATE AUFK-STDAT DATETIME 24 0 9 yes

55 WORK_BEGIN_DATE AUFK-USER7 DATETIME 24 0 9 yes

56 WORK_END_DATE AUFK-USER8 DATETIME 24 0 9 yes

INTERNAL_ORDER_HIER

CCSS-AUFNR - Internal Order Hierarchy- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Internal Order Child Node Description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Internal Order Child Node ID NVARCSTR 12 0 0 no




6 PARENT_DESCR Internal Order Parent Node Descritpion NVARCSTR 64 0 0 yes

7 PARENT_ID PK Internal Order Parent Node ID NVARCSTR 12 0 0 no




INTERNAL_ORDER_HIER_BAD

CCSS-AUFNR Internal Order Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP



Nullable








8 PARENT_DESCR Internal Order Parent Node Descritpion NVARCSTR 64 0 0 yes






CCSS-AUFNR - Internal Order hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 INTERNAL_ORDER_ID PK Internal order current node ID NVARCSTR 12 0 0 no

2 LEAF_LVL Current Node level depth DECIMAL 48 28 0 no



5 LVL_00_DESCR Internal Order Root node Description NVARCSTR 64 0 0 yes

6 LVL_00_FULL_NAME Internal Order Number and Descritpion forLevel 0 NVARCSTR 120 0 0 yes

7 LVL_00_ID PK Internal Order Root node id NVARCSTR 12 0 0 no

8 LVL_01_DESCR Internal Order Level 1node Descritpion NVARCSTR 64 0 0 yes


10 LVL_01_ID PK Internal Order Level 1node ID NVARCSTR 12 0 0 no

11 LVL_02_DESCR Internal Order Level 2 node Descritpion NVARCSTR 64 0 0 yes


13 LVL_02_ID PK Internal Order Level 2 node ID NVARCSTR 12 0 0 no










CCSS-AUFNR - Internal Order hierarchy flattenned vertically - cannot have primary key due to possible duplicate entries in SAP



Nullable


2 CHILD_FULL_NAME Internal Order Number and Description ChildNode) NVARCSTR 120 0 0 yes


4 DEPTH Internal Order Child depth level DECIMAL 48 28 0 yes

5 LEAF_FLAG Node Is leaf DECIMAL 48 28 0 yes



8 PARENT_DESCR Internal Order Parent Node Description NVARCSTR 64 0 0 yes

9 PARENT_FULL_NAME Internal Order Number and Description (ParentNode) NVARCSTR 120 0 0 yes


11 ROOT_FLAG Node Is root DECIMAL 48 28 0 yes




Internal Order status name and descritpion from TKO04



Nullable

1 DOC_TYPE_DESCR T003P.TXT -Short text NVARCSTR 40 0 0 yes

2 DOC_TYPE_ID PK TKO04.ART -Order type NVARCSTR 4 0 0 no



5 ORDER_STATUS_DESCR TKO04.TXT -Text (40 characters) for status NVARCSTR 40 0 0 yes

6 ORDER_STATUS_ID PK TKO04.ASTNR -Order status NVARCSTR 2 0 0 no


Maintenance Activity Type attributes from T353I/T353I_T



Nullable



3 MAINT_ACTIVITY_DESCR

T353I_T-ILATX - Description of maintenanceactivity type NVARCSTR 30 0 0 yes

4 MAINT_ACTIVITY_TYPE_ID PK T353I_T-ILART - Maintenance activity type NVARCSTR 3 0 0 no




Attritues from T356, T356T, T356A_T (for service orders and notifications)



Nullable



3 NUM_DAYS_END T356.TAGEN - Relative End Date forTask/Notification in Days INTEGER 4 0 0 yes

4 NUM_DAYS_START T356.TAGBN -Relative Start Date forTask/Notification in Days INTEGER 4 0 0 yes

5 PRIORITY_DESCR T356_T.PRIOKX - Priority text NVARCSTR 20 0 0 yes

6 PRIORITY_ID PK T356.PRIOK -Priority NVARCSTR 1 0 0 no

7 PRIORITY_TYPE_DESCR T356A_T.ARTPRX -Priority Type Text NVARCSTR 20 0 0 yes

8 PRIORITY_TYPE_ID PK T356.ARTPR -Priority Type NVARCSTR 2 0 0 no

9 UOM_ID_END T356.EHTEN -Relative End Date Unit NVARCSTR 3 0 0 yes

10 UOM_ID_START T356.EHTBG -Relative Start Date Unit NVARCSTR 3 0 0 yes



MALFUNCTION_CAUSE

One of 3 pre-defined notification catalog objects - Malfunction Cause



Nullable

1 CAUSE_DESCR QPCT-KURZTEXT - Code short text for Cause NVARCSTR 40 0 0 yes

2 CAUSE_GRP_DESCR QPGT-KURZTEXT (lookup) - Group short text-Cause group NVARCSTR 40 0 0 yes

3 CAUSE_GRP_ID PK QPCT-CODEGRUPPE - Mulfuction causeCode group NVARCSTR 8 0 0 no

4 CAUSE_ID PK QPCT-CODE - Code for Cause NVARCSTR 4 0 0 no

5 LOAD_DATE Dateand time loaded into Rapid Mart DATETIME 24 0 9 yes


MALFUNCTION_DAMAGE

One of 3 pre-defined notification catalog objects - Malfunction Damage



Nullable

1 DAMAGE_DESCR QPCT-KURZTEXT - Code short text forDamage NVARCSTR 40 0 0 yes

2 DAMAGE_GRP_DESCR

QPGT-KURZTEXT (lookup) - Group short text-Damage group NVARCSTR 40 0 0 yes

3 DAMAGE_GRP_ID PK QPCT-CODEGRUPPE - Mulfuction DamageCode group NVARCSTR 8 0 0 no

4 DAMAGE_ID PK QPCT-CODE - Code for Damage NVARCSTR 4 0 0 no





MALFUNCTION_EFFECT

Description of malfunction effects from T357A_T



Nullable

1 EFFECT_DESCR T357A_T.AUSWKT - Text - Effect on works NVARCSTR 40 0 0 yes

2 EFFECT_ID PK T357A_T.AUSWK - Effect on operation NVARCSTR 1 0 0 no



MALFUNCTION_OBJ_PART

One of 3 pre-defined notification catalog objects - Mulfunctioning Object Part



Nullable



3 OBJ_PART_DESCR QPCT-KURZTEXT - Code short text for ObjectPart NVARCSTR 40 0 0 yes

4 OBJ_PART_GRP_DESCR

QPGT-KURZTEXT (lookup) - Group short text-Object Part group NVARCSTR 40 0 0 yes

5 OBJ_PART_GRP_ID PK QPCT-CODEGRUPPE - Mulfuction ObjectPart Code group NVARCSTR 8 0 0 no

6 OBJ_PART_ID PK QPCT-CODE - Code for Obect Part NVARCSTR 4 0 0 no



MATERIAL

MARA - Material Master



Nullable

1 BATCH_MGMT_FLAG XCHPF Batch management requirementindicator NVARCSTR 1 0 0 yes

2 CREATE_DATE ERSDA Date of creation DATETIME 24 0 9 yes

3 DELETE_CODE MARA-LVORM - Deletion flag for all materialdata (central) NVARCSTR 1 0 0 yes

4 DELETE_DATE LIQDT Deletion date DATETIME 24 0 9 yes

5 DIVISION_DESCR TSPAT.VTEXT Division Description NVARCSTR 20 0 0 yes

6 DIVISION_ID MARA.SPART Division NVARCSTR 2 0 0 yes

7 INDUSTRY_SECTOR_ID MARA.MBRSH Industry Sector ID NVARCSTR 1 0 0 yes

8 INDUSTRY_SECT_DESCR

Lookup description of MARA.MBRSH Industrysector NVARCSTR 25 0 0 yes



11 LOW_LVL_CODE MARA.DISST - Low level code NVARCSTR 3 0 0 yes

12 MATERIAL_ID PK MATNR Material number NVARCSTR 18 0 0 no

13 MIN_REM_SHELF_LIFE MARA.MHDRZ Minimum remaining shelf life INTEGER 4 0 0 yes

14 MODIFIED_DATE MARA.LAEDA Date of last change DATETIME 24 0 9 yes

15 MTRL_CATEG_DESCR Category Description NVARCSTR 60 0 0 yes

16 MTRL_CATEG_ID MARA.ATTYP Material category NVARCSTR 2 0 0 yes



17 MTRL_DESCR MAKTX Material description NVARCSTR 40 0 0 yes

18 MTRL_FULL_NAME Material ID and Material Description NVARCSTR 64 0 0 yes

19 MTRL_GRP_DESCR WGBEZ Description of material group NVARCSTR 20 0 0 yes

20 MTRL_GRP_ID MATKL Material group NVARCSTR 9 0 0 yes

21 MTRL_ID_MANUFCTR MARA.MFRPN - Manfuacturer Part (Material)Number NVARCSTR 40 0 0 yes

22 MTRL_TYPE_DESCR Lookup description of MARA.MTART in T134T NVARCSTR 25 0 0 yes

23 MTRL_TYPE_ID MTART Material type NVARCSTR 4 0 0 yes

24 PROD_HIER_ID PK PRDHA Product hierarchy NVARCSTR 18 0 0 yes

25 PURCH_STATUS_CODE General material status: Purchasing NVARCSTR 2 0 0 yes

26 REVISION_LVL Lookup AEOI.REVLV - Material revision level NVARCSTR 2 0 0 yes

27 SALES_STATUS_CODE MARA.MSTAV General material status: sales NVARCSTR 2 0 0 yes

28 TRANSPORT_GRP_CODE MARA.TRAGR Transportation group NVARCSTR 4 0 0 yes

29 TTL_SHELF_LIFE MARA.MHDHB Total shelf life in days INTEGER 4 0 0 yes

30 UOM_ID_BASE MEINS Base unit of measure NVARCSTR 3 0 0 yes

31 UOM_ID_ORDER MARA.BSTME Order unit (purchasing) NVARCSTR 3 0 0 yes

32 UOM_ID_VOLUME MARA.VOLEH Volume unit NVARCSTR 3 0 0 yes

33 UOM_ID_WEIGHT MARA.GEWEI Unit of weight NVARCSTR 3 0 0 yes

34 VALID_FROM_DATE MARA.DATAB Date valid from DATETIME 24 0 9 yes



35 VOLUME MARA.VOLUM Volume DECIMAL 48 13 3 yes

36 WEIGHT MARA.NTGEW Net weight DECIMAL 48 13 3 yes



MATERIAL_BY_PLANT

MARA and MARC Tables - Plant Level Material attributes



Nullable

1 ABC_CATEG_DESCR TMABCT.TMABC - lookup on ABC indicatordescritpion NVARCSTR 30 0 0 yes

2 ABC_CATEG_ID MARC.MAABC ABC indicator NVARCSTR 1 0 0 yes

3 BASE_TO_PRODUCTN_MULTIPLR

Lookup MARM.UMREZ Factor to convert fromBASE UOM to PROD UOM. (PROD_QTY =MENGE / UMREZ)

INTEGER 4 0 0 yes

4 BATCH_MGMT_FLAG Lookup MARC.XCHAR Batch managementindicator (internal) NVARCSTR 1 0 0 yes

5 BATCH_MGMT_REQ_FLAG

MARC.XCHPF Batch managementrequirement indicator NVARCSTR 1 0 0 yes

6 BULK_MTRL_FLAG MARC.SCHGT Indicator: bulk material NVARCSTR 1 0 0 yes

7 COUNTRY_ID_ORIGIN MARC.HERKL Materials country of origin NVARCSTR 3 0 0 yes

8 COUNTRY_NAME_ORIGIN

Lookup description onT005T.LANDX forCountry name NVARCSTR 15 0 0 yes

9 DAYS_PLAN_DELIV MARC.PLIFZ - Planned delivery time in days INTEGER 4 0 0 yes

10 DAYS_PLAN_GRMARC.WEBAZ - Planned goods receiptprocessing time in days - includes inspectiontime

INTEGER 4 0 0 yes

11 DAYS_REPLENISHMARC.WZEIT - Total replenishment lead timein days - in house production time and/ordelivery lead tim

INTEGER 4 0 0 yes

12 DAYS_TO_PRODUCE MARC.DZEIT - In-house production time INTEGER 4 0 0 yes

13 DELETE_FLAG MARC.LVORM - Plant level material deletionindicator NVARCSTR 1 0 0 yes

14 DIVISION_DESCR TSPAT.VTEXT Division Description NVARCSTR 20 0 0 yes

15 DIVISION_ID MARA.SPART Division NVARCSTR 2 0 0 yes

16 INDUSTRY_SECTOR_DESCR

Lookup description of MARA.MBRSH Industrysector NVARCSTR 25 0 0 yes



17 INDUSTRY_SECTOR_ID MARA.MBRSH Industry Sector ID NVARCSTR 1 0 0 yes

18 LOAD_DATE Date and time loaded into RapidMart DATETIME 24 0 9 yes

19 LOAD_TIME Time loaded into RapidMart NVARCSTR 8 0 0 yes

20 MATERIAL_ID PK MARC.MATNR Material number NVARCSTR 18 0 0 no

21 MRP_CTRLLER_ID MARC.DISPO MRP controller NVARCSTR 3 0 0 yes

22 MRP_CTRLLER_NAME

T024D.DSNAM - Name of MRP controller -lookup NVARCSTR 18 0 0 yes

23 MRP_TYPE_DESCR T438T.DIBEZ -Long MRP Type Descriptionfrom T438T NVARCSTR 30 0 0 yes

24 MRP_TYPE_ID MARC.DISMM MRP type code NVARCSTR 2 0 0 yes

25 MTRL_CATEG_DESCR lookup on ATTYP domain in DD07T NVARCSTR 60 0 0 yes

26 MTRL_CATEG_ID MARA.ATTYP Material category NVARCSTR 2 0 0 yes

27 MTRL_DESCR MAKT.MAKTX -Material description NVARCSTR 40 0 0 yes

28 MTRL_FULL_NAME Material ID and Material Description NVARCSTR 64 0 0 yes

29 MTRL_GRP_DESCR WGBEZ Description of material group NVARCSTR 20 0 0 yes

30 MTRL_GRP_ID MATKL Material group NVARCSTR 9 0 0 yes

31 MTRL_TYPE_DESCR Lookup description of MARA.MTART in T134T NVARCSTR 25 0 0 yes

32 MTRL_TYPE_ID MTART Material type NVARCSTR 4 0 0 yes

33 PLANT_FULL_NAME Plant ID and Plant Name NVARCSTR 40 0 0 yes

34 PLANT_ID PK MARC.WERKS Plant NVARCSTR 4 0 0 no



35 PLANT_NAME T001W.NAME1 -Name NVARCSTR 30 0 0 yes

36 PROCUREMNT_TYPE_DESCR

Lookup DD07T - Procurement type - BESKZdomain NVARCSTR 60 0 0 yes

37 PROCUREMNT_TYPE_ID MARC.BESKZ - Procurement type code NVARCSTR 20 0 0 yes

38 PROFIT_CNTR_ID MARC.PRCTR Profit center NVARCSTR 10 0 0 yes

39 PURCH_GRP_DESCR Lookup description of T024.EKNAM - PurchaseGroup Name NVARCSTR 30 0 0 yes

40 PURCH_GRP_ID MARC.EKGRP Purchasing group NVARCSTR 3 0 0 yes

41 QTY_REORDER_POINT MARC.MINBE Reorder point DECIMAL 48 13 3 yes

42 QTY_SAFETY_STOCK MARC.EISBE Safety stock DECIMAL 48 13 3 yes

43 QUALITY_INSPECT_FLAG

MARC.INSMK - Quality inspection indicator - Xis yes NVARCSTR 1 0 0 yes

44 SPECL_PROCUREMNT_TYPE_DESCR

Lookup description of MARC.SOBSL in T460T-Special procurement type NVARCSTR 30 0 0 yes

45 SPECL_PROCUREMNT_TYPE_ID MARC.SOBSL - Special procurement type NVARCSTR 2 0 0 yes

46 SUPPLY_SRC_DESCR Lookup description on TMBWT.BWSCB forsupply source description NVARCSTR 40 0 0 yes

47 SUPPLY_SRC_ID MARC.BWSCL Source of supply IS-R NVARCSTR 1 0 0 yes

48 UOM_CODE_BASE Lookup MARC.AUSME in T006A to get BaseUnit External Code NVARCSTR 3 0 0 yes

49 UOM_CODE_ISSUE Lookup MARC.AUSME in T006A to get Unit ofIssue Long Description NVARCSTR 3 0 0 yes

50 UOM_CODE_PROD Lookup MARC.FRTME in T006A to getProduction UOM External code NVARCSTR 3 0 0 yes

51 UOM_ID_BASE MEINS Base unit of measure NVARCSTR 3 0 0 yes

52 UOM_ID_ISSUE MARC.AUSME - Unit of measure for goodsissue NVARCSTR 3 0 0 yes



53 UOM_ID_PROD MARC.FRTME Production unit of measure NVARCSTR 3 0 0 yes



MTBR_MTTR_FACT

Value added table to calculate MTTR (mean time to repare), MTBR (mean time between repairs)



Nullable

1 BUS_AREA_ID PK TGSB-GSBER-Business area NVARCSTR 4 0 0 yes

2 CMPNY_CODE_ID PK T001K.BURKS - lookup on Company Code ID NVARCSTR 4 0 0 yes

3 COMPLT_DATEQMEL-QMDAB - Date for completion ofnotification + QMEL-QMZAB - Completion timeof notification

DATETIME 24 0 9 yes

4 COST_CNTR_ID PK ILOA-KOSTL (lookup) - Cost Center NVARCSTR 10 0 0 yes

5 CTRL_AREA_ID PK ILOA-KOKRS (lookup) - Controlling Area NVARCSTR 4 0 0 yes

6 DAYS_DOWNTIME Calcualted Days of downtime (as Malf end -malf start) DECIMAL 48 22 7 yes

7 DAYS_UPTIME Calulcated Days of uptime: Prev Malf end date- malf start date DECIMAL 48 22 7 yes

8 DOC_CATEG_ID TQ80.QMTYP - Notification Category ID NVARCSTR 2 0 0 yes

9 DOC_TYPE_ID PK QMEL-QMART - Notification type NVARCSTR 2 0 0 yes

10 EFFECT_ID PK QMIH.AUSWK - Effect on operation NVARCSTR 1 0 0 yes

11 EQUIPMNT_ID PK QMIH-EQUNR - Equipment number NVARCSTR 18 0 0 yes

12 FUNCTNL_LOCATN_ID PK ILOA-TPLNR (lookup) - Functional location NVARCSTR 30 0 0 yes

13 HOURS_DOWNTIME Calcualted hours of downtime (as Malf end -malf start) DECIMAL 48 22 7 yes

14 HOURS_UPTIME Calulcated hours of uptime: Prev Malf end date- malf start date DECIMAL 48 22 7 yes

15 INTERNAL_ORDER_ID PK QMEL-AUFNR - Order Number NVARCSTR 12 0 0 yes





18 MALFNCTN_END_DATE

QMIH-AUSBS - End of malfunction (date) +QMIH-AUZTV - Start of malfunction (time) DATETIME 24 0 9 yes

19 MALFNCTN_END_DATE_PREV

Date and time of the previous malfunction enddate (calculated as lookup) DATETIME 24 0 9 yes

20 MALFNCTN_START_DATE

QMIH-AUSVN - Start of malfunction (date) +QMIH-AUSBS - End of malfunction (date) DATETIME 24 0 9 yes

21 MALFNCTN_START_DATE_NEXT

Date and time of the next malfunction start date(calculated as lookup) DATETIME 24 0 9 yes

22 MATERIAL_ID QMFE.MATNR - Material NVARCSTR 18 0 0 yes

23 MINS_DOWNTIME Calcualted minutes of downtime (as Malf end -malf start) DECIMAL 48 22 7 yes

24 MINS_UPTIME Calulcated mins of uptime: Prev Malf end date- malf start date DECIMAL 48 22 7 yes

25 NOTIFICTN_DATE PK QMEL-QMDAT - Date of notification (withouttimestamp) DATETIME 24 0 9 yes

26 NOTIFICTN_DATETIME

QMEL.QMDAT and QMEL.MZEIT - NotificationDate and Time DATETIME 24 0 9 yes

27 NOTIFICTN_DESCR QMEL-QMTXT - Short text NVARCSTR 40 0 0 yes

28 NOTIFICTN_ID QMIH-QMNUM - Notification number NVARCSTR 12 0 0 yes

29 OBJ_FLAG EQ for Equipment, FL for Functional Location NVARCSTR 2 0 0 yes

30 OBJ_ID PK Functional Location of Equipment ID NVARCSTR 30 0 0 no

31 PERSON_ID_RESP PK IHPA-PARNR - Person responsible ID NVARCSTR 12 0 0 yes

32 PLANNG_GRP_ID PK QMIH-INGRP - Maintenance planner group NVARCSTR 3 0 0 yes

33 PLANT_ID PK ILOA-SWERK (lookup) - Maintenance Plant NVARCSTR 4 0 0 no

34 PLANT_ID_PLAN QMIH-IWERK - Planning plant NVARCSTR 4 0 0 yes



35 PLANT_ID_WRKCNTR CRHD-WERKS (lookup) - Work Center Plant NVARCSTR 4 0 0 yes

36 PRIORITY_ID PK QMEL.PRIOK - Priority NVARCSTR 1 0 0 yes

37 PRIORITY_TYPE_ID PK QMEL.ARTPR - Priority type NVARCSTR 2 0 0 yes

38 SEQ_NUM PK Group Sequential number (generated) DECIMAL 48 28 0 no

39 STARTUP_DATE Object startup date and time DATETIME 24 0 9 yes

40 WORK_CNTR_ID PK CRHD-ARBPL (lookup) - Work Center uniquename NVARCSTR 8 0 0 yes



MTBR_MTTR_STAGE

Staging table for Uptime/Downtime measure calculations



Nullable

1 BUS_AREA_ID TGSB-GSBER-Business area NVARCSTR 4 0 0 yes

2 CMPNY_CODE_ID T001K.BURKS - lookup on Company Code ID NVARCSTR 4 0 0 yes


DATETIME 24 0 9 yes

4 COST_CNTR_ID ILOA-KOSTL (lookup) - Cost Center NVARCSTR 10 0 0 yes

5 CTRL_AREA_ID ILOA-KOKRS (lookup) - Controlling Area NVARCSTR 4 0 0 yes


7 DOC_TYPE_ID QMEL-QMART - Notification type NVARCSTR 2 0 0 yes

8 EFFECT_ID QMIH.AUSWK - Effect on operation NVARCSTR 1 0 0 yes

9 INTERNAL_ORDER_ID QMEL-AUFNR - Order Number NVARCSTR 12 0 0 yes








15 NOTIFICTN_DATE QMEL-QMDAT - Date of notification (Notimestamp) DATETIME 24 0 9 yes


QMEL-QMDAT - Date of notification +QMEL-MZEIT - Notification time DATETIME 24 0 9 yes




18 NOTIFICTN_ID QMIH-QMNUM - Notification number NVARCSTR 12 0 0 yes

19 OBJ_FLAG EQ for Equipment, FL for Functional Location NVARCSTR 2 0 0 yes

20 OBJ_ID PK Functional Location of Equipment ID NVARCSTR 30 0 0 no

21 PERSON_ID_RESP IHPA-PARNR - Person responsible ID NVARCSTR 12 0 0 yes

22 PLANNG_GRP_ID QMIH-INGRP - Maintenance planner group NVARCSTR 3 0 0 yes

23 PLANT_ID PK ILOA-SWERK (lookup) - Maintenance Plant NVARCSTR 4 0 0 no



26 PRIORITY_ID QMEL.PRIOK - Priority NVARCSTR 1 0 0 yes

27 PRIORITY_TYPE_ID QMEL.ARTPR - Priority type NVARCSTR 2 0 0 yes

28 SEQ_NUM PK Group Sequential number (generated) DECIMAL 48 28 0 no

29 STARTUP_DATE Lookup - Equipment of Functional Locationoriginal startup date and time DATETIME 24 0 9 yes

30 WORK_CNTR_ID CRHD-ARBPL (lookup) - Work Center uniquename NVARCSTR 8 0 0 yes



NOTIFICATION

Notification header from tables QMEL and QMIH.



Nullable

1 ASSEMBLY_ID QMIH-BAUTL - Assembly NVARCSTR 18 0 0 yes

2 BATCH_ID QMEL.CHARG - Batch number NVARCSTR 10 0 0 yes

3 BREAKDOWN_FLAG EQIH-MSAUS - Breakdown indicator. Set to 1if there is a breakdown DECIMAL 48 28 0 yes

4 BUS_AREA_DESCR TGSBT.GTEXT - Business Area Name (lookupon ILOA.GSBER) NVARCSTR 30 0 0 yes

5 BUS_AREA_ID ILOA.GSBER - Business area lookup NVARCSTR 4 0 0 yes

6 CHANGE_BY_LOGIN QMEL -AENAM - Name of accounting clerkwho changed record NVARCSTR 12 0 0 yes

7 CHANGE_DATE QMFE-AEDAT - Last changed on DATETIME 24 0 9 yes

8 CMPNY_CODE_DESCR

T001.BUTXT Company Code Name (lookup onILOA-BUKRS) NVARCSTR 25 0 0 yes

9 CMPNY_CODE_ID ILOA-BUKRS (lookup) - Company Code NVARCSTR 4 0 0 yes

10 COMPLT_DATE QMEL-QMDAB - Date for completion ofnotification DATETIME 24 0 9 yes

11 COST_CNTR_DESCR CSKT.KTEXT - Cost Center Name (lookup onILOA-KOSTL) NVARCSTR 30 0 0 yes

12 COST_CNTR_ID ILOA-KOSTL (lookup) - Cost Center NVARCSTR 10 0 0 yes

13 CREATE_BY_LOGIN QMEL-ERNAM - Name of person who createdobject NVARCSTR 12 0 0 yes

14 CREATE_DATE QMFE-ERDAT - Date on which the record wascreated DATETIME 24 0 9 yes

15 CTRL_AREA_DESCR TKA01.BEZEI - Controlling area name (lookupon ILOA-KOKRS) NVARCSTR 25 0 0 yes

16 CTRL_AREA_ID ILOA-KOKRS (lookup) - Controlling Area NVARCSTR 4 0 0 yes



17 DELETE_FLAG QMEL.KZLOESCH - Delete Data Record ("X" =Notification marked for Deletion) NVARCSTR 1 0 0 yes

18 DOC_CATEG_DESCR TQ8T_T.QMTTX - Notification Category Descr.(lookup on TQ80.QMTYP) NVARCSTR 20 0 0 yes

19 DOC_CATEG_ID TQ80.QMTYP - Notification Category NVARCSTR 2 0 0 yes

20 DOC_TYPE_DESCR TQ80_T.QMARTX - Notification Type Descr.(lookup on QMEL-QMART) NVARCSTR 20 0 0 yes

21 DOC_TYPE_ID QMEL-QMART - Notification type NVARCSTR 2 0 0 yes

22 EFFECT_ID QMIH.AUSWK - Effect on operation NVARCSTR 1 0 0 yes

23 EQUIPMNT_DESCR EQKT.EQKTX - Equipment Description(lookup on QMIH-EQUNR) NVARCSTR 40 0 0 yes

24 EQUIPMNT_ID QMIH-EQUNR - Equipment number NVARCSTR 18 0 0 yes

25 FUNCTNL_LOCATN_DESCR

IFLOTX.PLTXT - Functional location Descr.(lookup on ILOA.TPLNR) NVARCSTR 40 0 0 yes

26 FUNCTNL_LOCATN_ID ILOA-TPLNR (lookup) - Functional location NVARCSTR 30 0 0 yes

27 INTERNAL_ORDER_ID QMEL-AUFNR - Order Number NVARCSTR 12 0 0 yes



30 LOCATN_DESCR T499S.KTEXT - Location Description of Main.Object. (lookup on ILOA-STORT) NVARCSTR 40 0 0 yes

31 LOCATN_ID ILOA-STORT - Location of maintenance object(lookup) NVARCSTR 10 0 0 yes

32 MALFNCTN_END_DATE QMIH-AUSBS - End of malfunction (date) DATETIME 24 0 9 yes

33 MALFNCTN_START_DATE QMIH-AUSVN - Start of malfunction (date) DATETIME 24 0 9 yes

34 MATERIAL_ID QMEL.MATNR - Material number NVARCSTR 18 0 0 yes



35 MTRL_DESCR MAKT.MAKTX - Material Desc.r (lookup onQMEL.MATNR) NVARCSTR 40 0 0 yes

36 MTRL_GRP_DESCR T023T.WGBEZ - Material Group Descr.(lookup on QMEL.MATKL) NVARCSTR 20 0 0 yes

37 MTRL_GRP_ID QMEL.MATKL - Material group NVARCSTR 9 0 0 yes

38 NOTIFICTN_DATE QMEL-QMDAT - Date of notification DATETIME 24 0 9 yes


40 NOTIFICTN_ID PK QMIH-QMNUM - Notification number NVARCSTR 12 0 0 no

41 NOTIFICTN_ID_REF QMEL.QWRNUM - Reference NotificationNumber NVARCSTR 12 0 0 yes

42 OBJ_ID QMEL-OBJNR - Object number for statusmanagement NVARCSTR 22 0 0 yes

43 PERSON_ID_RESP IHPA-PARNR - Person responsible ID NVARCSTR 12 0 0 yes

44 PERSON_NAME_RESP

PA0002.NACHN, PA0002.VORNA - Personresponsible Last Name, First Name NVARCSTR 82 0 0 yes

45 PLANNG_GRP_ID QMIH-INGRP - Maintenance planner group NVARCSTR 3 0 0 yes

46 PLANNG_GRP_NAME T024I.INNAM - Maintenance planner groupName (lookup on QMIH.INGRP) NVARCSTR 18 0 0 yes

47 PLANT_ID ILOA-SWERK (lookup) - Maintenance Plant NVARCSTR 4 0 0 yes



50 PLANT_NAME T001W.NAME1 - Maint. Plant Descr. (lookupon ILOA-SWERK) NVARCSTR 30 0 0 yes

51 PLANT_NAME_PLAN T001W.NAME1 - Plant Name (lookup onQMIH.IWERK) NVARCSTR 30 0 0 yes

52 PLANT_NAME_WRKCNTR

T001W.NAME1 - Plant Name (lookup onCRHD.WERKS) NVARCSTR 30 0 0 yes



53 PRIORITY_DESCR T356_T.PRIOKX - Priority Descr. (lookup onQMEL.PRIOK) NVARCSTR 20 0 0 yes

54 PRIORITY_ID QMEL.PRIOK - Priority NVARCSTR 1 0 0 yes

55 PRIORITY_TYPE_DESCR

T356A_T.ARTPRX - Priority Type Descr.(lookup on QMEL.ARTPR) NVARCSTR 20 0 0 yes

56 PRIORITY_TYPE_ID QMEL.ARTPR - Priority type NVARCSTR 2 0 0 yes

57 QTY_DOWNTIME QMIH-AUSZT - Downtime DECIMAL 48 22 7 yes

58 REFERENCE_DATE QMEL.BEZDT- Notification reference date DATETIME 24 0 9 yes

59 REPORTED_BY_LOGIN

QMEL-QMNAM - Name of person reportingnotification NVARCSTR 12 0 0 yes

60 REQ_END_DATE QMEL-LTRMN - Required end date DATETIME 24 0 9 yes

61 REQ_START_DATE QMEL-STRMN - Required start date DATETIME 24 0 9 yes

62 UOM_CODE_DOWNTIME

T006A.MSEH3 - Downtime Unit of Meas.Code (lookup on QMIH-MAUEH) NVARCSTR 3 0 0 yes

63 UOM_DESCR_DOWNTIME

T006A.MSEH3 - Downtime Unit of Meas.Description (lookup on QMIH-MAUEH) NVARCSTR 30 0 0 yes

64 UOM_ID_DOWNTIME QMIH-MAUEH - Downtime unit NVARCSTR 3 0 0 yes

65 WORK_CNTR_DESCR CRTX.KTEXT - Work Center Description(lookup) NVARCSTR 40 0 0 yes

66 WORK_CNTR_ID QMEL.ARBPL - Object ID of PM work center NVARCSTR 8 0 0 yes



NOTIFICATION_FACT

Load NOTIFICATION_FACT from QMFE, QMIH, QMEL (Quality notifiction at line item level)



Nullable

1 ASSEMBLY_ID QMFE-BAUTL/QMIH.BAUTL - Assembly NVARCSTR 18 0 0 yes

2 BREAKDOWN_FLAG EQIH-MSAUS - Breakdown indicator. Set to 1if there is a breakdown DECIMAL 48 28 0 yes

3 BUS_AREA_ID PK TGSB-GSBER-Business area NVARCSTR 4 0 0 yes

4 CAUSE_GRP_ID PK QMUR-URGRP - Code group - Causes NVARCSTR 8 0 0 yes

5 CAUSE_ID PK QMUR-URCOD - Cause code NVARCSTR 4 0 0 yes

6 CHANGE_BY_LOGIN QMEL -AENAM - Name of accounting clerkwho changed record NVARCSTR 12 0 0 yes

7 CHANGE_DATE QMFE-AEDAT - Last changed on DATETIME 24 0 9 yes

8 CHANGE_DATE_HDR QMEL.AEDAT - Date of last change - headerlevel DATETIME 24 0 9 yes

9 CMPNY_CODE_ID PK T001K.BURKS - lookup on Company Code ID NVARCSTR 4 0 0 yes


DATETIME 24 0 9 yes

11 COMPLT_FLAGJEST-STAT (lookup) - NOCO notificationcompleted status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes

12 COST_CNTR_ID PK ILOA-KOSTL (lookup) - Cost Center NVARCSTR 10 0 0 yes

13 CREATE_BY_LOGIN QMEL-ERNAM - Name of person who createdobject NVARCSTR 12 0 0 yes

14 CREATE_DATE PK QMFE-ERDAT - Date on which the record wascreated DATETIME 24 0 9 yes

15 CREATE_DATE_HDR QMEL.ERDAT - Creation Date - header level DATETIME 24 0 9 yes

16 CTRL_AREA_ID PK ILOA-KOKRS (lookup) - Controlling Area NVARCSTR 4 0 0 yes



17 DAMAGE_GRP_ID PK QMFE-FEGRP - Code group - Problem NVARCSTR 8 0 0 yes

18 DAMAGE_ID PK QMFE-FECOD - Problem NVARCSTR 4 0 0 yes

19 DAYS_COMPLT Number of Days to elimiate malfunction(calcualted) DECIMAL 48 22 7 yes

20 DAYS_DOWNTIME Number of mulfunction days (calcualted) DECIMAL 48 22 7 yes

21 DAYS_REQ Number of Requied days to fix malfuction(calcualted) DECIMAL 48 22 7 yes


23 DOC_TYPE_ID PK QMEL-QMART - Notification type NVARCSTR 2 0 0 yes

24 EFFECT_ID PK QMIH.AUSWK - Effect on operation NVARCSTR 1 0 0 yes

25 EQUIPMNT_ID PK QMIH-EQUNR - Equipment number NVARCSTR 18 0 0 yes

26 EQUIPMNT_ID_AFFECT QMIH-BEQUI - Equipment affected NVARCSTR 18 0 0 yes

27 FUNCTNL_LOCATN_ID PK ILOA-TPLNR (lookup) - Functional location NVARCSTR 30 0 0 yes

28 FUNCTNL_LOCATN_ID_AFFECT QMIH-BTPLN - Functional location affected NVARCSTR 30 0 0 yes

29 HOURS_COMPLT Number of Hours to elimiate malfunction(calcualted) DECIMAL 48 22 7 yes

30 HOURS_DOWNTIME Number of mulfunction Hours (calcualted) DECIMAL 48 22 7 yes

31 HOURS_REQ Number of Requied Hours to fix malfuction(calcualted) DECIMAL 48 22 7 yes

32 INTERNAL_ORDER_ID PK QMEL-AUFNR - Order Number NVARCSTR 12 0 0 yes

33 IN_PROGRESS_FLAGJEST-STAT (lookup) - NOPR notification isprogress status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes

34 ITEM_DELETE_FLAG QMFE-KZLOESCH - Indicator: delete datarecord. Set to 1 if an item is deleted DECIMAL 48 28 0 yes





37 LOCATN_ID PK ILOA-STORT - Location of maintenance object(lookup) NVARCSTR 10 0 0 yes






41 MINS_COMPLT Number of Hours to elimiate malfunction(calcualted) DECIMAL 48 22 7 yes

42 MINS_DOWNTIME Number of mulfunction Minutes (calcualted) DECIMAL 48 22 7 yes

43 MINS_REQ Number of Requied Minutes to fix malfuction(calcualted) DECIMAL 48 22 7 yes

44 NOTIFICTN_DATE QMEL-QMDAT - Date of notification (withouttimestamp) DATETIME 24 0 9 yes


QMEL.QMDAT and QMEL.MZEIT - NotificationDate and Time DATETIME 24 0 9 yes

46 NOTIFICTN_DELETE_FLAG

JEST-STAT (lookup) - DLFL notificationcompleted status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes


48 NOTIFICTN_ID PK QMIH-QMNUM - Notification number NVARCSTR 12 0 0 no

49 NOTIFICTN_LINE_DESCR QMFE-FETXT - Notification item short text NVARCSTR 40 0 0 yes

50 NOTIFICTN_LINE_ITEM_ID PK QMFE-FENUM - Item number in item record NVARCSTR 4 0 0 no

51 OBJ_ID QMEL-OBJNR - Object number for statusmanagement NVARCSTR 22 0 0 yes

52 OBJ_ID_CLASS Concatenation of QMNUM and RENUM forclassification NVARCSTR 16 0 0 yes



53 OBJ_PART_GRP_ID PK QMFE-OTGRP - Code group - object parts NVARCSTR 8 0 0 yes

54 OBJ_PART_ID PK QMFE-OTEIL - Object part NVARCSTR 4 0 0 yes

55 OUTSTANDNG_FLAGJEST-STAT (lookup) - OSNO outstandingnotification status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes

56 PERSON_ID_RESP PK IHPA-PARNR - Person responsible ID NVARCSTR 12 0 0 yes

57 PLANNG_GRP_ID PK QMIH-INGRP - Maintenance planner group NVARCSTR 3 0 0 yes

58 PLANT_ID PK ILOA-SWERK (lookup) - Maintenance Plant NVARCSTR 4 0 0 yes



61 POSTPONE_FLAGJEST-STAT(lookup) - NOPO notificationpostponed status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes

62 PRIORITY_ID PK QMEL.PRIOK - Priority NVARCSTR 1 0 0 yes

63 PRIORITY_TYPE_ID PK QMEL.ARTPR - Priority type NVARCSTR 2 0 0 yes

64 QTY_DOWNTIME QMIH-AUSZT - Downtime DECIMAL 48 22 7 yes

65 REFERENCE_DATE QMEL.BEZDT- Notification reference date +QMEL.BEZUR - Notification reference time DATETIME 24 0 9 yes

66 REPORTED_BY_LOGIN

QMEL-QMNAM - Name of person reportingnotification NVARCSTR 12 0 0 yes

67 REQ_END_DATE QMEL-LTRMN - Required end date +QMEL-LTRUR - Required end date-time DATETIME 24 0 9 yes

68 REQ_START_DATE QMEL-STRMN - Required start date +QMEL-STRUR - Required start (time) DATETIME 24 0 9 yes

69 UOM_ID_DOWNTIME PK QMIH-MAUEH - Downtime unit NVARCSTR 3 0 0 yes




OBJECT_CLASS

DD07T - Object Class reference dimension



Nullable



3 OBJ_CLASS_DESCR Object Class Domain Descritpion NVARCSTR 60 0 0 yes

4 OBJ_CLASS_ID PK Object Class Domain ID NVARCSTR 10 0 0 no

OBJECT_TYPE

DD07T - Object Type reference dimension



Nullable

1 DIM_SRC_ID PKDimension Source. This is a combineddimension combining different varieties of"object type" from different sources. This fieldidentifies the source of "object type"

NVARCSTR 10 0 0 no



4 OBJ_TYPE_DESCR Description of Object Type NVARCSTR 75 0 0 yes

5 OBJ_TYPE_ID PK Object Type domain value ID NVARCSTR 10 0 0 no




Key suitability required for carrying out the operation (for example, welding certificate or NC programming course) - from T423T



Nullable



3 PLANT_ID PK T423T.WERKS -Plant NVARCSTR 4 0 0 no


5 SUITABILITY_DESCR T423T.TXT -Text for suitability NVARCSTR 30 0 0 yes

6 SUITABILITY_ID PK T423T.QUALF -Suitability NVARCSTR 2 0 0 no



PLANNING_GROUP

T024I - Planner group dimension



Nullable

1 CMPNY_CODE_ID T001K.BURKS - Company Code ID NVARCSTR 4 0 0 yes

2 CMPNY_CODE_NAME T001. BUTXT -Lookup on Company CodeName NVARCSTR 25 0 0 yes



5 PLANNG_GRP_ID PK T024I-INGRP - Maintenance planner group NVARCSTR 3 0 0 no

6 PLANNG_GRP_NAME T024i-INNAM - Name of the maintenanceplanning group NVARCSTR 18 0 0 yes

7 PLANNG_GRP_PHONE

T024I-INTEL - Maintenance planning groupphone number NVARCSTR 12 0 0 yes

8 PLANT_ID PK T024I-IWERK - Planning plant NVARCSTR 4 0 0 no

9 PLANT_ID_MAINT T001W.IWERK -Maintenance Planning Plant NVARCSTR 4 0 0 yes


11 PLANT_NAME_MAINT T001W.NAME1 Maintenance Plant Name NVARCSTR 30 0 0 yes

12 PURCH_ORG_DESCR T024E.EKOTX - Lookup on Description ofpurchasing organization NVARCSTR 20 0 0 yes

13 PURCH_ORG_ID T001W.EKORG -Purchasing Organization NVARCSTR 4 0 0 yes

14 VALUATN_AREA_ID T001W.BWKEY -Valuation area NVARCSTR 4 0 0 yes



PLANT

Contains Plant Level Information



Nullable

1 ADDRESS_ID Address ID NVARCSTR 10 0 0 yes

2 BATCH_STATUS_FLAG Batch Status Flag NVARCSTR 5 0 0 yes

3 CITY T001W.ORT01 CIty NVARCSTR 40 0 0 yes

4 CMPNY_CODE_ID Company code NVARCSTR 4 0 0 yes

5 CMPNY_CODE_NAME Company Code Name NVARCSTR 40 0 0 yes

6 COUNTRY_ID Country ID (Abbreviation) NVARCSTR 3 0 0 yes

7 COUNTRY_NAME Country Name (Full Name) NVARCSTR 15 0 0 yes

8 CTRL_AREA_ID Controlling area code NVARCSTR 4 0 0 yes

9 CTRL_AREA_NAME Control Area Name NVARCSTR 25 0 0 yes

10 DISTRICT District NVARCSTR 40 0 0 yes

11 FAX Fax Number NVARCSTR 40 0 0 yes

12 HOUSE_NUMBER House Number NVARCSTR 10 0 0 yes



15 PHONE Phone NVARCSTR 30 0 0 yes

16 PLANT_FULL_NAME ID and Name NVARCSTR 120 0 0 yes



17 PLANT_ID PK T001W.WERKS Plant NVARCSTR 4 0 0 no

18 PLANT_NAME Plant name NVARCSTR 40 0 0 yes

19 PLANT_NAME_01 T001W.NAME1 Plant Name NVARCSTR 40 0 0 yes

20 PLANT_NAME_02 T001W.NAME2 Plant Name NVARCSTR 40 0 0 yes

21 PLANT_NAME_03 Plant name 3 NVARCSTR 40 0 0 yes

22 PLANT_NAME_04 Plant name 3 NVARCSTR 40 0 0 yes

23 PURCH_ORG_ID T001W.EKORG Purchasing Organization NVARCSTR 4 0 0 yes

24 PURCH_ORG_NAME T001W.CHAZV Batch Management StatusIndicator NVARCSTR 20 0 0 yes

25 REGION_ID Region ID (Abbreviation of US State NVARCSTR 3 0 0 yes

26 REGION_NAME Region Name (Full Name of US State NVARCSTR 20 0 0 yes

27 SALES_ORG_ID T001W.VKORG Sales Organization NVARCSTR 4 0 0 yes

28 SALES_ORG_NAME Sales Organization name NVARCSTR 25 0 0 yes

29 STREET Street name NVARCSTR 60 0 0 yes

30 VALUATN_AREA_ID T001.BWKEY Valuation Area Key NVARCSTR 4 0 0 yes

31 ZIP Postal Code NVARCSTR 10 0 0 yes



PLANT_LOCATION

Plant Location attributes from T499S



Nullable

1 ADDRESS_ID Address NVARCSTR 10 0 0 yes

2 CITY City NVARCSTR 40 0 0 yes



5 COUNTRY_ID Country Key NVARCSTR 3 0 0 yes

6 COUNTRY_NAME Country name NVARCSTR 15 0 0 yes

7 DATE_TO Valid-to date DATETIME 24 0 9 yes


9 FAX First fax no.: dialling code+number NVARCSTR 30 0 0 yes




13 LOCATN_FULL_NAME T499S.STAND -Location ID + T499S.KTEXT-Text (40 characters) NVARCSTR 55 0 0 yes

14 LOCATN_ID PK T499S.STAND -Location NVARCSTR 10 0 0 no

15 LOCATN_NAME T499S.KTEXT -Text (40 characters) NVARCSTR 40 0 0 yes

16 PHONE First telephone no.: dialling code+number NVARCSTR 30 0 0 yes



17 PLANT_FULL_NAME ID and Name NVARCSTR 120 0 0 yes

18 PLANT_ID PK T499S.WERKS -Plant NVARCSTR 4 0 0 no


20 PLANT_NAME_01 Name 1 NVARCSTR 40 0 0 yes




24 REGION_ID Region (State, Province, County) NVARCSTR 3 0 0 yes

25 REGION_NAME Description NVARCSTR 20 0 0 yes

26 STREET Street NVARCSTR 60 0 0 yes

27 VALUATN_AREA_ID T001W.BWKEY -Valuation area NVARCSTR 4 0 0 yes

28 ZIP City postal code NVARCSTR 10 0 0 yes



PRODUCT_HIERARCHY

T179 - Product Hierarchy dimension



Nullable



3 LVL_01_DESCR Level 1 description NVARCSTR 40 0 0 yes

4 LVL_02_DESCR Level 2 description NVARCSTR 40 0 0 yes

5 LVL_03_DESCR Level 3 descritpion NVARCSTR 40 0 0 yes

6 PROD_DESCR Current Node description NVARCSTR 40 0 0 yes

7 PROD_HIER_ID PK Product Hierarchy Current Node ID NVARCSTR 18 0 0 no

8 PROD_LVL Node Level depth NVARCSTR 1 0 0 yes



PROFIT_CENTER

CEPC - Profit Center attributes



Nullable

1 CITY City NVARCSTR 40 0 0 yes

2 COUNTRY_ID Country key NVARCSTR 3 0 0 yes

3 COUNTRY_NAME Lookup on Country name NVARCSTR 15 0 0 yes

4 CTRL_AREA_ID PK Controlling area NVARCSTR 4 0 0 no

5 CURR_ID Currency key NVARCSTR 5 0 0 yes

6 DEPARTMENT Department NVARCSTR 12 0 0 yes


8 FAX Fax number NVARCSTR 40 0 0 yes

9 LANG_ID Language Key NVARCSTR 1 0 0 yes



12 PERSON_IN_CHARGE Person in charge of profit center NVARCSTR 20 0 0 yes

13 PHONE First telephone number NVARCSTR 30 0 0 yes

14 PROFIT_CNTR_AREA Profit center area NVARCSTR 12 0 0 yes

15 PROFIT_CNTR_DESCR Name of Profit Center NVARCSTR 40 0 0 yes

16 PROFIT_CNTR_FULL_NAME Profit Center Name and ID NVARCSTR 120 0 0 yes



17 PROFIT_CNTR_ID PK Profit center NVARCSTR 10 0 0 no

18 PROFIT_CNTR_NAME Profit Center Name NVARCSTR 20 0 0 yes

19 PROFIT_CNTR_NAME_01 Name 1 NVARCSTR 40 0 0 yes




23 REGION_ID Abbreviation of Region (State) NVARCSTR 3 0 0 yes

24 REGION_NAME Name of Region (State) NVARCSTR 20 0 0 yes

25 SEGMENT_DESCR Segment Description NVARCSTR 50 0 0 yes

26 SEGMENT_ID Segment ID for Segmental Reporting NVARCSTR 10 0 0 yes

27 STREET House number and street NVARCSTR 60 0 0 yes

28 VALID_FROM_DATE Valid-from date DATETIME 24 0 9 yes

29 VALID_TO_DATE Valid to date DATETIME 24 0 9 yes

30 ZIP Postal Code NVARCSTR 10 0 0 yes



PROFIT_CENTER_HIER

CCSS-RPRCTR - Profit Center Hierarchy- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Profit Center Child Node Description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Profit Center Child Node ID NVARCSTR 10 0 0 no


4 LEAF_FLAG PK Node Is Leaf NVARCSTR 1 0 0 no



7 PARENT_DESCR Profit Center Parent Node Descritpion NVARCSTR 64 0 0 yes

8 PARENT_ID PK Profit Center Parent Node ID NVARCSTR 10 0 0 no

9 ROOT_FLAG PK Node is Root NVARCSTR 1 0 0 no



PROFIT_CENTER_HIER_BAD

CCSS-RPRCTR - Profit Center Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Child Description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Child NVARCSTR 10 0 0 no

3 CTRL_AREA_ID PK Control Area ID NVARCSTR 4 0 0 no



6 LEAF_FLAG PK Leaf Flag NVARCSTR 1 0 0 no



9 PARENT_DESCR Parent Description NVARCSTR 64 0 0 yes

10 PARENT_ID PK Parent ID NVARCSTR 10 0 0 no

11 ROOT_FLAG PK Root Flag NVARCSTR 1 0 0 no




CCSS-RPRCTR - Profit Center hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP



Nullable


2 LEAF_LVL Current Node level depth DECIMAL 48 10 0 no



5 LVL_00_DESCR Profit Center Root node Description NVARCSTR 64 0 0 yes

6 LVL_00_FULL_NAME Profit Center ID and Description for the root NVARCSTR 120 0 0 yes

7 LVL_00_ID PK Profit Center Root node ID NVARCSTR 10 0 0 no

8 LVL_01_DESCR Profit Center Level 1 node Description NVARCSTR 64 0 0 yes

9 LVL_01_FULL_NAME Profit Center ID and Description for Level 1 NVARCSTR 120 0 0 yes

10 LVL_01_ID PK Profit Center Level 1 node ID NVARCSTR 10 0 0 no


12 LVL_02_FULL_NAME Prifit Center ID and Descritption for Level 2 NVARCSTR 120 0 0 yes



15 LVL_03_FULL_NAME Profit Center Id and Description NVARCSTR 120 0 0 yes





18 LVL_04_FULL_NAME Priofit Center ID and Description for Level 4 NVARCSTR 120 0 0 yes



21 LVL_05_FULL_NAME Profit Center Id and Descritpion for Level 5 NVARCSTR 120 0 0 yes



24 LVL_06_FULL_NAME Profit Center Id and Descripiton for Level 6 NVARCSTR 120 0 0 yes



27 LVL_07_FULL_NAME Profit Center Id and Descritpion for level 7 NVARCSTR 120 0 0 yes



30 LVL_08_FULL_NAME Profit Center Id and Descritpion for level 8 NVARCSTR 120 0 0 yes










38 PROFIT_CNTR_ID PK Profit Center ID NVARCSTR 10 0 0 no


CCSS-RPRCTR Profit Center Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Child Node Descritpion for Profit Center NVARCSTR 64 0 0 yes

2 CHILD_FULL_NAME Profit Center (Child) ID and Descritpion NVARCSTR 120 0 0 yes

3 CHILD_ID PK Child Node ID for Profit Center NVARCSTR 10 0 0 no

4 CTRL_AREA_ID PK Controlling Center ID NVARCSTR 4 0 0 no

5 DEPTH Current Child Node Depth INTEGER 4 0 0 yes

6 LEAF_FLAG Current Node is Leaf INTEGER 4 0 0 yes



9 PARENT_DESCR Parent Node Descritpion for Profit Center NVARCSTR 64 0 0 yes

10 PARENT_FULL_NAME Profit Center (Parent) ID and Descritpion NVARCSTR 120 0 0 yes

11 PARENT_ID PK Parent Node ID for Profit Center NVARCSTR 10 0 0 no

12 ROOT_FLAG Current Node is Root INTEGER 4 0 0 yes



PROJECT_ELEMENT

PRPS, PRTE - Project Element Master dimension



Nullable

1 ACTL_DURTN Actual length (duration) of the WBS element DECIMAL 48 5 1 yes

2 ACTL_FINISH_DATE Actual finish date of the WBS element DATETIME 24 0 9 yes

3 ACTL_START_DATE Actual start date for the WBS element DATETIME 24 0 9 yes

4 APPLICANT_ID Applicant number DECIMAL 48 28 0 yes

5 APPLICANT_NAME Applicant NVARCSTR 25 0 0 yes

6 BASIC_DURTN Length (duration) of the basic dates in the WBSelement DECIMAL 48 5 1 yes

7 BASIC_FINISH_DATE WBS element: Basic finish date DATETIME 24 0 9 yes

8 BASIC_SCHED_EARLST_FINISH_DATE Earliest scheduled finish date (basic) DATETIME 24 0 9 yes

9 BASIC_SCHED_EARLST_START_DATE Earliest scheduled start date (Basic) DATETIME 24 0 9 yes

10 BASIC_SCHED_LATEST_FINISH_DATE Latest scheduled finish date (basic) DATETIME 24 0 9 yes

11 BASIC_SCHED_LATEST_START_DATE Latest scheduled start date (basic) DATETIME 24 0 9 yes

12 BASIC_START_DATE WBS element: Basic start date DATETIME 24 0 9 yes

13 CREATED_BY Name of Person who Created the Object NVARCSTR 12 0 0 yes

14 CREATE_DATE Date on which the record was created DATETIME 24 0 9 yes

15 DELETE_FLAG Deletion indicator NVARCSTR 1 0 0 yes

16 FCST_DURTN Forecasted length (duration) of the WBSelement DECIMAL 48 5 1 yes



17 FCST_FINISH_DATE Forecasted finish date of the WBS element DATETIME 24 0 9 yes

18 FCST_SCHED_EARLST_FINISH_DATE Earliest scheduled finish date (forecast) DATETIME 24 0 9 yes

19 FCST_SCHED_LATEST_FINISH_DATE Latest scheduled finish date (Forecast) DATETIME 24 0 9 yes

20 FCST_SCHED_LATEST_START_DATE Latest scheduled start date (forecast) DATETIME 24 0 9 yes

21 FCST_SCHED_START_DATE Scheduled start date (Forecast) DATETIME 24 0 9 yes

22 FCST_START_DATE Forecasted start date of the WBS element DATETIME 24 0 9 yes



25 MILESTONE_FLAG Indicator: WBS element used in projectsummarization NVARCSTR 1 0 0 yes

26 PRIORITY_FLAG Priority NVARCSTR 1 0 0 yes

27 PROJ_ELEM_CODE PRPS.PSPNR - WBS element Internal ID DECIMAL 48 28 0 yes

28 PROJ_ELEM_DESCR PRPS.POST1 - WBS element (ProjectElement) Description NVARCSTR 40 0 0 yes

29 PROJ_ELEM_FULL_NAME

PRPS.POSID and PRPS.POST1 ProjectElement ID and Project Element Description NVARCSTR 100 0 0 yes

30 PROJ_ELEM_ID PK PRPS.POSID - WBS element External ID NVARCSTR 24 0 0 no

31 PROJ_ELEM_SHORT_ID PRPS.POSKI - WBS element short External ID NVARCSTR 16 0 0 yes

32 PROJ_ID PROJ.PSPID - (Lookup on PROJ) Project ID(external) NVARCSTR 24 0 0 yes

33 PROJ_NAME PROJ.POST1 - PS: Short description (1st textline) -- Lookup on PROJ NVARCSTR 40 0 0 yes

34 RESP_PERSON Name of responsible person (Project manager) NVARCSTR 25 0 0 yes



35 RESP_PERSON_ID Number of the responsible person (projectmanager) DECIMAL 48 28 0 yes

36 TNTV_FINISH_DATE Tentative actual finish date for WBS element DATETIME 24 0 9 yes

37 TNTV_START_DATE Tentative actual start date for WBS element DATETIME 24 0 9 yes

38 UOM_ID_ACTL_DURTN Unit for duration of actual WBS element dates NVARCSTR 3 0 0 yes

39 UOM_ID_BASIC_DURTN Unit for duration of basic WBS element dates NVARCSTR 3 0 0 yes

40 UOM_ID_FCST_DURTN

Unit for duration of WBS element planneddates NVARCSTR 3 0 0 yes

PROJECT_ELEMENT_HIER

PRHI - Project Element Hierarchy dimension



Nullable

1 CHILD_CODE PRPS.POSID - WBS element Internal ID -Project Element Child Node ID INTEGER 4 0 0 no

2 CHILD_DESCR Project Element Child Node Description NVARCSTR 100 0 0 yes

3 CHILD_FULL_NAME Project Element Child Node ID and Description NVARCSTR 100 0 0 yes

4 CHILD_ID PK PRPS.POSID - WBS element External ID -Project Element Child Node ID NVARCSTR 24 0 0 no



7 PARENT_CODE PRPS.POSID - WBS element Internal ID -Project Element Parent Node ID INTEGER 4 0 0 no

8 PARENT_DESCR Project Element Parent Node Description NVARCSTR 100 0 0 yes

9 PARENT_FULL_NAME Project Element Parent Node ID Description NVARCSTR 100 0 0 yes

10 PARENT_ID PK PRPS.POSID - WBS element External ID -Project Element Parent Node ID NVARCSTR 24 0 0 no



PROJECT_ELEMENT_HIER_BAD

Rejected Project Element Hierarchy records



Nullable

1 CHILD_CODE PRPS.POSID - WBS element Internal ID -Project Element Child Node ID INTEGER 4 0 0 no

2 CHILD_DESCR Project Element Child Node Description NVARCSTR 100 0 0 yes

3 CHILD_FULL_NAME Project Element Child Node ID and Description NVARCSTR 100 0 0 yes

4 CHILD_ID PK PRPS.POSID - WBS element External ID -Project Element Child Node ID NVARCSTR 24 0 0 no





9 PARENT_CODE PRPS.POSID - WBS element Internal ID -Project Element Parent Node ID INTEGER 4 0 0 yes

10 PARENT_DESCR Project Element Parent Node Description NVARCSTR 100 0 0 yes

11 PARENT_FULL_NAME Project Element Parent Node ID andDescription NVARCSTR 100 0 0 yes

12 PARENT_ID PK PRPS.POSID - WBS element External ID -Project Element Parent Node ID NVARCSTR 24 0 0 no




PRHI - Project element hierarchy flattenned horizontally



Nullable

1 LEAF_LVL Current Node level depth INTEGER 4 0 0 yes



4 LVL_00_DESCR Project Element Root Node Description NVARCSTR 100 0 0 yes

5 LVL_00_FULL_NAME Project Element Root Level ID and NodeDescription NVARCSTR 100 0 0 yes

6 LVL_00_ID PK Project Element Root Node ID NVARCSTR 24 0 0 no

7 LVL_01_DESCR Project Element Level 1 Node Description NVARCSTR 100 0 0 yes

8 LVL_01_FULL_NAME Project Element Level 1 Level ID and NodeDescription NVARCSTR 100 0 0 yes

9 LVL_01_ID PK Project Element Level 1 Node ID NVARCSTR 24 0 0 no












37 PROJ_ELEM_ID PK Project Element Current Node ID NVARCSTR 24 0 0 no


PRHI - Project Element Hierarchy vertically flattenned



Nullable

1 CHILD_DESCR Parent Node desc NVARCSTR 100 0 0 yes

2 CHILD_FULL_NAME Parent Node ID and Desc NVARCSTR 100 0 0 yes

3 CHILD_ID PK Parent Node ID NVARCSTR 24 0 0 no

4 DEPTH Node depth level INTEGER 4 0 0 yes

5 LEAF_FLAG Is Leaf INTEGER 4 0 0 yes



8 PARENT_DESCR Child Node Desc NVARCSTR 100 0 0 yes

9 PARENT_FULL_NAME Child Node ID and Desc NVARCSTR 100 0 0 yes

10 PARENT_ID PK Child Node ID NVARCSTR 24 0 0 no

11 ROOT_FLAG Is Root INTEGER 4 0 0 yes




AFRU - Order completion confirmations (also data from AFIH, AUFK)



Nullable

1 ACTIVITY_ID PK AFRU-LEARR - Activity type for confirmation NVARCSTR 6 0 0 yes

2 ASSEMBLY_ID AFIH-BAUTL - Assembly ID NVARCSTR 18 0 0 yes

3 BUS_AREA_ID PK AUFK.GSBER -Business Area NVARCSTR 4 0 0 yes

4 CAPACITY_ID PK AFRU.KAPID - Capacity ID NVARCSTR 20 0 0 yes

5 CHANGE_BY_LOGIN AFRU-AENAM - Name of accounting clerkwho changed record NVARCSTR 12 0 0 yes

6 CHANGE_DATE AFRU-LAEDA - Date of last change DATETIME 24 0 9 yes

7 CMPNY_CODE_ID PK AUFK.BUKRS -Company Code NVARCSTR 4 0 0 yes

8 CONFIRMATN_DESCR AFRU-LTXA1 - Confirmation text (inline) NVARCSTR 40 0 0 yes

9 CONFIRMATN_ID PK AFRU-RUECK - Confirmation number ofoperation NVARCSTR 10 0 0 no

10 CONFIRMATN_SEQ_ID PK AFRU-RMZHL - Confirmation counter NVARCSTR 8 0 0 no

11 COST_CNTR_ID PK AUFK.KOSTV -Responsible cost center NVARCSTR 10 0 0 yes

12 CREATE_BY_LOGIN AFRU-ERNAM - Name of person who createdobject NVARCSTR 12 0 0 yes

13 CREATE_DATE PK AFRU-ERSDA - Creation date DATETIME 24 0 9 yes

14 CTRL_AREA_ID PK AUFK-KOKRS - Controlling area NVARCSTR 4 0 0 yes

15 CURR_ID PK AUFK.WAERS -Order Currency NVARCSTR 5 0 0 yes

16 CUSTOMER_ID PK AFIH.KUNUM - Customer number NVARCSTR 10 0 0 yes



17 DAYS_COMPLT_FCST Calcualted Days to complete the operation (asForecas end - Forecat start) DECIMAL 48 22 7 yes

18 DAYS_EXECUTN Calcualted days of execution (as ExecutionStart end - Execution start) DECIMAL 48 22 7 yes

19 DOC_CATEG_ID AUFK.AUTYP - Document Category NVARCSTR 2 0 0 yes

20 DOC_TYPE_ID PK AUFK-AUART - Order type NVARCSTR 4 0 0 yes

21 EQUIPMNT_ID PK AFIH-EQUNR - Equipment number NVARCSTR 18 0 0 yes

22 EXECUTN_END_DATEAFRU-IEDD - Confirmed date for executionfinish + AFRU-IEDZ - Confirmed time forExecution finish

DATETIME 24 0 9 yes

23 EXECUTN_START_DATE

AFRU-ISDD - Confirmed date for start ofexecution) + AFRU-ISDZ - Confirmed time forExecution start

DATETIME 24 0 9 yes

24 FCST_END_DATEAFRU.PEDD - Forecast finish date of operationfrom confirmation) + AFRU.PEDZ - Forecastfinish time of operation from confirmation

DATETIME 24 0 9 yes

25 FINAL_CONFIRMATN_FLAG

AFRU-AUERU - Indicator: Partial/finalconfirmation DECIMAL 48 28 0 yes

26 FUNCTNL_AREA_ID PK AUFK.FUNC_AREA -Functional Area NVARCSTR 16 0 0 yes

27 FUNCTNL_LOCATN_ID PK ILOA-TPLNR (lookup) - Functional location ID NVARCSTR 30 0 0 yes

28 HOURS_COMPLT_FCST

Calcualted hours to complete the operation (asForecas end - Forecat start) DECIMAL 48 22 7 yes

29 HOURS_EXECUTN Calcualted hours of execution (as ExecutionStart end - Execution start) DECIMAL 48 22 7 yes

30 INTERNAL_ORDER_ID PK AFRU-AUFNR - Order Number NVARCSTR 12 0 0 yes



33 LOCATN_ID PK AUFK.STORT -Location NVARCSTR 10 0 0 yes

34 MAINT_ACTIVITY_TYPE_ID PK AFIH-ILART - Maintenance activity type NVARCSTR 3 0 0 yes



35 MATERIAL_ID PK AFIH.SERMAT - Material number NVARCSTR 18 0 0 yes

36 MINS_COMPLT_FCST Calcualted minutes to complete the operation(as Forecas end - Forecat start) DECIMAL 48 22 7 yes

37 MINS_EXECUTN Calcualted minutes of execution (as ExecutionStart end - Execution start) DECIMAL 48 22 7 yes

38 NOTIFICTN_ID AFIH.QMNUM - Notification number NVARCSTR 12 0 0 yes

39 NO_REMAIN_WORK_FLAG

AFRU-LEKNW - Indicator showing noremaining work expected DECIMAL 48 28 0 yes

40 OPERATN_ROUTING_ID

AFRU-AUFPL - Routing number for operationsin the order NVARCSTR 10 0 0 yes

41 OPERATN_SEQ_ID AFRU-APLZL - General counter for order NVARCSTR 8 0 0 yes

42 ORDER_STATUS_ID PK AUFK.ASTNR - Order status NVARCSTR 2 0 0 yes

43 PERSON_ID PK AFRU-PERNR - Personnel number - who filesCofirmation NVARCSTR 8 0 0 yes

44 PERSON_ID_RESP IHPA-PERNR - Person responsible for theService Order execution NVARCSTR 12 0 0 yes

45 PLANNG_GRP_ID PK AFIH-INGPR - Maintenance planner group NVARCSTR 3 0 0 yes

46 PLANT_ID PK AFRU-WERKS - Plant NVARCSTR 4 0 0 yes

47 PLANT_ID_PLANNG AFIH-IWERK - Planning plant NVARCSTR 4 0 0 yes

48 POST_DATE AFRU.BUDAT - Posting date DATETIME 24 0 9 yes

49 POST_OPEN_RESERVATN_FLAG AFRU.AUSOR - Post open reservations NVARCSTR 1 0 0 yes

50 PRIORITY_ID PK AFIH.PRIOK - Priority NVARCSTR 1 0 0 yes

51 PRIORITY_TYPE_ID PK AFIH.ARTPR - Priority type NVARCSTR 2 0 0 yes

52 PROD_HIER_ID MARA.PRDHA - Product Hierarchy ID - Lookup based on AFIH.SERMAT NVARCSTR 18 0 0 yes



53 PROFIT_CNTR_ID PK AUFK.PRCTR - Profit center NVARCSTR 10 0 0 yes

54 PROJ_ELEM_ID PK PRPS.POSID - Project Element (WBS)External ID NVARCSTR 24 0 0 yes

55 QTY_DURTN_ACTL AFRU.IDAUR - Actual duration for confirmation DECIMAL 48 5 1 yes

56 QTY_WORK_ACTL AFRU-ISMNW - Actual work (ifthenelsefunction call) DECIMAL 48 7 1 yes

57 QTY_WORK_REMAIN AFRU-OFMNW - Remaining work DECIMAL 48 7 1 yes

58 SERIAL_NUM AFIH.SERIALNR - Serial number NVARCSTR 18 0 0 yes

59 SUITABILITY_ID PK AFRU.QUALF - Suitability NVARCSTR 2 0 0 yes

60 SYSTEM_CONDITN_ID PK AFIH-ANLZU - System condition NVARCSTR 1 0 0 yes

61 UOM_ID_DURTN_ACTL PK AFRU.IDAUE- Unit for actual duration NVARCSTR 3 0 0 yes

62 UOM_ID_WORK_ACTL AFRU-ISMNE - Unit for work NVARCSTR 3 0 0 yes

63 UOM_ID_WORK_REMAIN

AFRU-OFMNE - Unit of measure for remainingwork NVARCSTR 3 0 0 yes





Extracts data from the table PMCO (cost summary for Plant Maintenence) in horizontal period activity representation



Nullable

1 ACCTNG_FLAG PK PMCO-BEMOT - Accounting indicator NVARCSTR 2 0 0 no

2 AMT_CR_PER00_TRX PMCO-WRT00 - Period Credit value in ledgercurrency DECIMAL 48 15 2 yes

















17 AMT_CR_PER15_TRX PMCO-WRT15- Period Credit value in ledgercurrency DECIMAL 48 15 2 yes


19 AMT_CR_QTR01_TRX PMCO-WRT00 through 03 - Quarter Creditvalue in ledger currency DECIMAL 48 15 2 yes




23 AMT_CR_YTD_TRX PMCO-WRT01 through 16 - Year Credit valuein ledger currency DECIMAL 48 15 2 yes

24 AMT_DR_PER00_TRX PMCO-WRT00 - Period Debit value in ledgercurrency DECIMAL 48 15 2 yes



















41 AMT_DR_QTR01_TRX PMCO-WRT00 through 03 - Quarter Debitvalue in ledger currency DECIMAL 48 15 2 yes




45 AMT_DR_YTD_TRX PMCO-WRT01 through 16 - Year Debit valuein ledger currency DECIMAL 48 15 2 yes


47 BUS_ACTIVITY_ID PK PMCO-VORGA - Budgeting / Planning Activity NVARCSTR 4 0 0 no




51 CTRL_AREA_ID PK AUFK.KOKRS -Controlling Area NVARCSTR 4 0 0 yes

52 CURR_ID_CTRL_AREA Lookup controlling area currency from TKA01 NVARCSTR 5 0 0 yes



53 CURR_ID_LOC Lookup company code currency from T001 NVARCSTR 5 0 0 yes

54 CURR_ID_TRX PK PMCO-COCUR - Currency ID (LedgerCurrency) NVARCSTR 5 0 0 no


56 DOC_TYPE_ID PK AUFK.AUART -Order Type NVARCSTR 4 0 0 yes


58 FISC_YEAR PK PMCO-GJAHR - Fiscal year INTEGER 4 0 0 no

59 FISC_YR_VARIANT_ID PK Fiscal Year Variant in SAP For Company Code NVARCSTR 2 0 0 yes



62 INTERNAL_ORDER_ID PK AUFK.AUFNR -Order Number NVARCSTR 12 0 0 yes

63 LOAD_DATE Date and Time This row was loaded into theRapid Mart DATETIME 24 0 9 yes

64 LOAD_TIME Time This row was loaded into the Rapid Mart NVARCSTR 8 0 0 yes


66 MAINT_ACTIVITY_TYPE_ID AFIH-ILART - Maintenance activity type NVARCSTR 3 0 0 yes

67 MATERIAL_ID AFIH.SERMAT - Material number NVARCSTR 18 0 0 yes

68 MAX_FISC_PERIOD PK PMCO-PERBL - Period block - Max # ofPeriods INTEGER 4 0 0 no

69 OBJ_ID PK PMCO-OBJNR - Object number NVARCSTR 22 0 0 no

70 PARTITION_YEAR PK Duplicate of Fisc. Year column to allow forTable partition on a field not in the Primary Key INTEGER 4 0 0 yes



71 PLANT_ID PK AUFK.WERKS -Plant NVARCSTR 4 0 0 yes




75 PROFIT_CNTR_ID PK AUFK.PRCTR -Profit Center NVARCSTR 10 0 0 yes


77 RECORD_CATEG_ID PK PMCO-ACPOS - Value category NVARCSTR 14 0 0 no

78 RECORD_TYPE_ID PK PMCO.WRTTP - Value type NVARCSTR 2 0 0 no


80 SURROGATE_DOC_ID Alternate key generated in the Rapid Mart forreporting purposes DECIMAL 48 18 0 yes


82 VARIANCE_CATEG_ID PK PMCO-ABKAT - Category: variance/resultsanalysis NVARCSTR 10 0 0 no





Computes Rolling Totals forService Cost Summary Vertical Fact. (Sourced from PMCO)



Nullable


2 AMT_CR_QTD_TRX PMCO-WRT01 through 16 - QTD Credit valuein ledger currency DECIMAL 48 15 2 yes

3 AMT_CR_TRXPMCO-WRT00 through WRT16 - PeriodCredit value in ledger currency. For Period 01- cumulative of Per 00 and Per 01; for Per 12 -cumulative of Per 12 through Per 16

DECIMAL 48 15 2 yes

4 AMT_CR_YTD_TRX PMCO-WRT01 through 16 - YTD Credit valuein ledger currency DECIMAL 48 15 2 yes

5 AMT_DR_QTD_TRX PMCO-WRT01 through 16 - QTD Debit valuein ledger currency DECIMAL 48 15 2 yes

6 AMT_DR_TRXPMCO-WRT00 through WRT16 - Period Debitvalue in ledger currency. For Period 01 -cumulative of Per 00 and Per 01; for Per 12 -cumulative of Per 12 through Per 16

DECIMAL 48 15 2 yes

7 AMT_DR_YTD_TRX PMCO-WRT01 through 16 - YTD Debit valuein ledger currency DECIMAL 48 15 2 yes

8 AMT_PER_BEGIN_TRX

PMCO-WRT01 through 16 - Period beginbalance value in ledger currency DECIMAL 48 17 2 yes

9 AMT_PER_ROLLING_TRX Rolling Total Balance - Transaction Currency DECIMAL 48 17 2 yes

10 AMT_PTD_TRX Period Begining Balance - TransactionCurrency DECIMAL 48 17 2 yes






16 CTRL_AREA_ID PK AUFK.KOKRS -Controlling Area NVARCSTR 4 0 0 yes







21 DOC_TYPE_ID PK AUFK.AUART -Order Type NVARCSTR 4 0 0 yes


23 FISC_PERIOD PK Fiscal Period (1 through 16) INTEGER 4 0 0 no


25 FISC_YR_VARIANT_ID PK Fiscal Year Variant in SAP For Company Code NVARCSTR 2 0 0 yes



28 INTERNAL_ORDER_ID PK AUFK.AUFNR -Order Number NVARCSTR 12 0 0 yes



31 LOCATN_ID AUFK.STORT -Location NVARCSTR 10 0 0 yes






35 PARTITION_YEAR PK PMCO-GJAHR - Same as Fiscal year for tablepartitions INTEGER 4 0 0 yes

36 PLANT_ID PK AUFK.WERKS -Plant NVARCSTR 4 0 0 yes




40 PROFIT_CNTR_ID PK AUFK.PRCTR -Profit Center NVARCSTR 10 0 0 yes





45 SUMMARY_KEY Concatenation ofr Primary Key for use inordering query. NVARCSTR 100 0 0 yes







SERVICE_COST_SUMMARY_STAGE_VR

Vertical representation of Service Order Cost period activity. Staging is used for further Rolling Summary calculation



Nullable


2 AMT_CR_QTD_TRX PMCO-WRT01 through 16 - QTD Credit valuein ledger currency DECIMAL 48 15 2 yes

3 AMT_CR_TRXPMCO-WRT00 through WRT16 - PeriodCredit value in ledger currency. For Period 01- cumulative of Per 00 and Per 01; for Per 12 -cumulative of Per 12 through Per 16

DECIMAL 48 15 2 yes

4 AMT_CR_YTD_TRX PMCO-WRT01 through 16 - YTD Credit valuein ledger currency DECIMAL 48 15 2 yes

5 AMT_DR_QTD_TRX PMCO-WRT01 through 16 - QTD Debit valuein ledger currency DECIMAL 48 15 2 yes

6 AMT_DR_TRXPMCO-WRT00 through WRT16 - Period Debitvalue in ledger currency. For Period 01 -cumulative of Per 00 and Per 01; for Per 12 -cumulative of Per 12 through Per 16

DECIMAL 48 15 2 yes

7 AMT_DR_YTD_TRX PMCO-WRT01 through 16 - YTD Debit valuein ledger currency DECIMAL 48 15 2 yes

8 AMT_PER_BEGIN_TRX

PMCO-WRT01 through 16 - Period beginbalance value in ledger currency DECIMAL 48 17 2 yes



11 BUS_AREA_ID AUFK.GSBER -Business Area NVARCSTR 4 0 0 yes

12 CMPNY_CODE_ID AUFK.BUKRS -Company Code NVARCSTR 4 0 0 yes

13 COST_CNTR_ID AUFK.KOSTV -Responsible cost center NVARCSTR 10 0 0 yes

14 CTRL_AREA_ID AUFK.KOKRS -Controlling Area NVARCSTR 4 0 0 yes







19 DOC_TYPE_ID AUFK.AUART -Order Type NVARCSTR 4 0 0 yes

20 EQUIPMNT_ID AFIH-EQUNR - Equipment number NVARCSTR 18 0 0 yes

21 FISC_PERIOD PK Fiscal Period (1 through 16) INTEGER 4 0 0 no


23 FISC_YR_VARIANT_ID Fiscal Year Variant in SAP For Company Code NVARCSTR 2 0 0 yes

24 FUNCTNL_AREA_ID AUFK.FUNC_AREA -Functional Area NVARCSTR 16 0 0 yes

25 FUNCTNL_LOCATN_ID ILOA-TPLNR (lookup) - Functional location ID NVARCSTR 30 0 0 yes

26 INTERNAL_ORDER_ID AUFK.AUFNR -Order Number NVARCSTR 12 0 0 yes



29 LOCATN_ID AUFK.STORT -Location NVARCSTR 10 0 0 yes

30 MAINT_ACTIVITY_TYPE_ID AFIH-ILART - Maintenance activity type NVARCSTR 3 0 0 yes

31 MATERIAL_ID AFIH.SERMAT - Material number NVARCSTR 18 0 0 yes


33 PARTITION_YEAR PK Duplicate of Fisc. Year column to allow forTable partition on a field not in the Primary Key INTEGER 4 0 0 yes

34 PLANT_ID AUFK.WERKS -Plant NVARCSTR 4 0 0 yes



35 PRIORITY_ID AFIH.PRIOK - Priority NVARCSTR 1 0 0 yes

36 PRIORITY_TYPE_ID AFIH.ARTPR - Priority type NVARCSTR 2 0 0 yes


38 PROFIT_CNTR_ID AUFK.PRCTR -Profit Center NVARCSTR 10 0 0 yes

39 PROJ_ELEM_ID PRPS.POSID - Project Element (WBS)External ID NVARCSTR 24 0 0 yes





44 SYSTEM_CONDITN_ID AFIH-ANLZU - System condition NVARCSTR 1 0 0 yes


46 WORK_CNTR_ID CRHD-ARBPL (lookup) - Work Center uniquename NVARCSTR 8 0 0 yes




Operations related to Service orders from AFIH, AFVC, AFVV



Nullable

1 ACTIVITY_ID PK AFVC.LARNT - Activity Type NVARCSTR 6 0 0 yes

2 ACTL_END_DATEAFVV-IEDD - Actual finish: Execution (date) +AFVV-ISDZ - AFVV-IEDZ - Actual finish:Execution (time)

DATETIME 24 0 9 yes

3 ACTL_START_DATEAFVV-ISDD - Actual start: Execution (date) +AFVV-ISDZ - Actual start: Execution/setup(time)

DATETIME 24 0 9 yes

4 AMT_COST_MTRL AFVC.MAT_PRKST - Material planning innetworks: primary costs DECIMAL 48 11 2 yes

5 AMT_COST_TTL AFVC.PRKST - Total Costs in the activity -Planned DECIMAL 48 11 2 yes

6 ASSEMBLY_ID AFIH.BAUTL - Assembly NVARCSTR 18 0 0 yes

7 BUS_AREA_ID PK AFVC.GSBER - Business Area NVARCSTR 4 0 0 yes

8 CAPACITY_REQUIRMNT_ID PK AFVC.BEDID - ID of the capacity requirements

record NVARCSTR 12 0 0 yes

9 CHART_OF_ACCT_ID PK T001.KTOPL-Chart of accts ID - Lookup NVARCSTR 4 0 0 yes

10 CMPNY_CODE_ID PK AFVC.BUKRS Company Code NVARCSTR 4 0 0 yes

11 COMPLT_FLAG AFVC-LEKNW - Indicator showing noremaining work expected if set to 1 DECIMAL 48 28 0 yes

12 CONFIRMATN_ID AFVC.RUECK Completion confirmationnumber for the operation NVARCSTR 10 0 0 yes

13 CONFIRMATN_SEQ_ID AFVC.RMZHL- Confirmation counter NVARCSTR 8 0 0 yes

14 COSTNG_FLAG AFVC.SELKZ - Selection indicator for costingline items NVARCSTR 1 0 0 yes

15 COST_CNTR_ID AUFK.KOSTV -Responsible cost center NVARCSTR 10 0 0 yes

16 COST_ELEM_ID PK AFVC.SAKTO - Cost Element NVARCSTR 10 0 0 yes



17 CREATE_DATE PK AUFK.ERDAT -Order Create date DATETIME 24 0 9 yes


19 CTRL_KEY_ID PK AFVC.STEUS - Control key NVARCSTR 4 0 0 yes

20 CURR_ID PK AFVC.WAERS - Currency Key NVARCSTR 5 0 0 yes


22 DAYS_EXECUTN_ACTL

Calcualted Days of Operation exeuction/startuptime (as Actl Start and Actl End datetime) DECIMAL 48 22 7 yes

23 DAYS_EXECUTN_SCHED

Calcualted Days of Operation exeuction/startuptime (as Sched Start and Sched End datetime) DECIMAL 48 22 7 yes

24 DELETE_FLAGJEST-STAT (lookup) - DEL operationisdeleted status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes


26 DOC_TYPE_ID AUFK.AUART - Document Type NVARCSTR 4 0 0 yes

27 EQUIPMNT_ID PK AFIH.EQUNR - Equipment number NVARCSTR 18 0 0 yes

28 EXECUTN_FACTOR AFVV-AUFKT - Execution factor INTEGER 4 0 0 yes

29 FINAL_CONFIRM_FLAG

JEST-STAT (lookup) - CNF operation is finallyconfirmed status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes


31 FUNCTNL_LOCATN_ID ILOA-TPLNR (lookup) - Functional location ID NVARCSTR 30 0 0 yes

32 HOURS_EXECUTN_ACTL

Calcualted Hours of Operationexeuction/startup time (as Actl Start and ActlEnd datetime)

DECIMAL 48 22 7 yes

33 HOURS_EXECUTN_SCHED

Calcualted Hours of Operationexeuction/startup time (as Sched Start andSched End datetime)

DECIMAL 48 22 7 yes

34 INTERNAL_ORDER_ID PK AFIH.AUFNR - Order Number NVARCSTR 12 0 0 yes



35 LOAD_DATE Date loaded into RapidMart DATETIME 24 0 9 yes

36 LOAD_TIME Time loaded into RapidMart NVARCSTR 8 0 0 yes




40 MINS_EXECUTN_ACTL

Calcualted Mins of Operation exeuction/startuptime (as Actl Start and Actl End datetime) DECIMAL 48 22 7 yes

41 MINS_EXECUTN_SCHED

Calcualted Mins of Operation exeuction/startuptime (as Sched Start and Sched End datetime) DECIMAL 48 22 7 yes


43 OBJ_CLASS_ID PK AFVC.SCOPE - Object Class NVARCSTR 10 0 0 yes

44 OBJ_ID AFVC.OBJNR - Object number NVARCSTR 22 0 0 yes

45 OBJ_TYPE_ID Object Type ID NVARCSTR 10 0 0 yes

46 OPERATN_DESCR AFVC.LTXA1 - Operation short text NVARCSTR 40 0 0 yes

47 OPERATN_NUM AFVC.VORNR - Operation Number NVARCSTR 4 0 0 yes

48 OPERATN_NUM_PAR AFVC.SUMNR - Node number of the superioroperation NVARCSTR 8 0 0 yes

49 OPERATN_ROUTING_ID PK AFVC.AUFPL - Routing number of operations

in the order NVARCSTR 10 0 0 no

50 OPERATN_SEQ_ID PK AFVC.APLZL - General counter for order NVARCSTR 8 0 0 no

51 PARTL_CONFIRM_FLAG

JEST-STAT (lookup) -PCNF operation ispartially confirmed status is active (1 is active,0 is inactive)

DECIMAL 48 28 0 yes




53 PLANT_ID PK AFVC.WERKS - Plant NVARCSTR 4 0 0 yes

54 PRIORITY_ID PK AFIH.PRIOK - Priority ID NVARCSTR 1 0 0 yes



57 PROFIT_CNTR_ID PK AFVC.PRCTR Profit Center NVARCSTR 10 0 0 yes


59 PURCH_DOC_ID AFVC.EBELN - Purchasing document number NVARCSTR 10 0 0 yes

60 PURCH_LINE_ITEM_ID

AFVC.EBELP - Item number of purchasingdocument NVARCSTR 5 0 0 yes

61 QTY_DURTN AFVV.DAUNO - Normal duration of the activity DECIMAL 48 5 1 yes

62 QTY_WORK_ACTL AFVV-ISMNW - Actual work DECIMAL 48 13 3 yes

63 QTY_WORK_FCST AFVV-ORMNW - Forecasted work (actual +remaining) DECIMAL 48 7 1 yes

64 QTY_WORK_SCHED AFVV-ARBEI - Work involved in the activity DECIMAL 48 7 1 yes

65 RELEASE_FLAGJEST-STAT (lookup) - REL operation isreleased status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes

66 REQUISITN_DOC_ID AFVC.BANFN Purchase requisition number NVARCSTR 10 0 0 yes

67 REQUISITN_LINE_ITEM_ID

AFVC.BNFPO - Item number of the purchaserequisition in the order NVARCSTR 5 0 0 yes

68 SCHED_END_DATEAFVV.FSEDD - Earliest scheduled finish:Execution (date) + AFVV.FSEDZ - Earliestscheduled finish: Execution (time)

DATETIME 24 0 9 yes

69 SCHED_START_DATEAFVV.FSAVD - Earliest scheduled start:Execution (date) + AFVV.FSAVZ - Earliestscheduled start: Execution (time)

DATETIME 24 0 9 yes




71 SUITABILITY_ID PK AFVC.QUALF Suitability NVARCSTR 2 0 0 yes

72 SYSTEM_CONDITN_ID PK AFVC-ANLZU - System condition NVARCSTR 1 0 0 yes

73 TECHN_COMPLT_FLAG

JEST-STAT (lookup) - TECO operation istechnically completed status is active (1 isactive, 0 is inactive)

DECIMAL 48 28 0 yes

74 UOM_ID_DURTN PK AFVV.DAUNE - Normal duration/unit NVARCSTR 3 0 0 yes

75 UOM_ID_WORK AFVV-ARBEH - Unit for work NVARCSTR 3 0 0 yes

76 VENDOR_ID PK AFVC.LIFNR - Account Number of Vendor orCreditor NVARCSTR 10 0 0 yes




SERVICE_ORDER_FACT

Internal Order Master - Service Order category from AFIH/AFKO/AUFK



Nullable

1 ACTL_END_DATE AFKO.GETRI - Confirmed order finish date DATETIME 24 0 9 yes

2 ACTL_RELEASE_DATE

AFKO-FTRMI - Actual release date (LastOperation is Released) DATETIME 24 0 9 yes

3 ACTL_START_DATE AFKO-GSTRI - Actual start date (FirstOperation is Started) DATETIME 24 0 9 yes


5 BASIC_END_DATE AFKO-GLTRP - Finish (basic) date DATETIME 24 0 9 yes

6 BASIC_START_DATE AFKO-GSTRP - Order (basic) start date DATETIME 24 0 9 yes

7 BLOCK_FLAG JEST-STAT (lookup) - LKD order is lockedstatus is active (1 is active, 0 is inactive) DECIMAL 48 28 0 yes


9 CHANGE_DATE AUFK-AEDAT - Change date DATETIME 24 0 9 yes

10 CLOSE_FLAG JEST-STAT (lookup) - CLSD order is closedstatus is active (1 is active, 0 is inactive) DECIMAL 48 28 0 yes



13 CREATE_DATE PK AUFK-ERDAT - Date created DATETIME 24 0 9 yes


15 CURR_ID PK AUFK.WAERS -Order Currency NVARCSTR 5 0 0 yes




17 DAYS_COMPLT_ACTL Number of Days to actually complete a serviceorder (calcualted) DECIMAL 48 22 7 yes

18 DAYS_COMPLT_BASIC

Number of Days to Basic complete a serviceorder (calcualted) DECIMAL 48 22 7 yes

19 DAYS_COMPLT_FCST Number of Forecast Days to complete aservice order (calcualted) DECIMAL 48 22 7 yes

20 DAYS_COMPLT_SCHED

Number of Days scheduled to complete aservice order (calcualted) DECIMAL 48 22 7 yes

21 DAYS_RELEASE_ACTL

Number of Days to actually release a serviceorder (calcualted) DECIMAL 48 22 7 yes

22 DAYS_RELEASE_SCHED

Number of Days scheduled to release a serviceorder (calcualted) DECIMAL 48 22 7 yes

23 DELETE_FLAG JEST-STAT (lookup) - DLFL order is deletedstatus is active (1 is active, 0 is inactive) DECIMAL 48 28 0 yes


25 DOC_TYPE_ID AUFK-AUART - Order type NVARCSTR 4 0 0 yes


27 FCST_END_DATE AFKO.GLTPP - Finish date (forecast) DATETIME 24 0 9 yes

28 FCST_SCHED_END_DATE AFKO.GLTPS - Scheduled forecast finish DATETIME 24 0 9 yes

29 FCST_SCHED_START_DATE AFKO.GSTPS - Scheduled forecast start DATETIME 24 0 9 yes

30 FCST_START_DATE AFKO.GSTPP - Forecast start date DATETIME 24 0 9 yes

31 FINAL_CONFIRM_FLAG

JEST-STAT (lookup) - CNF order is finallyconfirmed status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes



34 HOURS_COMPLT_ACTL

Number of Hours to actually complete a serviceorder (calcualted) DECIMAL 48 22 7 yes



35 HOURS_COMPLT_BASIC

Number of Hours to Basic complete a serviceorder (calcualted) DECIMAL 48 22 7 yes

36 HOURS_COMPLT_FCST

Number of Forecast Hours to complete aservice order (calcualted) DECIMAL 48 22 7 yes

37 HOURS_COMPLT_SCHED

Number of Hours scheduled to complete aservice order (calcualted) DECIMAL 48 22 7 yes

38 INTERNAL_ORDER_ID PK AFIH-AUFNR - Work Order Number NVARCSTR 12 0 0 no



41 LOCATN_ID PK AUFK.STORT -Location within Plant NVARCSTR 10 0 0 yes



44 MINS_COMPLT_ACTL Number of Minutes to actually complete aservice order (calcualted) DECIMAL 48 22 7 yes

45 MINS_COMPLT_BASIC

Number of Minutes to Basic complete a serviceorder (calcualted) DECIMAL 48 22 7 yes

46 MINS_COMPLT_FCST Number of Forecast Minutes to complete aservice order (calcualted) DECIMAL 48 22 7 yes

47 MINS_COMPLT_SCHED

Number of Minutes scheduled to complete aservice order (calcualted) DECIMAL 48 22 7 yes


49 OBJ_ID AUFK-OBJNR - Object number NVARCSTR 22 0 0 yes

50 OPERATN_ROUTING_ID

AFKO-AUFPL - Routing number for operationsin the order NVARCSTR 10 0 0 yes

51 OPERATN_SEQ_ID AFKO.APLZT - General Counter for Order NVARCSTR 8 0 0 yes

52 ORDER_STATUS_ID AUFK.ASTNR - Order status NVARCSTR 2 0 0 yes



53 PARTL_CONFIRM_FLAG

JEST-STAT (lookup) - PCNF order is partiallyconfirmed status is active (1 is active, 0 isinactive)

DECIMAL 48 28 0 yes

54 PERSON_ID_RESP IHPA-PERNR - Personnel number responsible NVARCSTR 12 0 0 yes


56 PLANT_ID PK AUFK-WERKS - Plant (for Work Center) NVARCSTR 4 0 0 yes

57 PLANT_ID_PLAN AFIH-IWERK - Planning plant NVARCSTR 4 0 0 yes




61 PROFIT_CNTR_ID PK AUFK.PRCTR - Profit center NVARCSTR 10 0 0 yes


63 RELEASE_FLAG JEST-STAT (lookup) - REL order is releasedstatus is active (1 is active, 0 is inactive) DECIMAL 48 28 0 yes

64 RESERVATN_ID AFKO.RSNUM - Number of reservation/dependent requirement NVARCSTR 10 0 0 yes

65 SCHED_END_DATE AFKO-GLTRS - Scheduled finish DATETIME 24 0 9 yes

66 SCHED_RELEASE_DATE AFKO-FTRMS - Scheduled release date DATETIME 24 0 9 yes

67 SCHED_START_DATE AFKO-GSTRS - Scheduled start DATETIME 24 0 9 yes


69 SERVICE_ORDER_DESCR AUFK-KTEXT - Short text NVARCSTR 40 0 0 yes

70 SERVICE_ORDER_ID_PAR AFKO-MAUFNR - Superior order number NVARCSTR 12 0 0 yes




72 TECHN_COMPLT_FLAG

JEST-STAT (lookup) - TECO order istechnically completed status is active (1 isactive, 0 is inactive)

DECIMAL 48 28 0 yes


SERVICE_PERSON

Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data



Nullable

1 FIRST_NAME PA0002-VORNA - First name NVARCSTR 40 0 0 yes

2 FULL_NAME PA0002-NACHN - Last name +PA0002-VORNA - First name NVARCSTR 90 0 0 yes

3 LAST_NAME PA0002-NACHN - Last name NVARCSTR 40 0 0 yes



6 PERSON_ID PK PA0002-PERNR - Personnel number NVARCSTR 8 0 0 no

SYSTEM_CONDITION

System Condition descriptive attributes from T253M_T



Nullable



3 SYSTEM_CONDITN_DESCR T357M_T-ANLZUX - Operating status text NVARCSTR 40 0 0 yes

4 SYSTEM_CONDITN_ID PK T357M_T-ANLZU - System condition NVARCSTR 1 0 0 no



TIME_DIM

Time Dimension (Daily)



Nullable

1 CALENDAR_DATE PK Calendar Date DATETIME 24 0 9 no

2 CALENDAR_MONTH Number of Calendar Month INTEGER 4 0 0 yes

3 CALENDAR_QUARTER Calendar Quarter INTEGER 4 0 0 yes

4 CALENDAR_YEAR Calenar Year INTEGER 4 0 0 yes

5 DAY_IN_PERIOD Number of a day in a fiscal period INTEGER 4 0 0 yes

6 DAY_IN_WEEK Day of the week INTEGER 4 0 0 yes

7 FISC_PERIOD Fiscal Period of Calendar Date. Retrieved fromSAP using FI_PERIOD_DETEMINE INTEGER 4 0 0 yes

8 FISC_YEAR Fiscal Year of Calendar Date. Retrieved fromSAP using FI_PERIOD_DETEMINE INTEGER 4 0 0 yes

9 IS_WEEKEND Indicates if date falls on a weekend (1) NVARCSTR 1 0 0 yes



12 MONTH_YEAR Calendar Month and Year NVARCSTR 10 0 0 yes

13 WEEK_IN_YEAR Number of week in the year DECIMAL 48 28 0 yes



TIME_DIM_WEEKLY

Time Dimension (WEEKLY). Used for summary facts (such as BENEFIT_ENROLL_SUMMARY_FACT)



Nullable

1 CALENDAR_YEAR PK Calenar Year INTEGER 4 0 0 no



4 WEEK_END_DATE Last date in the week DATETIME 24 0 9 yes

5 WEEK_IN_YEAR PK Number of week in the year DECIMAL 48 28 0 no

6 WEEK_NAME Week - Year concatenation NVARCSTR 60 0 0 yes

7 WEEK_START_DATE First date of the week DATETIME 24 0 9 yes

8 WEEK_START_FISC_PER Fiscal Period when the week starts INTEGER 4 0 0 yes

9 WEEK_START_FISC_YEAR Fiscal Year when the week starts INTEGER 4 0 0 yes

10 WEEK_START_MONTH

Number of Calendar Month when the weekstarts INTEGER 4 0 0 yes

11 WEEK_START_QUARTER Calendar Quarter when the week starts INTEGER 4 0 0 yes



UNIT_OF_MEASURE

T006A-Material Unit of Measure attritues



Nullable



3 UOM_CODET006A.MSEH3 -- Unit of Meas. ID in LocalLanguage (External unit of measurementcommercial format (3-char))

NVARCSTR 3 0 0 yes

4 UOM_DESCR T006A-MSEHT - Measurement unit text (max.10 char.) NVARCSTR 10 0 0 yes

5 UOM_ID PK T006A-MSEHI - Unit of measurement NVARCSTR 3 0 0 no

VARIANCE_CATEGORY

Financial Variance Category descriptive attributes (ABKAT domain from DD07T)



Nullable



3 VARIANCE_CATEG_DESCR

DD07T-DDTEXT - Short text describingABAP/4 Dictionary objects (ABKAT) NVARCSTR 60 0 0 yes

4 VARIANCE_CATEG_ID PK DD07T-DOMVALUE_L - Values for domains:Single value/upper limit(ABKAT) NVARCSTR 10 0 0 no



VENDOR

LIFNR - Vendor Master



Nullable

1 ACCT_GRP_DESCR Lookup LFA1.KTOKK Acount GroupDescription in T077Y NVARCSTR 30 0 0 yes

2 ACCT_GRP_ID Vendor Account Group ID NVARCSTR 4 0 0 yes

3 ADDRESS_ID Internal Address ID from SAP NVARCSTR 10 0 0 yes

4 ALT_PAYEE_NUM LFA1.LNRZA Account number of thealternative payee NVARCSTR 10 0 0 yes

5 CITY LFA1.ORT01 City NVARCSTR 40 0 0 yes

6 COUNTRY_ID LFA1.LAND1 Country key NVARCSTR 3 0 0 yes

7 COUNTRY_NAME Country Name (Full Name) NVARCSTR 15 0 0 yes

8 CREATE_DATE LFA1.ERDAT Date on which the record wascreated DATETIME 24 0 9 yes

9 CR_INFO_ID LFA1.KRAUS Credit information number NVARCSTR 11 0 0 yes

10 CUSTOMER_ID LFA1.KUNNR Customer number NVARCSTR 10 0 0 yes

11 CUSTOMER_NAME Customer Name NVARCSTR 40 0 0 yes

12 DELETE_FLAG LFA1.LOEVM Central delete flag for masterrecord NVARCSTR 5 0 0 yes

13 DISTRICT LFA1.ORT02 District NVARCSTR 40 0 0 yes

14 FAX LFA1.TELFX Fax number NVARCSTR 40 0 0 yes


16 INDUSTRY_DESCR Lookup description of Industry LFA1.BRSCH inT016T NVARCSTR 20 0 0 yes



17 INDUSTRY_ID LFA1.BRSCH Industry key NVARCSTR 4 0 0 yes

18 LANG_ID LFA1.SPRAS Language key NVARCSTR 1 0 0 yes



21 ONE_TIME_ACCT_DESCR

Lookup description of LFA1.XCPDK - OneTime Account Indicator NVARCSTR 5 0 0 yes

22 PHONE LFA1.TELF1 First telephone number NVARCSTR 30 0 0 yes

23 PLANT_ID LFA1.WERKS Plant NVARCSTR 4 0 0 yes

24 PLANT_NAME Plant Name NVARCSTR 30 0 0 yes

25 REGION_ID LFA1.REGIO Region (State NVARCSTR 3 0 0 yes

26 REGION_NAME Region Full Name (State NVARCSTR 20 0 0 yes

27 STREET LFA1.STRAS House number and street NVARCSTR 60 0 0 yes

28 TRADING_PARTNER_ID LFA1.VBUND Trading partner ID NVARCSTR 6 0 0 yes

29 TRADING_PARTNER_NAME Trading partner Name NVARCSTR 30 0 0 yes

30 VENDOR_FULL_NAME Vendor Full name NVARCSTR 120 0 0 yes

31 VENDOR_GRP_KEY LFA1.KONZS Group key NVARCSTR 10 0 0 yes

32 VENDOR_ID PK LIFNR Vendor (creditor) account number NVARCSTR 10 0 0 no

33 VENDOR_NAME Vendor Name NVARCSTR 40 0 0 yes

34 VENDOR_NAME_01 LFA1.NAME1 Vendor Name 1 NVARCSTR 40 0 0 yes



35 VENDOR_NAME_02 LFA1.NAME2 Vendor Name 2 NVARCSTR 40 0 0 yes

36 VENDOR_NAME_03 Vendor Name 3 NVARCSTR 40 0 0 yes

37 VENDOR_NAME_04 Vendor Name 4 NVARCSTR 40 0 0 yes

38 ZIP LFA1.PSTLZ Postal code NVARCSTR 10 0 0 yes



VENDOR_BY_COMPANY

Cross-reference of LFA1 and T001 tables (Vendors and Company Codes)



Nullable

1 ACCTNG_CLERK_ID T001S.BUSAB - Accounting clerk NVARCSTR 2 0 0 yes

2 ACCTNG_CLERK_NAME T001S.SNAME - Name of Accounting Clerk NVARCSTR 30 0 0 yes

3 ACCT_GRP_DESCR T077Y.TXT30 - VENDOR Account descr(lookup) NVARCSTR 30 0 0 yes

4 ACCT_GRP_DESCR_ONE_TIME

T077Y.TXT30 - VENDOR Account descr(lookup) - One time acct NVARCSTR 30 0 0 yes

5 ACCT_GRP_ID LFA1.XCPDK - Indicator: Is the account aone-time account? NVARCSTR 4 0 0 yes

6 ACCT_GRP_ID_ONE_TIME

LFA1.KTOCK -- Reference account group forone-time account (vendor) NVARCSTR 4 0 0 yes

7 BANK_ID_HOUSE LFB1.HBKID -- ID for one house bank NVARCSTR 5 0 0 yes

8 CALENDAR_DESCR TFACT.LTEXT - Factory Calendar Description NVARCSTR 60 0 0 yes

9 CALENDAR_ID LFA1.PLKAL -- Factory calendar key NVARCSTR 2 0 0 yes

10 CHART_OF_ACCT_DESCR T004T.KTPLT - Chart of Accounts Description NVARCSTR 50 0 0 yes

11 CHART_OF_ACCT_ID T001.KTOPL - Chart of Accounts (CompanyCode) NVARCSTR 4 0 0 yes

12 CMPNY_CODE_FULL_NAME Company Code and Company Name NVARCSTR 36 0 0 yes

13 CMPNY_CODE_ID PK LFB1-BUKRS -- Company code NVARCSTR 4 0 0 no

14 CMPNY_CODE_NAME T001.BUTXT - Name of the company code orcompany NVARCSTR 25 0 0 yes

15 CR_INFO_CODE LFA1.KRAUS -- Credit information number NVARCSTR 11 0 0 yes

16 CUSTOMER_ID LFA1.KUNNR -- Customer number NVARCSTR 10 0 0 yes



17 CUSTOMER_NAME KNA1.NAME1 - Customer Name as vendor NVARCSTR 40 0 0 yes

18 DELETE_BLOCK_FLAG

LFB1.NODEL - Company Code Level DeletionBlcok NVARCSTR 1 0 0 yes

19 DELETE_BLOCK_FLAG_CENTRAL LFA1.NODEL - Central Deletion Block NVARCSTR 1 0 0 yes

20 DELETE_FLAG LFB1.LOEVM -- Deletion flag for master record NVARCSTR 1 0 0 yes

21 DELETE_FLAG_CENTRAL

LFA1.LOEVM - Central Deletion Flag forMaster Record NVARCSTR 1 0 0 yes

22 GL_ACCT_DESCR_RECONCILE

SKAT.TXT50 - Descr. of Reconciliationaccount in G/L accounting NVARCSTR 60 0 0 yes

23 GL_ACCT_ID_RECONCILE

SKB1.SAKNR - Account Code (Reconciliationaccount in G/L accounting) NVARCSTR 10 0 0 yes

24 INTL_LOCATN_NUM_01

LFA1-BBBNR -- International location number(part 1) NVARCSTR 7 0 0 yes

25 INTL_LOCATN_NUM_02

LFA1-BBBSR -- International location number(part 2) NVARCSTR 5 0 0 yes

26 LOAD_DATE Date that this row was loaded into the datawarehouse DATETIME 24 0 9 yes

27 LOAD_TIME Time that this row was loaded into the datawarehouse NVARCSTR 10 0 0 yes

28 ONETIME_ACCT_FLAG LFA1.XCPDK - One Time Account flag NVARCSTR 1 0 0 yes

29 OUR_ACCT_NUM LFB1.EIKTO -- Our account number at thevendor NVARCSTR 12 0 0 yes

30 PAYMNT_BLOCK_DESCR T008T.TEXTL - Payment Block Description NVARCSTR 20 0 0 yes

31 PAYMNT_BLOCK_FLAG_CENTRAL LFA1.SPERZ - Central Payment Block NVARCSTR 1 0 0 yes

32 PAYMNT_BLOCK_ID LFB1.ZAHLS -- Block key for payment NVARCSTR 1 0 0 yes

33 PAYMNT_TERM_DESCR

TVZBT.VTEXT - Standard Payment termdescription NVARCSTR 50 0 0 yes

34 PAYMNT_TERM_ID LFB1.ZTERM - Payment terms key NVARCSTR 4 0 0 yes



35 PLANT_ID LFA1-WERKS Plant NVARCSTR 4 0 0 yes

36 PLANT_NAME T001W.NAME1 - Plant Name NVARCSTR 30 0 0 yes

37 POR_NUM LFA1.ESRNR -- POR subscriber number NVARCSTR 11 0 0 yes

38 POST_BLOCK_FLAG LFB1.SPERR - Company Code Level PostingBlock NVARCSTR 1 0 0 yes

39 POST_BLOCK_FLAG_CENTRAL LFA1.SPERR - Central Posting Block NVARCSTR 1 0 0 yes

40 PURCH_BLOCK_FLAG_CENTRAL LFA1.SPERM - Central Purchasing Block NVARCSTR 1 0 0 yes

41 SOLE_PROPR_FLAG LFA1.STKZN -- Indicator if partner is a soleproprietor NVARCSTR 1 0 0 yes

42 TAX_JURISDIC_NUM LFA1.TXJCD -- Jurisdiction for tax calculation -tax jurisdiction code NVARCSTR 15 0 0 yes

43 TAX_NUM_01 LFA1.STCD1 -- Tax number 1 NVARCSTR 16 0 0 yes

44 TAX_NUM_02 LFA1.STCD2 -- Tax number 2 NVARCSTR 11 0 0 yes

45 VAT_REGISTRTN_NUM LFA1.STCEG -- VAT registration number NVARCSTR 20 0 0 yes

46 VENDOR_FULL_NAME LFA1.NAME1+ LFA1.LIFNR - Full Name NVARCSTR 120 0 0 yes

47 VENDOR_ID PK LFA1.LIFNR NVARCSTR 10 0 0 no

48 VENDOR_ID_ALT_PAYEE

LFA1.LNRZA -- Account number of thealternative payee NVARCSTR 10 0 0 yes

49 VENDOR_NAME LFA1.NAME1 - Vendor Name 1 NVARCSTR 40 0 0 yes



WORK_CENTER

Work center descriptions and standard capacity information from CRHD used as default by capacity planning processes



Nullable

1 BACKFLUSH_FLAG CRHD.RGEKZ - Indicator: Backflushing (1/0) INTEGER 4 0 0 yes

2 CHANGE_DATE AEDAT_GRND - Changed on DATETIME 24 0 9 yes



5 CTRL_KEY_DESCR T430T-TXT -Control Key desctiption (lookup) NVARCSTR 40 0 0 yes

6 CTRL_KEY_ID CRHD.STEUS - Control key NVARCSTR 4 0 0 yes

7 CURRENT_FLAG 1 indicates record is currently in effect (1/0) INTEGER 4 0 0 yes

8 DELETE_FLAG CRHD.LVORM - Deletion flag for work center (1/0) INTEGER 4 0 0 yes

9 FORMULA_DESCR_OTHER

TC25T-TXT - Lookup on Formula descritpionfor Other NVARCSTR 20 0 0 yes

10 FORMULA_DESCR_PROCESS

TC25T-TXT - Lookup on Formula descritpionfor Process NVARCSTR 20 0 0 yes

11 FORMULA_DESCR_SETUP

TC25T-TXT - Lookup on Formula descritpionfor Setup NVARCSTR 20 0 0 yes

12 FORMULA_DESCR_TEARDOWN

TC25T-TXT - Lookup on Formula descritpionfor TearDown NVARCSTR 20 0 0 yes

13 FORMULA_ID_OTHER CRHD.FORTN - Formula for other workcentertimes NVARCSTR 6 0 0 yes

14 FORMULA_ID_PROCESS

CRHD.FORT2 - Formula for work centerprocessing time duration NVARCSTR 6 0 0 yes

15 FORMULA_ID_SETUP CRHD.FORT1 - Formula for work center setuptime NVARCSTR 6 0 0 yes

16 FORMULA_ID_TEARDOWN

CRHD.FORT3 - Formula for work centerteardown time calculation NVARCSTR 6 0 0 yes



17 LOAD_DATE Date and time when the record is loaded intoRapid Mart DATETIME 24 0 9 yes

18 LOAD_TIME Time loaded into Rapid Mart NVARCSTR 8 0 0 yes

19 LOCATN_GRP_DESCR

TC28T-TXT - Location group desctiption(lookup) NVARCSTR 20 0 0 yes

20 LOCATN_GRP_ID CRHD.ORTGR - Location group NVARCSTR 4 0 0 yes

21 MACHINE_TYPE_DESCR Lookup machine type group description NVARCSTR 40 0 0 yes

22 MACHINE_TYPE_GRP_ID CRHD.MATYP - Machine type grouping NVARCSTR 10 0 0 yes

23 MINS_MIN_QUEUE_TIME

CRHD.ZWMIN - Minimum queue timeconverted to minutes DECIMAL 48 9 3 yes

24 MINS_STD_QUEUE_TIME

CRHD.ZWNOR - Standard queue timeconverted to minutes DECIMAL 48 9 3 yes

25 OBJ_ID CRHD.HROID - Object ID NVARCSTR 8 0 0 yes

26 ORG_UNIT_TYPE_DESCR T777O-OTEXT -Object Type Description NVARCSTR 25 0 0 yes

27 ORG_UNIT_TYPE_ID CRHD.HRTYP - Object type NVARCSTR 2 0 0 yes

28 PERSON_RESP_CODE

CRHD.VERAN - Person responsible for thework center NVARCSTR 3 0 0 yes

29 PERSON_RESP_DESCR

Lookup TC24.KTEXT - Person responsible forthe work center VERAN NVARCSTR 40 0 0 yes

30 PLANT_ID PK CRHD.WERKS - Plant NVARCSTR 4 0 0 no

31 PLANT_NAME T001W.NAME1 - lookup on Plant Name NVARCSTR 40 0 0 yes

32 STD_TEXT_KEY_CODE CRHD.KTSCH - Standard text key NVARCSTR 7 0 0 yes

33 STD_VALUE_KEY_DESCR Lookup standard value key description in TC21 NVARCSTR 30 0 0 yes

34 STD_VALUE_KEY_ID CRHD.VGWTS - Standard value key NVARCSTR 4 0 0 yes



35 SUITABILITY_DESCR T423T-TXT - Sutability( Qualificiation/WageGroup) desctiption (lookup) NVARCSTR 30 0 0 yes

36 SUITABILITY_ID CRHD.QUALF - Suitability for carrying certaintasks NVARCSTR 2 0 0 yes

37 SUPPLY_AREA_DESCR PVKT-PVBTX -Supply Area Description NVARCSTR 40 0 0 yes

38 SUPPLY_AREA_ID CRHD.PRVBE Supply area NVARCSTR 10 0 0 yes

39 TASK_LIST_USG_DESCR Lookup task list usage descripton NVARCSTR 30 0 0 yes

40 TASK_LIST_USG_ID CRHD.PLANV - Key for task list usage NVARCSTR 3 0 0 yes

41 VALID_FROM_DATE CRHD.BEGDA - Effectivity Start date DATETIME 24 0 9 yes

42 VALID_TO_DATE CRHD.ENDDA - Effectivity end date DATETIME 24 0 9 yes

43 VALUATN_AREA_ID T001W.BWKEY Valuation area lookup NVARCSTR 4 0 0 yes

44 WORK_CNTR_CATEG_DESCR

Lookup description of Work Center category inTC30T NVARCSTR 20 0 0 yes

45 WORK_CNTR_CATEG_ID CRHD.VERWE - Work center category NVARCSTR 4 0 0 yes

46 WORK_CNTR_CODE CRHD.OBJID - Work center Internal Object ID NVARCSTR 8 0 0 yes

47 WORK_CNTR_DESCR Lookup work center description in CRTX NVARCSTR 40 0 0 yes

48 WORK_CNTR_FULL_NAME

CRHD.ARBPL - Work center Code + Name(Lookup work center description in CRTX NVARCSTR 50 0 0 yes

49 WORK_CNTR_ID PK CRHD.ARBPL - Work center- Visible ID inSAP NVARCSTR 8 0 0 no

50 WORK_CNTR_LOCATN_DESCR T499S-KTEXT - Location desctiption (lookup) NVARCSTR 40 0 0 yes

51 WORK_CNTR_LOCATN_ID CRHD.STAND - Work center location NVARCSTR 10 0 0 yes



WORK_CENTER_HIER

Work center parent-child relationship from CRHH/CRHS



Nullable

1 CHILD_CODE CRHD.ARBPL Work center Code - Child NVARCSTR 8 0 0 yes

2 CHILD_DESCR Lookup work center description in CRTX forChild WC NVARCSTR 40 0 0 yes

3 CHILD_FULL_NAME Concatentaion of WC code and description forChild Node NVARCSTR 50 0 0 yes

4 CHILD_ID PK CRHS.OBJID_HO - Object ID of the resourceand CRHH.NAME - Name of hierarchy NVARCSTR 50 0 0 no

5 LOAD_DATE Load date and time into the target database DATETIME 24 0 9 yes

6 LOAD_TIME Load time into the target database NVARCSTR 8 0 0 yes

7 OWNER_ID CRHH.VERAN - Person responsible for thework center NVARCSTR 3 0 0 yes

8 OWNER_NAME Lookup TC24.KTEXT - Person responsible forthe work center VERAN NVARCSTR 40 0 0 yes

9 PARENT_CODE CRHD.ARBPL - Work center - Parent node NVARCSTR 8 0 0 yes

10 PARENT_DESCR Lookup work center description in CRTX forParent WC NVARCSTR 40 0 0 yes

11 PARENT_FULL_NAME Concatentaion of WC code and description forParent Node NVARCSTR 50 0 0 yes

12 PARENT_ID PKCRHS.OBJID_UP - ID of superior object in thehierarchy and CRHH.NAME - Name ofhierarchy

NVARCSTR 50 0 0 no

13 PLANT_ID CRHH.WERKS - Plant NVARCSTR 4 0 0 yes


15 WORK_CNTR_HIER_ID PK CRHH.OBJID - Object ID of the resource NVARCSTR 8 0 0 no

16 WORK_CNTR_HIER_NAME CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 yes



WORK_CENTER_HIER_BAD

Work center parent-child relationship from CRHH/CRHS - Invalid Records



Nullable

1 CHILD_CODE CRHD.ARBPL Work center Code - Child NVARCSTR 8 0 0 yes

2 CHILD_DESCR Lookup work center description in CRTX forChild WC NVARCSTR 40 0 0 yes

3 CHILD_FULL_NAME Concatentaion of WC code and description forChild Node NVARCSTR 50 0 0 yes

4 CHILD_ID PK CRHS.OBJID_HO - Object ID of the resourceand CRHH.NAME - Name of hierarchy NVARCSTR 50 0 0 no

5 DI_ERROR_ACTN DI Error Action NVARCSTR 1 0 0 yes

6 DI_ERROR_COLUMN DI Error Columns NVARCSTR 500 0 0 yes

7 LOAD_DATE Load date and time into the target database DATETIME 24 0 9 yes

8 LOAD_TIME Load time into the target database NVARCSTR 8 0 0 yes

9 OWNER_ID CRHH.VERAN - Person responsible for thework center NVARCSTR 3 0 0 yes

10 OWNER_NAME Lookup TC24.KTEXT - Person responsible forthe work center VERAN NVARCSTR 40 0 0 yes

11 PARENT_CODE CRHD.ARBPL - Work center - Parent node NVARCSTR 8 0 0 yes

12 PARENT_DESCR Lookup work center description in CRTX forParent WC NVARCSTR 40 0 0 yes

13 PARENT_FULL_NAME Concatentaion of WC code and description forParent Node NVARCSTR 50 0 0 yes

14 PARENT_ID PKCRHS.OBJID_UP - ID of superior object in thehierarchy and CRHH.NAME - Name ofhierarchy

NVARCSTR 50 0 0 no

15 PLANT_ID CRHH.WERKS - Plant NVARCSTR 4 0 0 yes




17 WORK_CNTR_HIER_ID PK CRHH.OBJID - Object ID of the resource NVARCSTR 8 0 0 no

18 WORK_CNTR_HIER_NAME CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 yes



WORK_CENTER_HIER_HZ

Work Center Hierarchical relationship in Horizontal format from CRHH/CRHS



Nullable

1 LEAF_LVL Work Center Hierarchy Child ID DECIMAL 48 28 0 yes

2 LOAD_DATE Load date and time - for the target database DATETIME 24 0 9 yes

3 LOAD_TIME Load time for the target database NVARCSTR 8 0 0 yes

4 LVL_00_DESCR Description for 00 Parent Node NVARCSTR 40 0 0 yes

5 LVL_00_FULL_NAME Concatentaion of WC code and description forParent Node NVARCSTR 50 0 0 yes

6 LVL_00_ID PK CRHS.OBJID_HO - Object ID of the resource NVARCSTR 8 0 0 no


















22 PLANT_ID PK CRHH.WERKS - Plant ID NVARCSTR 4 0 0 no

23 WORK_CNTR_HIER_NAME PK CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 no

24 WORK_CNTR_ID PK CRHD-ARBPL (lookup) - Work Center uniquename NVARCSTR 8 0 0 no



WORK_CENTER_HIER_VR

Work Center Hierarchical relationship in Vertical format from CRHH/CRHS



Nullable

1 CHILD_FULL_NAME KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) -Object description/name lookup NVARCSTR 50 0 0 yes

2 CHILD_ID PK CRHD-ARBPL (lookup) - Work Center uniquename for Child ID NVARCSTR 8 0 0 no

3 DEPTH Node depth in the hierarchy DECIMAL 48 28 0 yes

4 LEAF_FLAG 1 - Leaf, 0 - Root DECIMAL 48 28 0 yes

5 LOAD_DATE Load date and time - target database DATETIME 24 0 9 yes

6 LOAD_TIME Load time - target database NVARCSTR 8 0 0 yes

7 PARENT_FULL_NAME KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) -Object description/name lookup NVARCSTR 50 0 0 yes

8 PARENT_ID PK CRHD-ARBPL (lookup) - Work Center uniquename for Parent ID NVARCSTR 8 0 0 no

9 PLANT_ID PK CRHH.WERKS - Plant ID NVARCSTR 4 0 0 no

10 ROOT_FLAG 1 - Root, 0 - Leaf DECIMAL 48 28 0 yes

11 WORK_CNTR_HIER_NAME PK CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 no


xi3 rm sap pm ug en

Documents

rapid mart data

sap products

rapid mart fits

sap netweaver

sap company

sap master data reports

contents rapid mart

sap business bydesign