JournalEntryHeaderType
In the Header, DocumentReferences is the link that ties back to a sub ledger transaction entry ID. It is the identifier of an original transaction or document. For example, it could be the receipt or the summarized inventory activity. This is the element that refers to an audit record. Together with the Sender information, the DocumentReferences is part of the referencing system, which will enable drill back audit trail functionality.
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/JournalEntry.xsd
Content
- Sequence
[1..1]
- 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
- DocumentDateTime [0..1] The date that document was created within the system of record.
- AccountingDate [0..1] Is the date that is used to determine the accounting period the transaction is posted within. It is also known as the effective or post date.
- 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.
- Sequence
[0..1]
- Amount [0..1] The monetary value of the object in which the amount is associated
- 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
- ExchangeRate [0..1] ** deprecated in favor of CurrencyExchangeRate ** ExchangeRate is the conversion from one one currency to another currency Identifing the conversion factor and the source in which it was obtained, the date in which the conversion factor was set, and the effective period in which it is to be used.
- CurrencyExchangeRate [0..1] Identifies the exchange rate between two currencies. For the transaction in which this is associated.
- EntryCreator [0..1] Identifies the user that creates the associated transaction
- 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.
- 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.
- 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.
- 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 LedgerEntryHeaderTypefrom group LedgerAmountGroupfrom group FreeFormTextGroupfrom group ReferencesGroup
Attributes
None
Used by
- Element JournalEntryHeader
Type inheritance chain
- LedgerEntryHeaderType
- JournalEntryHeaderType