@haritha.waidyaratne are there any calculated custom attributes that have been included in the layout of PURCHASE_ORDER_PRINT_REP?
I’m thinking that if there are many calculated custom attributes, maybe some of them are not very efficient and it takes a long time for the PURCHASE_ORDER_PRINT_RPI to insert the data in the RPT table and create the XML.
Thanks for posting a lot of helpful answers but they have finally got back saying that the problem vanished after restarting the application server, in the aftermath of applying certain patches.
For our future reference, the error was traced to its origins, like this:
In the foundation (fndbas) client file PrintDialog.client, this error is raised after the invocation of the method
ReportDirectPrintRequest() which resides in the projection PrintDialog. Report_Format_Request() called from there in that svc, will land a call on Report_SYS.Request_Formatting_Async().
Pdf_Archive_API.Get_Id() invoked at the end of the method, fails to fetch a value, resulting in the error.
It is reliably learnt that in certain instances the process may not wait till an entry in the pdf archive is created - which is made to happen asynchronously in consideration of other metrics that determine server loads, etc.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.