SAPWIN

[Former Member]

When I try to print to SWIN from ME22N, I get an error "Frontend Unavailable". If I use LOC1 (SAPLD), it works fine. Can anyone help? Do I have to create a sapscript form to print to SWIN?

Thanks,

-- Jackie

[Former Member]

When I try to print to SWIN from ME22N, I get an error "Frontend Unavailable". If I use LOC1 (SAPLD), it works fine. Can anyone help? Do I have to create a sapscript form to print to SWIN?

Thanks,

-- Jackie

[Former Member]

Hi

Check in the SPAD transaction how SWIN is defined

Max

[Former Member]

Device Type: SAPWIN

Device Class: Standard Printer

Host Spool Access Method: G: Frontend print with control technologie

Host Printer: __DEFAULT

[Former Member]

Hi

In my system there's not the "Host Spool Access Method" G, but F.

Anyway try to check if LOC1 is defined as SWIN.

The sapscript should be independent from the print, only the output can be changed because each SAP printer can used different device type.

Max

[Former Member]

There was a note, 821519, that described how to get the "G" host spool access method. We are using LOCX as the sapwin printer. LOC1 - 5 are SAPLPD.

[Former Member]

Hi

Try to see the note 901244:

Symptom

When you use access method 'G' for printing, problems may occur sporadically. The program assigns the status 'Front end unavailable' to some output requests.

This always happens if you start printing from an update work process. However, this is information is not clearly available to you.

Other terms

Front-end printing, access method 'G', printing with control technology, update, update process

Reason and Prerequisites

Up to now, it has not been possible to start a front-end control (the printer display window) when you start a printout from an update work process.

Solution

Import the relevant kernel patch and Support Package. Also, until further notice, you must set the profile parameter rdisp/gui_from_spool to '1' so that the new behavior is released. This parameter is not known in transaction RZ10; you can ignore the error message that appears when you check the profile.

IMPORTANT: If you implement only the correction instructions instead of the Support Package, you must manually remove the TRACE import parameter of the RSPO_LOCAL_PRINT function module using transaction SE37.

For Releases 46C and 46D, import Development Workbench Patch 2174

For Releases 620 and 640, import Development Workbench Patch 104.

For Release 700, import Development Workbench patch 36.

Max

[Former Member]

What is a development workbench patch? Is it the same as a support pack?

[Former Member]

I tried adding the profile parameter to my system, but I'm still getting the same error. Any other thoughts?