PeopleSoft 8.8 Setting Up Workforce Analytics Applications ... · Setting Up Workforce Analytics Applications PeopleBook ... market,isprecededbyathree-lettercodeinparentheses. ThecodefortheU.S.federalgovernmentisUSF;

PeopleSoft 8.8Setting Up Workforce AnalyticsApplications PeopleBook

December 2002

PeopleSoft 8.8Setting Up Workforce Analytics Applications PeopleBookSKU EPM88W FA-B 1202

PeopleBooks Contributors: Teams from PeopleSoft Product Documentation and Development.Copyright 1999 - 2002 PeopleSoft, Inc. All rights reserved.

Printed in the United States.

All material contained in this documentation is proprietary and confidential to PeopleSoft, Inc. ("PeopleSoft"),protected by copyright laws and subject to the nondisclosure provisions of the applicable PeopleSoftagreement. No part of this documentation may be reproduced, stored in a retrieval system, or transmittedin any form or by any means, including, but not limited to, electronic, graphic, mechanical, photocopying,recording, or otherwise without the prior written permission of PeopleSoft.

This documentation is subject to change without notice, and PeopleSoft does not warrant that the material containedin this documentation is free of errors. Any errors found in this document should be reported to PeopleSoft in writing.

The copyrighted software that accompanies this document is licensed for use only in strict accordancewith the applicable license agreement which should be read carefully as it governs the terms of useof the software and this document, including the disclosure thereof.

PeopleSoft, PeopleTools, PS/nVision, PeopleCode, PeopleBooks, PeopleTalk, and Vantive are registeredtrademarks, and Pure Internet Architecture, Intelligent Context Manager, and The Real-Time Enterprise aretrademarks of PeopleSoft, Inc. All other company and product names may be trademarks of their respectiveowners. The information contained herein is subject to change without notice.

Open Source Disclosure

This product includes software developed by the Apache Software Foundation (http://www.apache.org/). Copyright(c) 1999-2000 The Apache Software Foundation. All rights reserved. THIS SOFTWARE IS PROVIDED“AS IS’’ AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITSCONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USEOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

PeopleSoft takes no responsibility for its use or distribution of any open source or shareware software ordocumentation and disclaims any and all liability or damages resulting from use of said software or documentation.

Contents

General PrefaceAbout This PeopleBook ..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixPeopleSoft Application Prerequisites.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixPeopleSoft Application Fundamentals.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixRelated Documentation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .x

Obtaining Documentation Updates.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .xOrdering Printed Documentation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .x

Typographical Conventions and Visual Cues.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiTypographical Conventions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .xiVisual Cues.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . .xii

Comments and Suggestions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiiiCommon Elements in These PeopleBooks .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xiii

PrefaceSetting Up Workforce Analytics Applications Preface... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvPeopleSoft Enterprise Warehouse.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xvOther Related PeopleBooks.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xv

Chapter 1Getting Started with PeopleSoft Workforce Analytics Applications... . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1PeopleSoft Workforce Analytics Overview... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1Setting Up PeopleSoft Enterprise Warehouse.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1PeopleSoft Workforce Analytics Implementation.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

Setting Up PeopleSoft Workforce Analytics Application Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . . . .2

Chapter 2Designing Your PeopleSoft Workforce Analytics System.... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Defining Your Operational Structure.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5Processing Multiple Currencies for Workforce Analytics Applications.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Setting Up TableMaps and DataMaps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Creating Model IDs, Scenario IDs, and Jobstream Metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

PeopleSoft Proprietary and Confidential iii

Contents

Chapter 3Importing Internal Source Data to Data Warehouse Tables... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Understanding Internal Source Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Reviewing ETL Maps and Data Warehouse Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Setting Up Trees... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

Understanding Workforce Analytics Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .14Reviewing Trees Used in PeopleSoft Workforce Analytics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .15Setting Up the Account Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .17Setting Up the Compensation Code Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .17Setting Up the Competency Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .18Setting Up the Financials-Related Department Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .18Setting Up the FINCODE Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .18Setting Up the Geography Tree .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .18Setting Up the Organization (Department) Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .19Setting Up the INDUSTRY Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .19Setting Up the JOBCODE Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .19Setting Up the Position Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .20Setting Up the UNITCODE Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .20Defining Which Trees the System Uses.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .20

Mapping Personnel Actions for JOB_F00... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Pages Used to Map Personnel Actions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .21Reviewing Source Table Action and Reason Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .21Defining Action Types.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .21Mapping Action and Reason Combinations.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .22Reviewing Your Personnel Action Mappings.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .23Loading Your Personnel Action Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .23

Mapping Locations to Geography ID Codes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23Pages Used to Map Locations to Geography IDs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .24Reviewing and Loading Source Table Location Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .24Entering Geography IDs and Creating a Geography Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .24Mapping Locations to Geography IDs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .24Reviewing Your Location and Geography ID Mappings.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .25

Mapping Compensation Codes and Plan Values.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26Pages Used to Map Compensation Codes and Values.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .27Reviewing Source Table Earnings, Deductions and Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .27Entering Compensation Codes and Creating a COMPCODE Tree.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .28Loading Source Table Dependencies.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .28Mapping Deductions and Benefit Plans to Compensation Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .29Mapping Earnings to Compensation Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .32Mapping Pay Item Names to Compensation Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .33

iv PeopleSoft Proprietary and Confidential

Contents

Entering Benefit Plan Values .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .34Reviewing Benefits Valuation Maps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .35Loading Compensation Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .35

Loading Data Warehouse Tables.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Overview of Data Warehouse Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .37Understanding Benefits Enrollment Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .46Understanding Competency Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .47Understanding Staffing Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .48Understanding Job Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .48Understanding Employee Compensation History Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .49

Viewing and Editing Data in Dimension and Reference Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49Understanding Review and Edit of Dimension and Reference Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .50Pages Used to Access Dimension and Reference Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .50Viewing and Editing Departments.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .58Setting Up Geography IDs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .58Viewing and Editing Job Codes and Job Code Sets.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .59Viewing and Editing Personal Information .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .59Viewing and Editing Position Data .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .60Viewing and Editing Location Data .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .60Viewing and Editing Salary Grades and Steps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .61Setting Up Compensation Codes... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .61Setting Up Industry Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .62Setting Up Financial Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .62Setting Up Unit Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .62Defining Age, Service and Other Duration Groups.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .63

Chapter 4Importing External Survey Data to Data Warehouse Tables.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Understanding External Survey Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Reviewing the Operator Defaults Page.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Reviewing Sources of External Survey Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

Page Used to Access eSurvey Providers .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .66Accessing Survey Providers.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .66

Reviewing External Survey Tables and ETL Setup.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67Understanding External Survey Tables and ETL Setup.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .67Reviewing the Data Warehouse Tables and ETL Maps.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .68Reviewing the Survey File Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .71

Understanding the Survey Data ETL Batches.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Importing External Survey Data with the Setup ETL Batch.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72

PeopleSoft Proprietary and Confidential v

Contents

Viewing and Editing the Survey Data Warehouse Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72Pages Used to View and Edit Survey Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .73

Completing Survey Mapping Definitions... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Understanding Survey Mapping Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .74Pages Used to Map Survey Data.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .75Setting Up Workforce Trees.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .75Mapping Job Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .76Mapping Survey Compensation Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .77Mapping Geography IDs.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .77Mapping Industry Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .77Mapping Financial Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .78Mapping Unit Codes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .78

Reviewing Survey Mapping Definitions Online.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .78Pages Used to Review Survey Mapping Definitions Online.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .79

Importing External Survey Data with the Load ETL Batch.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79Importing External Survey Data with the Ongoing ETL Batch.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Generating External Survey Data Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80

Pages Used to Generate External Survey Data Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .81Reviewing the External Survey Flat File Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

Understanding External Flat File Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .82Reviewing the Author File Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .82Reviewing the Dimension File Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .83Reviewing the Survey Instance File Definition.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .85Reviewing the Compensation Survey File Definition... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .87Reviewing the Benchmark Survey File Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .90Reviewing the Employee Survey File Definition.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .92Reviewing the Valid Values for Selected Fields in the File Definitions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . . .93

Chapter 5Setting Up Workforce Groups and Group Sets... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Understanding Workforce Groups and Group Sets.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .107Defining Workforce Groups .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .108

Pages Used to Set Up Workforce Groups.. . . . .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .109Setting Up Workforce Groups.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .109

Reviewing Your Workforce Group Setup.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .110Page Used to Run the Workforce Crystal Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .111Running the Workforce Groups Crystal Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .111

Building and Reviewing Workforce Groups .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111Using Workforce Groups in Scenario Processes .. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .111

vi PeopleSoft Proprietary and Confidential

Contents

Reviewing Workforce Group Results from Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112Page Used to Review Workforce Group Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .112Reviewing Workforce Group Results. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .112

Defining Workforce Group Sets.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .114Pages Used to Define Workforce Group Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .114Setting Up Workforce Group Sets.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .. . . . . . .114

Running the Group, Group Set, and Security Processes.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .116

Appendix APeopleSoft Workforce Analytics Reports.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119Report Descriptions.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .119

Glossary of PeopleSoft Terms..... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .121

Index .... . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . . . .. . . . . . . . . . . . . .. . . . . . . . . . .133

PeopleSoft Proprietary and Confidential vii

Contents

viii PeopleSoft Proprietary and Confidential

About This PeopleBook

PeopleBooks provide you with the information that you need to implement and use PeopleSoft applications.

This preface discusses:

• PeopleSoft application prerequisites.

• PeopleSoft application fundamentals.

• Related documentation.

• Typographical elements and visual cues.

• Comments and suggestions.

• Common elements in PeopleBooks.

Note. PeopleBooks document only page elements that require additional explanation. If a page element is notdocumented with the process or task in which it is used, then either it requires no additional explanation or itis documented with common elements for the section, chapter, PeopleBook, or product line. Elements thatare common to all PeopleSoft applications are defined in this preface.

PeopleSoft Application PrerequisitesTo benefit fully from the information that is covered in these books, you should have a basicunderstanding of how to use PeopleSoft applications.

See Using PeopleSoft Applications.

You might also want to complete at least one PeopleSoft introductory training course.

You should be familiar with navigating the system and adding, updating, and deleting information byusing PeopleSoft windows, menus, and pages. You should also be comfortable using the World WideWeb and the Microsoft Windows or Windows NT graphical user interface.

These books do not review navigation and other basics. They present the information that you needto use the system and implement your PeopleSoft applications most effectively.

PeopleSoft Application FundamentalsEach application PeopleBook provides implementation and processing information for your PeopleSoftdatabase. However, additional, essential information describing the setup and design of your systemappears in a companion volume of documentation called the application fundamentals PeopleBook.Each PeopleSoft product line has its own version of this documentation.

PeopleSoft Proprietary and Confidential ix

General Preface

The application fundamentals PeopleBook consists of important topics that apply to many or allPeopleSoft applications across a product line. Whether you are implementing a single application,some combination of applications within the product line, or the entire product line, you shouldbe familiar with the contents of this central PeopleBook. It is the starting point for fundamentals,such as setting up control tables and administering security.

Related DocumentationThis section discusses how to:

• Obtain documentation updates.

• Order printed documentation.

Obtaining Documentation UpdatesYou can find updates and additional documentation for this release, as well as previous releases,on the PeopleSoft Customer Connection Website. Through the Documentation section ofPeopleSoft Customer Connection, you can download files to add to your PeopleBook Library.You’ll find a variety of useful and timely materials, including updates to the full PeopleSoftdocumentation that is delivered on your PeopleBooks CD-ROM.

Important! Before you upgrade, you must check PeopleSoft Customer Connection for updates to theupgrade instructions. PeopleSoft continually posts updates as the upgrade process is refined.

See AlsoPeopleSoft Customer Connection Website, http://www.peoplesoft.com/corp/en/login.asp

Ordering Printed DocumentationYou can order printed, bound volumes of the complete PeopleSoft documentation that is deliveredon your PeopleBooks CD-ROM. PeopleSoft makes printed documentation available for eachmajor release shortly after the software is shipped. Customers and partners can order printedPeopleSoft documentation by using any of these methods:

• Web

• Telephone

• Email

WebFrom the Documentation section of the PeopleSoft Customer Connection Website, access the PeopleSoftPress Website under the Ordering PeopleBooks topic. The PeopleSoft Press Website is a joint venturebetween PeopleSoft and Consolidated Publications Incorporated (CPI), the book print vendor. Use acredit card, money order, cashier’s check, or purchase order to place your order.

x PeopleSoft Proprietary and Confidential

General Preface

TelephoneContact CPI at 800 888 3559.

EmailSend email to CPI at [email protected].

See AlsoPeopleSoft Customer Connection Website, http://www.peoplesoft.com/corp/en/login.asp

Typographical Conventions and Visual CuesThis section discusses:

• Typographical conventions.

• Visual cues.

Typographical ConventionsThe following table contains the typographical conventions that are used in PeopleBooks:

Typographical Convention or Visual Cue Description

Bold Indicates PeopleCode function names, method names,language constructs, and PeopleCode reserved words thatmust be included literally in the function call.

Italics Indicates field values, emphasis, and PeopleSoft or otherbook-length publication titles. In PeopleCode syntax,italic items are placeholders for arguments that yourprogram must supply.

We also use italics when we refer to words as words orletters as letters, as in the following: Enter the number 0,not the letterO.

KEY+KEY Indicates a key combination action. For example, a plussign (+) between keys means that you must hold downthe first key while you press the second key. For ALT+W,hold down the ALT key while you press W.

Monospace font Indicates a PeopleCode program or other code example.

(quotation marks) Indicate chapter titles in cross-references and words thatare used differently from their intended meanings.

PeopleSoft Proprietary and Confidential xi

General Preface

Typographical Convention or Visual Cue Description

. . . (ellipses) Indicate that the preceding item or series can be repeatedany number of times in PeopleCode syntax.

{ } (curly braces) Indicate a choice between two options in PeopleCodesyntax. Options are separated by a pipe ( | ).

[ ] (square brackets) Indicate optional items in PeopleCode syntax.

& (ampersand) When placed before a parameter in PeopleCode syntax,an ampersand indicates that the parameter is an alreadyinstantiated object.

Ampersands also precede all PeopleCode variables.

(ISO) Information that applies to a specific country, to the U.S.federal government, or to the education and governmentmarket, is preceded by a three-letter code in parentheses.

The code for the U.S. federal government is USF;the code for education and government is E&G, andthe country codes from the International StandardsOrganization are used for specific countries. Here is anexample:

(GER) If you’re administering German employees,German law requires you to indicate special nationalityand citizenship information for German workers usingnationality codes established by the German DEUEVDirective.

Cross-references PeopleBooks provide cross-references either belowthe heading See Also or on a separate line precededby the word See. Cross-references lead to otherdocumentation that is pertinent to the immediatelypreceding documentation.

Visual CuesPeopleBooks contain the following visual cues.

NotesNotes indicate information that you should pay particular attention to as you work with the PeopleSoft system.

Note. Example of a note.

xii PeopleSoft Proprietary and Confidential

General Preface

A note that is preceded by Important! is crucial and includes information that concernswhat you must do for the system to function properly.

Important! Example of an important note.

WarningsWarnings indicate crucial configuration considerations. Pay close attention to warning messages.

Warning! Example of a warning.

Comments and SuggestionsYour comments are important to us. We encourage you to tell us what you like, or whatyou would like to see changed about PeopleBooks and other PeopleSoft reference andtraining materials. Please send your suggestions to:

PeopleSoft Product Documentation Manager PeopleSoft, Inc. 4460 Hacienda Drive Pleasanton, CA 94588

Or send email comments to [email protected].

While we cannot guarantee to answer every email message, we will pay careful attentionto your comments and suggestions.

Common Elements in These PeopleBooksAs of Date The last date for which a report or process includes data.

Business Unit An ID that represents a high-level organization of business information.You can use a business unit to define regional or departmentalunits within a larger organization.

Description Enter up to 30 characters of text.

Effective Date The date on which a table row becomes effective; the date that an actionbegins. For example, to close out a ledger on June 30, the effective datefor the ledger closing would be July 1. This date also determines whenyou can view and change the information. Pages or panels and batchprocesses that use the information use the current row.

Once, Always, and Don’tRun

Select Once to run the request the next time the batch process runs. After thebatch process runs, the process frequency is automatically set to Don’t Run.

Select Always to run the request every time the batch process runs.

Select Don’t Run to ignore the request when the batch process runs.

PeopleSoft Proprietary and Confidential xiii

General Preface

Report Manager Click to access the Report List page, where you can view report content,check the status of a report, and see content detail messages (which showyou a description of the report and the distribution list).

Process Monitor Click to access the Process List page, where you can view thestatus of submitted process requests.

Run Click to access the Process Scheduler request page, where you can specify thelocation where a process or job runs and the process output format.

Request ID An ID that represents a set of selection criteria for a report or process.

User ID An ID that represents the person who generates a transaction.

SetID An ID that represents a set of control table information, or TableSets.TableSets enable you to share control table information and processing optionsamong business units. The goal is to minimize redundant data and systemmaintenance tasks. When you assign a setID to a record group in a businessunit, you indicate that all of the tables in the record group are shared betweenthat business unit and any other business unit that also assigns that setID tothat record group. For example, you can define a group of common job codesthat are shared between several business units. Each business unit that sharesthe job codes is assigned the same setID for that record group.

Short Description Enter up to 15 characters of text.

See AlsoUsing PeopleSoft Applications

PeopleSoft Process Scheduler

xiv PeopleSoft Proprietary and Confidential

Setting Up Workforce Analytics ApplicationsPreface

Welcome to the PeopleSoft 8.8 Setting Up Workforce Analytics Applications PeopleBook. This PeopleBookdescribes how to set up your Workforce Analytics applications. This preface discusses:

• PeopleSoft Enterprise Warehouse PeopleBooks.

• Other related PeopleBooks.

PeopleSoft Enterprise WarehouseAdditional, essential information describing the setup and design of your system appears in a companionvolume of documentation called PeopleSoft 8.8 Enterprise Warehouse PeopleBook.

Note. One or more pages in PeopleSoft Workforce Analytics applications operate in deferred processing mode.Deferred processing is described in the preface in the PeopleSoft 8.8 Enterprise Warehouse PeopleBook.

Other Related PeopleBooksThis PeopleBook provides detailed implementation and setup information common to all, or morethan one, of the following PeopleSoft Workforce Analytics applications:

• PeopleSoft 8.8 Workforce Planning

• PeopleSoft 8.8 Workforce Rewards

• PeopleSoft 8.8 Workforce Scorecard

PeopleSoft Proprietary and Confidential xv

Preface

xvi PeopleSoft Proprietary and Confidential

CHAPTER 1

Getting Started with PeopleSoft WorkforceAnalytics Applications

This chapter provides an overview of Workforce Analytics applications and discusses how to:

• Set up the PeopleSoft Enterprise Warehouse.

• Implement PeopleSoft Workforce Analytics applications.

PeopleSoft Workforce Analytics OverviewPeopleSoft Workforce Analytics applications provide the tools to measure, manage, andmaximize your workforce performance. These comprise:

• PeopleSoft Workforce Rewards for planning compensation and retention initiatives.

• PeopleSoft Workforce Planning for aligning your workforce competencies with organizational goals.

• PeopleSoft Workforce Scorecard for assessing the impact of your workforce on enterpriseoperations to determine how best to meet future business objectives.

• PeopleSoft HRMS Warehouse for analyzing your workforce trends, performing compensation andbenefits comparisons, and gauging your effectiveness against external benchmark data.

Setting Up PeopleSoft Enterprise WarehousePrior to implementing PeopleSoft Workforce Analytics applications you must complete the setup of theEnterprise Warehouse. These tasks are described in PeopleSoft Enterprise Warehouse documentation.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook

PeopleSoft Workforce Analytics ImplementationSet up tables to enable your system to support PeopleSoft Workforce Analytics applications features.

PeopleSoft Proprietary and Confidential 1

Getting Started with PeopleSoft Workforce Analytics Applications Chapter 1

In the planning phases of your implementation, take advantage of all PeopleSoft sources ofinformation, including installation guides, ETL mapping reports, and data models. A completelist of these resources is in the preface of the PeopleSoft 8.8 Enterprise Warehouse PeopleBook,with information about where to find the most current version of each.

Note. The following table lists steps for a suggested implementation sequence, and thissequence provides a convenient structure for this documentation. The actual sequence bywhich you implement and use the application may differ.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “PeopleSoft Enterprise Warehouse Preface”

Setting Up PeopleSoft Workforce Analytics Application TablesThis section lists the steps to set up PeopleSoft Workforce Analytics applications.

Step Reference

1. Import internal source data to ODS tables using ETL. PeopleSoft 8.8 Enterprise Warehouse PeopleBook

2. Review data warehouse tables delivered with thesystem.

• PeopleTools Application Designer for the specificationsof the R00s, D00s, and F00s delivered with the system.

• PeopleSoft Customer Connection for suggestedETL mapping sequences, and transformation rulesfor mapping PeopleSoft application data to the datawarehouse tables.

3. Design and set up workforce-related trees. Note. At this point you have the option of loading thedimension data for building your trees. Then you can loadthe remainder of the dimension data later.

4. Perform workforce-related dimension and tree nodemapping.

Note. At this point you have the option of loading thedimension data for any dependencies in these pages. Thenyou can load the remainder of the dimension data later.

5. Run Data Loader to load the data warehouse tables. • PeopleSoft 8.8 Enterprise Warehouse PeopleBook

• PeopleSoft Customer Connection for suggested tableloading sequences, and transformation rules for mappingPeopleSoft application data to the Data Warehouse tables.

6. Review and edit data for D00s and R00s. Chapter 3, “Importing Internal Source Data to DataWarehouse Tables,” page 13

7. Review and modify the flat file definitions, datawarehouse tables, and ETL maps for external surveydata.

Chapter 4, “Importing External Survey Data to DataWarehouse Tables,” page 65

Note. The remaining steps from here to the end ofthis list apply to PeopleSoft HRMSWarehouse andPeopleSoft Workforce Rewards. External survey data is notincorporated into PeopleSoft Workforce Planning

8. Run the setup batch ETLs to populate the survey datawarehouse tables, and the survey mapping definitiontables.


2 PeopleSoft Proprietary and Confidential

Chapter 1 Getting Started with PeopleSoft Workforce Analytics Applications

Step Reference9. Review and edit the data in the survey data warehouse

tables.Chapter 4, “Importing External Survey Data to DataWarehouse Tables,” page 65

10. Complete survey mapping definition pages prior toLoad ETL batch.


11. Review the survey mappings. Chapter 4, “Importing External Survey Data to DataWarehouse Tables,” page 65

12. Run the survey Load ETL batch. Chapter 4, “Importing External Survey Data to DataWarehouse Tables,” page 65

13. Run the survey Ongoing ETL batches as needed. Chapter 4, “Importing External Survey Data to DataWarehouse Tables,” page 65

14. Run Crystal Reports to review survey dimension andmapping data as needed.



Getting Started with PeopleSoft Workforce Analytics Applications Chapter 1


CHAPTER 2

Designing Your PeopleSoft WorkforceAnalytics System

This chapter provides discusses how to:

• Define your operational structure.

• Process multiple currencies.

• Set up TableMaps and DataMaps.

• Create model IDs, scenario IDs, and jobstream metadata.

Defining Your Operational StructureWhen you set up the PeopleSoft Enterprise Warehouse system, you define your operational structureusing business units and SetIDs. There is logic specific to PeopleSoft Workforce Analytics weshould review at this time, regarding the determination of business units, SetIDs, and currency codeswhen bringing workforce data into PeopleSoft Enterprise Warehouse.

First, recall some common principles of the PeopleSoft Enterprise Warehouse datastructures and data migration logic:

• All fact tables (F00s) are keyed by business unit.

• Generally dimension tables (D00s) are keyed by SetID, but depending on the source table or thebusiness need of the EPM application, they may contain business units instead.

• Generally reference tables (R00s) are keyed by SetID, but depending on the source table or thebusiness need of the EPM application, they may contain business units instead.

• Each EPM business unit has one base currency code to support integrated data analysis on a common point.

• Each fact, dimension, or reference table that contains monetary values has an amount in the basecurrency of the related business unit (*_ BCE_AMT or *_BCE), and an amount in another currencywith a code identifying that currency (*_AMT and CURRENCY_CD).

• Each dimension or reference table that contains monetary values must have a SetID that relatesonly to business units with common base currency codes. (For example, if you have a salarystructure defined in Canadian Dollars that is keyed by a SetID, that SetID must only relateto business units with a base currency of Canadian Dollars.)

• When importing business units from a source system, they are mapped into the Enterprise Warehouserather than moved directly over; in the event you are consolidating for analysis purposes.


Designing Your PeopleSoft Workforce Analytics System Chapter 2

The data migration logic specific to PeopleSoft Workforce Analytics arises when the source table fromPeopleSoft HRMS has neither a business unit nor a SetID as a key. When this is the situation, you definethe business unit or SetID to use, with the exception being tables keyed by employee ID. In this case, thebusiness unit and corresponding base currency code are retrieved from the employee’s job record.

Note. Before you load internal source data into your data warehouse tables, map the business units fromyour PeopleSoft HRMS system to the business units you want to use in your PeopleSoft EPM system.Select Define Business Rules EPM, TableSets and Business Units, Source Unit Mapper.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Defining Your Operational Structure”

PeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Processing Multiple Currencies”

Processing Multiple Currencies for WorkforceAnalytics Applications

In PeopleSoft Workforce Analytics applications each fact, dimension, or reference table that containsmonetary values stores the amount in the original currency, along with a code identifying thatcurrency. Generally, these values are stored in fields named *_AMT or *_RT, and CURRENCY_CD.Tables containing monetary values also have a corresponding amount in the base currency ofthe related business unit. These values are known as base currency equivalent amounts (BCEs).Generally, BCEs are stored in fields named *_ BCE_AMT or *_BCE.

When you import source data, the data migration process loads the source amounts andcurrency codes. The process also defaults BCE amounts to zero (or to the same value as therelated amount field if your maps have been customized). Then you run a subsequent currencyconversion process that populates the BCE amount fields.

In PeopleSoft HRMS Warehouse and PeopleSoft Workforce Rewards certain Application Engine processesuse the BCE amount rather than the amount field. As a result, the data migration process and the subsequentcurrency conversion process that populates the BCE amount fields are critical. You must remember to run thecurrency conversion process (PF_MULT_CURR) after loading monetary data. This process correctly populatesall of the BCE amounts for the Workforce Analytics tables in the warehouse. You must do this before you canuse any HRMS Warehouse or workforce simulation data. When you run the currency conversion process, thebase currency equivalent (*_BCE_AMT or *_BCE) is calculated using the base currency code of the relatedEPM business unit, the source amount (*_AMT) and source amount currency code (CURRENCY_CD).

If your system is set up to run in a multiple currency environment, set up and run the currencyconversion process for the following tables and fields in Enterprise Warehouse:


Chapter 2 Designing Your PeopleSoft Workforce Analytics System

Table Base Currency EquivalentAmount Field Name

Amount Field Name

ACMPLISHMNT_F00 BONUS_ FRA_BCE_AMT BONUS_AMOUNT_FRA

CRSESESNCST_D00 FINANCD_CSTFRA_BCE FINANCED_COST_FRA

CRSESESNCST_D00 PER_UNIT_BCE_AMT PER_UNIT_COST

EMPLOYMENT_D00 GVT_APTLIMTAMT_BCE GVT_APPT_LIMIT_AMT

JOB_F00 ANNL_BBASE_BCE_AMT ANNL_BENEF_BASE_RT

JOB_F00 ANNUAL_BCE_AMT ANNUAL_RT

JOB_F00 CHANGE_BCE_AMT CHANGE_AMT

JOB_F00 COMPRATE_BCE_AMT COMPRATE

JOB_F00 HOURLY_BCE_AMT HOURLY_RT

JOB_F00 MONTHLY_BCE_AMT MONTHLY_RT

JOBCODE_D00 SURVEY_SAL_BCE_AMT SURVEY_SALARY

JOB_INTRADY_F00 ANNL_BBASE_BCE_AMT ANNL_BENEF_BASE_RT

JOB_INTRADY_F00 ANNUAL_BCE_AMT ANNUAL_RT

JOB_INTRADY_F00 CHANGE_BCE_AMT CHANGE_AMT

JOB_INTRADY_F00 COMPRATE_BCE_AMT COMPRATE

JOB_INTRADY_F00 DAILY_BCE_AMT DAILY_RT

JOB_INTRADY_F00 CTG_RATE_BCE CTG_RATE

JOB_INTRADY_F00 GVT_ANLRTNOLOC_BCE GVT_ANLRTNOLOC

JOB_INTRADY_F00 GVT_ANUITYOFST_BCE GVT_ANUITYOFST




Amount Field Name

JOB_INTRADY_F00 GVT_BIWEEKLYRT_BCE GVT_BIWEEKLYRT

JOB_INTRADY_F00 GVT_BWRTNOLOC_BCE GVT_BWRTNOLOC

JOB_INTRADY_F00 GVT_COMPRATE_BCE GVT_COMPRATE

JOB_INTRADY_F00 GVT_DAILY_RT_BCE GVT_DAILY_RT

JOB_INTRADY_F00 GVT_DLYRTNOLOC_BCE GVT_DLYRTNOLOC

JOB_INTRADY_F00 GVT_FEHB_PCT_BCE GVT_FEHB_PCT

JOB_INTRADY_F00 GVT_FGLIBSCPCT_BCE GVT_FGLIBSCPCT

JOB_INTRADY_F00 GVT_FGLIOPTPCT_BCE GVT_FGLIOPTPCT

JOB_INTRADY_F00 GVT_HRLYRTNOLC_BCE GVT_HRLYRTNOLC

JOB_INTRADY_F00 GVT_LIVING_AMT_BCE GVT_LIVING_AMT

JOB_INTRADY_F00 GVT_LOCALITYADJ_BCE GVT_LOCALITYADJ

JOB_INTRADY_F00 GVT_MNLYRTNOLC_BCE GVT_MNLYRTNOLC

JOB_INTRADY_F00 HOURLY_BCE_AMT HOURLY_RT

JOB_INTRADY_F00 MONTHLY_BCE_AMT MONTHLY_RT

JOB_INTRADY_F00 UNION_FEE_AMT_BCE UNION_FEE_AMOUNT

PRIORWRKEXP_D00 ENDING_RATE_BCE ENDING_RATE

SAL_GRADE_D00 MAX_RT_ANN_BCE_AMT MAX_RT_ANNUAL

SAL_GRADE_D00 MAX_RT_HR_BCE_AMT MAX_RT_HOURLY

SAL_GRADE_D00 MAX_RT_MON_BCE_AMT MAX_RT_MONTHLY




Amount Field Name

SAL_GRADE_D00 MID_RT_ANN_BCE_AMT MID_RT_ANNUAL

SAL_GRADE_D00 MID_RT_HR_BCE_AMT MID_RT_HOURLY

SAL_GRADE_D00 MID_RT_MON_BCE_AMT MID_RT_MONTHLY

SAL_GRADE_D00 MIN_RT_ANN_BCE_AMT MIN_RT_ANNUAL

SAL_GRADE_D00 MIN_RT_HR_BCE_AMT MIN_RT_HOURLY

SAL_GRADE_D00 MIN_RT_MON_BCE_AMT MIN_RT_MONTHLY

SAL_STEP_D00 ANNUAL_BCE_AMT ANNUAL_RT

SAL_STEP_D00 HOURLY_BCE_AMT HOURLY_RT

SAL_STEP_D00 MONTHLY_BCE_AMT MONTHLY_RT

ST_GRANT_F00 GRANT PRC_BCE_AMT GRANT_PRICE

WA_BEN_HST_F00 WA_ANNUAL_BCE_AMT WA_ANNUAL_AMT

WA_BEN_VALU_TBL ANNUAL_BCE_AMT ANNUAL_RT

WA_COMP_HST_F00 WA_AMOUNT_BCE WA_AMOUNT

WA_RECR_EXP_F00 PER_EE_CST_BCE_AMT PER_EE_COST

WA_REVWSCL_R00 AMOUNT_PER_PT_BCE AMOUNT_PER_POINT

WA_TRNCST_F00 PER_EE_CST_BCE_AMT PER_EE_COST

WA_TRNCST_F00 TUIT_REIMB_BCE_AMT TUIT_REIMB_AMT

WA_TRNSESSN_D00 PER_EE_CST_BCE_AMT PER_EE_COST

WA_TRNSESSN_D00 PER_UNIT_CST_BCE_AMT PER_UNIT_COST



Note. For any customized fields other than those delivered, modify the delivered Application Engineprocess, job, and rule sets to include your custom fields. If your implementation does not have a multiplecurrency environment, you can bypass the need to run the currency conversion process by re-mappingthe ETL maps to populate all BCE amounts with the corresponding source amounts.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Processing Multiple Currencies”

Setting Up TableMaps and DataMapsIn some PeopleSoft Workforce Analytics applications you specify datasets, filters, or constraintsfor use in creating scenarios. They are based on TableMaps, and provide a user-defined set ofinformation to the engines. Here are some examples of the ways you can use TableMap-baseddatasets, filters, or constraints in PeopleSoft Workforce Analytics applications:

• In datasets when setting up data elements in the Compensation Strategy moduleof PeopleSoft Workforce Rewards.

• In constraints or filters for setting up KPIs in PeopleSoft Workforce Scorecard.

• In constraints or filters to set up workforce groups for use in PeopleSoft WorkforceRewards and PeopleSoft Workforce Planning.

• In TableMaps, DataMaps, constraints, and filters when building data marts for PeopleSoftHRMS Warehouse and PeopleSoft Workforce Rewards.

In PeopleSoft Workforce Analytics, we deliver numerous workforce related TableMaps andDataMaps, to help streamline the process for you. To review the delivered TableMaps, or createadditional ones, access the pages using the following navigation:

• Entprse Warehouse Processing, Define Metadata, TableMap

• Entprse Warehouse Processing, Define Metadata, DataMap

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Setting Up and Using Metadata”

Creating Model IDs, Scenario IDs, and Jobstream MetadataYou must set up the metadata for your model IDs and scenario IDs in PeopleSoft Enterprise Warehouse.Sample data models and scenarios are delivered as examples, but are not system data. To create yourmodels and scenarios, access the pages using the following navigation:

• Entprse Warehouse Processing, Define Business Framework, Models

• Entprse Warehouse Processing, Define Business Framework, Scenarios



For each business process module requiring Application Engine processing we deliver ApplicationEngine IDs, job IDs, and jobstreams as system data. The delivered metadata is discussed in therelevant sections of the workforce application documentation. If you need to create additionaljobs or jobstreams, access the pages using the following navigation:

• Entprse Warehouse Processing, Update/Run Jobstreams, Job Metadata

• Entprse Warehouse Processing, Update/Run Jobstreams, Processes in Jobstream

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Defining Your Operational Structure,” Defining Models

PeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Streamlining Processing with Jobstreams”




CHAPTER 3

Importing Internal Source Data to DataWarehouse Tables

This chapter discusses how to:

• Review the delivered ETL maps and data warehouse tables.

• Set up trees.

• Map personnel actions for Job_F00.

• Map locations to geography ID codes.

• Map compensation codes and plan values.

• Load data warehouse tables.

• View and edit data in dimension and reference tables.

Understanding Internal Source DataInternal source data is the data from your organization’s PeopleSoft HRMS system, or other enterprisemanagement systems, that you use to populate the PeopleSoft Enterprise Warehouse data warehousetables. You first import the data from the PeopleSoft HRMS system into the Operational Data Store (ODS)staging tables using the Informatica PowerMart tool. This chapter assumes you have done this already.Then you use the Data Loader to load the data from the ODS into the data warehouse tables.

Reviewing ETL Maps and Data Warehouse TablesTo review the ETL maps and data warehouse tables:

• Begin by evaluating your own internal source tables and planning your approach.

• Use PeopleTools Application Designer to review the ODS tables and data warehouse tablesdelivered with PeopleSoft Enterprise Warehouse. Determine how you want to structureyour system to best fit the needs of your organization.

• Evaluate the ETL maps delivered in the Informatica PowerMart repository files that you useto import internal source data to the ODS staging tables, and determine if they are properlyconfigured to meet the needs of your organization.


Importing Internal Source Data to Data Warehouse Tables Chapter 3

• See PeopleSoft Customer Connection for a listing of table loading sequences for mapping PeopleSoftapplication data to the ODS tables and data warehouse tables.

Warning! Any changes you make to our delivered data warehouse tables have the potential to affectApplication Engine processes, Insight analysis templates, and PeopleCode processing throughoutthe system. Evaluate and execute these types of changes very carefully.

Setting Up TreesThis section provides an overview of trees in PeopleSoft 8.8 Workforce Analyticsapplications and discusses how to:

• Review trees.

• Set up the account tree.

• Set up the compensation code tree.

• Set up the competency tree.

• Set up the financials-related department tree.

• Set up the FINCODE tree.

• Set up the geography tree.

• Set up the organization tree.

• Set up the INDUSTRY tree.

• Set up the JOBCODE tree.

• Set up the position tree.

• Set up the UNITCODE tree.

• Define which trees the system uses.

Understanding Workforce Analytics TreesTrees define hierarchical relationships for dimensions in PeopleSoft Enterprise Warehouse. Treesadd a visual layer to dimensions, helping you see where detail items (such as departments or jobcodes) fit into your organization’s structure. Insight analysis templates in the HRMS Warehouseuse these hierarchical relationships to facilitate drilldown and roll-up through dimension data. Thesystem also uses these trees to control and organize processing rules.

Warning! PeopleTools does not require the use of levels when creating trees. However, in PeopleSoftEnterprise Warehouse, the use of levels is required whenever a tree is referenced by the Insight analysistemplates for the HRMS Warehouse. PeopleSoft Workforce Analytics trees provide a hierarchical roll-upstructure for the system dimensions. If you don’t use levels within your trees, the analysis templatescannot access the data in the data warehouse tables. For each of the trees we discuss in this section, youmust specify the use of levels on the Tree Definition Properties page, and you must define each level.The maximum number of tree levels that you can define for trees used with Insights is 16.


Chapter 3 Importing Internal Source Data to Data Warehouse Tables

Before we summarize the main trees in PeopleSoft Workforce Analytics, here’s a refresheron some of the tree terminology used in the table:

Tree Category This is the first level you see when you open PeopleTools Tree Managerto view the sample trees. The following two categories are especiallyimportant for PeopleSoft Workforce Analytics:

• SHARE: This category indicates the tree is used across the entire PeopleSoftEnterprise Performance Management product line. This categorycontains sample trees only, having a SetID of SHARE.

• WA: This category indicates the tree is used primarily within the PeopleSoftWorkforce Analytics applications. This category contains sample trees thatmust be used as templates for the full functionality of PeopleSoft WorkforceAnalytics to work properly. These trees have a SetID of MODEL or SHARE.The ones with SetID SHARE are sample trees provided as examples. Theones with SetID MODEL are templates your tree must look like.

Tree Structure ID This identification code corresponds to one of the main dimensions in thesystem. When you set up your trees in your system database, the followingtree structure IDs must be used for PeopleSoft Workforce Analytics tofunction properly: JOB_WA01, CMP_WA02, GEO_WA03, IND_WA04,FIN_WA05, UNT_WA06, and ORG_WA07, POS_WA08.

Tree Name This is the name for an individual tree. You must create your own trees,and you can give them any names you choose.

Sample This identifies that the tree that is delivered as sample data in your demodatabase (SetID = SHARE or MODEL). Trees with a SetID of SHAREare for your use as an example.The one tree with a SetID of MODELis for you to use as a template for creating your tree.

Reviewing Trees Used in PeopleSoft Workforce AnalyticsThe following table lists the trees you may need to set up for the various PeopleSoft WorkforceAnalytics applications. The last column uses these abbreviations:

PWSC PeopleSoft Workforce Scorecard

PWFI PeopleSoft HRMS Warehouse

PWRW PeopleSoft Workforce Rewards

PWDP PeopleSoft Workforce Planning



Tree StructureID/ Tree Name/Dimension Name

Use Sample withSetID of …

Tree Category(SHARE or WA)

PeopleSoft WorkforceAnalytics Application

ACCOUNT /WFA_ACCOUNT /WFAAccount

SHARE SHARE PWSC, PWFI

CMP_WA02 /COMPCODE /Compensation Code

MODEL WA PWSC, PWFI, PWRW

WA_COMPTENCY /WP_COMPETENCY /Competency

SHARE WA PWDP (optional)

DEPT ID /DEPARTMENT /(Financials-related)Department

SHARE SHARE PWSC, PWFI

FIN_WA05 / FINCODE /Financial Size

SHARE SHARE PWRW

GE0_WA03 /GEOGRAPHY /Geography

SHARE SHARE PWFI, PWRW

PWDP (optional)

ORG_WA07 /ORG/DEPT_SECURITY/ Organization (orDepartment)


PWDP (optional)

IND_WA04 / INDUSTRY/ Industry Type

SHARE SHARE PWRW

JOB_WA01 / JOBCODE /Job Code


POS_WA08 / POSITION/ Position

SHARE SHARE PWFI

UNT_WA06 /UNITCODE / Unit Size

SHARE SHARE PWRW



Note. Before you begin building your trees you have the option of loading the dimension data neededto build the trees. Then you can load the remainder of the dimension data later. Before you load anydimension data into your system, we strongly recommend you read the remainder of this chapter, and thechapter in this book entitled “Importing External Survey Data into Data Warehouse Tables.”

Note. If your implementation includes PeopleSoft HRMS Warehouse, depending on the reportingtool you choose, you may need to flatten the PeopleSoft dimension trees before processingthem. Consult with your systems implementation team.

Setting Up the Account TreeThis tree provides structure for the WFA account (Workforce Analytics account) dimension,for general ledger roll-up and drilldown.

It is a standard tree, meaning it has leaves, or details. You can expand the number oflevels of nodes and add nodes, and change and add details as needed to suit the revenueand expense account structure for your organization.

Setting Up the Compensation Code TreeThis tree provides structure for the compensation code dimension. When you create your tree you must use atree structure ID of CMP_WA02. All earnings codes, deduction codes, benefits plan types, and pay item namecodes from your source data must map to a compensation code if you plan to include them in your analysis.

It is a winter tree, meaning it has nodes but no details. The Model version of the tree has the minimumnumber of levels and the necessary nodes required for the system to aggregate your compensation dataproperly. The delivered nodes must be used for data to be correctly interpreted by the system.

You can add lower levels of nodes, and add nodes to the existing levels, as needed to suit the needs of yourorganization. To add nodes you use the Compensation Code page (WA_COMPCODE_D00).

On the COMPCODE tree all regular base pay plans should point to or roll up into the tree node 600 −Regular Base Compensation. Overtime earnings codes should point to or roll up into the 610 − PremiumBase Compensation tree node. Similarly, all health benefit plans should point to or roll up into the 550− Medical tree node, under the 450 − Health & Welfare Benefits tree node.

Later in the setup process you use the compensation mapping pages to map your EarningsCodes and Deduction Codes to these compensation codes.

See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” MappingCompensation Codes and Plan Values, page 26



Setting Up the Competency TreeThis tree provides structure for the competency dimension, that is, you can use it to provide a hierarchicalstructure for competency groupings. The competency tree is used in PeopleSoft Workforce Planning,although its use is optional. If you choose to use a competency tree, then you must use tree structureWA_COMPETENCY. Use the sample tree we deliver (tree structure WA_COMPETENCY, tree nameWP_COMPETENCY) as an example. The nodes are competencies and there are no details. It isimportant that you note this is not exactly the same as the PeopleSoft HRMS competency tree, whichhas nodes that are competency types, and details that are competencies.

Setting Up the Financials-Related Department TreeThis tree provides structure for the financials-related department dimension. The system uses this treeto roll up account data through the accounting relationship for your departments.

It is a standard tree, meaning it has leaves, or details. You can expand the number oflevels of nodes and add nodes, and change and add details as needed to suit the financialroll-up structure of the departments in your company.

The details, or leaves, for the DEPARTMENT tree come from the DEPARTMENT_TBL.DEPTIDfield. Either you import, using ETL, the department IDs that populate the DEPARTMENT_TBLtable, or you add or change departments using the Department Table page.

Setting Up the FINCODE TreeThis tree provides a hierarchical structure for the financial size dimension. This tree is primarily usedin the Workforce Rewards Market Compensation module, to deal with importing external surveydata. You use financial codes to define the relative financial size of an organization, categorizedata from external survey sources, and validate comparison to data for your organization. Whenyou create your tree you must use a tree structure ID of FIN_WA05.

It is a winter tree, meaning it has no leaves or details. You can change the labels andrange values for the nodes to financial categories appropriate for your industry. Use theWA_FINCODE_D00 page to create the nodes for the tree.

Setting Up the Geography TreeThis tree provides structure for the geography dimension. When you create your tree you must usea tree structure ID of GE0_WA03. All locations (from the location table) for your internal sourcedata must map to, and roll up to, a geography ID (identification) code.

It is a winter tree, meaning it has no leaves or details.

Review all of your locations in your internal source data, and determine the GEOGRAPHYtree nodes (geography ID codes) you want them to map to. Then use the Geography page tocreate the Geography ID codes used for the nodes of the tree.

Once you’ve created a GEOGRAPHY tree, map all of your location codes to nodes on this tree. You can importyour locations into the LOCATION_D00 table, or add or change locations using the Locations page. Later inthe setup process you use the WA_LOCATION_MAP page to map your locations to these geography ID codes.



See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” MappingLocations to Geography ID Codes , page 23

Setting Up the Organization (Department) TreeThis tree provides structure for the organizationally related department dimension. When you createyour tree you must use a tree structure ID of ORG_WA07. In this structure your departments are tiedto their organizational reporting hierarchy. The system uses this tree to roll up departmental level data,such as compensation data for employees within departments. A secondary purpose of this tree isthat it can provide a reference for setting up row-level employee security.

It is a winter tree, meaning it has no details or leaves. It uses the departments from thedepartment table (DEPARTMENT_TBL) for its nodes.

Note. If your implementation includes row-level security at the employee level, based on JOB_F00 andPERSONAL_D00, then first load the JOB_F00 and PERSONAL_D00 tables before setting up security.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Securing Your System,” Securing WorkforceAnalytics Applications with Row-Level Group Security

Setting Up the INDUSTRY TreeThis tree provides structure to the industry type dimension. Industry codes are primarily used inthe Workforce Rewards Market Compensation module, to deal with importing external survey data.You use industry codes to define the industry an organization is in, categorize data from externalsurvey sources, and validate comparison to data for your organization.

It is a winter tree, meaning it has no leaves or details. When you create your tree you must use a tree structure IDof IND_WA04. Use the WA_INDUSTRY_D00 page to create the nodes for the tree, called industry ID codes.You can change the labels and range values for the nodes to industries more appropriate for your organization.

Setting Up the JOBCODE TreeThis tree provides structure for the job code dimension. When you create your tree you must use a treestructure ID of JOB_WA01. The JOBCODE tree must have at least two levels. The highest level isfor all job codes. The next level down is for logical groupings of job codes into tree nodes called jobcode sets. The leaves of the job code set nodes are the individual job codes.

This is a standard tree, meaning it has details or leaves.

You use the Job Code Set page to create the nodes for the tree. A job code set is a group of related job codes, orany node on the JOBCODE tree. Most nodes are only labels to define relationships. The real meaning is inthe details of the tree, which are the job codes grouped together under that node. You either import your jobcodes to the JOBCODE_D00 table using ETL, or view and edit job codes using the Job Code page.



Setting Up the Position TreeThis tree provides structure for the position dimension. When you create your tree you must use a treestructure ID of POS_WA08. You import position data into the POSITION_D00 table. You can use thePOSITION_D00 page to access these positions and use them for the nodes for the tree.

It is a winter tree, meaning it has no details or leaves. It uses the positions from theposition table (POSITION_D00) for its nodes.

Setting Up the UNITCODE TreeThis tree provides structure for the unit size dimension. Unit codes are primarily used in the WorkforceRewards Market Compensation module, to deal with importing external survey data. You use unit codesto define the relative size of an organization (using a criteria other than a financial one), categorize datafrom external survey sources, and validate comparison to data for your organization.

It is a winter tree, meaning it has no leaves or details. When you create your tree you must use a tree structureID of UNT_WA06. You use the WA_UNITCODE_D00 page to create the nodes for the tree, called unit codes.You can change the labels and range values for the nodes to a unit of measure more appropriate for your industry.

Defining Which Trees the System UsesOnce you have set up trees for PeopleSoft Workforce Analytics, use the Workforce Analytics, WorkforceSetup, Setup Workforce Trees page to define which versions of the trees the system uses. The page isdiscussed in detail in the chapter titled “Importing External Survey Data to Data Warehouse Tables.”

See AlsoChapter 4, “Importing External Survey Data to Data Warehouse Tables,” Setting Up Workforce Trees, page 75

Mapping Personnel Actions for JOB_F00To map personnel actions for setting up the JOB_F00 table you:

1. Review your PeopleSoft HRMS source data tables to determine which action codes to map to which actiontypes. Also determine which action and reason code combinations to map to which termination values.

2. Map your action type codes to survey action types using the Action Types page.

3. Map the action and reason combinations to termination values, and map the actions toyour action types, using the Action Reason Map page.

4. Use the Data Loader to populate the data warehouse tables, specifically JOB_F00.



Pages Used to Map Personnel ActionsPage Name Object Name Navigation Usage

Action Type WA_ACTION_TYPE Entprse WarehouseDimensions, HRMS,Common, Action Type.

Define personnel actiontypes, and map them topersonnel action types frombenchmark metrics surveys.The primary purpose of theaction type definitionis to facilitate roll-up anddrilldown for this attributein the HRMSWarehouseInsight analysis templates.

Action Reason Map WA_ACTN_RSN_DFN Entprse WarehouseDimensions, HRMS,Common, Action ReasonMap.

Map action and reasoncombinations from yourPeopleSoft HRMSsystem to the VoluntaryTerm(voluntary termination)field in PeopleSoftEnterprise Warehouse. Youcan also map the action andreason combinations tobenchmark survey actiontype codes on using thispage. The primary purposeof these attributes is tofacilitate turnover metricsin the HRMSWarehouseInsight analysis templates.

Termination Reason Mapreport

RUN_RWA_0002 Entprse WarehouseDimensions, HRMS,Common, TerminationReasonMap Report.

Run the Action ReasonVoluntary Flag CrystalReport (WAC0002). Use thereport output to review yourpersonnel action mappings.

Reviewing Source Table Action and Reason CodesReview your PeopleSoft HRMS source table (PS_ACTN_REASON_TBL) and identifyall the valid combinations of action code and reason code you want to use in PeopleSoftEnterprise Warehouse. Then determine whether they should map to the workforce terminationvalues Voluntary, Involuntary, or Not a Termination.

Also review your PeopleSoft HRMS source table action codes and determine which actiontypes you want to group them into. For example, your human resources organization mayalready have standard action types, or you may want to use the same action types used by yourcompany’s third-party provider of benchmark metric data.

Defining Action TypesAccess the Action Type page by entering an Action Type.



Action Type setup page

Note. There is no ETL map for the WA_ACTION_TYPE table. You define ActionTypes online prior to running Data Loader.

The personnel Action Type code that you entered to access this page is displayed at the top of the page.Once you’ve created these codes, you can use them on the Action Reason Map page.

Select a Benchmark Action Type from the list of valid values. You map your action type toa standardized personnel action type used in many benchmark metrics surveys. Valid valuesare Hire, Other, Promotion, Separation, and Transfer. Other includes all other action typesthat are not hires, separations, transfers or promotions.

Mapping Action and Reason CombinationsAccess the Action Reason Map setup page by entering a SetID, Action, and Reason Code.

Action Reason Map setup page

Note. There is no ETL map for the WA_ACTN_RSN_DFN table. You map action andreason combinations online prior to running ETL.

To open the page you select an Action Code, which is a translate table value. The valid values are based on thetranslate table values for the action code field in PeopleSoft HRMS. Indicate a Reason Code, if there is one.Enter only what you consider valid combinations of action and reason from PeopleSoft HRMS. For example,your organization may not want to use a combination in which the action is a Separation, and the reason is Null.



In PeopleSoft Workforce Analytics applications, some of the turnover metrics in the data martsrequire the ability to define whether an action and reason combination results in a termination, andwhether the termination is voluntary or involuntary. Enter the Voluntary Term (voluntary termination)code to which you want to map this action and reason combination. Valid values are from thetranslate table, and include Involuntary, Voluntary and Not a Termination.

Enter the Action Type to which you want to map this action and reason code combination. Prompt valuesare from the WA_ACTION_TYPE table, which you created using the Action Types setup page.

Reviewing Your Personnel Action MappingsAccess the Termination Reason Map report page.

At any point after you have completed the Action Type and Action Reason Map setup pages, orafter you have imported your source personnel action data, you can run the Action Reason VoluntaryFlag report (WAC0002) to review your personnel action mappings.

See AlsoAppendix A, “Appendix A: PeopleSoft Workforce Analytics Reports,” page 119

Loading Your Personnel Action DataOnce you’ve completed the two mapping pages, run Data Loader to import your personnel action data intothe data warehouse tables. For each incoming row of employee data the process validates the reason codeagainst the WA_ACTN_RSN_DFN table. If there is a mapping then the system places the appropriate value(voluntary, involuntary, or not a termination), along with the row of data into the Job Data (JOB_F00) table. Ifthere is no reason code mapping on the WA_ACTN_RSN_DFN table, then the data goes to the error table.

Mapping Locations to Geography ID CodesPeopleSoft Enterprise Warehouse uses a hierarchical structure for the geography dimension based ongeography ID codes and the geography tree. Locations roll up into geography ID codes for geographicalregions. To map locations to geography ID codes perform the following steps:

1. Review your PeopleSoft HRMS location source table, and determine what geographicalregions you want your locations to roll up to.

2. Use the Geography page to enter the geography IDs into the GEOGRAPHY_D00 table, andthen create your PeopleSoft Workforce Analytics GEOGRAPHY tree.

3. Use the Location page to enter locations into the LOCATION_D00 table.

4. Use the Geography ID Map setup page (WA_LOCN_MAP_DFN) to map yourlocation codes to geography IDs.

5. Load your location data into the data warehouse tables. The location codes and correspondinggeography ID codes are stored in the LOCATION_D00 table.



Pages Used to Map Locations to Geography IDsPage Name Object Name Navigation Usage

Geography IDMap WA_LOCN_MAP_DFN Entprse WarehouseDimensions, HRMS,Common, Setup GeographyIDMap

Map location codes toGeography IDs. Thesemappings are stored in theWA_LOCN_MAP_DFNtable.

Geography IDMap report RUN_RWA_0006 Entprse WarehouseDimensions, HRMS,Common, Geography IDMap Report

Run the GeographyID/Location MappingCrystal report (WAC0006).

Reviewing and Loading Source Table Location CodesReview your PeopleSoft HRMS location table. In PeopleSoft Workforce Analytics each locationmust roll up to a geographical region on the geography tree. For each of your locations determinethe type of geographical regions to which you want to map them.

For the first time setup, either load your PeopleSoft HRMS locations to the LOCATION_D00 tablewithout mapping, or manually enter the locations using the LOCATION_D00 page.

Entering Geography IDs and Creating a Geography TreeCreate a GEOGRAPHY tree where the nodes of the tree are geography IDs. Enter the nodes of theGEOGRAPHY tree using the Geography page. The values are stored in the GEOGRAPHY_D00 table.

See AlsoChapter 3, “Importing Internal Source Data to DataWarehouse Tables,” Setting Up the Geography Tree , page 18

Mapping Locations to Geography IDsAccess the Geography ID Map setup page by entering a SetID and Location.



Geography ID Map setup page

Location CodeThe City, County, State, Postal Code, and Country for this Location Code display from the LOCATION_D00table. Locations in different countries may display different address fields depending on the formattingyou previously defined in the Country Table, Address Format page.

Geography IDSince Geography ID is not a part of the PeopleSoft HRMS location table (PS_LOCATION_TBL),you must map each location to a geography ID. Select the Geography ID (identification) code towhich you want to map this location code. Valid values prompt from the GEOGRAPHY_VW table,and represent nodes on the GEOGRAPHY tree. You create geography IDs using the Geographypage. Your mappings are stored in the WA_LOCN_MAP_DFN table.

Reviewing Your Location and Geography ID MappingsAccess the Geography ID Map report page.

After you have completed the Geography ID Map setup page, or after you loaded your sourcelocation data into the data warehouse tables, you can run the Geography ID/Location MappingCrystal report (WAC0006), to review your mappings.

When you run the Data Loader to load location codes, the system checks the WA_LOCN_MAP_DFN table for mapping to a geography ID. Locations, and corresponding geographyIDs, are then stored in the LOCATION_D00 table.




Mapping Compensation Codes and Plan ValuesTo map compensation codes and plan values you:

1. Evaluate your PeopleSoft HRMS deduction and earnings codes, benefits plans, plantypes, and pay item name codes.

2. Create your COMPCODE tree and enter compensation codes on the Compensation Code setup page.

3. Use the compensation code mapping pages to map each PeopleSoft HRMS deduction code, earnings code,benefits plan type, or pay item name to a PeopleSoft Workforce Analytics compensation code.

4. Use the Benefits Valuation Map page to map any needed amount values and amounttypes into the WA_BEN_VALU_TBL table.

5. Run the Data Loader to load compensation data into the data warehouse tables.



Pages Used to Map Compensation Codes and ValuesPage Name Object Name Navigation Usage

Compensation DeductionMap

WA_COMP_DED_MAP Entprse WarehouseDimensions, HRMS,Compensation,Compensation DeductionMap

Map deduction codesand benefits plans fromthe PeopleSoft HRMSsystem to compensationcodes in PeopleSoftEnterprise Warehouse.Mappings are stored in theWA_COMP_DED_MAPtable.

Compensation EarningsMap

WA_COMP_EARN_MAP Entprse WarehouseDimensions, HRMS,Compensation,Compensation Earnings Map

Map earnings codes fromthe PeopleSoft HRMSsystem to compensationcodes in PeopleSoftEnterprise Warehouse.Mappings are stored in theWA_COMP_EARN_MAPtable.

Compensation GP PINMap(compensation globalpayroll pay item name map)

WA_COMP_PIN_MAP Entprse WarehouseDimensions, HRMS,Compensation,Compensation GP Pin Map

Map PIN (pay itemname) codes from thePeopleSoft Global Payrollsystem to compensationcodes in PeopleSoftEnterprise Warehouse.Mappings are stored in theWA_COMP_PIN_MAPtable.

Benefits Valuation Map WA_BEN_VALU_TBL Entprse WarehouseDimensions, HRMS,Benefits, Benefits ValuationMap

Assign a monetaryamount to a benefit, andto distinguish whether theamount is an employeecost, employee value,or employer’s cost. Thebenefits amounts andvalues you enter using thispage are stored on theWA_BEN_VALUE_TBLtable. Use this page forcompensation codes thatyou have already set up inthe COMPCODE treeand mapped in the CompDeduction CodeMap(HR) page.

Benefits Valuation Map RUN_RWA_0003 Entprse WarehouseDimensions, HRMS,Benefits, Benefits ValuationMap report page

Run the Benefit Value TableCrystal report (WAC0003).

Reviewing Source Table Earnings, Deductions and BenefitsTo load compensation data the system uses the following PeopleSoft HRMS source tables:



Compensation Type PeopleSoft HRMS Source Tables

Deductions PS_PAY_DEDUCTION, PS_PAY_CHECK, andPS_TOTAL_DED.

Benefits PS_DEPENDENT_BENEF, PS_COVRG_CD,PS_HEALTH_BENEFIT, PS_LIFE_ADD_BEN,PS_DISABILITY_BEN, PS_FSA_BENEFIT,PS_SAVINGS_PLAN, PS_VACATION_BEN,PS_LEAVE_PLAN, PS_CAR_PLAN, PS_RTRMNT_PLAN, and PS_PENSION_PLAN.

Earnings PS_PAY_EARNINGS, PS_PAY_CHECK, andPS_PAY_OTH_EARNS

Pay Item Names PS_GP_RSLT_ERN_DED, and PS_GP_PIN

Generate a list of the PeopleSoft HRMS deduction and earnings codes, benefits plans and plan types, andpay item names (PINs). Use this list to determine which ones you want to import into PeopleSoft EnterpriseWarehouse. Each earnings code, deduction code, benefit plan and PIN code that you want to import intoPeopleSoft Enterprise Warehouse must map to one compensation code in the target system. Multiple codes andplan types can map to the same compensation code, or each one can have a separate compensation code.

Also determine if any of these deductions, earnings or benefit plan types normally don’t have cost orvalue data stored in the PeopleSoft HRMS system. Most commonly this occurs for benefit plan-relatedinformation. For those items in need of a cost or value, first determine the cost or value, and then alsodetermine whether it applies to the employee, the employer, or both. For example, assume that your companyallows employees to enroll in a dental plan, and neither the employee nor the employer costs or values ofthe dental plan are tracked through payroll. In this situation you may want to set up data in PeopleSoftEnterprise Warehouse to track the dental plan costs and to whom these costs apply.

Entering Compensation Codes and Creating a COMPCODE TreeOnce you have a plan for mapping your compensation codes from the PeopleSoft HRMS sourcetables to PeopleSoft Enterprise Warehouse, your next steps are to create your compensation codeson the Compensation Code page, and to create the COMPCODE tree.

See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Upthe Compensation Code Tree, page 17

Loading Source Table DependenciesOn the compensation and benefits mapping pages certain fields prompt from ODS tables. You populate theODS tables by ETL prior to beginning work on setting up PeopleSoft Workforce Analytics. The followingtable summarizes the prompts for fields on the compensation and benefits mapping pages:



Compensation or Benefit Mapping Page ODS Prompt Tables

Compensation Deduction Map Fields for deductions prompt to WA_PLAN_DED_VWandWA_PLAN_TYP_VW. These views in turn look atDEDUCTION_TBL and BENEF_PLAN_TBL.

Compensation Earnings Map Field for earnings prompt directly to EARNINGS_TBL.

Compensation GP Pin Map Fields for pay item names prompt to the GP_PIN_TYPEtable andWA_PLAN_PIN_VW table. These views inturn look to the GP_PIN table.

Mapping Deductions and Benefit Plans to Compensation CodesAccess the Compensation Deduction Map page by entering a SetID and Plan Type.

Compensation Deduction Map setup page

Plan TypesWhen you open the page you are prompted to specify a Plan Type.Valid values are from the translatetable. If this mapping is for a general deduction select General Deduction. To map a benefit, selectfrom the other available values, which are summarized in the following table:

Plan Type Description Plan Type Description

401(k) 401(k) RetirementAccount

PERS Public EmployeesRetirement System

AD/D Accidental Deathor DismembermentInsurance

Personal Personal Leave




Benefits Program Benefits Program Profit Sharing Profit Sharing

Capital Accumulation Capital Accumulation Retirement CounselingCanada

Canadian RetirementCounseling

Company Car Company Car Short-term Disability Short-term DisabilityInsurance

Dental Dental Insurance Sick Sick Leave

Dependent AD/D Dependent AccidentalDeath or DismembermentInsurance

Standard Pension Standard Pension(Canada)

Dependent Care Dependent Care FlexibleSpending Account

Supplemental AD/D SupplementalAccidental Deathand DismembermentInsurance

Dependent Life Dependent Life Insurance Supplemental Life Supplemental LifeInsurance

Employee Stock PurchasePlan

Employee Stock PurchaseProgram

Supplemental Pension Supplemental Pension(Canada)

Family andMedicalLeave Act

Family Medical LeaveAct

Survivors Income Survivors Income

General Deduction General Deductions Thrift U.S. federal governmentemployee Thrift SavingsPlan

Health Care Can Canadian Health Care USDB Pension Plan 1 U.S. Defined BenefitPension Plan 1

Health Care Health Care FlexibleSpending Account

USDB Pension Plan 2 U.S. Defined BenefitPension Plan 2

IRA Individual RetirementAccount





Life and AD/D Life Insurance-Accidental Deathor DismembermentInsurance


Life Life Insurance USDB Pension Plan 5 U.S. Defined BenefitPension Plan 5

Long-term Disability Long-term DisabilityInsurance


Major Medical Major Medical U.S. Savings Bonds U.S. Savings Bonds

Medical Medical Vacation Vacation Leave

NQ Dental Non-Qualified DentalInsurance

Vacation Buy Vacation Leave Buy

NQ Vision Non-Qualified VisionInsurance

Vacation Sell Vacation Leave Sell

Nonelective Contrib Non-electivecontributions to aretirement savings orpension plan.

Visn/Hear Vision and HearingInsurance

FEGLI − Living Ben Federal Employees GroupLife Insurance − LivingBenefit

Option A Standard Option A - StandardOption in the FEGLIprogram

403(b) Type of U.S. retirementsavings program.

Retirement TSP 1% U.S. governmentretirement plan calledThrifts Savings Plan,where agency contributionis one percent.

Employer Only Retirement savingsprogram contributions,which are employers only.

WA Compensation CodeThe Benefit Plancolumn includes those deductions with a plan type other than 00 in the PeopleSoft HRMSsystem, such as Medical. Prompt values are from the WA_PLAN_TYP_VW table. Ten PeopleSoft HRMSsource tables contain data used to track benefits enrollment and migration status.



Note. If both vacation buy and sell values are to be analyzed, you must define them separately.

The Deduction Code column includes those deductions with a plan type of 00 in the PeopleSoft HRMS system,such as Parking Reimbursements orCharitable Contributions. Prompt values are from the%EDITTABLE table.

A Coverage Code displays when you open the page for a plan type of 10 (Health Benefit, suchas Medical). Examples of coverage codes are Employee Only, Employee & Spouse, Employee &Dependents, Family, and so on. Prompt values are from the WA_COVG_CD_R00 table. Trackingcoverage codes in your PeopleSoft Enterprise Warehouse serves two purposes:

1. You can track health benefit enrollment migration at a lower level than the plan type. For example,instead of using only one compensation code for all coverage levels of medical insurance, you could haveseveral lower level compensation codes for different coverage levels of medical insurance, all of whichroll up to a single parent compensation code for the generic category called medical insurance.

2. You can populate health benefits-related compensation data in WA_COMP_HST_F00 table,using the mappings in the WA_BEN_VALU_TBL table, more accurately. This is possiblesince you are allowing for different coverage costs for the different coverage levels, ratherthan accepting just one default cost value for all coverage levels.

Note. Any new compensation codes you create to accommodate multiple coverage codes per a singleplan type must be added to the COMPCODE_D00 table, and to the COMPCODE tree.

The Compensation Code is a required field in the sense that all of the benefit plans and deductions you wantto include in your data warehouse tables must be mapped to a compensation code, which must correspondto a code on the Compensation tree. Prompt values are from the WA_COMP_ACCT_VW table. Youneed only bring data into the data warehouse tables that supports your planned analyses. Any deductioncode or benefits plan type that is not mapped using this page is not be brought into the data warehousetables. Mappings entered in this page are stored in the WA_COMP_DED_MAP table.

Select an Amount Type from the list of translate table values. Valid values are (none), EmployeeExpense, Employee Val. = Employer Expense (employee value equals employer expense), EmployeeValue, and Employer Expense. This indicates whether the monetary value of the deduction or benefitis an expense or value, to the employee or the employer. This is only the default value for thecompensation code, and is overridden if the deduction class on the pay deduction row from PeopleSoftHRMS indicates it is either an employer expense or employee expense. It is also overridden if a rowis set up on the PeopleSoft Workforce Analytics WA_BEN_VALUE_TBL table for this compensationcode. The system uses the amount type to determine employee and employer compensation costs,especially in the PeopleSoft HRMS Warehouse Insight analysis templates.


Mapping Earnings to Compensation CodesAccess the Compensation Earnings Map page entering a SetID and Earnings Code.



Compensation Earnings Map setup page

Earnings CodeWhen you open the page you are prompted to specify an Earnings Code. Earnings are those values from theERNCD field on the PS_EARNINGS and PS_PAY_OTHER_EARNS tables from PeopleSoft HRMS.

WA Compensation CodeThe Compensation Code is a required field in the sense that all earnings you want to include in yourdata warehouse tables must be mapped to a compensation code, which must correspond to a codeon the Compensation tree. Prompt values are from the WA_COMP_ACCT_VW table. You needonly bring data into the data warehouse tables that supports your planned analyses. Any earningscode that is not mapped using this page is not brought into the data warehouse tables. Mappingsentered in this page are stored in the WA_COMP_ERN_MAP table.

Select an Amount Type from the list of translate table values. Valid values are (none), Employee Expense,Employee Val. = Employer Expense (employee value equals employer expense), Employee Value, andEmployer Expense. This indicates whether the monetary value of the earnings is an expense or value, toeither the employee or the employer. The system uses the amount type to determine employee and employercompensation costs, especially in the PeopleSoft HRMS Warehouse Insight analysis templates.

Mapping Pay Item Names to Compensation CodesAccess the Compensation GP Pin Map page entering a SetID and Element Type.



Compensation GP Pin Map setup page

Pay Element TypesWhen you open the page you are prompted to specify a pay Element Type. Pay Elements are fromthe PeopleSoft Global Payroll system GP_PIN table. This is the main record in that application forsetting up elements such as Earnings, Deduction, Absence Taken, and so forth.

WA PIN CodeEnter a PIN Number (pay item name code or number). The system displays the related pay item name. Thisfield corresponds to the PeopleSoft Global Payroll field PIN_NUM, for pay items within pay element types. Forexample, pay elements such as Earningsmight include pay items such as Salary Plans, Sick Plans, and so forth.

The Compensation Code is a required field in the sense that all PIN codes you want to include inyour data warehouse tables must be mapped to a compensation code, which must correspond to acode on the Compensation tree. Prompt values are from the WA_COMP_ACCT_VW table. Youneed only bring data into the data warehouse tables that supports your planned analyses. Any PINcode that is not mapped using this page is not brought into the data warehouse tables. Mappingsentered in this page are stored in the WA_COMP_PIN_MAP table.

Select an Amount Type from the list of translate table values. Valid values are (none), Employee Expense,Employee Val. = Employer Expense (employee value equals employer expense), Employee Value, andEmployer Expense. This indicates whether the monetary value of the earnings is an expense or value, toeither the employee or the employer. The system uses the amount type to determine employee and employercompensation costs, especially in the PeopleSoft HRMS Warehouse Insight analysis templates.

Entering Benefit Plan ValuesAccess the Benefits Valuation Map page by entering a SetID and Compensation Code.



Benefits Valuation Map setup page

Warning! Whenever you enter data in this page take care to ensure that you aren’t creating redundantdata. Only use this page to provide a valuation of benefits plans that don’t otherwise have an amountand value associated with them in PeopleSoft HRMS. That is, use it for a given compensationcode when that information is not available through payroll data, or when your source data doesnot provide the amounts and values that your company wants to track. Do not use this table forexpenses, or for duplicating information available from payroll data.

Select an Amount Type from the list of translate table values. Valid values are (none),Employee Expense, Employee Val. = Employer Expense (employee value equals employerexpense), Employee Value, and Employer Expense.

Use the prompt list values in the Currency Code field to indicate the currency for the benefit valueamount. Prompt values are from the currency code table (CURRENCY_CD_TBL).

Enter an amount for the benefit value, either as the Annual Rate or the annual Percent of Salary.

These mappings are stored in the WA_BEN_VALU_TBL table.

Reviewing Benefits Valuation MapsAccess the Benefits Valuation Map report page.

To review the benefits valuation maps entered in the system, run the Benefit Value Table report (WAC0003).


Loading Compensation DataUse the Data Loader to load compensation data from the ODS staging tables to the data warehousetables. Here is a summary of what happens when you load compensation data:



Compensation Type Mapping Tables Referenced Target Data WarehouseTables

Deductions WA_COMP_DED_MAP. Anydeductions not mapped are notloaded.

WA_COMP_HST_F00 with rows ofemployee-level compensation costand value data.

Benefits WA_COMP_DED_MAP andWA_BEN_VALU_TBL tables. Anybenefit plans not mapped are notloaded.

WA_COMP_HST_F00 with rows ofemployee-level compensation costand value data, as annualized costs.

WA_BEN_HST_F00 with benefitsenrollment data.

Note. If, while loadingWA_COMP_HST_F00, the systemfinds an enrollment row for anemployee on one of the enrollmenttables (Health Benefit, Life AddBenefit, Disability Benefit, FSA,Savings, and so on), then the systemlooks to the BEN_VALU_TBL tablefor a corresponding compensationcode. If a row exists for mappingthat benefit to a compensation codeon the BEN_VALU_TBL table,then the mapped values associatedwith that benefit are inserted for thatemployee on COMP_HST_F00,with a Compensation Source of B.

Earnings WA_COMP_ERN_MAP. Anyearnings not mapped are not loaded.


Pay Item Names WA_COMP_PIN_MAP. Any payitems not mapped are not loaded.


Loading Data Warehouse TablesThis section provides an overview of the data warehouse tables of primary concern toPeopleSoft Workforce Analytics applications and discusses:

• Benefit enrollment data.

• Competency data.

• Staffing data.

• Job data.



• Employee compensation history data.

Overview of Data Warehouse TablesYou use the Data Loader to load internal source data from the ODS staging tables into your data warehousetables. The following table provides a brief overview of the data warehouse tables loaded by Data Loader thatare of primary concern to PeopleSoft Workforce Analytics applications. Important points about some of thefact (*_F00) tables are presented both in this table and in this section following the table. Important pointsabout some of the dimension (*_D00) and reference (*_R00) tables are discussed in the next section after that.

This table is not a comprehensive list of all of the data warehouse tables in PeopleSoft Enterprise Warehouse.See PeopleSoft Customer Connection for the most complete, up-to-date documentation of the data warehousetables. Where there is a discrepancy the report delivered on Customer Connection takes precedence.

See PeopleSoft Customer Connection for suggested table loading sequences.

Once you’ve run Data Loader, you must run the Currency Conversion job if, and only if, the data youimported with Data Loader contains currency amounts, which require standardization into a base currencyequivalent. Currency Conversion must be run as a standalone job within a jobstream.

Data Warehouse Table Name Source TablesUsage within Workforce

Analytics

ABS_CLASS_D00 ABS_CLASS_TBL

ABS_CODE_D00 ABS_CODE_TBL Workforce Insight

ABS_HIST_F00 ABSENCE_HIST Workforce Insight

ABS_TYPE_D00 ABS_TYPE_TBL Workforce Insight

ABSV_ACCR_F00 ABSV_ACCRUAL Workforce Insight

ABSV_ADDL_D00 ABSV_ADDL_TBL

ABSV_PLAN_D00 ABSV_PLAN_TBL Workforce Insight

ABSV_RATE_D00 ABSV_RATE_TBL

ABSV_REQ_D00 ABS_REQUEST

ACCOMP_D00 ACCOMP_TBL

ACCT_CD_D00 ACCT_CD_TBL Workforce Rewards




Analytics

ACMPLISHMNT_F00 ACCOMPLISHMENTS

APP_ACP_D00 APP_ACCOMPS

APP_CMP_D00 APP_COMPS

APP_DIS_D00 APP_DISABILITY Workforce Insight

APP_EMAIL_D00 APP_EMAIL_ADDRS

APPLICANT_D00 • APPLICANT_DATA

• PERS_APPL_INF0

• APPL_DATA_EFFDT

Workforce Insight

BUDGET_BU_D00 BUDGET_BUS_UNIT

BUDGET_PER_D00 BUDGET_PERIOD

CAN_ERN_BAL_F00 CAN_ERN_BALANCE

CM_CLUSTER_D00 CM_CLUSTER_TBL

CM_EVALUATN_D00 CM_EVALUATIONS

CM_ROLE_ACC_D00 CM_ROLE_ACCOMPS

CM_ROLE_D00 CM_ROLE

CM_ROLECOMP_D00 CM_ROLE_COMPS

CM_RTNGDSCR_D00 CM_RATING_DESCR

CM_TYPE_D00 CM_TYPE_TBL

CMCLUSTRACP_D00 CM_TYPE_TBL

CMCLUSTRCMP_D00 CM_CLUSTER_COMP




Analytics

CMPETNCYTYP_D00 COMPETENCY_TYPS

COMPANY_D00 COMPANY_TBL

COMPETENCY_D00 COMPETENCY_TBL Workforce Insight

Workforce Planning

COMPRT_GRP2_D00 COMPRT_GRP_TBL2

COURSE_COMP_D00 COURSE_COMPS Workforce Insight

COURSE_D00 HR_COURSE_TBL Workforce Insight

CRSE_SESSN_D00 CRSE_SESSN_TBL Workforce Insight

CRSESESINST_D00 CRSE_SESS_INSTR

CRSESESNCST_D00 CRSE_SESSN_COST

DED_FREQ_D00 DEDUCTION_FREQ

DEPARTMENT_TBL DEPT_TBL Workforce Insight

Workforce Planning

Workforce Rewards

DEPT_BUDDED_D00 DEPT_BUDGET_DED

DEPT_BUDERN_D00 DEPT_BUDGET_ERN Workforce Rewards

DISABILITY_D00 DISABILITY

EARNINGS_BL_F00 EARNINGS_BAL

EMPL_REVW_F00 EP_APPR and EP_APPR_ROLE Workforce Insight

Workforce Rewards

EMPLOYEES_D00 EMPLOYEES




Analytics

EMPLOYMENT_D00 EMPLOYMENT

ESTAB_D00 ESTAB_TBL

JOB_EARNDST_D00 JOB_EARNS_DIST

JOB_F00 JOB Workforce Planning

Workforce Rewards

Workforce Insight

Workforce Scorecard

JOB_INTRADY_F00 JOB Workforce Insight

JOB_REQ_F00 JOB_REQUISITION

JOB_TASK_D00 JOB_TASK_TBL

JOBCD_CMPRT_D00 JOBCD_COMP_RATE

JOBCD_TRNPR_D00 JOBCD_TRN_PROG Workforce Rewards

JOBCD_TSKDF_D00 JOBCD_TASK_DEFN

JOBCODE_D00 JOBCODE_TBL Workforce Insight

Workforce Rewards

Workforce Scorecard

LEAVE_PLAN_D00 LEAVE_PLAN

LOCATION_D00 LOCATION_TBL Workforce Planning

Workforce Rewards

Workforce Insight

NID_TYPE_D00 NID_TYPE_TBL

PERS_DETAIL_D00 PERSONAL_PHONE Workforce Scorecard




Analytics

PERS_NAMES_D00 NAMES

PERS_NID_D00 PERS_NID (child of PERSON)

SETID derived from JOB_F00_ETL_VW

PERSONAL_D00 • PERSON

• PERS_DATA_EFFDT

• NAME

• ADDRESS

• CITIZENSHIP

• PERS_APPL_INF0

Workforce Insight

Workforce Scorecard

POSITION_D00 POSITION_DATA

POSN_APPLD_F00 POSN_APPLIEDFOR Workforce Insight

PRIORWRKEXP_D00 PRIORWORK_EXPER

REVW_FACTOR_D00 REVW_FACTOR_TBL

REVWRWRCMP_F00 EP_APPR and EP_APPR_ITEM

SAL_GRADE_D00 SAL_GRADE_TBL Workforce Rewards

Workforce Insight

Workforce Scorecard

SAL_MTRXPCT_D00 SAL_MATRIX_PCT

SAL_MTRXTBL_D00 SAL_MATRIX_TBL

SAL_PLAN_R00 SAL_PLAN_TBL Workforce Insight

Workforce Rewards

Workforce Scorecard

SAL_RATECD_D00 SAL_RATECD_TBL Workforce Rewards




Analytics

SAL_STEP_D00 SAL_STEP_TBL Workforce Rewards

SCHOOL_D00 SCHOOL_TBL

SCHOOL_EDUC_D00 SCHOOL_EDUCAT

SCHOOL_TYPE_D00 SCHOOL_TYPE_TBL

ST_GRANT_F00 ST_GRANT

STAFFING_F00 JOB_REQUISITION or JOB andPOSITION_DATA

Workforce Insight

Workforce Scorecard

STOCK_PLAN_D00 STOCK_PLAN_TBL

TIME_LABOR_F00 TL_PAYABLE_TIME andTL_TRC_TBL

Workforce Insight

Workforce Scorecard

TL_EMPL_D00 TL_EMPL_DATA

TRN_DMND_D00 TRN_DEMAND

TRN_DMNDDPT_D00 TRN_DEMAND_DEPT

VC_EE_VCOMP_D00 VC_EE_VCOMP_DTL

VC_PLAN_D00 VC_PLAN_TBL Workforce Rewards

VENDOR_PLCY_D00 VENDOR_POLICY

WA_ACMP_MAJ_F00 ACCOMPLISHMENTS Workforce Planning

WA_ACMPLISH_F00 ACCOMPLISHMENTS Workforce Planning




Analytics

WA_BEN_HST_F00 • HEALTH_BENEFIT

• LIFE_ADD_BEN

• DISABILITY_BEN

• FSA_BENEFIT

• SAVINGS_PLAN

• VACATION_BEN

• LEAVE_PLAN

• CAR_PLAN

• RTRMT_PLAN

• PENSION_PLAN

• JOB

• WA_COMP_DED_MAP

Workforce Insight

WA_CMPTN_EE_F00 • COMPETENCIES

• NVQ_UNITS_PROG

• CAREER_STRENGTH

• CAREER_WEAKNESS

• EP_APPR

• EP_APPR_ITEM

Workforce Insight

Workforce Scorecard




Analytics

WA_COMP_HST_F00 • PAY_EARNINGS

• PAY_OTH_EARNS

• PAY_CHECK

• PAY_DEDUCTION

• TOTAL_DED

• GP_RSLT_ERN_DED

• GP_PYE_PRC_STAT

• HEALTH_BENEFIT

• LIFE_ADD_BEN

• DISABILITY_BEN

• FSA_BENEFIT

• SAVINGS_PLAN

• VACATION_BEN

• LEAVE_PLAN

• CAR_PLAN

• RTRMNT_PLAN

• PENSION_PLAN

• WA_COMP_ERN_MAP

• WA_COMP_DED_MAP

• WA_BEN_VALU_TBL

Workforce Insight

Workforce Scorecard

WA_COMPTNCY_F00 • COMPETENCIES

• COMPETENCY_TBL

• EP_APPR

• EP_APPR_ITEM

• WA_RATING_MAP

Workforce Planning

WA_COVG_CD_R00 COVRG_CD_TBL

WA_DEP_BEN_D00 DEPENDENT_BENEF

WA_INJ_ILL_D00 INJURY_ILL and INCIDENT_DATA Workforce Insight

Workforce Scorecard

WA_RECR_EXP_F00 APP_EXPENSES Workforce Insight




Analytics

WA_RECR_OFR_F00 OFFER Workforce Insight

WA_REVWRTG_R00 REVW_RATING_TBL Workforce Insight

Workforce Scorecard

WA_ROLE_D00 • CM_ROLE

• JOBCODE_TBL

• POSITION_DATA

Workforce Planning

WA_ROLEACMP_D00 CM_ROLE and CM_ROLE_ACCOMPS

Workforce Planning

WA_ROLECMPT_D00 CM_ROLE and CM_ROLE_COMPS Workforce Planning

WA_ROLETASK_D00 CM_ROLE and CM_ROLE_COMPS Workforce Planning

WA_RTGMDL_R00 RATING_MDL_TBL Workforce Insight

WA_STD_LTR_R00 STANDRD_LTR_TBL

WA_TASK_D00 • CM_CLUSTER_TBL

• CM_ROLE

• JOB_FAMILY_TBL

• JOB_TASK_TBL

Workforce Planning

WA_TASKACMP_D00 • CM_CLUSTER_ACMP

• CM_CLUSTER_TBL

• CM_ROLE_ACCOMPS

Workforce Planning

WA_TASKCMPT_D00 CM_ROLE_COMPS andCM_CLUSTER_TBL

Workforce Planning

WA_TRN_HST_D00 TRAINING Workforce Insight




Analytics

WA_TRNCST_F00 • TRN_EEEQUIP_CST

• TRN_EEEXPN_COST

• TRN_EEFACIL_CST

• TRN_EEINST_COST

• TRN_EEPROV_COST

• TRN_EESAL_COST

• TRN_SSEXPN_COST

• JOB_F00_ETL_VW

Workforce Insight

Workforce Scorecard

WA_TRNSESSN_D00 CRSE_SESSN_COST

WRKS_CNCL_D00 WRKS_CNCL_LCL

Note. Only some, not all, of the fields in the HRMS tables are used in the data warehouse tables.If there is an apparent discrepancy between the information on the previous chart and on CustomerConnection, the information in Customer Connection takes precedence.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Loading Data into the OperationalData Store and the Data Warehouse”

Understanding Benefits Enrollment DataIn the Benefits Enrollment History table (WA_BEN_HST_F00) there is a field called the WABenefit Enrollment Source (WA_BENSOURCE). This field is an identifier, populated duringdata loading, that indicates the PeopleSoft HRMS source table the benefits enrollment data isfrom. There are ten possible valid values and corresponding tables:

WA Benefit Enrollment Source PeopleSoft HRMS Source Table

Health Benefits PS_HEALTH_BENEFIT

Pension Plan PS_PENSION_PLAN

Life ADD Ben PS_LIFE_ADD_BEN

Disability Ben PS_DISABILITY_BEN



WA Benefit Enrollment Source PeopleSoft HRMS Source Table

FSA Benefit PS_FSA_BENEFIT

Savings Plan PS_SAVINGS_PLAN

Vacation Benefit PS_VACATION_BEN

Leave Plan PS_LEAVE_PLAN

Car Plan PS_CAR_PLAN

Retirement Plan PS_RTRMNT_PLAN

Understanding Competency DataThe WA_CMPTN_EE_F00 table records employee-level competency data. It is used primarily inPeopleSoft HRMS Warehouse and PeopleSoft Workforce Scorecard. In this table the competency sourcefield (WA_CMSOURCE) identifies the source of the competency data for an employee. The field ispopulated during data loading. The sources are the PeopleSoft HRMS modules that use competencies:Plan Careers, Manage Competencies, and Performance Management. Valid values are Career Strength,Career Weakness, Competencies, NVQ Units Progression, and Performance Management.

The WA_CMPTNCY_F00 table records competency ratings for each employee, applicant or contractorevaluation. The sources are the PeopleSoft HRMS modules: Manage Competencies and PerformanceManagement. (Employee Appraisals). Only the “approved/official” rating from employee reviewis selected. It is used primarily in PeopleSoft Workforce Planning.

The following are the main competency related dimension and fact data warehousetables used by PeopleSoft Workforce Planning:

• WA_CMPTNCY_F00

• WA_ACMPLISH_F00

• WA_ACMP_MAJ_F00

• WA_TASK_D00

• WA_TASKCMPT_D00

• WA_TASK_ACMP_D00

• WA_ROLE_D00

• WA_ROLECMPT_D00

• WA_ROLEACMP_D00

• WA_ROLE_TASK_D00



Understanding Staffing DataDuring data loading the system imports data for the Staffing table (STAFFING_F00) fromtwo PeopleSoft HRMS tables. When the data comes from the JOB_REQUISITION table, thevalue for the PeopleSoft EPM field REQ_NEW_POS is copied over directly, as Y (yes) or N(no). When the data is imported from the POSITION_DATA table the PeopleSoft EPM fieldREQ_NEW_POS value is derived using the following mapping logic:

If the PeopleSoft HRMS table POSITION_DATA.ACTION_REASON field value is NEW, then the value forthe PeopleSoft EPM field REQ_NEW_POS is set to Y. Otherwise, the value for REQ_NEW_POS is set to N.

Note. This mapping logic is new as of PeopleSoft 8 SP3 Enterprise Performance Management. If your datawas imported using earlier functionality, reload your data for populating the STAFFING_F00 table.

Understanding Job DataBefore you run Data Loader to load the data warehouse table JOB_F00, you must havecompleted setup of online pages for the following tables:

• CURRENCY_CD_TBL

• FREQUENCY_TBL

• SETID_TBL

• WA_LOCN_MAP_DFN

• WA_ACTN_RSN_DFN

• BUS_UNIT_TBL_PF

• BUS_UNIT_SRC_PF

During data loading the system creates an additional row in JOB_F00 for employees that have a morerecent row in JOB_F00 with another business unit, to indicate that the employee is no longer activefor the first business unit. For example, if the system imports two rows of data for an employeewith the following business units, effective dates, and effective statuses:

CORP1, 1/1999, Active

CORP2, 2/2000, Active

then the system will insert a third row of data into JOB_F00 to indicate the employeeis no longer active for the first business unit:

CORP1, 2/2000, Inactive

Understanding the WA_VOLUNTARY_FLAG FieldThe ACTION, ACTION_REASON, and WA_VOLUNTARY_FLAG fields are in the JOB_F00 table.The WA_VOLUNTARY_FLAG is a PeopleSoft Workforce Analytics field you map online prior to dataloading. The mapping identifies whether each action and reason combination imported from PeopleSoftHRMS results in a voluntary termination, involuntary termination, or no termination.



Importing Effective-Sequenced Job ActionsDuring data loading the system imports the maximum effective sequence row, for each effective date fromthe PeopleSoft HRMS Job Data table, and places that row in JOB_F00. In contrast, the system loads alleffective-sequenced rows from the PeopleSoft HRMS Job Data table into JOB_INTRADY_F00.

Importing Review Rating Data to JOB_F00Normally during data loading the system populates the PeopleSoft EPM review rating field(JOB_F00.REVIEW_RATING) with PeopleSoft HRMS data. When data is imported into the JOB_F00table from the PeopleSoft HRMS Job Data table, the loading process checks that only valid values arepopulated for REVIEW_RATING, by comparing them with values in the lookup table WA_REVWRTG_R00.If there isn’t a corresponding value on the WA_REVWRTG_R00 table, then some rows of data thatyou might expect to see for that employee may not be imported. You must verify that all values for agiven REVIEW_RATING have a corresponding row on WA_REVWRTG_R00.

Streamlining JOB_F00 and Row-Level SecurityIf your implementation includes row-level security at the employee level, based on JOB_F00 andPERSONAL_D00, then first load the JOB_F00 and PERSONAL_D00 tables before setting up security.

Understanding Employee Compensation History DataThe PeopleSoft EPM compensation code field (WA_COMPCODE), on the Compensation Codetable (COMPCODE_D00) categorizes types of compensation. These codes are used to relatecompensation to nodes on the COMPCODE tree. Prior to data loading earnings, deductions,benefits plans, and pay item types from PeopleSoft HRMS tables are mapped to these compensationcodes using online pages. During data loading employee compensation history is imported intothe employee Compensation History table (WA_COMP_HST_F00).

Viewing and Editing Data in Dimension and Reference TablesThis section discusses how to:

• View and edit departments.

• Set up geography IDs.

• View and edit job codes and job code sets.

• View and edit personal information.

• View and edit position data.

• View and edit location data.

• View and edit salary grades and steps.

• Set up compensation codes.

• Set up industry codes.

• Set up financial codes.



• Set up unit codes.

• Define age, service, and other duration groups.

UnderstandingReview andEdit of Dimension andReferenceDataOnce you’ve run Data Loader, and data from the ODS staging tables is brought into the data warehousetables, you can use the error processing capabilities provided by the Data Loader to edit the data.

In addition to this, you can view and edit the data in certain data warehouse dimension and reference tables, atany time, using the pages in the Entprse Warehouse Dimensions, HRMS menu. The main point to rememberabout these pages is that their intended purpose is for you to monitor and perform slight edits on the data in thedata warehouse tables. Do not use them in the traditional, transactional sense to manually add rows of data tothe system. Many of the edits and checks built into the PeopleSoft HRMS system to ensure data integrity arenot present in the data warehouse tables. This means you could create data that would not be valid in the sourcesystem. The vast majority of the data in your data warehouse tables should be imported using the Data Loader.

There are several dozen dimension and reference table access pages in the Entprse Warehouse Dimensions,HRMS menu. The fields on these pages and in the underlying tables are mostly a mirror representationof, or a selection of, those in the PeopleSoft HRMS system. The pages themselves are fairly simple setuppages. For these reasons this documentation does not address these pages in any great detail, except to makenote of any important differences in how they are applied in PeopleSoft Workforce Analytics.

Pages Used to Access Dimension and Reference DataPage Name Object Name Navigation Usage

Department DEPARTMENT_TBL Entprse WarehouseDimensions, Common,Department

View and edit departments,which can be used forfinancial related accountingpurposes, or to provide anorganizational hierarchy foryour company.

Geography GEOGRAPHY_D00 Entrpse WarehouseDimensions, Common,Geography

Create geographyidentification codes, whichare geographical regions,which your locations rollup to.

Employment EMPLOYMENT_D00 Entprse WarehouseDimensions, HRMS,Employee and Job,Employment

View and edit an employee’semployment relatedmilestones and dates.

Applicant Information APPLICANT_1_D00 Entprse WarehouseDimensions, HRMS,Applicants, ApplicantInformation

View and edit an applicant’sname information.

Applicant Accomplishment APP_ACP_D00 Entprse WarehouseDimensions, HRMS,Applicants, ApplicantAccomplishment

View and edit informationabout an applicant’saccomplishments.



Page Name Object Name Navigation UsageApplicant Competencies APP_CMP_D00 Entprse Warehouse

Dimensions, HRMS,Applicants, ApplicantCompetencies

View and edit informationabout an applicant’scompetencies.

Applicant Email APP_EMAIL_D00 Entprse WarehouseDimensions, HRMS,Applicants, Applicants Email

View and edit informationabout an applicant’s emailaddress.

Job Code JOBCODE_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Job Code

View and edit data inJOBCODE_D00, andprovide the details for theJOBCODE tree.

Job Code Set WA_JOBCDSET_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, JobCode Set

Create the nodes that definethe structure of yourJOBCODE tree. You mustenter this information foreach node using this page. Ajob code set is a collection ofrelated job codes.

Job Earnings Distribution JOB_EARNDST_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, JobEarnings Distribution

View and edit how anemployee’s earnings shouldbe posted for accountingpurposes. For example,earnings can be posted to ajob code, a department, alocation, a general ledgeraccount, a position, ordistributed among severalcategories.

Job Tasks JOB_TASK_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Job Tasks

View and edit job codesfor which there are sets ofjob tasks.

Job Code Comp Rate (jobcode compensation rate)

JOBCD_CMPRT_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Job CodeComp Rate

View and edit compensationrates, which apply to onlythose employees sharing thesame job code. All rates thatare to be used by payrollprocessing at the job codelevel must first be defined inthis table.

Job Code Task Definition JOBCD_TSKDF_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Job CodeTask Definition

View and edit the tasksassociated with a job code.This record is subordinate toJOB_TASK_D00.



Page Name Object Name Navigation UsagePersonal Data PERSONAL_D00 Entprse Warehouse

Dimensions, HRMS,Employee and Job, PersonalData

View and edit personalinformation aboutyour employees in thePERSONAL_D00table. Rows from thePeopleSoft HRMS tablesPS_PERSONAL_DATA,PS_EMPLOYMENT andPS_EMPLOYEES areintended to be brought in tothe PERSONAL_D00 tablewith Data Loader.

Personal Names PERS_NAMES_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, PersonalNames

View and edit employee’spersonal name information,such as suffixes, prefixes,legal names, preferrednames, and so on.

Personal Data National ID PERS_NID_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, PersonalData National ID

View and edit employee’sNational ID information.

National ID Type NID_TYPE_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, NationalID Type

View and edit NationalID types.

Dependent Data WA_DEP_BEN_D00 Entprse WarehouseDimensions, HRMS,Benefits, Dependent Data

View and edit informationabout dependents andbeneficiaries.

Position POSITION_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Position

View and edit position data,if Position Management isimplemented in the sourcePeopleSoft HRMS system.

Prior Work Experience 1 PRIORWRKEXP_1_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, PriorWork Experience

View and edit data aboutan employee’s prior jobexperience.

Prior Work Experience 2 PRIORWRKEXP_2_D00 Select the Prior Work Exp 2tab.

View and edit additional dataabout an employee’s priorjob experiences; includingpay grade, pay plan, full orpart time status, regular ortemporary status, positiontype, and so forth.

Salary Grade Data WA_SAL_GRADE_D00 Entprse WarehouseDimensions, HRMS, Salary,Grade

View and edit a salary gradestructure for your salaryadministration plan.

Salary Increase Matrix SAL_MTRXTBL_D00 Entprse WarehouseDimensions, HRMS, Salary,Increase Matrix

View and edit the identifierfor each set of salaryincrease guidelines, thename of the matrix, and whatrating scale is used for theranges.



Page Name Object Name Navigation UsageSalary Matrix Percent SAL_MTRXPCT_D00 Entprse Warehouse

Dimensions, HRMS, Salary,Matrix Percent

View and edit the acceptablepercentage ranges for salaryincreases.

Salary Rate Code SAL_RATECD_D00 Entprse WarehouseDimensions, HRMS, Salary,Rate Code

View and edit compensationrate code information.

Variable Comp Plan(variable compensationplan)

VC_PLAN_D00 Entprse WarehouseDimensions, HRMS,Compensation, VariableComp Plan

View and edit data fora variable compensationplan that is not likely tochange over the life of theplan. Plan types can bediscretionary bonus, goalsharing (performance-basedmonetary plan),non-monetary (basedon units), profit sharing(monetary), stock plans (fivetypes), and other.

Employee Variable Comp(employee variablecompensation )

VC_EE_VCOMP_D00 Entprse WarehouseDimensions, HRMS,Compensation, EmployeeVariable Comp

View and edit the detailinformation regardingan employee’s variablecompensation record.Includes, for each effectivedate, the informationregarding any and all plansthe employee is enrolled,including the target formulaand eligibility as of date.

Stock Plan STOCK_PLAN_D00 Entprse WarehouseDimensions, HRMS,Benefits, Stock Plan

View and edit stock plan andtype information.

Training History WA_TRN_HST_D00 Entprse WarehouseDimensions, HRMS,Training, Training History

View and edit employeetraining history alongwith related course costinformation.

Training Session WA_TRNSESSN_D00 Entprse WarehouseDimensions, HRMS,Training, Training Session

View and edit trainingsession expenses.

Training Course 1 COURSE_1_D00 Entprse WarehouseDimensions, HRMS,Training, Courses

View and edit trainingcourse information.

Training Course 2 COURSE_2_D00 Select the Course 2 tab. View and edit additionaltraining course details.

Course Session CRSE_SESSION_D00 Entprse WarehouseDimensions, HRMS,Training, Course Session

View and edit sessioninformation for trainingcourses.

Course Instructors CRSESESINST_D00 Entprse WarehouseDimensions, HRMS,Training, Course Instructors

View and edit informationabout instructors for trainingcourse sessions.



Page Name Object Name Navigation UsageCourse Session Cost CRSESESNCST_D00 Entprse Warehouse

Dimensions, HRMS,Training, Course SessionCost

View and edit costinformation for trainingcourse sessions.

Training Program Job Code JOBCD_TRNPR_D00 Entprse WarehouseDimensions, HRMS,Training, Training ProgramJob Codes

View and edit informationabout training programassignments for jobs in yourorganization.

Course Goal— Competency COURSE_COMP_D00 Entprse WarehouseDimensions, HRMS,Training, CourseGoal-Competency

View and edit thecompetencies, and theirassociated proficiency levelsthat are associated with aparticular training course.

General Demand byDepartment

TRN_DMNDDPT_D00 Entprse WarehouseDimensions, HRMS,Training, General Demandby Department

View and edit the numberof employees to be trainedin a specific course or setof courses for a particulardepartment during aspecified budget period.

Account Codes ACCT_CD_D00 Entprse WarehouseDimensions, HRMS,Common, Account Codes

View and edit the accountcode information fromgeneral ledger and payroll.

Compensation Code WA_COMPCODE_D00 Entprse WarehouseDimensions, HRMS,Compensation,Compensation Code

Create nodes for theCOMPCODE tree. Also usethis page to view and editcompensation code dataafter you have run ETLsto import compensationdata from your PeopleSoftHRMS system.

Standard Letter Code WA_STD_LTR_R00 Entprse WarehouseDimensions, HRMS,Common, Standard LetterCode

View and edit standard codesfor identifying business formletters.

Coverage Code WA_COVG_CD_R00 Entprse WarehouseDimensions, HRMS,Benefits, Coverage Code

View and edit benefitscoverage codes.

Establishment Codes ESTAB_D00 Entprse WarehouseDimensions, HRMS,Common, EstablishmentCodes

View and edit informationabout the regulatoryreporting establishments foryour organization.

Financial Code WA_FINCODE_D00 Entprse WarehouseDimensions, HRMS,Common, Financial Code

Create the nodes for theFINCODE tree.

Industry Code WA_INDUSTRY_D00 Entprse WarehouseDimensions, HRMS,Common, Industry Code

Create the nodes for theINDUSTRY tree.

Rate Code Group Code COMPRT_GRP2_D00 Entprse WarehouseDimensions, HRMS,Compensation, Rate CodeGroup Code

View and edit rate codes fora rate code group.



Page Name Object Name Navigation UsageUnit Code WA_UNITCODE_D00 Entprse Warehouse

Dimensions, HRMS,Common, Unit Code

Create the nodes for theUNITCODE tree.

School Codes SCHOOL_D00 Entprse WarehouseDimensions, HRMS,Competencies, School

View and edit codes toschools, colleges, anduniversities.

School Type SCHOOL_TYPE_D00 Entprse WarehouseDimensions, HRMS,Competencies, School Type

View and edit codes forschool types.

School Education SCHOOL_EDUC_D00 Entprse WarehouseDimensions, HRMS,Competencies, SchoolEducation

View and edit informationabout education achievedby an employee.

Accomplishment Data ACCOMP_D00 Entprse WarehouseDimensions, HRMS,Competencies,Accomplishments

View and edit theaccomplishments that youremployees, applicants orcontractors may achieve.Accomplishments arelanguages, degrees, licenses,certificates, honors, awards,professional memberships,tests, or NVQs (NationalVocational Qualifications).

Cluster CompntAccomplishment(cluster competencyaccomplishments)

CMCLUSTRACP_D00 Entprse WarehouseDimensions, HRMS,Competencies, ClusterCompnt Accomplishment

View and edit theaccomplishments of acompetency cluster, and theimportance of each.

Review Factor REVW_FACTOR_D00 Entprse WarehouseDimensions, HRMS, Salary,Review Factor

View and edit weightingfactors associated withrating scales.

Review Rating WA_REVWRTG_R00 Entprse WarehouseDimensions, HRMS, Salary,Review Rating

View and edit rating models,consisting of review ratings.

Review Scale WA_REVWSCL_R00 Entprse WarehouseDimensions, HRMS, Salary,Review Scale

View and edit review ratingscales used in rating groupsof employees.

Competencies COMPETENCY_D00 Entprse WarehouseDimensions, HRMS,Competencies,Competencies

View and edit competenciesorganized by the followinggeneral categories: ability,knowledge, skill, salaryplanning, and NVQ unit.

Competency Type CM_TYPE_D00 Entprse WarehouseDimensions, HRMS,Competencies, CompetencyTypes

View and edit codes forcompetency types.

Competency of ComptcyTypes (competency ofcompetency types)

CMPETNCYTYP_D00 Entprse WarehouseDimensions, HRMS,Competencies, Competencyof Competency Types

View and edit theassignment of competenciesto competency types.



Page Name Object Name Navigation UsageCompetency Cluster CM_CLUSTER_D00 Entprse Warehouse

Dimensions, HRMS,Competencies, CompetencyCluster

View and edit codes forcompetency clusters.

Competency of CompetencyCluster

CMCLUSTRCMP_D00 Entprse WarehouseDimensions, HRMS,Competencies, Competencyof Comptncy Cluster

View and edit theassignment of competenciesto competency clusters.

Person CompetencyEvaluation

CM_EVALUATN_D00 Entprse WarehouseDimensions, HRMS,Competencies, PersonCompetency Evaluation

View and edit employeeevaluation identificationcodes.

Competency RatingDescription

CM_RTNGDSCR_D00 Entprse WarehouseDimensions, HRMS,Competencies, CompetencyRating Description

View and edit thedescriptions of eachcompetency at a particularproficiency (review rating).

Competency of Role CM_ROLECOMP_D00 Entprse WarehouseDimensions, HRMS,Competencies, RoleCompetency

View and edit thecompetencies or competencyclusters that comprise a role(position, job code, job task,or job family).

Vacation Plan ABSV_PLAN_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Vacation Plan

View and edit informationabout vacation benefit plansfor employees in variousgroups; including the accrualfrequency, maximumbalance and maximumcarryover.

Vacation Bonus Entitlement ABSV_ADDL_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Vacation Bonus Entitlement

View and edit service bonusvalues, or extra vacationfor a given year. This datais used by the PeopleSoftHRMS system to calculatethe amount of vacation timean employee can have.

Vacation Request ABSV_REQ_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Vacation Request

View and edit vacationrequest data for any periodthat has had accrualsrun. PeopleSoft HRMSWarehouse Insight will onlyprocess or evaluate approvedvs. non-approved requests.

Vacation Service RateValues

ABSV_RATE_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Vacation Service Rate Values

View and edit informationabout the number of days ofvacation accrued per yearor per month for a givenvacation plan. Needed tocalculate amount of vacationtime an employee can have.

Leave Benefit Enrollment LEAVE_PLAN_D00 Entprse WarehouseDimensions, HRMS,Benefits, Leave BenefitEnrollments

View and edit informationregarding employee’s choiceof leave plans.



Page Name Object Name Navigation UsageAbsence Code ABS_CODE_D00 Entprse Warehouse

Dimensions, HRMS,Vacations/Absences,Absence Code

View and edit absence codesfor your absence types.

Absence Type ABS_TYPE_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Absence Type

View and edit the type ofabsences employees cantake.

Absence Class ABS_CLASS_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Absence Class

View and edit the codes forabsence classes.

Employee Time Profile TL_EMPL_D00 Entprse WarehouseDimensions, HRMS,Vacations/Absences,Employee TimeProfileManageWarehouse,Maintain HRMSDimensions, Setup

View and edit basicinformation from thePeopleSoft Time and Labortime reporter.

Health and Safety Data WA_INJ_ILL_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Healthand Safety Data

View and edit employee’shealth and safety incidentdata.

Applicant Disability APP_DIS_D00 Entprse WarehouseDimensions, HRMS,Applicants, ApplicantDisability

View and edit informationon an applicant’s disability.

Disability DISABILITY_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, Disability

View and edit informationabout an employee’sdisability.

CM Role CM_ROLE_D00 Entprse WarehouseDimensions, HRMS,Competencies, Role

View and edit roles(positions, job codes, jobtasks, and job families).

CM Role Accomplishment CM_ROLE_ACC_D00 Entprse WarehouseDimensions, HRMS,Competencies, RoleAccomplishment

View and edit theaccomplishments thatcomprise a role (position,job code, job task, or jobfamily).

Budget Period Bus Unit BUDGET_BU_D00 Entprse WarehouseDimensions, HRMS,Common, Budget PeriodBus Unit

View and edit budgetperiod and business unitinformation.

Department Budget DedDist (department budgetdeductions distribution)

DEPT_BUDDED_D00 Entprse WarehouseDimensions, HRMS,Compensation, DepartmentBudget Ded Dist

View and edit the deductionsdistributions to accountsfor each of the specifieddepartment budget levels.

Department Budget EarnDist (department budgetearnings distribution

DEPT_BUDERN_D00 Entprse WarehouseDimensions, HRMS,Compensation, DepartmentBudget Earn Dist

View and edit the earningsdistributions to accountsfor each of the specifieddepartment budget levels.



Page Name Object Name Navigation UsageVendor Address VENDOR_ADDR_D00 Entprse Warehouse

Dimensions, HRMS,Training, Vendor Address

View and edit vendoraddresses, such as forvendors used in purchasingor training .

Vendor Policy Detail VENDOR_PLCY_D00 Entprse WarehouseDimensions, HRMS,Training, Vendor PolicyDetail

View and edit vendor orprovider policy details.

Deduction Frequency DED_FREQ_D00 Entprse WarehouseDimensions, HRMS,Compensation, DeductionFrequency

View and edit informationthat defines how often permonth a deduction is takenfor each pay frequency.

Duration Group Definition WA_DUR_GRP_DFN Entprse WarehouseDimensions, HRMS,Common, Duration GroupDefinition

Define duration groupsbased upon time duration(such as age, service, job,grade, and so on) for usein PeopleSoft HRMSWarehouse Insight analysistemplates.

Works Council WRKS_CNCL_D00 Entprse WarehouseDimensions, HRMS,Employee and Job, WorksCouncil

View and edit data forGerman works councils.

Viewing and Editing DepartmentsLoad PeopleSoft HRMS departments into the Department table (DEPARTMENT_TBL). Use them to createa financial-related Department tree to provide a hierarchy for departmental accounts. Also use the samedepartments to create an Organization (Department) tree to provide a hierarchy for all departments in yourorganization. A secondary purpose of the Organization tree is in creating row-level group security.

See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Up theOrganization (Department) Tree, page 19

Setting Up Geography IDsThe Geography dimension in PeopleSoft Workforce Analytics helps provide a hierarchical structureto your organization’s locations, using the Geography tree. Prior to loading locations fromPeopleSoft HRMS, use the Geography page (GEOGRAPHY_D00) to create geographical regions,which logically group together locations in your organization. Map locations to the geographicalregions using the Location Mapping page (WA_LOCN_MAP_DFN).


Chapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Viewingand Editing Location Data , page 60



Viewing and Editing Job Codes and Job Code SetsThe job code dimension in PeopleSoft Workforce Analytics uses the Job Code tree to provide a hierarchicalstructure to your organizations jobs. Job code sets are the nodes of the tree. They are logical groupings ofjob codes that you create using the Job Code Set page (JOBCDSET_D00). Job codes provide the details ofthe tree. Load job codes into the Job Code table (JOBCODE_D00), prior to building the tree.

Understanding Compensation Values Associated with Job CodesIf you are using an external market compensation survey to compare your organization’ssalaries with industry averages, the salary midpoint for the equivalent job code goes in thesurvey salary field. These are usually annualized values.

Note. When you import market compensation survey data into the PeopleSoft Enterprise Warehouse tables,the data loading process annualizes the compensation values. All salary survey data processed in the DefineMarket Compensation module of PeopleSoft Workforce Rewards is standardized to annual values.

See AlsoChapter 3, “Importing Internal Source Data to DataWarehouse Tables,” Setting Up the JOBCODE Tree, page 19

Viewing and Editing Personal InformationWhen you have loaded personal data from PeopleSoft HRMS into the PERSONAL_D00 table, you canuse the pages in the Personal Data component to view and edit the information.

Running Application Engine PER099 Prior to Importing Personal DataRemember, the PS_EMPLOYEES table is used in PeopleSoft HRMS to improve the efficiency of reportprocessing. The table is not updated dynamically by the PeopleSoft HRMS system; you must run theApplication Engine process PER099 (Refresh Employees Table) to update the PS_EMPLOYEES table. Toensure you are loading the most up-to-date information into the PeopleSoft Enterprise Warehouse tables, run theApplication Engine process PER099 immediately prior to importing personal data into the ODS staging tables.

Clarifying Row-level Security Issues About Personal DataThe PERSONAL_D00 and JOB_F00 tables are intended to be populated with data using the ETLprocess. If you enter new rows of employee data manually using the Personal Data page, and thereis group security in effect based on JOB_D00_VW (which is a view of JOB_F00) then you maynot see this data displayed on pages having row-level security based on employees. Two additionalsteps are required to view the data. You must first add a corresponding row of data to JOB_F00, andthen you must rerun the PF_SECURITY process for security to be enabled.

If, after using the data migration process to load data into PERSONAL_D00, the data does not display inthe online pages such as Personal Data, then the problem may have to do with implementation of group(row-level) security based on employees. The search record for PERSONAL_D00 is PERSONAL_SRCH.PERSONAL_SRCH is a join of PERSONAL_D00 and PF_SY_CLASS_OBJ. PF_SY_CLASS_OBJis populated by running the PF_SECURITY process. If, in your implementation, row-level security isenabled at the employee level, then the security groups are likely built referencing JOB_F00 (or a viewof JOB_F00). Both JOB_F00 and PERSONAL_D00 must both be populated with corresponding rows ofdata, and then the PF_SECURITY process must be run, before the data displays online.



Note. If your implementation includes row-level security at the employee level, based on JOB_F00 andPERSONAL_D00, then first load the JOB_F00 and PERSONAL_D00 tables before setting up security.

Importing Personal NamesDuring data migration the system populates the personal name field in the PERSONAL_D00 tablewith the data from the name field in the PeopleSoft HRMS Personal Data table. You can view and editthis data using the Personal Data component. During data loading the system populates the personalname field with the name of the individual from the PeopleSoft HRMS Names table.

The last name, first name, and middle name fields separate the person’s personal name into its components.These fields are also populated by PeopleSoft HRMS source fields during data loading.

The last name search and first name search fields are populated from the PeopleSoft HRMSsource fields during data loading. These are versions of the names which have no punctuation(for example, apostrophes are removed) and are in all capital letters. These versions of thenames are used by the PeopleSoft HRMS system as search values.


Viewing and Editing Position DataThe POSITION_D00 page and underlying table are provided for those sites that use thePosition Management feature of PeopleSoft HRMS. Use of this page and table is not necessaryif Position Management is not used at your site.

The position dimension in PeopleSoft Workforce Analytics uses the Position tree to providea hierarchical structure for positions within an organization. Position data is loaded into thePosition table (POSITION_D00). Position data and job requisition data are aggregated into asingle structure, centering on the Staffing table (STAFFING_F00).

See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Up the Position Tree, page 20

Viewing and Editing Location DataYou import locations into the Location table, and map them to geography IDs. The geography dimension usesthe GEOGRAPHY tree to provide a hierarchical structure to your locations and geographical regions.

During initial setup first determine what geographical regions you want to map your PeopleSoftHRMS locations to. Enter the geography IDs for those regions using the Geography page.Create a GEOGRAPHY tree using these geography IDs. Then map your locations to thegeography IDs using the Location Mapping (WA_LOCN_MAP_DFN) page. If you have doneall of this correctly, then during the Data Loader process, for each location imported to theLOCATION_D00 table, the value from the WA_LOCN_MAP_DFN.GEOGRAPHY_ID field isused to populate the LOCATION_D00.GEOGRAPHY.ID field.




Chapter 3, “Importing Internal Source Data to DataWarehouse Tables,” Setting Up the Geography Tree , page 18

Viewing and Editing Salary Grades and StepsOnce you have loaded the salary administration plan, salary grade, and salary step information fromPeopleSoft HRMS into the data warehouse tables, you can use the Salary Grades component to viewand edit the grades and steps that make up salary administration plans.

Understanding Salary Value CalculationsOnce you have imported salary data then you can review the data, and correct it manually, using thesepages. When you change a value using one of the online pages, the PeopleSoft Enterprise Warehousesystem does not recalculate any of the other related numbers automatically.

Remember, in the PeopleSoft HRMS system the salary terms are defined as follows:

Monthly The annual rate divided by the pay months per year.

Hourly The monthly rate prorated to 12 pay periods, divided by 52 weeksin the year, divided by 40 hours per week.

Midpoint The maximum plus the minimum divided by two.

Note. In the PeopleSoft Workforce Rewards Define Base Pay Structure module the system defines andcalculates midpoints as the maximum plus the minimum divided by two. In your implementation ofPeopleSoft HRMS you may have chosen to define compensation midpoints differently. If this is thecase, then keep this difference in mind when comparing compensation midpoints from your importeddata with compensation midpoints created using PeopleSoft Workforce Rewards.

Setting Up Compensation CodesThe compensation dimension in PeopleSoft Workforce Analytics uses the CompensationCode tree to provide a hierarchical structure to the earnings, deductions, benefits values, andpay items loaded from the PeopleSoft HRMS system.

You create compensation codes using the Compensation Code page (COMPCODE_D00). Thenyou map the earnings, deductions, benefits values, and pay items from PeopleSoft HRMS tothese compensation codes using a series of mapping pages.

Understanding Compensation ClassesCompensation classes are from the translate table. The valid values correspond to thedelivered nodes on the model COMPCODE tree.

Understanding the Account FieldThe account field is used for tracking financial data. Prompt values are from the GL_ACCOUNT_TBL. Youload values for the GL_ACCOUNT_TBL during the setup for PeopleSoft Enterprise Warehouse.




Chapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Upthe Compensation Code Tree, page 17

Setting Up Industry CodesThe industry code dimension is used primarily in the PeopleSoft Workforce Rewards Market Compensationmodule, to deal with loading external survey data. You use the Industry Dimension page to enter industrycodes that define the industry an organization is in. These codes categorize data from external survey sources,and validate comparison to data for your organization. Industry codes are the nodes on the Industry tree.

See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Upthe INDUSTRY Tree, page 19

Setting Up Financial CodesThe financial code dimension is used primarily in the PeopleSoft Workforce Rewards MarketCompensation module, to deal with loading external survey data. You use the FinCode Dimensionpage to enter financial codes that define the relative financial size of your organization. Thesecodes categorize data from external survey sources, and validate comparison to data for yourorganization. Financial codes are the nodes on the FINCODE tree.

The from value and to value fields indicate the value range for the approximate sizeof an organization’s financial worth.

See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Up the FINCODE Tree, page 18

Setting Up Unit CodesThe unit code dimension is used primarily in the PeopleSoft Workforce Rewards Market Compensationmodule, to deal with loading external survey data. You use the Unit Code page to enter unit codesthat define the relative size of an organization (using an alternate criteria other than a financialone). These codes categorize data from external survey sources, and validate comparison to datafor your organization. Unit codes are the nodes on the UNITCODE tree.

Note. The purpose of the unit code dimension is to provide an alternate means of measuring the relative size ofcompanies participating in external surveys, as opposed to using the relative financial size of the companies. Atypical unit of measure would be the number of employees in a company. The concept of unit is generic enoughthat the units can be other measures besides number of employees. For example, in the hospital industry theunit could be the number of hospital beds. Or in the hotel industry the unit could be the number of rooms.

The from value and to value fields indicate the value range for the approximate size ofan organization based on this unit of measure.



See AlsoChapter 3, “Importing Internal Source Data to Data Warehouse Tables,” Setting Upthe UNITCODE Tree, page 20

Defining Age, Service and Other Duration GroupsPeopleSoft HRMS Warehouse Insight analysis templates use durations to provide a time dimension toPeopleSoft Workforce Analytics data. Since durations are not part of the PeopleSoft HRMS system,you define them online using the Duration Group page (WA_AGE_SERV_DFN).

You can define duration groups based on Age, Department, Grade, Job, Pay Change, Promotion, and Service.If the group is Service you can map your service group ID to a benchmark survey service ID.

You can specify whether you want to measure your group duration in Days, Months, or Years.This defines the frequency for the values you enter in the group low value and group high valuefields. For example, if you select a frequency of Months for the group type Promotion, then thesystem measures the duration since a person’s last promotion in months. If you select Days thenthe duration since their last promotion is measured in days, and so on.

The group low value and group high value fields enable you to define the range of values fora duration group. If you create a group ID such as No Service or No Age, enter a value of 0(zero) in both the group high value and group low value fields.




CHAPTER 4

Importing External Survey Data to DataWarehouse Tables

This chapter discusses how to:

• Review the operator defaults page.

• Review sources of external survey data.

• Review external survey tables and ETL setup.

• Understand survey data ETL batches.

• Import external survey data with the setup ETL batch.

• View and edit the survey Data Warehouse tables.

• Complete survey mapping definitions.

• Review survey mapping definitions online.

• Import external survey data with the load ETL batch.

• Import external survey data with the ongoing ETL batch.

• Generate external survey data reports.

• Review the external survey flat file definitions.

Understanding External Survey DataExternal survey data is workforce-related data you obtain from third-party survey providers (such as marketcompensation data from compensation surveys). This chapter discusses how to import external survey datafrom flat files, into data warehouse tables, using the Informatica PowerMart ETL tool.

Reviewing the Operator Defaults PageThe Operator Defaults page is accessed by first selecting Define Business Rules EPM, GeneralOptions. The purpose of the page is to enter default values for search keys (business unit,scenario ID, year) used to access the PeopleSoft Workforce Analytics pagelets through a portal.This functionality is documented in PeopleSoft Enterprise Performance Management PortalPeopleBook, in the chapter entitled “Workforce Analytics Pagelets.”


Importing External Survey Data to Data Warehouse Tables Chapter 4

Reviewing Sources of External Survey DataPeopleSoft Workforce Analytics applications are designed to integrate data fromthree main types of external surveys:

1. Compensation surveys, containing market compensation data, which you use in themodules within PeopleSoft Workforce Rewards.

2. Benchmark surveys, containing workforce-related metrics, which you use in the analysistemplates in PeopleSoft HRMS Warehouse Workforce Insight.

3. Employee surveys, containing employee satisfaction and exit survey results, which you usein the modules within PeopleSoft Workforce Rewards.

Note. You have the option of importing, by ETL, external data for PeopleSoft Workforce Planning; such asemployee competency data, competency dictionaries, skills inventories, standard proficiency ratings, jobprofiles, and so on. To do this you will have to create your own flat files and ETL maps. Our data model willsupport this, and you will have access to Informatica PowerMart to create the maps and run the ETLs.

Page Used to Access eSurvey ProvidersPage Name Object Name Navigation Usage

Survey Providers WAIC_SURVEY_PROV Workforce Analytics,Workforce Survey Setup,Review Survey Providers

Access selected workforcesurvey providers, includingtheir provider logos,descriptions of theirservices, and URLs linkingto their Websites.

Accessing Survey ProvidersAccess the Survey Providers page.


Chapter 4 Importing External Survey Data to Data Warehouse Tables

Survey Providers page

You can click either the survey provider icons or the associated links to access the provider’s URL and Website.

Reviewing External Survey Tables and ETL SetupThis section discusses:

• Data warehouse tables to store the survey data.

• File definitions for formatting the survey data prior to import.

• ETL (extract, transform, and load) maps linking data in the file definitions to the data warehouse tables.

• Informatica PowerMart ETL technology.

Understanding External Survey Tables and ETL SetupThe external survey data setup and import process is similar for each type of survey data. We deliver thetools to enable you to import external survey data into PeopleSoft Enterprise Warehouse.

We’ve worked closely with third-party survey providers to develop the file definitions, ETL maps anddata warehouse tables delivered with PeopleSoft Workforce Analytics. We designed the delivered filedefinitions, ETL maps and data warehouse tables to work efficiently and seamlessly together.



Reviewing the Data Warehouse Tables and ETL MapsBefore you begin, first take some time to plan your approach and evaluate your external survey data needs.

Use the PeopleTools Application Designer to review the data warehouse tables deliveredwith PeopleSoft Enterprise Warehouse. Determine how you want to structure yoursystem to best fit the needs of your organization.

Evaluate the ETL maps delivered in the Informatica PowerMart repository files that youuse to import external survey data to the data warehouse tables, and determine if they areproperly configured to meet the needs of your organization.

Warning! Any changes you make to our delivered data warehouse tables have the potential to affectApplication Engine processes, Insight analysis templates, and PeopleCode processing throughoutthe system. Evaluate and execute these types of changes very carefully.

Here is a table summarizing the delivered ETL maps and data warehouse tables:



Folder

Mapping

Source

Table

TargetTable

EXTERNALWFA

AUTHOR

AUTHOR

WA_AUTHOR_R00

EXTERNALWFA

BENCHMARK_SURVEY

WA_BENCHMARK_TMP

WA_BENCHMRK_F00

EXTERNALWFA

DIMENSION_COMP

DIMENSION

WA_SUR_COMP_D00

EXTERNALWFA

DIMENSION_FIN

DIMENSION

WA_SUR_FIN_D00

EXTERNALWFA

DIMENSION_GEO

DIMENSION

WA_SUR_GEO_D00

EXTERNALWFA

DIMENSION_IND

DIMENSION

WA_SUR_IND_D00

EXTERNALWFA

DIMENSION_JOB

DIMENSION

WA_SUR_JOB_D00

EXTERNALWFA

DIMENSION_UNIT

DIMENSION

WA_SUR_UNIT_D00

EXTERNALWFA

EMPLOYEE_SURVEY_BUS_UNIT

WA_EESURVEY_TMP

WA_EESURVEY_F00

EXTERNALWFA

EMPLOYEE_SURVEY_DEPTID

WA_EESURVEY_TMP

WA_EESURVEY_F00

EXTERNALWFA

EMPLOYEE_SURVEY_EMPLID

WA_EESURVEY_TMP

WA_EESURVEY_F00

EXTERNALWFA

EMPLOYEE_SURVEY_JOBCODE

WA_EESURVEY_TMP

WA_EESURVEY_F00

EXTERNALWFA

EMPLOYEE_SURVEY_LOCATION

WA_EESURVEY_TMP

WA_EESURVEY_F00

EXTERNALWFA

SALARY_SURVEY

WA_SURVALUE

WA_SURVALUE_F00

EXTERNALWFA

SURVEY_INSTANCE

SURVEY_INSTANCE

WA_SURVEY_R00

EXTERNALWFA

WA_BENCHMRK_FIN_MAP_DFN

WA_BENCHMRK_TMP

WA_FIN_MAP_DFN


Importing External Survey Data to Data Warehouse Tables Chapter 4Folder

Mapping

Source

Table

TargetTable

EXTERNALWFA

WA_BENCHMRK_FIN_MAP_DFN

WA_SURVEY_R00

WA_FIN_MAP_DFN

EXTERNALWFA

WA_BENCHMRK_GEO_MAP_DFN

WA_BENCHMRK_TMP

WA_GEO_MAP_DFN

EXTERNALWFA

WA_BENCHMRK_GEO_MAP_DFN

WA_SURVEY_R00

WA_GEO_MAP_DFN

EXTERNALWFA

WA_BENCHMRK_IND_MAP_DFN

WA_BENCHMRK_TMP

WA_IND_MAP_DFN

EXTERNALWFA

WA_BENCHMRK_IND_MAP_DFN

WA_SURVEY_R00

WA_IND_MAP_DFN

EXTERNALWFA

WA_BENCHMRK_TMP

BENCHMARK_SURVEY

WA_BENCHMARK_TMP

EXTERNALWFA

WA-BENCHMRK_UNIT_MAP_DFN

WA_BENCHMRK_TMP

WA_UNIT_MAP_DFN

EXTERNALWFA

WA-BENCHMRK_UNIT_MAP_DFN

WA_SURVEY_R00

WA_UNIT_MAP_DFN

EXTERNALWFA

WA_COMP_MAP_DFN

WA_SURVALUE_TMP

WA_COMP_MAP_DFN

EXTERNALWFA

WA_EESURVEY_TMP

EMPLOYEE_SURVEY

WA_EESURVEY_TMP

EXTERNALWFA

WA_FIN_MAP_DFN

WA_SURVALUE_TMP

WA_FIN_MAP_DFN

EXTERNALWFA

WA_GEO_MAP_DFN

WA_SURVALUE_TMP

WA_GEO_MAP_DFN

EXTERNALWFA

WA_IND_MAP_DFN

WA_SURVALUE_TMP

WA_IND_MAP_DFN

EXTERNALWFA

WA_JOB_MAP_DFN

WA_SURVALUE_TMP

WA_JOB_MAP_DFN

EXTERNALWFA

WA_SURVALUE_TMP

SALARY_SURVEY

WA_SURVALU_TMP

EXTERNALWFA

WA_UNIT_MAP_DFN

WA_SURVALUE_TMP

WA_UNIT_MAP_DFN




Reviewing the Survey File DefinitionsPrior to ETL processing, you must ensure your external survey data is in a standard flat file format toensure detailed and accurate mapping to the data warehouse tables. In PeopleSoft Workforce Analytics,we deliver standard file definitions for the following external survey elements:

1. Author file (common to all types of surveys).

2. Dimension file (common to all types of surveys).

3. Survey Instance file (common to all types of surveys).

4. Compensation Survey file.

5. Benchmark Survey file.

6. Employee Survey file.

The standard file definitions are provided in the tables at the end of this chapter, in the sectionUnderstanding the External Survey Flat File Definitions.

To use the ETL maps we deliver, you must work with your survey provider to ensure you receive yoursurvey data in files meeting these definitions. This includes ensuring the proper ordering of the fields,and using a comma-delimited, *.csv or *.txt, flat file format. A *.csv format file is recommendedand preferred. Arrange to receive separate survey data flat files for each of the elements in theprevious list. For compensation surveys arrange to obtain author, survey instance, dimensions, andcompensation survey files from the provider. For benchmark surveys arrange to obtain author, surveyinstance, dimensions, and benchmark survey files from the provider. For employee surveys, arrangeto obtain author, survey instance, and employee survey files from the provider.

If the external survey data you receive is from a provider whose data doesn’t fit thesefile definitions, then you have several options:

• Work with your current survey provider to make sure you receive the survey data ina format that meets these file definitions.

• Work with a different survey provider who delivers the survey data in a format that meets these file definitions.

• Manipulate the survey data you receive from your provider to get it into a formatthat meets these file definitions.

• Use our file definitions and ETL maps as templates, and modify them to suit your needs.



Understanding the Survey Data ETL BatchesWhen you import external survey data, the source data is in the form of flat files you create fromthe data you receive from your survey provider. The target tables are the data warehouse tables inPeopleSoft Enterprise Warehouse. You import the data in two separate survey ETL batches, referredto as setup and load batches. For ongoing updates to survey data there is a third ETL batch, which werefer to as the ongoing batch. The naming of these ETL batches is as follows:

Market CompensationSurveys

Employee Surveys Benchmark Metrics Surveys

Setup 1 Setup 2 Setup 3

Load 1 Load 2 Load 3

Ongoing 1 Ongoing 2 Ongoing 3

Importing External Survey Data with the Setup ETL BatchFor each type of survey source the setup ETL batch imports the author, survey instance, and surveydimensions data, and imports some data to the dimension map definitions:

1. The Author session populates the WA_AUTHOR_R00 table.

2. The Survey Dimension session populates the WA_SUR_COMP_D00, WA_SUR_FIN_D00,WA_SUR_GEO_D00, WA_SUR_IND_D00, WA_SUR_JOB_D00, and WA_SUR_UNIT_D00 tables.

3. The Survey Instance session populates the WA_SURVEY_R00 table.

4. The Temporary Table session populates the WA_SURVALU_TMP, WA_BENCHMRK_TMP,and WA_EESURVEY_TMP tables.

5. The Compensation Survey and Benchmark Survey sessions populate some data inthe mapping definition tables. For example:

a. The Compensation Survey 1 session populates the WA_COMP_MAP_DFN,WA_FIN_MAP_DFN, WA_GEO_MAP_DFN, WA_IND_MAP_DFN, WA_JOB_MAP_DFN, and WA_UNIT_MAP_DFN tables.

b. The Benchmark Survey 1 session populates the WA_FIN_MAP_DFN, WA_GEO_MAP_DFN,WA_IND_MAP_DFN, and WA_UNIT_MAP_DFN tables.

Viewing and Editing the Survey Data Warehouse TablesOnce you’ve run the first setup batch of ETLs you can view and edit the data in the data warehouse tables online.



Note. The following table lists pages used to view and edit survey data in the data warehouse tables.Since these pages are basic setup pages, and the fields for the underlying tables are shown in the flatfile definitions at the end of this chapter, we won’t discuss these pages in any detail here.

Pages Used to View and Edit Survey DataPage Name Object Name Navigation Usage

Survey Author WA_AUTHOR_R00 Workforce Analytics,Workforce Survey Setup,Setup Survey Author

View and edit dataabout external surveyproviders, and their addressinformation.

Survey Instance WA_SURVEY_R00 Workforce Analytics,Workforce Survey Setup,Setup Survey Instance

View and edit publicationinformation about a survey.

Survey Job Code WA_SUR_JOB_D00 Workforce Analytics,Workforce Survey Setup,Setup Survey Job Code

View and edit the job codesused in external surveys.

Survey Compensation Code WA_SUR_COMP_D00 Workforce Analytics,Workforce Survey Setup,Setup Survey CompensationCode

View and edit externalsurvey compensation codes.

Survey Geography ID WA_SUR_GEO_D00 Workforce Analytics,Workforce Survey Setup,Setup Survey Geography ID

View and edit externalsurvey geographical regions.

Survey Industry ID WA_SUR_IND_D00 Workforce Analytics,Workforce Survey Setup,Setup Survey Industry ID

View and edit externalsurvey industry categories.

Survey Financial Code WA_SUR_FIN_D00 Workforce Analytics,Workforce Survey Setup,Setup Survey Financial Code

View and edit data aboutthe financial size (basedon factors such as sales orrevenue) of companiesparticipating in externalsurveys.

Survey Unit Code WA_SUR_UNIT_D00 Workforce Analytics,Workforce Survey Setup,Setup Survey Unit Code

View and edit data, otherthan financial data, thatmeasures the relative size ofcompanies participating inexternal surveys.

See AlsoChapter 4, “Importing External Survey Data to Data Warehouse Tables,” UnderstandingExternal Survey Data, page 65

Completing Survey Mapping DefinitionsThis section discusses how to:



• Set up workforce trees.

• Map survey data

Understanding Survey Mapping DefinitionsWhen you run the setup batch of ETLs the system partially populates the following EnterpriseWarehouse mapping tables: WA_COMP_MAP_DFN, WA_FIN_MAP_DFN, WA_GEO_MAP_DFN,WA_IND_MAP_DFN, WA_JOB_MAP_DFN, and WA_UNIT_MAP_DFN. Your next task is to completethe data mapping definitions using the access pages for these tables. The mapping definitions are needed toprepare for your second set of ETLs. In this step you map survey data to previously defined PeopleSoftEnterprise Warehouse dimensions (JOB, COMPENSATION, GEOGRAPHY, INDUSTRY, FINANCIAL andUNIT) and trees (JOBCODE, COMPCODE, GEOGRAPHY, INDUSTRY, FINCODE and UNITCODE).

Common FieldsTo access the survey mapping pages you specify a SetID and Survey Instance. Depending upon the page,you also specify one of the following: a Survey Job Code, Survey Compensation Code, Survey GeographyID, Survey Industry Code, Survey Financial Code, or Survey Unit Code. The values for these fields arein the system for you to use as prompts once you have run the Setup batch of ETLs.

In the Survey box the system displays the Survey Author ID associated with this SurveyInstance. Click the Description button to access the Mapping Notes page, where you canenter a long description or more detailed mapping notes.

In the Workforce Analytics box click the View Tree button to access the Tree Viewer page,where you can specify the name of the tree node or detail to which you want to map your surveyvalue. The system also displays the name of the current selection for the appropriate defaultTree. You indicated this tree on the Workforce Trees page.



Pages Used to Map Survey DataPage Name Object Name Navigation Usage

Workforce Trees WA_MAP_TREE_TBL Workforce Analytics,Workforce Analytic Setup,SetupWorkforce Trees

Specify the SetID, EffectiveDate, and names of the treesyou want the system to use.In PeopleSoft WorkforceRewards (external surveys,market compensation,Insight analysis templates),PeopleSoft WorkforcePlanning, and PeopleSoftHRMSWarehouseWorkforce Insight, many ofthe main dimensions gettheir hierarchical structurefrom trees.

Job CodeMap WA_JOB_MAP_DFN Workforce Analytics,Workforce Survey Setup,Map Job Code

Use this page to map surveyjob codes to nodes ontheWorkforce AnalyticsJOBCODE tree.

Mapping Notes WA_DESCR_SPNL Access this page from theseother pages: Job CodeMap,Compensation CodeMap,Geography IDMap, IndustryMap, Financial Code Map,Unit Code Map.

Access the MappingNotes page by clicking theDescription button.

Enter a long description ormore detailed mapping notesfor the following primarypages: Job CodeMap,Compensation Code Map,Geography IDMap, IndustryCodeMap, Financial CodeMap, or Unit Code Map,whichever is applicable.

Compensation Code Map WA_COMP_MAP_DFN Workforce Analytics,Workforce Survey Setup,Map Compensation Code

Map survey compensationcodes to nodes on theWorkforce AnalyticsCOMPCODE tree.

Geography IDMap WA_GEO_MAP_DFN Workforce Analytics,Workforce Survey Setup,Map Geography ID

Map survey geography ID’sto nodes on theWorkforceAnalytics GEOGRAPHYtree.

Industry IDMap WA_IND_MAP_DFN Workforce Analytics,Workforce Survey Setup,Map Industry ID

Map survey industry ID’s tonodes on theWorkforceAnalytics INDUSTRY tree.

Financial Code Map WA_FIN_MAP_DFN Workforce Analytics,Workforce Survey Setup,Map Financial Code

Map survey financial codesto nodes on theWorkforceAnalytics FINCODE tree.

Unit Code Map WA_UNIT_MAP_DFN Workforce Analytics,Workforce Survey Setup,Map Unit Code

Map survey unit codes tonodes on theWorkforceAnalytics UNITCODE tree.

Setting Up Workforce TreesAccess the Workforce Trees page by entering a SetID.



Workforce Trees setup page

Note. This page has SetID as a key. When you specify a default tree on this page, for use with a WorkforceRewards application, the tree mapping value must remain constant. That is, the tree mapping must remainunchanged, from the start of your market compensation survey import, and all the way through youruse of the survey data in the PeopleSoft Workforce Rewards business process modules.

Job Code Tree,Compensation CodeTree, Geography Tree,Organization Tree, AccountTree, Position Tree, andBusiness Unit Tree

These trees are used in one or more of the PeopleSoft Workforce Analyticsapplications. Prompt values are from the PF_METATREE_TBL table. Thisensures that only those trees that have tree metadata are available to map.

Industry Tree, FinancialCode Tree, and UnitCode Tree

These trees are used in the PeopleSoft Workforce Rewards application.Prompt values are from the WA_INDTREE_VW, WA_FINCODE_VWand WA_UNITCODE_VW tables, respectively.

Competency Tree This tree is used in the PeopleSoft Workforce Planning application. Promptvalues are from the WA_CMPT_TREE_VW table.

Mapping Job CodesAccess the Job Code Map page by entering a SetID, Survey Instance, and Survey Job Code.



Survey Job Code Map setup page

In the Survey box the system displays the Description, FLSA Status, and Total Pointsfrom the WA_SUR_JOB_VW table.

In the Workforce Analytics box, select the Job Code Set to which you want to map the Survey Job Code. JobCode Set prompts from the WA_JBCDSET_VW table. A Job Code Set is a group of related job codes,belonging to the same node on the JOBCODE tree. A leaf or detail on the tree is an individual job code.

Mapping Survey Compensation CodesAccess the Compensation CodeMap page by entering a SetID, Survey Instance, and SurveyCompensation Code.

In the Survey box the system displays the Description from the WA_SUR_COMP_VW table.

In the Workforce Analytics box, select the Compensation Code to which you want to map the SurveyCompensation Code. Compensation Code prompts from the COMPCODE_VW table.

Mapping Geography IDsAccess the Geography ID Map page by entering a SetID, Survey Instance, and Survey Geography ID.

In the Survey box the system displays the Description from the WA_SUR_GEO_VW table.

In the Workforce Analytics box, select the Geography ID to which you want to map the SurveyGeography ID. Geography ID prompts from the GEOGRAPHY_VW table.

Mapping Industry CodesAccess the Industry Code Map page by entering a SetID, Survey Instance, and Survey Industry Code.

In the Survey box the system displays the Description from the WA_SUR_IND_VW table.

In the Workforce Analytics box, select the Industry ID to which you want to map the SurveyIndustry ID. Industry ID prompts from the WA_INDUSTRY_VW table.



Mapping Financial CodesAccess the Financial Code Map page by entering a SetID, Survey Instance, and Survey Financial Code.

In the Survey box the system displays the Description, From Value and To Valuefrom the WA_SUR_FIN_VW table.

In the Workforce Analytics box, select the Financial Code to which you want to map the SurveyFinancial Code. Financial Code prompts from the WA_FINCODE_VW table. When you Tab throughthe field the system displays the associated From Value and To Value.

Mapping Unit CodesAccess the Unit Code Map page by entering a SetID, Survey Instance, and Survey Unit Code.

In the Survey box the system displays the Description, From Value and To Valuefrom the WA_SUR_UNIT_VW table.

In the Workforce Analytics box, select the Unit Code to which you want to map the Survey UnitCode. Unit Code prompts from the WA_UNITCODE_VW table. When you Tab through thefield the system displays the associated From Value and To Value.

Reviewing Survey Mapping Definitions OnlineOnce you’ve entered your survey mapping definitions, you can view the survey mappingdefinitions at any time, using the following pages.



Pages Used to Review Survey Mapping Definitions OnlinePage Name Object Name Navigation Usage

Job CodeMap inquiry WA_SURMAP1_VW Workforce Analytics,Workforce Survey Setup,Review Job CodeMap

Review job code mappingdefinitions online.

Compensation Code Mapinquiry

WA_SURMAP2_VW Workforce Analytics,Workforce Survey Setup,Review CompensationCode Map

Review compensation codemapping definitions online.

Geography IDMap inquiry WA_SURMAP3_VW Workforce Analytics,Workforce Survey Setup,Review Geography IDMap

Review geography IDmapping definitions online.

Industry CodeMap inquiry WA_SURMAP4_VW Workforce Analytics,Workforce Survey Setup,Review Industry CodeMap

Review industry codemapping definitions online.

Financial Code Map inquiry WA_SURMAP5_VW Workforce Analytics,Workforce Survey Setup,Review Financial Code Map

Review financial codemapping definitions online.

Unit Code Map inquiry WA_SURMAP6_VW Workforce Analytics,Workforce Survey Setup,Review Unit Code Map

Review unit code mappingdefinitions online.

Importing External Survey Data with the Load ETL BatchOnce you’ve run the first set of external survey data ETLs, and then completed the mapping definitionpages in the Workforce Analytics, Workforce Surveys Setup menu, you’re ready to run your secondbatch of external survey data ETLs. We refer to this batch as the Load ETLs. You can think ofthis ETL batch as a process that matches dimension data with your data warehouse tables, andthen populates one of the three following Workforce Analytics Enterprise Warehouse fact tables:WA_SURVALUE_F00, WA_BENCHMRK_F00, or WA_EESURVEY_F00.

Note. Market compensation survey data from third-party survey providers may not be annualized.The Define Market Compensation module of PeopleSoft Workforce Rewards requires annualizedcompensation values. Compensation values from market surveys are annualized by the InformaticaETL tool as they are imported into the WA_SURVALUE_F00 table.


ETL mapping files in your Informatica PowerMart repository



Importing External Survey Data with the Ongoing ETL BatchAs you work with the PeopleSoft Workforce Analytics applications you may need to update your survey dataoccasionally. If the author and dimension data for the new survey have not changed from the previous survey,but the survey values have changed, then you can import this new information using the Ongoing batch ETLs.

If the author and dimension data has changed form the previous batch, then you need to run theSetup and Load batches again, instead of using the Ongoing batch.


ETL mapping files in your Informatica PowerMart repository

Generating External Survey Data ReportsOnce you’ve completed the batches of ETL sessions needed to import external surveydata into your data warehouse tables, you may want to review the data and mappings.To do this you use the following Crystal reports.




Pages Used to Generate External Survey Data ReportsPage Name Object Name Navigation Usage

Compensation SurveyData report

RUN_RWA_0020 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, CompensationSurvey Data

Run the CompensationSurvey Data Crystal report(WAC0020).

Benchmark Data Recordreport

RUN_RWA_0021 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Benchmark SurveyData

Run the Benchmark DataCrystal report (WAC0021).

Unit Code Map report RUN_RWA_0022 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Unit Code Map

Run the Unit Code MapCrystal report (WAC0022).

Compensation Code Mapreport

RUN_RWA_0023 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, CompensationCode Map

Run the CompensationCodeMap Crystal report(WAC0023).

Geography IDMap report RUN_RWA_0024 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Geography IDMap

Run the Geography IDMapCrystal report (WAC0024).

Industry CodeMap report RUN_RWA_0025 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Industry CodeMap

Run the Industry CodeMapCrystal report (WAC0025).

Job CodeMap report RUN_RWA_0026 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Job CodeMap

Run the Job CodeMapCrystal report (WAC0026).

Financial Code Map report RUN_RWA_0027 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Financial Code Map

Run the Financial Code MapCrystal report (WAC0027).

Employee Survey report RUN_RWA_0035 Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Employee SurveyData

Run the Employee SurveyData Map Crystal report(WAC0035).

Reviewing the External Survey Flat File DefinitionsThis section discusses how to:

• Review the author file definition.

• Review the dimension file definition.



• Review the survey instance file definition.

• Review the compensation survey file definition.

• Review the benchmark survey file definition.

• Review the employee survey file definition.

• Review valid values for selected field in the file definitions.

Understanding External Flat File DefinitionsIn this section, we present the external survey flat file definitions you use to work with your surveyproviders. Work with your providers to ensure the survey data you receive from them fits the formatspecified in these file definitions. At the end of this section, we also provide lists of the valid valuesfor selected fields in the file definitions that must use specified valid values.

Note. Wherever fields in the file definitions are designated as optional, we recommend you enter data inthose fields. If you don’t enter data in the optional fields, the system gives you error messages when yourun the ETL sessions, and data is not populated in those fields in the data warehouse tables.

Reviewing the Author File DefinitionThe following table contains the Author flat file definition.

Note. The Author file is needed when you have new author identification information. In otherwords, it is only needed when the survey provider data is new or has changed.

Field Name Field Type /Length / Format

ValidValues

Requiredor

Optional

Target PeopleSoft EnterpriseWarehouse Tables

WA_AUTHOR_ID Character / 10 R WA_AUTHOR_R00.WA_AUTHOR_ID

EFFDT Date / 8 /MMDDYYYY

R WA_AUTHOR_R00.EFFDT

EFF_STATUS Character / 1 Yes R WA_AUTHOR_R00.EFF_STATUS

ADDRESS1 Character / 35 R WA_AUTHOR_R00.WA_ADDR_SBR

ADDRESS2 Character / 35 O WA_AUTHOR_R00.WA_ADDR_SBR



CITY Character / 30 R WA_AUTHOR_R00.WA_ADDR_SBR



Field Name Field Type /Length / Format

ValidValues

Requiredor

Optional


COUNTRY Character / 3 R WA_AUTHOR_R00.WA_ADDR_SBR

COUNTRY_CODE

Character / 3 Yes R WA_AUTHOR_R00.BUS_PHONE_SBR

DESCR Character / 30 R WA_AUTHOR_R00.DESCR

DESCRLONG Long / 100 O WA_AUTHOR_R00.DESCRLONG

EXTENSION Character / 6 O WA_AUTHOR_R00.BUS_PHONE_SBR

FAX Character/ 24 O WA_AUTHOR_R00.BUS_PHONE_SBR

PHONE Character / 24 R WA_AUTHOR_R00.BUS_PHONE_SBR

POSTAL Character / 12 R WA_AUTHOR_R00.WA_ADDR_SBR

STATE Character / 6 R WA_AUTHOR_R00.WA_ADDR_SBR

The following example shows a single row of sample data, in comma delimited format,to assist you in creating your author file:

Example row of Author file data in flat file format

Reviewing the Dimension File DefinitionThe following table contains the Dimension flat file definition. With respect to the lasttwo columns, please note the following:

• If WA_SUR_DIM_TYPE = C, then the target record is WA_SUR_COMP_D00.

• If WA_SUR_DIM_TYPE = F, then the target record is WA_SUR_FIN_D00.

• If WA_SUR_DIM_TYPE = G, then the target record is WA_SUR_GEO_D00.

• If WA_SUR_DIM_TYPE = I, then the target record is WA_SUR_IND_D00.

• If WA_SUR_DIM_TYPE = J, then the target record is WA_SUR_JOB_D00.

• If WA_SUR_DIM_TYPE = U, then the target record is WA_SUR_UNIT_D00.



Note. The Dimension file is needed when you have a new or changed dimension information. TheWA_AUTHOR_ID in the Dimension file must be a valid author identification in the Author file definition.

Field Name Field Type/ Length /Format

Valid Values Requiredor

Optional

TargetPeopleSoftEnterpriseWarehouseTables

Comments

WA_AUTHOR_ID

Character / 10 R Target record isWA_AUTHOR_ID

WA_SUR_DIM_TYPE

Character / 1 Yes R Target record is*_CD

The “*“ symbolcould be G forGeography ID, Jfor Job Code, F forFinancial Code, andso on.

WA_SUR_CODE

Character / 10 R None Driver for TargetRecord ETLmapping. Theseare the actualGeography,Compensation, JobCodes, dependingupon theWA_SUR_DIM_TYPE.


R Target record isEFFDT

EFF_STATUS Character / 1 Yes R Target record isEFF_STATUS

JOB_TYPE Character / 1 Yes R Target record isFLSA_STATUS

Required onlywhen type ’J’

WA_POINTS Number / 3.0 R Target record isWA_POINTS


WA_FROM_VALUE

Number / 15.0 R Target record isWA_FROM_VALUE

Required onlywhen type ’F’ ortype ’U’



Field Name Field Type/ Length /Format

Valid Values Requiredor

Optional

TargetPeopleSoftEnterpriseWarehouseTables

Comments

WA_TO_VALUE

Number / 15.0 R Target record isWA_TO_VALUE

Required onlywhen type ’F’ ortype ’U’

DESCR Character / 30 R Target record isDESCR

DESCRLONG Long / 100 R Target record isDESCRLONG


The following example shows six rows of sample data, in comma delimited format, toassist you in creating your Dimension file:

Example rows of Dimension file data in flat file format

Reviewing the Survey Instance File DefinitionThe following table contains the Survey Instance flat file definition.

Note. The Survey Instance file is required for a new survey instance with new survey data. TheWA_AUTHOR_ID in this file must be a valid author identification in the Author file definition.


Importing External Survey Data to Data Warehouse Tables Chapter 4FieldName

FieldType/Length/

Format

Valid

Values

Required

orOptional

TargetPeopleSoftEnterpriseWarehouse

Tables

WA_SURVEY_ID

Character/10

RWA_SURVEY_R00.WA_SURVEY_ID

EFFDT

Date/8/MMDDYYYY

RWA_SURVEY_R00.DESCR

EFF_STATUS

Character/1

Yes

RWA_SURVEY_R00.EFF_STATUS

WA_AUTHOR_ID

Character/10

RWA_SURVEY_R00.WA_AUTHOR_ID

DESCR

Character/30

RWA_SURVEY_R00.DESCR

DESCRLONG

Long/100

NWA_SURVEY_R00.DESCRLONG

WA_PUBLICATION_DT

Date/8

RWA_SURVEY_R00.WA_PUBLICATION_ID

WA_SUR_CO_COUNT

Number/8.0

RWA_SURVEY_R00.WA_SUR_CO_COUNT

WA_SUR_EE_COUNT

Number/8.0

RWA_SURVEY_R00.WA_SUR_EE_COUNT

CURRENCY_CD

Character/3.0

Yes

RNote.Thisfieldisnotmappeddirectlytothe

WA_SURVEY_R00table.TheETLmappinguses

theCurrencyCodeasjoinconditiontodetermineall

oftheSetIDsfromtheWA_SET_CUR_VWwiththe

givenCurrencyCode.ThenthoseSetIDsareinserted

intheWA_SURVEY_R00table.



The following example shows a single row of sample data, in comma delimited format,to assist you in creating your Survey Instance file:

Example row of Survey Instance data in flat file format

Reviewing the Compensation Survey File DefinitionThe following table contains the Compensation Survey flat file definition.

Note. For the WA_SURVALUE_F00.WA_MEASURE_ID field, it is important you use thePeopleSoft EPM Measure IDs delivered with the system. To add more requires modificationsto the system. Also, note that the WA_SURVALUE_F00.WA_MEASURE_VAL field is forthe actual monetary value of the measure, not the ID code.


Importing External Survey Data to Data Warehouse Tables Chapter 4FieldName

FieldType

/Length/Format

Valid

Values

Requiredor

Optional?


Tables

WA_SURVEY_ID

Character/10

RWA_IND_MAP_DFN.WA_SURVEY_IDWA_FIN_MAP_

DFN.WA_SURVEY_IDWA_UNIT_MAP_DFN.WA_

SURVEY_IDWA_JOB_MAP_DFN.WA_SURVEY_ID

WA_COMP_MAP_DFN.WA_SURVEY_ID

WA_GEO_MAP_DFN.WA_SURVEY_IDWA_

SURVALUE_F00.WA_SURVEY_ID(ETL2)

WA_SUR_JOBCODE

Character/10

RWA_JOB_MAP_DFN.WA_SUR_JOBCODE

WA_SUR_COMPCODE

Character/10

RWA_COMP_MAP_DFN.WA_SUR_COMPCODE

WA_SUR_GEO_ID

Character/10

RWA_GEO_MAP_DFN.WA_SUR_GEO_ID

WA_SUR_IND_ID

Character/10

RWA_IND_MAP_DFN.WA_SUR_IND_ID

WA_SUR_FINCODE

Character/10

RWA_FIN_MAP_DFN.WA_SUR_FINCODE

WA_SUR_UNITCODE

Character/10

RWA_UNIT_MAP_DFN.WA_SUR_UNITCODE

EFFDT

Date/8/

MMDDYYYY

RWA_SURVALUE_F00.EFFDT

COMP_FREQUENCY

Character/1

Yes

RWA_SURVALUE_F00.COMP_FREQUENCY

WA_MEASURE_ID

Character/3

Yes

RWA_SURVALUE_F00.WA_MEASURE_ID

WA_MEASURE_VAL

Number/15.6

RWA_SURVALUE_F00.WA_MEASURE_VAL

CURRENCY_CD

Character/3

Yes

RWA_SURVALUE_F00.CURRENCY_CD

WA_UNITS

Character/1

Yes

RETLusestodeterminewhethervalueconversionisrequired.



FieldName

FieldType

/Length/Format

Valid

Values

Requiredor

Optional?


Tables

WA_SAMPLE_CO_

COUNT

Number/8.0

RWA_SURVALUE_F00.WA_SAMPLE_CO_COUNT

WA_SAMPLE_EE_

COUNT

Number/8.0

RWA_SURVALUE_F00.WA_SAMPLE_EE_COUNT



The following example shows six rows of sample data, in comma delimited format, toassist you in creating your Compensation Survey file:

Example rows of Compensation Survey data in flat file format

Reviewing the Benchmark Survey File DefinitionThe following table contains the Benchmark Survey flat file definition.

Note. For the WA_BENCHMRK_F00.PF_METRIC_ID field, it is important you use the PeopleSoft EPMmeasure IDs delivered with the system. To add more requires modifications to the system. Also, note that theWA_BENCHMRK_F00.WA_MEASURE_VAL field is for the actual value of the metric, not the ID code.



FieldName

FieldType/Len./

Format

Valid

Value

Required

orOptional

ETL


Tables

WA_SURVEY_ID

Character/10

R1,2

WA_IND_MAP_DFN.WA_SURVEY_ID

WA_FIN_MAP_DFN.WA_SURVEY_ID

WA_UNIT_MAP_DFN.WA_SURVEY_ID

WA_GEO_MAP_DFN.WA_SURVEY_ID

WA_BENCHMRK_F00.WA_SURVEY_ID(ETL2)

WA_SUR_GEO_ID

Character/10

R1

WA_GEO_MAP_DFN.WA_SUR_GEO_ID

WA_SUR_IND_ID

Character/10

R1

WA_IND_MAP_DFN.WA_SUR_IND_ID

WA_SUR_FINCODE

Character/10

R1

WA_FIN_MAP_DFN.WA_SUR_FINCODE

WA_SUR_UNITCODE

Character/10

R1

WA_UNIT_MAP_DFN.WA_SUR_UNITCODE

EFFDT

Date/8/

MMDDYYYY

R2

WA_BENCHMRK_F00.EFFDT

PF_METRIC_ID

Character/3

Yes

R2

WA_BENCHMRK_F00.PF_METRIC_ID

WA_MEASURE_VAL

Number/15.6

R2

WA_BENCHMRK_F00.WA_MEASURE_VAL

CURRENCY_CD

Character/3

Yes

R2

WA_BENCHMRK_F00.CURRENCY_CD

WA_UNITS

Character/1

Yes

R2

ETLusestodeterminewhetherconversionofvalueis

required.

WA_SAMPLE_CO_COUNT

Number/8.0

R2

WA_BENCHMRK_F00.WA_SAMPLE_CO_COUNT

WA_SAMPLE_EE_COUNT

Number/8.0

R2

WA_BENCHMRK_F00.WA_SAMPLE_EE_COUNT



The following example shows six rows of sample data, in comma delimited format, toassist you in creating your Benchmark Survey file:

Example rows of Benchmark Survey data in flat file format

Reviewing the Employee Survey File DefinitionThe following table contains the Employee Survey flat file definition.

Field Name Field Type/ Length/Format

ValidValues

Requiredor

Optional


WA_SURVEY_ID Character /10

R WA_EESURVEY_F00.WA_SURVEY_ID


R WA_EESURVEY_F00.EFFDT

EFF_STATUS Character / 1 Yes R WA_EESURVEY_F00.EFF_STATUS

WA_RM_FACTOR_ID Character /10

R WA_EESURVEY_F00.WA_RM_FACTOR_ID

PF_OBJ_ID Character /20

R WA_EESURVEY_F00.PF_OBJ_ID

PF_OBJ_TYPE Character / 4 Yes R WA_EESURVEY_F00.PF_OBJ_TYPE

WA_FACTOR_WEIGHT

Number / 5.0 R WA_EESURVEY_F00.WA_FACTOR_WEIGHT

WA_SAMPLE_EE_COUNT

Number / 8.0 R WA_EESURVEY_F00.WA_SAMPLE_EE_COUNT



Reviewing the Valid Values for Selected Fields inthe File DefinitionsIn the following tables in this section, we provide lists of the valid values for selected fieldsin the file definitions that must use specified valid values.

Effective Status

EFF_STATUS Valid Values

A = Active

I = Inactive

Country Code

COUNTRY_CODE Valid Values

CAN = Canada

DEU = Germany

ESP = Spain

FRA = France

GBR = United Kingdom

IND = India

ITA = Italy

JPN = Japan

NLD = Netherlands

USA = United States



Survey Dimension Type

WA_SUR_DIM_TYPE Valid Values

C = Compensation

F = Financials

G = Geography

I = Industry

J = Job

U = Unit

Job Type

JOB_TYPE Valid Values

A= Administrative

E= Executive

M=Management

N= Nonexempt

O= Outside Salesperson

P= Professional

X= None

Currency Code

CURRENCY_CD Valid Values

CAD = Canadian Dollar

DEM = Deutsche Mark



CURRENCY_CD Valid Values

ESP = Spanish Peseta

FRF = French Franc

GBP = Pound Sterling

INR = Indian Rupee

ITL = Italian Lira

JPY = Yen

NLG = Netherlands Guilder

USD = US Dollar

Compensation Frequency

COMP_FREQUENCY Valid Values

A= Annual

B= Biweekly

D= Daily

H= Hourly

M=Monthly

S= Semimonthly

W=Weekly

Note. PeopleSoft HRMS Warehouse Workforce Insight analysis templates, as delivered, are set upto use compensation frequency values of Annual only. Modification is needed if you want youranalysis templates to use any other compensation frequency values.



Units

WA_UNITS Valid Values

1= Ones

2= Hundreds

3= Thousands

4= 10 Thousands

5= 100 Thousands

6=Millions

7= 10Millions

8= 100 Millions

9= Billions

Object Type

PF_OBJ_TYPE Valid Values

1000 = Employee

2000 = Department

2100 = Business Unit

9000 = Job Code



Measure ID and Metric ID Codes

WA_MEASURE_ID /PF_METRIC_ID Valid Values

Description Survey Type

001 Y-Intercept- Natural Compensation Survey

002 Slope- Natural Compensation Survey

003 Standard Error Compensation Survey

004 R-Squared Compensation Survey

005 Actual 10th Percentile Amount Compensation Survey











016 Actual Average Amount Compensation Survey

017 Actual 10th Percentile Percent Compensation Survey















028 Actual Average Percent Compensation Survey

029 Actual % of Eligible Employees Compensation Survey

030 Target 10th Percentile Amount Compensation Survey















041 Target Average Amount Compensation Survey

042 Target 10th Percentile Percent Compensation Survey











053 Target Average Percent Compensation Survey

054 Target % of Eligible Employees Compensation Survey

055 Y-Intercept- Common Compensation Survey

056 Slope- Common Compensation Survey





057 R Compensation Survey

058 Standard Error- Logarithmic Compensation Survey

100 Productivity Factor Benchmark Survey

101 Efficiency Factor Benchmark Survey

102 Effectiveness Factor Benchmark Survey

103 Employee Compensation ROI Benchmark Survey

104 Workforce Compensation ROI Benchmark Survey

105 EmployeeWorkforce ROI Benchmark Survey

106 Contingent Workforce ROI Benchmark Survey

107 Total Compensation Revenue Ratio Benchmark Survey

108 Cash Compensation Revenue Ratio Benchmark Survey

109 Benefits Revenue Ratio Benchmark Survey

110 Total Compensation Expenses Ratio Benchmark Survey

111 Cash Compensation Expenses Ratio Benchmark Survey

112 Benefits Expenses Ratio Benchmark Survey

113 Executive Ratio Benchmark Survey

114 Supervisory Ratio Benchmark Survey

115 Executive Compensation Ratio Benchmark Survey

116 Supervisory Compensation Ratio Benchmark Survey





117 Executive Compensation Factor Benchmark Survey

118 Supervisory Compensation Factor Benchmark Survey

119 Employee Compensation Factor Benchmark Survey

120 ContingencyWorkforce Ratio Benchmark Survey

121 Contingency Revenue Ratio Benchmark Survey

122 Contingency Expenses Percent Benchmark Survey

123 Contingency Expenses Ratio Benchmark Survey

124 Total Labor Cost Revenue Ratio Benchmark Survey

125 Total Labor Cost Expense Ratio Benchmark Survey

126 Transfer Ratio Benchmark Survey

127 Promotion Ratio Benchmark Survey

128 Hire Ratio Benchmark Survey

129 Exempt Hire Ratio Benchmark Survey

130 Non-Exempt Hire Ratio Benchmark Survey

131 Increase Hire Ratio Benchmark Survey

132 Replacement Hire Ratio Benchmark Survey

133 Separation Ratio Benchmark Survey

134 Exempt Separation Ratio Benchmark Survey

135 Non-Exempt Separation Ratio Benchmark Survey





136 Open Position Ratio Benchmark Survey

137 Staffing- Hire Ratio Benchmark Survey

138 Staffing- Exempt Hire Ratio Benchmark Survey

139 Staffing- Non-Exempt Hire Ratio Benchmark Survey

140 Staffing- Increase Hire Ratio Benchmark Survey

141 Staffing- Replacement Hire Ratio Benchmark Survey

142 Staffing- Open Position Ratio Benchmark Survey

143 Time to Fill Factor Benchmark Survey

144 Exempt Time to Fill Factor Benchmark Survey

145 Non-Exempt Time to Fill Factor Benchmark Survey

146 Hire to Separation Ratio Benchmark Survey

147 Hiring Expenses Factor Benchmark Survey

148 Exempt Hiring Expenses Factor Benchmark Survey

149 Non-Exempt Hiring ExpensesFactor

Benchmark Survey

150 Hiring Expenses Ratio Benchmark Survey

151 Tenure Profile Benchmark Survey

152 Exempt Tenure Profile <=1 Year Benchmark Survey

153 Exempt Tenure Profile <=3 Years Benchmark Survey







156 Exempt Tenure Profile >10 Years Benchmark Survey

157 Non-Exempt Tenure <=1 Year Benchmark Survey

158 Non-Exempt Tenure <=3 Years Benchmark Survey



161 Non-Exempt Tenure >10 Years Benchmark Survey

162 Voluntary Separation Tenure <=1Year

Benchmark Survey

163 Voluntary Separation Tenure <=3Years

Benchmark Survey


Benchmark Survey


Benchmark Survey

166 Voluntary Separation Tenure >10Years

Benchmark Survey

167 Exempt Voluntary SeparationTenure <= 1 Year

Benchmark Survey

168 Exempt Voluntary SeparationTenure <= 3 Years

Benchmark Survey

169 Exempt Voluntary SeparationTenure <= 5 Years

Benchmark Survey

170 Exempt Voluntary SeparationTenure <=10 Years

Benchmark Survey





171 Exempt Voluntary SeparationTenure >10 Years

Benchmark Survey

172 Non-Exempt Voluntary SeparationTenure <=1 Year

Benchmark Survey

173 Non-Exempt Voluntary SeparationTenure <=3 Years

Benchmark Survey


Benchmark Survey


Benchmark Survey

176 Non-Exempt Voluntary SeparationTenure >10 Years

Benchmark Survey

178 Involuntary Separation Ratio Benchmark Survey

179 Voluntary Separation Ratio Benchmark Survey

180 Exempt Separation Ratio Benchmark Survey

181 Exempt Involuntary SeparationRatio

Benchmark Survey

182 Exempt Voluntary Separation Ratio Benchmark Survey

183 Non-Exempt Separation Ratio Benchmark Survey

184 Non-Exempt Involuntary SeparationRatio

Benchmark Survey

185 Non-Exempt Voluntary SeparationRatio

Benchmark Survey

186 Employee Lost Time Factor Benchmark Survey

187 FTE Lost Time Factor Benchmark Survey





188 Workers’ Compensation ExpensesRatio

Benchmark Survey

189 EmployeeWorkers’ CompensationFactor

Benchmark Survey

190 WorkforceWorkers’ CompensationFactor

Benchmark Survey

191 HR Readiness- Support Ratio Benchmark Survey

192 Exempt Ratio Benchmark Survey

193 Investment Factor Benchmark Survey

194 HR Readiness- Expenses Ratio Benchmark Survey

195 Employee Investment Factor Benchmark Survey

196 Trained Employee Investment Benchmark Survey

197 Training- Expenses Ratio Benchmark Survey

198 Training- Support Ratio Benchmark Survey

199 Healthcare Factor Benchmark Survey

200 Benefits Compensation ExpensesRatio

Benchmark Survey




CHAPTER 5

Setting Up Workforce Groups and Group Sets

This chapter provides an overview of workforce groups and group sets and discusses how to:

• Define workforce groups.

• Review your workforce group setup.

• Build and review workforce groups.

• Use workforce groups in scenario processes.

• Review workforce group results from scenarios.

• Define workforce group sets.

• Run the group, group set, and security processes.

Understanding Workforce Groups and Group SetsYou can use workforce groups and group sets in PeopleSoft Workforce Analyticsapplications for different purposes:

• In PeopleSoft Workforce Rewards, use workforce groups to specify which employees to include inworkforce reduction simulations, and retention and compensation planning scenarios.

• In PeopleSoft Workforce Planning, use workforce groups to specify which employees to includein a competency strategy scenario, for match processing.

• In PeopleSoft Workforce Rewards, use the groups from group sets to create security.

Although you can include your entire workforce in one workforce group, groups are most often a subsetof the workforce. Some examples of ways by which you can define workforce groups are:

• Geographical regions.

• Departments.

• Job codes.

• Personnel classifications such as Managers or Supervisors.

• Related jobs such as All Developers.

• Compensation plans such as Hourly Workers.

• Retention evaluation status, such as employees specified in retention management to retain, track or reduce.


Setting Up Workforce Groups and Group Sets Chapter 5

While it is possible for you to define universal workforce groups for use throughout PeopleSoftWorkforce Analytics, it is more likely you will create specific workforce groups to use witha particular rule, simulation, scenario, or function.

To use the workforce groups and group sets functionality in PeopleSoft Workforce Analytics follow these steps:

1. Plan your approach, to understand the types of workforce groups you need to create.

2. Define workforce groups using the Workforce Groups setup component.

3. Review the workforce groups setup with the Workforce Groups report page.

4. Run the Build Workforce Groups process (WA_BLDGRPS), in the WA_BLDGRPS jobstream,using the Workforce Groups process page. This process builds the workforce groups so youcan review the results prior to using the groups in an application.

5. Review the results of the Build Workforce Groups process using the Workforce Group inquiry page.

6. Use the workforce groups in a PeopleSoft Workforce Rewards or PeopleSoft WorkforcePlanning scenario, or in EPM row-level group security.

7. Define workforce group sets, if needed, with the Workforce Group Set setup component.

8. Run the WA_GROUPST (Group Set) jobstream, using the Workforce Groups processpage, to create group sets and group set definitions.

9. Run the WA_GRPSEC (Group Sets and Security Groups) jobstream, using the Workforce Groupsprocess page, to create the security group definitions and create security groups based on yourgroup set definition (security option checked on Group Set setup page).

Note. Not all of these functions or steps are applicable to every PeopleSoft Workforce Analytics application.In the remaining sections of this chapter, we clarify which applications have these features.


Defining Workforce GroupsYou define workforce groups using the Workforce Group component.


Chapter 5 Setting Up Workforce Groups and Group Sets

Pages Used to Set Up Workforce GroupsPage Name Object Name Navigation Usage

Workforce Group WA_CP_GROUP_DFN Workforce Analytics,Workforce Analytics Setup,Setup Groups

Define workforce groups foruse in PeopleSoft WorkforceInsight, PeopleSoftWorkforce Rewards, orPeopleSoft WorkforcePlanning.

Workforce Group - Notes WA_CP_GROUP_DFN2 Select the Notes tab. Provide additionalcomments, or notes, for aworkforce group definition.

Setting Up Workforce GroupsAccess the Workforce Group page by entering a SetID and Group ID.

Workforce Group setup page

Creating a Group for a Group SetIf you will use the group in a group set, the system requires you to select a Manager ID for the group.

Creating Constraint Defined GroupsTo create a group based on a constraint, select Constraint Defined, and then select a Constraint Code.Prompt values are from the WA_CONSTR_VW table. The system only allows the selection of constraintsbased on WA_JOB_S00 or JOB_F00. That is, the constraints must reference a DataMap that usesa TableMap whose primary table is WA_JOB_S00 or JOB_F00. If you want to include simulatedemployees (from the PeopleSoft Workforce Rewards, Workforce Simulation process) in your group,create or select a constraint based on a TableMap with WA_JOB_S00 as the primary table. If youdon’t want to include simulated employees, then create or select a constraint based on a TableMapwith JOB_F00 as the primary table. Enter one constraint per workforce group.



Constraints are collections of one or more filters. The system uses them to define subsets of data forprocessing. With respect to workforce groups, the applicable constraints and associated filters you selectshould define the set of employees you want to include in the group. You build constraints and filters using theConstraint Definition and Filter Definition pages in the Entprse Warehouse Processing, Define Metadata menu.

Using the Workforce Group - Notes PageSelect the Notes tab to access the Workforce Group - Notes page, where you canenter detailed notes or comments.

Using Constraints to Integrate Retention Strategy and Compensation StrategyYou can create an integration link between the Retention Strategy and Compensation Stragegy modulesof PeopleSoft Workforce Rewards. In Compensation Strategy, the scenario final output for the decisionsgoes to three tables, which are lists of employees to retain, employees to track, and employees to reduce.We’ve built the following sample constraints to point to the data in these tables:

• EMPL_REDUCE – Retention results on employees to reduce.

• BASE_PAY_RETAIN – Retention results as to the employees to retain by increasingtheir base pay or by granting stock options.

• HIGH_POTENTIAL – Retention results for high-potential employees to track.

• HIGH_RISK – Retention results for high-risk employees to track.

These sample constraints are under the SetID of SHARE.We built these examples for you to use as templates,so you can add them to your system. We built them based on the DataMaps and TableMaps deliveredwith the system. Once you’ve added the constraints to your system, you can reference them from thispage when creating workforce groups, and use them in the Compensation Strategy module.

Creating Manually Defined GroupsIf you want to create a small static group you may find it easier to do so manually. To do this select theManuallyDefined radio button, and then select an Employee ID. Prompt values are from the PERSONAL_SRCHview. When you select an employee the system displays their Empl Rcd# (employment record number) andPersonal Name. Add rows of data to enter multiple employees in the manual group definition.

Compiling the RuleIf you are using a constraint to define your workforce group, then the system will automatically compile theSQL for the rule when you save your work. If necessary, you can click the Compile Rule button to compilethe SQL for the rule at any time. In either case the system displays the SQL Object ID Prefix.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Setting Up and Using Metadata”

Reviewing Your Workforce Group SetupOnce you have set up your workforce groups, run the Workforce Groups Crystal reportto review your workforce group setup.



Page Used to Run the Workforce Crystal ReportPage Name Object Name Navigation Usage

Workforce Groups report RUN_RWA_0018 Workforce Analytics,Workforce Reports,Workforce Group Report

Run theWorkforce GroupsCrystal report (WAC0018),which provides a summaryof your workforce groupsetup.

Running the Workforce Groups Crystal ReportAccess the Workforce Group report page.

Use this page to run the Workforce Groups report (WAC0018), which is a query of theWA_CP_GROUP_DFN table. The report provides a summary of all the active workforcegroup definitions for a given SetID and effective date.

Building and Reviewing Workforce GroupsOnce you have completed setup of your workforce groups, you run the Workforce Group build process inthe WA_BLDGRPS jobstream and review the results using the Workforce Group inquiry page.

You can build your workforce groups using a standalone process, so you can review the results prior to using thegroups in an application. Use the Workforce Groups process page to run the Build Workforce Groups process(WA_BLDGRPS) in the WA_BLDGRPS jobstream. The results are stored in the WA_GROUP_F00 table.

Then review the results of the Build Workforce Groups process using the Workforce Group inquiry page. Thispage displays the results (group members) of the Application Engine processing. In the case of the standaloneWorkforce Group Build process, the results you view with the inquiry page are the workers in the originallydefined group, since the process has no further selection criteria or rules to further narrow the group.

The group results you see in the inquiry page are also subject to your level of row-level security access.The Workforce Group inquiry page uses the WA_GROUP_SRCH table, a view over WA_GROUP_F00,that joins in the security table so that you can only see what your security allows.

Using Workforce Groups in Scenario ProcessesYou can use workforce groups in various scenario processes. These include the competency Matchprocess in PeopleSoft Workforce Planning; and the Workforce Simulation, Retention Assignment, andCompensation Planning and Simulation processes in PeopleSoft Workforce Rewards.

When you run the scenario processes, an Application Engine library named WA_GRPBUILD iscalled. The process resolves the constraints and inserts the group members into a permanent table(WA_GROUP_F00), keyed by the business unit, scenario, fiscal year, accounting period, and group IDfields. This table stores the group results for viewing through an inquiry page.



However, keep in mind that some processes, such as the PeopleSoft Workforce Rewards Retention Assignmentprocess, and the PeopleSoft Workforce Planning Match process, do not necessarily use the groups exactly asdefined. In these cases the scenario rules may further narrow the actual population of people from the groupthat made it into the group build results. For example, the Retention process will start with the employeesin the group, but will not use employees that do not appear in the overall group defined for the retentionscenario. So if you have specified groups for the risk, cost, and value rules through the retention model,and the people in those groups do not appear in the overall group for the retention model, they will not beused. For these types of scenario processes the results you view using the inquiry page are the workersresulting from the scenario processing, and not necessarily all of the workers in the original group.

The system uses the group ID as a dimension in the PeopleSoft Workforce Rewards data marts.

Generally you run the scenario processes from the Run Jobstream page. This page is documented inthe PeopleSoft 8.8 Enterprise Warehouse Administration and Tools PeopleBook.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Streamlining Processing with Jobstreams”

Chapter 5, “Setting Up Workforce Groups and Group Sets,” Running the Group, GroupSet, and Security Processes, page 116

Reviewing Workforce Group Results from ScenariosYou can review workforce group results from scenarios on the Workforce Groups inquiry page.

Page Used to Review Workforce Group ResultsPage Name Object Name Navigation Usage

Workforce Groups inquiry WA_GROUP_INQ Workforce Analytics,Workforce Analytics Setup,Review Groups

Review the workforcegroups after running thegroup builder process, orafter running a scenariogenerating process inPeopleSoft WorkforceRewards or WorkforcePlanning.

Reviewing Workforce Group ResultsAccess the Workforce Groups inquiry page.



Workforce Groups inquiry page

Use this page to view the workforce groups for a particular scenario. To do this, begin by selecting search criteriafor a Business Unit and Scenario ID from the prompt list values. Valid values are from the SP_BU_PF_NONVWand SCENARIO_SRCH tables, respectively. These are the only two required search criteria.

You have the option of narrowing the search criteria by entering a Fiscal Year, Accounting Period,Group ID, or EmplID (employee identification). Prompt list values for the latter two fields are fromthe WA_CP_GROUP_DFN and PERSONAL_SRCH tables, respectively.

Once you have entered search criteria, click the Search button.

The system displays the results of the search in the Workforce Groups group box. The resultsare from the WA_GROUP_SRCH table. For each member of a group included in the scenario,the system displays their Group ID, Year, Accounting Period, EmplID (employee identification),Empl Rcd# (employment record number), and Personal Name.

Click the Workforce Group Info button to access the Workforce Group Description page,which displays the workforce group description.

The results you see in the Workforce Groups group box can vary depending on several factors:

• Scenario security – If your group is built from a scenario generating process in PeopleSoftWorkforce Rewards or PeopleSoft Workforce Planning, scenario level security can restrict youraccess to the results of a scenario. You can apply scenario security to pages throughout PeopleSoftWorkforce Rewards. In PeopleSoft Workforce Planning scenario security is not generallyavailable, with the exception of this Workforce Group inquiry page.

• Employee-level security – You can also apply row-level security at the employee level to this page. Thatmeans if you do not have the security access to see certain employees, then you won’t see them on this page.



• Process Run Standalone or in a Scenario – The results you see on this page differ depending on whetheryou are reviewing results of the WA_GRPBLD process run as a standalone process, or whether you arereviewing the results of a scenario generating process that calls WA_GRPBLD. If you run WA_GRPBLD asa standalone process, the group results you see on this page are for the group as you have defined it. If yourun a scenario generating process, the group results you see on this page may be further narrowed by rulesapplied to the scenario. In other words, you may only see a subset of the group as you originally defined it.

Defining Workforce Group SetsYou can also define sets of workforce groups using the Workforce Group Set component.

Pages Used to Define Workforce Group SetsPage Name Object Name Navigation Usage

Workforce Grp Set(workforce group set)

WA_GRP_SET_DFN Workforce Analytics,Workforce Analytics Setup,Setup Group Sets

Define sets of groups thatcan be used to define EPMrow-level security groups.

Workforce Group Set - Notes WA_GRP_SET_DFN2 Select the Notes tab. Provide additionalcomments, or notes, for agroup set definition.

Setting Up Workforce Group SetsAccess the Workforce Group Set page by entering a SetID and a Workforce Group Set Code.

Workforce Group Set setup page

Understanding Workforce Group SetsA workforce group set is a collection of groups.



Note. Workforce group sets are used for security. Workforce group sets are not used in theother PeopleSoft Workforce Analytics applications at this time.

Using the Workforce Group Set - Notes PageIn addition to the short description you can enter here, you can also select the Notes tab to access theWorkforce Group Set - Notes page, where you can enter detailed notes or comments.

Workforce Group SetSelect the Use for Security Groups check box if you wish to create EPM row-level security group definitionsbased on the groups within the group set. When you run the group set and security engines, the systemchecks to see whether this check box is selected. If it is, a security group will be defined and created for eachorganization tree or position table-based group (department or position) selected in the group set.

The system only allows one position-based and one org-tree-based group set where the Use for SecurityGroups check box is selected. You can define multiple groups based on Organization trees or thePosition table, but only one of each when the security check box is selected.

Creating Organization Tree Defined Group SetsYou can define a group set based on the Organization (Department) tree. To do thisselect Organization Tree Defined, and then select the appropriate Tree Name. Prompt listvalues are from the PF_METATREE_TBL table.

For security, the group is defined as all of the people in the departments who roll up to the specifieddepartment. The manager may or may not be included in the group, depending on the department they are in.

Creating Position Table Defined Group SetsYou can define a group set based on the Position table (POSITION_D00). To dothis select Position Table Defined.

If the group set is predominately for use in security, then the group is defined as all of thepeople below who roll up to a manager (or position). Whether or not the manager is includedin the group should be defined in the Position table.

Warning! When there is more than one person assigned to an employee’s Reports To position on the Positiontable it will cause the Build Workforce Groups AE process to end abnormally. If you have a workforcesituation, such as job sharing, where it might be valid to have multiple Reports Topositions for a singleemployee, review the data and pare down each affected employee until they have only one Reports To position.

Creating Manually Defined Group SetsIf you have a small group set you can define it manually. To do this select Manually Defined. Thenselect a Group ID from the prompt list values, which are from the WA_GRPSET_MN_VW table.This table limits the selection to groups that have a Manager ID selected on the Group Definitionpage. To include multiple groups in the group set add rows of data.



Running the Group, Group Set, and Security ProcessesYou run the StandaloneWFGroups, Group Set, and Group Sets and Security jobstreams from the Run Jobstreampage. This page is documented in the PeopleSoft Enterprise Warehouse Administration and Tools PeopleBook.

Understanding the Workforce Group and Group Set ProcessesThe following table summarizes the various delivered jobstreams, jobs, and engines that youcan run for workforce groups and groups sets, and their purpose:

Jobstream IDand Name

Job ID andName

Engine ID andName

Program ID /Name

Purpose

WA_BLDGRPS/ StandaloneWFGroups

WA_BLDGRPS /Build WorkforceGroups

WF_GP_MRG /Standalone WFGroups


MERGE / FinalTable Merge


PF_MERGE / FinalTable Merge

Run this jobstreamto build theworkforce groups.(This is an optionalstep if you wantto verify thepopulation of thegroup, or verifyyour constraint isgetting the rightgroup, prior tousing the groupsin an application.The results of thisprocess are notused in any furtherprocessing.)

WA_GROUPST /Group Set

WA_GROUPST /Group Set Job

WA_GPST_MG /Group Set Merge



WA_GROUPSET /WAGroup Set

PF_MERGE / FinalTable Merge

Run this jobstreamto create group setsand associatedsecurity groupdefinitions.

WA_GRPSEC /Group Sets andSecurity Groups

WA_GRPSEC /Group Set withSecurity

WA_SECURE / PFSecurity



SECURITY /Security

WA_GROUPSET /WAGroup Set

Table Merge forgroup set build

PF_SECURITY /Security

WA_SECMRG

Run this jobstreamto create the groupsets for use inrow-level groupsecurity.

Group and Group Set Primary Output TablesWhen you run the Build Workforce Groups process (WA_BLDGRPS) as a standalone process,the final output table is the WA_GROUP_F00 table.



In PeopleSoft Workforce Planning the Match process calls the Build Workforce Groups process(WA_BLDGRPS) to create the group during scenario processing. This is also the case for the PeopleSoftWorkforce Rewards Retention Assignment, Workforce Simulation, and Compensation Planning andSimulation processes. In these cases the final output table is the WA_GROUP_F00 table, but the groupresults you see may be different from that for the original group definition.

The output tables for the WA Group Set process (WA_GROUPSET) are as follows:

WA_GROUPSET_F00 Contains group set and associated groups.

WA_GRPSETAR_F00 Contains all direct reports for each group in the group set. For example, agroup created for the department at the top of the Organization tree wouldhave everyone attached to the organization tree in it.

WA_GROUP_F00 Contains all direct reports for each group. This is the same outputtable as for the Build Workforce Groups process.

WA_GRPSTMGR_F00 Contains the groups and manager IDs for the groups.

See AlsoPeopleSoft 8.8 Enterprise Warehouse PeopleBook, “Streamlining Processing with Jobstreams”




APPENDIX A

PeopleSoft Workforce Analytics Reports

This appendix provides a listing of Crystal reports common to PeopleSoft Workforce Analytics applications.

Note. For samples of these reports, see the PDF files published on CD-ROM with your documentation.

Report DescriptionsThis table lists the PeopleSoft Workforce Analytics common reports by report ID.

Report ID and ReportName

Description Navigation Run Control Page

WAC0002Termination Reason Map

Review the ActionReason/Voluntary Flagmappings you’ve entered inthe WA_ACTN_RSN_DFNtable.

Enterprise WarehouseDimensions, HRMS,Common, TerminationReasonMap Report

RUN_RWA_0002

WAC0003Benefits Valuation Map

Review the benefitsamount and value mappingyou entered in theWA_BEN_VALU_TBLtable.

Enterprise WarehouseDimensions, HRMS,Benefits, Benefits ValuationMap Report

RUN_RWA_0003

WAC0006Geography IDMap

Review the GeographyID and Location Codemapping you entered in theWA_LOCN_MAP_DFNtable.

Enterprise WarehouseDimensions, HRMS,Common, Geography IDMap Report

RUN_RWA_0006

WAC0018Workforce Groups

Review all the active groupsin a SetID as of a particulareffective date.

Workforce Analytics,Workforce Reports,Workforce Group Report

RUN_RWA_0018

WAC0020Compensation Survey Data

Understand and analyze themarket compensation surveydata you have available, andto determine how to usethis data in the ManageMarket Compensationmodule. The data is from theWA_SURVALUE_F00 table.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, CompensationSurvey Data

RUN_RWA_0020

WAC0021Benchmark Survey Data

Review external benchmarksurvey data that youhave imported into theWA_BENCHMRK_F00table, using ETL.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Benchmark SurveyData

RUN_RWA_0021


Appendix A

Report ID and ReportName

Description Navigation Run Control Page

WAC0022(Survey) Unit Code Map

Review the Survey andInternal Unit Codes stored intheWA_UNIT_MAP_DFNtable.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Unit Code Map

RUN_RWA_0022

WAC0023(Survey) CompensationCodeMap

Review the Survey andInternal CompensationCode mapping definitionscontained in theWA_COMP_MAP_DFNtable.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, CompensationCodeMap

RUN_RWA_0023

WAC0024(Survey) Geography IDMap

Review the Survey andInternal GeographyIDs stored in theWA_GEO_MAP_DFN table.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Geography IDMap

RUN_RWA_0024

WAC0025(Survey) Industry CodeMap

Review the Surveyand Internal IndustryCodes stored in theWA_IND_MAP_DFN table.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Industry Code Map

RUN_RWA_0025

WAC0026(Survey) Job CodeMap

Review the Survey andInternal Job Code mappingdefinitions stored in theWA_JOB_MAP_DFN table.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Job Code Map

RUN_RWA_0026

WAC0027(Survey) Financial CodeMap

Review the Surveyand Internal FinancialCodes stored in theWA_FIN_MAP_DFN table.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Financial Code Map

RUN_RWA_0027

WAC0035Employee Survey Data

Review the data in theWA_EESURVEY_F00 table.

Workforce Analytics,Workforce Reports,Workforce Survey SetupReports, Employee SurveyData

RUN_RWA_0035


Glossary of PeopleSoft Terms

absence entitlement This element defines rules for granting paid time off for valid absences, such as sicktime, vacation, and maternity leave. An absence entitlement element defines theentitlement amount, frequency, and entitlement period.

absence take This element defines the conditions that must be met before a payee is entitledto take paid time off.

account You use an account code to record and summarize financial transactions asexpenditures, revenues, assets, or liabilities balances. The use of this deliveredPeopleSoft ChartField is typically defined when you implement PeopleSoft GeneralLedger.

accounting class In PeopleSoft Enterprise Performance Management, the accounting class defines howa resource is treated for generally accepted accounting practices. The Inventoryclass indicates whether a resource becomes part of a balance sheet account, such asinventory or fixed assets, while the Non-inventory class indicates that the resource istreated as an expense of the period during which it occurs.

accounting date The accounting date indicates when a transaction is recognized, as opposed to the datethe transaction actually occurred. The accounting date and transaction date can be thesame. The accounting date determines the period in the general ledger to which thetransaction is to be posted. You can only select an accounting date that falls within anopen period in the ledger to which you are posting. The accounting date for an itemis normally the invoice date.

accounting entry A set of related debits and credits. An accounting entry is made up of multipleaccounting lines. In most PeopleSoft applications, accounting entries are alwaysbalanced (debits equal credits). Accounting entries are created to record accruals,payments, payment cancellations, manual closures, project activities in the generalledger, and so forth, depending on the application.

accounting split The accounting split method indicates how expenses are allocated or divided amongone or more sets of accounting ChartFields.

accumulator You use an accumulator to store cumulative values of defined items as they areprocessed. You can accumulate a single value over time or multiple values overtime. For example, an accumulator could consist of all voluntary deductions, or allcompany deductions, enabling you to accumulate amounts. It allows total flexibilityfor time periods and values accumulated.

action reason The reason an employee’s job or employment information is updated. The actionreason is entered in two parts: a personnel action, such as a promotion, termination,or change from one pay group to anotherand a reason for that action. Action reasonsare used by PeopleSoft Human Resources, PeopleSoft Benefits Administration,PeopleSoft Stock Administration, and the COBRAAdministration feature of theBase Benefits business process.

activity In PeopleSoft Enterprise LearningManagement, an instance of a catalog item deliverymethodit may also be called a class. The activity defines such things as meeting timesand locations, instructors, reserved equipment and materials, and detailed costs thatare associated with the offering, enrollment limits and deadlines, and waitlistingcapacities.

allocation rule In PeopleSoft Enterprise Incentive Management, an expression within compensationplans that enables the system to assign transactions to nodes and participants. Duringtransaction allocation, the allocation engine traverses the compensation structure


Glossary

from the current node to the root node, checking each node for plans that containallocation rules.

alternate account A feature in PeopleSoft General Ledger that enables you to create a statutory chartof accounts and enter statutory account transactions at the detail transaction level, asrequired for recording and reporting by some national governments.

application agent An application agent is an online agent that is loaded into memory with a PeopleSoftpage. It detects when a business rule has been triggered and determines the appropriateaction.

asset class An asset group used for reporting purposes. It can be used in conjunction with the assetcategory to refine asset classification.

attachment In PeopleSoft Enterprise LearningManagement, nonsystem-defined electronicmaterial that supplements a learning resource, such as an equipment items userhandbook or the site map of a large facility.

background process In PeopleSoft, background processes are executed through process-specific COBOLprograms and run outside theWindows environment.

benchmark job In PeopleSoft Workforce Analytics, a benchmark job is a job code for which there iscorresponding salary survey data from published, third-party sources.

branch A tree node that rolls up to nodes above it in the hierarchy, as defined in PeopleSoftTree Manager.

budgetary account only An account used by the system only and not by users; this type of account doesnot accept transactions. You can only budget with this account. Formerly calledsystem-maintained account.

budget check In commitment control, the processing of source transactions against control budgetledgers, to see if they pass, fail, or pass with a warning.

budget control In commitment control, budget control ensures that commitments and expendituresdon’t exceed budgets. It enables you to track transactions against correspondingbudgets and terminate a document’s cycle if the defined budget conditions are not met.For example, you can prevent a purchase order from being dispatched to a vendor ifthere are insufficient funds in the related budget to support it.

budget period The interval of time (such as 12 months or 4 quarters) into which a period is dividedfor budgetary and reporting purposes. The ChartField allows maximum flexibility todefine operational accounting time periods without restriction to only one calendar.

business event In PeopleSoft Sales Incentive Management, an original business transaction or activitythat may justify the creation of a PeopleSoft Enterprise Incentive Management event(a sale, for example).

catalog item In PeopleSoft Enterprise LearningManagement, a specific topic that a learner canstudy and have tracked. For example, Introduction to Microsoft Word. A catalog itemcontains general information about the topic and includes a course code, description,categorization, keywords, and delivery methods.

category In PeopleSoft Enterprise LearningManagement, a way to classify catalog items so thatusers can easily browse and search relevant entries in the learning catalog. Categoriescan be hierarchical.

ChartField A field that stores a chart of accounts, resources, and so on, depending on thePeopleSoft application. ChartField values represent individual account numbers,department codes, and so forth.

ChartField balancing You can require specific ChartFields to match up (balance) on the debit and the creditside of a transaction.


Glossary

ChartField combination edit The process of editing journal lines for valid ChartField combinations based onuser-defined rules.

ChartKey One or more fields that uniquely identify each row in a table. Some tables contain onlyone field as the key, while others require a combination.

child In PeopleSoft Tree Manager trees, a child is a node or detail on a tree linked toanother, higher-level node (referred to as the parent). Child nodes can be rolled upinto the parent. A node can be a child and a parent at the same time depending on itslocation within the tree.

Class ChartField A ChartField value that identifies a unique appropriation budget key when youcombine it with a fund, department ID, and program code, as well as a budget period.Formerly called sub-classification.

clone In PeopleCode, to make a unique copy. In contrast, to copymay mean making anew reference to an object, so if the underlying object is changed, both the copy andthe original change.

collection To make a set of documents available for searching in Verity, you must first createat least one collection. A collection is set of directories and files that allow searchapplication users to use the Verity search engine to quickly find and display sourcedocuments that match search criteria. A collection is a set of statistics and pointersto the source documents, stored in a proprietary format on a file server. Because acollection can only store information for a single location, PeopleSoft maintains a setof collections (one per language code) for each search index object.

compensation object In PeopleSoft Enterprise Incentive Management, a node within a compensationstructure. Compensation objects are the building blocks that make up a compensationstructure’s hierarchical representation.

compensation structure In PeopleSoft Enterprise Incentive Management, a hierarchical relationship ofcompensation objects that represents the compensation-related relationship betweenthe objects.

configuration parametercatalog

Used to configure an external system with PeopleSoft. For example, a configurationparameter catalog might set up configuration and communication parameters for anexternal server.

configuration plan In PeopleSoft Enterprise Incentive Management, configuration plans hold allocationinformation for common variables (not incentive rules) and are attached to a nodewithout a participant. Configuration plans are not processed by transactions.

content reference Content references are pointers to content registered in the portal registry. These aretypically either URLs or iScripts. Content references fall into three categories: targetcontent, templates, and template pagelets.

context In PeopleSoft Enterprise Incentive Management, a mechanism that is used todetermine the scope of a processing run. PeopleSoft Enterprise Incentive Managementuses three types of context: plan, period, and run-level.

corporate account Equivalent to the Account ChartField. Distinguishes between the chart of accountstypically used to record and report financial information for management,stockholders, and the general public, as opposed to a chart of statutory (alternate)accounts required by a regulatory authority for recording and reporting financialinformation.

cost profile A combination of a receipt cost method, a cost flow, and a deplete cost method. Aprofile is associated with a cost book and determines how items in that book arevalued, as well as how the material movement of the item is valued for the book.

cost row A cost transaction and amount for a set of ChartFields.


Glossary

data acquisition In PeopleSoft Enterprise Incentive Management, the process during which rawbusiness transactions are acquired from external source systems and fed into theoperational data store (ODS).

data elements Data elements, at their simplest level, define a subset of data and the rules by whichto group them.

For Workforce Analytics, data elements are rules that tell the system what measures toretrieve about your workforce groups.

data row Contains the entries for each field in a table. To identify each data row uniquely,PeopleSoft applications use a key consisting of one or more fields in the table.

data validation In PeopleSoft Enterprise Incentive Management, a process of validating and cleansingthe feed data to resolve conflicts and make the data processable.

DAT file This text file, used with the Verity search engine, contains all of the information fromdocuments that are searchable but not returned in the results list.

delivery method In PeopleSoft Enterprise LearningManagement, identifies a learning activitys deliverymethod type. An activity can have one or more delivery methods.

delivery method type In PeopleSoft Enterprise LearningManagement, specifies a method that yourorganization uses to deliver learning activities, for example, scheduled or self-pacedlearning.

distribution The process of assigning values to ChartFields. A distribution is a string of ChartFieldvalues assigned to items, payments, and budget amounts.

double byte character If youre working with Japanese or other Asian employees, you can enter theemployee’s name using double-byte characters. The standard double byte character setname format in PeopleSoft applications is: [last name] space [first name].

dynamic tree A tree that takes its detail valuesdynamic detailsdirectly from a table in the database,rather than from a range of values entered by the user.

edit table A table in the database that has its own record definition, such as the Department table.As fields are entered into a PeopleSoft application, they can be validated against anedit table to ensure data integrity throughout the system.

effective date Amethod of dating information in PeopleSoft applications. You can predateinformation to add historical data to your system, or postdate information in order toenter it before it actually goes into effect. By using effective dates, you don’t deletevalues; you enter a new value with a current effective date.

EIM job Abbreviation for Enterprise Incentive Management job. In PeopleSoft EnterpriseIncentive Management, a collection of job steps that corresponds to the steps in anorganizations compensation-related business process. An EIM job can be stopped toallow manual changes or corrections to be applied between steps, and then resumedfrom where it left off, continuing with the next step. A run can also be restartedor rolled back.

EIM ledger Abbreviation for Enterprise Incentive Management ledger. In PeopleSoft EnterpriseIncentive Management, an object to handle incremental result gathering within thescope of a participant. The ledger captures a result set with all of the appropriate tracesto the data origin and to the processing steps of which it is a result.

equipment In PeopleSoft Enterprise LearningManagement, resource items that can be assignedto a training facility, to a specific training room, or directly to an activity session.Equipment items are generally items that are used (sometimes for a fee) and returnedafter the activity is complete.

event Events are predefined points either in the application processor flow or in the programflow. As each point is encountered, the event activates each component, triggering anyPeopleCode program associated with that component and that event. Examples of


Glossary

events are FieldChange, SavePreChange, and OnRouteSubscription. In PeopleSoftHuman Resources, event also refers to incidents that affect benefits eligibility.

event propagation process In PeopleSoft Sales Incentive Management, a process that determines, through logic,the propagation of an original PeopleSoft Enterprise Incentive Management event andcreates a derivative (duplicate) of the original event to be processed by other objects.Sales Incentive Management uses this mechanism to implement splits, roll-ups, and soon. Event propagation determines who receives the credit.

external system In PeopleSoft, any system that is not directly compiled with PeopleTools servers.

fact In PeopleSoft applications, facts are numeric data values from fields from a sourcedatabase as well as an analytic application. A fact can be anything you want to measureyour business by, for example, revenue, actual, budget data, or sales numbers. Afact is stored on a fact table.

filter In PeopleSoft applications, a filter creates a subset of information. Filters are used intemplates to limit your information from a pick list of attribute values.

generic process type In PeopleSoft Process Scheduler, process types are identified by a generic processtype. For example, the generic process type SQR includes all SQR process types,such as SQR process and SQR report.

group Any set of records associated under a single name or variable in order to runcalculations in PeopleSoft business processes. In PeopleSoft Time and Labor, forexample, employees are placed in groups for time reporting purposes.

homepage Users can personalize the homepage, or the page that first appears when they accessthe portal.

incentive object In PeopleSoft Enterprise Incentive Management, the incentive-related objects thatdefine and support the PeopleSoft Enterprise Incentive Management calculationprocess and results, such as plan templates, plans, results data, user interaction objects,and so on.

incentive rule In PeopleSoft Sales Incentive Management, the commands that act on transactions andturn them into compensation. A rule is one part in the process of turning a transactioninto compensation.

key One or more fields that uniquely identify each row in a table. Some tables contain onlyone field as the key, while others require a combination.

learner group In PeopleSoft Enterprise LearningManagement, a group of learners within the samelearning environment that share the same attributes, such as department or job code.

learning activity See activity.

learning history In PeopleSoft Enterprise LearningManagement, a self-service repository for all of alearner’s completed learning activities.

learning plan In PeopleSoft Enterprise LearningManagement, a self-service repository for all of alearner’s planned and in-progress learning activities.

ledger mapping You use ledger mapping to relate expense data from general ledger accounts toresource objects. Multiple ledger line items can be mapped to one or more resourceIDs. You can also use ledger mapping to map dollar amounts (referred to as rates)to business units. You can map the amounts in two different ways: an actual amountthat represents actual costs of the accounting period, or a budgeted amount that can beused to calculate the capacity rates as well as budgeted model results. In PeopleSoftEnterprise Warehouse, you can map general ledger accounts to the EW Ledger table.

level A section of a tree that organizes groups of nodes.


Glossary

library section In PeopleSoft Enterprise Incentive Management, a section that is defined in a plan (ortemplate) and that is available for other plans to share. Changes to a library section arereflected in all plans that use it.

linked section In PeopleSoft Enterprise Incentive Management, a section that is defined in a plantemplate but appears in a plan. Changes to linked sections propagate to plans usingthat section.

linked variable In PeopleSoft Enterprise Incentive Management, a variable that is defined andmaintained in a plan template and that also appears in a plan. Changes to linkedvariables propagate to plans using that variable.

load The feature that initiates a process to automatically load information into a PeopleSoftapplicationfor example, populating the PeopleSoft Benefits database with plan-levelelection information.

local functionality In PeopleSoft HRMS, the set of information that is available for a specific country.You can access this information when you click the appropriate country flag in theglobal window, or when you access it by a local country menu.

location Locations enable you to indicate the different types of addressesfor a company, forexample, one address to receive bills, another for shipping, a third for postal deliveries,and a separate street address. Each address has a different location number. Theprimary locationindicated by a 1is the address you use most often and may be differentfrom the main address.

market template In PeopleSoft Enterprise Incentive Management, additional functionality that isspecific to a given market or industry and is built on top of a product category.

material In PeopleSoft Enterprise LearningManagement, a resource item that can be assignedto the sessions of an activity. Material items are generally consumed during theduration of an activity and not returned, and they may have an associated cost.

message definition An object definition specified in PeopleSoft Application Designer that containsmessage information for PeopleSoft Application Messaging.

meta-SQL Meta-SQL constructs expand into platform-specific SQL substrings. They are used infunctions that pass SQL strings, such as in SQL objects, the SQLExec function, andPeopleSoft Application Engine programs.

metastring Metastrings are special expressions included in SQL string literals. The metastrings,prefixed with a percent (%) symbol, are included directly in the string literals. Theyexpand at run time into an appropriate substring for the current database platform.

multibook Processes in PeopleSoft applications that can create both application entries andgeneral ledgers denominated in more than one currency.

multicurrency The ability to process transactions in a currency other than the business unit’s basecurrency.

objective In PeopleSoft Enterprise LearningManagement, an individual’s learning goal. Anexample of a learning goal is a competency gap.

override In PeopleSoft Enterprise Incentive Management, the ability to make a change to a planthat applies to only one plan context.

pagelet Each block of content on the homepage is called a pagelet. These pagelets displaysummary information within a small rectangular area on the page. The pagelet provideusers with a snapshot of their most relevant PeopleSoft and non-PeopleSoft content.

parent node A tree node linked to lower-level nodes or details that roll up into it. A node can be aparent and a child at the same time, depending on its location within the tree.

participant In PeopleSoft Enterprise Incentive Management, participants are recipients of theincentive compensation calculation process.


Glossary

participant object Each participant object may be related to one or more compensation objects.

See also participant object.

payout In PeopleSoft Enterprise Incentive Management, the resulting incentive plancomputation that is provided to payroll.

PeopleCode PeopleCode is a proprietary language, executed by the PeopleSoft applicationprocessor. PeopleCode generates results based upon existing data or user actions. Byusing business interlink objects, external services are available to all PeopleSoftapplications wherever PeopleCode can be executed.

PeopleCode event An action that a user takes upon an object, usually a record field, that is referencedwithin a PeopleSoft page.

PeopleSoft InternetArchitecture

The fundamental architecture on which PeopleSoft 8 applications are constructed,consisting of an RDBMS, an application server, a Web server, and a browser.

performance measurement In PeopleSoft Enterprise Incentive Management, a variable used to store data (similarto an aggregator, but without a predefined formula) within the scope of an incentiveplan. Performance measures are associated with a plan calendar, territory, andparticipant. Performance measurements are used for quota calculation and reporting.

period context In PeopleSoft Enterprise Incentive Management, because a participant typicallyuses the same compensation plan for multiple periods, the period context associatesa plan context with a specific calendar period and fiscal year. The period contextreferences the associated plan context, thus forming a chain. Each plan context has acorresponding set of period contexts.

per seat cost In PeopleSoft Enterprise LearningManagement, the cost per learner, based on thetotal activity costs divided by either minimum attendees or maximum attendees.Organizations use this cost to price PeopleSoft Enterprise Learning Managementactivities.

plan In PeopleSoft Sales Incentive Management, a collection of allocation rules, variables,steps, sections, and incentive rules that instruct the PeopleSoft Enterprise IncentiveManagement engine in how to process transactions.

plan context In PeopleSoft Enterprise Incentive Management, correlates a participant withthe compensation plan and node to which the participant is assigned, enablingthe PeopleSoft Enterprise Incentive Management system to find anything that isassociated with the node and that is required to perform compensation processing.Each participant, node, and plan combination represents a unique plan contextifthree participants are on a compensation structure, each has a different plan context.Configuration plans are identified by plan contexts and are associated with theparticipants that refer to them.

plan section In PeopleSoft Enterprise Incentive Management, a segment of a plan that handles aspecific type of event processing.

plan template In PeopleSoft Enterprise Incentive Management, the base from which a plan is created.A plan template contains common sections and variables that are inherited by all plansthat are created from the template. A template may contain steps and sections thatare not visible in the plan definition.

portal registry In PeopleSoft applications, the portal registry is a tree-like structure in which contentreferences are organized, classified, and registered. It is a central repository thatdefines both the structure and content of a portal through a hierarchical, tree-likestructure of folders useful for organizing and securing content references.

private view A user-defined view that is available only to the user who created it.

process See Batch Processes.


Glossary

process definition Process definitions define each run request.

process instance A unique number that identifies each process request. This value is automaticallyincremented and assigned to each requested process when the process is submitted torun.

process job You can link process definitions into a job request and process each request seriallyor in parallel. You can also initiate subsequent processes based on the return codefrom each prior request.

process request A single run request, such as an SQR, a COBOL program, or a Crystal report that yourun through PeopleSoft Process Scheduler.

process run control A PeopleTools variable used to retain PeopleSoft Process Scheduler values neededat runtime for all requests that reference a run control ID. Do not confuse these withapplication run controls, which may be defined with the same run control ID, but onlycontain information specific to a given application process request.

product category In PeopleSoft Enterprise Incentive Management, indicates an application in theEnterprise Incentive Management suite of products. Each transaction in the PeopleSoftEnterprise Incentive Management system is associated with a product category.

publishing In PeopleSoft Enterprise Incentive Management, a stage in processing that makesincentive-related results available to participants.

record definition A logical grouping of data elements.

record field A field within a record definition.

record group A set of logically and functionally related control tables and views. Record groupshelp enable TableSet sharing, which eliminates redundant data entry. Record groupsensure that TableSet sharing is applied consistently across all related tables and views.

record input VAT flag Abbreviation for record input value-added tax flag. Within PeopleSoft Purchasing,Payables, and General Ledger, this flag indicates that you are recording input VATon the transaction. This flag, in conjunction with the record output VAT flag, is usedto determine the accounting entries created for a transaction and to determine how atransaction is reported on the VAT return. For all cases within Purchasing and Payableswhere VAT information is tracked on a transaction, this flag is set to Yes. This flagis not used in PeopleSoft Order Management, Billing, or Receivables, where it isassumed that you are always recording only output VAT, or in PeopleSoft Expenses,where it is assumed that you are always recording only input VAT.

record output VAT flag Abbreviation for record output value-added tax flag.

See record input VAT flag.

reference data In PeopleSoft Sales Incentive Management, system objects that represent the salesorganization, such as territories, participants, products, customers, channels, and so on.

reference object In PeopleSoft Enterprise Incentive Management, this dimension-type object furtherdefines the business. Reference objects can have their own hierarchy (for example,product tree, customer tree, industry tree, and geography tree).

reference transaction In commitment control, a reference transaction is a source transaction that isreferenced by a higher-level (and usually later) source transaction, in order toautomatically reverse all or part of the referenced transaction’s budget-checkedamount. This avoids duplicate postings during the sequential entry of the transaction atdifferent commitment levels. For example, the amount of an encumbrance transaction(such as a purchase order) will, when checked and recorded against a budget, causethe system to concurrently reference and relieve all or part of the amount of acorresponding pre-encumbrance transaction, such as a purchase requisition.


Glossary

relationship object In PeopleSoft Enterprise Incentive Management, these objects further define acompensation structure to resolve transactions by establishing associations betweencompensation objects and business objects.

results management process In PeopleSoft Sales Incentive Management, the process during which compensationadministrators may review processing results, manually change transactions, processdraws, update and review payouts, process approvals, and accumulate and pushpayments to the EIM ledger.

role user A PeopleSoft Workflow user. A person’s role user ID serves much the same purpose asa user ID does in other parts of the system. PeopleSoft Workflow uses role user IDsto determine how to route worklist items to users (through an email address, forexample) and to track the roles that users play in the workflow. Role users do not needPeopleSoft user IDs.

role Describes how people fit into PeopleSoft Workflow. A role is a class of users whoperform the same type of work, such as clerks or managers. Your business rulestypically specify what user role needs to do an activity.

roll up In a tree, to roll up is to total sums based on the information hierarchy.

routing Connects activities in PeopleSoft Workflow. Routings specify where the informationgoes and what form it takesemail message, electronic form, or worklist entry.

run control A run control is a type of online page that is used to begin a process, such as thebatch processing of a payroll run. Run control pages generally start a program thatmanipulates data.

run control ID A unique ID to associate each user with his or her own run control table entries.

run-level context In PeopleSoft Enterprise Incentive Management, associates a particular run (and batchID) with a period context and plan context. Every plan context that participates in a runhas a separate run-level context. Because a run cannot span periods, only one run-levelcontext is associated with each plan context.

search query You use this set of objects to pass a query string and operators to the search engine.The search index returns a set of matching results with keys to the source documents.

section In PeopleSoft Enterprise Incentive Management, a collection of incentive rules thatoperate on transactions of a specific type. Sections enable plans to be segmented toprocess logical events in different sections.

security event In commitment control, security events trigger security authorization checking, suchas budget entries, transfers, and adjustments; exception overrides and notifications;and inquiries.

self-service application Self-service refers to PeopleSoft applications that are accessed by end users with abrowser.

session In PeopleSoft Enterprise LearningManagement, a single meeting day of an activity(that is, the period of time between start and finish times within a day). The sessionstores the specific date, location, meeting time, and instructor. Sessions are used forscheduled training.

session template In PeopleSoft Enterprise LearningManagement, enables you to set up commonactivity characteristics that may be reused while scheduling a PeopleSoft EnterpriseLearning Management activitycharacteristics such as days of the week, start and endtimes, facility and room assignments, instructors, and equipment. A session patterntemplate can be attached to an activity that is being scheduled. Attaching a templateto an activity causes all of the default template information to populate the activitysession pattern.


Glossary

setup relationship In PeopleSoft Enterprise Incentive Management, a relationship object type thatassociates a configuration plan with any structure node.

sibling A tree node at the same level as another node, where both roll up into the same parent.A node can be a sibling, parent, and child all at the same time, depending on itslocation in the tree.

single signon With single signon, users can, after being authenticated by a PeopleSoft applicationserver, access a second PeopleSoft application server without entering a user ID orpassword.

source transaction In commitment control, any transaction generated in a PeopleSoft or third-partyapplication that is integrated with commitment control and which can be checkedagainst commitment control budgets. For example, a pre-encumbrance, encumbrance,expenditure, recognized revenue, or collected revenue transaction.

SpeedChart A user-defined shorthand key that designates several ChartKeys to be used for voucherentry. Percentages can optionally be related to each ChartKey in a SpeedChartdefinition.

SpeedType A code representing a combination of ChartField values. SpeedTypes simplify theentry of ChartFields commonly used together.

SQR See Structured Query Report (SQR).

statutory account Account required by a regulatory authority for recording and reporting financialresults. In PeopleSoft, this is equivalent to the Alternate Account (ALTACCT)ChartField.

step In PeopleSoft Sales Incentive Management, a collection of sections in a plan. Eachstep corresponds to a step in the job run.

Structured Query Report (SQR) A type of printed or displayed report generated from data extracted from a PeopleSoftSQL-based relational database. PeopleSoft applications provide a variety of standardSQRs that summarize table information and data. You can use these reports as is,customize them, or create your own.

Summary ChartField You use summary ChartFields to create summary ledgers that roll up detail amountsbased on specific detail values or on selected tree nodes. When detail values aresummarized using tree nodes, summary ChartFields must be used in the summaryledger data record to accommodate the maximum length of a node name (20characters).

summary ledger An accounting feature used primarily in allocations, inquiries, and PS/nVisionreporting to store combined account balances from detail ledgers. Summary ledgersincrease speed and efficiency of reporting by eliminating the need to summarizedetail ledger balances each time a report is requested. Instead, detail balances aresummarized in a background process according to user-specified criteria and stored onsummary ledgers. The summary ledgers are then accessed directly for reporting.

summary tree A tree used to roll up accounts for each type of report in summary ledgers. Summarytrees enable you to define trees on trees. In a summary tree, the detail values are reallynodes on a detail tree or another summary tree (known as the basis tree). A summarytree structure specifies the details on which the summary trees are to be built.

table The underlying PeopleSoft data format, in which data is stored by columns (fields) androws (records, or instances).

TableSet sharing Specifies control table data for each business unit so that redundancy is eliminated.

target currency The value of the entry currency or currencies converted to a single currency for budgetviewing and inquiry purposes.

template A template is HTML code associated with aWeb page. It defines the layout of thepage and also where to get HTML for each part of the page. In PeopleSoft, you use


Glossary

templates to build a page by combining HTML from a number of sources. For aPeopleSoft portal, all templates must be registered in the portal registry, and eachcontent reference must be assigned a template.

territory In PeopleSoft Sales Incentive Management, hierarchical relationships of businessobjects, including regions, products, customers, industries, and participants.

TimeSpan A relative period, such as year-to-date or current period, that can be used in variousPeopleSoft General Ledger functions and reports when a rolling time frame, ratherthan a specific date, is required. TimeSpans can also be used with flexible formulas inPeopleSoft Projects.

transaction allocation In PeopleSoft Enterprise Incentive Management, the process of identifying the ownerof a transaction. When a raw transaction from a batch is allocated to a plan context,the transaction is duplicated in the PeopleSoft Enterprise Incentive Managementtransaction tables.

transaction loading process In PeopleSoft Enterprise Incentive Management, the process during whichtransactions are loaded into Sales Incentive Management. During loading, the sourcecurrency is converted to the business unit currency while retaining the source currencycode. At the completion of this stage, the transaction is in the first state.

transaction state In PeopleSoft Enterprise Incentive Management, a value assigned by an incentiverule to a transaction. Transaction states enable sections to process only transactionsthat are at a specific stage in system processing. After being successfully processed,transactions may be promoted to the next transaction state and picked up by a differentsection for further processing.

transaction type In PeopleSoft Enterprise Incentive Management, a way to categorize transactions toidentify specific transaction types (for example, shipment, order, opportunity, and soon). Plan sections process only one type of transaction type. Transaction types can bedefined based on a company’s specific processes model.

Translate table A system edit table that stores codes and translate values for the miscellaneous fields inthe database that do not warrant individual edit tables of their own.

tree The graphical hierarchy in PeopleSoft systems that displays the relationship betweenall accounting units (for example, corporate divisions, projects, reporting groups,account numbers) and determines roll-up hierarchies.

unclaimed transaction In PeopleSoft Enterprise Incentive Management, a transaction that is not claimedby a node or participant after the allocation process has completed, usually due tomissing or incomplete data. Unclaimed transactions may be manually assigned to theappropriate node or participant by a compensation administrator.

uniform resource locator (URL) In PeopleSoft, the term URL refers to the entire query string. Thefollowing is an example of a URL: http://serverx/InternetClient/InternetClientServlet?ICType=Script&ICScriptProgramName=WEBLIB_BEN_401k.PAGES.FieldFormula.iScript_Home401k

universal navigation header Every PeopleSoft portal includes the universal navigation header, intended to appear atthe top of every page as long as the user is signed on to the portal. In addition toproviding access to the standard navigation buttons (like Home, Favorites, and signoff)the universal navigation header can also display a welcome message for each user.

URL See uniform resource locator (URL).

user interaction object In PeopleSoft Sales Incentive Management, used to define the reporting componentsand reports that a participant can access in his or her context. All Sales IncentiveManagement user interface objects and reports are registered as user interactionobjects. User interaction objects can be linked to a compensation structure nodethrough a compensation relationship object (individually or as groups).


Glossary

variable In PeopleSoft Sales Incentive Management, the intermediate results of calculations.Variables hold the calculation results and are then inputs to other calculations.Variables can be plan variables that persist beyond the run of an engine or localvariables that exist only during the processing of a section.

warehouse A PeopleSoft data warehouse that consists of predefined ETL maps, data warehousetools, and DataMart definitions.

worksheet Away of presenting data through a PeopleSoft Business Analysis Modeler interfacethat enables users to do in-depth analysis using pivoting tables, charts, notes, andhistory information.

workflow The background process that creates a list of administrative actions based on selectioncriteria and specifies the procedure associated with each action.

worklist The automated to-do list that PeopleSoft Workflow creates. From the worklist, youcan directly access the pages you need to perform the next action, and then return tothe worklist for another item.

zero-rated VAT Abbreviation for zero-rated value-added tax. AVAT transaction with a VAT codethat has a tax percent of zero. Used to track taxable VAT activity where no actualVAT amount is charged.


Index

Aaccount field 61account tree 17Action Reason Map page 20, 22Action Reason Voluntary Flag report 23Action Type page 20–21additional documentation xage groups, defining 63application fundamentals ixauthor flat file definition 82

Bbase currenciesbase currency equivalent amounts(BCEs) 6in PeopleSoft Workforce Analytics 5

BCEs (base currency equivalents) 6Benchmark Survey file 90benefit plan types 29benefits enrollment history data 46Benefits Valuation Map report page 35Benefits Valuation Map setup page 34benefits, source tables mapping 27Build Workforce Groups process 111, 116business units 5

Ccomments, submitting xiiicommon elements xiiicompensation classes 61Compensation Code Map page 77Compensation Code page 61compensation code tree 17compensation codes, mapping 26compensation datareport descriptions 35

Compensation Deduction Map setuppage 29Compensation Earnings Map setuppage 32Compensation GP Pin Map setup page 33compensation history data,understanding 49compensation survey flat file definition 87competency data

understanding 47competency tree 18Consolidated Publications Incorporated(CPI) xcontact information xiiicountry-specific documentation xiicross-references xiiCrystal reports 119Crystal reports, report descriptions 119currencycodes 5processing conversions 6

Customer Connection Website x

Ddata warehouse tables 36external survey data 68overview 37

DataMapsdelivered 10setting up 10

deductions, source tables, mapping 27department (financials-related) tree 18department data, viewing and editing 58Department Table page 58dimension and reference tablesaccess pages 50data 49reivewing and editing 72

dimension flat file definition 83documentationcountry-specific xiiprinted xrelated xupdates x

Duration Group page 63

Eearnings, source tables mapping 27employeebenefits history 46compensation history data 49

Employee Survey file 92Enterprise Warehouse setup 1ETL maps


Index

delivered 68importing internal source data 13

ETL processload survey data ETL batch 79ongoing survey data ETL batch 80setup external survey data batch 72

external survey datacompleting survey mappingdefinitions 73Crystal reports 80flat file definitions 71, 81importing 65load ETL batch 79ongoing ETL batch 80providers, accessing 66reviewing online 78reviewing sources 66setup 67setup ETL batch 72survey ETL batches, understanding 72viewing and editing survey dimensionand reference tables 72

FFinancial Code Map page 78Financial Code page 62FINCODE tree 18FINCODE tree, defining nodes 62flat file definitionauthor 82benchmark survey 90compensation survey 87dimension 83employee survey 92survey instance 85valid values for selected fields 93

flat file definitions, external surveydata 71

Ggeography ID codesmapping locations 23setting up 58

Geography ID Map page 77Geography ID Map report page 25Geography ID Map setup page 24Geography ID/Location Mapping Crystalreport 25Geography page 58geography tree 18glossary 121

IIndustry Code Map page 77Industry Code page 62INDUSTRY tree 19INDUSTRY tree, defining nodes 62internal source dataloading 13overview 13reviewing ETL maps 13source tables to data warehousetables 36

JJob Code Map page 76Job Code page 59job data, understanding 48job IDs, delivered 10JOBCODE tree 19JOBCODE tree, defining details 59jobstream IDs, delivered 10

LLocation page 60

Mmaps, ETL 68model ID creation 10

Nnotes xii

OOperator Defaults page 65organization (department) tree 19

PPeopleBooksordering x

PeopleCode, typographicalconventions xiPeopleSoft application fundamentals ixPersonal Data component 59personal names, importing 60personnel action data, loading 23personnel actionsdefining 21mapping for JOB_F00 20

plan values, mapping 26Position page 60position tree 20


Index

prerequisites ixprinted documentation x

Rrelated documentation xreports 119Benefit Value Table (WAC0003) 35descriptions 119Workforce Groups 110

SSalary Grade page 61Salary Step page 61scenario ID creation 10Security process 116service groups, defining 63SetIDs 5source tables, reviewing 27staffing data, understanding 48suggestions, submitting xiiisurvey instance flat file definition 85Survey Providers page 66

TTableMapsdelivered 10setting up 10

tables, data warehouse 37Termination Reason Map report page 23terms 121treesaccount 17compensation code 17competency 18department (financials-related) 18FINCODE 18geography 18INDUSTRY 19JOBCODE 19organization (department) 19position 20setting up 14understanding 14UNITCODE 20used 15

typographical conventions xi

UUnit Code Map page 78

Unit Code page 62UNITCODE tree 20UNITCODE tree, defining nodes 62

Vvisual cues xiivoluntary termination flag field 48

WWA Group Set process 116warnings xiiiWorkforce Group - Notes page 110Workforce Group page 109Workforce Group report page 111workforce group setsdefining 114manually defined 115organization tree based 115output tables 116overview 107position table based 115setting up 107

Workforce Group Sets page 114workforce groupsoutput tables 116overview 107running group, group set, and securityprocesses 116running the build processes 111scenario processes using 111setting up 107

Workforce Groups Crystal report(WAC0018) 110Workforce Groups inquiry page 112Workforce Trees setup page 75


Documents

PeopleSoft 8.8 Setting Up Workforce Analytics Applications ... · Setting Up Workforce Analytics Applications PeopleBook ... market,isprecededbyathree-lettercodeinparentheses. ThecodefortheU.S.federalgovernmentisUSF;