Spreadtables: Service Request and Tasks Not Sorted Properly (Doc ID 2175680.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Teleservice - Version 12.1.3 and later
Information in this document applies to any platform.

Symptoms

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

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 use ORDER BY TASK_NUMBER (or REQUEST_NUMBER).

 

Cause

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