Penn Computing

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

LMS_PERSON - Data Element Index

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

 

Data element Definition
ASSIGNMENT_FEED_ELIGIBLE

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

A Yes/No flag indicating whether the Penn Profiler system may feed to Knowledge Link any records that it creates to assign courses to the person as a trainee. See also DATE_LAST_ASSIGNED_TO_PROFILER and LAST_CERTIFICATION_DATE.

In Knowledge Link, courses are assigned to business units, not to the trainees themselves. To enable courses to be assigned to individual trainees, a unique personal business unit has been created for each Penn Community member that has a FAC, STAF, or STU affiliation, or an auxiliary affiliation. (For the list of auxiliary affiliations, see PENN_COMMUNITY_MEMBER_STATUS.) These unique personal business units have identifiers that start with UP. If a Profiler user is a University of Pennsylvania Health System employee, but has not been assigned to a unique UP personal business unit in Knowledge Link, Profiler cannot feed Knowledge Link course assignments for the individual. For more information on business units, see the documentation on KNODE.IDENTIFIER.

ASSIGNMENT_FEED_ELIGIBLE is '.' if EXTRACT_SOURCE is 'L'.

Values:
Y (the Penn Profiler may feed course assignments for this 
   person to Knowledge Link)
N (the Penn Profiler may not feed course assignments for this person to Knowledge Link because the person has not been assigned to a unique UP personal business unit)
. (the Penn Profiler may not feed course assignments for this person to Knowledge Link because the person has no record in the Penn Profiler system)
DATE_LAST_ASSIGNED_TO_PROFILER

Indexed - no
Format - date
May be null? yes

The date when the Penn Profiler system last fed to Knowledge Link a course assignment record indicating that the person is currently required to take the Profiler survey. The value is null for some LMS_PERSON records. See also ASSIGNMENT_FEED_ELIGIBLE, NOTIFICATION_EMAIL, NOTIFICATION_REQUIRED, and LAST_CERTIFICATION_DATE.

Given the person’s responses to the survey questions about his or her academic activities and job responsibilities, Profiler determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Those who are currently required to take the Profiler survey ought to complete it at least once a year. They are also required to re-take the survey when there is a change in their academic activities or job responsibilities. University employees are required to re-take the survey when there is a change in the job class or the org. for their job appointment(s).

Example: 4/23/2008

Values:
List of values not available
DEPT_START_DATE

Indexed - no
Format - date
May be null? yes

The most recent date when the person's current job appointment began. This could be the date the person was hired to work in his or her current job department, or the date the person transferred into his or her current job department. (This is also stored in the Data Warehouse in CUSTOM_DATA.CUSTOM_V10.)

Currently, DEPT_START_DATE is used only for employees of the University of Pennsylvania Health System (UPHS), and indicates the most recent date when the person began working in his or her current UPHS department. See also UPHS_DEPARTMENT_CODE, UPHS_DEPARTMENT_NAME, and UPHS_DEPARTMENT_NAME_AS_IS.

DEPT_START_DATE is null for some UPHS employees. It is also null for people that are not UPHS employees. (Note: a person may be both a UPHS employee and a University employee.)

Sometimes, when a mandatory course is assigned to a UPHS business unit, not all of the people included in the business unit are required to take the course; some are "grandfathered". (For information on the inclusion of people in business units, see KNODE_USER_JOIN.KNODE_ID.) One of the tests for determining whether a particular person is grandfathered for a given course is to compare the person's DEPT_START_DATE with the effective date of the course assignment. If the person's DEPT_START_DATE falls before the effective date, the person is grandfathered. For more information on grandfathering, see the Caution regarding the GRANDFATHERING_VALUE in the documentation for the COURSE_OBJECT table.

Example: 6/28/2009

Values:
List of values not available
EMAIL_ADDRESS

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

The person's current (or last known) electronic mail address at work, as stored in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.EMAIL_WORK.) The value is not necessarily a valid e-mail address. See also LMS_PERSON.NOTIFICATION_EMAIL.

The value may be stored in upper case, lower case, or mixed case. The value is null for some LMS_PERSON records.

The ultimate source of the EMAIL_ADDRESS is the person's preferred e-mail address in the University's Online Directory.

Examples: Abigail.Adams@uphs.upenn.edu; franklin@pobox; NOT LISTED

Values:
List of values not available
EXTRACT_SOURCE

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

Indicates whether the source of the data in the LMS_PERSON record is the Penn Profiler system only, Knowledge Link (the Learning Management system) only, or both.

If EXTRACT_SOURCE is 'P', the data elements for information from Knowledge Link will be null. If EXTRACT_SOURCE is 'L', the data elements for information from the Penn Profiler system will be null.

Values:

B (the LMS_PERSON record includes data from both the Learning  
   Management System [Knowledge Link] and the Penn Profiler system)
L (the LMS_PERSON record includes data from the Learning  
   Management System [Knowledge Link] only)
P (the LMS_PERSON record includes data from the Penn Profiler  
   system only)
FIRST_NAME

Indexed - yes
Format - varchar2 (50)
May be null? yes

The person's given name, stored in upper case to facilitate record selection conditions and sorting. The value might be null for some LMS_PERSON records. See also FIRST_NAME_AS_IS, MIDDLE_INITIAL, LAST_NAME, and NAME.

The FIRST_NAME reflects the person's first name as stored in Knowledge Link.

Examples: ABIGAIL, BENJAMIN, JAMES

Values:
List of values not available.
FIRST_NAME_AS_IS

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

The person's given name, as stored in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.FIRST_NAME.) See also FIRST_NAME, MIDDLE_INITIAL, LAST_NAME, and NAME.

The value may be stored in upper case, lower case, or mixed case. The value might be null for some LMS_PERSON records.

Examples: ABIGAIL, benjamin, James

Values:
List of values not available
FULL_NAME_AS_IS

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

The person's name, as stored in the Penn Profiler system. See also NAME.

The value may be stored in upper case, lower case, or mixed case. In most cases, the person's name is stored in the format LASTNAME, FIRSTNAME MIDDLENAME (with a comma and a space separating the LASTNAME from the FIRSTNAME). However, some records have only a comma between the LASTNAME and the FIRSTNAME. The value may include a middle name, a middle initial, or neither after the FIRSTNAME. If the value includes a middle initial, it might or might not have a period after it. FULL_NAME_AS_IS might be null for some LMS_PERSON records.

More than one person may have the same name. For data elements that uniquely identify the person, see PENN_ID, PENNKEY, USER_REC_ID, HIBERNATE_ID, and UPHS_EMPLOYEE_NUMBER.

Examples: 'ADAMS, ABIGAIL S.'; 'franklin,benjamin'; 'Lafayette, James Armistead'; 'JONES,JOHN P' The value is stored without the surrounding quotes.

Values:
List of values not available
HIBERNATE_ID

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

A numeric value that uniquely identifies the Knowledge Link user within the Penn Profiler system.

The Penn Profiler system ("Profiler") is an online survey that presents a Profiler user with a customized set of questions about the respondent's academic activities and job responsibilities. Based on the responses to the questions, Profiler determines the training courses or packages (if any) that the respondent is currently required to complete, and transmits the relevant assignments to Knowledge Link (the learning management system used by the University and by the University of Pennsylvania Health System). Profiler also identifies the Profiler users that need to (re-) take the survey, and transmits the Profiler assignments to Knowledge Link. (Knowledge Link treats the Profiler online survey as a course.)

See also the PROFILER_USER_QUESTIONNAIRE, PROFILER_USER_ANSWER, and PROFILER_ASSIGNMENTS tables.

If the person is a Knowledge Link user, but not a Penn Profiler user, HIBERNATE_ID is null. See also EXTRACT_SOURCE.

For other data elements that uniquely identify the person, see PENN_ID, PENNKEY, USER_REC_ID, and UPHS_EMPLOYEE_NUMBER.

Example: 1861849

Values:
List of values not available
LAST_CERTIFICATION_DATE

Indexed - no
Format - date
May be null? yes

The date when the person last took the Profiler survey and certified that he or she had completed the survey and had given accurate responses to the survey questions. LAST_CERTIFICATION_DATE is null for some LMS_PERSON records. See also ASSIGNMENT_FEED_ELIGIBLE.

Given the responses to its survey questions about the person's academic activities and job responsibilities, the Penn Profiler system determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Those who are currently required to take the Profiler survey ought to complete it at least once a year. They are also required to re-take the survey when there is a change in their academic activities or job responsibilities. University employees are required to re-take the survey when there is a change in the job class or the org. for their job appointment(s).

Example: 5/22/2007

Values:
List of values not available
LAST_EXTRACT_DATE

Indexed - no
Format - date
May be null? yes

The date and time when the data for this record was extracted from Knowledge Link and the Penn Profiler system, and loaded into the Data Warehouse.

Business Objects hint: by default, just the date will appear in your report, but you can change the format of the cell to show just the time, if you so desire.

Example: 7/22/2008 3:38:07 AM

Values:
List of values not available.
LAST_NAME

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

The person's surname, stored in upper case to facilitate record selection conditions and sorting. The value might be null for some LMS_PERSON records. See also LAST_NAME_AS_IS, FIRST_NAME, MIDDLE_INITIAL, and NAME.

The LAST_NAME reflects the person's surname as stored in Knowledge Link.

Examples: ADAMS, FRANKLIN, LAFAYETTE

Values:
List of values not available.
LAST_NAME_AS_IS

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

The person's surname, as stored in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.LAST_NAME.) See also LAST_NAME, FIRST_NAME, MIDDLE_INITIAL, and NAME.

The value may be stored in upper case, lower case, or mixed case. The value might be null for some LMS_PERSON records.

Examples: ADAMS, franklin, Lafayette

Values:
List of values not available
LAST_NOTIFICATION

Indexed - no
Format - date
May be null? yes

The date when the Penn Profiler system last sent e-mail to the person, notifying him or her of the need to take (or re-take) the Profiler survey. The value is null for some LMS_PERSON records.

Note: LAST_NOTIFICATION has nothing to do with Knowledge Link's E-mail Notifications function.

Given the responses to its survey questions about the person's academic activities and job responsibilities, the Penn Profiler system determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Those who are currently required to take the Profiler survey ought to complete it at least once a year. They are also required to re-take the survey when there is a change in their academic activities or job responsibilities. University employees are required to re-take the survey when there is a change in the job class or the org. for their job appointment(s).

Example: 4/17/2008

Values:
List of values not available
LMS_DATE_CREATED

Indexed - no
Format - date
May be null? yes

The date when person's Knowledge Link user record was created in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.DATE_CREATED.) The value might be null for some LMS_PERSON records.

Example: 4/29/2005

Values:
List of values not available
LMS_DATE_MODIFIED

Indexed - no
Format - date
May be null? yes

The date when person's user record was last updated in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.DATE_MODIFIED.) The value might be null for some LMS_PERSON records.

Example: 7/11/2008

Values:
List of values not available
MIDDLE_INITIAL

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

The first letter of the person's middle name, stored in upper case. The value is null for some LMS_PERSON records. See also MIDDLE_NAME_AS_IS, LAST_NAME, FIRST_NAME, and NAME.

Note: although the value of MIDDLE_INITIAL ought to be an upper case letter (if it is not null), it can be a character of any type--for example, '-'.

The MIDDLE_INITIAL reflects the person's middle initial as stored in Knowledge Link.

Example: S

Values:
List of values not available.
MIDDLE_NAME_AS_IS

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

The first letter of the person's middle name, as stored in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.MIDDLE_INITIAL.) See also LAST_NAME, FIRST_NAME, MIDDLE_INITIAL, and NAME.

The value may be stored in upper case, lower case, or mixed case. The value is null for some LMS_PERSON records.

Note: although MIDDLE_NAME_AS_IS ought to store one letter at most, it can store a string of up to 10 characters of any type--for example, '-'.

Example: s

Values:
List of values not available.
NAME

Indexed - yes
Format - varchar2 (95)
May be null? yes

The person's name, stored in upper case to facilitate record selection conditions and sorting. The value begins with the person's surname.

If the person has a user record in Knowledge Link, NAME is stored in the format LASTNAME, FIRSTNAME M. The last name and first name are separated by a comma and a space; if the person has a middle initial, the value of NAME ends with a period. (See also LAST_NAME, FIRST_NAME, and MIDDLE_INITIAL.)

If the person does not have a user record in Knowledge Link, NAME reflects the person's name as stored in the Penn Profiler system. The last name and first name may be separated by a comma and a space, or just by a comma; the NAME value might or might not end with a period. (See also FULL_NAME_AS_IS.)

More than one person may have the same name. For data elements that uniquely identify the person, see PENN_ID, PENNKEY, USER_REC_ID, HIBERNATE_ID, and UPHS_EMPLOYEE_NUMBER.

Examples: 'ADAMS, ABIGAIL S.'; 'FRANKLIN,BENJAMIN'; 'LAFAYETTE, JAMES ARMISTEAD'; 'JONES,JOHN P' The value is stored without the surrounding quotes.

Values:
List of values not available
NOTIFICATION_EMAIL

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

The e-mail address to which the Penn Profiler system last sent (or will send) notifications intended for the person. The value is usually, but not always, a valid e-mail address. It may be stored in upper case, lower case, or mixed case. NOTIFICATION_EMAIL is null for some LMS_PERSON records. See also DATE_LAST_ASSIGNED_TO_PROFILER, NOTIFICATION_REQUIRED, and EMAIL_ADDRESS.

Note: NOTIFICATION_EMAIL has nothing to do with Knowledge Link's E-mail Notifications function.

Given the responses to its survey questions about the person's academic activities and job responsibilities, the Penn Profiler system determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Those who are currently required to take the Profiler survey ought to complete it at least once a year. They are also required to re-take the survey when there is a change in their academic activities or job responsibilities. University employees are required to re-take the survey when there is a change in the job class or the org. for their job appointment(s). The Penn Profiler system automatically e-mails a notification to the person when he or she needs to take (or re-take) the survey. After the person completes the survey, the Penn Profiler system automatically e-mails the person a notification listing all of the currently required courses that Profiler assigned to him or her, flagging those that the person is required to complete as soon as possible. That notification also lists otherwise assigned courses that the person is required to complete as soon as possible.

Examples: Abigail.Adams@uphs.upenn.edu; franklin@pobox; JONESJP@SEAS.UPENN.EDU

Values:
List of values not available
NOTIFICATION_REQUIRED

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

A Yes/No flag indicating whether the Penn Profiler system is due to notify the person via e-mail that he or she needs to take (or re-take) the Profiler survey.

Note: NOTIFICATION_REQUIRED has nothing to do with Knowledge Link's E-mail Notifications function.

Given the responses to its survey questions about the person's academic activities and job responsibilities, the Penn Profiler system determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Those who are currently required to take the Profiler survey ought to complete it at least once a year. They are also required to re-take the survey when there is a change in their academic activities or job responsibilities. University employees are required to re-take the survey when there is a change in the job class or the org. for their job appointment(s). The Penn Profiler system automatically e-mails a notification to the person when he or she needs to take (or re-take) the survey.

Values:
Y (the next run of the Penn Profiler notification process 
   ought to send e-mail to the person asking him or her
   to (re-)take the survey) 
N (the next run of the Penn Profiler notification process ought not to send e-mail to the person asking him or her to (re-)take the survey)
. (the Penn Profiler notification process will not send any e-mail to the person because the person has no record in the Penn Profiler system)
PENN_COMMUNITY_MEMBER_STATUS

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

An upper case letter indicating whether or not the person is an active user of the Knowledge Link and/or Penn Profiler systems. An active user is an active member of the Penn Community that has at least one active affiliation that is relevant to Knowledge Link. (The status information for Knowledge Link users is also stored in the Data Warehouse in GEN21_USER.STATUS, where 1 or 0 indicates whether the user is active or inactive.)

A person who has a Penn Community affiliation is associated with the University of Pennsylvania in a particular way. A person can have multiple Penn Community affiliations, but not all affiliations are relevant to Knowledge Link. An affiliation is relevant if persons with that affiliation have their training records and current training assignments stored in Knowledge Link. The following Penn Community affiliations are relevant to Knowledge Link:

  • University affiliations:
    • FAC (Faculty) a subset of University employees
    • STAF (Staff) a subset of University employees
    • STU (Student)
  • UPHS affiliations:
    • BFC (Benjamin Franklin Clinic)
    • CCA (Clinical Care Associates)
    • CCNJ (Clinical Care Associates NJ)
    • CPUP (Clinical Practices of the University of Pennsylvania)
    • GAMB (Gambro)
    • HCOR (Corporate on HUP Payroll)
    • HSSP (Health System Service Providers)
    • HUP (Hospital of the University of Pennsylvania)
    • JRB (John Rea Barton Practice)
    • MAPS (HUP/CPUP - MAPS employees)
    • MDUP (Hospital MDUPM)
    • PAH (Pennsylvania Hospital)
    • PAHM (Hall Mercer Community Mental Health/Mental Retardation Center)
    • PERF (Perfusion)
    • PHX (Phoenixville)
    • RES (Research)
    • TPHX (Phoenixville) this affiliation currently is not used
    • UNK (Unknown)
    • URSV (Urology Associates)
  • Auxiliary affiliations:
    • ADJF (Adjunct Faculty)
    • CHOP (Children's Hospital of Philadelphia)
    • CTSY (Courtesy)
    • MONL (Monell Chemical Senses Center)
    • MRES (Medical Resident)
    • PMC (Presbyterian Medical Center)
    • SERV (Service Provider)
    • TEMP (Temporary Staff)
    • UAGT (University Business Agent)
    • VFAC (Visiting Faculty)
    • VSCO (Visiting Scholar)
    • VMST (Visting Medical Student)
    • VSTU (Visiting Student)
    • WFAC (Wistar Faculty)
    • WSTF (Wistar Staff)
Values:
A (the person is an active member of the Penn Community
   with at least one active affiliation that is relevant
   to Knowledge Link)
I (the person has no active Penn Community affiliations that are relevant to Knowledge Link)
PENN_ID

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

The LMS_PERSON table has one record per PENN_ID.

  • For most LMS_PERSON records, PENN_ID is an 8-digit identification number assigned to the person by the Penn Community system. No two persons have the same Penn ID. (The Penn IDs for Knowledge Link users are also stored in the Data Warehouse in GEN21_USER.USER_NUMBER.)
  • Some LMS_PERSON records store information for Knowledge Link administrator user IDs. For those records, PENN_ID is not really a Penn ID, but a code that begins with a letter and is unique in the LMS_PERSON table.

Most tables in the Data Warehouse use PENN_ID as the unique identifier for a person. This facilitates joining tables with data that pertains to people, regardless of whether those tables are in the same data collection.

For other data elements that uniquely identify the person, see PENNKEY, USER_REC_ID, HIBERNATE_ID, and UPHS_EMPLOYEE_NUMBER.

Example: 12345678

Values:
List of values not available
PENNKEY

Indexed - no
Format - varchar2 (20)
May be null? no

For most LMS_PERSON records, PENNKEY stores the person's Penn Key, a unique name (attributable to a single individual) that serves as the Kerberos Principal and as a user name (logon ID) for the individual. The PennKey (along with the PennKey password) is used to authenticate the person's identity when he or she accesses certain University systems and services, such as Knowledge Link and the Penn Profiler system.

Some LMS_PERSON records store information for Knowledge Link administrator user IDs. For those records, PENNKEY stores the user ID.

The PENNKEY value may be stored in upper or lower case, and may include letters and numerals.

The PENNKEYs for Knowledge Link users are also stored in the Data Warehouse in GEN21_USER.GEN21_USER_NAME.

For other data elements that uniquely identify the person, see PENN_ID, USER_REC_ID, HIBERNATE_ID, and UPHS_EMPLOYEE_NUMBER.

Example: franklin; ADAMSA1

Values:
List of values not available
PRIMARY_BUSINESS_UNIT_ID

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

A string that uniquely identifies the person's primary Knowledge Position (KP), the business unit to which the person is primarily assigned in Knowledge Link. (This is also stored in the Data Warehouse in CUSTOM_DATA.CUSTOM_V21.) The PRIMARY_BUSINESS_UNIT_ID value corresponds to a KNODE.IDENTIFIER. See also PRIMARY_BUSINESS_UNIT_NAME, PRIMARY_BUSINESS_UNIT_NUMBER, and TRAINEE_ORG_BU_ID.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. A Knowledge Position (KP) is the only type of business unit to which a person can be directly assigned. (That is, the KNODE_USER_JOIN record cites the KP.) A KP may correspond to

  • a person that is a Penn Community member with a FAC, STAF, or STU affiliation, or with an auxiliary affiliation. (For the list of auxiliary affiliations, see PENN_COMMUNITY_MEMBER_STATUS.)
  • a person that is a University of Pennsylvania Health System (UPHS) nurse
  • a bureaucratic group that reflects an administrative subdivision used for UPHS employees
  • one of a number of privileged groups that classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system

A Knowledge Link user can be assigned to more than one KP. For example, John Doe could be assigned to one KP as a student and to another as a University employee with a FAC or STAF affiliation in the Penn Community. Jane Smith could be assigned to one KP as a UPHS employee, and to another as an auxiliary member of the Penn Community. A UPHS nurse is assigned both to a business unit in the entity/department hierarchy and to a business unit in a separate sub-branch for the Nursing Community. Roughly speaking, if the person has more than one active KP assignment, the primary one is the active KP for the person's

  • FAC or STAF affiliation in the Penn Community, or
  • UPHS departmental trainee group, or
  • STU affiliation in the Penn Community, or
  • auxiliary affiliation in the Penn Community

A course can be assigned to a KP either directly (where the KNODE_CRS_JOIN record cites the KP) or indirectly (where the KNODE_CRS_JOIN record cites a business unit that is above the KP in the business unit hierarchy). For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.

The PRIMARY_BUSINESS_UNIT_ID may include letters and/or numerals and/or other characters. The letters may be in upper case, lower case, or mixed case. The PRIMARY_BUSINESS_UNIT_ID for a UPHS business unit begins with HS; for a University or auxiliary business unit, it begins with UP. One of the qualifiers in a PRIMARY_BUSINESS_UNIT_ID may be the Penn ID, which is an 8-digit identification number assigned to an individual by the Penn Community system. No two persons have the same Penn ID.

Most PRIMARY_BUSINESS_UNIT_ID values are determined in the manner described below.

University primary business units

  • employee with a FAC or STAF affiliation in the Penn Community: UP.Penn ID
    • example: UP.12345678
  • student: UP.Penn ID.STU
    • example: UP.23456789.STU

UPHS primary business units

  • departmental trainee group: HS.entity.department.jobclass
    • example: HS.CRDTA.SUORA.A62
    • Entities are also known as process levels. Entities consist of departments (also known as cost centers or accounting units).
Auxiliary primary business units
  • UP.Penn ID.AUX
    • example: UP.34567890.AUX
Values:
List of values not available
PRIMARY_BUSINESS_UNIT_NAME

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

A phrase or string that describes the person's primary KP, the business unit to which the person is primarily assigned in Knowledge Link. It is possible for more than one business unit to have the same name. The PRIMARY_BUSINESS_UNIT_NAME value corresponds to a KNODE.NAME. See also PRIMARY_BUSINESS_UNIT_ID, PRIMARY_BUSINESS_UNIT_NUMBER, and TRAINEE_ORG_BU_NAME.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. A Knowledge Position (KP) is the only type of business unit to which a person can be directly assigned. (That is, the KNODE_USER_JOIN record cites the KP.) A KP may correspond to

  • a person that is a Penn Community member with a FAC, STAF, or STU affiliation, or with an auxiliary affiliation. (For the list of auxiliary affiliations, see PENN_COMMUNITY_MEMBER_STATUS.)
  • a person that is a University of Pennsylvania Health System (UPHS) nurse
  • a bureaucratic group that reflects an administrative subdivision used for UPHS employees
  • one of a number of privileged groups that classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system

A Knowledge Link user can be assigned to more than one KP. For example, John Doe could be assigned to one KP as a student and to another as a University employee with a FAC or STAF affiliation in the Penn Community. Jane Smith could be assigned to one KP as a UPHS employee, and to another as an auxiliary member of the Penn Community. A UPHS nurse is assigned both to a business unit in the entity/department hierarchy and to a business unit in a separate sub-branch for the Nursing Community. Roughly speaking, if the person has more than one active KP assignment, the primary one is the active KP for the person's

  • FAC or STAF affiliation in the Penn Community, or
  • UPHS departmental trainee group, or
  • STU affiliation in the Penn Community, or
  • auxiliary affiliation in the Penn Community

A course can be assigned to a KP either directly (where the KNODE_CRS_JOIN record cites the KP) or indirectly (where the KNODE_CRS_JOIN record cites a business unit that is above the KP in the business unit hierarchy). For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.

The PRIMARY_BUSINESS_UNIT_NAME may include letters and/or numerals and/or other characters. The letters may be in upper case, lower case, or mixed case. One of the qualifiers in a PRIMARY_BUSINESS_UNIT_NAME may be the person's PennKey (user name). For more information, see PENNKEY.

Most PRIMARY_BUSINESS_UNIT_NAME values are determined in the manner described below.

University primary business units

  • employee with a FAC or STAF affiliation in the Penn Community: UP.PennKey.name of home org.primary job appointment title, truncated at 50 characters
    • example: UP.franklin.DM-Sleep Medicine.RESEARCH INVESTIGATO
    • A University employee's home org. is the org. responsible for maintaining his or her record in the Payroll system. For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.
    • Information on the job class and title for the University employee's primary job appointment is available in the Salary Management data collection's documentation on EMPLOYEE_GENERAL and JOB_CLASS_GENERAL.
  • student: UP.PennKey.division.major
    • example: UP.janetdoe.NUG.ACNP
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly).

UPHS primary business units

  • departmental trainee group: Learner: department name: .jobclass (entity)
    • example: Learner: PAH Surgery - Orthopaedics: A62 (CRDTA)
    • Entities are also known as process levels. Entities consist of departments (also known as cost centers or accounting units).

Auxiliary primary business units

Values:
List of values not available
PRIMARY_BUSINESS_UNIT_NUMBER

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

A number used to uniquely identify the person's primary KP, the business unit to which the person is primarily assigned in Knowledge Link. The PRIMARY_BUSINESS_UNIT_NUMBER value corresponds to a KNODE.KNODE_ID. See also PRIMARY_BUSINESS_UNIT_ID, PRIMARY_BUSINESS_UNIT_NAME, and TRAINEE_ORG_BU_NUMBER.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. A Knowledge Position (KP) is the only type of business unit to which a person can be directly assigned. (That is, the KNODE_USER_JOIN record cites the KP.) A KP may correspond to

  • a person that is a Penn Community member with a FAC, STAF, or STU affiliation, or with an auxiliary affiliation. (For the list of auxiliary affiliations, see PENN_COMMUNITY_MEMBER_STATUS.)
  • a person that is a University of Pennsylvania Health System (UPHS) nurse
  • a bureaucratic group that reflects an administrative subdivision used for UPHS employees
  • one of a number of privileged groups that classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system

A Knowledge Link user can be assigned to more than one KP. For example, John Doe could be assigned to one KP as a student and to another as a University employee with a FAC or STAF affiliation in the Penn Community. Jane Smith could be assigned to one KP as a UPHS employee, and to another as an auxiliary member of the Penn Community. A UPHS nurse is assigned both to a business unit in the entity/department hierarchy and to a business unit in a separate sub-branch for the Nursing Community. Roughly speaking, if the person has more than one active KP assignment, the primary one is the active KP for the person's

  • FAC or STAF affiliation in the Penn Community, or
  • UPHS departmental trainee group, or
  • STU affiliation in the Penn Community, or
  • auxiliary affiliation in the Penn Community

A course can be assigned to a KP either directly (where the KNODE_CRS_JOIN record cites the KP) or indirectly (where the KNODE_CRS_JOIN record cites a business unit that is above the KP in the business unit hierarchy). For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.

Example: 21073

Values:
List of values not available
PROFILER_DATE_LAST_EDITED

Indexed - no
Format - date
May be null? yes

The date and time when the person's user record was last updated in the Penn Profiler system. The value might be null for some LMS_PERSON records.

Given the responses to its survey questions about the person's academic activities and job responsibilities, the Penn Profiler system determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Those who are currently required to take the Profiler survey ought to complete it at least once a year. They are also required to re-take the survey when there is a change in their academic activities or job responsibilities. University employees are required to re-take the survey when there is a change in the job class or the org. for their job appointment(s).

Business Objects hint: to select records for a particular date (say, 7/21/2008), set your query conditions to PROFILER_DATE_LAST_EDITED is greater than or equal to 7/21/2008 and PROFILER_DATE_LAST_EDITED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.) By default, just the date will appear in your report, but you can change the format of the cell to show just the time, if you so desire.

Example: 7/21/2008 3:32:34 AM

Values:
List of values not available
REMARKS

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

Comments stored in the person's user record in Knowledge Link. (This is also stored in the Data Warehouse in GEN21_USER.REMARKS.) The value is usually null.

Example: This is a generic trainer for EHRS.

Values:
List of values not available.
SUPERVISOR_EMAIL

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

The e-mail address of the person’s department chair, project principal investigator (PI), manager, or supervisor, as entered by the person the last time that he or she completed the Penn Profiler survey. The value is usually, but not always, a valid e-mail address. (The person might not have entered a fully qualified e-mail address, or might have made a typographical error when entering his or her supervisor's e-mail address.) SUPERVISOR_EMAIL may be stored in upper case, lower case, or mixed case.

SUPERVISOR_EMAIL is null if the person has never completed the Profiler survey. If the person has completed the Profiler survey more than once, SUPERVISOR_EMAIL data is not available for the surveys completed before the latest one. See also LAST_CERTIFICATION_DATE.

LMS_PERSON records for some people (such as housekeeping staff) might have a value for SUPERVISOR_EMAIL even though they have no value for EMAIL_ADDRESS and/or NOTIFICATION_EMAIL.

The value of SUPERVISOR_EMAIL is keyed in by hand, not selected from a list of values. It is the answer entered for the last question on the Profiler survey, which asks for the e-mail address of the person's department chair, project PI, manager, or supervisor. Faculty taking the survey are instructed to provide the e-mail address of their department chair. Staff (including temporary staff) are instructed to provide the e-mail address of their primary manager. Given the responses to its survey questions about the person's academic activities and job responsibilities, the Penn Profiler system determines the training courses that the person is currently required to take, and feeds the course assignments to Knowledge Link. Once a week, the Penn Profiler system e-mails notifications to the SUPERVISOR_EMAIL addresses specified in the surveys that were completed since the last such notifications were sent. The notifications list the people that completed those surveys, and include a link to a report that can be run to check the status of their currently required courses in Knowledge Link.

Examples: ivysuper@sas.upenn.edu; IVYSUPER@SAS.UPENN.EDU; IvySuper@sas.upenn.edu

Values:
List of values not available
TRAINEE_ORG_BU_ID

Indexed - yes
Format - varchar2 (40)
May be null? yes

A string that uniquely identifies the person's Trainee Org./BU, the business unit for the primary administrative group to which the person belongs. The TRAINEE_ORG_BU_ID value corresponds to a KNODE.IDENTIFIER. It may include letters and/or numerals and/or other characters. The letters may be in upper case, lower case, or mixed case. See also TRAINEE_ORG_BU_NAME, TRAINEE_ORG_BU_NUMBER, and PRIMARY_BUSINESS_UNIT_ID.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. A Trainee Org./BU corresponds to a departmental trainee group of University of Pennsylvania Health System (UPHS) employees, to a University Organization (org.), or to an auxiliary Penn Community affiliation. (Auxiliary members of the Penn Community are persons whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation.)

A Knowledge Position (KP) is the only type of business unit to which a person can be directly assigned. (That is, the KNODE_USER_JOIN record cites the KP.) A Knowledge Link user can be assigned to more than one KP. PRIMARY_BUSINESS_UNIT_ID indicates the person’s primary KP. If the person’s primary KP corresponds to a departmental trainee group of UPHS employees, the person’s Trainee Org./BU is the same as his or her primary KP. However, in many cases, the person’s primary KP is a business unit that includes only that person. In those cases, the person’s Trainee Org./BU is business unit that is the parent of the person’s primary KP—one step above that KP in the business unit hierarchy. (For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.)

If the person's primary business unit is then the person's trainee org is

the KP for the person's FAC or STAF affiliation in the Penn Community

the business unit that corresponds to the person’s home org. (the organization responsible for maintaining the person's record in the University's payroll system)
the KP for the person's UPHS departmental trainee group also the KP for the person's UPHS departmental trainee group
the KP for the person's STU affiliation in the Penn Community the business unit that corresponds to the person's primary academic division and primary major
the KP for the person's auxiliary affiliation in the Penn Community the business unit that corresponds to the person's auxiliary affiliation in the Penn Community

Most TRAINEE_ORG_BU_ID values are determined in the manner described below.

University Trainee Org./BUs

  • employees with a FAC or STAF affiliation in the Penn Community: UP.org. code
    • example: UP.9937
    • The trainee org. for an employee with a FAC or STAF affiliation in the Penn Community is the business unit for the employee's home org. For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.
  • students: UP.STU-.academic division.major
    • examples: UP.STU-.NUG, UP.STU-.NUG.ACNP
    • For a student, TRAINEE_ORG_BU_NAME and TRAINEE_ORG_BU_ID have the same value.
    • A student's trainee org. is the business unit for the student's primary academic division and primary major, per the SRS_DIVISION and SRS_MAJOR in the record for the student in the Penn Community AFFILIATION table. For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly)

UPHS Trainee Org./BUs

  • departmental trainee group: HS.entity.department.jobclass
    • example: HS.CRDTA.SUORA.A62
    • Entities are also known as process levels. Entities consist of departments (also known as cost centers or accounting units).

Auxiliary Trainee Org./BUs

Values:
List of values not available
TRAINEE_ORG_BU_NAME

Indexed - yes
Format - varchar2 (80)
May be null? yes

A phrase or string that describes the person's Trainee Org./BU, the business unit for the primary administrative group to which the person belongs. The TRAINEE_ORG_BU_NAME value corresponds to a KNODE.NAME. It may include letters and/or numerals and/or other characters. The letters may be in upper case, lower case, or mixed case. See also TRAINEE_ORG_BU_ID, TRAINEE_ORG_BU_NUMBER, and PRIMARY_BUSINESS_UNIT_NAME.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. A Trainee Org./BU corresponds to a departmental trainee group of University of Pennsylvania Health System (UPHS) employees, to a University Organization (org.), or to an auxiliary Penn Community affiliation. (Auxiliary members of the Penn Community are persons whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation.)

A Knowledge Position (KP) is the only type of business unit to which a person can be directly assigned. (That is, the KNODE_USER_JOIN record cites the KP.) A Knowledge Link user can be assigned to more than one KP. PRIMARY_BUSINESS_UNIT_ID indicates the person’s primary KP. If the person’s primary KP corresponds to a departmental trainee group of UPHS employees, the person’s Trainee Org./BU is the same as his or her primary KP. However, in many cases, the person’s primary KP is a business unit that includes only that person. In those cases, the person’s Trainee Org./BU is business unit that is the parent of the person’s primary KP—one step above that KP in the business unit hierarchy. (For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.)

If the person's primary business unit is then the person's trainee org is

the KP for the person's FAC or STAF affiliation in the Penn Community

the business unit that corresponds to the person’s home org. (the organization responsible for maintaining the person's record in the University's payroll system)
the KP for the person's UPHS departmental trainee group also the KP for the person's UPHS departmental trainee group
the KP for the person's STU affiliation in the Penn Community the business unit that corresponds to the person's primary academic division and primary major
the KP for the person's auxiliary affiliation in the Penn Community the business unit that corresponds to the person's auxiliary affiliation in the Penn Community

Most TRAINEE_ORG_BU_NAME values are determined in the manner described below.

University Trainee Org./BUs

  • employee with a FAC or STAF affiliation in the Penn Community: the name of the person's home org. (see ORG_CODES.DESCRIPTION), truncated at 50 characters
    • example: Journal of Biochemistry and Molecular Biology Educ
    • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.
  • student: UP.STU-.academic division.major
    • examples: UP.STU-.NUG, UP.STU-.NUG.ACNP
    • For a student, TRAINEE_ORG_BU_NAME and TRAINEE_ORG_BU_ID have the same value.
    • A student's trainee org. is the business unit for the student's primary academic division and primary major, per the SRS_DIVISION and SRS_MAJOR in the record for the student in the Penn Community AFFILIATION table. For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly)

UPHS Trainee Org./BUs

  • departmental trainee group: Learner: department name: .jobclass (entity)
    • example: Learner: PAH Surgery - Orthopaedics: A62 (CRDTA)
    • Entities are also known as process levels. Entities consist of departments (also known as cost centers or accounting units).

Auxiliary Trainee Org./BUs

Values:
List of values not available
TRAINEE_ORG_BU_NUMBER

Indexed - yes
Format - number (10)
May be null? yes

A number used to uniquely identify the person's Trainee Org./BU, the business unit for the primary administrative group to which the person belongs. The TRAINEE_ORG_BU_NUMBER value corresponds to a KNODE.KNODE_ID. See also TRAINEE_ORG_BU_ID, TRAINEE_ORG_BU_NAME, and PRIMARY_BUSINESS_UNIT_NUMBER.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. A Trainee Org./BU corresponds to a departmental trainee group of University of Pennsylvania Health System (UPHS) employees, to a University Organization (org.), or to an auxiliary Penn Community affiliation. (Auxiliary members of the Penn Community are persons whose training records and current training assignments are stored in Knowledge Link, but who are not UPHS employees or persons with a FAC, STAF, or STU affiliation.)

A Knowledge Position (KP) is the only type of business unit to which a person can be directly assigned. (That is, the KNODE_USER_JOIN record cites the KP.) A Knowledge Link user can be assigned to more than one KP. PRIMARY_BUSINESS_UNIT_ID indicates the person’s primary KP. If the person’s primary KP corresponds to a departmental trainee group of UPHS employees, the person’s Trainee Org./BU is the same as his or her primary KP. However, in many cases, the person’s primary KP is a business unit that includes only that person. In those cases, the person’s Trainee Org./BU is business unit that is the parent of the person’s primary KP—one step above that KP in the business unit hierarchy. (For more information on the business unit hierarchy, see the documentation on PARENT_ID and TYPE in the KNODE table.)

If the person's primary business unit is then the person's trainee org is

the KP for the person's FAC or STAF affiliation in the Penn Community

the business unit that corresponds to the person’s home org. (the organization responsible for maintaining the person's record in the University's payroll system)
the KP for the person's UPHS departmental trainee group also the KP for the person's UPHS departmental trainee group
the KP for the person's STU affiliation in the Penn Community the business unit that corresponds to the person's primary academic division and primary major
the KP for the person's auxiliary affiliation in the Penn Community the business unit that corresponds to the person's auxiliary affiliation in the Penn Community

Example: 45946

Values:
List of values not available
UNIV_PRIMARY_APPT_JOB_CLASS

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

The 6-digit job class code indicating the University employee's primary appointment job classification. UNIV_PRIMARY_APPT_JOB_CLASS is used only for University employees. Its value is null for people that are not University employees. A person that is both a UPHS employee and a University employee has a non-null UNIV_PRIMARY_APPT_JOB_CLASS.

The person's UNIV_PRIMARY_APPT_JOB_CLASS value is the person's "University Census Report" primary appointment job classification value. For more information about University primary appointments, see EMPLOYEE_GENERAL.PRIMARY_APPT_JOB_CLASS. For more information on the job title and other attributes associated with a University job class code, see the documentation for JOB_CLASS_GENERAL. To retrieve the attributes of a person's UNIV_PRIMARY_APPT_JOB_CLASS, select the attributes where LMS_PERSON.UNIV_PRIMARY_APPT_JOB_CLASS = DWADMIN.JOB_CLASS_GENERAL.JOB_CLASS.

Note: UNIV_PRIMARY_APPT_JOB_CLASS indicates the person's most recent University primary appointment job classification. A person who was once, but is no longer, a University employee has a non-null UNIV_PRIMARY_APPT_JOB_CLASS. To see whether the person is currently a University employee, check the Y/N indicator DWADMIN.EMPLOYEE_GENERAL_V.CURRENTLY_EMPLOYED where LMS_PERSON.PENN_ID = DWADMIN.EMPLOYEE_GENERAL_V.PENN_ID.

Example: 216000 (PROFESSOR A)

Values:
Refer to DWADMIN.JOB_CLASS_GENERAL_V for values.
UNIV_PRIMARY_APPT_ORG

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

The 4-digit number that represents the Organization responsible for the University employee's primary job appointment. UNIV_PRIMARY_APPT_ORG is used only for University employees. Its value is null for people that are not University employees. A person that is both a UPHS employee and a University employee has a non-null UNIV_PRIMARY_APPT_JOB_CLASS.

The person's UNIV_PRIMARY_APPT_ORG value is the person's "University Census Report" primary appointment Organization value. For more information about University primary appointments, see EMPLOYEE_GENERAL.PRIMARY_APPT_JOB_CLASS.

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. For more information on the name ("description") and other attributes associated with a University Organization, see the documentation for the ORG_CODES table. To retrieve the attributes of a person's UNIV_PRIMARY_APPT_ORG, select the attributes where LMS_PERSON.UNIV_PRIMARY_APPT_ORG = DWADMIN.ORG_CODES.ORGANIZATION_CODE.

Note: UNIV_PRIMARY_APPT_ORG indicates Organization responsible for the person's most recent University primary appointment job classification. A person who was once, but is no longer, a University employee has a non-null UNIV_PRIMARY_APPT_ORG. To see whether the person is currently a University employee, check the Y/N indicator DWADMIN.EMPLOYEE_GENERAL_V.CURRENTLY_EMPLOYED where LMS_PERSON.PENN_ID = DWADMIN.EMPLOYEE_GENERAL_V.PENN_ID.

Example: 1301 (Bioengineering)

Values:
Refer to DWADMIN.ORG_CODES for values.
UPHS_COMPANY_NUMBER

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

A number that uniquely identifies the person's company in the Lawson payroll system used by the University of Pennsylvania Health System (UPHS). (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_N1.) UPHS_COMPANY_NUMBER is a factor in compliance reports in Knowledge Link.

UPHS_COMPANY_NUMBER is used only for UPHS employees. Its value is null or 0 for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-zero UPHS_COMPANY_NUMBER.

Example: 8888

Values:
List of values not available
UPHS_DEPARTMENT_CODE

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

A string that uniquely identifies the person's department in the Lawson payroll system used by the University of Pennsylvania Health System (UPHS). (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_V2.) Departments are also known as a cost centers or accounting units. See also UPHS_DEPARTMENT_NAME and UPHS_DEPARTMENT_NAME_AS_IS.

UPHS_DEPARTMENT_CODE is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null UPHS_DEPARTMENT_CODE.

Example: UOB09 (OB-GYN Oncol 0-11021)

Values:
List of values not available
UPHS_DEPARTMENT_NAME

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

The name of the person's department in the Lawson payroll system used by the University of Pennsylvania Health System (UPHS). The value is stored in upper case to facilitate record selection conditions and sorting.

Departments are also known as a cost centers or accounting units. See also UPHS_DEPARTMENT_CODE and UPHS_DEPARTMENT_NAME_AS_IS.

UPHS_DEPARTMENT_NAME is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null value for UPHS_DEPARTMENT_NAME.

Example: 'OB-GYN ONCOL 0-11021' The value is stored without the surrounding quotes.

Values
List of values not available
UPHS_DEPARTMENT_NAME_AS_IS

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

As stored in Knowledge Link, the name of the person's department in the Lawson payroll system used by the University of Pennsylvania Health System (UPHS). (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_V3.) Departments are also known as a cost centers or accounting units. See also UPHS_DEPARTMENT_CODE and UPHS_DEPARTMENT_NAME.

UPHS_DEPARTMENT_NAME_AS_IS is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null value for UPHS_DEPARTMENT_NAME_AS_IS.

Example: 'OB-GYN Oncol 0-11021' The value is stored without the surrounding quotes.

Values:
List of values not available
Not Available
UPHS_EMPLOYEE_NUMBER

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

A numeric value, from 1 to 10 digits long, that uniquely identifies the person in the Lawson payroll system used by the University of Pennsylvania Health System (UPHS). (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_N2.)

UPHS_EMPLOYEE_NUMBER is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null UPHS_EMPLOYEE_NUMBER.

For other data elements that uniquely identify the person, see PENN_ID, PENNKEY, USER_REC_ID, and HIBERNATE_ID.

Example: 501952

Values:
List of values not available
UPHS_ENTITY_CODE

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

The abbreviation for the University of Pennsylvania Health System (UPHS) entity where the person has his or her UPHS job appointment. The value is stored in upper case. (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_V1.)

Also known as a process level, an entity is a division of UPHS that addresses one of the Health System's various areas and levels of service, support and practices. Entities consist of departments (also known as cost centers or accounting units).

UPHS_ENTITY_CODE is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null UPHS_ENTITY_CODE.

Values:
CCA   (Clinical Care Associates)
CCNJ (Clinical Care Associates -
New Jersey)

CNTRT (Contractors)
CORP (Corporate Services)
CPUP (Clinical Practices of the University
of Pennsylvania)

CRDTA (PAH credentialed non 2000 employees)
CRDTC (CCA credentialed non 2000 employees)
CRDTL (HUP credentialed non 2000 employees)
CRDTP (PMC credentialed non 2000 employees)
DAHR Rollup
HCHS (Penn Home Care and Hospice Services)
HUP (Hospital of the University of
Pennsylvania)

JRB (John Rhea Barton Practice)
MGMT (Management Staff)
PAH (Pennsylvania Hospital)
PAHHM (Pennsylvania Hospital - Hall Mercer
Community Mental Health)

PMC (Presbyterian Medical Center) SCON (UPHS System Confidential)
UPHS (University of Pennsylvania Health
System)

URSVC (Urology Associates)
WISS (Wissahickon Hospice)
UPHS_JOB_CODE

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

The code indicating the person's University of Pennsylvania Health System (UPHS) job. The code is used to identify the job in the Lawson payroll system used by UPHS. (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_V4.) See also UPHS_JOB_TITLE.

UPHS_JOB_CODE is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null value for UPHS_JOB_CODE.

Example: Z9001 (Physician)

Values:
List of values not available
UPHS_JOB_TITLE

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

The title of the person's University of Pennsylvania Health System (UPHS) job, per the Lawson payroll system used by UPHS. (This is also stored in the Data Warehouse in GEN21_USER.CUSTOM_V5.) See also UPHS_JOB_CODE.

UPHS_JOB_TITLE is used only for UPHS employees. Its value is null for people that are not UPHS employees. A person that is both a UPHS employee and a University employee has a non-null value for UPHS_JOB_TITLE.

Example: Physician

Values:
List of values not available
USER_REC_ID

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

A numeric value that uniquely identifies the person within the Knowledge Link system. (This is also stored in the Data Warehouse in GEN21_USER.USER_REC_ID.) The person may play one or more parts within Knowledge Link—a trainee, an instructor, an administrator, etc.

Some tables in the Data Warehouse's Learning Management data collection store data about Knowledge Link users but do not store the users' Penn IDs. USER_REC_ID enables the LMS_PERSON table to be joined to those tables.

USER_REC_ID is null if EXTRACT_SOURCE is 'P'.

For other data elements that uniquely identify the person, see PENN_ID, PENNKEY, HIBERNATE_ID, and UPHS_EMPLOYEE_NUMBER.

Example: 10159

Values:
Refer to the LMS_PERSON table or the 
  GEN21_USER table for values.

 

LMS_PERSON Table   Tables and Data Elements  Learning 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