"Simple" table design?

I have a very simple table design I need to set up, yet every setting I've tried is vexing me.
Table requirements:
1. Header with bold white text and black fill
2. Alternating rows, every 2, after header of a different fill color
3. All table text, excluding header, of a specific style
4. Row strokes to be after every 2nd row, to separate the different fill colors
I set up the following:
A table style with the alternating 2 row fill colors, and row strokes as: Every other row, first 1 row weight 2 pt white, next 1 row weight 0 pt, white, SKIP FIRST 1 ROWS
A paragraph style for the table text to set the font attributes
This setup gives me exactly what I need, except it puts a black row stroke after my first row after the header. I just want the first row stroke to be after the 2nd row (or 3rd row, if you count the header). But it's like it keeps including the header.
ALSO:
I would like to be able to set the header, row heights, left indent, etc., for my tables, but there is nowhere to do that in the table style. Very frustrating, because you can do it manually in the toolbar or menu bars (table options that are not available in the style), and then it overrides your styles.
I have a feeling this may be based on not understanding how table style, paragraph style, cell style and character styles, along with their "based on" settings coincide, but there are far too many combinations of those for me to grasp at this time.
Thanks for any help.
Mike

Figured it out, but I'd still like to know how to adjust ROW HEIGHT and COLUMN WIDTH in my table styles. It appears that if you highlight a row or table, and then change those settings in the upper toolbar, that it does not affect the style. But that's an arduous manual way to have to do it. I would think these settings could be automated somehow. Thanks.

Similar Messages

Table design help

I have simple table design issue which I would appreciate some feedback on. Lets say I have two tables to start: users and addresses. Both tables have their primary keys of userid and addressid. Assume no two users can share an addresss.
Is it better to have the userid in the address table, so as to associate the addresses to users OR is it better to have a third table only for associating userid's and addressid's? The latter requires an extra table but appeals to me more because the address table remains purely addresses... seems more appropriate for some reason, but I could be wrong.
Thanks

Frank Kulash wrote:
Hi,
When deciding which is the best option, weigh the costs and benefits of each option. What are the advantages and disadvantages of each?
The two-table model is certainly simpler. Joins will be more efficient, and slighltly less storage will be required.
What is the advantage of the three-table model? Why does it appeal to you? In the imaginary world where no two users can share an address, it makes sense to think of resident as an attribute of address. Each address can be related to (at most) one user, just like each address can be related to (at most) one postal code.
But, as others have said, that is an imaginary world. Even if you're designing an application where you know there is some kind of business rule that prevents two users from being at the same address, can you be sure that business rule won't change next month?
So I see the relevant costs ot the two-table design as: (the probablility of proving inadequate in the future) * (cost of re-writing all the queires based on the two-table design)
I see the costs of the three-table design as: extra time needed to write and execute joins + marginal costs of an additional table.
In practice, few applications really treat address as an entity. It's more common for address to be considered an attribute of the person, or, if a person can have multiple addresses, to have a separate table that links each address to a single person, with no attempt to minimize duplicates.You make two key points here that I'd like to highlight, just for re-emphasis to the OP.
The first is that business rules can change. When analyzing data relationships, one should always ask if the relationship definition is immutable or simply a reflection of the current business rule. For instance, gender is considered to be immutable. If gender is a property of the entity being tracked, you can pretty much figure that there will never be but two possible values, and only one value current at any given time. But if the business rule says an entity can only have one address ... that rule is definitely subject to change. So the design should be such as to already allow for a different rule. I spent 21 years at an auto manufacturing plant. When the plant was first built, the business rule was there would only be one line of vehicles, and only one shift a day. The IT people tried to build systems to allow more flexibility, but the business side said NO. They paid for that for the next 20 years. In the case of the OP's example, it is most definetly possible for a person (or business) to have more than one address, and it is just as possible for more than one person (or business) to share a single address. The system should be designed for that regardless of the business rule.
The other big point is that data designers need to pay close attention to what constitutes an "entity" vs. an "attribute". Making that distinction is key to getting a good 3NF design.

SIMPLE Database Design Problem !

Mapping is a big problem for many complex applications.
So what happens if we put all the tables into one table called ENTITY?
I have more than 300 attributeTypes.And there will be lots of null values in the records of that single table as every entityType uses the same table.
Other than wasting space if I put a clustered index on my entityType coloumn in that table.What kind of performance penalties to I get?
Definition of the table
ENTITY
EntityID > uniqueidentifier
EntityType > Tells the entityTypeName
Name >
LastName >
CompanyName > 300 attributeTypes
OppurtunityPeriod >
PS:There is also another table called RELATION that points the relations between entities.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
check the coloumn with WHERE _entityType='PERSON'
as there is is clustered index on entityType...there
is NO performance decrease.
there is also a clustered index on RELATION table on
relationType
when we say WHERE _entityType ='PERSON' or
WHERE relationType='CONTACTMECHANISM'.
it scans the clustered index first.it acts like a
table as it is physically ordered.I was thinking in terms of using several conditions in the same select, such as
WHERE _entityType ='PERSON'
AND LastName LIKE 'A%' In your case you have to use at least two indices, and since your clustered index comes first ...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Have you ever thought of using constraints in your
modell? How would you realize those?
...in fact we did.We have arranged the generic object
model in an object database.The knowledge information
is held in the object database.So your relational database is used only as a "simple" storage, everything has go through your object database.
But the data schema is held in the RDBMS with code
generation that creates a schema to hold data.If you think that this approach makes sense, why not.
But in able to have a efficent mapping and a good
performance we have thought about building only one
table.The problem is we know we are losing some space
but the thing is harddisk is much cheaper than RAM
and CPU.So our trade off concerated on the storage
cost.But I still wonder if there is a point that I
have missed in terms performance?Just test your approach by using sufficiently data - only you know how many records you have to store in your modell.
PS: it is not wise effective using generic object
models also in object databases as CPU cost is a lot
when u are holding the data.I don't know if I'd have taken your approach - using two database systems to hold data and business logic.
PS2: RDBMS is a value based system where object
databases are identity based.we are trying to be in
the gray area of both worlds.Like I wrote: if your approach works and scales to the required size, why not? I would assume that you did a load test with your approach.
What I would question though is that your discussing a "SIMPLE Database Design" problem. I don't see anything simple in your approach when it comes to implementation.
C.

Advise on Table design

Dear all,
I have a pool of data which are based organized has CATEGORY and SUB-CATEGORY. When I am configuring the database I should be able to define all categories at once, then being able to define which one is the Parent category of the others.
For exemple if I have a set of Dishes for a restaurant, then I can classify those dishes in different menu category which are then the Parents category for dishes.
Please note that a SUB-CATEGORY can have other sub categories attached.
To have a better idea of what I am trying to do is similar things when you create folders and sub folders on a file system. From the configuration side of the database I should be able to define my category and subcategories and then organize them by a link
ID or other stuff, in the same way I will organize folder.
What will be the best Database table design for that scenario ?
I am not a DBA, but have some basis so try to speak the same language as me :-)
Thanks for help
regards

I think you have it with your design. There are a few ways to represent a hierarchy in SQL, and having two tables like this:
CategoryID    CategoryName
ParentCategoryID
1001
Dishes          NULL
1002          Desserts
1001
1003          Icecream
1002
SubCategoryID    SubCategoryName
CategoryID
10001
Vanilla
1003
10002
Strawberry
1003
10003                   Butterscotch             1003
Make sense ONLY if you can guarantee a two level hierarchy (or a fixed number of levels, where you might have yet another table SubSubCategory). Having a fixed number of levels can make processing a ton easier because your queries can be written in
a straightforward manner because the levels of nodes in the tree remain the same.
Your requirements here:
"CATEGORY can have other sub categories attached."
Leads to the more flexible solution like you have set up:
CategoryID    CategoryName
ParentCategoryID
1001
Dishes          NULL
1002
Starters
1001
1003
Item1
1002
1004
SubCat1
1003
1005
SubCat2
1003
1006
SubCat3
1003
Because adding a subcategory on SubCat3 is as simple as:
1007          SubSubCat1
1006
Processing the hierarchy becomes an iterative process (using a recursive CTE) if you have needs to do a lot of aggregation on groups. There are techniques available to make things go faster than using this pattern in the implementation, but unless
you are going to need 1000s of nodes, then this pattern works great (known as the adjacency list, where you are basically storing the adjacent node in your tree).
Louis
Without good requirements, my advice is only guesses. Please don't hold it against me if my answer answers my interpretation of your questions.

Word wrap in simple table

Hello ,
Can some one suggest , how to word wrap long strings as field value in a simple Table .In my project there is a situation where i have to dispaly long description data in a table , but because of description usually being very long the width of the table becomes very long .Urgently waiting for your response..Thanks
Vivek Kumar

I am using SUN IDM 7.1 and this is the sample code i am using . I even tried to add noWrap to feilds definig rows but unfortunatly it does'nt seem to work for me.And thanks again for ur response...
<Field name='_Lists'>
<Display class='SimpleTable'>
<Property name='columns'>
<List>
<String>Mkt Part Desc</String>
<String>End Of Service Date</String>
</List>
</Property>
<Property name='noWrap'>
<Boolean>false</Boolean>
</Property>
</Display>
<FieldLoop for='partsIndex' in="Index">
<Field name='L_MKT_PT_DESC'>
<Display class='Label'>
<Property name='text'>
<rule name='Get Desc'>
</rule>
</Property>
</Display>
</Field>
<Field name='L_ENDOFSERVICE_DT_NEW'>
<Display class='Label'>
<Property name='text'>
<rule name='Get End_service_date'>
</rule>
</Property>
</Display>
</Field>
</FieldLoop>
</Field>

{SOL}Problem in Export/Import a simple table between two diff. characterset

Hi ,
I have created a simple table on SCOTT schema....
SQL> CREATE TABLE TEST(A NUMBER(1) , B VARCHAR2(10));
Table created
SQL> INSERT INTO TEST VALUES(1 , 'TEST_TEST');
1 row inserted
SQL> COMMIT;
Commit complete
SQL> INSERT INTO TEST VALUES(2 , 'ΤΕΣΤ_ΤΕΣΤ');     <------------greek chars
1 row inserted
SQL> COMMIT;
Commit complete
The nls_parameters:
SQL> SELECT * FROM NLS_INSTANCE_PARAMETERS;
PARAMETER                      VALUE
NLS_LANGUAGE                   GREEK
NLS_TERRITORY                  GREECE
NLS_SORT
NLS_DATE_LANGUAGE
NLS_DATE_FORMAT
NLS_CURRENCY
NLS_NUMERIC_CHARACTERS
NLS_ISO_CURRENCY
NLS_CALENDAR
NLS_TIME_FORMAT
NLS_TIMESTAMP_FORMAT
NLS_TIME_TZ_FORMAT
NLS_TIMESTAMP_TZ_FORMAT
NLS_DUAL_CURRENCY
NLS_COMP
NLS_LENGTH_SEMANTICS           BYTE
NLS_NCHAR_CONV_EXCP            FALSE
17 rows selected
SQL> SELECT * FROM NLS_SESSION_PARAMETERS;
PARAMETER                      VALUE
NLS_LANGUAGE                   AMERICAN
NLS_TERRITORY                  AMERICA
NLS_CURRENCY                   $
NLS_ISO_CURRENCY               AMERICA
NLS_NUMERIC_CHARACTERS         .,
NLS_CALENDAR                   GREGORIAN
NLS_DATE_FORMAT                DD-MON-RR
NLS_DATE_LANGUAGE              AMERICAN
NLS_SORT                       BINARY
NLS_TIME_FORMAT                HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT           DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT             HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT        DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY              $
NLS_COMP                       BINARY
NLS_LENGTH_SEMANTICS           BYTE
NLS_NCHAR_CONV_EXCP            FALSE
17 rows selected
and db characterset is EL8MSWIN1253
I export such as(following generally the instuctions found on Note:227332.1-Metalink):
C:\Documents and Settings\s_k>SET ORACLE_SID=EPESY
C:\Documents and Settings\s_k>SET NLS_LANG=GREEK_GREECE.EL8MSWIN1253
C:\Documents and Settings\s_k>C:\oracle\product\10.2.0\database10g\BIN\exp SYSTE
M/passwd@EPESY FILE=C:\TEST.DMP TABLES=(SCOTT.TEST) ROWS=Y LOG=C:\TEST2.TXT
Export: Release 10.2.0.1.0 - Production on ╩Ϋ± ╔ΎΫΊ 22 12:28:58 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
╕ήώΊί ≤²Ίϊί≤ύ ≤ί: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options
╟ ίΌάή∙ή▐ ▌ήώΊί ≤ΪΎ ≤ίΪ ≈ά±άΆΪ▐±∙Ί EL8MSWIN1253 Άάώ ≤ΪΎ ≤ίΪ ≈ά±άΆΪ▐±∙Ί NCHAR AL1
6UTF16
╨±ΎίΪΎώΉά≤▀ά ήώά ίΌάή∙ή▐ Ϊ∙Ί Ώ±Ύ≤ϊώΎ±ώ≤Ή▌Ί∙Ί ΏώΊ▄Ά∙Ί Ή▌≤∙ ╙ΫΉέάΪώΆ▐≥ ─ώάϊ±ΎΉ▐≥ .
╧ Ϊ±▌≈∙Ί ≈±▐≤Ϊύ≥ ▄ΈΈάΌί ≤ί SCOTT
. . ίΌάή∙ή▐ ΪΎΫ Ώ▀ΊάΆά                           TEST          2 ή±άΉΉ▌≥ ίΌ▐≈ϋύ≤
άΊ
╟ ίΌάή∙ή▐ ΪίΈί▀∙≤ί ίΏώΪΫ≈■≥ ≈∙±▀≥ Ώ±ΎίώϊΎΏΎ▀ύ≤ύ.Then , i shutdown this database and i start the other.....
with this nls_parameters
SQL> select * from nls_session_parameters;
PARAMETER                                                                        VALUE
NLS_LANGUAGE                                                                     AMERICAN
NLS_TERRITORY                                                                    AMERICA
NLS_CURRENCY                                                                     $
NLS_ISO_CURRENCY                                                                 AMERICA
NLS_NUMERIC_CHARACTERS                                                           .,
NLS_CALENDAR                                                                     GREGORIAN
NLS_DATE_FORMAT                                                                  DD-MON-RR
NLS_DATE_LANGUAGE                                                                AMERICAN
NLS_SORT                                                                         BINARY
NLS_TIME_FORMAT                                                                  HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT                                                             DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT                                                               HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT                                                          DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY                                                                $
NLS_COMP                                                                         BINARY
NLS_LENGTH_SEMANTICS                                                             CHAR
NLS_NCHAR_CONV_EXCP                                                              FALSE
17 rows selected
SQL>
SQL> select * from nls_instance_parameters;
PARAMETER                                                                        VALUE
NLS_LANGUAGE                                                                     GREEK
NLS_TERRITORY                                                                    GREECE
NLS_SORT
NLS_DATE_LANGUAGE
NLS_DATE_FORMAT
NLS_CURRENCY
NLS_NUMERIC_CHARACTERS
NLS_ISO_CURRENCY
NLS_CALENDAR
NLS_TIME_FORMAT
NLS_TIMESTAMP_FORMAT
NLS_TIME_TZ_FORMAT
NLS_TIMESTAMP_TZ_FORMAT
NLS_DUAL_CURRENCY
NLS_COMP
NLS_LENGTH_SEMANTICS                                                             CHAR
NLS_NCHAR_CONV_EXCP                                                              FALSE
17 rows selected
with this db characterset: UTF8
C:\Documents and Settings\s_k>SET NLS_LANG=GREEK_GREECE.EL8MSWIN1253
C:\Documents and Settings\s_k>C:\oracle\product\10.2.0\database10g\BIN\imp syste
m/passwd@info FROMUSER=SCOTT TOUSER=SCOTT FILE=C:\TEST.DMP LOG=C:\TEST0_IMP.TXT
Import: Release 10.2.0.1.0 - Production on ╩Ϋ± ╔ΎΫΊ 22 12:40:16 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
╕ήώΊί ≤²Ίϊί≤ύ ≤ί: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Pr
oduction
With the Partitioning, OLAP and Data Mining options
┴±≈ί▀Ύ ίΌάή∙ή▐≥ ϊύΉώΎΫ±ή▐ϋύΆί άΏⁿ EXPORT:V10.02.01 Ή▌≤∙ ≤ΫΉέάΪώΆ▐≥ ϊώάϊ±ΎΉ▐≥
ίώ≤άή∙ή▐ ▌ήώΊί ≤ί ≤ίΪ ≈ά±άΆΪ▐±∙Ί EL8MSWIN1253 Άάώ ≤ίΪ ≈ά±άΆΪ▐±∙Ί NCHAR UTF8
server ίώ≤άή∙ή▐≥ ≈±ύ≤ώΉΎΏΎώί▀ ≤ίΪ ≈ά±άΆΪ▐±∙Ί UTF8 (ϊΫΊάΪ▐ ΉίΪάΪ±ΎΏ▐ ≤ίΪ ≈ά±άΆΪ▐±
∙Ί)
server ίΌάή∙ή▐≥ ≈±ύ≤ώΉΎΏΎώί▀ ≤ίΪ ≈ά±άΆΪ▐±∙Ί NCHAR AL16UTF16 (ϊΫΊάΪ▐ ΉίΪάΪ±ΎΏ▐ ≤ί
Ϊ ≈ά±άΆΪ▐±∙Ί nchar)
. ίώ≤άή∙ή▐ Ϊ∙Ί άΊΪώΆίώΉ▌Ί∙Ί ΪΎΫ SCOTT ≤ΪΎ SCOTT
. . ίώ≤άή∙ή▐ ΪΎΫ Ώ▀ΊάΆά                         "TEST"          2 ή±άΉΉ▌≥ ίώ≤▐≈ϋ
ύ≤άΊ
╟ ίώ≤άή∙ή▐ ΪίΈί▀∙≤ί ίΏώΪΫ≈■≥ ≈∙±▀≥ Ώ±ΎίώϊΎΏΎ▀ύ≤ύ.
C:\Documents and Settings\s_k>SQLPLUS SCOTT/TIGER
SQL*Plus: Release 10.2.0.1.0 - Production on ╩Ϋ± ╔ΎΫΊ 22 12:41:20 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
╙²Ίϊί≤ύ ≤ί:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> SELECT * FROM TEST;
         A B
         1 TEST_TEST
         2 ????_????What may be the cause.....????
Note: I use db 10g v.2 on Windows XP platform.. and the two db instances reside on the same machine....
Thanks...
Sim

"Generally speaking the value of the NLS_LANG registry key or environment variable needs to be equal to the characterset of the database."
Yes...that's why i have set the NLS_LANG env.variable to GREEK_GREECE.EL8MSWIN1253 ..equal to:
SQL> select * from nls_database_parameters;
PARAMETER                      VALUE
NLS_LANGUAGE                   AMERICAN
NLS_TERRITORY                  AMERICA
NLS_CURRENCY                   $
NLS_ISO_CURRENCY               AMERICA
NLS_NUMERIC_CHARACTERS         .,
NLS_CHARACTERSET EL8MSWIN1253
NLS_CALENDAR                   GREGORIAN
NLS_DATE_FORMAT                DD-MON-RR
NLS_DATE_LANGUAGE              AMERICAN
NLS_SORT                       BINARY
NLS_TIME_FORMAT                HH.MI.SSXFF AM
NLS_TIMESTAMP_FORMAT           DD-MON-RR HH.MI.SSXFF AM
NLS_TIME_TZ_FORMAT             HH.MI.SSXFF AM TZR
NLS_TIMESTAMP_TZ_FORMAT        DD-MON-RR HH.MI.SSXFF AM TZR
NLS_DUAL_CURRENCY              $
NLS_COMP                       BINARY
NLS_LENGTH_SEMANTICS           BYTE
NLS_NCHAR_CONV_EXCP            FALSE
NLS_NCHAR_CHARACTERSET         AL16UTF16
NLS_RDBMS_VERSION              10.2.0.1.0"nls_language doesn't come into play, nor nls_instance_parameters."
Yes...it's true.
"So, in the dump you posted, no one can tell whether those characters were INSERTed correctly at all. Your NLS_LANG *registry key* may have been set to an incorrect value (it defaults to American_America.MSWIN1252)."
Actually , i have used a third-party tool PL/SQL Developer (which does have the OracleDB10g as default home).
Looking at the Windows registry of OracleDB10g the NLS_LANG is equal to GREEK_GREECE.EL8MSWIN1253.
"Thirdly, as I implied above the NLS_LANG on import should have been American_America.UTF8."
According to the Note 227332.1 , if the db characterset of the two dbs are not the same.. then it is preferable the conversion should be done on the import process and not the export....
So, in an example described there -export from a AMERICAN_AMERICA.WE8MSWIN1252 db and import on UTF8 db - (seems exactly the same as mine) the import is done as such:
c:\>set NLS_LANG=AMERICAN_AMERICA.WE8MSWIN1252
       c:\>imp ....
The conversion to UTF8 is done while inserting the data
       in the UTF8 database.Additional notes....
I have used many different patterns doing the import......
1) Use of AMERICAN_AMERICA.UTF8
2) Use of GREEK_GREECE.EL8ISO8859P7
3) Use the appropriate NLS_LANG that corresponds to the display of chcp command....
All tries display some '?' chars.....
Anyway... I 'll continue reading ... and testing
Thanks... a lot for your points
Sim

Resizing columns in a simple table

Hello,
I have several simple tables in my structured FM files. They were copied from unstructured FM when we went DITA. I want to resize the columns so the tables look presentable. I tried to do Table > Resize Colums, but when I run the map through the DITA OT for .pdf output, the columns revert back to what they were, which is all the same width. Do I need to change the element in some way to get the column width I want?

Any knowledgeable people who can help?

Table Designer third rule thick is not working for me. Any suggestions?

I am trying to turn the third rule in a four row table thick. I go into Table Designer and select Every 3rd Thick. The others are all none. The table is not responding to the command to make the third rule thick as I need it to be. Does anyone have any suggestions? Thank you.

To remove table format overrides, you need to go to Table > Format > Custom Ruling and Shading, and set as follows:
For more info, see page 171 of my book.
-Matt
Matt R. Sullivan
co-author Publishing Fundamentals: Unstructured FrameMaker 11

FND tables design

Hi,
I was going through FND Design Data section on eTRM website .
I need to understand a few things about table design here.
I was surprised to see one composite primary key and one composite unique key instead of primary keys in single columns(concurrent_queue_id,concurrent_program_id and concurrent_processor_id) in the following tables
FND_CONCURRENT_QUEUES -- Primary Key: FND_CONCURRENT_PROCESSORS_PK(columns:application_id,concurrent_queue_id)
               Primary Key: FND_CONCURRENT_PROCESSORS_UK1(columns:application_id,concurrent_queue_name)
FND_CONCURRENT_PROGRAMS -- Primary Key: FND_CONCURRENT_PROGRAMS_PK(columns:application_id,concurrent_program_id)
               Primary Key: FND_CONCURRENT_PROGRAMS_UK1(columns:application_id,concurrent_program_name)
FND_CONCURRENT_PROCESSORS -- Primary Key: FND_CONCURRENT_QUEUES_PK(columns:application_id,concurrent_processor_id)
               Primary Key: FND_CONCURRENT_QUEUES_UK(columns:application_id,concurrent_processor_name)
Let's consider FND_CONCURRENT_QUEUES table for instance.
As per my understanding, concurrent manager name and id has to be unique throughout the suite.
But, by decalring them as composite primary/unique key with application_id column,Oracle is saying that the uniqueness of concurrent manager's id and name is maintained across one particular module(application like AP,GL etc) only and not across the entire suite.
Is that actually the case?
Also,this concurrent_queue_id column is used as foreign key for many tables.
Now, for a column to be used as a foreign key, it has to be either unique key or primary key itself alone(not a part of a composite key) in its parent table.
In this case the column is a part of a composite primary key and still being referred from many tables as foreign key.
Please clarify.Any additional comments on this are very welcome.
I have exactly the same questions for the PROGRAMS and PROCESSORS(program library) tables as well.
Thanks,
Rushi

http://etrm.oracle.com/pls/etrmlatest/etrm_search.search
requires a metalink userid

Singel Selection in Simple Table

Hi friends
I am not using an advanced table. I am using a simple table (lets say header) with 5 messagestyledtext and a singleselection bean for query purpose which i have created manually. Below this (header), I have an other table (lets say line)
I have some issues which i want to discuss.
1- When i pressed the button to query, my records fetched properly in my header table as i want and it also populates my line table because of View Link. Problem is when my records fetched in header table, my lines table shows me the records pertaining to my first record of header table but my singleselection radio is selected for last record in header table. I am assuming that my viewobjects are working fine but cursor in my table beans are not working fine. Is there any way to reset my cursor in header and lines table according to my viewobjects?
2- since i am using my own custom query panel, I have two button "Go" and "Clear". How can i program my "Clear" button to wipe out the messageinputtext beans in my query panel ?
Since i am very new to OAF, kindly reply me in detail. I read OAF Developer guide but i am unable to understand. If possible then please write the code here.
Regards

Refer
Reset single selection radio to first row of table after execution of query
You can intercept your go button click like follows
On query region we can capture the Go button click and execute our own search along with Standard Search.
OAApplicationModule ap = (OAApplicationModule)pageContext.getApplicationModule(webBean);
OAQueryBean bean = (OAQueryBean)webBean.findIndexedChildRecursive("queryRN");
if(bean!=null)
String id = (String)bean.getGoButtonName();
if(pageContext.getParameter(id)!=null)
//here use the code mentioned in the above forum. (get the first row in VO using vo.first() and set the transient attribute value for the first row to "Y"
For more information on handling go button refer
http://oafqueries.blogspot.com/2010/10/how-to-capture-go-button-for-query.html
Regards
Ravi

Fact table design horizontal vs vertical

Hi Guys,
I am putting together a list of advantages and disadvatages of horizontal vs vertical fact table orientation.
Vertical:
ID, DimensionKey1, DimensionKey2, Factno (or KPIDimensionKey), Fact
Advantages:
-Easily extendible when new facts are integration
-A lot more rows
-Density
Disadvantages:
-Applications that can only deal with the horizontal format require a few to
transpose the rows into columns (additional computing time)
Horizontal:
ID, DimensionKey1, DimensionKey2, Fact1, Fact2, Fact3, Fact4, Fact5,...
Advantages:
-The most common fact table design
-Possibly faster access
Disadvantages:
-Sparsity
-Not easy to extend

Do you agree or can add something?

TABLE DESIGN

Hi I have this business rule which makes my table design very complex(at least for me)
My application keeps track of all the patients who are admitted to the hospital with some diagnosis(disease) like TB,asthma,Heart attack etc.Also my application is suppose to keep track of any procedure (operations) like Heart transplant,heart surgery etc performed on the patients.Later,depending upon the diagnosis and procedure ,the patients are clubbed under one group (help is needed to create the table for this group).
To satisfy my requirements I create a the following tables
DIAGNOSIS
Diagnosis_code pk
Diagnosis_Desc
PROCEDURE
Procedure_Code pk
Procedure_Desc
Now I am confused on how to create the table for patient group.I mean if any patient is suffering from a diagnosis like heart attack and has undergone a procedure like Heart transplant then this kind of patient should be clubbed under the group say XYZ.Similarly if any patient is suffering from TB and has undergone a procedure like Kidney transplant then he should be clubbed under the group say ABC.In short for every patient in the hospital this table is read to club the patient under certain group.Example
PatientGroup1 SomeDiagnosisCode1 SomeDiagnosisCode2 SomeProcedureCode1
PatientGroup2 SomeDiagnosisCode1 SomeProcedureCode6
PatientGroup3 SomeDiagnosisCode8 SomeProcedureCode9 Some DiagnosisCode6
etc etc
Please help with the design of the Patient group table.
thanks
MS

Depends on a few factors ...
The most flexible (that I can think of right now) design would be as follows:
DIAGNOSIS
diag_id
diag_desc
PROSEDURE
proc_id
proc_desc
PATIENT
patient_id
patient_name
PATIENT_DIAG -- associates zero, one, or more diagnosis with a patient
patient_diag_id
patient_id
diag_id
PATIENT_PROC -- associates zero, one, or more procedures with a patient
patient_proc_id
patient_id
proc_id
DIAG_PROC_CAT -- identifies a Group
diag_proc_cat_id
diag_proc_cat_desc
DIAG_PROC_CAT_DIAG -- associates zero, one, or more diagnosis with a Group
diag_proc_cat_diag_id
diag_proc_cat_id
diag_id
DIAG_PROC_CAT_PROC -- associates zero, one, or more procedures with a Group
diag_proc_cat_proc_id
diag_proc_cat_id
proc_id
PATIENT_DIAG_PROC_CAT -- associates zero, one, or more Groups with a patient
patient_diag_proc_cat_id
patient_id
pdpc_precedence_nmbr -- (1=highest ... don't need it if you're only gonna allow one association)
diag_proc_cat_id
Put the business rule code in TRIGGERs for PATIENT_DIAG and PATIENT_PROC to INSERT appropriate values into PATIENT_DIAG_PROC_CAT ... INSERT proper rows into DIAG_PROC_CAT, DIAG_PROC_CAT_DIAG, and DIAG_PROC_CAT_PROC tables to support business rule (if patient has same diagnosis and procedures as a Group/Category, then assign that Group/Category to the patient ... if more than one applies, you may or may not allow it ... if you do, indicate which is primary if doubling on reports/ui is a bad thing) ... Users may modify DIAG_PROC_CAT, DIAG_PROC_CAT_DIAG, and DIAG_PROC_CAT_PROC tables as needed to manage their own Groups/Categories.
Good luck.

Table design question

Hello,
I have a quick question on a table design. I currently have a table that will store approval information on a report. The individual report will need to go through 3 levels of approval before it's considered final. I have considered a few different scenarios on how to design the table but I'm not sure on what is the best choice. Currently I'm using 3 columns that will store each approval. For example,
Table 1:
file_id,
subject,
summary,
division_approve,
program_approve,
group_approve
I thought about using one column and simply stepping through a higher numeric value for each approval but found that doesn't work if I want to view items that were approved only at the division_approve level. Does anyone else have any suggestions? Hopefully I provided enough information.....
Thanks in advance!
Randy

yes, better going for higher level of normalisation and desiging more tables:
tab_aproval ( id,File_id,Approval_authority,rank )
id      File_id Approval_level rank
1     1 first_level 1
2     1 second_level 2
3     1 third_level 3
4     2 first_level 1
5     2 second_level 2
tab_file_approval
file_id, subject, summary, id
1 'doc 1' 'first level done' 1
1 'doc 1' 'second level done' 2
1 'doc 1' 'third level done' 3

Provide hints on attributes rendered in a simple table.

I have a requirement that if the cursor is hovering on a attribute/column (prefer if it can be displayed when cursor is hovering on its heading) in a simple table style region, user should see detailed explanation of what that field is for (more like detailed help). i cannot use short or long tip for this because then the detailed message appears under the field for EVERY ROW and that looks ugly. I tried using 'Additional text' but for some reason that is not displaying the detailed hint message as expected.....
what can i do to provide hints when the cursor is hovering on a field/column in a simple table (prefer if it can be displayed when cursor is hovering on its heading) ??
thanks.

Any inputs please ? can it be done ?
Thanks./

Reg Table Design

Hi,
Iam working on the Customization of table in WebDynpro.I have an application which has 2 views - TableView and CustomView.In the CustomView i have a dropdownbyindex ui element which has the values as "Standard", "Transparent", "Alternating".When the user selects any of these values and clicks on the Apply button, the table design should be changed in the TableView.
Can anyone guide me as how to proceed with this?
I hope i made my requirement very clear.
Regards,
Padmalatha.K
Points will be rewarded.

Hi,
Create an attribute of type "TableDesign" [com.sap.ide.webdynpro.uielementdefinitions.TableDesign]
bind this attribute to the Type property of the table.
In the init set the values as follows. or else change according your need.
wdContext.currentContextElement().setTableDesign(WDTableDesign.STANDARD);
And in the action handler of your drop down by index you can use the following code
In the below code my attribute name is TableDesign
Based on the condition you can use the following code to change the Type.
//Assuming the key returns you the selected value as int 0..1..2
switch (key) {
     case 1:
          wdContext.currentContextElement().setTableDesign(WDTableDesign.ALTERNATING);
          break;
     case 2:
          wdContext.currentContextElement().setTableDesign(WDTableDesign.TRANSPARENT);
          break
     default:
          wdContext.currentContextElement().setTableDesign(WDTableDesign.STANDARD);
          break;
Regards
Ayyapparaj

"Simple" table design?

Similar Messages

Maybe you are looking for