Temporary errors in standard background methods?

[Alon Raskin]

Hi Michael,
 
=20
 
I am really pleased that you brought this up as this has been one of my =
pet
gripes (one of many) about the BOR. What's worse is that it almost =
works.
 
=20
 
You can make the following call in your redefined method
 
=20
 
swc_call_method super 'MethodName' method_container.
 
=20
 
Super is a predefined reference to the supertype of the BOR Object that =
you
are in.
 
=20
 
And it ALMOST works. What it does is call the supertype method but if =
you
have delegation then it transfers the call back to the subtype. This =
means
that you end up in and endless loop! I tried logging this bug with OSS =
but I
honestly don't think they understood..
 
=20
 
If you have a subtype which is NOT delegated then this works perfectly. =
You
can redefine a method and then call the supertype just as real OO.
 
=20
 
Close but no Cigar.
 
=20
 
Good luck with OSS..
 
=20
 
Alon
 
=20
 
=20
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
Michael Pokraka
Sent: Wednesday, November 19, 2003 4:55 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Temporary errors in standard background methods?
 
=20
 
Hi Alon,
 
The reason I'd prefer not to redefine is the lack of 'proper' OO in
 
Business Objects, and remaining upwardly compatible. As far as I'm =
aware,
 
one cannot call the supertype method from a redefined method - which =
would
 
make redefining a perfect alternative.
 
I think I'll go with your suggestion about contacting SAP, some of these
 
just seem such an obvious candidate for temp errors that I find it a
 
little curious that it hasn't been changed yet (on 4.7 here).
 
=20
 
Thanks for your input.
 
Cheers
 
Mike
 
=20
 
Somewhere in the mists of time Alon Raskinwrote:
 
> Hi Michael,
 
>
 
> You almost got it.
 
>
 
> What I would do is redefine the method on the new sub-type. That way =
it
 
ensures that your method gets called by all developments.
 
>
 
> To be honest, before I go down that route, I would first log an OSS =
and
 
try to get SAP to change their exception to a temporary one.
 
>
 
> Regards,
 
>
 
> Alon
 
>
 
> ________________________________
 
>
 
>> From: SAP Workflow on behalf of Michael Pokraka
 
> Sent: Wed 19/11/2003 15:58
 
> To: SAP-WUG at MITVMA.MIT.EDU
 
> Subject: Temporary errors in standard background methods?
 
>
 
>
 
>
 
> Hi Folks,
 
> I'm surprised not to find anything in the archives about this one:
 
>
 
> Is there a simple way to mark a SAP-standard background method's
 
exception as a temporary error? SAP have a habit of using the temp
 
setting as little as possible, which is a bit annoying when trying to
 
use standard methods as far as possible - BUS2012.RELEASE is an obvious
 
example: if someone is editing the PO it immediately errors, no retry
 
via SWWERRE, resulting in an unhappy WF administrator.
 
>
 
> The only thing I can think of (and have used in the past) is to have a
 
custom delegated subtype of the object, with a custom method which calls
 
the original method and duplicates the exceptions with the desired
 
settings. This seems a bit of overkill just for setting a temporary
 
error.
 
>  In fact it seems so 'normal' that I'm wondering if I'm not missing
 
> something glaringly obvious...
 
>
 
> Any thoughts/suggestions would be appreciated,
 
> Cheers
 
> Mike
 
>