Reference table for codes indicating the business unit type, which
determines whether and how Knowledge Link users and courses can be assigned
to the business unit. (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 LMS_BUSINESS_UNIT_TYPE
the 3-digit BUSINESS_UNIT_TYPE_CODE and its full and abbreviated descriptions
(BUSINESS_UNIT_TYPE_DESC and BUSINESS_UNIT_TYPE_ABBR, respectively). For
example, the description corresponding to BUSINESS_UNIT_TYPE_CODE
158 is "Knowledge Community."
Displaying the full or abbreviated description of the business unit type, rather
appears in a related table. ("Don't show the codes in the report. Show
the English instead.")
||Indexed Data Elements
- There are three types of business units:
- Knowledge Position (KP)
- A Knowledge Link user can be assigned to it directly. That is,
the KNODE_USER_JOIN record cites the KP.
- A course can be assigned to it either directly (where the KNODE_CRS_JOIN
record cites the KP) or indirectly (where the KNODE_CRS_JOIN record
cites a Knowledge Community or Knowledge Microcommunity that is
above the KP in the business unit hierarchy).
- Knowledge Community (KC)--a group of KPs, corresponding to a University
org., academic division, or major; to a University of Pennsylvania Health
System (UPHS) entity (process level) or department (cost center or accounting
unit); or to an auxiliary Penn Community affiliation. (Auxiliary members
of the Penn Community are members 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 Link user cannot be assigned to a KC directly. A
KC includes a user if the user has a KNODE_USER_JOIN record that
cites a KP that is below the KC in the business unit hierarchy.
- A course may be assigned to a KC either directly (where the KNODE_CRS_JOIN
record cites the KC indirectly (where the KNODE_CRS_JOIN record
cites a BU that is above the KC in the business unit hierarchy).
- Knowledge Microcommunity (KMC)--a group of KPs that was created to
allow courses to be assigned to Knowledge Link users from unrelated UPHS
departments (also known as cost centers or accounting units)
- A Knowledge Link user cannot be assigned to a KMC directly. A
KMC includes a user if the user has a KNODE_USER_JOIN record that
cites a KP that is below the KMC in the business unit hierarchy.
- A course may be assigned to a KMC directly (where the KNODE_CRS_JOIN
record cites the KMC). A course may not be assigned to a KMC indirectly.
That is, if the KNODE_CRS_JOIN record cites a BU that is above
the KMC in the business unit hierarchy, the KMC does not have
the course assigned to it.
- Although the LMS_BUSINESS_UNIT_TYPE
table may be joined to any of the
related tables listed above, it is recommended that it be joined only to
KNODE (to decode TYPE). There is no need to join LMS_BUSINESS_UNIT_TYPE to
LMS_BUSINESS_UNIT_GROUP, because LMS_BUSINESS_UNIT_GROUP stores the full
and abbreviated descriptions of the business unit type (as well as the
business unit type code). LMS_DEFINITION is the source of the data in the
Knowledge Link, the learning management system used by the University and
by the University of Pennsylvania Health System (UPHS) since March, 2005.
Knowledge Link enables authorized administrators to schedule training
courses, assign resources to courses, assign groups of trainees to courses,
and to create online courses. It enables trainees to find out what courses
have been assigned to them, to register for those courses (whether those courses
are on-line or instructor-led), to take on-line courses, and to provide feedback
via course evaluations. Knowledge Link was first used to track information
on training required by regulation, but it now tracks information on a variety
Questions about this page? Email us at firstname.lastname@example.org