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.
Contents
Chapter 1 Introduction 11 What is a Rapid Mart? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Rapid Marts packages accelerate Time to Value . . . . . . . . . . . . . . . . 13 SAP BusinessObjects Rapid Marts packages architecture . . . . . . . . . 14 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Chapter 2 Overview 17
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 What you can do with this Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Supported analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Related Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Sharing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Where the Rapid Mart fits in the maintenance process . . . . . . . . . . . . . . . 25 Chapter 3 Subject Areas 27
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Plant Maintenance Process Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Technical Objects & Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 Classification & Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Maintenance Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Service Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Service Order Costs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 Service Notification Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
SAP BusinessObjects Plant Maintenance Rapid Mart XI 3.2 for SAP solutions User Guide
Contents
Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Service Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Service Operation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 Service Confirmation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Service Order Cost Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Service Master Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Chapter 4 Reports 81
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Service Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 MTBR MTTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Service Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Service Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113 Service Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Contents
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Service Order Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Service Master . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 SAP Master Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145 Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 Recommended table joins Chapter 5 Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160 165
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Universe Design Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166 Universe Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Universe Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Join Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Hierarchies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Geographic Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Time Dimension and Fiscal Period Hierarchies . . . . . . . . . . . . . . . . . 173 Material Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173 Horizontal & Vertical Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174 Hierarchy Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180 Plant Maintenance Specific Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Accounting Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 Additional Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 SAP Plant Maintenance Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187 Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189 Common Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190 Service Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Contents
Service Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206 Service Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Service Confirmation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Service Cost Summary (Horizontal) . . . . . . . . . . . . . . . . . . . . . . . . . . 216 Service Cost Summary (Vertical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219 MTBR and MTTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222 Filters & Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227 SAP Service Master Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229 SAP Service Master Universe Objects & Classes . . . . . . . . . . . . . . . 230 SAP Service Master Common Dimensions . . . . . . . . . . . . . . . . . . . . . 231 Equipment Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237 Functional Location Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . 239 SAP Service Master Filters & Techniques . . . . . . . . . . . . . . . . . . . . . 241 SAP Service Master Universe Validation . . . . . . . . . . . . . . . . . . . . . . 242 SAP Master Data Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244 Universe Objects & Classes - Master Data . . . . . . . . . . . . . . . . . . . . . 244 Universe Validation - Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Customizing the Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281 Splitting the SAP Plant Maintenance Universe . . . . . . . . . . . . . . . . . . 281 Chapter 6 Installing the Rapid Mart 283
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284 System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285 Personnel Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Rapid Mart product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287 Preparing your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Preparing Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289 Preparing Target Database Environment . . . . . . . . . . . . . . . . . . . . . . 289 Preparing Source Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 Preparing BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . 290
Contents
Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290 The Rapid Mart Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292 Install the Rapid Mart Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Create Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Install the Data Services Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Renaming the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296 Import ATL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Adjusting the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300 Using Auxiliary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307 Using ABAP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308 Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312 Installing Rapid Mart Reporting Content . . . . . . . . . . . . . . . . . . . . . . . . . 314 Import Wizard for Reporting Content BIAR File . . . . . . . . . . . . . . . . . 314 Creating Universe Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Chapter 7 Using the Rapid Mart 333
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334 Data Services automatic recovery feature . . . . . . . . . . . . . . . . . . . . . 334 Rapid Mart recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335 Execution status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 The execution status table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336 The execution status API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337 Executing a job with the Reset option . . . . . . . . . . . . . . . . . . . . . . . . 338 Extraction, transformation and loading process . . . . . . . . . . . . . . . . . . . . 338 Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Global Variable Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 340 Used in All Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 Used in 2 to 10 Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347 Used in Only 1 Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Setting Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367 Executing the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371 Initial (First) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371
Contents
Incremental (Delta) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . 372 Customizing the Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374 Chapter 8 Technical Implementation 377
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Service Notification Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378 Initial load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 381 Incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Service Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386 Service Operation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388 Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391 Service Confirmation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Service Order Cost Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397 Fact table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Service Master Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401 Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Characteristics Stage Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Fact Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403 Dimensions with Incremental Loads . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405 Functional Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Rolling Totals Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406 Optimization Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Table Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416 Data Transfer Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418 Hierarchy Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Contents
Dealing with NULL values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422 Fact Table Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423 Fiscal Periods & Time Dim Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424 Chapter 9 Documentation References 427
Data Services Documentation References . . . . . . . . . . . . . . . . . . . . . . . 428 BusinessObjects Enterprise Documentation References . . . . . . . . . . . . 428 Appendix A Rapid Mart Data Schema 431
Contents
10
Introduction
chapter
Introduction What is a Rapid Mart?
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.
12
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 companys 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 Value

Rapid 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 solutions 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 solutions 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 solutions SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions
Operational Suite:
Manufacturing Suite:
Human Capital Management (HCM) Suite:
13
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 architecture

Rapid Marts architecture is driven by SAP BusinessObjects technology. Rapid Mart Architecture:
Rapid Marts packages include the following components:
14
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.).
15
Introduction About this document
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 usersinformation 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
16
Overview
chapter
Overview Overview
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 Mart

The 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.
18
Overview Supported analyses
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 Technical Objects (Equipment or Functional Location) Type of analysis Equipment Reliability Measures available in the Rapid Mart
Equipment and components that require most frequent maintenance work Maintenance ranking by manufacturer, vendor, or year of production Technical object analysis by selected characteristics and their values Grouping by functional location and equipment class Life time performance of a piece of equipment Straight time versus overtime ratio Internal versus external labor analysis Backlog maintenance hours by order Operational analysis by company, plant, material group, etc.
Classification
Object history Service Orders Maintenance hours
Operational Analysis
19
Overview Supported analyses
Business function
Type of analysis Confirmations Planning efficiency
Measures available in the Rapid Mart
confirmation performance by Activity, Company Code, fiscal year, etc. Variance between actual and forecast work by planning group Ratio of scheduled versus completed orders Order execution by priority Yearly cost trends by category Detailed estimated/planned/actual costs by technical objects Total actual revenue Planned versus actual costs by labor and material Damage analysis by technical object Downtime by functional location and responsible party System conditions Time between repairs Average time between repair Time to repair Average time to repair
Maintenance costs
Notifications
Failures
MTBR and MTTR
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.
20
Overview Related Rapid Marts
Related Rapid Marts

Each 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.
21
Overview SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions schema
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):
22
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.
23
Plant Maintenance Rapid Mart Schema (3 of 3):
24
Overview Where the Rapid Mart fits in the maintenance process
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.
25
Overview Where the Rapid Mart fits in the maintenance process
Plant Maintenance Process:.
26
Subject Areas
chapter
Subject Areas Overview
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
28
Subject Areas Plant Maintenance Process Overview
Plant Maintenance Process Overview

Plant 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.
Integration
Through 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 & Systems

Technical 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.
29
Individual pumps (installed as equipment) form the next level down. Finally, a pump may be composed of individual components forming an equipment hierarchy. Heres how the structure would look: Filtration Company (Top Level, Functional Location Hierarchy)
Plant 1
Pump Station 1
Pump 1 (equipment) Pump 2 (equipment) Pump 3 (equipment) Pump 4 (equipment)
Pump Station 2
Plant 2, etc... Pump Housing
Pump 1 (Top Level, Equipment Hierarchy)
Motor
Power supply Gear box
Piping Filters Inlet valve Outlet valve
Holding tank
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 & Characteristics

When 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.
30
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 Notifications
These 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).
31
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, weve implemented three catalog types as distinct dimensions that are associated with the notifications. Catalog Type 5 B C Description Causes Object parts Overview of damage Rapid Mart Dimension Malfunction Cause Malfunction Object Part Malfunction Damage
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 Orders
Maintenance 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.
32
A service order is subdivided into operations and confirmations.
Service Operations
You 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 companys 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 Confirmations
A 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
33
Which technical data should be retained
Confirmations 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 completed
Confirmations 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 Confirmation As 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 Costs

SAP 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.
34
Subject Areas Service Notification Section
Service Notification Section

The 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 malfunction
Maintenance 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 - items
The target table in the Rapid Mart schema is NOTIFICATION_FACT.
35
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:
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 processing

The section captures the following dimensional attributes and their associated dimension tables: Attribute Name Business Area Classification Hierarchy Dimension Tables BUSINESS_AREA CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR COMPANY_CODE CONTROLLING_AREA
Company Code Controlling Area
36
Attribute Name Cost Center & Hierarchy
Dimension Tables COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_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_HIER_BAD MAINTENANCE_PRIORITY MALFUNCTION_CAUSE, MALFUNCTION_DAMAGE, MALFUNCTION_OBJ_PART MALFUNCTION_EFFECT MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT NOTIFICATION DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY PLANNING_GROUP PLANT PLANT_LOCATION SERVICE_PERSON TIME_DIM
Equipment & Hierarchy
Functional Location & Hierarchy
Internal Order & Hierarchy
Maintenance Priority Malfunction Catalogs
Malfunction Effect Material & Product Hierarchy Material By Plant Notification Notification Category Notification Type Planning Group Plant Plant Location Service Person Time Dimension
37
Attribute Name Unit Of Measure Work Center & Hierarchy
Dimension Tables UNIT_OF_MEASURE WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact Table Fields

The 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:
Fact Table Name MTBR_MTTR_FACT Column Name DAYS_DOWNTIME DAYS_UPTIME HOURS_DOWNTIME HOURS_UPTIME MINS_DOWNTIME MINS_UPTIME NOTIFICATION_FACT DAYS_COMPLT DAYS_DOWNTIME DAYS_REQ HOURS_COMPLT HOURS_DOWNTIME HOURS_REQ MINS_COMPLT MINS_DOWNTIME MINS_REQ QTY_DOWNTIME Description Calculated Days of downtime (as Malfunction end Malfunction start) Calculated Days of uptime: Prev Malfunction end date Malfunction start date Calculated hours of downtime (as Malfunction end Malfunction start) Calculated hours of uptime: Prev Malfunction end date Malfunction start date Calculated minutes of downtime (as Malfunction end Malfunction start) Calculated minutes of uptime: Prev Malfunction end date - Malfunction start date Number of Days to eliminate malfunction (calculated) Number of malfunction days (calculated) Number of Required days to fix malfunction (calculated) Number of Hours to eliminate malfunction (calculated) Number of malfunction Hours (calculated) Number of Required Hours to fix malfunction (calculated) Number of Hours to eliminate malfunction (calculated) Number of malfunction Minutes (calculated) Number of Required Minutes to fix malfunction (calculated) QMIH-AUSZT - Downtime
38
Additionally, several flags are employed to capture notification status on the NOTIFICATION_FACT table: Column Name BREAKDOWN_FLAG COMPLT_FLAG Description EQIH-MSAUS - Breakdown indicator. Set to 1 if there is a breakdown JEST-STAT (lookup) - NOCO notification completed status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - NOPR notification is progress status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - OSNO outstanding notification status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - NOPO notification postponed status is active (1 is active, 0 is inactive) QMFE-KZLOESCH - Indicator: delete data record. Set to 1 if an item is deleted JEST-STAT (lookup) - DLFL notification completed status is active (1 is active, 0 is inactive)
IN_PROGRESS_FLAG
OUTSTANDNG_FLAG
POSTPONE_FLAG
ITEM_DELETE_FLAG NOTIFICTN_DELETE_FLAG
39
Rapid Mart data

The following diagrams shows the tables in the notification section organized as a Star Schema: Notification Fact (1 of 2):
40
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
41
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 & Hierarchy 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?
You can use this section to answer questions such as:
42
Subject Areas Service Order Section
Service Order Section

The 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 objects status from defective to refurbished. The refurbishment process changes the value of the technical object.
43
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

This section captures the following dimensional attributes and their associated dimension tables: Attribute Name Business Area Classification Hierarchy Dimension Tables BUSINESS_AREA CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR COMPANY_CODE CONTROLLING_AREA COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD CUSTOMER DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY
Company Code Controlling Area Cost Center & Hierarchy
Customer Document Category Document Type
44
Attribute Name Equipment & Hierarchy
Dimension Tables EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_AREA, FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BAD, 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_HIER_BAD INTERNAL_ORDER_STATUS MAINTENANCE_ACTIVITY_TYPE MAINTENANCE_PRIORITY MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT CURRENCY NOTIFICATION PLANNING_GROUP PLANT PLANT_LOCATION PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT, PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ, PROJECT_ELEMENT_HIER_VR, PROJECT_ELEMENT_HIER_BAD SERVICE_PERSON
Functional Area & 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
45
Attribute Name System Condition Time Dimension Work Center & Hierarchy
Dimension Tables SYSTEM_CONDITION TIME_DIM WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact Table Fields

The 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: Column Name DAYS_COMPLT_ACTL DAYS_COMPLT_BASIC DAYS_COMPLT_FCST DAYS_COMPLT_SCHED DAYS_RELEASE_ACTL DAYS_RELEASE_SCHED HOURS_COMPLT_ACTL HOURS_COMPLT_BASIC HOURS_COMPLT_FCST HOURS_COMPLT_SCHED MINS_COMPLT_ACTL Description Number of Days to actually complete a service order (calculated) Number of Days to Basic complete a service order (calculated) Number of Forecast Days to complete a service order (calculated) Number of Days scheduled to complete a service order (calculated) Number of Days to actually release a service order (calculated) Number of Days scheduled to release a service order (calculated) Number of Hours to actually complete a service order (calculated) Number of Hours to Basic complete a service order (calculated) Number of Forecast Hours to complete a service order (calculated) Number of Hours scheduled to complete a service order (calculated) Number of Minutes to actually complete a service order (calculated)
46
Column Name MINS_COMPLT_BASIC MINS_COMPLT_FCST MINS_COMPLT_SCHED
Description Number of Minutes to Basic complete a service order (calculated) Number of Forecast Minutes to complete a service order (calculated) Number of Minutes scheduled to complete a service order (calculated)
The measures are based on different calculations between date fields on the SERVICE_ORDER_FACT table: Column Name ACTL_END_DATE ACTL_RELEASE_DATE ACTL_START_DATE BASIC_END_DATE BASIC_START_DATE FCST_END_DATE FCST_SCHED_END_DATE FCST_START_DATE SCHED_END_DATE SCHED_RELEASE_DATE SCHED_START_DATE Description AFKO.GETRI - Confirmed order finish date AFKO-FTRMI - Actual release date (Last Operation is Released) AFKO-GSTRI - Actual start date (First Operation is Started) AFKO-GLTRP - Finish (basic) date AFKO-GSTRP - Order (basic) start date AFKO.GLTPP - Finish date (forecast) AFKO.GLTPS - Scheduled forecast finish AFKO.GSTPP - Forecast start date AFKO-GLTRS - Scheduled finish AFKO-FTRMS - Scheduled release date AFKO-GSTRS - Scheduled start
FCST_SCHED_START_DATE AFKO.GSTPS - Scheduled forecast start
Additionally, several flags are employed to capture status on the SERVICE_ORDER_FACT table: Column Name BLOCK_FLAG CLOSE_FLAG DELETE_FLAG Description JEST-STAT (lookup) - LKD order is locked status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - CLSD order is closed status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - DLFL order is deleted status is active (1 is active, 0 is inactive)
47
Column Name FINAL_CONFIRM_FLAG
Description JEST-STAT (lookup) - CNF order is finally confirmed status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - PCNF order is partially confirmed status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - REL order is released status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - TECO order is technically completed status is active (1 is active, 0 is inactive)
PARTL_CONFIRM_FLAG
RELEASE_FLAG
TECHN_COMPLT_FLAG
Rapid Mart data

The following diagram shows the tables in the Service Order section organized as a Star Schema.
48
Service Orders:.
49
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
50
Subject Areas Service Operation Section
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 Section

The 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 operation
The 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.
51

This section captures the following dimensional attributes and their associated dimension tables: Attribute Name Activity & Hierarchy Dimension Tables ACTIVITY, ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD BUSINESS_AREA 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_CENTER_HIER_BAD COST_ELEMENT, COST_ELEMENT_HIER, COST_ELEMENT_HIER_HZ, COST_ELEMENT_HIER_VR, COST_ELEMENT_HIER_BAD CUSTOMER EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_AREA, FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BAD, FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER, FUNCTIONAL_LOCATION_HIER_HZ, FUNCTIONAL_LOCATION_HIER_VR
Business Area Chart Of Accounts Classification Hierarchy
Company Code Control Key Controlling Area Cost Center & Hierarchy
Cost Element & Hierarchy
Customer Equipment & Hierarchy
52
Attribute Name Internal Order & Hierarchy
Dimension Tables INTERNAL_ORDER, INTERNAL_ORDER_HIER, INTERNAL_ORDER_HIER_HZ, INTERNAL_ORDER_HIER_VR, INTERNAL_ORDER_HIER_BAD MAINTENANCE_ACTIVITY_TYPE MAINTENANCE_PRIORITY MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT CURRENCY NOTIFICATION OBJECT_CLASS OBJECT_TYPE OPERATION_SUITABILITY PLANNING_GROUP PLANT PLANT_LOCATION PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT, PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ, PROJECT_ELEMENT_HIER_VR, PROJECT_ELEMENT_HIER_BAD DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY SYSTEM_CONDITION TIME_DIM UNIT_OF_MEASURE VENDOR
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
Service Order Category Service Order Type System Condition Time Dimension Unit Of Measure Vendor
53
Attribute Name Vendor By Company Work Center & Hierarchy
Dimension Tables VENDOR_BY_COMPANY WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact Table Fields The section contains the following measures. Note: To report durations, measures are in time units rather than monetary currency or quantities: Column Name AMT_COST_MTRL AMT_COST_TTL DAYS_EXECUTN_ACTL Description AFVC.MAT_PRKST - Material planning in networks: primary costs AFVC.PRKST - Total Costs in the activity Planned Calculated Days of Operation execution/startup time (as Actual Start and Actual End datetime) Calculated Days of Operation execution/startup time (as Sched Start and Sched End datetime) Calculated Hours of Operation execution/startup time (as Actual Start and Actl End datetime) Calculated Hours of Operation execution/startup time (as Sched Start and Sched End datetime) Calculated minutes of Operation execution/startup time (as Actual Start and Actual End datetime) Calculated minutes of Operation execution/startup time (as Sched Start and Sched End datetime) AFVV.DAUNO - Normal duration of the activity AFVV-ISMNW - Actual work
DAYS_EXECUTN_SCHED
HOURS_EXECUTN_ACTL
HOURS_EXECUTN_SCHED
MINS_EXECUTN_ACTL
MINS_EXECUTN_SCHED
QTY_DURTN QTY_WORK_ACTL
54
Column Name QTY_WORK_FCST QTY_WORK_SCHED
Description AFVV-ORMNW - Forecasted work (actual + remaining) AFVV-ARBEI - Work involved in the activity
The following dates are used for duration calculations: Column Name ACTL_END_DATE Description AFVV-IEDD - Actual finish: Execution (date) + AFVV-ISDZ - AFVV-IEDZ - Actual finish: Execution (time) AFVV-ISDD - Actual start: Execution (date) + AFVV-ISDZ - Actual start: Execution/setup (time) AFVV.FSEDD - Earliest scheduled finish: Execution (date) + AFVV.FSEDZ - Earliest scheduled finish: Execution (time) AFVV.FSAVD - Earliest scheduled start: Execution (date) + AFVV.FSAVZ - Earliest scheduled start: Execution (time)
ACTL_START_DATE
SCHED_END_DATE
SCHED_START_DATE
Additionally, several flags are employed to capture status on the SERVICE_OPERATION_FACT table: Column Name COMPLT_FLAG COSTNG_FLAG DELETE_FLAG Description AFVC-LEKNW - Indicator showing no remaining work expected if set to 1 AFVC.SELKZ - Selection indicator for costing line items JEST-STAT (lookup) - DEL operation is deleted status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - CNF operation is finally confirmed status is active (1 is active, 0 is inactive) JEST-STAT (lookup) -PCNF operation is partially confirmed status is active (1 is active, 0 is inactive)
FINAL_CONFIRM_FLAG
PARTL_CONFIRM_FLAG
55
Column Name RELEASE_FLAG
Description JEST-STAT (lookup) - REL operation is released status is active (1 is active, 0 is inactive) JEST-STAT (lookup) - TECO operation is technically completed status is active (1 is active, 0 is inactive)
TECHN_COMPLT_FLAG
56
Rapid Mart data

The following diagram shows the tables in the Service Operations section organized as a star schema Service Operations:
57
Analysis
With the tables in this section, you can analyze maintenance Service Orders along several dimensions:

58
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 Areas Service Confirmation Section
Unit Of Measure Vendor Vendor By Company Work Center & Hierarchy 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 Section

The 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)
59
SAP solutions sets a Service Orders status to partially confirmed when at least one confirmation has been entered for an operation in that Service Order. SAP solutions sets a Service Orders 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 confirmations
Note 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.

The section captures the following dimensional attributes and their associated dimension tables: Attribute Name Activity & Hierarchy Dimension Tables ACTIVITY, ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD BUSINESS_AREA CAPACITY CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR COMPANY_CODE CONTROLLING_AREA
Business Area Capacity Classification Hierarchy
Company Code Controlling Area
60
Attribute Name Cost Center & Hierarchy
Dimension Tables COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD CUSTOMER EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_AREA, FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BAD, 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_HIER_BAD INTERNAL_ORDER_STATUS MAINTENANCE_ACTIVITY_TYPE MAINTENANCE_PRIORITY MATERIAL_BY_PLANT MATERIAL, PRODUCT_HIERARCHY CURRENCY NOTIFICATION OPERATION_SUITABILITY PLANNING_GROUP PLANT PLANT_LOCATION
Customer Equipment & 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
61
Attribute Name Profit Center & Hierarchy
Dimension Tables PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT, PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ, PROJECT_ELEMENT_HIER_VR, PROJECT_ELEMENT_HIER_BAD DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY SERVICE_PERSON SYSTEM_CONDITION TIME_DIM UNIT_OF_MEASURE WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Service Order Category Service Order Type Service Person System Condition Time Dimension Unit Of Measure Work Center & Hierarchy
Fact Table Fields

The SERVICE_CONFIRMATION_FACT table contains the following measures: Column Name DAYS_COMPLT_FCST DAYS_EXECUTN HOURS_COMPLT_FCST HOURS_EXECUTN MINS_COMPLT_FCST Description Calculated Days to complete the operation (as Forecast end - Forecast start) Calculated days of execution (as Execution Start end - Execution start) Calculated hours to complete the operation (as Forecast end - Forecast start) Calculated hours of execution (as Execution Start end - Execution start) Calculated minutes to complete the operation (as Forecast end - Forecast start)
62
Column Name MINS_EXECUTN QTY_DURTN_ACTL QTY_WORK_ACTL QTY_WORK_REMAIN
Description Calculated minutes of execution (as Execution Start end - Execution start) AFRU.IDAUR - Actual duration for confirmation AFRU-ISMNW - Actual work (ifthenelse function call) AFRU-OFMNW - Remaining work
The following dates are used for duration calculations: Column Name EXECUTN_END_DATE Description AFRU-IEDD - Confirmed date for execution finish + AFRU-IEDZ - Confirmed time for Execution finish AFRU-ISDD - Confirmed date for start of execution) + AFRU-ISDZ - Confirmed time for Execution start AFRU.PEDD - Forecast finish date of operation from confirmation) + AFRU.PEDZ - Forecast finish time of operation from confirmation
EXECUTN_START_DATE
FCST_END_DATE
Additionally, several flags are employed to capture status on the SERVICE_CONFIRMATION_FACT table: Column Name FINAL_CONFIRMATN_FLAG NO_REMAIN_WORK_FLAG POST_OPEN_RESERVATN_ FLAG Description AFRU-AUERU - Indicator: Partial/final confirmation AFRU-LEKNW - Indicator showing no remaining work expected AFRU.AUSOR - Post open reservations
63
Rapid Mart data

The following diagram shows some of the tables in the Service Confirmation section represented in Star Schema format. Service Confirmations:
64
Analysis
With 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
65
Subject Areas Service Order Cost Section
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 Section

The 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) module
SAP 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.
66
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 Format
The 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.

This section captures the following dimensional attributes and their associated dimension tables: Attribute Name Business Activity Business Area Classification Hierarchy Dimension Tables BUSINESS_ACTIVITY BUSINESS_AREA CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR COMPANY_CODE CONTROLLING_AREA COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR
Equipment & hierarchy
67
Attribute Name Financial Record Category Financial Record Type Fiscal Period Functional Area & Hierarchy
Dimension Tables FINANCIAL_RECORD_CATEGORY FINANCIAL_RECORD_TYPE FISC_PERIOD, FISC_PERIOD_STAGE FUNCTIONAL_AREA, FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BAD, 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_HIER_BAD MAINTENANCE_ACTIVITY_TYPE MAINTENANCE_PRIORITY MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT CURRENCY PLANT PLANT_LOCATION PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT, PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ, PROJECT_ELEMENT_HIER_VR, PROJECT_ELEMENT_HIER_BAD DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY
Maintenance Activity Type Maintenance Priority Material & Product Hierarchy Material By Plant Monetary Currency Plant Plant Location Profit Center & Hierarchy
Service Order Category Service Order Type
68
Attribute Name System Condition Variance Category Work Center & Hierarchy
Dimension Tables SYSTEM_CONDITION VARIANCE_CATEGORY WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact Table Fields

The section contains the following measures: SERVICE_COST_SUMMARY_FACT_HZ:
Column Name AMT_CR_PER00_TRX AMT_CR_PER01_TRX AMT_CR_PER02_TRX AMT_CR_PER03_TRX AMT_CR_PER04_TRX AMT_CR_PER05_TRX AMT_CR_PER06_TRX AMT_CR_PER07_TRX AMT_CR_PER08_TRX AMT_CR_PER09_TRX AMT_CR_PER10_TRX AMT_CR_PER11_TRX AMT_CR_PER12_TRX AMT_CR_PER13_TRX AMT_CR_PER14_TRX AMT_CR_PER15_TRX AMT_CR_PER16_TRX AMT_CR_QTR01_TRX AMT_CR_QTR02_TRX AMT_CR_QTR03_TRX SERVICE_COST_SUMMARY_HZ Description PMCO-WRT00 - Period Credit value in ledger currency PMCO-WRT01 - Period Credit value in ledger currency PMCO-WRT02 - Period Credit value in ledger currency PMCO-WRT03 - Period Credit value in ledger currency PMCO-WRT04 - Period Credit value in ledger currency PMCO-WRT05 - Period Credit value in ledger currency PMCO-WRT06 - Period Credit value in ledger currency PMCO-WRT07 - Period Credit value in ledger currency PMCO-WRT08 - Period Credit value in ledger currency PMCO-WRT09 - Period Credit value in ledger currency PMCO-WRT10 - Period Credit value in ledger currency PMCO-WRT11 - Period Credit value in ledger currency PMCO-WRT12 - Period Credit value in ledger currency PMCO-WRT13 - Period Credit value in ledger currency PMCO-WRT14 - Period Credit value in ledger currency PMCO-WRT15- Period Credit value in ledger currency PMCO-WRT16 - Period Credit value in ledger currency PMCO-WRT00 through 03 - Quarter Credit value in ledger currency PMCO-WRT04 through 06 - Quarter Credit value in ledger currency PMCO-WRT07 through 09 - Quarter Credit value in ledger currency
69
Column Name AMT_CR_QTR04_TRX AMT_CR_YTD_TRX AMT_DR_PER00_TRX AMT_DR_PER01_TRX AMT_DR_PER02_TRX AMT_DR_PER03_TRX AMT_DR_PER04_TRX AMT_DR_PER05_TRX AMT_DR_PER06_TRX AMT_DR_PER07_TRX AMT_DR_PER08_TRX AMT_DR_PER09_TRX AMT_DR_PER10_TRX AMT_DR_PER11_TRX AMT_DR_PER12_TRX AMT_DR_PER13_TRX AMT_DR_PER14_TRX AMT_DR_PER15_TRX AMT_DR_PER16_TRX AMT_DR_QTR01_TRX AMT_DR_QTR02_TRX AMT_DR_QTR03_TRX AMT_DR_QTR04_TRX AMT_DR_YTD_TRX
SERVICE_COST_SUMMARY_HZ Description PMCO-WRT10 through 16 - Quarter Credit value in ledger currency PMCO-WRT01 through 16 - Year Credit value in ledger currency PMCO-WRT00 - Period Debit value in ledger currency PMCO-WRT01 - Period Debit value in ledger currency PMCO-WRT002 - Period Debit value in ledger currency PMCO-WRT03 - Period Debit value in ledger currency PMCO-WRT04 - Period Debit value in ledger currency PMCO-WRT05 - Period Debit value in ledger currency PMCO-WRT06 - Period Debit value in ledger currency PMCO-WRT07 - Period Debit value in ledger currency PMCO-WRT08 - Period Debit value in ledger currency PMCO-WRT09 - Period Debit value in ledger currency PMCO-WRT10 - Period Debit value in ledger currency PMCO-WRT11 - Period Debit value in ledger currency PMCO-WRT12 - Period Debit value in ledger currency PMCO-WRT13 - Period Debit value in ledger currency PMCO-WRT14 - Period Debit value in ledger currency PMCO-WRT15 - Period Debit value in ledger currency PMCO-WRT16 - Period Debit value in ledger currency PMCO-WRT00 through 03 - Quarter Debit value in ledger currency PMCO-WRT04 through 06 - Quarter Debit value in ledger currency PMCO-WRT07 through 09 - Quarter Debit value in ledger currency PMCO-WRT10 through 16 - Quarter Debit value in ledger currency PMCO-WRT01 through 16 - Year Debit value in ledger currency
SERVICE_COST_SUMMARY_FACT_VR
Column Name AMT_CR_QTD_TRX AMT_CR_TRX SERVICE_COST_SUMMARY_FACT_VR Description PMCO-WRT01 through 16 - QTD Credit value in ledger currency 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
70
Column Name AMT_CR_YTD_TRX AMT_DR_QTD_TRX AMT_DR_TRX
SERVICE_COST_SUMMARY_FACT_VR Description PMCO-WRT01 through 16 - YTD Credit value in ledger currency PMCO-WRT01 through 16 - QTD Debit value in ledger currency 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 PMCO-WRT01 through 16 - YTD Debit value in ledger currency PMCO-WRT01 through 16 - Period begin balance value in ledger currency
AMT_DR_YTD_TRX AMT_PER_BEGIN_TRX
AMT_PER_ROLLING_TRX Rolling Total Balance - Transaction Currency AMT_PTD_TRX Period Beginning Balance - Transaction Currency
Rapid Mart data

The following diagrams shows some of the tables in the Service Order cost section as Star Schemas.
71
Service Cost Section - Horizontal (1 of 2):
72
Service Cost Section - Vertical (2 of 2):
Analysis
With 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
73
Subject Areas Service Master Section
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 & Hierarchy 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 Section

This 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.
74
The section contains two fact tables:
FUNCTIONAL_LOCATION_CHAR_FACT EQUIPMENT_CHAR_FACT
These are populated by joining characteristics with either the functional location or equipment. The source tables in SAP solutions are
FUNCTIONAL_LOCATION_CHAR_FACT -

1. 2.
IFLOT - Functional Location (Table) ILOA - PM Object Location and Account Assignment AUSP - Characteristic Values CABN - Characteristics TCLA - Class Types EQUI - Equipment master data ILOA - PM Object Location and Account Assignment EQUZ - Equipment time segment AUSP - Characteristic Values CABN - Characteristics TCLA - Class Types
EQUIPMENT_CHAR_FACT -
The section runs these steps: Runs the components to load the Equipment and Functional Location dimension tables (EQUIPMENT, FUNCTIONAL_LOCATION). 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. The CHARACTERISTIC_STAGE table is joined with the EQUIPMENT table to produce EQUIPMENT_CHAR_FACT. The CHARACTERISTIC_STAGE table is joined with the FUNCTIONAL_LOCATION table to produce FUNCTIONAL_LOCATION_CHAR_FACT.
3. 4.
75

This section also captures these dimensional attributes and their associated dimensions: Attribute Name Business Area Classification Hierarchy Dimension Tables BUSINESS_AREA CLASSIFICATION_HIER, CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR COMPANY_CODE CONTROLLING_AREA COST_CENTER, COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER, FUNCTIONAL_LOCATION_HIER_HZ, FUNCTIONAL_LOCATION_HIER_VR MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT PLANNING_GROUP PLANT PLANT_LOCATION SERVICE_PERSON TIME_DIM UNIT_OF_MEASURE VENDOR VENDOR_BY_COMPANY
Equipment & Hierarchy
Material & Product Hierarchy Material By Plant Planning Group Plant Plant Location Service Person Time Dimension Unit Of Measure Vendor Vendor By Company
76
Fact Table Fields

The section contains no measures of monetary amounts or quantities. However these fields are key for characteristic analysis, and are available in both fact tables: Column Name CHARACTSTC_DESCR Description CABNT-ATBEZ (lookup) - Characteristic description AUSP-ATINN - Internal characteristic CABN-ATNAM (lookup) - Characteristic unique name AUSP-ATWRT- Characteristic value AUSP-KLART - Characteristic Class type AUSP.ATFLV - Derived Date from and Time From bucket AUSP-ATFLV - Tolerance from AUSP.ATFLB - Derive Date To and Time To bucket AUSP-ATFLB - Tolerance to CABN-AMZDZ - Number of decimal places
CHARACTSTC_FORMAT CABN-ATFOR - Characteristic data type CHARACTSTC_ID CHARACTSTC_NAME CHARACTSTC_VALUE CLASS_TYPE_ID VALID_FROM_DATE VALID_FROM_VALUE VALID_TO_DATE VALID_TO_VALUE VALUE_SCALE
Rapid Mart data

The following diagrams show both fact tables and associated dimensions in Star Schema format:
77
Equipment Characteristics (1 of 2):
Functional Location Characteristics (2 of 2):
78
Analysis
You 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 Company 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
Typical queries for this section include:
79
80
Reports
chapter
Reports Overview
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 Master
SAP 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 Notification
The 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.
Reports
Sample Reports for the Notifications include:
Notification Listing Notification Details
82
Reports Service Notification
Notification Statistics Equipment Failures Analysis
Notification Listing
View 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.
Listing
View notification listing. Notification Id is a hyperlink to the Notification Details report.
83
Details
View notification details for all notifications in the result set.
Report SQL
SELECT 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),
84
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 FROM COMPANY_CODE, TIME_DIM TIME_DIM_NOTIFICTN, NOTIFICATION_FACT, SERVICE_PERSON, DOCUMENT_TYPE NOTIFICTN_DOC_TYPE, EQUIPMENT WHERE ( TIME_DIM_NOTIFICTN.CALENDAR_DATE=NOTIFICATION_FACT.NO TIFICTN_DATE ) AND ( COMPANY_CODE.CMPNY_CODE_ID=NOTIFICATION_FACT.CMPNY_ CODE_ID ) AND ( SERVICE_PERSON.PERSON_ID=NOTIFICATION_FACT.PERSON_ID_RE SP ) 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,
85
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 Details
View Notification detail information for the selected Notification Id.
Report SQL
All report SQL is located in the Rapid Mart installation directory under \Sample\DML.
86
Notification Statistics
View Notification statistics and trend information by Functional Location for the selected Company Code and Calendar Year.
Summary
View notification days complete and days downtime statistics by functional location.
87
Trend by Functional Location

View statistics as a trend by functional location.
Calculations
Days Complete % Mix = Percentage([NOTIFCTN - Days Complete]) Days Downtime % Mix = Percentage([NOTIFCTN - Days Downtime])
Report SQL
Equipment Failures Analysis

View summary of equipment failures for each functional location by Plant for a selected Company Code and Calendar Year.
88
Statistics
View equipment failure statistics by plant.
89
Listing
View equipment failure notifications by plant.
Report SQL
Recommended Table Joins

To 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 NOTIFICATION_FACT NOTIFICATION_FACT Dimension Table BUSINESS_AREA Join Expression BUSINESS_AREA.BUS_AREA_ID=NOTIFICATION_ FACT.BUS_AREA_ID
CLASSIFICATION_HIER_ NOTIFICATION_FACT.EQUIPMNT_ID = HZ CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ NOTIFICATION_FACT.FUNCTNL_LOCATN_ID HZ =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003'
NOTIFICATION_FACT
90
Fact Table NOTIFICATION_FACT
Dimension Table
Join Expression
CLASSIFICATION_HIER_ NOTIFICATION_FACT.EQUIPMNT_ID = VR CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ NOTIFICATION_FACT.FUNCTNL_LOCATN_ID VR =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' COMPANY_CODE CONTROLLING_AREA COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=NOTIFICATI ON_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=NOTIFICA TION_FACT.CTRL_AREA_ID NOTIFICATION_FACT.COST_CNTR_ID=COST_CE NTER.COST_CNTR_ID and NOTIFICATION_FACT.CTRL_AREA_ID=COST_CEN TER.CTRL_AREA_ID
NOTIFICATION_FACT
NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT
NOTIFICATION_FACT
COST_CENTER_HIER_H NOTIFICATION_FACT.CTRL_AREA_ID=COST_CEN Z TER_HIER_HZ.CTRL_AREA_ID and NOTIFICATION_FACT.COST_CNTR_ID=COST_CE NTER_HIER_HZ.COST_CNTR_ID COST_CENTER_HIER_V NOTIFICATION_FACT.CTRL_AREA_ID=COST_CEN R TER_HIER_VR.CTRL_AREA_ID and NOTIFICATION_FACT.COST_CNTR_ID=COST_CE NTER_HIER_VR.CHILD_ID DOCUMENT_CATEGORY DOCUMENT_CATEGORY.DOC_CATEG_ID = NOTIFICATION_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'NOTIFICTN' DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=NOTIFICATIO N_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=NOTIFICATION _FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'NOTIFICTN' NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT. EQUIPMNT_ID NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT _HIER_HZ.EQUIPMNT_ID NOTIFICATION_FACT.EQUIPMNT_ID=EQUIPMENT _HIER_VR.CHILD_ID NOTIFICATION_FACT.FUNCTNL_LOCATN_ID=FUN CTIONAL_LOCATION.FUNCTNL_LOCATN_ID NOTIFICATION_FACT.FUNCTNL_LOCATN_ID=FUN CTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCAT N_ID NOTIFICATION_FACT.FUNCTNL_LOCATN_ID=FUN CTIONAL_LOCATION_HIER_VR.CHILD_ID NOTIFICATION_FACT.INTERNAL_ORDER_ID=INTE RNAL_ORDER.INTERNAL_ORDER_ID
NOTIFICATION_FACT
NOTIFICATION_FACT
NOTIFICATION_FACT
NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ FUNCTIONAL_LOCATIO N_HIER_VR INTERNAL_ORDER
NOTIFICATION_FACT NOTIFICATION_FACT
91
Fact Table NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT
Dimension Table INTERNAL_ORDER_HIE R_HZ INTERNAL_ORDER_HIE R_VR MAINTENANCE_PRIORI TY
Join Expression NOTIFICATION_FACT.INTERNAL_ORDER_ID=INTE RNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID NOTIFICATION_FACT.INTERNAL_ORDER_ID=INTE RNAL_ORDER_HIER_VR.CHILD_ID MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID=N OTIFICATION_FACT.PRIORITY_TYPE_ID and MAINTENANCE_PRIORITY.PRIORITY_ID=NOTIFIC ATION_FACT.PRIORITY_ID NOTIFICATION_FACT.CAUSE_ID=MALFUNCTION_ CAUSE.CAUSE_ID and NOTIFICATION_FACT.CAUSE_GRP_ID=MALFUNC TION_CAUSE.CAUSE_GRP_ID NOTIFICATION_FACT.DAMAGE_ID=MALFUNCTIO N_DAMAGE.DAMAGE_ID and NOTIFICATION_FACT.DAMAGE_GRP_ID=MALFUN CTION_DAMAGE.DAMAGE_GRP_ID
NOTIFICATION_FACT
MALFUNCTION_CAUSE
NOTIFICATION_FACT
MALFUNCTION_DAMAG E
MALFUNCTION_EFFECT NOTIFICATION_FACT.EFFECT_ID=MALFUNCTION _EFFECT.EFFECT_ID MALFUNCTION_OBJ_PA RT NOTIFICATION_FACT.OBJ_PART_ID=MALFUNCTI ON_OBJ_PART.OBJ_PART_ID and NOTIFICATION_FACT.OBJ_PART_GRP_ID=MALFU NCTION_OBJ_PART.OBJ_PART_GRP_ID NOTIFICATION_FACT.MATERIAL_ID=MATERIAL.M ATERIAL_ID NOTIFICATION_FACT.MATERIAL_ID=MATERIAL_B Y_PLANT.MATERIAL_ID and NOTIFICATION_FACT.PLANT_ID=MATERIAL_BY_P LANT.PLANT_ID PLANNING_GROUP.PLANT_ID=NOTIFICATION_FA CT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=NOTIFICATI ON_FACT.PLANNG_GRP_ID PLANT.PLANT_ID=NOTIFICATION_FACT.PLANT_ID PLANT_LOCATION.PLANT_ID=NOTIFICATION_FAC T.PLANT_ID and PLANT_LOCATION.LOCATN_ID=NOTIFICATION_F ACT.LOCATN_ID SERVICE_PERSON.PERSON_ID=NOTIFICATION_F ACT.PERSON_ID_RESP TIME_DIM.CALENDAR_DATE=NOTIFICATION_FAC T.CREATE_DATE TIME_DIM.CALENDAR_DATE=NOTIFICATION_FAC T.NOTIFICTN_DATE UNIT_OF_MEASURE.UOM_ID=NOTIFICATION_FA CT.UOM_ID_DOWNTIME
MATERIAL MATERIAL_BY_PLANT
NOTIFICATION_FACT
PLANNING_GROUP
PLANT PLANT_LOCATION
NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT NOTIFICATION_FACT
SERVICE_PERSON TIME_DIM TIME_DIM UNIT_OF_MEASURE
92
Reports MTBR MTTR
Fact Table NOTIFICATION_FACT
Dimension Table WORK_CENTER
Join Expression NOTIFICATION_FACT.WORK_CNTR_ID=WORK_CE NTER.WORK_CNTR_ID AND NOTIFICATION_FACT.PLANT_ID = WORK_CENTER.PLANT_ID NOTIFICATION_FACT.WORK_CNTR_ID=WORK_CE NTER_HIER_HZ.WORK_CNTR_ID AND NOTIFICATION_FACT.PLANT_ID=WORK_CENTER _HIER_HZ.PLANT_ID NOTIFICATION_FACT.WORK_CNTR_ID=WORK_CE NTER_HIER_VR.CHILD_ID AND NOTIFICATION_FACT.PLANT_ID=WORK_CENTER _HIER_VR.PLANT_ID
NOTIFICATION_FACT
WORK_CENTER_HIER_ HZ
NOTIFICATION_FACT
WORK_CENTER_HIER_ VR
MTBR MTTR
MTBR and MTTR data is related to service notifications.
These are calculated from the notifications within the Rapid Mart load job.
Reports
Sample Reports for the MTBR MTTR include:
MTBR MTTR Analysis MTBR MTTR Listing
MTBR MTTR Analysis

View MTBR MTTR for all Companies by Plant and Equipment type for the selected Calendar Year.
93
Reports MTBR MTTR
Summary
View summary statistics including days uptime, days downtime, % mix and averages.
94
Reports MTBR MTTR
Trend
View MTBR MTTR data as a trend by equipment type.
Calculations
% Mix Days Uptime = Percentage([MTBR MTTR - Days Uptime])
Report SQL
95
Reports MTBR MTTR
MTBR MTTR Listing

View MTBR MTTR Listing for the selected Company Code and Calendar Year.
Report SQL

To analyze MTBR MTTR data you will need to create joins between the fact and dimension tables as follows:
96
Reports MTBR MTTR
Note: Additional joins between dimension and hierarchy tables are shown in Recommended table joins on page 27 for master reports. Fact Table MTBR_MTTR_FACT MTBR_MTTR_FACT Dimension Table BUSINESS_AREA CLASSIFICATION_HIE R_HZ Join Expression BUSINESS_AREA.BUS_AREA_ID=MTB R_MTTR_FACT.BUS_AREA_ID MTBR_MTTR_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_HZ.INTERNAL _CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TY PE_ID = '002' MTBR_MTTR_FACT.FUNCTNL_LOCAT N_ID =CLASSIFICATION_HIER_HZ.INTERNA L_CLASS_ID and CLASSIFICATION_HIER_HZ.CLASS_TY PE_ID = '003' MTBR_MTTR_FACT.EQUIPMNT_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_T YPE_ID = '002' MTBR_MTTR_FACT.FUNCTNL_LOCAT N_ID =CLASSIFICATION_HIER_VR.CHILD_I D and CLASSIFICATION_HIER_VR.CLASS_T YPE_ID = '003' COMPANY_CODE.CMPNY_CODE_ID= MTBR_MTTR_FACT.CMPNY_CODE_ID
MTBR_MTTR_FACT
CLASSIFICATION_HIE R_HZ
MTBR_MTTR_FACT
CLASSIFICATION_HIE R_VR
MTBR_MTTR_FACT
CLASSIFICATION_HIE R_VR
MTBR_MTTR_FACT MTBR_MTTR_FACT MTBR_MTTR_FACT
COMPANY_CODE
CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID =MTBR_MTTR_FACT.CTRL_AREA_ID COST_CENTER MTBR_MTTR_FACT.COST_CNTR_ID= COST_CENTER.COST_CNTR_ID and MTBR_MTTR_FACT.CTRL_AREA_ID=C OST_CENTER.CTRL_AREA_ID MTBR_MTTR_FACT.CTRL_AREA_ID=C OST_CENTER_HIER_HZ.CTRL_AREA_ ID and MTBR_MTTR_FACT.COST_CNTR_ID= COST_CENTER_HIER_HZ.COST_CNT R_ID
MTBR_MTTR_FACT
COST_CENTER_HIER _HZ
97
Reports MTBR MTTR
Fact Table MTBR_MTTR_FACT
Dimension Table
Join Expression
COST_CENTER_HIER MTBR_MTTR_FACT.CTRL_AREA_ID=C _VR OST_CENTER_HIER_VR.CTRL_AREA_ ID and MTBR_MTTR_FACT.COST_CNTR_ID= COST_CENTER_HIER_VR.CHILD_ID DOCUMENT_CATEGO DOCUMENT_CATEGORY.DOC_CATEG RY _ID = MTBR_MTTR_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'NOTIFICTN' DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=M TBR_MTTR_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=MT BR_MTTR_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'NOTIFICTN' MTBR_MTTR_FACT.EQUIPMNT_ID=EQ UIPMENT.EQUIPMNT_ID
MTBR_MTTR_FACT
MTBR_MTTR_FACT
MTBR_MTTR_FACT MTBR_MTTR_FACT MTBR_MTTR_FACT MTBR_MTTR_FACT
EQUIPMENT
EQUIPMENT_HIER_HZ MTBR_MTTR_FACT.EQUIPMNT_ID=EQ UIPMENT_HIER_HZ.EQUIPMNT_ID EQUIPMENT_HIER_V R MTBR_MTTR_FACT.EQUIPMNT_ID=EQ UIPMENT_HIER_VR.CHILD_ID
FUNCTIONAL_LOCATI MTBR_MTTR_FACT.FUNCTNL_LOCAT ON N_ID=FUNCTIONAL_LOCATION.FUNC TNL_LOCATN_ID FUNCTIONAL_LOCATI MTBR_MTTR_FACT.FUNCTNL_LOCAT ON_HIER_HZ N_ID=FUNCTIONAL_LOCATION_HIER_ HZ.FUNCTNL_LOCATN_ID FUNCTIONAL_LOCATI MTBR_MTTR_FACT.FUNCTNL_LOCAT ON_HIER_VR N_ID=FUNCTIONAL_LOCATION_HIER_ VR.CHILD_ID INTERNAL_ORDER MTBR_MTTR_FACT.INTERNAL_ORDE R_ID=INTERNAL_ORDER.INTERNAL_ ORDER_ID
MTBR_MTTR_FACT
MTBR_MTTR_FACT
MTBR_MTTR_FACT
MTBR_MTTR_FACT
INTERNAL_ORDER_HI MTBR_MTTR_FACT.INTERNAL_ORDE ER_HZ R_ID=INTERNAL_ORDER_HIER_HZ.IN TERNAL_ORDER_ID
98
Reports MTBR MTTR
Dimension Table
Join Expression
INTERNAL_ORDER_HI MTBR_MTTR_FACT.INTERNAL_ORDE ER_VR R_ID=INTERNAL_ORDER_HIER_VR.C HILD_ID MAINTENANCE_PRIO RITY MTBR_MTTR_FACT.PRIORITY_ID=MAI NTENANCE_PRIORITY.PRIORITY_ID and MTBR_MTTR_FACT.PRIORITY_TYPE_I D=MAINTENANCE_PRIORITY.PRIORIT Y_TYPE_ID MTBR_MTTR_FACT.EFFECT_ID=MALF UNCTION_EFFECT.EFFECT_ID MTBR_MTTR_FACT.MATERIAL_ID=MA TERIAL.MATERIAL_ID
MTBR_MTTR_FACT
MTBR_MTTR_FACT MTBR_MTTR_FACT MTBR_MTTR_FACT
MALFUNCTION_EFFE CT MATERIAL
MATERIAL_BY_PLANT MTBR_MTTR_FACT.MATERIAL_ID=MA TERIAL_BY_PLANT.MATERIAL_ID and MTBR_MTTR_FACT.PLANT_ID=MATER IAL_BY_PLANT.PLANT_ID NOTIFICATION PLANNING_GROUP MTBR_MTTR_FACT.NOTIFICTN_ID=N OTIFICATION.NOTIFICTN_ID PLANNING_GROUP.PLANT_ID=MTBR_ MTTR_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID =MTBR_MTTR_FACT.PLANNG_GRP_I D PLANT.PLANT_ID=MTBR_MTTR_FACT. PLANT_ID SERVICE_PERSON.PERSON_ID=MTB R_MTTR_FACT.PERSON_ID_RESP TIME_DIM.CALENDAR_DATE=MTBR_ MTTR_FACT.NOTIFICTN_DATE MTBR_MTTR_FACT.WORK_CNTR_ID= WORK_CENTER.WORK_CNTR_ID and MTBR_MTTR_FACT.PLANT_ID=WORK _CENTER.PLANT_ID
MTBR_MTTR_FACT MTBR_MTTR_FACT
MTBR_MTTR_FACT MTBR_MTTR_FACT MTBR_MTTR_FACT MTBR_MTTR_FACT
PLANT SERVICE_PERSON TIME_DIM WORK_CENTER
99
Reports Service Order
Dimension Table
Join Expression
WORK_CENTER_HIER MTBR_MTTR_FACT.WORK_CNTR_ID= _HZ WORK_CENTER_HIER_HZ.WORK_CN TR_ID AND MTBR_MTTR_FACT.PLANT_ID=WORK _CENTER_HIER_HZ.PLANT_ID WORK_CENTER_HIER MTBR_MTTR_FACT.WORK_CNTR_ID= _VR WORK_CENTER_HIER_VR.CHILD_ID AND MTBR_MTTR_FACT.PLANT_ID=WORK _CENTER_HIER_VR.PLANT_ID
MTBR_MTTR_FACT
Service Order
Service 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.
Reports
Sample Reports for this section include:
Service Order Analysis Service Order Listing
Service Order Analysis

View 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).
100
By Plant and Functional Loc

View service order statistics by Plant and Functional Location.
101
By Service Technician
View service order statistics for each Service Technician.
102
Order Details by Plant

View 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))
Report SQL
Service Order Listing

View Completed and Open service orders for the selected Company Code and Calendar Year.
103
Completed Orders
View service order listing for completed orders.
104
Open Orders
View 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))
Report SQL
105

To analyze Service Order data you will need to create joins between the fact and dimension tables as follows:
Fact Table Dimension Table Join Expression BUSINESS_AREA.BUS_AREA_ID=SERVICE_ORD ER_FACT.BUS_AREA_ID
SERVICE_ORDER_FACT BUSINESS_AREA
SERVICE_ORDER_FACT CLASSIFICATION_HIER_ SERVICE_ORDER_FACT.EQUIPMNT_ID = HZ CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' SERVICE_ORDER_FACT CLASSIFICATION_HIER_ SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID HZ =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003' SERVICE_ORDER_FACT CLASSIFICATION_HIER_ SERVICE_ORDER_FACT.EQUIPMNT_ID = VR CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' SERVICE_ORDER_FACT CLASSIFICATION_HIER_ SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID VR =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' SERVICE_ORDER_FACT COMPANY_CODE SERVICE_ORDER_FACT CONTROLLING_AREA SERVICE_ORDER_FACT COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=SERVICE_O RDER_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_ ORDER_FACT.CTRL_AREA_ID 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_H SERVICE_ORDER_FACT.COST_CNTR_ID=COST_ Z 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_V SERVICE_ORDER_FACT.CTRL_AREA_ID=COST_ R CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_ORDER_FACT.COST_CNTR_ID=COST_ CENTER_HIER_VR.CHILD_ID SERVICE_ORDER_FACT CURRENCY SERVICE_ORDER_FACT CUSTOMER CURRENCY.CURR_ID=SERVICE_ORDER_FACT.C URR_ID CUSTOMER.CUSTOMER_ID=SERVICE_ORDER_F ACT.CUSTOMER_ID
106
Fact Table
Dimension Table
Join Expression DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_ORDER_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER' DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_O RDER_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_OR DER_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER' SERVICE_ORDER_FACT.EQUIPMNT_ID=EQUIPME NT.EQUIPMNT_ID SERVICE_ORDER_FACT.EQUIPMNT_ID=EQUIPME NT_HIER_HZ.EQUIPMNT_ID SERVICE_ORDER_FACT.EQUIPMNT_ID=EQUIPME NT_HIER_VR.CHILD_ID SERVICE_ORDER_FACT.FUNCTNL_AREA_ID=FU NCTIONAL_AREA.FUNCTNL_AREA_ID SERVICE_ORDER_FACT.FUNCTNL_AREA_ID=FU NCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID SERVICE_ORDER_FACT.FUNCTNL_AREA_ID=FU NCTIONAL_AREA_HIER_VR.CHILD_ID SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID=F UNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID=F UNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOC ATN_ID SERVICE_ORDER_FACT.FUNCTNL_LOCATN_ID=F UNCTIONAL_LOCATION_HIER_VR.CHILD_ID SERVICE_ORDER_FACT.INTERNAL_ORDER_ID=I NTERNAL_ORDER.INTERNAL_ORDER_ID SERVICE_ORDER_FACT.INTERNAL_ORDER_ID=I NTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ ID SERVICE_ORDER_FACT.INTERNAL_ORDER_ID=I NTERNAL_ORDER_HIER_VR.CHILD_ID
SERVICE_ORDER_FACT DOCUMENT_CATEGOR Y
SERVICE_ORDER_FACT DOCUMENT_TYPE
SERVICE_ORDER_FACT EQUIPMENT SERVICE_ORDER_FACT EQUIPMENT_HIER_HZ SERVICE_ORDER_FACT EQUIPMENT_HIER_VR SERVICE_ORDER_FACT FUNCTIONAL_AREA SERVICE_ORDER_FACT FUNCTIONAL_AREA_HI ER_HZ SERVICE_ORDER_FACT FUNCTIONAL_AREA_HI ER_VR SERVICE_ORDER_FACT FUNCTIONAL_LOCATIO N SERVICE_ORDER_FACT FUNCTIONAL_LOCATIO N_HIER_HZ SERVICE_ORDER_FACT FUNCTIONAL_LOCATIO N_HIER_VR SERVICE_ORDER_FACT INTERNAL_ORDER SERVICE_ORDER_FACT INTERNAL_ORDER_HIE R_HZ SERVICE_ORDER_FACT INTERNAL_ORDER_HIE R_VR
SERVICE_ORDER_FACT INTERNAL_ORDER_STA INTERNAL_ORDER_STATUS.DOC_TYPE_ID=SER TUS VICE_ORDER_FACT.DOC_TYPE_ID and INTERNAL_ORDER_STATUS.ORDER_STATUS_ID= SERVICE_ORDER_FACT.ORDER_STATUS_ID SERVICE_ORDER_FACT MAINTENANCE_ACTIVIT SERVICE_ORDER_FACT.MAINT_ACTIVITY_TYPE_ Y_TYPE ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ACTI VITY_TYPE_ID SERVICE_ORDER_FACT MAINTENANCE_PRIORI TY SERVICE_ORDER_FACT.PRIORITY_ID=MAINTENA NCE_PRIORITY.PRIORITY_ID and SERVICE_ORDER_FACT.PRIORITY_TYPE_ID=MAI NTENANCE_PRIORITY.PRIORITY_TYPE_ID
107
Fact Table
Dimension Table
Join Expression SERVICE_ORDER_FACT.MATERIAL_ID=MATERIAL .MATERIAL_ID SERVICE_ORDER_FACT.MATERIAL_ID=MATERIAL _BY_PLANT.MATERIAL_ID and SERVICE_ORDER_FACT.PLANT_ID=MATERIAL_B Y_PLANT.PLANT_ID SERVICE_ORDER_FACT.NOTIFICTN_ID=NOTIFIC ATION.NOTIFICTN_ID PLANNING_GROUP.PLANT_ID=SERVICE_ORDER _FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=SERVICE_ ORDER_FACT.PLANNG_GRP_ID PLANT.PLANT_ID=SERVICE_ORDER_FACT.PLANT _ID PLANT_LOCATION.PLANT_ID=SERVICE_ORDER_ FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_ORDER _FACT.LOCATN_ID SERVICE_ORDER_FACT.PROD_HIER_ID=PRODU CT_HIERARCHY.PROD_HIER_ID SERVICE_ORDER_FACT.CTRL_AREA_ID=PROFIT _CENTER.CTRL_AREA_ID and SERVICE_ORDER_FACT.PROFIT_CNTR_ID=PROF IT_CENTER.PROFIT_CNTR_ID SERVICE_ORDER_FACT.CTRL_AREA_ID=PROFIT _CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_ORDER_FACT.PROFIT_CNTR_ID=PROF IT_CENTER_HIER_HZ.PROFIT_CNTR_ID SERVICE_ORDER_FACT.CTRL_AREA_ID=PROFIT _CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_ORDER_FACT.PROFIT_CNTR_ID=PROF IT_CENTER_HIER_VR.CHILD_ID SERVICE_ORDER_FACT.PROJ_ELEM_ID=PROJE CT_ELEMENT.PROJ_ELEM_ID SERVICE_ORDER_FACT.PROJ_ELEM_ID=PROJE CT_ELEMENT_HIER_HZ.PROJ_ELEM_ID SERVICE_ORDER_FACT.PROJ_ELEM_ID=PROJE CT_ELEMENT_HIER_VR.CHILD_ID SERVICE_PERSON.PERSON_ID=SERVICE_ORDE R_FACT.PERSON_ID_RESP SERVICE_ORDER_FACT.SYSTEM_CONDITN_ID=S YSTEM_CONDITION.SYSTEM_CONDITN_ID TIME_DIM.CALENDAR_DATE=SERVICE_ORDER_ FACT.CREATE_DATE SERVICE_ORDER_FACT.WORK_CNTR_ID=WORK _CENTER.WORK_CNTR_ID AND SERVICE_ORDER_FACT.PLANT_ID=WORK_CENT ER.PLANT_ID
SERVICE_ORDER_FACT MATERIAL SERVICE_ORDER_FACT MATERIAL_BY_PLANT
SERVICE_ORDER_FACT NOTIFICATION SERVICE_ORDER_FACT PLANNING_GROUP
SERVICE_ORDER_FACT PLANT SERVICE_ORDER_FACT PLANT_LOCATION
SERVICE_ORDER_FACT PRODUCT_HIERARCHY SERVICE_ORDER_FACT PROFIT_CENTER
SERVICE_ORDER_FACT PROFIT_CENTER_HIER _HZ
SERVICE_ORDER_FACT PROFIT_CENTER_HIER _VR
SERVICE_ORDER_FACT PROJECT_ELEMENT SERVICE_ORDER_FACT PROJECT_ELEMENT_HI ER_HZ SERVICE_ORDER_FACT PROJECT_ELEMENT_HI ER_VR SERVICE_ORDER_FACT SERVICE_PERSON SERVICE_ORDER_FACT SYSTEM_CONDITION SERVICE_ORDER_FACT TIME_DIM SERVICE_ORDER_FACT WORK_CENTER
108
Reports Service Operation
Fact Table
Dimension Table
Join Expression SERVICE_ORDER_FACT.WORK_CNTR_ID=WORK _CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_ORDER_FACT.PLANT_ID=WORK_CENT ER_HIER_HZ.PLANT_ID SERVICE_ORDER_FACT.WORK_CNTR_ID=WORK _CENTER_HIER_VR.CHILD_ID AND SERVICE_ORDER_FACT.PLANT_ID=WORK_CENT ER_HIER_VR.PLANT_ID
SERVICE_ORDER_FACT WORK_CENTER_HIER_ HZ
SERVICE_ORDER_FACT WORK_CENTER_HIER_ VR
Service Operation
You 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.
Reports
Service Operation Detail Service Operation Analysis Service Operation Listing
109
Service Operation Detail

View service operation details for the selected Company Code and service Operation Routing Id.
Report SQL
Service Operation Analysis

View service operation summary and listing for the selected Company Code and Calendar Year.
110
Summary
View service operation summary statistics by maintenance activity and functional location.
111
Trend
View 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]
Report SQL
112
Service Operation Listing

View 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]
Report SQL

To analyze Service Operation data you will need to create joins between the fact and dimension tables as follows:
113
Fact Table SERVICE_OPERATION_ FACT Dimension Table ACTIVITY Join Expression SERVICE_OPERATION_FACT.ACTIVITY_ID=ACTIVI TY.ACTIVITY_ID and SERVICE_OPERATION_FACT.CTRL_AREA_ID=AC TIVITY.CTRL_AREA_ID SERVICE_OPERATION_FACT.CTRL_AREA_ID=AC TIVITY_HIER_HZ.CTRL_AREA_ID and SERVICE_OPERATION_FACT.ACTIVITY_ID=ACTIVI TY_HIER_HZ.ACTIVITY_ID 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.BUS_AREA_ID=SERVICE_OPER ATION_FACT.BUS_AREA_ID
SERVICE_OPERATION_ FACT
ACTIVITY_HIER_HZ
ACTIVITY_HIER_VR
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
BUSINESS_AREA
CHART_OF_ACCOUNTS CHART_OF_ACCOUNTS.CHART_OF_ACCT_ID=SE RVICE_OPERATION_FACT.CHART_OF_ACCT_ID CLASSIFICATION_HIER_ SERVICE_OPERATION_FACT.EQUIPMNT_ID = HZ CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ HZ ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003' CLASSIFICATION_HIER_ SERVICE_OPERATION_FACT.EQUIPMNT_ID = VR CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ VR ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' COMPANY_CODE CONTROL_KEY CONTROLLING_AREA COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=SERVICE_O PERATION_FACT.CMPNY_CODE_ID CONTROL_KEY.CTRL_KEY_ID=SERVICE_OPERAT ION_FACT.CTRL_KEY_ID CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_ OPERATION_FACT.CTRL_AREA_ID SERVICE_OPERATION_FACT.COST_CNTR_ID=CO ST_CENTER.COST_CNTR_ID and SERVICE_OPERATION_FACT.CTRL_AREA_ID=CO ST_CENTER.CTRL_AREA_ID
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
114
Fact Table SERVICE_OPERATION_ FACT
Dimension Table
Join Expression
COST_CENTER_HIER_H SERVICE_OPERATION_FACT.CTRL_AREA_ID=CO Z ST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_OPERATION_FACT.COST_CNTR_ID=CO ST_CENTER_HIER_HZ.COST_CNTR_ID COST_CENTER_HIER_V SERVICE_OPERATION_FACT.CTRL_AREA_ID=CO R ST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_OPERATION_FACT.COST_CNTR_ID=CO ST_CENTER_HIER_VR.CHILD_ID COST_ELEMENT SERVICE_OPERATION_FACT.CHART_OF_ACCT_I D=COST_ELEMENT.CHART_OF_ACCT_ID and SERVICE_OPERATION_FACT.COST_ELEM_ID=CO ST_ELEMENT.COST_ELEM_ID
COST_ELEMENT_HIER_ SERVICE_OPERATION_FACT.COST_ELEM_ID=CO HZ ST_ELEMENT_HIER_HZ.COST_ELEM_ID and SERVICE_OPERATION_FACT.CHART_OF_ACCT_I D=COST_ELEMENT_HIER_HZ.CHART_OF_ACCT_ ID COST_ELEMENT_HIER_ SERVICE_OPERATION_FACT.CHART_OF_ACCT_I VR D=COST_ELEMENT_HIER_VR.CHART_OF_ACCT_ ID and SERVICE_OPERATION_FACT.COST_ELEM_ID=CO ST_ELEMENT_HIER_VR.CHILD_ID CURRENCY CUSTOMER DOCUMENT_CATEGOR Y CURRENCY.CURR_ID=SERVICE_OPERATION_FA CT.CURR_ID CUSTOMER.CUSTOMER_ID=SERVICE_OPERATIO N_FACT.CUSTOMER_ID DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_OPERATION_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER' DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_OP ERATION_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_OPE RATION_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER' SERVICE_OPERATION_FACT.EQUIPMNT_ID=EQUI PMENT.EQUIPMNT_ID SERVICE_OPERATION_FACT.EQUIPMNT_ID=EQUI PMENT_HIER_HZ.EQUIPMNT_ID SERVICE_OPERATION_FACT.EQUIPMNT_ID=EQUI PMENT_HIER_VR.CHILD_ID SERVICE_OPERATION_FACT.FUNCTNL_AREA_ID =FUNCTIONAL_AREA.FUNCTNL_AREA_ID SERVICE_OPERATION_FACT.FUNCTNL_AREA_ID =FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ ID SERVICE_OPERATION_FACT.FUNCTNL_AREA_ID =FUNCTIONAL_AREA_HIER_VR.CHILD_ID
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
DOCUMENT_TYPE
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR FUNCTIONAL_AREA FUNCTIONAL_AREA_HI ER_HZ FUNCTIONAL_AREA_HI ER_VR
115
Fact Table SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
Dimension Table FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ FUNCTIONAL_LOCATIO N_HIER_VR INTERNAL_ORDER INTERNAL_ORDER_HIE R_HZ INTERNAL_ORDER_HIE R_VR
Join Expression SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_I D SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_ LOCATN_ID SERVICE_OPERATION_FACT.FUNCTNL_LOCATN_ ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID SERVICE_OPERATION_FACT.INTERNAL_ORDER_ ID=INTERNAL_ORDER.INTERNAL_ORDER_ID SERVICE_OPERATION_FACT.INTERNAL_ORDER_ ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORD ER_ID SERVICE_OPERATION_FACT.INTERNAL_ORDER_ ID=INTERNAL_ORDER_HIER_VR.CHILD_ID
MAINTENANCE_ACTIVIT SERVICE_OPERATION_FACT.MAINT_ACTIVITY_T Y_TYPE YPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAINT_ ACTIVITY_TYPE_ID MAINTENANCE_PRIORI TY SERVICE_OPERATION_FACT.PRIORITY_ID=MAIN TENANCE_PRIORITY.PRIORITY_ID and SERVICE_OPERATION_FACT.PRIORITY_TYPE_ID =MAINTENANCE_PRIORITY.PRIORITY_TYPE_ID SERVICE_OPERATION_FACT.MATERIAL_ID=MATE RIAL.MATERIAL_ID SERVICE_OPERATION_FACT.MATERIAL_ID=MATE RIAL_BY_PLANT.MATERIAL_ID and SERVICE_OPERATION_FACT.PLANT_ID=MATERIA L_BY_PLANT.PLANT_ID SERVICE_OPERATION_FACT.NOTIFICTN_ID=NOTI FICATION.NOTIFICTN_ID OBJECT_CLASS.OBJ_CLASS_ID=SERVICE_OPER ATION_FACT.OBJ_CLASS_ID OBJECT_TYPE.OBJ_TYPE_ID=SERVICE_OPERATI ON_FACT.OBJ_TYPE_ID and OBJECT_TYPE.DIM_SRC_ID = 'ORDER'
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
NOTIFICATION OBJECT_CLASS OBJECT_TYPE
OPERATION_SUITABILIT OPERATION_SUITABILITY.PLANT_ID=SERVICE_O Y PERATION_FACT.PLANT_ID and OPERATION_SUITABILITY.SUITABILITY_ID=SERVI CE_OPERATION_FACT.SUITABILITY_ID PLANNING_GROUP PLANNING_GROUP.PLANT_ID=SERVICE_OPERAT ION_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=SERVICE_ OPERATION_FACT.PLANNG_GRP_ID PLANT.PLANT_ID=SERVICE_OPERATION_FACT.P LANT_ID
PLANT
116
Dimension Table PLANT_LOCATION
Join Expression PLANT_LOCATION.PLANT_ID=SERVICE_OPERATI ON_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_OPERA TION_FACT.LOCATN_ID SERVICE_OPERATION_FACT.PROD_HIER_ID=PR ODUCT_HIERARCHY.PROD_HIER_ID SERVICE_OPERATION_FACT.CTRL_AREA_ID=PR OFIT_CENTER.CTRL_AREA_ID and SERVICE_OPERATION_FACT.PROFIT_CNTR_ID=P ROFIT_CENTER.PROFIT_CNTR_ID SERVICE_OPERATION_FACT.CTRL_AREA_ID=PR OFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_OPERATION_FACT.PROFIT_CNTR_ID=P ROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID SERVICE_OPERATION_FACT.CTRL_AREA_ID=PR OFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_OPERATION_FACT.PROFIT_CNTR_ID=P ROFIT_CENTER_HIER_VR.CHILD_ID SERVICE_OPERATION_FACT.PROJ_ELEM_ID=PR OJECT_ELEMENT.PROJ_ELEM_ID SERVICE_OPERATION_FACT.PROJ_ELEM_ID=PR OJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID SERVICE_OPERATION_FACT.PROJ_ELEM_ID=PR OJECT_ELEMENT_HIER_VR.CHILD_ID SERVICE_OPERATION_FACT.SYSTEM_CONDITN_ ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ID TIME_DIM.CALENDAR_DATE=SERVICE_OPERATI ON_FACT.CREATE_DATE UNIT_OF_MEASURE.UOM_ID=SERVICE_OPERATI ON_FACT.UOM_ID_DURTN UNIT_OF_MEASURE.UOM_ID=SERVICE_OPERATI ON_FACT.UOM_ID_WORK VENDOR.VENDOR_ID=SERVICE_OPERATION_FA CT.VENDOR_ID
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
PRODUCT_HIERARCHY PROFIT_CENTER
PROFIT_CENTER_HIER _HZ
PROFIT_CENTER_HIER _VR
SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT SERVICE_OPERATION_ FACT
PROJECT_ELEMENT PROJECT_ELEMENT_HI ER_HZ PROJECT_ELEMENT_HI ER_VR SYSTEM_CONDITION TIME_DIM UNIT_OF_MEASURE UNIT_OF_MEASURE VENDOR
VENDOR_BY_COMPANY VENDOR_BY_COMPANY.VENDOR_ID=SERVICE_ OPERATION_FACT.VENDOR_ID and VENDOR_BY_COMPANY.CMPNY_CODE_ID=SERV ICE_OPERATION_FACT.CMPNY_CODE_ID WORK_CENTER SERVICE_OPERATION_FACT.WORK_CNTR_ID=W ORK_CENTER.WORK_CNTR_ID and SERVICE_OPERATION_FACT.PLANT_ID=WORK_C ENTER.PLANT_ID
117
Reports Service Confirmation
Dimension Table WORK_CENTER_HIER_ HZ
Join Expression SERVICE_OPERATION_FACT.WORK_CNTR_ID=W ORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_OPERATION_FACT.PLANT_ID=WORK_C ENTER_HIER_HZ.PLANT_ID SERVICE_OPERATION_FACT.WORK_CNTR_ID=W ORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_OPERATION_FACT.PLANT_ID=WORK_C ENTER_HIER_VR.PLANT_ID
Service Confirmation
The confirmation section extracts data about confirmations, which document the actual time to complete maintenance on an item.
Reports
Service Confirmation Listing Service Confirmation Details Service Confirmation Performance
Service Confirmation Listing

View service confirmation listing for the selected Company Code, Calendar Year, and Calendar Month. Includes a hyperlink by Confirmation ID to Service Confirmation Details.
118
By Plant
View service confirmation listing organized by plant.
119
By Service Order
View 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)
Report SQL
120
Service Confirmation Details

View service confirmation details for the selected Confirmation Id.
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)
Report SQL
Service Confirmation Performance

View service confirmation performance by Activity for the selected Company Code and Calendar Year.
121
Summary by Activity
View service confirmation summary statistics by activity.
122
Trend by Activity
View trend of service confirmation measures by activity.
Calculations
Hours Variance % (EXECTN vs FCST) = If([SVC CONF - Hours Execution] <> 0; ([SVC CONF - Hours Variance (EXECTN vs FCST)])/[SVC CONF - Hours Execution]; 0)
Report SQL

To analyze Service Confirmation data you will need to create joins between the fact and dimension tables as follows:
123
Fact Table SERVICE_CONFIRMATI ON_FACT Dimension Table ACTIVITY Join Expression SERVICE_CONFIRMATION_FACT.ACTIVITY_ID=AC TIVITY.ACTIVITY_ID and SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID= ACTIVITY.CTRL_AREA_ID SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID= ACTIVITY_HIER_HZ.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.ACTIVITY_ID=AC TIVITY_HIER_HZ.ACTIVITY_ID 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.BUS_AREA_ID=SERVICE_CONF IRMATION_FACT.BUS_AREA_ID CAPACITY.CAPACITY_ID=SERVICE_CONFIRMATI ON_FACT.CAPACITY_ID
SERVICE_CONFIRMATI ON_FACT
ACTIVITY_HIER_HZ
ACTIVITY_HIER_VR
SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT
BUSINESS_AREA CAPACITY
CLASSIFICATION_HIER_ SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID = HZ CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCA HZ TN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003' CLASSIFICATION_HIER_ SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID = VR CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCA VR TN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' COMPANY_CODE CONTROLLING_AREA COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=SERVICE_C ONFIRMATION_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_ CONFIRMATION_FACT.CTRL_AREA_ID 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_H SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID= Z COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.COST_CNTR_ID =COST_CENTER_HIER_HZ.COST_CNTR_ID
124
Fact Table SERVICE_CONFIRMATI ON_FACT
Dimension Table
Join Expression
COST_CENTER_HIER_V SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID= R COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.COST_CNTR_ID =COST_CENTER_HIER_VR.CHILD_ID CURRENCY CUSTOMER DOCUMENT_CATEGOR Y CURRENCY.CURR_ID=SERVICE_CONFIRMATION _FACT.CURR_ID CUSTOMER.CUSTOMER_ID=SERVICE_CONFIRM ATION_FACT.CUSTOMER_ID DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_CONFIRMATION_FACT.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER' DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_CO NFIRMATION_FACT.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_CON FIRMATION_FACT.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER' SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID=E QUIPMENT.EQUIPMNT_ID SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID=E QUIPMENT_HIER_HZ.EQUIPMNT_ID SERVICE_CONFIRMATION_FACT.EQUIPMNT_ID=E QUIPMENT_HIER_VR.CHILD_ID SERVICE_CONFIRMATION_FACT.FUNCTNL_AREA _ID=FUNCTIONAL_AREA.FUNCTNL_AREA_ID SERVICE_CONFIRMATION_FACT.FUNCTNL_AREA _ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AR EA_ID SERVICE_CONFIRMATION_FACT.FUNCTNL_AREA _ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCA TN_ID=FUNCTIONAL_LOCATION.FUNCTNL_LOCA TN_ID SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCA TN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNC TNL_LOCATN_ID SERVICE_CONFIRMATION_FACT.FUNCTNL_LOCA TN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD _ID SERVICE_CONFIRMATION_FACT.INTERNAL_ORD ER_ID=INTERNAL_ORDER.INTERNAL_ORDER_ID SERVICE_CONFIRMATION_FACT.INTERNAL_ORD ER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ ORDER_ID SERVICE_CONFIRMATION_FACT.INTERNAL_ORD ER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID
DOCUMENT_TYPE
SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR FUNCTIONAL_AREA FUNCTIONAL_AREA_HI ER_HZ FUNCTIONAL_AREA_HI ER_VR FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ FUNCTIONAL_LOCATIO N_HIER_VR INTERNAL_ORDER INTERNAL_ORDER_HIE R_HZ INTERNAL_ORDER_HIE R_VR
125
Fact Table SERVICE_CONFIRMATI ON_FACT
Dimension Table
Join Expression
INTERNAL_ORDER_STA INTERNAL_ORDER_STATUS.DOC_TYPE_ID=SER TUS VICE_CONFIRMATION_FACT.DOC_TYPE_ID and INTERNAL_ORDER_STATUS.ORDER_STATUS_ID= SERVICE_CONFIRMATION_FACT.ORDER_STATUS _ID MAINTENANCE_ACTIVIT SERVICE_CONFIRMATION_FACT.MAINT_ACTIVIT Y_TYPE Y_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE.MAI NT_ACTIVITY_TYPE_ID MAINTENANCE_PRIORI TY SERVICE_CONFIRMATION_FACT.PRIORITY_ID=M AINTENANCE_PRIORITY.PRIORITY_ID and SERVICE_CONFIRMATION_FACT.PRIORITY_TYPE _ID=MAINTENANCE_PRIORITY.PRIORITY_TYPE_I D SERVICE_CONFIRMATION_FACT.MATERIAL_ID=M ATERIAL.MATERIAL_ID SERVICE_CONFIRMATION_FACT.MATERIAL_ID=M ATERIAL_BY_PLANT.MATERIAL_ID and SERVICE_CONFIRMATION_FACT.PLANT_ID=MATE RIAL_BY_PLANT.PLANT_ID SERVICE_CONFIRMATION_FACT.NOTIFICTN_ID= NOTIFICATION.NOTIFICTN_ID
SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT
NOTIFICATION
OPERATION_SUITABILIT OPERATION_SUITABILITY.PLANT_ID=SERVICE_C Y ONFIRMATION_FACT.PLANT_ID and OPERATION_SUITABILITY.SUITABILITY_ID=SERVI CE_CONFIRMATION_FACT.SUITABILITY_ID PLANNING_GROUP PLANNING_GROUP.PLANT_ID=SERVICE_CONFIR MATION_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=SERVICE_ CONFIRMATION_FACT.PLANNG_GRP_ID PLANT.PLANT_ID=SERVICE_CONFIRMATION_FAC T.PLANT_ID PLANT_LOCATION.PLANT_ID=SERVICE_CONFIR MATION_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_CONFI RMATION_FACT.LOCATN_ID SERVICE_CONFIRMATION_FACT.PROD_HIER_ID= PRODUCT_HIERARCHY.PROD_HIER_ID SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID= PROFIT_CENTER.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.PROFIT_CNTR_I D=PROFIT_CENTER.PROFIT_CNTR_ID SERVICE_CONFIRMATION_FACT.CTRL_AREA_ID= PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_CONFIRMATION_FACT.PROFIT_CNTR_I D=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_I D=PROFIT_CENTER_HIER_VR.CHILD_ID
126
Reports Service Order Cost
Fact Table SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT SERVICE_CONFIRMATI ON_FACT
Dimension Table PROJECT_ELEMENT PROJECT_ELEMENT_HI ER_HZ PROJECT_ELEMENT_HI ER_VR SERVICE_PERSON SYSTEM_CONDITION
Join Expression 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.PERSON_ID=SERVICE_CONFI RMATION_FACT.PERSON_ID_RESP SERVICE_CONFIRMATION_FACT.SYSTEM_CONDI TN_ID=SYSTEM_CONDITION.SYSTEM_CONDITN_ ID TIME_DIM.CALENDAR_DATE=SERVICE_CONFIRM ATION_FACT.CREATE_DATE UNIT_OF_MEASURE.UOM_ID=SERVICE_CONFIR MATION_FACT.UOM_ID_DURTN_ACTL UNIT_OF_MEASURE.UOM_ID=SERVICE_CONFIR MATION_FACT.UOM_ID_WORK_ACTL SERVICE_CONFIRMATION_FACT.WORK_CNTR_ID =WORK_CENTER.WORK_CNTR_ID AND SERVICE_CONFIRMATION_FACT.PLANT_ID = WORK_CENTER.PLANT_ID SERVICE_CONFIRMATION_FACT.WORK_CNTR_ID =WORK_CENTER_HIER_HZ.WORK_CNTR_ID AND SERVICE_CONFIRMATION_FACT.PLANT_ID=WOR K_CENTER_HIER_HZ.PLANT_ID SERVICE_CONFIRMATION_FACT.WORK_CNTR_ID =WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_CONFIRMATION_FACT.PLANT_ID=WOR K_CENTER_HIER_VR.PLANT_ID
TIME_DIM UNIT_OF_MEASURE UNIT_OF_MEASURE WORK_CENTER
Service Order Cost

The 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.
Reports
Service Cost Balance Trend Comparison
127
Service Cost Balance Variance Trend Service Cost YTD Trend Analysis
Service Cost Balance Trend Comparison

Displays the service cost balance trend data for the selected Company Code, Fiscal Years, and Equipment hierarchy.
Actual Balance Trend

View actual service cost balance trend by equipment hierarchy.
128
Variance Previous Period

View 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.
Report SQL
129
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))
Report SQL
130
Service Cost YTD Trend Analysis

View 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))
Report SQL

To analyze Service Order Cost data you will need to create joins between the fact and dimension tables as follows:
131
Fact Table SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ Dimension Table BUSINESS_ACTIVITY BUSINESS_AREA Join Expression BUSINESS_ACTIVITY.BUS_ACTIVITY_ID=SERVICE _COST_SUMMARY_FACT_HZ.BUS_ACTIVITY_ID BUSINESS_AREA.BUS_AREA_ID=SERVICE_COST _SUMMARY_FACT_HZ.BUS_AREA_ID
CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT HZ _ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_ HZ LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003' CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT VR _ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_ VR LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' COMPANY_CODE CONTROLLING_AREA COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=SERVICE_C OST_SUMMARY_FACT_HZ.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_ COST_SUMMARY_FACT_HZ.CTRL_AREA_ID SERVICE_COST_SUMMARY_FACT_HZ.COST_CN TR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_COST_SUMMARY_FACT_HZ.CTRL_ARE A_ID=COST_CENTER.CTRL_AREA_ID
SERVICE_COST_SUMM ARY_FACT_HZ
SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ
COST_CENTER_HIER_H SERVICE_COST_SUMMARY_FACT_HZ.CTRL_ARE Z A_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.COST_CN TR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID COST_CENTER_HIER_V SERVICE_COST_SUMMARY_FACT_HZ.CTRL_ARE R A_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.COST_CN TR_ID=COST_CENTER_HIER_VR.CHILD_ID CURRENCY CURRENCY CURRENCY.CURR_ID=SERVICE_COST_SUMMAR Y_FACT_HZ.CURR_ID_CTRL_AREA CURRENCY.CURR_ID=SERVICE_COST_SUMMAR Y_FACT_HZ.CURR_ID_LOC
SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ
132
Fact Table SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ
Dimension Table CURRENCY DOCUMENT_CATEGOR Y
Join Expression CURRENCY.CURR_ID=SERVICE_COST_SUMMAR Y_FACT_HZ.CURR_ID_TRX DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_COST_SUMMARY_FACT_HZ.DOC_CAT EG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER' DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_CO ST_SUMMARY_FACT_HZ.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_COS T_SUMMARY_FACT_HZ.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER' SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT _ID=EQUIPMENT.EQUIPMNT_ID SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT _ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID SERVICE_COST_SUMMARY_FACT_HZ.EQUIPMNT _ID=EQUIPMENT_HIER_VR.CHILD_ID SERVICE_COST_SUMMARY_FACT_HZ.RECORD_ CATEG_ID=FINANCIAL_RECORD_CATEGORY.RE CORD_CATEG_ID SERVICE_COST_SUMMARY_FACT_HZ.RECORD_ TYPE_ID=FINANCIAL_RECORD_TYPE.RECORD_T YPE_ID and FINANCIAL_RECORD_TYPE.RECORD_TYPE_ID = 'COST' SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_ AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_I D SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_ AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTN L_AREA_ID SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_ AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_I D 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.F UNCTNL_LOCATN_ID SERVICE_COST_SUMMARY_FACT_HZ.FUNCTNL_ LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR. CHILD_ID SERVICE_COST_SUMMARY_FACT_HZ.INTERNAL _ORDER_ID=INTERNAL_ORDER.INTERNAL_ORD ER_ID SERVICE_COST_SUMMARY_FACT_HZ.INTERNAL _ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTER NAL_ORDER_ID
DOCUMENT_TYPE
SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR FINANCIAL_RECORD_C ATEGORY FINANCIAL_RECORD_T YPE
SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HI ER_HZ FUNCTIONAL_AREA_HI ER_VR FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ FUNCTIONAL_LOCATIO N_HIER_VR INTERNAL_ORDER
INTERNAL_ORDER_HIE R_HZ
133
Fact Table SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ SERVICE_COST_SUMM ARY_FACT_HZ
Dimension Table INTERNAL_ORDER_HIE R_VR
Join Expression SERVICE_COST_SUMMARY_FACT_HZ.INTERNAL _ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD _ID
MAINTENANCE_ACTIVIT SERVICE_COST_SUMMARY_FACT_HZ.MAINT_AC Y_TYPE TIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE .MAINT_ACTIVITY_TYPE_ID MAINTENANCE_PRIORI TY SERVICE_COST_SUMMARY_FACT_HZ.PRIORITY_ TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_T YPE_ID and SERVICE_COST_SUMMARY_FACT_HZ.PRIORITY_ ID=MAINTENANCE_PRIORITY.PRIORITY_ID SERVICE_COST_SUMMARY_FACT_HZ.MATERIAL _ID=MATERIAL.MATERIAL_ID 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_ID=SERVICE_COST_SUMMARY_FA CT_HZ.PLANT_ID PLANT_LOCATION.PLANT_ID=SERVICE_COST_S UMMARY_FACT_HZ.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_COST_ SUMMARY_FACT_HZ.LOCATN_ID SERVICE_COST_SUMMARY_FACT_HZ.PROD_HIE R_ID=PRODUCT_HIERARCHY.PROD_HIER_ID SERVICE_COST_SUMMARY_FACT_HZ.CTRL_ARE A_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.PROFIT_C NTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID SERVICE_COST_SUMMARY_FACT_HZ.CTRL_ARE A_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.PROFIT_C NTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNT R_ID SERVICE_COST_SUMMARY_FACT_HZ.CTRL_ARE A_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_HZ.PROFIT_C NTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID SERVICE_COST_SUMMARY_FACT_HZ.PROJ_ELE M_ID=PROJECT_ELEMENT.PROJ_ELEM_ID
PROJECT_ELEMENT
PROJECT_ELEMENT_HI SERVICE_COST_SUMMARY_FACT_HZ.PROJ_ELE ER_HZ M_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELE M_ID PROJECT_ELEMENT_HI SERVICE_COST_SUMMARY_FACT_HZ.PROJ_ELE ER_VR M_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID
134
Fact Table SERVICE_COST_SUMM ARY_FACT_HZ
Dimension Table SERVICE_COST_SUMM ARY_FACT_HZ
Join Expression SERVICE_COST_SUMMARY_FACT_HZ.FISC_YEA R= SERVICE_COST_SUMMARY_FACT_HZ.PARTITION _YEAR SERVICE_COST_SUMMARY_FACT_HZ.SYSTEM_ CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CO NDITN_ID VARIANCE_CATEGORY.VARIANCE_CATEG_ID=SE RVICE_COST_SUMMARY_FACT_HZ.VARIANCE_C ATEG_ID SERVICE_COST_SUMMARY_FACT_HZ.WORK_CN TR_ID=WORK_CENTER.WORK_CNTR_ID AND SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID = WORK_CENTER.PLANT_ID SERVICE_COST_SUMMARY_FACT_HZ.WORK_CN TR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_I D AND SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID =WORK_CENTER_HIER_HZ.PLANT_ID SERVICE_COST_SUMMARY_FACT_HZ.WORK_CN TR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_COST_SUMMARY_FACT_HZ.PLANT_ID =WORK_CENTER_HIER_VR.PLANT_ID BUSINESS_ACTIVITY.BUS_ACTIVITY_ID=SERVICE _COST_SUMMARY_FACT_VR.BUS_ACTIVITY_ID BUSINESS_AREA.BUS_AREA_ID=SERVICE_COST _SUMMARY_FACT_VR.BUS_AREA_ID
SYSTEM_CONDITION
VARIANCE_CATEGORY
WORK_CENTER
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
BUSINESS_ACTIVITY BUSINESS_AREA
CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_VR.EQUIPMN HZ T_ID = CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_ HZ LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003' CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_VR.EQUIPMN VR T_ID = CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_ VR LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=SERVICE_C OST_SUMMARY_FACT_VR.CMPNY_CODE_ID
SERVICE_COST_SUMM ARY_FACT_VR
135
Fact Table SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
Dimension Table CONTROLLING_AREA COST_CENTER
Join Expression CONTROLLING_AREA.CTRL_AREA_ID=SERVICE_ COST_SUMMARY_FACT_VR.CTRL_AREA_ID SERVICE_COST_SUMMARY_FACT_VR.COST_CN TR_ID=COST_CENTER.COST_CNTR_ID and SERVICE_COST_SUMMARY_FACT_VR.CTRL_ARE A_ID=COST_CENTER.CTRL_AREA_ID
COST_CENTER_HIER_H SERVICE_COST_SUMMARY_FACT_VR.CTRL_ARE Z A_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.COST_CN TR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID COST_CENTER_HIER_V SERVICE_COST_SUMMARY_FACT_VR.CTRL_ARE R A_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.COST_CN TR_ID=COST_CENTER_HIER_VR.CHILD_ID CURRENCY CURRENCY CURRENCY DOCUMENT_CATEGOR Y CURRENCY.CURR_ID=SERVICE_COST_SUMMAR Y_FACT_VR.CURR_ID_CTRL_AREA CURRENCY.CURR_ID=SERVICE_COST_SUMMAR Y_FACT_VR.CURR_ID_LOC CURRENCY.CURR_ID=SERVICE_COST_SUMMAR Y_FACT_VR.CURR_ID_TRX DOCUMENT_CATEGORY.DOC_CATEG_ID = SERVICE_COST_SUMMARY_FACT_VR.DOC_CAT EG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'INT_ORDER' DOCUMENT_TYPE.DOC_CATEG_ID=SERVICE_CO ST_SUMMARY_FACT_VR.DOC_CATEG_ID AND DOCUMENT_TYPE.DOC_TYPE_ID=SERVICE_COS T_SUMMARY_FACT_VR.DOC_TYPE_ID AND DOCUMENT_TYPE.DIM_SRC_ID = 'INT_ORDER' SERVICE_COST_SUMMARY_FACT_VR.EQUIPMN T_ID=EQUIPMENT.EQUIPMNT_ID SERVICE_COST_SUMMARY_FACT_VR.EQUIPMN T_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID SERVICE_COST_SUMMARY_FACT_VR.EQUIPMN T_ID=EQUIPMENT_HIER_VR.CHILD_ID SERVICE_COST_SUMMARY_FACT_VR.RECORD_ CATEG_ID=FINANCIAL_RECORD_CATEGORY.RE CORD_CATEG_ID SERVICE_COST_SUMMARY_FACT_VR.RECORD_ TYPE_ID=FINANCIAL_RECORD_TYPE.RECORD_T YPE_ID and FINANCIAL_RECORD_TYPE.RECORD_TYPE_ID = 'COST'
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
DOCUMENT_TYPE
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR FINANCIAL_RECORD_C ATEGORY FINANCIAL_RECORD_T YPE
136
Fact Table SERVICE_COST_SUMM ARY_FACT_VR
Dimension Table FISC_PERIOD
Join Expression FISC_PERIOD.FISC_YEAR=SERVICE_COST_SUM MARY_FACT_VR.FISC_YEAR and FISC_PERIOD.FISC_PERIOD=SERVICE_COST_SU MMARY_FACT_VR.FISC_PERIOD and FISC_PERIOD.FISC_YR_VARIANT_ID=SERVICE_C OST_SUMMARY_FACT_VR.FISC_YR_VARIANT_ID SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_ AREA_ID=FUNCTIONAL_AREA.FUNCTNL_AREA_I D SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_ AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTN L_AREA_ID SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_ AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_I D 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.F UNCTNL_LOCATN_ID SERVICE_COST_SUMMARY_FACT_VR.FUNCTNL_ LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR. CHILD_ID SERVICE_COST_SUMMARY_FACT_VR.INTERNAL _ORDER_ID=INTERNAL_ORDER.INTERNAL_ORD ER_ID SERVICE_COST_SUMMARY_FACT_VR.INTERNAL _ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTER NAL_ORDER_ID SERVICE_COST_SUMMARY_FACT_VR.INTERNAL _ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD _ID
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HI ER_HZ FUNCTIONAL_AREA_HI ER_VR FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ FUNCTIONAL_LOCATIO N_HIER_VR INTERNAL_ORDER
INTERNAL_ORDER_HIE R_HZ INTERNAL_ORDER_HIE R_VR
MAINTENANCE_ACTIVIT SERVICE_COST_SUMMARY_FACT_VR.MAINT_AC Y_TYPE TIVITY_TYPE_ID=MAINTENANCE_ACTIVITY_TYPE .MAINT_ACTIVITY_TYPE_ID MAINTENANCE_PRIORI TY SERVICE_COST_SUMMARY_FACT_VR.PRIORITY _TYPE_ID=MAINTENANCE_PRIORITY.PRIORITY_T YPE_ID and SERVICE_COST_SUMMARY_FACT_VR.PRIORITY _ID=MAINTENANCE_PRIORITY.PRIORITY_ID SERVICE_COST_SUMMARY_FACT_VR.MATERIAL _ID=MATERIAL.MATERIAL_ID 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_ID=SERVICE_COST_SUMMARY_FA CT_VR.PLANT_ID
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
PLANT
137
Dimension Table PLANT_LOCATION
Join Expression PLANT_LOCATION.PLANT_ID=SERVICE_COST_S UMMARY_FACT_VR.PLANT_ID and PLANT_LOCATION.LOCATN_ID=SERVICE_COST_ SUMMARY_FACT_VR.LOCATN_ID SERVICE_COST_SUMMARY_FACT_VR.PROD_HIE R_ID=PRODUCT_HIERARCHY.PROD_HIER_ID SERVICE_COST_SUMMARY_FACT_VR.CTRL_ARE A_ID=PROFIT_CENTER.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.PROFIT_C NTR_ID=PROFIT_CENTER.PROFIT_CNTR_ID SERVICE_COST_SUMMARY_FACT_VR.CTRL_ARE A_ID=PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.PROFIT_C NTR_ID=PROFIT_CENTER_HIER_HZ.PROFIT_CNT R_ID SERVICE_COST_SUMMARY_FACT_VR.CTRL_ARE A_ID=PROFIT_CENTER_HIER_VR.CTRL_AREA_ID and SERVICE_COST_SUMMARY_FACT_VR.PROFIT_C NTR_ID=PROFIT_CENTER_HIER_VR.CHILD_ID SERVICE_COST_SUMMARY_FACT_VR.PROJ_ELE M_ID=PROJECT_ELEMENT.PROJ_ELEM_ID
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
PROJECT_ELEMENT
PROJECT_ELEMENT_HI SERVICE_COST_SUMMARY_FACT_VR.PROJ_ELE ER_HZ M_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELE M_ID PROJECT_ELEMENT_HI SERVICE_COST_SUMMARY_FACT_VR.PROJ_ELE ER_VR M_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMMARY_FACT_VR.FISC_YEA R= SERVICE_COST_SUMMARY_FACT_VR.PARTITION _YEAR SERVICE_COST_SUMMARY_FACT_VR.SYSTEM_ CONDITN_ID=SYSTEM_CONDITION.SYSTEM_CO NDITN_ID VARIANCE_CATEGORY.VARIANCE_CATEG_ID=SE RVICE_COST_SUMMARY_FACT_VR.VARIANCE_C ATEG_ID SERVICE_COST_SUMMARY_FACT_VR.WORK_CN TR_ID=WORK_CENTER.WORK_CNTR_ID AND SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID = WORK_CENTER.PLANT_ID
SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR SERVICE_COST_SUMM ARY_FACT_VR
SYSTEM_CONDITION
VARIANCE_CATEGORY
WORK_CENTER
138
Reports Service Master
Dimension Table WORK_CENTER_HIER_ HZ
Join Expression SERVICE_COST_SUMMARY_FACT_VR.WORK_CN TR_ID=WORK_CENTER_HIER_HZ.WORK_CNTR_I D AND SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID =WORK_CENTER_HIER_HZ.PLANT_ID SERVICE_COST_SUMMARY_FACT_VR.WORK_CN TR_ID=WORK_CENTER_HIER_VR.CHILD_ID AND SERVICE_COST_SUMMARY_FACT_VR.PLANT_ID =WORK_CENTER_HIER_VR.PLANT_ID
Service Master
This 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.
Reports
Functional Location Characteristics Equipment Characteristics
139
Functional Location Characteristics

View Functional Location Characteristics summary for the selected Company Code.
Report SQL
Equipment Characteristics
View Equipment Characteristics summary for the selected Company Code and Characteristic Name.
140
Equipment Characteristics by Plant

View equipment characteristics organized by plant name.
141
Equipment Characteristics by Class

View equipment characteristics organized by equipment hierarchy.
Report SQL

To analyze Service Master data you will need to create joins between the fact and dimension tables as follows:
142
Fact Table EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT Dimension Table BUSINESS_AREA Join Expression BUSINESS_AREA.BUS_AREA_ID=EQUIPMENT_C HAR_FACT.BUS_AREA_ID
CLASSIFICATION_HIER_ EQUIPMENT_CHAR_FACT.EQUIPMNT_ID = HZ CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_ID AND CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '002' CLASSIFICATION_HIER_ EQUIPMENT_CHAR_FACT.EQUIPMNT_ID = VR CLASSIFICATION_HIER_VR.CHILD_ID AND CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '002' COMPANY_CODE CONTROLLING_AREA COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=EQUIPMENT _CHAR_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=EQUIPME NT_CHAR_FACT.CTRL_AREA_ID 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_FA CT
EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT
COST_CENTER_HIER_H EQUIPMENT_CHAR_FACT.CTRL_AREA_ID=COST Z _CENTER_HIER_HZ.CTRL_AREA_ID and EQUIPMENT_CHAR_FACT.COST_CNTR_ID=COST _CENTER_HIER_HZ.COST_CNTR_ID COST_CENTER_HIER_V EQUIPMENT_CHAR_FACT.CTRL_AREA_ID=COST R _CENTER_HIER_VR.CTRL_AREA_ID and EQUIPMENT_CHAR_FACT.COST_CNTR_ID=COST _CENTER_HIER_VR.CHILD_ID EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ EQUIPMENT_CHAR_FACT.EQUIPMNT_ID=EQUIP MENT.EQUIPMNT_ID EQUIPMENT_CHAR_FACT.EQUIPMNT_ID=EQUIP MENT_HIER_HZ.EQUIPMNT_ID EQUIPMENT_CHAR_FACT.EQUIPMNT_ID=EQUIP MENT_HIER_VR.CHILD_ID EQUIPMENT_CHAR_FACT.FUNCTNL_LOCATN_ID =FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID EQUIPMENT_CHAR_FACT.FUNCTNL_LOCATN_ID = FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LO CATN_ID EQUIPMENT_CHAR_FACT.FUNCTNL_LOCATN_ID = FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID EQUIPMENT_CHAR_FACT.MATERIAL_ID=MATERI AL.MATERIAL_ID
EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT
EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT
FUNCTIONAL_LOCATIO N_HIER_VR MATERIAL
143
Fact Table EQUIPMENT_CHAR_FA CT
Dimension Table MATERIAL_BY_PLANT
Join Expression EQUIPMENT_CHAR_FACT.MATERIAL_ID=MATERI AL_BY_PLANT.MATERIAL_ID and EQUIPMENT_CHAR_FACT.PLANT_ID=MATERIAL_ BY_PLANT.PLANT_ID PLANT.PLANT_ID=EQUIPMENT_CHAR_FACT.PLA NT_ID PLANT_LOCATION.PLANT_ID=EQUIPMENT_CHAR _FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=EQUIPMENT_CHA R_FACT.LOCATN_ID SERVICE_PERSON.PERSON_ID=EQUIPMENT_CH AR_FACT.PERSON_ID_RESP TIME_DIM.CALENDAR_DATE=EQUIPMENT_CHAR _FACT.VALID_FROM_DATE UNIT_OF_MEASURE.UOM_ID=EQUIPMENT_CHAR _FACT.UOM_ID_VALUE VENDOR.VENDOR_ID=EQUIPMENT_CHAR_FACT. VENDOR_ID
EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT
EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT EQUIPMENT_CHAR_FA CT
SERVICE_PERSON TIME_DIM UNIT_OF_MEASURE VENDOR
VENDOR_BY_COMPANY VENDOR_BY_COMPANY.VENDOR_ID=EQUIPMEN T_CHAR_FACT.VENDOR_ID and VENDOR_BY_COMPANY.CMPNY_CODE_ID=EQUI PMENT_CHAR_FACT.CMPNY_CODE_ID BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=FUNCTIONAL_L OCATION_CHAR_FACT.BUS_AREA_ID
FUNCTIONAL_LOCATIO N_CHAR_FACT FUNCTIONAL_LOCATIO N_CHAR_FACT
CLASSIFICATION_HIER_ FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_ HZ LOCATN_ID =CLASSIFICATION_HIER_HZ.INTERNAL_CLASS_I D and CLASSIFICATION_HIER_HZ.CLASS_TYPE_ID = '003' CLASSIFICATION_HIER_ FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_ VR LOCATN_ID =CLASSIFICATION_HIER_VR.CHILD_ID and CLASSIFICATION_HIER_VR.CLASS_TYPE_ID = '003' COMPANY_CODE CONTROLLING_AREA COST_CENTER COMPANY_CODE.CMPNY_CODE_ID=FUNCTIONA L_LOCATION_CHAR_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=FUNCTIO NAL_LOCATION_CHAR_FACT.CTRL_AREA_ID FUNCTIONAL_LOCATION_CHAR_FACT.COST_CN TR_ID=COST_CENTER.COST_CNTR_ID and FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_ARE A_ID=COST_CENTER.CTRL_AREA_ID
FUNCTIONAL_LOCATIO N_CHAR_FACT
FUNCTIONAL_LOCATIO N_CHAR_FACT FUNCTIONAL_LOCATIO N_CHAR_FACT FUNCTIONAL_LOCATIO N_CHAR_FACT
FUNCTIONAL_LOCATIO N_CHAR_FACT
COST_CENTER_HIER_H FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_ARE Z A_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and FUNCTIONAL_LOCATION_CHAR_FACT.COST_CN TR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID
144
Reports SAP Master Data Reports
Fact Table FUNCTIONAL_LOCATIO N_CHAR_FACT
Dimension Table
Join Expression
COST_CENTER_HIER_V FUNCTIONAL_LOCATION_CHAR_FACT.CTRL_ARE R A_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and FUNCTIONAL_LOCATION_CHAR_FACT.COST_CN TR_ID=COST_CENTER_HIER_VR.CHILD_ID FUNCTIONAL_LOCATIO N FUNCTIONAL_LOCATIO N_HIER_HZ FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_ LOCATN_ID=FUNCTIONAL_LOCATION.FUNCTNL_ LOCATN_ID FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_ LOCATN_ID = FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LO CATN_ID FUNCTIONAL_LOCATION_CHAR_FACT.FUNCTNL_ LOCATN_ID = FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID PLANNING_GROUP.PLANT_ID=FUNCTIONAL_LOC ATION_CHAR_FACT.PLANT_ID and PLANNING_GROUP.PLANNG_GRP_ID=FUNCTION AL_LOCATION_CHAR_FACT.PLANNG_GRP_ID PLANT.PLANT_ID=FUNCTIONAL_LOCATION_CHA R_FACT.PLANT_ID PLANT_LOCATION.PLANT_ID=FUNCTIONAL_LOC ATION_CHAR_FACT.PLANT_ID and PLANT_LOCATION.LOCATN_ID=FUNCTIONAL_LO CATION_CHAR_FACT.LOCATN_ID SERVICE_PERSON.PERSON_ID=FUNCTIONAL_L OCATION_CHAR_FACT.PERSON_ID_RESP TIME_DIM.CALENDAR_DATE = FUNCTIONAL_LOCATION_CHAR_FACT.VALID_FR OM_DATE UNIT_OF_MEASURE.UOM_ID=FUNCTIONAL_LOC ATION_CHAR_FACT.UOM_ID_VALUE
FUNCTIONAL_LOCATIO N_HIER_VR PLANNING_GROUP
FUNCTIONAL_LOCATIO N_CHAR_FACT FUNCTIONAL_LOCATIO N_CHAR_FACT FUNCTIONAL_LOCATIO N_CHAR_FACT
SERVICE_PERSON TIME_DIM
UNIT_OF_MEASURE
SAP Master Data Reports

SAP 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.
145
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
146
Activity Hierarchy Data Discovery

View Activity Hierarchies for a specified Controlling Area, Parent Activity, and Activity Hierarchy.
Report SQL
SELECT 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_FULLNAME FROM ACTIVITY_HIER_HR, ACTIVITY_HIER_VR, ACTIVITY WHERE ( 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
147
( ( 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 SQL
All report SQL is located in the Rapid Mart installation directory under "\Sample\DDL".
148
Profit Center Hierarchy Data Discovery

View Profit Center Hierarchies for a specified Controlling Area, Parent Profit Center(s), and Profit Center Hierarchy (or Hierarchies).
Report SQL
Cost Element Hierarchy Data Discovery

View Cost Element Hierarchies for a specified Chart of Accounts, Parent Cost Element, and Cost Element Hierarchy.
Report SQL
149
Internal Order Hierarchy Data Discovery

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

View Functional Area Hierarchies for a specified Parent Functional Area and Functional Area Hierarchy.
Report SQL
151
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)
Report SQL
152
FS Account Hierarchy Data Discovery

View 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 SQL
SELECT DISTINCT GL_ACCOUNT_HIER_HZ.LEVEL_0_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_1_FULLNAME, GL_ACCOUNT_HIER_HZ.LEVEL_2_FULLNAME,
153
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_NAME FROM GL_ACCOUNT_HIER_HZ, FS_HIERARCHY FS_HIERARCHY_DISCOVERY_HZ, GL_ACCOUNT_HIER GL_ACCOUNT_DISCOVERY_HZ, GL_ACCOUNT_MASTER WHERE ( 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.CUR RENT_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_DISCOVER Y_HZ.HIERARCHY_NAME and GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=GL_ACCOUNT_DISCOVE RY_HZ.CHART_OF_ACCTS_ID and GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=GL_ACCOUNT_DISCOVERY_H Z.CHILD_ID ) AND ( GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=FS_HIERARCHY_DISCO VERY_HZ.CHART_OF_ACCTS_ID and GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=FS_HIERARCHY_DISCOVE RY_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_2_ID AND GL_ACCOUNT_HIER_HZ.LEVEL_4_ID <> GL_ACCOUNT_HIER_HZ.LEVEL_3_ID AND GL_ACCOUNT_HIER_HZ.LEVEL_5_ID <> GL_ACCOUNT_HIER_HZ.LEVEL_4_ID )
154
Project Element Hierarchy Data Discovery

View Project Element Hierarchies for a specified Parent Project Element and Project Element Hierarchy.
Report SQL
Equipment Hierarchy Data Discovery

View Equipment Hierarchies for a specified Parent Equipment and Equipment Hierarchy.
Report SQL
155
Functional Location Hierarchy Data Discovery

View Functional Location Hierarchies for a specified Parent Functional Location and Functional Location Hierarchy.
Report SQL
Work Center Hierarchy Data Discovery

View Work Center Hierarchies for a specified Parent Work Center and Work Center Hierarchy.
Report SQL
156
BOM Hierarchy Data Discovery

View BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.
Report SQL
157
Organization Unit Data Discovery

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

View Position Hierarchies for the specified Parent Position(s).
Report SQL
158
Data Auditing
These 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: Report Name Invalid Cost Center Hierarchy Invalid Activity Hierarchy Invalid Cost Element Hierarchy Invalid Functional Area Hierarchy Invalid GL Account Hierarchy Invalid Internal Order Hierarchy Invalid Profit Center Hierarchy Invalid Project Element Hierarchy Invalid Work Center Hierarchy Invalid Data Table COST_CENTER_HIER_BAD ACTIVITY_HIER_BAD COST_ELEMENT_HIER_BAD FUNCTIONAL_AREA_HIER_BAD GL_ACCOUNT_HIER_BAD INTERNAL_ORDER_HIER_BAD PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT_HIER_BAD WORK_CENTER_HIER_BAD
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 Hierarchy

Show Cost Center Hierarchy records that have failed validation in Data Services.
Report SQL
SELECT 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,
159
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_FLAG FROM 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 ACTIVITY Hierarchy Table ACTIVITY_HIER_HZ Join Text ACTIVITY.CTRL_AREA_ID=ACTIVITY_HIER_H Z.CTRL_AREA_ID and ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HZ.A CTIVITY_ID ACTIVITY.CTRL_AREA_ID = ACTIVITY_HIER_VR.CTRL_AREA_ID and ACTIVITY.ACTIVITY_ID = ACTIVITY_HIER_VR.CHILD_ID BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_ OF_MATERIALS_HIER_HZ.BOM_CATEG_ID and BILL_OF_MATERIALS.BOM_ID=BILL_OF_MAT ERIALS_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_O F_MATERIALS_HIER_HZ.BOM_NODE_ID BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_ OF_MATERIALS_HIER_VR.BOM_CATEG_ID and BILL_OF_MATERIALS.BOM_ID=BILL_OF_MAT ERIALS_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_O F_MATERIALS_HIER_VR.CHILD_ID COST_CENTER.CTRL_AREA_ID=COST_CENT ER_HIER_HZ.CTRL_AREA_ID and COST_CENTER.COST_CNTR_ID=COST_CEN TER_HIER_HZ.COST_CNTR_ID
ACTIVITY
ACTIVITY_HIER_VR
BILL_OF_MATERIALS
BILL_OF_MATERIALS_HIE R_HZ
BILL_OF_MATERIALS
BILL_OF_MATERIALS_HIE R_VR
COST_CENTER
COST_CENTER_HIER_HZ
160
Dimension Table COST_CENTER
Hierarchy Table COST_CENTER_HIER_VR
Join Text COST_CENTER.CTRL_AREA_ID=COST_CENT ER_HIER_VR.CTRL_AREA_ID and COST_CENTER.COST_CNTR_ID=COST_CEN TER_HIER_VR.CHILD_ID COST_ELEMENT.COST_ELEM_ID=COST_ELE MENT_HIER_HZ.COST_ELEM_ID and COST_ELEMENT.CHART_OF_ACCT_ID=COST _ELEMENT_HIER_HZ.CHART_OF_ACCT_ID COST_ELEMENT.CHART_OF_ACCT_ID=COST _ELEMENT_HIER_VR.CHART_OF_ACCT_ID and COST_ELEMENT.COST_ELEM_ID=COST_ELE MENT_HIER_VR.CHILD_ID COUNTRY_GROUP.COUNTRY_GRP_ID = COUNTRY_GROUP_STATUS.COUNTRY_GRP _ID EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIE R_HZ.EQUIPMNT_ID EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIE R_VR.CHILD_ID GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_I D=FS_HIERARCHY.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_HZ.HIER_ID=FS_HIERA RCHY.FS_VERSION_ID and GL_ACCOUNT_HIER_HZ.GL_ACCT_ID=FS_HI ERARCHY.CHILD_ID GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I D=FS_HIERARCHY.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_VR.HIER_ID=FS_HIERA RCHY.FS_VERSION_ID and GL_ACCOUNT_HIER_VR.CHILD_ID=FS_HIER ARCHY.CHILD_ID
COST_ELEMENT
COST_ELEMENT_HIER_H Z
COST_ELEMENT
COST_ELEMENT_HIER_V R
COUNTRY_GROUP
COUNTRY_GROUP_STAT US EQUIPMENT_HIER_HZ EQUIPMENT_HIER_VR GL_ACCOUNT_HIER_HZ
EQUIPMENT EQUIPMENT FS_HIERARCHY
FS_HIERARCHY
GL_ACCOUNT_HIER_VR
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU _HZ NCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA _ID FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU _VR NCTIONAL_AREA_HIER_VR.CHILD_ID FUNCTIONAL_LOCATION_ FUNCTIONAL_LOCATION.FUNCTNL_LOCATN HIER_HZ _ID=FUNCTIONAL_LOCATION_HIER_HZ.FUN CTNL_LOCATN_ID FUNCTIONAL_LOCATION_ FUNCTIONAL_LOCATION.FUNCTNL_LOCATN HIER_VR _ID=FUNCTIONAL_LOCATION_HIER_VR.CHIL D_ID GL_ACCOUNT_HIER_HZ GL_ACCOUNT_HIER_HZ.HIER_ID=GL_ACCO UNT_HIER.HIER_ID and GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_I D=GL_ACCOUNT_HIER.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_HZ.GL_ACCT_ID=GL_A CCOUNT_HIER.CHILD_ID
FUNCTIONAL_AREA FUNCTIONAL_LOCATION
FUNCTIONAL_LOCATION
GL_ACCOUNT_HIER
161
Dimension Table GL_ACCOUNT_HIER
Hierarchy Table GL_ACCOUNT_HIER_VR
Join Text GL_ACCOUNT_HIER_VR.HIER_ID=GL_ACCO UNT_HIER.HIER_ID and GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I D=GL_ACCOUNT_HIER.CHART_OF_ACCT_ID and GL_ACCOUNT_HIER_VR.CHILD_ID=GL_ACC OUNT_HIER.CHILD_ID GL_ACCOUNT_MASTER.CHART_OF_ACCT_I D=GL_ACCOUNT_HIER_HZ.CHART_OF_ACC T_ID and GL_ACCOUNT_MASTER.GL_ACCT_ID=GL_A CCOUNT_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.CHART_OF_ACCT_I D=GL_ACCOUNT_HIER_VR.CHART_OF_ACC T_ID and GL_ACCOUNT_MASTER.GL_ACCT_ID=GL_A CCOUNT_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)
GL_ACCOUNT_MASTER
GL_ACCOUNT_HIER_HZ
GL_ACCOUNT_MASTER
GL_ACCOUNT_HIER_VR
INTERNAL_ORDER
INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN HZ TERNAL_ORDER_HIER_HZ.INTERNAL_ORDE R_ID INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN VR TERNAL_ORDER_HIER_VR.CHILD_ID PRODUCT_HIERARCHY OBJECT_STATUS MATERIAL.PROD_HIER_ID=PRODUCT_HIERA RCHY.PROD_HIER_ID OBJECT_STATUS_HZ.OBJ_ID=OBJECT_STAT US.OBJ_ID
INTERNAL_ORDER MATERIAL OBJECT_STATUS_HZ ORGANIZATION_UNIT
ORGANIZATION_UNIT_HIE ORGANIZATION_UNIT.ORG_UNIT_KEY R_HZ =ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT _KEY ORGANIZATION_UNIT_HIE ORGANIZATION_UNIT.ORG_UNIT_KEY=ORG R_VR ANIZATION_UNIT_HIER_VR.CHILD_KEY PAYROLL_PERIOD_PARA METER PAYROLL_PERIOD.PERIOD_PARAMETER_ID = PAYROLL_PERIOD_PARAMETER.PERIOD_PA RAMETER_ID
ORGANIZATION_UNIT PAYROLL_PERIOD
162
Dimension Table POSITION POSITION PROFIT_CENTER
Hierarchy Table POSITION_HIER_HZ POSITION_HIER_VR
Join Text POSITION.POSITION_ID=POSITION_HIER_HZ .POSITION_ID POSITION.POSITION_ID=POSITION_HIER_VR .CHILD_ID
PROFIT_CENTER_HIER_H PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C Z ENTER_HIER_HZ.CTRL_AREA_ID and PROFIT_CENTER.PROFIT_CNTR_ID=PROFIT _CENTER_HIER_HZ.PROFIT_CNTR_ID PROFIT_CENTER_HIER_V R PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C ENTER_HIER_VR.CTRL_AREA_ID and PROFIT_CENTER.PROFIT_CNTR_ID=PROFIT _CENTER_HIER_VR.CHILD_ID PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE CT_ELEMENT_HIER_HZ.PROJ_ELEM_ID PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE CT_ELEMENT_HIER_VR.CHILD_ID
PROFIT_CENTER
PROJECT_ELEMENT PROJECT_ELEMENT WORK_CENTER
PROJECT_ELEMENT_HIE R_HZ PROJECT_ELEMENT_HIE R_VR
WORK_CENTER_HIER_HZ WORK_CENTER.WORK_CNTR_ID=WORK_CE NTER_HIER_HZ.WORK_CNTR_ID and WORK_CENTER.PLANT_ID=WORK_CENTER_ HIER_HZ.PLANT_ID WORK_CENTER_HIER_VR WORK_CENTER.WORK_CNTR_ID=WORK_CE NTER_HIER_VR.CHILD_ID AND WORK_CENTER.PLANT_ID=WORK_CENTER_ HIER_VR.PLANT_ID
WORK_CENTER
163
164
Universe
chapter
Universe Overview
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 Hierarchies
Then 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 Universe
The 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 Universe
An additional section on customizing the SAP Plant Maintenance universe is also presented.
Customizing the Universe
Universe Design Principles

The 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.
166
Universe Universe Design Principles
Universe Terminology
Star 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
167
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 currency Semi-Additive Measure: measure that can be summarized only across selected dimensions, such as sales order quantity Non-Additive Measure: measures that cant be summarized, such as net price. Attribute: descriptive information; cant 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.
168
Universe Table Layout

The 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 Strategy
Contexts: 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.
169
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)
170
Universe Hierarchies
Techniques
These 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 years 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 Overview
In 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.
171
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
172
Note: The screenshot above is an example from the SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions.
Geographic Hierarchies
These 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 Dimension
The 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 Dimension

The 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 Hierarchy

This hierarchy organizes materials in reports by the SAP solutions Product Hierarchy.
173
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 Example

We 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.
174
Horizontal Hierarchy Structure

Horizontal hierarchies are organized so that all levels (or nodes) appear as columns on a single row of data. Vertical hierarchies represent each level or node with an individual row of data. The horizontal 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.
175
The primary key for a horizontal hierarchy contains all the level ids (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 Structure

The 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:
176
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.
177
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:
Vertical Hierarchy Subset for A1000
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.
178
Sample Report for Activity (Vertical Hierarchy):
Report Generation - Propagation of Leaf Nodes

As described earlier, the horizontal hierarchy can be used to create an indented report where the each lower level (leaf level) is more indented than the previous level.
179
Sample Report (Propagation of Leaf Nodes):
Hierarchy Filters
Hierarchy 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, well 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.
180
The filters appear below the Fact Table Classes in any universe. Those for GL Account Hierarchy appear as shown below:
Unique GL Account Hierarchy Filters

These 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.
181
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 Filters

All 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 Hierarchies
The 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.
182
Example: In the example below, Activity 1" is both the parent and child of Activity 2. (as Parent) Activity1
Activity2
Activity3 Activity5 Activity6
Activity1 (as Child)
Activity4
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 Classes

Invalid 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 Layout

The 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.
183
Invalid Hierarchies Layout:
Note: The screenshot above is an example from the SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions.
184
Universe Plant Maintenance Specific Hierarchies
Plant Maintenance Specific Hierarchies

Accounting Hierarchies
The 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: Hierarchy Name Activity Cost Center Cost Element Functional Area Internal Orders Table and Column CCSS-LSTAR CCSS-KOSTL CCSS-KSTAR GLFUNCT-RFAREA CCSS-AUFNR
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 Hierarchies
These 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 Classification Equipment Functional Location Project Element Work Center Source Tables KSSK, TCLA EQUI, EQUZ IFLOT, ILOA PRHI CRHD, CRHH, CRHS
185
Universe Plant Maintenance Specific Hierarchies
Of these hierarchies only Project Element can have invalid records in SAP solutions. See Invalid Hierarchies on page 182 for more details.
186
Universe SAP Plant Maintenance Universe
SAP Plant Maintenance Universe

The 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 hierarchies
The universe is well documented and logically organized to help universe users easily navigate to a specific object. The information in this chapter is useful to understand the data in the Rapid Mart and how to build reports using the data. The universe, and this chapter, are logically grouped into subject areas. They are:
Universe Objects & Classes Common Dimensions Service Notification Service Order Service Operation Service Confirmation
187
Service Cost Summary (Horizontal) Service Cost Summary (Vertical) MTBR and MTTR Filters & Techniques Universe Validation
188
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 below:
189
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 22 Techniques: These are advanced technique objects that have developed for the Web Intelligence reports. See Techniques on page 171 for details.
Common Dimensions
Common Dimensions are those dimensions shared by more than one subject area (or fact table). They appear as shown below in the universe.
190
Plant Maintenance Common Dimension Classes (1 of 2)
191
Plant Maintenance Common Dimension Classes (2 of 2)
192
ACTIVITY
Physical 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.
CAPACITY
The 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.
CLASSIFICATIONS
System 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 Class Hier Hz Functional Location Class Hier Vr
Functional Location Classification
COST CENTER
Organizational 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
193
Cost center hierarchies presented stacked vertically and flattened horizontally. Cost center contact numbers, and geography are also included.
COST ELEMENT
A cost element classifies the organization's valuated consumption of production factors within a controlling area. SAP solutions maintains both primary and secondary cost elements.
CUSTOMER
Customers are the companies and individuals to whom your company sells goods and services.
DOCUMENT ATTRIBUTES
Master 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 Category Document 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 Type Document 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:
194
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 clientspecific. 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. 2. 3. 1. Monitor the costs of short-term measures Monitor the costs and revenues related to a specific service Monitor ongoing costs Overhead orders
Internal orders are divided into the following categories:
195
2. 3. 4.
Capital investment orders Accrual orders 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:

OBJECT
Controlling Area Currency Local (Company Code) Currency Transaction (Document) Currency
Object 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 Class The 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).
196
Object Type A 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 STRUCTURE
Various components that classify transaction documents within your business enterprise. These include: Business Activity Business activity attributes from T022/T022T. Business Area An 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 Accounts A 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 Code The 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 Area An 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.
197
These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area. Planning Group The 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:

Plant
Customer - Bank collection Customer - Crisis area Vendor: - Member of a consolidation group
In 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 Location Plant location attributes.
PEOPLE
People 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 MAINTENANCE

Attributes associated Production Planning and Plant Maintenance functions. The sub-classes include: Control Key A 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
198
Maintenance Activity Type A 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 Priority The relationship between the order priority from a maintenance order and the requirement urgency. Malfunction Cause One of 3 pre-defined notification catalog objects - Malfunction Cause. Describes the incident or circumstances responsible for a malfunction Malfunction Damage One of 3 pre-defined notification catalog objects - Malfunction Damage. Describes the breakage sustained by a technical object Malfunction Effect Describes the consequences of the malfunction in the technical objects performance. Description of malfunction effects from T357A_T Malfunction Object Part One of 3 pre-defined notification catalog objects - Malfunctioning Object Part. Describes the physical location of the malfunction. Notification A 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 Suitability Key suitability required for carrying out the operation (for example, welding certificate or NC programming course) - from T423T System Condition System Condition descriptive attributes from T253M_T. Variance Category A classification of variances based on their cause.
199
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 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
You can calculate the following variance categories on the output side:
PROFIT CENTER
Organizational 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-ofsales 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 DIMENSIONS

Time related dimensions include relevant time dimensions, fiscal period dimensions, and Calendar dimensions. This class includes the Time Dimensions Allow 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
200
Notification Date Time Dim
FISCAL PERIOD DIMENSIONS Fiscal 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
VENDOR
Business 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
201
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 NOTIFICATION FACT SERVICE SERVICE CONFIRMCOST ATION SUMMARY FACT FACT X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X - vertical only X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X SERVICE OPERATION FACT X SERVICE ORDER FACT
Activity & Hierarchy Business Activity Business Area Capacity Chart Of Accounts Classification Hierarchy Company Code Control Key Controlling Area Cost Center & Hierarchy Cost Element & Hierarchy Currency Customer Document Category Document Type Equipment & Hierarchy Financial Record Category Financial Record Type Fisc Period Functional Area & Hierarchy Functional Location & Hierarchy Internal Order & Hierarchy Internal Order Status Maintenance Activity Type Maintenance Priority Malfunction Cause
202
Dimension Table
MTBR MTTR FACT
NOTIFICATION FACT X
SERVICE SERVICE CONFIRMCOST ATION SUMMARY FACT FACT
SERVICE OPERATION FACT
SERVICE ORDER FACT
Malfunction Damage Malfunction Effect Malfunction Object Part Material & Product Hierarchy Material By Plant Notification Object Class Object Type Operation Suitability Planning Group Plant Plant Location Profit Center & Hierarchy Project Element & Hierarchy Service Person System Condition Time Dim Unit Of Measure Variance Category Vendor Vendor By Company Work Center & Hierarchy X X X X X X X X X
X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X 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 Notification
A 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.
203
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 Measures Contains 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 Classes

The Notification subject area classes contain all remaining objects for Notification. They appear as shown below in the universe
204
Service Notification Subject Area Classes
NOTIFICATION Contains primary key elements for service notification and the following subclasses:
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 notifications unit of measurement. Notification - Time - Un-aggregated values (not summed, averaged, etc.) for:
downtime repair time completion time
Service Notification Star Schema Layout

Here is a graphical representation of the star schema for this subject area as it appears in the universe designer
205
Service Notification Star Schema
Service Order
Maintenance 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 Measures

The Service Order measures contain all additive and semi-additive measures for Service Orders. They appear as shown below in the universe:
206
Service Order Measures
Service Order Measures Contains 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 Classes

The Service Order subject area classes contain all remaining objects for service orders. They appear as shown below in the universe
207
Service Order Subject Area Classes
SERVICE ORDER Contains primary key elements for the service order and the following subclasses:
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 Layout

208
Service Order Star Schema
Service Operation
Service 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 Measures

The Service Operation measures contain all additive and semi-additive measures for Service Operations. They appear as shown below in the universe:
209
Service Operation Measures
Service Operation Measures Contains 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 Classes

The Service Operation subject area classes contain all remaining objects for service operations. They appear as shown below in the universe
210
Service Operation Subject Area Classes
SERVICE OPERATION Contains 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 Layout

211
Service Operation Star Schema
Service Confirmation
A 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
212
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 retained
Confirmations 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 completed
Confirmations can be partial or final.
Service Confirmation Measures

The 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 Measures Contains the confirmation related measures.
213
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 Classes

The Service Confirmation subject area classes contain all remaining objects for service confirmations. They appear as shown below in the universe Service Confirmation Subject Area Classes
SERVICE CONFIRMATION Contains 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
214
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 Layout

Here is a graphical representation of the star schema for this subject area as it appears in the universe designer Service Confirmation Star Schema
215
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:
The 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. Measures

The 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 Measures Contains 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
216
Service Cost Sum Hz - Budget Measures - Budget costs Beginning Balance for fiscal year. PTD balances (fiscal periods 1 - 16) QTD balances (quarters 1 - 4) YTD balance
Service Cost Summary Hz. Subject Area Classes

The Service Cost horizontal subject area classes contain all remaining objects for Service Cost in horizontal representation. They appear as shown below in the universe Service 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
217
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 Layout

Here is a graphical representation of the star schema for this subject area as it appears in the universe designer Service Cost Summary Hz. Star Schema
218
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:
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.
Service Cost Summary Vr. Measures

The 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 costs Period Beginning Balance PTD Balance Credit / Debit amounts for PTD, YTD, and QTD Rolling 16 period totals
219
Service Cost Sum Vr - Budget Measures TRX - Budget costs Period Beginning Balance PTD Balance Credit / Debit amounts for PTD, YTD, and QTD Rolling 16 period totals
Service Cost Summary Vr. Subject Area Classes

The Service Cost vertical subject area classes contain all remaining objects for Service Cost in vertical representation. They appear as shown below in the universe Service 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
220
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 Layout

Here is a graphical representation of the star schema for this subject area as it appears in the universe designer Service Cost Summary Vr. Star Schema
221
MTBR and MTTR

The section calculates:
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 Measures

The 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 Measures Contains 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 Classes

The MTBR & MTTR subject area classes contain all remaining objects for MTBR & MTTR. They appear as shown below in the universe
222
MTBR & MTTR Subject Area Classes
MTBR and MTTR Contains primary key elements for MTBR & MTTR and the following subclasses:
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 Layout

223
MTBR & MTTR Star Schema
Filters & Techniques

Filters
The universe contains filters that allow you to restrict the results of your reports. The filters appear after the Fact Table Classes in the universe
224
SAP Plant Maintenance Universe Filters:
225
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 Filters Includes 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 Filters Includes filters allowing selection of budget or actual values (Actual: Record Type = 04; Budget: Record Type= 01). Company Code Filters Conditions to limit result set to either a single or multiple Company Codes. Hierarchy Filters All 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)
226

Techniques
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)
Techniques are advanced technique objects developed for the Web Intelligence reports. They are described in Techniques on page 17.
Universe Validation
When 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.
227
Integrity Check Results.
Structure Divergences
Some 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 Errors

These 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 Divergences
These 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, SQLServer, and DB2 will have different messages for the same errors.
228
Universe SAP Service Master Universe
SAP Service Master Universe

The 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:
The universe is well documented and logically organized to help universe users easily navigate to a specific object. The information in this chapter is useful to understand the data in the Rapid Mart and how to build reports using the data. The universe, and this chapter, are logically grouped into subject 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
229
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 below Service 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.
230
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 22 Techniques: These are advanced technique objects that have developed for the Web Intelligence reports. See Techniques on page 17 for details.
SAP Service Master Common Dimensions

Common Dimensions are those dimensions shared by more than one subject area (or fact table). They appear as shown below in the universe.
231
Service Master Common Dimension Classes:
CLASSIFICATIONS
System 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.
232
Equipment Classification
Equipment Class Hier Hz Equipment Class Hier Vr Functional Location Class Hier Hz Functional Location Class Hier Vr
Functional Location Classification
COST CENTER
EQUIPMENT
Used 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 LOCATION
Organizational 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.
MATERIAL
The 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 Plant MARA and MARC Tables - Plant Level Material attributes.
233
Material (Product) Hierarchy Materials can be grouped into hierarchies. Every material (product) can be assigned to one material product hierarchy level.
Various components that classify transaction documents within your business enterprise. These include: Business Area An 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. Company Code The 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 Area An 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 Group The 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:

Plant
In 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.
234
Plant Location A place in a maintenance plant at which a technical object is physically located.
PEOPLE
Service Person - An employee who is actively involved in troubleshooting, maintenance, and repair activities.

Time related dimensions include relevant time dimensions, fiscal period dimensions, and Calendar dimensions. This class includes the Time Dimensions Allow 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:
Valid From Date Time Dim

Downtime Unit of Measure Duration Unit of Measure Work Unit of Measure
VENDOR
235
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 Dimension Table 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 Dim Unit Of Measure Vendor Vendor By Company X X X X X X X Equipment Characteristics X X X X X X X X X X X X X X X X Functional Location Characteristics X X X X 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.
236
This 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 Measures

Equipment 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 Classes

The Equipment Characteristics subject area classes contain all remaining objects for Equipment Characteristics. They appear as shown below in the universe Equipment Characteristics Subject Area Classes
237
EQUIPMENT CHAR Contains 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 Layout

Here is a graphical representation of the star schema for this subject area as it appears in the universe designer Equipment Characteristics Star Schema
238

This 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 Measures

Functional 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 Classes

The Functional Location Characteristics subject area classes contain all remaining objects for Functional Location Characteristics. They appear as shown below in the universe Functional Location Characteristics Subject Area Classes
239
FUNCTIONAL LOCATION CHAR Contains 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 validto 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 Layout

Here is a graphical representation of the star schema for this subject area as it appears in the universe designer Functional Location Characteristics Star Schema
240
SAP Service Master Filters & Techniques

Filters
The 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 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 Filters Conditions to limit result set to either a single or multiple Company Codes. Hierarchy Filters All 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)
241

Techniques
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)
Techniques are advanced technique objects developed for the Web Intelligence reports. They are described in Techniques on page 17.
SAP Service Master Universe Validation

Integrity Check Results.
242

These 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, SQLServer, and DB2 will have different messages for the same errors.
243
Universe SAP Master Data Universe
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:
The universe is well documented and logically organized to help universe users easily navigate to a specific object.
Universe Objects & Classes - Master Data

All 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
244
Top Level Classes
245
ACTIVITY
Physical 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.
BENEFITS
In 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 Area The 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 Plan The 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)
246
Benefit Program Group A 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 Account A 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 Coverage An option for a health plan, chararacterized by the number of dependents that can be covered. Enrollment Type Benefit program enrollment type descriptive attributes from DD07T, BEN_ENRTYP domain. A -Automatic, D - Default, M - Manual. Health Plan Health Plan descriptive attributes from T5UCE Insurance Coverage Group Benefit insurance coverage rules and formulas from T74FB, T74FC, PA0168 (date-effective) Insurance Option This 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 Group A customer-defined group of investments that can be assigned to plans in the categories 'Savings' and 'Miscellaneous'. Investment Plan A customer-defined option for plans in the categories Savings and Miscellaneous that lets employees choose how their contributions are invested.
247
BENEFIT RULES Identifying 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 Category Part 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 Status A tool used to control processing of a BOM in different application areas. Bill of Materials Usage A 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.
CAPACITY
The 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.
248
Capacity by Work Center Standard work center capacity information from CRCA/CRHD/KAKO. Capacity Category A 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 Type Capacity Object Type (like Order, Task List) - from DD07T TYPKZ domain. Capacity Planning Group Capacity planner group descriptive attributes (from TC27T).
CENTRAL ADDRESS
This 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.
CLASSIFICATIONS
System 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 CENTER
249
COST ELEMENT
A cost element classifies the organization's valuated consumption of production factors within a controlling area. SAP solutions maintains both primary and secondary cost elements.
CUSTOMER
Customers are the companies and individuals to whom your company sells goods and services. Customer by Company Intersection of Company and Customer records. Used by both Customer Items and Customer Totals
DOCUMENT ATTRIBUTES
Master 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 Category Document 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
250
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 Type Document 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 clientspecific. 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.
251
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 Key Key determining the reference date for various entities - Milestone, PRT Domain MLST_SDDAT; TCA55 Special Stock Indicator Stock of materials that must be managed separately for reasons of ownership or location. An example is consignment stock from vendors. Standard Text Key Standard text Key descriptions for activities from T435T. Standard Value Key Capacity Standard Value Key descriptive attributes from TC21T. Valuation Type The 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.
252
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.
253
Transaction Type - Transaction type of the Financial Document from table T856T. 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 freegoods, 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
PURCHASING DOCUMENT ATTRIBUTES
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
254
EMPLOYEE
In HR, the employee class tracks information about employees such as name,address, birth date, Gender, Marital status, number of dependents, etc.
EMPLOYEE ATTRIBUTES
Additional 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
255
EQUIPMENT
Used 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 LOCATION
Organizational 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 TERM01
Describes when in the delivery process the receiver of goods takes physical ownerships of the those goods.
INTERNAL ORDERS
Production 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. 2. Monitor the costs of short-term measures Monitor the costs and revenues related to a specific service
256
3. 1. 2. 3. 4.
Monitor ongoing costs Overhead orders Capital investment orders Accrual orders Orders with revenues.
Internal orders are divided into the following categories:
Internal Order Status Internal 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 Type Job leave type descriptive attributes from T533T
MATERIAL
The 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 Batch Batch material management - Material Master from MCHA Material by Plant MARA and MARC Tables - Plant Level Material attributes. Material Group A grouping of materials and services according to their characteristics.
257
Material (Product) Hierarchy Materials can be grouped into hierarchies. Every material (product) can be assigned to one material product hierarchy level. Material Production Defines production version information (from MKAL). Material Type A 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 Sources Currency 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 Types Currency 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:
258
Group currency Hard currency Index currency Global company currency
Monetary Currencies The 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 Rates These are the conversion rates used to convert one currency to another. They are used to compute global currency amounts in the universe.
MRP
Material 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 Controller The 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.
259
Mrp Element Type A 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 Group The 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 Size A key that defines which lot-sizing procedure the system uses for calculating the quantity to procure in the MRP run. Mrp Profile A 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 Type A 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.
OBJECT
Object 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 Class The 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
260
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 Type The 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 Status Object statuses from JEST. Object Status Hz Dimensional component loading horizontally represented selected ERP Object status information from JEST for selected Statuses from OBJECT_STATUS. Object Type A 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).
Various components that classify transaction documents within your business enterprise. These include: Account Type A 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.
261
Business Activity Business activity attributes from T022/T022T. Business Area An 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 Accounts A 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 Code The 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 Area An 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 Group A 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.
262
Credit Control Area An 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 Channel CA 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. Division An organizational unit based on responsibility for sales or profits from saleable materials or services. Employee Group The employee group is an organizational entity which is governed by specific personnel regulations. An employee group is divided into several employee subgroups. Employee Subgroup An employee subgroup is an organizational entity within an employee group which is governed by specific personnel regulations. Functional Area An 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 Hierarchy A 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.
263
Organization (Structure) Key A 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 Unit An 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 Area A 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 Administrator Portal 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
264
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 Area A 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 Subarea An organizational entity that represents part of a personnel area. It is delimited according to personnel administration, time management, and payroll accounting criteria. Planning Group The 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:

Plant
In 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 Location Plant location attributes. Purchase Group A 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.
265
Purchase Organization An 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 District A geographical sales district or sales region. You can assign customers to a sales district and use the sales district to generate sales statistics. Sales Group Organizational 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 Office A 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 Hierarchy Hierarchy associated with Sales Organizations Sales Organization A organizational unit in Logistics that structures the company according to its sales requirements. A sales organization is responsible for selling materials and services. Storage Location An 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 Area The 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.
266
The production supply area groups together work centers near to production storage bins, taking the material staging type into consideration. Valuation Area An organizational unit in Logistics subdividing an enterprise for the purpose of uniform and complete valuation of material stocks. Warehouse An organizational division of a plant for managing materials stored in different places. Work Contract A 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 Area The physical area of validity of a collective agreement. Pay Scale Type The economic area to which a collective agreement applies, for example metal industry or the chemical industry. Payroll Cumulation Type Descriptive attributes for calendar-associated cumulation types. Payroll Period Period for which regular payroll is run. A payroll period is identified by a period number and payroll year. Payroll Period Parameter Payroll Period Parameter descriptive attributes, defines periodicity of the payroll run. Payroll Status Descriptive attributes for Payroll Indicator for most recent update of results record. Payroll Type Characteristic used by the system to recognize which type of payroll run is to be carried out.
267
Salary Range Defines 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 Type Object 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.
PEOPLE
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.
POSITION
An 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 PROCEDURE
Rule 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 MAINTENANCE

Attributes associated Production Planning and Plant Maintenance functions. The sub-classes include:
268
Component An 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 Key A 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 Text Text 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 Type A 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 Priority The relationship between the order priority from a maintenance order and the requirement urgency. Malfunction Cause One of 3 pre-defined notification catalog objects - Malfunction Cause. Describes the incident or circumstances responsible for a malfunction Malfunction Damage One of 3 pre-defined notification catalog objects - Malfunction Damage. Describes the breakage sustained by a technical object
269
Malfunction Effect Describes the consequences of the malfunction in the technical objects performance. Description of malfunction effects from T357A_T Malfunction Object Part One of 3 pre-defined notification catalog objects - Malfunctioning Object Part. Describes the physical location of the malfunction. Notification A 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 Suitability Key suitability required for carrying out the operation (for example, welding certificate or NC programming course) - from T423T Procurement Type A classification indicating whether a material is produced internally, procured externally, or both. Production Scheduler Production scheduler descriptive attributes from T024F Scheduling Error Planned order scheduling error texts from DD07T, domain TRMER. Spare Part Indicator A 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 Type An 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
270
System Condition System Condition descriptive attributes from T253M_T. Variance Category A 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 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
You can calculate the following variance categories on the output side:
PROFIT CENTER
Organizational 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-ofsales 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
A 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.
271
PRT
(Production Resource Tool) A moveable operating resource used in production or plant maintenance. PRT includes the following sub-classes: PRT Category Descriptive attributes from TCF03 of Production Resource/Tools categories PRT Grouping Key Production Resource/Tools grouping key descriptive attributes from TCF1 PRT Status Descriptive attributes for PRT status from TCF05
ROUTING
A 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 Operation Routing master data from PLPO. Routing Sequence Routing (Task List) sequence definition from PLFL Task List Type A 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 Usage Task List Usage descriptive attributes from TC23T.

Time related dimensions include relevant time dimensions, fiscal period dimensions, and Calendar dimensions. This class includes the
272
Time Dimensions Allow 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:
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 DIMENSIONS Fiscal 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 Dimensions Certain Rapid Marts carry calendars subject areas specific calendars. Included here are:
Factory Calendar Factory Calendar Period Work Calendar

273
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.
VENDOR
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 Category Work Center Category Attributes from TC30T. Work Center Formula Capacity formulas from TC25; parameters are parsed from the formula equation text.
274
INVALID HIERARCHIES
This 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
FILTERS
This 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
275
Profit Center Hierarchy Filters Project Element Filters Work Center Filters
Personnel Area Filters Personnel Subarea Filters Project Filters
TECHNIQUES
These are advanced technique objects developed for the Web Intelligence reports.
Master Data Universe Layout

Here is a graphical representation of the Master Data Universe as it appears in the universe designer:
276
Master Data Universe (1 of 3)
277
Master Data Universe (2 of 3):
278
Master Data Universe (2 of 3):
Universe Validation - Master Data

279
Integrity Check Results

These 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.
280
Universe Customizing the Universe
Customizing the Universe

The 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 Universe

In 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. 2. Create a copy of the SAP Plant Maintenance Universe with file name:
SAP-PM-Notifications.unv
In the Universe Parameters, Definition tab, change the name of the universe to:
3.
SAP Plant Maint - Notifications
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. Repeat previous step for
4.

5.
SERVICE_OPERATION_FACT SERVICE_CONFIRMATION_FACT SERVICE_COST_SUMMARY_FACT_HZ SERVICE_COST_SUMMARY_FACT_VR SERVICE_ORDER_FACT SERVICE_OPERATION_FACT SERVICE_CONFIRMATION_FACT SERVICE_COST_SUMMARY_FACT_HZ SERVICE_COST_SUMMARY_FACT_VR
Delete these tables from the graphic representation of the universe:

6.
All joins associated with these tables will be deleted as you delete the tables.
281
Universe Customizing the Universe
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. If the un-joined dimensions have associated hierarchy tables you should delete all associated hierarchy objects and empty top level classes as well. 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.
8.
9.
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
282
Installing the Rapid Mart
chapter
Installing the Rapid Mart Overview
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
284
Installing the Rapid Mart System Prerequisites
System Prerequisites
To 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 databases
If 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 higher
If you have questions about system prerequisites, contact SAP BusinessObjects Technical Support.
285
Installing the Rapid Mart Personnel Prerequisites
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 Universe Designer Web Intelligence Query Designer
BusinessObjects Enterprise
For additional support we recommend expertise in: SAP solutions Administration (BASIS) Target Database DBA (Database Administration)
286
Installing the Rapid Mart Rapid Mart product components
Rapid Mart product components

The 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.erwin
The 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
287
Installing the Rapid Mart Rapid Mart product components
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.
288
Installing the Rapid Mart Preparing your environment
Preparing your environment

Preparing Data Services
Follow 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 Environment

Prepare your target database environment.
Currently the Rapid Mart supports Oracle, MS SQL Server, Teradata, and DB2 as target databases.
289
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 Tuning
The 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
290
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.
291
Installing the Rapid Mart The Rapid Mart Package
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.
292
Installing the Rapid Mart Install the Rapid Mart Target Schema
Install the Rapid Mart Target Schema

This section deals with the installation of the Rapid Mart target schema.The schema installation is manual.
Create Target Schema

After 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 Teradata
Create 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 Tables

In the appropriate target database directory locate the files:
SAP_Create_Tables.sql SAP_Create_Comments.sql
As 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. 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.
2.
293
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. 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:
4.
COST_CENTER_HIER_HZ FUNCTIONAL_AREA_HIER_HZ GL_ACCOUNT_HIER_HZ PROFIT_CENTER_HIER_HZ PROJECT_ELEMENT_HIER_HZ
Create Target Indexes

Creating 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.sql
The 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 disk
You may want to modify the index creation scripts to include these parameters before execution.
294
Create Dummy Procedures

The 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.sql
Execute 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 Indexes

Use 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 Oracles 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
295
Installing the Rapid Mart Install the Data Services Job(s)
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.atl SAPPM_Rapid_Mart.atl
Example: The Plant Maintenance Rapid Mart ATL file is named:
Renaming the Data Stores

This 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 store
If 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
296
Before Replace All
297
After Replace All
Repeat these steps for the RM_DS data store Save 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 File

See 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.
298
From the Tools Menu choose Import From File:
Choose the ATL File
299
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 Stores

As 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:
300
Edit the Data Store:
301
Open Advanced Edit Window
302
Edit Data Store Settings.
Click OK to close Edit Window Click OK to Close Advanced Window The 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):
303
Edit the Data Store:
304
Open Advanced Edit Window
305
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 owner
Click OK to close Edit Window
306
Click OK to Close Advanced Window The 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 Files

All Rapid Marts come with an auxiliary file:
dates.dat
This 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.
307
All files in this directory must be moved to the working directory you specified when Adjusting the Data Stores, as shown below:
Using ABAP Files

Rapid 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 .aba
They 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.
308
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 solutions ...\ETL\Files\ABAP\ RF011F_NEW.aba RF011F_OLD.aba RF011P_NEW.aba RF011P_OLD.aba etc.
If used, these files are located in:
Some examples of the files found in the Cost Center and GL Rapid Marts are:
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.aba
If you are running SAP solutions version 5.0 or newer, choose the files in directory: ...\ETL\Files\ABAP\ABAP50 If you are running SAP solutions version 4.6, choose the files in directory: ...\ETL\Files\ABAP\ABAP46
309
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.
310
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 solutions
For the rest of Rapid Marts, you will not see Custom ABAP transforms in the Transforms tab.
311
2.
Then, change path to be the same as where the ABAP files are installed
3. 4. 5.
Repeat this step for all the other ABAP transforms in the Object Library Save the changes 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 \).
312
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.
313
Installing the Rapid Mart Installing Rapid Mart Reporting Content
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.biar
Note: 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 File

Use 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.
314
On the first screen, click Next:
315
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: ...\Visuals File: sappm_Rapid_Mart_Visuals.biar
316
Choose CMS:
317
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.
318
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.
319
Check Import Scenario Radio Buttons as shown
Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2
320
Incremental Import - Check or Uncheck Boxes:
321
Acknowledge Message, Click Next
322
Select All to import complete contents of BIAR file.
323
Universe & Connection Options- Check or Uncheck as shown
324
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.
325
Select Import Options for Publications:
Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2
326
Acknowledge message, Click Next:
327
Verify Correct List of Objects to Import, Click FINISH to start import:
328
Wait for Import to Finish. Then Click View Detail Log:
Click on each item imported. Make sure there are no errors:
329
Click Done to Exit the Import Wizard:
This completes the Import Wizard for Reporting Content.
Creating Universe Connection

Now use the Universe Designer to change the connection in the imported universe(s).
330
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:
331
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.
332
Using the Rapid Mart
chapter
Using the Rapid Mart Overview
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 framework
When 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 feature

With 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.
334
Using the Rapid Mart Recovery framework
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 framework

The Rapid Mart contains an external execution status table (AW_JOBEXECUTION) that tracks the status of a jobs 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 jobs 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.
335
Using the Rapid Mart Execution status framework
To maintain consistency with data flowing to SAP solutions, the Rapid Mart always overlaps one days 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 days 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 table

The Rapid Mart installation procedure creates a table named AW_JOBEXECUTION in the target database. The execution status table has four columns. Table column NAME Description 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. The status of this job after the last execution. Possible status values are: started, done, or none. Last attempted start date of data retrieval. This date is also the ending date of the last successful run of the job. Last attempted end date of data retrieval.
STATUS EXTRACTLOW EXTRACTHIGH
336
Using the Rapid Mart Execution status framework
How job status is maintained

The 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 jobs existing status. If the previous execution of the job did not complete successfullythat is, the job status is not donethe 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 jobs 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 jobs status to done. If the job does not complete successfully, the jobs status remains set to started. The EXTRACTLOW and EXTRACTHIGH dates remain set to the current values.
The execution status API

The 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.
337
Using the Rapid Mart Extraction, transformation and loading process
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 option

You 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 jobs 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:
338
Using the Rapid Mart Extraction, transformation and loading process
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 framework
Note: 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
339
Using the Rapid Mart Global Variables
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 Variables
All 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-Reference

A 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
340
The global variables in each of these sections are described in detail after the matrix. Global Variable Name Data Type
varchar(4) datetime int varchar(1) datetime varchar(1) datetime varchar(8) varchar(7) datetime varchar(1) varchar(10) datetime
AP AR CA GL HR
IA
PM PP PR PS SA
Used in all 11 Rapid Marts

$G_CCODE $G_DEFAULT_DATE $G_DEFAULT_NUMBER $G_DEFAULT_TEXT $G_EDATE $G_LANGUAGE $G_LOAD_DATE $G_LOAD_TIME $G_LOAD_TYPE $G_MAX_DATE $G_REBUILD_INDEXES $G_RUN_MODE $G_SDATE X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
Used in 2 to 10 Rapid Marts

$A $B $C $D $E $F $G $G_ABSOLUTE_START_DA TE $G_ENDFISCALYEAR $G_EXCHANGE_TYPE_ID $G_GLOBAL_CURRENCY $G_INT_ORDER_CATEG_P P $G_INT_ORDER_CATEG_P S $G_ORIG_SDATE $G_STARTFISCALYEAR int int int int int int int datetime int varchar(4) varchar(5) varchar(2) varchar(2) datetime int X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X
341
Global Variable Name
Data Type
varchar(1) datetime varchar(1) varchar(2) varchar(2) datetime varchar(2) varchar(1) varchar(10)
AP AR CA GL HR
IA
PM PP PR PS SA
Used in Only 1 Rapid Mart

$G_ADDRESS_VERSION $G_BUS_PARTN_SDATE $G_BUS_PARTNER $G_COST_OF_SALES_LED GER_ID $G_COUNTRY_GRP $G_DEL_PERIOD $G_DEL_REJECT_REASON $G_DROP_SHIP $G_GL_ACCOUNT_HIER_N AME X X X X X X X X X X X X X X X X X X X X X X X X X X X
$G_GL_SUM_PLAN_LEDGE varchar(2) R_ID $G_GL_VERSION $G_HIRE_ACTION_01 $G_HIRE_ACTION_02 $G_HIRE_ACTION_03 $G_INIT_HIST_CHG varchar(3) varchar(2) varchar(2) varchar(2) varchar(1)
$G_MALFUNCTION_CAUSE varchar(20) $G_MALFUNCTION_DAMAG varchar(20) E $G_MALFUNCTION_OBJ_P ART $G_MRP_RESULTS_DELET E varchar(20) varchar(1)
$G_ONTIME_DELIV_WINDO int W $G_PC_ACCOUNT_HIER_N AME $G_PROFIT_CENTER_LED GER_ID $G_REHIRE_ACTION_01 $G_REHIRE_ACTION_02 $G_RETIRE_ACTION $G_SAP_VERSION $G_SCHOOL_TYPE varchar(10) varchar(2) varchar(2) varchar(2) varchar(2) int varchar(2)
342
Global Variable Name
Data Type
AP AR CA GL HR
X X X X X
IA
PM PP PR PS SA
$G_SERVICE_INTERVAL_01 int $G_SERVICE_INTERVAL_02 int $G_SERVICE_INTERVAL_03 int $G_SERVICE_INTERVAL_04 int $G_SERVICE_INTERVAL_05 int $G_TABLE_EQUIPMENT varchar(20)
X X X X X X X X X X X X X X X X X X X X X X X X X X X
$G_TABLE_FUNCTL_LOCAT varchar(20) N $G_TASK_TYPE_PROBATIO varchar(2) N_END $G_TERMINATION_ACTION $G_VALID_DATE $G_WAGE_TYPE_01 $G_WAGE_TYPE_02 $G_WAGE_TYPE_03 $G_WAGE_TYPE_04 $G_WAGE_TYPE_05 $G_WAGE_TYPE_06 $G_WAGE_TYPE_07 $G_WAGE_TYPE_08 $G_WAGE_TYPE_09 $G_WAGE_TYPE_10 $G_WAGE_TYPE_11 $G_WAGE_TYPE_12 $G_WAGE_TYPE_13 $G_WAGE_TYPE_14 $G_WAGE_TYPE_15 $G_WAGE_TYPE_16 $G_WAGE_TYPE_17 $G_WAGE_TYPE_18 $G_WAGE_TYPE_19 $G_WAGE_TYPE_20 $G_WORKDAY_EDATE $G_WORKDAY_SDATE varchar(2) datetime varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) varchar(4) datetime datetime
343
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: datetime Default Value: 31-Dec-9999 The default date for missing dates.
$G_DEFAULT_NUMBER
Data Type: int Default Value: -1 Default 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: datetime Default Value: NULL The 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.
344
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: datetime Default Value: System Date and Time Always 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 Time Always 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:

$G_MAX_DATE
FIRST - for the initial or first load DELTA - for incremental or delta loads
Setting this variable to anything else will cause the job to fail.
Data Type: datetime Default Value: 31-Dec-9999 Used in date effective transforms to match SAP value for infinite date as end of validity period.
345
$G_REBUILD_INDEXES
Data Type: varchar(1) Default Value: N on Weekdays, Y on Weekends Legal values:
Y - Run rebuild indexes script N - Do not run rebuild indexes script
As 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: NULL Legal 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: datetime Default Value: 01-Jan-1990 The 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:
346
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: int Default Value: 30 Where Used:
SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions
1 of 4 configurable past time periods (in days) to use for aged receivables and payables and late payments.
$B
2 of 4 configurable past time periods (in days) to use for aged receivables and payables and late payments
$C
Data Type: int Default Value: 90
347
Where Used:
$D
$E
1 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)
$F
SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions
348
SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions
$G
$G_ABSOLUTE_START_DATE
Data Type: datetime Default Value: NULL Where Used:
SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions SAP BusinessObjects Accounts Receivable 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 Inventory Rapid Mart, version for SAP solutions
Earliest 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.
349
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_ENDFISCALYEAR
Data Type: int Default Value: NULL Where Used:
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 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 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_ID
Data Type: varchar(4) Default Value: M - Standard Translation at Average Rate Where Used:
350
SAP BusinessObjects Sales Rapid Mart, version for SAP solutions
Used for lookup of exchange rates to Global Currency
$G_GLOBAL_CURRENCY
Data Type: varchar(5) Default Value: USD - U.S. Dollar Where Used:
SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions SAP BusinessObjects Sales Rapid Mart, version for SAP solutions
Global 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_PP
Data 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 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 Production Orders (PP Rapid Mart) is 10 Note: 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_PS
Data Type: varchar(2) Default Value: 20 Where Used:
SAP BusinessObjects Production Planning Rapid Mart, version for SAP solutions
351
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 20 Note: 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_SDATE
Data Type: datetime Default Value: NULL Where Used:
SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions SAP BusinessObjects Accounts Receivable 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 Inventory Rapid Mart, version for SAP solutions
This 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_STARTFISCALYEAR
Data Type: int Default Value: NULL Where Used:
352
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_VERSION
Data Type: varchar(1) Default Value: A single space Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Used for Extraction of Central Address dimension from table ADRC. Default value is a single space.
$G_BUS_PARTN_SDATE
Data Type: datetime Default Value: System Date - 8 Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Used 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_PARTNER
Data Type: varchar(1) Default Value: Sunday = Yes, all other days = No
353
Actual ATL Language Code: ifthenelse(day_in_week(sysdate())=7,'Y','N') Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Used in Component Work Flow C_SalesOrderNumberDelta_SAP If 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_ID
Data Type: varchar(2) Default Value: 0L Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions In 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_GRP
Data Type: varchar(2) Default Value: 10 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Default Country Grouping Code for HR as determined in SAP solutions table T500L.
$G_DEL_PERIOD
Data Type: datetime Default Value: System Date - 180 Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Used 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_REASON
Data Type: varchar(2) Default Value: DD
354
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Identifier 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_SHIP
Data Type: varchar(1) Default Value: Y - Calculate backlog for third-party delivery Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Third-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). Qty Ordered - Qty Delivered (for all items).
When set to N (No) the Rapid Mart calculates backlog as:
$G_GL_ACCOUNT_HIER_NAME
Data Type: varchar(10) Default Value: @GL 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 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.
355
$G_GL_SUM_PLAN_LEDGER_ID
Data Type: varchar(2) Default Value: L6 Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions In 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_VERSION
Data Type: varchar(3) Default Value: (see below) Legal Values: OLD or NEW Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions Tells 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_01
Data Type: varchar(2) Default Value: 01 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Hiring Action Variable 01
$G_HIRE_ACTION_02
Data Type: varchar(2) Default Value: 90 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Hiring Action Variable 02
356
$G_HIRE_ACTION_03
Data Type: varchar(2) Default Value: K1 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Hiring Action Variable 03
$G_INIT_HIST_CHG
Data Type: varchar(1) Default Value: Z Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Used 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 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
If any other value, then
$G_MALFUNCTION_CAUSE
Data Type: varchar(20) Default Value: 5 Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions Catalog type to use for Malfunction Cause on Notifications. Choose your system notification catalog group type for Cause.
$G_MALFUNCTION_DAMAGE
Data Type: varchar(20) Default Value: C Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions
357
Catalog type to use for Malfunction Damage on Notifications. Choose your system notification catalog group type for Damage.
$G_MALFUNCTION_OBJ_PART
Data Type: varchar(20) Default Value: B Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions Catalog type to use for Malfunction Object Part on Notifications. Choose your system notification catalog group type for Object Part.
$G_MRP_RESULTS_DELETE
Data Type: varchar(1) Default Value: N Where Used: SAP BusinessObjects Production Planning Rapid Mart, version for SAP solutions Determines if MRP Results should be deleted before an Incremental Load.
Y = Delete before Incremental Load. N = No Delete before Incremental Load
$G_ONTIME_DELIV_WINDOW
Data Type: int Default Value: 15 days Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Used by On Time Delivery Section. Tells the system to limit On Time Delivery loads to a date range based on the Sales Schedule Lines 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_NAME
Data Type: varchar(10) Default Value: @PC Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions
358
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_ID
Data Type: varchar(2) Default Value: L5 Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions In 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_01
Data Type: varchar(2) Default Value: "JD" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Rehiring Action Variable 01
$G_REHIRE_ACTION_02
Data Type: varchar(2) Default Value: "N7" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Rehiring Action Variable 02
$G_RETIRE_ACTION
Data Type: varchar(2) Default Value: "ZP
359
Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Retirement Action
$G_SAP_VERSION
Data Type: int Default Value: System Determined - see below Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions Automatically 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_TYPE
Data Type: varchar(2) Default Value: "50" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions School Type
$G_SERVICE_INTERVAL_01
Data Type: INT Default Value: 6 (1/2 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.
Data Type: INT Default Value: 12 (1 year) Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions
360
One of 5 Intervals for determining Employee Length of Service. Values are in Months.
Data Type: INT Default Value: 36 (3 years) 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_TABLE_EQUIPMENT
Data Type: varchar(20) Default Value: EQUI Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions Initialize according to your system class type for Equipment master table name
$G_TABLE_FUNCTL_LOCATN
Data Type: varchar(20)
361
Default Value: IFLOT Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions Initialize according to your system class type for Functional Location master table name
$G_TASK_TYPE_PROBATION_END
Data Type: varchar(2) Default Value: 01 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Probation End Task Type
$G_TERMINATION_ACTION
Data Type: varchar(2) Default Value: 10 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Termination Action
$G_VALID_DATE
Data Type: datetime Default Value: System Date (without Time) Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutions This 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_01
Data Type: varchar(4) Default Value: "/101" Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions
362
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.
$G_WAGE_TYPE_02
Data Type: varchar(4) Default Value: "/110" 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_03
$G_WAGE_TYPE_04
$G_WAGE_TYPE_05
$G_WAGE_TYPE_06
Data Type: varchar(4)
363
Default Value: "/405" 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_07
$G_WAGE_TYPE_08
$G_WAGE_TYPE_09
$G_WAGE_TYPE_10
364
$G_WAGE_TYPE_11
$G_WAGE_TYPE_12
Data Type: varchar(4) Default Value: "/5U0" 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_13
Data Type: varchar(4) Default Value: "/5U1" 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_14
Data Type: varchar(4) Default Value: "MI10" 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_15
Data Type: varchar(4) Default Value: "/102"
365
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_16
Data Type: varchar(4) Default Value: "////" 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_17
$G_WAGE_TYPE_18
$G_WAGE_TYPE_19
366
$G_WAGE_TYPE_20
$G_WORKDAY_EDATE
Data Type: datetime Default Value: 01-Jan-1994 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions First date of date range to populated Working Days dimension
$G_WORKDAY_SDATE
Data Type: datetime Default Value: 31-Dec-2006 Where Used: SAP BusinessObjects Human Resources Rapid Mart, version for SAP solutions Last date of date range to populated Working Days dimension
Setting Global Variables

Job Properties
The 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).
367
Job Properties:
InitializeJob Script
The 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 Mart
Each 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.
368
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.
369
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.
370
Using the Rapid Mart Executing the job
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 job

Before 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 Load

1. 2. In the project area right-click in the Plant_Maintenance_Load job to access the Properties window. Edit the job Global Variable properties: a. b. c. Make sure that the value for the $G_LOAD_TYPE variable is set to FIRST. In either the Properties window, or the job initialization script, set the starting and ending dates for the initial load. 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. 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.
d.
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.
371
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. b. In the project area, right-click the job and choose Execute. Data Services opens the Execution Properties window. 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 Load

1. 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.
372
b.
Set the starting and ending time periods for the delta load. The standard setting is the yesterdays date for the starting date ($G_SDATE) and todays date for ending date ($G_EDATE). This assumes the Initial (First) load has already successfully loaded all data through yesterday. Set values for the rest of global variables as needed. Click OK to accept the set properties and to close the window.
c. d.
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. b. In the project area, right-click the job and choose Execute. Data Services opens the Execution Properties window. 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.
373
Using the Rapid Mart Customizing the Rapid Mart
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. Change column names to be more meaningful in your business environment. Remove columns or tables you do not need in your business environment. Add:
For example, to customize the Rapid Mart, you might:
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.
374
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.
375
376
Technical Implementation
chapter
Technical Implementation Overview
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 C_BusinessArea_SAP Description Dimensional component loading Business Area information from TGSB and TGSBT Tables BUSINESS_AREA
C_ClassificationHier_SAP
Object Classification hierarchies for CLASSIFICATION_HIER, Equipment and Functional Locations CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR
378
Technical Implementation Service Notification Section
Work Flow C_CompanyCode_SAP
Description Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Dimensional component loading Cost Center information from CSKS and CSKT Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS Combined Document Category Dimension Combined Document Type Dimension Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy Populate FUNCTIONAL_LOCATION master data dimension from IFLOT/ILOA and Functional Location Hierarchy
Tables COMPANY_CODE
C_ControllingArea_SAP
CONTROLLING_AREA
C_CostCenter_SAP
COST_CENTER
C_CostCenterHier_SAP
COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_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_HIER_BAD MAINTENANCE_PRIORITY
C_DocumentCategory_SAP C_DocumentType_SAP C_Equipment_SAP
C_FunctLocation_SAP
C_InternalOrder_SAP C_InternalOrderHier_SAP
Load INTERNAL_ORDER dimension Dimensional component loading Internal Order Hierarchy information from CCSS-AUFNR and AUFK Load MAINTENANCE_PRIORITY dimension from T356, T356T (for service orders and notifications)
C_MaintenancePriority_SAP
C_MalfunctionCatalog_SAP
Load 3 pre-defined notification cata- MALFUNCTION_CAUSE, log objects into MALFUNCTION_DAMAGE, MALFUNCTION_CAUSE MALFUNCTION_OBJ_PART MALFUNCTION_DAMAGE MALFUNCTION_OBJ_PART Load MALFUNCTION_EFFECT dimension from T357A_T MALFUNCTION_EFFECT
C_MalfunctionEffect_SAP C_Material_SAP
Dimensional component loading MATERIAL, consisting of a first and delta load for PRODUCT_HIERARCHY the materials table from MARA. Loads the sales product hierarchy table which is linked to the material
379
Work Flow C_MaterialByPlant_SAP
Description Dimensional component loading plant-specific material information such as procurement type and purchasing group from MARC / MARA Notification Dimension - Sourced from QMEL and QMIH in SAP. Load descriptive attributes from T024I - Planner group into PLANNING_GROUP dimension Dimensional component loading the plant table from T001W.
Tables MATERIAL_BY_PLANT
C_Notification_SAP C_PlanningGroup_SAP
NOTIFICATION PLANNING_GROUP
C_Plant_SAP C_PlantLocation_SAP C_ServicePerson_SAP
PLANT
Plant Location attributes from T499S PLANT_LOCATION - PLANT_LOCATION 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 TIME_DIM generated time periods with SAP fiscal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are used Populates Units of Measure dimen- UNIT_OF_MEASURE sion during first and delta loads from Table T006A in SAP Load WORK_CENTER master data dimension Work Center Hierarchical relationship in Horizontal and Vertical formats from CRHH/CRHS; load WORK_CENTER_HIER, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_HZ WORK_CENTER WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
C_UnitOfMeasure_SAP
C_WorkCenter_SAP C_WorkCenterHier_SAP
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.
380
Initial load
During the initial load, the section loads the NOTIFICATION_FACT table followed by the MTBR_MTTR_FACT.
NOTIFICATION_FACT
Any 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 Types
Table 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 & Time
These values are expressed in Days, Hours, and minutes.
MTBR_MTTR_FACT
Any existing data in MTBR_MTTR_FACT is deleted before the initial load starts. For the MTBR_MTTR_FACT table, the section calculates
381
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 Equipment
Data 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. Malfunction End Date (Previous Notification) is the Startup Date of the Object Malfunction Start Date (Next Notification) is global variable $G_LOAD_DATE Up Time = Malfunction End Date Previous Notification - Malfunction Start Date Current Notification Down Time = Malfunction End Date Current Notification - Malfunction Start Date Current Notification
If there is no next or previous notification,
The final step is to calculate the Up Time and Down Time:
382
Technical Implementation Service Order Section
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 load
Only the NOTIFICATION_FACT has an incremental load. We do a full (initial) load of MTBR_MTTR_FACT at all times.
NOTFICATION_FACT
No 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_FACT
The 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 Section

The 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.
383
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:
Object Classification hierarchies for CLASSIFICATION_HIER, Equipment and Functional Locations CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Dimensional component loading Cost Center information from CSKS and CSKT Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS COMPANY_CODE
C_CompanyCode_SAP
CONTROLLING_AREA
C_CostCenter_SAP
COST_CENTER
COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD
C_Currency_SAP
Dimensional component loading cur- CURRENCY rency abbreviations and texts from TCURT, TCURC Dimensional component loading CUSTOMER consisting of a first and delta load for the customer table from KNA1. Combined Document Category Dimension Combined Document Type Dimension Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy Dimensional component loading Functional Area information from TFKB and TFKBT Functional Area Hierarchy from GLFUNCT-RFAREA DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_AREA
C_Customer_SAP
C_FunctionalArea_SAP
C_FunctionalAreaHier_SAP
FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BA D,
384
Work Flow C_FunctLocation_SAP
Description Populate FUNCTIONAL_LOCATION master data dimension from IFLOT/ILOA and Functional Location Hierarchy
Tables 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_HIER_BAD INTERNAL_ORDER_STATUS MAINTENANCE_ACTIVITY_TYP E MAINTENANCE_PRIORITY
Load INTERNAL_ORDER dimension Dimensional component loading Internal Order Hierarchy information from CCSS-AUFNR and AUFK Internal orders status reference dimension from TKO04 Maintenance Activity Type attributes from T353I/T353I_T. Populate MAINTENANCE_ACTIVITY_TYPE Load MAINTENANCE_PRIORITY dimension from T356, T356T (for service orders and notifications)
C_InternalOrderStatus_SAP C_MaintenanceActivityType_SAP
C_Material_SAP
Dimensional component loading MATERIAL, consisting of a first and delta load for PRODUCT_HIERARCHY the materials table from MARA. Loads the sales product hierarchy table which is linked to the material Dimensional component loading plant-specific material information such as procurement type and purchasing group from MARC / MARA Notification Dimension - Sourced from QMEL and QMIH in SAP. Load descriptive attributes from T024I - Planner group into PLANNING_GROUP dimension Dimensional component loading the plant table from T001W. MATERIAL_BY_PLANT
C_MaterialByPlant_SAP
C_Notification_SAP C_PlanningGroup_SAP
NOTIFICATION PLANNING_GROUP
C_Plant_SAP C_PlantLocation_SAP C_ProfitCenter_SAP
PLANT
Plant Location attributes from T499S PLANT_LOCATION - PLANT_LOCATION Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (EC-PCA Profit center hierarchy in SAP) Dimensional component loading Project Element (WBS) master data PROFIT_CENTER
C_ProfitCenterHier_SAP
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT
C_ProjectElement_SAP
385
Work Flow C_ProjectElementHier_SAP
Description Dimensional component loading project element hierarchy information
Tables PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ , PROJECT_ELEMENT_HIER_VR , PROJECT_ELEMENT_HIER_BA D SERVICE_PERSON
C_ServicePerson_SAP
Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data System Condition descriptive attributes from T253M_T. Load SYSTEM_CONDITION dimension
C_SystemCondition_SAP
SYSTEM_CONDITION
C_TimeDim_SAP
Dimensional component loading TIME_DIM generated time periods with SAP fiscal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are used Load WORK_CENTER master data dimension Work Center Hierarchical relationship in Horizontal and Vertical formats from CRHH/CRHS; load WORK_CENTER_HIER, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_HZ WORK_CENTER WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact table load

After 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 Load
Any 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 orders AUFK.AUTYP = 30
Records are restricted to those with Order Category = 30
386
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 Load
No 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.
387
Technical Implementation Service Operation Section
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 load
First, 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:
Work Flow C_Activity_SAP Description Dimensional component loading Activity information from CSLA and CSLT Dimensional component loading Cost Activity Hierarchy information from CCSS-LSTAR and CSLA Dimensional component loading Business Area information from TGSB and TGSBT Chart of Accts (T004 and T004T) in SAP Tables ACTIVITY
C_ActivityHier_SAP
ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD BUSINESS_AREA
C_BusinessArea_SAP
C_ChartofAccts_SAP C_ClassificationHier_SAP
CHART_OF_ACCOUNTS
Object Classification hierarchies for CLASSIFICATION_HIER, Equipment and Functional Locations CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR Dimensional component loading Company Codes information from T001 Dimensional component loading control key information and descriptions from T430/T430T Dimensional component loading Controlling Area information from TKA01 Dimensional component loading Cost Center information from CSKS and CSKT Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS COMPANY_CODE
C_CompanyCode_SAP
C_ControlKey_SAP
CONTROL_KEY
CONTROLLING_AREA
C_CostCenter_SAP
COST_CENTER
388
Work Flow C_CostElement_SAP
Description Dimensional component loading Cost Element information from CSKA and CSKU Dimensional component loading Cost Element Hierarchy information from CCSS-KSTAR and CSK1
Tables COST_ELEMENT
C_CostElementHier_SAP
COST_ELEMENT_HIER, COST_ELEMENT_HIER_HZ, COST_ELEMENT_HIER_VR, COST_ELEMENT_HIER_BAD
C_Currency_SAP
Dimensional component loading cur- CURRENCY rency abbreviations and texts from TCURT, TCURC Dimensional component loading CUSTOMER consisting of a first and delta load for the customer table from KNA1. Combined Document Category Dimension Combined Document Type Dimension Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy Dimensional component loading Functional Area information from TFKB and TFKBT Functional Area Hierarchy from GLFUNCT-RFAREA DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_AREA
C_Customer_SAP
FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BA D, 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_HIER_BAD MAINTENANCE_ACTIVITY_TYP E MAINTENANCE_PRIORITY
C_FunctLocation_SAP
Populate FUNCTIONAL_LOCATION master data dimension from IFLOT/ILOA and Functional Location Hierarchy
Load INTERNAL_ORDER dimension Dimensional component loading Internal Order Hierarchy information from CCSS-AUFNR and AUFK Maintenance Activity Type attributes from T353I/T353I_T. Populate MAINTENANCE_ACTIVITY_TYPE Load MAINTENANCE_PRIORITY dimension from T356, T356T (for service orders and notifications)
C_MaintenanceActivityType_SAP
389
Work Flow C_Material_SAP
Description
Tables
Dimensional component loading MATERIAL, consisting of a first and delta load for PRODUCT_HIERARCHY the materials table from MARA. Loads the sales product hierarchy table which is linked to the material Dimensional component loading plant-specific material information such as procurement type and purchasing group from MARC / MARA Notification Dimension - Sourced from QMEL and QMIH in SAP. Dimensional component loading Object Class information from DD07T MATERIAL_BY_PLANT
C_Notification_SAP C_ObjectClass_SAP
NOTIFICATION OBJECT_CLASS
C_ObjectType_SAP
Dimensional component loading OBJECT_TYPE Object Type information from various modules -- This is a combined dimension. Load OPERATION_SUTABILITY from T423T Load descriptive attributes from T024I - Planner group into PLANNING_GROUP dimension Dimensional component loading the plant table from T001W. OPERATION_SUITABILITY PLANNING_GROUP
C_OperationSuitability_SAP C_PlanningGroup_SAP
PLANT
Plant Location attributes from T499S PLANT_LOCATION - PLANT_LOCATION Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (EC-PCA Profit center hierarchy in SAP) Dimensional component loading Project Element (WBS) master data Dimensional component loading project element hierarchy information PROFIT_CENTER
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ , PROJECT_ELEMENT_HIER_VR , PROJECT_ELEMENT_HIER_BA D SYSTEM_CONDITION
C_ProjectElement_SAP C_ProjectElementHier_SAP
System Condition descriptive attributes from T253M_T. Load SYSTEM_CONDITION dimension
390
Work Flow C_TimeDim_SAP
Description
Tables
Dimensional component loading TIME_DIM generated time periods with SAP fiscal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are used Populates Units of Measure dimen- UNIT_OF_MEASURE sion during first and delta loads from Table T006A in SAP Dimensional component loading VENDOR vendor and supplier contact information from LFA1 1 - Extracts Vendor and associated financial information by company from LFA1 and LFB1. Load WORK_CENTER master data dimension Work Center Hierarchical relationship in Horizontal and Vertical formats from CRHH/CRHS; load WORK_CENTER_HIER, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_HZ VENDOR_BY_COMPANY
C_UnitOfMeasure_SAP
C_Vendor_SAP
C_VendorByCompany_SAP
WORK_CENTER WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact table load

After 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 Load
Any 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 operation
Records are restricted to those with Order Category = 30
391
AUFK.AUTYP = 30
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 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 Load
No 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.
392
Technical Implementation Service Confirmation Section
Service Confirmation Section

The 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 load
First, 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:
Work Flow C_Activity_SAP Description Dimensional component loading Activity information from CSLA and CSLT Dimensional component loading Cost Activity Hierarchy information from CCSS-LSTAR and CSLA Dimensional component loading Business Area information from TGSB and TGSBT Tables ACTIVITY
C_ActivityHier_SAP
ACTIVITY_HIER, ACTIVITY_HIER_HZ, ACTIVITY_HIER_VR, ACTIVITY_HIER_BAD BUSINESS_AREA
C_BusinessArea_SAP
C_Capacity_SAP C_ClassificationHier_SAP
Capacity Master from KAKO/KAKT - CAPACITY CAPACITY dimension Object Classification hierarchies for CLASSIFICATION_HIER, Equipment and Functional Locations CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Dimensional component loading Cost Center information from CSKS and CSKT Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS COMPANY_CODE
C_CompanyCode_SAP
CONTROLLING_AREA
C_CostCenter_SAP
COST_CENTER
C_Currency_SAP
Dimensional component loading cur- CURRENCY rency abbreviations and texts from TCURT, TCURC
393
Work Flow C_Customer_SAP
Description
Tables
Dimensional component loading CUSTOMER consisting of a first and delta load for the customer table from KNA1. Combined Document Category Dimension Combined Document Type Dimension Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy Dimensional component loading Functional Area information from TFKB and TFKBT Functional Area Hierarchy from GLFUNCT-RFAREA DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_AREA
FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BA D, 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_HIER_BAD INTERNAL_ORDER_STATUS MAINTENANCE_ACTIVITY_TYP E MAINTENANCE_PRIORITY
C_FunctLocation_SAP
Load INTERNAL_ORDER dimension Dimensional component loading Internal Order Hierarchy information from CCSS-AUFNR and AUFK Internal orders status reference dimension from TKO04 Maintenance Activity Type attributes from T353I/T353I_T. Populate MAINTENANCE_ACTIVITY_TYPE Load MAINTENANCE_PRIORITY dimension from T356, T356T (for service orders and notifications)
C_InternalOrderStatus_SAP C_MaintenanceActivityType_SAP
C_Material_SAP
Dimensional component loading MATERIAL, consisting of a first and delta load for PRODUCT_HIERARCHY the materials table from MARA. Loads the sales product hierarchy table which is linked to the material Dimensional component loading plant-specific material information such as procurement type and purchasing group from MARC / MARA MATERIAL_BY_PLANT
394
Work Flow C_Notification_SAP C_OperationSuitability_SAP C_PlanningGroup_SAP
Description Notification Dimension - Sourced from QMEL and QMIH in SAP. Load OPERATION_SUTABILITY from T423T Load descriptive attributes from T024I - Planner group into PLANNING_GROUP dimension Dimensional component loading the plant table from T001W.
Tables NOTIFICATION OPERATION_SUITABILITY PLANNING_GROUP
PLANT
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ , PROJECT_ELEMENT_HIER_VR , PROJECT_ELEMENT_HIER_BA D SERVICE_PERSON
C_ServicePerson_SAP
Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data System Condition descriptive attributes from T253M_T. Load SYSTEM_CONDITION dimension
SYSTEM_CONDITION
C_TimeDim_SAP
Dimensional component loading TIME_DIM generated time periods with SAP fiscal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are used Populates Units of Measure dimen- UNIT_OF_MEASURE sion during first and delta loads from Table T006A in SAP
C_UnitOfMeasure_SAP
395
Work Flow C_WorkCenter_SAP C_WorkCenterHier_SAP
Description Load WORK_CENTER master data dimension Work Center Hierarchical relationship in Horizontal and Vertical formats from CRHH/CRHS; load WORK_CENTER_HIER, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_HZ
Tables WORK_CENTER WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact table load

After 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 Load
Any 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 confirmations AUFK.AUTYP = 30
Records are restricted to those with Order Category = 30 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 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
396
Technical Implementation Service Order Cost Section
Forecast End Date - Execution Start Date
Incremental Load
No 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 Section

The 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 load
First, 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.
Work Flow C_BusinessActivity_SAP Description FK-SL Activity attributes from T022/T022T. Load BUSINESS_ACTIVITY dimension Dimensional component loading Business Area information from TGSB and TGSBT Tables BUSINESS_ACTIVITY
C_BusinessArea_SAP
BUSINESS_AREA
Object Classification hierarchies for CLASSIFICATION_HIER, Equipment and Functional Locations CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR Dimensional component loading Company Codes information from T001 COMPANY_CODE
C_CompanyCode_SAP
397
Work Flow C_ControllingArea_SAP
Description Dimensional component loading Controlling Area information from TKA01 Dimensional component loading Cost Center information from CSKS and CSKT Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS
Tables CONTROLLING_AREA
C_CostCenter_SAP
COST_CENTER
C_Currency_SAP
Dimensional component loading cur- CURRENCY rency abbreviations and texts from TCURT, TCURC Combined Document Category Dimension Combined Document Type Dimension Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR
C_FinRecordCategory_SAP
Descriptive attributes for Accounting FINANCIAL_RECORD_CATEGO Summary table Value Category from RY TPIR1T. Load FINANCIAL_RECORD_CATEGORY dimension Loads Special Ledger Record Types FINANCIAL_RECORD_TYPE dimension (Domain RRCTY) from table DD07T and Cost/Plant Maintenance value types from CO_WRTTP domain of DD07T table FINANCIAL_RECORD_ Dimensional component loading Fis- FISC_PERIOD, cal Year / Fiscal Period data FISC_PERIOD_STAGE Dimensional component loading Functional Area information from TFKB and TFKBT Functional Area Hierarchy from GLFUNCT-RFAREA FUNCTIONAL_AREA
C_FinRecordType_SAP
C_FiscalPeriod_SAP C_FunctionalArea_SAP
FUNCTIONAL_AREA_HIER, FUNCTIONAL_AREA_HIER_HZ, FUNCTIONAL_AREA_HIER_VR, FUNCTIONAL_AREA_HIER_BA D, FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER , FUNCTIONAL_LOCATION_HIER _HZ, FUNCTIONAL_LOCATION_HIER _VR
C_FunctLocation_SAP
398
Work Flow C_InternalOrder_SAP C_InternalOrderHier_SAP
Description Load INTERNAL_ORDER dimension Dimensional component loading Internal Order Hierarchy information from CCSS-AUFNR and AUFK Maintenance Activity Type attributes from T353I/T353I_T. Populate MAINTENANCE_ACTIVITY_TYPE Load MAINTENANCE_PRIORITY dimension from T356, T356T (for service orders and notifications)
Tables INTERNAL_ORDER INTERNAL_ORDER_HIER, INTERNAL_ORDER_HIER_HZ, INTERNAL_ORDER_HIER_VR, INTERNAL_ORDER_HIER_BAD MAINTENANCE_ACTIVITY_TYP E MAINTENANCE_PRIORITY
C_MaintenanceActivityType_SAP
C_Material_SAP
Dimensional component loading MATERIAL, consisting of a first and delta load for PRODUCT_HIERARCHY the materials table from MARA. Loads the sales product hierarchy table which is linked to the material Dimensional component loading plant-specific material information such as procurement type and purchasing group from MARC / MARA Dimensional component loading the plant table from T001W. MATERIAL_BY_PLANT
PLANT
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR, PROFIT_CENTER_HIER_BAD PROJECT_ELEMENT PROJECT_ELEMENT_HIER, PROJECT_ELEMENT_HIER_HZ , PROJECT_ELEMENT_HIER_VR , PROJECT_ELEMENT_HIER_BA D SYSTEM_CONDITION
System Condition descriptive attributes from T253M_T. Load SYSTEM_CONDITION dimension
C_VarianceCategory_SAP
Financial Variance Category descrip- VARIANCE_CATEGORY tive attributes (ABKAT domain from DD07T). Load VARIANCE_CATEGORY dimension
399
Work Flow C_WorkCenter_SAP C_WorkCenterHier_SAP
Description Load WORK_CENTER master data dimension Work Center Hierarchical relationship in Horizontal and Vertical formats from CRHH/CRHS; load WORK_CENTER_HIER, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_HZ
Tables WORK_CENTER WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD
Fact table load

After 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.
400
Technical Implementation Service Master Section
Service Master Section

The 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 load
First, 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.
Object Classification hierarchies for CLASSIFICATION_HIER, Equipment and Functional Locations CLASSIFICATION_HIER_HZ, CLASSIFICATION_HIER_VR Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Dimensional component loading Cost Center information from CSKS and CSKT Dimensional component loading Cost Center Hierarchy information from CCSS-KOSTL and CSKS Populate EQUIPMENT dimension with equipment master data from EQUI/EQUIZ/ILOA. Also loads Equipment Hierarchy Populate FUNCTIONAL_LOCATION master data dimension from IFLOT/ILOA and Functional Location Hierarchy COMPANY_CODE
C_CompanyCode_SAP
CONTROLLING_AREA
C_CostCenter_SAP
COST_CENTER
COST_CENTER_HIER, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR, COST_CENTER_HIER_BAD EQUIPMENT, EQUIPMENT_HIER, EQUIPMENT_HIER_HZ, EQUIPMENT_HIER_VR FUNCTIONAL_LOCATION, FUNCTIONAL_LOCATION_HIER , FUNCTIONAL_LOCATION_HIER _HZ, FUNCTIONAL_LOCATION_HIER _VR
C_Equipment_SAP
C_FunctLocation_SAP
401
Work Flow C_Material_SAP
Description
Tables
Dimensional component loading MATERIAL, consisting of a first and delta load for PRODUCT_HIERARCHY the materials table from MARA. Loads the sales product hierarchy table which is linked to the material Dimensional component loading plant-specific material information such as procurement type and purchasing group from MARC / MARA Load descriptive attributes from T024I - Planner group into PLANNING_GROUP dimension Dimensional component loading the plant table from T001W. MATERIAL_BY_PLANT
C_PlanningGroup_SAP
PLANNING_GROUP
C_Plant_SAP C_PlantLocation_SAP C_ServicePerson_SAP
PLANT
Plant Location attributes from T499S PLANT_LOCATION - PLANT_LOCATION 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 TIME_DIM generated time periods with SAP fiscal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are used Populates Units of Measure dimen- UNIT_OF_MEASURE sion during first and delta loads from Table T006A in SAP Dimensional component loading VENDOR vendor and supplier contact information from LFA1 1 - Extracts Vendor and associated financial information by company from LFA1 and LFB1. VENDOR_BY_COMPANY
C_UnitOfMeasure_SAP
C_Vendor_SAP
C_VendorByCompany_SAP
Background
The 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
402
Prerequisite dimension loads: Functional Location
Each of the two fact table work flows starts by loading the prerequisite dimensions listed above.
Characteristics Stage Table

Then, 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 Types
The 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.
Global Variable Default Description TCLA.OTAB Value EQUI IFLOT Defines value for Equipment Characteristics Defines value for Functional Location Characteristics
$G_TABLE_EQUIPMENT $G_TABLE_FUNCTL_LOCATN
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

Initial Load
Any 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 =
403
$G_TABLE_EQUIPMENT and CHARACTERISTIC_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 Load
The 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.

Initial Load
Any 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 and CHARACTERISTIC_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 Load
The 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
404
Technical Implementation Dimensions with Incremental Loads
Characteristics for any functional Location refreshed in the current load job will be selected.
Dimensions with Incremental Loads

Most 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.
Equipment
The 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 Steps

1. 2. Delete any data in the EQUIPMENT.dat table Read SAP solutions table EQUI, select Equipment IDs (EQUI.EQUNR) for all equipment created or changed in the date range defined by global variables $G_SDATE and $G_EDATE. Add the Equipment IDs to table EQUIPMENT.dat Read SAP solutions table EQUZ, select Equipment IDs (EQUI.EQUNR) for all equipment created or changed in the date range defined by global variables $G_SDATE and $G_EDATE. Add the Equipment IDs to table EQUIPMENT.dat The result is that EQUIPMENT.dat contains a list of Equipment IDs 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 IDs (to eliminate duplicates) from EQUIPMENT.dat and join this to EQUI and EQUZ to extract required equipment attributes. Use Table Comparison transform to update or add records in the EQUIPMENT table on the target database.
3.
4.
6.
405
Technical Implementation Rolling Totals Calculation
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 Steps

1. 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. Use Table Comparison transform to update or add records in the FUNCTIONAL_LOCATION table on the target database.
2.
Rolling Totals Calculation

Vertical 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: Rapid Mart Accts. Payable Cost General Ledger General Ledger General Ledger Vertical Summary Table VENDOR_SUMMARY_FACT_VR COST_SUMMARY_FACT_VR COST_OF_SALES_SUMMARY_FACT_VR GL_SUMMARY_FACT_VR LEDGER_SUMMARY_FACT_VR
Accts. Receivable CUSTOMER_SUMMARY_FACT_VR
General Ledger & PROFIT_CENTER_SUMMARY_FACT_VR Cost Plant Maint. Project Systems SERVICE_COST_SUMMARY_FACT_VR PROJECT_COST_SUMMARY_FACT_VR
To implement Rolling Totals we use a custom function
RM_RollingSummary_Calculation.
406
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...
407
PTDBALQuery - 1. Calculate PTD Values:
PTD values are calculated by subtracting Credits from Debits.
408
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.
409
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.
410
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
411
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:
412
They are defined as Parameters at the Data Flow level:
413
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.
414
An example of the output generated by this type of data flow and the Rolling Totals Function are shown below.
415
Technical Implementation Optimization Techniques
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 below However, 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 Partitions
Summary 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 partitions Each 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:
416
SYSIBM.SYSDATAPARTITIONS
in 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 Accts. Payable Subject Area Tables 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 COST_OF_SALES_SUMMARY_FACT_HZ, COST_OF_SALES_SUMMARY_FACT_VR, COST_OF_SALES_SUMMARY_STAGE_VR GL_SUMMARY_FACT_HZ, GL_SUMMARY_FACT_VR, GL_SUMMARY_STAGE_VR LEDGER_SUMMARY_FACT_HZ, LEDGER_SUMMARY_FACT_VR, LEDGER_SUMMARY_STAGE_VR PROFIT_CENTER_SUMMARY_FACT_HZ, PROFIT_CENTER_SUMMARY_FACT_VR, PROFIT_CENTER_SUMMARY_STAGE_VR SERVICE_COST_SUMMARY_FACT_HZ, SERVICE_COST_SUMMARY_FACT_VR, SERVICE_COST_SUMMARY_STAGE_VR PROJECT_COST_SUMMARY_FACT_HZ, PROJECT_COST_SUMMARY_FACT_VR, PROJECT_COST_SUMMARY_STAGE_VR
General Ledger
General Ledger
General Ledger
General Ledger
Plant Maint.
Projects
417
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 Transforms Circled in RED.
418
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 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. 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
Within the Ordering Query:
Within the Reverse-Pivot:
Hierarchy Optimizations
We 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:
419
Before Split (Single Data Flow):
After Split 1 of 2 Data Flows (Horizontal):
420
After Split 2 of 2 Data Flows (Vertical):
The 2 Split Data Flows in Context.
421
Technical Implementation Dealing with NULL values
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.
422
Technical Implementation Fact Table Stored Procedures
Fact Table Stored Procedures

When 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.
423
Technical Implementation Fiscal Periods & Time Dim Load
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
424
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.
425
426
Documentation References
chapter
Documentation References Data Services Documentation References
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 References

From 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 Data Services Supplement for SAP Data Services Tutorial Data Services Designer Guide Data Services Reference Guide Data Services Advanced Development Guide Data Services Performance Optimization Guide
Configuring Data Services for SAP solutions and security considerations: Extending/customizing Rapid Marts ETL:
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 Guide Administration Guide Deployment and Configuration Guide
Configuring BusinessObjects Enterprise and security considerations:
428
Documentation References BusinessObjects Enterprise Documentation References
Administrators Reference Guide Recommended Settings Guide Import Wizard Guide InfoView User Guide Designers 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)
Extending/customizing Rapid Marts Reporting Content:
429
Documentation References BusinessObjects Enterprise Documentation References
430
Rapid Mart Data Schema
appendix
Appendix Table Summary

This appendix provides detailed information about the tables and views in the SAP BusinessObjects Plant Maintenance Rapid 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
Appendix Table 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 Rapid Mart Data Schema 2
Appendix Table 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
Appendix Table Column Details
ACTIVITY
Activity Master (CSLA, CSLT)
# Column Name Key Column Desc Column Datatype Dtype Length Precision Scale Is Nullable
ACTIVITY_DESCR
CSLT-LTEXT-Description
NVARCSTR
40
yes
ACTIVITY_FULL_NAM E
Activity ID and Description
NVARCSTR
120
yes
ACTIVITY_ID
PK
CSLA-LSTAR-Activity type
NVARCSTR
no
ACTIVITY_NAME
CSLT-KTEXT-Name
NVARCSTR
20
yes
ACTIVITY_TYPE_CAT EG_CODE ALLOCTN_COST_ELE M_ID
CSLA-LATYPE-Activity type category
NVARCSTR
yes
CSLA-VKSTA-Allocation cost element
NVARCSTR
10
yes
CREATED_BY
CSLA-USNAM-Created by
NVARCSTR
12
yes
CREATE_DATE
CSLA-ERSDA-Created on
DATETIME
24
yes
CTRL_AREA_ID
PK
CSLA-KOKRS-Controlling area
NVARCSTR
no
10
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS)
24
yes
11
LOAD_TIME
NVARCSTR
yes
12
OUTPUT_FACTOR
CSLA-AUSFK-Output factor
DECIMAL
48
yes
13
UOM_ID
CSLA-LEINH-Activity unit
NVARCSTR
yes
14
UOM_ID_OUTPUT
CSLA-AUSEH-Output unit
NVARCSTR
yes
15
VALID_FROM_DATE
CSLA-DATAB-Date valid from
DATETIME
24
yes
16
VALID_TO_DATE
CSLA-DATBI-Valid to date
DATETIME
24
yes
ACTIVITY_HIER
Activity Hierarchy information - CCSS-LSTAR -- Note Does NOT Have a Primary Key due to duplication possible in SAP
CHILD_DESCR
CCSS-LSTAR-Activity Hierarchy Child ID Description
NVARCSTR
64
yes
CHILD_ID
PK
CCSS-LSTAR-Child Activity ID
NVARCSTR
12
no
CTRL_AREA_ID
PK
CCSS-LSTAR-Controling Area
NVARCSTR
no
LEAF_FLAG
PK
CCSS-LSTAR-Indicates if the Child ID doesn't have any subordinate leaves
NVARCSTR
no
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) CCSS-LSTAR-Activity Hierarchy Parent ID Description
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
NVARCSTR
64
yes
PARENT_ID
PK
CCSS-LSTAR-Parent Activity ID
NVARCSTR
12
no
ROOT_FLAG
PK
CCSS-LSTAR-Indicates if the Parent ID is a root of an activity group hierarchy
NVARCSTR
no
ACTIVITY_HIER_BAD
CCSS-LSTAR Activity Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
CCSS-LSTAR-Activity Hierarchy Child ID Description
NVARCSTR
64
yes
CHILD_ID
PK
CCSS-LSTAR-Child Activity ID
NVARCSTR
12
no
CTRL_AREA_ID
PK
NVARCSTR
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
yes
ETL_ERROR_COLU MN
Data Integrator Error message
NVARCSTR
500
yes
LEAF_FLAG
PK
CCSS-LSTAR-Indicates if the Child ID doesn't have any subordinate leaves
NVARCSTR
no
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) CCSS-LSTAR-Activity Hierarchy Parent ID Description
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
NVARCSTR
64
yes
10
PARENT_ID
PK
CCSS-LSTAR-Parent Activity ID
NVARCSTR
12
no
11
ROOT_FLAG
PK
NVARCSTR
no
ACTIVITY_HIER_HZ
Activity Hierarchy Horizontal Flattening - CCSS-LSTAR -- Cannot have a primary key due to duplication of entries possible in SAP
ACTIVITY_ID
PK
CCSS-LSTAR-Leaf of the Activity Group Hierarchy
NVARCSTR
12
no
CTRL_AREA_ID
PK
NVARCSTR
no
LEAF_LVL
CCSS-LSTAR-Depth of the leaf from the parent
INTEGER
no
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) CCSS-LSTAR-Activity Hierarchy Level_0_ID Description
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
NVARCSTR
64
yes
LVL_00_FULL_NAME
Activity ID and Descripiton for Root
NVARCSTR
120
yes
LVL_00_ID
PK
CCSS-LSTAR-Root of the Activity Group Hierarchy CCSS-LSTAR-Activity Hierarchy Level_1_ID Description
NVARCSTR
12
no
LVL_01_DESCR
NVARCSTR
64
yes
10
LVL_01_FULL_NAME
Activity ID and Descripiton for Level 1
NVARCSTR
120
yes
11
LVL_01_ID
PK
CCSS-LSTAR-A group or a Activity ID. It is null when the hierarchy ended with a lower NVARCSTR numbered node. CCSS-LSTAR-Activity Hierarchy Level_2_ID Description NVARCSTR
12
no
12
LVL_02_DESCR
64
yes
13
LVL_02_FULL_NAME
Activity ID and Descripiton for level 2
NVARCSTR
120
yes
14
LVL_02_ID
PK
12
no
15
LVL_03_DESCR
64
yes
16
LVL_03_FULL_NAME
Activity ID and Description for Level 3
NVARCSTR
120
yes
Appendix Table Column Details CCSS-LSTAR-A group or a Activity ID. It is null when the hierarchy ended with a lower NVARCSTR numbered node. CCSS-LSTAR-Activity Hierarchy Level_4_ID Description NVARCSTR
17
LVL_03_ID
PK
12
no
18
LVL_04_DESCR
64
yes
19
LVL_04_FULL_NAME
NVARCSTR
120
yes
20
LVL_04_ID
PK
12
no
21
LVL_05_DESCR
64
yes
22
LVL_05_FULL_NAME
NVARCSTR
120
yes
23
LVL_05_ID
PK
12
no
24
LVL_06_DESCR
64
yes
25
LVL_06_FULL_NAME
NVARCSTR
120
yes
26
LVL_06_ID
PK
12
no
27
LVL_07_DESCR
64
yes
28
LVL_07_FULL_NAME
Activity ID and Description for level 7
NVARCSTR
120
yes
29
LVL_07_ID
PK
CCSS-LSTAR-A group or a Activity ID. It is null when the hierarchy ended with a lower NVARCSTR numbered node.
12
no
ACTIVITY_HIER_VR
Activity Hierarchy Vertical Flattening - CCSS-LSTAR - cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
CCSS-LSTAR-Description of the descendant
NVARCSTR
64
yes
CHILD_FULL_NAME
Child Activity ID and Description
NVARCSTR
120
yes
CHILD_ID
PK
CCSS-LSTAR-Activity Hierarchy Child ID
NVARCSTR
12
no
CTRL_AREA_ID
PK
NVARCSTR
no
DEPTH
CCSS-LSTAR-Depth of the descendant from the ancestor CCSS-LSTAR-Indicates if the Parent ID is a leaf of an activity group hierarchy
INTEGER
yes
LEAF_FLAG
INTEGER
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
CCSS-LSTAR-Description of the ancestor
NVARCSTR
64
yes
10
PARENT_FULL_NAME
Parent Activity ID and Description
NVARCSTR
120
yes
11
PARENT_ID
PK
CCSS-LSTAR-Activity Hierarchy Parent ID
NVARCSTR
12
no
12
ROOT_FLAG
INTEGER
yes
AW_DIMENSION_SOURCE
Master list of values indicating sources of combined dimensions
DIM_SRC_DESCR
Description of Dimension Source Dimension Source. Used in combined dimension combining similar attributes from different sources in SAP.
NVARCSTR
60
yes
DIM_SRC_ID
PK
NVARCSTR
30
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.
JOB_END_DATE
$G_EDATE global variable setting at the time of the "First" or "Delta" run.
DATETIME
24
yes
JOB_LOAD_TYPE
PK
Will be FIRST or DELTA
NVARCSTR
10
no
JOB_NAME
PK
Name of the Rapid Mart Load Job.
NVARCSTR
100
no
JOB_START_DATE
$G_SDATE global variable setting at the time of the "First" or "Delta" run.
DATETIME
24
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
AW_JOBEXECUTION
Job Execution Status table
EXTRACTHIGH
End Date
NVARCSTR
10
yes
EXTRACTLOW
Start Date
NVARCSTR
10
yes
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart
24
yes
NAME
PK
Job Name
NVARCSTR
64
no
STATUS
Job Status
NVARCSTR
12
yes
AW_LOOKUP_INDEX
Auxilary table to store index information
ADDTNL_TXT
Notes
NVARCSTR
64
yes
COLUMN_NAME_01
Index column 1
NVARCSTR
64
yes
COLUMN_NAME_02
Index column 2
NVARCSTR
64
yes
COLUMN_NAME_03
Index column 3
NVARCSTR
64
yes
INDEX_NAME
Index Name
NVARCSTR
64
yes
LOAD_DATE
Load date in Rapid mart
DATETIME
24
yes
LOAD_TIME
Load time in Rapid mart
NVARCSTR
yes
TBL_NAME
Table name the index belong to
NVARCSTR
64
yes
BUSINESS_ACTIVITY
FK-SL Activity attributes from T022/T022T
BUS_ACTIVITY_DESC R
T022T.TXT -Text (30 Characters)
NVARCSTR
30
yes
BUS_ACTIVITY_ID
PK
T022.ACTIVITY -FI-SL Business Transaction
NVARCSTR
no
BUS_ACTIVITY_TYPE _DESCR BUS_ACTIVITY_TYPE _ID
lookup on VORGTYP domain in DD07T
NVARCSTR
60
yes
T022.VORGTYP -Activity type for FI-SL activities
NVARCSTR
yes
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
yes
LOAD_TIME
Time Loaded into Rapid mart
NVARCSTR
yes
RECORD_TYPE_DE SCR
lookup on RRCTY domain in DD07T
NVARCSTR
60
yes
RECORD_TYPE_ID
T022.SATZTYP -Record Type
NVARCSTR
yes
BUSINESS_AREA
Business Areas - TGSB, TSGBT
BUS_AREA_DESCR
TGSBT-GTEXT-Business area description
NVARCSTR
30
yes
BUS_AREA_FULL_NA ME
Business Area ID and Descritpion
NVARCSTR
120
yes
BUS_AREA_ID
PK
TGSB-GSBER-Business area
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
CAPACITY
Capacity master data from KAKO/KAKT
CALENDAR_DESCR
TFACT.LTEXT - Factory Calendar descritpion NVARCSTR
60
yes
CALENDAR_ID
KAKO.KALID - Factory calendar ID
NVARCSTR
yes
CAPACITY_CATEG_D ESCR
TC26T- TXT -Lookup capacity category description
NVARCSTR
20
yes
CAPACITY_CATEG_ID
KAKO.KAPAR - Capacity category
NVARCSTR
yes
CAPACITY_DESCR
Lookup description of capacity ID
NVARCSTR
40
yes
CAPACITY_FULL_NA ME
KAKO.NAME - Capacity name
NVARCSTR
55
yes
CAPACITY_ID
PK
KAKO.KAPID - Capacity ID
NVARCSTR
20
no
CAPACITY_NAME
KAKO.NAME - Capacity name
NVARCSTR
yes
CAPACITY_VERSION_ NUM
KAKO.VERSA - Active version of available capacity
NVARCSTR
yes
10
CMPNY_CODE_ID
T001K -BUKRS -Company Code ID
NVARCSTR
yes
11
CMPNY_CODE_NAME
Lookup on Company Code Name
NVARCSTR
25
yes
12
FINITE_SCHED_FLAG
KAKO.KAPTER - Indicator: Capacity relevant to finite scheduling
INTEGER
yes
13
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
yes
14
LOAD_TIME
Time when the record was loaded
NVARCSTR
yes
15
MULTIPLE_USE_FLAG
KOKO.KAPAVO - Indicator: Several operations can use capacity
INTEGER
yes
16
PLANNG_GRP_ID
KAKO.PLANR - Capacity planner group
NVARCSTR
yes
10
Appendix Table Column Details T024i-INNAM - Name of the maintenance planning group
17
PLANNG_GRP_NAME
NVARCSTR
18
yes
18
PLANT_ID
KAKO.WERKS - Plant
NVARCSTR
yes
19
PLANT_NAME
T001W.NAME1 Name - Lookup on Plant name for Planning Plant
NVARCSTR
30
yes
20
POOL_CAPACITY_FL AG PRCNT_OVERLOAD _RATE PRCNT_UTILIZATION_ RATE QTY_INDIVID_CAPACI TY SECS_CAPACITY_EN D SECS_CAPACITY_PA USE SECS_CAPACITY_ST ART SHORT_TERM_PLAN_ FLAG
KAKO.POOLK - Indicator for pooled capacity
INTEGER
yes
21
KAKO.UEBERLAST - Percent Overload
NVARCSTR
yes
22
KAKO.NGRAD - Capacity utilization rate (percent) KAKO.AZNOR - Number of individual capacities KAKO.ENDZT - Finish time in seconds (internal) KAKO.PAUSE - Cumulative break time in seconds (internal) KAKO.BEGZT - Start time in seconds (internal)
INTEGER
yes
23
DECIMAL
48
28
yes
24
DECIMAL
48
28
yes
25
DECIMAL
48
28
yes
26
DECIMAL
48
28
yes
27
KAKO.KAPLPL - Indicator: Capacity excluded INTEGER from long-term planning KAKO.MEINS - Base unit of measure for capacity
yes
28
UOM_ID_BASE
NVARCSTR
yes
29
VALUATN_AREA_ID
T001K.BWKEY -Valuation Area
NVARCSTR
yes
11
CHARACTERISTIC_STAGE
Staging of characteristics master data fro AUSP/CABN for Equipment and Funcational location
CHARACTSTC_DES CR CHARACTSTC_FOR MAT CHARACTSTC_HEA DNG_01 CHARACTSTC_HEA DNG_02
CABNT-ATBEZ(lookup) - Characteristic description
NVARCSTR
30
yes
CABN-ATFOR - Characteristic data type
NVARCSTR
yes
CABNT-ATUE1 (lookup) - First heading line
NVARCSTR
30
yes
CABNT-ATUE2 (lookup) - Second heading line NVARCSTR
30
yes
CHARACTSTC_ID
PK
AUSP-ATINN - Internal characteristic
NVARCSTR
10
no
CHARACTSTC_NAME
CABN-ATNAM (lookup) - Characteristic unique NVARCSTR name
30
yes
CHARACTSTC_VALUE
AUSP-ATWRT- Characteristic value
NVARCSTR
30
yes
CLASS_TYPE_ID
PK
AUSP-KLART - Characteristic Class type
NVARCSTR
no
LOAD_DATE
Date and Time Loaded into Rapid Mart
DATETIME
24
yes
10
LOAD_TIME
Time Loaded into Rapid Mart
NVARCSTR
yes
11
OBJ_ID
PK
AUSP-OBJEK - Object number
NVARCSTR
50
no
12
OBJ_TABLE_NAME
TCLA.OBTAB - Name of database table for object
NVARCSTR
10
yes
13
UOM_ID_VALUE
CABN--MSEHI - Unit of measurement
NVARCSTR
yes
14
VALID_FROM_DATE
AUSP.ATFLV - Derived Date from and Time From bucket
DATETIME
24
yes
15
VALID_FROM_NUMBE R
AUSP.ATFLV - Derived Number From bucket
DECIMAL
48
28
10
yes
16
VALID_FROM_VALUE
AUSP-ATFLV - Tolerance from
DECIMAL
48
28
10
yes
12
Appendix Table Column Details AUSP.ATFLB - Derive Date To and Time To bucket
17
VALID_TO_DATE
DATETIME
24
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
yes
21
VALUE_PRECISION
CABN-ANZST - Number of characters
NVARCSTR
yes
22
VALUE_SCALE
CABN-AMZDZ - Number of decimal places
NVARCSTR
yes
CHART_OF_ACCOUNTS
Chart of Accounts in SAP (T004 and T004T tables)
CHART_OF_ACCT_FU LL_NAME
Chart of accounts full name
NVARCSTR
120
yes
CHART_OF_ACCT_ID PK
Chart of accounts
NVARCSTR
no
CHART_OF_ACCT_NA ME
Chart of accounts description
NVARCSTR
50
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
13
CLASSIFICATION_HIER
Classification Hierarchy for the objects - KSSK/TCLA/KLAH
CHILD_DESCR
KLAT-TXTBZ (lookup) - Object description lookup
NVARCSTR
60
yes
CHILD_ID
PK
KSSK-OBJEK -Object number
NVARCSTR
50
no
CHILD_NAME
KLAH-CLASS (lookup) - Class name
NVARCSTR
60
yes
CLASS_TYPE_DESCR
TCLAT-KLART (lookup) - Class type description + KSSK-KLART - Class type ID
NVARCSTR
50
yes
CLASS_TYPE_ID
PK
KSSK-KLART - Class type
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
OBJ_CLASS_FLAG
PK
KSSK.MAFID - Indicator: object/class
NVARCSTR
no
PARENT_DESCR
KLAT-TXTBZ (lookup) - Class description lookup
NVARCSTR
60
yes
10
PARENT_ID
PK
KSSK-CLINT - Internal class number
NVARCSTR
50
no
11
PARENT_NAME
KLAH-CLASS (lookup) - Class number
NVARCSTR
60
yes
12
TABLE_NAME
TCLA.OBTAB - Name of database table for object
NVARCSTR
10
yes
14
CLASSIFICATION_HIER_HZ
Horizontal flattening of Equipment and Classification hierarchy relationships
CLASS_TYPE_FULL_ NAME
PK
TCLA-KLART (lookup) - Classific. type ID and NVARCSTR TCLAT-ARTXT Classific Type Description
50
yes
CLASS_TYPE_ID
PK
TCLA-KLART- Classification type ID
NVARCSTR
no
INTERNAL_CLASS_ID PK
KSSK-CLINT/KSSK-OBJEK - Internal class/Object number
NVARCSTR
50
no
LEAF_LVL
Cost Center Hierarchy Child ID
DECIMAL
48
28
yes
LOAD_DATE
Load date
DATETIME
24
yes
LOAD_TIME
Load time
NVARCSTR
yes
LVL_00_DESCR
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR Object description/name lookup
60
yes
LVL_00_FULL_NAME
Cost Center ID and Desc for Level 0
NVARCSTR
120
yes
LVL_00_ID
PK
KSSK-CLINT - Internal class number
NVARCSTR
50
no
10
LVL_01_DESCR
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR Object description/name lookup KSSK-CLINT/KSSK-OBJEK - Internal class/Object number + KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - Object description/name lookup PK KSSK-CLINT/KSSK-OBJEK - Internal class/Object number
60
yes
11
LVL_01_FULL_NAME
NVARCSTR
120
yes
12
LVL_01_ID
NVARCSTR
50
no
13
LVL_02_DESCR
60
yes
14
LVL_02_FULL_NAME
NVARCSTR
120
yes
15
LVL_02_ID
NVARCSTR
50
no
16
LVL_03_DESCR
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR Object description/name lookup
60
yes
15
Appendix Table Column Details KSSK-CLINT/KSSK-OBJEK - Internal class/Object number + KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - Object description/name lookup PK KSSK-CLINT/KSSK-OBJEK - Internal class/Object number
17
LVL_03_FULL_NAME
NVARCSTR
120
yes
18
LVL_03_ID
NVARCSTR
50
no
19
LVL_04_DESCR
60
yes
20
LVL_04_FULL_NAME
NVARCSTR
120
yes
21
LVL_04_ID
NVARCSTR
50
no
22
LVL_05_DESCR
60
yes
23
LVL_05_FULL_NAME
NVARCSTR
120
yes
24
LVL_05_ID
NVARCSTR
50
no
16
CLASSIFICATION_HIER_VR
Vertical flattening of Equipment and Classification hierarchy relationships
CHILD_DESCR
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR Object description/name lookup KSSK-CLINT/KSSK-OBJEK - Internal class/Object number + KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - Object description/name lookup PK KSSK-CLINT/KSSK-OBJEK - Internal class/Object number TCLAT-KLART (lookup) - Class type description + KSSK-KLART - Class type ID
60
yes
CHILD_FULL_NAME
NVARCSTR
120
yes
CHILD_ID
NVARCSTR
50
no
CLASS_TYPE_FULL_ NAME
NVARCSTR
50
no
CLASS_TYPE_ID
PK
TCLA-KLART- Classification type ID
NVARCSTR
no
DEPTH
Node depth in the hierarchy
DECIMAL
48
28
yes
LEAF_FLAG
1- Leaf, 0 - parent
DECIMAL
48
28
yes
LOAD_DATE
Load date
DATETIME
24
yes
LOAD_TIME
Load time
NVARCSTR
yes
10
PARENT_DESCR
60
yes
11
PARENT_FULL_NAME
NVARCSTR
120
yes
12
PARENT_ID
NVARCSTR
50
no
13
ROOT_FLAG
1 - Root, 0 - child
DECIMAL
48
28
yes
17
COMPANY_CODE
T001 - Company Code master
ADDRESS_ID
Company default address identifier
NVARCSTR
10
yes
CHART_OF_ACCT_ID
Company Code chart of accounts
NVARCSTR
yes
CHART_OF_ACCT_ID _COUNTRY CHART_OF_ACCT_NA ME
Chart of Accounts according to country legislation
NVARCSTR
yes
Chart of Accounts Name
NVARCSTR
50
yes
CITY
Company City Name
NVARCSTR
40
yes
CMPNY_CODE_FULL_ NAME
Company Code and Name
NVARCSTR
120
yes
CMPNY_CODE_ID
PK
T001-BURKS - Company Code ID
NVARCSTR
no
CMPNY_CODE_ID_OR IGINAL
Original Key of Company Code
NVARCSTR
yes
CMPNY_CODE_NAME
Company Code Name
NVARCSTR
40
yes
10
CMPNY_CODE_NAM E_01 CMPNY_CODE_NAM E_02 CMPNY_CODE_NAM E_03 CMPNY_CODE_NAM E_04
Name of the Company - 1st description
NVARCSTR
40
yes
11
Name of the Company - 2nd description
NVARCSTR
40
yes
12
Name of the Company - 3rd description
NVARCSTR
40
yes
13
Name of the Company - 4th description
NVARCSTR
40
yes
14
COUNTRY_ID
Country Identifier
NVARCSTR
yes
15
COUNTRY_NAME
Country Name (lookup)
NVARCSTR
15
yes
16
CR_CTRL_AREA_DES CR
Credit Controlling Area description
NVARCSTR
35
yes
18
17
CR_CTRL_AREA_ID
Credit Control area
NVARCSTR
yes
18
CURR_ID
Company Code Currency ID
NVARCSTR
yes
19
DISTRICT
District of the Company
NVARCSTR
40
yes
20
FAX
Fax no of the Company
NVARCSTR
40
yes
21
FIN_MGMT_AREA_ID
Financial Management Area
NVARCSTR
yes
22
FISC_YR_VARIANT_ID
Company code fiscal year variant
NVARCSTR
yes
23
FISC_YR_VARIANT_N AME
Company code fiscal year variant name
NVARCSTR
30
yes
24
HOUSE_NUMBER
Company code house number
NVARCSTR
10
yes
25
LANG_DESCR
Company code language Description
NVARCSTR
16
yes
26
LANG_ID
Company Code default language
NVARCSTR
yes
27
LOAD_DATE
24
yes
28
LOAD_TIME
NVARCSTR
yes
29
PHONE
Company code telephone number
NVARCSTR
30
yes
30
REGION_ID
Company code region
NVARCSTR
yes
31
REGION_NAME
Company code region name
NVARCSTR
20
yes
32
STREET
Company code street name
NVARCSTR
60
yes
33
TAX_JURISDIC_NUM
Jurisdiction fo tax calculation - tax jurisdiction code
NVARCSTR
15
yes
34
VAT_REGISTRTN_NU M
VAT regulation number
NVARCSTR
20
yes
19
35
ZIP
Company code postal code
NVARCSTR
10
yes
CONTROL_KEY
Business transactions should be executed for the object that belongs to the task list or order (from T430)
AUTO_GR_FLAG
T430.AUTWE - Indicator: automatic goods receipt
NVARCSTR
yes
CAPACITY_PLAN_FLA G CONFIRMATN_FLAG_ DESCR CONFIRMATN_FLAG_I D
T430.KAPA - Indicator: Capacity planning
NVARCSTR
yes
Lookup description of confirmation indicator
NVARCSTR
60
yes
T430.RUEK - Indicator: completion confirmation
NVARCSTR
yes
CTRL_KEY_DESCR
Lookup description of control key
NVARCSTR
40
yes
CTRL_KEY_ID
PK
T430.STEUS - Control key
NVARCSTR
no
INSPECTN_FLAG
T430.MRKKZ - Indicator: inspection characteristics for operation require
NVARCSTR
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
10
REWORK_FLAG
T430.REWORK - Indicator: Rework operation
NVARCSTR
yes
11
SCHEDULE_FLAG
T430.TERM - Indicator: Scheduling
NVARCSTR
yes
12
SERVICE_FLAG
T430.SERVICE - Indicator: Service
NVARCSTR
yes
20
CONTROLLING_AREA
TKA01 - Controlling areas master
CTRL_AREA_DESCR
Controlling Area Name
NVARCSTR
25
yes
CTRL_AREA_FULL_N AME
Controlling Area DI and Desc
NVARCSTR
120
yes
CTRL_AREA_ID
PK
TKA01-KORKS - Controlling Area ID
NVARCSTR
no
CURR_ID
Currency Code for Controlling Area
NVARCSTR
yes
FISC_YR_VARIANT_ID
Fiscal Year Variant
NVARCSTR
yes
LEDGER_ID_PROFIT_ CNTR
Financial Ledger ID profit Center
NVARCSTR
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
OPERTNG_CONCER N_ID
Operating Concern
NVARCSTR
yes
10
PROFIT_CNTR_AREA
Profit Center Group
NVARCSTR
12
yes
11
STD_SET_HIER_COD E
Standard Hierarchy for Cost Centers
NVARCSTR
12
yes
21
COST_CENTER
CSKS - Cost Center Master
ALT_FUNCTN
CSKS.AFUNK - Alternative function of Cost Center
NVARCSTR
yes
BUS_AREA_ID
Business Area ID
NVARCSTR
yes
CITY
Cost Center City Name
NVARCSTR
40
yes
CMPNY_CODE_ID
Company Code ID
NVARCSTR
yes
CMPNY_CODE_NAME
Company code name associated with this Cost NVARCSTR Center
40
yes
COST_CNTR_DESCR
Cost Center Descritpion
NVARCSTR
60
yes
COST_CNTR_FULL_N AME
Cost Center ID and Desc
NVARCSTR
120
yes
COST_CNTR_ID
PK
CSKS-KOSTL - Cost Center ID
NVARCSTR
10
no
COST_CNTR_ID_SUB SEQUENT
CSKS.NKOST - Subsequent Cost Center ID
NVARCSTR
10
yes
10
COST_CNTR_NAME
Cost Center Default Name
NVARCSTR
40
yes
11
COST_CNTR_NAME_0 1 COST_CNTR_NAME_0 2 COST_CNTR_NAME_0 3 COST_CNTR_NAME_0 4
Cost Center Name Line 1
NVARCSTR
40
yes
12
NVARCSTR
40
yes
13
NVARCSTR
40
yes
14
NVARCSTR
40
yes
15
COUNTRY_ID
Cost Center Country Code
NVARCSTR
yes
16
COUNTRY_NAME
Cost Center Country Name
NVARCSTR
15
yes
22
17
CREATED_BY
Person ID who created the record
NVARCSTR
12
yes
18
CREATE_DATE
Date when the record was created in the source system
DATETIME
24
yes
19
CTRL_AREA_DESCR
Control Area description
NVARCSTR
25
yes
20
CTRL_AREA_ID
PK
Controlling Area Identifier
NVARCSTR
no
21
CURR_ID
Cost Center Currency ID
NVARCSTR
yes
22
DEPARTMENT
CSKS.ABTEI - Department
NVARCSTR
12
yes
23
DISTRICT
Cost Center City District
NVARCSTR
40
yes
24
EQUITY_TYPE_CODE
CSKS.ETYPE - Equity type
NVARCSTR
yes
25
FAX
Cost Center fax number
NVARCSTR
40
yes
26
FUNCTN_CODE
CSKS.FUNKT - function of Cost Center
NVARCSTR
yes
27
LOAD_DATE
24
yes
28
LOAD_TIME
NVARCSTR
yes
29
PERSON_IN_CHARGE
CSKS.VERAK - Cost Center Manager
NVARCSTR
20
yes
30
PHONE
Cost Center phone # 1
NVARCSTR
30
yes
31
PROFIT_CNTR_DESC R
Profit Center Description
NVARCSTR
40
yes
32
PROFIT_CNTR_ID
CSKS.PRCTR - Profit Center Code
NVARCSTR
10
yes
33
REGION_ID
Region ID
NVARCSTR
yes
34
REGION_NAME
Region name
NVARCSTR
20
yes
23
35
STREET
Cost Center Street name
NVARCSTR
60
yes
36
TYPE_CODE
Cost Center Type Identifier
NVARCSTR
yes
37
VALID_FROM_DATE
Record is valid to
DATETIME
24
yes
38
VALID_TO_DATE
Record Valid from
DATETIME
24
yes
39
ZIP
Cost Center ZIP code
NVARCSTR
10
yes
COST_CENTER_HIER
Cost Center Hierarchy - CCSS-KOSTL - Cannot have a primary key due to possible duplicate entries in SAP
CHILD_DESCR
Cost Center Child description
NVARCSTR
64
yes
CHILD_ID
PK
Cost Center Child Node ID
NVARCSTR
12
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
no
LEAF_FLAG
PK
Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Cost Center parent descritpion
NVARCSTR
64
yes
PARENT_ID
PK
Cost Center Parent Node ID
NVARCSTR
12
no
ROOT_FLAG
PK
Is Root
NVARCSTR
no
24
COST_CENTER_HIER_BAD
CCSS-KOSTL Cost Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
Cost Center Child description
NVARCSTR
64
yes
CHILD_ID
PK
NVARCSTR
12
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
no
ETL_ERROR_ACTN
NVARCSTR
yes
ETL_ERROR_COLU MN
NVARCSTR
500
yes
LEAF_FLAG
PK
Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Cost Center parent descritpion
NVARCSTR
64
yes
10
PARENT_ID
PK
NVARCSTR
12
no
11
ROOT_FLAG
PK
Is Root
NVARCSTR
no
25
COST_CENTER_HIER_HZ
CCSS-KOSTL Cost Center hierarchy flattenned horizontally -- Cannot have a primary key on this table due to possible duplicate entries in SAP
COST_CNTR_ID
PK
Cost Center ID (current node)
NVARCSTR
12
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
no
LEAF_LVL
Is Leaf Level
INTEGER
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
Cost Center Root Node Description
NVARCSTR
64
yes
LVL_00_FULL_NAME
NVARCSTR
120
yes
LVL_00_ID
PK
Cost Center root node ID
NVARCSTR
12
no
LVL_01_DESCR
Cost Center level 1 Node Description
NVARCSTR
64
yes
10
LVL_01_FULL_NAME
NVARCSTR
120
yes
11
LVL_01_ID
PK
Cost Center level 1 Node ID
NVARCSTR
12
no
12
LVL_02_DESCR
NVARCSTR
64
yes
13
LVL_02_FULL_NAME
Cost Center Id and Desc for Level 2
NVARCSTR
120
yes
14
LVL_02_ID
PK
NVARCSTR
12
no
15
LVL_03_DESCR
NVARCSTR
64
yes
16
LVL_03_FULL_NAME
NVARCSTR
120
yes
26
17
LVL_03_ID
PK
NVARCSTR
12
no
18
LVL_04_DESCR
NVARCSTR
64
yes
19
LVL_04_FULL_NAME
NVARCSTR
120
yes
20
LVL_04_ID
PK
NVARCSTR
12
no
21
LVL_05_DESCR
NVARCSTR
64
yes
22
LVL_05_FULL_NAME
NVARCSTR
120
yes
23
LVL_05_ID
PK
NVARCSTR
12
no
24
LVL_06_DESCR
NVARCSTR
64
yes
25
LVL_06_FULL_NAME
NVARCSTR
120
yes
26
LVL_06_ID
PK
NVARCSTR
12
no
27
LVL_07_DESCR
NVARCSTR
64
yes
28
LVL_07_FULL_NAME
Cost Center Id and Dec for Level 7
NVARCSTR
120
yes
29
LVL_07_ID
PK
NVARCSTR
12
no
30
LVL_08_DESCR
NVARCSTR
64
yes
31
LVL_08_FULL_NAME
NVARCSTR
120
yes
32
LVL_08_ID
PK
NVARCSTR
12
no
33
LVL_09_DESCR
NVARCSTR
64
yes
34
LVL_09_FULL_NAME
NVARCSTR
120
yes
27
35
LVL_09_ID
PK
NVARCSTR
12
no
36
LVL_10_DESCR
NVARCSTR
64
yes
37
LVL_10_FULL_NAME
NVARCSTR
120
yes
38
LVL_10_ID
PK
NVARCSTR
12
no
COST_CENTER_HIER_VR
CCSS-KOSTL - Cost Center Hierarchy vertically flattenned - cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
Cost Center Child Node Description
NVARCSTR
64
yes
CHILD_FULL_NAME
Cost Center ID and Desc for the Child
NVARCSTR
120
yes
CHILD_ID
PK
NVARCSTR
12
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
no
DEPTH
Node depth level
INTEGER
yes
LEAF_FLAG
Is Leaf
INTEGER
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Cost Center Child Node Descritpion
NVARCSTR
64
yes
10
PARENT_FULL_NAME
Cost Center Parent ID and Desc
NVARCSTR
120
yes
11
PARENT_ID
PK
NVARCSTR
12
no
12
ROOT_FLAG
Is Root
INTEGER
yes
28
COST_ELEMENT
CSKA - Cost Element (GL Accounts) Master
CHART_OF_ACCT_ID PK
Accounting Chart of accounts ID
NVARCSTR
no
COST_ELEM_DESCR
Cost center description in default language
NVARCSTR
40
yes
COST_ELEM_FULL_N AME
Cost Element ID and Description
NVARCSTR
120
yes
COST_ELEM_ID
PK
Cost Element (GL Account) ID
NVARCSTR
10
no
CREATE_DATE
Date when the record was created in the source system
DATETIME
24
yes
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) CSKA.ZAHKZ - Cost element is payment-relevant
24
yes
LOAD_TIME
NVARCSTR
yes
PAYMNT_RELEVNT_F LAG
NVARCSTR
yes
TAX_RELEVNT_FLAG
CSKA.STEKZ - Cost Element is tax-relevant
NVARCSTR
yes
29
COST_ELEMENT_HIER
CCSS-KSTAR Cost Element hierarchy - cannot have primary key due to data duplication possible in SAP
CHART_OF_ACCT_ID PK
Accounting Chart of Accounts ID
NVARCSTR
no
CHILD_DESCR
Cost Element Child Node Description
NVARCSTR
64
yes
CHILD_ID
PK
Cost Element Child Node ID
NVARCSTR
12
no
LEAF_FLAG
PK
Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Cost Element Parent Node Descritpion
NVARCSTR
64
yes
PARENT_ID
PK
Cost Element Parent Node ID
NVARCSTR
12
no
ROOT_FLAG
PK
Is Root
NVARCSTR
no
30
COST_ELEMENT_HIER_BAD
CCSS-KSTAR Cost ElementHierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
CHART_OF_ACCT_ID PK
NVARCSTR
no
CHILD_DESCR
NVARCSTR
64
yes
CHILD_ID
PK
NVARCSTR
12
no
ETL_ERROR_ACTN
NVARCSTR
yes
ETL_ERROR_COLU MN
NVARCSTR
500
yes
LEAF_FLAG
PK
Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
NVARCSTR
64
yes
10
PARENT_ID
PK
NVARCSTR
12
no
11
ROOT_FLAG
PK
Is Root
NVARCSTR
no
31
COST_ELEMENT_HIER_HZ
CCSS-KSTAR - Cost Element Hierarchy- cannot have primary key due to possible duplicate entries in SAP
CHART_OF_ACCT_ID PK
Accounting Chart Of Account ID
NVARCSTR
no
COST_ELEM_ID
PK
Cost Element (GL Account) ID
NVARCSTR
12
no
LEAF_LVL
Cost Element Leaf level (depth)
DECIMAL
48
28
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
Cost Element Root Node Description
NVARCSTR
64
yes
LVL_00_FULL_NAME
Cost Element ID and Descripion for level 0
NVARCSTR
120
yes
LVL_00_ID
PK
Cost Element Root Node ID
NVARCSTR
12
no
LVL_01_DESCR
Cost Element Level 1 Node Description
NVARCSTR
64
yes
10
LVL_01_FULL_NAME
Cost Element ID and Desc for Level 1
NVARCSTR
120
yes
11
LVL_01_ID
PK
Cost Element Level 1 Node ID
NVARCSTR
12
no
12
LVL_02_DESCR
NVARCSTR
64
yes
13
LVL_02_FULL_NAME
NVARCSTR
120
yes
14
LVL_02_ID
PK
NVARCSTR
12
no
15
LVL_03_DESCR
NVARCSTR
64
yes
16
LVL_03_FULL_NAME
NVARCSTR
120
yes
32
17
LVL_03_ID
PK
NVARCSTR
12
no
18
LVL_04_DESCR
NVARCSTR
64
yes
19
LVL_04_FULL_NAME
NVARCSTR
120
yes
20
LVL_04_ID
PK
NVARCSTR
12
no
21
LVL_05_DESCR
NVARCSTR
64
yes
22
LVL_05_FULL_NAME
NVARCSTR
120
yes
23
LVL_05_ID
PK
NVARCSTR
12
no
24
LVL_06_DESCR
NVARCSTR
64
yes
25
LVL_06_FULL_NAME
NVARCSTR
120
yes
26
LVL_06_ID
PK
NVARCSTR
12
no
27
LVL_07_DESCR
NVARCSTR
64
yes
28
LVL_07_FULL_NAME
NVARCSTR
120
yes
29
LVL_07_ID
PK
NVARCSTR
12
no
33
COST_ELEMENT_HIER_VR
CCSS-KSTAR - Cost Element Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP
CHART_OF_ACCT_ID PK
NVARCSTR
no
CHILD_DESCR
NVARCSTR
64
yes
CHILD_FULL_NAME
Cost Element Child ID and Desc
NVARCSTR
120
yes
CHILD_ID
PK
NVARCSTR
12
no
DEPTH
Cost Element node depth level
DECIMAL
48
28
yes
LEAF_FLAG
Is Leaf
DECIMAL
48
28
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
NVARCSTR
64
yes
10
PARENT_FULL_NAME
Cost Element Parent ID and Desc
NVARCSTR
120
yes
11
PARENT_ID
PK
NVARCSTR
12
no
12
ROOT_FLAG
Is Root
DECIMAL
48
28
yes
34
CURRENCY
TCURC, TCURT
CURR_DECIMAL
Lookup TCURX.CURRDEC - Number of decimals to display amounts in this currency.
DECIMAL
48
28
yes
CURR_DESCR
TCURT-LTEXT - Long Text
NVARCSTR
60
yes
CURR_ID
PK
TCURC-WAERS - Currency Key
NVARCSTR
no
CURR_ID_ALT
TCURC-ALTWR - Alternative Key For Currencies
NVARCSTR
yes
CURR_ISO_CODE
TCURC-ISOCD - ISO Currency Code
NVARCSTR
yes
DISPLAY_FACTOR
Multiply currency amounts by this factor to display with correct number of decimals for the DECIMAL currency Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) TCURC-GDATU -Date Up Until Which The Currency Is Valid
48
17
14
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
VALID_TO_DATE
DATETIME
24
yes
35
CUSTOMER
General customer master data at the customer level (KNA1)
ACCT_GRP_ID
KNA1-KTOKD - Customer Group Account
NVARCSTR
yes
ACCT_GRP_NAME
Lookup of account group name from T077X.TXT30 from KNA1.KTKOD
NVARCSTR
30
yes
ADDRESS_ID
Load date
NVARCSTR
10
yes
AMT_ANNUAL_SALES
KNA1-UMSAT - Annual sale
DECIMAL
48
15
yes
AMT_ANNUAL_SALES _02
KNA1-UMSA1 - Annual Sales
DECIMAL
48
15
yes
ANNUAL_SALES_YR
KNA1-UMJAH - Year for which sales are given NVARCSTR
yes
CITY
KNA1-ORT01 - City
NVARCSTR
40
yes
CLASSIFCTN_CODE
KNA1-KUKLA - Customer Classification Lookup of TKUKT.VTEXT for description of customer classification (size by total sales) based on KNA1.KUKLA. KNA1-DEAR1 - Competitor ID
NVARCSTR
yes
CLASSIFCTN_DESCR
NVARCSTR
20
yes
10
COMPETITOR_FLAG
NVARCSTR
yes
11
COUNTRY_ID
KNA1-LAND1 - Country
NVARCSTR
yes
12
COUNTRY_NAME
Country Name
NVARCSTR
15
yes
13
CUSTOMER_FULL_NA ME CUSTOMER_GRP_K EY
Customer Full Name
NVARCSTR
120
yes
14
Customer Group Key
NVARCSTR
10
yes
15
CUSTOMER_ID
PK
KNA1-KUNNR - Customer Number
NVARCSTR
10
no
16
CUSTOMER_NAME
Customer Name
NVARCSTR
40
yes
36
Appendix Table Column Details CUSTOMER_NAME_ 01 CUSTOMER_NAME_ 02 CUSTOMER_NAME_ 03 CUSTOMER_NAME_ 04
17
KNA1-NAME1 - Customer Name 1
NVARCSTR
40
yes
18
KNA1-NAME2 - Customer Name 2
NVARCSTR
40
yes
19
Customer Name 3
NVARCSTR
40
yes
20
Customer Name 4
NVARCSTR
40
yes
21
DISTRICT
KNA1-ORT02 - District
NVARCSTR
40
yes
22
EMPL_COUNT
KNA1-JMZAH - Number of employees for the year
DECIMAL
48
28
yes
23
FAX
KNA1-TELFX - Fax Number
NVARCSTR
40
yes
24
HOUSE_NUMBER
Customer House Number
NVARCSTR
10
yes
25
INDUSTRY_ID
KNA1-BRSCH - Industry Lookup of industry name in T016T.BRTXT where SPRAS=$G_LANGUAGE and KNA1.BRSCH=T016T.BRSCH. KNA1-EKONT - Initial Contact
NVARCSTR
yes
26
INDUSTRY_NAME
NVARCSTR
20
yes
27
INITIAL_CONTACT
NVARCSTR
10
yes
28
LANG_DESCR
Description of the Language
NVARCSTR
16
yes
29
LANG_ID
KNA1-SPRAS -- Language
NVARCSTR
yes
30
LOAD_DATE
24
yes
31
LOAD_TIME
NVARCSTR
yes
32
NIELSEN_CODE
KNA1.NIELS - Nielsen ID
NVARCSTR
yes
33
PHONE
Telephone Number
NVARCSTR
30
yes
34
REGIONAL_MARKET
KNA1-RPMKR - Regional market
NVARCSTR
10
yes
37
35
REGION_ID
KNA1-REGIO - Region (State)
NVARCSTR
yes
36
REGION_NAME
Region Name (State Name)
NVARCSTR
20
yes
37
SALES_PARTNER_FL AG SALES_PROSPECT_F LAG
KNA1-DEAR2 - Sales Partner Indicator
NVARCSTR
yes
38
KNA1-DEAR3 - Sales Prospect ID
NVARCSTR
yes
39
STREET
KNA1-STRAS - Street and House Number
NVARCSTR
60
yes
40
VENDOR_ID
KNA1.LIFNR -- Vendor (creditor) account number
NVARCSTR
10
yes
41
ZIP
KNA1-PSTLZ - Postal Code
NVARCSTR
10
yes
DOCUMENT_CATEGORY
Domain VBTYP (Table DD07T) - Sales Document Categ
DIM_SRC_ID
PK
Dimension Source from table AW_DIMENSION_SOURCE Document Category Description from multiple sources in SAP
NVARCSTR
10
no
DOC_CATEG_DESCR
NVARCSTR
100
yes
DOC_CATEG_ID
PK
Document Category ID from multiple sources in NVARCSTR SAP
10
no
LOAD_DATE
Date and Time Loaded in Rapid Mart
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
38
DOCUMENT_TYPE
Internal Order Type attributes from T003O/T003P
DIM_SRC_ID
PK
Dimension Source from table AW_DIMENSION_SOURCE
NVARCSTR
10
no
DOC_CATEG_DESCR
Document Category Description
NVARCSTR
100
yes
DOC_CATEG_ID
PK
Document Category from multiple Sources in SAP
NVARCSTR
10
no
DOC_TYPE_DESCR
Document Type Description
NVARCSTR
100
yes
DOC_TYPE_ID
PK
Document Type from Multiple sources in SAP
NVARCSTR
10
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
39
EQUIPMENT
EQUI, EQUZ, ILOA - Equipment dimension
ABC_FLAG
ILOA-ABCKZ - ABC indicator for technical object
NVARCSTR
yes
ACQUISTN_DATE
EQUI-ANSDT - Acquisition date
DATETIME
24
yes
AMT_ACQUISTN
EQUI-ANSWT - Equipment acquisition value
DECIMAL
48
13
yes
ASSET_MAIN_ID
ILOA.ANLNR - Main asset number
NVARCSTR
12
yes
ASSET_SUB_ID
ILOA.ANLUN - Asset sub-number
NVARCSTR
yes
BUS_AREA_DESCR
Lookup on TGSBT-GTEXT for Sales Org Descr NVARCSTR
30
yes
BUS_AREA_ID
ILOA-GSBER - Business area
NVARCSTR
yes
CHANGE_BY_LOGIN
EQUI-AENAM - Name of accounting clerk who NVARCSTR changed record
12
yes
CHANGE_DATE
EQUI-AEDAT - Last changed on
DATETIME
24
yes
10
CMPNY_CODE_ID
ILOA-BUKRS - Company code
NVARCSTR
yes
11
CMPNY_CODE_NAME
T001.BUTXT -Lookup on Company Code Name
NVARCSTR
25
yes
12
CONSTRUCTN_MON TH
EQUI-BAUMM - Month of construction
DECIMAL
48
28
yes
13
CONSTRUCTN_YEAR
EQUI-BAUJJ - Year of construction
DECIMAL
48
28
yes
14
COST_CNTR_ID
ILOA.KOSTL - Cost center
NVARCSTR
10
yes
15
COST_CNTR_NAME
CSKT.KTEXT - Lookup on Cost Center Name
NVARCSTR
40
yes
16
CREATE_BY_LOGIN
EQUI-ERNAM - Name of person who created object
NVARCSTR
12
yes
40
Appendix Table Column Details EQUI-ERDAT - Date on which the record was DATETIME created
17
CREATE_DATE
24
yes
18
CTRL_AREA_ID
ILOA.KOKRS - Controlling area
NVARCSTR
yes
19
CTRL_AREA_NAME
Lookup on TKA01 for controlling area name
NVARCSTR
25
yes
20
CURR_ID
EQUI-WAERS - Currency key
NVARCSTR
yes
21
DAYS_DELIVER
Number of days from Acquisiton till Original Delivery (calcualted) Number of days from Acquisiton till Original startup (calcualted)
DECIMAL
48
28
yes
22
DAYS_INSTALL
DECIMAL
48
28
yes
23
DAYS_IN_OPERATIO N
Total number of days since the original startup DECIMAL as of LOAD_DATE (calcualted)
48
28
yes
24
DAYS_WARRANTY
Duration of the warranty (calcualted)
DECIMAL
48
28
yes
25
DISTRIBTN_CHANNEL _DESCR DISTRIBTN_CHANNEL _ID
Lookup on TVTWT-VTEXT for Sales Org Descr NVARCSTR
40
yes
26
ILOA.VTWEG - Distribution channel
NVARCSTR
yes
27
DIVISION_DESCR
40
yes
28
DIVISION_ID
ILOA.SPART - Division
NVARCSTR
yes
29
EQUIPMNT_CATEG_D ESCR EQUIPMNT_CATEG_I D
T370U-TYPTX (lookup) - Equipment category description
NVARCSTR
30
yes
30
EQUI-EQTYP - Equipment category
NVARCSTR
yes
31
EQUIPMNT_DESCR
EQKT-EQKTX (lookup)
NVARCSTR
40
yes
32
EQUIPMNT_FULL_NA ME
EQUI.EQUNR and EQKT-EQKTX - Equipment NVARCSTR Number and Descr.
65
yes
33
EQUIPMNT_ID
PK
EQUI-EQUNR - Equipment number
NVARCSTR
18
no
34
EQUIPMNT_ID_PAR
EQUZ-HEQUI - Superior equipment
NVARCSTR
18
yes
41
35
EQUIPMNT_SIZE
EQUI-GROES - Size/dimension
NVARCSTR
18
yes
36
EQUIPMNT_TYPE_DE SCR
T370K_T-EARTX (lookup) - Equipment Type description
NVARCSTR
20
yes
37
EQUIPMNT_TYPE_ID
EQUI-EQART - Equipment type
NVARCSTR
10
yes
38
FUNCTNL_LOCATN_D ESCR FUNCTNL_LOCATN_I D
IFLOTX-PLTXT (lookup) - Functional Loacation NVARCSTR descritpion
40
yes
39
ILOA-TPLNR - Functional location
NVARCSTR
30
yes
40
LOAD_DATE
DATETIME
24
yes
41
LOAD_TIME
NVARCSTR
yes
42
LOCATN_DESCR
T499S-KTEXT (lookup) - Text (40 characters) NVARCSTR
40
yes
43
LOCATN_ID
ILOA-STORT - Location of maintenance object NVARCSTR
10
yes
44
MANUFCTR_COUNT RY MANUFCTR_MODEL _NUM
EQUI-HERLD - Country of manufacture
NVARCSTR
yes
45
EQUI-TYPBZ - Manufacturer model number
NVARCSTR
20
yes
46
MANUFCTR_NAME
EQUI-HERST - Manufacturer of asset
NVARCSTR
30
yes
47
MANUFCTR_SERIAL_ NUM
EQUI-SERGE - Manufacturer serial number
NVARCSTR
30
yes
48
MATERIAL_DESCR
MAKT.MAKTX - Material Description lookup
NVARCSTR
40
yes
49
MATERIAL_ID
EQUI.MATNR - Material number
NVARCSTR
18
yes
50
OBJ_ID
EQUI-OBJNR - Object number
NVARCSTR
22
yes
51
PERSON_FULLNAME_ RESP
PA0002.NACHN - Personnel Last Name + PA0002.VORNA - Personnel First Name
NVARCSTR
85
yes
52
PERSON_ID_RESP
IHPA-PARNR (lookup on VW function)
NVARCSTR
12
yes
42
53
PLANT_ID
ILOA-SWERK - Maintenance plant
NVARCSTR
yes
54
PLANT_ID_PLAN
EQUZ.IWERK - Planning plant
NVARCSTR
yes
55
PLANT_NAME
T001W.NAME1 Name - Lookup on Plant name T001W.NAME1 Name - Lookup on Plant name for Planning Plant PRPS.POST1 - Lookup of Project (WBS) Element Description ILOA-PROID - Work breakdown structure element (WBS element)
NVARCSTR
30
yes
56
PLANT_NAME_PLAN
NVARCSTR
30
yes
57
PROJ_ELEM_DESCR
NVARCSTR
40
yes
58
PROJ_ELEM_ID
NVARCSTR
24
yes
59
ROOM
ILOA-MSGRP - Plant Room
NVARCSTR
yes
60
SALES_ORG_DESCR
Lookup on TVKOT-VTEXT for Sales Org Descr NVARCSTR
60
yes
61
SALES_ORG_ID
ILOA.VKORG Sales organization
NVARCSTR
yes
62
SECTION_ID
ILOA-BEBER - Plant section
NVARCSTR
yes
63
SECTION_PERSON_R ESP
T357-FING (lookup) - Person responsible for company area T357-TELE (lookup) - Phone number of person responsible for company area
NVARCSTR
14
yes
64
SECTION_PHONE
NVARCSTR
12
yes
65
SERIAL_NUM
EQUI.SERNR - Serial number
NVARCSTR
18
yes
66
STARTUP_DATE
EQUI-INBDT - First start-up date of the piece of equipment
DATETIME
24
yes
67
TECHNICAL_NUM
EQUZ-TIDNR - Technical identification number NVARCSTR
25
yes
68
UOM_ID_WEIGHT
EQUI-GEWEI - Unit of weight
NVARCSTR
yes
69
VALID_FROM_DATE
EQUI-GWLDT - Guarantee start date
DATETIME
24
yes
70
VALID_TO_DATE
EQUI-GWLEN - Date on which the warranty ends
DATETIME
24
yes
43
71
VENDOR_ID
EQUI-ELIEF - Vendor number
NVARCSTR
10
yes
72
WEIGHT
EQUI-BRGEW - Gross weight
DECIMAL
48
13
yes
44
EQUIPMENT_CHAR_FACT
Equipment Characteristic Details from AUSP/CABN/TCLA
ASSET_MAIN_ID
NVARCSTR
12
yes
ASSET_SUB_ID
NVARCSTR
yes
BUS_AREA_ID
PK
NVARCSTR
yes
NVARCSTR
30
yes
NVARCSTR
yes
NVARCSTR
30
yes
30
yes
CHARACTSTC_ID
PK
NVARCSTR
10
no
CHARACTSTC_NAME
30
yes
10
CHARACTSTC_VALUE
NVARCSTR
30
yes
11
CLASS_TYPE_ID
PK
NVARCSTR
no
12
CMPNY_CODE_ID
PK
NVARCSTR
yes
13
COST_CNTR_ID
PK
NVARCSTR
10
yes
14
CTRL_AREA_ID
PK
NVARCSTR
yes
15
DAYS_DIFF
Calculated date difference for Date-related caracteristics
DECIMAL
48
22
yes
16
EQUIPMNT_ID
PK
NVARCSTR
18
no
45
Appendix Table Column Details FUNCTNL_LOCATN_I D
17
PK
ILOA-TPLNR - Functional location
NVARCSTR
30
yes
18
LOAD_DATE
DATETIME
24
yes
19
LOAD_TIME
NVARCSTR
yes
20
LOCATN_ID
PK
10
yes
21
MATERIAL_ID
PK
EQUI.MATNR - Material number
NVARCSTR
18
yes
22
PERSON_ID_RESP
PK
NVARCSTR
12
yes
23
PLANT_ID
PK
NVARCSTR
yes
24
PROD_HIER_ID
MARA.PRDHA - Product Hierarchy ID - based on EQUI.MATNR
NVARCSTR
18
yes
25
UOM_ID_VALUE
PK
NVARCSTR
yes
26
VALID_FROM_DATE
PK
DATETIME
24
yes
27
VALID_FROM_NUMBE R
DECIMAL
48
28
10
yes
28
VALID_FROM_VALUE
DECIMAL
48
28
10
yes
29
VALID_TO_DATE
AUSP.ATFLB - Derive Date To and Time To bucket
DATETIME
24
yes
30
VALID_TO_NUMBER
DECIMAL
48
28
10
yes
31
VALID_TO_VALUE
DECIMAL
48
28
10
yes
32
VALUE_OPERATOR
NVARCSTR
yes
33
VALUE_PRECISION
NVARCSTR
yes
34
VALUE_SCALE
NVARCSTR
yes
46
35
VENDOR_ID
PK
EQUI-ELIEF - Vendor number
NVARCSTR
10
yes
EQUIPMENT_HIER
Equipment Hierarchy Stage table (from EQUI, EQUZ, EQUT in SAP)
CHILD_CATEG_DESC R
NVARCSTR
30
yes
CHILD_CATEG_ID
NVARCSTR
yes
CHILD_DESCR
EQKT-EQKTX (lookup)
NVARCSTR
40
yes
CHILD_FULL_NAME
EQUI-EQUNRI - Equipment ID +EQUT-EQLTX NVARCSTR - Equipment description
65
yes
CHILD_ID
PK
NVARCSTR
18
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_CATEG_DES CR
NVARCSTR
30
yes
PARENT_CATEG_ID
NVARCSTR
yes
10
PARENT_DESCR
EQKT-EQKTX (lookup)
NVARCSTR
40
yes
11
PARENT_FULL_NAME
65
yes
12
PARENT_ID
PK
EQUZ-HEQUI - Superior equipment
NVARCSTR
18
no
47
EQUIPMENT_HIER_HZ
EQUI, EQUZ, EQUT - Equipment hierarchy horizontal dimension
EQUIPMNT_ID
PK
EQUI-EQUNR - Equipment ID
NVARCSTR
18
no
LEAF_LVL
Leaf level
DECIMAL
48
28
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
EQUT-EQLTX - Equipment description
NVARCSTR
40
yes
LVL_00_FULL_NAME
65
yes
LVL_00_ID
EQUZ-HEQUI - Superior equipment ID
NVARCSTR
18
yes
LVL_01_DESCR
NVARCSTR
40
yes
LVL_01_FULL_NAME
65
yes
10
LVL_01_ID
EQUI-EQUNRI - Equipment ID
NVARCSTR
18
yes
11
LVL_02_DESCR
NVARCSTR
40
yes
12
LVL_02_FULL_NAME
65
yes
13
LVL_02_ID
NVARCSTR
18
yes
14
LVL_03_DESCR
NVARCSTR
40
yes
15
LVL_03_FULL_NAME
65
yes
16
LVL_03_ID
NVARCSTR
18
yes
48
17
LVL_04_DESCR
NVARCSTR
40
yes
18
LVL_04_FULL_NAME
65
yes
19
LVL_04_ID
NVARCSTR
18
yes
20
LVL_05_DESCR
NVARCSTR
40
yes
21
LVL_05_FULL_NAME
65
yes
22
LVL_05_ID
NVARCSTR
18
yes
49
EQUIPMENT_HIER_VR
EQUI, EQUZ, EQUT - Equipment hierarchy Vertical dimension
CHILD_DESCR
EQUT-EQLTX - Equipment text
NVARCSTR
40
yes
CHILD_FULL_NAME
65
yes
CHILD_ID
PK
NVARCSTR
18
no
DEPTH
Depth of the decendent
DECIMAL
48
28
yes
LEAF_FLAG
Leaf flag (1 - means this is a leaf, 0 - means it is not a leaf)
DECIMAL
48
28
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
NVARCSTR
40
yes
PARENT_FULL_NAME
65
yes
10
PARENT_ID
PK
EQUZ-HEQUI - Superior equipment number
NVARCSTR
18
no
11
ROOT_FLAG
Root flag (1 - means this is a root, 0 - means it DECIMAL is not a root)
48
28
yes
50
FINANCIAL_RECORD_CATEGORY
Descriptive attributes for Accounting Summary table Value Category from TPIR1T
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
RECORD_CATEG_D ESCR
TPIR1T-KTEXT - Text
NVARCSTR
30
yes
RECORD_CATEG_ID
PK
TPIR1T-ACPOS - Value category
NVARCSTR
14
no
FINANCIAL_RECORD_TYPE
Loads Special Ledger Record Types dimension (Domain RRCTY) from table DD07T and Cost/Plant Maintenance value types from CO_WRTTP domain of DD07T table - FINANCIAL_RECORD_
DIM_SRC_ID
PK
Dimension Source. Used in combined dimension combining similar attributes from different sources in SAP.
NVARCSTR
10
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
RECORD_TYPE_DE SCR
Financial Record Type Desc.
NVARCSTR
60
yes
RECORD_TYPE_ID
PK
Financial Record Type ID
NVARCSTR
10
no
51
FISC_PERIOD
Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)
CALENDAR_HALF
Calendar Half Year for this Fiscal Period
NVARCSTR
yes
CALENDAR_MONTH _LONG CALENDAR_MONTH _NUMERIC CALENDAR_MONTH _SHORT CALENDAR_QUART ER
Calendar Month (January - December) for this Fiscal Period Calendar Month (Numeric) for this Fiscal Period Calendar Month (JAN - DEC) for this fiscal Period
NVARCSTR
14
yes
NVARCSTR
yes
NVARCSTR
yes
Calendar Quarter for this Fiscal Period
INTEGER
yes
CALENDAR_YEAR
Calendar Year for this fiscal period
INTEGER
yes
CALENDAR_YEAR_HA LF CALENDAR_YEAR_ MONTH CALENDAR_YEAR_ QUARTER
Calendar Year and Half
NVARCSTR
12
yes
Calendar Year and Month
NVARCSTR
12
yes
Calendar Year and Quarter
NVARCSTR
12
yes
10
END_DATE
End Date for Fiscal Period
DATETIME
24
yes
11
FISC_HALF
Fiscal Half Year
NVARCSTR
yes
12
FISC_MONTH
Fiscal Month In SAP
NVARCSTR
yes
13
FISC_PERIOD
PK
Fiscal Period in SAP
INTEGER
no
14
FISC_QUARTER
Fiscal Quarter
NVARCSTR
yes
15
FISC_YEAR
PK
Fiscal Year in SAP
INTEGER
no
16
FISC_YEAR_HALF
Fiscal Year and Half
NVARCSTR
12
yes
52
17
FISC_YEAR_MONTH
Fiscal Year and Month
NVARCSTR
12
yes
18
FISC_YEAR_PERIOD
Fiscal Year and Period
NVARCSTR
12
yes
19
FISC_YEAR_QUARTE R
Fiscal Year and Quarter
NVARCSTR
12
yes
20
FISC_YR_VARIANT_ID PK
Fiscal Year Variant in SAP
NVARCSTR
no
21
Name of Fiscal Year Variant (Table T009T in SAP)
NVARCSTR
30
yes
22
LOAD_DATE
24
yes
23
LOAD_TIME
NVARCSTR
yes
24
SPECL_PERIOD_FLA G
Y = This is a special period in SAP, N = This is NVARCSTR NOT a special period in SAP
yes
25
START_DATE
Start Date for Fiscal Period
DATETIME
24
yes
53
FISC_PERIOD_STAGE
Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)
CALENDAR_DATE
PK
Calendar Date - range from 01-Jan-1990 through 31-Dec-2049
DATETIME
24
no
FISC_MONTH
Fiscal Month in range 1 to 12
NVARCSTR
yes
FISC_PERIOD
PK
Fiscal Period in range 1 to 16
INTEGER
no
FISC_YEAR
Fiscal Year in SAP
INTEGER
yes
Fiscal Year Variant in SAP
NVARCSTR
no
Name of Fiscal Year Variant (Table T009T in SAP)
NVARCSTR
30
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
REGISTRTN_PERIOD _COUNT SPECL_PERIOD_COU NT
Number of Regular Acctng Periods
INTEGER
yes
10
Number of Special Acctng Periods
INTEGER
yes
54
FUNCTIONAL_AREA
TFKB-FKBER - Functional Area reference table
FUNCTNL_AREA_DES CR FUNCTNL_AREA_FUL L_NAME
Functional Area Description
NVARCSTR
30
yes
ID and Description
NVARCSTR
120
yes
FUNCTNL_AREA_ID
PK
TFKB-FKBER - Functional Area Code
NVARCSTR
16
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
FUNCTIONAL_AREA_HIER
Functional Area Hierarchy
CHILD_DESCR
Child node description
NVARCSTR
64
yes
CHILD_ID
PK
Child node id
NVARCSTR
30
no
LEAF_FLAG
PK
Leaf node indicator (child node is leaf)
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Parent node description
NVARCSTR
64
yes
PARENT_ID
PK
Parent node id
NVARCSTR
30
no
ROOT_FLAG
PK
Root node indicator (parent node is root)
NVARCSTR
no
55
FUNCTIONAL_AREA_HIER_BAD
Functional Area Hierarchy - Invalid Records with Circular Dependency.
CHILD_DESCR
Child node description
NVARCSTR
64
yes
CHILD_ID
PK
Child node id
NVARCSTR
30
no
ETL_ERROR_ACTN
NVARCSTR
yes
ETL_ERROR_COLU MN
NVARCSTR
500
yes
LEAF_FLAG
PK
Leaf node indicator (child node is leaf)
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Parent node description
NVARCSTR
64
yes
PARENT_ID
PK
Parent node id
NVARCSTR
30
no
10
ROOT_FLAG
PK
Root node indicator (parent node is root)
NVARCSTR
no
56
FUNCTIONAL_AREA_HIER_HZ
Functional Area Hierarchy - Horizontal
FUNCTNL_AREA_ID
PK
Funct. Area ID (Current Leaf)
NVARCSTR
30
no
LEAF_LVL
Leaf Level
INTEGER
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
Funct. Area Level 0 Description
NVARCSTR
64
yes
LVL_00_FULL_NAME
Funct. Area Level 0 ID and Description
NVARCSTR
120
yes
LVL_00_ID
PK
Funct. Area Level 0 ID
NVARCSTR
30
no
LVL_01_DESCR
NVARCSTR
64
yes
LVL_01_FULL_NAME
NVARCSTR
120
yes
10
LVL_01_ID
PK
NVARCSTR
30
no
11
LVL_02_DESCR
NVARCSTR
64
yes
12
LVL_02_FULL_NAME
NVARCSTR
120
yes
13
LVL_02_ID
PK
NVARCSTR
30
no
14
LVL_03_DESCR
NVARCSTR
64
yes
15
LVL_03_FULL_NAME
NVARCSTR
120
yes
16
LVL_03_ID
PK
NVARCSTR
30
no
57
17
LVL_04_DESCR
NVARCSTR
64
yes
18
LVL_04_FULL_NAME
NVARCSTR
120
yes
19
LVL_04_ID
PK
NVARCSTR
30
no
20
LVL_05_DESCR
NVARCSTR
64
yes
21
LVL_05_FULL_NAME
NVARCSTR
120
yes
22
LVL_05_ID
PK
NVARCSTR
30
no
23
LVL_06_DESCR
NVARCSTR
64
yes
24
LVL_06_FULL_NAME
NVARCSTR
120
yes
25
LVL_06_ID
PK
NVARCSTR
30
no
26
LVL_07_DESCR
NVARCSTR
64
yes
27
LVL_07_FULL_NAME
NVARCSTR
120
yes
28
LVL_07_ID
PK
NVARCSTR
30
no
29
LVL_08_DESCR
NVARCSTR
64
yes
30
LVL_08_FULL_NAME
NVARCSTR
120
yes
31
LVL_08_ID
PK
NVARCSTR
30
no
32
LVL_09_DESCR
NVARCSTR
64
yes
33
LVL_09_FULL_NAME
NVARCSTR
120
yes
34
LVL_09_ID
PK
NVARCSTR
30
no
58
35
LVL_10_DESCR
NVARCSTR
64
yes
36
LVL_10_FULL_NAME
NVARCSTR
120
yes
37
LVL_10_ID
PK
NVARCSTR
30
no
FUNCTIONAL_AREA_HIER_VR
Functional Area Hierarchy - Vertical
CHILD_DESCR
Child Funct. Area Description
NVARCSTR
64
yes
CHILD_FULL_NAME
Child Funct. Area ID and Description
NVARCSTR
120
yes
CHILD_ID
PK
Child Funct. Area ID
NVARCSTR
30
no
DEPTH
Hierarchy Depth
INTEGER
yes
LEAF_FLAG
Leaf Flag
INTEGER
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Parent Funct. Area Description
NVARCSTR
64
yes
PARENT_FULL_NAME
Parent Funct. Area ID and Description
NVARCSTR
120
yes
10
PARENT_ID
PK
Parent Funct. Area ID
NVARCSTR
30
no
11
ROOT_FLAG
Root Flag
INTEGER
yes
59
FUNCTIONAL_LOCATION
Functional Location Master from IFLOT/ILOA
ABC_FLAG
ILOA - ABCKZ - ABC indicator for technical object IFLOT-IEQUI - Installation of equipment allowed at the functional location
NVARCSTR
yes
ALLOW_INSTALL_FLA G
NVARCSTR
yes
ASSET_MAIN_ID
NVARCSTR
12
yes
ASSET_SUB_ID
NVARCSTR
yes
BUS_AREA_DESCR
Lookup on TGSBT-GTEXT for Sales Org Descr NVARCSTR
30
yes
BUS_AREA_ID
NVARCSTR
yes
CHANGE_BY_LOGIN
IFLOT-AENAM - Name of the user who last changed the object
NVARCSTR
12
yes
CHANGE_DATE
IFLOT-AEDAT - Date on which the object was DATETIME last changed
24
yes
CMPNY_CODE_ID
NVARCSTR
yes
10
CMPNY_CODE_NAME
T001.BUTXT -Lookup on Company Code Name
NVARCSTR
25
yes
11
COST_CNTR_ID
NVARCSTR
10
yes
12
COST_CNTR_NAME
CSKT.KTEXT - Lookup on Cost Center Name
NVARCSTR
40
yes
13
CREATE_BY_LOGIN
IFLOT-ERNAM - Name of the user who created the object
NVARCSTR
12
yes
14
CREATE_DATE
IFLOT-ERDAT - Date on which the object was DATETIME created
24
yes
15
CTRL_AREA_ID
NVARCSTR
yes
16
CTRL_AREA_NAME
Lookup on TKA01 for controlling area name
NVARCSTR
25
yes
60
Appendix Table Column Details Total number of days since the original startup DECIMAL as of LOAD_DATE (calcualted)
17
DAYS_IN_OPERATN
48
28
yes
18
DISTRIBTN_CHANNEL _DESCR DISTRIBTN_CHANNEL _ID
40
yes
19
ILOA.VTWEG - Distribution channel
NVARCSTR
yes
20
DIVISION_DESCR
40
yes
21
DIVISION_ID
ILOA.SPART - Division
NVARCSTR
yes
22
FUNCTNL_LOCATN_C ATEG_DESCR FUNCTNL_LOCATN_C ATEG_ID FUNCTNL_LOCATN_D ESCR FUNCTNL_LOCATN_F ULL_NAME FUNCTNL_LOCATN_I D FUNCTNL_LOCATN_I D_PAR FUNCTNL_LOCATN_I D_REF
T370F_T-TYPTX (lookup) - Functional location NVARCSTR description
30
yes
23
IFLOT-FLTYP - Functional location category
NVARCSTR
yes
24
IFLOTX-PLTXT (lookup)
NVARCSTR
40
yes
25
IFLOT-TPLNR - Functional location and IFLOTX-PLTXT (lookup)
NVARCSTR
100
yes
26
PK
IFLOT-TPLNR - Functional location
NVARCSTR
30
no
27
IFLOT-TPLMA - Superior functional location
NVARCSTR
30
yes
28
IFLOT-TRPNR - Reference functional location NVARCSTR
30
yes
29
LOAD_DATE
DATETIME
24
yes
30
LOAD_TIME
NVARCSTR
yes
31
LOCATN_DESCR
T499S-KTEXT (lookup) - Text (40 characters) NVARCSTR
40
yes
32
LOCATN_ID
10
yes
33
OBJ_ID
IFLOT-OBJNR - Object number
NVARCSTR
22
yes
34
PERSON_FULLNAME_ RESP
PA0002.NACHN - Personnel Last Name + PA0002.VORNA - Personnel First Name
NVARCSTR
85
yes
61
35
PERSON_ID_RESP
NVARCSTR
12
yes
36
PLANNG_GRP_ID
IFLOT.INGRP Maintenance planner group
NVARCSTR
yes
37
PLANNG_GRP_NAME
T024i-INNAM - Lookup on Name of the maintenance planning group
NVARCSTR
18
yes
38
PLANT_ID
NVARCSTR
yes
39
PLANT_ID_PLAN
NVARCSTR
yes
40
PLANT_NAME
T001W.NAME1 Name - Lookup on Plant name T001W.NAME1 Name - Lookup on Plant name for Planning Plant PRPS.POST1 - Project Element Short description (1st text line) PRPS.POSID - Project Element (WBS) External ID
NVARCSTR
30
yes
41
PLANT_NAME_PLAN
NVARCSTR
30
yes
42
PROJ_ELEM_DESCR
NVARCSTR
40
yes
43
PROJ_ELEM_ID
NVARCSTR
24
yes
44
ROOM
ILOA-MSGRP - Plant Room
NVARCSTR
yes
45
SALES_ORG_DESCR
Lookup on TVKOT-VTEXT for Sales Org Descr NVARCSTR
60
yes
46
SALES_ORG_ID
ILOA.VKORG Sales organization
NVARCSTR
yes
47
SECTION_ID
ILOA-BEBER - Plant section
NVARCSTR
yes
48
SECTION_PERSON_R ESP
T357-FING (lookup) - Person responsible for company area T357-TELE (lookup) - Phone number of person responsible for company area
NVARCSTR
14
yes
49
SECTION_PHONE
NVARCSTR
12
yes
50
SINGLE_INSTALL_FLA G
IFLOT-EINZL - Single equipment installation at NVARCSTR functional location IFLOT-DATAB - Start-up date of functional location
yes
51
STARTUP_DATE
DATETIME
24
yes
62
FUNCTIONAL_LOCATION_CHAR_FACT
Functional Location Characteristic details from AUSTP/CABN/TCLA
BUS_AREA_ID
PK
NVARCSTR
yes
NVARCSTR
30
yes
NVARCSTR
yes
NVARCSTR
30
yes
30
yes
CHARACTSTC_ID
PK
NVARCSTR
10
no
CHARACTSTC_NAME
30
yes
CHARACTSTC_VALUE
NVARCSTR
30
yes
CLASS_TYPE_ID
PK
NVARCSTR
no
10
CMPNY_CODE_ID
PK
NVARCSTR
yes
11
COST_CNTR_ID
PK
NVARCSTR
10
yes
12
CTRL_AREA_ID
PK
NVARCSTR
yes
13
DAYS_DIFF
Calculated date difference for Date-related caracteristics
DECIMAL
48
22
yes
14
FUNCTNL_LOCATN_I D
PK
NVARCSTR
30
no
15
LOAD_DATE
DATETIME
24
yes
16
LOAD_TIME
NVARCSTR
yes
63
17
LOCATN_ID
PK
10
yes
18
PERSON_ID_RESP
PK
NVARCSTR
12
yes
19
PLANNG_GRP_ID
PK
IFLOT.INGRP Maintenance planner group
NVARCSTR
yes
20
PLANT_ID
PK
NVARCSTR
yes
21
PLANT_ID_PLAN
NVARCSTR
yes
22
UOM_ID_VALUE
PK
NVARCSTR
yes
23
VALID_FROM_DATE
DATETIME
24
yes
24
VALID_FROM_NUMBE R
DECIMAL
48
28
10
yes
25
VALID_FROM_VALUE
DECIMAL
48
28
10
yes
26
VALID_TO_DATE
AUSP.ATFLB - Derive Date To and Time To bucket
DATETIME
24
yes
27
VALID_TO_NUMBER
DECIMAL
48
28
10
yes
28
VALID_TO_VALUE
DECIMAL
48
28
10
yes
29
VALUE_OPERATOR
NVARCSTR
yes
30
VALUE_PRECISION
NVARCSTR
yes
31
VALUE_SCALE
NVARCSTR
yes
64
FUNCTIONAL_LOCATION_HIER
Parent/Child relationship between Functional Locations (from IFLOT/ILOA)
CHILD_CATEG_DESC R
30
yes
CHILD_CATEG_ID
NVARCSTR
yes
CHILD_DESCR
IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description PK IFLOT-TPLMA - functional location
NVARCSTR
40
yes
CHILD_FULL_NAME
NVARCSTR
55
yes
CHILD_ID
NVARCSTR
30
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_CATEG_DES CR
30
yes
PARENT_CATEG_ID
NVARCSTR
yes
10
PARENT_DESCR
IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description PK IFLOT-TPLMA - Superior functional location
NVARCSTR
40
yes
11
PARENT_FULL_NAME
NVARCSTR
75
yes
12
PARENT_ID
NVARCSTR
30
no
65
FUNCTIONAL_LOCATION_HIER_HZ
Horizontal flattening of Equipment and Classification hierarchy relationships
FUNCTNL_LOCATN_I D
PK
IFLOT-TPLMA - functional location
NVARCSTR
30
no
LEAF_LVL
Leaf level
DECIMAL
48
28
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Superior functional location
NVARCSTR
40
yes
LVL_00_FULL_NAME
NVARCSTR
75
yes
LVL_00_ID
NVARCSTR
30
yes
LVL_01_DESCR
IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - functional location
NVARCSTR
40
yes
LVL_01_FULL_NAME
NVARCSTR
75
yes
10
LVL_01_ID
NVARCSTR
30
yes
11
LVL_02_DESCR
NVARCSTR
40
yes
12
LVL_02_FULL_NAME
NVARCSTR
75
yes
13
LVL_02_ID
NVARCSTR
30
yes
14
LVL_03_DESCR
NVARCSTR
40
yes
15
LVL_03_FULL_NAME
NVARCSTR
75
yes
16
LVL_03_ID
NVARCSTR
30
yes
66
Appendix Table Column Details IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - functional location
17
LVL_04_DESCR
NVARCSTR
40
yes
18
LVL_04_FULL_NAME
NVARCSTR
75
yes
19
LVL_04_ID
NVARCSTR
30
yes
20
LVL_05_DESCR
NVARCSTR
40
yes
21
LVL_05_FULL_NAME
NVARCSTR
65
yes
22
LVL_05_ID
NVARCSTR
30
yes
67
FUNCTIONAL_LOCATION_HIER_VR
Vertical flattening of Equipment and Classification hierarchy relationships
CHILD_DESCR
IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description PK IFLOT-TPLMA - functional location
NVARCSTR
40
yes
CHILD_FULL_NAME
NVARCSTR
55
yes
CHILD_ID
NVARCSTR
30
no
DEPTH
Depth of the decendent
DECIMAL
48
28
yes
LEAF_FLAG
Leaf flag (1 - means this is a leaf, 0 - means it is not a leaf)
DECIMAL
48
28
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
IFLOTX-PLTXT (lookup) - Func Location Description IFLOT-TPLMA - Functional location+IFLOTX-PLTXT (lookup) - Func Location Description PK IFLOT-TPLMA - Superior functional location
NVARCSTR
40
yes
PARENT_FULL_NAME
NVARCSTR
75
yes
10
PARENT_ID
NVARCSTR
30
no
11
ROOT_FLAG
Root flag (1 - means this is a root, 0 - means it DECIMAL is not a root)
48
28
yes
68
INTERNAL_ORDER
AUFK - Internal Order Master
ALLOCTN_GRP_CO DE
Allocation Group Code
NVARCSTR
yes
APPLICTN_DATE
AUFK-USER5
DATETIME
24
yes
BUS_AREA_ID
AUFK-GSBER
NVARCSTR
yes
BUS_AREA_NAME
Business area description
NVARCSTR
30
yes
CHANGE_DATE
AUFK-AEDAT
DATETIME
24
yes
CLOSE_DATE
AUFK-IDAT3
DATETIME
24
yes
CMPNY_CODE_ID
AUFK-BUKRS
NVARCSTR
yes
CMPNY_CODE_NAME
Name of the company code or company
NVARCSTR
25
yes
COMPLT_DATE
AUFK-IDAT2
DATETIME
24
yes
10
COST_CNTR_ID_ALL OCTN COST_CNTR_ID_RES P COST_CNTR_ID_RQS T COST_COLLECTR_KE Y COST_ELEM_ID_SET TLMNT
AUFK-KOSTL
NVARCSTR
10
yes
11
AUFK-KOSTV
NVARCSTR
10
yes
12
AUFK-AKSTL
NVARCSTR
10
yes
13
AUFK-CCKEY
NVARCSTR
23
yes
14
AUFK-KSTAR
NVARCSTR
10
yes
15
CREATE_DATE
AUFK-ERDAT
DATETIME
24
yes
16
CTRL_AREA_ID
AUFK-KOKRS
NVARCSTR
yes
69
17
CTRL_AREA_NAME
Name of the controlling area
NVARCSTR
25
yes
18
CURR_ID
AUFK-WAERS
NVARCSTR
yes
19
DELETE_CODE
AUFK-LOEKZ
NVARCSTR
yes
20
DEPARTMENT
AUFK-USER6
NVARCSTR
15
yes
21
DOC_CATEG_DESCR
DD07T - DDTEXT(lookup) - Order category description
NVARCSTR
60
yes
22
DOC_CATEG_ID
AUFK-AUTYP
NVARCSTR
yes
23
DOC_TYPE_DESCR
T003P-TXT(lookup) - Short text
NVARCSTR
40
yes
24
DOC_TYPE_ID
AUFK-AUART
NVARCSTR
yes
25
EQUITY_TYPE_CODE
AUFK-ETYPE
NVARCSTR
yes
26
EST_TRX_COST_ORD ER EXTERNAL_ORDER _NUM GL_ACCT_ID_ALLOCT N
AUFK-USER4
DECIMAL
48
11
yes
27
AUFK-AUFEX
NVARCSTR
20
yes
28
AUFK-SAKNR
NVARCSTR
10
yes
29
INTERNAL_ORDER_ID PK
AUFK-AUFNR
NVARCSTR
12
no
30
INTERNAL_ORDER_ID _REF INTERNAL_ORDER_ID _STATS JOINT_VENTURE_CO DE
AUFK-REFNR
NVARCSTR
12
yes
31
AUFK-ASTNR
NVARCSTR
yes
32
AUFK-VNAME
NVARCSTR
yes
33
LOAD_DATE
24
yes
34
LOAD_TIME
NVARCSTR
yes
70
35
LOCATN_ID
AUFK-STORT
NVARCSTR
10
yes
36
OBJ_ID
AUFK-OBJNR
NVARCSTR
22
yes
37
ORDER_DESCR
AUFK-KTEXT
NVARCSTR
40
yes
38
ORDER_STATUS_ID
AUFK-ASTKZ
NVARCSTR
yes
39
OVERHEAD_CODE
AUFK-ZSCHL
NVARCSTR
yes
40
PLANNED_CLOSE_DA TE PLANNED_COMPLT _DATE
AUFK-PDAT3
DATETIME
24
yes
41
AUFK-PDAT2
DATETIME
24
yes
42
PLANNED_REL_DATE
AUFK-PDAT1
DATETIME
24
yes
43
PLANT_ID
AUFK-WERKS
NVARCSTR
yes
44
PLANT_ID_LOCATN
AUFK-SOWRK
NVARCSTR
yes
45
PLANT_NAME
Name
NVARCSTR
30
yes
46
PROFIT_CNTR_ID
AUFK-PRCTR
NVARCSTR
10
yes
47
PROJ_ELEM_DESCR
PS: Short description (1st text line)
NVARCSTR
40
yes
48
PROJ_ELEM_ID
AUFK-PSPEL lookup to PRPS.POSID - WBS element External ID
NVARCSTR
24
yes
49
RECOVERY_CODE
AUFK-RECID
NVARCSTR
yes
50
RELEASE_DATE
AUFK-IDAT1
DATETIME
24
yes
51
RESP_PERSON
AUFK-USER2
NVARCSTR
20
yes
52
SALES_LINE_ITEM_ID
AUFK-KDPOS
NVARCSTR
yes
71
53
SALES_ORDER_ID
AUFK-KDAUF
NVARCSTR
10
yes
54
STATUS_UPDT_DATE
AUFK-STDAT
DATETIME
24
yes
55
WORK_BEGIN_DATE
AUFK-USER7
DATETIME
24
yes
56
WORK_END_DATE
AUFK-USER8
DATETIME
24
yes
INTERNAL_ORDER_HIER
CCSS-AUFNR - Internal Order Hierarchy- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
Internal Order Child Node Description
NVARCSTR
64
yes
CHILD_ID
PK
Internal Order Child Node ID
NVARCSTR
12
no
LEAF_FLAG
PK
Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Internal Order Parent Node Descritpion
NVARCSTR
64
yes
PARENT_ID
PK
Internal Order Parent Node ID
NVARCSTR
12
no
ROOT_FLAG
PK
Is Root
NVARCSTR
no
72
INTERNAL_ORDER_HIER_BAD
CCSS-AUFNR Internal Order Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
NVARCSTR
64
yes
CHILD_ID
PK
NVARCSTR
12
no
ETL_ERROR_ACTN
NVARCSTR
yes
ETL_ERROR_COLU MN
NVARCSTR
500
yes
LEAF_FLAG
PK
Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Internal Order Parent Node Descritpion
NVARCSTR
64
yes
PARENT_ID
PK
NVARCSTR
12
no
10
ROOT_FLAG
PK
Is Root
NVARCSTR
no
73
INTERNAL_ORDER_HIER_HZ
CCSS-AUFNR - Internal Order hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP
Internal order current node ID
NVARCSTR
12
no
LEAF_LVL
Current Node level depth
DECIMAL
48
28
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
Internal Order Root node Description
NVARCSTR
64
yes
LVL_00_FULL_NAME
Internal Order Number and Descritpion for Level 0
NVARCSTR
120
yes
LVL_00_ID
PK
Internal Order Root node id
NVARCSTR
12
no
LVL_01_DESCR
Internal Order Level 1node Descritpion
NVARCSTR
64
yes
LVL_01_FULL_NAME
NVARCSTR
120
yes
10
LVL_01_ID
PK
Internal Order Level 1node ID
NVARCSTR
12
no
11
LVL_02_DESCR
Internal Order Level 2 node Descritpion
NVARCSTR
64
yes
12
LVL_02_FULL_NAME
NVARCSTR
120
yes
13
LVL_02_ID
PK
Internal Order Level 2 node ID
NVARCSTR
12
no
14
LVL_03_DESCR
NVARCSTR
64
yes
15
LVL_03_FULL_NAME
NVARCSTR
120
yes
16
LVL_03_ID
PK
NVARCSTR
12
no
74
17
LVL_04_DESCR
NVARCSTR
64
yes
18
LVL_04_FULL_NAME
NVARCSTR
120
yes
19
LVL_04_ID
PK
NVARCSTR
12
no
INTERNAL_ORDER_HIER_VR
CCSS-AUFNR - Internal Order hierarchy flattenned vertically - cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
NVARCSTR
64
yes
CHILD_FULL_NAME
Internal Order Number and Description Child Node)
NVARCSTR
120
yes
CHILD_ID
PK
NVARCSTR
12
no
DEPTH
Internal Order Child depth level
DECIMAL
48
28
yes
LEAF_FLAG
Node Is leaf
DECIMAL
48
28
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Internal Order Parent Node Description
NVARCSTR
64
yes
PARENT_FULL_NAME
Internal Order Number and Description (Parent NVARCSTR Node)
120
yes
10
PARENT_ID
PK
NVARCSTR
12
no
11
ROOT_FLAG
Node Is root
DECIMAL
48
28
yes
75
INTERNAL_ORDER_STATUS
Internal Order status name and descritpion from TKO04
DOC_TYPE_DESCR
T003P.TXT -Short text
NVARCSTR
40
yes
DOC_TYPE_ID
PK
TKO04.ART -Order type
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
ORDER_STATUS_D ESCR
TKO04.TXT -Text (40 characters) for status
NVARCSTR
40
yes
ORDER_STATUS_ID
PK
TKO04.ASTNR -Order status
NVARCSTR
no
MAINTENANCE_ACTIVITY_TYPE
Maintenance Activity Type attributes from T353I/T353I_T
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MAINT_ACTIVITY_DE SCR MAINT_ACTIVITY_TYP PK E_ID
T353I_T-ILATX - Description of maintenance activity type
NVARCSTR
30
yes
T353I_T-ILART - Maintenance activity type
NVARCSTR
no
76
MAINTENANCE_PRIORITY
Attritues from T356, T356T, T356A_T (for service orders and notifications)
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
NUM_DAYS_END
T356.TAGEN - Relative End Date for Task/Notification in Days T356.TAGBN -Relative Start Date for Task/Notification in Days
INTEGER
yes
NUM_DAYS_START
INTEGER
yes
PRIORITY_DESCR
T356_T.PRIOKX - Priority text
NVARCSTR
20
yes
PRIORITY_ID
PK
T356.PRIOK -Priority
NVARCSTR
no
PRIORITY_TYPE_DES CR
T356A_T.ARTPRX -Priority Type Text
NVARCSTR
20
yes
PRIORITY_TYPE_ID
PK
T356.ARTPR -Priority Type
NVARCSTR
no
UOM_ID_END
T356.EHTEN -Relative End Date Unit
NVARCSTR
yes
10
UOM_ID_START
T356.EHTBG -Relative Start Date Unit
NVARCSTR
yes
77
MALFUNCTION_CAUSE
One of 3 pre-defined notification catalog objects - Malfunction Cause
CAUSE_DESCR
QPCT-KURZTEXT - Code short text for Cause NVARCSTR
40
yes
CAUSE_GRP_DESCR
QPGT-KURZTEXT (lookup) - Group short text- NVARCSTR Cause group QPCT-CODEGRUPPE - Mulfuction cause Code group
40
yes
CAUSE_GRP_ID
PK
NVARCSTR
no
CAUSE_ID
PK
QPCT-CODE - Code for Cause
NVARCSTR
no
LOAD_DATE
Dateand time loaded into Rapid Mart
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MALFUNCTION_DAMAGE
One of 3 pre-defined notification catalog objects - Malfunction Damage
DAMAGE_DESCR
QPCT-KURZTEXT - Code short text for Damage
NVARCSTR
40
yes
DAMAGE_GRP_DES CR
QPGT-KURZTEXT (lookup) - Group short text- NVARCSTR Damage group QPCT-CODEGRUPPE - Mulfuction Damage Code group
40
yes
DAMAGE_GRP_ID
PK
NVARCSTR
no
DAMAGE_ID
PK
QPCT-CODE - Code for Damage
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
78
MALFUNCTION_EFFECT
Description of malfunction effects from T357A_T
EFFECT_DESCR
T357A_T.AUSWKT - Text - Effect on works
NVARCSTR
40
yes
EFFECT_ID
PK
T357A_T.AUSWK - Effect on operation
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MALFUNCTION_OBJ_PART
One of 3 pre-defined notification catalog objects - Mulfunctioning Object Part
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
OBJ_PART_DESCR
QPCT-KURZTEXT - Code short text for Object NVARCSTR Part QPGT-KURZTEXT (lookup) - Group short text- NVARCSTR Object Part group QPCT-CODEGRUPPE - Mulfuction Object Part Code group
40
yes
OBJ_PART_GRP_DES CR
40
yes
OBJ_PART_GRP_ID
PK
NVARCSTR
no
OBJ_PART_ID
PK
QPCT-CODE - Code for Obect Part
NVARCSTR
no
79
MATERIAL
MARA - Material Master
BATCH_MGMT_FLAG
XCHPF Batch management requirement indicator
NVARCSTR
yes
CREATE_DATE
ERSDA Date of creation
DATETIME
24
yes
DELETE_CODE
MARA-LVORM - Deletion flag for all material data (central)
NVARCSTR
yes
DELETE_DATE
LIQDT Deletion date
DATETIME
24
yes
DIVISION_DESCR
TSPAT.VTEXT Division Description
NVARCSTR
20
yes
DIVISION_ID
MARA.SPART Division
NVARCSTR
yes
INDUSTRY_SECTOR_I D INDUSTRY_SECT_DE SCR
MARA.MBRSH Industry Sector ID
NVARCSTR
yes
Lookup description of MARA.MBRSH Industry sector
NVARCSTR
25
yes
LOAD_DATE
24
yes
10
LOAD_TIME
NVARCSTR
yes
11
LOW_LVL_CODE
MARA.DISST - Low level code
NVARCSTR
yes
12
MATERIAL_ID
PK
MATNR Material number
NVARCSTR
18
no
13
MIN_REM_SHELF_LIF E
MARA.MHDRZ Minimum remaining shelf life
INTEGER
yes
14
MODIFIED_DATE
MARA.LAEDA Date of last change
DATETIME
24
yes
15
MTRL_CATEG_DES CR
Category Description
NVARCSTR
60
yes
16
MTRL_CATEG_ID
MARA.ATTYP Material category
NVARCSTR
yes
80
17
MTRL_DESCR
MAKTX Material description
NVARCSTR
40
yes
18
MTRL_FULL_NAME
Material ID and Material Description
NVARCSTR
64
yes
19
MTRL_GRP_DESCR
WGBEZ Description of material group
NVARCSTR
20
yes
20
MTRL_GRP_ID
MATKL Material group
NVARCSTR
yes
21
MTRL_ID_MANUFCTR
MARA.MFRPN - Manfuacturer Part (Material) Number
NVARCSTR
40
yes
22
MTRL_TYPE_DESCR
Lookup description of MARA.MTART in T134T NVARCSTR
25
yes
23
MTRL_TYPE_ID
MTART Material type
NVARCSTR
yes
24
PROD_HIER_ID
PK
PRDHA Product hierarchy
NVARCSTR
18
yes
25
PURCH_STATUS_C ODE
General material status: Purchasing
NVARCSTR
yes
26
REVISION_LVL
Lookup AEOI.REVLV - Material revision level
NVARCSTR
yes
27
SALES_STATUS_COD E TRANSPORT_GRP_ CODE
MARA.MSTAV General material status: sales
NVARCSTR
yes
28
MARA.TRAGR Transportation group
NVARCSTR
yes
29
TTL_SHELF_LIFE
MARA.MHDHB Total shelf life in days
INTEGER
yes
30
UOM_ID_BASE
MEINS Base unit of measure
NVARCSTR
yes
31
UOM_ID_ORDER
MARA.BSTME Order unit (purchasing)
NVARCSTR
yes
32
UOM_ID_VOLUME
MARA.VOLEH Volume unit
NVARCSTR
yes
33
UOM_ID_WEIGHT
MARA.GEWEI Unit of weight
NVARCSTR
yes
34
VALID_FROM_DATE
MARA.DATAB Date valid from
DATETIME
24
yes
81
35
VOLUME
MARA.VOLUM Volume
DECIMAL
48
13
yes
36
WEIGHT
MARA.NTGEW Net weight
DECIMAL
48
13
yes
82
MATERIAL_BY_PLANT
MARA and MARC Tables - Plant Level Material attributes
ABC_CATEG_DESCR
TMABCT.TMABC - lookup on ABC indicator descritpion
NVARCSTR
30
yes
ABC_CATEG_ID
MARC.MAABC ABC indicator
NVARCSTR
yes
BASE_TO_PRODUC TN_MULTIPLR
Lookup MARM.UMREZ Factor to convert from BASE UOM to PROD UOM. (PROD_QTY = INTEGER MENGE / UMREZ) Lookup MARC.XCHAR Batch management indicator (internal) MARC.XCHPF Batch management requirement indicator NVARCSTR
yes
BATCH_MGMT_FLAG
yes
BATCH_MGMT_REQ _FLAG
NVARCSTR
yes
BULK_MTRL_FLAG
MARC.SCHGT Indicator: bulk material
NVARCSTR
yes
COUNTRY_ID_ORIGIN
MARC.HERKL Materials country of origin
NVARCSTR
yes
COUNTRY_NAME_O RIGIN
Lookup description onT005T.LANDX for Country name
NVARCSTR
15
yes
DAYS_PLAN_DELIV
MARC.PLIFZ - Planned delivery time in days MARC.WEBAZ - Planned goods receipt processing time in days - includes inspection time MARC.WZEIT - Total replenishment lead time in days - in house production time and/or delivery lead tim MARC.DZEIT - In-house production time
INTEGER
yes
10
DAYS_PLAN_GR
INTEGER
yes
11
DAYS_REPLENISH
INTEGER
yes
12
DAYS_TO_PRODUCE
INTEGER
yes
13
DELETE_FLAG
MARC.LVORM - Plant level material deletion indicator
NVARCSTR
yes
14
DIVISION_DESCR
TSPAT.VTEXT Division Description
NVARCSTR
20
yes
15
DIVISION_ID
MARA.SPART Division
NVARCSTR
yes
16
INDUSTRY_SECTOR_ DESCR
Lookup description of MARA.MBRSH Industry sector
NVARCSTR
25
yes
83
Appendix Table Column Details INDUSTRY_SECTOR_I D
17
MARA.MBRSH Industry Sector ID
NVARCSTR
yes
18
LOAD_DATE
Date and time loaded into RapidMart
DATETIME
24
yes
19
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
yes
20
MATERIAL_ID
PK
MARC.MATNR Material number
NVARCSTR
18
no
21
MRP_CTRLLER_ID
MARC.DISPO MRP controller
NVARCSTR
yes
22
MRP_CTRLLER_NA ME
T024D.DSNAM - Name of MRP controller lookup T438T.DIBEZ -Long MRP Type Description from T438T
NVARCSTR
18
yes
23
MRP_TYPE_DESCR
NVARCSTR
30
yes
24
MRP_TYPE_ID
MARC.DISMM MRP type code
NVARCSTR
yes
25
MTRL_CATEG_DES CR
lookup on ATTYP domain in DD07T
NVARCSTR
60
yes
26
MTRL_CATEG_ID
MARA.ATTYP Material category
NVARCSTR
yes
27
MTRL_DESCR
MAKT.MAKTX -Material description
NVARCSTR
40
yes
28
MTRL_FULL_NAME
Material ID and Material Description
NVARCSTR
64
yes
29
MTRL_GRP_DESCR
WGBEZ Description of material group
NVARCSTR
20
yes
30
MTRL_GRP_ID
MATKL Material group
NVARCSTR
yes
31
MTRL_TYPE_DESCR
Lookup description of MARA.MTART in T134T NVARCSTR
25
yes
32
MTRL_TYPE_ID
MTART Material type
NVARCSTR
yes
33
PLANT_FULL_NAME
Plant ID and Plant Name
NVARCSTR
40
yes
34
PLANT_ID
PK
MARC.WERKS Plant
NVARCSTR
no
84
35
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
yes
36
PROCUREMNT_TYP E_DESCR PROCUREMNT_TYP E_ID
Lookup DD07T - Procurement type - BESKZ domain
NVARCSTR
60
yes
37
MARC.BESKZ - Procurement type code
NVARCSTR
20
yes
38
PROFIT_CNTR_ID
MARC.PRCTR Profit center
NVARCSTR
10
yes
39
PURCH_GRP_DESCR
Lookup description of T024.EKNAM - Purchase NVARCSTR Group Name
30
yes
40
PURCH_GRP_ID
MARC.EKGRP Purchasing group
NVARCSTR
yes
41
QTY_REORDER_POIN T
MARC.MINBE Reorder point
DECIMAL
48
13
yes
42
QTY_SAFETY_STOCK
MARC.EISBE Safety stock
DECIMAL
48
13
yes
43
QUALITY_INSPECT_F LAG SPECL_PROCUREM NT_TYPE_DESCR SPECL_PROCUREM NT_TYPE_ID
MARC.INSMK - Quality inspection indicator - X NVARCSTR is yes Lookup description of MARC.SOBSL in T460T- NVARCSTR Special procurement type
yes
44
30
yes
45
MARC.SOBSL - Special procurement type
NVARCSTR
yes
46
SUPPLY_SRC_DESCR
Lookup description on TMBWT.BWSCB for supply source description
NVARCSTR
40
yes
47
SUPPLY_SRC_ID
MARC.BWSCL Source of supply IS-R
NVARCSTR
yes
48
UOM_CODE_BASE
Lookup MARC.AUSME in T006A to get Base Unit External Code
NVARCSTR
yes
49
UOM_CODE_ISSUE
Lookup MARC.AUSME in T006A to get Unit of NVARCSTR Issue Long Description Lookup MARC.FRTME in T006A to get Production UOM External code
yes
50
UOM_CODE_PROD
NVARCSTR
yes
51
UOM_ID_BASE
MEINS Base unit of measure
NVARCSTR
yes
52
UOM_ID_ISSUE
MARC.AUSME - Unit of measure for goods issue
NVARCSTR
yes
85
53
UOM_ID_PROD
MARC.FRTME Production unit of measure
NVARCSTR
yes
86
MTBR_MTTR_FACT
Value added table to calculate MTTR (mean time to repare), MTBR (mean time between repairs)
BUS_AREA_ID
PK
NVARCSTR
yes
CMPNY_CODE_ID
PK
T001K.BURKS - lookup on Company Code ID
NVARCSTR
yes
COMPLT_DATE
QMEL-QMDAB - Date for completion of notification + QMEL-QMZAB - Completion time DATETIME of notification PK ILOA-KOSTL (lookup) - Cost Center NVARCSTR
24
yes
COST_CNTR_ID
10
yes
CTRL_AREA_ID
PK
ILOA-KOKRS (lookup) - Controlling Area
NVARCSTR
yes
DAYS_DOWNTIME
Calcualted Days of downtime (as Malf end malf start)
DECIMAL
48
22
yes
DAYS_UPTIME
Calulcated Days of uptime: Prev Malf end date DECIMAL - malf start date
48
22
yes
DOC_CATEG_ID
TQ80.QMTYP - Notification Category ID
NVARCSTR
yes
DOC_TYPE_ID
PK
QMEL-QMART - Notification type
NVARCSTR
yes
10
EFFECT_ID
PK
QMIH.AUSWK - Effect on operation
NVARCSTR
yes
11
EQUIPMNT_ID
PK
QMIH-EQUNR - Equipment number
NVARCSTR
18
yes
12
FUNCTNL_LOCATN_I D
PK
ILOA-TPLNR (lookup) - Functional location
NVARCSTR
30
yes
13
HOURS_DOWNTIME
Calcualted hours of downtime (as Malf end malf start)
DECIMAL
48
22
yes
14
HOURS_UPTIME
Calulcated hours of uptime: Prev Malf end date DECIMAL - malf start date
48
22
yes
15
QMEL-AUFNR - Order Number
NVARCSTR
12
yes
16
LOAD_DATE
DATETIME
24
yes
87
17
LOAD_TIME
NVARCSTR
yes
18
MALFNCTN_END_DAT E MALFNCTN_END_DAT E_PREV MALFNCTN_START_D ATE MALFNCTN_START_D ATE_NEXT
QMIH-AUSBS - End of malfunction (date) + QMIH-AUZTV - Start of malfunction (time) Date and time of the previous malfunction end date (calculated as lookup) QMIH-AUSVN - Start of malfunction (date) + QMIH-AUSBS - End of malfunction (date)
DATETIME
24
yes
19
DATETIME
24
yes
20
DATETIME
24
yes
21
Date and time of the next malfunction start date DATETIME (calculated as lookup)
24
yes
22
MATERIAL_ID
QMFE.MATNR - Material
NVARCSTR
18
yes
23
MINS_DOWNTIME
Calcualted minutes of downtime (as Malf end - DECIMAL malf start) Calulcated mins of uptime: Prev Malf end date - malf start date QMEL-QMDAT - Date of notification (without timestamp)
48
22
yes
24
MINS_UPTIME
DECIMAL
48
22
yes
25
NOTIFICTN_DATE
PK
DATETIME
24
yes
26
NOTIFICTN_DATETIM E
QMEL.QMDAT and QMEL.MZEIT - Notification DATETIME Date and Time
24
yes
27
NOTIFICTN_DESCR
QMEL-QMTXT - Short text
NVARCSTR
40
yes
28
NOTIFICTN_ID
QMIH-QMNUM - Notification number
NVARCSTR
12
yes
29
OBJ_FLAG
EQ for Equipment, FL for Functional Location
NVARCSTR
yes
30
OBJ_ID
PK
Functional Location of Equipment ID
NVARCSTR
30
no
31
PERSON_ID_RESP
PK
IHPA-PARNR - Person responsible ID
NVARCSTR
12
yes
32
PLANNG_GRP_ID
PK
QMIH-INGRP - Maintenance planner group
NVARCSTR
yes
33
PLANT_ID
PK
ILOA-SWERK (lookup) - Maintenance Plant
NVARCSTR
no
34
PLANT_ID_PLAN
QMIH-IWERK - Planning plant
NVARCSTR
yes
88
35
PLANT_ID_WRKCNTR
CRHD-WERKS (lookup) - Work Center Plant
NVARCSTR
yes
36
PRIORITY_ID
PK
QMEL.PRIOK - Priority
NVARCSTR
yes
37
PRIORITY_TYPE_ID
PK
QMEL.ARTPR - Priority type
NVARCSTR
yes
38
SEQ_NUM
PK
Group Sequential number (generated)
DECIMAL
48
28
no
39
STARTUP_DATE
Object startup date and time
DATETIME
24
yes
40
WORK_CNTR_ID
PK
CRHD-ARBPL (lookup) - Work Center unique name
NVARCSTR
yes
89
MTBR_MTTR_STAGE
Staging table for Uptime/Downtime measure calculations
BUS_AREA_ID
NVARCSTR
yes
CMPNY_CODE_ID
NVARCSTR
yes
COMPLT_DATE
QMEL-QMDAB - Date for completion of notification + QMEL-QMZAB - Completion time DATETIME of notification ILOA-KOSTL (lookup) - Cost Center NVARCSTR
24
yes
COST_CNTR_ID
10
yes
CTRL_AREA_ID
NVARCSTR
yes
DOC_CATEG_ID
NVARCSTR
yes
DOC_TYPE_ID
NVARCSTR
yes
EFFECT_ID
NVARCSTR
yes
INTERNAL_ORDER_ID
NVARCSTR
12
yes
10
LOAD_DATE
DATETIME
24
yes
11
LOAD_TIME
NVARCSTR
yes
12
MALFNCTN_END_DAT E MALFNCTN_START_D ATE
QMIH-AUSBS - End of malfunction (date) + QMIH-AUZTV - Start of malfunction (time) QMIH-AUSVN - Start of malfunction (date) + QMIH-AUSBS - End of malfunction (date)
DATETIME
24
yes
13
DATETIME
24
yes
14
MATERIAL_ID
NVARCSTR
18
yes
15
NOTIFICTN_DATE
QMEL-QMDAT - Date of notification (No timestamp) QMEL-QMDAT - Date of notification + QMEL-MZEIT - Notification time
DATETIME
24
yes
16
NOTIFICTN_DATETIM E
DATETIME
24
yes
90
17
NOTIFICTN_DESCR
NVARCSTR
40
yes
18
NOTIFICTN_ID
NVARCSTR
12
yes
19
OBJ_FLAG
EQ for Equipment, FL for Functional Location
NVARCSTR
yes
20
OBJ_ID
PK
Functional Location of Equipment ID
NVARCSTR
30
no
21
PERSON_ID_RESP
NVARCSTR
12
yes
22
PLANNG_GRP_ID
NVARCSTR
yes
23
PLANT_ID
PK
NVARCSTR
no
24
PLANT_ID_PLAN
NVARCSTR
yes
25
PLANT_ID_WRKCNTR
NVARCSTR
yes
26
PRIORITY_ID
NVARCSTR
yes
27
PRIORITY_TYPE_ID
NVARCSTR
yes
28
SEQ_NUM
PK
Group Sequential number (generated)
DECIMAL
48
28
no
29
STARTUP_DATE
Lookup - Equipment of Functional Location original startup date and time CRHD-ARBPL (lookup) - Work Center unique name
DATETIME
24
yes
30
WORK_CNTR_ID
NVARCSTR
yes
91
NOTIFICATION
Notification header from tables QMEL and QMIH.
ASSEMBLY_ID
QMIH-BAUTL - Assembly
NVARCSTR
18
yes
BATCH_ID
QMEL.CHARG - Batch number
NVARCSTR
10
yes
BREAKDOWN_FLAG
EQIH-MSAUS - Breakdown indicator. Set to 1 DECIMAL if there is a breakdown TGSBT.GTEXT - Business Area Name (lookup NVARCSTR on ILOA.GSBER)
48
28
yes
BUS_AREA_DESCR
30
yes
BUS_AREA_ID
ILOA.GSBER - Business area lookup
NVARCSTR
yes
CHANGE_BY_LOGIN
QMEL -AENAM - Name of accounting clerk who changed record
NVARCSTR
12
yes
CHANGE_DATE
QMFE-AEDAT - Last changed on
DATETIME
24
yes
CMPNY_CODE_DES CR
T001.BUTXT Company Code Name (lookup on NVARCSTR ILOA-BUKRS)
25
yes
CMPNY_CODE_ID
ILOA-BUKRS (lookup) - Company Code
NVARCSTR
yes
10
COMPLT_DATE
QMEL-QMDAB - Date for completion of notification CSKT.KTEXT - Cost Center Name (lookup on ILOA-KOSTL)
DATETIME
24
yes
11
COST_CNTR_DESCR
NVARCSTR
30
yes
12
COST_CNTR_ID
ILOA-KOSTL (lookup) - Cost Center
NVARCSTR
10
yes
13
CREATE_BY_LOGIN
QMEL-ERNAM - Name of person who created NVARCSTR object QMFE-ERDAT - Date on which the record was DATETIME created TKA01.BEZEI - Controlling area name (lookup NVARCSTR on ILOA-KOKRS)
12
yes
14
CREATE_DATE
24
yes
15
CTRL_AREA_DESCR
25
yes
16
CTRL_AREA_ID
NVARCSTR
yes
92
Appendix Table Column Details QMEL.KZLOESCH - Delete Data Record ("X" = NVARCSTR Notification marked for Deletion) TQ8T_T.QMTTX - Notification Category Descr. NVARCSTR (lookup on TQ80.QMTYP)
17
DELETE_FLAG
yes
18
DOC_CATEG_DESCR
20
yes
19
DOC_CATEG_ID
TQ80.QMTYP - Notification Category
NVARCSTR
yes
20
DOC_TYPE_DESCR
TQ80_T.QMARTX - Notification Type Descr. (lookup on QMEL-QMART)
NVARCSTR
20
yes
21
DOC_TYPE_ID
NVARCSTR
yes
22
EFFECT_ID
NVARCSTR
yes
23
EQUIPMNT_DESCR
EQKT.EQKTX - Equipment Description (lookup on QMIH-EQUNR)
NVARCSTR
40
yes
24
EQUIPMNT_ID
NVARCSTR
18
yes
25
FUNCTNL_LOCATN_D ESCR FUNCTNL_LOCATN_I D
IFLOTX.PLTXT - Functional location Descr. (lookup on ILOA.TPLNR)
NVARCSTR
40
yes
26
NVARCSTR
30
yes
27
INTERNAL_ORDER_ID
NVARCSTR
12
yes
28
LOAD_DATE
DATETIME
24
yes
29
LOAD_TIME
NVARCSTR
yes
30
LOCATN_DESCR
T499S.KTEXT - Location Description of Main. Object. (lookup on ILOA-STORT)
NVARCSTR
40
yes
31
LOCATN_ID
ILOA-STORT - Location of maintenance object NVARCSTR (lookup)
10
yes
32
QMIH-AUSBS - End of malfunction (date)
DATETIME
24
yes
33
QMIH-AUSVN - Start of malfunction (date)
DATETIME
24
yes
34
MATERIAL_ID
QMEL.MATNR - Material number
NVARCSTR
18
yes
93
Appendix Table Column Details MAKT.MAKTX - Material Desc.r (lookup on QMEL.MATNR) T023T.WGBEZ - Material Group Descr. (lookup on QMEL.MATKL)
35
MTRL_DESCR
NVARCSTR
40
yes
36
MTRL_GRP_DESCR
NVARCSTR
20
yes
37
MTRL_GRP_ID
QMEL.MATKL - Material group
NVARCSTR
yes
38
NOTIFICTN_DATE
QMEL-QMDAT - Date of notification
DATETIME
24
yes
39
NOTIFICTN_DESCR
NVARCSTR
40
yes
40
NOTIFICTN_ID
PK
NVARCSTR
12
no
41
NOTIFICTN_ID_REF
QMEL.QWRNUM - Reference Notification Number QMEL-OBJNR - Object number for status management
NVARCSTR
12
yes
42
OBJ_ID
NVARCSTR
22
yes
43
PERSON_ID_RESP
NVARCSTR
12
yes
44
PERSON_NAME_RE SP
PA0002.NACHN, PA0002.VORNA - Person responsible Last Name, First Name
NVARCSTR
82
yes
45
PLANNG_GRP_ID
NVARCSTR
yes
46
PLANNG_GRP_NAME
T024I.INNAM - Maintenance planner group Name (lookup on QMIH.INGRP)
NVARCSTR
18
yes
47
PLANT_ID
NVARCSTR
yes
48
PLANT_ID_PLAN
NVARCSTR
yes
49
PLANT_ID_WRKCNTR
NVARCSTR
yes
50
PLANT_NAME
T001W.NAME1 - Maint. Plant Descr. (lookup on ILOA-SWERK) T001W.NAME1 - Plant Name (lookup on QMIH.IWERK) T001W.NAME1 - Plant Name (lookup on CRHD.WERKS)
NVARCSTR
30
yes
51
PLANT_NAME_PLAN
NVARCSTR
30
yes
52
PLANT_NAME_WRK CNTR
NVARCSTR
30
yes
94
Appendix Table Column Details T356_T.PRIOKX - Priority Descr. (lookup on QMEL.PRIOK)
53
PRIORITY_DESCR
NVARCSTR
20
yes
54
PRIORITY_ID
NVARCSTR
yes
55
PRIORITY_TYPE_DES CR
T356A_T.ARTPRX - Priority Type Descr. (lookup on QMEL.ARTPR)
NVARCSTR
20
yes
56
PRIORITY_TYPE_ID
NVARCSTR
yes
57
QTY_DOWNTIME
QMIH-AUSZT - Downtime
DECIMAL
48
22
yes
58
REFERENCE_DATE
QMEL.BEZDT- Notification reference date
DATETIME
24
yes
59
REPORTED_BY_LOGI N
QMEL-QMNAM - Name of person reporting notification
NVARCSTR
12
yes
60
REQ_END_DATE
QMEL-LTRMN - Required end date
DATETIME
24
yes
61
REQ_START_DATE
QMEL-STRMN - Required start date
DATETIME
24
yes
62
UOM_CODE_DOWNT IME UOM_DESCR_DOWN TIME
T006A.MSEH3 - Downtime Unit of Meas. Code (lookup on QMIH-MAUEH) T006A.MSEH3 - Downtime Unit of Meas. Description (lookup on QMIH-MAUEH)
NVARCSTR
yes
63
NVARCSTR
30
yes
64
UOM_ID_DOWNTIME
QMIH-MAUEH - Downtime unit
NVARCSTR
yes
65
WORK_CNTR_DESCR
CRTX.KTEXT - Work Center Description (lookup)
NVARCSTR
40
yes
66
WORK_CNTR_ID
QMEL.ARBPL - Object ID of PM work center
NVARCSTR
yes
95
NOTIFICATION_FACT
Load NOTIFICATION_FACT from QMFE, QMIH, QMEL (Quality notifiction at line item level)
ASSEMBLY_ID
QMFE-BAUTL/QMIH.BAUTL - Assembly
NVARCSTR
18
yes
BREAKDOWN_FLAG
EQIH-MSAUS - Breakdown indicator. Set to 1 DECIMAL if there is a breakdown
48
28
yes
BUS_AREA_ID
PK
NVARCSTR
yes
CAUSE_GRP_ID
PK
QMUR-URGRP - Code group - Causes
NVARCSTR
yes
CAUSE_ID
PK
QMUR-URCOD - Cause code
NVARCSTR
yes
CHANGE_BY_LOGIN
QMEL -AENAM - Name of accounting clerk who changed record
NVARCSTR
12
yes
CHANGE_DATE
QMFE-AEDAT - Last changed on
DATETIME
24
yes
CHANGE_DATE_HDR
QMEL.AEDAT - Date of last change - header level
DATETIME
24
yes
CMPNY_CODE_ID
PK
NVARCSTR
yes
10
COMPLT_DATE
QMEL-QMDAB - Date for completion of notification + QMEL-QMZAB - Completion time DATETIME of notification JEST-STAT (lookup) - NOCO notification completed status is active (1 is active, 0 is inactive) PK ILOA-KOSTL (lookup) - Cost Center DECIMAL
24
yes
11
COMPLT_FLAG
48
28
yes
12
COST_CNTR_ID
NVARCSTR
10
yes
13
CREATE_BY_LOGIN
QMEL-ERNAM - Name of person who created NVARCSTR object QMFE-ERDAT - Date on which the record was DATETIME created
12
yes
14
CREATE_DATE
PK
24
yes
15
CREATE_DATE_HDR
QMEL.ERDAT - Creation Date - header level
DATETIME
24
yes
16
CTRL_AREA_ID
PK
NVARCSTR
yes
96
17
DAMAGE_GRP_ID
PK
QMFE-FEGRP - Code group - Problem
NVARCSTR
yes
18
DAMAGE_ID
PK
QMFE-FECOD - Problem
NVARCSTR
yes
19
DAYS_COMPLT
Number of Days to elimiate malfunction (calcualted)
DECIMAL
48
22
yes
20
DAYS_DOWNTIME
Number of mulfunction days (calcualted)
DECIMAL
48
22
yes
21
DAYS_REQ
Number of Requied days to fix malfuction (calcualted)
DECIMAL
48
22
yes
22
DOC_CATEG_ID
NVARCSTR
yes
23
DOC_TYPE_ID
PK
NVARCSTR
yes
24
EFFECT_ID
PK
NVARCSTR
yes
25
EQUIPMNT_ID
PK
NVARCSTR
18
yes
26
EQUIPMNT_ID_AFFEC T FUNCTNL_LOCATN_I D FUNCTNL_LOCATN_I D_AFFECT
QMIH-BEQUI - Equipment affected
NVARCSTR
18
yes
27
PK
NVARCSTR
30
yes
28
QMIH-BTPLN - Functional location affected
NVARCSTR
30
yes
29
HOURS_COMPLT
Number of Hours to elimiate malfunction (calcualted)
DECIMAL
48
22
yes
30
HOURS_DOWNTIME
Number of mulfunction Hours (calcualted)
DECIMAL
48
22
yes
31
HOURS_REQ
Number of Requied Hours to fix malfuction (calcualted)
DECIMAL
48
22
yes
32
QMEL-AUFNR - Order Number JEST-STAT (lookup) - NOPR notification is progress status is active (1 is active, 0 is inactive) QMFE-KZLOESCH - Indicator: delete data record. Set to 1 if an item is deleted
NVARCSTR
12
yes
33
IN_PROGRESS_FLAG
DECIMAL
48
28
yes
34
ITEM_DELETE_FLAG
DECIMAL
48
28
yes
97
35
LOAD_DATE
DATETIME
24
yes
36
LOAD_TIME
NVARCSTR
yes
37
LOCATN_ID
PK
ILOA-STORT - Location of maintenance object NVARCSTR (lookup) QMIH-AUSBS - End of malfunction (date) + QMIH-AUZTV - Start of malfunction (time) QMIH-AUSVN - Start of malfunction (date) + QMIH-AUSBS - End of malfunction (date)
10
yes
38
DATETIME
24
yes
39
DATETIME
24
yes
40
MATERIAL_ID
NVARCSTR
18
yes
41
MINS_COMPLT
Number of Hours to elimiate malfunction (calcualted)
DECIMAL
48
22
yes
42
MINS_DOWNTIME
Number of mulfunction Minutes (calcualted)
DECIMAL
48
22
yes
43
MINS_REQ
Number of Requied Minutes to fix malfuction (calcualted) QMEL-QMDAT - Date of notification (without timestamp)
DECIMAL
48
22
yes
44
NOTIFICTN_DATE
DATETIME
24
yes
45
NOTIFICTN_DATETIM E NOTIFICTN_DELETE_ FLAG
QMEL.QMDAT and QMEL.MZEIT - Notification DATETIME Date and Time JEST-STAT (lookup) - DLFL notification completed status is active (1 is active, 0 is inactive) QMEL-QMTXT - Short text
24
yes
46
DECIMAL
48
28
yes
47
NOTIFICTN_DESCR
NVARCSTR
40
yes
48
NOTIFICTN_ID
PK
NVARCSTR
12
no
49
NOTIFICTN_LINE_DE SCR NOTIFICTN_LINE_ITE PK M_ID
QMFE-FETXT - Notification item short text
NVARCSTR
40
yes
50
QMFE-FENUM - Item number in item record
NVARCSTR
no
51
OBJ_ID
QMEL-OBJNR - Object number for status management Concatenation of QMNUM and RENUM for classification
NVARCSTR
22
yes
52
OBJ_ID_CLASS
NVARCSTR
16
yes
98
53
OBJ_PART_GRP_ID
PK
QMFE-OTGRP - Code group - object parts
NVARCSTR
yes
54
OBJ_PART_ID
PK
QMFE-OTEIL - Object part JEST-STAT (lookup) - OSNO outstanding notification status is active (1 is active, 0 is inactive)
NVARCSTR
yes
55
OUTSTANDNG_FLAG
DECIMAL
48
28
yes
56
PERSON_ID_RESP
PK
NVARCSTR
12
yes
57
PLANNG_GRP_ID
PK
NVARCSTR
yes
58
PLANT_ID
PK
NVARCSTR
yes
59
PLANT_ID_PLAN
NVARCSTR
yes
60
PLANT_ID_WRKCNTR
CRHD-WERKS (lookup) - Work Center Plant JEST-STAT(lookup) - NOPO notification postponed status is active (1 is active, 0 is inactive) PK QMEL.PRIOK - Priority
NVARCSTR
yes
61
POSTPONE_FLAG
DECIMAL
48
28
yes
62
PRIORITY_ID
NVARCSTR
yes
63
PRIORITY_TYPE_ID
PK
NVARCSTR
yes
64
QTY_DOWNTIME
QMIH-AUSZT - Downtime
DECIMAL
48
22
yes
65
REFERENCE_DATE
QMEL.BEZDT- Notification reference date + QMEL.BEZUR - Notification reference time QMEL-QMNAM - Name of person reporting notification QMEL-LTRMN - Required end date + QMEL-LTRUR - Required end date-time QMEL-STRMN - Required start date + QMEL-STRUR - Required start (time)
DATETIME
24
yes
66
REPORTED_BY_LOGI N
NVARCSTR
12
yes
67
REQ_END_DATE
DATETIME
24
yes
68
REQ_START_DATE
DATETIME
24
yes
69
UOM_ID_DOWNTIME
PK
QMIH-MAUEH - Downtime unit
NVARCSTR
yes
70
WORK_CNTR_ID
PK
NVARCSTR
yes
99
OBJECT_CLASS
DD07T - Object Class reference dimension
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
OBJ_CLASS_DESCR
Object Class Domain Descritpion
NVARCSTR
60
yes
OBJ_CLASS_ID
PK
Object Class Domain ID
NVARCSTR
10
no
OBJECT_TYPE
DD07T - Object Type reference dimension
DIM_SRC_ID
PK
Dimension Source. This is a combined dimension combining different varieties of "object type" from different sources. This field identifies the source of "object type"
NVARCSTR
10
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
OBJ_TYPE_DESCR
Description of Object Type
NVARCSTR
75
yes
OBJ_TYPE_ID
PK
Object Type domain value ID
NVARCSTR
10
no
100
OPERATION_SUITABILITY
Key suitability required for carrying out the operation (for example, welding certificate or NC programming course) - from T423T
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PLANT_ID
PK
T423T.WERKS -Plant
NVARCSTR
no
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
yes
SUITABILITY_DESCR
T423T.TXT -Text for suitability
NVARCSTR
30
yes
SUITABILITY_ID
PK
T423T.QUALF -Suitability
NVARCSTR
no
101
PLANNING_GROUP
T024I - Planner group dimension
CMPNY_CODE_ID
T001K.BURKS - Company Code ID
NVARCSTR
yes
CMPNY_CODE_NAME
T001. BUTXT -Lookup on Company Code Name
NVARCSTR
25
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PLANNG_GRP_ID
PK
T024I-INGRP - Maintenance planner group
NVARCSTR
no
PLANNG_GRP_NAME
T024i-INNAM - Name of the maintenance planning group T024I-INTEL - Maintenance planning group phone number
NVARCSTR
18
yes
PLANNG_GRP_PHO NE
NVARCSTR
12
yes
PLANT_ID
PK
T024I-IWERK - Planning plant
NVARCSTR
no
PLANT_ID_MAINT
T001W.IWERK -Maintenance Planning Plant
NVARCSTR
yes
10
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
yes
11
PLANT_NAME_MAINT
T001W.NAME1 Maintenance Plant Name
NVARCSTR
30
yes
12
PURCH_ORG_DESCR
T024E.EKOTX - Lookup on Description of purchasing organization
NVARCSTR
20
yes
13
PURCH_ORG_ID
T001W.EKORG -Purchasing Organization
NVARCSTR
yes
14
VALUATN_AREA_ID
T001W.BWKEY -Valuation area
NVARCSTR
yes
102
PLANT
Contains Plant Level Information
ADDRESS_ID
Address ID
NVARCSTR
10
yes
BATCH_STATUS_FLA G
Batch Status Flag
NVARCSTR
yes
CITY
T001W.ORT01 CIty
NVARCSTR
40
yes
CMPNY_CODE_ID
Company code
NVARCSTR
yes
CMPNY_CODE_NAME
Company Code Name
NVARCSTR
40
yes
COUNTRY_ID
Country ID (Abbreviation)
NVARCSTR
yes
COUNTRY_NAME
Country Name (Full Name)
NVARCSTR
15
yes
CTRL_AREA_ID
Controlling area code
NVARCSTR
yes
CTRL_AREA_NAME
Control Area Name
NVARCSTR
25
yes
10
DISTRICT
District
NVARCSTR
40
yes
11
FAX
Fax Number
NVARCSTR
40
yes
12
HOUSE_NUMBER
House Number
NVARCSTR
10
yes
13
LOAD_DATE
24
yes
14
LOAD_TIME
NVARCSTR
yes
15
PHONE
Phone
NVARCSTR
30
yes
16
PLANT_FULL_NAME
ID and Name
NVARCSTR
120
yes
103
17
PLANT_ID
PK
T001W.WERKS Plant
NVARCSTR
no
18
PLANT_NAME
Plant name
NVARCSTR
40
yes
19
PLANT_NAME_01
T001W.NAME1 Plant Name
NVARCSTR
40
yes
20
PLANT_NAME_02
T001W.NAME2 Plant Name
NVARCSTR
40
yes
21
PLANT_NAME_03
Plant name 3
NVARCSTR
40
yes
22
PLANT_NAME_04
Plant name 3
NVARCSTR
40
yes
23
PURCH_ORG_ID
T001W.EKORG Purchasing Organization
NVARCSTR
yes
24
PURCH_ORG_NAME
T001W.CHAZV Batch Management Status Indicator
NVARCSTR
20
yes
25
REGION_ID
Region ID (Abbreviation of US State
NVARCSTR
yes
26
REGION_NAME
Region Name (Full Name of US State
NVARCSTR
20
yes
27
SALES_ORG_ID
T001W.VKORG Sales Organization
NVARCSTR
yes
28
SALES_ORG_NAME
Sales Organization name
NVARCSTR
25
yes
29
STREET
Street name
NVARCSTR
60
yes
30
VALUATN_AREA_ID
T001.BWKEY Valuation Area Key
NVARCSTR
yes
31
ZIP
Postal Code
NVARCSTR
10
yes
104
PLANT_LOCATION
Plant Location attributes from T499S
ADDRESS_ID
Address
NVARCSTR
10
yes
CITY
City
NVARCSTR
40
yes
CMPNY_CODE_ID
Company Code ID
NVARCSTR
yes
CMPNY_CODE_NAME
NVARCSTR
25
yes
COUNTRY_ID
Country Key
NVARCSTR
yes
COUNTRY_NAME
Country name
NVARCSTR
15
yes
DATE_TO
Valid-to date
DATETIME
24
yes
DISTRICT
District
NVARCSTR
40
yes
FAX
First fax no.: dialling code+number
NVARCSTR
30
yes
10
HOUSE_NUMBER
House Number
NVARCSTR
10
yes
11
LOAD_DATE
DATETIME
24
yes
12
LOAD_TIME
NVARCSTR
yes
13
LOCATN_FULL_NAME
T499S.STAND -Location ID + T499S.KTEXT -Text (40 characters)
NVARCSTR
55
yes
14
LOCATN_ID
PK
T499S.STAND -Location
NVARCSTR
10
no
15
LOCATN_NAME
T499S.KTEXT -Text (40 characters)
NVARCSTR
40
yes
16
PHONE
First telephone no.: dialling code+number
NVARCSTR
30
yes
105
17
PLANT_FULL_NAME
ID and Name
NVARCSTR
120
yes
18
PLANT_ID
PK
T499S.WERKS -Plant
NVARCSTR
no
19
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
yes
20
PLANT_NAME_01
Name 1
NVARCSTR
40
yes
21
PLANT_NAME_02
Name 2
NVARCSTR
40
yes
22
PLANT_NAME_03
Name 3
NVARCSTR
40
yes
23
PLANT_NAME_04
Name 4
NVARCSTR
40
yes
24
REGION_ID
Region (State, Province, County)
NVARCSTR
yes
25
REGION_NAME
Description
NVARCSTR
20
yes
26
STREET
Street
NVARCSTR
60
yes
27
VALUATN_AREA_ID
T001W.BWKEY -Valuation area
NVARCSTR
yes
28
ZIP
City postal code
NVARCSTR
10
yes
106
PRODUCT_HIERARCHY
T179 - Product Hierarchy dimension
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_01_DESCR
Level 1 description
NVARCSTR
40
yes
LVL_02_DESCR
Level 2 description
NVARCSTR
40
yes
LVL_03_DESCR
Level 3 descritpion
NVARCSTR
40
yes
PROD_DESCR
Current Node description
NVARCSTR
40
yes
PROD_HIER_ID
PK
Product Hierarchy Current Node ID
NVARCSTR
18
no
PROD_LVL
Node Level depth
NVARCSTR
yes
107
PROFIT_CENTER
CEPC - Profit Center attributes
CITY
City
NVARCSTR
40
yes
COUNTRY_ID
Country key
NVARCSTR
yes
COUNTRY_NAME
Lookup on Country name
NVARCSTR
15
yes
CTRL_AREA_ID
PK
Controlling area
NVARCSTR
no
CURR_ID
Currency key
NVARCSTR
yes
DEPARTMENT
Department
NVARCSTR
12
yes
DISTRICT
District
NVARCSTR
40
yes
FAX
Fax number
NVARCSTR
40
yes
LANG_ID
Language Key
NVARCSTR
yes
10
LOAD_DATE
24
yes
11
LOAD_TIME
NVARCSTR
yes
12
PERSON_IN_CHARGE
Person in charge of profit center
NVARCSTR
20
yes
13
PHONE
First telephone number
NVARCSTR
30
yes
14
PROFIT_CNTR_AREA
Profit center area
NVARCSTR
12
yes
15
PROFIT_CNTR_DESC R PROFIT_CNTR_FULL_ NAME
Name of Profit Center
NVARCSTR
40
yes
16
Profit Center Name and ID
NVARCSTR
120
yes
108
17
PROFIT_CNTR_ID
PK
Profit center
NVARCSTR
10
no
18
PROFIT_CNTR_NAME
Profit Center Name
NVARCSTR
20
yes
19
PROFIT_CNTR_NAME _01 PROFIT_CNTR_NAME _02 PROFIT_CNTR_NAME _03 PROFIT_CNTR_NAME _04
Name 1
NVARCSTR
40
yes
20
Name 2
NVARCSTR
40
yes
21
Name 3
NVARCSTR
40
yes
22
Name 4
NVARCSTR
40
yes
23
REGION_ID
Abbreviation of Region (State)
NVARCSTR
yes
24
REGION_NAME
Name of Region (State)
NVARCSTR
20
yes
25
SEGMENT_DESCR
Segment Description
NVARCSTR
50
yes
26
SEGMENT_ID
Segment ID for Segmental Reporting
NVARCSTR
10
yes
27
STREET
House number and street
NVARCSTR
60
yes
28
VALID_FROM_DATE
Valid-from date
DATETIME
24
yes
29
VALID_TO_DATE
Valid to date
DATETIME
24
yes
30
ZIP
Postal Code
NVARCSTR
10
yes
109
PROFIT_CENTER_HIER
CCSS-RPRCTR - Profit Center Hierarchy- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
Profit Center Child Node Description
NVARCSTR
64
yes
CHILD_ID
PK
Profit Center Child Node ID
NVARCSTR
10
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
no
LEAF_FLAG
PK
Node Is Leaf
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Profit Center Parent Node Descritpion
NVARCSTR
64
yes
PARENT_ID
PK
Profit Center Parent Node ID
NVARCSTR
10
no
ROOT_FLAG
PK
Node is Root
NVARCSTR
no
110
PROFIT_CENTER_HIER_BAD
CCSS-RPRCTR - Profit Center Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
Child Description
NVARCSTR
64
yes
CHILD_ID
PK
Child
NVARCSTR
10
no
CTRL_AREA_ID
PK
Control Area ID
NVARCSTR
no
ETL_ERROR_ACTN
NVARCSTR
yes
ETL_ERROR_COLU MN
NVARCSTR
500
yes
LEAF_FLAG
PK
Leaf Flag
NVARCSTR
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Parent Description
NVARCSTR
64
yes
10
PARENT_ID
PK
Parent ID
NVARCSTR
10
no
11
ROOT_FLAG
PK
Root Flag
NVARCSTR
no
111
PROFIT_CENTER_HIER_HZ
CCSS-RPRCTR - Profit Center hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
no
LEAF_LVL
DECIMAL
48
10
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
Profit Center Root node Description
NVARCSTR
64
yes
LVL_00_FULL_NAME
Profit Center ID and Description for the root
NVARCSTR
120
yes
LVL_00_ID
PK
Profit Center Root node ID
NVARCSTR
10
no
LVL_01_DESCR
Profit Center Level 1 node Description
NVARCSTR
64
yes
LVL_01_FULL_NAME
Profit Center ID and Description for Level 1
NVARCSTR
120
yes
10
LVL_01_ID
PK
Profit Center Level 1 node ID
NVARCSTR
10
no
11
LVL_02_DESCR
NVARCSTR
64
yes
12
LVL_02_FULL_NAME
Prifit Center ID and Descritption for Level 2
NVARCSTR
120
yes
13
LVL_02_ID
PK
NVARCSTR
10
no
14
LVL_03_DESCR
NVARCSTR
64
yes
15
LVL_03_FULL_NAME
Profit Center Id and Description
NVARCSTR
120
yes
16
LVL_03_ID
PK
NVARCSTR
10
no
112
17
LVL_04_DESCR
NVARCSTR
64
yes
18
LVL_04_FULL_NAME
Priofit Center ID and Description for Level 4
NVARCSTR
120
yes
19
LVL_04_ID
PK
NVARCSTR
10
no
20
LVL_05_DESCR
NVARCSTR
64
yes
21
LVL_05_FULL_NAME
Profit Center Id and Descritpion for Level 5
NVARCSTR
120
yes
22
LVL_05_ID
PK
NVARCSTR
10
no
23
LVL_06_DESCR
NVARCSTR
64
yes
24
LVL_06_FULL_NAME
Profit Center Id and Descripiton for Level 6
NVARCSTR
120
yes
25
LVL_06_ID
PK
NVARCSTR
10
no
26
LVL_07_DESCR
NVARCSTR
64
yes
27
LVL_07_FULL_NAME
Profit Center Id and Descritpion for level 7
NVARCSTR
120
yes
28
LVL_07_ID
PK
NVARCSTR
10
no
29
LVL_08_DESCR
NVARCSTR
64
yes
30
LVL_08_FULL_NAME
Profit Center Id and Descritpion for level 8
NVARCSTR
120
yes
31
LVL_08_ID
PK
NVARCSTR
10
no
32
LVL_09_DESCR
NVARCSTR
64
yes
33
LVL_09_FULL_NAME
NVARCSTR
120
yes
34
LVL_09_ID
PK
NVARCSTR
10
no
113
35
LVL_10_DESCR
NVARCSTR
64
yes
36
LVL_10_FULL_NAME
NVARCSTR
120
yes
37
LVL_10_ID
PK
NVARCSTR
10
no
38
PROFIT_CNTR_ID
PK
Profit Center ID
NVARCSTR
10
no
PROFIT_CENTER_HIER_VR
CCSS-RPRCTR Profit Center Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP
CHILD_DESCR
Child Node Descritpion for Profit Center
NVARCSTR
64
yes
CHILD_FULL_NAME
Profit Center (Child) ID and Descritpion
NVARCSTR
120
yes
CHILD_ID
PK
Child Node ID for Profit Center
NVARCSTR
10
no
CTRL_AREA_ID
PK
Controlling Center ID
NVARCSTR
no
DEPTH
Current Child Node Depth
INTEGER
yes
LEAF_FLAG
Current Node is Leaf
INTEGER
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Parent Node Descritpion for Profit Center
NVARCSTR
64
yes
10
PARENT_FULL_NAME
Profit Center (Parent) ID and Descritpion
NVARCSTR
120
yes
11
PARENT_ID
PK
Parent Node ID for Profit Center
NVARCSTR
10
no
12
ROOT_FLAG
Current Node is Root
INTEGER
yes
114
PROJECT_ELEMENT
PRPS, PRTE - Project Element Master dimension
ACTL_DURTN
Actual length (duration) of the WBS element
DECIMAL
48
yes
ACTL_FINISH_DATE
Actual finish date of the WBS element
DATETIME
24
yes
ACTL_START_DATE
Actual start date for the WBS element
DATETIME
24
yes
APPLICANT_ID
Applicant number
DECIMAL
48
28
yes
APPLICANT_NAME
Applicant
NVARCSTR
25
yes
BASIC_DURTN
Length (duration) of the basic dates in the WBS DECIMAL element
48
yes
BASIC_FINISH_DATE
WBS element: Basic finish date
DATETIME
24
yes
BASIC_SCHED_EARL ST_FINISH_DATE BASIC_SCHED_EARL ST_START_DATE BASIC_SCHED_LATE ST_FINISH_DATE BASIC_SCHED_LATE ST_START_DATE
Earliest scheduled finish date (basic)
DATETIME
24
yes
Earliest scheduled start date (Basic)
DATETIME
24
yes
10
Latest scheduled finish date (basic)
DATETIME
24
yes
11
Latest scheduled start date (basic)
DATETIME
24
yes
12
BASIC_START_DATE
WBS element: Basic start date
DATETIME
24
yes
13
CREATED_BY
Name of Person who Created the Object
NVARCSTR
12
yes
14
CREATE_DATE
Date on which the record was created
DATETIME
24
yes
15
DELETE_FLAG
Deletion indicator
NVARCSTR
yes
16
FCST_DURTN
Forecasted length (duration) of the WBS element
DECIMAL
48
yes
115
17
FCST_FINISH_DATE
Forecasted finish date of the WBS element
DATETIME
24
yes
18
FCST_SCHED_EARLS T_FINISH_DATE FCST_SCHED_LATES T_FINISH_DATE FCST_SCHED_LATES T_START_DATE FCST_SCHED_START _DATE
Earliest scheduled finish date (forecast)
DATETIME
24
yes
19
Latest scheduled finish date (Forecast)
DATETIME
24
yes
20
Latest scheduled start date (forecast)
DATETIME
24
yes
21
Scheduled start date (Forecast)
DATETIME
24
yes
22
FCST_START_DATE
Forecasted start date of the WBS element
DATETIME
24
yes
23
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) Indicator: WBS element used in project summarization
24
yes
24
LOAD_TIME
NVARCSTR
yes
25
MILESTONE_FLAG
NVARCSTR
yes
26
PRIORITY_FLAG
Priority
NVARCSTR
yes
27
PROJ_ELEM_CODE
PRPS.PSPNR - WBS element Internal ID
DECIMAL
48
28
yes
28
PROJ_ELEM_DESCR
PRPS.POST1 - WBS element (Project Element) Description PRPS.POSID and PRPS.POST1 Project Element ID and Project Element Description
NVARCSTR
40
yes
29
PROJ_ELEM_FULL_N AME
NVARCSTR
100
yes
30
PROJ_ELEM_ID
PK
PRPS.POSID - WBS element External ID
NVARCSTR
24
no
31
PROJ_ELEM_SHORT_ ID
PRPS.POSKI - WBS element short External ID NVARCSTR
16
yes
32
PROJ_ID
PROJ.PSPID - (Lookup on PROJ) Project ID (external) PROJ.POST1 - PS: Short description (1st text line) -- Lookup on PROJ
NVARCSTR
24
yes
33
PROJ_NAME
NVARCSTR
40
yes
34
RESP_PERSON
Name of responsible person (Project manager) NVARCSTR
25
yes
116
Appendix Table Column Details Number of the responsible person (project manager)
35
RESP_PERSON_ID
DECIMAL
48
28
yes
36
TNTV_FINISH_DATE
Tentative actual finish date for WBS element
DATETIME
24
yes
37
TNTV_START_DATE
Tentative actual start date for WBS element
DATETIME
24
yes
38
UOM_ID_ACTL_DURT N UOM_ID_BASIC_DUR TN UOM_ID_FCST_DURT N
Unit for duration of actual WBS element dates
NVARCSTR
yes
39
Unit for duration of basic WBS element dates
NVARCSTR
yes
40
Unit for duration of WBS element planned dates
NVARCSTR
yes
PROJECT_ELEMENT_HIER
PRHI - Project Element Hierarchy dimension
CHILD_CODE
PRPS.POSID - WBS element Internal ID Project Element Child Node ID
INTEGER
no
CHILD_DESCR
Project Element Child Node Description
NVARCSTR
100
yes
CHILD_FULL_NAME
Project Element Child Node ID and Description NVARCSTR
100
yes
CHILD_ID
PK
PRPS.POSID - WBS element External ID Project Element Child Node ID
NVARCSTR
24
no
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) PRPS.POSID - WBS element Internal ID Project Element Parent Node ID
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_CODE
INTEGER
no
PARENT_DESCR
Project Element Parent Node Description
NVARCSTR
100
yes
PARENT_FULL_NAME
Project Element Parent Node ID Description
NVARCSTR
100
yes
10
PARENT_ID
PK
PRPS.POSID - WBS element External ID Project Element Parent Node ID
NVARCSTR
24
no
117
PROJECT_ELEMENT_HIER_BAD
Rejected Project Element Hierarchy records
CHILD_CODE
PRPS.POSID - WBS element Internal ID Project Element Child Node ID
INTEGER
no
CHILD_DESCR
Project Element Child Node Description
NVARCSTR
100
yes
CHILD_FULL_NAME
Project Element Child Node ID and Description NVARCSTR
100
yes
CHILD_ID
PK
PRPS.POSID - WBS element External ID Project Element Child Node ID
NVARCSTR
24
no
ETL_ERROR_ACTN
NVARCSTR
yes
ETL_ERROR_COLU MN
NVARCSTR
500
yes
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) PRPS.POSID - WBS element Internal ID Project Element Parent Node ID
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_CODE
INTEGER
yes
10
PARENT_DESCR
Project Element Parent Node Description
NVARCSTR
100
yes
11
PARENT_FULL_NAME
Project Element Parent Node ID and Description PRPS.POSID - WBS element External ID Project Element Parent Node ID
NVARCSTR
100
yes
12
PARENT_ID
PK
NVARCSTR
24
no
118
PROJECT_ELEMENT_HIER_HZ
PRHI - Project element hierarchy flattenned horizontally
LEAF_LVL
INTEGER
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
LVL_00_DESCR
Project Element Root Node Description
NVARCSTR
100
yes
LVL_00_FULL_NAME
Project Element Root Level ID and Node Description
NVARCSTR
100
yes
LVL_00_ID
PK
Project Element Root Node ID
NVARCSTR
24
no
LVL_01_DESCR
Project Element Level 1 Node Description
NVARCSTR
100
yes
LVL_01_FULL_NAME
Project Element Level 1 Level ID and Node Description
NVARCSTR
100
yes
LVL_01_ID
PK
Project Element Level 1 Node ID
NVARCSTR
24
no
10
LVL_02_DESCR
NVARCSTR
100
yes
11
LVL_02_FULL_NAME
NVARCSTR
100
yes
12
LVL_02_ID
PK
NVARCSTR
24
no
13
LVL_03_DESCR
NVARCSTR
100
yes
14
LVL_03_FULL_NAME
NVARCSTR
100
yes
15
LVL_03_ID
PK
NVARCSTR
24
no
16
LVL_04_DESCR
NVARCSTR
100
yes
119
Appendix Table Column Details Project Element Level 4 Level ID and Node Description
17
LVL_04_FULL_NAME
NVARCSTR
100
yes
18
LVL_04_ID
PK
NVARCSTR
24
no
19
LVL_05_DESCR
NVARCSTR
100
yes
20
LVL_05_FULL_NAME
NVARCSTR
100
yes
21
LVL_05_ID
PK
NVARCSTR
24
no
22
LVL_06_DESCR
NVARCSTR
100
yes
23
LVL_06_FULL_NAME
NVARCSTR
100
yes
24
LVL_06_ID
PK
NVARCSTR
24
no
25
LVL_07_DESCR
NVARCSTR
100
yes
26
LVL_07_FULL_NAME
NVARCSTR
100
yes
27
LVL_07_ID
PK
NVARCSTR
24
no
28
LVL_08_DESCR
NVARCSTR
100
yes
29
LVL_08_FULL_NAME
NVARCSTR
100
yes
30
LVL_08_ID
PK
NVARCSTR
24
no
31
LVL_09_DESCR
NVARCSTR
100
yes
32
LVL_09_FULL_NAME
NVARCSTR
100
yes
33
LVL_09_ID
PK
NVARCSTR
24
no
34
LVL_10_DESCR
NVARCSTR
100
yes
120
Appendix Table Column Details Project Element Level 10 Level ID and Node Description
35
LVL_10_FULL_NAME
NVARCSTR
100
yes
36
LVL_10_ID
PK
NVARCSTR
24
no
37
PROJ_ELEM_ID
PK
Project Element Current Node ID
NVARCSTR
24
no
PROJECT_ELEMENT_HIER_VR
PRHI - Project Element Hierarchy vertically flattenned
CHILD_DESCR
Parent Node desc
NVARCSTR
100
yes
CHILD_FULL_NAME
Parent Node ID and Desc
NVARCSTR
100
yes
CHILD_ID
PK
Parent Node ID
NVARCSTR
24
no
DEPTH
Node depth level
INTEGER
yes
LEAF_FLAG
Is Leaf
INTEGER
yes
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PARENT_DESCR
Child Node Desc
NVARCSTR
100
yes
PARENT_FULL_NAME
Child Node ID and Desc
NVARCSTR
100
yes
10
PARENT_ID
PK
Child Node ID
NVARCSTR
24
no
11
ROOT_FLAG
Is Root
INTEGER
yes
121
SERVICE_CONFIRMATION_FACT
AFRU - Order completion confirmations (also data from AFIH, AUFK)
ACTIVITY_ID
PK
AFRU-LEARR - Activity type for confirmation
NVARCSTR
yes
ASSEMBLY_ID
AFIH-BAUTL - Assembly ID
NVARCSTR
18
yes
BUS_AREA_ID
PK
AUFK.GSBER -Business Area
NVARCSTR
yes
CAPACITY_ID
PK
AFRU.KAPID - Capacity ID
NVARCSTR
20
yes
CHANGE_BY_LOGIN
AFRU-AENAM - Name of accounting clerk who changed record
NVARCSTR
12
yes
CHANGE_DATE
AFRU-LAEDA - Date of last change
DATETIME
24
yes
CMPNY_CODE_ID
PK
AUFK.BUKRS -Company Code
NVARCSTR
yes
CONFIRMATN_DESCR
AFRU-LTXA1 - Confirmation text (inline)
NVARCSTR
40
yes
CONFIRMATN_ID
PK
AFRU-RUECK - Confirmation number of operation
NVARCSTR
10
no
10
CONFIRMATN_SEQ_I PK D
AFRU-RMZHL - Confirmation counter
NVARCSTR
no
11
COST_CNTR_ID
PK
AUFK.KOSTV -Responsible cost center
NVARCSTR
10
yes
12
CREATE_BY_LOGIN
AFRU-ERNAM - Name of person who created NVARCSTR object
12
yes
13
CREATE_DATE
PK
AFRU-ERSDA - Creation date
DATETIME
24
yes
14
CTRL_AREA_ID
PK
AUFK-KOKRS - Controlling area
NVARCSTR
yes
15
CURR_ID
PK
AUFK.WAERS -Order Currency
NVARCSTR
yes
16
CUSTOMER_ID
PK
AFIH.KUNUM - Customer number
NVARCSTR
10
yes
122
Appendix Table Column Details Calcualted Days to complete the operation (as DECIMAL Forecas end - Forecat start) Calcualted days of execution (as Execution Start end - Execution start)
17
DAYS_COMPLT_FCST
48
22
yes
18
DAYS_EXECUTN
DECIMAL
48
22
yes
19
DOC_CATEG_ID
AUFK.AUTYP - Document Category
NVARCSTR
yes
20
DOC_TYPE_ID
PK
AUFK-AUART - Order type
NVARCSTR
yes
21
EQUIPMNT_ID
PK
AFIH-EQUNR - Equipment number AFRU-IEDD - Confirmed date for execution finish + AFRU-IEDZ - Confirmed time for Execution finish AFRU-ISDD - Confirmed date for start of execution) + AFRU-ISDZ - Confirmed time for Execution start
NVARCSTR
18
yes
22
EXECUTN_END_DATE
DATETIME
24
yes
23
EXECUTN_START_DA TE
DATETIME
24
yes
24
FCST_END_DATE
AFRU.PEDD - Forecast finish date of operation from confirmation) + AFRU.PEDZ - Forecast DATETIME finish time of operation from confirmation AFRU-AUERU - Indicator: Partial/final confirmation DECIMAL
24
yes
25
FINAL_CONFIRMATN_ FLAG
48
28
yes
26
FUNCTNL_AREA_ID
PK
AUFK.FUNC_AREA -Functional Area
NVARCSTR
16
yes
27
FUNCTNL_LOCATN_I D HOURS_COMPLT_F CST
PK
ILOA-TPLNR (lookup) - Functional location ID NVARCSTR
30
yes
28
Calcualted hours to complete the operation (as DECIMAL Forecas end - Forecat start) Calcualted hours of execution (as Execution Start end - Execution start)
48
22
yes
29
HOURS_EXECUTN
DECIMAL
48
22
yes
30
AFRU-AUFNR - Order Number
NVARCSTR
12
yes
31
LOAD_DATE
DATETIME
24
yes
32
LOAD_TIME
NVARCSTR
yes
33
LOCATN_ID
PK
AUFK.STORT -Location
NVARCSTR
10
yes
34
MAINT_ACTIVITY_TYP PK E_ID
AFIH-ILART - Maintenance activity type
NVARCSTR
yes
123
35
MATERIAL_ID
PK
AFIH.SERMAT - Material number
NVARCSTR
18
yes
36
MINS_COMPLT_FCST
Calcualted minutes to complete the operation (as Forecas end - Forecat start)
DECIMAL
48
22
yes
37
MINS_EXECUTN
Calcualted minutes of execution (as Execution DECIMAL Start end - Execution start)
48
22
yes
38
NOTIFICTN_ID
AFIH.QMNUM - Notification number
NVARCSTR
12
yes
39
NO_REMAIN_WORK _FLAG OPERATN_ROUTING_ ID
AFRU-LEKNW - Indicator showing no remaining work expected
DECIMAL
48
28
yes
40
AFRU-AUFPL - Routing number for operations NVARCSTR in the order
10
yes
41
OPERATN_SEQ_ID
AFRU-APLZL - General counter for order
NVARCSTR
yes
42
ORDER_STATUS_ID
PK
AUFK.ASTNR - Order status
NVARCSTR
yes
43
PERSON_ID
PK
AFRU-PERNR - Personnel number - who files NVARCSTR Cofirmation IHPA-PERNR - Person responsible for the Service Order execution
yes
44
PERSON_ID_RESP
NVARCSTR
12
yes
45
PLANNG_GRP_ID
PK
AFIH-INGPR - Maintenance planner group
NVARCSTR
yes
46
PLANT_ID
PK
AFRU-WERKS - Plant
NVARCSTR
yes
47
PLANT_ID_PLANNG
AFIH-IWERK - Planning plant
NVARCSTR
yes
48
POST_DATE
AFRU.BUDAT - Posting date
DATETIME
24
yes
49
POST_OPEN_RESE RVATN_FLAG
AFRU.AUSOR - Post open reservations
NVARCSTR
yes
50
PRIORITY_ID
PK
AFIH.PRIOK - Priority
NVARCSTR
yes
51
PRIORITY_TYPE_ID
PK
AFIH.ARTPR - Priority type
NVARCSTR
yes
52
PROD_HIER_ID
MARA.PRDHA - Product Hierarchy ID - Look up based on AFIH.SERMAT
NVARCSTR
18
yes
124
53
PROFIT_CNTR_ID
PK
AUFK.PRCTR - Profit center
NVARCSTR
10
yes
54
PROJ_ELEM_ID
PK
PRPS.POSID - Project Element (WBS) External ID
NVARCSTR
24
yes
55
QTY_DURTN_ACTL
AFRU.IDAUR - Actual duration for confirmation DECIMAL
48
yes
56
QTY_WORK_ACTL
AFRU-ISMNW - Actual work (ifthenelse function call)
DECIMAL
48
yes
57
QTY_WORK_REMAIN
AFRU-OFMNW - Remaining work
DECIMAL
48
yes
58
SERIAL_NUM
AFIH.SERIALNR - Serial number
NVARCSTR
18
yes
59
SUITABILITY_ID
PK
AFRU.QUALF - Suitability
NVARCSTR
yes
60
SYSTEM_CONDITN_I D
PK
AFIH-ANLZU - System condition
NVARCSTR
yes
61
UOM_ID_DURTN_ACT PK L
AFRU.IDAUE- Unit for actual duration
NVARCSTR
yes
62
UOM_ID_WORK_ACTL
AFRU-ISMNE - Unit for work
NVARCSTR
yes
63
UOM_ID_WORK_RE MAIN
AFRU-OFMNE - Unit of measure for remaining NVARCSTR work CRHD-ARBPL (lookup) - Work Center unique name
yes
64
WORK_CNTR_ID
PK
NVARCSTR
yes
125
SERVICE_COST_SUMMARY_FACT_HZ
Extracts data from the table PMCO (cost summary for Plant Maintenence) in horizontal period activity representation
ACCTNG_FLAG
PK
PMCO-BEMOT - Accounting indicator
NVARCSTR
no
AMT_CR_PER00_TRX
PMCO-WRT00 - Period Credit value in ledger DECIMAL currency PMCO-WRT01 - Period Credit value in ledger DECIMAL currency PMCO-WRT02 - Period Credit value in ledger DECIMAL currency PMCO-WRT03 - Period Credit value in ledger DECIMAL currency PMCO-WRT04 - Period Credit value in ledger DECIMAL currency PMCO-WRT05 - Period Credit value in ledger DECIMAL currency PMCO-WRT06 - Period Credit value in ledger DECIMAL currency PMCO-WRT07 - Period Credit value in ledger DECIMAL currency PMCO-WRT08 - Period Credit value in ledger DECIMAL currency PMCO-WRT09 - Period Credit value in ledger DECIMAL currency PMCO-WRT10 - Period Credit value in ledger DECIMAL currency PMCO-WRT11 - Period Credit value in ledger DECIMAL currency PMCO-WRT12 - Period Credit value in ledger DECIMAL currency PMCO-WRT13 - Period Credit value in ledger DECIMAL currency PMCO-WRT14 - Period Credit value in ledger DECIMAL currency
48
15
yes
AMT_CR_PER01_TRX
48
15
yes
AMT_CR_PER02_TRX
48
15
yes
AMT_CR_PER03_TRX
48
15
yes
AMT_CR_PER04_TRX
48
15
yes
AMT_CR_PER05_TRX
48
15
yes
AMT_CR_PER06_TRX
48
15
yes
AMT_CR_PER07_TRX
48
15
yes
10
AMT_CR_PER08_TRX
48
15
yes
11
AMT_CR_PER09_TRX
48
15
yes
12
AMT_CR_PER10_TRX
48
15
yes
13
AMT_CR_PER11_TRX
48
15
yes
14
AMT_CR_PER12_TRX
48
15
yes
15
AMT_CR_PER13_TRX
48
15
yes
16
AMT_CR_PER14_TRX
48
15
yes
126
Appendix Table Column Details PMCO-WRT15- Period Credit value in ledger currency
17
AMT_CR_PER15_TRX
DECIMAL
48
15
yes
18
AMT_CR_PER16_TRX
PMCO-WRT16 - Period Credit value in ledger DECIMAL currency PMCO-WRT00 through 03 - Quarter Credit value in ledger currency PMCO-WRT04 through 06 - Quarter Credit value in ledger currency PMCO-WRT07 through 09 - Quarter Credit value in ledger currency PMCO-WRT10 through 16 - Quarter Credit value in ledger currency
48
15
yes
19
AMT_CR_QTR01_TRX
DECIMAL
48
15
yes
20
AMT_CR_QTR02_TRX
DECIMAL
48
15
yes
21
AMT_CR_QTR03_TRX
DECIMAL
48
15
yes
22
AMT_CR_QTR04_TRX
DECIMAL
48
15
yes
23
AMT_CR_YTD_TRX
PMCO-WRT01 through 16 - Year Credit value DECIMAL in ledger currency PMCO-WRT00 - Period Debit value in ledger currency PMCO-WRT01 - Period Debit value in ledger currency
48
15
yes
24
AMT_DR_PER00_TRX
DECIMAL
48
15
yes
25
AMT_DR_PER01_TRX
DECIMAL
48
15
yes
26
AMT_DR_PER02_TRX
PMCO-WRT002 - Period Debit value in ledger DECIMAL currency PMCO-WRT03 - Period Debit value in ledger currency PMCO-WRT04 - Period Debit value in ledger currency PMCO-WRT05 - Period Debit value in ledger currency PMCO-WRT06 - Period Debit value in ledger currency PMCO-WRT07 - Period Debit value in ledger currency PMCO-WRT08 - Period Debit value in ledger currency PMCO-WRT09 - Period Debit value in ledger currency PMCO-WRT10 - Period Debit value in ledger currency
48
15
yes
27
AMT_DR_PER03_TRX
DECIMAL
48
15
yes
28
AMT_DR_PER04_TRX
DECIMAL
48
15
yes
29
AMT_DR_PER05_TRX
DECIMAL
48
15
yes
30
AMT_DR_PER06_TRX
DECIMAL
48
15
yes
31
AMT_DR_PER07_TRX
DECIMAL
48
15
yes
32
AMT_DR_PER08_TRX
DECIMAL
48
15
yes
33
AMT_DR_PER09_TRX
DECIMAL
48
15
yes
34
AMT_DR_PER10_TRX
DECIMAL
48
15
yes
127
Appendix Table Column Details PMCO-WRT11 - Period Debit value in ledger currency PMCO-WRT12 - Period Debit value in ledger currency PMCO-WRT13 - Period Debit value in ledger currency PMCO-WRT14 - Period Debit value in ledger currency PMCO-WRT15 - Period Debit value in ledger currency PMCO-WRT16 - Period Debit value in ledger currency PMCO-WRT00 through 03 - Quarter Debit value in ledger currency PMCO-WRT04 through 06 - Quarter Debit value in ledger currency PMCO-WRT07 through 09 - Quarter Debit value in ledger currency PMCO-WRT10 through 16 - Quarter Debit value in ledger currency PMCO-WRT01 through 16 - Year Debit value in ledger currency
35
AMT_DR_PER11_TRX
DECIMAL
48
15
yes
36
AMT_DR_PER12_TRX
DECIMAL
48
15
yes
37
AMT_DR_PER13_TRX
DECIMAL
48
15
yes
38
AMT_DR_PER14_TRX
DECIMAL
48
15
yes
39
AMT_DR_PER15_TRX
DECIMAL
48
15
yes
40
AMT_DR_PER16_TRX
DECIMAL
48
15
yes
41
AMT_DR_QTR01_TRX
DECIMAL
48
15
yes
42
AMT_DR_QTR02_TRX
DECIMAL
48
15
yes
43
AMT_DR_QTR03_TRX
DECIMAL
48
15
yes
44
AMT_DR_QTR04_TRX
DECIMAL
48
15
yes
45
AMT_DR_YTD_TRX
DECIMAL
48
15
yes
46
ASSEMBLY_ID
NVARCSTR
18
yes
47
BUS_ACTIVITY_ID
PK
PMCO-VORGA - Budgeting / Planning Activity NVARCSTR
no
48
BUS_AREA_ID
PK
NVARCSTR
yes
49
CMPNY_CODE_ID
PK
NVARCSTR
yes
50
COST_CNTR_ID
PK
NVARCSTR
10
yes
51
CTRL_AREA_ID
PK
AUFK.KOKRS -Controlling Area
NVARCSTR
yes
52
CURR_ID_CTRL_ARE A
Lookup controlling area currency from TKA01
NVARCSTR
yes
128
53
CURR_ID_LOC
Lookup company code currency from T001
NVARCSTR
yes
54
CURR_ID_TRX
PK
PMCO-COCUR - Currency ID (Ledger Currency)
NVARCSTR
no
55
DOC_CATEG_ID
NVARCSTR
yes
56
DOC_TYPE_ID
PK
AUFK.AUART -Order Type
NVARCSTR
yes
57
EQUIPMNT_ID
PK
AFIH-EQUNR - Equipment number
NVARCSTR
18
yes
58
FISC_YEAR
PK
PMCO-GJAHR - Fiscal year
INTEGER
no
59
Fiscal Year Variant in SAP For Company Code NVARCSTR
yes
60
FUNCTNL_AREA_ID
PK
NVARCSTR
16
yes
61
FUNCTNL_LOCATN_I D
PK
30
yes
62
AUFK.AUFNR -Order Number
NVARCSTR
12
yes
63
LOAD_DATE
Date and Time This row was loaded into the Rapid Mart
DATETIME
24
yes
64
LOAD_TIME
Time This row was loaded into the Rapid Mart
NVARCSTR
yes
65
LOCATN_ID
PK
NVARCSTR
10
yes
66
MAINT_ACTIVITY_TYP E_ID
NVARCSTR
yes
67
MATERIAL_ID
NVARCSTR
18
yes
68
MAX_FISC_PERIOD
PK
PMCO-PERBL - Period block - Max # of Periods
INTEGER
no
69
OBJ_ID
PK
PMCO-OBJNR - Object number
NVARCSTR
22
no
70
PARTITION_YEAR
PK
Duplicate of Fisc. Year column to allow for Table partition on a field not in the Primary Key INTEGER
yes
129
71
PLANT_ID
PK
AUFK.WERKS -Plant
NVARCSTR
yes
72
PRIORITY_ID
PK
NVARCSTR
yes
73
PRIORITY_TYPE_ID
PK
NVARCSTR
yes
74
PROD_HIER_ID
NVARCSTR
18
yes
75
PROFIT_CNTR_ID
PK
AUFK.PRCTR -Profit Center
NVARCSTR
10
yes
76
PROJ_ELEM_ID
PK
NVARCSTR
24
yes
77
RECORD_CATEG_ID
PK
PMCO-ACPOS - Value category
NVARCSTR
14
no
78
RECORD_TYPE_ID
PK
PMCO.WRTTP - Value type
NVARCSTR
no
79
SERIAL_NUM
NVARCSTR
18
yes
80
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for reporting purposes
DECIMAL
48
18
yes
81
SYSTEM_CONDITN_I D
PK
NVARCSTR
yes
82
VARIANCE_CATEG_ID PK
PMCO-ABKAT - Category: variance/results analysis CRHD-ARBPL (lookup) - Work Center unique name
NVARCSTR
10
no
83
WORK_CNTR_ID
PK
NVARCSTR
yes
130
SERVICE_COST_SUMMARY_FACT_VR
Computes Rolling Totals forService Cost Summary Vertical Fact. (Sourced from PMCO)
ACCTNG_FLAG
PK
NVARCSTR
no
AMT_CR_QTD_TRX
PMCO-WRT01 through 16 - QTD Credit value DECIMAL in ledger currency 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
48
15
yes
AMT_CR_TRX
DECIMAL
48
15
yes
AMT_CR_YTD_TRX
PMCO-WRT01 through 16 - YTD Credit value DECIMAL in ledger currency PMCO-WRT01 through 16 - QTD Debit value in ledger currency
48
15
yes
AMT_DR_QTD_TRX
DECIMAL
48
15
yes
AMT_DR_TRX
PMCO-WRT00 through WRT16 - Period Debit value in ledger currency. For Period 01 DECIMAL cumulative of Per 00 and Per 01; for Per 12 cumulative of Per 12 through Per 16 PMCO-WRT01 through 16 - YTD Debit value in ledger currency PMCO-WRT01 through 16 - Period begin balance value in ledger currency DECIMAL
48
15
yes
AMT_DR_YTD_TRX
48
15
yes
AMT_PER_BEGIN_TR X AMT_PER_ROLLING_ TRX
DECIMAL
48
17
yes
Rolling Total Balance - Transaction Currency
DECIMAL
48
17
yes
10
AMT_PTD_TRX
Period Begining Balance - Transaction Currency
DECIMAL
48
17
yes
11
ASSEMBLY_ID
NVARCSTR
18
yes
12
BUS_ACTIVITY_ID
PK
no
13
BUS_AREA_ID
PK
NVARCSTR
yes
14
CMPNY_CODE_ID
PK
NVARCSTR
yes
15
COST_CNTR_ID
PK
NVARCSTR
10
yes
16
CTRL_AREA_ID
PK
NVARCSTR
yes
131
Appendix Table Column Details CURR_ID_CTRL_ARE A
17
NVARCSTR
yes
18
CURR_ID_LOC
NVARCSTR
yes
19
CURR_ID_TRX
PK
PMCO-COCUR - Currency ID (Ledger Currency)
NVARCSTR
no
20
DOC_CATEG_ID
NVARCSTR
yes
21
DOC_TYPE_ID
PK
NVARCSTR
yes
22
EQUIPMNT_ID
PK
NVARCSTR
18
yes
23
FISC_PERIOD
PK
Fiscal Period (1 through 16)
INTEGER
no
24
FISC_YEAR
PK
INTEGER
no
25
yes
26
FUNCTNL_AREA_ID
PK
NVARCSTR
16
yes
27
FUNCTNL_LOCATN_I D
PK
30
yes
28
NVARCSTR
12
yes
29
LOAD_DATE
DATETIME
24
yes
30
LOAD_TIME
NVARCSTR
yes
31
LOCATN_ID
NVARCSTR
10
yes
32
NVARCSTR
yes
33
MATERIAL_ID
PK
NVARCSTR
18
yes
34
OBJ_ID
PK
NVARCSTR
22
no
132
Appendix Table Column Details PMCO-GJAHR - Same as Fiscal year for table INTEGER partitions
35
PARTITION_YEAR
PK
yes
36
PLANT_ID
PK
AUFK.WERKS -Plant
NVARCSTR
yes
37
PRIORITY_ID
PK
NVARCSTR
yes
38
PRIORITY_TYPE_ID
PK
NVARCSTR
yes
39
PROD_HIER_ID
NVARCSTR
18
yes
40
PROFIT_CNTR_ID
PK
NVARCSTR
10
yes
41
PROJ_ELEM_ID
PK
NVARCSTR
24
yes
42
RECORD_CATEG_ID
PK
NVARCSTR
14
no
43
RECORD_TYPE_ID
PK
NVARCSTR
no
44
SERIAL_NUM
NVARCSTR
18
yes
45
SUMMARY_KEY
Concatenation ofr Primary Key for use in ordering query. Alternate key generated in the Rapid Mart for reporting purposes
NVARCSTR
100
yes
46
SURROGATE_DOC_ID
DECIMAL
48
18
yes
47
SYSTEM_CONDITN_I D
PK
NVARCSTR
yes
48
NVARCSTR
10
no
49
WORK_CNTR_ID
PK
NVARCSTR
yes
133
SERVICE_COST_SUMMARY_STAGE_VR
Vertical representation of Service Order Cost period activity. Staging is used for further Rolling Summary calculation
ACCTNG_FLAG
PK
NVARCSTR
no
AMT_CR_QTD_TRX
PMCO-WRT01 through 16 - QTD Credit value DECIMAL in ledger currency 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
48
15
yes
AMT_CR_TRX
DECIMAL
48
15
yes
AMT_CR_YTD_TRX
PMCO-WRT01 through 16 - YTD Credit value DECIMAL in ledger currency PMCO-WRT01 through 16 - QTD Debit value in ledger currency
48
15
yes
AMT_DR_QTD_TRX
DECIMAL
48
15
yes
AMT_DR_TRX
PMCO-WRT00 through WRT16 - Period Debit value in ledger currency. For Period 01 DECIMAL cumulative of Per 00 and Per 01; for Per 12 cumulative of Per 12 through Per 16 PMCO-WRT01 through 16 - YTD Debit value in ledger currency PMCO-WRT01 through 16 - Period begin balance value in ledger currency DECIMAL
48
15
yes
AMT_DR_YTD_TRX
48
15
yes
AMT_PER_BEGIN_TR X
DECIMAL
48
17
yes
ASSEMBLY_ID
NVARCSTR
18
yes
10
BUS_ACTIVITY_ID
PK
no
11
BUS_AREA_ID
NVARCSTR
yes
12
CMPNY_CODE_ID
NVARCSTR
yes
13
COST_CNTR_ID
NVARCSTR
10
yes
14
CTRL_AREA_ID
NVARCSTR
yes
15
CURR_ID_CTRL_ARE A
NVARCSTR
yes
16
CURR_ID_LOC
NVARCSTR
yes
134
Appendix Table Column Details PMCO-COCUR - Currency ID (Ledger Currency)
17
CURR_ID_TRX
PK
NVARCSTR
no
18
DOC_CATEG_ID
NVARCSTR
yes
19
DOC_TYPE_ID
NVARCSTR
yes
20
EQUIPMNT_ID
NVARCSTR
18
yes
21
FISC_PERIOD
PK
Fiscal Period (1 through 16)
INTEGER
no
22
FISC_YEAR
PK
INTEGER
no
23
FISC_YR_VARIANT_ID
yes
24
FUNCTNL_AREA_ID
NVARCSTR
16
yes
25
FUNCTNL_LOCATN_I D
30
yes
26
INTERNAL_ORDER_ID
NVARCSTR
12
yes
27
LOAD_DATE
DATETIME
24
yes
28
LOAD_TIME
NVARCSTR
yes
29
LOCATN_ID
NVARCSTR
10
yes
30
MAINT_ACTIVITY_TYP E_ID
NVARCSTR
yes
31
MATERIAL_ID
NVARCSTR
18
yes
32
OBJ_ID
PK
NVARCSTR
22
no
33
PARTITION_YEAR
PK
Duplicate of Fisc. Year column to allow for Table partition on a field not in the Primary Key INTEGER
yes
34
PLANT_ID
AUFK.WERKS -Plant
NVARCSTR
yes
135
35
PRIORITY_ID
NVARCSTR
yes
36
PRIORITY_TYPE_ID
NVARCSTR
yes
37
PROD_HIER_ID
NVARCSTR
18
yes
38
PROFIT_CNTR_ID
NVARCSTR
10
yes
39
PROJ_ELEM_ID
NVARCSTR
24
yes
40
RECORD_CATEG_ID
PK
NVARCSTR
14
no
41
RECORD_TYPE_ID
PK
NVARCSTR
no
42
SERIAL_NUM
NVARCSTR
18
yes
43
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for reporting purposes
DECIMAL
48
18
yes
44
SYSTEM_CONDITN_I D
NVARCSTR
yes
45
NVARCSTR
10
no
46
WORK_CNTR_ID
NVARCSTR
yes
136
SERVICE_OPERATION_FACT
Operations related to Service orders from AFIH, AFVC, AFVV
ACTIVITY_ID
PK
AFVC.LARNT - Activity Type
NVARCSTR
yes
ACTL_END_DATE
AFVV-IEDD - Actual finish: Execution (date) + AFVV-ISDZ - AFVV-IEDZ - Actual finish: DATETIME Execution (time) AFVV-ISDD - Actual start: Execution (date) + AFVV-ISDZ - Actual start: Execution/setup (time) AFVC.MAT_PRKST - Material planning in networks: primary costs AFVC.PRKST - Total Costs in the activity Planned DATETIME
24
yes
ACTL_START_DATE
24
yes
AMT_COST_MTRL
DECIMAL
48
11
yes
AMT_COST_TTL
DECIMAL
48
11
yes
ASSEMBLY_ID
AFIH.BAUTL - Assembly
NVARCSTR
18
yes
BUS_AREA_ID
PK
AFVC.GSBER - Business Area
NVARCSTR
yes
CAPACITY_REQUIRM PK NT_ID
AFVC.BEDID - ID of the capacity requirements NVARCSTR record
12
yes
CHART_OF_ACCT_ID PK
T001.KTOPL-Chart of accts ID - Lookup
NVARCSTR
yes
10
CMPNY_CODE_ID
PK
AFVC.BUKRS Company Code
NVARCSTR
yes
11
COMPLT_FLAG
AFVC-LEKNW - Indicator showing no remaining work expected if set to 1 AFVC.RUECK Completion confirmation number for the operation
DECIMAL
48
28
yes
12
CONFIRMATN_ID
NVARCSTR
10
yes
13
CONFIRMATN_SEQ_I D
AFVC.RMZHL- Confirmation counter
NVARCSTR
yes
14
COSTNG_FLAG
AFVC.SELKZ - Selection indicator for costing line items
NVARCSTR
yes
15
COST_CNTR_ID
NVARCSTR
10
yes
16
COST_ELEM_ID
PK
AFVC.SAKTO - Cost Element
NVARCSTR
10
yes
137
17
CREATE_DATE
PK
AUFK.ERDAT -Order Create date
DATETIME
24
yes
18
CTRL_AREA_ID
PK
NVARCSTR
yes
19
CTRL_KEY_ID
PK
AFVC.STEUS - Control key
NVARCSTR
yes
20
CURR_ID
PK
AFVC.WAERS - Currency Key
NVARCSTR
yes
21
CUSTOMER_ID
PK
NVARCSTR
10
yes
22
DAYS_EXECUTN_ACT L DAYS_EXECUTN_S CHED
Calcualted Days of Operation exeuction/startup DECIMAL time (as Actl Start and Actl End datetime) Calcualted Days of Operation exeuction/startup DECIMAL time (as Sched Start and Sched End datetime) JEST-STAT (lookup) - DEL operation isdeleted status is active (1 is active, 0 is inactive) AUFK.AUTYP - Document Category
48
22
yes
23
48
22
yes
24
DELETE_FLAG
DECIMAL
48
28
yes
25
DOC_CATEG_ID
NVARCSTR
yes
26
DOC_TYPE_ID
AUFK.AUART - Document Type
NVARCSTR
yes
27
EQUIPMNT_ID
PK
AFIH.EQUNR - Equipment number
NVARCSTR
18
yes
28
EXECUTN_FACTOR
AFVV-AUFKT - Execution factor
INTEGER
yes
29
FINAL_CONFIRM_FLA G
JEST-STAT (lookup) - CNF operation is finally confirmed status is active (1 is active, 0 is DECIMAL inactive) PK AUFK.FUNC_AREA -Functional Area NVARCSTR
48
28
yes
30
FUNCTNL_AREA_ID
16
yes
31
FUNCTNL_LOCATN_I D HOURS_EXECUTN_ ACTL HOURS_EXECUTN_ SCHED
ILOA-TPLNR (lookup) - Functional location ID NVARCSTR Calcualted Hours of Operation exeuction/startup time (as Actl Start and Actl End datetime) Calcualted Hours of Operation exeuction/startup time (as Sched Start and Sched End datetime) AFIH.AUFNR - Order Number
30
yes
32
DECIMAL
48
22
yes
33
DECIMAL
48
22
yes
34
NVARCSTR
12
yes
138
35
LOAD_DATE
Date loaded into RapidMart
DATETIME
24
yes
36
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
yes
37
LOCATN_ID
PK
NVARCSTR
10
yes
38
NVARCSTR
yes
39
MATERIAL_ID
PK
NVARCSTR
18
yes
40
MINS_EXECUTN_ACT L MINS_EXECUTN_SCH ED
Calcualted Mins of Operation exeuction/startup DECIMAL time (as Actl Start and Actl End datetime) Calcualted Mins of Operation exeuction/startup DECIMAL time (as Sched Start and Sched End datetime)
48
22
yes
41
48
22
yes
42
NOTIFICTN_ID
NVARCSTR
12
yes
43
OBJ_CLASS_ID
PK
AFVC.SCOPE - Object Class
NVARCSTR
10
yes
44
OBJ_ID
AFVC.OBJNR - Object number
NVARCSTR
22
yes
45
OBJ_TYPE_ID
Object Type ID
NVARCSTR
10
yes
46
OPERATN_DESCR
AFVC.LTXA1 - Operation short text
NVARCSTR
40
yes
47
OPERATN_NUM
AFVC.VORNR - Operation Number
NVARCSTR
yes
48
OPERATN_NUM_PAR
AFVC.SUMNR - Node number of the superior operation AFVC.AUFPL - Routing number of operations in the order
NVARCSTR
yes
49
OPERATN_ROUTING_ PK ID
NVARCSTR
10
no
50
OPERATN_SEQ_ID
PK
AFVC.APLZL - General counter for order JEST-STAT (lookup) -PCNF operation is partially confirmed status is active (1 is active, 0 is inactive)
NVARCSTR
no
51
PARTL_CONFIRM_FL AG
DECIMAL
48
28
yes
52
PLANNG_GRP_ID
PK
NVARCSTR
yes
139
53
PLANT_ID
PK
AFVC.WERKS - Plant
NVARCSTR
yes
54
PRIORITY_ID
PK
AFIH.PRIOK - Priority ID
NVARCSTR
yes
55
PRIORITY_TYPE_ID
PK
NVARCSTR
yes
56
PROD_HIER_ID
NVARCSTR
18
yes
57
PROFIT_CNTR_ID
PK
AFVC.PRCTR Profit Center
NVARCSTR
10
yes
58
PROJ_ELEM_ID
PK
NVARCSTR
24
yes
59
PURCH_DOC_ID
AFVC.EBELN - Purchasing document number
NVARCSTR
10
yes
60
PURCH_LINE_ITEM_I D
AFVC.EBELP - Item number of purchasing document
NVARCSTR
yes
61
QTY_DURTN
AFVV.DAUNO - Normal duration of the activity DECIMAL
48
yes
62
QTY_WORK_ACTL
AFVV-ISMNW - Actual work
DECIMAL
48
13
yes
63
QTY_WORK_FCST
AFVV-ORMNW - Forecasted work (actual + remaining)
DECIMAL
48
yes
64
QTY_WORK_SCHED
AFVV-ARBEI - Work involved in the activity JEST-STAT (lookup) - REL operation is released status is active (1 is active, 0 is inactive) AFVC.BANFN Purchase requisition number
DECIMAL
48
yes
65
RELEASE_FLAG
DECIMAL
48
28
yes
66
REQUISITN_DOC_ID
NVARCSTR
10
yes
67
REQUISITN_LINE_ITE M_ID
AFVC.BNFPO - Item number of the purchase requisition in the order AFVV.FSEDD - Earliest scheduled finish: Execution (date) + AFVV.FSEDZ - Earliest scheduled finish: Execution (time) AFVV.FSAVD - Earliest scheduled start: Execution (date) + AFVV.FSAVZ - Earliest scheduled start: Execution (time) AFIH.SERIALNR - Serial number
NVARCSTR
yes
68
SCHED_END_DATE
DATETIME
24
yes
69
SCHED_START_DATE
DATETIME
24
yes
70
SERIAL_NUM
NVARCSTR
18
yes
140
71
SUITABILITY_ID
PK
AFVC.QUALF Suitability
NVARCSTR
yes
72
SYSTEM_CONDITN_I D TECHN_COMPLT_FLA G
PK
AFVC-ANLZU - System condition JEST-STAT (lookup) - TECO operation is technically completed status is active (1 is active, 0 is inactive)
NVARCSTR
yes
73
DECIMAL
48
28
yes
74
UOM_ID_DURTN
PK
AFVV.DAUNE - Normal duration/unit
NVARCSTR
yes
75
UOM_ID_WORK
AFVV-ARBEH - Unit for work
NVARCSTR
yes
76
VENDOR_ID
PK
AFVC.LIFNR - Account Number of Vendor or Creditor CRHD-ARBPL (lookup) - Work Center unique name
NVARCSTR
10
yes
77
WORK_CNTR_ID
PK
NVARCSTR
yes
141
SERVICE_ORDER_FACT
Internal Order Master - Service Order category from AFIH/AFKO/AUFK
ACTL_END_DATE
AFKO.GETRI - Confirmed order finish date
DATETIME
24
yes
ACTL_RELEASE_DAT E
AFKO-FTRMI - Actual release date (Last Operation is Released) AFKO-GSTRI - Actual start date (First Operation is Started)
DATETIME
24
yes
ACTL_START_DATE
DATETIME
24
yes
ASSEMBLY_ID
NVARCSTR
18
yes
BASIC_END_DATE
AFKO-GLTRP - Finish (basic) date
DATETIME
24
yes
BASIC_START_DATE
AFKO-GSTRP - Order (basic) start date
DATETIME
24
yes
BLOCK_FLAG
JEST-STAT (lookup) - LKD order is locked status is active (1 is active, 0 is inactive)
DECIMAL
48
28
yes
BUS_AREA_ID
PK
NVARCSTR
yes
CHANGE_DATE
AUFK-AEDAT - Change date
DATETIME
24
yes
10
CLOSE_FLAG
JEST-STAT (lookup) - CLSD order is closed status is active (1 is active, 0 is inactive)
DECIMAL
48
28
yes
11
CMPNY_CODE_ID
PK
NVARCSTR
yes
12
COST_CNTR_ID
PK
NVARCSTR
10
yes
13
CREATE_DATE
PK
AUFK-ERDAT - Date created
DATETIME
24
yes
14
CTRL_AREA_ID
PK
NVARCSTR
yes
15
CURR_ID
PK
AUFK.WAERS -Order Currency
NVARCSTR
yes
16
CUSTOMER_ID
PK
NVARCSTR
10
yes
142
Appendix Table Column Details Number of Days to actually complete a service DECIMAL order (calcualted) Number of Days to Basic complete a service order (calcualted) Number of Forecast Days to complete a service order (calcualted) Number of Days scheduled to complete a service order (calcualted) Number of Days to actually release a service order (calcualted)
17
DAYS_COMPLT_ACTL
48
22
yes
18
DAYS_COMPLT_BASI C
DECIMAL
48
22
yes
19
DAYS_COMPLT_FCST
DECIMAL
48
22
yes
20
DAYS_COMPLT_SC HED DAYS_RELEASE_ACT L DAYS_RELEASE_SCH ED
DECIMAL
48
22
yes
21
DECIMAL
48
22
yes
22
Number of Days scheduled to release a service DECIMAL order (calcualted) JEST-STAT (lookup) - DLFL order is deleted status is active (1 is active, 0 is inactive)
48
22
yes
23
DELETE_FLAG
DECIMAL
48
28
yes
24
DOC_CATEG_ID
NVARCSTR
yes
25
DOC_TYPE_ID
AUFK-AUART - Order type
NVARCSTR
yes
26
EQUIPMNT_ID
PK
NVARCSTR
18
yes
27
FCST_END_DATE
AFKO.GLTPP - Finish date (forecast)
DATETIME
24
yes
28
FCST_SCHED_END_D ATE FCST_SCHED_START _DATE
AFKO.GLTPS - Scheduled forecast finish
DATETIME
24
yes
29
AFKO.GSTPS - Scheduled forecast start
DATETIME
24
yes
30
FCST_START_DATE
AFKO.GSTPP - Forecast start date JEST-STAT (lookup) - CNF order is finally confirmed status is active (1 is active, 0 is inactive) PK AUFK.FUNC_AREA -Functional Area
DATETIME
24
yes
31
FINAL_CONFIRM_FLA G
DECIMAL
48
28
yes
32
FUNCTNL_AREA_ID
NVARCSTR
16
yes
33
FUNCTNL_LOCATN_I D HOURS_COMPLT_A CTL
PK
30
yes
34
Number of Hours to actually complete a service DECIMAL order (calcualted)
48
22
yes
143
Appendix Table Column Details HOURS_COMPLT_B ASIC HOURS_COMPLT_F CST HOURS_COMPLT_S CHED Number of Hours to Basic complete a service order (calcualted) Number of Forecast Hours to complete a service order (calcualted) Number of Hours scheduled to complete a service order (calcualted)
35
DECIMAL
48
22
yes
36
DECIMAL
48
22
yes
37
DECIMAL
48
22
yes
38
AFIH-AUFNR - Work Order Number
NVARCSTR
12
no
39
LOAD_DATE
DATETIME
24
yes
40
LOAD_TIME
NVARCSTR
yes
41
LOCATN_ID
PK
AUFK.STORT -Location within Plant
NVARCSTR
10
yes
42
NVARCSTR
yes
43
MATERIAL_ID
PK
NVARCSTR
18
yes
44
MINS_COMPLT_ACTL
Number of Minutes to actually complete a service order (calcualted)
DECIMAL
48
22
yes
45
MINS_COMPLT_BASI C
Number of Minutes to Basic complete a service DECIMAL order (calcualted) Number of Forecast Minutes to complete a service order (calcualted) Number of Minutes scheduled to complete a service order (calcualted)
48
22
yes
46
MINS_COMPLT_FCST
DECIMAL
48
22
yes
47
MINS_COMPLT_SCHE D
DECIMAL
48
22
yes
48
NOTIFICTN_ID
NVARCSTR
12
yes
49
OBJ_ID
AUFK-OBJNR - Object number
NVARCSTR
22
yes
50
OPERATN_ROUTING_ ID
AFKO-AUFPL - Routing number for operations NVARCSTR in the order
10
yes
51
OPERATN_SEQ_ID
AFKO.APLZT - General Counter for Order
NVARCSTR
yes
52
ORDER_STATUS_ID
AUFK.ASTNR - Order status
NVARCSTR
yes
144
Appendix Table Column Details PARTL_CONFIRM_FL AG JEST-STAT (lookup) - PCNF order is partially confirmed status is active (1 is active, 0 is inactive)
53
DECIMAL
48
28
yes
54
PERSON_ID_RESP
IHPA-PERNR - Personnel number responsible NVARCSTR
12
yes
55
PLANNG_GRP_ID
PK
NVARCSTR
yes
56
PLANT_ID
PK
AUFK-WERKS - Plant (for Work Center)
NVARCSTR
yes
57
PLANT_ID_PLAN
AFIH-IWERK - Planning plant
NVARCSTR
yes
58
PRIORITY_ID
PK
NVARCSTR
yes
59
PRIORITY_TYPE_ID
PK
NVARCSTR
yes
60
PROD_HIER_ID
NVARCSTR
18
yes
61
PROFIT_CNTR_ID
PK
AUFK.PRCTR - Profit center
NVARCSTR
10
yes
62
PROJ_ELEM_ID
PK
PRPS.POSID - Project Element (WBS) External ID JEST-STAT (lookup) - REL order is released status is active (1 is active, 0 is inactive) AFKO.RSNUM - Number of reservation/ dependent requirement
NVARCSTR
24
yes
63
RELEASE_FLAG
DECIMAL
48
28
yes
64
RESERVATN_ID
NVARCSTR
10
yes
65
SCHED_END_DATE
AFKO-GLTRS - Scheduled finish
DATETIME
24
yes
66
SCHED_RELEASE_DA TE
AFKO-FTRMS - Scheduled release date
DATETIME
24
yes
67
SCHED_START_DATE
AFKO-GSTRS - Scheduled start
DATETIME
24
yes
68
SERIAL_NUM
NVARCSTR
18
yes
69
SERVICE_ORDER_DE SCR SERVICE_ORDER_ID_ PAR
AUFK-KTEXT - Short text
NVARCSTR
40
yes
70
AFKO-MAUFNR - Superior order number
NVARCSTR
12
yes
145
Appendix Table Column Details SYSTEM_CONDITN_I D TECHN_COMPLT_FLA G
71
PK
AFIH-ANLZU - System condition JEST-STAT (lookup) - TECO order is technically completed status is active (1 is active, 0 is inactive)
NVARCSTR
yes
72
DECIMAL
48
28
yes
73
WORK_CNTR_ID
PK
NVARCSTR
yes
SERVICE_PERSON
Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data
FIRST_NAME
PA0002-VORNA - First name
NVARCSTR
40
yes
FULL_NAME
PA0002-NACHN - Last name + PA0002-VORNA - First name
NVARCSTR
90
yes
LAST_NAME
PA0002-NACHN - Last name
NVARCSTR
40
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PERSON_ID
PK
PA0002-PERNR - Personnel number
NVARCSTR
no
SYSTEM_CONDITION
System Condition descriptive attributes from T253M_T
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SYSTEM_CONDITN_D ESCR SYSTEM_CONDITN_I D
T357M_T-ANLZUX - Operating status text
NVARCSTR
40
yes
PK
T357M_T-ANLZU - System condition
NVARCSTR
no
146
TIME_DIM
Time Dimension (Daily)
CALENDAR_DATE
PK
Calendar Date
DATETIME
24
no
CALENDAR_MONTH
Number of Calendar Month
INTEGER
yes
CALENDAR_QUART ER
Calendar Quarter
INTEGER
yes
CALENDAR_YEAR
Calenar Year
INTEGER
yes
DAY_IN_PERIOD
Number of a day in a fiscal period
INTEGER
yes
DAY_IN_WEEK
Day of the week
INTEGER
yes
FISC_PERIOD
Fiscal Period of Calendar Date. Retrieved from INTEGER SAP using FI_PERIOD_DETEMINE Fiscal Year of Calendar Date. Retrieved from SAP using FI_PERIOD_DETEMINE
yes
FISC_YEAR
INTEGER
yes
IS_WEEKEND
Indicates if date falls on a weekend (1)
NVARCSTR
yes
10
LOAD_DATE
24
yes
11
LOAD_TIME
NVARCSTR
yes
12
MONTH_YEAR
Calendar Month and Year
NVARCSTR
10
yes
13
WEEK_IN_YEAR
Number of week in the year
DECIMAL
48
28
yes
147
TIME_DIM_WEEKLY
Time Dimension (WEEKLY). Used for summary facts (such as BENEFIT_ENROLL_SUMMARY_FACT)
CALENDAR_YEAR
PK
Calenar Year
INTEGER
no
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
WEEK_END_DATE
Last date in the week
DATETIME
24
yes
WEEK_IN_YEAR
PK
Number of week in the year
DECIMAL
48
28
no
WEEK_NAME
Week - Year concatenation
NVARCSTR
60
yes
WEEK_START_DATE
First date of the week
DATETIME
24
yes
WEEK_START_FISC_ PER WEEK_START_FISC_ YEAR WEEK_START_MON TH WEEK_START_QUA RTER
Fiscal Period when the week starts
INTEGER
yes
Fiscal Year when the week starts
INTEGER
yes
10
Number of Calendar Month when the week starts
INTEGER
yes
11
Calendar Quarter when the week starts
INTEGER
yes
148
UNIT_OF_MEASURE
T006A-Material Unit of Measure attritues
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) T006A.MSEH3 -- Unit of Meas. ID in Local Language (External unit of measurement commercial format (3-char)) T006A-MSEHT - Measurement unit text (max. 10 char.)
24
yes
LOAD_TIME
NVARCSTR
yes
UOM_CODE
NVARCSTR
yes
UOM_DESCR
NVARCSTR
10
yes
UOM_ID
PK
T006A-MSEHI - Unit of measurement
NVARCSTR
no
VARIANCE_CATEGORY
Financial Variance Category descriptive attributes (ABKAT domain from DD07T)
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
VARIANCE_CATEG_D ESCR
DD07T-DDTEXT - Short text describing ABAP/4 Dictionary objects (ABKAT) DD07T-DOMVALUE_L - Values for domains: Single value/upper limit(ABKAT)
NVARCSTR
60
yes
NVARCSTR
10
no
149
VENDOR
LIFNR - Vendor Master
ACCT_GRP_DESCR
Lookup LFA1.KTOKK Acount Group Description in T077Y
NVARCSTR
30
yes
ACCT_GRP_ID
Vendor Account Group ID
NVARCSTR
yes
ADDRESS_ID
Internal Address ID from SAP
NVARCSTR
10
yes
ALT_PAYEE_NUM
LFA1.LNRZA Account number of the alternative payee
NVARCSTR
10
yes
CITY
LFA1.ORT01 City
NVARCSTR
40
yes
COUNTRY_ID
LFA1.LAND1 Country key
NVARCSTR
yes
COUNTRY_NAME
Country Name (Full Name)
NVARCSTR
15
yes
CREATE_DATE
LFA1.ERDAT Date on which the record was created
DATETIME
24
yes
CR_INFO_ID
LFA1.KRAUS Credit information number
NVARCSTR
11
yes
10
CUSTOMER_ID
LFA1.KUNNR Customer number
NVARCSTR
10
yes
11
CUSTOMER_NAME
Customer Name
NVARCSTR
40
yes
12
DELETE_FLAG
LFA1.LOEVM Central delete flag for master record
NVARCSTR
yes
13
DISTRICT
LFA1.ORT02 District
NVARCSTR
40
yes
14
FAX
LFA1.TELFX Fax number
NVARCSTR
40
yes
15
HOUSE_NUMBER
House Number
NVARCSTR
10
yes
16
INDUSTRY_DESCR
Lookup description of Industry LFA1.BRSCH in NVARCSTR T016T
20
yes
150
17
INDUSTRY_ID
LFA1.BRSCH Industry key
NVARCSTR
yes
18
LANG_ID
LFA1.SPRAS Language key
NVARCSTR
yes
19
LOAD_DATE
Date and time when the record was loaded into DATETIME Rapid Mart Time when the record was loaded into the RapidMart (string format HH24:MI:SS) Lookup description of LFA1.XCPDK - One Time Account Indicator
24
yes
20
LOAD_TIME
NVARCSTR
yes
21
ONE_TIME_ACCT_DE SCR
NVARCSTR
yes
22
PHONE
LFA1.TELF1 First telephone number
NVARCSTR
30
yes
23
PLANT_ID
LFA1.WERKS Plant
NVARCSTR
yes
24
PLANT_NAME
Plant Name
NVARCSTR
30
yes
25
REGION_ID
LFA1.REGIO Region (State
NVARCSTR
yes
26
REGION_NAME
Region Full Name (State
NVARCSTR
20
yes
27
STREET
LFA1.STRAS House number and street
NVARCSTR
60
yes
28
TRADING_PARTNER_I D TRADING_PARTNER_ NAME VENDOR_FULL_NA ME
LFA1.VBUND Trading partner ID
NVARCSTR
yes
29
Trading partner Name
NVARCSTR
30
yes
30
Vendor Full name
NVARCSTR
120
yes
31
VENDOR_GRP_KEY
LFA1.KONZS Group key
NVARCSTR
10
yes
32
VENDOR_ID
PK
LIFNR Vendor (creditor) account number
NVARCSTR
10
no
33
VENDOR_NAME
Vendor Name
NVARCSTR
40
yes
34
VENDOR_NAME_01
LFA1.NAME1 Vendor Name 1
NVARCSTR
40
yes
151
35
VENDOR_NAME_02
LFA1.NAME2 Vendor Name 2
NVARCSTR
40
yes
36
VENDOR_NAME_03
Vendor Name 3
NVARCSTR
40
yes
37
VENDOR_NAME_04
Vendor Name 4
NVARCSTR
40
yes
38
ZIP
LFA1.PSTLZ Postal code
NVARCSTR
10
yes
152
VENDOR_BY_COMPANY
Cross-reference of LFA1 and T001 tables (Vendors and Company Codes)
ACCTNG_CLERK_ID
T001S.BUSAB - Accounting clerk
NVARCSTR
yes
ACCTNG_CLERK_N AME
T001S.SNAME - Name of Accounting Clerk
NVARCSTR
30
yes
ACCT_GRP_DESCR
T077Y.TXT30 - VENDOR Account descr (lookup) T077Y.TXT30 - VENDOR Account descr (lookup) - One time acct LFA1.XCPDK - Indicator: Is the account a one-time account? LFA1.KTOCK -- Reference account group for one-time account (vendor)
NVARCSTR
30
yes
ACCT_GRP_DESCR _ONE_TIME
NVARCSTR
30
yes
ACCT_GRP_ID
NVARCSTR
yes
ACCT_GRP_ID_ONE_ TIME
NVARCSTR
yes
BANK_ID_HOUSE
LFB1.HBKID -- ID for one house bank
NVARCSTR
yes
CALENDAR_DESCR
TFACT.LTEXT - Factory Calendar Description
NVARCSTR
60
yes
CALENDAR_ID
LFA1.PLKAL -- Factory calendar key
NVARCSTR
yes
10
CHART_OF_ACCT_DE SCR
T004T.KTPLT - Chart of Accounts Description
NVARCSTR
50
yes
11
CHART_OF_ACCT_ID
T001.KTOPL - Chart of Accounts (Company Code)
NVARCSTR
yes
12
CMPNY_CODE_FULL_ NAME
Company Code and Company Name
NVARCSTR
36
yes
13
CMPNY_CODE_ID
PK
LFB1-BUKRS -- Company code
NVARCSTR
no
14
CMPNY_CODE_NAME
T001.BUTXT - Name of the company code or company
NVARCSTR
25
yes
15
CR_INFO_CODE
LFA1.KRAUS -- Credit information number
NVARCSTR
11
yes
16
CUSTOMER_ID
LFA1.KUNNR -- Customer number
NVARCSTR
10
yes
153
17
CUSTOMER_NAME
KNA1.NAME1 - Customer Name as vendor
NVARCSTR
40
yes
18
DELETE_BLOCK_FLA G DELETE_BLOCK_FLA G_CENTRAL
LFB1.NODEL - Company Code Level Deletion NVARCSTR Blcok
yes
19
LFA1.NODEL - Central Deletion Block
NVARCSTR
yes
20
DELETE_FLAG
LFB1.LOEVM -- Deletion flag for master record NVARCSTR
yes
21
DELETE_FLAG_CENT RAL GL_ACCT_DESCR_RE CONCILE GL_ACCT_ID_RECON CILE INTL_LOCATN_NUM_ 01 INTL_LOCATN_NUM_ 02
LFA1.LOEVM - Central Deletion Flag for Master Record SKAT.TXT50 - Descr. of Reconciliation account in G/L accounting SKB1.SAKNR - Account Code (Reconciliation account in G/L accounting) LFA1-BBBNR -- International location number (part 1) LFA1-BBBSR -- International location number (part 2) Date that this row was loaded into the data warehouse Time that this row was loaded into the data warehouse
NVARCSTR
yes
22
NVARCSTR
60
yes
23
NVARCSTR
10
yes
24
NVARCSTR
yes
25
NVARCSTR
yes
26
LOAD_DATE
DATETIME
24
yes
27
LOAD_TIME
NVARCSTR
10
yes
28
ONETIME_ACCT_FLA G
LFA1.XCPDK - One Time Account flag
NVARCSTR
yes
29
OUR_ACCT_NUM
LFB1.EIKTO -- Our account number at the vendor
NVARCSTR
12
yes
30
PAYMNT_BLOCK_D ESCR PAYMNT_BLOCK_FLA G_CENTRAL
T008T.TEXTL - Payment Block Description
NVARCSTR
20
yes
31
LFA1.SPERZ - Central Payment Block
NVARCSTR
yes
32
PAYMNT_BLOCK_ID
LFB1.ZAHLS -- Block key for payment
NVARCSTR
yes
33
PAYMNT_TERM_DE SCR
TVZBT.VTEXT - Standard Payment term description
NVARCSTR
50
yes
34
PAYMNT_TERM_ID
LFB1.ZTERM - Payment terms key
NVARCSTR
yes
154
35
PLANT_ID
LFA1-WERKS Plant
NVARCSTR
yes
36
PLANT_NAME
T001W.NAME1 - Plant Name
NVARCSTR
30
yes
37
POR_NUM
LFA1.ESRNR -- POR subscriber number
NVARCSTR
11
yes
38
POST_BLOCK_FLAG
LFB1.SPERR - Company Code Level Posting Block
NVARCSTR
yes
39
POST_BLOCK_FLAG_ CENTRAL PURCH_BLOCK_FLAG _CENTRAL
LFA1.SPERR - Central Posting Block
NVARCSTR
yes
40
LFA1.SPERM - Central Purchasing Block
NVARCSTR
yes
41
SOLE_PROPR_FLAG
LFA1.STKZN -- Indicator if partner is a sole proprietor
NVARCSTR
yes
42
TAX_JURISDIC_NUM
LFA1.TXJCD -- Jurisdiction for tax calculation - NVARCSTR tax jurisdiction code
15
yes
43
TAX_NUM_01
LFA1.STCD1 -- Tax number 1
NVARCSTR
16
yes
44
TAX_NUM_02
LFA1.STCD2 -- Tax number 2
NVARCSTR
11
yes
45
VAT_REGISTRTN_NU M VENDOR_FULL_NA ME
LFA1.STCEG -- VAT registration number
NVARCSTR
20
yes
46
LFA1.NAME1+ LFA1.LIFNR - Full Name
NVARCSTR
120
yes
47
VENDOR_ID
PK
LFA1.LIFNR
NVARCSTR
10
no
48
VENDOR_ID_ALT_PA YEE
LFA1.LNRZA -- Account number of the alternative payee
NVARCSTR
10
yes
49
VENDOR_NAME
LFA1.NAME1 - Vendor Name 1
NVARCSTR
40
yes
155
WORK_CENTER
Work center descriptions and standard capacity information from CRHD used as default by capacity planning processes
BACKFLUSH_FLAG
CRHD.RGEKZ - Indicator: Backflushing (1/0)
INTEGER
yes
CHANGE_DATE
AEDAT_GRND - Changed on
DATETIME
24
yes
CMPNY_CODE_ID
Company Code ID
NVARCSTR
yes
CMPNY_CODE_NAME
NVARCSTR
25
yes
CTRL_KEY_DESCR
T430T-TXT -Control Key desctiption (lookup)
NVARCSTR
40
yes
CTRL_KEY_ID
CRHD.STEUS - Control key
NVARCSTR
yes
CURRENT_FLAG
1 indicates record is currently in effect (1/0)
INTEGER
yes
DELETE_FLAG
CRHD.LVORM - Deletion flag for work center ( INTEGER 1/0) TC25T-TXT - Lookup on Formula descritpion for Other TC25T-TXT - Lookup on Formula descritpion for Process TC25T-TXT - Lookup on Formula descritpion for Setup TC25T-TXT - Lookup on Formula descritpion for TearDown
yes
FORMULA_DESCR_ OTHER FORMULA_DESCR_ PROCESS FORMULA_DESCR_ SETUP FORMULA_DESCR_ TEARDOWN
NVARCSTR
20
yes
10
NVARCSTR
20
yes
11
NVARCSTR
20
yes
12
NVARCSTR
20
yes
13
FORMULA_ID_OTHER
CRHD.FORTN - Formula for other workcenter NVARCSTR times CRHD.FORT2 - Formula for work center processing time duration
yes
14
FORMULA_ID_PROCE SS
NVARCSTR
yes
15
FORMULA_ID_SETUP
CRHD.FORT1 - Formula for work center setup NVARCSTR time CRHD.FORT3 - Formula for work center teardown time calculation
yes
16
FORMULA_ID_TEARD OWN
NVARCSTR
yes
156
Appendix Table Column Details Date and time when the record is loaded into Rapid Mart
17
LOAD_DATE
DATETIME
24
yes
18
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
yes
19
LOCATN_GRP_DES CR
TC28T-TXT - Location group desctiption (lookup)
NVARCSTR
20
yes
20
LOCATN_GRP_ID
CRHD.ORTGR - Location group
NVARCSTR
yes
21
MACHINE_TYPE_DES CR MACHINE_TYPE_GRP _ID MINS_MIN_QUEUE_TI ME MINS_STD_QUEUE_TI ME
Lookup machine type group description
NVARCSTR
40
yes
22
CRHD.MATYP - Machine type grouping
NVARCSTR
10
yes
23
CRHD.ZWMIN - Minimum queue time converted to minutes CRHD.ZWNOR - Standard queue time converted to minutes
DECIMAL
48
yes
24
DECIMAL
48
yes
25
OBJ_ID
CRHD.HROID - Object ID
NVARCSTR
yes
26
ORG_UNIT_TYPE_DE SCR
T777O-OTEXT -Object Type Description
NVARCSTR
25
yes
27
ORG_UNIT_TYPE_ID
CRHD.HRTYP - Object type
NVARCSTR
yes
28
PERSON_RESP_CO DE PERSON_RESP_DE SCR
CRHD.VERAN - Person responsible for the work center
NVARCSTR
yes
29
Lookup TC24.KTEXT - Person responsible for NVARCSTR the work center VERAN
40
yes
30
PLANT_ID
PK
CRHD.WERKS - Plant
NVARCSTR
no
31
PLANT_NAME
T001W.NAME1 - lookup on Plant Name
NVARCSTR
40
yes
32
STD_TEXT_KEY_COD E STD_VALUE_KEY_DE SCR
CRHD.KTSCH - Standard text key
NVARCSTR
yes
33
Lookup standard value key description in TC21 NVARCSTR
30
yes
34
STD_VALUE_KEY_ID
CRHD.VGWTS - Standard value key
NVARCSTR
yes
157
Appendix Table Column Details T423T-TXT - Sutability( Qualificiation/Wage Group) desctiption (lookup) CRHD.QUALF - Suitability for carrying certain tasks
35
SUITABILITY_DESCR
NVARCSTR
30
yes
36
SUITABILITY_ID
NVARCSTR
yes
37
SUPPLY_AREA_DESC R
PVKT-PVBTX -Supply Area Description
NVARCSTR
40
yes
38
SUPPLY_AREA_ID
CRHD.PRVBE Supply area
NVARCSTR
10
yes
39
TASK_LIST_USG_DES CR
Lookup task list usage descripton
NVARCSTR
30
yes
40
TASK_LIST_USG_ID
CRHD.PLANV - Key for task list usage
NVARCSTR
yes
41
VALID_FROM_DATE
CRHD.BEGDA - Effectivity Start date
DATETIME
24
yes
42
VALID_TO_DATE
CRHD.ENDDA - Effectivity end date
DATETIME
24
yes
43
VALUATN_AREA_ID
T001W.BWKEY Valuation area lookup
NVARCSTR
yes
44
WORK_CNTR_CATE G_DESCR WORK_CNTR_CATE G_ID
Lookup description of Work Center category in NVARCSTR TC30T
20
yes
45
CRHD.VERWE - Work center category
NVARCSTR
yes
46
WORK_CNTR_CODE
CRHD.OBJID - Work center Internal Object ID NVARCSTR
yes
47
WORK_CNTR_DESCR
Lookup work center description in CRTX
NVARCSTR
40
yes
48
WORK_CNTR_FULL _NAME
CRHD.ARBPL - Work center Code + Name (Lookup work center description in CRTX CRHD.ARBPL - Work center- Visible ID in SAP
NVARCSTR
50
yes
49
WORK_CNTR_ID
PK
NVARCSTR
no
50
WORK_CNTR_LOCA TN_DESCR WORK_CNTR_LOCA TN_ID
T499S-KTEXT - Location desctiption (lookup)
NVARCSTR
40
yes
51
CRHD.STAND - Work center location
NVARCSTR
10
yes
158
WORK_CENTER_HIER
Work center parent-child relationship from CRHH/CRHS
CHILD_CODE
CRHD.ARBPL Work center Code - Child
NVARCSTR
yes
CHILD_DESCR
Lookup work center description in CRTX for Child WC Concatentaion of WC code and description for Child Node CRHS.OBJID_HO - Object ID of the resource and CRHH.NAME - Name of hierarchy
NVARCSTR
40
yes
CHILD_FULL_NAME
NVARCSTR
50
yes
CHILD_ID
PK
NVARCSTR
50
no
LOAD_DATE
Load date and time into the target database
DATETIME
24
yes
LOAD_TIME
Load time into the target database
NVARCSTR
yes
OWNER_ID
CRHH.VERAN - Person responsible for the work center Lookup TC24.KTEXT - Person responsible for the work center VERAN
NVARCSTR
yes
OWNER_NAME
NVARCSTR
40
yes
PARENT_CODE
CRHD.ARBPL - Work center - Parent node
NVARCSTR
yes
10
PARENT_DESCR
Lookup work center description in CRTX for Parent WC Concatentaion of WC code and description for Parent Node
NVARCSTR
40
yes
11
PARENT_FULL_NAME
NVARCSTR
50
yes
12
PARENT_ID
PK
CRHS.OBJID_UP - ID of superior object in the hierarchy and CRHH.NAME - Name of NVARCSTR hierarchy CRHH.WERKS - Plant NVARCSTR
50
no
13
PLANT_ID
yes
14
PLANT_NAME
NVARCSTR
40
yes
15
WORK_CNTR_HIER_I PK D WORK_CNTR_HIER_N AME
CRHH.OBJID - Object ID of the resource
NVARCSTR
no
16
CRHH.NAME - Name of hierarchy
NVARCSTR
10
yes
159
WORK_CENTER_HIER_BAD
Work center parent-child relationship from CRHH/CRHS - Invalid Records
CHILD_CODE
CRHD.ARBPL Work center Code - Child
NVARCSTR
yes
CHILD_DESCR
Lookup work center description in CRTX for Child WC Concatentaion of WC code and description for Child Node CRHS.OBJID_HO - Object ID of the resource and CRHH.NAME - Name of hierarchy
NVARCSTR
40
yes
CHILD_FULL_NAME
NVARCSTR
50
yes
CHILD_ID
PK
NVARCSTR
50
no
DI_ERROR_ACTN
DI Error Action
NVARCSTR
yes
DI_ERROR_COLUMN
DI Error Columns
NVARCSTR
500
yes
LOAD_DATE
Load date and time into the target database
DATETIME
24
yes
LOAD_TIME
Load time into the target database
NVARCSTR
yes
OWNER_ID
CRHH.VERAN - Person responsible for the work center Lookup TC24.KTEXT - Person responsible for the work center VERAN
NVARCSTR
yes
10
OWNER_NAME
NVARCSTR
40
yes
11
PARENT_CODE
CRHD.ARBPL - Work center - Parent node
NVARCSTR
yes
12
PARENT_DESCR
Lookup work center description in CRTX for Parent WC Concatentaion of WC code and description for Parent Node
NVARCSTR
40
yes
13
PARENT_FULL_NAME
NVARCSTR
50
yes
14
PARENT_ID
PK
CRHS.OBJID_UP - ID of superior object in the hierarchy and CRHH.NAME - Name of NVARCSTR hierarchy CRHH.WERKS - Plant NVARCSTR
50
no
15
PLANT_ID
yes
16
PLANT_NAME
NVARCSTR
40
yes
160
Appendix Table Column Details WORK_CNTR_HIER_I PK D WORK_CNTR_HIER_N AME
17
CRHH.OBJID - Object ID of the resource
NVARCSTR
no
18
NVARCSTR
10
yes
161
WORK_CENTER_HIER_HZ
Work Center Hierarchical relationship in Horizontal format from CRHH/CRHS
LEAF_LVL
Work Center Hierarchy Child ID
DECIMAL
48
28
yes
LOAD_DATE
Load date and time - for the target database
DATETIME
24
yes
LOAD_TIME
Load time for the target database
NVARCSTR
yes
LVL_00_DESCR
Description for 00 Parent Node
NVARCSTR
40
yes
LVL_00_FULL_NAME
Concatentaion of WC code and description for Parent Node
NVARCSTR
50
yes
LVL_00_ID
PK
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
no
LVL_01_DESCR
NVARCSTR
40
yes
LVL_01_FULL_NAME
NVARCSTR
50
yes
LVL_01_ID
PK
NVARCSTR
no
10
LVL_02_DESCR
NVARCSTR
40
yes
11
LVL_02_FULL_NAME
NVARCSTR
50
yes
12
LVL_02_ID
PK
NVARCSTR
no
13
LVL_03_DESCR
NVARCSTR
40
yes
14
LVL_03_FULL_NAME
NVARCSTR
50
yes
15
LVL_03_ID
PK
NVARCSTR
no
16
LVL_04_DESCR
NVARCSTR
40
yes
162
Appendix Table Column Details Concatentaion of WC code and description for Parent Node
17
LVL_04_FULL_NAME
NVARCSTR
50
yes
18
LVL_04_ID
PK
NVARCSTR
no
19
LVL_05_DESCR
NVARCSTR
40
yes
20
LVL_05_FULL_NAME
NVARCSTR
50
yes
21
LVL_05_ID
PK
NVARCSTR
no
22
PLANT_ID
PK
CRHH.WERKS - Plant ID
NVARCSTR
no
23
WORK_CNTR_HIER_N PK AME
NVARCSTR
10
no
24
WORK_CNTR_ID
PK
NVARCSTR
no
163
WORK_CENTER_HIER_VR
Work Center Hierarchical relationship in Vertical format from CRHH/CRHS
CHILD_FULL_NAME
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR Object description/name lookup CRHD-ARBPL (lookup) - Work Center unique name for Child ID
50
yes
CHILD_ID
PK
NVARCSTR
no
DEPTH
Node depth in the hierarchy
DECIMAL
48
28
yes
LEAF_FLAG
1 - Leaf, 0 - Root
DECIMAL
48
28
yes
LOAD_DATE
Load date and time - target database
DATETIME
24
yes
LOAD_TIME
Load time - target database
NVARCSTR
yes
PARENT_FULL_NAME
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR Object description/name lookup CRHD-ARBPL (lookup) - Work Center unique name for Parent ID
50
yes
PARENT_ID
PK
NVARCSTR
no
PLANT_ID
PK
CRHH.WERKS - Plant ID
NVARCSTR
no
10
ROOT_FLAG
1 - Root, 0 - Leaf
DECIMAL
48
28
yes
11
WORK_CNTR_HIER_N PK AME
NVARCSTR
10
no
164

Xi3 RM Sap PM Ug en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Xi3 RM Sap PM Ug en

Uploaded by

Copyright:

Available Formats

SAP BusinessObjects Plant Maintenance Rapid Mart XI 3.

2, version for SAP solutions - User Guide

Introduction What is a Rapid Mart?

What is a Rapid Mart?

Data Services Universe Designer Web Intelligence.

Introduction What is a Rapid Mart?

Rapid Marts packages accelerate Time to Value

Human Capital Management (HCM) Suite:

Introduction What is a Rapid Mart?

SAP BusinessObjects Rapid Marts packages architecture

Rapid Marts packages include the following components:

Introduction What is a Rapid Mart?

Introduction About this document

About this document

What you can do with this Rapid Mart

Overview Supported analyses

Object history Service Orders Maintenance hours

Overview Supported analyses

Type of analysis Confirmations Planning efficiency

Measures available in the Rapid Mart

MTBR and MTTR

Overview Related Rapid Marts

Related Rapid Marts

Plant Maintenance Rapid Mart Schema (3 of 3):

Overview Where the Rapid Mart fits in the maintenance process

Where the Rapid Mart fits in the maintenance process

Overview Where the Rapid Mart fits in the maintenance process

Plant Maintenance Process:.

Subject Areas Overview

Subject Areas Plant Maintenance Process Overview

Plant Maintenance Process Overview

Technical Objects & Systems

Subject Areas Plant Maintenance Process Overview

Pump 1 (equipment) Pump 2 (equipment) Pump 3 (equipment) Pump 4 (equipment)

Plant 2, etc... Pump Housing

Pump 1 (Top Level, Equipment Hierarchy)

Power supply Gear box

Piping Filters Inlet valve Outlet valve

Classification & Characteristics

Subject Areas Plant Maintenance Process Overview

Subject Areas Plant Maintenance Process Overview

Subject Areas Plant Maintenance Process Overview

A service order is subdivided into operations and confirmations.

Subject Areas Plant Maintenance Process Overview

Which technical data should be retained

Service Order Costs

Subject Areas Service Notification Section

Service Notification Section

The target table in the Rapid Mart schema is NOTIFICATION_FACT.

Subject Areas Service Notification Section

Rapid Mart processing

Company Code Controlling Area

Subject Areas Service Notification Section

Attribute Name Cost Center & Hierarchy

Equipment & Hierarchy

Functional Location & Hierarchy

Internal Order & Hierarchy

Maintenance Priority Malfunction Catalogs

Subject Areas Service Notification Section

Attribute Name Unit Of Measure Work Center & Hierarchy

Dimension Tables UNIT_OF_MEASURE WORK_CENTER, WORK_CENTER_HIER, WORK_CENTER_HIER_HZ, WORK_CENTER_HIER_VR, WORK_CENTER_HIER_BAD

Fact Table Fields

Subject Areas Service Notification Section