EXIT_SAPLEBND_002 problem

[Former Member]

Hi All,

I have activated the exit EXIT_SAPLEBND_002. Whenever i open ME22N then it goes into the exit but when i save it its not processing that exit.

What could be the problem I'm facing.

varun

[Former Member]

hai Varun,

While saving PO this Exit EXIT_SAPLEBND_002 does not trigger, while Saving PO, Enhancement MM06E005 and exit EXIT_SAPMM06E_012 trigger.

Regards

shelly Malik

[Former Member]

Hi ,

There are many exits in a program and each one is having different purpose,

from your analysis it appears that exit EXIT_SAPLEBND_002 is triggred when you start the transaction and not during save.

You should try to search the exit after you press SAVE.

Hope this helps you

Edited by: Harsh Bhalla on Jan 9, 2010 1:45 PM

[kesavadas_thekkillath]

Before using a exit please test the enhancement( test button available in SMOD) - Put a explicit break-point in the include of the exitr funtion module, Then run your transaction and check whether the control passes through your include.

[Former Member]

Please read it carefully. Its going into break-point before saving. I want user exit for triggering release strategy after i click on SAVE.

[kesavadas_thekkillath]

Please donot post cross threads and do read the forum rules.

[Former Member]

no one seemed to be replying. anyways i have done needful in that.

[Former Member]

HAi Varun

Can you please eleborate more your Exact Requirement,

Regards

Shelly Malik

[Former Member]

Hi Shelly,

1. Suppose PO is fully released through ME29N.

2. Now someone changes anything (Qty, Price etc) then PO should again go through release strategy, when you click the save button.

EXIT_SAPLEBND_002 user exit is triggering just when I enter ME22N transaction.

I'm looking for exit that when PO is changed and saved then it should run release strategy again.

Thanks

Varun.

[Former Member]

hai Varun,

Please go through the given below link once: I hope it will somewhat solve your problem.

[http://mailman.mit.edu/pipermail/sap-wug/2004-January/011678.html]

[;

Regards

Shelly Malik

[Former Member]

Hi,,

I just checked that in ecc 6 the user exit runs for 1 time while in 4.7 it runs two time.

ECC-6 : Runs at time of transaction.

4.7 - Runs at time of transaction and also while saving.

How should i make it run at the PO saving time.

varun

Edited by: Varun Mathur on Jan 11, 2010 11:05 AM

[Former Member]

Hi Varun,

This is normally done thru functional configuration. Whenever a released PO is changed later on, the release strategy gets reset, and the PO then again needs to be released. This is a standard functionality in SAP which can be achieved via configuration.

So as per best practices, it is better to utilize the configuration and request the functional consultant for this.

Regards,

Amit Mittal.

[Former Member]

Hi Amit,

Yeah i too think so, but i also think that it can be done through user exit.

In 4.7 this user exit works absolutely fine, but in ECC 6.0 its not working correctly.

What could be the problem. I'm not able to understand.

varun

[Former Member]

Hi again,

For PO purpose, we have used the user exit MM06E005. There are many FM's inside it which can be helpful. EXIT_SAPMM06E_012 may be helpful. This is triggered prior to saving. Also please see the documentation of this exit. Hope this helps.

regards,

amit m.

[Former Member]

>

> Hi again,
> 
> For PO purpose, we have used the user exit MM06E005. There are many FM's inside it which can be helpful. EXIT_SAPMM06E_012 may be helpful. This is triggered prior to saving. Also please see the documentation of this exit. Hope this helps.
> 
> regards,
> amit m.

This user exit MM06E005 is used for customer fields, in case you have added them.

I don't think so its used for triggering release strategy.

[Former Member]

Hi again,

In our case we had also a similar problem. What we did (as the last option) was to change slightly, the standard FM - ME_REL_STRATEGIE_EKKO.

Inside the FM, there is one line (line number 94),

IF xchange NE space.

inside which we have written small some code to reset the strategy everytime after release. You can have a look at it (via debugging), if it helps.

Regards,

Amit Mittal.

[Former Member]

>

> Hi again,
> 
> In our case we had also a similar problem. What we did (as the last option) was to change slightly, the standard FM - ME_REL_STRATEGIE_EKKO.
> 
> Inside the FM, there is one line (line number 94),
> 
>   IF xchange NE space.
> 
> inside which we have written small some code to reset the strategy everytime after release. You can have a look at it (via debugging), if it helps.
> 
> Regards,
> Amit Mittal.

I did not understand completely. How will this function module called. I did put a break point in it.

But it did not go into it after changing PO and saving it.

varun

[Former Member]

Hi again,

It will go inside this FM only when the PO is eligible for some determination of release strategy.

Here we have also implemented version management of PO, so when we tick the checkbox of the version number ( in Versions tab), and then save, then only it goes inside the FM, to determine the release strategy.

In your case you can also try when creating a new PO and saving, or change some important field (eg. quantity, value) and then save.

Regards,

Amit Mittal.

[Former Member]

Ok. But here when i save it, it does not go into FM.

So i have asked my functional consultant help to check out whether release strategy is applied when changing the PO.

Varun

[Former Member]

>

> Hi again,
> 
> It will go inside this FM only when the PO is eligible for some determination of release strategy. 
> 
> Here we have also implemented version management of PO, so when we tick the checkbox  of the version number ( in Versions tab), and then save, then only it goes inside the FM, to determine the release strategy.
> 
> In your case you can also try when creating a new PO and saving, or change some important field (eg. quantity, value) and then save.
> 
> Regards,
> Amit Mittal.

I suppose this thread is similar to my problem.

[|]

[Former Member]

Yes after checking the version it is going into that exit.

Also the net value is not getting changed, that's why its not going into the exit.

Edited by: Varun Mathur on Jan 11, 2010 3:57 PM