Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 7 Viewing Logs : Audit Log

Audit Log
The audit log is used to store information about the messages and documents processed by TIBCO BusinessConnect. You can use the audit log to follow the processing states of inbound or outbound documents. Some of the types of information stored in the audit log include:
Summary View
The audit log summary view depends on the protocol.
Table 9, Common Audit Log Columns lists the columns common to all protocols except Gateway.
The columns specific to each protocol are listed in the following tables:
 
Values are TRUE or FALSE
Values of the user keys delimited by colon (:); if specified in the .sef guideline as an EVALU record using EDISIM Standards Editor
Example: PO:90392
Example: 000000001
 
If a transaction is sent via TEXT, this column should be True in the sender audit log and False in the receiver audit log.
 
If a transaction is sent via Gateway, this column should be True in the sender audit log and False in the receiver audit log.
 
Transaction Details View
To view the details of a transaction, click the document icon in the left-most column of an audit log entry.
The Log Viewer first displays the general information for this entry, then a table with available information for each event in that transaction. The table columns are listed in Table 14.
Status of the transaction. See Acknowledgment Messages for a list of the possible values and a description of the meaning of the status codes.
Transaction Detail View for the Gateway Protocol
The detail view of each scheduled transmission summary row displays transactions that are added or removed from the batch or scheduled transmission. It also shows the protocol, document ID, operation ID, and trading partner of the scheduled transaction and the scheduled transmission time.
A description of what happened for each entry. Example: Transaction added to batch for scheduled transmission successfully.
Status of the message, such as COMPLETED, PENDING, ERROR, COMPLETED WITH ERRORS, and so on.
Acknowledgment Messages
For information about how to see the error information contained in acknowledgments, see State Details View.
EDIFACT
For CONTRL messages, the status of the last event for the CONTRL message will be COMPLETED, if the message contains only the following acknowledgment codes:
1 acknowledged
7 this level acknowledged, next lower level acknowledged if not explicitly rejected
A code of 2 contained in the CONTRL message will be indicated by a status of ACK ACCEPTED WITH ERRORS. A code of 3, 4, or 6 in the CONTRL message will be indicated by a status of ACK REJECTED ERRORS. In this way it is possible to use the audit log to see which CONTRL messages report EDIFACT messages not accepted by your trading partner.
X12
For 997, 999 and TA1 acknowledgments, the status of the last event for each transaction will be COMPLETED, if the transactions contain an acknowledgment code of A for accepted. A status of ACK ACCEPTED WITH ERRORS will be indicated if the acknowledgment contains a code of E. A status of ACK REJECTED ERROR will be indicated if the acknowledgment contains any other code. In this way you can use the audit log to see which 997 or TA1 acknowledgments report X12 transactions or interchanges which were not accepted by your trading partner.
State Details View
To view the details of a specific state, click the document icon at the left of a transaction detail entry. The Log Viewer displays in one window all of the information from the summary view and transaction details view for this current state.
From the state details view you can save the message associated with the processing state entry to a file. To information on this feature, see the Viewing Logs and Reports chapter in TIBCO BusinessConnect Trading Partner Administration You can also save the HTML format validation audit error report to a file in case of validation errors. You have to configure to enable this feature.
State Detail View for the Gateway Protocol
Status of the message, such as COMPLETED, PENDING, ERROR, COMPLETED WITH ERRORS, and so on.
The current state of the message. Examples: TXN_ADDED_TO_BATCH, TXN_PACKAGED_FOR_BATCH.
Acknowledgments Display in the Audit Log
The following is an example of the audit log entry for previously transmitted transactions when an acknowledgment with acceptance status is received from your trading partner.
Status  ACK ACCEPTED
State  ACK_FROM_TP
Description   Acknowledgment received with the Ack code or Code name.
EDIFACT Acknowledgment Codes
The CONTRL Syntax and Service Report Message acknowledgment is available in EDIFACT. The CONTRL acknowledgment can have the action codes and code names listed in Table 17.
If the code of a CONTRL acknowledgment is 1 or 7, the status is COMPLETED. A code of 2 contained in the CONTRL message will be indicated by a status of ACK ACCEPTED WITH ERRORS. A code of 3, 4, or 6 in the CONTRL message will be indicated by a status of ACK REJECTED ERRORS.
X12 Acknowledgment Codes
The following acknowledgments are available in X12:
997 and 999 X12 Functional Acknowledgment
The 997 and 999 acknowledgments have codes and code names listed in Table 18.
If 997 and TA1 have code A, the status is COMPLETED. A status of ACK ACCEPTED WITH ERRORS will be indicated if the acknowledgment contains a code of E. The status of ACK REJECTED ERROR will be indicated if the acknowledgment contains any other code.
TA1 X12 Interchange Acknowledgment
The TA1 acknowledgment can have the codes and code names listed in Table 19.
If 997 or 999 and TA1 have code A, the status is COMPLETED. For all other codes, the status is COMPLETED WITH ERRORS. These values come from the status field in certain tables.
User Keys
Users can choose certain elements in their guidelines to be shown in an audit log, and these elements are searchable in the audit log summary rows.
For example, in EDIFACT and X12 protocol you would search for purchase orders or order numbers instead of actually looking into the EDI document.
To achieve the user key functionality, perform the following steps:
1.
2.
Select the DSR Mark/Unmark to mark the element. You would see a tick mark to indicate it is marked. This will define a user key for Reference Identification
3.
Click Apply.
4.
Click Save to save the guideline.
5.
When a transaction is received for the transaction type for which you requested the user key value to be shown, the BusinessConnect engine picks up the value for the field indicated in the guideline to be displayed in the User Key column, as well as the part of the userkey attribute of the ResponderRequest message.
You can add as many keys as you prefer. The key values will be shown in one column only and will be separated by a semicolon (:).
Retrieve the User Key
The user key will be retrieved after the documents have been converted from XML to EDI.
They can be retrieved only if outbound validation has been enabled for outbound documents, and inbound validation has been enabled for inbound documents.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved