SAP
SAP ALV Report Basic Operations: Sort, Filter, Subtotal, and Export
A practical guide to working with SAP ALV reports: setting selection criteria, sorting and filtering rows, creating subtotals, saving layouts, and exporting results safely.
SAP ALV reports present ABAP report output in a structured list or grid. The report program determines the available data and columns, while the ALV interface provides practical operations such as sorting, filtering, subtotals, layout variants, and export.
The safest workflow is to validate the selection criteria first, confirm the result set, apply display changes, and then save or export the final view. For the selection-screen stage, see SAP report execution and selection screen basics. For the distinction between delivered and custom reporting, see SAP standard vs. custom reports.
Start with a controlled report run
Define the reporting question
Write down the business question before opening the report. Examples include identifying open items for a company code, reviewing material movements for a period, or comparing sales documents by organizational unit. This determines which fields belong in the selection criteria and which columns matter in the result.
Use the narrowest meaningful date range, organizational scope, and status criteria. A focused first run makes it easier to identify incorrect filters and reduces unnecessary database and application-server work.
Validate the selection screen
Check required fields, default values, multiple selections, ranges, and exclusion indicators. Pay particular attention to date semantics: a posting date, document date, creation date, and clearing date answer different questions.
Save the selection variant when the same operational scope is used repeatedly. Give it a descriptive name and document its purpose so another operator can reproduce the run without guessing.
Check the initial result
Review the row count, key identifiers, totals, and a few representative records before changing the layout. Confirm that the first and last records fit the intended date and organizational scope. If the result is empty or unexpectedly large, return to the selection screen and investigate the criteria before continuing.
Use core ALV grid operations
Sort by one or more columns
Select a column and apply ascending or descending sort. A useful sort order usually begins with the main grouping field, such as company code, plant, customer, vendor, material, or document number, followed by a date or amount field.
For a multi-level review, apply the primary sort first and then add secondary sort criteria. Inspect the resulting order after each change. Numeric, date, and character values should appear in an order that matches their data type and business meaning.
Filter the displayed rows
Use a filter when the report has already returned the correct population and you need to focus the visible rows. Filter on stable values such as status, company code, plant, purchasing group, or document type. Combine filters deliberately and review the active-filter indicators before interpreting totals.
A display filter changes what is visible in the ALV result. It does not automatically change the report selection or recalculate the underlying business data. Remove or reset filters when handing the report to another user.
Resize, hide, and arrange columns
Resize columns to expose identifiers and important values without truncating them. Move high-value columns toward the left and place explanatory or technical fields farther right. Hide columns that distract from the current review while retaining the ability to restore them through the layout functions.
Keep a visible identifier in operational reports. For example, a document number, material, business partner, or accounting reference provides the traceability needed to investigate an individual row.
Freeze the working view
After arranging columns, sorting, and filtering, save the layout as a user-specific or shared variant when the report provides that option. Use a name that describes the business purpose, such as a monthly exception review or plant inventory analysis.
Before sharing a layout, verify that it contains no accidental personal filters or temporary test values. Shared variants should support a repeatable process rather than preserve one operator's investigation state.
Create subtotals and totals
Group records with a meaningful sort
Subtotals depend on grouping. Sort the report by the field that defines the group, then activate the subtotal function for the amount or quantity column. A subtotal by plant, company code, customer, or material can make a long list easier to review.
Choose a grouping field that reflects the decision being made. A subtotal by document number may be useful for line-item reconciliation, while a subtotal by organizational unit is better for management review.
Validate aggregation rules
Confirm the unit, currency, and sign of every aggregated value. Quantities with different units require careful interpretation, and amounts in different currencies should not be combined without an appropriate currency context.
Compare a few subtotal groups with the underlying rows. This catches hidden filters, duplicate-looking records, reversed signs, and grouping choices that do not match the business question.
Distinguish display totals from business reconciliation
ALV totals and subtotals summarize the rows returned to the report view. A reconciliation may require additional checks against source documents, accounting balances, inventory movements, or an approved control total.
Record the selection criteria, active filters, layout, and extraction time when the output supports a financial, inventory, or compliance decision. This creates an operational trail for later review.
Save and reuse ALV layouts
A layout is useful when it preserves a repeatable presentation: selected columns, order, widths, sorting, filtering, and aggregation. Save a personal layout for recurring work and use a shared layout only when its scope and ownership are clear.
Use descriptive names and a short usage note. Include the report purpose, key grouping field, and expected audience. Review saved layouts after report changes to ensure that the visible columns still support the process.
Avoid treating a layout as a data extract. The report selection, authorization context, execution time, and source data remain important even when the same layout is reused.
Export ALV results safely
Confirm the final selection, filters, sort order, subtotals, and visible columns before exporting. Choose a file format that preserves the required values and structure, then open the exported file and verify row counts, headers, dates, decimal separators, negative values, and totals.
Protect exported files according to the sensitivity of the data. Store them in an approved location, limit access, and remove temporary copies when the retention process allows it. See SAP report export to Excel and PDF basics for a focused export workflow.
For reports built with SAP Query, the report definition and query configuration can affect available fields and output behavior. See SAP Query, SQVI, and SQ01 basics when the report is based on that toolset.
Troubleshoot unexpected ALV results
Empty output
Review mandatory fields, date ranges, organizational restrictions, status values, and exclusion indicators. Check whether a saved selection variant contains an old restriction. Run a small, known-valid scope to separate selection logic from authorization or data availability issues.
Too many rows
Narrow the date range and organizational scope, then add business-relevant status or document-type criteria. Use a background execution path when the report supports it and the result is expected to be large. Avoid repeatedly launching broad foreground runs during peak activity.
Missing columns or actions
Check the current layout and reset it when necessary. Some functions are available only when the report supplies the relevant field or capability. If multiple users see the same missing field, record the report name, selection values, user context, and expected column for the application owner.
Incorrect totals
Inspect active filters, duplicate-looking rows, units, currencies, signs, and aggregation levels. Compare the visible rows with an independent control total where the process requires reconciliation. Capture the exact layout and selection details before escalating the issue.
Slow execution or display
Reduce the initial selection scope and avoid unnecessary columns or unrestricted date ranges. Separate database retrieval time from ALV rendering time by noting when execution starts and when the result becomes usable. Recurring performance issues belong in a structured reporting-troubleshooting process; see SAP reporting troubleshooting basics.
Use an operational ALV checklist
- Define the business question and required population.
- Check dates, organizational fields, statuses, ranges, and exclusions.
- Execute a controlled run and validate representative rows.
- Apply sorting, filtering, column arrangement, and subtotals.
- Confirm totals, units, currencies, and active filters.
- Save a clearly named layout when the view is repeatable.
- Verify the exported file and protect it according to data sensitivity.
- Record selection criteria and layout details for important decisions.
An ALV report becomes reliable operational evidence when its selection scope, visible transformations, totals, and export are all understood. The interface is most effective when display operations support a defined reporting question rather than replace one.