Enterprise Outline codes (Project, Resource, Task), an absolute an

[richardsantink]

I've searched and read the many posts here with respect to Enterprise custom
fields, as well as Enterprise outline codes. Recently we had a consultant
tell us to use Enterprise custom fields over Enterprise outline codes (task,
resource, and project), because we would not be able to report on Enterprise
custom fields/outline codes without purchasing additional software.

I thought that PS2003 could use Enterprise outline codes as dimensions in an
OLAP cube?
Can somebody confirm that this is correct or incorrect?

The reason i want to go with EOCs is that there is a hierarchical
relationship between the types of tasks we need to report on. For example

Development
|---- DVDs
|---- Training Materials
|----- Self-paced
|----- Instructor-led
|---- Documentation
|---- HTML/XML code

I need to report the amount of time that is spent on each of those 'types'
of tasks.

So, again CAN PS2003 use EOCs to report on this, or am I stuck with using
Enterprise custom fields, which allow for user error when selecting.

Thanks in advance,

Richard Santink

 

[Gary L. Chefetz [MVP]]

Richard:

Must have been a "free" consultant, because you got information that was
worthless. Both Project and Resource Enterprise Outline Codes become
dimensions in the Project Server 2003 OLAP cube. You do not need additional
software to report on their values unless you don't know SQL.

--


Gary L. Chefetz, MVP
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com
For Project Server Books: http://www.projectserverbooks.com
For Project Server Training: http://www.projectservertraining.com
For Project FAQS: http://www.mvps.org/project

 

[Marc Soester]

Hi Richard,

this information that the consultant gave you is wrong. When you create
Outline Codes, they will become Dimensions in the OLAP Cube.

I think what this guy ment was that if you create custom fields, out of the
box these custom fields will not become OLAP Cube Dimensions, which is
correct.

If you want to report against custom fields within the OLAP cubes, then you
either have to custom develop these requirements, or you purchase a third
party product which does this for you. You can check out this 3rd party
product called "Portfolio Analyser Extender" under:

http://www.bogdanov-associates.com/eng.asp?rubr_id=476

we have been using it for many implementations and it does greatly improve
your reporting capabillity ( e.g. custom fields extention, task level
reporting)
I hope this helps

 

[richardsantink]

Thanks Marc and Gary for you responses...

This is where I think I get confused:

I think what this guy ment was that if you create custom fields, out of the
box these custom fields will not become OLAP Cube Dimensions, which is
correct.

If you want to report against custom fields within the OLAP cubes, then you
either have to custom develop these requirements, or you purchase a third
party product which does this for you. You can check out this 3rd party
product called "Portfolio Analyser Extender" under:

Does this not contradict what Gary posted? I am either not clear on the
definition of 'custom fields' or, if we mean the same thing when we say
'report against' them.

I need to take the hierarchical outline codes, and produce a printable (or
soft) report that details the effort, cost, and time spent by resources on
each of the tasks and subtasks.



Thanks very much

Richard

 

[Raymond Chiu (coronabeach @ gmail)]

My understanding is as follows:

MSPS 2003: Fields are edited in Project Pro
============================

Enterprise Outline Codes
1) publish to OLAP cube as dimensions
2) Code mask required
3) Hierarchical

Enterprise Custom Fields
1) good for graphical indicators
2) not hierarchical
3) not OLAP cube dimensions

Any organization that uses MSPS 2003 should have a copy of (at least):

1) Administering an Enterprise PMO (Gary Chefetz)
2) Project Server 2003 Unleashed (Sams Publishing)

The latter has a chapter (chapter 9) to devoted to Enterprise Global codes.
The former provides a good explantion in chapter 3.

In the new 2007 version there are only EOCs.

Raymond Chiu

 

[Marc Soester]

Hi richard,

raymond is absolutatly right. Outline codes will be dispalyed as dimensions
custom fields ( which are not hierachical by the way ) cannot. They can only
be see on the Project Center. That does not mean that you cant report against
it. You can of course export the Project Center view into Excel and create
your report this way.
I hope that this shaded light on Outline codes and custom fields ( PS: 2007
does only have custom fields where you can set hierachies and they all will
be displayed on the OLAP cube)

 

[richardsantink]

Thanks everyone for the replies.. it's exactly what I was looking for. I do
have the 'Unleashed' book, and will re-review Chapter 9..

regards,

Richard