Afternoon all
Just in case anyone else meets this in the future:
Here at W-D we are experiencing some local unpleasantness with trying to load employees. Some of our recently employed bretheren are being rejected because 'The NI Number prefix is invalid.'.
These days of course, the NI number validation is all growed up - in that it checks the 2 letter prefix against a seeded lookup list of allowable values (lookup code = 'GB_NI_VALIDATION_PREFIX'). It seems that most of the prefixes have a start date of 06/04/2004. There are some new ones e.g. 'SG' that start on 06/04/2005. It would seem reasonable to assume then that the Revenue boys are issuing new prefixes year on year.
The interesting thing about this is that the checking of that lookup is encapsulated within a Fast*Ha*Fin*Ha*Formula called rather predictably NI_VALIDATION.
First thing this formula does is set a default for the session date of '06/04/2004'. Can you see where this is going? Yes, the absence of any session date (EG WHERE WE DARE TO RUN THIS FROM A NAFFING DATA PUMP SESSION FOR GOD'S SAKE!) means the default will apply - fine for most of the 'old' prefixes, but sadly for 'SG' and others starting after 06/04/2004, means the validation of the NI number, and therefore the loading of the employee, is doomed to failure. Seeded formula means we can't change it, 'System' type look-up means we can't alter the start dates of the affected prefixes, shat D-P means we can't set a session date other than by another bunch of user-hooks or we encapsulate the create employee api in our own api wrapper complete with session-date setup, and then DP-enable that.
Happy days! <img src="/ubbthreads/images/graemlins/Flush.gif" alt="" />
_________________________
L&K
CT
Remember: A dog is for life, not just for Christmas... unless you're in Korea