transaction_sys.Deferred_Call(job_id_, 'EPS_TECH_UTIL_API.UPDATE_ACTIVE_WORK_ORDER_BKUP','ATTRIBUTE', params_,'Update the Work Order',sysdate,'FALSE',2);
begin thewo:= client_sys.Get_Item_Value('wo_no_', params_);
INSERT INTO TEST2 VALUES ('wo_no_ '|| thewo); COMMIT; end;
What I am executing in the procedure is just for testing purposes, the finished procedure will look different. I don’t think the issue is the procedure the deferred call is calling, I think it is in the custom event the problem is. I have tried removing some of the parameters, renaming variables ,renaming the procedure, putting the procedure in a different package but nothing works.
I cannot make and deferred calls in custom events, I get this every time. Is there a limit on the number of times deferred call can be used in custom events?
I have lots of other custom events that use it and they all execute fine.
Best answer by EntNadeeL
I am getting this error on a custom event when I try to post a background job using a Deferred Call.
“Too many declarations of 'Deferred_Call' match this call”
transaction_sys.Deferred_Call(job_id_, 'EPS_TECH_UTIL_API.UPDATE_ACTIVE_WORK_ORDER_BKUP','ATTRIBUTE', params_,'Update the Work Order',sysdate,'FALSE',2);
begin thewo:= client_sys.Get_Item_Value('wo_no_', params_);
INSERT INTO TEST2 VALUES ('wo_no_ '|| thewo); COMMIT; end;
What I am executing in the procedure is just for testing purposes, the finished procedure will look different. I don’t think the issue is the procedure the deferred call is calling, I think it is in the custom event the problem is. I have tried removing some of the parameters, renaming variables ,renaming the procedure, putting the procedure in a different package but nothing works.
I cannot make and deferred calls in custom events, I get this every time. Is there a limit on the number of times deferred call can be used in custom events?
I have lots of other custom events that use it and they all execute fine.
Hi John,
You can follow below format in the event and it will post a background job everytime it triggers. It works like that.
transaction_sys.Deferred_Call(job_id_, 'EPS_TECH_UTIL_API.UPDATE_ACTIVE_WORK_ORDER_BKUP','ATTRIBUTE', params_,'Update the Work Order',sysdate,'FALSE',2);
begin thewo:= client_sys.Get_Item_Value('wo_no_', params_);
INSERT INTO TEST2 VALUES ('wo_no_ '|| thewo); COMMIT; end;
What I am executing in the procedure is just for testing purposes, the finished procedure will look different. I don’t think the issue is the procedure the deferred call is calling, I think it is in the custom event the problem is. I have tried removing some of the parameters, renaming variables ,renaming the procedure, putting the procedure in a different package but nothing works.
I cannot make and deferred calls in custom events, I get this every time. Is there a limit on the number of times deferred call can be used in custom events?
I have lots of other custom events that use it and they all execute fine.
Hi John,
You can follow below format in the event and it will post a background job everytime it triggers. It works like that.
transaction_sys.Deferred_Call(job_id_, 'EPS_TECH_UTIL_API.UPDATE_ACTIVE_WORK_ORDER_BKUP','ATTRIBUTE', params_,'Update the Work Order',sysdate,'FALSE',2);
begin thewo:= client_sys.Get_Item_Value('wo_no_', params_);
INSERT INTO TEST2 VALUES ('wo_no_ '|| thewo); COMMIT; end;
What I am executing in the procedure is just for testing purposes, the finished procedure will look different. I don’t think the issue is the procedure the deferred call is calling, I think it is in the custom event the problem is. I have tried removing some of the parameters, renaming variables ,renaming the procedure, putting the procedure in a different package but nothing works.
I cannot make and deferred calls in custom events, I get this every time. Is there a limit on the number of times deferred call can be used in custom events?
I have lots of other custom events that use it and they all execute fine.
Hi John,
You can follow below format in the event and it will post a background job everytime it triggers. It works like that.