| Data element |
Definition |
APPROVER_HOME_CENTER
Indexed - yes
Format - char (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.
|
APPROVER_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.
|
APPROVER_NAME
Indexed - yes
Format - varchar2 (100)
May be null? yes |
The name of the person who submitted/approved or rejected the request, at the point of status history indicated by the record. |
APPROVER_PENN_ID
Indexed - yes
Format - varchar2 (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.
|
COMP_PAY_REQUEST_ID
Indexed - yes
Format - number (22)
May be null? no
|
Uniquely identifies a record in the COMP_PAY_REQUEST table. |
COMP_PAY_ROUTING_HISTORY_ID
Indexed - yes
Format - number (22)
May be null? no
|
Uniquely identifies a record in the COMP_PAY_ROUTING_HISTORY table. |
ESCALATION_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date on which review of the request was escalated to the next level.
|
EXTRACT_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date on which the COMP_PAY_ROUTING_HISTORY record was loaded to the Data Warehouse.
|
PREWORK
Indexed - no
Format - varchar2 (1)
May be null? yes |
Indicates whether the request was an Additional Pay Prework request. |
REVIEWER_COMMENT
Indexed - no
Format - varchar2 (4000)
May be null? yes |
A comment submitted at the point of approval or rejection by the reviewer. |
|
ROUTING_ROLE_NAME
Indexed - no
Format - varchar2 (200)
May be null? yes
|
The specific application role of the person who submitted/approved or rejected the request, at the point of status history indicated by the record.
|
ROUTING_STATUS
Indexed - yes
Format - varchar2 (16)
May be null? yes |
The status of the request at the point of status history indicated by the record.
|
|
ROUTING_STATUS_DATE
Indexed - no
Format - date (7)
May be null? yes
|
The date of submission/approval or rejection, at the point of status history indicated by the record.
|
