MatchDocumentHeaderBaseType

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.
  1. DocumentType [0..1]    Types of Documents involved in a matching process. Typically the document type is one of these values: Invoice, Purchase Order, Receipt, Inspection
  2. LedgerID [0..1]    Identifies the financial ledger to be used when updating balances
  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.
  3. AccountingPeriod [0..1]    A period used for accounting period.
  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. RemittanceID [0..1]    Remittance refers to a reference identifier to print on a remittance advice, for example, supplier invoice number.
  7. PaymentMethodCode [0..1]    Is the payment method code for the associate entity.
  8. SpecialPriceAuthorizationCode [0..1]    Is the supplier's code to authorize special pricing as a result of an agreement.SYNONYMS: Price Authorization, Price Code
  9. ContractReference [0..1]    Is a reference to a contract
  10. ReleaseNumberID [0..1]    Identifies the Release Number in the case of Blanket POs
  11. EntryCreatorUser [0..1]    Identifies the user that creates the associated transaction
  12. SupplierParty [0..1]    Identifies the supplier organization/entity of the items or inventory for the associated transaction. In most cases there is one SupplierParty per transaction. i.e. one SupplierParty for a given PurchaseOrder. However in the cases where an transaction Broker is involved there are cases where a single transaction may have different SupplierParties at the line level or in the case of a Catalog for the Catalog.
  13. PaymentTerm [0..*]    Identifies the Terms i.e. the time and number of payments and the amount or percentage of the payment.
  14. Charge [0..*]    Specifies the details for Charges that may be applied to the associated transaction
  15. Distribution [0..*]    A distribution of the financial credit or debit of the transaction across an organization.
  16. 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.

Attributes

Used by

• Element MatchDocumentHeader via derived type MatchDocumentHeaderType

Type inheritance chain

• DocumentIdentificationBaseType
  • HeaderBaseType
    • StatusHeaderBaseType
      • MatchDocumentHeaderBaseType
        • extended by MatchDocumentHeaderType