Recently I had to modify a BPC Model in BPC10MS: a new dimension had to be added.

We received the error message:

“This model has journals defined; you cannot modify the model structure”

BPC01.jpg

In the model there was a journal template implemented but no journals neither posted nor saved.

We found the error message is a little bit misleading, but using “cannot modify model” keyword in EPM-BPC* we found OSS Note 1792879 – BPC-MS: “This Application has the journals” message when attempting to modify an Application.

This note seems not be be usefull because:

  • related to BPC 7.0 and/or BPC 7.5 MS
  • with a different error message

Symptom

Attempting to modify an existing Application (for instance by adding or removing dimensions from the Application) generates the following message when processing the application:

“This Application has the journals. You cannot modify the application structure”

Environment

  • SAP Business Planning and Consolidation 7.0 for Microsoft
  • SAP Business Planning and Consolidation 7.5 for Microsoft

Reproducing the Issue

Add any dimension to an existing model that has journals active and then attempt to process the model.

Cause

As all active dimensions are taken into account in the journal tables and templates, it is impossible to modify the dimension structure of an application if journals are active.

But any way we tried to see if the solution was working, since we were on a development environment.

So we modified table dbo.tblApp on MS SQL Server Management Studio side:

MS01.jpg

We changed Journal value from 1 to 0, while the Environment was offline, and then we were able to add the new Dimension in the Model!

So consider the OSS Note applicable also in BPC10MS.

But be carefull because of the warnings in the Solution proposed:

Resolution

Once activated, journals cannot be inactivated via the Administrator client.

The only solution is to modify the database tables directly.


WARNING: Doing so will invalidate all journal entries in the database. This should not be attempted unless you are sure that the existing journals are no longer needed and all data in the journals has been posted and properly validated or un-posted to back out the journal changes. Because of the possibility of data inconsistencies after this modification, it is strongly recommended that you test this process and validate your Application after changing it in a test environment before you perform the same change in production.


Process to inactivate Journals via database:

  1. For safety, first set the Application set as “Not Available” via the Administrator client and then close Administrator.
  2. Login to SQL Server and expand the database for the application set containing the application you wish to modify.
  3. Edit the ‘tblApp’ table and change the “Journal” column value from 1 to 0 for the Application you wish to disable.
  4. Open the Administrator client and set the Application set back to “Available”

Hope it helps!

GFV

To report this post you need to login first.