Hi all, well as you all will no doubt appreciate, I am not overly blessed with knowledge around this particular application, but some strange things have been happening with this table.

There appear to be certain situations (the details of which are not yet fully known) where some process or other just updates the last_updated_by and last_update_login for a large number of rows. The user who is shown as the last_update_by vehemently denies all knowledge, and indeed the responsibility is not one that would normally allow him or her access to that kind of data.

Furthermore, the last update login id, when one looks at fnd_logins, looks like it is 'concurrent' however there are no concurrent jobs that bear that login id.

So, my question is this: what other non-human interaction besides a concurrent job, would give rise to a login_id.

If I could get some kind of steer as to how else a background process could be initiated, I might be on the way to resolving this little problem.

It's not a show-stopper, and to be fair if it were not for a recent change to some reports that now show 'last updated by' in the details for these enrolments, people would have been none the wiser.

Nothing in Metalink of course, so anyone else out there seen this before? Any clues would be voraciously seized upon.

Hi CT,

I often use the following sql to find all concurrent processes running at the last update timestamp:

select
prog.user_concurrent_program_name
,req.request_id
,to_char(req.actual_start_date ,'Dy dd-Mon-rrrr hh24:mi:ss') start_time
,to_char(req.actual_completion_date,'Dy dd-Mon-rrrr hh24:mi:ss') end_time
from
applsys.fnd_concurrent_programs_tl prog
,applsys.fnd_concurrent_requests req
where prog.concurrent_program_id = req.concurrent_program_id
and to_date('29-Aug-2013 15:39:00','dd-Mon-rrrr hh24:mi:ss')
;

where 29-Aug-2013 15:39:00 is the last update time.

Hopefully it will return a culprit process.

Thanks Pat, however I've already run various scripts to try and reveal conc requests without success.

Cheers anyway

Figured you would have tried more than just the one script but hoped it would help.

The only other thing I can think of is could there be an Alert scheduled that isn't being picked up by your scripts.