Penn Computing

University of Pennsylvania
Penn Computing << go backback
HYP_SALARY Table   Tables and Data Elements   Salary Management Home   Data Warehouse Home

HYP_SALARY Table - Data Element Index

Select a data element to view its definition and its indexed, format, and null values.



Data element Definition
ACCOUNT

Indexed - yes
Format - char (26)
May be null? yes
The 26-digit account number from the present General Ledger accounting structure indicating the source of the payment to the employee. The Account consists of seven segments: CNAC; Org; Budget Check; Fund; Object; Program; and CREF.
ACCOUNTING_PERIOD

Indexed - yes
Format - char (6)
May be null? yes

The Accounting_Period corresponding to the Period. The Accounting Period is stated in MON-YY format. MON is the calendar month (stored in upper case), and YY is the calendar year. Note that the beginning and ending dates of an accounting period are not necessarily the same as the first and last day of the calendar month.

Example: JUL-07 (July 2007, which occurs in fiscal year 2008)

BUDGET_CHECK

Indexed - yes
Format - char (1)
May be null? yes

The budget check (BC) that represents the level at which funds availability checking occurs for the salary expense. The Budget Check is the third segment of the Account.

Example: 1 (CNAC/ORG/FUND Year-To-Date)

Values:
0     Project-To-Date for capital projects
1     CNAC/ORG/FUND Year-To-Date
2     CNAC/ORG/FUND/CREF Year-To-Date
4     CNAC/ORG/FUND/CREF Project-to-Date

CNAC

Indexed - yes
Format - char (3)
May be null? yes

The 3-character Center Net Asset Class. The first two positions of the CNAC identify the school or center. The last position identifies the Net Asset Class: 0 (Unrestricted); 1 (Temporarily Restricted); 2 (Permanently Restricted). CNAC is the first segment of the Account.

Examples: 880 (Medical School, Unrestricted); 921 (Human Relations, Temporarily Restricted)

Values:
Refer to the DWADMIN.CNAC_CODES table for values.

 

CREF

Indexed - yes
Format - char (4)
May be null? yes

The Center Reference Code. A 4-character identifier uniquely defined by school/ Center. CREF is used to record information that is important to a school or center but is inappropriate for any other segment of the Account. The value of the CREF is unique in a school or center. CREF is the seventh and last segment of the Account.

Examples (for center 02): 4045 (Graduate Programs); 4091 (SAS Newsletter)

Values:
Refer to the DWADMIN.CENTER_REF_CODES table for values.
EXTRACT_DATE

Indexed - no
Format - date
May be null? yes

Date information was extracted from Hyperion Planning to the Data Warehouse.

FISCAL_MONTH_SEQ

Indexed - yes
Format - char (2)
May be null? yes

The month (or accounting period) of the fiscal year. This field is used for sorting.

Examples: 01 (July); 11 (May). See also FISCAL_YEAR

Values:
01 July
02 August
03 September
04 October
05 November
06 December
07 January
08 February
09 March
10 April
11 May
12 June
13 Adjustment period
FISCAL_YEAR

Indexed - yes
Format - char (4)
May be null? yes
The financial year within which the Accounting_Period falls. Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year.

Example: for an accounting period of JUL-07, 2008 (fiscal year that began July 1, 2007, and ended June 30, 2008)

FUND

Indexed - yes
Format - char (6)
May be null? yes

The 6-character fund code. A fund is the unique identifier for a specific set of financial resources that needs tracking or management. Fund is the fourth segment of the Account.

Examples: 000000 (General Unrestricted Fund); 010201 (SAS: GEN FUND 1)

Values:
Refer to the DWADMIN.FUND_CODES table for values.
HOME_ORG

Indexed - yes
Format - char (4)
May be null? yes

The 4-digit number that represents the organization that owns the employee's record and is responsible for its maintenance. An organization is a subdivision of the University created for management purposes. An Organization belongs to only one School or Responsibility Center, and its organization code is unique. (The code set is from the University's General Ledger, and has been in use since July 1, 1996.)

Examples: 0104 (CHEMISTRY); 0001 (GEN UNIVERSITY)

Values:
Refer to the DWADMIN.ORG_CODES table for values.
OBJECT

Indexed - yes
Format - char (4)
May be null? yes

The 4-character Object Code that identifies the asset, liability, revenue, or expense. The Object is the fifth segment of the Account.

Examples: 5010 (STANDING FAC); 5110 (F/G SUPPORT)

Values:
Refer to the DWADMIN.OBJECT_CODES table for values.
ORG

Indexed - yes
Format - char (4)
May be null? yes

The 4-character code identifying the Organization. An Organization belongs to only one responsibility center, and its Organization code is unique. That is, no two Orgs will have the same values. Org is the second segment of the Account.

Examples: 0702 (Wharton Finance); 0705 (Wharton Legal Studies)

Values:
Refer to the DWADMIN.ORG_CODES table for values.
PENN_ID

Indexed - yes
Format - char (8)
May be null? yes
The 8-digit identification number assigned to the employee by Penn Community system. For example: 77777777. The Penn ID convention of "0001ANY" is used as a placeholder for payments that are planned, but not yet assigned to a particular employee.
PERIOD

Indexed - yes
Format - varchar2 (25)
May be null? yes
The period representing the calendar month, as stored in Hyperion Planning. For example: Dec.
PLANNING_AMOUNT

Indexed - no
Format - number
May be null? yes
The budget or forecast amount, as entered into Hyperion Planning.
PLAN_CREF

Indexed - no
Format - varchar2 (25)
May be null? yes
The CREF, as stored in Hyperion Planning. Planning dimensions have a prefix with the name of the dimension. For example: CREF-02-0217 indicates center reference code 0217, in center 02.
PLAN_FUND

Indexed - no
Format - varchar2 (25)
May be null? yes

The Fund, as stored in Hyperion Planning. Planning dimensions have a prefix with the name of the dimension. For example: FUND-00000

 

PLAN_ORG

Indexed - no
Format - varchar2 (25)
May be null? yes
The ORG, as stored in Hyperion Planning. Planning dimensions have a prefix with the name of the dimension. For example: ORG-0702
PLAN_PENNID

Indexed - no
Format - varchar2 (25)
May be null? yes
The Penn ID, as stored in Hyperion Planning. Planning dimensions have a prefix with the name of the dimension. For example: PENNID-77777777. Any Penn ID value ending in "ANY" indicates that budgeting or forecasting occured at the ORG level, rather than for an individual employee.
PLAN_PROGRAM

Indexed - no
Format - varchar2 (25)
May be null? yes
The Program, as stored in Hyperion Planning. Planning dimensions have a prefix with the name of the dimension. For example: PROG-7311.
PROGRAM

Indexed - yes
Format - char (4)
May be null? yes

The 4-character code indicating the program. This is an activity or work process commonly defined across the University for tracking a program's activity across Schools and Centers (or across organizations within a school or center). Program is the sixth segment of the Account.

Examples: 7311 (ALUMNI RELATIONS); 0001 (DISCRETIONARY)

Values:
Refer to the DWADMIN.PROGRAM_CODES table for values.
RESP_ORG

Indexed - yes
Format - char (4)
May be null? yes
The 4-character code for the organization responsible for managing the Fund. Many organizations may use the same fund, but only one organization -- the Responsible ORG-- is accountable for managing the fund. Those who are authorized to access records for the Responsible ORG for the Fund may access all records for the fund, regardless of the value of the ORG in the Account for the record.
Values:
Refer to the DWADMIN.ORG_CODES table for values.
SCENARIO

Indexed - yes
Format - varchar2 (25)
May be null? yes
Indicates the type of data. e.g., Actual, Budget, Forecast, Operating,
SOURCE

Indexed - yes
Format - varchar2 (100)
May be null? yes
Indicates the file that was the source of the data. For example: PennPln1_Salary_Level0.dat.
VERSION

Indexed - yes
Format - varchar2 (25)
May be null? yes
Indicates the version of data. e.g., Final, Working, Fall, Winter, Spring, Summer.
YEAR

Indexed - yes
Format - varchar2 (25)
May be null? yes
The year, as stored in Hyperion Planning. For example: 07 (for fiscal year 2007)

HYP_SALARY Table   Tables and Data Elements   Salary Management Home   Data Warehouse Home

Questions about this page? Email us at da-staff@isc.upenn.edu

Information Systems and Computing
University of Pennsylvania
Information Systems and Computing, University of Pennsylvania