Temporary errors in standard background methods?

[Michael Pokraka]

Alon Raskin wrote:
> Hi Michael,
>
>
>
> 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 work=
s.
>
>
>
> You can make the following call in your redefined method
>
>
>
> swc_call_method super 'MethodName' method_container.
>
>
>
> Super is a predefined reference to the supertype of the BOR Object that
> you
> are in.
>
>
>
> And it ALMOST works. What it does is call the supertype method but if y=
ou
> have delegation then it transfers the call back to the subtype. This me=
ans
> that you end up in and endless loop! I tried logging this bug with OSS =
but
> I
> honestly don't think they understood..
>
>
>
> 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.
>
>
>
> Close but no Cigar.
>
>
>
> Good luck with OSS..
>
>
>
> Alon
>
>
>
>
>
> -----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?
>
>
>
> 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 awar=
e,
>
> one cannot call the supertype method from a redefined method - which wo=
uld
>
> make redefining a perfect alternative.
>
> I think I'll go with your suggestion about contacting SAP, some of thes=
e
>
> 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).
>
>
>
> Thanks for your input.
>
> Cheers
>
> Mike
>
>
>
> 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 i=
t
>
> ensures that your method gets called by all developments.
>
>>
>
>> To be honest, before I go down that route, I would first log an OSS an=
d
>
> 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 call=
s
>
> 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
>
>>
>