Support Note KB0406356
Email
Contract workspace stuck in publishing/Pending as the effective date was mistakenly entered a future date.
Symptom

Contract workspace stuck in publishing/Pending as the effective date was mistakenly entered a future date.


Cause

The Contract Workspace is stuck in Publishing/Pending status because the Effective Date entered is a future date. Now we cannot amend the contract workspace.


Resolution

1.Publishing Contract Workspace: In the contract request document, add a serial approver before the approval node with aribasystem or any other completed approval node.
2.Ask the user to Deny the contract request approval.

Denying the contract request approval will set the contract workspace back to Draft status. Then you can proceed to edit Effective Date and republish the workspace.

3.Pending Contract Workspace: The processing will not complete until the Effective Date is reached.


See Also

For additional information regarding why aribasystem is added to the contract request approval flow when effective date is a future date see Contract request approval flow has aribasystem and cannot be fully approved.

You can check more information at: UTP - Contract Terms



Applies To

Purchasing > Contract Compliance

Terms of Use  |  Copyright  |  Security Disclosure  |  Privacy