Is it safe to deactivate sn_hr_core.hr_Utils Script Include when HRSD is not used?

[21p31a1220]

Our instance has HR Core / HRSD plugins installed, but HR Service Delivery is not implemented or used. We are seeing HR Profile synchronization between sys_user and sn_hr_core_profile, and noticed that the sn_hr_core.hr_Utils Script Include is referenced by HR-related Business Rules.

Could someone please clarify:

• Is it safe to deactivate sn_hr_core.hr_Utils when HRSD is not used?
• Does this Script Include impact any non‑HR modules?
• Are there upgrade or patch risks if it is deactivated?
• What is the supported way to stop all HR Profile–related processing when HRSD is out of scope?

Thanks in advance.

[pr8172510 · Accepted solution]

Hi,

 no, it’s not recommended to deactivate sn_hr_core.hr_Utils, even if you’re not actively using HRSD.

---

Why you shouldn’t deactivate it

• It’s a core Script Include delivered with HR Core
• It is referenced by multiple OOTB Business Rules and processes (like HR Profile sync)
• Deactivating it can lead to:
  • Script errors
  • Unexpected behavior during upgrades
  • Broken dependencies that are not immediately visible

Also, some logic may still be indirectly used even if HRSD is not fully implemented.

---

Does it impact non-HR modules?

Generally:

• It’s primarily scoped to HR
• But since it interacts with sys_user and profile data, it can have side effects beyond pure HR use cases

---

Upgrade / patch risk

Yes — high risk:

• OOTB components are expected to be active
• Future upgrades may assume this Script Include is available
• You could run into upgrade conflicts or skipped logic

---

Recommended approach (supported)

Instead of deactivating the Script Include, you should:

1. Disable related Business Rules

Identify HR sync rules like:

• HR Profile creation/update
• Sync between sys_user and sn_hr_core_profile

Then:

• Deactivate or conditionally restrict those Business Rules

---

2. Add conditions instead of removing logic

Safer approach:

• Add conditions (e.g., check if HR is in use)
• Prevent execution without removing OOTB components

---

3. Restrict via properties (if applicable)

Check if there are system properties controlling:

• HR profile sync
• HR integrations

(Some behavior can be toggled this way depending on version)

[Ankur Bawiskar]

@21p31a1220 

so is the sync happening from User -> HR Profile currently?

[21p31a1220]

Yes, Its happening vice‑versa