LoadReceivable schema, example, validation rules, validation stylesheet

LoadReceivable type: LoadReceivable

The purpose of the LoadReceiveable is to transmit data to create a receivable open item in a receivable application from the billing information generated in an order management application. The LoadReceiveable may also update the General Ledger, depending on the specific architecture of the accounting application. The scope of the LoadReceiveable is to create a BOD to recognize customer obligation (accounts receivable asset). Specific transactions include: 1. Sales Invoice 2. Credit Memo 3. Debit Memo 4. Charge Back The LoadReceiveable may also be used for transaction that do not originate from an order management application. The following two models illustrate that the LoadReceiveable may, in some cases, be adequate to update the financial applications, i.e., Receivables and General Ledger, and in other cases, will also require the PostJournal Business Object Document (BOD) to assure the General Ledger account balances are updated.

In the model above, the receivable application is a sub-ledger of the general ledger. Updates to G/L balances occur via the receivables module, therefore the Load Receivable contains both receivable and general ledger transaction information.

This other model illustrates the environment that sometime exists when General Ledger updates occur directly from the Order Management application. The reconciliation between the receivable and general ledger is a function within the financial applications and not of the integration space. This model allows the G/L balances to be updated in either detail or summarized form. The scope of the role of the receivable application includes functions such as: · Allowing Cash Application · Dunning · Dispute management

LoadReceivable extends: BusinessObjectDocument
Structure:
Elements:
Name Type Description
DataArea LoadReceivableDataArea

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

LoadReceivableDataArea extends: DataArea
Structure:
Elements:
Name Type Description
Load reference
Receivable reference

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

Receivable schema

Receivable type: Receivable

Receivable is a transaction representing an invoice, credit memo or debit memo to a customer. A receivable is an open (unpaid) item in the Accounts Receivable ledger.

Header type: ReceivableHeader

Information that applies to the entire receivable document, including totals, invoice identifier, and description.

Line type: ReceivableLine

Line associated with the receivable document. Can be an invoice line.

Receivable extends: FinancialDocument
Structure:

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

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