Site Title

Integrating PeopleSoft with EDM Using Universal Adapter: A Practical Guide

Integrating PeopleSoft with Enterprise Data Management (EDM) using the Universal Adapter enables organizations to efficiently manage and synchronize hierarchical data. One key aspect of this integration is handling TreeMover structures, which play a critical role in defining dimension hierarchies.

In this blog, we’ll walk through how TreeMover structures are represented in EDM, how to configure viewpoints, and how to generate properly formatted import files for seamless data exchange.

Understanding TreeMover Structures in PeopleSoft

In PeopleSoft, each dimension is associated with one or more TreeMover structures.

• The number of TreeMovers varies by dimension.
• Each TreeMover represents a hierarchy.
• In EDM, each TreeMover is modeled as a separate viewpoint within a dimension.

Additionally, every TreeMover consists of seven distinct layouts (sections), each corresponding to specific PeopleSoft tables.

TreeMover File Layout Overview

Each TreeMover extract contains seven sections, structured as follows:

Section Name	Description
TREE_VERSION	Contains the PeopleTools release number used to create the export file
TREE_STRUCTURE	Data from PSTREESTRCT table
TREE_DEFN	Data from PSTREEDEFN table
TREE_USERLEVEL	Data from PS_TREE_LEVEL_TBL table
TREE_LEVEL	Data from PSTREELEVEL table
TREE_USERNODE	Data from PS_TREE_NODE_TBL table
TREE_NODE	Data from PSTREENODE and PSTREELEAF tables

Note: If a tree version is not provided, the import process assumes the data is from a pre-8.1.999 PeopleSoft database.

EDM Configuration for Multiple TreeMovers

Let’s consider a scenario where the Account dimension has three TreeMover structures, including a primary hierarchy.

Recommended EDM Setup

To model this in EDM:

Include all required header columns for extract generation

Create a single dimension

Example: Account

Create multiple viewpoints

One viewpoint for each TreeMover

Total: 3 viewpoints

Use a single Node Type

Ensures consistency across all viewpoints

Define properties in Node Type

Include all required header columns for extract generation

Member Import Strategy in EDM

Managing member actions correctly is crucial when working with multiple TreeMovers.

Primary TreeMover Viewpoint

• Members are added using Subscription
• Action Type: ADD

Alternate TreeMover Viewpoints

• Members are inserted based on specific conditions
• Action Type: INSERT
• Reason: Same Node Type is shared across viewpoints

This distinction ensures proper hierarchy handling and avoids conflicts during data processing.

PeopleSoft Import File Format Overview

The PeopleSoft import process requires a strict file format for successful data loading.

Key Characteristics

• The import file contains 7 sections
• Each section has a unique structure
• Each section must be generated separately in EDM

Best Practice

• Create 7 individual extracts (one per section)
• Bundle them into a single extract package
• Generate a consolidated output file

File Structure Requirements

Each section in the import file follows strict formatting rules:

Column Specifications

Every column has predefined:

• Length
• Starting position
• Ending position

Fixed-Width Formatting

PeopleSoft expects a fixed-width file format, meaning:

• Each field must match its exact length
• No deviation is allowed

• Each section contains unique column headers.
• Every column has predefined:
  • Length
  • Starting position
  • Ending position

Data Formatting Rules

• If a field value is shorter than the required column length, we must use padding to fill the remaining space.
• Padding ensures that all fields strictly adhere to the fixed-width format expected by PeopleSoft.

Data Formatting Rules

To meet PeopleSoft requirements:

• If a field value is shorter than the required length → apply padding
• Padding fills the remaining space to maintain alignment

Why Padding Matters

• Ensures data integrity
• Prevents import failures
• Maintains compatibility with PeopleSoft parsing logic

Conclusion

Integrating PeopleSoft TreeMover structures with EDM requires careful planning and strict adherence to file formatting rules. By:

• Structuring TreeMovers as viewpoints
• Using a consistent Node Type
• Managing member actions correctly
• Generating properly formatted extract files

you can ensure a smooth and reliable data integration process.