In this blog i will be discussing about the AVL functionality in SAP Central Finance. AVL stands for “Accounting View of Logistics information”.
Accounting View of Logistics (AVL) is Central Finance-specific functionality in which logistical information is loaded and replicated from SAP source systems into Central Finance and stored in separate tables.
- AVL provides logistical insight in Central Finance without the need for extensive configuration and master data, customisation of data, or custom programs and tables
- AVL helps to bridge the data gap between Finance and Logistics without the need for a custom approach or extensive configuration and helps in driving the reporting strategy
- AVL also enables more detailed profitability analysis through the inclusion of partner functions such as Ship-to, Sold-to, and Bill-to
- AVL facilitates Central Finance’s ability to link financial documents to their associated Purchase Orders, Sales Orders, Supplier Invoices, and Customer Invoices
- Reporting integration across SD, MM, FI and CO data sets
- Revenue Accounting
- Central Purchase Order Accrual
- Advanced Compliance Reporting (ACR for Tax Reporting)
- Basis on which predictive accounting can be achieved via Central Finance
- The AVL is only supported for source systems of SAP ERP 6.0 EhP3 and higher, including SAP S/4HANA systems. (Replication of purchase orders is only supported for source systems of SAP ERP 6.0 EhP4 and higher.)
- Only one client per source system is supported in one SLT configuration.
- Data in the AVL (except purchasing documents and data for which a mapping relationship has been maintained, for example CO-PA or WBS data) is not validated against the Customizing nor the master data in the Central Finance system, which is different from General Ledger entries in the Central Finance processing.
What is Replicated?
AVL Tables in SAP S/4HANA
The logistical data from the source system tables are brought into the Central Finance system and are accessible for data analysis and reporting through a series of “CFIN_AV” tables
AIF Interfaces available
SLT Tables & set up – EKKO, RBKP, VBAK and VBRK
Now i will share end to end example of Sales order data replication and how it looks in CFIN AVL tables
Sales order created in SAP ECC (Order # 5)
In ECC, VBAK table entry is visible
Replication happens via SLT (VBLEN = 5)
Item data visible in AIF
Now we move to SAP S/4HANA 2020 and will see the data in AVL specific tables
CFIN_AV_SO_ROOT – Header Data table
CFIN_AV_SO_ITEM – Item Data table
CFIN_AV_SO_PART – Partner Data Table
CFIN_AV_SO_BIZ – Business Data Table
Now the Sales order is Delivered & billed in ECC
Document Flow is below
Billing Document gets replicated to CFIN (VBELN = 90000001)
Interface – AV_CI (Customer Invoice)
Data in CFIN
CFIN_AV_CI_ROOT – Billing Document Header Data
CFIN_AV_CI_ITEM – Billing Document Item Data
CFIN_AV_CI_PART – Billing Document Partner Data
Similarly it works for PO data and data of PO and Vendor invoice is replicated to below CFIN Tables
|Replicated Business Object||Central Finance Table||Source System Table|
|AVL Purchasing Document||CFIN_AV_PO_ACC||EKKN|