PR RELEASE STRATEGIES-Details Unseen it SPRO

Friends,
Over the time period there are several RELEASE Gropus & associated RELEASE Strategies also for PR in our scenario.
PR is also picking right RELEASE Strategies on item level basis.
However isse is that there are few RELEASE STRATEGIES picked up by RELEASE CRETERIA which I cannot see in SPRO config screen where we define / see release strategies...
However release strategy / rel Grp details are there in TABLES...
Then why system is NOT showing details of All RELEASE GROUPS / Rel codes / Rel indicators & Rel strategies which are so far configured till today in a client.
What can be possible de-link in system?

We can see release startegy customizing in the following path
SPRO -> Materials Management -> Purchasing -> Purchase Requisition
-> Release Procedure
under this Release Procedure -> Procedure with Classification ->
Check Release Strategies  we can check whether the basic settings
for our  release strategy are complete and correct
Please review the SAP note  365604  'FAQ: Release strategies in               
purchasing' which describes all the prerequisites for a release strategy          
to be determined correctly.                                                                               
If on the other hand, the release strategy you have defined for                   
purchase requisitions is not being determined by the system please check          
the following:                                                                               
1- Go into transaction CL30(N) and enter the values of the document and           
click on the button 'find in initial class'. If you do not get a result,          
check the customizing if there is a release strategy which matches the           
values of the document.                                                                               
2- If you get exactly one result, it is an indicator that the                     
   customizing was defined correctly. Then check:                                                                               
2.1  Is there a userexit activated (see note 365604 for the user              
         exit name)? If yes, check if it contains the magic line (for             
         purchase requisition: E_CEBAN = I_CEBAN)                                                                               
2.2- For purchase requisition, the overall release flag has to match          
    the one defined in transaction OMEB for the document type.                                                                               
3- If there is no release strategy determined after the implementation            
of a support package and you use a userexit, check note 435150.                   
4- Check in the customizing if the characteristics were entered in the  
internal format (e.g. the cost center must have 10 characters with      
leading zeros), see also note 365604, point 2b).                                                                               
5- In case the item category is used as a characteristic, check that you
use the internal format defined in OMH4.

Similar Messages

  • T code to get the detail of release strategies for all purchas groups?

    Hi,
    Is there any  T ode that i can run a report and get the current details of release strategies for all purchase groups exist at the moment?
    if so pls let me know
    or else how can i get that information?
    highly appreciate all of your assistance in this regard?
    thanks in advance
    Regards
    Sasika

    from T16FS you can only get which strategy are present.
    Which strategy you have can already be seen in the PO or requisition.
    But you are looking for the person. this is not really easy, as this can be more than one person.
    A strategy has the information what release code is needed.
    And this release code is in a role which is then assigned to an approver.
    So the only way would be to execute SUIM and then roles by authorization values.
    there you enter the authorization object M_EINK_FRG (hit enter) then you have to enter the release group and release code.
    Execute. SAP will list all roles that grand the authority to release order with this combination.
    in this list you can click another button to see the users that are assigned to this role.

  • PO release strategies

    Hi all,
    A requirement arose in my company, to get all the details of PO release strategies exist now.
    That is, when you consider a single department we identify that department in SAP by purchase group code allocate for that particular depaartment. At the same time there are few level in a particular purchase group like 0 to im value category , 1 m to 5 m value category, 5 m to 10 m value category, etc, etc.
    now it is a company need to collect all the data relating to release groups, that is who are the responsible people that are having the authority to approve each and every value categoryfor all purchase groups.
    there is no other way that i can see rather than collecting these information manually which will take atleast 3 weeks time if i do only this job,
    but if i can find the tables where the data is stored  i will  be able to write a small programme and collect the required informaion
    what are the tables related to SPRO  PO   release strategies
    Your assistance in this regard is highly appreciated
    Regards
    Sasika

    Hi ,
    Customizing Tables
    Release strategy without classification
    u2022 T161I as described above.
    u2022 T161E Release code and Description
    u2022 T161S Release indicator
    u2022 T161G Assignment to release indicator
    u2022 T161F Prerequisites
    AUSF Characteristics Value
    Release strategy with classification
    u2022 T16FG, T16FS as described above.
    u2022 T16FH description of the release group
    u2022 T16FT description of the release strategy
    u2022 T16FC Release code
    u2022 T16FD Description of the release code
    u2022 T16FV Prerequisites and actions
    u2022 T16FK Assignment to release indicator
    u2022 T16FB (purchasing documents), T161S(Purchase requisitions), T16FL(Service Entry sheet) is the release indicator
    u2022 T161U(requisition), T16FE(purchasing document), T16FM(service entry sheet) are the descriptions of the release indicator
    Regards,
    Anupam

  • Are these requisition release strategies common?

    All,
    I’m designing new requisition release strategies for indirect requisitions at a chemical industry client.  I’d like to know how often you have seen the following sorts of design before:
    Existing design: Item-based release with workflow, with three dollar levels.  At the lowest levels, two strategies for each cost center approver (the one used is based on whether the desired vendor is foreign or domestic).  Characteristics assign several cost centers to each approver.  Strategies and codes are named for users, so we change configuration whenever someone changes jobs.  The codes are linked to positions, which are attached to user IDs.  Result: about 80 release codes and 140 strategies, taking a lot of time to maintain.
    Current redesign: Overall release, using 6 strategies and 6 codes based on dollar level and foreign vs. domestic.  A user exit selects the approver for each code from a custom table that stores the user IDs for each cost center, with a custom maintenance transaction for the table.
    Now the client wants both individual approval by cost center owner and items with different cost centers on a single requisition combined with approval of the overall purchase.  I’m considering item-based approval of requisitions, with the user exit and custom table, and adding overall approval of indirect POs with the overall approvers.
    Thanks for your help!

    Hi,
    No-Requisition release strategies are not common, one need to design release strategies based on business requirement. Release strategies looks simple after designing but its design needs creating thought to it.
    In your case, you can go for designing redesigning release strategies for Overall release with using 6 strategies and 6 release codes. Considering you have configured release strategies with all release values for PO document type ,PO value and Purchasing group. Now design a custom table and go for followings:
    Client---Pur Group--Rel Code1-- Rel Code2-- Rel Code3-- Rel Code4-- Rel Code5-- Rel Code6
    The search help is required to pull in purchasing group details from T024 table and SAP user ID from Table USR01
    Concept: Create Purchasing Group (OME4) as Department & assign the Department name to Cost center (KS01).
    For more refer a discussion:
    PR release: place holder for Cost center and Material grp
    NOTE: User training required crate requisition for one department only where only one cost center involved- No requisition creation allowed for multiple cost center.
    You can also go for other concept designing of your Requisition release strategies
    Regards,
    Biju K

  • Purchase requisition : problem with check release Strategies

    Hi all,
    i created a new class, new release group, new release codes etc. I think all is ok but when i launch the transaction OMGQCK for check release Strategies the system give me an error in node 'Check re release indicators' : Define a release indicator for the status "released".
    But how can i do that, i created two release indicator : 'X' for blocked and 'V' for launched but what are the options for purchase requisition ?
    Is there a special value to give the release indicator 'released' ?
    Thanks for your help.
    Edited by: ToraTora on Mar 31, 2011 5:46 PM

    Hi,
    Goto SPRO -> Materials Management -> Purchasing -> Purchase Requisition -> Release Procedure -> Procedure with classification -> Setup Procedure with Classification
    select release indicator
    by default, you will be having the following release indicators in the system,
    1     Request for quotation
    2     RFQ/purchase order
    3     RFQ/PO no change of date
    4     RFQ/PO no changes
    A     Fixed RFQ
    B     Fixed RFQ/purchase order
    X     Blocked
    please check whether you have got these or else create and then assign them to the release strategies.

  • Stop Re-triggering of PR release strategies for closed PR's.

    Hi,
    Scenario is like, PR raised and converted it into PO and material has been received.
    After Receipt of material, system is allowing to change the quantities by un-releasing the release strategies.
    Once material receipt is completed, system should not allow to change in / revoke the release strategies.
    Please suggest.
    Thanks in advance.
    njs

    hi
    plz check ur release indicator in spro >mm>pur>pr>rel>
    here select the rel indicator and check the changability option in bottom it has to be 6
    hope it help
    regards
    kunal

  • RCCLBI01 and Purchase Requisition Release Strategies

    I'm trying to use RCCLBI01 to load Release Strategies.  I've found a few threads on it but they don't tell you what you can and can't do with it.  I know I can load the characteristic values for an already existing Release Strategy, but I have hundreds of Release Strategies that I need to create. 
    Will this load the strategies as well, or do I really have to go create them by hand in SPRO first then run it?  Or is there another program that will load strategies and the codes and the characteristics?

    Kris,
    RCCLDI01 is now used. However Here's my view:
    1. You will have to create chracteristics to begin with. I hope the number is not huge as it will narrow down the functionality otherwise.
    2. The class-- How many would you create?? I don't believe you would need a Batch input program to create a class as I believe there could not be more than a handful, unless necessary
    3.Now the classification.. the buggest task of all, where you could run in to hundreds.. Maintaining them is a nightmare and you'd have to have your strategies first.. I do not know of any input program to create Release strategies. So my answer is "a manual task"
    4. RCCLBI02  is of no help here for release strategies.
    5. I would rather use TCODE: CLMM to do the mass changes.. it makes life a lot easier.
    6. The last option is for some one technical to help you create a script to load the data.

  • Transport of release strategies

    Hello all
    Could anybody explain me how to transport release strategies (classification)? I found the note 45951, but is not clear for me.
    First, how do I have to save the changes on SPRO-Material management-Purchasing-Purchase requisition-Release procedure-Procedure with classification-Set up procedure with classification-Release strategies? I tried with menu Table view-transport is this correct? if not, how do I have to do?
    Then, when I have a transport number which are the following steps?
    Could anybody help me?
    Thank you in advance.

    Hi Henrique,
    The transport of Customizing data in the release procedure area 'Release strategies' can only be used in a restricted manner. The 'Transport' function displayed in Customizing under 'Table view' only takes the
    release strategies into account but not the dependent data of the release prerequisites, the release statuses and classification data.
    If you want to transport release strategies, proceed as described below:
    1. Transport of release strategies (entries in table T16FS)
    Use the transport function Customizing under 'Table view' -  'Transport'.
    2. Transport of Release prerequisites (entries in table T16FV)
    You can display all required entries of table T16FV which contains the release prerequisites for the corrresponding release strategy using the table display Transaction SE16 specifying the release group to be transported and the release strategy. Implement these table entries manually in a transport request.
       Program ID:                   R3TR
       Object type of the element:   TABU
       Object name:                  T16FV
       Client                           Client
       Release group                 Release group
       Release strategy              Release strategy
       Release code                  *
    3. Transport of Release statuses (entries in table T16FK)
    You can display all required entries of the table T16FK which contains the release statuses for the corresponding release strategy using the table display of Transaction SE16 specifying the release group to be transported and the release strategy.
    Implement these table entries manually into a transport request.
       Program ID:                     R3TR
       Object type of the element:     TABU
       Object name:                    T16FK
       Client                          Client
       Release group                   Release group
       Release strategy                Release strategy
       Release code                    *
    4.  Transport of classification data into release strategy
    Read Note 45951.
    Transport class type 032 (release strategy), the class, which you use for the release procedure, and the characteristics which are assigned to this class.
    >> Above instructions extracted from note 86900 <<
    Hope it helps to solve the issue!
    Cheers,
    Eduardo Junior

  • Regarding PO release strategies

    Hi Guys,
    During implementation, I came across one senario where some input are required.
    I am having certain release strategies already configured in SAP, based on,
    - PO Type
    - PO Net Value
    - Plant
    Now I am suppose to add one more criteria, for release strategy i.e.,
    - Purcahse Organisation for some of the document types only (which are newly created by me). Also existing release strategy should not be affected.
    - Now I have created 5 document types, out of which release strategy is required only for 3 document types and that is also only based on Purcahse Org. not any other criteria like value or plant etc.
    Please suggest me, how should I go for such case.
    (Business senario, is like for generating Import orders they have certain Purcahse Organisation, and only for that Purcahse Orgenisation, client wants certain relases should be there) w/o changing existing one.
    Thanks,
    Hetal

    Hi
    I guess you already have the Characteristic for BSART( Document type), Add the new document types in the Char Values which you wish to have in rel stg.
    Create onr more Char for EKORG and link it to Structure CEKKO
    Now you have all the new and old characteristcis.
    In CL02 first remove the BSART char which was previously assigned, and re_assing the same since it needs to pick up the new additions to it. Add the new characteristic which you have created  for EKORG.
    Are you going to assign the new valuesin old Rel strategies or would like to go with new one? If old one then check for the Classification value assignments for all your characteristcis for in each Rel stg.
    If New then it should not be problem as you can newly assign the details inside the classification.
    How-ever Please re_check all the Old/new Rel stgs and the values assignment inside the classification as during new assignemnet sometimes the old values goes out. Please chck ifyou find so then correct it.
    Best Regards

  • Release strategies to PO

    Dear friends !
    we will use release strategies to Purchase orders with standard workflow only to send a message to user (into tcode SBWP).
    I have configured release strategies and put it on field " Workflow"  the value " 1"Role resolution with group, code, and plant (T16FW) and  also put at the " Workflow " specific  , the Object Type = US and the userid = BRAZILA(logon to SAP).
    But after we save the PO no message has been sent to Users.
    does anyone knows if are necessary others customizing settings ?
    Which settings and tcodes are theses ?
    I´m looking for more details inside SDN but no specific transactions were available and easy to understand until now.
    Best regards,
    Ale

    Dear friend Thx for your answer
    Do you have any BPP to config this ?
    Any documentation general about this configuration!
    best regards
    ale

  • Delete Release strategies for PO that has been delete

    Hii SAP Expert,
    I'm facing this problem whereby there are Purchase Order that have been inactive which mean the line item for the Purchase Order have been deleted. The concern is the release strategies still appear in ME29 for PO that have been deleted.
    How do i remove this PO from the release strategies ?

    Dear Nikamz,
    Check to the PO item detail , if the delivery complete indicator and final invoice indicator is ticked, then the release strategy will remain in document although you already delete all the PO line items, try to untick the indicator and then unreset the delete indicator and delete the item again, see whether the release strategy still exist, also you may try to check notes : 527995(run report  ZKSTAPO1 to update the STAPO field).
    Regards,
    w1n

  • PO release strategies with Contract

    Hi,
    implementing a PO release strategy (SAP-MM module)I need to consider the case in which a PO is assigned to a Contract.
    If so, different release strategies should be selected according to the PO value.
    Possible cases:
    S0-strategy 0: Contract does not exist, PO value>=0eur
    S1-strategy 1: Contract exists, PO value>=100eur
    S2-strategy 2: Contract exists, PO value>=200eur
    Is someone aware if it is possible to activate such release strategy without defining manually in the characteristic for CEKKO-KONNR field all possible contract single values (entire range)?
    Thanks a lot for helping!
    Regards,
    Elisabetta Rizza
    Please contact me at following mail addresses:
    [email protected]
    [email protected]
    Hi Elisabetta,
    I've moved this here because it is a more appropriate thread.  BPX is the place for discussing the role of the buisness process expert.  This is a MM question
    Message was edited by: Marilyn Pratt

    Dear Amit,
    Requirement: If GR posting date exceeded 45 days than delivery date set in PO, then delivery date in PO has to be changed to current system date and at the same time New Release Strategy (B1) has to be triggered with one release code (02) automatically.
    So in that case the values in Release Strategy (A1) and (B1) would remain same,,, as you suggested we will assign the value 01 u2013 USRC1 to Rel Strategy (A1) and 02 u2013 USRC1 to Rel Strategy (B1) and the same we will try to incorporate in the coding of Exit u2018'M06E0004'
    We will check the process and confirm the same.
    Thanks for your suggestion.
    regards,
    Urendra Kumar

  • Block creation of PO if the release strategies is not applicable

    HI SAP,
    Can we block creation of PO if the release strategies is no applicable ?
    My release strategies is on the PO header. It's only work if the PO have one Plant only. If the user put more then one plant
    my release strategies will not work. how to solve this problem ?

    Hi,
    Check on it:-
    http://www.sapfans.com/forums/viewtopic.php?f=6&t=205684&start=0&st=0&sk=t&sd=a
    Re: Release Strategies in Purchase Order - possible values of caracteristics
    PO Release strategy question
    pherasath

  • Release Strategies in Purchase Order - possible values of caracteristics

    Hello,
    I have the following situation at hand.
    We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
    Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
    I can not change the caracteristics in the Release strateg because this would affect the already working strategies  and SAP does not allow to asign another Class to the PO release groups.
    Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
    Can I use something generic in the caracteristics field of the strategy?
    Thanks for any help. It would save me a lot of time!
    Aart

    Note 493900 - FAQ: Release Strategy
    1. Question :
    Why is the release strategy not determined?
    Answer :
    Please check the following points :
    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 use version management, the determination of the release strategy starts when the version is completed.
    You complete a version by setting the "version completed" indicator in the version tab.
    Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
    This is true for the other structures as well (CEKKO and CESSR). See note 52225.
    For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
    For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

  • Purchase Order Release Strategies for Changed Amount

    Hi Gurus,
    We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
    Example: Configuration is PO total amount <$5K requires only L1 approval.  PO total amount >$5K requires L1 and L2 approval.  PO was created for $8K and was release using L1 and L2 approvals.  Receipts were posted to PO in the amount of $7K.  Now the buyer has added an additional line item for $1K.  The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item).  Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
    Has anyone done this before?  Any ideas??
    Thanks,
    Gabe

    from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
    User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
    This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
    The following user fields are available:
    USRC1
    USRC2
    USRN1
    USRN2
    In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

Maybe you are looking for

  • Now my iPod touch won't work

    I previously posted about an error that occurred when I updated my daughter's ipod touch, 1st generation to 2.1. Here is the post: Error 0xe8000001: My daughter recently purchased an 8G refurbished ipod touch. Prior to upgrading to 2.1, her ipod conn

  • TechTool Deluxe resulted in failures

    I ran TechTool Deluxe on my MacBook Pro, and "Format Check", "Directory Scan" and "Volume Structure" resulted in failure.  I was unable to proceed with fixes.  Can anyone advise me?  Thank you.

  • Printing to local print device from WEBGUI

    Hi SAP expert Got a question regarding WEBGUI priniting. In SAPGUI when you select print to LOCL, it print to the PC default print device, but if we print via a WEBGUI screen, the printing output to a PDF file first, we can then print from the PDF fi

  • I can't get my iphone to located by bluetooth, what should I do?

    I can't get my iphone to locate my bluetooth device.  What can I do?  It just keeps searching.

  • EIS 6.5.1 - Drill through report

    Hi all,Is there any limitaion on number of fields in the EIS drill through reports. It seems it accepts only 10 columns, rest of the column data is not properly displayed.