Resources & Cost
Role Codes Tag Roles, Not Resources
Role codes tag roles; not resource codes; not assignment codes
What a planner means
Role codes classify roles. Oracle: grouping roles by code lets you see assignments to a particular skill and activities performed by a group. The help page says they “categorize assignments”; the stored assignment is still role → code, not TASKRSRC → code.
They sit on the role, not on a resource and not on an activity. They are not the role itself (ROLES), not resource codes, not assignment codes, and not OBS.
API: for each role code type, a role may have zero or one value. The assignment object ID is the pair (role, role code type).
Creating a code: unique name, optional Secure, maximum length for value names. Values are hierarchical (parent_role_catg_id).
Same shape as resource codes. Different tables. No scope column. No weight columns on the project XER map.
XER
ROLECATTYPE (Role Codes):
| Column | Oracle label |
|---|---|
role_catg_type_id | Unique ID |
role_catg_type | Role Code |
role_catg_short_len | Max Code Length |
seq_num | Sort Order |
super_flag | Secure Code |
ROLECATVAL (Role Code Values):
| Column | Oracle label |
|---|---|
role_catg_id | Unique ID |
role_catg_short_name | Role Code Name |
role_catg_name | Code Description |
role_catg_type_id | Role Code ID |
parent_role_catg_id | Parent Code |
seq_num | Sort Order |
ROLERCAT (Role Code Assignments):
| Column | Oracle label |
|---|---|
role_id | Role ID |
role_catg_type_id | Role Code ID |
role_catg_id | Code Value |
No TASK or TASKRSRC role-code assignment table.
Microsoft Project
MSP has no role object and no role-code dictionary. Generic resources are not roles. Do not map ROLERCAT to a resource outline code.
Don't
- Treat role codes as resource codes, assignment codes, or the role itself.
- Assign two values of the same role code type to one role.
- Put role codes on TASK or TASKRSRC.
- Map ROLECATTYPE to RCATTYPE or ACTVTYPE.