Onibex - SAP Volumetry Estimation Manual
Overview
This guide explains how to fill in the SAP Volume Estimation Tool — an Excel spreadsheet used to estimate the document volume your SAP system processes across the main business processes: Sales, Procurement, Production, Finance, and Materials.
The tool automatically calculates key metrics such as the average number of items per document, total documents processed, and a T-shirt size that summarizes the relative workload of your SAP instance.
Color Legend
The spreadsheet uses colors to indicate what each cell type means:
| Color | Meaning |
|---|---|
| Dark blue | Column headers — do not edit |
| Light blue | Data entry cells — enter your SAP record counts here |
| Green | Result cells - not editable, show results of the volumetry estimation |
| White / Gray | Auto-calculated cells — do not edit |
SAP Tables Reference
The main grid is organized by business process. Each process has one or two associated SAP tables:
| Business Process | SAP Table | Description | Recommended Date Field |
|---|---|---|---|
| Sales | YBAK | Sales order headers | ERDAT |
| Sales | YBAP | Sales order line items | ERDAT |
| Procurement | EKKO | Purchase order headers | AEDAT |
| Procurement | EKPO | Purchase order line items | AEDAT |
| Production | AFKO | Production order headers | ERDAT |
| Production | AFPO | Production order line items / components | ERDAT |
| Finance | BKPF | Accounting document headers | BUDAT |
| Finance | BSEG | Accounting document line items | BUDAT |
| Materials | MSEG | Material movement segments | BUDAT |
Querying Record Counts in SAP
To get the record count for each table you need to use transaction SE16 or SE16N in SAP. Repeat this process for each table and each year (2023, 2024, 2025).
Step 1 — Open the transaction
Log in to your SAP system (production client or the relevant environment). In the transaction bar, type SE16 or SE16N and press Enter.
Step 2 — Enter the table name and apply date filter
Follow these steps once inside SE16 / SE16N:
| # | Field | Action |
|---|---|---|
| 1 | Table Name | Type the table name (e.g. EKKO) and press Enter. |
| 2 | Date field | Locate the date field for that table (see SAP Tables Reference above) and enter the desired year range. |
| 3 | Date range | Enter 01.01.YYYY to 31.12.YYYY, replacing YYYY with the target year (2023, 2024, or 2025). |
| 4 | Maximum No. of Hits | Set this to 0 (unlimited) or a very large number such as 9999999 to get the real count. |
| 5 | Execute | Press F8 or click the Execute button (green triangle with a clock). |
| 6 | Read the count | The SAP status bar at the bottom will show "X entries found". That number is your record count. |
Filling In the Spreadsheet
Main grid — rows 2025, 2024, 2023
Once you have the record count from SAP for a given table and year, enter it in the corresponding light-blue cell:
| Row | Year to capture | Value to enter |
|---|---|---|
| 2025 | January–December 2025 (or year-to-date if the year is ongoing) | Record count returned by SE16 / SE16N for that table and year |
| 2024 | Full year January–December 2024 | Record count returned by SE16 / SE16N for that table and year |
| 2023 | Full year January–December 2023 | Record count returned by SE16 / SE16N for that table and year |
Example: You open SE16N → table EKKO → filter AEDAT from 01.01.2024 to 31.12.2024 → result: 15,430 entries found. Go to the Excel file, row 2024, column Procurement (EKKO), and enter 15430. Repeat for EKPO using the same year.
Last Year Average Items per Document
This row is calculated automatically by the spreadsheet. Do not edit it manually. It represents the average number of line items per header document for the most recent complete year.
Working days and hours (center section)
These two cells are editable. Enter the values that reflect how many days per month and hours per day your SAP system is actively running transactions. The tool uses these values to calculate document throughput per hour.
| Field | Default | What to enter |
|---|---|---|
| Working days per month | 22 | Number of days per month your SAP system is active (e.g. 20 if weekends and holidays are excluded). |
| Working hours per day | 12 | Number of hours per day during which transactions are processed (e.g. 8 for a single shift, 24 for a round-the-clock operation). |
Growth and T-shirt size (right section)
This section displays the final estimation output. All cells here are calculated automatically — do not edit them:
| Field | Description |
|---|---|
| Calculated Estimated Growth | Growth rate derived automatically from the historical data you entered. |
| Manually Adjusted Growth | Displays an adjusted growth result calculated by the tool. Read-only. |
| T-shirt size | Final result: XS, S, M, L, or XL based on the estimated total volume. Used to size projects, migrations, or integrations. |
Recommended Workflow
Follow this sequence to complete the tool efficiently:
| # | Activity | Detail |
|---|---|---|
| 1 | Confirm SAP access | Ensure you have read access to the productive SAP system (PRD) and can run SE16 or SE16N. |
| 2 | Query table by table | For each table (YBAK, YBAP, EKKO, EKPO, AFKO, AFPO, BKPF, BSEG, MSEG), run SE16 / SE16N filtered by year. |
| 3 | Record the results | Note down each count before switching to the spreadsheet. |
| 4 | Enter data in Excel | Fill in the light-blue cells, year by year and process by process. |
| 5 | Verify consistency | Line-item tables (e.g. EKPO) must always have more records than their corresponding header tables (e.g. EKKO). If not, recheck the date filter. |
| 6 | Set working days and hours | In the center section, enter the number of days per month and hours per day your SAP system actively processes transactions. |
| 7 | Review T-shirt size | The final result appears automatically in the T-shirt size cell once all light-blue and green cells are filled in. |
Troubleshooting
SAP shows exactly "500 entries" or "1000 entries"
You have reached the Maximum No. of Hits limit. Go back to the SE16 / SE16N selection screen, set Maximum No. of Hits to 0 (unlimited) or a very large number, and execute again.
The date field is not visible in the filter screen
In SE16, click Settings to enable additional filter fields. In SE16N, the date field appears in the selection criteria section — scroll down if needed.
No access to SE16 / SE16N
Contact your SAP BASIS administrator to request display-only access to SE16 or SE16N. Alternatively, ask them to run the queries and share the counts with you.
Line-item table has fewer records than its header table
This usually indicates a wrong date field or date range. Verify you are using the recommended date field (see SAP Tables Reference) and that the range is identical to the one used for the header table.
T-shirt size shows an unexpected result
Check that all light-blue cells for the most recent complete year (typically 2024) contain data. A blank column can skew the calculated average and distort the final result.
Related Articles
SmartGateway Configuration - Creating SAP Connectors
SmartGateway Configuration Manual Creating SAP Connectors on the SmartGateway Platform Note Each account and user will have the ability to create SAP connectors in their designated environment. The following will show how a SAP Connector is created ...Onibex Clickhouse Sink Connector
The Onibex Clickhouse JDBC connector sends real-time data from Kafka to write to Tables based on the topics subscription. It is possible to achieve idempotent writes with upserts. Auto-creation of tables and auto-evolution is supported using the ...SAP BTP - Infrastructure Requirements
Overview This document defines the minimum infrastructure sizing required to execute the BVC on SAP Business Technology Platform (BTP) using Kyma runtime environments. Three independent environments must be provisioned: One Connect Smart Gateway — ...One Connect - Pricing Manual
How One Connect Pricing Works One Connect uses a T-shirt sizing model: Small, Medium, and Large. Each component of the solution is quoted independently based on the size that best matches the data volume, processing load, or consumption of the ...Onibex Snowflake Sink Connector Benefits
The Onibex Snowflake Sink Connector enables real-time data ingestion from Confluent Platform and Confluent Cloud into topic-based subscription tables in Snowflake. It supports idempotent writes through elevator logic and allows for automatic table ...