Configure Release Strategy for Contract

Hi All,
I want to Configure Release Strategy for Contract.
I have configured Release Strategy  for PO. Is the process for both is similar?
What should the table & field name should we use for configuring Release Strategy for Contract.
Pls. guide.
Regards,

Thanks Neeraj for the reply.
For PO, I have used Table CEBAN, Field BSART, GNETW.
Could you pls. suggest what fields should we use.
Also tell me what would be process of releasing the contract using ME35K, as the Screen seems to be different from ME29N.
Regards,

Similar Messages

  • Purchase Order not subject to release strategy for contract rel. strategy

    Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
    So I have checked this release strategy with this codes:
    CL24N ok,
    CT04 ok,
    CL30N ok,
    CL20N ok,
    Release simulation in release strategy works,
    Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
    Thank you for your help in advance.

    I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
    I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
    Also compare your release strategy settings with many existing documents in SCN.
    Check your Classification should be like that.
    You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

  • Release Strategy for Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

  • 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

  • Release Strategy for Contract

    Hello Experts
        I am using release starategy for contract and using communication structure CEKKO in characteristics. I want to use other parameter such as material master number (MATNR) for characteristics. I see that CEKKO has component .INCLUDE (Communication Structure: PO release for User Exit). Does any one know how to use it in characteristics and if I use it can I design release strategy for particular materials?
    Thanks
    Ankit

    this has been discussed multiple times on this forum - "Release strategy at item level for purchasing docs - PO/SA/Contract" not possible...
    refer below threads
    Why release strategies for PO at header level only
    PO Release Strategy
    Release strategy - item level
    yogesh

  • Release Strategy for SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

  • Release Strategy for PO not kicking in

    Hello SAP Experts,
    I have gone through all the steps of configuring release strategy for PO. I checked at the end with the transaction code OMGSCK and everything is good with no error. But when I test the strategy by creating a PO, the 'Release Strategy' tab does not come on in the PO Header. This means that the Release Strategy did not work. I have troubleshot over and over again right from the Characteristics/Class, all the way to the Release Strategy, but no breakthrough.
    I will appreciate and award points for helpful hints.
    Thank you in advance.
    Joel.

    Please list all your char you have created and the value of char.
    Than please tell the PO details.
    once i got this info than only i can see the problems.
    you can do one more thing
    goto CL30n and enter the class and class type 032
    than hit enter and enter the value of char which you have used in the PO and then hit find initial class button from top menu
    see if any release strategy is pulled or not?
    if it is determine morethan one that means you have same value exist in more than one release strategy

  • Release strategy for Transport requests

    Hi,
    Can anybody give me the detail steps to configure release strategy for transporting requests?
    we are having Dev and Prd systems.
    Regards,
    Vinnu.

    Hello,
    I hope you have configured TMS for two system landscape.
    Just make the transport routes also, make DEV system as a Domain Controler.
    Then transport requests will automatically come in to the request queue.
    Using tx stms_import , import those request sequentially !!
    Note: Points always encourage me to reply !!

  • Release Strategy for STO

    Hello Experts,
    We have a requirement to configure release procedure for STO scenario. Release procedure needs to be captured in STO PO's.
    We have 6 plants - A,B,C,D,E,F, and each plant is having different approving authority individually.
    When STO PO is created, it has to be approved by Issuing plant authority & receiving plant authority as well. The major concern here is for eg., approval authority for plant A can be a issuing authority at one instance & receiving authority at another instance.
    How to configure release strategy for this.
    We believe ,creating those many release strategies for all the combinations of plants  will be a hectic task & still it'll multiply with the introduction of more number of plants.
    Hence looking for a more simpler & feasible workaround/solution.
    Regards
    Mahesh.C.R

    Hi,
    you can use Supplying plant ( RESWK) and issuing plant (werks) both as characteristic and with these combination you can configue release strategy.
    Or you can use User field format character for release strategy (USRC1)as per your requirement.
    YB

  • How to configure release procedure for rate contracts release

    Dear all,
    How to configure release procedure for rate  contract following are the requirements
    they are two release codes c1 & c2 <=100000,>=100000
                    if  c1 is not there c2 has to be approved
         Change in the value of the rate contract contract
         Change in the validity of the rate contract
         Addition of deletion of line items
    While using a non u2013 released rate contract in the PO an error message should shoot out.
    Also the logic should be changed while using the rate contract in the PO.
    The usage of the rate contract should be till the validity of the rate contract. i.e. the measurement should be end date of the rate contract and the PO creation date and not the delivery date of the PO. &
    It should be possible to refer existing valid rate contracts in purchase orders.
    Regards,
    bhaskar

    Hi,
    In SAP rate contract is known as value contract denoted with wk. The release procedure for rate contract is same as that of other contracts and scheduling agreements. The tables  for contracts will vary with SA (Scheduling agreement) .You may try and maintain condition records based on the customer combination and maintian the validity date of condition records as per your requirement.For contract and PO will have the same header/item table as EKKO/EKPO, and the release
    class in standard is the same FRG_EKKO, you can use the same for contract.
    To distinguish if it's a contract or PO, EKKO-BSART can be used.
    For contract EKKO-BSART will be MK or WK, while PO will have NB/UB etc..
    You can restrict the document type to set up the release strategy for only contract.
    Of cause, you can also create your own release class Z* for contract copying standard
    one FRG_EKKO via CL01/Class type 032, and then assign the class Z* to customizing:
    OLME:
    -> contract
    ->Release Procedure for Contracts
    ->Define Release Procedure for Contracts
    ->Release Groups
    If you have already created the PO release class.
    Assign a new chracteristic of Document Category -BSTYP
    Please check below link for detailed release procedure. I hope this wil help you out .Thanking you.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE#RELEASEPROCEDURE-TABLESUSEDFORRELEASEPROCEDURES

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

  • 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

  • Release strategy for PO, RFQ & Contract

    Hi,
    We have created release strategy for PO, RFQ & Contract.
    Characterisitc is created for Target Value for Header Area (CEKKO-KTWRT)
    for RFQ & Contract it working fine but for PO not triggering.
    what can be the cause.
    Pls guide.

    Hi,
    Melih is right, for POs you can not use the target value.
    What you might do is to include the document type and CEKKO-GNETW as additional characteristics and then set for contract document types the GNETW blank, and for PO documet type the target value blank. Blank means any value should fit.
    I hope this hint helps!
    Best Regards,
    Arminda Jack

  • MM:Release Strategy for Release Order again Approved Contract

    Hi,
    Release strategy for Release Order is required or not against approved contrat??
    As fas as I know once the contract is approved, release order is not required to approve again.
    This is the standard setting from SAP or We need to do some setting for this??
    In my support project I have studied the release procedure and found that, same release strategy and release Group has been used for Purchase Order and Contract.
    Please let me know if anyone have faced this rquirement  or I have to go for Z development for this requirement.
    Thanks you.

    Hi Lalita,
    Thank you for your quick suggestion.
    yes definitely the release stratergy and release group should be set up separately but here both are same
    that is the reason this is  picking of the same release procedure again evenif the contract is approved.
    we have following release characterstic for the release procedure.
    1) Purchasing Group
    2)Total Net Order Value
    3)Order Type
    4)Purchase Organisation
    5)Material Group.
    I think for the above characterstic we must a separater value for PO and Contract but Currently all are merge
    in this only
    But Can you tell me "Release Order should be subjected to release procedure" this is correct or not .
    If yes then what is the base for this, I mean is it working on the concept that " If do relevent
    release characterstic value is found then no release procedure and this is treated as autorelease in sap"
    Thanks you.

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

Maybe you are looking for