Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Sales Data <strong>Exchange</strong> System Specification and Implementation Guide Sections 1–6: General Information<br />
Section 5.4.3 TCN Processing For ISR<br />
Records are received in version 4.05 format from many data sources, and all will contain an address label<br />
(described in Section 4.2.1) showing the intended recipient airline. <strong>ATPCO</strong> enhances this address label<br />
by sending each transaction through the <strong>ATPCO</strong> Codeshare Process (Section 9.1), adding any relevant<br />
operating carriers who require the transaction for interline billing purposes.<br />
If any recipient in the enhanced address label is identified as an ISR customer, then two processes will<br />
occur:<br />
(1) the entire ticket transaction is loaded once into a staging table.<br />
(2) one row per recipient airline is loaded into an addressing table to control the distribution of the<br />
transaction.<br />
When the address label for the ticket—which contains key data elements to relate back to the complete<br />
transaction—is loaded, a “release date” is determined for the ticket. The release date is set based on the<br />
optimum hold period (from 0 to 9 days) for the transaction, depending on the likelihood of a BSP/ARC<br />
transaction being loaded and matched to that ticket. The following steps are taken in making that<br />
decision:<br />
(1) Check the validating carrier of the TCN record (TDNR positions 1-3) to determine whether that<br />
airline is a supplier of BSP/ARC data to the exchange.<br />
(2) Check the country of sale of the TCN (based on AGTN positions 1-3) to determine whether the<br />
validating carrier sends BSP/ARC data to <strong>ATPCO</strong> for that country of sale.<br />
(3) Check the form code of the ticket (TDNR positions 4-6) to determine whether that form code is<br />
used for agency sales.<br />
(4) Check that the first flight date (Record 5, FTDA) is after the intended release date of the ticket.<br />
If all of the above criteria are met, the release date for the address label is set based on a table held at<br />
the validating carrier level per country (not based on the recipient of the data) 1 . This is because only one<br />
copy of the ticket is held in order to standardize the data that each customer receives.<br />
If any of the above criteria are not met, then the ticket transaction will be set for immediate release. This<br />
effectively means that it will be released in subscriptions for that same day (that is, at 1300 hours eastern<br />
time). Otherwise, the transaction will be released for processing at the sooner of the following conditions:<br />
(1) listed release date for the ticket (table driven) which is generally date of issue (DAIS) + 6 days for<br />
daily BSP transactions, date of issue (DAIS) + 9 days for ARC transactions, and immediate for<br />
non-daily BSP transactions, or<br />
(2) a BSP/ARC transaction matches to a transaction in the table, in which case the matched<br />
transaction is released immediately<br />
During this process, if any transactions match based on ticket number, agency code, and mismatch on<br />
transaction code, they will be considered a sale and its associated cancel and will be merged together<br />
into one outbound transaction.<br />
These tables are also used to control duplicate processing within the ISR, and the address table<br />
information is held (by recipient, ticket number, transaction code, and agency code) for 90 days. Any<br />
TCN, BSP, or ARC transaction matching these criteria for a ticket which has already been sent to a<br />
customer will be dropped as a “duplicate.” 2<br />
1 The hold period will be enhanced in 2008 to be based on the choice of the recipient carrier<br />
2 Customers will be able to choose whether to drop or retain BSP/ARC to TCN duplicates after 2008<br />
18 November 2007
Change language