topic Re: Purchase Req user exit in Application Development and Automation Discussions

Purchase Req user exit

Former Member — Fri, 19 Nov 2010 06:51:29 GMT

I am having difficulty entering a user exit, M06B0002, function EXIT_SAPLEBND_001 include ZXM06U13. It should allow me to set CEBAN-USRC1 a user field which would allow me to determine the release strategy using this as a classification.

The system works fine for user exit M06B0001 which allows the person in workflow responsible to be determined. But this does not allow me to manipulate field USRC1.

I have added the enhancement M06B0002 to project Z06B0001 which already contains M06B0001 and activated the enhancement. Include ZXM06U13 has been activated as well, yet a breakpoint in the code is not hit.

Any suggestions?

Re: Purchase Req user exit

Former Member — Fri, 19 Nov 2010 07:05:22 GMT

Check the function module ME_REL_STRATEGIE_EBAN (Line number 50). Put a break-point here and debug to see whether the enhancement is called. The enhancement is called only when there is an entry in DB table T16FG where FRGOT = 1 and FRGFG <> 'X'.

Re: Purchase Req user exit

Former Member — Mon, 22 Nov 2010 08:38:13 GMT

Interesting. Not only is the Function ME_REL_STRATEGIE_EBAN not hit but the calling function ME_REL_STRATEGY_REQUISITION is not hit either.

I put breakpoints at the beginning of both functions. Though function EXIT_SAPLMEREQ_005 include ZXM02U05 is hit in a breakpoint.

There is an entry in table T16FG where FRGOT = 1 and FRGFG = 'X'.

Is there something incorrect with enhancement or could it be that introducing two more classifications that have not been completely determined in all classifications?

Re: Purchase Req user exit

Former Member — Mon, 13 Dec 2010 11:53:48 GMT

Progress has been made. It has been suggested that I should use enhancement M06B0005. This does enter function module ME_REL_STRATEGIE_EBAN and does come up with the correct release strategy.

However, if I change key fields in the pruchase req document, which should force it to re-calculate the release strategy, it does not.

By debugging it enters function ME_REL_STRATEGIE_EBAN, but does not come up with a result.

Still in DEVL so no harm done.

Re: Purchase Req user exit

Former Member — Thu, 16 Dec 2010 07:37:59 GMT

The release strategies have been configured (in DEVL) the coding is in place, and the correct release codes are listed. I have even got the substitution to work. However, if I change the document type before saving, it fails to re-evaluate the new release strategy. Since this is a mistake that many users will make, I need to determine why this is so. Debugging has shown that it is re-determining personnel in ZXM06U12, but this would be after the strategy had been determined. ZXM02U05 verifies the customer fieldsand the flag EX_RECHECK_ITEM is being set. I have checked SAP Notes. Any ideas?

Re: Purchase Req user exit

Former Member — Mon, 24 Jan 2011 23:29:12 GMT

I have determined that I have not introduced any bugs. the same situation already exists in PROD. The Release Strategy is not re-determined when the requisition has been checked, the doc type changed and re-checked. However if the value is changed by one cent the release strategy is re-determined.

The workaround is to save the requisition in ME51N then to edit it in ME52N or to make a change in the value.