Inheritance and Overrides
When configuration elements are the same throughout an Enterprise, inheritance allows you to configure the elements once and use them throughout the properties and revenue centers. When an operation differs at the property or revenue center levels, override allows you to break away from the inheritance.
When you configure a module at the Enterprise level, the property and revenue center levels inherit the module settings. If you want the property or revenue center to have a different configuration than the Enterprise level, you can override the inheritance at the property and revenue center levels. For example, you can configure menu items at the Enterprise level, and override the menu items for a property by changing the configuration at the property level.
-
Defined Here, No Override: This status indicates the record is defined in the location of the module that is open. The record does not override another record. It is possible that another record overrides this record. (EMC is not aware of records below the current location.)
-
Inherited: This status indicates the record is defined in another location, and it is inherited in the current module and location.
-
Defined Here, Overriding: This status indicates the record is defined in the location of the module that is open. The record overrides another record from a higher location.
For modules that support inheritance, create an override at a location when that location requires a different value. You cannot edit an inherited record from a child hierarchy level. When overrides exist for a record, the value at the lowest hierarchy level applies.