BudgetLedgerHeaderType

The JournalEntryID is the  ID in the source sub-ledger that generated the transaction

The IncrementIndicator identifies if the amounts in the ledger budget lines are intended to increment or replace any existing amounts

See http://www.openapplications.org/oagis/9.

Complex type information

Content

• Sequence [1..1]
  from type HeaderType
  from group DocumentIDsGroup
  Sequence [0..1]
  1. DocumentID [0..1]    Is the primary document id for the document associated.
  2. 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.
  from group FreeFormTextGroup
  Sequence [0..1]
  1. Description [0..*]    
  2. Note [0..*]    
  from group ReferencesGroup
  Sequence [0..1]
  1. DocumentReference [0..*]    
  2. 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.
  1. JournalEntryID [0..1]    Is the externally created identifier for a general ledger journal entry.
  2. IncrementIndicator [0..1]    Indicates whether the budget amounts are to replace the existing amounts or be summed into the existing budget amounts.
  3. LedgerID [0..1]    Identifies the financial ledger to be used when updating balances
  4. 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
  5. 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.
  6. TransactionAnalysisCode [0..1]    Is a segmenting code used to analyze accounting transactions. It is commonly used in project accounting applications.
  7. User [0..1]    Identifies the user of a given system.
  8. 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.

Attributes

None

Used by

• Element BudgetLedgerHeader

Type inheritance chain

• HeaderType
  • BudgetLedgerHeaderType