SRM 4.0 (EBP 5.0) n step item level WF

Mon Jun 13 15:26:39 EDT 2005

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.

Regards,
Natasha

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of lmillich at yahoo.com
Sent: Sunday, June 12, 2005 9:10 AM
To: SAP Workflow Users' Group
Subject: RE: SRM 4.0 (EBP 5.0) n step item level WF

Hi Miguel,

It was a programming problem with the approval
obejcts. We have min. 1 - max. 7 approval levels
dynamically depending on different things. Several
levels depends on the same object (e.g. cost
center),this caused the problem,  in this case my
interpretation of approval object creation was wrong,
the refresh is not needed.
It works now fine, the only problem is, that if on the
same level there are several approvers (e.g. for 2
different cost centers 2 different approvers), then
the approval preview works fine, the first approval is
fine, but after one of the 2 approvers approved his
item, then the work item for the second shop item
appears not only for the second approver, but also for
the first one. This is again weird.     

Have you seen any similar problem ?  

We are also on the SP5 level.

The whole BADI with the 3 tables seemed so simple, but
I always face new problems and I did not started yet
the workflow restart based on history tables.

Thanks for your comments and tips.

Best Regards,

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

>
> Hello Lazlo,
>
> I will send you off-line (tomorrow morning, here it
> is 21.30!) our OSS notes
> list but don't forget to check if they are
> applicable to your SP level. Some
> notes referring to the approval preview applet could
> maybe solve your
> problem (Although I have the feeling it is a
> programming error).
> Maybe you are not aware but SAP provides 2 BADI
> implementation examples,
> only refresh item_approval_obj if SAP does it in his
> examples (I don't think
> it is the case).
> There is an OSS note describing hints and tips on
> developing the BADI (it is
> worth to have more than just a look at it).
>
> Cheers.
>
>
________________________________________________________________________
___
> 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: 08 June 2005 20:31
> To: SAP Workflow Users' Group
> Subject: RE: SRM 4.0 (EBP 5.0) n step item level WF
>
> Thanks Miguel.
> Which notes did help? I did not find any specific
> for
> the double-ing probelm.
>
> Best Regards,
>
> Laszlo
>
> --- "Adao-Cruz, Miguel"
> <miguel.adao-cruz at capgemini.com> wrote:
>
> >
> > Hello Laszlo,
> >
> > I had the same kind of bugs with EBP 5.0.
> > Some of them were programming errors (not clear on
> > how to handle the
> > approval objects) in the BADI and others were
> solved
> > with OSS notes.
> > There are lot of OSS notes out there for EBP 5.0,
> we
> > are in the middle of
> > the implementation phase with already more or less
> > 30 notes implemented (we
> > are at support pack 5)!
> >
> > Good luck.
> >
> >
>
________________________________________________________________________
___
> > 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: 08 June 2005 08:22
> > To: SAP Workflow Users' Group
> > Subject: RE: SRM 4.0 (EBP 5.0) n step item level
> WF
> >
> > Hi Jocelyn,
> >
> > I'll reported it to OSS, but I'm still not sure,
> > whether it is my programming error or an SAP
> > bug.I'll
> > check the notes again.
> > I wrote the letter late night, I forgot the put my
> > name.
> >
> > Thanks for your input.
> >
> > Best Regards,
> > Laszlo Millich
> >
> >
> > --- "Dart, Jocelyn" <jocelyn.dart at sap.com> wrote:
> >
> > > Hi no name,
> > > Please check your support pack level and check
> for
> > > any OSS notes about
> > > duplicate approver display - I know there are
> some
> > > for EBP 5.0.   If I
> > > were you I'd look at all the notes for the BADI
> > > approval workflows and
> > > make sure you have the lot (e.g. installed via
> > > snote).
> > >
> > >
> > > Regards,
> > > Jocelyn Dart
> > > Senior Consultant
> > > SAP Australia Pty Ltd.
> > > Level 1/168 Walker St.
> > > North Sydney
> > > NSW, 2060
> > > Australia
> > > T   +61 412 390 267
> > > M   + 61 412 390 267
> > > E   jocelyn.dart at sap.com
> > > http://www.sap.com
> > >
> > >
> >
>
************************************************************************
> > > *****************
> > > The information contained in or attached to this
> > > electronic transmission
> > > is confidential and may be legally privileged.
> It
> > is
> > > intended only for
> > > the person or entity to which it is addressed.
> If
> > > you are not the
> > > intended recipient, you are hereby notified that
> > any
> > > distribution,
> > > copying, review, retransmission, dissemination
> or
> > > other use of this
> > > electronic transmission or the information
> > contained
> > > in it is strictly
> > > prohibited. If you have received this electronic
> > > transmission in error,
> > > please immediately contact the sender to arrange
> > for
> > > the return of the
> > > original documents.
> > > Electronic transmission cannot be guaranteed to
> be
> > > secure and
> > > accordingly, the sender does not accept
> liability
> > > for any such data
> > > corruption, interception, unauthorized
> amendment,
> > > viruses, delays or the
> > > consequences thereof.
> > > Any views expressed in this electronic
> > transmission
> > > are those of the
> > > individual sender, except where the message
> states
> > > otherwise and the
> > > sender is authorized to state them to be the
> views
> > > of SAP AG or any of
> > > its subsidiaries. SAP AG, its subsidiaries, and
> > > their directors,
> > > officers and employees make no representation
> nor
> > > accept any liability
> > > for the accuracy or completeness of the views or
> > > information contained
> > > herein. Please be aware that the furnishing of
> any
> > > pricing information/
> > > business proposal herein is indicative only, is
> > > subject to change and
> > > shall not be construed as an offer or as
> > > constituting a binding
> > > agreement on the part of SAP AG or any of its
> > > subsidiaries to enter into
> > > any relationship, unless otherwise expressly
> > stated.
> > >
>
=== message truncated ===

__________________________________
Yahoo! Mail Mobile
Take Yahoo! Mail with you! Check email on your mobile phone.
http://mobile.yahoo.com/learn/mail
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient,  you are not authorized to read, print, retain, copy, disseminate,  distribute, or use this message or any part thereof. If you receive this  message in error, please notify the sender immediately and delete all  copies of this message.