Larry_Jones
Legendary Poster
You're welcome Rosco, and - for the group - I'll apologize if we seem a little "defensive" about the subject of auditing and controls. SARBOX as implemented in many companies has made it frustrating for administrators to do their jobs - not an excuse but an explanation.
A bit more on the database side. While I haven't read the document Colin refers to I would not be surprised if some companies database security is non-existent. Its not hard to change this but I'll bet that some never do.
Re auditing changes - at my company we use database triggers to log changes to key documents/items (orders, items, ...). The audit tables themselves though read-only are described in JDE as tables and have inquiry applications linked to the relevant JDE apps. So if you need to see who changed the G/L Class on a Item and when they did it its very simple to find.
A bit more on the database side. While I haven't read the document Colin refers to I would not be surprised if some companies database security is non-existent. Its not hard to change this but I'll bet that some never do.
Re auditing changes - at my company we use database triggers to log changes to key documents/items (orders, items, ...). The audit tables themselves though read-only are described in JDE as tables and have inquiry applications linked to the relevant JDE apps. So if you need to see who changed the G/L Class on a Item and when they did it its very simple to find.
