Formal Name is displayed wrong on the Personal Information or wrong values are passed to Offboarding on termination
SuccessFactors - Employee Central
- In the Succession Data Model, enable the formal-name, set the visibility to be "both", give all the permissions for RBP.
- if set the visibility to be "view", give the view permission only, then it just can't be changed from UI.
System determines the formal Name of the employee based on the Logic Defined below.
If target user doesn’t have job info, then set formal-name as the hard coded formal name (firstName + middleName + lastName), and set the IsOverridden flag to be false(0). -> End
If target user has job info, go to Step2.
If target user has job info record, get Job Information record as of personal information’s effective start date.
- If there is formal-name change between database value and to-be-saved value, set formal-name as the value in request, and set isOverriden flag to be true(1).-> End
- If there is no formal-name change between database value and to-be-saved value, check database's EO's(previous record's)isOverriden flag. if previous record's isOverriden=null, then go to step3; if previous record's isOverriden is true, then return the to-be saved formal name, and set isOverriden flag to be true(1); if isOverriden flag is false,
then go to Step3.
Get Legal Entity from target user’s Job Information. Get Legal Entity record as of Personal Information’s effective start date.
-If NameFormat is not configured in Legal Entity and name format code is null, then set formal-name as default Name Format which is hard coded as firstName + middleName + lastName, and set isOverriden to be false
-If NameFormat is configured in Legal Entity, go to Step4
Get Legal Entity record as of personal information’s effective start date. Get NameFormat based on legal entity record’s association, set isOverriden to be false(0).
-If NameFormat GO record doesn’t exist, then set formal-name the default nameformat(firstName + middleName + lastName)
-If NameFormat is configured as one to one association in Legal Entity definition, and set NameFormat value in Legal Entity data
-If NameFormat is configured as one to many association in Legal Entity definition, and set NameFormat value in Legal Entity data. Always use the first NameFormat configured in Legal Entity. Then use the same logic as point 2.
NameFormat, Formal Name, formal-name, Personal Information, LOD-SF-EC-PER, PER , KBA , LOD-SF-EC-PER , Personal & Global Information , LOD-SF-EC-INT , Suite Integration (Manage Pending Hires RCM, ONB, Drafts) , Problem