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.

Similar Messages

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

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

  • BADI: Release strategy to Purchase Order

    Hello gurús,
    Do you know some enhancement or BADI that I can use to reset the release strategy in the purchase order?
    The transaction where I need this is ME22N.
    Thanks for your time and support.
    Regards,
    Sandra Palomo

    Hello Sandra
    Have you had a look at BAdI ME_PROCESS_REQ_CUST? Perhaps you find a method there which matches your requirements.
    Regards
      Uwe

  • Relation between Version and Release Strategy at Purchase Order level

    Our requirement is as follows:-
    Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
    now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
    Price-A can be equal to Price- B, Less than or greated than.
    I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
    Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
    and when i delete the version condition, we can see the release strategy tab in the PO.
    Thanks in advance,
    Vikas Rander.

    Our requirement is as follows:-
    Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
    now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
    Price-A can be equal to Price- B, Less than or greated than.
    I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
    Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
    and when i delete the version condition, we can see the release strategy tab in the PO.
    Thanks in advance,
    Vikas Rander.

  • Deputy on Release strategy of Purchase Order

    Hi,
    We had the following below release strategy to configure
    For value greater then 5000 the approvers will be
    At First Level  approver(User) A1 or his deputy (User) Approver A2
    At second level Approvers(User) will be A3 or his deputy  A4
    At third level Approver (User) will be A5 or his deputy  A6.
    Can we customize this type of PO release startegy. I had seen and found that we cannot have approvers as deputy in release startegy, correct me if I am wrong.
    I thought to configure in below way
    At First Level let the Approver Release code be X1
    At Second Level let the Approver Release code be X3
    At third Level let the Approver Release code be X5
    Assign these Release codes to the Approvers user id as well as to there deputy
    For e.g. if for first level the approver (user is ) A1 and its deputy (user) A2 then assign this Release code to both of them so that either of them can release the PO.
    Is there any other way to configure this scenario.
    Also one more thing the approver(User) A1 can also create the PO. So when he create the PO then the approver should not be he himself it should be new approvers that is
    At first Level approver(User) A7 or his deputy Approver A2
    At second level Approvers will be A3 or his deputy  A4
    At third level Approver will be A5 or his deputy  A6.
    Please suggest you valuable inputs on this.
    Thanks
    Shashi

    The scenario you have explained is possible with alternative release procedure where you can set the release prerequisit based on your reqs but the second scenario you have explained which required workflow functionality with org management than only you can have
    so if you are planning to use the workflow than use th user eixt M06E0005
    to identify the role and level.

  • Release Strategy in purchase order document type

    Hi Gurus..
    I'm tring to tweak the single RS in the system.
    I've set the charcteristic using table CEKKO field BSART, restriction 032, I've set two document types as the Characteristic Value (ZLOG - ZADM). Then I´ve set the class with this characteristic, Created Release Groups & linked to class , Created Release Codes, Release Indicator, and Set up strategies
    .. but  It doesn´t pick any release strategy.
    The funny thing is if I delete the document types values entered in CL20N it works for all doc typs, but if I set the docs types that it should take to pick the RS it doesn't work at all...
    Please advice..

    I´m not such a abapper but I guess there is not values taken to ekko, does it ring a bell?
                                            BUKRS                                       
                                            BSTYP                                       
                                            BSART                                       
                                            BSAKZ                                       
                                            LIFNR                                       
                                            SPRAS                                       
                                            EKORG                                       
                                            EKGRP                                       
                                            WAERS                                       
                                            BEDAT                                             00000000
                                            LLIEF                                       
                                            KUNNR                                       
                                            RESWK                                       
                                            LBLIF                                       
                                            INCO1                                       
                                            KTWRT                                             0.00
                                            LIFRE                                       
                                            WERKS                                       
                                            MATKL                                       
                                            LTSNR                                       
                                            USRC1                                       
                                            USRC2                                       
                                            USRN1                                             0000000000
                                            USRN2                                             0000000000
                                            GNETW                                             0.00
                                            SUBMI                                       
                                            MEMORY                                       
                                            KONNR                                       
                                            REVNO                                       
                                            PDUMMY                                       
                                            KDATB                                             00000000
                                            KDATE                                             00000000
                                            EBELN

  • 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

  • Release strategy in sales order is required before MRP run

    Hi Experts,
    My requirement is Release strategy in sales order is required before MRP run. My client is doing the following process:
    1) Creation of Sale order (MTO).  Ex: User creates 10 sale orders per day.
    2) MD04- Stock Requirement List. All 10 Sale orders should be displayed. So no problem here.
    3) MD50-Make to order-Planning . Here when user gives the sale order number and sale order item and press enter, then only the released sale orders should be allowed and the rest sale orders it should throw a error message and it should not allow to process further.
    How this situation can be addressed in SAP.
    Kindly post some hints and comments.
    Regards,
    Kiran.

    Hi Kiran,
    Define and Assign status profile BS02 at sales order detail (line item) lets say with create and release status
    SD>Sales>Sales documents>Define and assign status profile
    Have create status as default while creating SO with item
    And do a user exit change for MD50 with ABAP consultant help and release it when user keys in SO and item.
    For other line item I believe it will give an error
    Pls try and update if it solves your requirment
    Regards,
    Siva

  • Wat is the procedure to make a release strategy in sales order ?

    wat is the procedure to make a release strategy in sales order ?

    Dear all:
      my request is :
      when the sales order are saved(VA01) and it  is not   approved ,it can't make to MD04,
    if the sales order is approved,then can make to MD04.
    I user Status Profile  to do it,
    I  have set a user Status Profile in sales order header and item by BS02, in the user Status Profile i have two status  A00 and B00,I need a business transaction  to set in the status A00 ,
    but i don't know which business transaction can settle my problem.
    Acct. assignment order/project
    Activate final billing doc.
    Actual activity allocation
    Actual overhead (periodic)
    Actual settlement
    Automat. WIP/results analysis
    Change configuration data
    Complete
    Confirm order
    Create billing document
    Create changeable copy
    Create delivery
    Create inquiry
    Create quotation
    Create sales document

  • 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

Maybe you are looking for

  • Whats the difference between a combo update and using software update?

    I keep my Macbook up to date by checking regularly via software update, so far with no mishaps, but I have seen people on these forums mentioning that a it is better to download the combo updates direct from Apples website. Is this true, if so why, a

  • ITunes 10.6.3 freezes/spinning wheel when I click the 'book' tab for the ipad. HELP!

    Hey all, Tried searching the net but cannot find a suitable solution to my problem This problem occurs every now and then, but this time I can't fix it. When I connect my ipad to my Macbook (2.2 Ghz Intel Core 2 Duo 2009 running OS 10.5.8) and I try

  • G4 450 AGP to Radeon 9800 Pro upgrade low down.

    I have been looking to upgrade my G4 450 AGP graphics card. I'm running 2-22" ViewSonic 2235's at 1680x 1050 w/ Rage 128 AGP and PCI cards. I've learned that this G4 has 2x AGP slot and few cards fit, namely ATI's Radeon X800 XT or Radeon 9800 Pro, b

  • Smart Objects mis-behaving in Photoshop 5.1?

    Hi there I'm using Pshop 5.1 on Win 7 64bit Cince Adobe introduced Smart Objects in CS2 (I think it was CS2 - I jumped from 7) they've becom I standard part of my workflow that I use all the time However, having upgraded from CS4 to the latest, smart

  • Best practice for adding images to a RH8 HTML project?

    I'm working on a Word to RH8 HTML conversion. The images in Word are SNAG images but the resolution is poor and some of the images may need to be recreated from scratch again. Going forward I imagine I should work on getting them right in Snagit9. An