SAP IDoc Work Process Sizing Calculator
When inbound IDocs pile up in status 64, the question is usually whether you need more work processes, a faster posting routine, or less lock contention. This calculator applies a simple load model so you can see which lever matters.
Your numbers
Month end, promotions and batch window releases concentrate load. Take it from a busy day in your own statistics.
Application posting time, not just IDoc layer time. Check STAD or ST03N for the inbound function module.
Leave headroom for queueing delay and other workloads.
Your results
Queueing model for planning. Confirm with load tests, and remember that locking on the same master data object can limit useful parallelism.
Work processes needed vs average IDocs per hour
Sweeps Average IDocs per hour from 1000 to 100000, holding your other inputs fixed.
Integration performance review
Optional: an expert look at your IDoc inbound throughput and parallelization design.
Optional. The tool and every export work without this. No spam.
How to use it
Take average hourly volume from WE02 statistics, choose a peak factor from your busiest day, and enter the average time the inbound function module takes to post one IDoc. The tool returns the work processes busy at peak and the number you need at your chosen utilization target. Enter the work processes you can dedicate, for example the background processes assigned to parallel jobs of RBDAPP01, to see utilization and sustainable throughput.
The formula
The model is Little's law. Offered load in busy work processes equals the arrival rate in IDocs per second multiplied by the service time in seconds. Dividing by the target utilization gives the required work processes, because a pool running near 100 percent queues badly. A target of 60 to 70 percent is a typical planning point. The model assumes IDocs are independent. If many IDocs update the same material, customer or account, row locks serialize them and extra work processes will not help.
Reading the output
If utilization with available work processes is under your target, you have headroom. Between target and 100 percent, queues form at peak but drain afterwards. Above 100 percent the backlog grows during the peak and the backlog growth figure shows how fast it builds. Use the chart to see where your volume crosses the capacity of your current setup, and where an application-level improvement would help more than another process.
Common mistakes
Teams often use the IDoc layer time instead of total posting time, which understates load. Others size for the daily average and miss the spike when several partners send files together. A third mistake is sizing dialog work processes for a job that runs in background. Check the actual processing path in your partner profile in WE20 and process code in WE42 before you decide where capacity belongs.
Frequently Asked Questions
What does status 64 mean?
Status 64 means the IDoc is ready to be passed to the application. If many sit there, inbound processing is not keeping up or the background job that processes them is not running or is too limited.
How do I get processing time per IDoc?
Use transaction STAD or workload statistics in ST03N for the inbound function module, or compare timestamps in the status records of a sample of IDocs in WE02.
Why not just add more work processes?
More processes help only when the work is parallelizable and the system has CPU and memory. Lock contention on shared master data, or a slow custom enhancement, will cap the gain.
Is the queue model exact?
No. It is a first-order planning model using averages. Real arrivals are bursty, so use a conservative utilization target and validate with a load test.
If your IDoc inbound is slow and you want a second pair of eyes on the posting routine and parallelization design, Netray can review it with your SAP team.
Related Tools
SAP IDoc Database Growth Calculator
Estimate IDoc table growth from daily volume, segments per IDoc and retention days, and see when archiving pays off.
SAPSAP RFC Connection Pool Sizing Calculator
Calculate the concurrent RFC connections an external application needs and compare them with gateway and destination limits.
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 Interface Retry and Backoff Window Calculator
See how long an interface keeps retrying before it gives up, using initial delay, multiplier, retry count and jitter.
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)