OTM selects wrong deconsolidation Pool while doing bulk plan

Hi Friends,

We have Deconsolidation pool config like:
Location A ---> PoolA ---> Pool A Zip codes (serving few zip codes of CA)
Location B ---> PoolB ---> Pool B Zip codes (serving entire zip codes of CA and WA)

Two seperate multi-stop itineraries are configured for Location A -> Pool A zip codes and Location B -> Pool B zip codes in system.
We created a location profile (contains location A compatible pool locations) and assigned to Location A - Pool A itinerary to avoid selecting pool B locations while do bulk planning.

Bulk plan contains orders from Location A to CA Zip codes and Location A to WA Zip codes.
We are expecting system to build pool shipments/direct shipments based on the optimal planning of OTM, but system is planning pool shipments using Pool B location as deconsolidation pool and that is wrong.

Based on our investigation from log file, we found that OTM is looking for a matching common pool for orders from Location A to CA zip codes and Location A to WA zip codes and is picking Pool B location instead of Pool A location since Pool B has both Zip codes (CA and WA)

Any help is highly appreciated

Thanks,
Arun