UpdateMatchFailure schema, example, validation rules, validation stylesheet |
UpdateMatchFailure type: UpdateMatchFailure | |
In certain application suites, purchase order / invoice matching functionality exists in the purchasing application, while in other suites this functionality exists in the accounts payable application. The invoice matching process may include several document types, including the following: · Two way match - Purchase Order and the Invoice · Three way match - Purchase Order, Invoice, and the Receipt · Four way match – Purchase Order, Invoice, Receipt, and Inspection results Note: For the four way match, it is assumed that inspection results have been updated on the Purchase Order for visibility in matching. When matching takes place in the purchasing application, the accounts payable application may have to inform the purchasing application of the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched if the invoice is initially entered into the accounts payable application. Note that in some situations, invoices are entered directly into the purchase order application or are created by the purchase order application when using evaluated receipt settlement (ERS) and in this instance, it is not necessary to perform the separate integration described in these chapters. When matching takes place in the accounts payable application, the purchasing application must inform the accounts payable application of the purchasing transactions (purchase orders, goods receiving notes and inspection tickets) to which the invoice (in accounts payable) is to be matched. These integration scenarios have been developed for document matching to occur at the line level within the PO document and the Invoice document. This may be a one to one relationship, or it may be a many to one relationship from Invoice to PO or from the PO to the Invoice. Charges not associated with a specific Invoice line match be matched individually. The purpose of the UpdateMatchFailure is to notify the purchasing application of a matching failure such as a tolerance failure. The UpdateMatchOk is used for the accounts payable application to send successful matching notification to a purchasing application. The LoadMatchDocument is discussed in another chapter. The LoadMatchDocument is used to keep invoice, purchase order, goods receipt note and inspection ticket information current. In the model below, invoice matching functionality exists in the accounts payable application, the invoice is entered into accounts payable, and purchasing publishes matching document information to which accounts payable subscribes. |
UpdateMatchFailure extends: BusinessObjectDocument | |||||||
Structure: |
![]() |
||||||
Elements: |
|
UpdateMatchFailureDataArea extends: DataArea | ||||||||||
Structure: |
![]() |
|||||||||
Elements: |
|
UpdateMatchFailure Scenario Diagram |
Update schema |
Update type: Update | |
The Update verb is used to describe specific processing in a more fine-grained manner beyond add, change or delete processing. An example is the update of inspection information from one business application to another. The event is not adding a document, or changing fields per se, it is communicating the occurrence of an event as well as the corresponding data that accompanies the event. |
Update extends: Verb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
UpdateExpressionCriteria | |||||||||||||||||
Structure: |
![]() |
||||||||||||||||
Elements: |
|
||||||||||||||||
Attributes: |
|
||||||||||||||||
Enumerations: |
|
MatchFailure schema |
MatchFailure type: MatchDocument | |
Match Fail represents notification that purchasing lines have failed in matching to a supplier invoice. The matching of a purchase order to an invoice is used to determine the amount paid to the vendor |
Verb Common Files |
Verb.xsd schema |
AcknowledgableVerb extends: ConfirmableVerb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
AcknowledgementType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
ConfirmableVerb extends: Verb | |||||||||
Structure: |
![]() |
||||||||
Attributes: |
|
ConfirmType restricts: xs:NMTOKEN | |||||||
Enumerations: |
|
Expression restricts: xs:string | |
ExpressionCriteria | |||||||||
Structure: |
![]() |
||||||||
Elements: |
|
||||||||
Attributes: |
|
RequestVerb extends: ConfirmableVerb | |||||||
Structure: |
![]() |
||||||
Elements: |
|
VerbBase.xsd schema |
Verb type: Verb | |
Verb | |
Structure: |
![]() |
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: |
|