User exit me21n

hi experts!
does anybody know how can I find the user exits for ME21n? I checked the other threads and I am getting stuck at the step "find development class" in transaction se93. how can you find the development class here?
best regards,
ileana

Hi,
Here is the list od all User Exits in ME21N
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
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number
Thanks,
Kumar Arcot

Similar Messages

Purchase Order User Exit (ME21N)

Hello experts,
I have a request to enhance SAP for authorization when a user creates a PO (ME21N)that all of the line items have the same purchasing group as the what is in the header, or it cannot be created.
Anybody have any idea what exit this would be in?
Thanks.

Hi Tom,
Here are the user exits available for ME21N.
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
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
For your case, please check MM06E005 or you can try BADI ME_PROCESS_PO_CUST.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Doubt user exit ME21N

Hi All.
Automatically I need to Populate Picked quantity in VL02N when I creating STO (delivery will be created after STO in ME21N .it s done through configuration so no need to create delivery by VL10)
I found user exits for ME21N: EXIT_SAPMM06E_013
Include: ZXM06U44,
In my functional spec their given program FV50C302 also. Shall I need to copy as
ZFV50C302 and Include it in ZXM06U44 ?
Picked Quantity should be equal to delivery quantity (Picked Quantity LIPSD-PIKMG = LIPSD-G_LFIMG Delivery Quantity)
Please help me. Automatically how can populate picked quantity to VL02N?
To be reward all helpful answers.
Regards.
Jay

Hi Jay,
For the first question: there is no need to copy FV50C302 and make a Z. Just double click on ZXM06U44, it will show a warning press enter. it will ask for creating the include. create it and pass required value to it.
For the second question: for the pick quantity will be same of delivery quantity, try the exit V50PSTAT, and pass the required value.
Hope it will solve the problem.
Regards
Krishnendu

User Exit or BADi in Purchase Order Regarding

Hi Friends,
i have a requirement like this. If Item Categiry(At Item level, 3 Rd Column) in a Purchase order is type 'L'. We will have an option to enter multiple materials under components screen(It will come by giving on line item with 'Item categiry 'L''. at bottom under Material Data tab if we click Components button.)
At this screen i need to validate the component materials with line item material. Can any body tell me the User Exit name or Badi name for this requirement.
Thanks.
Sekhar.J

Hi,
Enhancement object MM06E005 has screen exits and function module exits that allow you to add customer fields to purchase order processing - both header and item overview.
Check txn CMOD or SMOD. Use CMOD to create a project with this enhancement object.
Check these links :
Re: ME21N - PO Enhancement using BADI
Re: How make validations before saving a Purchase Order ?
Re: Accesing Item Line Level Texts from MM06E005 user-exits (ME21N)
BAPI_PO_CHANGE
--DECLARATION OF INTERNAL TABLES USED--
DATA : RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE.
DATA : HEADER1 LIKE BAPIMEPOHEADER.
DATA : POHEADERX LIKE BAPIMEPOHEADERX.
DATA : POITEM LIKE BAPIMEPOITEM OCCURS 0 WITH HEADER LINE,
POITEMX LIKE BAPIMEPOITEMX OCCURS 0 WITH HEADER LINE.
--APPENDING THE DATAS IN THE INTERNAL TABLE--
HEADER1-PO_NUMBER = '4500000001'.
HEADER1-CREATED_BY = 'divya'.
HEADER1-CREAT_DATE = '20060407'.
POHEADERX-PO_NUMBER = 'X'.
POHEADERX-CREATED_BY = 'X'.
POHEADERX-CREAT_DATE = 'X'.
POITEM-PO_ITEM = '10'.
POITEM-MATERIAL = 'RUBBER'.
POITEM-SHORT_TEXT = 'RUBBER PRODUCTS'.
APPEND POITEM.
POITEMX-PO_ITEM = '10'.
POITEMX-PO_ITEMX = 'X'.
POITEMX-MATERIAL = 'X'.
POITEMX-SHORT_TEXT = 'X'.
APPEND POITEMX.
*CALLING FUNCTION MODULE BAPI_PO_CHANGE
CALL FUNCTION 'BAPI_PO_CHANGE'
EXPORTING
PURCHASEORDER = '4500000001'
POHEADER = HEADER1
POHEADERX = POHEADERX
TABLES
RETURN = RETURN
POITEM = POITEM
POITEMX = POITEMX.
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.
--TO DISPLAY MESSAGES--
LOOP AT RETURN.
WRITE : RETURN-TYPE , RETURN-NUMBER , RETURN-MESSAGE.
ENDLOOP.
Make the above changes.
Th header is just a work area, not an internal table.
Refer ths thread and see if it has an answer:
FM BAPI_PO_CHANGE & new PO line items
Reward points
Regards

BADI/user exit for ME21N - Warning message for "our reference" field

Dear all,
I have a problem.
In ME21N, I need to show a warning message (message w... ) when user enter an already-used-before input in "Our reference' field (EKKO-UNSEZ).
I've tried in two methods.
1. Using fm EXIT_SAPMM06E_004. But it can only works for Error message. My warning message never shows up.
2. Tried to implement classic BADI ME_PROCESS_PO_CUST, using the PROCESS_HEADER method. Got the break-point spot on, but still didn't show the warning message.
Why is my warning message always got override?
Please advise.
Thanks in advance
Ahmad

Hi Ahmad,
Check the below links:
Unable to put Warning messages in ME21N and ME22N in Exit / BAdI in ECC 6.0
Warning message in me22n check user-exit can't process?
Custome warning message in T. code me51n me52n & me21n , me22n
Regards,
Nisha Vengal.

Badi & User Exit for ME21N & ME22N

Hi,
        My requirement is when a Purchase order is created using ME21n or when a line is added or changed using ME22n, the system should copy the vendors tax jurisdiction to the purchase order line items jurisdiction code. I tried badi (ME_PROCESS_PO_CUST) but could not suceed. Can any one tell me if any badi or user exit available for the same???
Thanks in Advance.

hi,
Enhancement/ Business Add-in            Description
Enhancement
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
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
MEETA001                                Define schedule line type (backlog, immed. req., preview)
ME590001                                Grouping of requsitions for PO split in ME59
M06E0005                                Role determination for release of purchasing documents
M06E0004                                Changes to communication structure for release purch. doc.
M06B0005                                Changes to comm. structure for overall release of requisn.
M06B0004                                Number range and document number
M06B0003                                Number range and document number
Business Add-in
ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Customer
ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
ME_PO_PRICING                           Enhancements to Price Determination: Internal
ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
SMOD_MRFLB001                           Control Items for Contract Release Order
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_REQ_POSTED                           Purchase Requisition Posted
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_BSART_DET                            Change document type for automatically generated POs
ME_BAPI_PR_CREATE_02
ME_BAPI_PR_CREATE_01
ME_BAPI_PO_CREATE_02
ME_BAPI_PO_CREATE_01
ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMITMENT_RETURN                    Commitment for return item
ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CHECK_OA                             Check BAdI for Contracts
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
No.of Exits:         35
No.of BADis:         55
Arunima

User EXIT, BADI for T-code ME21n, ME21

Hi Guru's,
I have rquirement where for some company codes user dont want GR and GR based invoicing if net price for PO is less than 100 GBP as it is very small quantity.
To achive this we have to uncheck Goods receipt check bax from tab 'Delivery' and uncheck inv. receipt check box from tab 'Invoice' of item level view at the time of PO creation.
Now, i am serching for User exit or BADI which will serve this purpose, as T-code ME21n is enjoy transaction for ME21 i dont think we will get any user exit, we have to do it through BADI.
If anyone has done something like this and have idea how i can achive this please revert back.
regards,
Rahul

http://www.erpgenie.com/sap/abap/code/abap26.htm
which gives the list of exits for a tcode
Below code will give a list of BADIs for particular transaction.
*& Report ZNEGI16 *
REPORT ZNEGI16 .
TABLES : TSTC,
TADIR,
MODSAPT,
MODACT,
TRDIR,
TFDIR,
ENLFDIR,
SXS_ATTRT ,
TSTCT.
DATA : JTAB LIKE TADIR OCCURS 0 WITH HEADER LINE.
DATA : FIELD1(30).
DATA : V_DEVCLASS LIKE TADIR-DEVCLASS.
PARAMETERS : P_TCODE LIKE TSTC-TCODE,
P_PGMNA LIKE TSTC-PGMNA .
DATA wa_tadir type tadir.
START-OF-SELECTION.
IF NOT P_TCODE IS INITIAL.
SELECT SINGLE * FROM TSTC WHERE TCODE EQ P_TCODE.
ELSEIF NOT P_PGMNA IS INITIAL.
TSTC-PGMNA = P_PGMNA.
ENDIF.
IF SY-SUBRC EQ 0.
SELECT SINGLE * FROM TADIR
WHERE PGMID = 'R3TR'
AND OBJECT = 'PROG'
AND OBJ_NAME = TSTC-PGMNA.
MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
IF SY-SUBRC NE 0.
SELECT SINGLE * FROM TRDIR
WHERE NAME = TSTC-PGMNA.
IF TRDIR-SUBC EQ 'F'.
SELECT SINGLE * FROM TFDIR
WHERE PNAME = TSTC-PGMNA.
SELECT SINGLE * FROM ENLFDIR
WHERE FUNCNAME = TFDIR-FUNCNAME.
SELECT SINGLE * FROM TADIR
WHERE PGMID = 'R3TR'
AND OBJECT = 'FUGR'
AND OBJ_NAME EQ ENLFDIR-AREA.
MOVE : TADIR-DEVCLASS TO V_DEVCLASS.
ENDIF.
ENDIF.
SELECT * FROM TADIR INTO TABLE JTAB
WHERE PGMID = 'R3TR'
AND OBJECT in ('SMOD', 'SXSD')
AND DEVCLASS = V_DEVCLASS.
SELECT SINGLE * FROM TSTCT
WHERE SPRSL EQ SY-LANGU
AND TCODE EQ P_TCODE.
FORMAT COLOR COL_POSITIVE INTENSIFIED OFF.
WRITE:/(19) 'Transaction Code - ',
20(20) P_TCODE,
45(50) TSTCT-TTEXT.
SKIP.
IF NOT JTAB[] IS INITIAL.
WRITE:/(105) SY-ULINE.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
Sorting the internal Table
sort jtab by OBJECT.
data : wf_txt(60) type c,
wf_smod type i ,
wf_badi type i ,
wf_object2(30) type C.
clear : wf_smod, wf_badi , wf_object2.
Get the total SMOD.
LOOP AT JTAB into wa_tadir.
at first.
FORMAT COLOR COL_HEADING INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 'Enhancement/ Business Add-in',
41 SY-VLINE ,
42 'Description',
105 SY-VLINE.
WRITE:/(105) SY-ULINE.
endat.
clear wf_txt.
at new object.
if wa_tadir-object = 'SMOD'.
wf_object2 = 'Enhancement' .
elseif wa_tadir-object = 'SXSD'.
wf_object2 = ' Business Add-in'.
endif.
FORMAT COLOR COL_GROUP INTENSIFIED ON.
WRITE:/1 SY-VLINE,
2 wf_object2,
105 SY-VLINE.
endat.
case wa_tadir-object.
when 'SMOD'.
wf_smod = wf_smod + 1.
SELECT SINGLE MODTEXT into wf_txt
FROM MODSAPT
WHERE SPRSL = SY-LANGU
AND NAME = wa_tadir-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
when 'SXSD'.
For BADis
wf_badi = wf_badi + 1 .
select single TEXT into wf_txt
from SXS_ATTRT
where sprsl = sy-langu
and EXIT_NAME = wa_tadir-OBJ_NAME.
FORMAT COLOR COL_NORMAL INTENSIFIED ON.
endcase.
WRITE:/1 SY-VLINE,
2 wa_tadir-OBJ_NAME hotspot on,
41 SY-VLINE ,
42 wf_txt,
105 SY-VLINE.
AT END OF object.
write : /(105) sy-ULINE.
ENDAT.
ENDLOOP.
WRITE:/(105) SY-ULINE.
SKIP.
FORMAT COLOR COL_TOTAL INTENSIFIED ON.
WRITE:/ 'No.of Exits:' , wf_smod.
WRITE:/ 'No.of BADis:' , wf_badi.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(105) 'No userexits or BADis exist'.
ENDIF.
ELSE.
FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
WRITE:/(105) 'Transaction does not exist'.
ENDIF.
AT LINE-SELECTION.
data : wf_object type tadir-object.
clear wf_object.
GET CURSOR FIELD FIELD1.
CHECK FIELD1(8) EQ 'WA_TADIR'.
read table jtab with key obj_name = sy-lisel+1(20).
move jtab-object to wf_object.
case wf_object.
when 'SMOD'.
SET PARAMETER ID 'MON' FIELD SY-LISEL+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
when 'SXSD'.
SET PARAMETER ID 'EXN' FIELD SY-LISEL+1(20).
CALL TRANSACTION 'SE18' AND SKIP FIRST SCREEN.
endcase.
It may help you.
Best Regards,
Vibha
*Please mark all the helpful answers

Need the user exit/BADI name for Reverese order MIGo- ME21N(changing item)

Hi
I have the below requirement.
I am changing the item details in the transaction MIGO transaction,the value of MSEG entries
are got changed.and also it should change in the Purchase order level also(in the table EKKO).
Can anybody tell me the User Exit /BADI name which is triggered in the Reverse order
i.e MIGO -> ME21N.So that i can implement my code in the reverse order in the User Exit/BADI.

hi I did not find any paramater type EKPO in the Exporting or changing of any methods in the BADI's given by you...........

In ME21N,User Exit/BADI for Defaulting Vendor number at item level.

Hi Experts.
In ME21N, for every purchase order, we have condtion tab for each line item.
Many condition typesot taxes are listed based on the config for the materials.
My requirements is, When we go inside by selecting a condition type we find vendor number displayed.
I need a user exit/BADI for defaulting the Vendor number.
Regards
Balaji R

Hi,
check with below link,
fo this one you will find both user exit and badis
https://www.sdn.sap.com/irj/scn/wiki?path=/display/abap/find%252bapplication%252bclass%252bwith%252bexits%252band%252bbadis%252bfor%252ba%252btransaction
Regards,
Madhu

User exit for ME21N for displaying the tax code from custom table

Hi,
I have a requirement, in our system, the inforecord is not maintain for all the material and vendor combination, we have a custom table in which we have maintain the
Compnay code, Pur. Org., Vendor code Tax code, juridiction code
now we want that when a Po is created with ME21 or ME21N the tax code and jurisdiction code should be come from this table and if entry not found in this table then it should search as per the regular process like from last Po or info record. then which user exit we can use for this.
regards,
zafar

CLOSE

ME21N Update Text in Line Item User Exit

Hi, I have created a new PO text item for use in ME21N that I want to populate from document details held in the material master. After entering a material number what user exit do I need to use to update internal tables for display of the document details before they are saved along with the other PO details. I know the tables where the material document details are held. Thanks.

BADI ME_PROCESS_PO_CUST.
Note that this BADI has a number of methods with parameters defined as "Importing" which makes it look like you cannot change data, but some of these parameters are "TYPE REF TO" objects which themselves have methods such as GET_DATA and SET_DATA that actually allow you to access and change the fields.
Search for previous posts including "ME_PROCESS_PO_CUST" - there is sample code in some of them.
In transaction SE19, if you display the BADI then select menu option goto>sample code>display, you will be able to drill down on the PROCESS_ITEM method to some SAP supplied sample code.
This includes the definitions and method calls to get the item data:
DATA: ls_mepoitem TYPE mepoitem.
ls_mepoitem = im_item->get_data( ).
You then just change relevant fields in structure ls_mepoitem and call the set_data method to pass the data back
call method im_item->set_data exporting im_data = ls_mepoitem.
Take care with what you change - SAP does not validate that you have passed back correct / consistant data.
Not sure if the text field you want will be available - you may need to look at further methods of the BADI or of the parameter objects. If you drill down on the objects that the method parameters are defined as TYPE REF TO you will see the methods that are available - the GET_DATA and SET_DATA ones I have mentioned above are only a small part of the options. If there are none dealing with texts at the Header / Line, then you may need to put your code in at the latest method available (once the PO number is allocated) and call the SAVE_TEXT function module to do your update - not 100% way of doing it because standard code may save in update event and have rollback handling.
To use the BADI you will need to create an implementation of it - there is a menu option in SE18 to do this, or you can use SE19.
Andrew

User exit in ME21N

hi everybody
I have added 2 additional fields(zzqty, zzprice) at item level in PO, Ive also added the subscreen in me21N
My requirement is that these 2 fields should be copied from the fields menge and netpr for each line
I have coded the following in the user exit
EXIT_SAPMM06E_016
DATA: ekpo type ekpo.
ekpo = i_ekpo.
ekpo-zzqty = i_ekpo-netpr.
ekpo-zzprice = i_ekpo-netpr.
FREE MEMORY ID 'CUS_AKTYP'.
EXPORT aktyp FROM I_AKTYP TO MEMORY ID 'CUS_AKTYP'.
EXIT_SAPMM06E_018
data: ekpo type ekpo.
move-corresponding ekpo to e_ci_ekpo.
but its not working
can somebody tell me wat im missing?

if you can tell me what you want to achieve , i can tell you what to code.
but as of now you can try with the below coding,
EXIT_SAPMM06E_016
DATA: ekpo type ekpo.
ekpo = i_ekpo.
ekpo-zzqty = i_ekpo-netpr.
ekpo-zzprice = i_ekpo-netpr.
EXPORT ekpo FROM ekpo TO MEMORY ID 'SOMEID'.
EXIT_SAPMM06E_018
data: ekpo type ekpo.
import ekpo to ekpo from memory id 'SOMEID'.
"this id is should be same as above
move-corresponding ekpo to e_ci_ekpo.

User exit for tcode ME21N and ME22N

Hi everyone
Can anybody tell me the user exits found in the tcodes ME21N nad ME22N, when saving a PO?
Regards
Anjali

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
MRFLB001            Control Items for Contract Release Order
MEQUERY1            Enhancement to Document Overview ME21N/ME51N
MM06E011            Activate PReq Block
LMEKO001            Extend communications structure KOMK for pricing
LMEKO002            Extend communications structure KOMP for pricing
If useful reward.
Vasanth

User exit for component data in ME21n/ME22n

Hello,
I have a requirement to issue an error message if a component quantity is not evenly divisible by the end item quantity. The component data (BOM) is entered after clicking the components button on ME21n/ME22n at the item level detail. I need to evaluate the data after a user clicks save, but I cannot find a user exit where the data is passed into, or where it is defined as global data where I can reference it in a user exit. The data is stored on the screen in structure MDPM and stored in the database in table RESB.
I appreciate any help,
David

Thanks for pointing me in the right direction.
I was able to put my code in EXIT_SAPMM06E_012 and retrieve the component data through (SAPLEINK)XMDPM[]
Below is the code I used to assign the data to be able to evaluate it.
FIELD-SYMBOLS: <z_mdpm_x> TYPE ANY.
DATA: i_mdpm_x TYPE STANDARD TABLE OF MDPM_X.
Fetching Component data
ASSIGN ('(SAPLEINK)XMDPM[]') to <z_mdpm_x>.
CHECK sy-subrc = 0.
Assigning data into an internal table
i_mdpm_x[] = <z_mdpm_x>.
CHECK i_mdpm_x[] IS NOT INITIAL.
David
Edited by: David Herrema on Oct 20, 2010 3:03 PM

User exit for ME21N (Not functional or customer exit)

Hi Guys,
I want to get a user exit for PO as my requirement is to call custom screen before the PO is getting saved.
I have the functional exits and badi's list which will not fulfill my requirement as because on my custom screen i have cancel button.
On clicking the control needs to come back to the me21n second screen with the data entered with out order getting created.
The screen number for the second screen in ME21N is 14.
if i call screen 14 it will work in a user exit where as in customer exit(functional exit) we have limitations with the exporting and importing as so the screen number will not be recognised.
I am able to do the same calling of cust screen in Sales order creation and is sucessfull, the same should happen with PO also.
Probably if the user exit triggers at the time of syntax check i can achive my requirement rather than at save as the call back to the screen will not harm and database commits will not take place.
I also tried with all most of the enahancement points but the call screen statement is not working at any point of time which worked with Sales order exits. So i tried with making the validation fail but still by that time the PO number is getting generated and so if i try to cancel the PO before save and trying to get PO in edit mode but the sequence number is getting missed by by 1.
Please help.
Regards,
Amar.
Edited by: amar srinivas on Feb 11, 2011 10:16 AM
Edited by: amar srinivas on Feb 14, 2011 4:56 PM

Hi,
You can try it this way.
Check badi ME_PROCESS_PO_CUST , method - CHECK.
This badi/method gets triggered when the "CHeck" button and "SAVE" button is pressed.
It consists of a changing parameter CH_FAILED . Pass X to it when cancel button is hit in your custom screen.
Donot use any commit in this method. Read the documentation before doing it.

User exit me21n

Similar Messages

Maybe you are looking for