Control Character In Data Causes PERSON_BASIC_SYNC To Fail Without Error
Last updated on FEBRUARY 14, 2018
Applies to:PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
PERSON record being synced from Campus Solutions to HCM with the PERSON_BASIC_SYNC service operation did not get created, but the service operation did not get an error. The BIRTHPLACE field contained a backspace control character that was introduced by a bad data load, and it caused the message to come over with PsNonXml="Yes". Loading the record in a test environment with tracing turned on, it was observed that the message handler could not determine the value of PSCAMA.AUDIT_ACTN
The message should either function regardless of unexpected character or should at least generate an error message explaining the issue
The issue can be reproduced at will with the following steps:
1. Load data into system that includes text code of a control character
2. Integrate PERSON_BASIC_SYNC from CS to HCM
3. In message information, note PsNonXml="Yes"
4. No error message, but trace indicates PSCAMA.AUDIT_ACTN issue
The initial data load that included a control character was generated from a 3rd party. Issue would normally be blocked by validation in PeopleSoft
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms