Enterprise Project Outline Code

[Leo]

My company want to keep the Projects Code that was generated in our sales
system in the Ms Project Server.
Because we want to export this project code through portfolio analyzer.

So, I implemented the "Enterprise Project Outline Code" to make the PM
could choose the "Project Code" from the drop-down list everytime when PM
saved their new project.

I am using 3 level lookup table, i.e:
level 1: Projects
level 2: Project A
level 3: Project A Code
level 2: Project B
level 3: Project B Code
level 2:
level 3:
level 2:
level 3:
....
....
....

I don't know is this the best solution because the project code is the
unique code for every project and it will be growth.
I am just worrying about the performance once the project code become
hundreds/ thousands.

Is anybody can give me some advice regarding to this situation ??
Thks in advance..

 

[Mike Mahoney]

Leo

You have little choice but to maintain the Sales system code in an outline
code, however there seems little point to hierarchy you created. You can
get the desired analysis with a one level code containing the list of sales
system values.

Mike

 

[Leo]

Mike,
Thanks for your response..

I thought it will be informative for the PM to choose the Project-Name first
and then PM can find the correct Project-Code as an sub-ordinate from
Project Name rather than choose the project-code directly.
Because the project code only containts 3 characters and 5 digit numeric.

What I want to know is the performance issues after the project code had
become hundred or thousand.
Anybody have the experience by using hundred or thousand enterprise outline
code ??