LoadPurchaseLedgerInvoice schema, example, validation rules, validation stylesheet

LoadPurchaseLedgerInvoice type: LoadPurchaseLedgerInvoice

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 LoadPurchaseLedgerInvoice is to transmit data to create an unapproved open item in either a payables application or a purchasing application. The scope of the LoadPurchaseLedgerInvoice 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 LoadPayable.

LoadPurchaseLedgerInvoice extends: BusinessObjectDocument
Structure:
Elements:
Name Type Description
DataArea LoadPurchaseLedgerInvoiceDataArea

Is where the information that the BOD message carries is provided, in this case LoadPurchaseLedgerInvoice. The information consists of a Verb and one or more Nouns. The verb (Load) indicates the action to be performed on the Noun (PurchaseLedgerInvoice).

LoadPurchaseLedgerInvoiceDataArea extends: DataArea
Structure:
Elements:
Name Type Description
Load reference
PurchaseLedgerInvoice reference

LoadPurchaseLedgerInvoice Scenario Diagram

Load schema

Load type: Load

This verb is used to initiate the adding of a document or data entity to another business application. Generally this verb is used when maintenance to the document will then pass to the receiving application permanently. An example of this is Load Payable or Load Receivable, where once the request is processed, the sending application has no direct control over the document or entity again.

Load extends: Verb
Structure:
Elements:
Name Type Description
AdjustExpression Expression

The XPath expression detailing a field that is to be adjusted, based on the specific semantics on the Noun. In cases of LedgerBudget loading, adjust adjusts the budget amount by the corresponding specified amount.

ReplaceExpression Expression

The XPath expression detailing a field that is to have its value replaced by the corresponding specified amount.

PurchaseLedgerInvoice schema

PurchaseLedgerInvoice type: PurchaseLedgerInvoice

A PurchaseLedgerInvoice represents a not yet approved for payment purchase ledger invoice or debit memo. A PurchaseLedgerInvoice uses an InvoiceReference to reference the original suppliers invoice.

Header type: PurchaseLedgerInvoiceHeader

Line type: PurchaseLedgerInvoiceLine

PurchaseLedgerInvoice extends: FinancialDocument

A purchase ledger invoice or debit memo that has not yet been approvedfor payment.

Deprecation of VOUCHER, ORIGREF: From OAGIS 7.2.1: ORIGREF is the link that ties back to a sub ledger transaction entry ID. It is the identifier of an original transaction or document. For example, it could be the receipt or the summarized inventory activity. This is the singular field that refers to an audit record. Together with the Sender information, the ORIGREF is part of the referencing system, which will enable drill back audit trail functionality. PN: The ORIGREF field represents the voucher or unapproved invoice identifier. VOUCHER is the internal identifier associated with the external supplier’s invoice. REMITTANCE refers to a reference identifier to print on remittance advice, for example, supplier invoice number. In OAGIS 8: All of these can be accomplished with an InvoiceReference. I never understood why there was an ORIGREF, a VOUCHER and a REMITTANCE. I left REMITTANCE field in until the RemittanceAdvice BOD is part of OAGIS. Deprecation of USERID: An AccountingContact semantic has been added and is used within the CustomerParty instance of the PurchaseLedgerInvoice.

Structure:

PurchaseLedgerInvoiceHeader extends: FinancialDocumentHeader
Structure:
Elements:
Name Type Description
UserArea reference

PurchaseLedgerInvoiceLine extends: FinancialDocumentLine
Structure:
Elements:
Name Type Description
UserArea reference

Verb Common Files

Verb.xsd schema

AcknowledgableVerb extends: ConfirmableVerb
Structure:
Attributes:
Name Type Usage Description
acknowledge AcknowledgementType

AcknowledgementType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

ConfirmableVerb extends: Verb
Structure:
Attributes:
Name Type Usage Description
confirm ConfirmType

ConfirmType restricts: xs:NMTOKEN
Enumerations:
Always
Never
OnChange

Expression restricts: xs:string

ExpressionCriteria
Structure:
Elements:
Name Type Description
SelectExpression Expression

Allows the 1-n number of selection expressions for the information to be returned.

Attributes:
Name Type Usage Description
expressionLanguage xs:string optional

RequestVerb extends: ConfirmableVerb
Structure:
Elements:
Name Type Description
ReturnCriteria

Allows the initator of the BOD to indicate the information (down to the field level) that is requested to be returned. The expressionLanguage indicates the expression language being used.

VerbBase.xsd schema

Verb type: Verb

Verb
Structure:

Noun Common Files

FinancialDocument.xsd schema

FinancialDocument extends: Document
Structure:

FinancialDocumentHeader extends: DocumentHeader
Structure:
Elements:
Name Type Description
AccountingDate DateTimeAny

Is the date that is used to determine the accounting period the transaction is posted within. It is also known as the effective or post date.

AccountingPeriod Period

Is the accounting period the document is to post within. The period is within a fiscal year to which a business transaction is assigned.

AccountingYear Year

Is the accounting year the document is to post within. Generally a period of 12 months for which the company regularly has to create financial statements. A fiscal year may correspond to a calendar year.

EntryCreator UserId

The user’s enterprise-wide identifier. It is also known as the user code. SYNONYMS: Operator ID

GLSourceEntity GLEntity

The primary balancing segment of the G/L Account structure. P and L statements are required at this level. A G/L entity is the smallest organizational unit for which individual financial statements must be drawn up according to relevant commercial law.

Synonyms: Business Unit, Fund, General Ledger Company, Joint Venture, Non-Profit Association Name

LedgerId LedgerId

Identifies the Ledger to which this transaction entry is to be inserted

Parties reference
PaymentMethod PaymentMethod

Describes payment method on an invoice, for example, drafts, BACS, checks, or letter of credit.

Standard values from ISO 10962:2001?

Securities and related financial instruments - Classification of Financial Instruments (CFI code)

PaymentTerms reference

Identifies the payment terms for an Order or Invoice. Supports the abiility to specify an absolute due date, a number of days from a start daye, a percent discount or an absolute discount. A common term like "Net30Days" is explicitly code as either a calculated DueDateTime or a PaymentTermsDateTime and NumberOfDays.

Tax reference

Identifies a type of tax on order related BODs

Total Amounts

FinancialDocumentLine extends: DocumentLine
Structure:
Elements:
Name Type Description
TaxBaseAmount Amounts

Document.xsd schema

Document extends: Noun
Structure:
Elements:
Name Type Description
Header reference
Line reference

DocumentHeader
Structure:
Elements:
Name Type Description
Attachments reference
Description Description

Is a description of the document.

Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description..

DocumentDateTime DateTime

Is the date and time the document was last created. This is not the date and time that the BOD message instance was created.

DocumentIds reference

Is the identifier for the document. It is possible to carry the document identifier for the other Parties. These DocumentIds are referenced by sematic names.

Is the identifier for the document. It is possible to carry the document identifier for the other Parties. These DocumentIds are referenced by sematic names.

DocumentReferences reference
LastModificationDateTime DateTime

Is the date and time the document was last modified. This is not the date and time that the BOD message was sent.

Note Note

Is Note for the document in which it is contained.

A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified.

Status reference

DocumentLine
Structure:
Elements:
Name Type Description
LineNumber LineNumber

Is the Line Number of the given Line Coponent within the document. LineNumbers are assigned by the sending system.

Identifies the instance of a Line within a given document.

DocumentOrderHeader restricts: DocumentHeader
Structure:
Elements:
Name Type Description
Attachments reference
Description Description

Is a description of the document.

Free-form text description of the Noun or Componenet in which the description occurs. The lang attribute indicates the language the description is in. Owner inidcates the user or entity that provided teh description..

DocumentDateTime DateTime

Is the date and time the document was last created. This is not the date and time that the BOD message instance was created.

DocumentIds reference

Is the identifier for the document. It is possible to carry the document identifier for the other Parties. These DocumentIds are referenced by sematic names.

Is the identifier for the document. It is possible to carry the document identifier for the other Parties. These DocumentIds are referenced by sematic names.

DocumentReferences reference
LastModificationDateTime DateTime

Is the date and time the document was last modified. This is not the date and time that the BOD message was sent.

Note Note

Is Note for the document in which it is contained.

A free form note. The lang attribute identifies the language that the note is in. The author identifies the author of the note. The enrtyDate indicates the date the note was entered or last modified.