OData Services & Data Model
A single entity carries the open item — including clearing, dunning data, and references to SD.
In FI-AR, the open item is a line of an accounting document (classically BSID/BSAD, today the Universal Journal). The released API for this is called API_OPLACCTGDOCITEMCUBE_SRV and delivers the entity A_OperationalAcctgDocItemCube with 267 properties — including the clearing fields, the dunning fields, and the references to the sales order and invoice. That's exactly why the two optional scopes of this integration are cheap.
The Services
| Role | Service | Entities (Key) | Scope |
|---|---|---|---|
| Open Item | API_OPLACCTGDOCITEMCUBE_SRV (OData V2) | A_OperationalAcctgDocItemCube (CompanyCode, FiscalYear, AccountingDocument, AccountingDocumentItem) | Required |
| Master Data | API_BUSINESS_PARTNER (OData V2) | A_BusinessPartner · A_BusinessPartnerAddress · A_BusinessPartnerBank · A_BusinessPartnerTaxNumber · A_Customer · A_CustomerCompany (Customer, CompanyCode) · A_CustomerDunning (Customer, CompanyCode, DunningArea) | Required |
| Vendor | the same two services | A_Supplier · A_SupplierCompany; the items via FinancialAccountType = 'K' | optional (FI-AP) |
| Sales Order | API_SALES_ORDER_SRV | A_SalesOrder · A_SalesOrderItem · A_SalesOrderHeaderPartner | optional (SD) |
| Invoice | API_BILLING_DOCUMENT_SRV | A_BillingDocument · A_BillingDocumentItem; also delivers the invoice PDF | optional (SD) |
As an alternative for the item, there is API_JOURNALENTRYITEMBASIC_SRV. It keys on a technical ID instead of the document key — for a delta extraction that needs to update on the same key as Bilendo, that's the weaker anchor. In the Public Cloud, CE_API_ACCOUNTING_DOCUMENT_0001 ("Receivable Item – Read", OData V4) is additionally available; it doesn't exist in the On-Premise package, so it's not a common denominator.
Two Things That Don't Exist
No released FI-AR dunning API.
CADUNNING_0001belongs to Contract Accounts Receivable and Payable. One isn't needed anyway: the dunning data is on the customer (A_CustomerDunning: dunning procedure, level, last dunning date, block, dunning recipient) and on the item (DunningLevel,LastDunningDate,DunningArea,DunningKey,DunningBlockingReason).No remaining amount on the item. An item is either open or cleared (
IsCleared). What is a single field in other systems arises here from residual item formation — see the mapping page.
Delta Capability
Unlike Contract Accounts Receivable and Payable, the FI-AR item carries a change timestamp. Three filters, because a clearing doesn't move the timestamp in every system:
| Object | Change Timestamp | Impact on the Delta |
|---|---|---|
A_BusinessPartner | LastChangeDate + LastChangeTime | Filter on the timestamp. |
A_Customer / A_CustomerDunning | none | Carried along via the business partner; the dunning data is a small set and is read in full. |
A_OperationalAcctgDocItemCube | LastChangeDate, AccountingDocumentCreationDate + CreationTime | New items via PostingDate, changes via LastChangeDate, clearings additionally via ClearingDate. |
| Orders / Invoices | LastChangeDate | Secondary, only for numbers referenced by a delivered item. |
All windows start one day before the watermark. The same row appearing twice is harmless — Bilendo updates it.