In release strategy unrelease should happen from higher level

Dear Users,
In our release strategy we want to make changes like whenever user want to unrelease it should happen from higher hierarchy to bottom level as vice versa of release process. If there is any solution for this process please provide your suggestions.
Thanks,
Manoj

Hi,
For restriction from higher hierarchy to bottom level, refer similar blog
Release Strategy: Restrict lower users to revoke PO after the complete release by superior
Regards,
Biju K

Similar Messages

  • Release Strategy for reservation created from PM and PS

    Dear All,
    How to configure the release strategy for reservation generated  from PM and PS.
    Regards,
    Atanu

    do you talk about release strategie for requisitions, or really reservations?

  • Release strategy: User should release only with his highest release code

    Hello,
    Because of personel absences we want to configure the release strategy so that:
    User A or user B releases in the normal case the first level of a PO (with release code 01).
    User C (Manager) releases after release code 01 with release code 02.
    User A is deputy of user C. In this case user B will release with code 01 and user A will release with code 02.
    Because user A can use depending of the case release code 01 or 02 (C deputy) it must be avoided that user B sets release code 01 and 02 for the same purchase order.
    Do you know about a solution for this issue
    Br
    Manuel

    Dear W1N,
    But the systems knows that A released with code 01 and when A tries to release  with code 02 the system knows that the same person of release code 01 is trying with release code 02.
    <b>The aim is to avoid the second release from the same person and not to automate the release strategy.</b>
    In such a case A has to cancel the release for code 01 (ME28) and wait until B is reachable to do the release of code 01.
    When C is absent A knows that his task is to release code 02.
    Is this check really not possible?
    Best regards
    Manuel

  • Release strategy for PREQs created from PM work order

    Hi All,
    I have an issue with determining  release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
    We have activated release strategy for Purchase requisition based on the following characteristics:
    CEBAN_PLANT
    CEBAN_COST_CENTER_GROUP
    CEBAN_MANUAL
    Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding  cost center goups.
    In the user exit we have consider to cases:
    The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
    The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
    The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
    We have defined  for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
    Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
    Best Regards,
    Desislava

    Hi,
    For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
    Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
    Regards,
    Raj

  • Purchase order release strategy based on over delivery tolerance level

    Hi Boss,
    I like to set the Purchase order release strategy based on the over delivery tolerance. But when i checking, the over delivery tolerance filed UEBTO is not in the communication structure CEKKO. Can you please help me how should i extend the CEKKO with field UEBTO.
    I do not have the ABAP experience, please guide me with coding.
    Thank you,
    Siva

    Hi Siva:
    You should request the development key for this structure under your SAP system, then you can add the extra fields in CEKKO.
    Good luck
    Z.T

  • APO DP: Disaggregation to product&plant level from higher levels.

    Hi.
    We do demand planning on groups of products and for country/region in general, we have around 48.000 CVC's in our current setup. It works very well.
    A new situation has arisen where we need to have the forecast split down to product and plant level.
    As is we simply don't have the information at this level of granularity.
    I don't see how we can add for instance product to our setup, we have around 20.000 products so the number of CVC's in DP would become massive if we did this.
    I was thinking that perhaps something could be done by exporting the relevant key figures to a new DP setup with fewer characteristics (to keep the number of CVC's down) via some infocubes, perhaps some disaggregation could be done via some tables and the BW update rules. This still leaves the issue of how to get the figures properly disaggregated to plant and product though.
    Does anyone have experiences on how to get the figures split to lower levels from DP when you're planning on a higher level?

    Simon,
    One approach as you mentioned can be creating Z Table where in you set up disaggregation proportion from product group level to product level or product location level.
    Product Group X  100       Product A@loc1 10
                                          Product B@loc1 90
    Download your planning area data into infocube C and then use BW routines to convert the data from group in infocube C to lower level refereing Z Table....into another infocube..
    SAP also provides such standard functionality of spliting the aggregate Demand plan to detailed level
    SNP plan..through functionality like location slit or product split.
    Essential you will be using same concept in yor BW solution or you may also want to consider the
    release your DP to SNP planning area its as solution of diaggregation of data  to lower level.
    Regards,
    Manish

  • CALC DIM or AGG - Can we aggregate from higher levels?

    Hello everyone,
    We have a custom dimension called LOCATION, under which we have Continents ASIA and EUROPE. Under ASIA and EUROPE we again have countries (India & England) under which there are states. Now data may be entered at a Continent level or Country level. If we do a normal AGG or CALC DIM operation, the higher level data will get overwritten since aggregation is done on a bottom up basis from zero level members.
    Can we aggregate from a higher level (say Country or Continent) in the dimension up to the Location level (i.e. override the default zero level up aggregation) ?
    PS: Creating a dummy member would not be an elegant solution, since I have presented the problem in a much simplified way, and there are many level of hierarchies - and a dummy will be required under each hierarchy level.
    Any suggestion would be of great help.
    Thanks..
    Sayantan

    I know you are against creating dummy members but if you don't there is no way to know for sure you are aggregating correctly. Most people want to see the dummy members just so they know why the parent doesn't equal the sum of all the children.
    We have a million+ member customer dim. Quite a few of them are loaded at the parent level. Our parent child hierarchy (not dim) gets built from the fact table+dim. So if the etl finds a record in the fact table that has children in the dim table it creates the dummy member to load the data to. This has worked well for us. Good luck.
    Edited by: user7332747 on Apr 23, 2009 1:34 PM

  • Transfering PIR from higher level.

    Hi.
    i am having a problem  here. mine is   discrete manufacturing  process.i am using VC. few of my components are  common to 3 ferts in the BOM. one of the fert is a VC material. i dont want the reqirements to be transvered for the VC material to the raw materials.  but i want the requirements to be transvered from other two ferts to the raw material.
    how do i restrict the transver of reqirements for only one material.

    Hi,
    You maintain following Material Master settings for your FERT VC materials as below:
    1.For  Not Transferring dependent requirements to lower level of FERT:
    maintain 1     Materials for dependent requirements are not planned
    in Material Master--> MRP-4 View->MRP Dep Requirements
    2.For  Not Transferring dependent requirements to lower level of FERT:
    maintain (Blank) Materials for dependent requirements are planned
    in Material Master--> MRP-4 View->MRP Dep Requirements
    Save above settings for respective FERT materials and then try with MRP Run.
    Hope your problem resolves.
    Regards,
    Tejas

  • Need to activate release strategy for PR from PS(a/c assignment N)

    Dear experts,
    I need to establish release strategy in PR raised from Project System. PR account assignment in 'N'= network. PR will be differentiated PR value wise . Please help in this regards,
    Thank you.
    Kind regards,
    Zusen

    Hi
    You already have account assignment category (KNTTP) in communication structure CEBAN. You can use it to define your release strategy. If you wan to use field which is not there in CEBAN then you need to append CEBAN with the help of apaper.
    Use this link as an example for release procedure and create your own with KNTTP.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
    Regards
    Antony

  • 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 and workflow in Purchase Requisition

    Hello All,
    My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
    Thanks in advance for your help!!

    You will need to activate the user exit. This will keep the PO release strategy simple.
    Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
    In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
    Just a couple of points:
    1) What will you do if one item in PO is created with reference to PR and the another item is not?
    2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
    Hope this helps
    Lakshman

  • Autorization of release and derelease in ME29N  in release strategy tab.

    Hello Experts,
    I have a requirement where the authorization has to be given to a list of user maintained in my ztable for  RELEASE CODE (T16FS-FRGCO =  01).
    For rest of the release codes in release strategy it should work as the standard process. if the processor in  release stategy tab and sy-uname are same then the  system should allow to relase or derealse the PO and save it.
    But for RELEASE C ODE 01 i'm maintaing the ztable and checking that if user name maintained in my ztable and sy-uname are same then system should allow to realse, derelase and save the PO.
    I'm writing my code  in EXIT_SAPMM06E_006  -- Include ZXM06U36 for this check but it is not working for me.
    Please let me know the EXIT or the correct way of doing it.
    Thanks,
    Naveen

    Hi Jai,
    Try this exist:
    Enhancement   M06B0002       EXIT_SAPLEBND_001  ZXM06U13  Changes to comm. structure for purchase requisition release                    
    Sample code:
    *Check the authorization.
    * This is to set the  e_cekko-usrc1 = 'Y'  be excluded from the Release Strategy check.
    IF SY-SUBRC = 0.
       e_cekko = i_cekko.  
       e_cekko-usrc1 = 'Y'.
    ENDIF.
    Some alternative Exits:
    Enhancement     M06B0005     Changes to comm. structure for overall release of requisn.                    
    Enhancement     M06B0001     Role determination for purchase requisition release                    
    i hope this may helpfull.
    Thank you,
    Thanks,
    AMS

  • IF there are two release strategy, How it will work?

    Hi, Can u Please help, if we have two release strategy, and PO first gets blocked by one release strategy,  if we release that PO and check for the another release strategy, it is possible in ABAP? and How? Which Function module or BAPI we have to use for checking both the releasing strategies, If PO gets blocked by one release strategy and it is released from that particular release strategy, PO should get blocked by another release strategy, HOW this works? Kindly HELP!
    Edited by: Digheme on Sep 29, 2010 3:58 PM

    Hi,
    But instead of using cumulative, if you use defrential level 2 backups from maonday to saturday, it will do the same for you and will occupy less space.
    Navneet

  • Release Strategy Triggered even if the characteric values were not correct.

    Hi,
    I have configured release strategy based on characteristics
    Purchasing group and
    Document type
    It has 2 release indicators with 3 levels of release.
    There are 2 release strategies assigned to same group 01 but have  different release codes namely 01,02,03,04
    Release Strategy A1has
    Doc type NB and Purchasing group 120
    Release Strategy A2 has
    Doc type ZINT and Purchasing groups 130,131,132,134,135,136,137,138,139
    However a strange thing happened.The release strategy was triggered for doc type NB and Purchasing group 190.
    This purchasing group is not listed in either of the 2 strategies 
    Can any one explain why the release strategy got triggered?

    That means the old release strategy is not cleraed from the system
    do one test
    Go to CL30N tocde and enter you release class and class type 032
    hit enter
    now here enter the value of your char which is in the PO and hit Find in initial class from header
    see which release strategy is pulled by the system
    here you will see the release strategy and make sure that is not other than what you expect

  • PO release strategy - release code

    Hi Experts,
    I have completed the release strategy and transported to production.
    However noticed that the release codes that has been configured earlier wasn't in the production.
    Is there a way to update the release codes in the production besides using SPRO (no authorisation for maintaining - only display) like using CL24N to update the characteristics?
    Thanks and regards

    Hi,
    Please first check the attached notes that refer to transport issues.
      365604   FAQ: Release strategies in purchasing
      186809   OMGQ/CL24: Inconsistency for release strategy class
       86900   Transport of Release strategies (OMGQ,OMGS)
       45951   Transporting class data: system / client
       10745   Copying classification data to another client
    The classification data must be sent over using ALE. It does not get
    transported directly.  Notes 45951, 86900 and note 365604 should help.
    Please follow the instructions in note 45951.
    You can obtain more information about how to set-up ALE in the Online
    Documentation CD (R/3 Library > CA - Cross Aplication Components >
    Business Framework Architecture > ALE Integration Technology > ALE Quick
    start).
    However, if you can't set-up ALE, you can re-create the classification
    data agin in your target system. For that you have to:
      1- assign new values to the characteristic master data (t-code CT02)
      2- assign the new data to the classification system (t-code CL30)
      3- verify the consistency with t-code CL24. Please see note 186809.
    For more information, please see note 365604.
    The transport of release procedure customizing data can only be done
    in a restricted manner. Please take a look at attached Note 86900 and
    follow the procedure described in this note, in order to correctly
    transport your release strategies.
    Classification data can only be transported via ALE as per note 45951.
    Note 45951 explains what class data for the release strategy will be
    distributed from one system to another. It does not describe how to
    implement as this involves a lot of explanation and is truely a
    consulting issue.
    There is another possibility that you could take into consideration for
    the classification is to import them via batch input:
    RCCTBI01 for creating characteristics
    RCCLBi01 for creating classes
    RCCLBI03 for classification
    Best Regards,
    Arminda Jack

Maybe you are looking for