Common Elements
Field or Control |
Description |
---|---|
Associated Revenue |
The total amount of the revenue in the revenue budget associated with the budget. This displays either the collected or recognized revenue based on your selection on the Budget Definitions component. |
Available Budget |
For expenditure budgets, the amount available in the budget after deducting commitments and expenses from the budgeted amount. For revenue budgets, it is the revenue estimate amount less the recognized revenue amount. |
Budget Checking Header Status |
Also referred to as Budget Checking Status, Budget Header Status, and Budget Status. Records budget-checking results. Can be one of the following:
Note: This field is sometimes labeled Budget Header Status, but it is not the same as the Budget Header Status field when budgets are posted and although this field is sometimes labeled Budget Status, it is not the same as the Budget Status field that indicates whether a budget is open, closed, or on hold. See Understanding Exception Handling and Notification. See Understanding Entering and Posting Commitment Control Budget Journals. |
Budget Checking Process Status |
Records the results of a batch Budget Processor run. Can be one of the following:
|
Budget Header Status |
Updated by the Commitment Control Posting process. The status can be any one of the following:
|
Budget Close Status |
Also Budget Closed. Indicates whether the budget has been closed by the Budget Close COBOL process (FSPYCLOS). Status can be:
To change the status of a budget that has been closed by the Budget Close process, you must unclose the budget using that same process (FSPYCLOS). See Budget Close Status. |
Budget Status |
Also referred to as Status. Indicates whether the budget is Open, Closed, or on Hold.
Note: Budget status is applied manually. The Budget Close Status, on the other hand, is updated by Budget Close COBOL process (FSPYCLOS). See also Budget Checking Header Status. |
Budget Entry Type |
Select one of the following values:
|
Budgetary Only |
When you define a ChartField value and select this option, the ChartField value can be used for budget purposes only and is not available for recording actual transactional entries. This option is available for all fully configurable ChartFields, including DEPTID. You usually establish budget control using summary Budgetary Only ChartField values instead of establishing a budget for each detail transactional ChartField value. You then set up ChartField translation trees to roll up the detail transactional level ChartField values to the summary budgetary level values. |
Collected Revenue |
Commitment Control ledger type (amount type) for revenue that has been collected. |
Commitment Control Amount Type |
Determines which Commitment Control ledger is updated by the source transaction. Can be one of the following:
|
Commitment Control Transaction Date |
Activity Log date for the Commitment Control transaction. Also refer to the Commitment Control Transaction ID for additional related information. |
Commitment Control Transaction ID |
Activity Log transaction number for the Commitment Control transaction. When you budget-check a source transaction, the system creates activity lines, each of which can affect multiple budget definitions (ledger groups). The activity log creates a Commitment Control transaction ID and Commitment Control transaction date for each source transaction. The Commitment Control transaction ID and Commitment Control transaction date thus have a one-to-one correspondence with a source transaction, such as a single general ledger journal or a single voucher. |
Commitment Control Transaction Line |
The Commitment Control transaction line number has a one-to-one correspondence to a single source transaction line, such as a single general ledger journal line or single voucher line. See the Commitment Control Transaction ID for additional related information. |
Commitment Control Ledger Group |
A group of ledgers that comprise the structure of a control budget definition. Often used synonymously with budget definition. |
Commitment Control Options |
See Control Options. |
Control ChartField |
The key ChartField that the Budget Processor uses to determine whether or not to enforce budget-checking. For example, if you select DeptID as the control ChartField for the budget definition, you can then identify specific departments over which the Budget Processor enforces budgetary control using this budget definition and other departments which are exempt from budgetary control. |
Control Options |
Describes the degree of budgetary control:
|
Cumulative Cal (cumulative calendar) |
A budget period calendar that logically summarizes multiple budget periods in the Ruleset budget period calendar into single, larger periods. A calendar defined with annual budget periods, for example, can act as a cumulative calendar for a calendar defined with quarterly periods. Use to define a range of budget periods for cumulative budgeting. |
Derive Dates |
Select when cumulative budgeting is enabled if you want a cumulative calendar to define the range of budget periods that are available for cumulative budgeting. Deselect when cumulative budgeting is enabled if you want to enter a date range to define the range of budget periods that are available for cumulative budgeting. You enter cumulative date ranges on the Budget Attributes component or at budget entry. |
Dept (department) |
ChartField that indicates who is responsible for or affected by the transaction. |
Description |
Freeflow text up to 256 characters. |
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 information. Pages and batch processes that use the information use the current row. |
Encumbrance |
Commitment Control ledger type (amount type) for amounts that you are legally obliged to spend. Contracts and purchase orders are typical encumbrance transactions. |
Expense |
Commitment Control ledger (amount type) for actual expenditure amounts. |
Fiscal Year |
The fiscal year (twelve month period) in which the transaction takes place. |
Foreign Amount |
The amount in the entry currency. |
Fund |
ChartField that represents structural units for education and government accounting. |
Fund Affiliate |
ChartField used to correlate transactions between funds when using a singe intraunit account. |
Funding Source |
Amount to be spent that is allocated from expenditure and revenue budgets to a lower level distribution, such as to a project or program. |
Language |
The language in which you want the field labels and report headings of your reports to print. The field values appear as you enter them. |
Ledger Group |
On most PeopleSoft Commitment Control pages, this refers to the Commitment Control Ledger Group. |
Maximum Rows |
The maximum number of data rows you want to view in a scroll area. Often also applies to the scroll area of secondary pages you access from an initial page. |
Monetary Amount |
The amount in the base currency of the primary ledger. |
Oper Unit (operating unit) |
ChartField used to identify a location, such as a distribution warehouse or sales center. |
Operating Unit Affiliate |
ChartField used to correlate transactions between operating units when using a singe intraunit account. |
PC Business Unit |
Business unit assigned to a project in PeopleSoft Project Costing. |
Percent Available |
The percentage of the budget that is available after you deduct expenses and commitments. |
Period |
Accounting period. |
Planning |
Commitment Control ledger type (amount type) to record estimated amounts that you plan to spend. 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. See Planned and compare with Pre-encumbrance. |
Pre-encumbrance |
Commitment Control ledger type (amount type) for amounts that you expect to expend, but which you have no legal obligation to expend. A requisition is a typical pre-encumbrance transaction. |
Process Frequency |
Designates the appropriate frequency in the Process Frequency group box:
|
Process Monitor |
This link takes you to the Process List page, where you can view the status of submitted process requests. |
Process Status (for a Budget Processor instance) |
The status of a Budget Processor run can be one of the following:
|
Program |
ChartField that identifies groups of related activities, cost centers, revenue centers, responsibility centers, and academic programs. Tracks revenue and expenditures for programs. |
Project |
ChartField that captures information for project/grants accounting. |
Quantity |
The statistical amount for the transaction. Appears only for budgets that track statistical amounts. |
RSA |
See remaining spending authority. |
Recognized Revenue |
Commitment Control ledger type (amount type) for revenue that has been booked but not yet collected. |
Remaining Spending Authority |
For expenditure budgets, RSA is typically calculated by subtracting the sum total of pre-encumbrances, encumbrances and expenditures from the posted budget amount. If you have included a expenditure budget tolerances or your expenditure budget is associated with a revenue budget, the system includes with the posted budget amount, the revenue and finally any expenditure budget tolerance when calculating RSA. For revenue budgets, RSA is calculated by subtracting the sum total of recognized revenue from the posted budget amount. |
Request Number |
System-generated number to order a series of requests within a run control. |
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). |
Resource Type |
ChartField that identifies a type of resource, such as labor or materials, the use of which is associated with a cost. Used in conjunction with resource categories, subcategories, and groups. |
Revenue Estimate |
Commitment Control ledger type (amount type) for revenue estimate budget amounts. It records the total revenue you expect to generate in a budget period. |
Ruleset |
A RuleSet defines a group of chartfield values that share common budgetary attributes such as keys, calendars, and translation trees. RuleSets are used to allow different kinds of budgetary structures to be housed in the same Commitment Control Ledger Group. A Commitment Control budget definition must have at least one default RuleSet but may have many RuleSets defined based on the requirements for budget accounts. |
SetID |
A code that represents a set of control table information or TableSets. A TableSet is a group of tables (records) necessary to define your organizations accounting structure and processing options. |
Short Description |
Freeflow text up to 15 characters. |
Statistics Code |
ChartField that identifies non monetary statistical amounts. |
Status |
Indicates whether a row in a table is Active or Inactive. You cannot display inactive rows on transaction pages or use them for running batch processes. Inactivate rather than delete data you no longer use in order to maintain an audit trail. Contrast with Budget Status. |
Tolerance |
Also Budget Tolerance, Tolerance %. The percentage variance over budget that you allow a transaction and still allow it to pass budget checking. |
Unit |
Business unit. |
User ID |
The system identifier for the individual who generates a transaction. |
Year |
A calendar or fiscal year. |
See also PeopleTools: PeopleSoft Applications User's Guide
See also PeopleTools: PeopleSoft Process Scheduler
See also PeopleTools: "PeopleSoft Applications User's Guide," Working with Pages, Using Effective Dates