Incident DTO v11

Field Name Type Category Constraint Reference Description
breakdown Boolean Optional Flag that specify if the notification is related to the breakdown of the machine
businessPartner Identifier Required BusinessPartner : 16, 17, 18, 19, 20 BP attached to this Incident
code String Optional length >= 0 & length <= 255 Code of incident object
codeGroup String Optional length >= 0 & length <= 255 The types of the incidents are identified by a code and the codes are classified in the groups.
contact Identifier Optional Contact : 12, 13, 14, 15, 16 contact person attached to this Incident
description String Optional length >= 0 & length <= 255 Incident description
endTo Date Optional end date for this Incident
equipment Identifier Optional Equipment : 14, 15, 16, 17, 18 Incident on which equipment
malfunctionFrom Date Optional Date from when the machinery is not function properly.
malfunctionTo Date Optional Date when the machinery is back to normal.
priority Long Optional Resolve priority of incident object.
purchaseOrderDate Date Optional Each incident is created inside of a sales order, this field specify the date
purchaseOrderNo String Optional length >= 0 & length <= 255 Each incident is created inside of a sales order, this field specify the number
responsible String Optional length >= 0 & length <= 255 Person who report this Incident, this is not keep in our system
startFrom Date Optional Start date for this Incident
subject String Required length >= 0 & length <= 255 Incident's subject
type String Optional length >= 0 & length <= 255 There are several possible types for an incident