In this Article
Last week, we shared the case of one of our clients who prints 800,000 documents per month, without interruption, without loss, without a single incident. The post generated a lot of reactions, and one question kept coming up:
“But concretely, how does it work? How do you handle hundreds of thousands of SAP documents without anything breaking down?”
This article is the answer. I’ll explain, from A to Z, what SAP document printing and distribution management actually is: why it’s more complex than it looks, why SAP’s native system isn’t enough, and how a modern Output Management platform solves these problems.
Facts, concrete examples, and a clear picture of a subject that many underestimate until the day everything grinds to a halt.
First: What are we actually talking about?
When we say “SAP document,” we’re really talking about a very broad ecosystem. Here are the main categories we encounter with our clients.
Transactional documents
The most common ones: purchase orders, sales orders, delivery notes, customer and supplier invoices, payment advices, account statements. Each of these documents is automatically triggered by an event in SAP, a validation, a posting, a dispatch. They must reach the right recipient, at the right time, in the right format.
Production and logistics documents
Pallet labels, product labels, manufacturing orders, traveler sheets, traceability documents, picking slips… In the pharmaceutical, food, atomotive or aerospace industries, these documents are subject to very strict regulatory requirements. An unreadable barcode or a misdirected document can shut down an entire production line.
HR documents
Pay slips, certificates, contracts, individual letters. They require fine personalization and strict confidentiality rules.
Mass communications
Account statements, dunning letters, notifications sent simultaneously to thousands of recipients. Volume and delivery reliability are the key challenges here.
At any single client site, it’s often 10, 20, or 50 different document types flowing through SAP every day, each with its own rules, recipients, and format constraints.
The SAP Spool: The native print engine
SAP has a built-in system for managing document outputs: the Spool. Here’s how it works.
How the Spool works
When an SAP transaction generates a document, an invoice via VF01, a purchase order via ME21N, a label from the MM module, that request is placed in a queue: the SAP Spool (visible from transaction SP01). A dedicated process, called a Work Process of type SPO, handles each request and generates a file in an intermediate format: either OTF (Output Text Format) or Raw Data, depending on the form type.
This file is then sent to the printer or target system via a communication protocol defined in the SAP device configuration (transaction SPAD): LPR, IPP, or direct network connection.
SAP form technologies
Document formatting in SAP relies on several technologies, depending on the age and evolution of the system:
- SAPscript: Introduced in the 1980s and still present in legacy systems. It allows basic form design but is hard to maintain and graphically inflexible, not ideal for documents with a strong visual identity.
- Smart Forms: Introduced with SAP R/3 4.6, offering a more modern graphical design tool and better conditional logic management. Still widely used, but limited for complex layouts.
- Adobe Forms (ADS): SAP’s currently recommended solution. It relies on Adobe LiveCycle Designer for design and requires an ADS (Adobe Document Services) server for rendering. It natively supports PDF and offers better graphical capabilities.
- SAP S/4HANA Output Management: In modern S/4HANA environments, SAP introduced a built-in output management layer. It covers basic needs but often falls short in complex environments.
Why the native SAP spool isn’t enough
This is the heart of the matter. The SAP Spool works well for modest volumes and simple environments. As complexity grows, it quickly hits its limits and those limits are costly.
Saturation during peak periods
Spool Work Processes consume resources on the SAP application server. During a monthly close, a billing campaign, or a production spike, these processes become saturated. Printing slows down. Business transactions slow down too. In extreme cases, the entire chain comes to a standstill.
No high availability
If a printer goes offline, SAP does not automatically reroute the job. The document stays stuck in the Spool or is lost with no notification. In an industrial environment with hundreds of devices spread across multiple sites, this is a permanent risk.
No reliable traceability
SAP provides no proof of delivery. Knowing whether an invoice was actually sent, whether a delivery note was printed, whether a label reached the right printer is difficult or impossible without custom development. In the event of an audit or customer dispute, this is a critical gap.
Multichannel: virtually nonexistent natively
The SAP Spool is designed for physical printing. Sending by email with a secured PDF attachment, automatic archiving in PDF/A, publishing to a customer web portal — all of these require custom development that is expensive to build and maintain over time.
A complex administration and configuration
Jobs and printers monitoring is not possible in standard. The only information available is that a job is sent without clear status. In case of incident, there is no information allowing a fast issue solving. Device management in SAP (transaction SPAD) is also technical, unintuitive, and centralized with SAP Basis teams. Every new printer, every network change, every site relocation requires an intervention. In constantly evolving environments, this is a significant source of administrative burden.
„A saturated Spool doesn’t just slow down printing. It can block entire processes: billing, deliveries, accounting close. It’s an operational risk that few companies truly measure until they experience the consequences firsthand.“
The solution: external Output Servers and the BC-XOM interface
BC-XOM: SAP’s standardized opening
To address the limitations of the native Spool, SAP created a standardized, certified interface: BC-XOM (Business Connector — eXternal Output Management). This interface allows an external Output Management platform to integrate directly with the SAP Spool.
From SAP’s perspective, nothing changes: the printer still exists, the SPAD configuration remains in place. But behind the scenes, the actual processing is delegated to a far more powerful external system, capable of handling millions of documents per month.
The SEAL Systems BC-XOM agent: how it works
SEAL Systems’ BC-XOM implementation is built on an intelligent two-tier architecture.
A lightweight agent is installed directly within the SAP environment. This agent acts as an orchestrator:
- It intercepts each Spool request as soon as it is created and routes it to the PLOSSYS Output Engine platform via the IPP or IPPS protocol.
- It continuously monitors the availability of PLOSSYS services. If a service becomes unresponsive, it automatically fails over the request to a backup server or environment, no human intervention, no document loss.
- It encrypts data in transit via the IPPS protocol (Internet Printing Protocol Secure). Sensitive documents — invoices, pay slips, customer data — never travel unencrypted over the network.
- It sends processing status back to SAP via RFC callback, enabling full traceability across both systems.
„The SEAL Systems BC-XOM agent transforms SAP integration into a secure, resilient, and intelligent connection. With availability exceeding 99.9%, maintenance windows and downtime are a thing of the past.“
PLOSSYS Output Engine: The platform at the core
Behind every SAP document that gets distributed, there is PLOSSYS Output Engine, the platform developed by SEAL Systems and designed for the most demanding environments. The result of more than 40 years of experience.
A cloud-native microservices architecture
PLOSSYS Output Engine is built on a containerized microservices architecture (Docker/Kubernetes). Each service automatically scales to meet demand: during peak periods, resources are allocated; during off-peak periods, they are released. The result: processing times under 0.1 seconds per document in spool mode, and a processing capacity of several million pages per day. PLOSSYS runs on-premise, in private or public cloud, or in hybrid mode.
The OTF converter: zero format constraints
One of PLOSSYS’s most practical strengths is its OTF converter (SAPGOF Converter). It handles the transformation of SAP’s intermediate format downstream, depending on the actual destination channel:
- Network or industrial printer → conversion to PCL or PostScript tailored to the device model
- Email → high-fidelity native PDF
- Legal archiving → PDF/A compliant with ISO standards
- Web portal or document space → format adapted for online viewing
One SAP form. Zero ABAP modifications. Perfect distribution across all channels. This is what allows our clients to keep using their existing SAPscript, Smart Forms, or Adobe Forms, regardless of how their infrastructure evolves.
Universal channel management
PLOSSYS connects, from a single interface, all of the company’s output channels:
- Printing: network, local, industrial (labels, large format), and mobile printers
- Email: automatic sending with secured PDF attachments
- B2B exchanges with partners and suppliers
- Customer web portals and document spaces
- Automatic archiving: SAP ArchiveLink, SharePoint, DMS systems
- Fax and fax-to-mail
Document enrichment and composition
The platform can enrich SAP documents downstream, without touching the SAP configuration: stamps, watermarks, barcodes (1D, 2D, QR, OMR), logos, automatic numbering. Document templates are manageable via a drag-and-drop graphical interface, accessible to business teams with no ABAP skills required, thanks to our form and label composition solution.
Real-time traceability and monitoring
Every document is tracked end-to-end: trigger event, source system, distribution channel, target device, processing time, delivery status. A centralized dashboard allows IT teams to respond immediately in the event of an incident, without opening SAP. The complete history is available for audits and customer disputes.
Security at every level
Communications between components are encrypted via HTTPS, TLS, and IPPS. Authentication uses OIDC identity providers (e.g., Keycloak) or Active Directory/ADFS. Pull printing ensures a document only prints when the authorized user physically presents themselves at the printer and authenticates. Each document can carry a stamp or watermark indicating its status and issuer.
Native SAP forms vs. External design tools: Two complementary approaches
The question often comes up in projects: should you keep native SAP forms or invest in an external composition solution? The answer is rarely one or the other.
What native SAP forms do well
SAPscript, Smart Forms, and Adobe Forms are native to SAP, well-documented, and familiar to ABAP teams. For simple, standard, and infrequently changing documents, they remain relevant, especially if the company already has a large library of existing forms.
Where external composition delivers real value
Once requirements become more complex, strong visual identity, dynamic personalization, multilingual documents, data merging from multiple systems, massive volumes, an external composition solution brings decisive advantages:
- Templates editable by business teams, with zero ABAP development
- Clear separation between SAP data and document formatting
- Guaranteed continuity during SAP migrations: templates stay in PLOSSYS, independent of the SAP version
- Compliance with sector-specific regulatory requirements (aerospace, pharmaceuticals, finance…)
S/4HANA Migration: Output Management, an often-underestimated challenge
Every SAP IT department is thinking about it or actively working on it: migrating to S/4HANA. And in these projects, document output management is one of the least anticipated sources of cost overruns.
Why migration puts SAP outputs at risk
S/4HANA modifies the underlying data flows and drops certain legacy form technologies. SAPscript forms and in some cases Smart Forms often require a complete rewrite. OTF flows change in structure. Outputs that worked perfectly in ECC can end up blocked or corrupted after migration.
How PLOSSYS protects your existing setup
Because PLOSSYS processes documents downstream of SAP between the Spool and the output devices, it creates an abstraction layer that shields your document chain from SAP upgrades.
In practice:
- Your SAP forms continue to work, regardless of the SAP rendering engine.
- Your routing rules and device configurations stay in PLOSSYS, untouched.
- You can migrate to S/4HANA without redoing 10 or 15 years of output configuration.
We actively support ECC R/3 to S/4HANA migration projects. Our experience consistently shows that Output Management is one of the areas where companies recover the most value provided it has been planned for in advance.
A Concrete example: A global industrial leader
To illustrate what all of this looks like in practice, here is a real case we published recently.
A global group operating in a regulated industry, where documentary reliability and compliance are absolute imperatives , was using a multitude of local solutions to manage its SAP outputs: form composition, label management, SAP spool.
The result: high SAP Basis costs, no centralized monitoring, and insufficient traceability to meet regulatory requirements.
We deployed a unified PLOSSYS Output Engine platform across the entire group. By replacing the disparate solutions with a single architecture, we achieved:
- Guaranteed, real-time monitored print and distribution services
- Full standardization of document processes across the group
- Significant reduction in SAP Basis administration costs
- Centralized monitoring of all flows, jobs, and devices
- Simplified printer fleet management via easyPRIMA
This project illustrates how centralized, industrialized SAP print and distribution management becomes a true lever for performance, compliance, and cost control.
Who is SEAL Systems?
40 years of a single specialty
SEAL Systems was founded in 1981. For more than 40 years, we have done one thing only: Output Management and enterprise document management. We have never strayed from this specialty which has allowed us to build expertise that few players can match.
Today, we serve more than 1,500 clients worldwide, across industries as varied as manufacturing, aerospace, energy, finance, the public sector, and logistics. Our teams number more than 130 people, with our headquarters in Germany and subsidiaries in France and the United States.
A long-standing certified SAP partner
SEAL Systems has been a certified SAP partner for many years. Our BC-XOM, SAPGOF, and SAPGOFU interfaces are SAP-certified for both S/4HANA and ECC/R3. Our SAP competency center supports clients throughout the entire lifecycle of their SAP environment: from initial implementation through S/4HANA migration and ongoing optimization.
A consulting approach, not just a tool
Our difference lies not only in the technology. It lies in our ability to understand the business challenges behind document workflows and to propose a tailored solution, not a standard product. What used to take two weeks for some of our clients now takes less than an hour.
Measurable results
Our clients collectively generate more than €50 million in IT savings each year through our solutions. We have directly contributed to avoiding more than 3,000 tonnes of CO₂ emissions and, indirectly, to saving the equivalent of 5 billion liters of water per year through the reduction of unnecessary printing.
In summary
Here’s what I hope you take away from this article:
- SAP documents are not a technical detail, they are at the heart of your business processes.
- The native SAP Spool meets basic needs, but not the demands of a high-volume industrial environment.
- The BC-XOM interface allows an external Output Management platform to connect to SAP without changing anything on the SAP side.
- PLOSSYS Output Engine handles the entire chain: from receiving the Spool request to delivering on any channel, with full traceability and data encryption.
- During an S/4HANA migration, a well-integrated Output Management platform protects your existing setup and significantly reduces risk and cost.
800,000 documents per month. Without interruption. That’s not luck, it’s optimized architecture, a high-performance platform, and an environment that’s secure and simple to administer.