SAP IDoc Database Growth Calculator
IDoc tables grow quietly until a Basis admin notices a database that is far larger than the business data justifies. This calculator turns daily IDoc volume, segment counts and retention into a storage figure you can use to justify archiving or a shorter online retention.
Your numbers
Total inbound plus outbound IDocs created per day across all message types.
An ORDERS IDoc with 5 items is often 20 to 40 segments, a MATMAS can be well over 50. Use your own average.
EDID4 rows carry a segment header plus a 1000 character data field. Unicode systems and compression change the real figure.
Each status change writes a row. Errors and reprocessing add more.
Secondary indexes, free space and database page overhead.
Your results
Planning estimate only. Measure real sizes with DB02 or your database tools and adjust the byte inputs to match your system.
Online IDoc storage (GB) vs retention days
Sweeps Days kept online before archiving from 7 to 730, holding your other inputs fixed.
IDoc housekeeping review
Optional: a short expert review of your IDoc volumes, retention and archiving plan.
Optional. The tool and every export work without this. No spam.
How to use the calculator
Enter total IDocs per day, then the average data segments per IDoc. Pull both from WE02 or WE05 statistics, or count rows in EDIDC and EDID4 for a representative week. Adjust the stored bytes per segment if you have measured table sizes in DB02. The retention slider shows what changes if you move from keeping IDocs for a year to keeping them for a quarter before archiving.
- Use a representative busy week, not a quiet one.
- Count inbound and outbound together, they share the same tables.
- Include IDocs created by test or batch loads if they are not deleted.
What the formula models
Each IDoc has one control record in EDIDC, a number of data records in EDID4 and several status records in EDIDS. The calculator sums the three, multiplies by daily volume and an overhead factor for indexes and free space, then multiplies by retention days. EDID4 normally dominates, so segments per IDoc and bytes per segment move the result most. The model is linear, so the chart is a straight line. Real systems differ because of database compression and Unicode storage.
Reading the result and acting on it
Compare the steady-state size against what DB02 shows for EDID4, EDIDC and EDIDS today. If the real tables are much larger, you have IDocs older than your intended retention. The usual remedy is archiving through archiving object IDOC in SARA, with deletion of technical IDocs that have no audit value. Agree the retention with the business and audit owners first, because some IDocs, such as invoices to authorities, may need to be retained.
Common mistakes
The most common error is ignoring status records for IDocs that fail and are reprocessed many times, which can double the status volume. Another is assuming one message type represents all traffic: master data IDocs such as MATMAS are far larger than a simple status update. Finally, teams size for averages and forget that bulk loads during a migration or cutover can create millions of IDocs in a few days.
Frequently Asked Questions
Which tables hold IDoc data?
EDIDC holds the control record, EDID4 holds the data segment records on current releases, and EDIDS holds status records. Large systems often find EDID4 and EDIDS are among the biggest tables in the database.
Can I just delete old IDocs?
Technically yes, but deletion should follow your retention policy. Archive through archiving object IDOC where you need to keep the content, and delete only technical IDocs that have no audit or legal value.
How accurate is the estimate?
It is a planning figure. Accuracy depends on your segment counts and measured bytes per row. Calibrate by comparing the output with the current size of your IDoc tables in DB02 and adjust the inputs.
Does S/4HANA change the numbers?
HANA compression usually makes stored size smaller than the raw figure, so treat the result as an upper bound for column store tables and measure actual memory and disk use for your system.
If you want IDoc volumes, error rates and table growth surfaced from your live SAP system instead of typed in, Netray can build a read-only monitoring view for your Basis team.
Related Tools
SAP IDoc Processing Work Process Sizing Calculator
Work out how many work processes inbound IDoc processing needs at peak, and what throughput your current setup can sustain.
SAPSAP IDoc Error Backlog Clearance Calculator
Plan the cleanup of failed IDocs: how many can be reprocessed in bulk after a root-cause fix, how many need hands-on work, and how long it takes.
SAPSAP IDoc Interface Specification Document Template
Fill in a structured functional and technical specification for an IDoc-based interface and export it as a clean document.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)
Keep exploring
Free tools
- SAP IDoc Status Codes ReferenceLook up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.
- SAP IDoc Interface Go-Live ChecklistA practical checklist covering configuration, testing, monitoring and cutover steps before an IDoc interface goes into production.
- SAP IDoc Processing Work Process Sizing CalculatorWork out how many work processes inbound IDoc processing needs at peak, and what throughput your current setup can sustain.
ERP fixes and how-tos
- ERP Data Archiving Strategy: What to Archive and What to PurgeHow to decide what ERP data to archive or purge: find the big tables, set retention by record type, keep reports and audits working, and test restores first.
- SAP IDoc Status 51: Application Document Not PostedIDoc status 51 means Application document not posted, a category, not a diagnosis. Find the real cause in WE02 or SLG1 and reprocess safely with BD87.
- IDocs for SAP PP: LOIPRO, LOIROU and PORDCR Configuration and MonitoringWhich IDoc message types SAP PP uses for orders and routings, how to configure partner profiles and ALE, and how to monitor and reprocess failures.
Runs with your ERP
- SPS Commerce Fulfillment and SAP S/4HANA: EDI for retail partnersHow SPS Commerce Fulfillment connects SAP S/4HANA and ECC to retail trading partners: IDoc flow, managed maps, setup steps, pitfalls, alternatives and AI.
- Manhattan Active Warehouse Management with SAP S/4HANAHow large manufacturers run Manhattan Active Warehouse Management alongside SAP S/4HANA or ECC instead of EWM, with IDoc, API or EDI patterns and pitfalls.
- BarTender label printing with SAP S/4HANA and ECCHow BarTender prints barcode, RFID and compliance labels from SAP S/4HANA and ECC using IDocs, SAP AII or files, versus the BarTender Cloud ERP connector.