Contract Workspace (CW) stuck in Publishing/Pending as the effective date was mistakenly entered a future date.

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

• If CW in Publishing: In the Contract Request (CR) document, add a serial approver before the approval node with aribasystem or any other completed approval node.
  Ask the user to Deny the CR approval.

Denying the CR approval will set the CW back to Draft status. Then you can proceed to edit Effective Date and republish the CW.

• If CW in Pending: The processing will not complete until the Effective Date is reached.

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.

Purchasing > Contract Compliance
Strategic Contracts > Contract Terms/Spend
Strategic Contracts > Contract Workspace/Requests