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: 

User exit for ME21N transaction

vinod_vemuru2
Active Contributor
0 Kudos
71

Hi all,

Is there any user exit which consists of EKKO structure as CHANGING or TABLES parameter. My requirement is when the user press save while creating STO i have to do some validations and keep the document under hold. For this in EKKO table there is one flag indicator called <b>MEMORY</b> field. this field will be BLANK if the document is to be saved and it will be 'X' if the document is to be kept under HOLD. Please also let me know if any other structre has this field or any other field which indicates HOLD/SAVE status.

Thanks in Advance,

Vinod.

4 REPLIES 4

varma_narayana
Active Contributor
0 Kudos
45

Hi Vinod..

You can implement the BADI named ME_HOLD_PO (Check in Tcode SE18)

It has the method IS_ALLOWED in which there is PARAMETER called IM_EKKO .

see the Documentation of this BADI in SE18

and implement it in SE19.

reward if Helpful.

0 Kudos
45

Hi Varma,

Sorry i forgot add this. I am using 4.6C version. Can i implement this in my version.

Former Member
0 Kudos
45

Transaction Code - ME21N Create Purchase Order

Exit Name Description

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

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

MRFLB001 Control Items for Contract Release Order

AMPL0001 User subscreen for additional data on AMPL

No of Exits: 35

Rewards if useful..................

Minal

vinod_vemuru2
Active Contributor
0 Kudos
45

Thanks all