Trigger not changing a null value to -1 on insert, but works on update?

Question

Here is the trigger I am working on.
If i update a row it will update the org_type_id to -1. However, nightly a job runs to append new data to the table. I can't change the fact that every day a few "deleted org"'s have a org_type_id as null.
So, this trigger was supposed to solve it, but it ONLY works if a row is updated, it doesn't work on inserted new rows.
Thoughts?
CREATE OR REPLACE TRIGGER MDMR.MDM_ORG_TYPE_ID
BEFORE INSERT OR UPDATE
ON MDMR.MDM_ORG
FOR EACH ROW
declare
begin
if (UPDATING) then
if ((:old.org_name = 'Deleted Org') and (nvl(:old.org_type_id,0) = 0)) then
:new.org_type_id := -1;
end if;
end if;
if (INSERTING) then
DBMS_OUTPUT.put_line ('INSERTING1');
if ((:new.org_name = 'Deleted Org') and (nvl(:new.org_type_id,0) = 0)) then
DBMS_OUTPUT.put_line ('INSERTING2');
:new.org_type_id := -1;
end if;
end if;
end;
/

Answer 1

Hi,
It looks fine to me (or, rather, it would look fine if it were formatted), but I can't test it without your table.
Whenever you have a problem, post a little sample data (CREATE TABLE and INSERT statements), and the results you want from that data. In the case of DML problems (like this), the results are the contents of the changed table after each DML operation.
Are you sure that 'Deleted Org' is spelled exactly the same in the trigger and in your INSERT statements? That includes capital letters and trailing spaces, including those automatically supplied for CHAR columns.
Does it work when you test it, but fail during the nightly job?