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

Similar Messages

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.

Enhancement/BAdi/User Exit for ME21N

Hi
i am looking for a modification/enhancement/BAdi or userexit that would be triggered when the document type is changed on purchase order type in transaction ME21N.
can anyone help?
i have seen there are lots of many exits available, but i am after something more specific....
if anyone could help and point me in the right direction it would be much appreciated.
i found enhancement MEQUERY1, but not sure if i could utilise this for my needs.
thanks

i used the BAdi ME_PROCESS_PO_CUST and method PROCESS_ITEM
with this code:
METHOD if_ex_me_process_po_cust~process_item.
DATA: ls_mepoitem   TYPE mepoitem,
        ls_mepoheader TYPE mepoheader.
DATA: header_obj TYPE REF TO if_purchase_order_mm.
* get header data
header_obj = im_item->get_header( ).
ls_mepoheader = header_obj->get_data( ).
* get item data
ls_mepoitem = im_item->get_data( ).
IF ls_mepoheader-bsart = 'ZPSC' AND ls_mepoitem-umson IS INITIAL.
* Message: PSC Order requires 'Free' indicator selected
    MESSAGE e017(zenhance_msgcl).
ENDIF.
ENDMETHOD.

BADI / User exit for Purchase order(ME21N) after saving the document

Hi expert,
I need the BADI / User exit for Purchase order(ME21N) after saving the document
This is for email sending after create the purchase order so PO document number will be the import parameter
pls help me
point will be reward
Regards,
Ganesh

Hi Ganesh,
Could you please share your solution?
Thanks.
Hoops
Edited by: Hoops on Jun 13, 2011 10:51 PM

User Exit for ME21n - Urgent

HI all,
I want to add a function module when a Purchase order is saved(ME21n), i want to know how to find user exit for ME21n & which user exit to be changed.
I want to call a function module when the user saves the purchase order, please help.
Please also let me know the step to find the user exits.
Thanxs in advance.

Hi,
Please check enhancement MM06E005 (SMOD).
Here list of User exit and BADI for ME21N .
Transaction Code - ME21N                    Create Purchase Order
Enhancement/ Business Add-in            Description
USER EXIT
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
MM06E011                                Activate PReq Block
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
LMEDR001                                Enhancements to print program
LMEKO001                                Extend communications structure KOMK for pricing
LMEKO002                                Extend communications structure KOMP for pricing
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
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
M06B0002                                Changes to comm. structure for purchase requisition release
Business Add-in - BADI
ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
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_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
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_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
ME_PURCHDOC_POSTED                      Purchasing Document Posted
ME_RELEASE_CREATE                       BAdI: Release Creation for Sched. Agreemnts with Rel. Docs
ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
ME_REQ_POSTED                           Purchase Requisition Posted
ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
MM_EDI_DELFOR_OUT                       Enhancements for IDoc Output of SA Releases: Internal
MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
MM_EDI_ORDERS_OUT                       Enhancements for IDoc Output of Purchase Order: Internal
SMOD_MRFLB001                           Control Items for Contract Release Order
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
ME_BAPI_PR_CHANGE_01                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)
ME_BAPI_PR_CHANGE_02                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Change)
ME_BAPI_PR_CREATE_01                    BAdI: Enjoy BAPIs for Purchase Requisitions
ME_BAPI_PR_CREATE_02                    BAdI: Enjoy BAPIs for Purchase Requisitions (Method Create)
ME_BSART_DET                            Change document type for automatically generated POs
ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
ME_CIP_REF_CHAR                         Facilitates Reference Characteristics in Purchasing
ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
<b>Reward points</b>
Regards

BADI / user exit for Tcode IW32?

Hi
Are there any BADIs / user exits for changing component data in Transaction IW32 for a maintainance order?
regards
cs

Enhancement
IWO10012                                Maintenance order: Priority handling on central header
Business Add-in
IWO_UI_USEFLEX                          BAdI for Calling Up an Alternative UI
I hope it helps.
Best Regards,
Vibha
Please mark all the helpful answers

BADI/User Exit for KO02

Dear Experts,
When I'm setting the BUDGETED status manually to Internal Order (With out distributing the Budget to Order in IM52) and after if I m setting RELEASE status the system is accepting. So, I want to stop this without giving the budget in IO, it should not accept to release IO.
This is not possible with User Status, coz' User may go and set manually "REL" Status.
can anyone suggest me the BAdi/User Exit for KO02(Internal Order Change) tcode.
Thanks,
Sanju.

When you set a User status , you can assign an Authorization Object on who can change the status .
Follow the path in SPRO--> Controlling --> Internal orders --> Order Master Data > Status Management> Define authorization Keys for Status Management
Define Authorization Keys for Status Management
In this step you define authorization keys which you can use to set up authorization checks when you manually set or delete a user status. When the system sets a user status as a reaction to business transaction, it does not perform an authorization check.
When you set or delete a user status, the system checks whether the user is authorized for this action. In addition to the status profile and the object type, the system also checks the authorization key assigned to the user status in question.
Example
You want to define that certain user statuses can be changed only by a specified employee group.
To do this, create an authorization key and assign it to the relevant user statuses.
In the general authorization maintenance you can then assign authorizations for this key via the authorization object B_USERSTAT.
Activities
1. Check whether you want to define authorizations for your user statuses.
2. If necessary, create authorization keys as follows:
a) Choose "New entries".
b) Enter a key and an explanatory text in the appropriate fields and choose "Save".
You have now created the authorization key.
3. Assign the authorization key to one or more user statuses in your status profile.
4. Define corresponding authorizations and include them in the relevant authorization profiles.

BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE initial screen

Hi All,
I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.
please provide your suggestions.

Hi,
here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
DATA: faelligkeit TYPE d,
        faelligkeit_text type c length 10,
        meldungstext TYPE c LENGTH 100.
FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
IF sy-uname = 'XYZ'.
*    BREAK-POINT.
    READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
      ASSIGNING <it_source>.
    faelligkeit = <it_source>-dfaell.
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
       EXPORTING
         DATE_INTERNAL                  = faelligkeit
       IMPORTING
         DATE_EXTERNAL                  = faelligkeit_text
       EXCEPTIONS
         DATE_INTERNAL_IS_INVALID       = 1
         OTHERS                         = 2
    IF sy-subrc <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    IF faelligkeit <> sy-datum.
      CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
      CALL METHOD pi_proxy_messages->set_message
        EXPORTING
          pi_message_id       = 'T0'
          pi_message_number   = '101'
          pi_message_severity = 'E'
          pi_message_var1     = meldungstext
        EXCEPTIONS
          OTHERS              = 4.
    ENDIF.
ENDIF.
It is not a really nice coding but it shows in a simple way how to use the BAdI.
Regards
Robert

BADI/ User Exit for transaction FTR_EDIT/FTR_CREATE

Hi All,
I want a BADI/User Exit for FTR_EDIT/FTR_CREATE transactions to validate company code and partner fields.

Hi,
here is a coding example that I implemented in the BAdI FTR_TR_GENERIC. This coding is executed when the user press the check button. The method is EVT_TRANSACTION_CHECK. This example is checking the payment date dfaell if it is equal to the system date. If not then a message is sent to the message handler. Here is the code:
DATA: faelligkeit TYPE d,
        faelligkeit_text type c length 10,
        meldungstext TYPE c LENGTH 100.
FIELD-SYMBOLS: <it_source> LIKE LINE OF pi_proxy_transaction->a_tab_conditions.
IF sy-uname = 'XYZ'.
*    BREAK-POINT.
    READ TABLE pi_proxy_transaction->a_tab_conditions INDEX 1
      ASSIGNING <it_source>.
    faelligkeit = <it_source>-dfaell.
    CALL FUNCTION 'CONVERT_DATE_TO_EXTERNAL'
       EXPORTING
         DATE_INTERNAL                  = faelligkeit
       IMPORTING
         DATE_EXTERNAL                  = faelligkeit_text
       EXCEPTIONS
         DATE_INTERNAL_IS_INVALID       = 1
         OTHERS                         = 2
    IF sy-subrc <> 0.
       MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    IF faelligkeit <> sy-datum.
      CONCATENATE 'Fälligkeit' faelligkeit_text 'incorrect' INTO meldungstext separated by space.
      CALL METHOD pi_proxy_messages->set_message
        EXPORTING
          pi_message_id       = 'T0'
          pi_message_number   = '101'
          pi_message_severity = 'E'
          pi_message_var1     = meldungstext
        EXCEPTIONS
          OTHERS              = 4.
    ENDIF.
ENDIF.
It is not a really nice coding but it shows in a simple way how to use the BAdI.
Regards
Robert

BADI/User Exit for custom table update from Delivery

Hi
Our requirement is to update a custom table with the delivery number and other related details when the picking status is changed to "C". Kindly suggest BADI/User exit for this requirement .
Thanks in Advance for your immediate help .

Hi Joseph,
See SAP Note 415716 - User exits in delivery processing. It says when you have the document number available, what is permitted, what not, ....
I hope this helps you
Regards
Eduardo

BADI / USER-EXIT FOR DEFAULTING THE FIELD VTTK-TNDR_ACTC IN TCODE VT01N

Hi,
I require a BADI / USER-EXIT for defaulting the field VTTK-TNDR_ACTC(Currency of Actual Shipment costs) to 'EUR' in transaction VT01N(Shipment Transaction) .
Please could anyone help me with this .
Regards,
Sushanth H.S.

Hi!
User Exits in Transportation
In Transportation, there are enhancements that you can use with transaction CMOD.
For a detailed description of the individual enhancements, see the documentation on the individual enhancements or function modules in transaction SMOD.
You can display all enhancements that are available for the area of transportation by choosing F4 in the Enhancement field. Enter V56* in the Enhancement field and choose Execute. Enter V54* to get a list of all enhancements for the area of shipment cost processing.
Business Add-Ins in the transports
Business add-ins (BADIs) are predefined user exits. They enable businesses, partners, and customers to add additional softward to the SAP source code. The linkup of SAP's New Dimension Products, such as APO and BW, to the standard system is thus possible.
Customer-specific functions can be executed before the save time and after the database update.
The following methods are available for the BADI with the definition name 'BADI_LE_SHIPMENT':
AT_SAVE: BADI is called up at the time of the save. Checks and return to dialog are possible.
BEFORE:_UPDATE: BADI is called up right before the data is saved to the database, that is, when all the data is available (for example, internal ly assigned shipment number).
IN_UPDATE: BADI is called up after the database update.
Standard Settings
Creating a BADI method:
Call up transaction SE19. Enter a name of your choice. Choose "create" and in the dialog box enter the definition name 'BADI_LE_SHIPMENT'. Afterwards, enter a short text for implementation. Save the BADI.
On the tab page 'Interface', choose the method for implementation by double-clicking on it. Now you can enter your customer-specific program code. Save and activate the code. You can acess the transmission parameters entered in the BADI definition. With the method ***_AT_SAVE you can initiate the exception ERROR_WITH_MESSAGE (description 'An error message has occurred' ) if you wish to return to the dialog.
Afterwards, go to the heading and activate the interface.
Regards
Tamá

User exit - for ME21N, 22N, 23N - at line item level

Hi,
I want to add new text field to display the description of the MPM(material) in it.
That filed I want to add to the Account Assignment tab at item level.
How to add that field on the screen, I mean any screen exit for this?
and function module to pass the data to that field.
If anybody worked on such problem then pls. let me know.
Thanks in advance.
-- Umesh

Hi,
These are the user exits for me21n.
AMPL0001
LMEDR001
LMELA002
LMELA010
LMEQR001
M06B0001
M06B0002
M06B0003
M06B0004
M06B0005
M06E0004
M06E0005
ME590001
MEETA001
MEFLD004
MELAB001
MEVME001
MM06E001
MM06E003
MM06E004
MM06E005
MM06E007
MM06E008
MM06E009
MM06E010
MMAL0001
MMAL0002
MMAL0003
MMAL0004
MMDA0001
MMFAB001
Regards
praveen

User-Exit for the Me22n

Hi,
I am Mohan. I faced on Problem with the User Exit. I write the user exit for the ME21n for PO Creation. While Creation of the PO the Purchase Requition is mandatory. it is working for the ME21n. But PO creation is another two ways is there. Those are ME22N (Purchase order---> Create) and ME23N
(Purchase order---> Create) for this case also my condition applicable but it is not working for this case. How to write the Code for this. by using Sy-ucomm also. but it is not working.
Please help me.
Regards,
Mohan

Following the user exit's related to ME22N transaction.
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
Regards.

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.

BADI/user exit for transcation code "BP" in CRM

Hi Experts,
Is there a BADI / user exit that is triggered after successful saving/updating of Business Partner using transaction code "BP"?
We want to send general infos such as partner number, Name, Birth date, etc. about the business partner being created/updated using IDoc.
We are using CRM WinClient 4.0.
If you know the steps on how this requirement will be done, kindly post them.
Thank you very much.

I don't have any CRM system at hand, but I'm sure there are some BAdI's for this. Look in SE18 for BP or BUS, and i'm sure you will find something.
One suggestion though: Before going for the BadI, try and see if CRM also uses change pointers for sending Idoc's . This case you wont need any user exits / badis, an probably no programming at all.
Transaction
BD50: Activate Change Ptrs for Mess. Type
BD61: Activate Change Pointers - Generally
and use report RBDMIDOC for triggering IDoc.

Badi & User Exit for ME21N & ME22N

Similar Messages

Maybe you are looking for