FF log not going to Controller_urgent help required

[Former Member]

Dear Experts

We are on GRC10 SP13 and struggling with FF log review workflow which is not getting triggered even after several attempts.

I have tested (below listed)most of the thing but not sure what is missing:

1.parameter 4007 and 4009 set to yes, back ground jon spm-sync_update running every hour successfully.

2, MSMP workflow for log review configured correctly with notification setting in place at stage level. Generated at Production box again.

3. Wf-Batch user and Controller have email ids as master data.

I am really not sure what else i can check, Kindly help.

regards

Asheesh

[alessandr0 · Accepted solution]

Hi Asheesh,

do you get anything in the SLG1 logs? Sync job runnig successfully? Also please share screenshot of your EAM configuration in SPRO.

Regards,

Alessandro

[Former Member · Accepted solution]

Thank you alessandro for quick responce,

SLG1 there is no error, everything looks fine

Also i have made sure that GRC and backend system are in same time zone. Automatioc workflow customization everything is green

Kind Regards

Asheeh

[alessandr0 · Accepted solution]

Can you set parameter 4018 to YES? This will provide more log information in SGL1.

All other settings seem to be correct and I am wondering. Do you have scheduled the program GRAC_SPM_LOG_SYNC_UPDATE frequently?

Regards,

Alessandro

[alessandr0 · Accepted solution]

sorry - 4018 comes with SP14. See OSS note here:

http://service.sap.com/sap/support/notes/1855037

[Former Member · Accepted solution]

SPM_Synch_update every 1 hour running without any issue. Manually all the data is on FF reports in reports and analytics

[alessandr0 · Accepted solution]

okay - please also check the following notes:

http://service.sap.com/sap/support/notes/1959891

http://service.sap.com/sap/support/notes/2060165

http://service.sap.com/sap/support/notes/1934127

Let us know.

Regards,

Alessandro

[Former Member · Accepted solution]

hello alessandro,

most of the notes are alreay in place. Strange thing is 2 months back things were working fine in Dev and QA and still working fine there . Its in production only after recently transport,

I have activated the MSMP workflow also on manually to make sure its generated.

Any other pointer?

kind Regards

Asheesh

[Former Member · Accepted solution]

Hello Alessandro,

would you suggest any thing else to be checked . We are struggling badly with this issue.

kind Regards

Asheesh

[Former Member]

Dear All,

I really appreciate a lot, all the help/suggestion you offered which help me in ensuring that there is no issue from configuration.

Finally I had to  raise a message with SAP where they confirm that its a product bug on GRC 10 SP13.

Reason for the issue was when you run EAM log sync job for multiple connection(same time or with overlapped period), GRC get confused with connector information(because the way code is written) and hence don't send workflow to controller.

Fix for the issue is implement note 2100872 and 2105088.

Workaround- schedule jobs after certain interval but if log data is big and jobs time overlap you get issue.

This issue was not caught by us in Dev or Quality as we were testing with only one connector.

Hope this help..

Kind Regards

Ashish

[former_member185447]

Hello Asheesh,

Thanks a lot and my thanks goes to other contributors also as I came to what all needs to be checked when we have a issue with logs in EAM.

Regards,

Deepak M

[former_member225180]

Hi,

- have you check if the E-Mail adress of the Owner / Controller in GRC and the target System is right? (SU01D)

- have you check if the users have follwin roles in both System (GUI SU01)

  * SAP_GRAC_SUPER_USER_MGMT_CNTLR, SAP_GRAC_SUPER_USER_MGMT_OWNER SAP_GRAC_USER_MGMT_USER

- Check Settings in SAP GRC UI: Set up -> Superuser Assignment -> Owners: There you have to assign a FF-User to an FF-Owner.

- Check Setting in SAP GRC UI: Set up -> Controller -> There you have to assign the FF-user to the Controller (Notify by Workflow).

- Run Repository sync Job and EAM Master data syn Job.

- Create new FF-request to use the existing Firefighter and approve.

- Then execute a Change in the backend System via fire fighter.

- Now run the reports to update the ff-log and E-Mail Generation by workflow

Hope this will help.

BR

Melanie

[former_member185447]

Hello Asheesh,

Did the issue got resolved? What was the solution?

Regards,

Deepak M

[Former Member]

Hi asheesh,

check SAPCONNECT job ..and also scot settings ..

Message was edited by: Kapil Kandula

[Former Member]

Dear Kapil

SaP connect job is working every 2 minutes.

What else i can check?

Kind Regards

Asheesh

[alessandr0]

Asheesh,

is there a workflow item visible in ARM? Go to Access Management tab > Search Request  and search for Firefighter Log Report requests. Are the workflows created? If yes, what says the audit log?

Regards,

Alessandro

[Former Member]

No Alessandro in serch request  and process id as FF log review there is nothing its empty.

Just for you infromation we have ARQ and FF id request workflow which are working without any issue.

its just the log review workflow which is not trigger for controller,

Kind Regards

Asheesh

[Former Member]

Asheesh,

Can you check email status in SOST ,and scot settings like mail server host name and port are maintained properly or not in addition check out address area

[Former Member]

Hello Kapil SOST and Scot setting are fine. All the email notification for access request and FF id request are working fine.

This issue looks more about workflow not triiggered for log review. Even if there is email issue notifcation should go to controller GRC work inbox , even which is not a case right now.

Kind Regards

Asheesh

[alessandr0]

can you show as the configuration of the firefighter? did you set the notification method to "Workflow"? Log display and Email is also applicable..

Also check if your workflow is properly activated in MSMP. Maybe activate again to check if errors occur.

Regards,

Alessandro

[Former Member]

Hello Alessandro why configuration u would like to see.Nitifcation for controllers is set to Workflow.

And MSMP workflow is again generated on production without any error

Kind Regards

Asheesh

[Former Member]

Hello Alessandro,

Just notied a dump in St22 for exception in CX_WDR_RT_EXCEPTION;

below is the method in which its breaking:

data:

     wa_view_controller type wdr_controller_line,

     l_view             type ref to cl_wdr_view,

     l_controller_info  type ref to if_wdr_rr_controller,

     l_view_man         type ref to cl_wdr_view_manager,

     l_existing_view    type ref to cl_wdr_view,

     ls_service         like line of if_wdr_service_target~registered_services.

   field-symbols: <view_controller> type wdr_controller_line.

   l_view ?= view_controller.

   wa_view_controller-name       = view_controller->name.

   if l_view->view_info->type = if_wdr_rr_view=>co_view.

     wa_view_controller-controller_type = wdyn_ctlr_type_view.

   elseif l_view->view_info->type = if_wdr_rr_view=>co_interface_view.

     wa_view_controller-controller_type = wdyn_ctlr_type_intf_view.

   elseif l_view->view_info->type = if_wdr_rr_view=>co_window.

     wa_view_controller-controller_type = wdyn_ctlr_type_window.

   else.

     raise exception type cx_wdr_rt_exception

         exporting

           textid = cx_wdr_rt_exception=>wrong_controller_type

           msgv1  = wa_view_controller-controller->name.

   endif.

   wa_view_controller-controller = view_controller.

   l_controller_info = me->component_info->get_controller( view_controller->name ).

   wa_view_controller-controller_type = l_controller_info->definition-controller_type.

   insert wa_view_controller into table me->if_wdr_context_manager~controllers[].

   if sy-subrc <> 0.

       raise exception type cx_wdr_rt_exception

               exporting

                 textid = cx_wdr_rt_exception=>view_already_existing

                 msgv1  = wa_view_controller-controller->name.

     endif.

[madhusap]

Hi Asheesh,

We faced similar issue recently in production. Literally everything is fine as mentioned by you. But finally the issue was because batch user WF-BATCH had some authorizations missing and this was the reason.

May be you can check your batch user authorizations as well.

Regards,

Madhu.

[Former Member]

Hi Asheesh,

Below are the few important things you need to check for the FF Log workflow to work properly.

1.Check  if the Collector job is running properly in your GRC box.

2.Check if the FF setup is done properly with right email id maintained for Controller in user master data.

3.Check if the system time-zone are same for both back-end and GRC system.

4.Standard  tasks and Workflow templates are  converted to general tasks and activated  for FF Log workflow.

5.Right Controller userid is maintained at the stage.

6.Check the initiator for the FF log is correct and the mapping for the workflows is done properly and generated.

7.FF sync job is running properly with the right program and required authorization.

8.Make sure the FF login is working.

9.All the Sync job and EAM Master data Sync job are running properly.

10.Fireifghter id has been assigned with the Controller in GRC box.

11.All the FF Parameters are configured properly specially Workflow parameter for FF Log Review value set to be Yes.

12.Check in SLG1  if there is any error or log for the Workflow.

Hope this helps.

Regards

Pradeep