Study guide

6.4 Foundation Object Associations and Field Criteria

SAP Certified - SAP SuccessFactors Employee Central Core and Position Management C_THR81

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: C_THR81 Exam and SAP SuccessFactors Platform Foundations

1.1 C_THR81 Exam Format, Logistics, and Preparation Plan 1.2 SAP SuccessFactors Suite, Platform Capabilities, and Employee Central Core 1.3 Instances, Provisioning, and Company Settings 1.4 Administrator Types, Super Admin Access, and Admin Center Navigation 1.5 Release Management, Upgrade Center, Release Center, and Consultant Resources

2 Chapter 2: Security, Proxy, and System Administration

2.1 Role-Based Permissions: Groups, Roles, and Target Populations 2.2 RBP Troubleshooting, Reports, and Governance Best Practices 2.3 Proxy Management, Company System and Logo Settings, and Platform Feature Settings 2.4 Admin Alerts, Check Tool, and System Access Settings 2.5 Scheduled Job Manager, Provisioning Job Scheduler, and Execution Manager

3 Chapter 3: User Experience Configuration

3.1 People Search, Action Search, Custom Navigation, Org Chart, and Built-In Support 3.2 Home Page Configuration and Mobile Settings 3.3 E-mail Notifications, Themes, and Company Logo 3.4 Text Replacement, Manage Languages, and Translations

4 Chapter 4: People Profile, Picklists, User Data, and the Metadata Framework

4.1 Latest People Profile, Categories, Cards, and Custom MDF Cards 4.2 Manage Business Configuration and Succession Data Model XML Fundamentals 4.3 Picklist Center, Cascading Picklists, and the Employee Central Master Picklist 4.4 User Data File, Employee Import, and User Management Tools 4.5 Metadata Framework Enablement and Object Definition Settings 4.6 MDF Fields, Associations, Search, and Security

5 Chapter 5: Business Rules

5.1 Rules Engine Fundamentals: Scenarios, Base Objects, MDF Rule Events, and the Execution Log 5.2 Employee Central Rule Events, Rule Scenarios, and Model Base Objects 5.3 Propagation Rules and Hire/Rehire Rules 5.4 Cross-Entity Rules, Rule Context, and Rule Design Practices

6 Chapter 6: Foundation Objects and Corporate Data Models

6.1 The Four Employee Central Data Models, DTDs, and Upload Sequence 6.2 Foundation Objects: Organization, Pay, and Job Structures 6.3 Configuring Legacy and MDF Foundation Object Definitions 6.4 Foundation Object Associations and Field Criteria 6.5 Country-Specific Fields for Foundation Objects

7 Chapter 7: Employee Data Structures and Permissions

7.1 Person and Employment Objects, Effective Dating, and Employee Identifiers 7.2 Configuring the Succession Data Model with BCUI and XML 7.3 Country-Specific Succession Data Model: National ID, Addresses, Global Information, and Job Data 7.4 HRIS Synchronization and Sync Mappings 7.5 Employee Central Permissions for Administrators

8 Chapter 8: Employee Transactions and Data Maintenance

8.1 Hire, Rehire, Termination, and No-Show Transactions 8.2 Importing New Employees and Updating Employee Data by Import 8.3 Mass Data Management for Job Information, Job Relationships, and Positions 8.4 Employee and Manager Self-Service Permissions

9 Chapter 9: Workflows, Alerts, and Event Reasons

9.1 Workflow Configuration, Participants, Dynamic Roles, and Dynamic Groups 9.2 Managing Workflows: Approvals, Delegation, Reminders, Escalation, and Auto-Approval 9.3 Employee Central Alerts and Notifications 9.4 Events, Event Reasons, and Event Reason Derivation 9.5 Workflow Derivation Rules and How They Work with Event Reason Derivation

10 Chapter 10: Optional Employee Central Configurations

10.1 Employee Central Quick Actions and Internal Job History 10.2 Custom Hire Templates, the Diagnostic Tool, and Joule in Employee Central

11 Chapter 11: Position Management Setup

11.1 Position Management Overview: Positions, Jobs, and the Leading Hierarchy 11.2 Enabling Position Management and Setting Role-Based Permissions 11.3 Navigating and Configuring the Position Organization Chart 11.4 Configuring the Position Object 11.5 Position Management Settings 11.6 Creating, Maintaining, Importing, and Mass-Changing Positions

12 Chapter 12: Position Management in the Employee Lifecycle

12.1 Position Fields in Job Information and Hiring Employees to Positions 12.2 Maintaining Incumbents: Transfers, Reclassification, Global Assignments, and Right to Return 12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions 12.4 Terminations with Position Management and Position Workflows

13 Chapter 13: Position Management Rules, Integrations, and Company Structure

13.1 Position Management Rule Scenarios and Rules for Position Data Entry 13.2 Synchronization Rules and Mass Change Runs for Positions 13.3 Position Code Generation, Position Workflows, Right to Return Setup, and Rule Functions 13.4 Integrating Position Management with Recruiting and Succession 13.5 Building the Company Structure Overview

6.4 Foundation Object Associations and Field Criteria

Key Takeaways Explain This Topic AI

A Valid When association is created on the lower-level object being filtered and points to the higher-level object.

SAP recommends one-to-many multiplicity for new custom associations.

In jobInfo field criteria, the Destination Field Value is the HRIS field of the filtering higher-level object, such as business-unit.

For MDF-to-MDF filtering, the Source Field Name is the association name plus the parent's internal code field, such as cust_toBusinessUnit.internalId.

To filter MDF records by a legacy foundation object, use the pre-delivered wrapper object with a Composite association.

Last updated: September 2026

6.4 Foundation Object Associations and Field Criteria

Quick Answer: An association defines a relationship between foundation objects, so that choosing a higher-level record limits the lower-level choices. For example, choosing a business unit shows only its divisions. Filtering in employee data takes two configurations : the association on the object being filtered, and field criteria on the filtered field in Job Information (and on the Position object if Position Management is used).

Why Associations Matter

THR81's example: ACE Corp has 30 locations, 13 of them in the United States. Associating those 13 locations with the US legal entity means that when Ace USA is chosen, only 13 locations are offered. Associations make data entry easier and keep employee data consistent with the organization hierarchy. Some associations are pre-delivered , for example Location with Legal Entity, and Pay Range with Pay Grade.

Multiplicity

Multiplicity Behavior

One to One Each record links to one record, for example a location belonging to only one location group. It displays as a picklist on the record. Several standard one-to-one associations exist (Location–Geozone, Pay Range–Geozone, Pay Range–Pay Grade).

One to Many A record can link to several records. It displays as a separate section at the bottom of the FO record, where several records can be connected. For example, a job classification links to several country-specific job classifications.

SAP recommends that any new custom association be created as one-to-many. One-to-many does not force you to select several records; it keeps the option open.

Association Properties

  • Property Meaning
  • Name Unique; customer-defined associations are prefixed cust_ automatically
  • Multiplicity One to One or One to Many

Destination Object For Composite : the child object. For Valid When : the higher-level object in the hierarchy.

  • Type Composite or Valid When (Join By Column is not used in this training)
  • Label Display label for the related records
  • Category 1: MDF to MDF (Business Unit filters Division)

Step 1 – Create the relationship on the object being filtered (the lower level). In Configure Object Definitions , open Division and choose Take Action > Make Correction . In Associations > Details , set:

  • Name: for example toBusinessUnit (saved as cust_toBusinessUnit )
  • Multiplicity: One to Many
  • Destination Object: Business Unit (the higher-level, filtering object)
  • Type: Valid When

Then link the records in Manage Data. Each division record is associated with its business unit(s).

Step 2 – Apply the filter in the employee file. In Manage Business Configuration > HRIS Elements > jobInfo , open the division field (the field being filtered) and go to Details > Field Criteria :

Destination Field Value = business-unit. This is the HRIS field identifier of the higher-level object doing the filtering .

Source Field Name = cust_toBusinessUnit.internalId. This is the association name , a period, and the field name of the parent's internal code. Look it up in Configure Object Definitions as the field whose Database Field is InternalCode .

Step 3 – Apply the filter to positions (only if Position Management is enabled). In Configure Object Definitions > Position , open the division field's Details and fill in its Field Criteria the same way, so position records respect the hierarchy too.

Common trap: people often swap these two values. In SAP's configuration, the Destination Field Value is the filtering HRIS field (business-unit), and the Source Field Name is the association path on the filtered object (cust_toBusinessUnit.internalId).

Category 2: XML to MDF (Legal Entity filters Location)

Here the object being filtered, Location , is XML-based, so the association is built in the Corporate Data Model :

Open the latest corporate-datamodel.xml and go to the location element.

In its hris-associations section, add an association line with multiplicity ONE_TO_MANY and destination-entity = LegalEntity , the code of the MDF object from Configure Object Definitions.

Validate, save as a new version, and upload.

Then, in BCUI > jobInfo > location > Field Criteria :

Destination Field Value = company , the HRIS field of the filtering legal entity.

Source Field Name = LegalEntity , the code of the filtering object in Configure Object Definitions.

Finally, add the same field criteria to the Position object's location field if Position Management is used.

Category 3: XML to XML (Location Group filters Location)

Several XML-to-XML associations are pre-delivered. For a custom one, SAP's example adds this to the location element: <hris-associations>

  • <association id="id" multiplicity="ONE_TO_MANY" destination-entity="locationGroup" required="false"/>
  • </hris-associations>

Location Group is not a standard Job Information field, so a custom field ( custom-string3 ) displays the location group in jobInfo. The location field's criteria then point to it: <hris-field max-length="128" id="location" visibility="both">

  • <label>Location</label>
  • <field-criteria destinationFieldValue="custom-string3" sourceFieldName="locationGroup"/>
  • </hris-field>
  • Category 4: MDF to XML (Location filters a custom Garage object)

You cannot associate an MDF object directly with a legacy FO . Use the pre-delivered wrapper object that represents it, such as Location Wrapper . When a wrapper is used, the association type must be Composite , not Valid When.

THR81's Garage object (Basic effective dating, externalCode Auto Number, externalName Garage Name , carCapacity) gets the association toLocation : One to Many, destination Location Wrapper , type Composite . In jobInfo, a custom field ( custom-string4 , Type of Reference Object = Foundation Object, Reference Object = the garage object's code) shows the garage. Its field criteria use Destination Field Value = location and Source Field Name = cust_toLocation.externalCode . The external code connects the wrapper to the legacy object.

Validating the Setup

The Check Tool includes a validation for existing or missing field criteria.

Test with Add New Employee or Change Job and Compensation Info : choose the parent value and confirm that only associated records appear.

Remember effective dates. An association cannot link records if the child record starts before the parent record exists.