Departments

Departments organize positions, access, requests, reporting, and financial responsibility. The department hierarchy can change by date without rewriting earlier history.

Before you begin

You need the Manage organization settings permission to create departments, change the hierarchy, manage availability, or maintain financial classifications.

Create a department

Before creating a department, decide its stable name, external identifier when used, place in the hierarchy, and first effective date. A department should represent a lasting area of responsibility, not a temporary project or a person’s name.

1. Open Settings, then Departments.
2. Enter the name and external ID when used.
3. Choose the parent department and effective date.
4. Review and save the department.
5. Configure the job codes that positions in the department may use.
6. Configure position availability when the department should be available only for a defined period.
7. Review the hierarchy on the first effective date.

A department name must be unique across the organization while the department is available, regardless of its level or parent. Changing capitalization or adding spaces does not create a different name. A name may be reused after the earlier department becomes unavailable, provided their availability periods do not overlap, including scheduled future periods.

The external ID is useful when a trusted source or reporting process already identifies the department. Keep it stable. Do not reuse an old ID for a different department.

Keep four department choices separate

Department access that includes lower-level departments follows the dated hierarchy. Moving a department can therefore change which records people can access. Review the affected department coverage before saving the move. Making a department unavailable does not remove earlier positions or reports. Review each choice separately.

Change the hierarchy

Add a later parent relationship when a department moves in the organization. Correct an existing relationship only when the recorded parent or date was wrong.

Example: department reorganization

Customer Operations reports under Operations through June 30 and under Customer Experience beginning July 1.

Record the new parent beginning July 1. A June 30 hierarchy report continues to show the earlier structure, while a July 1 report shows the new one.

Do not overwrite the earlier parent. That would make historical position and report views appear as if the later organization had always existed.

Before moving a department, review:

• lower-level departments that move with it;
• positions whose reporting lines cross the old and new structure;
• access coverage that includes lower-level departments;
• approval reviewers assigned by department; and
• reports used to compare periods.

Availability

Make a department unavailable when it should remain in history but no longer be selected for new work. Review active positions, members, requests, and financial responsibilities before changing availability.

Use a later availability period for a real opening or closure. Use Correct only when a recorded start or end date was wrong. Use Remove only when the availability period should never have existed.

If positions remain active after the proposed end date, resolve that conflict before ending availability. The page may prevent a change that would leave approved information without valid setup.

Financial classifications

Use Set up department financial classifications to configure general ledger segments, allowed codes, and dated department values. Lower-level departments can inherit values from the department above. Review that inheritance when moving a department.

Verify a department change

1. Select a date before the change and confirm the earlier hierarchy and availability.
2. Select the effective date and confirm the new result.
3. Open one affected position and confirm its department remains valid.
4. Review job code choices for a position in the department.
5. Review one access role whose department coverage could be affected.
6. Run Department Hierarchy when you need a repeatable review result.
7. Open Activity to confirm who recorded the change and why.

Does moving a department move every employee?

The move changes the department hierarchy. Employee and assignment ownership follows the dated records that apply to each person, not merely the department’s parent.

Can two departments use the same job code?

Yes, when the job code is available to both departments. Department availability controls selection without creating duplicate job codes.

Review structure changes

Open Structure changes from organization settings or the department navigation. Use Upcoming, Today, Prior, or All to choose when changes take effect. Narrow the list by date and search; where offered, select the record type or source. A department-specific view stays limited to department changes.

Open the affected record to review its before and after values and effective date. Check departments beneath a moved department and any access or job-code availability that follows that hierarchy. Use the record’s supported change action for a correction; the list itself is for review.

Use Activity history when you need to know who recorded a change and when, rather than when the business change takes effect.