Resource outline code vs. Enterprise Number

[Kevin M]

Greetings,

I'm flying solo now on a Project 2003 EPMS a consultant helped out with on a
lot of the initial configuration as I was training up, and am noticing that
some outline codes contain only 1st-level items in the lookup table.

Since Project-level custom fields are also available in Portfolio Analyzer
(the main place we'll be using the coding for analysis) I was wondering why
it might be better to use an outline code to define, say, a resource's cost
center when I could assign a Resource Enterprise Number to contain the same
data and use the same values in the lookup table for the Number value list.

Other than saving me the effort, is there any reason to use outline coding
rather than project and resource level value lists when all items in the
lookup table are 1st-level?

Thanks,
Kevin

 

[Dale Howard [MVP]]

Kevin --

It sounds like your consultant knew what he/she was doing. Here's why
he/she created custom enterprise Project and Resource outline codes instead
of using custom enterprise fields with a Value List: because custom
enterprise Project and Resource outline codes automatically become available
Dimensions in the OLAP cube. This means that you can use these Dimensions
in Portfolio Analyzer views for reporting purposes. If you use custom
enterprise Project and Resource field with a Value List, they DO NOT become
Dimensions in the OLAP cube. Thus, your consultant knew he/she was doing.
Hope this helps.

 

[Kevin M]

Yes, he was good, but at the time I knew even less than now so I didn't know
to ask him exactly "why" he did it. I'll continue to use the outline coding
for my desired OLAP dimensions, I thought I'd checked the available field
list in Analyzer and seen some custom fields there, but thinking back on it
was probably the outline code we're calling "Project Number."

Thanks for the response.
--Kevin

 

[Dale Howard [MVP]]

Kevin M --

You are more than welcome, my friend!