BADI being called random times

[Former Member]

we have a requirement in our GTS system - while saving the customs duty calculation document, a warning message has to be displayed based on some values. As I haven't found any customer/user exits, I searched for BADI's and found a badi used for output determination, which has all the parameters I require. So, I have implemented my code there.

But the problem here is, that badi is being called random number of times - more than 1 time in 90% of cases, and that warning message is also being displayed random number of times.

I tried using ABAP memory for this - by setting a flag using EXPORT/IMPORT, but this approach is not working.

Any ideas how to implement this?? Any help would be appreciated.

[Former Member]

Thank you for visiting SAP Community to get answers to your questions. Since you're new in asking questions here, I recommend that you familiarize yourself with https://community.sap.com/resources/questions-and-answers (if you haven't already), as it provides tips for preparing questions that draw responses from our members.

Should you wish, you can revise your question now by selecting Actions, then Edit.

Finally, if you're hoping to connect with readers, please consider adding a picture to your profile. Here's how you do it: https://www.youtube.com/watch?v=F5JdUbyjfMA&list=PLpQebylHrdh5s3gwy-h6RtymfDpoz3vDS By personalizing your profile with a photo of you, you encourage readers to respond.

Best regards,

SAP Community moderator

[matt]

1. It's never random

2. What BAPI?

[former_member718889]

it is not optimal solution

but you can alsways get application call stack and check if it comes from where you want

[mouaz_benredjeb]

Hi Ramya,

Indeed, BADI /SAPSLL/PRN_DET could be called by the standard multiple times...

Have you explored the possibility of instead using the BADI /SAPSLL/IF_EX_CUS_ECC with method MODIFY_CONSISTENCY_CHECK?

This BADI is usually the BADI used to check the content of the declaration before to set the declaration as complete.

When implementing this BADI, you would do the following:

- Add your own logic to identify the issue for which an error or warning message should be issued

- Set parameter CV_CONSISTENT to blank (so the declaration is inconsistent)

- (Important) Add a message in the consistency/incompleteness log - This can be easily done by issuing a message from within the BADI.

The user will then see this error/warning message in the incompletion log. If it is a warning message, he can then proceed with the declaration (e.g. send it to customs authorities). If it is an error message, he/she won't be able to process the message to customs.

Hope this helps.

Mouaz

[RaymondGiuseppi]

Define some field or internal table in your BAdI implementation's instance attributes, set its value when warning is raised (or add a record when raised for an item) and don't raise the warning again if already done.

[Former Member]

I'm new to ABAP and i didn't know much, but whenever a second call is made, I think all the previously instantiated attributes gets recycled along with that object. Please correct me if I'm wrong. However, I haven't tried the approach yet, I'll try it today. Thanks.

[RaymondGiuseppi]

So did you try to either

• Find a BAdI only called once (a 'check' or 'prepare save' type of BAdI)
• Save your flag in a shared area with a lifetime related to your main transaction

[mouaz_benredjeb]

Hi Ramya,

In order to help, could you please share the name of the BADI definition you are using?

Thanks.

Mouaz

[Former Member]

Hi Mouaz,

The BADI is /SAPSLL/PRN_DET. I'm using it's implementation to write my "warning message" logic while saving customs duty regulation document.

Thanks

Ramya