Rights — Roles / Menus
The Rights — Roles / Menus screen joins the role-level rights matrix to the menu tree, with the licence component carried on each row. One line per (Application, Role, Object) triplet, restricted to rules where SER_USER_ID = '*ROLE' and SER_RUN = 'Y'. The menu breadcrumb (root + up to 9 levels) tells how a holder of the role would reach the object from the menu.
It is the cleanest view to discuss with a role owner: "here is everything your role grants, organised the way users actually browse it".
At a glance
Goal of the view
For each role on a connected application:
- The full inventory of what the role grants. Object, form, version + the menu path. Hand it to the role owner during the access review.
- Per-component breakdown. The Component column lets you measure how much of which licence the role consumes — useful before approving a new role.
- Hidden grants. Rows with no menu path point to rights with no navigation — the easiest target for cleanup since users cannot reach them through the standard UI.
Columns
| Column | Source | What it tells you |
|---|---|---|
| Application ID | SER_APPS_ID — application identifier. Filterable. | Which application the right applies to. |
| Role ID | SER_ROLE_ID — role granting the right. Filterable, scoped to the application. | The role the rule belongs to. |
| Component | CPT_ID — licence component. Filterable. | The licence bucket the right falls under. |
| Object | SER_OBJECT — technical object. Filterable, scoped to the application. | What the role unlocks. |
| Form | SERL_FORM — form code within the object. | Specific form. |
| Version | SER_VERSION — processing version. | Configuration variant. |
| Run / Add / Change / Delete | SER_RUN, SER_ADD, SER_CHG, SER_DEL — Y / N. | Action flags. |
| Root / Menu ID / Level 1 — 9 | MENU_ROOT, MENU_ID, MENU_LEVEL1 … MENU_LEVEL9 — text. | Menu breadcrumb. Empty when no menu path reaches the right. |
| Sequence | MENU_SEQ_UKID — internal stable sequence. | Used to keep menu rows in a deterministic order. |
Tips & best practices
- Filter by Role ID + sort by Level 1 to produce the per-role deliverable used in the access review.
- Filter by Component to extract every right a role brings under a specific licence — the data you need before renegotiating component volumes.
- Rows with empty Root are rights the role grants but no menu navigates to. They are typically the leftover of a removed menu entry that nobody trimmed in the security rights.
- Cross-reference with Roles not used — a role with very few menu paths is a candidate for retirement.