Error message “Thread id 65 attempted an illegal state transition from Approved to Pending. (18081,1006)” When Adding A New Req Line To A Req Where A Cancelled Req Line Already Exists (Doc ID 2067061.1)

Last updated on MAY 22, 2017

Applies to:

PeopleSoft Enterprise SCM Purchasing - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

Error When Adding a New Requisition Line to a Requisition Where a Cancelled Requisition Linen Already Exists.

Error message “Thread id 65 attempted an illegal state transition from Approved to Pending. (18081,1006)” displayed when a new line is added to a requisition where a cancelled line exists and Workflow Approval Required is selected on the PO Business Unit Definition, on Requisition Change Options page.

ERROR
-----------------------
18081,1006


STEPS
-----------------------
The issue can be reproduced at will with the following steps:

1. On Business Unit US005 Purchasing Definition – Requisition Change Options page, selected Workflow Approval Required.
2. Logged as user id VP1, created a new US005 Requisition by copying Requisition US005-000000002.
3. Requisition US005-0000000008 created in Pending status.
4. Requisition requires approval by User VP2
5. Signed in as VP2 and went to the Worklist. Selected Requisition US005-0000000008
6. Clicked Approve button.
7. Requisition is Approved
8. Signed back in as user VP1 and accessed Requisition US005-0000000008.
    Clicked on Budget Check
9. Requisition is budget checked. Clicked on line 2 details.
10. Clicked the Cancel X.
11. Click Yes to the message.
12. Requisition header displays Approved.
13. After Saving the Requisition Header Status changed to See Lines.
14. Added a requisition line 4.
15. When Saved, the following error message displayed:

Thread id 65 attempted an illegal state transition from Approved to Pending. (18081,1006) EOAW_CORE.Utils.OnExecute Name:ThrowIllegalStateTransitionException PCPC:20444 Statement:517
Called from:EOAW_CORE.ENGINE.Thread.OnExecute Name:Activate Statement:256
Called from:EOAW_CORE.ENGINE.PathInst.OnExecute Name:Launch Statement:58
Called from:EOAW_CORE.ENGINE.StageInst.OnExecute Name:InnerLaunch Statement:211
Called from:EOAW_CORE.ENGINE.StageInst.OnExecute Name:Launch Statement:229
Called from

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms