In basic terms, there is an indexation reference that runs run between the Cognos Controller and Planning Analytics applications. This is run through the FAP Publish Client.
When this update occurs on existing reporting structures that are already published and stable for content, the process runs as normal. There is no requirement for FAP Publish to update.
However, when a structural change is made within Controller, the FAP client triggers an update. This is because the existing indexation of structure within Planning Analytics does not include the new changes.
Where the changes are new elements, or additions to indexation, then the quick fix of ‘Update Structure’ from within the Data Marts tab will typically suffice. This update will push across the new elements.
However, where changes are made to structural content that has previously been published, then existing indexation references will need updating. The Partial Initial Publish will need to be run to re-align data and structure content. That being said, a full initial publish will also achieve the same result.
In summary, change management should be treated with care within Controller where content is integrated with Planning Analytics. Change activity is typically undertaken outside of the period end reporting cycle. This means that a stable position is held throughout the reporting period.