Clarification list FP09 - message text

[ankit_munshi2]

Hello,

We have a requirement to send some documents for post processing in FP09 (clarification list) when certain criteria is met. I found FQevent 259 useful for this requirement. But the problem is the message (probably an application log text) that comes up once FP09 processing is complete is very technical in nature and wont be useful for end users.

the message is : Item set according to event 0259 in clarification worklist.

FQevent 259 doesnt have any parameters where I could set my custom message. Any way out ?

Thanks!

AM

[AmlanBanerjee]

Hi Ankit,

Rather than doing the enhancement in event 259, try it in doing event 960.

In this event, item records are transferred to T_FKKRP table which can be modified.

In here based on the Business rules, you can set the field, XKLAE as X, to route the item to return clarification.

Hope it helps.

Thanks,

Amlan

[srinivasankh · Accepted solution]

Hi Ankit,

You can show custom message by using the FQevent 259, just before the raising the exception  DONT_POST, please set the below:

sy-msgid = <your custom message ID>

sy-msgno = <your custom message number>

sy-msgty = 'E'

This will ensure that the item will get into clarification list with your custom message displayed under 'Last message'. I have quickly checked this in my system here and it works fine. Please implement and test your case.

Hope this helps!

Thanks,

Srini

[ankit_munshi2]

Hello,

Thanks for your response!

I tried this trick already and it creates an entry in DFKKRPE, but the application log screen which shows up after the transaction run is over doesn't have the custom message entry... It just shows the standard message which is vague

[ankit_munshi2]

Hello,

I used FM : CALL FUNCTION 'FKK_TRACE_CATCH'
           EXPORTING
             i_msgty = lc_error
             i_msgid = lc_id
             i_msgno = lc_number
             i_msgv1 = lv_vkont
             i_msgv2 = lc_errmsg.

After setting sy- paranmeters with these values (just before RAISE exception).

The issue is resolved now.. thanks for your help !!

Regards,

AM

[Former Member]

Ankit - Can you share the solution ?