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
Rapid Mart Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
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 Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Project Cost Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Rapid Mart Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
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
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Network Relationship . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Project Cost . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
PRT Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Order Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
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
Chapter 5
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
5
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
6
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
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
Initial (First) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Incremental (Delta) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Network Relationship Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Project Cost Summary Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
PRT Assignment Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Initial (First) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Incremental (Delta) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
367
7
Contents
8
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Introduction
1
Introduction
What is a Rapid Mart?
What is a Rapid Mart?
SAP BusinessObjects Rapid Marts packages are blueprints for building data
marts with SAP BusinessObjects technology:
•
•
•
Data Services
Universe Designer
Web Intelligence.
Rapid Marts packages deliver jump-start ETL (extract, transform & load)
mappings, schema, and initial reporting content, accelerating the deployment
of BI (business intelligence) for enterprise applications from SAP, PeopleSoft,
Oracle, and Siebel.
Each Rapid Mart is designed to address the reporting needs of a specific
business area (or department) like accounting, sales, or purchasing. A
component-based framework allows conducting analysis across these
selected business areas by combining different packages within the same
source application suite.
Rapid Marts focus on basic standard configuration of the enterprise
applications. They are country and industry neutral templates meant to be
easily modified and extended to suit customer specific application
implementation and reporting needs.
Rapid Marts incorporate best practices, and provide easily modifiable
templates. With Rapid Marts total development time of a data mart solution is
greatly reduced.
Each customer situation is different. You will probably encounter one or more
of these:
•
Customizations you have made to SAP solutions the Rapid Mart does not
cover.
•
Standard SAP solutions data fields important for your specific business,
but not included in the Rapid Mart templates.
•
•
Optimization and performance challenges unique to your environment.
Reporting requirements not covered within the Rapid Mart template
reports.
Rapid Marts are flexible templates that you can adjust to account for these
unique situations. It is expected that some customization and optimization will
be needed to suit your individual environment. Rapid Marts are not an
out-of-the-box solution.
10
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Introduction
What is a Rapid Mart?
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
11
1
1
Introduction
What is a Rapid Mart?
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:
12
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Introduction
About this document
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
13
1
1
Introduction
About this document
14
•
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Overview
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.
The SAP BusinessObjects Project Systems Rapid Mart, version for SAP
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:
•
•
•
16
Milestone Trend Analysis
Earned Value Analysis
Billing Plan
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Overview
What you can do with this Rapid Mart
•
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
•
•
Funds management, effected by means of budget allocation
Automatic cost calculation wherever there are price and quantity
structures
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
17
2
2
Overview
Supported analyses
Supported analyses
The SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions supports several types of analyses:
Business function
Types of analysis
Details available in the
Rapid Mart
Project Costing
Project Balance Trend
Comparison
Displays the project balance
trend data for the selected
Company Code, Fiscal
Years, and Parent Project
Element.
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
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.
Project Cost YTD Trend
Analysis
View Actual YTD trends for
a specific Company Code,
Parent Project Element,
Fiscal Year, and Ledger
Version.
Project Cost Period
Comparison
View Actual, Planned (or
Budget), Variance Project
Element hierarchy
comparison for selected
Fiscal Year-Periods and
Ledger Version.
18
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Overview
Supported analyses
Business function
Types of analysis
Details available in the
Rapid Mart
Network Orders (Project
Orders)
Network Order Details
View network (production)
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.
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
Overview
View Network Relationship
overview for the selected
Project (or Network - also
called Internal Order Id) and
Operation Numbers (also
called Activities).
Production Resource & Tools
(PRT)
PRT Assignment Listing
View PRT assignments for
the selected Operation
Routing Id.
PRT Details
View PRT details for the
selected PRT (by PRT
Name).
Project Structure (Activity)
Planning
View project structure for
the selected Project Id.
Milestones
Activity (Project Order
Operations)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
19
2
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.
20
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Overview
Related Rapid Marts
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
21
2
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.
22
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Overview
Project Systems Rapid Mart schema
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
23
2
2
Overview
Where the Rapid Mart fits in Project Activities
Where the Rapid Mart fits in Project
Activities
The SAP BusinessObjects Project Systems Rapid Mart, version for SAP
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.
24
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Subject Areas
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:
•
26
Externally financed projects
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Projects (PS) Module Overview
•
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
27
3
3
Subject Areas
Projects (PS) Module Overview
Project Structure Overview
28
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Projects (PS) Module Overview
In the Rapid Mart, the various components of project structure are
represented:
•
•
Projects - are represented in the Project Dimension.
•
•
•
Networks - are represented by Network Orders
•
Many of the other items shown in the graphic above are also dimensions,
such as:
WBS Elements - are represented by the Project Element Dimension and
Project Element Hierarchy.
Activities - are represented by the Order Operations Dimension
Material Components - are represented by the Material Dimension and
Material by Plant Dimension
•
•
•
•
•
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
29
3
3
Subject Areas
Projects (PS) Module Overview
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.
30
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Projects (PS) Module Overview
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
31
3
3
Subject Areas
Projects (PS) Module Overview
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:
32
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Projects (PS) Module Overview
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
33
3
3
Subject Areas
Projects (PS) Module Overview
•
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:
•
34
Cost planning in various degrees of detail
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Milestone Section
•
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
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
35
3
3
Subject Areas
Milestone Section
Attribute Name
36
Dimension Tables
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Milestone Section
Attribute Name
Dimension Tables
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
Actual Milestone end
DAYS_DIFF_SCHED_BASIC
Number of Days between Scheduled Basic
and Actual Milestone end
DAYS_DIFF_SCHED_FCST
Number of Days between Scheduled Forecast
and Actual Milestone end
DAYS_SCHED_DURTN
Number of Days between MLST.TEDAT Scheduled milestone date (Basic) and
MLST.DATEH - Milestone created on
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
Actual Milestone end
HOURS_DIFF_FIXED_FCST
Number of Hours between Fixed Forecast
and Actual Milestone end
HOURS_DIFF_SCHED_BASIC
Number of Hours between Scheduled Basic
and Actual Milestone end
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
37
3
3
Subject Areas
Milestone Section
Column Name
Description
HOURS_DIFF_SCHED_FCST
Number of Hours between Scheduled
Forecast and Actual Milestone end
HOURS_SCHED_DURTN
Number of Hours between MLST.TEDAT Scheduled milestone date (Basic) and
MLST.DATEH - Milestone created on
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
MLST.LST_ACTDT - Actual date (Milestone
met) and MLST.DATEH - Milestone created
on
SECS_DIFF_FIXED_BASIC
Number of Seconds between Fixed Basic and
Actual Milestone end
SECS_DIFF_FIXED_FCST
Number of Seconds between Fixed Forecast
and Actual Milestone end
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 Scheduled milestone date (Basic) and
MLST.DATEH - Milestone created on
Additionally, several “flags” are employed to capture milestone status:
38
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Milestone Section
COLUMN_NAME
COMMENTS
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
39
3
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?
Network Order Section
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:
•
40
SAP BusinessObjects Production Planning Rapid Mart, version for SAP
solutions - Extracts only Order Category “10” (Standard Production
Orders).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Network Order Section
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
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
Rapid Mart Processing
The section captures the following dimensional attributes and their associated
dimension tables:
Attribute Name
Dimension Tables
Account Assignment Category
ACCT_ASSIGNMENT_CATEGORY
Business Area
BUSINESS_AREA
Company Code
COMPANY_CODE
Controlling Area
CONTROLLING_AREA
Cost Center & Hierarchy
COST_CENTER,
COST_CENTER_HIER,
COST_CENTER_HIER_HZ,
COST_CENTER_HIER_VR,
COST_CENTER_HIER_BAD
Cost Element & Hierarchy
COST_ELEMENT,
COST_ELEMENT_HIER,
COST_ELEMENT_HIER_HZ,
COST_ELEMENT_HIER_VR,
COST_ELEMENT_HIER_BAD
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
41
3
3
Subject Areas
Network Order Section
42
Attribute Name
Dimension Tables
Internal Order & Hierarchy
INTERNAL_ORDER,
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
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
Project Element & Hierarchy
PROJECT_ELEMENT,
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ,
PROJECT_ELEMENT_HIER_VR,
PROJECT_ELEMENT_HIER_BAD
Purchasing Organization
PURCH_ORGANIZATION
Routing
ROUTING
Service Person
SERVICE_PERSON
Special Procurement Type
SPECIAL_PROCUREMENT_TYPE
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Network Order Section
Attribute Name
Dimension Tables
Storage Location
STORAGE_LOCATION
Task List Type
TASK_LIST_TYPE
Task List Usage
TASK_LIST_USAGE
Time Dimension
TIME_DIM
Unit Of Measure
UNIT_OF_MEASURE
Valuation Area
VALUATION_AREA
Fact Table Fields
Important measures for Production Orders are both quantity and time
oriented:
Column Name
Description
DAYS_COMPLT_ACTL
Number of Days to actually complete
a service order (Calculated)
DAYS_COMPLT_BASIC
Number of Days to Basic complete a
service order (Calculated)
DAYS_COMPLT_FCST
Number of Forecast Days to complete a service order (Calculated)
DAYS_COMPLT_SCHED
Number of Days scheduled to complete a service order (Calculated)
DAYS_GR_PROCESS
AFPO.WEBAZ -Goods receipt processing time in days
DAYS_RELEASE_ACTL
Number of Days to actually release a
service order (Calculated)
DAYS_RELEASE_SCHED
Number of Days scheduled to
release a service order (Calculated)
HOURS_COMPLT_BASIC
Number of Hours to Basic complete a
service order (Calculated)
HOURS_COMPLT_FCST
Number of Forecast Hours to complete a service order (Calculated)
HOURS_COMPLT_SCHED
Number of Hours scheduled to complete a service order (Calculated)
MINS_COMPLT_ACTL
Number of Minutes to actually complete a service order (Calculated)
MINS_COMPLT_BASIC
Number of Minutes to Basic complete
a service order (Calculated)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
43
3
3
Subject Areas
Network Order Section
Column Name
Description
MINS_COMPLT_FCST
Number of Forecast Minutes to complete a service order (Calculated)
MINS_COMPLT_SCHED
Number of Minutes scheduled to
complete a service order (Calculated)
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.
44
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Network Order Section
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
Controlling Area
Cost Center & Hierarchy
Cost Element & Hierarchy
Document Type
Functional Area & Hierarchy
Internal Order & Hierarchy
Internal Order Status
Material Batch
Material By Plant
Material Group
Material Type
Material, Product Hierarchy
Monetary Currency
MRP Controller
Object Class
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
45
3
3
Subject Areas
Network Relationship Section
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Object Number Type
Object Status & Hierarchy
Plant
Plant Location
Profit Center & Hierarchy
Project
Project Element & Hierarchy
Purchasing Organization
Routing
Service Person
Special Procurement Type
Storage Location
Task List Type
Task List Usage
Time Dimension
Unit Of Measure
Valuation Area
Typical queries for this section include:
•
•
•
•
What is the average time to complete a network order?
•
Which Projects have the greatest / lowest shares of network orders in a
given plant?
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?
Network Relationship Section
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:
•
•
•
•
46
SS relationship (Start - Start)
FF relationship (Finish - Finish)
SF relationship (Start - Finish)
FS relationship (Finish - Start)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Network Relationship Section
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
AFVC - Operation within an order
The target table for Network Relationships is:
•
NETWORK_RELATIONSHIP_FACT
Rapid Mart Processing
The section captures the following dimensional attributes and their associated
dimension tables:
Attribute Name
Dimension Tables
Business Area
BUSINESS_AREA
Company Code
COMPANY_CODE
Control Key
CONTROL_KEY
Controlling Area
CONTROLLING_AREA
Functional Area & Hierarchy
FUNCTIONAL_AREA,
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BAD
Internal Order & Hierarchy
INTERNAL_ORDER,
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
MRP Controller
MRP_CONTROLLER
Object Status
OBJECT_STATUS,
OBJECT_STATUS_HZ
Order Operation
ORDER_OPERATION
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
47
3
3
Subject Areas
Network Relationship Section
Attribute Name
Dimension Tables
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
Relationship Type
RELATIONSHIP_TYPE
Storage Location
STORAGE_LOCATION
Time Dimension
TIME_DIM
Unit Of Measure
UNIT_OF_MEASURE
Valuation Area
VALUATION_AREA
Work Center Category
WORK_CENTER_CATEGORY
Work Center & Hierarchy
WORK_CENTER,
WORK_CENTER_HIER,
WORK_CENTER_HIER_HZ,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_BAD
Fact Table Fields
Important measures for Network Relationships are time oriented
COLUMN_NAME
COMMENTS
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
Relationship. Calculated as difference
between earliest end date and latest start
date
HOURS_DURTN_EARLST
Number of Hours for Network Relationship
based on Earliest start/end dates
48
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Network Relationship Section
COLUMN_NAME
COMMENTS
HOURS_DURTN_LATEST
Number of Hours for Network Relationship
based on Latest start/end dates
HOURS_DURTN_MAX
Max Number of Hours for Network
Relationship. Calculated as difference
between latest end date and earliest start
date
HOURS_DURTN_MIN
Min Number of Hours for Network
Relationship. Calculated as difference
between earliest end date and latest start
date
MAX_INTERVAL_FLAG
AFAB.MIMAX - Indicates whether maximum
time interval will be considered
MINS_DURTN_EARLST
Number of Minutes for Network Relationship
based on Earliest start/end dates
MINS_DURTN_LATEST
Number of Minutes for Network Relationship
based on Latest start/end dates
MINS_DURTN_MAX
Max Number of Minutes for Network
Relationship. Calculated as difference
between latest end date and earliest start
date
MINS_DURTN_MIN
Min Number of Minutes for Network
Relationship. Calculated as difference
between earliest end date and latest start
date
QTY_INTERVAL
AFAB.DAUER - Time interval between
relationships
SECS_DURTN
AFAB.DAUTM - Relationship duration (in
seconds) as result of scheduling
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
49
3
3
Subject Areas
Network Relationship Section
Rapid Mart data
The following diagram shows the tables in the Network Relationship section
as a Star Schema:
50
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Network Relationship Section
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
Controlling Area
Functional Area & Hierarchy
Internal Order & Hierarchy
MRP Controller
Object Status
Order Operation
Plant
Plant Location
Profit Center & Hierarchy
Project
Project Element & Hierarchy
Purchasing Organization
Relationship Type
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
51
3
3
Subject Areas
Project Cost Summary Section
•
•
•
•
•
•
Storage Location
Time Dimension
Unit Of Measure
Valuation Area
Work Center Category
Work Center & Hierarchy
Typical queries for this section include:
•
•
How are the operations within a given project linked to form a Network?
•
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?
Are there any dependencies (network relationships) missing in my
project?
Project Cost Summary Section
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
•
•
Funds management, effected by means of budget allocation
Automatic cost calculation wherever there are price and quantity
structures
Integration of project costs with Enterprise Controlling, such as
reconciliation with cost center accounting.
Project Costs are sourced from these SAP solutions tables:
•
•
•
•
RPSCO - Project info database: Costs, revenues, finances
AFVC - Operation within an order
PROJ - Project definition
PRPS - Project Element or WBS Element Master Data
The target tables for Project Costs are:
•
52
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Project Cost Summary Section
•
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.
Rapid Mart Processing
The section captures the following dimensional attributes and their associated
dimension tables:
Attribute Name
Dimension Tables
Business Activity
BUSINESS_ACTIVITY
Business Area
BUSINESS_AREA
Company Code
COMPANY_CODE
Controlling Area
CONTROLLING_AREA
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
Functional Area & Hierarchy
FUNCTIONAL_AREA,
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BAD
Monetary Currency
CURRENCY
Object Number Type
OBJECT_NUMBER_TYPE
Object Status
OBJECT_STATUS,
OBJECT_STATUS_HZ
Order Operation
ORDER_OPERATION
Pegging Object
PEGGING_OBJECT
Plant
PLANT
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
53
3
3
Subject Areas
Project Cost Summary Section
Attribute Name
Dimension Tables
Profit Center & Hierarchy
PROFIT_CENTER,
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
Progress Measure Method
PROGRESS_MEASURE_METHOD
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
Valuation Area
VALUATION_AREA
Variance Category
VARIANCE_CATEGORY
Fact Table Fields
Important measures for Project Cost Summary are:
PROJECT_COST_SUMMARY_FACT_HZ:
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
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)
AMT_CR_PER01_LOC
RPSCO.WLP01 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER01_TRX
RPSCO.WTP01 - PTD Credit value in
transactional currency
AMT_CR_PER02_LOC
RPSCO.WLP02 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER02_TRX
RPSCO.WTP02 - PTD Credit value in
transactional currency
AMT_CR_PER03_LOC
RPSCO.WLP03 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
54
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Project Cost Summary Section
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
AMT_CR_PER03_TRX
RPSCO.WTP03 - PTD Credit value in
transactional currency
AMT_CR_PER04_LOC
RPSCO.WLP04 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER04_TRX
RPSCO.WTP04 - PTD Credit value in
transactional currency
AMT_CR_PER05_LOC
RPSCO.WLP05 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER05_TRX
RPSCO.WTP05 - PTD Credit value in
transactional currency
AMT_CR_PER06_LOC
RPSCO.WLP06 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER06_TRX
RPSCO.WTP06 - PTD Credit value in
transactional currency
AMT_CR_PER07_LOC
RPSCO.WLP07 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER07_TRX
RPSCO.WTP07 - PTD Credit value in
transactional currency
AMT_CR_PER08_LOC
RPSCO.WLP08 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER08_TRX
RPSCO.WTP08 - PTD Credit value in
transactional currency
AMT_CR_PER09_LOC
RPSCO.WLP09 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER09_TRX
RPSCO.WTP09 - PTD Credit value in
transactional currency
AMT_CR_PER10_LOC
RPSCO.WLP10 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER10_TRX
RPSCO.WTP10 - PTD Credit value in
transactional currency
AMT_CR_PER11_LOC
RPSCO.WLP11 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER11_TRX
RPSCO.WTP11 - PTD Credit value in
transactional currency
AMT_CR_PER12_LOC
RPSCO.WLP12 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
55
3
3
Subject Areas
Project Cost Summary Section
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
AMT_CR_PER12_TRX
RPSCO.WTP12 - PTD Credit value in
transactional currency
AMT_CR_PER13_LOC
RPSCO.WLP13 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER13_TRX
RPSCO.WTP13 - PTD Credit value in
transactional currency
AMT_CR_PER14_LOC
RPSCO.WLP14 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER14_TRX
RPSCO.WTP14 - PTD Credit value in
transactional currency
AMT_CR_PER15_LOC
RPSCO.WLP15 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER15_TRX
RPSCO.WTP15 - PTD Credit value in
transactional currency
AMT_CR_PER16_LOC
RPSCO.WLP16 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_CR_PER16_TRX
RPSCO.WTP169 - PTD Credit value in
transactional currency
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_QTR02_LOC
RPSCO.WLP04 through 06 - Quarter Credit
(QTD) value in Ledger (Local) currency
AMT_CR_QTR02_TRX
RPSCO.WTP04 through 06 - Quarter Credit
value in transactional currency
AMT_CR_QTR03_LOC
RPSCO.WLP07 through 09 - Quarter Credit
(QTD) value in Ledger (Local) currency
AMT_CR_QTR03_TRX
RPSCO.WTP07 through 09 - Quarter Credit
value in transactional currency
AMT_CR_QTR04_LOC
RPSCO.WLP10 through 16 - Quarter Credit
(QTD) value in Ledger (Local) currency
AMT_CR_QTR04_TRX
RPSCO.WTP10 through 16 - Quarter Credit
value in transactional currency
AMT_CR_YTD_LOC
RPSCO.WLP00 through 16 - Quarter Credit
value in Ledger (Local) currency
56
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Project Cost Summary Section
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
AMT_CR_YTD_TRX
RPSCO.WTP00 through 16 - Quarter Credit
value in transactional currency
AMT_DR_PER00_LOC
RPSCO.WLP00 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER00_TRX
RPSCO.WTP00 - PTD Debit value in
transactional currency (Adjusting Year begin
period)
AMT_DR_PER01_LOC
RPSCO.WLP01 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER01_TRX
RPSCO.WTP01 - PTD Debit value in
transactional currency
AMT_DR_PER02_LOC
RPSCO.WLP02 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER02_TRX
RPSCO.WTP02 - PTD Debit value in
transactional currency
AMT_DR_PER03_LOC
RPSCO.WLP03 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER03_TRX
RPSCO.WTP03 - PTD Debit value in
transactional currency
AMT_DR_PER04_LOC
RPSCO.WLP04 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER04_TRX
RPSCO.WTP04 - PTD Debit value in
transactional currency
AMT_DR_PER05_LOC
RPSCO.WLP05 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER05_TRX
RPSCO.WTP05 - PTD Debit value in
transactional currency
AMT_DR_PER06_LOC
RPSCO.WLP06 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER06_TRX
RPSCO.WTP06 - PTD Debit value in
transactional currency
AMT_DR_PER07_LOC
RPSCO.WLP07 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER07_TRX
RPSCO.WTP07 - PTD Debit value in
transactional currency
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
57
3
3
Subject Areas
Project Cost Summary Section
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
AMT_DR_PER08_LOC
RPSCO.WLP08 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER08_TRX
RPSCO.WTP08 - PTD Debit value in
transactional currency
AMT_DR_PER09_LOC
RPSCO.WLP09 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER09_TRX
RPSCO.WTP09 - PTD Debit value in
transactional currency
AMT_DR_PER10_LOC
RPSCO.WLP10 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER10_TRX
RPSCO.WTP10 - PTD Debit value in
transactional currency
AMT_DR_PER11_LOC
RPSCO.WLP11 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER11_TRX
RPSCO.WTP11 - PTD Debit value in
transactional currency
AMT_DR_PER12_LOC
RPSCO.WLP12 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER12_TRX
RPSCO.WTP12 - PTD Debit value in
transactional currency
AMT_DR_PER13_LOC
RPSCO.WLP13 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER13_TRX
RPSCO.WTP13 - PTD Debit value in
transactional currency
AMT_DR_PER14_LOC
RPSCO.WLP14 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER14_TRX
RPSCO.WTP14 - PTD Debit value in
transactional currency
AMT_DR_PER15_LOC
RPSCO.WLP15 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER15_TRX
RPSCO.WTP15 - PTD Debit value in
transactional currency
AMT_DR_PER16_LOC
RPSCO.WLP16 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
AMT_DR_PER16_TRX
RPSCO.WTP16 - PTD Debit value in
transactional currency
58
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Project Cost Summary Section
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
AMT_DR_QTR01_LOC
RPSCO.WLP00 through 03 - Quarter Debit
(QTD) value in Ledger (Local) currency
AMT_DR_QTR01_TRX
RPSCO.WTP00 through 03 - Quarter Debit
(QTD) value in transactional currency
AMT_DR_QTR02_LOC
RPSCO.WLP04 through 06 - Quarter Debit
(QTD) value in Ledger (Local) currency
AMT_DR_QTR02_TRX
RPSCO.WTP04 through 06 - Quarter Debit
(QTD) value in transactional currency
AMT_DR_QTR03_LOC
RPSCO.WLP07 through 09 - Quarter Debit
(QTD) value in Ledger (Local) currency
AMT_DR_QTR03_TRX
RPSCO.WTP07 through 09 - Quarter Debit
(QTD) value in transactional currency
AMT_DR_QTR04_LOC
RPSCO.WLP10 through 16 - Quarter Debit
(QTD) value in Ledger (Local) currency
AMT_DR_QTR04_TRX
RPSCO.WTP10 through 16 - Quarter Debit
(QTD) value in transactional currency
AMT_DR_YTD_LOC
RPSCO.WLP00 through 16 - Quarter Debit
value in Ledger (Local) currency
AMT_DR_YTD_TRX
RPSCO.WTP00 through 16 - Quarter Debit
value in transactional currency
PROJECT_COST_SUMMARY_FACT_VR
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
59
3
3
Subject Areas
Project Cost Summary Section
PROJECT_COST_SUMMARY_FACT_HZ
Column Name
Description
AMT_CR_TRX
RPSCO-WTP01 through WTP16 - Period
Credit value in Transactional currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Per
16
AMT_CR_YTD_LOC
RPSCO-WLP01 through WLP16 - YTD Credit
value in Ledger (Local) currency
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
value in Ledger (Local) currency
AMT_DR_QTD_TRX
RPSCO-WTP01 through WTP16 - QTD Debit
value in Transactional currency
AMT_DR_TRX
RPSCO-WTP01 through WTP16 - Period
Debit value in Transactional currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Per
16
AMT_DR_YTD_LOC
RPSCO-WLP01 through WLP16 - YTD Debit
value in Ledger (Local) currency
AMT_DR_YTD_TRX
RPSCO-WTP01 through WTP16 - YTD Debit
value in Transactional currency
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
60
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
Project Cost Summary Section
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
Controlling Area
Cost Object Indicator
Financial Management Area
Financial Record Category
Financial Record Type
Financing Code
Fiscal Period
Functional Area & Hierarchy
Monetary Currency
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
61
3
3
Subject Areas
PRT Assignment Section
•
•
•
•
•
•
•
•
•
•
•
•
Object Number Type
Object Status
Order Operation
Pegging Object
Plant
Profit Center & Hierarchy
Progress Measure Method
Project
Project Element & Hierarchy
Purchasing Organization
Valuation Area
Variance Category
Typical queries for this section include:
•
•
•
What costs has my project incurred year-to-date?
•
What is the trend in project costs month-to-month for each Project (WBS)
Element?
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?
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.
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:
•
•
•
AFVC - Operation within an order
AFFH - PRT assignment data for the work order
CRFH - CIM production resource/tool master data
The section stores the data in the fact table
•
62
PRT_ASSIGNMENT_FACT
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
PRT Assignment Section
Rapid Mart processing
The section captures the following dimensional attributes and their associated
dimension tables
Attribute
Dimension Tables
Activity & Hierarchy
ACTIVITY, ACTIVITY_HIER,
ACTIVITY_HIER_HZ,
ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
Business Area
BUSINESS_AREA
Chart Of Accounts
CHART_OF_ACCOUNTS
Company Code
COMPANY_CODE
Control Key
CONTROL_KEY
Controlling Area
CONTROLLING_AREA
Cost Center & Hierarchy
COST_CENTER,
COST_CENTER_HIER,
COST_CENTER_HIER_HZ,
COST_CENTER_HIER_VR,
COST_CENTER_HIER_BAD
Cost Element & Hierarchy
COST_ELEMENT,
COST_ELEMENT_HIER,
COST_ELEMENT_HIER_HZ,
COST_ELEMENT_HIER_VR,
COST_ELEMENT_HIER_BAD
Functional Area & Hierarchy
FUNCTIONAL_AREA,
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BAD
Internal Order & Hierarchy
INTERNAL_ORDER,
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
Material, Product Hierarchy
MATERIAL,
PRODUCT_HIERARCHY
MRP Controller
MRP_CONTROLLER
Object Number Type
OBJECT_NUMBER_TYPE
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
63
3
3
Subject Areas
PRT Assignment Section
64
Attribute
Dimension Tables
Object Status
OBJECT_STATUS,
OBJECT_STATUS_HZ
Object Type
OBJECT_TYPE
Order Operation
ORDER_OPERATION
Plant
PLANT
Plant Location
PLANT_LOCATION
Profit Center
PROFIT_CENTER
Profit Center & Hierarchy
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
Project
PROJECT
Project Element & Hierarchy
PROJECT_ELEMENT,
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ,
PROJECT_ELEMENT_HIER_VR,
PROJECT_ELEMENT_HIER_BAD
PRT Category
PRT_CATEGORY
PRT Grouping Key
PRT_GROUPING_KEY
PRT Master
PRT_MASTER
PRT Status
PRT_STATUS
Purchasing Organization
PURCH_ORGANIZATION
Reference Date Key
REFERENCE_DATE_KEY
Routing
ROUTING
Routing Operation
ROUTING_OPERATION
Routing Sequence
ROUTING_SEQUENCE
Standard Text Key
STANDARD_TEXT_KEY
Storage Location
STORAGE_LOCATION
Task List Type
TASK_LIST_TYPE
Time Dimension
TIME_DIM
Unit Of Measure
UNIT_OF_MEASURE
Valuation Area
VALUATION_AREA
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
PRT Assignment Section
Attribute
Dimension Tables
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
Work Center Formula
WORK_CENTER_FORMULA,
FORMULA_PARAMETER
Fact Table Fields
Important measures for PRT Assignments are both quantity and time oriented
Column Name
Description
ACTL_USG_VALUE
AFFH.EWIST - Actual usage value for
production resource/tool
DAYS_DURTN_ACTL
Actual Number of Days for Network
Relationship. Calculated as difference
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
Relationship. Calculated as difference
between latest end date and earliest start date
(UOM_ID = TAG in IDES)
DAYS_DURTN_MIN
Min Number of Days for Network
Relationship. Calculated as difference
between earliest end date and latest start date
(UOM_ID = TAG in IDES)
HOURS_DURTN_ACTL
Actual Number of HOURS for Network
Relationship. Calculated as difference
between actual end date and start date
(UOM_ID = HUR in IDES)
HOURS_DURTN_EARLST
Number of Hours for Network Relationship
based on Earliest start/end dates (UOM_ID =
HUR in IDES)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
65
3
3
Subject Areas
PRT Assignment Section
Column Name
Description
HOURS_DURTN_LATEST
Number of HOURS for Network Relationship
based on Latest start/end dates (UOM_ID =
HUR in IDES)
HOURS_DURTN_MAX
Max Number of Hours for Network
Relationship. Calculated as difference
between latest end date and earliest start date
(UOM_ID = HUR in IDES)
HOURS_DURTN_MIN
Min Number of Hours for Network
Relationship. Calculated as difference
between earliest end date and latest start date
(UOM_ID = HUR in IDES)
MINS_DURTN_ACTL
Actual Number of Mins for Network
Relationship. Calculated as difference
between actual end date and start date
(UOM_ID = MIN in IDES)
MINS_DURTN_EARLST
Number of Mins for Network Relationship
based on Earliest start/end dates (UOM_ID =
MIN in IDES)
MINS_DURTN_LATEST
Number of Mins for Network Relationship
based on Latest start/end dates (UOM_ID =
MIN in IDES)
MINS_DURTN_MAX
Max Number of Mins for Network
Relationship. Calculated as difference
between latest end date and earliest start date
(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
production resource/tool
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
66
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
PRT Assignment Section
Column Name
Description
QTY_PRT_CONFIRM
AFFH.MGIST - Confirmed quantity of
production resource/tool
QTY_PRT_PLAN
AFFH.MGSOL - Total planned quantity of
production resource/tool
QTY_PRT_REMAIN
AFFH.MGRSTEH - Remaining quantity of the
production resource/tool
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
production resources/tools
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
67
3
3
Subject Areas
PRT Assignment Section
Rapid Mart data
The following diagram shows the tables in the PRT Assignment section as a
Star Schema.
68
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
PRT Assignment Section
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
Controlling Area
Cost Center & Hierarchy
Cost Element & Hierarchy
Functional Area & Hierarchy
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
69
3
3
Subject Areas
PRT Assignment Section
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Internal Order & Hierarchy
Material, Product Hierarchy
MRP Controller
Object Number Type
Object Status
Object Type
Order Operation
Plant
Plant Location
Profit Center
Profit Center & Hierarchy
Project
Project Element & Hierarchy
PRT Category
PRT Grouping Key
PRT Master
PRT Status
Purchasing Organization
Reference Date Key
Routing
Routing Operation
Routing Sequence
Standard Text Key
Storage Location
Task List Type
Time Dimension
Unit Of Measure
Valuation Area
Work Center & Hierarchy
Work Center Category
Work Center Formula
Typical queries for this section include:
•
•
70
Which are the top 10 PRT’s are assigned by Project?
Are Operations (Project Activities) using a specific PRT finishing on
schedule?
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Subject Areas
PRT Assignment Section
•
•
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?
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
71
3
3
Subject Areas
PRT Assignment Section
72
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Reports
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
Milestones are used in the Project System to designate significant events or
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).
74
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Milestone
Overview
View milestone listing for the specified Project Id.
Details
View Milestone details by Milestone Id section.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
75
4
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..
76
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Milestone
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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
77
4
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
TS
CHART_OF_ACCOUNTS.CHART_OF_
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
R_HZ
MILESTONE_FACT.COST_ELEM_ID=C
OST_ELEMENT_HIER_HZ.COST_ELE
M_ID and
MILESTONE_FACT.CHART_OF_ACCT_
ID=COST_ELEMENT_HIER_HZ.CHART
_OF_ACCT_ID
78
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Milestone
Fact Table
Dimension Table
Join Expression
MILESTONE_FACT
COST_ELEMENT_HIE
R_VR
MILESTONE_FACT.CHART_OF_ACCT_
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_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
MILESTONE_FACT.INTERNAL_ORDER
_ID=INTERNAL_ORDER.INTERNAL_O
RDER_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
79
4
4
Reports
Milestone
Fact Table
Dimension Table
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
ON
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
N
ROUTING_OPERATION.GROUP_TYPE
_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
80
Join Expression
PURCH_ORGANIZATION.PURCH_ORG
_ID=MILESTONE_FACT.PURCH_ORG_
ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network (Production) Order
Fact Table
Dimension Table
Join Expression
MILESTONE_FACT
WORK_CENTER_CAT
EGORY
MILESTONE_FACT.WORK_CNTR_CAT
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
A network order is a special type of production order used for Projects in the
SAP Applications system.
Reports
Network order is suited to detail, trend, and high level analysis. Below is a list
of the reports included here for analysis:
•
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
81
4
4
Reports
Network (Production) Order
Project Summary
View Network Order summary statistics by Project..
Listing
View network order listing by Order Id..
82
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network (Production) Order
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
83
4
4
Reports
Network (Production) Order
Summary
View network order summary statistics..
84
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network (Production) Order
Trend by Project
View network order trends by Business Area.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
85
4
4
Reports
Network (Production) Order
Top 10 Project Elements
View Top 10 Project Elements based on count of network orders. Uses Web
Intelligence ranking feature..
Calculations
86
•
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])
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network (Production) Order
Recommended Table Joins
To analyze Netowrk (Production) Order data you will need to create joins between
the fact and dimension tables as follows:
Fact Table
Dimension Table
Join Expression
MATERIAL
PRODUCT_HIERARCH MATERIAL.PROD_HIER_ID=PRODUCT
Y
_HIERARCHY.PROD_HIER_ID
PRODUCTION_ORDE
R_FACT
ACCT_ASSIGNMENT_ ACCT_ASSIGNMENT_CATEGORY.ACC
CATEGORY
T_ASSIGN_CATEG_ID=PRODUCTION_
ORDER_FACT.ACCT_ASSIGN_CATEG
_ID
PRODUCTION_ORDE
R_FACT
BUSINESS_AREA
BUSINESS_AREA.BUS_AREA_ID=PRO
DUCTION_ORDER_FACT.BUS_AREA_I
D
PRODUCTION_ORDE
R_FACT
CHART_OF_ACCOUN
TS
CHART_OF_ACCOUNTS.CHART_OF_
ACCT_ID=PRODUCTION_ORDER_FAC
T.CHART_OF_ACCT_ID
PRODUCTION_ORDE
R_FACT
COMPANY_CODE
COMPANY_CODE.CMPNY_CODE_ID=
PRODUCTION_ORDER_FACT.CMPNY_
CODE_ID
PRODUCTION_ORDE
R_FACT
CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
=PRODUCTION_ORDER_FACT.CTRL_
AREA_ID
PRODUCTION_ORDE
R_FACT
COST_CENTER
PRODUCTION_ORDER_FACT.CTRL_A
REA_ID=COST_CENTER.CTRL_AREA_
ID AND
PRODUCTION_ORDER_FACT.COST_C
NTR_ID=COST_CENTER.COST_CNTR
_ID
PRODUCTION_ORDE
R_FACT
COST_CENTER_HIER
_HZ
PRODUCTION_ORDER_FACT.CTRL_A
REA_ID=COST_CENTER_HIER_HZ.CT
RL_AREA_ID and
PRODUCTION_ORDER_FACT.COST_C
NTR_ID=COST_CENTER_HIER_HZ.CO
ST_CNTR_ID
PRODUCTION_ORDE
R_FACT
COST_CENTER_HIER
_VR
PRODUCTION_ORDER_FACT.CTRL_A
REA_ID=COST_CENTER_HIER_VR.CT
RL_AREA_ID and
PRODUCTION_ORDER_FACT.COST_C
NTR_ID=COST_CENTER_HIER_VR.CH
ILD_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
87
4
4
Reports
Network (Production) Order
Fact Table
Dimension Table
Join Expression
PRODUCTION_ORDE
R_FACT
COST_ELEMENT
PRODUCTION_ORDER_FACT.CHART_
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
R_FACT
COST_ELEMENT_HIE
R_HZ
PRODUCTION_ORDER_FACT.COST_E
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
R_FACT
COST_ELEMENT_HIE
R_VR
PRODUCTION_ORDER_FACT.CHART_
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
R_FACT
CURRENCY
CURRENCY.CURR_ID=PRODUCTION_
ORDER_FACT.CURR_ID
PRODUCTION_ORDE
R_FACT
DOCUMENT_TYPE
DOCUMENT_TYPE.DOC_CATEG_ID=P
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
R_FACT
FUNCTIONAL_AREA
PRODUCTION_ORDER_FACT.FUNCTN
L_AREA_ID=FUNCTIONAL_AREA.FUN
CTNL_AREA_ID
PRODUCTION_ORDE
R_FACT
FUNCTIONAL_AREA_
HIER_HZ
PRODUCTION_ORDER_FACT.FUNCTN
L_AREA_ID=FUNCTIONAL_AREA_HIE
R_HZ.FUNCTNL_AREA_ID
PRODUCTION_ORDE
R_FACT
FUNCTIONAL_AREA_
HIER_VR
PRODUCTION_ORDER_FACT.FUNCTN
L_AREA_ID=FUNCTIONAL_AREA_HIE
R_VR.CHILD_ID
PRODUCTION_ORDE
R_FACT
INTERNAL_ORDER
PRODUCTION_ORDER_FACT.INTERN
AL_ORDER_ID=INTERNAL_ORDER.IN
TERNAL_ORDER_ID
88
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network (Production) Order
Fact Table
Dimension Table
Join Expression
PRODUCTION_ORDE
R_FACT
INTERNAL_ORDER_HI PRODUCTION_ORDER_FACT.INTERN
ER_HZ
AL_ORDER_ID=INTERNAL_ORDER_HI
ER_HZ.INTERNAL_ORDER_ID
PRODUCTION_ORDE
R_FACT
INTERNAL_ORDER_HI PRODUCTION_ORDER_FACT.INTERN
ER_VR
AL_ORDER_ID=INTERNAL_ORDER_HI
ER_VR.CHILD_ID
PRODUCTION_ORDE
R_FACT
INTERNAL_ORDER_S
TATUS
PRODUCTION_ORDER_FACT.DOC_TY
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
R_FACT
MATERIAL
PRODUCTION_ORDER_FACT.MATERI
AL_ID=MATERIAL.MATERIAL_ID
PRODUCTION_ORDE
R_FACT
MATERIAL_BATCH
PRODUCTION_ORDER_FACT.BATCH_I
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
R_FACT
MATERIAL_BY_PLANT PRODUCTION_ORDER_FACT.MATERI
AL_ID=MATERIAL_BY_PLANT.MATERI
AL_ID and
PRODUCTION_ORDER_FACT.PLANT_I
D=MATERIAL_BY_PLANT.PLANT_ID
PRODUCTION_ORDE
R_FACT
MATERIAL_GROUP
PRODUCTION_ORDER_FACT.MTRL_G
RP_ID=MATERIAL_GROUP.MTRL_GRP
_ID
PRODUCTION_ORDE
R_FACT
MATERIAL_TYPE
PRODUCTION_ORDER_FACT.MTRL_T
YPE_ID=MATERIAL_TYPE.MTRL_TYP
E_ID
PRODUCTION_ORDE
R_FACT
MRP_CONTROLLER
PRODUCTION_ORDER_FACT.MRP_CT
RLLER_ID=MRP_CONTROLLER.MRP_
CTRLLER_ID and
PRODUCTION_ORDER_FACT.PLANT_I
D=MRP_CONTROLLER.PLANT_ID
PRODUCTION_ORDE
R_FACT
PRODUCTION_ORDE
R_FACT
PRODUCTION_ORDER_FACT.DOC_CA
TEG_ID='20'
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
89
4
4
Reports
Network (Production) Order
Fact Table
Dimension Table
Join Expression
PRODUCTION_ORDE
R_FACT
NETWORK_PROFILE
PRODUCTION_ORDER_FACT.GROUP
_APPLICTN_ID=NETWORK_PROFILE.
GROUP_APPLICTN_ID and
PRODUCTION_ORDER_FACT.NETWO
RK_PROFILE_ID=NETWORK_PROFILE
.NETWORK_PROFILE_ID
PRODUCTION_ORDE
R_FACT
OBJECT_CLASS
PRODUCTION_ORDER_FACT.OBJ_CL
ASS_ID=OBJECT_CLASS.OBJ_CLASS
_ID
PRODUCTION_ORDE
R_FACT
OBJECT_NUMBER_TY PRODUCTION_ORDER_FACT.OBJ_NU
PE
M_TYPE_ID=OBJECT_NUMBER_TYPE
.OBJ_NUM_TYPE_ID
PRODUCTION_ORDE
R_FACT
OBJECT_STATUS_HZ
PRODUCTION_ORDER_FACT.OBJ_ID=
OBJECT_STATUS_HZ.OBJ_ID
PRODUCTION_ORDE
R_FACT
PLANT
PLANT.PLANT_ID=PRODUCTION_ORD
ER_FACT.PLANT_ID
PRODUCTION_ORDE
R_FACT
PLANT_LOCATION
PLANT_LOCATION.PLANT_ID=PRODU
CTION_ORDER_FACT.PLANT_ID and
PLANT_LOCATION.LOCATN_ID=PROD
UCTION_ORDER_FACT.LOCATN_ID
PRODUCTION_ORDE
R_FACT
PRODUCT_HIERARCH PRODUCTION_ORDER_FACT.PROD_H
Y
IER_ID=PRODUCT_HIERARCHY.PROD
_HIER_ID
PRODUCTION_ORDE
R_FACT
PRODUCTION_SCHED PRODUCTION_ORDER_FACT.PLANT_I
ULER
D=
PRODUCTION_SCHEDULER.PLANT_I
D AND
PRODUCTION_ORDER_FACT.PROD_S
CHEDLER_ID=PRODUCTION_SCHED
ULER.PROD_SCHEDLER_ID
PRODUCTION_ORDE
R_FACT
PROFIT_CENTER
90
PRODUCTION_ORDER_FACT.CTRL_A
REA_ID=PROFIT_CENTER.CTRL_ARE
A_ID and
PRODUCTION_ORDER_FACT.PROFIT
_CNTR_ID=PROFIT_CENTER.PROFIT_
CNTR_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network (Production) Order
Fact Table
Dimension Table
Join Expression
PRODUCTION_ORDE
R_FACT
PROFIT_CENTER_HIE PRODUCTION_ORDER_FACT.CTRL_A
R_HZ
REA_ID=PROFIT_CENTER_HIER_HZ.C
TRL_AREA_ID and
PRODUCTION_ORDER_FACT.PROFIT
_CNTR_ID=PROFIT_CENTER_HIER_H
Z.PROFIT_CNTR_ID
PRODUCTION_ORDE
R_FACT
PROFIT_CENTER_HIE PRODUCTION_ORDER_FACT.CTRL_A
R_VR
REA_ID=PROFIT_CENTER_HIER_VR.
CTRL_AREA_ID and
PRODUCTION_ORDER_FACT.PROFIT
_CNTR_ID=PROFIT_CENTER_HIER_V
R.CHILD_ID
PRODUCTION_ORDE
R_FACT
PROJECT
PRODUCTION_ORDER_FACT.PROJ_I
D=PROJECT.PROJ_ID
PRODUCTION_ORDE
R_FACT
PROJECT_ELEMENT
PRODUCTION_ORDER_FACT.PROJ_E
LEM_ID=PROJECT_ELEMENT.PROJ_E
LEM_ID
PRODUCTION_ORDE
R_FACT
PROJECT_ELEMENT_ PRODUCTION_ORDER_FACT.PROJ_E
HIER_HZ
LEM_ID=PROJECT_ELEMENT_HIER_H
Z.PROJ_ELEM_ID
PRODUCTION_ORDE
R_FACT
PROJECT_ELEMENT_ PRODUCTION_ORDER_FACT.PROJ_E
HIER_VR
LEM_ID=PROJECT_ELEMENT_HIER_V
R.CHILD_ID
PRODUCTION_ORDE
R_FACT
PURCH_ORGANIZATI
ON
PURCH_ORGANIZATION.PURCH_ORG
_ID=PRODUCTION_ORDER_FACT.PU
RCH_ORG_ID
PRODUCTION_ORDE
R_FACT
ROUTING
ROUTING.ROUTING_ID=PRODUCTION
_ORDER_FACT.ROUTING_ID
PRODUCTION_ORDE
R_FACT
SERVICE_PERSON
SERVICE_PERSON.PERSON_ID=PRO
DUCTION_ORDER_FACT.PERSON_ID_
RESP
PRODUCTION_ORDE
R_FACT
SPECIAL_PROCUREM PRODUCTION_ORDER_FACT.SPECL_
ENT_TYPE
PROCUREMNT_TYPE_ID=SPECIAL_P
ROCUREMENT_TYPE.SPECL_PROCU
REMNT_TYPE_ID
PRODUCTION_ORDE
R_FACT
STORAGE_LOCATION STORAGE_LOCATION.STORAGE_LOC
ATN_ID=PRODUCTION_ORDER_FACT.
STORAGE_LOCATN_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
91
4
4
Reports
Network Relationship
Fact Table
Dimension Table
Join Expression
PRODUCTION_ORDE
R_FACT
TASK_LIST_TYPE
TASK_LIST_TYPE.GROUP_TYPE_ID=P
RODUCTION_ORDER_FACT.GROUP_T
YPE_ID
PRODUCTION_ORDE
R_FACT
TASK_LIST_USAGE
TASK_LIST_USAGE.GROUP_USG_ID=
PRODUCTION_ORDER_FACT.GROUP
_USG_ID
PRODUCTION_ORDE
R_FACT
TIME_DIM
TIME_DIM.CALENDAR_DATE=PRODU
CTION_ORDER_FACT.CREATE_DATE
PRODUCTION_ORDE
R_FACT
UNIT_OF_MEASURE
UNIT_OF_MEASURE.UOM_ID=PRODU
CTION_ORDER_FACT.UOM_ID
PRODUCTION_ORDE
R_FACT
VALUATION_AREA
VALUATION_AREA.VALUATN_AREA_ID
=PRODUCTION_ORDER_FACT.VALUA
TN_AREA_ID
OBJECT_STATUS_HZ
OBJECT_STATUS
OBJECT_STATUS_HZ.OBJ_ID=OBJEC
T_STATUS.OBJ_ID
Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 27 for master reports.
Network Relationship
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
of the reports included here for analysis:
•
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.
92
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network Relationship
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".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
93
4
4
Reports
Network Relationship
Recommended Table Joins
To analyze Network Relationship data you will need to create joins between the
fact and dimension tables as follows:
Fact Table
Dimension Table
Join Expression
NETWORK_RELATION BUSINESS_AREA
SHIP_FACT
BUSINESS_AREA.BUS_AREA_ID=NET
WORK_RELATIONSHIP_FACT.BUS_AR
EA_ID
NETWORK_RELATION COMPANY_CODE
SHIP_FACT
COMPANY_CODE.CMPNY_CODE_ID=
NETWORK_RELATIONSHIP_FACT.CM
PNY_CODE_ID
NETWORK_RELATION CONTROL_KEY
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.CTR
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
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.FUN
CTNL_AREA_ID=FUNCTIONAL_AREA.
FUNCTNL_AREA_ID
NETWORK_RELATION FUNCTIONAL_AREA_
SHIP_FACT
HIER_HZ
NETWORK_RELATIONSHIP_FACT.FUN
CTNL_AREA_ID=FUNCTIONAL_AREA_
HIER_HZ.FUNCTNL_AREA_ID
NETWORK_RELATION FUNCTIONAL_AREA_
SHIP_FACT
HIER_VR
NETWORK_RELATIONSHIP_FACT.FUN
CTNL_AREA_ID=FUNCTIONAL_AREA_
HIER_VR.CHILD_ID
NETWORK_RELATION INTERNAL_ORDER
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.INT
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
SHIP_FACT
94
NETWORK_RELATIONSHIP_FACT.MR
P_CTRLLER_ID=MRP_CONTROLLER.
MRP_CTRLLER_ID and
NETWORK_RELATIONSHIP_FACT.PLA
NT_ID=MRP_CONTROLLER.PLANT_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Network Relationship
Fact Table
Dimension Table
Join Expression
NETWORK_RELATION NETWORK_HIER_VR
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.REL
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
NETWORK_RELATIONSHIP_FACT.OPE
RATN_SEQ_ID_PAR=NETWORK_HIER
_VR.OPERATN_SEQ_ID_PARENT and
NETWORK_RELATIONSHIP_FACT.OPE
RATN_ROUTING_ID=NETWORK_HIER
_VR.OPERATN_ROUTING_ID_CHILD
and
NETWORK_RELATIONSHIP_FACT.OPE
RATN_SEQ_ID=NETWORK_HIER_VR.
OPERATN_SEQ_ID_CHILD
NETWORK_RELATION OBJECT_STATUS_HZ
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.OBJ
_ID=OBJECT_STATUS_HZ.OBJ_ID
NETWORK_RELATION ORDER_OPERATION
SHIP_FACT
ORDER_OPERATION.OPERATN_ROU
TING_ID=NETWORK_RELATIONSHIP_
FACT.OPERATN_ROUTING_ID and
ORDER_OPERATION.OPERATN_SEQ_
ID=NETWORK_RELATIONSHIP_FACT.
OPERATN_SEQ_ID
NETWORK_RELATION PLANT
SHIP_FACT
PLANT.PLANT_ID=NETWORK_RELATI
ONSHIP_FACT.PLANT_ID
NETWORK_RELATION PLANT_LOCATION
SHIP_FACT
PLANT_LOCATION.PLANT_ID=NETWO
RK_RELATIONSHIP_FACT.PLANT_ID
AND
PLANT_LOCATION.LOCATN_ID=NETW
ORK_RELATIONSHIP_FACT.LOCATN_I
D
NETWORK_RELATION PROFIT_CENTER
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.CTR
L_AREA_ID=PROFIT_CENTER.CTRL_
AREA_ID and
NETWORK_RELATIONSHIP_FACT.PRO
FIT_CNTR_ID=PROFIT_CENTER.PROF
IT_CNTR_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
95
4
4
Reports
Network Relationship
Fact Table
Dimension Table
Join Expression
NETWORK_RELATION PROFIT_CENTER_HIE NETWORK_RELATIONSHIP_FACT.CTR
SHIP_FACT
R_HZ
L_AREA_ID=PROFIT_CENTER_HIER_
HZ.CTRL_AREA_ID and
NETWORK_RELATIONSHIP_FACT.PRO
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
NETWORK_RELATIONSHIP_FACT.PRO
FIT_CNTR_ID=PROFIT_CENTER_HIER
_VR.CHILD_ID
NETWORK_RELATION PROJECT
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.PRO
J_ID=PROJECT.PROJ_ID
NETWORK_RELATION PROJECT_ELEMENT
SHIP_FACT
PROJECT_ELEMENT.PROJ_ELEM_ID=
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
SHIP_FACT
ON
PURCH_ORGANIZATION.PURCH_ORG
_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
SHIP_FACT
TIME_DIM.CALENDAR_DATE=NETWO
RK_RELATIONSHIP_FACT.EARLST_ST
ART_DATE
NETWORK_RELATION UNIT_OF_MEASURE
SHIP_FACT
UNIT_OF_MEASURE.UOM_ID=NETWO
RK_RELATIONSHIP_FACT.UOM_ID
NETWORK_RELATION VALUATION_AREA
SHIP_FACT
VALUATION_AREA.VALUATN_AREA_ID
=NETWORK_RELATIONSHIP_FACT.VA
LUATN_AREA_ID
96
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Project Cost
Fact Table
Dimension Table
Join Expression
NETWORK_RELATION WORK_CENTER
SHIP_FACT
NETWORK_RELATIONSHIP_FACT.PLA
NT_ID=WORK_CENTER.PLANT_ID and
NETWORK_RELATIONSHIP_FACT.WO
RK_CNTR_ID=WORK_CENTER.WORK
_CNTR_ID
NETWORK_RELATION WORK_CENTER_CAT
SHIP_FACT
EGORY
NETWORK_RELATIONSHIP_FACT.WO
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
NETWORK_RELATIONSHIP_FACT.PLA
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
NETWORK_RELATIONSHIP_FACT.PLA
NT_ID=WORK_CENTER_HIER_VR.PLA
NT_ID
OBJECT_STATUS_HZ
OBJECT_STATUS
OBJECT_STATUS_HZ.OBJ_ID=OBJEC
T_STATUS.OBJ_ID
Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 27 for master reports.
Project Cost
Project Costing is used to plan, monitor, and control project costs, thereby
achieving comprehensive cost accounting.
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
97
4
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]
98
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Project Cost
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
99
4
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]
•
Variance % = If([Actual] <> 0; [Variance]/[Actual]; If([Actual]= 0 And
[Variance]=0; 0;1))
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]
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
100
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Project Cost
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]
•
•
Budget YTD Balance = [PROJ COST SUM Vr Budget YTD Balance LOC]
Balance Variance = [PROJ COST SUM Vr Actual YTD Balance
LOC]-[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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
101
4
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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
102
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Project Cost
Recommended Table Joins
To analyze Project Cost Summary data you will need to create joins between the
fact and dimension tables as follows:
Fact Table
Dimension Table
Join Expression
OBJECT_STATUS_HZ
OBJECT_STATUS
OBJECT_STATUS_HZ.OBJ_ID=OBJEC
T_STATUS.OBJ_ID
PROJECT_COST_SUM BUSINESS_ACTIVITY
MARY_FACT_HZ
BUSINESS_ACTIVITY.BUS_ACTIVITY_I
D=PROJECT_COST_SUMMARY_FACT
_HZ.BUS_ACTIVITY_ID
PROJECT_COST_SUM BUSINESS_AREA
MARY_FACT_HZ
BUSINESS_AREA.BUS_AREA_ID=PRO
JECT_COST_SUMMARY_FACT_HZ.BU
S_AREA_ID
PROJECT_COST_SUM COMPANY_CODE
MARY_FACT_HZ
COMPANY_CODE.CMPNY_CODE_ID=
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
MARY_FACT_HZ
CURRENCY.CURR_ID=PROJECT_COS
T_SUMMARY_FACT_HZ.CURR_ID_TR
X
PROJECT_COST_SUM CURRENCY
MARY_FACT_HZ
CURRENCY.CURR_ID=PROJECT_COS
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
103
4
4
Reports
Project Cost
Fact Table
Dimension Table
Join Expression
PROJECT_COST_SUM FINANCING_CODE
MARY_FACT_HZ
FINANCING_CODE.FIN_MGMT_AREA_
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
MARY_FACT_HZ
PROJECT_COST_SUMMARY_FACT_H
Z.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_
MARY_FACT_HZ
HIER_HZ
PROJECT_COST_SUMMARY_FACT_H
Z.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA_HIER_HZ.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_
MARY_FACT_HZ
HIER_VR
PROJECT_COST_SUMMARY_FACT_H
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
MARY_FACT_HZ
PROJECT_COST_SUMMARY_FACT_H
Z.OBJ_ID=OBJECT_STATUS_HZ.OBJ_I
D
PROJECT_COST_SUM ORDER_OPERATION
MARY_FACT_HZ
ORDER_OPERATION.OPERATN_ROU
TING_ID=PROJECT_COST_SUMMARY
_FACT_HZ.OPERATN_ROUTING_ID
and
ORDER_OPERATION.OPERATN_SEQ_
ID=PROJECT_COST_SUMMARY_FACT
_HZ.OPERATN_SEQ_ID
PROJECT_COST_SUM PEGGING_OBJECT
MARY_FACT_HZ
PEGGING_OBJECT.OBJ_ID =
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
MARY_FACT_HZ
PLANT.PLANT_ID=PROJECT_COST_S
UMMARY_FACT_HZ.PLANT_ID
104
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Project Cost
Fact Table
Dimension Table
PROJECT_COST_SUM PROFIT_CENTER
MARY_FACT_HZ
Join Expression
PROJECT_COST_SUMMARY_FACT_H
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
PROJECT_COST_SUMMARY_FACT_H
Z.PROFIT_CNTR_ID=PROFIT_CENTER
_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
PROJECT_COST_SUMMARY_FACT_H
Z.PROFIT_CNTR_ID=PROFIT_CENTER
_HIER_VR.CHILD_ID
PROJECT_COST_SUM PROGRESS_MEASUR PROGRESS_MEASURE_METHOD.OBJ
MARY_FACT_HZ
E_METHOD
_ID =
PROJECT_COST_SUMMARY_FACT_H
Z.OBJ_ID and
PROGRESS_MEASURE_METHOD.PR
OGRESS_VERSION_FULL_NAME =
@Prompt('Progress Version Full
Name:','A','Progress Measure
Method\Progress Version Full
Name',Mono,Free,Persistent,,User:0)
PROJECT_COST_SUM PROJECT
MARY_FACT_HZ
PROJECT_COST_SUMMARY_FACT_H
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
MARY_FACT_HZ
PROJECT_COST_SUMMARY_FACT_H
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
105
4
4
Reports
Project Cost
Fact Table
Dimension Table
Join Expression
PROJECT_COST_SUM PURCH_ORGANIZATI
MARY_FACT_HZ
ON
PURCH_ORGANIZATION.PURCH_ORG
_ID=PROJECT_COST_SUMMARY_FAC
T_HZ.PURCH_ORG_ID
PROJECT_COST_SUM VALUATION_AREA
MARY_FACT_HZ
VALUATION_AREA.VALUATN_AREA_ID
=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
OBJECT_STATUS_HZ
OBJECT_STATUS
OBJECT_STATUS_HZ.OBJ_ID=OBJEC
T_STATUS.OBJ_ID
PROJECT_COST_SUM BUSINESS_ACTIVITY
MARY_FACT_VR
BUSINESS_ACTIVITY.BUS_ACTIVITY_I
D=PROJECT_COST_SUMMARY_FACT
_VR.BUS_ACTIVITY_ID
PROJECT_COST_SUM BUSINESS_AREA
MARY_FACT_VR
BUSINESS_AREA.BUS_AREA_ID=PRO
JECT_COST_SUMMARY_FACT_VR.BU
S_AREA_ID
PROJECT_COST_SUM COMPANY_CODE
MARY_FACT_VR
COMPANY_CODE.CMPNY_CODE_ID=
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
PROJECT_COST_SUM CURRENCY
MARY_FACT_VR
CURRENCY.CURR_ID=PROJECT_COS
T_SUMMARY_FACT_VR.CURR_ID_LO
C
PROJECT_COST_SUM CURRENCY
MARY_FACT_VR
CURRENCY.CURR_ID=PROJECT_COS
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
106
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Project Cost
Fact Table
Dimension Table
Join Expression
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
MARY_FACT_VR
FINANCING_CODE.FIN_MGMT_AREA_
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
MARY_FACT_VR
PROJECT_COST_SUMMARY_FACT_V
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
MARY_FACT_VR
PROJECT_COST_SUMMARY_FACT_V
R.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_
MARY_FACT_VR
HIER_HZ
PROJECT_COST_SUMMARY_FACT_V
R.FUNCTNL_AREA_ID=FUNCTIONAL_
AREA_HIER_HZ.FUNCTNL_AREA_ID
PROJECT_COST_SUM FUNCTIONAL_AREA_
MARY_FACT_VR
HIER_VR
PROJECT_COST_SUMMARY_FACT_V
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
MARY_FACT_VR
PROJECT_COST_SUMMARY_FACT_V
R.OBJ_ID=OBJECT_STATUS_HZ.OBJ_I
D
PROJECT_COST_SUM ORDER_OPERATION
MARY_FACT_VR
ORDER_OPERATION.OPERATN_ROU
TING_ID=PROJECT_COST_SUMMARY
_FACT_VR.OPERATN_ROUTING_ID
and
ORDER_OPERATION.OPERATN_SEQ_
ID=PROJECT_COST_SUMMARY_FACT
_VR.OPERATN_SEQ_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
107
4
4
Reports
Project Cost
Fact Table
Dimension Table
Join Expression
PROJECT_COST_SUM PEGGING_OBJECT
MARY_FACT_VR
PEGGING_OBJECT.OBJ_ID =
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
Name',Mono,Free,Persistent,,User:0)
PROJECT_COST_SUM PLANT
MARY_FACT_VR
PLANT.PLANT_ID=PROJECT_COST_S
UMMARY_FACT_VR.PLANT_ID
PROJECT_COST_SUM PROFIT_CENTER
MARY_FACT_VR
PROJECT_COST_SUMMARY_FACT_V
R.CTRL_AREA_ID=PROFIT_CENTER.C
TRL_AREA_ID and
PROJECT_COST_SUMMARY_FACT_V
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
PROJECT_COST_SUMMARY_FACT_V
R.PROFIT_CNTR_ID=PROFIT_CENTE
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
PROJECT_COST_SUMMARY_FACT_V
R.PROFIT_CNTR_ID=PROFIT_CENTE
R_HIER_VR.CHILD_ID
PROJECT_COST_SUM PROGRESS_MEASUR PROGRESS_MEASURE_METHOD.OBJ
MARY_FACT_VR
E_METHOD
_ID =
PROJECT_COST_SUMMARY_FACT_V
R.OBJ_ID and
PROGRESS_MEASURE_METHOD.PR
OGRESS_VERSION_FULL_NAME =
@Prompt('Progress Version Full
Name:','A','Progress Measure
Method\Progress Version Full
Name',Mono,Free,Persistent,,User:0)
PROJECT_COST_SUM PROJECT
MARY_FACT_VR
108
PROJECT_COST_SUMMARY_FACT_V
R.PROJ_ID=PROJECT.PROJ_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
PRT Assignment
Fact Table
Dimension Table
Join Expression
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
MARY_FACT_VR
PROJECT_COST_SUMMARY_FACT_V
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
MARY_FACT_VR
ON
PURCH_ORGANIZATION.PURCH_ORG
_ID=PROJECT_COST_SUMMARY_FAC
T_VR.PURCH_ORG_ID
PROJECT_COST_SUM VALUATION_AREA
MARY_FACT_VR
VALUATION_AREA.VALUATN_AREA_ID
=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
Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 27 for master reports.
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
of the reports included here for analysis:
•
•
PRT Assignment Listing
PRT Details
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
109
4
4
Reports
PRT Assignment
PRT Assignment Listing
View a listing of PRT assignments for the selected Operation Routing Id.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
PRT Details
View PRT details for the selected PRT (by PRT Name). Provides similar detail
as SAP transaction CF03.
110
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
PRT Assignment
Basic Data
View basic PRT data including durations, dates, location and project
grouping..
Defaults
View formulas, groupings, and general data.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
111
4
4
Reports
PRT Assignment
Recommended Table Joins
To analyze PRT Assignment data you will need to create joins between the fact
and dimension tables as follows:
Fact Table
Dimension Table
MATERIAL
PRODUCT_HIERARCH MATERIAL.PROD_HIER_ID=PRODUCT
Y
_HIERARCHY.PROD_HIER_ID
OBJECT_STATUS_HZ
OBJECT_STATUS
OBJECT_STATUS_HZ.OBJ_ID=OBJEC
T_STATUS.OBJ_ID
PRT_ASSIGNMENT_F
ACT
ACTIVITY
PRT_ASSIGNMENT_FACT.ACTIVITY_I
D=ACTIVITY.ACTIVITY_ID and
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=ACTIVITY.CTRL_AREA_ID
PRT_ASSIGNMENT_F
ACT
ACTIVITY_HIER_HZ
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=ACTIVITY_HIER_HZ.CTRL_AREA_
ID and
PRT_ASSIGNMENT_FACT.ACTIVITY_I
D=ACTIVITY_HIER_HZ.ACTIVITY_ID
PRT_ASSIGNMENT_F
ACT
ACTIVITY_HIER_VR
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID =
ACTIVITY_HIER_VR.CTRL_AREA_ID
and
PRT_ASSIGNMENT_FACT.ACTIVITY_I
D = ACTIVITY_HIER_VR.CHILD_ID
PRT_ASSIGNMENT_F
ACT
BUSINESS_AREA
BUSINESS_AREA.BUS_AREA_ID=PRT
_ASSIGNMENT_FACT.BUS_AREA_ID
PRT_ASSIGNMENT_F
ACT
CHART_OF_ACCOUN
TS
CHART_OF_ACCOUNTS.CHART_OF_
ACCT_ID=PRT_ASSIGNMENT_FACT.C
HART_OF_ACCT_ID
PRT_ASSIGNMENT_F
ACT
COMPANY_CODE
COMPANY_CODE.CMPNY_CODE_ID=
PRT_ASSIGNMENT_FACT.CMPNY_CO
DE_ID
PRT_ASSIGNMENT_F
ACT
CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID
=PRT_ASSIGNMENT_FACT.CTRL_ARE
A_ID
PRT_ASSIGNMENT_F
ACT
COST_CENTER
112
Join Expression
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=COST_CENTER.CTRL_AREA_ID
AND
PRT_ASSIGNMENT_FACT.COST_CNT
R_ID=COST_CENTER.COST_CNTR_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
PRT Assignment
Fact Table
Dimension Table
Join Expression
PRT_ASSIGNMENT_F
ACT
COST_CENTER_HIER
_HZ
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=COST_CENTER_HIER_HZ.CTRL_
AREA_ID and
PRT_ASSIGNMENT_FACT.COST_CNT
R_ID=COST_CENTER_HIER_HZ.COST
_CNTR_ID
PRT_ASSIGNMENT_F
ACT
COST_CENTER_HIER
_VR
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=COST_CENTER_HIER_VR.CTRL_
AREA_ID and
PRT_ASSIGNMENT_FACT.COST_CNT
R_ID=COST_CENTER_HIER_VR.CHIL
D_ID
PRT_ASSIGNMENT_F
ACT
COST_ELEMENT
PRT_ASSIGNMENT_FACT.CHART_OF_
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
ACT
COST_ELEMENT_HIE
R_HZ
PRT_ASSIGNMENT_FACT.COST_ELE
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
ACT
COST_ELEMENT_HIE
R_VR
PRT_ASSIGNMENT_FACT.CHART_OF_
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
ACT
FUNCTIONAL_AREA
PRT_ASSIGNMENT_FACT.FUNCTNL_A
REA_ID=FUNCTIONAL_AREA.FUNCTN
L_AREA_ID
PRT_ASSIGNMENT_F
ACT
FUNCTIONAL_AREA_
HIER_HZ
PRT_ASSIGNMENT_FACT.FUNCTNL_A
REA_ID=FUNCTIONAL_AREA_HIER_H
Z.FUNCTNL_AREA_ID
PRT_ASSIGNMENT_F
ACT
FUNCTIONAL_AREA_
HIER_VR
PRT_ASSIGNMENT_FACT.FUNCTNL_A
REA_ID=FUNCTIONAL_AREA_HIER_V
R.CHILD_ID
PRT_ASSIGNMENT_F
ACT
INTERNAL_ORDER
PRT_ASSIGNMENT_FACT.INTERNAL_
ORDER_ID=INTERNAL_ORDER.INTER
NAL_ORDER_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
113
4
4
Reports
PRT Assignment
Fact Table
Dimension Table
PRT_ASSIGNMENT_F
ACT
INTERNAL_ORDER_HI PRT_ASSIGNMENT_FACT.INTERNAL_
ER_HZ
ORDER_ID=INTERNAL_ORDER_HIER_
HZ.INTERNAL_ORDER_ID
PRT_ASSIGNMENT_F
ACT
INTERNAL_ORDER_HI PRT_ASSIGNMENT_FACT.INTERNAL_
ER_VR
ORDER_ID=INTERNAL_ORDER_HIER_
VR.CHILD_ID
PRT_ASSIGNMENT_F
ACT
MATERIAL
PRT_ASSIGNMENT_FACT.MATERIAL_I
D=MATERIAL.MATERIAL_ID
PRT_ASSIGNMENT_F
ACT
MRP_CONTROLLER
PRT_ASSIGNMENT_FACT.MRP_CTRLL
ER_ID=MRP_CONTROLLER.MRP_CTR
LLER_ID and
PRT_ASSIGNMENT_FACT.PLANT_ID=
MRP_CONTROLLER.PLANT_ID
PRT_ASSIGNMENT_F
ACT
OBJECT_NUMBER_TY PRT_ASSIGNMENT_FACT.OBJ_NUM_T
PE
YPE_ID =
OBJECT_NUMBER_TYPE.OBJ_NUM_T
YPE_ID
PRT_ASSIGNMENT_F
ACT
OBJECT_STATUS_HZ
PRT_ASSIGNMENT_FACT.OBJ_ID=OB
JECT_STATUS_HZ.OBJ_ID
PRT_ASSIGNMENT_F
ACT
OBJECT_TYPE
PRT_ASSIGNMENT_FACT.OBJ_TYPE_I
D = OBJECT_TYPE.OBJ_TYPE_ID AND
PRT_ASSIGNMENT_FACT.DIM_SRC_I
D_OBJTYP =
OBJECT_TYPE.OBJ_TYPE_ID
PRT_ASSIGNMENT_F
ACT
ORDER_OPERATION
ORDER_OPERATION.OPERATN_ROU
TING_ID=PRT_ASSIGNMENT_FACT.O
PERATN_ROUTING_ID and
ORDER_OPERATION.OPERATN_SEQ_
ID=PRT_ASSIGNMENT_FACT.OPERAT
N_SEQ_ID
PRT_ASSIGNMENT_F
ACT
PLANT
PLANT.PLANT_ID=PRT_ASSIGNMENT
_FACT.PLANT_ID
PRT_ASSIGNMENT_F
ACT
PLANT_LOCATION
PLANT_LOCATION.PLANT_ID=PRT_AS
SIGNMENT_FACT.PLANT_ID AND
PLANT_LOCATION.LOCATN_ID=PRT_
ASSIGNMENT_FACT.LOCATN_ID
114
Join Expression
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
PRT Assignment
Fact Table
Dimension Table
Join Expression
PRT_ASSIGNMENT_F
ACT
PROFIT_CENTER
PRT_ASSIGNMENT_FACT.CTRL_AREA
_ID=PROFIT_CENTER.CTRL_AREA_ID
and
PRT_ASSIGNMENT_FACT.PROFIT_CN
TR_ID=PROFIT_CENTER.PROFIT_CNT
R_ID
PRT_ASSIGNMENT_F
ACT
PROFIT_CENTER_HIE PRT_ASSIGNMENT_FACT.CTRL_AREA
R_HZ
_ID=PROFIT_CENTER_HIER_HZ.CTRL
_AREA_ID and
PRT_ASSIGNMENT_FACT.PROFIT_CN
TR_ID=PROFIT_CENTER_HIER_HZ.PR
OFIT_CNTR_ID
PRT_ASSIGNMENT_F
ACT
PROFIT_CENTER_HIE PRT_ASSIGNMENT_FACT.CTRL_AREA
R_VR
_ID=PROFIT_CENTER_HIER_VR.CTRL
_AREA_ID and
PRT_ASSIGNMENT_FACT.PROFIT_CN
TR_ID=PROFIT_CENTER_HIER_VR.C
HILD_ID
PRT_ASSIGNMENT_F
ACT
PROJECT
PRT_ASSIGNMENT_FACT.PROJ_ID=P
ROJECT.PROJ_ID
PRT_ASSIGNMENT_F
ACT
PROJECT_ELEMENT
PRT_ASSIGNMENT_FACT.PROJ_ELEM
_ID=PROJECT_ELEMENT.PROJ_ELEM
_ID
PRT_ASSIGNMENT_F
ACT
PROJECT_ELEMENT_ PRT_ASSIGNMENT_FACT.PROJ_ELEM
HIER_HZ
_ID=PROJECT_ELEMENT_HIER_HZ.P
ROJ_ELEM_ID
PRT_ASSIGNMENT_F
ACT
PROJECT_ELEMENT_ PRT_ASSIGNMENT_FACT.PROJ_ELEM
HIER_VR
_ID=PROJECT_ELEMENT_HIER_VR.C
HILD_ID
PRT_ASSIGNMENT_F
ACT
PRT_CATEGORY
PRT_ASSIGNMENT_F
ACT
PRT_GROUPING_KEY PRT_ASSIGNMENT_FACT.GROUPNG_
KEY_ID_01 =
PRT_GROUPING_KEY.GROUPNG_KE
Y_ID
PRT_ASSIGNMENT_F
ACT
PRT_MASTER
PRT_ASSIGNMENT_FACT.PRT_ID =
PRT_MASTER.PRT_ID
PRT_ASSIGNMENT_F
ACT
PRT_STATUS
PRT_ASSIGNMENT_FACT.PRT_STATU
S_ID = PRT_STATUS.PRT_STATUS_ID
PRT_ASSIGNMENT_FACT.PRT_CATEG
_ID = PRT_CATEGORY.PRT_CATEG_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
115
4
4
Reports
PRT Assignment
Fact Table
Dimension Table
Join Expression
PRT_ASSIGNMENT_F
ACT
PURCH_ORGANIZATI
ON
PURCH_ORGANIZATION.PURCH_ORG
_ID=PRT_ASSIGNMENT_FACT.PURCH
_ORG_ID
PRT_ASSIGNMENT_F
ACT
REFERENCE_DATE_K PRT_ASSIGNMENT_FACT.DATE_KEY_
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
ACT
ROUTING
ROUTING.ROUTING_ID=PRT_ASSIGN
MENT_FACT.ROUTING_ID
PRT_ASSIGNMENT_F
ACT
ROUTING_OPERATIO
N
ROUTING_OPERATION.GROUP_TYPE
_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
ACT
ROUTING_SEQUENCE ROUTING_SEQUENCE.ROUTING_ID =
PRT_ASSIGNMENT_FACT.ROUTING_I
D AND
ROUTING_SEQUENCE.GROUP_LINE_I
D=
PRT_ASSIGNMENT_FACT.GROUP_LIN
E_ID
PRT_ASSIGNMENT_F
ACT
STANDARD_TEXT_KE STANDARD_TEXT_KEY.STD_TEXT_KE
Y
Y_ID=PRT_ASSIGNMENT_FACT.STD_
TEXT_KEY_ID
PRT_ASSIGNMENT_F
ACT
STORAGE_LOCATION STORAGE_LOCATION.STORAGE_LOC
ATN_ID=PRT_ASSIGNMENT_FACT.ST
ORAGE_LOCATN_ID
PRT_ASSIGNMENT_F
ACT
TASK_LIST_TYPE
TASK_LIST_TYPE.GROUP_TYPE_ID=P
RT_ASSIGNMENT_FACT.GROUP_TYP
E_ID
PRT_ASSIGNMENT_F
ACT
TIME_DIM
TIME_DIM.CALENDAR_DATE=PRT_AS
SIGNMENT_FACT.CREATE_DATE
PRT_ASSIGNMENT_F
ACT
UNIT_OF_MEASURE
UNIT_OF_MEASURE.UOM_ID=PRT_A
SSIGNMENT_FACT.UOM_ID_DURTN
116
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Order Operation
Fact Table
Dimension Table
Join Expression
PRT_ASSIGNMENT_F
ACT
VALUATION_AREA
VALUATION_AREA.VALUATN_AREA_ID
=PRT_ASSIGNMENT_FACT.VALUATN_
AREA_ID
PRT_ASSIGNMENT_F
ACT
WORK_CENTER
PRT_ASSIGNMENT_FACT.PLANT_ID=
WORK_CENTER.PLANT_ID and
PRT_ASSIGNMENT_FACT.WORK_CNT
R_ID=WORK_CENTER.WORK_CNTR_I
D
PRT_ASSIGNMENT_F
ACT
WORK_CENTER_CAT
EGORY
PRT_ASSIGNMENT_FACT.WORK_CNT
R_CATEG_ID=WORK_CENTER_CATE
GORY.WORK_CNTR_CATEG_ID
PRT_ASSIGNMENT_F
ACT
WORK_CENTER_FOR PRT_ASSIGNMENT_FACT.FORMULA_I
MULA
D_PRT_QTY=WORK_CENTER_FORM
ULA.FORMULA_ID
PRT_ASSIGNMENT_F
ACT
WORK_CENTER_HIER PRT_ASSIGNMENT_FACT.WORK_CNT
_HZ
R_ID=WORK_CENTER_HIER_HZ.WOR
K_CNTR_ID and
PRT_ASSIGNMENT_FACT.PLANT_ID=
WORK_CENTER_HIER_HZ.PLANT_ID
PRT_ASSIGNMENT_F
ACT
WORK_CENTER_HIER PRT_ASSIGNMENT_FACT.WORK_CNT
_VR
R_ID=WORK_CENTER_HIER_VR.CHIL
D_ID AND
PRT_ASSIGNMENT_FACT.PLANT_ID=
WORK_CENTER_HIER_VR.PLANT_ID
WORK_CENTER_FOR FORMULA_PARAMET
MULA
ER
WORK_CENTER_FORMULA.PARAMET
ER_ID_01=FORMULA_PARAMETER.PA
RAMETER_ID
Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 27 for master reports.
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
117
4
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.
118
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Order Operation
Activity Data
View Activity listing by Project Element and Work Center..
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Recommended Table Joins
To analyze Order Operation data you will need to create joins between the fact
and dimension tables as follows:
Fact Table
Dimension Table
Join Expression
OBJECT_STATUS_HZ
OBJECT_STATUS
OBJECT_STATUS_HZ.OBJ_ID=OBJEC
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 =
ACTIVITY_HIER_VR.CHILD_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
119
4
4
Reports
Order Operation
Fact Table
Dimension Table
Join Expression
ORDER_OPERATION
BUSINESS_AREA
BUSINESS_AREA.BUS_AREA_ID=ORD
ER_OPERATION.BUS_AREA_ID
ORDER_OPERATION
CHART_OF_ACCOUN
TS
CHART_OF_ACCOUNTS.CHART_OF_
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
R_HZ
ORDER_OPERATION.COST_ELEM_ID
=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
R_VR
ORDER_OPERATION.CHART_OF_ACC
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_
HIER_HZ
ORDER_OPERATION.FUNCTNL_AREA
_ID=FUNCTIONAL_AREA_HIER_HZ.FU
NCTNL_AREA_ID
ORDER_OPERATION
FUNCTIONAL_AREA_
HIER_VR
ORDER_OPERATION.FUNCTNL_AREA
_ID=FUNCTIONAL_AREA_HIER_VR.C
HILD_ID
120
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
Order Operation
Fact Table
Dimension Table
Join Expression
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
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
ORDER_OPERATION.OPERATN_SEQ_
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
ORDER_OPERATION.OBJ_CLASS_ID
= OBJECT_CLASS.OBJ_CLASS_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
121
4
4
Reports
Order Operation
Fact Table
Dimension Table
ORDER_OPERATION
PROFIT_CENTER_HIE ORDER_OPERATION.CTRL_AREA_ID=
R_HZ
PROFIT_CENTER_HIER_HZ.CTRL_AR
EA_ID and
ORDER_OPERATION.PROFIT_CNTR_I
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
ORDER_OPERATION.PROFIT_CNTR_I
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
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
122
Join Expression
ROUTING.ROUTING_ID=ORDER_OPE
RATION.ROUTING_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data Reports
Fact Table
Dimension Table
Join Expression
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
Additional joins between dimension and hierarchy tables are shown in
“Recommended table joins” on page 27 for master reports.
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
123
4
4
Reports
SAP Master Data 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,
ACTIVITY_HIER_HR.LEVEL_1_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_2_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_3_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_4_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_5_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_6_FULLNAME,
124
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
125
4
4
Reports
SAP Master Data Reports
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
126
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data 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
All report SQL is located in the Rapid Mart installation directory under
"\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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
127
4
4
Reports
SAP Master Data Reports
Internal Order Hierarchy Data Discovery
View Internal Order Hierarchies for a specified Controlling Area, Parent
Internal Order, and Internal Order Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
128
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data Reports
Functional Area Hierarchy Data Discovery
View Functional Area Hierarchies for a specified Parent Functional Area and
Functional Area Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
129
4
4
Reports
SAP Master Data 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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
130
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data 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,
GL_ACCOUNT_HIER_HZ.LEVEL_1_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_2_FULLNAME,
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
131
4
4
Reports
SAP Master Data Reports
GL_ACCOUNT_HIER_HZ.LEVEL_3_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_4_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_5_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_6_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_7_FULLNAME,
FS_HIERARCHY_DISCOVERY_HZ.CREDIT_FLAG,
FS_HIERARCHY_DISCOVERY_HZ.DEBIT_FLAG,
FS_HIERARCHY_DISCOVERY_HZ.LOWER_ACCT_LIMIT,
FS_HIERARCHY_DISCOVERY_HZ.UPPER_ACCT_LIMIT,
GL_ACCOUNT_DISCOVERY_HZ.LEAF_FLAG,
GL_ACCOUNT_DISCOVERY_HZ.HIERARCHY_NAME
FROM
GL_ACCOUNT_HIER_HZ,
FS_HIERARCHY FS_HIERARCHY_DISCOVERY_HZ,
GL_ACCOUNT_HIER GL_ACCOUNT_DISCOVERY_HZ,
GL_ACCOUNT_MASTER
WHERE
(
GL_ACCOUNT_MASTER.CHART_OF_ACCTS_ID=GL_ACCOUNT_HIER_HZ.
CHART_OF_ACCTS_ID and
GL_ACCOUNT_MASTER.GL_ACCOUNT_ID=GL_ACCOUNT_HIER_HZ.CUR
RENT_LEAF AND
GL_ACCOUNT_MASTER.HIERARCHY_NAME in ('ACCOUNT','CAUS')
AND GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME = 'CAUS' )
AND (
GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=GL_ACCOUNT_DISCOVER
Y_HZ.HIERARCHY_NAME and
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=GL_ACCOUNT_DISCOVE
RY_HZ.CHART_OF_ACCTS_ID and
GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=GL_ACCOUNT_DISCOVERY_H
Z.CHILD_ID )
AND (
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=FS_HIERARCHY_DISCO
VERY_HZ.CHART_OF_ACCTS_ID and
GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=FS_HIERARCHY_DISCOVE
RY_HZ.FS_VERSION_ID and
GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=FS_HIERARCHY_DISCOVERY_
HZ.CHILD_ID )
AND
(
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID = 'CAUS'
AND
( GL_ACCOUNT_MASTER.HIERARCHY_NAME NOT IN ( '@PC', '@GL') )
AND
GL_ACCOUNT_HIER_HZ.LEVEL_2_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_1_ID
AND
GL_ACCOUNT_HIER_HZ.LEVEL_3_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_2_ID
AND
GL_ACCOUNT_HIER_HZ.LEVEL_4_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_3_ID
AND
GL_ACCOUNT_HIER_HZ.LEVEL_5_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_4_ID
)
132
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data Reports
Project Element Hierarchy Data Discovery
View Project Element Hierarchies for a specified Parent Project Element and
Project Element Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Equipment Hierarchy Data Discovery
View Equipment Hierarchies for a specified Parent Equipment and Equipment
Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
133
4
4
Reports
SAP Master Data Reports
Functional Location Hierarchy Data Discovery
View Functional Location Hierarchies for a specified Parent Functional
Location and Functional Location Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Work Center Hierarchy Data Discovery
View Work Center Hierarchies for a specified Parent Work Center and Work
Center Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
134
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data Reports
BOM Hierarchy Data Discovery
View BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
135
4
4
Reports
SAP Master Data Reports
Organization Unit Data Discovery
View Organization Unit Hierarchies for a specified Parent Organization
Unit(s).
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Position Data Discovery
View Position Hierarchies for the specified Parent Position(s).
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
136
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data 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,
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
137
4
4
Reports
SAP Master Data 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 =
ACTIVITY_HIER_VR.CHILD_ID
BILL_OF_MATERIALS
BILL_OF_MATERIALS_HIE
R_HZ
BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_
OF_MATERIALS_HIER_HZ.BOM_CATEG_ID
and
BILL_OF_MATERIALS.BOM_ID=BILL_OF_MAT
ERIALS_HIER_HZ.BOM_ID and
BILL_OF_MATERIALS.ALT_BOM_ID=BILL_OF_
MATERIALS_HIER_HZ.ALT_BOM_ID and
BILL_OF_MATERIALS.BOM_NODE_ID=BILL_O
F_MATERIALS_HIER_HZ.BOM_NODE_ID
BILL_OF_MATERIALS
BILL_OF_MATERIALS_HIE
R_VR
BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_
OF_MATERIALS_HIER_VR.BOM_CATEG_ID
and
BILL_OF_MATERIALS.BOM_ID=BILL_OF_MAT
ERIALS_HIER_VR.BOM_ID and
BILL_OF_MATERIALS.ALT_BOM_ID=BILL_OF_
MATERIALS_HIER_VR.ALT_BOM_ID and
BILL_OF_MATERIALS.BOM_NODE_ID=BILL_O
F_MATERIALS_HIER_VR.CHILD_ID
COST_CENTER
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
138
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data Reports
Dimension Table
Hierarchy Table
Join Text
COST_CENTER
COST_CENTER_HIER_VR
COST_CENTER.CTRL_AREA_ID=COST_CENT
ER_HIER_VR.CTRL_AREA_ID and
COST_CENTER.COST_CNTR_ID=COST_CEN
TER_HIER_VR.CHILD_ID
COST_ELEMENT
COST_ELEMENT_HIER_H
Z
COST_ELEMENT.COST_ELEM_ID=COST_ELE
MENT_HIER_HZ.COST_ELEM_ID and
COST_ELEMENT.CHART_OF_ACCT_ID=COST
_ELEMENT_HIER_HZ.CHART_OF_ACCT_ID
COST_ELEMENT
COST_ELEMENT_HIER_V
R
COST_ELEMENT.CHART_OF_ACCT_ID=COST
_ELEMENT_HIER_VR.CHART_OF_ACCT_ID
and
COST_ELEMENT.COST_ELEM_ID=COST_ELE
MENT_HIER_VR.CHILD_ID
COUNTRY_GROUP
COUNTRY_GROUP_STAT
US
COUNTRY_GROUP.COUNTRY_GRP_ID =
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
D=FS_HIERARCHY.CHART_OF_ACCT_ID and
GL_ACCOUNT_HIER_VR.HIER_ID=FS_HIERA
RCHY.FS_VERSION_ID and
GL_ACCOUNT_HIER_VR.CHILD_ID=FS_HIER
ARCHY.CHILD_ID
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU
_HZ
NCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA
_ID
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU
_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
FUNCTIONAL_LOCATION
FUNCTIONAL_LOCATION_ FUNCTIONAL_LOCATION.FUNCTNL_LOCATN
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
139
4
4
Reports
SAP Master Data Reports
Dimension Table
Hierarchy Table
Join Text
GL_ACCOUNT_HIER
GL_ACCOUNT_HIER_VR
GL_ACCOUNT_HIER_VR.HIER_ID=GL_ACCO
UNT_HIER.HIER_ID and
GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I
D=GL_ACCOUNT_HIER.CHART_OF_ACCT_ID
and
GL_ACCOUNT_HIER_VR.CHILD_ID=GL_ACC
OUNT_HIER.CHILD_ID
GL_ACCOUNT_MASTER
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
GL_ACCOUNT_MASTER.GL_ACCT_ID=GL_A
CCOUNT_HIER_VR.CHILD_ID AND
GL_ACCOUNT_MASTER.HIER_ID in
('ACCOUNT',@Prompt('Select GL Account
Hierarchy Code','A','GL Account\Hierarchy
Name',mono,free)) AND
GL_ACCOUNT_HIER_VR.HIER_ID =
@Prompt('Select GL Account Hierarchy
Code','A','GL Account Hierarchy Vr\Hierarchy
Name',mono,free)
INTERNAL_ORDER
INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN
HZ
TERNAL_ORDER_HIER_HZ.INTERNAL_ORDE
R_ID
INTERNAL_ORDER
INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN
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
METER
140
PAYROLL_PERIOD.PERIOD_PARAMETER_ID
=
PAYROLL_PERIOD_PARAMETER.PERIOD_PA
RAMETER_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Reports
SAP Master Data Reports
Dimension Table
Hierarchy Table
Join Text
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
R
PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C
ENTER_HIER_VR.CTRL_AREA_ID and
PROFIT_CENTER.PROFIT_CNTR_ID=PROFIT
_CENTER_HIER_VR.CHILD_ID
PROJECT_ELEMENT
PROJECT_ELEMENT_HIE
R_HZ
PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE
CT_ELEMENT_HIER_HZ.PROJ_ELEM_ID
PROJECT_ELEMENT
PROJECT_ELEMENT_HIE
R_VR
PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE
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
WORK_CENTER.PLANT_ID=WORK_CENTER_
HIER_VR.PLANT_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
141
4
4
Reports
SAP Master Data Reports
142
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Universe
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
The SAP BusinessObjects Project Systems Rapid Mart, version for SAP
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.
144
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Universe Design Principles
Universe Terminology
Star Schema: also called Subject Area. The dimensional data modeling
approach. A star schema has one large central table (fact table) and a set of
smaller attendant tables (dimension tables) displayed in a radial pattern
around the central table. Optionally, a hierarchy may be associated with a
dimension table. See diagram below for details
Dimension Table (Dim 1 - Dim 6): a table where the textual descriptions are
stored. Optionally, a Dimension may have an associated hierarchy - such as
Dim 6 in the diagram.
Hierarchy: A hierarchy is an ordered series of related objects. An example of
a hierarchy is time, or “date”, which may group objects as Year, Quarter, and
Month. You can use drill up or down to perform multi dimensional analysis
with a hierarchy. Hierarchies are described in great detail later in this chapter.
Fact Table: a table where the numerical measurements of the business are
stored. Each of these measurements is taken at the intersection of all the
dimensions. The fact table, if it represents a transactional table, might also
store some transaction descriptive attributes if there is no a proper dimension
for this attribute.
Fact tables can be detailed or summarized. These represent different levels
of granularity. A detailed fact table has a finer granularity, typically transaction
level detail. A summarized table aggregates the transaction data with fewer
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
145
5
5
Universe
Universe Design Principles
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.
146
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Universe Design Principles
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
147
5
5
Universe
Universe Design Principles
BACKLOG_FACT records are a subset of records in
SALES_ORDERS_FACT they share the same primary key (sales order
number, and sales order line item) and therefore the same granularity.
Inner Joins Only: The universe uses inner joins only. The Data Services job
loads a default row in each dimension table. The row is populated with the
default text (defined by a Data Services global variable) as primary key.
Example: We load a row with default text in the Material dimension. When a
financial document has no Material, we load that same default text as the
foreign key from the financial document to the Material table.
In this way we can avoid outer joins that can slow database performance.
Short Cut Joins: When a dimension is both joined to a fact table and also to
another dimension table we use a “short cut” join for the fact table join.
Example: In the diagram above the horizontal and vertical hierarchies are
joined both to the corresponding dimension (Dim 6) and the fact table. The
joins between hierarchy and dimension are short-cuts.
Complex Joins and Objects: In this scenario we use the @prompt() function
to allow users selecting appropriate constraints ar report run time.
Example: join between GL_ACCOUNT_MASTER and
GL_ACCOUNT_HIER_VR tables:
GL_ACCOUNT_MASTER.CHART_OF_ACCT_ID =
GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_ID and
GL_ACCOUNT_MASTER.GL_ACCT_ID =
GL_ACCOUNT_HIER_VR.CHILD_ID AND
GL_ACCOUNT_MASTER.HIER_ID in
('ACCOUNT',@Prompt('Select GL Account Hierarchy
Code','A','GL Account\Hierarchy Name',mono,free)) AND
GL_ACCOUNT_HIER_VR.HIER_ID = @Prompt('Select GL
Account Hierarchy Code','A','GL Account Hierarchy
Vr\Hierarchy Name',mono,free)
Default Coded Joins and Objects: This occurs when an object or join needs
to be restricted to certain values. A default code is introduced to restrict the
object to appropriate values.
Example: the “Line Debit Amt LOC” measure for Financial Documents. Here
the Debit / Credit indicator is restricted to “S” to ensure selection of only
“Debit” values:
SUM(Case when FINANCIAL_DOCUMENT_FACT.DR_CR_ID = 'S'
then FINANCIAL_DOCUMENT_FACT.AMT_LOC else 0 end)
148
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
Techniques
These are advanced technique objects developed for the Web Intelligence
reports.
•
Indexes: The index technique enables multiple measures to be returned
in a single data provider while providing different conditions for different
groups of measures.
For example, using indexes it is possible to return the total revenue,
revenue lost for returned items, and last 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
149
5
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
150
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
151
5
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.
152
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
153
5
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:
154
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
155
5
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.
156
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
157
5
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.
158
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
159
5
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.
160
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Hierarchies
Example: In the example below, “Activity 1" is both the parent and child of
“Activity 2”.
(as Parent)
Activity1
Activity2
Activity1
Activity4
Activity3
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
161
5
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.
162
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Project System Specific Hierarchies
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
163
5
5
Universe
SAP Project System 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:
•
•
•
•
164
Universe Objects & Classes
Common Dimensions
Milestone
Network Order
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
•
•
•
•
•
•
•
Network Relationship
Project Cost Summary (Horizontal)
Project Cost Summary (Vertical)
PRT Assignment
Order Operation
Filters & Techniques
Universe Validation
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
165
5
5
Universe
SAP Project System 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.
166
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
167
5
5
Universe
SAP Project System 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
168
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
169
5
5
Universe
SAP Project System 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.
170
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
171
5
5
Universe
SAP Project System 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.
172
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
173
5
5
Universe
SAP Project System 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.
174
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
175
5
5
Universe
SAP Project System 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-ofsales approach or the period accounting approach.
By analyzing the fixed capital as well, you can expand your profit centers for
use as investment centers.
PROJECT
A complex structure of tasks within a controlling area. It is used to control and
monitor the schedule, resources, capacities, cost, revenues, and funds
availability.
PROJECT ELEMENT (WBS)
Also called WBS (Work Breakdown Structure). Hierarchical outline of an
undertaking described in the project definition. The work breakdown structure
(WBS) forms the basis for the organization and coordination of a project.
A WBS consists of various WBS elements. The WBS elements describe
specific tasks or actions in the project to be carried out within a defined time
period.
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.
176
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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
A way of describing the link between the start and finish points of two
activities in a network or a standard network. Network relationship types
include the following:
•
•
•
•
SS relationship (Start - Start)
FF relationship (Finish - Finish)
SF relationship (Start - Finish)
FS relationship (Finish - Start)
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
177
5
5
Universe
SAP Project System 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.
178
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
179
5
5
Universe
SAP Project System 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
Table
MILESTONE
NETWORK ORDER
RELATION OPERA- SHIP
TION **
Acct
Assignment
Category
Activity &
Hierarchy
PRODUC- PROJECT
TION
COST
ORDER
SUMMARY
(Horizontal
)
X
X
X
X
Business
Activity
Business Area
Chart Of
Accounts
X
X
X
X
X
X
X
X
X
X
X
X
Control Key
X
X
X
Controlling
Area
X
X
X
Cost Center &
Hierarchy
X
X
X
X
X
X
X
X
Cost Object
Indicator
X
X
X
X
X
X
X
X
Document Type
Financial Mgmt
Area
180
X
X
X
Currency
X
X
X
Cost Element & X
Hierarchy
X
X
Company Code X
Document
Category
PROJECT PRT_
COST
ASSIGNSUMMARY MENT
(Vertical)
X
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Dimension
Table
MILESTONE
NETWORK ORDER
RELATION OPERA- SHIP
TION **
PRODUC- PROJECT
TION
COST
ORDER
SUMMARY
(Horizontal
)
PROJECT PRT_
COST
ASSIGNSUMMARY MENT
(Vertical)
Financial
Record
Category
X
X
Financial
Record Type
X
X
Financing Code
X
X
Fisc Period
X
Formula
Parameter
Functional Area
& Hierarchy
Internal Order
& Hierarchy
X
X
X
X
X
X
X
Internal Order
Status
X
Material
X
Material Batch
X
Material By
Plant
X
Material Group
X
Material Type
X
Milestone
Usage
X
X
X
X
X
X
Mrp Controller
X
Network Hier Vr
X
X
Network Profile X
X
X
Object Class
X
X
Object Number
Type
X
X
X
X
X
Object Status
X
X
X
X
X
X
Object Status
Hz
X
X
X
X
X
X
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
181
5
5
Universe
SAP Project System Universe
Dimension
Table
MILESTONE
NETWORK ORDER
RELATION OPERA- SHIP
TION **
Object Type
X
Operation
Suitability
X
Order
Operation
X
X
PRODUC- PROJECT
TION
COST
ORDER
SUMMARY
(Horizontal
)
X
X
Pegging Object
Plant
X
Plant Location
X
X
X
PROJECT PRT_
COST
ASSIGNSUMMARY MENT
(Vertical)
X
X
X
X
X
X
X
X
X
X
X
Product
Hierarchy
X
X
Production
Scheduler
X
Profit Center &
Hierarchy
X
X
X
Progress
Measure
Method
X
X
X
X
X
Project
X
X
X
X
X
X
X
Project
Element &
Hierarchy
X
X
X
X
X
X
X
Prt Category
X
Prt Grouping
Key
X
Prt Master
X
Prt Status
X
Purch
Organization
X
X
X
Reference Date X
Key
Relationship
Type
Routing
182
X
X
X
X
X
X
X
X
X
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Dimension
Table
MILESTONE
Routing
Operation
X
NETWORK ORDER
RELATION OPERA- SHIP
TION **
PRODUC- PROJECT
TION
COST
ORDER
SUMMARY
(Horizontal
)
PROJECT PRT_
COST
ASSIGNSUMMARY MENT
(Vertical)
X
Routing
Sequence
X
X
Service Person
X
Special
Procurement
Type
X
Standard Text
Key
Status Profile
X
X
Storage
Location
X
System
Condition
Task List Type
X
X
X
X
X
X
Task List Usage
X
Time Dim
X
X
X
X
Unit Of
Measure
X
X
X
X
X
X
Valuation Area
Variance
Category
Work Center &
Hierarchy
X
X
Work Center
Category
X
X
X
X
X
X
X
Work Center
Formula
X
X
X
X
** ORDER_OPERATION_FACT is included in the universe as an alias of
ORDER_OPERATION and constitutes a subject area in the universe.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
183
5
5
Universe
SAP Project System 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.
184
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Milestone
Milestones are used in the Project System to designate significant events or
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
185
5
5
Universe
SAP Project System 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:
186
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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
A network order is a special type of production order used for Projects in the
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
187
5
5
Universe
SAP Project System 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:
•
•
•
•
188
Network Order - Actual - actual duration measures
Network Order - Early - early duration measures
Network Order - Scheduled - scheduled duration measures
Network Order - Late - late duration measures
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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 subclasses:
•
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).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
189
5
5
Universe
SAP Project System Universe
Network Order Star Schema Layout
Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer
Network Relationship
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:
•
•
•
•
SS relationship (Start - Start)
FF relationship (Finish - Finish)
SF relationship (Start - Finish)
FS relationship (Finish - Start)
Read on for descriptions of Network Relationship classes in the SAP Project
System universe.
190
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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:
The following sub-classes are included to group like measures.
•
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
191
5
5
Universe
SAP Project System 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.
Network Relationship
Contains primary key elements for Network Relationships and the following
sub-classes:
192
•
Network Relationship - Additional Details (Ids) - the foreign keys to
the various associated dimensions
•
Network Relationship - Additional Details (Descriptive) - descriptive
attributes including the various “flags”
•
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).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Network Relationship Star Schema Layout
Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer.
Project Cost Summary (Horizontal)
Project Costing is used to plan, monitor, and control project costs, thereby
achieving comprehensive cost accounting. Here, cost data is represented in
horizontal format, or one row for each fiscal year with 16 columns for each
measure, one for each fiscal period in the year.
Read on for descriptions of Project Cost Summary (horizontal) classes in the
SAP Project System universe.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
193
5
5
Universe
SAP Project System 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:
The following sub-classes are included to group like measures.
•
Project Cost Sum - Hz Actual Measures - Actual cost measures
included in multiple currencies:
•
•
•
Project Cost Sum - Hz Actual Measures TRX - Transaction Currency
Project Cost Sum - Hz Budget Measures - Budget cost measures
included in multiple currencies:
•
•
194
Project Cost Sum - Hz Actual Measures LOC - Local Currency
Project Cost Sum - Hz Budget Measures LOC - Local Currency
Project Cost Sum - Hz Budget Measures TRX - Transaction
Currency
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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
following sub-classes:
•
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
Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
195
5
5
Universe
SAP Project System Universe
196
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Project Cost Summary (Vertical)
Project Costing is used to plan, monitor, and control project costs, thereby
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
measures for the single fiscal period.
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 semiadditive measures for Project Cost Summary (Vertical). They appear as
shown below in the universe:
The following sub-classes are included to group like measures.
•
Project Cost Sum - Vr Actual Measures - Actual cost measures
included in multiple currencies:
•
•
•
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
included in multiple currencies:
•
•
Project Cost Sum - Vr Budget Measures LOC - Local Currency
Project Cost Sum - Vr Budget Measures TRX - Transaction Currency
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
197
5
5
Universe
SAP Project System 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
following sub-classes:
198
•
Project Cost Sum Vr - Additional Details (Ids) - the foreign keys to the
various associated dimensions
•
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).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Project Cost Summary (Vertical) Star Schema Layout
Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer.
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
199
5
5
Universe
SAP Project System 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:
The following sub-classes are included to group like measures.
•
•
PRT Assignment - Qty Measures - quantities for PRT Assignment
PRT Assignment - Time Measures - time-related measures for PRT
Assignment, including the following sub-classes:
•
•
•
•
•
200
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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 subclasses:
•
PRT Assignment - Additional Details (Ids) - the foreign keys to the
various associated dimensions
•
PRT Assignment - Additional Details (Descriptive) - descriptive
attributes including the various “flags”
•
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).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
201
5
5
Universe
SAP Project System Universe
PRT Assignment Star Schema Layout
Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer
202
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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:
The following sub-classes are included to group like measures.
•
Order Operation - Currency TRX - Aggregated order operation costs,
including material cost, total cost, and price.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
203
5
5
Universe
SAP Project System 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 subclasses:
•
Order Operation - Additional Details (Ids) - the foreign keys to the
various associated dimensions
•
Order Operation - Additional Details (Descriptive) - descriptive
attributes including the various “flags”
•
Order Operation - Dates and Fiscal Periods - dates associated with
the Order Operation.
•
Order Operation - Values -
•
204
Order Operation - Transaction Currency Values - order operation
costs, including material cost, total cost, and price (no aggregation).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System Universe
Order Operation Star Schema Layout
Here is a graphical representation of the star schema for this subject area as
it appears in the universe designer.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
205
5
5
Universe
SAP Project System 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.
206
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Project System 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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
207
5
5
Universe
SAP Project System 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, SQLServer, and DB2 will have different messages for the same errors.
208
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
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
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
209
5
5
Universe
SAP Master Data Reports
Activity Hierarchy Data Discovery
View Activity Hierarchies for a specified Controlling Area, Parent Activity, and
Activity Hierarchy.
Report SQL
SELECT DISTINCT
ACTIVITY_HIER_HR.ACTIVITY_ID,
ACTIVITY_HIER_HR.CTRL_AREA_ID,
ACTIVITY_HIER_HR.LEAF_LEVEL,
ACTIVITY_HIER_HR.LEVEL_0_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_1_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_2_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_3_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_4_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_5_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_6_FULLNAME,
ACTIVITY_HIER_HR.LEVEL_7_FULLNAME
FROM
ACTIVITY_HIER_HR,
ACTIVITY_HIER_VR,
ACTIVITY
WHERE
( ACTIVITY.CTRL_AREA_ID = ACTIVITY_HIER_VR.CTRL_AREA_ID and
ACTIVITY.ACTIVITY_ID = ACTIVITY_HIER_VR.DESCENDANT_ID )
AND ( ACTIVITY.CTRL_AREA_ID=ACTIVITY_HIER_HR.CTRL_AREA_ID and
ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HR.ACTIVITY_ID )
AND
210
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
(
( ACTIVITY_HIER_VR.ANCESTOR_ID in ('A1') AND
ACTIVITY_HIER_HR.LEVEL_0_ID in ('A1') )
AND
ACTIVITY_HIER_HR.CTRL_AREA_ID = '1000'
AND
ACTIVITY_HIER_HR.CTRL_AREA_ID <> '?'
AND
ACTIVITY_HIER_HR.LEVEL_0_ID <> '?'
)
Cost Center Hierarchy Data Discovery
View Cost Center Hierarchies for a specified Controlling Area, Parent Cost
Center, and Cost Center Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
211
5
5
Universe
SAP Master Data 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
All report SQL is located in the Rapid Mart installation directory under
"\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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
212
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
Internal Order Hierarchy Data Discovery
View Internal Order Hierarchies for a specified Controlling Area, Parent
Internal Order, and Internal Order Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
213
5
5
Universe
SAP Master Data Reports
Functional Area Hierarchy Data Discovery
View Functional Area Hierarchies for a specified Parent Functional Area and
Functional Area Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
214
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data 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
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
215
5
5
Universe
SAP Master Data 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,
GL_ACCOUNT_HIER_HZ.LEVEL_1_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_2_FULLNAME,
216
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
GL_ACCOUNT_HIER_HZ.LEVEL_3_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_4_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_5_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_6_FULLNAME,
GL_ACCOUNT_HIER_HZ.LEVEL_7_FULLNAME,
FS_HIERARCHY_DISCOVERY_HZ.CREDIT_FLAG,
FS_HIERARCHY_DISCOVERY_HZ.DEBIT_FLAG,
FS_HIERARCHY_DISCOVERY_HZ.LOWER_ACCT_LIMIT,
FS_HIERARCHY_DISCOVERY_HZ.UPPER_ACCT_LIMIT,
GL_ACCOUNT_DISCOVERY_HZ.LEAF_FLAG,
GL_ACCOUNT_DISCOVERY_HZ.HIERARCHY_NAME
FROM
GL_ACCOUNT_HIER_HZ,
FS_HIERARCHY FS_HIERARCHY_DISCOVERY_HZ,
GL_ACCOUNT_HIER GL_ACCOUNT_DISCOVERY_HZ,
GL_ACCOUNT_MASTER
WHERE
(
GL_ACCOUNT_MASTER.CHART_OF_ACCTS_ID=GL_ACCOUNT_HIER_HZ.
CHART_OF_ACCTS_ID and
GL_ACCOUNT_MASTER.GL_ACCOUNT_ID=GL_ACCOUNT_HIER_HZ.CUR
RENT_LEAF AND
GL_ACCOUNT_MASTER.HIERARCHY_NAME in ('ACCOUNT','CAUS')
AND GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME = 'CAUS' )
AND (
GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=GL_ACCOUNT_DISCOVER
Y_HZ.HIERARCHY_NAME and
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=GL_ACCOUNT_DISCOVE
RY_HZ.CHART_OF_ACCTS_ID and
GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=GL_ACCOUNT_DISCOVERY_H
Z.CHILD_ID )
AND (
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID=FS_HIERARCHY_DISCO
VERY_HZ.CHART_OF_ACCTS_ID and
GL_ACCOUNT_HIER_HZ.HIERARCHY_NAME=FS_HIERARCHY_DISCOVE
RY_HZ.FS_VERSION_ID and
GL_ACCOUNT_HIER_HZ.CURRENT_LEAF=FS_HIERARCHY_DISCOVERY_
HZ.CHILD_ID )
AND
(
GL_ACCOUNT_HIER_HZ.CHART_OF_ACCTS_ID = 'CAUS'
AND
( GL_ACCOUNT_MASTER.HIERARCHY_NAME NOT IN ( '@PC', '@GL') )
AND
GL_ACCOUNT_HIER_HZ.LEVEL_2_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_1_ID
AND
GL_ACCOUNT_HIER_HZ.LEVEL_3_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_2_ID
AND
GL_ACCOUNT_HIER_HZ.LEVEL_4_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_3_ID
AND
GL_ACCOUNT_HIER_HZ.LEVEL_5_ID <>
GL_ACCOUNT_HIER_HZ.LEVEL_4_ID
)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
217
5
5
Universe
SAP Master Data Reports
Project Element Hierarchy Data Discovery
View Project Element Hierarchies for a specified Parent Project Element and
Project Element Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Equipment Hierarchy Data Discovery
View Equipment Hierarchies for a specified Parent Equipment and Equipment
Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
218
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
Functional Location Hierarchy Data Discovery
View Functional Location Hierarchies for a specified Parent Functional
Location and Functional Location Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Work Center Hierarchy Data Discovery
View Work Center Hierarchies for a specified Parent Work Center and Work
Center Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
219
5
5
Universe
SAP Master Data Reports
BOM Hierarchy Data Discovery
View BOM Hierarchies for a specified BOM Id and Parent BOM Hierarchy.
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
220
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
Organization Unit Data Discovery
View Organization Unit Hierarchies for a specified Parent Organization
Unit(s).
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
Position Data Discovery
View Position Hierarchies for the specified Parent Position(s).
Report SQL
All report SQL is located in the Rapid Mart installation directory under
"\Sample\DML".
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
221
5
5
Universe
SAP Master Data 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,
222
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data 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 =
ACTIVITY_HIER_VR.CHILD_ID
BILL_OF_MATERIALS
BILL_OF_MATERIALS_HIE
R_HZ
BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_
OF_MATERIALS_HIER_HZ.BOM_CATEG_ID
and
BILL_OF_MATERIALS.BOM_ID=BILL_OF_MAT
ERIALS_HIER_HZ.BOM_ID and
BILL_OF_MATERIALS.ALT_BOM_ID=BILL_OF_
MATERIALS_HIER_HZ.ALT_BOM_ID and
BILL_OF_MATERIALS.BOM_NODE_ID=BILL_O
F_MATERIALS_HIER_HZ.BOM_NODE_ID
BILL_OF_MATERIALS
BILL_OF_MATERIALS_HIE
R_VR
BILL_OF_MATERIALS.BOM_CATEG_ID=BILL_
OF_MATERIALS_HIER_VR.BOM_CATEG_ID
and
BILL_OF_MATERIALS.BOM_ID=BILL_OF_MAT
ERIALS_HIER_VR.BOM_ID and
BILL_OF_MATERIALS.ALT_BOM_ID=BILL_OF_
MATERIALS_HIER_VR.ALT_BOM_ID and
BILL_OF_MATERIALS.BOM_NODE_ID=BILL_O
F_MATERIALS_HIER_VR.CHILD_ID
COST_CENTER
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
223
5
5
Universe
SAP Master Data Reports
Dimension Table
Hierarchy Table
Join Text
COST_CENTER
COST_CENTER_HIER_VR
COST_CENTER.CTRL_AREA_ID=COST_CENT
ER_HIER_VR.CTRL_AREA_ID and
COST_CENTER.COST_CNTR_ID=COST_CEN
TER_HIER_VR.CHILD_ID
COST_ELEMENT
COST_ELEMENT_HIER_H
Z
COST_ELEMENT.COST_ELEM_ID=COST_ELE
MENT_HIER_HZ.COST_ELEM_ID and
COST_ELEMENT.CHART_OF_ACCT_ID=COST
_ELEMENT_HIER_HZ.CHART_OF_ACCT_ID
COST_ELEMENT
COST_ELEMENT_HIER_V
R
COST_ELEMENT.CHART_OF_ACCT_ID=COST
_ELEMENT_HIER_VR.CHART_OF_ACCT_ID
and
COST_ELEMENT.COST_ELEM_ID=COST_ELE
MENT_HIER_VR.CHILD_ID
COUNTRY_GROUP
COUNTRY_GROUP_STAT
US
COUNTRY_GROUP.COUNTRY_GRP_ID =
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
D=FS_HIERARCHY.CHART_OF_ACCT_ID and
GL_ACCOUNT_HIER_VR.HIER_ID=FS_HIERA
RCHY.FS_VERSION_ID and
GL_ACCOUNT_HIER_VR.CHILD_ID=FS_HIER
ARCHY.CHILD_ID
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU
_HZ
NCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA
_ID
FUNCTIONAL_AREA
FUNCTIONAL_AREA_HIER FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FU
_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
FUNCTIONAL_LOCATION
FUNCTIONAL_LOCATION_ FUNCTIONAL_LOCATION.FUNCTNL_LOCATN
HIER_VR
_ID=FUNCTIONAL_LOCATION_HIER_VR.CHIL
D_ID
GL_ACCOUNT_HIER
GL_ACCOUNT_HIER_HZ
224
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
SAP Master Data Reports
Dimension Table
Hierarchy Table
Join Text
GL_ACCOUNT_HIER
GL_ACCOUNT_HIER_VR
GL_ACCOUNT_HIER_VR.HIER_ID=GL_ACCO
UNT_HIER.HIER_ID and
GL_ACCOUNT_HIER_VR.CHART_OF_ACCT_I
D=GL_ACCOUNT_HIER.CHART_OF_ACCT_ID
and
GL_ACCOUNT_HIER_VR.CHILD_ID=GL_ACC
OUNT_HIER.CHILD_ID
GL_ACCOUNT_MASTER
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
GL_ACCOUNT_MASTER.GL_ACCT_ID=GL_A
CCOUNT_HIER_VR.CHILD_ID AND
GL_ACCOUNT_MASTER.HIER_ID in
('ACCOUNT',@Prompt('Select GL Account
Hierarchy Code','A','GL Account\Hierarchy
Name',mono,free)) AND
GL_ACCOUNT_HIER_VR.HIER_ID =
@Prompt('Select GL Account Hierarchy
Code','A','GL Account Hierarchy Vr\Hierarchy
Name',mono,free)
INTERNAL_ORDER
INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN
HZ
TERNAL_ORDER_HIER_HZ.INTERNAL_ORDE
R_ID
INTERNAL_ORDER
INTERNAL_ORDER_HIER_ INTERNAL_ORDER.INTERNAL_ORDER_ID=IN
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
METER
PAYROLL_PERIOD.PERIOD_PARAMETER_ID
=
PAYROLL_PERIOD_PARAMETER.PERIOD_PA
RAMETER_ID
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
225
5
5
Universe
SAP Master Data Reports
Dimension Table
Hierarchy Table
Join Text
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
R
PROFIT_CENTER.CTRL_AREA_ID=PROFIT_C
ENTER_HIER_VR.CTRL_AREA_ID and
PROFIT_CENTER.PROFIT_CNTR_ID=PROFIT
_CENTER_HIER_VR.CHILD_ID
PROJECT_ELEMENT
PROJECT_ELEMENT_HIE
R_HZ
PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE
CT_ELEMENT_HIER_HZ.PROJ_ELEM_ID
PROJECT_ELEMENT
PROJECT_ELEMENT_HIE
R_VR
PROJECT_ELEMENT.PROJ_ELEM_ID=PROJE
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
WORK_CENTER.PLANT_ID=WORK_CENTER_
HIER_VR.PLANT_ID
226
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Universe
Customizing the Universe
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:
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
•
•
•
•
•
•
5.
NETWORK_RELATIONSHIP_FACT
PROJECT_COST_SUMMARY_FACT_HZ
PROJECT_COST_SUMMARY_FACT_VR
PRT_ASSIGNMENT_FACT
ORDER_OPERATION_FACT
Delete these tables from the graphic representation of the universe:
•
•
•
•
•
•
6.
SAP Project - Milestones
NETWORK_ORDER_FACT
NETWORK_RELATIONSHIP_FACT
PROJECT_COST_SUMMARY_FACT_HZ
PROJECT_COST_SUMMARY_FACT_VR
PRT_ASSIGNMENT_FACT
ORDER_OPERATION_FACT
All joins associated with these tables will be deleted as you delete the
tables.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
227
5
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
NETWORK_RELATIONSHIP_FACT
ORDER_OPERATION_FACT
PRT_ASSIGNMENT_FACT
11. Validate and test the universe
228
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Installing the Rapid Mart
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
230
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
System Prerequisites
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
231
6
6
Installing the Rapid Mart
Personnel Prerequisites
Personnel Prerequisites
The Rapid Mart installation procedure is completely manual. There are many
intricacies. We recommend the team installing the Rapid Mart be fluent with
these SAP BusinessObjects products:
•
Data Services
•
•
•
•
Designer
Job Server
Web Administration
BusinessObjects Enterprise
•
•
Universe Designer
Web Intelligence Query Designer
For additional support we recommend expertise in:
•
•
232
SAP solutions Administration (BASIS)
Target Database DBA (Database Administration)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Rapid Mart product components
Rapid Mart product components
The Rapid Mart is delivered as a Zip file that includes all major product
components. These are organized as directories and sub-directories within
the zipped file. The main directories are:
• Data Model for the target database: This is an Integrated ERWin Data
Model of the complete target schema for all Rapid Marts related to SAP
solutions. The ERwin file is called:
•
SAP_Integrated_Model.erwin
The model is built with AllFusion ERwin Data Modeler Release: 7.2. If
you have ERwin release 7.2 or higher available, you can load the file and
use it to extend and customize the data model.
The model is used to generate SQL scripts for:
•
•
•
•
•
•
•
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
•
•
•
•
•
•
•
•
Creating Rapid Mart tables and views
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
233
6
6
Installing the Rapid Mart
Rapid Mart product components
•
Sample reporting SQL (DML): This is the SQL source statements
extracted from each of the sample Web Intelligence reports delivered
with the Rapid Mart. It also includes sample SQL (DDL) for suggested
database procedures.
•
Utilities (Rapid Mart Word Utility and Metadata Discovery Utility.)
Both Word Utility and Metadata Discovery Utility are metadata reporting
solutions designed to help you with the manual upgrade process and to
enforce pre-defined naming conventions when developing or customizing
Rapid Mart data model(s). It also provides better exposure of the data
model metadata details.
•
234
Visuals contains the Rapid Mart BIAR file (reporting content). These are
the sample Webi reports and universes (semantic layer) included with the
Rapid Mart.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Preparing your environment
Preparing your environment
Preparing Data Services
Follow these steps to prepare your environment for the Rapid Mart
installation:
•
Install SAP BusinessObjects Data Services XI 3.2 or higher, if it is not
already installed.
Refer to the Data Services Installation Guide for detailed installation
instructions.
Make sure that you install the Data Services Designer and that you install
and configure a Job Server and an Access Server. Though you need
Data Services job server to run Rapid Mart jobs, you need just Data
Services Designer to install Rapid Mart.
Create a separate repository for Rapid Mart(s) after the Data Services
installation using the Repository Manager. A Data Services repository is
required to install the Rapid Mart ETL job (ATL file). It is recommended to
import the ATL file(s) into an empty Data Services repository. Multiple
Rapid Marts can be installed in the same repository.
Make sure that the Job Server is associated to the repository. The
association sign in the right bottom corner of Data Services Designer
should be on:
If the association is inactive, the sign will have a red cross:
•
Start Data Services Designer and log on to the repository where you are
going to install the Rapid Mart.
This step ensures that your default connection is set appropriately.
•
Exit Data Services Designer.
Preparing Target Database Environment
Prepare your target database environment.
•
Currently the Rapid Mart supports Oracle, MS SQL Server, Teradata, and
DB2 as target databases.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
235
6
6
Installing the Rapid Mart
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:
•
•
•
•
236
Volume of data to be loaded, including growth rates
Physical disk layout and requirements
Network bandwidth
Frequency and duration of loads
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Preparing your environment
•
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
237
6
6
Installing the Rapid Mart
The Rapid Mart Package
The Rapid Mart Package
Download the Rapid Mart package.
Choose an appropriate location on your installation server and run unzip/
extract program to install the package. We recommend creating a
subdirectory called as the Rapid Mart name (example 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.
238
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Rapid Mart Target Schema
Install the Rapid Mart Target Schema
This section deals with the installation of the Rapid Mart target schema.The
schema installation is manual.
Create Target Schema
After you unzip the Rapid Mart package, to go the DataModel sub-directory.
You will find directories for each of the target databases supported:
•
•
•
•
Oracle
DB2
SQL Server
Teradata
Create the target schema using the files from the sub-directory for your target
database.
Note: The integrated data model includes the tables, views, and indexes
used by all Rapid Marts for SAP solutions. Thus, execute the set of scripts
only once when installing multiple Rapid Marts. The set of scripts is identical
in all Rapid Marts for SAP solutions.
Create Target Tables
In the appropriate target database directory locate the files:
•
•
SAP_Create_Tables.sql
SAP_Create_Comments.sql
As a quick start, execute the scripts in your target database. It will create all
database tables and views used by the Rapid Mart. Creating comments is
optional. It will ensure that Data Services will store tables and views with
descriptions in its repository after you re-import the tables and views.
Note: Please read notes below, and apply as needed:
1.
Use the results of Performance Tuning analysis to guide you in the
process of allocating storage space and physical disk location for your
tables You may want to modify the table create script to include these
parameters before execution.
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
239
6
6
Installing the Rapid Mart
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.
240
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Rapid Mart Target Schema
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
241
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
Install the Data Services Job(s)
This section deals with the installation of the Rapid Mart jobs using Data
Services Designer. Installation of reporting content is covered in “Installing
Rapid Mart Reporting Content” on page 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
242
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
Before Replace All
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
243
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
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.
244
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
•
From the Tools Menu choose Import From File:
•
Choose the ATL File
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
245
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
•
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:
246
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
Edit the Data Store:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
247
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
Open “Advanced” Edit Window
248
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
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):
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
249
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
Edit the Data Store:
250
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
Open “Advanced” Edit Window
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
251
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
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
252
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
253
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
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.
254
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
At this writing, only four Rapid Marts use ABAP files
•
•
SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions
•
SAP BusinessObjects Human Resources Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects Production Planning Rapid Mart, version for SAP
solutions
SAP BusinessObjects General Ledger Rapid Mart, version for SAP
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
255
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
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.
256
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
1.
Open Data Services and navigate to the Transforms tab of the Local
Object Library:
Note: This step applies only to:
•
SAP BusinessObjects Cost Center Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects Human Resources Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Production Planning Rapid Mart, version for
SAP solutions
For the rest of Rapid Marts, you will not see Custom ABAP transforms in
the Transforms tab.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
257
6
6
Installing the Rapid Mart
Install the Data Services Job(s)
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
•
258
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 “\”).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Install the Data Services Job(s)
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
259
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Installing Rapid Mart Reporting Content
Rapid Marts come with their own Reporting Content, supplied as Web
Intelligence reports and universes (semantic layer.) In order to use the
Reporting Content you must first install them to your BusinessObjects
Enterprise system and configure a connection to your Rapid Mart target
database.
If the BusinessObjects Enterprise server (CMS) is located on a different
machine, you need to have BusinessObjects Enterprise client installed, with
connectivity to that server.
The Reporting Content is delivered as a BIAR file, located in the unzipped
Visuals sub-directory:
•
•
Directory Path: ...\Visuals\
File Name: 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.
260
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
On the first screen, click “Next”:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
261
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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
262
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Choose CMS:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
263
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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.
264
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
265
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Check Import Scenario Radio Buttons as shown
Note: This screen does not appear in SAP BusinessObjects Enterprise XI
Release 2
266
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Incremental Import - Check or Uncheck Boxes:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
267
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Acknowledge Message, Click Next
268
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
“Select All” to import complete contents of BIAR file.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
269
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Universe & Connection Options- Check or Uncheck as shown
270
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
271
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Select Import Options for Publications:
Note: This screen does not appear in SAP BusinessObjects Enterprise XI
Release 2
272
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Acknowledge message, Click “Next”:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
273
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Verify Correct List of Objects to Import, Click FINISH to start import:
274
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
Wait for Import to Finish. Then Click “View Detail Log”:
Click on each item imported. Make sure there are no errors:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
275
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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).
276
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
277
6
6
Installing the Rapid Mart
Installing Rapid Mart Reporting Content
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.
278
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Using the Rapid Mart
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.
280
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Recovery framework
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
281
7
7
Using the Rapid Mart
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.
282
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Execution status framework
How job status is maintained
The Rapid Mart records a job status for each invocation of a particular job.
There are three possible values for job status:
•
•
None — The job status is none when the job has never been executed.
•
Done — Job status is set to done when a job completes successfully.
Started — Job status is set to started when a new invocation of a job
starts.
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
283
7
7
Using the Rapid Mart
Extraction, transformation and loading process
•
Checks the last execution status of the job.
If the job status is done, the function sets EXTRACTLOW to the
previous value of EXTRACTHIGH, the last successful end date;
next, the function sets EXTRACTHIGH to the value of $G_EDATE,
which you set in the initialization script. The function returns the
values in EXTRACTLOW and EXTRACTHIGH and the Rapid Mart
uses these values to update $G_SDATE and $G_EDATE.
If the job status is started, the function does not change the value of
EXTRACTLOW. Instead, this value remains the end date of the last
successful execution. The function does change EXTRACTHIGH to
the new value set in $G_EDATE. The function returns the
EXTRACTLOW and EXTRACTHIGH values, and the Rapid Mart
uses these values to update $G_SDATE and $G_EDATE.
•
AW_EndJob(job name)
The EndJob script calls this function to change the job status value in the
AW_JOBEXECUTION table to done when the job executes successfully.
Executing a job with the Reset option
You can use the reset mode to force the Rapid Mart to assign a new starting
extract time for data extracts. Use reset mode to force the starting and ending
dates (global variables $G_SDATE and $G_EDATE) to remain the same as
the values you set set in the initialization script or job properties.
Note: Using this option may cause gaps in the time sequence of data loaded
into target tables.
To specify reset mode, edit the 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:
284
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Extraction, transformation and loading process
•
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
285
7
7
Using the Rapid Mart
Global Variables
properties window. Thus, you can preserve the “as shipped” values for
reference in the properties window, while still using your own values as
set in the initialization script.
•
•
Sections that load a set of tables you can use to analyze and report on a
particular Subject Area in the Rapid Mart. A section consists of:
•
A work flow that loads the reporting dimensions applicable to the
subject area.
•
Work flows that load holding tables, intermediate tables, and auxiliary
tables that support loading the main subject area tables. Some of
these flows might be reusable components, which can be
incorporated into multiple sections of Rapid Marts. Components
have the “execute once” feature enabled.
•
A conditional object that determines whether the job executes the
initial or incremental loading logic.
•
Work flows that load the main tables for the subject area. These
tables are generally called “fact” tables in relational modeling
terminology. A section loads a single fact table and any additional
fact tables that depend on it. For example, an order analysis section
might load an order table and an order summary table.
A final script that updates the job execution status table
Global Variables
All Rapid Mart jobs use a standardized set of Global Variables. For
completeness, and multiple Rapid Mart integration. They are included with
each Rapid Mart job, regardless if they are used by the job.
Global Variable Cross-Reference
A complete Cross-Reference Matrix of Global Variables is shown below. It is
organized in three sections grouped by how many Rapid Marts use each
Global Variable:
•
•
•
286
Used in All Rapid Marts
Used in 2 to 10 Rapid Marts
Used in Only 1 Rapid Mart
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
The global variables in each of these sections are described in detail after the
matrix.
Global Variable Name
Data
Type
AP AR CA GL HR
IA
PM PP PR PS SA
Used in all 11 Rapid Marts
$G_CCODE
varchar(4)
X
X
X
X
X
X
X
X
X
X
X
$G_DEFAULT_DATE
datetime
X
X
X
X
X
X
X
X
X
X
X
$G_DEFAULT_NUMBER
int
X
X
X
X
X
X
X
X
X
X
X
$G_DEFAULT_TEXT
varchar(1)
X
X
X
X
X
X
X
X
X
X
X
$G_EDATE
datetime
X
X
X
X
X
X
X
X
X
X
X
$G_LANGUAGE
varchar(1)
X
X
X
X
X
X
X
X
X
X
X
$G_LOAD_DATE
datetime
X
X
X
X
X
X
X
X
X
X
X
$G_LOAD_TIME
varchar(8)
X
X
X
X
X
X
X
X
X
X
X
$G_LOAD_TYPE
varchar(7)
X
X
X
X
X
X
X
X
X
X
X
$G_MAX_DATE
datetime
X
X
X
X
X
X
X
X
X
X
X
$G_REBUILD_INDEXES
varchar(1)
X
X
X
X
X
X
X
X
X
X
X
$G_RUN_MODE
varchar(10)
X
X
X
X
X
X
X
X
X
X
X
$G_SDATE
datetime
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Used in 2 to 10 Rapid Marts
$A
int
$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
TE
datetime
X
X
$G_ENDFISCALYEAR
int
X
X
X
X
X
X
$G_EXCHANGE_TYPE_ID
varchar(4)
X
X
X
$G_GLOBAL_CURRENCY
varchar(5)
X
X
X
$G_INT_ORDER_CATEG_P
P
varchar(2)
X
X
$G_INT_ORDER_CATEG_P
S
varchar(2)
X
X
$G_ORIG_SDATE
datetime
X
X
$G_STARTFISCALYEAR
int
X
X
X
X
X
X
X
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
287
7
7
Using the Rapid Mart
Global Variables
Global Variable Name
Data
Type
AP AR CA GL HR
IA
PM PP PR PS SA
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
GER_ID
varchar(2)
$G_COUNTRY_GRP
varchar(2)
X
X
$G_DEL_PERIOD
datetime
X
$G_DEL_REJECT_REASON
varchar(2)
X
$G_DROP_SHIP
varchar(1)
$G_GL_ACCOUNT_HIER_N
AME
varchar(10)
X
X
$G_GL_SUM_PLAN_LEDGE varchar(2)
R_ID
X
$G_GL_VERSION
varchar(3)
X
$G_HIRE_ACTION_01
varchar(2)
X
$G_HIRE_ACTION_02
varchar(2)
X
$G_HIRE_ACTION_03
varchar(2)
X
$G_INIT_HIST_CHG
varchar(1)
X
$G_MALFUNCTION_CAUSE varchar(20)
X
$G_MALFUNCTION_DAMAG varchar(20)
E
X
$G_MALFUNCTION_OBJ_P
ART
varchar(20)
X
$G_MRP_RESULTS_DELET
E
varchar(1)
X
$G_ONTIME_DELIV_WINDO int
W
X
$G_PC_ACCOUNT_HIER_N
AME
varchar(10)
X
$G_PROFIT_CENTER_LED
GER_ID
varchar(2)
X
$G_REHIRE_ACTION_01
varchar(2)
X
$G_REHIRE_ACTION_02
varchar(2)
X
$G_RETIRE_ACTION
varchar(2)
X
$G_SAP_VERSION
int
$G_SCHOOL_TYPE
varchar(2)
288
X
X
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
Global Variable Name
Data
Type
AP AR CA GL HR
$G_SERVICE_INTERVAL_01 int
X
$G_SERVICE_INTERVAL_02 int
X
$G_SERVICE_INTERVAL_03 int
X
$G_SERVICE_INTERVAL_04 int
X
$G_SERVICE_INTERVAL_05 int
X
$G_TABLE_EQUIPMENT
IA
PM PP PR PS SA
varchar(20)
X
$G_TABLE_FUNCTL_LOCAT varchar(20)
N
X
$G_TASK_TYPE_PROBATIO varchar(2)
N_END
X
$G_TERMINATION_ACTION
varchar(2)
X
$G_VALID_DATE
datetime
$G_WAGE_TYPE_01
varchar(4)
X
$G_WAGE_TYPE_02
varchar(4)
X
$G_WAGE_TYPE_03
varchar(4)
X
$G_WAGE_TYPE_04
varchar(4)
X
$G_WAGE_TYPE_05
varchar(4)
X
$G_WAGE_TYPE_06
varchar(4)
X
$G_WAGE_TYPE_07
varchar(4)
X
$G_WAGE_TYPE_08
varchar(4)
X
$G_WAGE_TYPE_09
varchar(4)
X
$G_WAGE_TYPE_10
varchar(4)
X
$G_WAGE_TYPE_11
varchar(4)
X
$G_WAGE_TYPE_12
varchar(4)
X
$G_WAGE_TYPE_13
varchar(4)
X
$G_WAGE_TYPE_14
varchar(4)
X
$G_WAGE_TYPE_15
varchar(4)
X
$G_WAGE_TYPE_16
varchar(4)
X
$G_WAGE_TYPE_17
varchar(4)
X
$G_WAGE_TYPE_18
varchar(4)
X
$G_WAGE_TYPE_19
varchar(4)
X
X
$G_WAGE_TYPE_20
varchar(4)
X
$G_WORKDAY_EDATE
datetime
X
$G_WORKDAY_SDATE
datetime
X
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
289
7
7
Using the Rapid Mart
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
Data Type: varchar(1)
Default Value: “?”
Default text for dimension default rows, foreign keys, and primary keys. Also
used as a default for missing descriptions.
$G_EDATE
Data Type: datetime
Default Value: NULL
The ending date for data extraction.
For first (initial) run or incremental (delta) runs, we recommend leaving this
empty (null). The Initialize job script and function AW_StartJob will
automatically determine the proper value.
290
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
if you set the variable, jobs will not extract data entered into your SAP
solutions system after this date. For example, if your end date is June 4,
1999, the jobs will not extract data for June 5, 1999 or later.
$G_LANGUAGE
Data Type: varchar(1)
Default Value: “E” (English)
The language in which jobs extract text descriptions. Use the SAP solutions
standard language abbreviations if you require a different language.
$G_LOAD_DATE
Data Type: datetime
Default Value: System Date and Time
Always set to current system date and time by the Job Initialization script. Do
not change the setting of this variable.
$G_LOAD_TIME
Data Type: varchar(8)
Default Value: System Time
Always set to current system time by the Job Initialization script. Do not
change the setting of this variable.
$G_LOAD_TYPE
Data Type: varchar(7)
Default Value: “FIRST”
Legal values:
•
•
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
Default Value: 31-Dec-9999
Used in date effective transforms to match SAP value for “infinite” date as end
of validity period.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
291
7
7
Using the Rapid Mart
Global Variables
$G_REBUILD_INDEXES
Data Type: varchar(1)
Default Value: “N” on Weekdays, “Y” on Weekends
Legal values:
•
•
Y - Run rebuild indexes script
N - Do not run rebuild indexes script
As delivered, this is a place holder for custom performance tuning.
See Rapid Mart Deployment Guideline.pdf for more details on how to use
this variable in conjunction with the stored procedures in file
Create_Sample_Maintenance_SP.sql.
These stored procedures drop indexes before a Fact Table load, and
re-create the indexes when the load is complete.
Use this variable to further restrict the drop and re-create to weekends only.
$G_RUN_MODE
Data Type: varchar(10)
Default Value: NULL
Legal values:
•
•
RESET - Forces job to reload from value set in $G_SDATE.
NULL - Uses AW_JOBEXECUTION to determine $G_SDATE.
When set to “RESET”, this variable forces the Rapid Mart to use the starting
extract date you have set for variable $G_SDATE. Otherwise, the setting is
determine by querying table AW_JOBEXECUTION, and using the
EXTRACTHIGH value of the last successful run.
$G_SDATE
Data Type: datetime
Default Value: 01-Jan-1990
The start date for data extraction.
During an initial extract, the job does not extract data that was entered into
your SAP solutions system prior to $G_SDATE. For example, if your start
date is January 26, 2000, the initial extract job does not extract data that was
entered on January 25, 2000 or earlier.
During incremental (delta) extractions, the job only extracts data modified or
entered on or after this date. The incremental load job only uses the
$G_SDATE when one of these conditions is true:
292
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
•
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 BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
2 of 4 configurable past time periods (in days) to use for aged receivables and
payables and late payments
$C
Data Type: int
Default Value: 90
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
293
7
7
Using the Rapid Mart
Global Variables
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
3 of 4 configurable past time periods (in days) to use for aged receivables and
payables and late payments
$D
Data Type: int
Default Value: 120
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
4 of 4 configurable past time periods (in days) to use for aged receivables and
payables and late payments
$E
Data Type: int
Default Value: 14
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
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:
•
294
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
2 of 3 configurable forecast time periods (in days) used to calculate values of
financial documents at future dates (for discounting purposes, etc.)
$G
Data Type: int
Default Value: 45
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
3 of 3 configurable forecast time periods (in days) used to calculate values of
financial documents at future dates (for discounting purposes, etc.)
$G_ABSOLUTE_START_DATE
Data Type: datetime
Default Value: NULL
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects Human Resources Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Inventory Rapid Mart, version for SAP
solutions
Earliest date to use for delta load of Financial Documents, (in AP, AR, and GL
Rapid Marts). Closed documents created before this date WILL NOT be
loaded to the Rapid Mart.
It works in conjunction with variable $G_ORIG_SDATE for incremental loads
that do not carry a “date of last change” in the SAP solutions tables.
See the Technical Implementation chapter for each specific Rapid Mart for
full details on how this variable is used.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
295
7
7
Using the Rapid Mart
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 BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Cost Center Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects Plant Maintenance Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions
Determines the last fiscal year to be extracted for certain incremental loads.
This is used when a “date of last change” is not available in SAP solutions,
but the fiscal year of a transaction is available.
This is usually the year from global variable $G_EDATE.
$G_EXCHANGE_TYPE_ID
Data Type: varchar(4)
Default Value: “M” - Standard Translation at Average Rate
Where Used:
296
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
•
SAP BusinessObjects Sales Rapid Mart, version for SAP solutions
Used for lookup of exchange rates to Global Currency
$G_GLOBAL_CURRENCY
Data Type: varchar(5)
Default Value: “USD” - U.S. Dollar
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Sales Rapid Mart, version for SAP solutions
Global Currency Code. You assign a global currency for the Rapid Mart.
Used to present a consolidated picture of monetary values in one universal
currency.
$G_INT_ORDER_CATEG_PP
Data Type: varchar(2)
Default Value: “10”
Where Used:
•
SAP BusinessObjects Production Planning Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions
PRODUCTION_ORDER_FACT is a common table in each of these Rapid
Marts. However, we extract a different Order Category in each. The default
values for Production Orders (PP Rapid Mart) is 10
Note: If you have only the PP Rapid Mart set values for both
$G_INT_ORDER_CATEG_PP and $G_INT_ORDER_CATEG_PS to 10.
$G_INT_ORDER_CATEG_PS
Data Type: varchar(2)
Default Value: “20”
Where Used:
•
SAP BusinessObjects Production Planning Rapid Mart, version for
SAP solutions
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
297
7
7
Using the Rapid Mart
Global Variables
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions
PRODUCTION_ORDER_FACT is a common table in each of these Rapid
Marts. However, we extract a different Order Category in each. The default
values for Network Orders (PS Rapid Mart) is 20
Note: If you have only the PS Rapid Mart set values for both
$G_INT_ORDER_CATEG_PP and $G_INT_ORDER_CATEG_PS to 20.
$G_ORIG_SDATE
Data Type: datetime
Default Value: NULL
Where Used:
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects Human Resources Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Inventory Rapid Mart, version for SAP
solutions
This is set on the first (initial) load. It is the value of $G_SDATE at the time of
that first load. It is stored in database table AW_FIRST_RUN_DATE. During
“DELTA” (incremental) loads, it is retrieved from that table. It is used in
several Rapid Marts to determine the start date for the load of OPEN items.
It works in conjunction with variable $G_ABSOLUTE_START_DATE for
incremental loads that do not carry a “date of last change” in the SAP
solutions tables.
$G_STARTFISCALYEAR
Data Type: int
Default Value: NULL
Where Used:
298
•
SAP BusinessObjects Accounts Payable Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Accounts Receivable Rapid Mart, version for
SAP solutions
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
•
SAP BusinessObjects Cost Center Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions
•
SAP BusinessObjects Plant Maintenance Rapid Mart, version for
SAP solutions
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions
Determines the first fiscal year to be extracted for certain incremental loads.
This is used when a “date of last change” is not available in SAP solutions,
but the fiscal year of a transaction is available.
This is usually the year from global variable $G_SDATE.
Used in Only 1 Rapid Mart
$G_ADDRESS_VERSION
Data Type: varchar(1)
Default Value: “ “ A single space
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Used for Extraction of Central Address dimension from table ADRC. Default
value is a single space.
$G_BUS_PARTN_SDATE
Data Type: datetime
Default Value: System Date - 8
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Used in data flow R3_SalesOrdVBPADelta.
Tells how many days back in time we will check for changes in sales
document partners (bill-to partner, ship-to partner, etc.) Used in conjunction
with variable $G_BUS_PARTNER.
$G_BUS_PARTNER
Data Type: varchar(1)
Default Value: Sunday = Yes, all other days = No
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
299
7
7
Using the Rapid Mart
Global Variables
Actual ATL Language Code:
“ifthenelse(day_in_week(sysdate())=7,'Y','N')”
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Used in Component Work Flow C_SalesOrderNumberDelta_SAP
If “Y” (Sunday), the Rapid Mart will extract an incremental load of business
partners going back the number of days set in variable
$G_BUS_PARTN_DATE (see above).
$G_COST_OF_SALES_LEDGER_ID
Data Type: varchar(2)
Default Value: “0L”
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
In New GL, identifies the subset of the New FI-SL Standard Ledger that is
loaded into the Cost of Sales Detail and Summary Subject Areas. Choose the
Ledger ID in your business that best captures the Cost of Sales functionality.
$G_COUNTRY_GRP
Data Type: varchar(2)
Default Value: “10”
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Default Country Grouping Code for HR as determined in SAP solutions table
T500L.
$G_DEL_PERIOD
Data Type: datetime
Default Value: System Date - 180
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Used in Sales Order Incremental Load. Determines how far back (in days) the
Rapid Mart checks for orders that have been deleted in SAP solutions.
$G_DEL_REJECT_REASON
Data Type: varchar(2)
Default Value: “DD”
300
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Identifier used in the REJECT_REASON_ID field of SALES_ORDERS_FACT
when a sales order line has been deleted in SAP solutions. The code is also
added to the dimension table REJECT_REASON with the description
“Deleted”.
$G_DROP_SHIP
Data Type: varchar(1)
Default Value: “Y” - Calculate backlog for third-party delivery
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Third-party deliveries are those that are delivered by an outside (third-party)
organization such as a fulfillment house. They can also be for an intangible
material (such as a service) where no physical item is delivered.
When set to “Y” (Yes) the Rapid Mart calculates backlog as:
•
•
Qty Ordered - Qty Invoiced (for third-party items)
Qty Ordered - Qty Delivered (for all other items).
When set to “N” (No) the Rapid Mart calculates backlog as:
•
Qty Ordered - Qty Delivered (for all items).
$G_GL_ACCOUNT_HIER_NAME
Data Type: varchar(10)
Default Value: “@GL”
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
The GL Account Hierarchy tables in the Rapid Mart use field “HIER_ID” to
identify the source of the hierarchy entry.
Data from SAP solutions transaction GS03, source hierarchy GLT0-RACCT
are assigned “@GL”
You can change the assignment of this variable. However, this is not a
requirement.
See Technical Implementation Chapter in the SAP BusinessObjects General
Ledger Rapid Mart, version for SAP solutions User Guide for more
information.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
301
7
7
Using the Rapid Mart
Global Variables
$G_GL_SUM_PLAN_LEDGER_ID
Data Type: varchar(2)
Default Value: “L6”
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
In New GL, identifies the subset of the New FI-SL Standard Ledger that is
loaded into the GL Plan and GL Summary Subject Areas. Choose the Ledger
ID that best captures GL Summary and GL Plan functionality.
$G_GL_VERSION
Data Type: varchar(3)
Default Value: (see below)
Legal Values: “OLD” or “NEW”
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
Tells which version of SAP solutions GL Module you use. Using “NEW” with
SAP solutions releases older than ECC 5.0 is not possible as the New GL
module did not exist in these earlier releases.
In the SAP BusinessObjects General Ledger Rapid Mart, version for SAP
solutions, there are two jobs, one for OLD GL and one for NEW GL. The
default value in the NEW GL job is “NEW”. The default value in the OLD GL
job is “OLD”.
$G_HIRE_ACTION_01
Data Type: varchar(2)
Default Value: “01”
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Hiring Action Variable 01
$G_HIRE_ACTION_02
Data Type: varchar(2)
Default Value: “90”
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Hiring Action Variable 02
302
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
$G_HIRE_ACTION_03
Data Type: varchar(2)
Default Value: “K1”
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Hiring Action Variable 03
$G_INIT_HIST_CHG
Data Type: varchar(1)
Default Value: “Z”
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Used during the initial load of SALES_ORDER_HISTORY table.
IF default value “Z”, then
•
•
SALES_ORDER_HISTORY.QTY_DELTA_ORDER_SLSUOM = 0
SALES_ORDER_HISTORY.AMT_DELTA_NET_VALUE_TRX = 0
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
Data Type: varchar(20)
Default Value: “5”
Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart,
version for SAP solutions
Catalog type to use for Malfunction Cause on Notifications. Choose your
system notification catalog group type for “Cause”.
$G_MALFUNCTION_DAMAGE
Data Type: varchar(20)
Default Value: “C”
Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart,
version for SAP solutions
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
303
7
7
Using the Rapid Mart
Global Variables
Catalog type to use for Malfunction Damage on Notifications. Choose your
system notification catalog group type for “Damage”.
$G_MALFUNCTION_OBJ_PART
Data Type: varchar(20)
Default Value: “B”
Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart,
version for SAP solutions
Catalog type to use for Malfunction Object Part on Notifications. Choose your
system notification catalog group type for “Object Part”.
$G_MRP_RESULTS_DELETE
Data Type: varchar(1)
Default Value: “N”
Where Used: SAP BusinessObjects Production Planning Rapid Mart,
version for SAP solutions
Determines if MRP Results should be deleted before an Incremental Load.
•
•
Y = Delete before Incremental Load.
N = No Delete before Incremental Load
$G_ONTIME_DELIV_WINDOW
Data Type: int
Default Value: 15 days
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
Used by On Time Delivery Section. Tells the system to limit On Time Delivery
loads to a date range based on the Sales Schedule 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
Data Type: varchar(10)
Default Value: “@PC”
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
304
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
The GL Account Hierarchy tables in the Rapid Mart use field “HIER_ID” to
identify the source of the hierarchy entry.
Data from SAP solutions transaction GS03, source hierarchy GLPCT-RACCT
are assigned “@PC”
You can change the assignment of this variable. However, this is not a
requirement.
See Technical Implementation Chapter in the SAP BusinessObjects General
Ledger Rapid Mart, version for SAP solutions User Guide for more
information.
$G_PROFIT_CENTER_LEDGER_ID
Data Type: varchar(2)
Default Value: “L5”
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
In New GL, identifies the subset of the New FI-SL Standard Ledger that is
loaded into the Profit Center Detail and Summary Subject Areas
Choose the Ledger ID that best captures Profit Center Summary and Profit
Center functionality.
$G_REHIRE_ACTION_01
Data Type: varchar(2)
Default Value: "JD"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Rehiring Action Variable 01
$G_REHIRE_ACTION_02
Data Type: varchar(2)
Default Value: "N7"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Rehiring Action Variable 02
$G_RETIRE_ACTION
Data Type: varchar(2)
Default Value: "ZP”
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
305
7
7
Using the Rapid Mart
Global Variables
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Retirement Action
$G_SAP_VERSION
Data Type: int
Default Value: System Determined - see below
Where Used: SAP BusinessObjects General Ledger Rapid Mart, version
for SAP solutions
Automatically determined in the Rapid Mart jobs. The first digit of the SAP
solutions system variable SY-SAPRL. See Work Flow C_SAPVersion for
more details. This value is also stored in the one row target table
SAP_VERSION.
Attempting to run the “NEW” GL job with SAP solutions older than release
ECC 5.0 will cause the job to fail.
$G_SCHOOL_TYPE
Data Type: varchar(2)
Default Value: "50"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
School Type
$G_SERVICE_INTERVAL_01
Data Type: INT
Default Value: 6 (1/2 year)
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of 5 Intervals for determining Employee Length of Service. Values are in
Months.
$G_SERVICE_INTERVAL_02
Data Type: INT
Default Value: 12 (1 year)
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
306
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
One of 5 Intervals for determining Employee Length of Service. Values are in
Months.
$G_SERVICE_INTERVAL_03
Data Type: INT
Default Value: 36 (3 years)
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of 5 Intervals for determining Employee Length of Service. Values are in
Months.
$G_SERVICE_INTERVAL_04
Data Type: INT
Default Value: 60 (5 years)
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of 5 Intervals for determining Employee Length of Service. Values are in
Months.
$G_SERVICE_INTERVAL_05
Data Type: INT
Default Value: 120 (10 years)
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of 5 Intervals for determining Employee Length of Service. Values are in
Months.
$G_TABLE_EQUIPMENT
Data Type: varchar(20)
Default Value: “EQUI”
Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart,
version for SAP solutions
Initialize according to your system class type for Equipment master table
name
$G_TABLE_FUNCTL_LOCATN
Data Type: varchar(20)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
307
7
7
Using the Rapid Mart
Global Variables
Default Value: “IFLOT”
Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart,
version for SAP solutions
Initialize according to your system class type for Functional Location master
table name
$G_TASK_TYPE_PROBATION_END
Data Type: varchar(2)
Default Value: “01”
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Probation End Task Type
$G_TERMINATION_ACTION
Data Type: varchar(2)
Default Value: “10”
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Termination Action
$G_VALID_DATE
Data Type: datetime
Default Value: System Date (without Time)
Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP
solutions
This is identical to variable $G_LOAD_DATE without the timestamp
(midnight, beginning of the day).
Used in the incremental load of Sales Organization Hierarchy for comparison
to with the VALID_TO dates. Do not change the value in this variable.
$G_WAGE_TYPE_01
Data Type: varchar(4)
Default Value: "/101"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
308
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_02
Data Type: varchar(4)
Default Value: "/110"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_03
Data Type: varchar(4)
Default Value: "/401"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_04
Data Type: varchar(4)
Default Value: "/403"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_05
Data Type: varchar(4)
Default Value: "/404"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_06
Data Type: varchar(4)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
309
7
7
Using the Rapid Mart
Global Variables
Default Value: "/405"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_07
Data Type: varchar(4)
Default Value: "/406"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_08
Data Type: varchar(4)
Default Value: "/410"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_09
Data Type: varchar(4)
Default Value: "/441"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_10
Data Type: varchar(4)
Default Value: "/550"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
310
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
$G_WAGE_TYPE_11
Data Type: varchar(4)
Default Value: "/560"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_12
Data Type: varchar(4)
Default Value: "/5U0"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_13
Data Type: varchar(4)
Default Value: "/5U1"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_14
Data Type: varchar(4)
Default Value: "MI10"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_15
Data Type: varchar(4)
Default Value: "/102"
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
311
7
7
Using the Rapid Mart
Global Variables
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_16
Data Type: varchar(4)
Default Value: "////"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_17
Data Type: varchar(4)
Default Value: "////"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_18
Data Type: varchar(4)
Default Value: "////"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WAGE_TYPE_19
Data Type: varchar(4)
Default Value: "////"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
312
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
$G_WAGE_TYPE_20
Data Type: varchar(4)
Default Value: "////"
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to
"////" if not used.
$G_WORKDAY_EDATE
Data Type: datetime
Default Value: 01-Jan-1994
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
First date of date range to populated Working Days dimension
$G_WORKDAY_SDATE
Data Type: datetime
Default Value: 31-Dec-2006
Where Used: SAP BusinessObjects Human Resources Rapid Mart,
version for SAP solutions
Last date of date range to populated Working Days dimension
Setting Global Variables
Job Properties
The default values for most Global Variables are set on the Job Properties
window (shown below) of the Rapid Mart jobs. The exceptions are Global
Variables that are conditional (an “IF” statement is required).
The conditional Global Variables are set in the “InitializeJob” Script (see
below). The script is a common component (identical across all Rapid Marts).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
313
7
7
Using the Rapid Mart
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.
314
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Global Variables
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
315
7
7
Using the Rapid Mart
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:
316
•
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Executing the job
•
RM_GetFirstRunDate - Called in “DELTA” (incremental) loads only.
Retreives the value of $G_SDATE stored in table
AW_FIRST_RUN_DATE. The value retreived is stored in global variable
$G_ORIG_SDATE. Consult the Techinical Implementation Chapter for
each individual Rapid Mart for more details on how this is used.
Note: If you set your own value for $G_ORIG_DATE before the call to
RM_GetFirstRunDate, the Rapid Mart will use your value and not retreive
the value in AW_FIRST_RUN_DATE.
Executing the job
Before executing the job, make sure that the configuration steps in "Data
Services Supplement for SAP" have been completed and the connection to
SAP server is established.
The steps needed to execute a job, depend on the type of job:
•
•
Initial (First) Extraction and Load
Incremental (Delta) Extraction and Load
Initial (First) Extraction and Load
1.
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
317
7
7
Using the Rapid Mart
Executing the job
You can also set global variable values after you select Execute
command from the drop-down menu in the project area.
For more information about the variables see “Global Variables” on
page 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.
318
Make sure that the value for the $G_LOAD_TYPE global variable is
set to ‘DELTA’.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Using the Rapid Mart
Executing the job
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
319
7
7
Using the Rapid Mart
Customizing the Rapid Mart
Customizing the Rapid Mart
Rapid Marts are easy to customize. You can easily:
•
•
Customize the Rapid Mart data schema to meet your specific needs.
•
Transport Rapid Mart components and sections to different Rapid Marts
using the Data Services export and import facilities.
Expand the Rapid Mart to be used with various integrated query,
reporting, and data analysis applications.
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.
320
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Technical Implementation
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 information from CSLA and
CSLT
ACTIVITY
C_ActivityHier_SAP
Dimensional component loading
Cost Activity Hierarchy information
from CCSS-LSTAR and CSLA
ACTIVITY_HIER,
ACTIVITY_HIER_HZ,
ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
C_ChartofAccts_SAP
Chart of Accts (T004 and T004T) in
SAP solutions
CHART_OF_ACCOUNTS
322
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Milestone Section
Work Flow
Description
Tables
C_CompanyCode_SAP
Dimensional component loading
Company Codes information from
T001
COMPANY_CODE
C_ControlKey_SAP
Dimensional component loading
control key information and
descriptions from T430/T430T
CONTROL_KEY
C_ControllingArea_SAP
Dimensional component loading
Controlling Area information from
TKA01
CONTROLLING_AREA
C_CostElement_SAP
Dimensional component loading
Cost Element information from
CSKA and CSKU
COST_ELEMENT
C_CostElementHier_SAP
Dimensional component loading
Cost Element Hierarchy information
from CCSS-KSTAR and CSK1
COST_ELEMENT_HIER,
COST_ELEMENT_HIER_HZ,
COST_ELEMENT_HIER_VR,
COST_ELEMENT_HIER_BAD
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
dimension
INTERNAL_ORDER
C_InternalOrderHier_SAP
Dimensional component loading
Internal Order Hierarchy information
from CCSS-AUFNR and AUFK
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
C_MilestoneUsage_SAP
Milestone Usage Descriptive
attributes from T433T - load
MILESTONE_USAGE
MILESTONE_USAGE
C_NetworkProfile_SAP
Network profile descriptive attributes NETWORK_PROFILE
from TCN41, TCN41T
C_OrderOperation_SAP
Order Operation Master data - from
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 information
PROJECT
C_ProjectElement_SAP
Dimensional component loading
Project Element (WBS) master data
PROJECT_ELEMENT
ORDER_OPERATION
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
323
8
8
Technical Implementation
Milestone Section
Work Flow
Description
Tables
C_ProjectElementHier_SAP
Dimensional component loading
project element hierarchy
information
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ
,
PROJECT_ELEMENT_HIER_VR
,
PROJECT_ELEMENT_HIER_BA
D
C_PurchOrganization_SAP
Purchasing Organization Dimension
from table T024E in SAP solutions
PURCH_ORGANIZATION
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
PLKO - ROUNTING
ROUTING
C_RoutingOperation_SAP
Details of Task List
operations/activities from PLPO populate ROUTING_OPERATION
dimension
ROUTING_OPERATION
C_StatusProfile_SAP
Milestone Status profile descriptive
attributes from TJ20T - load
STATUS_PROFILE dimension
STATUS_PROFILE
C_TaskListType_SAP
Task List Type descriptive attributes
from TCA02 - TASK_LIST_TYPE
dimension
TASK_LIST_TYPE
C_TimeDim_SAP
Dimensional component loading
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
TIME_DIM
C_UnitOfMeasure_SAP
Populates Units of Measure
dimension during first and delta
loads from Table T006A in SAP
solutions
UNIT_OF_MEASURE
C_WorkCenter_SAP
Load WORK_CENTER master data
dimension
WORK_CENTER
C_WorkCenterCategory_SAP
Work Center Category descriptive
attributes from TC30T
WORK_CENTER_CATEGORY
C_WorkCenterHier_SAP
Work Center Hierarchical
relationship in Horizontal and Vertical
formats from CRHH/CRHS; load
WORK_CENTER_HIER,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_HZ
WORK_CENTER_HIER,
WORK_CENTER_HIER_HZ,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_BAD
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.
324
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Milestone Section
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
AFVC - Operation within an order
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”.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
325
8
8
Technical Implementation
Network Order Section
The extracted go through the same Effective Date transform to compute the
VALID_TO_DATE as the initial load.
Network Order Section
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:
•
SAP BusinessObjects Production Planning Rapid Mart, version for SAP
solutions - Extracts only Order Category “10” (Standard Production
Orders).
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions - Extracts only Order Category “20” (Network 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
Work Flow
Description
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 information from
TGSB and TGSBT
BUSINESS_AREA
C_ChartofAccts_SAP
Chart of Accts (T004 and T004T) in
SAP solutions
CHART_OF_ACCOUNTS
C_CompanyCode_SAP
Dimensional component loading
Company Codes information from
T001
COMPANY_CODE
C_ControllingArea_SAP
Dimensional component loading
Controlling Area information from
TKA01
CONTROLLING_AREA
C_CostCenter_SAP
Dimensional component loading
Cost Center information from CSKS
and CSKT
COST_CENTER
C_CostCenterHier_SAP
Dimensional component loading
Cost Center Hierarchy information
from CCSS-KOSTL and CSKS
COST_CENTER_HIER,
COST_CENTER_HIER_HZ,
COST_CENTER_HIER_VR,
COST_CENTER_HIER_BAD
C_CostElement_SAP
Dimensional component loading
Cost Element information from
CSKA and CSKU
COST_ELEMENT
326
Tables
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Network Order Section
Work Flow
Description
Tables
C_CostElementHier_SAP
Dimensional component loading
Cost Element Hierarchy information
from CCSS-KSTAR and CSK1
COST_ELEMENT_HIER,
COST_ELEMENT_HIER_HZ,
COST_ELEMENT_HIER_VR,
COST_ELEMENT_HIER_BAD
C_Currency_SAP
Dimensional component loading
currency abbreviations and texts
from TCURT, TCURC
CURRENCY
C_DocumentType_SAP
Combined Document Type Dim.
Contains: Billing Type Delivery
Type Financial Document Type
FISL Document Type (Special
Ledger Doc. Type) Internal Order
Type Notification Type Purch Doc
Type Sales Order Type
DOCUMENT_TYPE &
DOCUMENT_CATEGORY
C_FunctionalArea_SAP
Dimensional component loading
Functional Area information from
TFKB and TFKBT
FUNCTIONAL_AREA
C_FunctionalAreaHier_SAP
Functional Area Hierarchy from
GLFUNCT-RFAREA
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BA
D
C_InternalOrder_SAP
Load INTERNAL_ORDER
dimension
INTERNAL_ORDER
C_InternalOrderHier_SAP
Dimensional component loading
Internal Order Hierarchy information
from CCSS-AUFNR and AUFK
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
C_InternalOrderStatus_SAP
Internal orders status reference
dimension from TKO04
INTERNAL_ORDER_STATUS
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
plant-specific material information
such as procurement type and
purchasing group from MARC
C_MaterialGroup_SAP
Dimensional component loading
MATERIAL_GROUP
consisting of a first and delta load for
the MATERIAL_GROUP table from
T023T.
C_MaterialType_SAP
Material Type descriptive attributes
from T134, T134T
MATERIAL_BY_PLANT
MATERIAL_TYPE
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
327
8
8
Technical Implementation
Network Order Section
Work Flow
Description
Tables
C_MRPController_SAP
Dimensional component loading
MRP controller information from
T024D
MRP_CONTROLLER
C_NetworkProfile_SAP
Network profile descriptive attributes NETWORK_PROFILE
from TCN41, TCN41T
C_ObjectClass_SAP
Dimensional component loading
Object Class information from
DD07T
OBJECT_CLASS
C_ObjectNumberType_SAP
Object Key first 2 characters that
identify uniquely source table and
record from TBO01. Load
OBJECT_NUMBER_TYPE
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_Plant_SAP
Dimensional component loading
PLANT
consisting of a first and delta load for
the plant table from T001W.
C_PlantLocation_SAP
Plant Location attributes from T499S PLANT_LOCATION
- PLANT_LOCATION
C_ProfitCenter_SAP
Dimensional component loading
Profit Center master data
(Dimension)
PROFIT_CENTER
C_ProfitCenterHier_SAP
Dimensional component loading
profit center hierarchy (EC-PCA
Profit center hierarchy in SAP
solutions)
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
C_Project_SAP
Dimensional component loading
project information
PROJECT
C_ProjectElement_SAP
Dimensional component loading
Project Element (WBS) master data
PROJECT_ELEMENT
C_ProjectElementHier_SAP
Dimensional component loading
project element hierarchy
information
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ
,
PROJECT_ELEMENT_HIER_VR
,
PROJECT_ELEMENT_HIER_BA
D
C_PurchOrganization_SAP
Purchasing Organization Dimension
from table T024E in SAP solutions
PURCH_ORGANIZATION
C_Routing_SAP
Routing Header information from
PLKO - ROUNTING
ROUTING
C_ServicePerson_SAP
Populates SERVICE_PERSON
dimension with Employee names.
This is a reference dimension only,
and not Employee master data
SERVICE_PERSON
328
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Network Order Section
Work Flow
Description
Tables
C_SpecialProcurementType_SAP
Loads into
SPECIAL_PROCUREMENT_TYPE
dimension (from DD07T domain
SOBES)
SPECIAL_PROCUREMENT_TY
PE
C_StorageLocation_SAP
Dimensional component loading
storage location descriptions with
plant and division assignments from
T001L
STORAGE_LOCATION
C_TaskListType_SAP
Task List Type descriptive attributes
from TCA02 - TASK_LIST_TYPE
dimension
TASK_LIST_TYPE
C_TaskListUsage_SAP
Task List Usage descriptive
attributes from TC23T
(TASK_LIST_USAGE)
TASK_LIST_USAGE
C_TimeDim_SAP
Dimensional component loading
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 loaded. Modify
dates.dat file to change number of
dates
TIME_DIM
C_UnitOfMeasure_SAP
Populates Units of Measure
dimension during first and delta
loads from Table T006A in SAP
solutions
UNIT_OF_MEASURE
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:
•
SAP BusinessObjects Production Planning Rapid Mart, version for SAP
solutions - Extracts only Order Category “10” (Standard Production
Orders).
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
329
8
8
Technical Implementation
Network Order Section
•
SAP BusinessObjects Project Systems Rapid Mart, version for SAP
solutions - Extracts only Order Category “20” (Network 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"
Initial (First) Load
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.
Incremental (Delta) Load
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
$G_SDATE, and $G_EDATE the production order will be extracted.
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.
330
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Network Relationship Section
Network Relationship Section
A way of describing the link between the start and finish points of two
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.
This section first loads the required dimension components with work flow
WF_NetworkRelationshipDim_SAP. If these dimensions have already been
loaded during the current job, the job will not reload them.
Work Flow
Description
Tables
C_BusinessArea_SAP
Dimensional component loading
Business Area information from
TGSB and TGSBT
BUSINESS_AREA
C_CompanyCode_SAP
Dimensional component loading
Company Codes information from
T001
COMPANY_CODE
C_ControlKey_SAP
Dimensional component loading
control key information and
descriptions from T430/T430T
CONTROL_KEY
C_ControllingArea_SAP
Dimensional component loading
Controlling Area information from
TKA01
CONTROLLING_AREA
C_FunctionalArea_SAP
Dimensional component loading
Functional Area information from
TFKB and TFKBT
FUNCTIONAL_AREA
C_FunctionalAreaHier_SAP
Functional Area Hierarchy from
GLFUNCT-RFAREA
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BA
D
C_InternalOrder_SAP
Load INTERNAL_ORDER
dimension
INTERNAL_ORDER
C_InternalOrderHier_SAP
Dimensional component loading
Internal Order Hierarchy information
from CCSS-AUFNR and AUFK
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
C_MRPController_SAP
Dimensional component loading
MRP controller information from
T024D
MRP_CONTROLLER
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
331
8
8
Technical Implementation
Network Relationship Section
Work Flow
Description
Tables
C_OrderOperation_SAP
Order Operation Master data - from
AFVC loading
ORDER_OPERATION dimension
ORDER_OPERATION
C_Plant_SAP
Dimensional component loading
PLANT
consisting of a first and delta load for
the plant table from T001W.
C_PlantLocation_SAP
Plant Location attributes from T499S PLANT_LOCATION
- PLANT_LOCATION
C_ProfitCenter_SAP
Dimensional component loading
Profit Center master data
(Dimension)
PROFIT_CENTER
C_ProfitCenterHier_SAP
Dimensional component loading
profit center hierarchy (EC-PCA
Profit center hierarchy in SAP
solutions)
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
C_Project_SAP
Dimensional component loading
project information
PROJECT
C_ProjectElement_SAP
Dimensional component loading
Project Element (WBS) master data
PROJECT_ELEMENT
C_ProjectElementHier_SAP
Dimensional component loading
project element hierarchy
information
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ
,
PROJECT_ELEMENT_HIER_VR
,
PROJECT_ELEMENT_HIER_BA
D
C_PurchOrganization_SAP
Purchasing Organization Dimension
from table T024E in SAP solutions
PURCH_ORGANIZATION
C_RelationshipType_SAP
Network Relationship descriptive
attributes from TCN2T
RELATIONSHIP_TYPE
C_StorageLocation_SAP
Dimensional component loading
storage location descriptions with
plant and division assignments from
T001L
STORAGE_LOCATION
C_TimeDim_SAP
Dimensional component loading
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 loaded. Modify
dates.dat file to change number of
dates
TIME_DIM
C_UnitOfMeasure_SAP
Populates Units of Measure
dimension during first and delta
loads from Table T006A in SAP
solutions
UNIT_OF_MEASURE
332
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Project Cost Summary Section
Work Flow
Description
Tables
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)
C_WorkCenter_SAP
Load WORK_CENTER master data
dimension
WORK_CENTER
C_WorkCenterCategory_SAP
Work Center Category descriptive
attributes from TC30T
WORK_CENTER_CATEGORY
C_WorkCenterHier_SAP
Work Center Hierarchical
relationship in Horizontal and Vertical
formats from CRHH/CRHS; load
WORK_CENTER_HIER,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_HZ
WORK_CENTER_HIER,
WORK_CENTER_HIER_HZ,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_BAD
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
AFVC - Operation within an order
The target table for Network Relationships is:
•
NETWORK_RELATIONSHIP_FACT
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.
Project Cost Summary Section
Use Project Costing to plan, monitor, and control project costs, thereby
achieving comprehensive cost accounting.
The Rapid Mart calls C_ProjectCostSummarySection_SAP to load these
tables.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
333
8
8
Technical Implementation
Project Cost Summary Section
This section first loads the required dimension components with work flow
WF_ProjectCostSummaryFactDims_SAP. If these dimensions have
already been loaded during the current job, the job will not reload them
Work Flow
Description
Tables
C_BusinessActivity_SAP
FK-SL Activity attributes from
T022/T022T. Load
BUSINESS_ACTIVITY dimension
BUSINESS_ACTIVITY
C_BusinessArea_SAP
Dimensional component loading
Business Area information from
TGSB and TGSBT
BUSINESS_AREA
C_CompanyCode_SAP
Dimensional component loading
Company Codes information from
T001
COMPANY_CODE
C_ControllingArea_SAP
Dimensional component loading
Controlling Area information from
TKA01
CONTROLLING_AREA
C_CostObjectIndicator_SAP
Cost Object Indicator descriptive
attributes from DD07T domain
(BP_TRGKZ domain)
COST_OBJECT_INDICATOR
C_Currency_SAP
Dimensional component loading
currency abbreviations and texts
from TCURT, TCURC
CURRENCY
C_FinancialMgmtArea_SAP
Financial Management Area -- Also
called Funds Management Area -dimension loaded from table FM01T
FINANCIAL_MGMT_AREA
C_FinancingCode_SAP
Fund Management - FIFM:
Financing code from FMFINCODE
source table; load
FINANCING_CODE dimension
FINANCING_CODE
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
Fiscal Year / Fiscal Period data
FISC_PERIOD
C_FunctionalArea_SAP
Dimensional component loading
Functional Area information from
TFKB and TFKBT
FUNCTIONAL_AREA
C_FunctionalAreaHier_SAP
Functional Area Hierarchy from
GLFUNCT-RFAREA
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BA
D
334
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Project Cost Summary Section
Work Flow
Description
Tables
C_ObjectNumberType_SAP
Object Key first 2 characters that
identify uniquely source table and
record from TBO01. Load
OBJECT_NUMBER_TYPE
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_OrderOperation_SAP
Order Operation Master data - from
AFVC loading
ORDER_OPERATION dimension
ORDER_OPERATION
C_PeggingObject_SAP
Details of Pegging Objects from
PEGOB, PEGQTY; load
PEGGING_OBJECT dimension
PEGGING_OBJECT
C_Plant_SAP
Dimensional component loading
PLANT
consisting of a first and delta load for
the plant table from T001W.
C_ProfitCenter_SAP
Dimensional component loading
Profit Center master data
(Dimension)
PROFIT_CENTER
C_ProfitCenterHier_SAP
Dimensional component loading
profit center hierarchy (EC-PCA
Profit center hierarchy in SAP
solutions)
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
C_ProgressMeasureMethod_SAP
Descriptive attributes for PS object
PROGRESS_MEASURE_METH
progress measurement methods
OD
from EVOP; load
PROGRESS_MEASURE_METHOD
C_Project_SAP
Dimensional component loading
project information
PROJECT
C_ProjectElement_SAP
Dimensional component loading
Project Element (WBS) master data
PROJECT_ELEMENT
C_ProjectElementHier_SAP
Dimensional component loading
project element hierarchy
information
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ
,
PROJECT_ELEMENT_HIER_VR
,
PROJECT_ELEMENT_HIER_BA
D
C_PurchOrganization_SAP
Purchasing Organization Dimension
from table T024E in SAP solutions
PURCH_ORGANIZATION
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
335
8
8
Technical Implementation
Project Cost Summary Section
Work Flow
Description
Tables
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)
C_VarianceCategory_SAP
Financial Variance Category
descriptive attributes (ABKAT
domain from DD07T). Load
VARIANCE_CATEGORY dimension
VARIANCE_CATEGORY
Project Costs are sourced from these SAP solutions tables:
•
•
•
•
RPSCO - Project info database: Costs, revenues, finances
AFVC - Operation within an order
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.
•
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
measures for the single fiscal period.
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.
336
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
PRT Assignment Section
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.
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.
In SAP solutions, the PRT’s are assigned to an Order Operation.
The Rapid Mart calls C_PRTAssignmentSection_SAP to load these tables.
This section first loads the required dimension components with work flow
WF_PRTAssignemntDims_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 information from CSLA and
CSLT
ACTIVITY
C_ActivityHier_SAP
Dimensional component loading
Cost Activity Hierarchy information
from CCSS-LSTAR and CSLA
ACTIVITY_HIER,
ACTIVITY_HIER_HZ,
ACTIVITY_HIER_VR,
ACTIVITY_HIER_BAD
C_BusinessArea_SAP
Dimensional component loading
Business Area information from
TGSB and TGSBT
BUSINESS_AREA
C_ChartofAccts_SAP
Chart of Accts (T004 and T004T) in
SAP solutions
CHART_OF_ACCOUNTS
C_CompanyCode_SAP
Dimensional component loading
Company Codes information from
T001
COMPANY_CODE
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
337
8
8
Technical Implementation
PRT Assignment Section
Work Flow
Description
Tables
C_ControlKey_SAP
Dimensional component loading
control key information and
descriptions from T430/T430T
CONTROL_KEY
C_ControllingArea_SAP
Dimensional component loading
Controlling Area information from
TKA01
CONTROLLING_AREA
C_CostCenter_SAP
Dimensional component loading
Cost Center information from CSKS
and CSKT
COST_CENTER
C_CostCenterHier_SAP
Dimensional component loading
Cost Center Hierarchy information
from CCSS-KOSTL and CSKS
COST_CENTER_HIER,
COST_CENTER_HIER_HZ,
COST_CENTER_HIER_VR,
COST_CENTER_HIER_BAD
C_CostElement_SAP
Dimensional component loading
Cost Element information from
CSKA and CSKU
COST_ELEMENT
C_CostElementHier_SAP
Dimensional component loading
Cost Element Hierarchy information
from CCSS-KSTAR and CSK1
COST_ELEMENT_HIER,
COST_ELEMENT_HIER_HZ,
COST_ELEMENT_HIER_VR,
COST_ELEMENT_HIER_BAD
C_FunctionalArea_SAP
Dimensional component loading
Functional Area information from
TFKB and TFKBT
FUNCTIONAL_AREA
C_FunctionalAreaHier_SAP
Functional Area Hierarchy from
GLFUNCT-RFAREA
FUNCTIONAL_AREA_HIER,
FUNCTIONAL_AREA_HIER_HZ,
FUNCTIONAL_AREA_HIER_VR,
FUNCTIONAL_AREA_HIER_BA
D
C_InternalOrder_SAP
Load INTERNAL_ORDER
dimension
INTERNAL_ORDER
C_InternalOrderHier_SAP
Dimensional component loading
Internal Order Hierarchy information
from CCSS-AUFNR and AUFK
INTERNAL_ORDER_HIER,
INTERNAL_ORDER_HIER_HZ,
INTERNAL_ORDER_HIER_VR,
INTERNAL_ORDER_HIER_BAD
C_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_MRPController_SAP
Dimensional component loading
MRP controller information from
T024D
MRP_CONTROLLER
C_ObjectNumberType_SAP
Object Key first 2 characters that
identify uniquely source table and
record from TBO01. Load
OBJECT_NUMBER_TYPE
OBJECT_NUMBER_TYPE
338
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
PRT Assignment Section
Work Flow
Description
Tables
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_ObjectType_SAP
Dimensional component loading
OBJECT_TYPE
Object Type information from various
modules -- This is a combined
dimension.
C_OrderOperation_SAP
Order Operation Master data - from
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_PlantLocation_SAP
Plant Location attributes from T499S PLANT_LOCATION
- PLANT_LOCATION
C_ProfitCenter_SAP
Dimensional component loading
Profit Center master data
(Dimension)
PROFIT_CENTER
C_ProfitCenterHier_SAP
Dimensional component loading
profit center hierarchy (EC-PCA
Profit center hierarchy in SAP
solutions)
PROFIT_CENTER_HIER,
PROFIT_CENTER_HIER_HZ,
PROFIT_CENTER_HIER_VR,
PROFIT_CENTER_HIER_BAD
C_Project_SAP
Dimensional component loading
project information
PROJECT
C_ProjectElement_SAP
Dimensional component loading
Project Element (WBS) master data
PROJECT_ELEMENT
C_ProjectElementHier_SAP
Dimensional component loading
project element hierarchy
information
PROJECT_ELEMENT_HIER,
PROJECT_ELEMENT_HIER_HZ
,
PROJECT_ELEMENT_HIER_VR
,
PROJECT_ELEMENT_HIER_BA
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
details from CRHF
PRT_MASTER
C_PRTStatus_SAP
Descriptive attributes for PRT status
from TCF05; load PRT_STATUS
dimension
PRT_STATUS
ORDER_OPERATION
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
339
8
8
Technical Implementation
PRT Assignment Section
Work Flow
Description
Tables
C_PurchOrganization_SAP
Purchasing Organization Dimension
from table T024E in SAP solutions
PURCH_ORGANIZATION
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
PLKO - ROUNTING
ROUTING
C_RoutingOperation_SAP
Details of Task List
operations/activities from PLPO populate ROUTING_OPERATION
dimension
ROUTING_OPERATION
C_RoutingSequence_SAP
Routing (Task List) sequence
definition from PLFL; load
ROUTING_SEQUENCE dimension
ROUTING_SEQUENCE
C_StandardTextKey_SAP
Dimensional component loading
work center standard text
descriptions from T435T
STANDARD_TEXT_KEY
C_StorageLocation_SAP
Dimensional component loading
storage location descriptions with
plant and division assignments from
T001L
STORAGE_LOCATION
C_TaskListType_SAP
Task List Type descriptive attributes
from TCA02 - TASK_LIST_TYPE
dimension
TASK_LIST_TYPE
C_TimeDim_SAP
Dimensional component loading
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 loaded. Modify
dates.dat file to change number of
dates
TIME_DIM
C_UnitOfMeasure_SAP
Populates Units of Measure
dimension during first and delta
loads from Table T006A in SAP
solutions
UNIT_OF_MEASURE
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)
C_WorkCenter_SAP
Load WORK_CENTER master data
dimension
WORK_CENTER
C_WorkCenterCategory_SAP
Work Center Category descriptive
attributes from TC30T
WORK_CENTER_CATEGORY
340
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
PRT Assignment Section
Work Flow
Description
Tables
C_WorkCenterFormula_SAP
Dimensional component loading
work center formulas from TC25
and parameters and constants from
TC20 - FORMULAS
WORK_CENTER_FORMULA,
FORMULA_PARAMETER
C_WorkCenterHier_SAP
Work Center Hierarchical
relationship in Horizontal and Vertical
formats from CRHH/CRHS; load
WORK_CENTER_HIER,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_HZ
WORK_CENTER_HIER,
WORK_CENTER_HIER_HZ,
WORK_CENTER_HIER_VR,
WORK_CENTER_HIER_BAD
The PRT Assignment section extracts operation level data from these SAP
solutions tables:
•
•
•
AFVC - Operation within an order
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
The Rapid Mart selects only Operations that have a PRT assigned by inner
joining the source tables in SAP solutions.
Initial (First) Load
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
341
8
8
Technical Implementation
Rolling Totals Calculation
Incremental (Delta) Load
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
$G_SDATE, and $G_EDATE the production order will be extracted.
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.
Rolling Totals Calculation
Vertical summary tables in several Rapid Marts use Rolling 16 Fiscal Period
Totals. These totals present the last 16 months of Period-To-Date values
summed, for each set of primary keys in the table. The vertical summary
tables with rolling totals are:
Rapid Mart
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.
342
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Rolling Totals Calculation
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...
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
343
8
8
Technical Implementation
Rolling Totals Calculation
PTDBALQuery - 1. Calculate PTD Values:
“PTD” values are calculated by subtracting Credits from Debits.
344
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Rolling Totals Calculation
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
345
8
8
Technical Implementation
Rolling Totals Calculation
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.
346
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Rolling Totals Calculation
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
347
8
8
Technical Implementation
Rolling Totals Calculation
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:
348
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Rolling Totals Calculation
They are defined as Parameters at the Data Flow level:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
349
8
8
Technical Implementation
Rolling Totals Calculation
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.
350
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Rolling Totals Calculation
An example of the output generated by this type of data flow and the Rolling
Totals Function are shown below.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
351
8
8
Technical Implementation
Optimization Techniques
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:
352
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Optimization Techniques
•
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
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
353
8
8
Technical Implementation
Optimization Techniques
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.
354
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Optimization Techniques
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:
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
355
8
8
Technical Implementation
Optimization Techniques
Before Split (Single Data Flow):
After Split 1 of 2 Data Flows (Horizontal):
356
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Optimization Techniques
After Split 2 of 2 Data Flows (Vertical):
The 2 Split Data Flows in Context.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
357
8
8
Technical Implementation
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.
358
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Fact Table Stored Procedures
Fact Table Stored Procedures
When loading each fact table the Rapid Mart calls two stored procedures. A
PREPROCESSING_FACT_TABLE procedure is called before loading the fact
table and a POSTPROCESSING_FACT_TABLE procedure is called when
the load is finished.
The procedures, as delivered with the Rapid Mart, are only placeholders. The
Oracle version of the placeholder procedures is shown below:
CREATE OR REPLACE PROCEDURE
postprocessing_fact_table(pLoadType IN VARCHAR2,
pDropCreateIndex IN VARCHAR2, pFactTable IN VARCHAR2,
pMView_Failures OUT BINARY_INTEGER) IS
BEGIN
NULL;
END postprocessing_fact_table;
CREATE OR REPLACE PROCEDURE
preprocessing_fact_table(pLoadType IN VARCHAR2,
pDropCreateIndex IN VARCHAR2, pFactTable IN VARCHAR2)
IS
BEGIN
NULL;
END preprocessing_fact_table;
In order to use these procedures as a performance tuning tool, you need to
customize them. The Rapid Mart provides a sample script (for Oracle only):
•
Create_Sample_Maintenance_SP.sql
The sample PREPROCESSING_FACT_TABLE procedure will drop all
indexes and all materialized view logs enabled for the fact table. This should
reduce load time for the fact table in Data Services.
The POSTPROCESSING_FACT_TABLE procedure will recreate logs and
indexes. See the Rapid Mart Deployment Guide for details.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
359
8
8
Technical Implementation
Fiscal Periods & Time Dim Load
Fiscal Periods & Time Dim Load
These two dimensions use a text file named dates.dat to define the range of
dates you load. The file must be located in the Working Directory you defined
in your R/3 Data Store
360
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Technical Implementation
Fiscal Periods & Time Dim Load
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.
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
361
8
8
Technical Implementation
Fiscal Periods & Time Dim Load
362
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
chapter
Documentation References
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:
•
•
364
Administration Guide
Deployment and Configuration Guide
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
Documentation References
BusinessObjects Enterprise Documentation References
•
•
•
•
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)
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
365
9
9
Documentation References
BusinessObjects Enterprise Documentation References
366
SAP BusinessObjects Project Systems Rapid Mart XI 3.2 for SAP solutions User Guide
appendix
Rapid Mart Data Schema
Appendix
Table Summary
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
A
Appendix
Table Summary
● 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
Rapid Mart Data Schema
2
A
Appendix
Table Summary
● 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
Rapid Mart Data Schema
3
A
Appendix
Table Column Details
A
ACCT_ASSIGNMENT_CATEGORY
T163I and T163K - Texts for Account Assignment Categories
Column Desc
Column
Datatype
ACCT_ASSIGN_CATE PK
G_ID
T613I.KNTTP - Account assignment category
NVARCSTR
1
0
0
no
2
ACCT_ASSIGN_DESC
R
T163I.KNTTX - Account assignment category
description
NVARCSTR
20
0
0
yes
3
CONSUMP_DESCR
Lookup text description of T613K.KZVBR
NVARCSTR
20
0
0
yes
4
CONSUMP_ID
T163K.KZVBR - Indicator: consumption
posting, purchasing
NVARCSTR
1
0
0
yes
5
GOODS_RECPT_FL
AG
T163K.WEPOS- Goods receipt indicator
NVARCSTR
1
0
0
yes
6
INVOICE_RECPT_FLA
G
T163K.REPOS- Invoice receipt indicator
NVARCSTR
1
0
0
yes
7
LOAD_DATE
Load date
DATETIME
24
0
9
yes
8
LOAD_TIME
Load time
NVARCSTR
8
0
0
yes
9
SPECL_STOCK_DESC
R
Lookup text description of T163K.SOBKZ
NVARCSTR
20
0
0
yes
10
SPECL_STOCK_ID
T163K.SOBKZ- Special stock indicator
NVARCSTR
1
0
0
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
1
Appendix
Table Column Details
A
ACTIVITY
Activity Master (CSLA, CSLT)
Column Desc
Column
Datatype
ACTIVITY_DESCR
CSLT-LTEXT-Description
NVARCSTR
40
0
0
yes
2
ACTIVITY_FULL_NAM
E
Activity ID and Description
NVARCSTR
120
0
0
yes
3
ACTIVITY_ID
CSLA-LSTAR-Activity type
NVARCSTR
6
0
0
no
4
ACTIVITY_NAME
CSLT-KTEXT-Name
NVARCSTR
20
0
0
yes
5
ACTIVITY_TYPE_CAT
EG_CODE
CSLA-LATYPE-Activity type category
NVARCSTR
1
0
0
yes
6
ALLOCTN_COST_ELE
M_ID
CSLA-VKSTA-Allocation cost element
NVARCSTR
10
0
0
yes
7
CREATED_BY
CSLA-USNAM-Created by
NVARCSTR
12
0
0
yes
8
CREATE_DATE
CSLA-ERSDA-Created on
DATETIME
24
0
9
yes
9
CTRL_AREA_ID
CSLA-KOKRS-Controlling area
NVARCSTR
4
0
0
no
10
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
11
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
12
OUTPUT_FACTOR
CSLA-AUSFK-Output factor
DECIMAL
48
5
2
yes
13
UOM_ID
CSLA-LEINH-Activity unit
NVARCSTR
3
0
0
yes
14
UOM_ID_OUTPUT
CSLA-AUSEH-Output unit
NVARCSTR
3
0
0
yes
15
VALID_FROM_DATE
CSLA-DATAB-Date valid from
DATETIME
24
0
9
yes
16
VALID_TO_DATE
CSLA-DATBI-Valid to date
DATETIME
24
0
9
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
2
Appendix
Table Column Details
A
ACTIVITY_HIER
Activity Hierarchy information - CCSS-LSTAR -- Note Does NOT Have a Primary Key due to duplication possible in SAP
Column Desc
Column
Datatype
CCSS-LSTAR-Activity Hierarchy Child ID
Description
NVARCSTR
64
0
0
yes
PK
CCSS-LSTAR-Child Activity ID
NVARCSTR
12
0
0
no
CTRL_AREA_ID
PK
CCSS-LSTAR-Controling Area
NVARCSTR
4
0
0
no
4
LEAF_FLAG
PK
CCSS-LSTAR-Indicates if the Child ID doesn't
have any subordinate leaves
NVARCSTR
1
0
0
no
5
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
6
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
7
PARENT_DESCR
CCSS-LSTAR-Activity Hierarchy Parent ID
Description
NVARCSTR
64
0
0
yes
8
PARENT_ID
PK
CCSS-LSTAR-Parent Activity ID
NVARCSTR
12
0
0
no
9
ROOT_FLAG
PK
CCSS-LSTAR-Indicates if the Parent ID is a
root of an activity group hierarchy
NVARCSTR
1
0
0
no
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
3
Appendix
Table Column Details
A
ACTIVITY_HIER_BAD
CCSS-LSTAR Activity Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
CCSS-LSTAR-Activity Hierarchy Child ID
Description
NVARCSTR
64
0
0
yes
PK
CCSS-LSTAR-Child Activity ID
NVARCSTR
12
0
0
no
PK
CCSS-LSTAR-Controling Area
NVARCSTR
4
0
0
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
5
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
6
LEAF_FLAG
CCSS-LSTAR-Indicates if the Child ID doesn't
have any subordinate leaves
NVARCSTR
1
0
0
no
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
PARENT_DESCR
CCSS-LSTAR-Activity Hierarchy Parent ID
Description
NVARCSTR
64
0
0
yes
10
PARENT_ID
PK
CCSS-LSTAR-Parent Activity ID
NVARCSTR
12
0
0
no
11
ROOT_FLAG
PK
CCSS-LSTAR-Indicates if the Parent ID is a
root of an activity group hierarchy
NVARCSTR
1
0
0
no
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
CTRL_AREA_ID
4
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
4
Appendix
Table Column Details
A
ACTIVITY_HIER_HZ
Activity Hierarchy Horizontal Flattening - CCSS-LSTAR -- Cannot have a primary key due to duplication of entries possible in SAP
#
Column Name
Key
Column Desc
Column
Datatype
1
ACTIVITY_ID
PK
CCSS-LSTAR-Leaf of the Activity Group
Hierarchy
NVARCSTR
12
0
0
no
2
CTRL_AREA_ID
PK
CCSS-LSTAR-Controling Area
NVARCSTR
4
0
0
no
3
LEAF_LVL
CCSS-LSTAR-Depth of the leaf from the
parent
INTEGER
4
0
0
no
4
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
6
LVL_00_DESCR
CCSS-LSTAR-Activity Hierarchy Level_0_ID
Description
NVARCSTR
64
0
0
yes
7
LVL_00_FULL_NAME
Activity ID and Descripiton for Root
NVARCSTR
120
0
0
yes
8
LVL_00_ID
CCSS-LSTAR-Root of the Activity Group
Hierarchy
NVARCSTR
12
0
0
no
9
LVL_01_DESCR
CCSS-LSTAR-Activity Hierarchy Level_1_ID
Description
NVARCSTR
64
0
0
yes
10
LVL_01_FULL_NAME
Activity ID and Descripiton for Level 1
NVARCSTR
120
0
0
yes
11
LVL_01_ID
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
12
LVL_02_DESCR
CCSS-LSTAR-Activity Hierarchy Level_2_ID
Description
NVARCSTR
64
0
0
yes
13
LVL_02_FULL_NAME
Activity ID and Descripiton for level 2
NVARCSTR
120
0
0
yes
14
LVL_02_ID
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
15
LVL_03_DESCR
CCSS-LSTAR-Activity Hierarchy Level_3_ID
Description
NVARCSTR
64
0
0
yes
16
LVL_03_FULL_NAME
Activity ID and Description for Level 3
NVARCSTR
120
0
0
yes
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
5
Appendix
Table Column Details
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
LVL_04_DESCR
CCSS-LSTAR-Activity Hierarchy Level_4_ID
Description
NVARCSTR
64
0
0
yes
19
LVL_04_FULL_NAME
Activity ID and Description for Level 4
NVARCSTR
120
0
0
yes
20
LVL_04_ID
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
21
LVL_05_DESCR
CCSS-LSTAR-Activity Hierarchy Level_5_ID
Description
NVARCSTR
64
0
0
yes
22
LVL_05_FULL_NAME
Activity ID and Description for Level 5
NVARCSTR
120
0
0
yes
23
LVL_05_ID
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
24
LVL_06_DESCR
CCSS-LSTAR-Activity Hierarchy Level_6_ID
Description
NVARCSTR
64
0
0
yes
25
LVL_06_FULL_NAME
Activity ID and Description for Level 6
NVARCSTR
120
0
0
yes
26
LVL_06_ID
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
27
LVL_07_DESCR
CCSS-LSTAR-Activity Hierarchy Level_7_ID
Description
NVARCSTR
64
0
0
yes
28
LVL_07_FULL_NAME
Activity ID and Description for level 7
NVARCSTR
120
0
0
yes
29
LVL_07_ID
CCSS-LSTAR-A group or a Activity ID. It is null
when the hierarchy ended with a lower
NVARCSTR
numbered node.
12
0
0
no
17
LVL_03_ID
18
PK
PK
PK
PK
PK
Rapid Mart Data Schema
A
6
Appendix
Table Column Details
A
ACTIVITY_HIER_VR
Activity Hierarchy Vertical Flattening - CCSS-LSTAR - cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
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
4
CTRL_AREA_ID
PK
CCSS-LSTAR-Controling Area
NVARCSTR
4
0
0
no
5
DEPTH
CCSS-LSTAR-Depth of the descendant from
the ancestor
INTEGER
4
0
0
yes
6
LEAF_FLAG
CCSS-LSTAR-Indicates if the Parent ID is a
leaf of an activity group hierarchy
INTEGER
4
0
0
yes
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
PARENT_DESCR
CCSS-LSTAR-Description of the ancestor
NVARCSTR
64
0
0
yes
10
PARENT_FULL_NAME
Parent Activity ID and Description
NVARCSTR
120
0
0
yes
11
PARENT_ID
CCSS-LSTAR-Activity Hierarchy Parent ID
NVARCSTR
12
0
0
no
12
ROOT_FLAG
CCSS-LSTAR-Indicates if the Parent ID is a
root of an activity group hierarchy
INTEGER
4
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Is
Nullable
AW_DIMENSION_SOURCE
Master list of values indicating sources of combined dimensions
#
Column Name
1
DIM_SRC_DESCR
2
DIM_SRC_ID
Key
PK
Column Desc
Column
Datatype
Dtype
Length Precision Scale
Description of Dimension Source
NVARCSTR
60
0
0
yes
Dimension Source. Used in combined
dimension combining similar attributes from
different sources in SAP.
NVARCSTR
30
0
0
no
Rapid Mart Data Schema
Is
Nullable
7
Appendix
Table Column Details
A
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 Desc
Column
Datatype
$G_EDATE global variable setting at the time
of the "First" or "Delta" run.
DATETIME
24
0
0
yes
PK
Will be FIRST or DELTA
NVARCSTR
10
0
0
no
PK
Name of the Rapid Mart Load Job.
NVARCSTR
100
0
0
no
JOB_START_DATE
$G_SDATE global variable setting at the time
of the "First" or "Delta" run.
DATETIME
24
0
0
yes
5
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
0
yes
6
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
Column Desc
Column
Datatype
#
Column Name
1
JOB_END_DATE
2
JOB_LOAD_TYPE
3
JOB_NAME
4
Key
Dtype
Length Precision Scale
Is
Nullable
AW_JOBEXECUTION
Job Execution Status table
Key
Dtype
Length Precision Scale
Is
Nullable
#
Column Name
1
EXTRACTHIGH
End Date
NVARCSTR
10
0
0
yes
2
EXTRACTLOW
Start Date
NVARCSTR
10
0
0
yes
3
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
0
yes
4
NAME
Job Name
NVARCSTR
64
0
0
no
5
STATUS
Job Status
NVARCSTR
12
0
0
yes
PK
Rapid Mart Data Schema
8
Appendix
Table Column Details
A
AW_LOOKUP_INDEX
Auxilary table to store index information
Column Desc
Column
Datatype
ADDTNL_TXT
Notes
NVARCSTR
64
0
0
yes
2
COLUMN_NAME_01
Index column 1
NVARCSTR
64
0
0
yes
3
COLUMN_NAME_02
Index column 2
NVARCSTR
64
0
0
yes
4
COLUMN_NAME_03
Index column 3
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
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
9
Appendix
Table Column Details
A
BUSINESS_ACTIVITY
FK-SL Activity attributes from T022/T022T
Column Desc
Column
Datatype
T022T.TXT -Text (30 Characters)
NVARCSTR
30
0
0
yes
T022.ACTIVITY -FI-SL Business Transaction
NVARCSTR
4
0
0
no
BUS_ACTIVITY_TYPE
_DESCR
lookup on VORGTYP domain in DD07T
NVARCSTR
60
0
0
yes
4
BUS_ACTIVITY_TYPE
_ID
T022.VORGTYP -Activity type for FI-SL
activities
NVARCSTR
1
0
0
yes
5
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
6
LOAD_TIME
Time Loaded into Rapid mart
NVARCSTR
8
0
0
yes
7
RECORD_TYPE_DE
SCR
lookup on RRCTY domain in DD07T
NVARCSTR
60
0
0
yes
8
RECORD_TYPE_ID
T022.SATZTYP -Record Type
NVARCSTR
1
0
0
yes
Column Desc
Column
Datatype
#
Column Name
1
BUS_ACTIVITY_DESC
R
2
BUS_ACTIVITY_ID
3
Key
PK
Dtype
Length Precision Scale
Is
Nullable
BUSINESS_AREA
Business Areas - TGSB, TSGBT
Key
Dtype
Length Precision Scale
Is
Nullable
#
Column Name
1
BUS_AREA_DESCR
TGSBT-GTEXT-Business area description
NVARCSTR
30
0
0
yes
2
BUS_AREA_FULL_NA
ME
Business Area ID and Descritpion
NVARCSTR
120
0
0
yes
3
BUS_AREA_ID
TGSB-GSBER-Business area
NVARCSTR
4
0
0
no
4
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
8
0
0
yes
PK
NVARCSTR
Rapid Mart Data Schema
10
Appendix
Table Column Details
A
CHART_OF_ACCOUNTS
Chart of Accounts in SAP (T004 and T004T tables)
Column Desc
Column
Datatype
CHART_OF_ACCT_FU
LL_NAME
Chart of accounts full name
NVARCSTR
120
0
0
yes
2
CHART_OF_ACCT_ID PK
Chart of accounts
NVARCSTR
4
0
0
no
3
CHART_OF_ACCT_NA
ME
Chart of accounts description
NVARCSTR
50
0
0
yes
4
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
8
0
0
yes
#
Column Name
1
Key
NVARCSTR
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
11
Appendix
Table Column Details
A
COMPANY_CODE
T001 - Company Code master
Column Desc
Column
Datatype
ADDRESS_ID
Company default address identifier
NVARCSTR
10
0
0
yes
2
CHART_OF_ACCT_ID
Company Code chart of accounts
NVARCSTR
4
0
0
yes
3
CHART_OF_ACCT_ID
_COUNTRY
Chart of Accounts according to country
legislation
NVARCSTR
4
0
0
yes
4
CHART_OF_ACCT_NA
ME
Chart of Accounts Name
NVARCSTR
50
0
0
yes
5
CITY
Company City Name
NVARCSTR
40
0
0
yes
6
CMPNY_CODE_FULL_
NAME
Company Code and Name
NVARCSTR
120
0
0
yes
7
CMPNY_CODE_ID
T001-BURKS - Company Code ID
NVARCSTR
4
0
0
no
8
CMPNY_CODE_ID_OR
IGINAL
Original Key of Company Code
NVARCSTR
4
0
0
yes
9
CMPNY_CODE_NAME
Company Code Name
NVARCSTR
40
0
0
yes
10
CMPNY_CODE_NAM
E_01
Name of the Company - 1st description
NVARCSTR
40
0
0
yes
11
CMPNY_CODE_NAM
E_02
Name of the Company - 2nd description
NVARCSTR
40
0
0
yes
12
CMPNY_CODE_NAM
E_03
Name of the Company - 3rd description
NVARCSTR
40
0
0
yes
13
CMPNY_CODE_NAM
E_04
Name of the Company - 4th description
NVARCSTR
40
0
0
yes
14
COUNTRY_ID
Country Identifier
NVARCSTR
3
0
0
yes
15
COUNTRY_NAME
Country Name (lookup)
NVARCSTR
15
0
0
yes
16
CR_CTRL_AREA_DES
CR
Credit Controlling Area description
NVARCSTR
35
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
12
Appendix
Table Column Details
17
CR_CTRL_AREA_ID
Credit Control area
NVARCSTR
4
0
0
yes
18
CURR_ID
Company Code Currency ID
NVARCSTR
5
0
0
yes
19
DISTRICT
District of the Company
NVARCSTR
40
0
0
yes
20
FAX
Fax no of the Company
NVARCSTR
40
0
0
yes
21
FIN_MGMT_AREA_ID
Financial Management Area
NVARCSTR
4
0
0
yes
22
FISC_YR_VARIANT_ID
Company code fiscal year variant
NVARCSTR
2
0
0
yes
23
FISC_YR_VARIANT_N
AME
Company code fiscal year variant name
NVARCSTR
30
0
0
yes
24
HOUSE_NUMBER
Company code house number
NVARCSTR
10
0
0
yes
25
LANG_DESCR
Company code language Description
NVARCSTR
16
0
0
yes
26
LANG_ID
Company Code default language
NVARCSTR
1
0
0
yes
27
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
28
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
29
PHONE
Company code telephone number
NVARCSTR
30
0
0
yes
30
REGION_ID
Company code region
NVARCSTR
3
0
0
yes
31
REGION_NAME
Company code region name
NVARCSTR
20
0
0
yes
32
STREET
Company code street name
NVARCSTR
60
0
0
yes
33
TAX_JURISDIC_NUM
Jurisdiction fo tax calculation - tax jurisdiction
code
NVARCSTR
15
0
0
yes
34
VAT_REGISTRTN_NU
M
VAT regulation number
NVARCSTR
20
0
0
yes
Rapid Mart Data Schema
A
13
Appendix
Table Column Details
35
ZIP
Company code postal code
NVARCSTR
10
0
0
A
yes
CONTROL_KEY
Business transactions should be executed for the object that belongs to the task list or order (from T430)
Column Desc
Column
Datatype
AUTO_GR_FLAG
T430.AUTWE - Indicator: automatic goods
receipt
NVARCSTR
1
0
0
yes
2
CAPACITY_PLAN_FLA
G
T430.KAPA - Indicator: Capacity planning
NVARCSTR
1
0
0
yes
3
CONFIRMATN_FLAG_
DESCR
Lookup description of confirmation indicator
NVARCSTR
60
0
0
yes
4
CONFIRMATN_FLAG_I
D
T430.RUEK - Indicator: completion
confirmation
NVARCSTR
1
0
0
yes
5
CTRL_KEY_DESCR
Lookup description of control key
NVARCSTR
40
0
0
yes
6
CTRL_KEY_ID
T430.STEUS - Control key
NVARCSTR
4
0
0
no
7
INSPECTN_FLAG
T430.MRKKZ - Indicator: inspection
characteristics for operation require
NVARCSTR
1
0
0
yes
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
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
14
Appendix
Table Column Details
A
CONTROLLING_AREA
TKA01 - Controlling areas master
Column Desc
Column
Datatype
CTRL_AREA_DESCR
Controlling Area Name
NVARCSTR
25
0
0
yes
2
CTRL_AREA_FULL_N
AME
Controlling Area DI and Desc
NVARCSTR
120
0
0
yes
3
CTRL_AREA_ID
TKA01-KORKS - Controlling Area ID
NVARCSTR
4
0
0
no
4
CURR_ID
Currency Code for Controlling Area
NVARCSTR
5
0
0
yes
5
FISC_YR_VARIANT_ID
Fiscal Year Variant
NVARCSTR
2
0
0
yes
6
LEDGER_ID_PROFIT_
CNTR
Financial Ledger ID profit Center
NVARCSTR
2
0
0
yes
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
OPERTNG_CONCER
N_ID
Operating Concern
NVARCSTR
4
0
0
yes
10
PROFIT_CNTR_AREA
Profit Center Group
NVARCSTR
12
0
0
yes
11
STD_SET_HIER_COD
E
Standard Hierarchy for Cost Centers
NVARCSTR
12
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
15
Appendix
Table Column Details
A
COST_CENTER
CSKS - Cost Center Master
Column Desc
Column
Datatype
ALT_FUNCTN
CSKS.AFUNK - Alternative function of Cost
Center
NVARCSTR
3
0
0
yes
2
BUS_AREA_ID
Business Area ID
NVARCSTR
4
0
0
yes
3
CITY
Cost Center City Name
NVARCSTR
40
0
0
yes
4
CMPNY_CODE_ID
Company Code ID
NVARCSTR
4
0
0
yes
5
CMPNY_CODE_NAME
Company code name associated with this Cost NVARCSTR
Center
40
0
0
yes
6
COST_CNTR_DESCR
Cost Center Descritpion
NVARCSTR
60
0
0
yes
7
COST_CNTR_FULL_N
AME
Cost Center ID and Desc
NVARCSTR
120
0
0
yes
8
COST_CNTR_ID
CSKS-KOSTL - Cost Center ID
NVARCSTR
10
0
0
no
9
COST_CNTR_ID_SUB
SEQUENT
CSKS.NKOST - Subsequent Cost Center ID
NVARCSTR
10
0
0
yes
10
COST_CNTR_NAME
Cost Center Default Name
NVARCSTR
40
0
0
yes
11
COST_CNTR_NAME_0
1
Cost Center Name Line 1
NVARCSTR
40
0
0
yes
12
COST_CNTR_NAME_0
2
Cost Center Name Line 2
NVARCSTR
40
0
0
yes
13
COST_CNTR_NAME_0
3
Cost Center Name Line 3
NVARCSTR
40
0
0
yes
14
COST_CNTR_NAME_0
4
Cost Center Name Line 4
NVARCSTR
40
0
0
yes
15
COUNTRY_ID
Cost Center Country Code
NVARCSTR
3
0
0
yes
16
COUNTRY_NAME
Cost Center Country Name
NVARCSTR
15
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
16
Appendix
Table Column Details
17
CREATED_BY
Person ID who created the record
NVARCSTR
12
0
0
yes
18
CREATE_DATE
Date when the record was created in the
source system
DATETIME
24
0
9
yes
19
CTRL_AREA_DESCR
Control Area description
NVARCSTR
25
0
0
yes
20
CTRL_AREA_ID
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
27
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
28
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
29
PERSON_IN_CHARGE
CSKS.VERAK - Cost Center Manager
NVARCSTR
20
0
0
yes
30
PHONE
Cost Center phone # 1
NVARCSTR
30
0
0
yes
31
PROFIT_CNTR_DESC
R
Profit Center Description
NVARCSTR
40
0
0
yes
32
PROFIT_CNTR_ID
CSKS.PRCTR - Profit Center Code
NVARCSTR
10
0
0
yes
33
REGION_ID
Region ID
NVARCSTR
3
0
0
yes
34
REGION_NAME
Region name
NVARCSTR
20
0
0
yes
PK
Rapid Mart Data Schema
A
17
Appendix
Table Column Details
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
A
COST_CENTER_HIER
Cost Center Hierarchy - CCSS-KOSTL - Cannot have a primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
Cost Center Child description
NVARCSTR
64
0
0
yes
PK
Cost Center Child Node ID
NVARCSTR
12
0
0
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
4
0
0
no
4
LEAF_FLAG
PK
Is Leaf
NVARCSTR
1
0
0
no
5
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
6
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
18
Appendix
Table Column Details
A
COST_CENTER_HIER_BAD
CCSS-KOSTL Cost Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
Cost Center Child description
NVARCSTR
64
0
0
yes
PK
Cost Center Child Node ID
NVARCSTR
12
0
0
no
PK
Controlling Area ID
NVARCSTR
4
0
0
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
5
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
6
LEAF_FLAG
Is Leaf
NVARCSTR
1
0
0
no
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
11
ROOT_FLAG
PK
Is Root
NVARCSTR
1
0
0
no
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
CTRL_AREA_ID
4
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
19
Appendix
Table Column Details
A
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 Name
Key
Column Desc
Column
Datatype
1
COST_CNTR_ID
PK
Cost Center ID (current node)
NVARCSTR
12
0
0
no
2
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
4
0
0
no
3
LEAF_LVL
Is Leaf Level
INTEGER
4
0
0
no
4
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
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
10
LVL_01_FULL_NAME
Cost Center ID and Desc for Level 1
NVARCSTR
120
0
0
yes
11
LVL_01_ID
Cost Center level 1 Node ID
NVARCSTR
12
0
0
no
12
LVL_02_DESCR
Cost Center level 2 Node Description
NVARCSTR
64
0
0
yes
13
LVL_02_FULL_NAME
Cost Center Id and Desc for Level 2
NVARCSTR
120
0
0
yes
14
LVL_02_ID
Cost Center level 2 Node ID
NVARCSTR
12
0
0
no
15
LVL_03_DESCR
Cost Center level 3 Node Description
NVARCSTR
64
0
0
yes
16
LVL_03_FULL_NAME
Cost Center ID and Desc for Level 3
NVARCSTR
120
0
0
yes
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
20
Appendix
Table Column Details
17
LVL_03_ID
18
PK
Cost Center level 3 Node ID
NVARCSTR
12
0
0
no
LVL_04_DESCR
Cost Center level 4 Node Description
NVARCSTR
64
0
0
yes
19
LVL_04_FULL_NAME
Cost Center ID and Desc for Level 4
NVARCSTR
120
0
0
yes
20
LVL_04_ID
Cost Center level 4 Node ID
NVARCSTR
12
0
0
no
21
LVL_05_DESCR
Cost Center level 5 Node Description
NVARCSTR
64
0
0
yes
22
LVL_05_FULL_NAME
Cost Center ID and Desc for Level 5
NVARCSTR
120
0
0
yes
23
LVL_05_ID
Cost Center level 5 Node ID
NVARCSTR
12
0
0
no
24
LVL_06_DESCR
Cost Center level 6 Node Description
NVARCSTR
64
0
0
yes
25
LVL_06_FULL_NAME
Cost Center Id and Desc for Level 6
NVARCSTR
120
0
0
yes
26
LVL_06_ID
Cost Center level 6 Node ID
NVARCSTR
12
0
0
no
27
LVL_07_DESCR
Cost Center level 7 Node Description
NVARCSTR
64
0
0
yes
28
LVL_07_FULL_NAME
Cost Center Id and Dec for Level 7
NVARCSTR
120
0
0
yes
29
LVL_07_ID
Cost Center level 7 Node ID
NVARCSTR
12
0
0
no
30
LVL_08_DESCR
Cost Center level 8 Node Description
NVARCSTR
64
0
0
yes
31
LVL_08_FULL_NAME
Cost Center ID and Desc for Level 8
NVARCSTR
120
0
0
yes
32
LVL_08_ID
Cost Center level 8 Node ID
NVARCSTR
12
0
0
no
33
LVL_09_DESCR
Cost Center level 9 Node Description
NVARCSTR
64
0
0
yes
34
LVL_09_FULL_NAME
Cost Center Id and Desc for Level 9
NVARCSTR
120
0
0
yes
PK
PK
PK
PK
PK
Rapid Mart Data Schema
A
21
Appendix
Table Column Details
35
LVL_09_ID
36
PK
Cost Center level 9 Node ID
NVARCSTR
12
0
0
no
LVL_10_DESCR
Cost Center level 10 Node Description
NVARCSTR
64
0
0
yes
37
LVL_10_FULL_NAME
Cost Center ID and Desc for Level 10
NVARCSTR
120
0
0
yes
38
LVL_10_ID
Cost Center level 10 Node ID
NVARCSTR
12
0
0
no
PK
A
COST_CENTER_HIER_VR
CCSS-KOSTL - Cost Center Hierarchy vertically flattenned - cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
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
4
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
4
0
0
no
5
DEPTH
Node depth level
INTEGER
4
0
0
yes
6
LEAF_FLAG
Is Leaf
INTEGER
4
0
0
yes
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
PARENT_DESCR
Cost Center Child Node Descritpion
NVARCSTR
64
0
0
yes
10
PARENT_FULL_NAME
Cost Center Parent ID and Desc
NVARCSTR
120
0
0
yes
11
PARENT_ID
Cost Center Child Node ID
NVARCSTR
12
0
0
no
12
ROOT_FLAG
Is Root
INTEGER
4
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
22
Appendix
Table Column Details
A
COST_ELEMENT
CSKA - Cost Element (GL Accounts) Master
Column Desc
Column
Datatype
CHART_OF_ACCT_ID PK
Accounting Chart of accounts ID
NVARCSTR
4
0
0
no
2
COST_ELEM_DESCR
Cost center description in default language
NVARCSTR
40
0
0
yes
3
COST_ELEM_FULL_N
AME
Cost Element ID and Description
NVARCSTR
120
0
0
yes
4
COST_ELEM_ID
Cost Element (GL Account) ID
NVARCSTR
10
0
0
no
5
CREATE_DATE
Date when the record was created in the
source system
DATETIME
24
0
9
yes
6
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
8
PAYMNT_RELEVNT_F
LAG
CSKA.ZAHKZ - Cost element is
payment-relevant
NVARCSTR
1
0
0
yes
9
TAX_RELEVNT_FLAG
CSKA.STEKZ - Cost Element is tax-relevant
NVARCSTR
1
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
23
Appendix
Table Column Details
A
COST_ELEMENT_HIER
CCSS-KSTAR Cost Element hierarchy - cannot have primary key due to data duplication possible in SAP
Column Desc
Column
Datatype
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
4
LEAF_FLAG
PK
Is Leaf
NVARCSTR
1
0
0
no
5
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
6
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
9
ROOT_FLAG
PK
Is Root
NVARCSTR
1
0
0
no
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
24
Appendix
Table Column Details
A
COST_ELEMENT_HIER_BAD
CCSS-KSTAR Cost ElementHierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
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
Cost Element Child Node ID
NVARCSTR
12
0
0
no
4
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
5
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
6
LEAF_FLAG
Is Leaf
NVARCSTR
1
0
0
no
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
11
ROOT_FLAG
PK
Is Root
NVARCSTR
1
0
0
no
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
25
Appendix
Table Column Details
A
COST_ELEMENT_HIER_HZ
CCSS-KSTAR - Cost Element Hierarchy- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
CHART_OF_ACCT_ID PK
Accounting Chart Of Account ID
NVARCSTR
4
0
0
no
2
COST_ELEM_ID
Cost Element (GL Account) ID
NVARCSTR
12
0
0
no
3
LEAF_LVL
Cost Element Leaf level (depth)
DECIMAL
48
28
0
no
4
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
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
Cost Element Level 1 Node ID
NVARCSTR
12
0
0
no
12
LVL_02_DESCR
Cost Element Level 2 Node Description
NVARCSTR
64
0
0
yes
13
LVL_02_FULL_NAME
Cost Element ID and Desc for Level 2
NVARCSTR
120
0
0
yes
14
LVL_02_ID
Cost Element Level 2 Node ID
NVARCSTR
12
0
0
no
15
LVL_03_DESCR
Cost Element Level 3 Node Description
NVARCSTR
64
0
0
yes
16
LVL_03_FULL_NAME
Cost Element ID and Desc for Level 3
NVARCSTR
120
0
0
yes
#
Column Name
1
Key
PK
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
26
Appendix
Table Column Details
17
LVL_03_ID
18
PK
Cost Element Level 3 Node ID
NVARCSTR
12
0
0
no
LVL_04_DESCR
Cost Element Level 4 Node Description
NVARCSTR
64
0
0
yes
19
LVL_04_FULL_NAME
Cost Element ID and Desc for Level 4
NVARCSTR
120
0
0
yes
20
LVL_04_ID
Cost Element Level 4 Node ID
NVARCSTR
12
0
0
no
21
LVL_05_DESCR
Cost Element Level 5 Node Description
NVARCSTR
64
0
0
yes
22
LVL_05_FULL_NAME
Cost Element ID and Desc for Level 5
NVARCSTR
120
0
0
yes
23
LVL_05_ID
Cost Element Level 5 Node ID
NVARCSTR
12
0
0
no
24
LVL_06_DESCR
Cost Element Level 6 Node Description
NVARCSTR
64
0
0
yes
25
LVL_06_FULL_NAME
Cost Element ID and Desc for Level 6
NVARCSTR
120
0
0
yes
26
LVL_06_ID
Cost Element Level 6 Node ID
NVARCSTR
12
0
0
no
27
LVL_07_DESCR
Cost Element Level 7 Node Description
NVARCSTR
64
0
0
yes
28
LVL_07_FULL_NAME
Cost Element ID and Desc for Level 7
NVARCSTR
120
0
0
yes
29
LVL_07_ID
Cost Element Level 7 Node ID
NVARCSTR
12
0
0
no
PK
PK
PK
PK
Rapid Mart Data Schema
A
27
Appendix
Table Column Details
A
COST_ELEMENT_HIER_VR
CCSS-KSTAR - Cost Element Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
CHART_OF_ACCT_ID PK
Accounting Chart of Accounts ID
NVARCSTR
4
0
0
no
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
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
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
PARENT_DESCR
Cost Element Child Node Description
NVARCSTR
64
0
0
yes
10
PARENT_FULL_NAME
Cost Element Parent ID and Desc
NVARCSTR
120
0
0
yes
11
PARENT_ID
Cost Element Child Node ID
NVARCSTR
12
0
0
no
12
ROOT_FLAG
Is Root
DECIMAL
48
28
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
28
Appendix
Table Column Details
A
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 Desc
Column
Datatype
Short text describing ABAP/4 Dictionary
objects; domain BP_TRGKZ
NVARCSTR
60
0
0
yes
Values for domains: Single value/upper limit domain BP_TRGKZ
NVARCSTR
10
0
0
no
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
LOAD_TIME
Time loaded into Rapid mart
NVARCSTR
8
0
0
yes
Column Desc
Column
Datatype
#
Column Name
1
COST_OBJ_DESCR
2
COST_OBJ_ID
3
4
Key
PK
Dtype
Length Precision Scale
Is
Nullable
CURRENCY
TCURC, TCURT
Key
Dtype
Length Precision Scale
Is
Nullable
#
Column Name
1
CURR_DECIMAL
Lookup TCURX.CURRDEC - Number of
decimals to display amounts in this currency.
DECIMAL
48
28
0
yes
2
CURR_DESCR
TCURT-LTEXT - Long Text
NVARCSTR
60
0
0
yes
3
CURR_ID
TCURC-WAERS - Currency Key
NVARCSTR
5
0
0
no
4
CURR_ID_ALT
TCURC-ALTWR - Alternative Key For
Currencies
NVARCSTR
3
0
0
yes
5
CURR_ISO_CODE
TCURC-ISOCD - ISO Currency Code
NVARCSTR
3
0
0
yes
6
DISPLAY_FACTOR
Multiply currency amounts by this factor to
display with correct number of decimals for the DECIMAL
currency
48
17
14
yes
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
VALID_TO_DATE
TCURC-GDATU -Date Up Until Which The
Currency Is Valid
DATETIME
24
0
9
yes
PK
Rapid Mart Data Schema
29
Appendix
Table Column Details
A
DOCUMENT_CATEGORY
Domain VBTYP (Table DD07T) - Sales Document Categ
#
Column Name
Key
Column Desc
Column
Datatype
1
DIM_SRC_ID
PK
Dimension Source from table
AW_DIMENSION_SOURCE
NVARCSTR
10
0
0
no
2
DOC_CATEG_DESCR
Document Category Description from multiple
sources in SAP
NVARCSTR
100
0
0
yes
3
DOC_CATEG_ID
Document Category ID from multiple sources in NVARCSTR
SAP
10
0
0
no
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
PK
Dtype
Length Precision Scale
Is
Nullable
DOCUMENT_TYPE
Internal Order Type attributes from T003O/T003P
#
Column Name
Key
Column Desc
Column
Datatype
1
DIM_SRC_ID
PK
Dimension Source from table
AW_DIMENSION_SOURCE
NVARCSTR
10
0
0
no
2
DOC_CATEG_DESCR
Document Category Description
NVARCSTR
100
0
0
yes
3
DOC_CATEG_ID
Document Category from multiple Sources in
SAP
NVARCSTR
10
0
0
no
4
DOC_TYPE_DESCR
Document Type Description
NVARCSTR
100
0
0
yes
5
DOC_TYPE_ID
Document Type from Multiple sources in SAP
NVARCSTR
10
0
0
no
6
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
30
Appendix
Table Column Details
A
FINANCIAL_MGMT_AREA
FM01T - Funds Management Area Texts
#
Column Name
1
FIN_MGMT_AREA_DE
SCR
2
FIN_MGMT_AREA_ID
3
LOAD_DATE
4
LOAD_TIME
Key
PK
Column Desc
Column
Datatype
Name of FM area
NVARCSTR
25
0
0
yes
Financial Management Area
NVARCSTR
4
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
8
0
0
yes
NVARCSTR
Dtype
Length Precision Scale
Is
Nullable
FINANCIAL_RECORD_CATEGORY
Descriptive attributes for Accounting Summary table Value Category from TPIR1T
Column Desc
Column
Datatype
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time Loaded into Rapid mart
NVARCSTR
8
0
0
yes
3
RECORD_CATEG_D
ESCR
TPIR1T-KTEXT - Text
NVARCSTR
30
0
0
yes
4
RECORD_CATEG_ID
TPIR1T-ACPOS - Value category
NVARCSTR
14
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
31
Appendix
Table Column Details
A
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 Name
Key
Column Desc
Column
Datatype
1
DIM_SRC_ID
PK
Dimension Source. Used in combined
dimension combining similar attributes from
different sources in SAP.
NVARCSTR
2
LOAD_DATE
3
Dtype
Length Precision Scale
Is
Nullable
10
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
4
RECORD_TYPE_DE
SCR
Financial Record Type Desc.
NVARCSTR
60
0
0
yes
5
RECORD_TYPE_ID
Financial Record Type ID
NVARCSTR
10
0
0
no
PK
Rapid Mart Data Schema
32
Appendix
Table Column Details
A
FINANCING_CODE
Fund Managment - FIFM: Financing code from FMFINCODE source table
Column Desc
Column
Datatype
FM01T.FITXT - Name of FM area
NVARCSTR
25
0
0
yes
FMFINCODE.FIKRS - Financial management
area
NVARCSTR
4
0
0
no
FMFINT.BESCHR - Fund Description
NVARCSTR
40
0
0
yes
FMFINCODE.FINCODE - Fund
NVARCSTR
10
0
0
no
FUND_NAME
FMFINT.BEZEICH Fund Name
NVARCSTR
20
0
0
yes
6
FUND_TYPE_DESCR
FMFUNDTYPET.FUND_TYPET - Fund Type
Description
NVARCSTR
35
0
0
yes
7
FUND_TYPE_ID
FMFINCODE.TYPE - FM Fund Type ID
NVARCSTR
6
0
0
yes
8
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
9
LOAD_TIME
Time loaded into Rapid mart
NVARCSTR
8
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
#
Column Name
1
FIN_MGMT_AREA_DE
SCR
2
FIN_MGMT_AREA_ID
3
FUND_DESCR
4
FUND_ID
5
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
33
Appendix
Table Column Details
A
FISC_PERIOD
Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)
Column Desc
Column
Datatype
CALENDAR_HALF
Calendar Half Year for this Fiscal Period
NVARCSTR
2
0
0
yes
2
CALENDAR_MONTH
_LONG
Calendar Month (January - December) for this
Fiscal Period
NVARCSTR
14
0
0
yes
3
CALENDAR_MONTH
_NUMERIC
Calendar Month (Numeric) for this Fiscal
Period
NVARCSTR
2
0
0
yes
4
CALENDAR_MONTH
_SHORT
Calendar Month (JAN - DEC) for this fiscal
Period
NVARCSTR
3
0
0
yes
5
CALENDAR_QUART
ER
Calendar Quarter for this Fiscal Period
INTEGER
4
0
0
yes
6
CALENDAR_YEAR
Calendar Year for this fiscal period
INTEGER
4
0
0
yes
7
CALENDAR_YEAR_HA
LF
Calendar Year and Half
NVARCSTR
12
0
0
yes
8
CALENDAR_YEAR_
MONTH
Calendar Year and Month
NVARCSTR
12
0
0
yes
9
CALENDAR_YEAR_
QUARTER
Calendar Year and Quarter
NVARCSTR
12
0
0
yes
10
END_DATE
End Date for Fiscal Period
DATETIME
24
0
9
yes
11
FISC_HALF
Fiscal Half Year
NVARCSTR
2
0
0
yes
12
FISC_MONTH
Fiscal Month In SAP
NVARCSTR
2
0
0
yes
13
FISC_PERIOD
Fiscal Period in SAP
INTEGER
4
0
0
no
14
FISC_QUARTER
Fiscal Quarter
NVARCSTR
2
0
0
yes
15
FISC_YEAR
Fiscal Year in SAP
INTEGER
4
0
0
no
16
FISC_YEAR_HALF
Fiscal Year and Half
NVARCSTR
12
0
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
34
Appendix
Table Column Details
17
FISC_YEAR_MONTH
Fiscal Year and Month
NVARCSTR
12
0
0
yes
18
FISC_YEAR_PERIOD
Fiscal Year and Period
NVARCSTR
12
0
0
yes
19
FISC_YEAR_QUARTE
R
Fiscal Year and Quarter
NVARCSTR
12
0
0
yes
20
FISC_YR_VARIANT_ID PK
Fiscal Year Variant in SAP
NVARCSTR
2
0
0
no
21
FISC_YR_VARIANT_N
AME
Name of Fiscal Year Variant (Table T009T in
SAP)
NVARCSTR
30
0
0
yes
22
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
23
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
24
SPECL_PERIOD_FLA
G
Y = This is a special period in SAP, N = This is NVARCSTR
NOT a special period in SAP
1
0
0
yes
25
START_DATE
Start Date for Fiscal Period
24
0
9
yes
DATETIME
Rapid Mart Data Schema
A
35
Appendix
Table Column Details
A
FISC_PERIOD_STAGE
Table derived from Fisc. Yr Variants in SAP (tables T009, T009B, T009C, and T009T)
#
Column Name
Key
Column Desc
Column
Datatype
1
CALENDAR_DATE
PK
Calendar Date - range from 01-Jan-1990
through 31-Dec-2049
DATETIME
24
0
9
no
2
FISC_MONTH
Fiscal Month in range 1 to 12
NVARCSTR
2
0
0
yes
3
FISC_PERIOD
Fiscal Period in range 1 to 16
INTEGER
4
0
0
no
4
FISC_YEAR
Fiscal Year in SAP
INTEGER
4
0
0
yes
5
FISC_YR_VARIANT_ID PK
Fiscal Year Variant in SAP
NVARCSTR
2
0
0
no
6
FISC_YR_VARIANT_N
AME
Name of Fiscal Year Variant (Table T009T in
SAP)
NVARCSTR
30
0
0
yes
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
REGISTRTN_PERIOD
_COUNT
Number of Regular Acctng Periods
INTEGER
4
0
0
yes
10
SPECL_PERIOD_COU
NT
Number of Special Acctng Periods
INTEGER
4
0
0
yes
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
36
Appendix
Table Column Details
A
FORMULA_PARAMETER
Capacity Parameter details from TC20 that are related to Work Center formulars
Column Desc
Column
Datatype
COSTNG_ALLOW_F
LAG
TC20.VKALK - Indicates it is allowed for
costing
DECIMAL
48
10
0
yes
2
DIMENSION_TYPE_N
AME
TC20.DIMEN- Dimension key
NVARCSTR
6
0
0
yes
3
FIELD_NAME
TC20.VGFLD - Field name
NVARCSTR
10
0
0
yes
4
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
6
PARAMETER_DESCR
TC20T.TXT - Lookup parameter description
NVARCSTR
11
0
0
yes
7
PARAMETER_ID
TC20.PARID - Parameter ID
NVARCSTR
6
0
0
no
8
PARAMETER_KEYW
ORD
TC20T. TXTLG - Lookup keyword for
parameter
NVARCSTR
20
0
0
yes
9
PARAMETER_ORIGIN
_DESCR
Lookup on DD07T, docmain VGWRTKZ origin text
NVARCSTR
40
0
0
yes
10
PARAMETER_ORIGIN
_ID
TC20.VRWRT - Origin of the parameter value NVARCSTR
1
0
0
yes
11
UOM_ID_STD
TC20.UNIT- Unit of measure for the standard
value
NVARCSTR
3
0
0
yes
12
VALUE_STD
TC20.VALUE_DEF - Standard value
DECIMAL
48
9
3
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
37
Appendix
Table Column Details
A
FUNCTIONAL_AREA
TFKB-FKBER - Functional Area reference table
Column Desc
Column
Datatype
FUNCTNL_AREA_DES
CR
Functional Area Description
NVARCSTR
30
0
0
yes
2
FUNCTNL_AREA_FUL
L_NAME
ID and Description
NVARCSTR
120
0
0
yes
3
FUNCTNL_AREA_ID
TFKB-FKBER - Functional Area Code
NVARCSTR
16
0
0
no
4
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
8
0
0
yes
#
Column Name
1
Key
PK
NVARCSTR
Dtype
Length Precision Scale
Is
Nullable
FUNCTIONAL_AREA_HIER
Functional Area Hierarchy
Column Desc
Column
Datatype
Child node description
NVARCSTR
64
0
0
yes
PK
Child node id
NVARCSTR
30
0
0
no
PK
Leaf node indicator (child node is leaf)
NVARCSTR
1
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
LEAF_FLAG
4
LOAD_DATE
5
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
38
Appendix
Table Column Details
A
FUNCTIONAL_AREA_HIER_BAD
Functional Area Hierarchy - Invalid Records with Circular Dependency.
Column Desc
Column
Datatype
Child node description
NVARCSTR
64
0
0
yes
Child node id
NVARCSTR
30
0
0
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
4
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
5
LEAF_FLAG
Leaf node indicator (child node is leaf)
NVARCSTR
1
0
0
no
6
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
39
Appendix
Table Column Details
A
FUNCTIONAL_AREA_HIER_HZ
Functional Area Hierarchy - Horizontal
#
Column Name
Key
Column Desc
Column
Datatype
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
3
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
4
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
Funct. Area Level 0 ID
NVARCSTR
30
0
0
no
8
LVL_01_DESCR
Funct. Area Level 1 Description
NVARCSTR
64
0
0
yes
9
LVL_01_FULL_NAME
Funct. Area Level 1 ID and Description
NVARCSTR
120
0
0
yes
10
LVL_01_ID
Funct. Area Level 1 ID
NVARCSTR
30
0
0
no
11
LVL_02_DESCR
Funct. Area Level 2 Description
NVARCSTR
64
0
0
yes
12
LVL_02_FULL_NAME
Funct. Area Level 2 ID and Description
NVARCSTR
120
0
0
yes
13
LVL_02_ID
Funct. Area Level 2 ID
NVARCSTR
30
0
0
no
14
LVL_03_DESCR
Funct. Area Level 3 Description
NVARCSTR
64
0
0
yes
15
LVL_03_FULL_NAME
Funct. Area Level 3 ID and Description
NVARCSTR
120
0
0
yes
16
LVL_03_ID
Funct. Area Level 3 ID
NVARCSTR
30
0
0
no
PK
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
40
Appendix
Table Column Details
17
LVL_04_DESCR
Funct. Area Level 4 Description
NVARCSTR
64
0
0
yes
18
LVL_04_FULL_NAME
Funct. Area Level 4 ID and Description
NVARCSTR
120
0
0
yes
19
LVL_04_ID
Funct. Area Level 4 ID
NVARCSTR
30
0
0
no
20
LVL_05_DESCR
Funct. Area Level 5 Description
NVARCSTR
64
0
0
yes
21
LVL_05_FULL_NAME
Funct. Area Level 5 ID and Description
NVARCSTR
120
0
0
yes
22
LVL_05_ID
Funct. Area Level 5 ID
NVARCSTR
30
0
0
no
23
LVL_06_DESCR
Funct. Area Level 6 Description
NVARCSTR
64
0
0
yes
24
LVL_06_FULL_NAME
Funct. Area Level 6 ID and Description
NVARCSTR
120
0
0
yes
25
LVL_06_ID
Funct. Area Level 6 ID
NVARCSTR
30
0
0
no
26
LVL_07_DESCR
Funct. Area Level 7 Description
NVARCSTR
64
0
0
yes
27
LVL_07_FULL_NAME
Funct. Area Level 7 ID and Description
NVARCSTR
120
0
0
yes
28
LVL_07_ID
Funct. Area Level 7 ID
NVARCSTR
30
0
0
no
29
LVL_08_DESCR
Funct. Area Level 8 Description
NVARCSTR
64
0
0
yes
30
LVL_08_FULL_NAME
Funct. Area Level 8 ID and Description
NVARCSTR
120
0
0
yes
31
LVL_08_ID
Funct. Area Level 8 ID
NVARCSTR
30
0
0
no
32
LVL_09_DESCR
Funct. Area Level 9 Description
NVARCSTR
64
0
0
yes
33
LVL_09_FULL_NAME
Funct. Area Level 9 ID and Description
NVARCSTR
120
0
0
yes
34
LVL_09_ID
Funct. Area Level 9 ID
NVARCSTR
30
0
0
no
PK
PK
PK
PK
PK
PK
Rapid Mart Data Schema
A
41
Appendix
Table Column Details
35
LVL_10_DESCR
Funct. Area Level 10 Description
NVARCSTR
64
0
0
yes
36
LVL_10_FULL_NAME
Funct. Area Level 10 ID and Description
NVARCSTR
120
0
0
yes
37
LVL_10_ID
Funct. Area Level 10 ID
NVARCSTR
30
0
0
no
PK
A
FUNCTIONAL_AREA_HIER_VR
Functional Area Hierarchy - Vertical
Column Desc
Column
Datatype
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
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
6
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
8
PARENT_DESCR
Parent Funct. Area Description
NVARCSTR
64
0
0
yes
9
PARENT_FULL_NAME
Parent Funct. Area ID and Description
NVARCSTR
120
0
0
yes
10
PARENT_ID
Parent Funct. Area ID
NVARCSTR
30
0
0
no
11
ROOT_FLAG
Root Flag
INTEGER
4
0
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
42
Appendix
Table Column Details
A
INTERNAL_ORDER
AUFK - Internal Order Master
Column Desc
Column
Datatype
ALLOCTN_GRP_CO
DE
Allocation Group Code
NVARCSTR
2
0
0
yes
2
APPLICTN_DATE
AUFK-USER5
DATETIME
24
0
9
yes
3
BUS_AREA_ID
AUFK-GSBER
NVARCSTR
4
0
0
yes
4
BUS_AREA_NAME
Business area description
NVARCSTR
30
0
0
yes
5
CHANGE_DATE
AUFK-AEDAT
DATETIME
24
0
9
yes
6
CLOSE_DATE
AUFK-IDAT3
DATETIME
24
0
9
yes
7
CMPNY_CODE_ID
AUFK-BUKRS
NVARCSTR
4
0
0
yes
8
CMPNY_CODE_NAME
Name of the company code or company
NVARCSTR
25
0
0
yes
9
COMPLT_DATE
AUFK-IDAT2
DATETIME
24
0
9
yes
10
COST_CNTR_ID_ALL
OCTN
AUFK-KOSTL
NVARCSTR
10
0
0
yes
11
COST_CNTR_ID_RES
P
AUFK-KOSTV
NVARCSTR
10
0
0
yes
12
COST_CNTR_ID_RQS
T
AUFK-AKSTL
NVARCSTR
10
0
0
yes
13
COST_COLLECTR_KE
Y
AUFK-CCKEY
NVARCSTR
23
0
0
yes
14
COST_ELEM_ID_SET
TLMNT
AUFK-KSTAR
NVARCSTR
10
0
0
yes
15
CREATE_DATE
AUFK-ERDAT
DATETIME
24
0
9
yes
16
CTRL_AREA_ID
AUFK-KOKRS
NVARCSTR
4
0
0
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
43
Appendix
Table Column Details
17
CTRL_AREA_NAME
Name of the controlling area
NVARCSTR
25
0
0
yes
18
CURR_ID
AUFK-WAERS
NVARCSTR
5
0
0
yes
19
DELETE_CODE
AUFK-LOEKZ
NVARCSTR
1
0
0
yes
20
DEPARTMENT
AUFK-USER6
NVARCSTR
15
0
0
yes
21
DOC_CATEG_DESCR
DD07T - DDTEXT(lookup) - Order category
description
NVARCSTR
60
0
0
yes
22
DOC_CATEG_ID
AUFK-AUTYP
NVARCSTR
2
0
0
yes
23
DOC_TYPE_DESCR
T003P-TXT(lookup) - Short text
NVARCSTR
40
0
0
yes
24
DOC_TYPE_ID
AUFK-AUART
NVARCSTR
4
0
0
yes
25
EQUITY_TYPE_CODE
AUFK-ETYPE
NVARCSTR
3
0
0
yes
26
EST_TRX_COST_ORD
ER
AUFK-USER4
DECIMAL
48
11
2
yes
27
EXTERNAL_ORDER
_NUM
AUFK-AUFEX
NVARCSTR
20
0
0
yes
28
GL_ACCT_ID_ALLOCT
N
AUFK-SAKNR
NVARCSTR
10
0
0
yes
29
INTERNAL_ORDER_ID PK
AUFK-AUFNR
NVARCSTR
12
0
0
no
30
INTERNAL_ORDER_ID
_REF
AUFK-REFNR
NVARCSTR
12
0
0
yes
31
INTERNAL_ORDER_ID
_STATS
AUFK-ASTNR
NVARCSTR
1
0
0
yes
32
JOINT_VENTURE_CO
DE
AUFK-VNAME
NVARCSTR
6
0
0
yes
33
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
34
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
8
0
0
yes
NVARCSTR
Rapid Mart Data Schema
A
44
Appendix
Table Column Details
35
LOCATN_ID
AUFK-STORT
NVARCSTR
10
0
0
yes
36
OBJ_ID
AUFK-OBJNR
NVARCSTR
22
0
0
yes
37
ORDER_DESCR
AUFK-KTEXT
NVARCSTR
40
0
0
yes
38
ORDER_STATUS_ID
AUFK-ASTKZ
NVARCSTR
2
0
0
yes
39
OVERHEAD_CODE
AUFK-ZSCHL
NVARCSTR
6
0
0
yes
40
PLANNED_CLOSE_DA
TE
AUFK-PDAT3
DATETIME
24
0
9
yes
41
PLANNED_COMPLT
_DATE
AUFK-PDAT2
DATETIME
24
0
9
yes
42
PLANNED_REL_DATE
AUFK-PDAT1
DATETIME
24
0
9
yes
43
PLANT_ID
AUFK-WERKS
NVARCSTR
4
0
0
yes
44
PLANT_ID_LOCATN
AUFK-SOWRK
NVARCSTR
4
0
0
yes
45
PLANT_NAME
Name
NVARCSTR
30
0
0
yes
46
PROFIT_CNTR_ID
AUFK-PRCTR
NVARCSTR
10
0
0
yes
47
PROJ_ELEM_DESCR
PS: Short description (1st text line)
NVARCSTR
40
0
0
yes
48
PROJ_ELEM_ID
AUFK-PSPEL lookup to PRPS.POSID - WBS
element External ID
NVARCSTR
24
0
0
yes
49
RECOVERY_CODE
AUFK-RECID
NVARCSTR
2
0
0
yes
50
RELEASE_DATE
AUFK-IDAT1
DATETIME
24
0
9
yes
51
RESP_PERSON
AUFK-USER2
NVARCSTR
20
0
0
yes
52
SALES_LINE_ITEM_ID
AUFK-KDPOS
NVARCSTR
6
0
0
yes
Rapid Mart Data Schema
A
45
Appendix
Table Column Details
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
A
INTERNAL_ORDER_HIER
CCSS-AUFNR - Internal Order Hierarchy- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
Internal Order Child Node Description
NVARCSTR
64
0
0
yes
PK
Internal Order Child Node ID
NVARCSTR
12
0
0
no
PK
Is Leaf
NVARCSTR
1
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
8
ROOT_FLAG
PK
Is Root
NVARCSTR
1
0
0
no
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
LEAF_FLAG
4
LOAD_DATE
5
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
46
Appendix
Table Column Details
A
INTERNAL_ORDER_HIER_BAD
CCSS-AUFNR Internal Order Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
Internal Order Child Node Description
NVARCSTR
64
0
0
yes
Internal Order Child Node ID
NVARCSTR
12
0
0
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
4
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
5
LEAF_FLAG
Is Leaf
NVARCSTR
1
0
0
no
6
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
8
PARENT_DESCR
Internal Order Parent Node Descritpion
NVARCSTR
64
0
0
yes
9
PARENT_ID
PK
Internal Order Parent Node ID
NVARCSTR
12
0
0
no
10
ROOT_FLAG
PK
Is Root
NVARCSTR
1
0
0
no
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
47
Appendix
Table Column Details
A
INTERNAL_ORDER_HIER_HZ
CCSS-AUFNR - Internal Order hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
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
3
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
4
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
5
LVL_00_DESCR
Internal Order Root node Description
NVARCSTR
64
0
0
yes
6
LVL_00_FULL_NAME
Internal Order Number and Descritpion for
Level 0
NVARCSTR
120
0
0
yes
7
LVL_00_ID
Internal Order Root node id
NVARCSTR
12
0
0
no
8
LVL_01_DESCR
Internal Order Level 1node Descritpion
NVARCSTR
64
0
0
yes
9
LVL_01_FULL_NAME
Internal Order Number and Descritpion for
Level 1
NVARCSTR
120
0
0
yes
10
LVL_01_ID
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
12
LVL_02_FULL_NAME
Internal Order Number and Descritpion for
Level 2
NVARCSTR
120
0
0
yes
13
LVL_02_ID
Internal Order Level 2 node ID
NVARCSTR
12
0
0
no
14
LVL_03_DESCR
Internal Order Level 3 node Descritpion
NVARCSTR
64
0
0
yes
15
LVL_03_FULL_NAME
Internal Order Number and Descritpion for
Level 3
NVARCSTR
120
0
0
yes
16
LVL_03_ID
Internal Order Level 3 node ID
NVARCSTR
12
0
0
no
#
Column Name
1
Key
PK
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
48
Appendix
Table Column Details
17
LVL_04_DESCR
Internal Order Level 4 node Descritpion
NVARCSTR
64
0
0
yes
18
LVL_04_FULL_NAME
Internal Order Number and Descritpion for
Level 4
NVARCSTR
120
0
0
yes
19
LVL_04_ID
Internal Order Level 4 node ID
NVARCSTR
12
0
0
no
PK
A
INTERNAL_ORDER_HIER_VR
CCSS-AUFNR - Internal Order hierarchy flattenned vertically - cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
CHILD_DESCR
Internal Order Child Node Description
NVARCSTR
64
0
0
yes
2
CHILD_FULL_NAME
Internal Order Number and Description Child
Node)
NVARCSTR
120
0
0
yes
3
CHILD_ID
Internal Order Child Node ID
NVARCSTR
12
0
0
no
4
DEPTH
Internal Order Child depth level
DECIMAL
48
28
0
yes
5
LEAF_FLAG
Node Is leaf
DECIMAL
48
28
0
yes
6
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
8
PARENT_DESCR
Internal Order Parent Node Description
NVARCSTR
64
0
0
yes
9
PARENT_FULL_NAME
Internal Order Number and Description (Parent NVARCSTR
Node)
120
0
0
yes
10
PARENT_ID
Internal Order Parent Node ID
NVARCSTR
12
0
0
no
11
ROOT_FLAG
Node Is root
DECIMAL
48
28
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
49
Appendix
Table Column Details
A
INTERNAL_ORDER_STATUS
Internal Order status name and descritpion from TKO04
Column Desc
Column
Datatype
T003P.TXT -Short text
NVARCSTR
40
0
0
yes
TKO04.ART -Order type
NVARCSTR
4
0
0
no
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
4
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
5
ORDER_STATUS_D
ESCR
TKO04.TXT -Text (40 characters) for status
NVARCSTR
40
0
0
yes
6
ORDER_STATUS_ID
TKO04.ASTNR -Order status
NVARCSTR
2
0
0
no
#
Column Name
1
DOC_TYPE_DESCR
2
DOC_TYPE_ID
3
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
50
Appendix
Table Column Details
A
MATERIAL
MARA - Material Master
Column Desc
Column
Datatype
BATCH_MGMT_FLAG
XCHPF Batch management requirement
indicator
NVARCSTR
1
0
0
yes
2
CREATE_DATE
ERSDA Date of creation
DATETIME
24
0
9
yes
3
DELETE_CODE
MARA-LVORM - Deletion flag for all material
data (central)
NVARCSTR
1
0
0
yes
4
DELETE_DATE
LIQDT Deletion date
DATETIME
24
0
9
yes
5
DIVISION_DESCR
TSPAT.VTEXT Division Description
NVARCSTR
20
0
0
yes
6
DIVISION_ID
MARA.SPART Division
NVARCSTR
2
0
0
yes
7
INDUSTRY_SECTOR_I
D
MARA.MBRSH Industry Sector ID
NVARCSTR
1
0
0
yes
8
INDUSTRY_SECT_DE
SCR
Lookup description of MARA.MBRSH Industry
sector
NVARCSTR
25
0
0
yes
9
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
10
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
11
LOW_LVL_CODE
MARA.DISST - Low level code
NVARCSTR
3
0
0
yes
12
MATERIAL_ID
MATNR Material number
NVARCSTR
18
0
0
no
13
MIN_REM_SHELF_LIF
E
MARA.MHDRZ Minimum remaining shelf life
INTEGER
4
0
0
yes
14
MODIFIED_DATE
MARA.LAEDA Date of last change
DATETIME
24
0
9
yes
15
MTRL_CATEG_DES
CR
Category Description
NVARCSTR
60
0
0
yes
16
MTRL_CATEG_ID
MARA.ATTYP Material category
NVARCSTR
2
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
51
Appendix
Table Column Details
17
MTRL_DESCR
MAKTX Material description
NVARCSTR
40
0
0
yes
18
MTRL_FULL_NAME
Material ID and Material Description
NVARCSTR
64
0
0
yes
19
MTRL_GRP_DESCR
WGBEZ Description of material group
NVARCSTR
20
0
0
yes
20
MTRL_GRP_ID
MATKL Material group
NVARCSTR
9
0
0
yes
21
MTRL_ID_MANUFCTR
MARA.MFRPN - Manfuacturer Part (Material)
Number
NVARCSTR
40
0
0
yes
22
MTRL_TYPE_DESCR
Lookup description of MARA.MTART in T134T NVARCSTR
25
0
0
yes
23
MTRL_TYPE_ID
MTART Material type
NVARCSTR
4
0
0
yes
24
PROD_HIER_ID
PRDHA Product hierarchy
NVARCSTR
18
0
0
yes
25
PURCH_STATUS_C
ODE
General material status: Purchasing
NVARCSTR
2
0
0
yes
26
REVISION_LVL
Lookup AEOI.REVLV - Material revision level
NVARCSTR
2
0
0
yes
27
SALES_STATUS_COD
E
MARA.MSTAV General material status: sales
NVARCSTR
2
0
0
yes
28
TRANSPORT_GRP_
CODE
MARA.TRAGR Transportation group
NVARCSTR
4
0
0
yes
29
TTL_SHELF_LIFE
MARA.MHDHB Total shelf life in days
INTEGER
4
0
0
yes
30
UOM_ID_BASE
MEINS Base unit of measure
NVARCSTR
3
0
0
yes
31
UOM_ID_ORDER
MARA.BSTME Order unit (purchasing)
NVARCSTR
3
0
0
yes
32
UOM_ID_VOLUME
MARA.VOLEH Volume unit
NVARCSTR
3
0
0
yes
33
UOM_ID_WEIGHT
MARA.GEWEI Unit of weight
NVARCSTR
3
0
0
yes
34
VALID_FROM_DATE
MARA.DATAB Date valid from
DATETIME
24
0
9
yes
Rapid Mart Data Schema
A
52
Appendix
Table Column Details
35
VOLUME
MARA.VOLUM Volume
DECIMAL
48
13
3
yes
36
WEIGHT
MARA.NTGEW Net weight
DECIMAL
48
13
3
yes
Rapid Mart Data Schema
A
53
Appendix
Table Column Details
A
MATERIAL_BATCH
Batch material managerment - Material Master from MCHA
Column Desc
Column
Datatype
ABC_CATEG_DESCR
TMABCT.TMABC - lookup on ABC indicator
descritpion
NVARCSTR
30
0
0
yes
2
ABC_CATEG_ID
MARC.MAABC ABC indicator
NVARCSTR
1
0
0
yes
3
AMT_VALUATN_PRIC
E
Lookup MBEW.SALK3 - Stock Valuation Price ,
Moving Average or Standard depending on
price control indicator in MBEW (current Value DECIMAL
only)
48
13
2
yes
4
AVAIL_DATE
MCHA.VERAB - Availability date
24
0
9
yes
5
BASE_TO_PROD_U
OM_RATE
Lookup MARM.UMREZ Factor to convert from
BASE UOM to PROD UOM. (PROD_QTY =
INTEGER
MENGE / UMREZ)
4
0
0
yes
6
BATCH_ID
MCHA.CHARG - Batch number
NVARCSTR
10
0
0
no
7
BATCH_NUM_VEND
OR
MCHA.LICHA - Vendor batch number
NVARCSTR
15
0
0
yes
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
12
COUNTRY_NAME_O
RIGIN
Lookup description onT005T.LANDX for
Country name
NVARCSTR
15
0
0
yes
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
16
DAYS_PLAN_GR
MARC.WEBAZ - Planned goods receipt
processing time in days - includes inspection
time
INTEGER
4
0
0
yes
#
Column Name
1
Key
PK
DATETIME
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
54
Appendix
Table Column Details
17
DAYS_REPLENISH
MARC.WZEIT - Total replenishment lead time
in days - in house production time and/or
delivery lead tim
INTEGER
4
0
0
yes
18
DAYS_TO_PRODUCE
MARC.DZEIT - In-house production time
INTEGER
4
0
0
yes
19
DELETE_FLAG
MARC.LVORM - Plant level material deletion
indicator
NVARCSTR
1
0
0
yes
20
DIVISION_DESCR
TSPAT.VTEXT Division Description
NVARCSTR
20
0
0
yes
21
DIVISION_ID
MARA.SPART Division
NVARCSTR
2
0
0
yes
22
EXPIRE_DATE
MCHA.VFDAT - Shelf life expiration date
DATETIME
24
0
9
yes
23
INDUSTRY_SECTOR_I
D
MARA.MBRSH Industry Sector ID
NVARCSTR
1
0
0
yes
24
INDUSTRY_SECT_DE
SCR
Lookup description of MARA.MBRSH Industry
sector
NVARCSTR
25
0
0
yes
25
LOAD_DATE
Date and time when loaded into RapidMart
DATETIME
24
0
9
yes
26
LOAD_TIME
Time in a string format when the record was
loaded into the target database
NVARCSTR
8
0
0
yes
27
MATERIAL_ID
MARC.MATNR Material number
NVARCSTR
18
0
0
no
28
MRP_CTRLLER_ID
MARC.DISPO MRP controller
NVARCSTR
3
0
0
yes
29
MRP_CTRLLER_NA
ME
T024D.DSNAM - Name of MRP controller lookup
NVARCSTR
18
0
0
yes
30
MRP_TYPE_DESCR
T438T.DIBEZ -Long MRP Type Description
from T438T
NVARCSTR
30
0
0
yes
31
MRP_TYPE_ID
MARC.DISMM MRP type code
NVARCSTR
2
0
0
yes
32
MTRL_CATEG_DES
CR
lookup on ATTYP domain in DD07T
NVARCSTR
60
0
0
yes
33
MTRL_CATEG_ID
MARA.ATTYP Material category
NVARCSTR
2
0
0
yes
34
MTRL_DESCR
MAKT.MAKTX -Material description
NVARCSTR
40
0
0
yes
PK
Rapid Mart Data Schema
A
55
Appendix
Table Column Details
35
MTRL_GRP_DESCR
WGBEZ Description of material group
NVARCSTR
20
0
0
yes
36
MTRL_GRP_ID
MATKL Material group
NVARCSTR
9
0
0
yes
37
MTRL_TYPE_DESCR
Lookup description of MARA.MTART in T134T NVARCSTR
25
0
0
yes
38
MTRL_TYPE_ID
MTART Material type
NVARCSTR
4
0
0
yes
39
NEXT_INSPECTN_DA
TE
MCHA.QNDAT - Next inspection date
DATETIME
24
0
9
yes
40
PLANT_ID
MARC.WERKS Plant
NVARCSTR
4
0
0
no
41
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
0
0
yes
42
PROCUREMNT_TYP
E_DESCR
Lookup DD07T - Procurement type - BESKZ
domain
NVARCSTR
60
0
0
yes
43
PROCUREMNT_TYP
E_ID
MARC.BESKZ - Procurement type code
NVARCSTR
20
0
0
yes
44
PURCH_GRP_DESCR
Lookup description of T024.EKNAM - Purchase NVARCSTR
Group Name
30
0
0
yes
45
PURCH_GRP_ID
MARC.EKGRP Purchasing group
NVARCSTR
3
0
0
yes
46
QTY_REORDER_POIN
T
MARC.MINBE Reorder point
DECIMAL
48
13
3
yes
47
QTY_SAFETY_STOCK
MARC.EISBE Safety stock
DECIMAL
48
13
3
yes
48
QUALITY_INSPECT_F
LAG
MARC.INSMK - Quality inspection indicator - X NVARCSTR
is yes
1
0
0
yes
49
RESTRICT_STOCK_F
LAG
MCHA.ZUSTD - Batch in restricted-use stock
NVARCSTR
1
0
0
yes
50
SPECL_PROCUREM
NT_TYPE_DESCR
Lookup description of MARC.SOBSL in T460T- NVARCSTR
Special procurement type
30
0
0
yes
51
SPECL_PROCUREM
NT_TYPE_ID
MARC.SOBSL - Special procurement type
NVARCSTR
2
0
0
yes
52
SUPPLY_SRC_DESCR
Lookup description on TMBWT.BWSCB for
supply source description
NVARCSTR
40
0
0
yes
PK
Rapid Mart Data Schema
A
56
Appendix
Table Column Details
53
SUPPLY_SRC_ID
MARC.BWSCL Source of supply IS-R
NVARCSTR
1
0
0
yes
54
UOM_CODE_BASE
Lookup MARC.AUSME in T006A to get Base
Unit External Code
NVARCSTR
3
0
0
yes
55
UOM_CODE_ISSUE
Lookup MARC.AUSME in T006A to get Unit of NVARCSTR
Issue Long Description
3
0
0
yes
56
UOM_CODE_PROD
Lookup MARC.FRTME in T006A to get
Production UOM External code
NVARCSTR
3
0
0
yes
57
UOM_ID_BASE
MEINS Base unit of measure
NVARCSTR
3
0
0
yes
58
UOM_ID_ISSUE
MARC.AUSME - Unit of measure for goods
issue
NVARCSTR
3
0
0
yes
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
Rapid Mart Data Schema
A
57
Appendix
Table Column Details
A
MATERIAL_BY_PLANT
MARA and MARC Tables - Plant Level Material attributes
Column Desc
Column
Datatype
ABC_CATEG_DESCR
TMABCT.TMABC - lookup on ABC indicator
descritpion
NVARCSTR
30
0
0
yes
2
ABC_CATEG_ID
MARC.MAABC ABC indicator
NVARCSTR
1
0
0
yes
3
BASE_TO_PRODUC
TN_MULTIPLR
Lookup MARM.UMREZ Factor to convert from
BASE UOM to PROD UOM. (PROD_QTY =
INTEGER
MENGE / UMREZ)
4
0
0
yes
4
BATCH_MGMT_FLAG
Lookup MARC.XCHAR Batch management
indicator (internal)
NVARCSTR
1
0
0
yes
5
BATCH_MGMT_REQ
_FLAG
MARC.XCHPF Batch management
requirement indicator
NVARCSTR
1
0
0
yes
6
BULK_MTRL_FLAG
MARC.SCHGT Indicator: bulk material
NVARCSTR
1
0
0
yes
7
COUNTRY_ID_ORIGIN
MARC.HERKL Materials country of origin
NVARCSTR
3
0
0
yes
8
COUNTRY_NAME_O
RIGIN
Lookup description onT005T.LANDX for
Country name
NVARCSTR
15
0
0
yes
9
DAYS_PLAN_DELIV
MARC.PLIFZ - Planned delivery time in days
INTEGER
4
0
0
yes
10
DAYS_PLAN_GR
MARC.WEBAZ - Planned goods receipt
processing time in days - includes inspection
time
INTEGER
4
0
0
yes
11
DAYS_REPLENISH
MARC.WZEIT - Total replenishment lead time
in days - in house production time and/or
delivery lead tim
INTEGER
4
0
0
yes
12
DAYS_TO_PRODUCE
MARC.DZEIT - In-house production time
INTEGER
4
0
0
yes
13
DELETE_FLAG
MARC.LVORM - Plant level material deletion
indicator
NVARCSTR
1
0
0
yes
14
DIVISION_DESCR
TSPAT.VTEXT Division Description
NVARCSTR
20
0
0
yes
15
DIVISION_ID
MARA.SPART Division
NVARCSTR
2
0
0
yes
16
INDUSTRY_SECTOR_
DESCR
Lookup description of MARA.MBRSH Industry
sector
NVARCSTR
25
0
0
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
58
Appendix
Table Column Details
17
INDUSTRY_SECTOR_I
D
MARA.MBRSH Industry Sector ID
NVARCSTR
1
0
0
yes
18
LOAD_DATE
Date and time loaded into RapidMart
DATETIME
24
0
9
yes
19
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
8
0
0
yes
20
MATERIAL_ID
MARC.MATNR Material number
NVARCSTR
18
0
0
no
21
MRP_CTRLLER_ID
MARC.DISPO MRP controller
NVARCSTR
3
0
0
yes
22
MRP_CTRLLER_NA
ME
T024D.DSNAM - Name of MRP controller lookup
NVARCSTR
18
0
0
yes
23
MRP_TYPE_DESCR
T438T.DIBEZ -Long MRP Type Description
from T438T
NVARCSTR
30
0
0
yes
24
MRP_TYPE_ID
MARC.DISMM MRP type code
NVARCSTR
2
0
0
yes
25
MTRL_CATEG_DES
CR
lookup on ATTYP domain in DD07T
NVARCSTR
60
0
0
yes
26
MTRL_CATEG_ID
MARA.ATTYP Material category
NVARCSTR
2
0
0
yes
27
MTRL_DESCR
MAKT.MAKTX -Material description
NVARCSTR
40
0
0
yes
28
MTRL_FULL_NAME
Material ID and Material Description
NVARCSTR
64
0
0
yes
29
MTRL_GRP_DESCR
WGBEZ Description of material group
NVARCSTR
20
0
0
yes
30
MTRL_GRP_ID
MATKL Material group
NVARCSTR
9
0
0
yes
31
MTRL_TYPE_DESCR
Lookup description of MARA.MTART in T134T NVARCSTR
25
0
0
yes
32
MTRL_TYPE_ID
MTART Material type
NVARCSTR
4
0
0
yes
33
PLANT_FULL_NAME
Plant ID and Plant Name
NVARCSTR
40
0
0
yes
34
PLANT_ID
MARC.WERKS Plant
NVARCSTR
4
0
0
no
PK
PK
Rapid Mart Data Schema
A
59
Appendix
Table Column Details
35
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
0
0
yes
36
PROCUREMNT_TYP
E_DESCR
Lookup DD07T - Procurement type - BESKZ
domain
NVARCSTR
60
0
0
yes
37
PROCUREMNT_TYP
E_ID
MARC.BESKZ - Procurement type code
NVARCSTR
20
0
0
yes
38
PROFIT_CNTR_ID
MARC.PRCTR Profit center
NVARCSTR
10
0
0
yes
39
PURCH_GRP_DESCR
Lookup description of T024.EKNAM - Purchase NVARCSTR
Group Name
30
0
0
yes
40
PURCH_GRP_ID
MARC.EKGRP Purchasing group
NVARCSTR
3
0
0
yes
41
QTY_REORDER_POIN
T
MARC.MINBE Reorder point
DECIMAL
48
13
3
yes
42
QTY_SAFETY_STOCK
MARC.EISBE Safety stock
DECIMAL
48
13
3
yes
43
QUALITY_INSPECT_F
LAG
MARC.INSMK - Quality inspection indicator - X NVARCSTR
is yes
1
0
0
yes
44
SPECL_PROCUREM
NT_TYPE_DESCR
Lookup description of MARC.SOBSL in T460T- NVARCSTR
Special procurement type
30
0
0
yes
45
SPECL_PROCUREM
NT_TYPE_ID
MARC.SOBSL - Special procurement type
NVARCSTR
2
0
0
yes
46
SUPPLY_SRC_DESCR
Lookup description on TMBWT.BWSCB for
supply source description
NVARCSTR
40
0
0
yes
47
SUPPLY_SRC_ID
MARC.BWSCL Source of supply IS-R
NVARCSTR
1
0
0
yes
48
UOM_CODE_BASE
Lookup MARC.AUSME in T006A to get Base
Unit External Code
NVARCSTR
3
0
0
yes
49
UOM_CODE_ISSUE
Lookup MARC.AUSME in T006A to get Unit of NVARCSTR
Issue Long Description
3
0
0
yes
50
UOM_CODE_PROD
Lookup MARC.FRTME in T006A to get
Production UOM External code
NVARCSTR
3
0
0
yes
51
UOM_ID_BASE
MEINS Base unit of measure
NVARCSTR
3
0
0
yes
52
UOM_ID_ISSUE
MARC.AUSME - Unit of measure for goods
issue
NVARCSTR
3
0
0
yes
Rapid Mart Data Schema
A
60
Appendix
Table Column Details
53
UOM_ID_PROD
MARC.FRTME Production unit of measure
NVARCSTR
Column Desc
Column
Datatype
3
0
0
A
yes
MATERIAL_GROUP
T023T - Material Group
Key
Dtype
Length Precision Scale
Is
Nullable
#
Column Name
1
LOAD_DATE
Date and Time Loaded into Rapid Mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time Loaded into Rapid Mart
NVARCSTR
8
0
0
yes
3
MTRL_GRP_DESCR
Material Group Description
NVARCSTR
20
0
0
yes
4
MTRL_GRP_ID
Material Group ID
NVARCSTR
9
0
0
no
PK
Rapid Mart Data Schema
61
Appendix
Table Column Details
A
MATERIAL_TYPE
Material Type descriptive attributes from T134, T134T
Column Desc
Column
Datatype
CONFIG_FLAG
Configurable Material - X - yes
INTEGER
4
0
0
yes
2
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
3
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
4
MTRL_ITEM_GRP_DE
SCR
TPTMT.BEZEI Division Description
NVARCSTR
20
0
0
yes
5
MTRL_ITEM_GRP_ID
T134.VMTPO - Default value for material item
category group
NVARCSTR
4
0
0
yes
6
MTRL_TYPE_DESCR
T134T.MTBEZ -Description of material type
NVARCSTR
25
0
0
yes
7
MTRL_TYPE_ID
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
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
62
Appendix
Table Column Details
A
MILESTONE_FACT
Project Milestone details from MLST/PLKO/PLPO/AFVC
Column Desc
Column
Datatype
ACTIVITY_ID
AFVC/PLPO.LARNT -Activity Type
NVARCSTR
6
0
0
yes
2
ACTL_END_DATE
MLST.LST_ACTDT - Actual date (Milestone
met)+MLST.LST_ACTTM - Actual date/time
(Milestone met)
DATETIME
24
0
9
yes
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
6
COMPLETE_FLAG
Calculated based on MLST.LST_FERTG Percentage of completion (%) - if 100% then 1, INTEGER
else 0
4
0
0
yes
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
9
CTRL_AREA_ID
PLKO/TKA02.KOKRS - Controling Area ID (or
alternative lookup on Company Code)
NVARCSTR
4
0
0
yes
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
12
DATE_KEY_ID
MLST.SDDAT Key determining the date for
milestone in sales order (domain
MLST_SDDAT)
NVARCSTR
10
0
0
yes
13
DAYS_ACTL_DURTN
Number of Days between MLST.LST_ACTDT Actual date (Milestone met) and MLST.DATEH DECIMAL
- Milestone created on
48
22
7
yes
14
DAYS_DIFF_FIXED_B
ASIC
Number of Days between Fixed Basic and
Actual Milestone end
DECIMAL
48
22
7
yes
15
DAYS_DIFF_FIXED_F
CST
Number of Days between Fixed Forecast and
Actual Milestone end
DECIMAL
48
22
7
yes
16
DAYS_DIFF_SCHED_
BASIC
Number of Days between Scheduled Basic and DECIMAL
Actual Milestone end
48
22
7
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
63
Appendix
Table Column Details
17
DAYS_DIFF_SCHED_
FCST
Number of Days between Scheduled Forecast
and Actual Milestone end
18
DAYS_SCHED_DUR
TN
19
DIM_SRC_ID_DOCCT
G
20
DIM_SRC_ID_DTKEY
Number of Days between MLST.TEDAT Scheduled milestone date (Basic) and
MLST.DATEH - Milestone created on
Dimension Source. This is a combined
dimension combining different varieties of
"Reference Date Key" from different sources.
This field identifies the source of "Referere
Dimension Source. This is a combined
dimension combining different varieties of
"Reference Date Key" from different sources.
This field identifies the source of "Referere
21
DOC_CATEG_ID
22
FIXED_BASIC_END_D
ATE
23
FIXED_FCST_END_D
ATE
24
FUNCTION_FLAG
25
DECIMAL
48
22
7
yes
DECIMAL
48
22
7
yes
NVARCSTR
10
0
0
yes
NVARCSTR
10
0
0
yes
NVARCSTR
10
0
0
yes
DATETIME
24
0
9
yes
DATETIME
24
0
9
yes
MLST.KZ_WFLOW - Indicator: Milestone is
used for milestone functions
INTEGER
4
0
0
yes
GROUP_APPLICTN_ID
MLST.PLNTY - Standard network type
-Application of the task list
NVARCSTR
1
0
0
yes
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
29
HOURS_ACTL_DUR
TN
Number of Hours between MLST.LST_ACTDT
- Actual date (Milestone met) and
DECIMAL
MLST.DATEH - Milestone created on
48
22
7
yes
30
HOURS_DIFF_FIXED_
BASIC
Number of Hours between Fixed Basic and
Actual Milestone end
DECIMAL
48
22
7
yes
31
HOURS_DIFF_FIXED_
FCST
Number of Hours between Fixed Forecast and DECIMAL
Actual Milestone end
48
22
7
yes
32
HOURS_DIFF_SCHED
_BASIC
Number of Hours between Scheduled Basic
and Actual Milestone end
DECIMAL
48
22
7
yes
33
HOURS_DIFF_SCHED
_FCST
Number of Hours between Scheduled Forecast DECIMAL
and Actual Milestone end
48
22
7
yes
34
HOURS_SCHED_DU
RTN
Number of Hours between MLST.TEDAT Scheduled milestone date (Basic) and
MLST.DATEH - Milestone created on
48
22
7
yes
MLST.AUTYP - Order category (AUFTYP Internal Order category)
MLST.EDATU - Fixed milestone date
(basic)+MLST.EZEIT - Fixed milestone time
(Basic). Fixed date on which the milestone
should be reached (no offset is possible)
MLST.PDATU - Fixed milestone date
(F)+MLST.PZEIT - Fixed milestone time (F). Forecast date on which the milestone should
be reached (no offset is possible)
DECIMAL
Rapid Mart Data Schema
A
64
Appendix
Table Column Details
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
37
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
38
LOAD_TIME
Time loaded into Rapid mart
NVARCSTR
8
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
42
NETWORK_PROFILE_
ID
PLKO.PROFIDNETZ -Profile (network)
NVARCSTR
7
0
0
yes
43
OFFSET_TO_FINISH_
FLAG
MLST.DLTAS - Ind: Reference for offset
(start/finish activity date)
INTEGER
4
0
0
yes
44
OPERATN_ROUTING_
ID
MLST.AUFPL - Routing number for operations NVARCSTR
in the order
10
0
0
yes
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
47
PRCNT_COMPLETE
MLST.LST_FERTG - Percentage of completion INTEGER
(%)
4
0
0
yes
48
PRCNT_OFFSET
MLST.PRCNT - Percentual offset of milestone
to activity date
INTEGER
4
0
0
yes
49
PROGRESS_ANALYSI
S_FLAG
MLST.KZ_LSTWR - Milestone relevant for
progress analysis
INTEGER
4
0
0
yes
50
PROJ_ELEM_ID
NVARCSTR
24
0
0
yes
51
PROJ_ELEM_ID_STD
NVARCSTR
24
0
0
yes
52
PROJ_ID
NVARCSTR
24
0
0
yes
AFVC.PROJN -Work breakdown structure
element (WBS element) / Lookup to
PRPS.POSID - Project Element (WBS)
External ID
MLST.PSPNR - WBS element / Lookup to
PRPS.POSID - Project Element (WBS)
External ID
PROJ.PSPID - Project External ID
Rapid Mart Data Schema
A
65
Appendix
Table Column Details
53
PURCH_ORG_ID
T001W.EKORG Purchasing organization
(lookup)
NVARCSTR
4
0
0
yes
54
QTY_OFFSET
MLST.DELTA - Offset for milestone date
INTEGER
4
0
0
yes
55
RELEASE_STOP_FLA
G
MLST.KZ_FRMST - Release stop indicator
INTEGER
4
0
0
yes
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
58
SALES_DOC_DATE_F
LAG
MLST.KZ_FAKTP - Milestone is relevant for
date in sales document
4
0
0
yes
59
SCHED_BASIC_END_
DATE
24
0
9
yes
60
SCHED_FCST_END_D
ATE
24
0
9
yes
61
SECS_ACTL_DURTN
Number of Seconds between
MLST.LST_ACTDT - Actual date (Milestone
DECIMAL
met) and MLST.DATEH - Milestone created on
48
22
7
yes
62
SECS_DIFF_FIXED_B
ASIC
Number of Seconds between Fixed Basic and
Actual Milestone end
DECIMAL
48
22
7
yes
63
SECS_DIFF_FIXED_F
CST
Number of Seconds between Fixed Forecast
and Actual Milestone end
DECIMAL
48
22
7
yes
64
SECS_DIFF_SCHED_
BASIC
Number of Seconds between Scheduled Basic DECIMAL
and Actual Milestone end
48
22
7
yes
65
SECS_DIFF_SCHED_
FCST
Number of Seconds between Scheduled
Forecast and Actual Milestone end
DECIMAL
48
22
7
yes
66
SECS_SCHED_DUR
TN
Number of Seconds between MLST.TEDAT Scheduled milestone date (Basic) and
MLST.DATEH - Milestone created on
DECIMAL
48
22
7
yes
67
STATUS_PROFILE_ID
MLST.STSMA - Status profile (for the network) NVARCSTR
8
0
0
yes
68
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
69
TREND_ANALYSIS_FL
AG
MLST.KZ_TREND - Milestone relevant for
trend analysis
INTEGER
4
0
0
yes
70
UOM_ID_OFFSET
MLST.DELTE - Time unit for offset of milestone NVARCSTR
date
3
0
0
yes
INTEGER
MLST.TEDAT - Scheduled milestone date
(Basic); + MLST.TETIM - Scheduled milestone DATETIME
time (Basic). You can offset the milestone to
the start, finish value
MLST.TPDAT - Scheduled milestone date
(Forecast)+ MLST.TPTIM - Scheduled
DATETIME
milestone time (Forecast). It can be offset
Rapid Mart Data Schema
A
66
Appendix
Table Column Details
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
73
VALID_TO_DATE
The date until which this record is effective. It is
automatically generated by the Effective_Date DATETIME
transform
24
0
9
yes
74
WORK_CNTR_CATE
G_ID
CRHD.VERWE - Work center category ID
lookup
NVARCSTR
4
0
0
yes
75
WORK_CNTR_ID
CRHD.ARBPL - Work center- Visible ID in
SAP
NVARCSTR
8
0
0
yes
A
MILESTONE_USAGE
Milestone usage descriptive attributes from T433T
Column Desc
Column
Datatype
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time loaded into Rapid mart
NVARCSTR
8
0
0
yes
3
USAGE_DESCR
T433T.MSTXT - Milestone Usage description
NVARCSTR
40
0
0
yes
4
USAGE_ID
T433T.MLSTN - Milestone Usage ID
NVARCSTR
5
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
67
Appendix
Table Column Details
A
MRP_CONTROLLER
MRP controller information by plant from T024D
Column Desc
Column
Datatype
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
3
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
4
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
5
MRP_CTRLLER_ID
T024D.DISPO - MRP controller
NVARCSTR
3
0
0
no
6
MRP_CTRLLER_NA
ME
T024D.DSNAM - Name of MRP controller
NVARCSTR
18
0
0
yes
7
MRP_CTRLLER_PH
ONE
T024D.DSTEL - MRP controllers telephone
number
NVARCSTR
12
0
0
yes
8
PLANT_ID
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
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
68
Appendix
Table Column Details
A
NETWORK_HIER_VR
Vertical representation of Network Relationship stored in AFAB
Column Desc
Column
Datatype
CHILD_OPERATN_DE
SCR
AFVC.LTXA1 - Operation short text - Child
NVARCSTR
40
0
0
yes
2
CHILD_OPERATN_FU
LL_NAME
Child Node full name = Activity Number
(Operation Number) + Descr
NVARCSTR
60
0
0
yes
3
CHILD_OPERATN_NU
M
AFVC.VORNR Activity Number - child node
NVARCSTR
4
0
0
yes
4
CHILD_ORDER_DESC
R
AUFK-KTEXT - Internal Order Description -for
the child node
NVARCSTR
40
0
0
yes
5
DEPTH
Hierarchy Depth
INTEGER
4
0
0
yes
6
INTERNAL_ORDER_ID
_CHILD
AUFK.AUFNR - Network Id (order number) for
the child node
NVARCSTR
12
0
0
yes
7
INTERNAL_ORDER_ID
_PARENT
AUFK.AUFNR - Order Number of the Parent
node
NVARCSTR
12
0
0
yes
8
LEAF_FLAG
Node is the child (1/0)
INTEGER
4
0
0
yes
9
LEVEL_DISPLAY
Idented display Hierarchy Depth; hard-coded
up to 60 levels
NVARCSTR
250
0
0
yes
10
LOAD_DATE
Date and time when the record was loaded into DATETIME
the target database
24
0
9
yes
11
LOAD_TIME
Time when the record was loaded into the
target database
NVARCSTR
8
0
0
yes
12
OPERATN_ROUTING_ PK
ID_CHILD
AFAB.AUFPL_NCH/AFAB.AUFPL_VOR - No.
identifying the network to which the
successor/predecessor belongs
NVARCSTR
10
0
0
no
13
OPERATN_ROUTING_ PK
ID_PARENT
AFAB.AUFPL_NCH/AFAB.AUFPL_VOR - No.
identifying the network to which the
successor/predecessor belongs
NVARCSTR
10
0
0
no
14
OPERATN_SEQ_ID_C PK
HILD
AFAB.APLZL_NCH/AFAB.APLZL_VOR - No.
identifying the network to which the
successor/predecessor belongs
NVARCSTR
8
0
0
no
15
OPERATN_SEQ_ID_P PK
ARENT
AFAB.APLZL_NCH/AFAB.APLZL_VOR - No.
identifying the network to which the
successor/predecessor belongs
NVARCSTR
8
0
0
no
16
PARENT_OPERATN
_DESCR
AFVC.LTXA1 - Operation short text - Parent
NVARCSTR
40
0
0
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
69
Appendix
Table Column Details
17
PARENT_OPERATN_F
ULL_NAME
Parent Node full name = Activity Number
(Operation Number) + Descr
NVARCSTR
60
0
0
yes
18
PARENT_OPERATN
_NUM
AFVC.VORNR Node number of the Parent
operation
NVARCSTR
4
0
0
yes
19
PARENT_ORDER_D
ESCR
AUFK-KTEXT - Internal Order Description -for
the Parent node
NVARCSTR
40
0
0
yes
20
RELATIONSHIP_TYPE PK
_ID
AFAB.AOBAR - Type of relationship (lookup
onto TCN2T)
NVARCSTR
2
0
0
no
21
ROOT_FLAG
Node is Root (1/0)
INTEGER
4
0
0
yes
A
NETWORK_PROFILE
Network profile descriptive attributes from TCN41, TCN41T
Column Desc
Column
Datatype
GROUP_APPLICTN_D
ESCR
TCN4T.PROFI_TXT -Text for Profile
NVARCSTR
40
0
0
yes
2
GROUP_APPLICTN_ID PK
TCN41.PLNAW -Application of the task list
NVARCSTR
1
0
0
no
3
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
4
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
5
NETWORK_PROFILE_ PK
ID
TCN41.PROFIDNETZ -Network profile
NVARCSTR
7
0
0
no
6
UOM_CODE_DURTN
T006A.MSEH3 -- Unit of Meas. ID in Local
Language (External unit of measurement
commercial format (3-char))
NVARCSTR
3
0
0
yes
7
UOM_CODE_WORK
T006A.MSEH3 -- Unit of Meas. ID in Local
Language (External unit of measurement
commercial format (3-char))
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
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
70
Appendix
Table Column Details
A
NETWORK_RELATIONSHIP_FACT
Parent/Child relationship from AFAB for Internal Order Operations
Column Desc
Column
Datatype
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
5
DAYS_DURTN_EARLS
T
Number of Days for Network Relationship
based on Eraliest start/end dates
DECIMAL
48
22
7
yes
6
DAYS_DURTN_LATES
T
Number of Days for Network Relationship
based on Latest start/end dates
DECIMAL
48
22
7
yes
7
DAYS_DURTN_MAX
Max Number of Days for Network Relationship.
Calculated as difference between latest end
DECIMAL
date and earliest start date
48
22
7
yes
8
DAYS_DURTN_MIN
Min Number of Days for Network Relationship.
Calculated as difference between earliest end DECIMAL
date and latest start date
48
22
7
yes
9
EARLST_END_DATE
AFAB.FEABD - Earliest finish date for the
relationship+AFAB.FEABZ - Earliest finish time DATETIME
for the relationship
24
0
9
yes
10
EARLST_START_DAT
E
AFAB.FSABD - Earliest start date for the
relationship + AFAB.FSABZ - Earliest start time DATETIME
for the relationship
24
0
9
yes
11
FUNCTNL_AREA_ID
AFVC/AUFK.FUNC_AREA -Functional Area
NVARCSTR
16
0
0
yes
12
HOURS_DURTN_EA
RLST
Number of Hours for Network Relationship
based on Eraliest start/end dates
DECIMAL
48
22
7
yes
13
HOURS_DURTN_LA
TEST
Number of Hours for Network Relationship
based on Latest start/end dates
DECIMAL
48
22
7
yes
14
HOURS_DURTN_MAX
Max Number of Hours for Network
Relationship. Calculated as difference between DECIMAL
latest end date and earliest start date
48
22
7
yes
15
HOURS_DURTN_MIN
Min Number of Hours for Network Relationship.
Calculated as difference between earliest end DECIMAL
date and latest start date
48
22
7
yes
16
INTERNAL_ORDER_ID
AFKO.AUFNR - Order Number
12
0
0
yes
#
Column Name
1
Key
NVARCSTR
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
71
Appendix
Table Column Details
17
INTERNAL_ORDER_ID
_PAR
AUFK.AUFNR - Order Number of the Parent
node
18
LATEST_END_DATE
19
12
0
0
yes
AFAB.SEABD - Latest finish date of the
relationship+ AFAB.SEABZ - Latest finish time DATETIME
of the relationship
24
0
9
yes
LATEST_START_DAT
E
AFAB.SSABD - Latest start date of the
relationship + AFAB.SSABZ - Latest start time
of the relationship
DATETIME
24
0
9
yes
20
LOAD_DATE
Date and time when the record loaded into
RapidMart
DATETIME
24
0
9
yes
21
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
8
0
0
yes
22
LOCATN_ID
AUFK.STORT Plant Location
NVARCSTR
10
0
0
yes
23
MAX_INTERVAL_FLA
G
AFAB.MIMAX - Indicates whether maximum
time interval will be considered
INTEGER
4
0
0
no
24
MINS_DURTN_EARLS
T
Number of Minutes for Network Relationship
based on Eraliest start/end dates
DECIMAL
48
22
7
yes
25
MINS_DURTN_LATES
T
Number of Minutes for Network Relationship
based on Latest start/end dates
DECIMAL
48
22
7
yes
26
MINS_DURTN_MAX
Max Number of Minutes for Network
Relationship. Calculated as difference between DECIMAL
latest end date and earliest start date
48
22
7
yes
27
MINS_DURTN_MIN
Min Number of Minutes for Network
Relationship. Calculated as difference between DECIMAL
earliest end date and latest start date
48
22
7
yes
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
30
OPERATN_DESCR
AFVC.LTXA1 - Parent Operation short text (for NVARCSTR
child node)
40
0
0
yes
31
OPERATN_DESCR_
PAR
AFVC.LTXA1 - Parent Operation short text - for NVARCSTR
parent node
40
0
0
yes
32
OPERATN_FULL_NAM
E
Child Node full name - Activity Number
(Operation Number) + Description
NVARCSTR
256
0
0
yes
33
OPERATN_FULL_NAM
E_PAR
Parent Node full name - Activity Number
(Operation Number) + Description
NVARCSTR
256
0
0
yes
34
OPERATN_NUM
AFVC.VORNR Activity Number
NVARCSTR
4
0
0
yes
PK
NVARCSTR
Rapid Mart Data Schema
A
72
Appendix
Table Column Details
35
OPERATN_NUM_PAR
AFVC.VORNR Node number of the Parent
operation
NVARCSTR
4
0
0
yes
36
OPERATN_ROUTING_ PK
ID
AFAB.AUFPL_NCH - No. identifying the
network to which the successor belongs
NVARCSTR
10
0
0
no
37
OPERATN_ROUTING_ PK
ID_PAR
AFAB.AUFPL_VOR - No. identifying the
network to which the predecessor belong
NVARCSTR
10
0
0
no
38
OPERATN_SEQ_ID
PK
AFAB.APLZL_NCH - Internal counter for the
Child operation
NVARCSTR
8
0
0
no
39
OPERATN_SEQ_ID_P PK
AR
AFAB.APLZL_VOR - Internal counter for the
parent Operation
NVARCSTR
8
0
0
no
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
42
PROJ_ELEM_ID
AFVC/AFPO.PROJN - Work breakdown
structure element (WBS element) Lookup on
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
43
PROJ_ID
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
44
PURCH_ORG_ID
T001W.EKORG Purchasing organization
(lookup)
NVARCSTR
4
0
0
yes
45
QTY_INTERVAL
AFAB.DAUER - Time interval between
relationships
DECIMAL
48
5
1
yes
46
RELATIONSHIP_TYPE PK
_ID
AFAB.AOBAR - Type of relationship (lookup
onto TCN2T)
NVARCSTR
2
0
0
no
47
RESOURCE_ID
AFAB/AFVC.ARBID - Object ID
NVARCSTR
8
0
0
yes
48
SECS_DURTN
AFAB.DAUTM - Relationship duration (in
seconds) as result of scheduling
DECIMAL
48
28
0
yes
49
STORAGE_LOCATN_I
D
AFPO.LGORT Storage location
NVARCSTR
4
0
0
yes
50
UOM_ID
AFAB.ZEINH - Unit for the time interval
between relationships
NVARCSTR
3
0
0
yes
51
VALUATN_AREA_ID
T001W.BWKEY Valuation area lookup
NVARCSTR
4
0
0
yes
52
WORK_CNTR_CATE
G_ID
CRHD.VERWE - Work center category ID
lookup
NVARCSTR
4
0
0
yes
Rapid Mart Data Schema
A
73
Appendix
Table Column Details
53
CRHD.ARBPL - Work center- Visible ID in
SAP
WORK_CNTR_ID
NVARCSTR
8
0
0
A
yes
OBJECT_CLASS
DD07T - Object Class reference dimension
Key
Dtype
Length Precision Scale
Is
Nullable
Column Name
1
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
2
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
3
OBJ_CLASS_DESCR
Object Class Domain Descritpion
NVARCSTR
60
0
0
yes
4
OBJ_CLASS_ID
Object Class Domain ID
NVARCSTR
10
0
0
no
PK
Column Desc
Column
Datatype
#
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 Desc
Column
Datatype
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
3
OBJ_NUM_TYPE_DES
CR
TBO01.TXT60, TXT10, TXT15, TXT 20 Description
NVARCSTR
60
0
0
yes
4
OBJ_NUM_TYPE_ID
TBO01.OBART -Object Type Code
NVARCSTR
2
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
74
Appendix
Table Column Details
A
OBJECT_STATUS
Object statuses from JEST
Column Desc
Column
Datatype
INTERNAL_ORDER_ID
JEST.OBJNR Object number - for 'OR' and
'NP' types - Internal Order ID
NVARCSTR
10
0
0
yes
2
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
3
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
4
OBJ_ID
JEST-OBJNR - Object number
NVARCSTR
22
0
0
no
5
OBJ_NUM_TYPE_DES
CR
TBO01, TXT10 - Text, length 10
NVARCSTR
10
0
0
yes
6
OBJ_NUM_TYPE_ID
RPSCO.OBJNR Object number first 2
characters
NVARCSTR
2
0
0
yes
7
OPERATN_ROUTING_
ID
JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR
number of operations in the order
10
0
0
yes
8
OPERATN_SEQ_ID
JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR
number counter for order
8
0
0
yes
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
11
PROJ_ELEM_ID
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
12
PROJ_ID
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
13
STATUS_CODE
TJ02T.TXT04 - Individual status of an object
(short form)
NVARCSTR
4
0
0
yes
14
STATUS_CODE_NA
ME
TJ02T.TXT04 - Individual status of an object
(short form) + JEST.STAT - Object
status+TJ02T.TXT30 -Object status
NVARCSTR
60
0
0
no
15
STATUS_DESCR
TJ02T.TXT30 -Object status
NVARCSTR
30
0
0
yes
16
STATUS_ID
JEST.STAT - Object status
NVARCSTR
5
0
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
75
Appendix
Table Column Details
A
OBJECT_STATUS_HZ
Dimensional component loading horizontally represented selected ERP Object status sinformation from JEST for selected Statuses from
OBJECT_STATUS
Key
Column
Datatype
Is
Nullable
Column Name
1
ACCEPT_FLAG
JEST-STAT (lookup) -ACPT object is Accepted INTEGER
status is active (1 is active, 0 is inactive)
4
0
0
yes
2
BUDGET_FLAG
JEST-STAT (lookup) -BUDG object is
Budgeted status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
3
BUDGET_INSUFFICNT
_FLAG
JEST-STAT (lookup) -ISBD object is
Insuffiently Budgeted status is active (1 is
active, 0 is inactive)
INTEGER
4
0
0
yes
4
CLOSE_FLAG
JEST-STAT (lookup) -CLSD object is Close
status is active (1 is active, 0 is inactive)
INTEGER
4
0
0
yes
5
COST_PLAN_FLAG
JEST-STAT (lookup) -PLCS object is Cost
Planned status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
6
COST_POST_FLAG
JEST-STAT (lookup) -CSPS object is Cost
Posted status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
7
CREATE_FLAG
JEST-STAT (lookup) -CRTD order is created
status is active (1 is active, 0 is inactive)
INTEGER
4
0
0
yes
8
DELETE_FLAG
JEST-STAT (lookup) - DLFL, DLT object is
deleted status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
9
FCST_ONLY_FLAG
JEST-STAT (lookup) -NSCH object is Not
Scheduled status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
10
FINAL_CONFIRM_FLA
G
JEST-STAT (lookup) - CNF object is finally
confirmed status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
11
FINAL_RELEASE_FLA
G
JEST-STAT (lookup) -REL object is Released
status is active (1 is active, 0 is inactive)
INTEGER
4
0
0
yes
12
INTERNAL_ORDER_ID
JEST.OBJNR Object number - for 'OR' and
'NP' types - Internal Order ID
NVARCSTR
10
0
0
yes
13
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
14
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
15
MANUAL_CONFIRM_F
LAG
JEST-STAT (lookup) - MCNF object is
Manually confirmed status is active (1 is active, INTEGER
0 is inactive)
4
0
0
yes
16
OBJ_ID
JEST-OBJNR - Object number
22
0
0
no
PK
Column Desc
Dtype
Length Precision Scale
#
NVARCSTR
Rapid Mart Data Schema
76
Appendix
Table Column Details
17
OBJ_NUM_TYPE_DES
CR
TBO01, TXT10 - Text, length 10
NVARCSTR
10
0
0
yes
18
OBJ_NUM_TYPE_ID
RPSCO.OBJNR Object number first 2
characters
NVARCSTR
2
0
0
yes
19
OPERATN_ROUTING_
ID
JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR
number of operations in the order
10
0
0
yes
20
OPERATN_SEQ_ID
JEST.OBJNR for types 'NV' and 'OV' - Routing NVARCSTR
number counter for order
8
0
0
yes
21
OTHER_FLAG
JEST-STAT (lookup) -any other status is
active (1 is active, 0 is inactive)
INTEGER
4
0
0
yes
22
PARTL_CONFIRM_FL
AG
JEST-STAT (lookup) - PCNF object is partially
confirmed status is active (1 is active, 0 is
INTEGER
inactive)
4
0
0
yes
23
PARTL_RELEASE_FL
AG
JEST-STAT (lookup) -PRREL object is Partially
Released status is active (1 is active, 0 is
INTEGER
inactive)
4
0
0
yes
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
26
PROJ_ELEM_ID
24
0
0
yes
27
PROJ_ID
24
0
0
yes
28
TECHN_COMPLT_FLA
G
JEST.OBJRN - WBS for 'PR' object types or
derived from 'NV' type (network activity) then
NVARCSTR
lookup on PRPS.POSID - WBS element
External ID
JEST.OBJNR for 'PD' object type-Current
number of the appropriate project (or derived
from Project Element 'PR' type) then lookup on NVARCSTR
PROJ.PSPID - Project ID (external)
JEST-STAT (lookup) -TECO object is
Technically Completed status is active (1 is
INTEGER
active, 0 is inactive)
4
0
0
yes
29
TTL_NUM_ACTIVE_ST
ATUS
JEST-STAT- total number of actvie statuses
set to 1 for the object
4
0
0
yes
INTEGER
Rapid Mart Data Schema
A
77
Appendix
Table Column Details
A
OBJECT_TYPE
DD07T - Object Type reference dimension
#
Column Name
Key
Column Desc
Column
Datatype
1
DIM_SRC_ID
PK
Dimension Source. This is a combined
dimension combining different varieties of
"object type" from different sources. This field
identifies the source of "object type"
NVARCSTR
2
LOAD_DATE
3
Dtype
Length Precision Scale
Is
Nullable
10
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
4
OBJ_TYPE_DESCR
Description of Object Type
NVARCSTR
75
0
0
yes
5
OBJ_TYPE_ID
Object Type domain value ID
NVARCSTR
10
0
0
no
PK
Rapid Mart Data Schema
78
Appendix
Table Column Details
A
ORDER_OPERATION
Order Operation including Sequences from AFVC
Column Desc
Column
Datatype
ACTIVITY_ID
AFVC.LARNT - Activity Type
NVARCSTR
6
0
0
yes
2
AMT_COST_MTRL
AFVC.MAT_PRKST - Material planning in
networks: primary costs
DECIMAL
48
11
2
yes
3
AMT_COST_TTL
AFVC.PRKST - Total Costs in the activity Planned
DECIMAL
48
11
2
yes
4
AMT_PRICE
AFVC.PREIS - Price
DECIMAL
48
11
2
yes
5
BUS_AREA_FULL_NA
ME
AFVC.GSBER+TGSBT-GTEXT - Business
Area ID and Descritpion
NVARCSTR
40
0
0
yes
6
BUS_AREA_ID
AFVC.GSBER - Business Area
NVARCSTR
4
0
0
yes
7
CHART_OF_ACCT_ID
T001.KTOPL-Chart of accts ID - Lookup
NVARCSTR
4
0
0
yes
8
CMPNY_CODE_FULL_
NAME
T001K -BUKRS + T001. BUTXT - full Name of
the company code or company
NVARCSTR
120
0
0
yes
9
CMPNY_CODE_ID
AFVC.BUKRS Company Code
NVARCSTR
4
0
0
yes
10
COMPLT_FLAG
AFVC-LEKNW - Indicator showing no
remaining work expected if set to 1
INTEGER
4
0
0
yes
11
COSTNG_FLAG
AFVC.SELKZ - Selection indicator for costing
line items
INTEGER
4
0
0
yes
12
COST_ELEM_ID
AFVC.SAKTO - Cost Element
NVARCSTR
10
0
0
yes
13
CTRL_AREA_FULL_N
AME
TKA02.KOKRS +TKA01.BEZEI - Concatenated NVARCSTR
ID and Name for controlling area name
32
0
0
yes
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
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
79
Appendix
Table Column Details
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
19
GROUP_LINE_ID
AFVC.PLNFL - Sequence of operations within
a task list
NVARCSTR
6
0
0
yes
20
GROUP_NODE_ID
AFVC.PLNKN - Number of the task list node
NVARCSTR
8
0
0
yes
21
INTERNAL_ORDER_ID
AFKO.AUFNR - Internal Order Number Production
NVARCSTR
12
0
0
yes
22
LOAD_DATE
Date loaded into RapidMart
DATETIME
24
0
9
yes
23
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
8
0
0
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
27
OBJ_NUM_TYPE_DES
CR
TBO01, TXT10 - Text, length 10
NVARCSTR
10
0
0
yes
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
33
OPERATN_ROUTING_ PK
ID
AFVC.AUFPL - Routing number of operations
in the order
NVARCSTR
10
0
0
no
34
OPERATN_SEQ_ID
AFVC.APLZL - General counter for order
NVARCSTR
8
0
0
no
PK
Rapid Mart Data Schema
A
80
Appendix
Table Column Details
35
PLANT_FULL_NAME
STPO-PSWRK + T001W.NAME1 - Plant ID
and Plant Name
NVARCSTR
40
0
0
yes
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
40
PROJ_ELEM_ID
AFVC.PSPNR - Standard WBS element /
Lookup on PRPS.POSID - Project Element
(WBS) External ID
NVARCSTR
24
0
0
yes
41
PROJ_ID
PRPS.PSPHI - Project ID / Lookup on
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
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
46
SYSTEM_CONDITN_D
ESCR
T357M_T-ANLZUX - Operating status text
NVARCSTR
40
0
0
yes
47
SYSTEM_CONDITN_I
D
AFVC-ANLZU - System condition
NVARCSTR
1
0
0
yes
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
Rapid Mart Data Schema
A
81
Appendix
Table Column Details
A
PEGGING_OBJECT
Details of Pegging Objects from PEGOB, PEGQTY
Key
Column
Datatype
#
Column Name
Column Desc
1
CMPNY_CODE_FULL_
NAME
PEGOB.BUKRS - Company Code + Company NVARCSTR
Code Name from T001
2
CMPNY_CODE_ID
PEGOB.BUKRS - Company Code
3
CTRL_AREA_FULL_N
AME
4
Dtype
Length Precision Scale
Is
Nullable
120
0
0
yes
NVARCSTR
4
0
0
yes
Lookup on TKA02 PEGOB.KOKRS Controlling Area+name
NVARCSTR
120
0
0
yes
CTRL_AREA_ID
PEGOB.KOKRS - Controlling Area
NVARCSTR
4
0
0
yes
5
CURR_ID
PEGOB.WAERS - Currency Key
NVARCSTR
5
0
0
yes
6
DELETE_FLAG
PEGOB.DELFG - Deletion indicator for peg
(1/0)
INTEGER
4
0
0
yes
7
FIXED_ALLOCTN_FLA
G
PEGQTY.FIXED - Indicator: Allocated quantity INTEGER
fixed (1/0)
4
0
0
yes
8
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
9
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
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
PEGOB.OBJNR - Object number
NVARCSTR
22
0
0
no
13
OBJ_ID_ORIGINAL
PEGOB.ORGREQ - Object number of original
requirement (RESB-OBJNR)
NVARCSTR
22
0
0
yes
14
OBJ_ID_REPLENISH
PEGOB.REPOBJ - Object number of
replenishment elem. used for static peggin
NVARCSTR
22
0
0
yes
15
PEG_CATEG_DESCR
DD07T - PGASSCAT domain Lookup
description of Pegging Category
NVARCSTR
60
0
0
yes
16
PEG_CATEG_FULL_N PK
AME
PEGQTY.ASSCAT - Pegging category of the
assigned quantity+DD07T - PGASSCAT
domain Lookup description of Pegging
Category
NVARCSTR
120
0
0
no
PK
Rapid Mart Data Schema
82
Appendix
Table Column Details
17
PEG_CATEG_ID
PEGQTY.ASSCAT - Pegging category of the
assigned quantity
NVARCSTR
2
0
0
yes
18
PEG_COMPLETE_FLA
G
PEGOB.CLOSED - Indicator: Pegging
completed (1/0)
INTEGER
4
0
0
yes
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
21
PLANT_FULL_NAME
PEGOB.WERKS - Plant ID+T001W.NAME1 lookup on Plant Name
NVARCSTR
120
0
0
yes
22
PLANT_ID
PEGOB.WERKS - Plant
NVARCSTR
4
0
0
yes
23
PROJ_ELEM_ID_COM
PONENT
PEGOB.CMPPNR - Component WBS element NVARCSTR
24
0
0
yes
24
PROJ_ELEM_ID_GRP
PEGOB.GRPNR - Grouping WBS element. A
grouping WBS element is a WBS element that NVARCSTR
has valuated individual stock and has a special
function in materials requirements planni
24
0
0
yes
25
PROJ_ELEM_NAME_C
OMPONENT
PRPS.POSKI - WBS element short
identification (lookup) -for Component project
NVARCSTR
16
0
0
yes
26
PROJ_ELEM_NAME
_GRP
PRPS.POSKI - WBS element short
identification (lookup)
NVARCSTR
16
0
0
yes
27
QTY_ASSIGN
PEGQTY.QUANTY - Proportion assigned to
pegging object
DECIMAL
48
15
5
yes
28
QTY_TTL_REPLENISH
PEGOB.TOTQTY - Total quantity of
replenishm. elem. used for static pegging
DECIMAL
48
13
3
yes
29
QTY_TTL_REQ
PEGOB.QTYNEEDED - Quantity necessary to DECIMAL
satisfy the original requirement
48
15
5
yes
30
QTY_TTL_RESERVAT
N
PEGOB.REQQTY - Total required quantity of
the reservation
DECIMAL
48
13
3
yes
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
33
UOM_ID_RESERVATN
PEGOB.REQUNIT - Base unit of the original
requirement
NVARCSTR
3
0
0
yes
Rapid Mart Data Schema
A
83
Appendix
Table Column Details
A
PLANT
Contains Plant Level Information
Column Desc
Column
Datatype
ADDRESS_ID
Address ID
NVARCSTR
10
0
0
yes
2
BATCH_STATUS_FLA
G
Batch Status Flag
NVARCSTR
5
0
0
yes
3
CITY
T001W.ORT01 CIty
NVARCSTR
40
0
0
yes
4
CMPNY_CODE_ID
Company code
NVARCSTR
4
0
0
yes
5
CMPNY_CODE_NAME
Company Code Name
NVARCSTR
40
0
0
yes
6
COUNTRY_ID
Country ID (Abbreviation)
NVARCSTR
3
0
0
yes
7
COUNTRY_NAME
Country Name (Full Name)
NVARCSTR
15
0
0
yes
8
CTRL_AREA_ID
Controlling area code
NVARCSTR
4
0
0
yes
9
CTRL_AREA_NAME
Control Area Name
NVARCSTR
25
0
0
yes
10
DISTRICT
District
NVARCSTR
40
0
0
yes
11
FAX
Fax Number
NVARCSTR
40
0
0
yes
12
HOUSE_NUMBER
House Number
NVARCSTR
10
0
0
yes
13
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
14
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
15
PHONE
Phone
NVARCSTR
30
0
0
yes
16
PLANT_FULL_NAME
ID and Name
NVARCSTR
120
0
0
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
84
Appendix
Table Column Details
17
PLANT_ID
18
PK
T001W.WERKS Plant
NVARCSTR
4
0
0
no
PLANT_NAME
Plant name
NVARCSTR
40
0
0
yes
19
PLANT_NAME_01
T001W.NAME1 Plant Name
NVARCSTR
40
0
0
yes
20
PLANT_NAME_02
T001W.NAME2 Plant Name
NVARCSTR
40
0
0
yes
21
PLANT_NAME_03
Plant name 3
NVARCSTR
40
0
0
yes
22
PLANT_NAME_04
Plant name 3
NVARCSTR
40
0
0
yes
23
PURCH_ORG_ID
T001W.EKORG Purchasing Organization
NVARCSTR
4
0
0
yes
24
PURCH_ORG_NAME
T001W.CHAZV Batch Management Status
Indicator
NVARCSTR
20
0
0
yes
25
REGION_ID
Region ID (Abbreviation of US State
NVARCSTR
3
0
0
yes
26
REGION_NAME
Region Name (Full Name of US State
NVARCSTR
20
0
0
yes
27
SALES_ORG_ID
T001W.VKORG Sales Organization
NVARCSTR
4
0
0
yes
28
SALES_ORG_NAME
Sales Organization name
NVARCSTR
25
0
0
yes
29
STREET
Street name
NVARCSTR
60
0
0
yes
30
VALUATN_AREA_ID
T001.BWKEY Valuation Area Key
NVARCSTR
4
0
0
yes
31
ZIP
Postal Code
NVARCSTR
10
0
0
yes
Rapid Mart Data Schema
A
85
Appendix
Table Column Details
A
PLANT_LOCATION
Plant Location attributes from T499S
Column Desc
Column
Datatype
ADDRESS_ID
Address
NVARCSTR
10
0
0
yes
2
CITY
City
NVARCSTR
40
0
0
yes
3
CMPNY_CODE_ID
Company Code ID
NVARCSTR
4
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
8
DISTRICT
District
NVARCSTR
40
0
0
yes
9
FAX
First fax no.: dialling code+number
NVARCSTR
30
0
0
yes
10
HOUSE_NUMBER
House Number
NVARCSTR
10
0
0
yes
11
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
12
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
13
LOCATN_FULL_NAME
T499S.STAND -Location ID + T499S.KTEXT
-Text (40 characters)
NVARCSTR
55
0
0
yes
14
LOCATN_ID
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
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
86
Appendix
Table Column Details
17
PLANT_FULL_NAME
ID and Name
NVARCSTR
120
0
0
yes
18
PLANT_ID
T499S.WERKS -Plant
NVARCSTR
4
0
0
no
19
PLANT_NAME
T001W.NAME1 -Name
NVARCSTR
30
0
0
yes
20
PLANT_NAME_01
Name 1
NVARCSTR
40
0
0
yes
21
PLANT_NAME_02
Name 2
NVARCSTR
40
0
0
yes
22
PLANT_NAME_03
Name 3
NVARCSTR
40
0
0
yes
23
PLANT_NAME_04
Name 4
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
PK
Rapid Mart Data Schema
A
87
Appendix
Table Column Details
A
PRODUCT_HIERARCHY
T179 - Product Hierarchy dimension
Key
Dtype
Length Precision Scale
Is
Nullable
Column Name
1
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
2
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
Product Hierarchy Current Node ID
NVARCSTR
18
0
0
no
8
PROD_LVL
Node Level depth
NVARCSTR
1
0
0
yes
PK
Column Desc
Column
Datatype
#
Rapid Mart Data Schema
88
Appendix
Table Column Details
A
PRODUCTION_ORDER_FACT
Production orders from AUFK/AFKO/AFPO (at AFPO order line level detail)
Column Desc
Column
Datatype
ACCT_ASSIGN_CATE
G_ID
AFPO.KNTTP - Account assignment category
NVARCSTR
1
0
0
no
2
ACTL_CONFRM_EN
D_DATE
AFKO.GLTRI - Actual finish confimred date
DATETIME
24
0
9
yes
3
ACTL_RELEASE_DAT
E
AFKO-FTRMI - Actual release date (Last
Operation is Released)
DATETIME
24
0
9
yes
4
ACTL_START_DATE
AFKO-GSTRI - Actual start date (First
Operation is Started)
DATETIME
24
0
9
yes
5
BASIC_END_DATE
AFKO-GLTRP - Finish (basic) date
DATETIME
24
0
9
yes
6
BASIC_START_DATE
AFKO-GSTRP - Order (basic) start date
DATETIME
24
0
9
yes
7
BATCH_ID
AFPO.CHARG - Batch number
NVARCSTR
10
0
0
no
8
BLOCK_FLAG
JEST-STAT (lookup) - LKD order is locked
status is active (1 is active, 0 is inactive)
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
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
89
Appendix
Table Column Details
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
21
DAYS_COMPLT_ACTL
Number of Days to actually complete a service DECIMAL
order (calcualted)
48
22
7
yes
22
DAYS_COMPLT_BASI
C
Number of Days to Basic complete a service
order (calcualted)
DECIMAL
48
22
7
yes
23
DAYS_COMPLT_FCST
Number of Forecast Days to complete a
service order (calcualted)
DECIMAL
48
22
7
yes
24
DAYS_COMPLT_SC
HED
Number of Days scheduled to complete a
service order (calcualted)
DECIMAL
48
22
7
yes
25
DAYS_GR_PROCESS
AFPO.WEBAZ -Goods receipt processing time INTEGER
in days
4
0
0
yes
26
DAYS_RELEASE_ACT
L
Number of Days to actually release a service
order (calcualted)
DECIMAL
48
22
7
yes
27
DAYS_RELEASE_SCH
ED
Number of Days scheduled to release a service DECIMAL
order (calcualted)
48
22
7
yes
28
DELETE_FLAG
JEST-STAT (lookup) - DLFL order is deleted
status is active (1 is active, 0 is inactive)
INTEGER
4
0
0
yes
29
DELIV_FLAG
Check table JEST for delilvered status
INTEGER
4
0
0
yes
30
DIM_SRC_ID_DOCTY
P
Dimension Source from table
AW_DIMENSION_SOURCE; hard-coded to
'INT_ORDER'
NVARCSTR
10
0
0
no
31
DOC_CATEG_ID
AUFK.AUTYP - Document Category from
multiple Sources in SAP
NVARCSTR
10
0
0
no
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
34
FCST_SCHED_END_D
ATE
AFKO.GLTPS - Scheduled forecast finish
DATETIME
24
0
9
yes
Rapid Mart Data Schema
A
90
Appendix
Table Column Details
35
FCST_SCHED_START
_DATE
AFKO.GSTPS - Scheduled forecast start
DATETIME
24
0
9
yes
36
FCST_START_DATE
AFKO.GSTPP - Forecast start date
DATETIME
24
0
9
yes
37
FINAL_CONFIRM_FLA
G
JEST-STAT (lookup) - CNF order is finally
confirmed status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
38
FUNCTNL_AREA_ID
AUFK.FUNC_AREA -Functional Area
NVARCSTR
16
0
0
no
39
GL_ACCT_ID
AUFK.SAKNR -G/L account for basic
settlement
NVARCSTR
10
0
0
no
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
44
HOURS_COMPLT_A
CTL
Number of Hours to actually complete a service DECIMAL
order (calcualted)
48
22
7
yes
45
HOURS_COMPLT_B
ASIC
Number of Hours to Basic complete a service
order (calcualted)
DECIMAL
48
22
7
yes
46
HOURS_COMPLT_F
CST
Number of Forecast Hours to complete a
service order (calcualted)
DECIMAL
48
22
7
yes
47
HOURS_COMPLT_S
CHED
Number of Hours scheduled to complete a
service order (calcualted)
DECIMAL
48
22
7
yes
48
INTERNAL_ORDER_ID PK
AFPO.AUFNR - Order Number
NVARCSTR
12
0
0
no
49
INTERNAL_ORDER_ID
_NETWRK_PAR
AFKO.NTZUE - Superior network number
(Internal Order Number)
NVARCSTR
12
0
0
yes
50
INTERNAL_ORDER_ID
_PAR
AFKO-MAUFNR - Superior order number
NVARCSTR
12
0
0
yes
51
LOAD_DATE
Date and time when the record loaded into
RapidMart
DATETIME
24
0
9
yes
52
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
8
0
0
yes
Rapid Mart Data Schema
A
91
Appendix
Table Column Details
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
55
MINS_COMPLT_ACTL
Number of Minutes to actually complete a
service order (calcualted)
DECIMAL
48
22
7
yes
56
MINS_COMPLT_BASI
C
Number of Minutes to Basic complete a service DECIMAL
order (calcualted)
48
22
7
yes
57
MINS_COMPLT_FCST
Number of Forecast Minutes to complete a
service order (calcualted)
DECIMAL
48
22
7
yes
58
MINS_COMPLT_SCHE
D
Number of Minutes scheduled to complete a
service order (calcualted)
DECIMAL
48
22
7
yes
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
62
NETWORK_PROFILE_
ID
AFKO.PROFID - Network Profile
NVARCSTR
7
0
0
no
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
67
OPERATN_ROUTING_
ID
AFKO-AUFPL - Routing number for operations NVARCSTR
in the order
10
0
0
yes
68
ORDER_LINE_ITEM_I PK
D
AFPO.POSNR - Order item number
NVARCSTR
4
0
0
no
69
ORDER_STATUS_ID
AUFK.ASTNR - Order status
NVARCSTR
2
0
0
no
70
PARTL_CONFIRM_FL
AG
JEST-STAT (lookup) - PCNF order is partially
confirmed status is active (1 is active, 0 is
inactive)
INTEGER
4
0
0
yes
Rapid Mart Data Schema
A
92
Appendix
Table Column Details
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
74
PRIORITY_CODE
AFKO.APRIO - User specified order priority for NVARCSTR
information purposes
1
0
0
yes
75
PROD_HIER_ID
MARA.PRDHA - Product Hierarchy ID - Look
up based on AFIH.SERMAT
NVARCSTR
18
0
0
no
76
PROD_ORDER_DES
CR
AUFK-KTEXT - Short text
NVARCSTR
40
0
0
yes
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
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
no
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
84
QTY_PROD
AFPO.WEMNG - Quantity of goods produced
and received for the order item
DECIMAL
48
13
3
yes
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
87
RESERVATN_ID
AFKO.RSNUM - Number of reservation/
dependent requirement
NVARCSTR
10
0
0
yes
88
ROUTING_ID
Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR
11
0
0
no
Rapid Mart Data Schema
A
93
Appendix
Table Column Details
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
92
SCHED_LINE_ITEM_I
D
AFPO.KDEIN - Delivery schedule (sales order) NVARCSTR
4
0
0
yes
93
SCHED_RELEASE_DA
TE
AFKO-FTRMS - Scheduled release date
DATETIME
24
0
9
yes
94
SCHED_START_DATE
AFKO-GSTRS - Scheduled start
DATETIME
24
0
9
yes
95
SPECL_PROCUREM
NT_TYPE_ID
AFPO.PSOBS -Special procurement type;
Domain SOBES
NVARCSTR
1
0
0
no
96
STORAGE_LOCATN_I
D
AFPO.LGORT - Storage location
NVARCSTR
4
0
0
yes
97
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
no
98
TECHN_COMPLT_FLA
G
Check table JEST for completed status
INTEGER
4
0
0
yes
99
UOM_ID
AFPO.MEINS - Base unit of measure
NVARCSTR
3
0
0
no
T001W.BWKEY Valuation area lookup
NVARCSTR
4
0
0
no
100 VALUATN_AREA_ID
Rapid Mart Data Schema
A
94
Appendix
Table Column Details
A
PROFIT_CENTER
CEPC - Profit Center attributes
Column Desc
Column
Datatype
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
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
7
DISTRICT
District
NVARCSTR
40
0
0
yes
8
FAX
Fax number
NVARCSTR
40
0
0
yes
9
LANG_ID
Language Key
NVARCSTR
1
0
0
yes
10
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
11
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
12
PERSON_IN_CHARGE
Person in charge of profit center
NVARCSTR
20
0
0
yes
13
PHONE
First telephone number
NVARCSTR
30
0
0
yes
14
PROFIT_CNTR_AREA
Profit center area
NVARCSTR
12
0
0
yes
15
PROFIT_CNTR_DESC
R
Name of Profit Center
NVARCSTR
40
0
0
yes
16
PROFIT_CNTR_FULL_
NAME
Profit Center Name and ID
NVARCSTR
120
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
95
Appendix
Table Column Details
17
PROFIT_CNTR_ID
18
PK
Profit center
NVARCSTR
10
0
0
no
PROFIT_CNTR_NAME
Profit Center Name
NVARCSTR
20
0
0
yes
19
PROFIT_CNTR_NAME
_01
Name 1
NVARCSTR
40
0
0
yes
20
PROFIT_CNTR_NAME
_02
Name 2
NVARCSTR
40
0
0
yes
21
PROFIT_CNTR_NAME
_03
Name 3
NVARCSTR
40
0
0
yes
22
PROFIT_CNTR_NAME
_04
Name 4
NVARCSTR
40
0
0
yes
23
REGION_ID
Abbreviation of Region (State)
NVARCSTR
3
0
0
yes
24
REGION_NAME
Name of Region (State)
NVARCSTR
20
0
0
yes
25
SEGMENT_DESCR
Segment Description
NVARCSTR
50
0
0
yes
26
SEGMENT_ID
Segment ID for Segmental Reporting
NVARCSTR
10
0
0
yes
27
STREET
House number and street
NVARCSTR
60
0
0
yes
28
VALID_FROM_DATE
Valid-from date
DATETIME
24
0
9
yes
29
VALID_TO_DATE
Valid to date
DATETIME
24
0
9
yes
30
ZIP
Postal Code
NVARCSTR
10
0
0
yes
Rapid Mart Data Schema
A
96
Appendix
Table Column Details
A
PROFIT_CENTER_HIER
CCSS-RPRCTR - Profit Center Hierarchy- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
Profit Center Child Node Description
NVARCSTR
64
0
0
yes
PK
Profit Center Child Node ID
NVARCSTR
10
0
0
no
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
4
0
0
no
4
LEAF_FLAG
PK
Node Is Leaf
NVARCSTR
1
0
0
no
5
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
6
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
97
Appendix
Table Column Details
A
PROFIT_CENTER_HIER_BAD
CCSS-RPRCTR - Profit Center Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
Child Description
NVARCSTR
64
0
0
yes
PK
Child
NVARCSTR
10
0
0
no
PK
Control Area ID
NVARCSTR
4
0
0
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
5
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
6
LEAF_FLAG
Leaf Flag
NVARCSTR
1
0
0
no
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
#
Column Name
1
CHILD_DESCR
2
CHILD_ID
3
CTRL_AREA_ID
4
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
98
Appendix
Table Column Details
A
PROFIT_CENTER_HIER_HZ
CCSS-RPRCTR - Profit Center hierarchy horizontally flattenned- cannot have primary key due to possible duplicate entries in SAP
#
Column Name
Key
Column Desc
Column
Datatype
1
CTRL_AREA_ID
PK
Controlling Area ID
NVARCSTR
4
0
0
no
2
LEAF_LVL
Current Node level depth
DECIMAL
48
10
0
no
3
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
4
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
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
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
Profit Center Level 1 node ID
NVARCSTR
10
0
0
no
11
LVL_02_DESCR
Profit Center Level 2 node Description
NVARCSTR
64
0
0
yes
12
LVL_02_FULL_NAME
Prifit Center ID and Descritption for Level 2
NVARCSTR
120
0
0
yes
13
LVL_02_ID
Profit Center Level 2 node ID
NVARCSTR
10
0
0
no
14
LVL_03_DESCR
Profit Center Level 3 node Description
NVARCSTR
64
0
0
yes
15
LVL_03_FULL_NAME
Profit Center Id and Description
NVARCSTR
120
0
0
yes
16
LVL_03_ID
Profit Center Level 3 node ID
NVARCSTR
10
0
0
no
PK
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
99
Appendix
Table Column Details
17
LVL_04_DESCR
Profit Center Level 4 node Description
NVARCSTR
64
0
0
yes
18
LVL_04_FULL_NAME
Priofit Center ID and Description for Level 4
NVARCSTR
120
0
0
yes
19
LVL_04_ID
Profit Center Level 4 node ID
NVARCSTR
10
0
0
no
20
LVL_05_DESCR
Profit Center Level 5 node Description
NVARCSTR
64
0
0
yes
21
LVL_05_FULL_NAME
Profit Center Id and Descritpion for Level 5
NVARCSTR
120
0
0
yes
22
LVL_05_ID
Profit Center Level 5 node ID
NVARCSTR
10
0
0
no
23
LVL_06_DESCR
Profit Center Level 6 node Description
NVARCSTR
64
0
0
yes
24
LVL_06_FULL_NAME
Profit Center Id and Descripiton for Level 6
NVARCSTR
120
0
0
yes
25
LVL_06_ID
Profit Center Level 6 node ID
NVARCSTR
10
0
0
no
26
LVL_07_DESCR
Profit Center Level 7 node Description
NVARCSTR
64
0
0
yes
27
LVL_07_FULL_NAME
Profit Center Id and Descritpion for level 7
NVARCSTR
120
0
0
yes
28
LVL_07_ID
Profit Center Level 7 node ID
NVARCSTR
10
0
0
no
29
LVL_08_DESCR
Profit Center Level 8 node Description
NVARCSTR
64
0
0
yes
30
LVL_08_FULL_NAME
Profit Center Id and Descritpion for level 8
NVARCSTR
120
0
0
yes
31
LVL_08_ID
Profit Center Level 8 node ID
NVARCSTR
10
0
0
no
32
LVL_09_DESCR
Profit Center Level 9 node Description
NVARCSTR
64
0
0
yes
33
LVL_09_FULL_NAME
Profit Center Id and Descritpion for Level 9
NVARCSTR
120
0
0
yes
34
LVL_09_ID
Profit Center Level 9 node ID
NVARCSTR
10
0
0
no
PK
PK
PK
PK
PK
PK
Rapid Mart Data Schema
A
100
Appendix
Table Column Details
35
LVL_10_DESCR
Profit Center Level 10 node Description
NVARCSTR
64
0
0
yes
36
LVL_10_FULL_NAME
Profit Center Id and Descritpion for Level 10
NVARCSTR
120
0
0
yes
37
LVL_10_ID
PK
Profit Center Level 10 node ID
NVARCSTR
10
0
0
no
38
PROFIT_CNTR_ID
PK
Profit Center ID
NVARCSTR
10
0
0
no
A
PROFIT_CENTER_HIER_VR
CCSS-RPRCTR Profit Center Hierarchy vertically flattenned- cannot have primary key due to possible duplicate entries in SAP
Column Desc
Column
Datatype
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
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
PARENT_DESCR
Parent Node Descritpion for Profit Center
NVARCSTR
64
0
0
yes
10
PARENT_FULL_NAME
Profit Center (Parent) ID and Descritpion
NVARCSTR
120
0
0
yes
11
PARENT_ID
Parent Node ID for Profit Center
NVARCSTR
10
0
0
no
12
ROOT_FLAG
Current Node is Root
INTEGER
4
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
101
Appendix
Table Column Details
A
PROGRESS_MEASURE_METHOD
Descriptive attributes for PS object progress measurement methods from EVOP
Key
Column
Datatype
Is
Nullable
Column Name
1
COLLAPSE_FLAG_AC
TL
EVOP.EVZSF - Indicator: Collapse subtree for INTEGER
Actuals only (1/0)
4
0
0
yes
2
COLLAPSE_FLAG_PL
AN
EVOP.EVZSF - Indicator: Collapse subtree for INTEGER
Budgeting only (Plan)
4
0
0
yes
3
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
4
LOAD_TIME
Time Loaded into Rapid mart
NVARCSTR
8
0
0
yes
5
MEASURE_METHOD
_DESCR_ACTL
EVMTT. BEZ40 - PS Progress Measurementh
method description lookup for Actuals only
NVARCSTR
40
0
0
yes
6
MEASURE_METHOD
_DESCR_PLAN
EVMTT. BEZ40 - PS Progress Measurementh
method description lookup for Budgeting only
(Plan)
NVARCSTR
40
0
0
yes
7
MEASURE_METHOD_I
D_ACTL
EVOP.EVMET - Measurement method in PS
progress analysis - for Actuals only
NVARCSTR
10
0
0
yes
8
MEASURE_METHOD_I
D_PLAN
EVOP.EVMET - Measurement method in PS
progress analysis - for Budgeting only (Plan)
NVARCSTR
10
0
0
yes
9
OBJ_ID
EVOP.OBJNR - Object number
NVARCSTR
22
0
0
no
10
OBJ_ID_REF_ACTL
EVOP.REFOB - Reference object for
secondary proportionality for Actuals only
NVARCSTR
22
0
0
yes
11
OBJ_ID_REF_PLAN
EVOP.REFOB - Reference object for
secondary proportionality for Budgeting only
(Plan)
NVARCSTR
22
0
0
yes
12
PROGRESS_VERSI
ON_DESCR
EVVST. TEXT - PS Progress Version
description (default Controlling Area)
NVARCSTR
40
0
0
yes
13
PROGRESS_VERSI
ON_FULL_NAME
EVOP.VERSN_EV - Progress Version
Code+EVOP.VERSN_EV - Progress Version
Code+EVVST. TEXT - PS Progress Version
description (default Controlling Area)
NVARCSTR
120
0
0
no
14
PROGRESS_VERSI
ON_ID
EVOP.VERSN_EV - Progress Version Code
NVARCSTR
3
0
0
yes
PK
PK
Column Desc
Dtype
Length Precision Scale
#
Rapid Mart Data Schema
102
Appendix
Table Column Details
A
PROJECT
PROJ- Project Master dimension
Column Desc
Column
Datatype
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
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
LOCATN_DESCR
Location Description
NVARCSTR
40
0
0
yes
10
LOCATN_ID
Location
NVARCSTR
10
0
0
yes
11
PLANNED_FINISH_DA
TE
Project planned finish date
DATETIME
24
0
9
yes
12
PLANNED_START_DA
TE
Project planned start date
DATETIME
24
0
9
yes
13
PROFILE_BDGT_ID
Budget profile
NVARCSTR
6
0
0
yes
14
PROFILE_DISTRIBTN_
DESCR
Distribution Profitle Description
NVARCSTR
40
0
0
yes
15
PROFILE_DISTRIBTN_
ID
Distribution profile
NVARCSTR
6
0
0
yes
16
PROFILE_INVESTMNT
_DESCR
Investment Profile Description
NVARCSTR
50
0
0
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
103
Appendix
Table Column Details
17
PROFILE_INVESTMNT
_ID
Investment measure profile
NVARCSTR
6
0
0
yes
18
PROFILE_NETWORK_
DESCR
Network Profile Description
NVARCSTR
40
0
0
yes
19
PROFILE_NETWORK_
ID
Network profile
NVARCSTR
7
0
0
yes
20
PROFILE_PAYMNT_P
LAN_ID
Payment plan profile
NVARCSTR
6
0
0
yes
21
PROFILE_PLANNG_ID
Planning profile
NVARCSTR
6
0
0
yes
22
PROFILE_PROJ_DES
CR
Project Profile Description
NVARCSTR
40
0
0
yes
23
PROFILE_PROJ_ID
Project profile
NVARCSTR
7
0
0
yes
24
PROFILE_SIMULTN_D
ESCR
Simulation Profile Description
NVARCSTR
40
0
0
yes
25
PROFILE_SIMULTN_I
D
Simulation profile
NVARCSTR
7
0
0
yes
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
PROJ.PSPID - Project ID (external)
NVARCSTR
24
0
0
no
30
RESP_PERSON_ID
Number of the responsible person (project
manager)
DECIMAL
48
28
0
yes
31
RESP_PERSON_NA
ME
Name of responsible person (Project manager) NVARCSTR
25
0
0
yes
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
PK
Rapid Mart Data Schema
A
104
Appendix
Table Column Details
A
PROJECT_COST_SUMMARY_FACT_HZ
Extracts data from the table RPSCO (cost and revenue summary for Projects) in horizontal period activity representation
Key
Column
Datatype
Column Desc
Dtype
Length Precision Scale
Is
Nullable
#
Column Name
1
AMT_CR_PER00_LOC
RPSCO.WLP00 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
2
AMT_CR_PER00_TRX
RPSCO.WTP00 - PTD Credit value in
transactional currency (Adjusting year begin
period)
DECIMAL
48
15
2
yes
3
AMT_CR_PER01_LOC
RPSCO.WLP01 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
4
AMT_CR_PER01_TRX
RPSCO.WTP01 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
5
AMT_CR_PER02_LOC
RPSCO.WLP02 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
6
AMT_CR_PER02_TRX
RPSCO.WTP02 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
7
AMT_CR_PER03_LOC
RPSCO.WLP03 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
8
AMT_CR_PER03_TRX
RPSCO.WTP03 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
9
AMT_CR_PER04_LOC
RPSCO.WLP04 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
10
AMT_CR_PER04_TRX
RPSCO.WTP04 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
11
AMT_CR_PER05_LOC
RPSCO.WLP05 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
12
AMT_CR_PER05_TRX
RPSCO.WTP05 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
13
AMT_CR_PER06_LOC
RPSCO.WLP06 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
14
AMT_CR_PER06_TRX
RPSCO.WTP06 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
15
AMT_CR_PER07_LOC
RPSCO.WLP07 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
16
AMT_CR_PER07_TRX
RPSCO.WTP07 - PTD Credit value in
transactional currency
48
15
2
yes
DECIMAL
Rapid Mart Data Schema
105
Appendix
Table Column Details
17
AMT_CR_PER08_LOC
RPSCO.WLP08 - PTD Credit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
18
AMT_CR_PER08_TRX
RPSCO.WTP08 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
19
AMT_CR_PER09_LOC
RPSCO.WLP09 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
20
AMT_CR_PER09_TRX
RPSCO.WTP09 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
21
AMT_CR_PER10_LOC
RPSCO.WLP10 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
22
AMT_CR_PER10_TRX
RPSCO.WTP10 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
23
AMT_CR_PER11_LOC
RPSCO.WLP11 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
24
AMT_CR_PER11_TRX
RPSCO.WTP11 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
25
AMT_CR_PER12_LOC
RPSCO.WLP12 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
26
AMT_CR_PER12_TRX
RPSCO.WTP12 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
27
AMT_CR_PER13_LOC
RPSCO.WLP13 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
28
AMT_CR_PER13_TRX
RPSCO.WTP13 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
29
AMT_CR_PER14_LOC
RPSCO.WLP14 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
30
AMT_CR_PER14_TRX
RPSCO.WTP14 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
31
AMT_CR_PER15_LOC
RPSCO.WLP15 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
32
AMT_CR_PER15_TRX
RPSCO.WTP15 - PTD Credit value in
transactional currency
DECIMAL
48
15
2
yes
33
AMT_CR_PER16_LOC
RPSCO.WLP16 - PTD Credit value in Ledger DECIMAL
(Local) currency (Adjusting Year begin period)
48
15
2
yes
34
AMT_CR_PER16_TRX
RPSCO.WTP169 - PTD Credit value in
transactional currency
48
15
2
yes
DECIMAL
Rapid Mart Data Schema
A
106
Appendix
Table Column Details
35
AMT_CR_QTR01_LOC
RPSCO.WLP00 through 03 - Quarter Credit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
36
AMT_CR_QTR01_TRX
RPSCO.WTP00 through 03 - Quarter Credit
value in transactional currency
DECIMAL
48
15
2
yes
37
AMT_CR_QTR02_LOC
RPSCO.WLP04 through 06 - Quarter Credit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
38
AMT_CR_QTR02_TRX
RPSCO.WTP04 through 06 - Quarter Credit
value in transactional currency
DECIMAL
48
15
2
yes
39
AMT_CR_QTR03_LOC
RPSCO.WLP07 through 09 - Quarter Credit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
40
AMT_CR_QTR03_TRX
RPSCO.WTP07 through 09 - Quarter Credit
value in transactional currency
DECIMAL
48
15
2
yes
41
AMT_CR_QTR04_LOC
RPSCO.WLP10 through 16 - Quarter Credit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
42
AMT_CR_QTR04_TRX
RPSCO.WTP10 through 16 - Quarter Credit
value in transactional currency
DECIMAL
48
15
2
yes
43
AMT_CR_YTD_LOC
RPSCO.WLP00 through 16 - Quarter Credit
value in Ledger (Local) currency
DECIMAL
48
15
2
yes
44
AMT_CR_YTD_TRX
RPSCO.WTP00 through 16 - Quarter Credit
value in transactional currency
DECIMAL
48
15
2
yes
45
AMT_DR_PER00_LOC
RPSCO.WLP00 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
46
AMT_DR_PER00_TRX
RPSCO.WTP00 - PTD Debit value in
transactional currency (Adjusting Year begin
period)
DECIMAL
48
15
2
yes
47
AMT_DR_PER01_LOC
RPSCO.WLP01 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
48
AMT_DR_PER01_TRX
RPSCO.WTP01 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
49
AMT_DR_PER02_LOC
RPSCO.WLP02 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
50
AMT_DR_PER02_TRX
RPSCO.WTP02 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
51
AMT_DR_PER03_LOC
RPSCO.WLP03 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
52
AMT_DR_PER03_TRX
RPSCO.WTP03 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
Rapid Mart Data Schema
A
107
Appendix
Table Column Details
53
AMT_DR_PER04_LOC
RPSCO.WLP04 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
54
AMT_DR_PER04_TRX
RPSCO.WTP04 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
55
AMT_DR_PER05_LOC
RPSCO.WLP05 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
56
AMT_DR_PER05_TRX
RPSCO.WTP05 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
57
AMT_DR_PER06_LOC
RPSCO.WLP06 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
58
AMT_DR_PER06_TRX
RPSCO.WTP06 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
59
AMT_DR_PER07_LOC
RPSCO.WLP07 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
60
AMT_DR_PER07_TRX
RPSCO.WTP07 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
61
AMT_DR_PER08_LOC
RPSCO.WLP08 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
62
AMT_DR_PER08_TRX
RPSCO.WTP08 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
63
AMT_DR_PER09_LOC
RPSCO.WLP09 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
64
AMT_DR_PER09_TRX
RPSCO.WTP09 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
65
AMT_DR_PER10_LOC
RPSCO.WLP10 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
66
AMT_DR_PER10_TRX
RPSCO.WTP10 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
67
AMT_DR_PER11_LOC
RPSCO.WLP11 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
68
AMT_DR_PER11_TRX
RPSCO.WTP11 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
69
AMT_DR_PER12_LOC
RPSCO.WLP12 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
70
AMT_DR_PER12_TRX
RPSCO.WTP12 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
Rapid Mart Data Schema
A
108
Appendix
Table Column Details
71
AMT_DR_PER13_LOC
RPSCO.WLP13 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
72
AMT_DR_PER13_TRX
RPSCO.WTP13 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
73
AMT_DR_PER14_LOC
RPSCO.WLP14 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
74
AMT_DR_PER14_TRX
RPSCO.WTP14 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
75
AMT_DR_PER15_LOC
RPSCO.WLP15 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
76
AMT_DR_PER15_TRX
RPSCO.WTP15 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
77
AMT_DR_PER16_LOC
RPSCO.WLP16 - PTD Debit value in Ledger
(Local) currency (Adjusting Year begin period)
DECIMAL
48
15
2
yes
78
AMT_DR_PER16_TRX
RPSCO.WTP16 - PTD Debit value in
transactional currency
DECIMAL
48
15
2
yes
79
AMT_DR_QTR01_LOC
RPSCO.WLP00 through 03 - Quarter Debit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
80
AMT_DR_QTR01_TRX
RPSCO.WTP00 through 03 - Quarter Debit
(QTD) value in transactional currency
DECIMAL
48
15
2
yes
81
AMT_DR_QTR02_LOC
RPSCO.WLP04 through 06 - Quarter Debit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
82
AMT_DR_QTR02_TRX
RPSCO.WTP04 through 06 - Quarter Debit
(QTD) value in transactional currency
DECIMAL
48
15
2
yes
83
AMT_DR_QTR03_LOC
RPSCO.WLP07 through 09 - Quarter Debit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
84
AMT_DR_QTR03_TRX
RPSCO.WTP07 through 09 - Quarter Debit
(QTD) value in transactional currency
DECIMAL
48
15
2
yes
85
AMT_DR_QTR04_LOC
RPSCO.WLP10 through 16 - Quarter Debit
(QTD) value in Ledger (Local) currency
DECIMAL
48
15
2
yes
86
AMT_DR_QTR04_TRX
RPSCO.WTP10 through 16 - Quarter Debit
(QTD) value in transactional currency
DECIMAL
48
15
2
yes
87
AMT_DR_YTD_LOC
RPSCO.WLP00 through 16 - Quarter Debit
value in Ledger (Local) currency
DECIMAL
48
15
2
yes
88
AMT_DR_YTD_TRX
RPSCO.WTP00 through 16 - Quarter Debit
value in transactional currency
DECIMAL
48
15
2
yes
Rapid Mart Data Schema
A
109
Appendix
Table Column Details
89
BUDGET_LEDGER_ID PK
RPSCO.LEDNR - Budget/Planning Ledger
NVARCSTR
4
0
0
no
90
BUS_ACTIVITY_ID
PK
RPSCO.VORGA - Budget Type Budgeting /
Planning
NVARCSTR
4
0
0
no
91
BUS_AREA_ID
PK
PRPS.PGSBR/AFVC.GSBER/PROJ.VBSBR
-Business area for WBS element/Proj/Network NVARCSTR
4
0
0
yes
92
CMPNY_CODE_ID
PK
PRPS.PBUKR/AFVC.BUKRS/PROJ.VBUKR -Company code for WBS element
NVARCSTR
4
0
0
yes
93
COST_OBJ_ID
PK
RPSCO.TRGLZ - Object indicator
NVARCSTR
10
0
0
no
94
CTRL_AREA_ID
PK
PRPS.PKOKR/PROJ.VKOKR -Controlling area NVARCSTR
for WBS element/Proj/Network
4
0
0
no
95
CURR_ID_LOC
PK
TBPOL.WAERS - Ledger Currency Key
(lookup)
NVARCSTR
5
0
0
yes
96
CURR_ID_TRX
PK
RPSCO.TWAER - Transaction Currency
NVARCSTR
5
0
0
no
97
DIM_SRC_ID_RECTYP PK
Dimension Source. Used in combined
dimension combining similar attributes from
different sources in SAP.
NVARCSTR
10
0
0
yes
98
FIN_MGMT_AREA_ID
PK
TPIF2.FIKRS - Financial (Fund) Management
Area ID (lookup)
NVARCSTR
4
0
0
yes
99
FISC_YEAR
PK
RPSCO. GJAHR - Fiscal Year
INTEGER
4
0
0
no
TBPOL.WAERS - Ledger Fiscal Year Variant
(lookup)
NVARCSTR
2
0
0
yes
100 FISC_YR_VARIANT_ID
101 FUNCTNL_AREA_ID
PK
AFVC/PROJ/PRPS.FUNC_AREA -Functional
Area ID
NVARCSTR
16
0
0
yes
102 FUND_ID
PK
RPSCO.GEBER - Fund
NVARCSTR
10
0
0
no
103 LOAD_DATE
Date and Time This row was loaded into the
Rapid Mart
DATETIME
24
0
9
yes
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
Rapid Mart Data Schema
A
110
Appendix
Table Column Details
107 OBJ_NUM_TYPE_ID
PK
RPSCO.OBJNR Object number first 2
characters
NVARCSTR
2
0
0
yes
108 OPERATN_ROUTING_
PK
ID
AFVC.AUFPL -Routing number of operations in NVARCSTR
the order
10
0
0
yes
109 OPERATN_SEQ_ID
PK
AFVC.APLZL -General counter for order
8
0
0
yes
110 PARTITION_YEAR
PK
Duplicate of Fisc. Year column to allow for
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
113 PROJ_ELEM_ID
PK
AFVC/PRPS.PROJN -Work breakdown
structure element (WBS element) / Lookup on
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
114 PROJ_ID
PK
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
115 PURCH_ORG_ID
PK
T001W.EKORG Purchasing organization
(lookup)
NVARCSTR
4
0
0
yes
116 RECORD_CATEG_ID
PK
RPSCO.ACPOS - Value category
NVARCSTR
14
0
0
no
117 RECORD_TYPE_ID
PK
Financial Record Type ID
NVARCSTR
10
0
0
no
118 SURROGATE_DOC_ID PK
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
119 VALUATN_AREA_ID
T001W.BWKEY Valuation Area Key lookup
NVARCSTR
4
0
0
yes
RPSCO..ABKAT - Category for
Variance/Results Analysis
NVARCSTR
10
0
0
no
PK
120 VARIANCE_CATEG_ID PK
NVARCSTR
Rapid Mart Data Schema
A
111
Appendix
Table Column Details
A
PROJECT_COST_SUMMARY_FACT_VR
Computes Rolling Totals for ProjectCost Summary Vertical Fact (Sourced from RPSCO)
Column Desc
Column
Datatype
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 P
DECIMAL
48
15
2
yes
2
AMT_CR_QTD_LOC
RPSCO-WLP01 through WLP16 through 16 QTD Credit value in Ledger (Local) currency
DECIMAL
48
15
2
yes
3
AMT_CR_QTD_TRX
RPSCO-WTP01 through WTP16 through 16 QTD Credit value in Transactional currency
DECIMAL
48
15
2
yes
4
AMT_CR_TRX
RPSCO-WTP01 through WTP16 - Period
Credit value in Transactional currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Pe
DECIMAL
48
15
2
yes
5
AMT_CR_YTD_LOC
RPSCO-WLP01 through WLP16 - YTD Credit DECIMAL
value in Ledger (Local) currency
48
15
2
yes
6
AMT_CR_YTD_TRX
RPSCO-WTP01 through WTP16 - YTD Credit DECIMAL
value in Transactional currency
48
15
2
yes
7
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 Pe
DECIMAL
48
15
2
yes
8
AMT_DR_QTD_LOC
RPSCO-WLP01 through WLP16 - QTD Debit
value in Ledger (Local) currency
DECIMAL
48
15
2
yes
9
AMT_DR_QTD_TRX
RPSCO-WTP01 through WTP16 - QTD Debit
value in Transacitonal currency
DECIMAL
48
15
2
yes
10
AMT_DR_TRX
RPSCO-WTP01 through WTP16 - Period
Debit value in Transactional currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Per
DECIMAL
48
15
2
yes
11
AMT_DR_YTD_LOC
RPSCO-WLP01 through WLP16 - YTD Debit
value in Ledger (Local) currency
DECIMAL
48
15
2
yes
12
AMT_DR_YTD_TRX
RPSCO-WTP01 through WTP16 - YTD Debit
value in Transactional currency
DECIMAL
48
15
2
yes
13
AMT_PER_BEGIN_LO
C
RPSCO-WLP01 through WLP16 - Period
begin balance value in Ledger (Local) currency DECIMAL
48
17
2
yes
14
AMT_PER_BEGIN_TR
X
RPSCO-WTP01 through WTP16 - Period
begin balance value in Transacitonal currency
DECIMAL
48
17
2
yes
15
AMT_PER_ROLLING_
LOC
Rolling Total Balance - Ledger (Local)
Currency
DECIMAL
48
17
2
yes
16
AMT_PER_ROLLING_
TRX
Rolling Total Balance - Transaction Currency
DECIMAL
48
17
2
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
112
Appendix
Table Column Details
17
AMT_PTD_LOC
Period Begining Balance - Ledger (Local)
Currency
DECIMAL
48
17
2
yes
18
AMT_PTD_TRX
Period Begining Balance - Transaction
Currency
DECIMAL
48
17
2
yes
19
BUDGET_LEDGER_ID PK
RPSCO.LEDNR - Budget/Planning Ledger
NVARCSTR
4
0
0
no
20
BUS_ACTIVITY_ID
PK
RPSCO.VORGA - Budget Type Budgeting /
Planning
NVARCSTR
4
0
0
no
21
BUS_AREA_ID
PK
PRPS.PGSBR/AFVC.GSBER/PROJ.VBSBR
-Business area for WBS element/Proj/Network NVARCSTR
4
0
0
yes
22
CMPNY_CODE_ID
PK
PRPS.PBUKR/AFVC.BUKRS/PROJ.VBUKR -Company code for WBS element
NVARCSTR
4
0
0
yes
23
COST_OBJ_ID
PK
RPSCO.TRGLZ - Object indicator
NVARCSTR
10
0
0
no
24
CTRL_AREA_ID
PK
PRPS.PKOKR/PROJ.VKOKR -Controlling area NVARCSTR
for WBS element/Proj/Network
4
0
0
yes
25
CURR_ID_LOC
PK
TBPOL.WAERS - Ledger Currency Key
(lookup)
NVARCSTR
5
0
0
yes
26
CURR_ID_TRX
PK
RPSCO.TWAER - Transaction Currency
NVARCSTR
5
0
0
no
27
DIM_SRC_ID_RECTYP PK
Dimension Source. Used in combined
dimension combining similar attributes from
different sources in SAP.
NVARCSTR
10
0
0
yes
28
FIN_MGMT_AREA_ID
PK
TPIF2.FIKRS - Financial (Fund) Management
Area ID (lookup)
NVARCSTR
4
0
0
yes
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
TBPOL.WAERS - Ledger Fiscal Year Variant
(lookup)
NVARCSTR
2
0
0
yes
32
FUNCTNL_AREA_ID
PK
AFVC/PROJ/PRPS.FUNC_AREA -Functional
Area ID
NVARCSTR
16
0
0
yes
33
FUND_ID
PK
RPSCO.GEBER - Fund
NVARCSTR
10
0
0
no
34
LOAD_DATE
Date and Time This row was loaded into the
Rapid Mart
DATETIME
24
0
9
yes
Rapid Mart Data Schema
A
113
Appendix
Table Column Details
35
LOAD_TIME
Time This row was loaded into the Rapid Mart
NVARCSTR
8
0
0
yes
36
OBJ_ID
PK
RPSCO-OBJNR - Object number
NVARCSTR
22
0
0
no
37
OBJ_NUM_TYPE_ID
PK
RPSCO.OBJNR Object number first 2
characters
NVARCSTR
2
0
0
yes
38
OPERATN_ROUTING_ PK
ID
AFVC.AUFPL -Routing number of operations in NVARCSTR
the order
10
0
0
yes
39
OPERATN_SEQ_ID
PK
AFVC.APLZL -General counter for order
NVARCSTR
8
0
0
yes
40
PARTITION_YEAR
PK
For Partitioning only: RPSCO.GJAHR - Fiscal
Year
INTEGER
4
0
0
yes
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
AFVC/PRPS.PROJN -Work breakdown
structure element (WBS element) / Lookup on
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
44
PROJ_ID
PK
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
45
PURCH_ORG_ID
PK
T001W.EKORG Purchasing organization
(lookup)
NVARCSTR
4
0
0
yes
46
RECORD_CATEG_ID
PK
RPSCO.ACPOS - Value category
NVARCSTR
14
0
0
no
47
RECORD_TYPE_ID
PK
Financial Record Type ID
NVARCSTR
10
0
0
no
48
SUMMARY_KEY
Concatenation ofr Primary Key for use in
ordering query.
NVARCSTR
150
0
0
yes
49
SURROGATE_DOC_ID PK
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
50
VALUATN_AREA_ID
T001W.BWKEY Valuation Area Key lookup
NVARCSTR
4
0
0
yes
51
VARIANCE_CATEG_ID PK
RPSCO..ABKAT - Category for
Variance/Results Analysis
NVARCSTR
10
0
0
no
Rapid Mart Data Schema
A
114
Appendix
Table Column Details
A
PROJECT_COST_SUMMARY_STAGE_VR
Vertical representation of Project Cost period activity. Staging is used for further Rolling Summary calculation
Column Desc
Column
Datatype
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 P
DECIMAL
48
15
2
yes
2
AMT_CR_QTD_LOC
RPSCO-WLP01 through 16 - QTD Credit
value in Ledger (Local) currency
DECIMAL
48
15
2
yes
3
AMT_CR_QTD_TRX
RPSCO-WTP01 through 16 - QTD Credit
value in Transactional currency
DECIMAL
48
15
2
yes
4
AMT_CR_TRX
RPSCO-WTP01 through WTP16 - Period
Credit value in Transactional currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Pe
DECIMAL
48
15
2
yes
5
AMT_CR_YTD_LOC
RPSCO-WLP01 through WLP16 - YTD Credit DECIMAL
value in Ledger (Local) currency
48
15
2
yes
6
AMT_CR_YTD_TRX
RPSCO-WTP01 through WTP16 - YTD Credit DECIMAL
value in Transcactional currency
48
15
2
yes
7
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 P
DECIMAL
48
15
2
yes
8
AMT_DR_QTD_LOC
RPSCO-WLP01 through 16 - QTD Debit value DECIMAL
in Ledger (Local) currency
48
15
2
yes
9
AMT_DR_QTD_TRX
RPSCO-WTP01 through 16 - QTD Debit value DECIMAL
in Transactioal currency
48
15
2
yes
10
AMT_DR_TRX
RPSCO-WTP01 through WTP16 - Period
Debit value in Transactional currency. For
Period 01 - cumulative of Per 00 and Per 01;
for Per 12 - cumulative of Per 12 through Per
DECIMAL
48
15
2
yes
11
AMT_DR_YTD_LOC
RPSCO-WLP01 through 16 - YTD Debit value DECIMAL
in Ledger (Local) currency
48
15
2
yes
12
AMT_DR_YTD_TRX
RPSCO-WTP01 through 16 - YTD Debit value DECIMAL
in Transactional currency
48
15
2
yes
13
AMT_PER_BEGIN_LO
C
RPSCO-WLP01 through 16 - Period begin
balance value in Transactional Ledger (Local) DECIMAL
48
17
2
yes
14
AMT_PER_BEGIN_TR
X
RPSCO-WTP01 through 16 - Period begin
balance value in Transactional currency
DECIMAL
48
17
2
yes
15
BUDGET_LEDGER_ID PK
RPSCO.LEDNR - Budget/Planning Ledger
NVARCSTR
4
0
0
no
16
BUS_ACTIVITY_ID
RPSCO.VORGA - Budget Type Budgeting /
Planning
NVARCSTR
4
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
115
Appendix
Table Column Details
17
BUS_AREA_ID
PRPS.PGSBR/AFVC.GSBER/PROJ.VBSBR
-Business area for WBS element/Proj/Network NVARCSTR
4
0
0
yes
18
CMPNY_CODE_ID
PRPS.PBUKR/AFVC.BUKRS/PROJ.VBUKR -Company code for WBS element
NVARCSTR
4
0
0
yes
19
COST_OBJ_ID
RPSCO.TRGLZ - Object indicator
NVARCSTR
1
0
0
no
20
CTRL_AREA_ID
PRPS.PKOKR/PROJ.VKOKR -Controlling area NVARCSTR
for WBS element/Proj/Network
4
0
0
yes
21
CURR_ID_LOC
TBPOL.WAERS - Ledger Currency Key
(lookup)
NVARCSTR
5
0
0
yes
22
CURR_ID_TRX
RPSCO.TWAER - Transaction Currency
NVARCSTR
5
0
0
no
23
FIN_MGMT_AREA_ID
TPIF2.FIKRS - Financial (Fund) Management
Area ID (lookup)
NVARCSTR
4
0
0
yes
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
TBPOL.WAERS - Ledger Fiscal Year Variant
(lookup)
NVARCSTR
2
0
0
yes
27
FUNCTNL_AREA_ID
AFVC/PROJ/PRPS.FUNC_AREA -Functional
Area ID
NVARCSTR
16
0
0
yes
28
FUND_ID
RPSCO.GEBER - Fund
NVARCSTR
10
0
0
no
29
LOAD_DATE
Date and Time This row was loaded into the
Rapid Mart
DATETIME
24
0
9
yes
30
LOAD_TIME
Time This row was loaded into the Rapid Mart
NVARCSTR
8
0
0
yes
31
OBJ_ID
RPSCO. OBJNR - Object number
NVARCSTR
22
0
0
no
32
OBJ_NUM_TYPE_ID
RPSCO.OBJNR Object number first 2
characters
NVARCSTR
2
0
0
yes
33
OPERATN_ROUTING_
ID
AFVC.AUFPL -Routing number of operations in NVARCSTR
the order
10
0
0
yes
34
OPERATN_SEQ_ID
AFVC.APLZL -General counter for order
8
0
0
yes
PK
PK
PK
PK
NVARCSTR
Rapid Mart Data Schema
A
116
Appendix
Table Column Details
Duplicate of Fisc. Year column to allow for
Table partition on a field not in the Primary Key INTEGER
4
0
0
yes
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
38
PROJ_ELEM_ID
AFVC/PRPS.PROJN -Work breakdown
structure element (WBS element) / Lookup on
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
39
PROJ_ID
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
40
PURCH_ORG_ID
T001W.EKORG Purchasing organization
(lookup)
NVARCSTR
4
0
0
yes
41
RECORD_CATEG_ID
PK
RPSCO.ACPOS - Value category
NVARCSTR
14
0
0
no
42
RECORD_TYPE_ID
PK
RPSCO. WRTTP - Value Type
NVARCSTR
2
0
0
no
43
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
44
VALUATN_AREA_ID
T001W.BWKEY Valuation Area Key lookup
NVARCSTR
4
0
0
yes
45
VARIANCE_CATEG_ID PK
RPSCO..ABKAT - Category for
Variance/Results Analysis
NVARCSTR
2
0
0
no
35
PARTITION_YEAR
36
PK
Rapid Mart Data Schema
A
117
Appendix
Table Column Details
A
PROJECT_ELEMENT
PRPS, PRTE - Project Element Master dimension
Column Desc
Column
Datatype
ACTL_DURTN
Actual length (duration) of the WBS element
DECIMAL
48
5
1
yes
2
ACTL_FINISH_DATE
Actual finish date of the WBS element
DATETIME
24
0
9
yes
3
ACTL_START_DATE
Actual start date for the WBS element
DATETIME
24
0
9
yes
4
APPLICANT_ID
Applicant number
DECIMAL
48
28
0
yes
5
APPLICANT_NAME
Applicant
NVARCSTR
25
0
0
yes
6
BASIC_DURTN
Length (duration) of the basic dates in the WBS DECIMAL
element
48
5
1
yes
7
BASIC_FINISH_DATE
WBS element: Basic finish date
DATETIME
24
0
9
yes
8
BASIC_SCHED_EARL
ST_FINISH_DATE
Earliest scheduled finish date (basic)
DATETIME
24
0
9
yes
9
BASIC_SCHED_EARL
ST_START_DATE
Earliest scheduled start date (Basic)
DATETIME
24
0
9
yes
10
BASIC_SCHED_LATE
ST_FINISH_DATE
Latest scheduled finish date (basic)
DATETIME
24
0
9
yes
11
BASIC_SCHED_LATE
ST_START_DATE
Latest scheduled start date (basic)
DATETIME
24
0
9
yes
12
BASIC_START_DATE
WBS element: Basic start date
DATETIME
24
0
9
yes
13
CREATED_BY
Name of Person who Created the Object
NVARCSTR
12
0
0
yes
14
CREATE_DATE
Date on which the record was created
DATETIME
24
0
9
yes
15
DELETE_FLAG
Deletion indicator
NVARCSTR
1
0
0
yes
16
FCST_DURTN
Forecasted length (duration) of the WBS
element
DECIMAL
48
5
1
yes
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
118
Appendix
Table Column Details
17
FCST_FINISH_DATE
Forecasted finish date of the WBS element
DATETIME
24
0
9
yes
18
FCST_SCHED_EARLS
T_FINISH_DATE
Earliest scheduled finish date (forecast)
DATETIME
24
0
9
yes
19
FCST_SCHED_LATES
T_FINISH_DATE
Latest scheduled finish date (Forecast)
DATETIME
24
0
9
yes
20
FCST_SCHED_LATES
T_START_DATE
Latest scheduled start date (forecast)
DATETIME
24
0
9
yes
21
FCST_SCHED_START
_DATE
Scheduled start date (Forecast)
DATETIME
24
0
9
yes
22
FCST_START_DATE
Forecasted start date of the WBS element
DATETIME
24
0
9
yes
23
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
24
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
25
MILESTONE_FLAG
Indicator: WBS element used in project
summarization
NVARCSTR
1
0
0
yes
26
PRIORITY_FLAG
Priority
NVARCSTR
1
0
0
yes
27
PROJ_ELEM_CODE
PRPS.PSPNR - WBS element Internal ID
DECIMAL
48
28
0
yes
28
PROJ_ELEM_DESCR
PRPS.POST1 - WBS element (Project
Element) Description
NVARCSTR
40
0
0
yes
29
PROJ_ELEM_FULL_N
AME
PRPS.POSID and PRPS.POST1 Project
Element ID and Project Element Description
NVARCSTR
100
0
0
yes
30
PROJ_ELEM_ID
PRPS.POSID - WBS element External ID
NVARCSTR
24
0
0
no
31
PROJ_ELEM_SHORT_
ID
PRPS.POSKI - WBS element short External ID NVARCSTR
16
0
0
yes
32
PROJ_ID
PROJ.PSPID - (Lookup on PROJ) Project ID
(external)
NVARCSTR
24
0
0
yes
33
PROJ_NAME
PROJ.POST1 - PS: Short description (1st text
line) -- Lookup on PROJ
NVARCSTR
40
0
0
yes
34
RESP_PERSON
Name of responsible person (Project manager) NVARCSTR
25
0
0
yes
PK
Rapid Mart Data Schema
A
119
Appendix
Table Column Details
35
RESP_PERSON_ID
Number of the responsible person (project
manager)
DECIMAL
48
28
0
yes
36
TNTV_FINISH_DATE
Tentative actual finish date for WBS element
DATETIME
24
0
9
yes
37
TNTV_START_DATE
Tentative actual start date for WBS element
DATETIME
24
0
9
yes
38
UOM_ID_ACTL_DURT
N
Unit for duration of actual WBS element dates
NVARCSTR
3
0
0
yes
39
UOM_ID_BASIC_DUR
TN
Unit for duration of basic WBS element dates
NVARCSTR
3
0
0
yes
40
UOM_ID_FCST_DURT
N
Unit for duration of WBS element planned
dates
NVARCSTR
3
0
0
yes
A
PROJECT_ELEMENT_HIER
PRHI - Project Element Hierarchy dimension
Column Desc
Column
Datatype
CHILD_CODE
PRPS.POSID - WBS element Internal ID Project Element Child Node ID
INTEGER
2
CHILD_DESCR
Project Element Child Node Description
3
CHILD_FULL_NAME
4
CHILD_ID
5
LOAD_DATE
6
#
Column Name
1
Key
Dtype
Length Precision Scale
Is
Nullable
4
0
0
no
NVARCSTR
100
0
0
yes
Project Element Child Node ID and Description NVARCSTR
100
0
0
yes
PRPS.POSID - WBS element External ID Project Element Child Node ID
24
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
7
PARENT_CODE
PRPS.POSID - WBS element Internal ID Project Element Parent Node ID
INTEGER
4
0
0
no
8
PARENT_DESCR
Project Element Parent Node Description
NVARCSTR
100
0
0
yes
9
PARENT_FULL_NAME
Project Element Parent Node ID Description
NVARCSTR
100
0
0
yes
10
PARENT_ID
PRPS.POSID - WBS element External ID Project Element Parent Node ID
NVARCSTR
24
0
0
no
PK
PK
NVARCSTR
Rapid Mart Data Schema
120
Appendix
Table Column Details
A
PROJECT_ELEMENT_HIER_BAD
Rejected Project Element Hierarchy records
Column Desc
Column
Datatype
CHILD_CODE
PRPS.POSID - WBS element Internal ID Project Element Child Node ID
INTEGER
2
CHILD_DESCR
Project Element Child Node Description
3
CHILD_FULL_NAME
4
CHILD_ID
5
#
Column Name
1
Key
Dtype
Length Precision Scale
Is
Nullable
4
0
0
no
NVARCSTR
100
0
0
yes
Project Element Child Node ID and Description NVARCSTR
100
0
0
yes
PRPS.POSID - WBS element External ID Project Element Child Node ID
NVARCSTR
24
0
0
no
ETL_ERROR_ACTN
Data Integrator Action on Error
NVARCSTR
1
0
0
yes
6
ETL_ERROR_COLU
MN
Data Integrator Error message
NVARCSTR
500
0
0
yes
7
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
8
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
9
PARENT_CODE
PRPS.POSID - WBS element Internal ID Project Element Parent Node ID
INTEGER
4
0
0
yes
10
PARENT_DESCR
Project Element Parent Node Description
NVARCSTR
100
0
0
yes
11
PARENT_FULL_NAME
Project Element Parent Node ID and
Description
NVARCSTR
100
0
0
yes
12
PARENT_ID
PRPS.POSID - WBS element External ID Project Element Parent Node ID
NVARCSTR
24
0
0
no
PK
PK
Rapid Mart Data Schema
121
Appendix
Table Column Details
A
PROJECT_ELEMENT_HIER_HZ
PRHI - Project element hierarchy flattenned horizontally
Column Desc
Column
Datatype
LEAF_LVL
Current Node level depth
INTEGER
2
LOAD_DATE
3
#
Column Name
1
Key
Dtype
Length Precision Scale
Is
Nullable
4
0
0
yes
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
4
LVL_00_DESCR
Project Element Root Node Description
NVARCSTR
100
0
0
yes
5
LVL_00_FULL_NAME
Project Element Root Level ID and Node
Description
NVARCSTR
100
0
0
yes
6
LVL_00_ID
Project Element Root Node ID
NVARCSTR
24
0
0
no
7
LVL_01_DESCR
Project Element Level 1 Node Description
NVARCSTR
100
0
0
yes
8
LVL_01_FULL_NAME
Project Element Level 1 Level ID and Node
Description
NVARCSTR
100
0
0
yes
9
LVL_01_ID
Project Element Level 1 Node ID
NVARCSTR
24
0
0
no
10
LVL_02_DESCR
Project Element Level 2 Node Description
NVARCSTR
100
0
0
yes
11
LVL_02_FULL_NAME
Project Element Level 2 Level ID and Node
Description
NVARCSTR
100
0
0
yes
12
LVL_02_ID
Project Element Level 2 Node ID
NVARCSTR
24
0
0
no
13
LVL_03_DESCR
Project Element Level 3 Node Description
NVARCSTR
100
0
0
yes
14
LVL_03_FULL_NAME
Project Element Level 3 Level ID and Node
Description
NVARCSTR
100
0
0
yes
15
LVL_03_ID
Project Element Level 3 Node ID
NVARCSTR
24
0
0
no
16
LVL_04_DESCR
Project Element Level 4 Node Description
NVARCSTR
100
0
0
yes
PK
PK
PK
PK
Rapid Mart Data Schema
122
Appendix
Table Column Details
Project Element Level 4 Level ID and Node
Description
NVARCSTR
100
0
0
yes
Project Element Level 4 Node ID
NVARCSTR
24
0
0
no
LVL_05_DESCR
Project Element Level 5 Node Description
NVARCSTR
100
0
0
yes
20
LVL_05_FULL_NAME
Project Element Level 5 Level ID and Node
Description
NVARCSTR
100
0
0
yes
21
LVL_05_ID
Project Element Level 5 Node ID
NVARCSTR
24
0
0
no
22
LVL_06_DESCR
Project Element Level 6 Node Description
NVARCSTR
100
0
0
yes
23
LVL_06_FULL_NAME
Project Element Level 6 Level ID and Node
Description
NVARCSTR
100
0
0
yes
24
LVL_06_ID
Project Element Level 6 Node ID
NVARCSTR
24
0
0
no
25
LVL_07_DESCR
Project Element Level 7 Node Description
NVARCSTR
100
0
0
yes
26
LVL_07_FULL_NAME
Project Element Level 7 Level ID and Node
Description
NVARCSTR
100
0
0
yes
27
LVL_07_ID
Project Element Level 7 Node ID
NVARCSTR
24
0
0
no
28
LVL_08_DESCR
Project Element Level 8 Node Description
NVARCSTR
100
0
0
yes
29
LVL_08_FULL_NAME
Project Element Level 8 Level ID and Node
Description
NVARCSTR
100
0
0
yes
30
LVL_08_ID
Project Element Level 8 Node ID
NVARCSTR
24
0
0
no
31
LVL_09_DESCR
Project Element Level 9 Node Description
NVARCSTR
100
0
0
yes
32
LVL_09_FULL_NAME
Project Element Level 9 Level ID and Node
Description
NVARCSTR
100
0
0
yes
33
LVL_09_ID
Project Element Level 9 Node ID
NVARCSTR
24
0
0
no
34
LVL_10_DESCR
Project Element Level 10 Node Description
NVARCSTR
100
0
0
yes
17
LVL_04_FULL_NAME
18
LVL_04_ID
19
PK
PK
PK
PK
PK
PK
Rapid Mart Data Schema
A
123
Appendix
Table Column Details
35
LVL_10_FULL_NAME
36
LVL_10_ID
37
PROJ_ELEM_ID
Project Element Level 10 Level ID and Node
Description
NVARCSTR
100
0
0
yes
PK
Project Element Level 10 Node ID
NVARCSTR
24
0
0
no
PK
Project Element Current Node ID
NVARCSTR
24
0
0
no
A
PROJECT_ELEMENT_HIER_VR
PRHI - Project Element Hierarchy vertically flattenned
Column Desc
Column
Datatype
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
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
6
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
8
PARENT_DESCR
Child Node Desc
NVARCSTR
100
0
0
yes
9
PARENT_FULL_NAME
Child Node ID and Desc
NVARCSTR
100
0
0
yes
10
PARENT_ID
Child Node ID
NVARCSTR
24
0
0
no
11
ROOT_FLAG
Is Root
INTEGER
4
0
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
124
Appendix
Table Column Details
A
PRT_ASSIGNMENT_FACT
Production resource (tool) assignment details from AFFH/CRFH/AFVC
Column Desc
Column
Datatype
ACTIVITY_ID
AFVC.LARNT - Activity Type
NVARCSTR
6
0
0
yes
2
ACTL_END_DATE
AFFH.IEFHD - Actual finish (date) of PRT
usage+AFFH.IEFHZ - Actual finish (time) of
PRT usage
DATETIME
24
0
9
yes
3
ACTL_START_DATE
AFFH.ISFHD - Actual start (date) of PRT
usage+AFFH.ISFHZ - Actual start (time) of
PRT usage
DATETIME
24
0
9
yes
4
ACTL_USG_VALUE
AFFH.EWIST - Actual usage value for
production resource/tool
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
7
CHART_OF_ACCT_ID
T001.KTOPL-Chart of accts ID - Lookup
NVARCSTR
4
0
0
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
13
DATE_KEY_ID_END
AFFH.BZOFFE - Reference date for end of
production resource/tool usage
NVARCSTR
2
0
0
yes
14
DATE_KEY_ID_START
AFFH.BZOFFB - Reference date to start of
production resource/tool usage
NVARCSTR
10
0
0
yes
15
DAYS_DURTN_ACTL
48
22
7
yes
16
DAYS_DURTN_EARLS
T
48
22
7
yes
#
Column Name
1
Key
Actual Number of Days for Network
Relationship. Calculated as difference between DECIMAL
actual end date and start date(UOM_ID = TAG
in IDES)
Number of Days for Network Relationship
based on Eraliest start/end dates(UOM_ID =
DECIMAL
TAG in IDES)
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
125
Appendix
Table Column Details
17
DAYS_DURTN_LATES
T
18
DAYS_DURTN_MAX
19
DAYS_DURTN_MIN
20
DELETE_FLAG
21
DIM_SRC_ID_DTKEY
22
DIM_SRC_ID_OBJTYP
23
FORMULA_ID_PRT_Q
TY
24
Number of Days for Network Relationship
based on Latest start/end dates(UOM_ID =
DECIMAL
TAG in IDES)
Max Number of Days for Network Relationship.
Calculated as difference between latest end
date and earliest start date(UOM_ID = TAG in DECIMAL
IDES)
Min Number of Days for Network Relationship.
Calculated as difference between earliest end DECIMAL
date and latest start date(UOM_ID = TAG in
IDES)
48
22
7
yes
48
22
7
yes
48
22
7
yes
INTEGER
4
0
0
yes
NVARCSTR
10
0
0
yes
NVARCSTR
10
0
0
yes
AFFH.MGFORM - Formula for calculating the
total quantity of PRT
NVARCSTR
6
0
0
yes
FORMULA_ID_PRT_U
SG
AFFH.EWFORM - Formula for calculating the
total usage value of PRT
NVARCSTR
6
0
0
yes
25
FUNCTNL_AREA_ID
AFVC/AUFK.FUNC_AREA -Functional Area
NVARCSTR
16
0
0
yes
26
GROUPNG_KEY_ID_0
1
CRFH.FGRU1 - Grouping key 1 for production NVARCSTR
resources/tools
4
0
0
yes
27
GROUPNG_KEY_ID_0
2
CRFH.FGRU2 -Grouping key 2 for production
resources/tools
NVARCSTR
4
0
0
yes
28
GROUP_ID
AFVC.PLNNR - Key for Task List Group
NVARCSTR
8
0
0
yes
29
GROUP_LINE_ID
AFVC.PLNFL - Sequence of
operations/activities
NVARCSTR
6
0
0
yes
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
32
HOURS_DURTN_AC
TL
48
22
7
yes
33
HOURS_DURTN_EA
RLST
Actual Number of HOURS for Network
Relationship. Calculated as difference between DECIMAL
actual end date and start date(UOM_ID = HUR
in IDES)
Number of Hours for Network Relationship
based on Eraliest start/end dates(UOM_ID =
DECIMAL
HUR in IDES)
48
22
7
yes
34
HOURS_DURTN_LA
TEST
Number of HOURS for Network Relationship
based on Latest start/end dates(UOM_ID =
HUR in IDES)
48
22
7
yes
AFFH.LOEKZ - Deletion indicator (1/0)
Dimension Source. This is a combined
dimension combining different varieties of
"Reference Date Key" from different sources.
This field identifies the source of "Referere
Dimension Source. This is a combined
dimension combining different varieties of
"object type" from different sources. This field
identifies the source of "object type"
DECIMAL
Rapid Mart Data Schema
A
126
Appendix
Table Column Details
35
HOURS_DURTN_MAX
36
HOURS_DURTN_MIN
37
INTERNAL_ORDER_ID
Max Number of Hours for Network
Relationship. Calculated as difference between DECIMAL
latest end date and earliest start date(UOM_ID
= HUR in IDES)
Min Number of Hours for Network Relationship.
Calculated as difference between earliest end DECIMAL
date and latest start date(UOM_ID = HUR in
IDES)
AUFK-AUFNR
48
22
7
yes
48
22
7
yes
NVARCSTR
12
0
0
yes
NVARCSTR
4
0
0
yes
NVARCSTR
8
0
0
yes
38
ITEM_NUM
39
ITEM_SEQ_ID
AFFH.PSNFH - Item number for production
resource/tool. Number that specifies the
sequence in which the production
resources/tools allocated to the operation or
activity a
AFFH.PZLFH_KEY - Item counter for
production resources/tools
40
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
41
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
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
44
MINS_DURTN_ACTL
48
22
7
yes
45
MINS_DURTN_EARLS
T
48
22
7
yes
46
MINS_DURTN_LATES
T
48
22
7
yes
47
MINS_DURTN_MAX
48
22
7
yes
48
MINS_DURTN_MIN
48
22
7
yes
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
52
OBJ_TYPE_ID
AFFH.OBJCT - Object of a task list (domain
OBJKT)
10
0
0
yes
Actual Number of Mins for Network
Relationship. Calculated as difference between DECIMAL
actual end date and start date (UOM_ID = MIN
in IDES)
Number of Mins for Network Relationship
based on Eraliest start/end dates(UOM_ID =
DECIMAL
MIN in IDES)
Number of Mins for Network Relationship
based on Latest start/end dates(UOM_ID =
DECIMAL
MIN in IDES)
Max Number of Mins for Network Relationship.
Calculated as difference between latest end
date and earliest start date(UOM_ID = MIN in DECIMAL
IDES)
Min Number of Mins for Network Relationship.
Calculated as difference between earliest end DECIMAL
date and latest start date(UOM_ID = MIN in
IDES)
NVARCSTR
Rapid Mart Data Schema
A
127
Appendix
Table Column Details
53
OPERATN_NUM
AFVC.VORNR - Activity Number
NVARCSTR
4
0
0
yes
54
OPERATN_ROUTING_ PK
ID
AFFH.AUFPL - Routing number of operations
in the order
NVARCSTR
10
0
0
no
55
OPERATN_SEQ_ID
AFFH.APLZL - Internal counter
NVARCSTR
8
0
0
no
56
PLANT_ID
AFVC/AUFK.WERKS -Plant lID of the
production resource/tool
NVARCSTR
4
0
0
yes
57
PLAN_USG_VALUE
AFFH.EWSOL - Total planned usage value of
production resource/tool
DECIMAL
48
9
3
yes
58
PROFIT_CNTR_ID
AFVC/AUFK.PRCTR Profit Center
NVARCSTR
10
0
0
yes
59
PROJ_ELEM_ID
AFVC/AFPO.PROJN - Work breakdown
structure element (WBS element) / Lookup on
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
60
PROJ_ID
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
61
PRT_ASSIGNMNT_SE PK
Q_ID
AFFH.PZLFH - Item counter for production
resources/tools
NVARCSTR
8
0
0
no
62
PRT_ASSIGN_DESCR
AFFH.TXTZ1 - First line of text for production
resources/tools
NVARCSTR
40
0
0
yes
63
PRT_CATEG_ID
CRFH.FHMAR -Production resources/tools
category
NVARCSTR
1
0
0
yes
64
PRT_ID
AFFH.OBJID - Object ID of the resource
NVARCSTR
8
0
0
yes
65
PRT_NAME
CRVS_A./CRVS_B.SFHNR - Production
resources and tools Name (lookup)
NVARCSTR
18
0
0
yes
66
PRT_STATUS_ID
TCF05.STATUS - Production resources/tools
master: Status
NVARCSTR
2
0
0
yes
67
PURCH_ORG_ID
T001W.EKORG Purchasing organization
(lookup)
NVARCSTR
4
0
0
yes
68
QTY_DURTN
AFFH.DAUFL - Duration of PRT usage
DECIMAL
48
22
7
yes
69
QTY_OFFSET_END
AFFH.OFFSTE - Offset to finish of production
resource/tool usage
INTEGER
4
0
0
yes
70
QTY_OFFSET_START
AFFH.OFFSTB - Offset to start of production
resource/tool usage
INTEGER
4
0
0
yes
PK
Rapid Mart Data Schema
A
128
Appendix
Table Column Details
71
QTY_PRT_CHECKO
UT
AFFH.MGAUS - Quantity of checked-out
production resources/tools
DECIMAL
48
9
3
yes
72
QTY_PRT_CONFIRM
AFFH.MGIST - Confirmed quantity of
production resource/tool
DECIMAL
48
9
3
yes
73
QTY_PRT_PLAN
AFFH.MGSOL - Total planned quantity of
production resource/tool
DECIMAL
48
9
3
yes
74
QTY_PRT_REMAIN
AFFH.MGRSTEH - Remaining quantity of the
production resource/tool
DECIMAL
48
9
3
yes
75
QTY_PRT_STD
AFFH.MGVGW - Standard value for the PRT
quantity
DECIMAL
48
9
3
yes
76
REMAIN_USG_VALUE
AFFH.EWRST - Remaining usage value of the DECIMAL
production resource/tool
48
9
3
yes
77
RESOURCE_ID_WR
KCNTR
AFVC.ARBID -Object ID of the resource
NVARCSTR
8
0
0
yes
78
ROUTING_ID
Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR
11
0
0
yes
79
SCHED_EARLST_END
_DATE
AFFH.FEFHD - Earliest scheduled finish (date)
of PRT usage+AFFH.FEFHZ - Earliest
DATETIME
scheduled end (time) of PRT usage
24
0
9
yes
80
SCHED_EARLST_STA
RT_DATE
AFFH.FSFHD - Earliest scheduled start (date)
for PRT usage+ AFFH.FSFHZ - Earliest
scheduled start (time) for PRT usage
DATETIME
24
0
9
yes
81
SCHED_LATEST_END
_DATE
AFFH.SEFHD - Latest scheduled finish (date)
of PRT usage+AFFH.SEFHZ - Latest
scheduled end (time) for PRT usage
DATETIME
24
0
9
yes
82
SCHED_LATEST_STA
RT_DATE
AFFH.SSFHD - Latest scheduled start (date)
for PRT usage+AFFH.SSFHZ - Latest
scheduled start (time) for PRT usage
DATETIME
24
0
9
yes
83
STD_TEXT_KEY_ID
AFFH.KTSCH - Standard text key for
production resources/tools
NVARCSTR
7
0
0
yes
84
STD_USG_VALUE
AFFH.EWVGW - Standard usage value for
production resources/tools
DECIMAL
48
9
3
yes
85
STORAGE_LOCATN_I
D
AFPO.LGORT Storage location
NVARCSTR
4
0
0
yes
86
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
87
UOM_ID_ACTL_USG
AFFH.EWISTEH - Usage value unit of the
production resource/tool
NVARCSTR
3
0
0
yes
88
UOM_ID_DURTN
AFFH.DAUEH - Time unit for duration of PRT
usage
NVARCSTR
3
0
0
yes
Rapid Mart Data Schema
A
129
Appendix
Table Column Details
89
UOM_ID_END
AFFH.EHOFFE - Offset unit for end of
production resource/tool usage
NVARCSTR
3
0
0
yes
90
UOM_ID_PLAN_USG
AFFH.EWSOLEH - Usage value unit of the
production resource/tool
NVARCSTR
3
0
0
yes
91
UOM_ID_PRT_CHECK
OUT
AFFH.MGAUSEH - Quantity unit of production NVARCSTR
resource/tool
3
0
0
yes
92
UOM_ID_PRT_CONFI
RM
AFFH.MGISTEH - Quantity unit of production
resource/tool
NVARCSTR
3
0
0
yes
93
UOM_ID_PRT_PLAN
AFFH.MGSOLEH - Quantity unit of production
resource/tool
NVARCSTR
3
0
0
yes
94
UOM_ID_PRT_REMAI
N
AFFH.MGRSTEH - Quantity unit of production
resource/tool
NVARCSTR
3
0
0
yes
95
UOM_ID_PRT_STD
AFFH.MGEINH - Quantity unit of production
resource/tool
NVARCSTR
3
0
0
yes
96
UOM_ID_REMAIN_US
G
AFFH.EWRSTEH - Usage value unit of the
production resource/tool
NVARCSTR
3
0
0
yes
97
UOM_ID_START
AFFH.EHOFFB - Offset unit for start of prod.
resource/tool usage
NVARCSTR
3
0
0
yes
98
UOM_ID_STD_USG
AFFH.EWEINH - Usage value unit of the
production resource/tool
NVARCSTR
3
0
0
yes
99
VALUATN_AREA_ID
T001W.BWKEY Valuation area lookup
NVARCSTR
4
0
0
yes
100 WORK_CNTR_CATE
G_ID
CRHD.VERWE - Work center category ID
lookup
NVARCSTR
4
0
0
yes
101 WORK_CNTR_ID
CRHD.ARBPL - Work center- Visible ID in
SAP
NVARCSTR
8
0
0
yes
Rapid Mart Data Schema
A
130
Appendix
Table Column Details
A
PRT_CATEGORY
Descriptive attributes from TCF03 of Production Resource/Tools categories
Column Desc
Column
Datatype
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
3
PRT_CATEG_CODE
TCF03.FHMAR_EXT -Production resource/tool NVARCSTR
category
1
0
0
yes
4
PRT_CATEG_DESCR
TCF03.FAKTX -Language-dependent
description of the PRT category
NVARCSTR
40
0
0
yes
5
PRT_CATEG_ID
TCF03.FHMAR -Production resources/tools
category
NVARCSTR
1
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Is
Nullable
PRT_GROUPING_KEY
Production Resource/Tools grouping key descriptive attributes from TCF13
Column Desc
Column
Datatype
TCF13.FGRTXT -Text for the production
resources/tools group key
NVARCSTR
40
0
0
yes
TCF13.FGRUA -Grouping key 1 for production NVARCSTR
resources/tools
4
0
0
no
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
#
Column Name
1
GROUPNG_KEY_DE
SCR
2
GROUPNG_KEY_ID
3
4
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
131
Appendix
Table Column Details
A
PRT_MASTER
Master records from CRFH with production resource/tools details. Current records only
Column Desc
Column
Datatype
CHANGE_DATE
CRFH.AEDAT -Date of Last Change
DATETIME
24
0
9
yes
2
CMPNY_CODE_FULL_
NAME
Company Code ID + Company Code Name
from T001
NVARCSTR
120
0
0
yes
3
CMPNY_CODE_ID
Company Code ID
NVARCSTR
4
0
0
yes
4
CREATE_DATE
CRFH.ANDAT -Date record created on
DATETIME
24
0
9
yes
5
CTRL_AREA_FULL_N
AME
Lookup on TKA01 for controlling area ID +
name
NVARCSTR
120
0
0
yes
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
8
DELETE_FLAG
CRFH.LOEKZ =Deletion indicator for
production resources/tools master (1/0 values) INTEGER
4
0
0
yes
9
FORMULA_DESCR_
TTL_QTY
TC25T-TXT - Lookup on Formula descritpion
for Total Quantity
NVARCSTR
20
0
0
yes
10
FORMULA_DESCR_
TTL_USG
TC25T-TXT - Lookup on Formula descritpion
for Total usage
NVARCSTR
20
0
0
yes
11
FORMULA_ID_TTL_Q
TY
CRFH.MGFORM -Formula for calculating the
total quantity of PRT
NVARCSTR
6
0
0
yes
12
FORMULA_ID_TTL_U
SG
CRFH.EWFORM -Formula for calculating the
total usage value of PRT
NVARCSTR
6
0
0
yes
13
GROUPNG_KEY_DE
SCR_01
TCF13.FGRTXT - Text for the production
resources/tools group key (lookup)
NVARCSTR
40
0
0
yes
14
GROUPNG_KEY_DE
SCR_02
TCF13.FGRTXT - Text for the production
resources/tools group key (lookup)
NVARCSTR
40
0
0
yes
15
GROUPNG_KEY_ID_0
1
CRFH.FGRU1 - Grouping key 1 for production NVARCSTR
resources/tools
4
0
0
yes
16
GROUPNG_KEY_ID_0
2
CRFH.FGRU2 -Grouping key 2 for production
resources/tools
4
0
0
yes
#
Column Name
1
Key
NVARCSTR
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
132
Appendix
Table Column Details
17
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
18
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
19
LOCATN_FULL_NAME
Lookup onT499S for Plant Location ID +name NVARCSTR
120
0
0
yes
20
LOCATN_ID
CRFH.STORT- Location of a production
resource or tool
NVARCSTR
10
0
0
yes
21
PARAMETER_ID_01
CRFH.PAR01 -First parameter (for formulas)
NVARCSTR
6
0
0
yes
22
PARAMETER_ID_02
CRFH.PAR02 -Second parameter (for
formulas)
NVARCSTR
6
0
0
yes
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
27
PARAMETER_VALUE_
01
CRFH.PARV1 -Parameter value
DECIMAL
48
9
3
yes
28
PARAMETER_VALUE_
02
CRFH.PARV2 -Parameter value
DECIMAL
48
9
3
yes
29
PARAMETER_VALUE_
03
CRFH.PARV3 -Parameter value
DECIMAL
48
9
3
yes
30
PARAMETER_VALUE_
04
CRFH.PARV4 -Parameter value
DECIMAL
48
9
3
yes
31
PARAMETER_VALUE_
05
CRFH.PARV5 -Parameter value
DECIMAL
48
9
3
yes
32
PARAMETER_VALUE_
06
CRFH.PARV6 -Parameter value
DECIMAL
48
9
3
yes
33
PLANT_FULL_NAME
T001W.NAME1 - lookup on Plant ID+ Name
NVARCSTR
120
0
0
yes
34
PLANT_ID
CRFH.STOWK -Plant location of the
production resource/tool
NVARCSTR
4
0
0
yes
Rapid Mart Data Schema
A
133
Appendix
Table Column Details
35
PRT_CATEG_DESCR
TCF03.FAKTX - PRT Category Description
NVARCSTR
40
0
0
yes
36
PRT_CATEG_ID
CRFH.FHMAR -Production resources/tools
category
NVARCSTR
1
0
0
yes
37
PRT_CTRL_KEY_DES
CR
TCF11.STFTXT - Control key description
(lookup) for PRT
NVARCSTR
40
0
0
yes
38
PRT_CTRL_KEY_ID
CRFH.STEUF -Control key for management of NVARCSTR
production resources/tools
4
0
0
yes
39
PRT_DESCR
Lookup work center description in CRTX
NVARCSTR
40
0
0
yes
40
PRT_ID
CRFH.OBJID -Object ID of the resource
NVARCSTR
8
0
0
no
41
PRT_NAME
CRVS_A./CRVS_B.SFHNR - Production
resources and tools Name (lookup)
NVARCSTR
18
0
0
yes
42
PRT_STATUS_DESCR
TCF05.KTEXT - PRT Status Description
NVARCSTR
40
0
0
yes
43
PRT_STATUS_ID
CRFH.STATUS -Production resources/tools
master: Status
NVARCSTR
2
0
0
yes
44
STD_TEXT_KEY_DES
CR
T435T.TXT - Description of the standard text
key (lookup)
NVARCSTR
40
0
0
yes
45
STD_TEXT_KEY_ID
CRFH.KTSCH -Standard text key for
production resources/tools
NVARCSTR
7
0
0
yes
46
TASK_LIST_USG_DES
CR
TC23T.TXT - Description of the usage key
(lookup)
NVARCSTR
30
0
0
yes
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
49
UOM_ID_02
CRFH.PARU2 -Parameter unit
NVARCSTR
3
0
0
yes
50
UOM_ID_03
CRFH.PARU3 -Parameter unit
NVARCSTR
3
0
0
yes
51
UOM_ID_04
CRFH.PARU4 -Parameter unit
NVARCSTR
3
0
0
yes
52
UOM_ID_05
CRFH.PARU5 -Parameter unit
NVARCSTR
3
0
0
yes
PK
Rapid Mart Data Schema
A
134
Appendix
Table Column Details
53
UOM_ID_06
CRFH.PARU6 -Parameter unit
NVARCSTR
3
0
0
yes
54
UOM_ID_BASE
CRFH.BASEH -Base unit of measure for
production resources/tools
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
57
VALUATN_AREA_ID
T001W.BWKEY Valuation area lookup
NVARCSTR
4
0
0
yes
A
PRT_STATUS
Descriptive attribututes for PRT status from TCF05
Column Desc
Column
Datatype
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
3
PRT_STATUS_DESCR
TCF05.KTEXT PRT master: Status description NVARCSTR
40
0
0
yes
4
PRT_STATUS_ID
TCF05.STATUS - Production resources/tools
master: Status
2
0
0
no
#
Column Name
1
Key
PK
NVARCSTR
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
135
Appendix
Table Column Details
A
PURCH_ORGANIZATION
T024E - Purchasing Organization
Column Desc
Column
Datatype
CMPNY_CODE_ID
Company code
NVARCSTR
4
0
0
yes
2
CMPNY_CODE_NAME
T001.BUTXT - Lookup on Company Code
Name
NVARCSTR
25
0
0
yes
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
Purchasing organization
NVARCSTR
4
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Is
Nullable
REFERENCE_DATE_KEY
Key determining the reference date for various entities - Milestone, PRT - Domain MLST_SDDAT; TCA55
#
Column Name
1
DATE_KEY_DESCR
2
DATE_KEY_ID
Column Desc
Column
Datatype
Short text describing ABAP/4 Dictionary
objects; domain MLST_SDDAT
NVARCSTR
60
0
0
yes
PK
Values for domains: Single value/upper limit domain MLST_SDDAT
NVARCSTR
10
0
0
no
PK
Dimension Source. This is a combined
dimension combining different varieties of
"Reference Date Key" from different sources.
This field identifies the source of "Referere
NVARCSTR
10
0
0
no
Key
Dtype
Length Precision Scale
Is
Nullable
3
DIM_SRC_ID
4
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
5
LOAD_TIME
Time loaded into Rapid mart
NVARCSTR
8
0
0
yes
Rapid Mart Data Schema
136
Appendix
Table Column Details
A
RELATIONSHIP_TYPE
Network Relationship descriptive attributes from TCN2T
Column Desc
Column
Datatype
LOAD_DATE
Date and time when the record loaded into
RapidMart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time loaded into RapidMart
NVARCSTR
8
0
0
yes
3
RELATIONSHIP_TYPE
_DESCR
TCN2T.AOBTX -Short text for the type of
relationship
NVARCSTR
20
0
0
yes
4
RELATIONSHIP_TYPE PK
_ID
TCN2T.AOBKT - Short text for the relationship NVARCSTR
type
2
0
0
no
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
137
Appendix
Table Column Details
A
ROUTING
Routing Header information from PLKO
Column Desc
Column
Datatype
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
6
CMPNY_CODE_FULL_
NAME
T001K -BUKRS -Company Code ID+Lookup
on Company Code Name
NVARCSTR
120
0
0
yes
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
9
CTRL_AREA_FULL_N
AME
PLKO.KOKRS - Controlling
area+TKA01-BEZEI - Controlling area
description
NVARCSTR
120
0
0
yes
10
CTRL_AREA_ID
PLKO.KOKRS - Controlling area
NVARCSTR
4
0
0
yes
11
DELETE_FLAG
PLKO.DELKZ - Indicator: Delete completely in
reorganization run (1/0)
INTEGER
4
0
0
yes
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
14
GROUP_TYPE_DES
CR
Lookup desription of task list type in TC A02
NVARCSTR
30
0
0
yes
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
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
138
Appendix
Table Column Details
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
20
LOAD_TIME
Time in a string format when the record was
loaded into the target database
NVARCSTR
8
0
0
yes
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
25
PLANT_FULL_NAME_
PLAN
PLKO.IWERK - Planning plant+T001W.NAME1 NVARCSTR
-Name of Planning Plant
120
0
0
yes
26
PLANT_ID
PLKO.WERKS Plant
NVARCSTR
4
0
0
yes
27
PLANT_ID_PLAN
PLKO.IWERK - Planning plant
NVARCSTR
4
0
0
yes
28
PROCESS_TYPE_DES
CR
lookup on C2_PRTYP domain in DD07T
NVARCSTR
60
0
0
yes
29
PROJ_DESCR
PROJ.POST1 - Project Short description (1st
text line)
NVARCSTR
40
0
0
yes
30
PROJ_ELEM_DESCR
PRPS.POST1 - Project Element Short
description (1st text line)
NVARCSTR
40
0
0
yes
31
PROJ_ELEM_ID
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
32
PROJ_ID
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
33
ROUTING_DESCR
PLKO.KTEXT- Short description
NVARCSTR
40
0
0
yes
34
ROUTING_ID
Concatenated PLKO.PLNNR, PLNTY, PLNAL NVARCSTR
11
0
0
no
PK
Rapid Mart Data Schema
A
139
Appendix
Table Column Details
35
ROUTING_STATUS_D
ESCR
T412T.TXT - Routing status description lookup
NVARCSTR
40
0
0
yes
36
ROUTING_STATUS_ID
PLKO.STATU - Routing Status
NVARCSTR
3
0
0
yes
37
SYSTEM_CONDITN_D
ESCR
T357M_T-ANLZUX - Operating status text lookup
NVARCSTR
40
0
0
yes
38
SYSTEM_CONDITN_I
D
PLKO.ANLZU - System condition
NVARCSTR
1
0
0
yes
39
UOM_ID_BASE
PLKO.PLNME - Header unit of measure of
base material
NVARCSTR
3
0
0
yes
40
VALID_FROM_DATE
PLKO.DATUV - Valid-from date for routing
group assignment
DATETIME
24
0
9
yes
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
43
WORK_CNTR_FULL
_NAME
Lookup on CRHD.ARBPL - Work Center
Number+ Lookup work center description in
CRTX
NVARCSTR
120
0
0
yes
44
WORK_CNTR_ID
Lookup on CRHD.ARBPL - Work Center
Number
NVARCSTR
8
0
0
yes
Rapid Mart Data Schema
A
140
Appendix
Table Column Details
A
ROUTING_OPERATION
Routing master data from PLPO
Column Desc
Column
Datatype
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
5
CAPACITY_CATEG_D
ESCR
TC26T.TXT -Lookup capacity category
description
NVARCSTR
20
0
0
yes
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
8
CMPNY_CODE_FULL_
NAME
T001K -BUKRS -Company Code ID+Lookup
on Company Code Name
NVARCSTR
120
0
0
yes
9
CMPNY_CODE_ID
T001K -BUKRS -Company Code ID
NVARCSTR
4
0
0
yes
10
COSTNG_RELEVNT_F
LAG
PLPO. CKSELKZ - Indicator for relevancy to
costing
INTEGER
4
0
0
yes
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
14
CTRL_AREA_FULL_N
AME
PLKO.KOKRS - Controlling
area+TKA01-BEZEI - Controlling area
description
NVARCSTR
120
0
0
yes
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
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
141
Appendix
Table Column Details
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
22
GROUP_TYPE_DES
CR
TCA02.TXT - Lookup desription of task list type NVARCSTR
30
0
0
yes
23
GROUP_TYPE_ID
PLPO.PLNTY -Task List Type
NVARCSTR
1
0
0
no
24
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
25
LOAD_TIME
Load time
NVARCSTR
8
0
0
yes
26
NUM_CAPACITY_REQ
PLPO.ANZZL -Number of capacities required
DECIMAL
48
28
0
yes
27
OPERATN_DESCR_01
PLPO.LTXA1 - First line of operation
description
NVARCSTR
80
0
0
yes
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
33
PROJ_DESCR
PROJ.POST1 - Project Short description (1st
text line)
NVARCSTR
40
0
0
yes
34
PROJ_ELEM_DESCR
PRPS.POST1 - Project Element Short
description (1st text line)
NVARCSTR
40
0
0
yes
PK
Rapid Mart Data Schema
A
142
Appendix
Table Column Details
35
PROJ_ELEM_ID
PRPS.POSID - Project Element (WBS)
External ID
NVARCSTR
24
0
0
yes
36
PROJ_ID
PROJ.PSPID - Project External ID
NVARCSTR
24
0
0
yes
37
QTY_STD
PLPO.BMSCH - Quantity of the material to be
produced to which the standard values of the
operation refer
DECIMAL
48
13
3
yes
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
40
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
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
45
WAGE_GRP_DESCR
T421T.TXT - Lookup desription of wage group
description
NVARCSTR
30
0
0
yes
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
48
WORK_CNTR_FULL
_NAME
Lookup on CRHD.ARPBL - Visible Work
Center ID in SAPLookup work center
description in CRTX
NVARCSTR
120
0
0
yes
49
WORK_CNTR_ID
Lookup on CRHD.ARPBL - Visible Work
Center ID in SAP
NVARCSTR
8
0
0
yes
Rapid Mart Data Schema
A
143
Appendix
Table Column Details
A
ROUTING_SEQUENCE
Routing (Task List) sequence definition from PLFL
Column Desc
Column
Datatype
ALIGNMNT_KEY_DES
CR
TCA53.AUSCH_STXT - Lookup on short
desription of Allignment Key
NVARCSTR
10
0
0
yes
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
7
GROUP_LINE_CATEG
_DESCR
TCA08.FLG_STXT - Lookup on short
desription of task list sequence category
NVARCSTR
10
0
0
yes
8
GROUP_LINE_CATEG
_ID
PLFL.FLGAT - Sequence category
NVARCSTR
1
0
0
yes
9
GROUP_LINE_DESCR
PLFL.LTXA1 -Sequence description
NVARCSTR
40
0
0
yes
10
GROUP_LINE_ID
PLFL.PLNFL - Sequence of
operations/activities
NVARCSTR
6
0
0
no
11
GROUP_SEQ_ID
PLPO.PLNAL Group counter
NVARCSTR
2
0
0
yes
12
GROUP_TYPE_DES
CR
TCA02.TXT - Lookup desription of task list type NVARCSTR
30
0
0
yes
13
GROUP_TYPE_ID
PLFL.PLNTY -Task List Type
NVARCSTR
1
0
0
yes
14
LOAD_DATE
Date and time the record was loaded into
Rapid Mart
DATETIME
24
0
9
yes
15
LOAD_TIME
Load time
NVARCSTR
8
0
0
yes
16
LOT_SIZE_MAX
PLFL.LOSBS -To lot size
DECIMAL
48
13
3
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
144
Appendix
Table Column Details
17
LOT_SIZE_MIN
PLFL.LOSVN -From lot size
DECIMAL
48
13
3
yes
18
ROUTING_ID
Concatenate PLNNR, PLNTY, PLNAL
NVARCSTR
11
0
0
no
19
SURROGATE_DOC_ID
Alternate key generated in the Rapid Mart for
reporting purposes
DECIMAL
48
18
0
yes
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
PK
A
SERVICE_PERSON
Populates SERVICE_PERSON dimension with Employee names. This is a reference dimension only, and not Employee master data
Column Desc
Column
Datatype
FIRST_NAME
PA0002-VORNA - First name
NVARCSTR
40
0
0
yes
2
FULL_NAME
PA0002-NACHN - Last name +
PA0002-VORNA - First name
NVARCSTR
90
0
0
yes
3
LAST_NAME
PA0002-NACHN - Last name
NVARCSTR
40
0
0
yes
4
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
5
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
6
PERSON_ID
PA0002-PERNR - Personnel number
NVARCSTR
8
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
145
Appendix
Table Column Details
A
SPECIAL_PROCUREMENT_TYPE
Descriptive attributes from DD07T for domain SOBES
Column Desc
Column
Datatype
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
3
SPECL_PROCUREM
NT_TYPE_DESCR
DD07T.DDTEXT - Special Procurement type
description
NVARCSTR
30
0
0
yes
4
SPECL_PROCUREM
NT_TYPE_ID
DD07T.DOMVALUE_L - Special Procurement
type code
NVARCSTR
1
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Is
Nullable
STANDARD_TEXT_KEY
Standard text Key descriptions for activities from T435T
Column Desc
Column
Datatype
LOAD_DATE
Load date and time when the record was
loaded into the target database
DATETIME
24
0
9
yes
2
LOAD_TIME
Time in string format when the record was
loaded into the target database
NVARCSTR
8
0
0
yes
3
STD_TEXT_KEY_DES
CR
T435T.TXT - Description of the standard text
key
NVARCSTR
40
0
0
yes
4
STD_TEXT_KEY_ID
T435T.VLSCH - Standard text key
NVARCSTR
7
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
146
Appendix
Table Column Details
A
STATUS_PROFILE
Milestone Status profile descriptive attributes from TJ20T
Key
Column Desc
Column
Datatype
Dtype
Length Precision Scale
Is
Nullable
#
Column Name
1
LOAD_DATE
Date and time when the record was loaded into DATETIME
the target database
24
0
9
yes
2
LOAD_TIME
Time loaded into the target database
NVARCSTR
8
0
0
yes
3
STATUS_PROFILE_D
ESCR
TJ20T.TXT - Text (30 Characters)
NVARCSTR
30
0
0
yes
4
STATUS_PROFILE_ID PK
TJ20T.STSMA - Status profile
NVARCSTR
8
0
0
no
Rapid Mart Data Schema
147
Appendix
Table Column Details
A
STORAGE_LOCATION
T001L - Storage Locations in SAP
Column Desc
Column
Datatype
CMPNY_CODE_ID
T001K. BUKRS - Lookup for Company Code
ID
NVARCSTR
4
0
0
yes
2
CMPNY_CODE_NAME
Lookup on Company Code Name
NVARCSTR
25
0
0
yes
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
5
DISTRIBTN_CHANNEL
_DESCR
T001L.VTWEG Distribution channel
NVARCSTR
20
0
0
yes
6
DISTRIBTN_CHANNEL
_ID
T001L.VTWEG Distribution channel
NVARCSTR
2
0
0
yes
7
DIVISION_DESCR
Lookip TSPAT.VTEXT-Division Description
NVARCSTR
20
0
0
yes
8
DIVISION_ID
T001L.SPART Division
NVARCSTR
2
0
0
yes
9
GOODS_MVMT_AUT
HORIZTN_FLAG
T001L.XBLGO Storage location authorization
for goods movements active
NVARCSTR
1
0
0
yes
10
HANDLNG_UNIT_FLA
G
T001L.XHUPF Handling unit requirement
NVARCSTR
1
0
0
yes
11
LOAD_DATE
Date and Time Loaded into Rapid Mart
DATETIME
24
0
9
yes
12
LOAD_TIME
Time Loaded into Rapid Mart
NVARCSTR
8
0
0
yes
13
MRP_DESCR
Lookup T001L.DISKZ MRP Indicator
Description
NVARCSTR
60
0
0
yes
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
T001L.WERKS Plant
NVARCSTR
4
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
148
Appendix
Table Column Details
17
PLANT_NAME
T001W.NAME1 - Plant Name
NVARCSTR
30
0
0
yes
18
PURCH_ORG_ID
T001W.EKORG -Purchasing Organization
Code
NVARCSTR
4
0
0
yes
19
PURCH_ORG_NAME
Lookup on Purchasing org Name T024E
NVARCSTR
20
0
0
yes
20
RESOURCE_ALLOC
TN_FLAG
T001L.XRESS Storage location is allocated to
resource (storage resource)
NVARCSTR
1
0
0
yes
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
25
STORAGE_LOCATN
_DESCR
T001L.LGOBE Description of storage location
NVARCSTR
16
0
0
yes
26
STORAGE_LOCATN_F
ULL_NAME
Concatenation of Storage Location ID and
Description
NVARCSTR
26
0
0
yes
27
STORAGE_LOCATN_I PK
D
T001L.LGORT Storage location
NVARCSTR
4
0
0
no
28
STORAGE_LOCATN_I
D_PARTNER
T001L.PARLG Partner storage location of the
handling unit
NVARCSTR
4
0
0
yes
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
Rapid Mart Data Schema
A
149
Appendix
Table Column Details
A
TASK_LIST_TYPE
Task List Type descriptive attributes from TCA02 - TASK_LIST_TYPE dimension
Column Desc
Column
Datatype
TCA02.TXT -Desccription of the task list type
NVARCSTR
30
0
0
yes
TCA02.PLNTY -Task List Type
NVARCSTR
1
0
0
no
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
#
Column Name
1
GROUP_TYPE_DES
CR
2
GROUP_TYPE_ID
3
4
Key
PK
Dtype
Length Precision Scale
Is
Nullable
TASK_LIST_USAGE
Task List Usage descriptive attributes from TC23T (TASK_LIST_USAGE)
Column Desc
Column
Datatype
TC23T.TXT - Description of the usage key
NVARCSTR
30
0
0
yes
TC23T.PLANV - Key for task list usage
NVARCSTR
3
0
0
no
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
#
Column Name
1
GROUP_USG_DESCR
2
GROUP_USG_ID
3
4
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
150
Appendix
Table Column Details
A
TIME_DIM
Time Dimension (Daily)
#
Column Name
Key
Column Desc
Column
Datatype
Dtype
Length Precision Scale
1
CALENDAR_DATE
PK
Calendar Date
DATETIME
24
0
9
no
2
CALENDAR_MONTH
Number of Calendar Month
INTEGER
4
0
0
yes
3
CALENDAR_QUART
ER
Calendar Quarter
INTEGER
4
0
0
yes
4
CALENDAR_YEAR
Calenar Year
INTEGER
4
0
0
yes
5
DAY_IN_PERIOD
Number of a day in a fiscal period
INTEGER
4
0
0
yes
6
DAY_IN_WEEK
Day of the week
INTEGER
4
0
0
yes
7
FISC_PERIOD
Fiscal Period of Calendar Date. Retrieved from INTEGER
SAP using FI_PERIOD_DETEMINE
4
0
0
yes
8
FISC_YEAR
Fiscal Year of Calendar Date. Retrieved from
SAP using FI_PERIOD_DETEMINE
INTEGER
4
0
0
yes
9
IS_WEEKEND
Indicates if date falls on a weekend (1)
NVARCSTR
1
0
0
yes
10
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
11
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
12
MONTH_YEAR
Calendar Month and Year
NVARCSTR
10
0
0
yes
13
WEEK_IN_YEAR
Number of week in the year
DECIMAL
48
28
0
yes
Rapid Mart Data Schema
Is
Nullable
151
Appendix
Table Column Details
A
TIME_DIM_WEEKLY
Time Dimension (WEEKLY). Used for summary facts (such as BENEFIT_ENROLL_SUMMARY_FACT)
#
Column Name
Key
Column Desc
Column
Datatype
1
CALENDAR_YEAR
PK
Calenar Year
INTEGER
2
LOAD_DATE
3
Dtype
Length Precision Scale
Is
Nullable
4
0
0
no
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
4
WEEK_END_DATE
Last date in the week
DATETIME
24
0
9
yes
5
WEEK_IN_YEAR
Number of week in the year
DECIMAL
48
28
0
no
6
WEEK_NAME
Week - Year concatenation
NVARCSTR
60
0
0
yes
7
WEEK_START_DATE
First date of the week
DATETIME
24
0
9
yes
8
WEEK_START_FISC_
PER
Fiscal Period when the week starts
INTEGER
4
0
0
yes
9
WEEK_START_FISC_
YEAR
Fiscal Year when the week starts
INTEGER
4
0
0
yes
10
WEEK_START_MON
TH
Number of Calendar Month when the week
starts
INTEGER
4
0
0
yes
11
WEEK_START_QUA
RTER
Calendar Quarter when the week starts
INTEGER
4
0
0
yes
PK
Rapid Mart Data Schema
152
Appendix
Table Column Details
A
UNIT_OF_MEASURE
T006A-Material Unit of Measure attritues
Key
Column
Datatype
Is
Nullable
Column Name
1
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
2
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
3
UOM_CODE
T006A.MSEH3 -- Unit of Meas. ID in Local
Language (External unit of measurement
commercial format (3-char))
NVARCSTR
3
0
0
yes
4
UOM_DESCR
T006A-MSEHT - Measurement unit text (max.
10 char.)
NVARCSTR
10
0
0
yes
5
UOM_ID
T006A-MSEHI - Unit of measurement
NVARCSTR
3
0
0
no
PK
Column Desc
Dtype
Length Precision Scale
#
VALUATION_AREA
Describes level at which stocks are valuated together, generally a company, plant or group of plants.
Column Desc
Column
Datatype
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
5
LOAD_DATE
Date and time when the record was loaded into DATETIME
Rapid Mart
24
0
9
yes
6
LOAD_TIME
Time when the record was loaded into the
RapidMart (string format HH24:MI:SS)
NVARCSTR
8
0
0
yes
7
VALUATN_AREA_ID
T001.BWKEY Valuation Area Key
NVARCSTR
4
0
0
no
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
153
Appendix
Table Column Details
A
VARIANCE_CATEGORY
Financial Variance Category descriptive attributes (ABKAT domain from DD07T)
Column Desc
Column
Datatype
LOAD_DATE
Date and Time loaded into Rapid mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time Loaded into Rapid mart
NVARCSTR
8
0
0
yes
3
VARIANCE_CATEG_D
ESCR
DD07T-DDTEXT - Short text describing
ABAP/4 Dictionary objects (ABKAT)
NVARCSTR
60
0
0
yes
4
VARIANCE_CATEG_ID PK
DD07T-DOMVALUE_L - Values for domains:
Single value/upper limit(ABKAT)
NVARCSTR
10
0
0
no
#
Column Name
1
Key
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
154
Appendix
Table Column Details
A
WORK_CENTER
Work center descriptions and standard capacity information from CRHD used as default by capacity planning processes
Column Desc
Column
Datatype
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
3
CMPNY_CODE_ID
Company Code ID
NVARCSTR
4
0
0
yes
4
CMPNY_CODE_NAME
Lookup on Company Code Name
NVARCSTR
25
0
0
yes
5
CTRL_KEY_DESCR
T430T-TXT -Control Key desctiption (lookup)
NVARCSTR
40
0
0
yes
6
CTRL_KEY_ID
CRHD.STEUS - Control key
NVARCSTR
4
0
0
yes
7
CURRENT_FLAG
1 indicates record is currently in effect (1/0)
INTEGER
4
0
0
yes
8
DELETE_FLAG
CRHD.LVORM - Deletion flag for work center ( INTEGER
1/0)
4
0
0
yes
9
FORMULA_DESCR_
OTHER
TC25T-TXT - Lookup on Formula descritpion
for Other
NVARCSTR
20
0
0
yes
10
FORMULA_DESCR_
PROCESS
TC25T-TXT - Lookup on Formula descritpion
for Process
NVARCSTR
20
0
0
yes
11
FORMULA_DESCR_
SETUP
TC25T-TXT - Lookup on Formula descritpion
for Setup
NVARCSTR
20
0
0
yes
12
FORMULA_DESCR_
TEARDOWN
TC25T-TXT - Lookup on Formula descritpion
for TearDown
NVARCSTR
20
0
0
yes
13
FORMULA_ID_OTHER
CRHD.FORTN - Formula for other workcenter NVARCSTR
times
6
0
0
yes
14
FORMULA_ID_PROCE
SS
CRHD.FORT2 - Formula for work center
processing time duration
NVARCSTR
6
0
0
yes
15
FORMULA_ID_SETUP
CRHD.FORT1 - Formula for work center setup NVARCSTR
time
6
0
0
yes
16
FORMULA_ID_TEARD
OWN
CRHD.FORT3 - Formula for work center
teardown time calculation
6
0
0
yes
#
Column Name
1
Key
NVARCSTR
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
155
Appendix
Table Column Details
17
LOAD_DATE
Date and time when the record is loaded into
Rapid Mart
DATETIME
24
0
9
yes
18
LOAD_TIME
Time loaded into Rapid Mart
NVARCSTR
8
0
0
yes
19
LOCATN_GRP_DES
CR
TC28T-TXT - Location group desctiption
(lookup)
NVARCSTR
20
0
0
yes
20
LOCATN_GRP_ID
CRHD.ORTGR - Location group
NVARCSTR
4
0
0
yes
21
MACHINE_TYPE_DES
CR
Lookup machine type group description
NVARCSTR
40
0
0
yes
22
MACHINE_TYPE_GRP
_ID
CRHD.MATYP - Machine type grouping
NVARCSTR
10
0
0
yes
23
MINS_MIN_QUEUE_TI
ME
CRHD.ZWMIN - Minimum queue time
converted to minutes
DECIMAL
48
9
3
yes
24
MINS_STD_QUEUE_TI
ME
CRHD.ZWNOR - Standard queue time
converted to minutes
DECIMAL
48
9
3
yes
25
OBJ_ID
CRHD.HROID - Object ID
NVARCSTR
8
0
0
yes
26
ORG_UNIT_TYPE_DE
SCR
T777O-OTEXT -Object Type Description
NVARCSTR
25
0
0
yes
27
ORG_UNIT_TYPE_ID
CRHD.HRTYP - Object type
NVARCSTR
2
0
0
yes
28
PERSON_RESP_CO
DE
CRHD.VERAN - Person responsible for the
work center
NVARCSTR
3
0
0
yes
29
PERSON_RESP_DE
SCR
Lookup TC24.KTEXT - Person responsible for NVARCSTR
the work center VERAN
40
0
0
yes
30
PLANT_ID
CRHD.WERKS - Plant
NVARCSTR
4
0
0
no
31
PLANT_NAME
T001W.NAME1 - lookup on Plant Name
NVARCSTR
40
0
0
yes
32
STD_TEXT_KEY_COD
E
CRHD.KTSCH - Standard text key
NVARCSTR
7
0
0
yes
33
STD_VALUE_KEY_DE
SCR
Lookup standard value key description in TC21 NVARCSTR
30
0
0
yes
34
STD_VALUE_KEY_ID
CRHD.VGWTS - Standard value key
4
0
0
yes
PK
NVARCSTR
Rapid Mart Data Schema
A
156
Appendix
Table Column Details
35
SUITABILITY_DESCR
T423T-TXT - Sutability( Qualificiation/Wage
Group) desctiption (lookup)
NVARCSTR
30
0
0
yes
36
SUITABILITY_ID
CRHD.QUALF - Suitability for carrying certain
tasks
NVARCSTR
2
0
0
yes
37
SUPPLY_AREA_DESC
R
PVKT-PVBTX -Supply Area Description
NVARCSTR
40
0
0
yes
38
SUPPLY_AREA_ID
CRHD.PRVBE Supply area
NVARCSTR
10
0
0
yes
39
TASK_LIST_USG_DES
CR
Lookup task list usage descripton
NVARCSTR
30
0
0
yes
40
TASK_LIST_USG_ID
CRHD.PLANV - Key for task list usage
NVARCSTR
3
0
0
yes
41
VALID_FROM_DATE
CRHD.BEGDA - Effectivity Start date
DATETIME
24
0
9
yes
42
VALID_TO_DATE
CRHD.ENDDA - Effectivity end date
DATETIME
24
0
9
yes
43
VALUATN_AREA_ID
T001W.BWKEY Valuation area lookup
NVARCSTR
4
0
0
yes
44
WORK_CNTR_CATE
G_DESCR
Lookup description of Work Center category in NVARCSTR
TC30T
20
0
0
yes
45
WORK_CNTR_CATE
G_ID
CRHD.VERWE - Work center category
NVARCSTR
4
0
0
yes
46
WORK_CNTR_CODE
CRHD.OBJID - Work center Internal Object ID NVARCSTR
8
0
0
yes
47
WORK_CNTR_DESCR
Lookup work center description in CRTX
NVARCSTR
40
0
0
yes
48
WORK_CNTR_FULL
_NAME
CRHD.ARBPL - Work center Code + Name
(Lookup work center description in CRTX
NVARCSTR
50
0
0
yes
49
WORK_CNTR_ID
CRHD.ARBPL - Work center- Visible ID in
SAP
NVARCSTR
8
0
0
no
50
WORK_CNTR_LOCA
TN_DESCR
T499S-KTEXT - Location desctiption (lookup)
NVARCSTR
40
0
0
yes
51
WORK_CNTR_LOCA
TN_ID
CRHD.STAND - Work center location
NVARCSTR
10
0
0
yes
PK
Rapid Mart Data Schema
A
157
Appendix
Table Column Details
A
WORK_CENTER_CATEGORY
Work Center Category Attributes from TC30T
Column Desc
Column
Datatype
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
2
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
3
WORK_CNTR_CATE
G_DESCR
TC30T.KTEXT - Description of the work center NVARCSTR
category
20
0
0
yes
4
WORK_CNTR_CATE
G_ID
TC30T.VERWE - Work center cat.
4
0
0
no
#
Column Name
1
Key
PK
NVARCSTR
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
158
Appendix
Table Column Details
A
WORK_CENTER_FORMULA
Capacity formulas from TC25; parameters are parsed from the formula equation text
Column Desc
Column
Datatype
CAPACITY_CALC_FLA
G
TC25.VKAPA - Indicator: work center is
allowed for capacity requirements
INTEGER
4
0
0
yes
2
COSTNG_ALLOW_F
LAG
TC25.VKALK - Indicates it is allowed for
costing
INTEGER
4
0
0
yes
3
FORMULA_DESCR
TC25T.TXT - Lookup formula description in
TC25T
NVARCSTR
20
0
0
yes
4
FORMULA_EQUATN
_TEXT
TC25.FTEXT- Equation of formula
NVARCSTR
70
0
0
yes
5
FORMULA_ID
TC25.IDENT - Formula key
NVARCSTR
6
0
0
no
6
LOAD_DATE
Date and time loaded into Rapid Mart
DATETIME
24
0
9
yes
7
LOAD_TIME
Time when the record was loaded
NVARCSTR
8
0
0
yes
8
PARAMETER_ID_01
Calculated from TC25.FTEXT - parsed
Parameter 01 ID or constant
NVARCSTR
6
0
0
yes
9
PARAMETER_ID_02
Calculated from TC25.FTEXT - parsed
Parameter 02 ID or constant
NVARCSTR
6
0
0
yes
10
PARAMETER_ID_03
Calculated from TC25.FTEXT - parsed
Parameter 03 ID or constant
NVARCSTR
6
0
0
yes
11
PARAMETER_ID_04
Calculated from TC25.FTEXT - parsed
Parameter 04 ID or constant
NVARCSTR
6
0
0
yes
12
PARAMETER_ID_05
Calculated from TC25.FTEXT - parsed
Parameter 05 ID or constant
NVARCSTR
6
0
0
yes
13
PARAMETER_ID_06
Calculated from TC25.FTEXT - parsed
Parameter 06 ID or constant
NVARCSTR
6
0
0
yes
14
PARAMETER_ID_07
Calculated from TC25.FTEXT - parsed
Parameter 07 ID or constant
NVARCSTR
6
0
0
yes
15
PARAMETER_ID_08
Calculated from TC25.FTEXT - parsed
Parameter 08 ID or constant
NVARCSTR
6
0
0
yes
16
PARAMETER_ID_09
Calculated from TC25.FTEXT - parsed
Parameter 09 ID or constant
NVARCSTR
6
0
0
yes
#
Column Name
1
Key
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
159
Appendix
Table Column Details
17
PARAMETER_ID_10
Calculated from TC25.FTEXT - parsed
Parameter 10 ID or constant
NVARCSTR
6
0
0
yes
18
PRT_CALC_FLAG
TC25.VKAPF- Indicator: PRT allowed for
requirements
INTEGER
4
0
0
yes
19
SCHED_ALLOW_FL
AG
TC25.VTERM- Indicator: Allowed for
scheduling
INTEGER
4
0
0
yes
Rapid Mart Data Schema
A
160
Appendix
Table Column Details
A
WORK_CENTER_HIER
Work center parent-child relationship from CRHH/CRHS
Column Desc
Column
Datatype
CHILD_CODE
CRHD.ARBPL Work center Code - Child
NVARCSTR
8
0
0
yes
2
CHILD_DESCR
Lookup work center description in CRTX for
Child WC
NVARCSTR
40
0
0
yes
3
CHILD_FULL_NAME
Concatentaion of WC code and description for
Child Node
NVARCSTR
50
0
0
yes
4
CHILD_ID
CRHS.OBJID_HO - Object ID of the resource
and CRHH.NAME - Name of hierarchy
NVARCSTR
50
0
0
no
5
LOAD_DATE
Load date and time into the target database
DATETIME
24
0
9
yes
6
LOAD_TIME
Load time into the target database
NVARCSTR
8
0
0
yes
7
OWNER_ID
CRHH.VERAN - Person responsible for the
work center
NVARCSTR
3
0
0
yes
8
OWNER_NAME
Lookup TC24.KTEXT - Person responsible for
the work center VERAN
NVARCSTR
40
0
0
yes
9
PARENT_CODE
CRHD.ARBPL - Work center - Parent node
NVARCSTR
8
0
0
yes
10
PARENT_DESCR
Lookup work center description in CRTX for
Parent WC
NVARCSTR
40
0
0
yes
11
PARENT_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
12
PARENT_ID
CRHS.OBJID_UP - ID of superior object in the
hierarchy and CRHH.NAME - Name of
NVARCSTR
hierarchy
50
0
0
no
13
PLANT_ID
CRHH.WERKS - Plant
NVARCSTR
4
0
0
yes
14
PLANT_NAME
T001W.NAME1 - lookup on Plant Name
NVARCSTR
40
0
0
yes
15
WORK_CNTR_HIER_I PK
D
CRHH.OBJID - Object ID of the resource
NVARCSTR
8
0
0
no
16
WORK_CNTR_HIER_N
AME
CRHH.NAME - Name of hierarchy
NVARCSTR
10
0
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
161
Appendix
Table Column Details
A
WORK_CENTER_HIER_BAD
Work center parent-child relationship from CRHH/CRHS - Invalid Records
Column Desc
Column
Datatype
CHILD_CODE
CRHD.ARBPL Work center Code - Child
NVARCSTR
8
0
0
yes
2
CHILD_DESCR
Lookup work center description in CRTX for
Child WC
NVARCSTR
40
0
0
yes
3
CHILD_FULL_NAME
Concatentaion of WC code and description for
Child Node
NVARCSTR
50
0
0
yes
4
CHILD_ID
CRHS.OBJID_HO - Object ID of the resource
and CRHH.NAME - Name of hierarchy
NVARCSTR
50
0
0
no
5
DI_ERROR_ACTN
DI Error Action
NVARCSTR
1
0
0
yes
6
DI_ERROR_COLUMN
DI Error Columns
NVARCSTR
500
0
0
yes
7
LOAD_DATE
Load date and time into the target database
DATETIME
24
0
9
yes
8
LOAD_TIME
Load time into the target database
NVARCSTR
8
0
0
yes
9
OWNER_ID
CRHH.VERAN - Person responsible for the
work center
NVARCSTR
3
0
0
yes
10
OWNER_NAME
Lookup TC24.KTEXT - Person responsible for
the work center VERAN
NVARCSTR
40
0
0
yes
11
PARENT_CODE
CRHD.ARBPL - Work center - Parent node
NVARCSTR
8
0
0
yes
12
PARENT_DESCR
Lookup work center description in CRTX for
Parent WC
NVARCSTR
40
0
0
yes
13
PARENT_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
14
PARENT_ID
CRHS.OBJID_UP - ID of superior object in the
hierarchy and CRHH.NAME - Name of
NVARCSTR
hierarchy
50
0
0
no
15
PLANT_ID
CRHH.WERKS - Plant
NVARCSTR
4
0
0
yes
16
PLANT_NAME
T001W.NAME1 - lookup on Plant Name
NVARCSTR
40
0
0
yes
#
Column Name
1
Key
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
162
Appendix
Table Column Details
17
WORK_CNTR_HIER_I PK
D
CRHH.OBJID - Object ID of the resource
NVARCSTR
8
0
0
no
18
WORK_CNTR_HIER_N
AME
CRHH.NAME - Name of hierarchy
NVARCSTR
10
0
0
yes
Rapid Mart Data Schema
A
163
Appendix
Table Column Details
A
WORK_CENTER_HIER_HZ
Work Center Hierarchical relationship in Horizontal format from CRHH/CRHS
Column Desc
Column
Datatype
LEAF_LVL
Work Center Hierarchy Child ID
DECIMAL
48
28
0
yes
2
LOAD_DATE
Load date and time - for the target database
DATETIME
24
0
9
yes
3
LOAD_TIME
Load time for the target database
NVARCSTR
8
0
0
yes
4
LVL_00_DESCR
Description for 00 Parent Node
NVARCSTR
40
0
0
yes
5
LVL_00_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
6
LVL_00_ID
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
8
0
0
no
7
LVL_01_DESCR
Description for 01 Parent Node
NVARCSTR
40
0
0
yes
8
LVL_01_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
9
LVL_01_ID
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
8
0
0
no
10
LVL_02_DESCR
Description for 02 Parent Node
NVARCSTR
40
0
0
yes
11
LVL_02_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
12
LVL_02_ID
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
8
0
0
no
13
LVL_03_DESCR
Description for 03 Parent Node
NVARCSTR
40
0
0
yes
14
LVL_03_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
15
LVL_03_ID
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
8
0
0
no
16
LVL_04_DESCR
Description for 04 Parent Node
NVARCSTR
40
0
0
yes
#
Column Name
1
Key
PK
PK
PK
PK
Dtype
Length Precision Scale
Rapid Mart Data Schema
Is
Nullable
164
Appendix
Table Column Details
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
8
0
0
no
LVL_05_DESCR
Description for 05 Parent Node
NVARCSTR
40
0
0
yes
20
LVL_05_FULL_NAME
Concatentaion of WC code and description for
Parent Node
NVARCSTR
50
0
0
yes
21
LVL_05_ID
PK
CRHS.OBJID_HO - Object ID of the resource
NVARCSTR
8
0
0
no
22
PLANT_ID
PK
CRHH.WERKS - Plant ID
NVARCSTR
4
0
0
no
23
WORK_CNTR_HIER_N PK
AME
CRHH.NAME - Name of hierarchy
NVARCSTR
10
0
0
no
24
WORK_CNTR_ID
CRHD-ARBPL (lookup) - Work Center unique
name
NVARCSTR
8
0
0
no
17
LVL_04_FULL_NAME
18
LVL_04_ID
19
PK
PK
Rapid Mart Data Schema
A
165
Appendix
Table Column Details
A
WORK_CENTER_HIER_VR
Work Center Hierarchical relationship in Vertical format from CRHH/CRHS
#
Column Name
1
CHILD_FULL_NAME
2
CHILD_ID
3
Key
Column
Datatype
Column Desc
Dtype
Length Precision Scale
Is
Nullable
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR
Object description/name lookup
50
0
0
yes
CRHD-ARBPL (lookup) - Work Center unique
name for Child ID
NVARCSTR
8
0
0
no
DEPTH
Node depth in the hierarchy
DECIMAL
48
28
0
yes
4
LEAF_FLAG
1 - Leaf, 0 - Root
DECIMAL
48
28
0
yes
5
LOAD_DATE
Load date and time - target database
DATETIME
24
0
9
yes
6
LOAD_TIME
Load time - target database
NVARCSTR
8
0
0
yes
7
PARENT_FULL_NAME
KLAT-TXTBZ (lookup)/KLAH-CLASS (lookup) - NVARCSTR
Object description/name lookup
50
0
0
yes
8
PARENT_ID
PK
CRHD-ARBPL (lookup) - Work Center unique
name for Parent ID
NVARCSTR
8
0
0
no
9
PLANT_ID
PK
CRHH.WERKS - Plant ID
NVARCSTR
4
0
0
no
10
ROOT_FLAG
1 - Root, 0 - Leaf
DECIMAL
48
28
0
yes
11
WORK_CNTR_HIER_N PK
AME
CRHH.NAME - Name of hierarchy
NVARCSTR
10
0
0
no
PK
Rapid Mart Data Schema
166