>>Amadeus is re-writing a pretty garbled version of the PNR - without getting proper documentation for the format I don't see how you can reliably parse the information.
>>All I can glean (by guesswork) if that the record you posted relates to two flights:
>>
>>Tallinn to Vienna on flight no OV 0192 (Estonia Air) Departs 29th Aug 0725 Arrives 0845 (from U-001x))
>>Vienna to Ankara on flight no TK 8726 (Turkish Airlines) Departs 29th Aug 1030 Arrives 1400 (from H-019)
>>
>>You could also try assuming that G-X gives departure and final destination airports (VIEANK = Vienna, Ankara)
>>No idea where the reservation number is.
>
>Document http://www.amadeus.com/corp/xml/documents/aco/gb/en/EMDAIROct2011.pdf
>which I posted contains Amadeus terminal commands (whose documentation can found
>in Amadeus client tutorials and user manuals in internet) and
>corresponding AIR-BLK20x output.
>
>By analyzing those samples I think I guessed PNR record locator position which I provided
>in previous message.
>No idea why this is duplicated in same line.
>
>>FWIW:
>>Fare was 144 Euros (or 2255 Estonian Kroon @ 15.64660) (from K-F)
>>
>>KFTF and TAX are obviously various taxes in Kroon (Airport tax, etc)
>>Q- is probably the fare expressed as 'Neutral unit of construction' where ROE is the exchange rate for Euros.
>>SSR is probably 'Special Service Request'
>>
>>A bigger sample might provide a better guess :-{
>
>I havent found any such commands/ output sample which contains ticket numbers.
>It looks like my AIR sample message contains in end ticket number request, maybe it does
>not contain ticket numbers.
>Google search for AIR-BLK206 returns some additional AIR format samples.
>No idea do they contain ticket numbers or not.
>
>My goal in to compare sold tickets from Amazon with BSP billing reports. Every ticket in billing report
>must have corresponding invoice issued to customer by travel agency.

I looked at the document on the link you provided - that only seems to provide information on the added EMD segment not the complete interchange ?

Was the sample that you initially posted complete ? A full EDI interchange would have a UNA segment defining the separators used in the interchange.
In the sample this appeared to be using just CR or CR/LF as the segment separator and semi-colons for the component with no separator for data elements - the latter, where they contain multiple elements, look to be just fixed length fields.

If '2JW8HW' is the number then I'd guess the first occurrence is the main number. The repeat at the end is prefixed by 'OV' for Estonia Air followed by a second number (RZ3ZZ7) for the Turkish Airways leg?

I looked at : http://contentm.mkt3061.com/lp/10362/159354/ATC%20User%20Manual%20EN%20Feb0912%20v2_FINAL_1.pdf
The section near the end ('Back-Office') seems to bear out my assumption - this ticked is a round trip Paris - Frankfurt (all on Air France) and the ticket number (5PII3K) is only repeated once at the end (i.e. no other carrier involved). Also noted that the G-X segment is 'PARPAR' rather than 'CDGCDG' so seems to be based on the city rather than the airport.....

Can't fathom how the legs are listed. On your sample the second leg is listed first. On this one it's the other way around (and the prefixes are different) :-{