Cross tab query dynamically.

Question

Hi,
i want to do crosstab in my query. but the data was not static its dynamic.
CREATE TABLE ABTEST
  SEC_ID      NUMBER,
  MONYEAR     VARCHAR2(10 BYTE),
  NUM         NUMBER
SET DEFINE OFF;
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200802', 13);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200803', 25);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200804', 26);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200805', 13);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200806', 10);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200807', 11);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200808', 5);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200809', 14);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200810', 17);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200811', 12);
Insert into ABTEST
WHERE
   (SEC_ID, MONYEAR, NUM)
Values
   (91, '200812', 12);
COMMIT;
Currently it looks like below.
SEC_ID     MONYEAR     NUM
91     200802     13
91     200803     25
91     200804     26
91     200805     13
91     200806     10
91     200807     11
91     200808     5
91     200809     14
91     200810     17
91     200811     12
91     200812     12
I want to display the data like below.
sec_id 200802 ........200812
91      13                12is there any can we do that by sql query or procedure. The dates are not limited its dynamic.
Please help meout.
Thanks & Regards,
Venkat.

Answer 1

Hi,
The number of columns has to be hard-coded.
If you don't know the number of columns until run-time, then you have to use dynamic SQL where, at run-time, you figure out how many columns are needed and write that many columns.
See the script below for one way of doing that in SQL*Plus.
How to Pivot a Table with a Dynamic Number of Columns
This works in any version of Oracle
The "SELECT ... PIVOT" feature introduced in Oracle 11
is much better for producing XML output.
Say you want to make a cross-tab output of
the scott.emp table.
Each row will represent a department.
There will be a separate column for each job.
Each cell will contain the number of employees in
     a specific department having a specific job.
The exact same solution must work with any number
of departments and columns.
(Within reason: there's no guarantee this will work if you
want 2000 columns.)
Case 0 "Basic Pivot" shows how you might hard-code three
job types, which is exactly what you DON'T want to do.
Case 1 "Dynamic Pivot" shows how get the right results
dynamically, using SQL*Plus. 
(This can be easily adapted to PL/SQL or other tools.)
PROMPT     ==========  0. Basic Pivot  ==========
SELECT     deptno
,     COUNT (CASE WHEN job = 'ANALYST' THEN 1 END)     AS analyst_cnt
,     COUNT (CASE WHEN job = 'CLERK'   THEN 1 END)     AS clerk_cnt
,     COUNT (CASE WHEN job = 'MANAGER' THEN 1 END)     AS manager_cnt
FROM     scott.emp
WHERE     job     IN ('ANALYST', 'CLERK', 'MANAGER')
GROUP BY     deptno
ORDER BY     deptno
PROMPT     ==========  1. Dynamic Pivot  ==========
--     *****  Start of dynamic_pivot.sql  *****
-- Suppress SQL*Plus features that interfere with raw output
SET     FEEDBACK     OFF
SET     PAGESIZE     0
SPOOL     p:\sql\cookbook\dynamic_pivot_subscript.sql
SELECT     DISTINCT
     ',     COUNT (CASE WHEN job = '''
||     job
||     ''' '     AS txt1
,     'THEN 1 END)     AS '
||     job
||     '_CNT'     AS txt2
FROM     scott.emp
ORDER BY     txt1;
SPOOL     OFF
-- Restore SQL*Plus features suppressed earlier
SET     FEEDBACK     ON
SET     PAGESIZE     50
SPOOL     p:\sql\cookbook\dynamic_pivot.lst
SELECT     deptno
@@dynamic_pivot_subscript
FROM     scott.emp
GROUP BY     deptno
ORDER BY     deptno
SPOOL     OFF
--     *****  End of dynamic_pivot.sql  *****
EXPLANATION:
The basic pivot assumes you know the number of distinct jobs,
and the name of each one.  If you do, then writing a pivot query
is simply a matter of writing the correct number of ", COUNT ... AS ..."\
lines, with the name entered in two places on each one.  That is easily
done by a preliminary query, which uses SPOOL to write a sub-script
(called dynamic_pivot_subscript.sql in this example).
The main script invokes this sub-script at the proper point.
In practice, .SQL scripts usually contain one or more complete
statements, but there's nothing that says they have to.
This one contains just a fragment from the middle of a SELECT statement.
Before creating the sub-script, turn off SQL*Plus features that are
designed to help humans read the output (such as headings and
feedback messages like "7 rows selected.", since we do not want these
to appear in the sub-script.
Turn these features on again before running the main query.
*/