Uses the Component:PreferenceDetailType
The purpose of the PreferenceDetail component is to identify the preference parameters of a potential customer.
Table 6.127. Fields and Components
| Name | Description | Occurrence | Type | Data Type | User Notes |
|---|---|---|---|---|---|
| SaleClassCode |
Class of vehicle sale, ie new, used, demo, floor sample, etc. | 0..1 | Field | scl:SaleClassEnumeratedType | |
| MinimumPriceAmount |
Minimum price of vehicle. | 0..1 | Field | udt:AmountType | |
| MaximumPriceAmount |
Maximum price of vehicle. | 0..1 | Field | udt:AmountType | |
| MinimumModelYear |
Minimum model year of vehicle. | 0..1 | Field | qdt:YearDateType | |
| MaximumModelYear |
Maximum model year of vehicle. | 0..1 | Field | qdt:YearDateType | |
| MakeString |
Make of vehicle | 0..* | Field | qdt:StringType | |
| PreferredCategoryTypeCode |
Customer's preferred category of vehicle (i.e., SUV, Stationwagon, Runabouts, Cruiser, Multi-hull). | 0..* | Field | udt:CodeType | |
| MinimumLengthMeasure |
Minimum length of vehicle. | 0..1 | Field | sqdt:LengthMeasureType | |
| MaximumLengthMeasure |
Maximum length of vehicle. | 0..1 | Field | sqdt:LengthMeasureType |
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.127. PreferenceDetail
<PreferenceDetail>
<SaleClassCode>......</SaleClassCode> [0..1]
<MinimumPriceAmount>......</MinimumPriceAmount> [0..1]
<MaximumPriceAmount>......</MaximumPriceAmount> [0..1]
<MinimumModelYear>......</MinimumModelYear> [0..1]
<MaximumModelYear>......</MaximumModelYear> [0..1]
<MakeString>......</MakeString> [0..*]
<PreferredCategoryTypeCode>......</PreferredCategoryTypeCode> [0..*]
<MinimumLengthMeasure>......</MinimumLengthMeasure> [0..1]
<MaximumLengthMeasure>......</MaximumLengthMeasure> [0..1]
</PreferenceDetail>