getTransactionLog

Description
This inquiry transaction returns transaction audit information from the InfoSphere® MDM audit log tables, along with transaction history details from the history tables.
Web Services
Operation name: getTransactionLog
Service name: ProductServices
Example

Retrieve details of all compliance requirement activities performed by the user Jane Smith, whose user ID is Janesmith, on December 16, 2009.

Retrieve details of a party address update that was processed for Jane Smith's mailing address on December 16.

Usage information
The input to this transaction is one or more of the following parameters:
  • RequestType, which can be PartyId or ContractId
  • RequestValue, which is the actual value of the PartyId or ContractId
  • BusinessTransactionType
  • UserId
  • TransactionLogId
  • ClientSystemName
  • ClientTransactionName
  • ExternalCorrelationId

The InquireFromDate in the control object must also be provided. The InquireToDate in the control object is optional; if it is not provided the value is defaulted to the end of the day for InquireFromDate. If InquireFromDate is provided with or without InquireToDate, InquireAsOfDate cannot be provided.

Audit details include information such as the UserName or UserRole that executed the transaction, the transaction name, the PartyId or ContractId associated with the transaction, and others.

The transaction audit log can be queried using PartyId, ContractId, or BusinessTransactionType. PartyId and ContractId are defined as internal transaction keys in InfoSphere MDM. Other values can be defined that can then be used for log retrieval. All queries are performed by date or date range.

AdditionalDetailIndicator is an optional field with values Y or N. This field indicates whether History data is requested for a Party/Contract. If not provided, the AdditionalDetailIndicator uses a default value of N.

Preconditions
There must be historical records in the history database in order to use the getTransactionLog transaction to retrieve additional details about a transaction. If database triggers are altered, the getTransactionLog function is affected.
Mandatory input
  • InquireFromDate
  • InquiryLevel
Inquiry levels
InquiryLevel:
  • Level 0 - returns TAILTransactionLogBObj and TAILExternalLogTxnKeyBObj.
  • Level 1 - returns TAILTransactionLogBObj and its associated business objects, TAILInternalLogBObj, TAILExternalLogTxnKeyBObj, and TAILInternalLogTxnKeyBObj.
Filter values
Not applicable
Transaction behavior
Transaction audit details are written to the transaction audit information log (TAIL) tables at the time the transaction successfully completes.
Request message
<TCRMTxType> getTransactionLog

<TCRMTxObject> DWLTAILRequestBObj

<TCRMObject> DWLTAILRequestBObj

with associated business objects:

Response objects
DWLTAILResponseBObj

with associated business objects:

Special note
Not applicable