 Pre-encumbrance: Amount that you expect to spend, but which you have no legal obligation to spend. A requisition is a typical pre-encumbrance transaction. Encumbrance: Amount that you have a legal obligation to spend in the future. Issuance of a purchase order to a vendor is a typical encumbrance transaction.
 Planned: A free-form non-actuals amount. Can be used as a memo entry or an entry to estimate future spending. Can also be used to record third-party source transactions that precede pre-encumbrance documents. The latter usage requires defining a new source transaction type.
 Recognized Revenue: Revenue that you have booked and expect to receive.
 Business Unit: A business unit is an organizational entity which maintains its own transaction data.
 Transaction Tables: Transaction tables store data about day-to-day business activities. Transaction tables in PeopleSoft are keyed in by Business Unit.
 Control Tables: Control tables store information that define the accounting structure and processing rules that are used when transactions are entered into your PeopleSoft applications. Control tables include master lists such as customers, vendors, products, items, and chart of accounts. Control tables are static; they change only when you perform specific maintenance, appropriate to changes in your business policies. Most PeopleSoft tables are keyed by Table Set Identifier, rather than by Business Unit. In addition, most are effective-dated.
 TableSet Id: Most data recorded in control tables is stored by Table Set ID (also called as SetID). Whenever your enter information in control table, you must enter the SetID to establish the ownership of that information. A grouping of data that is keyed by the same SetID is called a TableSet.
 Record Groups: The control tables used by each of the financial and distribution applications are grouped by function into record groups. A record group is a set of logically and functionally related control tables and views. All tables in the same record group will have the same key on each table.
 Record Group Control: In the TableSet record group control panel, you specify which SetID you want a business unit to use for each record group. You can specify a single SetID for all Record Groups or a combination of any number of SetIDs.
 TableSet Sharing: TableSet sharing allows different business units to use, or share, the same control information.
