INTEGRATION-Invalid BF/SA combination is not returning distribution field in demand map response

Ramesh,

It appears that some of the responses coming back from TSA (DEV) are invalid (miising the mandatory distribution field)

An example request

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:dem="http://demandmap.mms.thesearchagency.com/">

<soapenv:Header/>

<soapenv:Body>

<dem:provideDemandMaps>

<!-Optional:->

<provideDemandMapsReq>

<!-1 or more repetitions:->

<demandMapRequest>

<businessFunctionServiceArea>

<businessFunctionID>1000001138</businessFunctionID>

<serviceAreaID>715</serviceAreaID>

</businessFunctionServiceArea>

<preferSearchEngineOrigin>true</preferSearchEngineOrigin>

<distribution>BING</distribution>

</demandMapRequest>

</provideDemandMapsReq>

</dem:provideDemandMaps>

</soapenv:Body>

</soapenv:Envelope>

Is returning :-

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">

<env:Header/>

<env:Body>

<ns2:provideDemandMapsResponse xmlns:ns2="http://demandmap.mms.thesearchagency.com/">

<provideDemandMapsResp>

<demandMapResponse>

<returnCode>invalidBusinessFunction</returnCode>

<demandMap>

<businessFunctionServiceArea>

<businessFunctionID>1000001138</businessFunctionID>

<serviceAreaID>715</serviceAreaID>

</businessFunctionServiceArea>

<minimumPrice>0.0</minimumPrice>

<maximumPrice>0.0</maximumPrice>

<minimumClicks>0.0</minimumClicks>

<maximumClicks>0.0</maximumClicks>

</demandMap>

</demandMapResponse>

</provideDemandMapsResp>

</ns2:provideDemandMapsResponse>

</env:Body>

</env:Envelope>

I suspect this is the case when the BF/SA combo is unknown - I've checked the list of valid BF's that Jo provided and can see that 1000001138 is not on there but the test data that we have has some campaigns using this.

I believe that the ESB service would normally set the budget figures to the 'default' values in this case but because you are not passing back a valid response (against your WSDL/XSD) this is not happening....

This is causing the ESB service to fail and hence the front-end !