Business Structure overview

A business structure defines trees containing nodes that represent these three components. Types represent logical organizational levels in your enterprise. Locations represent a physical location or a logistical unit that is not a physical location. Jobs represent roles with fixed responsibilities.

Introduction

A business structure's hierarchy consists of types, locations, and jobs:

• Types are logical organizational levels in your enterprise, such as region, division, store, area, and department.
• Locations can be a physical location (Operating Room or Mail Room) or a logistical unit that is not a physical location (Support, Administration, a Home Care Unit).
• Jobs are roles that have a fixed responsibility (Registered Nurse, Associate, Welder). Jobs are attached to locations on the business structure that represent locations where employees actually perform those jobs.

Labor Categories capture data that is not part of the hierarchical structure; typically, the "what" that is being worked on. Labor Categories are not required and are not mapped to the business structure.

Cost Center maps work to the General Ledger account in the financial system that pays for the work. The Cost Center field exists as an attribute on the business structure to charge work performed there to the company's General Ledger. This field is used whenever a different cost center is to be charged for work performed in a location than that location's attribute cost center. This separate charging can be:

• To the cost center of the employee's primary job
• To some other selected paying cost center

Six Labor Categories are available to describe the work performed.

Configuration

To define a business structure:

• Configure Cost Centers: This step is optional. Refer to the UI online help system for more information.
• Create Location Types: Define types for each level that you need in the business structure. When you build the business structure, you are required to attached an organizational type to each configured location. For example, when you configure a location for Boston, New York, and San Francisco, they each require a corresponding organizational type.
• Configure Locations: Using the API, you can create and manage Locations within the business structure to define the hierarchical relationships between them.
• Configure Jobs: Configure the Jobs that you will assign to the locations added to the business structure.

Note: Expiration dates in the Business Structure are exclusive dates. For example, when the expiration date is 01/31/2025, the 31st is not included in the span.

Build the Business Structure

Next, use the Business Structure API operations to establish a hierarchy of locations and jobs. You can use the operations listed in the API reference documentation to create, update, delete, and view jobs, locations, location sets, and location types.

Create Location Types

After you decide what types you need, create types using the Business
Structure Location Types (Organizational Map) resource.

You can specify the following attributes for each location type:

You cannot save the Location Type unless you specify all required fields.

Note that the following Org Types cannot be removed:

• All Org
• Company
• Site
• Department
• Job

Location Types are used for rolling up data in the KPI framework. The KPI framework supports rolling up by Job. Job can be the child of any node including the Company node.

Configure Locations

Using the API, you can create and manage Locations within the business structure to define the hierarchical relationships between them. This defines how the system handles scheduling, timekeeping, budgeting, reporting, and analytics.

• Company always begins as a default type at the top of the tree so you have a starting point, but you can edit it.
• You can create a new location type by adding a child location to the root node.
• You can update the existing location or create a new version with an effective date.

Note: A root node is the very first or parent node. Generally, nodes may have parent and children nodes, but because the root node is the first node, it only has children nodes. The business structure allows for trees containing multiple root nodes.

Remember, you can use the operations listed in the API reference documentation to create, update, delete, and view jobs, locations, location sets, and location types.

Note: You can only delete future dated types. Types that have an effective start date of Today, Beginning of Time or a date in the past cannot be deleted.

Configure Jobs

You can add one or more jobs to each location you configured. The job must be in the job list. The job can be the primary job or a transfer job. These jobs will be attached to locations in the business structure.

You can specify the following attributes for each job: