AW: SOFM.ImportFile

[Falk, Simone]

Hey there is an easy answer:
 
Why use background task ? Use a normal task with the same role as the =
last
normal task. USe directly forwarding and the task will be performed as =
if
it was a background task. The user will not see that he is performing =
this
task.
 
Best Regards
Simone
 
-----Urspr=FCngliche Nachricht-----
Von: Soady, Phil [mailto:phil.soady at sap.com]
Gesendet: Dienstag, 19. August 2003 13:30
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: SOFM.ImportFile
 
 
Simone is right;
in a few more words that may help explain:
 
A background task has no connection to the front end machine.
There is no SAPGUI connection. It has no way of knowing where
nor should it from an security point of view be able to write to any PC =
on
the network.
 
Only access to the Application server is possible in background tasks.
If the front/end can provide a share and the application server
can map to the share, then you can access the PC indirectly.
This of course is a deliberate action to expose the PC to the app =
server.
It also assumes the PC is on at the time.
=20
Note: most access to information on the Front End is made possible
via CALL "BACK" to the GUI.=20
CALL function XYZ destination "BACK".
No GUI connection, no front-end access.
 
The question remains what is a logical relationship between a PC and =
the
SAP system. Why should the SAP system pick PC XYZ to access ?=20
When you have answered this question, you will know the solution.
 
If the answer is the logical connection is the "current user", then
a background task is not suitable.
 
If the answer is where the user last did something...
then the user must "share" there resource , provide the connection =
details
and pass this into the workflow.  The file can then be sent via the
application server. This is however a scenario that should be seriously
questioned. Why is a file chasing a user asynchronously to the last PC =
they
used ? What if the PC is off ? What if they are no logged on somewhere =
else
? ... etc.
 
hth
 
Phil
 
 
Phil Soady
Senior Consultant
SAP Australia
Level 1, 168 Walker Street, North Sydney 2060, Australia.
M   +61 412 213 079
E   phil.soady at sap.com
http://www.sap.com
=20
 
-----Original Message-----
From: Falk, Simone [mailto:SIMONE.FALK at airbus.com]=20
Sent: Tuesday, August 19, 2003 8:57 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: AW: SOFM.ImportFile
 
Hello Jeffrey
 
if you import a file, you need a frontend. So you cannot use this =
method as
a Background task. ( see WS_DOWNLOAD - same problem )
 
Ciao
Simone
 
-----Urspr=FCngliche Nachricht-----
Von: Jeffrey Rappaport [mailto:businessworkflow at consultant.com]
Gesendet: Montag, 18. August 2003 19:25
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: SOFM.ImportFile
 
 
All,
 
   We're trying to use the above Method as a Background task instead
of Dialog. After changing the settings & testing through SWUS, it
works fine, but, when we trigger the Event in real time, it hangs up
at this step. Has anyone encountered this problem before?
 
Thanx,
 
Jeffrey A. Rappaport
Business Workflow, LLC
Jeff at Business-Workflow.com
www.Business-Workflow.com
 
--
__________________________________________________________
Sign-up for your own personalized E-mail at Mail.com
http://www.mail.com/?sr=3Dsignup
 
CareerBuilder.com has over 400,000 jobs. Be smarter about your job =
search
http://corp.mail.com/careers
 
This mail has originated outside your organization,
either from an external partner or the Global Internet.=20
Keep this in mind if you answer this message.
 
This mail has originated outside your organization,
either from an external partner or the Global Internet.=20
Keep this in mind if you answer this message.