7.1 Creating Positions & Position Hiring Restrictions

7.1 Creating Positions & Position Hiring Restrictions

Quick Summary: In Position Management, capacity starts as a Position—a durable seat in a Supervisory Organization. Create Position defines that seat with an effective date and position restrictions (Job Profile, location, time type, worker type, availability, org assignments). Those restrictions gate Hire and keep every fill aligned to the budgeted role design.

Jobs and Positions is a high-yield block inside HCM Fundamentals (about 30 of 50 questions on Workday Pro HCM Core). Blueprint tasks T28 Create positions and T29 Set hiring restrictions on positions assume you already know staffing models (Chapter 4) and Job Profiles (Chapter 5). This section turns those foundations into the operational steps that create and constrain seats.

Why Create Position Exists

Under Position Management, a Supervisory Organization does not accept unbounded hire volume into empty air. You typically:

1. Create Position (often with approvals) so a vacant seat exists.
2. Optionally open recruiting against that seat.
3. Hire (or staff) a worker into the position.

Without a position (or without creating one as part of the hire design), there is no approved seat to fill. That is the control finance and workforce planning paid for when they chose Position Management over Job Management.

Exam trap: Create Position is not Hire. A vacant position can sit open for months with no Worker attached.

Create Position — Conceptual Flow

Exact labels and required fields vary by tenant, but the exam-aligned flow is stable:

1. Initiate Create Position for a Position Management Supervisory Organization (security-gated—often HR Partner, HR Admin, or a workforce-planning role).
2. Set effective date — when the seat becomes true for HCM processing (distinct from the moment someone clicked Submit).
3. Enter position restrictions that define the seat (see next section).
4. Complete organization assignments so the seat sits correctly for supervisory, financial, and location reporting.
5. Route through the Create Position business process (approvals, To Dos, notifications per tenant design).
6. On completion, the Position exists as unfilled / open (subject to freeze/close and availability rules covered in 7.2).

Supervisory Org (Position Management)
        │
        ▼
Create Position (effective date + restrictions + org assignments)
        │
        ▼
Business Process approvals (HR / Finance / Manager as designed)
        │
        ▼
Vacant Position object ──► ready for Hire / recruiting

Configuration scenario: Apex Manufacturing needs a new Plant Controller seat at Plant 3. An HR Partner initiates Create Position in Sup Org “Plant 3 Leadership,” effective the first day of next fiscal quarter. Restrictions set Job Profile “Plant Controller,” location Plant 3 HQ, full-time employee time type, Cost Center Plant3-Ctrl, Company Apex US. Finance approves the Create Position BP. Recruiting later opens a requisition against that vacant position ID—not against a free-text wish list.

Position Hiring Restrictions (T29)

Position restrictions (also called hiring restrictions on the position) are the seat’s rule set. They answer: What is this seat allowed to be, and what defaults should staffing events inherit?

Core restriction fields to memorize

Not every tenant shows every field with the same label, but the exam concept is fixed: restrictions live on the Position, describe the seat, and validate Hire and later job changes into that seat.

Job Profile on the position

The Job Profile on position restrictions is the bridge to the job catalog:

• Supplies default title, management level, compensation grade, qualifications, and classification into staffing.
• Does not turn the profile into a unique seat—many positions can share one profile.
• Changing the profile on a vacant seat via Edit Position Restrictions redesigns the seat for the next hire.
• Changing the profile expectation for a filled seat usually pairs with a worker Change Job (or related process) so the person’s job matches the seat.

Location, time type, and worker type

These three fields are frequent exam distractors because they sound like worker personal data:

• On the position, they are seat design (this role is full-time at HQ as an employee seat).
• On the worker/job, they become the assignment after Hire succeeds.
• A mismatch (trying to hire a contingent worker into an employee-only seat, or remote location into an on-site-only seat) should fail validation or require restriction edits first.

Organization assignments on the position

Positions inherit a Supervisory Organization as their staffing home. Additional assignments (Cost Center, Company, Location hierarchy context, Region, etc.) drive:

• Manager and HR Partner routing via Sup Org roles
• Financial defaulting and costing
• Reporting roll-ups

Exam trap: Assigning a Cost Center does not replace Create Position, and Cost Center is not a staffing model. It is an organization assignment on (or alongside) the seat.

Position Restrictions vs Organization Hiring Restrictions

You already contrasted staffing models; lock the restriction layers:

Both can exist in a mature tenant. Day-to-day Create Position work is about position restrictions. Do not answer a Create Position stem with “set Job Management org restrictions only.”

Edit Position Restrictions

Edit Position Restrictions maintains an existing seat without running Hire or Terminate:

Configuration scenario: Vacant position P-4401 was created for “Financial Analyst I” in Location A. The team re-levels the open seat to “Financial Analyst II” and moves it to hybrid Location B before posting. HR runs Edit Position Restrictions—not Create Job Profile (the FA II profile already exists) and not Hire (no person yet).

Business Process and Security Context

Create Position is a business process. Expect:

• Initiators with domain/BP security (e.g., HR Partner on that Sup Org).
• Approvals (manager, finance, HR) depending on definition.
• Possible To Dos (budget checklist, headcount form).
• Effective dating so future-dated seats appear when planned capacity starts.

If Create Position “fails,” diagnose in order: security (cannot initiate) → staffing model (org is Job Management) → validation (missing required restriction) → BP stuck (awaiting approval)—same multi-cause reasoning pattern used throughout HCM Fundamentals.

End-to-End Seat Design Checklist (Exam)

1. Confirm Sup Org uses Position Management.
2. Confirm Job Profile exists in the catalog (create profile first if brand-new role type).
3. Create Position with effective date and full restriction set.
4. Complete BP approvals so the seat is truly available.
5. Only then Hire into the position (Section 7.3) or freeze/close if plans change (Section 7.2).

Master Create Position and position restrictions as the capacity layer: seats first, people second. That sequence is the heart of T28–T29 and the setup for every later staffing event in this chapter.