Uses the Component:VehicleOrderHeaderType
Vehicle Order 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 | |
OrderDate |
Date order originally placed | 0..1 | Field | udt:DateType | |
VehicleOrderTypeString |
Identifies vehicle order type | 0..1 | Field | qdt:StringType | |
OrderedByParty |
A person or organization that ordered an item. | 0..1 | Component | PartyABIEType | |
SoldToParty |
The party to which good or services were sold. | 0..1 | Component | PartyABIEType | |
ShipToParty |
The party receiving the goods or services. | 0..1 | Component | PartyABIEType | |
VehicleOrderQtyNumeric |
Total Number of Vehicles | 0..1 | Field | udt:NumericType | |
LoadNumberString |
Shipment carrier-assigned load number | 0..1 | Field | qdt:StringType | |
BorderCrossingIndicator |
BorderCrossing Indicator | 0..1 | Field | udt:IndicatorType | |
PortOfEntry |
Port of Entry | 0..1 | Field | udt:TextType | |
ReqDeliveryRangeStartDate |
Earliest estimated time of arrival | 0..1 | Field | udt:DateType | |
ReqDeliveryRangeEndDate |
Latest estimated time of arrival | 0..1 | Field | udt:DateType | |
CarrierID |
Carrier Code | 0..1 | Field | udt:IdentifierType | |
WarehouseID |
Warehouse Number | 0..1 | Field | udt:IdentifierType | |
DealerAssignedNumberString |
The number given to an order by a dealer | 0..1 | Field | qdt:StringType | |
StatusDate |
The date the current status was recorded | 0..1 | Field | udt:DateType | |
TargetBuildDate |
The date the OEM expects to build the vehicle | 0..1 | Field | udt:DateType | |
PromisedDeliveryDate |
Indicates the date in which the order was promised to be delivered to the dealer. This is the default unless specified otherwise at the lineitem level. | 0..1 | Field | udt:DateType | |
PromisedShipDate |
Indicates the date in which the order was promised to be shipped from the supplier to the dealer. This is the default unless specified otherwise at the lineitem. level. | 0..1 | Field | udt:DateType | |
SpecialInstructions |
Free form text identifying unique handling of order. | 0..1 | Field | udt:TextType | |
OrderComments |
Free form text of remarks regarding the order. | 0..1 | Field | udt:TextType | |
PriorityString | 0..1 | Field | qdt:StringType | ||
Status |
Deprecated: Use StatusDetail. This is a correction in the naming and design rules. StatusDetail contains the same information as this component. | 0..* | Field | StatusDetailType | |
StatusDetail |
Indicates the status of a particular message or line item. | 0..* | Component | StatusDetailType | |
LastChangeUserID |
The user ID of the person who made the last change in the source application. | 0..1 | Field | udt:TextType | |
VesselName |
The name of the shipping vessel. | 0..1 | Field | udt:TextType | |
ShippingPortCode |
The code identifying the Port of Entry. | 0..1 | Field | udt:TextType | |
PromisedDeliveryWeek |
The week the delivery was promised. | 0..1 | Field | udt:TextType | |
BillToParty |
The party that is receiving the bill for the goods or services. | 0..1 | Component | PartyABIEType | |
CustomerParty |
Is the organization that is the end customer of the goods or services being provided in the associated transaction. | 0..1 | Component | PartyABIEType | |
ManufacturerParty |
The person or organization that manufactures an item. | 0..1 | Component | PartyABIEType | |
PaymentTerms |
The PaymentTerms component represents the payment due dates and payment discount information. | 0..1 | Component | PaymentTermsType | |
IncoTerms |
The Incoterms (international Chamber of Commerce) rules have become an essential part of the daily language of trade. They have been incorporated in contracts for the sale of goods worldwide and provide rules and guidance to importers, exporters, lawyers, transporters, insurers and students of international trade. | 0..1 | Component | IncoTermsType | |
RequestedDeliveryDate |
Requested Delivery Date by the dealer/customer needs to be possible to communicate on header level. | 0..1 | Field | udt:DateType | |
RequestedShipDate |
Requested Shipment Date by the dealer/customer needs to be possible to communicate on header level. | 0..1 | Field | udt:DateType | |
DocumentReferenceIdentificationGroup |
A group of identifications that uniquely identifies this document | 0..1 | Component | DocumentReferenceIdentificationGroupType | |
OrderState |
The OrderState component represents the current and history states of the order. This component may occur many times reflecting the history of states. | 0..* | Component | OrderStateType | |
Price |
Price information | 0..* | Component | PriceABIEType |
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. VehicleOrderHeader
<VehicleOrderHeader> <DocumentDateTime>......</DocumentDateTime> [0..1] <SecondaryPassword>......</SecondaryPassword> [0..1] <SecondaryDealerNumberID>......</SecondaryDealerNumberID> [0..1] <DocumentIdentificationGroup>......</DocumentIdentificationGroup> [1..1] <OrderDate>......</OrderDate> [0..1] <VehicleOrderTypeString>......</VehicleOrderTypeString> [0..1] <OrderedByParty>......</OrderedByParty> [0..1] <SoldToParty>......</SoldToParty> [0..1] <ShipToParty>......</ShipToParty> [0..1] <VehicleOrderQtyNumeric>......</VehicleOrderQtyNumeric> [0..1] <LoadNumberString>......</LoadNumberString> [0..1] <BorderCrossingIndicator>......</BorderCrossingIndicator> [0..1] <PortOfEntry>......</PortOfEntry> [0..1] <ReqDeliveryRangeStartDate>......</ReqDeliveryRangeStartDate> [0..1] <ReqDeliveryRangeEndDate>......</ReqDeliveryRangeEndDate> [0..1] <CarrierID>......</CarrierID> [0..1] <WarehouseID>......</WarehouseID> [0..1] <DealerAssignedNumberString>......</DealerAssignedNumberString> [0..1] <StatusDate>......</StatusDate> [0..1] <TargetBuildDate>......</TargetBuildDate> [0..1] <PromisedDeliveryDate>......</PromisedDeliveryDate> [0..1] <PromisedShipDate>......</PromisedShipDate> [0..1] <SpecialInstructions>......</SpecialInstructions> [0..1] <OrderComments>......</OrderComments> [0..1] <PriorityString>......</PriorityString> [0..1] <Status>......</Status> [0..*] <StatusDetail>......</StatusDetail> [0..*] <LastChangeUserID>......</LastChangeUserID> [0..1] <VesselName>......</VesselName> [0..1] <ShippingPortCode>......</ShippingPortCode> [0..1] <PromisedDeliveryWeek>......</PromisedDeliveryWeek> [0..1] <BillToParty>......</BillToParty> [0..1] <CustomerParty>......</CustomerParty> [0..1] <ManufacturerParty>......</ManufacturerParty> [0..1] <PaymentTerms>......</PaymentTerms> [0..1] <IncoTerms>......</IncoTerms> [0..1] <RequestedDeliveryDate>......</RequestedDeliveryDate> [0..1] <RequestedShipDate>......</RequestedShipDate> [0..1] <DocumentReferenceIdentificationGroup>......</DocumentReferenceIdentificationGroup> [0..1] <OrderState>......</OrderState> [0..*] <Price>......</Price> [0..*] </VehicleOrderHeader>