If a central InfoObject with relationships with local characteristics is changed and activated, these local characteristics are automatically adjusted, together with any CompositeProviders defined on them.
In the administration screen for BW Workspaces, you can view a log detailing changes to InfoObjects and recognize how these will affect your local characteristics and CompositeProviders. You can call the log by choosing Display Impact Logs for InfoObjects in the initial screen for BW Workspace administration.
If the attribute is not authorization-relevant, it appears as a non-modifiable attribute in the local characteristic. All local CompositeProviders dependent on the local characteristic are reactivated, making the new attribute visible in the queries defined on it.
If an attribute is deleted from the local characteristic, all local CompositeProviders dependent on the local characterstic are reactivated. In certain cases, the existence of the deleted attribute is a prerequisite for a local attribute. This can be the case if the attribute is a compound parent of a local attribute. In this case, a local attribute is created for the local characteristic. This local attribute references the deleted attribute in order to keep the local characteristic consistent.
If A1 is now deleted from the master InfoObject, the local attribute A2 still exists in the local characteristic but does not have a compound parent. In order to avoid this inconsistency, a local attribute is created that references A1. A2 is thus fully specified again.
The local characteristic is reactivated. This has no effect on the local CompositeProviders.
If the attribute is not excludes from the characteristic, all CompositeProviders that use the local characteristic and that have the attribute as a navigation attribute are reactivated. You can exclude attributes in the definition of the local characteristic when editing attributes.
If the attribute is not excludes from the characteristic, all CompositeProviders that use the local characteristic and that have the attribute as a navigation attribute are reactivated.
If the attribute is not excludes from the characteristic, all CompositeProviders that use the local characteristic and that have the attribute as a navigation attribute are reactivated.
If the InfoObject is a master InfoObject, the local characteristics have to be modified so that they have the same text properties. All local CompositeProviders dependent on the local characteristic are activated. If however the InfoObject is a navigation attribute in a master InfoObject or is assigned to a local attribute of a local characteristic, only the local CompositeProviders that have the attribute as their navigation attribute are reactivated.
If the compound parent is deleted or added for a master InfoObject, the local characteristic is modified accordingly. The compound parent is only added to the local characteristic, if the parent is not authorization-relevant. All local CompositeProviders are reactivated. If the compound parent is authorization relevant, the master InfoObject cannot be used as the basis for local characteristics anymore. All local characteristics are deleted, and the CompositeProviders are set to inactive.
If the compounding is removed, an attribute might habe been excluded because of its authorization-relevant compound parent in the local characteristic. In this case, the attribute will appear again. If the InfoObject was used in a local attribute, a new local attribute is created with the compound parent.
If the InfoObject is a master InfoObject, the local characteristics are deleted, and the CompositeProviders set to inactive. If the attribute is in a master InfoObject, the same procedure applies as when deleting attributes. If the attribute is referenced in a local attribute, it is also deleted from the local characteristic, and all CompositeProviders are activated.
If the InfoObject is marked as authorization relevant, and the InfoObject is a master InfoObject or a parent of a master InfoObject, the same applies as when deleting an InfoObject. If the InfoObject is an attribute of a master InfoObject, it is excluded and processed the same way as for deletion of an attribute. If it is referenced in a local attribute, this attribute is deleted from the local characteristic.
Whenever an attribute is deleted from the local characteristic, the local data for this attribute is lost. Changing the authorization relevance of an InfoObject in particular can result in data being deleted from local characteristics and not being reproducible when this property is restarted.
If modification of the local characteristic terminates or cannot be performed, because the Workspace is locked for example, you can restart it. To do this, you use report RSL_WSP_EXECUTE_IOBJ_IMPACT. You can find the parameters required from the messages in the log. You have to select the corresponding action on an InfoObject and also the attribute name in the case of attributes. If you choose Force Activation, all affected objects are activated.