ShowShipment schema, example, validation rules, validation stylesheet |
ShowShipment type: ShowShipment | |
A Shipment is a business document that details the intent to transport a specific quantity of material goods from a supplier to a single customer business partner destination. The Shipment has been modeled after similar proprietary documents on popular business software packages (SAP's Delivery Note, Oracle Applications' Delivery document, etc.) A Shipment is typically derived from the shipping schedule associated with a customer's purchase or sales order, once overall demand and various other business factors which prioritize the availability of the supplier's goods inventory have been evaluated. The Shipment document is designed to have a dynamic structure and content. Initial shipment planning information can be updated and significant detail (actual picked inventory attributes, ship unit packaging, etc.) may be added during the execution phase of the supplier's order fulfillment and shipping business processes. The final form of the Shipment document can provide detail about the carrier and level of service used to transport the material, the exact quantity and attributes of the material shipped, and how that material is physically packaged and identified for transport. To aid the customer's planning and receiving business processes, the supplier may transmit the final Shipment document to customer in advance so that they can prepare for carrier arrival and then efficiently accept and utilize the ordered material. In this use case, the Shipment document may function as a traditional Advance Ship Notice (ASN). A ShipUnit is a data element that identifies and describes a specific collection of goods inventory that is packaged by a supplier for carrier transportation to a customer business partner destination. A ShipUnit is generally the smallest "thing" that can be individually moved and tracked throughout a carrier's transportation network. The physical size, inventory, content and internal nested container complexity within a ShipUnit is arbitrary. The ShipUnit component was specifically designed to be transportation mode independent. It may be used to represent any uniquely identifiable and trackable assembly, container or vessel including, but not limited to: a parcel express package; a pallet of identical or mixed items; a truck trailer, rail car or an ocean cargo container. This BOD does not usually cause updates to occur. Shipment Characteristics A Shipment document does not necessarily have a one-to-one relationship with any customer purchase/sales order document, line item or line item schedule. For shipping efficiency, a Shipment document may consolidate inventory shipment requests from a variety of different orders that have the same ultimate physical destination. In fact, there may be no customer sale at all, as when the supplier is simply transferring inventory from one warehouse site to another within their enterprise to maintain optimum stocking levels. A Shipment typically involves a minimum of three business partner entities: Supplier, Carrier, and Customer in the most common business transaction scenario. However these partner titles are more useful as descriptions of the basic roles in the Shipment process. The actual number and relationship of the potential business partners/parties involved in the transaction is intended to be flexible in usage to accommodate agents working on behalf of partners and unique or complex scenarios. The ShipUnit component identify and describe the physical shipping container(s) and internal packaging structure of the delivered goods. ShipUnit component are typically constructed to describe the result of an inventory picking and packing operation. The ShipUnit structure complements the line-item oriented summary information provided in the Shipment's ShipItem and InventoryDetail component with detailed information to accurately describe complex shipping unit assemblies and item packaging. This robust level of detail is often demanded by customers to improve the efficiency of their receiving operations. If the supplier provides trustworthy ship unit packaging information in advance, the customer does not have to spend valuable receiving personnel time breaking down the containers to inspect and tally each inventory item. The general industry trend toward smaller just-in-time deliveries of only the required amount of goods, customer-imposed packaging configurations and requirements, and suppliers performing value-added light assembly customization at the time of shipment is driving the need for more detailed information about the product as it is actually delivered. |
ShowShipment extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
ShowShipmentDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ShowShipment Scenario Diagram |
Show schema |
Show type: Show | |
The Show verb is used when sending the information about a specific instance of a business document or entity. The Show verb may be used to respond to a Get request or it can be used in a publish scenario, where it pushes information to other applications based on a business event.Although BODs based on this verb do not commonly cause updates to occur, there may be times when the component receiving the Show decides to use the information it receives to update. This is entirely the decision of the receiving software component and is not forbidden.The behavior of the Show verb is quite straight forward with one exception. The Show response to any Get request needs to read the request carefully to ensure the response is returning the requested Data Types. |
Show extends: ConfirmableVerb | |
Structure: |
![]() |
Shipment schema |
Shipment type: Shipment | |
A Shipment document identifies and describes a specific collection of goods to be transported by a carrier and delivered to one or more business partner destinations. A Shipment document represents the extent and content of "transportation work" to be done by the carrier. For transportation efficiency, a shipment document typically consolidates deliveries to multiple destinations within a certain geographic region and may provide carrier routing instructions to each delivery stop. |
Header type: Header | |
Provides general information about the document that is used to transport a specific quantity of material goods from a supplier to a single customer business partner destination. |
ShipUnit type: ShipUnit | |
Provides information that identifies and describes a shipping unit assembly or container for shipment. |
ShipItem type: ShipItem | |
Provides general information about the item inventory being delivered, including the planned and actual quantities. This information usually directly references a line item or shipment schedule line on a sales order, purchase order or other inventory transfer document. |
Container type: Container | |
Provides information about an intermediate packaging level within the shipping unit. |
ShipmentInventoryItem type: ShipmentInventoryItem | |
Provides a specific quantity of goods inventory packed within the ShipUnit or Container. This information usually references the related line item or shipment schedule on a sales order, purchase order or other inventory transfer document. |
Container | |||||||||||||||||||||||||||||||
All Container occurrences are required to have an identity (ContainerId) which is unique to all containers/packaging within the shipping unit. The ContainerId can be an actual unique physical identifier on the intermediate container/packaging or a logically unique construct of a business application. The latter method may be used when the intermediate container/packaging that has no unique physical identity, but a description of the nested relationship is still desired. The Container also contains an identity reference to its parent or outermost enclosing container (ParentContainerId). The parent container may be the ShipUnit container itself. When all ContainerID and ParentContianerId references within the ShipUnit are evaluated, the shipping unit's internal nested structure must form a spanning tree graph encompassing all defined Container and InventoryItem. No self-referencing or circular reference constructs are allowed. The spanning tree graph should accurately represent how all the containers and inventory items are physically packed within the shipping unit. |
|||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||
Elements: |
|
Header extends: SCEHeader | |||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
ShipItem extends: SCEItem | ||||||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
Shipment extends: Noun | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
ShipmentInventoryItem | |||||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
ShipUnit extends: SCEUnit | ||||||||||||||||
The ShipUnit supports the optional capability to accurately describe the internal intermediate container and item packaging structure with the shipping unit to any arbitrary complexity or nesting depth |
||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
Verb Common Files |
Verb.xsd schema |
AcknowledgableVerb extends: ConfirmableVerb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
AcknowledgementType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
ConfirmableVerb extends: Verb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
ConfirmType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
Expression restricts: xs:string | |
ExpressionCriteria | |||||||||
Structure: |
![]() |
||||||||
Elements: |
|
||||||||
Attributes: |
|
RequestVerb extends: ConfirmableVerb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
VerbBase.xsd schema |
Verb type: Verb | |
Verb | |
Structure: |
![]() |
Noun Common Files |
SupplyChainExecution.xsd schema |
InventoryDetail type: LotSerial | |
Provides additional inventory attribute information for an inventory item, such as lot numbers, quality/disposition, serial numbers, or other characteristics that may not be specified on the order documentation. |
ShipmentDocumentReference type: ShipmentDocumentReference | |
Is a reference to a Shipment. |
OwnershipCode type: OwnershipCode | |
is used to identify who or which organization owns the item or part. The content of this Field is user defined based on a specific Customer or Supplier. SYNONYMS: Vendor Consignment ID, Supplier Consignment ID Idenifies who owns the associated entity. |
FreightClass type: FreightClass | |
Qualifies goods for purposes of freight cost calculation. An example would the qualifications used by National Motor Freight Carriers. Qualifies goods for purposes of freight cost calculation. An example would the qualifications used by National Motor Freight Carriers. EXAMPLES National Motor Freight Carriers (NMFC) Class Code Based on an evaluation of density, stowability, ease of handling and liability, the commodities are grouped into one of 18 classes. |
CatchWeightQuantity type: Quantity | |
This is the actual weight of the ReceivedQuantity for the Item, if the NetWeightQuantity cannot be calculated precisely via arithmetic because the goods do not have a consistent per unit weight A decimal value. |
CatchWeightConversionFactor type: Factor | |
The catch weight conversion factor is a stock keeping conversion factor for inventory goods. This is a special conversion factor for when the units of measure can not be converted using arithmetic. This conversion factor is used with the CatchWeightQuantity. Examples of the use of this factor include: - Number of Chickens to a Box - Number of units of a chemical in a barrel |
NetWeight type: Quantity | |
This is the total net weight of the ReceivedQuantity for the Item, if the ReceivedQuantity is not in weight units. This is the weight of the goods received, disregarding any container or shipping packaging A decimal value. |
OriginationCountry type: Country | |
Is the country in which the Shipment originated. Standard values from ISO 3166-3:1999 Part 1 Codes for the representation of names of countries and their subdivisions - Part 1: Country codes |
ShipUnitReference type: ShipUnitReference | |
SCEHeader | ||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
SCEItem | |||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||||||||||||||
Elements: |
|
SCEUnit extends: Noun | ||||||||||||||||||||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||||||||||||||||||||
Elements: |
|
ShipmentDocumentReference extends: DocumentReference | ||||||||||||||||
Is a reference to a Shipment document. |
||||||||||||||||
Structure: |
![]() |
|||||||||||||||
Elements: |
|
ShipUnitReference | ||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|