Workflow Transport Problems

Richard Schot Richard.Schot at avelon-it.com
Thu Mar 22 11:17:46 EST 2001


Hi Wayne,
We are on level 4.6C level 13. We applied the oss note 378487 recently ; can
you check if you also used the same version? We applied version 20 valid from
13.03.2001. We did not generate a new version of it - the workflow definition
now functions correctly (using the correct version). Maybe another solution
after applying the note is re-generating a new version and transport it.
I think that another transport of the business object will not solve your
problem.
 
Regards,
Richard Schot
>
Business Workflow Consultant
_____________________________
Avelon
visit us at www.avelon-it.com
 
 
>=3D=3D=3D=3D=3D Original Message From SAP Workflow Users' Group
<SAP-WUG at MITVMA.MIT.EDU> =3D=3D=3D=3D=3D
>My workflow was working in our Development System.
>
>We next applied the hot package upgrade which took up to hot pack level 23.
>We are on version 46b.
>
>I transported the workflow configuration from our Development system to our
>Test system.
>
>The workflow didn't work in the Test system.
>
>I applied the OSS note 378487 to our Test system.
>
>I re-transported the workflow definition (PFTC) to the Test system.
>
>Do I need to re-transport the business object definition (SWO1) to the Test
>system?  I didn't see anyway to force a transport creation without changing
>something.
>
>Do I have the steps in the correct order?
>
>Thank you,
>
>Wayne Carson
>Solvay Information Technologies
>WAYNE.CARSON at SOLVAY.COM <mailto:WAYNE.CARSON at SOLVAY.COM>
>
>
>        -----Original Message-----
>        From:   Richard Schot [SMTP:Richard.Schot at avelon-it.com]
>        Sent:   Thursday, March 22, 2001 9:00 AM
>        To:     SAP-WUG at MITVMA.MIT.EDU
>        Subject:        Re: Workflow Transport Problems
>
>        Hi Manfred,
>
>        We have the same problem in version 46C. Just a few days ago we
>received the
>        new version of note 378487 (currently version 20). After applying
>the note our
>        transport and activation problems have been fixed. Maybe this
>version can also
>        help you.
>
>        Regards,
>        Richard Schot
>
>        Business Workflow Consultant
>        _____________________________
>        Avelon
>        visit us at www.avelon-it.com
>
>        >=3D=3D=3D=3D=3D Original Message From SAP Workflow Users' Group
>        <SAP-WUG at MITVMA.MIT.EDU> =3D=3D=3D=3D=3D
>        >Hi,
>        >
>        >try transaction SWUD. With this tool you can check your
>workflowdefinition.
>        >In the past I had some transport problems but this transaction can
>help.
>        >
>        >jan
>        >
>        >-----Original Message-----
>        >From: Manfred Austrup [mailto:manfred_austrup at WestLB-Systems.de]
>        >Sent: Dienstag, 20. M=E4rz 2001 18:26
>        >To: SAP-WUG at MITVMA.MIT.EDU
>        >Subject: Workflow Transport Problems
>        >
>        >
>        >Hi,
>        >
>        >I have applied the following notes for repairing the workflow
>transport
>        >issue
>        >for R/3 release 4.6c (currently hot package 12): 378487 und 315515.
>        >
>        >Unfortunately the transporting still does not work! Everything is
>        >transported
>        >except the workflow definition itself. Any hints?
>        >
>        >Regards,
>        >
>        >Manfred Austrup
>        >
>        >WestLB-Systems GmbH
>        >Global Products SAP
>        >Department 771-80814
>        >V=F6lklinger Str. 4
>        >D - 40219 D=FCsseldorf
>        >Tel.:     +49 211 826-9054
>        >Fax:     +49 211 826-8344
>        >Mobil:  +49 178 826-9054
>        >E-Mail: Manfred_Austrup at Westlb-Systems.de
>        >
>        >
>        >|--------------------------------------->
>        >|Diese Nachricht ist vertraulich. Sie   |
>        >|ist ausschliesslich fuer               |
>        >|den im Adressfeld ausgewiesenen        |
>        >|Adressaten bestimmt.                   |
>        >|Sollten Sie nicht der vorgesehene      |
>        >|Empfaenger sein, so bitten             |
>        >|wir um eine kurze Nachricht. Jede      |
>        >|unbefugte Weiterleitung                |
>        >|oder Fertigung einer Kopie ist         |
>        >|unzulaessig. Da wir nicht die          |
>        >|Echtheit oder Vollstaendigkeit der in  |
>        >|dieser Nachricht                       |
>        >|enthaltenen Informationen garantieren  |
>        >|koennen, schliessen wir                |
>        >|die rechtliche Verbindlichkeit der     |
>        >|vorstehenden Erklaerungen              |
>        >|und Aeusserungen aus. Wir verweisen in |
>        >|diesem Zusammenhang                    |
>        >|auch auf die  fuer die Bank geltenden  |
>        >|Regelungen ueber die                   |
>        >|Verbindlichkeit von Willenserklaerungen|
>        >|mit verpflichtendem                    |
>        >|Inhalt, die in den bankueblichen       |
>        >|Unterschriftenverzeichnissen           |
>        >|bekannt gemacht werden.                |
>        >|--------------------------------------->
>        >  >---------------------------------------|
>        >  |This message is confidential and may be|
>        >  |privileged. It is                      |
>        >  |intended solely for the named          |
>        >  |addressee. If you are not the          |
>        >  |intended recipient please inform us.   |
>        >  |Any unauthorised                       |
>        >  |dissemination, distribution or copying |
>        >  |hereof is prohibited.                  |
>        >  |As we cannot guarantee the  genuineness|
>        >  |or completeness of                     |
>        >  |the information contained in this      |
>        >  |message, the statements                |
>        >  |set forth above are not legally        |
>        >  |binding. In connection                 |
>        >  |therewith, we also refer to the        |
>        >  |governing regulations of               |
>        >  |WestLB concerning signatory authority  |
>        >  |published in the                       |
>        >  |standard bank signature lists with     |
>        >  |regard to the legally                  |
>        >  |binding effect of statements made with |
>        >  |the intent to                          |
>        >  |obligate WestLB.                       |
>        >  >---------------------------------------|
 


More information about the SAP-WUG mailing list