MatchOK schema |
MatchOk type: MatchDocument | |
Match OK represents notification that purchasing lines were successfully matched to a vendor invoice. The matching of a purchase order to an invoice is used to determine the amount paid to the vendor. |
Noun Common Files |
MatchDocument.xsd schema |
MatchDocument type: MatchDocument | |
Identifies an internal document containing matching information. Essential it holds cross reference information among the customer Purchase Order and the Suppier Invoice. It supports N-way matching. |
Header type: MatchDocumentHeader | |
Header information for the matching document instance. |
Line type: MatchDocumentLine | |
Line level infoi\rmatoin for the matching doucment. |
MatchPoint type: MatchPoint | |
A Match Line (like geometric lines) must consist of at least 2 Match Points. A Match Point can match different lines in documents identified in other Match Points. It is not required that LineNumbers are the same. |
MatchCriteria type: MatchCriteria | |
The Match Criteria is included in the match document to identify the type of information being matched. It identifies the information for the associated matching document. |
MatchCriteria | ||||||||||||||||||||||
Match Criteria identifies the detailed information that is being matched. Typically this is the unit price, unit quantity the the extended amount. |
||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||
Elements: |
|
MatchDocument extends: Document | |
Structure: |
![]() |
MatchDocumentHeader extends: DocumentHeader | |||||||||||||||||||||||||
A Matching Document is a document in and of itself. It may exist in an ERP application, just like a Sales Order. The Matching Document essentially holds a cross reference among the documents being matched. The header contains general and financial information. The document references used in the Header are for all of the doucments being matched in addition to documents that are not explicitly part of the matching process, but still need to be referenced, such as a Quote. However, since matching is essentiall N-way, even a Quote could be matched. Note that the Status on the MatchDocument indicates whether the Match was successful or was a failure. |
|||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|
MatchDocumentLine extends: DocumentLine | |||||||||||||
A Match Line contains the information for the matching cross reference among the documents being matched. Each Match Line contains 2 or more Match Points. A Match Point represents the document being matched and the matching critieria. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
MatchPoint | |||||||||||||
A Match Point identifies a document and the matching critier that is matched with other Match Points. The DocumentReference must be mutually exclusive of the other Match Point Document References for the Match Line. |
|||||||||||||
Structure: |
![]() |
||||||||||||
Elements: |
|
Document.xsd schema |
Document extends: Noun | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
DocumentHeader | ||||||||||||||||||||||||||||
Structure: |
![]() |
|||||||||||||||||||||||||||
Elements: |
|
DocumentLine | |||||||
Structure: |
![]() |
||||||
Elements: |
|
DocumentOrderHeader restricts: DocumentHeader | |||||||||||||||||||||||||
Structure: |
![]() |
||||||||||||||||||||||||
Elements: |
|