Home > Glossary > PeopleSoft Terms

PeopleSoft Terms

Back to Glossary Main Menu

accounting date control table pending item Short Description Field
activity Description Field PeopleCode SmartKey
Application Messaging dynamic detail tree Process Monitor
branch Effective Date project transaction Status
budget check EmplID record group subcustomer qualifier
budget control group regional sourcing summary ledger
budget period integration Report ID summary tree
budgetary account only integration point Report Manager system function
business unit item Request ID TableSet sharing
buyer Journal role third party
Category location role user TimeSpan
ChartField multicurrency roll up Translate table
ChartField balancing node-oriented tree Run tree
ChartField combination edit origin code Run Control ID User ID
ChartKey pay cycle SetID worklist

accounting date

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

activity

In PeopleSoft Project Costing, the unit of work that provides a further breakdown of projects—usually into specific tasks.

In PeopleSoft Workflow, a specific transaction that you might need to perform in a business process. Because it consists of the steps that are used to perform a transaction, it is also known as a step map.

Application Messaging

PeopleSoft Application Messaging enables applications within the PeopleSoft Enterprise product family to communicate synchronously or asynchronously with other PeopleSoft and third-party applications. An application message defines the records and fields to be published or subscribed to. This is all about interfaces of all the systems at the U.

branch

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

budget check

In Commitment Control, the processing of source transactions against control budget ledgers, to see if they pass, fail, or pass with a warning.

budget control

In Commitment Control, budget control ensures that commitments and expenditures don't exceed budgets. It enables you to track transactions against corresponding budgets 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 if there 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 divided for budgetary and reporting purposes. The ChartField allows maximum flexibility to define operational accounting time periods without restriction to only one calendar.

budgetary account only

An account used by the system only and not by users; this type of account does not accept transactions. You can only budget with this account. Formerly called “system-maintained account.”

business unit

An organizational entity that maintains its own transactions. This is the working definition for defining the General Ledger business unit.

In the other subsystems a business unit is an operational subset of an organization that enables you to plan operations based on the way the organization functions. This means we can have multiple business units in the subsystems based on the business practices of the universities units.

buyer

In PeopleSoft eSettlements, an organization (or business unit, as opposed to an individual) that transacts with suppliers (vendors) within the system. A buyer creates payments for purchases that are made in the system.

Category

ChartField value that represents the category for a project transaction in Project Costing. A category further defines a source type. For example, if you have a source type of labor, you might have categories for architect labor, carpenter labor, and plumber labor. This field is available only if you have Project Costing.

ChartField

In PeopleSoft applications, the fields that store your charts of accounts and provide your system with the basic structure to segregate and categorize transactional and budget data are called ChartFields. Each ChartField has its own attributes for maximum efficiency and flexibility in recording, reporting and analyzing its intended category of data. While a particular ChartField always represents only one category of data, it stores many values that you use to further categorize that same data.

ChartField balancing

Business unit or a ChartField is said to be balancing when you require debit amounts to equal credit amounts to maintain a balanced set of accounts for the particular business unit or ChartField. The U will use Fund and DeptID for its balancing ChartFields.

ChartField combination edit

The process of editing journal lines for valid ChartField combinations based on user-defined rules.  If the distribution string is not valid, the user will receive an error message at save time in the subsystems while the Edit Process will need to be run if the Journal Entry originated from the General Ledger.

ChartKey

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

control table

Stores information that controls the processing of an application. This type of processing might be consistent throughout an organization, or it might be used only by portions of the organization for more limited sharing of data. SetID is one of the key label to most control tables.

Description Field

Freeflow text up to 30 characters.

dynamic detail tree

A tree that takes its detail values—dynamic details—directly from a table in the database, rather than from a range of values that are entered by the user.

Effective Date

Date on which a table row becomes effective; the date that an action begins. For example, if you want to close out a ledger on June 30, the effective date for the ledger closing would be July 1. This date also determines when you can view and change the information. Pages or panels and batch processes that use the information use the current row. . By using effective dates, you don't delete values; you enter a new value with a current effective date.

EmplID (employee ID)

Unique identification code for an individual associated with the U.

group

In PeopleSoft Billing and Receivables, a posting entity that comprises one or more transactions (items, deposits, payments, transfers, matches, or write-offs).
In PeopleSoft Human Resources Management and Supply Chain Management, any set of records that are associated under a single name or variable to run calculations in PeopleSoft business processes. In PeopleSoft Time and Labor, for example, employees are placed in groups for time reporting purposes.

integration

A relationship between two compatible integration points that enables communication to take place between systems. Integrations enable PeopleSoft applications to work seamlessly with other PeopleSoft applications or with third-party systems or software.

integration point

An interface that a system uses to communicate with another PeopleSoft application or an external application.

item

In PeopleSoft Inventory (Purchasing), a tangible commodity that is stored in a business unit (The U currently calls this a Part).
In PeopleSoft Receivables, an individual receivable. An item can be an invoice, a credit memo, a debit memo, a write-off, or an adjustment.

Journal

Created when you edit journal lines (accounting entries) online in PeopleSoft General Ledger or you run the Journal Generator process for subsystem, imported, or batch accounting entries.

location

Locations enable you to indicate the different types of addresses—for a company, for example, 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. The primary location—indicated by a 1—is the address you use most often and may be different from the main address.

multicurrency

The ability to process transactions in a currency other than the business unit's base currency.

node-oriented tree

A tree that is based on a detail structure, but the detail values are not used.

origin code The bill-to location for vendor payments. When a requisition is processed, the bill-to address on the purchase order is equal to the original code. This tells the vendor where to send their invoice.

pay cycle

In PeopleSoft Payables, a set of rules that define the criteria by which it should select scheduled payments for payment creation.

pending item

In PeopleSoft Receivables, an individual receivable (such as an invoice, a credit memo, or a write-off) that has been entered in or created by the system, but hasn't been posted.

PeopleCode

PeopleCode is a proprietary language, executed by the PeopleSoft component processor. PeopleCode generates results based on existing data or user actions. By using various tools provided with PeopleTools, external services are available to all PeopleSoft applications wherever PeopleCode can be executed.

Process Monitor

This link takes you to the Process List page, where you can view the status of submitted process requests.

project transaction

In PeopleSoft Project Costing, an individual transaction line that represents a cost, time, budget, or other transaction row.

record group

A set of logically and functionally related control tables and views. Record groups help enable TableSet sharing, which eliminates redundant data entry. Record groups ensure that TableSet sharing is applied consistently across all related tables and views.

regional sourcing

In PeopleSoft Purchasing, provides the infrastructure to maintain, display, and select an appropriate vendor and vendor pricing structure that is based on a regional sourcing model where the multiple ship to locations are grouped. Sourcing may occur at a level higher than the ship to location.

Report ID

The report identifier.

Report Manager

This link takes you to the Report List page, where you can view report content, check the status of a report, and see content detail messages (which show you a description of the report and the distribution list).

Request ID

A request identification that represents a set of selection criteria for a report or process.

role

Describes how people fit into PeopleSoft Workflow. A role is a class of users who perform the same type of work, such as clerks or managers. Your business rules typically specify what user role needs to do an activity.

role user

A PeopleSoft Workflow user. A person's role user ID serves much the same purpose as a user ID does in other parts of the system. PeopleSoft Workflow uses role user IDs to determine how to route worklist items to users (through an email address, for example) and to track the roles that users play in the workflow. Role users do not need PeopleSoft user IDs.

roll up

In a tree, to roll up is to total sums based on the information hierarchy.

Run

This button takes you to the Process Scheduler request page, where you can specify the location where a process or job runs and the process output format.

Run Control ID

A request identification that represents a set of selection criteria for a report or process.

SetID

An identification code that represents a set of control table information or TableSets. A TableSet is a group of tables (records) necessary to define your company’s structure and processing options.

Short Description Field

Freeflow text up to 15 characters.

SmartKey

A user-defined shorthand key that designates several ChartKeys to be used for voucher entry.

Status

Indicates if a row in a table is active or inactive. You cannot display inactive rows or pages or use them for running batch processes. Use inactive rather than delete data you no longer use in order to maintain an audit trail.

subcustomer qualifier

A value that groups customers into a division for which you can generate detailed history, aging, events, and profiles.

summary ledger

An accounting feature used primarily in allocations, inquiries, and PS/nVision reporting to store combined account balances from detail ledgers. Summary ledgers increase speed and efficiency of reporting by eliminating the need to summarize detail ledger balances each time a report is requested. Instead, detail balances are summarized in a background process according to user-specified criteria and stored on summary 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. Summary trees enable you to define trees on trees. In a summary tree, the detail values are really nodes on a detail tree or another summary tree (known as the basis tree). A summary tree structure specifies the details on which the summary trees are to be built.

system function

In PeopleSoft Receivables, an activity that defines how the system generates accounting entries for the general ledger.

TableSet sharing

Shared data that is stored in many tables that are based on the same TableSets. Tables that use TableSet sharing contain the SETID field as an additional key or unique identifier.

third party

A company or vendor that has extensive PeopleSoft product knowledge and whose products and integrations have been certified and are compatible with PeopleSoft applications.

TimeSpan

A relative period, such as year-to-date or current period, that can be used in various PeopleSoft General Ledger functions and reports when a rolling time frame, rather than a specific date, is required. TimeSpans can also be used with flexible formulas in PeopleSoft Projects.

Translate table

A system edit table that stores codes and translate values for the miscellaneous fields in the database that do not warrant individual edit tables of their own.

tree

The graphical hierarchy in PeopleSoft systems that displays the relationship between all accounting units (for example, corporate divisions, projects, reporting groups, account numbers) and determines roll-up hierarchies.

User ID

The system identifier for the individual who generates a transaction.

worklist

The automated to-do list that PeopleSoft Workflow creates. From the worklist, you can directly access the pages you need to perform the next action, and then return to the worklist for another item.