Spreadtables: Service Request and Tasks Not Sorted Properly by Number (i.e. Find Service Request, Tasks tab) (Doc ID 2175680.1)

Last updated on JULY 21, 2020

Applies to:

Symptoms

Service Request (SR) or Tasks are not sorted in ascending/descending order properly based on SR or Task numbers.

For example:
In the "Find Service request" form, when searching for a SR by giving some parameters, the results are not sorted correctly when trying to arrange the results in ascending or descending order of the Service Request number.

Expected Behavior:

When you sort a set of SRs or Tasks (say 108743, 89786, 90312, 100337, 19824), the expected output would be:

     19824
     89786
     90312
   100337
   108743

However, it considers all the elements starting with '1' as the lowest value, producing the following output:

  100337
  108743
  19824
  89786
  90312

A similar behavior can be observed when using SQL*Plus, against the base views (JTF_TASKS_V or CS_INCIDENTS_ALL_B) and using ORDER BY TASK_NUMBER (or REQUEST_NUMBER).

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.