Regarding IF(IS NOT NULL) condition in Assignment

Hello, I am trying to write assignment with functions IF(IS NOT NULL(Product.record),xyz). In this condition, it seems IF condition is not working at all. Can some one confirm that in Assignment, IF condition do not work the way it works in Validation? I am using MDM 7.1 SP04.

Hi Priya,
1st thing as i can see COUNTRY Should be a field in your Main Table which is look-up to some Flat Table say Countries which has some fields (e.g First Name etc). You want if COUNTRY Field of your main table has some value mean that COUNTRY field is populated in your Main table then First Name field value (Which is available in Countries) should be populated using assignment. Suppose your Countries table has two records and two fields as shown below:
COUNTRYCODE FIRSTNAME
IND ABC
US XYZ
2nd thing if your Field COUNTRY of Main table is empty then First Name Value will not be populated as your field COUNTRY of main table is not linked with Countries table. Your Assignment Expression should be like this as given below:
IF(IS NOT NULL(COUNTRY.RECORD), COUNTRY.First Name)
Off-course, if country.record is null mean does not have any value assigned IND or US for main table record with Field COUNTRY, it removes the existing first name value since now this field COUNTRY of your main-table is empty and has not any value (US or IND) and therefore has not any linking of your Main table COUNTRY Field with Look-up Flat Table Countries and hence will remove the existing value.
But if your main table field COUNTRY has a value IND for a main table record, then using assignment expression it will populate ABC. If a main table record has value US then will populate FIRSTNAME XYZ using assignment Expression.
Can you please update the status of thread?
Regards,
Mandeep Saini

Similar Messages

How to add a "item not null" condition to an existing request condition ?

Hi,
I have a condition for displaying a region ;
Request Is NOT Contained within Expression 1
Expression 1 value is : "GET_DETAIL_MONTH || GET_DETAIL_DAY"
It works fine.
But the problem is that I would like to add a condtion to this. This condition would be that the item P10_DEPT is not NULL.
How to do ?
Thank you for your kind answers.

Hello,
Swith the condition type to a PL/SQL Expression and enter
(:P10_DEPT IS NOT NULL) and (:REQUEST NOT IN ('GET_DETAIL_MONTH','GET_DETAIL_DAY'))
Greetings,
Roel
http://roelhartman.blogspot.com/
You can reward this reply by marking it as either Helpful or Correct ;-)

Testing for IS NOT NULL with left join tables

Dear Experts,
The query is showing the NULL rows in the query below....
Any ideas, advice please? tx, sandra
This is the sql inspector:
SELECT O100321.FULL_NAME_LFMI, O100321.ID, O100404.ID, O100321.ID_SOURCE
, O100404.NAME, O100321.PERSON_UID, O100404.PERSON_UID, O100404.VISA_TYPE
FROM ODSMGR.PERSON O100321
, ODSMGR.VISA O100404
WHERE ( ( O100321.PERSON_UID = O100404.PERSON_UID(+) ) ) AND ( O100404.VISA_TYPE(+) IS NOT NULL )

Hi Everyone,
I am understanding alot of what Michael and Rod wrote.... I am just puzzled over the following:
the query below is left joining the STUDENT table to
HOLD table.
The HOLD table - contains rows for students who have holds on their record.
a student can have more than one hold (health, HIPAA, basic life saving course)
BUT, for this query: I'm only interested that a hold exists, so I'm choosing MAX on hold desc.
Selecting a MAX, helps me, bec. it reduces my join to a 1 to 1 relationship, instead of
1 to many relationship.
Before I posted this thread at all, the LEFT JOIN below testing for IS NOT NULL worked w/o
me having to code IS NOT NULL twice....
Is that because, what's happening "behind the scenes" is that a temporary table containing all max rows is being
created, for which Discoverer has no predefined join instructions, so it's letting me do a LEFT JOIN and have
the IS NOT NULL condition.
I would so appreciate clarification. I have a meeting on Tues, for which I have to explain LEFT JOINS to the user
and how they should create a query. I need to come up with rules.
If I feel "clear", I asked my boss to buy Camtasia videocast software to create a training clip for user to follow.
Also, if any Banner user would like me to email the DIS query to run on their machine, I would be glad to do so.
thx sooo much, Sandra
SELECT O100384.ACADEMIC_PERIOD, O100255.ID, O100384.ID, O100255.NAME, O100384.NAME, O100255.PERSON_UID, O100384.PERSON_UID, MAX(O100255.HOLD_DESC)
FROM ODSMGR.HOLD O100255, ODSMGR.STUDENT O100384
WHERE ( ( O100384.PERSON_UID = O100255.PERSON_UID(+) ) ) AND ( O100384.ACADEMIC_PERIOD = '200820' )
GROUP BY O100384.ACADEMIC_PERIOD, O100255.ID, O100384.ID, O100255.NAME, O100384.NAME, O100255.PERSON_UID, O100384.PERSON_UID
HAVING ( ( MAX(O100255.HOLD_DESC(+)) ) IS NOT NULL )
ORDER BY O100384.NAME ASC

SQL 7 - Oracle 8i - NOT NULL dropped for IDENTITY column

It appears that OMWB is dropping the NOT NULL condition for columns defined as IDENTITY in SQL server 7.
SQL code to create table:
CREATE TABLE [dbo].[PCPrsnCorp] (
[PrsnCorpId] [int] IDENTITY (1, 1) NOT NULL ,
[PrsnCorpTpEnum] [tinyint] NOT NULL ,
[Name] [varchar] (128) NOT NULL ,
[NameFirstIdx] [smallint] NULL ,
[NameMidIdx] [smallint] NULL ,
[NameLastIdx] [smallint] NULL ,
[NameSuffixIdx] [smallint] NULL ,
[NameLine2Idx] [smallint] NULL ,
[CmpyId] [smallint] NULL ,
[ClsnId] [int] NOT NULL
) ON [PRIMARY]
GO
OMWB migration script:
REM
REM Message : Created Table :sa.PCPRSNCORP
REM User : system
CREATE TABLE sa.PCPRSNCORP(PRSNCORPID NUMBER (10,0) ,PRSNCORPTPENUM NUMBER
(3,0) NOT NULL,NAME VARCHAR2 (128) NOT NULL,NAMEFIRSTIDX NUMBER (5,0)
,NAMEMIDIDX NUMBER (5,0) ,NAMELASTIDX NUMBER (5,0) ,NAMESUFFIXIDX NUMBER
(5,0) ,NAMELINE2IDX NUMBER (5,0) ,CMPYID NUMBER (5,0) ,CLSNID NUMBER
(10,0) NOT NULL) TABLESPACE ORACLEFULL
NOT NULL appears to be handled correctly if colummn is not defined as IDENTITY. Is there a patch, workaround, or OMWB option to get past this?

Currently, the Migration Workbench converts IDENTITY columns into a BEFORE INSERT trigger and an Oracle sequence.
This trigger will fire prior to any INSERT statement executing against the table. The trigger inserts the next value of the defined sequence into the converted IDENTITY column.
The NOT NULL column attribute is therefore no longer needed.
Strictly speaking, it would do no harm to keep the NOT NULL column attribute and so I will log a bug on your behalf.
Thanks for the info.
Brian.

Conditional Not Null

I am trying to create an item level validation on an entry form for a Conditional Not Null. For example ...
Field 1 = Animal Type
Field 2 = Dog Type
If Field 1 = Dog .... Field 2 must be Not Null.
Can someone help me set this up. Thanks in advance for your assistance.

Are REQUEST_TYPE and ACCT_EXTERNAL_ONLY page items? Because in that case you have to use the bind variable syntax to access them.
IF :REQUEST_TYPE = 'External' AND :ACCT_EXTERNAL_ONLY IS NULL THEN
RAISE_APPLICATION_ERROR (-20001,'Error Message');
END IF;Patrick
My APEX Blog: http://www.inside-oracle-apex.com
The APEX Builder Plugin: http://builderplugin.oracleapex.info/
The ApexLib Framework: http://apexlib.sourceforge.net/

How to combine two conditions : Exists and Item not null ?

Hello !
I have a flash chart region that I would like to display only if two conditions are both true.
The first condition is this one :
Exists (SQL query returns at least one row) :
select 1
from    observatoire.fiche aa, observatoire.activite_faite bb
where   aa.fiche_id = bb.fiche_id
and     bb.fiche_id = aa.fiche_id
AND     bb.activites_id = TO_NUMBER(:P23_ACTIVITES_ID)
AND     TRUNC(aa.date_activite, 'YYYY') = TRUNC(TO_DATE(:P23_ANNEE, 'YYYY'), 'YYYY')And the second condition would be :
Item not null :
P23_ACTIVITES_IDHow to combine these two conditions into one display condition ?
Thank you .
Christian

Hello,
The issue is that you're doing -
TO_NUMBER(:P23_ACTIVITES_ID)When you leave the Null return value blank like that, you'll typically see '%null%' used in session state (i.e. it's not actually null). Obviously '%null%' can't be converted to a number, hence the error you're seeing.
A simple solution would be to make your null return value -1 or some other value that is guaranteed not to be a valid id (and alternative is to convert the %null% to a real null via an App/Page process etc (if you search this forum you'll find a few examples on how to do that). Another alternative is to use a DECODE to detect the '%null%' etc.
Hope this helps,
John.
Blog: http://jes.blogs.shellprompt.net
Work: http://www.apex-evangelists.com
Author of Pro Application Express: http://tinyurl.com/3gu7cd
REWARDS: Please remember to mark helpful or correct posts on the forum, not just for my answers but for everyone!

Difference between Not Null and Null..

Hi All,
In Conditional Region portion i would like to know the difference between
Value of item in Expression 1 is not null and we will assign the text filed name in expression.
Value of item in Expression 1 is null
When we have use the above two scenerio's ..
Not null means what it has some value in text filed or not.
pls help me out.
Anoo..

Hello Anoo,
Validations check the input and will return an error message if the validation is not met (like 'Field is required').
Conditions can be used to run a Process (or render an item) when some condition is met - or not- (like do this only when field is not null).
Greetings,
Roel
http://roelhartman.blogspot.com/
http://www.bloggingaboutoracle.org/
http://www.logica.com/

How to use Not Null in

Hi All,
I did one personalization which is related to DFF of an Item.
It is working partially but i need the perfect solution will u please resolve my doubts.
My requirement is as follows:
I have one DFF in Items page say attribute1 which has a maximum of 3 values i.e., 'A' or 'B' or 'C'
In my Purchase order Auto create form, when an select an requisition, the related lines are displayed for me.
When i select an line and if the line has an item which has an attribute values of either 'A' or 'B' or 'C'.
Then i need to display an error message.
For this I do the following steps.
In conditions tab i wrote the following condiitons:
Not Null IN ( SELECT attribute1 FROM mtl_system_items_b where segment1= :REQ_LINES.ITEM_NUMBER AND organization_id=FND_PROFILE.VALUE('ORG_ID'))
But my condition evaluates to false, even though i have values in attribute1---------------------- My question is will the above query is right or not. if not will u please provide me the correct syntax of how to use not null.
'A' IN ( SELECT attribute1 FROM mtl_system_items_b where segment1= :REQ_LINES.ITEM_NUMBER AND organization_id=FND_PROFILE.VALUE('ORG_ID'))
The above query is working fine. Please help me on this issue.
Thanks and Regards
Zaheer

Dear Zaheer,
you compare the organization with Operating unit, Please use
fnd_profile.value('MFG_ORGANIZATION_ID') inspite of org_id.
Tariq.

Not null and enable or disable column in tabular form

Hi,
Using apex version 4.1 and working on tabular form.
ACT_COA_SEGMENT_MAS is Master table
and
ACT_SEGMENT_VALUES_MAS is detail table
I have entered 8 rows in master table and PARENT_SEGMENT_ID is column in master table which is null able. If i specified PARENT_SEGMENT_ID with value in master table then in detail table there is column PARENT_ID that should not be null and enable.
How i can enable or disable column when in master table PARENT_SEGMENT_ID column is null then in detail table PARENT_ID column should disable and vice versa.
I have created tabular form on Detail table. before insert into the tabular form Check in master table in first entry if PARENT_SEGMENT_ID is not null in first row of master table then in tabular form PARENT_ID should enable and not null able in corresponding to this first row id's lines in tabular form.
Same should check for second row in master table if PARENT_SEGMENT_ID is not null then entered rows with PARENT_ID into tabular form corresponding to 2nd id in master table should not nullable and column should enable in tabular form.
Thanks & Regards
Vedant
Edited by: Vedant on Jan 9, 2013 9:12 PM

Vedant,
You need to create you own manual tabular form and not use the wizard.
Using APEX_ITEM api you should be build you own form and you will be able to control how you wan to display the rows. (See Link [Apex Item Help|http://docs.oracle.com/cd/E37097_01/doc/doc.42/e35127/apex_item.htm#CACEEEJE] )
select case when PRIMARY_TABLE_COLUMN is null then APEX_ITEM.DISPLAY_AND_SAVE(3 , DETAIL_COLUMN ) else APEX_ITEM.TEXT(2,detail_column) end "ALIAS" from detail table
Hope that help.
Vivek

Is not null and null join

Hi, I am trying to properly display a list of tasks for a project however without a join to the project number (which I was aware of) and the employee table, I get over 500 results.
The task can be created without a employee assigned to it so therefore the page does not require the field to be filled in.
Here is the SQL code, any does anyone have any ideas?
select
    pd.pk_proj_detail_id    "Task Number",
    pd.task_title           "Task Title",
    pd.DETAIL_STATUS        "Task Status",
    pm.name                 "Associated Project",
    pps.last_name||', '||pps.first_name||', '||pps.middle_initial||'.' "Assigned Employee",
    pd.TRACKIT_NUMBER       "TrackIt! Number",
    pd.CREATEBY_DATE        "Date Entered",
    pd.DATE_BEGIN           "Date Began",
    pd.ESTIMATED_DATE       "Estimated Completion Date",
    pd.DATE_END             "Date Completed"
from
    PROTRAC_DETAIL pd,
    protrac_master pm,
    cobr.vw_pps_payroll pps,
    resources r
where
    pd.fk_proj_master_id = pm.PK_PROJ_MASTER_ID
    and r.fk_master_id = pm.PK_PROJ_MASTER_ID
    and (r.emp_id = pps.emple_no
        or r.emp_id is null)

It's 10g r2 with Application Express 3.1.0.00.32
This is the tasks (detail) table
ALTER TABLE PROTRAC_DETAIL
DROP PRIMARY KEY CASCADE;
DROP TABLE PROTRAC_DETAIL CASCADE CONSTRAINTS;
CREATE TABLE PROTRAC_DETAIL
PK_PROJ_DETAIL_ID      NUMBER                 NOT NULL,
FK_PROJ_MASTER_ID      NUMBER,
TRACKIT_NUMBER         NUMBER,
DETAIL_DESCRIPTION     VARCHAR2(4000 CHAR),
DETAIL_STATUS          VARCHAR2(19 CHAR),
DETAIL_STATUS_COMMENT VARCHAR2(4000 CHAR),
DATE_BEGIN             DATE,
DATE_END               DATE,
ESTIMATED_DATE         DATE,
CREATEBY_DATE          DATE,
CREATEBY_USER          VARCHAR2(50 CHAR),
LASTMOD_DATE           DATE,
LASTMOD_USER           VARCHAR2(50 CHAR),
TASK_TITLE             VARCHAR2(100 CHAR)
TABLESPACE DEVPROTRAC_DATA
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            MINEXTENTS       1
            MAXEXTENTS       2147483645
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
CREATE UNIQUE INDEX PROTRAC_DETAIL_PK ON PROTRAC_DETAIL
(PK_PROJ_DETAIL_ID)
TABLESPACE DEVPROTRAC_DATA
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            MINEXTENTS       1
            MAXEXTENTS       2147483645
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
CREATE OR REPLACE TRIGGER BUI_PROTRAC_DETAIL
before insert or update
on PROTRAC_DETAIL
referencing new as New old as Old
for each row
begin
    if inserting then
        select users_seq.nextval, sysdate, apex_application.g_user
            into :new.pk_proj_detail_id, :new.createby_date, :new.createby_user
            from dual;
    elsif updating then
        select sysdate, apex_application.g_user
            into :new.lastmod_date, :new.lastmod_user
            from dual;
    end if;
end;
SHOW ERRORS;
ALTER TABLE PROTRAC_DETAIL ADD (
CONSTRAINT PROTRAC_DETAIL_PK
PRIMARY KEY
(PK_PROJ_DETAIL_ID)
    USING INDEX
    TABLESPACE DEVPROTRAC_DATA
    PCTFREE    10
    INITRANS   2
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                MINEXTENTS       1
                MAXEXTENTS       2147483645
                PCTINCREASE      0
ALTER TABLE PROTRAC_DETAIL ADD (
CONSTRAINT PROTRAC_DETAIL_NUM
FOREIGN KEY (FK_PROJ_MASTER_ID)
REFERENCES PROTRAC_MASTER (PK_PROJ_MASTER_ID));
ALTER TABLE DEVPROTRAC.RESOURCES ADD (
FOREIGN KEY (FK_DETAIL_ID)
REFERENCES DEVPROTRAC.PROTRAC_DETAIL (PK_PROJ_DETAIL_ID));
SET DEFINE OFF;
Insert into PROTRAC_DETAIL
   (PK_PROJ_DETAIL_ID, FK_PROJ_MASTER_ID, TRACKIT_NUMBER, DETAIL_DESCRIPTION, DETAIL_STATUS,
    DETAIL_STATUS_COMMENT, DATE_BEGIN, DATE_END, ESTIMATED_DATE, CREATEBY_DATE,
    CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, TASK_TITLE)
Values
   (34, 24, NULL, 'test', 'Queued',
    NULL, NULL, NULL, NULL, TO_DATE('10/30/2008 13:37:01', 'MM/DD/YYYY HH24:MI:SS'),
    'LREDMOND', TO_DATE('11/03/2008 15:19:35', 'MM/DD/YYYY HH24:MI:SS'), NULL, 'bananana');
Insert into PROTRAC_DETAIL
   (PK_PROJ_DETAIL_ID, FK_PROJ_MASTER_ID, TRACKIT_NUMBER, DETAIL_DESCRIPTION, DETAIL_STATUS,
    DETAIL_STATUS_COMMENT, DATE_BEGIN, DATE_END, ESTIMATED_DATE, CREATEBY_DATE,
    CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, TASK_TITLE)
Values
   (41, 40, NULL, '2354234', 'Queued',
    NULL, NULL, NULL, NULL, TO_DATE('10/31/2008 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
    'LREDMOND', TO_DATE('11/03/2008 13:52:02', 'MM/DD/YYYY HH24:MI:SS'), 'LREDMOND', 'I can type on the keyboarddf');
Insert into PROTRAC_DETAIL
   (PK_PROJ_DETAIL_ID, FK_PROJ_MASTER_ID, TRACKIT_NUMBER, DETAIL_DESCRIPTION, DETAIL_STATUS,
    DETAIL_STATUS_COMMENT, DATE_BEGIN, DATE_END, ESTIMATED_DATE, CREATEBY_DATE,
    CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, TASK_TITLE)
Values
   (49, 32, 78888, 'one day fishsticks will walk on the moon.', 'Queued',
    'waiting for fishsticks.', NULL, NULL, NULL, TO_DATE('11/03/2008 11:28:11', 'MM/DD/YYYY HH24:MI:SS'),
    'LREDMOND', NULL, NULL, 'Fix the keyboard');
Insert into PROTRAC_DETAIL
   (PK_PROJ_DETAIL_ID, FK_PROJ_MASTER_ID, TRACKIT_NUMBER, DETAIL_DESCRIPTION, DETAIL_STATUS,
    DETAIL_STATUS_COMMENT, DATE_BEGIN, DATE_END, ESTIMATED_DATE, CREATEBY_DATE,
    CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, TASK_TITLE)
Values
   (50, 38, NULL, 'dfdfdfdfdfdfdfdfdf', 'Queued',
    NULL, NULL, NULL, NULL, TO_DATE('11/03/2008 12:03:06', 'MM/DD/YYYY HH24:MI:SS'),
    'LREDMOND', TO_DATE('11/03/2008 15:19:44', 'MM/DD/YYYY HH24:MI:SS'), NULL, 'resreeeeeeeeee');
Insert into PROTRAC_DETAIL
   (PK_PROJ_DETAIL_ID, FK_PROJ_MASTER_ID, TRACKIT_NUMBER, DETAIL_DESCRIPTION, DETAIL_STATUS,
    DETAIL_STATUS_COMMENT, DATE_BEGIN, DATE_END, ESTIMATED_DATE, CREATEBY_DATE,
    CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, TASK_TITLE)
Values
   (33, 31, NULL, 'Make sure the bananas are fresh', 'Queued',
    NULL, NULL, NULL, NULL, TO_DATE('10/29/2008 00:00:00', 'MM/DD/YYYY HH24:MI:SS'),
    'LREDMOND', TO_DATE('11/03/2008 15:19:52', 'MM/DD/YYYY HH24:MI:SS'), NULL, 'e543563465');
Insert into PROTRAC_DETAIL
   (PK_PROJ_DETAIL_ID, FK_PROJ_MASTER_ID, TRACKIT_NUMBER, DETAIL_DESCRIPTION, DETAIL_STATUS,
    DETAIL_STATUS_COMMENT, DATE_BEGIN, DATE_END, ESTIMATED_DATE, CREATEBY_DATE,
    CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, TASK_TITLE)
Values
   (48, 37, NULL, 'guitar heros! yay', 'Queued',
    NULL, NULL, NULL, NULL, TO_DATE('11/03/2008 11:26:06', 'MM/DD/YYYY HH24:MI:SS'),
    'LREDMOND', TO_DATE('11/03/2008 15:19:57', 'MM/DD/YYYY HH24:MI:SS'), NULL, '34444444444444543etfg');
COMMIT;This is for the resources table:
ALTER TABLE RESOURCES
DROP PRIMARY KEY CASCADE;
DROP TABLE RESOURCES CASCADE CONSTRAINTS;
CREATE TABLE RESOURCES
PK_RESOURCES_ID   NUMBER,
FK_DETAIL_ID      NUMBER,
EMP_ID            NUMBER,
RESOURCE_STATUS   VARCHAR2(8 CHAR),
RESOURCE_COMMENT VARCHAR2(4000 CHAR),
CREATEBY_DATE     DATE,
CREATEBY_USER     VARCHAR2(50 CHAR),
LASTMOD_DATE      DATE,
LASTMOD_USER      VARCHAR2(50 CHAR),
FK_MASTER_ID      NUMBER
TABLESPACE DEVPROTRAC_DATA
PCTUSED    0
PCTFREE    10
INITRANS   1
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            MINEXTENTS       1
            MAXEXTENTS       2147483645
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
CREATE UNIQUE INDEX RESOURCES_PK ON RESOURCES
(PK_RESOURCES_ID)
TABLESPACE DEVPROTRAC_DATA
PCTFREE    10
INITRANS   2
MAXTRANS   255
STORAGE    (
            INITIAL          64K
            MINEXTENTS       1
            MAXEXTENTS       2147483645
            PCTINCREASE      0
            BUFFER_POOL      DEFAULT
CREATE OR REPLACE TRIGGER BUI_RESOURCES
before insert or update
on RESOURCES
referencing new as New old as Old
for each row
begin
    if inserting then
        select users_seq.nextval, sysdate, apex_application.g_user
            into :new.pk_resources_id, :new.createby_date, :new.createby_user
            from dual;
    elsif updating then
        select sysdate, apex_application.g_user
            into :new.lastmod_date, :new.lastmod_user
            from dual;
    end if;
end;
SHOW ERRORS;
ALTER TABLE RESOURCES ADD (
CONSTRAINT RESOURCES_PK
PRIMARY KEY
(PK_RESOURCES_ID)
    USING INDEX
    TABLESPACE DEVPROTRAC_DATA
    PCTFREE    10
    INITRANS   2
    MAXTRANS   255
    STORAGE    (
                INITIAL          64K
                MINEXTENTS       1
                MAXEXTENTS       2147483645
                PCTINCREASE      0
ALTER TABLE RESOURCES ADD (
FOREIGN KEY (FK_DETAIL_ID)
REFERENCES PROTRAC_DETAIL (PK_PROJ_DETAIL_ID),
FOREIGN KEY (FK_MASTER_ID)
REFERENCES PROTRAC_MASTER (PK_PROJ_MASTER_ID));
SET DEFINE OFF;
Insert into RESOURCES
   (PK_RESOURCES_ID, FK_DETAIL_ID, EMP_ID, RESOURCE_STATUS, RESOURCE_COMMENT,
    CREATEBY_DATE, CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, FK_MASTER_ID)
Values
   (53, 50, 356654, 'Active', NULL,
    TO_DATE('11/04/2008 09:32:06', 'MM/DD/YYYY HH24:MI:SS'), 'LREDMOND', NULL, NULL, NULL);
Insert into RESOURCES
   (PK_RESOURCES_ID, FK_DETAIL_ID, EMP_ID, RESOURCE_STATUS, RESOURCE_COMMENT,
    CREATEBY_DATE, CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, FK_MASTER_ID)
Values
   (51, 41, 447250, 'Active', 'No Sure.',
    TO_DATE('11/03/2008 14:23:11', 'MM/DD/YYYY HH24:MI:SS'), NULL, TO_DATE('11/04/2008 09:00:04', 'MM/DD/YYYY HH24:MI:SS'), NULL, 40);
Insert into RESOURCES
   (PK_RESOURCES_ID, FK_DETAIL_ID, EMP_ID, RESOURCE_STATUS, RESOURCE_COMMENT,
    CREATEBY_DATE, CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, FK_MASTER_ID)
Values
   (54, 50, 323829, 'Active', NULL,
    TO_DATE('11/04/2008 10:26:08', 'MM/DD/YYYY HH24:MI:SS'), 'LREDMOND', NULL, NULL, 38);
Insert into RESOURCES
   (PK_RESOURCES_ID, FK_DETAIL_ID, EMP_ID, RESOURCE_STATUS, RESOURCE_COMMENT,
    CREATEBY_DATE, CREATEBY_USER, LASTMOD_DATE, LASTMOD_USER, FK_MASTER_ID)
Values
   (52, 33, 8915, 'Active', 'get to work',
    TO_DATE('11/03/2008 15:20:18', 'MM/DD/YYYY HH24:MI:SS'), 'LREDMOND', TO_DATE('11/03/2008 15:35:10', 'MM/DD/YYYY HH24:MI:SS'), NULL, NULL);
COMMIT;The results I want is everything above regardless of emp_id assigned (if any). Without the r.emp_id = pps.emple_no join, the query will generate 234234239482304234 results.
Hope this helps.
Edited by: leland on Nov 4, 2008 12:56 PM

BOOLEAN DEFAULT FALSE NOT NULL for key-column

Hello,
These statements show an unexpected behavior when a column is added to a table as 'BOOLEAN DEFAULT FALSE NOT NULL' and added afterward to the table's primary key column set:
create table test_1 (a char(1))
insert into test_1 values('A')
alter table test_1 add b boolean default false not null
alter table test_1 add primary key (a,b)
create table test_2 (a char(1), b boolean default false not null)
insert into test_2 (a) values('A')
alter table test_2 add foreign key f_test_1 (a,b) references test_1 (a,b)
      -> [350]: Referential integrity violated
update test_1 set b=false
alter table test_2 add foreign key f_test_1 (a,b) references test_1 (a,b)
      -> success
delete from test_2
delete from test_1
insert into test_1 (a,b) values('A',false)
insert into test_2 (a) values('A')
      -> success
I think the error message '[350] Referential integrity violated' should not happen because the column 'b' really contains 'false'. But there obviously seem to be a difference before and after setting the column 'b' explicitly to 'false'. I can imagine that this depends on the way how the index for the primary key is updated. Probably the index is not properly updated in this context(?)
Gabriel

Hi Gabriel,
you're right, this is a bug and indeed seems to caused by the way the DEFAULT boolean is stored in the page.
(There is no separate index for the primary key in MaxDB as all data is stored in B*trees - basically the table is the primary key).
This is how the record looks like when column b is 'false' only due to the change of the DEFAULT value:
ROOT/LEAF 460 perm       entries : 1         [block 0]
     bottom : 93         filevers: 14888     convvers: 83
                                              writecnt: 1
1: (pos 00081)
00001      recLen      : 12                recKeyLen   : 4
00005      recVarcolOff: 0                 recVarcolCnt: 0
     record
      1 2 3 4 5 6 7 8 9 10 11 12
     81 82 83 84 85 86 87 88 89 90 91 92
dec: 12 0 4 0 0 0 0 0 32 65 0 0
hex: 0C 00 04 00 00 00 00 00 20 41 00 00
chr:                             A
And this is how it looks like after the explicit UPDATE:
ROOT/LEAF 460 perm       entries : 1         [block 0]
     bottom : 93         filevers: 14888     convvers: 84
                                              writecnt: 2
1: (pos 00081)
00001      recLen      : 11                recKeyLen   : 3
00005      recVarcolOff: 0                 recVarcolCnt: 0
     record
      1 2 3 4 5 6 7 8 9 10 11
     81 82 83 84 85 86 87 88 89 90 91
dec: 11 0 3 0 0 0 0 0 32 65 0
hex: 0B 00 03 00 00 00 00 00 20 41 00
chr:                             A
Little difference but this leads to the problems during the foreign key validation.
I'll inform the developers next week about this.
As a workaround you'll have to explicitly update the columns for which you change the default setting.
regards,
Lars

Oracle BPEL - Does not cater for not null columns and use of "default".

Oracle BPEL - Does not cater for not null columns and use of "default".
BPEL fails with message:
ORA-01400: cannot insert NULL into ("EDDB"."SEISMIC_LINES"."COORD_SYSTEM_ID")
But SQL*PLUS command works:
INSERT into EDDB.SEISMIC_LINES
(etc)
regards
Allan Ford
Analyst / Programmer - IT Application Services, IT Services, Shared Business Services
Santos Ltd
Level 4, 91 King William Street, Adelaide SA 5000
Phone: 08 8224 7944 Fax: 08 8218 5320
Email: [email protected]

note: BPEL keeps it's own "offline" copy of table and database items. A column that is marked not null in the database can be marked as nullable in this area. (if you kmow that a trigger is going to cater for this ..)
One workaround is to use a trigger to provide value rather than use the column default ..

MySQL using Is Null and Is Not Null

Hi
I am using mySQL and PHP to design a web site. On one of the
pages I want to able to display a list of records based on a date
field either having a date inputted or not having a date inputted.
I want the user to be able to select these options on the page via
a list box as below
Label Value
Open Is Null
Closed Is Not Null
However I can not seem to get this to work (sql below), is
the syntax correct and should it be a GET or POST variable eg
$_POST['ListBox']. Hope this makes sense.
SELECT *
FROM tbltable
WHERE datefield variable
Thanks

Change the order of your conditions
SELECT name,
       lname,
       CASE WHEN creditcard IS NULL AND credit_used IS NULL THEN
         'Sell both'
       WHEN creditcard IS NULL THEN
         'Sell Card'
       WHEN credit_used IS NULL THEN
         'Sell Credit'
       ELSE
         'No Action'
       END "Action"
FROM customers;

Not null validaton in tabular form --Apex3.2

Hi,
i am working with apex_3.2.
i am working on tabular form. I want to set validation on tabular form column , Column value cannot be null.How i can do this?
Thanks & Regards
Vedant.

Vedant wrote:
Hi,
Thanks it is working. i Need some more help regarding this. I have set the validation on add row button. If i keep the particular field empty on which i have set the validation , and click on add row button, it clear to the complete record. value should not be clear when click on the add row button it just show the massage, Field (Active_FLG) )cannot be empty.
Thanks & Regards
VedantI am not clear; when do you trigger the validation? On submit? If yes, then it will not retain your session state values. What is the relationship between the ADD_ROW button and the validation?
FYI, if you wish to retain session state values in the tabular form, you should be writing manual tabular form using collections. You will get good amount of information on manual tabular forms and collections in this forum and outside(google).
BTW, if your question is answered, do not forget to mark the appropriate post as correct. It will help all of us in the forum.

NULL IS NOT NULL filter issue

Can someone explain why 'Y' = 'N' is not working with PARALLEL Plan? i.e. With the filter like 'Y' = 'N' specified and if PQ is used , it does not return instantly. In fact it reads the entire table.
Here is the test case.. Goal is to execute only one of the SQL joined by union all. I have included 'Y' = 'N' in both SQLs for the test purpose.
DB Version is 10.2.0.4
Create table test_tbl_01 nologging as select do.* from dba_objects do , dba_objects d1 where rownum < 22000001;
Create table test_tbl_02 nologging as select do.* from dba_objects do , dba_objects d1 where rownum < 22000001;
execute DBMS_STATS.GATHER_TABLE_STATS('SCOTT', 'TEST_TBL_01');
execute DBMS_STATS.GATHER_TABLE_STATS('SCOTT', 'TEST_TBL_02');
*Serial path with 2 table join*
SQL> select
2    /* parallel(t1,2 ) parallel(t2,2) */
3    t1.*
4    from test_tbl_01 t1 ,test_tbl_02 t2
5    where t1.object_name = t2.object_name
6    and 'Y' = 'N'
7    and t1.object_type = 'TABLE'
8    union all
9    select
10    /* parallel(t1,2 ) parallel(t2,2) */
11    t1.*
12    from test_tbl_01 t1 ,test_tbl_02 t2
13    where t1.object_name = t2.object_name
14    and 'Y' = 'N'
15 /
no rows selected
Elapsed: 00:00:00.01
Execution Plan
Plan hash value: 3500703583
| Id | Operation            | Name        | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT     |             |     2 |   168 |       |     0   (0)|          |
|   1 | UNION-ALL           |             |       |       |       |            |          |
|* 2 |   FILTER             |             |       |       |       |            |          |
|* 3 |    HASH JOIN         |             |   660G|    50T|   449M| 6242K (99)| 24:16:38 |
|* 4 |     TABLE ACCESS FULL| TEST_TBL_01 | 5477K|   386M|       | 41261   (2)| 00:09:38 |
|   5 |     TABLE ACCESS FULL| TEST_TBL_02 |    22M|   212M|       | 40933   (2)| 00:09:34 |
|* 6 |   FILTER             |             |       |       |       |            |          |
|* 7 |    HASH JOIN         |             | 2640G|   201T|   467M|    24M(100)| 95:54:53 |
|   8 |     TABLE ACCESS FULL| TEST_TBL_02 |    22M|   212M|       | 40933   (2)| 00:09:34 |
|   9 |     TABLE ACCESS FULL| TEST_TBL_01 |    21M| 1546M|       | 41373   (3)| 00:09:40 |
Predicate Information (identified by operation id):
   2 - filter(NULL IS NOT NULL)
   3 - access("T1"."OBJECT_NAME"="T2"."OBJECT_NAME")
   4 - filter("T1"."OBJECT_TYPE"='TABLE')
   6 - filter(NULL IS NOT NULL)
   7 - access("T1"."OBJECT_NAME"="T2"."OBJECT_NAME")
Statistics
          1 recursive calls
          0 db block gets
          0 consistent gets
          0 physical reads
          0 redo size
        567 bytes sent via SQL*Net to client
        232 bytes received via SQL*Net from client
          1 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          0 rows processed
*Parallel path with 2 table join*
SQL> select
2    /*+ parallel(t1,2 ) parallel(t2,2) */
3    t1.*
4    from test_tbl_01 t1 ,test_tbl_02 t2
5    where t1.object_name = t2.object_name
6    and 'Y' = 'N'
7    and t1.object_type = 'TABLE'
8    union all
9    select
10    /*+ parallel(t1,2 ) parallel(t2,2) */
11    t1.*
12    from test_tbl_01 t1 ,test_tbl_02 t2
13    where t1.object_name = t2.object_name
14    and 'Y' = 'N'
15 /
no rows selected
Elapsed: 00:01:09.34
Execution Plan
Plan hash value: 1557722279
| Id | Operation                   | Name        | Rows | Bytes |TempSpc| Cost (%CPU)| Time     |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT            |             |     2 |   168 |       |     0   (0)|          |     |         |            |
|   1 | PX COORDINATOR             |             |       |       |       |            |          |     |         |            |
|   2 |   PX SEND QC (RANDOM)       | :TQ10004    |       |       |       |            |          | Q1,04 | P->S | QC (RAND) |
|   3 |    BUFFER SORT              |             |     2 |   168 |       |            |          | Q1,04 | PCWP |            |
|   4 |     UNION-ALL               |             |       |       |       |            |          | Q1,04 | PCWP |            |
|* 5 |      FILTER                 |             |       |       |       |            |          | Q1,04 | PCWC |            |
|* 6 |       HASH JOIN             |             |   660G|    50T|   224M| 3465K (99)| 13:28:42 | Q1,04 | PCWP |            |
|   7 |        PX JOIN FILTER CREATE| :BF0000     | 5477K|   386M|       | 22861   (2)| 00:05:21 | Q1,04 | PCWP |            |
|   8 |         PX RECEIVE          |             | 5477K|   386M|       | 22861   (2)| 00:05:21 | Q1,04 | PCWP |            |
|   9 |          PX SEND HASH       | :TQ10000    | 5477K|   386M|       | 22861   (2)| 00:05:21 | Q1,00 | P->P | HASH       |
| 10 |           PX BLOCK ITERATOR |             | 5477K|   386M|       | 22861   (2)| 00:05:21 | Q1,00 | PCWC |            |
|* 11 |            TABLE ACCESS FULL| TEST_TBL_01 | 5477K|   386M|       | 22861   (2)| 00:05:21 | Q1,00 | PCWP |            |
| 12 |        PX RECEIVE           |             |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,04 | PCWP |            |
| 13 |         PX SEND HASH        | :TQ10001    |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,01 | P->P | HASH       |
| 14 |          PX JOIN FILTER USE | :BF0000     |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,01 | PCWP |            |
| 15 |           PX BLOCK ITERATOR |             |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,01 | PCWC |            |
| 16 |            TABLE ACCESS FULL| TEST_TBL_02 |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,01 | PCWP |            |
|* 17 |      FILTER                 |             |       |       |       |            |          | Q1,04 | PCWC |            |
|* 18 |       HASH JOIN             |             | 2640G|   201T|   233M|    13M(100)| 53:15:52 | Q1,04 | PCWP |            |
| 19 |        PX RECEIVE           |             |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,04 | PCWP |            |
| 20 |         PX SEND HASH        | :TQ10002    |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,02 | P->P | HASH       |
| 21 |          PX BLOCK ITERATOR |             |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,02 | PCWC |            |
| 22 |           TABLE ACCESS FULL | TEST_TBL_02 |    22M|   212M|       | 22679   (1)| 00:05:18 | Q1,02 | PCWP |            |
| 23 |        PX RECEIVE           |             |    21M| 1546M|       | 22924   (2)| 00:05:21 | Q1,04 | PCWP |            |
| 24 |         PX SEND HASH        | :TQ10003    |    21M| 1546M|       | 22924   (2)| 00:05:21 | Q1,03 | P->P | HASH       |
| 25 |          PX BLOCK ITERATOR |             |    21M| 1546M|       | 22924   (2)| 00:05:21 | Q1,03 | PCWC |            |
| 26 |           TABLE ACCESS FULL | TEST_TBL_01 |    21M| 1546M|       | 22924   (2)| 00:05:21 | Q1,03 | PCWP |            |
Predicate Information (identified by operation id):
   5 - filter(NULL IS NOT NULL)
   6 - access("T1"."OBJECT_NAME"="T2"."OBJECT_NAME")
11 - filter("T1"."OBJECT_TYPE"='TABLE')
17 - filter(NULL IS NOT NULL)
18 - access("T1"."OBJECT_NAME"="T2"."OBJECT_NAME")
Statistics
       1617 recursive calls
          3 db block gets
     488929 consistent gets
     493407 physical reads
        636 redo size
        567 bytes sent via SQL*Net to client
        232 bytes received via SQL*Net from client
          1 SQL*Net roundtrips to/from client
          6 sorts (memory)
          0 sorts (disk)
          0 rows processedHowever single table with UNION ALL and PQ works..
*NO Joins (i.e. Single Table with PQ ) , Issue does not show-up.*
_*SERIAL PLAN with one Table*_
SQL> select
2    /* parallel(t1,2 )   */
3    t1.*
4    from test_tbl_01 t1
5    where 'Y' = 'N'
6    and t1.object_type = 'TABLE'
7    union all
8    select
9    /* parallel(t1,2 )   */
10    t1.*
11    from test_tbl_01 t1
12    where 'Y' = 'N'
13 /
no rows selected
Elapsed: 00:00:00.01
Execution Plan
Plan hash value: 2870519681
| Id | Operation           | Name        | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT    |             |     2 |   148 |     0   (0)|          |
|   1 | UNION-ALL          |             |       |       |            |          |
|* 2 |   FILTER            |             |       |       |            |          |
|* 3 |    TABLE ACCESS FULL| TEST_TBL_01 | 5477K|   386M| 41261   (2)| 00:09:38 |
|* 4 |   FILTER            |             |       |       |            |          |
|   5 |    TABLE ACCESS FULL| TEST_TBL_01 |    21M| 1546M| 41373   (3)| 00:09:40 |
Predicate Information (identified by operation id):
   2 - filter(NULL IS NOT NULL)
   3 - filter("T1"."OBJECT_TYPE"='TABLE')
   4 - filter(NULL IS NOT NULL)
Statistics
          0 recursive calls
          0 db block gets
          0 consistent gets
          0 physical reads
          0 redo size
        567 bytes sent via SQL*Net to client
        232 bytes received via SQL*Net from client
          1 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          0 rows processed
_*PARALLEL PLAN with one Table*_
SQL> select
2    /*+ parallel(t1,2 )      */
3    t1.*
4    from test_tbl_01 t1
5    where 'Y' = 'N'
6    and t1.object_type = 'TABLE'
7    union all
8    select
9    /*+ parallel(t1,2 )      */
10    t1.*
11    from test_tbl_01 t1
12    where 'Y' = 'N'
13 /
no rows selected
Elapsed: 00:00:00.09
Execution Plan
Plan hash value: 3114025180
| Id | Operation              | Name        | Rows | Bytes | Cost (%CPU)| Time     |    TQ |IN-OUT| PQ Distrib |
|   0 | SELECT STATEMENT       |             |     2 |   148 |     0   (0)|          |        |      |            |
|   1 | PX COORDINATOR        |             |       |       |            |          |        |      |            |
|   2 |   PX SEND QC (RANDOM) | :TQ10000    |       |       |            |          | Q1,00 | P->S | QC (RAND) |
|   3 |    UNION-ALL           |             |       |       |            |          | Q1,00 | PCWP |            |
|* 4 |     FILTER             |             |       |       |            |          | Q1,00 | PCWC |            |
|   5 |      PX BLOCK ITERATOR |             | 5477K|   386M| 22861   (2)| 00:05:21 | Q1,00 | PCWC |            |
|* 6 |       TABLE ACCESS FULL| TEST_TBL_01 | 5477K|   386M| 22861   (2)| 00:05:21 | Q1,00 | PCWP |            |
|* 7 |     FILTER             |             |       |       |            |          | Q1,00 | PCWC |            |
|   8 |      PX BLOCK ITERATOR |             |    21M| 1546M| 22924   (2)| 00:05:21 | Q1,00 | PCWC |            |
|   9 |       TABLE ACCESS FULL| TEST_TBL_01 |    21M| 1546M| 22924   (2)| 00:05:21 | Q1,00 | PCWP |            |
Predicate Information (identified by operation id):
   4 - filter(NULL IS NOT NULL)
   6 - filter("T1"."OBJECT_TYPE"='TABLE')
   7 - filter(NULL IS NOT NULL)
Statistics
         28 recursive calls
          3 db block gets
          7 consistent gets
          0 physical reads
        628 redo size
        567 bytes sent via SQL*Net to client
        232 bytes received via SQL*Net from client
          1 SQL*Net roundtrips to/from client
          2 sorts (memory)
          0 sorts (disk)
          0 rows processed

The same behvious appears in 11.1.0.6, and you don't need such a large data set to prove the point. The paralllel distribution may change to a broadcast with a smaller data set, but I demonstrated the effect when my two tables simply selected 30,000 rows each from all_objects.
I think you should pass this to Oracle Corp. as a bug - using the smaller data set.
The problem seems to be the way that Oracle combines multiple lines of a plan into groups of operations (as in PCWC, PCWC, PCWP). It looks like this particularly example has managed to fold the FILTER into a group in such a way that Oracle has lost track of the fact that it is a 'pre-emptng - i.e. always false' filter rather than an ordinary data filter; consequently the filter doesn't apply until after the hash join starts running.
In my example (which did a broadcast distribution) I could see that Oracle read the entire first table, then started to read the second table, but stopped after one row of the second table, because my plan allowed the join and filter to be applied immediately after the first row from the second table. And I think Oracle decided that the filter was alway going to be false at that moment - so stopped running the second tablescan. You've used a hash/hash distribriution, which has resulted in both scans completing because the slaves in each layer don't talk to each other.
Regards
Jonathan Lewis
http://jonathanlewis.wordpress.com
http://www.jlcomp.demon.co.uk
"Science is more than a body of knowledge; it is a way of thinking"
Carl Sagan

Regarding IF(IS NOT NULL) condition in Assignment

Similar Messages

Maybe you are looking for