Access Requests get Hanged all of a Sudden in AC 10.1 !!

[Former Member]

Hello All ,

I have configured below workflows in AC 10.1 for my client :

New User , Change User , Removal of access , Lock User , Unlock User

Requests are getting raised but they are not being routed to the Stages configured by me. And this has started happening suddenly.

Please suggest.

Regards,

Rahul Muni

[former_member197694 · Accepted solution]

Hello Rahul,

Some of the below points will helps you to resolve issue

check WF-BATCH user id

Check your BRF+ if any changes are happened

Check in SLG1 and GRFNMW_DBGMONTOR_WD may be for some additional information

check also in SWIA

Regards

Baithi

[Former Member · Accepted solution]

Hello Baithi ,

What to check for WF-BATCH user ??

Regards,

Rahul Muni

[former_member193066 · Accepted solution]

go to SM59

logical connection.

look for workflow_Local_client may be 100 200 xyz.

then test connection if its working?

if not, then go to SWu3 tcode and perform  activity will reset WF-BATH user.

still issue, then you have to perform task specific customization of workflow.

spro>GRC>general setting >workflow>perform task specific customizing.

regards,

Prasant

[Former Member · Accepted solution]

Hello Prasant,

You were RIGHT ... The Authorization test for RFC ' WORKFLOW_LOCAL_200 ' was getting failed.

I had to perform the activity in SWU3 again. This solved the problems related to WF-BATCH user.

Thank you for your valuable input.

Regards,

Rahul Muni

[Former Member]

Hi,

I think there is workflow delay in trigerring to next path.

Thanks

KH

[Former Member]

Hello Katrice,

My workflows used to work properly. I dont know what  happened due to which the request has stopped reaching to first stage of my configured path.

And the same is happening for other workflows also. The request gets created but does not go to the designed stages.

Please suggest.

Regards,

Rahul Muni

[Former Member]

Hey Rahul,

      There seems to be some problem with Agent Rule. Looks like it isn't able to determine the agent. For more information, can you please share SWIA logs?

Go to swia t code -> Enter the Request creation date -> and share the log corresponding to the request.

Thanks and Regards,

Fazil

[Former Member]

Hello All,

Thank you everyone for your valuable inputs.

The Authorization test for RFC ' WORKFLOW_LOCAL_200 ' was getting failed.

I had to perform the activity in SWU3 again. This solved the problems related to WF-BATCH user and RFC ' WORKFLOW_LOCAL_200 '.

Thank you for your valuable inputs..!

Regards,

Rahul Muni

[Former Member]

Hi Rahul,

Could you share more inf. on WORKFLOW_LOCAL_<Client>. eg. how is this RFC used.

also,i see that , the login id used is WF-BATCH.

Regards

plaban

[former_member193066]

Plaban,

This is logical workflow connection created automatically when you perform standard workflow configuration.

you can refer workflow help guide over sap help portal for more details.

this connection uses WF-BATCH USER.

and password is automatically saved.

Regards,

Prasant

[Former Member]

Hello Plaban,

The RFC ' WORKFLOW_LOCAL_200 ' gets created in GRC system automatically once you perform the activities in SWU3.

The Password for WF-BATCH maintained by you in SWU3 gets stored automatically in both RFC ' WORKFLOW_LOCAL_200 ' and SU01 of WF-BATCH.

Regards,

Rahul Muni