New po release strategy

hi,
i am having xxxxx class for po release strategy with 3 characteristics-(plant, po value and document type)
now i want to have only 2 characteristics with document type and PO value.
again i want to use new release codes for my new strategy, keeping the same class for release strategy.
can i define new release strategy using the new codes?, then what shall be the impact of the same on below
1. already released PO, now want to amend,(after new release strategy implimented)- what would be the effect on PO?? which release codes shall hit the same?
2. already release PO(i understand there wont be a problem in GR, as release ia already effected)
3. new PO shall catch the new strategy- no problem with the same.
for implimenting the new strategy using the same class, can i delete the old release strategy with codes or i just need to remove the value mentioned in the classification view of the release proceedure.

thank u.
my point is while re-defining the release proceedure.
earlier i had 150 release strategies and arround 40-50 release codes. now only 12 release codes
i just need to get confirm, if i create a new release code and assign a new release strategy using the same class(only deleting the plant characteristics), what will happen to old po(released) for which now we are amending.
i assume i need to delete/remove all the data of old release strategy available in classification view, and keeping the release codes as it is in release pre-requisites fr old release strategy.
or just any body briefe me what are all the condition for changing the exsiting release strategy.if i need to create new release code,release strategy by using the same release class.

Similar Messages

  • Precautions to be taken before going for new PR Release strategy

    Dear all,
    We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
    Need your advice on
    1)If we go for new release strategy as off  with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
    2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
    3)Any other which I missed out, please suggest me
    Thanks
    RS

    Hi,
    It is better to release all existing PRs using your current procedure without classificaton and clean up.
    If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
    REgards
    Ram
    Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

  • PR Release Strategy Re-determining due to Change in Text

    The PR release strategy was configured by a previous company.  There are existing PRs that are not completely approved (Release Indicator = 2).  The SAP instanced was transitioned to the company that broke away.
    The PR release has now been re-configured with new release strategies (groups, codes..etc).  What we are experiencing is that the existing PRs that are "released" do not show the new release strategy when the combination of release strategy/release group does not exist- This OK as well.
    When a user made a change to the Item Text and nothing else, SAP re-determined the release strategy and started the release process over again.  Is there a way to stop these PRs from re-determining and therefore restarting?

    Hi There
    Though the release strategy is different, i think all the classifications are same or old classification (even 4 or 5 parameters) may also part of your new full release strategy(You may be trimmed from old release).
    So when you do any changes or just go to the change mode and Check (F7) , system may find the new rel strategy.
    i have not tested the above scenario, i could recall some older posting based on that i did suggest the above
    Thanks Senthil P

  • PO Release strategy, error: class POCLASS class type 032

    All SAP Gurus,
    We are configuring new PO release strategy.
    When we go to Release strategy - classification
    (Release procedure for PO - Define release procedure for PO - Release Strategies - classification)
    It gives following error: Error in classification (class POCLASS class type 032).
    Where we can maintain the classification?
    Regards,

    Dear,
    Please follow bellow detail.
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1)     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
    2)     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
    3)     Define Release Procedure of purchase order: -
    In this step four processes involved.
    1)     Release Groups
    2)     Release Codes
    3)     Release indicator
    4)     Release Strategies
    1)     Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2)     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.
    3)     Release indicator: - In this step you have to define release indicator.
    Like X - Blocked, I - Under process, S - Release.
    4)     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 continue
    Click on classification button, Enter values of purchasing group for which you want to created release strategy.
    Regards,
    Mahesh Wagh

  • Clear release strategy

    We have implemented a workflow solution for approving purchase requisitions.  When a user changes a partially approved req, we want the the current workflow to be cancelled and a new one started with a new cleared release strategy. 
    I think I can use the ME_UPDATE_REQUISITION_RELEASE to update eban-frgzu to null, which will reset the release strategy.  However, all of the user exits that I've found up to this point get overwritten.
    My questions:
    Is there a good place to add this function? EXIT_SAPLEBND_004 seems like the place but the frgzu field get's overwritten later in the process.
    Is there an easier way of resetting the release strategy?
    Thanks
    Travis

    Hi,
    Check the following link:
    http://www.sap-img.com/workflow/sap-workflow.htm
    Regards,
    Bhaskar

  • 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

  • New Release Strategy in case of PO amendment

    Dear All,
    We have the release strategy at PO level on 3 parameters,
    Purchasing Group, Value and Document type.. for each parameter we have created the characteristics EKKO- EKGRP, EKKO-BSART, EKKO-GNETW. Till date system is working ok and trigreeeing the release strategy as per it should.
    When ever users edit the PO, again system sets the release strategy as per above logic.
    Now our requiremet is, when ever user edite the PO value or PO quantity, system should trigger a new release strategy.I come to know that, SAP have a provision to maintain the release strategy on "Version level also", I have tried the same but i facing one problem, when we try to create the characteristic based on Version , system creates it and put field name "REVNO", data types is coming "CHAR".
    Can any one send me a user manual and steps for this.
    Thanks in advance,.
    Vikas

    Hi,
    You can set a control within Config. there is a parameter called as release indicator.
    Follow this IMG path:
    SPRO> Materials Management>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Release indicator
    1     Cannot be changed
    2     Changeable, no new determination of strategy
    3     Changeable, new release in case of new strategy
    4     Changeable, new release in case of new strat. or val. change
    5     Changeable, new release if new strategy/outputted
    6     Changeable, new rel. if new strat. or value change/outputted
         Changeable, new release in case of new strategy
    Changeability of purchasing document during/after release which means how the system reacts if an internal or external purchasing document is changed after the start of the release procedure.
    Note that the values 1 to 4 apply to internal purchasing documents (purchase requisitions) and the values 1 bis6 to external purchasing documents.
    So you would need to set this Indicator for the specific release Id. which specifies whether the purchasing document can be processed in or is blocked for follow-on functions.
    Hope this explanation was clear.
    Prashant Rathore.

  • New release strategy should not trgger for PO released with old Rel Strategy

    Hi All,
    Please suggest. Po has been fully released with Release Strtgy V1 XX. Now I m replacing release strategy  XX with ZZ. If I change any po which has old rel str XX , system will reset new release strategy as in config changeability indicator 4 maintained.
    But requirement is if there is  any change or value decreasing in fully released Pos with old strategy  it should not retrigger new release strategy. If value Increases then New strategy should retrigger.
    Please help me on this.
    regards,
    Rohit

    HI Rohit
    A reset of the release strategy only takes place if
           -  the changeability of the release indicator is set to '4' in
              case of a purchase requisition and '4' or '6' in case of
              another purchasing document (purchase order, request for
              quotation, contract, scheduling agreement),
           -  the document is still subject to the previous release
              strategy,
           -  the new TOTAL NET ORDER VALUE is higher than the old one.
    The most important thing to consider in to avoid changes to release strategy customizing once the release strategy is used.
    The commom steps are:
    1- make sure all of the old POs should have been released.
    2- don't delete/change the original release strategy. create a new release strategy with copy function, then the old release strategy will not be replaced.
    3- if you delete the original release strategy and add a new release strategy which the characteristics in classification is same as old release strategy then the PO (have been approved) will be replaced with the new release strategy.
    Kind regards,
    Lorraine

  • New release strategy / Old PReqs

    Hi,
    New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
    But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
    Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
    Many thanks in advance for your clues.
    Regards,
    Grzegorz

    Hi,
    Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

  • Release Strategy for New Plant

    Dear All,
    I have a Release strategy in my 3 Plants  and it is working fine.
    Now I want to add one more plant under the same release strategy.
    I tried to add the new Plant in CL24N. System allows me to add the same in this but the RS is not working in this new Plant.
    waiting for reply

    hi,
    you follow the following steps to insert new characteristics value in your release procedure.
    1. define the new characteristics value plant4 in your characteristics.
    2. assign the same characteristics value plant4 in classification of release strategy.
    3. run the release simulation and comes out.
    4. now create PO for your requirment and save it.
    5. u can use me22n/23n to view your release status of po.
    hope it helps....
    manoj singh

  • Release Strategy with New Class and Char.

    Dear All,
    I have facing problem when creating the new release strategy for different country. i have create new Characteristic and class for new Release streategy.
    when i going to add in Release group.. system giving the error.
    Diagnosis
    Here you can assign release groups to release classes. Only one release class should be used within the release groups for overall release and the release groups without overall release in each case. However, in this instance several release classes have been used.
    My existing Characteristic for india :
    ZP0_GNETW     Total net order value     CURR     15     2     INR
    ZPO_BSART     Order type (Purchasing)     CHAR     4     0          
    ZPO_EKORG     Purchasing Organization     CHAR     4     0          
    ZPO_EKGRP     Purchasing group     CHAR     3     0          
    New Characteristic for South africa :
    ZPOSA_BSART     PO Order Type ATSA     CHAR     4     0          
    ZPOSA_EKGRP     Purchasing Group ATSA     CHAR     3     0          
    ZPOSA_EKORG     Purchasing Organization ATSA     CHAR     4     0          
    ZPOSA_GNETW     Total net PO value ATSA     CURR     15     2     ZAR
    ZPOSA_WERKS     Plant     CHAR     4     0          
    Please help me how do configure 2 release strategy for 2 country.
    I will be very thankfull to u.
    Regards,
    Vishal Garg

    HI Biju K,
    I can use exising Characteristic Like Purchasing Organization & Purchasing Group & Plant etc. But in the case of Net order value : ZPO_GNETW Total net PO value for my indian company Currency is INR and for My SA company currency is ZAR. What will i do in that case.
    Please explain..
    And aslo clear the concept of creation of new Characteristic as Company Code & design different release strategies based on company code. How i can do that..??
    Please explain in details.
    I will be highly thankfull to u.
    Regards,
    Vishal Garg
    9810402156

  • How to assign Release strategy with new PO type

    Hi experts,
    I have created new PO type but the same is not mapped with release strategy at the time of raising purchase order.
    I have done the following steps :
    a ). Creation of new doc type via SPRO > MM > PURCHASING > PO > DEFINE PO TYPE
    b).  Edit characterstics in release strategy via path SPRO > MM > PURCHASING > PO > RELEASE PROECURE FOR PO > EDIT CHARACTERSTICS > VALUES  (  MENTION NEW PO TYPE & DESC. HERE )
    Still I am unable to find release strategy tab in purchase order. Please help.
    Suggestions / Rewards will be highly appreciated.
    Regards,
    ( Rajneesh Gulati )

    Hi ,
    I dont know how much customisation u have complited ,
    But for release strategy
    1 Following are the imp charecrticities ct04 you have to define
    Order type (Purchasing)
    Plant
    Total net order value ( with  table &  field)
    2.check or create relese group is assighned to appropriate class cl01 (with above charecricities )
    3.define relese code ( in this u define release level --supervisor , manager etc)
    4.release indicator  (block ,release)
    5.define the group with strategy in that specify prerequisites,release status,classification (specify to the document & plant you want to maintain)
    6.create po me22.  In me29 you can release it( unless u cant process)
    Dev

  • Release Strategy for a new material type in PR

    Dear Friends,
    One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
    Regards,
    Ask

    Hi,
    Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
    Then follow all the cusmozation path for your PR release startegy .
    For Config part refer the below wiki link it may help you.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
    http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808

  • 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

  • PO Release Strategy, include new field.

    Hi,
    What are the steps involved to include a new field ( for e.g Account Assignment Category ) which is not there in the standard structure CEKKO.
    Shall I have to change the structure CEKKOZZ or from the user exit 'M06E0004'?
    Thanks in advance,
    Regards,
    Madhu.

    Hi Arif,
    Thanks for your reply. My requirement is to exclude a material group from PO release strategy.
    If I include the characteristic related to material group in PO rlease class, and subsequently change the PO release startegy below is the problem.
    Suppose PO contains one item or multiple with same material group, then only it is picking release strategy ( let us say all materials belong to mat group: 101)
    If PO contains multiple items with different mat groups ( for e.g: 101, 102 & 103 ), then it is not picking up the Release strategy.
    classification data is perfect and release strategy is ok for all material groups ( if PO contains only one material group)
    I have checked in the program : MM06EF0S_STRATEGIE_CEKKO , the logic written in the program is such a way that, if two values exist for a doc field, then blank is passed to CEEKO structure.
    I will try with user exit, and please let me know if you have any other idea.
    Many Thanks,
    Madhu.

Maybe you are looking for

  • Random restarts with Eclipse SLI board

    This is a copy from my post on the Vista forums havent gotten much help there. Describe the problem in detail! I just built a new system on December 22nd 2008. I do Tier 2 and 3 Helpdesk work so I can work my way around a system. I put the machine to

  • Change in one line item should Populate for all line items

    Hi , We have added one custom field Prefereed Vendor at line item level. We have requirement that if Prefereed Vendor at one line item level is changed, then it should populate for all the line items. Can any one tell me how it can be implemented? Th

  • SAPKW70017  shows error XPRA_EXECUTION

    Dear Support, While applying SAPKW70017 it shows error. The import was stopped, since an error occurred during the phase XPRA_EXECUTION, which the Support Package Manager is unable to resolve without your input. After you have corrected the cause of

  • How to add custom columns with BO data from GP to UWL

    Hi We have CE 7.1 in our project UWL taskitems only have GP workflow tasks. In UWL we can see that by default there are standard columns but now we need to add custom columns with data from ours BO associated to process instance For that we need to d

  • Workshop problem in building relationship

    Hi there, It seems that workshop (comes with WebLogic 8.1) has problem building relationship. It keeps saying that it cannot retrieve column info. from my data source, when in fact creating entity beans from the exact data source/table works fine. Am