Release Strategy without Classification VS with Classification

Can you have a strategy based on with classification and another one without classification in the same client.
Thank you.

Hi
You can have either of the One active in a system
If you have activated RS without Classification, all the PR's will be subject to Release Process..
If you now activated RS with Classification then this will Not work as the sytem has already found a RS wothut classification & not depebndent on any charcterisitics.
So you can use only one of the Combination.
This is applicable to only Purchase requsitions.
For Purchase orders & othe Documents you will have only with Classification.
Thanks & Regards
Kishore

Similar Messages

  • Shifting the PR without classification to with classification

    Hi All,
    I have deleted the PR release strategy without classification  randomly and configured PR release with classification in dev server.
    Now I want to delete the PR without classification from Live server and incorporate the new PR release strategy with classification in live server.
    Let me know the sequence I should follow to delete the PR without classification from Quality server and apply in live server so that new PR release strategy with classification should take place.
    Thnx,
    AC

    hello Amit,
    yes, delte the strategies first.. check Table T16FS, T16FV and make sure there are no entries
    Then delete the codes and check T16FC, followed by the groups.. T16FG.. these should dbe empty
    You don't have to delete the characteristics and class information, if you know you'd be using them again

  • Migration form W/O Classification to With Classification Release Strategy

    Hi MM Experts,
    Our client is currently having purchasing requisition release strategy based on without classification. There are almost hunderds of release codes for multiple sites.
    Now he wishes to migrate to release strategy with classification. So, Can anyone guide me on what all the cut-over tasks that has to be considered before going live ???
    Thanks in advance.
    Best Regards,
    Devendra Gaware

    hi,
    first for doing  the settings
    follow this link
    http://www.sap123.com/showthread.php?t=59
    all these settings should be done in development server and test it
    if it working good
    migrate the data to production server
    if useful Reward me
    Thanks & Regards
    Swathi

  • How to set the Release Strategy without classification for PR

    Hi,
    I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
    I crated the Release Codes, however not able to find what options to choose in the following steps :-
    Release indicator
    Assign Release Indicators
    Release Points: Prerequisites
    Determination of Release Strategy
    Regards,
    Yogesh

    1. Release codes                                                            
       Create the release codes.     For  Purch. Officer, Manager and Sr. Manager                                                                               
    Like PO, MG, SM                                      
    2. Release indicators                                                       
       Define release indicators and branch to the detail screen. Here you      
       define whether fixed purchase requisitions may be changed by Materials   
       Planning, for example, and whether an RFQ or a purchase order may be     
       created from the requisition.                                            
       You can also determine the field selection here.                                                                               
    In the area "Changes after the start of the release procedure", you      
       specify whether a requisition may be changed after the release           
       procedure has begun. You specify whether the strategy has to be          
       redetermined after changes, or whether the release procedure has to      
       start all over again from the beginning.                                                                               
    This parameter bears a relation to the parameter "Value change". For     
       example, previous releases are not cancelled if the value of the         
       requisition item after the change does not exceed plus 10% of its        
       original value.                                                                               
    Attention:                                                               
       Be sure to create a release indicator (e.g. B for "blocked") that        
       serves as the starting point for subsequent indicators. Do not set the   
       indicators for release for the issue of RFQs and PO on the detail        
       screen for this indicator.                                               
       Also create a release indicator characterizing the released status.      
       Set the indicators for release for the issue of RFQs and PO on the       
       detail screen.                                                           
    You can use sytem defined indicator in this case you don’t have to do anything                                                                               
    3. Assignment of release indicators                                         
       Assign a release indicator in dependence on the status of the release.                                                                               
    Example:                                                                 
       You create a release strategy S1 consisting of two release codes 01      
       and 02. Release with 01 is a prerequisite for release with 02. If        
       release has been effected with 01, the requisition has been given the    
       "all clear" for the issue of RFQs.                                       
       You have created the release indicators B (blocked), 1 (cleared for      
       issue of RFQs) and 2 (cleared for RFQs and PO).                          
       Now enter the following as assignment:                                                                               
    Strategy   C1  C2  C3 ...                                                
       S1                          B (blocked)                                  
       S1         X                1 (RFQ)                                      
       S1         X   X            2 (RFQ/PO)                                                                               
    4. Release prerequisites                                                    
       Define which release codes are involved in a release strategy. Specify   
       whether a code is set for a release status following release, and        
       whether one release status is a prerequisite for another (+).            
       Example:                                                                 
      Strategy   Code  C1  C2  C3 ...                                  
    S1         01    X                                               
    S1         02    +   X                                                                               
    5. Determination of the release strategy                            
    Determine the conditions under which each release strategy is    
    assigned. The criteria are account assignment category, material 
    group, plant, and value of the requisition item.                                                                               
    Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
    E.G if you will not define the Material group here but it will default in req in that case this will not work that’s the reason you have to work with Classification.               
    <b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

  • Shifting the PR without classification to classification release strategy

    Hi Sap Guru,
                        I have deleted the PR release strategy without classification and configured PR release with classification in dev server.
    Now before putting to production server I have to delete the old one and transport the new one. I have done the same procedure in Quality server but while tranporting the request the old one is not deleted and new strategy is also not mapped in Quality server.
    Let me know which sequence I should delete the without classification in the system and incorporate the new release strategy with classification in live server.
    Thnx
    AC

    When you deeleted "Without classification". the chnages were supposed to be transported to Production all the way.. first
    This should be followed by your configuration through Classification.
    The order is :
    Characteristics first- BD91
    Class- BD92
    Your configuration and any other custom changes
    and Classification data- BD93 in the very end
    If you have messed up,
    delete your strategies first, and then your classes and then your charcateristics .. transport them and restart the cycle

  • Purchase Requisition Realease Strategy without classification

    Hi,
    Request for detail process and configurations for Purchase Requisition Release Strategy without classification.
    We have 5 authorities like A1 (Lowest) and A5 (Highest authority) in the organisation to release the PR.
    The PR should be released according to value slabs.
    Thanks a Lot.
    Sachin

    Hi Sachin,
    IMG> Materials Management>Purchasing> Purchase Requistion> Set up procedure without classification
    This process is similar to process of with classification
    Go through the link below:
    for this no need of creating characteristics and classes
    http://www.sap123.com/showthread.php?t=59
    http://help.sap.com/erp2005_ehp_03/helpdata/EN/75/ee150b55c811d189900000e8322d00/frameset.htm
    If useful, reward me
    Thanks & Regards,
    Swathi

  • PR-Rease strategy with classification

    Hi,
            What are the steps Involved from shifting PR without classification to with classification?
    Can we include the parameter # 1)  Total value of requisition for overall release procedure 2) Plant 3) purchasing group 4) cost centre 5) Account assignment category in with classification startegy ?
    Thanks.

    Hi,
    If you set up the release procedure with classification for purchase requisitions, the procedure without classification is deactivated. The two procedures are mutually exclusive (that is to say, you must decide in favor of one of them only - you cannot use both).
    If you wish to set up both the overall release procedure and the item-wise procedure for requisitions, you must create one class for each procedure.
    To set up a release procedure with classification, you must make a series of settings in Customizing. You must perform the following steps:
    1. Create characteristics and classes
    Note
    If you wish to link your release procedure to workflow, you must perform steps 2 and 3. You make these settings in Customizing for Business Workflow (Basis -> Business Management).
    Otherwise, continue with step 4.
    2. Define organizational plan
    3. Assign standard tasks and activate event-receiver linkage.
    4. Set up release procedure with classification
    a) Create release group
    b) Create release code
    c) Create release indicator
    d) Create release strategy
    Note
    You need only carry out the following step if you wish to link your release procedure to workflow.
    e) Assign release code to a release point
    5. Check release strategies
    And, regarding your 2nd query:
    In communication structure CEBAN, you will find all the fields that can be used as characteristics for a release condition (e.g. MATKL for the material group and GSWRT for the value of the item).
    Check which fields you wish to use as characteristics for your release strategy. To do so, choose Tools -> ABAP Workbench -> Development -> Dictionary, enter CEBAN in the Database table field, and choose Display.
    Regards,
    Narayana.

  • Difference between PR Relase with classification and Without classification

    Hi,
    Can any one tell me what is the difference between PR release  with and without classification
    Thanks
    Akkshaya

    For PR with release strategy without classification only item level release is possible. But for PR with release strategwithat classification overall release is possible.
    Below links will give you the complete details
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Both cannot be used together. Only one at a time can be used
    Regards,
    Ashwin

  • 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

  • Issue with Purchase Requisition Release strategy

    Hi Gurus,
    We are using ECC 6.0.For the approvals of purchase requisitions, we are using standard SAP functionality of release procedure. There were some 52 release strategies configured for the PR .The release strategy was based on value of the following fields that is below were characteristics grouped together for class for PR:
    1.     Creation Indicator of PR-R (Configured only for manually created PRs)
    2.     Purchasing Group
    3.     Value of the PR
    As a result of PM module implementation, there is requirement of additional 30 release strategies.
    We configured them but one more field of doc type was added in the characteristics fields.
    Now the release strategy was based upon following fields:
    1.     Creation Indicator of PR-R (Configured only for manually created PRs)
    2.     Purchasing Group-(Configured against new purchasing groups )
    3.     Value of the PR
    4.     Document type of purchase requisitions.
    Classification data was accordingly maintained that is for older release strategies,
    Old PR doc. Type: NB was maintained where as other values were same. For new release strategies, new PR document types:NB1-NB6 for Doc type have been maintained .
    The above set up worked fine for some time. But suddenly, none of the PR release strategies are working. I checked all the related configuration settings and all look fine. I also checked my release strategies in tcode: OMGQCK. But no error was there.
    Could any body help in finding the reason why PR release strategy stopped working all of a sudden? What could be the probable reasons? What should be the approach to resolve it?
    We are in testing phase. Many of the test scripts failed due to this issue.
    Quick response will be appreciated!!!
    Thanks & Regards,
    Niti

    Dear Niti,
    Please check if your "overall release" indicator is consistent for document type and release group:
    a)SPRO:MM-PUR-PR-Define Document Type
    "overall release" indicator
    b)SPRO: MM-PUR-PR-Release Procedure-Set Up Procedure with Classification
    ->Release group
    "overall release" indicator
    Regards,
    ian,Wong Loke Foong

  • 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

  • Release strategy tables

    Please tell me the tables used for release strategy of PR, PO, service PR, sercice PO, RFQ, contract, and delivery schedules.
    Is there a method of finding out the table by some methodology. It is not possible to remember all the tables.
    In case of PR item level release is required. Give some guidelines as to how to activate item level guidlines. it is possible both with and without classification.
    Regards

    HI,
    Release strategy tables
    Release strategy without classification
    • T161I as described above.
    • T161E Release code and Description
    • T161S Release indicator
    • T161G Assignment to release indicator
    • T161F Prerequisites
    Release strategy with classification
    • T16FG, T16FS as described above.
    • T16FH description of the release group
    • T16FT description of the release strategy
    • T16FC Release code
    • T16FD Description of the release code
    • T16FV Prerequisites and actions
    • T16FK Assignment to release indicator
    • T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
    • T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
    Other tables are
    EKBE History per Purchasing Document
    EKBZ History per Purchasing Document: Delivery Costs
    EKKN Account Assignment in Purchasing Document
    EKPA Partner Roles in Purchasing
    EKPB "Material Provided" Item in Purchasing Document
    EKPV Shipping Data For Stock Transfer of Purchasing Document Item
    EKRS ERS Procedure: Goods (Merchandise) Movements to be Invoiced
    EKUB Index for Stock Transport Orders for Material
    EBAN table has fields for release status and indicator.
    To See the tables
    goto Transaction SE11, in the field Table click F4, Click on Information system
    In the applciation Compnnets enter the following & execute
    MM* Materials Management
    MM-CBP* Consumption-Based Planning
    MM-PUR* Purchasing
    MM-SRV* External Services
    MM-IM* Inventory Management
    MM-IV* Invoice Verification
    MM-IS* Information System
    MM-EDI* Electronic Data Inter
    MM-FT* Foreign trade
    OR
    goto SE16 Click F4, You have two options Information system & Sap Applications.
    Click on SAP Applications & selec the application you wnat to see, for E.g Purchasing you can click on materials managemnt, Purchasing if you drill down you will see the list of tables....
    http://help.sap.com/saphelp_47x200/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Check release stratergy with and w/o classification
    Thanks & Regards,
    Kiran

  • Mm pr-po release strategy : error

    Dear MM experts,
    We already having MM-rel strategy for PR & PO with classification procedure and working fine,
    Now business requirement is to change the MM-Rel PR& PO strategy,
    New mm-rel strategy for PR customised in class 032  (not to use existing release groups & release strategies) 
    After doing config settings in customising client, the request moved to another client for testing.
    Testing client, request moved successful, and while checking the settings in testing client,
    in Release Strategies - details mode
    Informatination is available at Release pre-requisites, Release Statuses without any error,
    but when we try for Classification, we are getting the following error
    "Error in classification (class PRREL class type 032)"
    Can u please suggest what needs to be done so that we can go ahead further.
    Kindly note while doing config setting client, we did not encounter the above error, it has accepted all the settings (copy existing rel group & having differnt rel strategies, etc)
    pl help
    Thanks in advance
    Srihari

    Hi Friends,
    My requirement is to add new release strategy for pr & po.
    Characteristics & Class are remain unchanged.
    Pl advise to how to proceed, i mean
    i have to set/create new release procedure, ie.,
    New release groups
    New release codes (bcos new codes are added & release levels remained same)
    New release strategies
    How i can retain the Old PRs & POs released with earlier release strategy/release codes?
    PRs & POs not released can be with new release strategy,  but i have to ensure the old prs & pos (released) were with earlier release strategy & release code.
    Also, I need ur advise, how the new release strategy works for workflow
    pl help
    thanks & regards
    Srihari

  • PR release strategy for material group

    Hi,
    I have 2 different line items in PR with 2 different mat groups. How can I set up a release strategy for this scenario. Ex-line No 1 has mat group X and line item 2 has mat group Y. Do I release at header level or item wise release is possible

    Hello
    In PR you can set up this release strategy without classification release strategy.
    w/o classification strategy you can define the release line item wise. so you can give diiff materual group you can enter with line item wise.
    Laxman

  • Dynamic release strategy and static release strategy

    Hi,
    What is the difference between dynamic release strategy and static release strategy.
    What the customization setting required to activate dymanic and static release strategy.
    Thank you
    REgards,
    Yshu

    Dear Yshu,
    What do you mean by dynamic and static release strategy. In SAP, we don'y have this term.
    Please kindly give more explanation so we can help you.
    We only have with classification and without classification.
    Normally, release strategy without classification is used in R/2, and out of support in
    R/3. However the functionality still available in case you want to use it.
    You can not use Release without classification and Release with classification.
    If there is an entry present in Release Group table (T16FG-FRGOT), only release with
    classification can be used.
    If you are in R/3, then forget the release strategy without classification but just
    use the release strategy with classification as it had more flexibility than the old
    system design.
    Thanks
    Ian

Maybe you are looking for

  • App-v 5.0 Pre-cache error in VDI.

    Hello All,  I have a Citrix XenDesktop VDI Pooled Desktop (nonpersistent) deployment with Microsoft App-V 5.0 full infrastructure.  I was testing the pre-caching of my App-V 5.0 packages (%ProgramData%\App-v) as the Shared Content Store was not provi

  • Component for JSF Save as dialog Box

    Hi I would like to have a save as diolog box in my JSF based Web application I am using richfaces as the implementation.. Can anyone give some valuable points about how to implememt that..............

  • I Can't Update my iTunes on my Computer?

    It's with great disappointment that I say that my macintosh is apparently too old to recieve the new iTunes 10.7 update. Unfortunately for me,when I updated my iPhone to the new 6.0 version I wasn't aware that it requires iTunes 10.7 to sync my iPhon

  • Need a table with asset number and document number

    Hi to all experts. Im in a support project. There is an issue in the customized report the total expense for february is coming 10,322 dollars which is 322 dollars extra it should be 10,000 .but i see the table ANEP the value is 10,322 dollars,when i

  • Mail Server Woes

    Hey All, I could use some help debugging Mail on my Mac Mini Server (10.8.2 - All updates installed).  Two issues going on:  mail is not arriving in the inbox and outgoing mail sent from the server does not arrive at the destination - it doesn't matt