Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

me51n

Former Member
0 Kudos

hi,

can any one let me know any user exit of badi for me51n.i need this to trigger when we do the check there..

i had found some user exits and badis but they are not triggering.only triggered badu is PR posted one.

other than that can u please suggest me....

hi i want to check the AFNAM field.wether that is in tname entered exists in the user table or not.by the way the badi ME_PROCESS_REQ_CUST does not work i guess as i kept break points and it did not stop.

thanks alot.

5 REPLIES 5

GauthamV
Active Contributor
0 Kudos

You can use this badi for your requirement.

Badi - ME_PROCESS_REQ_CUST

Method - PROCESS_ITEM

Interface - IF_PURCHASE_REQUISITION_ITEM

Structure - MEREQ_ITEM-AFNAM

Former Member
0 Kudos

Hi Kiran,

Try using the User exit - EXIT_SAPLMEREQ_005

BADI - ME_PROCESS_REQ_CUST

Regards,

Swapna.

Former Member
0 Kudos

Hi Kiran,

BADI: ME_PROCESS_REQ_CUST

Use the follwing method for item level check

data : l_item type MEREQ_ITEM.

CALL METHOD im_item->get_data

receiving

re_data = l_item.

Dont forget to activate your BADI implementation and deactivate rest of the implementation for the same BADI.

Hope this will help.

Regards,

Nitin.

Former Member
0 Kudos

Hi Kiran,

Try out with program SAPLXM06 and function module EXIT_SAPMM06_006.

Hope it helps!

Much Regards,

Amuktha.

Former Member
0 Kudos

Hi Kiran,

Following are the main Enhancments in MM.

You can make use of them as per the requirment you have.

Hope it helps.

_______________________________________________________________________________

AMPL0001 - User subscreen for additional AMPL data (manufacturer part number)

LMELA002 - Adoption of batch number from shipping notification at time of posting of a goods receipt

LMELA010 - Incoming shipping notification: adoption of item data from IDoc

LMEQR001 - User exit for source determination

M06B0001 - Role determination for release of requisitions

M06B0001 - Changes to communication structure for release of requisitions

M06B0003 - Number range and document number

M06B0004 - Number range and document number

M06B0005 - Changes to communication structure for overall release of purchase requisitions

M06E0004 - Changes to communication structure for release of purchasing document

M06E0005 - Role determination for release of purchasing documents

ME590001 - Grouping of requisitions for PO split in transaction ME59

MEETA001 - Determination of schedule line type (backlog, immediate requirement, forecast)

MEFLD004 - Determination of earliest delivery date for checking at time of goods receipt (PO only)

MELAB001 - Generation of forecast delivery schedule: realization via creation profile

MEQUERY1 - Enhancement for document overview ME21N / ME51N

MEVME001 - Calculation of default GR quantity and over/underdelivery tolerances

MM06E001 - User exits for inbound EDI messages and outbound purchasing documents

MM06E003 - Number range and document number

MM06E004 - Control of import data screens in purchase orders

MM06E005 - Customer fields in purchasing documents

MEREQ001 - Customer's own data in purchase requisitions

MM06E007 - Change document for requisitions when converting into POs

MM06E008 - Monitoring of contract target value in case of release orders

MM06E009 - Relevant texts for "Texts exist" indicator

MM06E010 - Field selection for vendor address

MM06E011 - Activation of requisition block

MM06L001 - Exits for determination of ratings in vendor evaluation

MMAL0001 - ALE source list distribution: outbound processing

MMAL0002 - ALE source list distribution: inbound processing

MMAL0003 - ALE purchasing info record distribution: outbound processing

MMAL0004 - ALE purchasing info record distribution: inbound processing

MMDA0001 - Default values for delivery addresses

MMFAB001 - User exit for generation of releases

MRFLB001 - Control items during release creation

LWBON001 - Enhancement of LIS update through extension of the communication structure MCKONA (business volumes and rebate income)

LWBON003 - Change settlement data for end-of-period rebate settlement before creation of settlement documents

LWSUS001 - Customer-specific source determination in Retail

LMEXF001 - Conditions in purchasing documents without invoice receipt

LMEKO002 - Enhance communication structure KOMP for price determination

_______________________________________________________________________________