SES Release Strategy

Hi,
Need to configure release strategy for SES unfortunately SPRO setting for the configuration are closed on live client.
How can i get the client open, Do i need knowledge of specific objects?
Alternatively can i configure and transport the release strategy from a dev. client where SPRO is open ?
Any help would be appreciated

HI,
Make use of this path
SPRO-> IMG-> Materials Management-> External Services Management-> Define Release Procedure for Service Entry Sheet
You are not allowed to touch the configuration part in the production client. for that matter nobody will have.
what you have to do is that you have to config in the development and create a transfer request and then transfer this request to the Quality test the release process if everything is proper then transfer the request to production from development with proper approval
Thanks & regards,
Kiran

Similar Messages

  • SES Release Strategy not invoked in Backend from SRM confirmation posting

    Hi,
    I have configured a SES release strategy based on vendor number in R/3. When a SES is created in R/3 via ML81N the release strategy is invoked as expected. However, when a confirmation is entered in SRM for that vendor, the SES that is created in the backend system is created in accepted status and the release strategy is not invoked.
    Can anyone advise how to get this to work the same way as ML81N?
    I would expect that the SES would be created in the backend from the confirmation without acceptance and the release procedure to be the same as ML81N.
    thanks,
    Michelle.

    Hi,
    The SRM confirmation in EBP is the goods receipt(MIGO) and not the service entry sheet entry (ML81N) as we do in Materials management.
    As per my understanding there is no provision of service entry sheet entry in SRM 5.0 as of now  and SRM 7.0 has this option coming up :
    In SRM 7.0 ,
    "Supplier-maintained confirmation (service entry sheet) for services performed based on the service items within a purchase order
    Confirmation supporting hierarchical structure of service items"
    are added.
    Look for this information in the thread which speaks about SRM 7.0
    Re: Benefits of upgrading to SAP SRM 2007
    which gives the info in slide 11, Delta SRM 7.0, Service procurement -2
    Best regards,
    Sridhar.

  • SES release strategy being incorrectly triggered

    Dear All,
    We have maintained release strategy for Service Entry Sheet. In the SES release strategy class only the following characteristic is maintain
    a. Name of the person who creates the Service entry sheet
    In the release strategy only 'a', 'b' and 'c' users are maintained in the above characteristic. But in the system even if a user f creates the service entry sheet the system applied the release strategy on it too and asks for release code. The system should only ask for release code if a,b or c user creates SES.
    Thank you!

    Hi There
    Just a guess,,
    In CT04- for Name of Person who Created the SES (ERNAM)- in the values tab-
    Check the indicator-Additional Values is eanbled or not,, if enable remove it and try
    Thanks
    Senthil

  • Release strategy for PO and Service Entry Sheet

    Hi
    I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
    should I maintain the same characteristics for service entry sheet ?
    the approval will be the same for both

    Hi,
    The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
    Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
    Note: The release strategy must be based on the structure CESSR.
    The PO release strategy is based on the structure CEKKO.
    For the SEs release strategy you must create a different class.
    Regards,
    Edit

  • Release strategy tab is not coming in SES

    Hi All,
    I am facing a issue where I have created an SES, and release strategy is assigned to this SES. Problem is somehow the user is not able to see the release tab when he go wants to release the SES. The release tab is missing from the SES.
      Am sure somebody has faced this kind of issue and have any idea how to correct this.
    Thanks

    Hi,
    The direct reason that there is no release icon available in ML81N           
    is inconsistency in the field ESSR-FRGRL for affected SES's.                                                                               
    This field should be filled with 'X' as all those SES are subject            
    for release.                                                                               
    Have you changed customizing for involved release strategy recently ?        
    If a relase strategy is created with a certain name and documents are          
    created with respect to it afterwards, this release strategy should be         
    changed then IF AND ONLY IF a NEW name is assigned to it as well. In           
    other words, if such a strategy is already use, it should be RENAMED           
    before applying the desired changes.                                                                               
    Otherwise you will run into the observed inconsistencies when trying to        
    edit documents which were created BEFORE the strategy was changed              
    (since the system at some point always checks the NAME of the strategy         
    to be changed, NOT the content).                                                                               
    So if this case happens only for already created SES a good solution           
    for it is to delete affected SES and create a new one with changed             
    release strategy.                                                              
    I would delete affected SES and create it again.           
    It seems to be the fastest way to resolve this issue.      
    If you need a correction for this inconsistency issue, please open a SAP ticket for your problem.
    Regards,
    Edit

  • 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

  • User names of service entry sheet release strategy

    Dear Expert ,
    Kindly guide from which table could I get the user names values who done the release strategy for service entry sheet for example I have 3-release codes : 1. Creator
                            2. Verifier
                            3. Approver
    So I need to know who has done these 3-actions for respective service entry .
    Best Regards

    Hi,
    The information about the Person who has relesed the  entry sheet will be not stored in the change document for the entry sheet.          
    There is only the information about which release code has released the SES. In an organization a certain user or a group of   users can use the very same release code.
    However, if you have also configured a workflow with this release strategy, then it is possible to know who has                 
    released the SES.
    You will need to create you own report which reads the change history (CDHDR and CDPOS) and finds out the date when the last release code of  the release strategy has been released and to find out based on this data who was the approver.        
    Regards,
    Edit

  • Multiple release of Service Entry sheet in ML85 with a release Strategy

    Hello Techies,
    We have requirement where in we need to each release service entry sheet created in each month.
    We have created a release strategy and now using ML85 for releasing SES instead of ML81N.
    Is there any process so that all the SES are released at once(Mass release) .
    Thanks
    Jayashree

    Hi Dear,
    you select the SES as per your Release code and Code Grp, henceofrth the no of service entry sheets will be  display you can choose the multiple Entry sheets and select the green flag w/o coming to the same T-Code again and again.
    Hope it will help you.
    Regards,
    Yawar Khan

  • Service entry sheet Release strategy Error

    Hi Guys
    I have one scenario where Iam not able to post Service enrty sheet
    We have release strategies A1,A2,A3,A4,A5
    Some service entry sheets are there in the system with each release strategy
    We have deleted A2,A3,A4,A5 and A1 remains there
    While release the service entry sheets which are having Release strategies A2,A3,A4,A5
    We are facing problems not able to release
    please provide any solution to this error ,
    It is not possible to restore previous release strategies A2,A3,A4,A5
    We need to change release strtegy A2,A3,A4,A5 to A1 for existing service entry sheets
    Please suggest solution.
    Thanks in Advance
    SAP MM

    Hi,
    You are created release strategies A1, A2, A3, A4 & A5 and now deleted A2, A3, A4, A5 but A1 remains there in the system.
    You could have take precaution ieu2026u2026all SES should be released 1st and then deleted youu2019re release strategies A2, A3, A4 and A5.
    For quick solution------ >As now deleted A2, A3, A4, A5 and you want to triggers A1 only for all already created service entry sheet(SES) , then just go to all created SES, do some changes( like change quantity and then retrieve the original quantity in SES) by editing SES and see how re- triggers release strategy A1.{ 1st do it for one SES(as SES number created, you will have same SES number after changes in SES) and try  for all SES}
    Regards,
    Biju K

  • Service Entry Sheet Release Strategy

    Dear Friends,
    We are re-configuring Service entry sheet release strategy. My client wants 4 level release strategy like ,
    Level 1 (0-10 lacks )
    Level 2 ( 0-50lacks)
    Level 3 (0-100 lacks )
    Level 4 (> 100 lacks )
    I have created release group, with release object3.
    I have created 4 release codes and 4 release strategies.
    We have so many departments like commerciual, safety, HR, Projects.
    My client wants only 4 codes to be created. My problem is that, how each and every department’s HOD can release SES ? How I can control SES of his department to be released by him ?
    Please help.
    With Best Regards,
    Rajesh

    Hi,
    I've configured release strategy department wise(HOD's)
    For that you need to create new characteristic for Tracking number.
    You can enter tracking no such as HR,PRD, PUR etc.
    Now maintain these tracking no in classification.
    Release will work as per respective HODs.
    Seems bit lengthy but I found it very useful.
    Try it.
    Regards,
    Piyush

  • Release Strategy Question

    Hi,
    Can anyone explain me with example, why is it that we can have only one class and not more, when configuring groups in the release strategy.
    Why is it mandatory to have only one class for overall and one class for line item release, can someone explain with examples.
    The system allows creation of multiple groups, but all have to use the same Class when it comes to overall release/ Line item release.
    I am not able to understand the reason behind this restriction as of now, can someone share some insights.
    Thanks
    Shailesh

    Hi,
    Better & always keep one release class ....ie.......one release class for PR, one release class for PO, one release class for Contract & one release class for SES.Under each separate class keep your requires characteristics.Then do necessary confuguration for release statergy.
    For more check the links:
    /people/arminda.jack/blog/2009/03/12/mm--check-list-to-detect-and-solve-release-strategy-issues
    Re: Class and release group and code in release strategy??
    Regards,
    Biju K

  • PR Release Strategy tab processor field is not getting displayed

    Hi Experts,
    While creating Purchase Requisition, In the Release Strategy tab processor field is not getting displayed which should be showing the name of the user id which has been configured in the SPRO.
    SPRO--> Rel Proc for PR > Rel Group> Rel Code--> Object type (US) and --> Agent (User id who has to approve the PR).
    release strategy - Release code  -work flow 1
    That processer name is not displaying
    Thanks
    chandoo

    This is the workflow forum.

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

  • Release strategy for PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • PO Changeability / Release Strategy / BAPI_PO_RELEASE Issue

    Hello everyone,
    I've run into an interesting problem:
    We have defined several PO release strategies.  Most of these work in the traditional manner, requiring manual approval by a given user.  One release strategy, "99," gets picked up by a batch job and released automatically using BAPI_PO_RELEASE. Either way, the release indicator for all released PO's is set to "R." This all works as intended.
    We have maintained Changeability settings for each release indicator in customizing. "R" is set to "4 - Changeable, new release in case of new strat. or val. change," with a percent value change tolerance of 10%.
    If we make a change to a manually released PO that exceeds the threshold set in customizing, the release procedure starts over as intended.
    If we make a change exceeding the threshold to a PO that was released automatically by BAPI_PO_RELEASE, the release procedure does not start over, and the PO remains unblocked.
    What would cause this discrepancy?  The two records look virtually identical in EKKO, particularly in respect to the fields relevant to release.
    Thank you ahead of time for your help.
    -Jarrod

    Configuration issue/user error.

Maybe you are looking for