Minimum Required Fields for SuccessFactors ↔ ServiceNow SAM Integration

[iamkurt]

Hi everyone,

We’re currently integrating SAP SuccessFactors with ServiceNow Software Asset Management Pro (SAM Pro) in our DEV environment to track software compliance and manage subscriptions.

We followed the official documentation: 🔗ServiceNow ↔ SuccessFactors Integration Guide

After publishing the integration profile and executing the jobs, no software subscriptions were downloaded. On further inspection, the subflow "SuccessFactors Download Subscriptions" includes a "look up Users" action that references Microsoft AD Spoke, which seems unrelated.

We also realized that we need Email ID and User ID for this integration to work. 

To move forward, I need to build a business case and provide our SAP team with a clear list of minimum required fields for the integration.

Here’s the current list we’ve received:

userId, username, defaultFullName, firstName, lastName, gender, email, city, state, nationality, country, businessPhone, status, timeZone, title, hireDate, dateOfBirth, zipCode

We are particularly concerned about PII fields like dateOfBirth and gender. Can anyone confirm:

1) Are these fields strictly required for the integration to work?

2) What are the bare minimum fields needed to make this integration work?

3) Has anyone successfully implemented this integration with a reduced field set?

Just to add more clarity to our setup:

Our SAP SuccessFactors team enforces Roles Based Permission (RBP). As per ServiceNow documentation, they do not grant admin access to ServiceNow personas. Instead, they assign specific roles to these personas, which control what data can be accessed via the API.

Given this, we’re trying to understand:

Which specific fields should be included in the SAP role so that ServiceNow SAM Pro can perform key activities like:

• Software subscription reconciliation
• Compliance tracking
• License usage analysis

We want to avoid pulling unnecessary PII fields unless absolutely required (e.g., dateOfBirth, gender). Any guidance on the minimum viable field set for SAM functionality would be extremely helpful.

Any insights or experiences would be greatly appreciated!