Object Relationships

Overview

This page documents the relationships between core PeopleSoft metadata objects—fields, records, pages, components, menus, portal content references, Component Interfaces, Integration Broker definitions, Application Engine programs, Query Security Trees, BI Publisher reporting, Fluid UI, Related Content, File Layouts, Application Data Sets, and security definitions—and their underlying PeopleTools database tables.

PeopleSoft metadata is structured as an object hierarchy where granular data definitions build upward into visual pages, transaction components, menu structures, and portal navigation links. Security grants wrap around components, menus, Component Interfaces, web services, and portal content references to determine runtime user authorization.

Core Application Metadata Stack

The core application metadata stack consists of six object types:

1. Fields (PSDBFIELD): Define atomic data attributes including field name, data type, length, decimal precision, and label definitions (PSDBFLDLABL).
2. Records (PSRECDEFN, PSRECFIELD): Group fields into logical record definitions mapped to physical SQL tables (RECTYPE = 0), SQL views (RECTYPE = 1), derived work buffers (RECTYPE = 2), subrecords (RECTYPE = 3), dynamic views (RECTYPE = 5), query views (RECTYPE = 6), or temporary tables (RECTYPE = 7).
3. Pages (PSPNLDEFN, PSPNLFIELD): Define user interface screens containing visual controls (edit boxes, drop-down lists, check boxes, scroll areas, grids) bound to specific record fields.
4. Components (PSPNLGRPDEFN, PSPNLGROUP): Group one or more pages into a complete online business transaction. Every component relies on a primary search record (SEARCHRECNAME) to drive key selection and search dialogs.
5. Menus (PSMENUDEFN, PSMENUITEM): Organize components into logical menu bars (BARNAME) and menu items (ITEMNAME).
6. Portal Content References / CREFs (PSPRSMDEFN): Define navigation nodes, URLs, content providers (PORTAL_CNTPRV_NAM), and parent folders in the portal registry tree.

flowchart TD
    Field["Field (PSDBFIELD)"] -->|Included in| RecordField["Record Field (PSRECFIELD)"]
    RecordField -->|Belongs to| Record["Record (PSRECDEFN)"]
    Record -->|Bound to Controls| PageField["Page Control (PSPNLFIELD)"]
    PageField -->|Placed on| Page["Page (PSPNLDEFN)"]
    Page -->|Included in| ComponentPage["Component Page (PSPNLGROUP)"]
    ComponentPage -->|Belongs to| Component["Component (PSPNLGRPDEFN)"]
    Record -->|Primary Search Record| Component
    Component -->|Target of| MenuItem["Menu Item (PSMENUITEM)"]
    MenuItem -->|Belongs to| Menu["Menu (PSMENUDEFN)"]
    MenuItem -->|URI Segments| CREF["Portal Content Reference (PSPRSMDEFN)"]
    Menu -->|Parent Menu| CREF

Security & Authorization Architecture

Security in PeopleSoft governs access to components, menu items, Component Interfaces, web services, and portal content references through five security layers:

1. User Accounts (PSOPRDEFN): Represent individual user accounts containing symbolic IDs, default local nodes, user class settings, and assigned roles.
2. User Roles (PSROLEUSER, PSROLEDEFN): Assign role definitions to users.
3. Permission Lists (PSROLECLASS, PSCLASSDEFN): Map permission list definitions to roles.
4. Menu & Component Authorizations (PSAUTHITEM): Authorize specific actions (Get, Add, Update/Display, Update/Display All, Correction) granted by permission lists for menu items and components.
5. Portal Permissions (PSPRSMPERM): Grant permission lists (PORTAL_PERMTYPE = 'P') or roles (PORTAL_PERMTYPE = 'R') access to portal folders and content references.

flowchart TD
    User["User ID (PSOPRDEFN)"] -->|Assigned Roles| RoleUser["User Role Assignment (PSROLEUSER)"]
    RoleUser -->|Maps to| Role["Role Definition (PSROLEDEFN)"]
    Role -->|Includes Classes| RoleClass["Role Class Grant (PSROLECLASS)"]
    RoleClass -->|Maps to| PermList["Permission List (PSCLASSDEFN)"]
    PermList -->|Grants Actions| AuthItem["Authorized Item (PSAUTHITEM)"]
    AuthItem -->|Target Menu & Item| MenuItemSec["Menu Item (PSMENUITEM)"]
    MenuItemSec -->|Target Component| ComponentSec["Component (PSPNLGRPDEFN)"]
    PermList -->|CREF Grant| PortalPerm["Portal Permission (PSPRSMPERM)"]
    Role -->|CREF Grant| PortalPerm
    PortalPerm -->|Authorizes Access| CREFSec["Portal Content Reference (PSPRSMDEFN)"]

Component Interface (CI) Architecture & Security

Component Interfaces expose online components (PSPNLGRPDEFN) for external API invocation, Excel-to-CI batch loads, and web service integrations:

• CI Definitions (PSBCDEFN): Define Component Interface metadata, pointing to a target underlying component (PNLGRPNAME, MARKET) and primary search record.
• CI Properties & Keys (PSBCITEM): Map exposed Component Interface properties, collections, methods, and parameters to page controls and record fields on the underlying component.
• CI Security Grants (PSAUTHBUSCOMP): Authorize permission lists (CLASSID) to execute specific Component Interface actions (AUTHORIZEDACTIONS bitmask: Get, Create, Save).

flowchart TD
    CIDefn["Component Interface (PSBCDEFN)"] -->|Exposes Component| TargetComp["Component (PSPNLGRPDEFN)"]
    CIDefn -->|Contains Properties| CIItem["CI Property / Key (PSBCITEM)"]
    CIItem -->|Maps to| RecFieldCI["Record Field (PSRECFIELD)"]
    PermListCI["Permission List (PSCLASSDEFN)"] -->|Grants CI Access| CISec["CI Security (PSAUTHBUSCOMP)"]
    CISec -->|Target CI| CIDefn
    RoleCI["Role (PSROLEDEFN)"] -->|Includes Class| PermListCI
    UserCI["User (PSOPRDEFN)"] -->|Assigned Role| RoleCI

Integration Broker (IB) Architecture & Web Services Security

Integration Broker manages synchronous and asynchronous messaging, REST and SOAP web services, routings, handlers, and external message nodes:

• Services (PSSERVICE): Logical groupings of related service operations.
• Service Operations (PSOPERATION): Individual operations defining operation type (Asynchronous One-Way, Asynchronous Read-Sub, Synchronous, REST), message body definitions, and default versions.
• Operation Versions (PSOPRVERDFN): Versioned definitions of service operations mapping request and response messages.
• Routings (PSIBRTNGDEFN): Directional communication rules mapping sender nodes to receiver nodes, specifying transformations and transport connectors.
• Handlers (PSOPRHDLR): Code execution units (Application Classes or App Engines) that process incoming or outgoing service operation messages.
• Message Nodes (PSMSGNODEDEFN): External system or local environment connection targets.
• Queues (PSQUEUEDEFN): Asynchronous execution queues governing message sequencing and concurrency.
• Web Service Security (PSAUTHWS): Authorizes permission lists (CLASSID) to execute specific Service Operations (IB_OPERATIONNAME) within a Service (IB_SERVICE_NAME).

flowchart TD
    ServiceIB["Service (PSSERVICE)"] -->|Groups| OperationIB["Service Operation (PSOPERATION)"]
    OperationIB -->|Defines Version| VersionIB["Operation Version (PSOPRVERDFN)"]
    VersionIB -->|Configures Routing| RoutingIB["Routing (PSIBRTNGDEFN)"]
    VersionIB -->|Binds Handler| HandlerIB["Handler (PSOPRHDLR)"]
    RoutingIB -->|Sends / Receives| NodeIB["Message Node (PSMSGNODEDEFN)"]
    OperationIB -->|Processes via| QueueIB["Queue (PSQUEUEDEFN)"]
    PermListIB["Permission List (PSCLASSDEFN)"] -->|Grants Web Service| WSSec["Web Service Security (PSAUTHWS)"]
    WSSec -->|Target Operation| OperationIB
    RoleIB["Role (PSROLEDEFN)"] -->|Includes Class| PermListIB
    UserIB["User (PSOPRDEFN)"] -->|Assigned Role| RoleIB

Application Engine Architecture & Action Types

Application Engine programs handle batch data processing, interface file generation, and system background processing:

• Program Header (PSAEAPPLDEFN): Program definition header specifying program type, disable restart flag, and target database type.
• State Records (PSAEAPPLSTATE): Assigned state records maintaining in-memory rowset state and runtime process parameters.
• Temporary Tables (PSAEAPPLTEMPTBL): Dedicated temporary tables assigned for parallel batch processing.
• Sections (PSAESECTDEFN): Executable code containers composed of ordered steps.
• Steps (PSAESTEPDEFN): Individual execution steps containing actions.
• Actions (PSAESTMTDEFN): The statement actions evaluated within a step. Action types (AE_STMT_TYPE) include:
  • S (SQL): Executes SQL statements.
  • P (PeopleCode): Executes Application Engine PeopleCode.
  • C (Call Section): Calls another Application Engine section.
  • D (DoSelect): Executes child steps for each row returned by a SELECT query.
  • W (Do While): Loops child steps while a SQL condition evaluates to true.
  • N (Do Until): Loops child steps until a SQL condition evaluates to true.
  • H (Do When): Executes child steps conditionally based on SQL result.
  • X (XSLT): Applies XML transformations.
  • M (Log Message): Writes log messages to the execution report.

flowchart TD
    PrcsAE["Process Definition (PRCSDEFN)"] -->|Invokes Program| AppEngine["App Engine Program (PSAEAPPLDEFN)"]
    AppEngine -->|Assigns State| StateRec["State Record (PSAEAPPLSTATE)"]
    AppEngine -->|Allocates Temp Tables| TempTbl["Temp Table Instance (PSAEAPPLTEMPTBL)"]
    AppEngine -->|Contains Sections| Section["AE Section (PSAESECTDEFN)"]
    Section -->|Contains Steps| Step["AE Step (PSAESTEPDEFN)"]
    Step -->|Executes Action| Action["AE Action (PSAESTMTDEFN)"]
    Action -->|SQL Action (S)| SQLObj["SQL Statement (PSSQLDEFN)"]
    Action -->|PeopleCode Action (P)| PCProg["PeopleCode (PSPCMPROG)"]
    Action -->|Call Section (C)| SubSection["Target AE Section (PSAESECTDEFN)"]
    Action -->|DoSelect / Loops (D,W,N,H)| ChildStep["Child AE Steps (PSAESTEPDEFN)"]

Query Security Trees & BI Publisher (XMLP) Pipeline

PeopleSoft Query definitions interface with Query Security Trees for record authorization, and feed data into BI Publisher templates for document generation:

• Query Access Trees (PSTREEDEFN, PSTREENODE, PSTREELEAF): Hierarchical record structures organizing records into query access groups. Permission lists (PSCLASSDEFN) are granted access to specific tree nodes.
• Query Definitions (PSQRYDEFN, PSQRYRECORD): Queries selecting record data filtered by query tree security grants.
• Connected Queries (PSCONQRSDEFN, PSCONQRSMAP): Hierarchical structures linking multiple queries into a single nested XML payload.
• BI Publisher Data Sources (PSXPDATASRC): Data source definitions wrapping PS Queries, Connected Queries, or XML files.
• Report Definitions (PSXPRPTDEFN, PSXPTMPLDEFN): Report definitions linking data sources to RTF, PDF, or Excel templates (PSXPTMPLFILEDEF).

flowchart TD
    PermListTree["Permission List (PSCLASSDEFN)"] -->|Grants Access Group| QueryTree["Query Tree Node (PSTREENODE)"]
    QueryTree -->|Exposes Record| RecordQry["Record Definition (PSRECDEFN)"]
    RecordQry -->|Used in Query| PSQuery["PS Query (PSQRYDEFN)"]
    PSQuery -->|Nested in| ConnQuery["Connected Query (PSCONQRSDEFN)"]
    PSQuery -->|Data Source for| BIPDataSrc["BIP Data Source (PSXPDATASRC)"]
    ConnQuery -->|Data Source for| BIPDataSrc
    BIPDataSrc -->|Feeds Report| BIPReport["BIP Report Defn (PSXPRPTDEFN)"]
    BIPReport -->|Applies Template| BIPTemplate["RTF / PDF Template (PSXPTMPLDEFN)"]
    BIPTemplate -->|Generates Output| OutputDoc["PDF / Excel Document"]

Fluid UI Framework & Related Content Framework

Fluid UI definitions and Related Content services deliver responsive navigation tiles and contextual sidebar panels:

• Fluid Components (FLUIDMODE = 1): Components designed for responsive layout across desktop and mobile devices.
• Portal Tile Attributes (PSPRSMSYSATTRVL): System attribute key/value pairs attaching Fluid tile properties (ALLOW_NAVBAR_TILES, PORTAL_HIDE_FROM_NAV) to content references (PSPRSMDEFN).
• Related Content Services (PSPTCSSRVDEFN): Service definitions specifying target components, iScripts, or external URLs for contextual display.
• Related Content Configurations (PSPTCS_SRVCFG, PSPTCS_MAPFLDS): Configuration mappings linking target related content services to specific host component fields and keys.

flowchart TD
    CREFFluid["Fluid Content Ref (PSPRSMDEFN)"] -->|Configures Tile| TileAttr["Tile Attributes (PSPRSMSYSATTRVL)"]
    CREFFluid -->|Opens Component| CompFluid["Fluid Component (PSPNLGRPDEFN)"]
    CompFluid -->|Hosts Sidebar| RCConfig["Related Content Config (PSPTCS_SRVCFG)"]
    RCConfig -->|Maps Keys| RCMap["Field Mapping (PSPTCS_MAPFLDS)"]
    RCMap -->|Invokes Service| RCService["Related Content Service (PSPTCSSRVDEFN)"]
    RCService -->|Loads Target| TargetSrv["Target Component, iScript, or URL"]

File Layouts & Application Data Sets (ADS)

File Layouts and Application Data Sets manage flat-file interface parsing and structured data migration definitions:

• File Layout Definitions (PSFLDDEFN): Master file layout definitions specifying file format (CSV, Fixed Position, XML), record delimiters, and qualifiers.
• File Layout Segments (PSFLDSEGDEFN): Segment definitions mapping record ID prefixes to underlying target records (RECNAME_FILE).
• File Layout Fields (PSFLDFIELDDEFN): Field mappings defining start positions, lengths, data types, and date format masks.
• Application Data Sets (PSADSDEFN, PSADSOBJDEFN): Data set definitions defining hierarchical record trees for project-based data migrations.

flowchart TD
    FileInput["Flat File (CSV / Fixed / XML)"] -->|Parsed by| FileLayout["File Layout (PSFLDDEFN)"]
    FileLayout -->|Contains Segments| FileSeg["File Segment (PSFLDSEGDEFN)"]
    FileSeg -->|Maps Fields| FileFld["File Field (PSFLDFIELDDEFN)"]
    FileFld -->|Populates Record| TargetRec["Target Record (PSRECDEFN)"]
    TargetRec -->|Grouped in Data Set| ADSDefn["ADS Definition (PSADSDEFN)"]
    ADSDefn -->|Includes ADS Objects| ADSObj["ADS Object (PSADSOBJDEFN)"]

PeopleCode Binding Architecture

PeopleCode programs bind to metadata definitions through key schemes stored in PSPCMPROG, PSPCMTXT, and PSPCMNAME. The OBJECTID1 column in PSPCMPROG identifies the parent object type that owns the code:

• Record PeopleCode (OBJECTID1 = 1): Attached to record fields. Stores events like FieldChange, RowInit, SaveEdit, and FieldFormula.
• Menu PeopleCode (OBJECTID1 = 3): Attached to menu items for ItemSelected events.
• Page PeopleCode (OBJECTID1 = 9): Attached to pages for page activate events.
• Component PeopleCode (OBJECTID1 = 10): Attached to components at the component level (OBJECTID3 = 12), component record level (OBJECTID3 = 1), or component record-field level (OBJECTID3 = 1 with OBJECTID4 = 2).
• Application Engine PeopleCode (OBJECTID1 = 66): Attached to Application Engine step actions.
• Component Interface PeopleCode (OBJECTID1 = 74): Attached to Component Interface properties and methods.
• Application Package PeopleCode (OBJECTID1 = 104): Attached to Application Package classes and methods.

The PSPCMNAME table stores every object reference parsed from PeopleCode programs, enabling bidirectional cross-referencing between source code and metadata definitions.

flowchart TD
    PCodeProg["PeopleCode Program (PSPCMPROG / PSPCMTXT)"] -->|OBJECTID1 = 1| RecPCode["Record Field Event (PSRECFIELD)"]
    PCodeProg -->|OBJECTID1 = 10| CompPCode["Component Event (PSPNLGRPDEFN)"]
    PCodeProg -->|OBJECTID1 = 9| PagePCode["Page Event (PSPNLDEFN)"]
    PCodeProg -->|OBJECTID1 = 66| AEPCode["App Engine Action (PSAESTEPDEFN)"]
    PCodeProg -->|OBJECTID1 = 104| AppPkgPCode["App Package Method (PSPACKAGEROOT)"]
    PCodeProg -->|References Tracked in| PCodeRef["Cross Reference (PSPCMNAME)"]
    PCodeRef -->|Target Object| RefTarget["Referenced Field, Record, Component, or SQL"]

Process Scheduler & Query Wiring

Process Scheduler definitions and PeopleSoft Query definitions interface with records and components:

• Process Definitions (PRCSDEFN): Map batch processes (Application Engines, SQR, COBOL, BI Publisher) to parent process types (PRCSTYPE) and target components (PRCSDEFNPNL). Process groups (PRCSDEFNGRP) control user authorization to run processes from specific components.
• PeopleSoft Queries (PSQRYDEFN): Query definitions reference record definitions (PSQRYRECORD) and selected fields (PSQRYFIELD). Access to record data within Query Manager is governed by Query Security Trees (PSTREENODE), which are granted to permission lists (PSCLASSDEFN).

flowchart TD
    PrcsDefn["Process Definition (PRCSDEFN)"] -->|Runs from Component| PrcsPnl["Process Component (PRCSDEFNPNL)"]
    PrcsPnl -->|Target Component| CompPrcs["Component (PSPNLGRPDEFN)"]
    PrcsDefn -->|Grouped in| PrcsGrp["Process Group (PRCSDEFNGRP)"]
    QueryDefn["Query Definition (PSQRYDEFN)"] -->|Selects Records| QueryRec["Query Record (PSQRYRECORD)"]
    QueryRec -->|Points to| RecordQry["Record Definition (PSRECDEFN)"]
    RecordQry -->|Tree Access Controlled by| QueryTree["Query Tree Node (PSTREENODE)"]
    PermListQry["Permission List (PSCLASSDEFN)"] -->|Grants Tree Access| QueryTree

PeopleTools Table Reference

The table below lists the primary PeopleTools database tables and primary key structures for major metadata and security objects.

Security Evaluation Logic

When a user accesses an online component, Component Interface, web service, or portal content reference, PeopleSoft evaluates authorization through a multi-tier resolution path:

Top-Down User Authorization Evaluation

1. The runtime engine identifies the user’s OPRID in PSOPRDEFN.
2. PSROLEUSER fetches all roles assigned to OPRID.
3. PSROLECLASS collects all permission lists (CLASSID) mapped to those roles.
4. PSAUTHITEM verifies if any collected permission list grants authorized actions for the requested MENUNAME, BARNAME, and ITEMNAME.
5. PSAUTHBUSCOMP checks whether the user’s permission lists authorize Component Interface actions for a requested BCNAME.
6. PSAUTHWS checks whether the user’s permission lists authorize execution of a requested Service (IB_SERVICE_NAME) and Operation (IB_OPERATIONNAME).
7. PSPRSMPERM checks whether the user’s permission lists or roles authorize access to the target portal content reference (PORTAL_OBJNAME).

Bottom-Up Security Audit Path

To audit which users hold access to a specific component, CI, or web service:

1. Components: Identify the menu item (PSMENUITEM) pointing to PNLGRPNAME, query PSAUTHITEM for permission lists (CLASSID), query PSROLECLASS for roles, and query PSROLEUSER for assigned users.
2. Component Interfaces: Query PSAUTHBUSCOMP for permission lists with non-zero AUTHORIZEDACTIONS on BCNAME, then resolve roles (PSROLECLASS) and users (PSROLEUSER).
3. Integration Broker Web Services: Query PSAUTHWS for permission lists authorized for IB_SERVICE_NAME and IB_OPERATIONNAME, then resolve roles (PSROLECLASS) and users (PSROLEUSER).