Security Software

Like many of you know IdM projects are often rooted in analysis and not implementation (as much). As part of that I'm creating a matrix of OIM Profile (form) Fields and\or DB columns (mostly USR) - including name, isvalidated, isrequired, format, length, defaults, values, etc. Then the next step is to do the same with the resources (AD, LDAP, DB, etc). Then that analysis becomes the basis to determine what gets "pushed up" to the OIM profile, who should be the 'authoritative source', etc. I know this is a very common approach and one that Oracle even uses on many of it's OIM consulting gigs. Any comments on this approach is appreciated.

But what I'm most interested in is any insight people can share about these following OIM Fields\DB Columns:

1. USR.USR_CREATED, USR.USR_UPDATED - is that technically set to be SYSDATE (of the DB) upon insert\update? Opposed to likely defining a new Date() in the java. Is this true of all the DATE related columns? Are the DATE fields validated (OOB) so that they cannot occur in the past?
2. USR.USR_MANAGER vs USR.USR_MANAGER_KEY - Are these both references to the same thing? If so, why is this needed?
3. USR.USR_DATA_LEVEL - what\when is it used?
4. USR.USR_FSS - what\when is it used?
5. USR_LOCATION - what\when is it used?
6. USR_NOTE - what\when is it used?
7. USR_PWD_MIN_AGE_DATE - is that used to not allow people to change the password until after X many days? Or is more about finding the LCD password interval across all the resources & OIM?
8. USR_UPDATE_AD - Is this used for AD? If so, why isn't it prefixed with UDF?
9. USR_TODO - is this just there in case Oracle wants to add a field in the future? Or is actually used currently?