SAP printing FAQ

Answer: SAP S/4HANA Cloud makes print jobs available through print queues. To produce a printout on a printer in the company network, a local or external printing component is needed to retrieve the jobs from SAP and forward them to the physical print destination. The cloud service does not need to access the printer directly over the internet.

How Suchy MIPS helps: BENS OMS Print Hub is designed for exactly this workflow: it connects to the SAP print queues, retrieves new print jobs, maps them to a virtual printer defined in BENS and thus to a specific destination, and sends them to the local or remote printer. After processing, BENS updates the job status in SAP and can return a detailed message. Processed jobs are archived in BENS, where they can be analyzed or printed again.

For more complex printing environments, routing, Print Profiles and additional BENS processing functions can also be used.

Direct link to this question

Answer: No. A traditional Windows print server is not an inherent requirement for SAP S/4HANA Public Cloud. However, a component is needed to retrieve cloud print jobs and provide a connection to the physical printers. With SAP Cloud Print Manager, this component runs as a Windows service. An external OMS can perform this task using its own architecture.

How Suchy MIPS helps: BENS OMS Print Hub handles the print queue connection and manages the mapping of SAP queues to virtual BENS printers and actual destination devices. This makes it possible to build an SAP cloud printing architecture without necessarily relying on a traditional Windows print server. The local components required depend on the destination protocol, the printer and any drivers or conversions needed.

Direct link to this question

Answer: In many cases, yes. What matters is less the age of the printer than whether it can be addressed using suitable protocols and data formats, and whether required functions such as duplex printing, tray selection or finishing can be controlled. Representative printer models should therefore be tested with real business documents before migration.

How Suchy MIPS helps: BENS OMS Print Hub can manage existing printers as destinations. BENS supports common print data formats such as PDF, PostScript and PCL; where needed, data can be converted or supplemented with additional print control information. This often allows existing devices to remain in use even when cloud migration fundamentally changes the SAP printing path.

Direct link to this question

Answer: The typical workflow consists of several clear steps: an SAP application generates the output document, SAP places the job in a print queue, and a printing component retrieves the job, determines the destination and transmits the data to the printer. The processing status can then be reported back to SAP.

How Suchy MIPS helps: With BENS OMS Print Hub, the workflow is: SAP print queue → BENS OMS Print Hub → virtual BENS printer → physical print destination. BENS downloads the job from SAP, processes it if necessary, sends it to the configured destination and then updates the SAP status. The BENS web panel also provides job data, destinations, technical parameters and debugging information for traceability.

Direct link to this question

Answer: Yes. Cloud printing is not restricted to a single location. Print queues must be clearly assigned to a location or routing logic, and local print destinations must be securely reachable. With many branch offices, administration should be centralized wherever possible rather than creating a separate isolated solution for each location.

How Suchy MIPS helps: BENS OMS Print Hub can manage SAP queues centrally and map them to different virtual printers or physical destinations at different branch offices. For additional communication requirements, BENS SecureConnector can provide targeted, encrypted, bidirectional connections between cloud and on-premises environments. Unlike a traditional site-to-site VPN, SecureConnector does not connect entire networks, but only the applications, devices or data sources required.

Direct link to this question

Answer: Automatic invoice output starts with SAP output control: the output channel and print queue are determined for each document. The printing component then retrieves the job. Key factors include the document type, Output Parameter Determination, the queue used and the required print destination.

How Suchy MIPS helps: BENS OMS Print Hub retrieves invoice jobs made available in SAP print queues and forwards them to the configured destinations. Different queues can, for example, be mapped to different printers, printer pools or locations. BENS can also process the print data, for example to convert formats or apply printer-specific settings, and report the status back to SAP after processing.

Direct link to this question

Answer: To print directly in the shipping department, SAP must assign the delivery note to a suitable print queue. For a single shipping workstation, this queue can be linked to a fixed printer. With multiple shipping locations, additional routing logic can ensure that the job is automatically output at the correct location or shipping printer.

How Suchy MIPS helps: In BENS OMS Print Hub, the SAP queue is mapped to a virtual BENS printer and then to the required destination. If a simple 1:1 mapping is not sufficient, BENS can extend print distribution with additional rules. This can accommodate different shipping locations, document types or printer pools, for example. The complete job path remains traceable in BENS.

Direct link to this question

Answer: A traditional site-to-site VPN is not required for the usual pull-based printing from SAP S/4HANA Cloud. The local printing component establishes the connection to SAP and retrieves new jobs from the cloud, so SAP does not need to access the local printer directly. The firewall rules required depend on the architecture used.

How Suchy MIPS helps: BENS OMS Print Hub can retrieve print queues through the designated SAP interfaces and then forward the jobs locally or to remote print destinations. If a persistent bidirectional connection between cloud applications and specific local systems or devices is also needed, BENS SecureConnector can be used. The local connector initiates the encrypted outbound connection, so the local system does not need to be directly accessible from the internet.

Direct link to this question

Answer: The formats available depend on the SAP product, queue type and configuration. In practice, PDF and printer-specific data formats are particularly relevant. The key requirement is that the generated format is compatible with the destination device and the print functions required.

How Suchy MIPS helps: BENS OMS Print Hub can forward print data retrieved from SAP to suitable destination devices. If the output format is not compatible with the printer, BENS processing functions can be used, for example to convert between PDF, PostScript and PCL. Depending on the printer and data format, control information for functions such as duplex printing, paper selection, stapling, hole punching or folding can also be added.

Direct link to this question

Answer: Yes, provided the required output path supports PDF. A distinction is needed here: PDF may be the document format in the SAP print queue, or the destination may be a system or device that processes PDF directly. PDF output does not automatically constitute archiving; storage and archiving are separate processing steps.

How Suchy MIPS helps: BENS OMS Print Hub can retrieve PDF jobs from SAP and forward them to PDF-capable printers or other defined destinations. BENS can also convert documents to PDF or further process PDF data before output where needed. For physical printers, additional print instructions such as duplex printing or finishing can be added, provided the destination device supports these functions.

Direct link to this question

Answer: The main change when moving from SAP ECC to S/4HANA Public Cloud is the architecture. In traditional SAP environments, many companies use SAP Spool, output devices and direct integration with their internal printing infrastructure. In the public cloud, jobs are handed over through defined cloud interfaces and print queues. Existing printing processes should therefore be documented individually and mapped to the new architecture before migration.

How Suchy MIPS helps: BENS OMS Print Hub bridges the gap between SAP print queues and the existing printer environment. Existing destination devices, routing rules and specialized printing requirements can thus be incorporated into a new cloud printing architecture. For companies already using BENS OMS in traditional SAP environments, migration can also be planned to retain familiar BENS functions for distribution, processing and monitoring.

Direct link to this question

Answer: A reliable test should involve much more than a single test page. It should include a dedicated test queue, typical business documents, different printer models, paper trays, duplex printing, finishing, error scenarios and print destinations at different locations. Status reporting and recovery after printer or network failures should also be tested.

How Suchy MIPS helps: As part of a proof of concept, BENS OMS Print Hub can be connected to an SAP test environment or test queues. The BENS web panel allows received jobs, destination mappings, statuses, technical parameters and debug logs to be checked. This makes it possible to verify the complete process, including error handling and SAP status reporting, rather than just checking whether a sheet comes out of the printer.

Direct link to this question

Answer: An SAP print queue is a logical queue for print jobs. SAP applications place documents there, which are then retrieved by a suitable printing component or reported to an external OMS through a notification integration. The print queue is therefore the handover point between SAP and the downstream printing infrastructure, rather than the physical printer itself.

How Suchy MIPS helps: BENS OMS Print Hub reads the print queues configured in SAP and displays them in the web panel. For output, virtual printers are created in BENS that correspond to the SAP queues and are in turn mapped to a specific destination, such as a physical printer. This keeps the SAP-side queue logically separate from the actual printer address.

Direct link to this question

Answer: In SAP S/4HANA Cloud, a print queue is created using the app provided for this purpose. Typically, the name, description, output format and appropriate communication assignment are specified. For pull or notification integration, the queue type or communication scenario appropriate to the integration method must be selected.

How Suchy MIPS helps: After SAP has been configured, BENS OMS Print Hub connects to the SAP system and retrieves the queue information. In the BENS web panel, the SAP queue can be mapped to a virtual BENS printer and then to the required destination. This decouples the SAP configuration from the physical printer definition and enables centralized administration.

Direct link to this question

Answer: SAP Cloud Print Manager connects SAP cloud print jobs to local printers and covers standard scenarios. An external output management system becomes relevant when additional capabilities are needed, such as centralized control, detailed job tracking, flexible destination mapping, additional data processing, complex printer environments or advanced operational functions.

How Suchy MIPS helps: BENS OMS Print Hub is designed as an external output management solution for SAP cloud scenarios. It retrieves SAP print queues, maps them to virtual BENS printers and real destinations, processes jobs, updates the status in SAP and archives processed jobs for analysis or reprinting. The web panel displays queue mappings, job statuses, destinations, technical parameters and debug logs, among other details. BENS OMS Print Hub was also developed with the new SAP certification specifications S/4HC-PUB-PRINT-OMS, BTP-PRINT-OMS and S/4HC-PRINT-OMS in mind.

Direct link to this question

Answer: SAP_COM_0466 is the SAP communication scenario for pull integration in printing. The external printing component regularly checks SAP for new jobs, downloads available jobs from the print queue and then processes them. This approach is particularly suitable for cloud-to-on-premises scenarios because no inbound connection from the cloud to the local printer is required.

How Suchy MIPS helps: BENS OMS Print Hub can use this principle to monitor SAP print queues and retrieve new print jobs. After processing, the job status is reported back to SAP. The BENS web panel also allows processed jobs to be traced using their status, destination and technical details.

Direct link to this question

Answer: SAP_COM_0467 is intended for notification integration with external output management systems. SAP sends a notification to the OMS when new print jobs are available; the OMS then retrieves the job through the designated interface and updates its status after processing. A corresponding OMS queue for notification integration is configured in SAP for this purpose.

How Suchy MIPS helps: BENS OMS Print Hub is being developed for the new SAP OMS integration scenarios. A key requirement is end-to-end handling of queue information, print jobs, destination mapping and status reporting. Before going live, the released version should be checked to determine which integration method – pull or notification – is used in the relevant BENS version and SAP environment.

Direct link to this question

Answer: With pull integration, SAP does not wait to actively access a local printer. Instead, the external printing component regularly checks SAP for new print jobs and downloads them when required. This makes the approach well suited to cloud-to-on-premises architectures because the local side initiates the connection.

How Suchy MIPS helps: BENS OMS Print Hub can perform this role: it authenticates with SAP, queries the configured print queues, downloads new jobs, processes them and sends them to the assigned print destinations. BENS then updates the processing status in SAP and retains additional job and log data for analysis.

Direct link to this question

Answer: Yes. Multiple logical print queues can lead to the same physical print destination. This is useful, for example, when different document types or SAP processes use separate queues but ultimately need to print on the same printer while following different workflows. Conversely, a queue can also be distributed across multiple physical destinations, depending on the outcome of workflow or routing analysis. This 1:n distribution is frequently required in practice, for example when users, locations or printer pools need different destination devices.

How Suchy MIPS helps: In BENS OMS Print Hub, each relevant SAP queue is mapped to a virtual BENS printer. Multiple virtual printers can point to the same physical destination. Conversely, BENS can forward a job to different destination devices or printer pools based on defined rules. This preserves the SAP-side queue structure while allowing the actual printer environment and additional routing logic to be administered centrally in BENS.

Direct link to this question

Answer: The print queue is first created in SAP and configured for external printing integration. The actual mapping to the physical printer then takes place in the downstream printing component or OMS. After setup, the complete path should be tested using a test page or a real business document.

How Suchy MIPS helps: BENS OMS Print Hub uses virtual printers for this purpose. A virtual BENS printer corresponds to an SAP print queue and is mapped to a destination, such as a network printer. If the physical device changes later, the destination can be updated in BENS without necessarily having to change the SAP queue. This simplifies printer operation and replacement.

Direct link to this question

Answer: Output Parameter Determination defines how a business document is output in SAP. This can include the output channel, print queue, number of copies and other parameters. The rules must be tested carefully because even an incorrect queue assignment can cause a document to be printed at the wrong location or not printed at all.

How Suchy MIPS helps: BENS OMS Print Hub takes over once SAP has handed the print job to the print queue. BENS retrieves the queue, maps it to the configured destination and can handle further print processing. This provides a clear separation between SAP-side output rules and the actual printer environment: SAP decides which queue a document enters; BENS controls the subsequent path to the destination device.

Direct link to this question

Answer: Yes. In suitable configurations, SAP Cloud Print Manager can use print options such as duplex printing or paper tray selection. However, whether an option actually reaches the device depends on the print profile, data format, driver and printer model. These functions are therefore not inherently exclusive to an external OMS.

How Suchy MIPS helps: BENS OMS Print Hub can retrieve the Print Profiles defined in SAP and make their settings visible within the job. BENS also knows the configured destination devices and can supplement or correct print options such as duplex printing, paper tray selection or other finishing parameters, depending on the printer, data format and available BENS processing functions. This is particularly useful when SAP settings alone are insufficient or need to be implemented in a printer-specific way.

Direct link to this question

Answer: If an SAP print queue does not appear in the external OMS, first check the integration configuration: the queue type, communication scenario, communication arrangement, technical users, credentials and API URL must be compatible. Permissions or an incorrect system configuration can also prevent the OMS from reading the queue.

How Suchy MIPS helps: BENS OMS Print Hub displays the queues detected in SAP in the web panel. If a queue is missing, this helps distinguish quickly between a communication failure with SAP and a missing downstream destination mapping. BENS logs the communication and provides debugging information so that authentication, connection or configuration errors can be analyzed precisely.

Direct link to this question

Answer: If a job remains in the queue, several causes are possible: the printing component is not running, the connection to SAP is interrupted, credentials are invalid, the queue is not mapped correctly or the retrieval service has encountered an error. A useful approach is to check each stage, from the SAP queue status and communication through to the local printing service.

How Suchy MIPS helps: BENS OMS Print Hub maintains detailed processing logs. These show whether the queue was reached, whether a job was detected and downloaded, which destination mapping was used and where an error occurred. The web panel also displays technical job information and the debug log for each individual print job. This allows much more precise troubleshooting than relying solely on the SAP status.

Direct link to this question

Answer: The “New” status typically means that the external printing component has not yet successfully processed the print job and reported back to SAP. Check whether the job is visible in the OMS, whether it can be retrieved, whether destination mapping works and whether status updates can be sent to SAP.

How Suchy MIPS helps: BENS OMS Print Hub retrieves new jobs from the configured queues and updates the status in SAP after processing. Successful processing is reported accordingly; if an error occurs, BENS can return the “Failed” status together with a more detailed message. Additional technical details about the affected job are available in the BENS web panel and logs.

Direct link to this question

Answer: “Successful” does not automatically mean in every system that a physical sheet is in the output tray. Depending on the level of integration, the status may mean that the OMS has successfully accepted the job or handed it over to the printer. A paper jam, empty tray or error after handover may be a separate issue. The technical event that triggers the SAP status must therefore be clearly defined.

How Suchy MIPS helps: BENS OMS Print Hub tracks the job up to handover to the configured destination and stores processing and log data. PrintRadar can be added to provide visibility into the physical device status. This distinguishes two levels: BENS OMS shows print job processing, while PrintRadar shows device errors or paper and toner levels, for example. Together, they provide a much more complete picture.

Direct link to this question

Answer: If an SAP document reaches the wrong printer, check the process from the top down: which print queue did SAP determine? Which queue does the OMS see? Which virtual printer or destination is this queue mapped to? In complex multisite environments, overly broad or outdated routing rules can also be the cause.

How Suchy MIPS helps: BENS OMS Print Hub makes the mapping between the SAP queue, virtual BENS printer and destination device transparent. The web panel shows which job was sent through which queue to which destination. This quickly reveals whether the error originated in SAP output control or in the BENS destination mapping. The mapping can then be corrected centrally in BENS.

Direct link to this question

Answer: Shifted or cut-off printouts often result from a combination of paper size, scaling, non-printable margins, fonts, driver settings or incorrect interpretation of the data stream. First check whether the document generated by SAP is correct and whether the discrepancy only appears during print preparation or at the device.

How Suchy MIPS helps: BENS can modify print data using filters or plugins before output. Documents can, for example, be scaled slightly or adapted to a destination paper size if a printer cannot print certain margin areas. In complex cases, conversion to a different print format may also be useful. Processing takes place centrally, avoiding the need to adjust every individual workstation or printer driver.

Direct link to this question

Answer: If duplex printing does not work, first make sure that the printer supports duplex printing and that its duplex unit is functioning correctly. Then identify where the information is being lost. Check whether SAP or the Print Profile requests duplex printing, whether the data stream contains this information and whether the destination printer supports it. Drivers or downstream print processing can also override the setting.

How Suchy MIPS helps: BENS OMS Print Hub can evaluate SAP Print Profiles and make their job settings visible. If the required duplex command is missing or unsuitable for the destination device, BENS can adapt the print data using an appropriate filter or plugin. This allows duplex printing to be corrected centrally without modifying the SAP application or each individual workstation.

Direct link to this question

Answer: Size and resolution are particularly critical for labels. Check the defined label format, the media size in the printer, the device resolution and the printer language used. A data stream generated for 203 dpi can look significantly different on a 300 or 600 dpi device unless it is generated or scaled appropriately.

How Suchy MIPS helps: BENS can process label data and route it to suitable label printers. Depending on the input data format and the specific printer language, filters, conversions or printer-specific adjustments can be used. BENS is therefore also suitable for heterogeneous label printing environments with different printer models or resolutions. Actual label formats and devices should be tested together before going live.

Direct link to this question

Answer: A failed print job should only be reprinted once it is clear whether a physical printout has already been produced. Otherwise, duplicate output may result. The OMS should therefore maintain a traceable job status and history and support controlled retries.

How Suchy MIPS helps: BENS retains print jobs and their status information. If the destination is temporarily unreachable, the job remains in the BENS Printing Queue until the printer becomes available again. The print job can then be output automatically. BENS OMS Print Hub also archives processed jobs for analysis and reprinting. This allows an operator to make an informed decision about reprinting a job rather than blindly triggering the document again in SAP.

Direct link to this question

Answer: For troubleshooting, break the printing path down into individual stages: document generation in SAP, print queue, retrieval by the OMS, processing, destination mapping, handover to the printer and finally device status. Timestamps and unique job IDs are particularly helpful.

How Suchy MIPS helps: BENS OMS Print Hub retains extensive information about each processed job: title, status, destination, technical parameters, unique ID, attachments where applicable and debug log. This makes it possible to determine whether the job left SAP, when BENS retrieved it, which destination was used and whether an error occurred during handover. In traditional SAP Spool scenarios, SAP-related identifiers can also be used for searching, provided they are available in the job.

Direct link to this question

Answer: Automatic location selection works when the printing process has access to a suitable attribute, such as the plant, branch office, warehouse, workstation or a print queue already determined by SAP. The routing logic then maps this attribute to a printer or printer pool.

How Suchy MIPS helps: BENS can manage this mapping centrally. An SAP queue can be mapped to a virtual BENS printer, which in turn points to the print destination at the relevant location. Additional routing rules can be used for more complex scenarios, for example to accommodate different locations, document types or fallback destinations. If a local printer changes, only the destination definition in BENS needs to be updated; the SAP-side logic can remain unchanged.

Direct link to this question

Answer: Yes. SAP output control can already determine different print queues for different document types. For example, an invoice can be sent to a different queue from a delivery note. An additional OMS layer can refine this mapping further.

How Suchy MIPS helps: With BENS OMS Print Hub, SAP queues are retrieved separately and mapped to different virtual printers or destinations. For example, the invoice queue can lead to an office printer and the delivery note queue to a shipping printer. Where required, printer-specific settings or additional routing rules can be applied without unnecessarily complicating the SAP document logic.

Direct link to this question

Answer: A printer pool groups multiple physical devices into a single logical destination. This can be useful for balancing the workload or switching to another printer when a device is unavailable. Clear rules for priority, sequence and error handling are essential.

How Suchy MIPS helps: Printer pools can be built using BENS Server and BENS processing functions. The Load Balancing plugin can distribute jobs across multiple destination devices. Depending on the design, this can take into account a fixed sequence, availability or another rule, for example. For SAP, the pool remains a logical destination; BENS handles the actual distribution to the physical devices.

Direct link to this question

Answer: Like other print documents, labels from SAP S/4HANA Cloud are made available through a suitable output process and a print queue. Labels also require attention to format, printer language, resolution, media size and often barcode requirements. Testing should therefore always use real labels and the printers actually deployed.

How Suchy MIPS helps: BENS OMS Print Hub can retrieve the SAP queue and forward the label job to the designated label printer. BENS processing functions can be used where needed for conversion, printer-specific adjustments or barcode and label processing. This enables production, warehouse or shipping labels, for example, to be routed to the appropriate devices, including across multiple locations.

Direct link to this question

Answer: Yes. Zebra printers can be integrated into SAP cloud printing scenarios if the output format and printing path are compatible with the specific model. ZPL or other Zebra formats, printer resolution and the actual media size used are particularly relevant.

How Suchy MIPS helps: BENS OMS Print Hub can manage Zebra devices as destinations and forward SAP print jobs to them. If the incoming data stream is not directly compatible with the printer, BENS processing functions can be used for conversion or adaptation. For Zebra and other thermal printers, testing with the specific model and actual resolution is particularly important because 203, 300 and 600 dpi are not freely interchangeable.

Direct link to this question

Answer: Stapling, hole punching or folding only work if the destination device or finisher supports the required function and the print data or job tickets contain the appropriate control information. Support must therefore always be checked for each printer model and configuration.

How Suchy MIPS helps: BENS can add this finishing information centrally to the printing process. Depending on the device and data format, job tickets, driver information or BENS plugins can be used to control functions such as stapling, hole punching, folding, duplex printing or paper selection. BENS OMS Print Hub can also retrieve SAP Print Profiles; additional BENS processing can supplement them where SAP-side settings are insufficient for the destination device.

Direct link to this question

Answer: Paper tray selection depends on how the destination device addresses its trays and how the information is transmitted to the printer. Possible methods include SAP print profiles, driver settings, PCL/PostScript control commands or an OMS. The key requirement is that the logical request corresponds to the actual tray on the specific printer model.

How Suchy MIPS helps: BENS knows the configured destination device and can implement tray selection through appropriate print control, depending on the data format and printer. For example, one form can be printed on letterhead from tray 2 and another document from the default tray. In heterogeneous printer environments, BENS can handle device-specific implementation centrally instead of reproducing it in every SAP application.

Direct link to this question

Answer: Duplicate printouts usually arise within a very small window of uncertainty: a job has already been transmitted to the printer, but the acknowledgment is lost because the connection is interrupted. The system then cannot determine conclusively whether printing has actually started. Outside this special case, unique job IDs and clearly defined status transitions should prevent the same job from being sent more than once.

How Suchy MIPS helps: BENS processes print jobs in a controlled manner and generally maintains their sequence according to the FIFO principle. A job is not simply discarded because its destination is temporarily unavailable. BENS normally sends a print job to its destination only once; the main potential risk of duplication lies in the short period between completed transmission and the printer acknowledgment still being outstanding. Logging and job history make such exceptional cases traceable.

Direct link to this question

Answer: SAP BTP provides print queues and defined interfaces for connecting external printing systems. A local or external printing component retrieves the jobs from the cloud and sends them to the physical printers. The exact setup depends on the BTP environment or SAP Print Service being used.

How Suchy MIPS helps: BENS OMS Print Hub supports SAP BTP printing scenarios. Print queues are created in BTP and made accessible to technical BENS users. BENS retrieves these queues, maps them to virtual printers and physical destinations, downloads and processes jobs, and then updates the job status in BTP. The BENS web panel also displays queue mappings, Print Profiles, job details and debug logs.

Direct link to this question

Answer: SAP_COM_0466 represents pull integration: the external printing system checks SAP for new jobs and downloads them. SAP_COM_0467 represents notification integration: SAP notifies the external OMS of new jobs; the actual job retrieval and status updates then take place through the designated interfaces. Both approaches solve the same basic problem but differ in how the OMS learns about new jobs.

How Suchy MIPS helps: BENS OMS Print Hub is being developed for the new SAP OMS integration scenarios and certification specifications. Project planning must establish which integration method is supported and released in the SAP and BENS versions being used. Regardless of the method, the core tasks remain the same: identify the queue, retrieve the job, determine the destination, process it, output it and report the status back.

Direct link to this question

Answer: Yes. Pull-based printing architectures in particular are designed for the local component to establish an outbound connection to the cloud. The cloud then does not require direct access to the internal company network, and the local printer does not need to be accessible from the internet.

How Suchy MIPS helps: BENS OMS Print Hub can retrieve print jobs from the cloud through SAP interfaces and then output them in the local or connected printing network. If applications, devices or data sources also need bidirectional communication between cloud and on-premises environments, BENS SecureConnector can secure the connection. It provides a persistent, encrypted communication channel without connecting entire networks as a traditional site-to-site VPN would.

Direct link to this question

Answer: A secure architecture should avoid making printers or local servers directly accessible from the internet wherever possible. Appropriate measures include encrypted connections, technical users with minimal permissions, protected credentials, traceable logs and clearly defined communication paths. The measures required depend on whether jobs are only retrieved or whether additional bidirectional communication is needed.

How Suchy MIPS helps: For these scenarios, BENS SecureConnector provides a persistent, encrypted, bidirectional connection between defined applications, devices and data sources. In cloud-to-on-premises scenarios, the local connector initiates the outbound connection, so local systems do not need to be directly accessible from the internet. Unlike a traditional VPN, SecureConnector does not connect entire networks, but only the communication links actually required. For SAP print queue scenarios that use only pull integration, BENS OMS Print Hub can also operate without connecting entire networks.

Direct link to this question

Answer: In principle, yes. When using multiple SAP cloud systems, access credentials, queue names, clients or system assignments and routing must be clearly separated. Every print job must be traceable to its source system and queue at all times.

How Suchy MIPS helps: BENS OMS Print Hub can work with multiple SAP systems or multiple print queue configurations and map the received queues to shared or separate print destinations. During operation, distinct virtual printers, destination definitions and job information help keep the systems clearly identifiable. For large environments, the organization of authentication, permissions, logging and, where applicable, separation between locations should also be defined.

Direct link to this question

Answer: An output management system (OMS) is the layer between the application that generates a document and the actual output destination. Depending on the solution, it handles tasks such as printer mapping, routing, data conversion, print control, error handling, status tracking and centralized administration. An OMS therefore complements SAP output control with technical processing and distribution functions rather than replacing it.

How Suchy MIPS helps: Suchy MIPS offers different BENS components for this purpose. BENS OMS covers traditional SAP output management scenarios; BENS OMS Print Hub extends the concept to cloud-based SAP environments such as SAP S/4HANA Cloud Public Edition and SAP BTP. Print Hub retrieves SAP print queues, maps them to virtual printers and destinations, processes jobs, reports their status back to SAP and archives processed jobs for analysis or reprinting. BENS Server provides additional functions for data conversion, filters, plugins and print distribution.

Direct link to this question

Answer: An external OMS is particularly worthwhile when printing requirements go beyond “send a document to a printer,” when many printers need to be managed or when multiple SAP systems form an environment that requires consistent printer configuration. Typical reasons include many locations, heterogeneous printer models, automatic destination selection, printer pools, conversion, finishing, centralized error analysis, reprinting or a desire to decouple printing logic from the SAP application. For a small number of printers and straightforward standard requirements, an SAP standard solution may be entirely sufficient.

How Suchy MIPS helps: BENS is designed primarily for more complex printing environments that are important to business operations. Routing and destination mapping are managed centrally, print data can be processed or converted, jobs remain traceable and cloud print queues can be integrated through BENS OMS Print Hub. This avoids implementing specialized printing requirements separately in every SAP application or on every workstation.

Direct link to this question

Answer: Yes. In addition to SAP Cloud Print Manager, SAP provides for the integration of external output management systems. Whether an alternative is worthwhile depends on the SAP release, communication scenario, print functions required and preferred operating model. The deciding factor is therefore not just whether printing is possible, but what routing, processing, monitoring and support requirements need to be met.

How Suchy MIPS helps: Suchy MIPS offers external BENS solutions for different SAP architectures. BENS OMS and BENS OMS Panel address traditional SAP NetWeaver, S/4HANA on-premises and private cloud scenarios. BENS OMS Print Hub is designed for cloud-based SAP environments such as SAP S/4HANA Cloud Public Edition and SAP BTP and follows the SAP certification specifications S/4HC-PUB-PRINT-OMS, BTP-PRINT-OMS and S/4HC-PRINT-OMS. In addition to transporting print jobs, BENS provides centralized destination mapping, detailed job analysis, status reporting, archiving and the option to use additional BENS processing functions.

Direct link to this question

Answer: SAP Spool is part of the traditional SAP printing architecture: print jobs are managed in the SAP system as spool/output requests and assigned to output devices. In cloud scenarios, print queues serve as defined handover points through which external printing components retrieve the documents. The concepts therefore fulfill a similar intermediary role but differ in their technical implementation.

How Suchy MIPS helps: Suchy MIPS supports both environments. BENS OMS has long been used for traditional SAP and spool-based output management scenarios. BENS OMS Print Hub takes on this role in modern SAP cloud architectures by reading print queues, processing jobs, mapping them to physical destinations and reporting status information back to SAP. This allows existing BENS printing logic to be moved gradually to new SAP architectures.

Direct link to this question

Answer: Complete monitoring requires a distinction between two levels. First, the print job: was it retrieved from SAP, processed and handed over to the destination? Second, the physical device: is the printer online, does it have paper and toner, or is there a fault? A single system does not necessarily cover both levels in equal depth.

How Suchy MIPS helps: In traditional SAP OMS scenarios, BENS OMS Panel provides seamless tracking of print jobs from SAP Spool through BENS Server to handover to the physical output device. BENS OMS Print Hub provides the corresponding job and status tracking in cloud-based SAP scenarios. PrintRadar adds the device-level view and works closely with BENS OMS Panel: monitored printers are linked to the corresponding printer definitions on BENS Server and, where technically supported, directly to the physical device’s web interface. This allows an administrator to switch between the print job, BENS printer definition and device from a central view and open the web interface of supported printers with a click.

Direct link to this question