My Oracle Support Banner

PERSON_SYNC Message From HR To FIN Does Not Populate The SMOKER Field (Doc ID 2312865.1)

Last updated on SEPTEMBER 26, 2019

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 and later
Information in this document applies to any platform.


1) Having hired an Employee in HRMS environment, PERSON_BASIC_SYNC message gets triggered, and the XML message is sent to FSCM with SMOKER and SMOKER_DT values. The SMOKER and SMOKER_DT values in FSCM PERSON_BASIC_SYNC XML message. However, the PERSON_BASIC_SYNC at Finance does not have the field SMOKER_DT to capture the value from XML.

2) Furthermore, if the User adds a new row in HRMS environment with a change in SMOKER, and SMOKER_DT fields, and also modified PERSONAL_PHONE number, the resulting outcome in FSCM systems is that the PS_PERSONAL_DATA Record reflects the latest PERSONAL_PHONE number, but the SMOKER values were not present.

3) The problem occurs when the SMOKER_DT field is not populated in HRMS. When a change is made to that person, the SYNC message does not contain the SMOKER filed value. When that updates the PS_PERSONAL_DATA record in FSCM, it will delete any value in the SMOKER field. That is when Users get a problem with the system sending an email because the SMOKER field is not populated.

4) So the issue is caused by the message from HRMS to FSCM not containing a value for SMOKER when SMOKER_DT field is null.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.