Best Practice for Member codes naming convention in EPM Planning

we are creating metadata for the oracle planning application, however one of the point we want to check is what is the best practice for the naming convention of the members for the planning application. Is it best to include prefixes e.g. "ACC_" for Accounts, "ENT_" FOR entities as it would improve readability, Better experience in SmartView as sometime excel throws an error while confusing the codes with numbers and also prevents conflicts for codes and aliases across the dimensions. However we would like to understand Oracle view on what is the best practice