topic Re: MSMP workflow generation issue in Application Development and Automation Discussions

MSMP workflow generation issue

former_member699572 — Tue, 15 Dec 2020 13:11:36 GMT

We are unable to generate MSMP workflow after adding a new custom function module (FM) ZGRAC_NOTIF_VAR_WF_COMMENTS in global rules. Its throwing an error- “Error in Process Global Settings” This new FM is an exact copy of standard FM - GRAC_NOTIF_VAR_RULE_AR and we are just adding new custom variable in it.

Can somone help us to identify the exact issue?

Re: MSMP workflow generation issue

Colleen — Thu, 17 Dec 2020 00:47:00 GMT

HI Disha

I've found when adding the customer rules you need to save in 2 steps

1. Add it as a rules then save and refresh MSMP webdynpro

2. Change the global notification setting over to the new rule and save again

Does doing that help?

Have you checked the custom function module has been activated?

If still an issue, then screen shots of what you are doing and the error message would help

Re: MSMP workflow generation issue

former_member699572 — Mon, 21 Dec 2020 08:28:00 GMT

Hello Colleen,

Thenk you so much for your help. Above steps worked. I am able to add FM and activate the workflow successfully 🙂

But it says 'No changes were found for the process. No version Generated.'

Re: MSMP workflow generation issue

former_member699572 — Mon, 28 Dec 2020 15:12:14 GMT

Hello Colleen,

I got the solution for workflow generation issue. The issue is resolved after forcefully generating MSMP version from R3 backend system.

Can you please help me with below query?

I have added the customer rules using 2 steps and captured the changes in Transport request (TR).
So, when I will move TR in Quality system, I must save and generate version in quality. Will I get the same error while generating a version in Quality system?

Plese confirm.

Regards,
Disha Sarmalkar

Re: MSMP workflow generation issue

Colleen — Wed, 24 Feb 2021 06:36:51 GMT

sorry - didn't realised you had replied.... probably figured out by now

When you transport to QA you do not need to save it again. You would use transaction code GRFNMW_GEN_VERSION to generate the version after the transport (and you have completed a visual check that it looks right).