Write from R/3 to Unix

[Dart, Jocelyn]

Hi Mary,=20
There is a collection of useful list processing routines in function =
group
SLST including=20
LIST_TO_SPOOL which should get you close to what you want. =20
=20
If you are looking for useful function modules, you can often find =
these in:
* The reuse library - transaction SE83 (requires a 4.6 or above system)
* The R/3 library documentation, e.g. under Basis > ABAP Workbench >
Extended Applications Function Library
* Or you can put a query into OSS or http://service.sap.com
<http://service.sap.com> .
=20
As this is a WORKFLOW distribution list and not an ABAP distribution =
list we
would=20
appreciate if you did not ask ABAP questions here. =20
=20
=20
Regards,
=09
Jocelyn Dart=20
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow) =
 
SAP Australia
Email  <mailto:jocelyn.dart at sap.com> jocelyn.dart at sap.com
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
-----Original Message-----
From: Carroll, Mary L [mailto:mary.carroll at gwl.com]
Sent: Friday, 25 January 2002 10:38 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Write from R/3 to Unix
 
 
Thanks for your response, Joe.
=20
Actually, I didn't state my question properly.  I do know how to use =
the
MESSAGES INTO extension but I want everything defined by a WRITE =
statement
to go to a flat file, not just transaction messages.  This would =
include
report header lines, end-of-job counts, error messages I have defined =
myself
(writing a message and stopping the program before going to the call
transaction if, for example, the input file does not net to zero).=20
=20
Again, I know I can do it with the TRANSFER statement but was hoping =
for
something similar to a SPOOL or DESTINATION statement that would write
remotely.
=20
Thanks for any more input you might have,
=20
Mary
 
-----Original Message-----
From: Graf, Josef [mailto:josef.graf at sap.com]
Sent: Thursday, January 24, 2002 9:29 AM
To: SAP-WUG at mitvma.mit.edu
Subject: AW: Write from R/3 to Unix
 
 
Hi Carroll,
use the extension "MESSAGES INTO <internal table>" of the "CALL =
TRANSACTION"
statement.
Then all messages will be in the <internal table> after the CALL =
TRANSACTION
and can be
easily written to the UNIX file system.
Best regards=20
Joe
 
-----Urspr=FCngliche Nachricht-----
Von: Carroll, Mary L [mailto:mary.carroll at gwl.com]
Gesendet: Donnerstag, 24. J=E4nner 2002 16:52
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Write from R/3 to Unix
 
 
 
I'm an ABAP programmer, working on an R/3 (4.6c) install. I'm writing a
program that calls a transaction. When you execute the program in the
foreground, R/3 transaction error messages are displayed as output.  I =
want
to write these messages to a flat file at the unix (AIX) level rather =
than
(or in addition to) having them display at the terminal.  I realize I =
can
write TRANSFER statements in the ABAP code to accomplish this but what =
a
pain!  Can anyone help?
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020125/bdf94fea/attachment.htm