SD Report Custom development ALV report

Billing Item Detail Report with Pricing Conditions and Quantities

Short answer: An ALV report that lists billing documents item by item, with pricing conditions such as discounts, freight and bonus in separate columns, the quantity in both the sales unit and an alternative unit, and the accounting document and sales order on the same row. Sales and accounting teams no longer merge invoice lists, condition dumps and accounting entries in Excel every month.

Estimated effort
M · 5–8 working days
System
ECC and S/4HANA
Tables
10
Scope
Global
Built by
NeKuDos Teknoloji
Last updated

Why is the standard not enough?

VF05N lists billing documents but does not show condition values; conditions can only be seen document by document or by reading tables. KE24 shows profitability line items, but its value fields depend on the CO-PA setup and it does not carry an alternative unit of measure. The custom report takes the mapping of condition types to columns from a setup table, converts the quantity into the requested unit with the material's unit conversion and links the accounting document to the billing item.

Who uses it? Sales operations and billing teams, sales accounting, controllers and sales managers.

Closest standard alternatives

  • VF05N List of Billing Documents. Lists billing documents; does not show condition values or the quantity in an alternative unit.
  • KE24 Line Item Display – Actual Data (CO-PA). Shows profitability line items with value fields; columns depend on the CO-PA setup and no unit conversion is done.
  • VF03 Display Billing Document. Shows the conditions of a single invoice item by item; gives no list.

Tables used

The tables the report reads and their join fields. ECC and S/4HANA differences are marked separately.

TableRoleJoinSystem
VBRKBilling Document HeaderBilling header: billing type, date, payer, document currency, condition number (driving table)—ECC + S/4
VBRPBilling Document: Item DataBilling items: material, quantity, unit, weight, net value, order and delivery referenceVBRP-VBELN = VBRK-VBELNECC + S/4
PRCD_ELEMENTSPricing Elements (Document Conditions)Pricing conditions per item (S/4HANA)PRCD_ELEMENTS-KNUMV = VBRK-KNUMV AND KPOSN = VBRP-POSNRS/4HANA only
KONVConditions (Transaction Data)Pricing conditions per item (ECC)KONV-KNUMV = VBRK-KNUMV AND KPOSN = VBRP-POSNRECC only
MARMUnits of Measure for MaterialAlternative unit of measure conversion factorsMARM-MATNR = VBRP-MATNRECC + S/4
BKPFAccounting Document HeaderAccounting document created from the invoiceBKPF-AWTYP = 'VBRK' AND BKPF-AWKEY = VBRK-VBELNECC + S/4
ACDOCAUniversal Journal Entry Line ItemsAccounting amount and profit center (S/4HANA, optional)ACDOCA-RBUKRS = BKPF-BUKRS AND BELNR = BKPF-BELNR AND GJAHR = BKPF-GJAHRS/4HANA only
VBAKSales Document HeaderOrder type and order dateVBAK-VBELN = VBRP-AUBELECC + S/4
VBKDSales Document: Business DataPayment terms and incotermsVBKD-VBELN = VBRP-AUBELECC + S/4
KNA1Customer Master (General Section)Customer nameKNA1-KUNNR = VBRK-KUNAGECC + S/4

S/4HANA notes

  • KONV → PRCD_ELEMENTS: In S/4HANA document conditions are stored in PRCD_ELEMENTS; custom code reading KONV must be adapted.

BAPIs and functions used

  • UNIT_CONVERSION_SIMPLEConvert Unit of Measure (T006). Converts between weight and volume units

Selection screen parameters

ParameterDescriptionTypeReference fieldRequiredExample
S_VKORGSales organizationRange / multipleVBRK-VKORGYes1000
S_FKDATBilling dateRange / multipleVBRK-FKDATYes01.10.2026 – 31.10.2026
S_FKARTBilling typeRange / multipleVBRK-FKARTNoF2
S_KUNAGSold-to partyRange / multipleVBRK-KUNAGNo200145
S_MATNRMaterialRange / multipleVBRP-MATNRNoFG-10020
P_ALTMEAlternative unit of measureSingle valueMARM-MEINHNoKG
P_NOCANExclude cancelled and cancellation documentsCheckbox—NoX

Output columns

#ColumnSource
1Billing documentVBRK-VBELN
2ItemVBRP-POSNR
3Billing dateVBRK-FKDAT
4Customer nameKNA1-NAME1
5MaterialVBRP-MATNR
6Billed quantityVBRP-FKIMG
7Sales unitVBRP-VRKME
8Quantity in alternative unitCalculated FKLMG × MARM-UMREN / MARM-UMREZ (for the selected unit)
9List price valueCalculated Sum of KWERT for the conditions mapped to the 'list price' column during setup
10DiscountsCalculated Sum of KWERT for the conditions mapped to the discount column
11FreightCalculated Sum of KWERT for the conditions mapped to the freight column
12Bonus accrualCalculated Sum of KWERT for the conditions mapped to the bonus column
13Net valueVBRP-NETWR
14CurrencyVBRK-WAERK
15Accounting documentBKPF-BELNR
16Sales orderVBRP-AUBEL

Sample output

Billing documentItemBilling dateCustomer nameMaterialBilled quantitySales unitQuantity in alternative unitList price valueDiscountsFreightBonus accrualNet valueCurrencyAccounting documentSales order
900512311010/06/2026Örnek Ambalaj A.Ş.FG-100201,200KAR9,60054,000-4,3201,250-1,08049,930TRY180002341110004512
900512312010/06/2026Örnek Ambalaj A.Ş.FG-10035800KAR5,12031,200-2,496830-62428,910TRY180002341110004512
900512441010/07/2026Demo Gıda Ltd.FG-20110450KOL6,75040,50001,900-81041,590TRY180002346010004530
900513021010/09/2026Deneme Kimya San. A.Ş.FG-3000820TO20,00018,400-920600018,080EUR180002351710004588
A view built with fictional sample data; not real system data.

How does the report work?

  1. VBRK is read by the sales organization, billing date and billing type entered on the selection screen; cancelled documents (FKSTO) and cancellation invoices can be excluded.
  2. Items come from VBRP: material, billed quantity (FKIMG, VRKME), quantity in base unit (FKLMG), net/gross weight, net value, sales order reference (AUBEL/AUPOS) and delivery reference (VGBEL).
  3. Pricing conditions are read in one pass from PRCD_ELEMENTS in S/4HANA (KONV in ECC) using VBRK-KNUMV and the item number. A setup table maps each condition type to a report column (for example list price, customer discount, campaign discount, freight, bonus accrual); unmapped conditions are summed in an “other” column. Inactive conditions (KINAK) are left out.
  4. For the alternative unit, the conversion factors in MARM (UMREZ/UMREN) are used; conversions between weight units are done with UNIT_CONVERSION_SIMPLE. If the material has no conversion, the cell stays empty and the row is flagged.
  5. The accounting document is found in BKPF with AWTYP = ‘VBRK’ and AWKEY = billing document number; in S/4HANA the amount and profit center can be read from ACDOCA.
  6. Order type, customer order date and payment terms are added from VBAK/VBKD. The ALV shows the condition columns with totals; clicking the billing or order number opens the document.

Performance notes

Read conditions in one pass with FOR ALL ENTRIES or a JOIN on the KNUMV list of the selected invoices instead of one SELECT per invoice. One month is typically hundreds of thousands of condition rows; for month-end, run the report in the background and save the ALV layout. In S/4HANA, aggregating PRCD_ELEMENTS and ACDOCA in the database through CDS or AMDP can be considered.

Features

  • ALV list (sort, filter, subtotals)
  • User-specific layout variants Condition columns and totals can be saved as a user layout.
  • Double-click drill-down to the document Click through to the billing document, sales order and accounting document.
  • Export to Excel
  • Runs as a background job The month-end extract can be produced in the background and kept with its ALV layout.

Authorization objects

  • V_VBRK_VKOBilling document display by sales organization
  • V_VBRK_FKABilling document display by billing type
  • F_BKPF_BUKCompany code authorization for the accounting document column

Frequently asked questions

Does the report need to change when a new condition type is added?

No. The mapping of condition types to report columns is kept in a setup table; mapping the new condition type to a column is enough. Unmapped conditions appear in the 'other' column, so no amount is lost.

Where does the alternative unit of measure come from?

From the unit conversions in the material master (MARM). If the selected unit is not defined for the material and both units are weight units, the standard unit conversion is used; otherwise the cell stays empty and the row is flagged.

What is read instead of KONV in S/4HANA?

In S/4HANA pricing conditions are stored in PRCD_ELEMENTS; the report reads the right table for the release. On the accounting side the BKPF link stays the same, and ACDOCA can be used for the amount and profit center.

Related reports

SD Report Custom ALV report

Billing Documents Not Posted to Accounting Report

A custom ALV report that lists billing documents which exist in SD but have no accounting document yet, with the reason code, age and amount. At …

VBRK · VBRP · BKPF · KNA1

Let us build this report for your system

Briefly describe your system and expectations. We will clarify the scope and come back with an effort and price quote.

Related report: Billing Item Detail Report with Pricing Conditions and Quantities