screen output without connection to user

[Michael Stecher]

Stephan / Monica,
 
  I am doing a lot of work currently with BAPI's and RFC Function =
modules being called from outside SAP and am finding that even in these =
modules that are designed to be used from outside the system (implying =
background mode) SAP has coded message statements into the function =
modules.  I have reported several to OSS but they will not change the =
code for this.
 
  You can try to track this down by calling the function module in test =
mode from SE37.  If you are getting an error popup, the best answer from =
OSS was to create a new (custom) function module with the same interface =
as you are trying to call.  Within this new function module call the =
function module that you want to have run, but add a new exception code =
called ERROR_MESSAGE.  With this exception code any message statements =
will not trigger a popup, but will return to the new function module =
with sy-msgid, sy-msgty, sy-msgno, sy-msgv1, sy-msgv2, sy-msgv3, and =
sy-msgv4.
 
Mike Stecher
 
-----Original Message-----
From: Becker, Stephan [mailto:stephan_becker.ext at siemens.com]
Sent: Friday, January 30, 2004 4:03 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: screen output without connection to user
 
 
Hi Monica,
 
This happens mostly with call transactions, but also with some function
modules. Unfortunately, Workflow is not completely "honest" to the rest =
of
the system when it comes to declaring whether it's running in =
background..
something to do with the different background modes and the RFC, I =
guess..
in any case, many function modules have switches in them where they try =
to
ascertain whether they're being run in background, and maybe you can =
find
that switch and set it when you call the module..
 
Regards,
Stephan