The Validity field is used to define the period during which an Organizational Unit is valid in the organizational structure.

New Store Opening

A new store is planned to open on 1 October. The Organizational Unit can be created in advance with its validity starting on the opening date.

Configuration:

• Organizational Unit – Brno Store
• Valid From – 1 October
• Valid To – not specified

The store becomes part of the valid organizational structure from its planned opening date.

Permanent Branch Closure

A branch is scheduled to close permanently on 31 December.

Configuration:

• Organizational Unit – Branch
• Valid From – existing start date
• Valid To – 31 December

The validity period reflects when the branch ceases to be a valid Organizational Unit without requiring the unit to be removed from the structure.

Temporary Organizational Unit

A temporary unit is established for a defined period, for example for a seasonal operation.

Configuration:

• Organizational Unit – Seasonal Store
• Valid From – 1 November
• Valid To – 31 December

The Organizational Unit is valid only for the configured period, allowing the temporary part of the organization to be represented without treating it as a permanent unit.

The Parent Org. Unit and Validity fields are used to define where an Organizational Unit belongs in the hierarchy and during which period the relationship is valid.

Store Transfer Between Regions

A store currently belongs to the Central Region, but from 1 January it will become part of the East Region.

Configuration:

• Current Parent Org. Unit – Central Region
• Current relation Valid To – 31 December
• New Parent Org. Unit – East Region
• New relation Valid From – 1 January

The store remains the same Organizational Unit, while its position in the hierarchy changes from the effective date of the reorganization.

Department Transfer Between Production Plants

A department is transferred from one production plant to another as part of an organizational restructuring.

Configuration:

• Current Parent Org. Unit – Production Plant A
• Current relation Valid To – 30 June
• New Parent Org. Unit – Production Plant B
• New relation Valid From – 1 July

The validity of the relationships preserves the previous organizational assignment while defining the department's new position from July.

The Automatically Generate Shifts field is used to configure automatic shift generation for an Organizational Unit and its subunits.

Regional Store Network

A retail organization wants automatic shift generation to apply to all stores within one region.

Configuration:

• Organizational Unit – Region
• Automatically Generate Shifts – Yes including subunits

Automatic shift generation applies to the Region and all Organizational Units below it without configuring each Store separately.

Manually Planned Branch Network

A bank manages shifts manually for all branches within one region.

Configuration:

• Organizational Unit – Region
• Automatically Generate Shifts – No including subunits

Automatic shift generation is disabled for the Region and all Organizational Units below it.

Inherited Configuration

Individual Stores should follow the automatic shift generation configuration defined higher in the organizational hierarchy.

Configuration:

• Organizational Unit – Store
• Automatically Generate Shifts – Inherit

The Store inherits the applicable automatic shift generation setting instead of requiring its own configuration.