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

Customer will be able to select a specific Sub SSR form the Multiple Sub SSRs available in Bundle SSR across flight segments in Connection as well as Direct Flights

Effective Date

APIs Affected

NDC 17.2 ServiceList

Problem/ Issue

Initially the different segments of connection flight refers to the same bundle SSR with Child having multiple Sub SSRs , so different sub SSR selection for each segment is not possible, this issue exists for direct flight also.

Solution

From now on wards if a Bundle SSR having Child with multiple sub SSRs (Out of multiple SUB SSRs only one need to choose by a passenger), There will be unique Service Definition for each Bundle SSR with unique ServiceDefinitionIDs and Service Definition element  depending up on the no: of flight segments/leg in the PNR. Also there will be unique ServiceDefinitionIDs and Service Definition element  for the Child SSR having the Sub SSRs depending up on the no: of flight segment/leg in the search

ALaCarteOfferItem of each segment/leg will be available in the ServiceListRS linked to respective Passengers (PassengerRefs), Segments (SegmentRefs) and corresponding Service Definition ID (ServiceDefinitionRef).

In case of Connection flights, there will be a ServiceRef used to link the ALaCarteOfferItem of the connection flight segments. The first ALaCarteOfferItem will be linked with the second ALaCarteOfferItem using the ServiceRef. This is to handle Pax/O&D fees defined for the Bundle SSR. If the fee is a Pax/O&D application level, the Fee amount of the Bundle SSR will be available in the ALaCarteOfferItem without ServiceRef element and the ALaCarteOfferItem with the ServiceRef element, the fee amount will be updated as zero.

In case of Pax/Segment application type fee will be available in the each ALaCarteOfferItem.

Example of the ALaCarteOfferItem link in case of Connection Flight:

  1. First ALaCarteOfferItem of a connection flight without ServiceRef

2. Second ALaCarteOfferItem of the connection flight with ServiceRef, which is linked to first ALaCarteOfferItem

Critical Impact

LOW- This will not impact any breaking change to the consumption of iFlyRes 17.2 NDC APIs. Change is only for the Bundle SSR having Multiple Sub SSRs in ServiceListRS.

Remarks

This change is only applicable for Bundle SSR having a Child with multiple Sub SSR, all the other Normal SSRs and Bundle SSR without Sub SSRs will not have any changes from current implementation.

  • No labels