Agent USER does not exist in development server

[Former Member]

Hi guys,

In Mail step of my Workflow I want to use the Recipient type 'User', but user which I want does not exist in the development server, and is available in our test and production server.

Is there any way to handle this situation of assigning agents which does not exist in development environment.

thanks and advance.

regards,

Ishtiyaq

[Former Member]

Hi,

This can be handle in may ways...

1. Rule with resposibility

Please define a custom rule with responsibilities which will always return your test user.

And use this rule in your dialog step. As a rusult of that your test user will get tht task.

Note : user can added to responsibility through transaction OOCU_RESP in any environment.

2. Rule with Function Module.

Please define a custom rule with custom Function Module which will always return your test user.

And use this rule in your dialog step. As a rusult of that your test user will get tht task.

Logic is your test user will be maintained in a configurable table and FM will feche this user from this table.

Please refer below link for more details.

http://www.genipole.com/tutorials/creating-custom-rule-using-function-module-in-sap-workflow/

Thanks and regards,

SNJY

[Former Member]

Dear Sanju,

thank you very much for your quick reply.

I agree with both the ways you mentioned . Here in my case I don't want to maintain the user in any table, bcoz

the user I want to send mail exists in Quality and Production System. But the only issue is his id is not created in

development server.

One way would be, basis create the same user as production in development system. So that i can put his name

in my mail step and save the workflow. But issue is basis don't want to create the user in Development.

Hope anybody have some solution for this issue.

thanks.

Ishtiyaq

[Former Member]

Hi,

In that case it is impossible in DEV environment as per my knoledge.

This is like you are transfering money to an account but the account does not exists.

Please let me know if you found any solution.

Thanks and regards,

SNJY

[Former Member]

Hi,

In that case this is impossible as per my knowledge.

Please let me know if you found any solution.

Thanks and regards,

SNJY

[former_member185167]

Hello,

Does this mean that you have a username hardcoded into your workflow? That is a very poor design.

You want to have to do a transport every time that user is replaced or changes positions?

At the very least create a responsibility rule and put the user there.

Why is it a problem to create a userid in a DEV system anyway?

regards

Rick Bakker

hanabi technology

[Former Member]

thanks guys for your valuable suggesions.

As suggested will create a table and fetch the agents through rule.

regards.

Ishtiyaq.

[Eddie_Morris]

Hi,

If this is a sendmail step then yuo cannot use a rule so I would recommend a position or expression to hold the user ID. As Rick mentioned do not specify a user ID in the sendmail step directly as this will be a maintainence nightmare.

Regards,

Eddie

[Former Member]

thanks sangu .

[former_member185167]

Hello,

"As suggested will create a table and fetch the agents through rule."

Please do not create a table! SAP already has too many. Just create a responsibility rule and then create a step which calls a task which calls a method that accesses that rule using fm RH_GET_ACTORS. Put the result in a container element and you can use that in a SendMail step.

regards

Rick Bakker

hanabi technology