Skip to main content
C
ChoolweJoe
April 9, 2025
Solved

Entity - In Use Feature

  • April 9, 2025
  • 1 reply
  • 0 views

Hi all,

We have a situation where an Entity was created and incorrectly set up and contains data for period 2024M12 and 2025M3.

We decided to create a new Entity and updated the transformation rules to ensure that the data loaded goes to the newly created member and not the old one.

We have set the consolidation and ownership percentage of the old entity to 0 as added measure.

We are now faced with the challenge of not deleting the member as it contains data.

Kindly asking if it is advisable to set the In Use feature in this scenario and is there any impact that would cause.

Thanks in advance.

Best answer by rhankey

I would presume in the two months since the question was asked that you might have conducted a couple tests in a sandbox to discover the answers to your questions.  However, if this still remains an unknown:

  • Setting InUse=False will prevent new data from being imported.  This property is ScenarioType/Time varying, so can allow you to load or reload data up to a certain point, and prevent doing so thereafter.
  • Setting PercentConsolidation=0 for the Parent/Child relationship will stop the entity from consolidating (aggregating) to the parent entity.  This property is ScenarioType/Time varying as well, so you can have it consolidate to one parent up to a certain point in time, and not thereafter.  If the entity where to have moved, you could assign the same entity to a second parent, to which you would set PercentConsolidation=100% after a certain time period.  When combined with some custom member lists, PercentConsolidation opens the door into time varying Entity hierarchies - where the hierarchy users see in reports will vary based on what ScenarioType/Time period they run the report for.

 

1 reply

C
chul
May 6, 2025

If it's an entity that contains data but you don't want it to consolidate nor allow users to mistakenly load data to it, you can change the In Use to False. What type of impacts are of concern?

C
ChoolweJoeAuthor
May 23, 2025

Hi Chul,

Thanks for the feedback.

My concern was if the data that still exists, preserve it for Historical reload but date stamp the In Use to avoid data being loaded to the Entity in the future.

R
rhankeyAnswer
May 23, 2025

I would presume in the two months since the question was asked that you might have conducted a couple tests in a sandbox to discover the answers to your questions.  However, if this still remains an unknown:

  • Setting InUse=False will prevent new data from being imported.  This property is ScenarioType/Time varying, so can allow you to load or reload data up to a certain point, and prevent doing so thereafter.
  • Setting PercentConsolidation=0 for the Parent/Child relationship will stop the entity from consolidating (aggregating) to the parent entity.  This property is ScenarioType/Time varying as well, so you can have it consolidate to one parent up to a certain point in time, and not thereafter.  If the entity where to have moved, you could assign the same entity to a second parent, to which you would set PercentConsolidation=100% after a certain time period.  When combined with some custom member lists, PercentConsolidation opens the door into time varying Entity hierarchies - where the hierarchy users see in reports will vary based on what ScenarioType/Time period they run the report for.

 

Terms & ConditionsAccessibility statement