Dimension Configuration
Dimensions contain the hierarchies for the application and provide the foundation for metadata management in EPMware. This section covers the configuration and management of dimension classes, hierarchies, properties, mapping, and hierarchy actions.
Dimensions module showing the hierarchy structure and configuration options
Overview
The Dimensions module is comprised of the following components:
- Dimension Classes - Highest level component that groups dimensions
- Dimension Configuration - Define dimension attributes and settings
- Dimension Properties - Configure dimension-specific properties
- Dimension Mapping - Associate dimensions across applications
- Hierarchy Actions - Configure actions for dimension hierarchies
Quick Links
Dimension Classes
Dimension classes are the highest level component of dimensions. A dimension class can contain one or many dimensions, providing a logical grouping for related hierarchies.
Key Features
- Hierarchical Organization - Group related dimensions under a single class
- Action Set Assignment - Assign hierarchy action sets to control available operations
- Inheritance - Dimensions inherit properties from their parent class
- Security Integration - Apply security at the class level
Hierarchy Action Sets
EPMware includes pre-built hierarchy action sets for each application type:
- ANAPLAN - Hierarchy Actions
- Essbase - Hierarchy Actions
- FCCS - Hierarchy Actions
- FDMEE - Hierarchy Actions
- GENERIC - Hierarchy Actions
- HFM - Hierarchy Actions
- HSS - Hierarchy Actions
- ORACLE EBS - Hierarchy Actions
- ORACLE Fusion Cloud - Hierarchy Actions
- OneStream - Hierarchy Actions
- PBCS - Hierarchy Actions
- PCMCS - Hierarchy Actions
- Planning - Hierarchy Actions
- SAP Business Objects - Hierarchy Actions
- TRCS - Hierarchy Actions
Note
Hierarchy action sets are automatically assigned to dimension classes based on the application type. Custom action sets can be created for specific business requirements.
Common Dimension Classes
| Class Type | Description | Typical Dimensions |
|---|---|---|
| Financial | Core financial reporting dimensions | Account, Entity, Currency |
| Organizational | Business structure dimensions | Department, Cost Center, Region |
| Product | Product and service hierarchies | Product Line, Brand, Category |
| Generic | Flexible, multi-purpose dimensions | Custom1-8, User Defined |
Best Practice
Create dimension classes that align with your business structure. This simplifies administration and improves user experience.
Configuration Steps
- Navigate to Configuration → Dimensions → Classes
- Click the + icon to create a new class
- Configure class attributes:
- Name - Unique identifier for the class
- Hierarchy Action Set - Select from predefined sets
- Description - Document the class purpose
- Security Class - Optional security assignment
Dimension Classes configuration screen showing available classes
Add Class dialog with hierarchy action set selection
View Detailed Configuration Guide →
Dimension Configuration
Dimension configuration defines the attributes and behavior of individual dimensions within EPMware.
Dimension Configuration screen with application and dimension class filters
Core Attributes
| Attribute | Description | Impact |
|---|---|---|
| Enabled | Activates dimension in EPMware | Controls visibility and usability |
| Security Class | Assigns dimension-level security | Restricts access to authorized users |
| Read Only | Prevents modifications | Useful for reference dimensions |
| Derived | Flags as calculated dimension | Values populated via SQL scripts |
| Default Alias | Sets primary alias table | Determines default display names |
Advanced Configuration
Derived Dimensions
Derived dimensions are read-only hierarchies populated through SQL scripts:
-- Example: Derive organization hierarchy from source system
SELECT parent_code, child_code, consolidation
FROM source_system.org_hierarchy
WHERE active_flag = 'Y'
Security Configuration
Apply security at multiple levels: 1. Dimension Class - Broadest level 2. Individual Dimension - Specific dimension access 3. Member Level - Granular node security
Security Class property in the System category for member-level security
Security Precedence
Member-level security takes precedence over dimension security, which takes precedence over class security.
Dimension Attributes dialog showing configuration options
View Detailed Configuration Guide →
Dimension Properties
Dimension properties store configuration values specific to each dimension, controlling behavior and integration settings.
Dimension Properties screen showing application and dimension specific properties
Property Categories
System Properties
- Hierarchy type (Stored/Dynamic)
- Consolidation settings
- Data storage options
- Calculation rules
Integration Properties
- Source system mappings
- Import/export settings
- Validation rules
- Transformation logic
Custom Properties
- User-defined attributes
- Business metadata
- Reporting tags
- Workflow parameters
Member Properties Configuration
For detailed configuration of member properties including categories, mapping, validation, and derivation, see the Member Properties section. This includes: - Property category assignment and workflow filtering - Property mapping across dimensions - Property validation scripts - Property derivation rules
Managing Properties
Properties can be added, edited, or removed based on business requirements:
- System Properties - Predefined, cannot be deleted
- Application Properties - Imported from target systems
- Custom Properties - User-created for specific needs
Add Dimension Properties dialog
Dimension Properties dialog for editing property values
View Detailed Configuration Guide →
Dimension Mapping
Dimension mapping enables synchronization between dimensions across different applications, ensuring consistency in master data.
Dimension Mapping configuration with sync options across applications
Mapping Options
| Option | Description | Use Case |
|---|---|---|
| Sync | Full synchronization of members | Homogeneous hierarchies |
| Smart Sync | Conditional synchronization | Heterogeneous hierarchies |
| Script | Custom logic-based sharing | Complex transformations |
Mapping Workflow
graph LR
A[Source Dimension] --> B{Mapping Type}
B -->|Sync| C[Direct Copy]
B -->|Smart Sync| D[Conditional Copy]
B -->|Script| E[Transform & Copy]
C --> F[Target Dimension]
D --> F
E --> F
Configuration Example
Scenario: Map Account dimension between HFM and Planning applications
- Select dimensions to map
- Choose mapping type (Sync/Smart Sync/Script)
- Configure options:
- Parent validation
- Property mapping
- Conflict resolution
Note
Each mapped dimension creates a line item in the request workflow, allowing reviewers to approve changes per application.
Example of mapping Measures dimension between BSO Demo Classic and BSOALL applications
View Detailed Configuration Guide →
Hierarchy Actions
Hierarchy actions define the operations users can perform on dimension hierarchies, with optional pre and post-action scripts.
Hierarchy Actions configuration showing available actions and script assignments
Available Actions
The following hierarchy actions are available across different application types:
| Action | Description | Notes |
|---|---|---|
| Copy | Copy members and properties between applications/dimensions | Followed by Paste action |
| Cut | Move members within hierarchy | Followed by Paste action |
| Paste | Paste copied or cut members | As Child/Sibling/Replace |
| Create Member | Add new members | As Child or Sibling |
| Insert Member | Create from another application | For unmapped dimensions |
| Clone Member | Duplicate with all properties | Creates exact copy |
| Edit Properties | Modify member attributes | Based on security |
| Reorder Children | Change child member order | Parent level operation |
| Delete Member | Remove members and descendants | Multiple selection allowed |
| Rename Member | Change member name | Not available for all apps |
| Insert Shared | Create shared instances | Multiple selection allowed |
| Remove Shared | Remove shared instances | Specific instance removal |
| Activate/Inactivate | Toggle member status | Generic apps only |
📝 Create Member
Add new members to hierarchy
✏️ Edit Properties
Modify member attributes
🔄 Move Member
Relocate within hierarchy
🗑️ Delete Member
Remove from hierarchy
📋 Copy/Paste
Duplicate structures
🔗 Insert Shared
Create shared members
Action Scripts
Enhance hierarchy actions with Logic Builder scripts:
- Pre-Action Scripts - Validate before executing
- Post-Action Scripts - Automate follow-up tasks
Example: Auto-position in Shared Hierarchy
// Post-action script for Create Member
function positionInSharedHierarchy(member) {
if (isPrimaryHierarchy(member.parent)) {
var sharedParent = findSharedParent(member.type);
if (sharedParent) {
createSharedMember(member, sharedParent);
}
}
}
Security Integration
Assign security classes to specific actions:
- Restrict "Delete Member" to administrators
- Limit "Edit Properties" to data managers
- Control "Create Member" by dimension
Edit Hierarchy Action Properties dialog with pre/post action script configuration
View Detailed Configuration Guide →
Best Practices
1. Dimension Design
- Standardize Naming - Use consistent naming conventions
- Document Purpose - Maintain clear descriptions
- Plan Hierarchies - Design before implementation
- Consider Growth - Allow for future expansion
2. Performance Optimization
- Limit Depth - Keep hierarchies reasonably shallow
- Optimize Scripts - Test and tune SQL/Logic scripts
- Archive Inactive - Remove or hide obsolete members
- Index Properly - Ensure database indexes are maintained
3. Security & Governance
- Layer Security - Apply at appropriate levels
- Audit Changes - Enable comprehensive logging
- Review Regularly - Periodic access reviews
- Document Policies - Maintain governance documentation
4. Integration Management
- Test Mappings - Validate in non-production first
- Monitor Sync - Check mapping logs regularly
- Handle Conflicts - Define resolution strategies
- Version Control - Track configuration changes
Troubleshooting
Common Issues
| Issue | Possible Cause | Solution |
|---|---|---|
| Members not syncing | Mapping disabled | Check mapping configuration and enable |
| Hierarchy actions grayed out | Insufficient permissions | Verify security class assignments |
| Derived dimension empty | SQL error | Review SQL script and test independently |
| Import failures | Property mismatch | Validate property mappings |
Getting Help
- Check the detailed configuration guide
- Review application-specific requirements
- Contact EPMware support for assistance