Finance | Project Operations, Human Resources, ...

Workflow - Expenditure participant - Ununderstandable behavior (bug?)

(0) Share

Report

Posted on by Lionel Vrac

270

Hi,

I just discover a critical issue on project I'm currently working for.

When I create a purchase requisition involving a workflow assignment to a "dimension owner", I have this bug even though everything is set up correctly (users, employee exists with relationship in place etc..) + inventory posting are also correctly in place..

Stopped (error): X++ Exception: Participant token 'TPCO' does not resolve to any user
at SysWorkflowParticipantProvider-resolve
SysWorkflowParticipantProvider-resolveParticipants
SysWorkflowServiceProvider-resolveParticipant
SysWorkflowQueue-resume

("TPCO" behing the code of my expenditure participant setup related to purchase requisitions).

Now.. If I fill the MainAccoint dimension, it works !

So my conclusion is that we might have a bug there because it seems obvious that a requestor doesn't have to fill a MainAccount dimension when he creates a PR.

This dimension should be defaulted from posting setup + should be visible neither "overridenable".

Am I wrong ? is there something I missed in the setup on Procurement and/or LEdger modules ? Could you help ?

All responses (2)

Answers (0)

Ravi Goyal 12 on at

Like (0)

Report

RE: Workflow - Expenditure participant - Ununderstandable behavior (bug?)

Hi Lionel,

I am also facing the same issue in Purchase requisition workflow even every setup looks correct. Did you figure out the issue? Can you please share. Thanks.

Regards,

Ravi
Suggested answer

Ludwig Reinhard Microsoft Employee on at

Like (0)

Report

RE: Workflow - Expenditure participant - Ununderstandable behavior (bug?)

Hi Lionel,

Does your findim has an owner assigned?

If this is the case, can you double check whether you experience this issue also in a different demo/test environment?

If also this is the case then open a support ticket with MS to get this fixed.

Just double checked LCS but found nothing alike.

Therefore, opening a support case might be the best and fastest solution to get this issue resolved.

Best regards,

Ludwig