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

Similar Messages

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

  • Are these newly released iPods going to come down 33% in 2 months too?

    You may want to old off on buying the new ipod or you'll be the one screaming on hear.

    I am extremely disappointed with Apple on this price reduction some 60+ days after launch.
    Send apple some official feedback using this form.
    http://www.apple.com/feedback/iphone.html
    They need to here it loud and clear on all channels. Unfortunately they are deleting posts and threads at an alarming rate.

  • PO release startegy "common issue"

    if release strategy cirtera contains item level characterisitc then if po contains multiple line item with differnet values agains that char. then system does not blocks the PO and for time being let us say PLANT / MAterial group as char.
    now this issue is encountered by every one but i could not find the solution for this (i know the reason behind this issue but i dont know the precise solution some consultants say to maintain the blank value in char  value but i dont think system accepts blank value for char like plant/material group)
    i hope to get some soild reply

    so finally this is the solution for the issue
    Unfortunately there is no mechanism like entering a blank or * in order to make classification understand this characteristic is not relevant.
    The characteristic and its values will always been taken in consideration.
    In case you use a 'non-aggregated' field in your release strategy you need to enter all possible values for the corresponding characteristic (as a range - just in case of numeric characteristics).
    Example: You use item-wise release strategy for purchase requisitions
      and the plant is used in the release strategy (characteristic
      CEBAN-WERKS).
      Release strategy determination will be processed item by item.
      There will always be just one value for the plant (from the current
      item), multiple values and thus aggregation is not possible.
      In this case you have to enter all possible values for the
      characteristic CEBAN-WERKS.
    In case you use an 'aggregated' field in your release strategy (which is possible for overall release strategy for PRs and release strategy for POs) and multiple values are used for that field on a purchasing document, you can use a blank value for the corresponding characteristic if you'd like the release strategy be applied.
    Example: You use release strategy for a PO and the plant is one of the
      relevant fields (characteristic CEKKO-WERKS).
      You enter a first PO item with plant 0001 and a second item with plant
      0002.
      Since there are multiple values for the plant the system will
      'aggregate' to blank value and use blank value for searching for a
      release strategy.
      Since you have maintained a blank value for characteristic
      CEKKO-WERKS the system will find the corresponding release strategy.
    In this case please pay attention to note 732566.
    It causes an error in case blank values are used for release strategies.
    Even when the long text just talks about process orders the impact of the side effect is more general.
    Please take care note 754178 is implemented, it corrects note 732566.

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

  • Release strategies for purchase requisitions

    Hello,
    I'm having trouble with profiles and roles for release strategies, this is the scenario:
    -for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
    My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
    Many thanks
    Daniel

    HI,
    Not necessarily, you just need a different strategy for each different combination of release codes involved.
    So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
    Or however many different variations you have.
    Steve B

  • TS3274 Videos won't play.  Not YouTube or any other videos.  I also have no sound.  Are these common failures for a three year old gen 2  iPad?

    Videos won't play.  Not YouTube or any other videos (just started today).  I also have no sound, keypad clicks, shutoff click, etc.  Are these common failures for a three year old Gen 2 iPad?

    For the issue with the videos that will no longer work, try closing all apps and then reboot the iPad.
    Tap the home button once. Then tap the home button twice and the recents tray will appear at the bottom of the screen. Tap and hold down on any app icon until it begins to wiggle. Tap the minus sign in the upper left corner of the app that you want to close. Tap the home button twice.
    Reboot the iPad by holding down on the sleep and home buttons at the same time for about 10-15 seconds until the Apple Logo appears - ignore the red slider if it appears on the screen - let go of the buttons. Let the iPad start up.
    For the issue with sounds, you have system sounds muted.
    Check the side switch above the volume rocker on the side of the iPad. Flip it the other way and see if you get sound from the apps, keyboard clicks, etc.
    If not, double tap the home button to bring up the task bar at the bottom. In the task bar swipe all the way to the right. Look on the far left side and see if there is a speaker icon. If there is, tap it and see if the sounds on apps come back. Then tap the home button.
    You can change how the side switch works to either lock screen rotation or to mute system sounds. You can go to Settings>General>Set Side switch to Lock Rotation or mute. If you choose mute, the switch will turn off apps sounds. Otherwise you use the task bar as described above to mute those sounds.
    This support article from Apple explains how the side switch works.
    http://support.apple.com/kb/HT4085

  • Tables for Release strategies

    Hi ...
    I was referring to MM table doc , in that it is mentioned table EBELN & EBELP are for Purchase Order header / Line and BANFN & BNFPO are for PR header/ Line.
    But for release strategy ...people told me to refer CEKKO for PO and CEBAN for PR.
    does it mean that release strategy refers to different tables for execution ( and I believe these tables are used for release strategy purpose only and if Yes then at what point PO / PR data gets updated in these tables)
    Regards
    Suresh

    Hi,
    Please find release tables used in MM.
    EKAB       Release Documentation 
    EKEH        Scheduling Agreement Release Documentation 
    EKEK        Header Data for Scheduling Agreement Releases 
    T161E       Release Codes 
    T161F       Release Point Assignment for Purchase Requisition
    T161G       Release Prerequisite, Purchase Requisition 
    T161H       Fields for Release Procedure, Purchase Requisitio
    T161I        Determination of Release Strategy 
    T161S       Release Indicator, Purchase Requisition 
    T161U      Texts for Release Indicator 
    T163P        Release Creation Profile 
    T163S        Description for Release Creation Profile 
    T16FB        Release Indicators: Purchasing Document 
    T16FC        Release Codes 
    T16FD        Description of Release Codes 
    T16FE        Descriptions of Release Indicators: Purchasing Do 
    T16FG        Release Groups 
    T16FH        Descriptions of Release Groups 
    T16FK        Release Statuses 
    T16FS        Release Strategies 
    I think, it will help u.
    Ishu

  • 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

  • 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

  • Function Module giving pruchase requisition release code ?

    Hi everyone !!
    I am using the FM BAPI_REQUISITION_RELEASE_GEN in order to realease a purchase requisition, this works well as I give it a hard-coded value for input parameter REL_CODE.
    However in our company an intricate set of release strategies imposes that I should have a dynamic value for this release code.
    So I've been looking for a function module that would return the possible values of the release codes with either the requisition number as input or other parameters found in table EBAN !
    Anyone has any suggestions as to which FM or BAPI I could use to achieve this goal?
    Best regards !
    Ced

    Even i passed only currency then also i got the below errors.
    1-> No instance of object type PurchaseOrder has been created. External reference:
    2-> PO header data still faulty
    3-> No master record exists for vendor 100017
    4-> Vendor 100017 does not exist
    5-> Can delivery date be met?
    how to rectify these errors. Is it any functional problem or data passing problem
          header-comp_code = wa_dbtab-bukrs.
          header-doc_type   = wa_dbtab-bsart.           "Standard Order
          header-creat_date = sy-datum.
          header-vendor     = wa_dbtab-lifnr.
          header-purch_org  = wa_dbtab-ekorg.
          header-pur_group  = wa_dbtab-ekgrp.
          header-currency = wa_dbtab-currency.
    *POPULATE HEADER FLAG.
          headerx-comp_code  = c_x.
          headerx-doc_type   = c_x.
          headerx-creat_date = c_x.
          headerx-vendor     = c_x.
          headerx-purch_org  = c_x.
          headerx-pur_group  = c_x.
          headerX-currency = c_x.
         headerX-currency_iso = c_x.
        ENDIF.
    *POPULATE ITEM DATA.
        item-po_item  = wa_dbtab-item.
        item-material = wa_dbtab-matnr.
        item-plant    = wa_dbtab-werks.
        item-matl_group = wa_dbtab-mat_grp.
        item-quantity = wa_dbtab-menge.
        item-net_price   = wa_dbtab-netwr.
        APPEND item.
        CLEAR item.
    *POPULATE ITEM FLAG TABLE
        itemx-po_item    = wa_dbtab-item.
        itemx-po_itemx   = c_x.
        itemx-material   = c_x.
        itemx-plant      = c_x .
        itemx-matl_group = c_x.
        itemx-quantity   = c_x .
        itemx-net_price  = c_x.
        APPEND itemx.
        CLEAR itemx.

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

  • Release Strategies not works - When multiple material group in a single P.O

    Hai,
    This related to Release Strategies in SAP- IS -Retail.
    The Material group was one of the character in the Rel Strgy. 
    1) If i create a P.O for the item which is related to " X" material group , Rel Strgy been set to P.O
    2) If i create a P.O for the item which is related to " Y" material group ,  Rel Strgy been set to P.O
    If I combine material group "X' & "y" in a same Purchase order , then RELEASE STRATGY NOT BEEN SET TO P.O .
    How to make this as possible in SAP -IS-Retail - Version 6.0
    Thanks,
    PS

    Hi,
    Generally it is not advisable to use item level characteristics for overall release . Please refer the sap note 493900
    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.
    you have to maintain blank value in CT04 for material group and the same thing must be maintained for all strategies.
    The release procedure for purchasing documents is carried out on header level. For this, the following values are aggregated from the items on header level:
    item value
    plant
    material group
    Example WERK:
    The plant is only aggregated on header level if all items contain the same plant. If only one alternative plant exists, ' ' is aggregated on header level.
    A release strategy is then searched for with this value.
    Of course, a corresponding strategy is only found if the value ' ' was maintained for the characteristic 'Value' as an object value.
    The same functionality applies to the  plant

  • Active release strategies

    Dear SAP GURUS,
       Is there a transaction code where i can have a look at all the active release strategies.
    Thanx,
    Fayazuddin Syed.

    Dear Syed fayazuddin ,
    You can figure it out at CL24N or CL20N.
    Example :
    Transaction CL24N
    Class        => Fill in class name  
    Class Type :     032
    If it was active, then you will see
    status field = 1     Released and with the "Green Tick" icon.
    or else:
    2     Locked
    3     Incomplete
    Sometimes, if you are having inconsistency/corrupted for your release strategy, you will also see some
    message indicate that you had inconsistency in these transaction
    Thanks
    Loke Foong

  • Restrcuturing of PR and PO release strategies - corporate policies

    Hello,
    I´m in a proyect where a multinational company wants to restructure its PR and PO release strategies.
    We are in the fase of defining corporate policies as guidelines for the new structure.
    The multinational Holding contains Productive companies, distribution companies and other type of companies like investigation companies.
    I would like to have some feedback about how to guide the company management in this process off defining corporate policies.
    How does one or can one estandardize the release levels, release codes and amounts which separate the levels, in a diverse multinational.
    Are there any paradigmas, methods to acomplish this.?
    If anyone has experience with these kind of processes, please give me some feedback on how they tackled these issues.
    Thanks,
    Aart

    Hi,
    Normally when a company is coming into the sap , which have many business at various locations / countries , a structure will be defined in the SAP for the company as company code under which the plant and below the structure will be defined .
    However when comes to purchasing and for PRs POs , SAP give a communication strusture called CBAN for PRs and CEKKO for POs which can be viewed at SE16 . Thease tables contains the fields upon which the release strategies can be made .
    For example , say for one of your productive company , the company code created is XXXX and the plant under which is YYYY say , the policy can be for a groups of buyers which comes under the plant for a PO level , who can be the approver . Here for differrant PO/PR values differrant approvers can be added as strategies and based upon which the approval can be happened . and the approvers be the release codes .
    There are no standard paradisms rather , prior come into purchasing the organization structure be made.
    After that based upon the business/product , with in that company code defined , the levels can be defined in that perticular business .for purchases .
    In purchasing , to fhe plant / purchase group / storage location etc plays important and normally for a set of buyers/p grps , in that plant or group of plants in that company code , the levels of the PO/PR values can be defined for differrant strategies .
    Once at corporate level , the company code / plant is defined and under that the release strategy is easy to define .
    Regards,

Maybe you are looking for