ATPCO Ticket Exchange

Sales Data Exchange System Specification and Implementation Guide Sections 1–6: General Information
Section 3 Data Representation
Section 3.1 Alphabetic and Alphanumeric Elements
Alphabetic and alphanumeric elements shall contain left-aligned strings of characters with trailing blanks.
If there is no entry, the entire element is filled with blanks. Facsimile fields must be reported precisely as
they were generated by the ticketing system.
Section 3.2 Numeric Elements
Numeric elements shall be right aligned with leading zeros. If there is no entry, the entire element is filled
with zeros. When the data has passed through the Net Remit Data Removal process (see Section 9.2),
the entire element is filled with nines.
In numeric value amount elements, the decimal point shall be defined by the CUTP, which relates to
these specific elements. The Glossary (Section 10) lists all numeric values expressed in this way and
refers to the appropriate CUTP within the transaction.
No element shall be packed.
Neither low values nor special characters shall be provided.
Section 3.3 Data Validation
Section 3.3.1 Mandatory, Conditional, and Optional Status
The following conventions apply to data element descriptions:
• Where an element is annotated with status ‘M’ in the Glossary (Section 10), the data is
mandatory and indispensable for proper processing and must be provided at all times.
Mandatory elements may also include cross-edit conditions that provide for correct
formatting of the data.
• A mandatory element that is within a non-mandatory record must be provided when the
conditions for providing that record are met. If the record is not provided, the mandatory
element will also not be provided.
• Where an element is annotated with status ‘O’ in the Glossary (Section 10), the data will
be provided whenever available to the system provider.
• A data element will never be expressed as “Conditional.” It is either required in all cases
(mandatory) or not required in all cases (optional).
• Certain records have associated conditions; for example, the Record 6 (NFP Proration
Record) is supplied on the condition that the sale has been prorated. An element may be
mandatory within a conditional record. Elements may also be optional within a mandatory
record. See the Glossary (Section 10) for further detail at the element level.
Section 3.3.2 Application of Cross-Edits
Where an element or a record has an associated cross-edit, the data should conform to the check as
described. These cross-edits are used at a record and a data element level to audit and report on data
quality standards within reported files.
5 November 2007