CX_BO_ERROR

[Andy Curtis]

Hi Florin

Nice Blog post and I have that in place.  I have not found a way to present
the Exception Class 'Long' Text from the Wf Audit Log though.

The popup present the message (255 bytes) but it does not allow you to get
to the Long Text.  (I sound like a user now, give them something and they
want more!).  My idea was when my Task runs a transaction/BADI and receives
Error messages back, that I could output the Error messages to the
Exception Class Long Text, allowing Support to see why the Task has
errrored.

I don't think there is a way to do this, so I have a work around.  Before I
Raise the the ZCX_BO_ERROR exception, I write the messages to the Task
Container (Wf doesn't do it if you Raise an Exception).

I don't think this is the best solution in the world, but it gets the error
messages to the support team.

Andy


On Wed, Jun 19, 2013 at 8:34 AM, <sap-wug-request at mit.edu> wrote:

>    3. Aw: CX_BO_ERROR exception class (Florin Wach)
>


> From: "Florin Wach" <florin.wach at gmx.net>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Cc:
> Date: Wed, 19 Jun 2013 09:34:26 +0200 (CEST)
> Subject: Aw: CX_BO_ERROR exception class
> Hi Andy
>
> I have blogged that here:
>
> http://scn.sap.com/community/bpm/business-workflow/blog/2013/04/25/use-exceptions-in-abap-oo-workflow-with-custom-text
>
> And it's part of the book "Practical Workflow for SAP", where it's
> explained how to work with the text-ID's.
> In my blog post you can also find, how to work with message-ID's.
>
> With the very best wishes
>    Florin
>
> *Gesendet:* Freitag, 14. Juni 2013 um 18:20 Uhr
> *Von:* "Andy Curtis" <abcurtis at gmail.com>
> *An:* "SAP Workflow Users' Group" <sap-wug at mit.edu>
> *Betreff:* CX_BO_ERROR exception class
>  I know this hit the WUG recently so I'm hoping it's fresh in someones
> mind.  I have a subclass of CX_BO_ERROR and I can RAISE the Exception OK.
> I then goto the Wf log and I can find my exception raised and see my Text.
> But I want to give more detail about the exception.
>
> The exception class allows me to enter 'Long Text' behind the Text defined
> so I added it, and I can call Class Parameters from the Long Text which is
> great.
>
> The problem is, I can't see the Long Text from the Wf Log, short text,
> yes, Long text, no.  There are interface methods in the exception class to
> read the long text and if I use SE24 to create an instance I can then see
> the Long Text, but theres no mechanism from the Wf log to get to the Long
> Text.
>
> Unless ....... anyone knows better?
>
>
> Andy Curtis
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20130619/f66f2ca1/attachment.htm