Increasing the rowcount in ECM Planning table

Hi,
We are using ECM in our portal and we have a requirement to change the rowcount for the table in Planning iview.
Corresponding webdyno for java component is mss~ecm.
right now standard functionality in planning iview is showing 10 rows in the table and we want to change that rowcount.
when we tried ctrl+right click we were able to change but only for that user and only for that session.but we want to change that for all the users .
Please let me know what is the solution for changing the rowcount
points will be rewarded for sure
Thanks
Bala Duvvuri

Try the role-based (administrator) personalization. Log-in as admin into the Portal, open the "Content Admin Studio", navigate to the iView containing the Web Dynpro application and open the "preview". Then invoke the personalization UI via CTRL-Right-Click. You should now see the administration UI and be able to change all properties of the UI elements including the table's visible row count. These settings will be persisted and apply to the application automatically.
Armin

Similar Messages

How to increase the length of Hyperion Planning object_name

In order to store a long member alias in outline, i modified the definition of field OBJECT_NAME and OLD_NAME in table HSP_OBJECT, and field OBJECT_NAME in table HSP_UNIQUE_NAME as varchar2(240). The default definitions of the fields in Hyperion Planning database are all varchar2(80). Then edit the alias in Hyperion Planning. However, when refreshing the database, the member alias in Essbase is modified as NULL. it seems that the long alias doesn't work.
How can i fix this problem?

find the following restrictions from essbase admin guide:
Naming Restrictions for Dimensions, Members, and Aliases
1-When naming dimensions, members, and aliases in the database outline, follow these rules:
2-Use no more than 80 bytes when naming non-Unicode-mode dimensions, members, or
aliases.
3-Use no more than 80 characters when naming Unicode-mode dimensions, members, or
aliases.
4-Names are not case-sensitive unless case-sensitivity is enabled.
hope this may help you.

How to increase the max character for a table name..!!

Hi All,
The maximum characters that supports for the table Name is 30
How can I increase this so that I can have table names lengthier than 30
This is required as I was doing a conversion of the database from SQL server 2005 to Oracle 9i
Many thanks in advance...
Best Regards..,

So How can I make it possible..?!!If it not possible, you cannot make it possible.
If you can create a synonym on more than 30 char., you cannot use it on more than 30 char :
SQL> create synonym my_very_long_synonym_name_for_emp_table for emp;
Synonym created.
SQL> select count(*) from my_very_long_synonym_name_for_emp_table;
select count(*) from my_very_long_synonym_name_for_emp_table
ERROR at line 1:
ORA-00972: identifier is too long
SQL> select * from user_synonyms;
SYNONYM_NAME                   TABLE_OWNER                    TABLE_NAME
DB_LINK
/91b591a7_MY_VERY_LONG_SYNONYM SCOTT                          EMP
SQL> select count(*) from "/91b591a7_MY_VERY_LONG_SYNONYM";
COUNT(*)
        14Nicolas.

How to increase the length of a columnin existing publication item

We need to urgently increase the length of three columns in one of the tables that is sent offline as a publication item. I have searched everywhere to see if there is a procedure to see this. I only found process to add/drop columns but not modify to JUST increase the length.
Can we just alter the tables on the server and republish the application? Will that cause any data loss on the client end?
Any help is greatly appreciated.
Thanks
Sireesha

I totally forgot about this method. Metalink had it in the headlines today and remembered your question.
This should work for you.
Applies to:
Oracle Lite - Version: 10.2.0.1.0 to 10.2.0.2.0
Information in this document applies to any platform.
Goal
The Goal of this Document is to show the right steps when it is necessary to increase the Column Size for a table
which is used for the Synchronization with Oracle Lite 10GR2
BECAREFULL, it is not supported to change the Column Size or make any Schema Evolution on the Primary key
as The Synchronization Algorithm is based on Primary key
Solution
Create table test_sec (col1 number(10); varchar2(10));
alter table test_sec add primary key (col1));
Create Publication: PUB_TEST_SEC
Create Publication: PI_TEST_SEC: select COL1, COL2 from scott.TEST_SEC fast
Refresh, server wins, weight = 1 and add it to the Publicatio PUB_TEST_SEC
Synchronize this PUB_TEST_SEC
On the Server: increase the col2 WHICH IS NOT A PK, from 10 to 15
alter Table scott.TEST_SEC modify (col2 (varchar2(15));
To get the new Column Size on the olite DB, you need to alter the Publication item too using for example this code:
import java.sql.*;
import java.io.*;
import oracle.lite.sync.Consolidator;
import oracle.lite.sync.ConsolidatorManager;
import oracle.mobile.admin.*;
public class PublicationChange {
public static void main(String argv[]) throws Throwable
DriverManager.registerDriver ((Driver)Class.forName ("oracle.jdbc.driver.OracleDriver").newInstance());
ConsolidatorManager consolidatorManager = new ConsolidatorManager();
consolidatorManager.openConnection("mobileadmin","manager","JDBC:ORACLE:thin:@suppolite1.fr.oracle.com:1521:PROD");
System.out.println("Connected");
try
/*You need to put a Select Statment lightly different from the Publication item,
if you will use the same select statment, it won't take in Account
if you used: select * from owner.table to create the Publication Item
you need to use: select * from owner.table for the alterPublicationItem API
consolidatorManager.alterPublicationItem("PI_TEST_SEC","SELECT * FROM SCOTT.TEST_SEC");
System.out.println("Pub Item recreated");
catch (Throwable e) {
e.printStackTrace();
try
consolidatorManager.closeConnection();
System.out.println("The installation is done!");
} catch (Throwable e) {
Compile and run this java code.
Synchronize
Check your table Description on Oracle Lite Database to verify that this Schema Evolution has worked as expected.

Increase row height of a configurable table

Dear SCN members,
This is related to a configurable table realized using <chtmlb:configTable>. Please let me know about the following possibilities with this:
1. Is it possible to increase the row height of this table?
2. The content of a given cell is truncated with three dots and the complete content is visible on the tooltip if the context exceeds the column width. But is it possible to see the complete content of such cells on the table itself with some kind of wrapping rather than just on the tooltip?
Thanks!

It is not directly possible, however with iterator and use of text area, it is possible to display longer texts on a table.

MF50 : Planning table and planning time fence

HI,
I use the transaction MF50 as planning table ( in order to do my MPS planning), I use "set firming date" to fix a firming date.
Now, I want o know if it should possible to reveal a message when we create a planned order within the firming date??
Thanks for your answer.

Hi,
For clarity , I am describing below the functionlity of Set Firming date is explained as below:
By setting Manual Firming date , we extend the planning time fence.
If a planning time fence has been created for a material then the following applies:
If the manual firming date lies before the end of the planning time fence, the planning time fence is still valid.
If the manual firming date lies after the end of the planning time fence, the planning time fence is extended until this date.
All order proposals with availability dates that lie before the end of the planning time fence of the manually extended planning fence are firmed for the planning run, if the materials have an MRP type which contains firming type or firming type 1 or 2
The system does not automatically firm order proposals for materials that have an MRP type with firming type 3 or 4, even if their availability dates lie before the end of the planning time fence or manually extended planning time fence.
Please check if this helps you.
Regards
Datta

Significance or use of various planning tables

Hi All
Can anyone please explain the significance of various tables used in planning.
I have searched the whole of Oracle portal but i haven't found a documentation which explains the importance or significance of various tables of planning.
If possible please provide me the link of this documentation or kindly let me know the significance of various planning tables.
Thanks in advance
regards
krishnatilak

VK, locale controls what landing page the recipient would see if he clicked an Unsubscribe or Opt Out from List link. The landing page shows up in that language.
Character set governs the display of characters in the email such as text or double byte characters. It should be set to Unicode (UTF-8) unless there is a very specific reason not to.

To increase the XMLtype column data length

Hi ,
I have created a Table with an XMLtype column , when I am checking the data length it is showing only 2000.
How can I increase the length.
DBMS_METADATA.GET_DDL('TABLE','CC_EVENT_MESSAGES','UNS_STAGING_DEV5')
CREATE TABLE "UNS_STAGING_DEV5"."CC_EVENT_MESSAGES"
   (    "SRC_SYSTEM_CD" VARCHAR2(10) NOT NULL ENABLE,
        "SRC_SEQUENCE_NUM" NUMBER NOT NULL ENABLE,
        "SRC_EVENT_NAME" VARCHAR2(255) NOT NULL ENABLE,
        "SRC_EVENT_XSD_NAME" VARCHAR2(255) NOT NULL ENABLE,
        "SRC_EVENT_DATE" DATE NOT NULL ENABLE,
        "INSERT_TS" TIMESTAMP (6) NOT NULL ENABLE,
        "PROCESSED_TS" TIMESTAMP (6),
        "STAGING_NUM" NUMBER NOT NULL ENABLE,
        "MESSAGE_STATE" VARCHAR2(10) NOT NULL ENABLE,
        "MESSAGE_FRAME" "SYS"."XMLTYPE" NOT NULL ENABLE
   ) SEGMENT CREATION IMMEDIATE
PCTFREE 0 PCTUSED 0 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 1048576 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "UNS_STAGING_DEV5"
XMLTYPE COLUMN "MESSAGE_FRAME" STORE AS BASICFILE CLOB (
TABLESPACE "UNS_STAGING_DEV5" ENABLE STORAGE IN ROW CHUNK 8192 RETENTION
CACHE
STORAGE(INITIAL 65536 NEXT 65536 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT))
   CACHE
SQL> select OWNER,TABLE_NAME,column_name,data_type,data_length from dba_tab_columns where DATA_TYPE like '%XMLTYPE' and owner not in ('SYS','SYSTEM','XDB');
OWNER                TABLE_NAME           COLUMN_NAME     DATA_TYPE DATA_LENGTH
UNS_STAGING_DEV5     CC_EVENT_MESSAGES    MESSAGE_FRAME   XMLTYPE           2000

I have created a Table with an XMLtype column , when I am checking the data length it is showing only 2000.
Don't rely on this value, it's wrong.
XMLType datatype inherits the properties of its underlying LOB storage, in the present case CLOB, which can store TBs of data.

Customizing Graphical Planning Table Views

Where do I go to alter the look of the graphical planning tables that I find in transactions like CM21, 27, 31 and 32? There are no labels, everything is gray and difficult to read! Where can I go in and change the way these graphical planning tables look? Mainly the colors of the dispatched orders into the work centers (the single gray bars).

Dear,
Please refer this link,
[Lay-out Profile Set|New Lay-out Profile for CM25]
Regards,
R.Brahmankar

Increase the logoff time

Hi John,
i want to increase the logoff time for planning and workspace. Where shall i set the logoff time.And wat is the maximum limit for it

Hi,
Have a look at http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_hp_admin/ch13s15.html
and http://download.oracle.com/docs/cd/E10530_01/doc/epm.931/html_hs_admin/ch02s02s01.html
Ok?
Cheers
John
http://john-goodwin.blogspot.com/

How to increase the row height of the table in the smartform

Hi,
Can any one say,
How to increase the row height of the table in the smartform.
It is presently show the row width very small, i want to increase the row with of the table in the smartform.
Plase say how can we increase the row height in the smartform.

Hi Ravi,
In Smartforms , Select the Table and you can adjust the cell hieghts in OUTPUT OPTIONs TAB.
Reward points if that Helps.
Manish

Increasing the width of Pivot table Columns

Hi Gurus,
Small pivot table --> ( ie having less no of columns which generally can be seen in a single page without scrolling to the right)
If i have a small pivot table , then in the column properties through additional formatting options i can increase the width of an individual column.
However if the pivot table is Big,I am not able to increase the width of the individual column .
I tried setting width in the additional formatting options in the Content Properties( just above Rows and below Section there is a small grey box containing finger).
Now the Content Properties indeed increases the width of the column, but it also increase the width of the whole Pivot Table.
See...If i have a fixed number of columns in a PIVOT Table that do not change with prompt, then this solution work fine...
but the problem comes when the no of columns in pivot Table reduces based on the prompt selected.
In this case the less no of columns tries to occupy the whole width set in the content properties.
In short, with Content Properties the width of the PIVOT Table becomes fixed, irrespective of the no of columns coming.
Also after setting content properties, I am not able to print the report to PDF.
So the Question is... Can we increase the width of a Big Pivot Table whose no of columns keeps on changing based on the prompt....
Big pivot table -->
(ie table having no of columns which exceeds a single window frame and have to scroll to right to see the rest of the columns)
I hope i have not made things messy...
Thanks
Ashish

Ashish,
Yes, you can set a fixed size for these. I'm sure you are fixing these because of PDF issue which might be irregular in sizes. Just play arnd with Custom CSS options.

How to Increase the Length of Condition table in OV20

While creating a condition table in T.code OV20 if fields length is more that 50 bytes table is not getting generated.it gives error as Too Many Fields Selected(More than 50 Bytes).
Actually i need to create a tabel with Basic Material(WRKST) which has length of 48 bytes.
Is there a solution on how to increase the length so that error is avoided.
There is no such error occuring while crating condition table in V/03

Hi,
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Regards

How to increase the length of internal table dynamically

How to increase the length of internal table dynamically depending on the number of fields fetched into the internal table ?
The requirement code :
types: begin of t_data,
         form          like zscr_data_hdr-form,
         werks         like zscr_data_hdr-werks,
         matnr         like zscr_data_hdr-matnr,
         verid         like zscr_data_hdr-verid,
         lot           like zscr_data_hdr-lot,
         lot_qty       like zscr_data_hdr-lot_qty,
         udate         like zscr_data_hdr-udate,
         utime         like zscr_data_hdr-utime,
         zuser         like zscr_data_hdr-zuser,
         processed     like zscr_data_hdr-processed,
         defect        like zscr_defect_data-defect,
         vornr         like zscr_route_data-vornr,
         fld1          like zscr_defect_data-defect_val,
         fld2          like zscr_defect_data-defect_val,
         fld3          like zscr_defect_data-defect_val,
         fld4          like zscr_defect_data-defect_val,
         fld5          like zscr_defect_data-defect_val,
         fld6          like zscr_defect_data-defect_val,
         fld7          like zscr_defect_data-defect_val,
         fld8          like zscr_defect_data-defect_val,
         fld9          like zscr_defect_data-defect_val,
         fld10         like zscr_defect_data-defect_val,
         fld11         like zscr_defect_data-defect_val,
         fld12         like zscr_defect_data-defect_val,
         fld13         like zscr_defect_data-defect_val,
         fld14         like zscr_defect_data-defect_val,
         fld15         like zscr_defect_data-defect_val,
         fld16         like zscr_defect_data-defect_val,
         fld17         like zscr_defect_data-defect_val,
         fld18         like zscr_defect_data-defect_val,
         fld19         like zscr_defect_data-defect_val,
         fld20         like zscr_defect_data-defect_val,
         fld21         like zscr_defect_data-defect_val,
         fld22         like zscr_defect_data-defect_val,
         fld23         like zscr_defect_data-defect_val,
         fld24         like zscr_defect_data-defect_val,
         fld25         like zscr_defect_data-defect_val,
         fld26         like zscr_defect_data-defect_val,
         fld27         like zscr_defect_data-defect_val,
         fld28         like zscr_defect_data-defect_val,
         fld29         like zscr_defect_data-defect_val,
         fld30         like zscr_defect_data-defect_val,
         fld31         like zscr_defect_data-defect_val,
         fld32         like zscr_defect_data-defect_val,
         fld33         like zscr_defect_data-defect_val,
         fld34         like zscr_defect_data-defect_val,
         fld35         like zscr_defect_data-defect_val,
         fld36         like zscr_defect_data-defect_val,
         fld37         like zscr_defect_data-defect_val,
         fld38         like zscr_defect_data-defect_val,
         fld39         like zscr_defect_data-defect_val,
         fld40         like zscr_defect_data-defect_val,
         fld41         like zscr_defect_data-defect_val,
         fld42         like zscr_defect_data-defect_val,
         fld43         like zscr_defect_data-defect_val,
         fld44         like zscr_defect_data-defect_val,
         fld45         like zscr_defect_data-defect_val,
         fld46         like zscr_defect_data-defect_val,
         fld47         like zscr_defect_data-defect_val,
         fld48         like zscr_defect_data-defect_val,
         fld49         like zscr_defect_data-defect_val,
         fld50         like zscr_defect_data-defect_val,
         fld51         like zscr_defect_data-defect_val,
         fld52         like zscr_defect_data-defect_val,
         fld53         like zscr_defect_data-defect_val,
         fld54         like zscr_defect_data-defect_val,
         fld55         like zscr_defect_data-defect_val,
         fld56         like zscr_defect_data-defect_val,
         fld57         like zscr_defect_data-defect_val,
         fld58         like zscr_defect_data-defect_val,
         fld59         like zscr_defect_data-defect_val,
         fld60         like zscr_defect_data-defect_val,
         fld61         like zscr_defect_data-defect_val,
         fld62         like zscr_defect_data-defect_val,
         fld63         like zscr_defect_data-defect_val,
         fld64         like zscr_defect_data-defect_val,
         fld65         like zscr_defect_data-defect_val,
         fld66         like zscr_defect_data-defect_val,
         fld67         like zscr_defect_data-defect_val,
         fld68         like zscr_defect_data-defect_val,
         fld69         like zscr_defect_data-defect_val,
         fld70         like zscr_defect_data-defect_val,
         fld71         like zscr_defect_data-defect_val,
         fld72         like zscr_defect_data-defect_val,
         fld73         like zscr_defect_data-defect_val,
         fld74         like zscr_defect_data-defect_val,
         fld75         like zscr_defect_data-defect_val,
         fld76         like zscr_defect_data-defect_val,
         fld77         like zscr_defect_data-defect_val,
         fld78         like zscr_defect_data-defect_val,
         fld79         like zscr_defect_data-defect_val,
         fld80         like zscr_defect_data-defect_val,
         fld81         like zscr_defect_data-defect_val,
         fld82         like zscr_defect_data-defect_val,
         fld83         like zscr_defect_data-defect_val,
         fld84         like zscr_defect_data-defect_val,
         fld85         like zscr_defect_data-defect_val,
         fld86         like zscr_defect_data-defect_val,
         fld87         like zscr_defect_data-defect_val,
         fld88         like zscr_defect_data-defect_val,
         fld89         like zscr_defect_data-defect_val,
         fld90         like zscr_defect_data-defect_val,
         fld91         like zscr_defect_data-defect_val,
         fld92         like zscr_defect_data-defect_val,
         fld93         like zscr_defect_data-defect_val,
         fld94         like zscr_defect_data-defect_val,
         fld95         like zscr_defect_data-defect_val,
         fld96         like zscr_defect_data-defect_val,
         fld97         like zscr_defect_data-defect_val,
         fld98         like zscr_defect_data-defect_val,
         fld99         like zscr_defect_data-defect_val,
         fld100         like zscr_defect_data-defect_val,
         fld101         like zscr_defect_data-defect_val,
         fld102         like zscr_defect_data-defect_val,
         fld103         like zscr_defect_data-defect_val,
         fld104         like zscr_defect_data-defect_val,
         fld105         like zscr_defect_data-defect_val,
         fld106         like zscr_defect_data-defect_val,
         fld107         like zscr_defect_data-defect_val,
         fld108         like zscr_defect_data-defect_val,
         fld109         like zscr_defect_data-defect_val,
         fld110         like zscr_defect_data-defect_val,
         fld111         like zscr_defect_data-defect_val,
         fld112         like zscr_defect_data-defect_val,
         fld113         like zscr_defect_data-defect_val,
         fld114         like zscr_defect_data-defect_val,
         fld115         like zscr_defect_data-defect_val,
         fld116         like zscr_defect_data-defect_val,
         fld117         like zscr_defect_data-defect_val,
         fld118         like zscr_defect_data-defect_val,
         fld119         like zscr_defect_data-defect_val,
         fld120         like zscr_defect_data-defect_val,
         fld121         like zscr_defect_data-defect_val,
         fld122         like zscr_defect_data-defect_val,
         fld123         like zscr_defect_data-defect_val,
         fld124         like zscr_defect_data-defect_val,
         fld125         like zscr_defect_data-defect_val,
         fld126         like zscr_defect_data-defect_val,
         fld127         like zscr_defect_data-defect_val,
         fld128         like zscr_defect_data-defect_val,
         fld129         like zscr_defect_data-defect_val,
         fld130         like zscr_defect_data-defect_val,
         fld131         like zscr_defect_data-defect_val,
         fld132         like zscr_defect_data-defect_val,
         fld133         like zscr_defect_data-defect_val,
         fld134         like zscr_defect_data-defect_val,
         fld135         like zscr_defect_data-defect_val,
         dayst         like zscr_data_hdr-dayst,
       end of t_data.
In this fld1 to fld135 are defined in internal table.
But if the number of fields are more than 135 then the program is going to short dump.
Some times fld1 to fid170 or more fields will be there in my internal table.
Please suggest me how to make my requirement dynamic and display this data fetched into this internal table onto a .XLS file in the presentation server ?

Hi
You can try to use the type string:
form like zscr_data_hdr-form,
werks like zscr_data_hdr-werks,
matnr like zscr_data_hdr-matnr,
verid like zscr_data_hdr-verid,
lot like zscr_data_hdr-lot,
lot_qty like zscr_data_hdr-lot_qty,
udate like zscr_data_hdr-udate,
utime like zscr_data_hdr-utime,
zuser like zscr_data_hdr-zuser,
processed like zscr_data_hdr-processed,
defect like zscr_defect_data-defect,
vornr like zscr_route_data-vornr,
fieldxx type string,
dayst like zscr_data_hdr-dayst,
end of t_data.
So you can save you informations of every fld<n> concatenating their values into fieldxx.
Max

How to increase the rows of a Table control on ITS

Hi,
I'm trying to increase the number of rows to 20 on ITS but it always shows 2 rows per navigation. Although in the backend module pool there are 8 rows and the GV_SOS_LIST_CONTROL-LINES contains the total no of rows of the internal table. yet there are always 2 rows getting printed. This screen is in different function group and being called from some other function group i.e BBP_SC_UI_ITS. Are there any parameters that we have missed out to pass from BBP_SC_UI_ITS to our function group. Reply needed urgently!!!!!!!!!!!

Hi,
i tried increasing the rows on the browser by hard coding the counter and then the rows do increase but the records that are shown are still 2 per navigation. i doubt if it is a screen size constraint. the transaction in which i'm trying all this is bbpsc01.

Increasing the rowcount in ECM Planning table

Similar Messages

Maybe you are looking for