Why don't you just demonstrate the supposed problem?
It took me all of 2 minutes to do this, and most of that was a setup that you won't need to do:
SQL> create table mytest (ob_max number(3));
SQL> insert into mytest values (12);
1 row created.
SQL> select * from mytest;
Really, just go to sqlplus, insert the data you claim can't be inserted. copy the entire session and paste it back here.
BTW, it would be really helpful if you would go to your profile and give yourself a recognizable name. It doesn't have to be your real name, just something that looks like a real name. Who says my name is really Ed Stevens? But at least when people see that on a message they have a recognizable identity. Unlike the system generated name of 'ed0f625b-6857-4956-9b66-da280b7cf3a2', which is like going to the pub with a bag over your head.
And now read the error message and understand it...
I give you a hint
ora:12899: value too large for column 'premier'. 'p_pm_property'. "property_id"
Unfortunatly, this would not fully explain, why you get no error message in you original problem.
It might be, that there is some additional layer, that hides the oracle exception from you. That is why it is so important, to tell about missing bits and to test it using sql*plus.
Do you get another error message when using a fitting property_id?
insert into p_pm_property (property_id, overbook_max_percent) values ('tst123', '123');
I still expect an error message coming from the trigger.
AWWW I did a mistake when i test it
insert into p_pm_property (property_id, overbook_max_percent)
values ('tes', '123');
and got this error
ora-06502 pl/sql:numeric or value error: number precision too large
ora-06512: at "premier.inf_p_pm_property _tgr" line 99
ora-04088: error during execution of trigger 'premier.inf_p_pm_propery_tgr'
Good! Now we are talking.
Here is the reason. The important parts of the trigger are those:
CREATE OR REPLACE TRIGGER PREMIER.INF_P_PM_PROPERTY_TGR BEFORE DELETE OR INSERT OR UPDATE ON PREMIER.P_PM_PROPERTY
REFERENCING NEW AS NEW OLD AS OLD FOR EACH ROW
vUser p_personnel.username%type := sec_pkg.get_username;
IF INSERTING OR UPDATING THEN
v_inf_rec.overbook_max_percent := :NEW.overbook_max_percent;
INSERT INTO inf_P_PM_PROPERTY VALUES v_inf_rec;
You need to increase the column overbook_max_percent in table inf_p_pm_property from 2 to 3.
The datatype of the variable v_inf_rec is inherited from the target table (inf..) and it is number(2) for the overbook_max_percent column.
At the moment where you try to fit the 123 into the number(2) variable, you get the "number precision too large" error message
but inf_p_pm_property is NOT a table is a trigger.
select object_name, object_type from user_objects where upper(object_name) like '%P_PM_PROPERTY%';
This will show all tables, triggers and other stuff that you have with names similiar to p_pm_property.
Post the output here.