Uses the Component:PartMasterHeaderType
Part Master 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 | |
| PartMasterEffectiveDate |
Date on which the parts/prices in this document become effective. | 1..1 | Field | udt:DateType | |
| PartMasterCountryCode |
The ISO Country Codelist that the parts master applies. | 1..1 | Field | scl:CountryEnumeratedType | |
| RequestCode |
Used to indicate whether the PartsMaster is being sent as a delta or as complete. | 0..1 | Field | scl:RequestEnumeratedType | |
| SalesOrganization |
The sales organization is an organizational unit within Logistics. You can define your own master data within a sales organization. Each sales organization has its own customer and materials master data, its own conditions and its own pricing policy. | 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.2. PartMasterHeader
<PartMasterHeader>
<DocumentDateTime>......</DocumentDateTime> [0..1]
<SecondaryPassword>......</SecondaryPassword> [0..1]
<SecondaryDealerNumberID>......</SecondaryDealerNumberID> [0..1]
<DocumentIdentificationGroup>......</DocumentIdentificationGroup> [1..1]
<PartMasterEffectiveDate>......</PartMasterEffectiveDate> [1..1]
<PartMasterCountryCode>......</PartMasterCountryCode> [1..1]
<RequestCode>......</RequestCode> [0..1]
<SalesOrganization>......</SalesOrganization> [0..1]
</PartMasterHeader>