EPS

What a planner means

The enterprise project structure (EPS) is the hierarchy of all projects in the database. Oracle: nodes at the root might be divisions, phases, or sites; projects always represent the lowest level. Every project must sit in an EPS node.

You summarize and aggregate up the EPS, and you can push top-down budget down from an EPS node into its projects. That is portfolio/program grouping. It is not the WBS inside one project, and it is not the OBS.

Security on the EPS is through OBS. You must assign a Responsible Manager (OBS element) to each EPS node. Oracle: users associated with that manager have access to the selected EPS node and all nodes/projects within that branch. Users assigned to an OBS that is assigned to the root EPS have access to all nodes beneath the root.

That branch inheritance is EPS-side. It is not the same as OBS-to-OBS: user privileges on an OBS element are not passed down to child OBS elements (see OBS).

XER

The project XER data map lists PROJECT and PROJWBS. It does not list an EPS table. Do not invent one.

PROJWBS.proj_node_flag is Project Node — the WBS root of that project. It is not an EPS node.

PROJECT.project_flag is labeled Project Flag. Oracle does not say in the map what values mean. Do not treat it as “this row is an EPS node.”

A typical single-project XER is a project export. Whether the parent EPS node travels with that file is unverified here. Do not assume the Viewer can rebuild the enterprise tree from one XER.

Related: activity codes can be Global, EPS, or Project (AS_Global / AS_EPS / AS_Project on ACTVTYPE). EPS-level codes follow the EPS node; they are not the EPS itself. See Activity Codes Are a Pick-List, Not a UDF.

Microsoft Project

Desktop Project has no EPS. A master project + subprojects is a file link (Insert Subproject), not an enterprise tree with OBS security. Project Online/Server portfolios and SharePoint sites are a different product surface, not MSPDI.

Don't

• Treat EPS as WBS, or proj_node_flag as an EPS node.
• Treat EPS as OBS. OBS is who; EPS is where the project sits.
• Invent an EPS XER table or project_flag tokens you have not seen.
• Map EPS to MSP outline/summary tasks or to a master-file insert and call them the same object.
• Confuse “access to this EPS branch” with “access inherited down the OBS.”