Table of Contents - APTAStandards.com

Exhibit 4.8-5 Transaction Groups
Group UdType Description
Picc 1 Picc transactions- transactions related
to Picc
ad justments such as issue, unblock
Application 2 Application transactions- transactions
related to
Application adjustment such as create, delete, block,
unblock
Product 3 Product transactions- transactions
related to fare
processing, autoloads, add values, actionlists, product
usage
Other 4 Other transactions
Audit registers 5 Audit registers
Events 6 Event records
Project Specific Txns 7 Project specific transactions. Use of the UDSubType
values must be non-overlapping across projects.
The “Audit Registers”, “Events”, “Project Specific Transactions”
and the “Other”
transactions are deemed optional and beyond the scope of this specification. The
messages that fall into these transaction groups depend
on the requirements of the
specific operator/scheme manager.
All messages have a purpose field, which allows transactions of the same purpose to be
processed
via different paths from transactions of another purpose. They also allow
grouping for reporting purposes. Exhibit 4.8-6 provides a list of the purpose codes
supported by the specification.
4.8-6 Transaction Purposes
Transaction Description
Purpose
code
M Maintenance Transactions
F Financial Transactions which affect the
Master Database
B Blocking Transactions
S Miscellaneous Transactions
U Non Financial Usage Transactions
4.8.4.1
Transaction Data
The
Product Transaction Group (UD Type=3) messages, listed in exhibit 4.8-7, are ERG
equivalent to the “Farecard Usage Transaction” messages as proposed by the WG4.
Each message in every transaction group is assigned a unique sub-type ID based on the
fare product used and the entry/exit condition of the journey.
Page 62