ChangeAcknowledgeMatchDocument

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 

For the four way match, it is assumed that inspection results have been ChangeAcknowledged 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 PuchaseOrder 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 PuchaseOrder or from the PuchaseOrder to the Invoice.  Charges not associated with a specific Invoice line match be matched individually.

The LoadMatchDocument is for use both by the accounts payable application and the purchasing application in exchanging the transactions that are required to be matched.

The purpose of ChangeAcknowledgeMatchDocument is for the accounts payable application to send successful matching notification or a match fail.notification to a purchasing application. 

Element information

Content

• Sequence [1..1]
  from type BusinessObjectDocumentType
  ApplicationArea [1..1]    Provides the information that an application may need to know in order to communicate in an integration of two or more business applications. The ApplicationArea is used at the applications layer of communication. While the integration frameworks web services and middleware provide the communication layer that OAGIS operates on top of.
  1. DataArea [1..1]    Is where the information that the BOD message carries is provided, in this case ChangeAcknowledgeMatchDocument. The information consists of a Verb and one or more Nouns. The verb (ChangeAcknowledge) indicates the action to be performed on the Noun (MatchDocument).

Attributes

Sample instance

<ChangeAcknowledgeMatchDocument releaseID="normalizedString">
   <ApplicationArea>
      <Sender>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <TaskID>normalizedString</TaskID>
         <ReferenceID>normalizedString</ReferenceID>
         <ConfirmationCodes>...
         </ConfirmationCodes>
         <AuthorizationID>normalizedString</AuthorizationID>
      </Sender>
      <Receiver>
         <LogicalID>normalizedString</LogicalID>
         <ComponentID>normalizedString</ComponentID>
         <ID/>
      </Receiver>
      <CreationDateTime></CreationDateTime>
      <Signature>
         <!--any element-->
      </Signature>
      <ScenarioID>normalizedString</ScenarioID>
      <CorrelationID>normalizedString</CorrelationID>
      <BODID>normalizedString</BODID>
      <Extension>
         <AnyExtension>
            <!--any element-->
         </AnyExtension>
         <Amount/>
         <Code/>
         <DateTime></DateTime>
         <ID/>
         <Indicator>true</Indicator>
         <Measure/>
         <Name/>
         <Number>1.0</Number>
         <Quantity/>
         <Text/>
         <Time></Time>
         <ValueText>string</ValueText>
      </Extension>
   </ApplicationArea>
   <DataArea>
      <ChangeAcknowledge>
         <OriginalApplicationArea>...
         </OriginalApplicationArea>
         <ResponseCriteria>...
         </ResponseCriteria>
      </ChangeAcknowledge>
      <MatchDocument>
         <MatchDocumentHeader>...
         </MatchDocumentHeader>
         <MatchDocumentLine>...
         </MatchDocumentLine>
      </MatchDocument>
   </DataArea>
</ChangeAcknowledgeMatchDocument>