User status for purchase requisition

Dear all,
I have a basic question. I have created a status profile using transaction BS02. Now I want to apply that to purchase requisition. However I could not find any way to assign it to the PR (specially in PR document type).
Request your inputs in this regard.
Snigdho

Stefano,
   I dont think you can control the display mode on just one operation using any of the exisitng user exists or using the user status.
   The only way, that i think would be possible in this cenario, would be to intimate the responsble person or any specific user whenever there is change on the order which has a operation with a specific user status set. You can create a standard task (or workflow) to get this functionality accomplished.
Thansk
Narasimhan

Similar Messages

  • User exit for Purchase requisition

    Hello team
    At the time of creating the purchase requisition we want to know how much qty in order unit with their UOM .
    How to get this functions , Any user exit , Any sort of input will be highly appreciated
    Thanks
    JJ

    BAdI: Customer BAdI for Enjoy Purchase Requisition BAPIs
    Use
    This Business Add-In is used in the component MM-PUR.
    It makes available the two methods INBOUND and OUTBOUND.
    The INBOUND method (method for changing the import data of the Enjoy PR BAPIs) is invoked when the BAPIs PurchaseRequisition.CreateFromData1 and PurchaseRequisition.Change1 are invoked, before the data is passed on to mapping. Call up transaction code SWO1 and choose the business object BUS2105 (inbound delivery).
    The Inbound method (method for changing the export data of the Enjoy PR BAPIs) makes available the parameters passed on to the function modules BAPI_PR_CREATE and BAPI_PR_CHANGE.
    The Outbound method offers the parameters that can be returned to the function modules BAPI_PR_CREATE, BAPI_PR_CHANGE, and BAPI_PR_GETDETAIL.
    For more information, refer to the interface documentation: IF_EX_ME_BAPI_PR_CREATE_02
    Standard settings
    The BAdI can be used multiple times.
    There is no default implementation.
    Information about the implementation of BAdIs in the context of the Enhancement Concept is available in the SAP Library for SAP NetWeaver under BAdIs - Implementation.
    Example
    The class CL_EXM_IM_ME_BAPI_PR_CUST is available for an example implementation.

  • User Exit For Purchase Requisition *** FM

    Hi all,
    We have Funds management activate system.
    While creating purchase requisition currently system displays the msg if available balance is exausted.
    My requirement is :
    During PR creation, each time it should pop up a message of the available fund in the fund center selected by the user no matter it is exausted or it is available.
    Is there any user exit available for this while PR creation.I searched enhancements for PR but they are of no use.May in Funds Management some exit will be there.
    Please help.
    Regards,
    Sunny

    Hi,
    Please check the the FM EXIT_SAPLMEREQ_010 of user exit MEREQ001.
    Thanks and Regards,
    Jayakrishnan R

  • User Exit for Purchase Requisition Number Range

    Dear Experts,
    I searched on sdn, i got M06B0003 &M06B0004 this 2 user exit for PR Number range.
    I have activated both User exits but while creating PR is not getting effect of that user exit.
    I have checked by putting Break-point in respective user exit but while saving the PR it should go to that break-point but it not going there aslo.
    And also i have checked user exit MM06E003 but it is for Purchase Order number range.And for PO it is working.
    Please help me to solve this issue.Solution will be appreciated.
    Regards,
    Sanket.

    Hi,
    Sorry that badi will not help try this one ...EXIT_SAPLMEREQ_009 in MEREQ001 where the export parameters is purchase requisition number....
    Thanks,
    Shailaja Ainala.

  • BADI/User exit for Purchase Requisition from MRP

    I am looking for a BADI or any enhancement when a purchase requisition is created or modified from MRP .ie. MD50 transaction. Can anyone help ?
    THanks in advance.

    Hello Shareen
    Have you had a look at package <b>MD03 </b>(contains transaction MD50). It contains lots of BAdIs. Perhaps the following ones may be useful:
    MD_PLDORD_CHANGE (BAdI for Changing Planned Orders)
    MD_PURREQ_CHANGE (BADI for changing purchase requisitions)
    However, I should mention that I have not found anything when I checked the <i>Where-Used-List</i> for these BAdIs (on ECC 5.0).
    Regards
      Uwe

  • FM for Purchase requisition status

    Hi,
      Is there any FM for Purchase requisition status.
    Do let me know.
    Regards,
    SP

    Hi,
    Check this FM, hope this will solve ur problem.
    'BAPI_ACC_PURCHASE_REQUI_CHEC'

  • 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

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • Report - who is the current approver for purchase requisition

    Hi Experts
    Is there a report that can give information the status / who is the current approver for purchase requisition?
    currently if we open the PR directly, we can only know the release strategy, release code, status of approver, but we cannot have the information who is the person that should approve this PR.
    Thanks in advance
    Prashanth.v

    Hi All.
    Unfortunately we want to have this information for our end user, and they will not have the access to SE16.
    Another thinks is from CDHDR we will have the information if changes are made in PR. So it will give information user that already approve the PR
    What we want to have is a report of outstanding PR (not yet released) that have information who is the user (the user complete name / user id)  that should approve the PR.
    Thanks In Advance
    Prashanth.Venkategowda

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • Materials available only for Purchase requisition creation

    Hi Experts,
    My client wants some materials available only for Purchase requisition creation and some materials donu2019t want available only for Purchase requisition creation.
    How we can control
    Thanks in advance,
    Chandhu

    1) Solve your issue first you have to bifurcate between the materials where requisition is possible & where not...u can do this by selecting some field which is not in use presently in material master-basic data view & maintain some unique value for those materials for which PR will be not possible....otherwise check whether you can bifurcate it through material groups or not...
    After this take help of your ABAP person and implement BAdI::ME_PROCESS_REQ_CUST...here use the logic that after user enters the material code in PR system will check in the background what has been maintained in the said field in the basic data view of the material...if found blank then it will allow the user process further or if found any data in that field then system will stop the user from processing the same by throwing some customized error message.
    2) Use the Plant-sp.matl status in purchasing view as Blocked for procment/whse for those material against which you don't want to create any PR.But this will be plant specific and both PR & PO will get blocked.
    Regards,
    Indranil

  • No selectable items exist for purchase requisition l_banfn

    Hi,
    While creating PO with ref to PR getting the below error :
    no selectable items exist for purchase requisition l'banf .
    Checked if the PO is created, its not created,.
    checked if the item is blocked/cancelled/deleted. Nothing is set.
    PR looks fine. Dont know if any authorization data is missing?

    Check the status tab in ME53N whether all the qty in PR are already used up
    Or
    Check the line item in PR whether it is deleted
    Edited by: Karthik on Jul 20, 2011 12:37 PM

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    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
    Rgds,
    Naren

  • Regarding report for purchase requisition

    Hi gurus,
          I am preparing a report for purchase requisitions using SQVI. I am almost done with it but I was stuck at one thing. Our client criteria is to see it by name like they wanted users to view only purchase requisitions they created. They dont want all users to see purchase requisition created by other users. I dont know how to do that. Can anyone help me out with that.
         let me know if I am not clear about anything.
    Thanks in advance.
    Ravi Teja Boppana

    Hi,
          I added the field ERNAM from table EBAN. But the problem I am facing with it is any user can enter any user name in that field. Either I need that feild to be filled automatically with the username who logged in so that I can hide that field if that can be changed or filled automatically and cannot be change by user. Is there any option I can do like that. If I create a report in SQVI no one else except me can see that report, so I need this report in that manner.
          Let me know if i am not clear,
    Thanks in advance,
    Ravi Teja Boppana

  • BADI for Customer's own screen for Purchase Requisition.

    Hi All,
    I have a requirement where I need to create a BADI implementation for creating addition screens in the Purchase Requisition Transaction (ME51n/ME52n/ME53n).
    I know there are User exits but we donu2019t want to implement them. Now in case of PO there is a standard SAP given BADI -> ME_GUI_PO_CUST for Customeru2019s own screen but as far as my understanding goes there are no such BADIs for Purchase Requisition.
    Could anyone please advice if I can create a Custom BADI similar to ME_GUI_PO_CUST for PR for adding the screen and throw some light on it like how can this be achieved?
    Thanks,
    Ameesha

    Thanks Darek for replying back and the BADI   ME_BAPI_PR_CUST looks helpful but could you please help me in understanding how can i create my own custom screens within ME51N / ME52N / ME53N tcode using the BADI , ME_BAPI_PR_CUST.
    For example in PO, we have the BADI   ME_GUI_PO_CUST, with several methods like SUBSCRIBE and others which we can make use of for creating screen exits but what in the case of PR fpr BADI  ME_BAPI_PR_CUST. i couldn't find any sample code for implementing this.
    Any help is greatly appreciated.
    Thanks,
    Ameesha

Maybe you are looking for