Help Workflow to Production - Customazing request

[glauco]

Frinds,

I learned wrong about how to transport the workflow to quality and production. I thought that I had to configurate Agent assignme and triggering event in Quality and Production. But I was wrong, and in reality I have to create a Customazing request type.

But now I'm trying to change the workflow so can I appoint a (customazing) request to this (Agent assignme and triggering event), but the workflow only ask me to new workbanch request.

Does anybody know a way to solve my problem?

Message was edited by: Glauco Kubrusly

Message was edited by: Glauco Kubrusly

[Jocelyn_Dart]

Hi Glauco,

Yes if you change the workflow itself, that is a workbench request.

If you want to transport the event linkage, you can change the event linkage only in transaction SWE2 or SWETYPV and that will give you a customizing request.

Agent assignment is slightly more tricky as there are two ways to handle agent assignment:

1. Agent assignment is like master data or security profiles and maintained separately in each client/system

2. Agent assignment is configuration and transported through.

If you want the second option, then you need to use the HR transport programs which allow moving of HR relationships (and agent assignment is technically an HR relationship - even if you don't have HR). These are programs such as RHMOVE30 and RHMOVE50. You can use these programs to generate the necessary transport requests. Here you can transport Task (TS) to agent (S, P, US, AG, etc.) relationships, and even the general task relationship (infotype 1217).

Don't be concerned if you think "but we don't have HR" - the workflow-related part of HR is considered part of the SAP Basis/WebAs system.

Regards,

Jocelyn

[Former Member]

Hello Glauco

In my (limited) experience, SAP automatically assigns each change you make (to any application, not just workflow) to either a workbench or customizing request; you don't need to select which. For configuring the triggering event, I think you can simply change the entry, assign it to a new transport request (whichever SAP assigns), change the entry back to what it was or what you need it to be, and then transport the request to QA or production. This should make the necessary change in those systems as far as triggering events.

As for agent assignment, I've been having a similar problem myself. I find that in certain cases, agent assignment lists are not transportable from system to sytem or from client to client. Thus, I've had to configure agent assignment manually for every client/system I'm working on. Strangely, sometimes a transport does occur, I'm not sure why. For now, configuring the agent list manually should take care of the issue. If you don't have access to QA or production, talk to a functional with whom you can work together.

Hope this solves your problems.

Greetings

Juan Ramos