This content has been marked as final. Show 6 replies
I called a procedure in in-insert and on-updateWhy are you writing this code in the first place? If you have a block based on an updatable view, just let Forms do the inserts and updates.
If it's not an updatable view, use instead of triggers on the view.
See this current thread too:
INSTEAD of Trigger View for an Oracle EBS New form development
By over-riding the ON-INSERT and ON-UPDATE , I cut-and-paste my INSERT and delete statements into ON-INSERT and ON-UPDATE trigger at the block level. This effectively over-rides the insert which forms would have fired.
Also by using on-lock trigger at block level avoids the form from locking the table which now allows to do multiple update.
I m not sure whether this is correct way to do it?Wil try using instead of trigger also.
I m not sure whether this is correct way to do it?There is never (or hardly ever) a correct way of doing something. It depends on the situation, your company's guide lines etc.
IMHO it is not a good idea to perform SQL in a Forms procedure. At least put it in a database procedure and call this procedure from your form.
It also looks to me that is a form for the eBusiness Suite, right? In that case you'd better ask advice in the EBS forum. EBS provides API's for the tables.