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

Recommended Reading:

Definitive XML Schema

 

Web Service Contract Design and Versioning for SOA

 

Advanced XML Applications

 

CancelAcknowledgeInvoiceLedgerEntry

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 unapproved 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.

The purpose of the CancelAcknowledgeInvoiceLedgerEntry is to transmit data to create an unapproved open item in either a payables application or a purchasing application.

The scope of the CancelAcknowledgeInvoiceLedgerEntry indicates that the supplier's invoice has not yet been approved and the invoice is to be used as part of the invoice matching process.

OAGIS has already defined the scenario for invoices that are approved for payment in a separate BOD namely CancelAcknowledgePayable.

Element information

Type: CancelAcknowledgeInvoiceLedgerEntryType

Properties: Global, Qualified, ID: oagis-id-22a41d3eb8c14dba9fd08d83da47c905

Content

Attributes

NameOccTypeDescriptionNotes
releaseID [1..1]NormalizedStringTypeOAGIS Release this BOD Instances belongs or the OAGIS release that the derivative work is based on.from type BusinessObjectDocumentType
versionID [0..1]NormalizedStringTypeIndicates the version of the given BOD definition.from type BusinessObjectDocumentType
systemEnvironmentCode [0..1]SystemEnvironmentCodeContentTypeIndicates 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]LanguageCodeContentTypeIndicates the language that the contents of the BOD is in unless otherwise stated.Default value is "en-US". from type BusinessObjectDocumentType

Sample instance

<CancelAcknowledgeInvoiceLedgerEntry 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>
      <CancelAcknowledge>
         <OriginalApplicationArea>...
         </OriginalApplicationArea>
         <ResponseCriteria>...
         </ResponseCriteria>
      </CancelAcknowledge>
      <InvoiceLedgerEntry>
         <InvoiceLedgerEntryHeader>...
         </InvoiceLedgerEntryHeader>
         <InvoiceLedgerEntryLine>...
         </InvoiceLedgerEntryLine>
      </InvoiceLedgerEntry>
   </DataArea>
</CancelAcknowledgeInvoiceLedgerEntry>

Site developed and hosted by Datypic, Inc.

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