Workday-Pro-HCM-Reporting Exam Questions

To locate the correct fields and data sources for a custom report, Workday provides the Business Object Details report. This report displays all available fields, relationships, and related business objects that can be included in reporting. It ensures report writers can confirm which fields (e.g., Learning Content, Ratings, Popularity) are accessible for use.

From the Workday Reporting documentation:

''The report data source provides the view into the primary business object. This object gives you access to class report fields as well as links to related business objects.''

''The Business Object Details report is used to view which fields are available for reporting.''

Therefore, the correct answer is B. Run the Business Object Details report.

The Arithmetic Calculation function is designed for mathematical operations such as addition, subtraction, multiplication, and division. In this scenario, the bonus equals 10% of monthly sales, so you need to multiply the sales field by 0.10.

The Workday documentation highlights: ''Arithmetic Calculation -- Creates a numeric field using mathematical operations performed on existing fields.'' . This makes it the ideal choice for payroll- and incentive-related calculations.

Other options are less relevant: Evaluate Expression is for logical or Boolean conditions, Lookup Related Value is for retrieving fields from related objects (not calculations), and Sum Related Instances aggregates multiple rows of data but does not directly calculate percentages.

Thus, the arithmetic calculation provides a straightforward and efficient way to compute bonuses dynamically in the report.

Matrix reports in Workday allow grouping and summarization of data, but to drill down through hierarchical structures such as supervisory organizations, you must configure hierarchy-aware calculated fields. The Lookup Hierarchy Rollup function enables drillable hierarchies, showing performance metrics at each level of the organizational tree.

The Workday binder notes: ''Matrix reports allow you to group data, summarize the metrics for each grouping, and drill into the summarizations for further analysis.'' . This means you can expand results from the top supervisory org down to teams and individual workers.

Using a simple Lookup Related Value would only pull in one field from a related object, not enable hierarchical drill-down. Similarly, changing sort order or adding overrides does not create drillable hierarchies. Only Lookup Hierarchy Rollup enables this behavior.

When designing trending reports, the Group by Time Period field determines how the trended records are aggregated and displayed. By default, reports may show quarterly or annual rollups, but this can be easily adjusted to monthly without needing to reconfigure or regenerate trending data.

From the Workday documentation: ''In trending reports, the Group by Time Period setting allows users to choose the granularity of the results, such as monthly, quarterly, or annually. This setting controls the display of data in charts and tables.''

Other options are less appropriate: editing the Column Grouping grid changes report layout but not trending intervals, using a prompt does not change aggregation, and running the Maintain Trended Workers task changes system-wide trending setup, not individual report display.

Thus, the correct approach is B. Edit the Group by Time Period field in the report definition.

Performance issues often occur when trending reports pull fields from related business objects instead of directly from the Trended Workers data source. This requires Workday to join across objects at runtime, slowing down report execution. To improve performance, you should add the required field to the Trended Workers data source, ensuring the data is pre-joined and optimized for trending.

From the Workday binder: ''To improve performance, add commonly reported fields directly to the Trended Workers object. Using related business object fields requires additional joins and increases report runtime.''

Creating calculated fields adds complexity rather than improving speed. Purging or re-creating trending data maintains system hygiene but does not address field-level performance.

Thus, the correct solution is A. Add the field to the Trended Workers data source.