Symptom
Auto-closure function of contracts is scoped in the system.
But when checking a certain contract, the valid-to date is in the past, but it is still in Released status (but expired), not closed by system as expected.
Environment
SAP Business ByDesign
Reproducing the Issue
- Go to Business Configuration work center.
- Scope the question: "Do you want automatic notification of expiring purchasing contracts?"
- Go to Sourcing and Contracting work center, Contracts view.
- Select Expired from the dropdown list on the left top.
- See the contract XXX (XXX represents contract ID) is in Released status.
Cause
It is system design that for contract, if released value is equal to the target value, system will set it to expired even though valid-to date is still in the future. But system will not close it even though auto-closure function is scoped.
Therefore, although valid-to is in the past when user checks it, it will not be displayed in the Closed category but in "Expired" category with status being "Released".
User has to manually close the contract.
Resolution
This is a normal system behavior.
See Also
KBA 2354147 - Purchasing Contracts status set to Closed
Keywords
Contract; Close; Expired; Valid , KBA , SRD-SRM-SC , Sourcing and Contracting , Problem