Presentation Hierarchy with Attribute Column

HI,
We have a requirement to show Presentation Hierarchy(Report column 1) with Attribute (report column 2) column from the same Presentation table. In general this is not feasible just wanted to know if that the case. and do we have a wayaround for the same

Hello Gurus, Please let me know if you have any ideas

Similar Messages

Problem with the presentation hierarchy 0YEA_QUA_MON_DAY

Hi,
Kindly anybody help me to sort out this problem:
I have selected 0YEA_QUA_MON_DAY hierarchy on 0calday.In the query I have included 0calday as free characterstic.In quey execution , first of all it displaying few rows. If I drill down to 0calday level,it does not display any rows. Here the message is ,after drilldown to 0calday level:
The presentation hierarchy 0YEA_QUA_MON_DAY acts as a dynamic filter
Diagnosis
You have activated presentation hierarchy on characteristic Calendar day. This hierarchy has the attribute that the suppression of 'non assigned' nodes is switched on ( RSH1 -> Hierarchy attributes).
System response
All data records whose characteristic value Calendar day are arranged in hierarchy are filtered automatically.
This filter is not always displayed.
Notification Number BRAIN 133
With rgds,
Anil Kumar Sharma .P

Did any one have a solution for this?
I also have thesame issue.

Use presentation hierarchy column in table prompt section

Hi,
I right click on presentation hierarchy column -> Move -> To prompts.
Column filter appears in table prompts section but there is only one value to select in a dropdown - top levelparent of hierarchy.
Is there any way to make all hierarchy levels be displayed in prompt?
Regards,
mudi

Take 2 column first column as parent and second column as Child

ADF BC : "Attributes selected in query with no column type found! ..."

hi
Using JDeveloper 10.1.3.3.0, I have this "Selected in Query" attribute, "Never" updatable, in my Entity Object.
The Entity Object is based on the SCOTT.EMP table and the attribute, called "BonusInfo", is defined using the expression " '[bonus info ' || (SAL * 2) || ']' ".
see http://verveja.footsteps.be/~verveja/files/oracle/NoColumnTypeFoundApp-v0.01.zip
While creating this Entity Object, I got a "Business Components" dialog that says:
"Column type is not specified for this attribute. Specifying column-type and precision results in better query performance at runtime. Do you wish to set column type to VARCHAR2(255)?"
I clicked "Yes".
I also created two View Objects based on this Entity Object.
In the "Create View Object" wizard "Step 4 of 7: Attribute Settings" I got a "Business Components" diaglog that says:
"Attributes selected in query with no column type found! Specifying column-type and precision results in better query performance at runtime. Do you wish to set default column type for these attributes?"
I clicked "Yes".
Testing the query in "Step 5 of 7: SQL Statement" showed "Query is valid.".
question:
Why do I keep getting the message ...
"Attributes selected in query with no column type found! Specifying column-type and precision results in better query performance at runtime. Do you wish to set default column type for these attributes?"
... in the View Object Editor if I click on different attributes?
(I don't get such a message the first time I click on an attribute after opening the View Object Editor, but after that it keeps popping up each time I click on a different attribute, no matter what I answer "Yes", "No" or "Cancel".)
many thanks
Jan Vervecken

Jan,
BC needs the column type and precision so that we can allocate the correct JDBC buffer size; otherwise we would just allocate 2k per string.
Blaise

Attributes selected in query with no column type found! (solved)

Dear JHeadstart Team,
In the view object Editor I have two entity based attributes attrib1 and attrib2
both with type Number. Both have aliases with type number(9,0)
If attrib1 is null I want to have the value of attrib2.
In the expression box I put: nvl(attrib1,attrib2)
When I press the ok button I get the next error message.
"Attributes selected in query with no column type found!
Specifying column-type and precision results in better query performance at runtime.
Do you wish to set default column type for these attributes? "
When I say ok I get the next message:
"An error occurred. Unable to apply all the wizard changes.
Column type cannot be changed for Entity based attribute.
Exception: oracle.jbo.dt.objects.JboExeption."
The details button serves no extra information.
Since both the attributes have the same type I thought the nvl commando should work.
But what does the "no column type found" sentence mean?
regards,
Marcel.
Message was edited by:
user571204

Thanks Jan,
You've put me on the right track.
I found out that this is only possible in the entity object class.
So I have to check my limited java skills.

Bex Hierarchy showing just the key with Attributes ????

Hierarchy showing just the key with Attributes ???? I want the Text without attribute!
I had created a Hierarchy manually on 0companycode characteristic, but I have some problems.
1 u2013 Itu2019s showing just the KEY (On query Design is marked to show the text , and Iu2019m on the proper language).
2 u2013 On the last lever that is the company code, is showing the key with all attributes like this.
-> CONTRY_BR
-> KW11 Contry Canada Chart of account 0001 Currency 01
I want just the Text without the attributes.
Regards
Edited by: Marcus Coufal on Mar 4, 2011 1:53 PM

On the caracteristic -> attribute put 0 on "Order For"

Issue with Presentation Hierarchy in obiee 11g

Hi Guru's
I am using a presentation hierarchy in obiee 11 g, but it is behaving weirdly when expanding the hierarchy
for example i have a hierarchy for languages when i expand one country in the hierarchy all the countries which has similar childs are getting expanded
for Example Parent A B C D
under A i have 1, 2,3,4, under B i have 5,6,7,8 under C i have 9, 10 ,11, 12 under D i have 1, 13, 14, 15
so when i expand A in answers D is also getting expanded as i have 1 as common value in both the parents.
can some please help me how to fix this, as the user does not like this expansion
Thanks in advance,

That is strange... I downloaded the files from the left hand side of this page:
[Sample Application site|http://www.oracle.com/technetwork/middleware/bi-foundation/obiee-samples-167534.html]
... the title states quiite clearly that the Sample Application (Build 825) applies to OBIEE release 11g.
Best regards
Juan Algaba Colera

Tricky Situation with Disco columns!!

The problem is something like this..
I have a discoverer crosstab worksheet with a column axis called "Expenditure Category" which lists the expenditures (data point) against a list of employees (row axis). The expenditure categories that are present in the databse are, say, "ABC","DEF","XYZ".
Only ABC and DEF are the ones that need to be displayed under expenditure categories because their costs are in currency (INR). The costs for the expenditure type XYZ are in terms of HOURS and it needs to be displayed as a separate column (some calculation) alongside the employee names.
As of now, if i filter out the rows with expenditure category as "XYZ".. all those rows are lost and I cannot create any sort of calculation on them. On the other hand, if i include all those rows, then I get a column called "XYZ" under expenditure categories heading which I dont want.
Any suggestions ?

So are you saying that you want the XYZ to be an attribute of the Employee (thus in the left side drill) and not a fact (thus not in a cell) ?? And so it does not vary based on the cross-tab column, like the cost data does??
If so, then you want to create a folder that joins the Employee to the hours info calculation (choice of a folder based on database view, SQL folder, complex folder). Then you can use this Employee+Hours folder as your base instead of the standard Employees, and join that to the costs info and do your crosstab as you were.

11g presentation hierarchy - limit of levels?

Do you know of a limit on presentation hierarchy levels that can be displayed in OBIEE 11g analytics?
I faced an drill issue in my project and was able to reproduced it with OBIEE Samples Virtual Box image.
In particular case it's not possible to browse lower levels of hierarchy: [https://picasaweb.google.com/mudlaff.piotr/February132012]

Ok, that's too bad. No way to format individual items, we're talking about thousands of accounts in an account hierarchy. I'll put in an enhancement request for this feature. I guess one related question, is there any way in answers to add a column that returns what level of a hierarchy the given row is at? If I could do that, then I could format the measures conditionally based on that column?
Thanks,
Scott

Presentation Hierarchy Grand Total Values

Hi,
We have the following scenario,
Hierarchy Product A is created for Dimension Product A
Hierarchy Product B is created for Dimention Product B
Fact Product Measures is joined to Store Dimension , Dimension Product A, Dimention Product B and Fiscal Calendar
Dimension Product A contains subset of Products that are existing at Fact
Dimention Product B contains subset of Products that are existing at Fact
and some products can exists both at Dimension Product A and Dimension Product B
The issue we are facing is, when ever report is created using One of the Product Hierarchy and Fact. Product Sales (default aggregation is sum),
the grand total level is showing sum of all Product Sales. It is not limiting to Products that are in Product Hierarchy selected in the report.
But the sub levels are limiting based on selected Product Hierarchy which is causing not matching the roll up amount to grand total.
Is it possible to limit the grand total level value of Presentation Hierarchy based on selected Product Hierarchy.
Does anyone face similar issue.
Thanks in Advance

is your summary and detail reports hitting different facts, like summary hitting aggregate and detail report hitting it's corresponding detail level fact..?
if then,
From Front-end:
Fix the filter values in detail report that are passing from master report then try delete each columns then check the grand total. If you found your values is matching by deleting particular column then you need to investigate what is the issue around with that dimension table..
From Database side:
1. check first aggregate table has proper aggregate data of it's detail..
2. Take the detail report obiee generated query and try to comment each dimension table and it's corresponding joins to the facts, (before, this delete all the dimensional columns and other measures from select statement and put only that measure where you are getting wrong value, so that you need not to comment all the select and group by columns which saves your time.. ). Need to check by commenting each dimensional wid and it's table from clause, if you found that values is matching then there is some problem with wid columns data population in your ETL.
Is that BI-Apps project?
btw, whtz ur name?

Hierarchy with Intervals and Temporal Join

Hi,
I am loading a hierarchy structure (Time dependant and with Temporal Join and Intervals)
in the flat file structure for hier loading we have leaf to and leaf from fields which means Page of the hierarchy to and page of the hierarchy from.
can anyone let me know what is the use of these fields, and the values we have to pass for these fields with an example.
i haven't come across Hier loading with intervals and termporal join.
can anyone please help me in this?
Regards,
p423168.

Hi,
BI Process (Loading Hierarchies from Flat file to BI)
Go to RSA1
Create info object for customer as zcust_b5 and activate
Create info object as zcust_b5 and activate it
Select the info object and double click on it
Select the hierarchies tab and select the option with hierarchies
And select Hierarchies not time dependent
Click external characteristics in hierarchies
Select your Infoobjects in the list and pass it and activate it
After activating the objects we will see tables of hierarchies at maintain Hierarchies
Create an application component
Create the transfer rules for the info object and activate (for hierarchies, texts, attributes)
This screen will show the communication structure.
After creating the data source at info source level the field attributes are shown in above
Create an excel sheet with required values and save it in CSV file.
Uploading the Hierarchy Data into BW
a) Create Info Package for Hierarchy Upload. Select the Hierarchy to be uploaded
and also the Full Update button as we are uploading the entire Hierarchy.
b) There are three update methods for uploading the hierarchy.
Full Update: For Uploading the entire hierarchy structure
Insert Sub tree: For appending the hierarchy with new nodes.
Update Sub tree: For modifying the nodes of the hierarchy.
Create info package and schedule the data loads
Select the Hierarchy and name it before scheduling
Schedule and Start the data loads
After creating the info package of the info object the above screen shows the initial hierarchy maintenance
Hierarchy is done successfully by extracting data from flat file.
time dependent :
a) For making the hierarchy time dependent select the u2018Time-Dependent Hierarchy structureu2019 radio button and activate the info object ZSREP
b) In the transfer structure there will be 2 more additional fields date from and date to for the time dependent nodes.
c) Consider that Sales Representative u2018SREP2u2019 was in England up to 31/12/1995 and moved to USA
d) Flat file structure for the above hierarchy is shown below . It contains two extra columns Date-to and Date-from.
e) In the info-package Update tab , select Fixed Time interval radio button and give start date as 01/01/1000 and End date as 31/12/9999 so that all nodes are uploaded.
f) Upload the hierarchy data from flat-file to BW.
g) Display the loaded hierarchy.
Regards
Sudheer
Edited by: SUDHEER on Dec 30, 2008 12:52 PM

ALV Report Output Print issue with more Columns

Hi Experts ,
I'm facing an issue while printing an ALV report which has around 22 columns .If i reduce the column display in the code . I'm able to print but not with 22 columns.. I have used Line-size = 1023 and line-count = 60 , but still the problem persists .
I also searched in SDN with similar issue but managed to get only the above solution which is not working .
Any other ways of doing it , kindly suggest .
Many Thanks,
Kumaran

175 characters is the maximum number of characters that can be generated in a line of a spool (next characters are stored on the next line of the spool). When the spool is printed, these line feeds are respected.
What is possible (I don't know) is that ALV chooses its own format type instead of the format type you have chosen when you run your program in background. To check that, just look at spool attributes (SP01).

HOW TO CREATE A TABLE WITH 800 COLUMNS?

I have to create a table with 800 columns.I know the create statement to create a table but it will take more time.
So tell me the other method.

If you really think that you have to store 800 values for a given entity, it would be a wise idea if you store you information in columnar fashion. Make a main table and a attribute table, keep the primary identifier in the main table and store other attributes in the attribute table where you can keep the primary key of the first table as foreign key (not necessary) to maintain the relationship.
eg.
emp_id
emp_name
dob
city
state
country
pincode
1
Mr X
01/01/1990
ABC
ZXC
MMM
12345
Can be stored as
Main Table
emp_id
emp_name
1
Mr X
Attribute Table
attr_id
emp_id
attr_nam
attr_value
1
1
dob
01/01/1990
2
1
city
ABC
3
1
state
ZXC
4
1
country
MMM
5
1
pincode
12345
Creating table with large number of columns is bad design as suggested by other Gurus.
Thanks

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?

Convert a table with one column to panelList with outputText

Hi,
I have a table with one column, I would like to change it to use panelList to present it instead. What will be the syntax for panelList?
<af:table value="#{bindings.ItasUiRuleParamsVO2.collectionModel}"
var="row"
rows="#{bindings.ItasUiRuleParamsVO2.rangeSize}"
emptyText="#{bindings.ItasUiRuleParamsVO2.viewable ? 'No data to display.' : 'Access Denied.'}"
fetchSize="#{bindings.ItasUiRuleParamsVO2.rangeSize}"
rowBandingInterval="0"
selectedRowKeys="#{bindings.ItasUiRuleParamsVO2.collectionModel.selectedRow}"
selectionListener="#{bindings.ItasUiRuleParamsVO2.collectionModel.makeCurrent}"
rowSelection="single" id="t2"
partialTriggers="::t1">
<af:column sortProperty="RuleName" sortable="true"
headerText="#{bindings.ItasUiRuleParamsVO2.hints.RuleName.label}"
id="c11">
<af:outputText value="#{row.RuleName}"
id="ot11"/>
</af:column>
</af:table>
I tried this:
<af:panelList id="pl1">
<af:forEach items="#{bindings.ItasUiRuleParamsVO2.collectionModel}">
<af:outputText value="#{item.RuleName}" id="ot14"/>
</af:forEach>
</af:panelList>
but the error say:
javax.servlet.jsp.JspException: "items" must point to a List or array
at org.apache.myfaces.trinidadinternal.taglib.ForEachTag.doStartTag(ForEachTag.java:136)
Any ideas?
Thanks
-Mina

<af:forEach items="#{bindings.ItasUiRuleParamsVO2.collectionModel}" var="row">
<af:outputText value="#{row.RuleName}" />
</af:forEach>
and make sure the table binding is still in place in your pagedef (or binding tab)

Presentation Hierarchy with Attribute Column

Similar Messages

Maybe you are looking for