Can you please expand on why you want this and what the purpose is. How you see this? If something is changed, where does the "audit" have to go to?
I just want keep a track of all the data being updated through tabular form and then create a Audit report based on it.
Can you please suggest how to capture the data being updated ?
But why wouldn't you capture this data on an after-row trigger on the table? Why would you do this on the front-end?
If you are on at least 184.108.40.206 there is also the nowadays free option of using flashback archive.
I personally would vote against client side logic, let the database do what it does best: "Manage Data".
Documentation Links are always helpful: Using Oracle Flashback Technology
Oracle's Flashback technology should definitely be used.
However, depending on the true needs of the OP, archiving the "audit trail" using Flashback Data Archive may not be needed.
The "SELECT ... AS OF.." and "SELECT .. VERSIONS BETWEEN..." will work without "ALTER TABLE ... FLASHBACK ARCHIVE" for a small period of time.