PR status changes to "Cancelled" after resubmitting a rejected PR

(0) Share

Report

Posted on by Lubna

In purchase requisition workflow, once a PR is rejected by the approver, and the requester tries to resubmit, the workflow status changes to Cancelled. The PR header status remains Rejected.

This is also applicable when the approver selects request change action in the workflow. When the delegate submits the PR, the workflow status changes to Cancelled. The PR header status remains In review.

Is anyone else facing this issue? Please suggest on resolving this.

*This post is locked for comments

I have the same question (0)

All responses (7)

Answers (0)

RaviRaj 530 on at

Like (0)

Report

Hi LI,

Using the standard workflow or customize anything in standard workflow

Was this reply helpful? Yes No
Lubna on at

Like (0)

Report

Hi Raja,

There is no customization in the PR workflow. However we have done a customization in releasing PR to PO process to set the PO status to "Not submitted" instead of "Approved" as soon as its released.

Was this reply helpful? Yes No
Suggested answer

Jonathan Halland 11,310 on at

Like (2)

Report

Hi LI.

This is not a "Bug" in the system. When you resubmit a purchase requisition, the original workflow instance gets cancelled and a new one is auto-created and submitted.

I'm not 100% sure why MS decided to do this on PRs, but I suspect its to ensure that the whole workflow process is followed from start to finish on resubmit, rather than just going back to the step that had the original change request was made from.

Was this reply helpful? Yes No
Lubna on at

Like (0)

Report

Hi Jonathan,

The issue is once the original instance is cancelled, the new workflow instance doesn't get created. Hence the user is unable to proceed with the PR.

Was this reply helpful? Yes No
Jonathan Halland 11,310 on at

Like (0)

Report

Hi LI

What is the actual document status of the PurchReq? I'm assuming for now that the workflow batch job is running successfully as the new Instance gets kicked off only once the original is fully cancelled by the batch process. It sounds like there is a bug in your system, possibly caused by a customisation.

You can check the following

1. No customizations exist on the PurchReqWFTypeEventHandler (class) - Canceled (Method) - This is responsible for initiating a new workflow instance.

2. No customizations exist on the PurchReqWorkflow (Class) - reSubmitPurchReqTable (Method) - This is responsible for marking that the new workflow instance should be kicked off

Was this reply helpful? Yes No
Lubna on at

Like (0)

Report

The document status is Rejected. I have checked the methods suggested by you and it turns out there is no customization in them.

We have logged a case with the Microsoft support team regarding this issue.

Thank you for your time Jonathan!

Was this reply helpful? Yes No
fatihgork 3,817 on at

Like (0)

Report

Hi,

Have you tried a Full CIL? It worths a shot usually in workflows

Was this reply helpful? Yes No