PO release strategy status

Dear friends
is there any standard T code where i can get to know status of any PO pending for approval ie at which level this PO is waiting for approval
no me23n
Regards
Atul Ranjan

Dear friends
i am understanding what you are telling
first of all i dont want go for any report i.e no customized report
2ndly  in roles and authorization which i have created i have put tcode me29n for approving any po no use of me28 for approving purpose
so for that only i just want that these option i should hide if possible i.e release /cancel/(release +save) etc you can find this at header level in me28
any spro setting else we can use variant i guess 
Regards
atul

Similar Messages

  • PR Old Release Strategy - triggering NEW Release strategy any change OLD PR

    Dear Gurus,
    We have implement item level PR release strategy,
    characteristic used:  1. Document type, 2. PR item Value, 3. Material Group, 4. Change date & 5. Account Assignment Category.
    BEfore the above implementation, there is a OLD PR release Strategy existing in the system at one level release.
    Now the issue, the OLD release Strategy status is release completed, now the user goes and change the PURCHASING GROUP in old PR, new release gets triggered. How to Stop this, system should not trigger NEW STRATEGY,
    Please advice
    REgards
    RS

    HI,
    If i use date created as a characteristic, then Old release strategy get reset and the no release strategy will be trigger henceforth, the status of the PR will be INACTIVE.
    ANy charateristic we use, there will be only 2 options for old released PRs, 1) It will reset the strategy to new one or 2) the old strategy will be reset and make the PR status as INACTIVE.
    Is this is standard behaviour? pleae advice
    Regards
    RS

  • Release strategy's status

    Hi friends,
    I've created a new release strategy with new release codes.
    When I create a purchase requisition, the tab release strategy appears with the codes I've created.
    But, I cannot procede to release it via ME54N even if I got a SAP-All profile, the status still a yellow triangle...
    What's wrong with it ?
    Edited by: Bahia M. on Nov 25, 2009 11:48 AM

    Hi,
    Go to ME54N,
    Give the PR number and u will get release streatgy.
    and check for authorisation obeject in ur profile
    The authorization object Release Code and Release Group in Purchasing (M_BANF_FRG) determines which purchasing documents the user may release and which release codes he or she may use to do so. The authorization object
    M_EINK_FRG comprises the following fields:
    1 Release group
    You use the release group to determine which purchasing documents the user may release.
    Example 1:
    You have created different release groups for purchase orders for different plants (for example, release group 10 for PRs in plant 0001, release group 20 for PRs in plant 0002). Using the release group, you can now specify whether a user can release POs for plant 0001 only, or for both plant 0001 and plant 0002.
    Example 2:
    You have created the following release groups for different document categories: release group 01 for PRs; 02 for RFQs; and 03 for contracts. Using the release group, you can now specify whether the user can release RFQs onlyor PRs and contracts as well.
    2. Release code
    You use the release code to determine how the user may release purchasing documents.
    Example:
    The following values have been defined in the authorization object for the
    user Miller: release groups 01 and 02 (from example 2), and release code Z1.
    User Miller may thus release POs and RFQs using release code Z1.
    Hope Help U !
    Regards,
    Pardeep Malik

  • PR status as Active - after implementing Release Strategy

    Dear Gurus,
    We have implemented PR release Strategy and it work fine extacly, we are using material group as one of characteristic to trigger release strategy.
    if user or through MRP route, the Material group is not corrrect, the PR is created with Status as "ACTIVE" and PR can be processed for RFQ and PO. How to stop this, Please advice
    Thanks
    RS

    1- Create Rel Grp ZZ with description Strategy Error.
    2-Create Rel CodeZX with description Error .
    3-Create Rel Strategy ZF with description Forbidden Strategy.
    4-Maintain material group  characteristic in classification if it is blank then release status not released.

  • Old PR release strategy - release completed status change

    Dear Gurus,
    We have impletemented Item level release strategy for PR.
    There was old strategy exisitng only one level release, then we have implemented new release strategy which is multiple level release.
    Now the question, there are some PR are released completed for old strategy,. if we change the old PR with old strategy - which was release completed, the system triggeres new release strategy, which over writes the old strategy even though it was release completed status.
    Please advice
    Regards
    RS

    Hi,
    Check with T.Code OMGS (Define Release Strategy for Purchasing documents) , then go to release indicator --> then
    Check the value of Changeability of purchasing document during/after release  ( 1 - 6).
    Choose the appropriate value based on your req.
    Regards,
    Udayasankar Rajagopalan
    Edited by: Udayasankar.rajagopalan on Dec 9, 2009 1:07 PM

  • PO status if you change the release strategy procedure

    What will happen to the half released PO/PRS if we change the release strategy?

    Hi,
    It won't Happen for Half release PO Document. The rerelase will get affect once the final release done or No release initiated to the document.
    SAM

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

  • Issue with retriggering Release Strategy

    Hi all,
    We have a one off situation here. We had already 10 release staragies in our system. We added 2 more release strategies with a new characteristic. We updated the characteristic value only for the new 2 release strategues and did not update the rest 10. Although now we had updated the characteristic value for remaiining strategies, the purchase documents created in the mean tme is not subjected to release strategy. To ensure business control we need to retrigger back the release strategy for almost 1000's of documents.
    As any change to purcahsing document will retrigger it when done manually, but given the number of documents and as per Note 493900 we cannot trigger it by any backgoriund job to modify as below:
    16. Question :
    Why is there no release strategy determination when a program changes in
    background a purchasing document which corresponds to the classification of
    a release strategy ?
    Answer :
    This is the system design that a release strategy determination can only be
    triggered through a user action and not by changes made in background
    process.
    If you create a document (e.g. PO, Contract, etc), the determination of the
    release strategy takes place only in case of a user event like checking or
    saving the document.
    Kindly suggest any best practise to retrigger release strategy  for the missing documents to ensure business control. Any easy and time savig measure to get it resolved will be appreciated.
    Regards,
    Anand Sampath

    Hi Arnand,
    After investigation by searching customer messages database ,I found              
    other customer has  similar problem as the release strategy has changed           
    after creation of the SES please review the  explanation from developer           
    :(whose release code is 03 )                                                                               
    When you try to revoke the acceptance of the service entry sheets                 
    in ML81N or ML81, the 'Enter release code' pop  up window appears, but            
    entering the code that is determined via the menu path Goto -> Entry              
    Sheet -> Release Strategy (which is the 03), the SES remains the same.            
    Nothing changes. The status does not vary and no error or warning                 
    message is issued.                                                                               
    Checking the customizing for the release strategy, the release code               
    03 should have never been assigned to the SES 800024272 as the values             
    for the relevant characteristics were not included under that code.               
    I do not know how it was managed to accept the SES.                                                                               
    Now, when you try to revoke it, it seems that no release                          
    strategy can be determined, not even including the values RCARESANO               
    and 012 between the valid values for the characteristics of the release           
    code 03 (RCARESANO as valid value for SUPERVISOR_SERVICIOS                        
    (CESSR-ERNAM)and 012 as valid value for GRUPO_COMPRAS (CESSR-EKGRP)).                                                                               
    The only Possibility is to change now the SES so that the release                 
    strategy can be re-determined by the system.This is the Only possible             
    way that the system can  redetermine the Release Strategy , but it will           
    not be possible to do so as the SES is already accepted with the Old              
    strategy and it does not admit any further changes.                               
    To be able to change it you would need to revoke the SES first,                   
    but this Will also not be possible as the Release Strategy was changed            
    and the system still applies the old rules for determining the Release.           
    Solution to our Problem                                                                               
    The Only way to revoke the SES is to Restore back the Old Strategy that           
    was prior to 03 in the customizing.So now what will happen is that by             
    applying the Old Rules the System will be able to revoke the SES that#s           
    using the Old one. Once the necessary SES are revoked then go back to             
    customizing and apply the new strategy as it was did now, and                     
    Change the SES and save , the new value of the Release Strategy will get          
    updated in the table ESSR and the field frgsx will now have 03.                                                                               
    Problems associated if the Release strategy is changed                                                                               
    Actually the release strategy is not supposed to be changed when there     
    are some documents in the System that uses it and even if you change the   
    Strategy the Old records will not get AUTOMATICALLY UPDATED by the        
    system.The Release Strategy routine has to run again to update the         
    values. This is Possible by changing the document SES ,                    
    This change will happen only if the SES is not accepted and if its         
    accepted then you need to revoke and to revoke you need to restore the     
    old strategy , revoke and then change the SES , and have to go back to     
    customizing and Start using the New strategy from now on by doing so the   
    Routine will update the old record with the new strategy.                 
    b) You may want to use CEKKO-BADAT(Requisition Date) or any other
    structure in CEBAN or CEKKO and create a new release strategy    
    to differentiate the old release strategy.
    Hope this helps,
    Kind Regards,
    Matthew

  • Purchase order release strategy report

    Dear Gurus,
    We are using purchase order release strategy with classification.
    We have 3-4 level of release. We want to develop a report where we will come to know at which level purchase order is pending for release .
    How to get it ?
    Please provide ur help for the same
    Rgds,
    Saurabh

    Hi,
    Basically in EKKO table there is a field name FRGZU  -
        Release status based on that we can write a logic take the report.
    for example A1,B2,C3 ARE THREE release codes in that if A1 released means with check thable whether A1 released once it is release it will go to next release code it iwll check the status again inthe loop....
    Just tell him the logic to ABAP person they will develop
    Rehgards
    Murugan J

  • ME38 resets Release strategy of Scheduling agreement

    Hello,
    It seems when the users change the delivery date  in the delivery schedule (transaction ME38), the system in some cases resets the release strategy of the scheduling agreement from "Release" to "Not Release".It happened only in some case,release indicator set to "4" in our case.
    I cannot understand why this happens.
    Has anyone encountered such a problem before.
    Thanks
    Sunil

    Below are the (changed) item fields :
    Purchasing Document Item Change Date   AEDAT
    Item Delivery Date   EINDT
    Schedule Line is "Fixed  "FIXKZ
    Below are the (changed) header fields :
    Release Indicator: Purchasing Document  FRGKE
    Release status  FRGZU
    Purchasing document processing state PROCSTAT
    Item and header changes have same "Change document number " and transaction code "ME38" , this happened only in some cases,Rel Strategy is on  document type level ,I am also confused on this .
      Please assist  on this

  • Error while creating new release groups in PO release strategy

    Hi All
    I was creating a release procedure for PO and after completing steps, Create Characteristic and Create class & while creating new release grp with the class created i am not able to save it and the error message is (ME492) is" Only one release class should be used within the release groups for overall release...".
    But i am able to create from an already existing CLASS and able to proceed further.( Note: I am using the training module and in the learning stage.)
    Thanks for your support.
    Illan

    Dear,
    Please follow below mention path.
    *and check any things is missing, If you can go in bellow mention hints you cans create easily purchase release streatgy.*
    *- Follow below mention path.*
    *SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.*
    *Three steps involved in release process of purchase order.*
    **Edit Characteristic     Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP**
    **Edit Class     After creation of characteristic, create class for release purchase order. In which you can take reference of Class Type: - 032,Status: - Release,Class group: - Release strategy class,And put reference of your characteristic, which are created by you in first step.E.g: - Class - REL_PO**
    *Define Release Procedure of purchase order     In this step four processes involved.o     Release Groupso     Release Codeso     Release indicatoro     Release Strategies*
    Now see each steps of Define release procedure of purchase order in briefly: -
    Release Group     In which you can define release strategy groupExa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    Release code     In which you can define release code. Enter value as Release group: - 01,release code: -01 - Purchase Head,Release group: -01, release code: - 02 - Auditor
    Release indicator     In this step you have to define release indicator.Like X - Blocked, I - Under process, S - Release
    *Release Strategy     *This is the final step for release strategy.Assign release code 01, 02.Click on release prerequisites, select 02 - check box and click on continue.Click on release status button, enter release indicator X, I, S and click continueClick on classification button, enter values of purchasing group for which you want to created release strategy
    Than create purchase order for purchasing group, which you assign in classification of release strategy. Enter your values of purchase order and click on check button release strategy executed in your purchase order.
    Regards,
    Mahesh Wagh

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    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.
    e.g. 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.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and 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 (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    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
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    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,
    Ashok

  • Creation of release order possible during release strategy

    Hi folks,
    we have currently contract and purchase order release strategy parallel in place. Both are working fine.
    We are using quantity and value contracts.
    Quantity contracts are changed frequentely by the business; with every change (adding new items, changing prices of existing items), the release strategy is pulled again.
    Our release indicator is set to 6 and has value change 0,00%.
    The business requirement is now to release a contract with status X (e.g. 10 items and a total item value of 10.000EUR). After release, call offs can be created for all the released line items.
    If a new line item 11 is added, it should still be possible to create call offs for item 1-10 but not for item 11.
    Item 11 should undergo a new release.
    Has anyone ever come across such requirement?
    I have tried version management. However, version management will only force a new release whenever the version is completed.
    Even then, the complete contract is subject to release strategy and it is not possible to create call offs.
    We dont want to set error message ME347 "Release orders against contract xxxx not possible (contract not released)" to warning, as this will allow to always create call offs regardless of the contract  being released or not.
    Any ideas greately appreciated.
    Thanks!!

    I suppose program checks in EKKO whether contract is released,, irrespective of version exist it or not. IF you are able to direct it to EREV, then may be version 0  or ( current  - 1 ) released can be returned.
    Isn't it a special case that your version 0 data is intact in version 1; Even if someone change lines 1 to 10 , with or without adding line 11, it still triggers version 1. How do you ensure that lines up to 10 are not changed. you may have to look in CDPOS CDHDR with object Revision..
    This is  just an idea which you may discuss with your developer to see whether a copy of the program can be modified..

  • Release strategy problem in Purchase order

    Hi Guys,
    I was trying to configure Release strategy for the purchase order and this button   is not triggering in my purchase order.
    I dont know where I was doing wrong and  where might be the problem  as I tried several times.
    Can someone give me some good idea about it  how to configure in a proper way.
    If you need any further information please let me know.
    Thanks
    Krishna

    Hi
    I hope you followed the following steps:
    1. Create Characteristic using CT04
    2. Create a class and link to the characteristic using CL02( class type: 32)
    3. Configuration of release procedure
        SPRO IMG->MM-> Purchasing -> PO -> Release Procedure -> Set up procedure
        A) Create release group and link to class
        B) Create release code
        C) Set up the release indicator
        D) Set up Release Strategies-> strategy and codes
        E) Set up Release Strategies -> pre requisites
        F) Set up Release Strategies -> status
        G) Set up Release Strategies -> values for strategy
    Regards,
    Subhashini

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

Maybe you are looking for