Video summary

SAP SuccessFactors Training | SAP SuccessFactors course | SAP SuccessFactors Tutorial | CyberBrainer

Main summary

Key takeaways

Technology

Overview: What SAP SuccessFactors is

  • SAP SuccessFactors is presented as a cloud-based HR platform.
  • It supports:
    • People analytics
    • Basic HR management
    • Modular / “modified” HR solutions
  • It also includes performance management and in-depth performance evaluations, such as:
    • Allowing staff to track progress
    • Identifying improvement opportunities

The video frames the content as guidance for understanding the platform and how to work with it in real implementation/support contexts.

Learning series / tutorial structure

The speaker frames the material as an online training series (CyberBrainer) with a planned scope that includes:

  1. Introduction to Mastery (setup and consultant readiness)
  2. Admin Center settings
  3. Create user and template
  4. Corporate model and business configuration
  5. Permission groups
  6. Manage MDF object / employee data
  7. Workflow and events
  8. Business rules overview
  9. (Plus) concepts like create/manage workflow group

Tech/product concepts covered: architecture, environments, access

1) Cloud vs on-prem & SAP licensing model

  • SuccessFactors is cloud technology:
    • After purchasing/subscribing from SAP, the customer receives server space in SAP data centers.
  • Contrast with on-prem ERP:
    • Servers are hosted at the customer site.

2) SAP SuccessFactors partner/implementation model

  • Customers typically do not implement independently.
  • They engage SAP partner companies (SAP-associated consultants).
  • Partner responsibilities include:
    • Consulting
    • Implementation/support/upgrade delivery
    • Gathering customer requirements, such as:
      • Selected modules
      • Countries/regions
      • Team size
      • On-site vs off-shore needs
      • Contract details
  • Consultant resources may come from:
    • Bench/internal availability
    • Recruitment

3) Front-end vs back-end systems (Instant vs Provisioning)

The architecture is split into two systems:

  • Front end (“Instant” system) Used for consultants/customers to configure and work via the UI.

  • Back end (“Provisioning” system) Used for features/enablement that require SAP-side permission.

Key point:

  • A customer cannot directly grant back-end (Provisioning) access.
  • Provisioning access requires an approval email process via SAP.

Environments: Development / Preview (Quality) / Production

Main environments

The video describes three main environments:

  • Development
  • Preview / Quality (used for UAT—user acceptance testing)
  • Production (live system)

All environments are hosted within the same data center for a given tenant/subscription.

Deployment flow (described)

  • Configure & test in Development
  • Move to Preview for key user / UAT
  • Promote to Production after approval

Environment accounts & identifiers

Each environment has:

  • A unique URL
  • A company ID
  • Environment-specific username/password mappings

The speaker emphasizes synchronization:

  • Front-end and back-end changes must reflect correctly across aligned parts of the landscape.

How to tell which environment you’re on

The video highlights three ways:

  1. URL pattern (production vs preview indicators; preview URLs show data-center-related numbers)
  2. Company ID mapping differences across dev/preview/prod
  3. Company logo / label under the logo (naming makes test/dev/preview vs production visible)

Access workflow for consultants: implementation vs support

Implementation scenario (tutorial-like flow)

In implementation, a consultant may initially not have front-end access. The process described:

  1. Obtain approval email from the customer for Provisioning access (dev/preview/prod as needed)
  2. Raise the request to SAP
  3. SAP sends access/communication emails (separate per environment)
  4. Use the provided link + credentials to access Provisioning
  5. Inside Provisioning, use “Create Admin” to set up initial front-end/admin access
  6. Access the Instant (front-end) instances via the instance URL

Important note:

  • Front-end may start blank during implementation, since enabling features/configuration must happen provisioning-first.

Support scenario

  • In support projects, the landscape is already established.
  • A super admin exists and:
    • Creates profiles/permissions for consultants in the front-end
    • Shares credentials

Training & certification platform mechanics (SAP Training Hub)

The video includes a certification tutorial workflow:

  • Register via training.sap.com
  • For partner employees: obtain an internal Certification Hub voucher
  • For others: purchase the certification voucher on training.sap.com
  • Voucher validity: one year
  • Choose the correct module examination code
  • Book and take the exam; after passing, receive a P-user ID

User ID mapping concept

  • P-user ID: identity for the exam (external/personal registration)
  • Partner coordination maps it to an S-user ID linked to the company and official email
  • SAP then sends instructions to reset password
  • S-user ID + reset password is used to access provisioning/instances

Navigation/UI concepts inside SuccessFactors (overview for admins/consultants)

New homepage & SAP releases

  • The speaker mentions a new homepage (the previous one is described as deprecated/removed).
  • “Show version information” includes:
    • Company ID
    • Release number
  • Releases occur twice per year:
    • 1H (around April/May)
    • 2H (around October/November)
  • Example releases referenced: B221, followed by 2305

Homepage sections & tiles

Typical homepage areas:

  • Approvals
  • Organization updates
  • Notifications/alerts, including:
    • Manager/employee approvals
    • Contract end alerts
    • Leave requests
    • Salary-related items
    • Birthdays

Tiles/widgets may be:

  • Standard
  • or custom tiles configurable per customer needs

Global search vs configuration tools (and T-codes concept)

Global search can search:

  • Employee directory entries (active/inactive)
  • Configuration tools (note: SuccessFactors uses configuration tools rather than classic SAP HR “T-codes”)

Beginner note:

  • Early on, navigation may be needed.
  • Later, users can search tools they already know.

Admin Center as the entry point for configuration

  • Admin users enter:

    • Admin Center → Tools → configuration tools (examples mentioned: employee/company settings, calibration, performance, compensation-related tools)

  • Permissions determine what a key user can access:

    • Key users typically access only role-relevant areas (e.g., performance or compensation pages)
    • Other configuration tasks are handled by admins/consultants, often via tickets/requests routed to product owners

Main speakers / sources (as stated in the subtitles)

  • CyberBrainer (online training platform/channel)
  • The primary speaker is a trainer/consultant (names referenced in passing: Rahul and Hima, though the subtitles do not clearly confirm them as the main speaker; the instructional speaker appears to be the narrator/trainer).

Original video