CreditType

When the receiver of this Credit provides the credit management function.  If the sender is the accounts receivable application, the OpenItemAmount is the only required amount field.  When the sender is the customer order management application, the OrderAmount is the only required amount field. 

The OrderAmount Is the total of the sales order that is typically used to compare against a credit limit during credit checking.

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

Complex type information

Content

• Sequence [1..1]
  from type CreditBaseType
  from group IDsGroup
  Sequence [0..1]
  1. ID [0..*]    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.
  GLElement [0..1]    Is the primary balancing segment of the GL Account structure. Typically, this is the owning entity for the transaction. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law. P&L statements are required at this level.
  ApprovalStatus [0..1]    A code to reflect the approval status of a process. A process may be approved as a way of performing a task. A non standard process may be approved because of local legal or cultural norms.
  from group FreeFormTextGroup
  Sequence [0..1]
  1. Description [0..*]    
  2. Note [0..*]    
  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 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. OpenItemAmount [0..1]    Is the total orders invoiced yet still considered open items in the receivables balance.
  2. OrderAmount [0..1]    Is the total of the sales order that is typically used to compare against a credit limit during credit checking.
  3. ApprovedOrderAmount [0..1]    Is the total amount of orders approved but not yet invoiced.
  4. AvailableAmount [0..1]    Is the credit amount available for a trading partner to make an additional order against. This amount is typically a combination of orders approved but not yet invoiced and orders invoiced yet still considered open items in the receivables balance.
  5. OrderLimitAmount [0..1]    Is the credit limit of a single sales order used during credit checking.
  6. TotalCreditLimitAmount [0..1]    Is the total credit limit for a trading partner used during credit checking.
  7. DocumentDateTime [0..1]    Is the timestamp in which the document was created.
  8. EffectiveTimePeriod [0..1]    Defines the date and time when a particular document or item takes effect or becomes valid.
  9. LedgerID [0..1]    Identifies the financial ledger to be used when updating balances.
  10. Payment [0..*]    
  11. 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 Credit

Type inheritance chain

• CreditBaseType
  • CreditType