cancel
Showing results for 
Search instead for 
Did you mean: 

Error in MSMP Version Generation

Former Member
0 Kudos

Hi Experts,

Need your help and suggestions on the issue we are getting while trying to generate MSMP workflow with customization.

The error message we are getting is for a particuler stage - ZGRAC_AGENTS which is our first approval stage. Error message is -

Configuration ID ZGRAC_AGENTS check reported errors (BADI for task TS76308026 - class CL_GRAC_ACCESS_REQUEST_WF)

For other stages it is ok. We tried but couldn't find any difference between the different stages and Agent Rules. Any help on this error message is highly appreciated. Please help us out.

Thanks & Regards,

Sabita

View Entire Topic
Former Member
0 Kudos

Hi,

What type of Agent rule is it? ABAP Class based or BRFplus?

If it is ABAP Class based, you may need to implement the following SAP note (1672088 https://service.sap.com/sap/support/notes/1672088) to allow the MSMP functionality to recognise and use the custom agent correctly.

If you are on SP05-7, the note needs to be implemented manually.

Message was edited by: Kaushal Vastani

Former Member
0 Kudos

Hi Kaushal,

You forgot to include the note number

Regards,

Ajesh.

Former Member
0 Kudos

Hi Kaushal,

We are at SP07 and we are using BRF+ rules.

Regards,

Sabita

Former Member
0 Kudos

Editted

Former Member
0 Kudos

We have solved the issue, which was one configuration missing in task-specific settings. Now MSMP version is generated without errors. Now when I try to create and submit the request, I am getting below error -

Regards,

Sabita

Former Member
0 Kudos

Hi Sabita,

Re-check the initiator and the result rule set values mapping to the Paths.

Regards,

Ajesh.

Former Member
0 Kudos

Hi Ajesh,

I have checked it all once again but couldn't figure out what is missing.

My Initiator is based upon Employee Type and Request Type. To make it simple, I have done only few to test it first.

Initiator is -

If Employee Type is Business and Request is New Account then resultset is NEW_ACNT_BUS

If Employee type is Business and Request is Change Account then resultset

CHNG_ACNT_BUS

Similerly two for Support users.

In Global Rules - Process Initiator - I have given this initiator rule ID

For Path, I have created four paths for all four types of requests and in route mapping, I have given the resultsets of initiator with Path. MSMP workflow is generated successfully. The request number is also allocated to the request but in Instance status, it says error in line Items.

Can you suggest what I am missing here?

Regards,

Sabita

Former Member
0 Kudos

Hi Sabita,

Do the following and see if it works:

-Check if the initiator is activate in BRF+ (All nodes)

-Save and Re-generate the MSMP Process

-While submitting the Request check if all the mandatory fields are filled and Manager, approver information is maitained in the sources

Regards,

Ajesh.

Former Member
0 Kudos

Hi Ajesh,

It is still not working, giving the same error

Regards,

Sabita

pradeepmathewch
Employee
Employee
0 Kudos

Hi Sabita,

I'm getting the similar you faced at the beginning - activation error - (BADI for task TS76308026 - class CL_GRAC_ACCESS_REQUEST_WF).

Could you please let me know the workaround you did for this?

Thanks a lot in advance.

Warm Regards, Pradeep

Former Member
0 Kudos

Hi,

Just wondering if the Standard Task Agent  TS76308026 has been maintained via PFTC in the GRC system.

For more information on this, refer to the "Activate Common Workflow" section of the GRC Post Installation guide http://scn.sap.com/docs/DOC-1595.

pradeepmathewch
Employee
Employee
0 Kudos

Hi Kaushal,

Yes, It is maintained.

Can you please help here?

Thanks and Regards, Pradeep

Former Member
0 Kudos

Hi Pradeep,

Any chance of confirming that you have succesfully set up your system in accordance to the post installation guide attached above?

Have ALL the tasks been classified as "General"?

pradeepmathewch
Employee
Employee
0 Kudos

Yes Kaushal. Should I try a new agent rule?

Former Member
0 Kudos

If the workflows are functioning with no issues without a use of the problematic agent, it may be worthwhile recreating a new one. Keep the thread updated with your findings.

All the best.

pradeepmathewch
Employee
Employee
0 Kudos

I did. Same result

Former Member
0 Kudos

Is there any error reported within the Application Log (SLG1)?

Also, if you could giv e a brief description of exactly how you are trying to create your custom agent and assigning it into the workflow, that would be appreciated.

pradeepmathewch
Employee
Employee
0 Kudos

Hi,


Here we go...
Agent Id value zagent1 -> Agent Purpose value Approval -> Agent Type value GRC API Rules -> Agent Rule ID value guid Function ID used in creating the rule.
(I have entered users as Direct Value input.)
Then Go to Maintain Paths -> Selected a path -> I maintain only one stage ->  001 -> enter a stage conf id -> select the Agent Id previously created from F4 -> Approval type is anyone -> No Routing enabled and no escalation.
thats it.

In SLG1, I dont see any errors.

Thanks lot for your hep.

Warm Regards, Pradeep

Former Member
0 Kudos

Just a thought, do the directly mapped users exist on the GRC system? (i.e. in SU01?)

pradeepmathewch
Employee
Employee
0 Kudos

Yes Kaushal.