CAR INSIDE AVAILABILITY
GI/Zoom Bilateral
IMPLEMENTATION GUIDE
Based on UN/EDIFACT April 1999
Last Updated on: 7/12/2007
Revision History
NOTE: For questions or comments regarding the contents of this manual, please
contact your local Galileo Marketing representative.
Release Date Change Details
June 14th, 2002 / Initial release of reformatted document.July 31th, 2002 / Changed PRD in AVLRSP from M1 to C1 in diagrams.
Changed PRD in segment definitions from M1 to C1.
Corrected segment MSG to MSD in master diagrams.
Added ITM segment to AVLRSP segment listings.
Added clarifications for use of 4473 codes in IFT segment.
Changed RUL 4440 Free text from 70 to 55.
Added Appendix D – Misc. IA Information.
August 14th, 2002 / Clarified ERI Example information for ERI 25, 26, and 34.
October 8th, 2002 / Clarified PLI usage on AVLRSP messages
November 7th, 2002 / Added Appendix E – Availability and Sell Correlation
Added 7143 Code set numbers 901 and 902
November 21st, 2002 / Added notation on AVLRSP that one repetition of the TVL under GR16 is mandatory for all RSP messages.
July 16th, 2003 / Added under Appendix D, clarification on segment repetitions.
September 24, 2003 / Added 5361 code set items 816, 817, 818
August 12th, 2004 / Added support in MSD 1225 Matrix indicator
Added support in TVL 3224 for Org/Dst City name
Added two new codes in CRI 1153 for Promotional =3 and Tour=11.
November 22, 2004 / Addition of multi-company rate response including approximate total.
August 15th, 2006 / Added definitions for 5261 items 816-839.
September 5th, 2006 / Changed number of CAV lines of text from 16 to 14 (p32)
November 2nd, 2006 / Clarified RUL Rsp for CAV Composite E005/4440 changed from 20 to 1 repetitions. Updated Note #2.
January 17th, 2007 / Added “P = package/bundled rate in TFF
January 18th, 2007 / CAA transaction was decommissioned January 4th, 2007.
References to CAA removed from this document.
June 25th, 2007 / Changed TFF/5501 to Conditional from Mandatory
September 12th, 2007 / Added comments to TFF, Example #1 regarding rate types and free mileage information
TABLE OF CONTENTS
Revision History 2
TABLE OF CONTENTS 2
INTRODUCTION 2
REFERENCES AND CONTACTS 2
HOW TO USE THIS DOCUMENT 2
MESSAGE RELATIONSHIPS 2
REFERENCE TO SERVICE SEGMENTS 2
MESSAGE OVERVIEW 2
Availability Request Message – AVLREQ 2
Message Structure Branching Diagram – AVLREQ 2
Message Sub-Structure Branching Diagram – AVLREQ 2
Availability Response Message – AVLREQ 2
Message Structure Branching Diagram – AVLRSP part 1: 2
Message Structure Branching Diagram – AVLRSP part 1: 2
Message Structure Branching Diagram – AVLRSP – part 2: 2
Message Structure Branching Diagram – AVLRSP – part 3: 2
Message Sub-Structure Branching Diagram – AVLRSP 2
SEGMENT SPECIFICATIONS - AVLREQ 2
ADS...CAR IA ADDRESS 2
CRI...CONSUMER REFERENCE INFORMATION 2
ITM...ITEM NUMBER 2
MSD...MESSAGE ACTION DETAILS 2
ORG...ORIGINATOR OF REQUEST DETAILS 2
PLI...PRODUCT LOCATION INFORMATION 2
PRD...PRODUCT IDENTIFICATION 2
RTC...RATE TYPES 2
RUL...RULE INFORMATION 2
TFF...TARIFF INFORMATION 2
TVL...TRAVEL PRODUCT INFORMATION 2
UNB...INTERCHANGE HEADER 2
UNH...MESSAGE HEADER 2
UNT...MESSAGE TRAILER 2
UNZ...INTERCHANGE TRAILER 2
SEGMENT SPECIFICATIONS - AVLRSP 2
CON...CONTACT INFORMATION 2
ERI...APPLICATION ERROR INFORMATION 2
ITM...ITEM NUMBER 2
MSD...MESSAGE ACTION DETAILS 2
PDT...PRODUCT INFORMATION 2
PLI...PRODUCT LOCATION INFORMATION 2
PMT...PAYMENT INFORMATION 2
PRD...PRODUCT IDENTIFICATION 2
RTC...RATE TYPES 2
RUL...RULE INFORMATION 2
RUL...RULE INFORMATION 2
TFF...TARIFF INFORMATION 2
TFF...TARIFF INFORMATION 2
TVL...TRAVEL PRODUCT INFORMATION 2
UNB...INTERCHANGE HEADER 2
UNH...MESSAGE HEADER 2
UNT...MESSAGE TRAILER 2
UNZ...INTERCHANGE TRAILER 2
MESSAGE EXAMPLES 2
General Rate Availability (CAL) 2
Request (this example is showing all the optional parameters) 2
Request (a typical request) 2
Request was made for several car types (ICAR, ECAR, SCAR), but ECAR is not available. 2
Response 2
Request with approximate total. 2
Agent has requested rate code ‘2A’, but 2A is sold out. Vendor returns 2B rates. 2
Response 2
Company Specific Rate Availability (CAL) 2
Request 2
Response 2
Car Rules (CAV) 2
Request (this example is showing all the optional parameters) 2
Errors 2
System Temporarily Unavailable 2
Vendor Defined Error 2
Requested CCAR and ECAR, but CCAR is sold out. 2
Location Closed 2
Multiple lines of text 2
APPENDIX A – Code List 2
APPENDIX B – APSINQ/APSRES Polling Example 2
APPENDIX C – MISCELLANEOUS SELL INFORMATION 2
APPENDIX D – MISCELLANEOUS IA INFORMATION 2
APPENDIX E – AVAILABILITY & SELL CORRELATION 2
INTRODUCTION
The purpose of this document is to define the message formats agreed by Galileo International and “The Car Corporation” for the Car Inside Availability product. The AVLREQ/AVLRSP message will be the message format used.
Car Inside Availability consists of 3 types of messages:
General Rate Availability (CAL)
Company Specific Rate Availability (CAL)
Car Rules (CAV)
REFERENCES AND CONTACTS
UN/EDIFACT ISO 9735, Release I
UN/EDIFACT Interactive Directory D99A
UN web site – http://www.unece.org/trade/untdid
HOW TO USE THIS DOCUMENT
A single EDI message may satisfy one business function or a number of business functions. In the case where a single message can define more than one business function, data element 1225, contained in the MSD segment, is used to indicate the applicable business function.
To determine what a message must contain to satisfy a specific business function (transaction), refer to:
Implementation guide, section: Message Relationship
Implementation guide, section: Message Structure
Implementation guide, section: Segment Specification
Implementation guide, section: Code List
MESSAGE RELATIONSHIPS
The AVLREQ and AVLRSP messages described in this document will be used alone for this product. Each message will be a sessionless message.
The General Rate Availability (CAL) message may generate several message requests originating from the GI system. One message will be sent for each car location for each Inside Availability Vendor. Thereby, a vendor may receive one or more requests for one agent entry (note: each request is query/reply).
The Company Specific Rate Availability (CAL) and the Car Rules (CAV) messages are strictly query/reply. In this case, one agent entry will generate 1 request to the vendor.
Galileo supports EDIFACT polling messages (APSINQ/APSRES) with each vendor that implements Car Inside Availability. If Galileo (1V or 1G) does not receive a reply in the agreed amount of time, a polling message will be sent to the vendor. If the vendor does not reply to the polling message, the Galileo function will be inhibited until a successful response is received to a polling request. Galileo will send a polling message once per minute until the vendor responds successfully at which point traffic will start flowing normally to the vendor again.
REFERENCE TO SERVICE SEGMENTS
Galileo International supports 9735 Rel. 1 instead of the interactive service segments.
UNB – Interchange Header
UNH – Message Header
UNT – Message Trailer
UNZ – Interchange Trailer
Where a repeating composite exists (that is not at the end of a segment), a number of repetitions will be agreed. The ‘+’ separator will be used. Note the repeating composite separator (*) will not be used.
MESSAGE OVERVIEW
Availability Request Message – AVLREQ
This message enables travel agent computer reservation systems and others to request availability (which can include rates and rules) from a supplier system
Message Structure Branching Diagram – AVLREQ
Message Sub-Structure Branching Diagram – AVLREQ
This Sub-structure describes the structure that will be used for the Car Inside Availability requests, General Rate Availability (CAL), Company Specific Rate Availability (CAL) and Car Rules (CAV)).
Availability Response Message – AVLREQ
Message Structure Branching Diagram – AVLRSP part 1:
Message Structure Branching Diagram – AVLRSP – part 2:
Message Structure Branching Diagram – AVLRSP – part 3:
Message Sub-Structure Branching Diagram – AVLRSP
This Sub-structure describes the structure that will be used for the Car Inside Availability responses, General Rate Availability (CAL), Company Specific Rate Availability (CAL) and Car Rules (CAV)).
Notes:
· The PLI segment under Group 3 is Mandatory in all availability messages. It is Conditional only in the Rules messages.
· One (1) repetition of the TVL under GR16 is mandatory for all RSP messages.
SEGMENT SPECIFICATIONS - AVLREQ
Legend:
TAG / = Composite or Data Element TAG as applicableNAME / = Composite or Data Element Name as applicable
*
ST / = See code list
= Status, C-conditional, M- mandatory
RP / = Repetitions
FLD TYP / = Format
COMMENTS / = Implementation comments
ADS...CAR IA ADDRESS
Function: To specify a address.
TAG /NAME / ST / RP / FLD TYP / COMMENTS
E817 / Car IA Address / C / 1
3299 / Coded Address / C / 1 / an..3
CRI...CONSUMER REFERENCE INFORMATION
Function: To specify consumer reference information.
General Rate Availability (CAL) – used at level 0.
Company Specific Rate Availability (CAL) – used at level 0.
Car Rules (CAV) – used at level 0
TAG /NAME / ST / RP / FLD TYP / COMMENTS
E967 / CONSUMER REFERENCE IDENTIFICATION / M / 20
1153 / Reference qualifier * / M / 1 / an..3 / Identifies the type of reference number being used
1154 / Reference number / M / 1 / an..35 / A number identifying the travelers membership in a program
3036 / Party name / C / 1 / an..35 / Not used
1145 / Traveler reference number / C / 1 / an..35 / Not used
Example:
1. Corporate number… CRI+2:123456789'
- Corporate number and ID number… CRI+1:999999999+2:123456789’
ITM...ITEM NUMBER
Function: To specify an item number
General Rate Availability (CAL) – not used.
Company Specific Rate Availability (CAL) – not used.
Car Rules (CAV) – used at level 0
TAG /NAME / ST / RP / FLD TYP / COMMENTS
E212 / ITEM NUMBER DETAILS / C / 99
7140 / Item number / C / 1 / an..35 / Confo number from sold segment
7143 / Item number type, coded * / C / 1 / an..3 / 900=Conformation number
902=Yield management number
1131 / Code list qualifier / C / 1 / an..3 / Not used
3055 / Code list responsible agency, coded / C / 1 / an..3 / Not used
Example:
1. To indicate a confirmation number of a sold Segment… ITM+123456789:900’
MSD...MESSAGE ACTION DETAILS
Function: To specify the message processing requirements
General Rate Availability (CAL) – used at level 0.
Company Specific Rate Availability (CAL) – used at level 0.
Car Rules (CAV) – used at level 0
TAG /NAME / ST / RP / FLD TYP / COMMENTS
E972 / MESSAGE PROCESSING DETAILS / M / 1
4025 / Business function, coded * / M / 1 / an..3 / To indicate what type of service is being requested, i.e. air, car rental, rail, hotel, etc.
1225 / Message function, coded * / M / 1 / an..3 / To indicate the action being requested, i.e. sell, modify, cancel
3055 / Code list responsible agency, coded / C / 1 / an..3 / Not used
1225 / Message function, coded * / C / 9 / an..3 / Used for MATRIX function –
Approximate Total
4343 / RESPONSE TYPE, CODED * / C / 5 / an..3 / Not used
Example:
1. To request General Rate Availability (CAL)… MSD+2:36’
- To request Company Specific Rate Availability (CAL)… MSD+2:37’
3. To request Car Rules (CAV)… MSD+2:38’
ORG...ORIGINATOR OF REQUEST DETAILS
Function: To convey information pertaining to the originator of the message or location and commercial computer reservation system delivering the message.
General Rate Availability (CAL) – used at level 0.
Company Specific Rate Availability (CAL) – used at level 0.
Car Rules (CAV) – used at level 0
TAG /NAME / ST / RP / FLD TYP / COMMENTS
E973 / DELIVERING SYSTEM DETAILS / C / 1
3036 / Party name / C / 1 / an..35 / To specify the name of the company or system originating or delivering the message.
3225 / Place/location identification / C / 1 / an..25 / To identify the city code of the delivering system
3224 / Place/location / C / 1 / an..70 / Not used
E974 / ORIGINATOR IDENTIFICATION DETAILS / C / 1
3197 / Agent identification / C / 1 / an..9 / An IATA/ARC.
3465 / In-house identification / C / 1 / an..9 / Galileo pseudo city code
3197 / Agent identification / C / 1 / an..9 / Not used.
3036 / Party name / C / 1 / an..35 / Not used
E975 / LOCATION / C / 1
3225 / Place/location identification / C / 1 / an..25 / CRT location – city code
3224 / Place/location / C / 1 / an..70 / Not used.
3207 / Country, coded / C / 1 / an..3 / Not used
3227 / Place/location qualifier / C / 1 / an..3 / Not used
3036 / PARTY NAME / C / 1 / an..35 / Not used
3457 / ORIGINATOR TYPE, CODED * / C / 1 / an..3 / Not used
E976 / ORIGINATOR DETAILS / C / 1
3207 / Country, coded / C / 1 / an..3 / An ISO code identification of the country in which the request message originated
6345 / Currency, coded / C / 1 / an..3 / Not used
3453 / Language, coded / C / 1 / an..3 / Not used
3503 / ORIGINATOR’S AUTHORITY IDENTIFICATION / C / 1 / an..9 / Not used
Example:
1. Originating system 1V is located in DEN, has an IATA number 12345678, pseudo city code of 0GK5, the travel agency location is in SFO… ORG+1V:DEN+12345678:0GK5+SFO+++US’
PLI...PRODUCT LOCATION INFORMATION
Function: To specify product location information
General Rate Availability (CAL) – Conditional, used at level 0.
Company Specific Rate Availability (CAL) – Conditional, used at level 0.
Car Rules (CAV) – not used.
TAG /NAME / ST / RP / FLD TYP / COMMENTS
E008 / GEOGRAPHIC DETAILS / M / 99
3227 / Place/Location qualifier * / M / 1 / an..3 / 900= Reference point.
3224 / Place/location / M / 1 / an..70 / Location
5479 / Relation, coded / C / 1 / an..3 / Not used
6060 / Quantity / C / 1 / n..15 / Not used
6063 / Quantity qualifier / C / 1 / an..3 / Not used
2002 / Time / C / 1 / n4 / Not used
8179 / Type of means of transport identification / C / 1 / an..8 / Not used
8179 / Type of means of transport identification / C / 1 / an..8 / Not used
8179 / Type of means of transport identification / C / 1 / an..8 / Not used
8179 / Type of means of transport identification / C / 1 / an..8 / Not used
8179 / Type of means of transport identification / C / 1 / an..8 / Not used
6000 / Latitude / C / 1 / an..10 / Not used
6002 / Longitude / C / 1 / an..11 / Not used
Example: