Uses the Component:PackageInformationType
Package of work assigned to the workshop oder. This structures represents only the package head data. The content of the package meaning the corresponding labours, parts and sublets are represented as separated labour, sparepart etc elements of the order and has a corresponding RelatedPackage elememnt set to PackageID of the PackageInformation.
Table 6.114. Fields and Components
| Name | Description | Occurrence | Type | Data Type | User Notes |
|---|---|---|---|---|---|
| PackageID |
Technical PackageInfo item identification. The ID must be unique within the workshop order. The 'schemaID' attribute states the identification schema or origin of the ID. | 0..1 | Field | udt:TextType | |
| PackageNumber |
Business identification of the package, based on package catalog. The schemeID attribute identifies the corresponding package catalog (origin). Contact your package catalog provider for allowed values. | 0..1 | Field | udt:IdentifierType | |
| PackageLineNumber |
Sequence number of the packageInfo whithin this order item. Can be used to define the order of lines on an invoice. | 0..1 | Field | udt:NumericType | |
| PackageDescription |
Description of the item, normally invoice text. | 0..* | Field | udt:TextType | |
| Pricing |
Provides pricing infomation. | 0..* | Component | PricingABIEType | |
| Tags |
Whitespace separated list of tags for additional description of package kind ( e.g. maintenance). | 0..1 | Field | udt:TextType |
The XML Sample provided here is an approximation of the generated XML for this component. Not all of the fields are required for implementation.
Example 6.112. PackageInformation
<PackageInformation>
<PackageID>......</PackageID> [0..1]
<PackageNumber>......</PackageNumber> [0..1]
<PackageLineNumber>......</PackageLineNumber> [0..1]
<PackageDescription>......</PackageDescription> [0..*]
<Pricing>......</Pricing> [0..*]
<Tags>......</Tags> [0..1]
</PackageInformation>