In the context of financial integration transaction processing, a business object is a logistic entity or event such as an item, a purchase order, a business partner, or a warehouse issue.

A characteristic of the business object that can be used to map the integration transaction to specific ledger accounts and dimensions. For example, the Sales Order business object has the Series attribute and the Sales Order Type attribute, among others.

The unique code that identifies a specific business object. For example, the business object ID of a Purchase Order business object is the purchase order number.

A transaction identification more detailed than the business object, for example, a receipt number or an order number. You can use the reference during reconciliation to match transactions if the business object alone does not provide enough information, for example, during GRNI reconciliation.

Currency result caused by fluctuations in the exchange rate, for example, if the exchange rate between the invoice currency and your home currency differs between the invoice date and the payment date.

An internal purchase cost that can be booked on a non-finalized project. The transaction costs are posted separately if direct delivery occurs. If a delivery is made through a project warehouse, the expense tax is included in the valuation price or fixed transfer price (FTP).

A currency system in which all financial companies and logistic companies that are related to each other in the enterprise structure model use the same two or three home currencies. All transactions are registered in all the home currencies.

Currency rates are defined between the transaction currencies and all home currencies. Transaction amounts are converted directly from the transaction currency into the home currencies.

Represents a type of Operations Management transaction for the purpose of mapping and posting the integration transactions to Financials and for financial reconciliation.

The integration document types supplied by LN each have the corresponding business object attached to them. For example, the integration document types for the various sales order transactions have the Sales Order business object linked to them.

A scheme that defines the ledger accounts and dimensions to which the integration transactions are posted.

A collective name for the non-financial LN packages. Operations Management represents all the logistic LN packages.

A general area on which you can perform reconciliation, for example, Inventory, Production Order WIP, Interim Costs, and Invoice Accrual. The reconciliation area and subarea together form a reconciliation group which represents a group of integration ledger accounts.

A property of a logistic transaction that you can use to trace the transaction for reconciliation. The reconciliation elements correspond with the mapping elements of the business objects.

Represents a group of integration ledger accounts on which you can perform reconciliation. A reconciliation group consists of the combination of a reconciliation area and a subarea, for example, Invoice Accrual/ Purchase Order WIP.

A generated code that is attached to the debit posting and the credit posting of an integration transaction. You can use the reference link to match the postings on interim accounts that you cannot match business object ID because they belong to different business objects, for example, a Purchase Receipt and an Inventory Transaction.