User Exit when save Purchase Requisition (ME51N and ME52N)

Hy Everyboby,
I want to know an enhancement point/user exit activated when saving a Purchase requisition to control all item amount for a budget check.
So anyone can help me ?
Thanks in advance.

Hi All,
i am working on an enhancement where in i need to enhance the transactions ME41,42 , ME51n, 52n and ME21n and ME22n.
the requirement is whenever a PR is created/modified (ME51/52) and a business document is attached to it, then the same business document should be available in the RFQ created for this PR as an attachment. and the same flow should happen while creating the PO using the RFQ. I am unable to find a correct user exit for this requirement. kindlyreply me if you have any solutions for it.
your help is very much appreciated.
thanks,
Mohan

Similar Messages

User Exit ME51N/ME52N/ME53N when save purchase requisition

Hi,
I want to validate purchase requisition data for release startegy. If there is no value for release startegy .Then ME51N/ME52N/ME53N populate a custom message before saving.
I have found the Enhancement MEREQ001.Can anyone help me to find the exit because there are 10 user exit for this enhancment.
Thanks in advance,
Harinder

Hi,
Follow the following steps to find the EXIT
1. Open transaction SE24.
2. Now open the object CL_EXITHANDLER in display mode.
3. Go to the method tab and double click on the method GET_INSTANCE.
4. Put a break point on cl_exithandler=>get_class_name_by_interface.
5. Now execute the transaction you want to find EXIT for, it will take you to the above method.
6. Write EXIT_HANDLER in fieldnames and hit enter, it will tell you the EXIT used for your transaction.
7. Hit F8 and it will tell you all the EXITu2019s for your transaction.
Now put break points in each user exit and check which one gets triggered for your transaction.
Regards,
Manish

User exits when posting purchase document and goods movement (GR)

I want to update some custom tables when posting PO and goods movement (GR) .
Please suggest user exits for both posting.

Check the below exists
FOR PO
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
For Goods Movement
LMR1M001            User exits in Logistics Invoice Verification
LMR1M002            Account grouping for GR/IR account maintenance
LMR1M003            Number assignment in Logistics Invoice Verification
LMR1M004            Logistics Invoice Verification: item text for follow-on docs
LMR1M005            Logistics Inv. Verification: Release Parked Doc. for Posting
LMR1M006            Logistics Invoice Verification: Process XML Invoice
MRMH0001            Logistics Invoice Verification: ERS procedure
MRMH0002            Logistics Invoice Verification: EDI inbound
MRMH0003            Logistics Invoice Verification: Revaluation/RAP
MRMN0001            Message output and creation: Logistics Invoice Verification

User exit/BADI for Purchase requisition through release of Process order

Hi ,
i need to add some text to the Pur Req.
The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
regards

Hi
Check the following Exits and BADI for Pur Requisition
Enhancement
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
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
MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
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
Business Add-in
ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
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: Custome
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_PURCHDOC_POSTED                      Purchasing Document Posted
SMOD_MRFLB001                           Control Items for Contract Release Order
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)
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_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
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
ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
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
Reward points if useful
Regards
Anji

User Exit for getting Purchase Requisition Release Strategy

Hi Experts,
When a user creates a PR I need to know the user exit I need to implement so that the First Approver (Processor) text in the Release Strategy is populated from a custom table. I have seen that the field is MEREL_S_GRID1-STEXT. I also need to know if I can implement a user exit so that it pulls the release strategy for a PR for assets (Acct Category A) since it is pulling for Acct Category K (Cost Centre) and the Release Strategy tab is appearing in this case.
Kind Regards,
Darlington

Hi Meenakshi,
Thanks for the very useful answer. It has given clues on how to resolve this issue. I have resolved this issue for the Asset item category using the following thread: user exit for requisition release strategy, and also SAP Note 365604.
However, I have another issue, the release strategy for Stock Items, (item category blank) is not pulling through. I need to use the same method above but would like to know how it determines the funds centre for a specific stock item. I couldn't find where that is implemented in the material master and I need info on how to determine the account assignment for stock items based on the funds centre.
Regards and Thanks.

User exit when save production order

Hello,
I have to fill the OVERHEAD KEY field value in production order header at runtime based on some calculation. So I need a user exit which can be used to save the value of overhead key.
I already tried the exits PPCO0001, PPCO0007, PPCO0006, PPCO0012, and PPCO0018 but these all are not working for me as I am trying to insert or change the value of Overhead key(ZSCHL) but at the last value is not changing at all .
Please suggest me if you have any solution.
Thank you in advance!!!
Rock,

My question was:
I need a user exit, using which I can change the value of overhead key at runtime.
suppose I am creating a production order with a sales order (CO08), and overhead key value is NULL currently.....but at the time when I save that production order based on sales order type I have to enter the value of overhead key.....for that I need a user exit where I can change the value of overhead key
at runtime.
I already tried the exits PPCO0001, PPCO0007, PPCO0006, PPCO0012, and PPCO0018 but these all are not working for me as I am trying to insert or change the value of Overhead key(ZSCHL) but at the last value is not changing at all .
Please suggest me if you have any solution.
Thank you in advance!!!
Rock,

User Exit M06B0001 for Purchase Requisition Releases WF

Hi All,
I'm having some trouble with the User Exit M06B0001. I am trying to add logic in here to determine the correct agents based on release codes, cost centers etc. and send emails to the required agents.
Some background info: we are using BUS2105 (for overall release), with a custom WF based on the standard WS20000077, all the release strategies are configured..
My understanding was that when a PR is created and saved, the RELEASESTEPCREATED (this is what i configured in SWE2) event is kicked off and my WF is started, which all works fine. I thought it was at this point that the user exit M06B0001 was initiated.
But, what's happening is that if a user creates the PR and hits the "check" button (before hitting save), it hits the Exit several times...I thought it would only hit the exit once the WF was kicked off. Right now, it's hitting the Exit twice for each level of release, for example if a PR has level's 10,20,30, in the Exit (via Debug) the i_frgco shows 10,20, 30 and then again 10,20,30...so it goes in there 6 times (I get 6 emails from myself)! Once the user saves...it again hits the Exit, but without hitting my breakpoint (I know it's going in there because I get a 7th email..this time from the Wf-batch user)- this is the correct thing that is supposed to happen.
I would appreciate it if someone could explain this User exit to me and how it is supposed to work.
Thanks,
Suman

Hi:
Since it calls in include so it not necessary that exit signature you'll get.
You have 2 ways to find it out
1. go in se37 and put EXIT_SAPLMEREQ_006, select where used list - it would go in include -> again select include -> click on where used list -> it would give the calling position- just check the required data
2. Put the break point at the calling postion and check its parameters
Regards
Shashi

USer Exit/BADI for Purchase requisition creation in MDBT or WC27 /MRP Run

I am looking for an enhancement where a purchase req is created during MRP Run in the background ( MDBT or WC27 or program - RMMRP000 .
Any suggestions would be welcome.

Hi,
try the exits:
LMDR2001 User exits restr. profiles of opt. pur.ord.
LMDZU001 User exits in additional planning
Regards,
Renjith Michael.

User exit to change Purchase requisition created from VA01

Hi,
I am using item categories ZRUI and ZRUD for which PR is created in VA01 while saving the sales order.
I need to change address data in such PR. Can anyone suggest user exit to be used??

Hi,
You may use USEREXIT_MOVE_FIELD_TO_ME_REQ.
You can find this in include MV45AFZB.
<REMOVED BY MODERATOR>
Regards,
Sharad
Edited by: Alvaro Tejada Galindo on Jul 21, 2008 12:37 PM

How to find the ME29N 'USER EXIT' when our save the release PO after.

How to find the ME29N 'USER EXIT' when our save the release PO after.
which user exit will be used?
thanks.
alex.

Hi,
process :
    go to tranx code :   ME29N ,
       System---->Status , here copy the program name (SAPLMEGUI),
     go to abap editor and specify the program name SAPLMEGUI and find the package "ME".
     tranx code : CMOD , Utilites--->Sap Enanchement,
                                     specify the package name : ME
                                      and execute, displays a list of exits ,
                             and find out our suitable exit based on requirement.
check these :   EXIT_SAPMM06E_021
reg
Siva

Badi/user exit in tcodes me54n,me55,me28 and me29n

hi all,
1.which is the badi/user exits that is there in me54n and me55...for saving and releasing purchase requisation(s) .
2.which is the badi/user exits that is there in me28 and me29n...for saving and releasing purchase order(s) .
points will be rewarded.
regards,
johnson

Transaction Code - ME54N                    Release Purchase Requisition
Enhancement
MEREQ001                                Customers' Own Data in Purchase Requisition
Business Add-in
ME_COMMITMNT_PARKING                    BAdI for Redefining Commitment Interface When Parking
ME_MEREQ_PARKING                        BAdI Purchase Requisition: "Hold"
ME_REQ_HEADER_TEXT                      Copy Header Text: Enjoy Purchase Requisition
Transaction Code - ME55                     Collective Release of Purchase Reqs.
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.
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_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

FB60 Looking for user exit at Save

hello all,
   i need to do some verification on the company code and wbs. It would be best if i could find a user exit when the Save button is executed. Does anyone have any ideas ?
           thanks Scott

The below program gives all the user exits..try the program and awards points if it was useful
*& Report ZUSER
REPORT ZUSER no standard page heading.
*& Enter the transaction code that you want to search through in order
*& to find which Standard SAP User Exits exists.
*& 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 Modifactions
    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.
Thanks and regards.

How To Restrict Users To Only Create Purchase Requisitions with Item Catalog?

Hi, everyone
Please help me,
How To Restrict Users To Only Create Purchase Requisitions with Item Catalog? is it possible?
Regards, Manuel

Hi Steenie Norman
First click on the text item ---> Tools ---> Property Pallete ---->
and change the Keyboard State to Local Only also this Depend in your OS
hope this useful ....
Regards
Mohammed

Need User Exit before the Purchase Order saved!!!

Hai All,
 I am in search for User Exit before the Purchase Order gets saved.This User Exit should capture this generated Purchase Order and post it to the Destination System for further processing.
 Can anyone help me to find this User Exit.
Thanks,
Ugandhar.
Message was edited by: Ugandhar Domathoti

Check out this enchancement in smod MM06E001
in that EXIT_SAPLEINM_001
 EXIT_SAPLEINM_002
may help you ....
regards
vijay

Transfer attachment document from purchase Requisition(ME51n,ME52n) to Purc

Hi
How to do Transfer attachment document from purchase Requisition(ME51n,ME52n) to Purchase order(ME21n,ME23n).

Hi Muthu,
I understand that it is possible to bring attachments from ECC to the SRM system for the new release.
However, I have a slightly different question.
If I want to bring in requirements from a legacy system to SRM 7.0 system directly, what is the feasability of the same? If I have an attachment linked in the legacy system, then is it possible to bring it in SRM 7.0 system directly or will I be forced to route it to ECC 6.0 and then use the Plan Driven Procurement scenario for getting it into SRM?
Regards,
Abhilash

User Exit when save Purchase Requisition (ME51N and ME52N)

Similar Messages

Maybe you are looking for