Xi3 RM Sap Ps Ug en

SAP BusinessObjects Project Systems
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 9
What is a Rapid Mart? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Rapid Marts packages accelerate Time to Value . . . . . . . . . . . . . . . . 11
SAP BusinessObjects Rapid Marts packages architecture . . . . . . . . . 12
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Chapter 2 Overview 15
What you can do with this Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Supported analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Dimensions available to support these analyses . . . . . . . . . . . . . . . . . 20
Related Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Components shared with other SAP BusinessObjects Rapid Marts . . 20
Project Systems Rapid Mart schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Where the Rapid Mart fits in Project Activities . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 3 Subject Areas 25

Projects (PS) Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Work Breakdown Structure / Project Elements . . . . . . . . . . . . . . . . . . 29
Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Network Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Production Resource Tools (PRT) Assignments . . . . . . . . . . . . . . . . . 33
Milestones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Project Costing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Milestone Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Rapid Mart Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Rapid Mart Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Network Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide 3
Contents
Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Network Relationship Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Project Cost Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
PRT Assignment Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Chapter 4 Reports 73
Milestone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Network (Production) Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Network Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Project Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
PRT Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Order Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
SAP Master Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
4 SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Contents
Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
Chapter 5 Universe 143

Universe Design Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
Universe Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Universe Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Join Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Hierarchies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Geographic Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Time Dimension and Fiscal Period Hierarchies . . . . . . . . . . . . . . . . . 151
Material Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Horizontal & Vertical Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Project System Specific Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Accounting Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Additional Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
SAP Project System Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Common Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Milestone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Network Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Network Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Project Cost Summary (Horizontal) . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Project Cost Summary (Vertical) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
PRT Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Order Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Filters & Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
SAP Master Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Contents
Splitting the SAP Project System Universe . . . . . . . . . . . . . . . . . . . . . 227
Chapter 6 Installing the Rapid Mart 229

Preparing Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Preparing Target Database Environment . . . . . . . . . . . . . . . . . . . . . . 235
Preparing Source Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Preparing BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . 236
Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Create Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Renaming the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Import ATL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Adjusting the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Using Auxiliary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Using ABAP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Import Wizard for Reporting Content BIAR File . . . . . . . . . . . . . . . . . 260
Creating Universe Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Chapter 7 Using the Rapid Mart 279

Recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Data Services automatic recovery feature . . . . . . . . . . . . . . . . . . . . . 280
Rapid Mart recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Execution status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
The execution status table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
The execution status API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Executing a job with the Reset option . . . . . . . . . . . . . . . . . . . . . . . . . 284
Extraction, transformation and loading process . . . . . . . . . . . . . . . . . . . . 284
Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Global Variable Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286
Used in All Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Used in 2 to 10 Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Used in Only 1 Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Setting Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Contents
Executing the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Initial (First) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Incremental (Delta) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . 318
Customizing the Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320
Chapter 8 Technical Implementation 321

Milestone Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Initial (First) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Incremental (Delta) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Network Order Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Network Relationship Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Project Cost Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
PRT Assignment Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Rolling Totals Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Optimization Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Table Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Data Transfer Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Hierarchy Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Dealing with NULL values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Fact Table Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Fiscal Periods & Time Dim Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Chapter 9 Documentation References 363

Data Services Documentation References . . . . . . . . . . . . . . . . . . . . . . . 364
BusinessObjects Enterprise Documentation References . . . . . . . . . . . . 364
Appendix A Rapid Mart Data Schema 367
Contents
Introduction
chapter
1 Introduction
What is a Rapid Mart?

SAP BusinessObjects Rapid Marts packages are blueprints for building data
marts with SAP BusinessObjects technology:
• Data Services
• Universe Designer
• Web Intelligence.
Rapid Marts packages deliver jump-start ETL (extract, transform & load)
mappings, schema, and initial reporting content, accelerating the deployment
of BI (business intelligence) for enterprise applications from SAP, PeopleSoft,
Oracle, and Siebel.
Each Rapid Mart is designed to address the reporting needs of a specific
business area (or department) like accounting, sales, or purchasing. A
component-based framework allows conducting analysis across these
selected business areas by combining different packages within the same
source application suite.
Rapid Marts focus on basic standard configuration of the enterprise
applications. They are country and industry neutral templates meant to be
easily modified and extended to suit customer specific application
implementation and reporting needs.
Rapid Marts incorporate best practices, and provide easily modifiable
templates. With Rapid Marts total development time of a data mart solution is
greatly reduced.
Each customer situation is different. You will probably encounter one or more
of these:
• Customizations you have made to SAP solutions the Rapid Mart does not
cover.
• Standard SAP solutions data fields important for your specific business,
but not included in the Rapid Mart templates.
• Optimization and performance challenges unique to your environment.
• Reporting requirements not covered within the Rapid Mart template
reports.
Rapid Marts are flexible templates that you can adjust to account for these
unique situations. It is expected that some customization and optimization will
be needed to suit your individual environment. Rapid Marts are not an
out-of-the-box solution.
Introduction
What is a Rapid Mart? 1
BI tools and analytic tools can access Rapid Mart data through SQL queries.
Rapid Marts can be implemented individually, or in any combination, to form a
single platform that delivers the infrastructure for your company’s internal and
external information needs. They can also serve as a staging area for
enterprise analytic applications.
Rapid Marts provide your business with an accelerated time to value through
rapid BI deployments because you can implement them quickly and easily
customize them to meet specific analytic requirements.
Rapid Marts packages accelerate Time to 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
Operational Suite:
• SAP BusinessObjects Inventory Rapid Mart, version for SAP solutions
• SAP BusinessObjects Purchasing Rapid Mart, version for SAP solutions
• SAP BusinessObjects Sales Rapid Mart, version for SAP solutions
Manufacturing Suite:
• SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP
solutions
• SAP BusinessObjects Production Planning Rapid Mart, version for SAP
solutions
• SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions
Human Capital Management (HCM) Suite:
• SAP BusinessObjects Human Resources Rapid Mart, version for SAP
solutions
1 Introduction
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:
Introduction
About this document 1
• Data Movement Jobs - packaged source-to-target mappings and data
transformations. Each job is designed to perform initial and incremental
data movement;
• Data Model & Schema - set of data mart database objects designed with
dimensional data modeling approach. Rapid Marts packages for SAP
solutions has a single integrated data model. The schema are available
for Oracle, SQL Server IBM DB2, and Teradata;
• Semantic Layer (Universes) - SAP BusinessObjects metadata packages
for efficient query generation. There can be one or more universes per
Rapid Mart. Each universe is developed using Rapid Marts design
principles to ensure compatibility, code readability, and component
re-use. In addition, there is one Master universe for
development/maintenance of multiple use objects (like Customer,
Material, Currency, etc.);
• Reports (Samples) - set of 15-20 Web Intelligence reports per Rapid
Mart. They represent answers to mostly asked business questions (for
example, in the SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions - 'What is the monthly Revenue trend by Division for this
year?'). The reports are developed using Rapid Mart color/layout
templates. Reports are examples of Web Intelligence best practice
development (trends, listing, guided analysis, roll ups and downs, etc.).
About this document

This document describes the SAP BusinessObjects Project Systems Rapid
Mart, version for SAP solutions. This document contains information for a
variety of users—information that helps you understand the use of the Rapid
Mart, the data in the Rapid Mart, the reports you can create with the Rapid
Mart, and how to use and update the Rapid Mart.
This document contains the following chapters:
• Chapter 2: Overview — Describes the business problems you can solve
and the types of analyses you can do with this Rapid Mart
• Chapter 3: Subject Areas — Contains detailed information about each
componentized 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 the SAP BusinessObjects Universes
upon which the reports are built.
1 Introduction
About this document
• 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 setting parameters and considerations
you need to make when customizing the Rapid Mart
• Chapter 8: Technical Implementation —Describes each componentized
section and the work flows that run to load that section
• Chapter 9: Documentation References — Information about where to find
related to the Rapid Mart technical documentation on Data Services and
BusinessObjects Enterprise
• Appendix A: Rapid Mart Data Schema — Contains a detailed list of the
tables and views in the Rapid Mart
Overview
chapter
2 Overview
Overview
Overview
This chapter describes the business problems you can solve with the SAP
BusinessObjects Project Systems 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
• Project Systems Rapid Mart schema
• Where the Rapid Mart fits in Project Activities
What you can do with this Rapid Mart

The SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions supports analysis of project information entered within the Project
System (PS) module. Both large scale projects, such as building a factory,
and small-scale projects, such as organizing a trade fair, require precise
planning of the many detailed activities involved. The project manager has
the job of ensuring that the project is executed efficiently, on time, and within
budget - which he or she achieves by ensuring that the required resources
and funds are available as and when needed. The SAP BusinessObjects
Project Systems Rapid Mart, version for SAP solutions provides a framework
for monitoring projects progress, resources, costs and revenue.
solutions is made up of several componentized sections. Each section
supports a subject related to project analysis:
• Milestone Section — In general milestones are used to mark the
transition between various phases or departments. You can also use
Milestones for other tasks and functions in the Project System. You can
create milestones for activities and WBS elements. They can be used for
the following tasks:
• Milestone Trend Analysis
• Earned Value Analysis
• Billing Plan
Overview
What you can do with this Rapid Mart 2
• Network Order Section — A network can represent the sequence of
activities in a project or the sequence of a single activity within a project.
You can graphically display various structural elements of a project and
their interdependencies in the Project System.
The essential components of a network are stored as Network Orders in
SAP solutions. The network order is a category of internal order. The
Activities of the network order are analogous to the operations on the
internal order.
• Network Relationship Section — There is usually a reason for a
specific sequence of activities in a network. For example, there may be
technical dependencies between individual activities. These
dependencies are represented by relationships in which one activity is
the predecessor or the successor of another activity.
• Project Cost Summary Section — You use Project Costing to plan,
monitor, and control project costs, thereby achieving comprehensive cost
accounting.
Project Costing features include:
• Cost planning in various degrees of detail
• Automatic cost calculation wherever there are price and quantity
structures
• Funds management, effected by means of budget allocation
• Integration of project costs with Enterprise Controlling, such as
reconciliation with cost center accounting
• PRT Assignment Section — Unlike machines and fixed assets,
production resources and tools (PRTs) are movable (not stationary)
operating resources that are required to perform an activity and can be
used repeatedly. For example, PRTs include documents, engineering
drawings, and measurement instruments.
Chapter 3: Subject Areas discusses each of these sections in more detail and
how to link them together for a complete Project System Analysis solution.
2 Overview
Supported analyses
Supported analyses
solutions supports several types of analyses:
Business function Types of analysis Details available in the

Rapid Mart
Project Costing Project Balance Trend Displays the project balance
Comparison trend data for the selected
Company Code, Fiscal
Years, and Parent Project
Element.
Project Balance Trend by View actual project balance
Period period trends for the
selected Company Code,
Parent Project Element, and
Fiscal Year-Period range.
Results are grouped by
Project Element Hierarchy
Project Balance Variance View Actual, Planned (or
Trend Budget), Variance, and
Variance% period trends for
a specific Company Code,
Parent Project Element,
Fiscal Year, and Ledger
Version.
Project Cost YTD Trend View Actual YTD trends for
Analysis a specific Company Code,
Parent Project Element,
Fiscal Year, and Ledger
Version.
Project Cost Period View Actual, Planned (or
Comparison Budget), Variance Project
Element hierarchy
comparison for selected
Fiscal Year-Periods and
Ledger Version.
Overview
Supported analyses 2
Business function Types of analysis Details available in the
Rapid Mart
Network Orders (Project Network Order Details View network (production)
Orders) order listing, network order
details, and trend by
Business Area for the
selected Plant and Calendar
Year.
Network Order Analysis View network (production)
order analysis for selected
Plant and Calendar Year.
View Summary, Trend by
Business Area, and Top 10
Materials.
Milestones Milestone Overview Displays Milestone
information for the selected
Project (and Project
Elements).
Milestone Statistics View Milestone performance
statistics by Plant for the
selected Company Code.
Network Relationships Network Relationship View Network Relationship
Overview overview for the selected
Project (or Network - also
called Internal Order Id) and
Operation Numbers (also
called Activities).
Production Resource & Tools PRT Assignment Listing View PRT assignments for
(PRT) the selected Operation
Routing Id.
PRT Details View PRT details for the
selected PRT (by PRT
Name).
Activity (Project Order Project Structure (Activity) View project structure for
Operations) Planning the selected Project Id.
2 Overview
Related Rapid Marts
Dimensions available to support these analyses

Reporting dimensions available in the Rapid Mart include project, project
element, project element hierarchies, operations, work centers, capacities,
material master data, plant, storage location, currency, account assignment,
and time-related dimensions such as fiscal period, calendar date, month, and
quarter.
Related Rapid Marts

Components of the SAP BusinessObjects Project Systems Rapid Mart,
version for SAP solutions are related to other SAP BusinessObjects Rapid
Mart components, as follows:
• External procurement information, from purchase requisitions to
purchase orders, is included in the Purchasing SAP BusinessObjects
Purchasing Rapid Mart, version for SAP solutions.
• Revenue information resulting from sales orders can be found in the
Sales Analysis SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions.
• Cost Center & Cost Element Accounting information is included in the
Cost Center SAP BusinessObjects Cost Center Rapid Mart, version for
SAP solutions.
Components shared with other SAP BusinessObjects Rapid

Marts
The same components can be used in multiple Rapid Marts. For example, a
component that extracts information about materials bought, produced, and
sold is needed for a Rapid Mart that supports sales analysis and also for a
Rapid Mart that supports inventory analysis. Work flows that extract star
schema “dimensions” are components. You can add a component to any
Rapid Mart using a simple import procedure.
A Data Services job can include multiple instances of a component. For
example, each section includes all the required dimension components.
Therefore, a job with several sections may include several instances of a
particular dimension component. Components are set to execute only once
within a job. This “execute once” feature ensures that shared components do
not cause duplicate data extraction from SAP solutions. For more information
about the “execute once” feature, see the Data Integrator/Data Services
Designer Guide.
Overview
Related Rapid Marts 2
Each of the sections listed in “What you can do with this Rapid Mart” on
page 16 are considered components. You can identify a component within a
Data Services job by a “C_” prefix before its name. For example, the
component that contains PRT (Project Resource / Tools) Assignments and
the associated reporting dimensions is named
C_PRTAssignmentSection_SAP.
2 Overview
Project Systems Rapid Mart schema
Project Systems Rapid Mart schema

The following diagram shows an overview of the SAP BusinessObjects
Project Systems Rapid Mart, version for SAP solutions presented as a Star
Schema.
Overview
Project Systems Rapid Mart schema 2
The additional diagram shows the associated hierarchy and auxiliary tables
used by the Rapid Mart.
The following chapter describes each component and reporting dimensions in

more detail.
2 Overview
Where the Rapid Mart fits in Project Activities
Where the Rapid Mart fits in Project

Activities
solutions gives an overview of the functions and processes in SAP solutions
designed to support your Project related activities. It is intended for
decision-makers and personnel involved in developing and implementing
projects throughout your enterprise.
Subject Areas
chapter
3 Subject Areas
Overview
Overview
Each section in the SAP BusinessObjects Project Systems Rapid Mart,
version for SAP solutions pertains to a particular subject area. This chapter
describes each section and the processes each section captures. But first,
additional section “Projects (PS) Module Overview” defines the scope and
basic functionality within the SAP solutions Project System (PS) module
The information in this chapter is useful for readers who use the Rapid Mart to
design and support a real-time system, such as a Web application, and need
to understand the data in the Rapid Mart and how it relates to SAP solutions.
This chapter discusses:
• Projects (PS) Module Overview
• Milestone Section
• Network Order Section
• Network Relationship Section
• Project Cost Summary Section
• PRT Assignment Section
Projects (PS) Module Overview

Both large scale projects, such as building a factory, and small-scale projects,
such as organizing a trade fair, require precise planning of the many detailed
activities involved. The project manager has the job of ensuring that the
project is executed efficiently, on time, and within budget - which he or she
achieves by ensuring that the required resources and funds are available as
and when needed.
Projects are generally part of the internal processes of a company. To be able
to control all tasks in project execution, you need an organizational form that
is specific to the project and which is shared by all departments involved.
Before you can carry out a project in its entirety, the project goals must be
precisely described and the project activities to be carried out must be
structured. A clear, unambiguous project structure is the basis for successful
project planning, monitoring, and control.
You structure your project per the following points of view:
• By structures, using a work breakdown structure (WBS)
• By process, using individual activities (work packages)
Project managers usually distinguish between two types of project:
• Externally financed projects
Subject Areas
Projects (PS) Module Overview 3
• Customer projects
• Internally financed projects
• Overhead cost projects
• Capital investment projects
The high degree of integration between the Project System (PS) and other
application components means that you can plan, execute, and account for
projects as part of your normal commercial procedures. This means the
Project System has constant access to data in all the departments involved in
the project.
The Project System guarantees close and constant monitoring of all aspects
of your project. This includes both technical and commercial aspects of the
project.
Each project starts with the definition and classification of the structures
required for processing and the incorporation of these into the existing
enterprise structure.
The Project System has no organizational structures of its own; you
incorporate it into the existing structure by making assignments to the
organizational units in Accounting and Logistics. It is this which enables the
Project System to present data clearly and in many different ways.
3 Subject Areas
Project Structure Overview
Subject Areas
In the Rapid Mart, the various components of project structure are
represented:
• Projects - are represented in the Project Dimension.
• WBS Elements - are represented by the Project Element Dimension and
Project Element Hierarchy.
• Networks - are represented by Network Orders
• Activities - are represented by the Order Operations Dimension
• Material Components - are represented by the Material Dimension and
Material by Plant Dimension
• Many of the other items shown in the graphic above are also dimensions,
such as:
• Profit Center
• Company Code
• Business Area
• Plant
• Storage Location
• etc.
Additional Information on the more important components is given below:
Work Breakdown Structure / Project Elements

The Work Breakdown Structure (WBS) is a model of the work to be performed
in a project organized in a hierarchical structure. These are also called the
Project Elements. The WBS is an important tool which helps you keep an
overview of the project:
• It forms the basis for organization and coordination in the project.
• It shows the amount of work, the time required, and the costs involved in
the project.
It is the functional basis for further planning steps in a project, such as
process planning, cost planning, scheduling, date and capacity planning, or
costing, as well as project control. The project structure can be represented
according to different criteria:
• By phase (logic-oriented)
• By function (function-oriented)
• By object (object-oriented)
In a work breakdown structure (WBS), you describe the individual tasks and
activities in the project as individual elements in a hierarchy.
3 Subject Areas
Depending on the phase of your project, you continue to break down the
tasks and activities in your project, step-by-step, until you reach the level of
detail necessary to carry it out.
The individual elements represent activities within the work breakdown

structure. The elements are called work breakdown structure elements (WBS
Elements) in the Project System. WBS elements can be:
• Tasks
• Partial tasks which are subdivided further
• Work packages
Networks
A network can represent the sequence of activities in a project or the
sequence of a single activity within a project. You can graphically display
various structural elements of a project and their interdependencies in the
Project System.
Subject Areas
The essential components of a network are stored as Network Orders in SAP
solutions. The network order is a category of internal order. The Activities of
the network order are analogous to the operations on the order.
The essential components of a network are:
• Activities
• Relationships between the activities
• Activities
The following graphic shows you a network with activities and the different
types of relationships.
Activities
These are analogous to the operations on a network order. The most
important data describing an Activity in the Project System are:
• Work center in which the activity is to be carried out
• Duration of the activity
• Start and finish dates for the activity
• Resources required to carry out the activity
• Texts and documents describing the activity
3 Subject Areas
Network Relationships
There is usually a reason for a specific sequence of activities in a network.
For example, there may be technical dependencies between individual
activities. These dependencies are represented by relationships in which one
activity is the predecessor or the successor of another activity.
The relationship type specifies how the individual activities are linked with
each other:
• Finish - Start (FS) Relationship: Relationship between the finish of one
activity and the start of its successor.
• Start - Start (SS) Relationship: Relationship between the start of one

activity and the start of its successor.
• Finish - Finish (FF) Relationship: Relationship between the finish of

one activity and the finish of its successor.
Subject Areas
• Start - Finish (SF) Relationship: Relationship between the start of one
activity and the finish of its successor.
in the Rapid Mart, these are represented in the Network Relationships

section.
Production Resource Tools (PRT) Assignments

Unlike machines and fixed assets, production resources and tools (PRTs) are
movable (not stationary) operating resources that are required to perform an
activity and can be used repeatedly. For example, PRTs include documents,
engineering drawings, and measurement instruments.
You can assign production resources/tools to internal and external activities.
You use the assignment to determine:
• The quantity
• The operating time
• The dates
of the PRTs required to carry out the activity.
There are several categories of production resources and tools in the SAP
solutions system. The category determines the characteristics and business
functions that a PRT can have. You can create production resources/tools
with the following categories:
• Material PRT - A material PRT has its own material master record with
the view “PRT”. A material PRT can be procured, that is, it can either be
purchased or produced. You can also keep it in stock and track both its
value and quantity.
• Miscellaneous PRT - A miscellaneous PRT has its own PRT master
record and can neither be procured nor kept in stock.
3 Subject Areas
• Document PRT - A document PRT has its own document info record,
(for example engineering drawings or NC programs).You can manage
these PRTs using the SAP solutions document management.
Note: In the Project System you can assign documents directly to
activities. Consequently you will not use this type of PRT very often.
• Equipment PRT - An equipment PRT has its own equipment master
record and has the full equipment functionality. This category is
particularly useful for those production resources or tools which you must
maintain yourself or which must be serviced at regular intervals. With the
equipment category, you can furnish proof of service or usage values for
the production resource/tool.
Milestones
In general milestones are used to mark the transition between various phases
or departments. You can also use Milestones for other tasks and functions in
the Project System. You can create milestones for activities and WBS
elements. They can be used for the following tasks:
• Milestone Trend Analysis (MTA) - a simple and effective method of
controlling dates in a project. The milestone dates on different report
dates are compared. In the graphical MTA chart you recognize trends
and delays immediately.
• Earned Value Analysis - using the milestone technique. Each milestone
represents the portion of the work that is completed in an activity or in a
WBS element.
• Billing Plan - A milestone is linked with a date in the billing plan. When
the milestone is reached, the actual date of the milestone is copied into
the billing plan.
Project Costing
You use this component to plan, monitor, and control project costs, thereby
achieving comprehensive cost accounting. The component is thoroughly
integrated with other components, such as:
• CO - Controlling
• FI - Financial Accounting
• PP - Production Planning and Control
• MM - Materials Management
The component contains the following functions:
Subject Areas
Milestone Section 3
structures
reconciliation with cost center accounting
In the Rapid Mart, the Project Costing Section details the costs associated
with a project.
Milestone Section
Milestones are used in the Project System to designate significant events or
the completion of a project phase.
• For progress analysis
• As release stop indicators
• To trigger predefined functions and workflow tasks
Technically speaking, a milestone is a date where the start and end times are
identical.
Milestones exist as a subset of a task list (or routing) and order operation
within SAP solutions. The source tables for Milestones in SAP solutions are:
• MLST - Milestone
• PLKO - Task list - header
• PLPO - Task list - operation/activity
• AFVC - Operation within an order
In the Rapid Mart, the target table is MILESTONE_FACT. We choose only the
task list and operation records that have a corresponding milestone record.
Rapid Mart Processing

The section captures the following dimensional attributes and their associated
dimension tables:
Attribute Name Dimension Tables

Activity & Hierarchy ACTIVITY, ACTIVITY_HIER,
ACTIVITY_HIER_HZ,
ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
Chart Of Accounts CHART_OF_ACCOUNTS
Company Code COMPANY_CODE
3 Subject Areas
Milestone Section

Control Key CONTROL_KEY
Controlling Area CONTROLLING_AREA
Cost Element & Hierarchy COST_ELEMENT,
COST_ELEMENT_HIER,
COST_ELEMENT_HIER_HZ,
COST_ELEMENT_HIER_VR,
COST_ELEMENT_HIER_BAD
Document Category DOCUMENT_CATEGORY
Internal Order & Hierarchy INTERNAL_ORDER,
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
Milestone Usage MILESTONE_USAGE
Network Profile NETWORK_PROFILE
Order Operation ORDER_OPERATION
Plant PLANT
Project PROJECT
Project Element & Hierarchy PROJECT_ELEMENT,
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ,
PROJECT_ELEMENT_HIER_VR,
PROJECT_ELEMENT_HIER_BAD
Purchasing Organization PURCH_ORGANIZATION
Reference Date Key REFERENCE_DATE_KEY
Routing ROUTING
Routing Operation ROUTING_OPERATION
Status Profile STATUS_PROFILE
Task List Type TASK_LIST_TYPE
Time Dimension TIME_DIM
Unit Of Measure UNIT_OF_MEASURE
Subject Areas
Milestone Section 3
Work Center & Hierarchy WORK_CENTER,
WORK_CENTER_HIER,
WORK_CENTER_HIER_HZ,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_BAD
Work Center Category WORK_CENTER_CATEGORY
Fact table Fields

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

DAYS_ACTL_DURTN Number of Days between MLST.LST_ACTDT
- Actual date (Milestone met) and
MLST.DATEH - Milestone created on
DAYS_DIFF_FIXED_BASIC Number of Days between Fixed Basic and
Actual Milestone end
DAYS_DIFF_FIXED_FCST Number of Days between Fixed Forecast and
DAYS_DIFF_SCHED_BASIC Number of Days between Scheduled Basic
and Actual Milestone end
DAYS_DIFF_SCHED_FCST Number of Days between Scheduled Forecast
DAYS_SCHED_DURTN Number of Days between MLST.TEDAT -
Scheduled milestone date (Basic) and
HOURS_ACTL_DURTN Number of Hours between
MLST.LST_ACTDT - Actual date (Milestone
met) and MLST.DATEH - Milestone created
on
HOURS_DIFF_FIXED_BASIC Number of Hours between Fixed Basic and
HOURS_DIFF_FIXED_FCST Number of Hours between Fixed Forecast
HOURS_DIFF_SCHED_BASIC Number of Hours between Scheduled Basic
3 Subject Areas
Milestone Section

HOURS_DIFF_SCHED_FCST Number of Hours between Scheduled
Forecast and Actual Milestone end
HOURS_SCHED_DURTN Number of Hours between MLST.TEDAT -
PRCNT_COMPLETE MLST.LST_FERTG - Percentage of
completion (%)
PRCNT_OFFSET MLST.PRCNT - Percentage offset of
milestone to activity date
QTY_OFFSET MLST.DELTA - Offset for milestone date
SECS_ACTL_DURTN Number of Seconds between
met) and MLST.DATEH - Milestone created
on
SECS_DIFF_FIXED_BASIC Number of Seconds between Fixed Basic and
SECS_DIFF_FIXED_FCST Number of Seconds between Fixed Forecast
SECS_DIFF_SCHED_BASIC Number of Seconds between Scheduled
Basic and Actual Milestone end
SECS_DIFF_SCHED_FCST Number of Seconds between Scheduled
Forecast and Actual Milestone end
SECS_SCHED_DURTN Number of Seconds between MLST.TEDAT -
Additionally, several “flags” are employed to capture milestone status:
COLUMN_NAME COMMENTS
COMPLETE_FLAG Calculated based on
MLST.LST_FERTG - Percentage of
completion (%) - if 100% then 1, else
0
CURRENT_FLAG 1- the record is current
FUNCTION_FLAG MLST.KZ_WFLOW - Indicator:
Milestone is used for milestone
functions
LATEST_DATE_FLAG MLST.LATED- Indicator: Latest
dates
Subject Areas
Milestone Section 3
OFFSET_TO_FINISH_FLAG MLST.DLTAS - Ind: Reference for
offset (start/finish activity date)
PROGRESS_ANALYSIS_FLAG MLST.KZ_LSTWR - Milestone
relevant for progress analysis
RELEASE_STOP_FLAG MLST.KZ_FRMST - Release stop
indicator
SALES_DOC_DATE_FLAG MLST.KZ_FAKTP - Milestone is
relevant for date in sales document
TREND_ANALYSIS_FLAG MLST.KZ_TREND - Milestone
relevant for trend analysis
Rapid Mart Data

The following diagram shows the tables in the Milestone section organized as
a Star Schema:
With the tables in this section, you can analyze milestones along several
dimensions:
• Activity & Hierarchy
• Chart Of Accounts
• Company Code
• Control Key
• Controlling Area
3 Subject Areas
Network Order Section
• Cost Element & Hierarchy

• Document Category
• Internal Order & Hierarchy
• Milestone Usage
• Network Profile
• Order Operation
• Plant
• Project
• Project Element & Hierarchy
• Purchasing Organization
• Reference Date Key
• Routing
• Routing Operation
• Status Profile
• Task List Type
• Time Dimension
• Unit Of Measure
• Work Center & Hierarchy
• Work Center Category
Typical queries for this section include:
• What milestones are due on my project by month for the next year?
• Which milestones have I missed?
• How late or early are we hitting our milestones?
• Compare the percent of milestones “on-time” for one project with another.
• Which Project Elements (WBS) are consistently associated with missed
milestones?

A network order is a special type of production order used for Projects in the
SAP solutions system.
Network orders are a shared component. They are used in the following
Rapid Marts:
solutions - Extracts only Order Category “10” (Standard Production
Orders).
Subject Areas
Network Order Section 3
solutions - Extracts only Order Category “20” (Network Orders)
There is more information on how this shared component is used in Chapter
8: Technical Implementation of this user guide.
Network orders are source from these SAP solutions tables:
• AUFK - Order master data
• AFKO - Order header data PP orders
• AFPO - Order item
The target table for Production Orders is:
• PRODUCTION_ORDER_FACT

dimension tables:

Account Assignment Category ACCT_ASSIGNMENT_CATEGORY
Business Area BUSINESS_AREA
Cost Center & Hierarchy COST_CENTER,
COST_CENTER_HIER,
COST_CENTER_HIER_HZ,
COST_CENTER_HIER_VR,
COST_CENTER_HIER_BAD
COST_ELEMENT_HIER,
Document Type DOCUMENT_TYPE &
DOCUMENT_CATEGORY
Functional Area & Hierarchy FUNCTIONAL_AREA,
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BAD
3 Subject Areas

Internal Order Status INTERNAL_ORDER_STATUS
Material Batch MATERIAL_BATCH
Material By Plant MATERIAL_BY_PLANT
Material Group MATERIAL_GROUP
Material Type MATERIAL_TYPE
Material, Product Hierarchy MATERIAL,
PRODUCT_HIERARCHY
Monetary Currency CURRENCY
MRP Controller MRP_CONTROLLER
Object Class OBJECT_CLASS
Object Number Type OBJECT_NUMBER_TYPE
Object Status & Hierarchy OBJECT_STATUS,
OBJECT_STATUS_HZ
Plant PLANT
Plant Location PLANT_LOCATION
Profit Center & Hierarchy PROFIT_CENTER,
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
Project PROJECT
Routing ROUTING
Service Person SERVICE_PERSON
Special Procurement Type SPECIAL_PROCUREMENT_TYPE
Subject Areas
Storage Location STORAGE_LOCATION
Task List Usage TASK_LIST_USAGE
Valuation Area VALUATION_AREA
Fact Table Fields

Important measures for Production Orders are both quantity and time
oriented:

DAYS_COMPLT_ACTL Number of Days to actually complete
a service order (Calculated)
DAYS_COMPLT_BASIC Number of Days to Basic complete a
service order (Calculated)
DAYS_COMPLT_FCST Number of Forecast Days to com-
plete a service order (Calculated)
DAYS_COMPLT_SCHED Number of Days scheduled to com-
DAYS_GR_PROCESS AFPO.WEBAZ -Goods receipt pro-
cessing time in days
DAYS_RELEASE_ACTL Number of Days to actually release a
DAYS_RELEASE_SCHED Number of Days scheduled to
release a service order (Calculated)
HOURS_COMPLT_BASIC Number of Hours to Basic complete a
HOURS_COMPLT_FCST Number of Forecast Hours to com-
HOURS_COMPLT_SCHED Number of Hours scheduled to com-
MINS_COMPLT_ACTL Number of Minutes to actually com-
MINS_COMPLT_BASIC Number of Minutes to Basic complete
a service order (Calculated)
3 Subject Areas

MINS_COMPLT_FCST Number of Forecast Minutes to com-
MINS_COMPLT_SCHED Number of Minutes scheduled to
complete a service order (Calculated)
QTY AFPO.PSMNG - Order item quantity
QTY_PROD AFPO.WEMNG - Quantity of goods
produced and received for the order
item
QTY_SCRAP AFPO.PSAMG - Scrap quantity in
item
Rapid Mart data

The following diagram shows the tables in the Network order section
organized as a Star Schema.
Subject Areas
Additionally, these hierarchies are associated with Network orders:
With the tables in this section you can analyze Network Orders along several
dimensions:
• Account Assignment Category
• Business Area
• Company Code
• Cost Center & Hierarchy
• Document Type
• Functional Area & Hierarchy
• Internal Order Status
• Material Batch
• Material By Plant
• Material Group
• Material Type
• Material, Product Hierarchy
• Monetary Currency
• MRP Controller
• Object Class
3 Subject Areas
Network Relationship Section
• Object Number Type

• Object Status & Hierarchy
• Plant
• Plant Location
• Profit Center & Hierarchy
• Project
• Routing
• Service Person
• Special Procurement Type
• Task List Type
• Task List Usage
• Time Dimension
• Unit Of Measure
• Valuation Area
• What is the average time to complete a network order?
• Is one plant faster at completing network orders than another?
• Which network orders have the lowest / highest on-time completion?
• Are my network orders for a certain functional area evenly distributed
between plants?
• Which Projects have the greatest / lowest shares of network orders in a
given plant?

A way of describing the link between the start and finish points of two
activities in a network. Relationships determine the sequence of activities.
The SAP solutions system includes the following relationships:
• SS relationship (Start - Start)
• FF relationship (Finish - Finish)
• SF relationship (Start - Finish)
• FS relationship (Finish - Start)
Subject Areas
Network Relationship Section 3
A Network Relationship is a way of linking related Order Operations by one
of the four methods described above.
Network Relationships are sourced from these SAP solutions tables:
• AFAB - Network - Relationships
The target table for Network Relationships is:
• NETWORK_RELATIONSHIP_FACT

dimension tables:

Object Status OBJECT_STATUS,
OBJECT_STATUS_HZ
Plant PLANT
PROFIT_CENTER_HIER,
3 Subject Areas

Project PROJECT
Relationship Type RELATIONSHIP_TYPE
WORK_CENTER_HIER,
Fact Table Fields

Important measures for Network Relationships are time oriented
DAYS_DURTN_EARLST Number of Days for Network Relationship
based on Earliest start/end dates
DAYS_DURTN_LATEST Number of Days for Network Relationship
based on Latest start/end dates
DAYS_DURTN_MAX Max Number of Days for Network
Relationship. Calculated as difference
between latest end date and earliest start
date
DAYS_DURTN_MIN Min Number of Days for Network
between earliest end date and latest start
date
HOURS_DURTN_EARLST Number of Hours for Network Relationship
Subject Areas
HOURS_DURTN_LATEST Number of Hours for Network Relationship
HOURS_DURTN_MAX Max Number of Hours for Network
date
HOURS_DURTN_MIN Min Number of Hours for Network
date
MAX_INTERVAL_FLAG AFAB.MIMAX - Indicates whether maximum
time interval will be considered
MINS_DURTN_EARLST Number of Minutes for Network Relationship
MINS_DURTN_LATEST Number of Minutes for Network Relationship
MINS_DURTN_MAX Max Number of Minutes for Network
date
MINS_DURTN_MIN Min Number of Minutes for Network
date
QTY_INTERVAL AFAB.DAUER - Time interval between
relationships
SECS_DURTN AFAB.DAUTM - Relationship duration (in
seconds) as result of scheduling
3 Subject Areas
Rapid Mart data

The following diagram shows the tables in the Network Relationship section
as a Star Schema:
Subject Areas
Additionally, the following dimensions are associated with Network
Relationships:
With the tables in this section you can analyze Network Relationships along
several dimensions:
• Business Area
• Company Code
• Control Key
• MRP Controller
• Object Status
• Order Operation
• Plant
• Plant Location
• Project
• Relationship Type
3 Subject Areas
Project Cost Summary Section
• Time Dimension
• Unit Of Measure
• Valuation Area
• How are the operations within a given project linked to form a Network?
• Are there any dependencies (network relationships) missing in my
project?
• Which tasks (operations) are late because their predecessor task was
completed late?
• Which predecessor and successor tasks have the same Project
Elements (WBS) associate to them?

Use Project Costing to plan, monitor, and control project costs, thereby
achieving comprehensive cost accounting.
Project Costing features include:
structures
reconciliation with cost center accounting.
Project Costs are sourced from these SAP solutions tables:
• RPSCO - Project info database: Costs, revenues, finances
• PROJ - Project definition
• PRPS - Project Element or WBS Element Master Data
The target tables for Project Costs are:
• PROJECT_COST_SUMMARY_FACT_HZ - Cost data in horizontal
format. That is, one row for each fiscal year with 16 columns for each
measure, one for each fiscal period in the year.
Subject Areas
Project Cost Summary Section 3
• PROJECT_COST_SUMMARY_STAGE_VR - Staging table for Costs in
vertical format. Not actually used for queries in the target database.
• PROJECT_COST_SUMMARY_FACT_VR - Cost data in vertical format.
That is, one row for each fiscal year and fiscal period. There are 16 rows
per fiscal year, one for each fiscal period. Each row has individual
measures for the single fiscal period.

dimension tables:

Business Activity BUSINESS_ACTIVITY
Cost Object Indicator COST_OBJECT_INDICATOR
Financial Management Area FINANCIAL_MGMT_AREA
Financial Record Category FINANCIAL_RECORD_CATEGORY
Financial Record Type FINANCIAL_RECORD_TYPE
Financing Code FINANCING_CODE
Fiscal Period FISC_PERIOD
Monetary Currency CURRENCY
OBJECT_STATUS_HZ
Pegging Object PEGGING_OBJECT
Plant PLANT
3 Subject Areas

PROFIT_CENTER_HIER,
Progress Measure Method PROGRESS_MEASURE_METHOD
Project PROJECT
Variance Category VARIANCE_CATEGORY
Fact Table Fields

Important measures for Project Cost Summary are:
PROJECT_COST_SUMMARY_FACT_HZ:
PROJECT_COST_SUMMARY_FACT_HZ Description
Column Name
AMT_CR_PER00_LOC RPSCO.WLP00 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER00_TRX RPSCO.WTP00 - PTD Credit value in
transactional currency (Adjusting year begin
period)
transactional currency
Subject Areas
Column Name
3 Subject Areas
Column Name
AMT_CR_QTR01_LOC RPSCO.WLP00 through 03 - Quarter Credit
(QTD) value in Ledger (Local) currency
AMT_CR_QTR01_TRX RPSCO.WTP00 through 03 - Quarter Credit
value in transactional currency
AMT_CR_YTD_LOC RPSCO.WLP00 through 16 - Quarter Credit
value in Ledger (Local) currency
Subject Areas
Column Name
AMT_CR_YTD_TRX RPSCO.WTP00 through 16 - Quarter Credit
AMT_DR_PER00_LOC RPSCO.WLP00 - PTD Debit value in Ledger
AMT_DR_PER00_TRX RPSCO.WTP00 - PTD Debit value in
transactional currency (Adjusting Year begin
period)
3 Subject Areas
Column Name
Subject Areas
Column Name
AMT_DR_QTR01_LOC RPSCO.WLP00 through 03 - Quarter Debit
AMT_DR_QTR01_TRX RPSCO.WTP00 through 03 - Quarter Debit
(QTD) value in transactional currency
AMT_DR_YTD_LOC RPSCO.WLP00 through 16 - Quarter Debit
AMT_DR_YTD_TRX RPSCO.WTP00 through 16 - Quarter Debit
PROJECT_COST_SUMMARY_FACT_VR
Column Name
AMT_CR_LOC RPSCO-WLP01 through WLP16 - Period
Credit value in Ledger (Local) currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Per
16
AMT_CR_QTD_LOC RPSCO-WLP01 through WLP16 through 16 -
QTD Credit value in Ledger (Local) currency
AMT_CR_QTD_TRX RPSCO-WTP01 through WTP16 through 16 -
QTD Credit value in Transactional currency
3 Subject Areas
Column Name
AMT_CR_TRX RPSCO-WTP01 through WTP16 - Period
Credit value in Transactional currency. For
16
AMT_CR_YTD_LOC RPSCO-WLP01 through WLP16 - YTD Credit
AMT_CR_YTD_TRX RPSCO-WTP01 through WTP16 - YTD Credit
value in Transactional currency
AMT_DR_LOC RPSCO-WLP01 through WLP16 - Period Debit
value in Ledger (Local) currency. For Period 01
- cumulative of Per 00 and Per 01; for Per 12 -
cumulative of Per 12 through Per 16
AMT_DR_QTD_LOC RPSCO-WLP01 through WLP16 - QTD Debit
AMT_DR_QTD_TRX RPSCO-WTP01 through WTP16 - QTD Debit
AMT_DR_TRX RPSCO-WTP01 through WTP16 - Period
Debit value in Transactional currency. For
16
AMT_DR_YTD_LOC RPSCO-WLP01 through WLP16 - YTD Debit
AMT_DR_YTD_TRX RPSCO-WTP01 through WTP16 - YTD Debit
AMT_PER_BEGIN_LOC RPSCO-WLP01 through WLP16 - Period
begin balance value in Ledger (Local) currency
AMT_PER_BEGIN_TRX RPSCO-WTP01 through WTP16 - Period
begin balance value in Transactional currency
AMT_PER_ROLLING_LOC Rolling Total Balance - Ledger (Local) Currency
AMT_PER_ROLLING_TRX Rolling Total Balance - Transaction Currency
AMT_PTD_LOC Period Beginning Balance - Ledger (Local)
Currency
AMT_PTD_TRX Period Beginning Balance - Transaction
Currency
Subject Areas
Rapid Mart data
The following diagram shows the tables in the Project Cost Summary section
as a Star Schema:
With the tables in this section you can analyze Project Costs along several
dimensions:
• Business Activity
• Business Area
• Company Code
• Cost Object Indicator
• Financial Management Area
• Financial Record Category
• Financial Record Type
• Financing Code
• Fiscal Period
• Monetary Currency
3 Subject Areas
PRT Assignment Section

• Object Status
• Order Operation
• Pegging Object
• Plant
• Progress Measure Method
• Project
• Valuation Area
• Variance Category
• What costs has my project incurred year-to-date?
• How are certain projects performing vs. budget (actual vs. planned)?
• Which Profit Centers are incurring the most project related costs this year
by fiscal period?
• What is the trend in project costs month-to-month for each Project (WBS)
Element?

In SAP solutions, the PRT’s are assigned to an order operation.
The PRT Assignment section extracts operation level data from these SAP
solutions tables:
• AFFH - PRT assignment data for the work order
• CRFH - CIM production resource/tool master data
The section stores the data in the fact table
• PRT_ASSIGNMENT_FACT
Subject Areas
PRT Assignment Section 3
Rapid Mart processing
dimension tables
Attribute Dimension Tables

Activity & Hierarchy ACTIVITY, ACTIVITY_HIER,
ACTIVITY_HIER_HZ,
ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
Chart Of Accounts CHART_OF_ACCOUNTS
Cost Center & Hierarchy COST_CENTER,
COST_CENTER_HIER,
COST_CENTER_HIER_HZ,
COST_CENTER_HIER_VR,
COST_ELEMENT_HIER,
Material, Product Hierarchy MATERIAL,
PRODUCT_HIERARCHY
3 Subject Areas

OBJECT_STATUS_HZ
Object Type OBJECT_TYPE
Plant PLANT
Profit Center PROFIT_CENTER
Profit Center & Hierarchy PROFIT_CENTER_HIER,
Project PROJECT
PRT Category PRT_CATEGORY
PRT Grouping Key PRT_GROUPING_KEY
PRT Master PRT_MASTER
PRT Status PRT_STATUS
Reference Date Key REFERENCE_DATE_KEY
Routing ROUTING
Routing Operation ROUTING_OPERATION
Routing Sequence ROUTING_SEQUENCE
Standard Text Key STANDARD_TEXT_KEY
Subject Areas
WORK_CENTER_HIER,
Work Center Formula WORK_CENTER_FORMULA,
FORMULA_PARAMETER
Fact Table Fields

Important measures for PRT Assignments are both quantity and time oriented

ACTL_USG_VALUE AFFH.EWIST - Actual usage value for
production resource/tool
DAYS_DURTN_ACTL Actual Number of Days for Network
between actual end date and start date
(UOM_ID = TAG in IDES)
DAYS_DURTN_EARLST Number of Days for Network Relationship
based on Earliest start/end dates (UOM_ID =
TAG in IDES)
DAYS_DURTN_LATEST Number of Days for Network Relationship
based on Latest start/end dates (UOM_ID =
TAG in IDES)
DAYS_DURTN_MAX Max Number of Days for Network
between latest end date and earliest start date
DAYS_DURTN_MIN Min Number of Days for Network
between earliest end date and latest start date
HOURS_DURTN_ACTL Actual Number of HOURS for Network
(UOM_ID = HUR in IDES)
HOURS_DURTN_EARLST Number of Hours for Network Relationship
HUR in IDES)
3 Subject Areas

HOURS_DURTN_LATEST Number of HOURS for Network Relationship
HUR in IDES)
HOURS_DURTN_MAX Max Number of Hours for Network
HOURS_DURTN_MIN Min Number of Hours for Network
between earliest end date and latest start date
MINS_DURTN_ACTL Actual Number of Mins for Network
(UOM_ID = MIN in IDES)
MINS_DURTN_EARLST Number of Mins for Network Relationship
MIN in IDES)
MINS_DURTN_LATEST Number of Mins for Network Relationship
MIN in IDES)
MINS_DURTN_MAX Max Number of Mins for Network
(UOM_ID = MIN in IDES)
MINS_DURTN_MIN Min Number of Mins for Network Relationship.
Calculated as difference between earliest end
date and latest start date (UOM_ID = MIN in
IDES)
PLAN_USG_VALUE AFFH.EWSOL - Total planned usage value of
QTY_DURTN AFFH.DAUFL - Duration of PRT usage
QTY_OFFSET_END AFFH.OFFSTE - Offset to finish of production
resource/tool usage
QTY_OFFSET_START AFFH.OFFSTB - Offset to start of production
resource/tool usage
QTY_PRT_CHECKOUT AFFH.MGAUS - Quantity of checked-out
production resources/tools
Subject Areas
QTY_PRT_CONFIRM AFFH.MGIST - Confirmed quantity of
QTY_PRT_PLAN AFFH.MGSOL - Total planned quantity of
QTY_PRT_REMAIN AFFH.MGRSTEH - Remaining quantity of the
QTY_PRT_STD AFFH.MGVGW - Standard value for the PRT
quantity
REMAIN_USG_VALUE AFFH.EWRST - Remaining usage value of
the production resource/tool
STD_USG_VALUE AFFH.EWVGW - Standard usage value for
3 Subject Areas
Rapid Mart data

The following diagram shows the tables in the PRT Assignment section as a
Star Schema.
Subject Areas
Additionally, the following hierarchies are available for PRT Assignments:
With the tables in this section you can analyze PRT Assignments along
several dimensions:
• Activity & Hierarchy
• Business Area
• Chart Of Accounts
• Company Code
• Control Key
• Cost Center & Hierarchy
3 Subject Areas

• Material, Product Hierarchy
• MRP Controller
• Object Status
• Object Type
• Order Operation
• Plant
• Plant Location
• Profit Center
• Project
• PRT Category
• PRT Grouping Key
• PRT Master
• PRT Status
• Reference Date Key
• Routing
• Routing Operation
• Routing Sequence
• Standard Text Key
• Task List Type
• Time Dimension
• Unit Of Measure
• Valuation Area
• Work Center Formula
• Which are the top 10 PRT’s are assigned by Project?
• Are Operations (Project Activities) using a specific PRT finishing on
schedule?
Subject Areas
• Which Work Centers have critical PRT’s for my project?
• What is the total amount of time a certain PRT was used on my project
this month?
3 Subject Areas
Reports
chapter
4 Reports
Overview
Overview
You can use the SAP BusinessObjects Project Systems Rapid Mart, version
for SAP solutions to produce many kinds of reports. This chapter provides
examples of reports you could produce. The information in this chapter is
useful for those who analyze and produce reports with the Rapid Mart data.
This chapter provides a sample report and the recommended joins for each
componentized section in the Rapid Mart:
• Milestone
• Network (Production) Order
• Network Relationship
• Project Cost
• PRT Assignment
• Order Operation
SAP Master Data Reports are also described at the end of this chapter. These
reports are common across all Rapid Marts and are intended for hierarchy
discovery and record validation.
Note: All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Milestone
the completion of a project phase. Milestone data can be used to create
listings, high-level statistics by Company (or other dimension), and even
trending reports.
Reports
Milestone allows for a variety of trend and high level analysis. Below is a list
of the reports included here for analysis:
• Milestone Overview
• Milestone Statistics
Milestone Overview
This report displays Milestone information for the selected Project (and
Project Elements). Provides information similar to SAP Transactions: CN53N
and CJ20N (display WBS element milestones).
Reports
Milestone 4
Overview
View milestone listing for the specified Project Id.
Details
View Milestone details by Milestone Id section.
4 Reports
Milestone
Calculations
• Actual End Date = =If(FormatDate([Actl End Date]; [Default Date
Format])=[Default Date Text]; ""; [Actl End Date])
• Default Date Format = "MM/dd/yyyy"
• Detault Date Text = "01/01/1900"
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Milestone Statistics
View Milestone performance statistics by Plant for the selected Company
Code.
Summary
View milestone summary statistics for the specified Company Code. View
data as trend (Actual vs Scheduled Duratoin) and in tabular format by Plant
Name..
Reports
Milestone 4
Top 10 Projects by Variance %
View Top 10 Projects by milestone count and Variance %.
Calculations
• Variance % = If([MILESTONE - Days Actl Duration] <> 0; [MILESTONE -
Days Diff Actl Scheduled]/[MILESTONE - Days Actl Duration]; 0)
• Default Date Format = "MM/dd/yyyy"
• Detault Date Text = "01/01/1900"
Report SQL
"\Sample\DML".
4 Reports
Milestone
Recommended Table Joins

To analyze Milestone data you will need to create joins between the fact and
dimension tables as follows:
Fact Table Dimension Table Join Expression

MILESTONE_FACT ACTIVITY MILESTONE_FACT.ACTIVITY_ID=ACTI
VITY.ACTIVITY_ID and
MILESTONE_FACT.CTRL_AREA_ID=A
CTIVITY.CTRL_AREA_ID
MILESTONE_FACT ACTIVITY_HIER_HZ MILESTONE_FACT.CTRL_AREA_ID=A
CTIVITY_HIER_HZ.CTRL_AREA_ID and
MILESTONE_FACT.ACTIVITY_ID=ACTI
VITY_HIER_HZ.ACTIVITY_ID
MILESTONE_FACT ACTIVITY_HIER_VR MILESTONE_FACT.CTRL_AREA_ID =
ACTIVITY_HIER_VR.CTRL_AREA_ID
and MILESTONE_FACT.ACTIVITY_ID =
ACTIVITY_HIER_VR.CHILD_ID
MILESTONE_FACT CHART_OF_ACCOUN CHART_OF_ACCOUNTS.CHART_OF_
TS ACCT_ID=MILESTONE_FACT.CHART_
OF_ACCT_ID
MILESTONE_FACT COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
MILESTONE_FACT.CMPNY_CODE_ID
MILESTONE_FACT CONTROL_KEY MILESTONE_FACT.CTRL_KEY_ID=CO
NTROL_KEY.CTRL_KEY_ID
MILESTONE_FACT CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
=MILESTONE_FACT.CTRL_AREA_ID
MILESTONE_FACT COST_ELEMENT MILESTONE_FACT.CHART_OF_ACCT_
ID=COST_ELEMENT.CHART_OF_ACC
T_ID and
MILESTONE_FACT.COST_ELEM_ID=C
OST_ELEMENT.COST_ELEM_ID
MILESTONE_FACT COST_ELEMENT_HIE MILESTONE_FACT.COST_ELEM_ID=C
R_HZ OST_ELEMENT_HIER_HZ.COST_ELE
M_ID and
MILESTONE_FACT.CHART_OF_ACCT_
ID=COST_ELEMENT_HIER_HZ.CHART
_OF_ACCT_ID
Reports
Milestone 4
MILESTONE_FACT COST_ELEMENT_HIE MILESTONE_FACT.CHART_OF_ACCT_
R_VR ID=COST_ELEMENT_HIER_VR.CHART
_OF_ACCT_ID and
MILESTONE_FACT.COST_ELEM_ID=C
OST_ELEMENT_HIER_VR.CHILD_ID
MILESTONE_FACT DOCUMENT_CATEGO DOCUMENT_CATEGORY.DOC_CATEG
RY _ID=MILESTONE_FACT.DOC_CATEG_I
D and
DOCUMENT_CATEGORY.DIM_SRC_ID
=MILESTONE_FACT.DIM_SRC_ID_DO
CCTG
MILESTONE_FACT INTERNAL_ORDER MILESTONE_FACT.INTERNAL_ORDER
_ID=INTERNAL_ORDER.INTERNAL_O
RDER_ID
MILESTONE_FACT INTERNAL_ORDER_HI MILESTONE_FACT.INTERNAL_ORDER
ER_HZ _ID=INTERNAL_ORDER_HIER_HZ.INT
ERNAL_ORDER_ID
MILESTONE_FACT INTERNAL_ORDER_HI MILESTONE_FACT.INTERNAL_ORDER
ER_VR _ID=INTERNAL_ORDER_HIER_VR.CHI
LD_ID
MILESTONE_FACT MILESTONE_USAGE MILESTONE_USAGE.USAGE_ID =
MILESTONE_FACT.USAGE_ID
MILESTONE_FACT NETWORK_PROFILE NETWORK_PROFILE.GROUP_APPLIC
TN_ID=MILESTONE_FACT.GROUP_AP
PLICTN_ID and
NETWORK_PROFILE.NETWORK_PRO
FILE_ID=MILESTONE_FACT.NETWOR
K_PROFILE_ID
MILESTONE_FACT ORDER_OPERATION ORDER_OPERATION.OPERATN_ROU
TING_ID=MILESTONE_FACT.OPERATN
_ROUTING_ID and
ORDER_OPERATION.OPERATN_SEQ_
ID=MILESTONE_FACT.OPERATN_SEQ
_ID
MILESTONE_FACT PLANT PLANT.PLANT_ID=MILESTONE_FACT.
PLANT_ID
MILESTONE_FACT PROJECT MILESTONE_FACT.PROJ_ID=PROJEC
T.PROJ_ID
MILESTONE_FACT PROJECT_ELEMENT MILESTONE_FACT.PROJ_ELEM_ID=P
ROJECT_ELEMENT.PROJ_ELEM_ID
4 Reports
Milestone

MILESTONE_FACT PROJECT_ELEMENT_ MILESTONE_FACT.PROJ_ELEM_ID=P
HIER_HZ ROJECT_ELEMENT_HIER_HZ.PROJ_E
LEM_ID
MILESTONE_FACT PROJECT_ELEMENT_ MILESTONE_FACT.PROJ_ELEM_ID=P
HIER_VR ROJECT_ELEMENT_HIER_VR.CHILD_I
D
MILESTONE_FACT PURCH_ORGANIZATI PURCH_ORGANIZATION.PURCH_ORG
ON _ID=MILESTONE_FACT.PURCH_ORG_
ID
MILESTONE_FACT REFERENCE_DATE_K MILESTONE_FACT.DATE_KEY_ID=REF
EY ERENCE_DATE_KEY.DATE_KEY_ID
and
MILESTONE_FACT.DIM_SRC_ID_DTKE
Y=REFERENCE_DATE_KEY.DIM_SRC_
ID
MILESTONE_FACT ROUTING ROUTING.ROUTING_ID=MILESTONE_
FACT.ROUTING_ID
MILESTONE_FACT ROUTING_OPERATIO ROUTING_OPERATION.GROUP_TYPE
N _ID=MILESTONE_FACT.GROUP_TYPE
_ID and
ROUTING_OPERATION.GROUP_ID=MI
LESTONE_FACT.GROUP_ID and
ROUTING_OPERATION.GROUP_NODE
_ID=MILESTONE_FACT.GROUP_NODE
_ID
MILESTONE_FACT STATUS_PROFILE STATUS_PROFILE.STATUS_PROFILE_I
D=MILESTONE_FACT.STATUS_PROFIL
E_ID
MILESTONE_FACT TASK_LIST_TYPE TASK_LIST_TYPE.GROUP_TYPE_ID=
MILESTONE_FACT.GROUP_TYPE_ID
MILESTONE_FACT TIME_DIM TIME_DIM.CALENDAR_DATE=MILEST
ONE_FACT.CREATE_DATE
MILESTONE_FACT UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=MILEST
ONE_FACT.UOM_ID_OFFSET
MILESTONE_FACT WORK_CENTER MILESTONE_FACT.PLANT_ID=WORK_
CENTER.PLANT_ID and
MILESTONE_FACT.WORK_CNTR_ID=
WORK_CENTER.WORK_CNTR_ID
Reports
Network (Production) Order 4
MILESTONE_FACT WORK_CENTER_CAT MILESTONE_FACT.WORK_CNTR_CAT
EGORY EG_ID=WORK_CENTER_CATEGORY.
WORK_CNTR_CATEG_ID
MILESTONE_FACT WORK_CENTER_HIER MILESTONE_FACT.WORK_CNTR_ID=
_HZ WORK_CENTER_HIER_HZ.WORK_CN
TR_ID and
MILESTONE_FACT.PLANT_ID=WORK_
CENTER_HIER_HZ.PLANT_ID
MILESTONE_FACT WORK_CENTER_HIER MILESTONE_FACT.WORK_CNTR_ID=
_VR WORK_CENTER_HIER_VR.CHILD_ID
AND
MILESTONE_FACT.PLANT_ID=WORK_
CENTER_HIER_VR.PLANT_ID
Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 27 for master reports.
Network (Production) Order

SAP Applications system.
Reports
Network order is suited to detail, trend, and high level analysis. Below is a list
• Network Order Details
• Network Order Analysis
Network Order Details

View network (production) order listing, network order details, and trend by
Business Area for the selected Plant and Calendar Year.
4 Reports
Project Summary
View Network Order summary statistics by Project..
Listing
View network order listing by Order Id..
Reports
Details
View network order details by Order Id..
Calculations
• Max Basic End Date = Max([Basic End Date])
• Min Basic End Date = Min([Basic End Date])
Network Order Analysis

View network (production) order analysis for selected Plant and Calendar
Year. View Summary, Trend by Business Area, and Top 10 Materials.
4 Reports
Summary
View network order summary statistics..
Reports
Trend by Project
View network order trends by Business Area.
4 Reports
Top 10 Project Elements

View Top 10 Project Elements based on count of network orders. Uses Web
Intelligence ranking feature..
Calculations
• Days Release Variance % = If([NTWRK ORDER - Days Release
Actual]<> 0; [NTWRK ORDER - Days Release Variance (ACTL vs
SCHED)]/[NTWRK ORDER - Days Release Actual]; 0)
• Max Basic End Date = Max([Basic End Date])
• Min Basic End Date = Min([Basic End Date])
Reports
To analyze Netowrk (Production) Order data you will need to create joins between
the fact and dimension tables as follows:

MATERIAL PRODUCT_HIERARCH MATERIAL.PROD_HIER_ID=PRODUCT
Y _HIERARCHY.PROD_HIER_ID
PRODUCTION_ORDE ACCT_ASSIGNMENT_ ACCT_ASSIGNMENT_CATEGORY.ACC
R_FACT CATEGORY T_ASSIGN_CATEG_ID=PRODUCTION_
ORDER_FACT.ACCT_ASSIGN_CATEG
_ID
PRODUCTION_ORDE BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=PRO
R_FACT DUCTION_ORDER_FACT.BUS_AREA_I
D
PRODUCTION_ORDE CHART_OF_ACCOUN CHART_OF_ACCOUNTS.CHART_OF_
R_FACT TS ACCT_ID=PRODUCTION_ORDER_FAC
T.CHART_OF_ACCT_ID
PRODUCTION_ORDE COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
R_FACT PRODUCTION_ORDER_FACT.CMPNY_
CODE_ID
PRODUCTION_ORDE CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
R_FACT =PRODUCTION_ORDER_FACT.CTRL_
AREA_ID
PRODUCTION_ORDE COST_CENTER PRODUCTION_ORDER_FACT.CTRL_A
R_FACT REA_ID=COST_CENTER.CTRL_AREA_
ID AND
PRODUCTION_ORDER_FACT.COST_C
NTR_ID=COST_CENTER.COST_CNTR
_ID
PRODUCTION_ORDE COST_CENTER_HIER PRODUCTION_ORDER_FACT.CTRL_A
R_FACT _HZ REA_ID=COST_CENTER_HIER_HZ.CT
RL_AREA_ID and
NTR_ID=COST_CENTER_HIER_HZ.CO
ST_CNTR_ID
PRODUCTION_ORDE COST_CENTER_HIER PRODUCTION_ORDER_FACT.CTRL_A
R_FACT _VR REA_ID=COST_CENTER_HIER_VR.CT
RL_AREA_ID and
NTR_ID=COST_CENTER_HIER_VR.CH
ILD_ID
4 Reports

PRODUCTION_ORDE COST_ELEMENT PRODUCTION_ORDER_FACT.CHART_
R_FACT OF_ACCT_ID=COST_ELEMENT.CHAR
T_OF_ACCT_ID and
PRODUCTION_ORDER_FACT.COST_E
LEM_ID=COST_ELEMENT.COST_ELE
M_ID
PRODUCTION_ORDE COST_ELEMENT_HIE PRODUCTION_ORDER_FACT.COST_E
R_FACT R_HZ LEM_ID=COST_ELEMENT_HIER_HZ.C
OST_ELEM_ID and
PRODUCTION_ORDER_FACT.CHART_
OF_ACCT_ID=COST_ELEMENT_HIER_
HZ.CHART_OF_ACCT_ID
PRODUCTION_ORDE COST_ELEMENT_HIE PRODUCTION_ORDER_FACT.CHART_
R_FACT R_VR OF_ACCT_ID=COST_ELEMENT_HIER_
VR.CHART_OF_ACCT_ID and
PRODUCTION_ORDER_FACT.COST_E
LEM_ID=COST_ELEMENT_HIER_VR.C
HILD_ID
PRODUCTION_ORDE CURRENCY CURRENCY.CURR_ID=PRODUCTION_
R_FACT ORDER_FACT.CURR_ID
PRODUCTION_ORDE DOCUMENT_TYPE DOCUMENT_TYPE.DOC_CATEG_ID=P
R_FACT RODUCTION_ORDER_FACT.DOC_CAT
EG_ID and
DOCUMENT_TYPE.DOC_TYPE_ID=PR
ODUCTION_ORDER_FACT.DOC_TYPE
_ID and
DOCUMENT_TYPE.DIM_SRC_ID=PRO
DUCTION_ORDER_FACT.DIM_SRC_ID
_DOCTYP
PRODUCTION_ORDE FUNCTIONAL_AREA PRODUCTION_ORDER_FACT.FUNCTN
R_FACT L_AREA_ID=FUNCTIONAL_AREA.FUN
CTNL_AREA_ID
PRODUCTION_ORDE FUNCTIONAL_AREA_ PRODUCTION_ORDER_FACT.FUNCTN
R_FACT HIER_HZ L_AREA_ID=FUNCTIONAL_AREA_HIE
R_HZ.FUNCTNL_AREA_ID
PRODUCTION_ORDE FUNCTIONAL_AREA_ PRODUCTION_ORDER_FACT.FUNCTN
R_FACT HIER_VR L_AREA_ID=FUNCTIONAL_AREA_HIE
R_VR.CHILD_ID
PRODUCTION_ORDE INTERNAL_ORDER PRODUCTION_ORDER_FACT.INTERN
R_FACT AL_ORDER_ID=INTERNAL_ORDER.IN
TERNAL_ORDER_ID
Reports
PRODUCTION_ORDE INTERNAL_ORDER_HI PRODUCTION_ORDER_FACT.INTERN
R_FACT ER_HZ AL_ORDER_ID=INTERNAL_ORDER_HI
ER_HZ.INTERNAL_ORDER_ID
PRODUCTION_ORDE INTERNAL_ORDER_HI PRODUCTION_ORDER_FACT.INTERN
R_FACT ER_VR AL_ORDER_ID=INTERNAL_ORDER_HI
ER_VR.CHILD_ID
PRODUCTION_ORDE INTERNAL_ORDER_S PRODUCTION_ORDER_FACT.DOC_TY
R_FACT TATUS PE_ID=INTERNAL_ORDER_STATUS.D
OC_TYPE_ID and
PRODUCTION_ORDER_FACT.ORDER_
STATUS_ID=INTERNAL_ORDER_STAT
US.ORDER_STATUS_ID
PRODUCTION_ORDE MATERIAL PRODUCTION_ORDER_FACT.MATERI
R_FACT AL_ID=MATERIAL.MATERIAL_ID
PRODUCTION_ORDE MATERIAL_BATCH PRODUCTION_ORDER_FACT.BATCH_I
R_FACT D=MATERIAL_BATCH.BATCH_ID and
PRODUCTION_ORDER_FACT.MATERI
AL_ID=MATERIAL_BATCH.MATERIAL_I
D and
PRODUCTION_ORDER_FACT.PLANT_I
D=MATERIAL_BATCH.PLANT_ID
PRODUCTION_ORDE MATERIAL_BY_PLANT PRODUCTION_ORDER_FACT.MATERI
R_FACT AL_ID=MATERIAL_BY_PLANT.MATERI
AL_ID and
D=MATERIAL_BY_PLANT.PLANT_ID
PRODUCTION_ORDE MATERIAL_GROUP PRODUCTION_ORDER_FACT.MTRL_G
R_FACT RP_ID=MATERIAL_GROUP.MTRL_GRP
_ID
PRODUCTION_ORDE MATERIAL_TYPE PRODUCTION_ORDER_FACT.MTRL_T
R_FACT YPE_ID=MATERIAL_TYPE.MTRL_TYP
E_ID
PRODUCTION_ORDE MRP_CONTROLLER PRODUCTION_ORDER_FACT.MRP_CT
R_FACT RLLER_ID=MRP_CONTROLLER.MRP_
CTRLLER_ID and
D=MRP_CONTROLLER.PLANT_ID
PRODUCTION_ORDE PRODUCTION_ORDE PRODUCTION_ORDER_FACT.DOC_CA
R_FACT R_FACT TEG_ID='20'
4 Reports

PRODUCTION_ORDE NETWORK_PROFILE PRODUCTION_ORDER_FACT.GROUP
R_FACT _APPLICTN_ID=NETWORK_PROFILE.
GROUP_APPLICTN_ID and
PRODUCTION_ORDER_FACT.NETWO
RK_PROFILE_ID=NETWORK_PROFILE
.NETWORK_PROFILE_ID
PRODUCTION_ORDE OBJECT_CLASS PRODUCTION_ORDER_FACT.OBJ_CL
R_FACT ASS_ID=OBJECT_CLASS.OBJ_CLASS
_ID
PRODUCTION_ORDE OBJECT_NUMBER_TY PRODUCTION_ORDER_FACT.OBJ_NU
R_FACT PE M_TYPE_ID=OBJECT_NUMBER_TYPE
.OBJ_NUM_TYPE_ID
PRODUCTION_ORDE OBJECT_STATUS_HZ PRODUCTION_ORDER_FACT.OBJ_ID=
R_FACT OBJECT_STATUS_HZ.OBJ_ID
PRODUCTION_ORDE PLANT PLANT.PLANT_ID=PRODUCTION_ORD
R_FACT ER_FACT.PLANT_ID
PRODUCTION_ORDE PLANT_LOCATION PLANT_LOCATION.PLANT_ID=PRODU
R_FACT CTION_ORDER_FACT.PLANT_ID and
PLANT_LOCATION.LOCATN_ID=PROD
UCTION_ORDER_FACT.LOCATN_ID
PRODUCTION_ORDE PRODUCT_HIERARCH PRODUCTION_ORDER_FACT.PROD_H
R_FACT Y IER_ID=PRODUCT_HIERARCHY.PROD
_HIER_ID
PRODUCTION_ORDE PRODUCTION_SCHED PRODUCTION_ORDER_FACT.PLANT_I
R_FACT ULER D=
PRODUCTION_SCHEDULER.PLANT_I
D AND
PRODUCTION_ORDER_FACT.PROD_S
CHEDLER_ID=PRODUCTION_SCHED
ULER.PROD_SCHEDLER_ID
PRODUCTION_ORDE PROFIT_CENTER PRODUCTION_ORDER_FACT.CTRL_A
R_FACT REA_ID=PROFIT_CENTER.CTRL_ARE
A_ID and
PRODUCTION_ORDER_FACT.PROFIT
_CNTR_ID=PROFIT_CENTER.PROFIT_
CNTR_ID
Reports
PRODUCTION_ORDE PROFIT_CENTER_HIE PRODUCTION_ORDER_FACT.CTRL_A
R_FACT R_HZ REA_ID=PROFIT_CENTER_HIER_HZ.C
TRL_AREA_ID and
_CNTR_ID=PROFIT_CENTER_HIER_H
Z.PROFIT_CNTR_ID
PRODUCTION_ORDE PROFIT_CENTER_HIE PRODUCTION_ORDER_FACT.CTRL_A
R_FACT R_VR REA_ID=PROFIT_CENTER_HIER_VR.
CTRL_AREA_ID and
_CNTR_ID=PROFIT_CENTER_HIER_V
R.CHILD_ID
PRODUCTION_ORDE PROJECT PRODUCTION_ORDER_FACT.PROJ_I
R_FACT D=PROJECT.PROJ_ID
PRODUCTION_ORDE PROJECT_ELEMENT PRODUCTION_ORDER_FACT.PROJ_E
R_FACT LEM_ID=PROJECT_ELEMENT.PROJ_E
LEM_ID
PRODUCTION_ORDE PROJECT_ELEMENT_ PRODUCTION_ORDER_FACT.PROJ_E
R_FACT HIER_HZ LEM_ID=PROJECT_ELEMENT_HIER_H
Z.PROJ_ELEM_ID
PRODUCTION_ORDE PROJECT_ELEMENT_ PRODUCTION_ORDER_FACT.PROJ_E
R_FACT HIER_VR LEM_ID=PROJECT_ELEMENT_HIER_V
R.CHILD_ID
PRODUCTION_ORDE PURCH_ORGANIZATI PURCH_ORGANIZATION.PURCH_ORG
R_FACT ON _ID=PRODUCTION_ORDER_FACT.PU
RCH_ORG_ID
PRODUCTION_ORDE ROUTING ROUTING.ROUTING_ID=PRODUCTION
R_FACT _ORDER_FACT.ROUTING_ID
PRODUCTION_ORDE SERVICE_PERSON SERVICE_PERSON.PERSON_ID=PRO
R_FACT DUCTION_ORDER_FACT.PERSON_ID_
RESP
PRODUCTION_ORDE SPECIAL_PROCUREM PRODUCTION_ORDER_FACT.SPECL_
R_FACT ENT_TYPE PROCUREMNT_TYPE_ID=SPECIAL_P
ROCUREMENT_TYPE.SPECL_PROCU
REMNT_TYPE_ID
PRODUCTION_ORDE STORAGE_LOCATION STORAGE_LOCATION.STORAGE_LOC
R_FACT ATN_ID=PRODUCTION_ORDER_FACT.
STORAGE_LOCATN_ID
4 Reports
Network Relationship

PRODUCTION_ORDE TASK_LIST_TYPE TASK_LIST_TYPE.GROUP_TYPE_ID=P
R_FACT RODUCTION_ORDER_FACT.GROUP_T
YPE_ID
PRODUCTION_ORDE TASK_LIST_USAGE TASK_LIST_USAGE.GROUP_USG_ID=
R_FACT PRODUCTION_ORDER_FACT.GROUP
_USG_ID
PRODUCTION_ORDE TIME_DIM TIME_DIM.CALENDAR_DATE=PRODU
R_FACT CTION_ORDER_FACT.CREATE_DATE
PRODUCTION_ORDE UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=PRODU
R_FACT CTION_ORDER_FACT.UOM_ID
PRODUCTION_ORDE VALUATION_AREA VALUATION_AREA.VALUATN_AREA_ID
R_FACT =PRODUCTION_ORDER_FACT.VALUA
TN_AREA_ID
OBJECT_STATUS_HZ OBJECT_STATUS OBJECT_STATUS_HZ.OBJ_ID=OBJEC
T_STATUS.OBJ_ID
Network relationships describe the link between the start and finish points of
two activities in a network and determine the sequence of activities.
Reports
Network order is suited to detail, trend, and high level analysis. Below is a list
• Network Relationship Overview
Network Relationship Overview

View Network Relationship overview for the selected Project (or Network -
also called Internal Order Id) and Operation Numbers. Network relationship
display using SAP transaction CN23.
Reports
Network Relationship 4
Overview
View overview of Project operations for the given network.
Details
Detailed view of project operations based. Analyze data by Parent Operation
activity number.
Calculations
• Successor Flag = If([Operation Num]=[Parent Operation Num]; ""; "X")
Report SQL
• All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
4 Reports

To analyze Network Relationship data you will need to create joins between the
fact and dimension tables as follows:

NETWORK_RELATION BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=NET
SHIP_FACT WORK_RELATIONSHIP_FACT.BUS_AR
EA_ID
NETWORK_RELATION COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
SHIP_FACT NETWORK_RELATIONSHIP_FACT.CM
PNY_CODE_ID
NETWORK_RELATION CONTROL_KEY NETWORK_RELATIONSHIP_FACT.CTR
SHIP_FACT L_KEY_ID=CONTROL_KEY.CTRL_KEY
_ID
NETWORK_RELATION CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
SHIP_FACT =NETWORK_RELATIONSHIP_FACT.CT
RL_AREA_ID
NETWORK_RELATION FUNCTIONAL_AREA NETWORK_RELATIONSHIP_FACT.FUN
SHIP_FACT CTNL_AREA_ID=FUNCTIONAL_AREA.
FUNCTNL_AREA_ID
NETWORK_RELATION FUNCTIONAL_AREA_ NETWORK_RELATIONSHIP_FACT.FUN
SHIP_FACT HIER_HZ CTNL_AREA_ID=FUNCTIONAL_AREA_
HIER_HZ.FUNCTNL_AREA_ID
NETWORK_RELATION FUNCTIONAL_AREA_ NETWORK_RELATIONSHIP_FACT.FUN
SHIP_FACT HIER_VR CTNL_AREA_ID=FUNCTIONAL_AREA_
HIER_VR.CHILD_ID
NETWORK_RELATION INTERNAL_ORDER NETWORK_RELATIONSHIP_FACT.INT
SHIP_FACT ERNAL_ORDER_ID=INTERNAL_ORDE
R.INTERNAL_ORDER_ID
NETWORK_RELATION INTERNAL_ORDER_HI NETWORK_RELATIONSHIP_FACT.INT
SHIP_FACT ER_HZ ERNAL_ORDER_ID=INTERNAL_ORDE
R_HIER_HZ.INTERNAL_ORDER_ID
NETWORK_RELATION INTERNAL_ORDER_HI NETWORK_RELATIONSHIP_FACT.INT
SHIP_FACT ER_VR ERNAL_ORDER_ID=INTERNAL_ORDE
R_HIER_VR.CHILD_ID
NETWORK_RELATION MRP_CONTROLLER NETWORK_RELATIONSHIP_FACT.MR
SHIP_FACT P_CTRLLER_ID=MRP_CONTROLLER.
MRP_CTRLLER_ID and
NETWORK_RELATIONSHIP_FACT.PLA
NT_ID=MRP_CONTROLLER.PLANT_ID
Reports
Network Relationship 4
NETWORK_RELATION NETWORK_HIER_VR NETWORK_RELATIONSHIP_FACT.REL
SHIP_FACT ATIONSHIP_TYPE_ID=NETWORK_HIE
R_VR.RELATIONSHIP_TYPE_ID and
NETWORK_RELATIONSHIP_FACT.OPE
RATN_ROUTING_ID_PAR=NETWORK_
HIER_VR.OPERATN_ROUTING_ID_PA
RENT and
RATN_SEQ_ID_PAR=NETWORK_HIER
_VR.OPERATN_SEQ_ID_PARENT and
RATN_ROUTING_ID=NETWORK_HIER
_VR.OPERATN_ROUTING_ID_CHILD
and
RATN_SEQ_ID=NETWORK_HIER_VR.
OPERATN_SEQ_ID_CHILD
NETWORK_RELATION OBJECT_STATUS_HZ NETWORK_RELATIONSHIP_FACT.OBJ
SHIP_FACT _ID=OBJECT_STATUS_HZ.OBJ_ID
NETWORK_RELATION ORDER_OPERATION ORDER_OPERATION.OPERATN_ROU
SHIP_FACT TING_ID=NETWORK_RELATIONSHIP_
FACT.OPERATN_ROUTING_ID and
ID=NETWORK_RELATIONSHIP_FACT.
OPERATN_SEQ_ID
NETWORK_RELATION PLANT PLANT.PLANT_ID=NETWORK_RELATI
SHIP_FACT ONSHIP_FACT.PLANT_ID
NETWORK_RELATION PLANT_LOCATION PLANT_LOCATION.PLANT_ID=NETWO
SHIP_FACT RK_RELATIONSHIP_FACT.PLANT_ID
AND
PLANT_LOCATION.LOCATN_ID=NETW
ORK_RELATIONSHIP_FACT.LOCATN_I
D
NETWORK_RELATION PROFIT_CENTER NETWORK_RELATIONSHIP_FACT.CTR
SHIP_FACT L_AREA_ID=PROFIT_CENTER.CTRL_
AREA_ID and
NETWORK_RELATIONSHIP_FACT.PRO
FIT_CNTR_ID=PROFIT_CENTER.PROF
IT_CNTR_ID
4 Reports

NETWORK_RELATION PROFIT_CENTER_HIE NETWORK_RELATIONSHIP_FACT.CTR
SHIP_FACT R_HZ L_AREA_ID=PROFIT_CENTER_HIER_
HZ.CTRL_AREA_ID and
FIT_CNTR_ID=PROFIT_CENTER_HIER
_HZ.PROFIT_CNTR_ID
NETWORK_RELATION PROFIT_CENTER_HIE NETWORK_RELATIONSHIP_FACT.CTR
SHIP_FACT R_VR L_AREA_ID=PROFIT_CENTER_HIER_
VR.CTRL_AREA_ID and
FIT_CNTR_ID=PROFIT_CENTER_HIER
_VR.CHILD_ID
NETWORK_RELATION PROJECT NETWORK_RELATIONSHIP_FACT.PRO
SHIP_FACT J_ID=PROJECT.PROJ_ID
NETWORK_RELATION PROJECT_ELEMENT PROJECT_ELEMENT.PROJ_ELEM_ID=
SHIP_FACT NETWORK_RELATIONSHIP_FACT.PRO
J_ELEM_ID
NETWORK_RELATION PROJECT_ELEMENT_ NETWORK_RELATIONSHIP_FACT.PRO
SHIP_FACT HIER_HZ J_ELEM_ID=PROJECT_ELEMENT_HIE
R_HZ.PROJ_ELEM_ID
NETWORK_RELATION PROJECT_ELEMENT_ NETWORK_RELATIONSHIP_FACT.PRO
SHIP_FACT HIER_VR J_ELEM_ID=PROJECT_ELEMENT_HIE
R_VR.CHILD_ID
NETWORK_RELATION PURCH_ORGANIZATI PURCH_ORGANIZATION.PURCH_ORG
SHIP_FACT ON _ID=NETWORK_RELATIONSHIP_FACT.
PURCH_ORG_ID
NETWORK_RELATION RELATIONSHIP_TYPE RELATIONSHIP_TYPE.RELATIONSHIP
SHIP_FACT _TYPE_ID=NETWORK_RELATIONSHIP
_FACT.RELATIONSHIP_TYPE_ID
NETWORK_RELATION STORAGE_LOCATION STORAGE_LOCATION.STORAGE_LOC
SHIP_FACT ATN_ID=NETWORK_RELATIONSHIP_F
ACT.STORAGE_LOCATN_ID
NETWORK_RELATION TIME_DIM TIME_DIM.CALENDAR_DATE=NETWO
SHIP_FACT RK_RELATIONSHIP_FACT.EARLST_ST
ART_DATE
NETWORK_RELATION UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=NETWO
SHIP_FACT RK_RELATIONSHIP_FACT.UOM_ID
NETWORK_RELATION VALUATION_AREA VALUATION_AREA.VALUATN_AREA_ID
SHIP_FACT =NETWORK_RELATIONSHIP_FACT.VA
LUATN_AREA_ID
Reports
Project Cost 4
NETWORK_RELATION WORK_CENTER NETWORK_RELATIONSHIP_FACT.PLA
SHIP_FACT NT_ID=WORK_CENTER.PLANT_ID and
NETWORK_RELATIONSHIP_FACT.WO
RK_CNTR_ID=WORK_CENTER.WORK
_CNTR_ID
NETWORK_RELATION WORK_CENTER_CAT NETWORK_RELATIONSHIP_FACT.WO
SHIP_FACT EGORY RK_CNTR_CATEG_ID=WORK_CENTE
R_CATEGORY.WORK_CNTR_CATEG_I
D
NETWORK_RELATION WORK_CENTER_HIER NETWORK_RELATIONSHIP_FACT.WO
SHIP_FACT _HZ RK_CNTR_ID=WORK_CENTER_HIER_
HZ.WORK_CNTR_ID and
NT_ID=WORK_CENTER_HIER_HZ.PLA
NT_ID
NETWORK_RELATION WORK_CENTER_HIER NETWORK_RELATIONSHIP_FACT.WO
SHIP_FACT _VR RK_CNTR_ID=WORK_CENTER_HIER_
VR.CHILD_ID AND
NT_ID=WORK_CENTER_HIER_VR.PLA
NT_ID
T_STATUS.OBJ_ID
Project Cost
Project Costing is used to plan, monitor, and control project costs, thereby
Reports
Project Cost is suited to a variety of cost detail, trend, and summary analysis.
Below is a list of the reports included here for analysis:
• Project Balance Trend Comparision
• Project Balance Trend by Period
• Project Balance Variance Trend
• Project Cost YTD Trend Analysis
4 Reports
Project Cost
• Project Cost Period Comparison
Project Balance Trend Comparision

Displays the project balance trend data for the selected Company Code,
Fiscal Years, and Parent Project Element.
Actual Balance Trend
View trend comparison (between fiscal years) for actual project summary
costs by project element.
Variance Previous Period

View trend comparison (between fiscal years) for actual project summary
costs by project element.
Calculations
• Variance From Previous Period calculations are all similar to:
Period 2 = [PROJ COST SUM Hz Actual PTD Balance Per 02
LOC]-[PROJ COST SUM Hz Actual PTD Balance Per 01 LOC]
Reports
Project Cost 4
Report SQL
"\Sample\DML".
Project Balance Trend by Period

View actual project balance period trends for the selected Company Code,
Parent Project Element, and Fiscal Year-Period range. Results are grouped
by Project Element Hierarchy.
Report SQL
"\Sample\DML".
4 Reports
Project Cost
Project Balance Variance Trend

View Actual, Planned (or Budget), Variance, and Variance % period trends for
a specific Company Code, Parent Project Element, Fiscal Year, and Ledger
Version.
Calculations
• Actual = [PROJ COST SUM Vr Actual PTD Balance LOC]
• Budget = [PROJ COST SUM Vr Budget PTD Balance LOC]
• Variance = [PROJ COST SUM Vr Actual PTD Balance LOC]-[PROJ
COST SUM Vr Budget PTD Balance LOC]
• Variance % = If([Actual] <> 0; [Variance]/[Actual]; If([Actual]= 0 And
[Variance]=0; 0;1))
Report SQL
"\Sample\DML".
Reports
Project Cost 4
Project Cost YTD Trend Analysis
View Actual YTD trends for a specific Company Code, Parent Project
Element, Fiscal Year, and Ledger Version.
Calculations
• Actual YTD Balance = PROJ COST SUM Vr Actual YTD Balance LOC]
• Balance Variance = [PROJ COST SUM Vr Actual YTD Balance
LOC]-[PROJ COST SUM Vr Budget YTD Balance LOC]
• Budget YTD Balance = [PROJ COST SUM Vr Budget YTD Balance LOC]
• Variance % = If([PROJ COST SUM Vr Actual YTD Balance LOC] <> 0;
[Balance Variance]/[PROJ COST SUM Vr Actual YTD Balance LOC];
If([PROJ COST SUM Vr Actual YTD Balance LOC]=0 And [Balance
Variance]<>0; 1; 0))
Report SQL
"\Sample\DML".
4 Reports
Project Cost
Project Cost Period Comparison

View Actual, Planned (or Budget), Variance Project Element hierarchy
comparison for selected Fiscal Year-Periods and Ledger Version.
Calculations
• Actuals = [PROJ COST SUM Vr Actual PTD Balance LOC]
• Budget = [PROJ COST SUM Vr Budget PTD Balance LOC]
• Variance = [Actuals]-[Budget]
• Variance % = If([Actuals] <> 0; [Variance]/[Actuals]; If([Actuals]<> 0 And
[Variance] = 0; 1; 0))
Report SQL
"\Sample\DML".
Reports
Project Cost 4
To analyze Project Cost Summary data you will need to create joins between the
fact and dimension tables as follows:

T_STATUS.OBJ_ID
PROJECT_COST_SUM BUSINESS_ACTIVITY BUSINESS_ACTIVITY.BUS_ACTIVITY_I
MARY_FACT_HZ D=PROJECT_COST_SUMMARY_FACT
_HZ.BUS_ACTIVITY_ID
PROJECT_COST_SUM BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=PRO
MARY_FACT_HZ JECT_COST_SUMMARY_FACT_HZ.BU
S_AREA_ID
PROJECT_COST_SUM COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
MARY_FACT_HZ PROJECT_COST_SUMMARY_FACT_H
Z.CMPNY_CODE_ID
PROJECT_COST_SUM CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
MARY_FACT_HZ =PROJECT_COST_SUMMARY_FACT_
HZ.CTRL_AREA_ID
PROJECT_COST_SUM COST_OBJECT_INDIC COST_OBJECT_INDICATOR.COST_OB
MARY_FACT_HZ ATOR J_ID=PROJECT_COST_SUMMARY_FA
CT_HZ.COST_OBJ_ID
PROJECT_COST_SUM CURRENCY CURRENCY.CURR_ID=PROJECT_COS
MARY_FACT_HZ T_SUMMARY_FACT_HZ.CURR_ID_TR
X
MARY_FACT_HZ T_SUMMARY_FACT_HZ.CURR_ID_LO
C
PROJECT_COST_SUM FINANCIAL_MGMT_AR FINANCIAL_MGMT_AREA.FIN_MGMT_
MARY_FACT_HZ EA AREA_ID=PROJECT_COST_SUMMAR
Y_FACT_HZ.FIN_MGMT_AREA_ID
PROJECT_COST_SUM FINANCIAL_RECORD_ FINANCIAL_RECORD_CATEGORY.RE
MARY_FACT_HZ CATEGORY CORD_CATEG_ID=PROJECT_COST_S
UMMARY_FACT_HZ.RECORD_CATEG
_ID
PROJECT_COST_SUM FINANCIAL_RECORD_ FINANCIAL_RECORD_TYPE.RECORD
MARY_FACT_HZ TYPE _TYPE_ID=PROJECT_COST_SUMMAR
Y_FACT_HZ.RECORD_TYPE_ID and
FINANCIAL_RECORD_TYPE.DIM_SRC
_ID=PROJECT_COST_SUMMARY_FAC
T_HZ.DIM_SRC_ID_RECTYP
4 Reports
Project Cost

PROJECT_COST_SUM FINANCING_CODE FINANCING_CODE.FIN_MGMT_AREA_
MARY_FACT_HZ ID=PROJECT_COST_SUMMARY_FACT
_HZ.FIN_MGMT_AREA_ID and
FINANCING_CODE.FUND_ID=PROJEC
T_COST_SUMMARY_FACT_HZ.FUND_
ID
PROJECT_COST_SUM FUNCTIONAL_AREA PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ Z.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_ PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ HIER_HZ Z.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA_HIER_HZ.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_ PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ HIER_VR Z.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA_HIER_VR.CHILD_ID
PROJECT_COST_SUM OBJECT_NUMBER_TY PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ PE Z.OBJ_NUM_TYPE_ID=OBJECT_NUM
BER_TYPE.OBJ_NUM_TYPE_ID
PROJECT_COST_SUM OBJECT_STATUS_HZ PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ Z.OBJ_ID=OBJECT_STATUS_HZ.OBJ_I
D
PROJECT_COST_SUM ORDER_OPERATION ORDER_OPERATION.OPERATN_ROU
MARY_FACT_HZ TING_ID=PROJECT_COST_SUMMARY
_FACT_HZ.OPERATN_ROUTING_ID
and
ID=PROJECT_COST_SUMMARY_FACT
_HZ.OPERATN_SEQ_ID
PROJECT_COST_SUM PEGGING_OBJECT PEGGING_OBJECT.OBJ_ID =
MARY_FACT_HZ PROJECT_COST_SUMMARY_FACT_H
Z.OBJ_ID and
PEGGING_OBJECT.PEG_CATEG_FULL
_NAME = @Prompt('Pegging Category
Full Name:','A','Pegging Object\Pegging
Category Full
Name',Mono,Free,Persistent,,User:0)
PROJECT_COST_SUM PLANT PLANT.PLANT_ID=PROJECT_COST_S
MARY_FACT_HZ UMMARY_FACT_HZ.PLANT_ID
Reports
Project Cost 4
PROJECT_COST_SUM PROFIT_CENTER PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ Z.CTRL_AREA_ID=PROFIT_CENTER.C
TRL_AREA_ID and
PROJECT_COST_SUMMARY_FACT_H
Z.PROFIT_CNTR_ID=PROFIT_CENTER
.PROFIT_CNTR_ID
PROJECT_COST_SUM PROFIT_CENTER_HIE PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ R_HZ Z.CTRL_AREA_ID=PROFIT_CENTER_
HIER_HZ.CTRL_AREA_ID and
_HIER_HZ.PROFIT_CNTR_ID
PROJECT_COST_SUM PROFIT_CENTER_HIE PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ R_VR Z.CTRL_AREA_ID=PROFIT_CENTER_
HIER_VR.CTRL_AREA_ID and
_HIER_VR.CHILD_ID
PROJECT_COST_SUM PROGRESS_MEASUR PROGRESS_MEASURE_METHOD.OBJ
MARY_FACT_HZ E_METHOD _ID =
Z.OBJ_ID and
PROGRESS_MEASURE_METHOD.PR
OGRESS_VERSION_FULL_NAME =
@Prompt('Progress Version Full
Name:','A','Progress Measure
Method\Progress Version Full
PROJECT_COST_SUM PROJECT PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ Z.PROJ_ID=PROJECT.PROJ_ID
PROJECT_COST_SUM PROJECT_COST_SUM PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ MARY_FACT_HZ Z.FISC_YEAR=PROJECT_COST_SUM
MARY_FACT_HZ.PARTITION_YEAR
PROJECT_COST_SUM PROJECT_ELEMENT PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ Z.PROJ_ELEM_ID=PROJECT_ELEMEN
T.PROJ_ELEM_ID
PROJECT_COST_SUM PROJECT_ELEMENT_ PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ HIER_HZ Z.PROJ_ELEM_ID=PROJECT_ELEMEN
T_HIER_HZ.PROJ_ELEM_ID
PROJECT_COST_SUM PROJECT_ELEMENT_ PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ HIER_VR Z.PROJ_ELEM_ID=PROJECT_ELEMEN
T_HIER_VR.CHILD_ID
4 Reports
Project Cost

PROJECT_COST_SUM PURCH_ORGANIZATI PURCH_ORGANIZATION.PURCH_ORG
MARY_FACT_HZ ON _ID=PROJECT_COST_SUMMARY_FAC
T_HZ.PURCH_ORG_ID
PROJECT_COST_SUM VALUATION_AREA VALUATION_AREA.VALUATN_AREA_ID
MARY_FACT_HZ =PROJECT_COST_SUMMARY_FACT_
HZ.VALUATN_AREA_ID
PROJECT_COST_SUM VARIANCE_CATEGOR PROJECT_COST_SUMMARY_FACT_H
MARY_FACT_HZ Y Z.VARIANCE_CATEG_ID=VARIANCE_C
ATEGORY.VARIANCE_CATEG_ID
T_STATUS.OBJ_ID
PROJECT_COST_SUM BUSINESS_ACTIVITY BUSINESS_ACTIVITY.BUS_ACTIVITY_I
MARY_FACT_VR D=PROJECT_COST_SUMMARY_FACT
_VR.BUS_ACTIVITY_ID
PROJECT_COST_SUM BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=PRO
MARY_FACT_VR JECT_COST_SUMMARY_FACT_VR.BU
S_AREA_ID
PROJECT_COST_SUM COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
MARY_FACT_VR PROJECT_COST_SUMMARY_FACT_V
R.CMPNY_CODE_ID
PROJECT_COST_SUM CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
MARY_FACT_VR =PROJECT_COST_SUMMARY_FACT_
VR.CTRL_AREA_ID
PROJECT_COST_SUM COST_OBJECT_INDIC COST_OBJECT_INDICATOR.COST_OB
MARY_FACT_VR ATOR J_ID=PROJECT_COST_SUMMARY_FA
CT_VR.COST_OBJ_ID
MARY_FACT_VR T_SUMMARY_FACT_VR.CURR_ID_LO
C
MARY_FACT_VR T_SUMMARY_FACT_VR.CURR_ID_TR
X
PROJECT_COST_SUM FINANCIAL_MGMT_AR FINANCIAL_MGMT_AREA.FIN_MGMT_
MARY_FACT_VR EA AREA_ID=PROJECT_COST_SUMMAR
Y_FACT_VR.FIN_MGMT_AREA_ID
PROJECT_COST_SUM FINANCIAL_RECORD_ FINANCIAL_RECORD_CATEGORY.RE
MARY_FACT_VR CATEGORY CORD_CATEG_ID=PROJECT_COST_S
UMMARY_FACT_VR.RECORD_CATEG
_ID
Reports
Project Cost 4
PROJECT_COST_SUM FINANCIAL_RECORD_ FINANCIAL_RECORD_TYPE.RECORD
MARY_FACT_VR TYPE _TYPE_ID=PROJECT_COST_SUMMAR
Y_FACT_VR.RECORD_TYPE_ID and
FINANCIAL_RECORD_TYPE.DIM_SRC
_ID=PROJECT_COST_SUMMARY_FAC
T_VR.DIM_SRC_ID_RECTYP
PROJECT_COST_SUM FINANCING_CODE FINANCING_CODE.FIN_MGMT_AREA_
MARY_FACT_VR ID=PROJECT_COST_SUMMARY_FACT
_VR.FIN_MGMT_AREA_ID and
FINANCING_CODE.FUND_ID=PROJEC
T_COST_SUMMARY_FACT_VR.FUND_
ID
PROJECT_COST_SUM FISC_PERIOD PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R.FISC_YEAR=FISC_PERIOD.FISC_YE
AR AND
PROJECT_COST_SUMMARY_FACT_V
R.FISC_PERIOD =
FISC_PERIOD.FISC_PERIOD
PROJECT_COST_SUM FUNCTIONAL_AREA PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_ PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR HIER_HZ R.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA_HIER_HZ.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_ PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR HIER_VR R.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA_HIER_VR.CHILD_ID
PROJECT_COST_SUM OBJECT_NUMBER_TY PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR PE R.OBJ_NUM_TYPE_ID=OBJECT_NUM
BER_TYPE.OBJ_NUM_TYPE_ID
PROJECT_COST_SUM OBJECT_STATUS_HZ PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R.OBJ_ID=OBJECT_STATUS_HZ.OBJ_I
D
PROJECT_COST_SUM ORDER_OPERATION ORDER_OPERATION.OPERATN_ROU
MARY_FACT_VR TING_ID=PROJECT_COST_SUMMARY
_FACT_VR.OPERATN_ROUTING_ID
and
ID=PROJECT_COST_SUMMARY_FACT
_VR.OPERATN_SEQ_ID
4 Reports
Project Cost

PROJECT_COST_SUM PEGGING_OBJECT PEGGING_OBJECT.OBJ_ID =
MARY_FACT_VR PROJECT_COST_SUMMARY_FACT_V
R.OBJ_ID and
PEGGING_OBJECT.PEG_CATEG_FULL
_NAME = @Prompt('Pegging Category
Full Name:','A','Pegging Object\Pegging
Category Full
PROJECT_COST_SUM PLANT PLANT.PLANT_ID=PROJECT_COST_S
MARY_FACT_VR UMMARY_FACT_VR.PLANT_ID
PROJECT_COST_SUM PROFIT_CENTER PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R.CTRL_AREA_ID=PROFIT_CENTER.C
TRL_AREA_ID and
R.PROFIT_CNTR_ID=PROFIT_CENTE
R.PROFIT_CNTR_ID
PROJECT_COST_SUM PROFIT_CENTER_HIE PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R_HZ R.CTRL_AREA_ID=PROFIT_CENTER_
HIER_HZ.CTRL_AREA_ID and
R_HIER_HZ.PROFIT_CNTR_ID
PROJECT_COST_SUM PROFIT_CENTER_HIE PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R_VR R.CTRL_AREA_ID=PROFIT_CENTER_
HIER_VR.CTRL_AREA_ID and
R_HIER_VR.CHILD_ID
PROJECT_COST_SUM PROGRESS_MEASUR PROGRESS_MEASURE_METHOD.OBJ
MARY_FACT_VR E_METHOD _ID =
R.OBJ_ID and
PROGRESS_MEASURE_METHOD.PR
OGRESS_VERSION_FULL_NAME =
@Prompt('Progress Version Full
Name:','A','Progress Measure
Method\Progress Version Full
PROJECT_COST_SUM PROJECT PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R.PROJ_ID=PROJECT.PROJ_ID
Reports
PRT Assignment 4
PROJECT_COST_SUM PROJECT_COST_SUM PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR MARY_FACT_VR R.FISC_YEAR=PROJECT_COST_SUM
MARY_FACT_VR.PARTITION_YEAR
PROJECT_COST_SUM PROJECT_ELEMENT PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR R.PROJ_ELEM_ID=PROJECT_ELEME
NT.PROJ_ELEM_ID
PROJECT_COST_SUM PROJECT_ELEMENT_ PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR HIER_HZ R.PROJ_ELEM_ID=PROJECT_ELEME
NT_HIER_HZ.PROJ_ELEM_ID
PROJECT_COST_SUM PROJECT_ELEMENT_ PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR HIER_VR R.PROJ_ELEM_ID=PROJECT_ELEME
NT_HIER_VR.CHILD_ID
PROJECT_COST_SUM PURCH_ORGANIZATI PURCH_ORGANIZATION.PURCH_ORG
MARY_FACT_VR ON _ID=PROJECT_COST_SUMMARY_FAC
T_VR.PURCH_ORG_ID
PROJECT_COST_SUM VALUATION_AREA VALUATION_AREA.VALUATN_AREA_ID
MARY_FACT_VR =PROJECT_COST_SUMMARY_FACT_
VR.VALUATN_AREA_ID
PROJECT_COST_SUM VARIANCE_CATEGOR PROJECT_COST_SUMMARY_FACT_V
MARY_FACT_VR Y R.VARIANCE_CATEG_ID=VARIANCE_
CATEGORY.VARIANCE_CATEG_ID
PRT Assignment
Production resources and tools (PRTs) are movable (not stationary) operating
resources that are required to perform an activity and can be used repeatedly.
Reports
PRT Assignment is suited to detail and trend reporting analysis. Below is a list
• PRT Assignment Listing
• PRT Details
4 Reports
PRT Assignment
PRT Assignment Listing

View a listing of PRT assignments for the selected Operation Routing Id.
Report SQL
"\Sample\DML".
PRT Details
View PRT details for the selected PRT (by PRT Name). Provides similar detail
as SAP transaction CF03.
Reports
PRT Assignment 4
Basic Data
View basic PRT data including durations, dates, location and project
grouping..
Defaults
View formulas, groupings, and general data.
Report SQL
"\Sample\DML".
4 Reports
PRT Assignment

To analyze PRT Assignment data you will need to create joins between the fact
and dimension tables as follows:

MATERIAL PRODUCT_HIERARCH MATERIAL.PROD_HIER_ID=PRODUCT
Y _HIERARCHY.PROD_HIER_ID
T_STATUS.OBJ_ID
PRT_ASSIGNMENT_F ACTIVITY PRT_ASSIGNMENT_FACT.ACTIVITY_I
ACT D=ACTIVITY.ACTIVITY_ID and
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=ACTIVITY.CTRL_AREA_ID
PRT_ASSIGNMENT_F ACTIVITY_HIER_HZ PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT _ID=ACTIVITY_HIER_HZ.CTRL_AREA_
ID and
PRT_ASSIGNMENT_FACT.ACTIVITY_I
D=ACTIVITY_HIER_HZ.ACTIVITY_ID
PRT_ASSIGNMENT_F ACTIVITY_HIER_VR PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT _ID =
ACTIVITY_HIER_VR.CTRL_AREA_ID
and
PRT_ASSIGNMENT_FACT.ACTIVITY_I
D = ACTIVITY_HIER_VR.CHILD_ID
PRT_ASSIGNMENT_F BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=PRT
ACT _ASSIGNMENT_FACT.BUS_AREA_ID
PRT_ASSIGNMENT_F CHART_OF_ACCOUN CHART_OF_ACCOUNTS.CHART_OF_
ACT TS ACCT_ID=PRT_ASSIGNMENT_FACT.C
HART_OF_ACCT_ID
PRT_ASSIGNMENT_F COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
ACT PRT_ASSIGNMENT_FACT.CMPNY_CO
DE_ID
PRT_ASSIGNMENT_F CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
ACT =PRT_ASSIGNMENT_FACT.CTRL_ARE
A_ID
PRT_ASSIGNMENT_F COST_CENTER PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT _ID=COST_CENTER.CTRL_AREA_ID
AND
PRT_ASSIGNMENT_FACT.COST_CNT
R_ID=COST_CENTER.COST_CNTR_ID
Reports
PRT Assignment 4
PRT_ASSIGNMENT_F COST_CENTER_HIER PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT _HZ _ID=COST_CENTER_HIER_HZ.CTRL_
AREA_ID and
R_ID=COST_CENTER_HIER_HZ.COST
_CNTR_ID
PRT_ASSIGNMENT_F COST_CENTER_HIER PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT _VR _ID=COST_CENTER_HIER_VR.CTRL_
AREA_ID and
R_ID=COST_CENTER_HIER_VR.CHIL
D_ID
PRT_ASSIGNMENT_F COST_ELEMENT PRT_ASSIGNMENT_FACT.CHART_OF_
ACT ACCT_ID=COST_ELEMENT.CHART_O
F_ACCT_ID and
PRT_ASSIGNMENT_FACT.COST_ELE
M_ID=COST_ELEMENT.COST_ELEM_I
D
PRT_ASSIGNMENT_F COST_ELEMENT_HIE PRT_ASSIGNMENT_FACT.COST_ELE
ACT R_HZ M_ID=COST_ELEMENT_HIER_HZ.COS
T_ELEM_ID and
PRT_ASSIGNMENT_FACT.CHART_OF_
ACCT_ID=COST_ELEMENT_HIER_HZ.
CHART_OF_ACCT_ID
PRT_ASSIGNMENT_F COST_ELEMENT_HIE PRT_ASSIGNMENT_FACT.CHART_OF_
ACT R_VR ACCT_ID=COST_ELEMENT_HIER_VR.
CHART_OF_ACCT_ID and
PRT_ASSIGNMENT_FACT.COST_ELE
M_ID=COST_ELEMENT_HIER_VR.CHI
LD_ID
PRT_ASSIGNMENT_F FUNCTIONAL_AREA PRT_ASSIGNMENT_FACT.FUNCTNL_A
ACT REA_ID=FUNCTIONAL_AREA.FUNCTN
L_AREA_ID
PRT_ASSIGNMENT_F FUNCTIONAL_AREA_ PRT_ASSIGNMENT_FACT.FUNCTNL_A
ACT HIER_HZ REA_ID=FUNCTIONAL_AREA_HIER_H
Z.FUNCTNL_AREA_ID
PRT_ASSIGNMENT_F FUNCTIONAL_AREA_ PRT_ASSIGNMENT_FACT.FUNCTNL_A
ACT HIER_VR REA_ID=FUNCTIONAL_AREA_HIER_V
R.CHILD_ID
PRT_ASSIGNMENT_F INTERNAL_ORDER PRT_ASSIGNMENT_FACT.INTERNAL_
ACT ORDER_ID=INTERNAL_ORDER.INTER
NAL_ORDER_ID
4 Reports
PRT Assignment

PRT_ASSIGNMENT_F INTERNAL_ORDER_HI PRT_ASSIGNMENT_FACT.INTERNAL_
ACT ER_HZ ORDER_ID=INTERNAL_ORDER_HIER_
HZ.INTERNAL_ORDER_ID
PRT_ASSIGNMENT_F INTERNAL_ORDER_HI PRT_ASSIGNMENT_FACT.INTERNAL_
ACT ER_VR ORDER_ID=INTERNAL_ORDER_HIER_
VR.CHILD_ID
PRT_ASSIGNMENT_F MATERIAL PRT_ASSIGNMENT_FACT.MATERIAL_I
ACT D=MATERIAL.MATERIAL_ID
PRT_ASSIGNMENT_F MRP_CONTROLLER PRT_ASSIGNMENT_FACT.MRP_CTRLL
ACT ER_ID=MRP_CONTROLLER.MRP_CTR
LLER_ID and
PRT_ASSIGNMENT_FACT.PLANT_ID=
MRP_CONTROLLER.PLANT_ID
PRT_ASSIGNMENT_F OBJECT_NUMBER_TY PRT_ASSIGNMENT_FACT.OBJ_NUM_T
ACT PE YPE_ID =
OBJECT_NUMBER_TYPE.OBJ_NUM_T
YPE_ID
PRT_ASSIGNMENT_F OBJECT_STATUS_HZ PRT_ASSIGNMENT_FACT.OBJ_ID=OB
ACT JECT_STATUS_HZ.OBJ_ID
PRT_ASSIGNMENT_F OBJECT_TYPE PRT_ASSIGNMENT_FACT.OBJ_TYPE_I
ACT D = OBJECT_TYPE.OBJ_TYPE_ID AND
PRT_ASSIGNMENT_FACT.DIM_SRC_I
D_OBJTYP =
OBJECT_TYPE.OBJ_TYPE_ID
PRT_ASSIGNMENT_F ORDER_OPERATION ORDER_OPERATION.OPERATN_ROU
ACT TING_ID=PRT_ASSIGNMENT_FACT.O
PERATN_ROUTING_ID and
ID=PRT_ASSIGNMENT_FACT.OPERAT
N_SEQ_ID
PRT_ASSIGNMENT_F PLANT PLANT.PLANT_ID=PRT_ASSIGNMENT
ACT _FACT.PLANT_ID
PRT_ASSIGNMENT_F PLANT_LOCATION PLANT_LOCATION.PLANT_ID=PRT_AS
ACT SIGNMENT_FACT.PLANT_ID AND
PLANT_LOCATION.LOCATN_ID=PRT_
ASSIGNMENT_FACT.LOCATN_ID
Reports
PRT Assignment 4
PRT_ASSIGNMENT_F PROFIT_CENTER PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT _ID=PROFIT_CENTER.CTRL_AREA_ID
and
PRT_ASSIGNMENT_FACT.PROFIT_CN
TR_ID=PROFIT_CENTER.PROFIT_CNT
R_ID
PRT_ASSIGNMENT_F PROFIT_CENTER_HIE PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT R_HZ _ID=PROFIT_CENTER_HIER_HZ.CTRL
_AREA_ID and
TR_ID=PROFIT_CENTER_HIER_HZ.PR
OFIT_CNTR_ID
PRT_ASSIGNMENT_F PROFIT_CENTER_HIE PRT_ASSIGNMENT_FACT.CTRL_AREA
ACT R_VR _ID=PROFIT_CENTER_HIER_VR.CTRL
_AREA_ID and
TR_ID=PROFIT_CENTER_HIER_VR.C
HILD_ID
PRT_ASSIGNMENT_F PROJECT PRT_ASSIGNMENT_FACT.PROJ_ID=P
ACT ROJECT.PROJ_ID
PRT_ASSIGNMENT_F PROJECT_ELEMENT PRT_ASSIGNMENT_FACT.PROJ_ELEM
ACT _ID=PROJECT_ELEMENT.PROJ_ELEM
_ID
PRT_ASSIGNMENT_F PROJECT_ELEMENT_ PRT_ASSIGNMENT_FACT.PROJ_ELEM
ACT HIER_HZ _ID=PROJECT_ELEMENT_HIER_HZ.P
ROJ_ELEM_ID
PRT_ASSIGNMENT_F PROJECT_ELEMENT_ PRT_ASSIGNMENT_FACT.PROJ_ELEM
ACT HIER_VR _ID=PROJECT_ELEMENT_HIER_VR.C
HILD_ID
PRT_ASSIGNMENT_F PRT_CATEGORY PRT_ASSIGNMENT_FACT.PRT_CATEG
ACT _ID = PRT_CATEGORY.PRT_CATEG_ID
PRT_ASSIGNMENT_F PRT_GROUPING_KEY PRT_ASSIGNMENT_FACT.GROUPNG_
ACT KEY_ID_01 =
PRT_GROUPING_KEY.GROUPNG_KE
Y_ID
PRT_ASSIGNMENT_F PRT_MASTER PRT_ASSIGNMENT_FACT.PRT_ID =
ACT PRT_MASTER.PRT_ID
PRT_ASSIGNMENT_F PRT_STATUS PRT_ASSIGNMENT_FACT.PRT_STATU
ACT S_ID = PRT_STATUS.PRT_STATUS_ID
4 Reports
PRT Assignment

PRT_ASSIGNMENT_F PURCH_ORGANIZATI PURCH_ORGANIZATION.PURCH_ORG
ACT ON _ID=PRT_ASSIGNMENT_FACT.PURCH
_ORG_ID
PRT_ASSIGNMENT_F REFERENCE_DATE_K PRT_ASSIGNMENT_FACT.DATE_KEY_
ACT EY ID_START=REFERENCE_DATE_KEY.D
ATE_KEY_ID and
PRT_ASSIGNMENT_FACT.DIM_SRC_I
D_DTKEY=REFERENCE_DATE_KEY.DI
M_SRC_ID
PRT_ASSIGNMENT_F ROUTING ROUTING.ROUTING_ID=PRT_ASSIGN
ACT MENT_FACT.ROUTING_ID
PRT_ASSIGNMENT_F ROUTING_OPERATIO ROUTING_OPERATION.GROUP_TYPE
ACT N _ID=PRT_ASSIGNMENT_FACT.GROUP
_TYPE_ID and
ROUTING_OPERATION.GROUP_ID=P
RT_ASSIGNMENT_FACT.GROUP_ID
and
ROUTING_OPERATION.GROUP_NODE
_ID=PRT_ASSIGNMENT_FACT.GROUP
_NODE_ID
PRT_ASSIGNMENT_F ROUTING_SEQUENCE ROUTING_SEQUENCE.ROUTING_ID =
ACT PRT_ASSIGNMENT_FACT.ROUTING_I
D AND
ROUTING_SEQUENCE.GROUP_LINE_I
D=
PRT_ASSIGNMENT_FACT.GROUP_LIN
E_ID
PRT_ASSIGNMENT_F STANDARD_TEXT_KE STANDARD_TEXT_KEY.STD_TEXT_KE
ACT Y Y_ID=PRT_ASSIGNMENT_FACT.STD_
TEXT_KEY_ID
PRT_ASSIGNMENT_F STORAGE_LOCATION STORAGE_LOCATION.STORAGE_LOC
ACT ATN_ID=PRT_ASSIGNMENT_FACT.ST
ORAGE_LOCATN_ID
PRT_ASSIGNMENT_F TASK_LIST_TYPE TASK_LIST_TYPE.GROUP_TYPE_ID=P
ACT RT_ASSIGNMENT_FACT.GROUP_TYP
E_ID
PRT_ASSIGNMENT_F TIME_DIM TIME_DIM.CALENDAR_DATE=PRT_AS
ACT SIGNMENT_FACT.CREATE_DATE
PRT_ASSIGNMENT_F UNIT_OF_MEASURE UNIT_OF_MEASURE.UOM_ID=PRT_A
ACT SSIGNMENT_FACT.UOM_ID_DURTN
Reports
Order Operation 4
PRT_ASSIGNMENT_F VALUATION_AREA VALUATION_AREA.VALUATN_AREA_ID
ACT =PRT_ASSIGNMENT_FACT.VALUATN_
AREA_ID
PRT_ASSIGNMENT_F WORK_CENTER PRT_ASSIGNMENT_FACT.PLANT_ID=
ACT WORK_CENTER.PLANT_ID and
PRT_ASSIGNMENT_FACT.WORK_CNT
R_ID=WORK_CENTER.WORK_CNTR_I
D
PRT_ASSIGNMENT_F WORK_CENTER_CAT PRT_ASSIGNMENT_FACT.WORK_CNT
ACT EGORY R_CATEG_ID=WORK_CENTER_CATE
GORY.WORK_CNTR_CATEG_ID
PRT_ASSIGNMENT_F WORK_CENTER_FOR PRT_ASSIGNMENT_FACT.FORMULA_I
ACT MULA D_PRT_QTY=WORK_CENTER_FORM
ULA.FORMULA_ID
PRT_ASSIGNMENT_F WORK_CENTER_HIER PRT_ASSIGNMENT_FACT.WORK_CNT
ACT _HZ R_ID=WORK_CENTER_HIER_HZ.WOR
K_CNTR_ID and
WORK_CENTER_HIER_HZ.PLANT_ID
PRT_ASSIGNMENT_F WORK_CENTER_HIER PRT_ASSIGNMENT_FACT.WORK_CNT
ACT _VR R_ID=WORK_CENTER_HIER_VR.CHIL
D_ID AND
WORK_CENTER_HIER_VR.PLANT_ID
WORK_CENTER_FOR FORMULA_PARAMET WORK_CENTER_FORMULA.PARAMET
MULA ER ER_ID_01=FORMULA_PARAMETER.PA
RAMETER_ID
Order Operation
Detail for activity sequence in a workstep in a plan or work order.
Reports
Order Operation is suited to detail and summary reporting. Below is a list of
the reports included here for analysis:
• Project Structure Planning
4 Reports
Order Operation
Project Structure Planning

View project structure for the selected Project Id. Provides a similar display of
project data as seen in SAP transaction CJ2A.
WBS Basic Data
View Project Element listing by hierarchy level..
Dates
View project element dates by Activity.
Reports
Order Operation 4
Activity Data
View Activity listing by Project Element and Work Center..
Report SQL
"\Sample\DML".

To analyze Order Operation data you will need to create joins between the fact
and dimension tables as follows:

T_STATUS.OBJ_ID
ORDER_OPERATION ACTIVITY ORDER_OPERATION.ACTIVITY_ID=AC
TIVITY.ACTIVITY_ID and
ORDER_OPERATION.CTRL_AREA_ID=
ACTIVITY.CTRL_AREA_ID
ORDER_OPERATION ACTIVITY_HIER_HZ ORDER_OPERATION.CTRL_AREA_ID=
ACTIVITY_HIER_HZ.CTRL_AREA_ID
and
ORDER_OPERATION.ACTIVITY_ID=AC
TIVITY_HIER_HZ.ACTIVITY_ID
ORDER_OPERATION ACTIVITY_HIER_VR ORDER_OPERATION.CTRL_AREA_ID
= ACTIVITY_HIER_VR.CTRL_AREA_ID
and
ORDER_OPERATION.ACTIVITY_ID =
4 Reports
Order Operation

ORDER_OPERATION BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID=ORD
ER_OPERATION.BUS_AREA_ID
ORDER_OPERATION CHART_OF_ACCOUN CHART_OF_ACCOUNTS.CHART_OF_
TS ACCT_ID=ORDER_OPERATION.CHAR
T_OF_ACCT_ID
ORDER_OPERATION COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID=
ORDER_OPERATION.CMPNY_CODE_I
D
ORDER_OPERATION CONTROL_KEY ORDER_OPERATION.CTRL_KEY_ID=C
ONTROL_KEY.CTRL_KEY_ID
ORDER_OPERATION CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
=ORDER_OPERATION.CTRL_AREA_ID
ORDER_OPERATION COST_ELEMENT ORDER_OPERATION.CHART_OF_ACC
T_ID=COST_ELEMENT.CHART_OF_AC
CT_ID and
ORDER_OPERATION.COST_ELEM_ID
=COST_ELEMENT.COST_ELEM_ID
ORDER_OPERATION COST_ELEMENT_HIE ORDER_OPERATION.COST_ELEM_ID
R_HZ =COST_ELEMENT_HIER_HZ.COST_EL
EM_ID and
ORDER_OPERATION.CHART_OF_ACC
T_ID=COST_ELEMENT_HIER_HZ.CHA
RT_OF_ACCT_ID
ORDER_OPERATION COST_ELEMENT_HIE ORDER_OPERATION.CHART_OF_ACC
R_VR T_ID=COST_ELEMENT_HIER_VR.CHA
RT_OF_ACCT_ID and
ORDER_OPERATION.COST_ELEM_ID
=COST_ELEMENT_HIER_VR.CHILD_ID
ORDER_OPERATION CURRENCY CURRENCY.CURR_ID=ORDER_OPER
ATION.CURR_ID
ORDER_OPERATION FUNCTIONAL_AREA ORDER_OPERATION.FUNCTNL_AREA
_ID=FUNCTIONAL_AREA.FUNCTNL_A
REA_ID
ORDER_OPERATION FUNCTIONAL_AREA_ ORDER_OPERATION.FUNCTNL_AREA
HIER_HZ _ID=FUNCTIONAL_AREA_HIER_HZ.FU
NCTNL_AREA_ID
ORDER_OPERATION FUNCTIONAL_AREA_ ORDER_OPERATION.FUNCTNL_AREA
HIER_VR _ID=FUNCTIONAL_AREA_HIER_VR.C
HILD_ID
Reports
Order Operation 4
ORDER_OPERATION INTERNAL_ORDER ORDER_OPERATION.INTERNAL_ORD
ER_ID=INTERNAL_ORDER.INTERNAL
_ORDER_ID
ORDER_OPERATION INTERNAL_ORDER_HI ORDER_OPERATION.INTERNAL_ORD
ER_HZ ER_ID=INTERNAL_ORDER_HIER_HZ.I
NTERNAL_ORDER_ID
ORDER_OPERATION INTERNAL_ORDER_HI ORDER_OPERATION.INTERNAL_ORD
ER_VR ER_ID=INTERNAL_ORDER_HIER_VR.
CHILD_ID
ORDER_OPERATION OBJECT_CLASS ORDER_OPERATION.OBJ_CLASS_ID
= OBJECT_CLASS.OBJ_CLASS_ID
ORDER_OPERATION OBJECT_NUMBER_TY ORDER_OPERATION.OBJ_NUM_TYPE
PE _ID =
OBJECT_NUMBER_TYPE.OBJ_NUM_T
YPE_ID
ORDER_OPERATION OBJECT_STATUS_HZ ORDER_OPERATION.OBJ_ID=OBJECT
_STATUS_HZ.OBJ_ID
ORDER_OPERATION OBJECT_TYPE ORDER_OPERATION.OBJ_TYPE_ID =
OBJECT_TYPE.OBJ_TYPE_ID
ORDER_OPERATION OPERATION_SUITABIL ORDER_OPERATION.PLANT_ID =
ITY OPERATION_SUITABILITY.PLANT_ID
AND
ORDER_OPERATION.SUITABILITY_ID=
OPERATION_SUITABILITY.SUITABILITY
_ID
ORDER_OPERATION ORDER_OPERATION ORDER_OPERATION.OPERATN_ROU
TING_ID=ORDER_OPERATION.OPERA
TN_ROUTING_ID and
ID=ORDER_OPERATION.OPERATN_S
EQ_ID
ORDER_OPERATION PLANT PLANT.PLANT_ID=ORDER_OPERATIO
N.PLANT_ID
ORDER_OPERATION PROFIT_CENTER ORDER_OPERATION.CTRL_AREA_ID=
PROFIT_CENTER.CTRL_AREA_ID and
ORDER_OPERATION.PROFIT_CNTR_I
D=PROFIT_CENTER.PROFIT_CNTR_I
D
4 Reports
Order Operation

ORDER_OPERATION PROFIT_CENTER_HIE ORDER_OPERATION.CTRL_AREA_ID=
R_HZ PROFIT_CENTER_HIER_HZ.CTRL_AR
EA_ID and
D=PROFIT_CENTER_HIER_HZ.PROFI
T_CNTR_ID
ORDER_OPERATION PROFIT_CENTER_HIE ORDER_OPERATION.CTRL_AREA_ID=
R_VR PROFIT_CENTER_HIER_VR.CTRL_AR
EA_ID and
D=PROFIT_CENTER_HIER_VR.CHILD_
ID
ORDER_OPERATION PROJECT ORDER_OPERATION.PROJ_ID=PROJ
ECT.PROJ_ID
ORDER_OPERATION PROJECT_ELEMENT ORDER_OPERATION.PROJ_ELEM_ID=
PROJECT_ELEMENT.PROJ_ELEM_ID
ORDER_OPERATION PROJECT_ELEMENT_ ORDER_OPERATION.PROJ_ELEM_ID=
HIER_HZ PROJECT_ELEMENT_HIER_HZ.PROJ_
ELEM_ID
ORDER_OPERATION PROJECT_ELEMENT_ ORDER_OPERATION.PROJ_ELEM_ID=
HIER_VR PROJECT_ELEMENT_HIER_VR.CHILD
_ID
ORDER_OPERATION ROUTING ROUTING.ROUTING_ID=ORDER_OPE
RATION.ROUTING_ID
ORDER_OPERATION ROUTING_SEQUENCE ROUTING_SEQUENCE.ROUTING_ID =
ORDER_OPERATION.ROUTING_ID
AND
ROUTING_SEQUENCE.GROUP_LINE_I
D=
ORDER_OPERATION.GROUP_LINE_ID
ORDER_OPERATION SYSTEM_CONDITION ORDER_OPERATION.SYSTEM_CONDI
TN_ID =
SYSTEM_CONDITION.SYSTEM_COND
ITN_ID
ORDER_OPERATION WORK_CENTER ORDER_OPERATION.PLANT_ID=WOR
K_CENTER.PLANT_ID and
ORDER_OPERATION.WORK_CNTR_ID
=WORK_CENTER.WORK_CNTR_ID
Reports
SAP Master Data Reports 4
ORDER_OPERATION WORK_CENTER_HIER ORDER_OPERATION.WORK_CNTR_ID
_HZ =WORK_CENTER_HIER_HZ.WORK_C
NTR_ID and
ORDER_OPERATION.PLANT_ID=WOR
K_CENTER_HIER_HZ.PLANT_ID
ORDER_OPERATION WORK_CENTER_HIER ORDER_OPERATION.WORK_CNTR_ID
_VR =WORK_CENTER_HIER_VR.CHILD_ID
AND
ORDER_OPERATION.PLANT_ID=WOR
K_CENTER_HIER_VR.PLANT_ID
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
4 Reports
• 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,
Reports
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.
4 Reports
Report SQL
"\Sample\DML".
Reports
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
"\Sample\DML".
Cost Element Hierarchy Data Discovery

View Cost Element Hierarchies for a specified Chart of Accounts, Parent Cost
Element, and Cost Element Hierarchy.
Report SQL
"\Sample\DML".
4 Reports
Internal Order Hierarchy Data Discovery

View Internal Order Hierarchies for a specified Controlling Area, Parent
Internal Order, and Internal Order Hierarchy.
Report SQL
"\Sample\DML".
Reports
Functional Area Hierarchy Data Discovery
View Functional Area Hierarchies for a specified Parent Functional Area and
Functional Area Hierarchy.
Report SQL
"\Sample\DML".
4 Reports
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
"\Sample\DML".
Reports
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,
4 Reports
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
AND
AND
)
Reports
Project Element Hierarchy Data Discovery
View Project Element Hierarchies for a specified Parent Project Element and
Report SQL
"\Sample\DML".
Equipment Hierarchy Data Discovery

View Equipment Hierarchies for a specified Parent Equipment and Equipment
Hierarchy.
Report SQL
"\Sample\DML".
4 Reports
Functional Location Hierarchy Data Discovery

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

View Work Center Hierarchies for a specified Parent Work Center and Work
Center Hierarchy.
Report SQL
"\Sample\DML".
Reports
BOM Hierarchy Data Discovery
View BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.
Report SQL
"\Sample\DML".
4 Reports
Organization Unit Data Discovery

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

View Position Hierarchies for the specified Parent Position(s).
Report SQL
"\Sample\DML".
Reports
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 Data Table

Invalid Cost Center Hierarchy COST_CENTER_HIER_BAD
Invalid Activity Hierarchy ACTIVITY_HIER_BAD
Invalid Cost Element Hierarchy COST_ELEMENT_HIER_BAD
Invalid Functional Area Hierarchy FUNCTIONAL_AREA_HIER_BAD
Invalid GL Account Hierarchy GL_ACCOUNT_HIER_BAD
Invalid Internal Order Hierarchy INTERNAL_ORDER_HIER_BAD
Invalid Profit Center Hierarchy PROFIT_CENTER_HIER_BAD
Invalid Project Element Hierarchy PROJECT_ELEMENT_HIER_BAD
Invalid Work Center Hierarchy 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,
4 Reports
COST_CNTR_HIER_BAD.CHILD_DESC,
COST_CNTR_HIER_BAD.DI_ERRORACTION,
COST_CNTR_HIER_BAD.DI_ERRORCOLUMNS,
COST_CNTR_HIER_BAD.LEAF_FLAG,
COST_CNTR_HIER_BAD.LOAD_DATE,
COST_CNTR_HIER_BAD.LOAD_TIME,
COST_CNTR_HIER_BAD.ROOT_FLAG
FROM
COST_CNTR_HIER_BAD
Recommended table joins

When analyzing data hierarchy data, you need to create joins between the
dimension table and the hierarchy tables in the Rapid Mart. The following
shows joins provided in the SAP Master Data universe.
Dimension Table Hierarchy Table Join Text
ACTIVITY ACTIVITY_HIER_HZ ACTIVITY.CTRL_AREA_ID=ACTIVITY_HIER_H
Z.CTRL_AREA_ID and
ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HZ.A
CTIVITY_ID
ACTIVITY ACTIVITY_HIER_VR ACTIVITY.CTRL_AREA_ID =
ACTIVITY_HIER_VR.CTRL_AREA_ID and
ACTIVITY.ACTIVITY_ID =
BILL_OF_MATERIALS BILL_OF_MATERIALS_HIE BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_
R_HZ 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
R_VR OF_MATERIALS_HIER_VR.BOM_CATEG_ID
and
ERIALS_HIER_VR.BOM_ID and
MATERIALS_HIER_VR.ALT_BOM_ID and
F_MATERIALS_HIER_VR.CHILD_ID
COST_CENTER COST_CENTER_HIER_HZ 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
Reports
COST_CENTER COST_CENTER_HIER_VR COST_CENTER.CTRL_AREA_ID=COST_CENT
ER_HIER_VR.CTRL_AREA_ID and
TER_HIER_VR.CHILD_ID
COST_ELEMENT COST_ELEMENT_HIER_H COST_ELEMENT.COST_ELEM_ID=COST_ELE
Z MENT_HIER_HZ.COST_ELEM_ID and
COST_ELEMENT.CHART_OF_ACCT_ID=COST
_ELEMENT_HIER_HZ.CHART_OF_ACCT_ID
COST_ELEMENT COST_ELEMENT_HIER_V COST_ELEMENT.CHART_OF_ACCT_ID=COST
R _ELEMENT_HIER_VR.CHART_OF_ACCT_ID
and
COST_ELEMENT.COST_ELEM_ID=COST_ELE
MENT_HIER_VR.CHILD_ID
COUNTRY_GROUP COUNTRY_GROUP_STAT COUNTRY_GROUP.COUNTRY_GRP_ID =
US COUNTRY_GROUP_STATUS.COUNTRY_GRP
_ID
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIE
R_HZ.EQUIPMNT_ID
EQUIPMENT EQUIPMENT_HIER_VR EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIE
R_VR.CHILD_ID
FS_HIERARCHY GL_ACCOUNT_HIER_HZ 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
FS_HIERARCHY GL_ACCOUNT_HIER_VR GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I
GL_ACCOUNT_HIER_VR.HIER_ID=FS_HIERA
GL_ACCOUNT_HIER_VR.CHILD_ID=FS_HIER
ARCHY.CHILD_ID
FUNCTIONAL_AREA FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU
_HZ NCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA
_ID
_VR NCTIONAL_AREA_HIER_VR.CHILD_ID
FUNCTIONAL_LOCATION FUNCTIONAL_LOCATION_ FUNCTIONAL_LOCATION.FUNCTNL_LOCATN
HIER_HZ _ID=FUNCTIONAL_LOCATION_HIER_HZ.FUN
CTNL_LOCATN_ID
HIER_VR _ID=FUNCTIONAL_LOCATION_HIER_VR.CHIL
D_ID
GL_ACCOUNT_HIER 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
4 Reports

GL_ACCOUNT_HIER GL_ACCOUNT_HIER_VR GL_ACCOUNT_HIER_VR.HIER_ID=GL_ACCO
GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I
and
GL_ACCOUNT_HIER_VR.CHILD_ID=GL_ACC
OUNT_HIER.CHILD_ID
GL_ACCOUNT_MASTER GL_ACCOUNT_HIER_HZ 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 GL_ACCOUNT_HIER_VR GL_ACCOUNT_MASTER.CHART_OF_ACCT_I
D=GL_ACCOUNT_HIER_VR.CHART_OF_ACC
T_ID and
CCOUNT_HIER_VR.CHILD_ID AND
GL_ACCOUNT_HIER_VR.HIER_ID =
Code','A','GL Account Hierarchy Vr\Hierarchy
Name',mono,free)
INTERNAL_ORDER INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN
HZ TERNAL_ORDER_HIER_HZ.INTERNAL_ORDE
R_ID
VR TERNAL_ORDER_HIER_VR.CHILD_ID
MATERIAL PRODUCT_HIERARCHY MATERIAL.PROD_HIER_ID=PRODUCT_HIERA
RCHY.PROD_HIER_ID
OBJECT_STATUS_HZ OBJECT_STATUS OBJECT_STATUS_HZ.OBJ_ID=OBJECT_STAT
US.OBJ_ID
ORGANIZATION_UNIT ORGANIZATION_UNIT_HIE ORGANIZATION_UNIT.ORG_UNIT_KEY
R_HZ =ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT
_KEY
ORGANIZATION_UNIT ORGANIZATION_UNIT_HIE ORGANIZATION_UNIT.ORG_UNIT_KEY=ORG
R_VR ANIZATION_UNIT_HIER_VR.CHILD_KEY
PAYROLL_PERIOD PAYROLL_PERIOD_PARA PAYROLL_PERIOD.PERIOD_PARAMETER_ID
METER =
PAYROLL_PERIOD_PARAMETER.PERIOD_PA
RAMETER_ID
Reports
POSITION POSITION_HIER_HZ POSITION.POSITION_ID=POSITION_HIER_HZ
.POSITION_ID
POSITION POSITION_HIER_VR POSITION.POSITION_ID=POSITION_HIER_VR
.CHILD_ID
PROFIT_CENTER PROFIT_CENTER_HIER_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 PROFIT_CENTER_HIER_V PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C
R ENTER_HIER_VR.CTRL_AREA_ID and
_CENTER_HIER_VR.CHILD_ID
PROJECT_ELEMENT PROJECT_ELEMENT_HIE PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE
R_HZ CT_ELEMENT_HIER_HZ.PROJ_ELEM_ID
R_VR CT_ELEMENT_HIER_VR.CHILD_ID
WORK_CENTER 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 WORK_CENTER_HIER_VR WORK_CENTER.WORK_CNTR_ID=WORK_CE
NTER_HIER_VR.CHILD_ID AND
HIER_VR.PLANT_ID
4 Reports
Universe
chapter
5 Universe
Overview
Overview
Before we begin a detailed discussion of the Project System universe it is
important to understand certain concepts that are common to any Rapid Mart
universe.
• Universe Design Principles
• Hierarchies
• Project System Specific Hierarchies
solutions contains the following universes:
• SAP Project System Universe - business content universe for Project
System
• SAP Master Data Reports - an Auxiliary Universe designed to facilitate
data discovery and auditing within SAP solutions. It does not follow a star
schema approach.
Simple tips for customizing the SAP Project System universe are also
presented in Customizing the Universe.
Universe Design Principles

The universe design principles presented below are designed to help you
better understand universe content and how to use it.
All Rapid Mart universes use the same design principles to ensure ease of
use, and rapid creation of reporting solutions.
Universe
Universe Design Principles 5
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
5 Universe
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 can’t be summarized, such as net
price.
Attribute: descriptive information; can’t be aggregated, such as internal order
number, material number, etc.
Detail: a transaction attribute, such as Currency code, or Functional Area ID.
Subject: in most cases associated with the fact table name. Examples are
FINANCIAL_DOCUMENT_FACT, PROFIT_CENTER_FACT_VR.
Business Function/Process: processes and functions in ERP applications
that are captured when entering a transaction (Costing, Profitability, etc.). For
the Universe, it is logical grouping of attributes by function or processes
related to the subject. Examples are Activity Hierarchy, and Project Element
dates.
Common Dimension: a dimension table that is associated with multiple fact
tables; such as Internal Orders, Time Dim, Currency, and GL Account.
Universe
Universe Design Principles 5
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.
5 Universe
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
('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)
Universe
Hierarchies 5
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 year’s revenue all in a single
data provider, and using a single revenue object. Without this technique
multiple synchronized queries would be needed.
Think of indexes as providing vertical breaks in a single data provider.
Local variables can then be created using the index values.
• Zeros: These perform a similar function to indexes, namely they provide
a means to return filtered information in a single data provider. Just as
Indexes provide vertical breaks for measures, Zeros provide horizontal
breaks. This is often requires when comparing two time periods.
For example, you want to compare sales in a certain product line for each
quarter this year. However, the product line had no sales in third quarter.
Without use of the Zeros technique the data for 3rd quarter would be
missing in the report. With Zeros, a placeholder value (with zero value) is
shown.
• Blanks: Their purpose is to provide an additional object that can be used
in a display block. An example is a label that returns total company sales,
where a normal query would only provide breakdowns by some category.
Blanks are coded to ‘ ‘ (a space). Normally, this text is the same as the
name of the object.
• Hyperlink Start: provides a starting point for hyperlink jumps (for
example to details in another report). Used in a Java environment.
Hierarchies
Hierarchies 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.
5 Universe
Hierarchies
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
Universe
Hierarchies 5
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.
5 Universe
Hierarchies
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.
Universe
Hierarchies 5
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.
5 Universe
Hierarchies
The primary key for a horizontal hierarchy contains all the level id’s
(LVL_00_ID to LVL_xx_ID). Where “xx” is the limit set in Data Services.
In cases where there are more than “xx” levels in the hierarchy there are two
choices
• Change the primary key into a non-unique index.
• Customize the hierarchy to include the missing levels; expanding the
horizontal table and its primary key accordingly.
Propagation of Child (Leaf) Nodes:
Also note that child (leaf) nodes that belong to other than the last hierarchy
level (Leaf Level 1 and Leaf Level 2) have their Activity ID propagated to the
lowest Level ID of the hierarchy starting with the Level 1 ID. Leaf level 2
nodes are propagated out from level 2 ID to the lowest Level ID. Leaf level 3
nodes are propagated out from level 3 ID to the lowest level, etc.
.
Child (leaf) node propagation allows creating reports with indented listings of
Cost Elements, Cost and Profit Centers, and other hierarchical master data
where depth of indention depends on the node position (Leaf Level).
Vertical Hierarchy 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:
Universe
Hierarchies 5
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.
5 Universe
Hierarchies
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 “SAP Master
Data Reports” on page 253 for more details.
Universe
Hierarchies 5
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.
5 Universe
Hierarchies
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, we’ll use the GL Account Hierarchy as an example. All
hierarchies work in a similar method, but the GL Account Hierarchy has the
added complexity of combining more than one hierarchy from SAP solutions.
It has additional filters not found in the other hierarchies to deal with this
situation.
Universe
Hierarchies 5
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.
5 Universe
Hierarchies
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.
Universe
Hierarchies 5
Example: In the example below, “Activity 1" is both the parent and child of
“Activity 2”.
(as Parent)
Activity1
Activity2 Activity3
Activity1 Activity4 Activity5 Activity6
(as Child)
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.
5 Universe
Hierarchies
Invalid Hierarchies Layout:
Note: The screenshot above is an example from the SAP BusinessObjects

Cost Center Rapid Mart, version for SAP solutions.
Universe
Project System Specific Hierarchies 5
Project System Specific Hierarchies
Accounting Hierarchies
The Project Systems Rapid Mart has several Accounting Hierarchy
dimensions that report financial breakdowns in the same manner as SAP
solutions. These all appear as Set Hierarchies (SAP solutions transaction
GS03).
These hierarchies are organized in both horizontal and vertical format. They
are listed here with their corresponding SAP solutions Table and Column. The
Table and Column represent the lowest level (leaf level) in each hierarchy:
Hierarchy Name Table and Column

Activity CCSS-LSTAR
Cost Center CCSS-KOSTL
Cost Element CCSS-KSTAR
Functional Area GLFUNCT-RFAREA
Internal Orders CCSS-AUFNR
Profit Center GLPCT-RPRCTR
For each of the 6 hierarchies, two sub-classes within in each dimension

represent the vertical and horizontal hierarchies.
Each hierarchy also has a sub-class for invalid hierarchy records. See “Invalid
Hierarchies” on page 160 for more details.
Additional Hierarchies
These additional hierarchies, for the Project Systems Rapid Mart are also
organized both horizontally and vertically, but not maintained by
transaction GS03. Instead, they are associated with specific master data
records.
Hierarchy Name Source Tables

Project Element PRHI
Work Center CRHD, CRHH, CRHS
Of these hierarchies only Project Element can have invalid records in SAP
solutions. See “Invalid Hierarchies” on page 160 for more details.
5 Universe
SAP Project System Universe

The SAP Project System Universe gathers information from the SAP
solutions Project System module.
Projects are generally part of the internal processes of a company. To be able
to control all tasks in project execution, you need an organizational form that
is specific to the project and which is shared by all departments involved.
Before you can carry out a project in its entirety, the project goals must be
precisely described and the project activities to be carried out must be
structured. A clear, unambiguous project structure is the basis for successful
project planning, monitoring, and control.
You structure your project per the following points of view:
• By structures, using a work breakdown structure (WBS)
• By process, using individual activities (work packages)
To support these processes SAP solutions uses Company Code, Customers,
Activity, Cost Center, Functional Area, Functional Location, Fiscal Periods,
other master data, and numerous reference data. In some cases these
master data are organized into hierarchy (or tree) structures.
The SAP Project System universe is a reflection of this complexity. At this
writing, it has:
• 263 classes
• 2455 objects
• 117 conditions
• 103 tables
• 11 alias
• 293 joins
• 7 contexts
• 12 hierarchies
The universe is well documented and logically organized to help universe
users easily navigate to a specific object.
The information in this chapter is useful to understand the data in the Rapid
Mart and how to build reports using the data. The universe, and this chapter,
are logically grouped into subject areas. They are:
• Universe Objects & Classes
• Common Dimensions
• Milestone
• Network Order
Universe
SAP Project System Universe 5
• Network Relationship
• Project Cost Summary (Horizontal)
• Project Cost Summary (Vertical)
• PRT Assignment
• Order Operation
• Filters & Techniques
• Universe Validation
5 Universe
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:
Measures: The first Top Level class represents the Measures as described in
“Universe Terminology” on page 145. Measures are grouped into sub-folders
that represent the various monetary and quantity amounts of the fact tables in
the star schemas.
Universe
Each subject area is further divided into classes by types of measure specific
to the subject area.
Common Dimensions: These top level classes appear after the Measures.
These are the dimensions used in common by more than one subject area.
These are sub-divided into classes for each specific dimension table.
For example, the Organization Structure class has sub-classes for Company
Code, and Controlling Area. Each of these represents a specific dimension
table or alias of a dimension table. The Common Dimensions Matrix
(presented later in this chapter) details which subject areas can be used with
which common dimensions.
Fact Tables: Following the Dimensions are group of Top Level classes, one
for each subject area (also called fact table or star schema) in the universe.
These subject area classes are further divided into classes that are logical
groupings of fact table attributes. For example, the “Milestone - Dates and
Fiscal Periods” class under “MILESTONE” contains the dates that are
important for tracking project milestones.
Filters & Techniques:
Filters: This top level folder represents pre-defined conditions that can be
included in any report. Again, they are organized by subject area.
Techniques: These are advanced technique objects that have developed for
the Web Intelligence reports. See “Techniques” on page 149 for details.
5 Universe
Common Dimensions
Common Dimensions are those dimensions shared by more than one subject
area (or fact table). They appear as shown below in the universe.)
Note: PEOPLE follows ORGANIZATION

STRUCTURE
Universe
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.
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
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.
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.
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.
5 Universe
Reference Date Key

Key determining the reference date for various entities - Milestone, PRT -
Domain MLST_SDDAT; TCA55
Standard Text Key
Standard text Key descriptions for activities from T435T.
ACCOUNTING DOCUMENT ATTRIBUTES
• Financial Management Area - FM01T - Funds Management
Area Texts.
• Financial Record Category - Categorization for a financial
document.
• Financial Record Type - Special Ledger Record Types (Domain
RRCTY) from table DD07T and Cost/Plant Maintenance value
types from CO_WRTTP domain of DD07T table
PURCHASING DOCUMENT ATTRIBUTES
• Account Assignment Category - A key indicating whether an
item is to be assigned to an auxiliary account (such as a cost
center). The account assignment category determines which
account assignment details are required for the item (for
example, cost center or account number).
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. Monitor the costs of short-term measures
2. Monitor the costs and revenues related to a specific service
3. Monitor ongoing costs
Internal orders are divided into the following categories:
1. Overhead orders
2. Capital investment orders
3. Accrual orders
4. Orders with revenues.
Internal Order Status
Internal Order status name and description from TKO04.
Universe
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.
Material (Product) Hierarchy
Materials can be grouped into hierarchies. Every material (product) can
be assigned to one material product hierarchy level.
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:
Monetary Currencies
The Rapid Marts maintain various currencies, including:
• Local (Company Code) Currency - The monetary currency
assigned to the company code
5 Universe
• Transaction (Document) Currency - The monetary currency of

each individual transaction document.
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.
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
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.
Universe
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:
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.
5 Universe
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.
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.
Plant
In Logistics a plant is an organizational unit for dividing an enterprise
according to production, procurement, maintenance, and materials
planning. A place where materials are produced, or goods and services
are provided.
Plant Location
Plant location attributes.
Purchase 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.
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.
Valuation Area
An organizational unit in Logistics subdividing an enterprise for the
purpose of uniform and complete valuation of material stocks.
Universe
PEOPLE
People dimensions describing persons with specific job functions in an
operational setting:
• Service Person - An employee who is actively involved in
troubleshooting, maintenance, and repair activities.
PRODUCTION & PLANT MAINTENANCE
Attributes associated Production Planning and Plant Maintenance functions.
The sub-classes include:
Control Key
A key that specifies how an operation or a sub-operation is processed in
functions such as orders, costing or capacity planning.
The following are examples of processing types managed by a control
key for operations and sub-operations:
• External processing
• Completion confirmation
• Printing
• Scheduling
• Costing
Production Scheduler
Production scheduler descriptive attributes from T024F
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
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
You can calculate the following variance categories on the output side:
5 Universe
• Fixed cost variance (only in Overhead Cost Controlling)

• Mixed price variance (only in Product Cost Controlling)
• Output price variance
• Output quantity variance (only in Overhead Cost Controlling)
• Lot size variance (only in Product Cost Controlling)
• Remaining variances
PROFIT 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-of-
sales approach or the period accounting approach.
By analyzing the fixed capital as well, you can expand your profit centers for
use as investment centers.
PROJECT
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.
PROJECT SYSTEM
Dimensions related to project system, including milestones, network
relationships, network profile, and project progress. This class contains the
following sub-classes:
Cost Object Indicator
An object in cost accounting to which costs can be assigned to reflect
how they are incurred.
Financing Code
Fund Management - FIFM: Financing code from FMFINCODE source
table.
Universe
Milestone Status Profile
A combination of system and user statuses you define as selection
conditions and use to select data in the project information system and to
trigger predefined milestone functions.
Milestone Usage
Milestone usage descriptive attributes from T433T.
Network Hierarchy (Vertical)
Hierarchical view of the object containing instructions on how to perform
tasks in a specific way, in a specific order, and in a specific time period.
Network Profile
Network profile contains default values and control parameters for
processing objects and functions in the Project System.
Network Relationship Type
activities in a network or a standard network. Network relationship types
include the following:
Pegging Object
An object that has a relationship between receipt elements and issue
elements of a product in a location.
Progress Measure Method
Descriptive attributes for PS object progress measurement methods from
EVOP.
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
5 Universe
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
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
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.
Universe
Fiscal years are divided into halves, quarters, periods, and months for
reporting purposes. Fiscal years and fiscal calendars are defined by the
fiscal year variant.
There can be 12 regular fiscal periods, and 4 special processing periods.
Fiscal periods are numbered 1 - 12 for regular periods, 13 -16 for special
periods.
UNIT OF MEASURE (UOM)
Unit that enables you to determine the size of a quantity of material.
Examples: Each, Piece, Dozen, Kilogram, ounce, liter, centimeter, minute,
hour, etc. It includes these sub-classes:
• Base Unit of Measure
• Duration Unit of Measure
• Offset Unit of Measure
• Time Interval Unit of Measure
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.
5 Universe
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 MILE- NETWORK ORDER PRODUC- PROJECT PROJECT PRT_

Table STONE RELATION OPERA- TION COST COST ASSIGN-
- SHIP TION ** ORDER SUMMARY SUMMARY MENT
(Horizontal (Vertical)
)
Acct X
Assignment
Category
Activity & X X X
Hierarchy
Business X X
Activity
Business Area X X X X X X
Chart Of X X X X
Accounts
Company Code X X X X X X X
Control Key X X X
Controlling X X X X X X X
Area
Cost Center & X X
Hierarchy
Cost Element & X X X X
Hierarchy
Cost Object X X
Indicator
Currency X X X X
Document X
Category
Document Type X
Financial Mgmt X X
Area
Universe
)
Financial X X
Record
Category
Financial X X
Record Type
Financing Code X X
Fisc Period X
Formula
Parameter
Functional Area X X X X X X
& Hierarchy
Internal Order X X X X X
& Hierarchy
Internal Order X
Status
Material X X
Material Batch X
Material By X
Plant
Material Group X
Material Type X
Milestone X
Usage
Mrp Controller X X X
Network Hier Vr X
Network Profile X X
Object Class X X
Object Number X X X X X
Type
Object Status X X X X X X
Object Status X X X X X X
Hz
5 Universe

)
Object Type X X
Operation X
Suitability
Order X X X X X X
Operation
Pegging Object X X
Plant X X X X X X X
Plant Location X X X
Product X X
Hierarchy
Production X
Scheduler
Profit Center & X X X X X X
Hierarchy
Progress X X
Measure
Method
Project X X X X X X X
Project X X X X X X X
Element &
Hierarchy
Prt Category X
Prt Grouping X
Key
Prt Master X
Prt Status X
Purch X X X X X X
Organization
Reference Date X X
Key
Relationship X
Type
Routing X X X X
Universe
)
Routing X X
Operation
Routing X X
Sequence
Service Person X
Special X
Procurement
Type
Standard Text X
Key
Status Profile X
Storage X X X
Location
System X
Condition
Task List Type X X X
Task List Usage X
Time Dim X X X X
Unit Of X X X X
Measure
Valuation Area X X X X X
Variance X X
Category
Work Center & X X X X
Hierarchy
Work Center X X X
Category
Work Center X
Formula
** ORDER_OPERATION_FACT is included in the universe as an alias of
ORDER_OPERATION and constitutes a subject area in the universe.
5 Universe
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.
Universe
Milestone
the completion of a project phase. Milestones are used:
• For progress analysis
• As release stop indicators
• To trigger predefined functions and workflow tasks
Read on for descriptions of Milestone classes in the SAP Project System
universe.
Milestone Measures
The Milestone measures contain all additive and semi-additive measures for
Milestones. They appear as shown below in the universe:
Milestone Measures includes count and average percent complete and offset.
It also contains the following sub-classes are included to group like
measures.
• Milestone - Qty Measures - aggregated Milestone offset quantities.
• Milestone - Time Measures - aggregated Milestone days, hours,
and seconds. Measures are further grouped in sub-classes for:
• Actual
• Difference Scheduled
• Difference Basic
5 Universe
• Difference Forecast
• Scheduled
Milestone Subject Area Classes

The Milestone subject area classes contain all objects for Milestone. They
appear as shown below in the universe
Milestone
Contains primary key elements for milestones and the following sub-classes:
• Milestone - Additional Details (Ids) - the foreign keys to the various
associated dimensions
• Milestone - Additional Details (Descriptive) - descriptive attributes
including the various “flags”
• Milestone - Dates and Fiscal Periods - dates associated with the
Milestones, including actual, fixed, forecast, and scheduled end dates.
Universe
• Milestone - Values - all numeric values and time amounts related to
Milestones, including percent complete and percent offset. (no
aggregation).
• Milestone - Quantities - Milestone offset quantity
• Milestone - Time - Milestone days, hours, and seconds (no
aggregation).
Milestone Star Schema Layout

Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer.
Network Order
SAP Applications system. Network orders are a shared component and are
used by both the SAP BusinessObjects Production Planning Rapid Mart,
version for SAP solutions and SAP BusinessObjects Project Systems Rapid
Mart, version for SAP solutions. The target table for network order records is
PRODUCTION_ORDER_FACT.
Note: NETWORK_ORDER_FACT (used in the universe) is an alias of
PRODUCTION_ORDER_FACT.
Read on for descriptions of Network Order classes in the SAP Project System
universe.
5 Universe
Network Order Measures

The Network Order measures contain all additive and semi-additive
measures for Network Order. They appear as shown below in the universe:
The following sub-classes are included to group like measures.

• Network Order - Qty Measures- aggregated quantities for Network
Orders, including total, produced and scrap quantities.
• Network Order - Time Measures - aggregated time measures for
Network Orders, including time variance measures (actual vs. scheduled)
and days goods receipt. Additional sub-classes include:
• Network Order - Actual - actual duration measures
• Network Order - Early - early duration measures
• Network Order - Scheduled - scheduled duration measures
• Network Order - Late - late duration measures
Universe
Network Orders Subject Area Classes
The Network Orders subject area classes contain all remaining objects for
Network Orders. They appear as shown below in the universe
Network Order
Contains primary key elements for Network Orders and the following sub-
classes:
• Network Order - Additional Details (Ids) - the foreign keys to the
various associated dimensions
• Network Order - Additional Details (Descriptive) - descriptive
attributes including the various “flags”
• Network Order - Dates and Fiscal Periods - dates associated with the
Network Order.
• Network Order - Values -
• Network Order - Quantities - order, scrap, and produced quantities
(no aggregation).
• Network Order - Time - goods receipt processing, days receipt and
stock coverage (no aggregation).
5 Universe
Network Order Star Schema Layout

it appears in the universe designer
Network relationships describe the link between the start and finish points of
two activities in a network and determine the sequence of activities. A
Network Relationship is a way of linking related Order Operations by one of
four methods:
Read on for descriptions of Network Relationship classes in the SAP Project
System universe.
Universe
Network Relationship Measures
The Network Relationship measures contain all additive and semi-additive
measures for Network Relationships. They appear as shown below in the
universe:

• Network Relationship - Qty Measures - Average and total interval
quantities (with aggregation).
• Network Relationship - Time Measures - aggregated relationship
duration in days, hours, and minutes as follows:
• Minimum
• Maximum
• Earliest
• Latest
5 Universe
Network Relationship Subject Area Classes

The Network Relationship subject area classes contain all remaining objects
for Network Relationships. They appear as shown below in the universe.
Contains primary key elements for Network Relationships and the following
sub-classes:
• Network Relationship - Additional Details (Ids) - the foreign keys to
the various associated dimensions
• Network Relationship - Additional Details (Descriptive) - descriptive
• Network Relationship - Dates and Fiscal Periods - dates associated
with the Network Relationship.
• Network Relationship - Values -
• Network Relationship - Quantities - relationship interval quantities
(no aggregation).
• Network Relationship - Time - earliest and latest relationship
duration values (no aggregation).
Universe
Network Relationship Star Schema Layout
Project Cost Summary (Horizontal)

achieving comprehensive cost accounting. Here, cost data is represented in
horizontal format, or one row for each fiscal year with 16 columns for each
Read on for descriptions of Project Cost Summary (horizontal) classes in the
SAP Project System universe.
5 Universe
Project Cost Summary (Horizontal) Measures

The Project Cost Summary (Horizontal) measures contain all additive and
semi-additive measures for Project Cost Summary (Horizontal). They appear
as shown below in the universe:

• Project Cost Sum - Hz Actual Measures - Actual cost measures
included in multiple currencies:
• Project Cost Sum - Hz Actual Measures LOC - Local Currency
• Project Cost Sum - Hz Actual Measures TRX - Transaction Currency
• Project Cost Sum - Hz Budget Measures - Budget cost measures
• Project Cost Sum - Hz Budget Measures LOC - Local Currency
• Project Cost Sum - Hz Budget Measures TRX - Transaction
Currency
Universe
Project Cost Summary (Horizontal) Subject Area Classes
The Project Cost Summary (Horizontal) subject area classes contain all
remaining objects for Project Cost Summary (Horizontal). They appear as
shown below in the universe
PROJECT COST SUMMARY - Horizontal

Contains primary key elements for Project Cost Summary - Horizontal and the
• Project Cost Summary (Horizontal) - Additional Details (Ids) - the
foreign keys to the various associated dimensions
• Project Cost Summary (Horizontal) - Dates and Fiscal Periods -
dates related to project cost summary.
• Project Cost Sum Hz - Values
• Project Cost Sum Hz - Local Currency Values- cost summary
amounts in local currency (no aggregation).
• Project Cost Sum Hz - Transaction Currency Values- cost
summary amounts in transaction currency (no aggregation).
Project Cost Summary (Horizontal) Star Schema Layout

5 Universe
Universe
Project Cost Summary (Vertical)
achieving comprehensive cost accounting. Here, cost data is represented in
vertical format or one row for each fiscal year and fiscal period. There are 16
rows per fiscal year, one for each fiscal period. Each row has individual
Read on for descriptions of Project Cost Summary (vertical) classes in the
SAP Project System universe.
Project Cost Summary (Vertical) Measures

The Project Cost Summary (Vertical) measures contain all additive and semi-
additive measures for Project Cost Summary (Vertical). They appear as
shown below in the universe:

• Project Cost Sum - Vr Actual Measures - Actual cost measures
• Project Cost Sum - Vr Actual Measures LOC - Local Currency
• Project Cost Sum - Vr Actual Measures TRX - Transaction Currency
• Project Cost Sum - Vr Budget Measures - Budget cost measures
• Project Cost Sum - Vr Budget Measures LOC - Local Currency
• Project Cost Sum - Vr Budget Measures TRX - Transaction Currency
5 Universe
Project Cost Summary (Vertical) Subject Area Classes

The Project Cost Summary (Vertical) subject area classes contain all objects
for Project Cost Summary (Vertical). They appear as shown below in the
universe
PROJECT COST SUMMARY - Vertical

Contains primary key elements for Project Cost Summary - Vertical and the
• Project Cost Sum Vr - Additional Details (Ids) - the foreign keys to the
• Project Cost Sum Vr - Dates and Fiscal Periods - dates related to
project cost summary.
• Project Cost Sum Vr - Values
• Project Cost Sum Vr - Local Currency Values- cost summary
amounts in local currency (no aggregation).
• Project Cost Sum Vr - Transaction Currency Values- cost
summary amounts in transaction currency (no aggregation).
Universe
Project Cost Summary (Vertical) Star Schema Layout
PRT Assignment
Production resources and tools (PRTs) are movable (not stationary) operating
resources that are required to perform an activity and can be used repeatedly.
For example, PRTs include documents, engineering drawings, and
measurement instruments.
Read on for descriptions of PRT Assignment classes in the SAP Project
System universe.
5 Universe
PRT Assignment Measures

The PRT Assignment measures contain all additive and semi-additive
measures for PRT Assignment. They appear as shown below in the universe:

• PRT Assignment - Qty Measures - quantities for PRT Assignment
• PRT Assignment - Time Measures - time-related measures for PRT
Assignment, including the following sub-classes:
• PRT Assignment - Actual - actual duration measures
• PRT Assignment - Earliest - early duration measures
• PRT Assignment - Latest - late duration measures
• PRT Assignment - Min - minimum duration measures
• PRT Assignment - Max - maximum duration measures
Universe
PRT Assignment Subject Area Classes
The PRT Assignment subject area classes contain all remaining objects for
PRT Assignment. They appear as shown below in the universe
PRT Assignment
Contains primary key elements for PRT Assignment and the following sub-
classes:
• PRT Assignment - Additional Details (Ids) - the foreign keys to the
• PRT Assignment - Additional Details (Descriptive) - descriptive
• PRT Assignment - Dates and Fiscal Periods - dates associated with
the PRT Assignment, including actual and scheduled start and end dates.
• PRT Assignment - Values
• PRT Assignment - Quantities - offset, duration, and PRT quantities
(no aggregation)
• PRT Assignment - Time - Minimum, maximum, earliest, and latest
days, hours, and minutes duration (no aggregation).
5 Universe
PRT Assignment Star Schema Layout

Universe
Order Operation
Detail for activity sequence in a workstep in a plan or work order. Included as
a subject area in the universe for detail analysis of order operations.
ORDER_OPERATION_FACT is an alias of the ORDER_OPERATION
dimension.
Read on for descriptions of Order Operation classes in the SAP Project
System universe.
Order Operation Measures

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

• Order Operation - Currency TRX - Aggregated order operation costs,
including material cost, total cost, and price.
5 Universe
Order Operation Subject Area Classes

The Order Operation subject area classes contain all remaining objects for
Order Operation. They appear as shown below in the universe.
Order Operation
Contains primary key elements for Order Operation and the following sub-
classes:
• Order Operation - Additional Details (Ids) - the foreign keys to the
• Order Operation - Additional Details (Descriptive) - descriptive
• Order Operation - Dates and Fiscal Periods - dates associated with
the Order Operation.
• Order Operation - Values -
• Order Operation - Transaction Currency Values - order operation
costs, including material cost, total cost, and price (no aggregation).
Universe
Order Operation Star Schema Layout
5 Universe
Filters & Techniques

Filters
The SAP Project System universe contains filters that allow you to restrict the
results of your reports. The filters appear after the Fact Table Classes in the
universe.:
Each of the classes below contain filters that allow you to limit the
dimensional and hierarchy attributes selected to certain values.
Using these prompts in Web Intelligence prompts users to enter values at
report run time for: a single value, a range of values, or a list of multiple
values.
Universe
Company Code Filters
Conditions to limit result set to either a single or multiple Company
Codes.
Financial Document Type Filters
Conditions to limit result set based on type of financial document.
Fiscal Period Filters
Conditions to limit to single fiscal year, single fiscal year-period, multiple
fiscal years, or multiple fiscal year-periods.
Hierarchy Filters
All hierarchy filters provide two groups of conditions “Limit to Single
Parent” and “Limit to Multiple Parent” sub-classes. Each of the conditions
provided here allows the user to choose the level of the parent node (0 -
4)in the hierarchy tree. This universe provides the following hierarchy
filters:
• Internal Orders Hierarchy - Limit result set to a single or multiple
Internal Order parent node(s)
• Cost Center Filters - Limit result set to a single or multiple Cost
Center parent node(s)
• Work Center Filters - Limit result set to a single or multiple Work
Center parent node(s)
Project Filters
Conditions to limit to a single project, a single WBS Project Element, or
multiple WBS Project Elements.
Project Cost Summary HZ Filters
Conditions to limit project cost data by actual, budget, ledger version,
single fiscal year, multiple fiscal years, or a fiscal year range.
Project Cost Summary VR Filters
Conditions to limit project cost data by actual, budget, or ledger version.
Techniques
Techniques are advanced technique objects developed for the Web
Intelligence reports. They are described in “Techniques” on page 17.
5 Universe
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.
Integrity Check Results.
Structure Divergences
Some tables are not joined to other tables. This is because we use only
aliases of those tables in the universe. However, the original table must
remain as a placeholder for the original table name. Also, validation tables
(those ending in “_BAD”) are not joined to other tables.
Object Parsing Errors

These objects are in the Techniques section and are represented by valid
SQL. These objects are included in the universe to accommodate advanced
reporting techniques primarily in Web Intelligence and will work properly when
used with other objects in a query.
Cardinality Divergences
These are caused by the use of the “@prompt” function in the join. Since this
function requires user intervention to complete the SQL join condition, the
Universe Designer cannot check the cardinality vs. the database.
The error messages are specific to your database server. Thus Oracle, SQL-
Server, and DB2 will have different messages for the same errors.
Universe
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
• 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
5 Universe
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_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
Universe
(
( ACTIVITY_HIER_VR.ANCESTOR_ID in ('A1') AND
ACTIVITY_HIER_HR.LEVEL_0_ID in ('A1') )
AND
ACTIVITY_HIER_HR.CTRL_AREA_ID = '1000'
AND
ACTIVITY_HIER_HR.CTRL_AREA_ID <> '?'
AND
ACTIVITY_HIER_HR.LEVEL_0_ID <> '?'
)
Cost Center Hierarchy Data Discovery

View Cost Center Hierarchies for a specified Controlling Area, Parent Cost
Center, and Cost Center Hierarchy.
Report SQL
"\Sample\DML".
5 Universe
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
"\Sample\DML".
Cost Element Hierarchy Data Discovery

View Cost Element Hierarchies for a specified Chart of Accounts, Parent Cost
Element, and Cost Element Hierarchy.
Report SQL
"\Sample\DML".
Universe
Internal Order Hierarchy Data Discovery
View Internal Order Hierarchies for a specified Controlling Area, Parent
Internal Order, and Internal Order Hierarchy.
Report SQL
"\Sample\DML".
5 Universe
Functional Area Hierarchy Data Discovery

View Functional Area Hierarchies for a specified Parent Functional Area and
Functional Area Hierarchy.
Report SQL
"\Sample\DML".
Universe
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
"\Sample\DML".
5 Universe
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
Universe
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
AND
AND
AND
)
5 Universe
Project Element Hierarchy Data Discovery

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

View Equipment Hierarchies for a specified Parent Equipment and Equipment
Hierarchy.
Report SQL
"\Sample\DML".
Universe
Functional Location Hierarchy Data Discovery
View Functional Location Hierarchies for a specified Parent Functional
Location and Functional Location Hierarchy.
Report SQL
"\Sample\DML".
Work Center Hierarchy Data Discovery

View Work Center Hierarchies for a specified Parent Work Center and Work
Center Hierarchy.
Report SQL
"\Sample\DML".
5 Universe
BOM Hierarchy Data Discovery

View BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.
Report SQL
"\Sample\DML".
Universe
Organization Unit Data Discovery
View Organization Unit Hierarchies for a specified Parent Organization
Unit(s).
Report SQL
"\Sample\DML".
Position Data Discovery

View Position Hierarchies for the specified Parent Position(s).
Report SQL
"\Sample\DML".
5 Universe
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 Data Table

Invalid Cost Center Hierarchy COST_CENTER_HIER_BAD
Invalid Activity Hierarchy ACTIVITY_HIER_BAD
Invalid Cost Element Hierarchy COST_ELEMENT_HIER_BAD
Invalid Functional Area Hierarchy FUNCTIONAL_AREA_HIER_BAD
Invalid GL Account Hierarchy GL_ACCOUNT_HIER_BAD
Invalid Internal Order Hierarchy INTERNAL_ORDER_HIER_BAD
Invalid Profit Center Hierarchy PROFIT_CENTER_HIER_BAD
Invalid Project Element Hierarchy PROJECT_ELEMENT_HIER_BAD
Invalid Work Center Hierarchy 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,
Universe
COST_CNTR_HIER_BAD.CHILD_DESC,
COST_CNTR_HIER_BAD.DI_ERRORACTION,
COST_CNTR_HIER_BAD.DI_ERRORCOLUMNS,
COST_CNTR_HIER_BAD.LEAF_FLAG,
COST_CNTR_HIER_BAD.LOAD_DATE,
COST_CNTR_HIER_BAD.LOAD_TIME,
COST_CNTR_HIER_BAD.ROOT_FLAG
FROM
COST_CNTR_HIER_BAD
Recommended table joins

When analyzing data hierarchy data, you need to create joins between the
dimension table and the hierarchy tables in the Rapid Mart. The following
shows joins provided in the SAP Master Data universe.
ACTIVITY ACTIVITY_HIER_HZ ACTIVITY.CTRL_AREA_ID=ACTIVITY_HIER_H
Z.CTRL_AREA_ID and
ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HZ.A
CTIVITY_ID
ACTIVITY ACTIVITY_HIER_VR ACTIVITY.CTRL_AREA_ID =
ACTIVITY_HIER_VR.CTRL_AREA_ID and
ACTIVITY.ACTIVITY_ID =
R_HZ OF_MATERIALS_HIER_HZ.BOM_CATEG_ID
and
ERIALS_HIER_HZ.BOM_ID and
MATERIALS_HIER_HZ.ALT_BOM_ID and
F_MATERIALS_HIER_HZ.BOM_NODE_ID
R_VR OF_MATERIALS_HIER_VR.BOM_CATEG_ID
and
ERIALS_HIER_VR.BOM_ID and
MATERIALS_HIER_VR.ALT_BOM_ID and
F_MATERIALS_HIER_VR.CHILD_ID
COST_CENTER COST_CENTER_HIER_HZ COST_CENTER.CTRL_AREA_ID=COST_CENT
ER_HIER_HZ.CTRL_AREA_ID and
TER_HIER_HZ.COST_CNTR_ID
5 Universe

COST_CENTER COST_CENTER_HIER_VR COST_CENTER.CTRL_AREA_ID=COST_CENT
ER_HIER_VR.CTRL_AREA_ID and
TER_HIER_VR.CHILD_ID
COST_ELEMENT COST_ELEMENT_HIER_H COST_ELEMENT.COST_ELEM_ID=COST_ELE
Z MENT_HIER_HZ.COST_ELEM_ID and
COST_ELEMENT.CHART_OF_ACCT_ID=COST
_ELEMENT_HIER_HZ.CHART_OF_ACCT_ID
COST_ELEMENT COST_ELEMENT_HIER_V COST_ELEMENT.CHART_OF_ACCT_ID=COST
R _ELEMENT_HIER_VR.CHART_OF_ACCT_ID
and
COST_ELEMENT.COST_ELEM_ID=COST_ELE
MENT_HIER_VR.CHILD_ID
COUNTRY_GROUP COUNTRY_GROUP_STAT COUNTRY_GROUP.COUNTRY_GRP_ID =
US COUNTRY_GROUP_STATUS.COUNTRY_GRP
_ID
EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIE
R_HZ.EQUIPMNT_ID
EQUIPMENT EQUIPMENT_HIER_VR EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIE
R_VR.CHILD_ID
FS_HIERARCHY GL_ACCOUNT_HIER_HZ GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_I
GL_ACCOUNT_HIER_HZ.HIER_ID=FS_HIERA
GL_ACCOUNT_HIER_HZ.GL_ACCT_ID=FS_HI
ERARCHY.CHILD_ID
FS_HIERARCHY GL_ACCOUNT_HIER_VR GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I
GL_ACCOUNT_HIER_VR.HIER_ID=FS_HIERA
GL_ACCOUNT_HIER_VR.CHILD_ID=FS_HIER
ARCHY.CHILD_ID
_HZ NCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA
_ID
_VR NCTIONAL_AREA_HIER_VR.CHILD_ID
HIER_HZ _ID=FUNCTIONAL_LOCATION_HIER_HZ.FUN
CTNL_LOCATN_ID
HIER_VR _ID=FUNCTIONAL_LOCATION_HIER_VR.CHIL
D_ID
GL_ACCOUNT_HIER GL_ACCOUNT_HIER_HZ GL_ACCOUNT_HIER_HZ.HIER_ID=GL_ACCO
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCT_I
and
GL_ACCOUNT_HIER_HZ.GL_ACCT_ID=GL_A
CCOUNT_HIER.CHILD_ID
Universe
GL_ACCOUNT_HIER GL_ACCOUNT_HIER_VR GL_ACCOUNT_HIER_VR.HIER_ID=GL_ACCO
GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I
and
GL_ACCOUNT_HIER_VR.CHILD_ID=GL_ACC
OUNT_HIER.CHILD_ID
GL_ACCOUNT_MASTER GL_ACCOUNT_HIER_HZ GL_ACCOUNT_MASTER.CHART_OF_ACCT_I
D=GL_ACCOUNT_HIER_HZ.CHART_OF_ACC
T_ID and
CCOUNT_HIER_HZ.GL_ACCT_ID AND
GL_ACCOUNT_HIER_HZ.HIER_ID =
Code','A','GL Account Hierarchy Hz\Hierarchy
Name',mono,free)
GL_ACCOUNT_MASTER GL_ACCOUNT_HIER_VR GL_ACCOUNT_MASTER.CHART_OF_ACCT_I
D=GL_ACCOUNT_HIER_VR.CHART_OF_ACC
T_ID and
CCOUNT_HIER_VR.CHILD_ID AND
GL_ACCOUNT_HIER_VR.HIER_ID =
Code','A','GL Account Hierarchy Vr\Hierarchy
Name',mono,free)
HZ TERNAL_ORDER_HIER_HZ.INTERNAL_ORDE
R_ID
VR TERNAL_ORDER_HIER_VR.CHILD_ID
MATERIAL PRODUCT_HIERARCHY MATERIAL.PROD_HIER_ID=PRODUCT_HIERA
RCHY.PROD_HIER_ID
OBJECT_STATUS_HZ OBJECT_STATUS OBJECT_STATUS_HZ.OBJ_ID=OBJECT_STAT
US.OBJ_ID
ORGANIZATION_UNIT ORGANIZATION_UNIT_HIE ORGANIZATION_UNIT.ORG_UNIT_KEY
R_HZ =ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT
_KEY
ORGANIZATION_UNIT ORGANIZATION_UNIT_HIE ORGANIZATION_UNIT.ORG_UNIT_KEY=ORG
R_VR ANIZATION_UNIT_HIER_VR.CHILD_KEY
PAYROLL_PERIOD PAYROLL_PERIOD_PARA PAYROLL_PERIOD.PERIOD_PARAMETER_ID
METER =
PAYROLL_PERIOD_PARAMETER.PERIOD_PA
RAMETER_ID
5 Universe

POSITION POSITION_HIER_HZ POSITION.POSITION_ID=POSITION_HIER_HZ
.POSITION_ID
POSITION POSITION_HIER_VR POSITION.POSITION_ID=POSITION_HIER_VR
.CHILD_ID
PROFIT_CENTER PROFIT_CENTER_HIER_H PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C
Z ENTER_HIER_HZ.CTRL_AREA_ID and
_CENTER_HIER_HZ.PROFIT_CNTR_ID
PROFIT_CENTER PROFIT_CENTER_HIER_V PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C
R ENTER_HIER_VR.CTRL_AREA_ID and
_CENTER_HIER_VR.CHILD_ID
R_HZ CT_ELEMENT_HIER_HZ.PROJ_ELEM_ID
R_VR CT_ELEMENT_HIER_VR.CHILD_ID
WORK_CENTER WORK_CENTER_HIER_HZ WORK_CENTER.WORK_CNTR_ID=WORK_CE
NTER_HIER_HZ.WORK_CNTR_ID and
HIER_HZ.PLANT_ID
WORK_CENTER WORK_CENTER_HIER_VR WORK_CENTER.WORK_CNTR_ID=WORK_CE
NTER_HIER_VR.CHILD_ID AND
HIER_VR.PLANT_ID
Universe
Customizing the Universe 5
Customizing the Universe
The SAP Project System Universe can be modified easily to suit your specific
needs. Here is an example:
Splitting the SAP Project System Universe

The SAP Project System Universe, contains several subject areas. Suppose
your company wants a new universe with just the Milestone subject area
while keeping the original universe as is. You can follow these steps to create
two universes:
1. Create a copy of the SAP Project System Universe with file name:
• SAP-PS-Milestones.unv
2. In the Universe Parameters, Definition tab, change the name of the
universe to:
• SAP Project - Milestones
3. Go to the graphic representation of the universe, right click on
NETWORK_ORDER_FACT and choose view associated objects. This
will highlight a number of objects in left hand pane of the Universe
Designer. These object should be deleted from the universe. Also delete
any empty top level classes that remain for the objects after deletion.
4. Repeat previous step for
• PROJECT_COST_SUMMARY_FACT_HZ
• PROJECT_COST_SUMMARY_FACT_VR
• ORDER_OPERATION_FACT
5. Delete these tables from the graphic representation of the universe:
• NETWORK_ORDER_FACT
• PROJECT_COST_SUMMARY_FACT_HZ
• PROJECT_COST_SUMMARY_FACT_VR
6. All joins associated with these tables will be deleted as you delete the
tables.
5 Universe
Customizing the Universe
7. In the graphic representation, find all dimension tables not joined to a fact
table. For each of these tables, right click on the table and choose view
associated objects. Delete these objects from the universe. Also delete
any empty top level classes for the objects.
8. If the un-joined dimensions have associated hierarchy tables you should
delete all associated hierarchy objects and empty top level classes as
well.
9. In the graphic representation, delete all dimension tables not joined to a
fact table. This includes their associated hierarchy tables. Any joins
between dimensions and hierarchies will also be deleted automatically
when you do this.
10. Delete the following contexts in the universe:
• NETWORK_ORDER_FACT
• PROJECT_COST_SUMM_VR
• PROJECT_COST_SUMM_HZ
11. Validate and test the universe
Installing the Rapid Mart
chapter
6 Installing the Rapid Mart
Overview
Overview
This chapter contains the information you need to install the SAP
BusinessObjects Project Systems 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
System Prerequisites 6
System Prerequisites
To run the SAP BusinessObjects Project Systems 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.
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
• BusinessObjects Enterprise
• Universe Designer
• Web Intelligence Query Designer
For additional support we recommend expertise in:
• SAP solutions Administration (BASIS)
• Target Database DBA (Database Administration)
Rapid Mart product components 6
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
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.
Preparing your environment 6
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.
Preparing your environment
• 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
Preparing your environment 6
• Reporting query volumes and most frequently used subject areas
• Hardware configuration and capacity for all servers involved:
• SAP solutions server(s)
• Data Services Job Server(s)
• Target Database Server(s)
• BusinessObjects Enterprise Server(s)
From this analysis you will be able to implement proper database storage
parameters and proper indexes for your environment.
It is invaluable to have a qualified DBA and appropriately trained technical
staff for this analysis.
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 SAPPS_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 233 and ReadMe.txt file.
Install the Rapid Mart Target Schema 6
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.
2. If your target database is DB2 without Code Set UTF-8 (without
multi-byte character support), you will need to edit the
SAP_Create_Tables.sql script. Change all occurrences of data type
VARGRAPHIC to VARCHAR before creating tables.
Install the Rapid Mart Target Schema
3. If your target database is DB2 with Code Set UTF-8 (with multi-byte
character support), you do not need to make changes to
SAP_Create_Tables.sql script.
4. If your target database is DB2, regardless of Code Set, you must have
at least one tablespace with page size = 8 Kilobytes to accommodate
column size (table width) on some tables. The tables affected by this are:
• COST_CENTER_HIER_HZ
• FUNCTIONAL_AREA_HIER_HZ
• GL_ACCOUNT_HIER_HZ
• PROFIT_CENTER_HIER_HZ
• PROJECT_ELEMENT_HIER_HZ
Create Target 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.
Install the Rapid Mart Target Schema 6
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 Oracle’s “create or replace” syntax. Thus, no drop script is provided
for Oracle.
• SAP_Drop_Indexes_All.sql
• SAP_Drop_Indexes_Performance.sql
• SAP_Drop_Tables.sql
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 260.
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
Example: The Project Systems Rapid Mart ATL file is named:
• SAPPS_Rapid_Mart.atl
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
Install the Data Services Job(s) 6
Before Replace All
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
SAPPS_Rapid_Mart.atl instead of the file name shown in the example.
• From the Tools Menu choose Import From File:
• Choose the ATL File
• Click “OK” to any warnings. You might get pop-up windows warning
that the import may take a long time, or that the ATL file was created with
a lower version of Data Services. Answer “OK” to any of these. This will
start the import process.
Data Services will import the ATL file, creating all the repository objects
required to run Rapid Mart load jobs.
Adjusting the Data 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:
Edit the Data Store:
Open “Advanced” Edit Window
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):
Edit the Data Store:
Open “Advanced” Edit Window
Edit Data Store Settings.
Example: If your target database is Oracle, you would only change settings
in “Configuration1” column. For SQL-Server, change only “Configuration2”
column, etc.
Note: For “RM_USER” alias, enter the target database schema owner:
• For SQL Server - “dbo”
• For Oracle and DB2 UDB - database user name
• For Teradata - the schema owner
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 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.
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.
At this writing, only four Rapid Marts use ABAP files
• SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions
solutions
• SAP BusinessObjects Human Resources Rapid Mart, version for SAP
solutions
solutions
If used, these files are located in:
• ...\ETL\Files\ABAP\
Some examples of the files found in the Cost Center and GL Rapid Marts are:
• RF011F_NEW.aba
• RF011F_OLD.aba
• RF011P_NEW.aba
• RF011P_OLD.aba
• etc.
Note: For SAP BusinessObjects Human Resources Rapid Mart, version
for SAP solutions Only: be sure to choose the correct files for your SAP
solutions version:
There are two versions of these files:
• PA0167_ABAPXFORM.aba
• PA0168_ABAPXFORM.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
All these files should be moved to the Generated ABAP directory you
specified when Adjusting the Data Stores, as shown below:
Then, make sure the Data Services transforms using these files point to the
Generated ABAP directory as shown below.
1. Open Data Services and navigate to the Transforms tab of the Local
Object Library:
Note: This step applies only to:

• SAP BusinessObjects Cost Center Rapid Mart, version for SAP
solutions
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.
2. Then, change path to be the same as where the ABAP files are installed
3. Repeat this step for all the other ABAP transforms in the Object Library
4. Save the changes
5. Validate the Data Services jobs to ensure they are working correctly.
Final Steps
• If your Job Server runs on a UNIX system, using Data Services Designer
adjust the directory paths in all Rapid Mart file format definitions to follow
the UNIX convention (that is, change from “/” to “\”).
• Before running the job, you must initialize some global variables. For
information about executing the Rapid Mart job, see Chapter 7: Using the
Rapid Mart.
• Rapid Marts are developed against standard out-of-the-box SAP
solutions installation. It is important that during the Rapid Mart
implementation you:
• Re-import all Rapid Mart source objects (tables, hierarchies,
functions, etc.) to have object customization captured;
• Review each Rapid Mart dataflow to make sure that its Query
transform(s) contain(s) proper constraints when extracting data from
the source tables. Adjust “WHERE” conditions in Query Transforms if
necessary. Look for hard-coded constraints and other conditions that
need to be customized.
Installing 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: sapps_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.
Installing Rapid Mart Reporting Content 6
On the first screen, click “Next”:
Choose BIAR File:
Note: The BIAR file for the SAP BusinessObjects General Ledger Rapid
Mart, version for SAP solutions is used in this illustration. You should
use the proper file for the Project Systems Rapid Mart located in
Directory: ...\Visuals
File: sapps_Rapid_Mart_Visuals.biar
Choose CMS:
Select Object to Import - Check or Uncheck Boxes:
Note: The number of boxes to check on this screen may vary between
BusinessObjects Enterprise releases.
Regardless of release, just make sure only the “import folders and objects”
box is checked.
Do not click “Next” on this screen. Proceed to next page.
Select Object to Import - Check or Uncheck Boxes (continued):
Note: The number of boxes to check on this screen may vary between
BusinessObjects Enterprise releases.
Regardless of release, just make sure only the “import universes” box is
checked.
Check Import Scenario Radio Buttons as shown
Note: This screen does not appear in SAP BusinessObjects Enterprise XI

Release 2
Incremental Import - Check or Uncheck Boxes:
Acknowledge Message, Click Next
“Select All” to import complete contents of BIAR file.
Universe & Connection Options- Check or Uncheck as shown
Ensure All Objects are Selected:
Write down universe names. There can be more than one universe per a
Rapid Mart. You will need these names later when creating Universe
connection.
Select Import Options for Publications:
Note: This screen does not appear in SAP BusinessObjects Enterprise XI

Release 2
Acknowledge message, Click “Next”:
Verify Correct List of Objects to Import, Click FINISH to start import:
Wait for Import to Finish. Then Click “View Detail Log”:
Click on each item imported. Make sure there are no errors:
Click Done to Exit the Import Wizard:
This completes the Import Wizard for Reporting Content.
Creating Universe Connection

Now use the Universe Designer to change the connection in the imported
universe(s).
Start the Universe Designer, and import the universe(s) by choosing File ->
Import. Select universe(s) you wrote down when importing the BIAR file in the
previous step and import all of them. Then, navigate to the Universe
Parameters Screen:
For each universe, either choose an existing connection to Rapid Mart

target database, or create a new one:
Note: This illustration uses the SAP BusinessObjects Accounts Receivable

Rapid Mart, version for SAP solutions as an example only. The Universe
Designer will show the correct universe name for your Rapid Mart
Note: Consult the SAP BusinessObjects Universe Designer Guide for
details on how to assign or create a connection.
When done, export the universe(s) back to the CMS by choosing File ->
Export in the Universe Designer.
This concludes Rapid Mart installation.
Using the Rapid Mart
chapter
7 Using the Rapid Mart
Recovery framework
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
• 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.
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.
Recovery framework 7
For example, suppose two tables contain related data but are loaded in
separate work flows. In this case, the job can fail after successfully
completing the work flow that loads the first table but before completing the
work flow that loads the second table. During recovery, Data 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 job’s execution and the
time data was extracted. By using the execution status table, the Rapid Mart
ensures that data for the proper dates is extracted from the source datastore.
With each incremental (or delta) execution, the Rapid Mart job extracts data
between a start date and an end date. This is determined by setting the global
variable $G_LOAD_TYPE = ‘DELTA’. If the job fails and is rerun on the same
or a subsequent day, the new job uses the failed job’s start date to ensure that
all the data is extracted contiguously.
Note: There are exceptions to this, as certain subject areas may have delta
loads that use a different methodology. Consult the Technical
Implementation chapter for details on the delta loads for each subject area.
Upon execution, a job first checks the status of the last execution of the job. If
the last execution failed, the job determines the ending date of the last
successful execution. This date becomes the starting date of the next
execution of the job. All work flows are re-executed using the same starting
date to ensure consistency. For example, if a failed job is restarted on the
same day (without using the automatic recovery feature), the restarted job
refreshes all tables because the last execution of the job on that day was not
successful.
If a job continues to fail over several days, the job would continue using the
same start date used on the first failed attempt. This ensures that when the
job is eventually successful, it extracts the complete set of data that changed
since the start date.
Execution status framework
To maintain consistency with data flowing to SAP solutions, the Rapid Mart
always overlaps one day’s worth of data in incremental loads. For example, if
the end date is June 3, the incremental load job extracts data entered or
changed on June 3. The next incremental load job extracts data starting with
the June 3 date.
Up to one day’s worth of duplicate data may be extracted each time the job
runs; however, work flows are designed to detect and delete duplicate data
from the target data table before reloading the refreshed data. To do this,
many work flows use the auto correct load option or the Table Comparison
transform. Both of these check for an existing row with the same key as each
row flagged as an insert or update activity. If the row exists, Data Services
updates the row. If the row does not exist, Data Services inserts the row.
Execution status framework

The Rapid Mart uses two mechanisms to check the job execution status and
control execution:
• An execution status table that stores one record for each job. That record
contains:
• Status of previous job execution
• Starting and ending times of the last attempted execution of the job
• An application programming interface (API) that updates the status table
and supports the implementation of restartable jobs and flows
The execution status 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 Description

NAME The name of the job being executed. If the same target datastore is
used for more than one repository, you must ensure that all job names
are unique.
STATUS The status of this job after the last execution. Possible status values are:
started, done, or none.
EXTRACTLOW Last attempted start date of data retrieval. This date is also the ending
date of the last successful run of the job.
EXTRACTHIGH Last attempted end date of data retrieval.
Execution status framework 7
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 job’s existing status. If the
previous execution of the job did not complete successfully—that is, the job
status is not done—the Rapid Mart resets the starting date for data extraction
($G_SDATE) from the value specified in the job initialization script to the
ending date of the last successful run (EXTRACTHIGH). You can override the
reassignment of the starting date by forcing the starting date to be reset. See
“Executing a job with the Reset option” on page 284. The Rapid Mart never
changes the ending value ($G_EDATE) from the value specified in the
initialization script.
After checking the job’s existing status, the Rapid Mart sets the status of the
job to started, and starts a new execution of the job.
When a job successfully completes, the Rapid Mart sets the job’s status to
done. If the job does not complete successfully, the job’s status remains set to
started. The EXTRACTLOW and EXTRACTHIGH dates remain set to the
current values.
The execution status 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.
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 job’s initialization script or execution properties
and set global variable $G_RUN_MODE = ‘RESET’. When using reset mode,
be sure that the global variables $G_SDATE and $G_EDATE are set so that
no gaps in data occur.
Extraction, transformation and loading

process
The job Project_Systems_Load executes objects that load the load the data
from SAP solutions to Rapid Mart target database. This job contains:
Extraction, transformation and loading process 7
• Job global variable properties. This window can be accessed by
right-clicking on the Project_Systems_Load job and selecting the
Properties command from the drop-down list. Most of the Project
Systems 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
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
Global Variables 7
The global variables in each of these sections are described in detail after the
matrix.
Global Variable Name Data AP AR CA GL HR IA PM PP PR PS SA

Type
Used in all 11 Rapid Marts
$G_CCODE varchar(4) X X X X X X X X X X X
$G_DEFAULT_DATE datetime X X X X X X X X X X X
$G_DEFAULT_NUMBER int X X X X X X X X X X X
$G_DEFAULT_TEXT varchar(1) X X X X X X X X X X X
$G_EDATE datetime X X X X X X X X X X X
$G_LANGUAGE varchar(1) X X X X X X X X X X X
$G_LOAD_DATE datetime X X X X X X X X X X X
$G_LOAD_TIME varchar(8) X X X X X X X X X X X
$G_LOAD_TYPE varchar(7) X X X X X X X X X X X
$G_MAX_DATE datetime X X X X X X X X X X X
$G_REBUILD_INDEXES varchar(1) X X X X X X X X X X X
$G_RUN_MODE varchar(10) X X X X X X X X X X X
$G_SDATE datetime X X X X X X X X X X X
Used in 2 to 10 Rapid Marts
$A int X X
$B int X X
$C int X X
$D int X X
$E int X X
$F int X X
$G int X X
$G_ABSOLUTE_START_DA datetime X X X X X
TE
$G_ENDFISCALYEAR int X X X X X X
$G_EXCHANGE_TYPE_ID varchar(4) X X X
$G_GLOBAL_CURRENCY varchar(5) X X X
$G_INT_ORDER_CATEG_P varchar(2) X X
P
$G_INT_ORDER_CATEG_P varchar(2) X X
S
$G_ORIG_SDATE datetime X X X
$G_STARTFISCALYEAR int X X X X X X
Global Variables

Type
Used in Only 1 Rapid Mart
$G_ADDRESS_VERSION varchar(1) X
$G_BUS_PARTN_SDATE datetime X
$G_BUS_PARTNER varchar(1) X
$G_COST_OF_SALES_LED varchar(2) X
GER_ID
$G_COUNTRY_GRP varchar(2) X
$G_DEL_PERIOD datetime X
$G_DEL_REJECT_REASON varchar(2) X
$G_DROP_SHIP varchar(1) X
$G_GL_ACCOUNT_HIER_N varchar(10) X
AME
$G_GL_SUM_PLAN_LEDGE varchar(2) X
R_ID
$G_GL_VERSION varchar(3) X
$G_HIRE_ACTION_01 varchar(2) X
$G_INIT_HIST_CHG varchar(1) X
$G_MALFUNCTION_CAUSE varchar(20) X
$G_MALFUNCTION_DAMAG varchar(20) X
E
$G_MALFUNCTION_OBJ_P varchar(20) X
ART
$G_MRP_RESULTS_DELET varchar(1) X
E
$G_ONTIME_DELIV_WINDO int X
W
$G_PC_ACCOUNT_HIER_N varchar(10) X
AME
$G_PROFIT_CENTER_LED varchar(2) X
GER_ID
$G_REHIRE_ACTION_01 varchar(2) X
$G_REHIRE_ACTION_02 varchar(2) X
$G_RETIRE_ACTION varchar(2) X
$G_SAP_VERSION int X
$G_SCHOOL_TYPE varchar(2) X
Global Variables 7
Type
$G_SERVICE_INTERVAL_01 int X
$G_TABLE_EQUIPMENT varchar(20) X
$G_TABLE_FUNCTL_LOCAT varchar(20) X
N
$G_TASK_TYPE_PROBATIO varchar(2) X
N_END
$G_TERMINATION_ACTION varchar(2) X
$G_VALID_DATE datetime X
$G_WAGE_TYPE_01 varchar(4) X
$G_WORKDAY_EDATE datetime X
$G_WORKDAY_SDATE datetime X
Global Variables
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
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.
Global Variables 7
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
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
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
Default Value: “FIRST”
Legal values:
• 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.
$G_MAX_DATE
Data Type: datetime
Used in date effective transforms to match SAP value for “infinite” date as end
of validity period.
Global Variables
$G_REBUILD_INDEXES
Default Value: “N” on Weekdays, “Y” on Weekends
Legal values:
• Y - Run rebuild indexes script
• N - Do not run rebuild indexes script
As delivered, this is a place holder for custom performance tuning.
See Rapid Mart Deployment Guideline.pdf for more details on how to use
this variable in conjunction with the stored procedures in file
Create_Sample_Maintenance_SP.sql.
These stored procedures drop indexes before a Fact Table load, and
re-create the indexes when the load is complete.
Use this variable to further restrict the drop and re-create to weekends only.
$G_RUN_MODE
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:
Global Variables 7
• 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
Data Type: int
Default Value: 60
Where Used:
SAP solutions
SAP solutions
payables and late payments
$C
Data Type: int
Default Value: 90
Global Variables
Where Used:
SAP solutions
SAP solutions
$D
Data Type: int
Default Value: 120
Where Used:
SAP solutions
SAP solutions
$E
Data Type: int
Default Value: 14
Where Used:
SAP solutions
SAP solutions
1 of 3 configurable forecast time periods (in days) used to calculate values of
financial documents at future dates (for discounting purposes, etc.)
$F
Data Type: int
Default Value: 30
Where Used:
SAP solutions
Global Variables 7
SAP solutions
$G
Data Type: int
Default Value: 45
Where Used:
SAP solutions
SAP solutions
$G_ABSOLUTE_START_DATE
Data Type: datetime
Default Value: NULL
Where Used:
SAP solutions
SAP solutions
solutions
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.
Global Variables
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 solutions
SAP solutions
solutions
solutions
• SAP BusinessObjects Plant Maintenance Rapid Mart, version for
SAP solutions
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
Default Value: “M” - Standard Translation at Average Rate
Where Used:
SAP solutions
SAP solutions
Global Variables 7
Used for lookup of exchange rates to Global Currency
$G_GLOBAL_CURRENCY
Default Value: “USD” - U.S. Dollar
Where Used:
SAP solutions
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
Where Used:
SAP solutions
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
Where Used:
SAP solutions
Global Variables

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 solutions
SAP solutions
solutions
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:
SAP solutions
SAP solutions
Global Variables 7
solutions
solutions
• SAP BusinessObjects Plant Maintenance Rapid Mart, version for
SAP solutions
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
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
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
Default Value: Sunday = Yes, all other days = No
Global Variables
Actual ATL Language Code:

“ifthenelse(day_in_week(sysdate())=7,'Y','N')”
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
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
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
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
Default Value: “DD”
Global Variables 7
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
Default Value: “Y” - Calculate backlog for third-party delivery
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).
When set to “N” (No) the Rapid Mart calculates backlog as:
• Qty Ordered - Qty Delivered (for all items).
$G_GL_ACCOUNT_HIER_NAME
Default Value: “@GL”
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.
Global Variables
$G_GL_SUM_PLAN_LEDGER_ID
Default Value: “L6”
for SAP solutions
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
Default Value: (see below)
Legal Values: “OLD” or “NEW”
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
Hiring Action Variable 01
$G_HIRE_ACTION_02
Global Variables 7
$G_HIRE_ACTION_03
Default Value: “K1”
$G_INIT_HIST_CHG
Default Value: “Z”
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
If any other value, then
• SALES_ORDER_HISTORY.QTY_DELTA_ORDER_SLSUOM =
SALES_ORDER_FACT.QTY_ORDER_SLSUOM
• SALES_ORDER_HISTORY.AMT_DELTA_NET_VALUE_TRX =
SALES_ORDER_FACT.AMT_NET_VALUE_TRX
$G_MALFUNCTION_CAUSE
Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart,
Catalog type to use for Malfunction Cause on Notifications. Choose your
system notification catalog group type for “Cause”.
$G_MALFUNCTION_DAMAGE
Default Value: “C”
Global Variables
Catalog type to use for Malfunction Damage on Notifications. Choose your

system notification catalog group type for “Damage”.
$G_MALFUNCTION_OBJ_PART
Default Value: “B”
Catalog type to use for Malfunction Object Part on Notifications. Choose your
system notification catalog group type for “Object Part”.
$G_MRP_RESULTS_DELETE
Default Value: “N”
Where Used: SAP BusinessObjects Production Planning Rapid Mart,
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
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 Line’s Planned Goods
Issue Date (SAP solutions field VBEP.WADAT).
It means that the On Time Delivery will only process Sales orders scheduled
to ship between 15 days in the past and 15 days in the future from system
date.
$G_PC_ACCOUNT_HIER_NAME
Default Value: “@PC”
for SAP solutions
Global Variables 7
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
Default Value: “L5”
for SAP solutions
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
Default Value: "JD"
Rehiring Action Variable 01
$G_REHIRE_ACTION_02
Default Value: "N7"
Rehiring Action Variable 02
$G_RETIRE_ACTION
Default Value: "ZP”
Global Variables

Retirement Action
$G_SAP_VERSION
Data Type: int
Default Value: System Determined - see below
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
Default Value: "50"
School Type
$G_SERVICE_INTERVAL_01
Data Type: INT
Default Value: 6 (1/2 year)
One of 5 Intervals for determining Employee Length of Service. Values are in
Months.
Data Type: INT
Default Value: 12 (1 year)
Global Variables 7
Months.
Data Type: INT
Default Value: 36 (3 years)
Months.
Data Type: INT
Months.
Data Type: INT
Months.
$G_TABLE_EQUIPMENT
Default Value: “EQUI”
Initialize according to your system class type for Equipment master table
name
$G_TABLE_FUNCTL_LOCATN
Global Variables
Default Value: “IFLOT”

Initialize according to your system class type for Functional Location master
table name
$G_TASK_TYPE_PROBATION_END
Probation End Task Type
$G_TERMINATION_ACTION
Termination Action
$G_VALID_DATE
Data Type: datetime
Default Value: System Date (without Time)
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
Default Value: "/101"
Global Variables 7
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_02
"////" if not used.
$G_WAGE_TYPE_03
"////" if not used.
$G_WAGE_TYPE_04
"////" if not used.
$G_WAGE_TYPE_05
"////" if not used.
$G_WAGE_TYPE_06
Global Variables

"////" if not used.
$G_WAGE_TYPE_07
"////" if not used.
$G_WAGE_TYPE_08
"////" if not used.
$G_WAGE_TYPE_09
"////" if not used.
$G_WAGE_TYPE_10
"////" if not used.
Global Variables 7
$G_WAGE_TYPE_11
"////" if not used.
$G_WAGE_TYPE_12
Default Value: "/5U0"
"////" if not used.
$G_WAGE_TYPE_13
Default Value: "/5U1"
"////" if not used.
$G_WAGE_TYPE_14
Default Value: "MI10"
"////" if not used.
$G_WAGE_TYPE_15
Global Variables

"////" if not used.
$G_WAGE_TYPE_16
Default Value: "////"
"////" if not used.
$G_WAGE_TYPE_17
"////" if not used.
$G_WAGE_TYPE_18
"////" if not used.
$G_WAGE_TYPE_19
"////" if not used.
Global Variables 7
$G_WAGE_TYPE_20
"////" if not used.
$G_WORKDAY_EDATE
Data Type: datetime
Default Value: 01-Jan-1994
First date of date range to populated Working Days dimension
$G_WORKDAY_SDATE
Data Type: datetime
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).
Global Variables
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.
Global Variables 7
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.
Global Variables
Conditional Global Variables in InitializeJob Script:
The Conditional Settings section also determines that certain global variable
settings are accurate and compatible:
• $G_LOAD_TYPE - Is either “FIRST” or “DELTA”. Any other setting will
cause the job to abort
• $G_GL_VERSION - Is either “OLD” or “NEW”. Any other setting will
cause the job to abort.
This section also calls certain Rapid Mart functions to properly set up the job
environment:
• AW_StartJob - Stores the current job execution parameters in table
AW_JOBEXECUTION.
• RM_PutFirstRunDate - Called in “FIRST” (initial) loads only. Stores the
contents of $G_SDATE and $G_EDATE for the “FIRST” (initial) load in
table AW_FIRST_RUN_DATE. These dates are important in delta (or
incremental) loads later on.
Executing the job 7
• RM_GetFirstRunDate - Called in “DELTA” (incremental) loads only.
Retreives the value of $G_SDATE stored in table
AW_FIRST_RUN_DATE. The value retreived is stored in global variable
$G_ORIG_SDATE. Consult the Techinical Implementation Chapter for
each individual Rapid Mart for more details on how this is used.
Note: If you set your own value for $G_ORIG_DATE before the call to
RM_GetFirstRunDate, the Rapid Mart will use your value and not retreive
the value in AW_FIRST_RUN_DATE.
Executing the 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. In the project area right-click in the Project_Systems_Load job to access
the Properties window.
2. Edit the job Global Variable properties:
a. Make sure that the value for the $G_LOAD_TYPE variable is set to
‘FIRST’.
b. In either the Properties window, or the job initialization script, set the
starting and ending dates for the initial load.
c. Set the starting date (the value for $G_SDATE) low enough to select
the earliest data desired for all target tables. Set the ending date (the
value for $G_EDATE) to the current date.
d. Set values for the rest of global variables in the Properties window or
the job initialization script, and click OK to accept the set properties
and to close the window.
Note: We suggest setting global variables in the job initialization script.
That way the Properties window will preserve the “as delivered” settings,
while the initialization script will show your custom settings. The
initialization script executes after the values in the Properties window are
set, and overrides the setting in the Properties windows.
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 286.
3. Run the job.
a. In the project area, right-click the job and choose Execute.
Data Services opens the Execution Properties window.
b. Select the desired execution properties.
At this point, you must decide whether or not to enable automatic
recovery. See Data Services User Guide for more information.
If you enabled automatic recovery and a job failed, you can recover
from the failed job at this time.
c. Click OK to accept the selected properties and start the job.
The job completes several steps:
• Initializes the variables to the values you set in the initialization
script.
• Calls components to load the tables. Generally, the job truncates
the tables before loading them during the initial job.
Some components, such as work flows that load dimension
tables, are repeated. The job only executes these components
the first time because these work flows and data flows are set to
“execute only once.”
4. Check the error log and the execution status table to make sure the job
ran successfully.
Incremental (Delta) Extraction and Load

1. Open the Properties window for job Project_Systems_Load by
right-clicking on the job in the project area and selecting Properties
command. Edit the job Global Variable properties (remember, you can
also set the values in the job initialization script instead of using the
Properties window):
a. Make sure that the value for the $G_LOAD_TYPE global variable is
set to ‘DELTA’.
Executing the job 7
b. Set the starting and ending time periods for the delta load. The
standard setting is the yesterday’s date for the starting date
($G_SDATE) and today’s date for ending date ($G_EDATE). This
assumes the Initial (First) load has already successfully loaded all
data through yesterday.
c. Set values for the rest of global variables as needed.
d. Click OK to accept the set properties and to close the window.
Note: We suggest setting global variables in the job initialization script.
That way the Properties window will preserve the “as delivered” settings,
while the initialization script will show your custom settings. The
initialization script executes after the values in the Properties window are
set, and overrides the setting in the Properties windows.
2. Run the job.
a. In the project area, right-click the job and choose Execute.
Data Services opens the Execution Properties window.
b. Select the desired execution properties.
At this point, you must decide whether or not to enable automatic
recovery. See Data Services User Guide for more information about
automatic recovery.
If you enabled automatic recovery and a job failed, you can recover
from the failed job at this time.
c. Click OK to accept the selected properties and start the job.
The job completes several steps:
• Initializes the variables to the values you set in the initialization
script.
• Calls components to load the tables incrementally, inserting new
and changed data since the last job execution. The job deletes
outdated data from the target tables, and reloads the target
tables with new and changed data. The incremental load uses
the append option to load most tables.
Some components, such as work flows that load dimension
tables, are repeated. The job only executes these components
the first time because these work flows and data flows are set to
“execute only once.”
3. Check the error log and the execution status table to make sure the job
ran successfully.
Customizing the Rapid Mart
Customizing the Rapid Mart

Rapid Marts are easy to customize. You can easily:
• Customize the Rapid Mart data schema to meet your specific needs.
• Expand the Rapid Mart to be used with various integrated query,
reporting, and data analysis applications.
• Transport Rapid Mart components and sections to different Rapid Marts
using the Data Services export and import facilities.
For example, to customize the Rapid Mart, you might:
• Change column names to be more meaningful in your business
environment.
• Remove columns or tables you do not need in your business
environment.
• Add:
• Columns from tables already sourced
• New columns from tables not extracted
• Aggregates
• Calculated or scrubbed data
You change your Rapid Mart in exactly the same way you would change any
Data Services application. For information about how to make such changes,
see the Data Services product documentation.
Note: In general, whenever you make a change, you need to perform impact
analysis. Impacts to consider include:
• Initial load
• Incremental load
• Target tables
• Integrity of existing Rapid Mart data
• Integrity between batch extraction and real time jobs
• Downstream analysis and reporting and Web applications
• Variable settings used by imported components and sections
• Other Rapid Mart (in a multi-Rapid Mart environment)
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 the Rapid Mart Deployment Guide.
Technical Implementation
chapter
8 Technical Implementation
Overview
Overview
This chapter provides technical details about how the SAP BusinessObjects
Project Systems 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:
• Milestone Section
• Network Order Section
• Network Relationship Section
• Project Cost Summary Section
• PRT Assignment Section
• Rolling Totals Calculation
• Optimization Techniques
• Dealing with NULL values
• Fact Table Stored Procedures
• Fiscal Periods & Time Dim Load
Milestone Section
The Milestone section loads data about Project Milestones from SAP
solutions. The target fact table for this section is MILESTONE_FACT. The
Rapid Mart calls the C_MilestoneSection_SAP work flow to load tables
associated with SAP solutions work centers.
First, the section loads the required dimension components with work flow
WF_MilestoneDims_SAP. If these dimensions have already been loaded
during the current job, the job will not reload them.
Work Flow Description Tables
C_Activity_SAP Dimensional component loading ACTIVITY
Activity information from CSLA and
CSLT
C_ActivityHier_SAP Dimensional component loading ACTIVITY_HIER,
Cost Activity Hierarchy information ACTIVITY_HIER_HZ,
from CCSS-LSTAR and CSLA ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
C_ChartofAccts_SAP Chart of Accts (T004 and T004T) in CHART_OF_ACCOUNTS
SAP solutions
Milestone Section 8
C_CompanyCode_SAP Dimensional component loading COMPANY_CODE
Company Codes information from
T001
C_ControlKey_SAP Dimensional component loading CONTROL_KEY
control key information and
descriptions from T430/T430T
C_ControllingArea_SAP Dimensional component loading CONTROLLING_AREA
Controlling Area information from
TKA01
C_CostElement_SAP Dimensional component loading COST_ELEMENT
Cost Element information from
CSKA and CSKU
C_CostElementHier_SAP Dimensional component loading COST_ELEMENT_HIER,
Cost Element Hierarchy information COST_ELEMENT_HIER_HZ,
from CCSS-KSTAR and CSK1 COST_ELEMENT_HIER_VR,
C_DocumentCategory_SAP Combined Document Category Dim. DOCUMENT_CATEGORY
Contains: Accounting Document
Category (Note: the Accounting
Doc Category does NOT have
associated Document Types.)
Internal Order
C_InternalOrder_SAP Load INTERNAL_ORDER INTERNAL_ORDER
dimension
C_InternalOrderHier_SAP Dimensional component loading INTERNAL_ORDER_HIER,
Internal Order Hierarchy information INTERNAL_ORDER_HIER_HZ,
from CCSS-AUFNR and AUFK INTERNAL_ORDER_HIER_VR,
C_MilestoneUsage_SAP Milestone Usage Descriptive MILESTONE_USAGE
attributes from T433T - load
MILESTONE_USAGE
C_NetworkProfile_SAP Network profile descriptive attributes NETWORK_PROFILE
from TCN41, TCN41T
C_OrderOperation_SAP Order Operation Master data - from ORDER_OPERATION
AFVC loading
ORDER_OPERATION dimension
C_Plant_SAP Dimensional component loading PLANT
consisting of a first and delta load for
the plant table from T001W.
C_Project_SAP Dimensional component loading PROJECT
project information
C_ProjectElement_SAP Dimensional component loading PROJECT_ELEMENT
Project Element (WBS) master data
Milestone Section

C_ProjectElementHier_SAP Dimensional component loading PROJECT_ELEMENT_HIER,
project element hierarchy PROJECT_ELEMENT_HIER_HZ
information ,
PROJECT_ELEMENT_HIER_VR
,
PROJECT_ELEMENT_HIER_BA
D
C_PurchOrganization_SAP Purchasing Organization Dimension PURCH_ORGANIZATION
from table T024E in SAP solutions
C_ReferenceDateKey_SAP Key determining the reference date REFERENCE_DATE_KEY
for various entities - Milestone, PRT -
Domain MLST_SDDAT; TCA55.
load REFERENCE_DATE_KEY
C_Routing_SAP Routing Header information from ROUTING
PLKO - ROUNTING
C_RoutingOperation_SAP Details of Task List ROUTING_OPERATION
operations/activities from PLPO -
populate ROUTING_OPERATION
dimension
C_StatusProfile_SAP Milestone Status profile descriptive STATUS_PROFILE
attributes from TJ20T - load
STATUS_PROFILE dimension
C_TaskListType_SAP Task List Type descriptive attributes TASK_LIST_TYPE
from TCA02 - TASK_LIST_TYPE
dimension
C_TimeDim_SAP Dimensional component loading TIME_DIM
generated time periods with SAP
solutions fiscal year periods and
calendar parameters. By default
Calendar dates from 1990.01.01 up
to 2012.12.31 are
C_UnitOfMeasure_SAP Populates Units of Measure UNIT_OF_MEASURE
dimension during first and delta
loads from Table T006A in SAP
solutions
C_WorkCenter_SAP Load WORK_CENTER master data WORK_CENTER
dimension
C_WorkCenterCategory_SAP Work Center Category descriptive WORK_CENTER_CATEGORY
attributes from TC30T
C_WorkCenterHier_SAP Work Center Hierarchical WORK_CENTER_HIER,
relationship in Horizontal and Vertical WORK_CENTER_HIER_HZ,
formats from CRHH/CRHS; load WORK_CENTER_HIER_VR,
WORK_CENTER_HIER, WORK_CENTER_HIER_BAD
WORK_CENTER_HIER_HZ
Milestones exist as a subset of a task list (or routing) and order operation
within SAP solutions. Technically speaking, a milestone is a date where the
start and end times are identical.
Milestone Section 8
Next, the section calls work flow C_MilestoneFact_SAP to load the
MILESTONE_FACT table. This table is source from SAP solutions tables:
• MLST - Milestone
• PLKO - Task list - header
• PLPO - Task list - operation/activity
We choose only the task list and operation records that have a corresponding
milestone record. We do this by outer joining the source tables, with MLST as
the outer source.
Also, the join assumes that PLKO & PLPO tables are not CDC-enabled
(ZAEHL column in PLKO & PLPO is not used in the join condition).
Finally, we use the Effective Date transform to compute the VALID_TO_DATE
for each record in MILESTONE_FACT.
Initial (First) Load

The initial load selects Milestones in the date range defined by global
variables $G_SDATE and $G_EDATE. Milestones “created on” or “last
changed” within this period are extracted from SAP solutions. We compare
the global variables to these dates in the MLST table:
• MLST.DATEH - Date Milestone Created
• MLST.DATEV - Date Milestone Last Changed
In an initial load, the gap between $G_SDATE and $G_EDATE is typically
many years, thus increasing the volume of the load to include most if not all
Milestones. Any data in the target MILESTONE_FACT table is deleted before
newly extracted data is loaded.
Incremental (Delta) Load

The incremental load also selects Milestones in the date range defined by
global variables $G_SDATE and $G_EDATE. However, in an incremental
load the gap between these two variables is typically one or two days. Far
fewer records are extracted, and execution time is greatly reduced.
The incremental load uses a “flat file” MilestoneID.dat to collect the
Milestone numbers (MLST.MLST_ZAEHL) for milestones that have changed
or been created since the last load.
This “flat file” is used to delete milestones in the MILESTONE_FACT table.
Then, new or changed Milestones are extracted from SAP solutions using the
same “flat file”.
The extracted go through the same Effective Date transform to compute the
VALID_TO_DATE as the initial load.

SAP solutions system.
Network orders are a shared component. They are used in the following
Rapid Marts:
Orders).
The Rapid Mart calls C_NetworkOrder_Section_SAP to load these tables.
This section first loads the required dimension components with work flow
WF_NetworkOrderDims_SAP. If these dimensions have already been
loaded during the current job, the job will not reload them
C_AccountAssignCateg_SAP Dimensional component loading text ACCT_ASSIGNMENT_CATEGO
for account assignment category RY
from T163I
C_BusinessArea_SAP Dimensional component loading BUSINESS_AREA
Business Area information from
TGSB and TGSBT
SAP solutions
T001
TKA01
C_CostCenter_SAP Dimensional component loading COST_CENTER
Cost Center information from CSKS
and CSKT
C_CostCenterHier_SAP Dimensional component loading COST_CENTER_HIER,
Cost Center Hierarchy information COST_CENTER_HIER_HZ,
from CCSS-KOSTL and CSKS COST_CENTER_HIER_VR,
CSKA and CSKU
C_Currency_SAP Dimensional component loading CURRENCY
currency abbreviations and texts
from TCURT, TCURC
C_DocumentType_SAP Combined Document Type Dim. DOCUMENT_TYPE &
Contains: Billing Type Delivery DOCUMENT_CATEGORY
Type Financial Document Type
FISL Document Type (Special
Ledger Doc. Type) Internal Order
Type Notification Type Purch Doc
Type Sales Order Type
C_FunctionalArea_SAP Dimensional component loading FUNCTIONAL_AREA
Functional Area information from
TFKB and TFKBT
C_FunctionalAreaHier_SAP Functional Area Hierarchy from FUNCTIONAL_AREA_HIER,
GLFUNCT-RFAREA FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_BA
D
dimension
C_InternalOrderStatus_SAP Internal orders status reference INTERNAL_ORDER_STATUS
dimension from TKO04
C_Material_SAP Dimensional component loading MATERIAL,
consisting of a first and delta load for PRODUCT_HIERARCHY
the materials table from MARA.
Loads the sales product hierarchy
table which is linked to the material
table
C_MaterialBatch_SAP Load MATERIAL_BATCH dimension MATERIAL_BATCH
(from MCHA)
C_MaterialByPlant_SAP Dimensional component loading MATERIAL_BY_PLANT
plant-specific material information
such as procurement type and
purchasing group from MARC
C_MaterialGroup_SAP Dimensional component loading MATERIAL_GROUP
the MATERIAL_GROUP table from
T023T.
C_MaterialType_SAP Material Type descriptive attributes MATERIAL_TYPE
from T134, T134T

C_MRPController_SAP Dimensional component loading MRP_CONTROLLER
MRP controller information from
T024D
C_NetworkProfile_SAP Network profile descriptive attributes NETWORK_PROFILE
from TCN41, TCN41T
C_ObjectClass_SAP Dimensional component loading OBJECT_CLASS
Object Class information from
DD07T
C_ObjectNumberType_SAP Object Key first 2 characters that OBJECT_NUMBER_TYPE
identify uniquely source table and
record from TBO01. Load
OBJECT_NUMBER_TYPE
C_ObjectStatus_SAP Dimensional component loading OBJECT_STATUS,
objects and horizontally represented OBJECT_STATUS_HZ
selected project status information
from JEST; load OBJECT_STATUS,
PROJECT_STATUS_HZ,
OBJECT_STATUS_HZ
C_PlantLocation_SAP Plant Location attributes from T499S PLANT_LOCATION
- PLANT_LOCATION
C_ProfitCenter_SAP Dimensional component loading PROFIT_CENTER
Profit Center master data
(Dimension)
C_ProfitCenterHier_SAP Dimensional component loading PROFIT_CENTER_HIER,
profit center hierarchy (EC-PCA PROFIT_CENTER_HIER_HZ,
Profit center hierarchy in SAP PROFIT_CENTER_HIER_VR,
solutions) PROFIT_CENTER_HIER_BAD
project information
information ,
,
D
PLKO - ROUNTING
C_ServicePerson_SAP Populates SERVICE_PERSON SERVICE_PERSON
dimension with Employee names.
This is a reference dimension only,
and not Employee master data
C_SpecialProcurementType_SAP Loads into SPECIAL_PROCUREMENT_TY
SPECIAL_PROCUREMENT_TYPE PE
dimension (from DD07T domain
SOBES)
C_StorageLocation_SAP Dimensional component loading STORAGE_LOCATION
storage location descriptions with
plant and division assignments from
T001L
dimension
C_TaskListUsage_SAP Task List Usage descriptive TASK_LIST_USAGE
(TASK_LIST_USAGE)
to 2012.12.31 are loaded. Modify
dates.dat file to change number of
dates
solutions
C_ValuationArea_SAP Dimensional component loading VALUATION_AREA
stock valuation areas from T001 and
T001K and used to assign plants
with a common currency together for
valuation (VALUATION_AREA)
Next, the section calls C_ProductionOrderFact_SAP to load the

PRODUCTION_ORDER_FACT table.
Production orders are sourced from SAP solutions table
• AUFK - Order master data
• AFKO - Order header data PP orders
• AFPO - Order item
The data populates target table
• PRODUCTION_ORDER_FACT
Production orders are a shared component. They are used in the following
Rapid Marts:
Orders).

Rapid Marts use two global variables to distinguish which Order Category will
be loaded, their default values are shown below:
$G_INT_ORDER_CATEG_PP, default value "10"
$G_INT_ORDER_CATEG_PS, default value "20"
Note: If you have only the SAP BusinessObjects Production Planning Rapid
Mart, version for SAP solutions, set values for both global variables to "10"
Note: If you have only the SAP BusinessObjects Project Systems Rapid
Mart, version for SAP solutions, set values for both global variables to "20"

The Rapid Mart extracts data from the SAP solutions tables using the create
date (AUFK.ERDAT) and change date (AUFK.AEDAT). If either the create
date or change date falls between the values set for global variables
$G_SDATE, and $G_EDATE the production order will be extracted.
Any data in the target PRODUCTION_ORDER_FACT table will be deleted
before any newly extracted data is loaded. The first load is typically a large
load, encompassing several years of production order history. The range
defined by variables $G_SDATE, and $G_EDATE will typically be several
years.

Once again, the Rapid Mart extracts data from the SAP solutions tables using
the create date (AUFK.ERDAT) and change date (AUFK.AEDAT). If either the
create date or change date falls between the values set for global variables
However, in the delta load, no data is deleted from the target table. Instead,
the Table Comparison transform is used to either insert new or update
changed records in the Rapid Mart. The delta load is typically much smaller
than the first load. The range defined by variables $G_SDATE and
$G_EDATE is usually one or two days.
activities in a network. Relationships determine the sequence of activities. A
Network Relationship is a way of linking related Order Operations.
The Rapid Mart calls C_NetworkRelationshipSection_SAP to load these
tables.
WF_NetworkRelationshipDim_SAP. If these dimensions have already been
loaded during the current job, the job will not reload them.
TGSB and TGSBT
T001
TKA01
TFKB and TFKBT
D
dimension
T024D
PROJECT_STATUS_HZ,
OBJECT_STATUS_HZ

AFVC loading
- PLANT_LOCATION
(Dimension)
project information
information ,
,
D
C_RelationshipType_SAP Network Relationship descriptive RELATIONSHIP_TYPE
attributes from TCN2T
T001L
dates
solutions
dimension
WORK_CENTER_HIER_HZ
Next, the section calls work flow WF_NetworkRelationshipDim_SAP to load

the NETWORK_RELATIONSHIP_FACT table. Network Relationships are
sourced from these SAP solutions tables:
• AFAB - Network - Relationships
The target table for Network Relationships is:
Only Order Operations (AFVC table) that have an associated network
relationships (AFAB table) are selected by means of an inner join between the
two tables.
This section also loads the Network Relationship Hierarchy table
• NETWORK_HIER_VR
This hierarchy table is loaded from the NETWORK_RELATIONSHIP_FACT
table. Thus, the load of NETWORK_RELATIONSHIP_FACT is a prerequisite
for the hierarchy load. The hierarchy is a vertically flattened hierarchy using
the Hierarchy Flattening transform.
There is no incremental (delta) load for either
NETWORK_RELATIONSHIP_FACT or NETWORK_HIER_VR.

Use Project Costing to plan, monitor, and control project costs, thereby
The Rapid Mart calls C_ProjectCostSummarySection_SAP to load these
tables.
WF_ProjectCostSummaryFactDims_SAP. If these dimensions have
already been loaded during the current job, the job will not reload them
C_BusinessActivity_SAP FK-SL Activity attributes from BUSINESS_ACTIVITY
T022/T022T. Load
BUSINESS_ACTIVITY dimension
TGSB and TGSBT
T001
TKA01
C_CostObjectIndicator_SAP Cost Object Indicator descriptive COST_OBJECT_INDICATOR
attributes from DD07T domain
(BP_TRGKZ domain)
C_Currency_SAP Dimensional component loading CURRENCY
currency abbreviations and texts
from TCURT, TCURC
C_FinancialMgmtArea_SAP Financial Management Area -- Also FINANCIAL_MGMT_AREA
called Funds Management Area --
dimension loaded from table FM01T
C_FinancingCode_SAP Fund Management - FIFM: FINANCING_CODE
Financing code from FMFINCODE
source table; load
FINANCING_CODE dimension
C_FinRecordCategory_SAP Descriptive attributes for Accounting FINANCIAL_RECORD_CATEGO
Summary table Value Category from RY
TPIR1T. Load
FINANCIAL_RECORD_CATEGORY
dimension
C_FinRecordType_SAP Loads Special Ledger Record Types FINANCIAL_RECORD_TYPE
dimension (Domain RRCTY) from
table DD07T and Cost/Plant
Maintenance value types from
CO_WRTTP domain of DD07T table
- FINANCIAL_RECORD_TYPE
C_FiscalPeriod_SAP Dimensional component loading FISC_PERIOD
Fiscal Year / Fiscal Period data
TFKB and TFKBT
D
OBJECT_NUMBER_TYPE
PROJECT_STATUS_HZ,
OBJECT_STATUS_HZ
AFVC loading
C_PeggingObject_SAP Details of Pegging Objects from PEGGING_OBJECT
PEGOB, PEGQTY; load
PEGGING_OBJECT dimension
(Dimension)
C_ProgressMeasureMethod_SAP Descriptive attributes for PS object PROGRESS_MEASURE_METH
progress measurement methods OD
from EVOP; load
PROGRESS_MEASURE_METHOD
project information
information ,
,
D

C_VarianceCategory_SAP Financial Variance Category VARIANCE_CATEGORY
descriptive attributes (ABKAT
domain from DD07T). Load
VARIANCE_CATEGORY dimension
Project Costs are sourced from these SAP solutions tables:

• RPSCO - Project info database: Costs, revenues, finances
• PROJ - Project definition
• PRPS - Project Element or WBS Element Master Data
The target tables for Project Costs are:
• PROJECT_COST_SUMMARY_FACT_HZ - Cost data in horizontal
format. That is, one row for each fiscal year with 16 columns for each
• PROJECT_COST_SUMMARY_STAGE_VR - Staging table for Costs in
vertical format. Not actually used for queries in the universe (semantic
layer).
• PROJECT_COST_SUMMARY_FACT_VR - Cost data in vertical format.
That is, one row for each fiscal year and fiscal period. There are 16 rows
per fiscal year, one for each fiscal period. Each row has individual
After loading the dimensions, the work flow C_ProjectCostSumFact_SAP
determines whether you are loading the target tables for the first time, or if
this an incremental (delta) load by querying the $G_LOAD_TYPE global
variable.
The range of years to load is determined by global variables $G_SDATE and
$G_EDATE. The years stored in these variables are used to determine the
first and last fiscal years respectively to be loaded. These variables are used
in both first and incremental loads.
If $G_LOAD_TYPE = “FIRST”, this is a first or initial load. The target tables
are truncated (all data in them is deleted).
If $G_LOAD_TYPE = “DELTA”, this an incremental or delta load. Table
partitions for the range of fiscal years ($G_SDATE and $G_EDATE) are
dropped and re-added to the target tables. This effectively deletes all data
from the tables for the range of fiscal years. See Table Partitions later in this
chapter for more details.
Then common logic for both initial and incremental loads takes over:
• Project Cost data is extracted from the SAP solutions target tables. The
data extracted is restricted to the range of years specified by variables
$G_SDATE and $G_EDATE. The output is loaded to
PROJECT_COST_SUMMARY_FACT_HZ.
• Next, data from PROJECT_COST_SUMMARY_FACT_HZ is passed
through a Pivot transform to convert it into vertical format. The vertical
format is loaded to table PROJECT_COST_SUMMARY_STAGE_VR.
• A final set of transforms computes the “rolling 16 periods totals” on
PROJECT_COST_SUMMARY_STAGE_VR. Output is loaded to
PROJECT_COST_SUMMARY_FACT_VR. See the section on Rolling
Totals Calculation below for more details.

In SAP solutions, the PRT’s are assigned to an Order Operation.
The Rapid Mart calls C_PRTAssignmentSection_SAP to load these tables.
WF_PRTAssignemntDims_SAP. If these dimensions have already been
loaded during the current job, the job will not reload them
C_Activity_SAP Dimensional component loading ACTIVITY
Activity information from CSLA and
CSLT
C_ActivityHier_SAP Dimensional component loading ACTIVITY_HIER,
Cost Activity Hierarchy information ACTIVITY_HIER_HZ,
from CCSS-LSTAR and CSLA ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
TGSB and TGSBT
SAP solutions
T001

TKA01
C_CostCenter_SAP Dimensional component loading COST_CENTER
Cost Center information from CSKS
and CSKT
C_CostCenterHier_SAP Dimensional component loading COST_CENTER_HIER,
Cost Center Hierarchy information COST_CENTER_HIER_HZ,
from CCSS-KOSTL and CSKS COST_CENTER_HIER_VR,
CSKA and CSKU
TFKB and TFKBT
D
dimension
C_Material_SAP Dimensional component loading MATERIAL,
consisting of a first and delta load for PRODUCT_HIERARCHY
the materials table from MARA.
Loads the sales product hierarchy
table which is linked to the material
table
T024D
OBJECT_NUMBER_TYPE
PROJECT_STATUS_HZ,
OBJECT_STATUS_HZ
C_ObjectType_SAP Dimensional component loading OBJECT_TYPE
Object Type information from various
modules -- This is a combined
dimension.
AFVC loading
- PLANT_LOCATION
(Dimension)
project information
information ,
,
D
C_PRT_GroupingKey_SAP Production Resource/Tools grouping PRT_GROUPING_KEY
key descriptive attributes from
TCF13; load PRT_GROUPING_KEY
dimension
C_PRTCategory_SAP Descriptive attributes from TCF03 of PRT_CATEGORY
Production Resource/Tools
categories; load PRT_CATEGORY
C_PRTMaster_SAP Production Resource/Tools master PRT_MASTER
details from CRHF
C_PRTStatus_SAP Descriptive attributes for PRT status PRT_STATUS
from TCF05; load PRT_STATUS
dimension

C_ReferenceDateKey_SAP Key determining the reference date REFERENCE_DATE_KEY
for various entities - Milestone, PRT -
Domain MLST_SDDAT; TCA55.
load REFERENCE_DATE_KEY
PLKO - ROUNTING
C_RoutingOperation_SAP Details of Task List ROUTING_OPERATION
operations/activities from PLPO -
populate ROUTING_OPERATION
dimension
C_RoutingSequence_SAP Routing (Task List) sequence ROUTING_SEQUENCE
definition from PLFL; load
ROUTING_SEQUENCE dimension
C_StandardTextKey_SAP Dimensional component loading STANDARD_TEXT_KEY
work center standard text
descriptions from T435T
T001L
dimension
dates
solutions
dimension
C_WorkCenterFormula_SAP Dimensional component loading WORK_CENTER_FORMULA,
work center formulas from TC25 FORMULA_PARAMETER
and parameters and constants from
TC20 - FORMULAS
WORK_CENTER_HIER_HZ
The PRT Assignment section extracts operation level data from these SAP
solutions tables:
• AFFH - PRT assignment data for the work order
• CRFH - CIM production resource/tool master data
The section stores the data in the fact table
The Rapid Mart selects only Operations that have a PRT assigned by inner
joining the source tables in SAP solutions.

The Rapid Mart extracts data from the SAP solutions tables using the create
date (AFFH.DATUI) and change date (AFFH.DATUC) on the PRT assignment
table AFFH. If either the create date or change date falls between the values
set for global variables $G_SDATE, and $G_EDATE the production order will
be extracted.
Any data in the target PRT_ASSIGNMENT_FACT table will be deleted before
any newly extracted data is loaded. The first load is typically a large load,
encompassing several years of production order history. The range defined
by variables $G_SDATE, and $G_EDATE will typically be several years.
Rolling Totals Calculation

Once again, the Rapid Mart extracts data from the SAP solutions tables using
the create date (AFFH.DATUI) and change date (AFFH.DATUC). If either the
create date or change date falls between the values set for global variables
However, in the delta load, no data is deleted from the target table. Instead,
the Table Comparison transform is used to either insert new or update
changed records in the Rapid Mart. The delta load is typically much smaller
than the first load. The range defined by variables $G_SDATE and
$G_EDATE is usually one or two days.

Vertical summary tables in several Rapid Marts use Rolling 16 Fiscal Period
Totals. These totals present the last 16 months of Period-To-Date values
summed, for each set of primary keys in the table. The vertical summary
tables with rolling totals are:
Rapid Mart Vertical Summary Table

Accts. Payable VENDOR_SUMMARY_FACT_VR
Accts. Receivable CUSTOMER_SUMMARY_FACT_VR
Cost COST_SUMMARY_FACT_VR
General Ledger COST_OF_SALES_SUMMARY_FACT_VR
General Ledger GL_SUMMARY_FACT_VR
General Ledger LEDGER_SUMMARY_FACT_VR
General Ledger & PROFIT_CENTER_SUMMARY_FACT_VR
Cost
Plant Maint. SERVICE_COST_SUMMARY_FACT_VR
Project Systems PROJECT_COST_SUMMARY_FACT_VR
To implement Rolling Totals we use a custom function

• RM_RollingSummary_Calculation.
The function keeps track of the Period-to-Date values from the previous row
processed by Data Services. This is key for rolling totals.
Rolling totals and the use of the function need to be carefully set up in Data
Services as shown in the example below.
Rolling Totals Calculation 8
Vertical Summary data is first populated to a “staging” table that has all values
for the vertical summary except the PTD (Period-to-Date) and Rolling Totals
values. Then, rolling totals are computed, and the results moved from the
staging table to the vertical summary table.
A rolling totals data flow typically looks like this...
Details for each query transform follow...
PTDBALQuery - 1. Calculate PTD Values:
“PTD” values are calculated by subtracting Credits from Debits.
PTDBALQuery - 2. Concatenate Summary Key:
The “Summary Key” is the concatenated Primary Key in one column. If the
Fiscal Year and Fiscal Period are a part of the Primary Key, they are excluded
from the Summary Key.
Ordering Query:
The Ordering Query will sort the data by the Summary Key, Fiscal Year, and
Fiscal Period. This is important for Rolling Totals as the function will
• Reset totals to zero when the Summary Key changes.
• Keep tract of totals for the past 16 rows processed.
None of this would work correctly without the proper sorting of the data.
Calc Rolling Totals Query:
This query calls the RM_RollingSummary_Calculation function. The call for

AMT_PER_ROLLING_TRX is shown above. The call for
AMT_PER_ROLLING_LOC is:
RM_RollingSummary_Calculation(
SUMMARY_KEY,
AMT_PTD_LOC,
$c1, $c2, $c3, $c4,
$c5, $c6, $c7, $c8,
$c9, $c10, $c11, $c12,
$c13, $c14, $c15, $c16,
$rkey )
Rolling Summary Calculation uses the computed Summary Key and
Period-To-Date total as input parameters. The function is called twice, once
for each of the two Rolling Totals calculated. Each of the calls uses a set of 16
local variables
• $t1 through $t16 for the AMT_PER_ROLLING_TRX call
• $c1 through $c16 for the AMT_PER_ROLLING_LOC call
Should there be a third rolling total to calculate, we would use a third set of 16
variables.
A final local variable $rkey is the value of the Summary Key on the previous
row processed by Data Services. It is used in both calls.
It is important to setup and initialize these local variables up correctly. They
are defined as local variables at the Work Flow Level in Data Services:
They are defined as Parameters at the Data Flow level:
The “Call” values for the parameters are initialized at the Work Flow
level as shown below.
The value of $RKEY is initialized to value that will never appear in the
Summary Key. The remaining groups of 16 variables are all initialized to zero.
An example of the output generated by this type of data flow and the Rolling
Totals Function are shown below.
Optimization Techniques
Within Data Services there are several optimization techniques available.
Some of these are used extensively in the Project Systems Rapid Mart. They
are described below
However, every installation is unique. Other techiques may be applicable to
your particular Rapid Mart installation. This depends on many variables such
as data load volume, server configuration, network transfer rates, etc. Refer
to Data Services™ technical manuals for more information on the varous
tuning and optimizing techniques.
Table Partitions
Summary tables in SAP solutions present a particular challenge in terms of a
incremental (or delta) load. They often do not carry a “date of last change”
field in the source table. In most cases source table granularity is at the Fiscal
Period / Fiscal Year level.
Data Services performs incremental loads on these tables by fiscal year.
Data for a range of fiscal years is deleted from the target tables before each
incremental load. The range is determined by the fiscal years associated with
the global variables $G_SDATE and $G_EDATE.
Then the same range of years is re-loaded from the SAP solutions source
tables.
Deleting by fiscal year without partitions is resource intensive, and can take a
very long time. To facilitate these deletions we have partitioned the target
tables by fiscal year.
Partitions based on fiscal year can be dropped and re-added to the table very
quickly. Thus the delete of a range of fiscal years is much faster. with
partitions
Each of the databases supported (Oracle, SQL-Server, DB2) handles
partition logic differently. Separate cases for each have been coded into the
Data Services jobs. Use of partitions is transparent to the end-user.
Note: We do not use partition logic for Teradata. Terdata optimizes the
delete function in SQL so that partitions are not needed.
Note: In a DB2 target environment, proper database tuning is required to
handle detaching partitions properly. If not tuned, the database returns
control to the Data Services job before the partition is physically
detached. This will cause the job to fail.
To prevent this, we query the DB2 metadata table:
Optimization Techniques 8
• 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 Subject Area Tables

Accts. Payable VENDOR_SUMMARY_FACT_HZ,
VENDOR_SUMMARY_FACT_VR,
VENDOR_SUMMARY_STAGE_VR
Accts. Receivable CUSTOMER_SUMMARY_FACT_HZ,
CUSTOMER_SUMMARY_FACT_VR,
CUSTOMER_SUMMARY_STAGE_VR
Cost COST_SUMMARY_FACT_HZ,
COST_SUMMARY_FACT_VR,
COST_SUMMARY_STAGE_VR
General Ledger COST_OF_SALES_SUMMARY_FACT_HZ,
COST_OF_SALES_SUMMARY_FACT_VR,
COST_OF_SALES_SUMMARY_STAGE_VR
General Ledger GL_SUMMARY_FACT_HZ,
GL_SUMMARY_FACT_VR,
GL_SUMMARY_STAGE_VR
General Ledger LEDGER_SUMMARY_FACT_HZ,
LEDGER_SUMMARY_FACT_VR,
LEDGER_SUMMARY_STAGE_VR
General Ledger PROFIT_CENTER_SUMMARY_FACT_HZ,
PROFIT_CENTER_SUMMARY_FACT_VR,
PROFIT_CENTER_SUMMARY_STAGE_VR
Plant Maint. SERVICE_COST_SUMMARY_FACT_HZ,
SERVICE_COST_SUMMARY_FACT_VR,
SERVICE_COST_SUMMARY_STAGE_VR
Projects PROJECT_COST_SUMMARY_FACT_HZ,
PROJECT_COST_SUMMARY_FACT_VR,
PROJECT_COST_SUMMARY_STAGE_VR
Data Transfer Transform

Within Data Services we make extensive use of the “Data Transfer” transform
to optimize operations. Data Transfer insures the operations are “pushed
down”. That is, performed by the underlying database instead of Data
Services.
Data Transfer creates a temporary database table that is used as a staging
table for the operation, thus insuring the “push down”. The temporary table is
deleted once the data flow that uses it is complete.
Note: If your target database is DB2, you must provide the DB2 bulk
loader log-in name and password in the Target Datastore.
If you don't your job will finish with the red "X" across the traffic light
indicating an error. But, no error log displayed in Data Services. To see
the error, go to the log directory on the Data Services job server, you'll
find and error log file indicating a warning about the DB2 bulkloader
log-in and password.
Providing the missing bulkloader log-in and password prevents this from
happening.
Here is an example of how to use a Data Transfer::
Key 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
Within the Ordering Query:
• “Order by” all non-pivot columns used in the Reverse-Pivot
• Make sure the columns in the “order by” clause appear in the same
sequence as the non-pivot columns in the Reverse-Pivot.
Within the Reverse-Pivot:
• “Input Data is Grouped” is checked
• Make sure the non-pivot columns appear in the same sequence as the
“order by” clause of the Ordering Query
Hierarchy 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):
After Split 1 of 2 Data Flows (Horizontal):
After Split 2 of 2 Data Flows (Vertical):
The 2 Split Data Flows in Context.
Dealing with NULL values
Dealing with NULL values

As the first step in data cleansing, the SAP BusinessObjects Project Systems
Rapid Mart, version for SAP solutions allows replacing NULL values found in
the source system with configurable default ‘not-null’ values.
The Rapid Mart provides three categories of default values to treat NULLs:
• For columns that behave as a foreign key the Rapid Mart replaces NULL
value with a global variable $G_DEFAULT_NUMBER of data type
integer;
• For columns that store descriptions NULLs are replaced with
$G_DEFAULT_TEXT of data type char(1);
• For columns that store dates NULLs are replaced with
$G_DEFAULT_DATE of data type DATE.
Dimensions whose corresponding foreign keys in the fact tables can have
value NULL are loaded with an additional ‘dummy’ row to represent NULL.
The value of $G_DEFAULT_NUMBER global variable gets inserted into each
dimension primary key column.
Fact Table Stored Procedures 8
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.
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
Fiscal Periods & Time Dim Load 8
By default, the file contains all dates from 01-Jan-1990 through 31-Dec.-2012
in “YYYYMMDD” format
You can easily change the contents of dates.dat to include a different date
range that covers your specific needs.
Documentation References
chapter
9 Documentation References
Data Services Documentation References
The SAP BusinessObjects Project Systems 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
Configuring Data Services for SAP solutions and security considerations:
• Data Services Supplement for SAP
Extending/customizing Rapid Marts ETL:
• Data Services Tutorial
• Data Services Designer Guide
• Data Services Reference Guide
• Data Services Advanced Development Guide
• Data Services Performance Optimization Guide
BusinessObjects Enterprise Documentation

References
From the SAP help portal, BusinessObjects Enterprise documentation is
accessed via SAP BusinessObjects -> All Products -> BusinessObjects
Enterprise -> BusinessObjects XI Release 2 <or higher version> path.
Installing BusinessObjects Enterprise:
• Installation Guide
Configuring BusinessObjects Enterprise and security considerations:
• Administration Guide
• Deployment and Configuration Guide
Documentation References
BusinessObjects Enterprise Documentation References 9
• Administrator’s Reference Guide
• Recommended Settings Guide
• Import Wizard Guide
• InfoView User Guide
Extending/customizing Rapid Marts Reporting Content:
• Designer’s Guide (BusinessObjects -> All Products -> Universe
Designer path)
• Building queries with Web Intelligence (BusinessObjects -> All
Products -> Web Intelligence path)
• Using Functions, Formulas and Calculations in Web Intelligence
(BusinessObjects -> All Products -> Web Intelligence path)
9 Documentation References
BusinessObjects Enterprise Documentation References
Rapid Mart Data Schema
appendix
Appendix
Table Summary A
Rapid Mart Data Schema
This appendix provides detailed information about the tables and views in the SAP BusinessObjects Project System
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
● ACCT_ASSIGNMENT_CATEGORY
● ACTIVITY
● ACTIVITY_HIER
● ACTIVITY_HIER_HZ
● ACTIVITY_HIER_VR
● BUSINESS_ACTIVITY
● BUSINESS_AREA
● CHART_OF_ACCOUNTS
● COMPANY_CODE
● CONTROL_KEY
● CONTROLLING_AREA
● COST_CENTER
● COST_CENTER_HIER
● COST_CENTER_HIER_HZ
● COST_CENTER_HIER_VR
● COST_ELEMENT
● COST_ELEMENT_HIER
● COST_ELEMENT_HIER_HZ
● COST_ELEMENT_HIER_VR
● COST_OBJECT_INDICATOR
● CURRENCY
● DOCUMENT_CATEGORY
● DOCUMENT_TYPE
● FINANCIAL_MGMT_AREA
● FINANCIAL_RECORD_CATEGORY
● FINANCIAL_RECORD_TYPE
● FINANCING_CODE
● FISC_PERIOD
● FORMULA_PARAMETER
● FUNCTIONAL_AREA
Rapid Mart Data Schema 1

Appendix
Table Summary A
● FUNCTIONAL_AREA_HIER
● FUNCTIONAL_AREA_HIER_HZ
● FUNCTIONAL_AREA_HIER_VR
● INTERNAL_ORDER
● INTERNAL_ORDER_HIER
● INTERNAL_ORDER_HIER_HZ
● INTERNAL_ORDER_HIER_VR
● INTERNAL_ORDER_STATUS
● MATERIAL
● MATERIAL_BATCH
● MATERIAL_BY_PLANT
● MATERIAL_GROUP
● MATERIAL_TYPE
● MILESTONE_USAGE
● MRP_CONTROLLER
● NETWORK_HIER_VR
● NETWORK_PROFILE
● OBJECT_CLASS
● OBJECT_NUMBER_TYPE
● OBJECT_STATUS
● OBJECT_STATUS_HZ
● OBJECT_TYPE
● ORDER_OPERATION
● PEGGING_OBJECT
● PLANT
● PLANT_LOCATION
● PRODUCT_HIERARCHY
● PROFIT_CENTER
● PROFIT_CENTER_HIER
● PROFIT_CENTER_HIER_HZ
● PROFIT_CENTER_HIER_VR
● PROGRESS_MEASURE_METHOD
● PROJECT
● PROJECT_ELEMENT
● PROJECT_ELEMENT_HIER
● PROJECT_ELEMENT_HIER_HZ
● PROJECT_ELEMENT_HIER_VR
● PRT_CATEGORY
● PRT_GROUPING_KEY
● PRT_MASTER
● PRT_STATUS
● PURCH_ORGANIZATION
● REFERENCE_DATE_KEY
● RELATIONSHIP_TYPE
● ROUTING

Appendix
Table Summary A
● ROUTING_OPERATION
● ROUTING_SEQUENCE
● SERVICE_PERSON
● SPECIAL_PROCUREMENT_TYPE
● STANDARD_TEXT_KEY
● STATUS_PROFILE
● STORAGE_LOCATION
● TASK_LIST_TYPE
● TASK_LIST_USAGE
● TIME_DIM
● TIME_DIM_WEEKLY
● UNIT_OF_MEASURE
● VALUATION_AREA
● VARIANCE_CATEGORY
● WORK_CENTER
● WORK_CENTER_CATEGORY
● WORK_CENTER_FORMULA
● WORK_CENTER_HIER
● WORK_CENTER_HIER_HZ
● WORK_CENTER_HIER_VR
Fact Tables
● MILESTONE_FACT
● NETWORK_RELATIONSHIP_FACT
● PRODUCTION_ORDER_FACT
● PROJECT_COST_SUMMARY_FACT_HZ
● PROJECT_COST_SUMMARY_FACT_VR
● PRT_ASSIGNMENT_FACT
Staging Tables
● FISC_PERIOD_STAGE
● PROJECT_COST_SUMMARY_STAGE_VR
Validation Tables
● ACTIVITY_HIER_BAD
● COST_CENTER_HIER_BAD
● COST_ELEMENT_HIER_BAD
● FUNCTIONAL_AREA_HIER_BAD
● INTERNAL_ORDER_HIER_BAD
● PROFIT_CENTER_HIER_BAD
● PROJECT_ELEMENT_HIER_BAD
● WORK_CENTER_HIER_BAD

Appendix
Table Column Details A
ACCT_ASSIGNMENT_CATEGORY
T163I and T163K - Texts for Account Assignment Categories
Column Dtype Is
# Column Name Key Column Desc Datatype Length Precision Scale Nullable
ACCT_ASSIGN_CATE PK
1 T613I.KNTTP - Account assignment category NVARCSTR 1 0 0 no
G_ID
ACCT_ASSIGN_DESC T163I.KNTTX - Account assignment category

2 NVARCSTR 20 0 0 yes
R description
3 CONSUMP_DESCR Lookup text description of T613K.KZVBR NVARCSTR 20 0 0 yes
T163K.KZVBR - Indicator: consumption

4 CONSUMP_ID NVARCSTR 1 0 0 yes
posting, purchasing
GOODS_RECPT_FL
5 T163K.WEPOS- Goods receipt indicator NVARCSTR 1 0 0 yes
AG
INVOICE_RECPT_FLA
6 T163K.REPOS- Invoice receipt indicator NVARCSTR 1 0 0 yes
G
7 LOAD_DATE Load date DATETIME 24 0 9 yes
8 LOAD_TIME Load time NVARCSTR 8 0 0 yes
SPECL_STOCK_DESC
9 Lookup text description of T163K.SOBKZ NVARCSTR 20 0 0 yes
R
10 SPECL_STOCK_ID T163K.SOBKZ- Special stock indicator NVARCSTR 1 0 0 yes

Appendix
ACTIVITY
Activity Master (CSLA, CSLT)
Column Dtype Is
1 ACTIVITY_DESCR CSLT-LTEXT-Description NVARCSTR 40 0 0 yes
ACTIVITY_FULL_NAM
2 Activity ID and Description NVARCSTR 120 0 0 yes
E
3 ACTIVITY_ID PK CSLA-LSTAR-Activity type NVARCSTR 6 0 0 no
4 ACTIVITY_NAME CSLT-KTEXT-Name NVARCSTR 20 0 0 yes
ACTIVITY_TYPE_CAT
5 CSLA-LATYPE-Activity type category NVARCSTR 1 0 0 yes
EG_CODE
ALLOCTN_COST_ELE
6 CSLA-VKSTA-Allocation cost element NVARCSTR 10 0 0 yes
M_ID
7 CREATED_BY CSLA-USNAM-Created by NVARCSTR 12 0 0 yes
8 CREATE_DATE CSLA-ERSDA-Created on DATETIME 24 0 9 yes
9 CTRL_AREA_ID PK CSLA-KOKRS-Controlling area NVARCSTR 4 0 0 no
Date and time when the record was loaded into DATETIME
10 LOAD_DATE 24 0 9 yes
Rapid Mart
Time when the record was loaded into the

11 LOAD_TIME NVARCSTR 8 0 0 yes
RapidMart (string format HH24:MI:SS)
12 OUTPUT_FACTOR CSLA-AUSFK-Output factor DECIMAL 48 5 2 yes
13 UOM_ID CSLA-LEINH-Activity unit NVARCSTR 3 0 0 yes
14 UOM_ID_OUTPUT CSLA-AUSEH-Output unit NVARCSTR 3 0 0 yes
15 VALID_FROM_DATE CSLA-DATAB-Date valid from DATETIME 24 0 9 yes
16 VALID_TO_DATE CSLA-DATBI-Valid to date DATETIME 24 0 9 yes

Appendix
ACTIVITY_HIER
Activity Hierarchy information - CCSS-LSTAR -- Note Does NOT Have a Primary Key due to duplication possible in SAP
Column Dtype Is
CCSS-LSTAR-Activity Hierarchy Child ID

1 CHILD_DESCR NVARCSTR 64 0 0 yes
Description
2 CHILD_ID PK CCSS-LSTAR-Child Activity ID NVARCSTR 12 0 0 no
3 CTRL_AREA_ID PK CCSS-LSTAR-Controling Area NVARCSTR 4 0 0 no
CCSS-LSTAR-Indicates if the Child ID doesn't

4 LEAF_FLAG PK NVARCSTR 1 0 0 no
have any subordinate leaves
Rapid Mart

CCSS-LSTAR-Activity Hierarchy Parent ID

7 PARENT_DESCR NVARCSTR 64 0 0 yes
Description
8 PARENT_ID PK CCSS-LSTAR-Parent Activity ID NVARCSTR 12 0 0 no
CCSS-LSTAR-Indicates if the Parent ID is a

9 ROOT_FLAG PK NVARCSTR 1 0 0 no
root of an activity group hierarchy

Appendix
ACTIVITY_HIER_BAD
CCSS-LSTAR Activity Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
CCSS-LSTAR-Activity Hierarchy Child ID

Description
2 CHILD_ID PK CCSS-LSTAR-Child Activity ID NVARCSTR 12 0 0 no
4 ETL_ERROR_ACTN Data Integrator Action on Error NVARCSTR 1 0 0 yes
ETL_ERROR_COLU
5 Data Integrator Error message NVARCSTR 500 0 0 yes
MN
CCSS-LSTAR-Indicates if the Child ID doesn't

6 LEAF_FLAG PK NVARCSTR 1 0 0 no
have any subordinate leaves
Rapid Mart

CCSS-LSTAR-Activity Hierarchy Parent ID

Description
10 PARENT_ID PK CCSS-LSTAR-Parent Activity ID NVARCSTR 12 0 0 no

11 ROOT_FLAG PK NVARCSTR 1 0 0 no

Appendix
ACTIVITY_HIER_HZ
Activity Hierarchy Horizontal Flattening - CCSS-LSTAR -- Cannot have a primary key due to duplication of entries possible in SAP
Column Dtype Is
CCSS-LSTAR-Leaf of the Activity Group

1 ACTIVITY_ID PK NVARCSTR 12 0 0 no
Hierarchy
CCSS-LSTAR-Depth of the leaf from the

3 LEAF_LVL INTEGER 4 0 0 no
parent
Rapid Mart

CCSS-LSTAR-Activity Hierarchy Level_0_ID

6 LVL_00_DESCR NVARCSTR 64 0 0 yes
Description
7 LVL_00_FULL_NAME Activity ID and Descripiton for Root NVARCSTR 120 0 0 yes
CCSS-LSTAR-Root of the Activity Group

8 LVL_00_ID PK NVARCSTR 12 0 0 no
Hierarchy

Description
10 LVL_01_FULL_NAME Activity ID and Descripiton for Level 1 NVARCSTR 120 0 0 yes
CCSS-LSTAR-A group or a Activity ID. It is null

11 LVL_01_ID PK when the hierarchy ended with a lower NVARCSTR 12 0 0 no
numbered node.

Description
13 LVL_02_FULL_NAME Activity ID and Descripiton for level 2 NVARCSTR 120 0 0 yes

numbered node.

Description
16 LVL_03_FULL_NAME Activity ID and Description for Level 3 NVARCSTR 120 0 0 yes

Appendix
numbered node.

Description

numbered node.

Description

numbered node.

Description

numbered node.

Description
28 LVL_07_FULL_NAME Activity ID and Description for level 7 NVARCSTR 120 0 0 yes

numbered node.

Appendix
ACTIVITY_HIER_VR
Activity Hierarchy Vertical Flattening - CCSS-LSTAR - cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR CCSS-LSTAR-Description of the descendant NVARCSTR 64 0 0 yes
2 CHILD_FULL_NAME Child Activity ID and Description NVARCSTR 120 0 0 yes
3 CHILD_ID PK CCSS-LSTAR-Activity Hierarchy Child ID NVARCSTR 12 0 0 no
CCSS-LSTAR-Depth of the descendant from

5 DEPTH INTEGER 4 0 0 yes
the ancestor

6 LEAF_FLAG INTEGER 4 0 0 yes
leaf of an activity group hierarchy
Rapid Mart

9 PARENT_DESCR CCSS-LSTAR-Description of the ancestor NVARCSTR 64 0 0 yes
10 PARENT_FULL_NAME Parent Activity ID and Description NVARCSTR 120 0 0 yes
11 PARENT_ID PK CCSS-LSTAR-Activity Hierarchy Parent ID NVARCSTR 12 0 0 no

12 ROOT_FLAG INTEGER 4 0 0 yes
AW_DIMENSION_SOURCE
Master list of values indicating sources of combined dimensions
Column Dtype Is
1 DIM_SRC_DESCR Description of Dimension Source NVARCSTR 60 0 0 yes
Dimension Source. Used in combined

2 DIM_SRC_ID PK dimension combining similar attributes from NVARCSTR 30 0 0 no
different sources in SAP.

Appendix
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.
Column Dtype Is
$G_EDATE global variable setting at the time

1 JOB_END_DATE DATETIME 24 0 0 yes
of the "First" or "Delta" run.
2 JOB_LOAD_TYPE PK Will be FIRST or DELTA NVARCSTR 10 0 0 no
3 JOB_NAME PK Name of the Rapid Mart Load Job. NVARCSTR 100 0 0 no
$G_SDATE global variable setting at the time

4 JOB_START_DATE DATETIME 24 0 0 yes
of the "First" or "Delta" run.
Rapid Mart

AW_JOBEXECUTION
Job Execution Status table
Column Dtype Is
1 EXTRACTHIGH End Date NVARCSTR 10 0 0 yes
2 EXTRACTLOW Start Date NVARCSTR 10 0 0 yes
Rapid Mart
4 NAME PK Job Name NVARCSTR 64 0 0 no
5 STATUS Job Status NVARCSTR 12 0 0 yes

Appendix
AW_LOOKUP_INDEX
Auxilary table to store index information
Column Dtype Is
1 ADDTNL_TXT Notes NVARCSTR 64 0 0 yes
2 COLUMN_NAME_01 Index column 1 NVARCSTR 64 0 0 yes
5 INDEX_NAME Index Name NVARCSTR 64 0 0 yes
6 LOAD_DATE Load date in Rapid mart DATETIME 24 0 0 yes
7 LOAD_TIME Load time in Rapid mart NVARCSTR 8 0 0 yes
8 TBL_NAME Table name the index belong to NVARCSTR 64 0 0 yes

Appendix
BUSINESS_ACTIVITY
FK-SL Activity attributes from T022/T022T
Column Dtype Is
BUS_ACTIVITY_DESC
1 T022T.TXT -Text (30 Characters) NVARCSTR 30 0 0 yes
R
2 BUS_ACTIVITY_ID PK T022.ACTIVITY -FI-SL Business Transaction NVARCSTR 4 0 0 no
BUS_ACTIVITY_TYPE
3 lookup on VORGTYP domain in DD07T NVARCSTR 60 0 0 yes
_DESCR
BUS_ACTIVITY_TYPE T022.VORGTYP -Activity type for FI-SL

_ID activities
5 LOAD_DATE Date and Time loaded into Rapid mart DATETIME 24 0 9 yes
6 LOAD_TIME Time Loaded into Rapid mart NVARCSTR 8 0 0 yes
RECORD_TYPE_DE
7 lookup on RRCTY domain in DD07T NVARCSTR 60 0 0 yes
SCR
8 RECORD_TYPE_ID T022.SATZTYP -Record Type NVARCSTR 1 0 0 yes
BUSINESS_AREA
Business Areas - TGSB, TSGBT
Column Dtype Is
1 BUS_AREA_DESCR TGSBT-GTEXT-Business area description NVARCSTR 30 0 0 yes
BUS_AREA_FULL_NA
2 Business Area ID and Descritpion NVARCSTR 120 0 0 yes
ME
3 BUS_AREA_ID PK TGSB-GSBER-Business area NVARCSTR 4 0 0 no
Rapid Mart


Appendix
CHART_OF_ACCOUNTS
Chart of Accounts in SAP (T004 and T004T tables)
Column Dtype Is
CHART_OF_ACCT_FU
1 Chart of accounts full name NVARCSTR 120 0 0 yes
LL_NAME
2 CHART_OF_ACCT_ID PK Chart of accounts NVARCSTR 4 0 0 no
CHART_OF_ACCT_NA
3 Chart of accounts description NVARCSTR 50 0 0 yes
ME
Rapid Mart


Appendix
COMPANY_CODE
T001 - Company Code master
Column Dtype Is
1 ADDRESS_ID Company default address identifier NVARCSTR 10 0 0 yes
2 CHART_OF_ACCT_ID Company Code chart of accounts NVARCSTR 4 0 0 yes
CHART_OF_ACCT_ID Chart of Accounts according to country

_COUNTRY legislation
CHART_OF_ACCT_NA
4 Chart of Accounts Name NVARCSTR 50 0 0 yes
ME
5 CITY Company City Name NVARCSTR 40 0 0 yes
CMPNY_CODE_FULL_
6 Company Code and Name NVARCSTR 120 0 0 yes
NAME
7 CMPNY_CODE_ID PK T001-BURKS - Company Code ID NVARCSTR 4 0 0 no
CMPNY_CODE_ID_OR
8 Original Key of Company Code NVARCSTR 4 0 0 yes
IGINAL
9 CMPNY_CODE_NAME Company Code Name NVARCSTR 40 0 0 yes
CMPNY_CODE_NAM
10 Name of the Company - 1st description NVARCSTR 40 0 0 yes
E_01
CMPNY_CODE_NAM
11 Name of the Company - 2nd description NVARCSTR 40 0 0 yes
E_02
CMPNY_CODE_NAM
12 Name of the Company - 3rd description NVARCSTR 40 0 0 yes
E_03
CMPNY_CODE_NAM
13 Name of the Company - 4th description NVARCSTR 40 0 0 yes
E_04
14 COUNTRY_ID Country Identifier NVARCSTR 3 0 0 yes
15 COUNTRY_NAME Country Name (lookup) NVARCSTR 15 0 0 yes
CR_CTRL_AREA_DES
16 Credit Controlling Area description NVARCSTR 35 0 0 yes
CR

Appendix
17 CR_CTRL_AREA_ID Credit Control area NVARCSTR 4 0 0 yes
18 CURR_ID Company Code Currency ID NVARCSTR 5 0 0 yes
19 DISTRICT District of the Company NVARCSTR 40 0 0 yes
20 FAX Fax no of the Company NVARCSTR 40 0 0 yes
21 FIN_MGMT_AREA_ID Financial Management Area NVARCSTR 4 0 0 yes
22 FISC_YR_VARIANT_ID Company code fiscal year variant NVARCSTR 2 0 0 yes
FISC_YR_VARIANT_N
23 Company code fiscal year variant name NVARCSTR 30 0 0 yes
AME
24 HOUSE_NUMBER Company code house number NVARCSTR 10 0 0 yes
25 LANG_DESCR Company code language Description NVARCSTR 16 0 0 yes
26 LANG_ID Company Code default language NVARCSTR 1 0 0 yes
Rapid Mart

29 PHONE Company code telephone number NVARCSTR 30 0 0 yes
30 REGION_ID Company code region NVARCSTR 3 0 0 yes
31 REGION_NAME Company code region name NVARCSTR 20 0 0 yes
32 STREET Company code street name NVARCSTR 60 0 0 yes
Jurisdiction fo tax calculation - tax jurisdiction

33 TAX_JURISDIC_NUM NVARCSTR 15 0 0 yes
code
VAT_REGISTRTN_NU
34 VAT regulation number NVARCSTR 20 0 0 yes
M

Appendix
35 ZIP Company code postal code NVARCSTR 10 0 0 yes
CONTROL_KEY
Business transactions should be executed for the object that belongs to the task list or order (from T430)
Column Dtype Is
T430.AUTWE - Indicator: automatic goods

1 AUTO_GR_FLAG NVARCSTR 1 0 0 yes
receipt
CAPACITY_PLAN_FLA
2 T430.KAPA - Indicator: Capacity planning NVARCSTR 1 0 0 yes
G
CONFIRMATN_FLAG_
3 Lookup description of confirmation indicator NVARCSTR 60 0 0 yes
DESCR
CONFIRMATN_FLAG_I T430.RUEK - Indicator: completion

D confirmation
5 CTRL_KEY_DESCR Lookup description of control key NVARCSTR 40 0 0 yes
6 CTRL_KEY_ID PK T430.STEUS - Control key NVARCSTR 4 0 0 no
T430.MRKKZ - Indicator: inspection

7 INSPECTN_FLAG NVARCSTR 1 0 0 yes
characteristics for operation require
8 LOAD_DATE Date and time loaded into Rapid Mart DATETIME 24 0 9 yes
9 LOAD_TIME Time when the record was loaded NVARCSTR 8 0 0 yes
10 REWORK_FLAG T430.REWORK - Indicator: Rework operation NVARCSTR 1 0 0 yes
11 SCHEDULE_FLAG T430.TERM - Indicator: Scheduling NVARCSTR 1 0 0 yes
12 SERVICE_FLAG T430.SERVICE - Indicator: Service NVARCSTR 1 0 0 yes

Appendix
CONTROLLING_AREA
TKA01 - Controlling areas master
Column Dtype Is
1 CTRL_AREA_DESCR Controlling Area Name NVARCSTR 25 0 0 yes
CTRL_AREA_FULL_N
2 Controlling Area DI and Desc NVARCSTR 120 0 0 yes
AME
3 CTRL_AREA_ID PK TKA01-KORKS - Controlling Area ID NVARCSTR 4 0 0 no
4 CURR_ID Currency Code for Controlling Area NVARCSTR 5 0 0 yes
5 FISC_YR_VARIANT_ID Fiscal Year Variant NVARCSTR 2 0 0 yes
LEDGER_ID_PROFIT_
6 Financial Ledger ID profit Center NVARCSTR 2 0 0 yes
CNTR
Rapid Mart

OPERTNG_CONCER
9 Operating Concern NVARCSTR 4 0 0 yes
N_ID
10 PROFIT_CNTR_AREA Profit Center Group NVARCSTR 12 0 0 yes
STD_SET_HIER_COD
11 Standard Hierarchy for Cost Centers NVARCSTR 12 0 0 yes
E

Appendix
COST_CENTER
CSKS - Cost Center Master
Column Dtype Is
CSKS.AFUNK - Alternative function of Cost

1 ALT_FUNCTN NVARCSTR 3 0 0 yes
Center
2 BUS_AREA_ID Business Area ID NVARCSTR 4 0 0 yes
3 CITY Cost Center City Name NVARCSTR 40 0 0 yes
4 CMPNY_CODE_ID Company Code ID NVARCSTR 4 0 0 yes
Company code name associated with this Cost NVARCSTR

5 CMPNY_CODE_NAME 40 0 0 yes
Center
6 COST_CNTR_DESCR Cost Center Descritpion NVARCSTR 60 0 0 yes
COST_CNTR_FULL_N
7 Cost Center ID and Desc NVARCSTR 120 0 0 yes
AME
8 COST_CNTR_ID PK CSKS-KOSTL - Cost Center ID NVARCSTR 10 0 0 no
COST_CNTR_ID_SUB
9 CSKS.NKOST - Subsequent Cost Center ID NVARCSTR 10 0 0 yes
SEQUENT
10 COST_CNTR_NAME Cost Center Default Name NVARCSTR 40 0 0 yes
COST_CNTR_NAME_0
11 Cost Center Name Line 1 NVARCSTR 40 0 0 yes
1
COST_CNTR_NAME_0
2
COST_CNTR_NAME_0
3
COST_CNTR_NAME_0
4
15 COUNTRY_ID Cost Center Country Code NVARCSTR 3 0 0 yes
16 COUNTRY_NAME Cost Center Country Name NVARCSTR 15 0 0 yes

Appendix
17 CREATED_BY Person ID who created the record NVARCSTR 12 0 0 yes
Date when the record was created in the

18 CREATE_DATE DATETIME 24 0 9 yes
source system
19 CTRL_AREA_DESCR Control Area description NVARCSTR 25 0 0 yes
20 CTRL_AREA_ID PK Controlling Area Identifier NVARCSTR 4 0 0 no
21 CURR_ID Cost Center Currency ID NVARCSTR 5 0 0 yes
22 DEPARTMENT CSKS.ABTEI - Department NVARCSTR 12 0 0 yes
23 DISTRICT Cost Center City District NVARCSTR 40 0 0 yes
24 EQUITY_TYPE_CODE CSKS.ETYPE - Equity type NVARCSTR 3 0 0 yes
25 FAX Cost Center fax number NVARCSTR 40 0 0 yes
26 FUNCTN_CODE CSKS.FUNKT - function of Cost Center NVARCSTR 3 0 0 yes
Rapid Mart

29 PERSON_IN_CHARGE CSKS.VERAK - Cost Center Manager NVARCSTR 20 0 0 yes
30 PHONE Cost Center phone # 1 NVARCSTR 30 0 0 yes
PROFIT_CNTR_DESC
31 Profit Center Description NVARCSTR 40 0 0 yes
R
32 PROFIT_CNTR_ID CSKS.PRCTR - Profit Center Code NVARCSTR 10 0 0 yes
33 REGION_ID Region ID NVARCSTR 3 0 0 yes
34 REGION_NAME Region name NVARCSTR 20 0 0 yes

Appendix
35 STREET Cost Center Street name NVARCSTR 60 0 0 yes
36 TYPE_CODE Cost Center Type Identifier NVARCSTR 1 0 0 yes
37 VALID_FROM_DATE Record is valid to DATETIME 24 0 9 yes
38 VALID_TO_DATE Record Valid from DATETIME 24 0 9 yes
39 ZIP Cost Center ZIP code NVARCSTR 10 0 0 yes
COST_CENTER_HIER
Cost Center Hierarchy - CCSS-KOSTL - Cannot have a primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Cost Center Child description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no
3 CTRL_AREA_ID PK Controlling Area ID NVARCSTR 4 0 0 no
4 LEAF_FLAG PK Is Leaf NVARCSTR 1 0 0 no
Rapid Mart

7 PARENT_DESCR Cost Center parent descritpion NVARCSTR 64 0 0 yes
8 PARENT_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no
9 ROOT_FLAG PK Is Root NVARCSTR 1 0 0 no

Appendix
CCSS-KOSTL Cost Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Cost Center Child description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no
ETL_ERROR_COLU
MN
Rapid Mart

9 PARENT_DESCR Cost Center parent descritpion NVARCSTR 64 0 0 yes
10 PARENT_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no

Appendix
COST_CENTER_HIER_HZ
CCSS-KOSTL Cost Center hierarchy flattenned horizontally -- Cannot have a primary key on this table due to possible duplicate entries in
SAP
Column Dtype Is
1 COST_CNTR_ID PK Cost Center ID (current node) NVARCSTR 12 0 0 no
3 LEAF_LVL Is Leaf Level INTEGER 4 0 0 no
Rapid Mart

6 LVL_00_DESCR Cost Center Root Node Description NVARCSTR 64 0 0 yes
7 LVL_00_FULL_NAME Cost Center ID and Desc for Level 0 NVARCSTR 120 0 0 yes
8 LVL_00_ID PK Cost Center root node ID NVARCSTR 12 0 0 no
9 LVL_01_DESCR Cost Center level 1 Node Description NVARCSTR 64 0 0 yes
11 LVL_01_ID PK Cost Center level 1 Node ID NVARCSTR 12 0 0 no
13 LVL_02_FULL_NAME Cost Center Id and Desc for Level 2 NVARCSTR 120 0 0 yes

Appendix
28 LVL_07_FULL_NAME Cost Center Id and Dec for Level 7 NVARCSTR 120 0 0 yes

Appendix
COST_CENTER_HIER_VR
CCSS-KOSTL - Cost Center Hierarchy vertically flattenned - cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Cost Center Child Node Description NVARCSTR 64 0 0 yes
2 CHILD_FULL_NAME Cost Center ID and Desc for the Child NVARCSTR 120 0 0 yes
3 CHILD_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no
5 DEPTH Node depth level INTEGER 4 0 0 yes
6 LEAF_FLAG Is Leaf INTEGER 4 0 0 yes
Rapid Mart

9 PARENT_DESCR Cost Center Child Node Descritpion NVARCSTR 64 0 0 yes
10 PARENT_FULL_NAME Cost Center Parent ID and Desc NVARCSTR 120 0 0 yes
11 PARENT_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no
12 ROOT_FLAG Is Root INTEGER 4 0 0 yes

Appendix
COST_ELEMENT
CSKA - Cost Element (GL Accounts) Master
Column Dtype Is
1 CHART_OF_ACCT_ID PK Accounting Chart of accounts ID NVARCSTR 4 0 0 no
2 COST_ELEM_DESCR Cost center description in default language NVARCSTR 40 0 0 yes
COST_ELEM_FULL_N
3 Cost Element ID and Description NVARCSTR 120 0 0 yes
AME
4 COST_ELEM_ID PK Cost Element (GL Account) ID NVARCSTR 10 0 0 no
Date when the record was created in the

5 CREATE_DATE DATETIME 24 0 9 yes
source system
Rapid Mart

PAYMNT_RELEVNT_F CSKA.ZAHKZ - Cost element is

LAG payment-relevant
9 TAX_RELEVNT_FLAG CSKA.STEKZ - Cost Element is tax-relevant NVARCSTR 1 0 0 yes

Appendix
COST_ELEMENT_HIER
CCSS-KSTAR Cost Element hierarchy - cannot have primary key due to data duplication possible in SAP
Column Dtype Is
1 CHART_OF_ACCT_ID PK Accounting Chart of Accounts ID NVARCSTR 4 0 0 no
2 CHILD_DESCR Cost Element Child Node Description NVARCSTR 64 0 0 yes
3 CHILD_ID PK Cost Element Child Node ID NVARCSTR 12 0 0 no
Rapid Mart

7 PARENT_DESCR Cost Element Parent Node Descritpion NVARCSTR 64 0 0 yes
8 PARENT_ID PK Cost Element Parent Node ID NVARCSTR 12 0 0 no

Appendix
CCSS-KSTAR Cost ElementHierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
2 CHILD_DESCR Cost Element Child Node Description NVARCSTR 64 0 0 yes
3 CHILD_ID PK Cost Element Child Node ID NVARCSTR 12 0 0 no
ETL_ERROR_COLU
MN
Rapid Mart

9 PARENT_DESCR Cost Element Parent Node Descritpion NVARCSTR 64 0 0 yes
10 PARENT_ID PK Cost Element Parent Node ID NVARCSTR 12 0 0 no

Appendix
COST_ELEMENT_HIER_HZ
CCSS-KSTAR - Cost Element Hierarchy- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHART_OF_ACCT_ID PK Accounting Chart Of Account ID NVARCSTR 4 0 0 no
2 COST_ELEM_ID PK Cost Element (GL Account) ID NVARCSTR 12 0 0 no
3 LEAF_LVL Cost Element Leaf level (depth) DECIMAL 48 28 0 no
Rapid Mart

6 LVL_00_DESCR Cost Element Root Node Description NVARCSTR 64 0 0 yes
7 LVL_00_FULL_NAME Cost Element ID and Descripion for level 0 NVARCSTR 120 0 0 yes
8 LVL_00_ID PK Cost Element Root Node ID NVARCSTR 12 0 0 no
9 LVL_01_DESCR Cost Element Level 1 Node Description NVARCSTR 64 0 0 yes
10 LVL_01_FULL_NAME Cost Element ID and Desc for Level 1 NVARCSTR 120 0 0 yes
11 LVL_01_ID PK Cost Element Level 1 Node ID NVARCSTR 12 0 0 no

Appendix

Appendix
COST_ELEMENT_HIER_VR
CCSS-KSTAR - Cost Element Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
2 CHILD_DESCR Cost Element Parent Node Descritpion NVARCSTR 64 0 0 yes
3 CHILD_FULL_NAME Cost Element Child ID and Desc NVARCSTR 120 0 0 yes
4 CHILD_ID PK Cost Element Parent Node ID NVARCSTR 12 0 0 no
5 DEPTH Cost Element node depth level DECIMAL 48 28 0 yes
6 LEAF_FLAG Is Leaf DECIMAL 48 28 0 yes
Rapid Mart

9 PARENT_DESCR Cost Element Child Node Description NVARCSTR 64 0 0 yes
10 PARENT_FULL_NAME Cost Element Parent ID and Desc NVARCSTR 120 0 0 yes
11 PARENT_ID PK Cost Element Child Node ID NVARCSTR 12 0 0 no
12 ROOT_FLAG Is Root DECIMAL 48 28 0 yes

Appendix
COST_OBJECT_INDICATOR
The object indicator is used to classify cost objects. In the order value update, the indicator is used to show whether an order, network, or
network activity is appende
Column Dtype Is
Short text describing ABAP/4 Dictionary

1 COST_OBJ_DESCR NVARCSTR 60 0 0 yes
objects; domain BP_TRGKZ
Values for domains: Single value/upper limit -

2 COST_OBJ_ID PK NVARCSTR 10 0 0 no
domain BP_TRGKZ
4 LOAD_TIME Time loaded into Rapid mart NVARCSTR 8 0 0 yes
CURRENCY
TCURC, TCURT
Column Dtype Is
Lookup TCURX.CURRDEC - Number of

1 CURR_DECIMAL DECIMAL 48 28 0 yes
decimals to display amounts in this currency.
2 CURR_DESCR TCURT-LTEXT - Long Text NVARCSTR 60 0 0 yes
3 CURR_ID PK TCURC-WAERS - Currency Key NVARCSTR 5 0 0 no
TCURC-ALTWR - Alternative Key For

4 CURR_ID_ALT NVARCSTR 3 0 0 yes
Currencies
5 CURR_ISO_CODE TCURC-ISOCD - ISO Currency Code NVARCSTR 3 0 0 yes
Multiply currency amounts by this factor to

6 DISPLAY_FACTOR display with correct number of decimals for the DECIMAL 48 17 14 yes
currency
Rapid Mart

TCURC-GDATU -Date Up Until Which The

9 VALID_TO_DATE DATETIME 24 0 9 yes
Currency Is Valid

Appendix
DOCUMENT_CATEGORY
Domain VBTYP (Table DD07T) - Sales Document Categ
Column Dtype Is
Dimension Source from table

1 DIM_SRC_ID PK NVARCSTR 10 0 0 no
AW_DIMENSION_SOURCE
Document Category Description from multiple

2 DOC_CATEG_DESCR NVARCSTR 100 0 0 yes
sources in SAP
Document Category ID from multiple sources in NVARCSTR

3 DOC_CATEG_ID PK 10 0 0 no
SAP
4 LOAD_DATE Date and Time Loaded in Rapid Mart DATETIME 24 0 9 yes
5 LOAD_TIME Time Loaded into Rapid Mart NVARCSTR 8 0 0 yes
DOCUMENT_TYPE
Internal Order Type attributes from T003O/T003P
Column Dtype Is

AW_DIMENSION_SOURCE
2 DOC_CATEG_DESCR Document Category Description NVARCSTR 100 0 0 yes
Document Category from multiple Sources in

3 DOC_CATEG_ID PK NVARCSTR 10 0 0 no
SAP
4 DOC_TYPE_DESCR Document Type Description NVARCSTR 100 0 0 yes
5 DOC_TYPE_ID PK Document Type from Multiple sources in SAP NVARCSTR 10 0 0 no

Appendix
FINANCIAL_MGMT_AREA
FM01T - Funds Management Area Texts
Column Dtype Is
FIN_MGMT_AREA_DE
1 Name of FM area NVARCSTR 25 0 0 yes
SCR
2 FIN_MGMT_AREA_ID PK Financial Management Area NVARCSTR 4 0 0 no
Rapid Mart

FINANCIAL_RECORD_CATEGORY
Descriptive attributes for Accounting Summary table Value Category from TPIR1T
Column Dtype Is
RECORD_CATEG_D
3 TPIR1T-KTEXT - Text NVARCSTR 30 0 0 yes
ESCR
4 RECORD_CATEG_ID PK TPIR1T-ACPOS - Value category NVARCSTR 14 0 0 no

Appendix
FINANCIAL_RECORD_TYPE
Loads Special Ledger Record Types dimension (Domain RRCTY) from table DD07T and Cost/Plant Maintenance value types from
CO_WRTTP domain of DD07T table - FINANCIAL_RECORD_
Column Dtype Is

1 DIM_SRC_ID PK dimension combining similar attributes from NVARCSTR 10 0 0 no
Rapid Mart

RECORD_TYPE_DE
4 Financial Record Type Desc. NVARCSTR 60 0 0 yes
SCR
5 RECORD_TYPE_ID PK Financial Record Type ID NVARCSTR 10 0 0 no

Appendix
FINANCING_CODE
Fund Managment - FIFM: Financing code from FMFINCODE source table
Column Dtype Is
FIN_MGMT_AREA_DE
1 FM01T.FITXT - Name of FM area NVARCSTR 25 0 0 yes
SCR
FMFINCODE.FIKRS - Financial management

2 FIN_MGMT_AREA_ID PK NVARCSTR 4 0 0 no
area
3 FUND_DESCR FMFINT.BESCHR - Fund Description NVARCSTR 40 0 0 yes
4 FUND_ID PK FMFINCODE.FINCODE - Fund NVARCSTR 10 0 0 no
5 FUND_NAME FMFINT.BEZEICH Fund Name NVARCSTR 20 0 0 yes
FMFUNDTYPET.FUND_TYPET - Fund Type

6 FUND_TYPE_DESCR NVARCSTR 35 0 0 yes
Description
7 FUND_TYPE_ID FMFINCODE.TYPE - FM Fund Type ID NVARCSTR 6 0 0 yes
10 VALID_FROM_DATE FMFINCODE.DATAB - FM: Valid from date DATETIME 24 0 9 yes
11 VALID_TO_DATE FMFINCODE.DATBIS -FM: Valid to date DATETIME 24 0 9 yes

Appendix
FISC_PERIOD
Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)
Column Dtype Is
1 CALENDAR_HALF Calendar Half Year for this Fiscal Period NVARCSTR 2 0 0 yes
CALENDAR_MONTH Calendar Month (January - December) for this

_LONG Fiscal Period
CALENDAR_MONTH Calendar Month (Numeric) for this Fiscal

_NUMERIC Period
CALENDAR_MONTH Calendar Month (JAN - DEC) for this fiscal

_SHORT Period
CALENDAR_QUART
5 Calendar Quarter for this Fiscal Period INTEGER 4 0 0 yes
ER
6 CALENDAR_YEAR Calendar Year for this fiscal period INTEGER 4 0 0 yes
CALENDAR_YEAR_HA
7 Calendar Year and Half NVARCSTR 12 0 0 yes
LF
CALENDAR_YEAR_
8 Calendar Year and Month NVARCSTR 12 0 0 yes
MONTH
CALENDAR_YEAR_
9 Calendar Year and Quarter NVARCSTR 12 0 0 yes
QUARTER
10 END_DATE End Date for Fiscal Period DATETIME 24 0 9 yes
11 FISC_HALF Fiscal Half Year NVARCSTR 2 0 0 yes
12 FISC_MONTH Fiscal Month In SAP NVARCSTR 2 0 0 yes
13 FISC_PERIOD PK Fiscal Period in SAP INTEGER 4 0 0 no
14 FISC_QUARTER Fiscal Quarter NVARCSTR 2 0 0 yes
15 FISC_YEAR PK Fiscal Year in SAP INTEGER 4 0 0 no
16 FISC_YEAR_HALF Fiscal Year and Half NVARCSTR 12 0 0 yes

Appendix
17 FISC_YEAR_MONTH Fiscal Year and Month NVARCSTR 12 0 0 yes
18 FISC_YEAR_PERIOD Fiscal Year and Period NVARCSTR 12 0 0 yes
FISC_YEAR_QUARTE
19 Fiscal Year and Quarter NVARCSTR 12 0 0 yes
R
20 FISC_YR_VARIANT_ID PK Fiscal Year Variant in SAP NVARCSTR 2 0 0 no
FISC_YR_VARIANT_N Name of Fiscal Year Variant (Table T009T in

AME SAP)
Rapid Mart

SPECL_PERIOD_FLA Y = This is a special period in SAP, N = This is NVARCSTR

24 1 0 0 yes
G NOT a special period in SAP
25 START_DATE Start Date for Fiscal Period DATETIME 24 0 9 yes

Appendix
FISC_PERIOD_STAGE
Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)
Column Dtype Is
Calendar Date - range from 01-Jan-1990

1 CALENDAR_DATE PK DATETIME 24 0 9 no
through 31-Dec-2049
2 FISC_MONTH Fiscal Month in range 1 to 12 NVARCSTR 2 0 0 yes
3 FISC_PERIOD PK Fiscal Period in range 1 to 16 INTEGER 4 0 0 no
4 FISC_YEAR Fiscal Year in SAP INTEGER 4 0 0 yes
5 FISC_YR_VARIANT_ID PK Fiscal Year Variant in SAP NVARCSTR 2 0 0 no
FISC_YR_VARIANT_N Name of Fiscal Year Variant (Table T009T in

AME SAP)
Rapid Mart

REGISTRTN_PERIOD
9 Number of Regular Acctng Periods INTEGER 4 0 0 yes
_COUNT
SPECL_PERIOD_COU
10 Number of Special Acctng Periods INTEGER 4 0 0 yes
NT

Appendix
FORMULA_PARAMETER
Capacity Parameter details from TC20 that are related to Work Center formulars
Column Dtype Is
COSTNG_ALLOW_F TC20.VKALK - Indicates it is allowed for

1 DECIMAL 48 10 0 yes
LAG costing
DIMENSION_TYPE_N
2 TC20.DIMEN- Dimension key NVARCSTR 6 0 0 yes
AME
3 FIELD_NAME TC20.VGFLD - Field name NVARCSTR 10 0 0 yes
6 PARAMETER_DESCR TC20T.TXT - Lookup parameter description NVARCSTR 11 0 0 yes
7 PARAMETER_ID PK TC20.PARID - Parameter ID NVARCSTR 6 0 0 no
PARAMETER_KEYW TC20T. TXTLG - Lookup keyword for

ORD parameter
PARAMETER_ORIGIN Lookup on DD07T, docmain VGWRTKZ -

_DESCR origin text
PARAMETER_ORIGIN
10 TC20.VRWRT - Origin of the parameter value NVARCSTR 1 0 0 yes
_ID
TC20.UNIT- Unit of measure for the standard

11 UOM_ID_STD NVARCSTR 3 0 0 yes
value
12 VALUE_STD TC20.VALUE_DEF - Standard value DECIMAL 48 9 3 yes

Appendix
FUNCTIONAL_AREA
TFKB-FKBER - Functional Area reference table
Column Dtype Is
FUNCTNL_AREA_DES
1 Functional Area Description NVARCSTR 30 0 0 yes
CR
FUNCTNL_AREA_FUL
2 ID and Description NVARCSTR 120 0 0 yes
L_NAME
3 FUNCTNL_AREA_ID PK TFKB-FKBER - Functional Area Code NVARCSTR 16 0 0 no
Rapid Mart

FUNCTIONAL_AREA_HIER
Functional Area Hierarchy
Column Dtype Is
1 CHILD_DESCR Child node description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Child node id NVARCSTR 30 0 0 no
3 LEAF_FLAG PK Leaf node indicator (child node is leaf) NVARCSTR 1 0 0 no
Rapid Mart

6 PARENT_DESCR Parent node description NVARCSTR 64 0 0 yes
7 PARENT_ID PK Parent node id NVARCSTR 30 0 0 no
8 ROOT_FLAG PK Root node indicator (parent node is root) NVARCSTR 1 0 0 no

Appendix
Functional Area Hierarchy - Invalid Records with Circular Dependency.
Column Dtype Is
1 CHILD_DESCR Child node description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Child node id NVARCSTR 30 0 0 no
ETL_ERROR_COLU
MN
5 LEAF_FLAG PK Leaf node indicator (child node is leaf) NVARCSTR 1 0 0 no
Rapid Mart

8 PARENT_DESCR Parent node description NVARCSTR 64 0 0 yes
9 PARENT_ID PK Parent node id NVARCSTR 30 0 0 no
10 ROOT_FLAG PK Root node indicator (parent node is root) NVARCSTR 1 0 0 no

Appendix
FUNCTIONAL_AREA_HIER_HZ
Functional Area Hierarchy - Horizontal
Column Dtype Is
1 FUNCTNL_AREA_ID PK Funct. Area ID (Current Leaf) NVARCSTR 30 0 0 no
2 LEAF_LVL Leaf Level INTEGER 4 0 0 no
Rapid Mart

5 LVL_00_DESCR Funct. Area Level 0 Description NVARCSTR 64 0 0 yes
6 LVL_00_FULL_NAME Funct. Area Level 0 ID and Description NVARCSTR 120 0 0 yes
7 LVL_00_ID PK Funct. Area Level 0 ID NVARCSTR 30 0 0 no

Appendix

Appendix
FUNCTIONAL_AREA_HIER_VR
Functional Area Hierarchy - Vertical
Column Dtype Is
1 CHILD_DESCR Child Funct. Area Description NVARCSTR 64 0 0 yes
2 CHILD_FULL_NAME Child Funct. Area ID and Description NVARCSTR 120 0 0 yes
3 CHILD_ID PK Child Funct. Area ID NVARCSTR 30 0 0 no
4 DEPTH Hierarchy Depth INTEGER 4 0 0 yes
5 LEAF_FLAG Leaf Flag INTEGER 4 0 0 yes
Rapid Mart

8 PARENT_DESCR Parent Funct. Area Description NVARCSTR 64 0 0 yes
9 PARENT_FULL_NAME Parent Funct. Area ID and Description NVARCSTR 120 0 0 yes
10 PARENT_ID PK Parent Funct. Area ID NVARCSTR 30 0 0 no
11 ROOT_FLAG Root Flag INTEGER 4 0 0 yes

Appendix
INTERNAL_ORDER
AUFK - Internal Order Master
Column Dtype Is
ALLOCTN_GRP_CO
1 Allocation Group Code NVARCSTR 2 0 0 yes
DE
2 APPLICTN_DATE AUFK-USER5 DATETIME 24 0 9 yes
3 BUS_AREA_ID AUFK-GSBER NVARCSTR 4 0 0 yes
4 BUS_AREA_NAME Business area description NVARCSTR 30 0 0 yes
5 CHANGE_DATE AUFK-AEDAT DATETIME 24 0 9 yes
6 CLOSE_DATE AUFK-IDAT3 DATETIME 24 0 9 yes
7 CMPNY_CODE_ID AUFK-BUKRS NVARCSTR 4 0 0 yes
8 CMPNY_CODE_NAME Name of the company code or company NVARCSTR 25 0 0 yes
9 COMPLT_DATE AUFK-IDAT2 DATETIME 24 0 9 yes
COST_CNTR_ID_ALL
10 AUFK-KOSTL NVARCSTR 10 0 0 yes
OCTN
COST_CNTR_ID_RES
11 AUFK-KOSTV NVARCSTR 10 0 0 yes
P
COST_CNTR_ID_RQS
12 AUFK-AKSTL NVARCSTR 10 0 0 yes
T
COST_COLLECTR_KE
13 AUFK-CCKEY NVARCSTR 23 0 0 yes
Y
COST_ELEM_ID_SET
14 AUFK-KSTAR NVARCSTR 10 0 0 yes
TLMNT
15 CREATE_DATE AUFK-ERDAT DATETIME 24 0 9 yes
16 CTRL_AREA_ID AUFK-KOKRS NVARCSTR 4 0 0 yes

Appendix
17 CTRL_AREA_NAME Name of the controlling area NVARCSTR 25 0 0 yes
18 CURR_ID AUFK-WAERS NVARCSTR 5 0 0 yes
19 DELETE_CODE AUFK-LOEKZ NVARCSTR 1 0 0 yes
20 DEPARTMENT AUFK-USER6 NVARCSTR 15 0 0 yes
DD07T - DDTEXT(lookup) - Order category

21 DOC_CATEG_DESCR NVARCSTR 60 0 0 yes
description
22 DOC_CATEG_ID AUFK-AUTYP NVARCSTR 2 0 0 yes
23 DOC_TYPE_DESCR T003P-TXT(lookup) - Short text NVARCSTR 40 0 0 yes
24 DOC_TYPE_ID AUFK-AUART NVARCSTR 4 0 0 yes
25 EQUITY_TYPE_CODE AUFK-ETYPE NVARCSTR 3 0 0 yes
EST_TRX_COST_ORD
26 AUFK-USER4 DECIMAL 48 11 2 yes
ER
EXTERNAL_ORDER
27 AUFK-AUFEX NVARCSTR 20 0 0 yes
_NUM
GL_ACCT_ID_ALLOCT
28 AUFK-SAKNR NVARCSTR 10 0 0 yes
N
29 INTERNAL_ORDER_ID PK AUFK-AUFNR NVARCSTR 12 0 0 no
INTERNAL_ORDER_ID
30 AUFK-REFNR NVARCSTR 12 0 0 yes
_REF
INTERNAL_ORDER_ID
31 AUFK-ASTNR NVARCSTR 1 0 0 yes
_STATS
JOINT_VENTURE_CO
32 AUFK-VNAME NVARCSTR 6 0 0 yes
DE
Rapid Mart


Appendix
35 LOCATN_ID AUFK-STORT NVARCSTR 10 0 0 yes
36 OBJ_ID AUFK-OBJNR NVARCSTR 22 0 0 yes
37 ORDER_DESCR AUFK-KTEXT NVARCSTR 40 0 0 yes
38 ORDER_STATUS_ID AUFK-ASTKZ NVARCSTR 2 0 0 yes
39 OVERHEAD_CODE AUFK-ZSCHL NVARCSTR 6 0 0 yes
PLANNED_CLOSE_DA
40 AUFK-PDAT3 DATETIME 24 0 9 yes
TE
PLANNED_COMPLT
41 AUFK-PDAT2 DATETIME 24 0 9 yes
_DATE
42 PLANNED_REL_DATE AUFK-PDAT1 DATETIME 24 0 9 yes
43 PLANT_ID AUFK-WERKS NVARCSTR 4 0 0 yes
44 PLANT_ID_LOCATN AUFK-SOWRK NVARCSTR 4 0 0 yes
45 PLANT_NAME Name NVARCSTR 30 0 0 yes
46 PROFIT_CNTR_ID AUFK-PRCTR NVARCSTR 10 0 0 yes
47 PROJ_ELEM_DESCR PS: Short description (1st text line) NVARCSTR 40 0 0 yes
AUFK-PSPEL lookup to PRPS.POSID - WBS

48 PROJ_ELEM_ID NVARCSTR 24 0 0 yes
element External ID
49 RECOVERY_CODE AUFK-RECID NVARCSTR 2 0 0 yes
50 RELEASE_DATE AUFK-IDAT1 DATETIME 24 0 9 yes
51 RESP_PERSON AUFK-USER2 NVARCSTR 20 0 0 yes
52 SALES_LINE_ITEM_ID AUFK-KDPOS NVARCSTR 6 0 0 yes

Appendix
53 SALES_ORDER_ID AUFK-KDAUF NVARCSTR 10 0 0 yes
54 STATUS_UPDT_DATE AUFK-STDAT DATETIME 24 0 9 yes
55 WORK_BEGIN_DATE AUFK-USER7 DATETIME 24 0 9 yes
56 WORK_END_DATE AUFK-USER8 DATETIME 24 0 9 yes
INTERNAL_ORDER_HIER
CCSS-AUFNR - Internal Order Hierarchy- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Internal Order Child Node Description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Internal Order Child Node ID NVARCSTR 12 0 0 no
Rapid Mart

6 PARENT_DESCR Internal Order Parent Node Descritpion NVARCSTR 64 0 0 yes
7 PARENT_ID PK Internal Order Parent Node ID NVARCSTR 12 0 0 no

Appendix
CCSS-AUFNR Internal Order Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
ETL_ERROR_COLU
MN
Rapid Mart

8 PARENT_DESCR Internal Order Parent Node Descritpion NVARCSTR 64 0 0 yes

Appendix
INTERNAL_ORDER_HIER_HZ
CCSS-AUFNR - Internal Order hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 INTERNAL_ORDER_ID PK Internal order current node ID NVARCSTR 12 0 0 no
2 LEAF_LVL Current Node level depth DECIMAL 48 28 0 no
Rapid Mart

5 LVL_00_DESCR Internal Order Root node Description NVARCSTR 64 0 0 yes
Internal Order Number and Descritpion for

6 LVL_00_FULL_NAME NVARCSTR 120 0 0 yes
Level 0
7 LVL_00_ID PK Internal Order Root node id NVARCSTR 12 0 0 no
8 LVL_01_DESCR Internal Order Level 1node Descritpion NVARCSTR 64 0 0 yes

Level 1
10 LVL_01_ID PK Internal Order Level 1node ID NVARCSTR 12 0 0 no
11 LVL_02_DESCR Internal Order Level 2 node Descritpion NVARCSTR 64 0 0 yes

Level 2
13 LVL_02_ID PK Internal Order Level 2 node ID NVARCSTR 12 0 0 no

Level 3

Appendix

Level 4
INTERNAL_ORDER_HIER_VR
CCSS-AUFNR - Internal Order hierarchy flattenned vertically - cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
Internal Order Number and Description Child

2 CHILD_FULL_NAME NVARCSTR 120 0 0 yes
Node)
4 DEPTH Internal Order Child depth level DECIMAL 48 28 0 yes
5 LEAF_FLAG Node Is leaf DECIMAL 48 28 0 yes
Rapid Mart

8 PARENT_DESCR Internal Order Parent Node Description NVARCSTR 64 0 0 yes
Internal Order Number and Description (Parent NVARCSTR

9 PARENT_FULL_NAME 120 0 0 yes
Node)
11 ROOT_FLAG Node Is root DECIMAL 48 28 0 yes

Appendix
INTERNAL_ORDER_STATUS
Internal Order status name and descritpion from TKO04
Column Dtype Is
1 DOC_TYPE_DESCR T003P.TXT -Short text NVARCSTR 40 0 0 yes
2 DOC_TYPE_ID PK TKO04.ART -Order type NVARCSTR 4 0 0 no
ORDER_STATUS_D
5 TKO04.TXT -Text (40 characters) for status NVARCSTR 40 0 0 yes
ESCR
6 ORDER_STATUS_ID PK TKO04.ASTNR -Order status NVARCSTR 2 0 0 no

Appendix
MATERIAL
MARA - Material Master
Column Dtype Is
XCHPF Batch management requirement

1 BATCH_MGMT_FLAG NVARCSTR 1 0 0 yes
indicator
2 CREATE_DATE ERSDA Date of creation DATETIME 24 0 9 yes
MARA-LVORM - Deletion flag for all material

3 DELETE_CODE NVARCSTR 1 0 0 yes
data (central)
4 DELETE_DATE LIQDT Deletion date DATETIME 24 0 9 yes
5 DIVISION_DESCR TSPAT.VTEXT Division Description NVARCSTR 20 0 0 yes
6 DIVISION_ID MARA.SPART Division NVARCSTR 2 0 0 yes
INDUSTRY_SECTOR_I
7 MARA.MBRSH Industry Sector ID NVARCSTR 1 0 0 yes
D
INDUSTRY_SECT_DE Lookup description of MARA.MBRSH Industry

SCR sector
Rapid Mart

11 LOW_LVL_CODE MARA.DISST - Low level code NVARCSTR 3 0 0 yes
12 MATERIAL_ID PK MATNR Material number NVARCSTR 18 0 0 no
MIN_REM_SHELF_LIF
13 MARA.MHDRZ Minimum remaining shelf life INTEGER 4 0 0 yes
E
14 MODIFIED_DATE MARA.LAEDA Date of last change DATETIME 24 0 9 yes
MTRL_CATEG_DES
15 Category Description NVARCSTR 60 0 0 yes
CR
16 MTRL_CATEG_ID MARA.ATTYP Material category NVARCSTR 2 0 0 yes

Appendix
17 MTRL_DESCR MAKTX Material description NVARCSTR 40 0 0 yes
18 MTRL_FULL_NAME Material ID and Material Description NVARCSTR 64 0 0 yes
19 MTRL_GRP_DESCR WGBEZ Description of material group NVARCSTR 20 0 0 yes
20 MTRL_GRP_ID MATKL Material group NVARCSTR 9 0 0 yes
MARA.MFRPN - Manfuacturer Part (Material)

21 MTRL_ID_MANUFCTR NVARCSTR 40 0 0 yes
Number
22 MTRL_TYPE_DESCR Lookup description of MARA.MTART in T134T NVARCSTR 25 0 0 yes
23 MTRL_TYPE_ID MTART Material type NVARCSTR 4 0 0 yes
24 PROD_HIER_ID PRDHA Product hierarchy NVARCSTR 18 0 0 yes
PURCH_STATUS_C
25 General material status: Purchasing NVARCSTR 2 0 0 yes
ODE
26 REVISION_LVL Lookup AEOI.REVLV - Material revision level NVARCSTR 2 0 0 yes
SALES_STATUS_COD
27 MARA.MSTAV General material status: sales NVARCSTR 2 0 0 yes
E
TRANSPORT_GRP_
28 MARA.TRAGR Transportation group NVARCSTR 4 0 0 yes
CODE
29 TTL_SHELF_LIFE MARA.MHDHB Total shelf life in days INTEGER 4 0 0 yes
30 UOM_ID_BASE MEINS Base unit of measure NVARCSTR 3 0 0 yes
31 UOM_ID_ORDER MARA.BSTME Order unit (purchasing) NVARCSTR 3 0 0 yes
32 UOM_ID_VOLUME MARA.VOLEH Volume unit NVARCSTR 3 0 0 yes
33 UOM_ID_WEIGHT MARA.GEWEI Unit of weight NVARCSTR 3 0 0 yes
34 VALID_FROM_DATE MARA.DATAB Date valid from DATETIME 24 0 9 yes

Appendix
35 VOLUME MARA.VOLUM Volume DECIMAL 48 13 3 yes
36 WEIGHT MARA.NTGEW Net weight DECIMAL 48 13 3 yes

Appendix
MATERIAL_BATCH
Batch material managerment - Material Master from MCHA
Column Dtype Is
TMABCT.TMABC - lookup on ABC indicator

1 ABC_CATEG_DESCR NVARCSTR 30 0 0 yes
descritpion
2 ABC_CATEG_ID MARC.MAABC ABC indicator NVARCSTR 1 0 0 yes
Lookup MBEW.SALK3 - Stock Valuation Price ,

AMT_VALUATN_PRIC Moving Average or Standard depending on
3 price control indicator in MBEW (current Value DECIMAL 48 13 2 yes
E
only)
4 AVAIL_DATE MCHA.VERAB - Availability date DATETIME 24 0 9 yes
Lookup MARM.UMREZ Factor to convert from

BASE_TO_PROD_U
5 BASE UOM to PROD UOM. (PROD_QTY = INTEGER 4 0 0 yes
OM_RATE MENGE / UMREZ)
6 BATCH_ID PK MCHA.CHARG - Batch number NVARCSTR 10 0 0 no
BATCH_NUM_VEND
7 MCHA.LICHA - Vendor batch number NVARCSTR 15 0 0 yes
OR
8 BULK_MTRL_FLAG MARC.SCHGT Indicator: bulk material NVARCSTR 1 0 0 yes
9 CMPNY_CODE_ID T001K.BUKRS Company code NVARCSTR 4 0 0 yes
10 CMPNY_CODE_NAME T001.BUTXT Name of the company NVARCSTR 25 0 0 yes
11 COUNTRY_ID_ORIGIN MARC.HERKL Materials country of origin NVARCSTR 3 0 0 yes
COUNTRY_NAME_O Lookup description onT005T.LANDX for

RIGIN Country name
13 CREATE_DATE MCHA.ERSDA - Date of creation DATETIME 24 0 9 yes
14 CURR_ID Local Currency Key NVARCSTR 5 0 0 yes
15 DAYS_PLAN_DELIV MARC.PLIFZ - Planned delivery time in days INTEGER 4 0 0 yes
MARC.WEBAZ - Planned goods receipt

16 DAYS_PLAN_GR processing time in days - includes inspection INTEGER 4 0 0 yes
time

Appendix
MARC.WZEIT - Total replenishment lead time
17 DAYS_REPLENISH in days - in house production time and/or INTEGER 4 0 0 yes
delivery lead tim
18 DAYS_TO_PRODUCE MARC.DZEIT - In-house production time INTEGER 4 0 0 yes
MARC.LVORM - Plant level material deletion

19 DELETE_FLAG NVARCSTR 1 0 0 yes
indicator
22 EXPIRE_DATE MCHA.VFDAT - Shelf life expiration date DATETIME 24 0 9 yes
INDUSTRY_SECTOR_I
D
INDUSTRY_SECT_DE Lookup description of MARA.MBRSH Industry

SCR sector
25 LOAD_DATE Date and time when loaded into RapidMart DATETIME 24 0 9 yes
Time in a string format when the record was

loaded into the target database
27 MATERIAL_ID PK MARC.MATNR Material number NVARCSTR 18 0 0 no
28 MRP_CTRLLER_ID MARC.DISPO MRP controller NVARCSTR 3 0 0 yes
MRP_CTRLLER_NA T024D.DSNAM - Name of MRP controller -

ME lookup
T438T.DIBEZ -Long MRP Type Description

30 MRP_TYPE_DESCR NVARCSTR 30 0 0 yes
from T438T
31 MRP_TYPE_ID MARC.DISMM MRP type code NVARCSTR 2 0 0 yes
MTRL_CATEG_DES
32 lookup on ATTYP domain in DD07T NVARCSTR 60 0 0 yes
CR
34 MTRL_DESCR MAKT.MAKTX -Material description NVARCSTR 40 0 0 yes

Appendix
NEXT_INSPECTN_DA
39 MCHA.QNDAT - Next inspection date DATETIME 24 0 9 yes
TE
40 PLANT_ID PK MARC.WERKS Plant NVARCSTR 4 0 0 no
41 PLANT_NAME T001W.NAME1 -Name NVARCSTR 30 0 0 yes
PROCUREMNT_TYP Lookup DD07T - Procurement type - BESKZ

E_DESCR domain
PROCUREMNT_TYP
43 MARC.BESKZ - Procurement type code NVARCSTR 20 0 0 yes
E_ID
Lookup description of T024.EKNAM - Purchase NVARCSTR

44 PURCH_GRP_DESCR 30 0 0 yes
Group Name
45 PURCH_GRP_ID MARC.EKGRP Purchasing group NVARCSTR 3 0 0 yes
QTY_REORDER_POIN
46 MARC.MINBE Reorder point DECIMAL 48 13 3 yes
T
47 QTY_SAFETY_STOCK MARC.EISBE Safety stock DECIMAL 48 13 3 yes
QUALITY_INSPECT_F MARC.INSMK - Quality inspection indicator - X NVARCSTR

48 1 0 0 yes
LAG is yes
RESTRICT_STOCK_F
49 MCHA.ZUSTD - Batch in restricted-use stock NVARCSTR 1 0 0 yes
LAG
SPECL_PROCUREM Lookup description of MARC.SOBSL in T460T- NVARCSTR

50 30 0 0 yes
NT_TYPE_DESCR Special procurement type
SPECL_PROCUREM
51 MARC.SOBSL - Special procurement type NVARCSTR 2 0 0 yes
NT_TYPE_ID
Lookup description on TMBWT.BWSCB for

52 SUPPLY_SRC_DESCR NVARCSTR 40 0 0 yes
supply source description

Appendix
53 SUPPLY_SRC_ID MARC.BWSCL Source of supply IS-R NVARCSTR 1 0 0 yes
Lookup MARC.AUSME in T006A to get Base

54 UOM_CODE_BASE NVARCSTR 3 0 0 yes
Unit External Code
Lookup MARC.AUSME in T006A to get Unit of NVARCSTR

55 UOM_CODE_ISSUE 3 0 0 yes
Issue Long Description
Lookup MARC.FRTME in T006A to get

56 UOM_CODE_PROD NVARCSTR 3 0 0 yes
Production UOM External code
MARC.AUSME - Unit of measure for goods

58 UOM_ID_ISSUE NVARCSTR 3 0 0 yes
issue
59 UOM_ID_PROD MARC.FRTME Production unit of measure NVARCSTR 3 0 0 yes
60 VALUATN_AREA_ID T001W.BWKEY -Valuation area NVARCSTR 4 0 0 yes
61 VALUATN_TYPE_ID MCHA.BWTAR - Valuation type NVARCSTR 10 0 0 yes
62 VENDOR_ID MCHA.LIFNR - Vendors account number NVARCSTR 10 0 0 yes
63 VENDOR_NAME Lookup - LFA1.NAME1 Vendor Name 1 NVARCSTR 35 0 0 yes

Appendix
MATERIAL_BY_PLANT
MARA and MARC Tables - Plant Level Material attributes
Column Dtype Is
TMABCT.TMABC - lookup on ABC indicator

1 ABC_CATEG_DESCR NVARCSTR 30 0 0 yes
descritpion
2 ABC_CATEG_ID MARC.MAABC ABC indicator NVARCSTR 1 0 0 yes
Lookup MARM.UMREZ Factor to convert from

BASE_TO_PRODUC
3 BASE UOM to PROD UOM. (PROD_QTY = INTEGER 4 0 0 yes
TN_MULTIPLR MENGE / UMREZ)
Lookup MARC.XCHAR Batch management

4 BATCH_MGMT_FLAG NVARCSTR 1 0 0 yes
indicator (internal)
BATCH_MGMT_REQ MARC.XCHPF Batch management

_FLAG requirement indicator
6 BULK_MTRL_FLAG MARC.SCHGT Indicator: bulk material NVARCSTR 1 0 0 yes
7 COUNTRY_ID_ORIGIN MARC.HERKL Materials country of origin NVARCSTR 3 0 0 yes
COUNTRY_NAME_O Lookup description onT005T.LANDX for

RIGIN Country name
9 DAYS_PLAN_DELIV MARC.PLIFZ - Planned delivery time in days INTEGER 4 0 0 yes
MARC.WEBAZ - Planned goods receipt

10 DAYS_PLAN_GR processing time in days - includes inspection INTEGER 4 0 0 yes
time
MARC.WZEIT - Total replenishment lead time

11 DAYS_REPLENISH in days - in house production time and/or INTEGER 4 0 0 yes
delivery lead tim
12 DAYS_TO_PRODUCE MARC.DZEIT - In-house production time INTEGER 4 0 0 yes
MARC.LVORM - Plant level material deletion

13 DELETE_FLAG NVARCSTR 1 0 0 yes
indicator
INDUSTRY_SECTOR_ Lookup description of MARA.MBRSH Industry

DESCR sector

Appendix
INDUSTRY_SECTOR_I
D
18 LOAD_DATE Date and time loaded into RapidMart DATETIME 24 0 9 yes
19 LOAD_TIME Time loaded into RapidMart NVARCSTR 8 0 0 yes
20 MATERIAL_ID PK MARC.MATNR Material number NVARCSTR 18 0 0 no
21 MRP_CTRLLER_ID MARC.DISPO MRP controller NVARCSTR 3 0 0 yes
MRP_CTRLLER_NA T024D.DSNAM - Name of MRP controller -

ME lookup
T438T.DIBEZ -Long MRP Type Description

23 MRP_TYPE_DESCR NVARCSTR 30 0 0 yes
from T438T
24 MRP_TYPE_ID MARC.DISMM MRP type code NVARCSTR 2 0 0 yes
MTRL_CATEG_DES
25 lookup on ATTYP domain in DD07T NVARCSTR 60 0 0 yes
CR
27 MTRL_DESCR MAKT.MAKTX -Material description NVARCSTR 40 0 0 yes
28 MTRL_FULL_NAME Material ID and Material Description NVARCSTR 64 0 0 yes
33 PLANT_FULL_NAME Plant ID and Plant Name NVARCSTR 40 0 0 yes
34 PLANT_ID PK MARC.WERKS Plant NVARCSTR 4 0 0 no

Appendix
PROCUREMNT_TYP Lookup DD07T - Procurement type - BESKZ

E_DESCR domain
PROCUREMNT_TYP
37 MARC.BESKZ - Procurement type code NVARCSTR 20 0 0 yes
E_ID
38 PROFIT_CNTR_ID MARC.PRCTR Profit center NVARCSTR 10 0 0 yes
Lookup description of T024.EKNAM - Purchase NVARCSTR

39 PURCH_GRP_DESCR 30 0 0 yes
Group Name
40 PURCH_GRP_ID MARC.EKGRP Purchasing group NVARCSTR 3 0 0 yes
QTY_REORDER_POIN
41 MARC.MINBE Reorder point DECIMAL 48 13 3 yes
T
42 QTY_SAFETY_STOCK MARC.EISBE Safety stock DECIMAL 48 13 3 yes
QUALITY_INSPECT_F MARC.INSMK - Quality inspection indicator - X NVARCSTR

43 1 0 0 yes
LAG is yes
SPECL_PROCUREM Lookup description of MARC.SOBSL in T460T- NVARCSTR

44 30 0 0 yes
NT_TYPE_DESCR Special procurement type
SPECL_PROCUREM
45 MARC.SOBSL - Special procurement type NVARCSTR 2 0 0 yes
NT_TYPE_ID
Lookup description on TMBWT.BWSCB for

46 SUPPLY_SRC_DESCR NVARCSTR 40 0 0 yes
supply source description
47 SUPPLY_SRC_ID MARC.BWSCL Source of supply IS-R NVARCSTR 1 0 0 yes
Lookup MARC.AUSME in T006A to get Base

48 UOM_CODE_BASE NVARCSTR 3 0 0 yes
Unit External Code
Lookup MARC.AUSME in T006A to get Unit of NVARCSTR

49 UOM_CODE_ISSUE 3 0 0 yes
Issue Long Description
Lookup MARC.FRTME in T006A to get

50 UOM_CODE_PROD NVARCSTR 3 0 0 yes
Production UOM External code
MARC.AUSME - Unit of measure for goods

52 UOM_ID_ISSUE NVARCSTR 3 0 0 yes
issue

Appendix
53 UOM_ID_PROD MARC.FRTME Production unit of measure NVARCSTR 3 0 0 yes
MATERIAL_GROUP
T023T - Material Group
Column Dtype Is
1 LOAD_DATE Date and Time Loaded into Rapid Mart DATETIME 24 0 9 yes
3 MTRL_GRP_DESCR Material Group Description NVARCSTR 20 0 0 yes
4 MTRL_GRP_ID PK Material Group ID NVARCSTR 9 0 0 no

Appendix
MATERIAL_TYPE
Material Type descriptive attributes from T134, T134T
Column Dtype Is
1 CONFIG_FLAG Configurable Material - X - yes INTEGER 4 0 0 yes
MTRL_ITEM_GRP_DE
4 TPTMT.BEZEI Division Description NVARCSTR 20 0 0 yes
SCR
T134.VMTPO - Default value for material item

5 MTRL_ITEM_GRP_ID NVARCSTR 4 0 0 yes
category group
6 MTRL_TYPE_DESCR T134T.MTBEZ -Description of material type NVARCSTR 25 0 0 yes
7 MTRL_TYPE_ID PK T134T.MTART -Material type NVARCSTR 4 0 0 no
8 PRICE_CTRL_DESCR lookup on VPRSV domain in DD07T NVARCSTR 60 0 0 yes
9 PRICE_CTRL_ID T134.VPRSV -Price control indicator (VPRSV) NVARCSTR 1 0 0 yes

Appendix
MILESTONE_FACT
Project Milestone details from MLST/PLKO/PLPO/AFVC
Column Dtype Is
1 ACTIVITY_ID AFVC/PLPO.LARNT -Activity Type NVARCSTR 6 0 0 yes

2 ACTL_END_DATE met)+MLST.LST_ACTTM - Actual date/time DATETIME 24 0 9 yes
(Milestone met)
3 CHANGE_DATE MLST.DATEV - Milestone changed on DATETIME 24 0 9 yes
4 CHART_OF_ACCT_ID T001.KTOPL-Chart of accts ID - Lookup NVARCSTR 4 0 0 yes
5 CMPNY_CODE_ID AFVC/PLPO.BUKRS -Company Code NVARCSTR 4 0 0 yes
Calculated based on MLST.LST_FERTG -

6 COMPLETE_FLAG Percentage of completion (%) - if 100% then 1, INTEGER 4 0 0 yes
else 0
7 COST_ELEM_ID AFVC/PLPO.SAKTO -Cost Element NVARCSTR 10 0 0 yes
8 CREATE_DATE MLST.DATEH - Milestone created on DATETIME 24 0 9 yes
PLKO/TKA02.KOKRS - Controling Area ID (or

9 CTRL_AREA_ID NVARCSTR 4 0 0 yes
alternative lookup on Company Code)
10 CTRL_KEY_ID AFVC/PLPO.STEUS -Control key NVARCSTR 4 0 0 yes
11 CURRENT_FLAG 1- the record is current INTEGER 4 0 0 yes
MLST.SDDAT Key determining the date for

12 DATE_KEY_ID milestone in sales order (domain NVARCSTR 10 0 0 yes
MLST_SDDAT)
Number of Days between MLST.LST_ACTDT -

13 DAYS_ACTL_DURTN Actual date (Milestone met) and MLST.DATEH DECIMAL 48 22 7 yes
- Milestone created on
DAYS_DIFF_FIXED_B Number of Days between Fixed Basic and

ASIC Actual Milestone end
DAYS_DIFF_FIXED_F Number of Days between Fixed Forecast and

CST Actual Milestone end
DAYS_DIFF_SCHED_ Number of Days between Scheduled Basic and DECIMAL

16 48 22 7 yes
BASIC Actual Milestone end

Appendix
DAYS_DIFF_SCHED_ Number of Days between Scheduled Forecast
FCST and Actual Milestone end
Number of Days between MLST.TEDAT -

DAYS_SCHED_DUR
18 Scheduled milestone date (Basic) and DECIMAL 48 22 7 yes
TN MLST.DATEH - Milestone created on
Dimension Source. This is a combined
DIM_SRC_ID_DOCCT dimension combining different varieties of
G "Reference Date Key" from different sources.
This field identifies the source of "Referere
dimension combining different varieties of
20 DIM_SRC_ID_DTKEY NVARCSTR 10 0 0 yes
"Reference Date Key" from different sources.
MLST.AUTYP - Order category (AUFTYP -

21 DOC_CATEG_ID NVARCSTR 10 0 0 yes
Internal Order category)
MLST.EDATU - Fixed milestone date

FIXED_BASIC_END_D (basic)+MLST.EZEIT - Fixed milestone time
22 DATETIME 24 0 9 yes
ATE (Basic). Fixed date on which the milestone
should be reached (no offset is possible)
MLST.PDATU - Fixed milestone date
FIXED_FCST_END_D (F)+MLST.PZEIT - Fixed milestone time (F). -
ATE Forecast date on which the milestone should
be reached (no offset is possible)
MLST.KZ_WFLOW - Indicator: Milestone is

24 FUNCTION_FLAG INTEGER 4 0 0 yes
used for milestone functions
MLST.PLNTY - Standard network type

25 GROUP_APPLICTN_ID NVARCSTR 1 0 0 yes
-Application of the task list
26 GROUP_ID MLST.PLNNR Group key NVARCSTR 8 0 0 yes
27 GROUP_NODE_ID MLST.PLNKN - Number of the task list node NVARCSTR 8 0 0 yes
28 GROUP_TYPE_ID MLST.PLNTY -Task List Type NVARCSTR 1 0 0 yes
Number of Hours between MLST.LST_ACTDT

HOURS_ACTL_DUR
29 - Actual date (Milestone met) and DECIMAL 48 22 7 yes
HOURS_DIFF_FIXED_ Number of Hours between Fixed Basic and

BASIC Actual Milestone end
HOURS_DIFF_FIXED_ Number of Hours between Fixed Forecast and DECIMAL

31 48 22 7 yes
FCST Actual Milestone end
HOURS_DIFF_SCHED Number of Hours between Scheduled Basic

_BASIC and Actual Milestone end
HOURS_DIFF_SCHED Number of Hours between Scheduled Forecast DECIMAL

33 48 22 7 yes
_FCST and Actual Milestone end
Number of Hours between MLST.TEDAT -

HOURS_SCHED_DU
RTN MLST.DATEH - Milestone created on

Appendix
35 INTERNAL_ORDER_ID AFKO.AUFNR - Internal Order Number NVARCSTR 12 0 0 yes
36 LATEST_DATE_FLAG MLST.LATED- Indicator: Latest dates INTEGER 4 0 0 yes
39 MILESTONE_DESCR MLTX.KTEXT -Milestone description (lookup) NVARCSTR 40 0 0 yes
40 MILESTONE_ID PK MLST.MLST_ZAEHL - Milestone number NVARCSTR 12 0 0 no
41 MILESTONE_SEQ_ID PK MLST.ZAEHL - Internal counter NVARCSTR 8 0 0 no
NETWORK_PROFILE_
42 PLKO.PROFIDNETZ -Profile (network) NVARCSTR 7 0 0 yes
ID
OFFSET_TO_FINISH_ MLST.DLTAS - Ind: Reference for offset

43 INTEGER 4 0 0 yes
FLAG (start/finish activity date)
OPERATN_ROUTING_ MLST.AUFPL - Routing number for operations NVARCSTR

44 10 0 0 yes
ID in the order
45 OPERATN_SEQ_ID MLST.APLZL - Internal counter NVARCSTR 8 0 0 yes
46 PLANT_ID AFVC/PLPO/PLKO.WERKS - Plant ID NVARCSTR 4 0 0 yes
MLST.LST_FERTG - Percentage of completion INTEGER

47 PRCNT_COMPLETE 4 0 0 yes
(%)
MLST.PRCNT - Percentual offset of milestone

48 PRCNT_OFFSET INTEGER 4 0 0 yes
to activity date
PROGRESS_ANALYSI MLST.KZ_LSTWR - Milestone relevant for

S_FLAG progress analysis
AFVC.PROJN -Work breakdown structure

element (WBS element) / Lookup to
PRPS.POSID - Project Element (WBS)
External ID
MLST.PSPNR - WBS element / Lookup to
51 PROJ_ELEM_ID_STD PRPS.POSID - Project Element (WBS) NVARCSTR 24 0 0 yes
External ID
52 PROJ_ID PROJ.PSPID - Project External ID NVARCSTR 24 0 0 yes

Appendix
T001W.EKORG Purchasing organization
53 PURCH_ORG_ID NVARCSTR 4 0 0 yes
(lookup)
54 QTY_OFFSET MLST.DELTA - Offset for milestone date INTEGER 4 0 0 yes
RELEASE_STOP_FLA
55 MLST.KZ_FRMST - Release stop indicator INTEGER 4 0 0 yes
G
56 RESOURCE_ID AFVC/PLPO.ARBID -Object ID of the resource NVARCSTR 8 0 0 yes
57 ROUTING_ID Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR 11 0 0 yes
SALES_DOC_DATE_F MLST.KZ_FAKTP - Milestone is relevant for

LAG date in sales document
MLST.TEDAT - Scheduled milestone date
SCHED_BASIC_END_ (Basic); + MLST.TETIM - Scheduled milestone DATETIME
59 24 0 9 yes
DATE time (Basic). You can offset the milestone to
the start, finish value
MLST.TPDAT - Scheduled milestone date
SCHED_FCST_END_D
60 (Forecast)+ MLST.TPTIM - Scheduled DATETIME 24 0 9 yes
ATE milestone time (Forecast). It can be offset
Number of Seconds between

61 SECS_ACTL_DURTN MLST.LST_ACTDT - Actual date (Milestone DECIMAL 48 22 7 yes
met) and MLST.DATEH - Milestone created on
SECS_DIFF_FIXED_B Number of Seconds between Fixed Basic and

ASIC Actual Milestone end
SECS_DIFF_FIXED_F Number of Seconds between Fixed Forecast

CST and Actual Milestone end
SECS_DIFF_SCHED_ Number of Seconds between Scheduled Basic DECIMAL

64 48 22 7 yes
BASIC and Actual Milestone end
SECS_DIFF_SCHED_ Number of Seconds between Scheduled

FCST Forecast and Actual Milestone end
Number of Seconds between MLST.TEDAT -

SECS_SCHED_DUR
67 STATUS_PROFILE_ID MLST.STSMA - Status profile (for the network) NVARCSTR 8 0 0 yes
Alternate key generated in the Rapid Mart for

68 SURROGATE_DOC_ID DECIMAL 48 18 0 yes
reporting purposes
TREND_ANALYSIS_FL MLST.KZ_TREND - Milestone relevant for

AG trend analysis
MLST.DELTE - Time unit for offset of milestone NVARCSTR

70 UOM_ID_OFFSET 3 0 0 yes
date

Appendix
71 USAGE_ID MLST.MLSTN - Usage for the milestone NVARCSTR 5 0 0 yes
72 VALID_FROM_DATE MLST.DATUV - Valid-from date DATETIME 24 0 9 yes
The date until which this record is effective. It is

73 VALID_TO_DATE automatically generated by the Effective_Date DATETIME 24 0 9 yes
transform
WORK_CNTR_CATE CRHD.VERWE - Work center category ID

G_ID lookup
CRHD.ARBPL - Work center- Visible ID in

75 WORK_CNTR_ID NVARCSTR 8 0 0 yes
SAP
MILESTONE_USAGE
Milestone usage descriptive attributes from T433T
Column Dtype Is
3 USAGE_DESCR T433T.MSTXT - Milestone Usage description NVARCSTR 40 0 0 yes
4 USAGE_ID PK T433T.MLSTN - Milestone Usage ID NVARCSTR 5 0 0 no

Appendix
MRP_CONTROLLER
MRP controller information by plant from T024D
Column Dtype Is
1 BUS_AREA_DESCR TGSBT-GTEXT-Business area description NVARCSTR 30 0 0 yes
2 BUS_AREA_ID T024D.GSBER - Business area NVARCSTR 4 0 0 yes
5 MRP_CTRLLER_ID PK T024D.DISPO - MRP controller NVARCSTR 3 0 0 no
MRP_CTRLLER_NA
6 T024D.DSNAM - Name of MRP controller NVARCSTR 18 0 0 yes
ME
MRP_CTRLLER_PH T024D.DSTEL - MRP controllers telephone

ONE number
8 PLANT_ID PK T001W.WERKS Plant NVARCSTR 4 0 0 no
9 PLANT_NAME T001W.NAME1 - lookup on Plant Name NVARCSTR 40 0 0 yes
10 PROFIT_CNTR_ID T024D.PRCTR - Profit center NVARCSTR 10 0 0 yes
11 PROFIT_CNTR_NAME CEPC.NAME1 - lookup Prifit Center Name NVARCSTR 35 0 0 yes
12 PURCH_GRP_DESCR EKNAM.T024 Description of purchasing group NVARCSTR 18 0 0 yes
13 PURCH_GRP_ID T024D.EKGRP - Purchasing group NVARCSTR 3 0 0 yes
14 RECIPIENT_NAME T024D.MEMPF - Recipient name NVARCSTR 12 0 0 yes

Appendix
NETWORK_HIER_VR
Vertical representation of Network Relationship stored in AFAB
Column Dtype Is
CHILD_OPERATN_DE
1 AFVC.LTXA1 - Operation short text - Child NVARCSTR 40 0 0 yes
SCR
CHILD_OPERATN_FU Child Node full name = Activity Number

LL_NAME (Operation Number) + Descr
CHILD_OPERATN_NU
3 AFVC.VORNR Activity Number - child node NVARCSTR 4 0 0 yes
M
CHILD_ORDER_DESC AUFK-KTEXT - Internal Order Description -for

R the child node
5 DEPTH Hierarchy Depth INTEGER 4 0 0 yes
INTERNAL_ORDER_ID AUFK.AUFNR - Network Id (order number) for

_CHILD the child node
INTERNAL_ORDER_ID AUFK.AUFNR - Order Number of the Parent

_PARENT node
8 LEAF_FLAG Node is the child (1/0) INTEGER 4 0 0 yes
Idented display Hierarchy Depth; hard-coded

9 LEVEL_DISPLAY NVARCSTR 250 0 0 yes
up to 60 levels
the target database

target database
AFAB.AUFPL_NCH/AFAB.AUFPL_VOR - No.
OPERATN_ROUTING_ PK
12 identifying the network to which the NVARCSTR 10 0 0 no
ID_CHILD successor/predecessor belongs
AFAB.AUFPL_NCH/AFAB.AUFPL_VOR - No.
OPERATN_ROUTING_ PK
ID_PARENT successor/predecessor belongs
AFAB.APLZL_NCH/AFAB.APLZL_VOR - No.
OPERATN_SEQ_ID_C PK
HILD successor/predecessor belongs
AFAB.APLZL_NCH/AFAB.APLZL_VOR - No.
OPERATN_SEQ_ID_P PK
ARENT successor/predecessor belongs
PARENT_OPERATN
16 AFVC.LTXA1 - Operation short text - Parent NVARCSTR 40 0 0 yes
_DESCR

Appendix
PARENT_OPERATN_F Parent Node full name = Activity Number
ULL_NAME (Operation Number) + Descr
PARENT_OPERATN AFVC.VORNR Node number of the Parent

_NUM operation
PARENT_ORDER_D AUFK-KTEXT - Internal Order Description -for

ESCR the Parent node
RELATIONSHIP_TYPE PK AFAB.AOBAR - Type of relationship (lookup

20 NVARCSTR 2 0 0 no
_ID onto TCN2T)
21 ROOT_FLAG Node is Root (1/0) INTEGER 4 0 0 yes
NETWORK_PROFILE
Network profile descriptive attributes from TCN41, TCN41T
Column Dtype Is
GROUP_APPLICTN_D
1 TCN4T.PROFI_TXT -Text for Profile NVARCSTR 40 0 0 yes
ESCR
2 GROUP_APPLICTN_ID PK TCN41.PLNAW -Application of the task list NVARCSTR 1 0 0 no
NETWORK_PROFILE_ PK
5 TCN41.PROFIDNETZ -Network profile NVARCSTR 7 0 0 no
ID
T006A.MSEH3 -- Unit of Meas. ID in Local

6 UOM_CODE_DURTN Language (External unit of measurement NVARCSTR 3 0 0 yes
commercial format (3-char))

7 UOM_CODE_WORK Language (External unit of measurement NVARCSTR 3 0 0 yes
8 UOM_ID_DURTN TCN41.DAUNE -Normal duration/unit NVARCSTR 3 0 0 yes
9 UOM_ID_WORK TCN41.ARBEH - Unit for work NVARCSTR 3 0 0 yes

Appendix
NETWORK_RELATIONSHIP_FACT
Parent/Child relationship from AFAB for Internal Order Operations
Column Dtype Is
1 BUS_AREA_ID AFVC/AUFK.GSBER - Business Area NVARCSTR 4 0 0 yes
2 CMPNY_CODE_ID AFVC/AUFK.BUKRS Company Code NVARCSTR 4 0 0 yes
3 CTRL_AREA_ID AUFK.KOKRS -Controling Area ID NVARCSTR 4 0 0 yes
4 CTRL_KEY_ID AFVC.STEUS - Control key NVARCSTR 4 0 0 yes
DAYS_DURTN_EARLS Number of Days for Network Relationship

T based on Eraliest start/end dates
DAYS_DURTN_LATES Number of Days for Network Relationship

T based on Latest start/end dates
Max Number of Days for Network Relationship.

7 DAYS_DURTN_MAX Calculated as difference between latest end DECIMAL 48 22 7 yes
date and earliest start date
Min Number of Days for Network Relationship.

8 DAYS_DURTN_MIN Calculated as difference between earliest end DECIMAL 48 22 7 yes
date and latest start date
AFAB.FEABD - Earliest finish date for the

9 EARLST_END_DATE relationship+AFAB.FEABZ - Earliest finish time DATETIME 24 0 9 yes
for the relationship
AFAB.FSABD - Earliest start date for the

EARLST_START_DAT
10 relationship + AFAB.FSABZ - Earliest start time DATETIME 24 0 9 yes
E for the relationship
11 FUNCTNL_AREA_ID AFVC/AUFK.FUNC_AREA -Functional Area NVARCSTR 16 0 0 yes
HOURS_DURTN_EA Number of Hours for Network Relationship

RLST based on Eraliest start/end dates
HOURS_DURTN_LA Number of Hours for Network Relationship

TEST based on Latest start/end dates
Max Number of Hours for Network

14 HOURS_DURTN_MAX Relationship. Calculated as difference between DECIMAL 48 22 7 yes
latest end date and earliest start date
Min Number of Hours for Network Relationship.

15 HOURS_DURTN_MIN Calculated as difference between earliest end DECIMAL 48 22 7 yes
date and latest start date
16 INTERNAL_ORDER_ID AFKO.AUFNR - Order Number NVARCSTR 12 0 0 yes

Appendix
INTERNAL_ORDER_ID AUFK.AUFNR - Order Number of the Parent
_PAR node
AFAB.SEABD - Latest finish date of the

18 LATEST_END_DATE relationship+ AFAB.SEABZ - Latest finish time DATETIME 24 0 9 yes
of the relationship
AFAB.SSABD - Latest start date of the

LATEST_START_DAT
19 relationship + AFAB.SSABZ - Latest start time DATETIME 24 0 9 yes
E of the relationship
Date and time when the record loaded into

20 LOAD_DATE DATETIME 24 0 9 yes
RapidMart
22 LOCATN_ID AUFK.STORT Plant Location NVARCSTR 10 0 0 yes
MAX_INTERVAL_FLA AFAB.MIMAX - Indicates whether maximum

23 PK INTEGER 4 0 0 no
G time interval will be considered
MINS_DURTN_EARLS Number of Minutes for Network Relationship

T based on Eraliest start/end dates
MINS_DURTN_LATES Number of Minutes for Network Relationship

T based on Latest start/end dates
Max Number of Minutes for Network

26 MINS_DURTN_MAX Relationship. Calculated as difference between DECIMAL 48 22 7 yes
latest end date and earliest start date
Min Number of Minutes for Network

27 MINS_DURTN_MIN Relationship. Calculated as difference between DECIMAL 48 22 7 yes
earliest end date and latest start date
28 MRP_CTRLLER_ID AFKO.DISPO MRP controller for the order NVARCSTR 3 0 0 yes
29 OBJ_ID AFAB-OBJNR - Object number NVARCSTR 22 0 0 yes
AFVC.LTXA1 - Parent Operation short text (for NVARCSTR

30 OPERATN_DESCR 40 0 0 yes
child node)
OPERATN_DESCR_ AFVC.LTXA1 - Parent Operation short text - for NVARCSTR

31 40 0 0 yes
PAR parent node
OPERATN_FULL_NAM Child Node full name - Activity Number

E (Operation Number) + Description
OPERATN_FULL_NAM Parent Node full name - Activity Number

E_PAR (Operation Number) + Description
34 OPERATN_NUM AFVC.VORNR Activity Number NVARCSTR 4 0 0 yes

Appendix
AFVC.VORNR Node number of the Parent
35 OPERATN_NUM_PAR NVARCSTR 4 0 0 yes
operation
OPERATN_ROUTING_ PK AFAB.AUFPL_NCH - No. identifying the

ID network to which the successor belongs
OPERATN_ROUTING_ PK AFAB.AUFPL_VOR - No. identifying the

ID_PAR network to which the predecessor belong
AFAB.APLZL_NCH - Internal counter for the

38 OPERATN_SEQ_ID PK NVARCSTR 8 0 0 no
Child operation
OPERATN_SEQ_ID_P PK AFAB.APLZL_VOR - Internal counter for the

AR parent Operation
40 PLANT_ID AFAB/AFVC.WERKS - Plant NVARCSTR 4 0 0 yes
41 PROFIT_CNTR_ID AFVC/AUFK.PRCTR Profit Center NVARCSTR 10 0 0 yes
AFVC/AFPO.PROJN - Work breakdown

structure element (WBS element) Lookup on
External ID

(lookup)
AFAB.DAUER - Time interval between

45 QTY_INTERVAL DECIMAL 48 5 1 yes
relationships
RELATIONSHIP_TYPE PK AFAB.AOBAR - Type of relationship (lookup

_ID onto TCN2T)
47 RESOURCE_ID AFAB/AFVC.ARBID - Object ID NVARCSTR 8 0 0 yes
AFAB.DAUTM - Relationship duration (in

48 SECS_DURTN DECIMAL 48 28 0 yes
seconds) as result of scheduling
STORAGE_LOCATN_I
49 AFPO.LGORT Storage location NVARCSTR 4 0 0 yes
D
AFAB.ZEINH - Unit for the time interval

50 UOM_ID NVARCSTR 3 0 0 yes
between relationships
51 VALUATN_AREA_ID T001W.BWKEY Valuation area lookup NVARCSTR 4 0 0 yes
WORK_CNTR_CATE CRHD.VERWE - Work center category ID

G_ID lookup

Appendix
SAP
OBJECT_CLASS
DD07T - Object Class reference dimension
Column Dtype Is
Rapid Mart

3 OBJ_CLASS_DESCR Object Class Domain Descritpion NVARCSTR 60 0 0 yes
4 OBJ_CLASS_ID PK Object Class Domain ID NVARCSTR 10 0 0 no
OBJECT_NUMBER_TYPE
TBO01 - The object type is the first two characters of the object number, which is a unique object key per client (order, cost center, project,
...)
Column Dtype Is
OBJ_NUM_TYPE_DES TBO01.TXT60, TXT10, TXT15, TXT 20 -

CR Description
4 OBJ_NUM_TYPE_ID PK TBO01.OBART -Object Type Code NVARCSTR 2 0 0 no

Appendix
OBJECT_STATUS
Object statuses from JEST
Column Dtype Is
JEST.OBJNR Object number - for 'OR' and

1 INTERNAL_ORDER_ID NVARCSTR 10 0 0 yes
'NP' types - Internal Order ID
Date and time when the record is loaded into

Rapid Mart
3 LOAD_TIME Time loaded into Rapid Mart NVARCSTR 8 0 0 yes
4 OBJ_ID PK JEST-OBJNR - Object number NVARCSTR 22 0 0 no
OBJ_NUM_TYPE_DES
5 TBO01, TXT10 - Text, length 10 NVARCSTR 10 0 0 yes
CR
RPSCO.OBJNR Object number first 2

6 OBJ_NUM_TYPE_ID NVARCSTR 2 0 0 yes
characters
OPERATN_ROUTING_ JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR

7 10 0 0 yes
ID number of operations in the order
JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR

8 OPERATN_SEQ_ID 8 0 0 yes
number counter for order
9 PROJ_DESCR PROJ.POST1 - Project definition text NVARCSTR 40 0 0 yes
10 PROJ_ELEM_DESCR PRPS.POST1 Work breakdown structure Text NVARCSTR 40 0 0 yes

External ID
TJ02T.TXT04 - Individual status of an object

13 STATUS_CODE NVARCSTR 4 0 0 yes
(short form)
TJ02T.TXT04 - Individual status of an object

STATUS_CODE_NA
14 PK (short form) + JEST.STAT - Object NVARCSTR 60 0 0 no
ME status+TJ02T.TXT30 -Object status
15 STATUS_DESCR TJ02T.TXT30 -Object status NVARCSTR 30 0 0 yes
16 STATUS_ID JEST.STAT - Object status NVARCSTR 5 0 0 yes

Appendix
OBJECT_STATUS_HZ
Dimensional component loading horizontally represented selected ERP Object status sinformation from JEST for selected Statuses from
OBJECT_STATUS
Column Dtype Is
JEST-STAT (lookup) -ACPT object is Accepted INTEGER

1 ACCEPT_FLAG 4 0 0 yes
status is active (1 is active, 0 is inactive)
JEST-STAT (lookup) -BUDG object is

2 BUDGET_FLAG Budgeted status is active (1 is active, 0 is INTEGER 4 0 0 yes
inactive)
JEST-STAT (lookup) -ISBD object is

BUDGET_INSUFFICNT
3 Insuffiently Budgeted status is active (1 is INTEGER 4 0 0 yes
_FLAG active, 0 is inactive)
JEST-STAT (lookup) -CLSD object is Close

4 CLOSE_FLAG INTEGER 4 0 0 yes
JEST-STAT (lookup) -PLCS object is Cost

5 COST_PLAN_FLAG Planned status is active (1 is active, 0 is INTEGER 4 0 0 yes
inactive)
JEST-STAT (lookup) -CSPS object is Cost

6 COST_POST_FLAG Posted status is active (1 is active, 0 is INTEGER 4 0 0 yes
inactive)
JEST-STAT (lookup) -CRTD order is created

7 CREATE_FLAG INTEGER 4 0 0 yes
JEST-STAT (lookup) - DLFL, DLT object is

8 DELETE_FLAG deleted status is active (1 is active, 0 is INTEGER 4 0 0 yes
inactive)
JEST-STAT (lookup) -NSCH object is Not

9 FCST_ONLY_FLAG Scheduled status is active (1 is active, 0 is INTEGER 4 0 0 yes
inactive)
JEST-STAT (lookup) - CNF object is finally

FINAL_CONFIRM_FLA
10 confirmed status is active (1 is active, 0 is INTEGER 4 0 0 yes
G inactive)
FINAL_RELEASE_FLA JEST-STAT (lookup) -REL object is Released

G status is active (1 is active, 0 is inactive)
JEST.OBJNR Object number - for 'OR' and

'NP' types - Internal Order ID

Rapid Mart
JEST-STAT (lookup) - MCNF object is

MANUAL_CONFIRM_F
15 Manually confirmed status is active (1 is active, INTEGER 4 0 0 yes
LAG 0 is inactive)
16 OBJ_ID PK JEST-OBJNR - Object number NVARCSTR 22 0 0 no

Appendix
OBJ_NUM_TYPE_DES
CR

characters
OPERATN_ROUTING_ JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR

19 10 0 0 yes
ID number of operations in the order
JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR

20 OPERATN_SEQ_ID 8 0 0 yes
number counter for order
JEST-STAT (lookup) -any other status is

21 OTHER_FLAG INTEGER 4 0 0 yes
active (1 is active, 0 is inactive)
JEST-STAT (lookup) - PCNF object is partially

PARTL_CONFIRM_FL
AG inactive)
JEST-STAT (lookup) -PRREL object is Partially
PARTL_RELEASE_FL
23 Released status is active (1 is active, 0 is INTEGER 4 0 0 yes
AG inactive)
24 PROJ_DESCR PROJ.POST1 - Project definition text NVARCSTR 40 0 0 yes
25 PROJ_ELEM_DESCR PRPS.POST1 - Project Element definition text NVARCSTR 40 0 0 yes
JEST.OBJRN - WBS for 'PR' object types or

derived from 'NV' type (network activity) then
lookup on PRPS.POSID - WBS element
External ID
JEST.OBJNR for 'PD' object type-Current
number of the appropriate project (or derived
27 PROJ_ID from Project Element 'PR' type) then lookup on NVARCSTR 24 0 0 yes
PROJ.PSPID - Project ID (external)
JEST-STAT (lookup) -TECO object is
TECHN_COMPLT_FLA
28 Technically Completed status is active (1 is INTEGER 4 0 0 yes
G active, 0 is inactive)
TTL_NUM_ACTIVE_ST JEST-STAT- total number of actvie statuses

ATUS set to 1 for the object

Appendix
OBJECT_TYPE
DD07T - Object Type reference dimension
Column Dtype Is

"object type" from different sources. This field
identifies the source of "object type"
Rapid Mart

4 OBJ_TYPE_DESCR Description of Object Type NVARCSTR 75 0 0 yes
5 OBJ_TYPE_ID PK Object Type domain value ID NVARCSTR 10 0 0 no

Appendix
ORDER_OPERATION
Order Operation including Sequences from AFVC
Column Dtype Is
1 ACTIVITY_ID AFVC.LARNT - Activity Type NVARCSTR 6 0 0 yes
AFVC.MAT_PRKST - Material planning in

2 AMT_COST_MTRL DECIMAL 48 11 2 yes
networks: primary costs
AFVC.PRKST - Total Costs in the activity -

3 AMT_COST_TTL DECIMAL 48 11 2 yes
Planned
4 AMT_PRICE AFVC.PREIS - Price DECIMAL 48 11 2 yes
BUS_AREA_FULL_NA AFVC.GSBER+TGSBT-GTEXT - Business

ME Area ID and Descritpion
6 BUS_AREA_ID AFVC.GSBER - Business Area NVARCSTR 4 0 0 yes
CMPNY_CODE_FULL_ T001K -BUKRS + T001. BUTXT - full Name of

NAME the company code or company
9 CMPNY_CODE_ID AFVC.BUKRS Company Code NVARCSTR 4 0 0 yes
AFVC-LEKNW - Indicator showing no

10 COMPLT_FLAG INTEGER 4 0 0 yes
remaining work expected if set to 1
AFVC.SELKZ - Selection indicator for costing

11 COSTNG_FLAG INTEGER 4 0 0 yes
line items
12 COST_ELEM_ID AFVC.SAKTO - Cost Element NVARCSTR 10 0 0 yes
CTRL_AREA_FULL_N TKA02.KOKRS +TKA01.BEZEI - Concatenated NVARCSTR

13 32 0 0 yes
AME ID and Name for controlling area name
14 CTRL_AREA_ID TKA02.KOKRS -Controling Area ID NVARCSTR 4 0 0 yes
15 CTRL_KEY_DESCR T430T. TXT -Control Key description NVARCSTR 40 0 0 yes
16 CTRL_KEY_ID AFVC.STEUS - Control key NVARCSTR 4 0 0 yes

Appendix
17 CURR_ID AFVC.WAERS - Currency Key NVARCSTR 5 0 0 yes
18 FUNCTNL_AREA_ID AFVC.FUNC_AREA -Functional Area NVARCSTR 4 0 0 yes
AFVC.PLNFL - Sequence of operations within

19 GROUP_LINE_ID NVARCSTR 6 0 0 yes
a task list
20 GROUP_NODE_ID AFVC.PLNKN - Number of the task list node NVARCSTR 8 0 0 yes
AFKO.AUFNR - Internal Order Number -

Production
22 LOAD_DATE Date loaded into RapidMart DATETIME 24 0 9 yes
24 OBJ_CLASS_DESCR DD07T - domain SCOPE_CV lookup NVARCSTR 20 0 0 yes
25 OBJ_CLASS_ID AFVC.SCOPE - Object Class NVARCSTR 2 0 0 yes
26 OBJ_ID AFVC.OBJNR - Object number NVARCSTR 22 0 0 yes
OBJ_NUM_TYPE_DES
CR
28 OBJ_NUM_TYPE_ID AFVC.OBJNR Object number first 2 characters NVARCSTR 2 0 0 yes
29 OBJ_TYPE_DESCR T777O.OTEXT -Object Type Text NVARCSTR 60 0 0 yes
30 OBJ_TYPE_ID AFVC.OTYPE - Object type NVARCSTR 2 0 0 yes
31 OPERATN_DESCR AFVC.LTXA1 - Operation short text NVARCSTR 40 0 0 yes
32 OPERATN_NUM AFVC.VORNR - Operation Number NVARCSTR 4 0 0 yes
OPERATN_ROUTING_ PK AFVC.AUFPL - Routing number of operations

ID in the order
34 OPERATN_SEQ_ID PK AFVC.APLZL - General counter for order NVARCSTR 8 0 0 no

Appendix
STPO-PSWRK + T001W.NAME1 - Plant ID
35 PLANT_FULL_NAME NVARCSTR 40 0 0 yes
and Plant Name
36 PLANT_ID AFVC.WERKS - Plant NVARCSTR 4 0 0 yes
37 PRICE_UNIT AFVC.PEINH - Price Unit INTEGER 4 0 0 yes
38 PROFIT_CNTR_ID AFVC.PRCTR Profit Center NVARCSTR 10 0 0 yes
39 PROJ_DESCR PROJ.POST1 - Project Description NVARCSTR 40 0 0 yes
AFVC.PSPNR - Standard WBS element /

40 PROJ_ELEM_ID Lookup on PRPS.POSID - Project Element NVARCSTR 24 0 0 yes
(WBS) External ID
PRPS.PSPHI - Project ID / Lookup on

41 PROJ_ID NVARCSTR 24 0 0 yes
PROJ.PSPID - Project External ID
42 ROUTING_ID Concatenate PLNNR, PLNTY, PLNAL NVARCSTR 11 0 0 yes
43 ROUTING_SEQ_ID AFVC.ZAEHL Internal counter NVARCSTR 8 0 0 yes
44 SUITABILITY_DESCR T423T.TXT -Text for suitability NVARCSTR 30 0 0 yes
45 SUITABILITY_ID AFVC.QUALF Suitability NVARCSTR 2 0 0 yes
SYSTEM_CONDITN_D
46 T357M_T-ANLZUX - Operating status text NVARCSTR 40 0 0 yes
ESCR
SYSTEM_CONDITN_I
47 AFVC-ANLZU - System condition NVARCSTR 1 0 0 yes
D
48 WORK_CNTR_DESCR Lookup work center description in CRTX NVARCSTR 40 0 0 yes
49 WORK_CNTR_ID CRHD.ARBPL - Lookup of Workcenter ID NVARCSTR 8 0 0 yes

Appendix
PEGGING_OBJECT
Details of Pegging Objects from PEGOB, PEGQTY
Column Dtype Is
CMPNY_CODE_FULL_ PEGOB.BUKRS - Company Code + Company NVARCSTR

1 120 0 0 yes
NAME Code Name from T001
2 CMPNY_CODE_ID PEGOB.BUKRS - Company Code NVARCSTR 4 0 0 yes
CTRL_AREA_FULL_N Lookup on TKA02 PEGOB.KOKRS -

AME Controlling Area+name
4 CTRL_AREA_ID PEGOB.KOKRS - Controlling Area NVARCSTR 4 0 0 yes
5 CURR_ID PEGOB.WAERS - Currency Key NVARCSTR 5 0 0 yes
PEGOB.DELFG - Deletion indicator for peg

6 DELETE_FLAG INTEGER 4 0 0 yes
(1/0)
FIXED_ALLOCTN_FLA PEGQTY.FIXED - Indicator: Allocated quantity INTEGER

7 4 0 0 yes
G fixed (1/0)

Rapid Mart
10 MATERIAL_ID PEGOB.MATNR - Material Number NVARCSTR 18 0 0 yes
11 MTRL_DESCR MAKT.MAKTX Material description NVARCSTR 40 0 0 yes
12 OBJ_ID PK PEGOB.OBJNR - Object number NVARCSTR 22 0 0 no
PEGOB.ORGREQ - Object number of original

13 OBJ_ID_ORIGINAL NVARCSTR 22 0 0 yes
requirement (RESB-OBJNR)
PEGOB.REPOBJ - Object number of

14 OBJ_ID_REPLENISH NVARCSTR 22 0 0 yes
replenishment elem. used for static peggin
DD07T - PGASSCAT domain Lookup

15 PEG_CATEG_DESCR NVARCSTR 60 0 0 yes
description of Pegging Category
PEGQTY.ASSCAT - Pegging category of the

PEG_CATEG_FULL_N PK assigned quantity+DD07T - PGASSCAT
AME domain Lookup description of Pegging
Category

Appendix
PEGQTY.ASSCAT - Pegging category of the
17 PEG_CATEG_ID NVARCSTR 2 0 0 yes
assigned quantity
PEG_COMPLETE_FLA PEGOB.CLOSED - Indicator: Pegging

G completed (1/0)
19 PEG_DESCR PEGOB.KTEXT - Text Field NVARCSTR 40 0 0 yes
20 PEG_UNIQUE_FLAG PEGOB.PGUNI - Indicator: Unique peg (1/0) INTEGER 4 0 0 yes
PEGOB.WERKS - Plant ID+T001W.NAME1 -

21 PLANT_FULL_NAME NVARCSTR 120 0 0 yes
lookup on Plant Name
22 PLANT_ID PEGOB.WERKS - Plant NVARCSTR 4 0 0 yes
PROJ_ELEM_ID_COM
23 PEGOB.CMPPNR - Component WBS element NVARCSTR 24 0 0 yes
PONENT
PEGOB.GRPNR - Grouping WBS element. A

grouping WBS element is a WBS element that NVARCSTR
24 PROJ_ELEM_ID_GRP 24 0 0 yes
has valuated individual stock and has a special
function in materials requirements planni
PROJ_ELEM_NAME_C PRPS.POSKI - WBS element short

OMPONENT identification (lookup) -for Component project
PROJ_ELEM_NAME PRPS.POSKI - WBS element short

_GRP identification (lookup)
PEGQTY.QUANTY - Proportion assigned to

27 QTY_ASSIGN DECIMAL 48 15 5 yes
pegging object
PEGOB.TOTQTY - Total quantity of

28 QTY_TTL_REPLENISH DECIMAL 48 13 3 yes
replenishm. elem. used for static pegging
PEGOB.QTYNEEDED - Quantity necessary to DECIMAL

29 QTY_TTL_REQ 48 15 5 yes
satisfy the original requirement
QTY_TTL_RESERVAT PEGOB.REQQTY - Total required quantity of

N the reservation
31 UOM_ID PEGOB.MEINS - Base Unit of Measure NVARCSTR 3 0 0 yes
32 UOM_ID_ASSIGN PEGQTY.MEINS - Base Unit of Measure NVARCSTR 3 0 0 yes
PEGOB.REQUNIT - Base unit of the original

33 UOM_ID_RESERVATN NVARCSTR 3 0 0 yes
requirement

Appendix
PLANT
Contains Plant Level Information
Column Dtype Is
1 ADDRESS_ID Address ID NVARCSTR 10 0 0 yes
BATCH_STATUS_FLA
2 Batch Status Flag NVARCSTR 5 0 0 yes
G
3 CITY T001W.ORT01 CIty NVARCSTR 40 0 0 yes
4 CMPNY_CODE_ID Company code NVARCSTR 4 0 0 yes
5 CMPNY_CODE_NAME Company Code Name NVARCSTR 40 0 0 yes
6 COUNTRY_ID Country ID (Abbreviation) NVARCSTR 3 0 0 yes
7 COUNTRY_NAME Country Name (Full Name) NVARCSTR 15 0 0 yes
8 CTRL_AREA_ID Controlling area code NVARCSTR 4 0 0 yes
9 CTRL_AREA_NAME Control Area Name NVARCSTR 25 0 0 yes
10 DISTRICT District NVARCSTR 40 0 0 yes
11 FAX Fax Number NVARCSTR 40 0 0 yes
12 HOUSE_NUMBER House Number NVARCSTR 10 0 0 yes
Rapid Mart

15 PHONE Phone NVARCSTR 30 0 0 yes
16 PLANT_FULL_NAME ID and Name NVARCSTR 120 0 0 yes

Appendix
17 PLANT_ID PK T001W.WERKS Plant NVARCSTR 4 0 0 no
18 PLANT_NAME Plant name NVARCSTR 40 0 0 yes
19 PLANT_NAME_01 T001W.NAME1 Plant Name NVARCSTR 40 0 0 yes
20 PLANT_NAME_02 T001W.NAME2 Plant Name NVARCSTR 40 0 0 yes
21 PLANT_NAME_03 Plant name 3 NVARCSTR 40 0 0 yes
22 PLANT_NAME_04 Plant name 3 NVARCSTR 40 0 0 yes
23 PURCH_ORG_ID T001W.EKORG Purchasing Organization NVARCSTR 4 0 0 yes
T001W.CHAZV Batch Management Status

24 PURCH_ORG_NAME NVARCSTR 20 0 0 yes
Indicator
25 REGION_ID Region ID (Abbreviation of US State NVARCSTR 3 0 0 yes
26 REGION_NAME Region Name (Full Name of US State NVARCSTR 20 0 0 yes
27 SALES_ORG_ID T001W.VKORG Sales Organization NVARCSTR 4 0 0 yes
28 SALES_ORG_NAME Sales Organization name NVARCSTR 25 0 0 yes
29 STREET Street name NVARCSTR 60 0 0 yes
30 VALUATN_AREA_ID T001.BWKEY Valuation Area Key NVARCSTR 4 0 0 yes
31 ZIP Postal Code NVARCSTR 10 0 0 yes

Appendix
PLANT_LOCATION
Plant Location attributes from T499S
Column Dtype Is
1 ADDRESS_ID Address NVARCSTR 10 0 0 yes
2 CITY City NVARCSTR 40 0 0 yes
4 CMPNY_CODE_NAME Lookup on Company Code Name NVARCSTR 25 0 0 yes
5 COUNTRY_ID Country Key NVARCSTR 3 0 0 yes
6 COUNTRY_NAME Country name NVARCSTR 15 0 0 yes
7 DATE_TO Valid-to date DATETIME 24 0 9 yes
9 FAX First fax no.: dialling code+number NVARCSTR 30 0 0 yes
10 HOUSE_NUMBER House Number NVARCSTR 10 0 0 yes
T499S.STAND -Location ID + T499S.KTEXT

13 LOCATN_FULL_NAME NVARCSTR 55 0 0 yes
-Text (40 characters)
14 LOCATN_ID PK T499S.STAND -Location NVARCSTR 10 0 0 no
15 LOCATN_NAME T499S.KTEXT -Text (40 characters) NVARCSTR 40 0 0 yes
16 PHONE First telephone no.: dialling code+number NVARCSTR 30 0 0 yes

Appendix
17 PLANT_FULL_NAME ID and Name NVARCSTR 120 0 0 yes
18 PLANT_ID PK T499S.WERKS -Plant NVARCSTR 4 0 0 no
20 PLANT_NAME_01 Name 1 NVARCSTR 40 0 0 yes
24 REGION_ID Region (State, Province, County) NVARCSTR 3 0 0 yes
25 REGION_NAME Description NVARCSTR 20 0 0 yes
26 STREET Street NVARCSTR 60 0 0 yes
27 VALUATN_AREA_ID T001W.BWKEY -Valuation area NVARCSTR 4 0 0 yes
28 ZIP City postal code NVARCSTR 10 0 0 yes

Appendix
PRODUCT_HIERARCHY
T179 - Product Hierarchy dimension
Column Dtype Is
Rapid Mart

3 LVL_01_DESCR Level 1 description NVARCSTR 40 0 0 yes
4 LVL_02_DESCR Level 2 description NVARCSTR 40 0 0 yes
5 LVL_03_DESCR Level 3 descritpion NVARCSTR 40 0 0 yes
6 PROD_DESCR Current Node description NVARCSTR 40 0 0 yes
7 PROD_HIER_ID PK Product Hierarchy Current Node ID NVARCSTR 18 0 0 no
8 PROD_LVL Node Level depth NVARCSTR 1 0 0 yes

Appendix
PRODUCTION_ORDER_FACT
Production orders from AUFK/AFKO/AFPO (at AFPO order line level detail)
Column Dtype Is
ACCT_ASSIGN_CATE
1 AFPO.KNTTP - Account assignment category NVARCSTR 1 0 0 no
G_ID
ACTL_CONFRM_EN
2 AFKO.GLTRI - Actual finish confimred date DATETIME 24 0 9 yes
D_DATE
ACTL_RELEASE_DAT AFKO-FTRMI - Actual release date (Last

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

4 ACTL_START_DATE DATETIME 24 0 9 yes
Operation is Started)
5 BASIC_END_DATE AFKO-GLTRP - Finish (basic) date DATETIME 24 0 9 yes
6 BASIC_START_DATE AFKO-GSTRP - Order (basic) start date DATETIME 24 0 9 yes
7 BATCH_ID AFPO.CHARG - Batch number NVARCSTR 10 0 0 no
JEST-STAT (lookup) - LKD order is locked

8 BLOCK_FLAG INTEGER 4 0 0 yes
9 BUS_AREA_ID AUFK.GSBER -Business Area NVARCSTR 4 0 0 no
10 CHANGE_DATE AUFK.AEDAT - Change date DATETIME 24 0 9 yes
11 CHART_OF_ACCT_ID T001.KTOPL - Chart of accounts (lookup) NVARCSTR 4 0 0 yes
12 CLOSE_FLAG Check table JEST for closed status INTEGER 4 0 0 yes
13 CMPNY_CODE_ID AUFK.BUKRS -Company Code NVARCSTR 4 0 0 no
14 CONFRM_END_DATE AFKO.GETRI - Confirmed order finish date DATETIME 24 0 9 yes
15 COST_CNTR_ID AUFK.KOSTV -Responsible cost center NVARCSTR 10 0 0 no
16 COST_ELEM_ID AUFK.KSTAR -Settlement cost element NVARCSTR 10 0 0 yes

Appendix
17 CREATE_DATE AUFK.ERDAT - Date created DATETIME 24 0 9 no
18 CREATE_FLAG Check table JEST for created status INTEGER 4 0 0 yes
19 CTRL_AREA_ID AUFK-KOKRS - Controlling area NVARCSTR 4 0 0 no
20 CURR_ID AUFK.WAERS -Order Currency NVARCSTR 5 0 0 no
Number of Days to actually complete a service DECIMAL

21 DAYS_COMPLT_ACTL 48 22 7 yes
order (calcualted)
DAYS_COMPLT_BASI Number of Days to Basic complete a service

C order (calcualted)
Number of Forecast Days to complete a

23 DAYS_COMPLT_FCST DECIMAL 48 22 7 yes
service order (calcualted)
DAYS_COMPLT_SC Number of Days scheduled to complete a

HED service order (calcualted)
AFPO.WEBAZ -Goods receipt processing time INTEGER

25 DAYS_GR_PROCESS 4 0 0 yes
in days
DAYS_RELEASE_ACT Number of Days to actually release a service

L order (calcualted)
DAYS_RELEASE_SCH Number of Days scheduled to release a service DECIMAL

27 48 22 7 yes
ED order (calcualted)
JEST-STAT (lookup) - DLFL order is deleted

29 DELIV_FLAG Check table JEST for delilvered status INTEGER 4 0 0 yes

DIM_SRC_ID_DOCTY
30 AW_DIMENSION_SOURCE; hard-coded to NVARCSTR 10 0 0 no
P 'INT_ORDER'
AUFK.AUTYP - Document Category from

31 DOC_CATEG_ID NVARCSTR 10 0 0 no
multiple Sources in SAP
32 DOC_TYPE_ID AUFK.AUART Order type NVARCSTR 10 0 0 no
33 FCST_END_DATE AFKO.GLTPP - Finish date (forecast) DATETIME 24 0 9 yes
FCST_SCHED_END_D
34 AFKO.GLTPS - Scheduled forecast finish DATETIME 24 0 9 yes
ATE

Appendix
FCST_SCHED_START
35 AFKO.GSTPS - Scheduled forecast start DATETIME 24 0 9 yes
_DATE
36 FCST_START_DATE AFKO.GSTPP - Forecast start date DATETIME 24 0 9 yes
JEST-STAT (lookup) - CNF order is finally

FINAL_CONFIRM_FLA
G inactive)
38 FUNCTNL_AREA_ID AUFK.FUNC_AREA -Functional Area NVARCSTR 16 0 0 no
AUFK.SAKNR -G/L account for basic

39 GL_ACCT_ID NVARCSTR 10 0 0 no
settlement
40 GROUP_APPLICTN_ID AFKO.PLNAW -Application of the task list NVARCSTR 1 0 0 yes
41 GROUP_ID AFKO.PLNNR -Key for Task List Group NVARCSTR 8 0 0 yes
42 GROUP_TYPE_ID AFKO.PLNTY -Task List Type NVARCSTR 1 0 0 no
43 GROUP_USG_ID AFKO.PVERW -Task list usage NVARCSTR 3 0 0 no
HOURS_COMPLT_A Number of Hours to actually complete a service DECIMAL

44 48 22 7 yes
CTL order (calcualted)
HOURS_COMPLT_B Number of Hours to Basic complete a service

ASIC order (calcualted)
HOURS_COMPLT_F Number of Forecast Hours to complete a

CST service order (calcualted)
HOURS_COMPLT_S Number of Hours scheduled to complete a

CHED service order (calcualted)
48 INTERNAL_ORDER_ID PK AFPO.AUFNR - Order Number NVARCSTR 12 0 0 no
INTERNAL_ORDER_ID AFKO.NTZUE - Superior network number

_NETWRK_PAR (Internal Order Number)
INTERNAL_ORDER_ID
50 AFKO-MAUFNR - Superior order number NVARCSTR 12 0 0 yes
_PAR

RapidMart

Appendix
53 LOCATN_ID AUFK.STORT - Location of work center NVARCSTR 10 0 0 no
54 MATERIAL_ID AFPO.MATNR - Material number for order NVARCSTR 18 0 0 no
Number of Minutes to actually complete a

55 MINS_COMPLT_ACTL DECIMAL 48 22 7 yes
MINS_COMPLT_BASI Number of Minutes to Basic complete a service DECIMAL

56 48 22 7 yes
C order (calcualted)
Number of Forecast Minutes to complete a

57 MINS_COMPLT_FCST DECIMAL 48 22 7 yes
MINS_COMPLT_SCHE Number of Minutes scheduled to complete a

D service order (calcualted)
59 MRP_CTRLLER_ID AFKO.DISPO - MRP controller for the order NVARCSTR 3 0 0 no
60 MTRL_GRP_ID MARA.MATKL Material group NVARCSTR 9 0 0 no
61 MTRL_TYPE_ID MARA.MTART Material type NVARCSTR 4 0 0 no
NETWORK_PROFILE_
62 AFKO.PROFID - Network Profile NVARCSTR 7 0 0 no
ID
63 OBJ_CLASS_ID AUFK.SCOPE - Object class NVARCSTR 10 0 0 no
64 OBJ_ID AUFK-OBJNR - Object number NVARCSTR 22 0 0 yes
65 OBJ_NUM_TYPE_ID AUFK.OBJNR Object number first 2 characters NVARCSTR 2 0 0 yes
66 OPERATN_NUM_PAR AFKO.VORUE - Superior activity NVARCSTR 4 0 0 yes
OPERATN_ROUTING_ AFKO-AUFPL - Routing number for operations NVARCSTR

67 10 0 0 yes
ID in the order
ORDER_LINE_ITEM_I PK
68 AFPO.POSNR - Order item number NVARCSTR 4 0 0 no
D
69 ORDER_STATUS_ID AUFK.ASTNR - Order status NVARCSTR 2 0 0 no
JEST-STAT (lookup) - PCNF order is partially

PARTL_CONFIRM_FL
AG inactive)

Appendix
71 PERSON_ID_RESP IHPA-PERNR - Person responsible NVARCSTR 8 0 0 no
72 PLANNED_ORDER_ID AFPO.PLNUM -Planned order number NVARCSTR 10 0 0 yes
73 PLANT_ID AUFK.WERKS - Plant NVARCSTR 4 0 0 no
AFKO.APRIO - User specified order priority for NVARCSTR

74 PRIORITY_CODE 1 0 0 yes
information purposes
MARA.PRDHA - Product Hierarchy ID - Look

75 PROD_HIER_ID NVARCSTR 18 0 0 no
up based on AFIH.SERMAT
PROD_ORDER_DES
76 AUFK-KTEXT - Short text NVARCSTR 40 0 0 yes
CR
77 PROD_SCHEDLER_ID AFKO.FEVOR -Production scheduler NVARCSTR 3 0 0 yes
78 PROD_VERSION_ID AFPO.VERID - Production Version ID NVARCSTR 4 0 0 yes
79 PROFIT_CNTR_ID AUFK.PRCTR - Profit center NVARCSTR 10 0 0 no

80 PROJ_ELEM_ID NVARCSTR 24 0 0 no
External ID
81 PROJ_ID PROJ.PSPID - Project External ID NVARCSTR 24 0 0 no
82 PURCH_ORG_ID T001W.EKORG - Purchasing organization NVARCSTR 4 0 0 no
83 QTY AFPO.PSMNG - Order item quantity DECIMAL 48 13 3 yes
AFPO.WEMNG - Quantity of goods produced

84 QTY_PROD DECIMAL 48 13 3 yes
and received for the order item
85 QTY_SCRAP AFPO.PSAMG - Scrap quantity in item DECIMAL 48 13 3 yes
86 RELEASE_FLAG Check table JEST for released status INTEGER 4 0 0 yes
AFKO.RSNUM - Number of reservation/

87 RESERVATN_ID NVARCSTR 10 0 0 yes
dependent requirement
88 ROUTING_ID Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR 11 0 0 no

Appendix
89 SALES_DOC_ID AFPO.KDAUF - Sales order number NVARCSTR 10 0 0 yes
90 SALES_LINE_ITEM_ID AFPO .KDPOS - Sales order item NVARCSTR 6 0 0 yes
91 SCHED_END_DATE AFKO-GLTRS - Scheduled finish DATETIME 24 0 9 yes
SCHED_LINE_ITEM_I
92 AFPO.KDEIN - Delivery schedule (sales order) NVARCSTR 4 0 0 yes
D
SCHED_RELEASE_DA
93 AFKO-FTRMS - Scheduled release date DATETIME 24 0 9 yes
TE
94 SCHED_START_DATE AFKO-GSTRS - Scheduled start DATETIME 24 0 9 yes
SPECL_PROCUREM AFPO.PSOBS -Special procurement type;

NT_TYPE_ID Domain SOBES
STORAGE_LOCATN_I
96 AFPO.LGORT - Storage location NVARCSTR 4 0 0 yes
D

97 SURROGATE_DOC_ID DECIMAL 48 18 0 no
reporting purposes
TECHN_COMPLT_FLA
98 Check table JEST for completed status INTEGER 4 0 0 yes
G
99 UOM_ID AFPO.MEINS - Base unit of measure NVARCSTR 3 0 0 no
100 VALUATN_AREA_ID T001W.BWKEY Valuation area lookup NVARCSTR 4 0 0 no

Appendix
PROFIT_CENTER
CEPC - Profit Center attributes
Column Dtype Is
1 CITY City NVARCSTR 40 0 0 yes
2 COUNTRY_ID Country key NVARCSTR 3 0 0 yes
3 COUNTRY_NAME Lookup on Country name NVARCSTR 15 0 0 yes
4 CTRL_AREA_ID PK Controlling area NVARCSTR 4 0 0 no
5 CURR_ID Currency key NVARCSTR 5 0 0 yes
6 DEPARTMENT Department NVARCSTR 12 0 0 yes
8 FAX Fax number NVARCSTR 40 0 0 yes
9 LANG_ID Language Key NVARCSTR 1 0 0 yes
Rapid Mart

12 PERSON_IN_CHARGE Person in charge of profit center NVARCSTR 20 0 0 yes
13 PHONE First telephone number NVARCSTR 30 0 0 yes
14 PROFIT_CNTR_AREA Profit center area NVARCSTR 12 0 0 yes
PROFIT_CNTR_DESC
15 Name of Profit Center NVARCSTR 40 0 0 yes
R
PROFIT_CNTR_FULL_
16 Profit Center Name and ID NVARCSTR 120 0 0 yes
NAME

Appendix
17 PROFIT_CNTR_ID PK Profit center NVARCSTR 10 0 0 no
18 PROFIT_CNTR_NAME Profit Center Name NVARCSTR 20 0 0 yes
PROFIT_CNTR_NAME
19 Name 1 NVARCSTR 40 0 0 yes
_01
PROFIT_CNTR_NAME
_02
PROFIT_CNTR_NAME
_03
PROFIT_CNTR_NAME
_04
23 REGION_ID Abbreviation of Region (State) NVARCSTR 3 0 0 yes
24 REGION_NAME Name of Region (State) NVARCSTR 20 0 0 yes
25 SEGMENT_DESCR Segment Description NVARCSTR 50 0 0 yes
26 SEGMENT_ID Segment ID for Segmental Reporting NVARCSTR 10 0 0 yes
27 STREET House number and street NVARCSTR 60 0 0 yes
28 VALID_FROM_DATE Valid-from date DATETIME 24 0 9 yes
29 VALID_TO_DATE Valid to date DATETIME 24 0 9 yes
30 ZIP Postal Code NVARCSTR 10 0 0 yes

Appendix
PROFIT_CENTER_HIER
CCSS-RPRCTR - Profit Center Hierarchy- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Profit Center Child Node Description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Profit Center Child Node ID NVARCSTR 10 0 0 no
4 LEAF_FLAG PK Node Is Leaf NVARCSTR 1 0 0 no
Rapid Mart

7 PARENT_DESCR Profit Center Parent Node Descritpion NVARCSTR 64 0 0 yes
8 PARENT_ID PK Profit Center Parent Node ID NVARCSTR 10 0 0 no
9 ROOT_FLAG PK Node is Root NVARCSTR 1 0 0 no

Appendix
CCSS-RPRCTR - Profit Center Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Child Description NVARCSTR 64 0 0 yes
2 CHILD_ID PK Child NVARCSTR 10 0 0 no
3 CTRL_AREA_ID PK Control Area ID NVARCSTR 4 0 0 no
ETL_ERROR_COLU
MN
6 LEAF_FLAG PK Leaf Flag NVARCSTR 1 0 0 no
Rapid Mart

9 PARENT_DESCR Parent Description NVARCSTR 64 0 0 yes
10 PARENT_ID PK Parent ID NVARCSTR 10 0 0 no
11 ROOT_FLAG PK Root Flag NVARCSTR 1 0 0 no

Appendix
PROFIT_CENTER_HIER_HZ
CCSS-RPRCTR - Profit Center hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
2 LEAF_LVL Current Node level depth DECIMAL 48 10 0 no
Rapid Mart

5 LVL_00_DESCR Profit Center Root node Description NVARCSTR 64 0 0 yes
6 LVL_00_FULL_NAME Profit Center ID and Description for the root NVARCSTR 120 0 0 yes
7 LVL_00_ID PK Profit Center Root node ID NVARCSTR 10 0 0 no
8 LVL_01_DESCR Profit Center Level 1 node Description NVARCSTR 64 0 0 yes
9 LVL_01_FULL_NAME Profit Center ID and Description for Level 1 NVARCSTR 120 0 0 yes
10 LVL_01_ID PK Profit Center Level 1 node ID NVARCSTR 10 0 0 no
12 LVL_02_FULL_NAME Prifit Center ID and Descritption for Level 2 NVARCSTR 120 0 0 yes
15 LVL_03_FULL_NAME Profit Center Id and Description NVARCSTR 120 0 0 yes

Appendix
18 LVL_04_FULL_NAME Priofit Center ID and Description for Level 4 NVARCSTR 120 0 0 yes
21 LVL_05_FULL_NAME Profit Center Id and Descritpion for Level 5 NVARCSTR 120 0 0 yes
24 LVL_06_FULL_NAME Profit Center Id and Descripiton for Level 6 NVARCSTR 120 0 0 yes
27 LVL_07_FULL_NAME Profit Center Id and Descritpion for level 7 NVARCSTR 120 0 0 yes
30 LVL_08_FULL_NAME Profit Center Id and Descritpion for level 8 NVARCSTR 120 0 0 yes

Appendix
38 PROFIT_CNTR_ID PK Profit Center ID NVARCSTR 10 0 0 no
PROFIT_CENTER_HIER_VR
CCSS-RPRCTR Profit Center Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Dtype Is
1 CHILD_DESCR Child Node Descritpion for Profit Center NVARCSTR 64 0 0 yes
2 CHILD_FULL_NAME Profit Center (Child) ID and Descritpion NVARCSTR 120 0 0 yes
3 CHILD_ID PK Child Node ID for Profit Center NVARCSTR 10 0 0 no
4 CTRL_AREA_ID PK Controlling Center ID NVARCSTR 4 0 0 no
5 DEPTH Current Child Node Depth INTEGER 4 0 0 yes
6 LEAF_FLAG Current Node is Leaf INTEGER 4 0 0 yes
Rapid Mart

9 PARENT_DESCR Parent Node Descritpion for Profit Center NVARCSTR 64 0 0 yes
10 PARENT_FULL_NAME Profit Center (Parent) ID and Descritpion NVARCSTR 120 0 0 yes
11 PARENT_ID PK Parent Node ID for Profit Center NVARCSTR 10 0 0 no
12 ROOT_FLAG Current Node is Root INTEGER 4 0 0 yes

Appendix
PROGRESS_MEASURE_METHOD
Descriptive attributes for PS object progress measurement methods from EVOP
Column Dtype Is
COLLAPSE_FLAG_AC EVOP.EVZSF - Indicator: Collapse subtree for INTEGER

1 4 0 0 yes
TL Actuals only (1/0)
COLLAPSE_FLAG_PL EVOP.EVZSF - Indicator: Collapse subtree for INTEGER

2 4 0 0 yes
AN Budgeting only (Plan)
MEASURE_METHOD EVMTT. BEZ40 - PS Progress Measurementh

_DESCR_ACTL method description lookup for Actuals only
EVMTT. BEZ40 - PS Progress Measurementh

MEASURE_METHOD
6 method description lookup for Budgeting only NVARCSTR 40 0 0 yes
_DESCR_PLAN (Plan)
MEASURE_METHOD_I EVOP.EVMET - Measurement method in PS

D_ACTL progress analysis - for Actuals only
MEASURE_METHOD_I EVOP.EVMET - Measurement method in PS

D_PLAN progress analysis - for Budgeting only (Plan)
9 OBJ_ID PK EVOP.OBJNR - Object number NVARCSTR 22 0 0 no
EVOP.REFOB - Reference object for

10 OBJ_ID_REF_ACTL NVARCSTR 22 0 0 yes
secondary proportionality for Actuals only
EVOP.REFOB - Reference object for

11 OBJ_ID_REF_PLAN secondary proportionality for Budgeting only NVARCSTR 22 0 0 yes
(Plan)
PROGRESS_VERSI EVVST. TEXT - PS Progress Version

ON_DESCR description (default Controlling Area)
EVOP.VERSN_EV - Progress Version

PROGRESS_VERSI Code+EVOP.VERSN_EV - Progress Version
13 PK NVARCSTR 120 0 0 no
ON_FULL_NAME Code+EVVST. TEXT - PS Progress Version
description (default Controlling Area)
PROGRESS_VERSI
14 EVOP.VERSN_EV - Progress Version Code NVARCSTR 3 0 0 yes
ON_ID

Appendix
PROJECT
PROJ- Project Master dimension
Column Dtype Is
1 APPLICANT_ID Applicant number DECIMAL 48 28 0 yes
2 APPLICANT_NAME Applicant NVARCSTR 25 0 0 yes
3 CREATED_BY Name of Person who Created the Object NVARCSTR 12 0 0 yes
4 CREATE_DATE Date on which the record was created DATETIME 24 0 9 yes
5 DELETE_FLAG Deletion indicator NVARCSTR 1 0 0 yes
6 INACTIVE_FLAG Indicator: Project definition inactive NVARCSTR 1 0 0 yes
Rapid Mart

9 LOCATN_DESCR Location Description NVARCSTR 40 0 0 yes
10 LOCATN_ID Location NVARCSTR 10 0 0 yes
PLANNED_FINISH_DA
11 Project planned finish date DATETIME 24 0 9 yes
TE
PLANNED_START_DA
12 Project planned start date DATETIME 24 0 9 yes
TE
13 PROFILE_BDGT_ID Budget profile NVARCSTR 6 0 0 yes
PROFILE_DISTRIBTN_
14 Distribution Profitle Description NVARCSTR 40 0 0 yes
DESCR
PROFILE_DISTRIBTN_
15 Distribution profile NVARCSTR 6 0 0 yes
ID
PROFILE_INVESTMNT
16 Investment Profile Description NVARCSTR 50 0 0 yes
_DESCR

Appendix
PROFILE_INVESTMNT
17 Investment measure profile NVARCSTR 6 0 0 yes
_ID
PROFILE_NETWORK_
18 Network Profile Description NVARCSTR 40 0 0 yes
DESCR
PROFILE_NETWORK_
19 Network profile NVARCSTR 7 0 0 yes
ID
PROFILE_PAYMNT_P
20 Payment plan profile NVARCSTR 6 0 0 yes
LAN_ID
21 PROFILE_PLANNG_ID Planning profile NVARCSTR 6 0 0 yes
PROFILE_PROJ_DES
22 Project Profile Description NVARCSTR 40 0 0 yes
CR
23 PROFILE_PROJ_ID Project profile NVARCSTR 7 0 0 yes
PROFILE_SIMULTN_D
24 Simulation Profile Description NVARCSTR 40 0 0 yes
ESCR
PROFILE_SIMULTN_I
25 Simulation profile NVARCSTR 7 0 0 yes
D
26 PROJ_CODE PROJ.PSPNR - Project ID (internal) DECIMAL 48 28 0 yes
27 PROJ_DESCR PS: Short description (1st text line) NVARCSTR 40 0 0 yes
28 PROJ_FULL_NAME Project ID and Project Description NVARCSTR 100 0 0 yes
29 PROJ_ID PK PROJ.PSPID - Project ID (external) NVARCSTR 24 0 0 no
Number of the responsible person (project

30 RESP_PERSON_ID DECIMAL 48 28 0 yes
manager)
RESP_PERSON_NA
31 Name of responsible person (Project manager) NVARCSTR 25 0 0 yes
ME
32 UOM_DESCR Unit of Measure Description NVARCSTR 30 0 0 yes
33 UOM_ID Time unit in time scheduling NVARCSTR 3 0 0 yes

Appendix
PROJECT_COST_SUMMARY_FACT_HZ
Extracts data from the table RPSCO (cost and revenue summary for Projects) in horizontal period activity representation
Column Dtype Is
RPSCO.WLP00 - PTD Credit value in Ledger DECIMAL

1 AMT_CR_PER00_LOC 48 15 2 yes
RPSCO.WTP00 - PTD Credit value in

2 AMT_CR_PER00_TRX transactional currency (Adjusting year begin DECIMAL 48 15 2 yes
period)


4 AMT_CR_PER01_TRX DECIMAL 48 15 2 yes
RPSCO.WLP02 - PTD Credit value in Ledger

5 AMT_CR_PER02_LOC DECIMAL 48 15 2 yes












Appendix
RPSCO.WLP08 - PTD Credit value in Ledger
17 AMT_CR_PER08_LOC DECIMAL 48 15 2 yes


















Appendix
RPSCO.WLP00 through 03 - Quarter Credit
35 AMT_CR_QTR01_LOC DECIMAL 48 15 2 yes
RPSCO.WTP00 through 03 - Quarter Credit

36 AMT_CR_QTR01_TRX DECIMAL 48 15 2 yes







43 AMT_CR_YTD_LOC DECIMAL 48 15 2 yes

44 AMT_CR_YTD_TRX DECIMAL 48 15 2 yes
RPSCO.WLP00 - PTD Debit value in Ledger

45 AMT_DR_PER00_LOC DECIMAL 48 15 2 yes
RPSCO.WTP00 - PTD Debit value in

46 AMT_DR_PER00_TRX transactional currency (Adjusting Year begin DECIMAL 48 15 2 yes
period)


48 AMT_DR_PER01_TRX DECIMAL 48 15 2 yes





Appendix


















Appendix







RPSCO.WLP00 through 03 - Quarter Debit

79 AMT_DR_QTR01_LOC DECIMAL 48 15 2 yes
RPSCO.WTP00 through 03 - Quarter Debit

80 AMT_DR_QTR01_TRX DECIMAL 48 15 2 yes







87 AMT_DR_YTD_LOC DECIMAL 48 15 2 yes

88 AMT_DR_YTD_TRX DECIMAL 48 15 2 yes

Appendix
89 BUDGET_LEDGER_ID PK RPSCO.LEDNR - Budget/Planning Ledger NVARCSTR 4 0 0 no
RPSCO.VORGA - Budget Type Budgeting /

90 BUS_ACTIVITY_ID PK NVARCSTR 4 0 0 no
Planning
PRPS.PGSBR/AFVC.GSBER/PROJ.VBSBR
91 BUS_AREA_ID PK -Business area for WBS element/Proj/Network NVARCSTR 4 0 0 yes
PRPS.PBUKR/AFVC.BUKRS/PROJ.VBUKR -
92 CMPNY_CODE_ID PK NVARCSTR 4 0 0 yes
-Company code for WBS element
93 COST_OBJ_ID PK RPSCO.TRGLZ - Object indicator NVARCSTR 10 0 0 no
PRPS.PKOKR/PROJ.VKOKR -Controlling area NVARCSTR

94 CTRL_AREA_ID PK 4 0 0 no
for WBS element/Proj/Network
TBPOL.WAERS - Ledger Currency Key

95 CURR_ID_LOC PK NVARCSTR 5 0 0 yes
(lookup)
96 CURR_ID_TRX PK RPSCO.TWAER - Transaction Currency NVARCSTR 5 0 0 no

97 DIM_SRC_ID_RECTYP PK dimension combining similar attributes from NVARCSTR 10 0 0 yes
TPIF2.FIKRS - Financial (Fund) Management

98 FIN_MGMT_AREA_ID PK NVARCSTR 4 0 0 yes
Area ID (lookup)
99 FISC_YEAR PK RPSCO. GJAHR - Fiscal Year INTEGER 4 0 0 no
TBPOL.WAERS - Ledger Fiscal Year Variant

100 FISC_YR_VARIANT_ID NVARCSTR 2 0 0 yes
(lookup)
AFVC/PROJ/PRPS.FUNC_AREA -Functional
101 FUNCTNL_AREA_ID PK NVARCSTR 16 0 0 yes
Area ID
102 FUND_ID PK RPSCO.GEBER - Fund NVARCSTR 10 0 0 no
Date and Time This row was loaded into the

Rapid Mart
104 LOAD_TIME Time This row was loaded into the Rapid Mart NVARCSTR 8 0 0 yes
105 MAX_FISC_PERIOD PK RPSCO.PERBL - Period block INTEGER 4 0 0 no
106 OBJ_ID PK RPSCO-OBJNR - Object number NVARCSTR 22 0 0 no

Appendix
107 OBJ_NUM_TYPE_ID PK NVARCSTR 2 0 0 yes
characters
108 OPERATN_ROUTING_ AFVC.AUFPL -Routing number of operations in NVARCSTR

PK 10 0 0 yes
ID the order
109 OPERATN_SEQ_ID PK AFVC.APLZL -General counter for order NVARCSTR 8 0 0 yes
Duplicate of Fisc. Year column to allow for

110 PARTITION_YEAR PK Table partition on a field not in the Primary Key INTEGER 4 0 0 yes
111 PLANT_ID PK PRPS/PROJ/AFVC.WERKS -Plant NVARCSTR 4 0 0 yes
112 PROFIT_CNTR_ID PK PRPS/PROJ/AFVC.PRCTR -Profit Center NVARCSTR 10 0 0 yes
AFVC/PRPS.PROJN -Work breakdown

structure element (WBS element) / Lookup on
113 PROJ_ELEM_ID PK NVARCSTR 24 0 0 yes
External ID
114 PROJ_ID PK PROJ.PSPID - Project External ID NVARCSTR 24 0 0 yes

115 PURCH_ORG_ID PK NVARCSTR 4 0 0 yes
(lookup)
116 RECORD_CATEG_ID PK RPSCO.ACPOS - Value category NVARCSTR 14 0 0 no

118 SURROGATE_DOC_ID PK DECIMAL 48 18 0 yes
reporting purposes
119 VALUATN_AREA_ID PK T001W.BWKEY Valuation Area Key lookup NVARCSTR 4 0 0 yes
RPSCO..ABKAT - Category for

120 VARIANCE_CATEG_ID PK NVARCSTR 10 0 0 no
Variance/Results Analysis

Appendix
PROJECT_COST_SUMMARY_FACT_VR
Computes Rolling Totals for ProjectCost Summary Vertical Fact (Sourced from RPSCO)
Column Dtype Is
RPSCO-WLP01 through WLP16 - Period

1 AMT_CR_LOC DECIMAL 48 15 2 yes
for Per 12 - cumulative of Per 12 through P
RPSCO-WLP01 through WLP16 through 16 -

2 AMT_CR_QTD_LOC DECIMAL 48 15 2 yes
QTD Credit value in Ledger (Local) currency
RPSCO-WTP01 through WTP16 through 16 -

3 AMT_CR_QTD_TRX DECIMAL 48 15 2 yes
QTD Credit value in Transactional currency
RPSCO-WTP01 through WTP16 - Period

4 AMT_CR_TRX DECIMAL 48 15 2 yes
for Per 12 - cumulative of Per 12 through Pe
RPSCO-WLP01 through WLP16 - YTD Credit DECIMAL

5 AMT_CR_YTD_LOC 48 15 2 yes
RPSCO-WTP01 through WTP16 - YTD Credit DECIMAL

6 AMT_CR_YTD_TRX 48 15 2 yes

Debit value in Ledger (Local) currency. For
7 AMT_DR_LOC DECIMAL 48 15 2 yes
RPSCO-WLP01 through WLP16 - QTD Debit

8 AMT_DR_QTD_LOC DECIMAL 48 15 2 yes
RPSCO-WTP01 through WTP16 - QTD Debit

9 AMT_DR_QTD_TRX DECIMAL 48 15 2 yes
value in Transacitonal currency

10 AMT_DR_TRX DECIMAL 48 15 2 yes
RPSCO-WLP01 through WLP16 - YTD Debit
11 AMT_DR_YTD_LOC DECIMAL 48 15 2 yes
RPSCO-WTP01 through WTP16 - YTD Debit

12 AMT_DR_YTD_TRX DECIMAL 48 15 2 yes
AMT_PER_BEGIN_LO RPSCO-WLP01 through WLP16 - Period

13 begin balance value in Ledger (Local) currency DECIMAL 48 17 2 yes
C
AMT_PER_BEGIN_TR RPSCO-WTP01 through WTP16 - Period

X begin balance value in Transacitonal currency
AMT_PER_ROLLING_ Rolling Total Balance - Ledger (Local)

LOC Currency
AMT_PER_ROLLING_
16 Rolling Total Balance - Transaction Currency DECIMAL 48 17 2 yes
TRX

Appendix
Period Begining Balance - Ledger (Local)
17 AMT_PTD_LOC DECIMAL 48 17 2 yes
Currency
Period Begining Balance - Transaction

18 AMT_PTD_TRX DECIMAL 48 17 2 yes
Currency

Planning
21 BUS_AREA_ID PK -Business area for WBS element/Proj/Network NVARCSTR 4 0 0 yes
22 CMPNY_CODE_ID PK NVARCSTR 4 0 0 yes

24 CTRL_AREA_ID PK 4 0 0 yes

25 CURR_ID_LOC PK NVARCSTR 5 0 0 yes
(lookup)

27 DIM_SRC_ID_RECTYP PK dimension combining similar attributes from NVARCSTR 10 0 0 yes

28 FIN_MGMT_AREA_ID PK NVARCSTR 4 0 0 yes
Area ID (lookup)
29 FISC_PERIOD PK Pivot Generated Fiscal Period - 1-16 INTEGER 4 0 0 no
30 FISC_YEAR PK RPSCO.GJAHR - Fiscal Year INTEGER 4 0 0 no

31 FISC_YR_VARIANT_ID PK NVARCSTR 2 0 0 yes
(lookup)
32 FUNCTNL_AREA_ID PK NVARCSTR 16 0 0 yes
Area ID

Rapid Mart

Appendix
36 OBJ_ID PK RPSCO-OBJNR - Object number NVARCSTR 22 0 0 no

37 OBJ_NUM_TYPE_ID PK NVARCSTR 2 0 0 yes
characters
OPERATN_ROUTING_ PK AFVC.AUFPL -Routing number of operations in NVARCSTR

38 10 0 0 yes
ID the order
39 OPERATN_SEQ_ID PK AFVC.APLZL -General counter for order NVARCSTR 8 0 0 yes
For Partitioning only: RPSCO.GJAHR - Fiscal

40 PARTITION_YEAR PK INTEGER 4 0 0 yes
Year
41 PLANT_ID PK PRPS/PROJ/AFVC.WERKS -Plant NVARCSTR 4 0 0 yes
42 PROFIT_CNTR_ID PK PRPS/PROJ/AFVC.PRCTR -Profit Center NVARCSTR 10 0 0 yes

43 PROJ_ELEM_ID PK NVARCSTR 24 0 0 yes
External ID
44 PROJ_ID PK PROJ.PSPID - Project External ID NVARCSTR 24 0 0 yes

45 PURCH_ORG_ID PK NVARCSTR 4 0 0 yes
(lookup)
Concatenation ofr Primary Key for use in

48 SUMMARY_KEY NVARCSTR 150 0 0 yes
ordering query.

49 SURROGATE_DOC_ID PK DECIMAL 48 18 0 yes
reporting purposes
50 VALUATN_AREA_ID T001W.BWKEY Valuation Area Key lookup NVARCSTR 4 0 0 yes


Appendix
PROJECT_COST_SUMMARY_STAGE_VR
Vertical representation of Project Cost period activity. Staging is used for further Rolling Summary calculation
Column Dtype Is

1 AMT_CR_LOC DECIMAL 48 15 2 yes
RPSCO-WLP01 through 16 - QTD Credit

2 AMT_CR_QTD_LOC DECIMAL 48 15 2 yes
RPSCO-WTP01 through 16 - QTD Credit

3 AMT_CR_QTD_TRX DECIMAL 48 15 2 yes

4 AMT_CR_TRX DECIMAL 48 15 2 yes
RPSCO-WLP01 through WLP16 - YTD Credit DECIMAL

5 AMT_CR_YTD_LOC 48 15 2 yes
RPSCO-WTP01 through WTP16 - YTD Credit DECIMAL

6 AMT_CR_YTD_TRX 48 15 2 yes
value in Transcactional currency

Debit value in Ledger (Local) currency. For
7 AMT_DR_LOC DECIMAL 48 15 2 yes
RPSCO-WLP01 through 16 - QTD Debit value DECIMAL

8 AMT_DR_QTD_LOC 48 15 2 yes
in Ledger (Local) currency
RPSCO-WTP01 through 16 - QTD Debit value DECIMAL

9 AMT_DR_QTD_TRX 48 15 2 yes
in Transactioal currency

10 AMT_DR_TRX DECIMAL 48 15 2 yes
RPSCO-WLP01 through 16 - YTD Debit value DECIMAL
11 AMT_DR_YTD_LOC 48 15 2 yes
in Ledger (Local) currency
RPSCO-WTP01 through 16 - YTD Debit value DECIMAL

12 AMT_DR_YTD_TRX 48 15 2 yes
in Transactional currency
AMT_PER_BEGIN_LO RPSCO-WLP01 through 16 - Period begin

13 balance value in Transactional Ledger (Local) DECIMAL 48 17 2 yes
C
AMT_PER_BEGIN_TR RPSCO-WTP01 through 16 - Period begin

X balance value in Transactional currency

Planning

Appendix
17 BUS_AREA_ID -Business area for WBS element/Proj/Network NVARCSTR 4 0 0 yes
18 CMPNY_CODE_ID NVARCSTR 4 0 0 yes

20 CTRL_AREA_ID 4 0 0 yes

21 CURR_ID_LOC NVARCSTR 5 0 0 yes
(lookup)

23 FIN_MGMT_AREA_ID NVARCSTR 4 0 0 yes
Area ID (lookup)
24 FISC_PERIOD PK Pivot Generated Fiscal Period - 1-16 INTEGER 4 0 0 no
25 FISC_YEAR PK RPSCO. GJAHR - Fiscal Year INTEGER 4 0 0 no

26 FISC_YR_VARIANT_ID NVARCSTR 2 0 0 yes
(lookup)
27 FUNCTNL_AREA_ID NVARCSTR 16 0 0 yes
Area ID

Rapid Mart
31 OBJ_ID PK RPSCO. OBJNR - Object number NVARCSTR 22 0 0 no

characters
OPERATN_ROUTING_ AFVC.AUFPL -Routing number of operations in NVARCSTR

33 10 0 0 yes
ID the order
34 OPERATN_SEQ_ID AFVC.APLZL -General counter for order NVARCSTR 8 0 0 yes

Appendix
Duplicate of Fisc. Year column to allow for
35 PARTITION_YEAR PK Table partition on a field not in the Primary Key INTEGER 4 0 0 yes
36 PLANT_ID PRPS/PROJ/AFVC.WERKS -Plant NVARCSTR 4 0 0 yes
37 PROFIT_CNTR_ID PRPS/PROJ/AFVC.PRCTR -Profit Center NVARCSTR 10 0 0 yes

External ID

(lookup)
42 RECORD_TYPE_ID PK RPSCO. WRTTP - Value Type NVARCSTR 2 0 0 no

reporting purposes
44 VALUATN_AREA_ID T001W.BWKEY Valuation Area Key lookup NVARCSTR 4 0 0 yes


Appendix
PROJECT_ELEMENT
PRPS, PRTE - Project Element Master dimension
Column Dtype Is
1 ACTL_DURTN Actual length (duration) of the WBS element DECIMAL 48 5 1 yes
2 ACTL_FINISH_DATE Actual finish date of the WBS element DATETIME 24 0 9 yes
3 ACTL_START_DATE Actual start date for the WBS element DATETIME 24 0 9 yes
4 APPLICANT_ID Applicant number DECIMAL 48 28 0 yes
5 APPLICANT_NAME Applicant NVARCSTR 25 0 0 yes
Length (duration) of the basic dates in the WBS DECIMAL

6 BASIC_DURTN 48 5 1 yes
element
7 BASIC_FINISH_DATE WBS element: Basic finish date DATETIME 24 0 9 yes
BASIC_SCHED_EARL
8 Earliest scheduled finish date (basic) DATETIME 24 0 9 yes
ST_FINISH_DATE
BASIC_SCHED_EARL
9 Earliest scheduled start date (Basic) DATETIME 24 0 9 yes
ST_START_DATE
BASIC_SCHED_LATE
10 Latest scheduled finish date (basic) DATETIME 24 0 9 yes
ST_FINISH_DATE
BASIC_SCHED_LATE
11 Latest scheduled start date (basic) DATETIME 24 0 9 yes
ST_START_DATE
12 BASIC_START_DATE WBS element: Basic start date DATETIME 24 0 9 yes
13 CREATED_BY Name of Person who Created the Object NVARCSTR 12 0 0 yes
14 CREATE_DATE Date on which the record was created DATETIME 24 0 9 yes
15 DELETE_FLAG Deletion indicator NVARCSTR 1 0 0 yes
Forecasted length (duration) of the WBS

16 FCST_DURTN DECIMAL 48 5 1 yes
element

Appendix
17 FCST_FINISH_DATE Forecasted finish date of the WBS element DATETIME 24 0 9 yes
FCST_SCHED_EARLS
18 Earliest scheduled finish date (forecast) DATETIME 24 0 9 yes
T_FINISH_DATE
FCST_SCHED_LATES
19 Latest scheduled finish date (Forecast) DATETIME 24 0 9 yes
T_FINISH_DATE
FCST_SCHED_LATES
20 Latest scheduled start date (forecast) DATETIME 24 0 9 yes
T_START_DATE
FCST_SCHED_START
21 Scheduled start date (Forecast) DATETIME 24 0 9 yes
_DATE
22 FCST_START_DATE Forecasted start date of the WBS element DATETIME 24 0 9 yes
Rapid Mart

Indicator: WBS element used in project

25 MILESTONE_FLAG NVARCSTR 1 0 0 yes
summarization
26 PRIORITY_FLAG Priority NVARCSTR 1 0 0 yes
27 PROJ_ELEM_CODE PRPS.PSPNR - WBS element Internal ID DECIMAL 48 28 0 yes
PRPS.POST1 - WBS element (Project

28 PROJ_ELEM_DESCR NVARCSTR 40 0 0 yes
Element) Description
PROJ_ELEM_FULL_N PRPS.POSID and PRPS.POST1 Project

AME Element ID and Project Element Description
30 PROJ_ELEM_ID PK PRPS.POSID - WBS element External ID NVARCSTR 24 0 0 no
PROJ_ELEM_SHORT_
31 PRPS.POSKI - WBS element short External ID NVARCSTR 16 0 0 yes
ID
PROJ.PSPID - (Lookup on PROJ) Project ID

32 PROJ_ID NVARCSTR 24 0 0 yes
(external)
PROJ.POST1 - PS: Short description (1st text

33 PROJ_NAME NVARCSTR 40 0 0 yes
line) -- Lookup on PROJ
34 RESP_PERSON Name of responsible person (Project manager) NVARCSTR 25 0 0 yes

Appendix
Number of the responsible person (project
35 RESP_PERSON_ID DECIMAL 48 28 0 yes
manager)
36 TNTV_FINISH_DATE Tentative actual finish date for WBS element DATETIME 24 0 9 yes
37 TNTV_START_DATE Tentative actual start date for WBS element DATETIME 24 0 9 yes
UOM_ID_ACTL_DURT
38 Unit for duration of actual WBS element dates NVARCSTR 3 0 0 yes
N
UOM_ID_BASIC_DUR
39 Unit for duration of basic WBS element dates NVARCSTR 3 0 0 yes
TN
UOM_ID_FCST_DURT Unit for duration of WBS element planned

N dates
PROJECT_ELEMENT_HIER
PRHI - Project Element Hierarchy dimension
Column Dtype Is
PRPS.POSID - WBS element Internal ID -

1 CHILD_CODE INTEGER 4 0 0 no
Project Element Child Node ID
2 CHILD_DESCR Project Element Child Node Description NVARCSTR 100 0 0 yes
3 CHILD_FULL_NAME Project Element Child Node ID and Description NVARCSTR 100 0 0 yes
PRPS.POSID - WBS element External ID -

4 CHILD_ID PK NVARCSTR 24 0 0 no
Rapid Mart


7 PARENT_CODE INTEGER 4 0 0 no
Project Element Parent Node ID
8 PARENT_DESCR Project Element Parent Node Description NVARCSTR 100 0 0 yes
9 PARENT_FULL_NAME Project Element Parent Node ID Description NVARCSTR 100 0 0 yes

10 PARENT_ID PK NVARCSTR 24 0 0 no

Appendix
Rejected Project Element Hierarchy records
Column Dtype Is

1 CHILD_CODE INTEGER 4 0 0 no
2 CHILD_DESCR Project Element Child Node Description NVARCSTR 100 0 0 yes
3 CHILD_FULL_NAME Project Element Child Node ID and Description NVARCSTR 100 0 0 yes

ETL_ERROR_COLU
MN
Rapid Mart


9 PARENT_CODE INTEGER 4 0 0 yes
10 PARENT_DESCR Project Element Parent Node Description NVARCSTR 100 0 0 yes
Project Element Parent Node ID and

11 PARENT_FULL_NAME NVARCSTR 100 0 0 yes
Description


Appendix
PROJECT_ELEMENT_HIER_HZ
PRHI - Project element hierarchy flattenned horizontally
Column Dtype Is
1 LEAF_LVL Current Node level depth INTEGER 4 0 0 yes
Rapid Mart

4 LVL_00_DESCR Project Element Root Node Description NVARCSTR 100 0 0 yes
Project Element Root Level ID and Node

Description
6 LVL_00_ID PK Project Element Root Node ID NVARCSTR 24 0 0 no
7 LVL_01_DESCR Project Element Level 1 Node Description NVARCSTR 100 0 0 yes
Project Element Level 1 Level ID and Node

Description
9 LVL_01_ID PK Project Element Level 1 Node ID NVARCSTR 24 0 0 no

Description

Description

Appendix
Description

Description

Description

Description

Description

Description

Appendix
Description
37 PROJ_ELEM_ID PK Project Element Current Node ID NVARCSTR 24 0 0 no
PRHI - Project Element Hierarchy vertically flattenned
Column Dtype Is
1 CHILD_DESCR Parent Node desc NVARCSTR 100 0 0 yes
2 CHILD_FULL_NAME Parent Node ID and Desc NVARCSTR 100 0 0 yes
3 CHILD_ID PK Parent Node ID NVARCSTR 24 0 0 no
4 DEPTH Node depth level INTEGER 4 0 0 yes
5 LEAF_FLAG Is Leaf INTEGER 4 0 0 yes
Rapid Mart

8 PARENT_DESCR Child Node Desc NVARCSTR 100 0 0 yes
9 PARENT_FULL_NAME Child Node ID and Desc NVARCSTR 100 0 0 yes
10 PARENT_ID PK Child Node ID NVARCSTR 24 0 0 no
11 ROOT_FLAG Is Root INTEGER 4 0 0 yes

Appendix
PRT_ASSIGNMENT_FACT
Production resource (tool) assignment details from AFFH/CRFH/AFVC
Column Dtype Is
1 ACTIVITY_ID AFVC.LARNT - Activity Type NVARCSTR 6 0 0 yes
AFFH.IEFHD - Actual finish (date) of PRT

2 ACTL_END_DATE usage+AFFH.IEFHZ - Actual finish (time) of DATETIME 24 0 9 yes
PRT usage
AFFH.ISFHD - Actual start (date) of PRT

3 ACTL_START_DATE usage+AFFH.ISFHZ - Actual start (time) of DATETIME 24 0 9 yes
PRT usage
AFFH.EWIST - Actual usage value for

4 ACTL_USG_VALUE DECIMAL 48 9 3 yes
5 BUS_AREA_ID AFKO/AUFK.GSBER -Business Area NVARCSTR 4 0 0 yes
6 CHANGE_DATE AFFH.DATUC - Date of Last Change DATETIME 24 0 9 yes
8 CMPNY_CODE_ID AUFK/AFVC.BUKRS -Company Code NVARCSTR 4 0 0 yes
9 COST_CNTR_ID AUFK.KOSTL Cost center for basic settlement NVARCSTR 10 0 0 yes
10 COST_ELEM_ID AFVC.SAKTO - Cost Element NVARCSTR 10 0 0 yes
11 CREATE_DATE AFFH.DATUI - Date record created on DATETIME 24 0 9 yes
12 CTRL_AREA_ID AUFK.KOKRS -Controling Area ID NVARCSTR 4 0 0 yes
AFFH.BZOFFE - Reference date for end of

13 DATE_KEY_ID_END NVARCSTR 2 0 0 yes
production resource/tool usage
AFFH.BZOFFB - Reference date to start of

14 DATE_KEY_ID_START NVARCSTR 10 0 0 yes
Actual Number of Days for Network

Relationship. Calculated as difference between DECIMAL
15 DAYS_DURTN_ACTL 48 22 7 yes
actual end date and start date(UOM_ID = TAG
in IDES)
Number of Days for Network Relationship
DAYS_DURTN_EARLS
16 based on Eraliest start/end dates(UOM_ID = DECIMAL 48 22 7 yes
T TAG in IDES)

Appendix
Number of Days for Network Relationship
DAYS_DURTN_LATES
17 based on Latest start/end dates(UOM_ID = DECIMAL 48 22 7 yes
T TAG in IDES)
Max Number of Days for Network Relationship.
Calculated as difference between latest end
18 DAYS_DURTN_MAX date and earliest start date(UOM_ID = TAG in DECIMAL 48 22 7 yes
IDES)
Min Number of Days for Network Relationship.
Calculated as difference between earliest end DECIMAL
19 DAYS_DURTN_MIN 48 22 7 yes
date and latest start date(UOM_ID = TAG in
IDES)
20 DELETE_FLAG AFFH.LOEKZ - Deletion indicator (1/0) INTEGER 4 0 0 yes

21 DIM_SRC_ID_DTKEY NVARCSTR 10 0 0 yes
22 DIM_SRC_ID_OBJTYP NVARCSTR 10 0 0 yes
"object type" from different sources. This field
identifies the source of "object type"
FORMULA_ID_PRT_Q AFFH.MGFORM - Formula for calculating the
TY total quantity of PRT
FORMULA_ID_PRT_U AFFH.EWFORM - Formula for calculating the

SG total usage value of PRT
25 FUNCTNL_AREA_ID AFVC/AUFK.FUNC_AREA -Functional Area NVARCSTR 16 0 0 yes
GROUPNG_KEY_ID_0 CRFH.FGRU1 - Grouping key 1 for production NVARCSTR

26 4 0 0 yes
1 resources/tools
GROUPNG_KEY_ID_0 CRFH.FGRU2 -Grouping key 2 for production

2 resources/tools
28 GROUP_ID AFVC.PLNNR - Key for Task List Group NVARCSTR 8 0 0 yes
AFVC.PLNFL - Sequence of
29 GROUP_LINE_ID NVARCSTR 6 0 0 yes
operations/activities
30 GROUP_NODE_ID AFVC.PLNKN - Number of the task list node NVARCSTR 8 0 0 yes
31 GROUP_TYPE_ID AFFH.PLNTY_KEY - Task List Type NVARCSTR 1 0 0 yes
Actual Number of HOURS for Network

HOURS_DURTN_AC Relationship. Calculated as difference between DECIMAL
32 48 22 7 yes
TL actual end date and start date(UOM_ID = HUR
in IDES)
Number of Hours for Network Relationship
HOURS_DURTN_EA
RLST HUR in IDES)
Number of HOURS for Network Relationship

HOURS_DURTN_LA
TEST HUR in IDES)

Appendix
Max Number of Hours for Network
35 HOURS_DURTN_MAX 48 22 7 yes
latest end date and earliest start date(UOM_ID
= HUR in IDES)
Min Number of Hours for Network Relationship.
36 HOURS_DURTN_MIN 48 22 7 yes
date and latest start date(UOM_ID = HUR in
IDES)
37 INTERNAL_ORDER_ID AUFK-AUFNR NVARCSTR 12 0 0 yes
AFFH.PSNFH - Item number for production

resource/tool. Number that specifies the
38 ITEM_NUM sequence in which the production NVARCSTR 4 0 0 yes
resources/tools allocated to the operation or
activity a
AFFH.PZLFH_KEY - Item counter for
39 ITEM_SEQ_ID NVARCSTR 8 0 0 yes

Rapid Mart
42 LOCATN_ID AUFK.STORT Plant Location NVARCSTR 10 0 0 yes
43 MATERIAL_ID AFPO.MATNR Material Number for Order NVARCSTR 18 0 0 yes
Actual Number of Mins for Network

44 MINS_DURTN_ACTL 48 22 7 yes
actual end date and start date (UOM_ID = MIN
in IDES)
Number of Mins for Network Relationship
MINS_DURTN_EARLS
T MIN in IDES)
Number of Mins for Network Relationship

MINS_DURTN_LATES
T MIN in IDES)
Max Number of Mins for Network Relationship.
Calculated as difference between latest end
47 MINS_DURTN_MAX date and earliest start date(UOM_ID = MIN in DECIMAL 48 22 7 yes
IDES)
Min Number of Mins for Network Relationship.
48 MINS_DURTN_MIN 48 22 7 yes
date and latest start date(UOM_ID = MIN in
IDES)
49 MRP_CTRLLER_ID AFKO.DISPO MRP controller for the order NVARCSTR 3 0 0 yes
50 OBJ_ID AFFH-OBJNR - Object number NVARCSTR 22 0 0 yes
51 OBJ_NUM_TYPE_ID AFFH.OBJNR Object number first 2 characters NVARCSTR 2 0 0 yes
AFFH.OBJCT - Object of a task list (domain

52 OBJ_TYPE_ID NVARCSTR 10 0 0 yes
OBJKT)

Appendix
53 OPERATN_NUM AFVC.VORNR - Activity Number NVARCSTR 4 0 0 yes
OPERATN_ROUTING_ PK AFFH.AUFPL - Routing number of operations

ID in the order
55 OPERATN_SEQ_ID PK AFFH.APLZL - Internal counter NVARCSTR 8 0 0 no
AFVC/AUFK.WERKS -Plant lID of the

56 PLANT_ID NVARCSTR 4 0 0 yes
AFFH.EWSOL - Total planned usage value of

57 PLAN_USG_VALUE DECIMAL 48 9 3 yes
58 PROFIT_CNTR_ID AFVC/AUFK.PRCTR Profit Center NVARCSTR 10 0 0 yes
AFVC/AFPO.PROJN - Work breakdown

External ID
PRT_ASSIGNMNT_SE PK AFFH.PZLFH - Item counter for production

Q_ID resources/tools
AFFH.TXTZ1 - First line of text for production

62 PRT_ASSIGN_DESCR NVARCSTR 40 0 0 yes
resources/tools
CRFH.FHMAR -Production resources/tools

63 PRT_CATEG_ID NVARCSTR 1 0 0 yes
category
64 PRT_ID AFFH.OBJID - Object ID of the resource NVARCSTR 8 0 0 yes
CRVS_A./CRVS_B.SFHNR - Production
65 PRT_NAME NVARCSTR 18 0 0 yes
resources and tools Name (lookup)
TCF05.STATUS - Production resources/tools

66 PRT_STATUS_ID NVARCSTR 2 0 0 yes
master: Status

(lookup)
68 QTY_DURTN AFFH.DAUFL - Duration of PRT usage DECIMAL 48 22 7 yes
AFFH.OFFSTE - Offset to finish of production

69 QTY_OFFSET_END INTEGER 4 0 0 yes
resource/tool usage
AFFH.OFFSTB - Offset to start of production

70 QTY_OFFSET_START INTEGER 4 0 0 yes
resource/tool usage

Appendix
QTY_PRT_CHECKO AFFH.MGAUS - Quantity of checked-out
UT production resources/tools
AFFH.MGIST - Confirmed quantity of

72 QTY_PRT_CONFIRM DECIMAL 48 9 3 yes
AFFH.MGSOL - Total planned quantity of

73 QTY_PRT_PLAN DECIMAL 48 9 3 yes
AFFH.MGRSTEH - Remaining quantity of the

74 QTY_PRT_REMAIN DECIMAL 48 9 3 yes
AFFH.MGVGW - Standard value for the PRT

75 QTY_PRT_STD DECIMAL 48 9 3 yes
quantity
AFFH.EWRST - Remaining usage value of the DECIMAL

76 REMAIN_USG_VALUE 48 9 3 yes
RESOURCE_ID_WR
77 AFVC.ARBID -Object ID of the resource NVARCSTR 8 0 0 yes
KCNTR
78 ROUTING_ID Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR 11 0 0 yes
AFFH.FEFHD - Earliest scheduled finish (date)

SCHED_EARLST_END
79 of PRT usage+AFFH.FEFHZ - Earliest DATETIME 24 0 9 yes
_DATE scheduled end (time) of PRT usage
AFFH.FSFHD - Earliest scheduled start (date)

SCHED_EARLST_STA
80 for PRT usage+ AFFH.FSFHZ - Earliest DATETIME 24 0 9 yes
RT_DATE scheduled start (time) for PRT usage
AFFH.SEFHD - Latest scheduled finish (date)

SCHED_LATEST_END
81 of PRT usage+AFFH.SEFHZ - Latest DATETIME 24 0 9 yes
_DATE scheduled end (time) for PRT usage
AFFH.SSFHD - Latest scheduled start (date)

SCHED_LATEST_STA
82 for PRT usage+AFFH.SSFHZ - Latest DATETIME 24 0 9 yes
RT_DATE scheduled start (time) for PRT usage
AFFH.KTSCH - Standard text key for

83 STD_TEXT_KEY_ID NVARCSTR 7 0 0 yes
AFFH.EWVGW - Standard usage value for

84 STD_USG_VALUE DECIMAL 48 9 3 yes
STORAGE_LOCATN_I
85 AFPO.LGORT Storage location NVARCSTR 4 0 0 yes
D

reporting purposes
AFFH.EWISTEH - Usage value unit of the

87 UOM_ID_ACTL_USG NVARCSTR 3 0 0 yes
AFFH.DAUEH - Time unit for duration of PRT

88 UOM_ID_DURTN NVARCSTR 3 0 0 yes
usage

Appendix
AFFH.EHOFFE - Offset unit for end of
89 UOM_ID_END NVARCSTR 3 0 0 yes
AFFH.EWSOLEH - Usage value unit of the

90 UOM_ID_PLAN_USG NVARCSTR 3 0 0 yes
UOM_ID_PRT_CHECK AFFH.MGAUSEH - Quantity unit of production NVARCSTR

91 3 0 0 yes
OUT resource/tool
UOM_ID_PRT_CONFI AFFH.MGISTEH - Quantity unit of production

RM resource/tool
AFFH.MGSOLEH - Quantity unit of production

93 UOM_ID_PRT_PLAN NVARCSTR 3 0 0 yes
resource/tool
UOM_ID_PRT_REMAI AFFH.MGRSTEH - Quantity unit of production

N resource/tool
AFFH.MGEINH - Quantity unit of production

95 UOM_ID_PRT_STD NVARCSTR 3 0 0 yes
resource/tool
UOM_ID_REMAIN_US AFFH.EWRSTEH - Usage value unit of the

G production resource/tool
AFFH.EHOFFB - Offset unit for start of prod.

97 UOM_ID_START NVARCSTR 3 0 0 yes
resource/tool usage
AFFH.EWEINH - Usage value unit of the

98 UOM_ID_STD_USG NVARCSTR 3 0 0 yes
100 WORK_CNTR_CATE CRHD.VERWE - Work center category ID NVARCSTR 4 0 0 yes

G_ID lookup

SAP

Appendix
PRT_CATEGORY
Descriptive attributes from TCF03 of Production Resource/Tools categories
Column Dtype Is

Rapid Mart
TCF03.FHMAR_EXT -Production resource/tool NVARCSTR

3 PRT_CATEG_CODE 1 0 0 yes
category
TCF03.FAKTX -Language-dependent
4 PRT_CATEG_DESCR NVARCSTR 40 0 0 yes
description of the PRT category
TCF03.FHMAR -Production resources/tools

5 PRT_CATEG_ID PK NVARCSTR 1 0 0 no
category
PRT_GROUPING_KEY
Production Resource/Tools grouping key descriptive attributes from TCF13
Column Dtype Is
GROUPNG_KEY_DE TCF13.FGRTXT -Text for the production

SCR resources/tools group key
TCF13.FGRUA -Grouping key 1 for production NVARCSTR

2 GROUPNG_KEY_ID PK 4 0 0 no
resources/tools

Rapid Mart

Appendix
PRT_MASTER
Master records from CRFH with production resource/tools details. Current records only
Column Dtype Is
1 CHANGE_DATE CRFH.AEDAT -Date of Last Change DATETIME 24 0 9 yes
CMPNY_CODE_FULL_ Company Code ID + Company Code Name

NAME from T001
4 CREATE_DATE CRFH.ANDAT -Date record created on DATETIME 24 0 9 yes
CTRL_AREA_FULL_N Lookup on TKA01 for controlling area ID +

AME name
6 CTRL_AREA_ID Controling Area ID NVARCSTR 4 0 0 yes
7 CURRENT_FLAG Indicates that the record is current (1/0 values) INTEGER 4 0 0 yes
CRFH.LOEKZ =Deletion indicator for

8 DELETE_FLAG production resources/tools master (1/0 values) INTEGER 4 0 0 yes
FORMULA_DESCR_ TC25T-TXT - Lookup on Formula descritpion

TTL_QTY for Total Quantity

TTL_USG for Total usage
FORMULA_ID_TTL_Q CRFH.MGFORM -Formula for calculating the

TY total quantity of PRT
FORMULA_ID_TTL_U CRFH.EWFORM -Formula for calculating the

SG total usage value of PRT
GROUPNG_KEY_DE TCF13.FGRTXT - Text for the production

SCR_01 resources/tools group key (lookup)
GROUPNG_KEY_DE TCF13.FGRTXT - Text for the production

SCR_02 resources/tools group key (lookup)
GROUPNG_KEY_ID_0 CRFH.FGRU1 - Grouping key 1 for production NVARCSTR

15 4 0 0 yes
1 resources/tools
GROUPNG_KEY_ID_0 CRFH.FGRU2 -Grouping key 2 for production

2 resources/tools

Appendix
Rapid Mart
19 LOCATN_FULL_NAME Lookup onT499S for Plant Location ID +name NVARCSTR 120 0 0 yes
CRFH.STORT- Location of a production

20 LOCATN_ID NVARCSTR 10 0 0 yes
resource or tool
21 PARAMETER_ID_01 CRFH.PAR01 -First parameter (for formulas) NVARCSTR 6 0 0 yes
CRFH.PAR02 -Second parameter (for

22 PARAMETER_ID_02 NVARCSTR 6 0 0 yes
formulas)
23 PARAMETER_ID_03 CRFH.PAR03 -Third parameter (for formulas) NVARCSTR 6 0 0 yes
24 PARAMETER_ID_04 CRFH.PAR04 -Fourth parameter (for formulas) NVARCSTR 6 0 0 yes
25 PARAMETER_ID_05 CRFH.PAR05 -Fifth parameter (for formulas) NVARCSTR 6 0 0 yes
26 PARAMETER_ID_06 CRFH.PAR06 -Sixth parameter (for formulas) NVARCSTR 6 0 0 yes
PARAMETER_VALUE_
27 CRFH.PARV1 -Parameter value DECIMAL 48 9 3 yes
01
PARAMETER_VALUE_
02
PARAMETER_VALUE_
03
PARAMETER_VALUE_
04
PARAMETER_VALUE_
05
PARAMETER_VALUE_
06
33 PLANT_FULL_NAME T001W.NAME1 - lookup on Plant ID+ Name NVARCSTR 120 0 0 yes
CRFH.STOWK -Plant location of the

34 PLANT_ID NVARCSTR 4 0 0 yes

Appendix
35 PRT_CATEG_DESCR TCF03.FAKTX - PRT Category Description NVARCSTR 40 0 0 yes
CRFH.FHMAR -Production resources/tools

36 PRT_CATEG_ID NVARCSTR 1 0 0 yes
category
PRT_CTRL_KEY_DES TCF11.STFTXT - Control key description

CR (lookup) for PRT
CRFH.STEUF -Control key for management of NVARCSTR

38 PRT_CTRL_KEY_ID 4 0 0 yes
39 PRT_DESCR Lookup work center description in CRTX NVARCSTR 40 0 0 yes
40 PRT_ID PK CRFH.OBJID -Object ID of the resource NVARCSTR 8 0 0 no
CRVS_A./CRVS_B.SFHNR - Production
41 PRT_NAME NVARCSTR 18 0 0 yes
resources and tools Name (lookup)
42 PRT_STATUS_DESCR TCF05.KTEXT - PRT Status Description NVARCSTR 40 0 0 yes
CRFH.STATUS -Production resources/tools

43 PRT_STATUS_ID NVARCSTR 2 0 0 yes
master: Status
STD_TEXT_KEY_DES T435T.TXT - Description of the standard text

CR key (lookup)
CRFH.KTSCH -Standard text key for

45 STD_TEXT_KEY_ID NVARCSTR 7 0 0 yes
TASK_LIST_USG_DES TC23T.TXT - Description of the usage key

CR (lookup)
47 TASK_LIST_USG_ID CRFH.PLANV -Production resource/tool usage NVARCSTR 3 0 0 yes
48 UOM_ID_01 CRFH.PARU1 -Parameter unit NVARCSTR 3 0 0 yes

Appendix
CRFH.BASEH -Base unit of measure for

54 UOM_ID_BASE NVARCSTR 3 0 0 yes
55 VALID_FROM_DATE CRFH.DATUV -Valid-From Date DATETIME 24 0 9 yes
56 VALID_TO_DATE CRFH.DATUB -Valid-to date DATETIME 24 0 9 yes
PRT_STATUS
Descriptive attribututes for PRT status from TCF05
Column Dtype Is

Rapid Mart
3 PRT_STATUS_DESCR TCF05.KTEXT PRT master: Status description NVARCSTR 40 0 0 yes
TCF05.STATUS - Production resources/tools

4 PRT_STATUS_ID PK NVARCSTR 2 0 0 no
master: Status

Appendix
PURCH_ORGANIZATION
T024E - Purchasing Organization
Column Dtype Is
1 CMPNY_CODE_ID Company code NVARCSTR 4 0 0 yes
T001.BUTXT - Lookup on Company Code

2 CMPNY_CODE_NAME NVARCSTR 25 0 0 yes
Name
3 LOAD_DATE Data and Time Loaded into Rapid Mart DATETIME 24 0 9 yes
4 LOAD_TIME Time loaded into the Rapid Mart NVARCSTR 8 0 0 yes
5 PURCH_ORG_DESCR Description of purchasing organization NVARCSTR 20 0 0 yes
6 PURCH_ORG_ID PK Purchasing organization NVARCSTR 4 0 0 no
REFERENCE_DATE_KEY
Key determining the reference date for various entities - Milestone, PRT - Domain MLST_SDDAT; TCA55
Column Dtype Is
Short text describing ABAP/4 Dictionary

1 DATE_KEY_DESCR NVARCSTR 60 0 0 yes
objects; domain MLST_SDDAT
Values for domains: Single value/upper limit -

2 DATE_KEY_ID PK NVARCSTR 10 0 0 no
domain MLST_SDDAT


Appendix
RELATIONSHIP_TYPE
Network Relationship descriptive attributes from TCN2T
Column Dtype Is

RapidMart
RELATIONSHIP_TYPE TCN2T.AOBTX -Short text for the type of

_DESCR relationship
RELATIONSHIP_TYPE PK TCN2T.AOBKT - Short text for the relationship NVARCSTR

4 2 0 0 no
_ID type

Appendix
ROUTING
Routing Header information from PLKO
Column Dtype Is
1 ALT_BOM_ID PLKO.STLAL - Alternative BOM code NVARCSTR 2 0 0 yes
2 ASSEMBLY_ID PLKO.ISTRU - Assembly NVARCSTR 18 0 0 yes
3 BOM_CATEG_DESCR lookup on STLTY domain in DD07T NVARCSTR 60 0 0 yes
4 BOM_ID PLKO.STLNR - Bill of material NVARCSTR 8 0 0 yes
5 CHANGE_DATE PLKO.AEDAT Changed on DATETIME 24 0 9 yes
CMPNY_CODE_FULL_ T001K -BUKRS -Company Code ID+Lookup

NAME on Company Code Name
7 CMPNY_CODE_ID T001K -BUKRS -Company Code ID NVARCSTR 4 0 0 yes
8 CREATE_DATE PLKO.ANDAT Date record created on DATETIME 24 0 9 yes
PLKO.KOKRS - Controlling
CTRL_AREA_FULL_N
9 area+TKA01-BEZEI - Controlling area NVARCSTR 120 0 0 yes
AME description
10 CTRL_AREA_ID PLKO.KOKRS - Controlling area NVARCSTR 4 0 0 yes
PLKO.DELKZ - Indicator: Delete completely in

reorganization run (1/0)
12 GROUP_ID PLKO.PLNNR Group key NVARCSTR 8 0 0 yes
13 GROUP_SEQ_ID PLKO.PLNAL Group counter NVARCSTR 2 0 0 yes
GROUP_TYPE_DES
14 Lookup desription of task list type in TC A02 NVARCSTR 30 0 0 yes
CR
15 GROUP_TYPE_ID PLKO.PLNTY Task list type NVARCSTR 1 0 0 yes
16 GROUP_USG_DESCR T411T.TXT Lookup description of task usage NVARCSTR 20 0 0 yes

Appendix
17 GROUP_USG_ID PLKO.VERWE Task list usage NVARCSTR 3 0 0 yes
18 LAST_CALL_DATE PLKO.ABDAT- Date of the last call DATETIME 24 0 9 yes
19 LOAD_DATE Date and time when loaded into Rapid Mart DATETIME 24 0 9 yes
Time in a string format when the record was

21 LOT_SIZE_MAX PLKO.LOSBS- To lot size DECIMAL 48 13 3 yes
22 LOT_SIZE_MIN PLKO.LOSVN- From lot size DECIMAL 48 13 3 yes
23 NUM_CALLS PLKO.ABANZ- Number of calls INTEGER 4 0 0 yes
24 PLANT_FULL_NAME PLKO.WERKS Plant+T001W.NAME1 -Name NVARCSTR 120 0 0 yes
PLANT_FULL_NAME_ PLKO.IWERK - Planning plant+T001W.NAME1 NVARCSTR

25 120 0 0 yes
PLAN -Name of Planning Plant
26 PLANT_ID PLKO.WERKS Plant NVARCSTR 4 0 0 yes
27 PLANT_ID_PLAN PLKO.IWERK - Planning plant NVARCSTR 4 0 0 yes
PROCESS_TYPE_DES
28 lookup on C2_PRTYP domain in DD07T NVARCSTR 60 0 0 yes
CR
PROJ.POST1 - Project Short description (1st

29 PROJ_DESCR NVARCSTR 40 0 0 yes
text line)
PRPS.POST1 - Project Element Short

description (1st text line)

External ID
33 ROUTING_DESCR PLKO.KTEXT- Short description NVARCSTR 40 0 0 yes
34 ROUTING_ID PK Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR 11 0 0 no

Appendix
ROUTING_STATUS_D T412T.TXT - Routing status description -
ESCR lookup
36 ROUTING_STATUS_ID PLKO.STATU - Routing Status NVARCSTR 3 0 0 yes
SYSTEM_CONDITN_D T357M_T-ANLZUX - Operating status text -

ESCR lookup
SYSTEM_CONDITN_I
38 PLKO.ANLZU - System condition NVARCSTR 1 0 0 yes
D
PLKO.PLNME - Header unit of measure of

39 UOM_ID_BASE NVARCSTR 3 0 0 yes
base material
PLKO.DATUV - Valid-from date for routing

40 VALID_FROM_DATE DATETIME 24 0 9 yes
group assignment
41 VALID_TO_DATE Default Future Date DATETIME 24 0 9 yes
42 VALUATN_AREA_ID T001K.BWKEY -Valuation Area NVARCSTR 4 0 0 yes
Lookup on CRHD.ARBPL - Work Center

WORK_CNTR_FULL
43 Number+ Lookup work center description in NVARCSTR 120 0 0 yes
_NAME CRTX
Lookup on CRHD.ARBPL - Work Center

Number

Appendix
ROUTING_OPERATION
Routing master data from PLPO
Column Dtype Is
1 ACTIVITY_ID PLPO.LARNT -Activity Type NVARCSTR 6 0 0 yes
2 AMT_COST PLPO.PRKST Costs in the activity DECIMAL 48 11 2 yes
3 CALENDAR_DESCR TFACT.LTEXT - Factory Calendar descritpion NVARCSTR 60 0 0 yes
4 CALENDAR_ID PLPO.KALID - Factory calendar ID NVARCSTR 2 0 0 yes
CAPACITY_CATEG_D TC26T.TXT -Lookup capacity category

ESCR description
6 CAPACITY_CATEG_ID PLPO.KAPAR -Capacity category NVARCSTR 3 0 0 yes
7 CHANGE_DATE PLPO.AEDAT -Date of Last Change DATETIME 24 0 9 yes
CMPNY_CODE_FULL_ T001K -BUKRS -Company Code ID+Lookup

NAME on Company Code Name
9 CMPNY_CODE_ID T001K -BUKRS -Company Code ID NVARCSTR 4 0 0 yes
COSTNG_RELEVNT_F PLPO. CKSELKZ - Indicator for relevancy to

LAG costing
11 COST_CNTR_ID PLPO.ANFKO Requesting cost center NVARCSTR 10 0 0 yes
12 COST_ELEM_ID PLPO.SAKTO -Cost Element NVARCSTR 10 0 0 yes
13 CREATE_DATE PLPO.ANDAT Date record created on DATETIME 24 0 9 yes
PLKO.KOKRS - Controlling
CTRL_AREA_FULL_N
14 area+TKA01-BEZEI - Controlling area NVARCSTR 120 0 0 yes
AME description
15 CTRL_AREA_ID TKA02.KOKRS Controling Area ID NVARCSTR 4 0 0 yes
16 CTRL_KEY_ID PLPO.STEUS - Control key NVARCSTR 4 0 0 yes

Appendix
17 CURR_ID PLPO.WAERS -Currency Key NVARCSTR 5 0 0 yes
18 DELETE_FLAG PLPO.LOEKZ -Deletion Indicator INTEGER 4 0 0 yes
19 EMPL_COUNT PLPO.ANZMA -Number of employees DECIMAL 48 5 2 yes
20 GROUP_ID PK PLPO.PLNNR Group key NVARCSTR 8 0 0 no
21 GROUP_NODE_ID PK PLPO.PLNKN - Number of the task list node NVARCSTR 8 0 0 no
GROUP_TYPE_DES
22 TCA02.TXT - Lookup desription of task list type NVARCSTR 30 0 0 yes
CR
23 GROUP_TYPE_ID PK PLPO.PLNTY -Task List Type NVARCSTR 1 0 0 no
26 NUM_CAPACITY_REQ PLPO.ANZZL -Number of capacities required DECIMAL 48 28 0 yes
PLPO.LTXA1 - First line of operation

27 OPERATN_DESCR_01 NVARCSTR 80 0 0 yes
description
28 OPERATN_DESCR_02 PLPO.LTXA2 -Second line of the description NVARCSTR 40 0 0 yes
29 OPERATN_NUM PLPO.VORNR - Activity number NVARCSTR 4 0 0 yes
30 OPERATN_NUM_PAR Node number of the superior operation NVARCSTR 4 0 0 yes
31 PLANT_FULL_NAME PLKO.WERKS Plant+T001W.NAME1 -Name NVARCSTR 120 0 0 yes
32 PLANT_ID PLPO.WERKS - Operation plant NVARCSTR 4 0 0 yes
PROJ.POST1 - Project Short description (1st

33 PROJ_DESCR NVARCSTR 40 0 0 yes
text line)
PRPS.POST1 - Project Element Short

description (1st text line)

Appendix
External ID
PLPO.BMSCH - Quantity of the material to be

37 QTY_STD produced to which the standard values of the DECIMAL 48 13 3 yes
operation refer
38 STD_TEXT_KEY_ID PLPO.KTSCH - Standard text key NVARCSTR 7 0 0 yes
39 SUITABILITY_ID PLPO.QUALF -Suitability NVARCSTR 2 0 0 yes

reporting purposes
41 UOM_ID_STD PLPO.MEINH - Unit of measure for operation NVARCSTR 3 0 0 yes
42 VALID_FROM_DATE PLPO.DATUV -Valid-From Date DATETIME 24 0 9 yes
43 VALID_TO_DATE Ending effectivity date (calculated) DATETIME 24 0 9 yes
44 VALUATN_AREA_ID T001K.BWKEY -Valuation Area NVARCSTR 4 0 0 yes
T421T.TXT - Lookup desription of wage group

45 WAGE_GRP_DESCR NVARCSTR 30 0 0 yes
description
46 WAGE_GRP_ID PLPO.LOGRP -Wage group NVARCSTR 3 0 0 yes
47 WAGE_TYPE_CODE PLPO.LOART -Wage type NVARCSTR 4 0 0 yes
Lookup on CRHD.ARPBL - Visible Work

WORK_CNTR_FULL
48 Center ID in SAPLookup work center NVARCSTR 120 0 0 yes
_NAME description in CRTX
Lookup on CRHD.ARPBL - Visible Work

Center ID in SAP

Appendix
ROUTING_SEQUENCE
Routing (Task List) sequence definition from PLFL
Column Dtype Is
ALIGNMNT_KEY_DES TCA53.AUSCH_STXT - Lookup on short

CR desription of Allignment Key
2 ALIGNMNT_KEY_ID PLFL.AUSCHL -Alignment key for scheduling NVARCSTR 1 0 0 yes
3 CHANGE_DATE PLFL.AEDAT -Date of Last Change DATETIME 24 0 9 yes
4 CREATE_DATE PLFL.ANDAT -Date record created on DATETIME 24 0 9 yes
5 DELETE_FLAG PLFL.LOEKZ - Deletion Indicator INTEGER 4 0 0 yes
6 GROUP_ID PLKO.PLNNR Group key NVARCSTR 8 0 0 yes
GROUP_LINE_CATEG TCA08.FLG_STXT - Lookup on short

_DESCR desription of task list sequence category
GROUP_LINE_CATEG
8 PLFL.FLGAT - Sequence category NVARCSTR 1 0 0 yes
_ID
9 GROUP_LINE_DESCR PLFL.LTXA1 -Sequence description NVARCSTR 40 0 0 yes
PLFL.PLNFL - Sequence of
10 GROUP_LINE_ID PK NVARCSTR 6 0 0 no
operations/activities
11 GROUP_SEQ_ID PLPO.PLNAL Group counter NVARCSTR 2 0 0 yes
GROUP_TYPE_DES
12 TCA02.TXT - Lookup desription of task list type NVARCSTR 30 0 0 yes
CR
13 GROUP_TYPE_ID PLFL.PLNTY -Task List Type NVARCSTR 1 0 0 yes
Date and time the record was loaded into

Rapid Mart
16 LOT_SIZE_MAX PLFL.LOSBS -To lot size DECIMAL 48 13 3 yes

Appendix
17 LOT_SIZE_MIN PLFL.LOSVN -From lot size DECIMAL 48 13 3 yes
18 ROUTING_ID PK Concatenate PLNNR, PLNTY, PLNAL NVARCSTR 11 0 0 no

reporting purposes
20 VALID_FROM_DATE PLFL.DATUV -Valid-From Date DATETIME 24 0 9 yes
21 VALID_TO_DATE Calculated Ending effectivitiy date DATETIME 24 0 9 yes
SERVICE_PERSON
Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data
Column Dtype Is
1 FIRST_NAME PA0002-VORNA - First name NVARCSTR 40 0 0 yes
PA0002-NACHN - Last name +

2 FULL_NAME NVARCSTR 90 0 0 yes
PA0002-VORNA - First name
3 LAST_NAME PA0002-NACHN - Last name NVARCSTR 40 0 0 yes
6 PERSON_ID PK PA0002-PERNR - Personnel number NVARCSTR 8 0 0 no

Appendix
SPECIAL_PROCUREMENT_TYPE
Descriptive attributes from DD07T for domain SOBES
Column Dtype Is
SPECL_PROCUREM DD07T.DDTEXT - Special Procurement type

NT_TYPE_DESCR description
SPECL_PROCUREM DD07T.DOMVALUE_L - Special Procurement

4 PK NVARCSTR 1 0 0 no
NT_TYPE_ID type code
STANDARD_TEXT_KEY
Standard text Key descriptions for activities from T435T
Column Dtype Is
Load date and time when the record was

Time in string format when the record was

STD_TEXT_KEY_DES T435T.TXT - Description of the standard text

CR key
4 STD_TEXT_KEY_ID PK T435T.VLSCH - Standard text key NVARCSTR 7 0 0 no

Appendix
STATUS_PROFILE
Milestone Status profile descriptive attributes from TJ20T
Column Dtype Is
the target database
2 LOAD_TIME Time loaded into the target database NVARCSTR 8 0 0 yes
STATUS_PROFILE_D
3 TJ20T.TXT - Text (30 Characters) NVARCSTR 30 0 0 yes
ESCR
4 STATUS_PROFILE_ID PK TJ20T.STSMA - Status profile NVARCSTR 8 0 0 no

Appendix
STORAGE_LOCATION
T001L - Storage Locations in SAP
Column Dtype Is
T001K. BUKRS - Lookup for Company Code

1 CMPNY_CODE_ID NVARCSTR 4 0 0 yes
ID
3 CUSTOMER_ID T001L.KUNNR Account number of customer NVARCSTR 10 0 0 yes
4 CUSTOMER_NAME T001L.KUNNR Account number of customer NVARCSTR 35 0 0 yes
DISTRIBTN_CHANNEL
5 T001L.VTWEG Distribution channel NVARCSTR 20 0 0 yes
_DESCR
DISTRIBTN_CHANNEL
6 T001L.VTWEG Distribution channel NVARCSTR 2 0 0 yes
_ID
7 DIVISION_DESCR Lookip TSPAT.VTEXT-Division Description NVARCSTR 20 0 0 yes
8 DIVISION_ID T001L.SPART Division NVARCSTR 2 0 0 yes
GOODS_MVMT_AUT T001L.XBLGO Storage location authorization

HORIZTN_FLAG for goods movements active
HANDLNG_UNIT_FLA
10 T001L.XHUPF Handling unit requirement NVARCSTR 1 0 0 yes
G
11 LOAD_DATE Date and Time Loaded into Rapid Mart DATETIME 24 0 9 yes
Lookup T001L.DISKZ MRP Indicator

13 MRP_DESCR NVARCSTR 60 0 0 yes
Description
14 MRP_ID T001L.DISKZ Storage location MRP indicator NVARCSTR 1 0 0 yes
15 NEG_STOCK_FLAG Negative stocks allowed in storage location NVARCSTR 1 0 0 yes
16 PLANT_ID PK T001L.WERKS Plant NVARCSTR 4 0 0 no

Appendix
17 PLANT_NAME T001W.NAME1 - Plant Name NVARCSTR 30 0 0 yes
T001W.EKORG -Purchasing Organization

Code
19 PURCH_ORG_NAME Lookup on Purchasing org Name T024E NVARCSTR 20 0 0 yes
RESOURCE_ALLOC T001L.XRESS Storage location is allocated to

TN_FLAG resource (storage resource)
21 SALES_ORG_DESCR T001L.VKORG Sales organization NVARCSTR 20 0 0 yes
22 SALES_ORG_ID T001L.VKORG Sales organization NVARCSTR 4 0 0 yes
23 SHIP_POINT_DESCR T001L.VSTEL Shipping point/receiving point NVARCSTR 30 0 0 yes
24 SHIP_POINT_ID T001L.VSTEL Shipping point/receiving point NVARCSTR 4 0 0 yes
STORAGE_LOCATN
25 T001L.LGOBE Description of storage location NVARCSTR 16 0 0 yes
_DESCR
STORAGE_LOCATN_F Concatenation of Storage Location ID and

ULL_NAME Description
STORAGE_LOCATN_I PK
27 T001L.LGORT Storage location NVARCSTR 4 0 0 no
D
STORAGE_LOCATN_I T001L.PARLG Partner storage location of the

D_PARTNER handling unit
29 VALUATN_AREA_ID T001W.BWKEY - Valuation area Code NVARCSTR 4 0 0 yes
30 VENDOR_ID T001L.LIFNR Vendor account number NVARCSTR 10 0 0 yes
31 VENDOR_NAME T001L.LIFNR Vendor account number NVARCSTR 35 0 0 yes

Appendix
TASK_LIST_TYPE
Task List Type descriptive attributes from TCA02 - TASK_LIST_TYPE dimension
Column Dtype Is
GROUP_TYPE_DES
1 TCA02.TXT -Desccription of the task list type NVARCSTR 30 0 0 yes
CR
2 GROUP_TYPE_ID PK TCA02.PLNTY -Task List Type NVARCSTR 1 0 0 no
TASK_LIST_USAGE
Task List Usage descriptive attributes from TC23T (TASK_LIST_USAGE)
Column Dtype Is
1 GROUP_USG_DESCR TC23T.TXT - Description of the usage key NVARCSTR 30 0 0 yes
2 GROUP_USG_ID PK TC23T.PLANV - Key for task list usage NVARCSTR 3 0 0 no

Appendix
TIME_DIM
Time Dimension (Daily)
Column Dtype Is
1 CALENDAR_DATE PK Calendar Date DATETIME 24 0 9 no
2 CALENDAR_MONTH Number of Calendar Month INTEGER 4 0 0 yes
CALENDAR_QUART
3 Calendar Quarter INTEGER 4 0 0 yes
ER
4 CALENDAR_YEAR Calenar Year INTEGER 4 0 0 yes
5 DAY_IN_PERIOD Number of a day in a fiscal period INTEGER 4 0 0 yes
6 DAY_IN_WEEK Day of the week INTEGER 4 0 0 yes
Fiscal Period of Calendar Date. Retrieved from INTEGER

7 FISC_PERIOD 4 0 0 yes
SAP using FI_PERIOD_DETEMINE
Fiscal Year of Calendar Date. Retrieved from

8 FISC_YEAR INTEGER 4 0 0 yes
SAP using FI_PERIOD_DETEMINE
9 IS_WEEKEND Indicates if date falls on a weekend (1) NVARCSTR 1 0 0 yes
Rapid Mart

12 MONTH_YEAR Calendar Month and Year NVARCSTR 10 0 0 yes
13 WEEK_IN_YEAR Number of week in the year DECIMAL 48 28 0 yes

Appendix
TIME_DIM_WEEKLY
Time Dimension (WEEKLY). Used for summary facts (such as BENEFIT_ENROLL_SUMMARY_FACT)
Column Dtype Is
1 CALENDAR_YEAR PK Calenar Year INTEGER 4 0 0 no
Rapid Mart

4 WEEK_END_DATE Last date in the week DATETIME 24 0 9 yes
5 WEEK_IN_YEAR PK Number of week in the year DECIMAL 48 28 0 no
6 WEEK_NAME Week - Year concatenation NVARCSTR 60 0 0 yes
7 WEEK_START_DATE First date of the week DATETIME 24 0 9 yes
WEEK_START_FISC_
8 Fiscal Period when the week starts INTEGER 4 0 0 yes
PER
WEEK_START_FISC_
9 Fiscal Year when the week starts INTEGER 4 0 0 yes
YEAR
WEEK_START_MON Number of Calendar Month when the week

TH starts
WEEK_START_QUA
11 Calendar Quarter when the week starts INTEGER 4 0 0 yes
RTER

Appendix
UNIT_OF_MEASURE
T006A-Material Unit of Measure attritues
Column Dtype Is
Rapid Mart


3 UOM_CODE Language (External unit of measurement NVARCSTR 3 0 0 yes
T006A-MSEHT - Measurement unit text (max.

4 UOM_DESCR NVARCSTR 10 0 0 yes
10 char.)
5 UOM_ID PK T006A-MSEHI - Unit of measurement NVARCSTR 3 0 0 no
VALUATION_AREA
Describes level at which stocks are valuated together, generally a company, plant or group of plants.
Column Dtype Is
1 CITY T001.ORT01 City NVARCSTR 25 0 0 yes
2 CMPNY_CODE_ID T001.BUKRS Company Code NVARCSTR 4 0 0 yes
3 CMPNY_CODE_NAME T001.BUTXT Company Name NVARCSTR 25 0 0 yes
4 CURR_ID TCURC-WAERS - CURRENCY KEY NVARCSTR 5 0 0 yes
Rapid Mart

7 VALUATN_AREA_ID PK T001.BWKEY Valuation Area Key NVARCSTR 4 0 0 no

Appendix
VARIANCE_CATEGORY
Financial Variance Category descriptive attributes (ABKAT domain from DD07T)
Column Dtype Is
VARIANCE_CATEG_D DD07T-DDTEXT - Short text describing

ESCR ABAP/4 Dictionary objects (ABKAT)
DD07T-DOMVALUE_L - Values for domains:

Single value/upper limit(ABKAT)

Appendix
WORK_CENTER
Work center descriptions and standard capacity information from CRHD used as default by capacity planning processes
Column Dtype Is
1 BACKFLUSH_FLAG CRHD.RGEKZ - Indicator: Backflushing (1/0) INTEGER 4 0 0 yes
2 CHANGE_DATE AEDAT_GRND - Changed on DATETIME 24 0 9 yes
5 CTRL_KEY_DESCR T430T-TXT -Control Key desctiption (lookup) NVARCSTR 40 0 0 yes
6 CTRL_KEY_ID CRHD.STEUS - Control key NVARCSTR 4 0 0 yes
7 CURRENT_FLAG 1 indicates record is currently in effect (1/0) INTEGER 4 0 0 yes
CRHD.LVORM - Deletion flag for work center ( INTEGER

8 DELETE_FLAG 4 0 0 yes
1/0)

OTHER for Other

PROCESS for Process

SETUP for Setup

TEARDOWN for TearDown
CRHD.FORTN - Formula for other workcenter NVARCSTR

13 FORMULA_ID_OTHER 6 0 0 yes
times
FORMULA_ID_PROCE CRHD.FORT2 - Formula for work center

SS processing time duration
CRHD.FORT1 - Formula for work center setup NVARCSTR

15 FORMULA_ID_SETUP 6 0 0 yes
time
FORMULA_ID_TEARD CRHD.FORT3 - Formula for work center

OWN teardown time calculation

Appendix
Rapid Mart
LOCATN_GRP_DES TC28T-TXT - Location group desctiption

CR (lookup)
20 LOCATN_GRP_ID CRHD.ORTGR - Location group NVARCSTR 4 0 0 yes
MACHINE_TYPE_DES
21 Lookup machine type group description NVARCSTR 40 0 0 yes
CR
MACHINE_TYPE_GRP
22 CRHD.MATYP - Machine type grouping NVARCSTR 10 0 0 yes
_ID
MINS_MIN_QUEUE_TI CRHD.ZWMIN - Minimum queue time

ME converted to minutes
MINS_STD_QUEUE_TI CRHD.ZWNOR - Standard queue time

ME converted to minutes
25 OBJ_ID CRHD.HROID - Object ID NVARCSTR 8 0 0 yes
ORG_UNIT_TYPE_DE
26 T777O-OTEXT -Object Type Description NVARCSTR 25 0 0 yes
SCR
27 ORG_UNIT_TYPE_ID CRHD.HRTYP - Object type NVARCSTR 2 0 0 yes
PERSON_RESP_CO CRHD.VERAN - Person responsible for the

DE work center
PERSON_RESP_DE Lookup TC24.KTEXT - Person responsible for NVARCSTR

29 40 0 0 yes
SCR the work center VERAN
30 PLANT_ID PK CRHD.WERKS - Plant NVARCSTR 4 0 0 no
STD_TEXT_KEY_COD
32 CRHD.KTSCH - Standard text key NVARCSTR 7 0 0 yes
E
STD_VALUE_KEY_DE
33 Lookup standard value key description in TC21 NVARCSTR 30 0 0 yes
SCR
34 STD_VALUE_KEY_ID CRHD.VGWTS - Standard value key NVARCSTR 4 0 0 yes

Appendix
T423T-TXT - Sutability( Qualificiation/Wage
35 SUITABILITY_DESCR NVARCSTR 30 0 0 yes
Group) desctiption (lookup)
CRHD.QUALF - Suitability for carrying certain

36 SUITABILITY_ID NVARCSTR 2 0 0 yes
tasks
SUPPLY_AREA_DESC
37 PVKT-PVBTX -Supply Area Description NVARCSTR 40 0 0 yes
R
38 SUPPLY_AREA_ID CRHD.PRVBE Supply area NVARCSTR 10 0 0 yes
TASK_LIST_USG_DES
39 Lookup task list usage descripton NVARCSTR 30 0 0 yes
CR
40 TASK_LIST_USG_ID CRHD.PLANV - Key for task list usage NVARCSTR 3 0 0 yes
41 VALID_FROM_DATE CRHD.BEGDA - Effectivity Start date DATETIME 24 0 9 yes
42 VALID_TO_DATE CRHD.ENDDA - Effectivity end date DATETIME 24 0 9 yes
WORK_CNTR_CATE Lookup description of Work Center category in NVARCSTR

44 20 0 0 yes
G_DESCR TC30T
WORK_CNTR_CATE
45 CRHD.VERWE - Work center category NVARCSTR 4 0 0 yes
G_ID
46 WORK_CNTR_CODE CRHD.OBJID - Work center Internal Object ID NVARCSTR 8 0 0 yes
47 WORK_CNTR_DESCR Lookup work center description in CRTX NVARCSTR 40 0 0 yes
WORK_CNTR_FULL CRHD.ARBPL - Work center Code + Name

_NAME (Lookup work center description in CRTX

49 WORK_CNTR_ID PK NVARCSTR 8 0 0 no
SAP
WORK_CNTR_LOCA
50 T499S-KTEXT - Location desctiption (lookup) NVARCSTR 40 0 0 yes
TN_DESCR
WORK_CNTR_LOCA
51 CRHD.STAND - Work center location NVARCSTR 10 0 0 yes
TN_ID

Appendix
WORK_CENTER_CATEGORY
Work Center Category Attributes from TC30T
Column Dtype Is
WORK_CNTR_CATE TC30T.KTEXT - Description of the work center NVARCSTR

3 20 0 0 yes
G_DESCR category
WORK_CNTR_CATE
4 PK TC30T.VERWE - Work center cat. NVARCSTR 4 0 0 no
G_ID

Appendix
WORK_CENTER_FORMULA
Capacity formulas from TC25; parameters are parsed from the formula equation text
Column Dtype Is
CAPACITY_CALC_FLA TC25.VKAPA - Indicator: work center is

1 INTEGER 4 0 0 yes
G allowed for capacity requirements
COSTNG_ALLOW_F TC25.VKALK - Indicates it is allowed for

2 INTEGER 4 0 0 yes
LAG costing
TC25T.TXT - Lookup formula description in

3 FORMULA_DESCR NVARCSTR 20 0 0 yes
TC25T
FORMULA_EQUATN
4 TC25.FTEXT- Equation of formula NVARCSTR 70 0 0 yes
_TEXT
5 FORMULA_ID PK TC25.IDENT - Formula key NVARCSTR 6 0 0 no
Calculated from TC25.FTEXT - parsed

Parameter 01 ID or constant









Appendix
TC25.VKAPF- Indicator: PRT allowed for

18 PRT_CALC_FLAG INTEGER 4 0 0 yes
requirements
SCHED_ALLOW_FL TC25.VTERM- Indicator: Allowed for

AG scheduling

Appendix
WORK_CENTER_HIER
Work center parent-child relationship from CRHH/CRHS
Column Dtype Is
1 CHILD_CODE CRHD.ARBPL Work center Code - Child NVARCSTR 8 0 0 yes
Lookup work center description in CRTX for

Child WC
Concatentaion of WC code and description for

Child Node
CRHS.OBJID_HO - Object ID of the resource

and CRHH.NAME - Name of hierarchy
5 LOAD_DATE Load date and time into the target database DATETIME 24 0 9 yes
6 LOAD_TIME Load time into the target database NVARCSTR 8 0 0 yes
CRHH.VERAN - Person responsible for the

7 OWNER_ID NVARCSTR 3 0 0 yes
work center
Lookup TC24.KTEXT - Person responsible for

8 OWNER_NAME NVARCSTR 40 0 0 yes
the work center VERAN
9 PARENT_CODE CRHD.ARBPL - Work center - Parent node NVARCSTR 8 0 0 yes

Parent WC

Parent Node
CRHS.OBJID_UP - ID of superior object in the

12 PARENT_ID PK hierarchy and CRHH.NAME - Name of NVARCSTR 50 0 0 no
hierarchy
13 PLANT_ID CRHH.WERKS - Plant NVARCSTR 4 0 0 yes
WORK_CNTR_HIER_I PK
15 CRHH.OBJID - Object ID of the resource NVARCSTR 8 0 0 no
D
WORK_CNTR_HIER_N
16 CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 yes
AME

Appendix
Work center parent-child relationship from CRHH/CRHS - Invalid Records
Column Dtype Is
1 CHILD_CODE CRHD.ARBPL Work center Code - Child NVARCSTR 8 0 0 yes

Child WC

Child Node
CRHS.OBJID_HO - Object ID of the resource

and CRHH.NAME - Name of hierarchy
5 DI_ERROR_ACTN DI Error Action NVARCSTR 1 0 0 yes
6 DI_ERROR_COLUMN DI Error Columns NVARCSTR 500 0 0 yes
7 LOAD_DATE Load date and time into the target database DATETIME 24 0 9 yes
8 LOAD_TIME Load time into the target database NVARCSTR 8 0 0 yes
CRHH.VERAN - Person responsible for the

9 OWNER_ID NVARCSTR 3 0 0 yes
work center
Lookup TC24.KTEXT - Person responsible for

10 OWNER_NAME NVARCSTR 40 0 0 yes
the work center VERAN
11 PARENT_CODE CRHD.ARBPL - Work center - Parent node NVARCSTR 8 0 0 yes

Parent WC

Parent Node
CRHS.OBJID_UP - ID of superior object in the

14 PARENT_ID PK hierarchy and CRHH.NAME - Name of NVARCSTR 50 0 0 no
hierarchy
15 PLANT_ID CRHH.WERKS - Plant NVARCSTR 4 0 0 yes

Appendix
WORK_CNTR_HIER_I PK
17 CRHH.OBJID - Object ID of the resource NVARCSTR 8 0 0 no
D
WORK_CNTR_HIER_N
18 CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 yes
AME

Appendix
WORK_CENTER_HIER_HZ
Work Center Hierarchical relationship in Horizontal format from CRHH/CRHS
Column Dtype Is
1 LEAF_LVL Work Center Hierarchy Child ID DECIMAL 48 28 0 yes
2 LOAD_DATE Load date and time - for the target database DATETIME 24 0 9 yes
3 LOAD_TIME Load time for the target database NVARCSTR 8 0 0 yes
4 LVL_00_DESCR Description for 00 Parent Node NVARCSTR 40 0 0 yes

Parent Node
6 LVL_00_ID PK CRHS.OBJID_HO - Object ID of the resource NVARCSTR 8 0 0 no

Parent Node

Parent Node

Parent Node

Appendix
Parent Node

Parent Node
22 PLANT_ID PK CRHH.WERKS - Plant ID NVARCSTR 4 0 0 no
WORK_CNTR_HIER_N PK
23 CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 no
AME
CRHD-ARBPL (lookup) - Work Center unique

24 WORK_CNTR_ID PK NVARCSTR 8 0 0 no
name

Appendix
WORK_CENTER_HIER_VR
Work Center Hierarchical relationship in Vertical format from CRHH/CRHS
Column Dtype Is
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR

1 CHILD_FULL_NAME 50 0 0 yes
Object description/name lookup

name for Child ID
3 DEPTH Node depth in the hierarchy DECIMAL 48 28 0 yes
4 LEAF_FLAG 1 - Leaf, 0 - Root DECIMAL 48 28 0 yes
5 LOAD_DATE Load date and time - target database DATETIME 24 0 9 yes
6 LOAD_TIME Load time - target database NVARCSTR 8 0 0 yes
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR

7 PARENT_FULL_NAME 50 0 0 yes
Object description/name lookup

name for Parent ID
9 PLANT_ID PK CRHH.WERKS - Plant ID NVARCSTR 4 0 0 no
10 ROOT_FLAG 1 - Root, 0 - Leaf DECIMAL 48 28 0 yes
WORK_CNTR_HIER_N PK
11 CRHH.NAME - Name of hierarchy NVARCSTR 10 0 0 no
AME

Xi3 RM Sap Ps Ug en

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Xi3 RM Sap Ps Ug en

Uploaded by

Copyright:

Available Formats

SAP BusinessObjects Project Systems

Rapid Mart XI 3.2, version for SAP

Copyright © Copyright 2009 SAP AG. All rights reserved.

Chapter 3 Subject Areas 25

Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Chapter 5 Universe 143

Splitting the SAP Project System Universe . . . . . . . . . . . . . . . . . . . . . 227

Chapter 6 Installing the Rapid Mart 229

Chapter 7 Using the Rapid Mart 279

Executing the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

Chapter 8 Technical Implementation 321

Chapter 9 Documentation References 363

Appendix A Rapid Mart Data Schema 367

What is a Rapid Mart?

Rapid Marts packages accelerate Time to Value

SAP BusinessObjects Rapid Marts packages architecture

Rapid Marts packages include the following components:

About this document

What you can do with this Rapid Mart

Business function Types of analysis Details available in the

Dimensions available to support these analyses

Related Rapid Marts

Components shared with other SAP BusinessObjects Rapid

Project Systems Rapid Mart schema

The following chapter describes each component and reporting dimensions in

Where the Rapid Mart fits in Project

Projects (PS) Module Overview

Project Structure Overview

Work Breakdown Structure / Project Elements

The individual elements represent activities within the work breakdown

• Start - Start (SS) Relationship: Relationship between the start of one

• Finish - Finish (FF) Relationship: Relationship between the finish of

in the Rapid Mart, these are represented in the Network Relationships

Production Resource Tools (PRT) Assignments

Rapid Mart Processing

Attribute Name Dimension Tables

Attribute Name Dimension Tables

Fact table Fields

Column Name Description

Column Name Description

Rapid Mart Data

• Cost Element & Hierarchy

Network Order Section

Rapid Mart Processing

Attribute Name Dimension Tables

Attribute Name Dimension Tables

Fact Table Fields

Column Name Description

Column Name Description

Rapid Mart data

• Object Number Type

Network Relationship Section

Rapid Mart Processing

Attribute Name Dimension Tables

Attribute Name Dimension Tables

Fact Table Fields

Rapid Mart data

Project Cost Summary Section

Rapid Mart Processing

Attribute Name Dimension Tables

Attribute Name Dimension Tables