PDF_REPORT_CREATED - (Purchase Order) Event Action Randomly Get Failed

Can you please show us the event action code you’re using for the PDF_REPORT_CREATED, for either a filter on all report IDs or specifically on PURCHASE_ORDER_PRINT_REP, inside this screen:

If you’re calling a PLSQL Package in there, including a custom one, and if you’re regularly recompiling it, you can get this error (which would actually be the first stack message from the “existing state of packages has been discarded” error, every time you call this package for the first time after recompilation.

If that is the case, don’t forget you can just call the Init Procedure of the package after recompiling it to make sure to revalidate its state.

@SimonTestard  Thank you for the information.

I'm using following event action, which is basic configurations. (Action Type - “E-Mail”) Above error occurs randomly.

Hi @Lochana95 ,

Your event action page shoul be similar like below;

First check your report title it should be like PURCHASE_ORDER_REP,

or if you use layout name there should be .rdl at the end of title.

Second you should configure a mail sender with using ‘Setup IFS Connect’ page.

Hope it helps.

Kind Regards

Özgün Bal

@SimonTestard  Thank you for the information.

I'm using following event action, which is basic configurations. (Action Type - “E-Mail”) Above error occurs randomly.

 

Can you please provide the FULL error message you can see in the Print Manager, is there any text to the right that you haven’t shown in your first screenshot, specifically after “being called”, i.e. does it tell you which program unit was not found ? Quite important to debug this :)

And obviously make sure you specify the mail sender just in case, although I don’t think that’s the problem as you’re saying it’s sometimes working and sometimes not, for the same PO, and the event action itself doesn’t change between those times

@SimonTestard @Ozgun BAL Thank for the repones.

Unfortunately the error message only shows up to “being called” no further text after that. (I have exported the lines to an excel and checked as well)

“ORA-20105: FndEventAction.EVENT_ACTION_ERROR: The Event Action "E-Mail" on "PDF_REPORT_CREATED" has failed. Please contact your System Administrator to manage the Event Actions. ORA-06508: PL/SQL: could not find program unit being called"

I have tried with specifying mail_sender as well but it keeps failing randomly, and yes the event action is not changed.

Further I tried with SQL code as event action and writing the PLSQL inside begin and end block still it keeps failing randomly (added a exception block as well and still error shows up to “being called”)

 

How replicable is this? Can you get it to fail fairly “easily” ?

If so, can you try recompiling fnd_event_action_api and see if the error keeps happening after you’ve done that ?  (Don’t forget after you recompile you can run the Init procedure to make sure the package state is revalidated)

If you’re willing to some SQL Code stuff there might some debug options you can do, but the fact you’ve changed it to SQL code and it keeps doing it seems to indicate to me that the trigger is failing before the actual business logic is executed behind the scenes

Basically, your print triggers an insert, to the archive, the insert calls up the event, the event action fails, so the print does too. That means I don’t necessarily think it’s the fact you’re trying to send an email that fails, it might be an issue further up the chain

Also, @Lochana95 , can you try enabling Server Log for Events

And see if you get any entries in SERVER_LOG when that happens?

@SimonTestard Thank you for the information. As you mentioned I suspect the same that something is wrong in print agent server or somewhere along the line. I will check further after enable server log as you suggested.