Might be dumb, and have forgotten about this topic, but how are the charge code entries populated in the lookup for the indirect time entry on the timesheet ?
Not entirely.. you can change the value in ways that force it to the bottom of the list (prefix with 'z') and/or use a 'Do not use' designator to discourage it from being used. When you cannot uncheck the Open for Time Entry option I believe they would be the only alternatives.
Do you mean how it derives the description field from the database, or how it chooses which Charge Codes to display from those available, or both / something else?
"how it derives the description field from the database" - yes
The reason I asked is this - let's say that the users do not want to see the value, e.g. Capital. If I try to uncheck the open from the chargecode on the admin side, it wouldn't allow me to do so as there are transactions.
So, I am looking for a way to hide the value. Would be great if that can happen from GUI itself, without unchecking the open option
All of the text data comes from the prchargecode table (it's not localized into different languages for example).
So the Description field on the timesheet takes from the Charge Code Name field on the charge code's properties UI (this value can be changed even with transactions existing). It also corresponds to prchargecode.prname in the database.
The Charge Code column on the timesheet is the Charge Code ID field in the charge code properties UI (and this value is not allowed to be changed once the charge code has been used on transactions). Its value comes from prchargecode.prexternalid in the database.
"So the Description field on the timesheet takes from the Charge Code Name field on the charge code's properties UI (this value can be changed even with transactions existing). It also corresponds to prchargecode.prname in the database."
In the case I mentioned for the description field, I would like to hide the External charge code. Would that be possible ?
"Whatever can happen, will happen." No matter how one prefixes or renames inactive selections, users will find them and use them, even unintentionally (e.g. an old project with a task using an inactive charge code is copied as a template into a new project....).
Many parts of CA PPM already disallow use of inactive items (e.g. static lookups). It is necessary that all parts of CA PPM function in a consistent manner, disallowing use of all inactive items (including departments, locations, charge codes, et cetera).
Retrieving data ...