Table of Contents

Search

  1. Preface
  2. Configuring PowerExchange for PeopleSoft
  3. Understanding PowerExchange for PeopleSoft
  4. Working with PeopleSoft Sources
  5. Application Source Qualifier for PeopleSoft Sources
  6. Accessing XLATTABLE Data
  7. Creating PeopleSoft Sessions and Workflows
  8. Appendix A: Datatype Reference
  9. Appendix B: PeopleSoft Language Codes
  10. Appendix C: Glossary

PowerExchange for PeopleSoft User Guide for PowerCenter

PowerExchange for PeopleSoft User Guide for PowerCenter

Tree Metadata

Tree Metadata

You can import tree metadata from the following PeopleSoft trees:
  • Detail trees
  • Summary trees
  • Winter trees
You import PeopleSoft tree metadata at different times, depending on whether you import or create the tree source definition.
When you import a PeopleSoft tree source definition, you connect to the PeopleSoft system to access the PeopleSoft metadata tables. The Designer uses metadata in these tables to create the source definition in the Source Analyzer. You cannot configure this metadata manually.
When you create a tree source definition, the Designer creates a source definition based on a predefined tree structure stored in the repository. Therefore, you do not see or import PeopleSoft tree metadata for the created tree source definition in the Source Analyzer. To associate PeopleSoft tree metadata with a created tree source definition, you import Peoplesoft tree attributes into the created tree source definition in the Mapping Designer.
The following table shows the PeopleSoft metadata the Designer imports when you import a tree in the Source Analyzer or when you import PeopleSoft tree attributes into a created tree source definition in the Mapping Designer:
Source Definition Field
Contains
Applicable Tree Source Definitions
Source Name
Tree name.
Created and imported
Business Name
Business name for the tree.
Imported
Owner Name
Owner of the tree.
Created and imported
Table Type
PeopleSoft object type (PeopleSoft tree, PeopleSoft winter tree, or PeopleSoft tree for vertical flattening).
Created and imported
SetID
A value that provides a unique identifier for each hierarchy. It is used to organize and identify data, such as MFG for Manufacturing. Each PeopleSoft tree has a SetID.
Created and imported
Effective Date
Effective date for the tree.
Created and imported
Tree Name
Name of the tree.
Created and imported
Detail Table Name
Detail record name. The field appears on the Attributes tab of the source definition when opened in the Mapping Designer.
Imported
Detail Field Name
Column in the detail record used to join the detail record with the detail tree. The field appears on the Attributes tab of the source definition when opened in the Mapping Designer.
Imported
Set Control Value
Additional identifier used by some versions of PeopleSoft to identify winter trees. The field appears on the Attributes tab of the source definition when opened in the Mapping Designer.
Created and imported
To add or view metadata for a created PeopleSoft tree source definition, open the Edit Transformations dialog box for the source definition in the Mapping Designer.
The following figure shows an imported source definition:
The PeopleSoft object type and PeopleSoft Tree appear in the Table Type field. The SetID (HC), tree name (HC_DEPARTMENTS), and effective date (01/01/1900) appear in the Description field. The PeopleSoft business name, Department Rollup, appears in the Business Name field.

0 COMMENTS

We’d like to hear from you!