Configuring the Position Object

Objectives

After completing this lesson, you will be able to:
  • Set up the Position object
  • Create a Configurable UI for the Position object

Position Object

The Position object is an effective dated entity which has organization, job, and pay related fields. Each position is linked with a parent position and incumbent of parent position becomes the direct manager.

Being an MDF Object, the definition is maintained in Configure Object Definitions tool. Here you can make configuration decisions such as:

  • Displaying or hiding fields
  • Renaming standard labels
  • Adding translation labels
  • Adding custom fields*
  • Setting default field values
  • Configuring searchable fields
  • Setting up security
  • Setting up associations
  • Assigning a Default Screen UI
  • Assigning workflows and other business rules.

Note

* Currently, the limits on custom fields available for the Position object, are:
  • 30 custom String fields
  • 55 custom Number fields (mapped to Number, Boolean, Picklist, Translatable, Generic Object, Foundation Object...)
  • 20 custom Decimal fields
  • 15 custom Date fields (mapped to Date, DateTime, Time)

These limits are specific to Position object. There are different limits generally speaking, for Standard MDF Objects and Custom MDF Objects.

You will get a warning message when 80% of the limit is reached and an error message when the limit for the custom fields is exceeded, before the Object definition is saved.

For more information including the MDF Data Type Mapping, you can check: Custom Field Limits on Pre-delivered and Custom MDF Generic Objects

Object Details

When navigating to Configure Object Definitions, use the Search drop-downs to find the Object Definition → Position . Here you can choose Take Action → Make Correction.

At the top of the object definition is the object details section. This section determines the overall behavior of the object, such as the Status, Effective Dating and others. Some of the main details are :

Position Object main details

DetailDescriptionCurrent value
CodeThis is the unique identifier of the Generic Object in the systemPosition
Effective DatingDetermines whether the Generic Object is effective datedBasic
StatusStatus of the object (Active/Inactive)Active
MDF Version HistoryThe MDF Version History allows you to capture the MDF audit information about added, updated, and deleted field values and recordsNo
Default ScreenYou can assign a default configurable UI to an MDF objectN/A
LabelName of the object that appears on the UI. If no label is provided, the Code will be used.N/A
Workflow RoutingYou can add workflow routing to the object by associating it with a workflow. Alternatively, a workflow rule can be linked in the rules section.

Note

It is not recommended to assign a workflow at the object level. Instead, use business rules to trigger workflows, if needed, for Position creation, position changes, etc.
N/A
Pending DataIf you’ve linked a workflow to an object that involves an approval, and you want the data changes to take effect only if approved. In Position object, this is a requirement if workflows are to be triggered.No. This value should be set to Yes in the Position object definition.
Todo CategoryThis field is read-only. For all custom MDF objects, Generic Objects Change Requests is the default category. For predelivered MDF objects, the value is set by the respective business areasGeneric Object Change Requests

Note

Some of these current values will be changed in the exercise for Position Object set up, within this unit.

Fields

This section allows you to manage the object fields and the field attributes. On the position object, there are standard fields, business-relevant fields, position management fields, MDF system fields, and you can also create custom fields. Some labels/attributes might look slightly different in your system, however this will go over relevant information for the default set up:

  • Standard Fields - some standard fields of the object include basic fields used across the Metadata Framework, such as a Code, External Name, Status, Start Date, etc.
  • Business-Relevant Fields - some fields on the position object are connected to data coming from the organizational structure. These fields can be used to share data to employees assigned to positions. Some examples include Business Unit, Legal Entity (Company), Department, Job Classification (Job Code), FTE, Standard Hours, Employee Class, etc.
  • Position Management Fields - some fields have defined behaviors in the context of Position Management. Depending on the features used, these attributes may be mandatory. Some examples include Criticality, Position Controlled, Position Type, Target Capacity, Multiple Incumbents Allowed, To-Be Hired, Parent Position, and Right to Return. Some of these fields are only relevant for Succession Management.
  • MDF System Fields - some fields are technical fields and should NOT be modified or set to visible. These include internalId, and fields that start with "mdfSystem…", etc.
  • Custom Fields - you can add and set up custom fields for the position object to meet any customer needs.

Some specific fields will be described in this lesson. For more information on fields, please refer to the Fields in Position Object.

Business Relevant Fields

Fields that are job related are shared between objects like the Position Object, Job Classification object and the Job Information Object. These can be synchronized for data entry efficiency, since the data on these fields is common data and connected in the system. The business-relevant fields are standard fields that can be used in a synchronization between position and employee.

Job Code

The Job Code field is the standard field for the Job Classification on Job Information and Position and can be included on the synchronization between position and employee.

The Job Code field is commonly used to propagate other job-related fields from the Job Classification object when creating a Position record, when a job code is selected. Selecting a Job Code causes the fields from the Job Classification record to propagate onto common fields on the Position record..

Some of the default set of common fields between the Job Classification Object and the Position object include:

  • Job Title
  • Job Level
  • Regular Temporary
  • Employee Class
  • Pay Grade

Note

This data propagation from Job Classification to Position must be set up using a Business Rule. You must define the rule and assign the rule to the jobCode field in the Position object. You will learn how to set up the rule in the Unit 4 of this course.

Full Time Equivalent

The Target FTE (full-time equivalent) expresses the amount of accumulated FTE that may be assigned to this position. The FTE is calculated based on the standard hours that a person is scheduled to work. When an employee is assigned a position, they are staffed towards filling the Target FTE. If the Target FTE is 1, and one employee is hired full-time to the position, then the position is fully staffed. In some cases, the target FTE is greater than one in case more than one person would be required to staff the position.

Sometimes positions can be understaffed, whenever the current FTE value is lower than the planned FTE value for the position. In this case, there is no one working in the position, so the FTE shows as 0/1 FTE. In this situation, a To-Be-Hired graphic can be displayed to indicate the position needs to have someone hired to it. The position can be marked as not vacant, in which case although the FTE shows the position is understaffed, there is no To-Be-Hired graphic.

In some cases, a position may be overstaffed, which indicates the current FTE value is higher than the planned FTE for that position. The example above shows 3/2 FTE (3 incumbents assigned full-time to the position, but the planned FTE is 2 incumbents assigned full-time).

Note

The To-Be-Hired (TBH) adaptation is one of key Follow-Up processes in Position Management that will update the TBH status based on position assignments/unassignments, or whenever the employee's FTE who is assigned to a position is changed. There are different available options to control the ‘To Be Hired’ Status Adaptation behavior in Position Management Settings that you will learn in this course

It is also possible to configure the system to prevent the position from being over-staffed (Current FTE > Target FTE), enabling the Position Controlled field, and set the value to True in a Position record. The Position Controlled field will check the Target FTE when an employee is being assigned to the position and would prevent any overstaffing.

The Transition Period is another setting related to the FTE. If there is a need for temporary overstaffing (Current FTE > Target FTE), such as an employee being hired to a position while the employee leaving is still assigned (for a handover of tasks, etc), this transition period can be assigned in Position Management Settings globally for all positions, or you can use Position Types if only a group of positions should have this option.

Standard Hours

This is the standard field for the standard hours on job information and position and can be included in the synchronization between position and employee. In this case, the employee's FTE value will be calculated based on the standard hours inherited from the employee's assigned position.

A business rule to Calculate FTE would check the value of standard hours field from most to least specific value. Starting from the Standard Hours field in the Employee's Job Information. In case the value is null, the rule would be looking elsewhere to find the Standard Hours value and propagate it into the Job Information of the employee. Ultimately, the FTE would be calculated based on the Standard Hours.

The order that the business rule to calculate FTE will follow is: Job Information, Position, Job Classification, Location and Legal Entity.

Parent Position

The parent position is the higher-level position in the Position Hierarchy. When an employee is assigned a position in Job Information, this can be used to automatically replace the employee’s supervisor with the incumbent of the Parent Position.

When positions are created from Position Org Chart based on a source position (Create Same-Level Position / Add Lower Level Position), the Parent Position value is defaulted based on the position hierarchy and non-editable during position creation. For Copy Position, the position field values including the Parent Position would be copied over the new position(s) to be identical.

The Parent Position is technically a one-to-one association type in the Position Object definition.

Incumbent

The incumbent field is designed to display a user in the system who is currently occupying the position.

Note

This field is only relevant for Succession Management and how you set the visibility will depend on the following:

  • If Position Management and Succession Planning are being used : Set the visibility to Not Visible
  • If only Position Management is used : Set the visibility to Not Visible
  • If only Succession Planning is used: Set the visibility to Editable

The reason behind it is that in Employee Central Position Management, the assignment between a position and the incumbent is made using the position field on Job Information, so there is no requirement to maintain this field.

The Configure Object Definition tool will trigger an error message when saving changes in the Position object, if the incumbent field visibility is set to Editable or Read-Only and Employee Central Position Management is enabled.

Other relevant fields

Some other fields in the Position Object are :

Other relevant Position fields

CodeLabelDescriptionRecommended?
vacantTo Be HiredIndicates whether anyone will be hired for this position. If set to True, it is shown on the Position Org Chart as To Be Hired position. Some parameters in Position Management Settings can be used to set TBH status when an incumbent is assigned/unassigned from Position or based on FTE value changes.Yes
multipleIncumbentsAllowedMass PositionThis attribute controls whether the system allows the assignment of more than one employee to this position at any point in time.Enabled but set to No as default.
positionControlledPosition ControlledPosition Control helps to control FTE capacity of position. If a position is subject to position control, the FTE values of all incumbents assigned to the position may not be higher than the FTE value assigned to the position. This feature is used for budget control.Yes
typePosition TypeYou can use position types to modify standard system behavior for one or more positions for actions like workflows for position changes, reassignment of direct reports when a manager leaves a position or how to manage transition periods, reporting line or job relationships adaptation.No, unless there is a particular business need to use Position Types in the organization. Position Types would add more complexity to the organization.

Note

There are other fields, relevant for Succession Management, that will be discussed in Unit 5 - Integrating SAP SuccessFactors Employee Central Position Management with other SAP SuccessFactors solutions

To Define Field Labels and Visibility

You can define field labels, visibility, set default values, and add custom fields to your object as needed.

Steps

  1. Log in to the instance.

  2. Navigate to the Configure Object Definitions tool.

  3. Search for the Object Definition → Position.

  4. Select Take Action → Make Correction..

  5. Find a field that you would like to modify.

  6. Select the Details. Here you can define the field labels if you don’t want to use the default labels, define the visibility, if the field if mandatory or not, or add a default value.

  7. Under Details, you can maintain the uiFieldRenderer field to hide external codes for Generic Objects and Picklist fields, like Department, Job Code or Job Level, to display only the label. Use displayGOWithoutExternalCode for Generic Objects, and displayPickListWithoutExternalCode for Picklists

  8. To add a custom field, scroll to the bottom of the fields section. Identify an empty row to add a field that has the name "cust_".

  9. Add your custom field. Select the Details to modify the set up of the field be selecting a data type, adding the max length, visibility, required, and a label

  10. Click Save on the object.

Object Associations

As you learned in the SAP SuccessFactors Employee Central Core Academy course, Foundation Objects and Generic Objects can be associated using Associations. These associations define a hierarchical relationship between objects and therefore will determine, as an example, that a newly created Department belongs to a specific Division, or a Location is associated to several Legal Entities within the same country.

Ultimately, an association can be utilized for filtering results based on the parent field in the Employee File using field criteria that is set up in the Succession Data Model / Manage Business Configuration. Which means that, based on the Division (parent field) assigned to the employee when hiring or making changes from MSS UI or History, the available Departments (child or lower field) will be filtered to display only those associated to that Division. This would help in the data entry to ensure only the correct associated objects can be selected in the Employee File.

Custom Associations can be created according to your customer's needs.

Note

To refresh or expand the Associations topic you can review these resources in the SAP Help Portal: Associations, which covers the associations between Foundation Objects in Employee Central.

The guide Implementing the Metadata Framework (MDF) has also references to associations between generic objects: Associations in MDF

Associations in Position Object

Position object is not an exception and there are some standard associations that you will find in the Object Definition. The following table summarizes the available associations found in Position :

Position Object Associations

NameMultiplicityDestination ObjectTypeVisibility
positionMatrixRelationshipOne To ManyMatrix Relationship For PositionCompositeNot Visible
parentPositionOne To OnePositionValid WhenEditable

The most important association is the one from Position to Parent Position. This is a one-to-one association where you will essentially associate every position with its Parent Position to establish the position hierarchical level. Parent Position will also play an important role when creating Lower Level or Peer positions from the Position Org Chart since the value will be auto-populated depending on the hierarchical level between the Source and Target Position.

The Position to Matrix Relationship For Position relationship can be set to Editable to maintain Matrix Relationships for positions, synchronize between Matrix Relationships and Job Relationships when assigning employees to positions and restrictions, if needed, to apply in Role-Based Permissions to determine access to view or create positions based on this relationship.

Note

For more information about Matrix Relationships, you can check the following section in the guide Implementing Position Management , available in the SAP Help Portal: Matrix Relationships

Object Security

MDF Objects can be set to Secured or Non-Secured within Configure Object Definitions → Security. The Position object is set to be Secured, and therefore, access is controlled from role-based permissions, under Miscellaneous Permissions category.

You can verify the Position Generic Object security by following these steps:

  1. Go to the Admin Center and choose Configure Object Definitions.
  2. Search for Position and select Take Action → Make Correction.
  3. In the generic object definition, scroll down to the Security section. Verify that Secured is set to Yes , and Permission Category is set to Miscellaneous Permissions and save your changes.
  4. Go back to the Admin Center and choose Manage Permission Roles.
  5. Select the role name, such as System Admin, whose permissions you want to manage.
  6. Choose Edit, and on the Edit System Admin page, navigate to the step 2. Add Permissions.
  7. On the 2. Add Permissions screen, scroll down to Miscellaneous Permissions and specify which permissions users with this role should have. For example, you can define whether users should be able to view positions and also which actions they are allowed to perform for a position. In addition, you can define field level overrides for the position to ensure, for example, that users can’t access a particular position field.
  8. Choose Next to continue to step 3. Preview, and then, select Save to save all your changes.
  9. To further restrict which positions employees with the permission roles that you just maintained are allowed to view, create, insert, correct, or delete, you can define a Target Criteria on the Position object. Navigate back to Manage Permission Roles page, and select the role to edit.
  10. On the next step, select the Assignments tab, and on the Actions column, choose Edit.
  11. Navigate to step 4. Define Target Criteria, and locate Position, under Miscellaneous Permissions. By default, All is selected, which means that the permissions you granted for this role are valid for all positions in the system. Select the radio button for Restrict Target Criteria to:

    You can restrict the target population based on different options:

    • You can grant user access to every position, or to a specific target group of positions.
    • You can also restrict access to positions lower in the hierarchy than the granted user’s position.
    • If you are using Matrix Relationships on the Position object, you can also restrict access to positions based on the Matrix Relationships.

Set up Position Object

Your customer wants to implement several changes in the Position object definition such as, changing labels for some of the standard fields, adding custom fields, set up the association with Position Matrix Relationships and change the visibility for several fields.

Whenever possible, the customer does not want to see the external codes, only the labels (except for the Job Code), so you will need to work on these changes for Generic Objects and Picklists. As a last step, the customer also wants to confirm the Position object is secured and access can be controlled at a more granular level through permissions in Role-Based Permission framework.

Note

In a previous exercise, you already specified the target population for Position object to restrict access to certain actions for Managers and Employees. In this exercise, you will verify these restrictions will also apply when creating positions.

In the Position Standard Fields table, review the column UI Field Renderer and add the following values in Details → UI Field Renderer for those fields that are set to Yes, depending on the type of field.

  • For fields of type Picklist:displayPickListWithoutExternalCode.
  • For fields of type Generic Object:displayGOWithoutExternalCode.
ExerciseStart Exercise
ExerciseStart Exercise

Steps

  1. Make the following modifications to the Position Object. using the Object Details and Position Standard Fields tables below. Look for the highlighted values to be modified:

    Object Details.New value.
    Pending DataYes.
    Position Standard Fields
    NameData TypeLabelVisibilityRequiredUI Field Renderer
    multipleIncumbentsAllowedBooleanMass PositionEditableNo 
    positionControlledBooleanPosition ControlledEditableNo 
    standardHoursDecimalStandard Weekly HoursEditableNo 
    codeStringPosition CodeEditableYes 
    externalNameTranslatablePosition TitleEditableYes 
    positionTitleString Not VisibleNo 
    criticalityNumber Not VisibleNo 
    commentString Not VisibleNo 
    incumbentUserIncumbentNot VisibleNo 
    changeReasonPicklistChange ReasonNot VisibleNoN/A
    descriptionStringDescriptionNot VisibleNo 
    jobCodeGeneric ObjectJob CodeEditableYesNo
    jobLevelPicklistJob LevelEditableNoYes
    employeeClassPicklistEmployee ClassEditableNoYes
    regularTemporaryPicklistRegular/TemporaryEditableNoYes
    targetFTEDecimalFTEEditableNo 
    vacantBooleanTo Be HiredEditableNo 
    companyGeneric ObjectCompanyEditableNoYes
    businessUnitGeneric ObjectBusiness UnitEditableNoYes
    divisionGeneric ObjectDivisionEditableNoYes
    departmentGeneric ObjectDepartmentEditableNoYes
    costCenterGeneric ObjectCost CenterEditableNoYes

    1. Navigate to Configure Object Definitions using Action Search.

    2. In the Configure Object Definitions page, select Object Definition in the Search drop down, then type Position to search for the Position object, and select it.

    3. Once the Position object displays, choose Take Action → Make Correction on the right side.

    4. In the Object Definition details, make the changes highlighted in the Position Object details table.

    5. Scroll down to the Fields section, locate the fields given in the Position Standard Fields table and the make the required changes.

      Hint

      Choose Details button next to each field, to view more information of the field.

    6. Click Save to save all changes.

      Note

      When saving at this step, you will see a warning message that refers to the positionTitle field being searchable and set to 'Not Visible'. Select Yes to continue and save the object definition. You will remove this field as a searchable field in step 5, and use the default searchable fields externalCode and externalName and some additional fields to search for positions.

  2. Create a new picklist for the Position's Incentive Plan custom field you will be adding into the Position object definition.

    1. Navigate to Picklist Center using Action Search.

    2. Select + to create a new picklist, with the following details:

      • Code : IncPlan
      • Name: Incentive Plan
      • Status: Active
      • Effective Start Date: Jan 1, 1900
      • Display Order: Alphabetical

    3. Select Save.

    4. In the Picklist Values section, select + to add these 4 values. Select Save after adding each.

      • External Code : MGR Name : Manager
      • External Code: SMGR Name : Senior Manager
      • External Code: IND Name: Individual
      • External Code: EXEC Name: Executive

  3. Add two new custom fields, Incentive Plan and Onsite/Remote, to the Position object definition, using the Position Custom Fields table. For these new fields, your customer does not want to see the external codes of the picklist values, so make sure to use displayPickListWithoutExternalCode in the UI Field Renderer.

    Position Custom Fields
    NameMax LengthData TypeValid Values SourceRequiredVisibilityLabel
    cust_IncPlan38PicklistIncPlanNoEditableIncentive Plan
    cust_onsiteRemote38PicklistonsiteRemoteNoEditableOnsite / Remote

    1. Navigate back to Configure Object Definitions using Action Search.

    2. In the Configure Object Definitions page, select Object Definition in the Search drop down, then type Position to search for the Position object, and select it.

    3. Once the Position object displays, choose Take Action → Make Correction on the right side.

    4. Create the new custom fields given in the Position Custom Fields table above. Notice that cust_ will appear automatically in the name when adding new fields.

    5. Scroll down and choose Save.

  4. Enable the Position to Matrix Relationship For Position association.

    1. Navigate to Take Action → Make Correction to continue editing the Position object.

    2. Scroll down to the Associations section, and locate the positionMatrixRelationship association name.

    3. Do not change any of the existing options (Name, Multiplicity, Destination Object, Type) for this association and select the Details option.

    4. Make the following changes:

      • Visibility: Editable.
      • Label: Matrix Position.

    5. Select Done.

    6. Scroll down and Save.

  5. Make modifications in the Searchable Fields in the Position Object, to use the newly created custom fields and remove the existing field in the section.

    1. Navigate to Take Action → Make Correction to continue editing the Position object.

    2. Scroll down to the Searchable Fields section, and complete the following changes:

      • Remove positionTitle as a searchable field using the bin icon.
      • Add cust_IncPlan picklist as a searchable field. You will need to type cust_IncPlan.label
      • Add cust_onsiteRemote picklist as a searchable field. You will need to type cust_onsiteRemote.label .

    3. Scroll down and choose Save to save changes.

  6. Verify the Position Object is secured and make additional changes on the Security.

    Security
    FieldValue
    SecuredYes
    Permission CategoryMiscellaneous Permissions
    CREATE Respects Target CriteriaYes

    1. Navigate to Take Action → Make Correction to continue editing the Position object.

    2. Scroll down to the Security section.

    3. Verify the information is as shown in the Security table and set the value for CREATE Respects Target Criteria. to Yes.

    4. Click Save to save changes in the object definition.

  7. Verify you can see all the changes when creating a new position.

    1. Navigate to Manage Positions using Action Search.

    2. Select Create New → Position and confirm all your changes. When done, click Cancel.

  8. Verify that Managers can only create positions below their hierarchy as defined in the previous exercise Set Up Role-Based Permissions for Position Management.

    1. Proxy as Marcus Hoff to access the instance as a manager.

    2. Navigate to the Position Org Chart from Home → Company Info.

    3. Click on the Add Position icon found on the Position Org Chart toolbar.

    4. In the Job Code field, select Director, Operations (OPS-DIR)

    5. In the Parent Position field, select VP, Operations (POS-VPOPS)

    6. Complete any other required field to your choice.

    7. When finished, click Save. Verify an Error pop up dialog will prevent from creating the position, due to No Permission. The reason is that the Parent Position selected is not in your target population.

    8. Click OK. Cancel and do not save the changes.

Configurable UI for MDF Objects

In a previous lesson, you have learned how to make changes on the fields and attributes for the Position object, using the tool Configure Object Definition. Additionally, MDF Objects (Generic Objects) including Position object, can have a more user-friendly layout that can be configured in the tool Manage Configuration UI.

The Manage Configuration UI tool is part of the Metadata Framework options and access is granted from Manage Permission Roles → Administrator Permissions → Metadata Framework.

This tool is mainly used for any of these objectives :

  • Create an MDF Screen UI to use as Default Screen for the Object Definition, allowing for a more user-friendly layout when creating object records (Generally in Manage Data or Manage Positions in case of Position records.)
  • Create an MDF Screen UI to display an Object in Custom MDF Block in Employee File.

Some of the capabilities of Manage Configuration UI are:

  • Change label for fields.
  • Add new fields.
  • Change the display sequence of fields.
  • Change the layout of UI.
  • Change visibility of fields.
  • Set fields to required.
  • Add Rules
  • Delete a field from UI.
  • Add a link.
  • Add a group.

    Note

    This list is not an exhaustive list of capabilities for Manage Configuration UI tool. To find out more, check the following guide: Implementing the Metadata Framework (MDF)

Create a Configurable UI for Position object

Your customer has noticed that the Position Object definition is disorganized. They would like to rearrange fields, and group some of the fields in different sections for a more user friendly layout. In the following exercise, you will create a Configurable UI for Position Object to fulfill their requirement.

Note

You should exercise caution and not delete any field while creating the Configurable UI. The tool does not have a revert back option and you would need to start over if accidentally deleting a field. The best option is to organize all the fields first, and once all the changes have been saved, you can delete any field that is not needed. You will notice that the tool creates an Input field every time a new group is added, since it is a requirement to have at least one field per group. Once you have completed the steps and rearrange the position fields to every group, you can remove these Input fields

ExerciseStart Exercise

Prerequisites

Administrator should have permissions to access Manage Configuration UI tool.

Steps

  1. Verify that currently, Position records have the same layout as the image Position Object Details.

    1. Navigate to Manage Positions using Action Search.

    2. Search Position and locate Sales Director, NE (DIR_SALESNE) from the existing positions.

    3. Verify the layout displays as the image Position Details.

  2. Create a new Configurable UI Screen using the example from the images.Position Configurable UI Fields (rearranging fields as a first step) and Position Configurable UI Screen (the final results applying some UI layout changes).

    1. Navigate to Manage Configuration UI using Action Search.

    2. Click on Create New to create a new UI. Set the Id as PositionUI and Select Base Object, select Position.

    3. As a first step, rearrange the fields following the order from the Position Configurable UI Fields image.

    4. Click Save to make sure these changes are saved before continue to the next step.

    5. In the Position blue toolbar, select Add Group to create a new group. The new group will be added at the end of the screen with a default Title and a field Input.

    6. Hover over the new group to view the option Edit Properties. Click into this option.

    7. In the Title Type User Defined, change the Title to Job Classification Details.

    8. Expand the Title Style section and select the checkbox for Bold to display the title in bold.

    9. Scroll up and change the Layout to Flow.

    10. Click OK to confirm changes.

    11. Drag and drop the required fields that should be included in this section: Job Title, Job Level, Employee Class, Regular/Temporary and Pay Grade.

    12. Delete the Input field that was created when you added the new group.

    13. When done, click Save to ensure everything is saved as of this step.

    14. Repeat steps e and f to create another group and edit its properties. Remember that you must click Add Group from the option at the top of the page.

    15. In the Title Type User Defined, change the Title to Organizational Details.

    16. Expand the Title Style section and select the checkbox for Bold to display the title in bold.

    17. Click OK to confirm changes.

    18. Drag and drop the required fields that should be included in this section: Company, Business Unit, Division, Department, Location and Cost Center.

    19. Delete the Input field that was created when you added the new group.

    20. When done, click Save to Save Changes.

  3. Make additional changes on the Matrix Position association visible in the Position object.

    1. Locate the Matrix Position association, which includes the fields Type and Related Position.

    2. Change the Title to Matrix Position Details.

    3. Select the edit option in the Related Position field.

    4. Locate the Label Override and type Matrix Position. Select OK.

    5. Select Save to save all changes.

  4. Assign the new UI Screen to the Position Object

    1. Navigate to Configure Object Definitions using Action Search.

    2. Search Object Definition and locate Position on the drop down list.

    3. Select Take Action → Make Correction to make changes in the Position object.

    4. In the Default Screen field, select the PositionUI you created previously.

    5. Save changes.

  5. Verify changes navigating to Manage Positions and search for an existing position (Sales Director, NE (DIR_SALESNE))

    1. Navigate to Manage Positions using Action Search.

    2. Search Position and locate Sales Director, NE (DIR_SALESNE) from the existing positions.

    3. Verify the layout now has changed and fields are displayed following the Configurable UI you created. You can check the Position Configurable UI Screen.

  6. The Configuration UI is now completed

Log in to track your progress & complete quizzes

Learning

SAP FacebookSAP YoutubeSAP LinkedIn