Skip to main content

Service Objects

Service Objects represent a history of products sold to a customer. They contain all information related to the delivered item, such as
.

  • Masterdata (Item No., Description).
  • Details of the sale (customer, delivery recipient, invoice recipient)
  • Quantity, date of provision and date of next settlement
  • All Service Commitments (sales and Service Commitments including prices, terms and cancellation periods).

A Service Object can be created automatically from a sales order using the Shipment (see Service Commitment Option field on the Item card for prerequisites). When a Service Object is created on shipment, the information is taken from the order and delivery.
Alternatively, a Service Object can also be entered manually by creating a new record (action New in the Service Objects page) and filling in the fields on each fast tabs. This may be necessary, for example, in the case of a manual transfer of equipment or licenses. The Service Object with the associated Contract Commitments forms the basis for the Customer and Vendor Contracts and their periodic Recurring Billing.

The following information is required to manually create a Service Object:

  1. No. can be filled via a number series.
  2. Item No. is used to define the device/software/license/user/... that will be billed recurrently. Only items with the Service Commitment Option Sales with Service Commitments or Service Commitment Item can be selected.
  3. The Description is automatically taken from the item and can be edited.
  4. In the Quantity any positive, integer value can be entered. It specifies the number of devices/licenses whose Service Commitments are to be billed recurrently.
  5. The Service Commitments fast tab contains information (contact and customer information) about which customer has purchased the item and the Service Commitments. When creating a Service Object manually, the customer must be entered here.
  6. The Shipping and Billing fast tab contains information about the (original) shipment of the product and whether a different invoice recipient paid for the item. The contact details of the delivery recipient from the sales order are automatically used. The Ship-to party can be changed if required (even subsequently), in the same way as for sales documents. The other delivery recipient fields are automatically updated after modification.

As additional information, the Version, the Provision Start Date and the Provision End Date can be maintained, whereby the Provision Start Date is automatically entered when the Service Object is created via the delivery from a sales order.

info

A Service Object can only be deleted if all related Service Commitments are deleted. The Service Commitments are therefore - if possible - also deleted when the Service Object is deleted.

Entering Service Commitments in a Service Object#

An item is required to create Service Commitments, since Services Commitments themselves cannot be created manually. An item must be entered in the Service Object in order to create a Service Commitments. The Assign Service Commitments function can be used to view the Service Commitment Packages with the item's Service Commitments. The function opens the selection window of the same name. In the window, the Service and Calculation Start Date can be entered and Service Commitment Packages can be selected. Only Service Commitment Packages that have not yet been created as Services in the Service Object appear in the selection. For all selected Service Commitment Packages, the corresponding Service Commitments are created in the Service Object.

Quantity change#

For Service Objects whose items are not configured for item tracking (lot or serial number obligation), the quantity can be changed directly in the Service Object. This will result in a recalculation of the Service Amounts in the associated Service Commitments and contract lines. It is not possible to change the quantity for Service Objects whose items are configured for item tracking (lot or serial number obligation). Service Objects with lot number tracking retain the quantity from the delivery (or that of the initial entry). Service Objects with serial number tracking can only be created with quantity=1.