2.2 Business Objects & Finding Data

What Is a Business Object?

In Workday, a business object (BO) is a named type of data the system stores and secures — roughly analogous to an entity or record type. Each instance of a business object is one concrete record: one Worker, one Position, one Supervisory Organization, one Job Profile, one Location.

HCM Fundamentals expects you to recognize the purpose and use of business objects. You are not asked to memorize every object in the tenant. You are expected to know that almost everything you click — a person, an org, a job, a location — is a business object instance with fields and relationships, and that those relationships are how Workday finds and protects data.

Core HCM Business Objects to Know

Many other objects exist (Applicant, Requisition, Security Group, Business Process Definition). For this exam chapter, master the HCM core set above and the idea that every secured data element sits on some business object.

Fields Versus Related Business Objects

Each business object instance has:

1. Fields — values stored on that instance (for example, Worker’s legal name, hire date, employee ID; Position’s earliest hire date; Job Profile’s management level).
2. Related business objects — links to other instances (Worker’s current Position; Position’s Job Profile; Worker’s Supervisory Organization; Location on a position or worker).

Exam distinction. A field is a data element on an object. A related business object is another instance connected by a relationship. Report Writer and Calculated Fields constantly navigate from a primary BO across related BOs to reach fields that do not live on the starting object.

Why Business Objects Underpin Reports, Calculated Fields, and Security

Report Writer

Every report has a data source rooted in a business object (or a delivered data source built on BOs). When you build or interpret a report, you:

• Start from a primary business object or data source (for example, All Active Workers).
• Add columns that are fields on that object or on related objects reachable through the data model.
• Filter using fields and related-object criteria.

If you cannot answer “Which business object is this report about?” you will misread which fields are available and why a column is blank.

Calculated Fields

Calculated Fields are reusable computations defined against a business object. They read fields and related-object data (lookup related value, date difference, true/false conditions, extract text, and so on) and return a result used in reports, conditions, or other calculated fields. Calculated Fields do not float free of the model — they are always owned by a business object class.

Security Domains

Workday domain security protects groups of secured items (view/modify permissions) associated with functional areas and, critically, with data on business objects. Whether a user can see compensation fields on a Worker, open a Position, or run a report that includes certain columns depends on domain security policies and the security groups that hold permissions. Business process security separately controls who can initiate and act on processes. Both layers assume you understand which object holds the data or starts the process.

Finding Data via Business Object Relationships

Finding data in Workday is less about memorizing screen names and more about walking the graph:

Worker
  → Position (or Job, depending on staffing model and event)
    → Job Profile
    → Location
  → Supervisory Organization
    → Superior org / hierarchy
    → Roles (HR Partner, Manager, …)
  → Compensation (plans, grade, package components)
  → Company / Cost Center assignments

Example path. “What is the management level for Maria’s job?” You open the Worker, navigate to the current Position (or job), open the related Job Profile, and read the management level field. The answer never lived as a free-floating screen value; it lived on Job Profile, reached through relationships.

Example path. “Who is the HR Partner for this team?” Start at the Supervisory Organization, open Roles, find the HR Partner assignment — or start at a Worker and move to their supervisory org, then to roles. Same graph, different entry points.

Practical finding techniques that use the BO model:

• From a Worker profile, use tabs and related views that expose org, job, and compensation relationships.
• From an Organization, open membership, roles, and staffing views.
• From Search, open the object type you need rather than forcing every question through Worker.
• In reporting classwork (Report Writer track on this exam), choose the data source whose primary BO matches the question you are answering.

Entry Moment Versus Effective Date (Viewing Data)

HCM data is often effective-dated: changes apply as of a business Effective Date, not merely when someone typed them. Workday also tracks when the change was entered — the Entry Moment (sometimes discussed with transaction or audit timing concepts).

Why the exam cares. When you view a Worker or run a report “as of” a date, you are usually selecting an effective-dated lens: which version of the data is true for that business day. A correction entered today with an earlier effective date means historical views as of that earlier date can change even though the entry is recent. Confusing the two leads to wrong conclusions such as “the system shows today’s hire date so the person was hired today” when the entry was a late correction of an earlier effective hire.

Intro-level rule of thumb:

• Use Effective Date to answer what was/is true for the business on date D.
• Use Entry Moment (and process history) to answer when did someone record this in Workday.

You will deepen effective dating with staffing events (hire, job change, terminate) and org changes later; for this section, lock the vocabulary and the viewing implication.

Scenario: Using BOs to Answer a Real Question

Scenario. Leadership asks: “As of 1 March, what Job Profile and Location applied to worker W-2201, and which Supervisory Organization did they report into?”

1. Search and open Worker W-2201.
2. Set or use the view as of 1 March (effective-dated view) so you are not looking only at today’s values if a later job change occurred.
3. From the worker’s job/position relationship, open the Position (or job) that was active on that date.
4. Read related Job Profile and Location.
5. Read related Supervisory Organization (and manager role context if needed).

Every step is BO navigation. If a report is built instead, the report’s primary data source still rests on Worker (or a worker-centric source) and columns pull related Job Profile, Location, and Organization fields — same model, different UI.

Common Exam Traps

• Treating screens as unrelated forms instead of instances of business objects with relationships.
• Mixing up a field (value on an object) with a related business object (linked instance).
• Assuming Report Writer can invent columns with no path from the primary BO.
• Believing security is only “can I log in?” rather than domain and BP permissions on objects and processes.
• Confusing Effective Date (business validity) with Entry Moment (when recorded).

Connecting Back to Navigation

Navigation tools are how you reach business object instances. Business object knowledge is how you understand what you are looking at and where the next piece of data lives. Search finds instances; Related Actions act on them; My Tasks completes processes that change them; reports and calculated fields read across their relationships under security. Together, these skills satisfy the HCM Fundamentals outcomes: demonstrate navigation techniques, and recognize the purpose and use of business objects.

Quick Self-Check Before Moving On

Ask yourself for any HCM screen: (1) What business object instance is primary here? (2) Which fields are on this object versus on a related object? (3) What security domain might protect these fields? (4) If I change the as-of date, am I changing Effective Date perspective? If you can answer those four questions, you are ready for organizations, staffing models, and the rest of the Pro HCM Core blueprint.