15.2 Matrix Reports

15.2 Matrix Reports

Quick Summary: A Matrix report summarizes Workday data in a rows × columns grid with aggregated measures in the cells. You choose row groupings, column groupings, and summary fields, then enable drillable behavior so users can open detail data under each cell. Matrix is how Workday does pivot-style analytics inside Report Writer—not a separate product called “Pivot Table.”

Task T66 sits in the Report Writer track. Exam stems often describe a leader who needs counts or sums by two dimensions (org × job family, location × worker type) and ask which report type or which configuration step applies. If you only know Advanced tabular lists, you will mis-answer.

What Matrix Reports Are For

Capability snapshot

Mental model: Advanced report = detailed list (possibly with group/sort subtotals). Matrix report = summarized cross-tab designed for comparison and drill.

                    Column grouping → Job Family
                   ┌──────────┬──────────┬──────────┐
 Row grouping      │  Eng     │  Sales   │  Ops     │
   ↓               ├──────────┼──────────┼──────────┤
 Region West       │   42     │   18     │   25     │  ← cell = measure
 Region East       │   37     │   22     │   19     │
                   └──────────┴──────────┴──────────┘
                         click cell → detail workers

Matrix vs Other Report Types (Exam Vocabulary)

Workday custom report types include patterns such as Simple, Advanced, Matrix, Composite, Trending, Transposed, and Search. On HCM Core:

Exam trap: “Which is NOT a standard Workday custom report type?” → Pivot Table is the classic wrong label. Matrix is the real type.

Group By on Advanced vs Matrix

Advanced reports can group/sort and subtotal numeric columns. That is still a list with subtotals, not a full cross-tab of two independent dimensions with cell measures. When the requirement is “Job Family across the top, Supervisory Org down the side, headcount in cells,” choose Matrix.

Creating Matrix Grouping by Rows and Columns

Build sequence (exam-friendly)

1. Start from a suitable data source (often worker-, position-, or staffing-related for HCM headcount style reports). Index sources help performance (T69).
2. Choose Matrix as the report type (or convert an Advanced design into Matrix when the product path supports that workflow).
3. Select row grouping field(s) — the vertical categories (e.g., Supervisory Organization, Cost Center, Location).
4. Select column grouping field(s) — the horizontal categories (e.g., Job Family, Worker Type, Gender for diversity cubes where permitted).
5. Define measures / summary fields — what each cell calculates (Count of Workers, Sum of Base Pay, Average Tenure, etc.).
6. Add filters and prompts so one matrix serves many audiences without exploding row cardinality.
7. Configure drillable fields and detail data for interactive exploration.
8. Test with realistic security and prompt values; validate totals against a known Advanced detail report.

Choosing good dimensions

Configuration scenario: Global Retail Co. wants store-level headcount by Job Family. Report writer uses data source All Active Workers (or an indexed headcount-friendly source available in tenant), row grouping = Store Team Supervisory Organization, column grouping = Job Family, measure = Count. A prompt for Region lets regional HR partners run one definition. Managers with constrained security only see their stores’ cells populated.

Drillable Fields and Detail Data

What “drillable” means

A drillable field appears as a hyperlink in report output. Clicking it either:

• Opens the related business object (for example a Worker profile), or
• On Matrix reports, drills into the grouping / cell to show the underlying detail rows that compose the summary.

Drillability is a column/output attribute, not a calculated field function type. Do not answer “Lookup Related Value” when the stem asks what a drillable field is.

Allow Drill Down and detail configuration

Matrix reports support Allow Drill Down (wording may appear as enable drill-down on the matrix definition). When enabled, users move from a cell total into the detail data that produced that number.

Exam scenario: “User needs to click a column total and see the workers behind it.” → Enable drill-down and configure detail fields. Chart enablement alone is not enough; sharing alone is not enough; calculated fields alone are not enough.

Drill vs chart toggle

Matrix reports may also offer view as bar/pie/line chart options so users toggle between table and chart. That controls visualization mode, not whether detail drill exists. You can have charts without rich detail design—or detail drill with tabular matrix only.

Measures, Summaries, and Design Hygiene

Common HCM measures

Hygiene checklist

1. Filter before you matrix — exclude terminated workers if the story is active headcount.
2. Prompt for org scope — avoid enterprise-wide matrices for every manager.
3. Match measure to grain — counting workers on a position-grain source without care double-counts.
4. Document the as-of logic — effective-dated HCM data needs clear date prompts.
5. Plan for Discovery Board — if leaders want visuals, design matrix measures that chart cleanly (T67).

Realistic Multi-Part Scenario

Requirement: CHRO wants a quarterly diversity-style cube of active headcount by Region (rows) and Job Family Group (columns), with drill to worker detail including Supervisory Org and Manager.

Design moves:

1. Matrix report type on an appropriate worker data source.
2. Row grouping = Region; column grouping = Job Family Group.
3. Measure = Count of Workers; filter Employment Status = Active (or equivalent).
4. Prompt = Company or as-of date as required by tenant practice.
5. Allow Drill Down; detail fields = Worker, Supervisory Organization, Manager, Job Profile.
6. Share with CHRO role-based group; confirm domain access to worker fields.
7. Optionally schedule quarterly delivery (T65) with Calculate at Runtime for as-of date.

Failure modes exam writers love: Using Advanced with one Group By and calling it matrix; forgetting drill detail fields; expecting sharing to reveal compensation measures the runner cannot access; choosing “Pivot Table” as the type name.

Common Confusions Table

Study Links

• T57–T60: Data sources, fields from related BOs—matrix dimensions still come from BOs and relationships.
• T62–T63: Filters and prompts keep matrices usable.
• T65: Schedule matrix packs for leadership.
• T67: Discovery Boards consume matrix-oriented analytics.
• T68–T69: Calculated fields as dimensions/measures can be powerful and expensive—use deliberately.

If a stem says rows and columns, cell totals, or drill to detail, lock onto Matrix immediately, then answer the configuration sub-question (grouping vs drill vs chart).