Uses the Component:PartsActivityHeaderType
Parts Activity Header
Table 6.2. Fields and Components
| Name | Description | Occurrence | Type | Data Type | User Notes |
|---|---|---|---|---|---|
| DocumentDateTime |
Is the date and time the document was last created. This is not the date and time that the BOD message instance was created. | 0..1 | Field | udt:DateTimeType | |
| SecondaryPassword |
Secondary password used to validate access to the dealer information | 0..1 | Field | udt:TextType | |
| SecondaryDealerNumberID |
Identifies secondary dealer number if different than primary "Dealer Number" | 0..1 | Field | udt:IdentifierType | |
| DocumentIdentificationGroup |
A group of identifications that uniquely identifies this document | 1..1 | Component | DocumentIdentificationGroupType | |
| DeliveryTypeCode |
Transaction request delivery type | 0..1 | Field | sqdt:DeliveryTypeCodeType | |
| RequestDateRange |
A date range that is used to request transactions belonging to a specific start and end date range. For example, to request RetailDeliveryReporting, PartsInvoice, RepairOrder transactions belonging to a date range. This component was implemented to facilitate third party - dealer integrations, however it can be used in other scenarios. | 0..* | Component | PeriodABIEType |
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.2. PartsActivityHeader
<PartsActivityHeader>
<DocumentDateTime>......</DocumentDateTime> [0..1]
<SecondaryPassword>......</SecondaryPassword> [0..1]
<SecondaryDealerNumberID>......</SecondaryDealerNumberID> [0..1]
<DocumentIdentificationGroup>......</DocumentIdentificationGroup> [1..1]
<DeliveryTypeCode>......</DeliveryTypeCode> [0..1]
<RequestDateRange>......</RequestDateRange> [0..*]
</PartsActivityHeader>