Transactions

Purpose: Provides a container for multiple transactions within one aseXML A standard for energy transactions in XML. A set of schemas and usage guidelines that define how data should be exchanged under FRC in the gas and electricity industries in Australia. message.

Detail: An aseXML message can contain one or more transactions. All transactions within an aseXML message are grouped under this container.

Field	Restrictions	aseXML	Schema
Transactions	maxOccurs=”unbounded”	sequence	Transactions_r38
Transaction	Transaction choice	Transaction	Transactions_r38

Transaction

Purpose: Common container for all transactions.

Detail: All transactions within aseXML are carried within this container. You provide the transactionID and transactionDate for all transactions. You provide the initiatingTransactionID on response transactions, representing the transactionID of the initiating transaction.

Field	Restrictions	aseXML	Schema
Transaction	maxOccurs=”unbounded”, Restricted to Transaction main types (see Transaction types used in the B2B Procedures).	complex	Transactions_r38
transactionID	Mandatory, hexadecimal characters 0-9 and a-f (or A-F)	TransactionIdentifier	Transactions_r38
transactionDate	Mandatory	xsd:dateTime (ccyy-mm-ddThh:mm:ss.sss+hh:mm)	Transactions_r38
initiatingTransactionID	Optional, if response, must match the transactionID from initiating request	TransactionIdentifier	Transactions_r38

Table 53 Transaction types used in the B2B Procedures

Transaction	Procedure
Customer Details Notification	Customer and Site Details Notification
Customer Details Request	Customer and Site Details Notification
MeterDataMissingNotification	Meter Data
MeterDataNotification	Meter Data
MeterDataVerifyRequest	Meter Data
MeterFaultAndIssueNotification	One Way Notification
NoticeOfMeteringWorks	One Way Notification
NotifiedParty	One Way Notification
OneWayNotification	One Way Notification
PlannedInterruptionNotification	One Way Notification
SharedFuseNotification	One Way Notification
RemoteServiceRequest	Meter Data
RemoteServiceResponse	Meter Data
ServiceOrderRequest	Service Order
ServiceOrderResponse	Service Order
Site Access Request	Customer and Site Details Notification
CSVConsumptionData	Meter Data
CSVIntervalData	Meter Data
PlannedInterruptionNotification	One Way Notification
CSVConsumptionData	Meter Data
CSVIntervalData	Meter Data
Customer Details Notification	Customer and Site Details Notification
Customer Details Request	Customer and Site Details Notification
LifeSupportNotification	Customer and Site Details Notification
LifeSupportRequest	Customer and Site Details Notification
MeterDataMissingNotification	Meter Data
MeterDataNotification	Meter Data
MeterDataVerifyRequest	Meter Data
MeterFaultAndIssueNotification	One Way Notification
NoticeOfMeteringWorks	One Way Notification
NotifiedParty	One Way Notification
RemoteServiceRequest	Meter Data
RemoteServiceResponse	Meter Data
ServiceOrderResponse	Service Order
OneWayNotification	One Way Notification
PlannedInterruptionNotification	One Way Notification
PlannedInterruptionNotification	One Way Notification
Site Access Notification AmendMeterRouteDetails	Customer and Site Details Notification
Site Access Request	Customer and Site Details Notification

Support types

TransactionIdentifier

Purpose: Uniquely identify every transaction generated by the transaction sender.

Detail: Transaction See Relevant Rules or Procedures identifiers are not necessarily globally unique; they are only unique to a particular sender. The length allows you to use UUIDs as transaction identifiers, guaranteeing global uniqueness.

A transaction acknowledgement identifies which transaction it is acknowledging by providing the transaction identifier as an attribute.

In addition to carrying its own unique identifier, a transaction generated in response to the initial transaction, also carries the transaction identifier of the initial transaction.

Field	Restrictions	aseXML	Schema
TransactionIdentifier	Mandatory	UniqueIdentifier	Transactions_r38