Workflow works in QA but not working in production

[former_member202733]

Hi guys, how are you?

I'm faccing a problem with a workflow, it is a simple work flow, that is triggered when a entry sheet is created, there is a background step that executes a method in a ZBUS this BUS returns a value for a Rule that determine which agent can release the entry sheet and after the agente release the entry, a work iten is created to notify the workflow starter that the entry is released. Everything works fine in QAS, but not in production system. In production system, when a user creates a entry sheet, the event is triggered and stars the workflow, but, in my background step nothing happens, no value is setted to the container variable and since the next task is a general task, and no agent could be determinated, a lot of users receive this request.

I compare all objects in both systens and I cannot see any diffences between then.

In production system, I run SWIA transaction to see the container variables or check for erors, there is no errors but my container variable is not setted.

If I execute my ZBUS method in production system, it works fine and also the rule that determine the agent works fine.

I checked all steps, all tasks, all bindings, and everything is identical in QA and production.

For the first step, looking in both systems the container variables.

Now, let's look the workflow log for this step, the thecnical data. As you can see in both cases there is no error.

And finally, when I check for the selected agents, as you can see, in QAS, select only one, but in PRD all agents.

I am really desperate and this workflow is driving me crazy!

I don't know what is going on, and I don't know anything I could check.

Could somebody plese help me?

I appreciate any help.

best regards

Ronaldo S. Vieira

[DoanManhQuynh]

I got the same problem recently and it turned out the agent assignment somehow not activated in PRD. sometimes the workflow behavior quite strange and i just can say you should try on workflow buffer, or re-active the agent assignment...

[former_member202733]

Thanks quynh.doanmanh but when you say turn out agent assignment what do you mean?

best regards

Ronald S. Vieira

[DoanManhQuynh]

in my case, the agent assignment of user decision task are active (green) in QAS but in PRD is grey out (mean not active). in my case I just go to task's attributes screen and click transfer.

[bpawanchand]

Hi,

I think you should first try to understand why this one container element is not getting populated in the prod system.

After looking at the workflow graphical log I felt it is a background method which is determining the container element and passing it back to the workflow container.

1. I would first try to debug this method from SWO1 transaction bypassing all the inputs which are passed from workflow container to method. If and only if it is not updating or changing the status of the business object. Basically, debug or check the reason why this value is not getting read from DB.
2. Secondly, I execute the rule which is used to determine the agents by using the PFAC transaction. By enabling the checkbox to terminate if rule resolution without result will just simply make a workflow to hang or keep in the system without having any user assigned if in case you do not handle properly. Therefore first try to check the by passing valid values to the rule container by using PFAC transaction.

By completing the above two steps now you might understand the reason why the agents are not fetched, then you can follow the suggestions provided by other experts.

Regards

Pavan

[former_member186746]

Hi,

Did you transport the agent assignments of the dialog tasks with RHMOVE30?

Kind regards, Rob Dielemans

[former_member202733]

rob.dielemans Thanks, but I don't and as it is my first rodeo, shame on me, but I have no idea what is that.

Best regards,

Ronaldo S. Vieira

[former_member186746]

Hi,

For dialog tasks you can maintain the agent assignment in PFTC for the task, and then additional data-->agent assignment-->maintain.

This can also be done directly from the workflow builder. Any change you make here is regarded by SAP as an HR relation. Most SAP systems have recording of changes made to the Organizational structure off. So to transport these changes you have to use report RHMOVE30.

Kind regards, Rob Dielemans

[Vivek0459]

Hi Ronaldo,

You should give a try by refreshing runtime buffer in PRD , or run transaction SWU_OBUF.

Please try once and also let me know if it help.

[Sandra_Rossi]

Ronaldo Silveira Vieria SAP buffers the workflow definitions. It executes what is buffered (eventually it loads into buffer what is not buffered yet). When you transport, the buffer is not refreshed. It is refreshed implicitly at midnight every day, or via SWU_OBUF. For more information, read the SAP note 980834 - Buffering of workflow definitions

[former_member202733]

vivekkumar.singh2 thank you! I not allowed to execute this transaction in production system, but I ask basis people and after then run, I will ask the user to try again and come back and tell you the result.

Best regards,

Ronaldo S. Vieira

[former_member202733]

Hi, vivekkumar.singh2

Vivek Kumar Singh SWU_OBUF could not solve my problem.

best regards,

Ronaldo S. Vieira

[p244500]

Hi,

This will happen when you select the agent and if the agent is initial , you have to terminate the process, otherwise it will send work item to all SAP user.

Regards,

Nawa

[former_member202733]

nawanandana.edirisinghe thanks and it will be useful, but now it don't solve the problem I am faccing.

best regards,

Ronaldo S. Vieira

[p244500]

Hi ,

Other option will be refresh SAP inbox. Go to SAP business workplace> Setting>workflow Setting >Refresh organizational environment .

Regards,

Nawa.

[former_member202733]

Hi nawanandana.edirisinghe I have to do this for each user?

best regards

Ronaldo S. Vieira

[p244500]

Hi Ronaldo Silveira Vieria,

Normally you have to do it relevant users only. I mean this issue has has faced. Just try for one user and try it.

Regards,

Nawa.

[mh97]

Hi Ronaldo,

If SWU_OBUF mentioned above does not work -

You said it is a ZBUS method .. so a custom method, right? Can you have the developer debug the method with the input values provided in the workflow container?

Normally you would use an agent rule (transaction PFAC) to handle agent determination. In that case you should go to PFAC_DIS and test the rule with the relevant values. But it appears your custom method "Set_Agent" is where the issue is.

I hope this is helpful!

Margaret

[former_member202733]

mhilsbos thank you.

Yes, I have a ZBUS with a custom method, and if I execute this method in production system via SWO1 it works fine, but I have no idea why when the user creates the entry sheet it is not.

The rule, I can't execute PFAC in production system, but in SWDD I can do this:

And as you can see, it's works.

Now, what is the difference between my approach and using PFAC?

Best regards,

Ronaldo S. Vieira

[anjan_paul]

Hi,

Also check the business configuration setting in prod and compare with Quality.

Thanks

[former_member202733]

Thanks anjan.paul ! As I said before it is my first rodeo so could you please tell me where can I check those settings?

Best regards,

Ronaldo S. Vieira

[anjan_paul]

Hi Ronaldo,

Could you please check and share screenshots of both Prod and Quality for binding between Rule and Step in workflow.

Thanks.