12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions
Key Takeaways
- My Team Positions shows up to 50 active lower-level positions, sorted by position external code.
- Only positions valid and effective today appear; future-dated and pending-approval positions are not shown.
- Nine Quick Action use cases exist for positions, with up to 5 templates each; a manager should have access to only one template per use case.
- Position Quick Action templates allow up to 8 base fields, except the Create Same-Level Position use cases, which allow up to 10.
- Transfer, Promotion, and Demotion EC Quick Actions can include the position field and offer to move the position to the new manager.
12.3 Manager Self-Service with My Team Positions and Quick Actions for Positions
Quick Answer: My Team Positions lets managers see and update the positions below them, with or without employees. Actions use Employee Central Quick Action templates for positions, such as Change Location of Position or Create Same-Level Position (Copy Rule). These are configured in Manage Data and granted in RBP. Joule supports the same position use cases in conversation.
The My Team Positions Page
Managers open it from the Home Page quick action Manage Team Positions or from Company Info > My Team Positions, available to managers with lower-level positions. The page:
- shows direct reports' positions and vacant positions in the manager's hierarchy
- lets managers edit or create positions through Quick Action templates
- shows up to 50 active lower-level positions, in ascending order of the position external code
Only positions valid and effective today are shown. Future-dated positions and positions pending workflow approval do not appear.
Positions are grouped With Assigned Employees and Without Assigned Employees. Each card shows:
- the top three fields configured for the Position Org Chart, set in Org Chart Configuration
- current and target FTE
- TBH status
- incumbent photo. With more than two incumbents, the first name plus "X others" appears.
Prerequisites: Employee Central Quick Actions must be enabled in Manage Employee Central Settings, an administrator must create templates in Manage Data, and managers need RBP access to them. Managers can also create, view, and delete job requisitions or requests here with the Recruiting integration (Section 13.4).
Quick Actions for Positions
Available use cases:
| Use case | Supported fields | Notes |
|---|---|---|
| Change Location of Position | Location (default, mandatory), comment, custom | Needs Insert and/or Correct on the Position object |
| Change Job Details of Position | Job Code, Job Title (defaults), comment, custom | Job Code or Job Title mandatory |
| Change Organizational Data of Position | Business Unit, Division, Department (default), Cost Center, Legal Entity, Location, comment, custom | One of BU, Division, Department, or Cost Center mandatory. Legal Entity can change only if the position is not staffed. |
| Change "To Be Hired" Status of Position | To Be Hired, multipleIncumbentsAllowed, targetFTE, standardHours, comment, custom | To Be Hired default and mandatory |
| Change Working Time for Position | FTE (default), Standard Hours, comment, custom | FTE or Standard Hours mandatory |
| Create Same-Level Position (Copy Rule) | Position Code (only if not auto-generated), Job Code, FTE, Standard Working Hours, comment, custom | Uses the Rule for Defining Copy-Relevant Position Fields; up to 10 fields |
| Create Same-Level Position (Copy All Fields) | Comment, custom | Copies all fields except localized ones; up to 10 fields |
| Reclassify Position | Position Title, Job Title, Job Code, Pay Grade, Pay Range, comment, custom | Job Code, Job Title, or Pay Grade mandatory |
| Deactivate Position | Status, comment, custom | Status default and mandatory |
Limits: up to 5 templates per use case, but a manager should have access to only one template per use case, which RBP controls. The total number of base fields cannot exceed 8, except the two Create Same-Level use cases, which allow 10. The Insert permission on Position is required for some use cases.
Core Quick Actions Involving the Position Field
Three EC Core Quick Actions use Job Information as the base object, need an event and event reason, and can include the position field:
| Use case | Mandatory (one of) | Default field | Events |
|---|---|---|---|
| Transfer | Position or Manager | Position | Transfer |
| Promotion | Position, Manager, Pay Grade, or Job Code | Job Code | Promotion, Job Change |
| Demotion | Position, Manager, Pay Grade, or Job Code | Job Code | Demotion, Job Change |
When one of these changes the manager, users with Option to Move Position to New Manager on Job Info Change can move the position to the new manager. These actions start from the profile or Manage My Team. Enter Manager to Filter Positions can help pick positions, and the list respects the manager's permissions. A workflow usually approves the change, and the new position's attributes propagate to Job Information.
Setting Up Position Quick Actions (THR79)
- Admin permission: Manage Business Configuration > Employee Central Quick Action Template (View, Edit, Import, Export). Log out and in.
- Templates in Manage Data > Create New > Employee Central Quick Action Template:
- Change Location of Position: base object Position, field Location.
- Create Same-Level Position (Copy Rule): rule Default_Position_Attributes, with fields Position Code, Job Code, FTE, and Standard Weekly Hours, plus Position Title (placed under Position Code) and To Be Hired.
- Manager permission: Employee Central Quick Actions > Use for CHANGE_POSITION_LOCATION and CREATE_NEW_POSITION_FROM_GIVEN_POSITION.
- Test as a manager (Carla Grant): change a direct report's position location to New York, then create Sales Director, SE as a same-level position (To Be Hired). It appears under Without Assigned Employees, and a workflow runs if configured.
Joule for Positions
Joule supports transactional position use cases: create same-level position (copy rule or copy all fields), change location, job details, organizational data, To Be Hired status, and working time of a position, plus Transfer and Promotion. It also covers navigational (for example view employment information) and informational (Assisted Q&A) patterns. Prerequisites include an SAP BTP enterprise global account or IAS setup, the relevant Quick Action templates, and the Access to Joule permission. Changes are submitted for approval like any other position change.
A manager cannot see a position on My Team Positions that becomes effective next month. Why?
How many base fields can a Quick Action template for positions contain?
Which Quick Action for positions allows changing Legal Entity, and under what condition?