We are encountering an issue in the generate#CreateOrderFeed service where orders containing mixed shipment methods are being included in both "include" and "exclude" feeds during the generation of order feeds for NetSuite.

Context:

1. The service uses the EligibleOrdersForNetSuiteView to fetch eligible orders based on conditions such as:
   • orderId
   • fromOrderDate and thruOrderDate
   • includeShipmentMethod (e.g., POS_COMPLETED)
   • excludeShipmentMethod (e.g., POS_COMPLETED)
2. Orders are scheduled for processing in two scenarios:
   • Include Feed: Includes orders with POS_COMPLETED shipment methods.
   • Exclude Feed: Excludes orders with POS_COMPLETED shipment methods.

Problem:

For orders with mixed shipment methods (e.g., one order item has POS_COMPLETED, and another has STANDARD), the order satisfies the conditions for both scenarios:

• It gets included in the Include Feed because it has an item with the POS_COMPLETED shipment method.
• It gets included in the Exclude Feed because it also contains an item with a different shipment method.

This leads to making this order eligible in both feeds.

Root Cause:

• The current logic in the EligibleOrdersForNetSuiteView operates at the OrderHeader level and does not differentiate orders based on their item-level shipment methods.
• The conditions applied (IN or NOT IN for shipment methods) are evaluated at the order level, causing mixed shipment method orders to match both include and exclude criteria.