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 5 Next »

Overview

Description

The fields visible under this section maybe more or less depending on the interfaces that have been activated. Below is an illustration of some of the fields.

FieldDescription
Target GDSCheck boxes of interfaces that have been activated on the agency i.e Amadeus, Galileo, Sabre and so on

Interfaces

AeTM
Personal CC onConfiguration in which AeTM Field (possible values CC1, CC2 or CC3) the first personal credit card of the traveller will be transmitted.
2nd Personal CC onConfiguration in which AeTM Field (possible values CC1, CC2 or CC3) the second personal credit card of the traveller will be transmitted
3rd Personal CC onConfiguration in which AeTM Field (possible values CC1, CC2 or CC3) the third personal credit card of the traveller will be transmitted
AeTM Site-NameOptional field that can be used to store the AeTM site name
Site CodeEntry of the AeTM main community (L1). The Site-code can only be used once in an agency
Main GroupDrop down of the travel groups from which one must select the main travel group
Travel Groups, Group ID, Description

Company related AeTM communities including free text description

Disconnect travellers from AeTMAll AeTM login names in the traveller profiles, AeTM Site Name, Site Code, Main Group and Travel Groups will be removed in Umbrella Faces. No profiles will be deleted in AeTM
Amadeus
Travel Department OIDRegister the Amadeus Office ID to which the profile will be synchronized. If the field is empty, the profile will be synchronized to the main office ID set on the agency
Travel Department Org-IDRegister the Amadeus Organisation ID (allocated to the OID) (optional - only needed if the profile should be synchronized to a different OID as the one set on the agency
Reporting Office

The Amadeus Office ID will be transmitted as "shadow destination" ( A.I.R - FK and ES element)

Cytric
Cytric serverEntry of Cytric server if differs form the standard agency setting
Cytric orgSearch of the respective Cytric Location and Divison for the profile
Disconnect travellers from CytricAll Cytric login names in the traveller profiles, Cytric Org Id and Travel Groups will be removed from Faces although the profiles will still stay in Faces. The profiles will not be deleted from Cytric either. The connection between Faces and Cytric is hence disconnected and profiles are retained in both systems separately
Main GroupDrop down of the travel groups from which one must select the main travel group
Travel Groups, Group ID, Description

Company related Cytric Travel Policy Group including free text description

PCCRegister the Galielo PCC to which the profile will be synchronized. If the field is empty, the profile will be synchronized to the main PCC set on the agency
Host Access Profile (HAP)

Enter the HAP corresponding to the above entered Galileo PCC

Agency LocationEntry of the 3-letter-Code where the agency/company is located. (Galileo Phonefield Element)
  • No labels