Account Attribute: In Use versus Allow Input

Hi all,

We have hundreds of historical (no longer valid) accounts sitting in a cube and we are looking at ways of de-cluttering resulting data retrievals to avoid seeing them.  But additionally, we want to prevent any accidental loading to these accounts from the source system.

For reporting, I know we can populate one of the text fields with some text and then combine that with a Where() clause to filter out these old accounts.

But, from a data load perspective, just wondering what the risks / benefits are of utilizing either (or both) of the In Use or Allow Input attributes; to prevent accidental loading of data there.

• We want to be able to continue to see any historical data for these accounts and be able to drilldown from the parent account and see that data.
• There are no member formulas associated with these - they are all base accounts.
• We don't care about the Scenario/Time specificity capability

If anyone is using these attributes would very much appreciate any recommendations or hearing what your experience has been (before we go through the effort of testing either of these options).

Many thanks,
K.