SRM 4.0 (EBP 5.0) n step item level WF

[lmillich@yahoo.com]

Hi Miguel, 

Thanks for the reply. 
I know the debug facility using BBP_PD, it is good for
debugging at the beginning.What I miss is the proper
debugging during approval, not during SC creation. 
What I try to use is ITS (web) debugging, maybe this
is new info for you (OSS note 722735 describes it), in
transaction SICF the debugging can be switched on per
services, but it does not always stop, when it would
be needed. I'll check the method proposed by Jocelyn. 

Rejection: it does not work when using approval
(transaction BBPSC07), not the shop for function. What
is weird, that it worked previously, and in theory it
is a pure standard function, does not have to do
anything with the custom BADI development. 
I thought of even security settings problems. 
We do not use HR connection. 
If available basis will implement SP6 at the weekend,
maybe this will solve my problems miraculously. 

Thanks again, 

Laszlo  
 



--- "Adao-Cruz, Miguel"
<miguel.adao-cruz at capgemini.com> wrote:

> 
> Hello Lazlo,
> 
> There has been some messages on WUG last months
> about debugging EBP. One
> good way is the one proposed by Jocelyn (see message
> RE: BADI
> BBP_WFL_APPROV_BADI is not  getting
> APPROVAL_HISTORY_TABLE of 3/3/2005)using
> the functionality that some functions store the data
> that they have been
> called with.
> If you don't need to debug the entire process of the
> approval but just check
> if everything goes fine at the beginning (actually,
> this has been enough for
> me to solve 90% of the issues) just put a break
> point in the badi with your
> user_id (break-point user-id), create a shopping
> cart and put it ON HOLD.
> Then in the SAP GUI start transaction BBP_PD, enter
> BUS2121 as object type
> and your shopping cart number in object_id.
> A more dirty way is using infinite loops in the
> BADI.
> 
> I am not using "restart based on history tables" as
> my client wants
> rejections to be approved by requestors.
> 
> For your rejection issue I remember I saw a couple
> of OSS notes about issues
> with SC rejections. I think they will all come in
> Support Pack 6 which
> should be available for download this week, our
> basis are desperately
> waiting for it!! Are you using the "shop for"
> functionality when you have
> this problem? Is your EBP integrated with R/3 HR?
> 
> Cheers.
> Miguel.
>
___________________________________________________________________________
> Miguel Adao-Cruz | Capgemini | Woking
> Technology Services
> T.+44-870-238-2927 | Int.700 2927 |
> www.capgemini.com
> 
> 
> Join the Collaborative Business Experience
>
___________________________________________________________________________
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> lmillich at yahoo.com
> Sent: 27 June 2005 08:21
> To: SAP Workflow Users' Group
> Subject: RE: SRM 4.0 (EBP 5.0) n step item level WF
> 
> Hi Miguel,
> 
> I missed this mail, that's why I did not reply.
> OSS note 783110 is not yet implemented, after that I
> will see. I checked already the GUIDs, but was not
> sure, what is the good situation.
> I do the check at which level is called the BADI.
> How do you debug it? What I use, in our system for
> the
> services Approval and SC Creation the debugging is
> enabled so I debug it on the web, but this is slow.
> Is
> there a better or other way?
> 
> "restart based on history tables":
> I meant , that item level WF does not restart
> automatically based on user authorizations as other
> standard previous EBP workflows do. You have to
> program it ,there is an OSS note for it too. Did you
> face any problem with that ?
> 
> I have another problem in the meantime:
> The rejection does not work at all, when the
> approver
> reject the SC,a workitem is created and sent to the
> SC
> creator for accepting the changes. This is a
> standard
> feature and worked previously.
> In the recent week something went wrong, and the
> workitem is created, but it fails, as I see it from
> the WF log.
> The error message is :
> "Error in the evaluation of expression
> &LASTWORKITEM.EXECUTEDBYUSER.NAME&"
> "Error when determining attribute 'NAME' of object
> instance 'B0.USR01.]"
> 
> 
> I even restored the BADI code to the simplest code
> based on SAP sample. It does not work for one item
> and
> level either.
> Any tip ?
> 
> Thanks,
> 
> Laszlo 
> 
>   
>  
> 
> 
> --- "Adao-Cruz, Miguel"
> <miguel.adao-cruz at capgemini.com> wrote:
> 
> >
> > Hi Laszlo,
> >
> >
> > I didn't face a similar problem but I have the
> > impression you are having
> > again a programming problem (if note 783110 didn't
> > solve your issue). It
> > looks that the BADI recreates new approval objects
> > for the first level (line
> > item 1 cost center x, line item 2 cost center Y)
> > when it is called for the
> > second time.
> >
> > Do you do the check (like in the standard BADI
> > example) to know at which
> > level is called the BADI?
> >
> > Do you populate correctly the 3 tables at the end
> of
> > the BADI call?
> >
> > Once the BADI has been called the first time, the
> > second time it should not
> > process the code related to finding the agents of
> > the first level again, but
> > only from level 2 to 7 (in your case). And on top
> of
> > this, it looks like it
> > recreates two approval objects (different from the
> > first time the BADI has
> > been called)!!.
> >
> > I recommend that debug your badi.
> > First put your SC on hold, debug the badi, and
> > before leaving the badi save
> > the 3 tables content in a Excel sheet (save table
> > function from debug
> > transaction). Then after approving the first item
> > debug again the badi and
> > save the 3 tables in the Excel (Check if goes
> > through the code where it
> > generates the approval object for level 0 and 1).
> > Compare the GUIDs (boring task!!) and try to
> > understand what the badi is
> > doing with the approval objects.
> >
> > Hope it will help.
> >
> > PS: I didn't understand when you said "I did not
> > started yet
> > the workflow restart based on history tables".
> >
> >
> >
>
___________________________________________________________________________
> > Miguel Adao-Cruz | Capgemini | Woking
> > Technology Services
> > T.+44-870-238-2927 | Int.700 2927 |
> > www.capgemini.com
> >
> >
> > Join the Collaborative Business Experience
> >
>
___________________________________________________________________________
> >
> >
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu
> > [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> > Baunach, Natasha R
> > Sent: 12 June 2005 22:10
> > To: SAP Workflow Users' Group
> > Subject: RE: SRM 4.0 (EBP 5.0) n step item level
> WF
> >
> > Laszlo,
> >
> > Try applying OSS note 783110 to solve your
> problem.
> > Also, you might
> > want to consider applying support pack 6 -- there
> > are a lot of OSS notes
> > related to BADI approval workflow.
> >
> 
=== message truncated ===



		
__________________________________ 
Yahoo! Mail Mobile 
Take Yahoo! Mail with you! Check email on your mobile phone. 
http://mobile.yahoo.com/learn/mail