Hi All, I am building a people connector for SAP SuccessFactors and am running into countless issues where Reference codes and the data structure aligns exactly correct with the sy

Originally replied by Frank Ruffolo on Jul 21, 2026, 10:05 AM.

Hey Shane, I'm assuming you know all of this but I'll simplify it because sometimes it helps me explain it and sometimes shines a light on small things but this is how I see it:

1. Job XRefCode comes from here (your "7"):

   1. 

       

2. The Dept XRefCode comes from here (your "6"):

   1. 

       

3. The Location comes from here (your "500Operations") and make sure its where Physical Location is checked:

   1. 

       

4. Make sure there is a record under the job (which is the Position and ignore the XrefCode at this step) but make sure the Dept shows up here (your "500Operations" which may show up as Shortname), this marries the Job/Dept in the configuration:

   1. 

       

Let me know if this helps.

Originally replied by Shane Zahra on Jul 23, 2026, 11:20 PM.

Hi Frank, Thanks for confirming the areas relating to the API. That aligns perfectly with all my test cases. Are you aware of any specific access/permissions that could be causing this issue?

Originally replied by Frank Ruffolo on Jul 24, 2026, 9:35 AM.

Hey Shane, permission-wise just confirm you have:

1. Features: HCM Anywhere └─ Web Services └─ Patch/Post Employee HR Data
2. Authorizations:
   1. Employee Work Assignment - Primary — required for the employee’s primary assignment
   2. Employee Work Assignment — required for secondary/non-primary assignments; enabling both is safest
3. User Access:
   1. System Admin └─ User └─ Find the integration user └─ Location Access and make sure it has a location (for testing use the top of the Org).

Let me know how it goes.

Originally replied by Shane Zahra on Jul 29, 2026, 8:24 PM.

Thanks for your help, Frank, I have checked all these permissions on the SF user that's involved in the connector. Still no luck.

Originally replied by Shane Zahra on Jul 29, 2026, 10:16 PM.

FYI, we identified the root cause behind this issue being the LoginId being statically set. Setting this field to SF employee id resolved the issue. The connector was incrementing a 1,2,3 on each attempt. All mappings were correct. Very tricky one!

Originally replied by Frank Ruffolo on Jul 30, 2026, 8:35 AM.

Hey @Shane Zahra​, that's very weird I almost don't think I am following 🙂 Just a weird error considering the LoginId fixed it