2.6.

1 Associations

Associations define relationships between foundation objects.

For example, a business unit consists of several departments, so you would create an association of one business
unit to many departments — a ONE-TO-MANY relationship. Whereas a location can only have one geozone
associated with it — this is a ONE—TO—ONE association. The type of association restricts what the user can
display or enter in Employee Central — for a ONE_TO_ONE association from location to geozone, for example, the
user can enter exactly one geozone for a location on the UI.

The standard XML file for the Corporate Data Model already contains some associations. You can add more
ONE_TO_MANY associations, or change the existing associations in the XML file if needed. Each association has a
“driving object” that acts as the basis for the association.

Associations should always be configured to go from the lower-level object (the child object) to the higher-level
object (the parent object). In other words, the association should be placed on the object you expect to be filtered
based on the parent value selected. For example - Location (Child) to Legal Entity (Parent) requires that the
association be placed on the Location object. Following this, in the UI, after selecting the Legal Entity, a filtered list
of Locations will be available, based on the selection made in Legal Entity.

For Foundation Objects, you can only define a ONE_TO_MANY association and not a MANY_TO_ONE association.
In most cases, the one object typically filters the many object. However, it is recommended that associations be
modeled on the many object rather than the one object to achieve the required filtering behavior.

As an example, if we assume the job codes ENG01 and ENG02 are applicable to “Philadelphia" and you would like to
filter job codes by location. Logically, this would be a MANY-TO-ONE relationship from the jobCode to the location.
However, as only ONE-TO-MANY associations are supported, this would need to be configured as a ONE-TO-MANY
association from jobCode to location. Once this association has been defined, the valid locations can be attached
to the job codes in Employee Central when setting up the job codes on the UI.

Check Tool for Associations

You can use the Check Tool to find any inconsistencies in your associations. Any fix would result in the update to
your data in Employee Central. We recommend selecting checks available under the following sections:

• Check Tool System Health Tab Employee Central Core Invalid Effective End Date for FO/GO Area
• Check Tool Employee Central Core Object Relationship Area

For more information about Foundation Objects, refer to the Foundation Objects

Related Information

Working with Associations, Field Criteria and Value Help

Implementing Employee Central Core

30 PUBLIC Configuration Tasks
[Link] Using Associations to Structure Your Business

In this example of a company’s organization structure, you can see a range of different options for configuring and
customizing the associations to accommodate different hierarchies.

In this example, we can see that there is a ONE-TO-MANY association between the following objects:

• Legal Entity and Business Unit

• Business Unit and Division
• Division and Department

We can also see the ONE-TO-ONE associations between the following objects:

• Location Group and Location

• Geo Zone and Location Group

Should the standard Foundation Objects not account for the number of organization units that a company needs to
define their org hierarchy, additional levels can be created through the use of custom MDF Generic Objects. In this
example, we can see the following ONE-TO-MANY associations to custom objects:

• Area to Division
• Section to Department

An additional option available in constructing the Foundation Object associations is to build an association against
the same object. For example, if a larger department is divided into sub-departments, a parent-child association
can be created against the department object. The benefit of constructing this parent-child relationship is that it
does not drive any restrictions when drilling down the hierarchy. This is possible for all objects except Legal Entity,
since this must stay at the top of the hierarchy.

Implementing Employee Central Core

Configuration Tasks PUBLIC 31
[Link] Examples of Foundation Object Associations

This table lists several examples of associations to show the relationships between foundation objects.

 Note

References to Department, Division, Legal Entity and Business Unit in these examples now point to the MDF
foundation objects.

Source Target Multiplicity Description

Location Geozone ONE_TO_ONE A location can only belong to

one geozone. (Location is the
driving object.)

Legal Entity Location ONE_TO_MANY Several companies can have

the same location. (Legal En-
tity is the driving object.)

Business Unit Division ONE_TO_MANY A business unit can be asso-

ciated with several divisions.
(Business Unit is the driving
object.)

Implementing Employee Central Core

32 PUBLIC Configuration Tasks
Source Target Multiplicity Description

Division Department ONE_TO_MANY A division can be associated

with multiple departments.
(Division is the driving object)

Business Unit Job Code ONE_TO_MANY A job code can be used across
several business units. (Busi-
ness Unit is the driving ob-
ject.)

Pay Range Geozone ONE_TO_ONE Companies generally have dif-

ferent pay ranges for each
combination of Legal Entity,
Job Code, and Geozone.

Pay Range Pay Grade ONE_TO_ONE A pay range is generally asso-

ciated with one pay grade.

Pay Range Legal Entity ONE_TO_ONE Companies generally have dif-

ferent pay ranges for each
combination of Legal Entity,
Job Code, and Geozone.

Pay Component Group Pay Component ONE_TO_MANY A pay component group can
contain multiple pay compo-
nents.

Pay Group Legal Entity ONE_TO_ONE A pay group is generally asso-

ciated with one legal entity.

[Link] Configuring Associations

You need to fully understand the relationships between foundation objects in order to define them correctly in the
system.

Associations from Legacy FOs to other Legacy FOs are defined in the Corporate Data Model, whereas associations
from MDF FOs to Legacy FOs or to other MDF FOs (or GOs) are defined in MDF (Configure Object Definitions). For
associations from an MDF FO to a Legacy FO, associations cannot be directly defined. Instead, a wrapper MDF FO is
used. A wrapper is not required for associations to custom FOs as these are considered to be GOs.

For more details of how to configure associations based on the object destination, refer to the Working with
Associations, Field Criteria and Value Help topic.

Implementing Employee Central Core

Configuration Tasks PUBLIC 33
Creating Associations Between Different Entities

You can also add an association to a field that is not part of the same entitiy; for example, to filter the pay
components in Compensation Information based on Job Information criteria. To do this, you have to add a prefix of
the corresponding object as destination field value.

Here, the pay component that is part of the payComponentRecurring is filtered based on the payScaleGroup field
from the Job Information. To achieve this, you add the prefix jobInfo. to the destination field value.

 Note

You can only use IDs of effective-dated HRIS elements as prefixes, for example, jobInfo, compInfo, or
personalInfo as prefixes.

The next few sections describe how you can get associations to work for the following scenarios.

• Legacy Foundation Object filtering another Legacy Foundation Object

• Foundation Object filtering a Generic Object

Implementing Employee Central Core

34 PUBLIC Configuration Tasks
• Generic Object filtering a Foundation Object
• Generic Object filtering another Generic Object

The steps also describe optional configuration that is required only if you have position management enabled and
need associations to work on the position and the employee record.

[Link].1 Filtering Custom Fields in Foundation Objects

Disable the filter for custom fields of type Foundation Object in the system.

Context

Custom fields using the attribute type="foundationObject" take over the association settings of the corresponding
foundation object. For example, if you have a custom field of type="location", and you have associated the location
FO with the legal entity FO, the custom field would only show a restricted list of values (where the legal entity
defines which locations are displayed). However, if you prefer custom fields with type="foundationObject" to show
all the FOs available in the system, you need to check the following setting:

Procedure

1. Go to Admin Center Company Settings Company System and Logo Settings .

2. Under Company System Settings, select the checkbox Disable filter for custom fields of type Foundation Object.
To activate this setting, upload any data model in provisioning.
3. Save your settings.

[Link].2 Configuring a Generic Object to Filter Another

Generic Object Using Associations

It is possible to use one generic object as a filter for another.

Context

To understand the steps involved, consider the following example of the Generic Object cust_MarketCategory
being filtered by the Generic Object cust_FunctionalArea.

External Name Of Generic Object doing filtering cust_FunctionalArea

Implementing Employee Central Core

Configuration Tasks PUBLIC 35
Technical Name of field on Position referencing Generic Object cust_FunctionalArea_field
doing filtering

Technical Name of field on Position referencing Generic Object cust_jobMarketCategory_field

being filtered

External Name Of Generic Object to be filtered cust_jobMarketCategory

[Link].2.1 Step 1: Configuring the Association to the Generic

Object to be Filtered

Configure the association on the Generic Object to be filtered.

Context

This allows you to attach the parent Generic Object doing the filtering (cust_FunctionalArea) to the child Generic
Object being filtered (cust_jobMarketCategory).

Procedure

1. Create the Generic Objects that will do the filtering and be filtered.

2. Go to Admin Center Configure Object Definitions .

3. From the Search dropdown, select Object Definition and then select Job Market Category (the Generic Object to
be filtered) from the dropdown next to it.

The Configure Object Definitions page is displayed.

4. From the Take Action dropdown, select Make Correction.
5. Scroll to the Associations section at the bottom.
6. Select Details. We will now set the association for the child object, meaning the object to be filtered.
7. In the Name field, specify a name for the association.
8. In the Multiplicity field, select the type of association, either One to One or One to Many.
9. In the Destination Object field, select the Generic Object that will filter the values for this Generic Object on the
UI.

Results

A sample completed entry is shown below.

Implementing Employee Central Core

36 PUBLIC Configuration Tasks
[Link].2.2 Step 2: Attaching the Relevant Parent Generic
Object Values to the Child Generic Object

Attach the relevant Parent Generic Object values to the Foundation Object.

Context

This sets up which parent Generic Object values filter the child Generic object values.

Procedure

1. Go to Admin Center Manage Data .

2. From the Create New dropdown, select Job Market Category.
3. In the externalCode field, specify the name of the child Generic Object value to be filtered.
4. In the externalName field, specify the external name for this object.
5. In the effectiveStartDate field, specify the start date.
6. From the functionalArea dropdown, select the parent Generic Object value doing the filtering. In this case, HR.
7. Save your changes.

Implementing Employee Central Core

Configuration Tasks PUBLIC 37
Results

[Link].2.3 Step 3: Defining Field Criteria for the Generic Object

Field Being Filtered

In the Business Configuration UI (BCUI), define field criteria for the Generic Object field being filtered.

Context

This tells the system for this field what Generic Object is doing the filtering and the field that references it on Job
Information.

Procedure

1. Go to Admin Center Manage Business Configuration .

2. Go to the child value field (the field to be filtered).
3. Select Details to add the criteria.
4. For Destination Field Value, select the identifier of the parent field in Job Information. For the Source Field
Name, add the field from Step 1: Configuring the Association to the Generic Object to be Filtered.
5. Save your changes.

Implementing Employee Central Core

38 PUBLIC Configuration Tasks
Results

Implementing Employee Central Core

Configuration Tasks PUBLIC 39
  Note

The field name of the internal code on the parent Generic Object can be derived from the <internalCode>
database field name found in the Configure Object Definition page.

 Note

The field-criteria attribute is not supported for the country/region-specific data models.

[Link].2.4 Step 4: Defining the Field Criteria for the Child

Generic Object Being Filtered

Define field criteria for the child Generic Object being filtered.

Context

This step is to be done only when Position Management is enabled. This tells the system for this field what
Generic Object is doing the filtering and the field that references it on the Position object.

 Note

Refer to the previous step for information on how to derive the internal code.

Procedure

1. Go to Admin Center Configure Object Definitions .

2. From the Search drop-down list, select Object Definition and then select Position from the drop-down list next
to it.

The Configure Object Definitions page is displayed.

3. From the Take Action drop-down list, select Make Correction.
4. In the Fields section, scroll to the Generic Object field to be filtered. In this case, cust_jobMarketCategory_field.
5. Select the Details link to view the configuration.

Implementing Employee Central Core

40 PUBLIC Configuration Tasks
[Link].3 Configuring a Generic Object to Filter Another
Generic Object Using Field Criteria Only

It is possible to use one generic object as a filter for another using field criteria.

Context

It is possible to filter one-to-one associations.

[Link].3.1 Step 1: Configuring the Field to the Generic Object to

be Filtered

Configure the association on the Generic Object to be filtered.

Context

This allows you to attach the parent Generic Object doing the filtering to the child Generic Object being filtered.

Procedure

1. Go to Admin Center Configure Object Definitions .

Implementing Employee Central Core

Configuration Tasks PUBLIC 41
2. From the Search dropdown, select Object Definition and then select the Generic Object to be filtered from the
dropdown next to it.

The Configure Object Definitions page is displayed.

3. From the Take Action dropdown, select Make Correction.
4. Scroll to the end of the Fields list and add a new field.

For the new field, ensure that Data Type Generic Object is set.

5. Select Details. Update the Valid Value Source to be the technical name of the parent field.

6. Save your changes.

[Link].3.2 Step 2: Attaching the Relevant Parent Generic

Object Values to the Foundation Object

Attach the relevant Parent Generic Object values to the Foundation Object.

Context

This sets up which parent Generic Object values filter the child Generic object values.

Procedure

1. Go to Admin Center Manage Data .

Implementing Employee Central Core

42 PUBLIC Configuration Tasks
2. From the Search dropdown, select the child object type and search for the object to be filtered.
3. From the Take Action dropdown, select Make Correction.
4. For the field to be filtered, add the parent value.

5. Save your changes.

[Link].3.3 Step 3: Adding Field Criteria to Child Object Using

the Business Configuration UI

In the Business Configuraiton UI (BCUI), add the field criteria for the field to be filtered.

Context

This tells the system for this field what Generic Object is doing the filtering and the field that references it on Job
Information.

Procedure

1. Go to Admin Center Manage Business Configuration .

2. Go to the child value field (the field to be filtered).
3. Select Details to add the criteria.
4. For Destination Field Value, select the identifier of the parent field in Job Information. For the Source Field
Name, add the field from Step 1: Configuring the Field to the Generic Object to be Filtered [page 41] .

Implementing Employee Central Core

Configuration Tasks PUBLIC 43
 Implementing Employee Central Core
44 PUBLIC Configuration Tasks
5. Save your changes.

[Link].4 Configuring a Generic Object to Filter a Foundation

Object

It is possible to use one generic object as a filter for a foundation object.

Context

To understand the steps involved, consider the following example where Legal Entity (Generic Object) is required to
filter Location (Foundation Object) on Job Information and Position.

External Name of Generic Object doing filtering LegalEntity

Technical name of field on Position referencing the Generic company

Object doing filtering

Technical name of Foundation Object field on Position being location

filtered

Technical name of Foundation Object field on Job Information location

being filtered

Field name on Job Information referencing Generic Object company

doing the filtering

Foundation Object to be filtered location

[Link].4.1 Step 1: Adding an Association to the Generic Object

in the Foundation Object Element to Be Filtered

In the Corporate Data Model, add an association to the Generic Object in the Foundation object element that is to
be the subject of filtering.

Context

In this example, the association is added to the location.

Implementing Employee Central Core

Configuration Tasks PUBLIC 45
Procedure

1. Create the Generic Objects that will do the filtering and be filtered.

2. Go to Admin Center Configure Object Definitions .

3. From the Search dropdown, select Object Definition and then select the Generic Object to be filtered from the
dropdown next to it.

The Configure Object Definitions page is displayed.

4. From the Take Action dropdown, select Make Correction.
5. Scroll to the Associations section at the bottom.
6. Select Details. We will now set the association for the child object, meaning the object to be filtered.
7. In the Name field, specify a name for the association.
8. In the Multiplicity field, select the type of association, either One to One or One to Many.
9. In the Destination Object field, select the Generic Object that will filter the values for this Generic Object on the
UI.

[Link].4.2 Step 2: Attaching the Parent Generic Object Values

to the Foundation Object

Attach the relevant parent Generic Object values to the Foundation Object.

Context

This sets up Generic Object values that will filter the Foundation Object values.

Procedure

1. Go to Admin Center Manage Organization, Pay and Job Structures .

2. From the Search drop-down list, select Location (the object whose values will be filtered) and then select the
relevant location from the drop-down next to it. For this example, let’s select London. The Configure Object
Definitions page is displayed.

Implementing Employee Central Core

46 PUBLIC Configuration Tasks
[Link].4.3 Step 3: Defining Field Criteria for the Foundation
Object Field being Filtered (For Job Information)
Using the Business Configuration UI

Define field criteria for the foundation object field being filtered.

Context

This specifies which Generic Object is doing the filtering and the field that references it on Job Information.

Procedure

1. Go to Admin Center Manage Business Configuration .

2. Go to the child value field (the field to be filtered).
3. Select Details to add the criteria.
4. For Destination Field Value, select the identifier of the parent field in Job Information. For the Source Field
Name, add the field from Step 1: Adding an Association to the Generic Object in the Foundation Object Element
to Be Filtered [page 45] .

Implementing Employee Central Core

Configuration Tasks PUBLIC 47
 Implementing Employee Central Core
48 PUBLIC Configuration Tasks
  Note

The field-criteria attribute is currently not supported for the country/region-specific data models.

5. Save your changes.

[Link].4.4 Step 4: Defining Field Criteria for the Foundation

Object Field to be Filtered (For Position)

Define field criteria on the Foundation Object that is to be the subject of the filtering field on the Position Object.

Context

This step is to be done when the object doing the filtering is an MDF Object. This tells the system for this field which
Generic Object is doing the filtering and the field that references it on Position.

Procedure

1. Go to Admin Center Configure Object Definitions .

2. From the Search drop-down list, select Object Definition and then select Position from the drop-down next to it.

The Configure Object Definitions page is displayed.

3. From the Take Action drop-down list, select Make Correction.
4. In the Fields section, scroll to the Generic Object field to be filtered. In this case, location.
5. Select the Details link to view the configuration.
6. Scroll to the Field Criteria section.
7. In the Source Field Name field, enter the external name of the Generic Object doing the filtering.
8. In the Destination Field Value field, enter the technical field name of the Generic Object field doing the filtering
on the Position object, for example, the technical name for company (GO doing the filtering)

9. Save your changes.

Implementing Employee Central Core

Configuration Tasks PUBLIC 49
[Link].5 Configuring a Foundation Object to Filter Another
Foundation Object

It is possible to use one foundation object as a filter for another foundation object.

To understand the steps involved, consider an example where: Location Group (Foundation Object) is required to
filter Location (Foundation Object) on Job Information and Position.

Name of the Foundation Object doing the filtering Location Group

Name of the Foundation Object being filtered Location

[Link].5.1 Step 1: Adding an Association to the Foundation

Object to be Filtered

In the Corporate Data Model, add an association to the Foundation Object to be filtered.

Context

In this example, an association is added to the location.

Procedure

1. Create the Generic Objects that will do the filtering and be filtered.

2. Go to Admin Center Configure Object Definitions .

3. From the Search dropdown, select Object Definition and then select the Generic Object to be filtered from the
dropdown next to it.

The Configure Object Definitions page is displayed.

4. From the Take Action dropdown, select Make Correction.
5. Scroll to the Associations section at the bottom.
6. Select Details. We will now set the association for the child object, meaning the object to be filtered.
7. In the Name field, specify a name for the association.

Implementing Employee Central Core

50 PUBLIC Configuration Tasks
8. In the Multiplicity field, select the type of association, either One to One or One to Many.
9. In the Destination Object field, select the Generic Object that will filter the values for this Generic Object on the
UI.

[Link].5.2 Step 2: Attaching the Parent Foundation Object

Values to the Foundation Object

Attach the relevant parent Foundation Object values to the Foundation Object.

Context

This attaches the relevant parent Foundation Object values to the child Foundation Object and allows you to specify
which parent values filter which child values.

Procedure

1. Go to Admin Center Manage Organization, Pay and Job Structures .

2. From the Search drop-down list, select Location (the object to be the subject of filtering) and then select the
relevant Location values that will filter the chosen Location from the drop-down list next to the Location field.
For this example, let’s select ACE_STO_BE.

The Foundation Object page is displayed.

3. Select Insert New Record.
4. Specify the Location Group for the child foundation object. This will update the page.

Implementing Employee Central Core

Configuration Tasks PUBLIC 51
5. Save your changes.

[Link].5.3 Step 3: Defining Field Criteria Using the Business

Configuration UI

Define field criteria for the Foundation Object field being filtered (in this case, location).

Context

This step is to be done for Job Information in the Business Configuration UI. For the Position object, refer to the
next step.

Procedure

1. Go to Admin Center Manage Business Configuration .

2. Select jobInfo.
3. Select Make Correction.

Implementing Employee Central Core

52 PUBLIC Configuration Tasks
4. Go to the child value field (the field to be filtered).
5. Select Details to add the field criteria.
• Here, we are using a custom field in the field criteria, <custom-string18>, to refer to <locationGroup>
since locationGroup is not a standard field of Job Information.

Implementing Employee Central Core

Configuration Tasks PUBLIC 53
 Implementing Employee Central Core
54 PUBLIC Configuration Tasks
[Link].5.4 Step 4: Defining Field Criteria for the Foundation
Object Field to Be Filtered (For Position)

Define field criteria for the Foundation Object that is to be the subject of the filtering field on the Position Object.

Context

This step is to be done when the object doing the filtering is an MDF Object. We just defined the field criteria for the
FO that is the subject of filtering for Job Information. We will now do the same for the Position Object. This tells the
system for this field which Generic Object is doing the filtering and the field that references it on Position.

Procedure

1. Go to Admin Center Configure Object Definitions .

2. From the Search drop-down list, select Object Definition and then select Position from the drop-down next to it.

The Configure Object Definitions page is displayed.

3. From the Take Action drop-down, select Make Correction.
4. In the Fields section, scroll to the Generic Object field to be filtered. In this example, cust_locationGroup.

 Note

For the example, we assume that you have already created a custom field by the name of
cust_locationGroup which is of type Foundation Object.

5. Select the Details link to view the configuration.

6. Scroll to the Field Criteria section.
7. In the Source Field Name field, enter the external name of the Foundation Object doing the filtering.
8. In the Destination Field Value field, enter the technical field name of the Foundation Object field doing the
filtering on the Position object.

Implementing Employee Central Core

Configuration Tasks PUBLIC 55
9. Save your changes.

[Link].6 Configuring a Foundation Object to Filter a Generic

Object

It is possible to use one foundation object as a filter for a generic object.

Context

To understand the steps involved, consider the following example where the Foundation Object Pay Grade is
required to filter the Generic Object Grade Level on Job Information and Position.

Name of the Generic Object to be filtered cust_GradeLevel

Technical Name of Field on Position of Generic Object being cust_GradeLevel_field

filtered

Technical Name of Field on Position of Generic Object doing payGrade

filtering

Implementing Employee Central Core

56 PUBLIC Configuration Tasks
Name of the wrapper Generic Object required to connect the FOWPayGrade
Generic Object to be filtered to the Foundation Object (Note
that this is a pre-delivered wrapper. It is important that you do
not create or use a custom wrapper.)

Name of the association to the object doing the filtering cust_toFOWPayGrade

configured on the Generic object to be filtered (Note that
this association name follows the recommended naming
guideline. For ease of use, it is suggested that you follow the
same protocol: cust_to<Object External Code>.

Element name of the Foundation Object doing the filtering in payGrade

the Corporate Data Model

[Link].6.1 Step 1: Associating the Generic Object Wrapper to

the Child Generic Object

Associate the wrapper to the child generic object, which means the field that should have its values filtered.

Context

In the example, we associate the wrapper to cust_GradeLevel_field.

Procedure

1. Go to Admin Center Configure Object Definitions .

2. In the Search field, select Object Definition and then select Grade Level (the object whose values will be filtered)
from the drop-down next to it.
3. From the Take Action drop-down, select Make Correction.
4. Scroll to the Associations section at the bottom and create an association between the wrapper
(cust_toFOWPayGrade) and the Generic Object (Grade Level).

5. Save your changes.

Implementing Employee Central Core

Configuration Tasks PUBLIC 57
[Link].6.2 Step 2: Associating Values to be Filtered

Associate values to be filtered to the values doing the filtering on the child Generic Object to be filtered.

Context

With this, you configure the child values (Generic Object) that can be selected for specified parent values
(Foundation Object).

Procedure

1. Go to Admin Center Manage Data .

2. Choose the relevant values to be filtered and attach the values doing the filtering to this object. In this example,
the external code of the Grade Level is the value to be filtered by the external code of the Grade.

3. Save your changes.

[Link].6.3 Step 3: Defining the Field Criteria for the Generic

Object Field Being Filtered

In the Business Configuration UI, define the field criteria for the Generic Object field being filtered.

Context

This configuration ensures that the association works on Job Information.

Implementing Employee Central Core

58 PUBLIC Configuration Tasks
Procedure

1. Go to Admin Center Manage Business Configuration .

2. Go to the child value field (the field to be filtered).
3. Select Details to add the criteria.
4. For Destination Field Value, select the identifier of the parent field in Job Information. For the Source Field
Name, add the field from Step 1: Associating the Generic Object Wrapper to the Child Generic Object [page
57] .

Implementing Employee Central Core

Configuration Tasks PUBLIC 59
 Implementing Employee Central Core
60 PUBLIC Configuration Tasks
  Note

The field-criteria attribute is currently not supported for the country/region-specific data models.

5. Save your changes.

[Link].6.4 Step 4: Defining Field Criteria for the Generic Object

Field being Filtered

Define field criteria for the Generic Object field being filtered on the Position Generic Object.

Context

This step is to be done only when Position Management is enabled.

Procedure

1. Go to Admin Center Configure Object Definitions .

2. From the Search drop-down, select Object Definition and then select Position from the drop-down next to it.

The Configure Object Definitions page is displayed.

3. From the Take Action drop-down, select Make Correction.
4. In the Fields section, scroll to the Generic Object field to be filtered. In this example, cust_GradeLevel_field.
5. Select the Details link to view configuration.

Implementing Employee Central Core

Configuration Tasks PUBLIC 61
 Things to note for this scenario:
• When adding an association from a migrated GO to a Foundation Object, you must use one of the
pre-delivered wrappers like FOWPayGrade (Pay Grade Wrapper) instead of creating a custom wrapper.
However if OData or API features are enabled, it is important that you do NOT use a pre-delivered wrapper
for associations from other MDF objects to Foundation Objects. Pre-delivered wrappers can be identified
by their names: ‘<FO Name> Wrapper’ and their external code ‘FOW<FOName>’.
• If OData or API features are not enabled, it is possible to use pre-delivered wrappers as association
destination at more than one MDF object types. To do this you must manually remove the field criteria
for effective start date at the field “parent” of the FO wrapper type. There is the restriction that the FO
instances cannot be filtered by the parent’s effective start date.
• If a pre-delivered wrapper type is not used as association destination of CostCenter by an OData or API
customer, the pre-delivered wrapper type must be used to configure a Foundation Object to filter a Generic
Object.
6. Save your changes.

Implementing Employee Central Core

62 PUBLIC Configuration Tasks
2.7 Configuring Company System Settings

Allow the admin access to the Company System and Logo Settings link in the Admin Center, which has many
Employee Central relevant settings.

Prerequisites

Ensure that the permission for Administrator Permission Manage System Properties Company System and
Logo Settings is enabled.

Procedure

1. Go to Admin Center Company System and Logo Settings .

2. In the Company System Setting section, select what is required for the company. Go through the list carefully.
Many settings enable validations or affect search results.

We recommend that at least the following validations be selected:

• Enable Address Validations: validate if postal codes are in the correct format for your country or region
whenever you add or edit addresses in People Profile or import addresses
• Enable National ID Validations
• Enable Bank Account Validations
• Enable Payment Information Validations
3. Optional: If you use contingent workers, select the Enable target group based filtering for Worker fields
checkbox.

This means that, if checked, then the values in the dropdown list for Worker fields will be based on the target
group settings assigned in permissions. If not checked, then all users will be available in the dropdown list.
4. Save your settings.

2.8 Configuring Employee Central Settings

Enable areas within Employee Central from this page.

Prerequisites

You must have the required permissions to view the page: Permission Settings Manage System Properties
Employee Central Feature Settings

Implementing Employee Central Core

Configuration Tasks PUBLIC 63
Context

Manage the areas of Employee Central using the Admin Center, for example:

• Time and Attendance Management

• Person, Employment and Worker Type
• Position Management
• Deductions Management
• Advances
• Fiscal Year
• IT Declarations
• Cost Distribution

Procedure

1. Go to Admin Center Manage Employee Central Settings .

 Note

If you are unable to see this page, it is recommended that you log out and log back in to the Admin Center.
Doing so will trigger the changes in permission immediately. You should then be able to search for the
Manage Employee Central Settings page.

2. Enable your changes.

3. Save your changes.

2.9 Configuring the Internal Job History Block on Legacy

People Profile

Configure the Internal Job History on the legacy People Profile to view the internal career history of an employee.
This history can be shared with a broader audience with the company.

Prerequisites

• Ensure that you have permissions to use the admin tool for legacy People Profile from Administrator
Permissions Manage System Properties Configure People Profile .
• Create a rule using the Display Internal Job History rule scenario. You do this by going to Admin Center
Configure Business Rules Employee Central Core Display Internal Job History .

Implementing Employee Central Core

64 PUBLIC Configuration Tasks
 This rule scenario only supports Job Information as the base object. In the rule, you only add the If condition,
for example, to show job changes in the People Profile. You can’t change the Set condition in the rule, and it is
not shown in the rule.
Here is an example for a rule configured for an event reason for promotion. Rules can be configured and
customized based on customer requirements.

• Ensure that you have permissions for this card from User Permissions Employee Widgets Internal Job
History .
• Ensure that you have permissions to view Job Information records from User Permissions Employee
Central Effective Dated Entities Job Information .

Context

This is a read-only card, which is really a filtered version of the job history for an employee.

Procedure

1. Navigate to the Admin Center Configure People Profile .

2. Select Custom Cards Internal Job History .

3. Drag and drop the card to where it should show in the profile.

This is a double card, meaning it needs 2 spaces. The system does not allow you to place it in a single space.
4. Select the card to edit it's properties.
5. Edit the card.
a. Enter the title and description.
b. Optional: Select the option Show the description below the card title.

If you don't select the option, users access the description through the  Help in the card.
c. Select the Job Information fields from the dropdown that you would like to have in the card.

Implementing Employee Central Core

Configuration Tasks PUBLIC 65
  Note

The fields shown in the dropdown list are based on the configured fields of the Succession Data Model
as well as the Country/Region-Specific Succession Data Model.

 Note

Transient fields, for example, time in position, time in job, time in company, are not supported.

 Note

Any fields with the label NA do not show data in the card.

d. Select the rule you created using the Display Internal Job History rule scenario from the Rules dropdown.

 Note

Only the Display Internal Job History rule scenario rules are shown. If no rule is configured, then the
Rule dropdown will not be seen.

6. Save your changes.

Results

To view the Internal Job History, navigate to the legacy People Profile for the employee whose history you would like
to see. The new card appears on the Profile. You will see the filtered version of the job history for an employee based
on the rule scenario configured and the Job Information fields selected.

Related Information

Rule Scenarios for Employee Central Core [page 351]

Showing Internal Job History on Work Experience Card [page 199]

Implementing Employee Central Core

66 PUBLIC Configuration Tasks