Resource and Role Teams Are View Groups, Not Resources

What a planner means

A resource team is a named collection of resources. Oracle: it groups personnel into smaller, more meaningful sets so you can staff, track allocation, and look at progress by team. On Resources Planning, Assignments, and Analysis you can organize by resource team and see team totals or each member’s units. The Resource Team Summary portlet lists members, each resource’s primary role, and how many active projects they have.

A role team is a named collection of roles that are often needed on the same project or the same activities. Organize role pages by role team to see total team units or each role’s units.

Two scopes in the UI:

• Global — available to all users. Creating or editing needs the security privilege.
• User — only the logged-in user. Anyone who can view resource data can make a user role team; you can make user resource teams for personal use.

A resource can sit on more than one resource team. A role can sit on more than one role team.

Create them under Resources → Administration → Resource Teams or Role Teams. Add under the Global group or the User group, then assign members.

This is not a resource, not a role, not OBS, not a resource/role/assignment code, and not a TASKRSRC assignment. Grouping a layout by team does not staff an activity.

XER

Oracle’s project XER data map has no resource-team or role-team table. Do not invent RSRCTEAM / ROLETEAM (or any other name) on a project XER parse.

Teams are enterprise / administration data. EPPM export is Download on the Resource Teams or Role Teams tab (expand Global or User). That is a spreadsheet of the current view, not an XER table.

API fields (not XER column names). Do not write these as %T columns.

ResourceTeam (REST): Name, Description, ObjectId, UserObjectId (associated user), UserName, MemberResource[] (Id, Name, ObjectId).

RoleTeam (Integration API): Name, Description, ObjectId, UserObjectId (“a specific user who has access to the selected role team”), UserName, plus role members (getRoleObjectIds / addRole). Removing a member does not delete the role.

Do not invent that a blank UserObjectId means Global. The UI has Global vs User groups; the APIs expose UserObjectId. How a global team is stored is not on the project XER map.

Microsoft Project

Desktop Project has no resource-team or role-team dictionary. Do not map a P6 team to Resource Group, to a Generic resource, or to an MSP outline code.

Don't

• Treat a team as a resource, a role, OBS, or a code type.
• Invent a team table in a project XER parse.
• Assume a resource or role belongs to at most one team.
• Treat grouping by team as an activity assignment.
• Treat a user team as enterprise-wide.