Penn Computing

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

COMP_DISTRIBUTION_EXT Table - Data Element Index

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



Data element Definition
COMP_DISTRIBUTION_EXT_ID

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

Indexed - yes
Format - number (12)
May be null? yes
Uniquely identifies a record in the COMP_PERSON_ROLE table; can be used to determine the role to which the external 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.
 
EXT_DIST_END_FISCAL_YEAR

Indexed - yes
Format - char (4)
May be null? yes
The financial year within which the Ext_Distribution_Stop_Date falls. Note: If there is no definite end date for the external distribution, Ext_Dist_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 Ext_Distribution_Stop_Date 8/31/2009, the Ext_Dist_End_Fiscal_Year would be 2010 (the fiscal year that began July 1, 2009, and ended June 30, 2010).

EXT_DIST_START_FISCAL_YEAR

Indexed - yes
Format - char (4)
May be null? yes
The financial year within which the Ext_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 Ext_Distribution_Start_Date 8/15/2009, the Ext_Dist_Start_Fiscal_Year would be 2010 (the fiscal year that began July 1, 2009, and ended June 30, 2010)

EXT_DISTRIBUTION_AMOUNT

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

The pay period amount associated with the external distribution.
EXT_DISTRIBUTION_END_YEAR

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

Example: For Ext_Distribution_Stop_Date 8/31/2009, the Ext_Distribution_End_Year is 2009.

EXT_DISTRIBUTION_PERCENT

Indexed - no
Format - number (5,2)
May be null? yes
The percentage of standard hours to be paid from the external distribution source.
EXT_DISTRIBUTION_SOURCE

Indexed - no
Format - number (12)
May be null? yes

For distributions external to Penn Payroll, identifies the source of the distribution.

Values:
Refer to the COMP_EXT_DIST_SOURCE_LIST table for values.
EXT_DISTRIBUTION_SOURCE_REF

Indexed - no
Format - varchar2 (100)
May be null? yes
For distributions external to Penn Payroll, an identifier for the particular distribution record.
EXT_DISTRIBUTION_START_DATE

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

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

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

EXT_DISTRIBUTION_STATE

Indexed - yes
Format - varchar2 (1)
May be null? yes
Indicates whether the external distribution exists in PennWorks. Since 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.
    
EXT_DISTRIBUTION_STOP_DATE

Indexed - no
Format - date (7)
May be null? yes
The date when payment from the external source will cease.
EXTRACT_DATE

Indexed - no
Format - date (7)
May be null? yes
The date on which the COMP_DISTRIBUTION_EXT 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_EXT 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