Customers using both IBM Controller and IBM Planning Analytics often ask when the FAP Publish client needs to be updated.
At a high level, the integration between the two systems relies on an indexed structure. This index is created and maintained through the FAP Publish client, which ensures Planning Analytics reflects the structure defined in Controller.
Existing Reporting Structures #
If you are working with an existing, stable reporting structure, there is typically no need to update the FAP Publish client.
For example, adding new data to an existing company or account will flow through as expected, with no structural impact. The existing indexation already supports this activity, so no further action is required.
Structural Changes #
Things change when the structure within Controller is updated.
Because Planning Analytics relies on the indexed structure created during publishing, any structural changes in Controller will not automatically be reflected. This is when the FAP Publish client needs to be used.
The level of update required depends on the type of change:
- New elements added
If you are introducing new entities, accounts, or other structural components, a simple “Update Structure” from the Data Marts tab is usually enough. This pushes the new elements into Planning Analytics without requiring a full refresh. - Changes to existing structures
If you are modifying structures that have already been published, the existing indexation becomes outdated. In this case, you will need to run either:- a Partial Initial Publish (for selected periods), or
- a Full Initial Publish (across all periods)
In most cases, structural changes will require a Full Initial Publish to ensure consistency across the model.
Impact of a Full Initial Publish #
A Full Initial Publish will temporarily stop reporting in Planning Analytics while the process runs.
The duration varies depending on the size and complexity of the system, so it is important to plan this carefully. Most organisations schedule this activity outside of reporting cycles to minimise disruption.
Best Practice #
When Controller is integrated with Planning Analytics, structural changes should be managed with care.
Where possible, make changes outside of period-end reporting. This helps maintain a stable reporting environment and avoids unnecessary disruption to users.
If you’re unsure whether a change will require an update, or want help planning your publish strategy, feel free to get in touch with the team at Aramar.
The latest IBM Controller production documentation can be found on the IBM website
