DistributionType

A distribution identifies how monetary amounts are distributed accross an organization.

See http://www.openapplications.org/platform/1.

Complex type information

Content

• Sequence [1..1]
  1. LedgerID [0..1]    Identifies the financial ledger to be used when updating balances
  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.
  2. Percentage [0..1]    Identifies the percentage of the Line Price applicable to the distribution line. This is used to derive the Amount on the distribution line.
  3. Quantity [0..1]    Identifies the quantity of the associated service or item that is addresses by the component in which the quantity is associated.
  4. Amount [0..1]    The monetary value of the object in which the amount is associated
  5. GLNominalAccount [0..1]    Is the primary account classification within a chart of accounts. For example reveune, Fixed Asset, Land, Buildings, etc.
  6. GLElement [0..1]    Accounting code elements
  from group EnterpriseUnitGroup
  Sequence [0..1]
  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
  7. ProjectReference [0..1]    Identifies a project that is associated with the given component.
  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 Distribution