Apex IR report with Heading label

i have IR report with 15 column with heading..
The end user can accessing from different department, when the user can see the report shown only their particular department rows only. each department have different column value and Header label .how can display the column header depend on the department user.
e.g. IR report view
Seq# -- Department -- date -- Subject/Customer Message
1                          Communication done with Jony(from HR department)
2                          low sales from East region(from Sales Department)IN the IR report Table data structure.Heading_code value as LOV in IR form(1.Subject/2.Customer Message/ect...) and Column_value as Text Field.
Seq# -- Dept_name -- Heading_code --  Column_value
1        HR              1           Communication done with Jony
2        Sales           2           low sales from East regionApex have limitation of one IR report in one page. so i could not create different Report region even i don’t want create another page due to the further functionality issue.
Thanx,
Ram

I'm glad you could apply that approach. I'm not crystal clear on what is needed but I have a few general ideas.
1) If there will only have 3 or 4 classes (types) of users, you might try using a CASE statement in a Before Header process:
BEGIN;
  CASE
    WHEN condition for 'KAC' THEN
         SELECT [first label constant or variable], [second label], ...
              INTO &Px_COL_HEAD1., &Px_COL_HEAD2, ... FROM ... ;
    WHEN condition for 'MIS' THEN
         SELECT [first label constant or variable], [second label], ...
              INTO &Px_COL_HEAD1., &Px_COL_HEAD2, ... FROM ... ;
    WHEN  condition for "ADMIN"  THEN
         SELECT [first ADMIN label constant], [second ADMIN label constant], ...  
              INTO &Px_COL_HEAD1., &Px_COL_HEAD2, ... FROM ... ;
    ELSE -- default case
         SELECT [default first label constant or variable],
                     [default second label constant or variable], ...  
              INTO &Px_COL_HEAD1., &Px_COL_HEAD2, ... FROM ... ;
    END;
END; NOTE: Do not make the "ADMIN" case the default. That seems like a security hole. I would always want a data check for the ADMIN case.
2) Or put the above code in an Application Process rather than a Page (Before Header) Process so it's only computed once.
Does that give you some ideas?
Regards,
Howard

Similar Messages

  • Apex tabular report with title heading

    hi all,
    I want to create a apex report that is downloadable ( is that download or upload? I am confused about the term) anyways a report the is covertible to excel spreadsheets format, but I want it including the title of the report too printed on the excel file, when the user click the download link.
    example:
    SALES STATISTICS FOR
    JAN-08 to DEC-09
    PRODUCT_NAME    JAN   FEB    MAR   APR   MAR  JUN   JUL  AUG   SEP    OCT    NOV   DEC   TOTAL
    product1               10     15         9    7       0       2       1    8      10      12      20      15      105
    product2                0        0         0   0       0        0       0    0       0       0        0        0          0
    .Thanks a lot

    This is possible in later versions of Apex by clicking the Print Attributes tab when you edit the report. In there is a Page Header region that allows you to create you report title. This is available in both Standard and Interactive reports.
    Is this what you meant or is there a twist.
    Cheers
    Shunt

  • What is the best way to create a SSRS Report with Header Data and its associated child data

    So I have Member Information...Member ID...Member Addressing...etc.. I want to display this in the top part of the report like...
    Member Name:
    Member ID:
    Member Address Line 1:
    And then below I want to report on all the claims associated with a Member ID that is chosen by the Parameter. Obviously the Claim Data will be in Table format. Do I necessarily have to associate the Member Information with the Claim Information or simply
    use the same parameter? And what is the best Toolbox item to use to display the Member Information on top?
    Any help or guidance is greatly appreciated by this newbie.
    Thanks for your review and am hopeful for a reply.
    ITBobbyP

    Hi ITBobby,
    According to your description, you want to display all Claim Data for each Member. Right?
    In Reporting Services, we can use a table to display those Claim Data and make them group on Member ID. If you want to display the Member Information, we can put the data fields on parent group level. Then we can use create a parameter to filter the Member
    ID we need. We have tested this scenario in our local environment. Here are steps and screenshots for your reference:
    1. Create a DataSet(DataSet1) which contains the data fields of Member and Claim.
    2. Create a table and drag the Claim data into the table.
    3. In Row Group. Right click on Details and add a parent group.
    4. Select Member_ID in Group by.
    5. Right click on the textbox of Claim data. Select Insert Row->Outside of Group-Above. Drag the MemberName into the inserted row.
    6. In Report Data, right click on Parameter-> Add Parameter.
    7. Type Member_ID in Name and Prompt, select allow multiple values.
    8. In Available Values, select get data from a query. Choose DataSet1, select Member_ID in values and label. You can also set this in Default Values if you need.
    9. Save and preview.
    Reference:
    Understanding Groups (Report Builder and SSRS)
    Report Parameters (Report Builder and Report Designer)
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • Exporting a report with barcode label fails

    Post Author: Jega
    CA Forum: Exporting
    When i try to export a report which has a barcode label in it, the export fails "Font is not allowed to be embedded in the report"

    Post Author: V361
    CA Forum: Exporting
    A few questions....   If you print, does it work ok ?  What type of export, Word, Excel, PDF ?, What version of CR do you have ?

  • How to create report with Fixed Labels and Dynamic Columns

    I have static column labels in left side of report and field in 3 columns coming dynamically from 3 different command queries.
    Please let me know how to create it..Following is the sample data for report.

    Following is the sample report. Left side lables are fixed.
    I tried using pivot table functionality, earlier discussed in the forum.
    But they are creating huge no.of records. As it will turn the rows into columns.
    Is there any way to get this report done normally.?

  • Problem with Apex layout report  XSL-FO build by bi-publisher word plug-in

    Hi all...
    this is what I should do:
    - generate a layout with bi-publisher word plug-in ---> it's ok
    - export this layout in xsl-fo stylesheet --> it's ok.
    - create an apex layout report with xsl-fo stylesheet --> it's ok.
    - create an apex query report with the above layout
    At this point when I test the report I have a corrupted pdf file....
    can you help me!!!
    Many thanks
    araf

    Hi,
    do you use BI Publisher or another XSL-FO-Engine? Is BI Publisher running? Is it configured in the instance settings?
    Regards
    Rainer

  • SQL Report with Scroll - javascript

    This is an example of Apex SQL Report with Scroll - made with javascript: http://tryapexnow.com/apex/f?p=12090:9
    Waiting for comments here.

    Yes, because of the page generated by APEX, if you use the Report Template APEX 4.0 Standard, the div created for the report table has the ID "with_scroll" but there is another div which actually contains the table, and it's ID is "report_with_scroll", they just add a "report_" in front of it.
    I find the table by searching through the childs of that div: var table = document.getElementById(myRegion).rows[1].cells[0].firstChild;
    You can use the first one, with the ID "with_scroll", but this code line will be longer.
    Also to addapt the script for other report templates, you just need to see the code generated by every template, and correct this line, to get the real table containing your report.

  • Custom Report with 3 Header lines and three separate detail lines

    Need help in creating a report:
    Objectives - break on hidden first field with a horizontal line for the separator (no summing)
    Expand/collapse detail lines with resetting pagination for that page based on this action. (1-15 select list)
    Header 1 Header 2 Header3 Header4 Header5 Header6
    Header 1a Header2a Header3a Header6a
    Header3b Header4b Header5b
    (-)Detail1 field Detail1 field Detail1 field Detail1 field Detai1l field Detail1 field
    (-)Detail2 field Detail2 field Detail2 field Detail2 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    (-)Detail2 field Detail2 field Detail2 field Detail2 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    (-)Detail1 field Detail1 field Detail1 field Detail1 field Detail1 field Detail1 field
    (-)Detail2 field Detail2 field Detail2 field Detail2 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    Detail3 field Detail3 field Detail3 field Detail3 field
    (+)Detail2 field Detail2 field Detail2 field Detail2 field
    (-) = collapse ; (+)= expand
    Edited by: user1073751 on Sep 23, 2010 6:30 PM

    Hi cupboy1,
    According to your description, you want to design your report as the screenshot your post and hide the detail row until select in top parent group. Right?
    In this scenario, we can design the report as you have done by yourself, then delete the column (Label), but still keep the Label group, then add a column left of Disc, put the data field into appropriate textbox. You can get the same effect as your first
    screenshot. And we can hide the detail rows and set them toggled by Artist. We have tested your case in our local environment. Here are steps and screenshots for your reference:
    1. Create a table. Drag Disc into textbox, add parent group with header (group on Label) for Disc, add parent group with header (group on Artist) for Label.
    2. Delete the column Label, add a column left of Disc.
    3. Right click on detail rows, select Row Visibility. Set hide and toggled by Artist.
    4. Save and preview. It looks like below:
    Reference:
    Row Visibility Dialog Box (Report Builder)
    If you have any question, please feel free to ask.
    Best Regards,
    Simon Hou

  • Interactive Report With No Column Heading

    Is it possible to display a column with no heading (label) in an interactive report ?
    I have tried to delete the column heading and save, but when I run the report,
    it is still there
    Cheers
    Gus

    Gus,
    Try a space character or  
    Vikram

  • Custom Rowtype Template with apex.widget.report.sort() - does this work?

    Hi Folks!
    I have a report with a custom rowtype template (3 rows for each dataset) and I have fiddeled around with the build-in javascript sorting-function. (Cause as it seems you can't use the standard sorting functionality on custom rowtemplates.) I came up with a short solution, but I would like to know how safe this is.
    Setup very simple:
    The Header-Template [before rows]
    <table id="myDomId">
        <thead><tr>
            <th><a href="javascript:sortCol(1)">Col1</a></th>
            <th><a href="javascript:sortCol(2)">Details</a></th>
            <th><a href="javascript:sortCol(3)">Col3</a></th>
        </tr></thead>
    Then the javascript handling runs like that:
    var qmmSorter = {};
    $(function(){
       setupSorters();
    function setupSorters(){
        qmmSorter.DomCatch = /\d+/.exec($('#myDomId>div').attr('id'))[0];
        qmmSorter.lastCol = 1;
        qmmSorter.asc = true;
    function sortCol(colnum){
    //console.log(colnum);
        if (qmmSorter.DomCatch) {
            qmmSorter.lastCol = colnum;
            qmmSorter.asc = !qmmSorter.asc;
            javascript:apex.widget.report.sort( qmmDomCatch,'fsp_sort_'+colnum + ( qmmSorter.asc ? '' : '_desc') );
    Maybe I'll also add some arrows to indicate what sorting took place. Tested so far in IE9 and Moz - all we really use in our internal network.
    But this seems all a bit just too easy. so I'd be really thankful for your comments.
    Tanks and greetings,
    Tobi

    TobiP wrote:
    But this seems all a bit just too easy. so I'd be really thankful for your comments.
    It would be even easier to use column header substitution and retain the built-in sort functionality (although this includes the sort direction image bug).
    <table id="myDomId"> 
      <thead><tr>
        <th>#1#</th>
        <th>#2#</th> 
        <th>#3#</th> 
      </tr></thead>

  • Report With Two Heading

    Hi,
    How to create Report With Two Heading
    [http://apex.oracle.com/pls/apex/f?p=267:31:]
    thanks

    See: Re: Two level row header

  • Performance issues ..with apex in reports version 3.1

    Hello All,
    I am using apex 3.1 oracle 10g.
    I am facing with performance issues with apex . I am generating iteractive reports with apex and the number of records are huge - running in 30 to 40 thousands of records and the reports is taking almost 30 minutes.
    How I can improve the performance of this kind of report. I am using apex collections.
    How apex works in terms of retrieving the records -?
    Please let me know .
    Thanks/kumar
    Edited by: kumar73 on Jun 18, 2010 10:21 AM

    Hello Tony ,
    The following are the sequence of steps to run the test case.
    Note:- All the schemas , tables and variables are populated from database.
    From Schema and Relations tab choose the following:
    1)     Select P3I2008Q4 as schema.
    2)     Choose Relation as query path.
    3)     Select ECLA, ECLB, MTAB as relations.
    From Variables choose the following:
    4)     Choose the variables AGE_SEXA,CLODESCA,ALCNO from ECLA relation.
    5)     Choose the variables AGE_SEXB, ALCNO, CLODESCB from ECLB relation.
    6)     Choose the variables EXPNAME, ALCNO, COST_, COST from MTAB relation.
    From Conditions: Click the Run Report button this generated standard report ( Total no of records in report – 30150 )
    Click on Interactive report button –to generate an interactive report. ( Error occurred )
    We are using return sql statement in generationg the standard report and collections for interactive report.
    thanks/kumar

  • SSRS subreport with a sub-report as header on all pages

    Hello,
    I need some guidance on how to get a sub-report with a sub-report header and an expanding table. Please see below.
    This is the structure of things that I have:
    Main Report 1 is being invoked by ONLY Parameter 1 (User Text Box Entry).
    It Contains:
         Page 1: Sub-Report 1 invoked by Parameter 1
         Page 2 or more Pages: Sub-report 2 and a table (T1) expanding vertically based on Parameter 1 and Parameter 2. The Sub-report 2 should appear as header on all pages where T1 rows are there. Additionally, multiple Parameter 2
    values may be present and if so, they need to appear on a different page with appropriate header/table data. Parameter 1 and 2 are associated with a ONE dataset & its fields.
         Last Page: Sub-Report 3 and few text boxes below it. Invoked by Parameter 1
    The issue is I don't know how to insert Page 2 content. I tried making a new report with Sub-report 2 and the T1 below it. This is working fine but I'm not able to get the sub-report as header on all pages EXCEPT the first page. FixedData and RepeatOnNewPage
    properties are TRUE & KEEPwithGroup is set to 'AFTER'. Also, once I'm done with this report how do I insert it in the main report. Would it be in group / outside group in the group properties -- I would really appreciate if you can guide me with steps.
    Thank you,
    Nichesl
    Nichesl

    Thanks Asha ,
    Actually this is how my Report  layout is
    Group Header
    ---Detail1
    ---Detail2
    ---Detail3
    Group Footer1 (New Page After and Show at Bottom Setting)
    Group Footer 2 (New Page Before Setting)
    This is the layout of my report.
    When Details and Group Footer1 come in same page then my Group Header works perfect.
    When there are many details then the Group Footer1 skips into next page and Group Header does not show up in that page.
    Our requirement is such a way that Group Footer1 should have Group Header and Group Footer2 should always come in new page (i.e. last Page)
    I think I made it clear on my issue/requirement.
    Again I really appreciate for your reply.
    Regards
    Kalyan

  • Apex 2.2.1- error in editing a report withIE 6: ORA-20001- Checksum error

    Hi all,
    I'am getting an Error when I try to edit a report with Internet Explorer 6: ORA-20001-...- Checksum error.
    With Firefox it works fine.
    Customer is using IE as standard browser and Firefox is not available here.
    Any Ideas?
    Kazim

    I had to apply Patch 4554072, provided with APEX.
    This patch is available in the directory patch\bug4554072.
    Kazim

  • Re: BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns

    Hello Everyone.
    I've run into something quite strange and am hoping you can help me.
    I am using Apex 4.0.1 and Oracle version 10.2.0.5. I've created a "classical" report in which the underlying SQL is a very simple:
    select * from pvtabThe Oracle table pvtab consists of 419 columns, all of which are varchar2(88) and number type. That's it.
    When I run the report, al of the columns show up as expected.
    However, when I go into the "Report Attributes" tab and click on one of the fields (any of them, it doesn't matter which one), I immediately get the following error:
    ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "598CAA7B68746A66F4B99E1512C36DED" application checksum = "0"If if replace the "*" with a few actual column names, then I am able to access any of these columns without problem.
    If I put back the "*", I then encounter this error again.
    I have never seen this error with other SQL SELECT statements in which I use the "*" qualifier to retrieve all columns from the table.
    And so, I am wondering if the error is caused because of the large number of columns (419) in my table.
    I've seen this same error mentioned in connection with forms but never with a report.
    So, is there some limit to the number of columns one can have in a "classic" or interactive report?
    Any idea why I would be getting this error?
    Here is the DDL for my table pvtab:
    CREATE TABLE  "PVTAB"
       (     "MICRO" VARCHAR2(4),
         "PRIM" VARCHAR2(4),
         "UNIT" NUMBER,
         "SEC_REF_1" NUMBER,
         "SECN_1" VARCHAR2(88),
         "SEC_REF_2" NUMBER,
         "SECN_2" VARCHAR2(88),
         "SEC_REF_3" NUMBER,
         "SECN_3" VARCHAR2(88),
         "SEC_REF_4" NUMBER,
         "SECN_4" VARCHAR2(88),
         "SEC_REF_5" NUMBER,
         "SECN_5" VARCHAR2(88),
         "SEC_REF_6" NUMBER,
         "SECN_6" VARCHAR2(88),
         "SEC_REF_7" NUMBER,
         "SECN_7" VARCHAR2(88),
         "SEC_REF_8" NUMBER,
         "SECN_8" VARCHAR2(88),
         "SEC_REF_9" NUMBER,
         "SECN_9" VARCHAR2(88),
         "SEC_REF_10" NUMBER,
         "SECN_10" VARCHAR2(88),
         "SEC_REF_11" NUMBER,
         "SECN_11" VARCHAR2(88),
         "SEC_REF_12" NUMBER,
         "SECN_12" VARCHAR2(88),
         "SEC_REF_13" NUMBER,
         "SECN_13" VARCHAR2(88),
         "SEC_REF_14" NUMBER,
         "SECN_14" VARCHAR2(88),
         "SEC_REF_15" NUMBER,
         "SECN_15" VARCHAR2(88),
         "SEC_REF_16" NUMBER,
         "SECN_16" VARCHAR2(88),
         "SEC_REF_17" NUMBER,
         "SECN_17" VARCHAR2(88),
         "SEC_REF_18" NUMBER,
         "SECN_18" VARCHAR2(88),
         "SEC_REF_19" NUMBER,
         "SECN_19" VARCHAR2(88),
         "SEC_REF_20" NUMBER,
         "SECN_20" VARCHAR2(88),
         "SEC_REF_21" NUMBER,
         "SECN_21" VARCHAR2(88),
         "SEC_REF_22" NUMBER,
         "SECN_22" VARCHAR2(88),
         "SEC_REF_23" NUMBER,
         "SECN_23" VARCHAR2(88),
         "SEC_REF_24" NUMBER,
         "SECN_24" VARCHAR2(88),
         "SEC_REF_25" NUMBER,
         "SECN_25" VARCHAR2(88),
         "SEC_REF_26" NUMBER,
         "SECN_26" VARCHAR2(88),
         "SEC_REF_27" NUMBER,
         "SECN_27" VARCHAR2(88),
         "SEC_REF_28" NUMBER,
         "SECN_28" VARCHAR2(88),
         "SEC_REF_29" NUMBER,
         "SECN_29" VARCHAR2(88),
         "SEC_REF_30" NUMBER,
         "SECN_30" VARCHAR2(88),
         "SEC_REF_31" NUMBER,
         "SECN_31" VARCHAR2(88),
         "SEC_REF_32" NUMBER,
         "SECN_32" VARCHAR2(88),
         "SEC_REF_33" NUMBER,
         "SECN_33" VARCHAR2(88),
         "SEC_REF_34" NUMBER,
         "SECN_34" VARCHAR2(88),
         "SEC_REF_35" NUMBER,
         "SECN_35" VARCHAR2(88),
         "SEC_REF_36" NUMBER,
         "SECN_36" VARCHAR2(88),
         "SEC_REF_37" NUMBER,
         "SECN_37" VARCHAR2(88),
         "SEC_REF_38" NUMBER,
         "SECN_38" VARCHAR2(88),
         "SEC_REF_39" NUMBER,
         "SECN_39" VARCHAR2(88),
         "SEC_REF_40" NUMBER,
         "SECN_40" VARCHAR2(88),
         "SEC_REF_41" NUMBER,
         "SECN_41" VARCHAR2(88),
         "SEC_REF_42" NUMBER,
         "SECN_42" VARCHAR2(88),
         "SEC_REF_43" NUMBER,
         "SECN_43" VARCHAR2(88),
         "SEC_REF_44" NUMBER,
         "SECN_44" VARCHAR2(88),
         "SEC_REF_45" NUMBER,
         "SECN_45" VARCHAR2(88),
         "SEC_REF_46" NUMBER,
         "SECN_46" VARCHAR2(88),
         "SEC_REF_47" NUMBER,
         "SECN_47" VARCHAR2(88),
         "SEC_REF_48" NUMBER,
         "SECN_48" VARCHAR2(88),
         "SEC_REF_49" NUMBER,
         "SECN_49" VARCHAR2(88),
         "SEC_REF_50" NUMBER,
         "SECN_50" VARCHAR2(88),
         "SEC_REF_51" NUMBER,
         "SECN_51" VARCHAR2(88),
         "SEC_REF_52" NUMBER,
         "SECN_52" VARCHAR2(88),
         "SEC_REF_53" NUMBER,
         "SECN_53" VARCHAR2(88),
         "SEC_REF_54" NUMBER,
         "SECN_54" VARCHAR2(88),
         "SEC_REF_55" NUMBER,
         "SECN_55" VARCHAR2(88),
         "SEC_REF_56" NUMBER,
         "SECN_56" VARCHAR2(88),
         "SEC_REF_57" NUMBER,
         "SECN_57" VARCHAR2(88),
         "SEC_REF_58" NUMBER,
         "SECN_58" VARCHAR2(88),
         "SEC_REF_59" NUMBER,
         "SECN_59" VARCHAR2(88),
         "SEC_REF_60" NUMBER,
         "SECN_60" VARCHAR2(88),
         "SEC_REF_61" NUMBER,
         "SECN_61" VARCHAR2(88),
         "SEC_REF_62" NUMBER,
         "SECN_62" VARCHAR2(88),
         "SEC_REF_63" NUMBER,
         "SECN_63" VARCHAR2(88),
         "SEC_REF_64" NUMBER,
         "SECN_64" VARCHAR2(88),
         "SEC_REF_65" NUMBER,
         "SECN_65" VARCHAR2(88),
         "SEC_REF_66" NUMBER,
         "SECN_66" VARCHAR2(88),
         "SEC_REF_67" NUMBER,
         "SECN_67" VARCHAR2(88),
         "SEC_REF_68" NUMBER,
         "SECN_68" VARCHAR2(88),
         "SEC_REF_69" NUMBER,
         "SECN_69" VARCHAR2(88),
         "SEC_REF_70" NUMBER,
         "SECN_70" VARCHAR2(88),
         "SEC_REF_71" NUMBER,
         "SECN_71" VARCHAR2(88),
         "SEC_REF_72" NUMBER,
         "SECN_72" VARCHAR2(88),
         "SEC_REF_73" NUMBER,
         "SECN_73" VARCHAR2(88),
         "SEC_REF_74" NUMBER,
         "SECN_74" VARCHAR2(88),
         "SEC_REF_75" NUMBER,
         "SECN_75" VARCHAR2(88),
         "SEC_REF_76" NUMBER,
         "SECN_76" VARCHAR2(88),
         "SEC_REF_77" NUMBER,
         "SECN_77" VARCHAR2(88),
         "SEC_REF_78" NUMBER,
         "SECN_78" VARCHAR2(88),
         "SEC_REF_79" NUMBER,
         "SECN_79" VARCHAR2(88),
         "SEC_REF_80" NUMBER,
         "SECN_80" VARCHAR2(88),
         "SEC_REF_81" NUMBER,
         "SECN_81" VARCHAR2(88),
         "SEC_REF_82" NUMBER,
         "SECN_82" VARCHAR2(88),
         "SEC_REF_83" NUMBER,
         "SECN_83" VARCHAR2(88),
         "SEC_REF_84" NUMBER,
         "SECN_84" VARCHAR2(88),
         "SEC_REF_85" NUMBER,
         "SECN_85" VARCHAR2(88),
         "SEC_REF_86" NUMBER,
         "SECN_86" VARCHAR2(88),
         "SEC_REF_87" NUMBER,
         "SECN_87" VARCHAR2(88),
         "SEC_REF_88" NUMBER,
         "SECN_88" VARCHAR2(88),
         "SEC_REF_89" NUMBER,
         "SECN_89" VARCHAR2(88),
         "SEC_REF_90" NUMBER,
         "SECN_90" VARCHAR2(88),
         "SEC_REF_91" NUMBER,
         "SECN_91" VARCHAR2(88),
         "SEC_REF_92" NUMBER,
         "SECN_92" VARCHAR2(88),
         "SEC_REF_93" NUMBER,
         "SECN_93" VARCHAR2(88),
         "SEC_REF_94" NUMBER,
         "SECN_94" VARCHAR2(88),
         "SEC_REF_95" NUMBER,
         "SECN_95" VARCHAR2(88),
         "SEC_REF_96" NUMBER,
         "SECN_96" VARCHAR2(88),
         "SEC_REF_97" NUMBER,
         "SECN_97" VARCHAR2(88),
         "SEC_REF_98" NUMBER,
         "SECN_98" VARCHAR2(88),
         "SEC_REF_99" NUMBER,
         "SECN_99" VARCHAR2(88),
         "SEC_REF_100" NUMBER,
         "SECN_100" VARCHAR2(88),
         "SEC_REF_101" NUMBER,
         "SECN_101" VARCHAR2(88),
         "SEC_REF_102" NUMBER,
         "SECN_102" VARCHAR2(88),
         "SEC_REF_103" NUMBER,
         "SECN_103" VARCHAR2(88),
         "SEC_REF_104" NUMBER,
         "SECN_104" VARCHAR2(88),
         "SEC_REF_105" NUMBER,
         "SECN_105" VARCHAR2(88),
         "SEC_REF_106" NUMBER,
         "SECN_106" VARCHAR2(88),
         "SEC_REF_107" NUMBER,
         "SECN_107" VARCHAR2(88),
         "SEC_REF_108" NUMBER,
         "SECN_108" VARCHAR2(88),
         "SEC_REF_109" NUMBER,
         "SECN_109" VARCHAR2(88),
         "SEC_REF_110" NUMBER,
         "SECN_110" VARCHAR2(88),
         "SEC_REF_111" NUMBER,
         "SECN_111" VARCHAR2(88),
         "SEC_REF_112" NUMBER,
         "SECN_112" VARCHAR2(88),
         "SEC_REF_113" NUMBER,
         "SECN_113" VARCHAR2(88),
         "SEC_REF_114" NUMBER,
         "SECN_114" VARCHAR2(88),
         "SEC_REF_115" NUMBER,
         "SECN_115" VARCHAR2(88),
         "SEC_REF_116" NUMBER,
         "SECN_116" VARCHAR2(88),
         "SEC_REF_117" NUMBER,
         "SECN_117" VARCHAR2(88),
         "SEC_REF_118" NUMBER,
         "SECN_118" VARCHAR2(88),
         "SEC_REF_119" NUMBER,
         "SECN_119" VARCHAR2(88),
         "SEC_REF_120" NUMBER,
         "SECN_120" VARCHAR2(88),
         "SEC_REF_121" NUMBER,
         "SECN_121" VARCHAR2(88),
         "SEC_REF_122" NUMBER,
         "SECN_122" VARCHAR2(88),
         "SEC_REF_123" NUMBER,
         "SECN_123" VARCHAR2(88),
         "SEC_REF_124" NUMBER,
         "SECN_124" VARCHAR2(88),
         "SEC_REF_125" NUMBER,
         "SECN_125" VARCHAR2(88),
         "SEC_REF_126" NUMBER,
         "SECN_126" VARCHAR2(88),
         "SEC_REF_127" NUMBER,
         "SECN_127" VARCHAR2(88),
         "SEC_REF_128" NUMBER,
         "SECN_128" VARCHAR2(88),
         "SEC_REF_129" NUMBER,
         "SECN_129" VARCHAR2(88),
         "SEC_REF_130" NUMBER,
         "SECN_130" VARCHAR2(88),
         "SEC_REF_131" NUMBER,
         "SECN_131" VARCHAR2(88),
         "SEC_REF_132" NUMBER,
         "SECN_132" VARCHAR2(88),
         "SEC_REF_133" NUMBER,
         "SECN_133" VARCHAR2(88),
         "SEC_REF_134" NUMBER,
         "SECN_134" VARCHAR2(88),
         "SEC_REF_135" NUMBER,
         "SECN_135" VARCHAR2(88),
         "SEC_REF_136" NUMBER,
         "SECN_136" VARCHAR2(88),
         "SEC_REF_137" NUMBER,
         "SECN_137" VARCHAR2(88),
         "SEC_REF_138" NUMBER,
         "SECN_138" VARCHAR2(88),
         "SEC_REF_139" NUMBER,
         "SECN_139" VARCHAR2(88),
         "SEC_REF_140" NUMBER,
         "SECN_140" VARCHAR2(88),
         "SEC_REF_141" NUMBER,
         "SECN_141" VARCHAR2(88),
         "SEC_REF_142" NUMBER,
         "SECN_142" VARCHAR2(88),
         "SEC_REF_143" NUMBER,
         "SECN_143" VARCHAR2(88),
         "SEC_REF_144" NUMBER,
         "SECN_144" VARCHAR2(88),
         "SEC_REF_145" NUMBER,
         "SECN_145" VARCHAR2(88),
         "SEC_REF_146" NUMBER,
         "SECN_146" VARCHAR2(88),
         "SEC_REF_147" NUMBER,
         "SECN_147" VARCHAR2(88),
         "SEC_REF_148" NUMBER,
         "SECN_148" VARCHAR2(88),
         "SEC_REF_149" NUMBER,
         "SECN_149" VARCHAR2(88),
         "SEC_REF_150" NUMBER,
         "SECN_150" VARCHAR2(88),
         "SEC_REF_151" NUMBER,
         "SECN_151" VARCHAR2(88),
         "SEC_REF_152" NUMBER,
         "SECN_152" VARCHAR2(88),
         "SEC_REF_153" NUMBER,
         "SECN_153" VARCHAR2(88),
         "SEC_REF_154" NUMBER,
         "SECN_154" VARCHAR2(88),
         "SEC_REF_155" NUMBER,
         "SECN_155" VARCHAR2(88),
         "SEC_REF_156" NUMBER,
         "SECN_156" VARCHAR2(88),
         "SEC_REF_157" NUMBER,
         "SECN_157" VARCHAR2(88),
         "SEC_REF_158" NUMBER,
         "SECN_158" VARCHAR2(88),
         "SEC_REF_159" NUMBER,
         "SECN_159" VARCHAR2(88),
         "SEC_REF_160" NUMBER,
         "SECN_160" VARCHAR2(88),
         "SEC_REF_161" NUMBER,
         "SECN_161" VARCHAR2(88),
         "SEC_REF_162" NUMBER,
         "SECN_162" VARCHAR2(88),
         "SEC_REF_163" NUMBER,
         "SECN_163" VARCHAR2(88),
         "SEC_REF_164" NUMBER,
         "SECN_164" VARCHAR2(88),
         "SEC_REF_165" NUMBER,
         "SECN_165" VARCHAR2(88),
         "SEC_REF_166" NUMBER,
         "SECN_166" VARCHAR2(88),
         "SEC_REF_167" NUMBER,
         "SECN_167" VARCHAR2(88),
         "SEC_REF_168" NUMBER,
         "SECN_168" VARCHAR2(88),
         "SEC_REF_169" NUMBER,
         "SECN_169" VARCHAR2(88),
         "SEC_REF_170" NUMBER,
         "SECN_170" VARCHAR2(88),
         "SEC_REF_171" NUMBER,
         "SECN_171" VARCHAR2(88),
         "SEC_REF_172" NUMBER,
         "SECN_172" VARCHAR2(88),
         "SEC_REF_173" NUMBER,
         "SECN_173" VARCHAR2(88),
         "SEC_REF_174" NUMBER,
         "SECN_174" VARCHAR2(88),
         "SEC_REF_175" NUMBER,
         "SECN_175" VARCHAR2(88),
         "SEC_REF_176" NUMBER,
         "SECN_176" VARCHAR2(88),
         "SEC_REF_177" NUMBER,
         "SECN_177" VARCHAR2(88),
         "SEC_REF_178" NUMBER,
         "SECN_178" VARCHAR2(88),
         "SEC_REF_179" NUMBER,
         "SECN_179" VARCHAR2(88),
         "SEC_REF_180" NUMBER,
         "SECN_180" VARCHAR2(88),
         "SEC_REF_181" NUMBER,
         "SECN_181" VARCHAR2(88),
         "SEC_REF_182" NUMBER,
         "SECN_182" VARCHAR2(88),
         "SEC_REF_183" NUMBER,
         "SECN_183" VARCHAR2(88),
         "SEC_REF_184" NUMBER,
         "SECN_184" VARCHAR2(88),
         "SEC_REF_185" NUMBER,
         "SECN_185" VARCHAR2(88),
         "SEC_REF_186" NUMBER,
         "SECN_186" VARCHAR2(88),
         "SEC_REF_187" NUMBER,
         "SECN_187" VARCHAR2(88),
         "SEC_REF_188" NUMBER,
         "SECN_188" VARCHAR2(88),
         "SEC_REF_189" NUMBER,
         "SECN_189" VARCHAR2(88),
         "SEC_REF_190" NUMBER,
         "SECN_190" VARCHAR2(88),
         "SEC_REF_191" NUMBER,
         "SECN_191" VARCHAR2(88),
         "SEC_REF_192" NUMBER,
         "SECN_192" VARCHAR2(88),
         "SEC_REF_193" NUMBER,
         "SECN_193" VARCHAR2(88),
         "SEC_REF_194" NUMBER,
         "SECN_194" VARCHAR2(88),
         "SEC_REF_195" NUMBER,
         "SECN_195" VARCHAR2(88),
         "SEC_REF_196" NUMBER,
         "SECN_196" VARCHAR2(88),
         "SEC_REF_197" NUMBER,
         "SECN_197" VARCHAR2(88),
         "SEC_REF_198" NUMBER,
         "SECN_198" VARCHAR2(88),
         "SEC_REF_199" NUMBER,
         "SECN_199" VARCHAR2(88),
         "SEC_REF_200" NUMBER,
         "SECN_200" VARCHAR2(88),
         "SEC_REF_201" NUMBER,
         "SECN_201" VARCHAR2(88),
         "SEC_REF_202" NUMBER,
         "SECN_202" VARCHAR2(88),
         "SEC_REF_203" NUMBER,
         "SECN_203" VARCHAR2(88),
         "SEC_REF_204" NUMBER,
         "SECN_204" VARCHAR2(88),
         "SEC_REF_205" NUMBER,
         "SECN_205" VARCHAR2(88),
         "SEC_REF_206" NUMBER,
         "SECN_206" VARCHAR2(88),
         "SEC_REF_207" NUMBER,
         "SECN_207" VARCHAR2(88),
         "SEC_REF_208" NUMBER,
         "SECN_208" VARCHAR2(88)
       );Thank you for any help/advice.
    Elie
    Edited by: EEG on Jun 12, 2011 2:09 PM

    So, is there some limit to the number of columns one can have in a "classic" or interactive report?Yes. See Oracle® Application Express Application Builder User's Guide Release 4.0, Appendix B: Oracle Application Express Limits.
    Any idea why I would be getting this error?No, but I've replicated it in APEX 4.0.2.00.07 on 11.2.0.1.0 EE using a table of 420 <tt>varchar2(88)</tt> columns:
    >
    ORA-20503: Current version of data in database has changed since user initiated update process. current checksum = "50C9BDC0AA1AEF0EB272E9158B2117B4" application checksum = "0"
    >
    Happens whether using <tt>select *</tt> or including all column names in the query. (I know you don't want to type all the column names, but I'd never use <tt>select *</tt> in a production application: always use a proper column list. You can get one without typing by drag-and-drop of a table in most IDEs, or a query from <tt>user_tab_columns</tt>.)
    I hit the problem at 274 columns. Such an arbitrary number leads me to think that the problem is not one of the number of columns per se, but is due to some other limit (possibly a 32K VARCHAR2/RAW buffer somewhere).
    Workaround:
    Updates to the report column attributes are actually being saved, and you can navigate them using the Page Definition tree view as described in Appendix B.
    Getting More Help:
    This is probably a bug. If you have a support agreement with Oracle raise an SR with Oracle Support.
    Also:
    <li>Search the forum using the "ORA-20503" code and other possible terms to see if there's anything relevant. I had a quick look but the only thread in this context recommended an upgrade on an Oracle 9 DB version that's not compatible with APEX 4.0.
    <li>To get the attention of the Oracle APEX team or anyone else who may know more about this problem than we do, edit your original post and change the Subject to be more specific about the actual nature of the problem: <em>BUG? APEX 4.0: ORA-20503 error editing report with 400+ columns</em>, and include your database version/edition and the definition of the <tt>PVTAB</tt> table.
    Finally:
    Somebody's bound to ask, so we might as well get started:
    <li>Why so many columns?
    <li>What requirement is this trying to fulfil?

Maybe you are looking for