How to prepare and build JPB to make it future ready for Talent Intelligence Hub

By · · ·

Job Profile Builder (JPB) in SAP SuccessFactors: How to Prepare, Build, Enable, and Keep It Future-Ready for TIH, OMP, and AI



Why this matters: If you want SuccessFactors to scale into a skills-based and AI-assisted operating model (Talent Intelligence Hub, Growth Portfolio, Opportunity Marketplace, Recruiting/Learning recommendations), then Job Profile Builder (JPB) must be treated as governed master data—not as “just job descriptions”.

Long-term positioning: Use JPB for stable job architecture + structured job profile content. Align skills/attributes with TIH (Attributes Library + Growth Portfolio). Treat OMP as a downstream consumer that performs well only when your job/skill data is clean, consistent, and governed.

1) What success looks like (long-term)

  • Stable taxonomy: Families → Roles → Profiles that can survive reorganizations.
  • Skills strategy aligned to TIH: One enterprise approach to skill naming, proficiency, and ownership.
  • Downstream-ready: Recruiting, Learning, internal mobility, and recommendations consume structured profile data without turning into free-text chaos.
  • Operational governance: Workflow-driven changes, clear ownership, versioning, and lifecycle control.

2) Strategy (with 2–3 examples for every line item)

Strategy line item 2–3 examples (what “good” looks like)
Job Architecture model
(Families → Roles → Profiles)
  • Keep Job Families stable (e.g., Finance, Engineering, Sales) even when org structures change.
  • Define Roles by capability (e.g., Backend Engineer, FP&A Analyst), not by reporting line.
  • Standardize levels (e.g., L1–L6) with clear leveling rules to prevent duplicate roles.
Standardize profile templates
(sections + content)
  • Mandatory sections: Purpose, Responsibilities, Required Skills, Competencies, Education/Certifications.
  • Optional sections by population: Travel %, Physical requirements, Security clearance.
  • Define “locked global fields” vs “editable local fields” to balance standardization and compliance.
Skills & attributes strategy
(TIH-aligned)
  • Normalize skill naming (avoid duplicates like “Stakeholder Mgmt” vs “Stakeholder Management”).
  • Use one proficiency model enterprise-wide (Foundational/Working/Advanced/Expert).
  • Separate technical skills from behavioral competencies (e.g., Coaching, Leading Change) by job level.
Governance & change control
(ownership + approvals)
  • HR CoE owns taxonomy; Business validates responsibilities; TA/L&D co-own skill quality and learning alignment.
  • Quarterly “Job Catalog Review Board” to merge duplicates and retire unused roles.
  • All profile changes go through workflow approval before publishing (no ad-hoc edits).
Lifecycle & versioning
(create → publish → retire)
  • Statuses are typically managed through governance + deactivation/retirement actions, not a “Status” field on the Family create screen.
  • Review triggers: transformation programs, new tech/AI shifts, compliance changes, mergers.
  • Retire rule: no incumbents + no requisitions for X months → deprecate then retire (after unlinking roles/mappings).
Localization & compliance
  • Keep global purpose/skills consistent; localize legal wording of job description text only where required.
  • Country-specific additions: mandated certifications, safety requirements, working time clauses.
  • Translation SLA: EN master first; local translations within 30 days of change.
Bias & inclusive language controls
  • If Job Analyzer is available, run it during authoring of Short/Long Description.
  • If it’s not available, enforce an internal inclusive-language checklist + standard phrases library.
  • Replace inflated “years of experience” requirements with skills/outcomes where possible.
Consumer mapping
(Recruiting, Learning, OMP)
  • Recruiting: reuse structured requirements so requisitions don’t become free-text islands.
  • Learning: map skills to learning items so development recommendations are meaningful.
  • OMP: enable intelligent recommendations only when skills adoption and opportunity data are sufficient.
AI readiness & data hygiene
(normalize, dedupe, govern)
  • Normalize skills (avoid duplicates and abbreviations as separate skills).
  • Control who can add skills and how synonyms are handled (skills governance).
  • Set proficiency rules to reduce inflated ratings that degrade recommendations.

3) Enablement essentials (JPB, Security/Visibility, Workflow, Job Analyzer, TIH readiness)

Important: Some steps require Provisioning access (often done by SAP Support or an implementation partner). Plan these early to avoid delays.

3.1 JPB prerequisites (baseline)

  • Ensure MDF (Generic Objects) and Role-Based Permissions (RBP) are enabled.
  • Ensure the JPB / Skills Management switches are enabled for your tenant configuration.

3.2 Secure Job Profile, Skill Profile, and Rated Skills (required for Visibility + controlled access)

Where: Admin Center → Configure Object Definitions

  1. Job Profile: Take Action → Make Correction → Secured = Yes → assign appropriate Permission Category → Save
  2. Skill Profile: Take Action → Make Correction → Secured = Yes → assign appropriate Permission Category → Save
  3. Rated Skills: Take Action → Make Correction → Secured = Yes → assign appropriate Permission Category → Save

3.3 RBP permissions (minimum set most projects need)

Where: Admin Center → Manage Permission Roles

  • Admin permissions: Manage Job Profiles, Job Profile Templates, Manage Job Profile Content, Manage Job Profile Content Import/Export
  • Visibility permissions: grant view/edit access for Job Profile / Skill Profile / Rated Skills via the assigned permission category
  • Recommended: separate roles for View-only, Edit, and Approve

3.4 Workflow (non-negotiable for long-term governance)

  • Enforce Draft → Approval → Active for job profile changes.
  • Route approvals to To-Do so nothing is missed.
  • Define and enforce “no direct edits” as policy.

3.5 Upgrade Center of Capabilities to Job Profile Builder (what this really means + step-by-step)

Many customers say “upgrade Center of Capabilities to JPB”, but in the current SuccessFactors design, Center of Capabilities is automatically enabled when Job Profile Builder is enabled. The real “upgrade” is usually one of these:

  • You are on legacy Job Description Manager (JDM) / legacy competency structures and need to move to JPB + Center of Capabilities.
  • You already enabled JPB, but you still need to migrate legacy competencies / libraries into the new MDF-based capability structures so that mapping screens behave correctly.

A) Confirm whether JPB is enabled (and therefore Center of Capabilities is already enabled)

  1. Go to Admin Center.
  2. Search for Job Profile Builder tools:
    • Manage Job Profiles
    • Manage Job Profile Content
    • Manage Job Profile Content Import/Export
  3. If these are available and working, JPB is enabled, and Center of Capabilities is already enabled (no separate enablement required).

B) If you are upgrading from legacy (JDM / legacy competencies): run the migration to JPB + Center of Capabilities

This is the step that actually “converts” legacy structures into the JPB/Center of Capabilities framework.

  1. Prepare before migration
    • Freeze changes in legacy job descriptions/competencies during the migration window.
    • Identify duplicates (same competency/skill with different naming) and clean up where possible.
    • Confirm you have the required admin permissions to run migration tools (and Provisioning support if your landscape requires it).
  2. Enable JPB if not enabled
    • Go to Admin Center → Upgrade Center.
    • Enable the JPB-related upgrade in your tenant (names vary by tenant/release).
    • After enablement, verify JPB tools are available in Admin Center (Manage Job Profiles / Manage Job Profile Content).
  3. Run the migration from legacy data to JPB + Center of Capabilities
    • Follow the tenant’s migration process to move:
      • Job Families and Roles
      • Competencies / capability libraries
      • Associations used in job profiles
    • After migration, validate that competencies/capabilities are visible and selectable when mapping.
  4. Run post-migration checks (mandatory)
    • Use the Check Tool for Job Profile Builder / migration checks and resolve errors before opening maintenance to broader admin groups.
    • Spot-check a sample set:
      • Families and Roles exist
      • Mapped competencies/capabilities are available
      • Job profiles still display content correctly

C) What changes after the upgrade (so admins don’t get confused)

  • Legacy competency/library structures become represented in MDF-based objects used by Center of Capabilities.
  • Admins should maintain capabilities/competencies in the new framework going forward, not in legacy screens.
  • If you had duplicates earlier, you will feel it more now—so enforce naming standards and governance.

D) Troubleshooting if users still can’t see capabilities/competencies while mapping

  • Re-check RBP and secured object permissions (visibility issues often look like “data missing”).
  • Confirm the migration completed successfully and fix migration errors before proceeding.
  • Validate that you are maintaining data in the correct (new) place post-upgrade.

3.6 Upgrade Center of Capabilities (CoC) to Talent Intelligence Hub (TIH) (step-by-step)

In the current SuccessFactors direction, CoC capability portfolio functionality is moving to Talent Intelligence Hub (TIH). If you see messages like “This functionality has moved to Talent Intelligence Hub. Please upgrade to Talent Intelligence Hub and enable the Growth Portfolio”, that is the platform telling you the path forward is TIH.

Important: Think of this as a framework shift: competencies/capabilities and skills management becomes TIH-first (Attributes Library + Growth Portfolio), while JPB remains the job structure foundation (Families/Roles/Profiles).

A) Before you upgrade (mandatory readiness checks)

  1. Freeze change window: stop ad-hoc edits in CoC / competencies / skills during the upgrade and migration activities.
  2. Export a backup: export current competency/capability/skills libraries and mappings (all locales you use).
  3. Run Check Tool:
    • Go to Admin Center → Check Tool.
    • Run checks relevant to your starting point:
      • If you are still on Job Description Manager (JDM), run the JDM migration checks.
      • If you are already on JPB/CoC, run the JPB-related migration checks.
    • Resolve issues before proceeding (duplicates, missing required data, inconsistent locales, orphaned mappings).
  4. Confirm governance: define who can create/approve skills and who owns deduplication, proficiency scale, and naming standards.

B) Upgrade to TIH (Upgrade Center steps)

  1. Go to Admin Center → Upgrade Center.
  2. Under Recommended Upgrades (or a similar section in your tenant), find Talent Intelligence Hub.
  3. Choose Learn More (recommended) and then Upgrade Now.
  4. Confirm the upgrade prompt.
  5. After enablement, log out/in and verify TIH tools appear in Admin Center (search for TIH and Growth Portfolio tools).

C) Enable Growth Portfolio (so TIH is actually usable)

  1. Open the TIH-related admin area in your tenant (search in Admin Center for TIH and Growth Portfolio tools).
  2. Enable Growth Portfolio for your pilot population first (recommended), then expand.
  3. Assign permissions:
    • End users: ability to view/add/update their attributes in Growth Portfolio.
    • Admins: ability to manage the Attributes Library and control attribute governance.
    • Leaders/HR (optional): reporting/visibility permissions based on your policy.

D) What migrates when moving from CoC/JPB framework to TIH (what to expect)

  • What you keep as foundation:
    • JPB job structure (Families, Roles, Job Profiles) stays as your job catalog foundation.
    • Existing role-to-job-code mapping stays important for consistency and reporting.
  • What moves into TIH operating model:
    • Competencies/capabilities and skills become governed through the TIH framework (Attributes Library + Growth Portfolio).
    • Ongoing maintenance should be done in TIH-first locations going forward (not legacy CoC screens).

E) Post-upgrade configuration (so customers and consultants can actually use it)

  1. Set the enterprise proficiency model (one model across all skills).
  2. Normalize skill naming (merge duplicates; manage synonyms as synonyms, not separate skills).
  3. Rebuild mappings in a controlled way:
    • Map core skills at Family level (broad shared skills).
    • Map differentiator skills at Role level (what makes roles unique).
    • Keep “required vs preferred” consistent across families.
  4. Pilot first:
    • Pick 1–2 families and complete end-to-end: skills library → mapping → user adoption in Growth Portfolio.
    • Validate downstream consumers (Recruiting/Learning/OMP) before scaling.
  5. Scale using bulk operations:
    • Use your available import/export tools for JPB entities (Families/Roles/Profiles).
    • For TIH entities, use your tenant’s supported bulk approach to scale Attributes Library updates cleanly.

F) Troubleshooting (common reasons users say “TIH is enabled but nothing works”)

  • Growth Portfolio not enabled (TIH enabled alone is not enough for adoption).
  • Permissions not assigned (admins can’t manage library; users can’t maintain attributes).
  • Duplicates and inconsistent naming (recommendations degrade and mapping becomes messy).
  • Teams still maintaining content in legacy screens instead of TIH-first maintenance.

4) How to create and update Families, Roles, and Job Profiles (step-by-step + bulk options)

Golden rule: Always build and maintain in this order: Family → Role → Job Profile.

4.1 Create / Update Job Families (UI + bulk creation)

What you’ll see in the current UI: When creating a Family, the system asks for Family Name, then lets you map Family Skills and Family Competencies. Many tenants do not show “Description” or “Status” fields on the create screen.

Common UI path: Admin Center → search Manage Job Profile Content → Select Content Type: Set Up Families and Roles → Families tab

A) Create a Family (UI)

  1. Go to Admin Center.
  2. In Action Search, open Manage Job Profile Content.
  3. From Select Content Type, choose Set Up Families and Roles.
  4. Go to the Families tab.
  5. Click Create Family.
  6. In Family Name, enter the Family name (use your naming convention; keep it stable).
  7. (Optional) Map Family Skills:
    1. Go to the Family Skills tab.
    2. Click Map Skills.
    3. Search and select the skills you want to apply to all Roles in this Family.
    4. Confirm mapping (and set proficiency if your UI prompts for it).
    5. Save.
  8. (Optional) Map Family Competencies:
    1. Go to the Family Competencies tab.
    2. Click Map Competencies (if available in your tenant).
    3. Select competencies you want to apply to all Roles in this Family.
    4. Save.
  9. Click Save Family (or equivalent) to finalize.

B) How to capture “Description / Scope Rules” when the UI doesn’t provide a field

If your Family create screen doesn’t have a Description box, you still need scope rules. Use one (or more) of these practical patterns:

  • Pattern 1: Naming convention (recommended for simplicity)
    • Example: ENG – Engineering, FIN – Finance, CS – Customer Success
    • Keep the prefix stable and documented in your governance sheet.
  • Pattern 2: “Family Definition” maintained as controlled documentation
    • Maintain a central “Job Architecture Dictionary” (one row per Family) with: scope rules, owner, last review date.
    • Reference that dictionary as your audit and operating model artifact.
  • Pattern 3: Store scope rules at the Role/Profile level (where text fields exist)
    • If your job profile template includes a “Role Purpose” or “Scope” section, store what belongs/doesn’t belong there and keep it workflow-approved.

C) Retire / Deactivate a Family (when there is no “Status” field on create)

Since many tenants don’t expose a status toggle at creation, retirement is handled operationally:

  1. Stop usage first: move Roles to the correct surviving Family (or retire roles) and ensure no new assignments depend on the Family.
  2. Remove broad mappings: remove Family-level skill/competency mappings (so it stops propagating content).
  3. Deactivate via admin tools: depending on tenant behavior, deactivation can be done:
    • Directly in Set Up Families and Roles (if your UI offers deactivate/inactivate actions), OR
    • Via Manage Data for the relevant JPB entity (commonly used where the UI doesn’t expose an “inactive” action).

D) Bulk create / bulk update Families (enterprise-ready)

  1. Go to Manage Job Profile Content Import/Export.
  2. Download the Family template (choose “Template with existing data” if you want to update existing families).
  3. Edit the file in Excel:
    • Add new families (leave system-generated IDs blank for new rows)
    • Adjust names only if absolutely required
    • Prepare a second file for bulk family-to-skill mapping if your template supports it
  4. Import the file back using the same tool.
  5. Validate in UI (spot-check at least 10 records + role linkage).

4.1A How to manage/create Skills for “Map Skills”

This is the missing piece: “Map Skills” only lets you search and select skills that already exist. You must first ensure a clean skill library exists, and you must control who can add new skills to avoid duplicates.

Important: In many customer landscapes, Skills are managed in the TIH Attributes Library (recommended) and then reused across JPB/TIH/OMP.

A) Create a Skill (recommended pattern: TIH Attributes Library)

Common UI path: Admin Center → search Manage Talent Intelligence Hub or Attributes Library → Skills

  1. Open the Attributes Library (or TIH admin area in your tenant).
  2. Select Skills.
  3. Click Create New.
  4. Enter:
    • Skill Name (approved name; no abbreviations as separate skills)
    • Description (what the skill means in your organization)
    • Category (technical, functional, leadership, etc.)
    • (Optional) Synonyms (managed as synonyms, not new skills)
  5. Save.

B) Bulk create / bulk update Skills

  • If your tenant provides import/export for attributes/skills:
    1. Export existing skills as a baseline template.
    2. Update in Excel (new skills, descriptions, categories, synonyms).
    3. Import back in controlled waves (start with top families first).
    4. Validate duplicates (naming and synonyms) before opening skills creation broadly.
  • If your tenant does not provide an import tool for skills, the practical approach is:
    • Create the initial top 50–150 skills manually (controlled admin group).
    • Scale via governance (new skill requests are approved and added centrally).

C) Skill governance (so “Map Skills” stays clean)

  • One approved name per skill (no duplicate spellings like PowerBI vs Power BI).
  • Synonyms are synonyms (not separate skills).
  • Proficiency model: use one enterprise model and publish definitions (Foundational/Working/Advanced/Expert).
  • Ownership: define who can create, approve, merge, and retire skills.

D) Now go back and Map Skills

  • Once skills exist, use Map Skills under Family/Role to search and assign them.
  • Recommended approach:
    • Map core skills at Family level (shared across roles)
    • Map role-specific skills at Role level (differentiators)
    • Keep proficiency expectations consistent and realistic

4.2 Create / Update Job Roles (UI steps + job code mapping + bulk options)

Common UI path: Admin Center → Manage Job Profile Content → Set Up Families and Roles → Roles tab

A) Create a Role (UI)

  1. Open Manage Job Profile Content → Set Up Families and Roles.
  2. Go to the Roles tab.
  3. Click Create Role.
  4. Enter required fields:
    • Role Name (capability-based, not team-based)
    • Family (select the Family you created)
  5. (Optional) Map Job Codes:
    1. Click Map Job Codes.
    2. Search and select the correct Job Code(s).
    3. Save mapping.
  6. Map role-level content (choose what your tenant supports):
    • Mapped Skills
    • Mapped Competencies
  7. Click Save Role.

A1) Map Talent Pools to a Role (this is not on the “Create Role” screen)

In the current UI, “Mapped Talent Pools” is typically available as a tab on the Role details after the Role is created/saved. This is why you don’t see it on the initial “Create Role” screen.

  1. Go to Manage Job Profile Content → Set Up Families and Roles.
  2. Open the Roles tab.
  3. Select the Role you want to update (open the Role details).
  4. Go to the Mapped Talent Pools tab.
  5. Click Map Talent Pools.
  6. Select one or more Talent Pools and save.

A2) How to create/manage Talent Pools (so they appear in “Map Talent Pools”)

“Map Talent Pools” only lets you select Talent Pools that already exist. You must first create the Talent Pools.

Option 1 (common): Admin Center → search Manage Talent Pools (if available)

  1. Open Manage Talent Pools.
  2. Click Create New.
  3. Enter:
    • Pool Name (stable naming convention)
    • Description (optional, but recommended)
  4. Save.

Option 2 (MDF path): Admin Center → Manage Data → search for the Talent Pool object

  1. Open Manage Data.
  2. Search for the Talent Pool object used in your tenant.
  3. Click Create New and maintain the Pool details.
  4. Save.

A3) Bulk create/bulk update Talent Pools and Role↔Talent Pool mapping

  • Bulk Talent Pool creation: if your Talent Pools are MDF-based and your tenant allows it, use Admin Center → Import and Export Data to export the Talent Pool object template and import in bulk.
  • Bulk mapping Role↔Talent Pools: if your tenant provides templates in Manage Job Profile Content Import/Export for Role mappings, use those templates. If not, handle mapping in waves through the Role UI and validate after each wave.

B) Update a Role (UI)

  1. Select the Role in the Roles list.
  2. Open it and update:
    • Job code mappings (add/remove codes carefully)
    • Role-level mapped skills/competencies
    • Mapped Talent Pools (Role details → Mapped Talent Pools tab → Map Talent Pools)
    • Role name changes only if essential
  3. Save.

C) Bulk create / bulk update Roles (enterprise)

  1. Go to Manage Job Profile Content Import/Export.
  2. Download templates for Roles and mapping files (Role ↔ Job Code, Role ↔ Skills/Competencies).
  3. Update in Excel and import in controlled waves (family-by-family).
  4. Validate mappings and propagation using spot checks.

4.3 Create / Update Job Profiles (UI steps + workflow + bulk options)

Common UI path: Admin Center → Manage Job Profiles

A) Create a Job Profile (UI)

  1. Open Manage Job Profiles.
  2. Click Create New.
  3. Choose the correct Job Profile Template.
  4. Associate it correctly (based on your design):
    • Role-based profile: select the Job Role
    • Role + Position-based profile: use only where intentionally differentiated
  5. Populate required sections:
    • Purpose
    • Responsibilities
    • Required Skills
    • Preferred Skills
    • Competencies
    • Education/Certifications
  6. Save as Draft and submit for approval (if workflow is enabled).

B) Update a Job Profile (UI – safe change pattern)

  1. Open the Job Profile in Manage Job Profiles.
  2. Choose Edit or Create Draft.
  3. Update only what changed.
  4. Submit for approval → Activate when approved.

C) Bulk create / bulk update Job Profiles (enterprise release model)

  1. Go to Manage Job Profile Content Import/Export.
  2. Download the Job Profile template (with existing data if updating).
  3. Update in Excel and import in waves.
  4. Post-import validation checklist:
    • Profiles linked to correct roles
    • Mandatory sections populated
    • No accidental duplicates created

5) How to make JPB ready for TIH (what migrates vs what must be redesigned)

Key mindset: JPB remains your structured job foundation. TIH becomes your scalable attributes layer. If you “lift and shift” messy skills into TIH, you will multiply duplicates and reduce trust in recommendations.

5.1 What typically migrates well

  • Families and Roles (after de-duplication and stable naming)
  • Core profile structure (purpose, responsibilities, education/certifications) after template standardization
  • Role-to-job-code mappings (after cleanup)

5.2 What must be redesigned for TIH (do not blindly migrate)

  • Skills taxonomy (normalize, de-duplicate, govern synonyms)
  • Proficiency model (one model enterprise-wide)
  • Ownership model (who creates, approves, merges, retires skills)
  • Attribute policy (skills vs tools vs certifications vs interests)

5.3 TIH-ready sequencing

  1. De-duplicate Roles
  2. Standardize templates
  3. Normalize skills and governance
  4. Map role-to-skills in waves
  5. Adoption plan for Growth Portfolio
  6. Measure and tune continuously

6) Operating model (how to keep JPB accurate for years)

  • Monthly: recruiting blockers and urgent profile fixes.
  • Quarterly: dedupe roles, normalize skills, level alignment, quality checks.
  • Biannual: strategic refresh aligned to transformation programs, AI shifts, compliance changes.

7) Final checklist

  • JPB enabled + correct RBP roles configured
  • Object security configured (Job Profile, Skill Profile, Rated Skills)
  • Workflow enabled and enforced
  • Families/Roles built with stable naming + job code mappings
  • Profiles linked to roles and maintained in controlled releases
  • Skills are created/managed centrally and then mapped using Map Skills
  • Mapped Talent Pools are configured from Role details (Mapped Talent Pools tab) and Talent Pools are created first
  • CoC → JPB and CoC → TIH path is understood and planned (migration + governance + adoption)
  • TIH readiness executed in two phases: foundation cleanup + skills redesign

Closing thought: If you want skills-based talent programs and AI-driven recommendations to be trusted, govern JPB like finance master data: clean inputs, controlled changes, disciplined lifecycle.

No comments:

Post a Comment