Versions Compared

Version Old Version 1 New Version Current
Changes made by

Valentina Maio (Unlicensed)

Alvaro Chaparro

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Errors will always be shown in the applicable response message(ServiceListRS, OrderViewRS).

Scenarios

Scenario 1 - SSR requested in OfferPrice and then also in ServiceList

Formerly, these services could only be requested in the OfferPrice Service, and subsequently booked in OrderCreate. As explained in our Special Service Request page, they can now be requested in both the OfferPrice and the ServiceList messages. We recommend any new developments use the ServiceList, and those using the OfferPrice migrate to the ServiceList asap, as any new Special Services offered will more than likely only be offered through the ServiceList API.

...

The SSR code introduced is not among the ones listed in this table or is incorrect.

ServiceListRQ / OfferPriceRQ

ServiceListRS

In ServiceListRQ, the code DPNA ir incorrectly spelled in this case:

Code Block
languagexml
<Qualifier>
	<SpecialNeedQualifiers>
		<Code>DPRA</Code>
	</SpecialNeedQualifiers>
</Qualifier>

Error returned in ServiceListRS:

Code Block
languagexml
<Errors>
	<Error ShortText="NDC_DIST_SPNE_0003" Code="486">SPECIAL_NEED: Service code is not offered.</Error>
</Errors>

...

Special Service Requests are NOT available in Post-Sale scenarios.

ServiceListRQ

ServiceListRS

In ServiceListRQ with Order, we request the SSR code for Wheelchair for Steps (WCHS):

Code Block
languagexml
<Qualifier>
	<SpecialNeedQualifiers>
		<Code>WCHS</Code>
	</SpecialNeedQualifiers>
</Qualifier>

Error returned in ServiceListRS:

Code Block
languagexml
<Errors>
	<Error ShortText="NDC_DIST_SPNE_0001" Code="486">SpecialNeedQualifiers not available.</Error>
</Errors>

...