Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Special Seat Request in PNR_AddMultiElements #174

Closed
shaiby opened this issue Apr 6, 2018 · 8 comments
Closed

Special Seat Request in PNR_AddMultiElements #174

shaiby opened this issue Apr 6, 2018 · 8 comments

Comments

@shaiby
Copy link

shaiby commented Apr 6, 2018

I was trying to send special seat request. Here is what amadeus respond with the new preference

In this scenario, the issue is the NSSW (Non-smoking window seat) request. This is no longer supported by most airlines. In order to make a request for a preferred seat, please use the STR as below:

   <dataElementsIndiv>
      <elementManagementData>
        <reference>
          <qualifier>OT</qualifier>
          <number>1</number>
        </reference>
        <segmentName>STR</segmentName>
      </elementManagementData>
      <seatGroup>
        <seatRequest>
         <special>
            <seatType>A</seatType>
          </special>
        </seatRequest>
      </seatGroup>
      <referenceForDataElement>
        <reference>
          <qualifier>PT</qualifier>
          <number>1</number>
        </reference>
      </referenceForDataElement>
    </dataElementsIndiv>

In the seatType node, you can send the following:

A Aisle seat
H Seat with facilities for Handicapped/incapacitated
I Seat suitable for adult with an infant
K Bulkhead seat (B in customer profile)
MA Medically OK for travel
N No smoking seat
S Smoking seat
U Seat suitable for unaccompanied minor
W Window seat

But using class preference, it never add the tag in seat request...that's what cause the response to invalid. Is there any luck regarding this. Here is class generated XML in request that differ from Amadeus recommendation.

<ns1:dataElementsIndiv>
    <ns1:elementManagementData>
        <ns1:reference>
            <ns1:qualifier>OT</ns1:qualifier>
            <ns1:number>2</ns1:number>
        </ns1:reference>
        <ns1:segmentName>STR</ns1:segmentName>
    </ns1:elementManagementData>
    <ns1:seatGroup>
        <ns1:seatRequest>
            <ns1:seat>
                <ns1:type>A</ns1:type>
            </ns1:seat>
        </ns1:seatRequest>
    </ns1:seatGroup>
    <ns1:referenceForDataElement>
        <ns1:reference>
            <ns1:qualifier>PT</ns1:qualifier>
            <ns1:number>2</ns1:number>
        </ns1:reference>
        <ns1:reference>
            <ns1:qualifier>ST</ns1:qualifier>
            <ns1:number>1</ns1:number>
        </ns1:reference>
        <ns1:reference>
            <ns1:qualifier>ST</ns1:qualifier>
            <ns1:number>2</ns1:number>
        </ns1:reference>
    </ns1:referenceForDataElement>
</ns1:dataElementsIndiv> 
@DerMika
Copy link
Collaborator

DerMika commented Apr 6, 2018

Which version of PNR_AddMultiElements do you have in your WSAP?

@shaiby
Copy link
Author

shaiby commented Apr 6, 2018

this is I think PNRADD_16_1_1A

@DerMika
Copy link
Collaborator

DerMika commented Apr 9, 2018

The problem is that I don't find any samples on Amadeus' Extranet . What I have implemented is sample:

5.41 Operation: Seat Request

in the PNR_AddMultiElements user guide.

Can you point me to some Amadeus documentation regarding this new way to add Seat requests to the PNR?

@DerMika
Copy link
Collaborator

DerMika commented Apr 9, 2018

I've implemented it, calling it "Special Seat Type" for now. It's available on dev-master

I'm waiting to see if you can dig up any documentation which could give me a clue as to how to name this feature better.

@bimusiek
Copy link
Collaborator

bimusiek commented Apr 9, 2018

You can add seat request as SSR element as well. If you just want to specify if window or aisle.
NSSW is for window and NSSA for aisle.

@shaiby
Copy link
Author

shaiby commented Apr 10, 2018

I am sorry for being late in response...Yes you are correct...its name should be Special Seat Type Request. The help documentation is same as I post in issue statement.

@DerMika
Copy link
Collaborator

DerMika commented Apr 10, 2018

In that case you can test the new feature on the master. I'll release it with 1.7.0.

@DerMika DerMika closed this as completed Apr 10, 2018
@DerMika
Copy link
Collaborator

DerMika commented May 2, 2018

Version 1.7.0 has been released!

@DerMika DerMika added this to the 1.7.0 milestone May 2, 2018
@DerMika DerMika changed the title Special Seat Request in Pnr_addMultiElemenst Special Seat Request in PNR_AddMultiElements May 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants