UD PeopleSoft Financial System
Last updated on 3/29/2005.
Data Dictionary - for general campus users
This is not an exhaustive list of Records and Fields, but contains those most useful to general campus
users of queries and other aspects of the UD Financial System.
You can follow links among the definitions of individual Records and their Fields, or you can
print the dictionary in pdf-format (77 pages).
Back-Office users (GA, Budget, Procurement, etc) may have access to a broader set of Records and/or the
"Production Instance" of the system.
A broader dictionary is also available for those who have such access.
- Account Type: characterizes an account, transaction or balance broadly as Expense, Revenue, Asset,
Liability, or Equity.
- Budget Years: 4-digit fiscal years. Each fiscal year begins July 1, ends June 30, and is named for the
calendar year of the latter.
- Attributes provide a method for tagging chartfields with additional qualities not inherent in the
chartfield itself. Can be used as criteria or grouping in another way than lists and trees, but often
toward the same end. For example, the Purposes that are given a certain TRUSTSORT attribute here are
grouped together for reporting to Board of Trustees.
- Key sets comprised of (a Chartfield, an attribute, and a value) join here to yield a Description.
- This is the Purpose Table, which contains short and long descriptions as of an effective date. The
"Purpose" chartfield identifies discrete blocks of money used to make expenditures, collect revenues, or
track assets and liabilities (eg. PLSC11). Relates to the legacy 11-digit "account code".
- This is the Source Table, which contains short and long descriptions as of an effective date. The
"Source" chartfield is the source of funds. Will be used for Contracts & Grants and capital projects (eg.
33041101: Office of Education).
- This is the Userfield Table, which tags transactions with a code that each UDFS user can interpret as
(s)he finds useful (eg. USER_001 might mean "Paris" to one user or department, but mean "Fall lecture
series" to another).
- This is the Class Table, which contains short and long descriptions as of an effective date. "Class"
chartfield: identifies the faculty member or the staff position to which salary items apply. Descriptions
are not meaningful. Class relates to the legacy "line number".
- This is the Department Table, which contains short and long descriptions as of an effective date. The
"Department" chartfield identifies the administrative budget unit controling one or more Purposes (eg.
02537 = English). Some entries are not actual departments, but are merely nodes on a tree that
organizes departments into a hierarchy for reporting purposes.
- This is the Fund Table, which contains short and long descriptions as of an effective date. The "Fund"
chartfield identifies the fund type to which a certain Purpose belongs. Implies a set of accounting rules
that pertain to those Purposes (eg. OPBAS: Basic Operating). Corresponds to first two segments of the
legacy Account Code (01-1-...).
- This is the Account Table, which contains short and long descriptions as of an effective date. The
"Account" chartfield classifies transactions as a particular category of expenditure, revenue, asset,
liability or net assets. (eg. 141000: Office Supplies). Corresponds to the legacy "Object code".
- This is the Program Table, which contains short and long descriptions as of an effective date. The
"Program" chartfield characterizes a transaction as to the major University function to which it pertains
(eg. INST1 = Instruction). Corresponds to the legacy "function code".
- This is the Project Table, which contains short and long descriptions as of an effective date. The
"Project" Chartfield identifies contract and grant activities and facilities projects with a specific
beginning and end date (eg. ARTC37211199000). Subdivides activity within a particular "Purpose" (eg.
ARTC372111) by adding designators for fiscal year, building, or other coded details.
- This is the Speedtype Table, which contains short and long descriptions as of an effective date. The
"Speedtype" provides default values for several chartfields. Expedites filling in forms with default
values by entering this one field instead of each one separately.
- "Transaction Source": characterizes the origin or type of a transaction. Mimics the legacy "tran-code".
Not to be confused with "Source" (Chartfield2)
- Award Attributes:: Descriptive header information for each proposal once a Purpose and Project-ID(s) have
been assigned. Includes awards in "pre-award" status, through "awarded", "closed", etc. Similar to
Proposal Attributes, but data continues to be updated across the life of the award; whereas Proposal
Attributes are static as of the award date.
- Project: F&A (facilities & administration) rates associated with each project. Useful for analyzing the
overhead earned through the project.
- Project Resources: Individual expense transactions associated with each project. "Analysis Type" is an
essential field when querying this view and interpretting the various costs that are returned.
- Proposal Attributes: Descriptive header information for each proposal at the Pre-award stage. Shows the
status (eg. draft, pending, awarded, withdrawn,...)
- Proposal Budget: Specifies budgeted amounts for each item of each project within the proposal. Budgets
are as stated in the proposal and do not reflect changes made after awarded.
- Identifies each component of an employee's salary as a percentage of the entire salary.
This record is a child of UOD_LBR_DST_HDR.
- Labor Distributions (LAM) for each employee are given effective dates for Active/Inactive status in this
Further details are in this record's child: UOD_LBR_DST_DTL.
- Provides details (Purpose, Account, Amount, and other chartfields) of each Obligation/Encumbrance, both
salary and non-salary, in the parent record UOD_OBLIG_HDR. Salaries are automatically encumbered and
disencumbered by the Labor Allocation Module (LAM) and Payroll process. Non-salary items are manually
encumbered and disencumbered.
This record is a child of UOD_OBLIG_HDR.
- Enumerates Obligations (Encumbrances), both salary and non-salary. Salaries are automatically encumbered
and disencumbered by the Labor Allocation Module (LAM) and Payroll process. Non-salary items are manually
encumbered and disencumbered. Each Obligation may be divided into multiple details, each with their own
Chartfields and amounts in the child table, UOD_OBLIG_DTL.
Further details are in this record's child: UOD_OBLIG_DTL.
- Contains summary amounts for activity during each Accounting Period (starting, monthly, and year-end
adjustment periods) for each Chartfield-String. Also has starting balances, year-to-date budget changes,
and other information to assess financial situation of that Chartfield-String as of the specified
- Contains individual transactions, identified by their Chartfield-Strings, date, and the vehicle that
caused them (eg. which Purchase Order ID, Journal ID, Voucher ID, etc.). Equivalent to the DataWarehouse
table GA-TRANSACTIONS. This Record's data is compiled from multiple other Records, which are indicated
- Indicates the Purposes (Chartfield1) for which a user has approval authority.
- Contains row level security controls. For each user, there is at least one entry here that specifies a
certain degree of access. That access can be applied to one or more Purposes (Chartfield1) by appearing
in the child Record (UOD_ROW_SEC_LN) in conjunction with those Purposes.
Further details are in this record's child: UOD_ROW_SEC_LN.
- Contains the attachment between a user's degree of row level security access (from the parent
UOD_ROW_SEC_HDR) and one or more Purposes to which that security applies.
This record is a child of UOD_ROW_SEC_HDR.