RequisitionHeaderType
Complex type information
Namespace: http://www.openapplications.org/oagis/9
Schema document: org_openapplications_oagis/9_4_1/Developer/Nouns/Requisition.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
- PurchaseOrderReference [0..*] Is a reference to a PurchaseOrder
- 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.
- RequesterParty [0..1] The party that requested the associated entity.
- RequiredDeliveryDateTime [0..1] Indicates the date in which the buyer/customer requests the order to be delivered.
- 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 RequestHeaderType - Sequence
[0..1]
Attributes
None
Used by
- Element RequisitionHeader
Type inheritance chain
- HeaderType
- StatusEnabledHeaderType
- RequestHeaderType
- RequisitionHeaderType
- RequestHeaderType
- StatusEnabledHeaderType