Overview
Audited columns in a table can be updated by transactions that originate outside of JD Edwards EnterpriseOne through an interoperability model. When this occurs, JD Edwards EnterpriseOne creates an audit record for the transaction, but the system records only a portion of the audit information, such as the audited column, before and after values, and recorded columns. The audit information will not include a GUID, application ID, workstation name, or IP address, unless you configure the interoperability model to pass this data to the audit record.
Oracle provides audit APIs that enable the transfer of audit information from these interoperability types:
Business services
Java connector
COM connector
XPI
This table describes the audit record columns, the API used to pass the data to the columns, and the values that you enter as parameters for the API:
Audit Record Column |
API |
Value for API Parameter |
|---|---|---|
GUID |
setGUID |
Enter an available GUID. If you do not enter a GUID, the API generates a new GUID. |
ApplicationID |
setApplicationID |
Enter the application ID. If you do not enter an application ID, the API passes "INTEROP" for this value. |
WorkstationName |
setWorkstationName |
Enter the workstation name. If you do not enter a workstation name, the API passes the local workstation name for this value. |
IPAddress |
setIPAddress |
Enter the IP address. If you do not enter an IP address, the API passes the IP address of the local workstation. |
Oracle provides two sets of these APIs to pass audit information from interoperability transactions. The set of APIs used depends on the interoperability model being employed, as described in this table:
Interoperability Model |
API Set |
Platforms |
|---|---|---|
XPI, Java connector, and business services |
JAVA APIs |
JD Edwards EnterpriseOne supported platforms |
COM Connector |
C APIs |
WIN 32 platforms |
For more information about the APIs, see the JD Edwards EnterpriseOne Tools Release API Reference Guide on My Oracle Support web site at: