User Exit implementation

[Former Member]

Hi,

For the TCode FBL5N, for the line items, if we wants to change the payment method then payment block is mandatory. For this user exit is implemented. However, when trying to mass change for morethan one line items the user exit is not being triggered, thus the mandatory error message like "Payment Block is required" is not displaying. I just wanted to know why this user exit is not being triggered while mass change

Please help me in this regard

Regards

Shankar

[umashankar_sahu]

Hi shankary

As for as i Know FBL5N is dispaly only, can you explian in detail what is the Requirment whether it should be applicable for cleared Item or Open items or both. explain in detail so we can try to help you.

[brad_bohn]

As for as i Know FBL5N is dispaly only

Not correct. You can't key on the output screen itself, but if you'll look at the toolbar and the menus you'll see the individual change and mass change functions for changing line items.

To the OP: Can't say what the issue is because you didn't specify the exit or BTE that you used. Mass change simply calls FB02 via function FI_ITEMS_MASS_CHANGE so it's unlikely there's much of a difference in the calls. Use SE30 to trace the mass change call and check if your exit is called or debug the function call.

As far as the other post, that thread has nothing to do with the exit call, it references G/L account changes, presumably for field status configuration and opening a field for input - why is that related?

[Former Member]

Thanks for your reply Brad.

The User Exit that is being triggered is UGBB, while changing the payment method with initial value of Payment Block, while making individual change. Thorugh this user exit, the message "Payment Block is Required" is being poped-up.

It would be helpful, if i can know how to apply this user exit to be triggered even for mass change.

Rgds

Shankar

[brad_bohn]

I'm not familiar with 'UGBB' - so you're not using a BTE? Is that a custom validation exit? You're not going to be able to effect a popup in mass change mode; the transactions are called in the background in no-display mode. The best you can hope for is to error out the transaction which will send a message to the log, or you can set up the change process such that a default payment block is applied per payment method via substitution or BTE.