PaPM function doesn't get deployed at first, and only works after reloading the browser.

[LeonardoGarcia2]

Hello Experts! I've been trying to find the solution to this problematic, and I would really appreciate any help that can be provided.

When executing PAPM transactions, they are successfully carried out, but the window does not automatically display. However, the action is indeed performed, and this issue occurs with all transactions. Then after reloading the browser where the query is made, upon executing the function again, the table appears, without any changes to the configuration. The issue is that reloading does not always work on the first attempt, which is bothersome and delays the process.

It is important to note that this issue does not occur in the quality environment, which has the same configuration as the production environment. There, the tables display correctly on the first attempt without the need to reload the browser (whether it's Chrome, Firefox, Edge, etc.). We've reviewed the entire Post-Installation Steps as per SAP request, and everything has been done according to the documentation.

[Kevin_Topino · Accepted solution]

Hello Leonardo,

I understand that you are encountering this issue when executing PaPM transactions. To fix the issue, kindly follow the steps below:

1. Transaction SICF: Please make sure that node WDR_APC is activated
2. Web Dynpro application WD_GLOBAL_SETTING: Please make sure that the parameter WDNOTIFICATIONSERVICE is set to value PUSH. You can use this parameter also as URL Parameter.
3. SAP Note 2748620 - Requirements for Notification Service through WebSocket communication protocol

If still does not work, incident can be created and assign to Webdynpro component BC-WD-ABA-RUN.

Hope this helps!

Best regards,
Kevin