Search Hub Trans Log

About

The B2B Transaction An aseXML realisation of a Business Document. log records all the transactions the B2B Business-to-Business. Generic term used to refer to defined business-to-business interactions between participants; excludes interactions between a participant and market systems such as MSATS. Hub has handled; this includes all messages and transaction acknowledgements. Participant Users with appropriate access can search the transaction log for specific transactions.

Searching is accomplished by defining the appropriate search criteria in the Search Transaction See Relevant Rules or Procedures Log interface. The values you enter are used to extract the specific transactions matching your values.

Search trans log user rights access

For access to Search Trans Log, Participant Administrators select the B2B Hub Transaction Log entity in the Administration >Maintain Rights menu.

Searching the transaction log

To search the transaction log:

On the main menu, click B2B Browser and then click Search Trans Log.

The Search Transaction Log interface displays. Complete the relevant fields and click Search. For help, see Search Transaction Log fields.
Click Reset to start again.

The Search Transaction Log Results interface displays (for help understanding the fields see “Search Transaction Log Results) and select one of the following options:
Click Download Result as a CSV file at the bottom of the page to display the result in a spreadsheet format.
Click View in the Action column to see the message details, Viewing a transaction.
Click Search Related Record in the Action column to see information for related records. The link only displays for Service Order Request transaction types and searches for corresponding Service Order Response transactions, Searching related records.

Table 125 Search Transaction Log fields

Field	Description
From Participant	The Participant initiating the transaction
To Participant	The Recipient receiving the transaction.
Message ID	The ID of the message. This field supports SQL patterns (wildcards). This means that you can use % for wildcard and any other valid SQL constructs.
Initiating Transaction ID	The initiating transaction ID contained in the transaction. This field supports SQL patterns (wildcards). This means that you can use % for wildcard and any other valid SQL constructs.
Initiating Service Order ID	The ID of the initiating Service Order to view Option 1 and 2 Notified Party transactions raised against a Service Order Request. This field supports SQL patterns (wildcards). This means that you can use % for wildcard and any other valid SQL constructs.
Transaction Type	The transaction type of the transaction.
Transaction Status	The delivery status. For example ‘Completed’, ‘Rejected’ etc.
Message Context ID / Filename	The Message Context ID or filename of the transaction. This field supports SQL patterns but does not support the zip file extension.
Transaction ID	The transaction id of the transaction. This field supports SQL patterns (wildcards). This means that you can use % for wildcard and any other valid SQL constructs.
NMI	The NMI contained in the transaction.
Service Order Type	Select a service order type from the drop-down list.
Service Order Subtype	The subtype of the transaction.
Search by Transaction delivered date	Select to search by transaction delivered date.
Search by Transaction modified date	Select to search by transaction modified date.
From Date	Date when the Transaction was initially received by the e-Hub.
To Date	Date when the Transaction status was last updated based on an action by a participant.
From Time	Time when the Transaction was initially received by the e-Hub.
To Time	Time when the Transaction status was last updated based on an action by a participant.

Table 126 Search Transaction Log Results

Field	Description
From Participant	The Participant initiating the transaction.
To Participant	The Recipient receiving the transaction.
Message ID	The ID of the message.
Transaction ID	The transaction ID.
Init Transaction ID	The initiating transaction ID.
Init Service Order ID	The initiating service order ID
Transaction Type	The transaction type.
Service Order Type	The transaction subtype.
Hub Generated	Flags if the message was generated by the e-Hub: Y – Generated by the e-Hub (e.g. Initiator or Notified Party). N – Received from the participant or is a shell record.
NMI	The NMI of the transaction.
Message Context ID / Filename	The Context ID or Filename that contained the message.
Message Timestamp	When the file was written to the Participant’s B2B Hub inbox.
Transaction Status	The current status of the Message/Transaction either: COM - Completed D - Delivered REJ - Transaction Rejected TAWR - Transaction Acked Waiting for Response
Message Status	Indicates if a message is awaiting an action by the receiving party or an action is complete: D - Delivered MA - Message Acked REJ - Message Rejected by Recipient SC - Sync Completed
Action	Click to view the transaction details.

Viewing a transaction

You cannot view Transaction details for historical Service Order A request to perform specified work, see B2B Procedures: Service Order Process. types in the B2B Browser A web interface supporting the creation and management of a defined set of business-to-business transactions and acknowledgements. Optionally used to manage your B2B inbox and outbox. It remains part of the B2B e-Hub services.. To view details for these transactions: from the Participant File Server The publishing point from AEMO systems to participant systems. Each participant is allocated an account and access to private and public areas. Participants are responsible for interfacing with the participant file server. folder, open the actual XML eXtensible Mark-up Language. file. In the Service Order Type drop-down list, historical Service Order transactions have a [H] label.

To view a transaction:

Follow the instructions for Searching the transaction log.

Click View to display the View Message interface and select from the following options:

Click Download in the Action column to download the message.
Click Acknowledge Transaction to acknowledge the message.
Click Reject in the Action column to reject the message.
Select a Transaction ID, Transaction Type, NMI or Initiating Transaction ID to view further information.

For example, click the Transaction ID link to view the message information.

Searching related records

To search related records (searches for corresponding Service Order Response A B2B Communication in response to a Service Order Request that includes an explanation if the work is incomplete. transactions types only):

Follow the instructions for Searching the transaction log
Click Search Related Record.
The related Service Order Response for that Service Order Request displays.