AW: Workflow Attachment on System-Overlapping possible ?

[Seiz, Gert]

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