11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

Quick Answer: Administrators create positions in Manage Positions, the Position Org Chart, Copy Position, or by import. Managers create them from My Team Positions or Joule. Records are effective-dated: insert new records, correct, or permanently delete. Changes made in the Position Org Chart or Manage Positions can sync to incumbents, but changes made in Manage Data never do. Bulk updates use Import and Export Data, a rule-based Mass Change Run, or UI-based Mass Data Management.

Why a Separate Manage Positions Tool

Managing positions works like other EC objects (correct or insert effective-dated records). Manage Positions lets an administrator work with positions only through the Access Manage Positions permission, without the general Manage Data permission for all MDF objects. Other targeted permissions follow the same idea, such as Manage Sequence and Manage Mass Changes for Metadata Objects.

Ways to Create Positions

THR79's example creates Director of Marketing (DIR_MKT) under VP, Sales with To Be Hired = Yes, 40 standard hours, FTE 1, Position Controlled = Yes, plus organizational fields. It then sets a matrix relationship so the future incumbent becomes the Matrix Manager of another position's incumbent.

Maintaining Existing Positions

In Manage Positions, search the position and use Take Action:

• Make Correction
• Permanently Delete Entry: delete one history record, or the whole position if only one record remains
• Add to Transport Bundle: with the Configuration Transport Center, to move data between instances
• Insert New Record: a new effective-dated record, keeping the history

From the Position Org Chart, Show Details > Edit inserts a change, and Manage corrects or deletes. Changing the parent position changes the reporting line. When THR79 moves Account Manager, NE under Sales Director, NC, the incumbent's supervisor changes automatically, with the event reason Supervisor Change Only derived by ERD.

Synchronizing Position Changes to Incumbents

Synchronize Position to Job Information is a business rule that decides which common fields flow from a changed position to its incumbents' Job Information. Position Management Settings decide whether the sync is automatic or a user decision (Sections 11.5 and 13.2). Position sync occurs only when the position is updated from the Position Org Chart or Manage Positions. Updates through Manage Data never sync.

Importing Positions

Position is an MDF object, so use Import and Export Data: download the Position template, fill it, choose Validate, check the result in Scheduled Job Manager (View Result), then Import.

• Include dependencies = Yes downloads a ZIP with related entities, such as Position Type, Position-Matrix Position, Legal Entity, and Division.
• To sync imported changes to incumbents, add a technicalParameters column with the value SYNC (or sync) for the rows that should sync. Rows without it update the position only.
• The technicalParameters field is Not Visible by default. Either add the column manually, or make the field Editable and hide it with a Field Level Override (No Access), so the template includes it automatically.

Follow-Up Processes After Imports

These need an active Centralized Services HRIS Event Publishing Configuration record (HrisSLEventPublishConfiguration) in Manage Data with Enable Event Publish = Yes. Customers using PM before 1H 2025 already have it. Then set Position Management Settings > Import:

• Adapt Reporting Hierarchy After Position Import
• Validate Position Assignment During Job Information Import: status active, multiple incumbents, FTE capacity
• Adapt Position "To Be Hired" Status After Job Information Import
• Execute Reclassification or Transfer After Job Information Import
• Defaulting of the Manager or Position and Hierarchy Adaptation After Imports
• Execute Job Relationship Sync After Imports, and the Job Relationship on Position Assignment option

Mass Change Run

A Mass Change Run updates many positions through a business rule. The IF selects the positions, for example in one legal entity, and the THEN sets new values, for example pay grade or location. Create it in Manage Mass Changes for Metadata Objects and assign the rule. Changes are effective-dated and can sync to incumbents (Section 13.2).

Mass Data Management for Positions

Mass Data Management is UI-based and replaces the traditional method of rules and scheduled jobs. You filter and sort positions, modify many with one request, review highlighted changes, save and share drafts, download logs, and filter by matrix relationship. Limits: 999 positions per request, Effective Date is the only mandatory filter, and up to 8 filters (Section 8.3).