This content has been marked as final. Show 6 replies
Pl identify the parameters used to run the Workflow Background Process in both instances, along with the schedule in both instances.1 person found this helpful
Recommended Schedule For Workflow Background Process For Order Management [ID 971925.1]
Thank you for your reply. The Background process schedule is same in both the instances. Please advice.
How about the parameters being passed for the background process in the two instances ?
The PO Requisition Approval Notification Activity goes to 'Deferred' status instead of 'Notified' when the transition occurs and to make to 'Notified' i have to run the "Workflow Background Process" evrytime. The Same works fine in our Test Environment but does not work in our Development Instance. Both Instance is clone of Production. The "Workflow Background Process" is scheduled in both the instances.Please see these docs.
I am unable to find out what is causing this, is it WF Engine Threshold setup or something? If so how to find the Threshold in both the instances. Please help to solve
Workflow Background Process Does Not Progress Shipped Lines: Stuck in Fulfill - Deferred [ID 804133.1]
How To Diagnose Purchase Order And Requisition Workflows in Deferred Status? [ID 884391.1]
Why Is Requisition Approval Stuck In-Process / Deferred When Delegate Person Approves The Requisition? [ID 382935.1]
PO Does Not Get Automatically Generated As Workflow Activity Goes Into DEFERRED Mode when Calling WF_STANDARD.noop. [ID 779805.1]
11.5.10: How To Diagnose Intermittent Document Manager Error 3 During Purchase Order And Requisition Approval? [ID 1273090.1]
Thank you for your reply. The Background process schedule is same in both the instances. Please advice.Can you find any errors in the Workflow/Database log files?
Thanks to Hussein and Srini for your help. The Metalink Note "How To Diagnose Purchase Order And Requisition Workflows in Deferred Status? [ID 884391.1]" helped to identify the issue. The package “POXWPA7B.pls” version was different in our developement and test instances. This was because the patch 5508851 was applied in our test instance.
where line = 2
and name = 'PO_WF_PO_NOTIFICATION';
Development Instance: /* $Header: POXWPA7B.pls 115.38.11510.5 2005/03/22 10:15:55 nipagarw ship $ */
Test Instance: /* $Header: POXWPA7B.pls 115.38.11510.10 2006/07/12 13:20:02 ambansal ship $ */
After applying the same patch in development instance the deferreing of notification activity stopped occuring.