User exit for field BEDNR in transaction ME22N

Hi experts ,
i want to use a search help for the field BEDNR in transaction ME22N . Is there any user-exit or badi available .
This field is in the PO header table. if any more clarification required please inform me

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

Similar Messages

User exits for saving in IQ02 transaction.

Hi All,
I have the following problem: The end user is unable to save few fields (Stock type, plant, storage location) data in IQ02 transaction.
1. Enter IQ02 transaction, give the material and serial number.
2. In SerData tab, give the stock type, plant and storage location
3. Now when I am trying to save, the following error is prompted: "System status ESTO is active (EQU 30055392)"
4. After this when I press continue button, the data is not saved.
I feel that there could be some problem in the user exits for this transaction. Please tell me the user exits for saving in this transaction.
Thanks,
Vishal.

Hi Vishal,
Please find list of userexit for Tcode IQ02 as below,
Exit Name           Description
IEQM0001            Add. checks for equip. installation at functional locations
IEQM0002            Additional checks for definition of equipment hierarchies
IEQM0003            Additional checks before equipment update
IEQM0004            Object is allowed for contract partner (Order->MaintCont.)
IEQM0005            Object allowed for SD contract (MaintContract->MaintCont.)
IEQM0006            Object allowed for SD contract (Maintain maintenance cont.)
IEQM0007            Check/change manufacturer field in equipment master.

User exit for Exchange rate in PO (ME22n) of Delivery/invoice Tab

Hi SDN,
We are using 4.6c. I wanna make the FIELD "Exchange rate" in Purchase Order (Tx: ME22n) of Delivery/invoice Tab into display mode. So can any one tell the USER EXIT i have to use to make SCREEN-INPUT = 0 for this screen field, MEPO1226-WKURS.
Thanks in Advance.
Regards
Basha

Transaction Code - ME22N                    Change 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
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sapgenie.com/abap/code/abap26.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://wiki.ittoolbox.com/index.php/HOWTO:Implement_a_screen_exit_to_a_standard_SAP_transaction
http://www.easymarketplace.de/userexit.php
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sappoint.com/abap/userexit.pdfUser-Exit
http://www.sap-img.com/ab038.htm
http://help.sap.com/saphelp_46c/helpdata/en/64/72369adc56d11195100060b03c6b76/frameset.htm
USER EXIT
http://www.sap-img.com/abap/a-short-tutorial-on-user-exits.htm
http://www.sap-img.com/abap/what-is-user-exits.htm
http://expertanswercenter.techtarget.com/eac/knowledgebaseAnswer/0,295199,sid63_gci982756,00.html
Rewards if useful.........
Minal

User exit for save button in transaction code CBIH82

HI All.
i have got an issue with finding of user exit for transaction code cbih82.
my functional consultant want me to go for exit CBIH_LB39_UE_POST_COMMIT (se37) but i cont find any user exit in this function module as it is triggering when i click on save at cbih82 in debugging.
but i cont find any user exit in this CBIH_LB39_UE_POST_COMMIT.
so could any one help me in this issue for finding user exit which should trigger when i click on save at cbih82 tcode.
will be waiitng for a good answer.
bye.
regards.
seetaram.

check in smod
user exits for CBIH82
Exit Name           -- Description
EHSIAHM1           -- EH&S: Menu Exit 1 for Incident/Accident Log Header
EHSIAHM2           --- EH&S: Menu Exit 2 for Incident/Accident Log Header
EHSIAPM1           --- EH&S: Menu Exit 1 for Incident/Accident Log Person
EHSIAPM2           -- EH&S: Menu Exit 2 for Incident/Accident Log Person
EHSMPHM1        --   EHS: Menu Exit 1 for Measurement Project Header Data
EHSMPHM2         -- EHS: Menu Exit 2 for Measurement Project Header Data
EHSMPJM1          -- EHS: Menu Exit 1 for Measurement Project Measurements
EHSMPJM2          -- EHS: Menu Exit 2 for Measurement Project Measurements
EHSSARA            -- EHS: Check/Edit Lines in SARA List Before Printout
Salil...
Edited by: salil chavan on Nov 19, 2008 8:23 AM
Edited by: salil chavan on Nov 19, 2008 8:25 AM

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 field addition on standard SAP Screen

Hi,
I want to add one customer specific field on notification at header level. I have found one enhancement i.e. user exit QQMA0001, which says that this is to be used for adding the extra field on the notification header. Now my question is that
1. If I have to add the field, how user exit can help (I am aware that user exist consists of the function module, screen exit, programme and includes. Now do I need to use the screen exit for this or something else?)
2. Other question is that before going to screen exit in the above step, do in need to add the field in structure VIQMEL and the respective table QMEL or when the table QMEL is updated then the field in structure VIQMEL will get auto updated.
3. If the step 2 is only sufficient, then why is the need of step 1, I mean what is the point in considering the user exit i.e. we can simply update the QMEL data table and then this field will get autoavailable on the structure and after going to SE51, if we view the field added, then we can place it wherever we want on the screen of notification.
Request for the reply.

Thanks Pete,
I am not a developer and a functional person and right now i am in very initial phase with no developer around.
I got most of the points you mentioned here
Creation of data elemnt
Append the data table
Create the new subscreen for the main programme and then assign this subscreen to the notification type in SPRO.
If i am rightly followed then my questions are
1. What is the role of user exit here?
2. Why functional module is required here?
3. SE51 transaction you mentioned is the screen painter, Is it possible to create sub screen there. If no then where the new sub screen will be created i.e. T code in ABAP.
And the fianl question is that -
I f i succeed in attaching the subscreen to the notification type and my sub screen is only for one field then is it possible for me to set it up as a header data and place it anywhere below the notification user status field because i dont want to display it as subscreen bu header level information.
Thanks

User Exit for VA01 and VA02 transaction codes

Hi,
I am writing a userexit for PO number checking for VA01 and VA02 transaction codes.The PO number should be unique in the table (vbkd-bstkd).Duplicate PO number entries can be checked with Sold-to Party.If anybody written something like this....please advice me...
Thanks in advance.
fractal

Hi Fractel,
Why are you looking for a user exit to do this duplicate PO check?
This can be achieved through configuration of your sales order document type and message control. Follow the path below for configuration of the document type.
Implementation Guide for R/3 Customizing (IMG)
-->Sales and Distribution
   -->Sales
      -->Sales Documents
         -->Sales Document Header
            -->Define Sales Document Types
Once you execute this node, you will see all the available document types. Select the one you are interested in and click the details icon. In the subsequent screen, under "General Control" section, there is a field "Check purch.order no". Pick the value 'A' from the drop-down list.
Once you do this, system will check for duplicate PO numbers whenever you are creating or changing the sales order with that document type. If duplicate, it issues a message.

User Exit for PO creation(me21n and me22n) - A/c assgn Category is existing

Hi all,
I would like to have your guidance to find out an appropriate EXIT to meet the following req.
Requirement is such that : This EXIT should generate a G/L account automatically (or over-write the existing G/L a/c) during any PO creation(me21n and me22n tcodes - before saving) based on the fields(mandatory) :
A/c Assignment Category,
Material,
Company code and
Vendor
entered by the user(during his/her PO creation activity)
The identified EXITS as of now are EXIT_SAPLEBND_002 (But the package is not matching our PO tcodes : me21n and me22n)
and EXIT_SAPMM06E_017(Package ME- same as tcodes me21n,me22n)
and even other Exits available for PO based on <b>before saving</b> activity.
Even I tried out creating a PO in debugging mode(with break points set at the above EXITs).
Please do help me out at the earliest to identify the appropriate EXIT to meet this requirement.
With Regards,
Srividya

Hi!
in SMOD give MM06E005 enhancement
FM name
EXIT_SAPMM06E_017
This will be triggered during saving.
Regards
Tamá

User Exit for field resb-wempf in MB21

Hello Guru's,
I wish to put personal no. in this field resb-wempf for only a single material code.I used this Enhancement MBCF0002 and inserted my code also but while doing MB21 it is not stopping here please guide how to move ahead.
Thanks in advance.
Regards

hi,
use this exit.
MBCF0007.
EXIT_SAPMM07R_001.
TI_RESB_NEW STRUCTURE RESB
TI_RESB_OLD STRUCTURE RESB.

Regarding the User Exit for Goods Receipt (MIGO) Transaction code

Hi,
I have a requirement where I want to capture the Goods Receipt Document number when its got saved (Created).
I have find out Exits available for the MIGO.
MB_CF001
MBCF0002
MBCF0005
MBCF0006
MBCF0007
MBCF0009
MBCF0010
MBCF0011
I want to know which is the right one to serve my purpose (Exit Name).

Hi Nikhil.
I'm not sure which one is the best (there are several exits in SAP).
But what i usually do is:
- i have a dummy project in DEVELOPMENT SYSTEM, where i include the enhancements i suspect that solve my problems.
- then i set the project active, break point ... that's it.
Hope this helped.
Reward helpfull ideas.
Best regards.
Valter Oliveira.

Urgent: User exit for ME22N and ME32K transactions

I need to know a user exit(s) for changing Purchase Order and Contract line item fields from EKPO table. Please let me know if you know any. BADIs are also fine if the user exit does not exits. Thanks

Dear AP,
   I'm enlisting all the exits :-
Transaction Code - ME22N             Change Purchase Order
Exit Name
Description
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
No of Exits:         35
Transaction Code - ME32K                   Change Contract
|Exit Name|Description                                   |
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
No of Exits:         35
Regards,
Deva.

User Exit for checking Purchase Requisitioner Field in CJ20N Transaction

Hi,
I want user Exit for checking Purchase Requisitioner field while making PR through CJ20N transaction. I have trie EXIT_SAPLEBND_001 user exit. Problem in this user exit is I am not getting Purchase Requisitioner No & Item No in I_CEBAN
structure.
Please suggest what to do ?
Regard's
Shabbir

Hi,
You can check with this BADI ME_PROCESS_REQ_CUST.
Kindly refer below mentioned link for further details:
Badi ME_REQ_POSTED For CJ20N Transaction
Hope this will help you.
Regards,
Mudita

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.

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

How to find the user-exit for transaction fpp2

Hi experts,
could you help me how can I find the user-exit for transaction fpp2. I tried to after the package, but I did not find it.

Hi,
Use the following program to find user exits of specified code.
*& Tables
TABLES : tstc,     "SAP® Transaction Codes
         tadir,    "Directory of Repository Objects
         modsapt, "SAP® Enhancements - Short Texts
         modact,   "Modifications
         trdir,    "System table TRDIR
         tfdir,    "Function Module
         enlfdir, "Additional Attributes for Function Modules
         tstct.    "Transaction Code Texts
*& Variables
DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE.
DATA : field1(30).
DATA : v_devclass LIKE tadir-devclass.
*& Selection Screen Parameters
SELECTION-SCREEN BEGIN OF BLOCK a01 WITH FRAME TITLE text-001.
SELECTION-SCREEN SKIP.
PARAMETERS : p_tcode LIKE tstc-tcode OBLIGATORY.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN END OF BLOCK a01.
*& Start of main program
START-OF-SELECTION.
Validate Transaction Code
SELECT SINGLE * FROM tstc
    WHERE tcode EQ p_tcode.
Find Repository Objects for transaction code
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 = enlfdir-area.
        MOVE : tadir-devclass TO v_devclass.
      ENDIF.
    ENDIF.
Find SAP® Modifications
    SELECT * FROM tadir
      INTO TABLE jtab
      WHERE pgmid    = 'R3TR'
        AND object   = 'SMOD'
        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:/(95) sy-uline.
      FORMAT COLOR COL_HEADING INTENSIFIED ON.
      WRITE:/1 sy-vline,
      2 'Exit Name',
      21 sy-vline ,
      22 'Description',
      95 sy-vline.
      WRITE:/(95) sy-uline.
      LOOP AT jtab.
        SELECT SINGLE * FROM modsapt
        WHERE sprsl = sy-langu AND
        name = jtab-obj_name.
        FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
        WRITE:/1 sy-vline,
        2 jtab-obj_name HOTSPOT ON,
        21 sy-vline ,
        22 modsapt-modtext,
        95 sy-vline.
      ENDLOOP.
      WRITE:/(95) sy-uline.
      DESCRIBE TABLE jtab.
      SKIP.
      FORMAT COLOR COL_TOTAL INTENSIFIED ON.
      WRITE:/ 'No of Exits:' , sy-tfill.
    ELSE.
      FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
      WRITE:/(95) 'No User Exit exists'.
    ENDIF.
ELSE.
    FORMAT COLOR COL_NEGATIVE INTENSIFIED ON.
    WRITE:/(95) 'Transaction Code Does Not Exist'.
ENDIF.
Take the user to SMOD for the Exit that was selected.
AT LINE-SELECTION.
GET CURSOR FIELD field1.
CHECK field1(4) EQ 'JTAB'.
SET PARAMETER ID 'MON' FIELD sy-lisel+1(10).
CALL TRANSACTION 'SMOD' AND SKIP FIRST SCREEN.
I executed the above program but there are no user exits for the specified Transaction.
Thanks,
Naveen Kumar.

User exit for field BEDNR in transaction ME22N

Similar Messages

Maybe you are looking for