Penn Computing

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

COMP_DISTRIBUTION Table - Data Element Index

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



Data element Definition
COMP_DISTRIBUTION_ID

Indexed - yes
Format - number (12)
May be null? no
Uniquely identifies a record in the COMP_DISTRIBUTION table.
COMP_PERSON_ROLE_ID

Indexed - yes
Format - number (12)
May be null? no
Uniquely identifies a record in the COMP_PERSON_ROLE table; can be used to determine the role to which the distribution record applies.
 
CREATED_BY

Indexed - no
Format - varchar2 (12)
May be null? yes
The Penn ID of the PennWorks user who created the record in the PennWorks application.
 
CREATION_DATE

Indexed - no
Format - date (7)
May be null? yes
The date on which the record was created in the PennWorks application.
 

DISTRIBUTION_COA_AMOUNT

Indexed - no
Format - number (9,3)
May be null? yes

The pay period amount associated with the distribution.

DISTRIBUTION_COA_BC

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

The budgetary control character that represents the level at which funds availability checking occurs. Distribution_COA_BC is the third segment of the Distribution_COA_Number.

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

    
DISTRIBUTION_COA_CNAC

Indexed - yes
Format - char (3)
May be null? yes
The 3-character Center Net Asset Class. The first two positions of the Distribution_COA_CNAC identify the school or center. The last position identifies the Net Asset Class: 0 (Unrestricted); 1 (Temporarily Restricted); 2 (Permanently Restricted). Distribution_COA_CNAC is the first segment of the Distribution_COA_Number.

Examples: 880 (Medical Center, Unrestricted); 921 (Human Resources, Temporarily Restricted)


Values:

Refer to the DWADMIN.CNAC_CODES table for values.

    
DISTRIBUTION_COA_CREF

Indexed - yes
Format - char (4)
May be null? yes
The Center Reference Code. This is a 4-character identifier uniquely defined by each School or Center. Distribution_COA_Center_Ref is used to record information that is important to a school or center but is inappropriate for any other segment of the Distribution_COA_Account. The value of the Distribution_COA_Center_Ref is unique within a school or center. Distribution_COA_Center_Ref is the seventh and last segment of the Distribution_COA_Number.

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


Values:

Refer to the DWADMIN.CENTER_REF_CODES table for values.

    
DISTRIBUTION_COA_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. Distribution_COA_Fund is the fourth segment of the Distribution_COA_Number. If your organization is the Responsible_Org for the fund (even if it is not the Distribution_COA_Org, the Home_Org or the Role_Org), you will have access to the record.

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


Values:

Refer to the DWADMIN.FUND_CODES table for values.

    
DISTRIBUTION_COA_NUMBER

Indexed - yes
Format - char (9)
May be null? yes
The 26-digit account number indicating the funding source of this payroll distribution for the employee. The Distribution_COA_Account consists of seven segments:

Distribution_COA_CNAC
Distribution_COA_Org
Distribution_COA_BC
Distribution_COA_Fund
Distribution_COA_Object
Distribution_COA_Program
Distribution_COA_CREF

See also the definitions for Distribution_COA_CNAC, Distribution_COA_Org, Distribution_COA_BC, Distribution_COA_Fund, Distribution_COA_Object, Distribution_COA_Program, and Distribution_COA_CREF.

DISTRIBUTION_COA_OBJECT

Indexed - yes
Format - char (4)
May be null? yes
The 4-character Object Code. Identifies the asset, liability, revenue, or expense. Distribution_COA_Object is the fifth segment of the Distribution_COA_Number.

Examples: 5220 (EXTERNAL OFFICE SUPPLIES); 1149 (CASH SUSPENSE).


Values:

Refer to the DWADMIN.OBJECT_CODES table for values.

    
DISTRIBUTION_COA_ORG

Indexed - yes
Format - char (4)
May be null? yes
The 4-character code that identifies the Organization. An Organization is a subdivision of the University created for management purposes. An Organization belongs to only one responsibility center, and its Organization code is unique. That is, no two Organizations will have the same values for Distribution_COA_Org. Distribution_COA_Org is the second segment of the Distribution_COA_Number

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


Values:

Refer to the DWADMIN.ORG_CODES table for values.

    
DISTRIBUTION_COA_PROGRAM

Indexed - yes
Format - char (4)
May be null? yes
The 4-character program code. A program 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). Distribution_COA_Program is the sixth segment of the Distribution_COA_Number.

Examples: 7311 (Alumni Relations); 0001 (Discretionary)


Values:

Refer to the DWADMIN.PROGRAM_CODES Table for values.

    
DISTRIBUTION_COA_RESP_ORG

Indexed - yes
Format - char (4)
May be null? yes
The 4-character code for the organization responsible for managing the Distribution_COA_Fund. Many organizations may use the same fund, but only one organization -- the Responsible Organziation-- is accountable for managing the fund. Those who are authorized to access records for the Distribution_COA_Resp_ORG for the fund may access all records for the fund, regardless of the value of the Distribution_COA_Org in the Distribution_COA_Number for the record.

Values:

Refer to the DWADMIN.ORG_CODES table for values.

    
DISTRIBUTION_END_FISCAL_YEAR

Indexed - yes
Format - char (4)
May be null? yes
The financial year within which the Distribution_Stop_Date falls. Note: If there is no definite end date for the distribution, Distribution_End_Fiscal_Year will default to the latest available year in the Warehouse, which is 9999. Penn's fiscal year begins July 1 of one calendar year and ends June 30 of the next calendar year.

Example: for Distribution_Stop_Date 8/31/2009, the Distribution_End_Fiscal_Year would be 2010 (the fiscal year that began July 1, 2009, and ended June 30, 2010).

DISTRIBUTION_END_YEAR

Indexed - yes
Format - char (4)
May be null? yes
The calendar year within which the Distribution_Stop_Date falls. Note: If there is no definite end date for the distribution, Distribution_Stop_Year will default to the latest available year in the Warehouse, which is 9999.

Example: For Distribution_Stop_Date 8/31/2009, the Distribution_End_Year is 2009.

DISTRIBUTION_PERCENT

Indexed - no
Format - number (5,2)
May be null? yes
The percentage of standard hours to be paid from the distribution account. A value is only present for applicable job appointments.
DISTRIBUTION_START_DATE

Indexed - no
Format - date (7)
May be null? yes
The date on which payments will begin to be charged to the Distribution_COA_Number.
DISTRIBUTION_START_FISCAL_YEAR

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

Example: For Distribution_Start_Date 8/15/2009, the Distribution_Start_Fiscal_Year would be 2010 (the fiscal year that began July 1, 2009, and ended June 30, 2010)

DISTRIBUTION_START_YEAR

Indexed - yes
Format - char (4)
May be null? yes
The calendar year within which the Distribution_Start_Date falls.

Example: For Distribution_Start_Date 8/15/2009, the calendar year is 2009.

DISTRIBUTION_STATE

Indexed - yes
Format - varchar2 (1)
May be null? yes
Selected by the user to indicate the record is ready to be processed by the system if/when appropriate. Records with a state value of ‘P’ (projected) will remain in the PennWorks work area only. Users may select to delete records from PennWorks; these rows are retained in in the Data Warehouse for historical purposes with a state of 'X'.
Values:
Refer to the DWADMIN.ROLE_DIST_STATE_LOOKUP 
table for values.
DISTRIBUTION_STOP_DATE

Indexed - no
Format - date (7)
May be null? yes
The date when payment from this Distribution_COA_Number will cease.
EARNINGS_TYPE

Indexed - yes
Format - char (3)
May be null? yes
A 3-character code indicating the type of earnings. Currently, the Salary Management collection does include some Employee Benefits, and vacation and sick time data are only available for weekly paid employees.

Examples: RMO (regular monthly pay); OT2 (overtime at double time)

Values:
Refer to the DWPAY.PAYROLL_EARNINGS table for values.
EXTRACT_DATE

Indexed - no
Format - date (7)
May be null? yes
The date on which the COMP_DISTRIBUTION record was loaded to the Data Warehouse.
 
HOME_CENTER

Indexed - yes
Format - varchar2 (2)
May be null? yes
A 2-digit number used to identify the school or center that owns the employee's record and is responsible for its maintenance. The code set is from the University's General Ledger, and has been in use since July 1, 1996.

Example: 40 (School of Medicine)

Values:
Refer to the DWADMIN.ORG_CODES table, for values where 
Home_Center = Center_Code.
      
 
HOME_ORG

Indexed - yes
Format - varchar2 (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.
      
LAST_UPDATED_BY

Indexed - no
Format - varchar2 (12)
May be null? yes
The Penn ID of the PennWorks user who last updated the record in the PennWorks application.
 

LAST_UPDATE_DATE

Indexed - no
Format - date (7)
May be null? no

The date on which the record was last updated in the PennWorks application.

LAST_UPDATE_TIMESTAMP

Indexed - no
Format - timestamp (6)
May be null? no


The timestamp on which the record was last updated in the PennWorks application.
 
PENN_ID

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

The 8-digit identification number assigned to an individual by Penn Community system. For example: 77777777. No two persons have the same Penn ID. Note that Penn IDs created in and assigned by Penn Community begin at 10000000. Within the Data Warehouse, the numeric range from 00000000-00999999 is used for individuals who do not yet have a Penn ID in Penn Community, to allow for reliable joins between tables using the PENN_ID column. When a Penn ID appears for the individual appear in Penn Community, it will replace the assigned value throughout the Data Warehouse.

ROLE_CENTER

Indexed - yes
Format - varchar2 (2)
May be null? yes
The 2-digit number that represents the school or center in which the person performs the role.. The code set is from the University's General Ledger, and has been in use since July 1, 1996.

Example: 40 (School of Medicine)

Values:
Refer to the DWADMIN.ORG_CODES table, for values where 
Role_Center = Center_Code.
ROLE_ORG

Indexed - yes
Format - varchar2 (4)
May be null? yes
The 4-digit number that represents the organization in which the person performs the role. 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.

COMP_DISTRIBUTION 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