Release strategy for Purchase order

Hi Friends,
My client was using Release strategy for purchase order. Now we want to know the T-code for showing list of Rejected Purchase orders,  T-code for for showing list of approved purchase orders, T-code for showing list of blocked purchase order.
Thanks and regards
Krishna

HI,
You can go to SE16N view table name EKKO
FRGKE   Release ind.  = B 
FRGZU   Release status = <blank> 
mean, this PO yet to approve/ rejected.
FRGKE   Release ind.  = R
FRGZU   Release status = X
means, this PO has been approved.
Hope this helps

Similar Messages

  • Release strategy of Purchase order

    Dear all,
       I configured Release strategy for purchase order in which i create characteristic,Class.
       I also define release procedure for PO like release group,release code,release indicator & release strategy.
       But it is not reflecting in Purchase order.
    Regards,
    Nitin Patil.

    Hi Nitin,.
    check had you missed any step while creating the release procedure...
    Follow the link it may be useful to you, this is for PR.... this is same for PO also onle differnce is in coummunicaitton structure CEKKO you neet put...
    http://www.sap123.com/showthread.php?t=59&highlight=SettingsimpleReleaseProcedurePurchase+Requisitions
    regards
    anand

  • Release Strategy in Purchase Order

    Hi,
    Can any explain the usage of Release Strategy in Purchase Order.
    ganesh

    Hi Ganesh,
    Release strategy works the same way in purchasing documents (i.e. PR and PO). It is a form of control that company use to control the purchases made.
    In your scenario, a PO release strategy is used to control the PO release status for Good Receipt process. Once the PR is released by the relevant releaser, you will see that the PR is now unblocked for issuance of PO.
    Once the PO is issued with reference to the PR, it is now blocked again by a release strategy for user to perform Goods Issue. The releaser will evaluate the PO issued and determine if it is necessary to be released for GR / Service Acceptance process. At this stage, the releaser can still reject the PO although issued, and hence GR / Service Acceptance is not able to be performed. Different value will trigger different set of release strategy with different level of approvals, depending on how the PO release strategy is configured by the MM functional consultant. Usually, the PO release strategy has a flatter approving level as compared to PR release strategy, reason being that once the PR has been fully released by all releaser and the PO issued, usually the purchase is deemed necessary and PO releaser would usually consider to release the PO for GR  or Service Acceptance process, unless there is discrepancy or sudden change in decision of Management.
    Hence, all in all, the PO release strategy act as another form of control to the company to restrict the release of PO for GR or Service Acceptance.
    Hope this will give u a better understanding on the function of a PO release strategy.
    Rgds.

  • Wrong Release strategy in purchase order

    Hi,
    I have a specific purchase order with wrong release strategy.
    I had been creating others documents with the same total value and the release strategy work correctly.
    The release strategy configuration are right.
    How I can correct the release strategy in a specific document?
    Thanks.
    Best Regards.

    Hi,
    The release strtegy is basically conssitss of Different type of characters.
    What characters you are highlighting plays in release strategy.
    First you comapre the characters you mentioned in two purchase orders,
    eg: p.org, Pur Grp, Value,------
    o to bith release strategies and compre the things or characters you mentioned Release strategy and found wher you missed to get the required Strategy.
    SPRO>>MM>>Purchase order>>Release Procedure for Purchase Orders>>Define Release Procedure for Purchase Orders>>Click on release strategies
    Select your release strategy and go to Classification , here you chck the parameters in both release strategies and compare with your purchase orders.
    Regards,
    Andra.

  • Release Procudure for Purchase Order

    Hi Experts,
    I am new Release Procudure.My client wants release procedure for two users.
    End user wants create Purchase Order then other user wants release that purchase order and then another user wants final release. Please tell how can map this process in sap.
    Thanks in advance,
    Chandhu
    Edited by: chnadu9 on Jan 5, 2011 5:48 AM

    Hi,
    The release code is a two character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    An example of configuring a Purchase Order Release Strategy
    If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    Steps for configuring the PO release strategy
    Create the PO Characteristic
    Transaction code : CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data tabstrips
    Table name CEKKO Field name GNETW and press enter and you will see this information message :-
    Format data taken from Data Dictionary (press enter)
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data tabsritps (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >=10000 (equal or greater than 10000) and press enter
    Save your data
    Create the Class of the PO Release Strategy
    Transaction code : CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create button
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tabstrips, type NETVALUE to assign your characteristics to the class
    Save your data and this message will appear :-
    Class type 032: Class REL_PUR created
    Define the Release Procedure
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Save your entries.
    Release codes - New entries
    Grp Code
    02 01
    Save your entries.
    Release indicators - New entries
    Release indicators Release Description
    0 Blocked
    1 X Release
    Save your entries
    Release Strategy - New entries
    Release group 02
    Rel.strategy 01 - Release
    Release codes 01
    Release status 0 - Blocked
    1 - Release
    Click the Release prerequisities button
    Click the Relase statuses button the click the Continue button
    Click the Classification button
    Choose your check values
    Click the Back button
    Save your entries
    Check your PO release configuration
    Finally, check your PO Release Strategy configuration to make sure that there are no errors.
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Mohar

  • T.Code for Release Procedure for Purchase Order Type

    Hi Frd
    im working in ECC 6.0.
    OMGS is t.code for Release Procedure for Purchase Order Type in SAP 4.6.
    Can anyone tell me what is the t.code for Release Procedure for Purchase Order Type in ECC 6.0 .the OMGS t.code is not working in ECC.
    Thanks
    By
    Pari

    Hi Rajasekharan,
        Go to tcode ME22 and enter the Purchase order number.
    inside the Display screen,u can see a GREEN flag button on the Application Toolbar.
        Click on a item and press the Green Button.
    U will see the release code,provided the Purchase order is set to release strategy,after that Go to tocde ME28 enter the release code ,along with Document number and then release the Purchase order.
    Actually the tcode for releasing purchase order is ME28
    Reward points if useful.
    Cheers,
    Swamy Kunche

  • Define Release Procedure for Purchase Orders

    Hi Friends,
    We are changing Release procedure for purchase orders for one department from > $ 5000 to > $ 10000.
    We defined three characteristics for the class namely Purchasing Order Document, Purchasing Order Type and Ner Order Value which is Currency data type. I Defined Release Procedure for Purchase Orders in configuration master. It's working fine, I mean the Net order Value field is updated in Configuration Client.
    After transporting the above change to the Testing Client, the Net Order Value field did not update in testing Client even though I created Characteristics in Testing Client (as characters are not transportable, I created them seperately in Testing Client). I can't update the Net Order Value manually in Testing Client as it says "Client 010 (test) has status 'not modifiable' "
    Please tell me how to update that field, as the net order value didn't change even after transport. I can't change manually in testing Client as the status is "not modifiable"

    Hi,
    Yes I have already done that.
    In SPRO,
    After hitting the following:-
    MM --> Purchasing --> Purchase Order --> Release Procedure for Purchase Orders --> Define Release procedre for Purchase Orders
    I have to process the objects in the following sequence,
    Release Group, Release Code, Release Indicator, Release Strategy & Workflow.
    Upto Release Indicator it is fine. After hitting Release Strategy, I should select the release strategy (which I just created) and display. Then 4 buttons will be displayed namely,
    Release Prerequisites, Release statuses, Classification, Release simulation.
    Upto Release statuses it's fine. Afeter hitting Classification,
    the values of Purchase document & Order type are populated, but the Total Net Order Value is Blank. It is supposed to populate the amount & 10,000. But it is not.
    Actually that amount will be stored in the field GNETW of table CEKKO. But CEKKO is a Structure not a table. So I can't update the field.
    Please advice me...
    Thank You,
    Nag

  • 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

  • Is it possible to have release strategy for sales order?

    Is it possible to have release strategy for sales order?

    hi
    as per SAP standard there can not be any release strategy for sales order but if u want to control u can use authorization profile for this purpose.
    povide authoriztion to the required persons only..
    regards
    CMM

  • Release procedure for Purchase orders

    Hello SAP Gurus,
    Can anyone explain in steps the release procedure for purchase orders and also can any one explain how it differs from Puchase requisition release procedure.
    Thanks
    NDS

    Hi
    Release procedure for Purchase orders here is process flow.
    Go to spro>img>materials management>purchassing>Release procedure for Purchase orders
    1. Create characterstics  -Intially you will create characterstics based on which you would like to release a purchase order.
    Charactrestics are like plant, purchase order value,purchase group etc.. Assign characterstics to release class 032.
    2. Create Release group say 01 and create release codes like pm(project manager), gm(general manager) etcc..
    3.  Create a Release starategy say s1 and assign release group to it 01 and release class 032 and department to whom this release stategy applies say MM. define the order of release say first pm followed by gm etc..
    4.  under classfication define value limits for release of purchase order.
    5. define release indicators
    6. simulate the release
    7. assign if there is any workflow.
    hope it helps.

  • Release Strategy for Sales Order-IMP

    Hi Gurus,
    I want to know regarding <b>Release Strategy for sales orders</b>. I want to know the detailed step-wise procedure for SO and not for PO. My understanding is that standard SAP does not support Release Strategy for SO in SD Module. Please l want the following queries to be answered
    1) Is my understanding on Release Strategy for SO correct as mentioned above?
    2) What are the other alternatives and the steps of configuration step-wise.?
    Kindly help me post this information as it is required urgently. Suitable full Reward Points will be given to all answers.
    Many Thanks,
    Pankaj Mishra
    E-Mail : [email protected]

    Pankaj,
    There is no release strategy for sales order.
    You can try it doing Authorisation /Status  profile with your BASIS person...
    REWARD IF U FINDS THIS AS USEFUL...
    Regds
    MM

  • Steps for deleting release stretagy for Purchase Order

    Hi,
    Could you please help in deleting / cancelling the exisiting PO release stretagy? I need to create new release stretagy which is totally different from the existing one.
    What are the steps in cancelling existing release strategy.
    Can the same steps be used for cancelling release stretagy for Purchase Requistion?
    Thanks.
    Anand

    Hi,
      you goto
    spro> mm>purchasing> purchase order> release procedure
    there you go to to release strategy
    then follow following steps.
    1.delete release strategy
    2.delete release codes
    3.delete release groups
    then to create new release strategy and  follow following steps
    1 create characteristics ( use table cekko)
    2 create class( class type 032)
    3 . create release group and assign class to it.
    4 create release codes
    5 then create release strategy using  release group and release code.
    hope this will solve your problem
    Regards,
    Vijay

  • Two release stratergies for Purchase Order

    Hello Experts
       Our organization have 2 different company codes. My question is whether I can configured 2 different release stratergies for different company code for same object Purchase Order?
    Thanks
    Ankit

    Hi,
    You can only use (assign) one class for your client level , but what you can surely do is that based on release group you can differentiate and trigger separate release strategy 
    For example
    Release Group .....Class...............description
    ..........C1............... zclass_po ......C.code1 release
    ..........C2............... zclass_po ......C.code2 release
    Now based on this group you can differentiate and trigger separate release strategy (As both release code and release strategy is defined at release group level )
    Edited by: redriver on Feb 18, 2012 8:01 AM

  • Release stratedires for Purchase Order

    Hi
    Dear All
    I need a clarification that my needs cost centre based release strategy for Po, but t is not in Cekko table.i have to use customer exit M06E0004 or any other way to use cost centre as char in release st.
    i appreciare if anybody can help/ give the suggestion in this regard
    MVRAo

    Hi,
    Which Documents Can be Released (Approved)?
    Release procedures can be defined for the following documents:
    <b>Purchase Requisition</b></b>
    The external purchasing documents purchase order (PO), contract, scheduling agreement,request for quotation (RFQ), and service entry sheet</b>
    Release Procedure for Purchase Requisitions
    Two different procedures are available for requisitions:
      <b>With classification</b>
    With this procedure, requisitions can be released both at item level (i.e. item-by-item)and in total. The latter approach is also termed „overall release“.
    <b> Without classification</b>
    With this procedure, requisitions can only be released at item level.
    The two procedures are mutually exclusive (that is to say, you must decide in favor
    of one of them only - you cannot use both).
    Release Procedure for External Purchasing Documents
    External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
    Procedure Without Classification (Requisition Items Only)
    The conditions can be based on one of the following item characteristics or a combination of
    these:
    <b> Account assignment category
      Material group
      Plant
      Total value</b>
    Hope this will answer your question
    Thanks
    Arun agrawal.

  • Release strategy for purchase requization on basis of document type

    Hi All
    can somebody can explain me the procedure for creating releasing strategy on basis of doc type
    Nabil

    Hi,
    The below link will help you to understand the process.
    Please open the below link and u will get the complete process to have the Release stretegy on the basis of Doc. Type.
    http://www.sap-img.com/materials/release-procedure-for-purchase-requisitions.htm

Maybe you are looking for

  • How do I transfer all information from an old ipod to a new ipod

    I need to transfer all my data from an old ipod to a new ipod.  How do I do that?

  • Forms upgrade 4.5 to 6i

    Hi, Im in the process of upgrading forms from 4.5 to 6i. Is there any documentation supporting this process? Thanks, Matias

  • Number of times a Query is Run

    Hi Experts, I would like to find out: 1. what are the query names that are on my infocube(s) have been used most? 2. how many times each of these queires have run? 3. who are the users who ran these queries? 4. When was the last time each of these qu

  • Screen Goes Dark when No files Are Open

    Hi, Since I installed the CS 6, I seem to have a problem with my display going dark whenever Illustrator CS 6 doesn't have opened files, i.e., the application runs, no files are open, and my whole screen's brigthness goes down. It only happens with I

  • Lots of Warning 1706 logged on VMM 2008 R2 Sp1

    Hi, I have VMM 2008 R2 Sp1 server with 3 Hyper-V hosts connected. In VM Manager event log I have noticed lots of 1706 warnings: "Job <Id> (Refresh virtual machine) failed to complete". Is it anything dangerous for my servers? Should I troubleshoot it