Lookup tables columns as a measure?

Hi Everyone,
I am using ver 11.1.1.1.5
I am working on the lookup tables.
My lookup table is as below:
Param1 Param2 Param3 target
123 A B 100
123 A <NULL> 90
123 <NULL> <NULL> 80
Param 1, 2 and 3 come from 3 different dimension tables.
Based on the of the parameters, the value of the target is fetched.
So I am experimenting with Sparse function.
But when I use this, the "aggregation" tab is disabled and hence I cannot make this as a measure. I need to use this column for the "Target" in the KPI.
Any suggestions or alternatives?
Regards,
HPR

Thanks for your response.
Actually what happens is the sheet seems to have 2 sets of columns, namely A-D and E - I. When I sort say, column F, I select "Expand the selection", it only sorts columns E-I and A-D remains the same. Same thing happens when I sort any
column in A - D, E - I will remain the same after.
As mentioned earlier, when I click on the columns, column A - D seems to have an extra menu "TABLE TOOLS", but not column E to I.
Also, when I tried "Format as Table" under Styles and I changed the data of the table to "Column A to I ( =$A:$I), I got this error: A table cannot overlap another table
I believe the 2 sets of column stops me to perform sorting at the same time. How can revert them so that all columns belongs to the same table?
Thanks in advance. Your help is greatly appreciated!

Similar Messages

Designerd does not generate Order BY code for Sort Order on a lookup tabel column.

I am setting the Sort Order on a column which is based on a lookup table.
When generate the the module, designer does not generate the code for the Sort Order that I set on the lookup table column.
Is there a work around for this problem or is there some thing else that needs to be done in designer to make it generate the order by clause?
I will very much appreciate help.
Regards
Prasad.

A bound lookup item, will be generated as a NON-database item in Forms. Designer generates an ORDER BY CLAUSE (a Forms Block property) for the ordering. But a NON-database item cannot be included in the ORDER BY CLAUSE.
I used a stored function for ordering the lookup item.
Best regards
Harm van Zoest

Multiple columns (named the same originally) and mapped to the same lookup table are causing a Cube Build issue

Hey folks, looking for some insight here.
I've an implementation that contains some custom Enterprise columns mapped to lookup tables. In the instance I'm working with now, it looks like there was/is an issue with one of those columns. In this scenario, I have a column named
ProjectType, created initially with that name, mapped to a lookup table. This field's name was then changed to
Project Type. After that, it looks like another column was created, also called
ProjectType. So now, we have what I would have originally thought was two distinct columns, even though the names used are the same.
Below is the error we're currently getting during the Cube Build Process...
PWA:http://ps2010/PWA, ServiceApp:Project Web App, User:DOMAIN\user, PSI: SqlException occurred in DAL: <Error><Class>1</Class><LineNumber>1</LineNumber><Number>4506</Number><Procedure>MSP_EpmProject_OlapView_B8546719-4D4C-473A-84B1-89DEDA2307E0</Procedure>
<Message> System.Data.SqlClient.SqlError: Column names in each view or function must be unique. Column name 'ProjectType' in view or function 'MSP_EpmProject_OlapView_B8546719-4D4C-473A-84B1-89DEDA2307E0' is specified more than once. </Message>
<CallStack>
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureNoResult(String storedProcedureName, SqlParameter[] parameters) </CallStack> </Error>
I've tried deleting the one column, but the build still gives the above error.
Any thoughts as to how the above could be resolved?
Thanks! - M
Michael Mukalian | Jan 2010 - Dec 2010 MVP SharePoint Services | MCTS: MOSS 2007 Configuration | http://www.mukalian.com/blog

We tried taking it out of the cubes, and it builds fine. The challenge we're having is in building the cubes with that custom field "ProjectType". It's as if the cubes still hold some reference to it even when it's deleted.
Since the OLAP View ('MSP_EpmProject_OlapView_{guid}') is recreated, would it be as simple as deleting that View, and trying to recreate?
Thanks - M
Michael Mukalian | Jan 2010 - Dec 2010 MVP SharePoint Services | MCTS: MOSS 2007 Configuration | http://www.mukalian.com/blog

Stored procedure to identify column names from a lookup table

I have a working PL/SQL stored proc as below:
CREATE OR REPLACE PROCEDURE PROC_TEST IS
CURSOR GET_TEST_VALUES IS
SELECT
MF_master.comp_service_b,MF_master.normal_form_amount_b, MF_master.plan_id_b, MF_master.plan_percentage_b, MF_master.plan_service_b,MF_master.autoid,     ORA_master.comp_service_v, ORA_master.normal_form_amount_v,
ORA_master.plan_id_v, ORA_master.plan_percentage_v,
ORA_master.plan_service_v, ORA_master.autoid,     ORA_master.test_var     FROM MF_master, ORA_master
WHERE ((MF_master.autoid = ORA_master.autoid));
BEGIN
FOR REC IN GET_TEST_VALUES LOOP
begin
if rec.test_var='SVC' then
if (to_number(rec.plan_service_b) = to_number(rec.plan_service_v) ) and
(to_number(rec.comp_service_b) = to_number(rec.comp_service_v) ) then
update ORA_master set status_v = 'COMPLETE',last_updt_user_v = 'PROCEDURE',last_updt_date_v = SYSTIMESTAMP where autoid = rec.autoid;
else
update ORA_master set status_v = 'INCOMPLETE',last_updt_user_v = 'PROCEDURE',last_updt_date_v = SYSTIMESTAMP where autoid = rec.autoid;
end if;
end if;
if rec.test_var = 'TERM' then
if (to_number(rec.plan_percentage_b) = to_number(rec.plan_percentage_v) ) and
(to_number(rec.normal_form_amount_b) = to_number(rec.normal_form_amount_v) )
then
update ORA_master set status_v = 'COMPLETE',last_updt_user_v = 'PROCEDURE',last_updt_date_v = SYSTIMESTAMP where autoid = rec.autoid;
else
update ORA_master set status_v = 'INCOMPLETE',last_updt_user_v = 'PROCEDURE',last_updt_date_v = SYSTIMESTAMP where autoid = rec.autoid;
end if;
end if;
     end;
     END LOOP;
     COMMIT;
END;
What I am doing here is, if test_var = 'SVC', I am comparing 2 columns, plan_service_b and comp_service_b(with plan_service_v and
comp_service_v)
Similarly, for test_var = 'TERM', it is plan_percentage_b and normal_form_amount_b(with plan_percentage_v and normal_form_amount_v)
The above works fine as of now, but I am looking for a way to make this design more dynamic. In other words, these comparison columns may change from time
to time and each time something changes, I will have to change this code. Rather, I am looking for a way to have the comparison columns in a
lookup table that I can query to get what needs to be compared.
My thought is :
CREATE TABLE COMPARISON_COL_LOOKUP
(test_var VARCHAR2(10),
MF_column VARCHAR2(30),
ORA_column VARCHAR2(30) );
And then, insert
INSERT INTO COMPARISON_COL_LOOKUP ('SVC','PLAN_SERVICE_B','PLAN_SERVICE_V');
INSERT INTO COMPARISON_COL_LOOKUP ('SVC','COMP_SERVICE_B','COMP_SERVICE_V');
INSERT INTO COMPARISON_COL_LOOKUP ('TERM','PLAN_PERCENTAGE_B','PLAN_PERCENTAGE_V');
INSERT INTO COMPARISON_COL_LOOKUP ('TERM','NORMAL_FORM_AMOUNT_B','NORMAL_FORM_AMOUNT_V');
commit;
In this way, when tomorrow, when something changes - like new columns need to be compared for SVC or TERM, OR, if any comparisons need to
be removed, all I need to do is to change the data in this lookup table !
Now here's my question --- If I have this lookup table, how best can I update my above stored procedure to use this lookup table so that I don't need to
hard-code the column names for comparison ?
Any thoughts/suggestions are appreciated.

While it is certainly technically possible to use dynamic SQL here, I would suggest that you make absolutely certain that you're not making things unnecessarily complicated...
Dynamic SQL is generally substantially harder to write, debug, and maintain than equivalent static SQL. In addition, it takes a lot more work to ensure that dynamic SQL performs as well as static SQL (i.e. you now have to explicitly use bind variables) and that you're not introducing security holes via SQL injection.
If your comparisons are likely to change infrequently, and particularly as those changes would imply changes to the underlying requirements, I would tend to be biased toward keeping the working procedure and just planning on making code changes periodically.
Of course, not knowing your particular requirements, I certainly can't be certain that dynamic SQL would be inappropriate here, but I have seen lots of folks unnecessarily complicate their systems by building overly flexible systems that were painful to support and extend.
Justin

How to apply Foreign Keys on top of a Common Lookup table

I have an issue where i am mandated to enforce RI on an applications database (a good thing). but I have several common lookup tables where many of the "codes" reside for many different code types. I also have the mandate that i cannot change the
underlying DDL to make composite keys to match the codes table PK. I am currently looking at creating indexed views on top of the Codes table to seperate the logical tables it contains. This is several hundred views. Although doable is there another solution
I am not seeing? I have scoured the web in search of an answer knowing I cannot be the only SQL developer in this situation. I do know that I do not want to write several hundred triggers to enforce RI. Table schema below, the CdValue column is the column
that is used throughout the hundreds of tables that use this codes table, and their corresponding column is not named the same.
CREATE TABLE dbo.CodesTable (
PartyGrpId INT  NOT NULL
, CdTyp  VARCHAR ( 8 ) NOT NULL
, CompId INT  NOT NULL
, CdValue VARCHAR ( 8 ) NOT NULL
, CdValueDesc VARCHAR ( 255 ) NULL
, AltValueDesc VARCHAR ( 100 ) NULL
, DefaultInd CHAR ( 1 ) NULL
, OrderNum SMALLINT NULL
, ActiveCd CHAR ( 1 ) NULL
, ExpireDtm SMALLDATETIME NULL
, EffectDtm SMALLDATETIME NULL
, ModById INT  NULL
, ModDtm SMALLDATETIME NULL
, CreateById INT  NULL
, CreateDtm SMALLDATETIME NULL
, CONSTRAINT PC_dbo_EcdDetail
    PRIMARY KEY CLUSTERED ( PartyGrpId ASC, CdTyp ASC, CompId ASC, CdValue ASC )
    ON FG_Data
) ON FG_Data;
I did though run into one forum where a person brought up a great idea. Filtered Foreign Keys, what a novel concept, if it could work it would make so much less code to fix an issue like this. :)
ALTER TABLE dbo.BusinessStatus WITH NOCHECK
ADD CONSTRAINT FK_dbo_BusinessStatus_CodesTable FOREIGN KEY (LoanStsDtCd) REFERENCES dbo.CodesTable (CdValue) WHERE CdTyp = 'Status'
U.S. Army Airborne! The only way to fly

>> I have several common lookup tables where many of the "codes" reside for many different code types. <<
No! This is called “Automobiles, S quids and Lady Gaga” SQL and laugh at you or fire you or both. A table is a set; a set has one and only one kind of element it it. This is the basis of RDBMS and First Normal Form.
This is so bad it has a name; OTLT for “One True Lookup Table” ;I give an example of how stupid this in one of my books where a Dewey Decimal Classification for Churches is the same as the ICD code for deformed testicles.
There is no such crap as a “generic_type_code” in RDBMS. It either a “<something in particular>_type” or a “<something in particular>_code” in data modeling and the ISO-11179 standards.
You have more NULL-able columns in one table than you should have in an entire schema!
You have audit data (creation and modification) in the row under audit. This is both stupid and illegal. You cannot expose the audit trail to the data user by law. When you delete a row, you also destroy the audit trail –Doh!
You have no CHECK() constraint on the (effective_date, expiry_date) pair.
Putting “_table” in a table name is a design error called a “tibble” to make fun of how silly it. You might want to download the PDF of bad SQL code smells from Red Gate so you can avoid things like this.
>> the CdValue column is the column that is used throughout the hundreds of tables that use this codes table, and their corresponding column is not named the same. <<
“_value” and “_code” are both what ISO-1179 calls an attribute property. It is a silly as a list of adjectives without a noun.
Each encoding is a separate table in a valid schema, each with its own validation and verification. You have to stop doing this. This is fundamental!!
--CELKO-- Books in Celko Series for Morgan-Kaufmann Publishing: Analytics and OLAP in SQL / Data and Databases: Concepts in Practice Data / Measurements and Standards in SQL SQL for Smarties / SQL Programming Style / SQL Puzzles and Answers / Thinking
in Sets / Trees and Hierarchies in SQL

Creating a single context index on a one-to-many and lookup table

Hello,
I've been successfully setting up text indexes on multiple columns on the same table (using MULTI_COLUMN_DATASTORE preferences), but now I have a situation with a one-to-many data collection table (with a FK to a lookup table), and I need to search columns across both of these tables. Sample code below, more of my chattering after the code block:
CREATE TABLE SUBMISSION
( SUBMISSION_ID             NUMBER(10)          NOT NULL,
SUBMISSION_NAME           VARCHAR2(100)       NOT NULL
CREATE TABLE ADVISOR_TYPE
( ADVISOR_TYPE_ID           NUMBER(10)          NOT NULL,
ADVISOR_TYPE_NAME         VARCHAR2(50)        NOT NULL
CREATE TABLE SUBMISSION_ADVISORS
( SUBMISSION_ADVISORS_ID    NUMBER(10)          NOT NULL,
SUBMISSION_ID             NUMBER(10)          NOT NULL,
ADVISOR_TYPE_ID           NUMBER(10)          NOT NULL,
FIRST_NAME                VARCHAR(50)         NULL,
LAST_NAME                 VARCHAR(50)         NULL,
SUFFIX                    VARCHAR(20)         NULL
INSERT INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME) VALUES (1, 'Some Research Paper');
INSERT INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME) VALUES (2, 'Thesis on 17th Century Weather Patterns');
INSERT INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME) VALUES (3, 'Statistical Analysis on Sunny Days in March');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (1, 'Department Chair');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (2, 'Department Co-Chair');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (3, 'Professor');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (4, 'Associate Professor');
INSERT INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME) VALUES (5, 'Scientist');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (1,1,2,'John', 'Doe', 'PhD');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (2,1,2,'Jane', 'Doe', 'PhD');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (3,2,3,'Johan', 'Smith', NULL);
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (4,2,4,'Magnus', 'Jackson', 'MS');
INSERT INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX) VALUES (5,3,5,'Williard', 'Forsberg', 'AMS');
COMMIT;I want to be able to create a text index to lump these fields together:
SUBMISSION_ADVISORS.FIRST_NAME
SUBMISSION_ADVISORS.LAST_NAME
SUBMISSION_ADVISORS.SUFFIX
ADVISOR_TYPE.ADVISOR_TYPE_NAME
I've looked at DETAIL_DATASTORE and USER_DATASTORE, but the examples in Oracle Docs for DETAIL_DATASTORE leave me a little bit perplexed. It seems like this should be pretty straightforward.
Ideally, I'm trying to avoid creating new columns, and keeping the trigger adjustments to a minimum. But I'm open to any and all suggestions. Thanks for for your time and thoughts.
-Jamie

I would create a procedure that creates a virtual document with tags, which is what the multi_column_datatstore does behind the scenes. Then I would use that procedure in a user_datastore, so the result is the same for multiple tables as what a multi_column_datastore does for one table. I would also use either auto_section_group or some other type of section group, so that you can search using WITHIN as with the multi_column_datastore. Please see the demonstration below.
SCOTT@orcl_11gR2> -- tables and data that you provided:
SCOTT@orcl_11gR2> CREATE TABLE SUBMISSION
2 ( SUBMISSION_ID           NUMBER(10)          NOT NULL,
3    SUBMISSION_NAME           VARCHAR2(100)          NOT NULL
4 )
5 /
Table created.
SCOTT@orcl_11gR2> CREATE TABLE ADVISOR_TYPE
2 ( ADVISOR_TYPE_ID           NUMBER(10)          NOT NULL,
3    ADVISOR_TYPE_NAME      VARCHAR2(50)          NOT NULL
4 )
5 /
Table created.
SCOTT@orcl_11gR2> CREATE TABLE SUBMISSION_ADVISORS
2 ( SUBMISSION_ADVISORS_ID      NUMBER(10)          NOT NULL,
3    SUBMISSION_ID           NUMBER(10)          NOT NULL,
4    ADVISOR_TYPE_ID           NUMBER(10)          NOT NULL,
5    FIRST_NAME           VARCHAR(50)          NULL,
6    LAST_NAME           VARCHAR(50)          NULL,
7    SUFFIX                VARCHAR(20)          NULL
8 )
9 /
Table created.
SCOTT@orcl_11gR2> INSERT ALL
2 INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME)
3    VALUES (1, 'Some Research Paper')
4 INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME)
5    VALUES (2, 'Thesis on 17th Century Weather Patterns')
6 INTO SUBMISSION (SUBMISSION_ID, SUBMISSION_NAME)
7    VALUES (3, 'Statistical Analysis on Sunny Days in March')
8 SELECT * FROM DUAL
9 /
3 rows created.
SCOTT@orcl_11gR2> INSERT ALL
2 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
3    VALUES (1, 'Department Chair')
4 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
5    VALUES (2, 'Department Co-Chair')
6 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
7    VALUES (3, 'Professor')
8 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
9    VALUES (4, 'Associate Professor')
10 INTO ADVISOR_TYPE (ADVISOR_TYPE_ID, ADVISOR_TYPE_NAME)
11    VALUES (5, 'Scientist')
12 SELECT * FROM DUAL
13 /
5 rows created.
SCOTT@orcl_11gR2> INSERT ALL
2 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
3    VALUES (1,1,2,'John', 'Doe', 'PhD')
4 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
5    VALUES (2,1,2,'Jane', 'Doe', 'PhD')
6 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
7    VALUES (3,2,3,'Johan', 'Smith', NULL)
8 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
9    VALUES (4,2,4,'Magnus', 'Jackson', 'MS')
10 INTO SUBMISSION_ADVISORS (SUBMISSION_ADVISORS_ID, SUBMISSION_ID, ADVISOR_TYPE_ID, FIRST_NAME, LAST_NAME, SUFFIX)
11    VALUES (5,3,5,'Williard', 'Forsberg', 'AMS')
12 SELECT * FROM DUAL
13 /
5 rows created.
SCOTT@orcl_11gR2> -- constraints presumed based on your description:
SCOTT@orcl_11gR2> ALTER TABLE submission ADD CONSTRAINT submission_id_pk
2    PRIMARY KEY (submission_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE advisor_type ADD CONSTRAINT advisor_type_id_pk
2    PRIMARY KEY (advisor_type_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD CONSTRAINT submission_advisors_id_pk
2    PRIMARY KEY (submission_advisors_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD CONSTRAINT submission_id_fk
2    FOREIGN KEY (submission_id) REFERENCES submission (submission_id)
3 /
Table altered.
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD CONSTRAINT advisor_type_id_fk
2    FOREIGN KEY (advisor_type_id) REFERENCES advisor_type (advisor_type_id)
3 /
Table altered.
SCOTT@orcl_11gR2> -- resulting data:
SCOTT@orcl_11gR2> COLUMN submission_name FORMAT A45
SCOTT@orcl_11gR2> COLUMN advisor      FORMAT A40
SCOTT@orcl_11gR2> SELECT s.submission_name,
2          a.advisor_type_name || ' ' ||
3          sa.first_name || ' ' ||
4          sa.last_name || ' ' ||
5          sa.suffix AS advisor
6 FROM   submission_advisors sa,
7          submission s,
8          advisor_type a
9 WHERE sa.advisor_type_id = a.advisor_type_id
10 AND    sa.submission_id = s.submission_id
11 /
SUBMISSION_NAME                               ADVISOR
Some Research Paper                           Department Co-Chair John Doe PhD
Some Research Paper                           Department Co-Chair Jane Doe PhD
Thesis on 17th Century Weather Patterns       Professor Johan Smith
Thesis on 17th Century Weather Patterns       Associate Professor Magnus Jackson MS
Statistical Analysis on Sunny Days in March   Scientist Williard Forsberg AMS
5 rows selected.
SCOTT@orcl_11gR2> -- procedure to create virtual documents:
SCOTT@orcl_11gR2> CREATE OR REPLACE PROCEDURE submission_advisors_proc
2    (p_rowid IN           ROWID,
3      p_clob     IN OUT NOCOPY CLOB)
4 AS
5 BEGIN
6    FOR r1 IN
7       (SELECT *
8        FROM      submission_advisors
9        WHERE ROWID = p_rowid)
10    LOOP
11       IF r1.first_name IS NOT NULL THEN
12         DBMS_LOB.WRITEAPPEND (p_clob, 12, '<first_name>');
13         DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r1.first_name), r1.first_name);
14         DBMS_LOB.WRITEAPPEND (p_clob, 13, '</first_name>');
15       END IF;
16       IF r1.last_name IS NOT NULL THEN
17         DBMS_LOB.WRITEAPPEND (p_clob, 11, '<last_name>');
18         DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r1.last_name), r1.last_name);
19         DBMS_LOB.WRITEAPPEND (p_clob, 12, '</last_name>');
20       END IF;
21       IF r1.suffix IS NOT NULL THEN
22         DBMS_LOB.WRITEAPPEND (p_clob, 8, '<suffix>');
23         DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r1.suffix), r1.suffix);
24         DBMS_LOB.WRITEAPPEND (p_clob, 9, '</suffix>');
25       END IF;
26       FOR r2 IN
27         (SELECT *
28          FROM   submission
29          WHERE submission_id = r1.submission_id)
30       LOOP
31         DBMS_LOB.WRITEAPPEND (p_clob, 17, '<submission_name>');
32         DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r2.submission_name), r2.submission_name);
33         DBMS_LOB.WRITEAPPEND (p_clob, 18, '</submission_name>');
34       END LOOP;
35       FOR r3 IN
36         (SELECT *
37          FROM   advisor_type
38          WHERE advisor_type_id = r1.advisor_type_id)
39       LOOP
40         DBMS_LOB.WRITEAPPEND (p_clob, 19, '<advisor_type_name>');
41         DBMS_LOB.WRITEAPPEND (p_clob, LENGTH (r3.advisor_type_name), r3.advisor_type_name);
42         DBMS_LOB.WRITEAPPEND (p_clob, 20, '</advisor_type_name>');
43       END LOOP;
44    END LOOP;
45 END submission_advisors_proc;
46 /
Procedure created.
SCOTT@orcl_11gR2> SHOW ERRORS
No errors.
SCOTT@orcl_11gR2> -- examples of virtual documents that procedure creates:
SCOTT@orcl_11gR2> DECLARE
2    v_clob CLOB := EMPTY_CLOB();
3 BEGIN
4    FOR r IN
5       (SELECT ROWID rid FROM submission_advisors)
6    LOOP
7       DBMS_LOB.CREATETEMPORARY (v_clob, TRUE);
8       submission_advisors_proc (r.rid, v_clob);
9       DBMS_OUTPUT.PUT_LINE (v_clob);
10       DBMS_LOB.FREETEMPORARY (v_clob);
11    END LOOP;
12 END;
13 /
<first_name>John</first_name><last_name>Doe</last_name><suffix>PhD</suffix><submission_name>Some
Research Paper</submission_name><advisor_type_name>Department Co-Chair</advisor_type_name>
<first_name>Jane</first_name><last_name>Doe</last_name><suffix>PhD</suffix><submission_name>Some
Research Paper</submission_name><advisor_type_name>Department Co-Chair</advisor_type_name>
<first_name>Johan</first_name><last_name>Smith</last_name><submission_name>Thesis on 17th Century
Weather Patterns</submission_name><advisor_type_name>Professor</advisor_type_name>
<first_name>Magnus</first_name><last_name>Jackson</last_name><suffix>MS</suffix><submission_name>The
sis on 17th Century Weather Patterns</submission_name><advisor_type_name>Associate
Professor</advisor_type_name>
<first_name>Williard</first_name><last_name>Forsberg</last_name><suffix>AMS</suffix><submission_name
Statistical Analysis on Sunny Days inMarch</submission_name><advisor_type_name>Scientist</advisor_type_name>
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> -- user_datastore that uses procedure:
SCOTT@orcl_11gR2> BEGIN
2    CTX_DDL.CREATE_PREFERENCE ('sa_datastore', 'USER_DATASTORE');
3    CTX_DDL.SET_ATTRIBUTE ('sa_datastore', 'PROCEDURE', 'submission_advisors_proc');
4 END;
5 /
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> -- index (on optional extra column) that uses user_datastore and section group:
SCOTT@orcl_11gR2> ALTER TABLE submission_advisors ADD (any_column VARCHAR2(1))
2 /
Table altered.
SCOTT@orcl_11gR2> CREATE INDEX submission_advisors_idx
2 ON submission_advisors (any_column)
3 INDEXTYPE IS CTXSYS.CONTEXT
4 PARAMETERS
5    ('DATASTORE     sa_datastore
6       SECTION GROUP     CTXSYS.AUTO_SECTION_GROUP')
7 /
Index created.
SCOTT@orcl_11gR2> -- what is tokenized, indexed, and searchable:
SCOTT@orcl_11gR2> SELECT token_text FROM dr$submission_advisors_idx$i
2 /
TOKEN_TEXT
17TH
ADVISOR_TYPE_NAME
AMS
ANALYSIS
ASSOCIATE
CENTURY
CHAIR
CO
DAYS
DEPARTMENT
DOE
FIRST_NAME
FORSBERG
JACKSON
JANE
JOHAN
JOHN
LAST_NAME
MAGNUS
MARCH
PAPER
PATTERNS
PHD
PROFESSOR
RESEARCH
SCIENTIST
SMITH
STATISTICAL
SUBMISSION_NAME
SUFFIX
SUNNY
THESIS
WEATHER
WILLIARD
34 rows selected.
SCOTT@orcl_11gR2> -- sample searches across all data:
SCOTT@orcl_11gR2> VARIABLE search_string VARCHAR2(100)
SCOTT@orcl_11gR2> EXEC :search_string := 'professor'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2          a.advisor_type_name || ' ' ||
3          sa.first_name || ' ' ||
4          sa.last_name || ' ' ||
5          sa.suffix AS advisor
6 FROM   submission_advisors sa,
7          submission s,
8          advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string) > 0
10 AND    sa.advisor_type_id = a.advisor_type_id
11 AND    sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME                               ADVISOR
Thesis on 17th Century Weather Patterns       Professor Johan Smith
Thesis on 17th Century Weather Patterns       Associate Professor Magnus Jackson MS
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'doe'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> /
SUBMISSION_NAME                               ADVISOR
Some Research Paper                           Department Co-Chair John Doe PhD
Some Research Paper                           Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'paper'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> /
SUBMISSION_NAME                               ADVISOR
Some Research Paper                           Department Co-Chair John Doe PhD
Some Research Paper                           Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> -- sample searches within specific columns:
SCOTT@orcl_11gR2> EXEC :search_string := 'chair'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2          a.advisor_type_name || ' ' ||
3          sa.first_name || ' ' ||
4          sa.last_name || ' ' ||
5          sa.suffix AS advisor
6 FROM   submission_advisors sa,
7          submission s,
8          advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string || ' WITHIN advisor_type_name') > 0
10 AND    sa.advisor_type_id = a.advisor_type_id
11 AND    sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME                               ADVISOR
Some Research Paper                           Department Co-Chair John Doe PhD
Some Research Paper                           Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'phd'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2          a.advisor_type_name || ' ' ||
3          sa.first_name || ' ' ||
4          sa.last_name || ' ' ||
5          sa.suffix AS advisor
6 FROM   submission_advisors sa,
7          submission s,
8          advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string || ' WITHIN suffix') > 0
10 AND    sa.advisor_type_id = a.advisor_type_id
11 AND    sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME                               ADVISOR
Some Research Paper                           Department Co-Chair John Doe PhD
Some Research Paper                           Department Co-Chair Jane Doe PhD
2 rows selected.
SCOTT@orcl_11gR2> EXEC :search_string := 'weather'
PL/SQL procedure successfully completed.
SCOTT@orcl_11gR2> SELECT s.submission_name,
2          a.advisor_type_name || ' ' ||
3          sa.first_name || ' ' ||
4          sa.last_name || ' ' ||
5          sa.suffix AS advisor
6 FROM   submission_advisors sa,
7          submission s,
8          advisor_type a
9 WHERE CONTAINS (sa.any_column, :search_string || ' WITHIN submission_name') > 0
10 AND    sa.advisor_type_id = a.advisor_type_id
11 AND    sa.submission_id = s.submission_id
12 /
SUBMISSION_NAME                               ADVISOR
Thesis on 17th Century Weather Patterns       Professor Johan Smith
Thesis on 17th Century Weather Patterns       Associate Professor Magnus Jackson MS
2 rows selected.

How to create a lookup table in flex

Hi,
I am not sure how to construct and use a lookup table in flex, i have a string which needs to replaced with a string in the lookup table. Can someone let me know can i can do this.
Thanks

@learningflex,
Here is the simple example of doing this..
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" creationComplete="onCreationComplete();">
   <mx:Script>
   <![CDATA[
     import mx.collections.ArrayCollection;
     import flash.utils.setInterval;
     import mx.controls.Alert;
[Bindable]
private var dataList:ArrayCollection = new ArrayCollection([
{name:'Person'},
{name:'Student'},
{name:'Teacher'},
{name:'Employee'}]);
    private function onCreationComplete():void
      for(var i:int=0;i<dataList.length;i++)
       var obj:Object = dataList.getItemAt(i);
       obj.abbr = getAbbrevatedName(obj.name);
       dataList.setItemAt(obj,i);
      dataGrid.dataProvider = dataList;
    private function getAbbrevatedName(name:String):String
      switch(name)
       case "Person":
        return "prsn";
       case "Student":
        return "sdt";
       case "Teacher":
        return "tcr";
       case "Employee":
        return "emp";
       default:
        return "";
   ]]>
   </mx:Script>
<mx:DataGrid id="dataGrid" x="10" y="177" visible="true">
<mx:columns>
   <mx:DataGridColumn headerText="Actual Name" dataField="name"/>
   <mx:DataGridColumn width="150" headerText="Abbrevated Name" dataField="abbr"/>
</mx:columns>
</mx:DataGrid>
</mx:Application>
See I have displayed both the FullNames in one column and also the abbrevated names in another column. So you can make use of the second column.
Thanks,
Bhasker

Error while updating lookup table through PSI

Hi,
I am trying to update a lookuptable through PSI using following code :
$lookupTableGuid = $svcPSProxy.ReadLookupTables($EPMTYString, 0 , 1033).LookupTables | where {$_.LT_NAME -eq $Lookuptablename}
$lookuptable = $svcPSProxy.ReadLookupTablesbyUids($lookupTableGuid.LT_UID, 1 , 1033)
$lookuptablerowValues = $svcPSProxy.ReadLookupTablesbyUids($lookupTableGuid.LT_UID, 0 , 1033).LookupTableTrees
#get lookup table count
$lookuptableValues = $svcPSProxy.ReadLookupTablesbyUids($lookupTableGuid.LT_UID, 0 , 1033).LookupTableTrees
$count = $lookuptableValues.Count +1
#Insert the rows of table in Lookup Table
foreach ($rows in $table)
$value_Code = $rows.Item("Project_code")
$value_Name = $rows.Item("project_desc")
$GUID = [System.Guid]::NewGuid()
$LookupRow = $lookuptable.LookupTableTrees.NewLookupTableTreesRow()
$LookupRow.LT_STRUCT_UID = $GUID
$LookupRow.LT_UID = $lookupTableGuid.LT_UID
$LookupRow.LT_VALUE_TEXT = $value_Code
$LookupRow.LT_VALUE_DESC = $value_Name
$LookupRow.LT_VALUE_SORT_INDEX = ($count ++)
$lookuptable.LookupTableTrees.AddLookupTableTreesRow($LookupRow)
$error.clear()
#Exceptions Handling :
Try
$svcPSProxy.UpdateLookupTables($lookuptable , 0 , 1 , 1033)
Catch
write-host "Error updating the Lookup table, see the error below:" -ForeGroundColor Red -BackGroundColor White
write-host "$error" -ForeGroundColor Red
Initially, I tried to run with value of $value_code as "AACL", the code worked.
But when I tried to insert value of code as "AACL - ALKYL AMINES CHEMICALS LIMITED"
I got following error:
Exception calling "UpdateLookupTables" with "4" argument(s): "Response is not well-formed XML."
I could not understand why this error is appearing as I just added ' - ' to my code value. I checked for validity of ' - 'in the targeted column. No issue with that.
Please help.
Thanks and regards,
Jayesh

Hi All,
The entries are maintained from DB level.
Thanks for the help.
DVRK

Limiting the values in a lookup table

Hello everyone.
I was wondering if it is possible to limit the selectable values in a lookup table based on certain criteria, foremost the content of a separate field.
Example:
A product has a measurement key that determines which sizes are valid for a given product.
Is it possible for MDM to read this key and filter the values of the table holding all the values for all keys?
Hope that was somewhat clear what I'm trying to do.
Best regards,
Anders

Hello Andres:
I believe that what you should do is to place all the products types into Categories. There, you can give different attributes to each product and therefore, limit what the user can choose as its values.
For instance, you have two products A and B. Each one would have a separate "Measure" field.
Create Categories:
Cat_A
Cat_B
with separate attributes:
Cat_A
|____ Measure_A
Cat_B
|____ Measure_B
And in each Measure <b>Attribute</b> (not field) you can specify the correct values for each category (i.e Product type)
When the user chooses Cat_A as the product type, the Measure_A will appear, with its values. The same will happend for Cat_B
I hope that helps
Regards
Alejandro

Proper use of a Lookup table and adaptations for NET

Hello,
I need to create a few lookup tables and I often see the following:
create table Languages
Id int identity not null primary key (Id),
Code nvarchar (4) not null,
Description nvarchar (120) not null,
create table Posts
Id int identity not null primary key (Id),
LanguageId int not null,
Title nvarchar (400) not null,
insert into Languages (Id, Code, Description)
values (1, "en", "English");
This way I am localizing Posts with language id ...
IMHO, this is not the best scheme for Languages table because in a Lookup table the PK should be meaningful, right?
So instead I would use the following:
create table Languages
Code nvarchar (4) not null primary key (Code),
Description nvarchar (120) not null,
create table Posts
Id int identity not null primary key (Id),
LanguageCode nvarchar (4) not null,
Title nvarchar (400) not null,
insert into Languages (Code, Description)
values ("en", "English");
The NET applications usually use language code so this way I can get a Post in English without using a Join.
And with this approach I am also maintaining the database data integrity ...
This could be applied to Genders table with codes "M", "F", countries table, transaction types table (should I?), ...
However I think it is common to use int as PK in lookup tables because it is easier to map to ENUMS.
And know it is even possible to map to Flag Enums so have a Many to Many relationship in an ENUM.
That helps in NET code but in fact has limitations. A Languages table could never be mapped to a FLags Enum ...
... An flags enum can't have more than 64 items (Int64) because the keys must be a power of two.
A SOLUTION
I decided to find an approach that enforces database data integrity and still makes possible to use enums so I tried:
create table Languages
Code nvarchar (4) not null primary key (Code),
Key int not null,
Description nvarchar (120) not null,
create table Posts
Id int identity not null primary key (Id),
LanguageCode nvarchar (4) not null,
Title nvarchar (400) not null,
insert into Languages (Code, Key, Description)
values ("en", 1, "English");
With this approach I have a meaningfully Language code, I avoid joins and I can create an enum by parsing the Key:
public enum LanguageEnum {
[Code("en")
English = 1
I can even preserve the code in an attribute. Or I can switch the code and description ...
What about Flag enums? Well, I will have not Flag enums but I can have List<LanguageEnum> ...
And when using List<LanguageEnum> I do not have the limitation of 64 items ...
To me all this makes sense but would I apply it to a Roles table, or a ProductsCategory table?
In my opinion I would apply only to tables that will rarely change over time ... So:
    Languages, Countries, Genders, ... Any other example?
About the following I am not sure (They are intrinsic to the application):
   PaymentsTypes, UserRoles
And to these I wouldn't apply (They can be managed by a CMS):
   ProductsCategories, ProductsColors
What do you think about my approach for Lookup tables?
Thank You,
Miguel

>>IMHO, this is not the best scheme for Languages table because in a Lookup table the PK should be meaningful, right?<<
Not necessarily. The choice to use, or not to use, a surrogate key in a table is a preference, not a rule. There are pros and cons to either method, but I tend to agree with you. When the values are set as programming terms, I usually use a textual value
for the key. But this is nothing to get hung up over.
Bear in mind however, that this:
    create table Languages
      Id int identity not
null primary key
(Id),
      Code nvarchar (4)
not null, Description nvarchar
(120) not
null,
is not equivalent to
    create table Languages
      Code nvarchar (4)
not null primary
key (Code),
      Description nvarchar (120)
not null,
The first table needs a UNIQUE constraint on Code to make these solutions semantically the same. The first table could have the value 'Klingon' in it 20 times while the second only once.
>>However I think it is common to use int as PK in lookup tables because it is easier to map to ENUMS.<<
This was going to be my next point. For that case, I would only change the first table to not have an identity assigned key value, as it would be easier to manage at the same time and manner as the enum.
>>. A Languages table could never be mapped to a FLags Enum ...<<
You could, but I would highly suggest to avoid any values encoded in a bitwise pattern in SQL as much as possible. Rule #1 (First Normal Form) is partially to have 1 value per column. It is how the optimizer thinks, and how it works best.
My rule of thumb for lookup (or I prefer the term "domain" tables, as really all tables are there to look up values :)), is all data should be self explanatory in the database, through data if at all possible. So if you have a color column,
and it contains the color "Vermillion", and all you will ever need is the name, and you feel like it is good enough to manage in the UI, then great. But bear in mind, the beauty of a table that is there for domain purposes, is that you can then store
the R, G, and B attributes of the vermillion color (254, 73, 2 respectively, based on
http://www.colorcombos.com/colors/FE4902) and you can then use that in coding. Alternate names for the color could be introduce, etc. And if UserRoles are 1, 2, 3, and 42 (I have seen worse), then
definitely add columns. I think you are basically on the right track.
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.

How do I handle values in source that are not in "lookup" table?

hi there,
I have 3 tables (all Oracle technology):
1) Source table: CALLS with columns MSISDN, TRANS_DATE, TYPE, COST, DURATION
2) Lookup table: SUBSCRIBERS with columns SUBSCRIBERID, MSISDN, IMSI
3) Target table: FACT_CALLS with columns SUBSCRIBERID (not null), CALLDATE, CALLTYPE, CALLDURATION, CALLCHARGE.
Join between source and lookup table:
NVL(CALLS.MSISDN,0) =SUBSCRIBERS.MSISDN)
Mappings on target:
FACT_CALLS.SUBSCRIBERID --> SUBSCRIBERS.SUBSCRIBERID
FACT_CALLS.CALLDATE --> CALLS.TRANS_DATE
FACT_CALLS.CALLTYPE --> CALLS.TYPE
FACT_CALLS.CALLDURATION --> CALLS.DURATION
FACT_CALLS.CALLCHARGE --> CALLS.CHARGE
I have a dummy value in SUBSCRIBERS with values MSISDN = 0, SUBSCRIBERID = 0 and IMSI = 0, to be used if MSISDN in the source table is null or does not exist in the lookup table.
The NVL on the join takes care of the case when source MSISDN is null and this is working fine i.e. returns 0 for SUBSCRIBERID.
The problem occurs when the source MSISDN does have a value but such a value does not exist in the lookup table, such records are rejected.
How do I implement a solution for this?

hi Guru,
Yes I have 2 source tables and a target.
1) I created a join by dragging MSISDN on CALLS to MSISDN on SUBSCRIBERS then added the NVL part to have NVL(CALLS.MSISDN,0) =SUBSCRIBERS.MSISDN)
2) the target does not have MSISDN. Using the join the target SUBSCRIBERID column gets populated with the correct value from the lookup table.
i.e. FACT_CALLS.SUBSCRIBERID = (select SUBSCRIBERID from SUBSCRIBERS where SUBSCRIBERS.MSISDN = CALLS.MSISDN)

Lookup Table and Target Table are the same

Hi All,
I have a requirement in which I have to lookup the target table and based on the records in it, I need to load a new record into the target table.
Being very specific,
Suppose I have a key column which when changes I want to generate a new id and then insert this new value.
The target table record structure looks like this
list_id list_key list_name
1 'A' 'NAME1'
1 'A' 'NAME2'
1 'A' 'NAME3'
2 'B' 'NAME4'
2 'B' 'NAME5'
As shown the target table list_id changes only when the list key changes. I need to generate the list_id value from within OWB mapping.
Can anyone throw some light as to how this can be done in OWB???
regards
-AP

Hello, AP
You underestimate the power of single mapping :) If you could tolerate using additional stage table (with is definitly recomended in case your table from example will account a lot of rows).
You underestimate the power of single mapping :) It you could tolerate using additional stage table (witch is definitely recommended in case your table from example will account a lot of rows), you could accomplish all you need within one mapping and without using PLSQL function. This is true as far as you could have several targets within one mapping.
Source ----------------------------------------------------- >| Join2 | ---- > Target 2
|------------------------ >|Join 1| --> Lookup table -->|
Target Dedup >|
Here Target your target table. Join 1 operator covers operations needed to get existing key mapping (from dedup) and find new mappings. Results are stored within Lookup Table target (operation type TRUNCATE/INSERT).
Join 2 is used to perform final lookup and load it into the Target 2 the same as Target
The approach with lookup table is fast and reliable and could run on Set base mode. Also you could revisit lookup table to find what key mapping are loaded during last load operation.
Serhit

OBI Joining two lookup tables. [nQSError: 14025] No fact table exists at the requested level of detail

Hello,
I basically have only fact tables that I need for my analysis. No dimensions, no hierarchies.
When add two tables in OBI Answers to start the analysis I see this error:
[nQSError: 14025] No fact table exists at the requested level of detail
I have them defined as lookup tables. How can I join lookup tables?
In order to pre-filter them using the user_name session variable.

Hi Nagireddy.
As described:
open your rpd. go to "manage" -> Variable Manager / New / Session / Variable. so to create a new session variable in the .rpd.
then you create a variable NO_FORCE_TO_DETAIL_BIN and se the default to 1.
BUT....this did actually not do the trick
I have created a logical table that is a table made up of the two that I just want to join and as soon as I create a bi answers report that contain columns from those two tables I see the error 14025.

Distinct count using lookup table

How can I get a distinct count of column values using a different table?
Let's say I want to get a distinct count of all "company_name" records in table "emp" that corespond (match) with "lookup" table, "state" category.
What I want is to find counts for all companies that have a value of "california" in the "state" column of the "lookup" Table. I want the output to look like:
Sears 17
Pennys 22
Marshalls 6
Macys 9
I want the result to show me the company names dynamically as I don't know what they are, just that they are part of the "state" group in the lookup Table. Does this make sense?
M

Mark,
In the future you might consider creating test cases for us to work with. Something similar to the following where sample data is created for each table as the union all of multiple select statementsselect 'INIT_ASSESS' lookup_type
     , 1 lookup_value
     , 'Initial Assessment' lookup_value_desc
from dual union all
select 'JOB_REF', 2, 'Job Reference' from dual union all
select 'SPEC_STA', 3, 'SPEC STA' from dual;
select 'INIT_ASSESS' rfs_category
     , 1 val
from dual union all
select 'JOB_REF', 1 from dual union all
select 'JOB_REF', 1 from dual union all
select 'SPEC_STA', null from dual;Then we can either take your select statements and make them the source of a CTAS (create table as) statementcreate table lookup as
select 'INIT_ASSESS' lookup_type
     , 1 lookup_value
     , 'Initial Assessment' lookup_value_desc
from dual union all
select 'JOB_REF', 2, 'Job Reference' from dual union all
select 'SPEC_STA', 3, 'SPEC STA' from dual;, or include them as subfactored queries by using the with statement:with lookup as (
select 'INIT_ASSESS' lookup_type
     , 1 lookup_value
     , 'Initial Assessment' lookup_value_desc
from dual union all
select 'JOB_REF', 2, 'Job Reference' from dual union all
select 'SPEC_STA', 3, 'SPEC STA' from dual
), RFS as (
select 'INIT_ASSESS' rfs_category
     , 1 val
from dual union all
select 'JOB_REF', 1 from dual union all
select 'JOB_REF', 1 from dual union all
select 'SPEC_STA', null from dual
select lookup_value_desc, count_all, count_val, dist_val
from lookup
join (select rfs_category
             , count(*) count_all
             , count(val) count_val
             , count(distinct val) dist_val
          from RFS group by rfs_category)
    on rfs_category = lookup_type;Edited by: Sentinel on Nov 17, 2008 3:38 PM

Lookup Table Name for Sale Order Types

Hello,
What's the Lookup table name that contains the "meaning" for the column ORDER_TYPE_ID in the OE_ORDER_HEADERS_ALL table?
Thanks,
Smita

Thank you Srikanth!
I was just checking into the OE_TRANSACTION_TYPES table and it was empty!?
But OE_TRANSACTION_TYPES_TL did the trick!
Thanks again!
Smita:)

Lookup tables columns as a measure?

Similar Messages

Maybe you are looking for