Penn Computing

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

LMS_BUSINESS_UNIT_GROUP - Data Element Index

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

 

Data element Definition
BU_GROUP_UPHS_ADMIN_AS_IS

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

The name of the University of Pennsylvania Health System (UPHS) administrator for the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The UPHS administrator oversees the UPHS manager (BU_GROUP_UPHS_MANAGER), and is authorized to use Knowledge Link to run the Entity Administrator Report. (The report provides information on the compliancy of courses for UPHS departments, and the users within those departments.) See also BU_GROUP_UPHS_ADMINISTRATOR and BU_GROUP_UPHS_ADMIN_PENNID. Further information on the administrator is available in the LMS_PERSON table.

BU_GROUP_UPHS_ADMIN_AS_IS is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: Piesieski, Patricia

Values:
List of values not available
Source: KNODE.CUSTOM_V4 for the business unit group
BU_GROUP_UPHS_ADMIN_PENNID

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

The Penn ID of the University of Pennsylvania Health System (UPHS) administrator for the business unit group (BUSINESS_UNIT_GROUP_ID). A Penn ID is an 8-digit identification number assigned to an individual by the Penn Community system. No two persons have the same Penn 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. 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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The UPHS administrator oversees the UPHS manager (BU_GROUP_UPHS_MANAGER), and is authorized to use Knowledge Link to run the Entity Administrator Report. (The report provides information on the compliancy of courses for UPHS departments, and the users within those departments.) See also BU_GROUP_UPHS_ADMINISTRATOR and BU_GROUP_UPHS_ADMIN_AS_IS. Further information on the administrator is available in the LMS_PERSON table.

BU_GROUP_UPHS_ADMIN_PENNID is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: 10226126

Values:
List of values not available
Source: KNODE.CUSTOM_N2 for the business unit group
BU_GROUP_UPHS_ADMINISTRATOR

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

The name of the University of Pennsylvania Health System (UPHS) administrator for the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in upper case. It may be preferable to select and sort records based on the name in upper case rather than in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The UPHS administrator oversees the UPHS manager (BU_GROUP_UPHS_MANAGER), and is authorized to use Knowledge Link to run the Entity Administrator Report. (The report provides information on the compliancy of courses for UPHS departments, and the users within those departments.) See also BU_GROUP_UPHS_ADMIN_AS_IS and BU_GROUP_UPHS_ADMIN_PENNID. Further information on the administrator is available in the LMS_PERSON table.

BU_GROUP_UPHS_ADMINISTRATOR is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: PIESIESKI, PATRICIA

Values:
List of values not available
Source: KNODE.CUSTOM_V4 for the business unit group, in upper case
BU_GROUP_UPHS_COST_CENTER

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

Text used in Knowledge Link's Entity Administrator Report for the business unit group (BUSINESS_UNIT_GROUP_ID). The value of BU_GROUP_UPHS_COST_CENTER (if it is not null) is 'Cost Center' (without the quotes).

The Entity Administrator Report provides information on the compliancy of courses for UPHS departments, and the users within those departments.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

BU_GROUP_UPHS_COST_CENTER is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Value:
Cost Center
Source: KNODE.CUSTOM_V1 for the business unit group
BU_GROUP_UPHS_DEPT_NAME

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

The name of the University of Pennsylvania Health System (UPHS) department for the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in upper case. It may be preferable to select and sort records based on the name in upper case rather than in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Also known as a cost center or accounting unit, a UPHS department is a subdivision of a UPHS entity or process level. See also BU_GROUP_UPHS_DEPT_NAME_AS_IS and BU_GROUP_UPHS_MANAGER.

BU_GROUP_UPHS_DEPT_NAME is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: NURSING SILVERSTEIN 7

Values:
List of values not available
Source: KNODE.CUSTOM_V5 for the business unit group, in upper case
BU_GROUP_UPHS_DEPT_NAME_AS_IS

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

The name of the University of Pennsylvania Health System (UPHS) department for the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Also known as a cost center or accounting unit, a UPHS department is a subdivision of a UPHS entity or process level. See also BU_GROUP_UPHS_DEPT_NAME and BU_GROUP_UPHS_MANAGER.

BU_GROUP_UPHS_DEPT_NAME_AS_IS is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: Nursing Silverstein 7

Values:
List of values not available
Source: KNODE.CUSTOM_V5 for the business unit group
BU_GROUP_UPHS_ENTITY

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

The name of the University of Pennsylvania Health System (UPHS) entity that includes the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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).

BU_GROUP_UPHS_ENTITY is used for UPHS business unit groups, but its value is null for University business unit groups.

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)
Source: KNODE.CUSTOM_V2 for the business unit group
BU_GROUP_UPHS_MANAGER

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

The name of the University of Pennsylvania Health System (UPHS) manager of the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in upper case. It may be preferable to select and sort records based on the name in upper case rather than in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The manager is the person responsible for the UPHS department. (Also known as a cost center or accounting unit, a department is a subdivision of a UPHS entity or process level.) The manager is authorized to use Knowledge Link to run the Entity Administrator Report, which provides information on the compliancy of courses for UPHS departments, and the users within those departments. See also BU_GROUP_UPHS_MANAGER_AS_IS, BU_GROUP_UPHS_MANAGER_PENNID, and BU_GROUP_UPHS_ADMINISTRATOR. Further information on the manager is available in the LMS_PERSON table.

BU_GROUP_UPHS_MANAGER is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: RICH, VICTORIA

Values:
List of values not available
Source: KNODE.CUSTOM_V3 for the business unit group, in upper case
BU_GROUP_UPHS_MANAGER_AS_IS

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

The name of the University of Pennsylvania Health System (UPHS) manager of the business unit group (BUSINESS_UNIT_GROUP_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The manager is the person responsible for the UPHS department. (Also known as a cost center or accounting unit, a department is a subdivision of a UPHS entity or process level.) The manager is authorized to use Knowledge Link to run the Entity Administrator Report, which provides information on the compliancy of courses for UPHS departments, and the users within those departments. See also BU_GROUP_UPHS_MANAGER, BU_GROUP_UPHS_MANAGER_PENNID, and BU_GROUP_UPHS_ADMINISTRATOR. Further information on the manager is available in the LMS_PERSON table.

BU_GROUP_UPHS_MANAGER_AS_IS is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: Rich, Victoria

Values:
List of values not available
Source: KNODE.CUSTOM_V3 for the business unit group
BU_GROUP_UPHS_MANAGER_PENN_ID

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

The Penn ID of the University of Pennsylvania Health System (UPHS) manager of the business unit group (BUSINESS_UNIT_GROUP_ID). A Penn ID is an 8-digit identification number assigned to an individual by the Penn Community system. No two persons have the same Penn 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. 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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The manager is the person responsible for the UPHS department. (Also known as a cost center or accounting unit, a department is a subdivision of a UPHS entity or process level.) The manager is authorized to use Knowledge Link to run the Entity Administrator Report, which provides information on the compliancy of courses for UPHS departments, and the users within those departments. See also BU_GROUP_UPHS_MANAGER, BU_GROUP_UPHS_MANAGER_AS_IS, and BU_GROUP_UPHS_ADMINISTRATOR. Further information on the manager is available in the LMS_PERSON table.

BU_GROUP_UPHS_MANAGER_PENN_ID is used for business unit groups that correspond to UPHS departments. Its value is null for other UPHS business unit groups, and for all University business unit groups.

Example: 10107547

Values:
List of values not available
Source: KNODE.CUSTOM_N1 for the business unit group
BU_GROUP_UPHS_TRANSACTION_ID

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

If the data for the KNODE record for the business unit group (BUSINESS_UNIT_GROUP_ID) was entered into the Knowledge Link system via a record in an XML feed from the University of Pennsylvania Health System (UPHS), BU_GROUP_UPHS_TRANSACTION_ID identifies that record in the XML feed.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

BU_GROUP_UPHS_TRANSACTION_ID can be used for UPHS business unit groups, but its value is null for University business unit groups.

Example: 3149937

Values:
List of values not available
Source: KNODE.CUSTOM_N5 for the business unit group
BU_MEMBER_UPHS_ADMIN_AS_IS

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

The name of the University of Pennsylvania Health System (UPHS) administrator for the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The UPHS administrator oversees the UPHS manager (BU_MEMBER_UPHS_MANAGER), and is authorized to use Knowledge Link to run the Entity Administrator Report. (The report provides information on the compliancy of courses for UPHS departments, and the users within those departments.) See also BU_MEMBER_UPHS_ADMINISTRATOR and BU_MEMBER_UPHS_ADMIN_PENNID. Further information on the administrator is available in the LMS_PERSON table.

BU_MEMBER_UPHS_ADMIN_AS_IS is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: Piesieski, Patricia

Values:
List of values not available
Source: KNODE.CUSTOM_V4 for the business unit member
BU_MEMBER_UPHS_ADMIN_PENNID

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

The Penn ID of the University of Pennsylvania Health System (UPHS) administrator for the business unit member (BUSINESS_UNIT_MEMBER_ID). A Penn ID is an 8-digit identification number assigned to an individual by the Penn Community system. No two persons have the same Penn 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. 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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The UPHS administrator oversees the UPHS manager (BU_MEMBER_UPHS_MANAGER), and is authorized to use Knowledge Link to run the Entity Administrator Report. (The report provides information on the compliancy of courses for UPHS departments, and the users within those departments.) See also BU_MEMBER_UPHS_ADMINISTRATOR and BU_MEMBER_UPHS_ADMIN_AS_IS. Further information on the administrator is available in the LMS_PERSON table.

BU_MEMBER_UPHS_ADMIN_PENNID is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: 10226126

Values:
List of values not available
Source: KNODE.CUSTOM_N2 for the business unit member
BU_MEMBER_UPHS_ADMINISTRATOR

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

The name of the University of Pennsylvania Health System (UPHS) administrator for the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in upper case. It may be preferable to select and sort records based on the name in upper case rather than in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The UPHS administrator oversees the UPHS manager (BU_MEMBER_UPHS_MANAGER), and is authorized to use Knowledge Link to run the Entity Administrator Report. (The report provides information on the compliancy of courses for UPHS departments, and the users within those departments.) See also BU_MEMBER_UPHS_ADMIN_AS_IS and BU_MEMBER_UPHS_ADMIN_PENNID. Further information on the administrator is available in the LMS_PERSON table.

BU_MEMBER_UPHS_ADMIN_AS_IS is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: PIESIESKI, PATRICIA

Values:
List of values not available
Source: KNODE.CUSTOM_V4 for the business unit member, in upper case
BU_MEMBER_UPHS_COST_CENTER

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

Text used in Knowledge Link's Entity Administrator Report for the business unit member (BUSINESS_UNIT_MEMBER_ID). The value of BU_MEMBER_UPHS_COST_CENTER (if it is not null) is 'Cost Center' (without the quotes).

The Entity Administrator Report provides information on the compliancy of courses for UPHS departments, and the users within those departments.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

BU_MEMBER_UPHS_COST_CENTER is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Value:
Cost Center
Source: KNODE.CUSTOM_V1 for the business unit member
BU_MEMBER_UPHS_DEPT_NAME

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

The name of the University of Pennsylvania Health System (UPHS) department for the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in upper case. It may be preferable to select and sort records based on the name in upper case rather than in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Also known as a cost center or accounting unit, a UPHS department is a subdivision of a UPHS entity or process level. See also BU_MEMBER_UPHS_DEPT_NAME_AS_IS and BU_MEMBER_UPHS_MANAGER.

BU_MEMBER_UPHS_DEPT_NAME is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: NURSING SILVERSTEIN 7

Values:
List of values not available
Source: KNODE.CUSTOM_V5 for the business unit member, in upper case
BU_MEMBER_UPHS_DEPT_NAME_AS_IS

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

The name of the University of Pennsylvania Health System (UPHS) department for the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Also known as a cost center or accounting unit, a UPHS department is a subdivision of a UPHS entity or process level. See also BU_MEMBER_UPHS_DEPT_NAME and BU_MEMBER_UPHS_MANAGER.

BU_MEMBER_UPHS_DEPT_NAME_AS_IS is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: Nursing Silverstein 7

Values:
List of values not available
Source: KNODE.CUSTOM_V5 for the business unit member
BU_MEMBER_UPHS_ENTITY

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

The name of the University of Pennsylvania Health System (UPHS) entity that includes the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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).

BU_MEMBER_UPHS_ENTITY is used for UPHS business unit members, but its value is null for University business unit members.

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)
Source: KNODE.CUSTOM_V2 for the business unit member
BU_MEMBER_UPHS_MANAGER

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

The name of the University of Pennsylvania Health System (UPHS) manager of the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in upper case. It may be preferable to select and sort records based on the name in upper case rather than in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The manager is the person responsible for the UPHS department. (Also known as a cost center or accounting unit, a department is a subdivision of a UPHS entity or process level.) The manager is authorized to use Knowledge Link to run the Entity Administrator Report, which provides information on the compliancy of courses for UPHS departments, and the users within those departments. See also BU_MEMBER_UPHS_MANAGER_AS_IS, BU_MEMBER_UPHS_MANAGER_PENNID, and BU_MEMBER_UPHS_ADMINISTRATOR. Further information on the manager is available in the LMS_PERSON table.

BU_MEMBER_UPHS_MANAGER is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: RICH, VICTORIA

Values:
List of values not available
Source: KNODE.CUSTOM_V3 for the business unit member, in upper case
BU_MEMBER_UPHS_MANAGER_AS_IS

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

The name of the University of Pennsylvania Health System (UPHS) manager of the business unit member (BUSINESS_UNIT_MEMBER_ID). The name is stored in mixed case.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The manager is the person responsible for the UPHS department. (Also known as a cost center or accounting unit, a department is a subdivision of a UPHS entity or process level.) The manager is authorized to use Knowledge Link to run the Entity Administrator Report, which provides information on the compliancy of courses for UPHS departments, and the users within those departments. See also BU_MEMBER_UPHS_MANAGER, BU_MEMBER_UPHS_MANAGER_PENNID, and BU_MEMBER_UPHS_ADMINISTRATOR. Further information on the manager is available in the LMS_PERSON table.

BU_MEMBER_UPHS_MANAGER_AS_IS is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: Rich, Victoria

Values:
List of values not available
Source: KNODE.CUSTOM_V3 for the business unit member
BU_MEMBER_UPHS_MANAGER_PENN_ID

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

The Penn ID of the University of Pennsylvania Health System (UPHS) manager of the business unit member (BUSINESS_UNIT_MEMBER_ID). A Penn ID is an 8-digit identification number assigned to an individual by the Penn Community system. No two persons have the same Penn 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. 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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

The manager is the person responsible for the UPHS department. (Also known as a cost center or accounting unit, a department is a subdivision of a UPHS entity or process level.) The manager is authorized to use Knowledge Link to run the Entity Administrator Report, which provides information on the compliancy of courses for UPHS departments, and the users within those departments. See also BU_MEMBER_UPHS_MANAGER, BU_MEMBER_UPHS_MANAGER_AS_IS, and BU_MEMBER_UPHS_ADMINISTRATOR. Further information on the manager is available in the LMS_PERSON table.

BU_MEMBER_UPHS_MANAGER_PENN_ID is used for business unit members that correspond to UPHS departments. Its value is null for other UPHS business unit members, and for all University business unit members.

Example: 10107547

Values:
List of values not available
Source: KNODE.CUSTOM_N1 for the business unit member
BU_MEMBER_UPHS_TRANSACTION_ID

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

If the data for the KNODE record for the business unit member (BUSINESS_UNIT_MEMBER_ID) was entered into the Knowledge Link system via a record in an XML feed from the University of Pennsylvania Health System (UPHS), BU_MEMBER_UPHS_TRANSACTION_ID identifies that record in the XML feed.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

BU_MEMBER_UPHS_TRANSACTION_ID can be used for UPHS business unit members, but its value is null for University business unit members.

Example: 3149937

Values:
List of values not available
Source: KNODE.CUSTOM_N5 for the business unit member
BUSINESS_UNIT_GROUP_ID

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

A string that uniquely identifies the business unit group to Knowledge Link users. See also BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_NAME.

The BUSINESS_UNIT_GROUP_ID may include letters and/or numerals and/or other characters. The letters in BUSINESS_UNIT_GROUP_ID may be in upper case, lower case, or mixed case. The BUSINESS_UNIT_GROUP_ID for a University of Pennsylvania Health System (UPHS) business unit begins with HS; for a University or auxiliary business unit, it begins with UP. (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.) One of the qualifiers in a BUSINESS_UNIT_GROUP_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.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Most BUSINESS_UNIT_GROUP_ID values are determined in the manner described below. Generally speaking, the further down the business unit is in the hierarchy, the more qualifiers its BUSINESS_UNIT_GROUP_ID has.

University business units

  • org.: UP.org. code
    • example: UP.9937
    • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.
    • A University employee with a FAC or STAF affiliation in the Penn Community is included in the business unit for his or her home org., which is the org. responsible for maintaining his or her record in the Payroll system.
  • individual University employee with a FAC or STAF affiliation in the Penn Community: UP.Penn ID
    • example: UP.12345678
    • For information on University employees, see the Salary Management data collection's documentation on EMPLOYEE_GENERAL.
  • academic division and major: UP.division.major
    • examples: UP.NUG, UP.NUG.PERI
    • Note: if an org. exists for an academic division or major, there will be separate business units for the org. and for the academic division or major.
    • Knowledge Link users and courses are not assigned to the business units created for academic divisions and majors. These business units are used as the basis for creating the business units for students.
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly)
  • group of students: UP.STU-.academic division.major
    • examples: UP.STU-.NUG, UP.STU-.NUG.ACNP
    • A student is included in a business unit for a group of students based on his or her 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.
  • individual student: UP.Penn ID.STU
    • example: UP.23456789.STU
    • For information on students, see the Student data collection's documentation on the PERSON table (updated nightly).

UPHS business units

  • entity and department: HS.entity.department.jobclass.EEO code
    • examples: HS.CRDTL; HS.CRDTL.NeontChiefA.A.10
    • Entities are also known as process levels. Departments are also known as a cost centers or accounting units.
  • Knowledge Microcommunity: HS.microcommunity abbreviation
    • example: HS.PATREG
    • A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (See BUSINESS_UNIT_GROUP_TYPE_DESC.)
  • 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 business units

  • group of auxiliary Penn Community members: UP.AUX-.affiliation abbreviation
  • individual auxiliary Penn Community member: UP.Penn ID.AUX
    • example: UP.34567890.AUX
    • For information on auxiliary members, see the documentation on the Penn Community MEMBER table.
Values:
Refer to the KNODE table for values.
Source: the KNODE.IDENTIFIER for the business unit group
BUSINESS_UNIT_GROUP_NAME

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

A phrase or string that describes the business unit group. It is possible for more than one business unit group to have the same name. See also BUSINESS_UNIT_GROUP_ID and BUSINESS_UNIT_GROUP_NUMBER.

The BUSINESS_UNIT_GROUP_NAME may include letters and/or numerals and/or other characters. The letters in BUSINESS_UNIT_GROUP_NAME may be in upper case, lower case, or mixed case. One of the qualifiers in a BUSINESS_UNIT_GROUP_NAME may be the Penn Key, which is a unique name (attributable to a single individual) that serves as the Kerberos Principal and as a user name (logon ID) for the individual in various Penn systems (such as e-mail).

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Most BUSINESS_UNIT_GROUP_NAME values are determined in the manner described below.

University business units

  • org.: the name of the 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.
  • individual University employee with a FAC or STAF affiliation in the Penn Community: UP.Penn Key.name of home org.primary job appointment title, truncated at 50 characters
    • example: UP.franklin.DM-Sleep Medicine.RESEARCH INVESTIGATO
    • A University employee with a FAC or STAF affiliation in the Penn Community is included in the business unit for his or her home org., which is the org. responsible for maintaining his or her record in the Payroll system. Information on the primary job appointment and other information on University employees is available in the Salary Management data collection's documentation on EMPLOYEE_GENERAL.
  • academic division and major: UP.division.major
    • examples: UP.NUG, UP.NUG.PERI
    • Note: if an org. exists for an academic division or major, there will be separate business units for the org. and for the academic division or major.
    • Knowledge Link users and courses are not assigned to the business units created for academic divisions and majors. These business units are used as the basis for creating the business units for students.
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly).
  • group of students: UP.STU-.academic division.major
    • examples: UP.STU-.NUG, UP.STU-.NUG.ACNP
    • A student is placed in a group based on his or her 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.
  • individual student: UP.Penn Key.division.major
    • example: UP.janetdoe.NUG.ACNP
    • For information on students, see the Student data collection's documentation on the PERSON table (updated nightly).

UPHS business units

  • entity: HS.entity
    • example: HS.CRDTL
    • Entities are also known as process levels.
  • department: the department name
    • example: Administrator: Neonatology* (CRDTL)
    • Departments are also known as a cost centers or accounting units.
  • Knowledge Microcommunity: the microcommunity name
    • example: Patient Registration
    • A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (See BUSINESS_UNIT_GROUP_TYPE_DESC.)
  • 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 business units

  • group of auxiliary Penn Community members: UP.AUX-.affiliation description
  • individual auxiliary Penn Community member: UP.Penn Key.affiliation description
    • example: UP.mcurie.Wistar Faculty
    • For information on auxiliary members, see the documentation on the Penn Community MEMBER table.
Values:
List of values not available
Source: the KNODE.NAME for the business unit group
BUSINESS_UNIT_GROUP_NUMBER

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

A number used to uniquely identify the business unit group within the Knowledge Link system. See also BUSINESS_UNIT_GROUP_ID and BUSINESS_UNIT_GROUP_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. 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.

Business units are arranged in a hierarchy. The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member. (See also BUSINESS_UNIT_MEMBER_NUMBER.)

The business unit hierarchy is based on the hierarchies of the administrative groupings in the source systems, as described briefly below. (See also BUSINESS_UNIT_GROUP_TYPE_DESC.)

University business units

  • Business units for University orgs. follow the University's org. hierarchy. A business unit for a University employee with a FAC or STAF affiliation in the Penn Community has as its parent the business unit for the employee's home org. (The home org. is the organization that owns the employee's record and is responsible for its maintenance in the payroll system.)
    • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table; the documentation on its PARENT_ORG_CODE data element describes the org. hierarchy. For information on University employees, see the Salary Management data collection's documentation on EMPLOYEE_GENERAL.
  • The business unit for a University major has as its parent the business unit for the University academic division that offers the major.
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly).
  • The business unit hierarchy for University students parallels the hierarchy for the academic divisions and majors. A business unit for a University student has as its parent the UP.STU- business unit for the student's primary major in his or her primary academic division, per the SRS_DIVISION and SRS_MAJOR in the record for the student in the Penn Community AFFILIATION table.

UPHS business units

  • Most Health System business units use the same hierarchy as for the UPHS entities (also known as process levels) and departments (also known as a cost centers or accounting units).
  • The UPHS branch of the business unit hierarchy has a separate sub-branch for Knowledge Microcommunities. (See also TYPE.)
  • 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 business units

  • A business unit has been created for each auxiliary Penn Community affiliation. The business unit for a Knowledge Link user with an auxiliary affiliation has as its parent the UP.AUX- business unit for the user's auxiliary Penn Community affiliation (per the Penn Community AFFILIATION table).

Example: 44317

Values:
Refer to the KNODE table for values.
Source: the KNODE.KNODE_ID for the business unit group
BUSINESS_UNIT_GROUP_SOURCE

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

A code that indicates the ultimate source of the information on the business unit group (BUSINESS_UNIT_GROUP_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. 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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Values:
HS (the University of Pennsylvania Health System)
LMS (the Learning Management System (Knowledge Link)) UP (the University of Pennsylvania)
BUSINESS_UNIT_GROUP_STATUS

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

A letter that indicates whether the business unit group (BUSINESS_UNIT_GROUP_ID) is active or inactive. See also BUSINESS_UNIT_GROUP_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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

If BUSINESS_UNIT_GROUP_NUMBER = BUSINESS_UNIT_MEMBER_NUMBER, BUSINESS_UNIT_GROUP_STATUS also indicates whether the business unit member is active or inactive. An active group may have inactive members, and an inactive group may have active members.

A business unit must be active if a record is to be created to assign a Knowledge Link user or course to the business unit. (See the KNODE_USER_JOIN and KNODE_CRS_JOIN tables.) Also, a business unit must be active if a record is to be created or updated to name the business unit as the owner of a course version or package. (See the COURSE_OBJECT, LMS_COURSE_MASTER, and PKG tables.) Once a business unit has been named as the owner of a course version or package, it retains ownership even if it becomes inactive.

Values:
A (the business unit group is active)
I (the business unit group is inactive)
BUSINESS_UNIT_GROUP_TYPE_ABBR

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

An abbreviation (in upper case) of the BUSINESS_UNIT_GROUP_TYPE_DESC (the description of the business unit group's type). The type determines whether and how Knowledge Link users and courses can be assigned to the business unit group (BUSINESS_UNIT_GROUP_ID). See also BUSINESS_UNIT_GROUP_TYPE_CODE and BUSINESS_UNIT_GROUP_STATUS.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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) or 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.
Values:
KC  (Knowledge Community)
KMC (Knowledge Microcommunity)
KP  (Knowledge Position)
Source: LMS_BUSINESS_UNIT_TYPE.BUSINESS_UNIT_TYPE_ABBR
for the business unit group type code stored in LMS_BUSINESS_UNIT_GROUP.BUSINESS_UNIT_GROUP_TYPE_CODE
BUSINESS_UNIT_GROUP_TYPE_CODE

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

A number that uniquely identifies the business unit group's type. The type determines whether and how Knowledge Link users and courses can be assigned to the business unit group (BUSINESS_UNIT_GROUP_ID). See also BUSINESS_UNIT_GROUP_TYPE_DESC, BUSINESS_UNIT_GROUP_TYPE_ABBR, and BUSINESS_UNIT_GROUP_STATUS.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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) or 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.
Values:
158 (Knowledge Community)
159 (Knowledge Microcommunity)
160 (Knowledge Position)
Source: the KNODE.TYPE for the business unit group
BUSINESS_UNIT_GROUP_TYPE_DESC

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

The description of the business unit group's type (in mixed case). The type determines whether and how Knowledge Link users and courses can be assigned to the business unit group (BUSINESS_UNIT_GROUP_ID). See also BUSINESS_UNIT_GROUP_TYPE_ABBR, BUSINESS_UNIT_GROUP_TYPE_CODE, and BUSINESS_UNIT_GROUP_STATUS.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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) or 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.
Values:
Knowledge Community
Knowledge Microcommunity
Knowledge Position
Source: LMS_BUSINESS_UNIT_TYPE.BUSINESS_UNIT_TYPE_DESC
for the business unit group type code stored in LMS_BUSINESS_UNIT_GROUP.BUSINESS_UNIT_GROUP_TYPE_CODE
BUSINESS_UNIT_MEMBER_ID

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

A string that uniquely identifies the business unit member to Knowledge Link users. See also BUSINESS_UNIT_MEMBER_NUMBER and BUSINESS_UNIT_MEMBER_NAME.

The BUSINESS_UNIT_MEMBER_ID may include letters and/or numerals and/or other characters. The letters in BUSINESS_UNIT_MEMBER_ID may be in upper case, lower case, or mixed case. The BUSINESS_UNIT_MEMBER_ID for a University of Pennsylvania Health System (UPHS) business unit begins with HS; for a University or auxiliary business unit, it begins with UP. (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.) One of the qualifiers in a BUSINESS_UNIT_MEMBER_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.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Most BUSINESS_UNIT_MEMBER_ID values are determined in the manner described below. Generally speaking, the further down the business unit is in the hierarchy, the more qualifiers its BUSINESS_UNIT_MEMBER_ID has.

University business units

  • org.: UP.org. code
    • example: UP.9937
    • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table.
    • A University employee with a FAC or STAF affiliation in the Penn Community is included in the business unit for his or her home org., which is the org. responsible for maintaining his or her record in the Payroll system.
  • individual University employee with a FAC or STAF affiliation in the Penn Community: UP.Penn ID
    • example: UP.12345678
    • For information on University employees, see the Salary Management data collection's documentation on EMPLOYEE_GENERAL.
  • academic division and major: UP.division.major
    • examples: UP.NUG, UP.NUG.PERI
    • Note: if an org. exists for an academic division or major, there will be separate business units for the org. and for the academic division or major.
    • Knowledge Link users and courses are not assigned to the business units created for academic divisions and majors. These business units are used as the basis for creating the business units for students.
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly)
  • group of students: UP.STU-.academic division.major
    • examples: UP.STU-.NUG, UP.STU-.NUG.ACNP
    • A student is included in a business unit for a group of students based on his or her 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.
  • individual student: UP.Penn ID.STU
    • example: UP.23456789.STU
    • For information on students, see the Student data collection's documentation on the PERSON table (updated nightly).

UPHS business units

  • entity and department: HS.entity.department.jobclass.EEO code
    • examples: HS.CRDTL; HS.CRDTL.NeontChiefA.A.10
    • Entities are also known as process levels. Departments are also known as a cost centers or accounting units.
  • Knowledge Microcommunity: HS.microcommunity abbreviation
    • example: HS.PATREG
    • A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (See BUSINESS_UNIT_MEMBER_TYPE_DESC.)
  • 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 business units

  • group of auxiliary Penn Community members: UP.AUX-.affiliation abbreviation
  • individual auxiliary Penn Community member: UP.Penn ID.AUX
    • example: UP.34567890.AUX
    • For information on auxiliary members, see the documentation on the Penn Community MEMBER table.
Values:
Refer to the KNODE table for values.
Source: the KNODE.IDENTIFIER for the business unit member
BUSINESS_UNIT_MEMBER_NAME

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

A phrase or string that describes the business unit member. It is possible for more than one business unit member to have the same name. See also BUSINESS_UNIT_MEMBER_ID and BUSINESS_UNIT_MEMBER_NUMBER.

The BUSINESS_UNIT_MEMBER_NAME may include letters and/or numerals and/or other characters. The letters in BUSINESS_UNIT_MEMBER_NAME may be in upper case, lower case, or mixed case. One of the qualifiers in a BUSINESS_UNIT_MEMBER_NAME may be the Penn Key, which is a unique name (attributable to a single individual) that serves as the Kerberos Principal and as a user name (logon ID) for the individual in various Penn systems (such as e-mail).

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Most BUSINESS_UNIT_MEMBER_NAME values are determined in the manner described below.

University business units

  • org.: the name of the 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.
  • individual University employee with a FAC or STAF affiliation in the Penn Community: UP.Penn Key.name of home org.primary job appointment title, truncated at 50 characters
    • example: UP.franklin.DM-Sleep Medicine.RESEARCH INVESTIGATO
    • A University employee with a FAC or STAF affiliation in the Penn Community is included in the business unit for his or her home org., which is the org. responsible for maintaining his or her record in the Payroll system. Information on the primary job appointment and other information on University employees is available in the Salary Management data collection's documentation on EMPLOYEE_GENERAL.
  • academic division and major: UP.division.major
    • examples: UP.NUG, UP.NUG.PERI
    • Note: if an org. exists for an academic division or major, there will be separate business units for the org. and for the academic division or major.
    • Knowledge Link users and courses are not assigned to the business units created for academic divisions and majors. These business units are used as the basis for creating the business units for students.
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly).
  • group of students: UP.STU-.academic division.major
    • examples: UP.STU-.NUG, UP.STU-.NUG.ACNP
    • A student is placed in a group based on his or her 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.
  • individual student: UP.Penn Key.division.major
    • example: UP.janetdoe.NUG.ACNP
    • For information on students, see the Student data collection's documentation on the PERSON table (updated nightly).

UPHS business units

  • entity: HS.entity
    • example: HS.CRDTL
    • Entities are also known as process levels.
  • department: the department name
    • example: Administrator: Neonatology* (CRDTL)
    • Departments are also known as a cost centers or accounting units.
  • Knowledge Microcommunity: the microcommunity name
    • example: Patient Registration
    • A Knowledge Microcommunity is a business unit that was created to allow courses to be assigned to Knowledge Link users from unrelated UPHS departments. (See BUSINESS_UNIT_MEMBER_TYPE_DESC.)
  • 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 business units

  • group of auxiliary Penn Community members: UP.AUX-.affiliation description
  • individual auxiliary Penn Community member: UP.Penn Key.affiliation description
    • example: UP.mcurie.Wistar Faculty
    • For information on auxiliary members, see the documentation on the Penn Community MEMBER table.
Values:
List of values not available
Source: the KNODE.NAME for the business unit member
BUSINESS_UNIT_MEMBER_NUMBER

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

A number used to uniquely identify the business unit member within the Knowledge Link system. See also BUSINESS_UNIT_MEMBER_ID and BUSINESS_UNIT_MEMBER_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. 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.

Business units are arranged in a hierarchy. The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member. (See also BUSINESS_UNIT_GROUP_NUMBER.)

The business unit hierarchy is based on the hierarchies of the administrative groupings in the source systems, as described briefly below. (See also BUSINESS_UNIT_MEMBER_TYPE_DESC.)

University business units

  • Business units for University orgs. follow the University's org. hierarchy. A business unit for a University employee with a FAC or STAF affiliation in the Penn Community has as its parent the business unit for the employee's home org. (The home org. is the organization that owns the employee's record and is responsible for its maintenance in the payroll system.)
    • For information on orgs., see the General Ledger data collection's documentation on the ORG_CODES table; the documentation on its PARENT_ORG_CODE data element describes the org. hierarchy. For information on University employees, see the Salary Management data collection's documentation on EMPLOYEE_GENERAL.
  • The business unit for a University major has as its parent the business unit for the University academic division that offers the major.
    • For information on academic divisions and majors, see the Student data collection's documentation on the DIVISION and MAJOR tables (updated nightly).
  • The business unit hierarchy for University students parallels the hierarchy for the academic divisions and majors. A business unit for a University student has as its parent the UP.STU- business unit for the student's primary major in his or her primary academic division, per the SRS_DIVISION and SRS_MAJOR in the record for the student in the Penn Community AFFILIATION table.

UPHS business units

  • Most Health System business units use the same hierarchy as for the UPHS entities (also known as process levels) and departments (also known as a cost centers or accounting units).
  • The UPHS branch of the business unit hierarchy has a separate sub-branch for Knowledge Microcommunities. (See also TYPE.)
  • 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 business units

  • A business unit has been created for each auxiliary Penn Community affiliation. The business unit for a Knowledge Link user with an auxiliary affiliation has as its parent the UP.AUX- business unit for the user's auxiliary Penn Community affiliation (per the Penn Community AFFILIATION table).

Example: 21073

Values:
Refer to the KNODE table for values.
Source: the KNODE.KNODE_ID for the business unit member
BUSINESS_UNIT_MEMBER_SOURCE

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

A code that indicates the ultimate source of the information on the business unit member (BUSINESS_UNIT_MEMBER_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. 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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Values:
HS (the University of Pennsylvania Health System)
LMS (the Learning Management System (Knowledge Link)) UP (the University of Pennsylvania)
BUSINESS_UNIT_MEMBER_TYPE_ABBR

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

An abbreviation (in upper case) of the BUSINESS_UNIT_MEMBER_TYPE_DESC (the description of the business unit member's type). The type determines whether and how Knowledge Link users and courses can be assigned to the business unit member (BUSINESS_UNIT_MEMBER_ID). See also BUSINESS_UNIT_MEMBER_TYPE_CODE and BUSINESS_UNIT_GROUP_STATUS.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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) or 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.
Values:
KC  (Knowledge Community)
KMC (Knowledge Microcommunity)
KP  (Knowledge Position)
Source: LMS_BUSINESS_UNIT_TYPE.BUSINESS_UNIT_TYPE_ABBR
for the business unit member type code stored in LMS_BUSINESS_UNIT_GROUP.BUSINESS_UNIT_MEMBER_TYPE_CODE
BUSINESS_UNIT_MEMBER_TYPE_CODE

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

A number that uniquely identifies the business unit member's type. The type determines whether and how Knowledge Link users and courses can be assigned to the business unit member (BUSINESS_UNIT_MEMBER_ID). See also BUSINESS_UNIT_MEMBER_TYPE_DESC, BUSINESS_UNIT_MEMBER_TYPE_ABBR, and BUSINESS_UNIT_GROUP_STATUS.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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) or 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.
Values:
158 (Knowledge Community)
159 (Knowledge Microcommunity)
160 (Knowledge Position)
Source: the KNODE.TYPE for the business unit member
BUSINESS_UNIT_MEMBER_TYPE_DESC

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

The description of the business unit member's type (in mixed case). The type determines whether and how Knowledge Link users and courses can be assigned to the business unit member (BUSINESS_UNIT_MEMBER_ID). See also BUSINESS_UNIT_MEMBER_TYPE_ABBR, BUSINESS_UNIT_MEMBER_TYPE_CODE, and BUSINESS_UNIT_GROUP_STATUS.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

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) or 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.
Values:
Knowledge Community
Knowledge Microcommunity
Knowledge Position
Source: LMS_BUSINESS_UNIT_TYPE.BUSINESS_UNIT_TYPE_DESC
for the business unit member type code stored in LMS_BUSINESS_UNIT_GROUP.BUSINESS_UNIT_MEMBER_TYPE_CODE

DATE_BU_GROUP_CREATED

Indexed - no
Format - date
May be null? yes

The date when the KNODE record for the business unit group (BUSINESS_UNIT_GROUP_ID) was created in Knowledge Link.

If BUSINESS_UNIT_GROUP_NUMBER = BUSINESS_UNIT_MEMBER_NUMBER, DATE_BU_GROUP_CREATED also indicates when the KNODE record for the business unit member (BUSINESS_UNIT_MEMBER_ID) was created in Knowledge Link.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Example: 10/24/2006

Values:
List of values not available
Source: the KNODE.DATE_CREATED for the business unit group
DATE_BU_GROUP_MODIFIED

Indexed - no
Format - date
May be null? yes

The date when the KNODE record for the business unit group (BUSINESS_UNIT_GROUP_ID) was last updated in Knowledge Link.

If BUSINESS_UNIT_GROUP_NUMBER = BUSINESS_UNIT_MEMBER_NUMBER, DATE_BU_GROUP_MODIFIED also indicates when the KNODE record for the business unit member (BUSINESS_UNIT_MEMBER_ID) was created in Knowledge Link.

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. Business units are arranged in a hierarchy. (See BUSINESS_UNIT_GROUP_NUMBER and BUSINESS_UNIT_GROUP_TYPE_DESC.) The members of business unit group X are business unit X itself and all of the business units that fall below it in the hierarchy. The LMS_BUSINESS_UNIT_GROUP table has one record per combination of business unit group and business unit member.

Example: 11/13/2007

Values:
List of values not available
Source: the KNODE.DATE_MODIFIED for the business unit group
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_GROUP 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