Schema Central > OAGIS® 10 > LoadResponseMatchDocument.xsd > LoadResponseMatchDocument
Advanced search
Need XML Help?

Recommended Reading:

Definitive XML Schema

 

Web Service Contract Design and Versioning for SOA

 

Advanced XML Applications

 

LoadResponseMatchDocument

The purpose of the LoadResponseMatchDocument is to LoadResponse to the communication of a Change or Update of the MatchDocument information concerning invoice matching  from another business 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 purchasing application may have to request the accounts payable application to provide the supplier invoice to which purchasing transactions (purchase orders, goods receiving notes and inspection tickets) are to be matched.  This is the generally the situation when the invoice is initially entered into the accounts payable application.

Note that in some situations, accounts payable will send invoices to the purchasing application unsolicited. In others, 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. Alternatively, the accounts payable application can request the information.

Element information

Type: LoadResponseMatchDocumentType

Properties: Global, Qualified, ID: oagis-id-ac6ff94fc7fc4ed7b8e4b372fadb5167

Content

Attributes

Name Occ Type Description Notes
releaseID [1..1] NormalizedStringType OAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on. from type BusinessObjectDocumentType
versionID [0..1] NormalizedStringType Indicates the version of the given BOD definition. from type BusinessObjectDocumentType
systemEnvironmentCode [0..1] SystemEnvironmentCodeContentType Indicates whether this BOD is being sent in a "Test" or a "Production" mode. If the BOD is being sent in a test mode, it's information should not affect the business operation. However, if the BOD is sent in "Production" mode it is assumed that all test has been complete and the contents of the BOD are to affect the operation of the receiving business application(s). Default value is "Production". from type BusinessObjectDocumentType
languageCode [0..1] LanguageCodeContentType Indicates the language that the contents of the BOD is in unless otherwise stated. Default value is "en-US". from type BusinessObjectDocumentType

Sample instance

<LoadResponseMatchDocument 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>
      <LoadResponse>
         <OriginalApplicationArea>...
         </OriginalApplicationArea>
         <ResponseCriteria>...
         </ResponseCriteria>
      </LoadResponse>
      <MatchDocument>
         <MatchDocumentHeader>...
         </MatchDocumentHeader>
         <MatchDocumentLine>...
         </MatchDocumentLine>
      </MatchDocument>
   </DataArea>
</LoadResponseMatchDocument>

Site developed and hosted by Datypic, Inc.

Please report errors or comments about this site to contrib@functx.com