ME11 User Exit.

[Former Member]

Guru's,

Have a requirement that whenever a new info record for material and vendor is saved a user community would like to get an email. Thought this was a fairly simple requirement, so found the development class for ME11 and looked for user exit. Found many but none of them were actually for ME11.(Also checked same via searching customer-function in SAPMM06I but none user exits where found ).

Any pointers on what I might be missing ? Looked at some forums and found that we can sometimes use BADI for similar user exit type requirements but don't know how or wheather we have one a available for ME11.

[Former Member]

hi,

In order to find BAdi,

Goto to SE80.

Package = <development class for ME11>.

Check Enhancement..

This lists the BADi's available..

You can also refer to recenlty published webblog by Alwin van de Put named How to search for BAdIs? (Trace it).

Here is the link..

/people/alwin.vandeput2/blog/2006/04/13/how-to-search-for-badis-trace-it

please refer to thread

Also i shall forward to you one excellent BADI tutorial which will give you hands on BADI and ways to find BADi..

Let me know ur email id..

Hope that helps!

Regards,

Tanveer.

<b>Please mark helpful answers.</b>

[Former Member]

Tanveer,

Can you please send me the BAPI documentation at sinho.sap@gmail.com.

Thanks

Saket....

[Former Member]

goto se80 put package ME ther and it will list u all the enhancements....try this out...

reward point if it helps

regards

gunjan

[LucianoBentiveg]

I saw this ones:

LMEKO001 Extend communications structure KOMK for pricing

LMEKO002 Extend communications structure KOMP for pricing

MM06E011 Activate PReq Block

AMPL0001 User subscreen for additional data on AMPL

LMEDR001 Enhancements to print program

LMELA002 Adopt batch no. from shipping notification when posting a GR

LMELA010 Inbound shipping notification: Transfer item data from IDOC

LMEQR001 User exit for source determination

LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt

LWSUS001 Individual customer source determination in Retail

M06B0001 Role determination for purchase requisition release

M06B0002 Changes to comm. structure for purchase requisition release

M06B0003 Number range and document number

M06B0004 Number range and document number

M06B0005 Changes to comm. structure for overall release of requisn.

M06E0004 Changes to communication structure for release purch. doc.

M06E0005 Role determination for release of purchasing documents

ME590001 Grouping of requsitions for PO split in ME59

MEETA001 Define schedule line type (backlog, immed. req., preview)

MEFLD004 Determine earliest delivery date f. check w. GR (only PO)

MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.

MEVME001 WE default quantity calc. and over/ underdelivery tolerance

MM06E001 User exits for EDI inbound and outbound purchasing documents

MM06E003 Number range and document number

MM06E004 Control import data screens in purchase order

MM06E005 Customer fields in purchasing document

MM06E007 Change document for requisitions upon conversion into PO

MM06E008 Monitoring of contr. target value in case of release orders

MM06E009 Relevant texts for "Texts exist" indicator

MM06E010 Field selection for vendor address

MMAL0001 ALE source list distribution: Outbound processing

MMAL0002 ALE source list distribution: Inbound processing

MMAL0003 ALE purcasing info record distribution: Outbound processing

MMAL0004 ALE purchasing info record distribution: Inbound processing

MMDA0001 Default delivery addresses

MMFAB001 User exit for generation of release order

MEQUERY1 Enhancement to Document Overview ME21N/ME51N

MRFLB001 Control Items for Contract Release Order

[Former Member]

HI

GOOD

HERE IS SOME USER EXITS OF ME11,

AMPL0001 User subscreen for additional data on AMPL

LMEDR001 Enhancements to print program

LMELA002 Adopt batch no. from shipping notification when posting a GR

LMELA010 Inbound shipping notification: Transfer item data from IDOC

LMEQR001 User exit for source determination

LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt

LWSUS001 Customer-Specific Source Determination in Retail

M06B0001 Role determination for purchase requisition release

M06B0002 Changes to comm. structure for purchase requisition release

M06B0003 Number range and document number

M06B0004 Number range and document number

M06B0005 Changes to comm. structure for overall release of requisn.

M06E0004 Changes to communication structure for release purch. doc.

M06E0005 Role determination for release of purchasing documents

ME590001 Grouping of requsitions for PO split in ME59

MEETA001 Define schedule line type (backlog, immed. req., preview)

MEFLD004 Determine earliest delivery date f. check w. GR (only PO)

MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.

MEQUERY1 Enhancement to Document Overview ME21N/ME51N

MEVME001 WE default quantity calc. and over/ underdelivery tolerance

MM06E001 User exits for EDI inbound and outbound purchasing documents

MM06E003 Number range and document number

MM06E004 Control import data screens in purchase order

MM06E005 Customer fields in purchasing document

MM06E007 Change document for requisitions upon conversion into PO

MM06E008 Monitoring of contr. target value in case of release orders

MM06E009 Relevant texts for "Texts exist" indicator

MM06E010 Field selection for vendor address

THANKS

MRUTYUN

[Former Member]

Took a look at this and found out that although we have all these user exits for ME11(Either by using an ABAP to find user exit or getting development class of ME11 and doing a look up using SMOD), none of these are actually called used in ME11 transaction. Think the issue is that these user exits exist for the development class for ME11's program but along with that program we have many other programs for same development class and these user exists corresponds to those programs. So now how do we solve Prem's problem ?

Saket....