Penn Computing

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

LMS_TRAINEE_BU_COURSE_ASSIGN - Data Element Index

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

 

Data element Definition
BU_CRS_ASSIGNMNT_STATUS

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

An upper case letter indicating whether or not the course version (CO_REC_ID) is actively assigned to the trainee (USER_REC_ID) per this mandatory assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID).

For all LMS_TRAINEE_BU_COURSE_ASSIGN records, BU_CRS_ASSIGNMNT_STATUS is 'A' (active).

A trainee registers for a course iteration, which is an offering of a particular version of a course (CO_MAS_ID). A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee.

BU_CRS_ASSIGNMNT_STATUS is one of the factors that determine whether the course is currently required for the trainee. See CURRENTLY_REQUIRED.

Values:
A (this mandatory assignment of the course version to the
   trainee is currently active)
I (this mandatory assignment of the course version to the trainee is currently inactive)
CO_MAS_ID

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

The number used within the Knowledge Link system as the unique identifier for the course, which is assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). A course is assigned to a trainee if a course assignment specifies that a version of the course (CO_REC_ID) has been assigned to a business unit that includes the trainee.

See also COURSE_MASTER_ID, COURSE_TITLE, USER_REC_ID, PENN_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

To retrieve the attributes of the course, query the LMS_COURSE_MASTER table where LMS_TRAINEE_BU_COURSE_ASSIGN.CO_MAS_ID = LMS_COURSE_MASTER.CO_MAS_ID.

Examples: 12437 (UNIV_ALL_ALL_PROFILER ); 10252 (UPHS_HUP_NURS_ORT131)

Values:
Refer to the LMS_COURSE_MASTER
or COURSE_MASTER table for values. Note: some of the courses in those tables have no associated LMS_TRAINEE_BU_COURSE_ASSIGN
records.
CO_REC_ID

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

The number used within the Knowledge Link system as the unique identifier for the course version that has been assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID).

A trainee registers for a course iteration, which is an offering of a particular version of a course (CO_MAS_ID). A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee.

See also PENN_ID, FIRST_NAME, MIDDLE_INITIAL, LAST_NAME, COURSE_MASTER_ID, and COURSE_TITLE.

To retrieve the attributes of the course version, query the COURSE_OBJECT table where LMS_TRAINEE_BU_COURSE_ASSIGN.CO_REC_ID = COURSE_OBJECT.CO_REC_ID.

Examples: 12675 (UNIV_ALL_ALL_PROFILER_v1; PennProfiler-Required Training Assessment-VPR); 10272 (UPHS_HUP_NURS_ORT131_v1; Nurse Residency Program - HUP); 10000 (UPHS_ALL_WORK_HIPAA105_v1; HIPAA Privacy Overview for the Workforce [Learning Module Only] - UPHS)

Values:
Refer to the COURSE_OBJECT table for values.
Note:  some of the course versions in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
COMPLIANT

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

A Yes/No flag indicating whether the trainee (USER_REC_ID) is
compliant with the requirement imposed by this mandatory assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of the course version (CO_REC_ID) to the trainee.

 
LMS_TRAINEE_BU_COURSE_ASSIGN data element
COMPLETE Mandatory Assignment Grandfathered CURRENTLY_REQUIRED STATUS_DUEDATE_DESCRIPTION COMPLIANT
any value
'Y'
'Y'
'N'
'Neither Soon Due nor Past Due'
'Y'
no
'Y'
'N'
'Y'
any value
'N'
yes
'Y'
'N'
'Y'
'Neither Soon Due nor Past Due'
'Y'
yes
'Y'
'N'
'Y'
'Soon Due'
'Y'
yes
'Y'
'N'
'Y'
'Past Due'
'N'

The trainee is compliant with the requirement imposed by this mandatory assignment if one of the following is true:

  • the trainee is grandfathered for the course per this assignment
  • the trainee has completed an iteration of the course, and is not overdue to re-take it per this assignment. For information on the trainee's latest completion of the course (if any), see the record in the LMS_REGISTRATION table where LMS_TRAINEE_BU_COURSE_ASSIGN.CO_MAS_ID = LMS_REGISTRATION.CO_MAS_ID and LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_REGISTRATION.USER_REC_ID and LMS_REGISTRATION.LAST_COURSE_COMPLETION_FLAG = 'Y'

If the trainee has only one currently required course assignment for the course (CO_MAS_ID), the trainee's COMPLIANT status for that assignment is the same as the trainee's COMPLIANT status for the course.

If the trainee has multiple currently required assignments for the course, the assignment with the lowest non-null value of DUE_DATE is the one with the trainee's COMPLIANT status for the course. For the trainee's COMPLIANT status for the course, see the LMS_TRAINEE_COURSE_COMPLIANCE table, the LMS_TRAINEE_COURSE_ASSIGN table, or the LMS_TRAINEE_COURSE_COMPLIANCE table.

Values:
Y (the trainee is compliant with the requirement
   to take the course per this mandatory course assignment)
N (the trainee is not compliant with the requirement
   to take the course per this mandatory course assignment)
COURSE_ASSIGNMENT_BU_ID

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

A string that uniquely identifies the business unit that has the course version (CO_REC_ID) assigned to it as a mandatory course and that includes the trainee (USER_REC_ID), per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID).

See also CO_MAS_ID, COURSE_MASTER_ID, COURSE_TITLE, PENN_ID, FIRST_NAME, MIDDLE_INITIAL, LAST_NAME, COURSE_ASSIGNMENT_BU_NUMBER, COURSE_ASSIGNMENT_BU_NAME, TRAINEE_ASSIGNMENT_BU_NUMBER, TRAINEE_ASSIGNMENT_BU_ID, and TRAINEE_ASSIGNMENT_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. Business unit X includes a trainee if that trainee is actively assigned to X (see the KNODE_USER_JOIN table) or to a business unit that that falls below X 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 COURSE_ASSIGNMENT_BU_ID is the KNODE.IDENTIFIER where LMS_TRAINEE_BU_COURSE_ASSIGN.COURSE_ASSIGNMENT_BU_NUMBER = KNODE.KNODE_ID. For information on how the COURSE_ASSIGNMENT_BU_ID value is formatted, see the data element documentation for KNODE.IDENTIFIER.

Examples: 'UP.10001205'; 'UP.0101'; 'HS.BCCD' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
COURSE_ASSIGNMENT_BU_NAME

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

A phrase or string that describes the business unit that has the course version (CO_REC_ID) assigned to it as a mandatory course and that includes the trainee (USER_REC_ID), per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). It is possible for more than one business unit to have the same name.

See also CO_MAS_ID, COURSE_MASTER_ID, COURSE_TITLE, PENN_ID, FIRST_NAME, MIDDLE_INITIAL, LAST_NAME, COURSE_ASSIGNMENT_BU_NUMBER, COURSE_ASSIGNMENT_BU_ID, TRAINEE_ASSIGNMENT_BU_NUMBER, TRAINEE_ASSIGNMENT_BU_ID, and TRAINEE_ASSIGNMENT_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. Business unit X includes a trainee if that trainee is actively assigned to X (see the KNODE_USER_JOIN table) or to a business unit that that falls below X 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 COURSE_ASSIGNMENT_BU_NAME is the KNODE.NAME where LMS_TRAINEE_BU_COURSE_ASSIGN.COURSE_ASSIGNMENT_BU_NUMBER = KNODE.KNODE_ID. For information on how the COURSE_ASSIGNMENT_BU_NAME value is formatted, see the data element documentation for KNODE.NAME.

Examples: 'UP.jsheehan.External Affairs.ASSOC DEAN ADMIN'; 'Anthropology'; 'Billing Compliance (BCCD)' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
COURSE_ASSIGNMENT_BU_NUMBER

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

A number used to uniquely identify the business unit that has the course version (CO_REC_ID) assigned to it as a mandatory course and that includes the trainee (USER_REC_ID), per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). The COURSE_ASSIGNMENT_BU_NUMBER value corresponds to a KNODE.KNODE_ID.

See also CO_MAS_ID, COURSE_MASTER_ID, COURSE_TITLE, PENN_ID, FIRST_NAME, MIDDLE_INITIAL, LAST_NAME, COURSE_ASSIGNMENT_BU_NAME, COURSE_ASSIGNMENT_BU_ID, TRAINEE_ASSIGNMENT_BU_NUMBER, TRAINEE_ASSIGNMENT_BU_ID, and TRAINEE_ASSIGNMENT_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. Business unit X includes a trainee if that trainee is actively assigned to X (see the KNODE_USER_JOIN table) or to a business unit that that falls below X 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.)

Examples: 10022, 44239, 61352

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
COURSE_MASTER_ID

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

A string that uniquely identifies the course, which is assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). A course is assigned to a trainee if a course assignment specifies that a version of the course (CO_REC_ID) has been assigned to a business unit that includes the trainee.

See also CO_MAS_ID, COURSE_TITLE, PENN_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

To retrieve the attributes of the course, query the LMS_COURSE_MASTER table where LMS_TRAINEE_BU_COURSE_ASSIGN.COURSE_MASTER_ID = LMS_COURSE_MASTER.COURSE_MASTER_ID.

The COURSE_MASTER_ID may include letters and/or numerals and/or other characters. The letters in COURSE_MASTER_ID may be in upper case, lower case, or mixed case. Most COURSE_MASTER_ID values consist of four segments, in the following format:

1. the enterprise that developed the course, followed by an underscore. Examples: UNIV (the University); UPHS (the University of Pennsylvania Health System); SOM (the School of Medicine)
2. the intended audience for the course at the entity, school or center level, followed by an underscore. Examples: MED (Medicine); CPP (Clinical Practices); ALL (all entities)
3. the intended audience for the course at the level of the division within the enterprise, followed by an underscore. Examples: EHRS (Environmental Health and Radiation Safety); NURS (Nursing); ALL (all schools or divisions)
4. the course identifier code (determined by the course developer)

Examples: UNIV_ALL_ALL_PROFILER; UPHS_HUP_NURS_ORT131

Values:
Refer to the LMS_COURSE_MASTER
or COURSE_MASTER table for values. Note: some of the courses in those tables have no associated LMS_TRAINEE_BU_COURSE_ASSIGN
records.
COURSE_OWNER_BU_ID

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

A string that uniquely identifies the business unit that owns the course version (CO_REC_ID) assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). See also COURSE_OWNER_BU_NAME and COURSE_OWNER_BU_NUMBER.

Knowledge Communities (KC) and Knowledge Microcommunities (KMCs) are the types of business units that are course version owners. The KCs that own course versions correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments. (For further information on business units, see the documentation for the KNODE table. The business unit hierarchy is described in the documentation for PARENT_ID in the KNODE table.)

The owner of the course version is one of the criteria used to determine what course versions (if any) are included on the list of course versions that a given user can assign. For more information, see the data element documentation for COURSE_OBJECT.KNODE_ID.

The COURSE_OWNER_BU_ID is the KNODE.IDENTIFIER where LMS_TRAINEE_BU_COURSE_ASSIGN.COURSE_OWNER_BU_NUMBER = KNODE.KNODE_ID. For information on how the COURSE_OWNER_BU_ID value is formatted, see the data element documentation for KNODE.IDENTIFIER.

Examples: 'UP.EHRS'; 'HS.PATREG' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
COURSE_OWNER_BU_NAME

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

A phrase or string that describes the business unit that owns the course version (CO_REC_ID) assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). It is possible for more than one business unit to have the same name. See also COURSE_OWNER_BU_ID and COURSE_OWNER_BU_NUMBER.

Knowledge Communities (KC) and Knowledge Microcommunities (KMCs) are the types of business units that are course version owners. The KCs that own course versions correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments. (For further information on business units, see the documentation for the KNODE table. The business unit hierarchy is described in the documentation for PARENT_ID in the KNODE table.)

The owner of the course version is one of the criteria used to determine what course versions (if any) are included on the list of course versions that a given user can assign. For more information, see the data element documentation for COURSE_OBJECT.KNODE_ID.

The COURSE_OWNER_BU_NAME is the KNODE.NAME where LMS_TRAINEE_BU_COURSE_ASSIGN.COURSE_OWNER_BU_NUMBER = KNODE.KNODE_ID. For information on how the COURSE_OWNER_BU_NAME value is formatted, see the data element documentation for KNODE.NAME.

Examples: 'Environmental Health and Radiation Safety Parent'; 'Patient Registration' The value is stored without the surrounding quotes.

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
COURSE_OWNER_BU_NUMBER

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

The number used within the Knowledge Link system as the unique identifier for the business unit that owns the course version (CO_REC_ID) assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). The COURSE_OWNER_BU_NUMBER value corresponds to a KNODE.KNODE_ID. See also COURSE_OWNER_BU_ID and COURSE_OWNER_BU_NAME.

Knowledge Communities (KC) and Knowledge Microcommunities (KMCs) are the types of business units that are course version owners. The KCs that own course versions correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments. (For further information on business units, see the documentation for the KNODE table. The business unit hierarchy is described in the documentation for PARENT_ID in the KNODE table.)

The owner of the course version is one of the criteria used to determine what course versions (if any) are included on the list of course versions that a given user can assign. For more information, see the data element documentation for COURSE_OBJECT.KNODE_ID.

Example: 44922 (Environmental Health and Radiation Safety Parent [UP.EHRS])

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.

COURSE_TITLE

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

The latest title of the course, which is assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). A course is assigned to a trainee if a course assignment specifies that a version of the course (CO_REC_ID) has been assigned to a business unit that includes the trainee.

See also CO_MAS_ID, COURSE_MASTER_ID, PENN_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

The latest title of the course is title of the version of the course that has the highest version number. (This is usually, but not always, the course version whose iterations are scheduled in the future, or were scheduled most recently in the past. It is not necessarily the same as the version to which the trainee has been assigned.) The course per se has no title specified in Knowledge Link, but the title of the course's latest version may be considered to be the current title of the course.

Most course version titles consist of three parts, in the following format: segments identify both the content and provider of the course version, and follow the following format:

1. text briefly identifying the course content
2. a dash ('-') with spaces on either side, to serve as a separator
3. the enterprise that developed the course. Examples: UNIV (the University); UPHS (the University of Pennsylvania Health System); SOM (the School of Medicine)

COURSE_TITLE is taken from the LMS_COURSE_MASTER table where LMS_TRAINEE_BU_COURSE_ASSIGN.CO_MAS_ID = LMS_COURSE_MASTER.CO_MAS_ID. Further information about the course is available in the LMS_COURSE_MASTER table.

Example: 'Bloodborne Pathogens for Childcare Center Employees - EHRS' The value is stored without the surrounding quotes.

Values:
Refer to the LMS_COURSE_MASTER table for values.
Note:  some of the courses in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN
records.
CURRENTLY_REQUIRED

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

A Yes/No flag indicating whether or not the course (CO_MAS_ID) is currently required for the trainee (USER_REC_ID) per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). See also COMPLIANT.

If the course is actively assigned as a mandatory course to a business unit that currently includes the trainee (as is the case for all LMS_TRAINEE_BU_COURSE_ASSIGN records), and the trainee is not grandfathered for the course, CURRENTLY_REQUIRED is 'Y'. See BU_CRS_ASSIGNMNT_STATUS, MANDATORY, and GRANDFATHERED.

If the trainee has at least one currently required course assignment for the course (CO_MAS_ID), the course is currently required for the trainee. For the trainee's CURRENTLY_REQUIRED status for the course, see the LMS_TRAINEE_COURSE_ASSIGN table, or the LMS_TRAINEE_COURSE_COMPLIANCE table. Note: if there is no record for the trainee and course in either of those tables, the course is not currently required for the trainee.

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on mandatory course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

One of the factors that determine whether Knowledge Link sends E-mail Notifications about a course to a trainee is whether the course is currently required for the trainee. For more information, see the data element documentation for COURSE_OBJECT.SD_BOUNDARY.

Values:
Y (the course is currently required for the 
   trainee, per this mandatory course assignment)
N (the course is currently optional for the 
   trainee, per this mandatory course assignment)
DATE_BU_CRS_ASSIGNMNT_CREATED

Indexed - no
Format - date
May be null? yes

The date when the record was created for the assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of the course version (CO_REC_ID) to the trainee (USER_REC_ID) as a mandatory course. See also DATE_BU_CRS_ASSIGNMNT_MODIFIED.

The value of DATE_BU_CRS_ASSIGNMNT_CREATED might or might not include the time.

Business Objects hints:

  • 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.
  • To select records that were created on a particular date (say, 7/21/2008), set your query conditions to DATE_BU_CRS_ASSIGNMNT_CREATED is greater than or equal to 7/21/2008 and DATE_BU_CRS_ASSIGNMNT_CREATED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

The USER_COURSES table is the main source of the data in the LMS_TRAINEE_BU_COURSE_ASSIGN table. DATE_BU_CRS_ASSIGNMNT_CREATED is the date the source record was created in the USER_COURSES table. It may or may not be the same as the date when the record was created in the KNODE_CRS_JOIN table to track the assignment of the course version to a business unit that includes the trainee. (See COURSE_ASSIGNMENT_BU_NUMBER and KCJ_REC_ID.)

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on mandatory course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

Examples: 6/30/2008; 12/18/2008; 3/13/2006 8:14:46 AM

Values:
List of values not available
DATE_BU_CRS_ASSIGNMNT_MODIFIED

Indexed - no
Format - date
May be null? yes

The date when the last update was made to the record for the assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of the course version (CO_REC_ID) to the trainee (USER_REC_ID) as a mandatory course. See also DATE_BU_CRS_ASSIGNMNT_CREATED.

The DATE_BU_CRS_ASSIGNMNT_MODIFIED is either the same as or later than the DATE_BU_CRS_ASSIGNMNT_CREATED.

Business Objects hints:

  • 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.
  • To select records that were updated on a particular date (say, 7/21/2008), set your query conditions to DATE_BU_CRS_ASSIGNMNT_MODIFIED is greater than or equal to 7/21/2008 and DATE_BU_CRS_ASSIGNMNT_MODIFIED is less than 7/22/2008. (The system will supply the time--12:00:00 AM--for both dates.)

The USER_COURSES table is the main source of the data in the LMS_TRAINEE_BU_COURSE_ASSIGN table. DATE_BU_CRS_ASSIGNMNT_CREATED is the date the source record was created in the USER_COURSES table. It may or may not be the same as the date when the record was created in the KNODE_CRS_JOIN table to track the assignment of the course version to a business unit that includes the trainee. (See COURSE_ASSIGNMENT_BU_NUMBER and KCJ_REC_ID.)

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on mandatory course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

Examples: 6/30/2008; 12/18/2008; 3/13/2006 8:14:46 AM

Values:
List of values not available
DUE_DATE

Indexed - no
Format - date
May be null? yes

The date when the trainee (USER_REC_ID) is next due to complete an iteration of the currently required course (CO_MAS_ID), per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). See also PERIODICITY.

DUE_DATE is null if any of the following is true:

  • GRANDFATHERED is 'Y'
  • No initial due date was specified for the mandatory course assignment, and the trainee has yet to complete an iteration of the course.
    • The assignment's initial due date is stored in LMS_GOVERNING.INITIAL_DUE_DATE where LMS_TRAINEE_BU_COURSE_ASSIGN.KCJ_REC_ID = LMS_GOVERNING.KCJ_REC_ID.
    • For information on the trainee's latest completion of the course (if any), see the record in the LMS_REGISTRATION table where LMS_TRAINEE_BU_COURSE_ASSIGN.CO_MAS_ID = LMS_REGISTRATION.CO_MAS_ID and LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_REGISTRATION.USER_REC_ID and LMS_REGISTRATION.LAST_COURSE_COMPLETION_FLAG = 'Y'
  • PERIODICITY is null or 0, and the trainee has completed an iteration of the course.

DUE_DATE is one of the factors that determine whether the trainee (USER_REC_ID) is compliant with the requirement imposed by this mandatory assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of the course version (CO_REC_ID) to the trainee. See COMPLIANT.

If the trainee has only one currently required course assignment for the course (CO_MAS_ID), the trainee's DUE_DATE for that assignment is the same as the trainee's DUE_DATE for the course.

If the trainee has multiple currently required assignments for the course, the lowest non-null value of DUE_DATE in the set of those assignments is the value of DUE_DATE for the course. For the trainee's DUE_DATE for the course, see the LMS_TRAINEE_COURSE_COMPLIANCE table, the LMS_TRAINEE_COURSE_ASSIGN table, or the LMS_TRAINEE_COURSE_COMPLIANCE table.

The trainee's DUE_DATE for the course is one of the factors that determine whether Knowledge Link sends E-mail Notifications about a course to a trainee. For more information, see the data element documentation for COURSE_OBJECT.SD_BOUNDARY.

Example: 11/19/2009 8:19:41 PM

Values:
List of values not available
EFFECTIVE_DATE

Indexed - no
Format - date
May be null? yes

The date when this mandatory course assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) takes effect. The value may be null.

The trainee is grandfathered for this mandatory course assignment if the trainee's DEPT_START_DATE falls before the EFFECTIVE_DATE. See GRANDFATHERED.

The trainee's DEPT_START_DATE is stored in LMS_PERSON.DEPT_START_DATE where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Examples: 11/19/2009 8:19:41 PM

Values:
List of values not available
FIRST_NAME

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

The given name of the trainee (USER_REC_ID), stored in upper case to facilitate record selection conditions and sorting. See also MIDDLE_INITIAL and LAST_NAME.

The FIRST_NAME is taken from LMS_PERSON.FIRST_NAME where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: ABIGAIL

Values:
List of values not available.
GRANDFATHERED

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

A Yes/No flag indicating whether or not the trainee is grandfathered for this mandatory course assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). See also CURRENTLY_REQUIRED.

GRANDFATHERED is one of the factors that determine whether the trainee (USER_REC_ID) is compliant with the requirement imposed by this mandatory assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of the course version (CO_REC_ID) to the trainee. See COMPLIANT.

A trainee is grandfathered for this mandatory course assignment if at least one of the following is true:

  • the trainee's DEPT_START_DATE (per the LMS_PERSON table) falls before the EFFECTIVE_DATE
    • The trainee's DEPT_START_DATE is stored in LMS_PERSON.DEPT_START_DATE where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.
  • the trainee's TRANSFER_TYPE is grandfathered according to the GRANDFATHERING_VALUE for the course version named in the mandatory course assignment
    • the trainee's TRANSFER_TYPE is stored in KNODE_USER_JOIN.TRANSFER_TYPE where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = KNODE_USER_JOIN.USER_REC_ID.

If the trainee has only one mandatory assignment for the course (CO_MAS_ID), the trainee's grandfathered status for that assignment is the trainee's grandfathered status for the course.

If the trainee has more than one mandatory assignment for the course, the trainee is grandfathered for the course only if the trainee is grandfathered for all of the assignments. Otherwise, the trainee is not grandfathered for the course.

If the trainee is not grandfathered for the course, the trainee's grandfathered status for the course is available in the LMS_TRAINEE_COURSE_COMPLIANCE table, which also stores information used by Knowledge Link when sending E-mail Notifications to the trainee about the mandatory course.

The trainee's grandfathered status for the course is one of the factors that determine whether the course is currently required for the trainee. Because of this, it is also one of the factors that determine whether Knowledge Link sends E-mail Notifications about a course to a trainee. For more information, see the data element documentation for COURSE_OBJECT.SD_BOUNDARY.

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on mandatory course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

Values:
Y (the trainee is grandfathered for
   this mandatory course assignment)
N (the trainee is not grandfathered for
   this mandatory course assignment)
KCJ_REC_ID

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

A number used within the Knowledge Link system as the unique identifier for the record for the mandatory course assignment that specifies that this course version (CO_REC_ID) is actively assigned to a business unit that includes the trainee (USER_REC_ID). The KCJ_REC_ID value corresponds to a KNODE_CRS_JOIN.KCJ_REC_ID.

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on mandatory course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

Example: 12437

Values:
Refer to the KNODE_CRS_JOIN table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
LAST_EXTRACT_DATE

Indexed - no
Format - date
May be null? yes

The date and time when this record was extracted from Knowledge Link 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: 8/29/2009 3:09:00 AM

Values:
List of values not available.
LAST_NAME

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

The surname of the trainee (USER_REC_ID), stored in upper case to facilitate record selection conditions and sorting. See also FIRST_NAME and MIDDLE_INITIAL.

The LAST_NAME is taken from LMS_PERSON.LAST_NAME where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: ADAMS

Values:
List of values not available
MANDATORY

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

A Yes/No flag indicating whether or not the course version (CO_REC_ID) is assigned to the trainee (USER_REC_ID) as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID).

For all LMS_TRAINEE_BU_COURSE_ASSIGN records, MANDATORY is 'Y'.

MANDATORY is one of the factors that determine whether the course is currently required for the trainee. See CURRENTLY_REQUIRED.

Values:
Y (per this assignment, the course version is currently 
   assigned to the trainee as a mandatory course)
N (per this assignment, the course version is currently 
   assigned to the trainee as an optional course)
MIDDLE_INITIAL

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

The first letter of the middle name of the trainee (USER_REC_ID), stored in upper case. The value is null for some trainees. See also FIRST_NAME and LAST_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 is taken from LMS_PERSON.MIDDLE_INITIAL where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: S

Values:
List of values not available
PENN_ID

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

An 8-digit identification number assigned by the Penn Community system to the trainee. Per this LMS_TRAINEE_BU_COURSE_ASSIGN record (TRAINEE_BU_CRS_ASSIGNMENT_ID), the course version (CO_REC_ID) has been assigned to the trainee as a mandatory course. No two persons have the same Penn ID.

See also USER_REC_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

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.

The PENN_ID is taken from LMS_PERSON.PENN_ID where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID. Further information about the trainee is available in the LMS_PERSON table.

Example: 12345678

Values:
Refer to the LMS_PERSON table for values.
Note:  some of the trainees in that table have
no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
PERIODICITY

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

An integer (with no decimal places) indicating the number of months in the period from the time when a trainee completes the course to the time when the trainee is due to complete it again, per this mandatory course assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). When PERIODICITY is null or 0, the trainee is required to complete the course only once. When CURRENTLY_REQUIRED is 'N', PERIODICITY is irrelevant, even if its value is not null. See also DUE_DATE.

If the trainee has only one currently required course assignment for the course (CO_MAS_ID), the trainee's PERIODICITY for that assignment is the same as the trainee's PERIODICITY for the course.

If the trainee has multiple currently required assignments for the course, the assignment with the lowest non-null value of DUE_DATE is the one with the trainee's PERIODICITY for the course. (When the trainee has completed the course at least once, the assignment the lowest non-null value of DUE_DATE is also the assignment with the lowest non-null, non-zero value for PERIODICITY.) For the trainee's PERIODICITY for the course, see LMS_TRAINEE_COURSE_ASSIGN.PERIODICITY or LMS_TRAINEE_COURSE_COMPLIANCE.CURRENT_PERIODICITY.

Examples: 0, 12

Values:
List of values not available
PKG_ID

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

If the course version (CO_REC_ID) was assigned to the trainee (USER_REC_ID) as part of a package, PKG_ID stores the number used within the Knowledge Link system as the unique identifier for the package. A package is a set of courses that may be taken in any order, and that can be assigned to a business unit using one assignment specification. The PKG_ID value corresponds to a PKG.PKG_ID.

PKG_ID is 0 when the course version was not assigned to the trainee as part of a package.

Examples: 10704

Values:

Not Available
STATUS_DUEDATE_DESCRIPTION

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

A phrase describing when the trainee (USER_REC_ID) is next due to complete an iteration of the course (CO_MAS_ID), which is currently required for the trainee (USER_REC_ID) per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of a version of the course (CO_REC_ID) to the trainee. If the DUE_DATE is null, STATUS_DUEDATE_DESCRIPTION is 'Neither Soon Due nor Past Due'. See also PERIODICITY.

STATUS_DUEDATE_DESCRIPTION is one of the factors that determine whether the trainee (USER_REC_ID) is compliant with the requirement imposed by this mandatory assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID) of the course version (CO_REC_ID) to the trainee. See COMPLIANT.

If the trainee has only one currently required course assignment for the course (CO_MAS_ID), the trainee's STATUS_DUEDATE_DESCRIPTION for that assignment is the same as the trainee's STATUS_DUEDATE_DESCRIPTION for the course.

If the trainee has multiple currently required assignments for the course, the assignment with the lowest non-null value of DUE_DATE is the one with the trainee's STATUS_DUEDATE_DESCRIPTION for the course. For the trainee's STATUS_DUEDATE_DESCRIPTION for the course, see the LMS_TRAINEE_COURSE_COMPLIANCE table, the LMS_TRAINEE_COURSE_ASSIGN table, or the LMS_TRAINEE_COURSE_COMPLIANCE table.

The trainee's STATUS_DUEDATE_DESCRIPTION for the course is one of the factors that determine whether Knowledge Link sends E-mail Notifications about a course to a trainee. For more information, see the data element documentation for COURSE_OBJECT.SD_BOUNDARY.

Values:

Neither Soon Due nor Past Due
Past Due
Soon Due
TRAINEE_ASSIGNMENT_BU_ID

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

A string that uniquely identifies the trainee's Knowledge Position (KP) that falls under the business unit (COURSE_ASSIGNMENT_BU_ID) that has the course version (CO_REC_ID) assigned to it as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). See also TRAINEE_ASSIGNMENT_BU_NAME, TRAINEE_ASSIGNMENT_BU_NUMBER, COURSE_ASSIGNMENT_BU_NAME, and COURSE_ASSIGNMENT_BU_NUMBER

A trainee registers for a course iteration, which is an offering of a particular version of a course. A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee. A course can be assigned to a KP either directly (when the assignment cites the KP) or indirectly (when the assignment 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.

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 the documentation for LMS_PERSON.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

The TRAINEE_ASSIGNMENT_BU_ID is the KNODE.IDENTIFIER where LMS_TRAINEE_BU_COURSE_ASSIGN.TRAINEE_ASSIGNMENT_BU_NUMBER = KNODE.KNODE_ID. Most TRAINEE_ASSIGNMENT_BU_ID values are determined in the manner described below.

University KPs

  • 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 KPs

  • 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).
  • individual nurse: HS.RN.entity.Penn ID
    • example: HS.RN.HUP.34567890
    • UPHS has created a business unit for each of its nurses, but not for each of its other employees.
    • 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.
Auxiliary KPs
  • UP.Penn ID.AUX
    • example: UP.34567890.AUX
Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
TRAINEE_ASSIGNMENT_BU_NAME

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

A phrase or string that describes the trainee's Knowledge Position (KP) that falls under the business unit (COURSE_ASSIGNMENT_BU_ID) that has the course version (CO_REC_ID) assigned to it as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). It is possible for more than one KP to have the same name. See also TRAINEE_ASSIGNMENT_BU_ID, TRAINEE_ASSIGNMENT_BU_NUMBER, COURSE_ASSIGNMENT_BU_NAME, and COURSE_ASSIGNMENT_BU_NUMBER.

A trainee registers for a course iteration, which is an offering of a particular version of a course. A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee. A course can be assigned to a KP either directly (when the assignment cites the KP) or indirectly (when the assignment 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.

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 the documentation for LMS_PERSON.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

The TRAINEE_ASSIGNMENT_BU_NAME is the KNODE.NAME where LMS_TRAINEE_BU_COURSE_ASSIGN.TRAINEE_ASSIGNMENT_BU_NUMBER = KNODE.KNODE_ID. Most TRAINEE_ASSIGNMENT_BU_NAME values are determined in the manner described below.

University KPs

  • 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 KPs

  • 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).
  • individual nurse: Nurse: Lastname, Firstname (department name)
    • example: Nurse: Nightingale, Florence (Nursing Rehab)
    • UPHS has created a business unit for each of its nurses, but not for each of its other employees.
    • 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.

Auxiliary KPs

  • UP.PennKey.affiliation description
    • example: UP.mcurie.Wistar Faculty
    • For the list of auxiliary affiliations, see the documentation for LMS_PERSON.PENN_COMMUNITY_MEMBER_STATUS.
    • For affiliation descriptions, see the documentation on Penn Community Affiliations.
Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
TRAINEE_ASSIGNMENT_BU_NUMBER

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

A number used to uniquely identify the trainee's Knowledge Position (KP) that falls under the business unit (COURSE_ASSIGNMENT_BU_ID) that has the course version (CO_REC_ID) assigned to it as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID). The TRAINEE_ASSIGNMENT_BU_NUMBER value corresponds to a KNODE.KNODE_ID. See also TRAINEE_ASSIGNMENT_BU_ID, TRAINEE_ASSIGNMENT_BU_NAME, COURSE_ASSIGNMENT_BU_NAME, and COURSE_ASSIGNMENT_BU_NUMBER.

A trainee registers for a course iteration, which is an offering of a particular version of a course. A trainee cannot register for an iteration of a course version if that course version does not have an active assignment to a business unit that includes the trainee. A course can be assigned to a KP either directly (when the assignment cites the KP) or indirectly (when the assignment 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.

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 the documentation for LMS_PERSON.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

Example: 21073

Values:
Refer to the KNODE table for values.
Note:  some of the business units in that table
have no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
TRAINEE_BU_CRS_ASSIGNMENT_ID

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

A number used within the Knowledge Link system as the unique identifier for the LMS_TRAINEE_BU_COURSE_ASSIGN record, which stores information on the mandatory assignment of the course version (CO_REC_ID) to the trainee (USER_REC_ID) via a business unit that includes the trainee (COURSE_ASSIGNMENT_BU_NUMBER). A course is assigned to a trainee if a course assignment specifies that a version of the course (CO_REC_ID) has been assigned to a business unit that includes the trainee.

The TRAINEE_ASSIGNMENT_BU_NUMBER value corresponds to a USER_COURSES.USER_CRS_ID and to an LMS_COMPLIANCE.USER_CRS_ID.

The primary source of information on which courses are currently required for trainees is the KNODE_CRS_JOIN table, which stores information on mandatory and optional courses currently
assigned to business units that may represent individual trainees or groups of trainees. The USER_COURSES and LMS_TRAINEE_BU_COURSE_ASSIGN tables store information on mandatory courses currently assigned to individual trainees. If a trainee belongs to multiple business units that have the same mandatory course assigned to them, these tables store more than one record for the trainee and course. The LMS_TRAINEE_COURSE_ASSIGN table stores one record per trainee and currently required course. Historical information on mandatory course assignments is not available. If a trainee was once required to take a particular course, but is not currently required to take it, there is no way to tell that the course was ever required for the trainee.

Example: 853153171

Values:
List of values not available
USER_REC_ID

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

The number used within the Knowledge Link system as the unique identifier for the trainee to whom the course version (CO_REC_ID) has been assigned as a mandatory course per this assignment (TRAINEE_BU_CRS_ASSIGNMENT_ID).

See also PENN_ID, FIRST_NAME, MIDDLE_INITIAL, and LAST_NAME.

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_TRAINEE_BU_COURSE_ASSIGN table to be joined to those tables.

Further information about the trainee is available in the LMS_PERSON table where LMS_TRAINEE_BU_COURSE_ASSIGN.USER_REC_ID = LMS_PERSON.USER_REC_ID.

Example: 10159

Values:
Refer to the LMS_PERSON table or the 
  GEN21_USER table for values.
Note:  some of the trainees in those tables have 
no associated LMS_TRAINEE_BU_COURSE_ASSIGN records.
XACCESS

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

A numeric code that indicates the course version's access level, which is one of the criteria that were used to determine that the course version (CO_REC_ID) could be assigned to the business unit (COURSE_ASSIGNMENT_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. The business units to which Knowledge Link users are assigned are known as KPs, or Knowledge Positions. (See the KNODE_USER_JOIN table.) Some KPs denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system.

Business units are organized into a hierarchy. In the business unit hierarchy, the parent of a KP can be a Knowledge Community (KC) or a Knowledge Microcommunity (KMC). KCs and KMCs are the types of business units that are course version owners. The KCs that own course versions correspond to University orgs. or to University of Pennsylvania Health System (UPHS) entities (process levels) or departments (cost centers or accounting units). A KMC identifies a group of trainees from unrelated UPHS departments.

The course version’s XACCESS, the course version’s owner (COURSE_OBJECT.KNODE_ID), and the user’s privileges are among the criteria that determine whether the course version is included in the list of course versions that the user can assign. Course versions can be assigned by Knowledge Link users with administrator, junior administrator, or instructor privileges. Note:

  • If the user has administrator privileges, the user can assign any course version to any business unit, regardless of the course version’s owner and XACCESS.
  • If the user is assigned to a KP for a group whose privileges include the ability to assign course versions, and that KP’s parent is a KMC, the course version’s XACCESS is irrelevant. The list of course versions that the user can assign will include a given course version only if that KMC is the course version’s owner.

There are three kinds of XACCESS:

  • Global—the course version is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, and (2) the parent of that KP is a KC (not a KMC). The course version’s owner is irrelevant if XACCESS is 165 (Global).
  • Inheritable—the course version is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, (2) the parent of that KP is a KC (not a KMC), and (3) that KC is the same as the course version’s owner, or falls above the course version’s owner in the business unit hierarchy. 166 (Inheritable) is the default value for XACCESS.
  • Local—the course version is included on the list of those that the user can assign if: (1) the user is assigned to a KP denoting a group whose privileges include the ability to assign course versions, (2) the parent of that KP is a KC (not a KMC), and (3) that KC is the same as the course version’s owner.

The description for XACCESS is LMS_DEFINITION.NAME where LMS_TRAINEE_BU_COURSE_ASSIGN.XACCESS = LMS_DEFINITION.DEF_ID.

Values:
165 (Global)
166 (Inheritable)
167 (Local)

 

LMS_TRAINEE_BU_COURSE_ASSIGN 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