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

Similar Messages

  • PO release strategy is not triggering if Quantity pre.Qty

    Standard SAP design will trigger the 'PO release strategy' if Total net order value (GNETW) is more than set. Lets take if PO created with Qty 100 and Price 50 then first time 'PO release strategy' is triggering when you save the PO. Next time when you change Qty less than the previous value like 80 from 100 then 'PO release strategy' is not triggering but if you enter more than previous value as 120 then its triggering. Ofcourse it makes sense but our user wants to trigger if any changes happened to QTY or PRICE. Is there anyway to trigger?
    Found user exit - EXIT_SAPLEBND_002 but not sure what needs to be changed. Can one let me know the solution, if you have any.

    Hi.
    According to  note 493900, question 4, release strategy is reset only
    for some specific case. Alternatively, please question 5 from this note
    release strategy might be redetermined. However in order to determine a
    new release strategy the field that is changed in PO must be included
    as one of the fields in the strategy. Thus there is no standard way
    for resetting/redermining release strategy for a change of e.g. text
    on header or item level.
    Please also kindly refer to other 2 useful notes for this area:
    662993     Resetting an already occurred release
    365604     FAQ: Release strategies in purchasing
    BR
    Nadia Orlandi

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

  • Release strategy not getting triggered.

    Hello,
    As per the client request, new Purchase group had to be added to the existing release strategy.
    I had added the purchase group in the edit characteristics and in the release strategies: classification.
    But now the the release strategy is not getting triggerred.
    In CL20n I see that the, status is marked 3 i.e incomplete. The reason to this is not known as customizing done is correct.
    In OMGSCK i see that no errors are found with the release strategy.
    Please suggest.
    Regards,
    Neetha

    hi,
    Sometimes the strategies are taken after restarting the sap system...there has been one same situation before also..at that time the same strategy started working after restarting the sap system...
    pls check it may be the same issue with you also..
    Regards
    Priyanka.P

  • 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

  • PO Release Strategy not triggerred for particular Total Net Order Value

    Dear,
    I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
    For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
    All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
    But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
    Please suggest for solution.
    Thank you.
    Warm Regards.

    Dear All,
    While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
    But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
    May I know how the value for this field gets calculated.
    Thank you.
    Warm Regards.

  • Release strategy for RFQ's not triggered after change

    Folks,
    Release strategy is active for RFQ's. In case of initial creation, the release strategy is active. After releasal a change is made to the existing RFQ. However, the release strategy is not triggered. Characteristics used are:
    1) document type (AN)
    2) purchasing type (RFQ purchasing document)
    It is obvious that these characteristics will not re-trigger the release strategy. On header level, there is no field in CEKKO available to re-trigger, for example total quantity? Any suggestions for a characteristic that can re-trigger the RS?
    Message was edited by:
            MdZ

    Hi,
    For RFQ Release strategy will be applicable only for Document type.No other characteristics will apply for that.
    As RFQ don't have any specific table where the data is stored related to RFQ.
    So we Use CEKKO which only identifies the document type of RFQ.
    In your case in initial process while creating the RFQ release strategy is active.
    What change you have made to the Released RFQ.
    rgds
    Chidanand

  • Release Strategy for contracts.

    Hi gurus,
    Good day,.
    Please help on this.
    We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
    Example.
    Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
    Thank you.

    Dear Acel,
    The example you given was working just fine and correct.
    a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    -> The release strategy will only be reset if the total net value for the contract was higher the previous
    value but not lower.
    As your example, quantity was updated to 1200, then it will reset when changing from 1000
    to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
    release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
    In system, it always assume if you had approved for the total value of the higher 1 before, then
    it should be fine for the lower total net value for your management and therefore not need to re-approve
    again for redundancy job. This was very logic in common business scenario in many companies.
    However, like in your example , if you had define a different release strategy for a value that met the
    the 1100 quantity, it will redermine the different release strategy. For example:
    USD 1 for every quantity = 1
    Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
    USD 1200 for quantity = 1200.
    Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
    Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
    Release strategy C for 1200 , characteristics from USD 1200 onwards
    Then if you change the quantity from 1200 to 1100, it will redetermine the release
    strategy B which means from Release strategy C to Release strategy B. If you
    only had Release strategy C that had a characteristics from 1000-1200, then
    it will keep the Release strategy C as released and it won't be reset unless
    if you had change it and the condition of the total net value was higher than any value
    before.
    Hope this will explain the logic.
    Ian Wong

  • PO release strategy for changes in price ($ and %)

    Hello,
    I have searched this forum and others to find an answer to my question, but as I was unsuccessful, I decided to post my question here.
    I have a requirement for a PO release strategy that involves triggering the release strategy only if the total value of the PO has increased over a certain dollar amount or %.  I will need to calculate the difference in the total value between the original PO and the changed PO. 
    Example:
    Original PO total net value is $1000
    PO after a price change - total net value is $1500
    Total net value has increased by $500 or 50%.
    Tolerance for price change is $200 or $20, so tolerance has been exceeded.
    I know I will be using the total net order value (CEKKO-GNETW).  I will have my tolerances in a custom table, and I will need to take the difference in the total net value from the changed PO and the original PO and check against my custom tolerance table.  I also know that I will use a user defined field (CEKKO-USRC1) to indicate if the tolerance has been exceeded or not.  I know that I will put this tolerance check code in the M06E0004 enhancement for changes to communication structure for release of PO.
    What I don't know is where will I find the previous total net order value once the PO has been changed?  Is the only place that information is stored in the change logs?  If so, what is the change log table name?  Or is there a different table that would contain this information?
    Thanks in advance for any help you can provide.
    Sincerely,
    Angela

    Update:
    I utilized function module EXIT_SAPLEBND_002 as a solution to this.  I got the old PO value from the database table EKPO, and I got the new/changed value from the I_CEKKO structure which is accessible from this FM.
    I check to see if my tolerance has been exceeded. If it has, I pass a 'Y' as a tolerance flag via CEKKO-USRC1.
    I originally thought about using the change document tables, but I discounted this when I discovered that those tables weren't updated at the time that the function module EXIT_SAPLEBND_002 was being hit.

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • Issue: Purchase order release strategy with storage loaction.

    Hi Friends,
    I have created release strategy for purchase order considering following characteristics.
    1. Plant
    2. Purchase organization
    3. Purchase group
    4. Document type
    Hence the release strategy is working fine.
    Now the requirement is changed, PO approves should be picked depending on the storage location wise. So i tried to create characteristic for storage location with table name CEKKO and with field LGORT. However system not allowing to create, telling that field LGORT not found in table CEKKO.
    Can any one tell me how to maintain this LGORT filed in structure CEKKO.
    Thanks in advance
    Shashidhar

    HI Shashi ,
      Thanks for your quick response,
    I have Appended a structure to Standard Structure CEKKO with Field LGOBE.
    Also we written the code :move:  i_cekko = e_cekko, in user User-Exit M06E0004 function exit
    FUNCTION EXIT_SAPLEBND_002.
    However, the release strategy is not triggering when PO is saved,
    also the user-exit is not getting triggered , even though i have included the statement ' Break-Point'
    in it.
    Kindly reply.
    Thanks  ,
    Shashidhar

  • Issue with PO Release strategy

    Hi experts,
    I have problem with Po release strategy in 5 to 10 purchase orders, i have created few purchase orders(2000 Po's) with same document type and company code ..etc and saved, then release strategy has been triggered.
    For few purhcase orders release strategy has not been triggered.
    If i take 1 po from that few purchase orders(Release strategy has not triggered) as reference and again if i create PO,new purchase order have getting created with release strategy.
    Can some body tel how this ican be possible, hope this might be standard syatem behaviour.
    Hope i should delete thos e purchase orders and i should create new PO's instead of of old PO's (Without release strategy).
    Some experts can share their experiance in this regard.
    And how i should proceed further with this issue.??
    Thanks

    Hi,
    You issue in your system has 2000Nou2019s purchase orders  with release strategy has been triggered but 5 to 10 purchase orders do have release strategy.
    & when you are creating a new PO with reference to old purchase orders (which release strategy has not triggered) and on saving NEW PO created with triggering release strategy.
    Cause for above:
    PO which release strategy does not trigger because the purchase orders are created before setting release strategy for PO. Those PO triggered release strategy and all are created after setting release strategy for PO.
    Action:
    Its completely business call for business users to go for options:
    Option-- >1# You can use same old PO which release strategy does not triggered, do GR and all other process
    Option-- >2# You can create new PO with reference old PO which release strategy does not triggered and upon saving you will have new PO number with release strategy triggered, then release PO & do GR and other related process.
    Regards,
    Biju K

  • Rel. strategy is not triggered while creation of PR with cost centr

    Hi Gurus,
    While creation of PR release strategy is not getting triggered with cost centre BCWSV870. But release strategy of PR triggered for cost centre BCWSV852 (In PR changed only cost centre as BCWSV852 instead of BCWSV870). Both cost centres are similar and the both cost centres are exist in characteristics value in CL20N for the same release strategy.
    My question is why for one cost centre triggers release strategy triggers and for other cost centre release strategy is not triggered. Can you please tell how come this and rewarded for answer this.
    With regards,
    C. Sundar Rajan

    Hi,
    In regard to problematic PR with cost center BCWSV870, was your PR maintained with only one line item? or multiple line items?.  In additions, when defining cost center as part of the release strategy structure, did you enter all cost centers with leading zeros?  Tak a further look into OSS Note 365604 for your further investigation.
    Cheers,
    HT

  • Release strategy for PR in Third party case

    Hi,
    We have this third party scenario where Purchase reqs are created at the time of Sales Order creation. A release strategy is attached to these purchase req by defining a custom field in MMaster, whenever qty goes up or equal to tht field release strategy is applied.
    The problem is, for the same material's PR, the release strategy is set in one case whereas for other PR (of different sales order) it is not set. Please help let me know what could have gone wrong.
    Thx.
    Amit

    Per your information you say that based on a custom field qty in material master release strategy is triggered. Do you have any charecteristic maintained for the Release strategy anything other than this parameter- because there must be some difference between the 2 Reqs.
    Or check the change history in Material master it may be possible that at the time of second sales order if the field value was changed so that release strategy was not triggered.
    Please give more details
    Thanks
    Deepak

  • 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

Maybe you are looking for