Thrive and SAP SuccessFactors Integration

Prev Next

Thrive and SAP SuccessFactors Integration allows you to create a unified learning experience by letting users access and complete their formal SAP training directly from Thrive. This guide details how mandatory assignments, learning records, and certificates are synced between both platforms, ensuring all learning is tracked accurately and intuitively for every user.

Integration Features

  • SAP Assignments in Thrive: Thrive automatically receives and displays all SAP SuccessFactors learning items, programmes, and surveys, including the item's title, due date, and whether it's required. This ensures users are aware of their formal training obligations in one place.

  • SAP Assigned Content: Learners can launch SAP-mastered content directly from Thrive. Using a deep link, Thrive acts as a primary hub for all your learning, seamlessly navigating you to the SAP platform to consume the content.

  • Completion Tracking: All learning completions on SAP SuccessFactors are accurately recorded and reflected in a user's Thrive learning history.

  • SAP Catalogue Discoverability: The SAP SuccessFactors content catalogue is surfaced in Thrive, making content discoverable to Kiki and all users. Thrive presents this as link-based content with titles and metadata, but access is controlled entirely by SAP's catalogue permissions. Thrive reflects the catalogue as provided by SAP without replicating its entitlement logic.

  • Unified Assignment View: SAP assignments (including titles, thumbnails, and due dates) automatically sync to Thrive and appear as Assigned Learning.

  • Direct Content Launch: Users can launch SAP content via deep links on content cards. On mobile, this opens an in-app browser that bypasses SAP's "view in app" prompts.

  • Enhanced Content Discoverability: Full SAP catalog integration with a 12,000-character free-text metadata field. This ensures SAP content is searchable and optimized for Kiki (AI Assistant).

  • Automated Completion Sync: Learning history and statuses sync from SAP to Thrive hourly for active users and daily for others.

  • Instant Certificates: Direct links to SAP-hosted certificates are available in Thrive immediately upon completion.

Prerequisites

  • User Provisioning: When a user is provisioned in Thrive, their SAP SuccessFactors user ID or staff ID will be available to Thrive.

  • Notification Cadence: Notifications for assigned learning will align with internal Thrive assignments. This includes notifications sent at the point of assignment and then at 28, 21, 14, 7, 1, and 0 days before the due date. Overdue assignment notifications will be sent weekly for 12 weeks after the due date.

Future Developments

The following features are not part of the current integration but are planned for a future release:

  • Thrive Content in SAP: The ability to log completions for Thrive-mastered content directly within SAP SuccessFactors is planned for a later phase.

  • SAP Assignment Administration: We will introduce the ability to administer SAP assignments directly from within the Thrive platform.

Frequently Asked Questions (FAQs)

What information is ingested into Thrive from SAP SuccessFactors?

Thrive ingests the following:

  • Learning that has been assigned to a particular user in SAP - aka ‘assignments’ - provided that this user also exists in Thrive

  • Learning that has been completed by a particular user in SAP - aka ‘completions’ - provided that this user also exists in Thrive

  • Content that is present in the SAP content catalogue

How often does the synchronisation happen between Thrive and SAP SuccessFactors?

Thrive currently runs 2 automated regular syncing processes:

  • The first runs every day during the early hours of the morning and picks up any changes that have occurred within the preceding 24hrs for user Assigned Learning, user Completed Learning, or Content available within Success Factors.

  • The second runs every hour of the day but only picks up changes that have occurred within the last hour, and only for users that have logged into Thrive during the last hour. E.g. if a user logged into Thrive at 09:25 and then completed a piece of SAP Success Factors learning, Thrive would update that Completion at 10:00 when the hourly sync job runs. Note: the hourly job is only for assigned learning and completed learning, it does not exist for general Content ingestion - that is a daily job only.

The difference between the 2 jobs is the first picks up all changes for any user within the last 24hrs, the second only picks up changes for ‘active’ users that have logged into Thrive within the last hour.

How is content displayed within Thrive?

Content that is ingested from SAP SuccessFactors takes the form of ‘link’ content in Thrive. Tags on content can be created automatically as part of the ingested process - for example the domainId can be turned into a tag on the content item which then allows this to be surfaced in specific places in Thrive based on rules/logic. Additionally we take the itemId , description , and targetAudience from SAP and concatenate these into a user friendly description of the content in Thrive. This is useful for discoverability by users of the platform, either using our search functionality, or via our AI Assistant (Kiki).

Are there any pre-requisites I need to be aware of?

Yes, there are a few things to consider when setting up a sync between SAP SuccessFactors and Thrive, these are:

  • Users must be present in both SAP and in Thrive for assigned learning and completed learning to be corrected ingested and reflected in Thrive. The user’s Person ID in SAP must match their ref within Thrive for the syncs to work correctly.

  • Thrive must have access to both the SAP API (for the hourly synchronisation) and a means by which to securely receive exported files from SAP’s report scheduling tool (for the daily sync) - e.g. an SFTP location to extract the files from. Without both of these in place, we’re unable to receive the data necessary.

  • Historic data loading will need to handled via a one-off process because the daily and hourly sync jobs only include changes from the past 24hrs and 1hr respectively.