Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

 

Change of Travel department OID

If a new travel department OID is registered (or modified) on an existing company, then:

  1. The company in the old OID is deactivated (also all associated travellers are deactivated)
  2. A new company in the registered OID is created
  3. In Faces all CSX record locator of all travellers will be deleted. Within the next 60 minutes all travellers affected are created in the new OID 

 

Error MessageProfile TypeMeaningSolution
Profile type mismatch, expected TRAVELLER, got nullTraveler

RECORD LOCATOR NOT FOUND 

Remove record locator and save again
Publishing failed with the error: soap message header incorrectCompanySomething is wrong with OID or WSAPContact Amadeus
Duplicate IndexCompanyDupe customer numberEnsure that a customer number is only used/ assigned once or renumber the company customer number in Faces
The backend didn't understand the incoming query. Please contact your helpdesk.Company

Time out in Amadeus

 or

There is a wrong entry in some field i.e. spaces after a line in custom fileds

Save again

or

Amend entry and save again

Invalid external no.:123456CompanyThere is a special character or space in /after the customer numberAmend the customer number and save again
Internal errorTraveller/ CompanySpecial character/ space has been inserted somewhere on the profileRemove special characters/ spaces and save again
Pending Reading from Profile/ Data TruncationTraveller/ Company

This means that the profile(s) abeing imported have

  • AP lines that are too long
  • Remarks that are too long (max 150 characters allowed)
  • Special characters in the elements i.e commas, slashes and so on
Clean up the profiles in CSX by removing special characters, spaces or reducing the AP/ RMs, saving the profile in the GDS again before getting back to Faces to save the profile again.
11 SessionTraveller/ CompanyOID has not yet been added to the WSAPContact Amadeus to add the OID to your WSAP
SR-DOCS cannot exceed length of 70 charsTravellerDue to a long name, the SR DOCs line is then too long (maximum characters allowed are 70 chars)

Only occurs if the agency is using the Tenzing version of Amadeus webservices. This is a Webservice limitation for Tenzing hat does not exist in Amadeus Cental System or for the Tenzing_V2 version. To solve this error, the name has to either shortened in Faces or the SR DOCs copy command has to be removed/ deactivated in Faces. The complete SR DOCS line can be separately directly inserted in Amadeus Cental

  • No labels