Xi3 Rm Sap Hr Ug En

SAP BusinessObjects HR 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? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Rapid Marts packages accelerate Time to Value . . . . . . . . . . . . . . . . 11SAP BusinessObjects Rapid Marts packages architecture . . . . . . . . . 12

About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Chapter 2 Overview 15What you can do with this Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Supported analyses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Dimensions available to support these analyses . . . . . . . . . . . . . . . . . 19Related Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Components shared with other SAP BusinessObjects Rapid Marts . . 19Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 3 Subject Areas 23Infotypes Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Employee Administration Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Organization Hierarchies Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Relationship to other sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Leave Entitlement Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

SAP BusinessObjects HR Rapid Mart XI 3.2 for SAP solutions User Guide 3

Contents

SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Benefit Enrollment Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

Employee Wage Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Payroll Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60SAP solutions processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Rapid Mart processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Rapid Mart data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Chapter 4 Reports 67Employee Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Leave Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Benefit Enrollment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Employee Wage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

Payroll . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Recommended Table Joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

SAP Master Data Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

4 SAP BusinessObjects HR Rapid Mart XI 3.2 for SAP solutions User Guide

Contents

Data Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Data Auditing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Recommended table joins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145

Chapter 5 Universe 149Universe Design Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

Universe Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Universe Table Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Join Strategy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Hierarchies Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Geographic Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Time Dimension and Fiscal Period Hierarchies . . . . . . . . . . . . . . . . . 158Material Product Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Horizontal & Vertical Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Hierarchy Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Human Resources Specific Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . 170Accounting Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Additional Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

SAP Human Resources Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Universe Design Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Common Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Employee Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Employee Wage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Benefit Enrollment Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Benefit Enrollment Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Leave Entitlement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Payroll Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Payroll Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Filters & Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Sample Measures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209


Contents

Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210SAP HR Master Data Universe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Universe Objects & Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213Universe Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Infotype Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Filters & Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Universe Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Universe Objects & Classes - Master Data . . . . . . . . . . . . . . . . . . . . . 220Universe Validation - Master Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Splitting the SAP Human Resources Universe . . . . . . . . . . . . . . . . . . 257

Chapter 6 Installing the Rapid Mart 259Preparing Data Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265Preparing Target Database Environment . . . . . . . . . . . . . . . . . . . . . . 265Preparing Source Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Preparing BusinessObjects Enterprise . . . . . . . . . . . . . . . . . . . . . . . . 266Performance Tuning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266Create Target Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269Renaming the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272Import ATL File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274Adjusting the Data Stores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276Using Auxiliary Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283Using ABAP Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284Final Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288Import Wizard for Reporting Content BIAR File . . . . . . . . . . . . . . . . . 290Creating Universe Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Chapter 7 Using the Rapid Mart 311Recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

Data Services automatic recovery feature . . . . . . . . . . . . . . . . . . . . . 312Rapid Mart recovery framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Execution status framework . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314


Contents

The execution status table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314The execution status API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315Executing a job with the Reset option . . . . . . . . . . . . . . . . . . . . . . . . 316

Extraction, transformation and loading process . . . . . . . . . . . . . . . . . . . . 316Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318

Global Variable Cross-Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . 318Used in All Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322Used in 2 to 10 Rapid Marts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325Used in Only 1 Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331Setting Global Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Executing the job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Initial (First) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349Incremental (Delta) Extraction and Load . . . . . . . . . . . . . . . . . . . . . . 350

Customizing the Rapid Mart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

Chapter 8 Customizing the Rapid Mart 353Payroll Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354

Changing the Identification Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354Include All Wage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356Adding Additional Wage Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358Changing the Payroll Structure and Cluster Table . . . . . . . . . . . . . . . 362

Leave Entitlement Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Extract New Infotype PA0261 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369Modify Leave Entitlement to use PA0261 . . . . . . . . . . . . . . . . . . . . . 370

Function Calls in Custom ABAP Transforms . . . . . . . . . . . . . . . . . . . . . . 371PA0167 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371Differences Between PA0167 & PA0168 . . . . . . . . . . . . . . . . . . . . . . 376

Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

Chapter 9 Technical Implementation 377Common Transformations for Date Effective Sections . . . . . . . . . . . . . . 378

Incremental Load Challenges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 379Dimensions With Surrogate Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . 379


Contents

Minimum Date Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382Dimension Valid Date Range Driver . . . . . . . . . . . . . . . . . . . . . . . . . . 383Fact Valid Date Range Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384Vertical and Horizontal Fact Organization . . . . . . . . . . . . . . . . . . . . . . 389

Infotypes Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392Infotype Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394Initial (First) and Incremental (Delta) Loads . . . . . . . . . . . . . . . . . . . . 395Infotypes 0167 (Health) and 0168 (Insurance) . . . . . . . . . . . . . . . . . . 395Infotype 0008 (Pay History) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

Employee Administration Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397Leave Entitlement Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403

Leave Deduction Dimension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405Leave Entitlement Fact . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

Benefit Enrollment Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407Employee Wage Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413Payroll Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

Initial (First) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421Incremental (Delta) Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

Optimization Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422Table Partitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423Data Transfer Transform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424Hierarchy Optimizations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426

Dealing with NULL values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 428Fact Table Stored Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430Fiscal Periods & Time Dim Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

Chapter 10 Documentation References 433Data Services Documentation References . . . . . . . . . . . . . . . . . . . . . . . . 434BusinessObjects Enterprise Documentation References . . . . . . . . . . . . . 434

Appendix A Rapid Mart Data Schema 437


Introduction

chapter

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

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

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

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


IntroductionWhat is a Rapid Mart? 1

BI tools and analytic tools can access Rapid Mart data through SQL queries. Rapid Marts can be implemented individually, or in any combination, to form a single platform that delivers the infrastructure for your company’s internal and external information needs. They can also serve as a staging area for enterprise analytic applications.Rapid Marts provide your business with an accelerated time to value through rapid BI deployments because you can implement them quickly and easily customize them to meet specific analytic requirements.

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

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

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

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

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

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

solutionsHuman Capital Management (HCM) Suite:• SAP BusinessObjects HR Rapid Mart, version for SAP solutionsYou 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.


IntroductionWhat is a Rapid Mart?1
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:• Data Movement Jobs - packaged source-to-target mappings and data

transformations. Each job is designed to perform initial and incremental data movement;


IntroductionAbout this document 1

• 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 documentThis document describes the SAP BusinessObjects HR 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.• Chapter 6: Installing the Rapid Mart — Contains the information you need

to install the Rapid Mart


IntroductionAbout this document1

• 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: Customizing the Rapid Mart — Describes customization challenges unique to the HR Rapid Mart.

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

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

• Appendix A: Rapid Mart Data Schema — Contains a detailed list of the tables and views in the Rapid Mart


Overview

chapter

OverviewOverview2
Overview
This chapter describes the business questions you can answer with the SAP BusinessObjects HR 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• Schema

What you can do with this Rapid MartThe SAP BusinessObjects HR Rapid Mart, version for SAP solutions supports analysis of benefits, payroll and other employment related information. Some of the information in Human Resources may be sensitive and appropriate access controls must be exercised. Analysis of Human Resources helps one to better understand the personnel development and compensation programs within the company. The SAP solutions HR Module is very flexible, allowing customers around the globe to implement Human Resources according to the rules of their own particular jurisdiction. The SAP BusinessObjects HR Rapid Mart, version for SAP solutions is a flexible template that allows you to customize and localize your Human Resources reporting in according to the same rules.All Rapid Marts are flexible templates that you can customize for your particular needs. This is especially valuable in the HR Rapid Mart. Human Resources reporting requirements vary greatly from country to country. Each jurisdiction has its own regulatory requirements. The SAP BusinessObjects HR Rapid Mart, version for SAP solutions is made up of several componentized sections (also called subject areas). Each section supports a subject related to human resources management. The subject areas are presented as U.S. regulatory specific templates that can be customized and localized for other countries and jurisdictions.• Infotypes: The SAP solutions infotypes (tables PA0000, PA0001,

PA0002, etc.) are used throughout the following sections. They are presented here as they appear in SAP solutions, with minimal


OverviewSupported analyses 2

transformations. These can provide additional analyses not covered elsewhere in the Rapid Mart. They also serve as a starting point for additional Rapid Mart customizations.

• Employee Administration: Helps to analyze personal and employment related information by employee or by organizational unit. This section addresses information such as age, length of service, annual salary, deadlines and other significant dates and directory of current employees. You can also analyze various employee demographics such as marital status, education, job qualifications, etc.

• Leave Entitlement: Helps analyze employee absences such as vacation, sick time, personal leave, maternity or paternity leave, etc. The section focuses on US leave entitlement. Modification of the Rapid Mart is required for other countries.

• Benefit Enrollment: Tracks the various fringe benefits of your employees. These include health care, pension, savings plans, and insurance plans. Enrollment and eligibility information can be analyzed from an employee of benefit plan perspective.

• Employee Wage: Tracks the salaries and wages you pay your employees. This includes pay rates, pay scales, job descriptions, positions, position hierarchies, and organizational hierarchies.

• Payroll: Assists in analyzing historical and current compensation paid by various wage types. Compensation amounts are summarized for easy analysis. This section is specific to US payroll. Modification of the Rapid Mart is required for other countries.

Chapter 3: Subject Areas discusses each of these sections in more detail and how to link them together for complete human resources information across several sections.

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

Business function Type of analysis Measures available in the Rapid Mart

Employee Administration Employee demographics Analyze employee length of service and demographics such as Marital Status, Education, Qualifications, Language Skills, etc.

Benefits Administration Benefit plan enrollment Weekly enrollment and eligibility statistics by benefit area, benefit group, benefit status, and plan


OverviewSupported analyses2

Employee benefits profile

Benefit plan coverage options by employee for health insurance, life insurance, spending accounts, savings plans, and credit plansChanges in employee benefits profiles over timeBenefits census summary by age, gender, marital status, length of service, location, or other demographic factors

Dependents Analysis Analysis of employee dependents covered by the various benefit plans.

Employee Benefit Costs Costing of Benefits by employee or employer contribution.

Compensation Wage and salary administration

Comparison of salary by job classification, position, organizational unit, pay scale groupSalary range penetration and compa-ratio by employee or selected groups of employees

Salary history Average increase in salary versus prior periodAverage length of time between salary increases

EEO comparable worth analysis

Comparison of salary based on position, ethnicity, gender, age, seniority, handicapped status or other EEO demographics

Payroll Employee pay history Gross-to-net pay by period using organizational hierarchies to drill down or roll up Cumulative to-date payroll results by month, quarter, and year

Organizational Planning Turnover analysis Terminations by length of serviceVacancy analysis Length of time to fill positionsHead count Drill down or roll up using organizational

hierarchiesEmployment Information Employee listing Current employee directory

Event tracking Employee event tracking and date/deadline reminders



OverviewRelated Rapid Marts 2

Dimensions available to support these analysesReporting dimensions available in the Rapid Mart include country, currency, company code, employee groups, personnel areas, payroll areas, pay scale areas, benefit areas, benefit groups, benefit plans and time-related dimensions such as fiscal period, calendar date, month and quarter.

Related Rapid MartsMost of the components in the SAP BusinessObjects HR Rapid Mart, version for SAP solutions are independent; very few components are shared with the other Rapid Marts. Dimensions used for analysis, such as currency, company code, time are shared with the other Rapid Marts. The country component in HR Rapid Mart is different from the country component used in the other Rapid Marts.

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.

Leave Entitlement Leave Accumulation & use

Track leave time accumulated by employees vs. time taken.

Infotype Analysis Infotypes “as found” in SAP solutions

All infotype fields for infotypes used in other sections of the Rapid Mart



OverviewSchema2

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.

SchemaThe following diagram shows an overview of the SAP BusinessObjects HR Rapid Mart, version for SAP solutions components and their relationships. The central column is the fact tables corresponding to componentized sections; the side columns indicate dimensional components that may apply to multiple sections. Additional diagrams show the SAP solutions Infotype records used, hierarchies, auxiliary, and stage tables. A few dimension tables are stand alone (not joined to a fact table). These are available for additional analyses in certain sections or subject areas.


OverviewSchema 2

Overview Schema (1 of 2):


OverviewSchema2

Overview Schema (2 of 2):


Subject Areas

chapter

Subject AreasOverview3
Overview
Each section in the SAP BusinessObjects HR Rapid Mart, version for SAP solutions pertains to a particular subject area. This chapter describes each section and the processes each section captures. The information in this chapter is useful for readers who use the Rapid Mart to design and support a real-time system, such as a Web application, and need to understand the data in the Rapid Mart and how it relates to SAP solutionsThis chapter discusses these subject areas: • Infotypes Section• Employee Administration Section • Organization Hierarchies Section• Leave Entitlement Section• Benefit Enrollment Section• Employee Wage Section• Payroll Section

Infotypes SectionThis subject area includes the infotype records used by the other sections in this chapter. Within the Data Services job for the HR Rapid Mart, the infotypes are extracted from SAP solutions before any other subject area. This is to ensure the infotype data is available for the transformations necessary in other subject areas.Note: This section is not organized as a star schema. The infotype tables are independent of each other and presented solely as master data.The infotypes are the basis for most of the fact tables in the Rapid Mart. They are presented here with minimal transformation as a deeper level of detail for Human Resources reporting.This section includes information about:• SAP solutions processing• Rapid Mart processing• Rapid Mart data


Subject AreasInfotypes Section 3

SAP solutions processingInfotypes are the core of the HR module in SAP solutions. They are date-range specific master data covering all types of employee information including:• Demographics• Dependents• Benefits• Wages• Taxes• Numerous Country Specific RequirementsTo satisfy the country specific requirements, there are several hundred infotype tables available in SAP solutions. The Data Services job extracts data only from those used to construct the fact tables for the Rapid Mart. Customization is required if other infotypes are used for reporting in your organization.Because they are date-range specific, correlation of information between the various infotype tables is challenging.Example: Employee dependent information will change when there is an event concerning members of an employee’s family such as birth of children, marriage, etc. However employee salary information will only change once a year with annual raises in salary. Thus, the dates of the changes in these two infotypes will rarely coincide.Chapter 9: Technical Implementation gives details on how the Rapid Mart combines data from the various infotypes with overlapping date ranges into a consolidated reporting environment.

Rapid Mart processingThe Rapid Mart extracts the following infotype tables with minimal transformations:

SAP solutions Source Table

Rapid Mart Target Table Description

PA0000 HR_INFOTYPE_0000_ACTION Employee Events records from Infotype PA0000

PA0001 HR_INFOTYPE_0001_ASSIGNMENT HR Master Data: Organizational Assignment from PA0001


Subject AreasInfotypes Section3

PA0002 HR_INFOTYPE_0002_PERSONAL HR master data - infotype PA0002 -- Personal data

PA0005 HR_INFOTYPE_0005_LEAVE HR master data from PA0005 infotype - Leave Entitlement;

PA0006 HR_INFOTYPE_0006_ADDRESS Load Personnel Address and Communications master data from PA0006, PA0105

PA0007 HR_INFOTYPE_0007_WORKTIME HR Master data: Planned Working Time from PA0007

PA0008 HR_INFOTYPE_0008_HISTORY Uses HR_INFOTYPE_0008_PAY to create a salary history that stores prior salary, and salary one year ago;

PA0008 HR_INFOTYPE_0008_PAY HR Master data - Basic Pay from PA0008

PA0014 HR_INFOTYPE_0014_DEDUCTION HR Master Data, Recurring Deductions from PA0014

PA0015 HR_INFOTYPE_0015_PAYMENT HR Master data: Infotype for additional payments, PA0015

PA0016 HR_INFOTYPE_0016_CONTRACT HR Master Data for Contract information from PA0016 infotype

PA0019 HR_INFOTYPE_0019_DATES HR Master data: Monitoring of Dates infotype from PA0019

PA0021 HR_INFOTYPE_0021_DEPENDENT HR master data - infotype PA0021 -- Dependents Personal data

PA0022 HR_INFOTYPE_0022_EDUCATION HR Master data: Education from Infotype PA0022

PA0024 HR_INFOTYPE_0024_QUALIFICATION HR infotype Master PA0024 - Personnel Qualifications

PA0041 HR_INFOTYPE_0041_SPEC HR Master: date specification inforecord PA0041

PA0077 HR_INFOTYPE_0077_PERSONAL HR Master for Additional Personal Data from PA0077

PA0094 HR_INFOTYPE_0094_RESIDENCE HR Master for Residence status in N/A from PA0094





Note: Table HR_INFOTYPE_VALIDATION: The table caries a validity flag (1 or 0). If there is more than one record valid at a time (overlapping date ranges) the record with the latest date range has validity flag = 1 and all other overlapping records have validity flag = 0. Records without ovelapping date ranges also have validity flag = 1. The table is used for loading Employee Administration and Benefit Enrollment subject areasNote: There are no associated dimensions as the infotypes are presented as master data.

PA0167 HR_INFOTYPE_0167_HEALTH HR Master: Health Plans from Infotype PA0167

PA0168 HR_INFOTYPE_0168_INSURANCE HR Master for Insurance Plans from infotype PA0168

PA0169 HR_INFOTYPE_0169_SAVINGS HR master data for Savings Plan from Infotype 0169

PA0170 HR_INFOTYPE_0170_FLEX HR Master data for Flexible Spending Accounts from infotype PA0170

PA0171 HR_INFOTYPE_0171_BENEFIT HR Master data for General Benefits from infotype PA0171

PA0236 HR_INFOTYPE_0236_CREDIT HR Master data for Credit Plans from infotype PA0236

HRP1000 HR_INFOTYPE_1000_DBTABLE HR Master data for Organizational unit descriptions from the active plan from HPR1000 infotype

HRP1001 HR_INFOTYPE_1001_DBTABLE HR master data - HR objects details from infotype HRP1001


N/A HR_INFOTYPE_VALIDATION Derived by Data Services Job: Distinct Merge of date-effective records from all infotypes




Measures
The infotype tables contain the following measure fields that can be used for data analyses:

Table Name Column Name Description

HR_INFOTYPE_0005_LEAVE

AMT_LEAVE_ACCOUNTED_01

PA0005.UAB01 Leave days accounted (Hours or Days)



PA0005.UAB02 Leave days accounted (Days or Hours)






PA0005.UAB04 Leave days accounted








AMT_LEAVE_ENTITLMNT_01

PA0005.UAN01 Leave entitlement (Hours or Days)



PA0005.UAN02 Leave entitlement (Days or Hours)













HR_INFOTYPE_0008_HISTORY

AMT_SALARY_YR PA0008.ANSAL Annual salary


AMT_SALARY_YR_AGO

HR_INFOTYPE_0008_PAY.AMT_SALARY_Y -Lookup annual salary on this day one year ago


AMT_SALARY_YR_PREV

HR_INFOTYPE_0008_PAY.AMT_SALARY_YR Previous salary lookup

HR_INFOTYPE_0008_PAY

AMT_PAYMNT_01 PA0008.BET01 Wage type 01 amount for payments






AMT_SALARY_YR PA0008.ANSAL Annual salary

HR_INFOTYPE_0014_DEDUCTION

AMT_PAYMNT PA0014.BETRG Amount of payment for the wage type

HR_INFOTYPE_0015_PAYMENT

AMT_PAYMNT PA0015.BETRG Amount

HR_INFOTYPE_0022_EDUCATION

AMT_COST PA0022.JBEZ1 Course fees

HR_INFOTYPE_0167_HEALTH

AMT_EMPLEE_COST Monthly Benefit Employee Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_EMPLEE_POST_TAX

Benefits Additional Employee Post-Tax Costs from Function HR_BEN_GET_PLAN_COST


AMT_EMPLER_COST_CREDIT

Benefit Employer Cost/Credit Amount from Function HR_BEN_GET_PLAN_COST


AMT_IMPUTED_INCOME

Benefits Imputed Income from Function HR_BEN_GET_PLAN_COST


AMT_PROVIDER_COST

Benefit Provider Cost Amount from Function HR_BEN_GET_PLAN_COST

HR_INFOTYPE_0168_INSURANCE

AMT_ALT_COVERAGE PA0168.COVOV - Benefit alternative amount for insurance coverage amount


AMT_BASIC_COVERAGE

Benefit Insurance Coverage Basic Amount from Function HR_BEN_EVAL_AMOUNT


AMT_BENFT_SALARY Annual Benefit Salary from Function HR_BEN_GET_PLAN_SALARY


AMT_COVERAGE PA0168.COVOV/ T74FC.COVAM- Coverage amount - Life only when Coverage Group is not defined. Calculated as a lookup on INSURANCE_COVERAGE_RULE


AMT_COVERAGE_MAX

T74FC.MAXAM - Maximum coverage amount. Calculated as a lookup on INSURANCE_COVERAGE_RULE




Rapid Mart dataThe following diagram shows the infotypes


AMT_EMPLEE_COST Monthly Benefit Employee Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_EMPLEE_POST_TAX



AMT_EMPLER_COST_CREDIT

Benefit Employer Cost/Credit Amount from Function HR_BEN_GET_PLAN_COST


AMT_IMPUTED_INCOME

Benefits Imputed Income from Function HR_BEN_GET_PLAN_COST


AMT_INSURANCE_COVERAGE

Benefit Insurance Coverage Amount from Function HR_BEN_CALC_COVERAGE_AMOUNT


AMT_PER_ADDTL_INSURANCE_UNIT

T74FC.ADDUN (via function HR_BEN_GET_RULE_COVERAGE) - Benefit Value of each Unit of Additional Insurance Coverage


AMT_PROVIDER_COST

Benefit Provider Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_SALARY_OVERRIDE

PA0168.SALOV- Benefits salary override

HR_INFOTYPE_0169_SAVINGS

AMT_PENSION_ADJUST

PA0169.PAAMT - Pension adjustment amount


AMT_POSTTAX_SAVNG

PA0169.PTAMT - Employee post-tax savings plan contribution amount


AMT_PRETAX_SAVNG PA0169.EEAMT Employees pre-tax saving contribution amount

HR_INFOTYPE_0170_FLEX

AMT_CONTRIBUTN_EMPLEE

PA0170.CAMNT - Employee contribution amount to spending account

HR_INFOTYPE_0236_CREDIT

AMT_CREDIT PA0236.CRAMO Employees actual credit amount




Infotypes Schema:

Typical queries:The infotypes are used to provide detailed analyses of information summarized in the fact tables (other subject ares). Typically this is a drill-down (or sub-query) into specific infotypes for a specific employees.Example: An Employee Listing report drills down to detail on Employee Actions (Infotype 0000), Employee Assignments (Infotype 0001), and Employee Pay (Infotype 0008).


Subject AreasEmployee Administration Section 3

Employee Administration SectionThe employee administration subject area of this Rapid Mart allows you to analyze information about employee attributes, such as age, length of service, and annual salary, and about employee events, such as deadlines and other significant dates. Additional analyses of employee demographics (age, marital status, education, qualifications, etc.) is also available.This section includes information about:• SAP solutions processing• Rapid Mart processing• Rapid Mart data


Subject AreasEmployee Administration Section3
SAP solutions processing
SAP solutions stores employee data in several Personnel Administration (PA-PAD) infotypes. Each infotype contains information that inter-related and is likely to change simultaneously. For example, information related to an employee’s home address and phone number is contained in a single infotype (PA0006). If an employee moves, both address and phone number are likely to change. But, if the move is the result of a transfer and promotion, information contained in other infotypes, such as salary (PA0008), will also change.Each record in an infotype has effective dates — a beginning date and an ending date. The ending date for the current record is always 12/31/9999. When you insert a new record in an infotype, SAP solutions delimits the date in the record that was current. In other words, SAP solutions updates the previously unspecified ending date (12/31/9999) with the correct ending date—the last date the old record is in effect. The new record has a beginning date that shows when the record becomes effective and an unspecified ending date (12/31/9999). Maintaining employee information in separate infotypes and delimiting infotypes as they change improves SAP solutions performance and reduces the volume of data required to keep current and historic information for all employee attributes. However, effective dates are not synchronized for different infotypes. Therefore, joining data inside SAP solutions from multiple infotypes for reporting purposes is difficult.

Rapid Mart processingThe Rapid Mart extracts data from the following SAP solutions infotypes:• PA0000 — Events • PA0001 — Organizational Assignment • PA0002 — Personal Data• PA0007 — Work Schedule • PA0008 — Basic Pay• PA0016 — Contract Elements• PA0019 — Date Monitoring• PA0022 — Education• PA0024 — Qualifications• PA0041 — Date Specifications• PA0077 — Additional Personal Data • PA0094 — Residency Status (North America)



• PA0169 — Savings Plans These tables are extracted without much transformation and are stored in holding tables. The holding tables are available for additional analyses in the Infotypes Section described later on in this chapter. These holding tables are used as sources to load the final Rapid Mart tables used for analysis.The target table is EMPLOYEE_ADMINISTRATION_FACT.This section also captures these dimensional attributes and their associated dimension tables

Attribute Name Dimension Tables

Benefit Area BENEFIT_AREABenefit Plan BENEFIT_PLANBenefit Program Group BENEFIT_PROGRAM_GROUPBenefit Termination Rule BENEFIT_TERMINATION_RULEBusiness Area BUSINESS_AREACertificate Type CERTIFICATE_TYPECompany Code COMPANY_CODEContribution Rule CONTRIBUTION_RULEControlling Area CONTROLLING_AREACost Center COST_CENTERCost Center Hierarchy COST_CENTER_HIER,

COST_CENTER_HIER_BAD, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR

Country Group & Status COUNTRY_GROUP, COUNTRY_GROUP_STATUS

Monetary Currency CURRENCYEducation Type EDUCATION_TYPEEligibility Rule ELIGIBILITY_RULEEmployee EMPLOYEEEmployee Group EMPLOYEE_GROUPEmployee Subgroup EMPLOYEE_SUBGROUPEthnic Origin ETHNIC_ORIGINGender GENDERHoliday Calendar & Work Calendar HOLIDAY_CALENDAR,

WORK_CALENDAR



Identification Type IDENTIFICATION_TYPEInsurance Coverage Rule INSURANCE_COVERAGE_RULEInvestment Group INVESTMENT_GROUPInvestment Plan INVESTMENT_PLANJob JOBLanguage LANGUAGEService Interval Hr SERVICE_INTERVAL_HRLine Manager Hierarchy LINE_MANAGER_HIERMarital Status MARITAL_STATUSMilitary Status MILITARY_STATUSNationality NATIONALITYOrganization Key ORGANIZATION_KEYOrganization Unit ORGANIZATION_UNITOrganization Unit Hierarchy ORGANIZATION_UNIT_HIER,

ORGANIZATION_UNIT_HIER_HZ, ORGANIZATION_UNIT_HIER_VR

Payroll Area PAYROLL_AREAPay Scale Area PAY_SCALE_AREAPay Scale Type PAY_SCALE_TYPEPersonnel Action Reason PERSONNEL_ACTION_REASONPersonnel Action Status PERSONNEL_ACTION_STATUSPersonnel Action Type PERSONNEL_ACTION_TYPEPersonnel Administrator PERSONNEL_ADMINISTRATORPersonnel Area PERSONNEL_AREAPersonnel Date Type PERSONNEL_DATE_TYPEPersonnel Subarea PERSONNEL_SUBAREAPersonnel Task Status PERSONNEL_TASK_STATUSPersonnel Task Type PERSONNEL_TASK_TYPEPosition POSITIONPosition Hierarchy POSITION_HIER,

POSITION_HIER_HZ, POSITION_HIER_VR




Fact table FieldsThe EMPLOYEE_ADMINISTRATION_FACT table contains the following measures:

Proficiency PROFICIENCYQualification QUALIFICATIONReligion RELIGIONResidence Status RESIDENCE_STATUSSalary Range SALARY_RANGESchool Type SCHOOL_TYPEStudy Branch STUDY_BRANCHTime Dimension TIME_DIM, TIME_DIM_WEEKLYTime Management Status TIME_MANAGEMENT_STATUSUnit Of Time UNIT_OF_TIMEVesting Rule VESTING_RULEWage Type WAGE_TYPEWork Contract WORK_CONTRACTWork Contract Type WORK_CONTRACT_TYPEWork Permit Type WORK_PERMIT_TYPE


Column Name Description

AMT_COST_EDUCATN PA0022.JBEZ1 Course feesAMT_PAYMNT_01 PA0008.BET01 Wage type 01

amount for paymentsAMT_PAYMNT_02 PA0008.BET02 Wage type 02

amount for paymentsAMT_PAYMNT_03 PA0008.BET03 Wage type 03

amount for paymentsAMT_PENSION_ADJUST PA0169.PAAMT - Pension

adjustment amountAMT_POSTTAX_SAVNG PA0169.PTAMT - Employee post-tax

savings plan contribution amountAMT_PRETAX_SAVNG PA0169.EEAMT Employees pre-tax

saving contribution amount



AMT_SALARY_YR PA0008.ANSAL Annual salaryAMT_SALARY_YR_PREV HR_INFOTYPE_0008_PAY.AMT_SA

LARY_YR Previous salary lookupCOUNT_BENEFIC_DEPENDNT Calculated number of savings plan

dependentsCOUNT_EMPLEE_SVC_INTERVAL_01

Count of Employees with length of service within Interval 1

COUNT_EMPLEE_SVC_INTERVAL_02










COUNT_EMPLEE_SVC_UNKNOWN

Count of Employees where length of service is not known (Employee Original Hire Date is missing).

HOURS_DAY PA0007.ARBST Daily working hoursHOURS_DAY_MAX PA0007.MAXTA Maximum number

of work hours per dayHOURS_DAY_MIN PA0007.MINTA Minimum number of

work hours per dayHOURS_MONTH PA0007.MOSTD Monthly hoursHOURS_MONTH_MAX PA0007.MAXMO Maximum number

of work hours per monthHOURS_MONTH_MIN PA0007.MINMO Minimum number of

work hours per monthHOURS_WEEK PA0007.WOSTD Weekly hoursHOURS_WEEK_MAX PA0007.MAXWO Maximum number

of work hours per weekHOURS_WEEK_MIN PA0007.MINWO Minimum weekly

working hours




Rapid Mart dataThe following diagram shows the employee administration section and the components used as dimensions and their associated hierarchies:Employee Administration Schema:

The universe (semantic layer) joins the organization unit and position hierarchies with the fact table to allow analyses of the demographics summarized by hierarchy levels.

HOURS_WORK PA0008.DIVGV Hours worked per accounting period

HOURS_YEAR PA0007.JRSTD Annual working hours

HOURS_YEAR_MAX PA0007.MAXJA Maximum number of work hours per year

HOURS_YEAR_MIN PA0007.MINJA Minimum number of work hours per year




You can analyze the data in this subject area along any of the dimensions or hierarchies listed above.Typical queries include:• What are the salary ranges by gender within each department?• List employees with more than three years in the company and with

annual salary less than $40,000?• What is the distribution of employees by age groups: below 20, between

21 and 40, and above 40 years old?• Are there any current employees qualified for the new opening in my

department?• Which employees have doctoral degree in the R&D Department?• What is the average tenure of salaried employees vs. hourly employees?• What is the employee head count within Sales and Marketing

organization shown as a hierarchy (organization chart)?• Which managers have more than ten people directly to reporting them?


Subject AreasOrganization Hierarchies Section 3

Organization Hierarchies SectionThe Organization Hierarchies of this Rapid Mart enables analysis of information in other sections within this Rapid Mart summarized at any level of the organization or position hierarchies. This chapter includes information about:• SAP solutions processing• Rapid Mart processing• Relationship to other sections• Rapid Mart data

SAP solutions processingUsing SAP solutions’s Personnel Development Organizational Management sub-module (PD-OM), Human Resources planners can build and maintain organizational structures that reflect the company’s current and planned work force. Organizational hierarchies show chain-of-command relationships between various entities within an enterprise. SAP solutions maintains other types of relationships for many different kinds of organizational entities.


Subject AreasOrganization Hierarchies Section3

The SAP BusinessObjects HR Rapid Mart, version for SAP solutions concentrates on the “reports to” relationship within the organizational unit and the employee position hierarchies. The following diagram shows an example of an organizational hierarchy that represents the Sales & Marketing division of a U.S. subsidiary. Each node is identified by an organizational unit ID.

Rapid Mart processingThe organization hierarchies are stored in these infotype tables:• HRP1000 table. It contains information about jobs, positions and

organizational units within the company. This is the source for the Position Hierarchy

• HRP1001 table. It contains the relationship between different levels within jobs, positions and organizational units. This is the source for the Organization Unit Hierarchy

These two tables are extracted as holding tables and from them the Rapid Mart tables in this section are extracted. They are also used to create the organizational dimensions used in this and other subject areas of the Rapid Mart


Subject AreasOrganization Hierarchies Section 3

Relationship to other sectionsThe hierarchies are presented as dimension tables used by other subject areas in the Rapid Mart. The hierarchies in this section can be used to analyze the data in the other sections based on position or organizational hierarchical levels.

Rapid Mart dataThe Rapid Mart represents the organization unit and position hierarchies in three tables each. Depending on the reporting requirements, one may be more suitable than the others.

Organization Unit Hierarchy• ORGANIZATION_UNIT_HIER — A direct mapping from the SAP

solutions organizational unit hierarchies• ORGANIZATION_UNIT_HIER_VR — A vertically flattened version of the

organizational unit hierarchies• ORGANIZATION_UNIT_HIER_HZ — A horizontally flattened version of

the organizational unit hierarchies.

Position Hierarchy• POSITION_HIER — A direct mapping from the SAP solutions position

hierarchies• POSITION_HIER_VR — A vertically flattened version of the position

hierarchies• POSITION_HIER_HZ — A horizontally flattened version of the position

hierarchiesFor information about SAP solutions hierarchies and hierarchy flattening methods used in the Rapid Mart, see the section on Hierarchies in Chapter 5: Universe.You can use data in this section to answer demands like:• Show the hierarchical employee head count within Sales and Marketing

organization• List employees who have more than ten people directly to reporting them.


Subject AreasLeave Entitlement Section3
Leave Entitlement Section
The leave entitlement subject area of this Rapid Mart allows you to analyze information about employee absences, such as vacations, sick leave, jury duty, maternity leave, etc. You can correlate accrued leave time vs. leave taken. You can also analyze the information by the organization, cost center, and position hierarchies.This section includes information about:• SAP solutions processing• Rapid Mart processing• Rapid Mart data

SAP solutions processingSAP solutions stores leave data in several Personnel Administration (PA-PAD) infotypes. Leave infotypes are like any other infotypes: they are effective date specific, and each may change independently of the others. The same challenges in extracting and reporting infotype information hold true for Leave Entitlement as other subject areas.

Rapid Mart processingThe Rapid Mart extracts data from the following SAP solutions infotypes:• PA0000 — Events • PA0001 — Organizational Assignment • PA0005 — Leave EntitlementThese tables are extracted without much transformation and are stored in holding tables. The holding tables are available for additional analyses in the Infotypes Section described later on in this chapter. These holding tables are used as sources to load the final Rapid Mart tables used for analysis.The target table is LEAVE_ENTITLEMENT_FACT.This section also captures these dimensional attributes and their associated dimension tables


Business Area BUSINESS_AREACompany Code COMPANY_CODEControlling Area CONTROLLING_AREA


Subject AreasLeave Entitlement Section 3

Cost Center COST_CENTERCost Center Hierarchy COST_CENTER_HIER,



Employee EMPLOYEEEmployee Group EMPLOYEE_GROUPEmployee Subgroup EMPLOYEE_SUBGROUPHoliday Calendar & Work Calendar HOLIDAY_CALENDAR,

WORK_CALENDARJob JOBLeave Deduction LEAVE_DEDUCTIONLeave Type LEAVE_TYPELine Manager Hier LINE_MANAGER_HIEROrganization Key ORGANIZATION_KEYOrganization Unit ORGANIZATION_UNITOrganization Unit Hierarchy ORGANIZATION_UNIT_HIER,


Payroll Area PAYROLL_AREAPersonnel Administrator PERSONNEL_ADMINISTRATORPersonnel Area PERSONNEL_AREAPersonnel Subarea PERSONNEL_SUBAREAPosition POSITIONPosition Hierarchy POSITION_HIER,


Time Dimension TIME_DIM, TIME_DIM_WEEKLYWork Contract WORK_CONTRACT



Subject AreasLeave Entitlement Section3
Fact table Fields
The LEAVE_ENTITLEMENT_FACT table contains the following measures. These detail the amounts of leave accrued:

The LEAVE_DEDUCTION stand alone dimension contains the following measures. These detail the amounts of leave taken:

Rapid Mart dataThe following diagram shows the employee administration section and the components used as dimensions and their associated hierarchies:


AMT_LEAVE_ACCOUNTED PA0005.UAB01-6 Leave days accounted (Hours or Days)

AMT_LEAVE_ENTITLMNT PA0005.UAN01- 6 Leave entitlement (Hours or Days) Leave type 01-06

COUNT_WRKDAY Calculated as count of number of working days from WORKING_CALENDAR dimension based on LEAVE_START_DATE and LEAVE_END_DATE

DAYS_LEAVE_DEDUCT PURLT.ANZH1 - Amount - Deducted Leave in Days

HOURS_LEAVE_DEDUCT PURLT.ANZHL - amount - Deducted leave in Hours


DAYS_LEAVE PURLT.ANZH1 - AmountHOURS_LEAVE PURLT.ANZHL - AmountLEAVE_YEAR PURLT.URLJJ - Leave year


Subject AreasBenefit Enrollment Section 3

Leave Entitlement Schema

You can analyze the data in this subject area along any of the dimensions or hierarchies listed above.Typical queries include:• How much productivity has been lost to sick days by cost center this

month?• Which employees have the highest accrued vacation?• Which employees take the most sick days?• Is absenteeism more prevalent in certain parts of the organization?• How many employees do not have enough vacation time to cover the

upcoming one week shutdown of the company?

Benefit Enrollment SectionWith the benefit enrollment section of this Rapid Mart, you can analyze information about the enrollment in and usage of company benefits. You can use the SAP BusinessObjects HR Rapid Mart, version for SAP solutions to analyze benefit plan enrollment from two perspectives. First, you can analyze enrollment from the employee perspective, listing plans and coverage options by employee personnel number. Second, you can analyze enrollment from


Subject AreasBenefit Enrollment Section3

the plan perspective, listing point-in-time statistics by plan and showing enrollment, eligibility, and other measures such as average number of beneficiaries.This section includes information about:• SAP solutions processing• Rapid Mart processing• Rapid Mart data

SAP solutions processingThe SAP solutions Personnel Benefits Administration (PA-Ben) sub-module stores information about each employee’s eligibility for and enrollment in various benefit plans. SAP solutions also stores information on plan options, cost, coverage, employee/employer contributions, dependent coverage, vesting rules, and investment options.Benefit infotypes are like any other infotypes: they are effective date specific, and each may change independently of the others. The same challenges in extracting and reporting infotype information hold true for Benefit Enrollment as other subject areas.Each benefits infotype contains a subtype field that divides the information into groups of related data. For example, the health plans infotype (PA0167) has subtypes for medical, dental, and vision plans.



SAP solutions uses time constraints to define and manage validity periods for time-dependent data. SAP solutions assigns the general benefits infotype to time constraint 1 and all other benefit infotypes to time constraint 2. In infotypes assigned time constraint 1, SAP solutions allows exactly one record to be valid for a given employee at a given time and permits no gaps and no overlaps. In infotypes assigned time constraint 2, SAP solutions allows gaps in time sequence but no overlaps. Therefore, in an infotype with time constraint 2, an employee may have no valid record at a given time, but will never have more than one valid record at a given time.

Rapid Mart processingSpecifically, the Rapid Mart extracts employee benefit information from these infotypes:• PA0001 — Organizational Assignment • PA0167 — Health plans• PA0168 — Insurance plans• PA0169 — Savings plans• PA0170 — Spending accounts (United States)• PA0171 — General benefits data• PA0236 — Credit plansThese tables are extracted without much transformation and are stored in holding tables. The holding tables are available for additional analyses in the Infotypes Section described later on in this chapter. These holding tables are used as sources to load the final Rapid Mart tables used for analysis.Employees who can enroll in plans must have a record in the general benefits data infotype (PA0171). This infotype contains the employee’s benefit group assignment, which determines plan options, cost, and eligibility criteria.The target tables are BENEFIT_ENROLLMENT_FACT, and BENEFIT_ENROLL_SUMMARY_FACT.This section also captures these dimensional attributes and their associated dimension tables:


Benefit Area BENEFIT_AREABenefit Cost Rule BENEFIT_COST_RULEBenefit Plan BENEFIT_PLANBenefit Program Group BENEFIT_PROGRAM_GROUPBenefit Spending Account BENEFIT_SPENDING_ACCOUNT



Benefit Termination Rule BENEFIT_TERMINATION_RULEBusiness Area BUSINESS_AREACompany Code COMPANY_CODEContribution Rule CONTRIBUTION_RULEControlling Area CONTROLLING_AREACost Center COST_CENTERCost Center Hierarchy COST_CENTER_HIER,


Country Group & Country Group Status

COUNTRY_GROUP, COUNTRY_GROUP_STATUS

Monetary Currency CURRENCYDependent Coverage DEPENDENT_COVERAGEEligibility Rule ELIGIBILITY_RULEEmployee EMPLOYEEEmployee Group EMPLOYEE_GROUPEmployee Subgroup EMPLOYEE_SUBGROUPEnrollment Type ENROLLMENT_TYPEHealth Plan HEALTH_PLANHoliday Calendar & Work Calendar HOLIDAY_CALENDAR,

WORK_CALENDARInsurance Coverage Group INSURANCE_COVERAGE_GROUPInsurance Coverage Rule INSURANCE_COVERAGE_RULEInsurance Option INSURANCE_OPTIONInvestment Group INVESTMENT_GROUPInvestment Plan INVESTMENT_PLANJob JOBLeave Deduction LEAVE_DEDUCTIONLine Manager Hierarchy LINE_MANAGER_HIEROrganization Key ORGANIZATION_KEYOrganization Unit ORGANIZATION_UNIT




Fact table FieldsThe BENEFIT_ENROLLMENT_FACT, and BENEFIT_ENROLL_SUMMARY_FACT tables contain the following measures:

Organization Unit Hierarchy ORGANIZATION_UNIT_HIER, ORGANIZATION_UNIT_HIER_HZ, ORGANIZATION_UNIT_HIER_VR

Payroll Area PAYROLL_AREAPersonnel Administrator PERSONNEL_ADMINISTRATORPersonnel Area PERSONNEL_AREAPersonnel Subarea PERSONNEL_SUBAREAPosition POSITIONPosition Hierarchy POSITION_HIER,


Time Dim, Time Dim Weekly TIME_DIM, TIME_DIM_WEEKLYVesting Rule VESTING_RULEWork Contract WORK_CONTRACT



BENEFIT_ENROLL_SUMMARY_FACT

AMT_BENFT_SALARY_AVG Average Annual Benefit Salary from Function HR_BEN_GET_PLAN_SALARY


AMT_BENFT_SALARY_MAX Max Annual Benefit Salary from Function HR_BEN_GET_PLAN_SALARY


AMT_CONTRIBUTN_EMPLEE_AVG

Average PA0170.CAMNT - Employee contribution amount to spending account OR Benefit Employee Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_CONTRIBUTN_EMPLEE_MAX

Max PA0170.CAMNT - Employee contribution amount to spending account OR Benefit Employee Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_COVERAGE_AVG Average PA0168.COVOV/ T74FC.COVAM- Coverage amount - Life only when Coverage Group is not defined. Calculated as a lookup on INSURANCE_COVERAGE_RULE


AMT_COVERAGE_MAX Average PA0168.COVOV/ T74FC.COVAM- Coverage amount - Life only when Coverage Group is not defined. Calculated as a lookup on INSURANCE_COVERAGE_RULE




AMT_EMPLEE_POSTTAX_INSUR_AVG

Average Benefits Additional Employee Post-Tax Costs from Function HR_BEN_GET_PLAN_COST


AMT_EMPLEE_POSTTAX_INSUR_MAX

Max Benefits Additional Employee Post-Tax Costs from Function HR_BEN_GET_PLAN_COST


AMT_EMPLEE_POSTX_HEALTH_AVG

Average Benefits Additional Employee Post-Tax Costs from Function HR_BEN_GET_PLAN_COST


AMT_EMPLEE_POSTX_HEALTH_MAX

Max Benefits Additional Employee Post-Tax Costs from Function HR_BEN_GET_PLAN_COST


AMT_EMPLER_COST_AVG Average Benefit Employer Cost/Credit Amount from Function HR_BEN_GET_PLAN_COST


AMT_EMPLER_COST_MAX Max Benefit Employer Cost/Credit Amount from Function HR_BEN_GET_PLAN_COST


AMT_IMPUTED_INCOME_AVG Average Benefits Imputed Income from Function HR_BEN_GET_PLAN_COST


AMT_IMPUTED_INCOME_MAX Max Benefits Imputed Income from Function HR_BEN_GET_PLAN_COST


AMT_INSUR_COVERAGE_AVG Average Benefit Insurance Coverage Amount from Function HR_BEN_CALC_COVERAGE_AMOUNT


AMT_INSUR_COVERAGE_MAX Max Benefit Insurance Coverage Amount from Function HR_BEN_CALC_COVERAGE_AMOUNT


AMT_PER_ADDTL_INSUR_UNIT_AVG

T74FC.ADDUN (via function HR_BEN_GET_RULE_COVERAGE) - Average Benefit Value of each Unit of Additional Insurance Coverage


AMT_PER_ADDTL_INSUR_UNIT_MAX

T74FC.ADDUN (via function HR_BEN_GET_RULE_COVERAGE) - Max Benefit Value of each Unit of Additional Insurance Coverage


AMT_POSTTAX_SAVNG_AVG Average PA0169.PTAMT - Employee post-tax savings plan contribution amount


AMT_POSTTAX_SAVNG_MAX Max PA0169.PTAMT - Employee post-tax savings plan contribution amount


AMT_PRETAX_SAVNG_AVG PA0169.EEAMT Average Employees pre-tax saving contribution amount


AMT_PRETAX_SAVNG_MAX PA0169.EEAMT Max Employees pre-tax saving contribution amount


AMT_PROVIDER_COST_AVG Average Benefit Provider Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_PROVIDER_COST_MAX Max Benefit Provider Cost Amount from Function HR_BEN_GET_PLAN_COST





COUNT_BENEFIC_DEPENDNT_AVG

Average Number of Dependents or beneficiaries listed on plan (from PA0168/0167/169/170/171/236)


COUNT_BENEFIC_DEPENDNT_MAX

Max number of dependents or beneficiaries (from PA0168/0167/169/170/171/236)


COUNT_BENEFIC_DEPENDNT_TTL

Total Number of Dependents or beneficiaries listed on plan (from PA0168/0167/169/170/171/236)


COUNT_EMPLEE_ENROLL Number of employees enrolled in plan - based on eligibility date and participation date.


PRCNT_POSTTAX_SAVNG_AVG Average PA1069.PTPCT - Employee post-tax saving plan contribution percentage


PRCNT_POSTTAX_SAVNG_MAX Max PA1069.PTPCT - Employee post-tax saving plan contribution percentage


PRCNT_PRETAX_SAVNG_AVG Average PA1069.EEPCT - Employees pre-tax savings plan contribution percentage


PRCNT_PRETAX_SAVNG_MAX Max PA1069.EEPCT - Employees pre-tax savings plan contribution percentage


QTY_ADDTL_INSUR_UNITS_AVG PA0168.ADDNO - Average Benefit Number of Additional Insurance Coverage Units


QTY_ADDTL_INSUR_UNITS_MAX PA0168.ADDNO - Max Benefit Number of Additional Insurance Coverage Units

BENEFIT_ENROLLMENT_FACT

AMT_ALT_COVERAGE PA0168.COVOV - Benefit alternative amount for insurance coverage amount


AMT_BASIC_COVERAGE Benefit Insurance Coverage Basic Amount from Function HR_BEN_EVAL_AMOUNT


AMT_BENFT_SALARY Annual Benefit Salary from Function HR_BEN_GET_PLAN_SALARY


AMT_CONTRIBUTN_EMPLEE PA0170.CAMNT - Employee contribution amount to spending account OR Benefit Employee Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_CONTRIBUTN_MAX T5UBG.RMAXA Maximum contribution to spending account (Lookup on table BENEFIT_SPENDING_ACCOUNT)


AMT_CONTRIBUTN_MIN T5UBG.RMINA Minimum contribution to spending account (Lookup on table BENEFIT_SPENDING_ACCOUNT)


AMT_COVERAGE PA0168.COVOV/ T74FC.COVAM- Coverage amount - Life only when Coverage Group is not defined. Calculated as a lookup on INSURANCE_COVERAGE_RULE


AMT_COVERAGE_MAX T74FC.MAXAM - Maximum coverage amount. Calculated as a lookup on INSURANCE_COVERAGE_RULE





AMT_CREDIT PA0236.CRAMO Employees actual credit amount


AMT_EMPLEE_POSTTAX_HEALTH Benefits Additional Employee Post-Tax Costs from Function HR_BEN_GET_PLAN_COST


AMT_EMPLEE_POSTTAX_INSURANCE



AMT_EMPLER_COST Benefit Employer Cost/Credit Amount from Function HR_BEN_GET_PLAN_COST


AMT_IMPUTED_INCOME Benefits Imputed Income from Function HR_BEN_GET_PLAN_COST


AMT_INSURANCE_COVERAGE Benefit Insurance Coverage Amount from Function HR_BEN_CALC_COVERAGE_AMOUNT


AMT_PENSION_ADJUST PA0169.PAAMT - Pension adjustment amount


AMT_PER_ADDTL_INSURANCE_UNIT

T74FC.ADDUN (via function HR_BEN_GET_RULE_COVERAGE) - Benefit Value of each Unit of Additional Insurance Coverage


AMT_POSTTAX_SAVNG PA0169.PTAMT - Employee post-tax savings plan contribution amount


AMT_PRETAX_SAVNG PA0169.EEAMT Employees pre-tax saving contribution amount


AMT_PROVIDER_COST Benefit Provider Cost Amount from Function HR_BEN_GET_PLAN_COST


AMT_SALARY_OVERRIDE PA0168.SALOV- Benefits salary override


PRCNT_INVESTMNT_01 PA0169.IPT01 Investment percentage










PRCNT_INVESTMNT_OTHER PA0169.ITP06-ITP20Remaining percent investment not covered by IPT1-5. Check SAP for remaining percentages


PRCNT_POSTTAX_SAVNG PA1069.PTPCT - Employee post-tax saving plan contribution percentage


PRCNT_PRETAX_SAVNG PA1069.EEPCT - Employees pre-tax savings plan contribution percentage




Rapid Mart dataThe following diagram shows the benefit enrollment section and the components used as dimensionsBenefit Enrollment Schema.

You can analyze the data in this subject area along any of the dimensions or hierarchies listed above. Typical queries that can be answered with this section include: • What percentage of employees opt for additional Life Insurance coverage

broken down by Organization Hierarchy?• What is the count of employees who enroll in 401(k) savings plans within

the Position hierarchy?• What is the employer’s cost for health care by cost center this fiscal year?


QTY_ADDTL_INSURANCE_UNITS PA0168.ADDNO - Benefit Number of Additional Insurance Coverage Units


RATE_SALARY_MULTIPLR T74FC.COVFA - Benefits factor for calculating insurance coverage base on Salary (Multiplier). Calculated as a lookup on INSURANCE_COVERAGE_RULE



Subject AreasEmployee Wage Section3

• How many employees do not have health care insurance?• Which health care insurance policy is most popular by Cost Center

hierarchy?

Employee Wage SectionThe employee wage section lets you correlate employee wage information (wage types, pay scales, etc.) with certain organizational aspects (position, organization, job, etc.). Payment amounts for each Wage Type are the key measure in this section. The key difference between the Employee Wage Section and the Payroll Section is that Employee Wages shows history of the gross wage or salary amounts from the perspective of your organization’s pay and deduction structures and internal set-up. The Payroll shows the actual payments generated from this internal setup. It records the actual payments made each payday to your employees. It includes information on deductions for taxes, various benefits, etc. The Payroll perspective is for external consumption by various government agencies as well as the employees themselves.This section includes information about:SAP solutions processingRapid Mart processingRapid Mart data

SAP solutions processingSAP solutions stores Wage data in several Personnel Administration (PA-PAD) infotypes. Wage infotypes are like any other infotypes: they are effective date specific, and each may change independently of the others. The same challenges in extracting and reporting infotype information hold true for Employee Wages as other subject areas.The SAP solutions personnel administration and payroll sub-module (PA-PAY) calculates gross compensation for each employee based on wage type payment structures. SAP solutions also uses wage types to calculate deductions in pay due to employee contributions, benefit plan costs, involuntary deductions, and taxes. There are two kinds of wage types: primary and secondary. Primary wage types are those entered as employee master data. Secondary wage types are those created by SAP solutions during a payroll run. Secondary wage types have a slash (/) prefix.


Subject AreasEmployee Wage Section 3

In SAP solutions, wage types have three fields: amount, rate, and number of units. When pay is a fixed amount, SAP solutions uses these fields individually to determine pay. When pay is time based, SAP solutions combines the fields to determine pay (that is, pay equals amount times rate times number of units). When SAP solutions computes pay based on table values stored elsewhere, these wage type fields may be left blank. Wage type valuation based on master data within the infotype is called direct valuation. Wage type valuation based on table lookups is called indirect valuation.

Rapid Mart processingThe Rapid Mart extracts data from the following SAP solutions infotypes:• PA0001 — Organizational Assignment • PA0008 — Basic Pay• PA0014 — Recurring benefits and deductions• PA0015 — Additional paymentsThese tables are extracted without much transformation and are stored in holding tables. The holding tables are available for additional analyses in the Infotypes Section described later on in this chapter. These holding tables are used as sources to load the final Rapid Mart tables used for analysis.The target table is EMPLOYEE_WAGE_FACT.This section also captures these dimensional attributes and their associated dimension tables:


Business Area BUSINESS_AREACompany Code COMPANY_CODEControlling Area CONTROLLING_AREACost Center COST_CENTERCost Center Hierarchy COST_CENTER_HIER,



Monetary Currency CURRENCYEmployee EMPLOYEEEmployee Group EMPLOYEE_GROUP


Subject AreasEmployee Wage Section3

Fact Table FieldsThe EMPLOYEE_WAGE_FACT table contains the following measures:

Employee Subgroup EMPLOYEE_SUBGROUPJob JOBLine Manager Hierarchy LINE_MANAGER_HIEROrganization Key ORGANIZATION_KEYOrganization Unit ORGANIZATION_UNITOrganization Unit Hierarchy ORGANIZATION_UNIT_HIER,


Payroll Area PAYROLL_AREAPay Scale Area PAY_SCALE_AREAPay Scale Type PAY_SCALE_TYPEPersonnel Administrator PERSONNEL_ADMINISTRATORPersonnel Area PERSONNEL_AREAPersonnel Subarea PERSONNEL_SUBAREAPosition POSITIONPosition Hierarchy POSITION_HIER,


Salary Range SALARY_RANGETime Dimension TIME_DIM, TIME_DIM_WEEKLYUnit Of Time UNIT_OF_TIMEWage Type WAGE_TYPEWork Contract WORK_CONTRACT



AMT_PAYMNT PA0014.BETRG Amount of payment for the wage typeQTY_UNIT PA0014.ANZHL an amount or number (and also a unit)

for wage type 01


Subject AreasEmployee Wage Section 3

Rapid Mart dataThe following diagram shows the Employee Wage section and the components used as dimensions and their associated hierarchies:Employee Wage Schema:

You can analyze the data in this subject area along any of the dimensions or hierarchies listed above.Typical queries include:• What is the monthly trend in net to gross pay ratio by employee group?• How many employees receive a housing allowance (wage type MA20)?• What is the count of employees by salary by cost center?• Who are the top 10 highest paid employees this year vs. last year?• What was the average hourly wage this year vs. last year?


Subject AreasPayroll Section3
Payroll Section
Using the employee payroll section of this Rapid Mart, you can analyze information about different wage types. Each payment or deduction in a paycheck is a wage type. Typically, a company’s payroll process calculates remuneration based on wage types and a country-specific set of rules. Companies cumulate wage types that represent individual payments or deductions to determine gross pay. Payment wage types include basic pay, bonuses, special pay, and so forth. Net pay calculations handle country-specific adjustments to gross pay. Adjustments and deductions may be voluntary, such as charitable contributions, or statutory, such as taxes. Finally, the payroll process combines results of previous payroll runs with the current results to get cumulative gross and net pay amounts.Note: The Payroll section is designed to meet U.S. payroll requirements. Customization of the Rapid Mart is required for other countries.The key difference between the Employee Wage Section and the Payroll Section is that Employee Wages shows history of the gross wage or salary amounts from the perspective of your organization’s pay and deduction structures and internal set-up. The Payroll shows the actual payments generated from this internal setup. It records the actual payments made each payday to your employees. It includes information on deductions for taxes, various benefits, etc. The Payroll perspective is for external consumption by various government agencies as well as the employees themselves.This section includes information about:• SAP solutions processing• Rapid Mart processing• Rapid Mart data

SAP solutions processingThe SAP solutions personnel administration and payroll sub-module (PA-PAY) calculates gross remuneration for each employee based on wage type payment structures. SAP solutions also uses wage types to calculate deductions in pay due to employee contributions, benefit plan costs, involuntary deductions, and taxes. There are two kinds of wage types: primary and secondary. Primary wage types are those entered as employee master data. Secondary wage types are those created by SAP solutions during a payroll run. Secondary wage types have a slash (/) prefix.


Subject AreasPayroll Section 3

In SAP solutions, wage types have three fields: amount, rate, and number of units. When pay is a fixed amount, SAP solutions uses these fields individually to determine pay. When pay is time based, SAP solutions combines the fields to determine pay (that is, pay equals amount times rate times number of units). When SAP solutions computes pay based on table values stored elsewhere, these wage type fields may be left blank. Wage type valuation based on master data within the infotype is called direct valuation. Wage type valuation based on table lookups is called indirect valuation.The payroll process uses primary wage types as input and generates secondary wage types as output.

SAP solutions stores payroll results in data structures called PCL clusters. Clusters are grouped based on a relation ID (RELID). SAP solutions stores payroll accounting results in PCL2 clusters. Individual country payroll results are grouped according to relation id “Rn” where n refers to a human resources country indicator. The default version of the SAP BusinessObjects HR Rapid Mart, version for SAP solutions supports relation id “RU,” where “U” refers to the United States.

Primary wage types used as input Secondary wage types created as output

M001 – Hourly Rate /101 – Total Gross PayMM01 – Basic Overtime /401 – Withholding TaxD240 – Life Insurance Deduction /110 – Employee Deductions



SAP solutions assigns a sequence number to each employee in the payroll accounting results. The sequence number is associated with a payroll period and depends on the pay frequency of the employee. Each payroll period is associated with three dates:• For period —Indicates the period for which the pay applies• In period — Indicates the period in which the payroll run occurred• Actual date — Indicates the payroll dateRetroactive changes to master data can affect prior payroll calculations. When retroactive changes occur, SAP solutions recalculates payroll and cumulative payroll results to reflect the changes.

Rapid Mart processingThe Rapid Mart extracts payroll data from three SAP solutions payroll cluster tables:• PC207 — Payroll results table• PC22Y — Payroll cumulated results table (USA)• PC261 — Cluster directory for import and export of payroll resultsThe target tables are PAYROLL_FACT and PAYROLL_SUMMARY_FACT.This section also captures these dimensional attributes and their associated dimension tables:


Business Area BUSINESS_AREACompany Code COMPANY_CODEControlling Area CONTROLLING_AREACost Center COST_CENTERCost Center Hierarchy COST_CENTER_HIER,



Monetary Currency CURRENCYEmployee EMPLOYEEEmployee Group EMPLOYEE_GROUPEmployee Subgroup EMPLOYEE_SUBGROUP



Fact Table FieldsThe PAYROLL_FACT and PAYROLL_SUMMARY_FACT tables contain the following measures:

Job JOBLine Manager Hierarchy LINE_MANAGER_HIEROrganization Key ORGANIZATION_KEYOrganization Unit ORGANIZATION_UNITOrganization Unit Hierarchy ORGANIZATION_UNIT_HIER,


Payroll Area PAYROLL_AREAPayroll Cumulation Type PAYROLL_CUMULATION_TYPEPayroll Period PAYROLL_PERIODPayroll Period Parameter PAYROLL_PERIOD_PARAMETERPayroll Status PAYROLL_STATUSPayroll Type PAYROLL_TYPEPersonnel Administrator PERSONNEL_ADMINISTRATORPersonnel Area PERSONNEL_AREAPersonnel Subarea PERSONNEL_SUBAREAPosition POSITIONPosition Hierarchy POSITION_HIER,


Time Dimension TIME_DIM, TIME_DIM_WEEKLYUnit Of Time UNIT_OF_TIMEWage Type WAGE_TYPEWork Contract WORK_CONTRACT



PAYROLL_FACT AMT_PAYROLL PC207.BETRG - Payroll AmountPAYROLL_FACT NUM_OF_UNITS PC207.ANZHL - HR payroll: Number - used for non-

pay wage types such as absences



PAYROLL_SUMMARY_FACT

AMT_PAYROLL PC22Y.BETRG - Period-to-date payroll amount


NUM_OF_UNITS PC22Y.ANZHL - Number of units in cumulative payroll amount




Rapid Mart dataThe following diagram shows the payroll section and the components used as dimensionsPayroll Schema.

You can analyze the data in this subject area along any of the dimensions or hierarchies listed above.Typical queries include:• What is the monthly trend in net to gross pay ratio by employee group?• How many employees receive a housing allowance (wage type MA20)?• What is the count of employees by salary by cost center?• Who are the top 10 highest paid employees this year vs. last year?• What was the average hourly wage this year vs. last year?Example:


Reports

chapter

ReportsOverview4
Overview
You can use the SAP BusinessObjects HR 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:• Employee Administration• Leave Entitlement• Benefit Enrollment• Employee Wage• PayrollYou can use the SAP BusinessObjects HR 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.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".

Employee AdministrationThe employee administration subject area of this Rapid Mart allows you to analyze information about employee attributes, such as age, length of service, and annual salary, and about employee events, such as deadlines and other significant dates.

ReportsEmployee administration allows for a variety of detail, trend, and high level analysis. Below is a list of the reports included here for analysis:• Employee Listing• Company Employee Analysis• Employee 360 Overview• Employee Change History (Valid Between Dates)


ReportsEmployee Administration 4

• Employee 360 Snapshot (As Of)

Employee Listing View employee listing for the selected Company Code and Personnel Area. Includes a hyperlink on Person Id to view Employee 360 Overview.

Listing by Personnel SubareaView employee listing by Personnel Subarea.

Listing by Org UnitView employee listing by Org Unit.


ReportsEmployee Administration4

Top 10 Years of ServiceView Top 10 employees (based on years of service) for each personnel subarea.

Calculations• TTL Years of Service = [Years Of Service]

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

Company Employee Analysis View Company statistics for a selected Company Code and Personnel Area (all time vs. point in time) for Head Count, Turnover, New Hires, and Length of Service. Includes a hyperlink in the report header to view Employee Listing.



SummaryView company employee counts for each Personnel Subarea for the Current Date compared to the prompted As Of Date.



Length of ServiceView employee length of service by interval (0-6 mo., > 6 mo. <= 1yr, > 1 yr. <= 3 yrs., etc.). Results are shown by employee count in each interval.

Calculations• % New Hires (All To Date) = If([EMPL ADMIN - Num Current Employees]

<> 0; [EMPL ADMIN - Num New Hires]/[EMPL ADMIN - Num Current Employees]; 0)

• % New Hires (Point in Time) = If([EMPL ADMIN - Num (Point in Time) Employees] <> 0; [EMPL ADMIN - Num (Point in Time) New Hires]/[EMPL ADMIN - Num (Point in Time) Employees]; 0)



• % Staff Growth (All To Date) = If([EMPL ADMIN - Num Current Employees] <> 0; ([EMPL ADMIN - Num New Hires]-[EMPL ADMIN - Num Terminated Employees])/[EMPL ADMIN - Num Current Employees]; 0)

• % Staff Growth (Point in Time) = If([EMPL ADMIN - Num (Point in Time) Employees] <> 0; ([EMPL ADMIN - Num (Point in Time) New Hires]-[EMPL ADMIN - Num (Point in Time) Terminated Employees])/[EMPL ADMIN - Num (Point in Time) Employees]; 0)

• % Terminates (All To Date) = If([EMPL ADMIN - Num Current Employees] <> 0; [EMPL ADMIN - Num Terminated Employees]/[EMPL ADMIN - Num Current Employees]; 0)

• % Terminates (Point in Time) = If([EMPL ADMIN - Num (Point in Time) Employees] <> 0; [EMPL ADMIN - Num (Point in Time) Terminated Employees]/[EMPL ADMIN - Num (Point in Time) Employees]; 0)

• As Of Date = ToDate(Left([UR Point In Time Date];Pos([UR Point In Time Date]; " ")-1); "MM/dd/yyyy")

• Current Date = CurrentDate()


Employee 360 Overview View current Employee administration information (no filter is set on Valid To and Valid From dates). Detailed information is also included for employee actions, organizational assignment changes, and basic pay. Includes hyperlinks (in the report header) to related reports, including:• Employee Listing• Employee Wage History• Benefits Participation Details



Employee DetailsView employee information as well as detailed information about employee actions and organizational assignment changes.



CompensationView employee information as well as full history of basic pay changes.




Employee Change History (Valid Between Dates)
View Employee administration information between Valid To and Valid From dates. Detailed information is also included for employee actions, organizational assignment changes, and basic pay.







Employee 360 Snapshot (As Of) View Employee administration information as of the selected date. Detailed information is also included for employee actions, organizational assignment changes, and basic pay.





CalculationsTTL Years of Service = [Years Of Service]


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

Fact Table Dimension Table Join Expression

EMPLOYEE_ADMINISTRATION_FACT

BENEFIT_AREA BENEFIT_AREA.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID


BENEFIT_PLAN EMPLOYEE_ADMINISTRATION_FACT.BENFT_PLAN_KEY = BENEFIT_PLAN.BENFT_PLAN_KEY




BENEFIT_PROGRAM_GROUP

BENEFIT_PROGRAM_GROUP.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID and BENEFIT_PROGRAM_GROUP.PROGRAM_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.PROGRAM_GRP_ID_01 and BENEFIT_PROGRAM_GROUP.PROGRAM_CODE = '01'



BENEFIT_PROGRAM_GROUP.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID and BENEFIT_PROGRAM_GROUP.PROGRAM_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.PROGRAM_GRP_ID_02 and BENEFIT_PROGRAM_GROUP.PROGRAM_CODE = '02'


BENEFIT_TERMINATION_RULE

BENEFIT_TERMINATION_RULE.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID AND BENEFIT_TERMINATION_RULE.TERMINATN_RULE_ID = EMPLOYEE_ADMINISTRATION_FACT.TERMINATN_RULE_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BUS_AREA_ID


CERTIFICATE_TYPE CERTIFICATE_TYPE.CERTIFICATE_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.CERTIFICATE_TYPE_ID


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = EMPLOYEE_ADMINISTRATION_FACT.CMPNY_CODE_ID





CONTRIBUTION_RULE

CONTRIBUTION_RULE.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID and CONTRIBUTION_RULE.BENFT_PLAN_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_PLAN_ID and CONTRIBUTION_RULE.CONTRIBTN_RULE_ID = EMPLOYEE_ADMINISTRATION_FACT.CONTRIBTN_RULE_ID_EMPLEE and CONTRIBUTION_RULE.CONTRIBTN_CODE = 'EMPLEE'


CONTRIBUTION_RULE

CONTRIBUTION_RULE.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID and CONTRIBUTION_RULE.BENFT_PLAN_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_PLAN_ID and CONTRIBUTION_RULE.CONTRIBTN_RULE_ID= EMPLOYEE_ADMINISTRATION_FACT.CONTRIBTN_RULE_ID_EMPLER and CONTRIBUTION_RULE.CONTRIBTN_CODE = 'EMPLER'


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.CTRL_AREA_ID


COST_CENTER COST_CENTER.CTRL_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = EMPLOYEE_ADMINISTRATION_FACT.COST_CNTR_ID


COST_CENTER_HIER_HZ

EMPLOYEE_ADMINISTRATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and EMPLOYEE_ADMINISTRATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID





COST_CENTER_HIER_VR

EMPLOYEE_ADMINISTRATION_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and EMPLOYEE_ADMINISTRATION_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


COUNTRY_GROUP COUNTRY_GROUP.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID


CURRENCY CURRENCY.CURR_ID = EMPLOYEE_ADMINISTRATION_FACT.CURR_ID


EDUCATION_TYPE EDUCATION_TYPE.EDUCATN_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.EDUCATN_TYPE_ID


ELIGIBILITY_RULE ELIGIBILITY_RULE.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID AND ELIGIBILITY_RULE.ELIGIBLTY_RULE_ID = EMPLOYEE_ADMINISTRATION_FACT.ELIGIBLTY_RULE_ID


EMPLOYEE EMPLOYEE.EMPLOYEE_KEY = EMPLOYEE_ADMINISTRATION_FACT.EMPLOYEE_KEY


EMPLOYEE_GROUP EMPLOYEE_GROUP.EMPLOYEE_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.EMPLOYEE_GRP_ID


EMPLOYEE_SUBGROUP

EMPLOYEE_SUBGROUP.EMPLOYEE_SUBGRP_ID = EMPLOYEE_ADMINISTRATION_FACT.EMPLOYEE_SUBGRP_ID


ETHNIC_ORIGIN ETHNIC_ORIGIN.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND ETHNIC_ORIGIN.ETHNIC_ORIGIN_ID = EMPLOYEE_ADMINISTRATION_FACT.ETHNIC_ORIGIN_ID





GENDER GENDER.GENDER_ID = EMPLOYEE_ADMINISTRATION_FACT.GENDER_ID


IDENTIFICATION_TYPE

IDENTIFICATION_TYPE.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND IDENTIFICATION_TYPE.IDENTIFICTN_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.IDENTIFICTN_TYPE_ID


INVESTMENT_GROUP INVESTMENT_GROUP.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID AND INVESTMENT_GROUP.INVESTMNT_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.INVESTMNT_GRP_ID


INVESTMENT_PLAN INVESTMENT_PLAN.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID AND INVESTMENT_PLAN.INVESTMNT_PLAN_ID = EMPLOYEE_ADMINISTRATION_FACT.INVESTMNT_PLAN_ID_01


JOB JOB.JOB_KEY = EMPLOYEE_ADMINISTRATION_FACT.JOB_KEY


LANGUAGE LANGUAGE.LANG_ID = EMPLOYEE_ADMINISTRATION_FACT.LANG_ID





LINE_MANAGER_HIER LINE_MANAGER_HIER.POSITION_ID = EMPLOYEE_ADMINISTRATION_FACT.POSITION_ID AND LINE_MANAGER_HIER.PERSON_ID = EMPLOYEE_ADMINISTRATION_FACT.PERSON_ID andLINE_MANAGER_HIER.VALID_FROM_DATE <= EMPLOYEE_ADMINISTRATION_FACT. VALID_FROM_DATE_POSTN andLINE_MANAGER_HIER.VALID_TO_DATE >= EMPLOYEE_ADMINISTRATION_FACT. VALID_TO_DATE_POSTN


MARITAL_STATUS EMPLOYEE_ADMINISTRATION_FACT.MARITAL_STATUS_ID = MARITAL_STATUS.MARITAL_STATUS_ID


MILITARY_STATUS MILITARY_STATUS.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND MILITARY_STATUS.MILITARY_STATUS_ID = EMPLOYEE_ADMINISTRATION_FACT.MILITARY_STATUS_ID


NATIONALITY EMPLOYEE_ADMINISTRATION_FACT.NATIONALITY_ID = NATIONALITY.NATIONALITY_ID


ORGANIZATION_KEY ORGANIZATION_KEY.ORG_KEY_ID = EMPLOYEE_ADMINISTRATION_FACT.ORG_KEY_ID


ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_KEY = EMPLOYEE_ADMINISTRATION_FACT.ORG_UNIT_KEY


ORGANIZATION_UNIT_HIER_HZ

ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY = EMPLOYEE_ADMINISTRATION_FACT.ORG_UNIT_KEY





ORGANIZATION_UNIT_HIER_VR

EMPLOYEE_ADMINISTRATION_FACT.ORG_UNIT_KEY = ORGANIZATION_UNIT_HIER_VR.CHILD_KEY


PAY_SCALE_AREA PAY_SCALE_AREA.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND PAY_SCALE_AREA.PAY_SCALE_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.PAY_SCALE_AREA_ID


PAY_SCALE_TYPE PAY_SCALE_TYPE.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND PAY_SCALE_TYPE.PAY_SCALE_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.PAY_SCALE_TYPE_ID


PAYROLL_AREA PAYROLL_AREA.PAYROLL_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.PAYROLL_AREA_ID


PERSONNEL_ACTION_REASON

PERSONNEL_ACTION_REASON.ACTION_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.ACTION_TYPE_ID AND PERSONNEL_ACTION_REASON.ACTION_REASON_ID = EMPLOYEE_ADMINISTRATION_FACT.ACTION_REASON_ID


PERSONNEL_ACTION_STATUS

PERSONNEL_ACTION_STATUS.STATUS_CATEG_ID = EMPLOYEE_ADMINISTRATION_FACT.STATUS_CATEG_ID_EMPLMNT AND PERSONNEL_ACTION_STATUS.STATUS_ID = EMPLOYEE_ADMINISTRATION_FACT.STATUS_ID_EMPLMNT


PERSONNEL_ACTION_TYPE

EMPLOYEE_ADMINISTRATION_FACT.ACTION_TYPE_ID = PERSONNEL_ACTION_TYPE.ACTION_TYPE_ID





PERSONNEL_ADMINISTRATOR

PERSONNEL_ADMINISTRATOR.ADMIN_GRP_CODE = EMPLOYEE_ADMINISTRATION_FACT.ADMIN_GRP_CODE AND PERSONNEL_ADMINISTRATOR.ADMIN_ID = EMPLOYEE_ADMINISTRATION_FACT.ADMIN_ID_HR


PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.PERSONNEL_AREA_ID


PERSONNEL_DATE_TYPE

EMPLOYEE_ADMINISTRATION_FACT.DATE_TYPE_ID_01 = PERSONNEL_DATE_TYPE.DATE_TYPE_ID


PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.PERSONNEL_AREA_ID AND PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID = EMPLOYEE_ADMINISTRATION_FACT.PERSONNEL_SUBAREA_ID


PERSONNEL_TASK_STATUS

PERSONNEL_TASK_STATUS.TASK_STATUS_ID = EMPLOYEE_ADMINISTRATION_FACT.TASK_STATUS_ID


PERSONNEL_TASK_TYPE

PERSONNEL_TASK_TYPE.TASK_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.TASK_TYPE_ID


POSITION POSITION.POSITION_KEY = EMPLOYEE_ADMINISTRATION_FACT.POSITION_KEY


POSITION_HIER_HZ EMPLOYEE_ADMINISTRATION_FACT.POSITION_ID=POSITION_HIER_HZ.POSITION_ID


POSITION_HIER_VR EMPLOYEE_ADMINISTRATION_FACT.POSITION_ID=POSITION_HIER_VR.CHILD_ID





PROFICIENCY PROFICIENCY.PROFICIENCY_ID = EMPLOYEE_ADMINISTRATION_FACT.PROFICIENCY_ID


QUALIFICATION QUALIFICATION.QUALIFICTN_ID = EMPLOYEE_ADMINISTRATION_FACT.QUALIFICTN_ID


RELIGION RELIGION.RELIGION_ID = EMPLOYEE_ADMINISTRATION_FACT.RELIGION_ID


RESIDENCE_STATUS RESIDENCE_STATUS.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND RESIDENCE_STATUS.RESIDENCE_STATUS_ID = EMPLOYEE_ADMINISTRATION_FACT.RESIDENCE_STATUS_ID


SALARY_RANGE SALARY_RANGE.SALARY_RANGE_KEY = EMPLOYEE_ADMINISTRATION_FACT.SALARY_RANGE_KEY


SCHOOL_TYPE SCHOOL_TYPE.SCHOOL_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.SCHOOL_TYPE_ID


SERVICE_INTERVAL_HR

EMPLOYEE_ADMINISTRATION_FACT.SERVICE_INTERVAL_ID=SERVICE_INTERVAL_HR.SERVICE_INTERVAL_ID


STUDY_BRANCH STUDY_BRANCH.STUDY_BRANCH_ID = EMPLOYEE_ADMINISTRATION_FACT.STUDY_BRANCH_ID


TIME_DIM EMPLOYEE_ADMINISTRATION_FACT.ORIGINAL_HIRE_DATE = TIME_DIM.CALENDAR_DATE


TIME_MANAGEMENT_STATUS

TIME_MANAGEMENT_STATUS.TIME_MGMT_STATUS_ID = EMPLOYEE_ADMINISTRATION_FACT.TIME_MGMT_STATUS_ID


UNIT_OF_TIME UNIT_OF_TIME.UOT_ID = EMPLOYEE_ADMINISTRATION_FACT.UOT_ID_01



ReportsLeave Entitlement 4

Leave EntitlementThe leave entitlement subject area of this Rapid Mart allows you to analyze information about employee absences, such as vacations, sick leave, jury duty, maternity leave, etc.

ReportsLeave entitlement allows for a variety of detail, trend, and high level analysis. Below is a list of the reports included here for analysis:• Leave Entitlement Listing• Leave Entitlement Details


VESTING_RULE VESTING_RULE.BENFT_AREA_ID = EMPLOYEE_ADMINISTRATION_FACT.BENFT_AREA_ID AND VESTING_RULE.VESTNG_RULE_ID = EMPLOYEE_ADMINISTRATION_FACT.VESTNG_RULE_ID


WAGE_TYPE EMPLOYEE_ADMINISTRATION_FACT.WAGE_TYPE_KEY_01 = WAGE_TYPE.WAGE_TYPE_KEY


WORK_CONTRACT WORK_CONTRACT.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND WORK_CONTRACT.CONTRACT_ID = EMPLOYEE_ADMINISTRATION_FACT.CONTRACT_ID


WORK_CONTRACT_TYPE

WORK_CONTRACT_TYPE.CONTRACT_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.CONTRACT_TYPE_ID


WORK_PERMIT_TYPE WORK_PERMIT_TYPE.COUNTRY_GRP_ID = EMPLOYEE_ADMINISTRATION_FACT.COUNTRY_GRP_ID AND WORK_PERMIT_TYPE.WORK_PERMIT_TYPE_ID = EMPLOYEE_ADMINISTRATION_FACT.WORK_PERMIT_TYPE_ID



ReportsLeave Entitlement4
Leave Entitlement Listing
View listing of employee leave entitlement for the selected Company Code, Leave Year, As Of Date, and Personnel Area.


Leave Entitlement Details View employee leave entitlement details selected Employee, Company Code, Leave Year, As Of Date, and Personnel Area. Displays similar details as found in SAP Transaction PA20.



Calculations• SSN = Left([Identification Num];3)+" - "+Substr([Identification Num];4;2)+"

- "+Right([Identification Num];4)


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


LEAVE_ENTITLEMENT_FACT

BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID = LEAVE_ENTITLEMENT_FACT.BUS_AREA_ID


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = LEAVE_ENTITLEMENT_FACT.CMPNY_CODE_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = LEAVE_ENTITLEMENT_FACT.CTRL_AREA_ID


COST_CENTER COST_CENTER.CTRL_AREA_ID = LEAVE_ENTITLEMENT_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = LEAVE_ENTITLEMENT_FACT.COST_CNTR_ID


COST_CENTER_HIER_HZ

LEAVE_ENTITLEMENT_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and LEAVE_ENTITLEMENT_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

LEAVE_ENTITLEMENT_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and LEAVE_ENTITLEMENT_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


ReportsLeave Entitlement4


COUNTRY_GROUP COUNTRY_GROUP.COUNTRY_GRP_ID = LEAVE_ENTITLEMENT_FACT.COUNTRY_GRP_ID


EMPLOYEE EMPLOYEE.EMPLOYEE_KEY = LEAVE_ENTITLEMENT_FACT.EMPLOYEE_KEY


EMPLOYEE_GROUP EMPLOYEE_GROUP.EMPLOYEE_GRP_ID = LEAVE_ENTITLEMENT_FACT.EMPLOYEE_GRP_ID


EMPLOYEE_SUBGROUP

EMPLOYEE_SUBGROUP.EMPLOYEE_SUBGRP_ID = LEAVE_ENTITLEMENT_FACT.EMPLOYEE_SUBGRP_ID


JOB JOB.JOB_KEY = LEAVE_ENTITLEMENT_FACT.JOB_KEY


LEAVE_TYPE LEAVE_TYPE.LEAVE_TYPE_KEY = LEAVE_ENTITLEMENT_FACT.LEAVE_TYPE_KEY


LINE_MANAGER_HIER LINE_MANAGER_HIER.POSITION_ID = LEAVE_ENTITLEMENT_FACT.POSITION_ID AND LINE_MANAGER_HIER.PERSON_ID = LEAVE_ENTITLEMENT_FACT.PERSON_ID andLINE_MANAGER_HIER.VALID_FROM_DATE <= LEAVE_ENTITLEMENT_FACT. VALID_FROM_DATE_POSTN andLINE_MANAGER_HIER.VALID_TO_DATE >= LEAVE_ENTITLEMENT_FACT. VALID_TO_DATE_POSTN


ORGANIZATION_KEY ORGANIZATION_KEY.ORG_KEY_ID = LEAVE_ENTITLEMENT_FACT.ORG_KEY_ID


ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_KEY = LEAVE_ENTITLEMENT_FACT.ORG_UNIT_KEY






ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY = LEAVE_ENTITLEMENT_FACT.ORG_UNIT_KEY



LEAVE_ENTITLEMENT_FACT.ORG_UNIT_KEY = ORGANIZATION_UNIT_HIER_VR.CHILD_KEY


PAYROLL_AREA PAYROLL_AREA.PAYROLL_AREA_ID = LEAVE_ENTITLEMENT_FACT.PAYROLL_AREA_ID



PERSONNEL_ADMINISTRATOR.ADMIN_GRP_CODE = LEAVE_ENTITLEMENT_FACT.ADMIN_GRP_CODE AND PERSONNEL_ADMINISTRATOR.ADMIN_ID = LEAVE_ENTITLEMENT_FACT.ADMIN_ID_HR


PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID = LEAVE_ENTITLEMENT_FACT.PERSONNEL_AREA_ID


PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID = LEAVE_ENTITLEMENT_FACT.PERSONNEL_AREA_ID AND PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID = LEAVE_ENTITLEMENT_FACT.PERSONNEL_SUBAREA_ID


POSITION POSITION.POSITION_KEY = LEAVE_ENTITLEMENT_FACT.POSITION_KEY


POSITION_HIER_HZ LEAVE_ENTITLEMENT_FACT.POSITION_ID=POSITION_HIER_HZ.POSITION_ID



ReportsBenefit Enrollment4

Benefit EnrollmentWith the benefit enrollment section of this Rapid Mart, you can analyze information about employee enrollment and usage of company benefits.

ReportsBenefit enrollment allows for a variety of detail, trend, and high level analysis. Below is a list of the reports included here for analysis:• Benefits Participation• Benefits Participation Details• Benefit Enrollment Analysis

Benefits Participation View employee benefits participation costs/coverage summary and employee listing for the selected Benefit Area and time period. Replicates similar functionality to Human Resources Benefits Participation report HRBEN0072.


POSITION_HIER_VR LEAVE_ENTITLEMENT_FACT.POSITION_ID=POSITION_HIER_VR.CHILD_ID


WORK_CONTRACT WORK_CONTRACT.COUNTRY_GRP_ID = LEAVE_ENTITLEMENT_FACT.COUNTRY_GRP_ID AND WORK_CONTRACT.CONTRACT_ID = LEAVE_ENTITLEMENT_FACT.CONTRACT_ID



ReportsBenefit Enrollment 4

Costs & Coverage SummaryView breakdown of costs and coverage amounts by benefit plan.



ListingView benefits employee participation listing by Benefit Plan Type.

Calculations• Employee Participation Date = If(FormatDate([Participation Date]; "MM/

dd/yyyy") = [Null Date Text]; " "; FormatDate([Participation Date]; "MM/dd/yyyy"))

• Employee Valid From Date =If(FormatDate([Valid From Date - PK]; "MM/dd/yyyy") = [Null Date Text]; " "; FormatDate([Valid From Date - PK]; "MM/dd/yyyy"))

• Employee Valid To Date = If(FormatDate([Valid To Date - PK]; "MM/dd/yyyy") = [Null Date Text]; " "; FormatDate([Valid To Date - PK]; "MM/dd/yyyy"))

• Forever Date Text = "12/31/9999"• Null Date Text = "01/01/1900"


Benefits Participation Details View employee benefit plan details for the selected Person Id, Period Start, and Period End date. Employee dependent master data is also shown (although not linked to the benefit plans).



ParticipationView employee info, employee dependents, and in which benefit plans the employee participates (current and previous).



Costs and Coverage SummaryView employee’s benefit plan cost and coverage summary. In particular see detailed employee, employer, and provider costs; as well as, view employee insurance coverage amounts.

Calculations• Current Benefit = "Current Benefit Plan"• Employee Participation Date = If(FormatDate([Participation Date]; "MM/

dd/yyyy") = [Null Date Text]; " "; FormatDate([Participation Date]; "MM/dd/yyyy"))

• Employee Valid From Date = If(FormatDate([Valid From Date - PK]; "MM/dd/yyyy") = [Null Date Text]; " "; FormatDate([Valid From Date - PK]; "MM/dd/yyyy"))

• Employee Valid To Date = If(FormatDate([Valid To Date - PK]; "MM/dd/yyyy") = [Null Date Text]; " "; FormatDate([Valid To Date - PK]; "MM/dd/yyyy"))

• Empty String =""• Forever Date Text = "12/31/9999"• Null Date Text = "1/1/1900"• Previous Benefit = "Previous Benefit Plans"




Benefit Enrollment Analysis View Benefits Summary statistics and trend analysis for the selected Benefit Area and Calendar Year.

ParticipationView number of employees and dependents enrolled in each benefit plan.



CostsView average costs to employees, the employer, and the provider by benefit plan.



CoveragesView average coverage and insurance amounts by benefit plan.


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



BENEFIT_AREA BENEFIT_AREA.BENFT_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.BENFT_AREA_ID


BENEFIT_PLAN BENEFIT_ENROLL_SUMMARY_FACT.BENFT_PLAN_KEY = BENEFIT_PLAN.BENFT_PLAN_KEY





BENEFIT_PROGRAM_GROUP.BENFT_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.BENFT_AREA_ID and BENEFIT_PROGRAM_GROUP.PROGRAM_GRP_ID = BENEFIT_ENROLL_SUMMARY_FACT.PROGRAM_GRP_ID_01 and BENEFIT_PROGRAM_GROUP.PROGRAM_CODE = '01'



BENEFIT_PROGRAM_GROUP.BENFT_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.BENFT_AREA_ID and BENEFIT_PROGRAM_GROUP.PROGRAM_GRP_ID = BENEFIT_ENROLL_SUMMARY_FACT.PROGRAM_GRP_ID_02 and BENEFIT_PROGRAM_GROUP.PROGRAM_CODE = '02'



BENEFIT_TERMINATION_RULE.BENFT_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.BENFT_AREA_ID AND BENEFIT_TERMINATION_RULE.TERMINATN_RULE_ID = BENEFIT_ENROLL_SUMMARY_FACT.TERMINATN_RULE_ID


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = BENEFIT_ENROLL_SUMMARY_FACT.CMPNY_CODE_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.CTRL_AREA_ID


COST_CENTER COST_CENTER.CTRL_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = BENEFIT_ENROLL_SUMMARY_FACT.COST_CNTR_ID





COST_CENTER_HIER_HZ

BENEFIT_ENROLL_SUMMARY_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and BENEFIT_ENROLL_SUMMARY_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

BENEFIT_ENROLL_SUMMARY_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and BENEFIT_ENROLL_SUMMARY_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


CURRENCY CURRENCY.CURR_ID = BENEFIT_ENROLL_SUMMARY_FACT.CURR_ID


ELIGIBILITY_RULE ELIGIBILITY_RULE.BENFT_AREA_ID = BENEFIT_ENROLL_SUMMARY_FACT.BENFT_AREA_ID AND ELIGIBILITY_RULE.ELIGIBLTY_RULE_ID = BENEFIT_ENROLL_SUMMARY_FACT.ELIGIBLTY_RULE_ID


ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_KEY = BENEFIT_ENROLL_SUMMARY_FACT.ORG_UNIT_KEY



ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY = BENEFIT_ENROLL_SUMMARY_FACT.ORG_UNIT_KEY



BENEFIT_ENROLL_SUMMARY_FACT.ORG_UNIT_KEY = ORGANIZATION_UNIT_HIER_VR.CHILD_KEY


PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID=BENEFIT_ENROLL_SUMMARY_FACT.PERSONNEL_AREA_ID





PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID =BENEFIT_ENROLL_SUMMARY_FACT.PERSONNEL_AREA_ID and PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID =BENEFIT_ENROLL_SUMMARY_FACT.PERSONNEL_SUBAREA_ID


BENEFIT_AREA BENEFIT_AREA.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID


BENEFIT_PLAN BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_KEY = BENEFIT_PLAN.BENFT_PLAN_KEY



BENEFIT_PROGRAM_GROUP.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID and BENEFIT_PROGRAM_GROUP.PROGRAM_GRP_ID = BENEFIT_ENROLLMENT_FACT.PROGRAM_GRP_ID_01 and BENEFIT_PROGRAM_GROUP.PROGRAM_CODE = '01'



BENEFIT_PROGRAM_GROUP.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID and BENEFIT_PROGRAM_GROUP.PROGRAM_GRP_ID = BENEFIT_ENROLLMENT_FACT.PROGRAM_GRP_ID_02 and BENEFIT_PROGRAM_GROUP.PROGRAM_CODE = '02'


BENEFIT_SPENDING_ACCOUNT

BENEFIT_SPENDING_ACCOUNT.SPENDNG_ACCT_KEY = BENEFIT_ENROLLMENT_FACT.SPENDNG_ACCT_KEY






BENEFIT_TERMINATION_RULE.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND BENEFIT_TERMINATION_RULE.TERMINATN_RULE_ID = BENEFIT_ENROLLMENT_FACT.TERMINATN_RULE_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID = BENEFIT_ENROLLMENT_FACT.BUS_AREA_ID


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = BENEFIT_ENROLLMENT_FACT.CMPNY_CODE_ID


CONTRIBUTION_RULE

CONTRIBUTION_RULE.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID and CONTRIBUTION_RULE.BENFT_PLAN_ID = BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_ID and CONTRIBUTION_RULE.CONTRIBTN_RULE_ID = BENEFIT_ENROLLMENT_FACT.CONTRIBTN_RULE_ID_EMPLEE and CONTRIBUTION_RULE.CONTRIBTN_CODE = 'EMPLEE'


CONTRIBUTION_RULE

CONTRIBUTION_RULE.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID and CONTRIBUTION_RULE.BENFT_PLAN_ID = BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_ID and CONTRIBUTION_RULE.CONTRIBTN_RULE_ID = BENEFIT_ENROLLMENT_FACT.CONTRIBTN_RULE_ID_EMPLER and CONTRIBUTION_RULE.CONTRIBTN_CODE = 'EMPLER'





CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = BENEFIT_ENROLLMENT_FACT.CTRL_AREA_ID


COST_CENTER COST_CENTER.CTRL_AREA_ID = BENEFIT_ENROLLMENT_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = BENEFIT_ENROLLMENT_FACT.COST_CNTR_ID


COST_CENTER_HIER_HZ

BENEFIT_ENROLLMENT_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and BENEFIT_ENROLLMENT_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

BENEFIT_ENROLLMENT_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and BENEFIT_ENROLLMENT_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


COUNTRY_GROUP COUNTRY_GROUP.COUNTRY_GRP_ID = BENEFIT_ENROLLMENT_FACT.COUNTRY_GRP_ID


CURRENCY CURRENCY.CURR_ID = BENEFIT_ENROLLMENT_FACT.CURR_ID


DEPENDENT_COVERAGE

DEPENDENT_COVERAGE.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND DEPENDENT_COVERAGE.DEPENDNT_COVERAGE_ID = BENEFIT_ENROLLMENT_FACT.DEPENDNT_COVERAGE_ID





ELIGIBILITY_RULE ELIGIBILITY_RULE.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND ELIGIBILITY_RULE.ELIGIBLTY_RULE_ID = BENEFIT_ENROLLMENT_FACT.ELIGIBLTY_RULE_ID


EMPLOYEE EMPLOYEE.EMPLOYEE_KEY = BENEFIT_ENROLLMENT_FACT.EMPLOYEE_KEY


EMPLOYEE_GROUP EMPLOYEE_GROUP.EMPLOYEE_GRP_ID = BENEFIT_ENROLLMENT_FACT.EMPLOYEE_GRP_ID


EMPLOYEE_SUBGROUP

EMPLOYEE_SUBGROUP.EMPLOYEE_SUBGRP_ID = BENEFIT_ENROLLMENT_FACT.EMPLOYEE_SUBGRP_ID


ENROLLMENT_TYPE ENROLLMENT_TYPE.ENROLLMNT_TYPE_ID = BENEFIT_ENROLLMENT_FACT.ENROLLMNT_TYPE_ID


HEALTH_PLAN HEALTH_PLAN.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND HEALTH_PLAN.BENFT_PLAN_ID = BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_ID AND HEALTH_PLAN.HEALTH_PLAN_ID = BENEFIT_ENROLLMENT_FACT.HEALTH_PLAN_ID


INSURANCE_COVERAGE_GROUP

INSURANCE_COVERAGE_GROUP.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND INSURANCE_COVERAGE_GROUP.COVERAGE_GRP_ID = BENEFIT_ENROLLMENT_FACT.COVERAGE_GRP_ID





INSURANCE_OPTION INSURANCE_OPTION.INSURANCE_OPTION_KEY = BENEFIT_ENROLLMENT_FACT.INSURANCE_OPTION_KEY


INVESTMENT_GROUP INVESTMENT_GROUP.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND INVESTMENT_GROUP.INVESTMNT_GRP_ID = BENEFIT_ENROLLMENT_FACT.INVESTMNT_GRP_ID


INVESTMENT_PLAN INVESTMENT_PLAN.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND INVESTMENT_PLAN.INVESTMNT_PLAN_ID = BENEFIT_ENROLLMENT_FACT.INVESTMNT_PLAN_ID_01


JOB JOB.JOB_KEY = BENEFIT_ENROLLMENT_FACT.JOB_KEY


LINE_MANAGER_HIER LINE_MANAGER_HIER.POSITION_ID = BENEFIT_ENROLLMENT_FACT.POSITION_ID AND LINE_MANAGER_HIER.PERSON_ID = BENEFIT_ENROLLMENT_FACT.PERSON_ID andLINE_MANAGER_HIER.VALID_FROM_DATE <= BENEFIT_ENROLLMENT_FACT.VALID_FROM_DATE_POSTN andLINE_MANAGER_HIER.VALID_TO_DATE >= BENEFIT_ENROLLMENT_FACT. VALID_TO_DATE_POSTN


ORGANIZATION_KEY ORGANIZATION_KEY.ORG_KEY_ID = BENEFIT_ENROLLMENT_FACT.ORG_KEY_ID





ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_KEY = BENEFIT_ENROLLMENT_FACT.ORG_UNIT_KEY



ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY = BENEFIT_ENROLLMENT_FACT.ORG_UNIT_KEY



BENEFIT_ENROLLMENT_FACT.ORG_UNIT_KEY = ORGANIZATION_UNIT_HIER_VR.CHILD_KEY


PAYROLL_AREA PAYROLL_AREA.PAYROLL_AREA_ID = BENEFIT_ENROLLMENT_FACT.PAYROLL_AREA_ID



PERSONNEL_ADMINISTRATOR.ADMIN_GRP_CODE = BENEFIT_ENROLLMENT_FACT.ADMIN_GRP_CODE AND PERSONNEL_ADMINISTRATOR.ADMIN_ID = BENEFIT_ENROLLMENT_FACT.ADMIN_ID_HR


PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID = BENEFIT_ENROLLMENT_FACT.PERSONNEL_AREA_ID


PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID=BENEFIT_ENROLLMENT_FACT.PERSONNEL_AREA_ID


PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID =BENEFIT_ENROLLMENT_FACT.PERSONNEL_AREA_ID and PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID =BENEFIT_ENROLLMENT_FACT.PERSONNEL_SUBAREA_ID


POSITION POSITION.POSITION_KEY = BENEFIT_ENROLLMENT_FACT.POSITION_KEY



ReportsEmployee Wage4

Employee WageThe employee wage section lets you correlate employee wage information (wage types, pay scales, etc.) with certain organizational aspects (position, organization, job, etc.). Payment amounts for each Wage Type are the key measure in this section.

ReportsEmployee wage allows for a variety of detail, trend, and high level analysis. Below is a list of the reports included here for analysis:• Wage Analysis• Employee Wage History• IDES Sample Employee Wage Summary


POSITION_HIER_HZ BENEFIT_ENROLLMENT_FACT.POSITION_ID=POSITION_HIER_HZ.POSITION_ID


POSITION_HIER_VR BENEFIT_ENROLLMENT_FACT.POSITION_ID=POSITION_HIER_VR.CHILD_ID


TIME_DIM TIME_DIM.CALENDAR_DATE = BENEFIT_ENROLLMENT_FACT.PARTICIPATN_DATE


VESTING_RULE VESTING_RULE.BENFT_AREA_ID = BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID AND VESTING_RULE.VESTNG_RULE_ID = BENEFIT_ENROLLMENT_FACT.VESTNG_RULE_ID


WORK_CONTRACT WORK_CONTRACT.COUNTRY_GRP_ID = BENEFIT_ENROLLMENT_FACT.COUNTRY_GRP_ID AND WORK_CONTRACT.CONTRACT_ID = BENEFIT_ENROLLMENT_FACT.CONTRACT_ID



ReportsEmployee Wage 4

Wage Analysis View wage summary and employee listing for the selected Company Code, Personnel Area, Wage Types, and As Of Date.

SummaryView wage number of employees, total payment amount, minimum payment amount, and maximum payment amount for each wage type.



ListingView employee wage listing for each wage type by personnel area and org unit. Includes a hyperlink on Person Id to view Employee Wage History.

Calculations• Current Date = CurrentDate()




Employee Wage History View wage history details for the selected employee, company code, and personnel area, and selected As Of Date.


IDES Sample Employee Wage Summary Analyze Salary, Bonus, and Hourly Rate wages for Sample IDES Company Code = 'IDES US INC' by Organization Unit Id = '00000001'. This report provides a sample using custom universe objects to view specific wages.Note: This report uses sample objects hard-coded to specific wage type Ids in the IDES sample data.



Summary by Personnel AreaView Salary, Bonus, and Hourly Rate summaries by Org Unit hierarchy.



Top 10 EmployeesView Top 10 wage earning employees for Salary, Bonus, and Hourly Rate wage types. Includes a hyperlink on Person Id to view Employee Wage History.

Calculations• Current Date = CurrentDate()



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


EMPLOYEE_WAGE_FACT

BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID = EMPLOYEE_WAGE_FACT.BUS_AREA_ID

EMPLOYEE_WAGE_FACT

COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = EMPLOYEE_WAGE_FACT.CMPNY_CODE_ID

EMPLOYEE_WAGE_FACT

CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = EMPLOYEE_WAGE_FACT.CTRL_AREA_ID

EMPLOYEE_WAGE_FACT

COST_CENTER COST_CENTER.CTRL_AREA_ID = EMPLOYEE_WAGE_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = EMPLOYEE_WAGE_FACT.COST_CNTR_ID

EMPLOYEE_WAGE_FACT

COST_CENTER_HIER_HZ

EMPLOYEE_WAGE_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and EMPLOYEE_WAGE_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID

EMPLOYEE_WAGE_FACT

COST_CENTER_HIER_VR

EMPLOYEE_WAGE_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and EMPLOYEE_WAGE_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

EMPLOYEE_WAGE_FACT

COUNTRY_GROUP COUNTRY_GROUP.COUNTRY_GRP_ID = EMPLOYEE_WAGE_FACT.COUNTRY_GRP_ID

EMPLOYEE_WAGE_FACT

CURRENCY CURRENCY.CURR_ID = EMPLOYEE_WAGE_FACT.CURR_ID

EMPLOYEE_WAGE_FACT

EMPLOYEE EMPLOYEE.EMPLOYEE_KEY = EMPLOYEE_WAGE_FACT.EMPLOYEE_KEY



EMPLOYEE_WAGE_FACT

EMPLOYEE_GROUP EMPLOYEE_GROUP.EMPLOYEE_GRP_ID = EMPLOYEE_WAGE_FACT.EMPLOYEE_GRP_ID

EMPLOYEE_WAGE_FACT

EMPLOYEE_SUBGROUP

EMPLOYEE_SUBGROUP.EMPLOYEE_SUBGRP_ID = EMPLOYEE_WAGE_FACT.EMPLOYEE_SUBGRP_ID

EMPLOYEE_WAGE_FACT

JOB JOB.JOB_KEY = EMPLOYEE_WAGE_FACT.JOB_KEY

EMPLOYEE_WAGE_FACT

LINE_MANAGER_HIER LINE_MANAGER_HIER.POSITION_ID = EMPLOYEE_WAGE_FACT.POSITION_ID AND LINE_MANAGER_HIER.PERSON_ID = EMPLOYEE_WAGE_FACT.PERSON_ID andLINE_MANAGER_HIER.VALID_FROM_DATE <= EMPLOYEE_WAGE_FACT. VALID_FROM_DATE andLINE_MANAGER_HIER.VALID_TO_DATE >= EMPLOYEE_WAGE_FACT. VALID_TO_DATE

EMPLOYEE_WAGE_FACT

ORGANIZATION_KEY ORGANIZATION_KEY.ORG_KEY_ID = EMPLOYEE_WAGE_FACT.ORG_KEY_ID

EMPLOYEE_WAGE_FACT

ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_KEY = EMPLOYEE_WAGE_FACT.ORG_UNIT_KEY

EMPLOYEE_WAGE_FACT


ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY = EMPLOYEE_WAGE_FACT.ORG_UNIT_KEY

EMPLOYEE_WAGE_FACT


EMPLOYEE_WAGE_FACT.ORG_UNIT_KEY = ORGANIZATION_UNIT_HIER_VR.CHILD_KEY




EMPLOYEE_WAGE_FACT

PAY_SCALE_AREA PAY_SCALE_AREA.COUNTRY_GRP_ID = EMPLOYEE_WAGE_FACT.COUNTRY_GRP_ID AND PAY_SCALE_AREA.PAY_SCALE_AREA_ID = EMPLOYEE_WAGE_FACT.PAY_SCALE_AREA_ID

EMPLOYEE_WAGE_FACT

PAY_SCALE_TYPE PAY_SCALE_TYPE.COUNTRY_GRP_ID = EMPLOYEE_WAGE_FACT.COUNTRY_GRP_ID AND PAY_SCALE_TYPE.PAY_SCALE_TYPE_ID = EMPLOYEE_WAGE_FACT.PAY_SCALE_TYPE_ID

EMPLOYEE_WAGE_FACT

PAYROLL_AREA PAYROLL_AREA.PAYROLL_AREA_ID = EMPLOYEE_WAGE_FACT.PAYROLL_AREA_ID

EMPLOYEE_WAGE_FACT


PERSONNEL_ADMINISTRATOR.ADMIN_GRP_CODE = EMPLOYEE_WAGE_FACT.ADMIN_GRP_CODE AND PERSONNEL_ADMINISTRATOR.ADMIN_ID = EMPLOYEE_WAGE_FACT.ADMIN_ID_HR

EMPLOYEE_WAGE_FACT

PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID = EMPLOYEE_WAGE_FACT.PERSONNEL_AREA_ID

EMPLOYEE_WAGE_FACT

PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID = EMPLOYEE_WAGE_FACT.PERSONNEL_AREA_ID AND PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID = EMPLOYEE_WAGE_FACT.PERSONNEL_SUBAREA_ID

EMPLOYEE_WAGE_FACT

POSITION POSITION.POSITION_KEY = EMPLOYEE_WAGE_FACT.POSITION_KEY



ReportsPayroll 4

PayrollUsing the employee payroll section of this Rapid Mart, you can analyze payroll payments and/or deductions by wage type. Typically, a company’s payroll process calculates remuneration based on wage types and a country-specific set of rules. The Payroll section is designed to meet U.S. payroll requirements. Customizing the Rapid Mart is required for other countries.

ReportsPayroll allows for a variety of detail, trend, and high level analysis. Below is a list of the reports included here for analysis:• Payroll Run Details• Employee Payroll Details• Payroll Trend Analysis

EMPLOYEE_WAGE_FACT

POSITION_HIER_HZ EMPLOYEE_WAGE_FACT.POSITION_ID=POSITION_HIER_HZ.POSITION_ID

EMPLOYEE_WAGE_FACT

POSITION_HIER_VR EMPLOYEE_WAGE_FACT.POSITION_ID=POSITION_HIER_VR.CHILD_ID

EMPLOYEE_WAGE_FACT

SALARY_RANGE SALARY_RANGE.SALARY_RANGE_KEY = EMPLOYEE_WAGE_FACT.SALARY_RANGE_KEY

EMPLOYEE_WAGE_FACT

UNIT_OF_TIME UNIT_OF_TIME.UOT_ID = EMPLOYEE_WAGE_FACT.UOT_ID

EMPLOYEE_WAGE_FACT

WAGE_TYPE WAGE_TYPE.WAGE_TYPE_KEY = EMPLOYEE_WAGE_FACT.WAGE_TYPE_KEY

EMPLOYEE_WAGE_FACT

WORK_CONTRACT WORK_CONTRACT.COUNTRY_GRP_ID = EMPLOYEE_WAGE_FACT.COUNTRY_GRP_ID AND WORK_CONTRACT.CONTRACT_ID = EMPLOYEE_WAGE_FACT.CONTRACT_ID



ReportsPayroll4
Payroll Run Details
View Payroll Run details for the selected Payroll Area, and payroll run date.

Calculations• Payroll Run Month =Substr([UR Payroll Run Date]; 0;Pos([UR Payroll

Run Date]; "/")-1)



ReportsPayroll 4

Employee Payroll Details View Payroll details for the selected employee (Person Id) and the selected date range.



ReportsPayroll4
Payroll Trend Analysis
View payroll summary trends for the specified Company Code, Organization Unit, Payroll Area Id, and Cumulation Year.


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


PAYROLL_FACT BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID = PAYROLL_FACT.BUS_AREA_ID

PAYROLL_FACT COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = PAYROLL_FACT.CMPNY_CODE_ID

PAYROLL_FACT CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = PAYROLL_FACT.CTRL_AREA_ID


ReportsPayroll 4

PAYROLL_FACT COST_CENTER COST_CENTER.CTRL_AREA_ID = PAYROLL_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = PAYROLL_FACT.COST_CNTR_ID

PAYROLL_FACT COST_CENTER_HIER_HZ

PAYROLL_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and PAYROLL_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID

PAYROLL_FACT COST_CENTER_HIER_VR

PAYROLL_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and PAYROLL_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID

PAYROLL_FACT COUNTRY_GROUP COUNTRY_GROUP.COUNTRY_GRP_ID = PAYROLL_FACT.COUNTRY_GRP_ID

PAYROLL_FACT CURRENCY CURRENCY.CURR_ID = PAYROLL_FACT.CURR_ID

PAYROLL_FACT EMPLOYEE PAYROLL_FACT.PERSON_ID = EMPLOYEE.PERSON_ID andEMPLOYEE.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andEMPLOYEE.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT EMPLOYEE_GROUP EMPLOYEE_GROUP.EMPLOYEE_GRP_ID = PAYROLL_FACT.EMPLOYEE_GRP_ID

PAYROLL_FACT EMPLOYEE_SUBGROUP

EMPLOYEE_SUBGROUP.EMPLOYEE_SUBGRP_ID = PAYROLL_FACT.EMPLOYEE_SUBGRP_ID

PAYROLL_FACT JOB JOB.JOB_ID = PAYROLL_FACT.JOB_ID andJOB.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andJOB.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE



ReportsPayroll4

PAYROLL_FACT LINE_MANAGER_HIER LINE_MANAGER_HIER.POSITION_ID = PAYROLL_FACT.POSITION_ID AND LINE_MANAGER_HIER.PERSON_ID = PAYROLL_FACT.PERSON_ID andLINE_MANAGER_HIER.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andLINE_MANAGER_HIER.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT ORGANIZATION_KEY ORGANIZATION_KEY.ORG_KEY_ID = PAYROLL_FACT.ORG_KEY_ID

PAYROLL_FACT ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_ID = PAYROLL_FACT.ORG_UNIT_ID andORGANIZATION_UNIT.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andORGANIZATION_UNIT.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT ORGANIZATION_UNIT_HIER_HZ

ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_ID = PAYROLL_FACT.ORG_UNIT_ID andORGANIZATION_UNIT_HIER_HZ.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andORGANIZATION_UNIT_HIER_HZ.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT ORGANIZATION_UNIT_HIER_VR

ORGANIZATION_UNIT_HIER_VR.CHILD_ID = PAYROLL_FACT.ORG_UNIT_ID andORGANIZATION_UNIT_HIER_VR.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andORGANIZATION_UNIT_HIER_VR.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT PAYROLL_AREA PAYROLL_AREA.PAYROLL_AREA_ID = PAYROLL_FACT.PAYROLL_AREA_ID



ReportsPayroll 4

PAYROLL_FACT PAYROLL_PERIOD PAYROLL_PERIOD.PERIOD_PARAMETER_ID = PAYROLL_FACT.PERIOD_PARAMETER_ID AND PAYROLL_PERIOD.PAYROLL_PERIOD_ID = PAYROLL_FACT.PAYROLL_PERIOD_ID

PAYROLL_FACT PAYROLL_STATUS PAYROLL_STATUS.PAYROLL_STATUS_ID = PAYROLL_FACT.PAYROLL_STATUS_ID

PAYROLL_FACT PAYROLL_TYPE PAYROLL_TYPE.PAYROLL_TYPE_ID = PAYROLL_FACT.PAYROLL_TYPE_ID

PAYROLL_FACT PERSONNEL_ADMINISTRATOR

PERSONNEL_ADMINISTRATOR.ADMIN_GRP_CODE = PAYROLL_FACT.ADMIN_GRP_CODE AND PERSONNEL_ADMINISTRATOR.ADMIN_ID = PAYROLL_FACT.ADMIN_ID_HR

PAYROLL_FACT PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID = PAYROLL_FACT.PERSONNEL_AREA_ID

PAYROLL_FACT PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID = PAYROLL_FACT.PERSONNEL_AREA_ID AND PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID = PAYROLL_FACT.PERSONNEL_SUBAREA_ID

PAYROLL_FACT POSITION POSITION.POSITION_ID = PAYROLL_FACT.POSITION_ID and POSITION.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andPOSITION.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE



ReportsPayroll4

PAYROLL_FACT POSITION_HIER_HZ PAYROLL_FACT.POSITION_ID=POSITION_HIER_HZ.POSITION_ID and POSITION_HIER_HZ.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE and POSITION_HIER_HZ.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT POSITION_HIER_VR PAYROLL_FACT.POSITION_ID=POSITION_HIER_VR.CHILD_ID and POSITION_HIER_VR.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE and POSITION_HIER_VR.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT TIME_DIM PAYROLL_FACT.PAYROLL_RUN_DATE = TIME_DIM.CALENDAR_DATE

PAYROLL_FACT UNIT_OF_TIME UNIT_OF_TIME.UOT_ID = PAYROLL_FACT.UOT_ID

PAYROLL_FACT WAGE_TYPE WAGE_TYPE.WAGE_TYPE_ID = PAYROLL_FACT.WAGE_TYPE_ID andWAGE_TYPE.VALID_FROM_DATE <= PAYROLL_FACT. PAYROLL_RUN_DATE andWAGE_TYPE.VALID_TO_DATE >= PAYROLL_FACT. PAYROLL_RUN_DATE

PAYROLL_FACT WORK_CONTRACT WORK_CONTRACT.COUNTRY_GRP_ID = PAYROLL_FACT.COUNTRY_GRP_ID AND WORK_CONTRACT.CONTRACT_ID = PAYROLL_FACT.CONTRACT_ID

PAYROLL_PERIOD PAYROLL_PERIOD_PARAMETER

PAYROLL_PERIOD.PERIOD_PARAMETER_ID = PAYROLL_PERIOD_PARAMETER.PERIOD_PARAMETER_ID


BUSINESS_AREA BUSINESS_AREA.BUS_AREA_ID = PAYROLL_SUMMARY_FACT.BUS_AREA_ID



ReportsPayroll 4


COMPANY_CODE COMPANY_CODE.CMPNY_CODE_ID = PAYROLL_SUMMARY_FACT.CMPNY_CODE_ID


CONTROLLING_AREA CONTROLLING_AREA.CTRL_AREA_ID = PAYROLL_SUMMARY_FACT.CTRL_AREA_ID


COST_CENTER COST_CENTER.CTRL_AREA_ID = PAYROLL_SUMMARY_FACT.CTRL_AREA_ID AND COST_CENTER.COST_CNTR_ID = PAYROLL_SUMMARY_FACT.COST_CNTR_ID


COST_CENTER_HIER_HZ

PAYROLL_SUMMARY_FACT.CTRL_AREA_ID=COST_CENTER_HIER_HZ.CTRL_AREA_ID and PAYROLL_SUMMARY_FACT.COST_CNTR_ID=COST_CENTER_HIER_HZ.COST_CNTR_ID


COST_CENTER_HIER_VR

PAYROLL_SUMMARY_FACT.CTRL_AREA_ID=COST_CENTER_HIER_VR.CTRL_AREA_ID and PAYROLL_SUMMARY_FACT.COST_CNTR_ID=COST_CENTER_HIER_VR.CHILD_ID


COUNTRY_GROUP COUNTRY_GROUP.COUNTRY_GRP_ID = PAYROLL_SUMMARY_FACT.COUNTRY_GRP_ID


CURRENCY CURRENCY.CURR_ID = PAYROLL_SUMMARY_FACT.CURR_ID


EMPLOYEE PAYROLL_SUMMARY_FACT.PERSON_ID = EMPLOYEE.PERSON_ID andEMPLOYEE.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andEMPLOYEE.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE



ReportsPayroll4


EMPLOYEE_GROUP EMPLOYEE_GROUP.EMPLOYEE_GRP_ID = PAYROLL_SUMMARY_FACT.EMPLOYEE_GRP_ID


EMPLOYEE_SUBGROUP

EMPLOYEE_SUBGROUP.EMPLOYEE_SUBGRP_ID = PAYROLL_SUMMARY_FACT.EMPLOYEE_SUBGRP_ID


JOB JOB.JOB_ID = PAYROLL_SUMMARY_FACT.JOB_ID andJOB.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andJOB.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE


LINE_MANAGER_HIER LINE_MANAGER_HIER.POSITION_ID = PAYROLL_SUMMARY_FACT.POSITION_ID AND LINE_MANAGER_HIER.PERSON_ID = PAYROLL_SUMMARY_FACT.PERSON_ID andLINE_MANAGER_HIER.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andLINE_MANAGER_HIER.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE


ORGANIZATION_KEY ORGANIZATION_KEY.ORG_KEY_ID = PAYROLL_SUMMARY_FACT.ORG_KEY_ID


ORGANIZATION_UNIT ORGANIZATION_UNIT.ORG_UNIT_ID = PAYROLL_SUMMARY_FACT.ORG_UNIT_ID andORGANIZATION_UNIT.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andORGANIZATION_UNIT.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE



ReportsPayroll 4



ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_ID = PAYROLL_SUMMARY_FACT.ORG_UNIT_ID andORGANIZATION_UNIT_HIER_HZ.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andORGANIZATION_UNIT_HIER_HZ.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE



ORGANIZATION_UNIT_HIER_VR.CHILD_ID = PAYROLL_SUMMARY_FACT.ORG_UNIT_ID andORGANIZATION_UNIT_HIER_VR.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andORGANIZATION_UNIT_HIER_VR.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE


PAYROLL_AREA PAYROLL_AREA.PAYROLL_AREA_ID = PAYROLL_SUMMARY_FACT.PAYROLL_AREA_ID


PAYROLL_CUMULATION_TYPE

PAYROLL_CUMULATION_TYPE.CUMULATN_TYPE_ID = PAYROLL_SUMMARY_FACT.CUMULATN_TYPE_ID


PAYROLL_PERIOD PAYROLL_PERIOD.PERIOD_PARAMETER_ID = PAYROLL_SUMMARY_FACT.PERIOD_PARAMETER_ID AND PAYROLL_PERIOD.PAYROLL_PERIOD_ID = PAYROLL_SUMMARY_FACT.PAYROLL_PERIOD_ID


PAYROLL_STATUS PAYROLL_STATUS.PAYROLL_STATUS_ID = PAYROLL_SUMMARY_FACT.PAYROLL_STATUS_ID



ReportsPayroll4


PAYROLL_TYPE PAYROLL_TYPE.PAYROLL_TYPE_ID = PAYROLL_SUMMARY_FACT.PAYROLL_TYPE_ID



PERSONNEL_ADMINISTRATOR.ADMIN_GRP_CODE = PAYROLL_SUMMARY_FACT.ADMIN_GRP_CODE AND PERSONNEL_ADMINISTRATOR.ADMIN_ID = PAYROLL_SUMMARY_FACT.ADMIN_ID_HR


PERSONNEL_AREA PERSONNEL_AREA.PERSONNEL_AREA_ID = PAYROLL_SUMMARY_FACT.PERSONNEL_AREA_ID


PERSONNEL_SUBAREA

PERSONNEL_SUBAREA.PERSONNEL_AREA_ID = PAYROLL_SUMMARY_FACT.PERSONNEL_AREA_ID AND PERSONNEL_SUBAREA.PERSONNEL_SUBAREA_ID = PAYROLL_SUMMARY_FACT.PERSONNEL_SUBAREA_ID


POSITION POSITION.POSITION_ID = PAYROLL_SUMMARY_FACT.POSITION_ID andPOSITION.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE andPOSITION.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE


POSITION_HIER_HZ PAYROLL_SUMMARY_FACT.POSITION_ID=POSITION_HIER_HZ.POSITION_ID and POSITION_HIER_HZ.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE and POSITION_HIER_HZ.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE



ReportsSAP Master Data Reports 4

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


POSITION_HIER_VR PAYROLL_SUMMARY_FACT.POSITION_ID=POSITION_HIER_VR.CHILD_ID and POSITION_HIER_VR.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE and POSITION_HIER_VR.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE


TIME_DIM PAYROLL_SUMMARY_FACT.PAYROLL_RUN_DATE = TIME_DIM.CALENDAR_DATE


UNIT_OF_TIME UNIT_OF_TIME.UOT_ID = PAYROLL_SUMMARY_FACT.UOT_ID


WAGE_TYPE WAGE_TYPE.WAGE_TYPE_ID = PAYROLL_SUMMARY_FACT.WAGE_TYPE_ID and WAGE_TYPE.VALID_FROM_DATE <= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE and WAGE_TYPE.VALID_TO_DATE >= PAYROLL_SUMMARY_FACT. PAYROLL_RUN_DATE


WORK_CONTRACT WORK_CONTRACT.COUNTRY_GRP_ID = PAYROLL_SUMMARY_FACT.COUNTRY_GRP_ID AND WORK_CONTRACT.CONTRACT_ID = PAYROLL_SUMMARY_FACT.CONTRACT_ID



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



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

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

ACTIVITY.ACTIVITY_ID=ACTIVITY_HIER_HR.ACTIVITY_ID ) AND



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

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

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




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


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



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




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



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




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

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



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

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

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

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

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

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

GL_ACCOUNT_HIER_HZ.LEVEL_1_ID AND GL_ACCOUNT_HIER_HZ.LEVEL_3_ID <>



GL_ACCOUNT_HIER_HZ.LEVEL_4_ID )



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


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



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


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




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



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


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




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

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

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

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

Report Name Invalid Data Table

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



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

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

Dimension Table Hierarchy Table Join Text

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

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

BILL_OF_MATERIALS BILL_OF_MATERIALS_HIER_HZ

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

BILL_OF_MATERIALS BILL_OF_MATERIALS_HIER_VR

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

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



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

COST_ELEMENT COST_ELEMENT_HIER_HZ

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

COST_ELEMENT COST_ELEMENT_HIER_VR

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

COUNTRY_GROUP COUNTRY_GROUP_STATUS

COUNTRY_GROUP.COUNTRY_GRP_ID = COUNTRY_GROUP_STATUS.COUNTRY_GRP_ID

EQUIPMENT EQUIPMENT_HIER_HZ EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIER_HZ.EQUIPMNT_ID

EQUIPMENT EQUIPMENT_HIER_VR EQUIPMENT.EQUIPMNT_ID=EQUIPMENT_HIER_VR.CHILD_ID

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

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

FUNCTIONAL_AREA FUNCTIONAL_AREA_HIER_HZ

FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_HZ.FUNCTNL_AREA_ID

FUNCTIONAL_AREA FUNCTIONAL_AREA_HIER_VR

FUNCTIONAL_AREA.FUNCTNL_AREA_ID=FUNCTIONAL_AREA_HIER_VR.CHILD_ID

FUNCTIONAL_LOCATION FUNCTIONAL_LOCATION_HIER_HZ

FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_HZ.FUNCTNL_LOCATN_ID

FUNCTIONAL_LOCATION FUNCTIONAL_LOCATION_HIER_VR

FUNCTIONAL_LOCATION.FUNCTNL_LOCATN_ID=FUNCTIONAL_LOCATION_HIER_VR.CHILD_ID

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




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

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

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

INTERNAL_ORDER INTERNAL_ORDER_HIER_HZ

INTERNAL_ORDER.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_HZ.INTERNAL_ORDER_ID

INTERNAL_ORDER INTERNAL_ORDER_HIER_VR

INTERNAL_ORDER.INTERNAL_ORDER_ID=INTERNAL_ORDER_HIER_VR.CHILD_ID

MATERIAL PRODUCT_HIERARCHY MATERIAL.PROD_HIER_ID=PRODUCT_HIERARCHY.PROD_HIER_ID

OBJECT_STATUS_HZ OBJECT_STATUS OBJECT_STATUS_HZ.OBJ_ID=OBJECT_STATUS.OBJ_ID

ORGANIZATION_UNIT ORGANIZATION_UNIT_HIER_HZ

ORGANIZATION_UNIT.ORG_UNIT_KEY =ORGANIZATION_UNIT_HIER_HZ.ORG_UNIT_KEY

ORGANIZATION_UNIT ORGANIZATION_UNIT_HIER_VR

ORGANIZATION_UNIT.ORG_UNIT_KEY=ORGANIZATION_UNIT_HIER_VR.CHILD_KEY

PAYROLL_PERIOD PAYROLL_PERIOD_PARAMETER

PAYROLL_PERIOD.PERIOD_PARAMETER_ID = PAYROLL_PERIOD_PARAMETER.PERIOD_PARAMETER_ID




POSITION POSITION_HIER_HZ POSITION.POSITION_ID=POSITION_HIER_HZ.POSITION_ID

POSITION POSITION_HIER_VR POSITION.POSITION_ID=POSITION_HIER_VR.CHILD_ID

PROFIT_CENTER PROFIT_CENTER_HIER_HZ

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

PROFIT_CENTER PROFIT_CENTER_HIER_VR

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

PROJECT_ELEMENT PROJECT_ELEMENT_HIER_HZ

PROJECT_ELEMENT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_HZ.PROJ_ELEM_ID

PROJECT_ELEMENT PROJECT_ELEMENT_HIER_VR

PROJECT_ELEMENT.PROJ_ELEM_ID=PROJECT_ELEMENT_HIER_VR.CHILD_ID

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

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



Universe

chapter

UniverseOverview5
Overview
Before we begin a detailed discussion of the SAP Human Resources universes it is important to understand certain concepts that are common to any Rapid Mart universe.• Universe Design Principles• Hierarchies• Human Resources Specific HierarchiesThe SAP BusinessObjects HR Rapid Mart, version for SAP solutions contains the following universes:• SAP Human Resources Universe - business content universe for Human

Resources• SAP HR Master Data Universe - auxiliary universe for browsing master

data, including infotypes and calendars• SAP Master Data Universe - 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 Human Resources universe are also presented in Customizing the Universe.

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


UniverseUniverse Design Principles 5

Universe TerminologyStar Schema: also called Subject Area. The dimensional data modeling approach. A star schema has one large central table (fact table) and a set of smaller attendant tables (dimension tables) displayed in a radial pattern around the central table. Optionally, a hierarchy may be associated with a dimension table. See diagram below for details

Dimension Table (Dim 1 - Dim 6): a table where the textual descriptions are stored. Optionally, a Dimension may have an associated hierarchy - such as Dim 6 in the diagram.Hierarchy: A hierarchy is an ordered series of related objects. An example of a hierarchy is time, or “date”, which may group objects as Year, Quarter, and Month. You can use drill up or down to perform multi dimensional analysis with a hierarchy. Hierarchies are described in great detail later in this chapter.Fact Table: a table where the numerical measurements of the business are stored. Each of these measurements is taken at the intersection of all the dimensions. The fact table, if it represents a transactional table, might also store some transaction descriptive attributes if there is no a proper dimension for this attribute. Fact tables can be detailed or summarized. These represent different levels of granularity. A detailed fact table has a finer granularity, typically transaction level detail. A summarized table aggregates the transaction data with fewer


UniverseUniverse Design Principles5

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

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

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


UniverseUniverse Design Principles 5

Universe Table LayoutThe Rapid Mart data model uses star design principle. Fact tables are used to store measures and dimension tables to store attributes. The universe table layout follows the Rapid Mart data model. Fact Tables are placed vertically in the middle of the universe between two parallel rows of dimension tables.Dimensions are grouped logically by business function or process. These groups are documented in the universe graphical layout. There are screen shots of the graphical layout for each subject area in this chapter.In some cases, like the Metadata universe, a star schema is not possible due to the nature of the data. In these cases the layout is presented as simply and logically as possible.

Join StrategyContexts: Dimensions that relate to multiple fact tables (common dimensions) are joined to each of those fact tables. No aliasing of the dimensions is used. Instead, a context for each fact table has been created and all dimensional joins for that fact table are included in the context. as shown below:

Aliases: Aliases are used when the same dimension describes different business processes. For example, the Time Dimension needs to be associated with different processes – document creation, and posting. All of these may be in the same subject area (fact table). In this case, there will be a Time Dimension alias for each process.Facts to Fact Joins: Fact tables are not joined with each other unless they represent the same subject and have similar granularity. Example: SALES_ORDERS_FACT and BACKLOG_FACT.


UniverseUniverse Design Principles5

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

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

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

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

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


UniverseHierarchies 5

TechniquesThese are advanced technique objects developed for the Web Intelligence reports.• Indexes: The index technique enables multiple measures to be returned

in a single data provider while providing different conditions for different groups of measures. For example, using indexes it is possible to return the total revenue, revenue lost for returned items, and last year’s revenue all in a single data provider, and using a single revenue object. Without this technique multiple synchronized queries would be needed.Think of indexes as providing vertical breaks in a single data provider. Local variables can then be created using the index values.

• Zeros: These perform a similar function to indexes, namely they provide a means to return filtered information in a single data provider. Just as Indexes provide vertical breaks for measures, Zeros provide horizontal breaks. This is often requires when comparing two time periods.For example, you want to compare sales in a certain product line for each quarter this year. However, the product line had no sales in third quarter. Without use of the Zeros technique the data for 3rd quarter would be missing in the report. With Zeros, a placeholder value (with zero value) is shown.

• Blanks: Their purpose is to provide an additional object that can be used in a display block. An example is a label that returns total company sales, where a normal query would only provide breakdowns by some category.Blanks are coded to ‘ ‘ (a space). Normally, this text is the same as the name of the object.

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

Hierarchies

Hierarchies OverviewIn general, hierarchies allow users to perform multi-dimensional analysis. Multi-dimensional analysis uses dimension objects organized in a meaningful order. Multi-dimensional analysis allows users to observe data from various viewpoints. This enables them to spot trends or exceptions in the data.


UniverseHierarchies5

A hierarchy is an ordered series of related objects. An example of a hierarchy is time, or “date”, which may group objects as Year, Quarter, and Month. You can use drill up or down to perform multi dimensional analysis with a hierarchy. Time is an example of a horizontal hierarchy where each level in the hierarchy is presented as a column in a database table. Thus, Year, Quarter, Month, and Date are all column names.You can use this hierarchy in a report to drill down from a higher level of aggregation (year) to a more detailed level (quarter). You can also drill up from quarter to year.The hierarchies appear both as sub-classes in the dimensions of each universe and in their own display screen in Web Intelligence (as shown below).Web Intelligence- Location of Rapid Mart Hierarchies



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

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

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

Time Dimension and Fiscal Period Hierarchies

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

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

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

• Controlling Area Fiscal Periods• Company Code Fiscal Periods

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


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

Activity Hierarchy ExampleWe will use Activity as an example to illustrate how vertical and horizontal hierarchies work together. The principles in this example holds true for any hierarchy, regardless of its source in SAP solutions.The illustration below shows a sample set of Activities organized into a three level hierarchy:

Note: The hierarchy contains a “ragged” node. This happens when a node reports to more than one ancestor (or parent) node. In our example, the node 1421 has two ancestors. This legal and acceptable in both SAP solutions and the Rapid Mart.



Horizontal Hierarchy StructureHorizontal hierarchies are organized so that all levels (or nodes) appear as columns on a single row of data. Vertical hierarchies represent each level or node with an individual row of data.The horizontal structure for Activities is the Activity Hierarchy Hz class, and the corresponding ACTIVITY_HIER_HR table. Within this table and class, the hierarchy is represented as shown below.Horizontal Hierarchy Structure:

In the horizontal representation, one row shows the entire hierarchy for each node in the hierarchy. Note: Be careful of the ragged hierarchy nodes. If your query simply selects for Activity ID = 1421, you will get two rows returned because Activity 1421 reports to two different sets of ancestors or parents. You must also specify the Level 2 ID (P1000 or P2000) to uniquely identify the hierarchy. In this case, you could also specify the Level 1 ID (A1000 or A3000) to uniquely identify the hierarchy.Note: Be careful of Primary Key violations. The Horizontal Hierarchy tables have an arbitrary limit of how may levels of hierarchy are extracted. If your data contains more levels than the limit, you can have a primary key violation when loading horizontal data.



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

horizontal table and its primary key accordingly.Propagation of Child (Leaf) Nodes:Also note that child (leaf) nodes that belong to other than the last hierarchy level (Leaf Level 1 and Leaf Level 2) have their Activity ID propagated to the lowest Level ID of the hierarchy starting with the Level 1 ID. Leaf level 2 nodes are propagated out from level 2 ID to the lowest Level ID. Leaf level 3 nodes are propagated out from level 3 ID to the lowest level, etc..

Child (leaf) node propagation allows creating reports with indented listings of Cost Elements, Cost and Profit Centers, and other hierarchical master data where depth of indention depends on the node position (Leaf Level).

Vertical Hierarchy StructureThe vertical structure for the Activities hierarchy is the Activity Hierarchy Vr class, and the corresponding ACTIVITY_HIER_VR table. The vertical hierarchy uses many more rows to represent the same hierarchy. Each row is an ancestor / descendant combination showing only a single relationship in the hierarchy. For simplicity, only the “A1000” hierarchy is shown in the diagram below:



Vertical Hierarchy Structure:

In this representation the Level (or leaf level) indicates how many generations exist between ancestor and descendant. Level 0 indicates no generations (ancestor and descendant the same). Level 1 indicates parent to child, level 2 grandparent to child, level 3 great-grandparent to child, etc.You can find more information on how hierarchies are created in the Data Services documentation for the Hierarchy Flattening Transform, Pivot Transform, and Reverse Pivot Transform.


Hierarchy Report Generation
When you choose the “Select Single Parent Activity for Group (Vertical Hierarchy)” filter in a report, you are prompted to “Select a Single Parent Activity for Group” at run time. Entering “A1000” selects this subset of data from the Vertical Hierarchy Structure:

This subset contains all relationships in the hierarchy, no matter how many generations are between the ancestor (or parent) chosen and its descendant nodes.When you include objects from the horizontal “Activity Hierarchy Hz” class in the same query, the results will show the entire “family” structure for the selected Activity Hierarchy Group. Thus, the vertical hierarchy gives us the selection criteria (via the filter) and the horizontal hierarchy gives us the report contents.Note: We recommend using “Select Single Parent Activity Group (Vertical Hierarchy)” filter only with hierarchy data discovery reports. See Hierarchy Data Discovery in Reports Chapter for more details.

VerticalHierarchySubset forA1000



Sample Report for Activity (Vertical Hierarchy):

Report Generation - Propagation of Leaf NodesAs described earlier, the horizontal hierarchy can be used to create an indented report where the each lower level (leaf level) is more indented than the previous level.



Sample Report (Propagation of Leaf Nodes):

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



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

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

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

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


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

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

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



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

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

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

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

Activity1

Activity2 Activity3

Activity5Activity1 Activity4 Activity6

(as Parent)

(as Child)



Invalid Hierarchies Layout:

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


UniverseHuman Resources Specific Hierarchies 5

Human Resources Specific HierarchiesIn the Rapid Mart, 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:The universe contains two sub-classes within in each dimension represent the vertical and horizontal hierarchies.

Accounting HierarchiesThe HR Rapid Mart includes a single Accounting Hierarchy dimension to report financial breakdowns in the same manner as SAP solutions. For more information look at Set Hierarchies (SAP solutions transaction GS03).

See “Invalid Hierarchies” on page 167 for more details on viewing invalid accounting hierarchy data.

Additional HierarchiesThese additional hierarchies, for the HR 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 Table and Column

Activity CCSS-LSTAR

Hierarchy Name Source Tables

Position HRP1001Organization Unit HRP1001


UniverseSAP Human Resources Universe5
SAP Human Resources Universe
The SAP Human Resources universe gathers information from the SAP solutions Human Resources module.The SAP BusinessObjects HR Rapid Mart, version for SAP solutions supports analysis of benefits, payroll and other employment related information. Analysis of Human Resources helps one to better understand the personnel development and compensation programs within the company. To support these processes SAP solutions uses Benefit Area, Company Code, Cost Center, Personnel Area, Position, Personnel Area, other master data, and numerous reference data. In some cases these master data are organized into hierarchy (or tree) structures.The SAP Human Resources universe is a reflection of this complexity. At this writing, it has:• 219 classes• 1816 objects• 66 conditions• 88 tables• 4 alias• 256 joins• 7 contextsThe universe is well documented and logically organized to help universe users easily navigate to a specific object.The information in this chapter is useful to understand the data in the Rapid Mart and how to build reports using the data. The universe, and this chapter, are logically grouped into subject areas. They are:• Universe Design Considerations• Universe Design Considerations• Common Dimensions• Employee Administration• Employee Wage• Benefit Enrollment Detail• Benefit Enrollment Summary• Leave Entitlement• Payroll Detail• Payroll Summary


UniverseSAP Human Resources Universe 5

• Filters & Techniques• Sample Measures• Universe Validation

Universe Design ConsiderationsDue to the date effective nature of Human Resources data, this universe must adapt join strategy. Of the 6, subject areas, only payroll uses natural key joins in the universe. Employee Administration Benefits Enrollment, Leave Entitlement, and Employee Wage subject areas contain surrogate keys in the fact tables to simplify joins. Using surrogate keys in these cases eliminates the need to join on the validity dates, and allows for better query performance.Example: See below how EMPLOYEE dimension is joined to BENEFIT_ENROLLMENT_FACT (using surrogate key) vs. PAYROLL_FACT (no surrogate key available).

Benefit Enrollment FactEMPLOYEE.EMPLOYEE_KEY =

BENEFIT_ENROLLMENT_FACT.EMPLOYEE_KEYPayroll FactPAYROLL_FACT.PERSON_ID = EMPLOYEE.PERSON_ID andEMPLOYEE.VALID_FROM_DATE <=

PAYROLL_FACT.PAYROLL_RUN_DATE andEMPLOYEE.VALID_TO_DATE >=

PAYROLL_FACT.PAYROLL_RUN_DATE


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 13. Measures are grouped into sub-folders that represent the various monetary and quantity amounts of the fact tables in the star schemas.



Each subject area is further divided into classes by types of measure specific to the subject area.Common Dimensions: These top level classes appear after the Measures. These are the dimensions used in common by more than one subject area. These are sub-divided into classes for each specific dimension table. For example, the Organization Structure class has sub-classes for Company Code, and Controlling Area. Each of these represents a specific dimension table or alias of a dimension table. The Common Dimensions Matrix (presented later in this chapter) details which subject areas can be used with which common dimensions.Fact Tables: Following the Dimensions are group of Top Level classes, one for each subject area (also called fact table or star schema) in the universe.These subject area classes are further divided into classes that are logical groupings of fact table attributes. For example, the “Benefit Enroll - Dates and Fiscal Periods” class under “BENEFIT ENROLLMENT” contains the dates that are relevant to benefit enrollment.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 155 for details.


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



BENEFITSIn HR, these are the various employee benefits including health insurance and savings plans as well as the rules associated with the plans. The class carries the following sub-classes:

Benefit AreaThe highest-level subdivision of benefits data.Benefit areas enable different pools of benefit plans to be administered separately, for example, to reflect geographical location, departments, or production areas.Employees are sorted into benefit areas during processing, according to the corresponding feature.Example: The medical benefits offered by a company in the chemical industry are organized according to production areas. Employees in plastics production have different plans to employees in fertilizer production. Each production areas is represented by a benefit area.

Benefit PlanThe central element of the Benefit Administration component, representing a single benefit offered by the employer. A plan belongs to a plan category, and is defined by the following:• General plan data (for example, provider)• Any relevant plan options (for example, health plan coverage,

investments)• Rules determining the calculation of monetary amounts relating to

plans (for example, costs, contributions, coverage, credit)• Plan-specific checks (for example, evidence of insurability)

Benefit Program GroupA set of benefit plans offered to a specific group of employees.Benefit programs are defined for one, or a combination of two program groupings, and therefore control high-level eligibility. Low-level eligibility in controlled by the eligibility rules assigned to the individual plans within a program.

Benefit Spending AccountA benefit plan that allows employees to set aside tax-free dollars for anticipated medical care and dependent care expenses. Flexible spending accounts are available in North America only.



Dependent CoverageAn option for a health plan, chararacterized by the number of dependents that can be covered.

Enrollment TypeBenefit program enrollment type descriptive attributes from DD07T, BEN_ENRTYP domain. A -Automatic, D - Default, M - Manual.

Health PlanHealth Plan descriptive attributes from T5UCE

Insurance Coverage GroupBenefit insurance coverage rules and formulas from T74FB, T74FC, PA0168 (date-effective)

Insurance OptionThis is the insurance plan option, within the insurance plan.

Example: The Standard Life plan has 2 options, which the employee selects the desired coverage from: HIGH - $120,000 option; LOW - $80,000 option

Investment GroupA customer-defined group of investments that can be assigned to plans in the categories 'Savings' and 'Miscellaneous'.

Investment PlanA customer-defined option for plans in the categories Savings and Miscellaneous that lets employees choose how their contributions are invested.

BENEFIT RULESIdentifying rules for benefits participation and contribution. Sub-classes include: Benefit Termination Rule, Contribution Rule, Eligibility Rule, and Vesting Rule.

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

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



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

EMPLOYEEIn HR, the employee class tracks information about employees such as name, address, birth date, Gender, Marital status, number of dependents, etc.

EMPLOYEE ATTRIBUTESAdditional information about the employee such as Personnel Actions, Education, Job Qualifications, Work Permit status, etc. This area contains the following sub-classes:

• Certificate Type• Education Type• Ethnic Origin• Gender• Identification Type• Language• Marital Status• Military Status• Nationality• Personnel Action Reason• Personnel Action Status• Personnel Action Type• Personnel Date Type• Personnel Task Status• Personnel Task Type• Proficiency• Qualification• Religion• Residence Status• School Type• Study Branch• Time Management Status• Work Permit Type

JOB An organizational object that serves as a template for creating positions when you create an organizational plan.



Unlike Positions that can be occupied by holders, for example, secretary in the marketing department. Jobs are a classification of functions in an enterprise, for example, secretary, defined by the tasks and characteristics assigned to them. Job descriptions apply to different positions with similar tasks and characteristics. This includes Exempt/Non-Exempt Status, Payscale, etc.

LEAVE Information about the types of leave (vacation, sick leave, maternity leave, etc.) an employee may have.

Leave TypeJob leave type descriptive attributes from T533T

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:• Benefit Currency - The monetary currency associated with

personnel administration.

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

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

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



Controlling AreaAn organizational unit within a company, used to represent a closed system for cost accounting purposes. A controlling area may include single or multiple company codes that may use different currencies. These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area.

Country GroupA grouping of countries for which the political restrictions or AFS quota are equally valid (e.g. EU). The grouping of countries facilitates the entry and processing of country-specific restrictions and AFS quota.

Employee GroupThe employee group is an organizational entity which is governed by specific personnel regulations. An employee group is divided into several employee subgroups.

Employee SubgroupAn employee subgroup is an organizational entity within an employee group which is governed by specific personnel regulations.

Line Manager HierarchyA person who holds a managerial position in a company or department and who makes decisions in an area of responsibility. Line managers can act as the first person responsible for applicant correspondence.

Organization (Structure) KeyA hierarchy in which the organizational units in an enterprise are arranged according to tasks and functions.The organizational structure differs from the administrative enterprise or personnel structure, whose structural elements are relevant to payroll accounting and accounting.

Organization UnitAn object used to depict the basic structure of an organization.Organizational units are functional units of a company. Depending on how tasks are distributed at a company, organizational units can be departments, groups or project teams.Organizational units are different from other entities at a company such as personnel areas, company codes, and business areas. These are used to depict administrative or accounting structures in the corresponding components.



Payroll AreaA group of employees included in the same payroll run.A payroll area is used to group employees together who have the same payroll periodicity, for whom the payroll runs at the same time, who have the same payment date, and to whom the same earliest possible retroactive accounting period applies. Examples:

• Payroll area Salaried Employees (monthly payroll run on 25th of each month)

• Payroll area Retired Employee (monthly payroll run on 20th of each month)

• Payroll area Weekly Wage Earners (weekly payroll run on each Friday)

Personnel AdministratorPortal role that performs all tasks related to managing employees. He or she primarily performs personnel services, management and advising tasks for the specialist fields. Typical tasks in this area are:• Administrating/changing HR master data, (such as new hires, salary

changes, transfers, employees on leave, and so on) • Administrating personnel appraisals • Processing organizational data • Year-end closing work • Statements and providing information • Creating diverse, sporadic required evaluations • Advising all employees, retired employees, and managers Other personnel management tasks such as anniversaries/birthdays, cooperating with the organization, or performing work's council and spokespersons' committee elections, cooperating with the mass creation of messages, and so on.

Personnel AreaA personnel area is an organizational entity representing an area within an enterprise defined by specific aspects of personnel administration, time management and payroll.Personnel areas are subdivided into personnel subareas.

Personnel SubareaAn organizational entity that represents part of a personnel area.It is delimited according to personnel administration, time management, and payroll accounting criteria.



Work ContractWork (Employment) Contract descriptive attributes from T542T.

Common Dimensions MatrixBecause 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 BENEFIT_ENROLL_SUMMARY_FACT



EMPLOYEE_WAGE_FACT


PAYROLL_FACT


Benefit Area X X XBenefit Plan X X XBenefit Program Group

2 2 2

Benefit Spending Account

X

Benefit Termination Rule

X X X

Business Area X X X X X XCertificate Type XCompany Code X X X X X X XContribution Rule

2 2

Controlling Area X X X X X X XCost Center & Hierarchy

X X X X X X X

Country Group X X X X X XCountry Group Status

X X X X X X

Currency Benefit

X X X X X X

Dependent Coverage

X



Education Type XEligibility Rule X X XEmployee X X X X X XEmployee Group

X X X X X X

Employee Subgroup

X X X X X X

Enrollment Type XEthnic Origin XGender XHealth Plan XIdentification Type

X

Insurance Coverage Group

X

Insurance Option

X

Investment Group

X X

Investment Plan X XJob X X X X X XLanguage XLeave Type XLine Manager Hier

X X X X X X

Marital Status XMilitary Status XNationality XOrganization Key

X X X X X X




EMPLOYEE_WAGE_FACT


PAYROLL_FACT




Organization Unit & Hierarchy

X X X X X X X

Pay Scale Area X XPay Scale Type X XPayroll Area X X X X X XPayroll Cumulation Type

X

Payroll Period X XPayroll Period Parameter

X X

Payroll Status X XPayroll Type X XPersonnel Action Reason

X

Personnel Action Status

X

Personnel Action Type

X

Personnel Administrator

X X X X X X

Personnel Area X 2 X X X X XPersonnel Date Type

X

Personnel Subarea

X X X X X X X

Personnel Task Status

X

Personnel Task Type

X

Position & Hierarchy

X X X X X X

Proficiency X




EMPLOYEE_WAGE_FACT


PAYROLL_FACT




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.

Qualification XReligion XResidence Status

X

Salary Range X XSchool Type XService Interval Hr

X

Study Branch XTime Dim X X X XTime Management Status

X

Unit Of Time X X X XVesting Rule X XWage Type X X X XWork Calendar XWork Contract X X X X X XWork Contract Type

X

Work Permit Type

X




EMPLOYEE_WAGE_FACT


PAYROLL_FACT




Employee AdministrationThe employee administration subject area of this Rapid Mart allows you to analyze information about employee attributes, such as age, length of service, and annual salary, and about employee events, such as deadlines and other significant dates. Additional analyses of employee demographics (age, marital status, education, qualifications, etc.) is also available.Read on for descriptions of Employee Administration classes in the SAP Human Resources universe.

Employee MeasuresThe Employee measures contain all additive and semi-additive measures. These can be used by any subject area joining to the Employee dimension, but are most pertinent to Employee Administration. They appear as shown below in the universe:

There are only 2 measures for Employee: Employee Count and Average Age.


Employee Administration Measures
The Employee Administration measures contain all additive and semi-additive measures. They appear as shown below in the universe:

Employee Administration contains the following sub-classes are included to group like measures.

• Employee Administration - Count Measures - aggregated counts for number of current employees, terminated employees, new hires, FTE, PTE, and current positions. All these measures are also available as Point in Time values prompted to check records as of a prompted validity date.



• Employee Administration - (Benefit Currency) Measures - aggregated salary, pre-tax savings, post-tax savings, education costs, and other amounts in benefit currency.

• Employee Administration - Length of Service Measures - aggregated length of service measures. Includes average and maximum length of service, and also calculates number of employees by pre-defined intervals (0 - 6mo, > 6 mo, 1-3 yrs, etc.).

• Employee Administration - Percent Measures - aggregated percentage metrics including average investments, pre-tax savings, post-tax savings, and annual salary increase.

• Employee Administration - Qty Measures - aggregated quantities related to employee administration.

• Employee Administration - Time Measures - aggregated hours per day, hours per week, hours per period, and hours per year. All measures are available as total, average, minimum, and maximum.

Employee Administration Subject Area ClassesThe Employee Administration subject area classes contain all objects for Employee Administration. They appear as shown below in the universe

EMPLOYEE ADMINISTRATIONContains primary key elements for employee administration and the following sub-classes:• Employee Admin - Additional Details (Ids) - the foreign keys to the

various associated dimensions



• Employee Admin - Additional Details (Descriptive) - descriptive attributes including the various “flags”

• Employee Admin - Dates and Fiscal Periods - dates associated with the Employee Administration, including birth date, original hire date, departure date, etc.

• Employee Admin - Values - all numeric and time values related to Employee Administration, including (no aggregation).• Employee Admin - Benefit Currency Values - Salary, pre-tax

savings, post-tax savings, education costs, and other amounts in benefit currency.

• Employee Admin - Quantities - quantities related to employee administration

• Employee Admin - Time - length of service, minimum/maximum/total hours per day, week, month, or year (no aggregation).

Employee Administration Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the Universe Designer.



Employee WageEmployee Wage provides employee wage information (wage types, pay scales, etc.) with certain organizational aspects (position, organization, job, etc.). Payment amounts for each Wage Type are the key measure in this section.Note: The key difference between the Employee Wage and the Payroll is that Employee Wages shows history of the gross wage or salary amounts from the perspective of your organization’s pay and deduction structures and internal set-upRead on for descriptions of Employee Wage classes in the SAP Human Resources universe.

Employee Wage MeasuresThe Employee Wage measures contain all additive and semi-additive measures for Employee Wage. They appear as shown below in the universe:

Employee Wage Measures includes number of current employee records. It also contains the following sub-classes are included to group like measures:• Employee Wage - Qty Measures - aggregated (total, average,

minimum, maximum) wage quantity unit.• Employee Wage - (Benefit Currency) Measures - aggregated (total,

average, minimum, maximum) payment amounts.


Employee Wage Subject Area Classes
The Employee Wage subject area classes contain all remaining objects for Employee Wage. They appear as shown below in the universe

EMPLOYEE WAGEContains primary key elements for Employee Wage and the following sub-classes:• Employee Wage - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Employee Wage - Additional Details (Descriptive) - descriptive

attributes including the various “flags” • Employee Wage - Dates and Fiscal Periods - dates associated with the

employee wage payments, including first payment date and origin date.• Employee Wage - Values -

• Employee Wage - Benefit Currency Values - payment amount (no aggregation).

• Employee Wage - Quantities - wage quantity (no aggregation).

Employee Wage Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the Universe Designer


Benefit Enrollment Detail
Benefit enrollment details allow for analysis of employee enrollment in company benefits. Benefit enrollment details provide plan details by employee, as well as, other information relevant for eligibility and benefits usage.

Benefit Enrollment Detail MeasuresThe Benefit Enrollment Detail measures contain all additive and semi-additive measures for Benefit Enrollment Details. They appear as shown below in the universe:

The following sub-classes are included to group like measures.• Benefit Enrollment - Benefit Currency Measures - aggregated

benefit enrollment amounts including employee, employer, and provider benefit plan contributions and insurance coverage amounts.

• Benefit Enrollment - Count Measures - aggregated counts including number of employees, employees at a prompted point in time, (total, average, maximum) number of beneficiaries and dependents, count of benefit plans, and quantity of additional insurance units.

• Benefit Enrollment - Percent Measures - average percentage amounts relating to investments and pre-tax/post-tax savings.



Benefit Enrollment Detail Subject Area ClassesThe Benefit Enrollment Detail subject area classes contain all objects for Benefit Enrollment Detail. They appear as shown below in the universe

BENEFIT ENROLLMENTContains primary key elements for service notification and the following sub-classes:• Benefit Enrollment - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Benefit Enrollment - Additional Details (Descriptive) - descriptive

attributes including the various “flags” • Benefit Enrollment - Dates and Fiscal Periods - dates associated with

the Benefit Enrollment details.• Benefit Enrollment - Values - all numeric values and time amounts

related to Benefit Enrollment details• Benefit Enrollment - Benefit Currency Values - Benefit enrollment

amounts including employee, employer, and provider benefit plan contributions and insurance coverage amounts (no aggregation).



• Benefit Enrollment - Count Values - counts including number of employees, employees at a prompted point in time, (total, average, maximum) number of beneficiaries and dependents, count of benefit plans, and quantity of additional insurance units (no aggregation).

• Benefit Enrollment - Percent Values - percentage amounts relating to investments and pre-tax/post-tax savings (no aggregation).

Benefit Enrollment Detail Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the Universe Designer.

Benefit Enrollment SummaryBenefit Enrollment Summary allows for benefit enrollment analysis at a summarized level, including benefit plan, company, organization unit, and personnel area.



Benefit Enrollment Summary MeasuresThe Benefit Enrollment Summary measures contain all additive and semi-additive measures for Benefit Enrollment Summary. They appear as shown below in the universe:

The following sub-classes are included to group like measures.• Benefit Enroll Summ - Benefit Currency Measures - aggregated

benefit enrollment amounts including employee, employer, and provider benefit plan contributions and insurance coverage amounts.

• Benefit Enroll Summ - Count Measures - aggregated counts including number of employees, employees at a prompted point in time, (total, average, maximum) number of beneficiaries and dependents, count of benefit plans, and quantity of additional insurance units.

• Benefit Enroll Summ - Percent Measures - average percentage amounts relating to investments and pre-tax/post-tax savings.


Benefit Enrollment Summary Subject Area Classes
The Benefit Enrollment Summary subject area classes contain all remaining objects for Benefit Enrollment Summary. They appear as shown below in the universe

BENEFIT ENROLLMENT SUMMARYContains primary key elements for Benefit Enrollment Summary and the following sub-classes:• Benefit Enroll Summary - Additional Details (Ids) - the foreign keys to

the various associated dimensions• Benefit Enroll Summary - Additional Details (Descriptive) -

descriptive attributes including the various “flags” • Benefit Enroll Summary - Dates and Fiscal Periods - dates associated

with the Benefit Enrollment summary.• Benefit Enroll Summary - Values - all numeric values and time amounts

related to Benefit Enrollment summary.



• Benefit Enroll Summary - Benefit Currency Values - Benefit enrollment amounts including employee, employer, and provider benefit plan contributions and insurance coverage amounts (no aggregation).

• Benefit Enroll Summary - Count Values - counts including number of employees, employees at a prompted point in time, (total, average, maximum) number of beneficiaries and dependents, count of benefit plans, and quantity of additional insurance units (no aggregation).

• Benefit Enroll Summary - Percent Values - percentage amounts relating to investments and pre-tax/post-tax savings (no aggregation).

Benefit Enrollment Summary Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the Universe Designer


Leave Entitlement
Leave Entitlement allows for analysis of employee absences, such as vacations, sick leave, jury duty, maternity leave, etc. View leave accounted vs. leave entitled vs. leave deducted.

Leave Entitlement MeasuresThe Leave Entitlement measures contain all additive and semi-additive measures for Leave Entitlements. They appear as shown below in the universe:

Leave Entitlement contains measures for number of current employees and number of work days. It also contains the following sub-classes are included to group like measures:• Leave Entitlement - Time Measures

• Leave Entitlement - Leave Accounted Measures - (aggregated) total, average, maximum, and minimum days of leave accounted.

• Leave Entitlement - Leave Entitled Measures - (aggregated) total, average, maximum, and minimum days of leave entitled.

• Leave Entitlement - Leave Deducted Measures - days and hours leave deducted aggregated as total, average, minimum, and maximum.



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

LEAVE ENTITLEMENTContains primary key elements for Leave Entitlements and the following sub-classes:• Leave Entitlement - Additional Details (Ids) - the foreign keys to the

various associated dimensions• Leave Entitlement - Additional Details (Descriptive) - descriptive

attributes including the various “flags” • Leave Entitlement - Dates and Fiscal Periods - dates associated with

the Leave Entitlement including leave start, leave end, and various validity dates.

• Leave Entitlement - Values• Leave Entitlement - Benefit Currency Values - amount leave

accounted and leave entitlement are here, but truly are time-related rather than currency values. There are no currency values for leave entitlement.

• Leave Entitlement - Time - days and hours leave deducted (no aggregation). Amount leave accounted and amount leave entitlement objects belong here.


Leave Entitlement Star Schema Layout
Here is a graphical representation of the star schema for this subject area as it appears in the Universe Designer.

Payroll DetailPayroll detail aids in wage type analysis. Each payment or deduction in a pay check is a wage type. Typically, a company’s payroll process calculates remuneration based on wage types and a country-specific set of rules. Companies cumulate wage types that represent individual payments or deductions to determine gross pay. Payment wage types include basic pay, bonuses, special pay, and so forth. Net pay calculations handle country-specific adjustments to gross pay. Adjustments and deductions may be voluntary, such as charitable contributions, or statutory, such as taxes. Finally, the payroll process combines results of previous payroll runs with the current results to get cumulative gross and net pay amounts.Note: The Payroll section is designed to meet U.S. payroll requirements. Customization of the Rapid Mart is required for other countries.



Payroll Detail MeasuresThe Payroll Detail measures contain all additive and semi-additive measures for Payroll Details. They appear as shown below in the universe:

Payroll measures include number of employees and number of units. The following sub-classes are included to group like measures:• Payroll - (Benefit Currency) Measures - aggregated total, average,

minimum, and maximum payroll amounts.

Payroll Detail Subject Area ClassesThe Payroll detail subject area classes contain all remaining objects for Payroll Details. They appear as shown below in the universe



PAYROLL DETAILContains primary key elements for Payroll and the following sub-classes:• Payroll - Additional Details (Ids) - the foreign keys to the various

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

including the various “flags”.• Payroll - Dates and Fiscal Periods - dates associated with the payroll

including, payroll date, payroll run date, payroll period start, payroll period end, etc.

• Payroll - Values• Payroll Detail - Benefit Currency Values - payroll amount (without

aggregation).

Payroll Detail Star Schema LayoutHere is a graphical representation of the star schema for this subject area as it appears in the Universe Designer

Payroll SummaryPayroll Summary uses Payroll Detail data to create a summarization based on Cumulation Year, Cumulation Period, and Cumulation type. This data can be used for a higher level analysis rather than employee level analysis.



Payroll Summary MeasuresThe Payroll Summary measures contain all additive and semi-additive measures for Payroll Summary. They appear as shown below in the universe:

Payroll Summary measures includes number of units. The following sub-classes are included to group like measures:

• Payroll Summary - (Benefit Currency) Measures - aggregated total, average, minimum, and maximum payroll amounts.

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

PAYROLL SUMMARYContains primary key elements for Payroll Summary and the following sub-classes:



• Payroll Summary - Additional Details (Ids) - the foreign keys to the various associated dimensions

• Payroll Summary - Additional Details (Descriptive) - descriptive attributes including the various “flags”.

• Payroll Summary - Dates and Fiscal Periods - dates associated with the payroll including, payroll date, payroll period start, payroll period end, etc.

• Payroll Summary - Values• Payroll Summary - Benefit Currency Values - payroll amount

(without aggregation).

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



Filters & Techniques

FiltersThe SAP Human Resources 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.

Benefits FiltersConditions to limit benefits analysis to single or multiple benefit plans, benefit areas, or benefit plan types.

Benefits Enrollment FiltersConditions to limit benefits enrollment analysis to current detail records, a point in time, or records valid between a prompted range.

Company Code FiltersConditions to limit result set to either a single or multiple Company Codes.

Employee FiltersConditions to limit employee results set to only current employees (based on current flag in EMPLOYEE dimension).

Employee Administration FiltersConditions to limit employee administration analysis to current records, a point in time, or records valid between a prompted range.

Employee Wage FiltersConditions to limit employee wage analysis to current records, a point in time, or records valid between a prompted range.

Hierarchy FiltersAll hierarchy filters provide two groups of conditions “Limit to Single Parent” and “Limit to Multiple Parent” sub-classes. Each of the conditions provided here allows the user to choose the level of the parent node (0 - 4) in the hierarchy tree. This universe provides the following hierarchy filters:• Cost Center Filters - Limit result set to a single or multiple Cost

Center parent node(s)• Organization Unit Filters - Limit result set to a single or multiple

Organization Unit parent node(s)• Position Filters - Limit result set to a single or multiple Position

parent node(s)



Leave Entitlement FiltersConditions to limit leave entitlement analysis to current records, a point in time, or records valid between a prompted range.

Payroll FiltersConditions to limit payroll detail analysis to a single payroll run date, payroll date, or records where either of those dates falls between a prompted range.

Payroll Summary FiltersConditions to limit payroll summary results set to a single cumulation year.

Personnel Area FiltersConditions to limit the result set to a single or multiple personnel area(s).

Personnel Subarea FiltersConditions to limit the result set to a single or multiple personnel sub-area(s).

TechniquesTechniques are advanced technique objects developed for the Web Intelligence reports. They are described in “Techniques” on page 17.

Sample Measuresthe SAP Human Resources Rapid Mart is highly customizable as is the Human Resources module in SAP solutions. This translates to a reality the that many customer metrics required for complete analysis of Human Resources data will also be customizable. To that end, the SAP Human Resources universe includes some sample measures based on IDES data. These measures are included in the IDES US INC Sample Employee Wage measures class, and as samples of how to analyze specific wage types for the Employee Wage subject area.



Note: These will need to be measures will require customization to use wage types specific to a customer implementation.

IDES US INC Sample - Salary MeasuresMeasures in this sample class are limited to WAGE_TYPE_ID in ('1002','M002','M003'). These are the salary-related wage types in the Wage type dimension, as loaded from IDES sample data.

IDES US INC Sample - Bonus MeasuresMeasures in this sample class are limited to WAGE_TYPE_ID in ('M101','1110','CM03','1053','9M11'). These are the bonus-related wage types in the Wage type dimension, as loaded from IDES sample data.

IDES US INC Sample - Hourly Rate MeasuresMeasures in this sample class are limited to WAGE_TYPE_ID in ('M001','1000','1001'). These are the hourly rate-related wage types in the Wage type dimension, as loaded from IDES sample data.

Universe ValidationWhen validating the universe within the Universe Designer, some errors are expected and acceptable. They do not harm universe performance in any way. They are detailed below.



Integrity Check Results.

Structure DivergencesSome tables are not joined to other tables. This is because we use only aliases of those tables in the universe. However, the original table must remain as a placeholder for the original table name. Also, validation tables (those ending in “_BAD”) are not joined to other tables.

Object Parsing ErrorsThese objects are in the Techniques section and are represented by valid SQL. These objects are included in the universe to accommodate advanced reporting techniques primarily in Web Intelligence and will work properly when used with other objects in a query.

Cardinality DivergencesThese are caused by the use of the “@prompt” function in the join. Since this function requires user intervention to complete the SQL join condition, the Universe Designer cannot check the cardinality vs. the database. The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.


UniverseSAP HR Master Data Universe5
SAP HR Master Data Universe
The HR Master Data Universe contains master Infotype data from SAP solutions Human Resources module. Various other dimensions are also included for analysis as they are not incorporated into the business content universe. The purpose of this universe is for data browsing, particularly for browsing infotype data.The HR Master Data universe is a reflection of this complexity. At this writing, it has:• 45 classes• 1264 objects• 9 conditions• 34 tables• 0 alias• 35 joins• 0 contexts• 2 hierarchiesThe universe is well documented and logically organized to help universe users easily navigate to a specific object.The information in this chapter is useful to understand the data in the Rapid Mart and how to build reports using the data. The universe, and this chapter, are logically grouped into subject areas. They are:• Universe Objects & Classes• Universe Design• Dimensions• Infotype Tables• Filters & Techniques• Universe Validation


UniverseSAP HR Master Data Universe 5

Universe Objects & ClassesAll Rapid Mart dimension and infotype 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



Dimensions: These are the dimensions included for data browsing. As the intent of this universe is for data browsing, they are not joined to any tables. Infotype Tables: Infotype tables are used throughout the Human Resources module to and provide a set of data grouped according to subject matter.The Human Resources component aims to enable the user to process employee data in an effective structure in accordance with business requirements. The data structure of infotypes mirrors a logical set of data records. Infotypes can be identified by their four-digit keys, for example, the Addresses infotype (0006).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 17 for details.

Universe DesignThis universe does not follow the typical design conventions used by other universes in the SAP BusinessObjects Rapid Mart Suite for SAP. Most notably:• the universe does not follow a star schema• TIME_DIM is the only dimension joined to other tables, and is joined via

CHANGE_DATE to most tablesExample: TIME_DIM.CALENDAR_DATE = HR_INFOTYPE_0000_ACTION.CHANGE_DATE

DimensionsThe following table describes the function of each dimension class:

Class Name Description

Benefit Cost Rule Benefit Cost rule details from T5UBH, T5UBI, T5UCH

Holiday Calendar Public holidays calendar - THOCInsurance Coverage Rule Benefit insurance coverage rules and

formulas from T74FB, T74FC, PA0168 (date-effective)



Infotype TablesThe following table describes the function of each of the infotype classes:

Time Dim Time Dimension (Daily)Work Calendar Calculated calendar based on

Holiday calendar



Hr Infotype 0000 Action Employee Events records from Infotype PA0000

Hr Infotype 0001 Assignment HR Master Data: Organizational Assignment from PA0001

Hr Infotype 0002 Personal HR master data - infotype PA0002 -- Personal data

Hr Infotype 0005 Leave HR master data from PA0005 infotype - Leave Entitlement;

Hr Infotype 0006 Address Load Personnel Address and Communications master data from PA0006, PA0105

Hr Infotype 0007 Worktime HR Master data: Planned Working Time from PA0007

Hr Infotype 0008 History Uses HR_INFOTYPE_0008_PAY to create a salary history that stores prior salary, and salary one year ago;

Hr Infotype 0008 Pay HR Master data - Basic Pay from PA0008

Hr Infotype 0014 Deduction HR Master Data, Recurring Deductions from PA0014

Hr Infotype 0015 Payment HR Master data: Infotype for additional payments, PA0015

Hr Infotype 0016 Contract HR Master Data for Contract information from PA0016 infotype

Hr Infotype 0019 Dates HR Master data: Monitoring of Dates infotype from PA0019

Hr Infotype 0021 Dependent HR master data - infotype PA0021 -- Dependents Personal data



Hr Infotype 0022 Education HR Master data: Education from Infotype PA0022

Hr Infotype 0024 Qualification HR infotype Master PA0024 - Personnel Qualifications

Hr Infotype 0041 Spec HR Master: date specification inforecord PA0041

Hr Infotype 0077 Personal HR Master for Additional Personal Data from PA0077

Hr Infotype 0094 Residence HR Master for Residence status in N/A from PA0094

Hr Infotype 0167 Health HR Master: Health Plans from Infotype PA0167

Hr Infotype 0168 Insurance HR Master for Insurance Plans from infotype PA0168

Hr Infotype 0169 Savings HR master data for Savings Plan from Infotype 0169

Hr Infotype 0170 Flex HR Master data for Flexible Spending Accounts from infotype PA0170

Hr Infotype 0171 Benefit HR Master data for General Benefits from infotype PA0171

Hr Infotype 0236 Credit HR Master data for Credit Plans from infotype PA0236

Hr Infotype 1000 Dbtable HR Master data for Organizational unit descriptions from the active plan from HPR1000 infotype

Hr Infotype 1001 Dbtable HR master data - HR objects details from infotype HRP1001

Hr Infotype 1007 Dbtable HR master data - HR objects details from infotype HRP1007

Hr Infotype Validation Derived by Data Services Job: Distinct Merge of date-effective records from all infotypes

Leave Deduction Deduction detailed data from PCL1 where RELID = PC - Personal Calendar




Filters & Techniques

FiltersThe SAP Capacity Planning and MRP 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.

Infotype 0000 Action FiltersConditions to limit Infotype 0000 Action analysis to current detail records, a point in time, or records valid between a prompted range.

Infotype 0001 Assignment FiltersConditions to limit Infotype 0001 Assignment analysis to current detail records, a point in time, or records valid between a prompted range.

Infotype 0008 Action FiltersConditions to limit Infotype 0008 Pay analysis to current detail records, a point in time, or records valid between a prompted range.

TechniquesTechniques are advanced technique objects developed for the Web Intelligence reports. They are described in “Techniques” on page 17.


Universe Validation
When validating the universe within the Universe Designer, some errors are expected and acceptable. They do not harm universe performance in any way. They are detailed below.

Integrity Check Results.



Cardinality DivergencesThese are caused by the use of the “@prompt” function in the join. Since this function requires user intervention to complete the SQL join condition, the Universe Designer cannot check the cardinality vs. the database.The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.


UniverseSAP Master Data Universe5
SAP Master Data Universe
The SAP Master Data universe defines a common class structure and contains common master data dimension objects, techniques, and conditions used by all Rapid Mart universes in the SAP BusinessObjects Rapid Mart Suite for SAP.This universe is designed to facilitate Rapid mart universe integration and customization, master data discovery, and auditing hierarchy structures in SAP solutions.In the business content universes these hierarchies and master data are dimension tables joined to one or more fact tables. The SAP Master Data universe contains no fact tables. Therefore, it is not organized as a star schema.All hierarchies, except Material (Product) Hierarchy, are organized both horizontally and vertically. The SAP Master Data universe also provides reports to identify Invalid Hierarchies. These are hierarchy records that have failed validation in Data Services.The SAP Master Data universe, at this writing, has:• 394 classes• 4100 objects• 199 conditions• 261 tables• 44 alias• 36 joins• 0 contexts• 26 hierarchiesThe universe is well documented and logically organized to help universe users easily navigate to a specific object.

Universe Objects & Classes - Master DataAll Rapid Mart dimension columns are exposed as objects. Universe Objects are grouped in folders and sub-folders. These folders and sub-folders are also called classes. The classes, sub-classes and all objects they contain are organized alphabetically for ease of navigation. The top level classes are shown below


UniverseSAP Master Data Universe 5

Top Level Classes



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

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

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

BENEFITSIn HR, these are the various employee benefits including health insurance and savings plans as well as the rules associated with the plans. The class carries the following sub-classes:

Benefit AreaThe highest-level subdivision of benefits data.Benefit areas enable different pools of benefit plans to be administered separately, for example, to reflect geographical location, departments, or production areas.Employees are sorted into benefit areas during processing, according to the corresponding feature.Example: The medical benefits offered by a company in the chemical industry are organized according to production areas. Employees in plastics production have different plans to employees in fertilizer production. Each production areas is represented by a benefit area.

Benefit PlanThe central element of the Benefit Administration component, representing a single benefit offered by the employer. A plan belongs to a plan category, and is defined by the following:• General plan data (for example, provider)• Any relevant plan options (for example, health plan coverage,

investments)• Rules determining the calculation of monetary amounts relating to

plans (for example, costs, contributions, coverage, credit)• Plan-specific checks (for example, evidence of insurability)



Benefit Program GroupA set of benefit plans offered to a specific group of employees.Benefit programs are defined for one, or a combination of two program groupings, and therefore control high-level eligibility. Low-level eligibility in controlled by the eligibility rules assigned to the individual plans within a program.

Benefit Spending AccountA benefit plan that allows employees to set aside tax-free dollars for anticipated medical care and dependent care expenses. Flexible spending accounts are available in North America only.

Dependent CoverageAn option for a health plan, chararacterized by the number of dependents that can be covered.

Enrollment TypeBenefit program enrollment type descriptive attributes from DD07T, BEN_ENRTYP domain. A -Automatic, D - Default, M - Manual.

Health PlanHealth Plan descriptive attributes from T5UCE

Insurance Coverage GroupBenefit insurance coverage rules and formulas from T74FB, T74FC, PA0168 (date-effective)

Insurance OptionThis is the insurance plan option, within the insurance plan.

Example: The Standard Life plan has 2 options, which the employee selects the desired coverage from: HIGH - $120,000 option; LOW - $80,000 option

Investment GroupA customer-defined group of investments that can be assigned to plans in the categories 'Savings' and 'Miscellaneous'.

Investment PlanA customer-defined option for plans in the categories Savings and Miscellaneous that lets employees choose how their contributions are invested.



BENEFIT RULESIdentifying rules for benefits participation and contribution. Sub-classes include: Benefit Termination Rule, Contribution Rule, Eligibility Rule, and Vesting Rule.

BILL OF MATERIALS (BOM)A formally structured list of the components that make up a product or assembly. The list contains the object number of each component, together with the quantity and unit of measure.BOMs are used in their different forms in various situations where a finished product is assembled from several component parts or materials. Depending on the industry sector, they can also be called recipes or lists of ingredients and so on.They contain important basic data for numerous areas of a company, for example:

• MRP• Material provisions for production• Product costing• Plant maintenance

Bill of Materials Item CategoryPart of a bill of material containing information about the quantity and unit of measure of a component. According to the object referred to (for example, material or document) and other criteria (such as inventory management criteria), BOM items are defined in different item categories that determine which item data is managed.

Bill of Materials StatusA tool used to control processing of a BOM in different application areas.

Bill of Materials UsageA tool that allows you to enter BOMs, for example, for material LAMP, for specific sections of your company. You can enter a separate BOM for each section in your company, for example, production, so that each section only processes the items relevant to that section. The usage is an important selection criterion in the BOM application, which controls the automatic explosion of BOMs.

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



Capacity by Work CenterStandard work center capacity information from CRCA/CRHD/KAKO.

Capacity CategoryA description that classifies a capacity at a work center. A capacity category can exist only once at each work center. However, capacities at different work centers can have the same capacity category. Capacity category descriptions from TC26T.

Capacity Object TypeCapacity Object Type (like Order, Task List) - from DD07T TYPKZ domain.

Capacity Planning GroupCapacity planner group descriptive attributes (from TC27T).

CENTRAL ADDRESSThis is the Central Address repository (table ADRC) in SAP. Currently, it is used to store Customer Ship-To addresses for sales orders and billings (Sales Rapid Mart). But, can be easily expanded to show addresses associated with purchase orders, vendors, etc.

CLASSIFICATIONSSystem that is used to describe objects on the basis of characteristics by grouping together into classes (i.e. classifying) objects according to freely definable criteria.Objects can be retrieved with the aid of classes and the characteristics defined in the classes, enabling objects that are identical or similar from a point of view of their characteristics to be retrieved as quickly as possible.We carry two sets of Classification data for:

• Equipment Classification• Functional Location Classification

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

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



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

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

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

Customer by CompanyIntersection of Company and Customer records. Used by both Customer Items and Customer Totals

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

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

• Accounting Document Category - Domain DOCCT in SAP solutions.

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

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



• Purchase Document Category - Broadly categorizes purchase documents as “requisitions”, “purchase orders”, “contracts” etc.

• Sales Document Category - One of a set of classes used to control how the system processes a sales document in the sales and distribution component module. Sales document categories include:- Inquiries and quotations - Sales orders - Outline agreements

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

• Billing Document Type - indicates type of billing document• Delivery Document Type - indicates type of delivery document• Financial Document Type - Records what the posting was for.

Examples: Goods Issue, Goods Receipt, Asset posting, Vendor Payment, Customer Payment

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

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

• Purchase Document Type - A further subdivision of Purchase Document Categories.



• Sales Document Type - A categorization of a Sales Document as an invoice, credit memo, debit memo, pro forma invoice, or cancellation document.

• Special Ledger Document Type - Document Type (tables T889 and T889TE)

Reference Date KeyKey determining the reference date for various entities - Milestone, PRT - Domain MLST_SDDAT; TCA55

Special Stock IndicatorStock of materials that must be managed separately for reasons of ownership or location. An example is consignment stock from vendors.

Standard Text KeyStandard text Key descriptions for activities from T435T.

Standard Value KeyCapacity Standard Value Key descriptive attributes from TC21T.

Valuation TypeThe basic criterion for calculating the asset value. In a depreciation area, in addition to the acquisition and production costs and ordinary depreciation, the following special valuation types can be calculated: Revaluation, Investment support measures, Special depreciation, Unplanned depreciation, Transfer of reserves, and Interest.

ACCOUNTING DOCUMENT ATTRIBUTES• Bank Account Information - Bank account details defined by

account.• Controlling (Business) Transaction Type - Cost Accounting

(or business) transaction types. Examples: cost planning, invoice posting, or overhead calculation.

• Debit Credit Indicator - From Domain SHKZG. Values: H = Credit, S = Debit

• Financial Document Status - Status (from Domain BSTAT), indicates if a financial document is a normal, clearing or parked document.

• Financial Management Area - FM01T - Funds Management Area Texts.

• Financial Record Category - Categorization for a financial document.



• Financial Record Type - Special Ledger Record Types (Domain RRCTY) from table DD07T and Cost/Plant Maintenance value types from CO_WRTTP domain of DD07T table

• Financial Version - Special Ledger Version (T894T table in SAP solutions)

• Ledger Group - A combination of ledgers for the purpose of applying the functions and processes of general ledger accounting to the group as a whole.

• Payment Block - An indicator that allows you (by entering a payment block) to block an account or individual items for payment. The payment blocking indicator is placed in the customer or vendor's master record, or in the line item. from table T008T - indicates any Holds preventing payment to a vendor.

• Payment Reason - From table T053S - Classification of Payment Differences (Texts)

• Payment Term - Relevant only for Financial Documents, describes when payments to a vendor or from a customer are due. Also describes any discounts associated with early payment.

• Posting Key Type -The posting key defines if it is a debit or credit posting, and which account type (customer or vendor) is posted. The posting keys for special G/L transactions must be indicated as such.

• Reference Procedure - Object Type Names for Accounting (TTYPT).

• Segment - A division of a company that can create its own financial statements for external reporting. A segment can be entered in the master record of a profit center. The segment is then derived from the assigned profit center during posting. This is the business segment. It is available in New GL only (release ECC 5.0 or higher).

• Special GL Indicators - Special G/L transactions are special transactions in accounts receivable and accounts payable that are displayed separately in the general ledger and the subledger. This is achieved by posting to alternative reconciliation accounts, instead of posting to the reconciliation accounts for receivables and payables.

• Special Ledger Master - Identifies the Standard or Special Ledger used.



• Transaction Type - Transaction type of the Financial Document from table T856T.

PURCHASING DOCUMENT ATTRIBUTES• Account Assignment Category - A key indicating whether an

item is to be assigned to an auxiliary account (such as a cost center). The account assignment category determines which account assignment details are required for the item (for example, cost center or account number).

• Condition Type - Identification that defines characteristics, attributes, and business meaning of a condition. The system can, for example, contain different condition types for free-goods, sales-based rebate, or gross price discount. Every condition type has its own access sequences, condition tables, and condition records.

• Purchase Document Price History - A series of prices charged or quoted by a vendor for a material or service over a certain period up to the present.

• Purchase Document Source - Describes where the purchase document originated (BAPI, RFQ conversion, Third Party, Kanban, etc.)

• Purchase Item Category - An identifier indicating the characteristics of an item. The item category determines whether the following are mandatory or admissible for an item:- Material number - Additional account assignment - Inventory management in the SAP solutions system - Goods receipt - Invoice receipt

SALES DOCUMENT ATTRIBUTES• Billing Block - A block that prevents the release of billing

documents to financial accounting. • Delivery Block - A block that prevents the release of products

for documents to financial accounting.• Delivery Route - Delivery route details.• Sales Order Status - Status descriptions for sales orders



EMPLOYEEIn HR, the employee class tracks information about employees such as name,address, birth date, Gender, Marital status, number of dependents, etc.

EMPLOYEE ATTRIBUTESAdditional information about the employee such as Personnel Actions, Education, Job Qualifications, Work Permit status, etc. This area contains the following sub-classes:

• Certificate Type• Education Type• Ethnic Origin• Gender• Identification Type• Language• Marital Status• Military Status• Nationality• Personnel Action Reason• Personnel Action Status• Personnel Action Type• Personnel Date Type• Personnel Task Status• Personnel Task Type• Proficiency• Qualification• Religion• Residence Status• School Type• Study Branch• Time Management Status• Work Permit Type



EQUIPMENTUsed in Plant Maintenance and Service modules of SAP. Individual, physical object that is to be maintained as an autonomous unit. Equipment can be internal, such as machinery in your factory used to manufacture goods for sale. Equipment can also be external, such as the machine that is manufactured and sold to your customer.

FUNCTIONAL LOCATIONOrganizational unit within Logistics that structures the maintenance objects of a company according to functional, process-oriented or spatial criteria. A functional location represents the place at which a maintenance task is to be performed.

GL ACCOUNTS and HIERARCHIES General Ledger accounts are a structure that records value movements in a company code and represents the G/L account items in a chart of accounts. The Debit / Credit Flag indicates a debit or credit posting.The accounts can be organized into various hierarchies, such as those need to produce Profit & Loss or other Financial Statements. Use the Hierarchy Data Discovery Class to explore these hierarchies. Additionally these dimensions include sub-classes that facility data discovery of the GL Account Hierarchies and Financial Statement (FS) Hierarchies, without linking to any fact table.

• GL Account• Hierarchy Data Discovery

• GL Account Discovery Hz• GL Account Discovery Vr• FS Hierarchy Discovery Hz• FS Hierarchy Discovery Vr

INTERCOMPANY TERM01Describes when in the delivery process the receiver of goods takes physical ownerships of the those goods.

INTERNAL ORDERSProduction Orders, Service Orders, and associated hierarchies. Object used to monitor costs and, in some instances, revenues for an organization. Internal orders can be used to:

1. Monitor the costs of short-term measures 2. Monitor the costs and revenues related to a specific service



3. Monitor ongoing costs Internal orders are divided into the following categories:

1. Overhead orders2. Capital investment orders 3. Accrual orders4. Orders with revenues.

Internal Order StatusInternal Order status name and description from TKO04.

JOB An organizational object that serves as a template for creating positions when you create an organizational plan.Unlike Positions that can be occupied by holders, for example, secretary in the marketing department. Jobs are a classification of functions in an enterprise, for example, secretary, defined by the tasks and characteristics assigned to them. Job descriptions apply to different positions with similar tasks and characteristics. This includes Exempt/Non-Exempt Status, Payscale, etc.

LEAVE Information about the types of leave (vacation, sick leave, maternity leave, etc.) an employee may have.

Leave TypeJob leave type descriptive attributes from T533T

MATERIALThe Materials Master in SAP R/3 and ERP. Goods that are the subject of business activity. The material can be traded, used in manufacture, consumed, or produced. They can also be bought or sold.This class also contains the following subclasses:

Material BatchBatch material management - Material Master from MCHA

Material by PlantMARA and MARC Tables - Plant Level Material attributes.

Material GroupA grouping of materials and services according to their characteristics.



Material (Product) HierarchyMaterials can be grouped into hierarchies. Every material (product) can be assigned to one material product hierarchy level.

Material ProductionDefines production version information (from MKAL).

Material TypeA grouping together of materials with the same basic attributes such as raw materials, semi-finished products, or finished products.All materials must be assigned to a material type which determines:• Whether the material is intended for a specific purpose such as a

configurable material or process material • Whether the material number can be assigned internally or externally • The number range from which the material number is drawn • Which screens appear and in what sequence • Which user department data you may enter • What procurement type the material has; that is, whether it is

manufactured in-house or procured externally, or both

MONETARY DIMENSIONS A medium of exchange in current use within a particular country to valuate goods and services. For example the US Dollar, the Euro, the Japanese Yen, etc. Contains the following sub-classes related to the valuation of various monetary currencies:

Currency SourcesCurrency Sources for 2nd and 3rd Local Currencies. The Currency source indicates which currency was used as a source for the 2nd or 3rd Local currency. The exchange rate is determined from this source currency to the 2nd or 3rd local currency. Standard Values:

• 1 = Translation taking first local currency as basis, i.e., the main Local Currency or Company Code Currency was used as the currency source.

• 2 = Translation taking transaction (or document) currency as basis.

Currency TypesCurrency Types for 2nd and 3rd Local Currencies. Key identifying the role of a currency in the R/3 System. In addition to the local currency as house currency, you can manage parallel currencies with the following currency types:



• Group currency • Hard currency • Index currency • Global company currency

Monetary CurrenciesThe Rapid Marts maintain various currencies, including:

• Benefit Currency - The monetary currency associated with personnel administration.

• Controlling Area Currency - The monetary currency assigned to the controlling area

• Group Currency - Group currency is used in the consolidated financial statements. Before the consolidation process can be completed all values in the individual financial statements must be translated from the local or transaction currency into group currency.

• Local (Company Code) Currency - The monetary currency assigned to the company code

• Transaction (Document) Currency - The monetary currency of each individual transaction document.

• Update Currency - Used for Euro conversion in European Union: The update currency is the currency, in addition to the local (company) currency, in which the transaction figures are updated in the general ledger. You specify whether the document or account currencies should also be the update currency in the G/L account master record.

Monetary Exchange RatesThese are the conversion rates used to convert one currency to another. They are used to compute global currency amounts in the universe.

MRPMaterial Resource Planning - A term for procedures in requirements planning that take into account and plan every future requirement during the creation of order proposals such as independent requirements, and dependent requirements. Contains the following sub-classes:

Mrp ControllerThe person responsible for a group of materials in MRP in a plant or company. Material that takes part in material requirements planning must be assigned to an MRP controller.



Mrp Element TypeA term for all objects displayed as items in the MRP list or in the stock and requirements list. Such objects include planned orders, purchase orders, reservations, and sales orders.

Mrp GroupThe MRP group, groups material from the material requirements planning point of view to allocate them control parameters for planning.The control parameters include the strategy group, the planning horizon and the creation indicator for the planning run.

Mrp Lot SizeA key that defines which lot-sizing procedure the system uses for calculating the quantity to procure in the MRP run.

Mrp ProfileA collection of data required for updating the material master record for planning. The MRP profile contains the necessary MRP data for the material master.This simplifies updating the material master record. When creating or changing a material master, the data in the MRP profile is copied automatically to the material master. The MRP profile defines:• Which fields are mandatory when entering MRP data • Values of these fields • Which values can be overwritten (default values) or not (fixed values)

Mrp TypeA key that controls the MRP procedure (MRP or reorder point) used for planning a material. It contains additional control parameters, for example, for using the forecast for the materials planning, or for firming procurement proposals.

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

Object ClassThe object class categorizes Controlling objects according to their business function and enables you to analyze cost flows within Controlling from different business perspectives. The following object classes are available: overhead, production, investment, profitability analysis and sales



While certain object types automatically belong to a particular class (for example, cost centers belong to the "Overhead" class), others need to be explicitly assigned to an object class in their master record (this is the case with internal orders and work breakdown structure elements, for example).In addition to the functional area, the object class is required to determine or explain certain values in the external accounting components. Object Class (from Domain SCOPE_CV).

Object Number TypeThe object type is the first two characters of the object number (from TBO01), which is a unique object key per client (order, cost center, project, etc.).

Object StatusObject statuses from JEST.

Object Status HzDimensional component loading horizontally represented selected ERP Object status information from JEST for selected Statuses from OBJECT_STATUS.

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

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

Account TypeA key that specifies the accounting area to which an account belongs. Examples of account types are:• Asset accounts • Customer accounts • Vendor accounts • G/L accounts The account type is required in addition to the account number to identify an account, because the same account number can be used for each account type.



Business ActivityBusiness activity attributes from T022/T022T.

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

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

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

Controlling AreaAn organizational unit within a company, used to represent a closed system for cost accounting purposes. A controlling area may include single or multiple company codes that may use different currencies. These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area.

Country GroupA grouping of countries for which the political restrictions or AFS quota are equally valid (e.g. EU). The grouping of countries facilitates the entry and processing of country-specific restrictions and AFS quota.



Credit Control AreaAn organizational unit that represents an area responsible for granting and monitoring credit. This organizational unit is either a single company code or, if credit control is performed across several company codes, multiple company codes. Credit information can be made available per customer within a credit control area.

Distribution ChannelCA channel through which saleable materials or services reach customers.Distribution channels include wholesale, retail, and direct sales. You can assign a distribution channel to one or more sales organizations.

DivisionAn organizational unit based on responsibility for sales or profits from saleable materials or services.

Employee GroupThe employee group is an organizational entity which is governed by specific personnel regulations. An employee group is divided into several employee subgroups.

Employee SubgroupAn employee subgroup is an organizational entity within an employee group which is governed by specific personnel regulations.

Functional AreaAn organizational unit in Accounting that classifies the expenses of an organization by functions such as:• Administration • Sales and distribution • Marketing • Production • Research and development Classification takes place to meet the needs of cost-of-sales accounting.

Line Manager HierarchyA person who holds a managerial position in a company or department and who makes decisions in an area of responsibility. Line managers can act as the first person responsible for applicant correspondence.



Organization (Structure) KeyA hierarchy in which the organizational units in an enterprise are arranged according to tasks and functions.The organizational structure differs from the administrative enterprise or personnel structure, whose structural elements are relevant to payroll accounting and accounting.

Organization UnitAn object used to depict the basic structure of an organization.Organizational units are functional units of a company. Depending on how tasks are distributed at a company, organizational units can be departments, groups or project teams.Organizational units are different from other entities at a company such as personnel areas, company codes, and business areas. These are used to depict administrative or accounting structures in the corresponding components.

Payroll AreaA group of employees included in the same payroll run.A payroll area is used to group employees together who have the same payroll periodicity, for whom the payroll runs at the same time, who have the same payment date, and to whom the same earliest possible retroactive accounting period applies. Examples:

• Payroll area Salaried Employees (monthly payroll run on 25th of each month)

• Payroll area Retired Employee (monthly payroll run on 20th of each month)

• Payroll area Weekly Wage Earners (weekly payroll run on each Friday)

Personnel AdministratorPortal role that performs all tasks related to managing employees. He or she primarily performs personnel services, management and advising tasks for the specialist fields. Typical tasks in this area are:• Administrating/changing HR master data, (such as new hires, salary

changes, transfers, employess on leave, and so on) • Administrating personnel appraisals • Processing organizational data • Year-end closing work • Statements and providing information



• Creating diverse, sporadic required evaluations • Advising all employees, retired employees, and managers Other personnel management tasks such as anniversaries/birthdays, cooperating with the organization, or performing work's council and spokespersons' committee elections, cooperating with the mass creation of messages, and so on.

Personnel AreaA personnel area is an organizational entity representing an area within an enterprise defined by specific aspects of personnel administration, time management and payroll.Personnel areas are subdivided into personnel subareas.

Personnel SubareaAn organizational entity that represents part of a personnel area.It is delimited according to personnel administration, time management, and payroll accounting criteria.

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

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

Plant LocationPlant location attributes.

Purchase GroupA key for a buyer or group of buyers responsible for certain purchasing activities. The purchasing group is internally responsible for the procurement of a material or a class of materials The principal channel for a company's dealings with its vendors.



Purchase OrganizationAn organizational unit responsible for procuring materials or services for one or more plants and for negotiating general conditions of purchase with vendors. The purchasing organization assumes legal responsibility for all external purchase transactions.

Sales DistrictA geographical sales district or sales region. You can assign customers to a sales district and use the sales district to generate sales statistics.

Sales GroupOrganizational unit that performs and is responsible for sales transactions. Constituent component in a distribution chain (with a sales manager per sales group, for example). Sales groups can be used for reporting purposes. In its capacity as a customer, a store can have a sales group assigned to it; this sales group is then responsible for sales to this store.

Sales OfficeA organizational unit in a geographical area of a sales organization. A sales office establishes contact between the firm and the regional market.Constituent component in a distribution chain (with a sales manager per sales group, for example). Sales groups can be used for reporting purposes. In its capacity as a customer, a store can have a sales group assigned to it; this sales group is then responsible for sales to this store.

Sales Org HierarchyHierarchy associated with Sales Organizations

Sales OrganizationA organizational unit in Logistics that structures the company according to its sales requirements. A sales organization is responsible for selling materials and services.

Storage LocationAn organizational unit that allows the differentiation of material stocks within a plant. The storage location is hierarchically situated between the plant and the warehouse number.

Supply AreaThe production supply area exists directly in the production area. You stage the material in the production supply area in productions storage bins, so that it can be removed directly for production.



The production supply area groups together work centers near to production storage bins, taking the material staging type into consideration.

Valuation AreaAn organizational unit in Logistics subdividing an enterprise for the purpose of uniform and complete valuation of material stocks.

WarehouseAn organizational division of a plant for managing materials stored in different places.

Work ContractA contract under private law in which the employee undertakes to work directly for the employer, and the employer undertakes to remunerate the employee.

PAYROLL and WAGES Information about the compensation and other payments an employee receives. Includes the following sub-classes:

Pay Scale AreaThe physical area of validity of a collective agreement.

Pay Scale TypeThe economic area to which a collective agreement applies, for example metal industry or the chemical industry.

Payroll Cumulation TypeDescriptive attributes for calendar-associated cumulation types.

Payroll PeriodPeriod for which regular payroll is run. A payroll period is identified by a period number and payroll year.

Payroll Period ParameterPayroll Period Parameter descriptive attributes, defines periodicity of the payroll run.

Payroll StatusDescriptive attributes for Payroll Indicator for most recent update of results record.

Payroll TypeCharacteristic used by the system to recognize which type of payroll run is to be carried out.



Salary RangeDefines the minimum, midpoint and maximum reported for the job by organizations with a formal salary structure. The salary range reflects the market value of a job.

Wage TypeObject in Payroll and Personnel Administration in which the user or the system stores amounts and time units that are used, for example, for calculating pay or for determining statistics. Wage types separate amounts and time units for various business purposes. This also enables the system to process amounts and time units in different ways during the payroll run.

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

• Accounting Clerk - Person responsible for collections or payments.• Sales Person - Person responsible for selling goods to the customer.• Service Person - An employee who is actively involved in

troubleshooting, maintenance, and repair activities.

POSITIONAn organizational object used to distribute tasks to posts in an organizational plan and to model the reporting structure between posts. Positions are concrete posts in an enterprise, which can be occupied by holders (employees or contractors), for example purchasing administrator, European sales manager, or secretary in the marketing department. Positions are not the same as jobs. A job is not a concrete position in an enterprise. It is a construct that enables you to create a number of positions with similar tasks and features.

PRICING PROCEDURERule type for pricing. Defines the conditions which are permitted for a particular document and the sequence in which the system takes these conditions into account during pricing. The Standard Pricing Procedure contains the conditions most commonly used. These include material prices as well as various discounts and surcharges (freight, tax).

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



ComponentAn object used as part of a bill of material by entering the object number. Example: A material is entered as a component of a bill of material by entering the material number. A document is entered as a component of a bill of material by entering the document number, document type, document part, and document version.

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

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

Exception TextText that describes an exception and is specified in an exception class. An exception text can be parameterized using the attributes of the exception class.

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

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

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

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



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

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

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

• Maintenance notifications • Service notifications • Quality notifications

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

Procurement TypeA classification indicating whether a material is produced internally, procured externally, or both.

Production SchedulerProduction scheduler descriptive attributes from T024F

Scheduling ErrorPlanned order scheduling error texts from DD07T, domain TRMER.

Spare Part IndicatorA material used to replace a defective part. This material may or may not be kept in stock. This table stores descriptions of these spare parts as defined in T413T.

Special Procurement TypeAn indicator in the material master record that defines external procurement or in-house production of the material precisely. Example:

• Consignment • Stock transfer • Production in another plant



System ConditionSystem Condition descriptive attributes from T253M_T.

Variance CategoryA classification of variances based on their cause.You can calculate the following variance categories on the input side:

• Scrap variances (only in Product Cost Controlling) • Input price variances • Resource usage variances • Input quantity variances • Remaining input variances

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

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

PROJECTA complex structure of tasks within a controlling area. It is used to control and monitor the schedule, resources, capacities, cost, revenues, and funds availability.

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



PRT(Production Resource Tool) A moveable operating resource used in production or plant maintenance. PRT includes the following sub-classes:

PRT CategoryDescriptive attributes from TCF03 of Production Resource/Tools categories

PRT Grouping KeyProduction Resource/Tools grouping key descriptive attributes from TCF1

PRT StatusDescriptive attributes for PRT status from TCF05

ROUTINGA description of the production process used to manufacture materials or provide services in the manufacturing industry. Routing includes the following sub-classes:

Order Operation Order Operation including Sequences from AFVC

Routing OperationRouting master data from PLPO.

Routing SequenceRouting (Task List) sequence definition from PLFL

Task List TypeA tool that classifies task lists according to function. In PP, the following task list types are used:

• Routing • Reference operation set • Rate routing • Standard rate routing

Task List UsageTask List Usage descriptive attributes from TC23T.

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



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

• Document Date Time Dim• Early Start Time Dim• Hire Date Time Dim• Notification Time Dim• Participation Time Dim• Payroll Run Date Time Dim• Planned Open Date Time Dim• Weekly Time Dim

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

• Company Code Fiscal Period• Controlling Area Fiscal Period

Calendar DimensionsCertain Rapid Marts carry calendars subject areas specific calendars. Included here are:

• Factory Calendar• Factory Calendar Period• Work Calendar

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• Downtime Unit of Measure• Duration Unit of Measure• Offset Unit of Measure• Standard Unit of Measure• Time Interval Unit of Measure• Work Unit of Measure

UNIT OF TIME (UOT) Human Resources related unit of time descriptive attributes.

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

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

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

• Machines • People • Production lines • Groups of craftsmen

Work Center CategoryWork Center Category Attributes from TC30T.

Work Center FormulaCapacity formulas from TC25; parameters are parsed from the formula equation text.



INVALID HIERARCHIESThis set of classes reports hierarchy records that have failed validation in the Data Services job. Use this information to correct the source records in SAP solutions. Corrected data will be reloaded into the proper tables with the next Data Services job run. The sub-classes are:

• Invalid Activity Hierarchy• Invalid Cost Center Hierarchy• Invalid Cost Element Hierarchy• Invalid Functional Area Hierarchy• Invalid GL Acct Hierarchy• Invalid Internal Order Hierarchy• Invalid Profit Center Hierarchy• Invalid Project Element Hierarchy• Invalid Work Center Hierarchy

FILTERSThis top level folder represents pre-defined conditions that can be included in any report (filters). They are organized by subject area, and include the following sub-classes:

• Benefits Filters• Company Code Filters• Employee Filters• Financial Document Type Filters• Fiscal Period Filters• Hierarchy Filters

• Activity Filters• Bill of Materials Filters• Cost Center Filters• Cost Element Filters• Equipment Filters• Functional Area Filters• Functional Location Filters• GL Account Hierarchy Filters• Internal Orders Hierarchy• Organization Unit Filters• Position Filters



• Profit Center Hierarchy Filters• Project Element Filters• Work Center Filters

• Personnel Area Filters• Personnel Subarea Filters• Project Filters

TECHNIQUESThese are advanced technique objects developed for the Web Intelligence reports.

Master Data Universe LayoutHere is a graphical representation of the Master Data Universe as it appears in the universe designer:



Master Data Universe (1 of 3)



Master Data Universe (2 of 3):



Master Data Universe (2 of 3):

Universe Validation - Master DataWhen validating the universe within the Universe Designer, some errors are expected and acceptable. They do not harm universe performance in any way. They are detailed below.


Integrity Check Results


Cardinality DivergencesThese are caused by the use of the “@prompt” function in the join. Since this function requires user intervention to complete the SQL join condition, the Universe Designer cannot check the cardinality vs. the database.Note: The error messages are specific to your database server. Thus Oracle, SQL-Server, and DB2 will have different messages for the same errors.


UniverseCustomizing the Universe 5

Customizing the UniverseThe SAP Human Resources Universe and the SAP Service Master Universe can be modified easily to suit your specific needs. Here is an example:

Splitting the SAP Human Resources UniverseIn the SAP Human Resources Universe, contains several subject areas. Your company wants a new universe with just Benefit Enrollment subject areas; keeping the original universe as is. You can follow these steps to create two universes:1. Create a copy of the SAP Human Resources Universe with file name:

• SAP-HR-Benefits.unv2. In the Universe Parameters, Definition tab, change the name of the

universe to:• SAP HR - Benefit Enrollment

3. Go to the graphic representation of the universe, right click on EMPLOYEE_ADMINISTRATION_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• EMPLOYEE_WAGE_FACT• LEAVE_ENTITLEMENT_FACT• PAYROLL_SUMMARY_FACT• PAYROLL_FACT

5. Delete these tables from the graphic representation of the universe:• EMPLOYEE_ADMINISTRATION_FACT• EMPLOYEE_WAGE_FACT• LEAVE_ENTITLEMENT_FACT• PAYROLL_SUMMARY_FACT• PAYROLL_FACT

6. All joins associated with these tables will be deleted as you delete the tables.


UniverseCustomizing the Universe5

7. In the graphic representation, find all dimension tables not joined to a fact table. For each of these tables, right click on the table and choose view associated objects. Delete these objects from the universe. Also delete any empty top level classes for the objects.

8. If the un-joined dimensions have associated hierarchy tables you should delete all associated hierarchy objects and empty top level classes as well.

9. In the graphic representation, delete all dimension tables not joined to a fact table. This includes their associated hierarchy tables. Any joins between dimensions and hierarchies will also be deleted automatically when you do this.

10. Delete the following contexts in the universe:• EMPLOYEE_ADMINISTRATION_FACT• EMPLOYEE_WAGE_FACT• LEAVE_ENTITLEMENT_FACT• PAYROLL_SUMMARY_FACT• PAYROLL_FACT

11. Validate and test the universe


UniverseCustomizing the Universe 5


UniverseCustomizing the Universe5


Installing the Rapid Mart

chapter

Installing the Rapid MartOverview6
Overview
This chapter contains the information you need to install the SAP BusinessObjects HR Rapid Mart, version for SAP solutions. The information in this chapter is useful for system administrators or others who install the Rapid Mart. See ‘Documentation References’ chapter for Data Services and BusinessObjects Enterprise installation and configuration documentation location.This chapter contains the following sections:• System Prerequisites• Personnel Prerequisites• Rapid Mart product components• Preparing your environment• The Rapid Mart Package• Install the Rapid Mart Target Schema• Install the Data Services Job(s)• Installing Rapid Mart Reporting Content


Installing the Rapid MartSystem Prerequisites 6

System PrerequisitesTo run the SAP BusinessObjects HR Rapid Mart, version for SAP solutions, you need the following:• SAP solutions release 4.6 or higher.• SAP BusinessObjects Enterprise XI Release 2 or higher (for reporting

content only)• SAP BusinessObjects Data Services XI 3.2, or higher• A “Target” database that is one of:

• Oracle• Microsoft SQL Server• IBM DB2 UDB• Teradata

Note: Using Teradata as a target requires additional customizations and modifications to the Rapid Mart. View xi3_rm_sap_td_suppl_en.pdf document for details. We recommend that your consulting or technical staff be well versed in both Teradata and Data Services functionality before proceeding.

Consult the Supported Platforms document for details on supported versions of:• SAP solutions• BusinessObjects Enterprise• Data Services• Target databasesIf you are installing the Rapid Mart over network, the system you are using needs to have at least:• SAP BusinessObjects Data Services XI 3.2 Designer or higher• SAP BusinessObjects Enterprise XI Release 2 Client or higherIf you have questions about system prerequisites, contact SAP BusinessObjects Technical Support.


Installing the Rapid MartPersonnel Prerequisites6
Personnel Prerequisites
The Rapid Mart installation procedure is completely manual. There are many intricacies. We recommend the team installing the Rapid Mart be fluent with these SAP BusinessObjects products:• Data Services

• Designer• Job Server• Web Administration

• BusinessObjects Enterprise• Universe Designer• Web Intelligence Query Designer

For additional support we recommend expertise in:• SAP solutions Administration (BASIS)• Target Database DBA (Database Administration)


Installing the Rapid MartRapid Mart product components 6

Rapid Mart product componentsThe Rapid Mart is delivered as a Zip file that includes all major product components. These are organized as directories and sub-directories within the zipped file. The main directories are:• Data Model for the target database: This is an Integrated ERWin Data

Model of the complete target schema for all Rapid Marts related to SAP solutions. The ERwin file is called: • SAP_Integrated_Model.erwinThe model is built with AllFusion ERwin Data Modeler Release: 7.2. If you have ERwin release 7.2 or higher available, you can load the file and use it to extend and customize the data model.The model is used to generate SQL scripts for:• Creating Rapid Mart tables and views• Dropping Rapid Mart tables and views• Creating Rapid Mart indexes• Dropping Rapid Mart indexes• Creating database stored procedures• Dropping database stored procedures

• Documentation for the Rapid Mart including:• Business Guide• User Guide • Release Notes• Deployment Guidelines for Oracle• Integrated Data Model User Guide• White Paper on Rapid Marts manual upgrade process• Customizing Rapid Marts for Teradata Supplement• Rapid Marts Word Utility User Guide.

• ETL (Extract Transformation Load) logic including:• SAP BusinessObjects Data Services XI 3.2 ATL file that specifies the

full (initial) load and incremental (delta) update jobs. These jobs perform the extract from SAP solutions and load to the Rapid Mart target tables

• Auxiliary Data Files used by the jobs• Source code for custom ABAP programs used by the jobs


Installing the Rapid MartRapid Mart product components6

• Sample reporting SQL (DML): This is the SQL source statements extracted from each of the sample Web Intelligence reports delivered with the Rapid Mart. It also includes sample SQL (DDL) for suggested database procedures.

• Utilities (Rapid Mart Word Utility and Metadata Discovery Utility.) Both Word Utility and Metadata Discovery Utility are metadata reporting solutions designed to help you with the manual upgrade process and to enforce pre-defined naming conventions when developing or customizing Rapid Mart data model(s). It also provides better exposure of the data model metadata details.

• Visuals contains the Rapid Mart BIAR file (reporting content). These are the sample Webi reports and universes (semantic layer) included with the Rapid Mart.


Installing the Rapid MartPreparing your environment 6

Preparing your environment

Preparing Data ServicesFollow these steps to prepare your environment for the Rapid Mart installation:• Install SAP BusinessObjects Data Services XI 3.2 or higher, if it is not

already installed.Refer to the Data Services Installation Guide for detailed installation instructions.Make sure that you install the Data Services Designer and that you install and configure a Job Server and an Access Server. Though you need Data Services job server to run Rapid Mart jobs, you need just Data Services Designer to install Rapid Mart.Create a separate repository for Rapid Mart(s) after the Data Services installation using the Repository Manager. A Data Services repository is required to install the Rapid Mart ETL job (ATL file). It is recommended to import the ATL file(s) into an empty Data Services repository. Multiple Rapid Marts can be installed in the same repository.Make sure that the Job Server is associated to the repository. The association sign in the right bottom corner of Data Services Designer should be on:

If the association is inactive, the sign will have a red cross:

• Start Data Services Designer and log on to the repository where you are going to install the Rapid Mart.This step ensures that your default connection is set appropriately.

• Exit Data Services Designer.

Preparing Target Database EnvironmentPrepare your target database environment. • Currently the Rapid Mart supports Oracle, MS SQL Server, Teradata, and

DB2 as target databases.


Installing the Rapid MartPreparing your environment6

• Ensure there is an empty database schema/user for use as target database. Create one if necessary.

• Be sure to have the target database connection information (user name, password, etc.) available. Target database connection information is required when setting up connectivity in Data Services Designer.

• If your target database is Microsoft SQL-Server, make sure the database uses Case Sensitive collation (like Latin1_General_BIN).

Preparing Source Application• Confirm your SAP solutions version. Minimum required version is SAP

solutions release 4.6 or higher.• Sometimes Rapid Marts process data differently, depending upon the

version. See ‘Data Service Supplement for SAP’ document for details on how to setup connectivity between Data Services and SAP.

Preparing BusinessObjects Enterprise Follow these steps to prepare your environment for the Rapid Mart Reporting Content installation:• Ensure the SAP BusinessObjects Enterprise XI Release 2 or higher

Client is available on your installation machine.• Ensure BusinessObjects Enterprise Client has correct connectivity to the

CMS you will use for the sample reporting content. • The CMS must also be SAP BusinessObjects Enterprise XI Release 2 or

higher.• Ensure the Import Wizard utility is available to import the BIAR file.

Performance TuningThe table and index creation scripts provided in the Rapid Mart are a guideline and starting point. As no two installation environments are the same, we recommend a performance tuning analysis of the target environment considering:• Volume of data to be loaded, including growth rates• Physical disk layout and requirements• Network bandwidth• Frequency and duration of loads


Installing the Rapid MartPreparing your environment 6

• Reporting query volumes and most frequently used subject areas• Hardware configuration and capacity for all servers involved:

• SAP solutions server(s)• Data Services Job Server(s)• Target Database Server(s)• BusinessObjects Enterprise Server(s)

From this analysis you will be able to implement proper database storage parameters and proper indexes for your environment. It is invaluable to have a qualified DBA and appropriately trained technical staff for this analysis.


Installing the Rapid MartThe Rapid Mart Package6
The Rapid Mart Package
Download the Rapid Mart package.Choose an appropriate location on your installation server and run unzip/extract program to install the package. We recommend creating a subdirectory called as the Rapid Mart name (example SAPHR_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 263 and ReadMe.txt file.


Installing the Rapid MartInstall the Rapid Mart Target Schema 6

Install the Rapid Mart Target SchemaThis section deals with the installation of the Rapid Mart target schema.The schema installation is manual.

Create Target SchemaAfter you unzip the Rapid Mart package, to go the DataModel sub-directory. You will find directories for each of the target databases supported:• Oracle• DB2• SQL Server• TeradataCreate the target schema using the files from the sub-directory for your target database.Note: The integrated data model includes the tables, views, and indexes used by all Rapid Marts for SAP solutions. Thus, execute the set of scripts only once when installing multiple Rapid Marts. The set of scripts is identical in all Rapid Marts for SAP solutions.

Create Target TablesIn the appropriate target database directory locate the files:• SAP_Create_Tables.sql• SAP_Create_Comments.sqlAs a quick start, execute the scripts in your target database. It will create all database tables and views used by the Rapid Mart. Creating comments is optional. It will ensure that Data Services will store tables and views with descriptions in its repository after you re-import the tables and views.Note: Please read notes below, and apply as needed:1. Use the results of Performance Tuning analysis to guide you in the

process of allocating storage space and physical disk location for your tables You may want to modify the table create script to include these parameters before execution.

2. If your target database is DB2 without Code Set UTF-8 (without multi-byte character support), you will need to edit the SAP_Create_Tables.sql script. Change all occurrences of data type VARGRAPHIC to VARCHAR before creating tables.


Installing the Rapid MartInstall the Rapid Mart Target Schema6

3. If your target database is DB2 with Code Set UTF-8 (with multi-byte character support), you do not need to make changes to SAP_Create_Tables.sql script.

4. If your target database is DB2, regardless of Code Set, you must have at least one tablespace with page size = 8 Kilobytes to accommodate column size (table width) on some tables. The tables affected by this are:• COST_CENTER_HIER_HZ• FUNCTIONAL_AREA_HIER_HZ• GL_ACCOUNT_HIER_HZ• PROFIT_CENTER_HIER_HZ• PROJECT_ELEMENT_HIER_HZ

Create Target IndexesCreating indexes is optional. We highly recommend that the DBAs first review the indexes and decide which indexes should be created to ensure proper performance for both ETL process and reporting query responses.In the appropriate target database directory locate the files:• SAP_Create_Indexes_All.sql• SAP_Create_Indexes_Performance.sqlThe first script includes all indexes for all tables in the data model. These include indexes for each foreign key in the model.The second script is a subset of indexes (from SAP_Create_Indexes_All.sql) tuned for performance in our internal SAP BusinessObjects development environment. This includes optimization for both Data Services load performance and reporting performance.For a quick start, we suggest starting with the SAP_Create_Indexes_Performance.sql file, and then creating / dropping indexes as needed in your environment.Note: Use the results of Performance Tuning analysis to guide you in the process of:• selecting indexes to create• allocating storage space• allocating physical diskYou may want to modify the index creation scripts to include these parameters before execution.


Installing the Rapid MartInstall the Rapid Mart Target Schema 6

Create Dummy ProceduresThe Rapid Mart contains 2 templates or “dummy” database procedures. As delivered, they are place holders for custom performance tuning. See Rapid Mart Deployment Guideline.pdf for more details on how to use these procedures.One procedure is called before each fact table load in the Rapid Mart, and the other after the fact table is loaded. The procedures need to be installed for the Data Services jobs to run. Locate the file:• Create_Dummy_Maintenance_SP.sqlExecute this file in your target database environment to create the dummy procedures.You can modify these procedures to help load performance. For example, the first procedure could be modified to drop secondary (foreign key) indexes on the fact table before a load. The other, could be modified to re-create these indexes (for query performance) at the end of the load. The Rapid Mart contains an example (File Create_Sample_Maintenance_SP.sql in the Sample directory) of how to do this with an Oracle target database.

Dropping Tables, Procedures and IndexesUse these scripts as needed to drop tables, procedures, views, and indexes. When starting with an empty target database / schema, they are not required for installation. They are provided to ensure a complete DDL (Data Definition Language) package for each target database.• Drop_Dummy_Maintenance_SP.sql

Note: The Oracle version of Create_Dummy_Maintenance_SP.sql uses Oracle’s “create or replace” syntax. Thus, no drop script is provided for Oracle.

• SAP_Drop_Indexes_All.sql• SAP_Drop_Indexes_Performance.sql• SAP_Drop_Tables.sql


Installing the Rapid MartInstall the Data Services Job(s)6
Install the Data Services Job(s)
This section deals with the installation of the Rapid Mart jobs using Data Services Designer. Installation of reporting content is covered in “Installing Rapid Mart Reporting Content” on page 290.The Rapid Mart Job Installation is manual.The ETL subdirectory for the Rapid Mart package contains the ATL file. ATL files are specific to each Rapid Mart and follow the naming convention• (RM_ABBR)_Rapid_Mart.atlExample: The HR Rapid Mart ATL file is named:• SAPHR_Rapid_Mart.atl

Renaming the Data StoresThis step is optional. You can configure and customize the Rapid Mart with Data Services Designer, except for changing Data Store names. The default names for the data stores in the ATL are• R3_DS for the SAP solutions data store• RM_DS for the target database data storeIf you are satisfied with these names, proceed to the next step, Import ATL File.To rename the data stores proceed as shown below.Note: This step is prone to human error. We strongly urge you to make a backup copy of the ATL file before you start.Open the ATL file in a text editor such as Wordpad.Note: DO NOT use Notepad. Notepad does not handle text wrapping properly and will corrupt the ATL file. We suggest Wordpad instead.Use the “global replace” function or “replace all” function to change all occurrences of the default SAP solutions data store name with one of your choosing. Example: using Wordpad


Installing the Rapid MartInstall the Data Services Job(s) 6

Before Replace All



After Replace All

Repeat these steps for the RM_DS data storeSave the ATL file.Note: DO NOT use the same name for the R3_DS and the RM_DS data stores as this will corrupt the file.

Import ATL FileSee ‘Data Services Designer Guide’ for details on importing files.• Start Data Services Designer and log on to the local repository where you

are going to install the Rapid Mart.Note: The example below uses the ATL file for the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions. Be sure to use file SAPHR_Rapid_Mart.atl instead of the file name shown in the example.



• From the Tools Menu choose Import From File:

• Choose the ATL File



• Click “OK” to any warnings. You might get pop-up windows warning that the import may take a long time, or that the ATL file was created with a lower version of Data Services. Answer “OK” to any of these. This will start the import process.Data Services will import the ATL file, creating all the repository objects required to run Rapid Mart load jobs.

Adjusting the Data StoresAs imported, the Rapid Mart data stores point to “dummy” data sources for both SAP solutions and your target database. You will need to provide proper connectivity and login information for both. • R3_DS (SAP solutions Data Store):Navigate to the Data Store:



Edit the Data Store:



Open “Advanced” Edit Window



Edit Data Store Settings.

Click OK to close Edit WindowClick OK to Close Advanced WindowThe Data Store window should close without any warnings or errors, indicating successful connection and log-in to the SAP solutions server.Note: The local repository must be associated with the Data Services Job Server to complete the R/3 datastore configuration successfully.Re-import R/3 tables used by the Rapid Mart. Use R/3 datastore ‘Reimport All...’ command you can access by right-clicking on the R/3 datastore name.

• RM_DS (Target Database Data Store):



Edit the Data Store:



Open “Advanced” Edit Window



Edit Data Store Settings.

Example: If your target database is Oracle, you would only change settings in “Configuration1” column. For SQL-Server, change only “Configuration2” column, etc.Note: For “RM_USER” alias, enter the target database schema owner:• For SQL Server - “dbo”• For Oracle and DB2 UDB - database user name• For Teradata - the schema ownerClick OK to close Edit Window



Click OK to Close Advanced WindowThe Data Store window should close without any warnings or errors, indicating successful connection and log-in to the Target Database server.Re-import target tables used by the Rapid Mart. Use the target datastore (RM_DS) ‘Reimport All...’ command you can access by right-clicking on the target (RM_DS) datastore name.

Using Auxiliary FilesAll Rapid Marts come with an auxiliary file: • dates.datThis file is used to load the Fiscal Period and Time Dimensions. After unzipping, this file is located in the ETL subdirectories, the path is:• ...\ETL\Files\Data\Note: There may be additional Rapid Mart specific files in this directory.



All files in this directory must be moved to the working directory you specified when Adjusting the Data Stores, as shown below:

Using ABAP FilesRapid Marts may come with additional ABAP files. These are ABAP code snippets used by the Rapid Mart to assist in extracting data from SAP solutions. • ABAP files always end with the suffix .abaThey are used when regular Data Services transformations are insufficient to extract the data. For example, they are used to read from a clustered table in SAP solutions.



At this writing, only four Rapid Marts use ABAP files• SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

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

solutionsIf used, these files are located in:• ...\ETL\Files\ABAP\Some examples of the files found in the Cost Center and GL Rapid Marts are:• RF011F_NEW.aba• RF011F_OLD.aba• RF011P_NEW.aba• RF011P_OLD.aba• etc.Note: For SAP BusinessObjects HR Rapid Mart, version for SAP solutions Only: be sure to choose the correct files for your SAP solutions version:There are two versions of these files:• PA0167_ABAPXFORM.aba• PA0168_ABAPXFORM.abaIf you are running SAP solutions version 5.0 or newer, choose the files in directory:...\ETL\Files\ABAP\ABAP50If you are running SAP solutions version 4.6, choose the files in directory:...\ETL\Files\ABAP\ABAP46



All these files should be moved to the Generated ABAP directory you specified when Adjusting the Data Stores, as shown below:

Then, make sure the Data Services transforms using these files point to the Generated ABAP directory as shown below.



1. Open Data Services and navigate to the Transforms tab of the Local Object Library:

Note: This step applies only to:• SAP BusinessObjects Cost Center Rapid Mart, version for SAP

solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

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

SAP solutionsFor the rest of Rapid Marts, you will not see Custom ABAP transforms in the Transforms tab.



2. Then, change path to be the same as where the ABAP files are installed

3. Repeat this step for all the other ABAP transforms in the Object Library4. Save the changes5. Validate the Data Services jobs to ensure they are working correctly.

Final Steps• If your Job Server runs on a UNIX system, using Data Services Designer

adjust the directory paths in all Rapid Mart file format definitions to follow the UNIX convention (that is, change from “/” to “\”).



• Before running the job, you must initialize some global variables. For information about executing the Rapid Mart job, see Chapter 7: Using the Rapid Mart.

• Rapid Marts are developed against standard out-of-the-box SAP solutions installation. It is important that during the Rapid Mart implementation you:• Re-import all Rapid Mart source objects (tables, hierarchies,

functions, etc.) to have object customization captured;• Review each Rapid Mart dataflow to make sure that its Query

transform(s) contain(s) proper constraints when extracting data from the source tables. Adjust “WHERE” conditions in Query Transforms if necessary. Look for hard-coded constraints and other conditions that need to be customized.


Installing the Rapid MartInstalling Rapid Mart Reporting Content6
Installing Rapid Mart Reporting Content
Rapid Marts come with their own Reporting Content, supplied as Web Intelligence reports and universes (semantic layer.) In order to use the Reporting Content you must first install them to your BusinessObjects Enterprise system and configure a connection to your Rapid Mart target database.If the BusinessObjects Enterprise server (CMS) is located on a different machine, you need to have BusinessObjects Enterprise client installed, with connectivity to that server.The Reporting Content is delivered as a BIAR file, located in the unzipped Visuals sub-directory:• Directory Path: ...\Visuals\• File Name: saphr_Rapid_Mart_Visuals.biarNote: We recommend that you start with a clean CMS, or by deleting any old versions of Rapid Mart reports or universes. This will avoid confusion with older versions.

Import Wizard for Reporting Content BIAR FileUse the BusinessObjects Enterprise Import Wizard to import the BIAR file. The Import Wizard can be identified by this icon:

Start the Import Wizard and follow these instructions. Note: The screen shots here are from SAP BusinessObjects Enterprise XI Release 3. Some screens do not appear in SAP BusinessObjects Enterprise XI Release 2. The missing screens are indicated below. If you are using SAP BusinessObjects Enterprise XI Release 2, simply ignore the missing screens.


Installing the Rapid MartInstalling Rapid Mart Reporting Content 6

On the first screen, click “Next”:



Choose BIAR File:

Note: The BIAR file for the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions is used in this illustration. You should use the proper file for the HR Rapid Mart located in Directory: ...\VisualsFile: saphr_Rapid_Mart_Visuals.biar



Choose CMS:



Select Object to Import - Check or Uncheck Boxes:

Note: The number of boxes to check on this screen may vary between BusinessObjects Enterprise releases. Regardless of release, just make sure only the “import folders and objects” box is checked.Do not click “Next” on this screen. Proceed to next page.



Select Object to Import - Check or Uncheck Boxes (continued):

Note: The number of boxes to check on this screen may vary between BusinessObjects Enterprise releases. Regardless of release, just make sure only the “import universes” box is checked.



Check Import Scenario Radio Buttons as shown

Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2



Incremental Import - Check or Uncheck Boxes:



Acknowledge Message, Click Next



“Select All” to import complete contents of BIAR file.



Universe & Connection Options- Check or Uncheck as shown



Ensure All Objects are Selected:

Write down universe names. There can be more than one universe per a Rapid Mart. You will need these names later when creating Universe connection.



Select Import Options for Publications:

Note: This screen does not appear in SAP BusinessObjects Enterprise XI Release 2



Acknowledge message, Click “Next”:



Verify Correct List of Objects to Import, Click FINISH to start import:



Wait for Import to Finish. Then Click “View Detail Log”:

Click on each item imported. Make sure there are no errors:



Click Done to Exit the Import Wizard:

This completes the Import Wizard for Reporting Content.

Creating Universe ConnectionNow use the Universe Designer to change the connection in the imported universe(s).



Start the Universe Designer, and import the universe(s) by choosing File -> Import. Select universe(s) you wrote down when importing the BIAR file in the previous step and import all of them. Then, navigate to the Universe Parameters Screen:



For each universe, either choose an existing connection to Rapid Mart target database, or create a new one:

Note: This illustration uses the SAP BusinessObjects Accounts Receivable Rapid Mart, version for SAP solutions as an example only. The Universe Designer will show the correct universe name for your Rapid Mart Note: Consult the SAP BusinessObjects Universe Designer Guide for details on how to assign or create a connection.When done, export the universe(s) back to the CMS by choosing File -> Export in the Universe Designer.This concludes Rapid Mart installation.


Installing the Rapid Mart 6


Installing the Rapid Mart6


Using the Rapid Mart

chapter

Using the Rapid MartOverview7
Overview
This chapter describes how to execute the Rapid Mart, including information about the variables that the Rapid Mart uses. This chapter also discusses considerations you need to make when customizing the Rapid Mart. The information in this chapter is useful for administrators and others who run or modify the Rapid Mart.Specific topics include:• Recovery framework• Execution status framework• Extraction, transformation and loading process• Global Variables• Customizing the Rapid Mart

Recovery frameworkWhen executing the Rapid Mart, it is important that you do not load any duplicate data and that you do not extract data redundantly, even in cases of failure. There are two mechanisms to ensure that you do not load duplicate data:• Data Services automatic recovery feature• Rapid Mart recovery framework

Data Services automatic recovery featureWith automatic recovery, Data Services records the result of each successfully completed step in a job. If a job fails, you can choose to run the job again in recovery mode. During recovery mode, Data Services retrieves the results for successfully completed steps and reruns uncompleted or failed steps under the same conditions as the original job. For recovery purposes, Data Services considers steps that raise exceptions as failed steps, even if the step is caught in a try/catch block.To use the automatic recovery feature, you must enable the feature during the initial execution of a job. In the Execution Properties window, select the Enable Recovery check box.


Using the Rapid MartRecovery framework 7

The automatic recovery option is useful during testing and development phases. However, use caution with this feature during a production run because the data may lose its integrity if significant changes in SAP solutions source tables occur between the failed run and the recovery run. For example, suppose two tables contain related data but are loaded in separate work flows. In this case, the job can fail after successfully completing the work flow that loads the first table but before completing the work flow that loads the second table. During recovery, Data Services does not re-run a successfully completed work flow; therefore, the first table is not loaded again. However, Data Services will run the work flow that loads the second table during the recovery job. If the work flow loads the entire table regardless of dates, the second table will contain data added to SAP solutions between the initial run and the recovery run, but the first table will not contain this data. As a result, the two tables will be inconsistent.

Rapid Mart recovery frameworkThe Rapid Mart contains an external execution status table (AW_JOBEXECUTION) that tracks the status of a job’s execution and the time data was extracted. By using the execution status table, the Rapid Mart ensures that data for the proper dates is extracted from the source datastore.With each incremental (or delta) execution, the Rapid Mart job extracts data between a start date and an end date. This is determined by setting the global variable $G_LOAD_TYPE = ‘DELTA’. If the job fails and is rerun on the same or a subsequent day, the new job uses the failed job’s start date to ensure that all the data is extracted contiguously. Note: There are exceptions to this, as certain subject areas may have delta loads that use a different methodology. Consult the Technical Implementation chapter for details on the delta loads for each subject area.Upon execution, a job first checks the status of the last execution of the job. If the last execution failed, the job determines the ending date of the last successful execution. This date becomes the starting date of the next execution of the job. All work flows are re-executed using the same starting date to ensure consistency. For example, if a failed job is restarted on the same day (without using the automatic recovery feature), the restarted job refreshes all tables because the last execution of the job on that day was not successful. If a job continues to fail over several days, the job would continue using the same start date used on the first failed attempt. This ensures that when the job is eventually successful, it extracts the complete set of data that changed since the start date.


Using the Rapid MartExecution status framework7

To maintain consistency with data flowing to SAP solutions, the Rapid Mart always overlaps one day’s worth of data in incremental loads. For example, if the end date is June 3, the incremental load job extracts data entered or changed on June 3. The next incremental load job extracts data starting with the June 3 date. Up to one day’s worth of duplicate data may be extracted each time the job runs; however, work flows are designed to detect and delete duplicate data from the target data table before reloading the refreshed data. To do this, many work flows use the auto correct load option or the Table Comparison transform. Both of these check for an existing row with the same key as each row flagged as an insert or update activity. If the row exists, Data Services updates the row. If the row does not exist, Data Services inserts the row.

Execution status framework The Rapid Mart uses two mechanisms to check the job execution status and control execution:• An execution status table that stores one record for each job. That record

contains:• Status of previous job execution• Starting and ending times of the last attempted execution of the job

• An application programming interface (API) that updates the status table and supports the implementation of restartable jobs and flows

The execution status tableThe Rapid Mart installation procedure creates a table named AW_JOBEXECUTION in the target database.The execution status table has four columns.

Table column Description

NAME The name of the job being executed. If the same target datastore is used for more than one repository, you must ensure that all job names are unique.

STATUS The status of this job after the last execution. Possible status values are: started, done, or none.

EXTRACTLOW Last attempted start date of data retrieval. This date is also the ending date of the last successful run of the job.

EXTRACTHIGH Last attempted end date of data retrieval.


Using the Rapid MartExecution status framework 7

How job status is maintainedThe Rapid Mart records a job status for each invocation of a particular job. There are three possible values for job status: • None — The job status is none when the job has never been executed.• Started — Job status is set to started when a new invocation of a job

starts.• Done — Job status is set to done when a job completes successfully.When a job is started, the Rapid Mart checks the job’s existing status. If the previous execution of the job did not complete successfully—that is, the job status is not done—the Rapid Mart resets the starting date for data extraction ($G_SDATE) from the value specified in the job initialization script to the ending date of the last successful run (EXTRACTHIGH). You can override the reassignment of the starting date by forcing the starting date to be reset. See “Executing a job with the Reset option” on page 316. The Rapid Mart never changes the ending value ($G_EDATE) from the value specified in the initialization script.After checking the job’s existing status, the Rapid Mart sets the status of the job to started, and starts a new execution of the job.When a job successfully completes, the Rapid Mart sets the job’s status to done. If the job does not complete successfully, the job’s status remains set to started. The EXTRACTLOW and EXTRACTHIGH dates remain set to the current values.

The execution status APIThe execution status API updates the execution status table to control gaps in the time sequence of data extraction.The API contains two external functions. These functions mark the start and termination of jobs.• AW_StartJob ($jobname input, $run_mode input, $load_type input, extractlow input/

output, extracthigh date input/output) The InitializeJob script calls this function to initialize a job and check the last execution status. When called for a new job execution, the function inserts a new row into table AW_JOBEXECUTION. When called for a restarted job execution, the function: • Checks the run mode to see if you set the reset option.

If $G_RUN_MODE is RESET, the function resets EXTRACTLOW and EXTRACTHIGH to the $G_SDATE and $G_EDATE values specified in the initialization script.


Using the Rapid MartExtraction, transformation and loading process7

• Checks the last execution status of the job. If the job status is done, the function sets EXTRACTLOW to the previous value of EXTRACTHIGH, the last successful end date; next, the function sets EXTRACTHIGH to the value of $G_EDATE, which you set in the initialization script. The function returns the values in EXTRACTLOW and EXTRACTHIGH and the Rapid Mart uses these values to update $G_SDATE and $G_EDATE.If the job status is started, the function does not change the value of EXTRACTLOW. Instead, this value remains the end date of the last successful execution. The function does change EXTRACTHIGH to the new value set in $G_EDATE. The function returns the EXTRACTLOW and EXTRACTHIGH values, and the Rapid Mart uses these values to update $G_SDATE and $G_EDATE.

• AW_EndJob(job name) The EndJob script calls this function to change the job status value in the AW_JOBEXECUTION table to done when the job executes successfully.

Executing a job with the Reset optionYou can use the reset mode to force the Rapid Mart to assign a new starting extract time for data extracts. Use reset mode to force the starting and ending dates (global variables $G_SDATE and $G_EDATE) to remain the same as the values you set set in the initialization script or job properties. Note: Using this option may cause gaps in the time sequence of data loaded into target tables. To specify reset mode, edit the job’s initialization script or execution properties and set global variable $G_RUN_MODE = ‘RESET’. When using reset mode, be sure that the global variables $G_SDATE and $G_EDATE are set so that no gaps in data occur.

Extraction, transformation and loading process

The job HR_Load executes objects that load the load the data from SAP solutions to Rapid Mart target database. This job contains:


Using the Rapid MartExtraction, transformation and loading process 7

• Job global variable properties. This window can be accessed by right-clicking on the HR_Load job and selecting the Properties command from the drop-down list. Most of the HR Rapid Mart global variables are initialized here.

• An initialization script. The script contains description of each global variable set in the job Properties window. It also completes several steps: • Sets the initial values of the Rapid Mart framework variables that the

job uses• Initiates the execution status frameworkNote: If you plan to change global variable settings from the default “as shipped” values, we suggest you do so in the initialization script. The initialization script executes after the global variables are set in the


Using the Rapid MartGlobal Variables7

properties window. Thus, you can preserve the “as shipped” values for reference in the properties window, while still using your own values as set in the initialization script.

• Sections that load a set of tables you can use to analyze and report on a particular Subject Area in the Rapid Mart. A section consists of: • A work flow that loads the reporting dimensions applicable to the

subject area.• Work flows that load holding tables, intermediate tables, and auxiliary

tables that support loading the main subject area tables. Some of these flows might be reusable components, which can be incorporated into multiple sections of Rapid Marts. Components have the “execute once” feature enabled.

• A conditional object that determines whether the job executes the initial or incremental loading logic.

• Work flows that load the main tables for the subject area. These tables are generally called “fact” tables in relational modeling terminology. A section loads a single fact table and any additional fact tables that depend on it. For example, an order analysis section might load an order table and an order summary table.

• A final script that updates the job execution status table

Global VariablesAll Rapid Mart jobs use a standardized set of Global Variables. For completeness, and multiple Rapid Mart integration. They are included with each Rapid Mart job, regardless if they are used by the job.

Global Variable Cross-ReferenceA complete Cross-Reference Matrix of Global Variables is shown below. It is organized in three sections grouped by how many Rapid Marts use each Global Variable:• Used in All Rapid Marts• Used in 2 to 10 Rapid Marts• Used in Only 1 Rapid Mart


Using the Rapid MartGlobal Variables 7

The global variables in each of these sections are described in detail after the matrix.

Global Variable Name Data Type

AP AR CA GL HR IA PM PP PR PS SA

Used in all 11 Rapid Marts$G_CCODE varchar(4) X X X X X X X X X X X

$G_DEFAULT_DATE datetime X X X X X X X X X X X

$G_DEFAULT_NUMBER int X X X X X X X X X X X

$G_DEFAULT_TEXT varchar(1) X X X X X X X X X X X

$G_EDATE datetime X X X X X X X X X X X

$G_LANGUAGE varchar(1) X X X X X X X X X X X

$G_LOAD_DATE datetime X X X X X X X X X X X

$G_LOAD_TIME varchar(8) X X X X X X X X X X X

$G_LOAD_TYPE varchar(7) X X X X X X X X X X X

$G_MAX_DATE datetime X X X X X X X X X X X

$G_REBUILD_INDEXES varchar(1) X X X X X X X X X X X

$G_RUN_MODE varchar(10) X X X X X X X X X X X

$G_SDATE datetime X X X X X X X X X X X

Used in 2 to 10 Rapid Marts$A int X X

$B int X X

$C int X X

$D int X X

$E int X X

$F int X X

$G int X X

$G_ABSOLUTE_START_DATE

datetime X X X X X

$G_ENDFISCALYEAR int X X X X X X

$G_EXCHANGE_TYPE_ID varchar(4) X X X

$G_GLOBAL_CURRENCY varchar(5) X X X

$G_INT_ORDER_CATEG_PP

varchar(2) X X

$G_INT_ORDER_CATEG_PS

varchar(2) X X

$G_ORIG_SDATE datetime X X X

$G_STARTFISCALYEAR int X X X X X X



Used in Only 1 Rapid Mart$G_ADDRESS_VERSION varchar(1) X

$G_BUS_PARTN_SDATE datetime X

$G_BUS_PARTNER varchar(1) X

$G_COST_OF_SALES_LEDGER_ID

varchar(2) X

$G_COUNTRY_GRP varchar(2) X

$G_DEL_PERIOD datetime X

$G_DEL_REJECT_REASON varchar(2) X

$G_DROP_SHIP varchar(1) X

$G_GL_ACCOUNT_HIER_NAME

varchar(10) X

$G_GL_SUM_PLAN_LEDGER_ID

varchar(2) X

$G_GL_VERSION varchar(3) X

$G_HIRE_ACTION_01 varchar(2) X



$G_INIT_HIST_CHG varchar(1) X

$G_MALFUNCTION_CAUSE varchar(20) X

$G_MALFUNCTION_DAMAGE

varchar(20) X

$G_MALFUNCTION_OBJ_PART

varchar(20) X

$G_MRP_RESULTS_DELETE

varchar(1) X

$G_ONTIME_DELIV_WINDOW

int X

$G_PC_ACCOUNT_HIER_NAME

varchar(10) X

$G_PROFIT_CENTER_LEDGER_ID

varchar(2) X

$G_REHIRE_ACTION_01 varchar(2) X

$G_REHIRE_ACTION_02 varchar(2) X

$G_RETIRE_ACTION varchar(2) X

$G_SAP_VERSION int X

$G_SCHOOL_TYPE varchar(2) X





$G_SERVICE_INTERVAL_01 int X





$G_TABLE_EQUIPMENT varchar(20) X

$G_TABLE_FUNCTL_LOCATN

varchar(20) X

$G_TASK_TYPE_PROBATION_END

varchar(2) X

$G_TERMINATION_ACTION varchar(2) X

$G_VALID_DATE datetime X

$G_WAGE_TYPE_01 varchar(4) X




















$G_WORKDAY_EDATE datetime X

$G_WORKDAY_SDATE datetime X




Used in All Rapid Marts
$G_CCODE Data Type: varchar(4)Default Value: “0001”The SAP solutions Company Code used for Time Dimension extraction. The fiscal variant associated with this company code is used to determine the fiscal periods of the Time Dimension.Set this to the Company Code that carries the Fiscal Calendar (determined by the Fiscal Variant) that best suits your needs.

$G_DEFAULT_DATE Data Type: datetimeDefault Value: 31-Dec-9999The default date for missing dates.

$G_DEFAULT_NUMBER Data Type: intDefault Value: -1Default number for dimension default rows, foreign keys, and primary keys. Also used as a default for missing numbers.

$G_DEFAULT_TEXT Data Type: varchar(1)Default Value: “?”Default text for dimension default rows, foreign keys, and primary keys. Also used as a default for missing descriptions.

$G_EDATE Data Type: datetimeDefault Value: NULLThe ending date for data extraction.For first (initial) run or incremental (delta) runs, we recommend leaving this empty (null). The Initialize job script and function AW_StartJob will automatically determine the proper value.



if you set the variable, jobs will not extract data entered into your SAP solutions system after this date. For example, if your end date is June 4, 1999, the jobs will not extract data for June 5, 1999 or later.

$G_LANGUAGE Data Type: varchar(1)Default Value: “E” (English)The language in which jobs extract text descriptions. Use the SAP solutions standard language abbreviations if you require a different language.

$G_LOAD_DATE Data Type: datetimeDefault Value: System Date and TimeAlways set to current system date and time by the Job Initialization script. Do not change the setting of this variable.

$G_LOAD_TIME Data Type: varchar(8)Default Value: System TimeAlways set to current system time by the Job Initialization script. Do not change the setting of this variable.

$G_LOAD_TYPE Data Type: varchar(7)Default Value: “FIRST”Legal values:• FIRST - for the initial or first load• DELTA - for incremental or delta loadsSetting this variable to anything else will cause the job to fail.

$G_MAX_DATEData Type: datetimeDefault Value: 31-Dec-9999Used in date effective transforms to match SAP value for “infinite” date as end of validity period.


$G_REBUILD_INDEXES
Data Type: varchar(1)Default Value: “N” on Weekdays, “Y” on WeekendsLegal values:• Y - Run rebuild indexes script• N - Do not run rebuild indexes scriptAs delivered, this is a place holder for custom performance tuning. See Rapid Mart Deployment Guideline.pdf for more details on how to use this variable in conjunction with the stored procedures in file Create_Sample_Maintenance_SP.sql.These stored procedures drop indexes before a Fact Table load, and re-create the indexes when the load is complete.Use this variable to further restrict the drop and re-create to weekends only.

$G_RUN_MODE Data Type: varchar(10)Default Value: NULLLegal values:• RESET - Forces job to reload from value set in $G_SDATE. • NULL - Uses AW_JOBEXECUTION to determine $G_SDATE.When set to “RESET”, this variable forces the Rapid Mart to use the starting extract date you have set for variable $G_SDATE. Otherwise, the setting is determine by querying table AW_JOBEXECUTION, and using the EXTRACTHIGH value of the last successful run.

$G_SDATE Data Type: datetimeDefault Value: 01-Jan-1990The start date for data extraction. During an initial extract, the job does not extract data that was entered into your SAP solutions system prior to $G_SDATE. For example, if your start date is January 26, 2000, the initial extract job does not extract data that was entered on January 25, 2000 or earlier. During incremental (delta) extractions, the job only extracts data modified or entered on or after this date. The incremental load job only uses the $G_SDATE when one of these conditions is true:



• Execution status table AW_JOBEXECUTION has no rows that correspond to the current job.

• The variable $G_RUN_MODE is set to “RESET” in the initialization script for the job.

Otherwise, the incremental job determines $G_SDATE by querying table AW_JOBEXECUTION and using the EXTRACTHIGH of the last successfully executed job.If there was no previous successful execution, the EXTRACTLOW value is used.

Used in 2 to 10 Rapid Marts

$A Data Type: intDefault Value: 30Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for

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

SAP solutions1 of 4 configurable past time periods (in days) to use for aged receivables and payables and late payments.

$B Data Type: intDefault Value: 60Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions2 of 4 configurable past time periods (in days) to use for aged receivables and payables and late payments

$C Data Type: intDefault Value: 90



Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for



$D Data Type: intDefault Value: 120Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for



$E Data Type: intDefault Value: 14Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions1 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)

$F Data Type: intDefault Value: 30Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for

SAP solutions



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

2 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)

$G Data Type: intDefault Value: 45Where Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions3 of 3 configurable forecast time periods (in days) used to calculate values of financial documents at future dates (for discounting purposes, etc.)

$G_ABSOLUTE_START_DATEData Type: datetimeDefault Value: NULLWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects HR Rapid Mart, version for SAP solutions• SAP BusinessObjects Inventory Rapid Mart, version for SAP

solutionsEarliest date to use for delta load of Financial Documents, (in AP, AR, and GL Rapid Marts). Closed documents created before this date WILL NOT be loaded to the Rapid Mart. It works in conjunction with variable $G_ORIG_SDATE for incremental loads that do not carry a “date of last change” in the SAP solutions tables.See the Technical Implementation chapter for each specific Rapid Mart for full details on how this variable is used.



In General: If you set Absolute Start Date in the initialization script, this is the value that will be used in the delta load. If Absolute Start Date is NOT set in the initialization script (the default value NULL), the date of the earliest OPEN Document will be used. We use the earliest OPEN date because the earliest open document may have been closed since your last load. So, to be sure it is re-loaded as a “closed” item, we need to use the earliest open date from the last load. This is stored as the MIN(ENTRY_DATE) in associated Fact Table for open documents

$G_ENDFISCALYEARData Type: intDefault Value: NULLWhere Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects Cost Center Rapid Mart, version for SAP

solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects Plant Maintenance Rapid Mart, version for

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

solutionsDetermines the last fiscal year to be extracted for certain incremental loads. This is used when a “date of last change” is not available in SAP solutions, but the fiscal year of a transaction is available. This is usually the year from global variable $G_EDATE.

$G_EXCHANGE_TYPE_IDData Type: varchar(4)Default Value: “M” - Standard Translation at Average RateWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions



• SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed for lookup of exchange rates to Global Currency

$G_GLOBAL_CURRENCYData Type: varchar(5)Default Value: “USD” - U.S. DollarWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsGlobal Currency Code. You assign a global currency for the Rapid Mart. Used to present a consolidated picture of monetary values in one universal currency.

$G_INT_ORDER_CATEG_PPData Type: varchar(2)Default Value: “10”Where Used: • SAP BusinessObjects Production Planning Rapid Mart, version for

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

solutionsPRODUCTION_ORDER_FACT is a common table in each of these Rapid Marts. However, we extract a different Order Category in each. The default values for Production Orders (PP Rapid Mart) is 10Note: If you have only the PP Rapid Mart set values for both $G_INT_ORDER_CATEG_PP and $G_INT_ORDER_CATEG_PS to 10.

$G_INT_ORDER_CATEG_PSData Type: varchar(2)Default Value: “20”Where Used: • SAP BusinessObjects Production Planning Rapid Mart, version for

SAP solutions



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

PRODUCTION_ORDER_FACT is a common table in each of these Rapid Marts. However, we extract a different Order Category in each. The default values for Network Orders (PS Rapid Mart) is 20Note: If you have only the PS Rapid Mart set values for both $G_INT_ORDER_CATEG_PP and $G_INT_ORDER_CATEG_PS to 20.

$G_ORIG_SDATEData Type: datetimeDefault Value: NULLWhere Used: • SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions• SAP BusinessObjects General Ledger Rapid Mart, version for SAP

solutions• SAP BusinessObjects HR Rapid Mart, version for SAP solutions• SAP BusinessObjects Inventory Rapid Mart, version for SAP

solutionsThis is set on the first (initial) load. It is the value of $G_SDATE at the time of that first load. It is stored in database table AW_FIRST_RUN_DATE. During “DELTA” (incremental) loads, it is retrieved from that table. It is used in several Rapid Marts to determine the start date for the load of OPEN items. It works in conjunction with variable $G_ABSOLUTE_START_DATE for incremental loads that do not carry a “date of last change” in the SAP solutions tables.

$G_STARTFISCALYEARData Type: intDefault Value: NULLWhere Used:• SAP BusinessObjects Accounts Payable Rapid Mart, version for


SAP solutions



• SAP BusinessObjects Cost Center Rapid Mart, version for SAP solutions

• SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions

• SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions

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

Determines the first fiscal year to be extracted for certain incremental loads. This is used when a “date of last change” is not available in SAP solutions, but the fiscal year of a transaction is available. This is usually the year from global variable $G_SDATE.

Used in Only 1 Rapid Mart

$G_ADDRESS_VERSIONData Type: varchar(1)Default Value: “ “ A single spaceWhere Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed for Extraction of Central Address dimension from table ADRC. Default value is a single space.

$G_BUS_PARTN_SDATEData Type: datetimeDefault Value: System Date - 8Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed in data flow R3_SalesOrdVBPADelta. Tells how many days back in time we will check for changes in sales document partners (bill-to partner, ship-to partner, etc.) Used in conjunction with variable $G_BUS_PARTNER.

$G_BUS_PARTNERData Type: varchar(1)Default Value: Sunday = Yes, all other days = No



Actual ATL Language Code: “ifthenelse(day_in_week(sysdate())=7,'Y','N')”Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed in Component Work Flow C_SalesOrderNumberDelta_SAPIf “Y” (Sunday), the Rapid Mart will extract an incremental load of business partners going back the number of days set in variable $G_BUS_PARTN_DATE (see above).

$G_COST_OF_SALES_LEDGER_IDData Type: varchar(2)Default Value: “0L”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsIn New GL, identifies the subset of the New FI-SL Standard Ledger that is loaded into the Cost of Sales Detail and Summary Subject Areas. Choose the Ledger ID in your business that best captures the Cost of Sales functionality.

$G_COUNTRY_GRPData Type: varchar(2)Default Value: “10”Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsDefault Country Grouping Code for HR as determined in SAP solutions table T500L.

$G_DEL_PERIODData Type: datetimeDefault Value: System Date - 180Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed in Sales Order Incremental Load. Determines how far back (in days) the Rapid Mart checks for orders that have been deleted in SAP solutions.

$G_DEL_REJECT_REASONData Type: varchar(2)Default Value: “DD”



Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsIdentifier used in the REJECT_REASON_ID field of SALES_ORDERS_FACT when a sales order line has been deleted in SAP solutions. The code is also added to the dimension table REJECT_REASON with the description “Deleted”.

$G_DROP_SHIPData Type: varchar(1)Default Value: “Y” - Calculate backlog for third-party deliveryWhere Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsThird-party deliveries are those that are delivered by an outside (third-party) organization such as a fulfillment house. They can also be for an intangible material (such as a service) where no physical item is delivered.When set to “Y” (Yes) the Rapid Mart calculates backlog as:• Qty Ordered - Qty Invoiced (for third-party items)• Qty Ordered - Qty Delivered (for all other items).When set to “N” (No) the Rapid Mart calculates backlog as:• Qty Ordered - Qty Delivered (for all items).

$G_GL_ACCOUNT_HIER_NAMEData Type: varchar(10)Default Value: “@GL”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsThe GL Account Hierarchy tables in the Rapid Mart use field “HIER_ID” to identify the source of the hierarchy entry. Data from SAP solutions transaction GS03, source hierarchy GLT0-RACCT are assigned “@GL”You can change the assignment of this variable. However, this is not a requirement. See Technical Implementation Chapter in the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions User Guide for more information.


$G_GL_SUM_PLAN_LEDGER_ID
Data Type: varchar(2)Default Value: “L6”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsIn New GL, identifies the subset of the New FI-SL Standard Ledger that is loaded into the GL Plan and GL Summary Subject Areas. Choose the Ledger ID that best captures GL Summary and GL Plan functionality.

$G_GL_VERSIONData Type: varchar(3)Default Value: (see below)Legal Values: “OLD” or “NEW”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsTells which version of SAP solutions GL Module you use. Using “NEW” with SAP solutions releases older than ECC 5.0 is not possible as the New GL module did not exist in these earlier releases. In the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions, there are two jobs, one for OLD GL and one for NEW GL. The default value in the NEW GL job is “NEW”. The default value in the OLD GL job is “OLD”.

$G_HIRE_ACTION_01Data Type: varchar(2)Default Value: “01”Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsHiring Action Variable 01

$G_HIRE_ACTION_02Data Type: varchar(2)Default Value: “90”Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsHiring Action Variable 02



$G_HIRE_ACTION_03Data Type: varchar(2)Default Value: “K1”Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsHiring Action Variable 03

$G_INIT_HIST_CHGData Type: varchar(1)Default Value: “Z”Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed during the initial load of SALES_ORDER_HISTORY table.IF default value “Z”, then • SALES_ORDER_HISTORY.QTY_DELTA_ORDER_SLSUOM = 0• SALES_ORDER_HISTORY.AMT_DELTA_NET_VALUE_TRX = 0 If any other value, then • SALES_ORDER_HISTORY.QTY_DELTA_ORDER_SLSUOM =

SALES_ORDER_FACT.QTY_ORDER_SLSUOM• SALES_ORDER_HISTORY.AMT_DELTA_NET_VALUE_TRX =

SALES_ORDER_FACT.AMT_NET_VALUE_TRX

$G_MALFUNCTION_CAUSEData Type: varchar(20)Default Value: “5”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsCatalog type to use for Malfunction Cause on Notifications. Choose your system notification catalog group type for “Cause”.

$G_MALFUNCTION_DAMAGEData Type: varchar(20)Default Value: “C”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutions



Catalog type to use for Malfunction Damage on Notifications. Choose your system notification catalog group type for “Damage”.

$G_MALFUNCTION_OBJ_PARTData Type: varchar(20)Default Value: “B”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsCatalog type to use for Malfunction Object Part on Notifications. Choose your system notification catalog group type for “Object Part”.

$G_MRP_RESULTS_DELETEData Type: varchar(1)Default Value: “N”Where Used: SAP BusinessObjects Production Planning Rapid Mart, version for SAP solutionsDetermines if MRP Results should be deleted before an Incremental Load. • Y = Delete before Incremental Load. • N = No Delete before Incremental Load

$G_ONTIME_DELIV_WINDOWData Type: intDefault Value: 15 daysWhere Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsUsed by On Time Delivery Section. Tells the system to limit On Time Delivery loads to a date range based on the Sales Schedule Line’s Planned Goods Issue Date (SAP solutions field VBEP.WADAT). It means that the On Time Delivery will only process Sales orders scheduled to ship between 15 days in the past and 15 days in the future from system date.

$G_PC_ACCOUNT_HIER_NAMEData Type: varchar(10)Default Value: “@PC”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions



The GL Account Hierarchy tables in the Rapid Mart use field “HIER_ID” to identify the source of the hierarchy entry. Data from SAP solutions transaction GS03, source hierarchy GLPCT-RACCT are assigned “@PC”You can change the assignment of this variable. However, this is not a requirement. See Technical Implementation Chapter in the SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutions User Guide for more information.

$G_PROFIT_CENTER_LEDGER_IDData Type: varchar(2)Default Value: “L5”Where Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsIn New GL, identifies the subset of the New FI-SL Standard Ledger that is loaded into the Profit Center Detail and Summary Subject Areas Choose the Ledger ID that best captures Profit Center Summary and Profit Center functionality.

$G_REHIRE_ACTION_01Data Type: varchar(2)Default Value: "JD"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsRehiring Action Variable 01

$G_REHIRE_ACTION_02Data Type: varchar(2)Default Value: "N7"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsRehiring Action Variable 02

$G_RETIRE_ACTIONData Type: varchar(2)Default Value: "ZP”



Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsRetirement Action

$G_SAP_VERSIONData Type: intDefault Value: System Determined - see belowWhere Used: SAP BusinessObjects General Ledger Rapid Mart, version for SAP solutionsAutomatically determined in the Rapid Mart jobs. The first digit of the SAP solutions system variable SY-SAPRL. See Work Flow C_SAPVersion for more details. This value is also stored in the one row target table SAP_VERSION.Attempting to run the “NEW” GL job with SAP solutions older than release ECC 5.0 will cause the job to fail.

$G_SCHOOL_TYPEData Type: varchar(2)Default Value: "50"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsSchool Type

$G_SERVICE_INTERVAL_01Data Type: INTDefault Value: 6 (1/2 year)Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of 5 Intervals for determining Employee Length of Service. Values are in Months.

$G_SERVICE_INTERVAL_02Data Type: INTDefault Value: 12 (1 year)Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutions



One of 5 Intervals for determining Employee Length of Service. Values are in Months.

$G_SERVICE_INTERVAL_03Data Type: INTDefault Value: 36 (3 years)Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of 5 Intervals for determining Employee Length of Service. Values are in Months.



$G_TABLE_EQUIPMENTData Type: varchar(20)Default Value: “EQUI”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsInitialize according to your system class type for Equipment master table name

$G_TABLE_FUNCTL_LOCATNData Type: varchar(20)



Default Value: “IFLOT”Where Used: SAP BusinessObjects Plant Maintenance Rapid Mart, version for SAP solutionsInitialize according to your system class type for Functional Location master table name

$G_TASK_TYPE_PROBATION_ENDData Type: varchar(2)Default Value: “01”Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsProbation End Task Type

$G_TERMINATION_ACTIONData Type: varchar(2)Default Value: “10”Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsTermination Action

$G_VALID_DATEData Type: datetimeDefault Value: System Date (without Time)Where Used: SAP BusinessObjects Sales Rapid Mart, version for SAP solutionsThis is identical to variable $G_LOAD_DATE without the timestamp (midnight, beginning of the day). Used in the incremental load of Sales Organization Hierarchy for comparison to with the VALID_TO dates. Do not change the value in this variable.

$G_WAGE_TYPE_01Data Type: varchar(4)Default Value: "/101"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutions



One of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_02Data Type: varchar(4)Default Value: "/110" Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.




$G_WAGE_TYPE_06Data Type: varchar(4)



Default Value: "/405" Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_07Data Type: varchar(4)Default Value: "/406"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.







$G_WAGE_TYPE_12Data Type: varchar(4)Default Value: "/5U0"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_13Data Type: varchar(4)Default Value: "/5U1" Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_14Data Type: varchar(4)Default Value: "MI10" Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_15Data Type: varchar(4)Default Value: "/102"



Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.

$G_WAGE_TYPE_16Data Type: varchar(4)Default Value: "////"Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsOne of upto 20 Wage Types used in SAP solutions table PCL2. Set Values to "////" if not used.







$G_WORKDAY_EDATEData Type: datetimeDefault Value: 01-Jan-1994Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsFirst date of date range to populated Working Days dimension

$G_WORKDAY_SDATEData Type: datetimeDefault Value: 31-Dec-2006Where Used: SAP BusinessObjects HR Rapid Mart, version for SAP solutionsLast date of date range to populated Working Days dimension

Setting Global Variables

Job PropertiesThe default values for most Global Variables are set on the Job Properties window (shown below) of the Rapid Mart jobs. The exceptions are Global Variables that are conditional (an “IF” statement is required).The conditional Global Variables are set in the “InitializeJob” Script (see below). The script is a common component (identical across all Rapid Marts).



Job Properties:

“InitializeJob” ScriptThe script is divided into the same sections categorizing Global Variables as shown above:• Used in All Rapid Marts• Used in 2 to 10 Rapid Marts• Used in Only 1 Rapid MartEach of these sections in the script shows the same information as the sections above as comments.These are followed by a fourth section where the Conditional Global Variables are set.



Note: The “InitializeJob” script is the first executable in any Rapid Mart job. If you have set Global variables on the Job Properties window in Data Services and also in the “InitializeJob” script, the values in the script will be used. They will override any setting in the Job Properties window.Tip: We suggest that you not touch the settings in the Job Properties window. Make any changes to the Global Variable settings in the InitializeJob script, as shown below. Thus, you can preserve the original “as delivered” settings while still using your own.Custom Global Variable Settings:.

Next, the fourth section of the “InitializeJob” script sets the Conditional Global Variables.



Conditional Global Variables in InitializeJob Script:

The Conditional Settings section also determines that certain global variable settings are accurate and compatible:• $G_LOAD_TYPE - Is either “FIRST” or “DELTA”. Any other setting will

cause the job to abort• $G_GL_VERSION - Is either “OLD” or “NEW”. Any other setting will

cause the job to abort.This section also calls certain Rapid Mart functions to properly set up the job environment:• AW_StartJob - Stores the current job execution parameters in table

AW_JOBEXECUTION.• RM_PutFirstRunDate - Called in “FIRST” (initial) loads only. Stores the

contents of $G_SDATE and $G_EDATE for the “FIRST” (initial) load in table AW_FIRST_RUN_DATE. These dates are important in delta (or incremental) loads later on.


Using the Rapid MartExecuting the job 7

• RM_GetFirstRunDate - Called in “DELTA” (incremental) loads only. Retreives the value of $G_SDATE stored in table AW_FIRST_RUN_DATE. The value retreived is stored in global variable $G_ORIG_SDATE. Consult the Techinical Implementation Chapter for each individual Rapid Mart for more details on how this is used.Note: If you set your own value for $G_ORIG_DATE before the call to RM_GetFirstRunDate, the Rapid Mart will use your value and not retreive the value in AW_FIRST_RUN_DATE.

Executing the jobBefore executing the job, make sure that the configuration steps in "Data Services Supplement for SAP" have been completed and the connection to SAP server is established.The steps needed to execute a job, depend on the type of job:• Initial (First) Extraction and Load • Incremental (Delta) Extraction and Load

Initial (First) Extraction and Load1. In the project area right-click in the HR_Load job to access the Properties

window.2. Edit the job Global Variable properties:

a. Make sure that the value for the $G_LOAD_TYPE variable is set to ‘FIRST’.

b. In either the Properties window, or the job initialization script, set the starting and ending dates for the initial load.

c. Set the starting date (the value for $G_SDATE) low enough to select the earliest data desired for all target tables. Set the ending date (the value for $G_EDATE) to the current date.

d. Set values for the rest of global variables in the Properties window or the job initialization script, and click OK to accept the set properties and to close the window.

Note: We suggest setting global variables in the job initialization script. That way the Properties window will preserve the “as delivered” settings, while the initialization script will show your custom settings. The initialization script executes after the values in the Properties window are set, and overrides the setting in the Properties windows.


Using the Rapid MartExecuting the job7

You can also set global variable values after you select Execute command from the drop-down menu in the project area.For more information about the variables see “Global Variables” on page 318.

3. Run the job.a. In the project area, right-click the job and choose Execute.

Data Services opens the Execution Properties window.b. Select the desired execution properties.

At this point, you must decide whether or not to enable automatic recovery. See Data Services User Guide for more information.If you enabled automatic recovery and a job failed, you can recover from the failed job at this time.

c. Click OK to accept the selected properties and start the job.The job completes several steps:• Initializes the variables to the values you set in the initialization

script.• Calls components to load the tables. Generally, the job truncates

the tables before loading them during the initial job.Some components, such as work flows that load dimension tables, are repeated. The job only executes these components the first time because these work flows and data flows are set to “execute only once.”

4. Check the error log and the execution status table to make sure the job ran successfully.

Incremental (Delta) Extraction and Load1. Open the Properties window for job HR_Load by right-clicking on the job

in the project area and selecting Properties command. Edit the job Global Variable properties (remember, you can also set the values in the job initialization script instead of using the Properties window):a. Make sure that the value for the $G_LOAD_TYPE global variable is

set to ‘DELTA’.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.


Using the Rapid MartCustomizing the Rapid Mart 7

c. Set values for the rest of global variables as needed. d. Click OK to accept the set properties and to close the window.Note: We suggest setting global variables in the job initialization script. That way the Properties window will preserve the “as delivered” settings, while the initialization script will show your custom settings. The initialization script executes after the values in the Properties window are set, and overrides the setting in the Properties windows.

2. Run the job.a. In the project area, right-click the job and choose Execute.

Data Services opens the Execution Properties window. b. Select the desired execution properties.

At this point, you must decide whether or not to enable automatic recovery. See Data Services User Guide for more information about automatic recovery. If you enabled automatic recovery and a job failed, you can recover from the failed job at this time.

c. Click OK to accept the selected properties and start the job.The job completes several steps:• Initializes the variables to the values you set in the initialization

script.• Calls components to load the tables incrementally, inserting new

and changed data since the last job execution. The job deletes outdated data from the target tables, and reloads the target tables with new and changed data. The incremental load uses the append option to load most tables.Some components, such as work flows that load dimension tables, are repeated. The job only executes these components the first time because these work flows and data flows are set to “execute only once.”

3. Check the error log and the execution status table to make sure the job ran successfully.

Customizing the Rapid MartRapid Marts are easy to customize. You can easily:• Customize the Rapid Mart data schema to meet your specific needs.


Using the Rapid MartCustomizing the Rapid Mart7

• Expand the Rapid Mart to be used with various integrated query, reporting, and data analysis applications.

• Transport Rapid Mart components and sections to different Rapid Marts using the Data Services export and import facilities.

For example, to customize the Rapid Mart, you might:• Change column names to be more meaningful in your business

environment.• Remove columns or tables you do not need in your business

environment.• Add:

• Columns from tables already sourced• New columns from tables not extracted • Aggregates• Calculated or scrubbed data

You change your Rapid Mart in exactly the same way you would change any Data Services application. For information about how to make such changes, see the Data Services product documentation.Note: In general, whenever you make a change, you need to perform impact analysis. Impacts to consider include: • Initial load• Incremental load• Target tables• Integrity of existing Rapid Mart data• Integrity between batch extraction and real time jobs• Downstream analysis and reporting and Web applications• Variable settings used by imported components and sections• Other Rapid Mart (in a multi-Rapid Mart environment) If you are implementing the Rapid Mart on Oracle platforms, you can take advantage of pre-processing and post-processing performance tuning stored procedures described in “Fact Table Stored Procedures” on page 430 and in the Rapid Mart Deployment Guide.Additional HR Rapid Mart specific customizations are presented in Chapter 8: Customizing the Rapid Mart


Customizing the Rapid Mart

chapter

Customizing the Rapid MartOverview8
Overview
All Rapid Marts are designed as user-customizable templates. The HR Rapid Mart specifically requires custom “localization”. As written, it is a U.S. specific template. Payroll, Benefits, and other sections are designed to work within the U.S. regulatory environment. Here are some examples of customizations you may need to make to localize the Rapid Mart for different jurisdictions:• Payroll Customization - Three different types of customization are shown.• Leave Entitlement Customization - How to use different infotypes in a

subject area.• Function Calls in Custom ABAP Transforms - Describes how Custom

ABAP Transforms call SAP solutions functions.• Conclusion

Payroll CustomizationPayroll can require several steps in localizing to a different jurisdiction. As a prerequisite for these customizations we suggest an investigative effort to find the following information. Each of these introduces a different level of complexity in the customization:• Identification Areas used• Wage Types used• Payroll Structures used• Payroll Cluster tables usedThe customization suggestions below are a guideline. Those making the customizations should be familiar with:• The SAP solutions HR module• ABAP Programming• Data ServicesOf these, changing the Identification area is the simplest.

Changing the Identification AreaPayroll Cluster tables (PCL1 through PCL5) are organized into various “identification areas” that are country-specific. This corresponds to column RELID in the tables. Each RELID column has a SAP solutions data dictionary domain (table DD07T) that specifies the legal values.We use two in the Rapid Mart Payroll section:


Customizing the Rapid MartPayroll Customization 8

• CU - Cluster directory. Used to populate structure PC261.• RU - Payroll results (USA). Used to populate structures PC207 and

PC22Y.Of these, “RU” is country specific and needs to change when the Rapid Mart is localized for another country. Choose the Identification area for your country. Example: The Identification Area for Spain is “RE”. Next, edit the custom ABAP code snippets used in the Custom ABAP Transforms for PC207 and PC22Y. Locate the two files PC207.aba and PC22Y.aba. They should be in the Generated ABAP directory you defined in your R3 Data Store.Tip: Make backup copies of both files before you edit them. Manual editing is very prone to human error. A backup copy ensures you can recover from such errors.Edit the files in a text editor such as Wordpad. Do not use Notepad, as it may corrupt the files. In each file, there are 2 places where you should change the Identification Area, as shown below. In our example we would change “RU” for U.S. to “RE” for Spain:


Customizing the Rapid MartPayroll Customization8

Note: There are numerous comments (lines beginning with *) in the two ABAP files with references to Identification Area “RU”. While not required, it is a good idea to change these as well.

Include All Wage TypesBy default the Rapid Mart allows up to 20 Wage Types in Payroll. These are Identified by global variables $G_WAGE_TYPE_01 through $G_WAGE_TYPE_20. Wage Types are used as selectivity criteria when extracting data from the payroll clusters. If more than 30 wage types are required, you should consider extracting all wage types and filtering any you do not need in the Rapid Mart target database. We do not recommend using more than 30 wage type variables for extraction performance reasonsWage Types are passed to the PC207 and PC22Y ABAP Transforms as parameters.



Locate the two files PC207.aba and PC22Y.aba. They should be in the Generated ABAP directory you defined in your R3 Data Store.Tip: Make backup copies of both files before you edit them. Manual editing is very prone to human error. A backup copy ensures you can recover from such errors.Edit the files in a text editor such as Wordpad. Do not use Notepad, as it may corrupt the files.In each file, comment out the “IF” statement that restricts Wage Types as shown below:

You comment each line by putting an asterisk (*) at the beginning of the line.


Adding Additional Wage Types
Note: We suggest that you do not exceed 30 distinct Wage Types for performance reasons. If you require more than 30 Wage Types, see previous section: Include All Wage Types.Adding additional Wage Types requires these changes:1. Add additional Global Variables for Wage Types to the HR Rapid Mart

job:

Make sure each wage type is defined as varchar(4).



2. Add Additional Wage Type Parameters to the ABAP Data Flows, such as R3_PayrollPC207:

3. Pass values of the New Global Variables to the New Parameters to the ABAP data flow from the calling data flow



After defining the Wage Type parameters in previous step, you should see additional “Calls” in the calling data flow (EDF_PayrollFact_SAP):

4. Modify the Custom ABAP Code.Locate the two files PC207.aba and PC22Y.aba. They should be in the Generated ABAP directory you defined in your R3 Data Store.Make backup copies of both files before you edit them. Manual editing is very prone to human error. A backup copy ensures you can recover from such errors.



Edit the files in a text editor such as Wordpad. Do not use Notepad, as it may corrupt the files. You will be adding additional “Append” statements to the ABAP. Make “Append” changes as shown:



Note: the $PARAMxx numbers inside the ABAP will not correspond to the global variable numbers. The $PARAMxx will be 2 numbers higher than the global variables. This is because $PARAM1 and $PARAM2 are the values for $G_SDATE and $G_EDATE. Example: • $PARAM23 = $G_WAGE_TYPE21• $PARAM24 = $G_WAGE_TYPE22, etc.

Changing the Payroll Structure and Cluster TableShould you need to use a different SAP solutions payroll structure, cluster table, or both; the changes are more complicated. Note: You should be familiar with SAP solutions HR module architecture before attempting this type of change. Start by identifying the payroll cluster table, Identification Area, and payroll structure to populate.The ABAP transforms are named to show the structure extracted. Therefore, you should create a new ABAP transform for the new structure.



In Data Services, open the Object Library, choose Transforms tab, then right-click on “Platform” and choose “New ABAP Transform:

A new ABAP Transform called “New_ABAP_Transform” will be created.Next, rename the transform to the name of the new Payroll Structure you will be using, for this example we will use Payroll Structure PC2071.



After renaming “New_ABAP_Transform” to “PC2071”, Open the ABAP transform:



This will open an editing window where you can add the columns (fields) from the Payroll Structure:



When you are done, it should look like this:

Next, write the ABAP code snippet. For this example, you can start by copying the existing PC207.aba to a new file called PC2071.aba.



Then, proceed to edit the new file as follows:



Change the <<<OTAB>>> fields to those in the new payroll structure PC2071:

Save all changes and exit your editor.


Customizing the Rapid MartLeave Entitlement Customization 8

Next step is to create an ABAP Data flow to extract the data using the new Custom ABAP Transform. You can replicate existing data flows and modify them to use the new ABAP Transform:Example: Replicate ABAP Data Flow R3_PayrollPC207 and rename it to R3_PayrollPC2071. Then edit the new ABAP Data Flow to use the new ABAP transform PC2071.This new ABAP Data Flow can be used in payroll customizations.

Leave Entitlement CustomizationDifferent jurisdictions (countries) use different infotypes to store HR data. Example: In the U.S., infotype PA0005 stores Leave Entitlement Data. However infotype PA0261 is used in Australia. If you are implementing the HR Rapid Mart in Australia, you need to change the Leave Entitlement section to used PA0261 instead of PA0005.Note: Each localization change will bring a unique set of challenges and requirements to the customization effort. What works in Australia will not work for another country.Here is a quick overview of customizing Leave Entitlement for Australia:

Extract New Infotype PA02611. Replicate and rename the following Data Flows:

2. Modify each of the new data flows to use PA0261 instead of PA0005.3. Modify DF_Infotype0261LeaveAustralia_SAP to call

EDF_Infotype0261LeaveAustralia_SAP instead of EDF_Infotype0005Leave_SAP

Existing Data Flow (Replicate These):

Rename Replicated Copies to:

R3_Infotype0005Leave R3_Infotype0261LeaveAustraliaR3_Infotype0005Validate R3_Infotype0261ValidateEDF_Infotype0005Leave_SAP EDF_Infotype0261LeaveAustralia_SAPDF_Infotype0005Leave_SAP DF_Infotype0261LeaveAustralia_SAPDF_Infotype0005LeaveDelta_SAP DF_Infotype0261LeaveAustraliaDelta_

SAP


Customizing the Rapid MartLeave Entitlement Customization8

4. Modify DF_Infotype0261LeaveAustralia_SAP to write to a new target table for PA0261.Tip: You can use a “template” table to quickly create a target table to receive the data from infotype PA0261. Name the new table HR_INFOTYPE_0261_LV_AUSTRALIA (30 character limit)

5. Modify DF_Infotype0261LeaveAustraliaDelta_SAP to call EDF_Infotype0261LeaveAustralia_SAP instead of EDF_Infotype0005Leave_SAP

6. Modify DF_Infotype0261LeaveAustraliaDelta_SAP to write to a new target table for PA0261.Tip: You can use a “template” table to quickly create a target table to receive the data from infotype PA0261. Name the new table HR_INFOTYPE_0261_LV_AUSTRALIA (30 character limit)

7. Modify Work Flow EDF_Infotype0261LeaveAustralia_SAP to include R3_Infotype0261LeaveAustralia instead of R3_Infotype0005Leave

8. Modify Work Flow WF_Infotype_SAP to include DF_Infotype0261LeaveAustralia_SAP.

9. Modify WF_InfotypeDelta_SAP to include DF_Infotype0005LeaveDelta_SAP.

10. Modify DF_InfotypeValidation_SAP to include R3_Infotype0261Validate11. Run and test all new work flows / data flows to make sure they are

working correctly.

Modify Leave Entitlement to use PA02611. Modify DF_LeaveValidFromDate_SAP to use the new

HR_INFOTYPE_0261_LV_AUSTRALIA table instead of HR_INFOTYPE_0005_LEAVE

2. Modify DF_LeaveEntitlementFact_SAP to use the new HR_INFOTYPE_0261_LV_AUSTRALIA table instead of HR_INFOTYPE_0005_LEAVE

Note: The structure of PA0261 is very different than that of PA0005. You will need to redefine the structure (columns) of the LEAVE_ENTITLEMENT_FACT and LEAVE_ENTITLEMENT_STAGE tables accordingly. This may also require additional changes in these data flows:• DF_LeaveEntitlmentWorkaysStage_SAP• DF_LeaveEntitlmentDeductStage_SAP• DF_LeaveEntitlementUpdate_SAP


Customizing the Rapid MartFunction Calls in Custom ABAP Transforms 8

Function Calls in Custom ABAP TransformsThe extracts for infotypes PA0167 and PA0168 both call SAP solutions functions to gather benefit costs, rules, etc. As you customize the HR Rapid Mart to include new functionality you may discover that you will also need to call internal functions to return proper data. Here is an overview of how it is done for PA0167 and PA0168. You can use this as a guideline for any customizations you make. Note: You should be very familiar with the HR Module, ABAP programming, and Data Services before making these customizations.The key here is that we make two passes through the infotype data to call the functions. The first pass extracts infotype data and writes it to a flat file on the SAP solutions server. The second pass reads this file, calls the functions, and updates the data with the results.The second pass uses a custom ABAP transform to call the SAP solutions functions. The functions return data as internal tables. Therefore, we cannot import them into Data Services and use them directly.

PA0167 ExampleThe logic for both PA0167 and PA0168 is quite similar, however we will use PA0167 as our example.


Customizing the Rapid MartFunction Calls in Custom ABAP Transforms8

Examine work flow C_InfoType0167Health_SAP:

Data Flow DF_Infotype0167HealthFile_SAP reads the PA0167 table into flat file PA0167.datData Flow DF_Infotype0167Health_SAP reads file PA0167.dat, calls the functions and puts the results in table HR_INFOTYPE_0167_HEALTH on the target database. Data Flow DF_Infotype0167Health_SAP contains ABAP Data Flow R3_Infotype0167HealthFunction. This in turn, calls the custom ABAP Transform PA0167.Like all Custom ABAP transforms this one contains an ABAP code snippet stored as a file in the “generated ABAP directory” you define in your SAP solutions Data Store. This file is called PA0167_ABAPXFORM.aba.Note: The Rapid Mart contains two versions of PA0167_ABAPXFORM.aba one for SAP solutions release 4.6, and one for SAP solutions release 5.0 or newer. See Chapter 6: Installing the Rapid Mart for more details on how to choose the correct version of the file.



Key elements of the ABAP code snippet are:1. Definition of data. Here data fields used by the function calls are defined.

Note: The field num_char is used to receive the number of dependents from the incoming PA0167.dat file. The incoming data file is all characters, and this field will be converted to a numeric value later on.Note: the table ERROR_TABLE is returned by the function call:


Customizing the Rapid MartFunction Calls in Custom ABAP Transforms8

2. Read incoming PA0167.dat data file, and split it into component fields:



3. Setup and call the function:


Customizing the Rapid MartConclusion8
Differences Between PA0167 & PA0168
The main difference between PA0167 and PA0168 is the number of functions called. PA0167 calls only one function PA0168 calls five.If you examine the code snippet for PA0168 (PA0168_ABAPXFORM.aba) you will find that it is very similar in structure to the example for PA0167, but contains five function calls. The key here is to understand: • which function calls are needed• the input and output parameters each function• the correct order in which to call the functions. Again this is only possible with a good understanding of the architecture of the HR module in SAP solutions, and with good ABAP programming skills.

ConclusionThe SAP solutions HR Module is very flexible, allowing customers around the globe to implement Human Resources according to the rules of their own particular jurisdiction. The SAP BusinessObjects HR Rapid Mart, version for SAP solutions is a flexible template that allows you to customize and localize your Human Resources reporting in according to the same rules.


Technical Implementation

chapter

Technical ImplementationOverview9
Overview
This chapter provides technical details about how the SAP BusinessObjects HR 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.The chapter starts by describing common logic and transformations shared by four of the sections (or subject areas) in the Rapid Mart:• Common Transformations for Date Effective Sections

• Incremental Load Challenges• Dimensions With Surrogate Keys• Minimum Date Driver• Dimension Valid Date Range Driver• Fact Valid Date Range Driver• Vertical and Horizontal Fact Organization

Next, are technical details unique to each subject area or section:• Infotypes Section• Employee Administration Section • Leave Entitlement Section• Benefit Enrollment Section• Employee Wage Section• Payroll SectionAdditional technical details for the Rapid Mart are included in:• Optimization Techniques• Dealing with NULL values• Fact Table Stored Procedures• Fiscal Periods & Time Dim Load

Common Transformations for Date Effective Sections

Four of the sections (or subject areas) in the Rapid Mart are derived from date effective infotype tables and date effective dimensions. They are:1. Employee Administration


Technical ImplementationCommon Transformations for Date Effective Sections 9

2. Benefit Enrollment3. Leave Entitlement4. Employee WageThese four areas use a set of common transformation techniques. These are presented and discussed in the order of use (or load) within the Data Services job.

Incremental Load ChallengesThe four subject areas listed above do not have incremental (delta) loads. The Rapid Mart does a full refresh of these subject areas on each run of the Data Services job.There are several reasons why a delta load is not practical:• The HR module allows changing records in the past• The HR module allows deleting records created in the past• Delta logic becomes extremely complex and inefficient since it requires

recalculation of records merged from several infotypes for every employee if any of the changes describe above occur.

Delta loads are available for:• Infotypes (PAxxxx tables). These are the source tables for the four

subject areas and also for certain dimensions (see Dimensions With Surrogate Keys). Each infotype record carries a “date of last change” making a delta possible.

• Payroll. This is a fifth subject area, not based on infotypes. Payroll is based Cluster tables that carry a “date of last change” thus making the delta load possible.

The infotype source tables are in reality master data, not transactional data. The data volume is not large enough to present performance challenges. Even in large organizations with thousands of employees, Infotype data typically changes 2 or 3 times a year per employee.The average “large” company has about 50,000 employees. These are not large volumes in the source infotypes, and can be handled efficiently with a full load.

Dimensions With Surrogate KeysThe first step in loading a subject area is to load its component dimensions. Most Rapid Marts use the natural primary key for dimensions. However, certain dimensions in the HR Rapid Mart are based on date effective tables.


Technical ImplementationCommon Transformations for Date Effective Sections9

That is, each row in the dimension table has valid from date and a valid to date. Additionally, the fact tables in the HR Rapid Mart are also date effective. This sets up a performance issue when we try to join data between fact and dimension. Because we would need to compare date ranges using the greater than (>) and less than (<) operators; queries would be inefficient.To avoid this issue, date effective dimensions in the HR Rapid Mart carry surrogate primary keys. The same key value is carried as a foreign key in the fact tables that join to these dimensions. This allows us to use a simple one column join between fact table and dimension in the universe (semantic layer). Example: The BENEFIT_PLAN dimension joins to BENEFIT_ENROLLMENT_FACT. Without the surrogate keys, the join would be:

BENEFIT_ENROLLMENT_FACT.BENFT_AREA_ID = BENEFIT_PLAN.BENFT_AREA_ID and

BENEFIT_ENROLLMENT_FACT.PROGRAM_GRP_ID_01 = BENEFIT_PLAN.PROGRAM_GRP_ID_01 and

BENEFIT_ENROLLMENT_FACT.PROGRAM_GRP_ID_02 = BENEFIT_PLAN.PROGRAM_GRP_ID_02 and

BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_ID = BENEFIT_PLAN.BENFT_PLAN_ID and

BENEFIT_ENROLLMENT_FACT.VALID_FROM_DATE <= BENEFIT_PLAN.VALID_TO_DATE and

BENEFIT_ENROLLMENT_FACT.VALID_TO_DATE >= BENEFIT_PLAN.VALID_TO_DATE and

BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_TYPE_ID = BENEFIT_PLAN.BENFT_PLAN_TYPE_ID

With the surrogate keys, the join is:BENEFIT_ENROLLMENT_FACT.BENFT_PLAN_KEY =

BENEFIT_PLAN.BENFT_PLAN_KEY When we load the fact table, we use the non-surrogate key join to lookup (function lookup_ext) the correct BENFT_PLAN_KEY value. The lookup also compensates for the fact that a date range in the fact table may point to more than one date range (and surrogate key) in the dimension. When that occurs, the lookup chooses the latest date range available in the dimension.



The call to lookup_ext for BENEFIT_PLAN can be found in data flow DF_BenefitEnrollmentFact_SAP, in the Lookup Query, as function call lookup_ext_5.The edit window for the lookup appears as:

The dimensions using primary surrogate keys are:

Dimension Table Name Primary Key Column Name

BENEFIT_PLAN BENFT_PLAN_KEYBENEFIT_SPENDING_ACCOUNT SPENDNG_ACCT_KEY

EMPLOYEE * EMPLOYEE_KEY



* = Dimension uses natural key (not surrogate key) for join to PAYROLL_FACT and PAYROLL_SUMMARY_FACTNote: PAYROLL_FACT and PAYROLL_SUMMARY_FACT tables are the exceptions. They use the equivalent non-surrogate (or natural) keys. This is because

1. Payroll fact tables are based on clustered tables in SAP solutions, not infotypes. They are not effective date driven like infotypes.

2. Payroll data volume is quite large and requires a delta (incremental) load. Other subject areas are much smaller and do not have a delta load. If we used surrogate keys we would have to do a full refresh as described in the next note.

Note: reloading the dimension tables by themselves may change primary key values so that the foreign keys in the fact table will point to incorrect entries in the dimension. If you reload dimensions using surrogate keys you must also reload all the fact tables, except payroll.

Minimum Date DriverOnce the dimension components are loaded, the fact tables for a subject area are loaded. To build the fact tables, we need to join infotype records (employee information) with dimensional data. Example: BENFIT_ENROLLMENT_FACT joins data from several infotypes as well as data from the JOB dimension.If we simply join data from the infotypes and JOB we can end up with a situation where the JOB pre-dates the employee (the job was created before the employee was hired). This in turn would create invalid date ranges for the fact table where no employee is valid.

INSURANCE_OPTION INSURANCE_OPTION_KEY

JOB * JOB_KEY

LEAVE_TYPE LEAVE_TYPE_KEY

ORGANIZATION_UNIT * ORG_UNIT_KEY

POSITION * POSITION_KEY

SALARY_RANGE SALARY_RANGE_KEYWAGE_TYPE * WAGE_TYPE_KEY

Dimension Table Name Primary Key Column Name



Example: The job “Accountant” was created on 01-Jan. However, nobody was hired to fill that job until 01-June. Joining employee job assignment (infotype) data with the JOB data would yield a 6 month period where no employee was available to fill the position.To compensate for this we choose the earliest valid from date for each employee based on one or more of the infotypes that are used to populate the fact table. We then limit all other infotype and dimension data for that employee to records valid on or after that earliest valid from date. The choice of Infotypes depends on how the fact table is organized. Horizontally organized fact tables use one infotype for the minimum date driver. Vertically organized fact tables have a minimum date driver for each infotype used. See “Vertical and Horizontal Fact Organization” on page 389 for more details.Fact tables using the minimum date driver are:

Within the Data Services job, data flow EDF_ValidFromDateStage_SAP captures the earliest valid from date, and stores this information in table VALID_FROM_DATE_STAGE. The data flow is called during the load of each of the fact tables shown above.

Dimension Valid Date Range DriverSome of the date effective dimensions described in Dimensions With Surrogate Keys are also used to determine date ranges to load in the fact tables for these subject areas:

Fact Table Fact Table Organization

Min Date Driver is Based On Infotype(s):

BENEFIT_ENROLLMENT_FACT Vertical PA0167PA0168PA0169PA0170PA0236

EMPLOYEE_WAGE_FACT Vertical PA0008PA0014PA0015

LEAVE_ENTITLEMENT_FACT Horizontal PA0000EMPLOYEE_ADMINISTRATION_FACT Horizontal PA0000



• Employee Administration• Benefit Enrollment• Employee Wage• Leave EntitlementThe date effective dimensions are:• JOB• POSITION• ORGANIZATION_UNIT• EMPLOYEE• LINE_MANAGER_HIERThe Rapid Mart merges the valid from and valid to date information from these dimensions and loads table DATE_VALID_FROM_DIMENSION.The DATE_VALID_FROM_DIMENSION is joined with data from table VALID_FROM_DATE_STAGE (populated in Minimum Date Driver above), and is then passed into the Fact Valid Date Range Driver described below.

Fact Valid Date Range DriverThe next step is to extract information from the various infotypes that contain the data for the subject area. SAP solutions stores employee data in several Personnel Administration infotypes. An Infotype contains information that is inter-related and is not likely to change simultaneously. For example, information related to an employee’s home address and phone number is contained in a single infotype (PA0006). If an employee moves, both address and phone number are likely to change. But, if the move is the result of a transfer and raise, information contained in other infotypes, such as Basic Pay (PA0008), will also change.Furthermore, even though the raise and transfer happened simultaneously, the employee’s physical move to the new location may happen at a later date. Thus, the changes in infotypes PA0006 and PA0008 may not occur on the same date.To record these changes, each record in an infotype has effective dates — a valid from date and a valid to date. The valid to date for the current record is always 12/31/9999. Infotype tables are date effective, much like the dimensions discussed in Dimensions With Surrogate Keys.When you insert a new record in an infotype, SAP solutions updates the valid to date in the record that was current. The value 12/31/9999 is changed to the day before the new record takes effect. This becomes the last date the old record was in effect.



The new record has a valid from date that is the day after the old record ends and valid to date of 12/31/9999. The validity dates in infotypes change independently of each other. They are not synchronized. In addition there can be “gaps” in the data where no infotype record is valid. Another condition that can occur is that more than one record is valid in a particular infotype for a particular employee.Example: Enrolled in two courses

An employee is enrolled in two education programs, at two different institutions simultaneously:

1. University course from 09/01/2001 to 05/30/20022. Certification program from 03/01/2002 to 07/15/2002.

In this case there would be two records in infotype PA0022 (Education) with overlapping validity dates for that employee.

All these situations present challenges in merging data from the various infotypes for the Rapid Mart. It means we need to break the date effective ranges into smaller intervals corresponding to the changes in validity for each infotype included in the merge.Key goals for merging of this data in the Rapid Mart environment are:• Quick query response time for Analytics (Webi reports, etc.)• Simplify query construct:

• Avoid Universe joins using greater than (>) or less than (<)• Avoid using sub-queries when joining multiple tables

• Reporting ‘as-of-date’, or ‘for the period of’ – past history analysis• Consistent with design of other Rapid Marts (dimensional model)To accomplish these goals we use a series of standardized transformationsExample: Merging data in infotypes for Address (PA0006), Job (PA0001), and Salary (PA0008) for the EMPLOYEE_ADMINISTRATION_FACT. We use the following steps to merge and segment the data into a series of date ranges that eliminate overlap in validity. Here are the steps we follow:1. Merge data from

• The various component infotypes. To handle the “Enrolled in two courses” example above, we include all infotype records where VALID_FLAG = 1. The VALID_FLAG is set during “Infotype Validation” on page 394.

• VALID_FROM_DATE_STAGE table (populated in Minimum Date Driver above)



• DATE_VALID_FROM_DIMENSION table (populated by Dimension Valid Date Range Driver)

into the DATE_VALID_FROM_STAGE table. It looks something like this:

Note: There are multiple date range overlaps, and there is a “gap” in address data from 10/6/2006 - 11/5/2006.



2. The next step is to combine the overlapping date ranges into a single set of distinct date ranges that cover all possible time period and data combinations. This includes any time period “gaps” in the data. In our example, we would created a set of 7 date ranges:

3. The valid date ranges are stored in the table DATE_VALID_DRIVER along with key information to link back to the infotype records.



4. Next, the DATE_VALID_DRIVER is joined with the various infotype records. Attributes (Address, Job, or Salary) for each of the 7 date ranges are assigned. The output looks something like this:

Note: For the “gap” in Address we have included a record for the missing time period, and assigned a “Null” Address value (in gold color). Note: Salary was not defined before 2/1/2003 and is also “Null”.Note: Finally, no job was defined before 1/5/2001. It is also “Null’

5. The next step in the transformation is to is to perform a “lookup” on the foreign keys for dimensions using surrogate primary keys. In our example, this is the JOB dimension. See “Dimensions With Surrogate



Keys” on page 379 for more information on this type of dimension. The final result looks like this and is stored in the fact table EMPLOYEE_ADMINISTRATION_FACT:

Note: Since the JOB dimension is also date effective, there may be multiple date ranges, and therefore multiple foreign keys for the same job title. In the example above JOB_KEY 4516 and 4789 both link to the “Director” job title, but have different effective date ranges in the dimension.

Vertical and Horizontal Fact OrganizationTwo of the infotype based subject areas are vertically organized:1. Benefit Enrollment2. Employee WageTwo of the infotype based subject areas are horizontally organized:1. Employee Administration2. Leave Entitlement



Vertical or horizontal organization determines which infotypes are used for the Minimum Date Driver.

Vertical OrganizationIn vertical organization the fact table has one row for each component infotype used. The fact table has a column that identifies the source infotype.The vertical organization uses the MERGE transform the Data Services to load the fact table, as shown in this screen shot from data flow DF_BenefitEnrollmentFact_SAP, which loads BENEFIT_ENROLLMENT_FACT:



Horizontal OrganizationIn horizontal organization, one row joins data from multiple infotypes. There is no column in the fact table that identifies the source infotype.The horizontal organization uses an Outer Join QUERY transform to load the fact table as shown in this screen shot from the data flow DF_LeaveEntitlementFact_SAP which loads LEAVE_ENTITLEMENT_FACT.


Technical ImplementationInfotypes Section9
Infotypes Section
This subject area includes the infotype records used by the other sections in this chapter. Within the Data Services job for the HR Rapid Mart, the infotypes are extracted from SAP solutions before any other subject area. This is to ensure the infotype data is available for the transformations necessary in other subject areas.Note: This section is not organized as a star schema. The infotype tables are independent of each other and presented solely as master data.The infotypes are the basis for most of the fact tables in the Rapid Mart. They are presented here with minimal transformation as a deeper level of detail for Human Resources reporting.

The infotype tables use in the HR Rapid Mart are:



PA0000 HR_INFOTYPE_0000_ACTION Employee Events records from Infotype PA0000

PA0001 HR_INFOTYPE_0001_ASSIGNMENT HR Master Data: Organizational Assignment from PA0001

PA0002 HR_INFOTYPE_0002_PERSONAL HR master data - infotype PA0002 -- Personal data

PA0005 HR_INFOTYPE_0005_LEAVE HR master data from PA0005 infotype - Leave Entitlement;

PA0006 HR_INFOTYPE_0006_ADDRESS Load Personnel Address and Communications master data from PA0006, PA0105

PA0007 HR_INFOTYPE_0007_WORKTIME HR Master data: Planned Working Time from PA0007

PA0008 HR_INFOTYPE_0008_HISTORY Uses HR_INFOTYPE_0008_PAY to create a salary history that stores prior salary, and salary one year ago;

PA0008 HR_INFOTYPE_0008_PAY HR Master data - Basic Pay from PA0008

PA0014 HR_INFOTYPE_0014_DEDUCTION HR Master Data, Recurring Deductions from PA0014


Technical ImplementationInfotypes Section 9

PA0015 HR_INFOTYPE_0015_PAYMENT HR Master data: Infotype for additional payments, PA0015

PA0016 HR_INFOTYPE_0016_CONTRACT HR Master Data for Contract information from PA0016 infotype

PA0019 HR_INFOTYPE_0019_DATES HR Master data: Monitoring of Dates infotype from PA0019

PA0021 HR_INFOTYPE_0021_DEPENDENT HR master data - infotype PA0021 -- Dependents Personal data

PA0022 HR_INFOTYPE_0022_EDUCATION HR Master data: Education from Infotype PA0022

PA0024 HR_INFOTYPE_0024_QUALIFICATION HR infotype Master PA0024 - Personnel Qualifications

PA0041 HR_INFOTYPE_0041_SPEC HR Master: date specification inforecord PA0041

PA0077 HR_INFOTYPE_0077_PERSONAL HR Master for Additional Personal Data from PA0077

PA0094 HR_INFOTYPE_0094_RESIDENCE HR Master for Residence status in N/A from PA0094

PA0167 HR_INFOTYPE_0167_HEALTH HR Master: Health Plans from Infotype PA0167

PA0168 HR_INFOTYPE_0168_INSURANCE HR Master for Insurance Plans from infotype PA0168

PA0169 HR_INFOTYPE_0169_SAVINGS HR master data for Savings Plan from Infotype 0169

PA0170 HR_INFOTYPE_0170_FLEX HR Master data for Flexible Spending Accounts from infotype PA0170

PA0171 HR_INFOTYPE_0171_BENEFIT HR Master data for General Benefits from infotype PA0171

PA0236 HR_INFOTYPE_0236_CREDIT HR Master data for Credit Plans from infotype PA0236

HRP1000 HR_INFOTYPE_1000_DBTABLE HR Master data for Organizational unit descriptions from the active plan from HPR1000 infotype






The Rapid Mart calls the C_Infotype_Section_SAP work flow to load infotype tables from SAP solutions.

Infotype ValidationThis is the first step in the infotype loads. It prepares data for and works with the “Fact Valid Date Range Driver” on page 384 to determine distinct validity date ranges for the validity dates in all infotypes extracted. The primary key information (including validity dates) from all infotypes are merged into a single data set. The data set is input to the Date Effective transform to create the set of distinct date ranges.The distinct date ranges are then stored in table HR_INFOTYPE_VALIDATION. This table is used in the infotype loads (first and delta) to determine the Validity Flag.If there is more than one record valid at a time (overlapping date ranges) the record with the latest date range has validity flag = 1 and all other overlapping records have validity flag = 0. Records without ovelapping date ranges also have validity flag = 1. The table is used for loading Employee Administration and Benefit enrollment fact tables.Examples:


N/A HR_INFOTYPE_VALIDATION Derived by Data Services Job: Distinct Merge of date-effective records from all infotypes



Person ID

Valid From Date

Valid To Date

Valid Flag

Comment

70043 1966-09-01 1970-12-31 0 These 2 records Overlap. The earlier record has Valid Flag = 0. The later record has Valid Flag = 170043 1970-09-01 1972-04-30 1

70043 1972-09-01 1974-04-30 1 this record has no overlap with previous records for this Person; Valid Flag = 1

70203 1987-09-01 1988-06-30 1 No Overlap, Valid Flag = 1 for Both Records70203 1989-09-01 1992-04-30 1


Technical ImplementationInfotypes Section 9

The validity flag is used to filter the data before generating the Fact / Dimension merge driving table. The infotype validation is implemented as data flow DF_InfotypeValidation_SAP.

Initial (First) and Incremental (Delta) LoadsThe infotype tables carry a change date field (column name AEDTM). This change date is used in both the first (initial) and delta (incremental) loads. All records where AEDTM is between global variables $G_SDATE and $G_EDATE are extracted in both the first and delta loads. In a first load, the window between these two global variables typically covers several years of past data. Thus, the first load will take much longer than the delta.In a delta load the window is much smaller, typically a day or two. Thus, the amount of data is much smaller and the delta load takes less time than the first load.In the first load, data in the infotype target tables is deleted (truncated) before new data is inserted.In the delta load, data is not truncated in the target tables, and the Table Comparison transform is used to update or insert records in the target tables.

Infotypes 0167 (Health) and 0168 (Insurance)These two infotypes use custom ABAP transforms to call certain SAP solutions functions that determine benefit coverage, benefit costs, and benefit related salary information. This information is not readily available in the raw infotype tables (PA0167 and PA0168). For information on how to customize these two infotypes see “Function Calls in Custom ABAP Transforms” on page 371.

Infotype 0167 (Health)Calls custom ABAP transform PA0167 which uses a custom ABAP code snippet (stored in file PA0167_ABAPXFORM.aba). The custom ABAP code calls one ABAP function:• HR_BEN_GET_PLAN_COST - Calculates costs of a benefit on a

monthly basis. This includes employee and employer costs, imputed income, and benefit provider costs.


Infotype 0168 (Insurance)
Calls custom ABAP transform PA0168 which uses a custom ABAP code snippet (stored in file PA0168_ABAPXFORM.aba). The custom ABAP code calls these ABAP functions:• HR_BEN_GET_RULE_COVERAGE - Determines benefit coverage

rules as stored in SAP solutions table T74FC.• HR_BEN_GET_PLAN_SALARY - Determines annual salary used in

benefit value and cost calculations• HR_BEN_EVAL_AMOUNT - Returns Basic Coverage Amount.• HR_BEN_CALC_COVERAGE_AMOUNT - Returns insurance coverage

amounts.• HR_BEN_GET_PLAN_COST - Calculates costs of a benefit on a

monthly basis. This includes employee and employer costs, imputed income, and benefit provider costs.

Infotype 0008 (Pay History)The final step in the infotype loads is to call data flow DF_Infotype0008History_SAP.Uses HR_INFOTYPE_0008_PAY to create a salary history that stores previous salary, and salary one year ago. Data is loaded to HR_INFOTYPE_0008_HISTORY table.


Technical ImplementationEmployee Administration Section 9

The data flow finds previous salary, but only if the previous salary is different than the current salary (in case something besides salary may have changed on the PA0008 infotype). Then the data flow generates new effective dates for every actual salary change (uses Date Effective Transform).Note: Some countries do not use annual salary to track employee compensation. In this case, modify the data flow to look for changes in Wage Type rather than salary.

Employee Administration Section The employee administration subject area of this Rapid Mart allows you to analyze information about employee attributes, such as age, length of service, and annual salary, and about employee events, such as deadlines and other significant dates. Additional analyses of employee demographics (age, marital status, education, qualifications, etc.) is also available.The Rapid Mart calls the C_EmployeeAdministraton_Section_SAP work flow to load tables from SAP solutions. First, work flow WF_EmployeeAdministrationDims_SAP loads the dimensions required for this section. If these dimensions have already been loaded during the current job, the job will not reload them.The section uses work flow components to load dimension tables.

Work Flow Description Tables

C_BenefitArea_SAP Benefits Area descriptive attributes from T5UB3, T5UC3; load BENEFIT_AREA dimension

BENEFIT_AREA

C_BenefitPlan_SAP Date-effective information from T5UBG, T5UBU, T5UBA; load BENEFIT_PLAN dimension

BENEFIT_PLAN

C_BenefitProgramGroup_SAP Benefit Program grouping 1 and 2 descriptive attributes from T5UCT, T5UC9; load BENEFIT_PROGRAM_GROUP


C_BenefitTerminationRule_SAP Benefit Termination Rule descriptive attributes from T5UEU; load BENEFIT_TERMINATION_RULE


C_BusinessArea_SAP Dimensional component loading Business Area information from TGSB and TGSBT

BUSINESS_AREA

C_CertificateType_SAP Employee certification type descriptive attributes from T519T load CERTIFICATE_TYPE dimension

CERTIFICATE_TYPE


Technical ImplementationEmployee Administration Section9

C_CompanyCode_SAP Dimensional component loading Company Codes information from T001

COMPANY_CODE

C_ContributionRule_SAP Employee and Employer benefit contribution rule descriptive attributes from T74GE, T74GG; load CONTRIBUTION_RULE dimension

CONTRIBUTION_RULE

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_BAD, COST_CENTER_HIER_HZ, COST_CENTER_HIER_VR

C_CountryGroup_SAP Extracts and loads Country related data. Country specific data is extracted and loaded into Country Lookup table.


C_Currency_SAP Dimensional component loading currency abbreviations and texts from TCURT, TCURC

CURRENCY

C_EducationType_SAP Education type descriptive attributes from T518B load EDUCATION_TYPE dimension

EDUCATION_TYPE

C_EligibilityRule_SAP Benefit eligibility rule descriptive attributes from T5UCV; load ELIGIBILITY_RULE dimension

ELIGIBILITY_RULE

C_Employee_SAP HR master date-effective personal information from PA0002, PA0006 infotypes; load EMPLOYEE dimension; full reload only; date-effective records are merged as distinct union

EMPLOYEE

C_EmployeeGroup_SAP Employee Group descriptive information from T501T; load EMPLOYEE_GROUP dimension

EMPLOYEE_GROUP

C_EmployeeSubgroup_SAP Employee sub-group descriptive information from T503T; load EMPLOYEE_SUBGROUP dimension

EMPLOYEE_SUBGROUP

C_EthnicOrigin_SAP Ethnic Origin descriptive attributes from T505S; load ETHNIC_ORIGIN dimension

ETHNIC_ORIGIN

C_Gender_SAP Gender descriptive attributes from DD07T, 'GESCH' domain; load GENDER dimension

GENDER




C_HolidayCalendar_SAP THOC - Public holiday calendar; load HOLIDAY_CALENDAR dimension

HOLIDAY_CALENDAR, WORK_CALENDAR

C_IdentificationType_SAP Employee Identification type descriptive attributes from T509G; load IDENTIFICATION_TYPE dimension

IDENTIFICATION_TYPE

C_InsuranceCoverageRule_SAP Benefit insurance coverage rules and formulas from T74FB, T74FC, PA0168; load INSURANCE_COVERAGE_RULE dimension

INSURANCE_COVERAGE_RULE

C_InvestmentGroup_SAP Benefit-related employee investment group descriptive attributes from T5UCO; load INVESTMENT_GROUP dimension

INVESTMENT_GROUP

C_InvestmentPlan_SAP Benefit Investment plan descriptive attributes from T5UCN; load INVESTMENT_PLAN dimension

INVESTMENT_PLAN

C_Job_SAP Extracts and loads information related all Job codes set up in SAP System.

JOB

C_Language_SAP Language (key) descriptive attributes from T002T load LANGUAGE dimension

LANGUAGE

C_LengthOfServiceInterval_SAP Writes Length of Service Intervals (in months) from global variables $G_SERVICE_INTERVAL_01 through $G_SERVICE_INTERVAL_06 to database table SERVICE_INTERVAL_HR.

SERVICE_INTERVAL_HR

C_LineManagerHier_SAP Organization -> Position relationship from HRP1001 infotype; load LINE_MANAGER_HIER table

LINE_MANAGER_HIER

C_MaritalStatus_SAP Marital Status descriptive attributes from T502T; load MARITAL_STATUS dimension

MARITAL_STATUS

C_MilitaryStatus_SAP Military Status descriptive attributes from T505N; load MILITARY_STATUS dimension

MILITARY_STATUS

C_Nationality_SAP Nationality attributes from T005T (such as Nationality); load NATIONALITY dimension

NATIONALITY

C_OrganizationKey_SAP Organization structure (key) descriptive attributes from T527O; load ORGANIZATION_KEY dimension

ORGANIZATION_KEY

C_OrganizationUnit_SAP Extracts and loads all Organizational Units set up in SAP System.

ORGANIZATION_UNIT




C_OrganizationUnitHier_SAP Organization Unit hierarchy vertically and horizontally flattened from Infotype HRP1001 (DB Table); load ORGANIATION_UNIT_HIER_VR, ORGANIZATION_UNIT_HIER_HZ, and ORGANIZATION

ORGANIZATION_UNIT_HIER, ORGANIZATION_UNIT_HIER_HZ, ORGANIZATION_UNIT_HIER_VR

C_PayrollArea_SAP HR module Payroll Area descriptive attributes from T549T; load PAYROLL_AREA

PAYROLL_AREA

C_PayScaleArea_SAP Salary Pay scale area descriptive attributes from T510G; load PAY_SCALE_AREA

PAY_SCALE_AREA

C_PayScaleType_SAP Salary Pay scale type descriptive attributes from T510A; load PAY_SCALE_TYPE

PAY_SCALE_TYPE

C_PersonnelActionReason_SAP HR event (action) reasons descriptive attributes from T530T; load PERSONNEL_ACTION_REASON dimension


C_PersonnelActionStatus_SAP HR event (action) status (employment status) descriptive attributes from T529U; load PERSONNEL_ACTION_STATUS dimension


C_PersonnelActionType_SAP HR event (action) type descriptive attributes from T529T; load PERSONNEL_ACTION_TYPE dimension


C_PersonnelAdministrator_SAP Personnel Administrator details from T526; load PERSONNEL_ADMINISTRATOR


C_PersonnelArea_SAP Personnel Areas set up in SAP System from T500P; load PERSONNEL_AREA dimension

PERSONNEL_AREA

C_PersonnelDateType_SAP Date specification descriptive attributes for HR administration from T548Y, T548T; load PERSONNEL_DATE_TYPE dimension

PERSONNEL_DATE_TYPE

C_PersonnelSubArea_SAP Extracts and loads Personnel Sub Areas set up in SAP System.

PERSONNEL_SUBAREA

C_PersonnelTaskStatus_SAP Gender descriptive attributes from DD07T, 'BVMRK' domain; load PERSONNEL_TASK_STATUS dimension


C_PersonnelTaskType_SAP Type of deadlines associated with personnel events from T531, T531S; load PERSONNEL_TASK_TYPE

PERSONNEL_TASK_TYPE




C_Position_SAP Merged vacancy and position information from HRP1000, HRP1007; load POSITION dimension

POSITION

C_PositionHier_SAP Position hierarchy vertically and horizontally flattened from Infotype HRP1001 (DB Table); load POSITION_UNIT_HIER_VR, POSITION_UNIT_HIER_HZ, and POSITION_UNIT_HIER

POSITION_HIER, POSITION_HIER_HZ, POSITION_HIER_VR

C_Proficiency_SAP Employee proficiency descriptive attributes from T777Q; load PROFICIENCY dimension

PROFICIENCY

C_Qualification_SAP Employee qualification descriptive attributes from T574B; load QUALIFICATION dimension

QUALIFICATION

C_Religion_SAP Religion denomination descriptive attributes from T516T; load RELIGION dimension

RELIGION

C_ResidenceStatus_SAP Residence Status descriptive attributes from T505V; load RESIDENCE_STATUS dimension

RESIDENCE_STATUS

C_SalaryRange_SAP Pay scale group and level dimension table lists pay ranges (North America) T510N, T510F; load SALARY_RANGE dimension

SALARY_RANGE

C_SchoolType_SAP School (college, university, etc) descriptive attributes from T517T load SCHOOL_TYPE dimension

SCHOOL_TYPE

C_StudyBranch_SAP Studies branch descriptive attributes from T517X load STUDY_BRANCH dimension

STUDY_BRANCH

C_TimeDim_SAP Dimensional component loading generated time periods with SAP fiscal year periods and calendar parameters. By default Calendar dates from 1990.01.01 up to 2012.12.31 are

TIME_DIM, TIME_DIM_WEEKLY

C_TimeMgmtStatus_SAP Employee time management status descriptive attributes from T555V; load TIME_MANAGEMENT_STATUS dimension


C_UnitOfTime_SAP HR related unit of time descriptive attributes from T538A, T538T; load UNIT_OF_TIME

UNIT_OF_TIME

C_VestingRule_SAP Benefit Vesting rule descriptive attributes from T5UCR; load VESTING_RULE dimension

VESTING_RULE




After the loading dimensions, the component loads the EMPLOYEE_ADMINISTRATION_FACT. There is no delta (incremental) load for this section.EMPLOYEE_ADMINISTRATION_FACT combines data from the following SAP solutions infotypes:• PA0000 — Events • PA0001 — Organizational Assignment • PA0002 — Personal Data• PA0007 — Work Schedule • PA0008 — Basic Pay• PA0016 — Contract Elements• PA0019 — Date Monitoring• PA0022 — Education• PA0024 — Qualifications• PA0041 — Date Specifications• PA0077 — Additional Personal Data • PA0094 — Residency Status (North America) To load EMPLOYEE_ADMINISTRATION_FACT the component calls work flow C_EmployeeAdministrationFact_SAP. This in turn calls several data flows:• DF_MinDate0000_SAP - Selects Minimum Valid From Date for each

Person ID in InfoType PA0000. See “Minimum Date Driver” on page 382 for more details.

• DF_EmplAdmin0000_Stage_SAP - Selects valid records from PA0000 where the Subtype Code is Blank and Action Type is Hire, Re-Hire, Termination, or Retire. Loads data to table EMPLOYEE_ADMIN_0000_STAGE.

C_WageType_SAP Employee wage type date-effective records from T511, T512T; load WAGE_TYPE dimension

WAGE_TYPE

C_WorkContract_SAP Work (Employment) Contract descriptive attributes from T542T; load WORK_CONTRACT dimension

WORK_CONTRACT

C_WorkContractType_SAP Work (Employment) Contract Type descriptive attributes from T547S; load WORK_CONTRACT_TYPE dimension

WORK_CONTRACT_TYPE

C_WorkPermitType_SAP Work permit type descriptive attributes from T509I; load WORK_PERMIT_TYPE dimension

WORK_PERMIT_TYPE



Technical ImplementationLeave Entitlement Section 9

• DF_DimensionValidFromDate_SAP - Determines valid date ranges for dimensions used in the load. See “Dimension Valid Date Range Driver” on page 383 for more details.

• DF_EmplAdminValidFromDate_SAP - Merges effective dates from the various infotype tables, VALID_FROM_DATE_STAGE table and DATE_VALID_FROM_DIMENSION table. target is DATE_VALID_FROM_STAGE table. See “Fact Valid Date Range Driver” on page 384 for more details.

• DF_DateValidDriver_SAP - Populates DATE_VALID_DRIVER staging table to hold unique date ranges of all date-effective records being merged. This flow also creates beginning and ending dates for gaps in employee events. This data flow is used in multiple subject area loads within the HR Rapid Mart. See “Fact Valid Date Range Driver” on page 384 for more details.

• DF_EmployeeAdministrationFact_SAP - Performs an outer join between the various infotypes used in the load and DATE_VALID_DRIVER table to populate EMPLOYEE_ADMINISTRATION_FACT. See “Vertical and Horizontal Fact Organization” on page 389 for more details. Also performs lookup of surrogate keys for certain dimensions. See “Dimensions With Surrogate Keys” on page 379 for more details.

Leave Entitlement SectionThe leave entitlement subject area of this Rapid Mart allows you to analyze information about employee absences, such as vacations, sick leave, jury duty, maternity leave, etc. You can correlate accrued leave time vs. leave taken. You can also analyze the information by the organization, cost center, and position hierarchies.The Rapid Mart calls the C_LeaveEntitlement_Section_SAP work flow to load tables from SAP solutions. First, work flow WF_LeaveEntitlementDims_SAP loads the dimensions required for this section. If these dimensions have already been loaded during the current job, the job will not reload them.


Technical ImplementationLeave Entitlement Section9

The section uses work flow components to load dimension tables:



BUSINESS_AREA


COMPANY_CODE


CONTROLLING_AREA


COST_CENTER






EMPLOYEE


EMPLOYEE_GROUP


EMPLOYEE_SUBGROUP




JOB

C_LeaveDeduction_SAP Employee Leave Deductions details from Cluster PC1; load LEAVE_DEDUCTION

LEAVE_DEDUCTION

C_LeaveType_SAP Job leave type descriptive attributes from T533T; load LEAVE_TYPE

LEAVE_TYPE


LINE_MANAGER_HIER


Technical ImplementationLeave Entitlement Section 9

Leave Deduction DimensionOne of the dimensions used in Leave Entitlement (LEAVE_DEDUCTION) needs further explanation. it is extracted by component work flow C_LeaveDeduction_SAP listed above.


ORGANIZATION_KEY


ORGANIZATION_UNIT




PAYROLL_AREA




PERSONNEL_AREA


PERSONNEL_SUBAREA


POSITION






WORK_CONTRACT



Technical ImplementationLeave Entitlement Section9

The Leave Deduction dimension shows actual leave taken (vacation, sick time, maternity leave, etc.) while the Leave Entitlement Fact stored total entitled leave. Thus subtracting Leave Deduction values from Leave Entitlement values gives available leave remaining.Leave Deduction extracts data from SAP solutions Payroll Cluster table PCL1. The PCL1 table is organized into various “identification areas”. We use only one in the Rapid Mart:• PC - Personnel Calendar.Data from the PCL1 table is extracted with a custom ABAP transform (also called PCL1). The ABAP transform uses a custom written ABAP code snippet (stored in file PURLT.aba) to read data from the PCL1 cluster table. Data is extracted from PCL1 into SAP solutions internal structure PURLT (Leave Deduction), and the contents of this structure are used to populate the LEAVE_DEDUCTION table.

Leave Entitlement FactAfter the loading dimensions, the component loads the LEAVE_ENTITLEMENT_FACT. There is no delta (incremental) load for this section.LEAVE_ENTITLEMENT_FACT combines data from the following SAP solutions infotypes:• PA0000 — Events • PA0001 — Organizational Assignment • PA0005 — Leave EntitlementTo load LEAVE_ENTITLEMENT_FACT the component calls work flow C_LeaveEntitlementFact_SAP. This in turn calls several data flows:• DF_MinDate0000_SAP - Selects Minimum Valid From Date for each


• DF_DimensionValidFromDate_SAP - Determines valid date ranges for dimensions used in the load. See “Dimension Valid Date Range Driver” on page 383 for more details.

• DF_LeaveValidFromDate_SAP - Merges effective dates from the various infotype tables, VALID_FROM_DATE_STAGE table and DATE_VALID_FROM_DIMENSION table. target is DATE_VALID_FROM_STAGE table. See “Fact Valid Date Range Driver” on page 384 for more details.


Technical ImplementationBenefit Enrollment Section 9


• DF_LeaveEntitlementFact_SAP - Performs an outer join between the various infotypes used in the load and DATE_VALID_DRIVER table to populate LEAVE_ENTITLEMENT_FACT. See “Vertical and Horizontal Fact Organization” on page 389 for more details.The data from outer join query is split into 6 queries, one corresponding to each Leave Type in use. This is equivalent to using a Reverse Pivot Transform, taking values for upto 6 Leave Types in a single row of data and creating upto 6 rows of data (one for each Leave Type) in the target table.Also performs lookup of surrogate keys for certain dimensions. See “Dimensions With Surrogate Keys” on page 379 for more details.

• DF_LeaveEntitlmentWorkaysStage_SAP - Calculate number of working days during Start and End Leave period based on WORKING_CALENDAR dimension. Loads staging table LEAVE_ENTITLEMENT_STAGE

• DF_LeaveEntitlmentDeductStage_SAP - Calculate number of days/hours deducted between Start and End Leave period based on LEAVE_DEDUCTION dimension. Updates staging table LEAVE_ENTITLEMENT_STAGE

• DF_LeaveEntitlementUpdate_SAP - Updates LEAVE_ENTITLEMENT_FACT with calculated fields from LEAVE_ENTITLEMENT_STAGE

Benefit Enrollment SectionWith the benefit enrollment section of this Rapid Mart, you can analyze information about the enrollment in and usage of company benefits. You can use the SAP BusinessObjects HR Rapid Mart, version for SAP solutions to analyze benefit plan enrollment from two perspectives. First, you can analyze enrollment from the employee perspective, listing plans and coverage options by employee personnel number. Second, you can analyze enrollment from the plan perspective, listing point-in-time statistics by plan and showing enrollment, eligibility, and other measures such as average number of beneficiaries.


Technical ImplementationBenefit Enrollment Section9

The Rapid Mart calls the C_BenefitEnrollment_Section_SAP work flow to load tables from SAP solutions. First, work flow WF_BenefitEnrollmentDims_SAP loads the dimensions required for this section. If these dimensions have already been loaded during the current job, the job will not reload them.The section uses work flow components to load dimension tables


C_BenefitArea_SAP Benefits Area descriptive attributes from T5UB3, T5UC3; load BENEFIT_AREA dimension

BENEFIT_AREA

C_BenefitCostRule_SAP Benefit Cost rule details from T5UBH, T5UCH; load BENEFIT_COST_RULE dimension

BENEFIT_COST_RULE

C_BenefitPlan_SAP Date-effective information from T5UBG, T5UBU, T5UBA; load BENEFIT_PLAN dimension

BENEFIT_PLAN

C_BenefitProgramGroup_SAP Benefit Program grouping 1 and 2 descriptive attributes from T5UCT, T5UC9; load BENEFIT_PROGRAM_GROUP


C_BenefitSpendingAccount_SAP Benefit Spending account date-effective dimension from T5UBG; load BENEFIT_SPENDING_ACCOUNT dimension


C_BenefitTerminationRule_SAP Benefit Termination Rule descriptive attributes from T5UEU; load BENEFIT_TERMINATION_RULE



BUSINESS_AREA


COMPANY_CODE

C_ContributionRule_SAP Employee and Employer benefit contribution rule descriptive attributes from T74GE, T74GG; load CONTRIBUTION_RULE dimension

CONTRIBUTION_RULE


CONTROLLING_AREA


COST_CENTER








CURRENCY

C_DependentCoverage_SAP Benefit dependent coverage descriptive attributes from T5UBF, T5UCF; load DEPENDENT_COVERAGE dimension

DEPENDENT_COVERAGE

C_EligibilityRule_SAP Benefit eligibility rule descriptive attributes from T5UCV; load ELIGIBILITY_RULE dimension

ELIGIBILITY_RULE


EMPLOYEE


EMPLOYEE_GROUP


EMPLOYEE_SUBGROUP

C_EnrollmentType_SAP Benefit program enrollment type descriptive attributes from DD07T, 'BEN_ENRTYP' domain; load ENROLLMENT_TYPE dimension

ENROLLMENT_TYPE

C_HealthPlan_SAP Benefits - Health Option descriptive attributes from T5UCE; load HEALTH_PLAN dimension

HEALTH_PLAN



C_InsuranceCoverageGroup_SAP Insurance coverage grouping descriptive attributes from T74G2; load INSURANCE_COVERAGE_GROUP dimension


C_InsuranceCoverageRule_SAP Benefit insurance coverage rules and formulas from T74FB, T74FC, PA0168; load INSURANCE_COVERAGE_RULE dimension


C_InsuranceOption_SAP Benefits - Insurance Option date-effective attributes from T74FA, T74GA; load INSURANCE_OPTION dimension

INSURANCE_OPTION




C_InvestmentGroup_SAP Benefit-related employee investment group descriptive attributes from T5UCO; load INVESTMENT_GROUP dimension

INVESTMENT_GROUP

C_InvestmentPlan_SAP Benefit Investment plan descriptive attributes from T5UCN; load INVESTMENT_PLAN dimension

INVESTMENT_PLAN


JOB

C_LeaveDeduction_SAP Employee Leave Deductions details from Cluster PC1; load LEAVE_DEDUCTION

LEAVE_DEDUCTION


LINE_MANAGER_HIER


ORGANIZATION_KEY


ORGANIZATION_UNIT




PAYROLL_AREA




PERSONNEL_AREA


PERSONNEL_SUBAREA


POSITION






After the loading dimensions, the component loads the BENEFIT_ENROLLMENT_FACT and BENEFIT_ENROLL_SUMMARY_FACT. There is no delta (incremental) load for this section.BENEFIT_ENROLLMENT_FACT and BENEFIT_ENROLL_SUMMARY_FACT combine data from the following SAP solutions infotypes:• PA0001 — Organizational Assignment • PA0167 — Health plans• PA0168 — Insurance plans• PA0169 — Savings plans• PA0170 — Spending accounts (United States)• PA0171 — General benefits data• PA0236 — Credit plansTo load the two Benefit Enrollment Fact tables, the component calls work flow C_BenefitEnrollmentFact_SAP. This in turn calls several work flows and data flows:• DF_DimensionValidFromDate_SAP - Determines valid date ranges for

dimensions used in the load. See “Dimension Valid Date Range Driver” on page 383 for more details.

• WF_Benefit0167Stage_SAP -Uses these dataflows to load staging table BENEFIT_ENROLL_0167_STAGE.• DF_MinDate0167_SAP - Selects Minimum Valid From Date for each




C_VestingRule_SAP Benefit Vesting rule descriptive attributes from T5UCR; load VESTING_RULE dimension

VESTING_RULE


WORK_CONTRACT




• DF_Benefit0167ValidFromDate_SAP - Merges effective dates from infotypes PA0167, PA0001, PA0171, VALID_FROM_DATE_STAGE table and DATE_VALID_FROM_DIMENSION table. target is DATE_VALID_FROM_STAGE table. See “Fact Valid Date Range Driver” on page 384 for more details.


• DF_BenefitEnroll0167Stage_SAP - Outer joins DATE_VALID_DRIVER and infotypes PA0001, PA0167, and PA0171 to populate staging table BENEFIT_ENROLL_0167_STAGE

• WF_Benefit0168Stage_SAP - Uses similar dataflows as WF_Benefit0167Stage_SAP to load staging table BENEFIT_ENROLL_0168_STAGE.




• DF_BenefitEnrollmentFact_SAP - Merges data from the 5 stage tables (BENEFIT_ENROLL_0167 _STAGE - BENEFIT_ENROLL_0236_STAGE) to populate BENEFIT_ENROLLMENT_FACT. See “Vertical and Horizontal Fact Organization” on page 389 for more details. Also performs lookup of surrogate keys for certain dimensions. See “Dimensions With Surrogate Keys” on page 379 for more details.

• DF_BenefitEnrollSummaryFact_SAP - groups data in BENEFIT_ENROLLMENT_FACT to produce BENEFIT_ENROLL_SUMMARY_FACT. Grouping is by:• Benefit Area• Benefit Plan• Program Grouping 1• Program Grouping 2


Technical ImplementationEmployee Wage Section 9

• Monetary Currency• Company Code• Cost Center• Controlling Area• Organization Unit• Personnel Area• Personnel Sub-Area

Employee Wage SectionThe employee wage section lets you correlate employee wage information (wage types, pay scales, etc.) with certain organizational aspects (position, organization, job, etc.). Payment amounts for each Wage Type are the key measure in this section. The key difference between the Employee Wage Section and the Payroll Section is that Employee Wages shows history of the gross wage or salary amounts from the perspective of your organization’s pay and deduction structures and internal set-up. The Payroll shows the actual payments generated from this internal setup. It records the actual payments made each payday to your employees. It includes information on deductions for taxes, various benefits, etc. The Payroll perspective is for external consumption by various government agencies as well as the employees themselves.From a technical perspective, Employee Wage is based on infotypes, while Payroll is based on the payroll cluster tables in SAP solutions.The Rapid Mart calls the C_EmployeeWage_Section_SAP work flow to load tables from SAP solutions. First, work flow WF_EmployeeWageDims_SAP loads the dimensions required for this section. If these dimensions have already been loaded during the current job, the job will not reload them.The section uses work flow components to load dimension tables:



BUSINESS_AREA


COMPANY_CODE


CONTROLLING_AREA


Technical ImplementationEmployee Wage Section9


COST_CENTER






CURRENCY


EMPLOYEE


EMPLOYEE_GROUP


EMPLOYEE_SUBGROUP


JOB


LINE_MANAGER_HIER


ORGANIZATION_KEY


ORGANIZATION_UNIT




PAYROLL_AREA



Technical ImplementationEmployee Wage Section 9

After the loading dimensions, the component loads the EMPLOYEE_WAGE_FACT. There is no delta (incremental) load for this section.EMPLOYEE_WAGE_FACT combines data from the following SAP solutions infotypes:

C_PayScaleArea_SAP Salary Pay scale area descriptive attributes from T510G; load PAY_SCALE_AREA

PAY_SCALE_AREA

C_PayScaleType_SAP Salary Pay scale type descriptive attributes from T510A; load PAY_SCALE_TYPE

PAY_SCALE_TYPE




PERSONNEL_AREA


PERSONNEL_SUBAREA


POSITION



C_SalaryRange_SAP Pay scale group and level dimension table lists pay ranges (North America) T510N, T510F; load SALARY_RANGE dimension

SALARY_RANGE




UNIT_OF_TIME


WAGE_TYPE


WORK_CONTRACT



Technical ImplementationEmployee Wage Section9

• PA0001 — Organizational Assignment • PA0008 — Basic Pay• PA0014 — Recurring benefits and deductions• PA0015 — Additional paymentsTo load EMPLOYEE_WAGE_FACT the component calls work flow C_EmployeeWageFact_SAP. This in turn calls several work flows and data flows:• DF_DimensionValidFromDate_SAP - Determines valid date ranges for

dimensions used in the load. See “Dimension Valid Date Range Driver” on page 383 for more details.

• WF_EmplWage0008Stage_SAP - Uses these dataflows to load staging table EMPLOYEE_WAGE_0008_STAGE.• DF_MinDate0008_SAP - Selects Minimum Valid From Date for each


• DF_EmplWage0008ValidFromDate_SAP - Merges effective dates from infotypes PA0008, VALID_FROM_DATE_STAGE table and DATE_VALID_FROM_DIMENSION table. target is DATE_VALID_FROM_STAGE table. See “Fact Valid Date Range Driver” on page 384 for more details.


• DF_EmplWage0008Stage_SAP - Outer joins DATE_VALID_DRIVER and infotypes PA0001, and PA0008 to populate staging table EMPLOYEE_WAGE_0008_STAGE

• WF_EmplWage0014Stage_SAP - Uses similar dataflows as WF_EmplWage0008Stage_SAP to load staging table EMPLOYEE_WAGE_0014_STAGE.

• WF_EmplWage0015Stage_SAP - Uses similar dataflows as WF_EmplWage0008Stage_SAP to load staging table EMPLOYEE_WAGE_0015_STAGE.

• DF_EmployeeWageFact_SAP - Merges data from the 3 stage tables (EMPLOYEE_WAGE_0008_STAGE - EMPLOYEE_WAGE_0015_STAGE) to populate BENEFIT_ENROLLMENT_FACT. See “Vertical and Horizontal Fact Organization” on page 389 for more details.


Technical ImplementationPayroll Section 9

The data from EMPLOYEE_WAGE_0008_STAGE is split into 20 queries, one corresponding to each Wage Type in use. This is equivalent to using a Reverse Pivot Transform, taking values for upto 20 Wage Types in a single row of data and creating upto 20 rows of data (one for each Wage Type) in the target table.Also performs lookup of surrogate keys for certain dimensions. See “Dimensions With Surrogate Keys” on page 379 for more details.

Payroll SectionUsing the employee payroll section of this Rapid Mart, you can analyze information about different wage types. Each payment or deduction in a paycheck is a wage type. Typically, a company’s payroll process calculates remuneration based on wage types and a country-specific set of rules. Companies cumulate wage types that represent individual payments or deductions to determine gross pay. Payment wage types include basic pay, bonuses, special pay, and so forth. Net pay calculations handle country-specific adjustments to gross pay. Adjustments and deductions may be voluntary, such as charitable contributions, or statutory, such as taxes. Finally, the payroll process combines results of previous payroll runs with the current results to get cumulative gross and net pay amounts.Note: The Payroll section is designed to meet U.S. payroll requirements. Customization of the Rapid Mart is required for other countries. Consult the section “Payroll Customization” on page 354 for more details.The key difference between the Employee Wage Section and the Payroll Section is that Employee Wages shows history of the gross wage or salary amounts from the perspective of your organization’s pay and deduction structures and internal set-up. The Payroll shows the actual payments generated from this internal setup. It records the actual payments made each payday to your employees. It includes information on deductions for taxes, various benefits, etc. The Payroll perspective is for external consumption by various government agencies as well as the employees themselves.From a technical perspective, Employee Wage is based on infotypes, while Payroll is based on the payroll cluster tables in SAP solutions.The Rapid Mart calls the C_Payroll_Section_SAP work flow to load tables from SAP solutions.


Technical ImplementationPayroll Section9

First, work flow WF_PayrollDims_SAP loads the dimensions required for this section. If these dimensions have already been loaded during the current job, the job will not reload them.



BUSINESS_AREA


COMPANY_CODE


CONTROLLING_AREA


COST_CENTER






CURRENCY


EMPLOYEE


EMPLOYEE_GROUP


EMPLOYEE_SUBGROUP


JOB


LINE_MANAGER_HIER


ORGANIZATION_KEY




ORGANIZATION_UNIT




PAYROLL_AREA

C_PayrollCumulationType_SAP Descriptive attributes for calendar-associated accumulation types from T54C2, T54CT; load PAYROLL_CUMULATION_TYPE dimension


C_PayrollPeriod_SAP Payroll Period details from T549Q; load PAYROLL_PERIOD

PAYROLL_PERIOD

C_PayrollPeriodParam_SAP Payroll Period Parameter descriptive attributes from T549N; load PAYROLL_PERIOD_PARAMETER

PAYROLL_PERIOD_PARAMETER

C_PayrollStatus_SAP Load PAYROLL_STATUS dimension (DD07T domain 'SRTZA') - descriptive attributes for Payroll Indicator for most recent update of results record

PAYROLL_STATUS

C_PayrollType_SAP Load PAYROLL_TYPE dimension (DD07T domain 'PAYTY') - descriptive attributes for Payroll type

PAYROLL_TYPE




PERSONNEL_AREA


PERSONNEL_SUBAREA


POSITION





Technical ImplementationPayroll Section9

After the loading dimensions, the component loads the PAYROLL_FACT & PAYROLL_SUMMARY_FACT tables. The Payroll Cluster table (PCL2) is the source for both payroll fact tables. The PCL2 table is organized into various “identification areas”. We use two in the Rapid Mart:• CU - Cluster directory. Used to populate structure PC261.• RU - Payroll results (USA). Used to populate structures PC207 and

PC22Y.As PCL2 is a clustered table we use 3 custom ABAP transforms to read the data in the table. these are • PC261 - Reads the Cluster Directory• PC207 - Reads the US Payroll results (detailed)• PC22Y - Reads the US Payroll results (summary)The PCL2 table carries a change date field (PCL2.AEDTM). This change date is used in both the first (initial) and delta (incremental) loads. All records where PCL2.AEDTM is between global variables $G_SDATE and $G_EDATE are extracted in both the first and delta loads. In a first load, the window between these two global variables typically covers several years of past payroll data. Thus, the first load will take much longer than the delta.In a delta load the window is much smaller, typically a single payroll cycle (weekly, biweekly, monthly, etc.) Thus, the amount of data is much smaller and the delta load takes less time than the first load.




UNIT_OF_TIME


WAGE_TYPE


WORK_CONTRACT




Initial (First) LoadIf global variable $G_LOAD_TYPE is equal to 'FIRST' the Data Services job performs the initial payroll load with these steps:1. DF_PayrollPC261Stage_SAP - Loads PAYROLL_PC261_STAGE table.

This data flow uses a custom ABAP transform (file name PC261.aba). The custom ABAP extracts data from clustered payroll table PCL2 into SAP solutions internal structure PC261 - Cluster Directory (For Export and Import of Payroll Results). The contents of the structure are then loaded to the PAYROLL_PC261_STAGE table. All data in target tables is deleted (truncated) before new data is inserted.

2. DF_PayrollFact_SAP - Loads PAYROLL_FACT table.This data flow uses a custom ABAP transform (file name PC07.aba). The custom ABAP extracts data from clustered payroll table PCL2 into SAP solutions internal structure PC207 - Payroll Results: Results Table (for U.S.). The contents of the structure are then inner joined to the PAYROLL_PC261_STAGE table and loaded to the PAYROLL_FACT table. All data in target tables is deleted (truncated) before new data is inserted.Note: For performance optimization, consider staging results of R3_PayrollPC207 before joining them with PAYROLL_PC261_STAGE (using Data Transfer or splitting this data flow in 2 dataflows and adding a staging table).Note: Currency ID (CURR_ID) is always NULL when returned from the Payroll Cluster (PC207). We set the default value is "USD" (U.S. dollar) in TimeStampQuery. If you are customizing the Rapid Mart for a country other than U.S. change the default value in TimeStampQuery.

3. DF_PayrollSummaryFact_SAP - Loads PAYROLL_SUMMARY_FACT table.This data flow uses a custom ABAP transform (file name PC22Y.aba). The custom ABAP extracts data from clustered payroll table PCL2 into SAP solutions internal structure PC22Y - Payroll Results: Cumulated Results Table (for U.S.). The contents of the structure are then inner joined to the PAYROLL_PC261_STAGE table and loaded to the PAYROLL_SUMMARY_FACT table. All data in target tables is deleted (truncated) before new data is inserted.


Technical ImplementationOptimization Techniques9

Note: For performance optimization, consider staging results of R3_PayrollPC22Y before joining them with PAYROLL_PC261_STAGE (using Data Transfer or splitting this data flow in 2 dataflows and adding a staging table).Note: Currency ID (CURR_ID) is always NULL when returned from the Payroll Cluster (PC22Y). We set the default value is "USD" (U.S. dollar) in TimeStampQuery. If you are customizing the Rapid Mart for a country other than U.S. change the default value in TimeStampQuery.

Incremental (Delta) LoadIf global variable $G_LOAD_TYPE is not equal to 'FIRST' the Data Services job performs the incremental payroll load with these steps:1. DF_PayrollPC261StageDelta_SAP - Loads PAYROLL_PC261_STAGE

table. Performs similar steps to DF_PayrollPC261Stage_SAP in the initial load. However, data is not truncated in the target tables, and the Table Comparison transform is used to update or insert records in the target table.

2. DF_PayrollFactDelta_SAP - Loads PAYROLL_FACT table.Performs similar steps to DF_PayrollFact_SAP in the initial load. However, data is not truncated in the target tables, and the Table Comparison transform is used to update or insert records in the target table.

3. DF_PayrollSummaryFactDelta_SAP - Loads PAYROLL_SUMMARY_FACT table.Performs similar steps to DF_PayrollSummaryFact_SAP in the initial load. However, data is not truncated in the target tables, and the Table Comparison transform is used to update or insert records in the target table.

Optimization TechniquesWithin Data Services there are several optimization techniques available. Some of these are used extensively in the HR Rapid Mart. They are described below


Technical ImplementationOptimization Techniques 9

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 PartitionsSummary tables in SAP solutions present a particular challenge in terms of a incremental (or delta) load. They often do not carry a “date of last change” field in the source table. In most cases source table granularity is at the Fiscal Period / Fiscal Year level.Data Services performs incremental loads on these tables by fiscal year.Data for a range of fiscal years is deleted from the target tables before each incremental load. The range is determined by the fiscal years associated with the global variables $G_SDATE and $G_EDATE.Then the same range of years is re-loaded from the SAP solutions source tables.Deleting by fiscal year without partitions is resource intensive, and can take a very long time. To facilitate these deletions we have partitioned the target tables by fiscal year. Partitions based on fiscal year can be dropped and re-added to the table very quickly. Thus the delete of a range of fiscal years is much faster. with partitionsEach of the databases supported (Oracle, SQL-Server, DB2) handles partition logic differently. Separate cases for each have been coded into the Data Services jobs. Use of partitions is transparent to the end-user.

Note: We do not use partition logic for Teradata. Terdata optimizes the delete function in SQL so that partitions are not needed.Note: In a DB2 target environment, proper database tuning is required to handle detaching partitions properly. If not tuned, the database returns control to the Data Services job before the partition is physically detached. This will cause the job to fail.To prevent this, we query the DB2 metadata table:• SYSIBM.SYSDATAPARTITIONSin a “while” loop, upto 100 times, with a 10 second sleep in between each query. When this table shows that the partitions are truly detached, the job proceeds. However, in a poorly tuned system even this may not be enough time. Proper tuning is essential.



Tables and Rapid Marts that use partition logic are:

Data Transfer TransformWithin 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.

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



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::

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

Key TransformsCircled in RED.



• Make sure the columns in the “order by” clause appear in the same sequence as the non-pivot columns in the Reverse-Pivot.

Within the Reverse-Pivot:• “Input Data is Grouped” is checked• Make sure the non-pivot columns appear in the same sequence as the

“order by” clause of the Ordering Query

Hierarchy OptimizationsWe also use optimizations for Hierarchy Flattening Transforms. Hierarchy Flattening Transforms are set to run as “Separate Process” (in the properties window). The data flow that calls the Hierarchy Flattening Transform is set to 2 degrees of parallelism.This degree of parallelism is tied to number of CPUs on your server, and can require manual tuning. Refer to Data Services technical manuals for more details on Distributed Data Flows.Hierarchy flattening transforms are resource intensive. To prevent overtaxing system resources on the Data Services job server you can split the Vertical and Horizontal hierarchy flattening into two separate workflows. The diagrams below show an example:Before Split (Single Data Flow):



After Split 1 of 2 Data Flows (Horizontal):

After Split 2 of 2 Data Flows (Vertical):


Technical ImplementationDealing with NULL values9

The 2 Split Data Flows in Context.

Dealing with NULL valuesAs the first step in data cleansing, the SAP BusinessObjects HR 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.


Technical ImplementationDealing with NULL values 9

Dimensions whose corresponding foreign keys in the fact tables can have value NULL are loaded with an additional ‘dummy’ row to represent NULL. The value of $G_DEFAULT_NUMBER global variable gets inserted into each dimension primary key column.


Technical ImplementationFact Table Stored Procedures9
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.


Technical ImplementationFiscal Periods & Time Dim Load 9

Fiscal Periods & Time Dim LoadThese two dimensions use a text file named dates.dat to define the range of dates you load. The file must be located in the Working Directory you defined in your R/3 Data Store


Technical ImplementationFiscal Periods & Time Dim Load9

By default, the file contains all dates from 01-Jan-1990 through 31-Dec.-2012 in “YYYYMMDD” format

You can easily change the contents of dates.dat to include a different date range that covers your specific needs.


Documentation References

chapter

Documentation ReferencesData Services Documentation References10

The SAP BusinessObjects HR Rapid Mart XI 3.2 for SAP solutions User Guide requires familiarity with SAP BusinessObjects Enterprise and Data Services applications. Documentation for both applications can be found in http://help.sap.com.

Data Services Documentation ReferencesFrom the SAP help portal, Data Services documentation is accessed via SAP BusinessObjects -> All Products -> Data Services -> SAP BusinessObjects XI 3.2 <or higher version> path.Installing Data Services:

• Data Services Installation Guide• Data Services Getting Started Guide

Configuring Data Services for SAP solutions and security considerations:• Data Services Supplement for SAP

Extending/customizing Rapid Marts ETL:• Data Services Tutorial• Data Services Designer Guide• Data Services Reference Guide• Data Services Advanced Development Guide• Data Services Performance Optimization Guide

BusinessObjects Enterprise Documentation References

From the SAP help portal, BusinessObjects Enterprise documentation is accessed via SAP BusinessObjects -> All Products -> BusinessObjects Enterprise -> BusinessObjects XI Release 2 <or higher version> path.Installing BusinessObjects Enterprise:

• Installation GuideConfiguring BusinessObjects Enterprise and security considerations:

• Administration Guide• Deployment and Configuration Guide


Documentation ReferencesBusinessObjects Enterprise Documentation References 10

• Administrator’s Reference Guide• Recommended Settings Guide• Import Wizard Guide• InfoView User Guide

Extending/customizing Rapid Marts Reporting Content:• Designer’s Guide (BusinessObjects -> All Products -> Universe

Designer path)• Building queries with Web Intelligence (BusinessObjects -> All

Products -> Web Intelligence path)• Using Functions, Formulas and Calculations in Web Intelligence

(BusinessObjects -> All Products -> Web Intelligence path)


Documentation ReferencesBusinessObjects Enterprise Documentation References10


Rapid Mart Data Schema

appendix

Appendix ATable Summary

Rapid Mart Data Schema

This appendix provides detailed information about the tables and views in the SAP BusinessObjects Human ResourcesRapid Mart XI 3.2, version for SAP solutions. This information applies to an Oracle target datastore.

Auxiliary Tables

● AW_FIRST_RUN_DATE

● AW_JOBEXECUTION

● AW_LOOKUP_INDEX

● DATE_VALID_DRIVER

● DATE_VALID_FROM_DIMENSION

Dimension Tables

● BENEFIT_AREA

● BENEFIT_COST_RULE

● BENEFIT_PLAN

● BENEFIT_PROGRAM_GROUP

● BENEFIT_SPENDING_ACCOUNT

● BENEFIT_TERMINATION_RULE

● BUSINESS_AREA

● CERTIFICATE_TYPE

● COMPANY_CODE

● CONTRIBUTION_RULE

● CONTROLLING_AREA

● COST_CENTER

● COST_CENTER_HIER

● COST_CENTER_HIER_HZ

● COST_CENTER_HIER_VR

● COUNTRY_GROUP

● COUNTRY_GROUP_STATUS

● CURRENCY

● DEPENDENT_COVERAGE

● EDUCATION_TYPE

● ELIGIBILITY_RULE

● EMPLOYEE

● EMPLOYEE_GROUP

● EMPLOYEE_SUBGROUP

● ENROLLMENT_TYPE

● ETHNIC_ORIGIN

● GENDER

● HEALTH_PLAN

1Rapid Mart Data Schema

Appendix ATable Summary● HOLIDAY_CALENDAR

● IDENTIFICATION_TYPE

● INSURANCE_COVERAGE_GROUP

● INSURANCE_COVERAGE_RULE

● INSURANCE_OPTION

● INVESTMENT_GROUP

● INVESTMENT_PLAN

● JOB

● LANGUAGE

● LEAVE_DEDUCTION

● LEAVE_TYPE

● LINE_MANAGER_HIER

● MARITAL_STATUS

● MILITARY_STATUS

● NATIONALITY

● ORGANIZATION_KEY

● ORGANIZATION_UNIT

● ORGANIZATION_UNIT_HIER

● ORGANIZATION_UNIT_HIER_HZ

● ORGANIZATION_UNIT_HIER_VR

● PAYROLL_AREA

● PAYROLL_CUMULATION_TYPE

● PAYROLL_PERIOD

● PAYROLL_PERIOD_PARAMETER

● PAYROLL_STATUS

● PAYROLL_TYPE

● PAY_SCALE_AREA

● PAY_SCALE_TYPE

● PERSONNEL_ACTION_REASON

● PERSONNEL_ACTION_STATUS

● PERSONNEL_ACTION_TYPE

● PERSONNEL_ADMINISTRATOR

● PERSONNEL_AREA

● PERSONNEL_DATE_TYPE

● PERSONNEL_SUBAREA

● PERSONNEL_TASK_STATUS

● PERSONNEL_TASK_TYPE

● POSITION

● POSITION_HIER

● POSITION_HIER_HZ

● POSITION_HIER_VR

● PROFICIENCY

● QUALIFICATION

● RELIGION

● RESIDENCE_STATUS


Appendix ATable Summary● SALARY_RANGE

● SCHOOL_TYPE

● SERVICE_INTERVAL_HR

● STUDY_BRANCH

● TIME_DIM

● TIME_DIM_WEEKLY

● TIME_MANAGEMENT_STATUS

● UNIT_OF_TIME

● VESTING_RULE

● WAGE_TYPE

● WORK_CALENDAR

● WORK_CONTRACT

● WORK_CONTRACT_TYPE

● WORK_PERMIT_TYPE

Fact Tables

● BENEFIT_ENROLLMENT_FACT

● BENEFIT_ENROLL_SUMMARY_FACT

● EMPLOYEE_ADMINISTRATION_FACT

● EMPLOYEE_WAGE_FACT

● LEAVE_ENTITLEMENT_FACT

● PAYROLL_FACT

● PAYROLL_SUMMARY_FACT

Infotype Master Tables

● HR_INFOTYPE_0000_ACTION

● HR_INFOTYPE_0001_ASSIGNMENT

● HR_INFOTYPE_0002_PERSONAL

● HR_INFOTYPE_0005_LEAVE

● HR_INFOTYPE_0006_ADDRESS

● HR_INFOTYPE_0007_WORKTIME

● HR_INFOTYPE_0008_HISTORY

● HR_INFOTYPE_0008_PAY

● HR_INFOTYPE_0014_DEDUCTION

● HR_INFOTYPE_0015_PAYMENT

● HR_INFOTYPE_0016_CONTRACT

● HR_INFOTYPE_0019_DATES

● HR_INFOTYPE_0021_DEPENDENT

● HR_INFOTYPE_0022_EDUCATION

● HR_INFOTYPE_0024_QUALIFICATION

● HR_INFOTYPE_0041_SPEC

● HR_INFOTYPE_0077_PERSONAL

● HR_INFOTYPE_0094_RESIDENCE


Appendix ATable Summary● HR_INFOTYPE_0167_HEALTH

● HR_INFOTYPE_0168_INSURANCE

● HR_INFOTYPE_0169_SAVINGS

● HR_INFOTYPE_0170_FLEX

● HR_INFOTYPE_0171_BENEFIT

● HR_INFOTYPE_0236_CREDIT

● HR_INFOTYPE_1000_DBTABLE



Staging Tables

● BENEFIT_ENROLL_0167_STAGE





● BENEFIT_FSA_STAGE

● BENEFIT_PLAN_STAGE

● DATE_VALID_FROM_STAGE

● EMPLOYEE_ADMIN_0000_STAGE

● EMPLOYEE_WAGE_0008_STAGE



● JOB_STAGE

● LEAVE_ENTITLEMENT_STAGE

● PAYROLL_PC261_STAGE

● VALID_FROM_DATE_STAGE

Validation Tables

● COST_CENTER_HIER_BAD

● HR_INFOTYPE_VALIDATION


AppendixTable 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 Name Key Column Desc ColumnDatatype

DtypeLength Precision Scale Is

Nullable

1 JOB_END_DATE $G_EDATE global variable setting at the timeof the "First" or "Delta" run. DATETIME 24 0 0 yes

2 JOB_LOAD_TYPE PK Will be FIRST or DELTA NVARCSTR 10 0 0 no

3 JOB_NAME PK Name of the Rapid Mart Load Job. NVARCSTR 100 0 0 no

4 JOB_START_DATE $G_SDATE global variable setting at the timeof the "First" or "Delta" run. DATETIME 24 0 0 yes

5 LOAD_DATE Date and time when the record was loaded intoRapid Mart DATETIME 24 0 0 yes

6 LOAD_TIME Time when the record was loaded into theRapidMart (string format HH24:MI:SS) NVARCSTR 8 0 0 yes

AW_JOBEXECUTION

Job Execution Status table



Nullable

1 EXTRACTHIGH End Date NVARCSTR 10 0 0 yes

2 EXTRACTLOW Start Date NVARCSTR 10 0 0 yes


4 NAME PK Job Name NVARCSTR 64 0 0 no

5 STATUS Job Status NVARCSTR 12 0 0 yes



AW_LOOKUP_INDEX

Auxilary table to store index information



Nullable

1 ADDTNL_TXT Notes NVARCSTR 64 0 0 yes

2 COLUMN_NAME_01 Index column 1 NVARCSTR 64 0 0 yes



5 INDEX_NAME Index Name NVARCSTR 64 0 0 yes

6 LOAD_DATE Load date in Rapid mart DATETIME 24 0 0 yes

7 LOAD_TIME Load time in Rapid mart NVARCSTR 8 0 0 yes

8 TBL_NAME Table name the index belong to NVARCSTR 64 0 0 yes



BENEFIT_AREA

Benefits Area descriptive attributes from T5UB3, T5UC3; load BENEFIT_AREA dimension



Nullable

1 BENFT_AREA_DESCR T5UC3.LTEXT Text (20 characters) NVARCSTR 20 0 0 yes

2 BENFT_AREA_FULL_NAME

Concatenated: T5UB3.BAREA Benefit area +T5UC3.LTEXT Text (20 characters) NVARCSTR 30 0 0 yes

3 BENFT_AREA_ID PK T5UB3.BAREA Benefit area NVARCSTR 2 0 0 no

4 COUNTRY_GRP_DESCR T005T.LTEXT Country Group Descr (lookup) NVARCSTR 25 0 0 yes

5 COUNTRY_GRP_ID T5UB3.MOLGA Country grouping NVARCSTR 2 0 0 yes

6 CURR_ID T5UB3.CURRE Currency key for benefits NVARCSTR 5 0 0 yes

7 LOAD_DATE Date and Time loaded into Rapid mart DATETIME 24 0 9 yes

8 LOAD_TIME Time Loaded into Rapid mart NVARCSTR 8 0 0 yes



BENEFIT_COST_RULE

Benefit Cost rule details from T5UBH, T5UBI, T5UCH; load BENEFIT_COST_RULE dimension



Nullable

1 AGE_GRP_ID PK T5UBI.AGEGR Benefit age group VARCSTR 4 0 0 no

2 AGE_RELEVNT_FLAG T5UBH.AGEIN Benefit Age group relevanceindicator INTEGER 4 0 0 yes

3 AMT_COST_BASE_INSURANCE

T5UBI.INCRE Benefit base unit for insurancecost calculation DECIMAL 48 13 2 yes

4 AMT_COST_EMPLEE T5UBI.EECST - Benefit Employee CostAmount DECIMAL 48 13 2 yes

5 AMT_COST_EMPLEE_POSTTAX

T5UBI.PTCST Benefits Additional EmployeePost-Tax Costs DECIMAL 48 13 2 yes

6 AMT_COST_EMPLER T5UBI.ERCST Benefit Employer Cost/CreditAmount DECIMAL 48 13 2 yes

7 AMT_COST_PROVIDER T5UBI.ACCST Benefit Provider Cost Amount DECIMAL 48 13 2 yes

8 AMT_IMPUTED_INCOME T5UBI.IMINC Benefits Imputed Income DECIMAL 48 13 2 yes

9 AMT_STEP_LIMIT PK T5UBI.LIMITBenefit insurance cost rule variantlimit DECIMAL 48 15 0 no

10 BENFT_AGE_GRP_DESCR

Lookup T5UCL.LTEXT lookup on Benefit agedgroup descritpion VARCSTR 20 0 0 yes

11 BENFT_AREA_DESCR T5UC3.LTEXT - lookup on Benefit Areadescription VARCSTR 30 0 0 yes

12 BENFT_AREA_ID PK T5UCH.BAREA Benefit area VARCSTR 2 0 0 no

13 BENFT_PLAN_DESCR Lookup PA0167.BOPTI description in T5UCA -Benefits Plan text VARCSTR 30 0 0 yes

14 BENFT_PLAN_ID PK T5UCH.BPLAN Benefit plan VARCSTR 4 0 0 no

15 CALCULATN_PERIOD_DESCR

DD07T.DDTEXT - Calculation period Desclookup, domain PFREQ VARCSTR 40 0 0 yes

16 CALCULATN_PERIOD_ID Benefit period for calculations VARCSTR 2 0 0 yes



17 COST_GRP_FULL_NAME

Lookup T5UC5.LTEXT lookup on Cost groupdescritpion VARCSTR 30 0 0 yes

18 COST_GRP_ID PK T5UBI.CSTV1Benefit cost grouping VARCSTR 4 0 0 no

19 COST_RULE_FULL_NAME

Concatenated: T5UCH.BCOST Benefit costrule variant + T5UCH.LTEXT Text (30Characters)

VARCSTR 40 0 0 yes

20 COST_RULE_ID PK T5UCH.BCOST Benefit cost rule variant VARCSTR 4 0 0 no

21 CURR_ID Lookup T5UBY.CURRE lookup on CurrencyKey VARCSTR 5 0 0 yes

22 FACTOR_COST_EMPLEE

T5UBI.CSTFA Benefits Factor for EmployeeCosts DECIMAL 48 7 4 yes

23 FACTOR_COST_EMPLER

T5UBI.ERCFA Benefit Factor for EmployerCredit/Costs DECIMAL 48 7 4 yes

24 FACTOR_COST_PROVIDER T5UBI.ACCFA Benefit Factor for Provider Cost DECIMAL 48 7 4 yes

25 GENDER_GRP_DESCR

DD07T.DDTEXT - Gender Grp Desc lookup,domain BEN_GENDER VARCSTR 40 0 0 yes

26 GENDER_GRP_ID PK T5UBI.GENDR Benefit gender data forinsurance costs calculation VARCSTR 1 0 0 no

27 GENDER_RELEVNT_FLAG

T5UBH.GENIN Benefit indicator gender isrelevant for cost rule variant INTEGER 4 0 0 yes


29 LOAD_TIME Time Loaded into Rapid mart VARCSTR 8 0 0 yes

30 LOOKUP_MAX_AGE Lookup T5UBL maximum age in age group orset to 99 if no maximum specified INTEGER 4 0 0 yes

31 LOOKUP_MAX_LOS Lookup T5UBM maximum LOS in LOS groupor set to 999 if no maximum specified INTEGER 4 0 0 yes

32 LOOKUP_MAX_SAL Lookup T5UBK max salary in salary group orset to big number if no maximum specified DECIMAL 48 15 2 yes

33 LOOKUP_MIN_AGE Lookup T5UBL minimum age in age group orset to 0 if no minimum specified INTEGER 4 0 0 yes

34 LOOKUP_MIN_LOS Lookup T5UBM minimum LOS in LOS group orset to 0 if no minimum specified INTEGER 4 0 0 yes



35 LOOKUP_MIN_SAL Lookup T5UBK minimum salary in salary groupor set to 0 if no minimum specified DECIMAL 48 15 2 yes

36 PARAMETER_GRP_FULL_NAME

Concatenated: T5UBH.CRGRP BenefitParameter Group for Grouping + LookupT5UCY.LTEXT lookup on Cost groupdescription

VARCSTR 30 0 0 yes

37 PARAMETER_GRP_ID T5UBH.CRGRP Benefit Parameter Group forGrouping VARCSTR 4 0 0 yes

38 SALARY_GRP_DESCR

Lookup T5UCK.LTEXT lookup on Salary groupdescritpion VARCSTR 20 0 0 yes

39 SALARY_GRP_ID PK T5UBI.SALGR Benefit salary group VARCSTR 4 0 0 no

40 SALARY_RELEVNT_FLAG

T5UBH.SALIN Benefit indicator salary isrelevant INTEGER 4 0 0 yes

41 SENIORITY_GRP_ID PK T5UBI.LOSGR Benefit seniority group VARCSTR 4 0 0 no

42 SENIORITY_RELEVNT_FLAG

T5UBH.LOSIN Benefit indicator seniority isrelevant INTEGER 4 0 0 yes

43 SMOKER_FLAG PK Benefit smoker indicator INTEGER 4 0 0 no

44 SMOKER_RELEVNT_FLAG

T5UBH.SMOIN Benefit indicator smokerrelevant for cost rule variant INTEGER 4 0 0 yes

45 VALID_FROM_DATE T5UBI.BEGDA Start Date DATETIME 24 0 9 yes

46 VALID_TO_DATE PK T5UBI.ENDDA End Date DATETIME 24 0 9 no



BENEFIT_ENROLL_0167_STAGEInclude date-effective attributes from PA0167, PA0001, Job, Employee, Postion, Org Unit dimensions; used to loadBENEFIT_ENROLLMENT_FACT



Nullable

1 ADDTNL_PROVIDER_NAME PA0167.PROVI Additional benefit provider NVARCSTR 30 0 0 yes

2 ADJUST_REASON_ID PA0167.EVENT Benefit adjustment reason NVARCSTR 4 0 0 yes

3 ADMIN_GRP_CODE PA0001.SBMOD Administrator group NVARCSTR 4 0 0 yes

4 ADMIN_ID_HR PA0001.SACHP Administrator for HR masterdata NVARCSTR 3 0 0 yes

5 ADMIN_ID_TIME PA0001.SACHZ Administrator for timerecording NVARCSTR 3 0 0 yes

6 AFFIDAVIT_DATE PA0171.AFFDT Affidavit date DATETIME 24 0 9 yes

7 AMT_EMPLEE_COST Monthly Benefit Employee Cost Amount fromFunction HR_BEN_GET_PLAN_COST DECIMAL 48 13 2 yes

8 AMT_EMPLEE_POST_TAX

Benefits Additional Employee Post-Tax Costsfrom Function HR_BEN_GET_PLAN_COST DECIMAL 48 13 2 yes

9 AMT_EMPLER_COST_CREDIT

Benefit Employer Cost/Credit Amount fromFunction HR_BEN_GET_PLAN_COST DECIMAL 48 13 2 yes

10 AMT_IMPUTED_INCOME

Benefits Imputed Income from FunctionHR_BEN_GET_PLAN_COST DECIMAL 48 13 2 yes

11 AMT_PROVIDER_COST

Benefit Provider Cost Amount from FunctionHR_BEN_GET_PLAN_COST DECIMAL 48 13 2 yes

12 BENFT_AREA_ID PA0167.BAREA Benefit area NVARCSTR 2 0 0 yes

13 BENFT_OFFICER_FLAG PA0171.OFFIC Benefits company officer (1/0) INTEGER 4 0 0 yes

14 BENFT_PLAN_ID PA0167.BPLAN Benefit plan NVARCSTR 4 0 0 yes

15 BENFT_PLAN_TYPE_ID PK PA0167.PLTYP/SUBTYP - Benefit plan type NVARCSTR 4 0 0 no

16 BUS_AREA_ID PA0001.GSBER Business area NVARCSTR 4 0 0 yes



17 CALC_ELIGIBLTY_DATE PA0167.ELIDT Calculated eligibility date DATETIME 24 0 9 yes

18 CMPNY_CODE_ID PA0001.BUKRS Company code NVARCSTR 4 0 0 yes

19 CONTRACT_ID PA0001.ANSVH Work contract (grouping forstatistical reporting) NVARCSTR 2 0 0 yes

20 COST_CNTR_ID PA0001.KOSTL Cost center NVARCSTR 10 0 0 yes

21 COST_RULE_ID T5UBB.BCOST - Benefit Cost Rule Variant NVARCSTR 4 0 0 yes

22 COUNTRY_GRP_ID T500P.MOLGA - Country Name - LookupMOLGA from T500P NVARCSTR 2 0 0 yes

23 COUNT_BENEFIC_DEPENDNT

Calculated: Number of dependents covered onhealth plan INTEGER 4 0 0 yes

24 CREDIT_USABLE_FLAG

Benefits Indicator: Credits Can Be Used. FromFunction HR_BEN_GET_PLAN_COST (0 = no,1 = Yes)

INTEGER 4 0 0 yes

25 CTRL_AREA_ID PA0001.KOKRS Controlling area NVARCSTR 4 0 0 yes

26 CURRENT_FLAG Set to 1 if the record is current (ENDDA =9999.12.31) INTEGER 4 0 0 yes

27 CURR_ID PA0167.CURRE - Benefit Currency Key NVARCSTR 5 0 0 yes

28 DEPENDNT_COVERAGE_ID

PA0167.DEPCV - Dependent coverage forhealth plan NVARCSTR 4 0 0 yes

29 ELIGIBLTY_RULE_ID PA0167.BELIG - Eligibility rule/Type ofEnrollment ID NVARCSTR 4 0 0 yes

30 EMPLOYEE_GRP_ID PA0001.PERSG Employee group NVARCSTR 1 0 0 yes

31 EMPLOYEE_SUBGRP_ID PA0001.PERSK Employee subgroup NVARCSTR 2 0 0 yes

32 ENROLLMNT_TYPE_ID

PA0167.ENRTY - Benefit type of planenrollment NVARCSTR 1 0 0 yes

33 HEALTH_PLAN_ID PA0167.BOPTI Health plan options NVARCSTR 4 0 0 yes

34 HIGH_COMPENSATN_FLAG PA0171.HICMP Highly compensated (1/0) INTEGER 4 0 0 yes



35 INFOTYPE_ID Hard-coded value PA0167 NVARCSTR 6 0 0 yes

36 INSURED_FLAG PA0171.EVINS Evidence of insurability (1/0) INTEGER 4 0 0 yes

37 JOB_ID PA0001.STELL Job NVARCSTR 8 0 0 yes

38 LOAD_DATE Date and time when the record was loaded DATETIME 24 0 9 yes

39 LOAD_TIME Time when the record was loaded NVARCSTR 8 0 0 yes

40 MANUAL_ELIGIBLTY_DATE PA0167.ELDTO Override eligibility date DATETIME 24 0 9 yes

41 ORG_KEY_ID PA0001.VDSK1 Organizational key NVARCSTR 14 0 0 yes

42 ORG_UNIT_ID PA0001.ORGEH Organizational unit NVARCSTR 8 0 0 yes

43 OTHER_BENFT_FLAG PA0167.COORD Benefits coordinationindicator/Other Benefits Flag INTEGER 4 0 0 yes

44 OTHER_PLAN_FLAG PA0171.OTHER Employee covered by anotherplan (1/0) INTEGER 4 0 0 yes

45 OWNER_FLAG PA0171.OWNER Enterprise owner (1/0) INTEGER 4 0 0 yes

46 PARTICIPATN_DATE PA0167.PARDT Participation date DATETIME 24 0 9 yes

47 PAYROLL_ADMIN_ID PA0001.SACHA Payroll administrator NVARCSTR 3 0 0 yes

48 PAYROLL_AREA_ID PA0001.ABKRS Payroll area NVARCSTR 2 0 0 yes

49 PERSONNEL_AREA_ID PA0001.WERKS Personnel area NVARCSTR 4 0 0 yes

50 PERSONNEL_SUBAREA_ID PA0001.BTRT Personnel subarea NVARCSTR 4 0 0 yes

51 PERSON_ID PK PA1067.PERNR - Personnel number NVARCSTR 8 0 0 no

52 PERSON_ID_SUPERVISOR

PA0001.MSTBR Supervisor area - Specialfeature for USA and Canada: use this field tostore the personnel number of the supervisor towhom the employee is assigned

NVARCSTR 8 0 0 yes



53 POLICY_NUM PA0167.POLNR Policy number NVARCSTR 20 0 0 yes

54 POSITION_ID PA0001.PLANS Position NVARCSTR 8 0 0 yes

55 PROGRAM_GRP_ID_01

PA0167.BENGR Employee benefit firstprogram grouping NVARCSTR 4 0 0 yes


PA0167.BSTAT Benefit second programgrouping NVARCSTR 4 0 0 yes

57 SEASONAL_WORKER_FLAG PA0171.SEASN Seasonal worker (1/0) INTEGER 4 0 0 yes

58 SMOKER_FLAG PA0171.SMOKE Smoker indicator (1/0) INTEGER 4 0 0 yes

59 TERMINATN_RULE_ID T5UBU.BTERM - Benefit Termination rule NVARCSTR 4 0 0 yes

60 VALID_FROM_DATE PK PA0167.ENDDA End date DATETIME 24 0 9 no

61 VALID_FROM_DATE_ASSIGN PA0001.BEGDA Start date DATETIME 24 0 9 yes

62 VALID_FROM_DATE_BENFT PA0167.BEGDA Start date DATETIME 24 0 9 yes

63 VALID_FROM_DATE_GENERAL

PA0171.ENDDA End date - for GeneralBenefits infotype DATETIME 24 0 9 yes

64 VALID_TO_DATE PK PA0167.BEGDA Start date DATETIME 24 0 9 no

65 VALID_TO_DATE_ASSIGN PA0001.ENDDA End date DATETIME 24 0 9 yes

66 VALID_TO_DATE_BENFT PA0167.ENDDA End date DATETIME 24 0 9 yes

67 VALID_TO_DATE_GENERAL

PA0171.BEGDA Start date for GeneralBenefits Infotype DATETIME 24 0 9 yes






Nullable





5 AMT_ALT_COVERAGE

PA0168.COVOV - Salary override coverageamount DECIMAL 48 15 2 yes

6 AMT_BASIC_COVERAGE

Benefit Insurance Coverage Basic Amountfrom Function HR_BEN_EVAL_AMOUNT DECIMAL 48 15 2 yes

7 AMT_BENFT_SALARY Annual Benefit Salary from FunctionHR_BEN_GET_PLAN_SALARY DECIMAL 48 15 2 yes

8 AMT_COVERAGEPA0168.COVOV/ T74FC.COVAM- Coverageamount - Life only when Coverage Group is notdefined. Caluclated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes

9 AMT_COVERAGE_MAX T74FC.MAXAM - Maximum coverage amount DECIMAL 48 15 2 yes








14 AMT_INSURANCE_COVERAGE

Benefit Insurance Coverage Amount fromFunctionHR_BEN_CALC_COVERAGE_AMOUNT

DECIMAL 48 15 2 yes

15 AMT_PER_ADDTL_INSURANCE_UNIT

T74FC.ADDUN - Benefit Unit of AdditionalInsurance Coverage DECIMAL 48 15 2 yes





17 AMT_SALARY_OVERRIDE PA0168.SALOV- Benefits salary override DECIMAL 48 15 2 yes




21 BENFT_PLAN_TYPE_ID PK PA0168.PLTYP/SUBTY - Benefit plan type NVARCSTR 4 0 0 no



24 CHANGE_DATE PA0168.AEDTM Last changed on DATETIME 24 0 9 yes




28 COST_RULE_ID T74FA.BCOST Plan cost formula NVARCSTR 4 0 0 yes


30 COUNT_BENEFIC_DEPENDNT Calculated:Number of beneficiaries DECIMAL 48 28 0 yes

31 COVERAGE_GRP_FLAG T74FB.COVIN Indicator for coverage group DECIMAL 48 28 0 yes

32 COVERAGE_GRP_ID Lookup Coverage Group using SAP function NVARCSTR 4 0 0 yes

33 COVERAGE_RULE_ID T74FA.BCOVE Benefits insurance coverageformula NVARCSTR 4 0 0 yes



INTEGER 4 0 0 yes





37 CURR_ID PA0168.CURRE Benefit currency key NVARCSTR 5 0 0 yes

38 ELIGIBLTY_RULE_ID T5UBU.BELIG - Benefits eligibility rule NVARCSTR 4 0 0 yes



41 ENROLLMNT_TYPE_ID PA0168.ENRTY Benefit type of plan enrollment NVARCSTR 1 0 0 yes



44 INSURANCE_OPTION_DESCR

T74GA.LTEXT -Lookup text for BCOVR -Insurance options NVARCSTR 30 0 0 yes

45 INSURANCE_OPTION_ID PA0168.BCOVR - Benefits insurance option NVARCSTR 4 0 0 yes

















60 PERSON_ID PK PA0168.PERNR Personnel number NVARCSTR 8 0 0 no


PA0001.MSTBR Supervisor area - Specialfeature for USA and Canada:use this field to store the personnel number ofthe supervisor to whom the employee isassigned

NVARCSTR 8 0 0 yes



PA0168.BENGR BSTAT Benefit first programgrouping NVARCSTR 4 0 0 yes


PA0168.BSTAT BSTAT Benefit secondprogram grouping NVARCSTR 4 0 0 yes

65 QTY_ADDTL_INSURANCE_UNITS

PA0168.ADDNO - Benefit Number ofAdditional Insurance Coverage Units INTEGER 4 0 0 yes

66 RATE_SALARY_MULTIPLR

T74FC.COVFA - Benefits factor for calculatinginsurance coverage base on Salary(Multiplier) DECIMAL 48 8 5 yes



69 TERMINATN_RULE_ID T5UBU.BTERM - Benefits termination rule NVARCSTR 4 0 0 yes

70 VALID_FROM_DATE PK PA0168.BEGDA Start date DATETIME 24 0 9 no






PA0171.ENDDA End date for General BenefitsInfotype DATETIME 24 0 9 yes

74 VALID_TO_DATE PK PA0168.ENDDA End date DATETIME 24 0 9 no










Nullable

1 ACCOUNT_NUM PA0169.ACCTN - Account number NVARCSTR 20 0 0 yes





6 AMT_PENSION_ADJUST PA0169.PAAMT - Pension adjustment amount DECIMAL 48 13 2 yes

7 AMT_POSTTAX_SAVNG

PA0169.PTAMT - Employee post-tax savingsplan contribution amount DECIMAL 48 13 2 yes

8 AMT_PRETAX_SAVNG

PA0169.EEAMT Employees pre-tax savingcontribution amount DECIMAL 48 13 2 yes

9 BENFT_AREA_ID PA0169.BAREA - Benefit area NVARCSTR 2 0 0 yes


11 BENFT_PLAN_ID PA0169.BPLAN - Benefit plan NVARCSTR 4 0 0 yes

12 BENFT_PLAN_TYPE_ID PK PA0169.PLTYP/SUBTYP - Benefit plan type NVARCSTR 4 0 0 no


14 CALC_ELIGIBLTY_DATE PA0169.ELIDT - Calculated eligibility date DATETIME 24 0 9 yes





17 CONTRIBTN_RULE_ID_EMPLEE

T74FD. EECON Benefits employeecontribution rule NVARCSTR 4 0 0 yes

18 CONTRIBTN_RULE_ID_EMPLER T74FD.ERCON - Employer contribution rule NVARCSTR 4 0 0 yes



21 COUNT_BENEFIC_DEPENDNT Calculated number of savings plan dependents INTEGER 4 0 0 yes




25 ELIGIBLTY_RULE_ID T5UBU.BELIG - Eligibility rule NVARCSTR 4 0 0 yes




PA0169.ENRTY Benefit type of planenrollment NVARCSTR 1 0 0 yes

29 EXIST_FLAG PA0169.PERNR - Personnel number NVARCSTR 8 0 0 yes




33 INVESTMNT_GRP_ID T74FD.INVGR - Savings plans investmentgroup NVARCSTR 4 0 0 yes

34 INVESTMNT_OTHER_FLAG

PA0169.IPT01-IPT05 Indicates that more than5 investment funds are used. Check SAP fornames of other funds

DECIMAL 48 4 1 yes



35 INVESTMNT_PLAN_ID_01 PA0169.INV01 Investments for savings plans NVARCSTR 4 0 0 yes








43 MANUAL_ELIGIBLTY_DATE PA0169.ELDTO - Override eligibility date DATETIME 24 0 9 yes





48 PARTICIPATN_DATE PA0169.PARDT - Participation date DATETIME 24 0 9 yes










NVARCSTR 8 0 0 yes


56 PRCNT_INVESTMNT_01 PA0169.IPT01 Investment percentage INTEGER 4 0 0 yes





61 PRCNT_INVESTMNT_OTHER

PA0169.ITP06-ITP20Remaining percentinvestment not covered by IPT1-5. Check SAPfor remaining percentages

INTEGER 4 0 0 yes

62 PRCNT_POSTTAX_SAVNG

PA1069.PTPCT - Employee post-tax savingplan contribution percentage DECIMAL 48 5 2 yes

63 PRCNT_PRETAX_SAVNG

PA1069.EEPCT - Employees pre-tax savingsplan contribution percentage DECIMAL 48 5 2 yes

64 PROGRAM_GRP_ID_01 PA0169.BENGR - Employee benefit first group NVARCSTR 4 0 0 yes

65 PROGRAM_GRP_ID_02 PA0169.BSTAT - Benefit Program Grouping 2 NVARCSTR 4 0 0 yes



68 START_POSTTAX_FLAG

PA0169.PSTTX - Start post tax contributionsimmediately INTEGER 4 0 0 yes


70 VALID_FROM_DATE PK PA0169.BEGDA - Start date DATETIME 24 0 9 no







74 VALID_TO_DATE PK PA0169.ENDDA - End date DATETIME 24 0 9 no





78 VESTNG_RULE_ID T74FD.VESTI - Vesting rules for employeecontributions to savings plans NVARCSTR 4 0 0 yes






Nullable





5 AMT_CONTRIBUTN_EMPLEE

PA0170.CAMNT - Employee contributionamount to spending account DECIMAL 48 13 2 yes




9 BENFT_PLAN_TYPE_ID PK PA0170.PLTYP Benefit plan type NVARCSTR 4 0 0 no












19 ELIGIBLTY_RULE_ID T5UBU.BELIG - Benefit eligibility rule NVARCSTR 4 0 0 yes

























NVARCSTR 8 0 0 yes



PA0170.BENGR Employee benefit programfirst group NVARCSTR 4 0 0 yes


PA0170.BSTAT Employee benefit programsecond group NVARCSTR 4 0 0 yes



46 TERMINATN_RULE_ID T5UBU.BTERM - Benefit termination rule NVARCSTR 4 0 0 yes

47 VALID_FROM_DATE PK PA0170.ENDDA/T5UBG.ENDDA End date DATETIME 24 0 9 no





51 VALID_TO_DATE PK PA0170.BEGDAT5UBG.BEGDA Start date DATETIME 24 0 9 no







Nullable





5 AMT_CREDIT PA0236.CRAMO Employees actual creditamount DECIMAL 48 13 2 yes




9 BENFT_PLAN_TYPE_ID PK PA0236.PLTYP Plan type NVARCSTR 4 0 0 no












19 ELIGIBLTY_RULE_ID T5UBU. BELIG Eligibility rule NVARCSTR 4 0 0 yes

























NVARCSTR 8 0 0 yes



PA0236.BENGR Employee benefit programfirst grouping NVARCSTR 4 0 0 yes


PA0236.BSTAT- Benefit program secondgrouping NVARCSTR 4 0 0 yes



46 TERMINATN_RULE_ID T5UBU.BTERM - Termination rule NVARCSTR 4 0 0 yes

47 VALID_FROM_DATE PK PA0236.BEGDA From DATETIME 24 0 9 no





51 VALID_TO_DATE PK PA0236.ENDDA To DATETIME 24 0 9 no




BENEFIT_ENROLLMENT_FACTBenefit plan enrollment information (Employee Level) merged from PA0167, PA0168, PA0171, PA0000, PA0001, PA0002, PA0008,PA0169, PA0170, PA0236 infotypes



Nullable

1 ADMIN_GRP_CODE PK PA0001.SBMOD Administrator group NVARCSTR 4 0 0 no

2 ADMIN_ID_HR PK PA0001.SACHP Administrator for HR masterdata NVARCSTR 3 0 0 no

3 ADMIN_ID_PAYROLL PK PA0001.SACHA Payroll administrator NVARCSTR 3 0 0 no

4 ADMIN_ID_TIME PK PA0001.SACHZ Administrator for timerecording NVARCSTR 3 0 0 no


6 AMT_ALT_COVERAGE

PA0168.COVOV - Benefit alternative amountfor insurance coverage amount DECIMAL 48 15 2 yes





PA0170.CAMNT - Employee contributionamount to spending account OR BenefitEmployee Cost Amount from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 15 2 yes

10 AMT_CONTRIBUTN_MAX

T5UBG.RMAXA Maximum contribution tospending account (Lookup on tableBENEFIT_SPENDING_ACCOUNT)

DECIMAL 48 15 2 yes

11 AMT_CONTRIBUTN_MIN

T5UBG.RMINA Minimum contribution tospending account (Lookup on tableBENEFIT_SPENDING_ACCOUNT)

DECIMAL 48 15 2 yes

12 AMT_COVERAGEPA0168.COVOV/ T74FC.COVAM- Coverageamount - Life only when Coverage Group is notdefined. Calculated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes

13 AMT_COVERAGE_MAX

T74FC.MAXAM - Maximum coverage amount.Calculated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes


15 AMT_EMPLEE_POSTTAX_HEALTH


16 AMT_EMPLEE_POSTTAX_INSURANCE




17 AMT_EMPLER_COST Benefit Employer Cost/Credit Amount fromFunction HR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes





DECIMAL 48 15 2 yes



T74FC.ADDUN (via functionHR_BEN_GET_RULE_COVERAGE) - BenefitValue of each Unit of Additional InsuranceCoverage

DECIMAL 48 15 2 yes

22 AMT_POSTTAX_SAVNG


23 AMT_PRETAX_SAVNG





26 BENFT_AREA_ID PK PA0168/0167/169/170/171/236.BAREA Benefitarea NVARCSTR 2 0 0 no


28 BENFT_PLAN_ID PK PA0168/0167/169/170/171/236.BPLAN Benefitplan NVARCSTR 4 0 0 no

29 BENFT_PLAN_KEY PK Lookup on BENEFIT_PLAN dimensionsurrogate key DECIMAL 48 28 0 no

30 BENFT_PLAN_TYPE_ID PK PA0168/0167/169/170/171/236.PLTYP/SUBTY

- Benefit plan type NVARCSTR 4 0 0 no

31 BUS_AREA_ID PK PA0001.GSBER Business area NVARCSTR 4 0 0 no

32 CALC_ELIGIBLTY_DATE

PA0168/0167/169/170/171/236.ELIDTCalculated eligibility date DATETIME 24 0 9 yes

33 CMPNY_CODE_ID PK PA0001.BUKRS Company code NVARCSTR 4 0 0 no

34 CONTRACT_ID PK PA0001.ANSVH Work contract (grouping forstatistical reporting) NVARCSTR 2 0 0 no



35 CONTRIBTN_RULE_ID_EMPLEE PK T74FD. EECON Benefits employee

contribution rule NVARCSTR 4 0 0 no

36 CONTRIBTN_RULE_ID_EMPLER PK T74FD.ERCON - Employer contribution rule NVARCSTR 4 0 0 no

37 COST_CNTR_ID PK PA0001.KOSTL Cost center NVARCSTR 10 0 0 no

38 COST_RULE_ID PK T74FA.BCOST Plan cost formula NVARCSTR 4 0 0 no

39 COUNTRY_GRP_ID PK T500P.MOLGA - Country Name - LookupMOLGA from T500P NVARCSTR 2 0 0 no


Calculated:Number ofbeneficiaries/Dependents INTEGER 4 0 0 yes

41 COVERAGE_GRP_FLAG T74FB.COVIN Indicator for coverage group DECIMAL 48 28 0 yes

42 COVERAGE_GRP_ID PK Lookup Coverage Group using SAPfunction/T74FC.COVGR - Coverage group NVARCSTR 4 0 0 no

43 COVERAGE_RULE_ID PK T74FA.BCOVE Benefits insurance coverageformula NVARCSTR 4 0 0 no



INTEGER 4 0 0 yes

45 CTRL_AREA_ID PK PA0001.KOKRS Controlling area NVARCSTR 4 0 0 no

46 CURRENT_FLAG PK Set to 1 if the record is current (ENDDA =9999.12.31) INTEGER 4 0 0 yes

47 CURR_ID PK PA0168/169/170/171/236.CURRE Benefitcurrency key NVARCSTR 5 0 0 no

48 DEPENDNT_COVERAGE_ID PK PA0167.DEPCV - Dependent coverage for

health plan NVARCSTR 4 0 0 no

49 ELIGIBLTY_RULE_ID PK T5UBU.BELIG - Benefits eligibility rule NVARCSTR 4 0 0 no

50 EMPLOYEE_GRP_ID PK PA0001.PERSG Employee group NVARCSTR 1 0 0 no

51 EMPLOYEE_KEY PK EMPLOYEE.EMPLOYEE_KEY - lookup on thesurrogate key for EMPLOYEE dimension DECIMAL 48 28 0 no

52 EMPLOYEE_KEY_MGR PK

LINE_MANAGER_HIER.EMPLOYEE_KEY -lookup on the surrogate key forLINE_MANAGER_HIER dimension

DECIMAL 48 28 0 no



53 EMPLOYEE_SUBGRP_ID PK PA0001.PERSK Employee subgroup NVARCSTR 2 0 0 no

54 ENROLLMNT_TYPE_ID PK PA0168/0167/169/170/171/236.ENRTY Benefit

type of plan enrollment NVARCSTR 1 0 0 no

55 HEALTH_PLAN_ID PK PA0167.BOPTI Health plan options NVARCSTR 4 0 0 no


57 INFOTYPE_CODE Hard-coded valuesPA0168/0167/169/170/171/236 NVARCSTR 6 0 0 yes

58 INSURANCE_OPTION_ID PK PA0168.BCOVR - Benefits insurance option NVARCSTR 4 0 0 yes

59 INSURANCE_OPTION_KEY

Surrogate key generated for date-effectiveINSURANCE_OPTION_KEY dimension DECIMAL 48 28 0 no


61 INVESTMNT_GRP_ID PK T74FD.INVGR - Savings plans investmentgroup NVARCSTR 4 0 0 no



DECIMAL 48 4 1 yes

63 INVESTMNT_PLAN_ID_01 PK PA0169.INV01 Investments for savings plans NVARCSTR 4 0 0 no






69 JOB_KEY PK JOB.JOB_KEY - lookup on the surrogate keyfor JOB dimension DECIMAL 48 28 0 no





72 MANUAL_ELIGIBLTY_DATE

PA0168/0167/169/170/171/236.ELDTOOverride eligibility date DATETIME 24 0 9 yes

73 ORG_KEY_ID PK PA0001.VDSK1 Organizational key NVARCSTR 14 0 0 no


75 ORG_UNIT_KEY PKORGANIZATION_UNIT.ORG_UNIT_KEY -lookup on the surrogate key forORGANIZATION_UNIT dimension

DECIMAL 48 28 0 no



78 PARTICIPATN_DATE PK PA0168/0167/169/170/171/236.PARDTParticipation date DATETIME 24 0 9 no

79 PAYROLL_AREA_ID PK PA0001.ABKRS Payroll area NVARCSTR 2 0 0 no

80 PERSONNEL_AREA_ID PK PA0001.WERKS Personnel area NVARCSTR 4 0 0 no

81 PERSONNEL_SUBAREA_ID PK PA0001.BTRT Personnel subarea NVARCSTR 4 0 0 no

82 PERSON_ID PK PA0168/0167/169/170/171/236.PERNRPersonnel number NVARCSTR 8 0 0 no

83 PERSON_ID_MGRLINE_MANAGER_HIER.PERSON_ID - lookupon the Manager Personnel Number forLINE_MANAGER_HIER dimension

NVARCSTR 8 0 0 yes



NVARCSTR 8 0 0 yes


86 POSITION_KEY PK POSITION.POSITION_KEY - lookup on thesurrogate key for POSITION dimension DECIMAL 48 28 0 no










INTEGER 4 0 0 yes





95 PROGRAM_GRP_ID_01 PK PA0168/0167/169/170/171/236.BENGR

BSTAT Benefit first program grouping NVARCSTR 4 0 0 no

96 PROGRAM_GRP_ID_02 PK PA0168/0167/169/170/171/236.BSTAT Benefit

second program grouping NVARCSTR 4 0 0 no




T74FC.COVFA - Benefits factor for calculatinginsurance coverage base on Salary(Multiplier).Calculated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 8 5 yes



101 SPENDNG_ACCT_KEY PK Lookup on surrogate key of

BENEFIT_SPENDING_ACCOUNT dimension INTEGER 4 0 0 no



103 TERMINATN_RULE_ID PK T5UBU.BTERM - Benefits termination rule NVARCSTR 4 0 0 no

104 UOM_CONTRIBUTN_EMPLEE

Unit of Measure for Employee ContributionAmount NVARCSTR 10 0 0 yes

105 VALID_FROM_DATE PK Calculated Merged Start date DATETIME 24 0 9 no




107 VALID_FROM_DATE_BENFT

PA0168/0167/169/170/171/236.BEGDA Startdate DATETIME 24 0 9 yes

108 VALID_FROM_DATE_EMPL

EMPLOYEE.VALID_FROM_DATE - Start datefor valid Employee Personal record DATETIME 24 0 9 yes



110 VALID_FROM_DATE_JOB

JOB.VALID_FROM_DATE - Start date for validJobrecord DATETIME 24 0 9 yes

111 VALID_FROM_DATE_ORG

ORGANIZATION_UNIT.VALID_FROM_DATE -Start date for valid Org unit record DATETIME 24 0 9 yes

112 VALID_FROM_DATE_POSTN

POSITION.VALID_FROM_DATE - Start datefor valid Position record DATETIME 24 0 9 yes

113 VALID_TO_DATE PK Calculated End date DATETIME 24 0 9 no


115 VALID_TO_DATE_BENFT

PA0168/0167/169/170/171/236.ENDDA Enddate DATETIME 24 0 9 yes

116 VALID_TO_DATE_EMPL

EMPLOYEE.VALID_TO_DATE - End date forvalid Employee Personal record DATETIME 24 0 9 yes



118 VALID_TO_DATE_JOB JOB.VALID_TO_DATE - End date for validJobrecord DATETIME 24 0 9 yes

119 VALID_TO_DATE_ORG

ORGANIZATION_UNIT.VALID_TO_DATE -End date for valid Org unit record DATETIME 24 0 9 yes

120 VALID_TO_DATE_POSTN

POSITION.VALID_TO_DATE - End date forvalid Position record DATETIME 24 0 9 yes

121 VALID_TO_DATE_PREV Calculated BEGDA Start date - 1 DATETIME 24 0 9 yes

122 VESTNG_RULE_ID PK T74FD.VESTI - Vesting rules for employeecontributions to savings plans NVARCSTR 4 0 0 no




Summarization of BENEFIT_ENROLLMENT_FACT by certain dimensions



Nullable

1 AMT_BENFT_SALARY_AVG

Average Annual Benefit Salary from FunctionHR_BEN_GET_PLAN_SALARY DECIMAL 48 15 2 yes

2 AMT_BENFT_SALARY_MAX

Max Annual Benefit Salary from FunctionHR_BEN_GET_PLAN_SALARY DECIMAL 48 15 2 yes

3 AMT_CONTRIBUTN_EMPLEE_AVG

Average PA0170.CAMNT - Employeecontribution amount to spending account ORBenefit Employee Cost Amount from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 13 2 yes

4 AMT_CONTRIBUTN_EMPLEE_MAX

Max PA0170.CAMNT - Employee contributionamount to spending account OR BenefitEmployee Cost Amount from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 13 2 yes

5 AMT_COVERAGE_AVG

Average PA0168.COVOV/ T74FC.COVAM-Coverage amount - Life only when CoverageGroup is not defined. Calculated as a lookupon INSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes

6 AMT_COVERAGE_MAX

Average PA0168.COVOV/ T74FC.COVAM-Coverage amount - Life only when CoverageGroup is not defined. Calculated as a lookupon INSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes

7 AMT_EMPLEE_POSTTAX_INSUR_AVG

Average Benefits Additional EmployeePost-Tax Costs from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 15 2 yes

8 AMT_EMPLEE_POSTTAX_INSUR_MAX

Max Benefits Additional Employee Post-TaxCosts from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 15 2 yes

9 AMT_EMPLEE_POSTX_HEALTH_AVG

Average Benefits Additional EmployeePost-Tax Costs from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 15 2 yes

10 AMT_EMPLEE_POSTX_HEALTH_MAX

Max Benefits Additional Employee Post-TaxCosts from FunctionHR_BEN_GET_PLAN_COST

DECIMAL 48 15 2 yes

11 AMT_EMPLER_COST_AVG

Average Benefit Employer Cost/Credit Amountfrom Function HR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes

12 AMT_EMPLER_COST_MAX

Max Benefit Employer Cost/Credit Amountfrom Function HR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes

13 AMT_IMPUTED_INCOME_AVG

Average Benefits Imputed Income fromFunction HR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes

14 AMT_IMPUTED_INCOME_MAX

Max Benefits Imputed Income from FunctionHR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes

15 AMT_INSUR_COVERAGE_AVG

Average Benefit Insurance Coverage Amountfrom FunctionHR_BEN_CALC_COVERAGE_AMOUNT

DECIMAL 48 15 2 yes

16 AMT_INSUR_COVERAGE_MAX

Max Benefit Insurance Coverage Amount fromFunctionHR_BEN_CALC_COVERAGE_AMOUNT

DECIMAL 48 15 2 yes



17 AMT_PER_ADDTL_INSUR_UNIT_AVG

T74FC.ADDUN (via functionHR_BEN_GET_RULE_COVERAGE) -Average Benefit Value of each Unit ofAdditional Insurance Coverage

DECIMAL 48 15 2 yes

18 AMT_PER_ADDTL_INSUR_UNIT_MAX

T74FC.ADDUN (via functionHR_BEN_GET_RULE_COVERAGE) - MaxBenefit Value of each Unit of AdditionalInsurance Coverage

DECIMAL 48 15 2 yes

19 AMT_POSTTAX_SAVNG_AVG

Average PA0169.PTAMT - Employee post-taxsavings plan contribution amount DECIMAL 48 13 2 yes

20 AMT_POSTTAX_SAVNG_MAX

Max PA0169.PTAMT - Employee post-taxsavings plan contribution amount DECIMAL 48 13 2 yes

21 AMT_PRETAX_SAVNG_AVG

PA0169.EEAMT Average Employees pre-taxsaving contribution amount DECIMAL 48 13 2 yes

22 AMT_PRETAX_SAVNG_MAX

PA0169.EEAMT Max Employees pre-taxsaving contribution amount DECIMAL 48 13 2 yes

23 AMT_PROVIDER_COST_AVG

Average Benefit Provider Cost Amount fromFunction HR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes

24 AMT_PROVIDER_COST_MAX

Max Benefit Provider Cost Amount fromFunction HR_BEN_GET_PLAN_COST DECIMAL 48 15 2 yes

25 BENFT_AREA_ID PK T5UBV.BAREA Benefit area NVARCSTR 2 0 0 no

26 BENFT_PLAN_ID PK T5UBU.BPLAN Benefit plan NVARCSTR 4 0 0 no

27 BENFT_PLAN_KEY Lookup on BENEFIT_PLAN dimensionsurrogate key DECIMAL 48 28 0 yes




31 COUNT_BENEFIC_DEPENDNT_AVG

Average Number of Dependents orbeneficiaries listed on plan (fromPA0168/0167/169/170/171/236)

DECIMAL 48 4 2 yes

32 COUNT_BENEFIC_DEPENDNT_MAX

Max number of dependents orbeneficiaries(fromPA0168/0167/169/170/171/236)

DECIMAL 48 28 0 yes

33 COUNT_BENEFIC_DEPENDNT_TTL

Total Number of Dependents or beneficiarieslisted on plan(fromPA0168/0167/169/170/171/236)

DECIMAL 48 28 0 yes

34 COUNT_EMPLEE_ENROLL

Number of employees enrolled in plan - basedon eligibility date and participation date. DECIMAL 48 28 0 yes




36 CURR_ID PK T5UB3.CURRE Currency key for benefits(lookup) NVARCSTR 5 0 0 no

37 ELIGIBLTY_RULE_ID T5UBU.BELIG Eligibility rule NVARCSTR 4 0 0 yes



40 ORG_UNIT_KEY PKORGANIZATION_UNIT.ORG_UNIT_KEY -lookup on the surrogate key forORGANIZATION_UNIT dimension

DECIMAL 48 28 0 no



43 PRCNT_POSTTAX_SAVNG_AVG

Average PA1069.PTPCT - Employee post-taxsaving plan contribution percentage DECIMAL 48 5 2 yes

44 PRCNT_POSTTAX_SAVNG_MAX

Max PA1069.PTPCT - Employee post-taxsaving plan contribution percentage DECIMAL 48 5 2 yes

45 PRCNT_PRETAX_SAVNG_AVG

Average PA1069.EEPCT - Employees pre-taxsavings plan contribution percentage DECIMAL 48 5 2 yes

46 PRCNT_PRETAX_SAVNG_MAX

Max PA1069.EEPCT - Employees pre-taxsavings plan contribution percentage DECIMAL 48 5 2 yes

47 PROGRAM_GRP_ID_01 PK T5UBU.BENGR Employee benefit group NVARCSTR 4 0 0 no

48 PROGRAM_GRP_ID_02 PK T5UBU.BSTAT - Employee status NVARCSTR 4 0 0 no

49 QTY_ADDTL_INSUR_UNITS_AVG

PA0168.ADDNO - Average Benefit Number ofAdditional Insurance Coverage Units DECIMAL 48 28 0 yes

50 QTY_ADDTL_INSUR_UNITS_MAX

PA0168.ADDNO - Max Benefit Number ofAdditional Insurance Coverage Units DECIMAL 48 28 0 yes

51 TERMINATN_RULE_ID T5UBU.BTERM Termination rule NVARCSTR 4 0 0 yes



BENEFIT_FSA_STAGE

Flexible Spending Account(FSA) benefits from T5UBG date-effective table - staging to load BENEFIT_PLAN dimension



Nullable


T5UBG.RMAXA Maximum contribution tospending account DECIMAL 48 13 2 yes


T5UBG.RMINA Minimum contribution tospending account DECIMAL 48 13 2 yes

3 BENFT_AREA_ID PK T5UBG.BAREA Benefit area NVARCSTR 2 0 0 no

4 BENFT_PLAN_ID PK T5UBG.BPLAN Benefit plan NVARCSTR 4 0 0 no






10 VALID_FROM_DATE PK T5UBG.BEGDA Start date DATETIME 24 0 9 no

11 VALID_TO_DATE PK T5UBG.ENDDA End date DATETIME 24 0 9 no

12 VALID_TO_DATE_PREV T5UBG.BEGDA Start date - 1 DATETIME 24 0 9 yes



BENEFIT_PLAN

Benefit Plan, Program, FSA detailed date-effected records from T5UBU, T5UB1, T5UBA (merge of date-effective dates)



Nullable





3 BENFT_AREA_DESCR T5UC3.LTEXT - lookup on Benefit Areadescription NVARCSTR 30 0 0 yes

4 BENFT_AREA_ID T5UBA.BAREA - Benefit area NVARCSTR 2 0 0 yes

5 BENFT_PLAN_CATEG_DESCR

DD07T. DDTEXT -Lookup text for benefit plancategory - domain BEN_CATEG NVARCSTR 60 0 0 yes

6 BENFT_PLAN_CATEG_ID T5UB1.BPCAT Benefits plan category NVARCSTR 18 0 0 yes

7 BENFT_PLAN_DESCR Loookup T5UCA.LTEXT Benefit PlanDescription NVARCSTR 30 0 0 yes

8 BENFT_PLAN_FULL_NAME

Concatenated: T5UBA.BPLAN Benefit plan +Loookup T5UCA.LTEXT Benefit PlanDescription

NVARCSTR 40 0 0 yes

9 BENFT_PLAN_ID T5UBA.BPLAN Benefit plan NVARCSTR 4 0 0 yes

10 BENFT_PLAN_KEY PK Generated surrogate key for BENEFIT_PLANdimension DECIMAL 48 28 0 no

11 BENFT_PLAN_STATUS_DESCR

T5UC2.STEXT - Benefit Plan Statusdescription (lookup) NVARCSTR 10 0 0 yes

12 BENFT_PLAN_STATUS_FULL_NAME

Concatenated: T5UBA.PLSTA Benefit planstatus + T5UC2.STEXT - Benefit Plan Statusdescription (lookup)

NVARCSTR 20 0 0 yes

13 BENFT_PLAN_STATUS_ID T5UBA.PLSTA Benefit plan status NVARCSTR 2 0 0 yes

14 BENFT_PLAN_TYPE_DESCR

Lookup T5UC1. LTEXT - Plan TypeDescription NVARCSTR 20 0 0 yes

15 BENFT_PLAN_TYPE_FULL_NAME

Concatenated: T5UBA.PLTYP Plan type +Lookup T5UC1. LTEXT - Plan TypeDescription

NVARCSTR 30 0 0 yes

16 BENFT_PLAN_TYPE_ID T5UBA.PLTYP Plan type NVARCSTR 4 0 0 yes



17 BENFT_PROVIDER_DESCR T51RT.CRETX: Benefit Provider NVARCSTR 30 0 0 yes

18 BENFT_PROVIDER_ID T5UBA.CRENR Benefit provider NVARCSTR 8 0 0 yes

19 COUNTRY_GRP_DESCR T005T.LANDX Country Name (lookup) NVARCSTR 15 0 0 yes




23 ELIGIBLTY_RULE_DESCR

LookupT5UCV.LTEXT lookup on Eligibility ruledescritpion NVARCSTR 20 0 0 yes




27 PROGRAM_GRP_DESCR_01

LookupT5UCT.LTEXT description lookup forthe first benefits program grouping NVARCSTR 20 0 0 yes


LookupT5UC9.LTEXT description lookup forthe second benefits program grouping NVARCSTR 20 0 0 yes

29 PROGRAM_GRP_ID_01 T5UBU.BENGR Employee benefit group NVARCSTR 4 0 0 yes

30 PROGRAM_GRP_ID_02 T5UBU.BSTAT - Employee status NVARCSTR 4 0 0 yes


32 TERMINTN_RULE_DESCR

Lookup T5UEU.LTEXT lookup on Terminationrule descritpion NVARCSTR 20 0 0 yes

33 VALID_FROM_DATE T5UBA.ENDDA End date DATETIME 24 0 9 yes

34 VALID_FROM_DATE_FSA T5UBG.BEGDA Start date DATETIME 24 0 9 yes



35 VALID_FROM_DATE_PLAN T5UBA.ENDDA End date DATETIME 24 0 9 yes

36 VALID_TO_DATE T5UBA.BEGDA Start date DATETIME 24 0 9 yes

37 VALID_TO_DATE_FSA T5UBG.ENDDA End date DATETIME 24 0 9 yes

38 VALID_TO_DATE_PLAN T5UBA.BEGDA Start date DATETIME 24 0 9 yes

39 VALID_TO_DATE_PREV T5UBA/T5UBG.BEGDA Start date - 1 DATETIME 24 0 9 yes

40 WAGE_TYPE_DESCR_EMPLEE

T512T.LGTXT - Long Wage Type Text forEmployee wage type contributions NVARCSTR 25 0 0 yes

41 WAGE_TYPE_DESCR_EMPLER

T512T.LGTXT - Long Wage Type Text forEmployer wage type contributions NVARCSTR 25 0 0 yes

42 WAGE_TYPE_ID_EMPLEE

T5UBA.EEWTY Wage type for employeecontributions NVARCSTR 4 0 0 yes

43 WAGE_TYPE_ID_EMPLER

T5UBA.ERWTY Wage type for employercontributions NVARCSTR 4 0 0 yes



BENEFIT_PLAN_STAGE

Benefit Plans date-effected records from T5UBU, T5UB1, T5UBA, T5UBG, T5UB3; used to load BENEFIT_PLAN dimension



Nullable


2 BENFT_AREA_ID PK T5UBA.BAREA - Benefit area NVARCSTR 2 0 0 no

3 BENFT_PLAN_CATEG_DESCR

DD07T. DDTEXT -Lookup text for benefit plancategory - domain BEN_CATEG NVARCSTR 60 0 0 yes

4 BENFT_PLAN_CATEG_ID T5UB1.BPCAT Benefits plan category NVARCSTR 18 0 0 yes


6 BENFT_PLAN_ID PK T5UBA.BPLAN Benefit plan NVARCSTR 4 0 0 no

7 BENFT_PLAN_STATUS_DESCR

T5UC2.STEXT - Benefit Plan Statusdescription (lookup) NVARCSTR 10 0 0 yes

8 BENFT_PLAN_STATUS_ID T5UBA.PLSTA Benefit plan status NVARCSTR 2 0 0 yes


Lookup T5UC1. LTEXT - Plan TypeDescription NVARCSTR 20 0 0 yes

10 BENFT_PLAN_TYPE_ID PK T5UBA.PLTYP Plan type NVARCSTR 4 0 0 no

11 BENFT_PROVIDER_DESCR T51RT.CRETX: Benefit Provider NVARCSTR 30 0 0 yes

12 BENFT_PROVIDER_ID T5UBA.CRENR Benefit provider NVARCSTR 8 0 0 yes
















23 PROGRAM_GRP_ID_01 PK T5UBU.BENGR Employee benefit group NVARCSTR 4 0 0 no

24 PROGRAM_GRP_ID_02 PK T5UBU.BSTAT - Employee status NVARCSTR 4 0 0 no




27 VALID_FROM_DATE PK T5UBA.ENDDA End date DATETIME 24 0 9 no

28 VALID_TO_DATE PK T5UBA.BEGDA Start date DATETIME 24 0 9 no

29 VALID_TO_DATE_PREV T5UBA.BEGDA Start date - 1 DATETIME 24 0 9 yes

30 WAGE_TYPE_DESCR_EMPLEE

T512T.LGTXT - Long Wage Type Text forEmployee wage type contributions NVARCSTR 25 0 0 yes

31 WAGE_TYPE_DESCR_EMPLER

T512T.LGTXT - Long Wage Type Text forEmployer wage type contributions NVARCSTR 25 0 0 yes

32 WAGE_TYPE_ID_EMPLEE

T5UBA.EEWTY Wage type for employeecontributions NVARCSTR 4 0 0 yes

33 WAGE_TYPE_ID_EMPLER

T5UBA.ERWTY Wage type for employercontributions NVARCSTR 4 0 0 yes




Benefit Program grouping 1 and 2 descriptive attributes from T5UCT, T5UC9; load BENEFIT_PROGRAM_GROUP



Nullable


2 BENFT_AREA_ID PK T5UCT/T5UC9.BAREA Benefit area NVARCSTR 2 0 0 no



5 PROGRAM_CODE PK Hard-coded to 01 / 02 to distinguish betweenFirst and Second Program grouping NVARCSTR 2 0 0 no

6 PROGRAM_GRP_DESCR

T5UCT/T5UCT/T5UC9.LTEXT Benfit first /second program grouping text NVARCSTR 20 0 0 yes

7 PROGRAM_GRP_FULL_NAME

Concatenated: T5UCT/T5UC9.BENGRBenefitfirst/second program grouping +T5UCT/T5UCT/T5UC9.LTEXT Benfit first /second program grouping text

NVARCSTR 30 0 0 yes

8 PROGRAM_GRP_ID PK T5UCT/T5UC9.BENGRBenefit first/secondprogram grouping NVARCSTR 4 0 0 no




Benefit Spending account date-effective dimension from T5UBG; load BENEFIT_SPENDING_ACCOUNT dimension



Nullable





3 AMT_REIMBURSMNT_MIN

T5UBG.REMIN Minimum reimbursementamount DECIMAL 48 13 2 yes


5 BENFT_AREA_ID PK T5UBG.BAREA Benefit area NVARCSTR 2 0 0 yes


7 BENFT_PLAN_ID PK T5UBG.BPLAN Benefit plan NVARCSTR 4 0 0 yes



10 CURRENT_FLAG PK Set to 1 if the record is current INTEGER 4 0 0 yes




14 REIMBURSMNT_FLAG T5UBG.REIND Reimbursement indicator NVARCSTR 1 0 0 yes

15 SPENDNG_ACCT_KEY PK Surrogate key generated for

BENENFIT_SPENDING_ACCOUNT INTEGER 4 0 0 no

16 VALID_FROM_DATE PK T5UBG.ENDDA End date DATETIME 24 0 9 yes



17 VALID_TO_DATE PK T5UBG.BEGDA Start date DATETIME 24 0 9 yes

18 WAGE_TYPE_DESCR_REIMB T512T.LGTXT - Wage type text NVARCSTR 25 0 0 yes

19 WAGE_TYPE_ID_REIMB T5UBG.REWTY Reimburs. wage type NVARCSTR 4 0 0 yes


Benefit Termination Rule descriptive attributes from T5UEU; load BENEFIT_TERMINATION_RULE



Nullable


2 BENFT_AREA_ID PK T5UEU.BAREA Benefit area NVARCSTR 2 0 0 no



5 TERMINATN_RULE_DESCR T5UEU.LTEXT Text, 20 characters NVARCSTR 20 0 0 yes

6 TERMINATN_RULE_FULL_NAME

Concatenated: T5UEU.BTERM Benefittermination rule variant + T5UC3.LTEXT -lookup on Benefit Area description

NVARCSTR 30 0 0 yes

7 TERMINATN_RULE_ID PK T5UEU.BTERM Benefit termination rule variant NVARCSTR 4 0 0 no



BUSINESS_AREA

Business Areas - TGSB, TSGBT



Nullable

1 BUS_AREA_DESCR TGSBT-GTEXT-Business area description NVARCSTR 30 0 0 yes

2 BUS_AREA_FULL_NAME Business Area ID and Descritpion NVARCSTR 120 0 0 yes

3 BUS_AREA_ID PK TGSB-GSBER-Business area NVARCSTR 4 0 0 no



CERTIFICATE_TYPE

Employee certification type descriptive attributes from T519T load CERTIFICATE_TYPE dimension



Nullable

1 CERTIFICATE_TYPE_DESCR T519T.STEXT Certificate text NVARCSTR 40 0 0 yes

2 CERTIFICATE_TYPE_ID PK T519T.SLABS Certificate NVARCSTR 2 0 0 no





COMPANY_CODE

T001 - Company Code master



Nullable

1 ADDRESS_ID Company default address identifier NVARCSTR 10 0 0 yes

2 CHART_OF_ACCT_ID Company Code chart of accounts NVARCSTR 4 0 0 yes

3 CHART_OF_ACCT_ID_COUNTRY

Chart of Accounts according to countrylegislation NVARCSTR 4 0 0 yes

4 CHART_OF_ACCT_NAME Chart of Accounts Name NVARCSTR 50 0 0 yes

5 CITY Company City Name NVARCSTR 40 0 0 yes

6 CMPNY_CODE_FULL_NAME Company Code and Name NVARCSTR 120 0 0 yes

7 CMPNY_CODE_ID PK T001-BURKS - Company Code ID NVARCSTR 4 0 0 no

8 CMPNY_CODE_ID_ORIGINAL Original Key of Company Code NVARCSTR 4 0 0 yes

9 CMPNY_CODE_NAME Company Code Name NVARCSTR 40 0 0 yes

10 CMPNY_CODE_NAME_01 Name of the Company - 1st description NVARCSTR 40 0 0 yes

11 CMPNY_CODE_NAME_02 Name of the Company - 2nd description NVARCSTR 40 0 0 yes

12 CMPNY_CODE_NAME_03 Name of the Company - 3rd description NVARCSTR 40 0 0 yes

13 CMPNY_CODE_NAME_04 Name of the Company - 4th description NVARCSTR 40 0 0 yes

14 COUNTRY_ID Country Identifier NVARCSTR 3 0 0 yes

15 COUNTRY_NAME Country Name (lookup) NVARCSTR 15 0 0 yes

16 CR_CTRL_AREA_DESCR Credit Controlling Area description NVARCSTR 35 0 0 yes



17 CR_CTRL_AREA_ID Credit Control area NVARCSTR 4 0 0 yes

18 CURR_ID Company Code Currency ID NVARCSTR 5 0 0 yes

19 DISTRICT District of the Company NVARCSTR 40 0 0 yes

20 FAX Fax no of the Company NVARCSTR 40 0 0 yes

21 FIN_MGMT_AREA_ID Financial Management Area NVARCSTR 4 0 0 yes

22 FISC_YR_VARIANT_ID Company code fiscal year variant NVARCSTR 2 0 0 yes

23 FISC_YR_VARIANT_NAME Company code fiscal year variant name NVARCSTR 30 0 0 yes

24 HOUSE_NUMBER Company code house number NVARCSTR 10 0 0 yes

25 LANG_DESCR Company code language Description NVARCSTR 16 0 0 yes

26 LANG_ID Company Code default language NVARCSTR 1 0 0 yes



29 PHONE Company code telephone number NVARCSTR 30 0 0 yes

30 REGION_ID Company code region NVARCSTR 3 0 0 yes

31 REGION_NAME Company code region name NVARCSTR 20 0 0 yes

32 STREET Company code street name NVARCSTR 60 0 0 yes

33 TAX_JURISDIC_NUM Jurisdiction fo tax calculation - tax jurisdictioncode NVARCSTR 15 0 0 yes

34 VAT_REGISTRTN_NUM VAT regulation number NVARCSTR 20 0 0 yes



35 ZIP Company code postal code NVARCSTR 10 0 0 yes

CONTRIBUTION_RULE

Employee and Employer benefit contribution rule descriptive attributes from T74GE, T74GG; load CONTRIBUTION_RULE dimension



Nullable


2 BENFT_AREA_ID PK T74GE/T74GG.BAREA Benefit area NVARCSTR 2 0 0 no

3 BENFT_PLAN_DESCR Lookup PA0167.BOPTI description in T5UCA -Benefits Plan text NVARCSTR 30 0 0 yes

4 BENFT_PLAN_ID PK T74GE/T74GG.BPLAN Benefit plan NVARCSTR 4 0 0 no

5 CONTRIBTN_CODE PKHard-coded to EMPLER / EMPLEE todistinguish between First and Second Programgrouping

NVARCSTR 10 0 0 no

6 CONTRIBTN_RULE_DESCR

T74GE/T74GG.LTEXT Benefit employer /employeecontribution rule text NVARCSTR 20 0 0 yes

7 CONTRIBTN_RULE_FULL_NAME

Concatenated: T74GE/T74GG.ERCONEmployers benefits contribution variant +T74GE/T74GG.LTEXT Benefit employer /employeecontribution rule text

NVARCSTR 30 0 0 yes

8 CONTRIBTN_RULE_ID PK T74GE/T74GG.ERCON Employers benefitscontribution variant NVARCSTR 4 0 0 no





CONTROLLING_AREA

TKA01 - Controlling areas master



Nullable

1 CTRL_AREA_DESCR Controlling Area Name NVARCSTR 25 0 0 yes

2 CTRL_AREA_FULL_NAME Controlling Area DI and Desc NVARCSTR 120 0 0 yes

3 CTRL_AREA_ID PK TKA01-KORKS - Controlling Area ID NVARCSTR 4 0 0 no

4 CURR_ID Currency Code for Controlling Area NVARCSTR 5 0 0 yes

5 FISC_YR_VARIANT_ID Fiscal Year Variant NVARCSTR 2 0 0 yes

6 LEDGER_ID_PROFIT_CNTR Financial Ledger ID profit Center NVARCSTR 2 0 0 yes



9 OPERTNG_CONCERN_ID Operating Concern NVARCSTR 4 0 0 yes

10 PROFIT_CNTR_AREA Profit Center Group NVARCSTR 12 0 0 yes

11 STD_SET_HIER_CODE Standard Hierarchy for Cost Centers NVARCSTR 12 0 0 yes



COST_CENTER

CSKS - Cost Center Master



Nullable

1 ALT_FUNCTN CSKS.AFUNK - Alternative function of CostCenter NVARCSTR 3 0 0 yes

2 BUS_AREA_ID Business Area ID NVARCSTR 4 0 0 yes

3 CITY Cost Center City Name NVARCSTR 40 0 0 yes

4 CMPNY_CODE_ID Company Code ID NVARCSTR 4 0 0 yes

5 CMPNY_CODE_NAME Company code name associated with this CostCenter NVARCSTR 40 0 0 yes

6 COST_CNTR_DESCR Cost Center Descritpion NVARCSTR 60 0 0 yes

7 COST_CNTR_FULL_NAME Cost Center ID and Desc NVARCSTR 120 0 0 yes

8 COST_CNTR_ID PK CSKS-KOSTL - Cost Center ID NVARCSTR 10 0 0 no

9 COST_CNTR_ID_SUBSEQUENT CSKS.NKOST - Subsequent Cost Center ID NVARCSTR 10 0 0 yes

10 COST_CNTR_NAME Cost Center Default Name NVARCSTR 40 0 0 yes

11 COST_CNTR_NAME_01 Cost Center Name Line 1 NVARCSTR 40 0 0 yes




15 COUNTRY_ID Cost Center Country Code NVARCSTR 3 0 0 yes

16 COUNTRY_NAME Cost Center Country Name NVARCSTR 15 0 0 yes



17 CREATED_BY Person ID who created the record NVARCSTR 12 0 0 yes

18 CREATE_DATE Date when the record was created in thesource system DATETIME 24 0 9 yes

19 CTRL_AREA_DESCR Control Area description NVARCSTR 25 0 0 yes

20 CTRL_AREA_ID PK Controlling Area Identifier NVARCSTR 4 0 0 no

21 CURR_ID Cost Center Currency ID NVARCSTR 5 0 0 yes

22 DEPARTMENT CSKS.ABTEI - Department NVARCSTR 12 0 0 yes

23 DISTRICT Cost Center City District NVARCSTR 40 0 0 yes

24 EQUITY_TYPE_CODE CSKS.ETYPE - Equity type NVARCSTR 3 0 0 yes

25 FAX Cost Center fax number NVARCSTR 40 0 0 yes

26 FUNCTN_CODE CSKS.FUNKT - function of Cost Center NVARCSTR 3 0 0 yes



29 PERSON_IN_CHARGE CSKS.VERAK - Cost Center Manager NVARCSTR 20 0 0 yes

30 PHONE Cost Center phone # 1 NVARCSTR 30 0 0 yes

31 PROFIT_CNTR_DESCR Profit Center Description NVARCSTR 40 0 0 yes

32 PROFIT_CNTR_ID CSKS.PRCTR - Profit Center Code NVARCSTR 10 0 0 yes

33 REGION_ID Region ID NVARCSTR 3 0 0 yes

34 REGION_NAME Region name NVARCSTR 20 0 0 yes



35 STREET Cost Center Street name NVARCSTR 60 0 0 yes

36 TYPE_CODE Cost Center Type Identifier NVARCSTR 1 0 0 yes

37 VALID_FROM_DATE Record is valid to DATETIME 24 0 9 yes

38 VALID_TO_DATE Record Valid from DATETIME 24 0 9 yes

39 ZIP Cost Center ZIP code NVARCSTR 10 0 0 yes

COST_CENTER_HIER

Cost Center Hierarchy - CCSS-KOSTL - Cannot have a primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Cost Center Child description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no

3 CTRL_AREA_ID PK Controlling Area ID NVARCSTR 4 0 0 no

4 LEAF_FLAG PK Is Leaf NVARCSTR 1 0 0 no



7 PARENT_DESCR Cost Center parent descritpion NVARCSTR 64 0 0 yes

8 PARENT_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no

9 ROOT_FLAG PK Is Root NVARCSTR 1 0 0 no



COST_CENTER_HIER_BAD

CCSS-KOSTL Cost Hierarchy table with invalid records- cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Cost Center Child description NVARCSTR 64 0 0 yes

2 CHILD_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no


4 ETL_ERROR_ACTN Data Integrator Action on Error NVARCSTR 1 0 0 yes

5 ETL_ERROR_COLUMN Data Integrator Error message NVARCSTR 500 0 0 yes

6 LEAF_FLAG PK Is Leaf NVARCSTR 1 0 0 no



9 PARENT_DESCR Cost Center parent descritpion NVARCSTR 64 0 0 yes

10 PARENT_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no

11 ROOT_FLAG PK Is Root NVARCSTR 1 0 0 no



COST_CENTER_HIER_HZCCSS-KOSTL Cost Center hierarchy flattenned horizontally -- Cannot have a primary key on this table due to possible duplicate entries inSAP



Nullable

1 COST_CNTR_ID PK Cost Center ID (current node) NVARCSTR 12 0 0 no


3 LEAF_LVL Is Leaf Level INTEGER 4 0 0 no



6 LVL_00_DESCR Cost Center Root Node Description NVARCSTR 64 0 0 yes

7 LVL_00_FULL_NAME Cost Center ID and Desc for Level 0 NVARCSTR 120 0 0 yes

8 LVL_00_ID PK Cost Center root node ID NVARCSTR 12 0 0 no

9 LVL_01_DESCR Cost Center level 1 Node Description NVARCSTR 64 0 0 yes


11 LVL_01_ID PK Cost Center level 1 Node ID NVARCSTR 12 0 0 no


13 LVL_02_FULL_NAME Cost Center Id and Desc for Level 2 NVARCSTR 120 0 0 yes

















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













COST_CENTER_HIER_VR

CCSS-KOSTL - Cost Center Hierarchy vertically flattenned - cannot have primary key due to possible duplicate entries in SAP



Nullable

1 CHILD_DESCR Cost Center Child Node Description NVARCSTR 64 0 0 yes

2 CHILD_FULL_NAME Cost Center ID and Desc for the Child NVARCSTR 120 0 0 yes

3 CHILD_ID PK Cost Center Parent Node ID NVARCSTR 12 0 0 no


5 DEPTH Node depth level INTEGER 4 0 0 yes

6 LEAF_FLAG Is Leaf INTEGER 4 0 0 yes



9 PARENT_DESCR Cost Center Child Node Descritpion NVARCSTR 64 0 0 yes

10 PARENT_FULL_NAME Cost Center Parent ID and Desc NVARCSTR 120 0 0 yes

11 PARENT_ID PK Cost Center Child Node ID NVARCSTR 12 0 0 no

12 ROOT_FLAG Is Root INTEGER 4 0 0 yes



COUNTRY_GROUP

HR specific Country Grouping from T500L



Nullable

1 CLUSTER_CODE T500L.RELID - Area identification onimport/export database PCL2 NVARCSTR 2 0 0 yes

2 COUNTRY_CODE_ADMIN

T500L.RPLND - Personnel AdministrationCountry indicator NVARCSTR 1 0 0 yes

3 COUNTRY_GRP_DESCR

T500T.LTEXT - Designation for personnelcountry grouping NVARCSTR 25 0 0 yes

4 COUNTRY_GRP_ID PK T500T.MOLGA - Country Grouping for HR NVARCSTR 2 0 0 no

5 COUNTRY_ID T005.LAND1 Country key (lookup) NVARCSTR 3 0 0 yes

6 COUNTRY_ISO_CODE T500L.INTCA - Country ISO code NVARCSTR 2 0 0 yes

7 COUNTRY_NAME T005T.LANDX Country Name (lookup) NVARCSTR 15 0 0 yes





COUNTRY_GROUP_STATUSLoads country dependent status data from T505N, T509I, T505V, T505S. The output table is used later to look up definintions whichdepend on the employees country at the



Nullable

1 COUNTRY_GRP_ID PK MOLGA - Country grouping NVARCSTR 2 0 0 no



4 SOURCE_COLUMN_NAME PK Hard-coded column name from the source

table NVARCSTR 6 0 0 no

5 VALUE_CODE PK Country status codes NVARCSTR 2 0 0 no

6 VALUE_DESCR Country status value texts - length 25 NVARCSTR 25 0 0 yes



CURRENCY

TCURC, TCURT



Nullable

1 CURR_DECIMAL Lookup TCURX.CURRDEC - Number ofdecimals to display amounts in this currency. DECIMAL 48 28 0 yes

2 CURR_DESCR TCURT-LTEXT - Long Text NVARCSTR 60 0 0 yes

3 CURR_ID PK TCURC-WAERS - Currency Key NVARCSTR 5 0 0 no

4 CURR_ID_ALT TCURC-ALTWR - Alternative Key ForCurrencies NVARCSTR 3 0 0 yes

5 CURR_ISO_CODE TCURC-ISOCD - ISO Currency Code NVARCSTR 3 0 0 yes

6 DISPLAY_FACTORMultiply currency amounts by this factor todisplay with correct number of decimals for thecurrency

DECIMAL 48 17 14 yes



9 VALID_TO_DATE TCURC-GDATU -Date Up Until Which TheCurrency Is Valid DATETIME 24 0 9 yes



DATE_VALID_DRIVER

Temporary table to hold unique beginning and ending dates of all employee events/positon/job/etc date-effective records being merged



Nullable


2 EXTRACT_DATE Date when the record was loaded DATETIME 24 0 9 yes



5 RECORD_ID PKAdditional column to include in the joiningcondition (like ORG_UNIT_ID in Line ManagerHierarchy)

NVARCSTR 60 0 0 no

6 RECORD_MERGE_KEY PK

Union of Personnel number (PERSON_ID)from Date-Effective dimensions and infotypetables

NVARCSTR 8 0 0 no

7 VALID_FROM_DATE PK Beginning date of records that have changedfor this employee during this load DATETIME 24 0 9 no

8 VALID_TO_DATE End date of records that have changed for thisemployee during this load DATETIME 24 0 9 yes

DATE_VALID_FROM_DIMENSIONIntermediate table used internally to hold sorted beginning dates to build temp DATE_DRIVER table; stores date effective records derivedfrom dimensions - POSITION, JOB,



Nullable




Union of Personnel number (PERSON_ID)from Date-Effective dimensions and infotypetables

NVARCSTR 8 0 0 no

4 VALID_FROM_DATE PK BEGDA Start date DATETIME 24 0 9 no

5 VALID_TO_DATE PK ENDDA End date DATETIME 24 0 9 no



DATE_VALID_FROM_STAGEIntermediate table used internally to hold sorted beginning dates to build temp DATE_DRIVER table; used to perfrom distinct merge ofdate-effecitve records from multiple



Nullable



3 RECORD_ID PKAdditional column to include in the joiningcondition (like ORG_UNIT_ID in Line ManagerHierarchy). If not used, set to$G_DEFAULT_TEXT

NVARCSTR 60 0 0 no


Union of Position number (POSITION_ID)from Date-Effective dimensions and infotypetables

NVARCSTR 8 0 0 no

5 SOURCE_TABLE_NAME Identifies which infotype this data comes from NVARCSTR 60 0 0 yes

6 VALID_FROM_DATE PK BEGDA Start date DATETIME 24 0 9 no

7 VALID_TO_DATE PK ENDDA End date DATETIME 24 0 9 no



DEPENDENT_COVERAGE

Benefit dependent coverage descriptive attributes from T5UBF, T5UCF; load DEPENDENT_COVERAGE dimension



Nullable


2 BENFT_AREA_ID PK T5UBF.BAREA Benefit area NVARCSTR 2 0 0 no

3 COUNT_BENEFIC_DEPENDNT_MAX

T5UBF.NODEP Benefit Maximum Number ofDependents INTEGER 4 0 0 yes

4 COUNT_BENEFIC_DEPENDNT_MIN

T5UBF.MIDEP Benefits Minimum Number ofDependents- - avaiable in ECC 5 and higheronly

INTEGER 4 0 0 yes

5 DEPENDNT_COVERAGE_DESCR T5UCF.LTEXT Text (20 characters) NVARCSTR 20 0 0 yes

6 DEPENDNT_COVERAGE_FULL_NAME

Concatenated: T5UBF.DEPCV BenefitDependent Coverage + T5UCF.LTEXT Text(20 characters)

NVARCSTR 30 0 0 yes

7 DEPENDNT_COVERAGE_ID PK T5UBF.DEPCV Benefit Dependent Coverage NVARCSTR 4 0 0 no



EDUCATION_TYPE

Education type descriptive attributes from T518B load EDUCATION_TYPE dimension



Nullable

1 EDUCATN_TYPE_DESCR T518B.ATEXT Educ./train. text NVARCSTR 40 0 0 yes

2 EDUCATN_TYPE_ID PK T518B.AUSBI Education/training NVARCSTR 8 0 0 no





ELIGIBILITY_RULE

Benefit eligibility rule descriptive attributes from T5UCV; load ELIGIBILITY_RULE dimension



Nullable


2 BENFT_AREA_ID PK T5UCV.BAREA Benefit area NVARCSTR 2 0 0 no

3 ELIGIBLTY_RULE_DESCR T5UCV.LTEXT Text, 20 characters NVARCSTR 20 0 0 yes

4 ELIGIBLTY_RULE_FULL_NAME

Concatenated: T5UCV.BELIG Benefit eligibilityrule variant + T5UCV.LTEXT Text, 20characters

NVARCSTR 30 0 0 yes

5 ELIGIBLTY_RULE_ID PK T5UCV.BELIG Benefit eligibility rule variant NVARCSTR 4 0 0 no





EMPLOYEE

Employee personal date-effective information from Personal and Address infotypes (PA0002, PA0006)



Nullable

1 BIRTH_COUNTRY PA0002.GBLND Country of birth NVARCSTR 3 0 0 yes

2 BIRTH_DATE PA0002.GBDAT Date of birth (basic) - used forcalculation of Age, etc DATETIME 24 0 9 yes

3 BIRTH_DATE_PASSPORT PA0002.GBPAS Date of birth acc.to passport DATETIME 24 0 9 yes

4 BIRTH_PLACE PA0002.GBORT Birthplace NVARCSTR 40 0 0 yes

5 BIRTH_STATE PA0002.GBDEP State NVARCSTR 3 0 0 yes

6 BUS_ROUTE_CODE PA0006.BUSRT Bus route NVARCSTR 3 0 0 yes

7 CITY PA0006.ORT01 City NVARCSTR 40 0 0 yes

8 CMPNY_APARTMNT_FLAG PA0006.WKWNG Company-owned apartment INTEGER 4 0 0 yes

9 CONTACT_NAME PA0006.NAME2 C/O name (in care of) -Contact name NVARCSTR 40 0 0 yes

10 CONTACT_PHONE PA0006.TELNR Telephone number of thecontact NVARCSTR 14 0 0 yes

11 COUNTRY_ID PA0006.LAND1 Country key - Address NVARCSTR 3 0 0 yes

12 COUNTRY_NAME T005T.LANDX - Country Descr(lookup) NVARCSTR 15 0 0 yes

13 COUNTY_ID PA0006.COUNC County code NVARCSTR 3 0 0 yes

14 COUNTY_NAME T005F.BEZEI - County Descr(lookup) NVARCSTR 20 0 0 yes


16 DAY_BIRTH PA0002.GBTAG Birth date (to month/year) -day INTEGER 4 0 0 yes



17 DISTANCE_KM PA0006.ENTKM Distance in kilometers INTEGER 4 0 0 yes

18 DISTRICT PA0006.ORT02 District NVARCSTR 40 0 0 yes

19 EMPLOYEE_KEY PK Surrogate key generated for EMPLOYEEdimension (date-effective records) DECIMAL 48 28 0 no

20 FAX PA0105.USRID Communication ID/number(Fax comm type) NVARCSTR 30 0 0 yes

21 FIRST_NAME PA0002.VORNA First name NVARCSTR 40 0 0 yes

22 FIRST_NAME_SEARCH PA0002.VNAMC First name (matchcode field) NVARCSTR 25 0 0 yes

23 FULL_NAME PA0002.CNAME Complete Name NVARCSTR 80 0 0 yes

24 FULL_NAME_MIXED PA0002.NCHMC + PA0002.VNAMC Last andFirst name (matchcode field) in Mixed case NVARCSTR 60 0 0 yes

25 FULL_NAME_UPPER PA0002.NCHMC + PA0002.VNAMC Last andFirst name (matchcode field) in Upper case NVARCSTR 60 0 0 yes

26 GENDER_DESCR DD07T.DDTEXT Lookup description forGESCH in DD07T NVARCSTR 10 0 0 yes

27 GENDER_ID PA0002.GESCH Gender key NVARCSTR 1 0 0 yes

28 HOUSE_NUMBER PA0006.HSNMR House Number NVARCSTR 10 0 0 yes

29 IDENTIFICTN_NUM PA0002.PERID Personal ID number (SSN,Tax ID) NVARCSTR 20 0 0 yes

30 INITIALS PA0002.INITS Employees initials NVARCSTR 10 0 0 yes

31 INTERNET PA0105.USRID Communication ID/number(Internet Communication Type) NVARCSTR 30 0 0 yes

32 LANG_DESCR T002T.SPTXT - Lookup on Languagedescritpion NVARCSTR 16 0 0 yes

33 LANG_ID PA0002.SPRSL Language key NVARCSTR 1 0 0 yes

34 LAST_NAME PA0002.NACHN Last name NVARCSTR 40 0 0 yes



35 LAST_NAME_BIRTH PA0002.NAME2 2nd surname / name at birth NVARCSTR 40 0 0 yes

36 LAST_NAME_SEARCH PA0002.NCHMC Last name (matchcode field) NVARCSTR 25 0 0 yes



39 MARITAL_STATUS_DESCR

T502T. FTEXT - Lookup on Marital statusdescritpion NVARCSTR 50 0 0 yes

40 MARITAL_STATUS_ID PA0002.FAMST Marital status key NVARCSTR 1 0 0 yes

41 MIDDLE_NAME PA0002.MIDNM Middle Name NVARCSTR 40 0 0 yes

42 MONTH_BIRTH PA0002.GBMON Month of birth INTEGER 4 0 0 yes

43 MULTIPLE_NATIONALITY_FLAG Set to 1 if Employee has multiple nationalities INTEGER 4 0 0 yes

44 MUNICPL_CITY_CODE PA0006.RCTVC Municipal city code NVARCSTR 6 0 0 yes

45 NATIONALITY_DESCR_01

T005T.NATIO - Lookup on Nationalitydescritpion NVARCSTR 15 0 0 yes


T005T. NATIO - Seconde Nationality Textlookup NVARCSTR 15 0 0 yes

47 NATIONALITY_DESCR_03 T005T.NATIO -Third Nationality Text lookup NVARCSTR 15 0 0 yes

48 NATIONALITY_ID_01 PA0002.NATIO Country of the First Nationality NVARCSTR 3 0 0 yes

49 NATIONALITY_ID_02 PA0002.NATI2 Second nationality Country NVARCSTR 3 0 0 yes

50 NATIONALITY_ID_03 PA0002.NATI3 Third nationality Country NVARCSTR 3 0 0 yes

51 NICKNAME PA0002.RUFNM Known as NVARCSTR 40 0 0 yes

52 NUM_OF_CHILDREN PA0002.ANZKD Number of children INTEGER 4 0 0 yes



53 PERSON_ID PKUnion of Personnel number (PERSON_ID)from Date-Effective dimensions and infotypetables

NVARCSTR 8 0 0 yes

54 PHONE PA0006.TELNR Telephone number NVARCSTR 14 0 0 yes

55 PREFIX_NAME_01 PA0002.VORSW Name Prefix NVARCSTR 15 0 0 yes

56 PREFIX_NAME_02 PA0002.VORS2 Second name prefix NVARCSTR 15 0 0 yes

57 REGION_ID PA0006.STATE Region (State, Province,County) NVARCSTR 3 0 0 yes

58 REGION_NAME T005U.BEZEI - Region (state) Descr(lookup) NVARCSTR 20 0 0 yes

59 RELATIONSHIP_DESCR

T577S.ATEXT - Relationship Descr(lookup);Family Characteristis = A NVARCSTR 20 0 0 yes

60 RELIGION_CODET516T.KTEXT - Lookup on ReligiousDenomination as it is displayed during dataentry

NVARCSTR 4 0 0 yes

61 RELIGION_DESCR T516T.KTEXT - Lookup on ReligiousDenomination descritpion NVARCSTR 25 0 0 yes

62 RELIGION_ID PA0002.KONFE Religious denomination key NVARCSTR 2 0 0 yes

63 STREET PA0006.STRAS Street and house number NVARCSTR 60 0 0 yes

64 TITLE_01 T522T. ATEXT - Lookup on Form of Address(Title) descritpion NVARCSTR 5 0 0 yes

65 TITLE_02 PA0002.TITL2 Second title NVARCSTR 15 0 0 yes

66 TITLE_ACADEMIC PA0002.TITEL Title NVARCSTR 15 0 0 yes

67 TITLE_OTHER PA0002.NAMZU Title NVARCSTR 15 0 0 yes

68 VALID_FROM_DATE PK PA0002/PA0006.BEGDA - Beginning date ofrecords DATETIME 24 0 9 yes

69 VALID_FROM_DATE_ADDRESS PA0006.BEGDA From DATETIME 24 0 9 yes

70 VALID_FROM_DATE_MARITAL

PA0002.FAMDT Validity begin date for currentmarital status DATETIME 24 0 9 yes



71 VALID_FROM_DATE_PERSNL PA0002.BEGDA From DATETIME 24 0 9 yes

72 VALID_TO_DATE PK PA0002/PA0006.ENDDA - Ending date ofrecords DATETIME 24 0 9 yes

73 VALID_TO_DATE_ADDRESS PA0006.ENDDA To DATETIME 24 0 9 yes

74 VALID_TO_DATE_PERSNL PA0002.ENDDA To DATETIME 24 0 9 yes


76 VOICEMAIL PA0105.USRID Communication ID/number(Voicemail communication type) NVARCSTR 30 0 0 yes

77 YEARS_AGE Calculated Age as of Load Date DECIMAL 48 5 2 yes

78 YEAR_BIRTH PA0002.GBJHR Year of birth INTEGER 4 0 0 yes

79 YEAR_MONTH_BIRTH PA0002.GBJHR + PA0002.GBMON -concatenated Year and Month of birth NVARCSTR 10 0 0 yes

80 YEAR_MONTH_DAY_BIRTH

PA0002.GBJHR + PA0002.GBMON+PA002.GBTAG concatenated Year, Montrand Day of birth

NVARCSTR 16 0 0 yes

81 ZIP PA0006.PSTLZ Postal code NVARCSTR 10 0 0 yes



EMPLOYEE_ADMIN_0000_STAGELimit number of subtypes avaiable in PA0000 (Events) to a single default School type; It is used to loadEMPLOYEE_ADMINISTRATION_FACT



Nullable

1 ACTION_REASON_DESCR

T530T. MGTXT - Description for ActionReason (lookup) NVARCSTR 30 0 0 yes

2 ACTION_REASON_ID PA0000.MASSG Reason for action NVARCSTR 2 0 0 yes

3 ACTION_SELECT_FLAG

Set to 1 if the status is one of pre-definedRapid Mart Variables: $G_HIRE_ACTION_01 -03, $G_TERMINATION_ACTION,$G_REHIRE_ACTION_01 - 02,$G_RETIRE_ACTION

DECIMAL 48 28 0 yes

4 ACTION_TYPE_DESCR

T529T. MNTXT -Action Type description(lookup) NVARCSTR 30 0 0 yes

5 ACTION_TYPE_ID PA0000.MASSN Action type NVARCSTR 2 0 0 yes



8 CUSTOM_STATUS_DESCR

T529U. TEXT1 -User-defined statusdescription (lookup) NVARCSTR 40 0 0 yes

9 CUSTOM_STATUS_ID PA0000.STAT1 User-defined status NVARCSTR 1 0 0 yes

10 DEPARTURE_DATE PA0000.BEGDA - Start date for TerminationAction DATETIME 24 0 9 yes

11 EMPLMNT_STATUS_DESCR

T529U. TEXT1 -Employment status description(lookup) NVARCSTR 40 0 0 yes

12 EMPLMNT_STATUS_ID PA0000.STAT2 Employment status NVARCSTR 1 0 0 yes


14 INFOTYPE_ID Hard-coded - SAP source table name toPA0000 NVARCSTR 6 0 0 yes





17 ORIGINAL_HIRE_DATE

PA0000.BEGDA - Start date for Hire actions(1-3) DATETIME 24 0 9 yes


19 REHIRE_DATE PA0000.BEGDA - Start date for re-Hire actions(1-2) DATETIME 24 0 9 yes

20 RETIREMNT_DATE PA0000.BEGDA - Start date for RetirementAction DATETIME 24 0 9 yes

21 SPECL_PAYMNT_STATUS_DESCR

T529U. TEXT1 -Special Payment statusdescription (lookup) NVARCSTR 40 0 0 yes

22 SPECL_PAYMNT_STATUS_ID PA0000.STAT3 Special payment status NVARCSTR 1 0 0 yes


24 VALID_TO_DATE PK PA0022.ENDDA End Date DATETIME 24 0 9 no



EMPLOYEE_ADMINISTRATION_FACTMerged employee demographics (administration) data from multiple infotypes (PA0001, PA0000, PA0002, PA0007, PA0008, PA0016,PA0024, PA0077, PA0094, PA0041, PA0022, PA0019



Nullable

1 ACTION_REASON_ID PA0000.MASSG Reason for action NVARCSTR 2 0 0 no

2 ACTION_REASON_ID_DEPARTURE

PA0000.MASSN - Action Reason id (for$G_TERMINATION_ACTION) NVARCSTR 50 0 0 no

3 ACTION_TYPE_ID PA0000.MASSN Action type NVARCSTR 2 0 0 no

4 ACTION_TYPE_ID_DEPARTURE

PA0000.MASSN - Action Type id (for$G_TERMINATION_ACTION) NVARCSTR 50 0 0 no

5 ACTIVE_EMPLOYEE_FLAG

PA0001.PERSG Set to 1 for the employeegroup value 1 = Active INTEGER 4 0 0 yes

6 ADMIN_GRP_CODE PA0001.SBMOD Administrator group NVARCSTR 4 0 0 no

7 ADMIN_ID_HR PA0001.SACHP Administrator for HR masterdata NVARCSTR 3 0 0 no

8 ADMIN_ID_PAYROLL PA0001.SACHA Payroll administrator NVARCSTR 3 0 0 no

9 ADMIN_ID_TIME PA0001.SACHZ Administrator for timerecording NVARCSTR 3 0 0 no

10 AMT_COST_EDUCATN PA0022.JBEZ1 Course fees DECIMAL 48 11 2 yes

11 AMT_PAYMNT_01 PA0008.BET01 Wage type 01 amount forpayments DECIMAL 48 13 2 yes




15 AMT_POSTTAX_SAVNG


16 AMT_PRETAX_SAVNG




17 AMT_SALARY_YR PA0008.ANSAL Annual salary DECIMAL 48 15 2 yes

18 AMT_SALARY_YR_PREV

HR_INFOTYPE_0008_PAY.AMT_SALARY_YR Previous salary lookup DECIMAL 48 15 2 yes

19 BENFT_AREA_ID PA0169.BAREA - Benefit area NVARCSTR 2 0 0 no

20 BENFT_PLAN_ID PA0169.BPLAN - Benefit plan NVARCSTR 4 0 0 no

21 BENFT_PLAN_KEY Lookup on Benefit Plan dimension surrogatekey DECIMAL 48 28 0 no

22 BENFT_PLAN_TYPE_ID PA0169.PLTYP - Benefit plan type NVARCSTR 4 0 0 yes

23 BIRTH_DATE PA0002.GBDAT Date of birth (basic) - used forcalculation of Age, etc DATETIME 24 0 9 no

24 BUS_AREA_ID PA0001.GSBER Business area NVARCSTR 4 0 0 no


26 CAPACITY_UTILIZTN_LVL PA0008.BSGRD Capacity utilization level DECIMAL 48 5 2 yes

27 CERTIFICATE_TYPE_ID PA0022.SLABS Certificate NVARCSTR 2 0 0 no

28 CMPNY_CODE_ID PA0001.BUKRS Company code NVARCSTR 4 0 0 no

29 CONTRACT_ID PA0001.ANSVH Work contract (grouping forstatistical reporting) NVARCSTR 2 0 0 no

30 CONTRACT_NUM PA0016.CTNUM Contract number NVARCSTR 20 0 0 yes

31 CONTRACT_TYPE_ID PA0016.CTTYP Contract type NVARCSTR 2 0 0 no


T74FD. EECON Benefits employeecontribution rule NVARCSTR 4 0 0 no

33 CONTRIBTN_RULE_ID_EMPLER T74FD.ERCON - Employer contribution rule NVARCSTR 4 0 0 no

34 COST_CNTR_ID PA0001.KOSTL Cost center NVARCSTR 10 0 0 no



35 COST_OF_LVNG_ALLOWANCE_LVL PA0008.ORZST Cost of living allowance level NVARCSTR 2 0 0 yes

36 COUNTRY_GRP_ID T500P.MOLGA - Country Name - LookupMOLGA from T500P NVARCSTR 2 0 0 no


38 COUNT_EMPLEE_SVC_INTERVAL_01

Count of Employees with length of servicewithin Interval 1 DECIMAL 48 28 0 yes











44 COUNT_EMPLEE_SVC_UNKNOWN

Count of Employees where length of service isnot known (Employee Original Hire Date ismissing).

DECIMAL 48 28 0 yes

45 COURSE_NAME PA0022.KSBEZ Course name NVARCSTR 25 0 0 yes

46 CTRL_AREA_ID PA0001.KOKRS Controlling area NVARCSTR 4 0 0 no


48 CURR_ID PA0008.WAERS Currency key NVARCSTR 5 0 0 no

49 CURR_ID_BENFT PA0169.CURRE Benefit currency key NVARCSTR 5 0 0 yes

50 CURR_ID_EDUCATN PA0022.WAERS Currency Key NVARCSTR 5 0 0 yes

51 CURR_ID_SALARY_PREV

HR_INFOTYPE_0008_PAY.CURR_ID_SALARY lookup Previous currency NVARCSTR 5 0 0 yes

52 DATE_01 PA0041.DAT01 Date for date type 01 DATETIME 24 0 9 yes





55 DATE_TYPE_DESCR_01

Lookup T548T.DTEXT - Lookup date text forDate Type 01 NVARCSTR 20 0 0 yes


Lookup T548T.DTEXT - Lookup date text fordate type 02 NVARCSTR 20 0 0 yes



58 DATE_TYPE_ID_01 PA0041.DAR01 Date type 01 NVARCSTR 2 0 0 no



61 DAYS_OF_SERVICE Days of service as of current date DECIMAL 48 28 0 yes

62 DAYS_WEEK PA0007.WKWDY Weekly working days INTEGER 4 0 0 yes


64 DEDUCTN_OR_REF_01

PA0008.OPK01 Operation indicator for wagetypes 01 (DEDUCT/REFER) NVARCSTR 10 0 0 yes






68 DISABILITY_DATE PA0077.DISDT Date of determination ofdisability status DATETIME 24 0 9 yes

69 DISABILITY_FLAG PA0077.DISAB Person is disabled INTEGER 4 0 0 yes

70 DYNAMIC_SCHED_FLAG

PA0007.DYSCH Create dynamic daily workschedule DECIMAL 48 10 2 yes



71 EDUCATN_TYPE_ID PA0022.AUSBI Education/training NVARCSTR 8 0 0 no

72 EEO_EXEMPT_FLAG PA0077.EEOEX EEO Exempt Indicator INTEGER 4 0 0 yes

73 ELIGIBLTY_RULE_ID T5UBU.BELIG - Eligibility rule NVARCSTR 4 0 0 no

74 EMPLOYEE_GRP_ID PA0001.PERSG Employee group NVARCSTR 1 0 0 no

75 EMPLOYEE_KEY Lookup on EMPLOYEE dimension surrogateprimary key DECIMAL 48 28 0 no

76 EMPLOYEE_KEY_MGR

EMPLOYEE.EMPLOYEE_KEY - lookup onsurrogate key for Employee dimension DECIMAL 48 28 0 no

77 EMPLOYEE_SUBGRP_CAP_CODE

T503.TRFKZ - EE subgroup grouping forcollective agreement provision (lookup):1 = Industrial workers/hourly wages2 = Industrial workers/monthly wages3 = Salaried em

NVARCSTR 1 0 0 yes

78 EMPLOYEE_SUBGRP_ID PA0001.PERSK Employee subgroup NVARCSTR 2 0 0 no

79 END_DATE PA0016.CTEDT Contract end date DATETIME 24 0 9 yes

80 ENTRY_DATE PA0016.EINDT Initial entry DATETIME 24 0 9 yes

81 ETHNIC_ORIGIN_ID PA0077.RACKY Ethnic origin NVARCSTR 2 0 0 no

82 EXPIRATN_DATE PA0016.ARBER Expiration date of work permit DATETIME 24 0 9 yes

83 FINAL_GRADE PA0022.EMARK Final Mark NVARCSTR 4 0 0 yes



86 FULL_NAME_MIXED PA0001.ENAME Formatted name of employeeor applicant (Mixed case) NVARCSTR 40 0 0 yes

87 FULL_NAME_UPPER PA0001.SNAME Employees name (can besorted acc.LAST NAME FIRST NAME) NVARCSTR 30 0 0 yes

88 FULL_OR_PART_TIME If PA0007.WOSTD = 100% then FULL elsePART NVARCSTR 4 0 0 yes



89 GENDER_ID PA0002.GESCH Gender key NVARCSTR 1 0 0 no

90 HOLIDAY_CALENDAR_ID T001P.MOFID Public holiday calendar ID NVARCSTR 2 0 0 no

91 HOURS_DAY PA0007.ARBST Daily working hours DECIMAL 48 5 2 yes

92 HOURS_DAY_MAX PA0007.MAXTA Maximum number of workhours per day DECIMAL 48 5 2 yes

93 HOURS_DAY_MIN PA0007.MINTA Minimum number of workhours per day DECIMAL 48 5 2 yes

94 HOURS_MONTH PA0007.MOSTD Monthly hours DECIMAL 48 5 2 yes

95 HOURS_MONTH_MAX PA0007.MAXMO Maximum number of workhours per month DECIMAL 48 5 2 yes

96 HOURS_MONTH_MIN PA0007.MINMO Minimum number of workhours per month DECIMAL 48 5 2 yes

97 HOURS_WEEK PA0007.WOSTD Weekly hours DECIMAL 48 5 2 yes

98 HOURS_WEEK_MAX PA0007.MAXWO Maximum number of workhours per week DECIMAL 48 5 2 yes

99 HOURS_WEEK_MIN PA0007.MINWO Minimum weekly workinghours DECIMAL 48 5 2 yes

100 HOURS_WORK PA0008.DIVGV Hours worked per accountingperiod DECIMAL 48 5 2 yes

101 HOURS_YEAR PA0007.JRSTD Annual working hours DECIMAL 48 7 2 yes

102 HOURS_YEAR_MAX PA0007.MAXJA Maximum number of workhours per year DECIMAL 48 7 2 yes

103 HOURS_YEAR_MIN PA0007.MINJA Minimum number of workhours per year DECIMAL 48 7 2 yes

104 IDENTIFICTN_EXPIRE_DATE PA0094.EXPID ID expiry date DATETIME 24 0 9 yes

105 IDENTIFICTN_ISSUE_DATE PA0094.DATE1 Date of issue for personal ID DATETIME 24 0 9 yes




107 IDENTIFICTN_TYPE_ID

PA0094.FPNCD Personal ID and work permit(USA) NVARCSTR 2 0 0 no

108 INVESTMNT_GRP_ID T74FD.INVGR - Savings plans investmentgroup NVARCSTR 4 0 0 no

109 INVESTMNT_PLAN_ID_01 PA0169.INV01 Investments for savings plans NVARCSTR 4 0 0 no




113 JOB_KEY Lookup on JOB_KEY in JOB dimension DECIMAL 48 28 0 no

114 LANG_ID PA0002.SPRSL Language key NVARCSTR 1 0 0 no





119 MARITAL_STATUS_ID PA0002.FAMST Marital status key NVARCSTR 1 0 0 no

120 MEDICARE_FLAG PA0077.MEDIC Medicare indicator INTEGER 4 0 0 yes

121 MILITARY_STATUS_ID PA0077.MILSA Military status NVARCSTR 2 0 0 no

122 MONTHS_OF_SERVICE Months of service as of current date DECIMAL 48 8 2 yes


124 MULTIPLE_NATIONALITY_FLAG Set to 1 if Employee has multiple nationalities INTEGER 4 0 0 yes



125 NATIONALITY_ID PA0002.NATIO Country of the First Nationality NVARCSTR 3 0 0 no

126 NEXT_INCREASE_DATE PA0008.STVOR Date of next increase DATETIME 24 0 9 yes

127 NOTIFICTN_DATE PA0077.DISLE Date employer learned ofdisability status DATETIME 24 0 9 yes

128 ORG_KEY_ID PA0001.VDSK1 Organizational key NVARCSTR 14 0 0 no


130 ORG_UNIT_ID_PREV Lookup on PA0001.ORGEH for previousrecord) NVARCSTR 250 0 0 yes

131 ORG_UNIT_KEY Lookup on ORG_UNIT_KEY inORGANIZATION_UNIT dimension DECIMAL 48 28 0 no


PA0000.BEGDA - Start date for Hire actions(1-3); if there are not record; it is selected asVALID_FROM_DATE_EMPL (EmployeeDimension Valid From Date) or ContractInfotyp

DATETIME 24 0 9 no


134 PARTTIME_FLAG PA0007.TEILK Checkbox for part-timeemployee (1/0) INTEGER 4 0 0 yes

135 PAYROLL_AREA_ID PA0001.ABKRS Payroll area NVARCSTR 2 0 0 no

136 PAY_SCALE_AREA_ID PA0008.TRFGB Pay scale area NVARCSTR 2 0 0 no

137 PAY_SCALE_GRP_CODE PA0008.TRFGR Pay scale group NVARCSTR 8 0 0 yes

138 PAY_SCALE_LVL PA0008.TRFST Pay scale level NVARCSTR 2 0 0 yes

139 PAY_SCALE_TYPE_ID PA0008.AEDTM Pay scale type NVARCSTR 2 0 0 no

140 PERSONNEL_AREA_ID PA0001.WERKS Personnel area NVARCSTR 4 0 0 no

141 PERSONNEL_SUBAREA_ID PA0001.BTRT Personnel subarea NVARCSTR 4 0 0 no


NVARCSTR 8 0 0 no



143 PERSON_ID_MGR Lookup on PERSION_ID inLINE_MANAGER_HIER dimension NVARCSTR 8 0 0 yes



NVARCSTR 8 0 0 yes


146 POSITION_KEY Lookup on POSITION_KEY in POSITIONdimension DECIMAL 48 28 0 no








152 PRCNT_SALARY_INCRSE_ANNUAL

Percent increase (or decrease) of annualsalary on BEGIN_DATE versus one year ago DECIMAL 48 9 2 yes

153 PROBATION_END_DATE

PA0019.TERMN - Date/deadline for task typeset to $G_TASK_TYPE_PROBATION_END DATETIME 24 0 9 yes

154 PROFICIENCY_ID PA0024.AUSPR Proficiency of aQualification/Requirement NVARCSTR 4 0 0 no

155 PROGRAM_GRP_ID_01 PA0169.BENGR - Employee benefit first group NVARCSTR 4 0 0 no

156 PROGRAM_GRP_ID_02 PA0169.BSTAT - Benefit Program Grouping 2 NVARCSTR 4 0 0 no

157 QTY_DURATN_EDUCATN PA0022.ANZKL Duration of training course INTEGER 4 0 0 yes

158 QTY_UNIT_01 PA0008.ANZ01 an amount or number (andalso a unit) for wage type 01 DECIMAL 48 7 2 yes

159 QTY_UNIT_02 PA0008.ANZ02 Number Wage Type 02 DECIMAL 48 7 2 yes

160 QTY_UNIT_03 PA0008.ANZ03 Number for Wage type 03 DECIMAL 48 7 2 yes



161 QUALIFICTN_ID PA0024.QUALI Qualification key NVARCSTR 8 0 0 no



164 REMINDER_DATE PA0019.MNDAT Reminder date DATETIME 24 0 9 yes

165 RESIDENCE_STATUS_ID PA0094.RESIS Residence status NVARCSTR 1 0 0 yes


167 SALARY_DATE_PREV PA0008.BEGDA Date of the previous salary DATETIME 24 0 9 yes

168 SALARY_RANGE_KEY Lookup on Salary Range ID DECIMAL 48 28 0 no

169 SAVNG_401K_FLAG Calculated from PA0169.SUBTY - 1 indicates401K participation INTEGER 4 0 0 yes

170 SCHOOL_TYPE_ID PA0022.SLART Educational establishment NVARCSTR 2 0 0 no

171 SERVICE_INTERVAL_ID

Foreight Key to SERVICE_INTERVAL_HRtable DECIMAL 48 28 0 yes

172 START_DATE PA0016.CTBEG Start of contract DATETIME 24 0 9 yes



174 STATUS_CATEG_ID_EMPLMNT

T529U.STATN Status number (Categoryidentifier) for Employment; hard-coded to 2 NVARCSTR 1 0 0 yes

175 STATUS_ID_EMPLMNT

PA0000.STAT2 Employment (personnel action)status NVARCSTR 1 0 0 no

176 STUDY_BRANCH_ID PA0022.SLTP1 Branch of study NVARCSTR 5 0 0 no

177 TASK_DATE PA0019.TERMN Date/deadline DATETIME 24 0 9 yes

178 TASK_STATUS_ID PA0019.BVMRK Processing indicator(personnel task Status) NVARCSTR 1 0 0 no



179 TASK_TYPE_ID PA0019.TMART TASK type NVARCSTR 2 0 0 no

180 TERMINATN_RULE_ID T5UBU.BTERM - Benefits termination rule NVARCSTR 4 0 0 no

181 TIME_MGMT_STATUS_ID

PA0007.ZTERF Employee status for TimeManagement NVARCSTR 1 0 0 no

182 UOT_ID_01 PA0008.EIN01 Unit of time/measurement forWage type 01 NVARCSTR 3 0 0 no

183 UOT_ID_02 PA0008.EIN02 Unit of time/measurement forWage Type 02 NVARCSTR 3 0 0 no

184 UOT_ID_03 PA0008.EIN03 Unit of time/measurement forWage Type03 NVARCSTR 3 0 0 no

185 UOT_ID_EDUCATN PA0022.ANZEH Unit of time/measurement NVARCSTR 3 0 0 no


187 VALID_FROM_DATE_ACTION PA0000.BEGDA Start date (Event/Action) DATETIME 24 0 9 yes

188 VALID_FROM_DATE_ASSIGN PA0001.BEGDA Start date for PA0001 DATETIME 24 0 9 yes

189 VALID_FROM_DATE_BENFT

PA0169.BEGDA - Start date for Savingsplanned infotype DATETIME 24 0 9 yes

190 VALID_FROM_DATE_CONTRACT

PA0016.BEGDA Start Date for Contractinfotype DATETIME 24 0 9 yes

191 VALID_FROM_DATE_DATES

PA0019.BEGDA From for Monitoring datesinfotype DATETIME 24 0 9 yes

192 VALID_FROM_DATE_EDUCATN

PA0022.BEGDA Start Date for educationinfotype DATETIME 24 0 9 yes


PA0002/PA0006.BEGDA - Beginning date ofrecords DATETIME 24 0 9 yes


TRP1000/T5U13.BEGDA - Combined tablebeginning date DATETIME 24 0 9 yes

195 VALID_FROM_DATE_MGR HRP1001/HRP1000.BEGDA - Begin Date DATETIME 24 0 9 yes

196 VALID_FROM_DATE_ORG HRP1000.BEGDA - Beginning effective date DATETIME 24 0 9 yes



197 VALID_FROM_DATE_PAY

PA0008.BEGDA PA0008.BEGDA Start date forBasic Pay information DATETIME 24 0 9 yes

198 VALID_FROM_DATE_PERSNL

PA0002.BEGDA From for Personal datainfotype DATETIME 24 0 9 yes


HRP1000/HRP1007.BEGDA - Beginningeffective date (merged) DATETIME 24 0 9 yes

200 VALID_FROM_DATE_QUALIFCTN

PA0024.BEGDA Start Date for Qualificationsinfotype DATETIME 24 0 9 yes

201 VALID_FROM_DATE_RESIDNCE

PA0094.BEGDA From for Residence Statusinfotype DATETIME 24 0 9 yes

202 VALID_FROM_DATE_WRKTIME

PA0007.BEGDA From for Planned worktimeinfotype DATETIME 24 0 9 yes

203 VALID_TO_DATE PK End date of records that have changed for thisemployee during this load DATETIME 24 0 9 no

204 VALID_TO_DATE_ACTION PA0000.ENDDA End date - Event/Action DATETIME 24 0 9 yes

205 VALID_TO_DATE_ASSIGN PA0001.ENDDA End date for PA0001 infotype DATETIME 24 0 9 yes

206 VALID_TO_DATE_BENFT

PA0169.ENDDA - End date for Plannedsavings / investments infotype DATETIME 24 0 9 yes

207 VALID_TO_DATE_CONTRACT

PA0016.ENDDA End Date for ContractInfotype DATETIME 24 0 9 yes

208 VALID_TO_DATE_DATES

PA0019.ENDDA To for monitoring datesinfotype DATETIME 24 0 9 yes

209 VALID_TO_DATE_EDUCATN

PA0022.ENDDA End Date for Educationinfotype DATETIME 24 0 9 yes


PA0002/PA0006.ENDDA - Ending date ofrecords DATETIME 24 0 9 yes

211 VALID_TO_DATE_JOB TRP1000/T5U13.ENDDA - Combined tableEding date DATETIME 24 0 9 yes

212 VALID_TO_DATE_MGR HRP1001/HRP1000.ENDDA - End Date DATETIME 24 0 9 yes

213 VALID_TO_DATE_ORG HRP1000.ENDDA - Ending effective date DATETIME 24 0 9 yes

214 VALID_TO_DATE_PAY PA0008.ENDDA End date for Basic Payinformation DATETIME 24 0 9 yes



215 VALID_TO_DATE_PERSNL

PA0002.ENDDA To - For Personal datainfotype DATETIME 24 0 9 yes


HRP1000/HRP1007.ENDDA - Ending effectivedate (merged) DATETIME 24 0 9 yes


218 VALID_TO_DATE_QUALIFICTN

PA0024.ENDDA End Date for Qualificationinfotype DATETIME 24 0 9 yes

219 VALID_TO_DATE_RESIDNCE

PA0094.ENDDA To for Residence statusinfotype DATETIME 24 0 9 yes

220 VALID_TO_DATE_WRKTIME

PA0007.ENDDA To for Palnned worktimeinfotype DATETIME 24 0 9 yes

221 VESTNG_RULE_ID T74FD.VESTI - Vesting rules for employeecontributions to savings plans NVARCSTR 4 0 0 no

222 VETERAN_STATUS_CODE PA0077.VETST Veteran status NVARCSTR 1 0 0 yes

223 WAGE_TYPE_ID_01 PA0008.LGA01 Wage type 01 NVARCSTR 4 0 0 yes

224 WAGE_TYPE_ID_02 PA0008.LGA02 Wage type 02 NVARCSTR 4 0 0 no

225 WAGE_TYPE_ID_03 PA0008.LGA03 Wage type 03 NVARCSTR 4 0 0 no

226 WAGE_TYPE_KEY_01 Lookup on surrogate key of WAGE_TYPEdimension for Wage Type 01 DECIMAL 48 28 0 no



229 WORK_PERMIT_EXPIRE_DATE PA0094.EXPDT Expiry date of work permit DATETIME 24 0 9 yes

230 WORK_PERMIT_ISSUE_DATE PA0094.DATE2 Date of issue for work permit DATETIME 24 0 9 yes

231 WORK_PERMIT_TYPE_ID PA0094.FWOCD Type of work permit NVARCSTR 2 0 0 no

232 YEARS_OF_SERVICE Years of service as of current date DECIMAL 48 5 2 yes







NVARCSTR 16 0 0 yes

EMPLOYEE_GROUP

Employee Group descriptive information from T501T



Nullable

1 EMPLOYEE_GRP_DESCR T501T.PTEXT - Name of employee group NVARCSTR 20 0 0 yes

2 EMPLOYEE_GRP_FULL_NAME

Concatenated: T501T.PERSG - Employeegroup + T501T.PTEXT - Name of employeegroup

NVARCSTR 30 0 0 yes

3 EMPLOYEE_GRP_ID PK T501T.PERSG - Employee group NVARCSTR 1 0 0 no



EMPLOYEE_SUBGROUP

Employee sub-group descriptive information from T503T



Nullable

1 EMPLOYEE_SUBGRP_DESCR

T503T.PERSK - Employee subgroupdescription NVARCSTR 20 0 0 yes

2 EMPLOYEE_SUBGRP_FULL_NAME

Concatenated: T503T.PERSK - Employeesubgroup + T503T.PERSK - Employeesubgroup description

NVARCSTR 30 0 0 yes

3 EMPLOYEE_SUBGRP_ID PK T503T.PERSK - Employee subgroup NVARCSTR 2 0 0 no





EMPLOYEE_WAGE_0008_STAGEInclude date-effective attributes from PA0008, PA0001, Job, Employee, Postion, Org Unit dimensions; used to loadEMPLOYEE_WAGE_FACT



Nullable



3 ADMIN_ID_PAYROLL PA0001.SACHA Payroll administrator NVARCSTR 3 0 0 yes



















20 AMT_PAYMNT_16 PA0008.BET16 Wage typ 16e amount forpayments DECIMAL 48 13 2 yes








28 CHANGE_DATE PA0008.AEDTM Last time this infotype waschanged. DATETIME 24 0 9 yes










36 CURR_ID_PAYMNT PA0008.WAERS Currency key NVARCSTR 5 0 0 yes

37 CURR_ID_SALARY PA0008.ANCUR Currency key for annualsalary NVARCSTR 5 0 0 yes








PA0008.OPK04 Operation indicator for wagetypes 04 (DEDUCT_REFER) NVARCSTR 10 0 0 yes





































T510N.TRFKZ - EE grouping for collectiveagreement provision (CAP) NVARCSTR 1 0 0 yes



62 INDIRECT_VALUATN_FLAG_01 PA0008.IND01 Indicator for indirect valuation INTEGER 4 0 0 yes


























86 NEXT_INCREASE_DATE_COMPR PA0008.VGLSV Date of next increase DATETIME 24 0 9 yes





89 PARTNERSHIP_TYPE_ID PA0008.PARTN Partnership NVARCSTR 2 0 0 yes


91 PAY_SCALE_AREA_ID PA0008.TRFGB Pay scale area NVARCSTR 2 0 0 yes

92 PAY_SCALE_AREA_ID_COMPR PA0008.VGLGB Comparison pay scale area NVARCSTR 2 0 0 yes


94 PAY_SCALE_GRP_CODE_COMPR PA0008.VGLGR Comparison pay scale group NVARCSTR 8 0 0 yes


96 PAY_SCALE_LVL_COMPR PA0008.VGLST Comparison pay scale level NVARCSTR 2 0 0 yes

97 PAY_SCALE_TYPE_ID PA0008.TRFAR Pay scale type NVARCSTR 2 0 0 yes

98 PAY_SCALE_TYPE_ID_COMPR PA0008.VGLTA Comparison pay scale type NVARCSTR 2 0 0 yes






NVARCSTR 8 0 0 yes







107 QTY_UNIT_04 PA0008.ANZ04 Number for Wage Type 04 DECIMAL 48 7 2 yes

















124 SUBTYPE_CODE PK PA0008.SUBTY Subtype NVARCSTR 4 0 0 no



125 UOT_ID_01 PA0008.EIN01 Unit of time/measurement forWage type 01 NVARCSTR 3 0 0 yes

126 UOT_ID_02 PA0008.EIN02 Unit of time/measurement forWage Type 02 NVARCSTR 3 0 0 yes

127 UOT_ID_03 PA0008.EIN03 Unit of time/measurement forWage Type03 NVARCSTR 3 0 0 yes





132 UOT_ID_08 PA0008.EIN08 Unit of time/measurement forWage TYpe 08 NVARCSTR 3 0 0 yes















145 VALID_FROM_DATE PK PA0008.BEGDA PA0008.BEGDA Start date DATETIME 24 0 9 no


147 VALID_FROM_DATE_PAY PA0008.BEGDA PA0008.BEGDA Start date DATETIME 24 0 9 yes



150 VALID_TO_DATE_PAY PA0008.ENDDA End date DATETIME 24 0 9 yes









159 WAGE_TYPE_ID_09 PA0008.BET09 Wage type 09 NVARCSTR 4 0 0 yes







Nullable





5 AMT_PAYMNT PA0014.BETRG Amount of payment for thewage type DECIMAL 48 13 2 yes

6 ASSIGNMNT_NUM PA0014.ZUORD Assignment number NVARCSTR 20 0 0 yes


8 CHANGE_DATE PA0014.AEDTM Changed on DATETIME 24 0 9 yes




12 COUNTRY_GRP_ID PA0001.COUNTRY_GRP_ID (lookup 0MOLGA) NVARCSTR 2 0 0 yes


14 CURRENT_FLAG Set to 1 if the record is current (ENDDA =9999.12.31) DECIMAL 48 28 0 yes

15 CURR_ID PA0014.WAERS Currency key NVARCSTR 5 0 0 yes

16 DEDUCTN_OR_REF PA0014.OPKEN Operation indicator for wagetypes NVARCSTR 10 0 0 yes








21 FIRST_PAYMNT_DATE PA0014.ZDATE First payment date DATETIME 24 0 9 yes

22 FIRST_PAYMNT_PERIOD PA0014.ZFPER First payment period NVARCSTR 2 0 0 yes

23 INDIRECT_VALUATN_FLAG PA0014.INDBW Indicator for indirect valuation DECIMAL 48 28 0 yes







30 PAYMNT_INTERVAL PA0014.ZANZL Number for determining furtherpayment dates DECIMAL 48 28 0 yes

31 PAYMNT_MODEL_DESCR T549Y.LTEXT - Payment Model Description NVARCSTR 50 0 0 yes

32 PAYMNT_MODEL_ID PA0014.MODEL Payment model NVARCSTR 4 0 0 yes









NVARCSTR 8 0 0 yes


39 QTY_UNIT PA0014.ANZHL an amount or number (andalso a unit) for wage type 01 DECIMAL 48 7 2 yes


41 TRANSFER_DATE PA0014.UWDAT Bank Transfer date DATETIME 24 0 9 yes

42 UOT_ID PA0014.ZEINH Time/measurement unit NVARCSTR 3 0 0 yes

43 UOT_ID_INTERVAL PA0014.ZEINZ Time unit for determining nextpayment NVARCSTR 3 0 0 yes



46 VALID_FROM_DATE_DEDUCT PA0014.BEGDA From DATETIME 24 0 9 yes



49 VALID_TO_DATE_DEDUCT PA0014.ENDDA To DATETIME 24 0 9 yes

50 VALID_TO_DATE_PREV PA0014.BEGDA Start date - 1 DATETIME 24 0 9 yes

51 WAGE_TYPE_ID PA0014.LGART Wage type NVARCSTR 4 0 0 yes






Nullable





5 AMT_PAYMNT PA0015.BETRG Amount DECIMAL 48 13 2 yes


















20 INDIRECT_VALUATN_FLAG PA0014.INDBW Indicator for indirect valuation DECIMAL 48 28 0 yes






26 ORIGIN_DATE PA0015.ESTDT Date of origin DATETIME 24 0 9 yes


28 PAYROLL_PERIOD PA0015.PABRP Payroll period DECIMAL 48 28 0 yes

29 PAYROLL_YEAR PA0015.PABRJ Payroll year DECIMAL 48 28 0 yes






NVARCSTR 8 0 0 yes




35 QTY_UNIT PA0015.ANZHL an amount or number (andalso a unit) if wage types are entered DECIMAL 48 7 2 yes

36 SUBTYPE_CODE PK PA0015.SUBTY Subtype (Wage Type) NVARCSTR 4 0 0 no

37 TRANSFER_DATE PA0015.UWDAT Transfer date DATETIME 24 0 9 yes

38 UOT_DESCR T538T.ETEXT - Unit of Time/Measuredescription lookup NVARCSTR 20 0 0 yes

39 UOT_ID TPA0015.ZEINHime/measurement unit NVARCSTR 3 0 0 yes



42 VALID_FROM_DATE_PAYMNT PA0015.BEGDA From DATETIME 24 0 9 yes



45 VALID_TO_DATE_PAYMNT PA0015.ENDDA To DATETIME 24 0 9 yes


47 YEAR_PERIOD_PAYROLL

PA0015.PABRJ + PA0015.PABRP -concatenated Year and Month of birth NVARCSTR 10 0 0 yes



EMPLOYEE_WAGE_FACT

Employee wage types from PA0008, PA0014 and PA0015 accumulated into a single Fact by Pivoting on Wage Type



Nullable




4 ADMIN_ID_TIME PA0001.SACHZ Administrator for timerecording NVARCSTR 3 0 0 no






10 COUNTRY_GRP_ID PA0008/PA0014/PA0015.COUNTRY_GRP_ID(lookup MOLGA) NVARCSTR 2 0 0 no



13 CURR_ID PA0014.WAERS Currency key NVARCSTR 5 0 0 no


15 EMPLOYEE_KEY Lookup on surrogate key of EMPLOYEEdate-effective dimension DECIMAL 48 28 0 no






19 INDIRECT_VALUATN_FLAG PA0014.INDBW Indicator for indirect valuation INTEGER 4 0 0 yes

20 INFOTYPE_ID PK Hard-coded value PA0014 NVARCSTR 6 0 0 no


22 JOB_KEY Lookup on surrogate key of JOB date-effectivedimension DECIMAL 48 28 0 no





27 ORG_UNIT_KEYLookup on surrogate key ofORGANIZATION_UNIT date-effectivedimension

DECIMAL 48 28 0 no

28 ORIGIN_DATE Only - PA0015.ESTDT Date of origin DATETIME 24 0 9 yes

29 PAYMNT_INTERVAL PA0014.ZANZL Number for determining furtherpayment dates INTEGER 4 0 0 yes

30 PAYROLL_AREA_ID PA0001.ABKRS Payroll area NVARCSTR 2 0 0 no

31 PAY_SCALE_AREA_ID T510G.TRFGB - Pay scale area NVARCSTR 2 0 0 no

32 PAY_SCALE_TYPE_ID T510A.TRFAR Pay scale type NVARCSTR 2 0 0 no





35 PERSON_ID PK PA0008/PA0014/PA0015.PERNR Personnelnumber NVARCSTR 8 0 0 no


37 POSITION_KEY Lookup on surrogate key of POSITIONdate-effective dimension DECIMAL 48 28 0 no


39 SALARY_RANGE_KEY Surrogate key generated DECIMAL 48 28 0 no

40 UOT_ID PA0014.ZEINH Time/measurement unit NVARCSTR 3 0 0 no

41 UOT_ID_INTERVAL PA0014.ZEINZ Time unit for determining nextpayment NVARCSTR 3 0 0 no



44 WAGE_SEQ_ID PKCorresponds to LGART order (1-20) in originalPA0008 record or is zero for other infotypes.Used to make key unique if the same wagetype is used more than once in PA000

INTEGER 4 0 0 no

45 WAGE_TYPE_ID PK PA0008/PA0014/PA0015.LGART Wage type NVARCSTR 4 0 0 no

46 WAGE_TYPE_KEY Lookup on surrogate key of WAGE_TYPEdimension for Wage Type ID DECIMAL 48 28 0 no



ENROLLMENT_TYPE

Benefit program enrollment type descriptive attributes from DD07T, BEN_ENRTYP domain; load ENROLLMENT_TYPE dimension



Nullable

1 ENROLLMNT_TYPE_DESCR

DD07T.DDTEXT Short text describing ABAP/4Dictionary objects (BEN_ENRTYP domain) NVARCSTR 60 0 0 yes

2 ENROLLMNT_TYPE_FULL_NAME

Concatenated:DD07TDD07T.DOMVALUE_Lvalue/upper limit(BEN_ENRTYP domain) + DD07T.DDTEXTShort text describing ABAP/4 Dictionaryobjects (BEN_ENRTYP domain)

NVARCSTR 70 0 0 yes

3 ENROLLMNT_TYPE_ID PK DD07TDD07T.DOMVALUE_Lvalue/upper limit

(BEN_ENRTYP domain) NVARCSTR 1 0 0 no



ETHNIC_ORIGIN

Ethnic Origin descriptive attributes from T505S; load ETHNIC_ORIGIN dimension



Nullable


2 COUNTRY_GRP_ID PK T505S.MOLGA Country grouping NVARCSTR 2 0 0 no

3 ETHNIC_ORIGIN_DESCR T505S.LTEXT Text length 25 NVARCSTR 25 0 0 yes

4 ETHNIC_ORIGIN_ID PK T505S.RACKY Ethnic origin NVARCSTR 2 0 0 no





GENDER

Gender descriptive attributes from DD07T, GESCH domain; load GENDER dimension



Nullable

1 GENDER_DESCR DD07T.DDTEXT Short text describing ABAP/4Dictionary objects (GESCH domain) NVARCSTR 60 0 0 yes

2 GENDER_ID PK DD07T Values for domains: Single value/upperlimit (GESCH domain) NVARCSTR 1 0 0 no



HEALTH_PLAN

Benefits - Insurance Health Plan descriptive attributes from T5UCE



Nullable


2 BENFT_AREA_ID PK T5UCE.BAREA Benefit area NVARCSTR 2 0 0 no


4 BENFT_PLAN_ID PK T5UCE.BPLAN Benefit plan NVARCSTR 4 0 0 no

5 HEALTH_PLAN_DESCR T5UCE.LTEXT Description (30 characters) NVARCSTR 30 0 0 yes

6 HEALTH_PLAN_FULL_NAME

Concatenated: T5UCE.BOPTI Health planoptions + T5UCE.LTEXT Description (30characters)

NVARCSTR 40 0 0 yes

7 HEALTH_PLAN_ID PK T5UCE.BOPTI Health plan options NVARCSTR 4 0 0 no





HOLIDAY_CALENDAR

Public holidays calendar - THOC



Nullable

1 CALENDAR_DATE PK THOC.DATUM Date DATETIME 24 0 9 no

2 COUNT_HOLIDAY Set to 1 be to used for aggregations to countnumber of holidays DECIMAL 48 28 0 yes

3 GUARANTEED_FLAG Public holiday guaranteed flag (1/0) INTEGER 4 0 0 yes

4 HOLIDAY_CALENDAR_DESCR THOCT.LTEXT Text for object NVARCSTR 60 0 0 yes

5 HOLIDAY_CALENDAR_ID PK THOC.IDENT Public Holiday Calendar NVARCSTR 2 0 0 no

6 HOLIDAY_DESCR THOLT.LTEXT Long text NVARCSTR 30 0 0 yes

7 HOLIDAY_ID PK THOC.FTGID Public holiday key NVARCSTR 3 0 0 no





HR_INFOTYPE_0000_ACTION

Employee Events records from Infotype PA0000



Nullable

1 ACTION_REASON_DESCR

T530T. MGTXT - Description for ActionReason (lookup) NVARCSTR 30 0 0 yes

2 ACTION_REASON_ID PA0000.MASSG Reason for action NVARCSTR 2 0 0 yes

3 ACTION_SELECT_FLAG

Set to 1 if the status is one of pre-definedRapid Mart Variables: $G_HIRE_ACTION_01 -03, $G_TERMINATION_ACTION,$G_REHIRE_ACTION_01 - 02,$G_RETIRE_ACTION

INTEGER 4 0 0 yes

4 ACTION_TYPE_DESCR


5 ACTION_TYPE_ID PA0000.MASSN Action type NVARCSTR 2 0 0 yes





10 INFOTYPE_ID Hard-coded - SAP source table name toPA0000 NVARCSTR 6 0 0 yes




PA0000.BEGDA - Start date for Hire actions(1-3) DATETIME 24 0 9 yes






17 STATUS_DESCR_CUSTOM

T529U. TEXT1 -User-defined statusdescription (lookup) NVARCSTR 40 0 0 yes

18 STATUS_DESCR_EMPLMNT

T529U. TEXT1 -Employment status description(lookup) NVARCSTR 40 0 0 yes

19 STATUS_DESCR_SPECL_PAYMNT

T529U. TEXT1 -Special Payment statusdescription (lookup) NVARCSTR 40 0 0 yes

20 STATUS_ID_CUSTOM PA0000.STAT1 User-defined status NVARCSTR 1 0 0 yes

21 STATUS_ID_EMPLMNT PA0000.STAT2 Employment status NVARCSTR 1 0 0 yes

22 STATUS_ID_SPECL_PAYMNT PA0000.STAT3 Special payment status NVARCSTR 1 0 0 yes


24 VALID_FLAGIf there is duplication in date-effective periodsfor the same record, the flag is set to 0, if therecord is unique - then it is 1; used to filter thedata before genera

INTEGER 4 0 0 yes






HR_INFOTYPE_0001_ASSIGNMENT

HR Master Data: Organizational Assignment from PA0001



Nullable

1 ADMIN_GRP_CODE PA0001.SBMOD Administrator group; used forAdministrator identification NVARCSTR 4 0 0 yes




5 ADMIN_NAME_HR T526.SACHN - HR Master Data AdministratorName(lookup) NVARCSTR 20 0 0 yes

6 BUS_AREA_DESCR TGSBT.GTEXT - Business Area Descr(lookup) NVARCSTR 30 0 0 yes


8 CHANGE_DATE PA0001.AEDTM -Last time this infotype waschanged. DATETIME 24 0 9 yes


10 CMPNY_CODE_NAME T001.BUTXT - Company Code Name (lookup) NVARCSTR 25 0 0 yes

11 CONTRACT_DESCR T542T.ATX - Work Contract Descr(lookup) NVARCSTR 15 0 0 yes


13 COST_CNTR_DESCR CSKT. KTEXT - Cost Center Desription(lookup) NVARCSTR 50 0 0 yes


15 COUNTRY_GRP_DESCR

T500T.LTEXT - Country Grouping for HRdescription (lookup) NVARCSTR 25 0 0 yes




17 CTRL_AREA_DESCR TKA01.BEZEI - Controlling Area description(lookup) NVARCSTR 25 0 0 yes



20 EMPLOYEE_GRP_DESCR

T501T.PTEXT - Employee GroupDescr(lookup) NVARCSTR 20 0 0 yes




NVARCSTR 1 0 0 yes


T503T.PTEXT - Employee Sub-GroupDescr(lookup) NVARCSTR 20 0 0 yes





28 HOLIDAY_CALENDAR_ID T001P.MOFID Public holiday calendar ID NVARCSTR 2 0 0 yes

29 INFOTYPE_ID Hard-coded Name of infotype PA0001 NVARCSTR 6 0 0 yes

30 JOB_DESCR T513S.STLTX - Job Descr Descr(lookup) NVARCSTR 25 0 0 yes


32 LEAVE_TYPE_GRP_CODE

T001P.MOURA Personnel subarea groupingfor leave types(lookup) NVARCSTR 2 0 0 yes

33 LEGAL_PERSON_CODE

PA0001.JUPER Legal person - a body ofpersons, an enterprise, a partnership, or otherlegal group that is recognized by law as thesubject of rights and duties

NVARCSTR 4 0 0 yes





36 OBJ_TYPE_DESCR T777O.OTEXT - Object Type Descr(lookup) NVARCSTR 25 0 0 yes

37 OBJ_TYPE_ID PA0001.OTYPE Object type (from T778O) NVARCSTR 2 0 0 yes

38 ORG_KEY_DESCR T527O.TEXT2 - Organizational Key Name(lookup) NVARCSTR 50 0 0 yes


40 ORG_UNIT_DESCR T527X.ORGTX - Org Unit Descr Descr(lookup) NVARCSTR 25 0 0 yes


42 PAYROLL_AREA_DESCR T549T.ATEXT - Payroll Area Descr(lookup) NVARCSTR 20 0 0 yes



45 PERSONNEL_AREA_NAME

T500P.NAME1 - Personnel Area Name(lookup) NVARCSTR 25 0 0 yes


47 PERSONNEL_SUBAREA_NAME

T001P.BTEXT - Personnel Sub-area Name(lookup) NVARCSTR 15 0 0 yes




NVARCSTR 8 0 0 yes

50 POSITION_DESCR T528T.PLSTX - Position Descr Descr(lookup) NVARCSTR 25 0 0 yes






INTEGER 4 0 0 yes



56 VALID_TO_DATE_PREV

(PA0001.BEGDA - 1) -Link to previous recordin the same infotype DATETIME 24 0 9 yes



HR_INFOTYPE_0002_PERSONAL

HR master data - infotype PA0002 -- Personal data



Nullable

1 BIRTH_COUNTRY PA0002.GBLND Country of birth NVARCSTR 3 0 0 yes

2 BIRTH_DATE PA0002.GBDAT Date of birth (basic) - used forcalculation of Age, etc DATETIME 24 0 9 yes

3 BIRTH_DATE_PASSPORT PA0002.GBPAS Date of birth acc.to passport DATETIME 24 0 9 yes

4 BIRTH_PLACE PA0002.GBORT Birthplace NVARCSTR 40 0 0 yes

5 BIRTH_STATE PA0002.GBDEP State NVARCSTR 3 0 0 yes






11 FIRST_NAME_KATAKANA PA0002.FNAMK First Name (Katakana) NVARCSTR 40 0 0 yes

12 FIRST_NAME_ROMAJI PA0002.FNAMR First Name (Romaji) NVARCSTR 40 0 0 yes

13 FIRST_NAME_SEARCH PA0002.VNAMC First name (matchcode field) NVARCSTR 25 0 0 yes


15 GENDER_DESCR DD07T.DDTEXT Lookup description forGESCH in DD07T NVARCSTR 10 0 0 yes

16 GENDER_ID PA0002.GESCH Gender key NVARCSTR 1 0 0 yes





19 INITIALS PA0002.INITS Employees initials NVARCSTR 10 0 0 yes

20 LANG_DESCR T002T.SPTXT - Lookup on Languagedescritpion NVARCSTR 16 0 0 yes

21 LANG_ID PA0002.SPRSL Language key NVARCSTR 1 0 0 yes


23 LAST_NAME_BIRTH PA0002.NAME2 2nd surname / name at birth NVARCSTR 40 0 0 yes

24 LAST_NAME_BIRTH_KATAKANA

PA0002.NABIK Name of Birth (Maiden)(Katakana) NVARCSTR 40 0 0 yes

25 LAST_NAME_BIRTH_ROMAJI

PA0002.NABIR Name of Birth (Romaji) -Maiden name NVARCSTR 40 0 0 yes

26 LAST_NAME_KATAKANA PA0002.LNAMK Last Name (Katakana) NVARCSTR 40 0 0 yes

27 LAST_NAME_ROMAJI PA0002.LNAMR Last Name (Romaji) NVARCSTR 40 0 0 yes

28 LAST_NAME_SEARCH PA0002.NCHMC Last name (matchcode field) NVARCSTR 25 0 0 yes



31 MARITAL_STATUS_DESCR

T502T. FTEXT - Lookup on Marital statusdescritpion NVARCSTR 50 0 0 yes

32 MARITAL_STATUS_ID PA0002.FAMST Marital status key NVARCSTR 1 0 0 yes

33 MIDDLE_NAME PA0002.MIDNM Middle Name NVARCSTR 40 0 0 yes





T005T. NATIO - Seconde Nationality Textlookup NVARCSTR 15 0 0 yes

36 NATIONALITY_DESCR_02 T005T.NATIO -Third Nationality Text lookup NVARCSTR 15 0 0 yes


T005T.NATIO - Lookup on First Nationalitydescritpion NVARCSTR 15 0 0 yes

38 NATIONALITY_ID_01 PA0002.NATIO Country of the First Nationality NVARCSTR 3 0 0 yes

39 NATIONALITY_ID_02 PA0002.NATI2 Second nationality Country NVARCSTR 3 0 0 yes

40 NATIONALITY_ID_03 PA0002.NATI3 Third nationality Country NVARCSTR 3 0 0 yes

41 NICKNAME PA0002.RUFNM Known as NVARCSTR 40 0 0 yes

42 NICKNAME_KATAKANA PA0002.NICKK Nickname (Katakana) NVARCSTR 40 0 0 yes

43 NICKNAME_ROMAJI PA0002.NICKR Nickname (Romaji) NVARCSTR 40 0 0 yes

44 NUM_OF_CHILDREN PA0002.ANZKD Number of children INTEGER 4 0 0 yes


46 PREFIX_NAME_01 PA0002.VORSW Name Prefix NVARCSTR 15 0 0 yes

47 PREFIX_NAME_02 PA0002.VORS2 Second name prefix NVARCSTR 15 0 0 yes


NVARCSTR 4 0 0 yes




52 TITLE_01 T522T. ATEXT - Lookup on Form of Address(Title) descritpion NVARCSTR 5 0 0 yes



53 TITLE_02 PA0002.TITL2 Second title NVARCSTR 15 0 0 yes

54 TITLE_ACADEMIC PA0002.TITEL Title NVARCSTR 15 0 0 yes

55 TITLE_OTHER PA0002.NAMZU Title NVARCSTR 15 0 0 yes


INTEGER 4 0 0 yes


58 VALID_FROM_DATE_MARITAL

PA0002.FAMDT Validity begin date for currentmarital status DATETIME 24 0 9 yes







NVARCSTR 16 0 0 yes




HR master data from PA0005 infotype - Leave Entitlement;



Nullable

1 AMT_LEAVE_ACCOUNTED_01

PA0005.UAB01 Leave days accounted (Hoursor Days) DECIMAL 48 10 5 yes


PA0005.UAB02 Leave days accounted (Daysor Hours) DECIMAL 48 10 5 yes



4 AMT_LEAVE_ACCOUNTED_04 PA0005.UAB04 Leave days accounted DECIMAL 48 10 5 yes





7 AMT_LEAVE_ENTITLMNT_01

PA0005.UAN01 Leave entitlement (Hours orDays) DECIMAL 48 10 5 yes


PA0005.UAN02 Leave entitlement (Days orHours) DECIMAL 48 10 5 yes















17 INFOTYPE_ID Source of infotype data; hard-coded to PA0005 NVARCSTR 6 0 0 yes

18 LEAVE_END_DATE PA0005.UREND To date of leave DATETIME 24 0 9 yes

19 LEAVE_END_DATE_01

PA0005.UEN01 To date of leave for LeaveType 1 DATETIME 24 0 9 yes




PA0005.UEN03 To date of leave for Leavetype 3 DATETIME 24 0 9 yes







25 LEAVE_START_DATE PA0005.URBEG Leave begin date DATETIME 24 0 9 yes

26 LEAVE_START_DATE_01

PA0005.UBE01 Leave begin date for LeaveType 01 DATETIME 24 0 9 yes











32 LEAVE_TYPE_DESCR_01

T533T.URTXT - Lookup on Leave type (1)descritpion NVARCSTR 20 0 0 yes














T001P.MOURA Personnel subarea groupingfor leave types(lookup) NVARCSTR 2 0 0 yes

39 LEAVE_TYPE_ID_01 PA0005.UAR01 Leave type NVARCSTR 2 0 0 yes

40 LEAVE_TYPE_ID_02 PA0005.UAR02 Leave type for Leave Type 2 NVARCSTR 2 0 0 yes

41 LEAVE_TYPE_ID_03 PA0005.UAR03 Leave type 3 NVARCSTR 2 0 0 yes




45 LEAVE_YEAR PA0005.URLJJ Leave year INTEGER 4 0 0 yes



48 OBJ_IDENTIFICTN_CODE PK PA0005.OBJPS Object identification NVARCSTR 2 0 0 no

49 PERSONNEL_AREA_ID Lookup Personnel Area (WERKS) in PA0001 NVARCSTR 4 0 0 yes

50 PERSONNEL_AREA_NAME

T500P.NAME1 - Personnel Area Name(lookup) NVARCSTR 30 0 0 yes

51 PERSONNEL_SUBAREA_ID

Lookup Personnel Sub Area (BTRTL) inPA0001 NVARCSTR 4 0 0 yes

52 PERSONNEL_SUBAREA_NAME

T001P.BTEXT - Personnel Sub-area Name(lookup) NVARCSTR 15 0 0 yes




54 SUBTYPE_CODE PK PA0005.SUBTY Subtype (Leave Year) NVARCSTR 4 0 0 no


INTEGER 4 0 0 yes






HR_INFOTYPE_0006_ADDRESS

Load Personnel Address and Communications master data from PA0006, PA0105



Nullable

1 ADDRESS_TYPE_DESCR

T503T.PTEXT - Address Record TypeDescr(lookup) NVARCSTR 40 0 0 yes

2 ADDRESS_TYPE_ID PA0006.ANSSA Address Record Type NVARCSTR 4 0 0 yes

3 BUS_ROUTE_CODE PA0006.BUSRT Bus route NVARCSTR 3 0 0 yes


5 CITY PA0006.ORT01 City NVARCSTR 40 0 0 yes

6 CMPNY_APARTMNT_FLAG PA0006.WKWNG Company-owned apartment INTEGER 4 0 0 yes

7 COUNTRY_ID PA0006.LAND1 Country key NVARCSTR 3 0 0 yes

8 COUNTRY_NAME T005T.LANDX - Country Descr(lookup) NVARCSTR 15 0 0 yes

9 COUNTY_ID PA0006.COUNC County code NVARCSTR 3 0 0 yes

10 COUNTY_NAME T005F.BEZEI - County Descr(lookup) NVARCSTR 20 0 0 yes


12 DISTANCE_KM PA0006.ENTKM Distance in kilometers INTEGER 4 0 0 yes

13 DISTRICT PA0006.ORT02 District NVARCSTR 40 0 0 yes


15 FAX PA0105.USRID Communication ID/number(Fax comm type) NVARCSTR 30 0 0 yes

16 HOUSE_NUMBER PA0006.HSNMR House Number NVARCSTR 10 0 0 yes




18 INTERNET PA0105.USRID Communication ID/number(Internet Communication Type) NVARCSTR 30 0 0 yes

19 IN_CARE_OF_NAME PA0006.NAME2 C/O name NVARCSTR 40 0 0 yes



22 MUNICPL_CITY_CODE PA0006.RCTVC Municipal city code NVARCSTR 6 0 0 yes


24 PHONE PA0006.TELNR Telephone number NVARCSTR 14 0 0 yes

25 REGION_ID PA0006.STATE Region (State, Province,County) NVARCSTR 3 0 0 yes

26 REGION_NAME T005U.BEZEI - Region (state) Descr(lookup) NVARCSTR 20 0 0 yes

27 RELATIONSHIP_DESCR

T577S.ATEXT - Relationship Descr(lookup);Family Characteristis = A NVARCSTR 20 0 0 yes

28 RELATIONSHIP_IDPA0006.INDRL Indicator for relationship(specification code) - Charactesitic (EIGSH) =A in T577S

NVARCSTR 2 0 0 yes

29 STREET PA0006.STRAS Street and house number NVARCSTR 60 0 0 yes

30 SUBTYPE_CODE PK PA0006.SUBTY Subtype (address type) NVARCSTR 4 0 0 no


INTEGER 4 0 0 yes






35 VOICEMAIL PA0105.USRID Communication ID/number(Voicemail communication type) NVARCSTR 30 0 0 yes

36 ZIP PA0006.PSTLZ Postal code NVARCSTR 10 0 0 yes



HR_INFOTYPE_0007_WORKTIME

HR Master data: Planned Working Time from PA0007



Nullable



3 DAYS_WEEK PA0007.WKWDY Weekly working days DECIMAL 48 4 2 yes

4 DYNAMIC_SCHED_FLAG

PA0007.DYSCH Create dynamic daily workschedule DECIMAL 48 10 2 yes


6 HOURS_DAY PA0007.ARBST Daily working hours DECIMAL 48 5 2 yes

7 HOURS_DAY_MAX PA0007.MAXTA Maximum number of workhours per day DECIMAL 48 5 2 yes

8 HOURS_DAY_MIN PA0007.MINTA Minimum number of workhours per day DECIMAL 48 5 2 yes

9 HOURS_MONTH PA0007.MOSTD Monthly hours DECIMAL 48 5 2 yes

10 HOURS_MONTH_MAX PA0007.MAXMO Maximum number of workhours per month DECIMAL 48 5 2 yes

11 HOURS_MONTH_MIN PA0007.MINMO Minimum number of workhours per month DECIMAL 48 5 2 yes

12 HOURS_WEEK PA0007.WOSTD Weekly hours DECIMAL 48 5 2 yes

13 HOURS_WEEK_MAX PA0007.MAXWO Maximum number of workhours per week DECIMAL 48 5 2 yes

14 HOURS_WEEK_MIN PA0007.MINWO Minimum weekly workinghours DECIMAL 48 5 2 yes

15 HOURS_YEAR PA0007.JRSTD Annual working hours DECIMAL 48 7 2 yes

16 HOURS_YEAR_MAX PA0007.MAXJA Maximum number of workhours per year DECIMAL 48 7 2 yes



17 HOURS_YEAR_MIN PA0007.MINJA Minimum number of workhours per year DECIMAL 48 7 2 yes




21 PARTTIME_FLAG PA0007.TEILK Checkbox for part-timeemployee (1/0) INTEGER 4 0 0 yes


23 PRCNT_EMPLOYMNT PA0007.EMPCT Employment percentage DECIMAL 48 5 2 yes

24 SUBTYPE_CODE PK PA0007.SUBTY Subtype (Grouping Value inECC 5.0 and higher) NVARCSTR 4 0 0 no

25 TIME_MGMT_STATUS_DESCR

T555V.ZTEXT - Employee Time ManagementStatus description (lookup) NVARCSTR 50 0 0 yes

26 TIME_MGMT_STATUS_ID

PA0007.ZTERF Employee status for TimeManagement NVARCSTR 1 0 0 yes


INTEGER 4 0 0 yes







Uses HR_INFOTYPE_0008_PAY to create a salary history that stores prior salary, and salary one year ago;



Nullable


2 AMT_SALARY_YR_AGO

HR_INFOTYPE_0008_PAY.AMT_SALARY_Y-Lookup annual salary on this day one yearago

DECIMAL 48 15 2 yes

3 AMT_SALARY_YR_PREV

HR_INFOTYPE_0008_PAY.AMT_SALARY_YR Previous salary lookup DECIMAL 48 15 2 yes



6 CURR_ID_SALARY_PREV

HR_INFOTYPE_0008_PAY.CURR_ID_SALARY lookup Previous currency NVARCSTR 5 0 0 yes

7 CURR_ID_SALARY_YR_AGO

HR_INFOTYPE_0008_PAY.CURR_ID_SALARY -Lookup currency for last years salary NVARCSTR 5 0 0 yes





12 SALARY_DATE_PREV PA0008.BEGDA Date of the previous salary DATETIME 24 0 9 yes


14 VALID_TO_DATE PK Calculated; based on PA0008.ENDDA Enddate DATETIME 24 0 9 no




HR Master data - Basic Pay from PA0008



Nullable
















16 AMT_PAYMNT_16 PA0008.BET16 Wage typ 16e amount forpayments DECIMAL 48 13 2 yes









23 CHANGE_DATE PA0008.AEDTM Last time this infotype waschanged. DATETIME 24 0 9 yes




27 CURR_ID_PAYMNT PA0008.WAERS Currency key NVARCSTR 5 0 0 yes




















75 NEXT_INCREASE_DATE_COMPR PA0008.VGLSV Date of next increase DATETIME 24 0 9 yes

76 PARTNERSHIP_TYPE_DESCR

T577S.ATEXT - Partnership Descr(lookup);Family Characteristis = 5 NVARCSTR 20 0 0 yes

77 PARTNERSHIP_TYPE_ID PA0008.PARTN Partnership NVARCSTR 2 0 0 yes

78 PAY_SCALE_AREA_ID PA0008.TRFGB Pay scale area NVARCSTR 2 0 0 yes

79 PAY_SCALE_AREA_ID_COMPR PA0008.VGLGB Comparison pay scale area NVARCSTR 2 0 0 yes


81 PAY_SCALE_GRP_CODE_COMPR PA0008.VGLGR Comparison pay scale group NVARCSTR 8 0 0 yes


83 PAY_SCALE_LVL_COMPR PA0008.VGLST Comparison pay scale level NVARCSTR 2 0 0 yes

84 PAY_SCALE_TYPE_ID PA0008.TRFAR Pay scale type NVARCSTR 2 0 0 yes

85 PAY_SCALE_TYPE_ID_COMPR PA0008.VGLTA Comparison pay scale type NVARCSTR 2 0 0 yes







108 UOT_DESCR_01T538T.ETEXT - Unit of Time/Measuredescription lookup (EIN01; LGA01 wage typecolumn)

NVARCSTR 20 0 0 yes


NVARCSTR 20 0 0 yes


NVARCSTR 20 0 0 yes


NVARCSTR 20 0 0 yes


NVARCSTR 20 0 0 yes



115 UOT_ID_03 PA0008.EIN03 Unit of time/measurement forWage Type03 NVARCSTR 3 0 0 yes





120 UOT_ID_08 PA0008.EIN08 Unit of time/measurement forWage TYpe 08 NVARCSTR 3 0 0 yes
















INTEGER 4 0 0 yes














145 WAGE_TYPE_ID_09 PA0008.BET09 Wage type 09 NVARCSTR 4 0 0 yes














HR_INFOTYPE_0014_DEDUCTION

HR Mater Data, Recurring Deductions from PA0014



Nullable















15 PAYMNT_INTERVAL PA0014.ZANZL Number for determining furtherpayment dates INTEGER 4 0 0 yes

16 PAYMNT_MODEL_DESCR T549Y.LTEXT - Payment Model Description NVARCSTR 50 0 0 yes



17 PAYMNT_MODEL_ID PA0014.MODEL Payment model NVARCSTR 4 0 0 yes




21 TRANSFER_DATE PA0014.UWDAT Bank Transfer date DATETIME 24 0 9 yes


23 UOT_ID PA0014.ZEINH Time/measurement unit NVARCSTR 3 0 0 yes

24 UOT_ID_INTERVAL PA0014.ZEINZ Time unit for determining nextpayment NVARCSTR 3 0 0 yes


INTEGER 4 0 0 yes







HR_INFOTYPE_0015_PAYMENT

HR Master data: Infotype for additional payments, PA0015



Nullable

1 AMT_PAYMNT PA0015.BETRG Amount DECIMAL 48 13 2 yes












13 ORIGIN_DATE PA0015.ESTDT Date of origin DATETIME 24 0 9 yes

14 PAYROLL_PERIOD PA0015.PABRP Payroll period INTEGER 4 0 0 yes

15 PAYROLL_YEAR PA0015.PABRJ Payroll year INTEGER 4 0 0 yes




17 QTY_UNIT PA0015.ANZHL an amount or number (andalso a unit) if wage types are entered DECIMAL 48 7 2 yes

18 SUBTYPE_CODE PK PA0015.SUBTY Subtype (Wage Type) NVARCSTR 4 0 0 no

19 TRANSFER_DATE PA0015.UWDAT Transfer date DATETIME 24 0 9 yes


21 UOT_ID TPA0015.ZEINHime/measurement unit NVARCSTR 3 0 0 yes


INTEGER 4 0 0 yes





27 YEAR_PERIOD_PAYROLL

PA0015.PABRJ + PA0015.PABRP -concatenated Year and Month of birth NVARCSTR 10 0 0 yes



HR_INFOTYPE_0016_CONTRACT

HR Master Data for Contract information from PA0016 infotype



Nullable


2 CONTACT_TYPE_DESCR T547S.CTTXT Contract Type Descr NVARCSTR 50 0 0 yes

3 CONTRACT_NUM PA0016.CTNUM Contract number NVARCSTR 20 0 0 yes

4 CONTRACT_TYPE_ID PA0016.CTTYP Contract type NVARCSTR 2 0 0 yes


6 EMPLOYEE_GRP_DESCR

T501T.PTEXT - Employee GroupDescr(lookup) NVARCSTR 20 0 0 yes

7 EMPLOYEE_GRP_ID PA0016.PERSG Employee Group NVARCSTR 1 0 0 yes


T503T.PTEXT - Employee Sub-GroupDescr(lookup) NVARCSTR 20 0 0 yes

9 EMPLOYEE_SUBGRP_ID PA0016.PERSK Employee Subgroup NVARCSTR 2 0 0 yes

10 END_DATE PA0016.CTEDT Contract end date DATETIME 24 0 9 yes

11 ENTRY_DATE PA0016.EINDT Initial entry DATETIME 24 0 9 yes

12 EXPIRATN_DATE PA0016.ARBER Expiration date of work permit DATETIME 24 0 9 yes







17 NOTICE_PER_DESCR_EMPLEE

T547T.KTEXT - Dismissals notices period forEmployer descripiton lookup NVARCSTR 20 0 0 yes

18 NOTICE_PER_DESCR_EMPLER

T547T.KTEXT - Dismissals notices period forEmployer descripiton lookup NVARCSTR 20 0 0 yes

19 NOTICE_PER_ID_EMPLEE

PA0016.KDGF2 Dismissals notice period foremployee NVARCSTR 2 0 0 yes

20 NOTICE_PER_ID_EMPLER

PA0016.KDGFR Dismissals notice period foremployer NVARCSTR 2 0 0 yes


22 QTY_CNTIND_PAY PA0016.LFZFR Period of continued pay(number) INTEGER 4 0 0 yes

23 QTY_PROBTN PA0016.PRBZT Probationary period (number) INTEGER 4 0 0 yes

24 QTY_SICK_PAY PA0016.KGZFR Sick pay supplement period(number) INTEGER 4 0 0 yes

25 START_DATE PA0016.CTBEG Start of contract DATETIME 24 0 9 yes


27 UOT_DESCR_CNTIND_PAY

T538T.ETEXT - Unit of Time/Measuredescription lookup for Continued Pay Qty NVARCSTR 20 0 0 yes

28 UOT_DESCR_PROBTN

T538T.ETEXT - Unit of Time/Measuredescription lookup for Probation Qty NVARCSTR 20 0 0 yes

29 UOT_DESCR_SICK_PAY

T538T.ETEXT - Unit of Time/Measuredescription lookup for Continued Pay Qty NVARCSTR 20 0 0 yes

30 UOT_ID_PROBTN PA0016.PRBEH Probationary period (unit) NVARCSTR 3 0 0 yes


INTEGER 4 0 0 yes

32 VALID_FROM_DATE PK PA0016.BEGDA Start Date DATETIME 24 0 9 no





35 WORK_LOCATN_NAME

PA0016.WRKPL Work location (ContractElements infotype) NVARCSTR 40 0 0 yes



HR_INFOTYPE_0019_DATES

HR Master data: Monitoring of Dates infotype from PA0019



Nullable








8 QTY_REMINDER_LEAD

T531.VORLZ Lead time (number). Thelead/follow-up time defines a period before orafter which the system should remind you of acertain task.

INTEGER 4 0 0 yes

9 REMINDER_DATE PA0019.MNDAT Reminder date DATETIME 24 0 9 yes

10 REMINDER_DAY PA0019.MNTAG Reminder day (within amonth/year) INTEGER 4 0 0 yes

11 REMINDER_MONTH PA0019.MNMON Monthly reminder INTEGER 4 0 0 yes

12 REMINDER_YEAR PA0019.MNJHR Annual reminder INTEGER 4 0 0 yes


14 TASK_DATE PA0019.TERMN Date/deadline DATETIME 24 0 9 yes

15 TASK_DAY PA0019.TMTAG Scheduled date (inmonth/year) INTEGER 4 0 0 yes

16 TASK_MONTH PA0019.TMMON Scheduled month INTEGER 4 0 0 yes



17 TASK_STATUS_DESCR Lookup description for BVMRK in DD07T NVARCSTR 10 0 0 yes

18 TASK_STATUS_ID PA0019.BVMRK Processing indicator NVARCSTR 1 0 0 yes

19 TASK_TYPE_DESCR T531S.TMTXT Text for date/deadline typelookup NVARCSTR 20 0 0 yes

20 TASK_TYPE_ID PA0019.TMART TASK type NVARCSTR 2 0 0 yes

21 TASK_YEAR PA0019.TMJHR Year of deadline INTEGER 4 0 0 yes

22 UOT_DESCR Lookup T538T.ETEXT - Lead time units ofmeasure text NVARCSTR 20 0 0 yes

23 UOT_ID T531.ZEINH Time/measurement unit NVARCSTR 3 0 0 yes


INTEGER 4 0 0 yes




28 YEAR_MONTH_REMINDER

PA0019.MNJHR + PA0019.MNMON -concatenated Year and Month of the task NVARCSTR 10 0 0 yes

29 YEAR_MONTH_TASK PA0019.TMJHR + PA0019.TMMON -concatenated Year and Month of the task NVARCSTR 10 0 0 yes



HR_INFOTYPE_0021_DEPENDENT

HR master data - infotype PA0021 -- Dependents Personal data



Nullable

1 BIRTH_COUNTRY PA0021.FGBLD Country of birth VARCSTR 3 0 0 yes

2 BIRTH_DATE PA0021.FGBDT Date of Birth DATE 24 0 9 yes

3 BIRTH_NAME PA0021.FGBNA Name at Birth VARCSTR 40 0 0 yes

4 BIRTH_PLACE PA0021.FGBOT Birthplace VARCSTR 40 0 0 yes

5 BIRTH_STATE PA0021.FGDEP State VARCSTR 3 0 0 yes



8 DAY_BIRTH PA0021.FGBDT - calculated day of birth DECIMAL 48 4 0 yes

9 EMERGENCY_CONTACT PA0021.EMRGN Emergency Contact VARCSTR 1 0 0 yes


11 FAMILY_RECORD_TYPE_DESCR T591S.STEXT - Subtype Text for PA0021 VARCSTR 40 0 0 yes

12 FAMILY_RECORD_TYPE_ID PA0021.FAMSA Type of Family Record VARCSTR 4 0 0 yes

13 FIRST_NAME PA0021.FAVOR First name VARCSTR 40 0 0 yes

14 FULL_NAME PA0021.FCNAM Complete Name VARCSTR 80 0 0 yes

15 GENDER_DESCR DD07T.DDTEXT Lookup description forGESCH in DD07T VARCSTR 10 0 0 yes

16 GENDER_ID PA0021.FASEX Gender key VARCSTR 1 0 0 yes



17 INITIALS PA0021.FINIT Employee's initials VARCSTR 10 0 0 yes

18 LAST_NAME PA0021.FANAM Last name VARCSTR 40 0 0 yes


20 LOAD_TIME Time when the record was loaded VARCSTR 8 0 0 yes

21 MONTH_BIRTH PA0021.FGBDT - calculated month of birth DECIMAL 48 4 0 yes


T005T.NATIO - Lookup on Nationalitydescritpion VARCSTR 15 0 0 yes





25 NATIONALITY_ID_01 PA0021.FANAT Country of the FirstNationality VARCSTR 3 0 0 yes

26 NATIONALITY_ID_02 PA0021.FANA2 Second Nationality VARCSTR 3 0 0 yes

27 NATIONALITY_ID_03 PA0021.FANA3 Third Nationality VARCSTR 3 0 0 yes

28 OBJ_IDENTIFICTN_CODE PA0021.OBJPS Object Identification VARCSTR 2 0 0 yes

29 PERSON_ID PA0021.PERNR Personnel number VARCSTR 8 0 0 yes

30 PREFIX_NAME_01 PA0021.FVRSW Name Prefix VARCSTR 15 0 0 yes

31 PREFIX_NAME_02 PA0021.FVRS2 Second name prefix VARCSTR 15 0 0 yes

32 SUBTYPE_CODE PA0021.SUBTY Subtype VARCSTR 4 0 0 yes

33 TITLE PA0021.TITEL Title VARCSTR 15 0 0 yes

34 TITLE_OTHER PA0021.FNMZU Title - Other VARCSTR 15 0 0 yes




DECIMAL 48 4 0 yes

36 VALID_FROM_DATE PA0021.BEGDA From DATETIME 24 0 9 yes

37 VALID_TO_DATE PA0021.ENDDA To DATETIME 24 0 9 yes


39 YEAR_BIRTH PA0021.FGBDT - calculated year of birth DECIMAL 48 4 0 yes



HR_INFOTYPE_0022_EDUCATION

HR Master data: Education from Infotype PA0022



Nullable

1 AMT_COST PA0022.JBEZ1 Course fees DECIMAL 48 11 2 yes

2 CERTIFICATE_TYPE_DESCR T519T.STEXT Certificate Type NVARCSTR 50 0 0 yes

3 CERTIFICATE_TYPE_ID PA0022.SLABS Certificate NVARCSTR 2 0 0 yes


5 COUNTRY_ID PA0022.SLAND Country key NVARCSTR 3 0 0 yes

6 COUNTRY_NAME T005T.LANDX - Lookup on Country descritpion NVARCSTR 15 0 0 yes

7 COURSE_APPRAISAL PA0022.TX122 Course appraisal NVARCSTR 40 0 0 yes

8 COURSE_NAME PA0022.KSBEZ Course name NVARCSTR 25 0 0 yes


10 CURR_ID PA0022.WAERS Currency Key NVARCSTR 5 0 0 yes

11 DEPARTMENT_CODE PA0022.DPTMT Department NVARCSTR 40 0 0 yes

12 EDUCATN_TYPE_DESCR

T518B.ATEXT Type of Education/Traningdescritpion lookup NVARCSTR 40 0 0 yes

13 EDUCATN_TYPE_ID PA0022.AUSBI Education/training NVARCSTR 8 0 0 yes


15 FACULTY_CODE PA0022.FACCD Faculty code NVARCSTR 3 0 0 yes

16 FINAL_GRADE PA0022.EMARK Final Mark NVARCSTR 4 0 0 yes







21 QTY_DURATN PA0022.ANZKL Duration of training course INTEGER 4 0 0 yes

22 SCHOOL_CODE PA0022.SCHCD Institute/school code NVARCSTR 10 0 0 yes

23 SCHOOL_LOCATN_NAME PA0022.INSTI Institute/location of training NVARCSTR 80 0 0 yes

24 SCHOOL_TYPE_DESCR

T517T.STEXT Education Establishemtdescritpion lookup NVARCSTR 30 0 0 yes

25 SCHOOL_TYPE_ID PA0022.SLART Educational establishment NVARCSTR 2 0 0 yes

26 STUDY_BRANCH_DESCR

T517X.STEXT Branch of Study descritpionlookup NVARCSTR 40 0 0 yes

27 STUDY_BRANCH_ID PA0022.SLTP1 Branch of study NVARCSTR 5 0 0 yes



30 UOT_ID PA0022.ANZEH Unit of time/measurement NVARCSTR 3 0 0 yes


INTEGER 4 0 0 yes






HR_INFOTYPE_0024_QUALIFICATION

HR infotype Master PA0024 - Personnel Qualifications



Nullable








8 PROFICIENCY_DESCR

T777Q.CHARA_TEXT Qualifiction descriptionlookup NVARCSTR 25 0 0 yes

9 PROFICIENCY_ID PA0024.AUSPR Proficiency of aQualification/Requirement NVARCSTR 4 0 0 yes

10 QUALIFICTN_DESCR T574B.QTEXT Qualification key NVARCSTR 40 0 0 yes

11 QUALIFICTN_ID PA0024.QUALI Qualification key NVARCSTR 8 0 0 yes



INTEGER 4 0 0 yes






HR_INFOTYPE_0041_SPEC

HR Master: date specification inforecord PA0041



Nullable








8 DATE_06 PA0041.DAT06 Date for date type DATETIME 24 0 9 yes

































27 DATE_TYPE_ID_01 PA0041.DAR01 Date type 01 NVARCSTR 2 0 0 yes





















INTEGER 4 0 0 yes






HR_INFOTYPE_0077_PERSONAL

HR Mater for Additional Personal Data from PA0077



Nullable




4 DISABILITY_DATE PA0077.DISDT Date of determination ofdisability status DATETIME 24 0 9 yes

5 DISABILITY_FLAG PA0077.DISAB Person is disabled INTEGER 4 0 0 yes

6 EEO_EXEMPT_FLAG PA0077.EEOEX EEO Exempt Indicator INTEGER 4 0 0 yes

7 ETHNIC_ORIGIN_ID PA0077.RACKY Ethnic origin NVARCSTR 2 0 0 yes





12 MEDICARE_FLAG PA0077.MEDIC Medicare indicator INTEGER 4 0 0 yes

13 MILITARY_STATUS_ID PA0077.MILSA Military status NVARCSTR 2 0 0 yes

14 NOTIFICTN_DATE PA0077.DISLE Date employer learned ofdisability status DATETIME 24 0 9 yes



NVARCSTR 4 0 0 yes




18 RELIGION_ID PA0077.RELGN Religious denomination key NVARCSTR 2 0 0 yes



INTEGER 4 0 0 yes




24 VETERAN_STATUS_CODE PA0077.VETST Veteran status NVARCSTR 1 0 0 yes



HR_INFOTYPE_0094_RESIDENCE

HR Master for Residence status in N/A from PA0094



Nullable





5 IDENTIFICTN_AUTHORITY PA0094.AUTH1 Issuing authority NVARCSTR 30 0 0 yes

6 IDENTIFICTN_DESCR PA0094.FPNID ID type text NVARCSTR 30 0 0 yes

7 IDENTIFICTN_EXPIRE_DATE PA0094.EXPID ID expiry date DATETIME 24 0 9 yes

8 IDENTIFICTN_ISSUE_DATE PA0094.DATE1 Date of issue for personal ID DATETIME 24 0 9 yes

9 IDENTIFICTN_NUM PA0094.DOCN1 Document number forpersonal identification NVARCSTR 20 0 0 yes

10 IDENTIFICTN_TYPE_ID

PA0094.FPNCD Personal ID and work permit(USA) NVARCSTR 2 0 0 yes





15 RESIDENCE_STATUS_ID PA0094.RESIS Residence status NVARCSTR 1 0 0 yes





INTEGER 4 0 0 yes




21 WORK_PERMIT_AUTHORITY PA0094.AUTH2 Issuing authority NVARCSTR 30 0 0 yes

22 WORK_PERMIT_DESCR PA0094.FWORK Work permit type text NVARCSTR 30 0 0 yes

23 WORK_PERMIT_EXPIRE_DATE PA0094.EXPDT Expiry date of work permit DATETIME 24 0 9 yes

24 WORK_PERMIT_ISSUE_DATE PA0094.DATE2 Date of issue for work permit DATETIME 24 0 9 yes

25 WORK_PERMIT_NUM PA0094.DOCN2 Document number for workpermit NVARCSTR 20 0 0 yes

26 WORK_PERMIT_TYPE_ID PA0094.FWOCD Type of work permit NVARCSTR 2 0 0 yes




HR Master: Heallth Plans from Infotype PA0167



Nullable

1 ADDTNL_PROVIDER_NAME PA0167.PROVI Additional benefit provider NVARCSTR 30 0 0 yes

2 ADJUST_REASON_DESCR

LookupT74IA.LTEXT description lookup forbenefits adjustment reason NVARCSTR 20 0 0 yes

3 ADJUST_REASON_ID PA0167.EVENT Benefit adjustment reason NVARCSTR 4 0 0 yes








8 AMT_PROVIDER_COST







Lookup PA0167.BOPTI description in T5UC1 -Benefits Plan Type text NVARCSTR 15 0 0 yes

14 BENFT_PLAN_TYPE_ID PA0167.PLTYP Benefit plan type NVARCSTR 4 0 0 yes





17 COST_RULE_ID T5UBB.BCOST - Benefit Cost Rule Variant NVARCSTR 4 0 0 yes


19 COUNTRY_GRP_ID T5UB3.MOLGA Country grouping (lookup) NVARCSTR 2 0 0 yes


Calculated: Number of dependents covered onhealth plan INTEGER 4 0 0 yes



INTEGER 4 0 0 yes


23 CURR_ID PA0167.CURRE - Benefit Currency Key NVARCSTR 5 0 0 yes

24 DEPENDNT_COVERAGE_DESCR

Lookup DEPCV in T5UCF - Dependentcoverage text NVARCSTR 20 0 0 yes

25 DEPENDNT_COVERAGE_ID

PA0167.DEPCV - Dependent coverage forhealth plan NVARCSTR 4 0 0 yes



27 ELIGIBLTY_RULE_ID PA0167.BELIG - Eligibility rule/Type ofEnrollment ID NVARCSTR 4 0 0 yes


Lookup description for BEN_ENRTYP domainin DD07T NVARCSTR 10 0 0 yes


PA0167.ENRTY - Benefit type of planenrollment NVARCSTR 1 0 0 yes


31 HEALTH_PLAN_DESCR

Lookup PA0167.BOPTI description in T5UCE -Benefits Health Plan Option text NVARCSTR 30 0 0 yes

32 HEALTH_PLAN_ID PA0167.BOPTI Health plan options NVARCSTR 4 0 0 yes







37 OTHER_BENFT_FLAG PA0167.COORD Benefits coordinationindicator/Other Benefits Flag INTEGER 4 0 0 yes



40 POLICY_NUM PA0167.POLNR Policy number NVARCSTR 20 0 0 yes






PA0167.BENGR Employee benefit firstprogram grouping NVARCSTR 4 0 0 yes


PA0167.BSTAT Benefit second programgrouping NVARCSTR 4 0 0 yes


46 TERMINATN_RULE_DESCR


47 TERMINATN_RULE_ID T5UBU.BTERM - Benefit Termination rule NVARCSTR 4 0 0 yes


INTEGER 4 0 0 yes

49 VALID_FROM_DATE PK PA0167.BEGDA End date DATETIME 24 0 9 no






HR Master for Insurance Plans from infotype PA0168



Nullable

1 AMT_ALT_COVERAGE

PA0168.COVOV - Benefit alternative amountfor insurance coverage amount DECIMAL 48 15 2 yes




4 AMT_COVERAGEPA0168.COVOV/ T74FC.COVAM- Coverageamount - Life only when Coverage Group is notdefined. Calculated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes

5 AMT_COVERAGE_MAX

T74FC.MAXAM - Maximum coverage amount.Calculated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 15 2 yes










DECIMAL 48 15 2 yes


T74FC.ADDUN (via functionHR_BEN_GET_RULE_COVERAGE) - BenefitValue of each Unit of Additional InsuranceCoverage

DECIMAL 48 15 2 yes















22 COST_RULE_DESCR Lookup T5UCH.LTEXT lookup on Benefitinsurance cost rule descritpion NVARCSTR 30 0 0 yes

23 COST_RULE_ID T74FA.BCOST Plan cost formula NVARCSTR 4 0 0 yes



26 COUNT_BENEFIC_DEPENDNT Calculated:Number of beneficiaries INTEGER 4 0 0 yes

27 COVERAGE_GRP_DESCR

Lookup T74G2.LTEXT lookup on CoverageGroup descritpion NVARCSTR 20 0 0 yes

28 COVERAGE_GRP_FLAG T74FB.COVIN Indicator for coverage group INTEGER 4 0 0 yes

29 COVERAGE_GRP_ID Lookup Coverage Group using SAPfunction/T74FC.COVGR - Coverage group NVARCSTR 4 0 0 yes

30 COVERAGE_RULE_DESCR

Lookup T74GB.LTEXT lookup on Benefitinsurance coverage rule descritpion NVARCSTR 20 0 0 yes

31 COVERAGE_RULE_ID T74FA.BCOVE Benefits insurance coverageformula NVARCSTR 4 0 0 yes



INTEGER 4 0 0 yes







36 ELIGIBLTY_RULE_ID T5UBU.BELIG - Benefits eligibility rule NVARCSTR 4 0 0 yes







T74GA.LTEXT -Lookup text for BCOVR -Insurance options NVARCSTR 30 0 0 yes

42 INSURANCE_OPTION_ID PA0168.BCOVR - Benefits insurance option NVARCSTR 4 0 0 yes











PA0168.BENGR BSTAT Benefit first programgrouping NVARCSTR 4 0 0 yes


PA0168.BSTAT BSTAT Benefit secondprogram grouping NVARCSTR 4 0 0 yes






T74FC.COVFA - Benefits factor for calculatinginsurance coverage base on Salary(Multiplier).Calculated as a lookup onINSURANCE_COVERAGE_RULE

DECIMAL 48 8 5 yes






INTEGER 4 0 0 yes







HR master data for Savings Plan from Infotype 0169



Nullable

1 ACCOUNT_NUM PA0169.ACCTN - Account number NVARCSTR 20 0 0 yes


3 AMT_POSTTAX_SAVNG


4 AMT_PRETAX_SAVNG



6 BENFT_AREA_ID PA0169.BAREA - Benefit area NVARCSTR 2 0 0 yes


8 BENFT_PLAN_ID PA0169.BPLAN - Benefit plan NVARCSTR 4 0 0 yes



10 BENFT_PLAN_TYPE_ID PA0169.PLTYP - Benefit plan type NVARCSTR 4 0 0 yes


12 CHANGE_DATE PA0169.AEDTM - Last changed on DATETIME 24 0 9 yes

13 CONTRIBTN_RULE_DESCR_EMPLEE

Lookup T74GE.LTEXT - Contribution Variantdescription (Employee) NVARCSTR 20 0 0 yes

14 CONTRIBTN_RULE_DESCR_EMPLER

Lookup T74GE.LTEXT - Contribution Variantdescription (Employer) NVARCSTR 20 0 0 yes


T74FD. EECON Benefits employeecontribution rule NVARCSTR 4 0 0 yes

16 CONTRIBTN_RULE_ID_EMPLER T74FD.ERCON - Employer contribution rule NVARCSTR 4 0 0 yes










23 ELIGIBLTY_RULE_ID T5UBU.BELIG - Eligibility rule NVARCSTR 4 0 0 yes




PA0169.ENRTY Benefit type of planenrollment NVARCSTR 1 0 0 yes



28 INVESTMNT_GRP_DESCR

Lookup T5UCO.LTEXT - Benefit investmentgroup texts NVARCSTR 20 0 0 yes

29 INVESTMNT_GRP_ID T74FD.INVGR - Savings plans investmentgroup NVARCSTR 4 0 0 yes



DECIMAL 48 4 1 yes

31 INVESTMNT_PLAN_DESCR_01

LookupT5UCN.LTEXT - Investments 01 forsavings plans description NVARCSTR 20 0 0 yes




























INTEGER 4 0 0 yes











56 PROGRAM_GRP_ID_01 PA0169.BENGR - Employee benefit first group NVARCSTR 4 0 0 yes

57 PROGRAM_GRP_ID_02 PA0169.BSTAT - Benefit Program Grouping 2 NVARCSTR 4 0 0 yes



59 SUBTYPE_CODE PK PA0169.SUBTY - Subtype NVARCSTR 4 0 0 no

60 TERMINATN_RULE_DESCR




INTEGER 4 0 0 yes

63 VALID_FROM_DATE PK PA0169.BEGDA - Start date DATETIME 24 0 9 no

64 VALID_TO_DATE PK PA0169.ENDDA - End date DATETIME 24 0 9 no


66 VESTNG_RULE_DESCR Lookup T5UCR.LTEXT - Vesting text NVARCSTR 20 0 0 yes

67 VESTNG_RULE_ID T74FD.VESTI - Vesting rules for employeecontributions to savings plans NVARCSTR 4 0 0 yes



HR_INFOTYPE_0170_FLEX

HR Master data for Flexible Spending Accounts from infotype PA0170



Nullable


PA0170.CAMNT - Employee contributionamount to spending account DECIMAL 48 13 2 yes









9 CHANGE_DATE PA0170.CAMNT - Employee contributionamount to spending account DATETIME 24 0 9 yes

10 COUNTRY_GRP_DESCR T005T.LANDX Country Name (lookup) NVARCSTR 15 0 0 yes






15 ELIGIBLTY_RULE_ID T5UBU.BELIG - Benefit eligibility rule NVARCSTR 4 0 0 yes


















PA0170.BENGR Employee benefit programfirst group NVARCSTR 4 0 0 yes


PA0170.BSTAT Employee benefit programsecond group NVARCSTR 4 0 0 yes


30 TERMINATN_RULE_ID T5UBU.BTERM - Benefit termination rule NVARCSTR 4 0 0 yes




INTEGER 4 0 0 yes


34 VALID_TO_DATE PK PA0170 - Calculated End Date DATETIME 24 0 9 no



HR_INFOTYPE_0171_BENEFIT

HR Master data for General Benefits from infotype PA0171



Nullable




















18 PHYSICIAN_NAME PA0171.DOCN1 Name of physician NVARCSTR 30 0 0 yes

19 PHYSICIAN_NUM PA0171.DOCI1 Physician ID NVARCSTR 20 0 0 yes





22 PROGRAM_GRP_ID_01 PA0171.BENGR Employee benefit group o1 NVARCSTR 4 0 0 yes


PA0171.BSTAT Benefit Program secondgrouping NVARCSTR 4 0 0 yes





INTEGER 4 0 0 yes






HR_INFOTYPE_0236_CREDIT

HR Master data for Credit Plans from infotype PA0236



Nullable








7 BENFT_PLAN_TYPE_ID PA0236.PLTYP Plan type NVARCSTR 4 0 0 yes









15 ELIGIBLTY_RULE_ID T5UBU. BELIG Eligibility rule NVARCSTR 4 0 0 yes


















PA0236.BENGR Employee benefit programfirst grouping NVARCSTR 4 0 0 yes


PA0236.BSTAT- Benefit program secondgrouping NVARCSTR 4 0 0 yes


30 TERMINATN_RULE_ID T5UBU.BTERM - Termination rule NVARCSTR 4 0 0 yes




INTEGER 4 0 0 yes





HR_INFOTYPE_1000_DBTABLE

HR Master data forOrganizational unit descriptions from the active plan from HPA1000 infotype



Nullable

1 CHANGE_DATE HRP1000.AEDTM Changed on DATETIME 24 0 9 yes



4 HIST_RECORD_FLAG HRP1000.HISTO Historical record flag INTEGER 4 0 0 yes

5 INFOTYPE_ID Hard-coded value HRP1000 NVARCSTR 7 0 0 yes



8 OBJ_ID PK HRP1000.OBJID Object ID NVARCSTR 8 0 0 no

9 OBJ_ID_FULL HRP1000.OTJID Concatenation of object typeand object ID NVARCSTR 10 0 0 yes

10 OBJ_NAME HRP1000.STEXT Object name NVARCSTR 40 0 0 yes

11 OBJ_NAME_SEARCH HRP1000.MC_SEARK Search string NVARCSTR 52 0 0 yes

12 OBJ_NAME_SHORT HRP1000.SHORT Object abbreviation NVARCSTR 12 0 0 yes

13 OBJ_TYPE_DESCR Lookup T777O.OTEXT description for ObjectType from T7770 NVARCSTR 25 0 0 yes

14 OBJ_TYPE_ID PK HRP1000.OTYPE Object type NVARCSTR 2 0 0 no

15 VALID_FLAG Valid record or not (1/0) - 0 - duplicate onvalidity dates INTEGER 4 0 0 yes

16 VALID_FROM_DATE PK HRP1000.BEGDA Start date DATETIME 24 0 9 no



17 VALID_TO_DATE PK HRP1000.ENDDA End date DATETIME 24 0 9 no

18 VALID_TO_DATE_PREV HRP1000.BEGDA Start date - 1 DATETIME 24 0 9 yes




HR master data - hr objects details from infotype HRP1001



Nullable










10 OBJ_ID_PAR HRP1001.SOBID ID of the related object NVARCSTR 45 0 0 yes


12 OBJ_TYPE_DESCR_PAR

Lookup T777O.OTEXT description for therelated Object Type from T7770 NVARCSTR 25 0 0 yes


14 OBJ_TYPE_ID_PAR HRP1001.SCLAS Type of related object NVARCSTR 2 0 0 yes

15 PLOG_VARIATION_FIELD PK HRP1001.VARYF Variation field for file PLOG NVARCSTR 10 0 0 no

16 PRCNT_WEIGHT HRP1001.PROZT Weighting percentage DECIMAL 48 5 2 yes



17 PRIORITY_CODE PK HRP1001.PRIOX Priority NVARCSTR 2 0 0 no

18 RELATIONSHIP_DESCR Lookup HRP1001.RTEXT - Relationship Text NVARCSTR 25 0 0 yes

19 RELATIONSHIP_ID PK HRP1001.RELAT Relationship betweenobjects NVARCSTR 3 0 0 no

20 RELATIONSHIP_TYPE_DESCR

Lookup description for RSIGN domain inDD07T NVARCSTR 60 0 0 yes

21 RELATIONSHIP_TYPE_ID PK HRP1001.RSIGN Relationship specification NVARCSTR 1 0 0 no

22 SUBTYPE_DESCR Lookup T777U.SUTXT - Subtype Text NVARCSTR 25 0 0 yes

23 SUBTYPE_ID HRP1001.SUBTY Subtype NVARCSTR 4 0 0 yes







HR master data - hr objects details from infotype HRP1007



Nullable












12 VACANCY_STATUS_DESCR Lookup text for vacancy status NVARCSTR 10 0 0 yes

13 VACANCY_STATUS_ID HRP1007.STATUS Status of vacancy NVARCSTR 1 0 0 yes

14 VALID_FLAG Valid record or not (1/0) - 0 - duplicate onvalidity dates INTEGER 4 0 0 yes






HR_INFOTYPE_VALIDATIONDistinct Merge of date-effective records works only when there is a single valid record stored in the source system (unique by Valid FromDate or unique by Valid To Date)



Nullable



3 INFOTYPE_ID PK Hard-coded value in PA<xxxx> format NVARCSTR 6 0 0 no



6 OBJ_IDENTIFICTN_CODE PK PA0005.OBJPS Object Identification NVARCSTR 2 0 0 no



9 VALID_FLAG Set to 1 if the record is unique for the effectiveperiod INTEGER 4 0 0 yes



12 VALID_TO_DATE_CALC

The date until which this record is effective. It isautomatically generated by the Effective_Datetransform

DATETIME 24 0 9 yes



IDENTIFICATION_TYPE

Employee Identification type descriptive attributes from T509G; load IDENTIFICATION_TYPE dimension



Nullable


2 COUNTRY_GRP_ID PK T509G.MOLGA Country Grouping NVARCSTR 2 0 0 no

3 IDENTIFICTN_TYPE_DESCR T509G.IDTEX ID type text NVARCSTR 30 0 0 yes

4 IDENTIFICTN_TYPE_ID PK T509G.IDCOD Personal ID and work permit

(USA) NVARCSTR 2 0 0 no




Insurance coverage grouping descriptive attributes from T74G2; load INSURANCE_COVERAGE_GROUP dimension



Nullable


2 BENFT_AREA_ID PK T74G2.BAREA Benefit area NVARCSTR 2 0 0 no


T74G2.LTEXT Benefit insurance coveragegrouping text NVARCSTR 20 0 0 yes

4 COVERAGE_GRP_FULL_NAME

Concatenated: T74G2.COVGR Benefitinsurance coverage grouping + T74G2.LTEXTBenefit insurance coverage grouping text

NVARCSTR 30 0 0 yes

5 COVERAGE_GRP_ID PK T74G2.COVGR Benefit insurance coveragegrouping NVARCSTR 4 0 0 no






Benefit insurance coverage rules and formulas from T74FB, T74FC, PA0168 (date-effective)



Nullable

1 AGE_GRP_DESCR Lookup T5UCL.LTEXT lookup on Benefit agedgroup descritpion NVARCSTR 20 0 0 yes

2 AGE_GRP_ID PK T74FC.AGEGR - Age Group NVARCSTR 4 0 0 no

3 AGE_MAX Lookup T5UBL maximum age in age group orset to 99 if no maximum specified INTEGER 4 0 0 yes

4 AGE_MIN Lookup T5UBL minimum age in age group orset to 0 if no minimum specified INTEGER 4 0 0 yes

5 AMT_COVERAGE T74FC.COVAM - Coverage amount DECIMAL 48 15 2 yes

6 AMT_COVERAGE_MAX T74FC.MAXAM - Maximum coverage amount DECIMAL 48 15 2 yes

7 AMT_COVERAGE_MIN T74FC.MINAM - Minimum coverage amount DECIMAL 48 15 2 yes

8 AMT_SALARY_MAX Lookup T5UBK max salary in salary group orset to big number if no maximum specified DECIMAL 48 15 2 yes

9 AMT_SALARY_MIN Lookup T5UBK minimum salary in salary groupor set to 0 if no minimum specified DECIMAL 48 15 2 yes


11 BENFT_AREA_ID PK T74FC.BAREA - Benefit area NVARCSTR 2 0 0 no


13 BENFT_PLAN_ID PK T74FC.BPLAN - Benefit plan NVARCSTR 4 0 0 no

14 COVERAGE_FLAG T74FB.COVIN- Benefits indicator for insurancecoverage group (1/0) DECIMAL 48 10 2 yes


Lookup T74G2.LTEXT lookup on CoverageGroup descritpion NVARCSTR 20 0 0 yes

16 COVERAGE_GRP_ID PK T74FC.COVGR - Coverage group NVARCSTR 4 0 0 no




Lookup T74GB.LTEXT lookup on Benefitinsurance coverage rule descritpion NVARCSTR 20 0 0 yes

18 COVERAGE_RULE_FULL_NAME

Concatenated: T74FC.BCOVE - Insurancecoverage formula (rule) + LookupT74GB.LTEXT lookup on Benefit insurancecoverage rule descritpion

NVARCSTR 30 0 0 yes

19 COVERAGE_RULE_ID PK T74FC.BCOVE - Insurance coverage formula(rule) NVARCSTR 4 0 0 no


21 CURR_ID Lookup T5UBY.CURRE lookup on CurrencyKey NVARCSTR 5 0 0 yes




25 PARAMETER_GRP_DESCR

Lookup T5UCY.LTEXT lookup on Cost groupdescritpion NVARCSTR 20 0 0 yes

26 PARAMETER_GRP_ID T74FB.CRGRP Cost/credit group criteria ID NVARCSTR 4 0 0 yes


T74FC.COVFA - Benefits factor for calculatinginsurance coverage base on Salary(Multiplier) DECIMAL 48 8 5 yes

28 SALARY_GRP_DESCR

Lookup T5UCK.LTEXT lookup on Salary groupdescritpion NVARCSTR 20 0 0 yes

29 SALARY_GRP_ID PK T74FC.SALGR - Salary group NVARCSTR 4 0 0 no

30 SENIORITY_GRP_DESCR

Lookup T5UCM.LTEXT lookup on BenefitSeniority group descritpion NVARCSTR 20 0 0 yes

31 SENIORITY_GRP_ID PK T74FC.LOSGR - Length of service group NVARCSTR 4 0 0 no

32 SENIORITY_MAX Lookup T5UBM maximum LOS in LOS groupor set to 999 if no maximum specified INTEGER 4 0 0 yes

33 SENIORITY_MIN Lookup T5UBM minimum LOS in LOS group orset to 0 if no minimum specified INTEGER 4 0 0 yes

34 VALID_FROM_DATE PK T74FC.BEGDA - Beginning effective date DATETIME 24 0 9 no



35 VALID_TO_DATE T74FC.ENDDA - Ending effective date DATETIME 24 0 9 yes

36 VALID_TO_DATE_PREV T74FC.BEGDA Start date - 1 DATETIME 24 0 9 yes



INSURANCE_OPTION

Benefits - Insurance Option date-effective attributes from T74FA, T74GA; load INSURANCE_OPTION dimension



Nullable

1 BENFT_AREA_DESCR T5UC3.LTEXT - lookup on Benefit Areadescription VARCSTR 30 0 0 yes

2 BENFT_AREA_ID T74FA.BAREA Benefit area VARCSTR 2 0 0 yes

3 BENFT_PLAN_DESCR Lookup PA0167.BOPTI description in T5UCA -Benefits Plan text VARCSTR 30 0 0 yes

4 BENFT_PLAN_ID T74FA.BPLAN Benefit plan VARCSTR 4 0 0 yes

5 COST_RULE_DESCR T5UCH.LTEXT Text (30 Characters) VARCSTR 30 0 0 yes

6 COST_RULE_ID T74FA.BCOST Plan cost formula VARCSTR 4 0 0 yes


Lookup T74GB.LTEXT lookup on Benefitinsurance coverage rule descritpion VARCSTR 20 0 0 yes

8 COVERAGE_RULE_ID T74FA.BCOVE Benefits insurance coverageformula VARCSTR 4 0 0 yes



T74GA.LTEXT Benefits insurance coveragelevel text VARCSTR 30 0 0 yes

11 INSURANCE_OPTION_FULL_NAME

Concatenated: T74FA.BCOVR Benefitsinsurance option+ T74GA.LTEXT Benefitsinsurance coverage level text

NVARCSTR 40 0 0 yes

12 INSURANCE_OPTION_ID T74FA.BCOVR Benefits insurance option VARCSTR 4 0 0 yes

13 INSURANCE_OPTION_KEY PK Surrogate key generated for date-effective

INSURANCE_OPTION_KEY dimension DECIMAL 48 28 0 no


15 LOAD_TIME Time Loaded into Rapid mart VARCSTR 8 0 0 yes

16 VALID_FROM_DATE T74FA.BEGDA Start date DATETIME 24 0 9 yes



17 VALID_TO_DATE T74FA.ENDDA End date DATETIME 24 0 9 yes

INVESTMENT_GROUP

Benefit-related employee investment group descriptive attributes from T5UCO; load INVESTMENT_GROUP dimension



Nullable


2 BENFT_AREA_ID PK T5UCO.BAREA Benefit area NVARCSTR 2 0 0 no

3 INVESTMNT_GRP_DESCR T5UCO.LTEXT Text, 20 characters NVARCSTR 20 0 0 yes

4 INVESTMNT_GRP_FULL_NAME

Concatenated: T5UCO.INVGR Benefit savingsplan investment group + T5UCO.LTEXT Text,20 characters

NVARCSTR 30 0 0 yes

5 INVESTMNT_GRP_ID PK T5UCO.INVGR Benefit savings planinvestment group NVARCSTR 4 0 0 no





INVESTMENT_PLAN

Benefit Investment plan descriptive attributes from T5UCN; load INVESTMENT_PLAN dimension



Nullable


2 BENFT_AREA_ID PK T5UCN.BAREA Benefit area NVARCSTR 2 0 0 no

3 INVESTMNT_PLAN_DESCR T5UCN.LTEXT Text, 20 characters NVARCSTR 20 0 0 yes

4 INVESTMNT_PLAN_FULL_NAME

Concatenated: T5UCN.INVES BenefitInvestment for Savings Plans + T5UCN.LTEXTText, 20 characters

NVARCSTR 30 0 0 yes

5 INVESTMNT_PLAN_ID PK T5UCN.INVES Benefit Investment for SavingsPlans NVARCSTR 4 0 0 no





JOB

Job master data from T5U13; HRP1000; date-effective records are merged as distinct union



Nullable

1 AAP_CATEG_DESCR Lookup T5UAA.LTEXT -AAP categorydescription (Job Class) NVARCSTR 100 0 0 yes

2 AAP_CATEG_ID T5U13.AAPCT - AAP (Affirmative ActionPlanning) Category (Job CLASS) NVARCSTR 4 0 0 yes

3 CURRENT_FLAG 1 indicates record is currently in effect INTEGER 4 0 0 yes

4 EEO_JOB_CATEG_DESCR

Lookup EEOCT in T5UEE - Equal Opportunitycategory description NVARCSTR 30 0 0 yes

5 EEO_JOB_CATEG_ID T5U13.EEOCT - Equal Employee OpportunityJob category ID NVARCSTR 2 0 0 yes

6 EXEMPT_FLAG T5U13.EXMPT - Indicator:Exempt/non-exempt - 1/0 INTEGER 4 0 0 yes

7 EXEMPT_STATUS_DESCR

T5U13.EXMPT Indicator: Exempt/non-exempt.Values are: EXCEMPT/NON_EXECMPT NVARCSTR 10 0 0 yes

8 EXEMPT_STATUS_ID T5U13.EXMPT Indicator: Exempt/non-exempt NVARCSTR 2 0 0 yes

9 JOB_DESCR HRP1000.STEXT - Job title (name) NVARCSTR 40 0 0 yes

10 JOB_DESCR_SEARCH

HRP1000.MC_SEARK - Job description textfor selecting and searching NVARCSTR 52 0 0 yes

11 JOB_DESCR_SHORT HRP1000.SHORT - Short job description NVARCSTR 12 0 0 yes

12 JOB_FULL_NAME Concatenated: HRP1000.OBJID - Job ID +HRP1000.STEXT - Job title (name) NVARCSTR 60 0 0 yes

13 JOB_ID HRP1000.OBJID - Job ID NVARCSTR 8 0 0 yes

14 JOB_KEY PK Generated Surrogate key for Job DECIMAL 48 28 0 no





17 PAYSCALE_GRP_CODE

T5U13.GRADE - Payscale group (jobclassification) NVARCSTR 8 0 0 yes

18 VALID_FROM_DATE TRP1000/T5U13.BEGDA - Combined tablebeginning date DATETIME 24 0 9 yes

19 VALID_TO_DATE BEGDA - Combined table einding date DATETIME 24 0 9 yes



JOB_STAGE

Jobs descriptive attributes from T5U13; load JOB_STAGE as date-effective intermediate table to load JOB dimension



Nullable

1 AAP_CATEG_DESCR Lookup T5UAA.LTEXT -AAP categorydescription (Job Class) NVARCSTR 100 0 0 yes

2 AAP_CATEG_ID T5U13.AAPCT - AAP (Affirmative ActionPlanning) Category (Job CLASS) NVARCSTR 4 0 0 yes


4 EEO_JOB_CATEG_DESCR

Lookup EEOCT in T5UEE - Equal Opportunitycategory description NVARCSTR 30 0 0 yes

5 EEO_JOB_CATEG_ID T5U13.EEOCT - Equal Employee OpportunityJob category ID NVARCSTR 2 0 0 yes

6 EXEMPT_FLAG T5U13.EXMPT - Indicator:Exempt/non-exempt - 1/0 INTEGER 4 0 0 yes

7 EXEMPT_STATUS_DESCR

T5U13.EXMPT Indicator: Exempt/non-exempt.Values are: EXCEMPT/NON_EXECMPT NVARCSTR 10 0 0 yes

8 EXEMPT_STATUS_ID T5U13.EXMPT Indicator: Exempt/non-exempt NVARCSTR 2 0 0 yes


10 INFOTYPE_ID Hard-coded value T5U13 NVARCSTR 6 0 0 yes

11 JOB_ID PK T5U13.STELL Job NVARCSTR 8 0 0 no



14 PAYSCALE_GRP_CODE

T5U13.GRADE - Payscale group (jobclassification) NVARCSTR 8 0 0 yes

15 SRC_TBL PK Indicates if record is sourced from SAP tableT5U13 or T513 NVARCSTR 6 0 0 no

16 VALID_FROM_DATE PK T5U13.BEGDA From DATETIME 24 0 9 no



17 VALID_TO_DATE PK T5U13.ENDDA To DATETIME 24 0 9 no

18 VALID_TO_DATE_PREV T5U13.BEGDA Start date - 1 DATETIME 24 0 9 yes

LANGUAGE

Language (key) descriptive attributes from T002T load LANGUAGE dimension



Nullable

1 LANG_DESCR T002T.SPTXT Language NVARCSTR 16 0 0 yes

2 LANG_ID PK T002T.SPRSL Language Key NVARCSTR 1 0 0 no





LEAVE_DEDUCTION

Deduction detailed data from PCL1 where RELID = PC - Personal Calendar



Nullable

1 CALENDAR_YEAR PCL1.KJAHR -Calendar Year for leavededuction INTEGER 4 0 0 yes

2 CHANGE_DATE PCL1.AEDTM - Change Date DATETIME 24 0 9 yes


4 DAYS_LEAVE PURLT.ANZH1 - Amount DECIMAL 48 28 2 yes

5 HOURS_LEAVE PURLT.ANZHL - AMount DECIMAL 48 28 2 yes

6 LEAVE_DATE PK PURLT.DATUM Date DATETIME 24 0 9 no

7 LEAVE_TYPE_CODE PURLT.URART - Type of Leave NVARCSTR 2 0 0 yes

8 LEAVE_TYPE_DESCR T533T.URTXT - Lookup on Leave typedescritpion NVARCSTR 20 0 0 yes

9 LEAVE_TYPE_GRP_CODE T533T.MOURA - Leave Type Group NVARCSTR 2 0 0 yes

10 LEAVE_TYPE_KEY PK Key to Leave Description table NVARCSTR 4 0 0 no

11 LEAVE_YEAR PK PRULT.URLJJ - Leave year INTEGER 4 0 0 no



14 OBJ_IDENTIFICTN_CODE PK PC1.OBJPS Object identification NVARCSTR 2 0 0 no

15 PERSON_ID PK PCL1.PERNR - Personnel Number NVARCSTR 8 0 0 no




Empoyee Leave Entitlement date-effective details from PA0005 and PA0001



Nullable

1 ADMIN_GRP_CODE PK PA0001.SBMOD Administrator group NVARCSTR 4 0 0 no

2 ADMIN_ID_HR PK PA0001.SACHP Administrator for HR masterdata NVARCSTR 3 0 0 no

3 ADMIN_ID_PAYROLL PK PA0001.SACHA Payroll administrator NVARCSTR 3 0 0 no

4 ADMIN_ID_TIME PK PA0001.SACHZ Administrator for timerecording NVARCSTR 3 0 0 no

5 AMT_LEAVE_ACCOUNTED

PA0005.UAB01-6 Leave days accounted(Hours or Days) DECIMAL 48 28 5 yes

6 AMT_LEAVE_ENTITLMNT

PA0005.UAN01- 6 Leave entitlement (Hours orDays) Leave type 01-06 DECIMAL 48 28 5 yes

7 BUS_AREA_ID PK PA0001.GSBER Business area NVARCSTR 4 0 0 no


9 CONTRACT_ID PK PA0001.ANSVH Work contract (grouping forstatistical reporting) NVARCSTR 2 0 0 no


11 COUNTRY_GRP_ID PK T500P.MOLGA - Country Name - LookupMOLGA from T500P NVARCSTR 2 0 0 no

12 COUNT_WRKDAYCalculated as count of number of working daysfrom WORKING_CALENDAR dimension basedon LEAVE_START_DATE andLEAVE_END_DATE

DECIMAL 48 28 0 yes



15 DAYS_LEAVE_DEDUCT

PURLT.ANZH1 - Amount - Deducted Leave inDays DECIMAL 48 28 2 yes

16 EMPLOYEE_GRP_ID PK PA0001.PERSG Employee group NVARCSTR 1 0 0 no



17 EMPLOYEE_KEY EMPLOYEE.EMPLOYEE_KEY - lookup on theEmployee Key DECIMAL 48 28 0 no

18 EMPLOYEE_KEY_MGR

LINE_MANAGER_HIER.EMPLOYEE_KEY -lookup on the Manager Employee Key DECIMAL 48 28 0 no



NVARCSTR 1 0 0 yes

20 EMPLOYEE_SUBGRP_ID PK PA0001.PERSK Employee subgroup NVARCSTR 2 0 0 no



23 HOLIDAY_CALENDAR_ID PK T001P.MOFID Public holiday calendar ID

(THOC) NVARCSTR 2 0 0 no

24 HOURS_LEAVE_DEDUCT

PURLT.ANZHL - AMount - Deducted leave inHours DECIMAL 48 28 2 yes


26 JOB_KEY PK JOB.JOB_KEY - lookup on the Job Key DECIMAL 48 28 0 no

27 LEAVE_END_DATE PA0005.UEN01-6 To date of leave for LeaveType 1-6 DATETIME 24 0 9 no

28 LEAVE_SEQ_ID PK Concatenation of OBJPS and "01" for leave 1 -sequence for each leave year NVARCSTR 4 0 0 no

29 LEAVE_START_DATE PK PA0005.UBE01-6 Leave begin date for LeaveType 01-06 DATETIME 24 0 9 no

30 LEAVE_TYPE_CODE PA0005.UAR01-06 Leave type 01-06 NVARCSTR 2 0 0 yes


T001P.MOURA Personnel subarea groupingfor leave types (lookup) NVARCSTR 2 0 0 yes

32 LEAVE_TYPE_KEY PK T001P.MAURA + UAR01/06 - Key toLEAVE_TYPE dimension (concatenated key) NVARCSTR 4 0 0 no

33 LEAVE_YEAR PK PA0005.SUBTY Subtype (Leave Year) - innumeric format DECIMAL 48 28 0 no





36 OBJ_IDENTIFICTN_CODE PA0005.OBJPS Object identification NVARCSTR 2 0 0 yes

37 ORG_KEY_ID PK PA0001.VDSK1 Organizational key NVARCSTR 14 0 0 no


39 ORG_UNIT_KEY PK ORGANIZATION_UNIT.ORG_UNIT_KEY -lookup on the Org Unit Key DECIMAL 48 28 0 no

40 PAYROLL_AREA_ID PK PA0001.ABKRS Payroll area NVARCSTR 2 0 0 no




NVARCSTR 8 0 0 no

44 PERSON_ID_MGR LINE_MANAGER_HIER.PERSON_ID -Manager Personnel ID (lookup) NVARCSTR 8 0 0 yes



NVARCSTR 8 0 0 yes


47 POSITION_KEY PK POSITION.POSITION_KEY - lookup on thePostiion Key DECIMAL 48 28 0 no




EMPLOYEE.VALID_FROM_DATE - lookup onStart Effective Date of EMPLOYEE dimensionrecords

DATETIME 24 0 9 yes


JOB.VALID_FROM_DATE - lookup on StartEffective Date of JOB dimension records DATETIME 24 0 9 yes

52 VALID_FROM_DATE_LEAVE PA0005.BEGDA From DATETIME 24 0 9 yes



53 VALID_FROM_DATE_ORG

ORGANIZATION_UNIT.VALID_FROM_DATE -lookup on Start Effective Date ofORGANIZATION_UNIT dimension records

DATETIME 24 0 9 yes


POSITION.VALID_FROM_DATE - lookup onStart Effective Date of POSITION dimensionrecords

DATETIME 24 0 9 yes




EMPLOYEE.VALID_TO_DATE - lookup onEnd Effective Date of EMPLOYEE dimensionrecords

DATETIME 24 0 9 yes

58 VALID_TO_DATE_JOB JOB.VALID_TO_DATE - lookup on EndEffective Date of JOB dimension records DATETIME 24 0 9 yes

59 VALID_TO_DATE_LEAVE PA0005.ENDDA To DATETIME 24 0 9 yes

60 VALID_TO_DATE_ORG

ORGANIZATION_UNIT.VALID_TO_DATE -lookup on End Effective Date ofORGANIZATION_UNIT dimension records

DATETIME 24 0 9 yes


POSITION.VALID_TO_DATE - lookup on EndEffective Date of POSITION dimension records DATETIME 24 0 9 yes




LEAVE_ENTITLEMENT_STAGECalculate number of working days during Start and End Leave period based on WORKING_CALENDAR dimension + Aggreated Deductiondays and Hours for the same period from LEAVE



Nullable

1 AMT_LEAVE_ACCOUNTED

PA0005.UAB01-6 Leave days accounted(Hours or Days) DECIMAL 48 28 5 yes

2 AMT_LEAVE_ENTITLMNT

PA0005.UAN01- 6 Leave entitlement (Hours orDays) Leave type 01-06 DECIMAL 48 28 5 yes

3 COUNT_WRKDAYCalculated as count of number of working daysfrom WORKING_CALENDAR dimension basedon LEAVE_START_DATE andLEAVE_END_DATE

DECIMAL 48 28 0 yes


5 DAYS_LEAVE_DEDUCT

PURLT.ANZH1 - Amount - Deducted Leave inDays DECIMAL 48 28 2 yes

6 HOURS_LEAVE_DEDUCT

PURLT.ANZHL - AMount - Deducted leave inHours DECIMAL 48 28 2 yes

7 LEAVE_END_DATE PA0005.UEN01-6 To date of leave for LeaveType 1-6 DATETIME 24 0 9 yes

8 LEAVE_SEQ_ID PK Concatenation of OBJPS and "01" for leave 1 -sequence for each leave year NVARCSTR 4 0 0 no

9 LEAVE_START_DATE PA0005.UBE01-6 Leave begin date for LeaveType 01-06 DATETIME 24 0 9 yes

10 LEAVE_TYPE_KEY PK T001P.MAURA + UAR01/06 - Key toLEAVE_TYPE dimension (concatenated key) NVARCSTR 4 0 0 no

11 LEAVE_YEAR PK PA0005.SUBTY Subtype (Leave Year) - innumeric format DECIMAL 48 28 0 no




NVARCSTR 8 0 0 no





LEAVE_TYPE

Job leave type descriptive attributes from T533T



Nullable

1 LEAVE_TYPE_CODE T533T.URART - Leave type NVARCSTR 2 0 0 yes

2 LEAVE_TYPE_DESCR T533T.URTXT - Leave Type description NVARCSTR 20 0 0 yes


T533T.URMO - Personnel subarea groupingfor leave types NVARCSTR 2 0 0 yes

4 LEAVE_TYPE_KEY PKLeave Type concatenated key(URMO +URART) based on leave type group and leavetype

NVARCSTR 4 0 0 no





LINE_MANAGER_HIER

Org Unit -> Manager Positon/Personnel relationship from HRP1001 infotype (based on Belongs To and Managers Relationship codes)



Nullable


2 EMPLOYEE_KEY EMPLOYEE.EMPLOYEE_KEY - lookup on theEMPLOYEE dimension surrogate key DECIMAL 48 28 0 yes




6 MANAGER_FLAG Set to 1 if the position is a Managementpostion for the related Organizational unit INTEGER 4 0 0 yes

7 ORG_UNIT_DESCR T527X.ORGTX - Org Unit Descr Descr(lookup) NVARCSTR 25 0 0 yes



10 POSITION_DESCR T528T.PLSTX - Position Descr Descr(lookup) NVARCSTR 25 0 0 yes

11 POSITION_ID PK HRP1001.OBJID Object ID NVARCSTR 8 0 0 no

12 POSITION_KEY POSITION.POSITION_KEY - lookup on thedimension surrogate key DECIMAL 48 28 0 yes

13 VALID_FROM_DATE PK HRP1001/HRP1000.BEGDA - Begin Date DATETIME 24 0 9 no

14 VALID_TO_DATE PK HRP1001/HRP1000.ENDDA - Begin Date DATETIME 24 0 9 no




MARITAL_STATUS

Marital Status descriptive attributes from T502T; load MARITAL_STATUS dimension



Nullable



3 MARITAL_STATUS_DESCR T502T.FTEXT Marital Status NVARCSTR 6 0 0 yes

4 MARITAL_STATUS_ID PK T502T.FAMST Marital Status Key NVARCSTR 1 0 0 no

MILITARY_STATUS

Military Status descriptive attributes from T505N; load MILITARY_STATUS dimension



Nullable


2 COUNTRY_GRP_ID PK T505N.MOLGA Country grouping NVARCSTR 2 0 0 no



5 MILITARY_STATUS_DESCR T505N.LTEXT Text length 25 NVARCSTR 25 0 0 yes

6 MILITARY_STATUS_ID PK T505N.MILSA Military status NVARCSTR 2 0 0 no



NATIONALITY

Nationality attributes from T005T (such as Nationality); load NATIONALITY dimension



Nullable

1 COUNTRY_NAME T005T.LANDX Country name NVARCSTR 15 0 0 yes



4 NATIONALITY_ID PK T005T.LAND1 Country key NVARCSTR 3 0 0 no

5 NATIONALITY_NAME T005T.NATIO Nationality Name NVARCSTR 15 0 0 yes

ORGANIZATION_KEY

Organization structure (key) descriptive attributes from T527O; load ORGANIZATION_KEY dimension



Nullable

1 ELEMENT_TYPE_CODE

T527O.NODTY Org.element type: J: AssignpersonnelN: Do not assign personnel

NVARCSTR 1 0 0 yes



4 ORG_ELEMENT_DESCR T527O.TEXT2 Name of organizational element NVARCSTR 40 0 0 yes

5 ORG_ELEMENT_NAME

T527O.TEXT1 Abbreviation for OrganizationalElement NVARCSTR 10 0 0 yes

6 ORG_KEY_ID PK T527O.ORGKY Organizational Key NVARCSTR 14 0 0 no



ORGANIZATION_UNIT

Organizational Units descriptive attributes from HRP1000 infotype



Nullable




4 ORG_UNIT_DESCR HRP1000.STEXT - Org Unit Name NVARCSTR 40 0 0 yes

5 ORG_UNIT_DESCR_SEARCH HRP1000.MC_SEARK Search string NVARCSTR 52 0 0 yes

6 ORG_UNIT_DESCR_SHORT HRP1000.SHORT Object abbreviation NVARCSTR 12 0 0 yes

7 ORG_UNIT_FULL_NAME

Concatenated: HRP1000.OBJID - Org Unit ID+ HRP1000.STEXT - Org Unit Name NVARCSTR 60 0 0 yes

8 ORG_UNIT_ID HRP1000.OBJID - Org Unit ID NVARCSTR 8 0 0 yes

9 ORG_UNIT_KEY PK Generated Surrogate key for Org Unit DECIMAL 48 28 0 no

10 VALID_FROM_DATE HRP1000.BEGDA - Beginning effective date DATETIME 24 0 9 yes

11 VALID_TO_DATE HRP1000.ENDDA - Ending effective date DATETIME 24 0 9 yes



ORGANIZATION_UNIT_HIER

Organization Unit hierarchy as parent/child relationship from Infotype HRP1001 (DB Table)



Nullable

1 CHILD_DESCR HRP1000.SHORT - lookup on the objectdescription (for Child node) - Organization Unit NVARCSTR 12 0 0 yes

2 CHILD_ID PK HRP1001.SOBID ID of the related object -Child (Organization Unit) NVARCSTR 8 0 0 no

3 CHILD_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension - Child Node DECIMAL 48 28 0 yes




7 PARENT_DESCRHRP1000.SHORT - lookup on the objectdescription (for Parent node) - OrganizaitonUnit

NVARCSTR 12 0 0 yes

8 PARENT_ID PK HRP1001.OBJID Object ID - Parent -Organization Unit NVARCSTR 8 0 0 no

9 PARENT_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension - Parent DECIMAL 48 28 0 yes


11 VALID_TO_DATE PKThe date until which this record is effective. It isautomatically generated by the Effective_Datetransform

DATETIME 24 0 9 no




Organization Unit hierarchy horizontally flattened from Infotype HRP1001 (DB Table)



Nullable


2 LEAF_LEVEL Current node level in the hierarchy INTEGER 4 0 0 yes



5 LVL_00_DESCR HRP1000.SHORT - lookup on the objectdescription (for Parent node) - Root Level NVARCSTR 12 0 0 yes

6 LVL_00_FULL_NAMEConcatenated: HRP1001.OBJID Object ID -Parent root level + HRP1000.SHORT - lookupon the object description (for Parent node) -Root Level

NVARCSTR 30 0 0 yes

7 LVL_00_ID PK HRP1001.OBJID Object ID - Parent root level NVARCSTR 8 0 0 no

8 LVL_00_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension - Root Level DECIMAL 48 28 0 yes

9 LVL_01_DESCR HRP1000.SHORT - lookup on the objectdescription (for Child node) - Level 01 NVARCSTR 12 0 0 yes

10 LVL_01_FULL_NAMEConcatenated: HRP1001.SOBID ID of therelated object - Child - Level 01 +HRP1000.SHORT - lookup on the objectdescription (for Child node) - Level 01

NVARCSTR 30 0 0 yes

11 LVL_01_ID PK HRP1001.SOBID ID of the related object -Child - Level 01 NVARCSTR 8 0 0 no

12 LVL_01_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension - Level 01 DECIMAL 48 28 0 yes



NVARCSTR 30 0 0 yes







NVARCSTR 30 0 0 yes



21 LVL_04_DESCR HRP1000.SHORT - lookup on the objectdescription (for Child node) Level 04 NVARCSTR 12 0 0 yes


NVARCSTR 30 0 0 yes




26 LVL_05_FULL_NAMEConcatenated: HRP1001.SOBID ID of therelated object - Child Level 05 +HRP1000.SHORT - lookup on the objectdescription (for Child node) - Level 05

NVARCSTR 30 0 0 yes

27 LVL_05_ID PK HRP1001.SOBID ID of the related object -Child Level 05 NVARCSTR 8 0 0 no

28 LVL_05_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension Level 05 DECIMAL 48 28 0 yes

29 LVL_06_DESCR HRP1000.SHORT - lookup on the objectdescription (for Child node) NVARCSTR 12 0 0 yes


NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes



35 LVL_07_ID PK HRP1001.SOBID ID of the related object -Child NVARCSTR 8 0 0 no




NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes



49 ORG_UNIT_ID PK HRP1001.OBJID Object ID - Current node inthe hierarchy NVARCSTR 8 0 0 no

50 ORG_UNIT_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension DECIMAL 48 28 0 yes



DATETIME 24 0 9 no




Organization Unit hierarchy Vertically flattened from Infotype HRP1001 (DB Table)



Nullable


2 CHILD_FULL_NAMEConcatenated: HRP1001.SOBID ID of therelated object - Child (Organization Unit) +HRP1000.SHORT - lookup on the objectdescription (for Child node) - Organization Unit

NVARCSTR 30 0 0 yes


4 CHILD_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension DECIMAL 48 28 0 yes


6 DEPTH Number of levels in the relationship for thenode INTEGER 4 0 0 yes

7 LEAF_FLAG 1 - if the node is leaf INTEGER 4 0 0 yes




NVARCSTR 12 0 0 yes

11 PARENT_FULL_NAMEConcatenated: HRP1001.OBJID Object ID -Parent - Organization Unit + HRP1000.SHORT- lookup on the object description (for Parentnode) - Organizaiton Unit

NVARCSTR 30 0 0 yes


13 PARENT_KEY Lookup on Organization Unit Key inORGANIATION_UNIT dimension DECIMAL 48 28 0 yes

14 ROOT_FLAG 1 if the node is root INTEGER 4 0 0 yes



DATETIME 24 0 9 no



PAYROLL_AREA

HR module Payroll Area descriptive attributes from T549T



Nullable



3 PAYROLL_AREA_DESCR T549T.ATEXT - Payroll area text NVARCSTR 20 0 0 yes

4 PAYROLL_AREA_FULL_NAME

Concatenated: T549T.ABKRS - Payroll area +T549T.ATEXT - Payroll area text NVARCSTR 30 0 0 yes

5 PAYROLL_AREA_ID PK T549T.ABKRS - Payroll area NVARCSTR 2 0 0 no


Descriptive attributes for calendar-associated cumulation types from T54C2, T54CT



Nullable

1 CUMULATN_TYPE_DESCR T54CT.LTEXT Calendar type - long name NVARCSTR 20 0 0 yes

2 CUMULATN_TYPE_FULL_NAME

Concatenated: T54C2.CUMTY - CumulationType + T54CT.LTEXT Calendar type - longname

NVARCSTR 30 0 0 yes

3 CUMULATN_TYPE_ID PK T54C2.CUMTY - Cumulation Type NVARCSTR 1 0 0 no

4 CUMULATN_TYPE_NAME T54CT.STEXT Text (5 char. long) - short name NVARCSTR 5 0 0 yes




8 UOT_ID T54C2.ZEINH Payroll time units NVARCSTR 2 0 0 yes



PAYROLL_FACT

Payroll Run details from PC207, PC261 culster directories



Nullable




4 ADMIN_ID_TIME PA0001.SACHP Administrator for HR masterdata NVARCSTR 3 0 0 no

5 AMT_PAYROLL PC207.BETRG - Payroll Amount DECIMAL 48 15 2 yes

6 ASSIGNMNT_CODE_01 PK PC207.CNTR1 - National assignment

indicator1 NVARCSTR 2 0 0 no





9 ASSIGNMNT_CODE_ABSENCE PK PC207.ABZNR - Absence assignment NVARCSTR 2 0 0 no

10 ASSIGNMNT_CODE_WORKCNTR PK PC207.APZNR -PC205 Work center

assignmentfor basic pay NVARCSTR 2 0 0 no

11 BONUS_DATE PC261.BONDT - Date of bonus accounting run DATETIME 24 0 9 yes


13 CHANGE_DATE PCL2.AEDTM - Last date PCL2 changed DATETIME 24 0 9 yes






17 COUNTRY_GRP_ID Hardcoded value of for US payroll NVARCSTR 2 0 0 no


19 CURR_ID PK PC207.AMT_CURR - Currency key NVARCSTR 5 0 0 no

20 CURR_ID_RATE PC207.RTE_CURR - Currency key - for RateAmount NVARCSTR 5 0 0 no



23 JOB_ID PA0001.STELL Job NVARCSTR 8 0 0 no



26 NUM_OF_UNITS PC207.ANZHL - HR payroll: Number - used fornon-pay wage types such as absences DECIMAL 48 15 2 yes


28 ORG_UNIT_ID PA0001.ORGEH Organizational unit NVARCSTR 8 0 0 no

29 PAYROLL_AREA_ID PC261.ABKRS - Payroll Area NVARCSTR 2 0 0 no

30 PAYROLL_CODE PC261.PAYID -Payroll identifier(alpha-numeric) NVARCSTR 1 0 0 yes

31 PAYROLL_DATE PC261.PAYDT - Pay date for payroll result DATETIME 24 0 9 yes

32 PAYROLL_PERIOD_ID PC261.FPPER - For period for payroll NVARCSTR 6 0 0 no

33 PAYROLL_PERIOD_ID_IN PC261.INPER -In-period for payroll NVARCSTR 6 0 0 yes

34 PAYROLL_RUN_DATE PC261.RUNDT - Date of payroll run DATETIME 24 0 9 no



35 PAYROLL_SEQ_ID PK PC207.SEQNO - Payroll sequence number NVARCSTR 5 0 0 no

36 PAYROLL_STATUS_ID PC261.SRTZA - Indicator: Status of record(SRTZA domain in DD07T) NVARCSTR 1 0 0 no

37 PAYROLL_TYPE_ID PC261.PAYTY - Payroll type NVARCSTR 4 0 0 no

38 PERIOD_END_DATE PC261.FPEND - End of payroll period(for-period) DATETIME 24 0 9 yes

39 PERIOD_PARAMETER_ID T549N.PERMO Period Parameters NVARCSTR 2 0 0 yes

40 PERIOD_START_DATE

PC261.FPBEG - Start of payroll period(for-period) DATETIME 24 0 9 yes



43 PERSON_ID PK PC207.PERNR - Personnel Number NVARCSTR 8 0 0 no

44 POSITION_ID PA0001.PLANS Position NVARCSTR 8 0 0 no

45 UOT_ID PC207.ZEINH - Time/Unit of measure NVARCSTR 3 0 0 no

46 WAGE_TYPE_ID PK PC207.LGART - Wage type NVARCSTR 4 0 0 no



PAYROLL_PC261_STAGE

Payroll run results from PC261 cluster table



Nullable











11 COUNTRY_GRP_ID Hardcoded value of for US payroll NVARCSTR 2 0 0 yes











20 PAYROLL_AREA_ID PC261.ABKRS - Payroll Area NVARCSTR 2 0 0 yes



23 PAYROLL_PERIOD_ID PC261.FPPER - For period for payroll NVARCSTR 6 0 0 yes


25 PAYROLL_RUN_DATE PC261.RUNDT - Date of payroll run DATETIME 24 0 9 yes

26 PAYROLL_SEQ_ID PK PC261.SEQNR - Payroll sequence ID NVARCSTR 5 0 0 no

27 PAYROLL_STATUS_ID PC261.SRTZA - Indicator: Status of record(SRTZA domain in DD07T) NVARCSTR 1 0 0 yes

28 PAYROLL_TYPE_ID PC261.PAYTY - Payroll type NVARCSTR 4 0 0 yes


30 PERIOD_END_DATE_IN

PC261.IPEND - End of payroll period(in-period) DATETIME 24 0 9 yes

31 PERIOD_PARAMETER_ID PC261.IPERM - Period parameter NVARCSTR 2 0 0 yes







35 PERSON_ID PK PC261.PERNR - Personnel Number NVARCSTR 8 0 0 no


PAYROLL_PERIOD

Payroll Period details from T549Q



Nullable



3 PAYROLL_PERIOD_ID PK T549Q.PABRJ Payroll Year + T549Q.PABRPPayroll Period NVARCSTR 6 0 0 no

4 PAYROLL_PERIOD_NUM T549Q.PABRP Payroll Period INTEGER 4 0 0 yes

5 PAYROLL_PERIOD_NUM_PREV T549Q.VABRP Previous payroll period INTEGER 4 0 0 yes

6 PERIOD_END_DATE T549Q.ENDDA End Date DATETIME 24 0 9 yes

7 PERIOD_PARAMETER_DESCR T549N.ATEXT Period parameter - name NVARCSTR 20 0 0 yes

8 PERIOD_PARAMETER_ID PK T549Q.PERMO Period Parameters NVARCSTR 2 0 0 no

9 PERIOD_START_DATE T549Q.BEGDA Start Date DATETIME 24 0 9 yes

10 PERIOD_YEAR T549Q.PABRJ Payroll Year INTEGER 4 0 0 yes

11 PERIOD_YEAR_PREV T549Q.VABRJ Previous payroll year INTEGER 4 0 0 yes



PAYROLL_PERIOD_PARAMETER

Payroll Period Parameter descriptive attributes from T549N



Nullable



3 PERIOD_PARAMETER_DESCR T549N.ATEXT Period parameter - name NVARCSTR 20 0 0 yes

4 PERIOD_PARAMETER_FULL_NAME

Concatenated: T549N.PERMO PeriodParameters + T549N.ATEXT Period parameter- name

NVARCSTR 30 0 0 yes

5 PERIOD_PARAMETER_ID PK T549N.PERMO Period Parameters NVARCSTR 2 0 0 no

PAYROLL_STATUS

(DD07T domain SRTZA) - descriptive attributes for Payroll Indicator for most recent update of results record



Nullable



3 PAYROLL_STATUS_DESCR

DD07T.DDTEXT Short text describing ABAP/4Dictionary objects (SRTZA domain) NVARCSTR 60 0 0 yes

4 PAYROLL_STATUS_FULL_NAME

Concatenated: DD07T.DOMVALUE_L Valuesfor domains: Single value/upper limit (SRTZAdomain) + DD07T.DDTEXT Short textdescribing ABAP/4 Dictionary objects (SRTZAdomain)

NVARCSTR 70 0 0 yes

5 PAYROLL_STATUS_ID PK DD07T.DOMVALUE_L Values for domains:Single value/upper limit (SRTZA domain) NVARCSTR 1 0 0 no




Joins cumulative payroll results (PC22Y) with cluster directory (PC261) to associate pay period dates with payroll amounts



Nullable




4 ADMIN_ID_TIME PA0001.SACHP Administrator for HR masterdata NVARCSTR 3 0 0 no

5 AMT_PAYROLL PC22Y.BETRG - Period-to-date payroll amount DECIMAL 48 15 2 yes







12 COUNTRY_GRP_ID Hardcoded value of for US payroll NVARCSTR 2 0 0 no


14 CUMULATN_MONTH Cumulation Month number within the year INTEGER 4 0 0 yes

15 CUMULATN_PERIOD PK PC22Y.CUMNO - Cumulation Interval Number INTEGER 4 0 0 no

16 CUMULATN_QTR Cumulation Quarter number within the year INTEGER 4 0 0 yes



17 CUMULATN_TYPE_ID PK PC22Y.CUMTY - Calendar type abbreviationfor cumulative amounts NVARCSTR 1 0 0 no

18 CUMULATN_WEEK Cumulation Week number within the year(based on WW standard) INTEGER 4 0 0 yes

19 CUMULATN_YEAR PK PC22Y.CUMYR - Cumulation Interval Year orcalculated based on Payroll Run Date INTEGER 4 0 0 no

20 CURR_ID PK PC22Y.AMT_CURR - Currency for cumulativepayroll amount NVARCSTR 5 0 0 no



23 JOB_ID PA0001.STELL Job NVARCSTR 8 0 0 no



26 NUM_OF_UNITS PC22Y.ANZHL - Number of units in cumulativepayroll amount DECIMAL 48 15 2 yes


28 ORG_UNIT_ID PA0001.ORGEH Organizational unit NVARCSTR 8 0 0 no

29 PAYROLL_AREA_ID PC261.ABKRS - Payroll Area NVARCSTR 2 0 0 no



32 PAYROLL_PERIOD_ID PC261.FPPER - For period for payroll NVARCSTR 6 0 0 no


34 PAYROLL_RUN_DATE PC261.RUNDT - Date of payroll run DATETIME 24 0 9 no



35 PAYROLL_SEQ_ID PK PC261.SEQNR - Payroll sequence number NVARCSTR 5 0 0 no

36 PAYROLL_STATUS_ID PC261.SRTZA - Indicator: Status of record(SRTZA domain in DD07T) NVARCSTR 1 0 0 no

37 PAYROLL_TYPE_ID PC261.PAYTY - Payroll type NVARCSTR 1 0 0 no


39 PERIOD_PARAMETER_ID PC261.IPERM - Period parameter NVARCSTR 2 0 0 no





43 PERSON_ID PK PCL261.PERNR - Personnel Number NVARCSTR 8 0 0 no

44 POSITION_ID PA0001.PLANS Position NVARCSTR 8 0 0 no

45 UOT_ID Lookup on default Units of Time ID inWAGE_TYPE date-effective dimension NVARCSTR 3 0 0 no

46 VALID_FROM_DATE PK PC22Y.BEGDA - Start Date DATETIME 24 0 9 no

47 VALID_TO_DATE PK PC22Y.ENDDA End Date DATETIME 24 0 9 no

48 WAGE_TYPE_ID PK PC22Y.LGART - Wage Type NVARCSTR 4 0 0 no



PAYROLL_TYPE

(DD07T domain PAYTY) - descriptive attributes for Payroll type



Nullable



3 PAYROLL_TYPE_DESCR

DD07T.DDTEXT Short text describing ABAP/4Dictionary objects (PAYTY domain) NVARCSTR 60 0 0 yes

4 PAYROLL_TYPE_FULL_NAME

Concatenated: DD07T.DOMVALUE_L Valuesfor domains: Single value/upper limit (PAYTYdomain) + DD07T.DDTEXT Short textdescribing ABAP/4 Dictionary objects (PAYTYdomain)

NVARCSTR 70 0 0 yes

5 PAYROLL_TYPE_ID PK DD07T.DOMVALUE_L Values for domains:Single value/upper limit (PAYTY domain) NVARCSTR 1 0 0 no

PAY_SCALE_AREA

Salary Pay scale area descriptive attributes from T510G; load PAY_SCALE_AREA



Nullable


2 COUNTRY_GRP_ID PK T510G.MOLGA - Country grouping NVARCSTR 2 0 0 no



5 PAY_SCALE_AREA_DESCR 5150G.TGBTX Pay scale area designation NVARCSTR 20 0 0 yes

6 PAY_SCALE_AREA_FULL_NAME

Concatenated: T510G.TRFGB - Pay scale area+ 5150G.TGBTX Pay scale area designation NVARCSTR 30 0 0 yes

7 PAY_SCALE_AREA_ID PK T510G.TRFGB - Pay scale area NVARCSTR 2 0 0 no



PAY_SCALE_TYPE

Salary Pay scale type descriptive attributes from T510A; load PAY_SCALE_TYPE



Nullable


2 COUNTRY_GRP_ID PK T510A.MOLGA Country grouping NVARCSTR 2 0 0 no



5 PAY_SCALE_TYPE_CODE T510A.ITRFA Internal pay scale type NVARCSTR 2 0 0 yes

6 PAY_SCALE_TYPE_DESCR T510A.TARTX Pay scale text NVARCSTR 20 0 0 yes

7 PAY_SCALE_TYPE_ID PK T510A.TRFAR Pay scale type NVARCSTR 2 0 0 no


HR event (action) reasons descriptive attributes from T530T; load PERSONNEL_ACTION_REASON dimension



Nullable

1 ACTION_REASON_DESCR T530T.MGTXT Name of reason for action NVARCSTR 30 0 0 yes

2 ACTION_REASON_ID PK T530T.MASSG Reason for action NVARCSTR 2 0 0 no

3 ACTION_TYPE_DESCR


4 ACTION_TYPE_ID PK T530T.MASSN Action type NVARCSTR 2 0 0 no






HR event (action) status (employment status) descriptive attributes from T529U; load PERSONNEL_ACTION_STATUS dimension



Nullable



3 STATUS_CATEG_DESCR

DD07T. DDTEXT -Lookup text for benefit plancategory - domain STATN NVARCSTR 60 0 0 yes

4 STATUS_CATEG_ID PK T529U.STATN Status number (Categoryidentifier) NVARCSTR 1 0 0 no

5 STATUS_DESCR T529U.TEXT1 Text, 40 Characters Long NVARCSTR 40 0 0 yes

6 STATUS_ID PK T529U.STATV Status indicator for actions NVARCSTR 1 0 0 no


HR event (action) type descriptive attributes from T529T; load PERSONNEL_ACTION_TYPE dimension



Nullable

1 ACTION_TYPE_DESCR T529T.MNTXT Name of action type NVARCSTR 30 0 0 yes

2 ACTION_TYPE_ID PK T529T.MASSN Action type NVARCSTR 2 0 0 no






Personnel Administrator details from T526



Nullable

1 ADMIN_FULL_NAME Concatenated: T526.SACHX Administrator +T526.SACHN Name of administrator NVARCSTR 30 0 0 yes

2 ADMIN_GRP_CODE PK T526.WERKS Administrator Group NVARCSTR 4 0 0 no

3 ADMIN_ID PK T526.SACHX Administrator NVARCSTR 3 0 0 no

4 ADMIN_NAME T526.SACHN Name of administrator NVARCSTR 20 0 0 yes

5 ADMIN_TITLE T522T. ATEXT - Lookup on Form of Address(Title) descritpion NVARCSTR 5 0 0 yes



8 PHONE T526.TELNR Telephone number NVARCSTR 14 0 0 yes

9 USER_NAME SAP name of a SAPoffice user (login User ID) NVARCSTR 12 0 0 yes



PERSONNEL_AREA

Personnel area descriptive attributes from T005T, T005U, ADRC; load PERSONNEL_AREA dimension



Nullable

1 ADDRESS_ID T500P.ADRNR: Address NVARCSTR 10 0 0 yes

2 CITY ADRC.CITY1 City NVARCSTR 40 0 0 yes

3 CMPNY_CODE_ID T500P.BUKRS - Company code NVARCSTR 4 0 0 yes

4 CMPNY_CODE_NAME T001.BUTXT Lookup on Company Code Name NVARCSTR 25 0 0 yes

5 COUNTRY_GRP_DESCR

T500T.LTEXT - Designation for personnelcountry grouping lookup NVARCSTR 25 0 0 yes

6 COUNTRY_GRP_ID T500P.MOLGA - Country grouping NVARCSTR 2 0 0 yes

7 COUNTRY_ID ADRC.COUNTRY Country Key NVARCSTR 3 0 0 yes

8 COUNTRY_NAME T005T.LANDX Country name NVARCSTR 15 0 0 yes

9 CURR_ID T001.WAERS Currency Key NVARCSTR 5 0 0 yes

10 DISTRICT ADRC.CITY2 District NVARCSTR 40 0 0 yes

11 FAX ADRC.FAX_NUMBER First fax no.: diallingcode+number NVARCSTR 30 0 0 yes

12 HOUSE_NUMBER ADRC.HOUSE_NUM1 House Number NVARCSTR 10 0 0 yes



15 PERSONNEL_AREA_FULL_NAME

T500P.PERSA +T500P.NAME1 - Personnelarea text NVARCSTR 120 0 0 yes

16 PERSONNEL_AREA_ID PK T500P.PERSA - Personnel area NVARCSTR 4 0 0 no



17 PERSONNEL_AREA_NAME T500P.NAME1 - Personnel area text NVARCSTR 30 0 0 yes

18 PERSONNEL_AREA_NAME_01 ADRC.NAME1 Name 1 NVARCSTR 40 0 0 yes




22 PHONE ADRC.TEL_NUMBER First telephone no.:dialling code+number NVARCSTR 30 0 0 yes

23 REGION_ID ADRC.REGION Region (State, Province,County) NVARCSTR 3 0 0 yes

24 REGION_NAME T005U.BEZEI Region Description NVARCSTR 20 0 0 yes

25 STREET ADRC.STREET Street NVARCSTR 60 0 0 yes

26 ZIP ADRC.POST_CODE1 City postal code NVARCSTR 10 0 0 yes

PERSONNEL_DATE_TYPE

Date specification descriptive attributes for HR administration from T548Y, T548T; load PERSONNEL_DATE_TYPE dimension



Nullable

1 DATE_TYPE_DESCR T548T.DTEXT Date type text NVARCSTR 20 0 0 yes

2 DATE_TYPE_ID PK T548T.DATAR Date type NVARCSTR 2 0 0 no





PERSONNEL_SUBAREA

Personnel sub area descriptive attributes from T5U0P, T001P



Nullable

1 CMPNY_CODE_ID T500P.BUKRS Company code NVARCSTR 4 0 0 yes

2 CMPNY_CODE_NAME T001.BUTXT Lookup on Company Code Name NVARCSTR 25 0 0 yes

3 COUNTRY_GRP_DESCR

T500T.LTEXT - Designation for personnelcountry grouping lookup NVARCSTR 25 0 0 yes

4 COUNTRY_GRP_ID T001P.MOLGA Country grouping NVARCSTR 2 0 0 yes

5 CURR_ID T001.WAERS Currency Key NVARCSTR 5 0 0 yes

6 DISTRICT T5U0P.ORDIS District NVARCSTR 3 0 0 yes

7 HOLIDAY_CALENDAR_DESCR

THOCT.LTEXT Public calendar description(lookup) NVARCSTR 60 0 0 yes


9 INDUSTRY_CODE_DESCR

T5USC.STEXT - Standard Industry Code namelookup NVARCSTR 30 0 0 yes

10 INDUSTRY_CODE_ID T5U0P.SICNO Standard industry code NVARCSTR 5 0 0 yes


T001P.MOURA Personnel subarea groupingfor leave types NVARCSTR 2 0 0 yes



14 PAY_SCALE_AREA_DESCR T510G.TGBTX - Pay scale area name lookup NVARCSTR 20 0 0 yes

15 PAY_SCALE_AREA_ID T001P.TRFGB Pay scale area NVARCSTR 2 0 0 yes

16 PAY_SCALE_TYPE_DESCR T510A.TARTX - Pay scale type name lookup NVARCSTR 20 0 0 yes



17 PAY_SCALE_TYPE_ID T001P.TRFAR Pay scale type NVARCSTR 2 0 0 yes

18 PERSONNEL_AREA_FULL_NAME

T001P.WERKS+T500P.NAME1 Personnelarea text NVARCSTR 120 0 0 yes

19 PERSONNEL_AREA_ID PK T001P.WERKS Personnel area NVARCSTR 4 0 0 no

20 PERSONNEL_AREA_NAME T500P.NAME1 Personnel area text NVARCSTR 30 0 0 yes

21 PERSONNEL_SUBAREA_FULL_NAME

T001P.BTRTL+T001P.BTEXT Personnelsubarea text NVARCSTR 120 0 0 yes

22 PERSONNEL_SUBAREA_ID PK T001P.BTRTL Personnel subarea NVARCSTR 4 0 0 no

23 PERSONNEL_SUBAREA_NAME T001P.BTEXT Personnel subarea text NVARCSTR 15 0 0 yes

24 REGION T5U0P.ORREG Region NVARCSTR 3 0 0 yes

25 TAX_CMPNY_ID T5U0P.TXCMP Tax company NVARCSTR 4 0 0 yes

26 TAX_CMPNY_NAME T5UTL.LTEXT - Tax Company name lookup NVARCSTR 40 0 0 yes


Gender descriptive attributes from DD07T, BVMRK domain; load PERSONNEL_TASK_STATUS dimension



Nullable



3 TASK_STATUS_DESCR

DD07T.DDTEXT Short text describing ABAP/4Dictionary objects (BVMRK domain) NVARCSTR 60 0 0 yes

4 TASK_STATUS_ID PK DD07T.DOMVALUE_L Values for domains:Single value/upper limit (BVMRK domain) NVARCSTR 1 0 0 no



PERSONNEL_TASK_TYPE

Type of deadlines associated with personnel events from T531, T531S; load PERSONNEL_TASK_TYPE



Nullable

1 DAYS_LEAD_TIME T531.VORLZ Lead time (number) NVARCSTR 3 0 0 yes



4 TASK_TYPE_DESCR T531S.TMTXT Text for date/deadline type NVARCSTR 20 0 0 yes

5 TASK_TYPE_ID PK T531S.TMART Date/deadline type NVARCSTR 2 0 0 no

6 UOT_DESCR Lookup T538T.ETEXT - Lead time units ofmeasure text NVARCSTR 20 0 0 yes

7 UOT_ID T531.ZEINH Unit of time/measurement NVARCSTR 3 0 0 yes



POSITIONDate-tracked dimension holding position definitions. A position is defined as the unique occurrence of a job in one organization - fromHRP1000, HRP1007, HRP1001



Nullable




4 POSITION_DESCR HRP1000.STEXT - Position description NVARCSTR 40 0 0 yes

5 POSITION_DESCR_PAR

HRP1000.STEXT - Position description ParentPostiion NVARCSTR 40 0 0 yes

6 POSITION_DESCR_SEARCH

HRP1000.MC_SEARK - Keyword text used forsearching NVARCSTR 52 0 0 yes

7 POSITION_DESCR_SEARCH_PAR

HRP1000.MC_SEARK - Keyword text used forsearching - Parent Position NVARCSTR 52 0 0 yes

8 POSITION_DESCR_SHORT

HRP1000.SHORT - Short Description ofposition NVARCSTR 12 0 0 yes

9 POSITION_DESCR_SHORT_PAR

HRP1000.SHORT - Short Description ofposition - Parent Position NVARCSTR 12 0 0 yes

10 POSITION_FULL_NAME

Concatenated: T527B.PLANS - Position key +HRP1000.STEXT - Position description NVARCSTR 60 0 0 yes

11 POSITION_ID T527B.PLANS - Position key NVARCSTR 8 0 0 yes

12 POSITION_ID_PAR HRP1001.OBJID - Lookup position ID ofsupervisor NVARCSTR 8 0 0 yes

13 POSITION_KEY PK Surrogate key generated for POSITIONdimension (date-effective records) DECIMAL 48 28 0 no

14 VACANCY_STATUS_DESCR Lookup text for vacancy status NVARCSTR 10 0 0 yes

15 VACANCY_STATUS_ID HRP1007.STATUS Status of vacancy NVARCSTR 1 0 0 yes

16 VACANT_FLAG HRP1007.VACAN- Indicator for vacancy of aposition INTEGER 4 0 0 yes



17 VACANT_FROM_DATE

HRP1007.BEGDA - Beginning date for avacancy in this position DATETIME 24 0 9 yes

18 VALID_FROM_DATE HRP1000/HRP1007.BEGDA - Beginningeffective date (merged) DATETIME 24 0 9 yes

19 VALID_TO_DATE HRP1000/HRP1007 - Merged ENDDA - Endingeffective date DATETIME 24 0 9 yes

POSITION_HIER

Position hierarchy as parent/child relationship from Infotype HRP1001 (DB Table)



Nullable



3 CHILD_KEY Lookup on Position Key in POSITIONdimension - Child Node DECIMAL 48 28 0 yes





NVARCSTR 12 0 0 yes


9 PARENT_KEY Lookup on Position Key in POSITIONdimension - Parent DECIMAL 48 28 0 yes





POSITION_HIER_HZ

Position hierarchy as parent/child relationship from Infotype HRP1001 (DB Table)



Nullable


2 LEAF_LEVEL Current node level in the hierarchy INTEGER 4 0 0 yes



5 LVL_00_DESCR HRP1000.SHORT - lookup on the objectdescription (for Parent node) - Root Level NVARCSTR 12 0 0 yes

6 LVL_00_FULL_NAMEConcatenated: HRP1001.OBJID Object ID -Parent root level + HRP1000.SHORT - lookupon the object description (for Parent node) -Root Level

NVARCSTR 30 0 0 yes

7 LVL_00_ID PK HRP1001.OBJID Object ID - Parent root level NVARCSTR 8 0 0 no

8 LVL_00_KEY Lookup on Position Key in POSITIONdimension - Root Level DECIMAL 48 28 0 yes



NVARCSTR 30 0 0 yes


12 LVL_01_KEY Lookup on Position Key in POSITIONdimension - Level 01 DECIMAL 48 28 0 yes



NVARCSTR 30 0 0 yes







NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes


28 LVL_05_KEY Lookup on Position Key in POSITIONdimension Level 05 DECIMAL 48 28 0 yes

29 LVL_06_DESCR HRP1000.SHORT - lookup on the objectdescription (for Child node) NVARCSTR 12 0 0 yes


NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes



35 LVL_07_ID PK HRP1001.SOBID ID of the related object -Child NVARCSTR 8 0 0 no




NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes





NVARCSTR 30 0 0 yes



49 POSITION_ID PK HRP1001.OBJID Object ID - Current node inthe hierarchy NVARCSTR 8 0 0 no

50 POSITION_KEY Lookup on Position Key in POSITIONdimension DECIMAL 48 28 0 yes





POSITION_HIER_VR

Position hierarchy Vertically flattened from Infotype HRP1001 (DB Table)



Nullable


2 CHILD_FULL_NAMEConcatenated: HRP1001.SOBID ID of therelated object - Child (Organization Unit) +HRP1000.SHORT - lookup on the objectdescription (for Child node) - Organization Unit

NVARCSTR 30 0 0 yes


4 CHILD_KEY Lookup on Position Key in POSITIONdimension - Child node DECIMAL 48 28 0 yes


6 DEPTH Number of levels in the relationship for thenode INTEGER 4 0 0 yes

7 LEAF_FLAG 1 - if the node is leaf INTEGER 4 0 0 yes




NVARCSTR 12 0 0 yes

11 PARENT_FULL_NAMEConcatenated: HRP1001.OBJID Object ID -Parent - Organization Unit + HRP1000.SHORT- lookup on the object description (for Parentnode) - Organizaiton Unit

NVARCSTR 30 0 0 yes


13 PARENT_KEY Lookup on Position Key in POSITIONdimension - Parent node DECIMAL 48 28 0 yes

14 ROOT_FLAG 1 if the node is root INTEGER 4 0 0 yes





PROFICIENCY

Employee proficiency descriptive attributes from T777Q



Nullable



3 PROFICIENCY_DESCR T777Q.CHARA_TEXT Proficiency text NVARCSTR 25 0 0 yes

4 PROFICIENCY_ID PK T777Q.CHARA Proficiency of aQualification/Requirement NVARCSTR 4 0 0 no

QUALIFICATION

Employee qualification descriptive attributes from T574B; load QUALIFICATION dimension



Nullable



3 QUALIFICTN_DESCR T574B.QTEXT Qualification text NVARCSTR 40 0 0 yes

4 QUALIFICTN_ID PK T574B.QUALI Qualification key NVARCSTR 8 0 0 no



RELIGION

Religion denomination descriptive attributes from T516T; load RELIGION dimension



Nullable



3 RELIGION_DESCR T516T.KTEXT Religious Denomination LongText NVARCSTR 25 0 0 yes

4 RELIGION_ID PK T516T.KONFE Religious Denomination Key NVARCSTR 2 0 0 no

5 RELIGION_NAME T516T.KITXT Religious Denomination NVARCSTR 4 0 0 yes

RESIDENCE_STATUS

Residence Status descriptive attributes from T505V; load RESIDENCE_STATUS dimension



Nullable


2 COUNTRY_GRP_ID PK T505V.MOLGA Country grouping NVARCSTR 2 0 0 no



5 RESIDENCE_STATUS_DESCR T505V.LTEXT Residence status texts NVARCSTR 25 0 0 yes

6 RESIDENCE_STATUS_ID PK T505V.RESIS Residence status NVARCSTR 1 0 0 no



SALARY_RANGE

Pay scale group and level dimension table lists pay ranges (North America) T510N, T510F



Nullable

1 AMT_SALARY_MAX T510N.GRMAX- Salary grade maximumannual salary DECIMAL 48 11 2 yes

2 AMT_SALARY_MIN T510N.GRMIN - Salary grade minimum annualsalary DECIMAL 48 11 2 yes

3 COUNTRY_GRP_ID T510.MOLGA - Country ID NVARCSTR 2 0 0 yes

4 CURRENT_FLAG 1 - the record is current (based on BEGDA,ENDDA) INTEGER 4 0 0 yes

5 CURR_ID T510F.WAERS - Currency key NVARCSTR 5 0 0 yes





9 PAY_SCALE_AREA_DESCR

Lookup T510G.TGBTX - Description of payscale Areas NVARCSTR 20 0 0 yes

10 PAY_SCALE_AREA_ID T510N.TRFGB - Pay scale area NVARCSTR 2 0 0 yes

11 PAY_SCALE_GRP_CODE T510N.TRFGR - Pay scale group NVARCSTR 8 0 0 yes

12 PAY_SCALE_LVL T510N.TRFST - Pay scale level NVARCSTR 2 0 0 yes

13 PAY_SCALE_TYPE_DESCR

Lookup T510A.TARTX - Description of payscale type NVARCSTR 20 0 0 yes

14 PAY_SCALE_TYPE_ID T510N.TRFAR - Pay scale type NVARCSTR 2 0 0 yes

15 PRCNT_SALARY_MAX T510N.PCTMX - Maximum annual salaryincrease expressed as a percentage DECIMAL 48 5 2 yes

16 SALARY_RANGE_KEY PK Surrogate key generated DECIMAL 48 28 0 no



17 VALID_FROM_DATE BEGDA - Beginning effective date DATETIME 24 0 9 yes

18 VALID_TO_DATE ENDDA - Ending effective DATETIME 24 0 9 yes

SCHOOL_TYPE

School (college, university, etc) descriptive attributes from T517T load SCHOOL_TYPE dimension



Nullable



3 SCHOOL_TYPE_DESCR T517T.STEXT Education establishment text NVARCSTR 20 0 0 yes

4 SCHOOL_TYPE_ID PK T517T.SLART Educational establishment NVARCSTR 2 0 0 no



SERVICE_INTERVAL_HR



Nullable

1 LABEL_01_SERVICE_INTERVAL

Length of Service (in Years and Months) Label01 NVARCSTR 100 0 0 yes











7 LOAD_DATE Date and Time Loaded into Rapid Mart DATETIME 24 0 9 yes

8 LOAD_TIME Time loaded into Rapid Mart NVARCSTR 8 0 0 yes

9 SERVICE_INTERVAL_01 Length (in months) of Service 01 DECIMAL 48 28 0 yes





14 SERVICE_INTERVAL_ID PK Length of service Intervals Identifier (primary

key) DECIMAL 48 28 0 no



STUDY_BRANCH

Studies branch descriptive attributes from T517X load STUDY_BRANCH dimension



Nullable



3 STUDY_BRANCH_DESCR T517X.FTEXT Text for branch of study NVARCSTR 40 0 0 yes

4 STUDY_BRANCH_ID PK T517X.FAART Branch of study NVARCSTR 5 0 0 no



TIME_DIM

Time Dimension (Daily)



Nullable

1 CALENDAR_DATE PK Calendar Date DATETIME 24 0 9 no

2 CALENDAR_MONTH Number of Calendar Month INTEGER 4 0 0 yes

3 CALENDAR_QUARTER Calendar Quarter INTEGER 4 0 0 yes

4 CALENDAR_YEAR Calenar Year INTEGER 4 0 0 yes

5 DAY_IN_PERIOD Number of a day in a fiscal period INTEGER 4 0 0 yes

6 DAY_IN_WEEK Day of the week INTEGER 4 0 0 yes

7 FISC_PERIOD Fiscal Period of Calendar Date. Retrieved fromSAP using FI_PERIOD_DETEMINE INTEGER 4 0 0 yes

8 FISC_YEAR Fiscal Year of Calendar Date. Retrieved fromSAP using FI_PERIOD_DETEMINE INTEGER 4 0 0 yes

9 IS_WEEKEND Indicates if date falls on a weekend (1) NVARCSTR 1 0 0 yes



12 MONTH_YEAR Calendar Month and Year NVARCSTR 10 0 0 yes

13 WEEK_IN_YEAR Number of week in the year DECIMAL 48 28 0 yes



TIME_DIM_WEEKLY

Time Dimension (WEEKLY). Used for summary facts (such as BENEFIT_ENROLL_SUMMARY_FACT)



Nullable

1 CALENDAR_YEAR PK Calenar Year INTEGER 4 0 0 no



4 WEEK_END_DATE Last date in the week DATETIME 24 0 9 yes

5 WEEK_IN_YEAR PK Number of week in the year DECIMAL 48 28 0 no

6 WEEK_NAME Week - Year concatenation NVARCSTR 60 0 0 yes

7 WEEK_START_DATE First date of the week DATETIME 24 0 9 yes

8 WEEK_START_FISC_PER Fiscal Period when the week starts INTEGER 4 0 0 yes

9 WEEK_START_FISC_YEAR Fiscal Year when the week starts INTEGER 4 0 0 yes

10 WEEK_START_MONTH

Number of Calendar Month when the weekstarts INTEGER 4 0 0 yes

11 WEEK_START_QUARTER Calendar Quarter when the week starts INTEGER 4 0 0 yes




Employee time management status descriptive attributes from T555V; load TIME_MANAGEMENT_STATUS dimension



Nullable



3 TIME_MGMT_STATUS_DESCR

T555V.ZTEXT Text for time recording status(IT Planned Working Time) NVARCSTR 50 0 0 yes

4 TIME_MGMT_STATUS_ID PK T555V.ZTERF Employee Time Management

Status NVARCSTR 1 0 0 no

UNIT_OF_TIME

HR related unit of time descriptive attributes from T538A, T538T



Nullable



3 UOT_CODE T538A.MSEHI Unit of Measurement NVARCSTR 3 0 0 yes

4 UOT_DESCR T538T.ETEXT Text, 20 characters NVARCSTR 20 0 0 yes

5 UOT_ID PK T538A.ZEINH Time/Measurement Unit NVARCSTR 3 0 0 no



VALID_FROM_DATE_STAGE

Selects Min. VALID_FROM_DATE for each PERSON_ID in an InfoType record



Nullable

1 INFOTYPE_ID Hard-coded value PAxxxx VARCSTR 6 0 0 yes


3 LOAD_TIME Time when the record was loaded VARCSTR 8 0 0 yes

4 PERSON_ID PK PAxxxx.PERNR Personnel number VARCSTR 8 0 0 no

5 VALID_FROM_DATE PAxxxx.BEGDA Minimum Valid From Date DATETIME 24 0 9 yes

VESTING_RULE

Benefit Vesting rule descriptive attributes from T5UCR; load VESTING_RULE dimension



Nullable


2 BENFT_AREA_ID PK T5UCR.BAREA Benefit area NVARCSTR 2 0 0 no



5 VESTNG_RULE_DESCR T5UCR.LTEXT Description (20 characters) NVARCSTR 20 0 0 yes

6 VESTNG_RULE_FULL_NAME

Concatenated: T5UCR.VESTI Vesting rulesfor employee contributions to savings plans +T5UCR.LTEXT Description (20 characters)

NVARCSTR 30 0 0 yes

7 VESTNG_RULE_ID PK T5UCR.VESTI Vesting rules for employeecontributions to savings plans NVARCSTR 4 0 0 no



WAGE_TYPE

Employee wage type date-effective records from T511, T512T



Nullable

1 ADDITIVTY_FLAG T511.ADSUM - Add to total amount for basicpay total INTEGER 4 0 0 yes


3 COUNTRY_GRP_ID T512T.MOLGA - Country Grouping NVARCSTR 2 0 0 yes


5 DEDUCTN_FLAG T511.OPKEN - Operation indicator for wagetypes (1 is payment, 0 is a deduction) NVARCSTR 1 0 0 yes



8 UOT_DESCR Lookup T538T.ETEXT - Units description NVARCSTR 20 0 0 yes

9 UOT_ID T511.ZEINH - Time Unit NVARCSTR 3 0 0 yes

10 VALID_FROM_DATE T511.BEGDA - Beginnng effective date DATETIME 24 0 9 yes

11 VALID_TO_DATE T511.ENDDA - Ending effective date DATETIME 24 0 9 yes

12 VALID_TO_DATE_PREV T511.BEGDA Start date - 1 DATETIME 24 0 9 yes

13 VALUATN_MODEL_DESCR

T511IV_MT.MODTX Inderct Evaluation ModuleText (lookup) NVARCSTR 60 0 0 yes

14 VALUATN_MODEL_ID T511.MODNA - Module for indirect valuation NVARCSTR 5 0 0 yes

15 WAGE_TYPE_DESCR T512T.LGTXT - Wage type text NVARCSTR 25 0 0 yes

16 WAGE_TYPE_FULL_NAME

Concatenated: T512T.LGART - Wage Type +T512T.LGTXT - Wage type text NVARCSTR 40 0 0 yes



17 WAGE_TYPE_ID T512T.LGART - Wage Type NVARCSTR 4 0 0 yes

18 WAGE_TYPE_KEY PK Generated Surrogate Key for Wage Typedimension DECIMAL 48 28 0 no

19 WAGE_TYPE_NAME T512T.KZTXT Short text for wage type NVARCSTR 8 0 0 yes



WORK_CALENDAR

Caclualted calendar based on Holiday calendar; load WORK_CALENDAR



Nullable

1 CALENDAR_DATE PK Calendar Date DATETIME 24 0 9 no

2 CALENDAR_MONTH Number of Calendar Month DECIMAL 48 28 0 yes

3 CALENDAR_QUARTER Calendar Quarter DECIMAL 48 28 0 yes

4 CALENDAR_YEAR Calenar Year DECIMAL 48 28 0 yes

5 COUNT_WRKDAY Set to 1 be to used for aggregations to countnumber of working days DECIMAL 48 28 0 yes

6 DAY_IN_PERIOD Number of a day in a fiscal period DECIMAL 48 28 0 yes

7 DAY_IN_WEEK Day of the week DECIMAL 48 28 0 yes

8 FISC_PERIOD Fiscal Period of Calendar Date. Retrieved fromSAP using FI_PERIOD_DETEMINE DECIMAL 48 28 0 yes

9 FISC_YEAR Fiscal Year of Calendar Date. Retrieved fromSAP using FI_PERIOD_DETEMINE DECIMAL 48 28 0 yes

10 HOLIDAY_CALENDAR_ID PK THOC.IDENT Public Holiday Calendar NVARCSTR 2 0 0 no



13 MONTH_YEAR Calendar Month and Year NVARCSTR 10 0 0 yes

14 WEEK_IN_YEAR Number of week in the year DECIMAL 48 28 0 yes



WORK_CONTRACT

Work (Employment) Contract descriptive attributes from T542T; load WORK_CONTRACT dimension



Nullable

1 CONTRACT_DESCR T542T.ATX Work Contract Text NVARCSTR 15 0 0 yes

2 CONTRACT_FULL_NAME

Concatenated: T542T.ANSVH Work Contract +T542T.ATX Work Contract Text NVARCSTR 20 0 0 yes

3 CONTRACT_ID PK T542T.ANSVH Work Contract NVARCSTR 2 0 0 no


5 COUNTRY_GRP_ID PK T542T.MOLGA Country Grouping NVARCSTR 2 0 0 no



WORK_CONTRACT_TYPE

Work (Employment) Contract Type descriptive attributes from T547S; load WORK_CONTRACT_TYPE dimension



Nullable

1 CONTRACT_TYPE_DESCR

T547S.CTTXT Text for contract type (ContractElements infotype) NVARCSTR 20 0 0 yes

2 CONTRACT_TYPE_FULL_NAME

Concatenated: T547S.CTTYP Contract type +T547S.CTTXT Text for contract type (ContractElements infotype)

NVARCSTR 30 0 0 yes

3 CONTRACT_TYPE_ID PK T547S.CTTYP Contract type NVARCSTR 2 0 0 no





WORK_PERMIT_TYPE

Work permit type descriptive attributes from T509I; load WORK_PERMIT_TYPE dimension



Nullable


2 COUNTRY_GRP_ID PK T509I.MOLGA Country grouping NVARCSTR 2 0 0 no



5 WORK_PERMIT_TYPE_DESCR T509I.WPTEX Work permit type text NVARCSTR 30 0 0 yes

6 WORK_PERMIT_TYPE_ID PK T509I.WPCOD Type of work permit NVARCSTR 2 0 0 no


Xi3 Rm Sap Hr Ug En

Documents

Transcript of Xi3 Rm Sap Hr Ug En