Problem
When attempting to import a PNR (Passenger Name Record) from Amadeus or Galileo, the import fails with an error message indicating that a specific airport code is not found in the system (e.g., ‘No airport with REL code found in the system’).
What We Found
For a PNR to import successfully, ALL airport codes and airline codes referenced in the PNR must exist as Location records in the Salesforce org. This includes not only the primary departure and arrival airports, but also any technical stops or intermediate airports included in the GDS response. When an airport code is missing, Kaptio cannot map the flight segment data and the import fails.
Solution
- Identify the missing airport code from the error message (e.g., ‘REL’, ‘BKQ’)
- Look up the airport details using the IATA code (e.g., REL = Trelew Airport, Argentina; BKQ = Blackall Airport, Australia)
- In Salesforce, navigate to Locations (KaptioTravel__Location__c)
- Create a new Location record or update an existing one to include the IATA code in the appropriate field
- Retry the PNR import - it should now complete successfully
Notes
- Technical stops in flight routes may include airport codes not visible in the GDS display but present in the API response
- The same principle applies to airline codes - all airlines referenced in the PNR must exist in the org
- Consider proactively adding commonly used regional airports to prevent future import failures
Source: KHELP-12341