Transport workflow userexits

Thu May 8 03:13:05 EDT 2003

Make sure the correct User Exit is active.
Check also the task and Transport releases.
What release are we talking about ?

Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com

-----Original Message-----
From: Marty Braithwaite [mailto:Marty_Braithwaite at cpr.ca]
Sent: Thursday, May 08, 2003 12:17 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Transport workflow userexits

Thanks Phil, that clears up the mystery of the CTS BADI's......

I suppose I'm not seeing the BADI's being triggered upon release of a request via se10 due to the fact that we have transport workflow turned on?

Regards,
Marty Braithwaite

-----Original Message-----
From: Soady, Phil [mailto:phil.soady at sap.com]
Sent: Wednesday, May 07, 2003 8:06 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Transport workflow userexits

Transport proposal is unrelated to the CTS exit.

CTS exits are used to handle activities in CTS.
IE Se10 RELEASE, these BADIs are good for capturing activity around SE09 Se10 and Se01. There are 5 of them from memory.

The transport proposal is a very strange beast (in my humble opinion). It is for generating a workflow that allows for a transport to be control the by the workflow recipient.  Typically they would approve the import into another system.

This is best seen as control of special export requests for transports to be imported and generally sent around outside of the normal transport paths.

I personally don't like the concept.

Why not go back to the badis and trigger you own events and have custom workflows approve the actions.  You can call functions to release a transport for example.

Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com

-----Original Message-----
From: Marty Braithwaite [mailto:Marty_Braithwaite at cpr.ca]
Sent: Wednesday, May 07, 2003 11:43 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Transport workflow userexits

Thanks Michael, I had looked at doing that already, however these Badi's had me intrigued, since they looked like I should be able to use them for just that purpose, without customizing my own workflow.  However, they don't seem to be tied to the transport workflow process, so it looks like
customization is the key...

-----Original Message-----
From: Michael Chong [mailto:miquelchong at netscape.net]
Sent: Tuesday, May 06, 2003 11:42 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Transport workflow userexits

Hi Marty,
   You should look up SAP Note 503459. The idea is to copy the standard transport workflow to a custom workflow, insert a send mail task into the custom workflow before the approval task, and "activate" the custom workflow as mentioned in the note.

Regards,
Michael

Marty Braithwaite <Marty_Braithwaite at cpr.ca> wrote:

>Thanks Jocelyn, I agree that's probably my best bet.  There is very
>little documentation on this, all I've found is a little on one of the
>badi's that says "the method is only called for requests that are
>exported when they are released (by the transport program tp).  It is
>not called for local requests or tasks."  I guess I don't understand
>the underlying structure of the transport environment well enough, but
>I figured tp would be called in all cases when you release a transport
>and import it.  I'm guessing it means that by releasing the request
>manually I'm not going to trigger the method...but how else would I
>release a request??
>
>-----Original Message-----
>From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
>Sent: Thursday, May 01, 2003 5:45 PM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: Transport workflow userexits
>
>
>Hi Marty,
>Why don't you put your query in OSS?  The developers are the best ones
>to confirm whether that BADI can be used for that purpose.  The fact
>that you don't hit in via breakpoint is not conclusive - e.g. it might be called in the update task.  The developers may an alternative approach to suggest. Regards,
>        Jocelyn Dart
>Consultant (SRM, EBP, Workflow)
>and co-author of the book
>"Practical Workflow for SAP"
>SAP Australia
>email: jocelyn.dart at sap.com
>phone: +61 412 390 267
>fax:   +61 2 9935 4880
>
>
>
>
>-----Original Message-----
>From: Marty Braithwaite [mailto:Marty_Braithwaite at cpr.ca]
>Sent: Tuesday, 29 April 2003 5:07 AM
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Transport workflow userexits
>
>
>Hi everyone, we are on 4.6C and have implemented the standard transport
>workflow to our landscape.  Our transport administrator requested that they be automatically emailed in their Outlook inbox whenever a transport was released to be approved.  I found a BADI definition(CTS_EXPORT_FEEDBACK) that
looks like it should work, so within it, I coded a send email message routine.  I activated the BADI but I have not been able to get it to invoke. The routine works when I test the badi on it's own.   I thought that as soon as the Transport proposal as created and sent to the administrator, the BADI
would be invoked and an email would be sent as well, but I sent a breakpoint at the BADI and it doesn't even get to it.  Has anyone used these BADI's before, if so do you have any insights on what I might be missing?  Does this BADI even work for this scenario??
>
>
>Thanks,
>Marty Braithwaite
>------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
>------------------------------
>
>Computer viruses can be transmitted via email. Recipient should check
>this email and any attachments for the presence of viruses. Sender and
>sender company accept no liability for any damage caused by any virus
>transmitted by this email.
>
>This email transmission and any accompanying attachments contain
>confidential information intended only for the use of the individual or
>entity named above.  Any dissemination, distribution, copying or action
>taken in reliance on the contents of this email by anyone other than
>the intended recipient is strictly prohibited.  If you have received
>this email in error please immediately delete it and  notify sender at
>the above email address.
>
>
>Le courrier ilectronique peut jtre porteur de virus informatiques.  Le
>destinataire doit donc passer le prisent courriel et les pihces qui y
>sont jointes au ditecteur de virus.  L'expiditeur et son employeur
>diclinent toute responsabiliti pour les dommages causis par un virus
>contenu dans le courriel.
>
>Le prisent message et les pihces qui y sont jointes contiennent des
>renseignements confidentiels destinis uniquement ` la personne ou `
>l'organisme nommi ci-dessus.  Toute diffusion, distribution,
>reproduction ou utilisation comme rifirence du contenu du message par
>une autre personne que le destinataire est formellement interdite.  Si
>vous avez regu ce courriel par erreur, veuillez le ditruire
>immidiatement et en informer l'expiditeur ` l'adresse ci-dessus.
>
>------------------------------ IMPORTANT NOTICE - AVIS IMPORTANT
>------------------------------
>

__________________________________________________________________
Try AOL and get 1045 hours FREE for 45 days! http://free.aol.com/tryaolfree/index.adp?375380

Get AOL Instant Messenger 5.1 for FREE! Download Now! http://aim.aol.com/aimnew/Aim/register.adp?promo=380455