Issue: Missing Personnel Area (PA) Codes for Contractors Causing Request Failures

[ab_frostbite]

Issue: Missing Personnel Area (PA) Codes for Contractors Causing Request Failures

Hi Team,

A few weeks ago, a fix was implemented to address missing Personnel Area (PA) codes for contractor users in ServiceNow. This helped resolve issues where users could not be correctly identified in approval workflows.

However, the issue appears to have reoccurred. We are again seeing users with empty PA codes, which is causing request failures in ServiceNow.

Example:

• Contractor user record missing PA code (multiple occurrences identified)

Impact:

• Approval workflows are failing because users cannot be properly identified
• Requests are not progressing as expected

Ask:

1. Can someone run a check to identify all users with missing or empty Personnel Area (PA) codes in ServiceNow?
2. What could be the root cause of this issue reoccurring (e.g., upstream HR data feed issue, integration/mapping logic, or data sync gaps)?
3. What is the recommended remediation approach to:
   • Fix existing impacted users
   • Prevent recurrence going forward

Any insights, similar experiences, or recommended solutions would be greatly appreciated.

Thanks in advance!

[Tanushree Maiti]

Hi @ab_frostbite ,

• If the data is being imported through a transform map, make sure the transform map is configured to prevent empty inbound values from overwriting existing ServiceNow profile data.
• In the field map, map the field only when the source value contains data and is not empty.
• Review the coalesce fields on the user table to confirm updates are matched correctly and do not result in unintended blank values.