Event Action on Project Create Invoice

​@Barth  The problem is that your event is incorrect. As you want to run it in the background using a stmt_ you will have to make sure you did not make a mistake in your event. 

99% of the time its due to wrongly escaping a string or variable (as you have to build up your statement as a string you have to make sure you correctly use the accents in your code so the system tries to run the transaction, it hits your custom event and it fails because there is an error in your event. 

Could you paste your full event here? otherewise just strip it to the bare minimum and then work your way back adding piece by piece to see when it fails and on which line. 

easiest is to open it in a vs code editor and check the formatting that could give you an idea.

 

Thank you for the quick feedback.

There is another test.

The code in the event action : 

DECLARE
    ATTR_         	VARCHAR2(32000);
    SQL_MSG_      	VARCHAR2(32000);
    STMT_         	VARCHAR2(32000);
    JOB_ID_       	NUMBER;
    ERROR_TEXT_   	VARCHAR2(2000);
	count_        	NUMBER;
	vCompany 		VARCHAR2(100) := '&NEW:COMPANY';
	vIdentity 		VARCHAR2(100) := '&NEW:IDENTITY';
	vProjecId 		VARCHAR2(100) := '&NEW:PROJECT_ID';
	vInvoiceId 		VARCHAR2(100) := '&NEW:INVOICE_ID';
BEGIN

	STMT_ := 'General_SYS.Init_Method(''CUSTOMEVENT'', ''INVOICE_TAB'', ''AQ_PROJECT_INVOICE_TXTFACT '');';

	SQL_MSG_ := MESSAGE_SYS.CONSTRUCT('UPD');
	MESSAGE_SYS.ADD_ATTRIBUTE(SQL_MSG_,'SQL',STMT_);
	CLIENT_SYS.CLEAR_ATTR(ATTR_);
	CLIENT_SYS.ADD_TO_ATTR('SQL_DATA_',SQL_MSG_,ATTR_);
	CLIENT_SYS.ADD_TO_ATTR('MSG_','',ATTR_);

	-- Déclenchement post-commit dans une queue rapide
	TRANSACTION_SYS.DEFERRED_CALL(
	 id_                        => job_id_,
	 procedure_name_            => 'Fnd_Event_Action_API.Action_Executeonlinesql',
	 argument_type_db_          => 'PARAMETER',
	 arguments_                 => attr_,
	 description_               => 'AQ_PROJECT_INVOICE_TXTFACT',
	 posted_date_               => SYSDATE,      
	 lang_indep_                => 'TRUE',       
	 queue_id_                  => 20,          
	 total_work_                => NULL,
	 stream_msg_on_completion_  => 'FALSE',
	 stream_notes_              => NULL
	);

END;

The return :

Here is another exemple more explicit : 

DECLARE
    ATTR_             VARCHAR2(32000);
    SQL_MSG_          VARCHAR2(32000);
    STMT_             VARCHAR2(32000);
    JOB_ID_           NUMBER;
    ERROR_TEXT_       VARCHAR2(2000);
    count_            NUMBER;
    vCompany         VARCHAR2(100) := '&NEW:COMPANY';
    vIdentity         VARCHAR2(100) := '&NEW:IDENTITY';
    vProjecId         VARCHAR2(100) := '&NEW:PROJECT_ID';
    vInvoiceId         VARCHAR2(100) := '&NEW:INVOICE_ID';
BEGIN
    
    RAISE_APPLICATION_ERROR(-20001, 'Problem');

END;

The raise should be launch on the previous window, not show as a recap on an error field in a table.

​@Barth the project invoice creation process is quite different compared to other invoice type creation process. I don’t understand what is your issue here. You would expect to get the error when you click Finish? I’m afraid this is not possible for project invoice.

That's exactly what I'm trying to do.

If this is not possible, what would be the solution for executing an SQL statement after the action?

Even if it takes some time.

The RAISE_APPLICATION_ERROR function is only there to illustrate my point of view on this system; I do not need to display a message during my actual action.

I want to update PROJECT_INVOICE with PROJECT_INVOICE_API.MODIFY__.

​@Barth I have such an event created that runs a bckg job when project invoice is created.

I leave below the details. Maybe it’s helpful:

DECLARE
   attr_ VARCHAR2(3200);
   event_id_   VARCHAR2(8000) := 'C_UPD_PRJ_INV_BKJ';
   lu_name_    VARCHAR2(8000) := 'FndEvent';
   event_msg_  VARCHAR2(8000);

BEGIN
   event_msg_ := Message_sys.Construct('C_INV_PLAN_DATE');
   Message_sys.Add_Attribute(event_msg_, 'INVOICE_ID', '&NEW:INVOICE_ID');
   Message_sys.Add_Attribute(event_msg_, 'COMPANY', '&NEW:COMPANY');
   client_sys.Clear_Attr(attr_);
   Client_SYS.Add_To_Attr('EVENT_DATA_', event_msg_, attr_);
   Client_SYS.Add_To_Attr('EVENT_ID_', event_id_, attr_);
   Client_SYS.Add_To_Attr('EVENT_LU_NAME_', lu_name_, attr_);
   attr_ := Replace(attr_, chr(31) || chr(31), chr(31));

Transaction_Sys.Deferred_Call('Event_sys.Event_Execute','PARAMETER', attr_, 'Event C_UPD_PRJ_INV_DATE: Update invoice dates');

END;

I'm going to test this method and I'll come back to give feedback on how it works.

Could you share a part of the code of C_UPD_PRJ_INV_BKJ, just to see how you pass the attribute to the BKJ event please ?

Also could you explain me what the goal of this line :

event_msg_ := Message_sys.Construct('C_INV_PLAN_DATE');

What is C_INV_PLAN_DATE ? Just the name of the message ?

and just for my knoledge why did you replace part of attribut here : 

attr_ := Replace(attr_, chr(31) || chr(31), chr(31));

Thanks

Honestly, thank you, it works perfectly. 
It's still very complex to do very little, but at least it takes a weight off my mind.

I owe you a beer ! 😁