Logging PeopleSoft, E-Business Suite and SAP End-Users in Oracle RDBMS Audit Logs

Logging and auditing database connections to application users for SAP, PeopleSoft and the E-Business Suite is possible with a standard feature of the Oracle RDBMS. SAP, PeopleSoft and the E-Business Suite all populate a database attribute that is automatically passed to Oracle’s native audit logs. This attribute is the CLIENT_ID and within the Oracle dictionary and documentation is also referred to as CLIENTID and CLIENT_IDENTIFIER.

The CLIENT_ID is an application context. Application contexts are name-value pairs that the Oracle Database stores in memory. Consider application contexts as global variables that hold information for the duration of session, they are not persistent.

The CLIENT_ID context is NOT the same as the CLIENT_INFO context.  The essential difference between the two is one contains application’s end-user username and is passed to the native Oracle audit logs and the other holds an abbreviated application log string and is not passed to Oracle’s native audit logs.