Different Supplier when Create Order Proposal

​@ModinA 

The filter in OrderProposal is real, but it only tests the primary supplier

OrderProposalManager skips any part that fails Purchase_Part_Supplier_API.Include_In_Order_Proposal, and that function does:

IF (NVL(vendor_no_, string_null_) != '%') THEN   IF (Get_Primary_Supplier_No(contract_, part_no_) != vendor_no_) THEN      RETURN FALSE;   END IF;END IF;

Two consequences, and both bite:

1. It's primary supplier only. A part where 10071 is a valid supplier but not flagged primary is excluded. The parameter is not "parts I can buy from 10071", it's "parts whose primary supplier is 10071".

2. Parts with no primary supplier slip through. This is a bug.

Get_Primary_Supplier_No returns NULL when no purchase_part_supplier row for that site + part has primary_vendor = 'Y':

IF get_primary_vendor_no%NOTFOUND THEN   micro_cache_primary_vendor_no_ := NULL;END IF;

Then NULL != '10071' evaluates to NULL, not TRUE. The IF doesn't fire, RETURN FALSE never executes, and the part is included. Note the asymmetry in the code: vendor_no_ is wrapped in NVL, the left-hand side isn't.

Your screenshot confirms it. Requisitions 2429 (11993) and 2430 (11318) are precisely the two rows with a blank Supplier column, while every correctly-filtered row shows 10071. IFS found no primary supplier for those two parts and then failed to exclude them for exactly that reason.

The NULL handling looks unintended rather than designed. A part with no primary supplier matching every supplier filter isn't sensible behaviour, and the NVL on one side of the comparison but not the other suggests an oversight. Worth a support case; it's a small fix at that line.

(Traced in IFS Cloud 26.1.3 source: OrderProposalManager.plsql line 342, PurchasePartSupplier.plsql Include_In_Order_Proposal and Update_Cache_Impl___.)