Our monthly billing cycle processes approximately 500,000 invoices and the runtime has been increasing with data volume growth. We’re currently taking 18-20 hours for the complete cycle, which is cutting into our processing window and delaying downstream financial close activities.
The billing run uses standard SAP batch jobs for invoice creation, but we’re seeing significant performance degradation in the database commit phase and during PDF generation for customer documents. Resource monitoring shows CPU spikes during peak processing but database wait times seem to be the main bottleneck.
I’m interested in hearing what parallel processing strategies others have implemented successfully. Also, what database optimization techniques have proven effective for large billing runs? How do you balance batch scheduling to maximize throughput while maintaining system stability for concurrent online users?
Looking for practical experiences with high-volume billing performance tuning.
The 18-20 hour runtime for 500K invoices suggests you’re processing serially or with minimal parallelization. We had similar volumes and reduced runtime to 6 hours by implementing proper parallel processing. The key is splitting the workload intelligently - not just by arbitrary ranges, but by logical groupings that minimize database lock contention. Split by company code, billing type, or customer account ranges. Configure multiple batch job variants running simultaneously, each processing a subset. Start with 4-6 parallel streams and monitor database performance before increasing.
Good points on parallelization and database tuning. What about the PDF generation bottleneck? That’s consuming about 30% of our total runtime. We’re using standard SAP output management with Adobe Document Services. Is there a more efficient approach for high-volume document generation, or optimization techniques within the current architecture?
PDF generation at scale requires separating it from the billing transaction. Don’t generate PDFs synchronously during invoice creation - that’s your bottleneck. Configure output determination to create output requests without immediate processing. Then run a separate parallel job for PDF generation after billing documents are created. We use transaction RSNAST00 with multiple variants running in parallel, each processing a range of output requests. This decoupling reduced our billing runtime by 40% because document creation isn’t waiting for PDF rendering. Also consider whether all customers need PDF immediately - some might accept next-day delivery, allowing you to spread PDF generation over a longer window.