OAGIS 9_2 -- PurchaseOrder Documentation

Table of Contents

top

Schema Document Properties

Target Namespace http://www.openapplications.org/oagis/9
Element and Attribute Namespaces
  • Global element and attribute declarations belong to this schema's target namespace.
  • By default, local element declarations belong to this schema's target namespace.
  • By default, local attribute declarations have no namespace.
Schema Composition
  • This schema includes components from the following schema document(s):
    • ../Components/Operational/OrderManagementComponents.xsd

Declared Namespaces

Prefix Namespace
Default namespace http://www.openapplications.org/oagis/9
xml http://www.w3.org/XML/1998/namespace
xsd http://www.w3.org/2001/XMLSchema
Schema Component Representation
<xsd:schema targetNamespace="http://www.openapplications.org/oagis/9" elementFormDefault="qualified">
<xsd:include schemaLocation="../Components/Operational/OrderManagementComponents.xsd"/>
...
</xsd:schema>
top

Global Schema Components

Element: PurchaseOrder

Name PurchaseOrder
Type PurchaseOrderType
Nillable no
Abstract no
Documentation The purpose of the PurchaseOrder Business Object Document is to communicate an order to purchase goods from a buyer to a supplier. The PurchaseOrder carries information to and from the buyer and supplier. The PurchaseOrder is a legally binding document once both Parties agree to the contents and the specified terms and conditions of the order.
More information at: http://www.openapplications.org/oagis/9.

The Process PurchaseOrder sends the electronic form of a purchase order document from a customer to a supplier in order to purchase n-number of Lines each of which containes an Ordered Item.
More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<PurchaseOrder>
<PurchaseOrderHeader> ... </PurchaseOrderHeader> [0..1]
<PurchaseOrderLine> ... </PurchaseOrderLine> [0..*]
</PurchaseOrder>
Schema Component Representation
<xsd:element name="PurchaseOrder" type=" PurchaseOrderType "/>
top

Element: PurchaseOrderHeader

Name PurchaseOrderHeader
Type PurchaseOrderHeaderType
Nillable no
Abstract no
Documentation The Purchase Order Header contains information that applies to the entire purchase order. This Component is required.
More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<PurchaseOrderHeader>
<!-- ' OrderHeaderType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<OrderDateTime> ... </OrderDateTime> [0..1]
<BuyerParty> ... </BuyerParty> [0..1]
<AcceptByDateTime> ... </AcceptByDateTime> [0..1]
<ReleaseNumber> ... </ReleaseNumber> [0..1]
<RequisitionReference> ... </RequisitionReference> [0..*]
<QuoteReference> ... </QuoteReference> [0..*]
<SalesOrderReference> ... </SalesOrderReference> [0..*]
<UserArea> ... </UserArea> [0..1]
</PurchaseOrderHeader>
Schema Component Representation
<xsd:element name="PurchaseOrderHeader" type=" PurchaseOrderHeaderType "/>
top

Element: PurchaseOrderLine

Name PurchaseOrderLine
Type PurchaseOrderLineType
Nillable no
Abstract no
Documentation The Purchase Order Line indicates the ordered item or product ordered along with the quantity, price and other descriptive information. It is also possible to provide additional Parties, PaymentTerms, Charge, and Attachment information as needed at the line level. At least one occurrence of this Component is required for each occurrence of the Purchase Order.
More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<PurchaseOrderLine>
<!-- ' OrderLineType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<BackOrderedQuantity> ... </BackOrderedQuantity> [0..1]
<ReceivedQuantity> ... </ReceivedQuantity> [0..1]
<OpenQuantity> ... </OpenQuantity> [0..1]
<QuoteReference> ... </QuoteReference> [0..1]
<SalesOrderReference> ... </SalesOrderReference> [0..1]
<BuyerParty> ... </BuyerParty> [0..1]
<PurchaseOrderSubLine> ... </PurchaseOrderSubLine> [0..*]
<PurchaseOrderSchedule> ... </PurchaseOrderSchedule> [0..*]
<UserArea> ... </UserArea> [0..1]
</PurchaseOrderLine>
Schema Component Representation
<xsd:element name="PurchaseOrderLine" type=" PurchaseOrderLineType "/>
top

Element: PurchaseOrderSubLine

Name PurchaseOrderSubLine
Type PurchaseOrderSubLineType
Nillable no
Abstract no
Documentation The Component Subline represents any additional information concerning the product on the Line. The Subline can be used to describe a specific configuration of the ordered item.
More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<PurchaseOrderSubLine>
<!-- ' RequestSubLineType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<UserArea> ... </UserArea> [0..1]
</PurchaseOrderSubLine>
Schema Component Representation
<xsd:element name="PurchaseOrderSubLine" type=" PurchaseOrderSubLineType "/>
top

Element: PurchaseOrderSchedule

Name PurchaseOrderSchedule
Type PurchaseOrderScheduleType
Nillable no
Abstract no
Documentation The Component Schedule represents the requested ship or delivery dates for goods ordered. The Schedule is an optional Component. The Schedule can not be associated with a Subline. It is only associated with a Line.
More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<PurchaseOrderSchedule>
<!-- ' ProcurementScheduleType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<UserArea> ... </UserArea> [0..1]
</PurchaseOrderSchedule>
Schema Component Representation
<xsd:element name="PurchaseOrderSchedule" type=" PurchaseOrderScheduleType "/>
top

Complex Type: PurchaseOrderType

Super-types: None
Sub-types: None
Name PurchaseOrderType
Abstract no
Documentation The schema type for PurchaseOrder. MAKE ALL CHANGES TO ORDER, NOT PO! PurchaseOrder's base abstract type, Order, is shared between PurchaseOrder and SalesOrder. SalesOrder is essentially an extension of PurchaseOrder, but in order to use the local-global design pattern, each of PO and SO needs to instantiate its own Header and Line elements.To do this, we factored out the PO content models, instantiated both PO and SO from Order.
More information at: http://www.openapplications.org/oagis/9.
XML Instance Representation
<...>
<PurchaseOrderHeader> ... </PurchaseOrderHeader> [0..1]
<PurchaseOrderLine> ... </PurchaseOrderLine> [0..*]
</...>
Schema Component Representation
<xsd:complexType name="PurchaseOrderType">
<xsd:sequence>
<xsd:element ref=" PurchaseOrderHeader " minOccurs="0"/>
<xsd:element ref=" PurchaseOrderLine " minOccurs="0" maxOccurs="unbounded"/>
</xsd:sequence>
</xsd:complexType>
top

Complex Type: PurchaseOrderHeaderType

Super-types: OrderHeaderType < PurchaseOrderHeaderType (by extension)
Sub-types: None
Name PurchaseOrderHeaderType
Abstract no
XML Instance Representation
<...>
<!-- ' OrderHeaderType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<OrderDateTime> ... </OrderDateTime> [0..1]
<BuyerParty> ... </BuyerParty> [0..1]
<ReleaseNumber> ... </ReleaseNumber> [0..1]
<UserArea> ... </UserArea> [0..1]
</...>
Schema Component Representation
<xsd:complexType name="PurchaseOrderHeaderType">
<xsd:complexContent>
<xsd:extension base=" OrderHeaderType ">
<xsd:sequence>
<xsd:element ref=" OrderDateTime " minOccurs="0"/>
<xsd:element ref=" BuyerParty " minOccurs="0"/>
<xsd:element ref=" AcceptByDateTime " minOccurs="0"/>
<xsd:element ref=" ReleaseNumber " minOccurs="0"/>
<xsd:element ref=" RequisitionReference " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref=" QuoteReference " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref=" SalesOrderReference " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref=" UserArea " minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Complex Type: PurchaseOrderLineType

Super-types: OrderLineType < PurchaseOrderLineType (by extension)
Sub-types: None
Name PurchaseOrderLineType
Abstract no
XML Instance Representation
<...>
<!-- ' OrderLineType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<OpenQuantity> ... </OpenQuantity> [0..1]
<BuyerParty> ... </BuyerParty> [0..1]
<UserArea> ... </UserArea> [0..1]
</...>
Schema Component Representation
<xsd:complexType name="PurchaseOrderLineType">
<xsd:complexContent>
<xsd:extension base=" OrderLineType ">
<xsd:sequence>
<xsd:element ref=" BackOrderedQuantity " minOccurs="0"/>
<xsd:element ref=" ReceivedQuantity " minOccurs="0"/>
<xsd:element ref=" OpenQuantity " minOccurs="0"/>
<xsd:element ref=" QuoteReference " minOccurs="0"/>
<xsd:element ref=" SalesOrderReference " minOccurs="0"/>
<xsd:element ref=" BuyerParty " minOccurs="0"/>
<xsd:element ref=" PurchaseOrderSubLine " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref=" PurchaseOrderSchedule " minOccurs="0" maxOccurs="unbounded"/>
<xsd:element ref=" UserArea " minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Complex Type: PurchaseOrderSubLineType

Super-types: RequestSubLineType < PurchaseOrderSubLineType (by extension)
Sub-types: None
Name PurchaseOrderSubLineType
Abstract no
XML Instance Representation
<...>
<!-- ' RequestSubLineType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<UserArea> ... </UserArea> [0..1]
</...>
Schema Component Representation
<xsd:complexType name="PurchaseOrderSubLineType">
<xsd:complexContent>
<xsd:extension base=" RequestSubLineType ">
<xsd:sequence>
<xsd:element ref=" UserArea " minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top

Complex Type: PurchaseOrderScheduleType

Super-types: ProcurementScheduleType < PurchaseOrderScheduleType (by extension)
Sub-types: None
Name PurchaseOrderScheduleType
Abstract no
XML Instance Representation
<...>
<!-- ' ProcurementScheduleType ' super type was not found in this schema. Some elements and attributes may be missing. -->
<UserArea> ... </UserArea> [0..1]
</...>
Schema Component Representation
<xsd:complexType name="PurchaseOrderScheduleType">
<xsd:complexContent>
<xsd:extension base=" ProcurementScheduleType ">
<xsd:sequence>
<xsd:element ref=" UserArea " minOccurs="0"/>
</xsd:sequence>
</xsd:extension>
</xsd:complexContent>
</xsd:complexType>
top