New Hire Import- Data Not Populating Into Pending Worker Fields
(Doc ID 2081302.1)
Last updated on MARCH 08, 2017
Applies to:Oracle Fusion Global Human Resources Cloud Service - Version 220.127.116.11.0 and later
Information in this document applies to any platform.
On : 18.104.22.168.0 version, Taleo Integration
When importing new hires into Fusion from Taleo, the Postcode comes through if the letters are Uppercase and in the right format. E.g. M1 5AN
The postcode is blocked if it’s in uppercase and the wrong format. E.g. PM1 P56
The postcode is blocked if it’s in lower case and in the wrong format e.g. m1 mh6
The postcode is blocked if it’s in lower case and in the right format: cm1 4hg
In Fusion > FSM > Manage Address Formats > you can select UK and make Post Code mandatory. This is what has been done but there is also an option for 'Uppercase'. This has been de-selected.
The behavior customer expects is that during the convert worker process the Post Code is displayed as it was entered in Taleo and if it is invalid then it should error when 'Next' is clicked or if that field is selected.
This would then allow the user to update the information. At the moment an invalid post code is blank, so the user is unable to re-enter anything.
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|