Name associated with the different kinds of accounts used in a PeopleSoft General Ledger, such as Asset, Liability, Equity, Revenue, and Expense.
The date a transaction is recognized as opposed to the date the transaction actually occurred-transaction date (although the two dates can be the same). 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.
Accounting Entry Template
A user-defined table that controls the use of system-generated accounting lines in the posting processes.
The ChartField by which you store data at the lowest level required for all budget items in PeopleSoft Budgets.
Application Journal Template
A set of rules and default values to control the creation of journals from accounting entries.
In a client/server environment, any task or process that is grouped with another and runs in the background. Background processes are usually scheduled to run on a regular basis. All background processes are executed through process-specific COBOL programs.
A tree node that rolls up to nodes above it in the hierarchy defined in the Tree Manager.
Budget Checking Module (BCM)
A Cobol program that updates recognized revenue and collected revenue with user-defined budget checking definitions.
A corporation or an organizational entity that maintains its own business activity. PeopleSoft General Ledger business units typically comprise individual entities for accounting purposes. PeopleSoft Payables business units are either Vouching (have payables accrued to them) or Charge to (have voucher expense distributions charged to them), and pass journals to general ledger units. PeopleSoft Purchasing business units share vendor, purchase order, and receiving information with PeopleSoft Payables units in the same SetID.
ChartField Combination Edit
Also called Combo Edit. The process of editing journal lines for valid ChartField combinations based on user-defined rules.
A node on a tree linked to another, higher-level node (referred to as the parent). A node can be a child and a parent at the same time depending on its location within the tree.
A mechanism to group vouchers together for the purpose of controlling voucher input into PeopleSoft Payables. Generally used for assigning vouchers to data entry personnel and for reviewing input.
The relationship between business units, origins, vendors, and control groups in PeopleSoft Payables that defines which processing data will be automatically entered on each voucher.
A tree that employs ranges of detail values under each node; you must specify the detail values.
The act of moving from the general to the specific. By drilling down you can examine the data underlying any summarized form of information in your PeopleSoft system. You can also drill down from one PeopleSoft system to other systems from which information was received.
A tree that takes its detail values-Dynamic Details-directly from a table in the database, rather than from a range of values.
A table on 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 an edit table to ensure data integrity throughout the system.
A method of dating information in your system. You can predate information to add historical data to your system, or postdate information in order to enter it before it actually goes into effect.
A batch of accounting entries entered online or input from a feeder system (payables, receivables, asset management, and so on) to the general ledger. Consists of multiple journal lines and one Journal Header, identified by the Journal ID. Information about the journal as a whole is stored in the Journal Header table.
Journal Generator Template
A table containing defaults to be used in journal generation.
A record storing a double-sided, balanced entry for a given journal. The sum of the monetary amounts for the journal lines in one journal totals zero (debits = credits).
A list of characteristics of the general ledger journal entries that will be created.
An identifier used to categorize conversations.
A set of posted balances that represent a set of books for a business unit. PeopleSoft General Ledger supports detail, multiple, and summary ledgers.
In PeopleSoft General Ledger, a group of ledgers consisting of one primary ledger and any number of secondary ledgers.
A table containing records and fields common to all ledgers that ensures that all ledgers specified in a ledger group share the same physical layout.
A section of a tree that organizes groups of nodes.
Locations enable you to indicate the different types of addresses a company has-for example, one to receive bills, another for shipping, a third for postal deliveries, and a separate street address. Each of these addresses has a different location number.
The process of applying system match control rules against voucher, purchase order, and receiver documents, ensuring that an invoice being entered reflects the amounts ordered and received before it is approved for payment.
An individual item on a tree. Nodes summarize detail values or other nodes, and may or may not roll up into other nodes or levels.
A PS/ nVision feature that enables you to expand rows and columns in your spreadsheet to underlying details, as in drilldown.
An entry point for transactions into a PeopleSoft system. Origins can designate both online and background interfaces and can be defined to have their own editing and default options.
A tree node linked to lower-level nodes or details that roll up into it.
A set of rules that define to PeopleSoft Payables the criteria by which it should select scheduled payments for payment creation.
A process by which PeopleSoft Payables selects scheduled payments that are eligible to be paid in a pay cycle.
The customer attribute that determines due dates, discount dates and amounts, and due and discount grace periods.
Payment Terms Timing
A definition of the time increments used in figuring payment terms.
The process by which accounting entries are created or updated based on user transaction input and accounting entry templates.
The number the system assigns each job that runs in background processing.
A process that performs tasks behind the scenes of your application. It can run several kinds of processes-COBOL, crystal-on a regular schedule or at your request, at your workstation or on a server.
Specifies a method of purchasing an item. Purchase options specify a vendor, associated lead times, and costs for this item.
A logical grouping of data elements.
A feature that creates multiple instances of an nVision report using a single report request. Each instance contains data specific to an individual ChartField, such as a business unit or department, or for a group of ChartFields, such as all sales departments. Using Scope, each report instance can share the same layout while containing data unique to these particular ChartFields.
The act of totaling sums based on information tree hierarchies. You can roll up data for any group of details that you have defined as dependent with the Tree Manager.
Run Control ID
Process run controls enable you to predefine parameters that are later used to a given process request.
The label that identifies a TableSet.
A tree node at the same level as another node, where both roll up into the same parent.
The Source table stores valid journal entry and posting sources. These can include job titles (such as CFO), operator IDs (such as CLERK123).
A user-defined shorthand key designating several chartkeys to be used for voucher entry. Percentages can optionally be related to each chartkey in a speedchart definition.
A code representing a combination of ChartField values. SpeedTypes simplify the entry of ChartFields when the same set is commonly used together.
Structured Query Report (SQR)
A type of printed or displayed report generated from data extracted from PeopleSoft. PeopleSoft applications provide a variety of standard SQRs that summarize table information and data. You can use these reports as is, customize them, or create your own.
An accounting feature used primarily in allocations, inquiries, and PS/nVision reporting to store combined account balances from detail ledgers. They increase the speed and efficiency of reporting by eliminating the need to summarize detail ledger balances each time a report is requested.
A tree used to roll up accounts for each type of report in summary ledgers. In a summary tree, the detail values are really nodes on a detail tree or another summary tree (known as the basis tree).
The underlying format in which data is stored by columns (fields) and rows (records, or instances).
A group of rows across control tables identified by the same SetID.
Relative periods, 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.
The date a transaction actually occurred as opposed to the date the transaction is recognized-the accounting date (although the two dates can be the same).
A system edit table that stores codes and translate values for the miscellaneous fields on the database that do not warrant individual edit tables of their own.
The graphical hierarchy in PeopleSoft systems that displays the relationship between all accounting units (e.g. corporate divisions, projects, reporting groups, account numbers) and determines roll-up hierarchies.
Unit of Measure (UOM)
A type of unit used for quantifying in PeopleSoft systems. Depending on the application, units of measure might describe dimensions, weights, volumes, or amounts of locations, containers, or business activities. Examples include inches, pounds, work hours, and standard cost dollars.