Re-trigger EAM Logs to Controller

p_gray — Thu, 16 Mar 2023 03:33:21 GMT

Our WF-BATCH id was lacking enough security during which time 21 FF logs were created. Therefore emails did not get sent and now these logs are stuck at Path ID: Z_TI_LOG_REPORT_PATH. I have attempted to re-direct them back to Path ID, Z_TI_LOG_REPORT_PATH through the Administration button to trigger email, however, the Path ID is greyed out. Is there another way I can re-direct these logs back to Path ID, Z_TI_LOG_REPORT_PATH, so that email gets triggered to FF Controller and FF log is back on track with Path ID, in black?

Re: Re-trigger EAM Logs to Controller

stephanm2 — Thu, 16 Mar 2023 22:19:05 GMT

You can cancel all the workflow and just initiate them again using program GRAC_EAM_LOG_SYNC_TIMEBASED through SA38.

1. You can create new workflow (duplicates) and then cancel the old ones. (You can also simulate first to see if you get the right results)

2. The Timestamp is funny so make sure you enter your date in this format 20230216000000 and the system will change it to the below. (I usually save a variant to to remind me for future incidents) (1st 6 characters is date and the 2nd 6 is TIME)

3. You can also use this program to update the logs. Sometimes data didn't fill properly and you can execute the update logs to re-insert the FF log data.

Hope you come right.

topic Re: Re-trigger EAM Logs to Controller in Application Development and Automation Discussions

Re-trigger EAM Logs to Controller

Re: Re-trigger EAM Logs to Controller