SRM 4.0 (EBP 5.0) n step item level WF

[lmillich@yahoo.com]

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.
> 
> 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
> 
=== message truncated ===




		
____________________________________________________ 
Yahoo! Sports 
Rekindle the Rivalries. Sign up for Fantasy Football 
http://football.fantasysports.yahoo.com