Defining an Output Device for Printing with Output
Management Systems
Use
You want to make a output device that is served by an external output management system (OMS)
accessible for SAP printing and (optionally) faxing. To do this, you must create the corresponding
device definition in the SAP System.
This definition creates an output device that forwards the formatted print data to the OMS. The
OMS outputs the data independently of the SAP System.
Prerequisites

You require authorization to create output devices.

You must have already defined the external Output Management System (OMS) in the SAP spool system. The
definitions for the real OMS (ROMS) and logical OMS (LOMS) must already exist. For more information, see
Integrating the Spool System into an External Output Management System.

If you cannot already print from your host systems to your OMS output device, you must first install the output
device in the OMS.
Procedure
If you want to create an SAP output device definition for printing using an Output Management
System (OMS) follow the procedure below:
...
1. Call Spool Administration (transaction SPAD), and, on the Devices/Servers tab page, choose Output
Devices.
2.
3.
If you are not in change mode, switch to this mode by choosing
You can now do the following:
1. 
Change.
You can create a new device definition by choosing Output Device  Create.
2. 
4.
You can use an existing device definition as a template.
To do this, click the entry for the output device that is to be used as a template, and choose Output
Device  Create Using Template.
Specify the name of the output device and fill out the mandatory fields of the individual tab pages as follows:
Field
Input
Device
Attributes Tab Device Type
Page
Enter the device type defined in the SAP System for your printer
model.
For printing under Microsoft Windows, you can also use the
generic SWIN device type. This lets you use any device
supported by Microsoft Windows, even if the device type is not
defined in the SAP System.
For a list of the device types delivered, see SAP Note 8928 in
the SAP Service Marketplace.
Spool Server
Enter the name of the SAP spool server (application server with
the spool work process) that is to prepare the output for this
device.
Authorization
Group
To assign the output device to an authorization group, enter the
name here. For more information, see Authorization Groups for
Output Devices.
Host Spool
Access
Method
Access Method
Enter E, for printing using of an external output management
system.
Host Printer
Enter the name of the output device in the external OMS.
Logical OMS
Choose the LOMS to which this device should be assigned. A
LOMS specifies how the device is to be accessed in the
external output management system (OMS).
For more information, see Assigning OMS Output Devices to
Logical OMSs.
5. Optional: Classify the device. To do this, choose Edit  Classification and then the appropriate output type
classification for this device. Although classification of output devices is optional, it provides this advantage:
If you also classify your spool servers, the spool system checks that the device and server classifications match.
This helps to ensure an optimal output configuration.
6.
If you are preparing to assign a mass printer to a time-critical production server, then the spool system
warns you of this disparity.
Save the device definition and exit.
Result
The OMS output device is immediately available to SAP users and programs for printing ABAP lists
and SAPscript/Smart Form documents.
Integrating the Spool System into an External Output Management System
Purpose
External output management systems control printing operating in large, complex IT environments. You can
integrate the SAP spool system into an external output management system (OMS) of this type so that you
can use the functions of the OMS from your SAP System.
An example of a function of an external OMS: The OMS distributes a print request to 20 different printers.
You only need to define one output device in the SAP System that points to this OMS. If you print using
this output device, the request goes to the OMS, which then redirects it to the 20 printers. Without the
OMS, you would have to print 20 times in the SAP System.
Prerequisites

XOM Interface
You require the XOM application programming interface to be able to use your OMS for printing from an SAP
System.

Compatible OMS:
Your OMS must be compatible with the SAP System or you must implement the OMS interface yourself.
If you already have an OMS installed, then you must upgrade it so that it supports the XOM interface.
If you are buying an OMS, it should be one certified for the XOM interface.

Local Access
An OMS and all of the devices it serves must be "local" to all SAP spool servers. This means that the OMS
commands issued by SAP spool servers must be executable on the host system on which the corresponding
SAP spool server is running.
Explanation: An SAP R/3 spool server stores output data for an OMS device in a file on the host where the server
is running. This file is referenced in the OMS Submit command issued by the server, and the file must be
accessible to the OMS.
For more information about certified OMS products and implementing and certifying the OMS interface, see
http://www.sap.com/partners/software/.
Process Flow
Follow this procedure for each OMS you want to integrate into SAP output (if you have more than one OMS):
...
1. Define the OMS as a real OMS (ROMS).
The ROMS is the definition of the external OMS in your SAP System and specifies the properties of the external
OMS, such as whether the OMS is started using a command line or an RFC, or whether the status of the print
request is determined using polling (the SAP System queries the status) or callback (OMS informs the SAP
System about the status).
See: Defining a Real OMS (ROMS) in the SAP System
2. Optional: You can take an “inventory” of the output devices and if necessary assign your output devices to
different logical OMSs (LOMSs). In this way, you can categorize output devices that use the external OMS in the
same way and assign each category to a different group (LOMS).
Production printers should be traced using RFC callback, non-critical printers only using polling. You
should allow a LOM for each group. After you have defined this LOM (see step 3), you must assign the
devices to this LOM using the device definition.
Although classification into different LOMSs is optional, you must however create at least one LOMS. This is
because when you want to create an output device that forwards its print requests to an OMS (access method E),
you must assign it to an LOMS. It is not possible to assign devices directly to the real OMS.
See: Assigning Output Devices to Logical OMS (LOMS)
3. Define one or more logical OMSs (LOMS) in the SAP System. Only one is required.
See: Creating a Logical OMS
4. Define one or more sets of operating system specific commands.
You need at least one command set for each operating system on which your SAP R/3 servers are running.
See: Defining OMS Command Sets for LOMS
5. Make one or more of the OMS output devices available for use in SAP printing and faxing.
To do this, you must create the corresponding device definitions in the SAP System.
See: Defining an Output Device for Printing with Output Management Systems.
6. If you are working in a test system, replicate your OMS definitions in other SAP R/3 Systems.
See: Transporting OMS Definitions Between Systems.
7. During the production use of your OMS: If you are using RFC callback for reporting OMS job and device
status, you can force reconfiguration of the callback client.
This is an optional step. Usually the OMS callback client reconfigures itself.
See: Triggering OMS Reconfiguration
Defining a Real OMS (ROMS) in the SAP System
Use
To be able to integrate the SAP spool system into an external output management system (OMS), first define
the OMS as a real OMS (ROMS) in the spool system. The ROMS definition specifies the properties of the
external OMS to the SAP System. Not every OMS offers all of the operations that the OMS interface allows.
Therefore, when you create the real OMS in the SAP System, you should specify the options that are
supported by the OMS you are using.
Prerequisites

Your external OMS system should be installed and ready to run before you define it in the SAP System.

OMS manufacturers have the option of delivering a configuration file to you. If such a file is available, then
uploading it into the spool system creates the ROMS and operating system specific commands for you.
Before proceeding, check to see if such a file is available for your OMS.
Procedure
There are two ways to create a ROMS, depending on whether your OMS vendor provides a configuration file
or not.
If the OMS vendor provides a configuration file, you only need to upload the file. The ROMS is then
created for you. For more information about uploading, see Importing OMS Definitions.
If no configuration file is provided, create a ROMS definition in the SAP System as follows:
...
1. Call transaction SPAD, and choose Extended Administration or Full Administration.
2. Then, on the Output Management Systems tab page, choose Real Output Management Systems.
The list of defined ROMSs appears.
3.
4.


If you are not in change mode, switch to this mode by choosing
You can now do the following:
Change.
You can create a new ROMS definition by choosing Real OMS  Create.

You can use an existing ROMS definition as a template.
To do this, click the entry in the list of ROMSs for the ROMS to be used as a template, and choose
Real OMS  Create Using Template.

5. Enter the name of the ROMS and a description.
6. Fill out or edit the fields of the OMS Attributes subwindow using the OMS documentation.
In this subwindow, you select which function are implemented in the OMS, such as whether the vendor has
implemented OMS command line commands or RFC function modules that can be called from the SAP System.
7. You can enter an initialization instance in the SAP Configuration subwindow.
Generally, SAP expects that OMS commands can be issued from any SAP server. However, it is possible that an
OMS requires that the initialization command be issued at a particular host. In this case, you can use the
Initialization Instance field to meet this requirement.
8. Save the ROMS definition and exit the function.
9. If you are using callback (the job status is returned by the OMS), you must define the SAP user and the
password for the callback client.
The user name and password are used to log onto the SAP System if you are using callbacks. To define user
names and passwords, choose Tools  Administration  User Maintenance  Users. Note that the values
entered in the OMS are the same. For additional information, see the
User Maintenance Manual.
Create the user in the logon client of the callback client. To be able to log on to the CCMS XOM-API, the user
requires authorization for S_XMI_PROD (Authorization for external management interfaces (XMI)) with the value
XOM for the Interface ID field.
For example: S_XMI_ADMIN or S_XMI_XOM_A.
Result
Your ROMS definition for identifying an external OMS is finished. You can now define logical output
Management systems (LOMSs) and OMS printers that reference the ROMS.
Importing OMS Definitions
Use
You want to import an ROMS/LOMS definition from an OMS configuration file:

that has been provided by your OMS supplier

that you have exported yourself from a test or another SAP System.
If such a configuration file is available, then uploading it into the SAP spool system creates the ROMS/LOMS
and operating system specific commands for you. This means that you do not have to create the
ROMS/LOMS definition yourself in the SAP System.
Prerequisites
You must have copied the configuration file to one of the following directories:

A directory on your frontend PC or on your workstation

A directory that you can access from the servers of the SAP target system (the system into which you want to
import the file).
You can copy the file to the tmp directory of the SAP server at which you are logged on or to the global
work directory of the SAP System.
Procedure
...
1.
Log on to the SAP System into which the file is to be imported.
Choose Tools  CCMS  Spool  Spool Administration (transaction SPAD) and then Utilities  For output
management system  Import.
2. Specify the following on the selection screen:
–
In Export/Import file name field, enter the full path name of the configuration file.
–
file.
Select Server or Frontend computer depending upon where you have copied the configuration
–
Select Import, Execute import, and Generate log.
3. Run the report.
The report displays a list showing the ROMS and LOMS definitions that have been imported into the SAP R/3
System.
Result
You have imported ROMS and LOMS definitions into the SAP R/3 spool system.

If you have imported a configuration file that was provided by an OMS maker, then your SAP System now has
the starter set of definitions provided by the manufacturer.

If you have imported a file that you created yourself, then the OMS definitions that you exported have been
replicated in your current SAP System.
You can now make any changes necessary (such as altered server names) to the definitions.
Creating a Logical OMS
Use
After you have defined the real output management system (ROMS) during the integration of the SAP spool
system into an external output management system, you can define one or more logical OMS (LOMS) as the
next step.
However, you must certainly define at least one LOMS. This is because when you want to create an output
device that forwards its print requests to an OMS (access method E), you must assign it to an LOMS. It is not
possible to assign devices directly to the real OMS.
Defining additional LOMSs is optional. It is useful, if you want to combine your output devices into different
groups that use the external OMS in different ways. For more information about the LOMS concept and its
uses, see Organizing OMS Output Devices in Logical OMSs.
Prerequisites
You have defined the real OMS (ROMS) to which your LOMS definitions will refer.
Procedure
If you have imported a configuration file or a configuration file was delivered with your system, there is probably at least
one LOMS already defined for you. If this is not the case, or if you require additional LOMSs, you can create LOMSs as
follows in the SAP System:
...
1. Call transaction SPAD, and choose Extended Administration or Full Administration.
2. Then, on the Output Management Systems tab page, choose Logical Output Mgmt Systems.
The list of defined LOMSs appears.
3.
4.


Change.
You can create a new LOMS definition by choosing Logical OMS  Create.

You can use an existing LOMS definition as a template.
To do this, click the entry in the list of LOMS for the LOMS is to be used as a template, and choose
Logical OMS  Create Using Template.

5.


If you are not in change mode, switch to this mode by choosing
You can now do the following:


6.
Enter the most important attributes for the LOMS:
Name and description
ROMS that this LOMS uses
Choose
to copy the settings for the selected ROMS, which you can then edit if necessary.
You can also select an SAP server as a tasking target (on which the OMS runs) or as a callback target.
7. Select a command group, if any have been defined. Otherwise, enter a character to define a command
group.
Local commands: If you want to define commands only for this LOMS, then select Local as the command group.
When you define a command group, the commands will be used only for this LOMS. The command group cannot
be selected from other LOMSs.
8. If you are using callback (reports about job status by the OMS): Specify additional options and parameters
on the OMS Configuration tab page, if necessary.
If you want to adjust the message filtering, choose
9. Save the LOMS and exit the function.
.
Result
Your LOMS definition that specifies how SAP output devices are to access an external OMS is complete.
You can now define additional LOMSs or define the commands that are required by LOMSs.