Humanitarian and Marine Products
HUMANITARIAN and MARINE Products |
|---|
Humanitarian and Marine are private products holding advantages for NGOs, Vessel or Platform workers.
Presently, the purchase of these products is available in instant purchase scenarios and on hold flows, and must be requested during the booking process.
It should be noted that all passengers must work or be assigned to the same NGO or Vessel company accordingly, since this inclusion is unique to each Order.
In order to correctly complete the additional information:
For Humanitarian product, the NGO Organization Name is the applicable element.
For Marine product, the name of the vessel or platform, along with the Country it is registered to, need to be included.
Please, find the codes and format to be used shown in the table below:
Product Type | Code to be used |
|---|---|
HUMANITARIAN | HUMN/Organization Name |
MARINE VESSEL | SEMN/Vessel Name/Country |
MARINE PLATFORM | OFSH/Platform Name/Country |
Note: As of today, some of the characters that are allowed (accents, symbols, punctuation marks, among others): “ñ” “Ñ” “-” “/” “ó” “ò” “ô” “ö” “ç” “ã” “.” “,” “(“ “)” “*” “#” ”?” “¿”
In case the NGO, Vessel or Platform name contains non-permitted characters, an error will be returned, preventing the Order from being created. You will find a specific scenario of this in our Warning Messages for Humanitarian and Marine Products page.
This information must be inserted in the InstructionList section within the DataLists, whose values will be displayed within the Remark section of the messages, later explained in this page, and supported by following examples:
AirShoppingRQ |
In the AirShoppingRQ we introduce the FarePreferences type code as in our Private Fare Types table, corresponding to Humanitarian and Marine products.
Below, two snippets of codes from both products from different Orders:
<Preference>
<FarePreferences>
<Types>
<Type PreferencesContext="HUMANITARIAN">758</Type>
</Types>
</FarePreferences>
<FlightPreferences>
<...>
</Preference><Preference>
<FarePreferences>
<Types>
<Type PreferencesContext="MARINE">758</Type>
</Types>
</FarePreferences>
<FlightPreferences>
<...>
</Preference>
AirShoppingRS and OfferPriceRS |
In the response, the product requested is returned in the DescriptionList and FareList. Again, examples from different Orders:
<DescriptionList>
<Description ObjectKey="HUMANITARIAN">
<Text>HUMANITARIAN</Text>
</Description>
</DescriptionList>
<...>
<FareList>
<FareGroup refs="HUMANITARIAN" ListKey="NDL0NQM7H">
<Fare>
<FareCode>758</FareCode>
</Fare>
<FareBasisCode>
<Code>NDL0NQM7H</Code>
</FareBasisCode>
</FareGroup>
</FareList>
OrderCreateRQ |
|---|
Being the product previously requested in the AirShoppingRQ, in the InstructionsList section of the OrderCreateRQ we will include the NGO name, the Vessel or Platform name the employees are assigned to as Humanitarian or Marine product accordingly.
This process can also be carried out in instant purchase and On-Hold scenarios.
When requesting the Humanitarian product, only the NGO Organization, in which passengers are employed, will be available for inclusion as shown in the example below HUMN/NACIONES UNIDAS.
As per the Marine product, and depending on whether the employees are assigned to a Vessel or Platform company, will be available as shown below, SEMN/Vessel Name/Country OFSH/Platform Name/Country.
Note1: Unlike the Sport Product, Humanitarian and Marine products will not be included in the InstructionsList in the OrderViewRS.
Note2: If these formats are not correct, a warning message will be returned (since the company has not been included), not preventing the Order from being created. Please, visit our Warnings Messages page to learn more about the warning scenarios related to both Humanitarian and Marine products.
Examples of messages with complete flows can be downloaded from here.
