I suggest you enable the dev tools link and install the IFS Cloud devtools web extension to be able to see the real error: (Link is for workflows but it is the same window you can see other things.)https://docs.ifs.com/techdocs/23r2/040_tailoring/500_business_process_automation/040_workflow_tooling/#how_to_enable_trace_details Here I have created a datasource with incorrect SQL and made a preview:
Not sure what it can be without more details.Do you have access and can check the table bpa_async_sys_tab? There the event action should create a record per execution.
Not sure why you want to add CustomerOrderLine, isn’t it a load of an external files of lines that shall be added to PreAccounting?Anyway, key between those PreAccounting and CustomerOrderLine is pre_accounting_id.company and contract are not keys in PreAccounting.
If the requirement is to always show the PO number from the CO at the time of first invoice creation. Maybe you can create a persistent field on customer order and save the value there with a workflow.Then you can use that field in the custom field for invoice.Reprint original is just showing the PDF connected to the record in the report archive so the original PO number is not re-fetched from any table in the database. So you can’t access it.
If you do not want to change the parameters you could use a PLSQL block to send into the deferred job in the event instead. Something like this: DECLARE attr_ VARCHAR2(32000); sql_msg_ VARCHAR2(32000); stmt_ VARCHAR2(32000);BEGIN stmt_ :='DECLARE shipment_id_ NUMBER; BEGIN MYPACKAGE_API.SFD_EV_SC_053(''&NEW:ORDER_NO'',''&NEW:LINE_NO'',''&NEW:REL_NO'',''&NEW:LINE_ITEM_NO'', shipment_id_); END;'; sql_msg_ := Message_SYS.Construct('CALL_SFD'); 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_); Transaction_SYS.Deferred_Call('Fnd_Event_Action_API.Action_Executeonlinesql', 'PARAMETER', attr_, Language_SYS.Translate_Constant('Event', 'DESCRIPTION: #SQL Treatment' ));END;
Change view from PURCHASE_ORDER_LINE_ALL to PURCHASE_ORDER_LINE.PURCHASE_ORDER_LINE_ALL is a join with PURCHASE_ORDER_TAB which you have triggered on and as Shehan says that will cause an error.
Looking at the package names in the error message, YVDMS_ etc., you have a German extension installed which most probably causes this.I have no more information than that.Maybe search for YVDMS in our internal sharepoint site “MyIFS” and you might find something?
I have not tested it but it “should” work to read from it in a Workflow.You can’t have any actions in those projections to change data. That has to be done by other projections, “normal” or STD entity.
You do not need to upgrade to 23R2 to get to 24R1.The reason why you do not see 24R1 is probably that it is not released yet, it will be 30th May 2024.I’m not sure if the impact assessment can be done earlier than that or not.
If you want to trigger a Workflow from background jobs. Have you set the timing to “Asynchronous”? Since that is the only one available in that scenario.
You could use Transaction_SYS.Log_Status_Info method to add information to the background job for trace purposes.Transaction_SYS.Log_Status_Info('<Enter your text here>', 'INFO'); The text you enter will be logged here, even if the background job fails:
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.