-
1. Re: Problem with "user data detail"
1 person found this helpfulSupanut,
See the processor help here:
http://www.oracle.com/webfolder/technetwork/data-quality/edqhelp/index.htm
The details are only added when used in a real time [i.e. web services] call or run as part of a job.
regards,
Nick
-
2. Re: Problem with "user data detail"
Thank you for your helpful reply.
I make a test and it is really as you and the help file stated.
It is working on realtime data input.
If you would be kind to help me more,
My destination data table has a field named "UPDATE_USER" to record name of who put or update the data.
Are there anyway to link EDQ username to be put in the output data so that non EDQ user know which of the edq user put the data in?
-
3. Re: Problem with "user data detail"
1 person found this helpfulHi,
If you're talking about writing the EDQ data back to a database table then you need to read the help topic on Exports.
regards,
Nick
-
4. Re: Problem with "user data detail"
thanks again
I forgot to mention that the input data is non-real time and the problem that I currently have is to aqquire the username from EDQ user since from what i understand "User data detail" only work on real time data. I have no problem writting data back to the database.
regards,
T
-
5. Re: Problem with "user data detail"
Yes, this processor is specifically designed for real-time mode. The username that invoked a batch job is stored in the event log [which can be snapshotted - see System Information - Event log data store] but it's not easy to add this to batch data [as this would require some post-processing to do the lookup].
-
6. Re: Problem with "user data detail"
Batch jobs that write data to external targets are normally run from a schedule by a system user (with rights to execute batch jobs) in any case, rather than by a specific 'user' who is logged into EDQ. Depending on your use case, it might therefore be that you need to identify the update as from EDQ rather than from anyone specific?