The following attributes must be replaced in the POS element with appropriate values. If you do not have these details, please contact the airline’s Database Administrator to get them.
The following are examples of log in details and a POS element.
The following log in details will be extracted from the XPath specified. Please see example below.
TerminalUserID = /POS/Source/@ERSP_UserID TerminalPassword = /POS/Source/@ERSP_UserID AgentID = /POS/Source/@AgentSine AgentPassword = /POS/Source/@AgentSine Office = /POS/Source/@PseudoCityCode GroupCode = /POS/Source/@AgentDutyCode CountryCode = /POS/Source/@ISOCountry CityCode = POS/Source/@AirportCode CustomerCode = /POS/Source/@AirlineVendorID
Do not use the values below, they are only shown here as an example, replace them with the ones received from your airline’s Database Administrator.
TerminalUserID/Password = MYIDTVL/1AGT4HA
3 -7 alphanumeric/1 numeric, Slash (/) 3 alpha, 1-3 numeric
Sign-In function code, 2-alpha airline code. 1 to 6 numeric agent number,slash (/). 1-6 numeric 1 alpha password, slash (/), 1-3 numeric duty code, slash (/), 3 alpha, 3 numeric city code
Note: Please make sure to use the appropriate Duty Code (AKA User Group), according to the functionality you wish to access, i.e. User Group 121 for DCS Check-in functions, User Group 41 for RES PNR functions, Airfare itinerary pricing, and Ticketing.
This would resolve into the following POS element for AirFlifoRQ
<OTA_AirFlifoRQ TransactionIdentifier=""> <POS> <Source ERSP_UserID=" MYIDTVL/!AGT4HA" AgentSine="321/999W" PseudoCityCode="WWW001" AgentDutyCode="41" ISOCountry="IN" AirlineVendorID="ha" AirportCode="WWW"/> </POS> <Airline Code="HA"/><FlightNumber>2014>/FlightNumber<DepartureDate>2009-04-22</DepartureDate> </OTA_AirFlifoRQ>