PayableHeaderType

Complex type information

Content

• Sequence [1..1]
  from type DocumentIdentificationBaseType
  ID [0..1]    Is the Identifiers of the given instance of an entity within the scope of the integration. The schemeAgencyID attribute identifies the party that provided or knows this party by the given identifier.
  RevisionID [0..1]    Is the revision of the semantically named document. The combination of the ID and its revision uniquely identifies the associated entity.
  VariationID [0..1]    
  DocumentIDSet [0..*]    
  from type HeaderBaseType
  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.
  from group FreeFormTextGroup
  Description [0..*]    
  Note [0..*]    
  from group ReferencesGroup
  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.
  from type StatusHeaderBaseType
  Status [0..*]    Indicates the status of the associated object by providing the Status Code along with a description and when the status is effective.
  from type LedgerEntryHeaderBaseType
  LedgerID [0..1]    Identifies the financial ledger to be used when updating balances
  GLEntityID [0..1]    A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law. It is normally the primary balancing segment of the GL Account structure. Typically, this is the owning entity for the transaction. Synonyms are Business Unit, Fund, G/L Company, Joint Venture, Non-Profit Association Name
  AccountingPeriod [0..1]    A period used for accounting period.
  SourceDocumentReference [0..1]    This is the link that ties back to a sub ledger transaction entry ID. It is the identifier of an original/ source transaction or document. The type indicates the type of document i.e. PurchaseOrder, Invoice, Receipt, Credit Memo, Voucher etc. For example, it could be the receipt or the summarized inventory activity. This is the singular field that refers to an audit record. Together with the Sender information, this is part of the referencing system, which will enable drill back audit trail functionality.
  from group LedgerAmountGroup
  Amount [0..1]    The monetary value of the object in which the amount is associated
  DebitCreditCode [0..1]    
  TaxBaseAmount [0..1]    This is the Amount for the associated object expressed in the ledger or base currency
  FunctionalAmount [0..1]    The monetary value of the object to which the FunctionalAmount is associated, expressed in the ledger or base currency
  TaxBaseFunctionalAmount [0..1]    This is the Tax Amount for the associated object expressed in the ledger or base currency
  CurrencyExchangeRate [0..1]    A rate of exchange between two currencies.
  EntryCreatorUser [0..1]    Identifies the user that creates the associated transaction
  PaymentTerm [0..*]    Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment.
  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.
  from type PayableHeaderBaseType
  VoucherReference [0..1]    Is a reference to a voucher document. This is typically an internal voucher, possibly created as a a payable reference against an external invoice
  RemitToParty [0..1]    Identifies the party or location that the payment is to be remitted to or sent to.
  PayeeParty [0..1]    This is a Party that is identified as a Payee on an Accounts Payable document. The SupplierParty of the goods or services typically.
  1. Extension [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 Extension is always the last element in all components, except where the component has been extended inline.

Attributes

None

Used by

• Element PayableHeader

Type inheritance chain

• DocumentIdentificationBaseType
  • HeaderBaseType
    • StatusHeaderBaseType
      • LedgerEntryHeaderBaseType
        • PayableHeaderBaseType
          • PayableHeaderType