Customer Subscreen for Purchase Requisition

Hello All,
I need a custom subscreen on requisition at <b>HEADER</b> level.  'MEREQ001' adds a screen at item level. Is there any Screen Exit / BADI to add a custom screen at header level? Any kind of help is really appreciated.
Thank you all,
Chandni

Hi Chandi Reddy,
The t.code is ME51 For this available exits are :
AMPL0001  User subscreen for additional data on AMPL
LMEDR001  Enhancements to print program
LMELA002  Adopt batch no. from shipping notification when posting
LMELA010  Inbound shipping notification: Transfer item data from
LMEQR001  User exit for source determination
LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
LWSUS001  Customer-Specific Source Determination in Retail
M06B0001  Role determination for purchase requisition release
M06B0002  Changes to comm. structure for purchase requisition rel
M06B0003  Number range and document number
M06B0004  Number range and document number
M06B0005  Changes to comm. structure for overall release of requi
M06E0004  Changes to communication structure for release purch. d
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., previe
MEFLD004  Determine earliest delivery date f. check w. GR (only P
MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
MEQUERY1  Enhancement to Document Overview ME21N/ME51N
MEVME001  WE default quantity calc. and over/ underdelivery toler
MM06E001  User exits for EDI inbound and outbound purchasing docu
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 P
MM06E008  Monitoring of contr. target value in case of release or
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 proces
MMAL0004  ALE purchasing info record distribution: Inbound proces
MMDA0001  Default delivery addresses
MMFAB001  User exit for generation of release order
MRFLB001
For t.code we51n the available exits and badi are :
Enhancement/ Business Add-in            Description
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
o.of Exits:          1
o.of BADis:          3
Rewards some points.
Rgds,
P.Naganjana Reddy

Similar Messages

  • Custom Event for Purchase Requisition Create, Change & Delete

    Hello Experts,
    I want to create a custom event which triggers on Purchase Requisition Create, SAP provide's standard event's for purchase requisition release but not for create.
    What are all the steps and how to create a new event.
    Thanks in Adavance,
    Sandhya.

    Hi Sandhya,
    may i know the reason why you are trying to create custom methods.
    You have business object BUS2009(for PR line item wise release) and BUS2105(for PR overall release).
    Both those business object have events RELEASESTEPCREATED (for PR creation) and SIGNIFICANTLYCHANGED(For PR change).
    Even then if you want to create custom events, create a subtype of the standard business object, then click on events, and then select create. Now create your Z-events, say ZCREATED (For creation), ZCHANGED (for changed) and ZDELETED (for deleted). Now select each event, click on edit -> Change release status -> object type component -> to be implemented. Follow the same for all the events. Then select each event, click on edit -> Change release status -> object type component -> to be released.
    Now click on your custom object, click on edit -> Change release status -> object type component -> to be implemented.Then click on your custom object, click on edit -> Change release status -> object type component -> to be released.
    After this in SWEC tcode, click on new entries. Select change document object as BANF, business object as say ZBUS2105 and event as ZCREATED. make sure radio button on create is checked.
    Similary create entries for ZCHANGED event and ZDELETED.
    Select on change and on delete radio button for event ZCHANGED and ZDELETED event respectively.
    let me know if you have any queries.
    Regards,
    Raj

  • Change customer for purchase requisition

    Hi gurus,
    i'm trying to change customer number for purchase requisition.
    i tried to enter this code in badi ME_PROCESS_REQ_CUST~PROCESS_ITEM but KUNNR is not changed:
      DATA : ls_item_data   TYPE mereq_item,
             ls_item_datax  TYPE mereq_itemx,
             lv_obj         TYPE REF TO object,
             lv_attr        TYPE string,
             lv_aktyp       TYPE aktyp,
             lv_kunnr       TYPE ekunnr.
      FIELD-SYMBOLS : <fs_lcl> TYPE any,
                     <fs_source> TYPE any.
      IF im_count EQ 1.  " to avoid infinate Loop"
    Access Attributes value of Local Class
    for getting the transaction mode of Line item
    H-> Create
        lv_obj ?= im_item.
        MOVE 'MY_STATE->AKTYP' TO lv_attr.
        ASSIGN lv_obj->(lv_attr) TO <fs_lcl>.
        lv_aktyp = <fs_lcl>.
        IF lv_aktyp EQ 'H' OR lv_aktyp EQ 'V'.        "While creating line item"
    Extracting existing Item Data and Modify the fields
    Requestor Name (AFNAM) & Source of supply details
          CLEAR : ls_item_data.
          ls_item_data = im_item->get_data( ).
         ls_item_datax = im_item->get_datax( ).
         MOVE ls_item_data-ernam TO ls_item_data-afnam.
          lv_kunnr = '0000100000'.
          ls_item_data-kunnr = lv_kunnr.
             ls_item_datax-kunnr = 'X'.
         im_item->set_datax(
         EXPORTING
         im_datax = ls_item_datax ).
          im_item->set_data(
          EXPORTING
          im_data = ls_item_data ).
        ENDIF.
      ENDIF.
    when trying changing other fields like AFNAM for example, the data is changed.
    the customer number exists in KNA1.
    any ideas?
    Thanks,
    Sagit.

    SEARCH  SEARCH  SEARCH  SEARCH  SEARCH  SEARCH  SEARCH
    Good work

  • 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

  • Customer field to purchase requisition

    Hello,
    I add the customer field at subscreen of purchase requisition ( at the data base table i add the relative field in ci_ebandb include ) by EXIT_SAPLMEREQ_001 and
    EXIT_SAPLMEREQ_002 and EXIT_SAPLMEREQ_003.
    I add the same customer field at subscreen of purchase order ( at the data base table i add the relative field in ci_ekpodb include ) by EXIT_SAPLMEREQ_016 and EXIT_SAPLMEREQ_017 and EXIT_SAPLMEREQ_018.
    The problem is: when i convert the purchase requisition in purchase order, the data into customer field of
    purchase requisition not are transfert in the customer field of purchase order.
    thanks for help,
    Roberto Baldassarre.

    correction **
    tks for your help,
    but i had just done it. I explain with detail my step:
    I add the customer field at subscreen of purchase requisition by
    EXIT_SAPLMEREQ_001 and EXIT_SAPLMEREQ_002 and EXIT_SAPLMEREQ_003 (at
    the data base table I add the relative field on ci_ebandb include).
    I add the same customer field at subscreen of purchase order by
    EXIT_SAPMM06E_016 and EXIT_SAPMM06E_017 and EXIT_SAPMM06E_018 (at
    the data base table i add the relative field on ci_ekpodb include).
    Step followed:
    1. add field at EBAN table by CI_EBANDB include
    2. add same field at EKPO table by CI_EKPODB include.
    3. write code at EXIT_SAPLMEREQ_001,EXIT_SAPLMEREQ_003 following
    document's help.
    4. write code at EXIT_SAPMM06E_016, EXIT_SAPMM06E_017 ,
    EXIT_SAPMM06E_018 following document's help.
    5. build dynpro 0111 on function group XM02
    6. build dynpro 0111 on function group XM06
    The problem is: when i convert the purchase requisition in purchase
    order (ME59n), the data into customer fields of purchase requisition
    not are copied in the customer fields of purchase order (this field are
    empty).
    Tks for your help!

  • 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.

  • Account assignement category for purchase requisition - error message

    Hi All!
    I created a new Item category in service order (IW31) "O" with the account assignment category "O". If I don't set the Consumption posting indicator to V for this category, when I set the account assignment category "O" to the purchase requisition in <i>Plant Maintenance and Customer Service-Maintenance and Service Processing-Maintenance and Service Orders-General Data-Define Account Assignment Category/Document Type for Purchase Requisitions</i>, I receive the message:
    <b>"Acct. assign. cat. "O" for purchase req. does not exist.
    Message no. CS 075"</b>
    The client request is not to charge immediately for the goods receipt with the relevant costs the service order. The client wants to create the goods receipt in a storage location for the plant and then confirm the components and charge the costs after the component confirmation (movement type 261) - similar to stock material.
    Any idea about what should I do?
    Thank you.

    Hi Everyone,
    The problem is solved now. The cause was that the test requisition that I was making was satisfying more than one rules and hence I end dated the remaining rules which solved the problem.
    Thanks!

  • Redetermine release strategy for purchasing requisitions

    Hi Guys,
    How can I redetermine the release strategy for purchasing requisions when changes on the costcenter (EBKN-KOSTL)  are done -
    I know that it will be redermined when I add the costcenter as charateristics in customizing for release strategy but thats not an option
    I also tried to add coding in userexit for changing the communication strategy (Include ZXM06U13) but this exit doesn't provide information of the document number and position (EBAN, EBKN ..) so I can't find out if changes have been made
    I spend several hours trying to find solutions for this issue but no working results so far ..
    I hope you can help me on that
    TIA
    Manuel

    Hi,
    Note that EBKN will have entries corresponding to a PR only when it is        
    saved or checked, so KOSTL will not have any values for a PR which is under              
    creation. You should always use fields from structure CEBAN while             
    creating characteristics for Requisition release procedure as it              
    contains most of the relevant data about a PR under creation/change.
    I would advice you to check the note 365604.
    Please also check the changeability indicator in the customizing:
    transaction OLME -> Purchase Requisitions -> Release Procedure -> Procedure with Classification -> Set Up Procedure with Classification -> Release indicator -> check the detail screen for settings.
    Please check additionally the possible values for your characteristic cost centre (transaction CT04).
    Regards,
    Edit

  • 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

  • Table for Purchase Requisition Item Text

    I would like to know, what is the table which stores the item text in tab texts for Purchase Requisition?

    Hai,
    the table is STXH.
    CALL FUNCTION 'READ_TEXT'
          EXPORTING
      CLIENT                        = SY-MANDT
            ID                            = IT_STXH-TDID "ID
            LANGUAGE                      = IT_STXH-TDSPRAS " LANGUAGE
            NAME                          = IT_STXH-TDNAME
            OBJECT                        = IT_STXH-TDOBJECT
      ARCHIVE_HANDLE                = 0
      LOCAL_CAT                     = ' '
    IMPORTING
      HEADER                        =
          TABLES
            LINES                         = L_LINES
    Regards,
    Venkat

  • 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

  • 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

  • SAP  workflow for purchase requisition and purchase  order

    Hello  Sap Workflow,
    Can you  please help me on  building workflow for purchase requisition and  purchase order    with  the necessary screen shots  ?
    your quick response  will be greatly appreciated.
    Thanks in Advance

    Hi,
    Please check http://help.sap.com .
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/04/92761846f311d189470000e829fbbd/frameset.htm
    http://help.sap.com/erp2005_ehp_04/helpdata/EN/04/92775546f311d189470000e829fbbd/frameset.htm
    Configuration guides are available in SAP Solution Manager.
    Regards,
    Masa

Maybe you are looking for