Skip to end of metadata
Go to start of metadata


Connection or Printing issues related to the Connector for SAP Applications using BC-XOM communication.


This article outlines how to verify the necessary information required to configure the Connector for SAP to receive requests via BC-XOM. This is more of a list of data points than a tutorial but should be helpful when validating a customer environment. This does not cover the configuration of the CLI as access to the SAP server is required and should be handled by the SAP Basis team.

General Case

This information is for the general case and may not cover every deployment.


  1. Open SAP interface.
  2. Access Spooler Admin (SPAD).
  3. Enable Extended admin, or Full admin.
  4. Access Output management systems tab.
  5. Click on Display for Logical Output Management Systems (LOMS).
  6. Double click on the OMS Name.
  7. Verify the Target for callback value.

  8. Go Back (F3) twice and click Display for Real Output Management Systems.
  9. Note the Real OMS Name (ROMS).
  10. Access the Loftware Connector UI System Configuration.
  11. Make sure that the SAP call back matches the LOMS Target for callback.
  12. Make sure that the ROMS matches the ROMS Name.

  13. Configuring the sapwrfc.ini file
    1. DEST= any value as long as it matches the related entry in the NLINK Configuration.xml file.
    2. TYPE= A for Single instance BCXOM configuration / B for R/3 Load Balancing.
    3. ASHOST= the SAP Connector Server Name (ecc60js5) from SAP Logon 740 interface System menu, Status, Host field.
    4. SYSNR= System number (30) from SAP Logon 740 interface System menu, Status, “Server name” (ecc60js5_js5_30).

  14. Configuring the NLINK Configuration.xml
    1. XmiCallback[X]Destination= must match a DEST value in the sapwrfc.ini file.
    2. XmiCallback[X]Client= Client number used when signing in to SAP (i.e. 900).
    3. XmiCallback[X]UserID= User Configured in SAP so the connector can log in to update job status.
    4. XmiCallback[X]Password= Encrypted password for the UserID above. Use NLINKPassword.exe to encrypt the password.


Load Balancing

While there is a bug in the UI that prevents the entry of duplicate External System Numbers (ESN), the Provda Database does not have a unique constraint on that column. Load balanced systems should use the same ESN for all callback System Configurations.

Access the Provda database using Microsoft Access and modify the xom_callback_target_xref so that the load balanced systems use a single ESN. Modify the NLink Configuration.xml file removing duplicate entries, making sure that there are no empty entries in the middle of the list and then adjust the ESN values to match.

Article Number



All supported versions of the Loftware Connector for SAP Applications


Any supported environment for the Loftware Connector for SAP Applications