PurchaseOrderHeaderType
Complex type information
Namespace: http://www.openapplications.org/oagis/9
Schema document: org_openapplications_oagis/9_4_1/Developer/Nouns/PurchaseOrder.xsd
Content
- Sequence
[1..1]
- Sequence
[0..1]
- DocumentID [0..1] Is the primary document id for the document associated.
- AlternateDocumentID [0..*] Is the alternate document id for the associated document.
- LastModificationDateTime [0..1] The datetime on which the object was last modified
- DocumentDateTime [0..1] The date that document was created within the system of record.
- Sequence
[0..1]
- Description [0..*]
- Note [0..*]
- Sequence
[0..1]
- 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.
- Status [0..*] Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective.
- 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.
- CustomerParty [0..1] Is the organization that is the end customer of the goods or services being provided in the associated transaction.
- SupplierParty [0..1] Identifies the supplier organization/entity of the items or inventory for the associated transaction. In most cases there is one SupplierParty per transaction. i.e. one SupplierParty for a given PurchaseOrder. However in the cases where an transaction Broker is involved there are cases where a single transaction may have different SupplierParties at the line level or in the case of a Catalog for the Catalog.
- 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
- PlannerContact [0..1] Identifies the contact information of the person, organization, department, or group that planned for the timing of the exchange of goods/services that this document is associated at the document or line level.
- CatalogReference [0..1] Is a reference to a catalogue.
- ContractReference [0..1] Is a reference to a contract
- ExtendedAmount [0..1] Is an amount not including taxes or charges. In the case of orders, this is typically the Unit Price times the Order Quantity.
- TotalAmount [0..1] Indicates the total amount of the object associated. This includes the Price and the total of all the charges, allowances and taxes.
- QualifiedAmount [0..1]
- EnterpriseUnit [0..1] Identifies the agiven portion of an organization. Some commonly defined Units are identified here. These units are typically used to track financial data in reporting systems within an organization. Similar to Business Units, Organizational Units are only relevant within an enterprise
- BillToParty [0..1] Identifies the party that the bill or invoice is to be sent. In most cases this is the same as the CustomerParty however there are many cases where the CustomerParty and the BillToParty will be different.
- CarrierParty [0..1] Idenitfies the party that serves as the carrier of the goods or services for the transaction.
- PayFromParty [0..1] Identifies the party that the payment for the goods or services will come.
- PartialShipmentAllowedIndicator [0..1] Identifies if a partial shipment to a customer is allowed.
- DropShipmentAllowedIndicator [0..1] Indicates whether the order can be drop shipped or not.
- EarlyShipmentAllowedIndicator [0..1] Communicates if it is permitted to ship a good or service prior to the date it is due
- LicenseIndicator [0..*] Indicates what type of licenses are required and indicates which are required.
- TaxExemptIndicator [0..1] Specifies whether the associated element is exempt from withholding taxes.
- TransportationTerm [0..*] When a seller ships something via common to a buyer in accordance with the Uniform Commerical Code and international legal agreements, you must specify a particular "phrase" that states who assumes the risk of shipment, who is responsible for loading and unloading the goods, where ownership or title to the goods passes, who paid or pays the carrirer, etc. Examples of these "phrases" include: - "FOB Origin Prepaid and Add" (Free On Board - no cost for loading, title passes at seller's dock, seller prepaid freight cost and delivery insurance, seller will freight costs to cost of goods) - "FOB Destination" or "FOB Destination Prepaid" (Free On Board - no cost for loading, title passes at buyer's dock, seller prepaid freight cost and delivery insurance) In software applications, this phrase is commonly split into two coded pieces, a "legal terms" risk and responsibility component for use with common carriers (FOB Destination) and some kind of qualifying component (Prepaid and Add).
- PaymentTerm [0..*] Identifies the payment term for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays.
- DistributedCharge [0..*]
- DistributedTax [0..*]
- Tax [0..*] Indicates the tax for the object associated.
- Distribution [0..*] The accounting distribution information associated with a Business Object Document. The position of the Distribution within a Business Object Document provides the context and additional meaning.
- Charge [0..*] Represents the different Charges that may be applied to the associated document.
- Allowance [0..*] Identifies the discount or allowance that the Customer is to receive off of the TotalAmount owed as a result of the associated document or sub-portion of a document.
- SpecialPriceAuthorizationCode [0..1] Is the supplier's code to authorize special pricing as a result of an agreement.SYNONYMS: Price Authorization, Price Code
- EarliestShipDateTime [0..1] This indicates the earliest possible date at which a shipment can be made for the line item
- RequestedShipDateTime [0..1] Indicates the date in which the buyer/customer requests the order to be shipped.
- PromisedShipDateTime [0..1] Indicates the date in which the associated object was promised to be shipped from the supplier.
- PromisedDeliveryDateTime [0..1] Indicates the date in which the associated was promised to be delivered to the customer or consumer.
- PaymentMethodCode [0..1] Is the payment method code for the associate entity.
- Payment [0..*]
- ShippingInstructions [0..1] Is information about the shipping of an item.
- TaxExemptCodes [0..1]
- Event [0..*]
- Classification [0..*] This identifies the classification of an entity. An entity may be classified into mulitple groups for different reasons. Examples of Classification include Commodity Codes, Freight Classifications, Product Line classifications and so on. Suggested Values are COMMODITY, FREIGHT, PRODUCTLINE
- OrderDateTime [0..1] Datetime the order was placed
- BuyerParty [0..1] The entity that is responsible for Buying the document or element in which it is associacted. Additionally, the contact may be a person or a group or department.
- AcceptByDateTime [0..1] Date by which the vendor is expected to accept the PO
- ReleaseNumber [0..1] Identifies the Release Number in the case of Blanket POs
- RequisitionReference [0..*] Is a reference to a Requisition
- QuoteReference [0..*] Is a reference to a Quote
- SalesOrderReference [0..*] Is a reference to a SalesOrder
- UserArea [0..1] Allows the user of OAGIS to extend the specification in order to provide additional information that is not captured in OAGIS.This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document through the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document.The Open Applications Group will make best efforts to quickly consider all proposed submissions.The USERAREA is always the last element in all components, except where the component has been extended inline.
from type HeaderTypefrom group DocumentIDsGroupfrom group FreeFormTextGroupfrom group ReferencesGroupfrom type StatusEnabledHeaderTypefrom type RequestHeaderTypefrom type ProcurementHeaderTypefrom type OrderHeaderType - Sequence
[0..1]
Attributes
None
Used by
- Element PurchaseOrderHeader
Type inheritance chain
- HeaderType
- StatusEnabledHeaderType
- RequestHeaderType
- ProcurementHeaderType
- OrderHeaderType
- PurchaseOrderHeaderType
- OrderHeaderType
- ProcurementHeaderType
- RequestHeaderType
- StatusEnabledHeaderType