EXIT_PROPERTY_NOT_FOUND

[Michael Pokraka]

Hi Alon,
Interesting question. Personally I avoid it as far as possible, and pass
blank values back, placing the onus on whatever uses an attribute to deal
with empties.
The main reasoning behind it is that it invariably ends up being used in =
a
binding somewhere and sends a workflow into error when you don't want it
to. Particularly nasty situations can happen where it becomes impossible
to restart a workflow in error.
 
I stick to using it only for system-type this-really-shouldn't-happen err=
ors.
 
Cheers
Mike
 
Alon Raskin wrote:
> Hi All,
>
> SAP provides the macro EXIT_PROPERTY_NOT_FOUND in the include <OBJECT>.
> Would you say that this should be used when the value of the attribute =
is
> empty or not able to be calculated. If that is the case then when the
> right time to use EXIT_OBJECT_NOT_FOUND? Should this macro be used for
> attributes that are BOR Objects or can this macro be used for attribute=
s
> that are not BOR types (I think not).
>
> I have seen fairly inconsistent use of these macros throughout the SAP
> delivered BOR Object and I would love to hear how people use these macr=
os
> when coding their attributes.
>
> Regards,
>
> Alon
>
>