Answer
Use the ServiceQuotationUtil entity together with the SRV_QUOTATION_SERVICES view instead — that combination actually holds the origin/connection information for a Service Quotation (whether it came from a Customer Order or a Work Order), where SERVICE_QUOTATION_CONN itself turns out to be sparsely populated and isn't the right source for this.