How to create an OSI element in the Amadeus PNR?

Note: An OSI element is not a Service Request (SR) and does not require a confirmation from the airline. Unlike SSR elements, OSI elements do not result in the automatic placement of PNRs on the queue if a response is received from the airline.

To create an OSI: the mandatory items are the transaction code OS and the two-letter code of the airline to which the information is to be sent.

• When you want to advise more than one airline in a PNR, use the generic airline code YY. If an OSI element is not passenger associated, the system assumes it belongs to all passengers
• Every new PNR that is created by a travel agency has an OSI CTCT element automatically created by the system. This contact element contains the IATA city code, telephone number, and agency name
• All information contained in the OSI element is taken from the travel agency office profile
• Segment association is not allowed - you will receive an error message SEGMENT ASSOCIATION IS NOT ALLOWED

Transaction code	Explanation
OS 6X VIP ABC CORP/P2 (General information)
OS	Transaction code
6X	Airline code of the airline to be advised. Note1: in a single PNR (a PNR containing codeshare segments that have been merged into a single segment), you can enter the OSI entry with the marketing or the operating carrier code. For this reason, you may see a carrier code in the OSI element that does not appear in the itinerary. Note2: Use YY (for the airline code) if you want to advise more than one airline in a PNR.
VIP ABC CORP	Free-flow text
/P2	Slash, passenger association. Include passenger association if the information applies to a particular passenger or passengers. If no passenger association is specified in the entry, the system applies the OSI element to all passengers in the PNR.
OS 6X TKNO 172-1234567890/P4 (Single ticket number)
OS	Transaction code
6X	Airline code of the airline to be advised
TKNO	Transaction code
172-12345678901	Ticket number (transmits a single number) Note: the required format for sending ticket numbers differs between airlines. Some airlines require an SSR element rather than an OSI element. For airline specific information, enter: HE TICKETNUMBER, GP MTN
OS 6X TKNO 172-1234567890-91 (Conjunction ticket)
OS	Transaction code
6X	Airline code of the airline to be advised.
TKNO	Transaction code
172-1234567890-91	Ticket numbers (transmits a number range) Note: the required format for sending ticket numbers differs between airlines. Some airlines require an SSR element rather than an OSI element. For airline specific information, enter: HE TICKETNUMBER, GP MTN
/P4	Slash, passenger number (to enter SSR elements for selected passengers, you add passenger association
OS 6X ARR CTCH JOE SMITH SFO 212 555 5555 (Adult collecting unaccompanied minor on arrival)
OS	Transaction code
6X	Airline code of the airline to be advised
ARR	Transaction code
CTCH	Contact home telephone code
JOE SMITH SFO 212 555 5555	Name of the adult collecting the unaccompanied minor on arrival and telephone number.
OS 6X DEP CTC HKG 212 555 1212 /MRS SMITH /MOTHER (Adult leaving unaccompanied minor at departure)
OS	Transaction code
6X	Airline code of the airline to be advised
CTC	Contact code
HKG 212 555 1212 /MRS SMITH /MOTHER	True city code, telephone number, slash, name of the person leaving the unaccompanied minor at departure, slash, relation to minor.
OS 7X DOB 15MAR11 (Date of birth of unaccompanied minor)
OS	Transaction code
7X	Airline code of the airline to be advised
DOB	Date of birth code
15MAR11	Date of birth

For information: THE SERVICE INFORMATION CAN BE ANY TEXT OF YOUR CHOICE. THE ENTRY CAN CONTAIN A MAXIMUM OF 68 CHARACTERS. A PNR CAN CONTAIN A MAXIMUM OF 127 OSI ELEMENTS. 

Codes used in OSI elements

CTC CONTACT This is the TRUE CITY CODE, plus primary phone number, plus office name from the office profile. It is sent to all airlines in the itinerary if the PNR was created in an airport or city ticket office (ATO/CTO). CTCE The Format uses AIRIMP (Interline Message Procedure) standards (listed below) and must follow the format exactly to be read by the airline. Two forward slashes // are used in place of the @ symbol Two periods .. are used in place of an underscore line CTCE/ CTCE CTC/ CTC identifies the POS as an email address Example: SI DL CTC CHRIS.TRAVELER//YAHOO.COM *Note: for multiple e-mail addresses, use separate OSIs CTCT Contact - Travel Agency phone This is the TRUE CITY CODE, plus primary phone number, plus office name from the office profile. It is sent to all airlines in the itinerary if the PNR was created in a travel agency CTCP Contact - AP phone This is the phone number that you entered using one of the following: The AP transaction, provided that APO is set to Y in the office profile. The APS transaction Note: airlines that do not wish to receive this information can suppress its transmission. CTCM Contact - Mobile phone This is the mobile phone number that you entered using the APM transaction. The message is generated provided that APO is set to Y in the office profile, and the airline wishes to receive this information. APA, APB, APE, APF, APH, API, APX These contact elements do not generate an OSI message ARR Arrival CONT Continuing CONX Connection CTCA Contact - Address CTCB Contact - Business address CTCH Contact - Home phone PWCT Passenger will contact TCP The complete party is VIP Very important passenger