Sales RM User Guide

SAP BusinessObjects Sales 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 Related Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 Sharing components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 SAP BusinessObjects Sales Rapid Mart, version for SAP solutions schema 24 Where the Rapid Mart fits in the customer order management cycle . . . . 25 Chapter 3 Subject Areas 27
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Sales Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Rapid Mart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 Backlog Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 Schedule Lines Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 Delivery Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
SAP BusinessObjects Sales Rapid Mart XI 3.2 for SAP solutions User Guide
Contents
Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 Billing Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 Sales Order History Preservation Section . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 Document Flow Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Rapid Mart Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 Rapid Mart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 On Time Delivery Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 Rapid Mart Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 Document Validation Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Rapid Mart Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76 Rapid Mart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Chapter 4 Reports 79
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Sales Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 Deliveries and On-Time Delivery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107 Billing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Summary Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Backlog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Sample report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 Schedule Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Contents
Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129 Sales Order History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133 Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 Document Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139 Invalid Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141 Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143 SAP Master Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144 Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158 Recommended table joins Chapter 5 Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159 163
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Universe Design Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 Universe Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165 Universe Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Join Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167 Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Hierarchies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169 Geographic Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Time Dimension and Fiscal Period Hierarchies . . . . . . . . . . . . . . . . . 171 Material Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 Horizontal & Vertical Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172 Hierarchy Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 SAP Sales Analysis Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183 Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184 Common Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186 Fact Table Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Contents
Sales Orders & Backlog Subject Area . . . . . . . . . . . . . . . . . . . . . . . . 197 Schedule Lines Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202 Deliveries Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204 Billings Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209 Sales Order History Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212 Document Flow Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215 Current On Time Delivery Subject Area . . . . . . . . . . . . . . . . . . . . . . . 217 History On Time Delivery Subject Area . . . . . . . . . . . . . . . . . . . . . . . . 221 Invalid Documents Subject Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224 Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226 Using Fact Tables as Dimensions to Other Fact Tables . . . . . . . . . . . 227 SAP Master Data Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 Universe Objects & Classes - Master Data . . . . . . . . . . . . . . . . . . . . . 230 Universe Validation - Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 265 Customizing the SAP Sales Analysis Universe . . . . . . . . . . . . . . . . . . . . . 267 Chapter 6 Installing the Rapid Mart 269
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270 System Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271 Personnel Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272 Rapid Mart product components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273 Preparing your environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Preparing Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275 Preparing Target Database Environment . . . . . . . . . . . . . . . . . . . . . . 275 Preparing Source Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 Preparing BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . 276 Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276 The Rapid Mart Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278 Install the Rapid Mart Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Create Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279 Install the Data Services Job(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Renaming the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282 Import ATL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Contents
Adjusting the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286 Using Auxiliary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293 Using ABAP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294 Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298 Installing Rapid Mart Reporting Content . . . . . . . . . . . . . . . . . . . . . . . . . 300 Import Wizard for Reporting Content BIAR File . . . . . . . . . . . . . . . . . 300 Creating Universe Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316 Chapter 7 Using the Rapid Mart 319
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320 Data Services automatic recovery feature . . . . . . . . . . . . . . . . . . . . . 320 Rapid Mart recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321 Execution status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 The execution status table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322 The execution status API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323 Executing a job with the Reset option . . . . . . . . . . . . . . . . . . . . . . . . 324 Extraction, transformation and loading process . . . . . . . . . . . . . . . . . . . . 324 Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Global Variable Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 326 Used in All Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330 Used in 2 to 10 Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333 Used in Only 1 Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339 Setting Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353 Executing the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Initial (First) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357 Incremental (Delta) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . 358 Customizing the Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359 Chapter 8 Technical Implementation 361
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Sales order section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362 Dimension Table Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Contents
Initial load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366 Incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369 Processes completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 370 Delivery section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Dimension table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373 Initial load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376 Incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Processes completed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377 Billing section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Dimension table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379 Initial load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382 Incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383 Backlog section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Dimension table load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384 Initial and incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 Schedule lines section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393 Initial and incremental load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395 Sales order history preservation section . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Dimension load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396 Initial and Incremental Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398 On Time Delivery Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 Dimension Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400 On Time Delivery Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402 Optimization Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 Table Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407 Data Transfer Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409 Hierarchy Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411 Dealing with NULL values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413 Fact Table Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415 Fiscal Periods & Time Dim Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Contents
Chapter 9
Documentation References
419
Data Services Documentation References . . . . . . . . . . . . . . . . . . . . . . . 420 BusinessObjects Enterprise Documentation References . . . . . . . . . . . . 420 Appendix A Rapid Mart Data Schema 423
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-ofthe-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 reuse. 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 Sales 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 in the Rapid Mart, including the processes each section captures Chapter 4: Reports Provides examples of reports you can produce Chapter 5: Universe Describes SAP BusinessObjects Universe upon which the reports are based Chapter 6: Installing the Rapid Mart Contains the information you need to install the Rapid Mart Chapter 7: Using the Rapid Mart Describes how to execute the Rapid Mart, including information about initializing variables and 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 Sales 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 Sales Rapid Mart, version for SAP solutions schema Where the Rapid Mart fits in the customer order management cycle
What you can do with this Rapid Mart

The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions supports analysis of data in the Sales and Distribution (SD) module of SAP solutions. This module allows businesses to manage products, sales, and services and to manage their performance with customers and other business partners. Using this Rapid Mart, you can:
Analyze sales trends Determine customer behavior Forecast product sales with greater accuracy Plan product life cycles Track deliveries you make to your customers Track On Time Delivery Performance Report Bookings, Billings, Backlog in SAP solutions Document Currency or your Global Currency
The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions addresses three sub-modules of SD:
Sales (SD-SLS) Shipping (SD-SHP) Billing (SD-BIL)
18
Overview What you can do with this Rapid Mart
With the SAP BusinessObjects Sales Rapid Mart, version for SAP solutions you can answer the following kinds of questions:
How are new product features affecting sales? How do sales vary by region? What is the average delivery time for a product? How well are we meeting our scheduled deliveries to customers? How well are we planning our deliveries for our customers? How do distribution, pricing, and promotional activities compare across geographically diverse locations and various time periods? Are we fulfilling our commitments to customers in a timely fashion? What would our revenue have been if all originally entered sales orders had been fulfilled? What are the trends in my sales orders history? What are my monetary exchange rate variances between my document currency and Global currency? How do my bookings (sales orders) compare to my billings in a given time period? How many credit memos are we issuing? What impact do credit memos have on revenue?
19
Overview Supported analyses
Supported analyses
The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions supports several types of analyses. Business function Sales Orders (Bookings) Types of analysis Sales Measures available in the Rapid Mart
Sales order volumes and trends across time at summary level for the enterprise or any level down to individual line-item information Sales ranking by customer, product, sales representative, region, or sales type Detailed sales order analysis by customer, product, sales representative, region, sales type Customer requests fulfillment in terms of delivery dates and quantities Sales orders of return category Return trends over time by customer, product, region, sales type Un-delivered sales orders Un-billed sales orders Days Early or Late (Customer Requested Delivery Date vs. Planned Delivery Dates). Compare Returns vs. Sales (booking) Trends Average order-to-delivery cycle time Cycle time patterns between order and delivery by customer, product, sales office Comparison of scheduled and actual material availability, loading, goods issue, and delivery dates Backlog quantities by customer, product, region Completion status by customer, product, region Shipped products for revenue recognition
Returns
Backlog Schedule Lines
By Delivery By Billing Planning
Delivery
Efficiency
Service Level
20
Overview Supported analyses
Business function Billing
Types of analysis Discounting
Measures available in the Rapid Mart
Trends for discounting by product over time for different customers Relationship between discounting and sales volume Base price to discount price and product cost comparisons to identify margins and time by product Revenue over time by customer, product, sales organizations What if revenue analysis Deletion of sales orders by sales person, by product, by customer Unfulfilled Sales Orders Sales Order fulfillment Lifecycle (sales order creation to billing time) Lifecycle by customer, product, sales representative, region, sales type Average Days Delivery is Early or Late Quantities Early or Late Net Value Early or Late On Time Delivery Performance Sales Orders rejected by the Data Services Billings rejected by the Data Services
Margins Revenue Sales Order History Document Flow Sales order changes preservation Sales Order Lifecycle
On Time Delivery
By Schedule Line or Delivery
Invalid Documents by Sales Order or Billing
To support these analyses, the SAP BusinessObjects Sales Rapid Mart, version for SAP solutions contains a number of dimension tables. Tables extracted from SAP solutions master data and customizable tables include enterprise entities such as country, region, currency, plant, customer, and material data. Tables extracted from the SD module include pricing, organizational elements and their hierarchies (sales organization, division, distribution channel, sales office, sales group, sales person), and sales documents.
21
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 Sales Rapid Mart, version for SAP solutions are related to other SAP BusinessObjects Rapid Mart components. For example:
Sales orders for make-to-order materials are included in the:
SAP BusinessObjects Inventory Rapid Mart, version for SAP solutions - linked by material movements. SAP BusinessObjects Production Planning Rapid Mart, version for SAP solutions - linked by reservations, and production orders.
These linkages give a complete view of the manufacturing process.
Sales orders for Purchased materials are tracked in the:
SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions. - linked by purchasing documents, goods receipts, and invoice receipts. SAP BusinessObjects Accounts Payable Rapid Mart, version for SAP solutions - linked by purchasing documents (financial view) and vendor financial documents.
Tracking of customer payments for sales billings are included in the SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions.
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
22
Overview Related Rapid Marts
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 an Data Services job by a C_ prefix before its name. For example, the component that contains sales order and the associated reporting dimensions is named C_SalesOrder_Section.
23
Overview SAP BusinessObjects Sales Rapid Mart, version for SAP solutions schema
SAP BusinessObjects Sales Rapid Mart, version for SAP solutions schema
The following diagram shows an overview of the SAP BusinessObjects Sales Rapid Mart, version for SAP solutions Star Schema Layout. Tables in the center of the diagram are the fact tables and correspond to particular sections; the side boxes contain dimension tables that may apply to multiple sections.
24
Overview Where the Rapid Mart fits in the customer order management cycle
Additionally the Sales Rapid Mart includes the following hierarchy, staging, validation, and auxiliary tables that are not organized as a star schema:
Where the Rapid Mart fits in the customer order management cycle
The SAP solutions customer order management cycle consists of the following elements:
Pre-sales activities (such as quotations, inquiries, contracts, and scheduling agreements) Sales order processing Inventory sourcing Delivery Billing Payment
25
Overview Where the Rapid Mart fits in the customer order management cycle
Other Rapid Marts (see Related Rapid Marts on page 22) fit into the Order Management Cycle as shown below:.
26
Subject Areas
chapter
Subject Areas Overview
Overview
Each section in the SAP BusinessObjects Sales 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 to understand the data in the Rapid Mart and how it relates to SAP solutions. This chapter discusses:
Sales Order Section Backlog Section Schedule Lines Section Delivery Section Billing Section Sales Order History Preservation Section Document Flow Section On Time Delivery Section Document Validation Section
Sales Order Section

A sales order is a document that captures and records customer commitment to purchase goods or services. The sales order contains all the information needed to process the customer commitment throughout the SD module. The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions has no restrictions on sales document categories. The sales order section captures:
sales orders, returns, credit and debit memo requests, pre-sales documents, such as
quotes, inquiries, contracts, scheduling agreements.
When creating a sales order, SAP solutions copies default information from the following:
28
Subject Areas Sales Order Section
Customer master Material master Condition records for pricing Pre-set configuration for shipping point and route
SAP solutions can create a sales order that references another sales document, such as a quote, an inquiry, scheduling agreement, or a contract. SAP solutions can overwrite copied information for a particular sales order. SAP solutions supports many types of sales transactions within sales order processing, including:
Standard order Product request from a customer with 'normal' delivery requirements Rush order Product request from a customer with immediate delivery Returns authorization Product return from a customer Delivery free of charge Product delivered to a customer with no charge Consignment Product sent to a customer but paid for only as it is used Service Contracts Used by the SAP solutions Service Module Quotation Initial quote to a customer before sales order is created. Can be turned into a sales order once the sale is agreed to. Debit Memo Request A precursor to a Debit Memo. These are instructions for additional charges to a customer. Credit Memo Request A precursor to Credit Memo. These are instructions to reduce charges to a customer. Inquiries A precursor to a quotation. A Customer can ask for detailed information about specific goods, in particular their prices.
The sales order section extracts order-related data from SAP solutions header and line item tables. The section stores the transactions for individual sales order documents in the SALES_ORDER_FACT table. This section does not store the history of data changes to sales orders. Sales order processing in Data Services for the Rapid Mart has two major branches. The first is the initial load. This is a full refresh of all sales orders in the SAP solutions system. Typically, you will run this refresh only once when you first implement the Rapid Mart. The second branch is the incremental or delta load of the sales orders. The Data Services keeps track of the run date for each Rapid Mart refresh, including the first. Subsequent refreshes load only those sales orders that have been added, deleted, or changed in SAP solutions since the previous refresh.
29
Note: The Rapid Mart treats deleted sales orders differently than SAP solutions. In SAP solutions the sales orders are physically deleted from the database. However, the Rapid Mart does not delete the records, but assigns them a reject code. Both the first and incremental refreshes use a staging table to prepare sales order information for the Rapid Mart. The table is named SALES_ORDER_STAGE. Data extracted from SAP solutions is loaded here first. Further transformations of the data take place in the stage table. These include lookup of Global Currency exchange rates and of the ship to address for each sales order Once the staging table is fully updated, the global currency exchange rates lookups are validated using a Validation transform in the Rapid Mart. Rows that do not validate are written to the SALES_ORDER_FACT_BAD table. Rows that pass validation update the SALES_ORDER_FACT table. See the Document Validation Section later in this chapter for more details.
Rapid Mart processing

Sales orders are stored in the SALES_ORDER_FACT table of the target database. Additionally, this section captures the following dimensional attributes and their associated dimension tables. Attribute Billing Block Central Address Company Code Controlling Area Credit Control Area Credit Management Risk Class Monetary Currency Customer Customer Group Delivery Block Delivery Route Distribution Channel Division Dimension Table Names BILLING_BLOCK CENTRAL_ADDRESS COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_AREA CREDIT_MGMT_RISK_CLASS CURRENCY CUSTOMER CUSTOMER_GROUP DELIVERY_BLOCK DELIVERY_ROUTE DISTRIBUTION_CHANNEL DIVISION
30
Attribute Document Category Document Type Inter Company Terms Material & Product Hierarchy Material Alternate Unit of Measure Material By Plant Material Group Order Reason Payment Term Plant Pricing Procedure (Horizontal & Vertical) Profit Center & Hierarchy
Dimension Table Names DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY INTER_COMPANY_TERM01 MATERIAL, PRODUCT_HIERARCHY MATERIAL_ALT_UOM MATERIAL_BY_PLANT MATERIAL_GROUP ORDER_REASON PAYMENT_TERM PLANT PRICING_PROCEDURE_HZ, PRICING_PROCEDURE_VR PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_BAD, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR REJECT_REASON SALES_DISTRICT SALES_GROUP SALES_OFFICE SALES_ORDER_STATUS SALES_ORGANIZATION, SALES_ORGANIZATION_HIER SALES_PERSON SHIPPING_POINT STORAGE_LOCATION TIME_DIM UNIT_OF_MEASURE
Reject Reason Sales District Sales Group Sales Office Sales Order Status Sales Organization & Hierarchy Sales Person Shipping Point Storage Location Time Dimension Unit Of Measure
Fact Table Fields

The SALES_ORDER_FACT table contains the following measures
31
Note: The suffix GBL is for Global Currency. The suffix TRX is for transaction (or Document) Currency.: Col. Name AMT_NET_PRICE_GBL Description VBAP-NETPR - Net Price -after discounts and surcharges are applied, but excluding tax - Global Currency VBAP-NETPR - Net Price -after discounts and surcharges are applied, but excluding tax - Transaction Currency VBAP-NETWR - Net value of the order line item in Global currency
AMT_NET_PRICE_TRX
AMT_NET_VALUE_GBL
AMT_NET_VALUE_HDR_GBL VBAK-NETWR - Net value of the order (all line items) in Global currency AMT_NET_VALUE_HDR_TRX VBAK-NETWR - Net value of the order (all line items) in transaction currency AMT_NET_VALUE_TRX AMT_RECEIVED_GBL VBAP-NETWR - Net value of the order line item in transaction currency Calculated field: for sales documents of categories A or B it is 0, for sales documents of categories H or K without rejection reasons it is set to a negative of the net item value, for the rest sales documents without rejection reasons it is the net item value - In Global Currency Calculated field: for sales documents of categories A or B it is 0, for sales documents of categories H or K without rejection reasons it is set to a negative of the net item value, for the rest sales documents without rejection reasons it is the net item value - In Transaction Currency VBAP-WAVWR - Cost in transaction currency VBAP-WAVWR - Cost in transaction currency VBAP-KZWI1 - Customer-configurable subtotal 1 VBAP-KZWI1 - Customer-configurable subtotal 1
AMT_RECEIVED_TRX
AMT_STD_COST_GBL AMT_STD_COST_TRX AMT_SUBTTL_01_GBL AMT_SUBTTL_01_TRX
32
Col. Name AMT_SUBTTL_02_GBL AMT_SUBTTL_02_TRX AMT_SUBTTL_03_GBL AMT_SUBTTL_03_TRX AMT_SUBTTL_04_GBL AMT_SUBTTL_04_TRX AMT_SUBTTL_05_GBL AMT_SUBTTL_05_TRX AMT_SUBTTL_06_GBL AMT_SUBTTL_06_TRX AMT_TRGT_GBL AMT_TRGT_TRX QTY_CONFIRM_SLSUOM QTY_ORDER_SLSUOM QTY_PRICE_UNIT QTY_RECEIVED_SLSUOM
Description VBAP-KZWI2 - Customer-configurable subtotal 2 VBAP-KZWI2 - Customer-configurable subtotal 2 VBAP-KZWI3 - Customer-configurable subtotal 3 VBAP-KZWI3 - Customer-configurable subtotal 3 VBAP-KZWI4 - Customer-configurable subtotal 4 VBAP-KZWI4 - Customer-configurable subtotal 4 VBAP-KZWI5 - Customer-configurable subtotal 5 VBAP-KZWI5 - Customer-configurable subtotal 5 VBAP-KZWI6 - Customer-configurable subtotal 6 VBAP-KZWI6 - Customer-configurable subtotal 6 VBAP-ZWERT - Target value for outline agreement in transaction currency VBAP-ZWERT - Target value for outline agreement in transaction currency VBAP-KBMENG - Cumulative confirmed quantity in sales unit VBAP- KWMENG - Cumulative Order Quantity in Sales Units VBAP-KPEIN - Condition pricing unit Calculated field: for sales documents of categories A or B it is 0, for sales documents of categories H or K without rejection reasons it is set to a negative of the sales qty, for the rest sales documents without rejection reasons it is the sales qty VBAP-ZMENG - Target quantity in sales units
QTY_TRGT_SLSUOM
33
Status fields (for the whole document and for each line item) for tracking sales orders include: Col. Name BILL_STATUS_ID BILL_STATUS_ID_HDR DELIV_STATUS_ID Description VBUP-FKSAA - Billing Status of ORder-Related BIlling Document VBUK-FKSAK - Billing Status of ORder-Related Billing Document (lookup) VBUP-LFGSA - Overall Delivery Status of the Item
DELIV_STATUS_ID_HD VBUK-LFGSK - Overall Delivery Status of the R Item (lookup) INCOMPLT_STATUS_ID VBUP-UVALL - General Incompletion Status of the Item INCOMPLT_STATUS_ID VBUK-UVALL - General Incompletion Status of _HDR the Item PROCESS_STATUS_ID VBUP-GBSTA - Overall Processing Status of the SD item PROCESS_STATUS_ID VBUK-GBSTK - Overall Processing Status of the _HDR SD item (lookup) REF_STATUS_ID REF_STATUS_ID_HDR REJECT_STATUS_ID VBUP-RFGSA - Overall status of reference VBAK-RFGSK - Total reference status of all items VBAP-ABSTA - Rejection status for SD item
REJECT_STATUS_ID_H VBUK-ABSTK - Rejection status DR SALES_DOC_STATUS_ Concatenated values of Sales Document Status KEY fields Other important attributes (fields) of the SALES_ORDER_FACT table are: Col. Name CURR_ID_GBL CURR_ID_STATS CURR_ID_TRX CURR_ID_TRX_HDR Description Global Currency (Global Variable Set in Rapid Mart Job) VBAK-STWAE - Statistics currency VBAP-WAERK - Line Item transaction currency VBAK-WAERK - Document header Currency code
34
Col. Name CUSTOMER_ID_BILLT O
Description VBPA-KUNNR - Bill-to Customer Number (lookup)
CUSTOMER_ID_SHIPT VBPA-KUNNR - Ship-to Customer Number O (lookup) CUSTOMER_ID_SOLD TO EXCH_RATE_GBL EXCH_RATE_STATS EXCH_TYPE_ID_GBL EXCH_TYPE_ID_STAT S VBAK-KUNNR - Sold-to Customer Number TCURR.UKURS - Exchange rate from transaction currency to Global Currency VBAP-STCUR - Exchange rate for statistics (Exch.rate at time of creation) Global Exchange Rate Type (Global Variable Set in Rapid Mart Job) VBAK.KURST - Exchange rate type
SALES_TO_BASE_DIVI VBAP-UMVKN - Denominator (divisor) for SOR conversion of sales qty. into Stock-keeping unit of measure SALES_TO_BASE_MUL VBAP-UMVKZ - Numerator (factor) for conversion TIPLR of sales quantity into Stock-keeping unit of measure VALID_FROM_DATE VALID_TO_DATE VBAK-GUEBG - Valid-from date (outline agreements, product proposals) VBAK-GUEEN - Valid-to date (outline agreements, product proposals)
35
Rapid Mart Data

The sales order section includes sales transaction detail. The SALES_ORDER_FACT stores these details. SALES_ORDER_FACT and associated dimensions are organized as a star schema as shown below:
36
Analysis
With the tables in this section, you can analyze sales orders along several dimensions:
By material By customer By sales organization elements By order reason By rejection reason By billing or delivery blocking codes By various sales order statuses By profit center and associated hierarchy By various sales order operational dimensions By time period vs. previous period, quarter vs. previous quarter, year vs. previous year What was the top selling product in the line last quarter, last year? Who is our top sales rep. in the company? What are our sales trends in this region for the last 5 years? How have our sales numbers per sales office changed since the sales groups reassignments? How well do we honor our contract obligations? Who are our 10 biggest customers by bookings value? How do my sales vary seasonally (or quarterly)? Which customers are most satisfied / dissatisfied (as measured by returns)? Which materials (or products) are my best sellers? Which products are not well received by my customers (as measured by slow sales and high rate of returns)? Which factories (or plants) are processing the most bookings? Which operating company had the most sales this quarter? This year? What are the gross margins on each product line we sell? Which sales district generated the most bookings last year? Did our bookings numbers look better using last years sales organization structure or this years? How do my bookings compare to my billings for this quarter? This year?
Typical queries include:
37
Subject Areas Backlog Section
Backlog Section
The backlog section stores backlog quantities for open sales orders. The section calculates the backlog as the difference between booked quantities and shipped quantities. All backlog processing takes place in the Rapid Mart. It is important that Sales Orders, Deliveries, and Billings be loaded before backlog processing, as backlog relies on data from those subject ares. The backlog section calculates backlog using the SALES_ORDER_FACT and DELIVERY_FACT tables. Additionally, in the case of drop shipment or intangible delivery orders, the backlog section also uses the BILLING_FACT table. For a sales order item line item, the backlog is the quantity that has not been delivered yet (the ordered quantity less the delivered quantity.) The backlog section stores this data in the BACKLOG_FACT table. The section uses several rules when calculating backlog:
Includes sales orders of category 'C.' The Rapid Mart makes use of the fact that a delivery line item refers to one and only one sales order line item.
Excludes contracts and scheduling agreements. Contracts are sales orders that eventually turn into category 'C' orders. You can customize the Rapid Mart to include contracts and scheduling agreements by allowing categories 'E' and 'G.'
Excludes billed line items with no delivery information. Note: Drop Shipments / Intangible Deliveries Some companies use drop shipments (third-party delivery). In this case, a sales order line item has the Billing Relevant indicator set to B or F. No Delivery document is generated in your SAP solutions system (as the third party does that). However, an invoice is produced and backlog is reduced by the invoice rather than the delivery. The Billing Relevant indicator is also set to B or F in cases of an intangible delivery. That is a delivery where no physical material is delivered, such as when a service is purchased. If you use drop shipments or intangible deliveries, set the $G_DROP_SHIP global variable to Y (yes). The Rapid Mart will segregate these orders and reduce backlog when invoices are generated for these orders (ordered quantity less invoice quantity).
38
With every incremental load, the section removes deleted or cancelled orders from the BACKLOG_FACT table. It also removes orders that are fully delivered and therefore no longer backlog. As an alternative backlog calculation you can use SALES_DOC_FLOW_VIEW. The view represents a union of SALES_ORDER_FACT, DELIVERY_FACT, and BILLING_FACT. It has fact table common attribute fields such as sales order number, customer id, material id, sales document category id. In addition, it contains fact table measurement fields, such as sales order requested quantity, net item value, delivery quantity, billing document quantity and net item value. Aggregating by common fields you can calculate the difference between ordered, delivered, and billed quantities and amounts by sales order number, by customer, by material.

Backlog is stored in the BACKLOG_FACT table. Which is associated with the following dimensional attributes and dimension tables. Additionally, in the universe, BACKLOG_FACT is joined to SALES_ORDER_FACT as both tables have the same primary key. This allows the use of any Sales Order dimension with Backlog. Attribute Company Code Controlling Area Customer Material & Product Hierarchy Material By Plant Plant Dimension Table Name COMPANY_CODE CONTROLLING_AREA CUSTOMER MATERIAL, PRODUCT_HIERARCHY MATERIAL_BY_PLANT PLANT
Profit Center & Hierarchy PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_BAD, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_VR Storage Location Time Dimension STORAGE_LOCATION TIME_DIM
39
Fact Table Fields

The Backlog table includes the following measures:
Col. Name QTY_BACKLOG_SLSUOM Description
Regular Backlog: SALES_ORDER_FACT.QTY_ORDER_SLSUOM DELIVERY_FACT.QTY_DELIV_SLSUOM Third Party (Drop Ship) Backlog: SALES_ORDER_FACT.QTY_ORDER_SLSUOM BILLING_FACT.QTY_BILL_SLSUOM
QTY_DELIV_SLSUOM QTY_ORDER_SLSUOM
DELIVERY_FACT.QTY_DELIV_SLSUOM - Actually Delivered Qty SALES_ORDER_FACT.QTY_ORDER_SLSUOM Cumulative Sales Order Qty
Rapid Mart data

BACKLOG_FACT and associated dimensions are organized as a star schema as shown below.
40
Analysis
With the dimensions in this section, plus sales order dimensions you can analyze backlog along several dimensions:
By customer By material By sales organization elements By period vs. previous period, quarter vs. previous quarter, year vs. previous year By any sales order attribute. What was ordered but not delivered yet, listed by customer and product? What was ordered, delivered but not billed yet by plant? What is the gap between ordered and delivered products in this quarter? Which products have the greatest delivery backlog? Who is the most unsatisfied customer in terms of unfulfilled orders? Where is my greatest revenue potential as measured by backlog? By customer? By Sales Organization? By material? How old is my backlog? (How long are customers waiting for delivery?)
All dimensions associated with sales orders can be used with backlog. Refer to the Sales Order Section -Analysis in this chapter for more details.
41
Subject Areas Schedule Lines Section
Schedule Lines Section

The schedule lines section extracts detailed information about scheduled deliveries for sales orders. In SAP solutions, all sales documents have the same structurea document header with any number of items. The items can have any number of schedule lines.
A schedule line contains all the data needed for a delivery. For example, suppose a customer orders 20 units of a particular material. You enter this as one item in the sales order. Suppose, however, that you can only deliver 15 pieces now. The customer wants the remaining 5 pieces next month. In this case, you need to schedule two deliveries. SAP solutions stores the data for these deliveries (dates, confirmed quantities, and so forth) in two separate schedule lines. These schedule lines differ by delivery date and quantity. Schedule lines can also have different control elements. For example, material requirements planning might be completed for some schedule lines but not other schedule lines. Similarly, schedule lines defined in a returns document post a goods receipt, not a goods issue. Data recorded in schedule lines includes:
Schedule line quantity Schedule Line Date Delivery Date (also called Planned Delivery Date in SAP solutions) Goods Issue Date (also called Planned Goods Issue Date in SAP solutions) Sales Order Create Date Requested Delivery Date (from the sales order)
42
Loading Date Material Available Date Transportation Planning Date Confirmed Quantity Order Quantity Rounded Quantity Required Quantity
For sales documents where delivery data is not relevantfor example, in contracts, credit and debit memo requestsSAP solutions does not create schedule lines. The schedule lines section extracts detailed scheduled delivery information for sales orders from SAP solutions table VBEP into the SALES_SCHED_LINE_FACT table. This table only contains information for relevant sales orders. Some sales documents, such as inquiries, quotations, and contracts, do not contain delivery data, and therefore have not schedule lines. The section uses the same approach SAP solutions uses for handling deleted schedule lines information. When SAP solutions removes an existing sales order or sales order line item and all related schedule lines, the Rapid Mart removes the corresponding records from the schedule line fact table. This section only extracts current information. This section does not store historical information. The section uses an initial full load strategy, followed by subsequent incremental (delta) loads. Only schedule lines added, changed, or deleted since the previous Rapid Mart refresh are loaded in an incremental load.

Schedule Lines include the following dimensional attributes and associated dimension tables: Attribute Delivery Block Material & Product Hierarchy Material Alternate Unit of Measure Material by Plant Material Group Dimension Table Name DELIVERY_BLOCK MATERIAL, PRODUCT_HIERARCHY MATERIAL_ALT_UOM MATERIAL_BY_PLANT MATERIAL_GROUP
43
Attribute Plant Time Dimension Unit of Measure
Dimension Table Name PLANT TIME_DIM UNIT_OF_MEASURE
Fact Table Fields

The schedule lines include the following measures: Column Name DAYS_EARLY_LATE Description Difference between Requested Deliv. Date (VBAK.VDATU) and Planned Goods Issue Date (VBEP.WADAT). A negative number indicates Late Delivery. A positive number indicates Early Delivery. VBEP-CMENG - Corrected quantity in sales unit VBEP-BMENG - Confirmed quantity - sales units Order quantity in Base Units VBEP-WMENG - Order quantity in sales units
QTY_ADJUST_SLSUOM
QTY_CONFIRM_BASEUOM Confirmed quantity in Base Units QTY_CONFIRM_SLSUOM QTY_ORDER_BASEUOM QTY_ORDER_SLSUOM
These are additional important attributes for the Schedule Line: Column Name DELIV_DATE GI_DATE MTRL_AVAIL_DATE RQST_DELIV_DATE SCHED_LOAD_DATE Description VBEP-EDATU - Delivery date for the schedule line VBEP-WADAT - Goods issue date VBEP-MBDAT - Material availability date VBAK-VDATU - Proposed schedule line date VBEP-LDDAT - Scheduled Loading date
TRANSPORT_SCHED_DATE VBEP-TDDAT - Transportation scheduling date Additional information on these attributes:
DELIV_DATE (also called Planned Delivery Date in SAP solutions) A requested delivery date or confirmed delivery date. This is the date you expect the customer to receive the goods.
44
For most sales orders, SAP solutions creates schedule lines automatically. When you enter a requested delivery date for a sales order or a sales order line item, SAP solutions runs a material availability check to calculate a confirmed delivery date. If the requested quantity can be delivered on the requested date, SAP solutions creates one schedule line. If the requested quantity cannot be delivered as requested, SAP solutions creates multiple schedule lines. The first line contains the requested delivery date in the DELIVERY_DATE field. Subsequent lines have confirmed delivery dates in this field.
GI_DATE (also called Planned Goods Issue Date in SAP solutions) The date when the goods should leave the shipping point. Calculated by adding loading lead time to the loading date.
MTRL_AVAIL_DATE The date when the goods are available and the delivery process can begin.
RQST_DELIV_DATE The requested delivery date from the sales order header. This is used to calculate the delivery date (above). It is also used in measuring how well we are planning vs. customer requests.
SCHED_LOAD_DATE The date when the goods are scheduled to be loaded for transport. SAP solutions calculates by adding the pick, pack, and stage lead times to the material availability date.
TRANSPORT_SCHED_DATE The date when transportation planning is scheduled to start. Calculated by subtracting transportation lead time from the load date.
45
Rapid Mart data

SALES_SCHED_LINE_FACT and associated dimensions are organized as a star schema as shown below
Analysis
With the tables in this section, you can analyze scheduled deliveries for sales orders along several dimensions:
By material and its product hierarchy By customer By sales organization elements By time period vs. previous period, quarter vs. previous quarter, or year vs. previous year. How many sales orders can not meet the customers requested delivery date? How often do we need to schedule multiple deliveries for a single order line item because we do not have enough quantity in stock to satisfy the demand? How well are we planning to meet customer requested delivery date? When are our deliveries scheduled? (By month, quarter, or year) What are our average days early (or late) meeting customer requested delivery dates?
46
Subject Areas Delivery Section
Delivery Section
This section extracts information about deliveries, return deliveries, shipments, and shipping notifications from SAP solutions. Creating the delivery document signals the start of the shipping activities for the sales order. It is the electronic means to manage all the activities of delivery processing, including picking product, packing, planning and monitoring shipments, preparing shipping papers, and goods issue documents. Delivery includes several shipping processes that take place within the plant. When the product is available and ready to be processed in the warehouse, a shipping scheduler creates a delivery document so that the warehouse can efficiently pick, stage, and release (goods issue) the product to the customer. When creating a delivery document that references a sales order, SAP solutions copies critical shipping information from the sales order into the delivery document. SAP solutions can overwrite some of this information (such as quantities to deliver) on a particular delivery document. The delivery section extracts delivery information from the SAP solutions tables at the header (Table LIKP) and line-item levels (table LIPS). The section stores the extracted data in a fact table called DELIVERY_FACT. The section extracts all categories of delivery documents, including delivery, returns delivery, shipment, and shipping notification. The section stores the latest version of each delivery. This section does not store the history of data changes to deliveries. The Rapid Mart has an initial (first) load and an incremental (delta) load. Unlike the Sales Orders section, this load does not use a Stage table. Both the initial and incremental loads are direct to the Delivery Fact table. Note: This section follows the convention of SAP solutions for handling deleted delivery information. Existing deliveries or delivery line items that are deleted within SAP solutions are also removed from the delivery fact table. Note: The Rapid Mart does not maintain global currency values for deliveries. However, the SAP BusinessObjects Universe calculates global currency values using the exchange rates from the associated sales order.
47

Deliveries include the following dimensional attributes and associated dimension tables. Attribute Name Billing Block Company Code Controlling Area Credit Control Area Credit Mgmt Risk Class Monetary Currency Customer Customer Group Delivery Block Delivery Priority Delivery Route Delivery Status Distribution Channel Division Document Category Document Type Inter Company Terms Material & Product Hierarchy Material Alternative Unit of Measure Material By Plant Material Group Plant Pricing Procedure (Horizontal & Vertical) Dimension Table BILLING_BLOCK COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_AREA CREDIT_MGMT_RISK_CLASS CURRENCY CUSTOMER CUSTOMER_GROUP DELIVERY_BLOCK DELIVERY_PRIORITY DELIVERY_ROUTE DELIVERY_STATUS DISTRIBUTION_CHANNEL DIVISION DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY INTER_COMPANY_TERM01 MATERIAL, PRODUCT_HIERARCHY MATERIAL_ALT_UOM MATERIAL_BY_PLANT MATERIAL_GROUP PLANT PRICING_PROCEDURE_VR, PRICING_PROCEDURE_HZ
48
Attribute Name Profit Center & Hierarchy
Dimension Table PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_BAD, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_V SALES_GROUP SALES_OFFICE SALES_ORGANIZATION & SALES_ORGANIZATION_HIER SHIPPING_POINT STORAGE_LOCATION TIME_DIM UNIT_OF_MEASURE
Sales Group Sales Office Sales Organization & Sales Organization Hierarchy Shipping Point Storage Location Time Dimension Unit Of Measure
Fact Table Fields

Deliveries contain the following measures: Column Name AMT_STD_COST_TRX AMT_SUBTTL_01_TRX AMT_SUBTTL_02_TRX AMT_SUBTTL_03_TRX AMT_SUBTTL_04_TRX AMT_SUBTTL_05_TRX AMT_SUBTTL_06_TRX QTY_DELIV_BASEUOM QTY_DELIV_SLSUOM QTY_GROSS_WEIGHT Description LIPS-WAVWR - Cost in Document Currency LIPS-KZWI1 - CustomerConfigurable Subtotal 1 LIPS-KZWI2 - CustomerConfigurable Subtotal 2 LIPS-KZWI3 - CustomerConfigurable Subtotal 3 LIPS-KZWI4 - CustomerConfigurable Subtotal 4 LIPS-KZWI5 - CustomerConfigurable Subtotal 5 LIPS-KZWI6 - CustomerConfigurable Subtotal 6 LIPS-LGMNG - Actual Quantity Delivered (in Base Units) LIPS-LFIMG - Actual Quantity Delivered (in Sales Units) LIPS-BRGEW - Gross weight
49
Column Name QTY_NET_WEIGHT QTY_VOLUME
Description LIPS-NTGEW - Net weight LIPS-VOLUM - Volume
Note: AMT_SUBTTL_01_TRX - AMT_SUBTTL_06_TRX: These subtotals (in sales document currency) contain the values of certain pricing conditions used in a specific pricing procedure. Typically, Subtotal 1 is the List Price. Price calculation in SAP solutions depends on various factors such as:
Customer Sales order type Sales organization Quantity
Each delivery can have its own definition for what is contained in subtotal 1-6 fields. The descriptions of these fields are in the Pricing Procedure tables. Additional important fields in the DELIVERY_FACT table are: Column Name Status Columns Values: Blank = Not Applicable Description
A = Not yet processed B = Partially processed C = Completely Processed
BILL_STATUS_DELIV_RELTD_ID VBUP-FKSTA - Billing Status of Delivery-Related Billing Documents DELIV_STATUS_KEY GI_STATUS_ID Concatenated values of Sales Document Status fields VBUP-WBSTA - Goods Issue status (indicates whether goods have left the warehouse) VBUP-PKSTA - Packing status VBUP.KOQUA - Picking confirmation status VBUP-KOSTA - Picking Status VBUP-GBSTA - Overall processing status of the SD document item
PACKNG_STATUS_ID PICKNG_CONFIRM_STATUS_ID PICKNG_STATUS_ID PROCESS_STATUS_ID Date/Day Columns
50
Column Name ACTL_GI_DATE
Description LIKP.WADAT_IST - Actual Goods Issue Date. The date the goods actually left the shipping point. LIPS-VBEAF - Fixed Shipping Processing Time in Days (setup time). This field contains a fixed shipping processing time in days. This time is needed in shipping to process a specific quantity of a material in base units. An example is the time required to load a van that transports the material to a customer LIPS-VBEAV - Variable Shipping Processing Time in Days. This field contains the processing time in days for shipping a particular quantity of an item. It is used for capacity planning for deliveries. Formula: Confirmed_Qty x Processing_Time / BASE_QTY LIKP-LFDAT - Delivery Date. The date by which the delivery should be received by the customer. LIKP-LDDAT - Loading Date. The date by which picking and packing must be completed so that the goods are ready for loading and for the delivery to the customer LIPS-MBDAT - Material Availability Date. The date by which sufficient quantities of the item must be available for picking to begin LIKP-KODAT - Picking Date. The date by which picking must begin for the delivery item to reach the customer on time. LIKP-WADAT - Planned Goods Issue Date. The date on which the goods must physically leave the shipping point to reach the customer on time.
DAYS_FIXED_PROCESS
DAYS_SHIP_PROCESS
DELIV_DATE
DELIV_LOAD_DATE
MTRL_AVAIL_DATE
PICKNG_DATE
PLAN_GI_DATE
51
Rapid Mart data

The Delivery Fact and its associated dimensions form a Star Schema as shown below:
Analysis
With the tables in this section, you can analyze deliveries along several dimensions:
By material By customer By sales organization elements By region By plant By billing or delivery blocking codes By delivery priority
52
Which customers did not receive deliveries on the requested date? What is the average delivery time by product, by customer? How big are my shipments in terms of volume and weight monthly? What is the value of my deliveries, in global currency or document currency? How long between planned goods issue and actual goods issue? Which deliveries are in process right now?
53
Subject Areas Billing Section
Billing Section
The billing section extracts billing information from SAP solutions. The section extracts information about invoices, pro forma invoices, credit memos, and debit memos. After a material is shipped, an invoice is sent to the customer and a billing document is created. In the SD module, order processing ends with billing. SAP solutions creates a billing document by copying billing information from the sales order and/or delivery document. For example, copied information includes the name of the business partner who receives and verifies the invoice address, the name of the business partner who pays the invoice, the address and payment terms, and material and delivered quantity. SAP solutions can overwrite some of the copied data, such as price and quantity, for a particular billing document. Typically, when creating a billing document, SAP solutions automatically updates general ledger accounts. For example, SAP solutions debits the customer receivable account and credits the revenue account. The billing section extracts billing information from SAP solutions at header (table VBRK) and line item level (table VBRP). The section stores the extracted data in a fact table called BILLING_FACT. The section extracts all categories of billing documents, including invoices, credit and debit memos, pro-forma items, intercompany invoices, and intercompany credit memos. It also captures any cancellation documents such as a cancelled credit memo or invoice. The section stores the latest version of each billing document. The section does not store changes as a billing document history. Billings have an initial full load where all billing records are transferred from SAP solutions. Subsequent loads are incremental (Delta) loads where only changed, or cancelled billing documents are loaded into the Rapid Mart. Like sales orders, billings are first loaded to a BILLING_STAGE table. Here transforms such as the lookup of Global Currency exchange rates occur. Once the staging table is fully updated, these changes are validated using a Validation transform in the Rapid Mart. Rows that do not validate are written to the BAD_BILLING_FACT table. Rows that do pass validation update the BILLING_FACT table. See the Document Validation Section later in this chapter for more details.
54

Billings include the following dimensional attributes and associated dimension tables: Attribute Name Company Code Controlling Area Credit Control Area Monetary Currency Customer Customer Group Distribution Channel Division Document Category Document Type Fiscal Period Inter Company Terms Material & Product Hierarchy Material Alternative Unit of Measure Material By Plant Material Group Payment Term Plant Pricing Procedure Profit Center & Hierarchy Dimension Tables COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_AREA CURRENCY CUSTOMER CUSTOMER_GROUP DISTRIBUTION_CHANNEL DIVISION DOCUMENT_CATEGORY DOCUMENT_TYPE & DOCUMENT_CATEGORY FISC_PERIOD INTER_COMPANY_TERM01 MATERIAL, PRODUCT_HIERARCHY MATERIAL_ALT_UOM MATERIAL_BY_PLANT MATERIAL_GROUP PAYMENT_TERM PLANT PRICING_PROCEDURE_HZ, PRICING_PROCEDURE_VR PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_BAD, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_V SALES_DOC_STATUS SALES_GROUP SALES_OFFICE
Sales Document Status Sales Group Sales Office
55
Attribute Name Sales Organization & Sales Organization Hierarchy Shipping Point Storage Location Time Dim Unit Of Measure
Dimension Tables SALES_ORGANIZATION & SALES_ORGANIZATION_HIER SHIPPING_POINT STORAGE_LOCATION TIME_DIM UNIT_OF_MEASURE
Fact Table Fields

Billings contain the following measures: Column Name AMT_NET_VALUE_GBL Description VBRP-NETWR - Net Value (Global Currency)
AMT_NET_VALUE_HDR_GBL Net value in document currency (Global Currency) AMT_NET_VALUE_HDR_TRX VBRK-NETWR - Net Value of the billing document in Document Currency AMT_NET_VALUE_TRX AMT_REVENUE_GBL VBRP-NETWR - Net value of the line item in document currency Calculated field (Global Currency): for sales documents of categories U or 5 or 6 it 0, for sales documents of categories N or O it set to a negative of the net item value, for the rest sales documents it the net item value Calculated field: for sales documents of categories U or 5 or 6 it 0, for sales documents of categories N or O it set to a negative of the net item value, for the rest sales documents it the net item value VBRP-WAVWR - Cost in Global Currency VBRP-WAVWR - Cost in Document Currency VBRP-KZWI1 - Customer Configurable Subtotal 1 (Global Currency) VBRP-KZWI1 - Customer-Configurable Subtotal 1
AMT_REVENUE_TRX
AMT_STD_COST_GBL AMT_STD_COST_TRX AMT_SUBTTL_01_GBL AMT_SUBTTL_01_TRX
56
Column Name AMT_SUBTTL_02_GBL AMT_SUBTTL_02_TRX AMT_SUBTTL_03_GBL AMT_SUBTTL_03_TRX AMT_SUBTTL_04_GBL AMT_SUBTTL_04_TRX AMT_SUBTTL_05_GBL AMT_SUBTTL_05_TRX AMT_SUBTTL_06_GBL AMT_SUBTTL_06_TRX QTY_BILL_SLSUOM
Description VBRP-KZWI2 - Customer Configurable Subtotal 2 (Global Currency) VBRP-KZWI2 - Customer-Configurable Subtotal 2 VBRP-KZWI3 - Customer Configurable Subtotal (Global Currency) VBRP-KZWI3 - Customer-Configurable Subtotal 3 VBRP-KZWI4 - Customer Configurable Subtotal 4 (Global Currency) VBRP-KZWI4 - Customer-Configurable Subtotal 4 VBRP-KZWI5 - Customer Configurable Subtotal 5 (Global Currency) VBRP-KZWI5 - Customer-Configurable Subtotal 5 VBRP-KZWI6 - Customer Configurable Subtotal 6 (Global Currency) VBRP-KZWI6 - Customer-Configurable Subtotal 6 Calculated field = QTY_BILL_STOCKUOM X SALES_TO_BASE_DIVISOR / SALES_TO_BASE_MULTIPLR VBRP-FKLMG - Billing Qty in Stockkeeping Unit of Measure
QTY_BILL_STOCKUOM
Note: AMT_SUBTTL_01_TRX - AMT_SUBTTL_06_TRX and AMT_SUBTTL_01_GBL- AMT_SUBTTL_06_GBL: These subtotals (in transaction or global currency) contain the values of certain pricing conditions used in a specific pricing procedure. Typically, Subtotal 1 is the List Price. Price calculation in SAP solutions depends on various factors such as:
Customer Sales order type Sales organization Quantity
57
Each billing can have its own definition for what is contained in subtotal 16 fields. The descriptions of these fields are in the Pricing Procedure tables. Additional important fields in the BILLING_FACT table are: Column Name BILL_DATE BILL_DOC_ID_CANCEL Description VBRK.FKDAT - Billing Date or Invoice Date. VBRK-SFAKN - Cancelled billing document number. This field references either an invoice, a credit memo, or a credit memo list that has been cancelled by the current billing document. This field is only populated for billing documents of type cancellation, Calculated field - If the Billing document line item is cancelled it is set to 1 VBUP-GBSTA - Overall Processing Status of the SD item. This field allows you to monitor whether a line item is open, being processed, or complete. VBRP-VGBEL - Document number of the reference document (allows you to monitor a referenced delivery.) VBRP-VGPOS - Item number of the reference item (allows you to monitor a referenced delivery.)
DOC_CANCEL_FLAG PROCESS_STATUS_ID
REF_DOC_ID
REF_LINE_ITEM_ID
58
Rapid Mart data

The following diagram shows the billing tables organized as a star schema.
Analysis
With the tables in this section, you can analyze billing documents along several dimensions:
By material By customer By payer (can be different from Customer who placed a sales order) By sales organization elements By plant By billing document type By period vs. previous period, quarter vs. previous quarter, year vs. previous year via Fiscal Period Dimension By period vs. previous period, quarter vs. previous quarter, year vs. previous year via Time Dimension
59
What is the average time between booking a sales order and issuing a bill by customer and product? What are discount/margin trends by customer and product? What is the company revenue by month, quarter, and year? What is the difference between bookings and expected revenue? What are my gross margins? By material? By factory (plant)? Which customers have the most credit memos? What are billings by company code? By Sales Office? How do foreign currency exchange variances affect the bottom line? Are there seasonal variations in my revenue (Billings) flow? Who are my top 10 customers by revenue (Billings generated)?
60
Subject Areas Sales Order History Preservation Section
Sales Order History Preservation Section

The sales order history preservation section tracks changes to sales orders. By using this section, you can avoid querying SAP solutionss transaction log tables (CDHDR - the change document header table and CDPOS - the change line item table) to determine changes. In most cases, querying SAP solutions transaction logs is very resource intensive. Therefore, most SAP solutions sites avoid such queries. All Sales Order History Preservation processing takes place in the Rapid Mart. The sales order history preservation section extracts changes to a sales order and stores the changes in the SALES_ORDER_HISTORY table. In particular, the section stores these changes:
A sales order (or a sales order line item) is deleted and the requested quantity of the deleted line items and their net value become 0. The quantity of a sales order line item is increased or reduced. The line item net value is increased or reduced. When multiple changes occur in the same field of a sales order between two incremental loads, the Rapid Mart only captures the net effect of all the changes. The Rapid Mart does not detect deleted line items for free goods (goods with a net item value of 0) because the SAP solutions sales order header table does not change when such line items are deleted. The Rapid Mart does not capture sales orders that are created and deleted between two incremental loads.
There are limitations to the captured changes:
See Chapter 8: Sales order history preservation section for more details about how the section captures changes.

Sales Order History includes the following dimensional attributes and associated dimension tables: Attribute Name Company Code Controlling Area Currency Dimension Table COMPANY_CODE CONTROLLING_AREA CURRENCY
61
Attribute Name Customer Plant Profit Center & Hierarchy
Dimension Table CUSTOMER PLANT PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_BAD, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_V SALES_ORGANIZATION SALES_PERSON STORAGE_LOCATION TIME_DIM UNIT_OF_MEASURE
Sales Organization Sales Person Storage Location Time Dim Unit Of Measure
Fact table fields

Sales Order History contains the following measures: Column Name Description
AMT_NET_VALUE_DELTA_TRX Calculated change in net item value since last run. (A negative number indicates a decrease in net value) AMT_NET_VALUE_TRX VBAP-NETWR - Net Value of the Order Line Item in Document Currency for validity dates shown on this record. This is set to zero on a deleted record.
QTY_ORDER_DELTA_SLSUOM Calculated change in quantity since last run. (A negative number indicates the quantity decreased on the sales order.) QTY_ORDER_SLSUOM VBAP- KWMENG - Cumulative Order Quantity In Sales Units for validity dates shown on this record. This is set to zero on a deleted record.
62
Additional important fields in Sales Order History are: Column Name CURRENT_FLAG SURROGATE_KEY_ID Description C = Current version, H = Historical version (older version) A surrogate primary key generated by Data Services. (The natural primary key would be composed of the SALES_ORDER_NUMBER, SALES_LINE_ITEM_ID, and VALID_FROM_DATE columns.) Calculated date - Starting Validity Date for this Record Calculated date - Ending Validity Date for this Record
VALID_FROM_DATE VALID_TO_DATE
Example: history for a sales order: Original order is for 10 items at 10.00 each. (Total net value 100.00.) This is followed by a change in quantity, then a change in price, and finally order cancellation.
Surrogate Key Id 1 2 3 4 Current Valid Flag From Date H H H C 01-Jan2009 04-Jan2009 10-Jan2009 17-Jan2009 Valid To Date Qty Amt Order Net Slsuom Value Trx 10 100.00 7 7 0 70.00 84.00 0.00 Qty Order Delta Slsuom 10 -3 0 -7 Amt Net Value Delta Trx Comment
03-Jan2009 09-Jan2009 16-Jan2009 31-Dec9999
100.00 Original Order -30.00 Quantity Decreased by 3 14.00 Price Increased by 2.00 -84.00 Order Cancelled
The initialization values of these fields in the First Load (or for the new rows in incremental load) is configured with the $G_INIT_HIST_CHG global variable: they can be set to 0 if you want to be able to sum and obtain the total changes made to the orders, or they can be set to the values of the QTY_RECEIVED_SLSUOM and AMT_RECEIVED_TRX fields if you want to obtain the current values by summing. See Chapter 8: Sales order history preservation section for details about how this global variable is used.
63
Rapid Mart data

The sales order history preservation section complements the sales order section with an additional fact table as shown below:
Analysis
You can analyze deleted or changed sales orders along several dimensions:
By customer By sales organization By sales person By time period vs. previous period, quarter vs. previous quarter, or year vs. previous year
64
Typical queries posed with the Sales Order History table include:
How many sales orders or line items have been deleted per customer? Which sales person has the most sales orders or line items deleted? What would our revenue have been if all deleted sales orders and line items had been delivered and the quantities of other orders and line items had not been reduced? Which time periods show the most deleted sales orders? Which companies or plants are most affected by order changes and deletions?
65
Subject Areas Document Flow Section
Document Flow Section

The Document Flow is a view (SALES_DOC_FLOW_VIEW) in the Rapid Mart database creates a union of information from Sales Orders, Deliveries, and Billings. This section allows you to see query related sales order, delivery and billing documents. You can see the entire order fulfillment lifecycle. This view has fact tables common attribute fields such as sales order number, customer id, material id, sales document category id. In addition, it contains fact table measurement fields, such as sales order requested quantity, net item value, delivery quantity, billing document quantity and net item value. Aggregating by common fields you can trace sales orders history. For example what quantities and amounts were delivered and billed for each sales order. All Document Flow processing takes place in the Rapid Mart. The Rapid Mart simply contains a database view that creates a union of the 3 fact tables (SALES_ORDER_FACT, DELIVERY_FACT, & BILLING_FACT) together. The join is on the Sales Order Number and Sales Order Line Item. These two fields are the primary key to the Sales Orders Fact, and are foreign keys in Delivery Fact and Billing Fact.
Rapid Mart Processing

Document Flow includes the following dimensional attributes and associated dimension tables: Attribute Name Company Code Controlling Area Currency Customer Distribution Channel Division Document Category Material Material Alternative Unit of Measure Material By Plant Plant Dimension Tables COMPANY_CODE CONTROLLING_AREA CURRENCY CUSTOMER DISTRIBUTION_CHANNEL DIVISION DOCUMENT_CATEGORY MATERIAL MATERIAL_ALT_UOM MATERIAL_BY_PLANT PLANT
66
Attribute Name Profit Center & Hierarchy
Dimension Tables PROFIT_CENTER, PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_BAD, PROFIT_CENTER_HIER_HZ, PROFIT_CENTER_HIER_V SALES_DISTRICT SALES_GROUP SALES_OFFICE SALES_ORGANIZATION, SALES_ORGANIZATION_HIER SALES_PERSON STORAGE_LOCATION
Sales District Sales Group Sales Office Sales Organization & Hierarchy Sales Person Storage Location
View Fields
The Document Flow View contains the following measures: Col. Name AMT_BILL_NET_VALUE_GBL AMT_BILL_NET_VALUE_TRX AMT_BILL_REVENUE_GBL Description Net value (Global Currency) Net value in document currency Calculated field: for sales documents of categories U or 5 or 6 it is 0, for sales documents of categories N or O it is set to a negative of the net item value, for the rest sales documents it is the net item value - Global Currency Calculated field: for sales documents of categories U or 5 or 6 it is 0, for sales documents of categories N or O it is set to a negative of the net item value, for the rest sales documents it is the net item value - Transaction Currency Net value in Global currency Net value in document currency
AMT_BILL_REVENUE_TRX
AMT_SALES_NET_VALUE_GBL AMT_SALES_NET_VALUE_TRX
67
Col. Name AMT_SALES_RECEIVED_GBL
Description Calculated field: for sales documents of categories A or B it is 0, for sales documents of categories H or K without rejection reasons it is set to a negative of the net item value, for the rest sales documents without rejection reasons it is the net item value - Global Currency Calculated field: for sales documents of categories A or B it is 0, for sales documents of categories H or K without rejection reasons it is set to a negative of the net item value, for the rest sales documents without rejection reasons it is the net item value - Transaction Currency Calculated field as QTY_INVOICED * SLS_TO_BASE_DIVISOR / SLS_TO_BASE_NUMERATOR LIPS-LFIMG - Actual Quantity Delivered (in Sales Units) Cumulative Order Quantity in Sales Units
AMT_SALES_RECEIVED_TRX
QTY_BILL_SLSUOM
QTY_DELIV_SLSUOM QTY_ORDER_SLSUOM
68
Rapid Mart Data

The Document Flow Union View links the Sales Orders, Deliveries, and Billings as shown below
Analysis
Document Flow allows you analyze along several dimensions:
By bill-to, ship-to, or sold-to customer By sales order create date By sales organization attributes By material and factory attributes By financial organization attributes. By sales organization attributes By Profit center and hierarchy How many deliveries were issued for this sales order? What is the average number of deliveries for a sales order?
Typical queries on document flow include:
69
Subject Areas On Time Delivery Section
Which sales orders are delivered, but not yet invoiced? What is the value of deliveries or billings vs. the booked value of the sales orders?
On Time Delivery Section

This section uses information derived from the Schedule Lines and Deliveries sections described earlier in this chapter. On Time Delivery allows you to track how well you are delivering to schedule by calculating the days a delivery is early or late. On Time Delivery focuses on a subset of Schedule Line and Delivery information. The idea is focus on the deliveries that are due in the near future or near past. The default range is 15 days past and 15 days future. The range is configured with global variable $G_ONTIME_DELIV_WINDOW. On Time Delivery also has a history table that keeps a copy of all previous runs. This allows you to see how delivery schedules have changed over time. Example: your current snapshot of On Time Delivery shows a sales order delivered on schedule. But when you examine the history table you find the sales order was rescheduled several times over a period of weeks and was originally planned to be delivered weeks earlier. By this measure the delivery is late. All On Time Delivery processing occurs in the Rapid Mart. Sales Orders, Schedule Lines, and Deliveries must be loaded before On Time Delivery processing can occur. Data from the Schedule Lines is merged with data from the deliveries. The delivery quantity is allocated to the schedule line. When there is more than one schedule line or more than one delivery (or both) for an item, we distribute the total delivered quantity for the item across the schedule lines. The earliest schedule line is assigned the quantity from the earliest delivery. Example: A sales order item has three schedule lines, each with an order quantity of 50 pieces. You make two deliveries: the first for 20 pieces, the second for 60 pieces. The delivered quantity allocated to the first schedule line is 50 pieces (20 from the first delivery and 30 from the second delivery). This leaves 30 pieces remaining on the second delivery, which is allocated to the second schedule line. The allocation quantity for the third schedule line is zero.
70
If you delete the first delivery (20 pieces), the delivered quantity for this schedule line is still 50 pieces, but now this allocated from the second delivery. There are still 10 pieces available on the second delivery to further allocate. The system allocates the remaining 10 pieces to the next schedule line. The third schedule, still has zero allocated. The tables below illustrate this example:
With Both Deliveries:

Sched Line Number 1 2 3 Second Delivery 1 2 3 2 2 2 50 50 50 60 60 60 30 30 0 Delivery Sched Delivery Allocated Number Line Qty Qty Delivery Qty 1 1 1 50 50 50 20 20 20 20 0 0
First Delivery
With First Delivery Deleted:

Sched Line Number 1 2 3 Delivery Sched Delivery Allocated Number Line Qty Qty Delivery Qty 2 2 2 50 50 50 60 60 60 50 10 0
Second Delivery Only
The Rapid Mart also calculates if a delivery is on time, late, or early. The formula uses the Planned Goods Issue Date from the Schedule Line and the Actual Goods Issue Date from the Delivery. These correspond to the SAP solutions fields VBEP.WADAT and LIKP.WADAT_IST, respectively. If the Planned Goods Issue Date is in the past and there is no Delivery, we use the current system date instead to the Actual Goods Issue Date. The formula is: Days Early or Late =
71
Planned Goods Issue Date - Actual Goods Issue Date A late delivery will be a negative number, and an early delivery will be a positive number. Zero indicates an on time delivery. Each schedule line is also assigned a delivery status based on these two dates.
EARLY - The Actual Goods Issue Date is before the Planned Goods Issue Date ON TIME - Actual Goods Issue Date and Planned Goods Issue Date are the same LATE - Actual Goods Issue Date is after the Planned Goods Issue Date DND - (Did Not Deliver) Planned Goods Issue Date is in the Past and there is no Delivery. This is a missed delivery. N/A - (Not Applicable) Planned Goods Issue Date is in the future and there is no Delivery. No delivery is due yet
The Rapid Mart also relies on a global variable that sets the date range window. The default setting is 15 days. This tells the system to look only at schedule lines that have a Planned Goods Issue Date 15 days in the past or future from today. This allows you to focus on the immediate deliveries due or past due. This date range is expandable, but keep in mind that the loading job will run longer as the window expands. The final feature in On Time Delivery is the ability to focus on changes between runs. The Rapid Mart initially loads data to a staging table and compares this stage table to the results of the last run. A change status is assigned by doing this comparison:
NEW - The schedule line / delivery combination was not included in the previous run, but is in the current run. This may be because the record is new in the SAP solutions system or because, until now, the Planned Goods Issue Date was outside the date range set by the global variable. On the very first run of On Time Delivery all records will be assigned status NEW. CHANGE - The schedule line / delivery information has changed since the previous run. A change in any of the fields in the On Time Delivery fact table when compared to the previous run will generate this change status. NO CHANGE - The schedule line / delivery information has not changed since the previous run. DELETED - The schedule line / delivery combination was in the previous run, but not the current run. This may be because of physical deletion of records in SAP solutions, or because the Planned Goods Issue Date has changed and is now outside the date range set by the global variable.
72

On Time Delivery has two fact tables.
ONTIME_DELIVERY_FACT - A picture of the current delivery status within the On Time Delivery window. ONTIME_DELIVERY_HISTORY - Historical snapshots of previous runs of On Time Delivery. The contents of ONTIME_DELIVERY_FACT are appended to ONTIME_DELIVERY_HISTORY before each refresh of the data.
On Time Delivery & On Time Delivery History include the following dimensional attributes and associated dimension tables: Attribute Name Monetary Currency Customer Delivery Block Distribution Channel Division Inter Company Terms Material & Product Hierarchy Material Alternative Unit of Measure Material By Plant Plant Sales Office Sales Organization Sales Person Time Dimension Dimension Tables CURRENCY CUSTOMER DELIVERY_BLOCK DISTRIBUTION_CHANNEL DIVISION INTER_COMPANY_TERM01 MATERIAL, PRODUCT_HIERARCHY MATERIAL_ALT_UOM MATERIAL_BY_PLANT PLANT SALES_OFFICE SALES_ORGANIZATION SALES_PERSON TIME_DIM
On Time Delivery and On Time Delivery History contain the following Measures Column Name AMT_NET_PRICE_GBL AMT_NET_PRICE_TRX Description VBAP-NETPR - Net Price VBAP-NETPR - Net Price
73
Column Name DAYS_EARLY_LATE
Description Calculated - difference between Sched. Goods Issue Date and Actual Goods Issue Date. A positive number indicates an early delivery. A negative number indicates a late delivery. Calculated - Sched Line Quantity allocated to the Delivery LIPS-LFIMG - Actual Quantity Delivered (in Sales Units) VBAP- KWMENG - Cumulative Order Quantity in Sales Units Schedule line confirmed quantity
QTY_ALLOCTN_SLSUOM QTY_DELIV_SLSUOM QTY_ORDER_SLSUOM QTY_SCHED_CONFIRM_SLSUOM
74
Rapid Mart data

The On Time Delivery section is composed of two fact tables ONTIME_DELIVERY_FACT and ONTIME_DELIVERY_HISTORY. There is also a staging table called ONTIME_DELIVERY_STAGE. The fact tables share the same set of dimensions. They are organized as a star schema as shown below:
Analysis
With the tables in this section, you can analyze billing documents along several dimensions
By Material By Plant By Division, Distribution Channel, or Sales Organization By Sales Person By Inter-Company Terms
75
Subject Areas Document Validation Section
How is my On Time delivery performance? Are we meeting delivery schedules? Which customers are getting the most late deliveries? Which plants are producing the most late deliveries? Which plants are delivering early? (may indicate unused capacity). What sales orders must I prepare to ship in the next week? Month? Which sales orders need to be expedited because they did not ship as scheduled?
Document Validation Section

The Data Services load job validates that sales orders and billings meet certain validation criteria. The Rapid Mart validates both sales orders and billings for accurate exchange rates and conversion of monetary values to global currency. Invalid records are not loaded into the Sales Orders Fact or Billing Fact tables. Instead, they are loaded to two special tables that can be queried in the SAP BusinessObjects Universe. You must make corrections to the sales order or billings in SAP solutions and then re-load the Rapid Mart with the corrected records. All validation occurs in the Rapid Mart. The Rapid Mart uses the Data Services validation transform to check that documents in the BILLING_STAGE and SALES_ORDER_STAGE tables have correct global currency and exchange rates. Documents passing this check are loaded to the BILLING_FACT and SALES_ORDER_FACT tables. Documents failing this check are loaded to the BILLING_FACT_BAD and SALES_ORDER_FACT_BAD instead.

The Rapid Mart data consists of two tables
SALES_ORDER_FACT_BAD BILLING_FACT_BAD
They have these associated dimensions Attribute Customer Material Plant Table Names CUSTOMER MATERIAL PLANT
76
Attribute Sales Organization Division Distribution Channel Material By Plant
Table Names SALES_ORGANIZATION DIVISION DISTRIBUTION_CHANNEL MATERIAL_BY_PLANT
Fact Table Fields

SALES_ORDER_FACT_BAD and BILLNG_FACT_BAD tables are almost identical to the SALES_ORDER_FACT and BILLING_FACT tables. The differences are:
They each include two additional fields:
ETL_ERROR_ACTN - An error message describing the why the validation failed ETL_ERROR_COLUMN - Lists the column names that caused validation to fail
The primary keys also includes the LOAD_DATE (includes load date and timestamp). This allows multiple versions of the invalid documents can be loaded and gives you an audit trail of how often the same document has failed validation.
Rapid Mart Data

The Validation tables for Sales Orders and Billings can be organized as star schemas with the same dimensions as the Sales Order Fact and Billing Fact tables: Rapid Mart Data on page 36 for Sales Orders Rapid Mart data on page 59 for Billings.
Analysis
You can analyze the invalid documents by several dimensions.
By Material and Product Hierarchy By Plant By Sales Organization, Division, Distribution Channel By Document (or Transaction) Currency By Global Currency
77
Which sales orders and billings failed validation? What errors caused the validation to fail? Which fields caused the validation to fail?
78
Reports
chapter
Reports Overview
Overview
You can use the SAP BusinessObjects Sales Rapid Mart, version for SAP solutions to produce many kinds of reports. This chapter provides examples of reports you could generate using the Sales Rapid Mart universe. The information in this chapter is useful for those who design reporting solutions for Sales Analysis. This chapter provides reports and the recommended joins for each section in the Rapid Mart:
Sales Orders Deliveries and On-Time Delivery Billing Backlog Schedule Lines Sales Order History Document Flow Invalid Documents SAP Master Data Reports
Note that all report SQL is located in the Rapid Mart installation directory under "\Sample\DML".
Sales Orders
The sales order section captures sales orders, returns, credit and debit memo requests, and pre-sales documents, such as quotes, inquiries, contracts, and scheduling agreements.
Reports
Using the sales order information, you can complete numerous analyses and generate different reports. For example, reports you can generate include:
Sales Order Discount Analysis Number of Deals Trend Analysis Bookings vs Returns Returns Trend Analysis Top 10 Bookings Booking Trends
80
Reports Sales Orders
Top Sales Reps by Quarter
Sales Order Discount Analysis

This report analyzes sales order discounts by Product Hierarchy, Company Code, and Sales Rep.
By Company Code
View overall trend summaries by Company Code based on net value and also on Discount %. The report also includes a section for each Company Code with detailed discount information.
81
By Product Hierarchy
View the Top 10 discounts by Product Hierarchy Level 1. This report uses the Web Intelligence ranking feature to limit displayed results to Top 10 by Discount %. .
By Sales Rep
View Peer Performance and detailed discount information for each Sales Rep.
82
Report SQL
All report SQL is located in the Rapid Mart installation directory under "\Sample\DML".
Number of Deals Trend Analysis

This report analyzes Number of Deals trends; providing a high-level summary analysis and detailed analysis by Sales Rep and Company Code
Summary
View dashboard-style summary for Number of Deals for the entire enterprise.
Report SQL
SELECT COMPANY_CODE.CMPNY_CODE_NAME, SALES_ORGANIZATION.SALES_ORG_DESCR, DIVISION.DIVISION_DESCR, sum(SALES_ORDER_FACT.AMT_SUBTTL_01_GBL), SALES_PERSON.SALES_PERSON_FIRST_NAME, SALES_PERSON.SALES_PERSON_LAST_NAME, sum(SALES_ORDER_FACT.AMT_SUBTTL_01_GBL SALES_ORDER_FACT.AMT_NET_VALUE_GBL), TIMEDIM_CREATE_DATE.CALENDAR_YEAR, sum(SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL), MATERIAL.MTRL_TYPE_DESCR, CUSTOMER_SOLDTO.CUSTOMER_NAME_01,
83
CUSTOMER_SOLDTO.CUSTOMER_NAME_02, TIMEDIM_CREATE_DATE.CALENDAR_QUARTER, PRODUCT_HIERARCHY.LVL_01_DESCR, CURRENCY_GLOBAL.CURR_ISO_CODE, avg(SALES_ORDER_FACT.QTY_ORDER_SLSUOM), sum(SALES_ORDER_FACT.QTY_ORDER_SLSUOM), sum(SALES_ORDER_FACT.AMT_NET_VALUE_GBL SALES_ORDER_FACT.AMT_STD_COST_GBL), case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL < 200 then 'Small Order (less than 200.00)' else case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL >= 200 and SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL < 500 then 'Medium Order(200.00 to 499.99)' else case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL >= -30 and SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL < 0 then '1 - 30 Days Late' else case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL >= 500 then 'Large Order (500.00 or more)' else 'N/A' end end end end , COUNT( DISTINCT SALES_ORDER_FACT.SALES_DOC_ID) FROM COMPANY_CODE, SALES_ORGANIZATION, DIVISION, SALES_ORDER_FACT, SALES_PERSON, TIME_DIM TIMEDIM_CREATE_DATE, MATERIAL, CUSTOMER CUSTOMER_SOLDTO, PRODUCT_HIERARCHY, CURRENCY CURRENCY_GLOBAL WHERE ( SALES_ORDER_FACT.CREATE_DATE=TIMEDIM_CREATE_DATE.CALEND AR_DATE ) AND ( SALES_ORGANIZATION.SALES_ORG_ID=SALES_ORDER_FACT.SALES_O RG_ID ) AND ( SALES_PERSON.SALES_PERSON_ID=SALES_ORDER_FACT.SALES_PERSO N_ID ) AND ( DIVISION.DIVISION_ID=SALES_ORDER_FACT.DIVISION_ID ) AND ( CUSTOMER_SOLDTO.CUSTOMER_ID=SALES_ORDER_FACT.CUSTOMER_I D_SOLDTO ) AND ( SALES_ORDER_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID ) AND ( COMPANY_CODE.CMPNY_CODE_ID=SALES_ORDER_FACT.CMPNY_COD E_ID ) AND ( MATERIAL.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID ) AND ( CURRENCY_GLOBAL.CURR_ID=SALES_ORDER_FACT.CURR_ID_GBL ) AND ( SALES_ORDER_FACT.SALES_DOC_ID<> '?' ) AND (
84
( (SALES_ORDER_FACT.DOC_CATEG_ID= 'C' or SALES_ORDER_FACT.DOC_CATEG_ID= 'I') ) AND TIMEDIM_CREATE_DATE.CALENDAR_YEAR In @prompt('Calendar Year:','N','Doc. Creation Date Time Dim\Calendar Year',Multi,Free,Persistent,,User:0) ) GROUP BY COMPANY_CODE.CMPNY_CODE_NAME, SALES_ORGANIZATION.SALES_ORG_DESCR, DIVISION.DIVISION_DESCR, SALES_PERSON.SALES_PERSON_FIRST_NAME, SALES_PERSON.SALES_PERSON_LAST_NAME, TIMEDIM_CREATE_DATE.CALENDAR_YEAR, MATERIAL.MTRL_TYPE_DESCR, CUSTOMER_SOLDTO.CUSTOMER_NAME_01, CUSTOMER_SOLDTO.CUSTOMER_NAME_02, TIMEDIM_CREATE_DATE.CALENDAR_QUARTER, PRODUCT_HIERARCHY.LVL_01_DESCR, CURRENCY_GLOBAL.CURR_ISO_CODE, case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL < 200 then 'Small Order (less than 200.00)' else case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL >= 200 and SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL < 500 then 'Medium Order(200.00 to 499.99)' else case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL >= -30 and SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL < 0 then '1 - 30 Days Late' else case when SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL >= 500 then 'Large Order (500.00 or more)' else 'N/A' end end end end HAVING sum(SALES_ORDER_FACT.AMT_SUBTTL_01_GBL SALES_ORDER_FACT.AMT_NET_VALUE_GBL) <> 0
Bookings vs Returns
This report analyzes company Bookings vs Returns trends by Company Code and Plant for selected Calendar Years. This report uses two synchronized queries, one to retrieve Bookings data and the other for Returns data. Common dimensions are merged and the Net Value amount from each query is used in the report.
85
Report SQL
86
Returns Trend Analysis

View Returns Trend Analysis for a selected set of Calendar Years by:
Company Code Sales Org Plant
Report SQL
87
Top 10 Bookings
View summary of top bookings for the enterprise over the selected Calendar Year, including Top 10:
Customers Sales Reps Products
This report uses the Web Intelligence ranking feature to limit displayed results to Top 10.
Report SQL
SELECT TIMEDIM_CREATE_DATE.CALENDAR_QUARTER, TIMEDIM_CREATE_DATE.CALENDAR_YEAR, CUSTOMER_SOLDTO.CUSTOMER_NAME_01, CUSTOMER_SOLDTO.CUSTOMER_NAME_02, SALES_PERSON.SALES_PERSON_FIRST_NAME, SALES_PERSON.SALES_PERSON_LAST_NAME,
88
sum(SALES_ORDER_FACT.AMT_NET_VALUE_HDR_GBL), PRODUCT_HIERARCHY.LVL_01_DESCR FROM SALES_ORDER_FACT, TIME_DIM TIMEDIM_CREATE_DATE, SALES_PERSON, CUSTOMER CUSTOMER_SOLDTO, PRODUCT_HIERARCHY WHERE ( SALES_ORDER_FACT.CREATE_DATE=TIMEDIM_CREATE_DATE.CALEND AR_DATE ) AND ( SALES_PERSON.SALES_PERSON_ID=SALES_ORDER_FACT.SALES_PERSO N_ID ) AND ( CUSTOMER_SOLDTO.CUSTOMER_ID=SALES_ORDER_FACT.CUSTOMER_I D_SOLDTO ) AND ( SALES_ORDER_FACT.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIE R_ID ) AND ( SALES_ORDER_FACT.SALES_DOC_ID<> '?' ) AND ( TIMEDIM_CREATE_DATE.CALENDAR_YEAR = @prompt('Calendar Year:','N','Doc. Creation Date Time Dim\Calendar Year',Mono,Free,Persistent,,User:0) AND ( (SALES_ORDER_FACT.DOC_CATEG_ID= 'C' or SALES_ORDER_FACT.DOC_CATEG_ID= 'I') ) ) GROUP BY TIMEDIM_CREATE_DATE.CALENDAR_QUARTER, TIMEDIM_CREATE_DATE.CALENDAR_YEAR, CUSTOMER_SOLDTO.CUSTOMER_NAME_01, CUSTOMER_SOLDTO.CUSTOMER_NAME_02, SALES_PERSON.SALES_PERSON_FIRST_NAME, SALES_PERSON.SALES_PERSON_LAST_NAME, PRODUCT_HIERARCHY.LVL_01_DESCR
89
Booking Trends
This report analyzes Booking Trends for the entire enterprise over the selected set of Calendar Years by:
Company Code Sales Org Product Hierarchy
Report SQL
90
Top Sales Reps by Quarter

View Top Sales Reps for the selected Calendar Years. Bookings amounts are displayed for each quarter. Sales Reps are sorted according to highest Bookings amount
Report SQL
91
Recommended table joins

When analyzing data from the sales order section, you need to create joins between different tables. Specifically, you need to create joins between the SALES_ORDERS_FACT table and other dimension tables in the Rapid Mart Note: BACKLOG_FACT and SALES_ORDER_FACT are joined because they share the same primary key. This allows Backlog and Sales Orders to share the same set of dimensions in the universe. Dimension Table Join Expression
BACKLOG_FACT (Fact to Fact - BACKLOG_FACT.SALES_DOC_ID=SALES allows Backlog Orders to be used as _ORDER_FACT.SALES_DOC_ID AND a dimension to Sales Orders) BACKLOG_FACT.SALES_LINE_ITEM_ID=S ALES_ORDER_FACT.SALES_LINE_ITEM_I D BILLING_BLOCK CENTRAL_ADDRESS BILLING_BLOCK.BILL_BLOCK_ID=SALES _ORDER_FACT.BILL_BLOCK_ID CENTRAL_ADDRESS.ADDRESS_ID= SALES_ORDER_FACT.ADDRESS_ID_SHI PTO COMPANY_CODE.CMPNY_CODE_ID=SAL ES_ORDER_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=S ALES_ORDER_FACT.CTRL_AREA_ID SALES_ORDER_FACT.CR_CTRL_AREA_I D= CREDIT_CONTROL_AREA.CR_CTRL_AR EA_ID
COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_AREA
CREDIT_MGMT_RISK_CLAS SALES_ORDER_FACT.CR_CTRL_AREA_I S D= CREDIT_MGMT_RISK_CLASS.CR_CTRL_ AREA_ID and SALES_ORDER_FACT.CR_MGMT_RISK_C LASS_ID = CREDIT_MGMT_RISK_CLASS.CR_MGMT _RISK_CLASS_ID CURRENCY CURRENCY CURRENCY CURRENCY.CURR_ID=SALES_ORDER_F ACT.CURR_ID_GBL CURRENCY.CURR_ID=SALES_ORDER_F ACT.CURR_ID_STATS CURRENCY.CURR_ID=SALES_ORDER_F ACT.CURR_ID_TRX
92
Dimension Table CUSTOMER CUSTOMER CUSTOMER CUSTOMER_GROUP
Join Expression CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT.CUSTOMER_ID_BILLTO CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT.CUSTOMER_ID_SHIPTO CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT.CUSTOMER_ID_SOLDTO SALES_ORDER_FACT.CUSTOMER_GRP_ 01_ID=CUSTOMER_GROUP.CUSTOMER_ GRP_ID DELIVERY_BLOCK.DELIV_BLOCK_ID=SA LES_ORDER_FACT.DELIV_BLOCK_ID SALES_ORDER_FACT.DELIV_ROUTE_ID= DELIVERY_ROUTE.DELIV_ROUTE_ID DISTRIBUTION_CHANNEL.DISTRIBTN_C HANNEL_ID=SALES_ORDER_FACT.DISTR IBTN_CHANNEL_ID DIVISION.DIVISION_ID=SALES_ORDER_F ACT.DIVISION_ID SALES_ORDER_FACT.DOC_CATEG_ID=D OCUMENT_CATEGORY.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'SALES' SALES_ORDER_FACT.DOC_CATEG_ID=D OCUMENT_TYPE.DOC_CATEG_ID and SALES_ORDER_FACT.DOC_TYPE_ID=DO CUMENT_TYPE.DOC_TYPE_ID and DOCUMENT_TYPE.DIM_SRC_ID = 'SALES' SALES_ORDER_FACT.INTER_CMPNY_TE RM01_ID=INTER_COMPANY_TERM01.INT ER_CMPNY_TERM01_ID SALES_ORDER_FACT.MATERIAL_ID=MAT ERIAL.MATERIAL_ID SALES_ORDER_FACT.MATERIAL_ID=MAT ERIAL_ALT_UOM.MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE)
DELIVERY_BLOCK DELIVERY_ROUTE DISTRIBUTION_CHANNEL
DIVISION DOCUMENT_CATEGORY
DOCUMENT_TYPE
INTER_COMPANY_TERM01
MATERIAL MATERIAL_ALT_UOM
93
Dimension Table MATERIAL_BY_PLANT
Join Expression MATERIAL_BY_PLANT.PLANT_ID=SALES _ORDER_FACT.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=SAL ES_ORDER_FACT.MATERIAL_ID SALES_ORDER_FACT.MTRL_GRP_ID=MA TERIAL_GROUP.MTRL_GRP_ID SALES_ORDER_FACT.ORDER_REASON_I D=ORDER_REASON.ORDER_REASON_I D SALES_ORDER_FACT.PAYMNT_TERM_ID =PAYMENT_TERM.PAYMNT_TERM_ID AND PAYMENT_TERM.PAYMNT_TERM_DAY_LI MIT = '?' PLANT.PLANT_ID=SALES_ORDER_FACT. PLANT_ID SALES_ORDER_FACT.PRICE_PROCEDU RE_ID=PRICING_PROCEDURE_HZ.PRICE _PROCEDURE_ID and PRICING_PROCEDURE_HZ.APPLICTN_ID = 'V' and PRICING_PROCEDURE_HZ.USAGE_ID = 'A' SALES_ORDER_FACT.PROD_HIER_ID=P RODUCT_HIERARCHY.PROD_HIER_ID SALES_ORDER_FACT.PROFIT_CNTR_ID = PROFIT_CENTER.PROFIT_CNTR_ID AND SALES_ORDER_FACT.CTRL_AREA_ID = PROFIT_CENTER.CTRL_AREA_ID SALES_ORDER_FACT.PROFIT_CNTR_ID = PROFIT_CENTER_HIER_HZ.PROFIT_CNT R_ID AND SALES_ORDER_FACT.CTRL_AREA_ID = PROFIT_CENTER_HIER_HZ.CTRL_AREA_ ID
MATERIAL_GROUP ORDER_REASON
PAYMENT_TERM
PLANT PRICING_PROCEDURE_HZ
PRODUCT_HIERARCHY PROFIT_CENTER
PROFIT_CENTER_HIER_HZ
94
Dimension Table PROFIT_CENTER_HIER_VR
Join Expression SALES_ORDER_FACT.PROFIT_CNTR_ID = PROFIT_CENTER_HIER_VR.CHILD_ID AND SALES_ORDER_FACT.CTRL_AREA_ID = PROFIT_CENTER_HIER_VR.CTRL_AREA _ID SALES_ORDER_FACT.REJECT_REASON_ ID=REJECT_REASON.REJECT_REASON_ ID SALES_DISTRICT.SALES_DISTRICT_ID=S ALES_ORDER_FACT.SALES_DISTRICT_I D SALES_GROUP.SALES_GRP_ID=SALES_ ORDER_FACT.SALES_GRP_ID SALES_OFFICE.SALES_OFFICE_ID=SALE S_ORDER_FACT.SALES_OFFICE_ID SALES_ORDER_FACT.SALES_DOC_ID<> '?' SALES_ORDER_FACT.SALES_DOC_STAT US_KEY=SALES_ORDER_STATUS.SALES _DOC_STATUS_KEY SALES_ORGANIZATION.SALES_ORG_ID= SALES_ORDER_FACT.SALES_ORG_ID
REJECT_REASON
SALES_DISTRICT
SALES_GROUP SALES_OFFICE SALES_ORDER_FACT SALES_ORDER_STATUS
SALES_ORGANIZATION
95
Dimension Table
Join Expression
SALES_ORGANIZATION_HIE SALES_ORDER_FACT.SALES_ORG_ID=S R ALES_ORGANIZATION_HIER.SALES_OR G_ID and SALES_ORDER_FACT.SALES_GRP_ID=S ALES_ORGANIZATION_HIER.SALES_GRP _ID and SALES_ORDER_FACT.SALES_OFFICE_ID =SALES_ORGANIZATION_HIER.SALES_O FFICE_ID and SALES_ORDER_FACT.DISTRIBTN_CHAN NEL_ID=SALES_ORGANIZATION_HIER.DI STRIBTN_CHANNEL_ID and SALES_ORDER_FACT.DIVISION_ID_HDR =SALES_ORGANIZATION_HIER.DIVISION _ID and @Prompt('Enter Sales Org Hierarchy Date','D',,MONO,FREE) between SALES_ORGANIZATION_HIER.VALID_FR OM_DATE and SALES_ORGANIZATION_HIER.VALID_TO_ DATE SALES_PERSON SHIPPING_POINT STORAGE_LOCATION SALES_PERSON.SALES_PERSON_ID=SA LES_ORDER_FACT.SALES_PERSON_ID SALES_ORDER_FACT.SHIP_POINT_ID=S HIPPING_POINT.SHIP_POINT_ID STORAGE_LOCATION.STORAGE_LOCAT N_ID=SALES_ORDER_FACT.STORAGE_L OCATN_ID and STORAGE_LOCATION.PLANT_ID=SALES_ ORDER_FACT.PLANT_ID SALES_ORDER_FACT.CREATE_DATE=TI ME_DIM.CALENDAR_DATE SALES_ORDER_FACT.DOC_DATE=TIME_ DIM.CALENDAR_DATE SALES_ORDER_FACT.RQST_DELIV_DAT E_HDR=TIME_DIM.CALENDAR_DATE UNIT_OF_MEASURE.UOM_ID=SALES_OR DER_FACT.UOM_ID_BASE UNIT_OF_MEASURE.UOM_ID=SALES_OR DER_FACT.UOM_ID_SALES UNIT_OF_MEASURE.UOM_ID=SALES_OR DER_FACT.UOM_ID_TRGT
TIME_DIM TIME_DIM TIME_DIM UNIT_OF_MEASURE UNIT_OF_MEASURE UNIT_OF_MEASURE
96
Reports Deliveries and On-Time Delivery
Deliveries and On-Time Delivery

The delivery and on-time delivery section contains information about all deliveries; including returns, shipments, shipment notifications, and information for tracking delivery status.
Reports
Using the delivery information, you can complete numerous analyses and generate different reports, including:
On-time Delivery Trends On-time Delivery Details On-Time Delivery Summary On-Time Delivery Top 10 Customers On-Time Delivery Top 10 Documents
On-time Delivery Trends

This report analyzes On-Time delivery trends for selected Calendar Years by:
Plant Division
97
Report SQL
SELECT PLANT.PLANT_ID, PLANT.PLANT_NAME_01, DIVISION.DIVISION_ID, DIVISION.DIVISION_DESCR, MATERIAL.MTRL_DESCR, TIMEDIM_GOODS_ISSUE_DATE.CALENDAR_YEAR, TIMEDIM_GOODS_ISSUE_DATE.CALENDAR_QUARTER, AVG(ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE), AVG(case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else 0.0 end end end end end end end ), SUM(case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then
98
(ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else 0.0 end end end end end end end ), case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then 'More than 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then '31 - 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then '1 - 30 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then 'On Time' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then '1 - 30 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then '31 - 60 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then 'More than 60 Days Early' else 'N/A' end end end end end end end FROM PLANT, DIVISION, MATERIAL, TIME_DIM TIMEDIM_GOODS_ISSUE_DATE, ONTIME_DELIVERY_FACT WHERE ( ONTIME_DELIVERY_FACT.SCHED_GI_DATE=TIMEDIM_GOODS_ISSUE_D ATE.CALENDAR_DATE ) AND ( ONTIME_DELIVERY_FACT.DIVISION_ID=DIVISION.DIVISION_ID ) AND ( PLANT.PLANT_ID=ONTIME_DELIVERY_FACT.PLANT_ID ) AND ( MATERIAL.MATERIAL_ID=ONTIME_DELIVERY_FACT.MATERIAL_ID ) AND TIMEDIM_GOODS_ISSUE_DATE.CALENDAR_YEAR In @prompt('Calendar Year(s):','N','Planned Goods Issue Date Time Dim\Calendar Year',Multi,Free,Persistent,,User:0) GROUP BY PLANT.PLANT_ID, PLANT.PLANT_NAME_01, DIVISION.DIVISION_ID, DIVISION.DIVISION_DESCR, MATERIAL.MTRL_DESCR, TIMEDIM_GOODS_ISSUE_DATE.CALENDAR_YEAR, TIMEDIM_GOODS_ISSUE_DATE.CALENDAR_QUARTER, case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then 'More than 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then '31 - 60 Days Late' else
99
case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then '1 - 30 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then 'On Time' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then '1 - 30 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then '31 - 60 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then 'More than 60 Days Early' else 'N/A' end end end end end end end
100
On-time Delivery Details

Operational report showing current deliveries. For a selected Plant, Division, and Scheduled delivery date between the selected date range, view details by (Rapid Mart calculated) delivery status:
Overdue Late Early On time
Report SQL
101
On-Time Delivery Summary

View a summary of On-Time Delivery metrics for the selected Calendar Year and Quarter by:
Division Company Code
This report offers drill down capability to see Top 10 Customers for a Plant (by opening On-Time Delivery Top 10 Customers).
Report SQL
102
On-Time Delivery Top 10 Customers

View Top 10 Customers based on Net Value for a selected Plant, Calendar Year, and Delivery Status. This report uses the Web Intelligence ranking feature to limit to the Top 10 Customers by Total Delivered Net Value. This report offers drill down capability to see Top 10 Documents for a Customer (by opening On-Time Delivery Top 10 Documents).
Report SQL
103
On-Time Delivery Top 10 Documents

View Top 10 Sales Documents for a selected Customer, Calendar Year, and Delivery Status. This report uses the Web Intelligence ranking feature to limit to the Top 10 Customers by Total Delivered Net Value.
Report SQL
SELECT PLANT.PLANT_ID, PLANT.PLANT_NAME_01, DIVISION.DIVISION_ID, DIVISION.DIVISION_DESCR, MATERIAL.MTRL_DESCR, ONTIME_DELIVERY_FACT.NAME_01_SHIPTO, ONTIME_DELIVERY_FACT.NAME_02_SHIPTO, ONTIME_DELIVERY_FACT.COUNTRY_ID_SHIPTO, ONTIME_DELIVERY_FACT.REGION_ID_SHIPTO, ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE, ONTIME_DELIVERY_FACT.SCHED_GI_DATE, ONTIME_DELIVERY_FACT.ACTL_GI_DATE, ONTIME_DELIVERY_FACT.DELIV_STATUS_FLAG, ONTIME_DELIVERY_FACT.QTY_SCHED_CONFIRM_SLSUOM, ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM, ONTIME_DELIVERY_FACT.SALES_DOC_ID, ONTIME_DELIVERY_FACT.SALES_LINE_ITEM_ID, ONTIME_DELIVERY_FACT.SCHED_LINE_ITEM_ID, ONTIME_DELIVERY_FACT.DELIV_ID, ONTIME_DELIVERY_FACT.DELIV_LINE_ITEM_ID, ONTIME_DELIVERY_FACT.CHANGE_STATUS_FLAG,
104
AVG(ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE), SUM(case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM * ONTIME_DELIVERY_FACT.AMT_NET_PRICE_TRX) else 0.0 end end end end end end end ), case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then 'More than 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then '31 - 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then '1 - 30 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then 'On Time' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then '1 - 30 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then '31 - 60 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then 'More than 60 Days Early' else 'N/A' end end end end end end end, SUM(case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then
105
(ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then (ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM) else 0.0 end end end end end end end ) FROM PLANT, DIVISION, MATERIAL, ONTIME_DELIVERY_FACT WHERE ( ONTIME_DELIVERY_FACT.DIVISION_ID=DIVISION.DIVISION_ID ) AND ( PLANT.PLANT_ID=ONTIME_DELIVERY_FACT.PLANT_ID ) AND ( MATERIAL.MATERIAL_ID=ONTIME_DELIVERY_FACT.MATERIAL_ID ) AND ( PLANT.PLANT_NAME_01 = @prompt('Plant:','A','Plant\Plant Name 1',Mono,Free,Persistent,,User:0) AND ONTIME_DELIVERY_FACT.DELIV_STATUS_FLAG = @prompt('Delivery Status:','A','Curr On Time - Additional Details (IDs)\Delivery Status',Mono,Free,Persistent,,User:1) AND ONTIME_DELIVERY_FACT.NAME_01_SHIPTO = @prompt('Customer Name:','A','Curr On Time - Ship To Address\Name1',Mono,Free,Persistent,,User:2) ) GROUP BY PLANT.PLANT_ID, PLANT.PLANT_NAME_01, DIVISION.DIVISION_ID, DIVISION.DIVISION_DESCR, MATERIAL.MTRL_DESCR, ONTIME_DELIVERY_FACT.NAME_01_SHIPTO, ONTIME_DELIVERY_FACT.NAME_02_SHIPTO, ONTIME_DELIVERY_FACT.COUNTRY_ID_SHIPTO, ONTIME_DELIVERY_FACT.REGION_ID_SHIPTO, ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE, ONTIME_DELIVERY_FACT.SCHED_GI_DATE, ONTIME_DELIVERY_FACT.ACTL_GI_DATE, ONTIME_DELIVERY_FACT.DELIV_STATUS_FLAG, ONTIME_DELIVERY_FACT.QTY_SCHED_CONFIRM_SLSUOM, ONTIME_DELIVERY_FACT.QTY_ALLOCTN_SLSUOM, ONTIME_DELIVERY_FACT.SALES_DOC_ID, ONTIME_DELIVERY_FACT.SALES_LINE_ITEM_ID, ONTIME_DELIVERY_FACT.SCHED_LINE_ITEM_ID, ONTIME_DELIVERY_FACT.DELIV_ID, ONTIME_DELIVERY_FACT.DELIV_LINE_ITEM_ID,
106
ONTIME_DELIVERY_FACT.CHANGE_STATUS_FLAG, case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -60 then 'More than 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -60 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < -30 then '31 - 60 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE >= -30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE < 0 then '1 - 30 Days Late' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE = 0 then 'On Time' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 0 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 30 then '1 - 30 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 30 and ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE <= 60 then '31 - 60 Days Early' else case when ONTIME_DELIVERY_FACT.DAYS_EARLY_LATE > 60 then 'More than 60 Days Early' else 'N/A' end end end end end end end

When analyzing data from the delivery section, you need to create joins between different tables. Specifically, you need to create joins between DELIVERY_FACT, ON_TIME_DELIVERY_FACT, and ON_TIME_DELIVERY_HISTORY tables and other dimension tables in the Rapid Mart.
107
Delivery Fact
Dimension Table BILLING_BLOCK COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_AREA Join Expression BILLING_BLOCK.BILL_BLOCK_ID=DELIVERY_FACT.BIL L_BLOCK_ID COMPANY_CODE.CMPNY_CODE_ID=DELIVERY_FACT .CMPNY_CODE_ID DELIVERY_FACT.CTRL_AREA_ID=CONTROLLING_AR EA.CTRL_AREA_ID DELIVERY_FACT.CR_CTRL_AREA_ID = CREDIT_CONTROL_AREA.CR_CTRL_AREA_ID
CREDIT_MGMT_RISK_CLAS DELIVERY_FACT.CR_CTRL_AREA_ID = S CREDIT_MGMT_RISK_CLASS.CR_CTRL_AREA_ID and DELIVERY_FACT.CR_MGMT_RISK_CLASS_ID = CREDIT_MGMT_RISK_CLASS.CR_MGMT_RISK_CLAS S_ID CURRENCY CURRENCY CUSTOMER CUSTOMER CUSTOMER_GROUP DELIVERY_BLOCK DELIVERY_FACT DELIVERY_PRIORITY DELIVERY_ROUTE DELIVERY_STATUS DISTRIBUTION_CHANNEL DIVISION CURRENCY.CURR_ID=DELIVERY_FACT.CURR_ID_STA TS CURRENCY.CURR_ID=DELIVERY_FACT.CURR_ID_TR X CUSTOMER.CUSTOMER_ID=DELIVERY_FACT.CUSTO MER_ID_SHIPTO CUSTOMER.CUSTOMER_ID=DELIVERY_FACT.CUSTO MER_ID_SOLDTO DELIVERY_FACT.CUSTOMER_GRP_ID=CUSTOMER_G ROUP.CUSTOMER_GRP_ID DELIVERY_BLOCK.DELIV_BLOCK_ID=DELIVERY_FAC T.DELIV_BLOCK_ID DELIVERY_FACT.DELIV_ID<> '?' DELIVERY_FACT.DELIV_PRIORITY_ID=DELIVERY_PRI ORITY.DELIV_PRIORITY_ID DELIVERY_ROUTE.DELIV_ROUTE_ID=DELIVERY_FAC T.DELIV_ROUTE_ID DELIVERY_FACT.DELIV_STATUS_KEY=DELIVERY_STA TUS.DELIV_STATUS_KEY DISTRIBUTION_CHANNEL.DISTRIBTN_CHANNEL_ID= DELIVERY_FACT.DISTRIBTN_CHANNEL_ID DIVISION.DIVISION_ID=DELIVERY_FACT.DIVISION_ID
108
Dimension Table DOCUMENT_CATEGORY
Join Expression DELIVERY_FACT.DOC_CATEG_ID=DOCUMENT_CATE GORY.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'SALES' DELIVERY_FACT.DOC_CATEG_ID=DOCUMENT_TYPE. DOC_CATEG_ID and DELIVERY_FACT.DOC_TYPE_ID=DOCUMENT_TYPE.D OC_TYPE_ID and DOCUMENT_TYPE.DIM_SRC_ID = 'SALES' INTER_COMPANY_TERM01.INTER_CMPNY_TERM01_I D=DELIVERY_FACT.INTER_CMPNY_TERM01_ID DELIVERY_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ ID DELIVERY_FACT.MATERIAL_ID=MATERIAL_ALT_UOM. MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE) MATERIAL_BY_PLANT.PLANT_ID=DELIVERY_FACT.PL ANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=DELIVERY_FACT .MATERIAL_ID MATERIAL_GROUP.MTRL_GRP_ID=DELIVERY_FACT.M TRL_GRP_ID PLANT.PLANT_ID=DELIVERY_FACT.PLANT_ID DELIVERY_FACT.PRICE_PROCEDURE_ID=PRICING_P ROCEDURE_HZ.PRICE_PROCEDURE_ID and PRICING_PROCEDURE_HZ.APPLICTN_ID = 'V' and PRICING_PROCEDURE_HZ.USAGE_ID = 'A' PRODUCT_HIERARCHY.PROD_HIER_ID=DELIVERY_F ACT.PROD_HIER_ID PROFIT_CENTER.PROFIT_CNTR_ID=DELIVERY_FACT. PROFIT_CNTR_ID AND PROFIT_CENTER.CTRL_AREA_ID = DELIVERY_FACT.CTRL_AREA_ID PROFIT_CENTER_HIER_HZ.PROFIT_CNTR_ID=DELIV ERY_FACT.PROFIT_CNTR_ID AND PROFIT_CENTER_HIER_HZ.CTRL_AREA_ID = DELIVERY_FACT.CTRL_AREA_ID PROFIT_CENTER_HIER_VR.CHILD_ID=DELIVERY_FA CT.PROFIT_CNTR_ID AND PROFIT_CENTER_HIER_VR.CTRL_AREA_ID = DELIVERY_FACT.CTRL_AREA_ID
DOCUMENT_TYPE
INTER_COMPANY_TERM01 MATERIAL MATERIAL_ALT_UOM
MATERIAL_BY_PLANT
MATERIAL_GROUP PLANT PRICING_PROCEDURE_HZ
PROFIT_CENTER_HIER_VR
109
Dimension Table SALES_GROUP SALES_OFFICE SALES_ORDER_FACT (Fact to Fact - allows Sales Orders to be used as a dimension to Deliveries) SALES_ORGANIZATION
Join Expression SALES_GROUP.SALES_GRP_ID=DELIVERY_FACT.SAL ES_GRP_ID DELIVERY_FACT.SALES_OFFICE_ID=SALES_OFFICE. SALES_OFFICE_ID SALES_ORDER_FACT.SALES_DOC_ID=DELIVERY_FA CT.SALES_DOC_ID and SALES_ORDER_FACT.SALES_LINE_ITEM_ID=DELIVE RY_FACT.SALES_LINE_ITEM_ID SALES_ORGANIZATION.SALES_ORG_ID=DELIVERY_F ACT.SALES_ORG_ID
SALES_ORGANIZATION_HIE DELIVERY_FACT.SALES_ORG_ID=SALES_ORGANIZAT R ION_HIER.SALES_ORG_ID and DELIVERY_FACT.SALES_GRP_ID=SALES_ORGANIZAT ION_HIER.SALES_GRP_ID and DELIVERY_FACT.SALES_OFFICE_ID=SALES_ORGANI ZATION_HIER.SALES_OFFICE_ID and DELIVERY_FACT.DISTRIBTN_CHANNEL_ID=SALES_O RGANIZATION_HIER.DISTRIBTN_CHANNEL_ID and DELIVERY_FACT.DIVISION_ID=SALES_ORGANIZATIO N_HIER.DIVISION_ID and @Prompt('Enter Sales Org Hierarchy Date','D',,MONO,FREE) between SALES_ORGANIZATION_HIER.VALID_FROM_DATE and SALES_ORGANIZATION_HIER.VALID_TO_DATE SHIPPING_POINT STORAGE_LOCATION SHIPPING_POINT.SHIP_POINT_ID=DELIVERY_FACT.S HIP_POINT_ID DELIVERY_FACT.PLANT_ID=STORAGE_LOCATION.PL ANT_ID and DELIVERY_FACT.STORAGE_LOCATN_ID=STORAGE_L OCATION.STORAGE_LOCATN_ID DELIVERY_FACT.ACTL_GI_DATE=TIME_DIM.CALENDA R_DATE DELIVERY_FACT.CREATE_DATE_HDR=TIME_DIM.CAL ENDAR_DATE DELIVERY_FACT.DELIV_DATE=TIME_DIM.CALENDAR_ DATE DELIVERY_FACT.PLAN_GI_DATE=TIME_DIM.CALENDA R_DATE UNIT_OF_MEASURE.UOM_ID=DELIVERY_FACT.UOM_I D_BASE
TIME_DIM TIME_DIM TIME_DIM TIME_DIM UNIT_OF_MEASURE
110
Dimension Table UNIT_OF_MEASURE UNIT_OF_MEASURE UNIT_OF_MEASURE
Join Expression UNIT_OF_MEASURE.UOM_ID=DELIVERY_FACT.UOM_I D_SALES UNIT_OF_MEASURE.UOM_ID=DELIVERY_FACT.UOM_I D_VOLUME UNIT_OF_MEASURE.UOM_ID=DELIVERY_FACT.UOM_I D_WEIGHT
111
Current On-Time Delivery

Dimension Table CURRENCY CURRENCY CUSTOMER DELIVERY_BLOCK DISTRIBUTION_CHANNEL DIVISION INTER_COMPANY_TERM01 Join Expression CURRENCY.CURR_ID=ONTIME_DELIVERY_FACT.CUR R_ID_GBL CURRENCY.CURR_ID=ONTIME_DELIVERY_FACT.CUR R_ID_TRX CUSTOMER.CUSTOMER_ID=ONTIME_DELIVERY_FAC T.CUSTOMER_ID_SHIPTO DELIVERY_BLOCK.DELIV_BLOCK_ID=ONTIME_DELIV ERY_FACT.DELIV_BLOCK_ID DISTRIBUTION_CHANNEL.DISTRIBTN_CHANNEL_ID= ONTIME_DELIVERY_FACT.DISTRIBTN_CHANNEL_ID ONTIME_DELIVERY_FACT.DIVISION_ID=DIVISION.DIVI SION_ID ONTIME_DELIVERY_FACT.INTER_CMPNY_TERM01_ID =INTER_COMPANY_TERM01.INTER_CMPNY_TERM01 _ID MATERIAL.MATERIAL_ID=ONTIME_DELIVERY_FACT.M ATERIAL_ID ONTIME_DELIVERY_FACT.MATERIAL_ID=MATERIAL_A LT_UOM.MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE) MATERIAL_BY_PLANT.PLANT_ID=ONTIME_DELIVERY _FACT.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=ONTIME_DELIVE RY_FACT.MATERIAL_ID PLANT.PLANT_ID=ONTIME_DELIVERY_FACT.PLANT_I D PRODUCT_HIERARCHY.PROD_HIER_ID=ONTIME_DEL IVERY_FACT.PROD_HIER_ID SALES_OFFICE.SALES_OFFICE_ID=ONTIME_DELIVE RY_FACT.SALES_OFFICE_ID SALES_ORGANIZATION.SALES_ORG_ID=ONTIME_DE LIVERY_FACT.SALES_ORG_ID SALES_PERSON.SALES_PERSON_ID=ONTIME_DELIV ERY_FACT.SALES_PERSON_ID
MATERIAL_BY_PLANT
PLANT PRODUCT_HIERARCHY SALES_OFFICE SALES_ORGANIZATION SALES_PERSON
112
Dimension Table TIME_DIM TIME_DIM
Join Expression ONTIME_DELIVERY_FACT.ACTL_GI_DATE=TIME_DIM. CALENDAR_DATE ONTIME_DELIVERY_FACT.SCHED_GI_DATE=TIME_DI M.CALENDAR_DATE
113
History On-Time Delivery

Dimension Table CURRENCY CURRENCY CUSTOMER DELIVERY_BLOCK DISTRIBUTION_CHANNEL Join Expression CURRENCY.CURR_ID=ONTIME_DELIVERY_HISTORY. CURR_ID_GBL CURRENCY.CURR_ID=ONTIME_DELIVERY_HISTORY. CURR_ID_TRX CUSTOMER.CUSTOMER_ID=ONTIME_DELIVERY_HIS TORY.CUSTOMER_ID_SHIPTO DELIVERY_BLOCK.DELIV_BLOCK_ID=ONTIME_DELIV ERY_HISTORY.DELIV_BLOCK_ID DISTRIBUTION_CHANNEL.DISTRIBTN_CHANNEL_ID= ONTIME_DELIVERY_HISTORY.DISTRIBTN_CHANNEL_I D ONTIME_DELIVERY_HISTORY.DIVISION_ID=DIVISION. DIVISION_ID ONTIME_DELIVERY_HISTORY.INTER_CMPNY_TERM0 1_ID=INTER_COMPANY_TERM01.INTER_CMPNY_TER M01_ID MATERIAL.MATERIAL_ID=ONTIME_DELIVERY_HISTOR Y.MATERIAL_ID ONTIME_DELIVERY_HISTORY.MATERIAL_ID=MATERIA L_ALT_UOM.MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE) MATERIAL_BY_PLANT.PLANT_ID=ONTIME_DELIVERY _HISTORY.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=ONTIME_DELIVE RY_HISTORY.MATERIAL_ID PLANT.PLANT_ID=ONTIME_DELIVERY_HISTORY.PLAN T_ID PRODUCT_HIERARCHY.PROD_HIER_ID=ONTIME_DEL IVERY_HISTORY.PROD_HIER_ID SALES_OFFICE.SALES_OFFICE_ID=ONTIME_DELIVE RY_HISTORY.SALES_OFFICE_ID SALES_ORGANIZATION.SALES_ORG_ID=ONTIME_DE LIVERY_HISTORY.SALES_ORG_ID SALES_PERSON.SALES_PERSON_ID=ONTIME_DELIV ERY_HISTORY.SALES_PERSON_ID
DIVISION INTER_COMPANY_TERM01
MATERIAL_BY_PLANT
PLANT PRODUCT_HIERARCHY SALES_OFFICE SALES_ORGANIZATION SALES_PERSON
114
Reports Billing
Dimension Table TIME_DIM TIME_DIM
Join Expression ONTIME_DELIVERY_HISTORY.ACTL_GI_DATE=TIME_ DIM.CALENDAR_DATE ONTIME_DELIVERY_HISTORY.SCHED_GI_DATE=TIME _DIM.CALENDAR_DATE
Billing
The billing section stores billing information, including invoices, credit and debit memos, pro-forma items, intercompany invoices, and intercompany credit memos, as well as status information to track bills.
Summary Reports
Using the billing information, you can complete numerous analyses and generate different reports. For example, reports you can generate include:
Operational Revenue per Quarter Bookings vs Billings Credit Memo Analysis Credit Memo Customer Detail Credit Memo Trends
Operational Revenue per Quarter

Operational Revenue for selected Calendar Years by
Calendar Year Calendar Year and Qtr
Charts for each calendar year use the Web Intelligencereport ranking feature.
115
Reports Billing
116
Reports Billing
Report SQL
Bookings vs Billings
Analyze sales orders bookings amounts against invoice amounts for selected Calendar Years - by Company Code - by Sales Rep This report uses two queries, one to retrieve Bookings data, the other to retrieve Billings. It also includes Alerts for when the variance % between net Bookings and Billings amounts is greater than 20%.
Report SQL
Credit Memo Analysis

Analyze credit memos for selected Calendar Year and Quarter by Company Code. This report also includes drill down to Credit Memo Customer Detail report by clicking the desired Customer Name.
117
Reports Billing
Report SQL
Credit Memo Customer Detail

View credit memo details for a specific Customer during a selected Calendar Year and Quarter.
118
Reports Billing
Report SQL
Credit Memo Trends

Analyze credit memo trends for selected Calendar Years. View data by Company Code, Sales Org and Calendar Quarter.
Report SQL

When analyzing data from the billing section, you need to create joins between different tables. Specifically, you need to create joins between the BILLING_FACT table and other dimension tables in the Rapid Mart. Dimension Table BILLING_FACT COMPANY_CODE Join Expression BILLING_FACT.BILL_DOC_ID<> '?' COMPANY_CODE.CMPNY_CODE_ID=BIL LING_FACT.CMPNY_CODE_ID
119
Reports Billing
Dimension Table CONTROLLING_AREA CREDIT_CONTROL_AREA
Join Expression CONTROLLING_AREA.CTRL_AREA_ID=BI LLING_FACT.CTRL_AREA_ID BILLING_FACT.CR_CTRL_AREA_ID = CREDIT_CONTROL_AREA.CR_CTRL_AR EA_ID CURRENCY.CURR_ID=BILLING_FACT.CU RR_ID_GBL CURRENCY.CURR_ID=BILLING_FACT.CU RR_ID_STATS CURRENCY.CURR_ID=BILLING_FACT.CU RR_ID_TRX CUSTOMER.CUSTOMER_ID=BILLING_FA CT.CUSTOMER_ID_PAYER CUSTOMER.CUSTOMER_ID=BILLING_FA CT.CUSTOMER_ID_SOLDTO BILLING_FACT.CUSTOMER_GRP_ID=CUS TOMER_GROUP.CUSTOMER_GRP_ID DISTRIBUTION_CHANNEL.DISTRIBTN_C HANNEL_ID=BILLING_FACT.DISTRIBTN_C HANNEL_ID DIVISION.DIVISION_ID=BILLING_FACT.DI VISION_ID BILLING_FACT.DOC_CATEG_ID=DOCUME NT_CATEGORY.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'SALES' BILLING_FACT.DOC_CATEG_ID=DOCUME NT_TYPE.DOC_CATEG_ID and BILLING_FACT.DOC_TYPE_ID=DOCUMEN T_TYPE.DOC_TYPE_ID and DOCUMENT_TYPE.DIM_SRC_ID = 'SALES' BILLING_FACT.FISC_PERIOD=FISC_PERI OD.FISC_PERIOD and BILLING_FACT.FISC_YEAR=FISC_PERIO D.FISC_YEAR and BILLING_FACT.FISC_YR_VARIANT_ID=FIS C_PERIOD.FISC_YR_VARIANT_ID
CURRENCY CURRENCY CURRENCY CUSTOMER CUSTOMER CUSTOMER_GROUP DISTRIBUTION_CHANNEL
DIVISION DOCUMENT_CATEGORY
DOCUMENT_TYPE
FISC_PERIOD
120
Reports Billing
Dimension Table INTER_COMPANY_TERM01
Join Expression INTER_COMPANY_TERM01.INTER_CMPN Y_TERM01_ID=BILLING_FACT.INTER_CM PNY_TERM01_ID BILLING_FACT.MATERIAL_ID=MATERIAL. MATERIAL_ID BILLING_FACT.MATERIAL_ID=MATERIAL_ ALT_UOM.MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE) MATERIAL_BY_PLANT.PLANT_ID=BILLIN G_FACT.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=BILL ING_FACT.MATERIAL_ID MATERIAL_GROUP.MTRL_GRP_ID=BILLI NG_FACT.MTRL_GRP_ID PAYMENT_TERM.PAYMNT_TERM_ID=BIL LING_FACT.PAYMNT_TERM_ID PLANT.PLANT_ID=BILLING_FACT.PLANT_ ID BILLING_FACT.PRICE_PROCEDURE_ID= PRICING_PROCEDURE_HZ.PRICE_PROC EDURE_ID and PRICING_PROCEDURE_HZ.APPLICTN_ID = 'V' and PRICING_PROCEDURE_HZ.USAGE_ID = 'A' PRODUCT_HIERARCHY.PROD_HIER_ID= BILLING_FACT.PROD_HIER_ID PROFIT_CENTER.PROFIT_CNTR_ID=BILL ING_FACT.PROFIT_CNTR_ID and PROFIT_CENTER.CTRL_AREA_ID=BILLIN G_FACT.CTRL_AREA_ID PROFIT_CENTER_HIER_HZ.PROFIT_CNT R_ID=BILLING_FACT.PROFIT_CNTR_ID and PROFIT_CENTER_HIER_HZ.CTRL_AREA_ ID=BILLING_FACT.CTRL_AREA_ID
MATERIAL_BY_PLANT
MATERIAL_GROUP PAYMENT_TERM PLANT PRICING_PROCEDURE_HZ
121
Reports Billing
Dimension Table PROFIT_CENTER_HIER_VR
Join Expression PROFIT_CENTER_HIER_VR.CHILD_ID=BI LLING_FACT.PROFIT_CNTR_ID and PROFIT_CENTER_HIER_VR.CTRL_AREA _ID=BILLING_FACT.CTRL_AREA_ID BILLING_FACT.PROCESS_STATUS_ID=SA LES_DOC_STATUS.SALES_DOC_STATUS _ID SALES_GROUP.SALES_GRP_ID=BILLING _FACT.SALES_GRP_ID BILLING_FACT.SALES_OFFICE_ID=SALE S_OFFICE.SALES_OFFICE_ID SALES_ORDER_FACT.SALES_DOC_ID=BI LLING_FACT.SALES_DOC_ID and SALES_ORDER_FACT.SALES_LINE_ITEM _ID=BILLING_FACT.SALES_LINE_ITEM_ID SALES_ORGANIZATION.SALES_ORG_ID= BILLING_FACT.SALES_ORG_ID
SALES_DOC_STATUS
SALES_GROUP SALES_OFFICE SALES_ORDER_FACT (Fact to Fact - allows Sales Orders to be used as a Dimension for Billings) SALES_ORGANIZATION
SALES_ORGANIZATION_HIE BILLING_FACT.SALES_ORG_ID=SALES_O R RGANIZATION_HIER.SALES_ORG_ID and BILLING_FACT.SALES_GRP_ID=SALES_O RGANIZATION_HIER.SALES_GRP_ID and BILLING_FACT.SALES_OFFICE_ID=SALE S_ORGANIZATION_HIER.SALES_OFFICE _ID and BILLING_FACT.DISTRIBTN_CHANNEL_ID= SALES_ORGANIZATION_HIER.DISTRIBTN _CHANNEL_ID and BILLING_FACT.DIVISION_ID=SALES_ORG ANIZATION_HIER.DIVISION_ID and @Prompt('Enter Sales Org Hierarchy Date','D',,MONO,FREE) between SALES_ORGANIZATION_HIER.VALID_FR OM_DATE and SALES_ORGANIZATION_HIER.VALID_TO_ DATE SHIPPING_POINT STORAGE_LOCATION SHIPPING_POINT.SHIP_POINT_ID=BILLIN G_FACT.SHIP_POINT_ID BILLING_FACT.PLANT_ID=STORAGE_LO CATION.PLANT_ID and BILLING_FACT.STORAGE_LOCATN_ID=S TORAGE_LOCATION.STORAGE_LOCATN _ID
122
Reports Backlog
Dimension Table TIME_DIM UNIT_OF_MEASURE UNIT_OF_MEASURE
Join Expression BILLING_FACT.CREATE_DATE=TIME_DIM. CALENDAR_DATE UNIT_OF_MEASURE.UOM_ID=BILLING_F ACT.UOM_ID_BASE UNIT_OF_MEASURE.UOM_ID=BILLING_F ACT.UOM_ID_SALES
Backlog
The backlog section stores information about backlog quantitiesthe difference between booked quantities and shipped quantities.
Sample report
Using the backlog information, you can complete numerous analyses and generate different reports. Backlog Analysis is an example of one report you could generate.
Backlog Analysis
Analyze order backlog for selected Plants by:
Product Hierarchy Company Code and Plant
123
Reports Backlog
This report uses the Web Intelligence ranking feature in the charts to see only the Top 10 Materials backlog for each Division.
Report SQL
SELECT SALES_ORGANIZATION.SALES_ORG_DESCR, COMPANY_CODE.CMPNY_CODE_NAME, DIVISION.DIVISION_DESCR, PLANT.PLANT_NAME_01, DISTRIBUTION_CHANNEL.DISTRIBTN_CHANNEL_DESCR, MATERIAL.MTRL_DESCR, UOM_SALES.UOM_DESCR, SUM(BACKLOG_FACT.QTY_BACKLOG_SLSUOM), CURRENCY_GLOBAL.CURR_ISO_CODE, SUM(BACKLOG_FACT.QTY_BACKLOG_SLSUOM*SALES_ORDER_FACT.A MT_NET_PRICE_GBL), PRODUCT_HIERARCHY.LVL_01_DESCR, PRODUCT_HIERARCHY.LVL_02_DESCR FROM SALES_ORGANIZATION, COMPANY_CODE, DIVISION, PLANT, DISTRIBUTION_CHANNEL, MATERIAL, UNIT_OF_MEASURE UOM_SALES, BACKLOG_FACT, CURRENCY CURRENCY_GLOBAL,
124
Reports Backlog
SALES_ORDER_FACT, PRODUCT_HIERARCHY WHERE ( SALES_ORGANIZATION.SALES_ORG_ID=SALES_ORDER_FACT.SALES_O RG_ID ) AND ( DIVISION.DIVISION_ID=SALES_ORDER_FACT.DIVISION_ID ) AND ( DISTRIBUTION_CHANNEL.DISTRIBTN_CHANNEL_ID=SALES_ORDER_FA CT.DISTRIBTN_CHANNEL_ID ) AND ( SALES_ORDER_FACT.MATERIAL_ID=MATERIAL.MATERIAL_ID ) AND ( UOM_SALES.UOM_ID=SALES_ORDER_FACT.UOM_ID_SALES ) AND ( PLANT.PLANT_ID=SALES_ORDER_FACT.PLANT_ID ) AND ( COMPANY_CODE.CMPNY_CODE_ID=SALES_ORDER_FACT.CMPNY_COD E_ID ) AND ( MATERIAL.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID ) AND ( CURRENCY_GLOBAL.CURR_ID=SALES_ORDER_FACT.CURR_ID_GBL ) AND ( BACKLOG_FACT.SALES_DOC_ID=SALES_ORDER_FACT.SALES_DOC_ID AND BACKLOG_FACT.SALES_LINE_ITEM_ID=SALES_ORDER_FACT.SALES_LINE_I TEM_ID ) AND ( SALES_ORDER_FACT.SALES_DOC_ID<> '?' ) AND PLANT.PLANT_NAME_01 In @prompt('Plant Name(s):','A','Plant\Plant Name 1',Multi,Free,Persistent,,User:0) GROUP BY SALES_ORGANIZATION.SALES_ORG_DESCR, COMPANY_CODE.CMPNY_CODE_NAME, DIVISION.DIVISION_DESCR, PLANT.PLANT_NAME_01, DISTRIBUTION_CHANNEL.DISTRIBTN_CHANNEL_DESCR, MATERIAL.MTRL_DESCR, UOM_SALES.UOM_DESCR, CURRENCY_GLOBAL.CURR_ISO_CODE, PRODUCT_HIERARCHY.LVL_01_DESCR, PRODUCT_HIERARCHY.LVL_02_DESCR

BACKLOG_FACT is joined to SALES_ORDER_FACT in the universe. Therefore, BACKLOG_FACT can use any of the dimensions associated with SALES_ORDER_FACT. For the full list of joins, see Recommended table joins on page 92 in the Sales Order section.
125
Reports Schedule Lines
Schedule Lines
The schedule lines section stores detailed information about scheduled deliveries for sales orders. Using data in the schedule lines section, you can complete numerous analyses and generate different reports.
Reports
Schedule line analysis can show how your company is performing on customer requested versus planned delivery date. Included with this Rapid Mart is one report to see Sales Orders Scheduling Efficiency.
126
Sales Orders Scheduling Efficiency

The Sales Orders Scheduling Efficiency report analyzes Sales Order Schedule Lines metrics for a selected Company Code and set of Calendar Year(s):
by Plant by Division
Report SQL
SELECT PLANT.PLANT_NAME_01, DIVISION.DIVISION_DESCR, CUSTOMER_SHIPTO.CUSTOMER_NAME_01, CUSTOMER_SHIPTO.COUNTRY_NAME, CUSTOMER_SHIPTO.REGION_NAME, CUSTOMER_SHIPTO.CITY, AVG(SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE), case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < -60 then 'More than 60 Days Late' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE >= -60 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < -30 then '31 - 60 Days Late' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE >= -30 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < 0 then '1 - 30 Days Late' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE = 0 then 'On Time' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 0 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE <= 30 then '1 - 30 Days Early' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 30 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE <= 60 then '31 - 60 Days Early' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 60 then 'More than 60 Days Early' else 'N/A' end end end end end end end,
127
TIMEDIM_DELIVERY_DATE.CALENDAR_YEAR, AVG(case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < -60 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE >= -60 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < -30 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE >= -30 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < 0 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE = 0 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 0 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE <= 30 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 30 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE <= 60 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 60 then (SALES_SCHED_LINE_FACT.QTY_CONFIRM_SLSUOM) else 0.0 end end end end end end end ) FROM PLANT, DIVISION, CUSTOMER CUSTOMER_SHIPTO, SALES_SCHED_LINE_FACT, TIME_DIM TIMEDIM_DELIVERY_DATE, COMPANY_CODE, SALES_ORDER_FACT SODIM_SCHED_LINES WHERE ( SODIM_SCHED_LINES.SALES_DOC_ID=SALES_SCHED_LINE_FACT.SALE S_DOC_ID and SODIM_SCHED_LINES.SALES_LINE_ITEM_ID=SALES_SCHED_LINE_FAC T.SALES_LINE_ITEM_ID ) AND ( SALES_SCHED_LINE_FACT.DELIV_DATE=TIMEDIM_DELIVERY_DATE.CA LENDAR_DATE ) AND ( PLANT.PLANT_ID=SALES_SCHED_LINE_FACT.PLANT_ID ) AND ( DIVISION.DIVISION_ID=SODIM_SCHED_LINES.DIVISION_ID_HDR ) AND ( COMPANY_CODE.CMPNY_CODE_ID=SODIM_SCHED_LINES.CMPNY_COD E_ID ) AND ( CUSTOMER_SHIPTO.CUSTOMER_ID=SODIM_SCHED_LINES.CUSTOMER_I D_SHIPTO ) AND ( COMPANY_CODE.CMPNY_CODE_NAME = @prompt('Company Code:','A','Company Code\Company Name',Mono,Free,Persistent,,User:1) AND TIMEDIM_DELIVERY_DATE.CALENDAR_YEAR In @prompt('Calendar Year(s):','N','Delivery Date Time Dim\Calendar Year',Multi,Free,Persistent,,User:0) ) GROUP BY
128
PLANT.PLANT_NAME_01, DIVISION.DIVISION_DESCR, CUSTOMER_SHIPTO.CUSTOMER_NAME_01, CUSTOMER_SHIPTO.COUNTRY_NAME, CUSTOMER_SHIPTO.REGION_NAME, CUSTOMER_SHIPTO.CITY, case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < -60 then 'More than 60 Days Late' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE >= -60 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < -30 then '31 - 60 Days Late' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE >= -30 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE < 0 then '1 - 30 Days Late' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE = 0 then 'On Time' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 0 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE <= 30 then '1 - 30 Days Early' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 30 and SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE <= 60 then '31 - 60 Days Early' else case when SALES_SCHED_LINE_FACT.DAYS_EARLY_LATE > 60 then 'More than 60 Days Early' else 'N/A' end end end end end end end, TIMEDIM_DELIVERY_DATE.CALENDAR_YEAR

When analyzing data from the schedule lines section, you need to create joins between the SALES_SCHED_LINE_FACT table and other tables in the Rapid Mart. Dimension Table COMPANY_CODE CONTROLLING_AREA CUSTOMER CUSTOMER CUSTOMER DISTRIBUTION_CHANNEL Join Expression COMPANY_CODE.CMPNY_CODE_ID=SAL ES_ORDER_FACT.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=S ALES_ORDER_FACT.CTRL_AREA_ID CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT.CUSTOMER_ID_BILLTO CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT.CUSTOMER_ID_SHIPTO CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT.CUSTOMER_ID_SOLDTO DISTRIBUTION_CHANNEL.DISTRIBTN_C HANNEL_ID=SALES_ORDER_FACT.DISTR IBTN_CHANNEL_ID
129
Dimension Table DIVISION DOCUMENT_CATEGORY
Join Expression DIVISION.DIVISION_ID=SALES_ORDER_F ACT.DIVISION_ID_HDR SALES_ORDER_FACT.DOC_CATEG_ID=D OCUMENT_CATEGORY.DOC_CATEG_ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'SALES' SALES_ORDER_FACT.DOC_CATEG_ID=D OCUMENT_TYPE.DOC_CATEG_ID and SALES_ORDER_FACT.DOC_TYPE_ID=DO CUMENT_TYPE.DOC_TYPE_ID and DOCUMENT_TYPE.DIM_SRC_ID = 'SALES' SALES_ORDER_FACT.PROFIT_CNTR_ID = PROFIT_CENTER.PROFIT_CNTR_ID AND SALES_ORDER_FACT.CTRL_AREA_ID = PROFIT_CENTER.CTRL_AREA_ID SALES_ORDER_FACT.PROFIT_CNTR_ID = PROFIT_CENTER_HIER_HZ.PROFIT_CNT R_ID AND SALES_ORDER_FACT.CTRL_AREA_ID = PROFIT_CENTER_HIER_HZ.CTRL_AREA_ ID SALES_ORDER_FACT.PROFIT_CNTR_ID = PROFIT_CENTER_HIER_VR.CHILD_ID AND SALES_ORDER_FACT.CTRL_AREA_ID = PROFIT_CENTER_HIER_VR.CTRL_AREA _ID SALES_DISTRICT.SALES_DISTRICT_ID=S ALES_ORDER_FACT.SALES_DISTRICT_I D SALES_GROUP.SALES_GRP_ID=SALES_ ORDER_FACT.SALES_GRP_ID SALES_OFFICE.SALES_OFFICE_ID=SALE S_ORDER_FACT.SALES_OFFICE_ID SALES_ORDER_FACT.SALES_DOC_STAT US_KEY=SALES_ORDER_STATUS.SALES _DOC_STATUS_KEY
DOCUMENT_TYPE
PROFIT_CENTER
SALES_DISTRICT
SALES_GROUP SALES_OFFICE SALES_ORDER_STATUS
130
Dimension Table SALES_ORGANIZATION
Join Expression SALES_ORGANIZATION.SALES_ORG_ID= SALES_ORDER_FACT.SALES_ORG_ID
SALES_ORGANIZATION_HIE SALES_ORDER_FACT.SALES_ORG_ID=S R ALES_ORGANIZATION_HIER.SALES_OR G_ID and SALES_ORDER_FACT.SALES_GRP_ID=S ALES_ORGANIZATION_HIER.SALES_GRP _ID and SALES_ORDER_FACT.SALES_OFFICE_ID =SALES_ORGANIZATION_HIER.SALES_O FFICE_ID and SALES_ORDER_FACT.DISTRIBTN_CHAN NEL_ID=SALES_ORGANIZATION_HIER.DI STRIBTN_CHANNEL_ID and SALES_ORDER_FACT.DIVISION_ID_HDR =SALES_ORGANIZATION_HIER.DIVISION _ID and @Prompt('Enter Sales Org Hierarchy Date','D',,MONO,FREE) between SALES_ORGANIZATION_HIER.VALID_FR OM_DATE and SALES_ORGANIZATION_HIER.VALID_TO_ DATE SALES_PERSON STORAGE_LOCATION SALES_PERSON.SALES_PERSON_ID=SA LES_ORDER_FACT.SALES_PERSON_ID STORAGE_LOCATION.STORAGE_LOCAT N_ID=SALES_ORDER_FACT.STORAGE_L OCATN_ID and STORAGE_LOCATION.PLANT_ID = SALES_ORDER_FACT.PLANT_ID DELIVERY_BLOCK.DELIV_BLOCK_ID=SA LES_SCHED_LINE_FACT.DELIV_BLOCK_I D MATERIAL.MATERIAL_ID=SALES_SCHED _LINE_FACT.MATERIAL_ID SALES_SCHED_LINE_FACT.MATERIAL_ID =MATERIAL_ALT_UOM.MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE)
DELIVERY_BLOCK
131
Dimension Table MATERIAL_BY_PLANT
Join Expression MATERIAL_BY_PLANT.PLANT_ID=SALES _SCHED_LINE_FACT.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=SAL ES_SCHED_LINE_FACT.MATERIAL_ID SALES_SCHED_LINE_FACT.MTRL_GRP_I D=MATERIAL_GROUP.MTRL_GRP_ID PLANT.PLANT_ID=SALES_SCHED_LINE_ FACT.PLANT_ID PRODUCT_HIERARCHY.PROD_HIER_ID= SALES_SCHED_LINE_FACT.PROD_HIER_ ID SALES_ORDER_FACT.SALES_DOC_ID=S ALES_SCHED_LINE_FACT.SALES_DOC_I D and SALES_ORDER_FACT.SALES_LINE_ITEM _ID=SALES_SCHED_LINE_FACT.SALES_L INE_ITEM_ID SALES_SCHED_LINE_FACT.CREATE_DAT E=TIME_DIM.CALENDAR_DATE SALES_SCHED_LINE_FACT.DELIV_DATE =TIME_DIM.CALENDAR_DATE SALES_SCHED_LINE_FACT.GI_DATE=TIM E_DIM.CALENDAR_DATE SALES_SCHED_LINE_FACT.RQST_DELIV _DATE=TIME_DIM.CALENDAR_DATE UNIT_OF_MEASURE.UOM_ID=SALES_SC HED_LINE_FACT.UOM_ID_BASE UNIT_OF_MEASURE.UOM_ID=SALES_SC HED_LINE_FACT.UOM_ID_SALES
MATERIAL_GROUP PLANT PRODUCT_HIERARCHY
SALES_ORDER_FACT
TIME_DIM TIME_DIM TIME_DIM TIME_DIM UNIT_OF_MEASURE UNIT_OF_MEASURE
132
Reports Sales Order History
Sales Order History

The sales order history preservation section tracks changes to sales orders. In particular, the section stores information about deleted sales orders and changes in the quantity or net item value of sales order line items.
Reports
You can perform many different types of analysis on sales order history. Deleted Sales Order Audit is included to show one example of the usefulness of sales order history.
Deleted Sales Order Audit

This report shows the net value of Sales Orders that were deleted by sales representative during the selected Calendar Year. This report includes a graph showing the Top 10 Sales Reps by highest net value (using the Web Intelligence ranking feature).
Report SQL
SELECT SALES_PERSON.SALES_PERSON_FIRST_NAME, SALES_PERSON.SALES_PERSON_LAST_NAME, TIMEDIM_CREATE_DATE.CALENDAR_YEAR, TIMEDIM_CREATE_DATE.CALENDAR_MONTH, TIMEDIM_CREATE_DATE.CALENDAR_QUARTER, sum(SALES_ORDER_HISTORY.AMT_NET_VALUE_DELTA_TRX), sum(SALES_ORDER_HISTORY.QTY_ORDER_DELTA_SLSUOM),
133
Avg (SALES_ORDER_HISTORY.QTY_ORDER_DELTA_SLSUOM), SALES_ORGANIZATION.SALES_ORG_DESCR, SALES_ORDER_HISTORY.CREATE_DATE, SALES_ORDER_HISTORY.VALID_FROM_DATE, COMPANY_CODE.CMPNY_CODE_NAME, COMPANY_CODE.COUNTRY_NAME, SALES_ORDER_HISTORY.SALES_DOC_ID, SALES_ORDER_HISTORY.SALES_LINE_ITEM_ID FROM SALES_PERSON, TIME_DIM TIMEDIM_CREATE_DATE, SALES_ORDER_HISTORY, SALES_ORGANIZATION, COMPANY_CODE, SALES_ORDER_FACT SODIM_SALES_ORDERS_HIST WHERE ( SALES_ORDER_HISTORY.SALES_DOC_ID =SODIM_SALES_ORDERS_HIST.SALES_DOC_ID and SALES_ORDER_HISTORY.SALES_LINE_ITEM_ID=SODIM_SALES_ORDERS _HIST.SALES_LINE_ITEM_ID ) AND ( SALES_ORDER_HISTORY.SALES_PERSON_ID=SALES_PERSON.SALES_PE RSON_ID ) AND ( SALES_ORGANIZATION.SALES_ORG_ID=SALES_ORDER_HISTORY.SALES _ORG_ID ) AND ( SALES_ORDER_HISTORY.CREATE_DATE=TIMEDIM_CREATE_DATE.CALE NDAR_DATE ) AND ( COMPANY_CODE.CMPNY_CODE_ID=SALES_ORDER_HISTORY.CMPNY_C ODE_ID ) AND ( ( SODIM_SALES_ORDERS_HIST.REJECT_REASON_ID = 'DD' ) AND TIMEDIM_CREATE_DATE.CALENDAR_YEAR = @prompt('Calendar Year:','N','Doc. Creation Date Time Dim\Calendar Year',Mono,Free,Persistent,,User:0) ) GROUP BY SALES_PERSON.SALES_PERSON_FIRST_NAME, SALES_PERSON.SALES_PERSON_LAST_NAME, TIMEDIM_CREATE_DATE.CALENDAR_YEAR, TIMEDIM_CREATE_DATE.CALENDAR_MONTH, TIMEDIM_CREATE_DATE.CALENDAR_QUARTER, SALES_ORGANIZATION.SALES_ORG_DESCR, SALES_ORDER_HISTORY.CREATE_DATE, SALES_ORDER_HISTORY.VALID_FROM_DATE, COMPANY_CODE.CMPNY_CODE_NAME, COMPANY_CODE.COUNTRY_NAME, SALES_ORDER_HISTORY.SALES_DOC_ID, SALES_ORDER_HISTORY.SALES_LINE_ITEM_ID
134

When analyzing data from the sales order history preservation section, you need to create joins between the SALES_ORDERS_HISTORY table and other tables in the Rapid Mart. Dimension Table COMPANY_CODE CONTROLLING_AREA CURRENCY CUSTOMER PLANT PROFIT_CENTER Join Expression COMPANY_CODE.CMPNY_CODE_ID=SAL ES_ORDER_HISTORY.CMPNY_CODE_ID CONTROLLING_AREA.CTRL_AREA_ID=S ALES_ORDER_HISTORY.CTRL_AREA_ID CURRENCY.CURR_ID=SALES_ORDER_HI STORY.CURR_ID_TRX CUSTOMER.CUSTOMER_ID=SALES_ORD ER_HISTORY.CUSTOMER_ID_SOLDTO PLANT.PLANT_ID = SALES_ORDER_HISTORY.PLANT_ID SALES_ORDER_HISTORY.CTRL_AREA_I D=PROFIT_CENTER.CTRL_AREA_ID and SALES_ORDER_HISTORY.PROFIT_CNTR _ID=PROFIT_CENTER.PROFIT_CNTR_ID SALES_ORDER_HISTORY.CTRL_AREA_I D=PROFIT_CENTER_HIER_HZ.CTRL_AR EA_ID and SALES_ORDER_HISTORY.PROFIT_CNTR _ID=PROFIT_CENTER_HIER_HZ.PROFIT_ CNTR_ID SALES_ORDER_HISTORY.CTRL_AREA_I D=PROFIT_CENTER_HIER_VR.CTRL_AR EA_ID and SALES_ORDER_HISTORY.PROFIT_CNTR _ID=PROFIT_CENTER_HIER_VR.CHILD_I D SALES_ORGANIZATION.SALES_ORG_ID= SALES_ORDER_HISTORY.SALES_ORG_I D SALES_ORDER_HISTORY.SALES_PERSO N_ID=SALES_PERSON.SALES_PERSON_ ID
SALES_ORGANIZATION
SALES_PERSON
135
Reports Document Flow
Dimension Table
Join Expression
SODIM_SALES_ORDERS_HI SALES_ORDER_HISTORY.SALES_DOC_I ST D =SODIM_SALES_ORDERS_HIST.SALES_ DOC_ID and SALES_ORDER_HISTORY.SALES_LINE_I TEM_ID=SODIM_SALES_ORDERS_HIST.S ALES_LINE_ITEM_ID STORAGE_LOCATION SALES_ORDER_HISTORY.STORAGE_LO CATN_ID=STORAGE_LOCATION.STORAG E_LOCATN_ID and SALES_ORDER_HISTORY.PLANT_ID=ST ORAGE_LOCATION.PLANT_ID SALES_ORDER_HISTORY.CREATE_DATE =TIME_DIM.CALENDAR_DATE UNIT_OF_MEASURE.UOM_ID=SALES_OR DER_HISTORY.UOM_ID_SALES SODIM_SALES_ORDERS_HIST.SALES_D OC_STATUS_KEY=SALES_ORDER_STAT US.SALES_DOC_STATUS_KEY
TIME_DIM UNIT_OF_MEASURE SALES_ORDER_STATUS
Document Flow
The Document Flow is a view (SALES_DOC_FLOW_VIEW) in the Rapid Mart database that joins information from Sales Orders, Deliveries, and Billings. This allows analyses across the entire order fulfillment lifecycle with queries against related sales order, delivery, and billing documents.
Reports
Numerous analyses can be created to analyze the fulfillment lifecycle. The sample report included with this Rapid Mart is Sales Order History Document Flow.
Sales Order History Document Flow

This report shows sales order history document flow by Company Code for orders within the selected Calendar Year(s).
136
Report SQL
SELECT UOM_SALES.UOM_DESCR, CUSTOMER_SOLDTO.CUSTOMER_NAME_01, CUSTOMER_SOLDTO.CUSTOMER_NAME_02, MATERIAL.MTRL_DESCR, sum(SALES_DOC_FLOW_VIEW.QTY_BILL_SLSUOM), SUM(SALES_DOC_FLOW_VIEW.QTY_ORDER_SLSUOM), SALES_DOC_FLOW_VIEW.SALES_DOC_ID, COMPANY_CODE.CMPNY_CODE_NAME, sum(SALES_DOC_FLOW_VIEW.QTY_DELIV_SLSUOM), SODIM_DOCFLOW.CREATE_DATE_HDR, SALES_DOC_FLOW_VIEW.SALES_LINE_ITEM_ID, DOCFLOW_DELIVERY_DIM.DELIV_DATE, DOCFLOW_DELIVERY_DIM.PLAN_GI_DATE, SODIM_DOCFLOW.RQST_DELIV_DATE_HDR, sum(SALES_DOC_FLOW_VIEW.AMT_BILL_NET_VALUE_TRX), sum(SALES_DOC_FLOW_VIEW.AMT_SALES_NET_VALUE_TRX), SODIM_DOCFLOW.CURR_ID_TRX FROM UNIT_OF_MEASURE UOM_SALES,
137
CUSTOMER CUSTOMER_SOLDTO, MATERIAL, SALES_DOC_FLOW_VIEW, COMPANY_CODE, SALES_ORDER_FACT SODIM_DOCFLOW, DELIVERY_FACT DOCFLOW_DELIVERY_DIM, TIME_DIM TIMEDIM_CREATE_DATE WHERE ( SODIM_DOCFLOW.SALES_DOC_ID=SALES_DOC_FLOW_VIEW.SALES_DO C_ID and SODIM_DOCFLOW.SALES_LINE_ITEM_ID=SALES_DOC_FLOW_VIEW.SAL ES_LINE_ITEM_ID ) AND ( DOCFLOW_DELIVERY_DIM.DELIV_ID=SALES_DOC_FLOW_VIEW.DELIV_ ID and DOCFLOW_DELIVERY_DIM.DELIV_LINE_ITEM_ID=SALES_DOC_FLOW_ VIEW.DELIV_LINE_ITEM_ID ) AND ( MATERIAL.MATERIAL_ID=SALES_DOC_FLOW_VIEW.MATERIAL_ID ) AND ( CUSTOMER_SOLDTO.CUSTOMER_ID=SALES_DOC_FLOW_VIEW.CUSTO MER_ID_SOLDTO ) AND ( COMPANY_CODE.CMPNY_CODE_ID = SALES_DOC_FLOW_VIEW.CMPNY_CODE_ID ) AND ( UOM_SALES.UOM_ID=SODIM_DOCFLOW.UOM_ID_SALES ) AND ( SODIM_DOCFLOW.CREATE_DATE=TIMEDIM_CREATE_DATE.CALENDAR _DATE ) AND ( TIMEDIM_CREATE_DATE.CALENDAR_YEAR = @prompt('Calendar Year:','N','Doc. Creation Date Time Dim\Calendar Year',Mono,Free,Persistent,,User:1) AND SALES_DOC_FLOW_VIEW.SALES_DOC_ID In @prompt('Sales Order Number(s):','A','Doc Flow - Additional Details (IDs)\Sales Document Id',Multi,Free,Persistent,,User:0) ) GROUP BY UOM_SALES.UOM_DESCR, CUSTOMER_SOLDTO.CUSTOMER_NAME_01, CUSTOMER_SOLDTO.CUSTOMER_NAME_02, MATERIAL.MTRL_DESCR, SALES_DOC_FLOW_VIEW.SALES_DOC_ID, COMPANY_CODE.CMPNY_CODE_NAME, SODIM_DOCFLOW.CREATE_DATE_HDR, SALES_DOC_FLOW_VIEW.SALES_LINE_ITEM_ID, DOCFLOW_DELIVERY_DIM.DELIV_DATE, DOCFLOW_DELIVERY_DIM.PLAN_GI_DATE, SODIM_DOCFLOW.RQST_DELIV_DATE_HDR, SODIM_DOCFLOW.CURR_ID_TRX
138
Recommended Table Joins

When analyzing data from the sales document flow section, you need to create joins between the SALES_DOC_FLOW_VIEW and other tables in the Rapid Mart. Dimension Table Join Expression
BILLING_FACT (Fact to Fact - BILLING_FACT.BILL_DOC_ID=SALES_DO allows billings to be used as a C_FLOW_VIEW.BILL_DOC_ID and dimension to the view) BILLING_FACT.BILL_LINE_ITEM_ID=SALE S_DOC_FLOW_VIEW.BILL_LINE_ITEM_ID COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = SALES_DOC_FLOW_VIEW.CMPNY_CODE _ID SALES_DOC_FLOW_VIEW.CTRL_AREA_I D= CONTROLLING_AREA.CTRL_AREA_ID CURRENCY.CURR_ID=SALES_DOC_FLO W_VIEW.CURR_ID_GBL CURRENCY.CURR_ID=SALES_DOC_FLO W_VIEW.CURR_ID_TRX CUSTOMER.CUSTOMER_ID=SALES_DOC _FLOW_VIEW.CUSTOMER_ID_BILLTO CUSTOMER.CUSTOMER_ID=SALES_DOC _FLOW_VIEW.CUSTOMER_ID_SHIPTO CUSTOMER.CUSTOMER_ID=SALES_DOC _FLOW_VIEW.CUSTOMER_ID_SOLDTO DELIVERY_FACT.DELIV_ID=SALES_DOC_ FLOW_VIEW.DELIV_ID and DELIVERY_FACT.DELIV_LINE_ITEM_ID=S ALES_DOC_FLOW_VIEW.DELIV_LINE_ITE M_ID DISTRIBUTION_CHANNEL.DISTRIBTN_C HANNEL_ID=SALES_DOC_FLOW_VIEW.D ISTRIBTN_CHANNEL_ID DIVISION.DIVISION_ID=SALES_DOC_FLO W_VIEW.DIVISION_ID
CONTROLLING_AREA
CURRENCY CURRENCY CUSTOMER CUSTOMER CUSTOMER DELIVERY_FACT
DISTRIBUTION_CHANNEL
DIVISION
139
Dimension Table DOCUMENT_CATEGORY
Join Expression SALES_DOC_FLOW_VIEW.DOC_CATEG_I D=DOCUMENT_CATEGORY.DOC_CATEG _ID and DOCUMENT_CATEGORY.DIM_SRC_ID = 'SALES' MATERIAL.MATERIAL_ID=SALES_DOC_F LOW_VIEW.MATERIAL_ID SALES_DOC_FLOW_VIEW.MATERIAL_ID= MATERIAL_ALT_UOM.MATERIAL_ID and MATERIAL_ALT_UOM.UOM_ID_ALT = @Prompt('Enter Alt. Unit of Meas.','A', ,MONO,FREE) MATERIAL_BY_PLANT.PLANT_ID=SALES _DOC_FLOW_VIEW.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=SAL ES_DOC_FLOW_VIEW.MATERIAL_ID PLANT.PLANT_ID=SALES_DOC_FLOW_VI EW.PLANT_ID PROFIT_CENTER.PROFIT_CNTR_ID=SAL ES_DOC_FLOW_VIEW.PROFIT_CNTR_ID SALES_DOC_FLOW_VIEW.CTRL_AREA_I D=PROFIT_CENTER_HIER_VR.CTRL_AR EA_ID and SALES_DOC_FLOW_VIEW.PROFIT_CNTR _ID=PROFIT_CENTER_HIER_VR.CHILD_I D SALES_DISTRICT.SALES_DISTRICT_ID=S ALES_DOC_FLOW_VIEW.SALES_DISTRIC T_ID SALES_GROUP.SALES_GRP_ID=SALES_ DOC_FLOW_VIEW.SALES_GRP_ID SALES_OFFICE.SALES_OFFICE_ID=SALE S_DOC_FLOW_VIEW.SALES_OFFICE_ID SALES_ORDER_FACT.SALES_DOC_ID=S ALES_DOC_FLOW_VIEW.SALES_DOC_ID and SALES_ORDER_FACT.SALES_LINE_ITEM _ID=SALES_DOC_FLOW_VIEW.SALES_LI NE_ITEM_ID
MATERIAL_BY_PLANT
PLANT PROFIT_CENTER PROFIT_CENTER_HIER_VR
SALES_DISTRICT
SALES_GROUP SALES_OFFICE SALES_ORDER_FACT
140
Reports Invalid Documents
Dimension Table SALES_ORGANIZATION
Join Expression SALES_ORGANIZATION.SALES_ORG_ID= SALES_DOC_FLOW_VIEW.SALES_ORG_I D SALES_PERSON.SALES_PERSON_ID=SA LES_DOC_FLOW_VIEW.SALES_PERSON _ID STORAGE_LOCATION.STORAGE_LOCAT N_ID = SALES_DOC_FLOW_VIEW.STORAGE_LO CATN_ID AND STORAGE_LOCATION.PLANT_ID = SALES_DOC_FLOW_VIEW.PLANT_ID
SALES_PERSON
STORAGE_LOCATION
Invalid Documents
This Rapid Mart comes with BILLING_FACT_BAD and SALES_ORDER_FACT_BAD tables. Upon running the Rapid Mart load data is loaded into these tables where there are issues with monetary exchange rates for converting documents to global currency. You have the ability to report on these tables via the Universe.
Reports
Two reports are included to report on Invalid Documents. Sales Order Data Validation and Billing Data Validation.
Sales Order Data Validation

Invalid Sales Documents identified during Rapid Mart load.
141
Report SQL
SELECT SALES_ORDER_FACT_BAD.SALES_DOC_ID, SALES_ORDER_FACT_BAD.SALES_LINE_ITEM_ID, SALES_ORDER_FACT_BAD.ETL_ERROR_ACTN, SALES_ORDER_FACT_BAD.ETL_ERROR_COLUMN, SALES_ORDER_FACT_BAD.AMT_NET_VALUE_HDR_TRX, SALES_ORDER_FACT_BAD.EXCH_TYPE_ID_GBL, SALES_ORDER_FACT_BAD.EXCH_RATE_GBL, SALES_ORDER_FACT_BAD.FROM_FACTOR_GBL, SALES_ORDER_FACT_BAD.TO_FACTOR_GBL, SALES_ORDER_FACT_BAD.AMT_NET_VALUE_HDR_GBL, SALES_ORDER_FACT_BAD.CREATE_DATE_HDR, SALES_ORDER_FACT_BAD.CURR_ID_GBL, SALES_ORDER_FACT_BAD.CURR_ID_TRX, PLANT.PLANT_NAME_01, MATERIAL.MTRL_DESCR FROM SALES_ORDER_FACT_BAD, PLANT, MATERIAL WHERE ( MATERIAL.MATERIAL_ID=SALES_ORDER_FACT_BAD.MATERIAL_ID ) AND ( PLANT.PLANT_ID=SALES_ORDER_FACT_BAD.PLANT_ID ) AND ( SALES_ORDER_FACT_BAD.CREATE_DATE_HDR BETWEEN @prompt('Order Create Date (Start):','D','Sales Order Objects\Order Create Date',Mono,Free,Persistent,,User:1) AND @prompt('Order Create Date (End):','D','Sales Order Objects\Order Create Date',Mono,Free,Persistent,,User:2) AND SALES_ORDER_FACT_BAD.CURR_ID_TRX In @prompt('Document Currency Id(s):','A','Sales Order Objects\Doc Currency Id',Multi,Free,Persistent,,User:0) )
Billing Data Validation

Invalid Billing Documents identified during Rapid Mart load.
Report SQL
142
Recommended Table Joins

These Bad data tables are included to help identify problems with data in the source SAP solutions system. Here are the Rapid Mart joins that would be useful to further analyze the bad data identified by the load.
Invalid Sales Orders

This is the list of joins relevant to Sales Order Fact validation. Dimension Table CUSTOMER DISTRIBUTION_CHANNEL Join Expression CUSTOMER.CUSTOMER_ID=SALES_ORD ER_FACT_BAD.CUSTOMER_ID_SOLDTO DISTRIBUTION_CHANNEL.DISTRIBTN_C HANNEL_ID=SALES_ORDER_FACT_BAD. DISTRIBTN_CHANNEL_ID SALES_ORDER_FACT_BAD.DIVISION_ID_ HDR=DIVISION.DIVISION_ID MATERIAL.MATERIAL_ID=SALES_ORDER _FACT_BAD.MATERIAL_ID MATERIAL_BY_PLANT.PLANT_ID=SALES _ORDER_FACT_BAD.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=SAL ES_ORDER_FACT_BAD.MATERIAL_ID PLANT.PLANT_ID=SALES_ORDER_FACT_ BAD.PLANT_ID SALES_ORGANIZATION.SALES_ORG_ID= SALES_ORDER_FACT_BAD.SALES_ORG _ID
DIVISION MATERIAL MATERIAL_BY_PLANT
PLANT SALES_ORGANIZATION
Invalid Billing Documents

This is the list of joins relevant to Billing Fact validation. Dimension Table CUSTOMER DISTRIBUTION_CHANNEL Join Expression CUSTOMER.CUSTOMER_ID=BILLING_FA CT_BAD.CUSTOMER_ID_SOLDTO DISTRIBUTION_CHANNEL.DISTRIBTN_C HANNEL_ID=BILLING_FACT_BAD.DISTRI BTN_CHANNEL_ID BILLING_FACT_BAD.DIVISION_ID=DIVISI ON.DIVISION_ID
DIVISION
143
Reports SAP Master Data Reports
Dimension Table MATERIAL MATERIAL_BY_PLANT
Join Expression MATERIAL.MATERIAL_ID=BILLING_FACT_ BAD.MATERIAL_ID MATERIAL_BY_PLANT.PLANT_ID=BILLIN G_FACT_BAD.PLANT_ID and MATERIAL_BY_PLANT.MATERIAL_ID=BILL ING_FACT_BAD.MATERIAL_ID PLANT.PLANT_ID=BILLING_FACT_BAD.PL ANT_ID SALES_ORGANIZATION.SALES_ORG_ID= BILLING_FACT_BAD.SALES_ORG_ID
PLANT SALES_ORGANIZATION
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.
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
144
Equipment Hierarchy Data Discovery Functional Location Hierarchy Data Discovery Work Center Hierarchy Data Discovery BOM Hierarchy Data Discovery Organization Unit Data Discovery Position Data Discovery
Activity Hierarchy Data 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,
145
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 ( ( 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.
146
Report SQL
All report SQL is located in the Rapid Mart installation directory under "\Sample\DDL".
147
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
148
Internal Order Hierarchy Data Discovery

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

View Functional Area Hierarchies for a specified Parent Functional Area and Functional Area Hierarchy.
Report SQL
150
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
151
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,
152
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 )
153
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
154
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
155
BOM Hierarchy Data Discovery

View BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.
Report SQL
156
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
157
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,
158
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

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
159
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
160
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
161
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
162
Universe
chapter
Universe Overview
Overview
Before we begin a detailed discussion of the Sales Universes it is important to understand certain concepts that are common to any Rapid Mart Universe.
Overview (this section) Universe Design Principles Hierarchies
Then we can discuss the details of the Universes. The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions contains two universes. The first is a Business Content Universe organized around fact tables and dimensions in a classic star schema layout.
SAP Sales Analysis 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 Sales Analysis Universe is also presented. Customizing the SAP Sales Analysis 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.
164
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
165
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.
166
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.
167
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)
168
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.
169
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
170
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.
171
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.
172
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.
173
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:
174
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.
175
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.
176
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.
177
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.
178
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.
179
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.
180
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.
181
Invalid Hierarchies Layout:
Note: The screenshot above is an example from the SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions.
182
Universe SAP Sales Analysis Universe
SAP Sales Analysis Universe

The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions comes with a single business content universe called SAP Sales Analysis. It is a union of the Rapid Mart subject areas. This chapter describes overall universe design principles, and details of each subject area as well as common dimensions. The SAP solutions Sales and Distribution Module (SD module) represents the complex processes of capturing prospect inquires and quotations, entering sales contracts and sales orders, generating deliveries and customer invoices, and registering returns. To support these processes SAP solutions uses customer, product (material), sales organization, other master data, and numerous reference data. The SAP Sales Analysis universe is a reflection of this complexity. At this writing, it has:
227 Classes 2302 Objects 50 Tables 49 Aliases 248 Joins 10 Contexts 21 Hierarchies 30 Filters
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 Fact Table Dimensions Sales Orders & Backlog Subject Area Schedule Lines Subject Area Deliveries Subject Area Billings Subject Area Sales Order History Subject Area Document Flow Subject Area
183
Current On Time Delivery Subject Area History On Time Delivery Subject Area Invalid Documents Subject Area Universe Validation Using Fact Tables as Dimensions to Other Fact Tables
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
184
Top Level Classes:
185
Measures: The first Top Level class represents the Measures as described in Universe Terminology on page 165. 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, Business Area, etc. 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 Table Dimensions: These classes show dimensions that are linked to only one subject area. Unlike Common Dimensions, they are not shared with other subject areas. 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 Sales Order - Additional Details (Ids) class under SALES ORDERS contains the foreign keys that reference the Organization Structure dimensions. Invalid Data and Hierarchies: These classes are for auditing purposes. They allow you to report records that have failed validation in Data Services and give you the opportunity to correct these errors in SAP solutions. Corrected records will load into the proper tables on the next Data Services job run. 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.
Common Dimensions
Common Dimensions ar those that are shared by more than one subject area (or fact table). They appear as shown below in the universe.
186
Common Dimension Classes (1 of 2):
187
Common Dimension Classes (2 of 2):
CENTRAL ADDRESS
Shows Customer Ship-To address for each line of a sales order. These may be different than the addresses associated with the Ship-To Customer (see below).
CUSTOMER
These classes give details about the business partners that purchase goods and services from your company. There can be several types of customer associated with a sales document, including:
Customer Group Bill To Customer Ship To Customer Sold To Customer Payer Customer
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:
188
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:
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 Sales Document Type - A categorization of a Sales Document as an invoice, credit memo, debit memo, pro forma invoice, or cancellation document. 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. 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
ACCOUNTING DOCUMENT ATTRIBUTES
SALES DOCUMENT ATTRIBUTES
189
INTERCOMPANY TERM01
Describes when in the delivery process the receiver of goods takes physical ownerships of the those goods.
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. Material Group A grouping of materials and services according to their characteristics. Material (Product) Hierarchy Materials can be grouped into hierarchies. Every material (product) can be assigned to one material product hierarchy level.
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: Monetary Currencies The Rapid Marts maintain various currencies, including:
Transaction (Document) Currency - The monetary currency of the sales document Global Currency - a currency defined in Data Services via global variable $G_GLOBAL_CURRENCY. Transaction amounts in other currencies are converted to Global Currency to facilitate reporting in a single currency. Statistics Currency - A monetary currency assigned to the Sales Organization. Thus, offers the ability to consolidate reporting in a single currency at the Sales Organization level.
ORGANIZATION STRUCTURE
Various components that classify transaction documents within your business enterprise. These include:
190
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. Credit Mgmt Risk Class Allows grouping of sales orders and deliveries by the credit risk associated with a particular customer. 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. 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.Sales District - A geographical area by which sales are consolidated 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.
191
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. Shipping Point Organizational unit in Logistics which carries out shipping processing. The shipping point is the part of the company responsible for the type of shipping, the necessary shipping materials and the means of transport. Storage Locations 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.
PEOPLE
People dimensions describing persons with specific job functions in an operational setting:
Sales Person - Person responsible for selling goods to the customer.
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).
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.
192
By analyzing the fixed capital as well, you can expand your profit centers for use as investment centers.
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:
Actual Goods Issue Date Time Dim Doc. Creation Date Time Dim Delivery Date Time Dim Document Date Time Dim Planned Goods Issue Date Time Dim Requested Delivery 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. SAP Master Data universe provides these aliases for Fiscal Period analysis:
Company Code Fiscal Period
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:
Base Unit of Measure Sales Unit of Measure Weight Unit of Measure Volume Unit of Measure Target Sales Unit of Measure
193
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 Billing Fact Delivery Fact Ontime Delivery Fact & History Sales Doc Flow View Sales Order Fact & Backlog Fact Sales Order History Sales Sched Line Fact
BILLING_BLOCK CENTRAL_ADDRESS COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_A REA CREDIT_MGMT_RISK_ CLASS CURRENCY CUSTOMER CUSTOMER_GROUP DELIVERY_BLOCK DELIVERY_PRIORITY DELIVERY_ROUTE DELIVERY_STATUS DISTRIBUTION_CHAN NEL DIVISION DOCUMENT_CATEGO RY DOCUMENT_TYPE FISC_PERIOD INTER_COMPANY_TE RM01 MATERIAL MATERIAL_ALT_UOM MATERIAL_BY_PLANT MATERIAL_GROUP
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
194
Dimension Table
Billing Fact
Delivery Fact
Ontime Delivery Fact & History
Sales Doc Flow View
Sales Order Fact & Backlog Fact
Sales Order History
Sales Sched Line Fact
ORDER_REASON PAYMENT_TERM PLANT PRICING_PROCEDUR E_HZ PRODUCT_HIERARCH Y PROFIT_CENTER PROFIT_CENTER_HIE R_HZ PROFIT_CENTER_HIE R_VR REJECT_REASON SALES_DISTRICT SALES_DOC_STATUS SALES_GROUP SALES_OFFICE SALES_ORDER_STAT US SALES_ORGANIZATIO N SALES_ORGANIZATIO N_HIER SALES_PERSON SHIPPING_POINT STORAGE_LOCATION TIME_DIM UNIT_OF_MEASURE
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
Fact Table Dimensions

Fact Table Dimensions are those that are unique to one subject area (or fact table). In many cases an alias of one fact table is used as a dimension to another fact table.
195
Example: Sales Orders are used as a dimension to Deliveries. The Sales Document ID and Sales Doc Line Item ID appear as foreign keys in the Delivery. This allows us to use the Sales Orders as a dimension. See Using Fact Tables as Dimensions to Other Fact Tables on page 227 for more information. Fact Table Dimensions appear in the universe as shown below: Fact Table Dimension Classes:
BILLING FACT DIMS
Billing Process Status Header: Billing Process Status and Description Billing Sales Orders Fact as DIM: Sales Orders as a Dimension to Billings
DELIVERY FACT DIMS
196
Delivery Priority: Delivery Priority and Description Delivery Sales Orders Fact as DIM: Sales Orders as a Dimension to Deliveries Delivery Status: Various Statuses associated with a Delivery (Picking Status, Packing Status, Goods Issue Status, etc.) Docflow Billing as a DIM: Billings as a dimension to Sale Document Flow Docflow Delivery as a DIM: Deliveries as a dimension to Sales Document Flow Docflow Sales Orders as a DIM: Sales Orders as a dimension to Sales Document Flow Order Reason: Order Reason and Description Reject Reason: Reject Reason and Description Sales Orders Hist - Sales Order as a DIM: Sales Orders as a dimension to Sales Order History Sched Line Sales Orders Fact as DIM: Sales Orders as a dimension to Sales Schedule Lines
SALES DOCUMENT FLOW DIMS
SALES ORDER FACT DIMS
SALES ORDER HISTORY DIMS
SCHEDULE LINE FACT DIMS
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.
Sales Orders & Backlog Subject Area

Sales orders are the primary document for recording sales (or bookings) transactions in SAP solutions. They record the customer, materials, quantities and prices for each sale. Documents in this category include Inquiry, Quotation, Contract, Scheduling Agreement, Sales Order, Return, Credit/ Debit Memo request. Use filters from FILTERS folder to analyze selected sales order categories. Sales orders and backlog are presented together. Backlog is a subset of sales orders representing those line items on a sales order that have not shipped. Backlog appears in the star schema as a subsidiary fact table to sales orders.
197
See Backlog Outer Join in Customizing the SAP Sales Analysis Universe on page 267 for more information on the join between Backlog and Sales Orders.
Sales Order Measures

The sales order measures contain all additive and semi-additive measures for sales orders and backlog. They appear as shown below in the universe: Sales Order Measures
Sales Order Measures: Top Level for Sales Order and Backlog measures. Contains all other classes as sub-classes. Also contains measures that are global counts of sales orders. Backlog Doc. Curr. Measures: Backlog net value measures in document currency. Backlog Global Curr. Measures: Backlog net value measures in global currency Backlog Qty Measures (Sales UOM): Contains Total and Average backlog quantities in Sales Unit of Measure. Sales Order Doc. Curr. Measures: Contains summable monetary measures in document currency. Sales Order Global Curr. Measures: Contains summable monetary measures in global currency. .Sales Order Qty Measures: Contains Total and Average sales quantities in Sales Unit of Measure.
198
Sales Order Subject Area Classes

The sales order subject area classes contain all remaining objects for sales orders and backlog. They appear as shown below in the universe:
SALES ORDERS: Contains the Primary Key attributes for a sales order. Sales Order - Additional Details (Ids): These are the attributes used as Foreign keys to the dimension tables. Sales Order - Additional Details (Descriptive): Attributes that are not foreign keys such as Customers Purchase Order Number, and descriptive texts, Sales Order - Dates and Fiscal Periods: Dates associated with the sales order. Such as Creation Date, Requested Delivery Date, etc. Sales Order - Monetary Currency: These identifiers link to the monetary currency dimensions Sales Order - Values: these are similar to the Sales Order Measures, but do not aggregate (sum, average, min, max, etc.) in queries. Available values include:
Sales Order - Quantities Sales Order Amts - Transaction Currency Sales Order Amts - Global Currency
Sales Order Filters

The following filters are available for sales orders:
199
Sales Order Filters:
Deleted Sales Documents: returns only those sales orders or sales order line items that have been physically deleted in SAP solutions. These have Reject Reason ID = 'DD'. Sales Order Credit Memo Requests: These are sales orders where Sales Doc Category = K. Sales Order Debit Memo Requests: These are sales orders where Sales Doc Category = L Sales Orders Only: These are sales orders where Sales Doc Category = C or I. Sales Order Quotations: These are sales orders where Sales Doc Category = B. Sales Order Returns: These are sales orders where Sales Doc Category = H. Sales Order Service Contracts: These are sales orders where Sales Doc Category = G.
200
Sales Orders & Backlog Star Schema Layout

Heres is the Sales Order and Backlog Star Schema as it appears in the universe:
201
Schedule Lines Subject Area

These are delivery plans for a sales order/scheduling agreement. They instruct the factory as to when a customer expects delivery, and in what quantity. The schedule lines are all about the dates that govern factory logistics planning for each delivery. Some schedule line information comes from the sales order which appears as a dimension table to schedule lines in this subject area.
Schedule Line Measures

The schedule line measures contain all additive and semi-additive measures for schedule lines. They appear as shown below in the universe: Schedule Line Measures
Sched Line Days Early or Late Aging: These measures show how well we are planning to customer requests. Days Early or Late is the difference between the requested customer delivery date on the sales order, and the planned goods issue date on the schedule line. The SAP solutions fields are VBAK.VDATU and VBEP.WADAT respectively. Sched Line Qty Measures: The quantities scheduled, confirmed, etc. Available in both sales unit of measure and base unit of measure.
Schedule Line Subject Area Classes

The schedule line subject area classes contain all remaining objects for schedule lines. They appear as shown below in the universe.
202
Schedule Line Subject Area Classes:
SCHEDULE LINES: Contains the primary key attributes for a schedule line. Schedule Line - Additional Details (Ids): Identifiers used as foreign keys to the various dimensions Schedule Line - Dates and Fiscal Periods: Dates on the schedule line such as Planned Delivery Date, Material Availability Date, Goods Issue Date, etc. Schedule Line - Monetary Currency: Identifiers for the Transaction (or document) Currency and Global Currency, and exchange rates. Schedule Line - Values: Similar to measures, but cannot be aggregated in a report (sum, average, etc.)
Sched Lines - Quantities Sched Line - Amounts
Schedule Line Filters

There are no filters on schedule lines.
203
Schedule Line Star Schema Layout

Below is a graphical representation of the star schema for this subject area as it appears in the universe designer.
Deliveries Subject Area

These record the actual shipments or deliveries to a customer for each sales order. They also capture the return delivery of materials from a customer. They include the quantities delivery dates, material delivered, etc.
204
Deliveries Measures
The delivery measures contain all additive and semi-additive measures for deliveries. They appear as shown below in the universe: Delivery Measures
Delivery Doc Currency Measures: Net price, List Price (Subtotal 1), and Standard cost in Document Currency. Delivery Global Currency Measures: Net price, List Price (Subtotal 1), and Standard cost in Global Currency. Delivery Qty Measures: These are total and average quantities delivered in both sales and base unit of measure. Note: Global currencies values are not carried directly on the delivery. Instead, the global exchange rate from the associated sales order is used to convert the document currency amounts to global currency amounts.
205
Deliveries Subject Area Classes

Delivery Subject Area Classes:
DELIVERIES: The primary key attributes that uniquely define a delivery. Delivery - Additional Details (Ids): Foreign key attributes to the various dimensions associated with deliveries Delivery - Additional Details (Descriptive): Additional attributes that are not foreign keys such as Ship Processing Days. Delivery - Dates and Fiscal Periods: Dates associated with a delivery such as Actual Goods Issue Date Delivery - Values: Non-aggregatable values similar to measures including:

Deliveries Filters
Delivery Amts - Transaction Currency Delivery Amts - Global Currency Delivery - Quantities
Delivery Filters:
Deliveries - Outbound Deliveries only: These are deliveries where the delivery category = J.
206
Deliveries - Returns Deliveries Only: These are deliveries where the delivery category = T.
Deliveries Star Schema Layout

207
Deliveries Star Schema:.
208
Billings Subject Area

The final step in the cycle started with a sales order. These are the invoices, credit memos, and other documents that record how much a customer owes us. Billings are typically generated after a delivery takes place. Use filters to analyze selected billing document categories.
Billings Measures
Billings Measures:
Billing Doc Currency Measures: Net Values, List Price (Subtotal 1), and Standard Cost in document currency. Billing Global Currency Measures: Net Values, List Price (Subtotal 1), and Standard Cost in global currency. Billing Qty Measures: Total and average quantities invoiced in both sales and base units of measure.
209
Billings Subject Area Classes

Billings Subject Area Classes:
BILLINGS: The primary key attributes that uniquely define a billing document. Billing - Additional Details (Ids): Attributes that are foreign keys to the billing dimensions. Billing - Additional Details (Descriptive): Attributes that are not foreign keys such as the Returns Flag. Billing - Dates and Fiscal Periods: Date associated with a billing such as the Billing Date. Billing - Monetary Currency: Currency IDs and exchange rates for the billing document. Billing Values: Values are similar to measures but cannot be aggregated (sum, average, etc.) and include:
Billing Quantities Billing Amts - Transaction Currency Billing Amts - Global Currency
210
Billings Filters
Billings Filters:
Billings Credit Memo Cancellations: These are billings where the billing doc. category = S. Billings Credit Memos: These are billings where the billing doc. category = O. Billings Debit Memos: These are billings where the billing doc. category = P. Billings Invoice Cancellations: These are billings where the billing doc. category = N. Billings Invoices: These are billings where the billing doc. category = M. Billings Pro Forma Invoices: These are billings where the billing doc. category = U.
Billings Star Schema Layout

211
Billings Star Schema:
Sales Order History Subject Area

Sales Orders (as maintained in SAP solutions) are a current snapshot. They cannot tell you what that sales order looked like in the past. Sales Order History allows the Rapid Mart to track changes over time to sales order quantities and sales order amounts. This allows you to see what the sales order looked like in the past.
212
Sales Order History Measures

Sales Order History Measures:
Sales Order History Doc Currency Measures: net item value, and changed (delta) net item value in document currency. Sales Order History Qty Measures: Shows total and average quantities in sales unit of measure. Also shows the quantity change (delta quantity) from the previous version of the sales order.
Sales Order History Subject Area Classes

Sales Order History Subject Area Classes:
SALES ORDER HISTORY: contains the Surrogate Key, which is the primary key that uniquely identifies a Sales Order History record. Sales Order Hist. - Additional Details (IDs): Foreign keys to the dimensions used by Sales Order History. Also includes the sales document number and sales document line item ID. Sales Order Hist. - Additional Details (Descriptive): Non-foreign key fields associated with Sales Order History. Sales Order Hist. - Dates and Fiscal Periods: The validity dates for this Sales Order History record, and the sales order create date. Sales Order Hist. - Monetary Currency: the Transaction (Document) Currency ID.
213
Sales Order Hist. - Values: Similar to measures but cannot be aggregated (Sum, Average, etc.). They include:
Sales Doc Hist. Amts - Transaction Currency Sales Order Hist. - Quantities
Sales Order History Filters

Sales Order History Filters:
Sales Order Hist - Current Records Only: Shows only the most current version of the sales order in the history table. Sales Order Hist - Deleted Records: Shows only history for deleted sales orders. Uses the Reject Reason ID from the associated sales order. Deleted orders have Reject Reason ID = DD. Note: The value DD is maintained by a global variable in the Data Services job. If you change the value in the job, you must change this filter to the same value. Sales Order Hist - Validity Date Range: Allows you to select a date in history to report. Only sales orders current (valid) on that date will be shown in the report. The filter causes the report to prompt you for a date at run time. Example: A sales order was created May 1st and then changed on May 10th. There will be two records in the sales order history. The first, valid from May 1 through May 9. The 2nd valid from May 10 through today.
If you choose a validity date before May 1, the sales order will not appear in the report. If you choose a validity date of May 1 through 9, the first version of the order will appear in the report. If you choose a validity date of May 10 or later, the 2nd version of the order will appear in the report.
Sales Order History Star Schema Layout

Below is a graphical representation of the star schema for this subject area as it appears in the universe designer
214
Sales Order History Star Schema:
Document Flow Subject Area

Document Flow is a union of the Sales Orders, Deliveries, and Billings based on Sales order number and sales order item number. It also contains Organization Structure, customer, and materials. It allows us to report the entire order lifecycle. In the universe (and database), it appears as a view called SALES_DOC_FLOW_VIEW that combines data from the three fact tables.
Document Flow Measures

Document Flow Measures:
Doc Flow Doc Currency Measures: Sales order bookings (received item value), sales order net item value, billing revenue, and billing net value in document currency.
215
Doc Flow Global Currency Measures: Sales order bookings (received item value), sales order net item value, billing revenue, and billing net value in global currency. Doc Flow Qty Measures: Sales order, delivery and invoice (billing) quantities in sales unit of measure. Both total and average measures available.
Document Flow Subject Area Classes

Document Flow Subject Area Classes:
Doc Flow - Additional Details (IDs): Foreign key fields to the various dimensions. For Document Flow, Sales Orders, Deliveries, and Billings are treated as dimensions. Doc Flow - Monetary Currency: Global and Transaction Currency IDs Doc Flow - Values: Similar to measures, but not aggregated (sum, average, etc.). They include:
Doc Flow Billings Amts - Transaction Currency Doc Flow Billings Values - Global Currency Doc Flow - Quantities
Document Flow Filters

Document Flow does not have any filters.
Document Flow Star Schema Layout

216
Document Flow Star Schema:
Current On Time Delivery Subject Area

Measures the how the factory is executing to plan. Compares the scheduled delivery date to the actual delivery date and computes the days early or late for each delivery. Also assists the factory in planning for deliveries by tracking upcoming deliveries as well as missed deliveries.
217
Current On Time Delivery Measures

Current On Time Delivery Measures:
Curr On Time - Days Early or Late Aging (Doc Currency): Ages on time delivery performance (days early or late). Default values are:
More than 60 Days Late 31 to 60 Days Late 1 to 30 Days Late On Time 1 to 30 Days Early 31 to 60 Days Early More than 60 Days Early
You can change these values by revising the case statements in the measures. The values aged by these time periods are total and average delivery quantities, in sales unit of measure. Also provides total and average net value of the delivery in document currency. Curr On Time - Days Early or Late Aging (Global Curr.): Provides equivalent aging time periods for net and average value of the delivery in global currency. Curr On Time Deliv Doc Currency Measures: scheduled and delivered net values in document currency - without aging time periods. Curr On TIme Deliv Global Currency Measures: scheduled and delivered net values in global currency - without aging time periods. Curr On Time Deliv Qty Measures: Total and average delivery quantity and total and average scheduled quantity. All in sales unit of measure - without aging time periods.
218
Current On Time Delivery Subject Area Classes

Current On Time Delivery Subject Area Classes:
CURRENT ON TIME DELIVERY: Includes the Primary Key for Current OnTime Delivery. Curr On Time - Additional Details (IDs): These are foreign keys to the dimensions associated with Current On-Time Delivery Curr On Time - Additional Details (Descriptive): Descriptive attributes that are not foreign keys. Includes a sub-class for the Ship-To address. Curr On Time - Dates and Fiscal Periods: Includes Actual Goods Issue Date and Scheduled Goods Issue Date Curr On Time - Values: Quantities and Values associated with On-Time Delivery. These are not aggregated (sum, average, etc.)
Current On Time Delivery Filters

Sales Order History Filters:
219
Each of the filters works on the Delivery Status maintained by On TIme Delivery. Early Deliveries: Restricts reports to Delivery status = Early. Delivery was made ahead of the planned date. Future Deliveries: Restricts reports to Delivery status = N/A. Delivery is planned for the future and the item has not been delivered. Late Deliveries: Restricts reports to Delivery Status = Late. Delivery was made after the planned date. Missed Deliveries (Did Not Deliver): Restricts reports to Delivery Status = DND. Delivery has not been made and planned date is in the past. On Time Deliveries: Restricts reports to Delivery Status = On Time. Delivery was made on the planned date.
Current On Time Delivery Star Schema Layout

Below is a graphical representation of the star schema for this subject area as it appears in the universe designer. Current On Time Delivery Star Schema:
220
History On Time Delivery Subject Area

Maintains a history of each On Time Delivery snapshot. This allows you to monitor changes in delivery schedules and trend delivery performance over time. Example: your current snapshot of On Time Delivery shows a sales order delivered on schedule. But when you examine the history you find the sales order was rescheduled several times and was originally planned to be delivered weeks earlier. By this measure the delivery is late.
History On Time Delivery Measures

History On Time Delivery Measures:
Hist On Time - Days Early or Late Aging (Doc Currency): Ages on time delivery performance (days early or late). Default values are:
More than 60 Days Late 31 to 60 Days Late 1 to 30 Days Late On Time 1 to 30 Days Early 31 to 60 Days Early More than 60 Days Early
You can change these values by revising the case statements in the measures. The values aged by these time periods are total and average delivery quantities, in sales unit of measure. Also provides total and average net value of the delivery in document currency. Hist On Time - Days Early or Late Aging (Global Curr.): Provides equivalent aging time periods for net and average value of the delivery in global currency.
221
Hist On Time Deliv Doc Currency Measures: scheduled and delivered net values in document currency - without aging time periods. Hist On TIme Deliv Global Currency Measures: scheduled and delivered net values in global currency - without aging time periods. Hist On Time Deliv Qty Measures: Total and average delivery quantity and total and average scheduled quantity. All in sales unit of measure - without aging time periods.
History On Time Delivery Subject Area Classes

History On Time Delivery Subject Area Classes:
HISTORY ON TIME DELIVERY: Includes the Primary Key for Current OnTime Delivery. For history records, the primary key includes the Load Date to identify each snapshot of history. Hist On Time - Additional Details (IDs): These are foreign keys to the dimensions associated with History On-Time Delivery Hist On Time - Additional Details (Descriptive): Descriptive attributes that are not foreign keys. Includes a sub-class for the Ship-To address. Hist On Time - Dates and Fiscal Periods: Includes Actual Goods Issue Date and Scheduled Goods Issue Date Hist On Time - Values: Quantities and Values associated with On-Time Delivery. These are not aggregated (sum, average, etc.)
222
History On Time Delivery Filters

History On Time Delivery Filters:
History Date Range: Prompts user for a beginning and ending date range. Only records with Load Date in the range entered will be shown in the report. Note: Each of the remaining filters (below) works on the Delivery Status maintained by On TIme Delivery. Early Deliveries: Restricts reports to Delivery status = Early. Delivery was made ahead of the planned date. Future Deliveries: Restricts reports to Delivery status = N/A. Delivery is planned for the future and the item has not been delivered. History Date Range: Prompts for a range of Load Dates. This allows you to focus on a range of history snapshots. Late Deliveries: Restricts reports to Delivery Status = Late. Delivery was made after the planned date. Missed Deliveries (Did Not Deliver): Restricts reports to Delivery Status = DND. Delivery has not been made and planned date is in the past. On Time Deliveries: Restricts reports to Delivery Status = On Time. Delivery was made on the planned date.
History On Time Delivery Star Schema Layout

Below is a graphical representation of the star schema for this subject area as it appears in the universe designer
223
History On Time Delivery Star Schema:
Invalid Documents Subject Area

Any sales order or billing documents that are rejected by the Rapid Mart load are stored here. It provides an audit trail of invalid records, and allows users to correct those records in SAP solutions so that they may be properly loaded in the next Rapid Mart refresh. The Rapid Mart validates both sales orders and billings for accurate exchange rates and conversion of monetary values to global currency. Invalid records are not loaded into the Sales Orders Fact or Billing Fact tables. Instead, they are loaded here.
Invalid Documents Measures

Invalid Documents do not have any measures.
224
Invalid Documents Subject Area Classes

Invalid Documents Subject Area Classes:
Invalid Billings: Details the billing number, line item id, load date & time. The error messages detail why the load of this record failed. The Object Names specify the objects that failed to process. Billings Objects: All available objects in the BILLING_FACT table are provided here. Invalid Sales Orders: Details the sales order, line item id, load date & time. The error messages detail why the load of this record failed. The Object Names specify the objects that failed to process. Sales Order Objects: All available objects in the SALES_ORDERS_FACT table are provided here.
Invalid Documents Filters

Invalid Documents do not have any filters.
225
Invalid Documents Star Schema Layout

Invalid Documents Star Schema:
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.
226
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.
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.
Using Fact Tables as Dimensions to Other Fact Tables

One fact table can be a dimension to another.
227
Example: Sales Orders as a Dimension to Deliveries: Deliveries are subsequent documents to a sales order in the Sales Order Lifecycle. The delivery line refers to a single sales order line (the sales order and sales order line are the foreign key on the delivery). However, you can also have a delivery made independent of a sales order (the sales order is not referenced on the delivery). In the SAP Sales Analysis Universe we have introduced aliases for fact tables that will be used as dimensions:
Sales Order Aliases:
SODIM_BILLING - Used in Billings Subject Area SODIM_DELIVERY - Used in Deliveries Subject Area SODIM_DOCFLOW - Used in Document Flow Subject Area SODIM_SALES_ORDERS_HIST - Used in Sales Order History Subject Area SODIM_SCHED_LINES - Used in Schedule Lines Subject Area. DOCFLOW_BILLING_DIM - Used in Document Flow Subject Area DOCFLOW_DELIVERY_DIM - Used in Document Flow Subject Area
Billing Aliases: Delivery Aliases:
To further accommodate the use of fact tables as dimensions we have: In Data Services introduced a default row in:
SALES_ORDER_FACT BILLING_FACT DELIVERY_FACT
As we do for any other dimension, the primary key values in the default rows are set to the default text character defined in the Data Services job by global variable $G_DEFAULT_TEXT.
In the universe, introduced a self-joins on:
SALES_ORDER_FACT BILLING_FACT DELIVERY_FACT
These self-joins remove the default row from any queries where these 3 tables are used as the fact table. The self joins are:
SALES_ORDER_FACT.SALES_DOC_ID<>'?' BILLING_FACT.BILL_DOC_ID<>'?'
228
DELIVERY_FACT.DELIV_ID<>'?'
Note: If youve set global variable $G_DEFAULT_TEXT to a character other than ? you must modify these joins accordingly. Note: The aliases do not have a self join to remove the default row. The default row is needed for cases where there is no referenced sales order.
229
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:
394 classes 4100 objects 199 conditions 261 tables 44 alias 36 joins 0 contexts 26 hierarchies
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
230
Top Level Classes
231
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)
232
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.
233
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.
234
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
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
235
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. 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
236
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.
237
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.
238
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.
239
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
240
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
241
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
242
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.
243
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:
244
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.
245
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
246
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).
ORGANIZATION STRUCTURE
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.
247
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.
248
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.
249
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
250
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
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. 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.
251
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.
252
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.
253
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
People dimensions describing persons with specific job functions in an operational setting:
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:
254
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
255
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
256
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.
257
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

Time related dimensions include relevant time dimensions, fiscal period dimensions, and Calendar dimensions. This class includes the
258
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
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:
259
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
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
Work Center Category Work Center Category Attributes from TC30T. Work Center Formula Capacity formulas from TC25; parameters are parsed from the formula equation text.
260
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
261
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:
262
Master Data Universe (1 of 3)
263
Master Data Universe (2 of 3):
264
Master Data Universe (2 of 3):
Universe Validation - Master Data

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.
265
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. Note: The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.
266
Universe Customizing the SAP Sales Analysis Universe
Customizing the SAP Sales Analysis Universe

The universe can be modified easily to suit your specific needs.
Splitting the Universe: The universe was designed to be all inclusive of the subject areas in the SAP solutions SD module. This is because it is easier to remove subject areas (and simply the universe) than to add subject areas (and make it more complex). Example: If you want to keep certain users from seeing revenue (billing) data you can create a copy of the universe and strip out the Billings Subject Area. (You simply remove the billings tables and objects from the universe).
Additional Common Dimensions: Another modification that is relatively easy is to include additional common dimensions from the sales order with another subject area. Example: You need to know the Sales Person on a Delivery. But, sales person is not available in the DELIVERY_FACT table. However, sales person is available in SALES_ORDER_FACT. You create a join from the SODIM_DELIVERY table (an alias of SALES_ORDER_FACT) to the SALES_PERSON table. Then add the new join to the context for deliveries. Now, you can use the Sales Persons Class in the common dimensions in your reports.
Backlog Outer Join: The join between BACKLOG_FACT and SALES_ORDER_FACT is an inner join. Any query that selects objects from both these tables will only show sales orders that have backlog. Fully delivered sales orders will not appear in the query results. To see the all sales orders in the query, regardless if they have backlog or not, change the join between BACKLOG_FACT and SALES_ORDER fact to and outer join so that all rows in SALES_ORDER_FACT are selected. Note: Use with caution: outer joins can slow query performance. With the outer join, when a sales order has no backlog, NULL values will be returned for Backlog measures. This may cause sums and averages to calculate incorrectly. To avoid this, change the Select clause for Backlog Measures to convert any NULL values to zero.
267
Universe Customizing the SAP Sales Analysis Universe
Here is a complete list of measures that need this change:
268
Installing the Rapid Mart
chapter
Installing the Rapid Mart Overview
Overview
This chapter contains the information you need to install the SAP BusinessObjects Sales 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
270
Installing the Rapid Mart System Prerequisites
System Prerequisites
To run the SAP BusinessObjects Sales 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.
271
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)
272
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
273
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.
274
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.
275
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
276
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.
277
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 SAPSA_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 273 and ReadMe.txt file.
278
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.
279
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.
280
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
281
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 300. 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 SAPSA_Rapid_Mart.atl
Example: The Sales 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
282
Before Replace All
283
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 SAPSA_Rapid_Mart.atl instead of the file name shown in the example.
284
From the Tools Menu choose Import From File:
Choose the ATL File
285
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:
286
Edit the Data Store:
287
Open Advanced Edit Window
288
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):
289
Edit the Data Store:
290
Open Advanced Edit Window
291
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
292
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.
293
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.
294
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
295
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.
296
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.
297
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 \).
298
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.
299
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: sapsa_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.
300
On the first screen, click Next:
301
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 Sales Rapid Mart located in Directory: ...\Visuals File: sapsa_Rapid_Mart_Visuals.biar
302
Choose CMS:
303
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.
304
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.
305
Check Import Scenario Radio Buttons as shown
Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2
306
Incremental Import - Check or Uncheck Boxes:
307
Acknowledge Message, Click Next
308
Select All to import complete contents of BIAR file.
309
Universe & Connection Options- Check or Uncheck as shown
310
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.
311
Select Import Options for Publications:
Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2
312
Acknowledge message, Click Next:
313
Verify Correct List of Objects to Import, Click FINISH to start import:
314
Wait for Import to Finish. Then Click View Detail Log:
Click on each item imported. Make sure there are no errors:
315
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).
316
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:
317
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.
318
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.
320
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.
321
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
322
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 324. 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.
323
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 Sales_Load_SAP executes objects that load the load the data from SAP solutions to Rapid Mart target database. This job contains:
324
Using the Rapid Mart Extraction, transformation and loading process
Job global variable properties. This window can be accessed by rightclicking on the Sales_Load_SAP job and selecting the Properties command from the drop-down list. Most of the Sales 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
325
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
326
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
327
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)
328
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
329
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.
330
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.
331
$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 recreate 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:
332
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
333
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
334
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.
335
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:
336
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
337
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:
338
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
339
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
340
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.
341
$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
342
$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
343
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
344
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
345
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
346
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)
347
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
348
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)
349
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
350
$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"
351
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
352
$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).
353
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.
354
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.
355
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.
356
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 Sales_Load_SAP 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.
357
Using the Rapid Mart Executing the job
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 326. 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 Sales_Load_SAP 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. b. Make sure that the value for the $G_LOAD_TYPE global variable is set to DELTA. 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.
358
Using the Rapid Mart Customizing the Rapid Mart
c. d.
Set values for the rest of global variables as needed. Click OK to accept the set properties and to close the window.
Note: We suggest setting global variables in the job initialization script. That way the Properties window will preserve the as delivered settings, while the initialization script will show your custom settings. The initialization script executes after the values in the Properties window are set, and overrides the setting in the Properties windows. 2. Run the job. a. 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.
Customizing the Rapid Mart

Rapid Marts are easy to customize. You can easily:
Customize the Rapid Mart data schema to meet your specific needs.
359
Using the Rapid Mart Customizing the Rapid Mart
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)
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 415 and in the Rapid Mart Deployment Guide.
360
Technical Implementation
chapter
Technical Implementation Overview
Overview
This chapter provides technical details about how the SAP BusinessObjects Sales 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:
Sales order section Delivery section Billing section Backlog section Schedule lines section Sales order history preservation section On Time Delivery Section Optimization Techniques Dealing with NULL values Fact Table Stored Procedures Fiscal Periods & Time Dim Load
Sales order section

The sales order section of this Rapid Mart stores the transactions for individual sales order documents. The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions extracts sales order header and line-item information from the SAP solutions system. The Rapid Mart calls the C_SalesOrder_Section_SAP work flow to load sales order tables from SAP solutions. First, the section executes work flow WF_SalesOrderDims_SAP to load the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them.
362
Technical Implementation Sales order section
Dimension Table Load

WF_SalesOrderDims_SAP uses these work flow components to load the dimension tables. Work Flow Name C_BillingBlock_SAP C_CentralAddress_SAP C_CompanyCode_SAP Description Populates BILLING_BLOCK during first and delta loads Tables Loaded BILLING_BLOCK
Extracts Central Address table CENTRAL_ADDRESS from SAP table ADRC Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Loads Credit Management Risk Class COMPANY_CODE
C_ControllingArea_SAP
CONTROLLING_AREA
C_CreditControlArea_SAP C_CreditMgmtRisk_SAP C_Currency_SAP
Loads Credit Control Area Dim CREDIT_CONTROL_AREA CREDIT_MGMT_RISK_CL ASS
Dimensional component load- CURRENCY ing currency abbreviations and texts from TCURT, TCURC Performs full extraction of Cur- CURRENCY_CONVERT_R rency Conversion Rate dimen- ATE sion Dimensional component loading consisting of a first and delta load for the customer table from KNA1. Dimensional component loading consisting of a first and delta load for the billing type table from TVV1T. CUSTOMER
C_CurrencyConvRate_SAP
C_Customer_SAP
C_CustomerGroup_SAP
CUSTOMER_GROUP
C_DeliveryBlock_SAP C_DeliveryRoute_SAP C_DistributionChannel_SAP
Populates DELIVERY_BLOCK DELIVERY_BLOCK during first and delta loads Populates ROUTE dimension from TVROT table DELIVERY_ROUTE
Dimensional component load- DISTRIBUTION_CHANNEL ing for the Distribution channel
363
Work Flow Name C_Division_SAP C_DocumentCategory_SAP C_DocumentType_SAP C_GlobalCurrency_SAP
Description Dimensional component loading for Division Dim
Tables Loaded DIVISION
Combined Document Category DOCUMENT_CATEGORY Dim. Combined Document Type Dim. DOCUMENT_TYPE & DOCUMENT_CATEGORY
Dimensional component load- GLOBAL_CURRENCY ing for the GLOBAL_CURRENCY dimension (reporting currency) Dimensional component loading consisting of a first and delta load for the Inter-Company Terms 01 table from TINCT. Dimensional component loading consisting of a first and delta load for the materials table from MARA. Also loads the sales product hierarchy table INTER_COMPANY_TERM0 1
C_InterCmpnyTerm_SAP
C_Material_SAP
MATERIAL, PRODUCT_HIERARCHY
C_MaterialAltUOM_SAP
Dimensional component load- MATERIAL_ALT_UOM ing consisting of a first and delta load for the Material Units Of Measure convention table from MARM and MARA. Dimensional component load- MATERIAL_BY_PLANT ing plant-specific material information such as procurement type and purchasing group from MARC Dimensional component loading MATERIAL_GROUP table from T023T. Populates ORDER_REASON during first and delta loads Dimensional component. Loads payment terms. Standard terms from TVZBT and Own terms from T052U MATERIAL_GROUP
C_MaterialByPlant_SAP
C_MaterialGroup_SAP
C_OrderReason_SAP C_PaymentTerm_SAP
ORDER_REASON PAYMENT_TERM
364
Work Flow Name C_Plant_SAP
Description Dimensional component loading consisting of a first and delta load for the plant table from T001W. Does the following: 1 - Data Flow logic to load PRICING_PROCEDURE_VR table 2 - Pivots PRICING_PROC_VR table to PRICING_PROC_HZ Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (ECPCA Profit center hierarchy in SAP)
Tables Loaded PLANT
C_PricingProcedure_SAP
PRICING_PROCEDURE_H Z
C_ProfitCenter_SAP
PROFIT_CENTER
C_ProfitCenterHier_SAP
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_H Z, PROFIT_CENTER_HIER_V R, PROFIT_CENTER_HIER_B AD
C_RejectReason_SAP C_SalesDistrict_SAP
Populates REJECT_REASON REJECT_REASON during first and delta loads Dimensional component loading SALES_DISTRICT table from T171T. SALES_DISTRICT
C_SalesDocStatus_SAP
Populates SALES_ORDER_STATUS SALES_DOC_STATUS dimension with status information Dimensional component loading for Sales Group Dimensional component loading for Sales Office Dimensional component loading consisting of a first and delta load for the plant table from TVKO and TVKOT. SALES_GROUP SALES_OFFICE SALES_ORGANIZATION
C_SalesGroup_SAP C_SalesOffice_SAP C_SalesOrg_SAP
365
Work Flow Name C_SalesOrgHierarchy_SAP
Description
Tables Loaded
Does the following: 1- INITIAL SALES_ORGANIZATION_ HIER LOAD - Loads into SALES_ORGANIZATION_HIE R and SALES_ORGANIZATION_HIE R_CUR tables 2 - DELTA LOAD - a. Loads into a stage table SALES_O Dimensional component loading for Sales Persons from SAP Table PA0002 (HR master) Dimensional component loading SHIPPING_POINT table from TVSTT. Dimensional component loading storage location descriptions with plant and division assignments from T001L SALES_PERSON
C_SalesPerson_SAP
C_ShippingPoint_SAP
SHIPPING_POINT
C_StorageLocation_SAP
STORAGE_LOCATION
C_TimeDim_SAP
Dimensional component load- TIME_DIM ing generated time periods with SAP fiscal year and calendar parameters. Populates Units of Measure dimension during first and delta loads from Table T006A in SAP UNIT_OF_MEASURE
C_UnitOfMeasure_SAP
Initial load
After loading the dimensions, the work flow determines whether you are loading the sales order table for the first time. If you are, the Rapid Mart executes the initial load work flow WF_SalesOrderFact_SAP. If not, the Rapid Mart executes the incremental load work flow (see Incremental load on page 369.) The initial load job extracts a snapshot of the appropriate SAP solutions data into the SALES_ORDER_FACT table. The job selects from the SAP solutions Sales Order tables (VBAK, VBAP, VBUK, & VBUP) and restricts create and change date fields (VBAK.ERDAT, VBAK.AEDAT) to the range specified by the $G_SDATE and $G_EDATE variables.
366
The extracted snapshot includes data for all sales order categories and types. You can customize the extraction to limit the sales order categories and types by adding conditions to the WHERE clause of the data flow R3_SalesOrdersFact.
Where VBAK.VBTYP IN (<list of values>) - will limit Sales Order Categories Where VBAK.AUART IN (<list of values>) - will limit Sales Order Types.
The sales order section extracts order-related data from SAP solutions header (VBAK) and line item tables (VBAP). It also selects status information from the Header Status table (VBUK) and the Line Item Status Table (VBUP). The section stores the transactions for individual sales order documents in the SALES_ORDER_FACT table. This section does not store the history of data changes to sales orders. It only records the current state of snapshot of sales orders at run time.
Stage Table and Validation Table

Both the first and incremental refreshes use a staging table to prepare sales order information for the Rapid Mart. The table is named SALES_ORDER_STAGE. Data extracted from SAP solutions is loaded here first. Further transformations of the data take place in the stage table. These include lookup of Global Currency exchange rates and of the ship to address for each sales order Once the staging table is fully updated, the global currency exchange rates are validated using a Validation transform in the Rapid Mart. Rows that do not have valid exchange rates are written to the SALES_ORDER_FACT_BAD table. Rows that do have valid exchange rates are written to the SALES_ORDER_FACT table.
Global Currency Logic

Global currency is determined by two global variables set in the Data Services job. $G_GLOBAL_CURRENCY Determines the global currency id. The default is USD (US Dollar) $G_EXCHANGE_TYPE_ID Determines the exchange rate type. It is used to access the SAP solutions currency exchange rate tables as each currency may have more than one exchange type. The default value is M (Standard translation at average rate).
367
The two global variables are used in conjunction with the sales order document currency, and the sales order line item create date to lookup the exchange rate in Rapid Mart table CURRENCY_CONVERT_RATE. Note: line items on the same sales order may have different exchange rates because they were created on different dates. The lookup returns the exchange rate and the From Factor and To Factor. These are all used to covert measures in the document currency to the global currency. The two factors are multiples in which the currency is stored. The formula for currency translation is: Global Currency Value = Doc. Currency Value X Exchange Rate / From Factor / To Factor The following table shows the Document Currency Fields and their corresponding Global Currency Fields in the SALES_ORDER_FACT table: Document Currency Fields AMT_NET_VALUE_TRX AMT_STD_COST_TRX AMT_NET_PRICE_TRX AMT_TRGT_TRX AMT_NET_VALUE_TRX AMT_RECEIVED_TRX AMT_SUBTTL_01_TRX AMT_SUBTTL_02_TRX AMT_SUBTTL_03_TRX AMT_SUBTTL_04_TRX AMT_SUBTTL_05_TRX AMT_SUBTTL_06_TRX Global Currency Fields AMT_NET_VALUE_GBL AMT_STD_COST_GBL AMT_NET_PRICE_GBL AMT_TRGT_GBL AMT_NET_VALUE_GBL AMT_RECEIVED_GBL AMT_SUBTTL_01_GBL AMT_SUBTTL_02_GBL AMT_SUBTTL_03_GBL AMT_SUBTTL_04_GBL AMT_SUBTTL_05_GBL AMT_SUBTTL_06_GBL
Ship-To Address Logic

The ship-to address on each line item of a sales order may be a unique address different from the ship-to customers default address maintained on the customer master. The field: SALES_ORDER_FACT.ADDRESS_ID_SHIPTO stores a link to the CENTRAL_ADDRESSES table. This table contains all the ship-to addresses for sales orders, both default and unique.
368
Ship-To address logic relies on the SAP solutions change history for delta or incremental refreshes. You must make sure the SAP solutions system configuration is set-up to capture changes to table VBPA in the change history (tables CDHDR & CDPOS).
Incremental load
The incremental load job updates all changed sales orders, deletes any cancelled orders, and loads new orders created since the last Rapid Mart refresh. Specifically, the job completes these tasks:
DF_SalesOrderCancelDelta_SAP: Determines sales order line item that have been deleted in SAP solutions by comparing the current contents of SAP solutions tables VBAK and VBAP with the current contents of Rapid Mart table SALES_ORDERS_FACT. This section uses a global variable $G_DEL_PERIOD to determine how far back to look for deleted order lines. The default is 180 days, and can be configured to your individual needs. Note: The Rapid Mart treats deleted sales orders differently than SAP solutions. In SAP solutions, the sales orders are physically deleted from the database. However, the Rapid Mart does not delete the records, but assigns them a reject reason code determined by global variable $G_DEL_REJECT_REASON.
C_SalesOrderNumberDelta_SAP: Collects all new and changed salesorder numbers from SAP solutionss header (VBAK) and line item (VBAP) tables. New and changed orders are identified when the values of these fields are between the $G_SDATE and $G_EDATE global variables:
VBAK.ERDAT - Sales Order header create date VBAK.AEDAT - Sales Order header change date VBAP.ERDAT - Sales Order Line Item create date VBAP.ERDAT - Sales Order Line items change date
This work flow optionally collects new and changed sales order numbers for partner data (table VBPA in SAP solutions). Global variable $G_BUS_PARTNER must be set to Y, and you must make sure the SAP solutions system configuration is set-up to capture changes to VBPA in tables CDHDR & CDPOS tables for this to work. The list of new or changed sales order numbers are written to the flat file OrderNum.dat on the SAP solutions server.
369
DF_SalesOrderStageDelta_SAP: Table SALES_ORDER_STAGE is truncated (all data in the table is deleted). Next, data for the list of sales orders identified in table OrderNum.dat is extracted from SAP solutions and loaded into table SALES_ORDER STAGE. Like the initial load, tables VBAK, VBAP, VBUK, & VBUP are the data sources. DF_BacklogStage_SAP: Table BACKLOG_STAGE is truncated (all data deleted) and backlog information is added from SALES_ORDER_STAGE. This is preparation for updating the BACKLOG_FACT table later on. DF_SalesOrderStageUpdate_SAP: Updates the SALES_ORDER_STAGE table with correct global currency exchange rates. DF_SalesOrdersValidDelta_SAP: validates that all sales orders in SALES_ORDER_STAGE have valid exchange rates. Those without are sent to the SALES_ORDER_FACT_BAD table. Those with, update the SALES_ORDER_FACT table using table comparison transform. WF_SalesOrderDeltaStatus_SAP: This work flow updates the various statuses on the sales orders that have changed.
Processes completed
The Rapid Mart completes several processes when loading the sales order section. The variable values you set affect how the Rapid Mart completes these processes. Processes completed during the load of the sales order section include:
Processing new and changed sales orders Capturing any possible deletion during a limited period Tracing changes for business partners Tracing changes of status fields Processing sales organization hierarchies
Processing new and changed sales orders

The Rapid Mart traces changes in sales document header, line item, and business partners (optional) data. It accumulates document numbers of new and changed records in SAP solutions VBAK, VBAP, and VBPA (optional) tables into a staging file: OrderNum.dat. Then it deletes those sales document records from SALES_ORDERS_FACT to ensure that deleted since previous load line items will be removed from the target before reloading SALES_ORDERS_FACT with new and changed records. Note: the Rapid Mart does not trace deleted free items.
370
Capturing any possible deletion during a limited period

The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions deletes cancelled or deleted orders from SALES_ORDERS_FACT during every incremental load. In most cases sales orders are deleted or canceled shortly after they are created. This method locates deleted or cancelled orders within a set period. By default, the period is 180 days from the extraction date. You can set the period with the $G_DEL_PERIOD variable. The job compares the sales orders in SAP solutions that were created within the defined period to the sales orders in the SALES_ORDERS_FACT table. Note: The Rapid Mart treats deleted sales orders differently than SAP solutions. In SAP solutions, the sales orders are physically deleted from the database. However, the Rapid Mart does not delete the records, but assigns them a reject reason code determined by global variable $G_DEL_REJECT_REASON.
Tracing changes for business partners

If you want to track changes of business partners for sales orders, set the $BUS_PARTNER variable value to 'Y' in the initialization script before running the incremental job. This option activates an additional data flow that extracts changes in business partners from SAP solutions tables. The job appends the resultssales order numbers with modified business partnersto the OrderNum.dat staging file before deleting sales orders from SALES_ORDERS_FACT. Note: Capturing business partner changes can be performance intensive. Note: Business Partner logic relies on the SAP solutions change history for delta or incremental refreshes. You must make sure the SAP solutions system configuration is set-up to capture changes to table VBPA in the change history (tables CDHDR & CDPOS).
Tracing changes of status fields

This is a part of the incremental load. In SAP solutions, the status of a sales document changes if a subsequent sales document is created. For example, the billing status of a sales order will change from 'A' (not yet billed) to 'B' (partially billed) or 'C' (fully billed) if a billing document is created based on that sales order. The sales-order header table and the sales-order line item table will not change, but the status table will reflect this status update. The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions uses the SAP solutions sales document flow table to trace sales document numbers (orders and deliveries) with a status that has changed or that could
371
have changed during the incremental period. The status fields of SALES_ORDERS_FACT are updated after deleted from SAP solutions sales documents are removed from the fact tables. The work flow completes several steps:
Joins the SAP solutions sales document flow table and the sales document item status table to extract sales document numbers, line item numbers, and relevant statuses for those sales documents that have been created or updated in the sales document flow table during the incremental period. Loads the result into a staging table STATUS_STAGE. Joins the SALES_ORDERS_FACT and STATUS_STAGE tables to determine sales-order numbers and line item numbers with corresponding current sales-order statuses.
Processing sales organization hierarchies

The SALES_ORG_HIER dimension preserves the history of changes in the company sales organization hierarchy over time. The initial load populates SALES_ORG_HIER with the current hierarchy. The initial load sets the VALID_FROM field to the current date and the VALID_TO field is set to '9999.12.31'. During every incremental load, changed data causes a new record to be inserted in SALES_ORG_HIER. When a record changes, the VALID_FROM value of that record changes to the date of the load. When processing sales organization hierarchies, the Rapid Mart:
Copies hierarchies from the table SALES_ORG_HIER into a staging table, SALES_HIER_STAGE. Copied hierarchies must be valid after the current date (i.e., VALID_TO > sysdate). Extracts the current SAP solutions hierarchies from SAP solutions and compares them to the hierarchies in SALES_HIER_STAGE using the Table_Comparison transform. Appends any hierarchies from SAP solutions that do not appear in the staging table to SALES_ORG_HIER. Sets the VALID_FROM dates to sysdate, and the VALID_TO dates to '9999.12.31'. Updates every row in SALES_ORG_HIER that has changed compared to the current SAP solutions hierarchies. Resets VALID_TO dates from '9999.12.31' to the current date (sysdate).
The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions maintains the SALES_ORG_HIER_CUR dimension with a snapshot of the current sales organization hierarchy.
372
Technical Implementation Delivery section
Delivery section
The delivery section provides a number of status or reference fields for tracking deliveries. The Rapid Mart extracts delivery information from SAP solutions at the line-item level and stores the data in the delivery fact table. The Rapid Mart extracts all categories of delivery documents, including delivery, returns delivery, shipment and shipping notification. The Rapid Mart calls the C_Delivery_Section_SAP work flow to load tables from SAP solutions.
Dimension table load

First, the Delivery section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses these work flow components to load dimension tables: Work Flow Name C_BillingBlock_SAP C_CompanyCode_SAP Description Populates BILLING_BLOCK during first and delta loads Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Loads Credit Management Risk Class Tables Loaded BILLING_BLOCK COMPANY_CODE
CONTROLLING_AREA
C_CreditControlArea_SAP C_CreditMgmtRisk_SAP C_Currency_SAP
Loads Credit Control Area Dim CREDIT_CONTROL_AREA CREDIT_MGMT_RISK_CL ASS
Dimensional component load- CURRENCY ing currency abbreviations and texts from TCURT, TCURC Performs full extraction of Cur- CURRENCY_CONVERT_R rency Conversion Rate dimen- ATE sion Dimensional component loading consisting of a first and delta load for the customer table from KNA1. CUSTOMER
C_Customer_SAP
373
Work Flow Name C_CustomerGroup_SAP
Description Dimensional component loading consisting of a first and delta load for the billing type table from TVV1T.
Tables Loaded CUSTOMER_GROUP
C_DeliveryBlock_SAP C_DeliveryPriority_SAP C_DistributionChannel_SAP C_Division_SAP C_DocumentCategory_SAP C_DocumentType_SAP C_InterCmpnyTerm_SAP
Populates DELIVERY_BLOCK DELIVERY_BLOCK during first and delta loads Populates DELIV_PRIORITY during first and delta loads DELIVERY_PRIORITY
Dimensional component load- DISTRIBUTION_CHANNEL ing for the Distribution channel Dimensional component loading for Division Dim DIVISION
Combined Document Category DOCUMENT_CATEGORY Dim. Combined Document Type Dim. Dimensional component loading consisting of a first and delta load for the Inter-Company Terms 01 table from ITNCT. Dimensional component loading consisting of a first and delta load for the materials table from MARA. Also loads the sales product hierarchy table DOCUMENT_TYPE & DOCUMENT_CATEGORY INTER_COMPANY_TERM0 1
C_Material_SAP
MATERIAL & PRODUCT_HIERARCHY
Dimensional component load- MATERIAL_ALT_UOM ing consisting of a first and delta load for the Material Units Of Measure convention table from MARM and MARA. Dimensional component load- MATERIAL_BY_PLANT ing plant-specific material information such as procurement type and purchasing group from MARC
374
Work Flow Name C_MaterialGroup_SAP
Description Dimensional component loading consisting of a first and delta load for the MATERIAL_GROUP table from T023T. Dimensional component loading consisting of a first and delta load for the plant table from T001W. Does the following: 1 - Data Flow logic to load PRICING_PROCEDURE_VR table 2 - Pivots PRICING_PROC_VR table to PRICING_PROC_HZ Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (ECPCA Profit center hierarchy in SAP)
Tables Loaded MATERIAL_GROUP
C_Plant_SAP
PLANT
PRICING_PROCEDURE_H Z, PRICING_PROCEDURE_V R
C_ProfitCenter_SAP
PROFIT_CENTER
SALES_DOC_STATUS Populates SALES_DOC_STATUS dimension with status information Dimensional component loading for Sales Group Dimensional component loading for Sales Office Dimensional component loading consisting of a first and delta load for the plant table from TVKO and TVKOT. SALES_GROUP SALES_OFFICE SALES_ORGANIZATION
375
Work Flow Name C_SalesOrgHierarchy_SAP
Description Loads into SALES_ORGANIZATION_HIE R and SALES_ORGANIZATION_HIE R_CUR tables Dimensional component loading consisting of a first and delta load for the SHIPPING_POINT table from TVSTT. Dimensional component loading storage location descriptions with plant and division assignments from T001L
Tables Loaded SALES_ORGANIZATION_ HIER, SALES_ORGANIZATION_ HIER_CUR SHIPPING_POINT
C_ShippingPoint_SAP
STORAGE_LOCATION
C_TimeDim_SAP
Dimensional component load- TIME_DIM ing generated time periods with SAP fiscal year and calendar parameters Populates Units of Measure dimension during first and delta loads from Table T006A in SAP UNIT_OF_MEASURE
C_UnitOfMeasure_SAP
Initial load
After loading the dimensions, the work flow determines whether you are loading the delivery table for the first time. If you are, the Rapid Mart executes the initial load work flow. If not, the Rapid Mart executes the incremental load work flow. The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions uses different algorithms for the initial load and for the incremental load. The initial load job extracts a snapshot of the SAP solutions Delivery tables (LIKP Delivery header, & LIPS - Delivery Line Items) into the DELIVERY_FACT table. The job restricts data to the deliveries created in the range of dates specified by the $G_SDATE and $G_EDATE variables. The extracted snapshot includes data for all delivery categories and types. You can customize the extraction to limit the delivery categories and types extracted by adding constraints to the where clause of the Query in data flow R3_DeliveryFact.
Where LIKP.VBTYP IN (<list of values>) - will limit Delivery Categories
376
Where LIKP.LFART IN (<list of values>) - will limit Delivery Types.
Incremental load
The incremental load job updates all changed sales orders, deletes any cancelled orders, and loads new orders created since the last time the incremental job ran. Specifically, the job completes these tasks:
Collects all new and changed delivery numbers for the incremental date range defined by $G_SDATE and $G_EDATE from SAP solutionss header (LIKP) and line item (LIPS) tables and writes them in the file DelivNum.dat on the SAP solutions server. Uses list of delivery numbers in DelivNum.dat to extract all changed and newly created deliveries and loads the results in the DELIVERY_FACT table using append mode.
Processes completed
The Rapid Mart completes several processes when loading the sales order section. The variable values you set affect how the Rapid Mart completes these processes. Processes completed during the load of the sales order section include:
Processing new and changed sales orders Capturing any possible deletion during a limited period Tracing changes of status fields
Processing new and changed deliveries

The Rapid Mart traces changes in delivery document header and line item data. It accumulates delivery document numbers of new and changed records in SAP solutions tables LIKP & LIPS into a staging file: DelivNum.dat. Then it deletes those delivery records from DELIVERY_FACT to ensure that deleted since previous load line items will be removed from the target before reloading DELIVERY_FACT with new and changed records.
Capturing any possible deletion during a limited period

The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions deletes cancelled or deleted deliveries from DELIVERY_FACT during every incremental load. This is done in data flow R3_DeliveryCancelDelta.
377
In most cases deliveries are deleted or canceled shortly after they are created. This method locates deleted or cancelled deliveries within a set period. By default, the period is 180 days from the extraction date. You can set the period with the $DEL_PERIOD variable. Note: The job compares the deliveries in SAP solutions that were created within the defined period to the deliveries in the DELIVERY_FACT table. The job physically deletes from the Rapid Mart any deliveries not found in SAP solutions.
Tracing changes of status fields

In SAP solutions, the status of a delivery document changes if a subsequent document is created. For example, the picking status of a delivery will change from 'A' (not yet picked) to 'B' (partially picked) or 'C' (fully picked) if a transfer order is created based on that delivery document. The delivery header table and the delivery line item table will not change, but the status table will reflect this status update. The SAP BusinessObjects Sales Rapid Mart, version for SAP solutions uses the SAP solutions sales document flow table (VBFA) to trace delivery document numbers (orders and deliveries) with a status that has changed or that could have changed during the incremental period. The status fields of DELIVERY_FACT are updated after deleted from SAP solutions sales documents are removed from the fact tables. The work flow completes several steps:
Joins the SAP solutions sales document flow table and the sales document item status table to extract sales document numbers, line item numbers, and relevant statuses for those sales documents that have been created or updated in the sales document flow table during the incremental period. Loads the result into a staging table SALES_DOC_STATUS_STAGE.
Joins the DELIVERY_FACT and SALES_DOC_STATUS_STAGE tables to determine delivery numbers and line item numbers with corresponding current delivery statuses. Then, updates DELIVERY_FACT with the current status from SALES_DOC_STATUS_STAGE (in auto-correct mode).
378
Technical Implementation Billing section
Billing section
The billing section extracts billing document information at the billing header and the billing line item level. The fact table stores all header and line item data for the latest version of each and every billing document. The Rapid Mart calls the C_Billing_Section_SAP work flow to load tables from SAP solutions. The following diagram shows the tables that the billing section loads.

First, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses work flow components to load dimension tables. Work Flow Name C_CompanyCode_SAP Description Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Tables Loaded COMPANY_CODE
CONTROLLING_AREA
C_CreditControlArea_SAP C_Currency_SAP
Loads Credit Control Area Dim CREDIT_CONTROL_AREA Dimensional component load- CURRENCY ing currency abbreviations and texts from TCURT, TCURC Performs full extraction of Cur- CURRENCY_CONVERT_R rency Conversion Rate dimen- ATE sion Dimensional component loading consisting of a first and delta load for the customer table from KNA1. Dimensional component loading consisting of a first and delta load for the billing type table from TVV1T. CUSTOMER
C_Customer_SAP
C_CustomerGroup_SAP
CUSTOMER_GROUP
C_DistributionChannel_SAP
Dimensional component load- DISTRIBUTION_CHANNEL ing for the Distribution channel
379
Work Flow Name C_Division_SAP C_DocumentCategory_SAP C_DocumentType_SAP C_FiscalPeriod_SAP
Description Dimensional component loading for Division Dim
Tables Loaded DIVISION
Combined Document Category DOCUMENT_CATEGORY Dim. Combined Document Type Dim. Dimensional component loading Fiscal Year / Fiscal Period data DOCUMENT_TYPE & DOCUMENT_CATEGORY FISC_PERIOD
C_GlobalCurrency_SAP
Dimensional component load- GLOBAL_CURRENCY ing for the GLOBAL_CURRENCY dimension (reporting currency) Dimensional component loading consisting of a first and delta load for the Inter-Company Terms 01 table from TINCT. Dimensional component loading consisting of a first and delta load for the materials table from MARA. Also loads the sales product hierarchy INTER_COMPANY_TERM0 1
C_Material_SAP
Dimensional component load- MATERIAL_ALT_UOM ing consisting of a first and delta load for the Material Units Of Measure convention table from MARM and MARA. Dimensional component load- MATERIAL_BY_PLANT ing plant-specific material information such as procurement type and purchasing group from MARC Dimensional component loading consisting of a first and delta load for the MATERIAL_GROUP table from T023T. MATERIAL_GROUP
C_MaterialGroup_SAP
380
Work Flow Name C_PaymentTerm_SAP
Description Dimensional component. Loads payment terms. Standard terms from TVZBT and Own terms from T052U Dimensional component loading consisting of a first and delta load for the plant table from T001W. Data Flow logic to load PRICING_PROCEDURE_VR & PRICING_PROCEDURE_HZ Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (ECPCA Profit center hierarchy in SAP)
Tables Loaded PAYMENT_TERM
C_Plant_SAP
PLANT
PRICING_PROCEDURE_V R& PRICING_PROCDEDURE_ HZ PROFIT_CENTER
C_ProfitCenter_SAP
Populates SALES_DOC_STATUS SALES_DOC_STATUS dimension with status information Dimensional component loading for Sales Group Dimensional component loading for Sales Office Dimensional component loading consisting of a first and delta load for the plant table from TVKO and TVKOT. Loads into SALES_ORGANIZATION_HIE R and SALES_ORGANIZATION_HIE R_CUR tables SALES_GROUP SALES_OFFICE SALES_ORGANIZATION
C_SalesOrgHierarchy_SAP
SALES_ORGANIZATION_ HIER & SALES_ORGANIZATION_ HIER_CUR
381
Work Flow Name C_ShippingPoint_SAP
Description Dimensional component loading consisting of a first and delta load for the SHIPPING_POINT table from TVSTT. Dimensional component loading storage location descriptions with plant and division assignments from T001L
Tables Loaded SHIPPING_POINT
STORAGE_LOCATION
C_TimeDim_SAP
Dimensional component load- TIME_DIM ing generated time periods with SAP fiscal year and calendar parameters. By default Calendar dates up to 2010.12.31 are loaded. Modify R3_TimeDi Populates Units of Measure dimension during first and delta loads from Table T006A in SAP UNIT_OF_MEASURE
C_UnitOfMeasure_SAP
Initial load
After loading the dimensions, the section determines whether you are loading the billing table for the first time. If you are, the section executes the initial load work flow. In the initial load, billings from SAP solutions tables VBRK (Billing Header) and VBRP (Billing Line Items) are extracted. All billings created in the date range defined by global variables $G_SDATE and $G_EDATE are extracted. Extracted data is loaded to the target table BILLING_STAGE. Global currency exchange rates are determined for the records in BILLING_STAGE. Those that do not have valid exchange rates, are moved from BILLING_STAGE to BILLING_FACT_BAD. Those that do have valid exchange rates are flagged as cancelled or not cancelled, in data flow DF_BillingFactSetCancelFlag_SAP and then moved to BILLING_FACT. The extracted snapshot includes data for all billing categories and types. You can customize the extraction to limit the billing categories and types extracted by adding constraints to the where clause of the Query in data flow R3_BillingFact.
382
Where VBRK.VBTYP IN (<list of values>) - will limit Billing Categories Where VBRK.FKART IN (<list of values>) - will limit Billing Types.
Incremental load
During the incremental load, the work flow that loads BILLING_FACT includes these objects:
Collects all new and changed billing document numbers from SAP solutionss header and line item tables and writes them in the file BillNum.dat on the SAP solutions server. Extracts all changed and newly created billing documents (using the BillNum.dat file) in the incremental period and loads the results in the BILLING_FACT table using Auto Correct mode. During this step (optional) a staging table, BILLING_BACKLOG_STAGE_D is loaded with sales order numbers and invoiced quantities to be used during backlog calculation of drop shipments. Cancellation flag is calculated from new and changed billing documents.
Stage Table and Validation Table

Like sales orders, billings are first loaded to a BILLING_STAGE table. Here transforms such as the lookup of Global Currency exchange rates occur. Once the staging table is fully updated, these lookups are validated using a Validation transform in the Rapid Mart. Rows that do not validate are written to the BAD_BILLING_FACT table. Rows that do pass validation update the BILLING_FACT table.
Global Currency Logic

Global currency in Billings works the same way as in sales orders with one difference. Billings use the header level create date of the billing (rather than the line item create date) to look up the exchange rate. Refer to Sales Order Section -Global Currency Logic for more details on how global currency values are calculated.
383
Technical Implementation Backlog section
Backlog section
The backlog section extracts sales order backlog information at the line-item level. The fact table stores ordered quantity, shipped quantity and the difference between these two columns as backlog quantity. The Rapid Mart calls the C_Backlog_Section_SAP work flow to load backlog tables from SAP solutions.

First, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses work flow components to load dimension tables. Work Flow Name C_CompanyCode_SAP Description Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Dimensional component loading consisting of a first and delta load for the customer table from KNA1. Tables Loaded COMPANY_CODE
CONTROLLING_AREA
C_Customer_SAP
CUSTOMER
C_Material_SAP
Dimensional component load- MATERIAL & ing consisting of a first and PRODUCT_HIERARCHY delta load for the materials table from MARA and the sales product hierarchy Dimensional component load- MATERIAL_BY_PLANT ing plant-specific material information such as procurement type and purchasing group from MARC Dimensional component loading consisting of a first and delta load for the plant table from T001W. PLANT
C_Plant_SAP
384
Work Flow Name C_ProfitCenter_SAP
Description Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (ECPCA Profit center hierarchy in SAP)
Tables Loaded PROFIT_CENTER
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_H Z, PROFIT_CENTER_HIER_V R, PROFIT_CENTER_HIER_B AD STORAGE_LOCATION
Dimensional component loading storage location descriptions with plant and division assignments from T001L
C_TimeDim_SAP
Dimensional component load- TIME_DIM ing generated time periods with SAP fiscal year and calendar parameters
Initial and incremental load

Backlog Section populates BACKLOG_FACT fact table which is a calculated from SALES_ORDERS_FACT, DELIVERY_FACT, and (optionally) BILLING_FACT. These three source tables need to be populated first. After loading the dimensions, the section determines whether you are loading the backlog table 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. During the load, the section completes several processes or steps:
Processing Drop Shipments Backlog First Load Logic Backlog Delta Load Logic
Processing Drop Shipments

(Also called Third Party Delivery): By default, the SAP BusinessObjects Sales Rapid Mart, version for SAP solutions includes sales orders in backlog. These are either:
sales orders delivered by a third party sales orders for services where no tangible product is sold
385
For Drop Ship sales orders, backlog is relieved (reduced) when you bill the customer. For sales orders that are not Drop Ship, backlog is relieved when you deliver to the customer. Drop Shipments are identified in SAP solutions when the billing relevant flag on the sales order line items (VBAP.FKREL) is set to B or F. If you need to exclude these orders in backlog calculation, set the variable $G_DROP_SHIP = N. This will cause the Rapid Mart to compute all backlog based on delivery. Use this setting only if you do not use Drop Shipments. Note: if you have $G_DROP_SHIP = N and you are using Drop Shipments; the Drop Ship orders will always have backlog. Backlog will not be relieved at billing. Note: SAP solutions does not allow for deletion of billing documents. Instead, it allows you to cancel an invoice created in error, and then invoice that sales order again. (For example, you might do this to make a correction). Therefore, the Rapid Mart sums the net effect of invoices and cancellations for Drop Ship sales orders. Thus, if an invoice is created, and then cancelled, the backlog is not reduced. If a second invoice is created, the backlog will be reduced. Example 1 - Invoice Created (all 3 examples assume Sales Order Qty = 10): Invoice 1 Qty 10 Sum (BackBacklog
log reduced by Qty this Amount)
10
Example 2 - Invoice Canceled: Invoice 1 Qty 10 Invoice 1 Canceled Qty -10 Sum (BackBacklog log reduced by Qty this Amount) 0 10
Example 3 - Invoice Reissued: Invoice 1 Qty 10 Invoice 1 Canceled Qty -10 Invoice 2 Qty 7 Sum (Backlog reduced by this Amount)
Backlog Qty 3
386
Backlog First Load Logic

The following Diagrams show how backlog is calculated on the First Load Sales orders, Deliveries, and Billings must be loaded into the Rapid Mart before Backlog can run. Then, the process is shown below:
387
388
Backlog Delta Load Logic

The Delta Load is distributed between the Sales Order Delta, Delivery Delta, Billing Delta, and Backlog Delta as illustrated below:
389
390
391
392
Technical Implementation Schedule lines section
Schedule lines section

The schedule lines section extracts detailed information about scheduled deliveries for sales orders. The fact table in this section only contains sales orders with deliveries. Some sales documents, such as inquiries, quotations, and contracts, are not associated with deliveries. The Rapid Mart calls the C_ScheduleLine_Section_SAP work flow to load tables from SAP solutions.
Dimension load
First, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them.
393
The section uses these work flow components to load dimension tables. Work Flow Name C_DeliveryBlock_SAP C_Material_SAP Description Tables Loaded
Populates DELIVERY_BLOCK DELIVERY_BLOCK during first and delta loads Dimensional component loading consisting of a first and delta load for the materials table from MARA and product hierarchy table MATERIAL & PRODUCT_HIERARCHY
Dimensional component load- MATERIAL_ALT_UOM ing consisting of a first and delta load for the Material Units Of Measure convention table from MARM and MARA. Dimensional component load- MATERIAL_BY_PLANT ing plant-specific material information such as procurement type and purchasing group from MARC Dimensional component loading consisting of a first and delta load for the MATERIAL_GROUP table from T023T. Dimensional component loading consisting of a first and delta load for the plant table from T001W. MATERIAL_GROUP
C_MaterialGroup_SAP
C_Plant_SAP
PLANT
C_TimeDim_SAP
C_UnitOfMeasure_SAP
394
Initial and incremental load

After loading the dimensions, the work flow determines whether you are loading the schedule line fact table for the first time. If you are, the section executes the initial load work flow. If you are not, the section executes the incremental load work flow. The initial load joins tables VBAK (Sales Order Header), VBAP (Sales Order Lines), and VBEP (Schedule Lines) and extracts records created in the date range defined by global variables $G_SDATE and $G_EDATE. The schedule lines table (VBEP) does not have date created or date changed fields. Changes in this table are reflected in change dates on VBAP and VBAK (line item and header tables). The data extracted is used to populate SALES_SCHED_LINE_FACT in the target database. During the incremental (delta) load, the section completes these steps:
DF_SchedLineCanceledDelta_SAP Calculates fully deleted from the source system sales orders by outer-joining SALES_SCHED_LINE_FACT and SAP solutions VBAK source table (Data Flow R3_SalesOrderCancelDelta) records with order create date that falls within a set period (180 days by default} and then removes those records from SALES_SCHED_LINE_FACT. The deletion period is defined by global variable $G_DEL_PERIOD.
395
Technical Implementation Sales order history preservation section
C_SalesOrderNumberDelta_SAP accumulates sales order numbers of new and changed records from VBAK, VBAP. The schedule lines table (VBEP) does not have date created or date changed fields. Changes in this table are reflected in change dates on VBAP and VBAK (line item and header tables). Note: this component is also used in the Sales Orders section, but is set to execute only once per job run.
DF_SchedLineDeltaInsert_SAP inserts new and changed records into SALES_SCHED_LINE_FACT.
Sales order history preservation section

The sales order history preservation section tracks changes to sales orders. The section stores information about deleted sales orders and changes in the quantity or net item value of sales order line items. Because the section calculates changes to the sales orders stored in the SALES_ORDER_FACT table, this section requires that the sales order section run first. First, the Rapid Mart calls the C_SalesOrdersHist_Section_SAP work flow to load tables from SAP solutions. See Sales order section on page 362 for more information about that section.
Dimension load
Next, the section loads the required dimension components. If these dimensions have already been loaded during the current job, the job will not reload them. The section uses these work flow components to load dimension tables. Work Flow Name C_CompanyCode_SAP Description Dimensional component loading Company Codes information from T001 Dimensional component loading Controlling Area information from TKA01 Tables Loaded COMPANY_CODE
CONTROLLING_AREA
C_Currency_SAP
Dimensional component load- CURRENCY ing currency abbreviations and texts from TCURT, TCURC Performs full extraction of Cur- CURRENCY_CONVERT_R rency Conversion Rate dimen- ATE sion
396
Work Flow Name C_Customer_SAP
Description Dimensional component loading consisting of a first and delta load for the customer table from KNA1. Dimensional component loading consisting of a first and delta load for the plant table from T001W. Dimensional component loading Profit Center master data (Dimension) Dimensional component loading profit center hierarchy (ECPCA Profit center hierarchy in SAP)
Tables Loaded CUSTOMER
C_Plant_SAP
PLANT
C_ProfitCenter_SAP
PROFIT_CENTER
PROFIT_CENTER_HIER, PROFIT_CENTER_HIER_H Z, PROFIT_CENTER_HIER_V R, PROFIT_CENTER_HIER_B AD SALES_ORGANIZATION
C_SalesOrg_SAP
Dimensional component loading consisting of a first and delta load for the plant table from TVKO and TVKOT. Loads into SALES_ORGANIZATION_HIE R and SALES_ORGANIZATION_HIE R_CUR tables Dimensional component loading for Sales Persons from SAP Table PA0002 (HR master) Dimensional component loading storage location descriptions with plant and division assignments from T001L
SALES_ORGANIZATION_ HIER & SALES_ORGANIZATION_ HIER_CUR SALES_PERSON
C_SalesPerson_SAP
STORAGE_LOCATION
397
Work Flow Name C_TimeDim_SAP
Description
Tables Loaded
C_UnitOfMeasure_SAP
Next, the section determines whether you are loading the sales order history table 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 and Incremental Load

During the initial load, the section takes a snapshot of the SALES_ORDER_FACT table and loads the data into SALES_ORDER_HISTORY. The QTY_ORDER_DELTA_SLSUOM and AMT_NET_VALUE_DELTA_TRX fields use a global variable ($G_INIT_HIST_CHG) to know what they should be initialized with:
If you want the sum of changes to equal 0 at initialization (i.e. no changes occurred to the sales orders), set $G_INIT_HIST_CHG to Z, and the QTY_ORDER_DELTA_SLSUOM and AMT_NET_VALUE_DELTA_TRX fields will be set to 0 If you want the sum of changes to equal the current qty and value at all times, set $G_INIT_HIST_CHG to (or anything other than Z), and the QTY_ORDER_DELTA_SLSUOM and AMT_NET_VALUE_DELTA_TRX fields will be set to QTY_RECEIVED_SLSUOM and AMT_RECEIVED_TRX from SALES_ORDER_FACT respectively. By Default, $G_INIT_HIST_CHG is set to Z
During the incremental load, the section captures changes to the QTY_ORDER_SLSUOM and AMT_NET_VALUE_TRX fields in SALES_ORDER_FACT. It does so by doing an outer-join between the SALES_ORDER_FACT and SALES_ORDER_HISTORY tables. It selects
rows that dont exist in SALES_ORDER_HISTORY rows where either the QTY_RECEIVED_SLSUOM or AMT_RECEIVED_TRX has changed.
398
Then, these rows are fed to the Table_Comparison, History_Preserving and Key_Generation transforms to create new rows or update existing rows in the SALES_ORDER_HISTORY table.
399
Technical Implementation On Time Delivery Section
On Time Delivery Section

This section uses information derived from the Schedule Lines and Deliveries sections described earlier in this chapter. On Time Delivery allows you to track how well you are delivering to schedule by calculating the days a delivery is early or late. On Time Delivery focuses on a subset of Schedule Line and Delivery information. The idea is focus on the deliveries that are due in the near future or near past. The Rapid Mart relies on a global variable ($G_ONTIME_DELIV_WINDOW) that sets the date range window. The default setting is 15 days. This tells the system to look only at schedule lines that have a Planned Goods Issue Date 15 days in the past or future from today. This allows you to focus on the immediate deliveries due or past due. This date range is expandable, but keep in mind that the loading job will run longer as the window expands. On Time Delivery also has a history table that keeps a copy of all previous runs. This allows you to see how delivery schedules have changed over time. The Rapid Mart calls Work Flow C_OnTime_Delivery_Section to load the On Time Delivery section.
Dimension Load
First, the section loads the Sales Orders, Deliveries, and Schedule Lines sections. If these sections have already been loaded during the job, they will not be reloaded. Then, required dimension components are loaded. 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 the following dimension tables. Work Flow Name C_Currency_SAP Description Tables Loaded
Dimensional component load- CURRENCY ing currency abbreviations and texts from TCURT, TCURC Performs full extraction of Cur- CURRENCY_CONVERT_R rency Conversion Rate dimen- ATE sion
400
Work Flow Name C_Customer_SAP
Description Dimensional component loading consisting of a first and delta load for the customer table from KNA1.
Tables Loaded CUSTOMER
C_DeliveryBlock_SAP C_DistributionChannel_SAP C_Division_SAP C_GlobalCurrency_SAP
Populates DELIVERY_BLOCK DELIVERY_BLOCK during first and delta loads Dimensional component load- DISTRIBUTION_CHANNEL ing for the Distribution channel Dimensional component loading for Division Dim DIVISION
Dimensional component load- GLOBAL_CURRENCY ing for the GLOBAL_CURRENCY dimension (reporting currency) Dimensional component loading consisting of a first and delta load for the Inter-Company Terms 01 table from ITNCT. Dimensional component loading consisting of a first and delta load for the materials table from MARA. Also loads the sales product hierarchy table INTER_COMPANY_TERM0 1
C_Material_SAP
Dimensional component load- MATERIAL_ALT_UOM ing consisting of a first and delta load for the Material Units Of Measure convention table from MARM and MARA. Dimensional component load- MATERIAL_BY_PLANT ing plant-specific material information such as procurement type and purchasing group from MARC Dimensional component loading consisting of a first and delta load for the plant table from T001W. Dimensional component loading for Sales Office PLANT
C_Plant_SAP
C_SalesOffice_SAP
SALES_OFFICE
401
Work Flow Name C_SalesOrg_SAP
Description Dimensional component loading consisting of a first and delta load for the plant table from TVKO and TVKOT. Does the following: 1- INITIAL LOAD - Loads into SALES_ORGANIZATION_HIE R and SALES_ORGANIZATION_HIE R_CUR tables 2 - DELTA LOAD - a. Loads into a stage table SALES_O Dimensional component loading for Sales Persons from SAP Table PA0002 (HR master)
Tables Loaded SALES_ORGANIZATION
SALES_ORGANIZATION_ HIER & SALES_ORGANIZATION_ HIER_CUR
C_SalesPerson_SAP
SALES_PERSON
C_TimeDim_SAP
Dimensional component load- TIME_DIM ing generated time periods with SAP fiscal year and calendar parameters. By default Calendar dates up to 2010.12.31 are loaded. Modify R3_TimeDi
On Time Delivery Processing

The On Time Delivery section is composed of two fact tables ONTIME_DELIVERY_FACT and ONTIME_DELIVERY_HISTORY. There is also a staging table called ONTIME_DELIVERY_STAGE. The section also shares common dimensions with the rest of the Rapid Mart. Sales Orders, Schedule Lines, and Deliveries must be loaded before On Time Delivery processing can occur. Data from the Schedule Lines is merged with data from the deliveries. The delivery quantity is allocated to the schedule line. When there is more than one schedule line or more than one delivery (or both) for an item, we distribute the total delivered quantity for the item across the schedule lines. The earliest schedule line is assigned the quantity from the earliest delivery. Example: The following is an example of how On Time Delivery allocates delivered quantities and computes delivery statuses.
402
Delivery Quantity Allocation

A sales order item has three schedule lines, each with an order quantity of 50 pieces. You make two deliveries: the first for 20 pieces, the second for 60 pieces. The delivered quantity allocated to the first schedule line is 50 pieces (20 from the first delivery and 30 from the second delivery). This leaves 30 pieces remaining on the second delivery, which is allocated to the second schedule line. The allocation quantity for the third schedule line is zero. If you delete the first delivery (20 pieces), the delivered quantity for this schedule line is still 50 pieces, but now this allocated from the second delivery. There are still 10 pieces available on the second delivery to further allocate. The system allocates the remaining 10 pieces to the next schedule line. The third schedule line still has zero allocated. The tables below illustrate this example:
403
With Both Deliveries:

Sched Line Number 1 2 3 Second Delivery 1 2 3 2 2 2 50 50 50 60 60 60 30 30 0 DelivSched Delivery Line Qty ery Qty Number 1 1 1 50 50 50 20 20 20 Allocated Delivery Qty 20 0 0
First Delivery
With First Delivery Deleted:

Sched Line Number 1 2 3 DelivSched Delivery Allocated ery Line Qty Qty Delivery Number Qty 2 2 2 50 50 50 60 60 60 50 10 0
Second Delivery Only
Days Early or Late

The Rapid Mart calculates how late or early a delivery is. The formula uses the Planned Goods Issue Date from the Schedule Line and the Actual Goods Issue Date from the Delivery. These correspond to the SAP solutions fields VBEP.WADAT and LIKP.WADAT_IST, respectively. If the Planned Goods Issue Date is in the past and there is no Delivery, we use the current system date instead to the Actual Goods Issue Date. The formula (with Delivery): Days Early or Late = Planned Goods Issue Date - Actual Goods Issue Date The formula (without Delivery): Days Early or Late = Planned Goods Issue Date - Current System Date
404
A late delivery will be a negative number, and an early delivery will be a positive number. Zero indicates an on time delivery.
Delivery Status
Each schedule line is also assigned a delivery status based on these two dates. EARLY - The Actual Goods Issue Date is before the Planned Goods Issue Date ON TIME - Actual Goods Issue Date and Planned Goods Issue Date are the same LATE - Actual Goods Issue Date is after the Planned Goods Issue Date DND - (Did Not Deliver) Planned Goods Issue Date is in the Past and there is no Delivery. This is a missed delivery. N/A - (Not Applicable) Planned Goods Issue Date is in the future and there is no Delivery. No delivery is due yet
Change Status
The final feature in On Time Delivery is the ability to focus on changes between runs. The Rapid Mart initially loads data to a staging table and compares this stage table to the results of the last run (using a table comparison transform). A change status is assigned by doing this comparison: NEW - The schedule line / delivery combination was not included in the previous run, but is in the current run. This may be because the record is new in the SAP solutions system or because, until now, the Planned Goods Issue Date was outside the date range set by the global variable. On the very first run of On Time Delivery all records will be assigned status NEW. CHANGE - The schedule line / delivery information has changed since the previous run. A change in any of the fields in the On Time Delivery fact table when compared to the previous run will generate this change status. NO CHANGE - The schedule line / delivery information has not changed since the previous run. DELETED - The schedule line / delivery combination was in the previous run, but not the current run. This may be because of physical deletion of records in SAP solutions, or because the Planned Goods Issue Date has changed and is now outside the date range set by the global variable.
405
On Time Delivery Custom Functions

On Time Delivery uses three custom functions to allocate delivery quantity, compute days early (or late), and compute delivery status:
Delivery_Qty_Allocation Determine_Days_Early_Late Determine_Delivery_Status
On Time Delivery History

This is the history of each On Time Delivery run. Once processing of the stage table is complete, its records are added to the history table (ONTIME_DELIVERY_HISTORY) in append mode. This allows you to see how delivery schedules have changed over time. Example: your current snapshot of On Time Delivery shows a sales order delivered on schedule. But when you examine the history table you find the sales order was rescheduled several times over a period of weeks and was originally planned to be delivered weeks earlier. By this measure the delivery is late. The primary key for the history table is the same as the other two tables (ONTIME_DELIVERY_FACT & ONTIME_DELIVERY_STAGE) with addition of Load Date. The additional field is complete date and timestamp. It allows us to maintain a history of each run. This table will grow as the results of each new run are appended. You can keep as much history as you like by creating a custom purge routine.
Table Usage
Here is a quick summary of how each of the 3 On Time Delivery tables is used in the Rapid Mart: ONTIME_DELIVERY_STAGE is the stage table. It is where the data from schedule lines and deliveries is loaded first. Most processing occurs in this table. It is truncated (all data in it deleted) at the beginning of each On Time Delivery run. Delivery quantity allocation, calculation of Days Early or Late, assignment of Delivery Status and assignment of Change Status all occur here. Change status is determined by comparing the contents of this table to ONTIME_DELIVERY_FACT (results of previous run). This table does not appear in the Rapid Mart universe as it is only used to stage data. Its primary key consists of:
Sales Order Number Sales Order Line Item
406
Technical Implementation Optimization Techniques
Schedule Line Number Delivery Number Delivery Line Number
ONTIME_DELIVERY_FACT contains the results of the latest load of On Time Delivery. Once the processing of the stage table is complete, this table is truncated and the contents of the stage table are copied to it. It shares the same primary key as the stage table. it appears in the Rapid Mart universe as the Current On Time Delivery classes. ONTIME_DELIVERY_HISTORY is the history of each On Time Delivery run. Once processing of the stage table is complete, its records are added to the history table in append mode. The primary key is the same as the other two tables with addition of Load Date. The Load Date is a complete date and timestamp. It allows us to maintain a history of each run. This table will grow as the results of each new run are appended. You can keep as much history as you like by creating a custom purge routine.
Optimization Techniques
Within Data Services there are several optimization techniques available. Some of these are used extensively in the Sales 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.
407
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:
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
General Ledger
408
Rapid Mart General Ledger
Subject Area Tables 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
Plant Maint.
Projects
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 login and password. Providing the missing bulkloader log-in and password prevents this from happening.
409
Here is an example of how to use a Data Transfer::
Key Transforms Circled in RED.
In this example the 3 circled transforms are the key to this optimization. Within the Data Transfer:
Enable Transfer is checked Transfer Type is Automatic Join Rank is 0 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:
410
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: Before Split (Single Data Flow):
411
After Split 1 of 2 Data Flows (Horizontal):
After Split 2 of 2 Data Flows (Vertical):
412
Technical Implementation Dealing with NULL values
The 2 Split Data Flows in Context.
Dealing with NULL values

As the first step in data cleansing, the SAP BusinessObjects Sales 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.
413
Technical Implementation Dealing with NULL values
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.
414
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.
415
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
416
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.
417
418
Documentation References
chapter
Documentation References Data Services Documentation References
The SAP BusinessObjects Sales 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:
420
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:
421
Documentation References BusinessObjects Enterprise Documentation References
422
Rapid Mart Data Schema
appendix
Appendix Table Summary

This appendix provides detailed information about the tables and views in the SAP BusinessObjects Sales 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
BILLING_BLOCK CENTRAL_ADDRESS COMPANY_CODE CONTROLLING_AREA CREDIT_CONTROL_AREA CREDIT_MGMT_RISK_CLASS CURRENCY CURRENCY_CONVERT_RATE CUSTOMER CUSTOMER_GROUP DELIVERY_BLOCK DELIVERY_PRIORITY DELIVERY_ROUTE DELIVERY_STATUS DISTRIBUTION_CHANNEL DIVISION DOCUMENT_CATEGORY DOCUMENT_TYPE FISC_PERIOD GLOBAL_CURRENCY INTER_COMPANY_TERM01 MATERIAL MATERIAL_ALT_UOM MATERIAL_BY_PLANT MATERIAL_GROUP ORDER_REASON PAYMENT_TERM PLANT
Appendix Table Summary PRICING_PROCEDURE_HZ PRICING_PROCEDURE_VR PRODUCT_HIERARCHY PROFIT_CENTER PROFIT_CENTER_HIER PROFIT_CENTER_HIER_BAD PROFIT_CENTER_HIER_HZ PROFIT_CENTER_HIER_VR REJECT_REASON SALES_DISTRICT SALES_DOC_STATUS SALES_GROUP SALES_OFFICE SALES_ORDER_STATUS SALES_ORGANIZATION SALES_ORGANIZATION_HIER SALES_ORGANIZATION_HIER_CUR SALES_PERSON SHIPPING_POINT STORAGE_LOCATION TIME_DIM TIME_DIM_WEEKLY UNIT_OF_MEASURE
Fact Tables
BACKLOG_FACT BILLING_FACT DELIVERY_FACT ONTIME_DELIVERY_FACT ONTIME_DELIVERY_HISTORY SALES_ORDER_FACT SALES_ORDER_HISTORY SALES_SCHED_LINE_FACT
Staging Tables
AVAILABLE_DELIVERY_STAGE BACKLOG_STAGE BILLING_BACKLOG_STAGE BILLING_BACKLOG_STAGE_D BILLING_STAGE DELIVERY_BACKLOG_STAGE_D FISC_PERIOD_STAGE
Appendix Table Summary ONTIME_DELIVERY_STAGE SALES_DOC_STATUS_STAGE SALES_ORDER_STAGE SALES_ORGANIZATION_HIER_STAGE
Validation Tables
BILLING_FACT_BAD SALES_ORDER_FACT_BAD
Appendix Table Column Details
AVAILABLE_DELIVERY_STAGE
This is a table that is used to keep tract of Delivery Qty allocated to sales order schedule lines. Needed because a delivery can be allocated to more than one schedule
# Column Name Key Column Desc Column Datatype Dtype Length Precision Scale Is Nullable
DELIV_ID
PK
LIPS-VBELN - Delivery
NVARCSTR
10
no
DELIV_LINE_ITEM_ID PK
LIPS-POSNR - Delivery Item
NVARCSTR
no
LOAD_DATE
Date and Time loaded into Rapid Mart
DATETIME
24
yes
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
yes
QTY_AVAIL_SLSUOM
LIPS-LFIMG - Actual Qties Delivered (in Sales DECIMAL Units)
48
13
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
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
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
BACKLOG_FACT
Difference Between Ordered and Shipped Quantities and Amounts
CMPNY_CODE_ID
PK
VBAK.BUKRS_VF -- Company Code
NVARCSTR
yes
CREATE_DATE_SALE S CREATE_DATE_SALE PK S_HDR
ORDER_FACT.CREATED_ON - Date When the Document was created
DATETIME
24
yes
SALES_ORDERS_FACT-CREATE_DATE_SA DATETIME LES_HDR
24
yes
CTRL_AREA_ID
PK
VBAK.KOKRS - Controlling Area
NVARCSTR
yes
CUSTOMER_ID_SOLD PK TO
ORDER_FACT.CUSTOMER_ID_SOLDTO Customer Number
NVARCSTR
10
yes
LOAD_DATE
Date Time when the record was loaded
DATETIME
24
yes
LOAD_TIME
Time in HH24:MI:SS string format when the record was created
NVARCSTR
yes
MATERIAL_ID
VBAP.MATNR - Material
NVARCSTR
18
yes
PLANT_ID
PK
VBAP.WERKS Plant
NVARCSTR
yes
10
PROFIT_CNTR_ID
PK
VBAP.PRCTR - Profit Center
NVARCSTR
10
yes
11
QTY_BACKLOG_SLSU OM
ORDER_FACT.QTY DELIVERY_FACT.QTY_SALES_UNITS DELIVERY_FACT.QTY_SALES_UNITS Actually Delivered Qty
DECIMAL
48
15
yes
12
QTY_DELIV_SLSUOM
DECIMAL
48
15
yes
13
QTY_ORDER_SLSU OM
ORDER_FACT.QTY - Cumulative Sales Order DECIMAL Qty
48
15
yes
14
SALES_DOC_ID
PK
VBAP-VBELN - Sales Document
NVARCSTR
10
no
15
SALES_LINE_ITEM_ID PK
VBAP-POSNR - Sales Document Item
NVARCSTR
no
16
SALES_TO_BASE_DIV ISOR
Denominator (divisor) to convert Sales UOM of INTEGER Material into its Base UOM
yes
Appendix Table Column Details SALES_TO_BASE_MU LTIPLR STORAGE_LOCATN_I PK D Numerator (factor) to convert Sales UOM of Material into its Base UOM
17
INTEGER
yes
18
VBAP.LGORT Storage location
NVARCSTR
yes
BACKLOG_STAGE
Difference Between Ordered and Shipped Quantities and Amounts
CMPNY_CODE_ID
VBAK.BUKRS_VF -- Company Code
NVARCSTR
yes
CREATE_DATE_SALE S CREATE_DATE_SALE PK S_HDR
ORDER_FACT.CREATED_ON - Date When the Document was created
DATETIME
24
yes
SALES_ORDERS_FACT-CREATE_DATE_SA DATETIME LES_HDR
24
yes
CTRL_AREA_ID
PK
NVARCSTR
yes
ORDER_FACT.CUSTOMER_ID_SOLDTO Customer Number
NVARCSTR
10
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MATERIAL_ID
VBAP.MATNR - Material
NVARCSTR
18
yes
PLANT_ID
PK
VBAP.WERKS Plant
NVARCSTR
yes
10
PROFIT_CNTR_ID
NVARCSTR
10
yes
11
QTY_BACKLOG_SLSU OM
ORDER_FACT.QTY DELIVERY_FACT.QTY_SALES_UNITS DELIVERY_FACT.QTY_SALES_UNITS Actually Delivered Qty
DECIMAL
48
15
yes
12
QTY_DELIV_SLSUOM
DECIMAL
48
15
yes
13
QTY_ORDER_SLSU OM
48
15
yes
14
SALES_DOC_ID
PK
NVARCSTR
10
no
15
NVARCSTR
no
16
SALES_TO_BASE_DIV ISOR
Denominator (divisor) to convert Sales UOM of INTEGER Material into its Base UOM
yes
Appendix Table Column Details SALES_TO_BASE_MU LTIPLR STORAGE_LOCATN_I D Numerator (factor) to convert Sales UOM of Material into its Base UOM
17
INTEGER
yes
18
NVARCSTR
yes
BILLING_BACKLOG_STAGE
Staging table to hold sales orders relative to billing
LOAD_DATE
Date and Time Loaded into Rapid Mart
DATETIME
24
yes
LOAD_TIME
Time Loaded into Rapid Mart
NVARCSTR
yes
QTY_ORDER_SLSU OM
48
15
yes
SALES_DOC_ID
PK
NVARCSTR
10
no
NVARCSTR
no
BILLING_BACKLOG_STAGE_D
Staging table for BACKLOG_FACT in delta load (for changes in Billing Documents)
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
QTY_BILL_SLSUOM
VBRP-FKIMG - Billing Qty in Sales Unit of Meas
DECIMAL
48
13
yes
SALES_DOC_ID
PK
VBRP-AUBEL - Sales Document
NVARCSTR
10
no
VBRP-AUPOS - Sales Document Item
NVARCSTR
no
BILLING_BLOCK
TVFST - Billing Block
BILL_BLOCK_DESCR
TVFST-VTEXT - Description
NVARCSTR
20
yes
BILL_BLOCK_ID
PK
TVFST-FAKSP - Billing block in the document NVARCSTR header
no
LOAD_DATE
Date and time when the record was loaded
DATETIME
24
yes
LOAD_TIME
Time when the record was loaded
NVARCSTR
yes
BILLING_FACT
VBRP,VBRK - Table for Sales Billing Documents including Invoices, Credt Memos, Invoice Cancellations, Debit Memos, Pro Forma Invoices, etc.
AMT_NET_VALUE_GB L AMT_NET_VALUE_HD R_GBL AMT_NET_VALUE_HD R_TRX AMT_NET_VALUE_TR X
VBRP-NETWR - Net Value (Global Currency)
DECIMAL
48
17
yes
Net value in document currency (Global Currency)
DECIMAL
48
15
yes
VBRP-NETWR - Net Value of the billing Item in DECIMAL Document Currency
48
15
yes
Net value in document currency Calcualted field (Global Currency): for sales documents of catetories U or 5 or 6 it is 0, for sales documents of categories N or O it is set to a negative of the net it Calcualted field: for sales documents of catetories U or 5 or 6 it is 0, for sales documents of categories N or O it is set to a negative of the net item value, for ther VBRP-WAVWR - Cost in Global Currency
DECIMAL
48
15
yes
AMT_REVENUE_GBL
DECIMAL
48
15
yes
AMT_REVENUE_TRX
DECIMAL
48
15
yes
AMT_STD_COST_GBL
DECIMAL
48
15
yes
AMT_STD_COST_TRX
VBRP-WAVWR - Cost in Document Currency
DECIMAL
48
13
yes
AMT_SUBTTL_01_GB L AMT_SUBTTL_01_TR X AMT_SUBTTL_02_GB L AMT_SUBTTL_02_TR X AMT_SUBTTL_03_GB L AMT_SUBTTL_03_TR X AMT_SUBTTL_04_GB L AMT_SUBTTL_04_TR X
VBRP-KZWI1 - Customer Configurable Subtotal 1 (Global Currency) VBRP-KZWI1 - Customer-Configurable Subtotal 1 VBRP-KZWI2 - Customer Configurable Subtotal 2 (Global Currency) VBRP-KZWI2 - Customer-Configurable Subtotal 2 VBRP-KZWI3 - Customer Configurable Subtotal (Global Currency) VBRP-KZWI3 - Customer-Configurable Subtotal 3 VBRP-KZWI4 - Customer Configurable Subtotal 4 (Global Currency) VBRP-KZWI4 - Customer-Configurable Subtotal 4
DECIMAL
48
15
yes
10
DECIMAL
48
13
yes
11
DECIMAL
48
15
yes
12
DECIMAL
48
13
yes
13
DECIMAL
48
15
yes
14
DECIMAL
48
13
yes
15
DECIMAL
48
15
yes
16
DECIMAL
48
13
yes
Appendix Table Column Details AMT_SUBTTL_05_GB L AMT_SUBTTL_05_TR X AMT_SUBTTL_06_GB L AMT_SUBTTL_06_TR X VBRP-KZWI5 - Customer Configurable Subtotal 5 (Global Currency) VBRP-KZWI5 - Customer-Configurable Subtotal 5 VBRP-KZWI6 - Customer Configurable Subtotal 6 (Global Currency) VBRP-KZWI6 - Customer-Configurable Subtotal 6
17
DECIMAL
48
15
yes
18
DECIMAL
48
13
yes
19
DECIMAL
48
15
yes
20
DECIMAL
48
13
yes
21
BILL_DATE
PK
VBRK.FKDAT - Billing Date
DATETIME
24
yes
22
BILL_DOC_ID
PK
VBRP-VBELN - Billing Document
NVARCSTR
10
no
23
BILL_DOC_ID_CANCE L
VBRK-SFAKN - Cancelled billing document number
NVARCSTR
10
yes
24
BILL_LINE_ITEM_ID
PK
VBRP-POSNR - Billing Item
NVARCSTR
no
25
BILL_PLAN_ID
VBRP.FPLNR - Billing plan number
NVARCSTR
10
yes
26
CHANGE_DATE
VBRK-AEDAT - Changed On
DATETIME
24
yes
27
CMPNY_CODE_ID
PK
VBRK.BUKRS Company Code
NVARCSTR
yes
28
CREATE_DATE
VBRP-ERDAT - Date on Which the Record Was Created
DATETIME
24
yes
29
CR_CTRL_AREA_ID
PK
VBRK.KKBER - Credit control area
NVARCSTR
yes
30
CTRL_AREA_ID
PK
VBRP.KOKRS Controlling Area
NVARCSTR
yes
31
CURR_ID_GBL
PK
TCURR-FCURR - From currency
NVARCSTR
yes
32
CURR_ID_STATS
VBRK-STWAE - Statistics currency
NVARCSTR
yes
33
CURR_ID_TRX
PK
VBRK-WAERK - Document Currency
NVARCSTR
yes
34
CUSTOMER_GRP_ID
PK
VBRP-KVGR1 - Customer Group 1
NVARCSTR
yes
10
Appendix Table Column Details CUSTOMER_ID_PAYE R CUSTOMER_ID_SOLD PK TO DISTRIBTN_CHANNEL PK _ID
35
VBRK-KUNRG - Payer
NVARCSTR
10
yes
36
VBRK-KUNAG - Sold-to Party
NVARCSTR
10
yes
37
VBRK-VTWEG - Distribution Channel
NVARCSTR
yes
38
DIVISION_ID
PK
VBRP-SPART - Division
NVARCSTR
yes
39
DOC_CANCEL_FLAG
VBRP-SHKZG - Billing document line item is cancelled if set to 1
INTEGER
yes
40
DOC_CATEG_ID
PK
VBRK-VBTYP - SD category
NVARCSTR
yes
41
DOC_CATEG_ID_PRE CDNG
VBRP-VGTYP - Document category of preceding SD document
NVARCSTR
yes
42
DOC_CATEG_ID_REF
VBRP-AUTYP - SD document category
NVARCSTR
yes
43
DOC_TYPE_ID
PK
VBRK-FKART - Billing Type
NVARCSTR
yes
44
EXCH_RATE_ACCT NG
VBRK-KURRF - Exchange Rate for Financial Accounting
DECIMAL
48
20
yes
45
EXCH_RATE_GBL
TCURR-UKURS - Exchange rate
DECIMAL
48
yes
46
EXCH_RATE_STATS
VBRP-STCUR - Exchange rate for statistics (Exch.rate at time of creation)
DECIMAL
48
yes
47
EXCH_TYPE_ID_GBL
PK
TCURR-KURST - Exchange rate type
NVARCSTR
yes
48
FISC_PERIOD
PK
Fiscal Period in SAP
INTEGER
yes
49
FISC_YEAR
PK
Fiscal Year in SAP
INTEGER
yes
50
FISC_YR_VARIANT_ID PK
Fiscal Year Variant in SAP
NVARCSTR
yes
51
FROM_FACTOR_GBL
TCURR-FFACT - Number of Currency for the from currency units
INTEGER
yes
52
INTER_CMPNY_TERM 01_ID
VBRK.INCO1 Incoterms (Part 1)
NVARCSTR
yes
11
53
ITEM_CATEG_ID
SD document item category
NVARCSTR
yes
54
LOAD_DATE
System date of loading
DATETIME
24
yes
55
LOAD_TIME
System time load
NVARCSTR
yes
56
MATERIAL_ID
PK
VBRP-MATNR - Material Number
NVARCSTR
18
yes
57
MTRL_GRP_ID
VBRP.MATKL Material Group
NVARCSTR
yes
58
PAYMNT_TERM_ID
VBRK.ZTERM Terms of payment key
NVARCSTR
yes
59
PLANT_ID
PK
VBRP-WERKS - Plant ID
NVARCSTR
yes
60
PRICE_PROCEDURE_ PK ID PROCESS_STATUS_I PK D
VBRK-KALSM - Pricing procedure for sales and distribution VBUP-GBSTA - Overall Processing Status of the SD item
NVARCSTR
yes
61
NVARCSTR
yes
62
PROD_HIER_ID
VBRP.PRODH Product Hierarchy
NVARCSTR
18
yes
63
PROFIT_CNTR_ID
PK
VBRP.PRCTR Profit center Calculated field as QTY_INVOICED * SLS_TO_BASE_DIVISOR / SLS_TO_BASE_NUMERATOR VBRP-FKLMG - Billing Qty in StockKeeping Unit VBRP-VGBEL - Document number of the reference document
NVARCSTR
10
yes
64
QTY_BILL_SLSUOM
DECIMAL
48
13
yes
65
QTY_BILL_STOCKUO M
DECIMAL
48
13
yes
66
REF_DOC_ID
NVARCSTR
10
yes
67
REF_LINE_ITEM_ID
VBRP-VGPOS - Item number of the reference NVARCSTR item
yes
68
RETURN_FLAG
VBRP-SHKZG - Returns item
NVARCSTR
yes
69
SALES_DOC_ID
VBRP-AUBEL - Sales Document Number
NVARCSTR
10
yes
70
SALES_GRP_ID
PK
VBRP-VKGRP - Sales group
NVARCSTR
yes
12
71
SALES_LINE_ITEM_ID
NVARCSTR
yes
72
SALES_OFFICE_ID
PK
VBRP-VKBUR - Sales Office
NVARCSTR
yes
73
SALES_ORG_ID
PK
VBRK-VKORG - Sales Organization
NVARCSTR
yes
74
SALES_TO_BASE_DIV ISOR SALES_TO_BASE_MU LTIPLR
VBRP-UMVKN - Denominator (divisor) for conversion of sales qty. into SKU VBRP-UMVKZ - Numerator (factor) for conversion of sales quantity into SKU
INTEGER
yes
75
INTEGER
yes
76
SHIP_POINT_ID
VBRP.VSTEL Shipping Point/Receiving Point
NVARCSTR
yes
77
STORAGE_LOCATN_I PK D
VBRP.LGORT Storage location
NVARCSTR
yes
78
TO_FACTOR_GBL
TCURR-TFACT - Number of Currency for the units in the To-currency
INTEGER
yes
79
UOM_ID_BASE
VBRP-MEINS - Base Unit of Measure
NVARCSTR
yes
80
UOM_ID_SALES
PK
VBRP-VRKME - Sales Unit
NVARCSTR
yes
13
BILLING_FACT_BAD
DECIMAL
48
17
yes
DECIMAL
48
15
yes
48
15
yes
DECIMAL
48
15
yes
AMT_REVENUE_GBL
DECIMAL
48
15
yes
AMT_REVENUE_TRX
DECIMAL
48
15
yes
AMT_STD_COST_GBL
DECIMAL
48
15
yes
AMT_STD_COST_TRX
DECIMAL
48
13
yes
DECIMAL
48
15
yes
10
DECIMAL
48
13
yes
11
DECIMAL
48
15
yes
12
DECIMAL
48
13
yes
13
DECIMAL
48
15
yes
14
DECIMAL
48
13
yes
15
DECIMAL
48
15
yes
16
DECIMAL
48
13
yes
14
17
DECIMAL
48
15
yes
18
DECIMAL
48
13
yes
19
DECIMAL
48
15
yes
20
DECIMAL
48
13
yes
21
BILL_DATE
DATETIME
24
yes
22
BILL_DOC_ID
PK
NVARCSTR
10
no
23
BILL_DOC_ID_CANCE L
NVARCSTR
10
yes
24
BILL_LINE_ITEM_ID
PK
NVARCSTR
no
25
BILL_PLAN_ID
NVARCSTR
10
yes
26
CHANGE_DATE
DATETIME
24
yes
27
CMPNY_CODE_ID
NVARCSTR
yes
28
CREATE_DATE
DATETIME
24
yes
29
CR_CTRL_AREA_ID
NVARCSTR
yes
30
CTRL_AREA_ID
NVARCSTR
yes
31
CURR_ID_GBL
NVARCSTR
yes
32
CURR_ID_STATS
NVARCSTR
yes
33
CURR_ID_TRX
NVARCSTR
yes
34
CUSTOMER_GRP_ID
NVARCSTR
yes
15
Appendix Table Column Details CUSTOMER_ID_PAYE R CUSTOMER_ID_SOLD TO DISTRIBTN_CHANNEL _ID
35
VBRK-KUNRG - Payer
NVARCSTR
10
yes
36
NVARCSTR
10
yes
37
NVARCSTR
yes
38
DIVISION_ID
NVARCSTR
yes
39
DOC_CANCEL_FLAG
INTEGER
yes
40
DOC_CATEG_ID
NVARCSTR
yes
41
NVARCSTR
yes
42
DOC_CATEG_ID_REF
NVARCSTR
yes
43
DOC_TYPE_ID
NVARCSTR
yes
44
ETL_ERROR_ACTN
DI Validation transform error action code
NVARCSTR
yes
45
ETL_ERROR_COLU MN EXCH_RATE_ACCT NG
DI Valication transfrom error column name
NVARCSTR
500
yes
46
DECIMAL
48
20
yes
47
EXCH_RATE_GBL
DECIMAL
48
yes
48
EXCH_RATE_STATS
DECIMAL
48
yes
49
EXCH_TYPE_ID_GBL
NVARCSTR
yes
50
FISC_PERIOD
INTEGER
yes
51
FISC_YEAR
Fiscal Year in SAP
INTEGER
yes
52
FISC_YR_VARIANT_ID
NVARCSTR
yes
16
Appendix Table Column Details TCURR-FFACT - Number of Currency for the from currency units
53
FROM_FACTOR_GBL
INTEGER
yes
54
NVARCSTR
yes
55
ITEM_CATEG_ID
NVARCSTR
yes
56
LOAD_DATE
PK
DATETIME
24
no
57
LOAD_TIME
System time load
NVARCSTR
yes
58
MATERIAL_ID
NVARCSTR
18
yes
59
MTRL_GRP_ID
NVARCSTR
yes
60
PAYMNT_TERM_ID
NVARCSTR
yes
61
PLANT_ID
NVARCSTR
yes
62
PRICE_PROCEDURE_ ID PROCESS_STATUS_I D
NVARCSTR
yes
63
NVARCSTR
yes
64
PROD_HIER_ID
NVARCSTR
18
yes
65
PROFIT_CNTR_ID
NVARCSTR
10
yes
66
QTY_BILL_SLSUOM
DECIMAL
48
13
yes
67
QTY_BILL_STOCKUO M
DECIMAL
48
13
yes
68
REF_DOC_ID
NVARCSTR
10
yes
69
REF_LINE_ITEM_ID
yes
70
RETURN_FLAG
NVARCSTR
yes
17
71
SALES_DOC_ID
NVARCSTR
10
yes
72
SALES_GRP_ID
NVARCSTR
yes
73
SALES_LINE_ITEM_ID
NVARCSTR
yes
74
SALES_OFFICE_ID
NVARCSTR
yes
75
SALES_ORG_ID
NVARCSTR
yes
76
INTEGER
yes
77
INTEGER
yes
78
SHIP_POINT_ID
NVARCSTR
yes
79
STORAGE_LOCATN_I D
NVARCSTR
yes
80
TO_FACTOR_GBL
INTEGER
yes
81
UOM_ID_BASE
NVARCSTR
yes
82
UOM_ID_SALES
NVARCSTR
yes
18
BILLING_STAGE
DECIMAL
48
17
yes
DECIMAL
48
15
yes
48
15
yes
DECIMAL
48
15
yes
AMT_REVENUE_GBL
DECIMAL
48
15
yes
AMT_REVENUE_TRX
DECIMAL
48
15
yes
AMT_STD_COST_GBL
DECIMAL
48
15
yes
AMT_STD_COST_TRX
DECIMAL
48
13
yes
DECIMAL
48
15
yes
10
DECIMAL
48
13
yes
11
DECIMAL
48
15
yes
12
DECIMAL
48
13
yes
13
DECIMAL
48
15
yes
14
DECIMAL
48
13
yes
15
DECIMAL
48
15
yes
16
DECIMAL
48
13
yes
19
17
DECIMAL
48
15
yes
18
DECIMAL
48
13
yes
19
DECIMAL
48
15
yes
20
DECIMAL
48
13
yes
21
BILL_DATE
DATETIME
24
yes
22
BILL_DOC_ID
PK
NVARCSTR
10
no
23
BILL_DOC_ID_CANCE L
NVARCSTR
10
yes
24
BILL_LINE_ITEM_ID
PK
NVARCSTR
no
25
BILL_PLAN_ID
NVARCSTR
10
yes
26
CHANGE_DATE
DATETIME
24
yes
27
CMPNY_CODE_ID
NVARCSTR
yes
28
CREATE_DATE
DATETIME
24
yes
29
CR_CTRL_AREA_ID
NVARCSTR
yes
30
CTRL_AREA_ID
NVARCSTR
yes
31
CURR_ID_GBL
NVARCSTR
yes
32
CURR_ID_STATS
NVARCSTR
yes
33
CURR_ID_TRX
NVARCSTR
yes
34
CUSTOMER_GRP_ID
NVARCSTR
yes
20
Appendix Table Column Details CUSTOMER_ID_PAYE R CUSTOMER_ID_SOLD TO DISTRIBTN_CHANNEL _ID
35
VBRK-KUNRG - Payer
NVARCSTR
10
yes
36
NVARCSTR
10
yes
37
NVARCSTR
yes
38
DIVISION_ID
NVARCSTR
yes
39
DOC_CANCEL_FLAG
INTEGER
yes
40
DOC_CATEG_ID
NVARCSTR
yes
41
NVARCSTR
yes
42
DOC_CATEG_ID_REF
NVARCSTR
yes
43
DOC_TYPE_ID
NVARCSTR
yes
44
EXCH_RATE_ACCT NG
DECIMAL
48
20
yes
45
EXCH_RATE_GBL
DECIMAL
48
yes
46
EXCH_RATE_STATS
DECIMAL
48
yes
47
EXCH_TYPE_ID_GBL
NVARCSTR
yes
48
FISC_PERIOD
INTEGER
yes
49
FISC_YEAR
Fiscal Year in SAP
INTEGER
yes
50
FISC_YR_VARIANT_ID
Fiscal Year Variant ID in SAP
NVARCSTR
yes
51
FROM_FACTOR_GBL
TCURR-FFACT - Number of Currency for the from currency units
INTEGER
yes
52
NVARCSTR
yes
21
53
ITEM_CATEG_ID
NVARCSTR
yes
54
LOAD_DATE
DATETIME
24
yes
55
LOAD_TIME
System time load
NVARCSTR
yes
56
MATERIAL_ID
NVARCSTR
18
yes
57
MTRL_GRP_ID
NVARCSTR
yes
58
PAYMNT_TERM_ID
NVARCSTR
yes
59
PLANT_ID
NVARCSTR
yes
60
NVARCSTR
yes
61
NVARCSTR
yes
62
PROD_HIER_ID
NVARCSTR
18
yes
63
PROFIT_CNTR_ID
NVARCSTR
10
yes
64
QTY_BILL_SLSUOM
DECIMAL
48
13
yes
65
QTY_BILL_STOCKUO M
DECIMAL
48
13
yes
66
REF_DOC_ID
NVARCSTR
10
yes
67
REF_LINE_ITEM_ID
yes
68
RETURN_FLAG
NVARCSTR
yes
69
SALES_DOC_ID
NVARCSTR
10
yes
70
SALES_GRP_ID
NVARCSTR
yes
22
71
SALES_LINE_ITEM_ID
NVARCSTR
yes
72
SALES_OFFICE_ID
NVARCSTR
yes
73
SALES_ORG_ID
NVARCSTR
yes
74
INTEGER
yes
75
INTEGER
yes
76
SHIP_POINT_ID
NVARCSTR
yes
77
STORAGE_LOCATN_I D
NVARCSTR
yes
78
TO_FACTOR_GBL
INTEGER
yes
79
UOM_ID_BASE
NVARCSTR
yes
80
UOM_ID_SALES
NVARCSTR
yes
23
CENTRAL_ADDRESS
Sourced from table ADRC in SAP, Only Ship-to addresses for Sales orders are included
ADDRESS_ID
PK
Address number
NVARCSTR
10
no
CITY
City
NVARCSTR
40
yes
COUNTRY_ID
Country key
NVARCSTR
yes
COUNTRY_NAME
T005T.LANDX - Country Name
NVARCSTR
20
yes
CUSTOMER_NAME_ 01 CUSTOMER_NAME_ 02 CUSTOMER_NAME_ 03 CUSTOMER_NAME_ 04
Name 1
NVARCSTR
40
yes
Name 2
NVARCSTR
40
yes
Name 3
NVARCSTR
40
yes
Name 4
NVARCSTR
40
yes
DISTRICT
District
NVARCSTR
40
yes
10
FAX
First fax no.: dialling code+number
NVARCSTR
30
yes
11
HOUSE_NUMBER
House number
NVARCSTR
10
yes
12
LOAD_DATE
DATETIME
24
yes
13
LOAD_TIME
NVARCSTR
yes
14
PHONE
First telephone no.: dialling code+number
NVARCSTR
30
yes
15
REGION_ID
Region (State, Province, County)
NVARCSTR
yes
16
REGION_NAME
T005U.BEZEI - Region Name (State, Province, NVARCSTR etc.)
20
yes
24
17
STREET
Street
NVARCSTR
60
yes
18
ZIP
City postal code
NVARCSTR
10
yes
25
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
26
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
27
35
ZIP
Company code postal code
NVARCSTR
10
yes
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
28
CREDIT_CONTROL_AREA
T014T - Credit Control Area Names
CR_CTRL_AREA_DES CR CR_CTRL_AREA_FUL L_NAME
T014T.KKBTX - Description of the credit control area Concatenation of Credit Ctrl Area ID and Description
NVARCSTR
35
yes
NVARCSTR
120
yes
CR_CTRL_AREA_ID
PK
T014T.KKBER - Credit control area
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
CREDIT_MGMT_RISK_CLASS
T691T - Credit management risk classes text
CR_CTRL_AREA_ID
PK
Credit Control Area ID
NVARCSTR
no
CR_MGMT_RISK_CLA SS_DESCR CR_MGMT_RISK_CLA PK SS_ID
Name of the risk class
NVARCSTR
30
yes
Credit management: Risk Class
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
29
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
30
CURRENCY_CONVERT_RATE
TCURR and TCURW - Monetary Conversion rates
CURR_ID_FROM
PK
NVARCSTR
no
CURR_ID_TO
PK
TCURR-TCURR - To-currency
NVARCSTR
no
EXCH_RATE
DECIMAL
48
yes
EXCH_TYPE_DESCR
TCURW-CURVW - Exchange rate type usage
NVARCSTR
40
yes
EXCH_TYPE_ID
PK
NVARCSTR
no
FROM_FACTOR
TCURR-FFACT - Number of Currency for the from currency units "Y" if original value of TCURR.UKURS was negative. Otherwise "N"
INTEGER
yes
INVERSE_RATE_FLA G
NVARCSTR
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
Time in HH24:MI:SS string format when the record was created TCURR-TFACT - Number of Currency for the units in the To-currency TCURR-GDATU- Date since when the exchange rate has been valid To be used by Effective Date to generate VALID_TO output
NVARCSTR
yes
10
TO_FACTOR
INTEGER
yes
11
VALID_FROM_DATE
PK
DATETIME
24
no
12
VALID_TO_DATE
DATETIME
24
yes
31
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
32
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
33
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
CUSTOMER_GROUP
TVV1T - Customer Group
CUSTOMER_GRP_D ESCR
TVV1T-BEZEI - Description
NVARCSTR
60
yes
CUSTOMER_GRP_ID
PK
TVV1T-KVGR1 - Customer Group 1
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
34
DELIVERY_BACKLOG_STAGE_D
New or Deleted Deliveries for a Given Period. NOTE: TABLE MUST NOT HAVE A PRIMARY KEY!!!!!
DELIV_ID
NVARCSTR
10
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_DOC_ID
LIPS-VGBEL - Document Number of the Reference Document
NVARCSTR
10
no
DELIVERY_BLOCK
TVLST - Delivery Block
DELIV_BLOCK_DESC R
TVLST-VTEXT - Delivery Block Description
NVARCSTR
20
yes
DELIV_BLOCK_ID
PK
TVLST-LIFSP - Delivery block ID
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
35
DELIVERY_FACT
LIPS, LIKP - Delivery records for Sales Documents
ACTL_GI_DATE
PK
LIKP.WADAT_IST - Actual Goods Issue Date
DATETIME
24
yes
AMT_STD_COST_TRX
LIPS-WAVWR - Cost in Document Currency
DECIMAL
48
15
yes
AMT_SUBTTL_01_TR X AMT_SUBTTL_02_TR X AMT_SUBTTL_03_TR X AMT_SUBTTL_04_TR X AMT_SUBTTL_05_TR X AMT_SUBTTL_06_TR X
LIPS-KZWI1 - Customer-Cofigurable Subtotal 1 DECIMAL
48
15
yes
48
15
yes
48
15
yes
48
15
yes
48
15
yes
48
15
yes
BILL_BLOCK_ID
PK
TVFST-FAKSP - Billing block ID
NVARCSTR
yes
10
BILL_STATUS_DELIV_ RELTD_ID
VBUP-FKSTA - Billing Status of Delivery-Related Billing Documents
NVARCSTR
yes
11
CHANGE_DATE
LIPS-AEDAT - Changed On - Line Item Level
DATETIME
24
yes
12
CMPNY_CODE_ID
PK
LIKP.BUKRS --Company code
NVARCSTR
yes
13
CREATE_DATE
LIPS-ERDAT - Date on Which the Delivery Line Item was Created
DATETIME
24
yes
14
CREATE_DATE_HDR
PK
LIKP.ERDAT - Date Delivery Created
DATETIME
24
yes
15
CR_CTRL_AREA_ID
PK
NVARCSTR
yes
16
CR_MGMT_RISK_CLA PK SS_ID
NVARCSTR
yes
36
17
CTRL_AREA_ID
PK
LIPS-KOKRS-Controlling area
NVARCSTR
yes
18
CURR_ID_STATS
LIKP-STWAE - Statistics currency
NVARCSTR
yes
19
CURR_ID_TRX
PK
LIKP-WAERK - Document Currency
NVARCSTR
yes
20
CUSTOMER_GRP_ID
PK
LIPS-KVGR1 - Customer Group 1
NVARCSTR
yes
21
CUSTOMER_ID_SHIP TO CUSTOMER_ID_SOLD TO DAYS_FIXED_PROCE SS DAYS_SHIP_PROCES S
LIKP-KUNNR - Ship-to Party
NVARCSTR
10
yes
22
LIKP-KUNAG - Sold-to Party
NVARCSTR
10
yes
23
LIPS-VBEAF - Fixed Shipping Processing Time DECIMAL in Days (= setup time) LIPS-VBEAV - Variable Shipping Processing Time in Days
48
yes
24
DECIMAL
48
yes
25
DELIV_BLOCK_ID
PK
TVLST-LIFSP - Delivery Block ID
NVARCSTR
yes
26
DELIV_DATE
LIKP-LFDAT - Delivery Date
DATETIME
24
yes
27
DELIV_ID
PK
NVARCSTR
10
no
28
NVARCSTR
no
29
DELIV_LOAD_DATE
LIKP-LDDAT - Loading Date
DATETIME
24
yes
30
DELIV_PRIORITY_ID
PK
TPRIT-LPRIO - Delivery Priority ID
NVARCSTR
yes
31
DELIV_ROUTE_ID
LIKP.ROUTE - Delivery Route
NVARCSTR
yes
32
DELIV_STATUS_KEY
PK
Concatenated values of Sales Document Status fields
NVARCSTR
36
yes
33
DISTRIBTN_CHANNEL PK _ID
LIPS-VTWEG - Distribution Channel
NVARCSTR
yes
34
DIVISION_ID
PK
LIPS-SPART - Division
NVARCSTR
yes
37
35
DOC_CATEG_ID
PK
LIKP-VBTYP - SD Document Category
NVARCSTR
yes
36
DOC_CATEG_ID_REF
LIPS -VBTYP - Reference Document Category NVARCSTR (Sales Order)
yes
37
DOC_TYPE_ID
PK
LIKP-LFART - Delivery Type
NVARCSTR
yes
38
EXCH_RATE_STATS
LIKP-STCUR - Exchange Rate for Statistics
DECIMAL
48
20
yes
39
GI_STATUS_ID
PK
VBUP-WBSTA - Goods Issue status (indicates NVARCSTR whether goods have left the warehouse)
yes
40
LIPS.INCO1 Incoterms (Part 1)
NVARCSTR
yes
41
LOAD_DATE
DATETIME
24
yes
42
LOAD_TIME
NVARCSTR
yes
43
MATERIAL_ID
PK
LIPS-MATNR - Material Number
NVARCSTR
18
yes
44
MTRL_AVAIL_DATE
LIPS-MBDAT - Material Availability Date
DATETIME
24
yes
45
MTRL_GRP_ID
LIPS.MATKL Material Group
NVARCSTR
yes
46
PACKNG_STATUS_ID
Packing status
NVARCSTR
10
yes
47
PARTIAL_DELIV_ID
LIPS-KZTLF - Partial delivery at item level
NVARCSTR
yes
48
PICKNG_CONFIRM_S TATUS_ID
VBUP.KOQUA - Picking confirmation status
NVARCSTR
yes
49
PICKNG_DATE
LIKP-KODAT - Picking Date
DATETIME
24
yes
50
PICKNG_STATUS_ID
VBUP-KOSTA - Picking Status
NVARCSTR
yes
51
PLANT_ID
PK
LIPS.WERKS Plant
NVARCSTR
yes
52
PLAN_GI_DATE
LIKP-WADAT - Planned Goods Issue Date
DATETIME
24
yes
38
Appendix Table Column Details PRICE_PROCEDURE_ PK ID PROCESS_STATUS_I D
53
T683S-KALSM - Pricing Procedure
NVARCSTR
yes
54
VBUP-GBSTA - Overall processing status of the SD document item
NVARCSTR
yes
55
PROD_HIER_ID
LIPS.PRODH Product Hierarchy
NVARCSTR
18
yes
56
PROFIT_CNTR_ID
PK
LIPS.PRCTR - Profit center
NVARCSTR
10
yes
57
QTY_DELIV_BASEUO M
LIPS-LGMNG - Actual Quantity Delivered (in Base Units) LIPS-LFIMG - Actual Quantity Delivered (in Sales Units)
DECIMAL
48
13
yes
58
QTY_DELIV_SLSUOM
DECIMAL
48
13
yes
59
QTY_GROSS_WEIG HT
LIPS-BRGEW - Gross weight
DECIMAL
48
15
yes
60
QTY_NET_WEIGHT
LIPS-NTGEW - Net weight
DECIMAL
48
15
yes
61
QTY_VOLUME
LIPS-VOLUM - Volume
DECIMAL
48
15
yes
62
RETURN_FLAG
LIPS-SHKZG - Debit/credit indicator
NVARCSTR
yes
63
SALES_DOC_ID
LIPS-VGBEL - Document Number of the Reference Document
NVARCSTR
10
yes
64
SALES_GRP_ID
PK
LIPS-VKGRP - Sales Group
NVARCSTR
yes
65
SALES_LINE_ITEM_ID
LIPS-VGPOS - Item Number of the Reference Item
NVARCSTR
yes
66
SALES_OFFICE_ID
PK
LIPS-VKBUR - Sales Office
NVARCSTR
yes
67
SALES_ORG_ID
PK
LIKP-VKORG - Sales Organization
NVARCSTR
yes
68
SHIP_POINT_ID
LIKP.VSTEL Shipping Point/Receiving Point
NVARCSTR
yes
69
STORAGE_LOCATN_I PK D
LIPS.LGORT Storage location
NVARCSTR
yes
70
UOM_ID_BASE
LIPS-MEINS - Base Unit of Measure
NVARCSTR
yes
39
71
UOM_ID_SALES
PK
LIPS.VRKME - Sales Unit of Meas.
NVARCSTR
yes
72
UOM_ID_VOLUME
LIPS-VOLEH - Volume unit
NVARCSTR
yes
73
UOM_ID_WEIGHT
LIPS-GEWEI - Unit of weight
NVARCSTR
yes
DELIVERY_PRIORITY
TPRIT - Delivery Priority
DELIV_PRIORITY_DE SCR
TPRIT-BEZEI - Delivery Priority description
NVARCSTR
20
yes
DELIV_PRIORITY_ID
PK
TPRIT-LPRIO - Delivery Priority ID
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
DELIVERY_ROUTE
TVROT - Delivery Route
DELIV_ROUTE_DESC R
TVROT.BEZEI - Delivery Route Descr.
NVARCSTR
40
yes
DELIV_ROUTE_ID
PK
TVROT.ROUTE Delivery Route ID
NVARCSTR
no
LOAD_DATE
Data and Time Loaded into Rapid Mart
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
40
DELIVERY_STATUS
Delivery Document Statuses code combinations
BILL_STATUS_DESCR
Lookup on Delivery Document Status dimension for the status descritpion VBUP-FKSTA - Billing Status of Delivery-Related Billing Documents Concatenated values of Sales Document Status fields Lookup on Delivery Document Status dimension for the status descritpion
NVARCSTR
60
yes
BILL_STATUS_ID
NVARCSTR
yes
DELIV_STATUS_KEY
PK
NVARCSTR
36
no
GI_STATUS_DESCR
NVARCSTR
60
yes
GI_STATUS_ID
VBUP-WBSTA - Goods Issue status (indicates NVARCSTR whether goods have left the warehouse)
yes
LOAD_DATE
System date and time of loading
DATETIME
24
yes
LOAD_TIME
Time in string format when the record was loaded Lookup on Delivery Document Status dimension for the status descritpion
NVARCSTR
yes
PACKNG_STATUS_DE SCR
NVARCSTR
60
yes
PACKNG_STATUS_ID
VBUP-PKSTA - Packing status of item
NVARCSTR
yes
10
PICKNG_CONFIRM_S TATUS_DESCR PICKNG_CONFIRM_S TATUS_ID PICKNG_STATUS_DE SCR
Lookup on Delivery Document Status dimension for the status descritpion
NVARCSTR
60
yes
11
NVARCSTR
yes
12
Lookup on Delivery Document Status dimension for the status descritpion
NVARCSTR
60
yes
13
PICKNG_STATUS_ID
VBUP-KOSTA - Picking status
NVARCSTR
yes
14
PROCESS_STATUS_D ESCR PROCESS_STATUS_I D
Lookup on Delivery Document Status dimension for the status descritpion VBUP-GBSTA - Overall Processing Status fo the SD item
NVARCSTR
60
yes
15
NVARCSTR
yes
41
DISTRIBUTION_CHANNEL
TVTWT - Distribution Channel
DISTRIBTN_CHANNEL _DESCR DISTRIBTN_CHANNEL PK _ID
TVTWT-VTEXT - Name
NVARCSTR
40
yes
TVTW-VTWEG - Distribution Channel
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
DIVISION
TSPAT - Division
DIVISION_DESCR
TSPAT-VTEXT - Name
NVARCSTR
40
yes
DIVISION_ID
PK
TSPAT-SPART - Properties
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
42
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
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
Date and time loaded into Rapid Mart
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
43
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
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
44
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
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
45
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
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
GLOBAL_CURRENCY
Global Currency from $G_GLOBAL_CURRENCY
CURR_ID_GBL
PK
Global Currenncy ID from Global Variable $G_GLOBAL_CURRENCY Global Currency Exchange Type ID from Global Variable $G_EXCHANGE_TYPE_ID
NVARCSTR
no
EXCH_TYPE_ID_GBL
NVARCSTR
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
46
INTER_COMPANY_TERM01
TINCT - Inter Company Terms01
INTER_CMPNY_TERM PK 01_ID INTER_CMPNY_TERM 01_NAME
TINCT.INCO1 - IncoTerms (part 1) ID
NVARCSTR
no
TINCT.BEZEI - IncoTerms (part 1) Description NVARCSTR
30
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
47
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
48
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
49
35
VOLUME
MARA.VOLUM Volume
DECIMAL
48
13
yes
36
WEIGHT
MARA.NTGEW Net weight
DECIMAL
48
13
yes
MATERIAL_ALT_UOM
MARM - Material Alt Uom
ALT_TO_BASE_DIVIS OR ALT_TO_BASE_MULTI PLR
MARM-UMREN - Denominator for conversion INTEGER from alternative to base units of measure MARM-UMREZ - Numerator for converting from alternative to base unit of measure
yes
INTEGER
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MATERIAL_ID
PK
MARM-MATNR - Material number
NVARCSTR
18
no
UOM_ID_ALT
PK
MARM-MEINH - Alternative unit of measure for stockkeeping unit
NVARCSTR
no
UOM_ID_BASE
MARA-MEINS - Material Base Unit of Measure NVARCSTR
yes
50
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
51
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
52
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
53
53
UOM_ID_PROD
MARC.FRTME Production unit of measure
NVARCSTR
yes
MATERIAL_GROUP
T023T - Material Group
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MTRL_GRP_DESCR
Material Group Description
NVARCSTR
20
yes
MTRL_GRP_ID
PK
Material Group ID
NVARCSTR
no
54
ONTIME_DELIVERY_FACT
Current Snapshot of ONTIME_DELIVERY_FACT
ACTL_GI_DATE
PK
DATETIME
24
yes
AMT_NET_PRICE_GB L AMT_NET_PRICE_TR X CHANGE_STATUS_FL AG
VBAP-NETPR - Net Price
DECIMAL
48
11
yes
DECIMAL
48
11
yes
Is this a New, Changed, or Deleted Record?
NVARCSTR
10
yes
CITY_SHIPTO
City
NVARCSTR
40
yes
COUNTRY_ID_SHIPT O COUNTRY_NAME_SHI PTO
Country ID
NVARCSTR
yes
Country Name
NVARCSTR
20
yes
CURR_ID_GBL
PK
Global currency code
NVARCSTR
yes
CURR_ID_TRX
PK
Sales order currency code (document)
NVARCSTR
yes
10
CUSTOMER_ID_SHIP TO
VBPA-KUNNR - Customer Number (lookup)
NVARCSTR
10
yes
11
CUSTOMER_PO_NUM
VBAK-BSTNK - Customer purchase order number
NVARCSTR
20
yes
12
DAYS_EARLY_LATE
Difference between Sched. Goods Issue Date and Actual Goods Issue Date. A positive number indicates an early delivery. A negative INTEGER number indicates a late delivery. PK VBEP-LIFSP - Delivery block (Sched. Line) NVARCSTR
yes
13
DELIV_BLOCK_ID
yes
14
DELIV_BLOCK_ID_HD R
VBAK-LIFSK - Delivery block (document header)
NVARCSTR
yes
15
DELIV_ID
PK
NVARCSTR
10
no
16
NVARCSTR
no
55
17
DELIV_STATUS_FLAG
Is this Delivery On Time, Early, or Late?
NVARCSTR
10
yes
18
VBAK-VTWEG - Distribution Channel
NVARCSTR
yes
19
DISTRICT_SHIPTO
District
NVARCSTR
40
yes
20
DIVISION_ID
VBAK-SPART - Division
NVARCSTR
yes
21
HOUSE_NUM_SHIPTO
House number
NVARCSTR
10
yes
22
VBKD.INCO1 - IncoTerms Part 1
NVARCSTR
yes
23
NVARCSTR
28
yes
24
LOAD_DATE
Date and Time Extracted from SAP
DATETIME
24
yes
25
LOAD_TIME
Time when the record was loaded into the target database
NVARCSTR
yes
26
MATERIAL_ID
PK
VBAP-MATNR - Material Number
NVARCSTR
18
yes
27
NAME_01_SHIPTO
Name 1
NVARCSTR
40
yes
28
NAME_02_SHIPTO
Name 2
NVARCSTR
40
yes
29
NAME_03_SHIPTO
Name 3
NVARCSTR
40
yes
30
NAME_04_SHIPTO
Name 4
NVARCSTR
40
yes
31
PHONE_SHIPTO
NVARCSTR
30
yes
32
PLANT_ID
PK
VBAP-WERKS -- Plant
NVARCSTR
yes
33
PROD_HIER_ID
VBAP.PRODH Product Hierarchy
NVARCSTR
18
yes
34
QTY_ALLOCTN_SLSU OM
Sched Line Qty allocated to the Delivery
DECIMAL
48
13
yes
56
Appendix Table Column Details LIPS-LFIMG - Actual Qties Delivered (in Sales DECIMAL Units) VBAP- KWMENG - Cumulative Order Quantity DECIMAL in Sales Units
35
QTY_DELIV_SLSUOM
48
13
yes
36
QTY_ORDER_SLSU OM QTY_SCHED_CONFIR M_SLSUOM
48
15
yes
37
Schdeule line confirmed quantity
DECIMAL
48
13
yes
38
REGION_ID_SHIPTO
Region (State, Province, County) ID
NVARCSTR
yes
39
REGION_NAME_SHIP TO
Region (State, Province, County) Name
NVARCSTR
20
yes
40
SALES_DOC_ID
PK
Sales Order Number
NVARCSTR
10
no
41
Sales Order Item number
NVARCSTR
no
42
SALES_OFFICE_ID
PK
VBAK-VKBUR - Sales office
NVARCSTR
yes
43
SALES_ORG_ID
PK
VBAK-VKORG - Sales Organization
NVARCSTR
yes
44
SALES_PERSON_ID
PK
VBPA-PERNR - Sales person ID
NVARCSTR
yes
45
SCHED_GI_DATE
Schedule line goods issue date
DATETIME
24
yes
46
SCHED_LINE_ITEM_I D
PK
Schedule line number
NVARCSTR
no
47
STREET_SHIPTO
Street
NVARCSTR
60
yes
48
ZIP_SHIPTO
City Postal Code
NVARCSTR
10
yes
57
ONTIME_DELIVERY_HISTORY
History table for On Time Delivery - Contains Previous snapshots
ACTL_GI_DATE
PK
DATETIME
24
yes
DECIMAL
48
11
yes
DECIMAL
48
11
yes
NVARCSTR
10
yes
CITY_SHIPTO
City
NVARCSTR
40
yes
Country ID
NVARCSTR
yes
Country Name
NVARCSTR
20
yes
CURR_ID_GBL
PK
NVARCSTR
yes
CURR_ID_TRX
PK
NVARCSTR
yes
10
CUSTOMER_ID_SHIP TO
NVARCSTR
10
yes
11
CUSTOMER_PO_NUM
NVARCSTR
20
yes
12
DAYS_EARLY_LATE
Difference between Sched. Goods Issue Date and Actual Goods Issue Date. A positive number indicates an early delivery. A negative INTEGER number indicates a late delivery. PK VBEP-LIFSP - Delivery block (Sched. Line) NVARCSTR
yes
13
DELIV_BLOCK_ID
yes
14
DELIV_BLOCK_ID_HD R
NVARCSTR
yes
15
DELIV_ID
PK
NVARCSTR
10
no
16
NVARCSTR
no
58
17
DELIV_STATUS_FLAG
NVARCSTR
10
yes
18
DISTRIBTN_CHANNEL _ID
NVARCSTR
yes
19
DISTRICT_SHIPTO
District
NVARCSTR
40
yes
20
DIVISION_ID
NVARCSTR
yes
21
HOUSE_NUM_SHIPTO
House number
NVARCSTR
10
yes
22
NVARCSTR
yes
23
NVARCSTR
28
yes
24
LOAD_DATE
PK
DATETIME
24
no
25
LOAD_TIME
NVARCSTR
yes
26
MATERIAL_ID
PK
NVARCSTR
18
yes
27
NAME_01_SHIPTO
Name 1
NVARCSTR
40
yes
28
NAME_02_SHIPTO
Name 2
NVARCSTR
40
yes
29
NAME_03_SHIPTO
Name 3
NVARCSTR
40
yes
30
NAME_04_SHIPTO
Name 4
NVARCSTR
40
yes
31
PHONE_SHIPTO
NVARCSTR
30
yes
32
PLANT_ID
PK
VBAP-WERKS -- Plant
NVARCSTR
yes
33
PROD_HIER_ID
NVARCSTR
18
yes
34
QTY_ALLOCTN_SLSU OM
DECIMAL
48
13
yes
59
35
QTY_DELIV_SLSUOM
48
13
yes
36
48
15
yes
37
DECIMAL
48
13
yes
38
REGION_ID_SHIPTO
NVARCSTR
yes
39
REGION_NAME_SHIP TO
NVARCSTR
20
yes
40
SALES_DOC_ID
PK
Sales Order Number
NVARCSTR
10
no
41
NVARCSTR
no
42
SALES_OFFICE_ID
PK
NVARCSTR
yes
43
SALES_ORG_ID
PK
NVARCSTR
yes
44
SALES_PERSON_ID
PK
NVARCSTR
yes
45
SCHED_GI_DATE
DATETIME
24
yes
46
SCHED_LINE_ITEM_I D
PK
NVARCSTR
no
47
STREET_SHIPTO
Street
NVARCSTR
60
yes
48
ZIP_SHIPTO
City Postal Code
NVARCSTR
10
yes
60
ONTIME_DELIVERY_STAGE
Staging table to assist loading ONTIME_DELIVERY_FACT and History tables
ACTL_GI_DATE
DATETIME
24
yes
DECIMAL
48
11
yes
DECIMAL
48
11
yes
NVARCSTR
10
yes
CITY_SHIPTO
City
NVARCSTR
40
yes
Country ID
NVARCSTR
yes
Country Name
NVARCSTR
20
yes
CURR_ID_GBL
NVARCSTR
yes
CURR_ID_TRX
NVARCSTR
yes
10
CUSTOMER_ID_SHIP TO
NVARCSTR
10
yes
11
CUSTOMER_PO_NUM
NVARCSTR
20
yes
12
DAYS_EARLY_LATE
Difference between Sched. Goods Issue Date and Actual Goods Issue Date. A positive number indicates an early delivery. A negative INTEGER number indicates a late delivery. VBEP-LIFSP - Delivery block (Sched. Line) NVARCSTR
yes
13
DELIV_BLOCK_ID
yes
14
DELIV_BLOCK_ID_HD R
NVARCSTR
yes
15
DELIV_ID
PK
NVARCSTR
10
no
16
NVARCSTR
no
61
17
DELIV_STATUS_FLAG
NVARCSTR
10
yes
18
DISTRIBTN_CHANNEL _ID
NVARCSTR
yes
19
DISTRICT_SHIPTO
District
NVARCSTR
40
yes
20
DIVISION_ID
NVARCSTR
yes
21
HOUSE_NUM_SHIPTO
House number
NVARCSTR
10
yes
22
INTER_CMPNY_TERM 01_ID INTER_CMPNY_TERM 02_NAME
NVARCSTR
yes
23
NVARCSTR
28
yes
24
LOAD_DATE
DATETIME
24
yes
25
LOAD_TIME
NVARCSTR
yes
26
MATERIAL_ID
NVARCSTR
18
yes
27
NAME_01_SHIPTO
Name 1
NVARCSTR
40
yes
28
NAME_02_SHIPTO
Name 2
NVARCSTR
40
yes
29
NAME_03_SHIPTO
Name 3
NVARCSTR
40
yes
30
NAME_04_SHIPTO
Name 4
NVARCSTR
40
yes
31
PHONE_SHIPTO
NVARCSTR
30
yes
32
PLANT_ID
VBAP-WERKS -- Plant
NVARCSTR
yes
33
PROD_HIER_ID
NVARCSTR
18
yes
34
QTY_ALLOCTN_SLSU OM
DECIMAL
48
13
yes
62
35
QTY_DELIV_SLSUOM
48
13
yes
36
48
15
yes
37
DECIMAL
48
13
yes
38
REGION_ID_SHIPTO
NVARCSTR
yes
39
REGION_NAME_SHIP TO
NVARCSTR
20
yes
40
SALES_DOC_ID
PK
Sales Order Number
NVARCSTR
10
no
41
NVARCSTR
no
42
SALES_OFFICE_ID
NVARCSTR
yes
43
SALES_ORG_ID
NVARCSTR
yes
44
SALES_PERSON_ID
NVARCSTR
yes
45
SCHED_GI_DATE
DATETIME
24
yes
46
SCHED_LINE_ITEM_I D
PK
NVARCSTR
no
47
STREET_SHIPTO
Street
NVARCSTR
60
yes
48
ZIP_SHIPTO
City Postal Code
NVARCSTR
10
yes
63
ORDER_REASON
TVAUT - Order Reason
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
ORDER_REASON_D ESCR
TVAUT-BEZEI - Description
NVARCSTR
40
yes
ORDER_REASON_ID
PK
TVAUT-AUGRU - Order reason (reason for the business transaction)
NVARCSTR
no
PAYMENT_TERM
Table of explanations of payment term keys
LOAD_DATE
24
yes
LOAD_TIME
NVARCSTR
yes
PAYMNT_TERM_DA Y_LIMIT PAYMNT_TERM_DE SCR
PK
Day limit
NVARCSTR
no
Description of payment terms
NVARCSTR
50
yes
PAYMNT_TERM_ID
PK
Payment terms key
NVARCSTR
no
64
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
65
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
66
PRICING_PROCEDURE_HZ
T683S,T683U,T683T - Pricing Procedure and Subtotal Descriptions Horizontal
APPLICTN_ID
PK
T683S-KAPPL - Application
NVARCSTR
no
CONDITN_SEQ_ID
T683S.ZAEHK Condition counter
NVARCSTR
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
PRICE_PROCEDURE_ DESCR PRICE_PROCEDURE_ PK ID
T683U-VTEXT - Description
NVARCSTR
30
yes
NVARCSTR
no
STEP_NUM
T683S.ZAEHK Condition counter
NVARCSTR
yes
SUBTTL_01_DESCR
T683T.VTEXT - Subtotal Description 1
NVARCSTR
30
yes
SUBTTL_02_DESCR
NVARCSTR
30
yes
10
SUBTTL_03_DESCR
NVARCSTR
30
yes
11
SUBTTL_04_DESCR
NVARCSTR
30
yes
12
SUBTTL_05_DESCR
NVARCSTR
30
yes
13
SUBTTL_06_DESCR
NVARCSTR
30
yes
14
USAGE_ID
PK
T683S-KVEWE - Usage of the Condition Table NVARCSTR
no
67
PRICING_PROCEDURE_VR
T683S,T683U,T683T - Pricing Procedure and Subtotal Descriptions Vertical
APPLICTN_ID
PK
T683S-KAPPL - Application
NVARCSTR
no
CONDITN_SEQ_ID
PK
T683S.ZAEHK - Condition counter
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
Time Loaded into the Rapid Mart
NVARCSTR
yes
PRICE_PROCEDURE_ DESCR PRICE_PROCEDURE_ PK ID
T683U-VTEXT - Description (lookup)
NVARCSTR
30
yes
NVARCSTR
no
STEP_NUM
PK
T683S.STUNR - Step number
NVARCSTR
no
SUBTTL_DESCR
T683T, T685T-VTEXT - Description (lookup)
NVARCSTR
30
yes
SUBTTL_ID
T683S-KZWIW - Condition Subtotal
NVARCSTR
yes
10
USAGE_ID
PK
T683S-KVEWE - Usage of the Condition Table NVARCSTR
no
68
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
69
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
70
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
71
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
72
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
Data Integrator Action on Error
NVARCSTR
yes
ETL_ERROR_COLU MN
Data Integrator Error message
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
73
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
Current Node level depth
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
74
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
75
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
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
76
REJECT_REASON
TVAGT - Reject Reason
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
REJECT_REASON_DE SCR
TVAGT-BEZEI - Description
NVARCSTR
40
yes
REJECT_REASON_ID PK
TVAGT-ABGRU - Reason for rejection of quotations and sales orders
NVARCSTR
no
SALES_DISTRICT
T171T - Sales District
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_DISTRICT_ID
PK
T171T.BZIRK - Sales district
NVARCSTR
no
SALES_DISTRICT_NA ME
T171T.BZTXT - Sales district Name
NVARCSTR
20
yes
77
SALES_DOC_STATUS
Status code values (DD07T STATV domain)
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_DOC_STATUS _DESCR SALES_DOC_STATUS PK _ID
Status text DD07T STATV domain
NVARCSTR
60
yes
Status code from DD07T STATV domain
NVARCSTR
no
78
SALES_DOC_STATUS_STAGE
VBFA, VBUK, VBUP - Information of changed statuses during delta extraction
BILL_STATUS_DELIV_ RELTD_ID BILL_STATUS_HDR_I D
VBUP-FKSTA - Billing status of delivery-related billing documents VBUK-FKSAK - Billing status (order-related billing document)
NVARCSTR
yes
NVARCSTR
yes
BILL_STATUS_ID
VBUP-FKSAA - Billing status for order-related NVARCSTR billing documents VBUP-LFGSA - Overall delivery status of the item VBAK-LFGSK - Overall delivery status for all items
yes
DELIV_STATUS_ID
NVARCSTR
yes
DELIV_STATUS_ID_H DR
NVARCSTR
yes
GI_STATUS_ID
VBUP-WBSTA - Goods Issue status (indicates NVARCSTR whether goods have left the warehouse) VBUP-UVALL - General incompletion status of NVARCSTR the item VBUK-UVALL - General incompletion status of NVARCSTR the header
yes
INCOMPLT_STATUS_I D INCOMPLT_STATUS_I D_HDR
yes
yes
LOAD_DATE
DATETIME
24
yes
10
LOAD_TIME
NVARCSTR
yes
11
PACKNG_STATUS_ID
VBUP-PKSTA - Packing status of item
NVARCSTR
yes
12
PICKNG_CONFIRM_S TATUS_ID
NVARCSTR
yes
13
PICKNG_STATUS_ID
VBUP-KOSTA - Picking status
NVARCSTR
yes
14
PROCESS_STATUS_I D PROCESS_STATUS_I D_HDR
VBUP-GBSTA - Overall processing status of the SD document item VBUK-GBSTK - Overall processing status of document
NVARCSTR
yes
15
NVARCSTR
yes
16
REF_STATUS_ID
VBUP.RFGSA - Overall status of reference for NVARCSTR line item
yes
79
Appendix Table Column Details REF_STATUS_ID_HD R VBUK.RFGSK - Total reference status of all items
17
NVARCSTR
yes
18
REJECT_STATUS_ID
VBUP-ABSTA - Rejection status for SD item
NVARCSTR
yes
19
REJECT_STATUS_ID_ HDR
VBUK-ABSTK - Overall rejection status of all document items VBUP-VBELN - Preceding sales and distribution document VBUP-POSNR - Preceding item of an SD document
NVARCSTR
yes
20
SALES_DOC_ID
PK
NVARCSTR
10
no
21
NVARCSTR
no
SALES_GROUP
TVGRT - Sales Group
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_GRP_DESCR
TVGRT-BEZEI - Description
NVARCSTR
40
yes
SALES_GRP_ID
PK
TVGRT-VKGRP - Sales group
NVARCSTR
no
SALES_OFFICE
TVKBT - Sales Office
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_OFFICE_DES CR
TVKBT-BEZEI - Description
NVARCSTR
60
yes
SALES_OFFICE_ID
PK
TVKBT-VKBUR - Sales Office
NVARCSTR
no
80
SALES_ORDER_FACT
VBAP , VBAK - Sales Documents from SAP
ADDRESS_ID_SHIPTO PK
VBPA.ADRNR - Address ID for True Ship-to address on Sales order
NVARCSTR
10
yes
AMT_NET_PRICE_GB L AMT_NET_PRICE_TR X AMT_NET_VALUE_GB L AMT_NET_VALUE_HD R_GBL AMT_NET_VALUE_HD R_TRX AMT_NET_VALUE_TR X
DECIMAL
48
11
yes
DECIMAL
48
11
yes
VBAP-NETWR - Net value of the order item in DECIMAL document currency VBAK-NETWR - Net value of the order in document currency VBAK-NETWR - Net value of the order in document currency
48
15
yes
DECIMAL
48
15
yes
DECIMAL
48
15
yes
VBAP-NETWR - Net value of the order item in DECIMAL document currency Calcualted field: for sales documents of catetories A or B it is 0, for sales documents of DECIMAL categories H or K without rejection reasons it is set to a negative ofthe net i Calcualted field: for sales documents of catetories A or B it is 0, for sales documents of DECIMAL categories H or K without rejection reasons it is set to a negative of the neti VBAP-WAVWR - Cost in document currency DECIMAL
48
15
yes
AMT_RECEIVED_GBL
48
15
yes
AMT_RECEIVED_TRX
48
15
yes
10
AMT_STD_COST_GBL
48
13
yes
11
AMT_STD_COST_TRX
VBAP-WAVWR - Cost in document currency
DECIMAL
48
13
yes
12
AMT_SUBTTL_01_GB L AMT_SUBTTL_01_TR X AMT_SUBTTL_02_GB L AMT_SUBTTL_02_TR X AMT_SUBTTL_03_GB L
VBAP-KZWI1 - Customer-configurable subtotal DECIMAL 1 VBAP-KZWI1 - Customer-configurable subtotal DECIMAL 1 VBAP-KZWI2 - Customer-configurable subtotal DECIMAL 2 VBAP-KZWI2 - Customer-configurable subtotal DECIMAL 2 VBAP-KZWI3 - Customer-configurable subtotal DECIMAL 3
48
13
yes
13
48
13
yes
14
48
13
yes
15
48
13
yes
16
48
13
yes
81
Appendix Table Column Details AMT_SUBTTL_03_TR X AMT_SUBTTL_04_GB L AMT_SUBTTL_04_TR X AMT_SUBTTL_05_GB L AMT_SUBTTL_05_TR X AMT_SUBTTL_06_GB L AMT_SUBTTL_06_TR X VBAP-KZWI3 - Customer-configurable subtotal DECIMAL 3 VBAP-KZWI4 - Customer-configurable subtotal DECIMAL 4 VBAP-KZWI4 - Customer-configurable subtotal DECIMAL 4 VBAP-KZWI5 - Customer-configurable subtotal DECIMAL 5 VBAP-KZWI5 - Customer-configurable subtotal DECIMAL 5 VBAP-KZWI6 - Customer-configurable subtotal DECIMAL 6 VBAP-KZWI6 - Customer-configurable subtotal DECIMAL 6 VBAP-ZWERT - Target value for outline agreement in document currency VBAP-ZWERT - Target value for outline agreement in document currency
17
48
13
yes
18
48
13
yes
19
48
13
yes
20
48
13
yes
21
48
13
yes
22
48
13
yes
23
48
13
yes
24
AMT_TRGT_GBL
DECIMAL
48
13
yes
25
AMT_TRGT_TRX
DECIMAL
48
13
yes
26
BILL_BLOCK_ID
PK
VBAP-FAKSP- Billing block for item
NVARCSTR
yes
27
BILL_BLOCK_ID_HDR
VBAK-FAKSK - Billing block in SD document
NVARCSTR
yes
28
BILL_PLAN_ID
VBKD.FPLNR - Billing Plan / Invoicing Plan number
NVARCSTR
10
yes
29
BILL_RELEVNT_ID
VBAP-FKREL - Relevant for billing
NVARCSTR
yes
30
BILL_STATUS_ID
VBUP-FKSAA - Billing Status of ORder-Related Biling Document VBUK-FKSAK - Billing Status of ORder-Related Biling Document (lookup)
NVARCSTR
yes
31
BILL_STATUS_ID_HD R
NVARCSTR
yes
32
CHANGE_DATE
VBAP-AEDAT - Changed on
DATETIME
24
yes
33
CHANGE_DATE_HDR
VBAK-AEDAT - Changed on
DATETIME
24
yes
34
CMPNY_CODE_ID
PK
VBAK.BUKRS_VF Company Code to be billed NVARCSTR
yes
82
35
COST_CNTR_ID
VBAK.KOSTL - Cost Center
NVARCSTR
10
yes
36
CREATED_BY
VBAK-ERNAM - Name of the use who created NVARCSTR the record VBAK-ERNAM - Name of the use who created NVARCSTR the record VBAP-ERDAT - Date on which the record was created
12
yes
37
CREATED_BY_HDR
12
yes
38
CREATE_DATE
DATETIME
24
yes
39
CREATE_DATE_HDR
PK
VBAK-ERDAT - Date on which the record was DATETIME created
24
yes
40
CREATE_TIME
VBAP.ERZET - Entry time
NVARCSTR
yes
41
CREATE_TIME_HDR
VBAK.ERZET - Entry time
NVARCSTR
yes
42
CR_CTRL_AREA_ID
PK
NVARCSTR
yes
43
CR_MGMT_RISK_CLA PK SS_ID
NVARCSTR
yes
44
CTRL_AREA_ID
PK
VBAK.KOKRS - Controlling area
NVARCSTR
yes
45
CURR_ID_GBL
PK
Global Currency (Global Variable Set in Rapid Mart Job)
NVARCSTR
yes
46
CURR_ID_STATS
VBAK-STWAE - Statistics currency
NVARCSTR
yes
47
CURR_ID_TRX
PK
VBAP-WAERK - Line Item Document Currency NVARCSTR
yes
48
CURR_ID_TRX_HDR
VBAK-WAERK - Document header Currency code
NVARCSTR
yes
49
CUSTOMER_GRP_01_ PK ID CUSTOMER_GRP_02_ ID CUSTOMER_GRP_03_ ID CUSTOMER_GRP_04_ ID
VBAK-KVGR1 - Customer group 1
NVARCSTR
yes
50
VBAK.KVGR2 - Customer group 2
NVARCSTR
yes
51
NVARCSTR
yes
52
NVARCSTR
yes
83
Appendix Table Column Details CUSTOMER_GRP_05_ ID CUSTOMER_ID_BILLT O CUSTOMER_ID_SHIP TO CUSTOMER_ID_SOLD PK TO CUSTOMER_PO_DA TE CUSTOMER_PO_LINE _NUM
53
NVARCSTR
yes
54
NVARCSTR
10
yes
55
NVARCSTR
10
yes
56
VBAK-KUNNR -Customer Number
NVARCSTR
10
yes
57
VBAK-BSTDK - Customer PO date
DATETIME
24
yes
58
VBAP-POSEX - Item number of the underlying NVARCSTR customer PO VBAK-BSTNK - Customer purchase order number VBAK-LIFSK - Delivery block (document header)
yes
59
CUSTOMER_PO_NUM
NVARCSTR
20
yes
60
DELIV_BLOCK_ID
PK
NVARCSTR
yes
61
DELIV_RELEVNT_FLA G
VBAP.LFREL - Item is relevant for delivery
NVARCSTR
yes
62
DELIV_ROUTE_ID
PK
VBAP.ROUTE - Route
NVARCSTR
yes
63
DELIV_STATUS_ID
VBUP-LFGSA - Overall Delivery Status of the Item VBUK-LFGSK - Overall Delivery Status of the Item (lookup)
NVARCSTR
yes
64
DELIV_STATUS_ID_H DR DISTRIBTN_CHANNEL PK _ID
NVARCSTR
yes
65
NVARCSTR
yes
66
DIVISION_ID
PK
VBAP-SPART - Division
NVARCSTR
yes
67
DIVISION_ID_HDR
NVARCSTR
yes
68
DOC_CATEG_ID
PK
VBAK-VBTYP - SD document category
NVARCSTR
yes
69
DOC_CATEG_ID_REF
VBAP-VGTYP - Document category of preceding SD document VBAK.AUDAT - Document date (incoming or outgoing date)
NVARCSTR
yes
70
DOC_DATE
PK
DATETIME
24
yes
84
71
DOC_TYPE_ID
PK
VBAK-AUART - Sales Document Type
NVARCSTR
yes
72
EXCH_RATE_GBL
TCURR.UKURS - Exchange rate from Document Currency to Global Currency VBAP-STCUR - Exchange rate for statistics (Exch.rate at time of creation) Global Exchange Type (Global Variable Set in Rapid Mart Job)
DECIMAL
48
yes
73
EXCH_RATE_STATS
DECIMAL
48
yes
74
EXCH_TYPE_ID_GBL
PK
NVARCSTR
yes
75
EXCH_TYPE_ID_STAT S
VBAK.KURST - Exchange rate type
NVARCSTR
yes
76
FROM_FACTOR_GBL
TCURR.FFACT - Ratio for the document currency units
INTEGER
yes
77
VBUP-UVALL - General Incompletion Status of NVARCSTR the Item VBUK-UVALL - General Incompletion Status of NVARCSTR the Item
yes
78
yes
79
INTERNAL_ORDER_ID
VBAP.AUFNR - Order number
NVARCSTR
12
yes
80
INTERNAL_ORDER_ID _HDR INTER_CMPNY_TERM PK 01_ID INTER_CMPNY_TERM 02_NAME LINE_ITEM_ID_HIGHE R
VBAK.AUFNR - Order Number
NVARCSTR
12
yes
81
NVARCSTR
yes
82
NVARCSTR
28
yes
83
VBAP-UEPOS - Higher-level item in bill of material structures
NVARCSTR
yes
84
LOAD_DATE
DATETIME
24
yes
85
LOAD_TIME
System time load
NVARCSTR
yes
86
MATERIAL_ID
PK
NVARCSTR
18
yes
87
MTRL_GRP_01_ID
VBAP.MVGR1 - Material pricing group 1
NVARCSTR
yes
88
MTRL_GRP_02_ID
VBAP.MVGR2 - Material group 2 (customer-defined)
NVARCSTR
yes
85
Appendix Table Column Details VBAP.MVGR3 - Material group 3 (customer-defined) VBAP.MVGR4 - Material group 4 (customer-defined)
89
MTRL_GRP_03_ID
NVARCSTR
yes
90
MTRL_GRP_04_ID
NVARCSTR
yes
91
MTRL_GRP_05_ID
NVARCSTR
yes
92
MTRL_GRP_ID
PK
VBAP.MATKL - Material group
NVARCSTR
yes
93
MTRL_SHORT_TXT
VBAP.ARKTX - Short text for sales order item NVARCSTR
40
yes
94
NOTIFICTN_ID
VBAK.QMNUM - Notification number
NVARCSTR
12
yes
95
ORDER_REASON_ID
PK
VBAK-AUGRU - Order reason (reason for the business transaction)
NVARCSTR
yes
96
PAYMNT_TERM_ID
PK
VBKD.ZTERM - Payment Terms ID
NVARCSTR
yes
97
PLANT_ID
PK
VBAP.WERKS Plant
NVARCSTR
yes
98
PRICE_PROCEDURE_ PK ID PROCESS_STATUS_I PK D
VBAK-KALSM - Pricing procedure for sales and distribution VBUP-GBSTA - Overall Processing Status of the SD item VBUK-GBSTK - Overall Processing Status of the SD item (lookup)
NVARCSTR
yes
99
NVARCSTR
yes
100 PROCESS_STATUS_I D_HDR
NVARCSTR
yes
101 PROD_HIER_ID
VBAP.PRODH - Product hierarchy
NVARCSTR
18
yes
102 PROFIT_CNTR_ID
PK
VBAP.PRCTR - Profit center
NVARCSTR
10
yes
103 QTY_CONFIRM_SLSU OM 104 QTY_ORDER_SLSU OM
VBAP-KBMENG - Cumulative confirmed quantity in sales unit
DECIMAL
48
15
yes
VBAP- KWMENG - Cumulative Order Quantity DECIMAL in Sales Units
48
15
yes
105 QTY_PRICE_UNIT
VBAP-KPEIN - Condition pricing unit
INTEGER
yes
106 QTY_RECEIVED_SLS UOM
Calcualted field: for sales documents of catetories A or B it is 0, for sales documents of DECIMAL categories H or K without rejection reasons it is set to a negative of the sale
48
15
yes
86
107 QTY_TRGT_SLSUOM
VBAP-ZMENG - Target quantity in sales units DECIMAL
48
13
yes
108 REF_DOC_ID
VBAP-VGVEL - Reference Document Number NVARCSTR
10
yes
109 REF_LINE_ITEM_ID
VBAP-VGPOS - Item number of the reference NVARCSTR item
yes
110 REF_STATUS_ID
VBUP-RFGSA - Overall status of reference
NVARCSTR
yes
111 REF_STATUS_ID_HD R
VBAK-RFGSK - Total reference status of all items VBAP-ABGRU - Reason for rejection of quotations and sales orders
NVARCSTR
yes
112 REJECT_REASON_ID PK
NVARCSTR
yes
113 REJECT_STATUS_ID
VBAP-ABSTA - Rejection status for SD item
NVARCSTR
yes
114 REJECT_STATUS_ID_ HDR
VBUK-ABSTK - Rejection status
NVARCSTR
yes
115 RETURN_FLAG
VBAP-SHKZG - Returns item
NVARCSTR
yes
116 RQST_DELIV_DATE_ HDR
VBAK-VDATU - Proposed schedule line date
DATETIME
24
yes
117 SALES_DISTRICT_ID
PK
VBKD.BZIRK - Sales District
NVARCSTR
yes
118 SALES_DOC_ID
PK
VBAP-VBELN - Sales Document Number
NVARCSTR
10
no
119 SALES_DOC_STATUS PK _KEY
NVARCSTR
36
yes
120 SALES_GRP_ID
PK
VBAK-VKGRP - Sales group
NVARCSTR
yes
121 SALES_LINE_ITEM_ID PK
VBAP-POSNR - Sales Document item
NVARCSTR
no
122 SALES_OFFICE_ID
PK
NVARCSTR
yes
123 SALES_ORG_ID
PK
NVARCSTR
yes
124 SALES_PERSON_ID
PK
NVARCSTR
yes
87
Appendix Table Column Details 125 SALES_TO_BASE_DIV ISOR 126 SALES_TO_BASE_MU LTIPLR VBAP-UMVKN - Denominator (divisor) for conversion of sales qty. into SKU VBAP-UMVKZ - Numerator (factor) for conversion of sales quantity into SKU
INTEGER
yes
INTEGER
yes
127 SHIP_POINT_ID
PK
VBAP.VSTEL - Shipping point
NVARCSTR
yes
128 STORAGE_LOCATN_I PK D
NVARCSTR
yes
129 TO_FACTOR_GBL
TCURR.TFACT - Ratio for the Global currency INTEGER units
yes
130 UOM_ID_BASE
VBAP-MEINS - Base unit of measure
NVARCSTR
yes
131 UOM_ID_PRICE
VBAP-KMEIN - Condition Unit of Measure
NVARCSTR
yes
132 UOM_ID_SALES
PK
VBAP-VRKME - Sales Unit
NVARCSTR
yes
133 UOM_ID_TRGT
VBAP-ZIEME - Sales unit of target quantity
NVARCSTR
yes
134 VALID_FROM_DATE
PK
VBAK-GUEBG - Valid-from date (outline agreements, product proposals) VBAK-GUEEN - Valid-to date (outline agreements, product proposals) VBAK.GWLDT - Beginning of the warranty period
DATETIME
24
yes
135 VALID_TO_DATE
DATETIME
24
yes
136 WARRANTY_START _DATE
DATETIME
24
yes
88
SALES_ORDER_FACT_BAD
Invalid Sales Documents fact (similar to SALES_ORDER_FACT structure)
ADDRESS_ID_SHIPTO
NVARCSTR
10
yes
DECIMAL
48
11
yes
DECIMAL
48
11
yes
48
15
yes
DECIMAL
48
15
yes
DECIMAL
48
15
yes
48
15
yes
AMT_RECEIVED_GBL
48
15
yes
AMT_RECEIVED_TRX
48
15
yes
10
AMT_STD_COST_GBL
48
13
yes
11
AMT_STD_COST_TRX
DECIMAL
48
13
yes
12
48
13
yes
13
48
13
yes
14
48
13
yes
15
48
13
yes
16
48
13
yes
89
17
48
13
yes
18
48
13
yes
19
48
13
yes
20
48
13
yes
21
48
13
yes
22
48
13
yes
23
48
13
yes
24
AMT_TRGT_GBL
DECIMAL
48
13
yes
25
AMT_TRGT_TRX
DECIMAL
48
13
yes
26
BILL_BLOCK_ID
NVARCSTR
yes
27
BILL_BLOCK_ID_HDR
NVARCSTR
yes
28
BILL_PLAN_ID
NVARCSTR
10
yes
29
BILL_RELEVNT_ID
NVARCSTR
yes
30
BILL_STATUS_ID
NVARCSTR
yes
31
BILL_STATUS_ID_HD R
NVARCSTR
yes
32
CHANGE_DATE
DATETIME
24
yes
33
CHANGE_DATE_HDR
DATETIME
24
yes
34
CMPNY_CODE_ID
yes
90
35
COST_CNTR_ID
NVARCSTR
10
yes
36
CREATED_BY
12
yes
37
CREATED_BY_HDR
12
yes
38
CREATE_DATE
DATETIME
24
yes
39
CREATE_DATE_HDR
24
yes
40
CREATE_TIME
NVARCSTR
yes
41
CREATE_TIME_HDR
NVARCSTR
yes
42
CR_CTRL_AREA_ID
NVARCSTR
yes
43
CR_MGMT_RISK_CLA SS_ID
NVARCSTR
yes
44
CTRL_AREA_ID
NVARCSTR
yes
45
CURR_ID_GBL
NVARCSTR
yes
46
CURR_ID_STATS
NVARCSTR
yes
47
CURR_ID_TRX
yes
48
CURR_ID_TRX_HDR
NVARCSTR
yes
49
CUSTOMER_GRP_01_ ID CUSTOMER_GRP_02_ ID CUSTOMER_GRP_03_ ID CUSTOMER_GRP_04_ ID
NVARCSTR
yes
50
NVARCSTR
yes
51
NVARCSTR
yes
52
NVARCSTR
yes
91
Appendix Table Column Details CUSTOMER_GRP_05_ ID CUSTOMER_ID_BILLT O CUSTOMER_ID_SHIP TO CUSTOMER_ID_SOLD TO CUSTOMER_PO_DA TE CUSTOMER_PO_LINE _NUM
53
NVARCSTR
yes
54
NVARCSTR
10
yes
55
NVARCSTR
10
yes
56
NVARCSTR
10
yes
57
DATETIME
24
yes
58
yes
59
CUSTOMER_PO_NUM
NVARCSTR
20
yes
60
DELIV_BLOCK_ID
NVARCSTR
yes
61
DELIV_RELEVNT_FLA G
NVARCSTR
yes
62
DELIV_ROUTE_ID
VBAP.ROUTE - Route
NVARCSTR
yes
63
DELIV_STATUS_ID
NVARCSTR
yes
64
DELIV_STATUS_ID_H DR DISTRIBTN_CHANNEL _ID
NVARCSTR
yes
65
NVARCSTR
yes
66
DIVISION_ID
NVARCSTR
yes
67
DIVISION_ID_HDR
NVARCSTR
yes
68
DOC_CATEG_ID
NVARCSTR
yes
69
DOC_CATEG_ID_REF
NVARCSTR
yes
70
DOC_DATE
DATETIME
24
yes
92
71
DOC_TYPE_ID
NVARCSTR
yes
72
ETL_ERROR_ACTN
DI Validation transform error action code
NVARCSTR
yes
73
ETL_ERROR_COLU MN
DI Valication transfrom error column name
NVARCSTR
500
yes
74
EXCH_RATE_GBL
DECIMAL
48
yes
75
EXCH_RATE_STATS
DECIMAL
48
yes
76
EXCH_TYPE_ID_GBL
NVARCSTR
yes
77
EXCH_TYPE_ID_STAT S
NVARCSTR
yes
78
FROM_FACTOR_GBL
INTEGER
yes
79
yes
80
yes
81
INTERNAL_ORDER_ID
NVARCSTR
12
yes
82
INTERNAL_ORDER_ID _HDR INTER_CMPNY_TERM 01_ID INTER_CMPNY_TERM 02_NAME LINE_ITEM_ID_HIGHE R
NVARCSTR
12
yes
83
NVARCSTR
yes
84
NVARCSTR
28
yes
85
NVARCSTR
yes
86
LOAD_DATE
PK
DATETIME
24
no
87
LOAD_TIME
System time load
NVARCSTR
yes
88
MATERIAL_ID
NVARCSTR
18
yes
93
89
MTRL_GRP_01_ID
NVARCSTR
yes
90
MTRL_GRP_02_ID
VBAP.MVGR2 - Material group 2 (customer-defined) VBAP.MVGR3 - Material group 3 (customer-defined) VBAP.MVGR4 - Material group 4 (customer-defined)
NVARCSTR
yes
91
MTRL_GRP_03_ID
NVARCSTR
yes
92
MTRL_GRP_04_ID
NVARCSTR
yes
93
MTRL_GRP_05_ID
NVARCSTR
yes
94
MTRL_GRP_ID
NVARCSTR
yes
95
MTRL_SHORT_TXT
40
yes
96
NOTIFICTN_ID
NVARCSTR
12
yes
97
ORDER_REASON_ID
NVARCSTR
yes
98
PAYMNT_TERM_ID
NVARCSTR
yes
99
PLANT_ID
VBAP-WERKS -- Plant
NVARCSTR
yes
100 PRICE_PROCEDURE_ ID 101 PROCESS_STATUS_I D 102 PROCESS_STATUS_I D_HDR
NVARCSTR
yes
NVARCSTR
yes
NVARCSTR
yes
103 PROD_HIER_ID
NVARCSTR
18
yes
104 PROFIT_CNTR_ID
NVARCSTR
10
yes
DECIMAL
48
15
yes
48
15
yes
94
107 QTY_PRICE_UNIT
INTEGER
yes
Calcualted field: for sales documents of catetories A or B it is 0, for sales documents of DECIMAL categories H or K without rejection reasons it is set to a negative of the sale VBAP-ZMENG - Target quantity in sales units DECIMAL
48
15
yes
109 QTY_TRGT_SLSUOM
48
13
yes
110 REF_DOC_ID
10
yes
yes
112 REF_STATUS_ID
NVARCSTR
yes
NVARCSTR
yes
114 REJECT_REASON_ID
NVARCSTR
yes
NVARCSTR
yes
NVARCSTR
yes
117 RETURN_FLAG
NVARCSTR
yes
DATETIME
24
yes
NVARCSTR
yes
120 SALES_DOC_ID
PK
NVARCSTR
10
no
121 SALES_DOC_STATUS _KEY
NVARCSTR
36
yes
122 SALES_GRP_ID
NVARCSTR
yes
NVARCSTR
no
124 SALES_OFFICE_ID
NVARCSTR
yes
95
125 SALES_ORG_ID
NVARCSTR
yes
126 SALES_PERSON_ID
NVARCSTR
yes
127 SALES_TO_BASE_DIV ISOR 128 SALES_TO_BASE_MU LTIPLR
VBAP-UMVKN - Denominator (divisor) for conversion of sales qty. into SKU VBAP-UMVKZ - Numerator (factor) for conversion of sales quantity into SKU
INTEGER
yes
INTEGER
yes
129 SHIP_POINT_ID
NVARCSTR
yes
130 STORAGE_LOCATN_I D
VBAP.LGORT - Storage location
NVARCSTR
yes
131 TO_FACTOR_GBL
yes
132 UOM_ID_BASE
NVARCSTR
yes
133 UOM_ID_PRICE
NVARCSTR
yes
134 UOM_ID_SALES
NVARCSTR
yes
135 UOM_ID_TRGT
NVARCSTR
yes
136 VALID_FROM_DATE
DATETIME
24
yes
137 VALID_TO_DATE
DATETIME
24
yes
DATETIME
24
yes
96
SALES_ORDER_HISTORY
VBAP , VBAK - extraction with history preservation
AMT_NET_VALUE_DE LTA_TRX AMT_NET_VALUE_TR X
Calculated changed net item value
DECIMAL
48
17
yes
VBAP-NETWR - Net Value of the Order Line Item in Document Currency
DECIMAL
48
17
yes
CMPNY_CODE_ID
PK
VBAK.BUKRS_VF - Company code
NVARCSTR
yes
CREATE_DATE
PK
VBAK-ERDAT - Date when the record was created
DATETIME
24
yes
CTRL_AREA_ID
PK
NVARCSTR
yes
CURRENT_FLAG
If set to 'C' indicates the current record, if set to 'D' indicates the deleted record, if set to ' ' NVARCSTR indicates that the record is not current PK VBAK-STWAE - Statistics Currency NVARCSTR
yes
CURR_ID_TRX
yes
VBAK-KUNNR - Sold-to Customer Number
NVARCSTR
10
yes
LOAD_DATE
DATETIME
24
yes
10
LOAD_TIME
NVARCSTR
yes
11
PLANT_ID
PK
VBAP.WERKS Plant
NVARCSTR
yes
12
PROFIT_CNTR_ID
PK
NVARCSTR
10
yes
13
QTY_ORDER_DELTA_ SLSUOM QTY_ORDER_SLSU OM
Calculated changed quantity
DECIMAL
48
15
yes
14
VBAP- KWMENG - Cumulative Order Quantity DECIMAL In Sales Units
48
15
yes
15
SALES_DOC_ID
NVARCSTR
10
yes
16
SALES_LINE_ITEM_ID
NVARCSTR
yes
97
17
SALES_ORG_ID
PK
TVKO-VKORG - Sales Organization ID
NVARCSTR
yes
18
SALES_PERSON_ID
PK
PA0002-PERNR - Personnel Number
NVARCSTR
yes
19
STORAGE_LOCATN_I D
NVARCSTR
yes
20
SURROGATE_KEY_ID PK
AW Generated key
INTEGER
no
21
UOM_ID_SALES
PK
NVARCSTR
yes
22
VALID_FROM_DATE
Calculated date
DATETIME
24
yes
23
VALID_TO_DATE
Calculated date
DATETIME
24
yes
98
SALES_ORDER_STAGE
Staging table for sales order fact - used for efficient currency conversion and address processing
ADDRESS_ID_SHIPTO
NVARCSTR
10
yes
DECIMAL
48
11
yes
DECIMAL
48
11
yes
48
15
yes
DECIMAL
48
15
yes
DECIMAL
48
15
yes
48
15
yes
AMT_RECEIVED_GBL
48
15
yes
AMT_RECEIVED_TRX
48
15
yes
10
AMT_STD_COST_GBL
48
13
yes
11
AMT_STD_COST_TRX
DECIMAL
48
13
yes
12
48
13
yes
13
48
13
yes
14
48
13
yes
15
48
13
yes
16
48
13
yes
99
17
48
13
yes
18
48
13
yes
19
48
13
yes
20
48
13
yes
21
48
13
yes
22
48
13
yes
23
48
13
yes
24
AMT_TRGT_GBL
DECIMAL
48
13
yes
25
AMT_TRGT_TRX
DECIMAL
48
13
yes
26
BILL_BLOCK_ID
NVARCSTR
yes
27
BILL_BLOCK_ID_HDR
NVARCSTR
yes
28
BILL_PLAN_ID
NVARCSTR
10
yes
29
BILL_RELEVNT_ID
NVARCSTR
yes
30
BILL_STATUS_ID
NVARCSTR
yes
31
BILL_STATUS_ID_HD R
NVARCSTR
yes
32
CHANGE_DATE
DATETIME
24
yes
33
CHANGE_DATE_HDR
DATETIME
24
yes
34
CMPNY_CODE_ID
yes
100
35
COST_CNTR_ID
NVARCSTR
10
yes
36
CREATED_BY
12
yes
37
CREATED_BY_HDR
12
yes
38
CREATE_DATE
DATETIME
24
yes
39
CREATE_DATE_HDR
24
yes
40
CREATE_TIME
NVARCSTR
yes
41
CREATE_TIME_HDR
NVARCSTR
yes
42
CR_CTRL_AREA_ID
NVARCSTR
yes
43
CR_MGMT_RISK_CLA SS_ID
NVARCSTR
yes
44
CTRL_AREA_ID
NVARCSTR
yes
45
CURR_ID_GBL
NVARCSTR
yes
46
CURR_ID_STATS
NVARCSTR
yes
47
CURR_ID_TRX
yes
48
CURR_ID_TRX_HDR
NVARCSTR
yes
49
CUSTOMER_GRP_01_ ID CUSTOMER_GRP_02_ ID CUSTOMER_GRP_03_ ID CUSTOMER_GRP_04_ ID
NVARCSTR
yes
50
NVARCSTR
yes
51
NVARCSTR
yes
52
NVARCSTR
yes
101
Appendix Table Column Details CUSTOMER_GRP_05_ ID CUSTOMER_ID_BILLT O CUSTOMER_ID_SHIP TO CUSTOMER_ID_SOLD TO CUSTOMER_PO_DA TE CUSTOMER_PO_LINE _NUM
53
NVARCSTR
yes
54
NVARCSTR
10
yes
55
NVARCSTR
10
yes
56
NVARCSTR
10
yes
57
DATETIME
24
yes
58
yes
59
CUSTOMER_PO_NUM
NVARCSTR
20
yes
60
DELIV_BLOCK_ID
NVARCSTR
yes
61
DELIV_RELEVNT_FLA G
NVARCSTR
yes
62
DELIV_ROUTE_ID
VBAP.ROUTE - Route
NVARCSTR
yes
63
DELIV_STATUS_ID
NVARCSTR
yes
64
DELIV_STATUS_ID_H DR DISTRIBTN_CHANNEL _ID
NVARCSTR
yes
65
NVARCSTR
yes
66
DIVISION_ID
NVARCSTR
yes
67
DIVISION_ID_HDR
NVARCSTR
yes
68
DOC_CATEG_ID
NVARCSTR
yes
69
DOC_CATEG_ID_REF
NVARCSTR
yes
70
DOC_DATE
DATETIME
24
yes
102
71
DOC_TYPE_ID
NVARCSTR
yes
72
EXCH_RATE_GBL
DECIMAL
48
yes
73
EXCH_RATE_STATS
DECIMAL
48
yes
74
EXCH_TYPE_ID_GBL
NVARCSTR
yes
75
EXCH_TYPE_ID_STAT S
NVARCSTR
yes
76
FROM_FACTOR_GBL
INTEGER
yes
77
yes
78
yes
79
INTERNAL_ORDER_ID
NVARCSTR
12
yes
80
INTERNAL_ORDER_ID _HDR INTER_CMPNY_TERM 01_ID INTER_CMPNY_TERM 02_NAME LINE_ITEM_ID_HIGHE R
NVARCSTR
12
yes
81
NVARCSTR
yes
82
NVARCSTR
28
yes
83
NVARCSTR
yes
84
LOAD_DATE
DATETIME
24
yes
85
LOAD_TIME
System time load
NVARCSTR
yes
86
MATERIAL_ID
NVARCSTR
18
yes
87
MTRL_GRP_01_ID
NVARCSTR
yes
88
MTRL_GRP_02_ID
VBAP.MVGR2 - Material group 2 (customer-defined)
NVARCSTR
yes
103
Appendix Table Column Details VBAP.MVGR3 - Material group 3 (customer-defined) VBAP.MVGR4 - Material group 4 (customer-defined)
89
MTRL_GRP_03_ID
NVARCSTR
yes
90
MTRL_GRP_04_ID
NVARCSTR
yes
91
MTRL_GRP_05_ID
NVARCSTR
yes
92
MTRL_GRP_ID
NVARCSTR
yes
93
MTRL_SHORT_TXT
40
yes
94
NOTIFICTN_ID
NVARCSTR
12
yes
95
ORDER_REASON_ID
NVARCSTR
yes
96
PAYMNT_TERM_ID
NVARCSTR
yes
97
PLANT_ID
VBAP-WERKS -- Plant
NVARCSTR
yes
98
NVARCSTR
yes
99
NVARCSTR
yes
100 PROCESS_STATUS_I D_HDR
NVARCSTR
yes
101 PROD_HIER_ID
NVARCSTR
18
yes
102 PROFIT_CNTR_ID
NVARCSTR
10
yes
DECIMAL
48
15
yes
48
15
yes
105 QTY_PRICE_UNIT
INTEGER
yes
Calcualted field: for sales documents of catetories A or B it is 0, for sales documents of DECIMAL categories H or K without rejection reasons it is set to a negative of the sale
48
15
yes
104
107 QTY_TRGT_SLSUOM
VBAP-ZMENG - Target quantity in sales units DECIMAL
48
13
yes
108 REF_DOC_ID
10
yes
yes
110 REF_STATUS_ID
NVARCSTR
yes
NVARCSTR
yes
112 REJECT_REASON_ID
NVARCSTR
yes
NVARCSTR
yes
NVARCSTR
yes
115 RETURN_FLAG
NVARCSTR
yes
DATETIME
24
yes
NVARCSTR
yes
118 SALES_DOC_ID
PK
NVARCSTR
10
no
119 SALES_DOC_STATUS _KEY
NVARCSTR
36
yes
120 SALES_GRP_ID
NVARCSTR
yes
NVARCSTR
no
122 SALES_OFFICE_ID
NVARCSTR
yes
123 SALES_ORG_ID
NVARCSTR
yes
124 SALES_PERSON_ID
NVARCSTR
yes
105
Appendix Table Column Details 125 SALES_TO_BASE_DIV ISOR 126 SALES_TO_BASE_MU LTIPLR VBAP-UMVKN - Denominator (divisor) for conversion of sales qty. into SKU VBAP-UMVKZ - Numerator (factor) for conversion of sales quantity into SKU
INTEGER
yes
INTEGER
yes
127 SHIP_POINT_ID
NVARCSTR
yes
128 STORAGE_LOCATN_I D
VBAP.LGORT - Storage location
NVARCSTR
yes
129 TO_FACTOR_GBL
yes
130 UOM_ID_BASE
NVARCSTR
yes
131 UOM_ID_PRICE
NVARCSTR
yes
132 UOM_ID_SALES
NVARCSTR
yes
133 UOM_ID_TRGT
NVARCSTR
yes
134 VALID_FROM_DATE
DATETIME
24
yes
135 VALID_TO_DATE
DATETIME
24
yes
DATETIME
24
yes
106
SALES_ORDER_STATUS
Sales Document statuses code combinations
BILL_STATUS_DESCR
Lookup on Sales Document Status dimension for the status descritpion VBUP-FKSAA - Billing Status of ORder-Related Biling Document Lookup on Sales Document Status dimension for the status descritpion VBUP-LFGSA - Overall Delivery Status of the Item Lookup on Sales Document Status dimension for the status descritpion
NVARCSTR
60
yes
BILL_STATUS_ID
NVARCSTR
yes
DELIV_STATUS_DES CR
NVARCSTR
60
yes
DELIV_STATUS_ID
NVARCSTR
yes
INCOMPLT_STATUS_ DESCR INCOMPLT_STATUS_I D
NVARCSTR
60
yes
VBUP-UVALL - General Incompletion Status of NVARCSTR the Item
yes
LOAD_DATE
System date and time of loading
DATETIME
24
yes
LOAD_TIME
Time in string format when the record was loaded Lookup on Sales Document Status dimension for the status descritpion VBUP-GBSTA - Overall Processing Status of the SD item Lookup on Sales Document Status dimension for the status descritpion
NVARCSTR
yes
PROCESS_STATUS_D ESCR PROCESS_STATUS_I D
NVARCSTR
60
yes
10
NVARCSTR
yes
11
REF_STATUS_DESCR
NVARCSTR
60
yes
12
REF_STATUS_ID
NVARCSTR
yes
13
REJECT_STATUS_DE SCR
Lookup on Sales Document Status dimension for the status descritpion
NVARCSTR
60
yes
14
REJECT_STATUS_ID
NVARCSTR
yes
15
SALES_DOC_STATUS PK _KEY
NVARCSTR
36
no
107
SALES_ORGANIZATION
TVKOT - Sales Organization
CMPNY_CODE_ID
TVKO-BUKRS - Company Code Of The Sales Org
NVARCSTR
yes
CMPNY_CODE_NAME
T001-VTEXT - Company Code name
NVARCSTR
25
yes
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_ORG_DESCR
TVKOT-VTEXT - Description
NVARCSTR
60
yes
SALES_ORG_ID
PK
TVKO-VKORG - Sales Organization
NVARCSTR
no
108
SALES_ORGANIZATION_HIER
TVBVK, TVKBZ, TVTA - Sales Organization Hierarchy (History) - Type 2 Slowly Changing Dimension
TVKBZ-VTWEG
NVARCSTR
no
DIVISION_ID
PK
TVKBZ-SPART
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_GRP_ID
PK
TVBKV-VKGRP
NVARCSTR
no
SALES_OFFICE_ID
PK
TVKBZ-VKBUR
NVARCSTR
no
SALES_ORG_ID
PK
TVKBZ-VKORG
NVARCSTR
no
VALID_FROM_DATE
PK
Valid From Date
DATETIME
24
no
VALID_TO_DATE
Valid to date
DATETIME
24
yes
109
SALES_ORGANIZATION_HIER_CUR
TVBVK, TVKBZ, TVTA - Sales Organization Hierarchy (Current)
TVTA-VTWEG - Distribution channel
NVARCSTR
no
DIVISION_ID
PK
TVTA-SPART - Division
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_GRP_ID
PK
TVBKV-VKGRP - Sales Group
NVARCSTR
no
SALES_OFFICE_ID
PK
TVKBZ-VKBUR - Sales Office
NVARCSTR
no
SALES_ORG_ID
PK
TVTA-VKORG - Sales organization
NVARCSTR
no
SALES_ORGANIZATION_HIER_STAGE
Staging table for capture of changed rows in sales org hierarchy
TVKBZ-VTWEG
NVARCSTR
no
DIVISION_ID
PK
TSPAT-SPART -- Division
NVARCSTR
no
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_GRP_ID
PK
TVGRT-VKGRP - Sales Group
NVARCSTR
no
SALES_OFFICE_ID
PK
TVKBT-VKBUR - Sales Office
NVARCSTR
no
SALES_ORG_ID
PK
TVTA-VKORG - Sales Organization
NVARCSTR
no
110
SALES_PERSON
From PA0002 - HR Master Record - Names of Sales People
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SALES_PERSON_FIR ST_NAME SALES_PERSON_FUL L_NAME
P0002-VORNA - First Name
NVARCSTR
40
yes
P0002-VORNA and P0002-NACHN Concatenation of First Name and Last Name
NVARCSTR
100
yes
SALES_PERSON_ID
PK
PA0900-PERNR - Personnel Number
NVARCSTR
no
SALES_PERSON_LAS T_NAME
PA0002-NACHN - Last Name
NVARCSTR
40
yes
111
SALES_SCHED_LINE_FACT
VBEP - Sales Order Schedule Lines
CREATE_DATE
DAYS_EARLY_LATE
DELIV_BLOCK_ID
PK
VBAK-ERDAT - Date on which the record was created Difference between Requested Deliv. Date (VBAK.VDATU) and Planned Goods Issue Date (VBEP.WADAT). A negative number indicates Late Delivery. A positive number indicatesE VBEP-LIFSP - Schedule line blocked for delivery
DATETIME
24
yes
INTEGER
yes
NVARCSTR
yes
DELIV_DATE
PK
VBEP-EDATU - Delivery date for the schedule DATETIME line
24
yes
DELIV_TIME
VBEP-EZEIT - Arrival time
NVARCSTR
yes
GI_DATE
VBEP-WADAT - Goods issue date
DATETIME
24
yes
LOAD_DATE
Date when the record is loaded
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
MATERIAL_ID
PK
MATNR Material number
NVARCSTR
18
yes
10
MTRL_AVAIL_DATE
VBEP-MBDAT - Material availability date
DATETIME
24
yes
11
MTRL_GRP_ID
VBAP.MATKL Material Group
NVARCSTR
yes
12
PLANT_ID
PK
VBAP-WERKS - Plant ID (lookup)
NVARCSTR
yes
13
PROD_HIER_ID
NVARCSTR
18
yes
14
QTY_ADJUST_SLSUO M QTY_CONFIRM_BASE UOM QTY_CONFIRM_SLSU OM
VBEP-CMENG - Corrected quantity in sales unit
DECIMAL
48
13
yes
15
Confirmed quantity in Base Units
DECIMAL
48
13
yes
16
VBEP-BMENG - Confirmed quantity
DECIMAL
48
13
yes
112
Appendix Table Column Details QTY_ORDER_BASE UOM QTY_ORDER_SLSU OM
17
Order quantity in Base Units
DECIMAL
48
13
yes
18
VBEP-WMENG - Order quantity in sales units
DECIMAL
48
13
yes
19
RQST_DELIV_DATE
Proposed schedule line date
DATETIME
24
yes
20
SALES_DOC_ID
PK
VBEP-VBELN - Sales document
NVARCSTR
10
no
21
VBEP-POSNR - Sales document item
NVARCSTR
no
22
SALES_TO_BASE_DIV ISOR SALES_TO_BASE_MU LTIPLR SCHED_LINE_ITEM_I D
VBEP-UMVKN - Denominator (divisor) for conversion of sales qty. into SKU VBEP-UMVKZ - Numerator (factor) for conversion of sales quantity into SKU
INTEGER
yes
23
INTEGER
yes
24
PK
VBEP-ETENR - Schedule line
NVARCSTR
no
25
SCHED_LOAD_DATE
VBEP-LDDAT - Loading date
DATETIME
24
yes
26
TRANSPORT_SCHE D_DATE
VBEP-TDDAT - Transportation scheduling date
DATETIME
24
yes
27
UOM_ID_BASE
VBEP-MEINS - Base unit of measure
NVARCSTR
yes
28
UOM_ID_SALES
PK
VBEP.VRKME - Sales Unit of Measure
NVARCSTR
yes
SHIPPING_POINT
TVSTT - Shipping Point
LOAD_DATE
DATETIME
24
yes
LOAD_TIME
NVARCSTR
yes
SHIP_POINT_DESCR
TVSTT.VTEXT - Shipping point/receiving point NVARCSTR Description
30
yes
SHIP_POINT_ID
PK
TVSTT.VSTEL - Shipping point/receiving point NVARCSTR
no
113
STORAGE_LOCATION
T001L - Storage Locations in SAP
CMPNY_CODE_ID
T001K. BUKRS - Lookup for Company Code ID
NVARCSTR
yes
CMPNY_CODE_NAME
Lookup on Company Code Name
NVARCSTR
25
yes
CUSTOMER_ID
T001L.KUNNR Account number of customer
NVARCSTR
10
yes
CUSTOMER_NAME
T001L.KUNNR Account number of customer
NVARCSTR
35
yes
DISTRIBTN_CHANNEL _DESCR DISTRIBTN_CHANNEL _ID
T001L.VTWEG Distribution channel
NVARCSTR
20
yes
T001L.VTWEG Distribution channel
NVARCSTR
yes
DIVISION_DESCR
Lookip TSPAT.VTEXT-Division Description
NVARCSTR
20
yes
DIVISION_ID
T001L.SPART Division
NVARCSTR
yes
GOODS_MVMT_AUT HORIZTN_FLAG HANDLNG_UNIT_FLA G
T001L.XBLGO Storage location authorization for goods movements active
NVARCSTR
yes
10
T001L.XHUPF Handling unit requirement
NVARCSTR
yes
11
LOAD_DATE
DATETIME
24
yes
12
LOAD_TIME
NVARCSTR
yes
13
MRP_DESCR
Lookup T001L.DISKZ MRP Indicator Description
NVARCSTR
60
yes
14
MRP_ID
T001L.DISKZ Storage location MRP indicator
NVARCSTR
yes
15
NEG_STOCK_FLAG
Negative stocks allowed in storage location
NVARCSTR
yes
16
PLANT_ID
PK
T001L.WERKS Plant
NVARCSTR
no
114
17
PLANT_NAME
T001W.NAME1 - Plant Name
NVARCSTR
30
yes
18
PURCH_ORG_ID
T001W.EKORG -Purchasing Organization Code
NVARCSTR
yes
19
PURCH_ORG_NAME
Lookup on Purchasing org Name T024E
NVARCSTR
20
yes
20
RESOURCE_ALLOC TN_FLAG
T001L.XRESS Storage location is allocated to resource (storage resource)
NVARCSTR
yes
21
SALES_ORG_DESCR
T001L.VKORG Sales organization
NVARCSTR
20
yes
22
SALES_ORG_ID
T001L.VKORG Sales organization
NVARCSTR
yes
23
SHIP_POINT_DESCR
T001L.VSTEL Shipping point/receiving point
NVARCSTR
30
yes
24
SHIP_POINT_ID
T001L.VSTEL Shipping point/receiving point
NVARCSTR
yes
25
STORAGE_LOCATN _DESCR STORAGE_LOCATN_F ULL_NAME STORAGE_LOCATN_I PK D STORAGE_LOCATN_I D_PARTNER
T001L.LGOBE Description of storage location
NVARCSTR
16
yes
26
Concatenation of Storage Location ID and Description
NVARCSTR
26
yes
27
T001L.LGORT Storage location
NVARCSTR
no
28
T001L.PARLG Partner storage location of the handling unit
NVARCSTR
yes
29
VALUATN_AREA_ID
T001W.BWKEY - Valuation area Code
NVARCSTR
yes
30
VENDOR_ID
T001L.LIFNR Vendor account number
NVARCSTR
10
yes
31
VENDOR_NAME
T001L.LIFNR Vendor account number
NVARCSTR
35
yes
115
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
116
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
117
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
118

Sales RM User Guide

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Sales RM User Guide

Caricato da

Copyright:

Formati disponibili

SAP BusinessObjects Sales 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

Sales (SD-SLS) Shipping (SD-SHP) Billing (SD-BIL)

Overview What you can do with this Rapid Mart

Overview Supported analyses

Backlog Schedule Lines

By Delivery By Billing Planning

Overview Supported analyses

Business function Billing

Types of analysis Discounting

Measures available in the Rapid Mart

By Schedule Line or Delivery

Invalid Documents by Sales Order or Billing

Overview Related Rapid Marts

Related Rapid Marts

Sales orders for make-to-order materials are included in the:

These linkages give a complete view of the manufacturing process.

Sales orders for Purchased materials are tracked in the:

Overview Related Rapid Marts

Subject Areas Overview

Sales Order Section

quotes, inquiries, contracts, scheduling agreements.

Subject Areas Sales Order Section

Subject Areas Sales Order Section

Rapid Mart processing

Subject Areas Sales Order Section

Fact Table Fields

Subject Areas Sales Order Section

AMT_STD_COST_GBL AMT_STD_COST_TRX AMT_SUBTTL_01_GBL AMT_SUBTTL_01_TRX

Subject Areas Sales Order Section

Subject Areas Sales Order Section

Subject Areas Sales Order Section

Col. Name CUSTOMER_ID_BILLT O

Description VBPA-KUNNR - Bill-to Customer Number (lookup)

Subject Areas Sales Order Section

Rapid Mart Data

Subject Areas Sales Order Section

Typical queries include:

Subject Areas Backlog Section

Subject Areas Backlog Section

Rapid Mart processing

Subject Areas Backlog Section

Fact Table Fields

DELIVERY_FACT.QTY_DELIV_SLSUOM - Actually Delivered Qty SALES_ORDER_FACT.QTY_ORDER_SLSUOM Cumulative Sales Order Qty

Rapid Mart data

Subject Areas Backlog Section

Typical queries include:

Subject Areas Schedule Lines Section

Schedule Lines Section

Subject Areas Schedule Lines Section