IFS Audit Trail Capability

If nothing else you could create an Event to create a log of the first 2 items, triggered when rows are added to the underlying tables.  Not sure about #3

FndEventAction and QuickReport are both available to log through History Configuration.

Note however that you won’t be able to log anything to do with the actual CONTENTS of said Reports/Event Actions (i.e. PL/SQL Code being changed for instance), because those fields are saved as CLOB rather than VARCHAR2 (this is to overcome the 4000 characters limit of Varchar2), and History Configuration is not compatible with CLOB/BLOB fields :)

For number 3, you can log Event Action ERRORS, but I don’t believe you can log executions out of the box.

You’d need each event action to log itself executing (probably as a pragma autonomous_transaction if you want the log to persist even if the event ends up in a rollback, by writing to a custom table you’d have created to store that data) if you really need to trace event executions.

​@SimonTestard 

​@NickPorter 

appreciate both inputs here.

​@SimonTestard 

the screenshot you took is from IFS Cloud version, correct?

I really cannot find them in IEE/Aurena (APP10).

Thank you.

History Log and Server Log features have been available since IFS75 version.

​

In Apps 10 if I’m not mistaken, you can only find it in IEE under History, I can’t find an entry for it for Aurena.

Note that you’ll need to Right Mouse Button and tick “Show Foundation1 Component” in order for things in FNDBAS (such as fnd_event_action_tab) to show up

​