AW: Workflow Attachment on System-Overlapping possible ?

[Seiz, Gert]

Hy Stephan,
I guess this is a great Idea.
I will try this.
Many thanks, also to Alon
 
Regards=20
Gert
 
 
-----Urspr=FCngliche Nachricht-----
Von: Becker Stephan (extern) =
[mailto:Stephan.Becker.ext at mchw.siemens.de]
Gesendet: Mittwoch, 23. Januar 2002 18:21
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Workflow Attachment on System-Overlapping possible ?
 
 
Gert,
I would probably try to copy the attachments to system B, and then =
exchange
the original attachment numbers with the new ones before sending the
workflow over. Ensure you don't save the new numbers on system A.. This
solution assumes no attachments are being changed or added in system =
B..=20
Have a look at so_document_move_api1, you should be able to copy to a =
remote
location directly..
Stephan
 
-----Original Message-----
From: Raskin, Alon (Soliance) [mailto:ARaskin at cps-satx.com]
Sent: Mittwoch, 23. Januar 2002 17:55
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Attachment on System-Overlapping possible ?
 
 
I am not too familiar with BW so maybe somebody else wants to comment=20
BUT..
 
I cant see how you can attach an object to a workflow which doesn't =
exist in
the system it is running in. If that object does a EXISTENCECHECK then =
it
fail and the workflow will probably error. I am only speculating here.. =
not
sure.
 
Attaching the object should allow the user to view that object by =
clicking
on it. I don't see how that could happen in that system. Unless there =
is a
way of telling SAP of executing a RFC back to system A to get the data. =
I am
not aware of such functionality.
 
Can you just pass the info to System B as text?
 
Regards,
 
Alon Raskin
Workflow Advisor - Soliance=20
(xtn. 3183)
 
 -----Original Message-----
From:   Seiz, Gert [mailto:gert.seiz at sap.com]=20
Sent:   January 23 2002 10:36
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        AW: Workflow Attachment on System-Overlapping possible =
?
 
Hy Alon,
on System B I don't have access to the tables for the object.
 
On System A the attachment can be created in Backround for the Object =
via
standard routines.
In this workflow will start a backround step an another workflow on =
system B
and is waiting for response.=20
System B is an Business Warehouse.
On System B the Workflow is running on a dummy - Object.
Only approve or reject depending from the attachment should be possible =
in
one step.
After this the workflow on system A could be reaktivated via an event =
or
what ever, and is making the next steps.
 
Regards Gert
 
-----Urspr=FCngliche Nachricht-----
Von: Raskin, Alon (Soliance) [mailto:ARaskin at cps-satx.com]
Gesendet: Mittwoch, 23. Januar 2002 17:17
An: SAP-WUG at MITVMA.MIT.EDU
Betreff: Re: Workflow Attachment on System-Overlapping possible ?
 
 
Depending on your requirements, you could create the attachment on =
System B
before calling SWU_START_WORKFLOW.
 
Will that work for you?
 
Alon Raskin
Workflow Advisor - Soliance
(xtn. 3183)
 
 -----Original Message-----
From:   Seiz, Gert [mailto:gert.seiz at sap.com]
Sent:   January 23 2002 9:40
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Workflow Attachment on System-Overlapping possible ?
 
Hy there,
we have a scenario for start a workflow on system A and create an =
attachment
in backround for binding to the Workflow.
After this step an other workflow should start on stytem B via
SWU_START_WORKFLOW e.g.
On this workflow it should be also possible to have access to the =
attachment
on the system B.
But you can fill the parameter ATTACHMENT_LIST only with an ID . So you =
have
a reference and not a copy of the attachment.
So you doesn't have the ID on the second System.
Does anybody has experience with this ?
System A 4.5B
System B 4.6C
Regards Gert