EAI Siebel Adapter Query/QueryPage methods ignore BC Sort Specification
Last updated on APRIL 30, 2018
Applies to:Siebel CRM - Version 18.104.22.168 SIA  and later
Information in this document applies to any platform.
""Checked For Relevance on 02-Oct-2016""
As result the retrieved data appear in different order as these would be displayed in the list applet or obtained by custom browser and server-side script.
For standard tables, the user key columns will be used to sort being retrieved table records using the accordant index.
For example: if one defines a standard Busines Component /BC) based on the S_ORG_EXT table and sets BC Sort Spec. property to "Intgeration Id (ASC)" field (this field is mapped to the "INTEGRATION_ID" column),
the EAI Query will use the "NAME" and "LOC" columns in the ORDER BY clause to sort returned records from the S_ORG_EXT table. while Siebel UI will display records obtained with the ORDER BY INTEGRATION_ID clause.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms