topic Enhancing NUMBER_GET_NEXT when RETURNCODE is 1 in Application Development and Automation Discussions

Enhancing NUMBER_GET_NEXT when RETURNCODE is 1

Former Member — Wed, 04 Aug 2010 10:36:57 GMT

Hi,

When NUMBER_GET_NEXT return '1' we know that critical value reached. This return code set within NUMBER_GET_NEXT >> PERFORM LOCAL_BUFFER routine.

Requirement: when ever NUMBER_GET_NEXT returns '1' i have to send a mail to some fixed mail id. Though SAP gives an informatin message, but when in any background job function module NUMBER_GET_NEXT returns '1' , user will not be able to see that message.

according to my analysis as there is no exit , badi or enhancement. So it is not possible other than changing FM with access key.

As this FM called every where I have to write only within FM. not outside of this FM.

Please tell me if it is possible in any other way.

Regards,

Manab.

Re: Enhancing NUMBER_GET_NEXT when RETURNCODE is 1

Former Member — Thu, 05 Aug 2010 13:48:59 GMT

I got the solutin . In version 6 you have to write code within enhancement spot BADI_NUMBER_GET_NEXT >> CL_BADI_NUMBER_GET_NEXT_FALLB >> IF_BADI_NUMBER_GET_NEXT~NUMBER_GET >> double click.

Within this method we have to calculate critical number using NRIV table and then percentage field of TNRO table.

if NRIV-nrlevel GE ctitical_number then send mail.

Thanks.

Manab.

Re: Enhancing NUMBER_GET_NEXT when RETURNCODE is 1

Former Member — Wed, 28 Sep 2011 11:46:53 GMT

Hi,

could you, please, tell how did you manage to create implementation for enhancement spot BADI_NUMBER_GET_NEXT?

Within this spot there is already existing enhancement implementation WDK_NUMBER_GET_NEXT, but it does not allow to make any changes.

If I create my own enhancement implementation and when I try to create Badi implementation, it generates the following error message "BAdi is internal SAP; implementation in customer namespace not allowed".