Non Travel Expenses workflow error

[former_member201225]

Hi ,

There is a current requirement for our client to incorporate the non-travel related expenses.

There is already a WF tat takes care of the Travel Expenses. The client wants to incorporate the non travel related expenses in the same scenario with affecting the existing WF.

The process flow for the already existing WF is as follows : The user creates a travel request and an travel request id is generated. Once the travel is done, he goes an fills up his reimbursement and that is mapped against this travel request id. The WF is triggered and this passes to a verifier and in turn passes to the approver who approves it.

The existing WF is working fine.

Now there is a requirement of incorporating non travel related expenses. For eg : Team Outing, client lunch etc etc. The client wants this also to be mapped to the given workflow scenario as that of the Travel Expenses without affecting the existing process.

The entries are made in the front end. There is a webdynpro consultant who takes care of the same. The webdynpro consultant has made changes in the portal screen to incorporate non-travel related stuff. A non-travel related request does not in essence have a trip id.So a dummy trip id is like kind of maintained to take care of the non-travel related expense.

The existing WF for travel related expenses validates whether there is any approved travel request id generated against which a travel expenses can be mapped. In the case of non-travel request, the webdynpro consultant is doing a validity check in the front end itself to see if there is a trip id present and if so only is the process continuing further.

The issue arises in the following place : When the normal scenario is run where the travel expenses is raised , the WF works correctly and it is sent to the approver without any issues.

When a non-expense related issue is raised, it goes up to the verifier but it does not reach the approver stating that No Agents found. I checked the binding and the agent assignment and whether the agent assignment was general etc.....everything was fine. I am not able to figure out what the issue is.

Is there anything tat can be tweaked in the workflow. Everything works fine in the normal expense related stuff. When a non-expense is raised, it is not able to get the agents for the approver. Is there anything that can be done from the front end of webdynpro or anything that can be tweaked in the workflow.

Please help us out on the same.

Thanks in advance for all the help.

[Former Member]

I assume the task is classified as general already since it is working for some scenario. As mentioned above, test the agent assignment rule. My guess is that although the binding is correct, fields passed to the agent assignment rule have some blank values. It could be that the rule expects a trip ID (or a trip-related value), but that value is not available because the WF is for non-travel expenses.

[suresh_subramanian2]

Hello Eshram !

Are you using rule to determine the agents ? If so, please check at PFAC , whether it populates the agent details properly.

If rule is working fine, check the workflow log.In the workflow log, if agent details are found,then make sure that the agent is possible agent(not in excluded agent list) and still verify whether the agent has authorization to receive the work item.

Some times, if workflow and organizational buffers are not up- to-date, no agent found would be the error message.So, refresh the workflow and organization buffers at SWU_OBUF and PPWFBUF transactions respectively.

Regards,

S.Suresh

[Former Member]

Hello eshram,

We had a almost similar scenario where the client wanted to take care of the non-travel related expense in the existing set up.

There is no absolutely no tweaking that would be required in the workflow.Please note that in the existing WF there will be validations to check for the trip id.

Any tweaking in the existing WF would imply change in the business scenario itself and that would affect the existing process of the standard workflow for travel related expenses.

There should be some changes in the parameters in the front end coding done by the dynpro consultant. The reason why you are getting the errors that no agents are existing in the approver for your workflow is bcos there are validations done by SAP and it is failing.

We had also tried to tweak the workflow but after spending days and nights of R&D, we could not change the workflow as per the requirement as it was affecting the standard flow.

Either the webdynpro consultant should check for the parameters to be passed from his/her end or there should be an alternate solution to take care of non travel expenses separately.....it cannot be kind of mapped to the existing process.

Hope this suffices.

Cheers,

Ganesh