Approver SAP ID for purchase requesition

Dear team,
I have approver workflow for Purchase Requesition, now I want to pull the history of PR from 2012 to 2015 current month. Here main requirement is the approver name who has approved the PR, but don't find any standard report or table where I can find this detail. Please guide me how I can pull this data from SAP.

Dear ME5A will not give us the apprver detail but in SCN i found help & did same. I got my result.
Thanks for your quick response.
(1) Browse table CDHDR (Change document header), specify:
Change doc. Object = BANF
Object value = PR number (remember to add first 2 zeros) i.e. 0010002620
Transaction = ME54N (release manually) and/or ME55 (collective release)
The result showing the user who has run transaction ME54N and/or ME55 for the PR, then user may be the approver of the PR. If multiple records found for a particular PR, it may be approve/reject several times.  You may only extract the latest record.
(2) Because transaction ME54N can either approver or reject PR, it is necessary to further check table CDPOS (Change document items), specify:
Change doc. Object = BANF
Document number = <found in step (1)>
Table Name = EBAN (Purchase Requisition)
Field Name = FRGKZ (Release Indicator)
In the result, if field FRGKZ (Release Indicator) changed from Old value 'X' (blocked) to New value '2' (PO creation allowed), we know that the user found in step (1) is the PR approver.

Similar Messages

  • Is it possible Line level approval in AME for purchasing requisition?

    hi
    is it possible Line level approval in AME for  purchasing requisition ?
    so that send each line to separate approver ?

    If using AME, it should be possible. Check AME Guide for POs for details. Let me know if you run into issues.
    Thanks
    Shree

  • 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

  • What is  Sap Scripts for purchase order

    hai,
    what is the sap script or smart form for purchase order,
    and how to modify the existing standerd one.
    explain me in step by step.

    hi
    Please ask question on sapscript in sapscript forum.
    use sap script form  medruck for PO
    SmartForm /BPR3PF/MMPO_L is the standard delivered Purchase Order in 4.6c
    Transaction code m/34 allows you to associate your 'Y' copy of the standad PO to your included company specific PO requirements such as company log graphic and other particulars.
    Go to transaction OMFE. Tell me what you see there for the output type you are interested in. Let me take the standard output type NEU. The entry looks something like this.
    NEU Purchase order 1 SAPFM06P ENTRY_NEU MEDRUCK.
    The first one is your output type, next is its description, next is the medium, then the program, routine, and the form name.
    You already copied the layout MEDRUCK to ZMEDRUCK. Now copy SAPFM06P to ZZSAPFM06P. Now ENTRY_NEU routine is in the include FM06PE02. You need to make your changes here to accommodate for the new field. So copy this include to ZZFM06PE02 and make your changes. Also, in ZZSAPFM06P, change the line where it says INCLUDE FM06PE02 to INCLUDE ZZFM06PE02.
    Now in this routine ENTRY_NEU, there is a function module call ME_READ_PO_FOR_PRINTING which reads in the PO data from the tables. We need to copy this function module as well as this is where you will do your extra selections for the new fields. You will do the same with the other function call ME_PRINT_PO, if you need to change anything on the print.
    after this to define output type...
    NACE
    You can track the form and the print program used for that form
    NACE is used to create output type while creating the output type you will mention forms, and driver program.
    that will be maintained in the table TNAPR.if you create the output type using NACE then it will be automatically visible in table NAST and TNAPR.
    so check in NAST, TNAPR table
    http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1989fe43b111d1896f0000e8322d00/frameset.htm
    Condition records in NACE?
    EX--in simple terms..take a transaction say ME21N ( Purchase Order ), u can see a Print icon there. now when u click on this icon, it has to print the PO document. Now how does it do that? when u click Print, the control gets transffered to a print program, now which program gets triggered is decided by what program name u specify in NACE.
    So in NACE>EF>Output Type>NEU>processing routine--> u can see some standard program already configured( maybe SAPFM06P n form MEDRUCK )..these are the programs n sapscript that gets executed wen u say "PRINT" in the transactrion...so u can customise the print program for customer changes over here by copying the standard program n form into a Z/Y one and replacing the program names in NACE.
    Yogesh N
    Edited by: Yogesh N on Aug 20, 2008 3:19 AM

  • Which are the most popular reports in SAP BI for Purchasing and Sales

    Hi Experts,
    I'm looking to work on one completed BI content flow.
    I wanted to work on 1 report from each module to activate the relevant objects.
    Can anyone please let me know which reports in Purchasing and Sales are frequently used in SAP BI.
    Thanks

    Hi,
    Please check table - RSRREPDIR       
    Report names which are related to purchasing  - 0PUR_C0N_Q00Y, N and Y indicates number.
    same for sales report names - 0SD_C0N_Q00Y .
    Query tech names - 0PUR_C01_Q0021
    Thanks

  • Standard SAP report for purchase price variance

    Hi All,
    I need to know if there is a standard SAP report that shows the purchase price variance.
    Thanks,
    Regards

    Hi Ritika,
    There is no standard report available to compare purchase order price cost and standard cost of a material.
    You can check if FBL3N helps to resolve your purpose or not. Or else you have to make a customized report with the help of ABAP'er on the informations based on the following tables.
      MBEW
            EKKO
            EKPO
            EKBE
           MKPF       
            MSEG                  
            KEKO
            KEPH,                        
            BKPF                                            
            BSEG                                          
            LFA1         
    Thanks,
    Vasanthan

  • Picking the correct vendor for purchase requesition

    Hello
    We have done a carv out of an system for a client and they have abandond SRM and MDM. since the new company only are using one catalog, all of these materials are established as standard material master. But there is a small problem, when we are creating serviceorders in IW31, and PR are created on the bases of this the vendor/inforecord is not picked up, so at the creation of PO the purchaser must add the vendor after he has picked up the PR. The inforecord exists for only one combination of material-vendor. I have tried to create a sourcelist for the material, the settings in the sourcelist are a date range (010110-311210) the vendor, purchorg, the tick for fixed source is set and the MRP value is set to 1. Then I belived that it should have been picked up during creation of the PR. If i go into the PR an click on "assign source of supply" it picks the correct vendor and inforecord, there are no options, there are no contracts. What can i do to make the PR pick this automaticly?
    Regards
    Ivar

    I tried that but it did not work. We have also since last time maintained some values in OMI8. and set the parameter EVO on the user, but nothing helps. So now we have called in the abap-man to se if he can debugg whats wromg. Since after the small changes we did, when creating the PR manually in ME51N it picks up the vendor and inforecord without clicking on, basicly we set the pid EVO on the user and it defaults the sourcedetermination tick in ME51N to be set.
    But sitll not possible to get it from the serviceorder in IW31, the PR that are created in the background there still is without vendor and inforecord.
    Any more tips?
    regards
    Ivar

  • Offline approval for Purchase order response

    Hi All,
    Currently we are in SRM 7.02. we want to know whether offline approval is applicable for Purchase order response (PCO).
    I have searched all available blogs but in Vain. Hope someone can enlighten me in this topic
    Regards,
    Nishanth

    Hi Nishanth,
    We have implemented custom solution for the same in line of SC offline approval process.
    And its working fine in Production environment.
    Check this blog for SC:
    http://scn.sap.com/docs/DOC-56096
    http://wiki.scn.sap.com/wiki/display/SRM/Debugging+hints+for+sending+email+in+offline+approval
    Thanks
    Ankit Jain

  • Idocs for Purchase RFQ

    Hi Friends,
    Does anybody knows how to configure, an Outbound Idoc to non SAP application for Purchase Request For Quotation? And after inbound a similar Idocr for update Quotation into SAP using estandar Idocs messages?
    Thanks for your help,
    Andres.

    Hi
    Check these links for Idoc
    Data Creation in Idoc
    IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
    asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
    While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
    IDoc is a intermediate document to exchange data between two SAP Systems.
    *IDocs are structured ASCII files (or a virtual equivalent).
    *Electronic Interchange Document
    *They are the file format used by SAP R/3 to exchange data with foreign systems.
    *Data Is transmitted in ASCII format, i.e. human readable form
    *IDocs exchange messages
    *IDocs are used like classical interface files
    IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    FOr testing you can use WE19.
    How to create idoc?
    *WE30 - you can create a IDOC type
    For more information in details on the same along with the examples can be viewed on:
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
    http://www.sappoint.com/presentation.html
    http://www.allsaplinks.com/idoc_search.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://www.erpgenie.com/sapedi/idoc_abap.htm
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30 )
    Create Message Type ( WE81 )
    Assign Idoc Type to Message Type ( WE82 )
    Creating a Segment
    Go to transaction code WE31
    Enter the name for your segment type and click on the Create icon
    Type the short text
    Enter the variable names and data elements
    Save it and go back
    Go to Edit -> Set Release
    Follow steps to create more number of segments
    Create IDOC Type
    Go to transaction code WE30
    Enter the Object Name, select Basic type and click Create icon
    Select the create new option and enter a description for your basic IDOC type and press enter
    Select the IDOC Name and click Create icon
    The system prompts us to enter a segment type and its attributes
    Choose the appropriate values and press Enter
    The system transfers the name of the segment type to the IDOC editor.
    Follow these steps to add more number of segments to Parent or as Parent-child relation
    Save it and go back
    Go to Edit -> Set release
    Create Message Type
    Go to transaction code WE81
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter
    Click New Entries to create new Message Type
    Fill details
    Save it and go back
    Assign Message Type to IDoc Type
    Go to transaction code WE82
    Change the details from Display mode to Change mode
    After selection, the system will give this message “The table is cross-client (see Help for further info)”. Press Enter.
    Click New Entries to create new Message Type.
    Fill details
    Save it and go back
    Check these out..
    Re: How to create IDOC
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    ALE/ IDOC
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    go trough these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
    1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
    2.IDOCs are independent of the sending and receiving systems.
    3.IDOCs are independent of the direction of data exchange.
    The two available process for IDOCs are
    Outbound Process
    Inbound Process
    AND There are basically two types of IDOCs.
    Basic IDOCs
    Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
    Extended IDOCs
    Extending the functionality by adding more segments to existing Basic IDOCs.
    To Create Idoc we need to follow these steps:
    Create Segment ( WE31)
    Create Idoc Type ( WE30)
    Create Message Type ( WE81)
    Assign Idoc Type to Message Type ( WE82)
    imp links
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    www.sappoint.com
    --here u can find the ppts and basic seetings for ALE
    http://sappoint.com/presentation.html
    www.sapgenie.com
    http://www.sapgenie.com/ale/index.htm
    WE30 - you can create a IDOC type.
    An IDOC with data, will have to be triggered by the application that is trying to send out the data.
    Try this..Hope this will help.
    >>>> SAP ALE & IDOC<<<<
    Steps to configuration(Basis) >>
    1. Create Logical System (LS) for each applicable ALE-enabled client
    2. Link client to Logical System on the respective servers
    3. Create background user, to be used by ALE(with authorizaton for ALE postings)
    4. Create RFC Destinations(SM59)
    5. Ports in Idoc processing(WE21)
    6. Generate partner profiles for sending system
    The functional configuration(Tcode: SALE)
    • Create a Customer Distribution Model (CDM);
    • Add appropriate message types and filters to the CDM;
    • Generate outbound partner profiles;
    • Distribute the CDM to the receiving systems; and
    • Generate inbound partner profiles on each of the clients.
    Steps to customize a new IDoc >>>
    1. Define IDoc Segment (WE31)
    2. Convert Segments into an IDoc type (WE30)
    3. Create a Message Type (WE81)
    4. Create valid Combination of Message & IDoc type(WE82)
    5. Define Processing Code(WE41 for OUT / WE42 for IN)
    6. Define Partner Profile(WE20)
    Important Transaction Codes:
    SALE - IMG ALE Configuration root
    WE20 - Manually maintain partner profiles
    BD64 - Maintain customer distribution model
    BD71 - Distribute customer distribution model
    SM59 - Create RFC Destinations
    BDM5 - Consistency check (Transaction scenarios)
    BD82 - Generate Partner Profiles
    BD61 - Activate Change Pointers - Globally
    BD50 - Activate Change Pointer for Msg Type
    BD52 - Activate change pointer per change.doc object
    BD59 - Allocation object type -> IDOC type
    BD56 - Maintain IDOC Segment Filters
    BD53 - Reduction of Message Types
    BD21 - Select Change Pointer
    BD87 - Status Monitor for ALE Messages
    BDM5 - Consistency check (Transaction scenarios)
    BD62 - Define rules
    BD79 - Maintain rules
    BD55 - Defining settings for IDoc conversion
    WEDI - ALE IDoc Administration
    WE21 - Ports in Idoc processing
    WE60 - IDoc documentation
    SARA - IDoc archiving (Object type IDOC)
    WE47 - IDoc status maintenance
    WE07 - IDoc statistics
    BALE - ALE Distribution Administration
    WE05 - IDoc overview
    BD87 - Inbound IDoc reprocessing
    BD88 - Outbound IDoc reprocessing
    BDM2 - IDoc Trace
    BDM7 - IDoc Audit Analysis
    BD21 - Create IDocs from change pointers
    SM58 - Schedule RFC Failures
    Basic config for Distributed data:
    BD64: Maintain a Distributed Model
    BD82: Generate Partner Profile
    BD64: Distribute the distribution Model
    Programs
    RBDMIDOC – Creating IDoc Type from Change Pointers
    RSEOUT00 – Process all selected IDocs (EDI)
    RBDAPP01 - Inbound Processing of IDocs Ready for Transfer
    RSARFCEX - Execute Calls Not Yet Executed
    RBDMOIND - Status Conversion with Successful tRFC Execution
    RBDMANIN - Start error handling for non-posted IDocs
    RBDSTATE - Send Audit Confirmations
    FOr testing you can use WE19.
    Check these links.
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://www.sapgenie.com/sapedi/idoc_abap.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sappoint.com/abap.html
    http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
    http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
    http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
    http://www.sapgenie.com/sapedi/index.htm
    http://www.allsaplinks.com/idoc_sample.html
    http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
    Please check this PDF documents for ALE and IDoc.
    http://www.sappoint.com/abap/ale.pdf
    http://www.sappoint.com/abap/ale2.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
    Check below link. It will give the step by step procedure for IDOC creation.
    http://www.supinfo-projects.com/cn/2005/idocs_en/2/
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Standard smartform for Purchse requesition slip

    Dear Friends,
    What is standard smartform for Purchase requisition slip
    Regards,
    Reddy

    hii
    standard program for purchase requesition is SAPMM06B.but not smartform .check it i hope it will help you.
    regards
    twinkal

  • Storing Attachments for Purchasing Documents

    Standard SAP functionality for purchasing document attachments stores the files on the SAP Database (for both SRM and ECC).
    /cisap/edoc/<SYSID>/<filename>
    SAP does not appear to provide a straight forward way to configure a different storage location on a file server. Post go live, and before space runs out in the database, a new approach will have to be implemented for the physical storage location of purchasing document attachments.
    MY Client would prefer to store these attachments on a file server.
    Please suggest me how to do it,
    Thanks & Regards
    Sada

    Cancelled.

  • Workflow to send mail for purchase requisation and approval msg which automatically updates sap

    I am new to workflow,I need to create work flow for purchase requisation and send mail for concern person for approval,like if he clicks approve in mail ,automatically it should get updated in sap if he rejects then he should enter reason for rejection
    pls help...

    Hi Surya,
    SAP had provided you with a standard WF template for PR. You only have to activate it. The workflow template is WS20000077. In this what you have to do is, make all the tasks in this
    WF as a general task. For that go to each activity and double click on the task ID. Then from within the task go to menu Additional Data->Agent Assignment->Maintan. Then slect the task and press Attributes and select general task. This will ask for a customizing request. Do this for all task.
    The give event linkage by going to the Basic Data of the workflow and give binding. This will fulfill
    your requirement.
    Regards,
    Abijith

  • Standard n-step approval workflow for Purchase Order in sap 4.7?

    Hello friend,
                 In SAP 4.7 there is any standard template for  n-step approval workflow for Purchase Order.
    thanks in advance.

    Hi AM,
    there is no std template for n-step approvals but for Single Release.
    What you could do is create a custom one as per the number of approvals for PO.
    Also note a PO Release Strategy can handle only 8 levels of approval.
    Hope it helps.
    Aditya

  • Setting up Approval Process for Purchase Requsition and PO in SAP

    We are using SAP R/3 V 3.6, Doesn't have the work flow for PR or PO approval. PR is being done in SAP to process PO and approval request is being done seperatly though email system (outlook), which doesn't seem an efficient process rather it's a double work for people.....
    Can anybody advise if I want to set up the approval work flow for PR & PO what needs to be done, I know this can be done as I saw it in my other work places.......but not sure what it requires to set this up, any additional module or just configaration??
    Need a bit detail, how to proceed.........??
    Please advise..
    Thanks
    Maruf

    Create Classification for Workflow (Class Type 032):
    Class:            FRG_EBAN    Header release for P.req
    Characteristics:      WERKS     Plant
    GFWRT                          Total value of requisition for
    ESTKZ                           Creation indicator (purchase req)
    Class:          CEKKO2   Release Class for Outline Agreements
    Characteristics:     CEKKO-GNETW Total net order value
              CEKKO-BSART   Order type     
    Class:          FRG_EBAN2     
    Characteristics:     GFWRT     Total value of requisition for
    ESTKZ                          Creation indicator (purchase req)
    Class:          CEKKO   Release Purchasing Document
    Characteristics:     CEKKO-WERKS Plant
    CEKKO-GNETW                  Total net order value
    CEKKO-BSART                   Order type     
    Class:          CESSR   Release strategy for services
    Characteristics:     CESSR-LWERT Value of services
    CT01 u2013 Create Characteristic
    CL01 u2013 Create Class
    Once Classification and Characteristics have been set up need to do the following configuration:
    OMGQ - Release Strategy
    Grp     Strat     Description
    S1        R1       Release Level 1
    S1        R2       Release Level 2
    S1        R3       Release Level 3
    S1        R4       Release Level 4
    Double-click into each one
    example:  R1
    Fill out Values of Class FRG_EBAN2 - Object S1 R1
    Characteristics Description  / Value
        Total Value of requisition  / 0.01 - 2500.00 USD
        Creation Indicator (pur req) / work order
    Save and Transport u2026
    To actually Turn Workflow on involves sending an email to your Basis team with something like:
    Subject: Please Activate Workflow in Q40-101
    Please Activate Workflow in Q40-101
    Transaction SWU3, use password for RFC connection maintenance.
    Let me know how it goes.
    Nodes              SWU3                Automatic Workflow Customizing    
    Preceding node                         Utilities                         
    Preceding node                         SAP Business Workflow             
    Preceding node                         Development                       
    Preceding node                         ABAP Workbench                    
    Preceding node                         Tools                                                                               
    Nodes              SWU2                Workflow RFC monitor              
    Preceding node                         Utilities                         
    Preceding node                         SAP Business Workflow             
    Preceding node                         Development                       
    Preceding node                         ABAP Workbench                    
    Preceding node                         Tools  
    I hope this helps.......

  • None approval process for Purchasing Info Record

    Hi,
    Are there some approval process in SAP for Purchasing Info Record?
    Now, we use ME11 to creat Purchasing Info Record. And use ME12 to modify Purchasing Info Record. I feel it is very dangerous. Becase if someone make a mistake. Nobody know.
    If the price is lower than actual price, vendor must ask us modify it. If the price is higher than actual price, I am not very sure what will happen.
    So, we are seeking for an approval process in SAP system.
    Dan Yang

    >
    DanYang!@# wrote:
    > Hi,
    >
    > Are there some approval process in SAP for Purchasing Info Record?
    > Now, we use ME11 to creat Purchasing Info Record.
    And use ME12 to modify Purchasing Info Record. I feel it is very dangerous.
    Becase if someone make a mistake. Nobody know.
    >
    > If the price is lower than actual price, vendor must ask us modify it.
    If the price is higher than actual price, I am not very sure what will happen.
    >
    > So, we are seeking for an approval process in SAP system.
    >
    > Dan Yang
    There is no approval process in standard,Since it serves as master.
    Better provide authorization for ME11 & ME12 to restrict it.
    Raise quotation to maintain vendor prices.

Maybe you are looking for