InvoiceHeaderType
The InvoiceHeader type supports summary amounts for line items, charges and allowances.
See http://www.openapplications.org/oagis/9.
Complex type information
Namespace: http://www.openapplications.org/oagis/9
Schema document: org_openapplications_oagis/9_4_1/Developer/Nouns/Invoice.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.
- 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]
- 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.
- CustomerParty [0..1] Is the organization that is the end customer of the goods or services being provided in the associated transaction.
- RemitToParty [0..1] Identifies the party or location that the payment is to be remitted to or sent to.
- 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.
- ReasonCode [0..1] A code for the invoice.Example: Special allowance for preferred customers.
- PurchaseOrderReference [0..*] Is a reference to a PurchaseOrder
- ContractReference [0..*] Is a reference to a contract
- 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.
- Payment [0..1]
- Tax [0..*] Indicates the tax for the object associated.
- DistributedCharge [0..*]
- DistributedTax [0..*]
- 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.
- 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 StatusEnabledHeaderType - Sequence
[0..1]
Attributes
None
Used by
- Element InvoiceHeader
Type inheritance chain
- HeaderType
- StatusEnabledHeaderType
- InvoiceHeaderType
- StatusEnabledHeaderType