Service contract life cycle
A service contract goes through the various states in each phase of its life cycle.
| Life-cycle | State | Action |
|---|---|---|
| A service contract is generated. | Draft |
|
| Service contract gets activated on the date of activation. | Active |
|
| Service contract is deactivated on the date of expiration. | Expired | No action. |
| Service contract is canceled. | Canceled | No action. |
The service contract line items and entitlements also perform similar actions in the respective states.
When a parent entity moves to the Expired state, the child entities inherit the same state. For example, when a service contract expires, the related contract lines and entitlements also expire.
However, the state change of a child entity doesn't affect it parent entity.
The sold product or install base item referenced either in the contract line or an entitlement must be in the same state as the entity where it's referenced.
Suspended state
When a sold product is suspended, the related service contract lines and entitlements, in the Draft or Active states, move to the Suspended state as well.
- Editing the field values.
- Creating records in the corresponding related lists.
On resuming the sold product, the related service contract line item or entitlement acquires the state depending on its start and end dates. For example, a resumed entitlement that has its start date in the past and its end date in the future, acquires the Active state.
Exceptionally, when a contract line or entitlement in the Suspended state has reached its end date, it moves to the Expired state automatically.
Date validations
A service contract line associated with a service contract must be created within the service contract's start and end dates. Any modification to the dates of service contract lines must comply with the date range of the parent service contract.