Penn Computing

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

LMS_BUSINESS_UNIT_TYPE - Data Element Index

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

 

Data element Definition
BUSINESS_UNIT_TYPE_ABBR

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

An abbreviation (in upper case) of the BUSINESS_UNIT_TYPE_DESC (the description of the business unit type). The business unit type is one of the factors that determines whether and how Knowledge Link users and courses can be assigned to the business unit. See also BUSINESS_UNIT_TYPE_CODE.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (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). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system. For more information on business units, see the documentation for the KNODE table.

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.

For information on the business unit hierarchy, see the documentation for PARENT_ID in the KNODE table.

Values:
KC  (Knowledge Community)
KMC (Knowledge Microcommunity)
KP  (Knowledge Position)
BUSINESS_UNIT_TYPE_CODE

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

A number that uniquely identifies the business unit type. The business unit type is one of the factors that determines whether and how Knowledge Link users and courses can be assigned to the business unit. See also BUSINESS_UNIT_TYPE_ABBR and BUSINESS_UNIT_TYPE_DESC.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (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). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system. For more information on business units, see the documentation for the KNODE table.

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.

For information on the business unit hierarchy, see the documentation for PARENT_ID in the KNODE table.

Values:
158 (Knowledge Community)
159 (Knowledge Microcommunity)
160 (Knowledge Position)
BUSINESS_UNIT_TYPE_DESC

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

The description of the business unit type (in mixed case).The business unit type is one of the factors that determines whether and how Knowledge Link users and courses can be assigned to the business unit. See also BUSINESS_UNIT_TYPE_ABBR and BUSINESS_UNIT_TYPE_CODE.

A business unit (also known as a BU, role, Knowledge Node, or K Node) is a set of one or more Knowledge Link users. Most business units correspond to bureaucratic groups that reflect various administrative subdivisions used for University of Pennsylvania Health System (UPHS) employees, University employees, University students, and auxiliary members of the Penn Community (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). Some business units denote privileged groups, used to classify certain Knowledge Link users according to what they are authorized to do within the Knowledge Link system. For more information on business units, see the documentation for the KNODE table.

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.

For information on the business unit hierarchy, see the documentation for PARENT_ID in the KNODE table.

Values:
Knowledge Community
Knowledge Microcommunity
Knowledge Position
LAST_EXTRACT_DATE

Indexed - no
Format - date
May be null? yes

The date this record was extracted from Knowledge Link and loaded into the Data Warehouse.

Example: 3/31/2008

Values:
List of values not available.

 

LMS_BUSINESS_UNIT_TYPE 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