Contracts are used to group multiple Service Objects and their Service Commitments so that they can be billed together on a recurring basis. A contract in DYCE is the technical equivalent of one or more actual contract documents. A contract defines the commercial framework (contractual partners, invoice recipients, accounting conditions). Service Objects (and their Service Commitments) represent the components of the contract.
A Service Object is something that the customer either buys or for which a contractual agreement is concluded, resulting in mutual obligations. A Service Object can thus be clearly assigned to a customer. The Service Object is usually static, but the associated Service Commitments can change. Furthermore, additional information can be stored in the Service Object that is independent of the Service Commitments themselves. The Service Object itself does not contain any billing-relevant information - this belongs to the associated Service Commitments. Service Commitments that are not invoiced via a contract can also belong to a Service Object.
Service Commitments describe the content of agreements with customers and suppliers. They exist in customer-side and vendor-side form and always belong to a concrete Service Object. In addition, they contain billing information such as the quantity to be billed, the billing period and the amount. The Service Commitments of a Service Object and the creation of these Service Commitments are defined via a multi-level hierarchy. It includes Service Commitment Templates and Service Commitment Packages that can be assigned to items. Service Objects are created via the sale of these items, to which the associated Service Commitments are visible.