6.3 Configuring Legacy and MDF Foundation Object Definitions
Key Takeaways
- Legacy (XML-based) foundation objects are configured in the Corporate Data Model; MDF-based foundation objects are configured in Configure Object Definitions.
- In MDF tools, a legacy foundation object is simply called a Foundation Object, and any MDF-based object is a Generic Object.
- Custom objects can be created only with MDF, not with the Corporate Data Model.
- In an MDF foundation object, field criteria create cascading picklists, and Condition Field and Condition Values show or hide a field.
- Codes and external codes of fields, objects, and records are case- and space-sensitive.
6.3 Configuring Legacy and MDF Foundation Object Definitions
Quick Answer: To change the structure of a foundation object (labels, visibility, required flags, custom fields, associations, rules), use the Corporate Data Model for XML-based objects and Configure Object Definitions for MDF-based objects. When the standard objects are not enough, for example an extra hierarchy level, create a custom generic object. That is only possible with MDF.
The Corporate Data Model
The Corporate Data Model lets you define labels for XML-based foundation objects and their fields, configure which fields are visible and required, use custom fields, customize associations, and assign business rules. It can be imported and exported from Provisioning or from Admin Center (Import/Export Corporate Data Model). You can change attributes and labels and add custom fields to meet customer requirements.
Worked Example: Relabel a Location Field
- In Import/Export Corporate Data Model, export the model and save it in the folder that contains the DTD files.
- Open it in an XML editor. Optionally, set the DOCTYPE to corporate-datamodel.dtd for local validation.
- Go to the location element and its standardHours field, and change the label to Standard Weekly Hours.
- Validate, save, and import the model through Import/Export Corporate Data Model.
- In Manage Organization, Pay and Job Structures > Create New > Location, confirm the new label.
MDF-Based Foundation Objects
MDF-based foundation objects, such as Legal Entity and Job Classification, are customized in Configure Object Definitions. Search Object Definition, choose the object, then Take Action > Make Correction. Each field's Details section holds attributes such as labels and visibility. The records in Manage Data reflect the definition. As with the Corporate Data Model, you can change attributes, relabel fields, and add custom fields.
Terminology
| Term | Meaning |
|---|---|
| Foundation Objects | The core structures SAP pre-delivers to hold company information. They can be XML-based or MDF-based. |
| Legacy Foundation Objects | XML-based foundation objects, the HRIS elements in the Corporate Data Model. In MDF tools, a legacy foundation object is simply called a "Foundation Object". |
| MDF-Based Foundation Objects | Foundation objects that have been migrated to the Metadata Framework |
| Generic Objects | Any MDF-based object, standard or custom |
Put simply: Foundation Objects = legacy (XML) FOs + MDF-based FOs, and Generic Objects = MDF-based FOs + all other MDF objects. This matters when you pick a data type for a field. In MDF, the data type Foundation Object points to a legacy FO such as Location, while Generic Object points to an MDF object such as Business Unit.
Custom Generic Objects
The standard foundation objects are customizable, but some requirements need more. A customer who needs more organizational hierarchy levels than SAP delivers creates a custom object, which is only possible with MDF, not the Corporate Data Model. Custom objects store additional company and people information. Their common characteristics:
- they may or may not be effective-dated
- they may or may not be secured (new custom objects must now be secured; Section 4.6)
- they may or may not be associated with another object
- they may or may not be available for self-service
Worked Example: Cascading Custom Fields on Legal Entity
ACE Corp wants two picklist fields, Scope and Region, on new legal entities. Region must depend on Scope and appear only when Scope = Global.
Step 1 – Picklists (Picklist Center or Import and Export Data)
| Picklist | Code | Parent | Values |
|---|---|---|---|
| Scope | SCOPE | none | global (Global), local (Local) |
| Region | REGION | SCOPE | AMER, EMEA, APAC, each with parent value global |
Picklist codes and external codes are case- and space-sensitive. If you import, the legacy picklist ID must match the code.
Step 2 – Fields on the Legal Entity object (Configure Object Definitions)
| Field | Setting |
|---|---|
| cust_scope | Data Type Picklist, Valid Value Source SCOPE, Label Scope; placed before countryOfRegistration |
| cust_region | Data Type Picklist, Valid Value Source REGION, Label Region |
| cust_region field criteria | Source Field Name = parentPickListValue, Destination Field Name = cust_scope |
| cust_region condition | Condition Field ID = cust_scope, Condition Values = global |
Step 3 – Test in Manage Data. Create a legal entity such as Axis Germany (AXIS_DEU). When Local is selected, Region stays hidden. When Global is selected, Region appears with only the child values.
Two different mechanisms are at work:
- Field criteria filter which values Region offers, based on the parent picklist value chosen in Scope.
- Condition / Condition Values decide whether Region is shown at all.
Worked Example: Adjust Job Classification
To change the Job Classification structure, open it in Configure Object Definitions, choose Take Action > Make Correction, update only the requested attributes, and save. Verify in Manage Data > Create New > Job Classification. SAP's instruction to change only the highlighted values reflects good practice: leave other attributes alone.
Choosing the Right Path
| Requirement | Path |
|---|---|
| Relabel or add a field on Location, Pay Range, Event Reason, or Workflow | Corporate Data Model (XML) |
| Relabel or add a field on Legal Entity, Business Unit, Division, Department, Cost Center, or Job Classification | Configure Object Definitions |
| Add a new organizational level or company data structure | Custom generic object in Configure Object Definitions |
| Show a field only for certain values | MDF Condition Field / Condition Values |
| Filter one field's values by another | Field criteria (MDF field or data model), plus an association where objects are involved (Section 6.4) |
A customer needs an additional organizational hierarchy level that SAP does not deliver. How is it implemented?
In the Legal Entity exercise, the Region field must appear only when Scope is Global. Which configuration controls whether Region is shown?
In MDF terminology, which statement is correct?