ebp 4.0 bbp_wfl_approv_badi activation

Wed Feb 11 18:52:21 EST 2004

Trying to activate the following BADI

BBP_WFL_APPROV_BADI

results in, "There are already implementations active!" (oh really!?)

Some other details -

Implementation name: ZBBP_WFL_APPROV_BADI (my name)
Definition name: BBP_WFL_APPROV_BADI
Method (GET_REMAINING_APPROVERS)

I see a note out there (604276) that says the default implementation of this
badi was changed around but was fixed in BBPCRM 4.0 Support Package 01.

Has anyone activated this particular wf badi and had this issue ? Many
thanks!

Regards,

Jim Stewart

________________________________________________
Jim Stewart
SAP EBP Workflow Consultant
o: 858.826.3619
m: 562.212.4312
mailto:frank.j.stewart at saic.com
mailto:jstewart at equitytechgroup.com

 -----Original Message-----
From:   SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]  On Behalf Of
Sergey Breslavets
Sent:   Tuesday, February 10, 2004 9:47 AM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: SO_DOCUMENT_INSERT_API1

so, the differences are:
   1. you test with your user id, while workflow executes it under wf-batch
   2. committing changes to database: they either not committed or update is
terminated.

if all commit statements are in place, then it leaves user id...
   check wf-batch vs your_id: unless there is an explicit program logic
instructing to not create file if sy-user is WF-BATCH (just kidding), there
are basically three possible reasons for malfunctioning:

   1. a background execution error (e.g. attempt to write to non-existent
folder), or
        - check rfc log - if there are some execution errors error you'll
see them in the log

   2. an authorization issue (wf-batch is not allowed to write to the
folder)
        - activate a security trace for wf-batch and run workflow again,
then inspect trace logs - it'll show you if there were any authorization
problems. it usually helps to locate the problem area.

   3. terminated update process (U2)
        - check SM13 (terminated processes)

end if :))

regards,
Sergey

-----Original Message-----
From: M Doe [mailto:monica_sap at hotmail.com]
Sent: Tuesday, February 10, 2004 11:11 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: SO_DOCUMENT_INSERT_API1

Yes I did.  It works when I test in SWO1 or SWUD(test method).

This is so weird!

Regards,
Monica

>From: "Becker, Stephan" <stephan_becker.ext at siemens.com>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Re: SO_DOCUMENT_INSERT_API1
>Date: Tue, 10 Feb 2004 17:41:39 +0100
>
>Try test method in swud or straight from swo1 (test object)
>
>-----Mensaje original-----
>De: M Doe [mailto:monica_sap at hotmail.com]
>Enviado el: 10 February 2004 17:32
>Para: SAP-WUG at MITVMA.MIT.EDU
>Asunto: Re: SO_DOCUMENT_INSERT_API1
>
>Hi Stephan,
>
>I tried putting the "commit work" statement in my pgm.  It did not make a
>difference.
>
>The pgm works and creates a folder in my outbox with the document as it was
>doing before.  But the workflow even though it says completed does not
>create a folder in the outbox.  I am using the same pgm behind the method
>in
>the workflow.
>
>If the workflow did not create the folder- how do I debug it to find out
>what went wrong?
>
>Regards,
>Monica
>
>
>
>
> >From: "Becker, Stephan" <stephan_becker.ext at siemens.com>
> >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> >To: SAP-WUG at MITVMA.MIT.EDU
> >Subject: Re: SO_DOCUMENT_INSERT_API1
> >Date: Tue, 10 Feb 2004 16:05:45 +0100
> >
> >Seems you're lacking a commit work.
> >Stephan
> >
> >-----Mensaje original-----
> >De: M Doe [mailto:monica_sap at hotmail.com]
> >Enviado el: 10 February 2004 15:59
> >Para: SAP-WUG at MITVMA.MIT.EDU
> >Asunto: Re: SO_DOCUMENT_INSERT_API1
> >
> >Hi Sergey,
> >
> >Thanks for your response.  I checked the authorization for wf-batch.  It
> >has
> >SAP_ALL and SAP_NEW in the proflie.
> >
> >What could be wrong here?
> >
> >Regards,
> >Monica
> >
> >
> >
> >
> > >From: Sergey Breslavets <sergey.breslavets at epstechnology.com>
> > >Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
> > >To: SAP-WUG at MITVMA.MIT.EDU
> > >Subject: Re: SO_DOCUMENT_INSERT_API1
> > >Date: Mon, 9 Feb 2004 15:48:27 -0600
> > >
> > >check authorization for wf-batch
> > >
> > >-----Original Message-----
> > >From: M Doe [mailto:monica_sap at hotmail.com]
> > >Sent: Monday, February 09, 2004 3:40 PM
> > >To: SAP-WUG at MITVMA.MIT.EDU
> > >Subject: SO_DOCUMENT_INSERT_API1
> > >
> > >
> > >Hello all,
> > >
> > >I am trying to insert a document in a user's outbox using the function
> > >module "SO_DOCUMENT_INSERT_API1" .  I created a subtype to SOFM and
> >coded
> > >this method.  This  works fine( I see the document in the user's
>outbox)
> > >when I execute the method from swo1 but when I use this method in a
>task
> > >nothing happens.
> > >
> > >I also wrote a pgm with the same code and executed the pgm and it works
> >but
> > >the same code does not work when it is used in the workflow.
> > >
> > >Can someone explain why?  I just don't understand what could be wrong.
> >The
> > >underlying code works so why does it not do anything when I have a task
> > >that
> > >uses this method.
> > >
> > >Thanks.
> > >Monica
> > >
> > >_________________________________________________________________
> > >Let the advanced features & services of MSN Internet Software maximize
> >your
> > >online time. http://click.atdmt.com/AVE/go/onm00200363ave/direct/01/
> >
> >_________________________________________________________________
> >Let the advanced features & services of MSN Internet Software maximize
>your
> >online time. http://click.atdmt.com/AVE/go/onm00200363ave/direct/01/
>
>_________________________________________________________________
>Click here for a FREE online computer virus scan from McAfee.
>http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

_________________________________________________________________
Let the advanced features & services of MSN Internet Software maximize your
online time. http://click.atdmt.com/AVE/go/onm00200363ave/direct/01/