StopDetailBaseType

Complex type information

Content

• Sequence [1..1]
  from type IdentificationType
  ID [0..*]    Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier.
  IDSet [0..*]    
  1. ContainerID [0..*]    The unique identifier of a container that holds the associated entity. A container is typically used for shipping material. Whether they be raw material or finished goods or piece parts.
  from group FreeFormTextGroup
  Description [0..*]    
  Note [0..*]    
  2. TrackingID [0..1]    TRACKINGID is a unique identifier for the purpose of tracking an individual package or shipment Examples of a valid TRACKINGID include: •An express parcel tracking number as typically assigned by UPS, DHL, Fedex or other similar carriers. •A UCC (Uniform Code Council) Serialized Shipping Container (SCC-18) identifier, as assigned by the shipper. •A "Pro Number" (Progressive Number), as assigned by an LTL (less-than-truckload) freight carrier. Since the same Pro Number can be assigned to multiple shipping units within an LTL shipment, the SHIPUNITSEQ and SHIPUNITTOT field identifiers may be used to identify the individual pieces. •The unique identifier of a motor freight trailer, railroad box or tank car, ocean freight container or other transportation vessel.
  3. ShipToParty [0..1]    Identifies the ShipToParty for the document or the line. In a lot of cases, this is the same as the CustomerParty. In multi-organization purchasing, the CustomerParty may be different from the BuyerParty
  4. Party [0..*]    A generic Party for non-validated or application-validated parties. A work-around for situations where Schema-validation of Parties is not feasible or not desired.
  5. ShipUnitReference [0..*]    
  6. ShipmentReference [0..*]    Is a reference to a Shipment.
  from group ReferencesGroup
  DocumentReference [0..*]    
  Attachment [0..*]    The Attachment represents binary data files that may be included within a BOD. These files replace the paper specifications and drawings attached to a BOD definition to clearly communicate design requirements. This Data Type is optional. Attachment usage is further defined by its position.
  7. BillOfLadingReference [0..1]    Is a reference to the associated Bill of Lading document.

Attributes

Name	Occ	Type	Description	Notes
typeCode	[0..1]	CodeType_1E7368		from type IdentificationType
actionCode	[0..1]	ActionCodeContentType		from type IdentificationType

Used by

• Element StopDetail via derived type StopDetailType

Type inheritance chain

• IdentificationType
  • StopDetailBaseType
    • extended by StopDetailType