How to setup a release strategy for store generated purchase order

Hi there,
Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
Greatly thank for your help.
Kind Regards,
2tea

Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
PO RELEASE STRATEGY
The release code is a two-character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
e.g. If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
CT04 - Create Characteristic e.g. NETVALUE
Click Additional data Table name CEKKO Field name GNETW and press enter
(for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
In the Basic data (X refers to tick),
X Mutliple values
X Interval values
In the Value data, in the Char. value column, type >10000 and press enter
Save your data
CL02 - Class
Class - Create REL_PUR
Class type - 032
Click Create
Description - Release Procedure for Purchase Order
In the Same Classification section, click Check with error
In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
OMGS - Define Release Procedure for Purchase Order Type
Release Group - New entries
Rel.group Rel. Object Class Description
02 REL_PUR Rel. Strategy for PO
Release codes - New entries
Grp Code
02 01
Release indicators
Release indicators Release Description
0 Blocked
1 X Release
Release Strategy
Release group 02
Rel.strategy 01
Release codes 01
Release status 01
Classification Choose your check values
OMGSCK - Check Release Strategies
(make sure there are no error messages)
Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
The person with the release authorization have to use ME28 to release the Purchase Order.
Regards,
Ashok

Similar Messages

  • Release strategy for MRP generated PR.

    Dear friends,
    Can we have release strategy for MRP generated purchase requisitions.....
    What are the steps required if yes.....
    Plz. suggest....
    Thanks in advance
    Navin

    HI,
    IF you want to characteris MRP genrated PR then you have to define different document type other than the standrad one.
    For this MRP define the release stratergy has usual procedure.
    In case if ou dont have a different document type also the standard release procedure which you have conffigured will hold good.
    Thanks & Regards,
    KIran

  • Release strategyu for contracts and purchase order

    Hi,
    My client want both contracts and release orders (purchase order created w.r.t contract) must to go to release approval before procuring the material or service.
    Is it possible to configure seperate release strategies for contact and purchase order?
    Please let me know.
    Thanks in advance.
    Regards
    Kishore.

    Hi,
    Thanks for your replies.
    Characters for contract will be
    1. Company code
    2. Aggreement type
    3. Target value
    4. Purchase group
    Characters for Purchase order will be
    1. Company code
    2. Dodument type
    3. Net value + VAT(Gross value)
    4. Purchase group
    BASED ON THE ABOVE CRITERIA, PLEASE LET ME KNOW HOW TO CONFIGURE. Release strategy for purchase orders already existing in the system as mentioned above as per the mentioned characteristics. Now i need to configure for contracts only.
    Please help me in this regard.
    Regards
    Kishore.
    Edited by: Jyothula Kishore on Feb 2, 2010 7:37 AM
    Edited by: Jyothula Kishore on Feb 2, 2010 12:01 PM

  • Release strategy for PR generated through  network activity (Project)

    *Hi,
    I am facing the problem that  PR generated through  network activity (Project) does not have release strategy attached. For same combination of characteristics value of  PR document type , account assignment, release strategy strategy is attached for PR created manuelly.
    Please suggest
    Regards.*

    What is the account assignment used in Network generated PR, Have included that in your characteristics? Is PR in Your defined document type?

  • How to get the loaded cost for the Parked Purchase Order Invoices.

    Hi,
    Could any one of you please help me out to find out how the loaded cost is calculated for Parked Purchase Order Invoices which have not been posted. The problem is that if the invoice is posted the ekbe-wrbtr field contains the total amt for any particular line item, i.e. the (material cost + unplanned costs + taxes ).
    But for the documents which are not posted ekbe-wrbtr does not have all the key data fields as that of a posted document. Is there any way out to find the total cost for the line item which is not posted.
    Please try to help me..
    Thanks & Regards,
    Sanjay.

    in that case u have to get the document amt of that accouting Document of PO invoice.
    how --->
    get the IR number from EKBE
    CALL FUNCTION 'FI_DOCUMENT_RECORD'
        EXPORTING
          I_AWTYP            =  'RMRP'
          I_AWREF            =  W_AWREF1----->IR of Po
          I_AWORG            =  W_GJAHR1----->year
        I_AWSYS            = ' '
        I_AWTYP_INCL       = ' '
        I_AWTYP_EXCL       = ' '
        I_BUKRS            = ' '
        TABLES
          T_DOCUMENTS        = T_DOC.--->here u get the accouting document number.
    Regards
    Prabhu

  • Release Strategy for reservation created from PM and PS

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

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

  • Reset Release Strategy for any change in the Purchase Order

    Hi,
    Is it possible in SAP standards to reset release strategy for even minor changes in the Purchase Order irrespective of whether it is value change or any change in the text or Purchasing group change or whatever it is?
    If so, where do we need to make the configurations.
    I have seen in some thread about resetting the release strategy for decrease in Purchase Order value.Even that was possible through some BAPI.
    Thanks in Advance.
    S.Raghavan

    hi sandesh,
    sorry, i know it's too late.
    i tried your suggestion, it works blocking the purchase order after release strategies are setted.
    sandesh, raghavan:
    i need to reset the strategies after to make any change in the po. i'll appreciate your help if you can give it.
    regards
    f

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

  • Release strategy for GR?

    Hi,
    My company has requirement that GR should be subject to approval process before it can be posted. As far as I know there is no standard functionality in SAP for this (at least in ECC, as in SRM there is one).
    Has anyone encounter this before? And how you deal with this? I have tried to persuade the user to drop this, but the problem is they already have this functionality in their legacy (which is custom made web based application), so it is pretty hard to argue with them in this area.
    Any help will be appreciated.
    Best regard

    Hi Yosea,
    Yes you said is right that there is no Release strategy. And can't imagine the situation in the legacy as well for this approval process thru Release strategy while doing the GR. But there is another way of accepting the goods either partial or full using movement types, you can do so.
    My question is why do you (i.e., your client or company) want to control (through the approval process) at Goods receipt level. That makes complex and un logical as well, thats why there is an approval process comes into picture at PO (Purchase order is an external purchase document and is going out to an external party /vendor /supplier) against that they can supply the material /provide the services to the Organization/company and is required to control before issuing this perticular document called PO (i.e., work order and is required to be controlled thru Electronic release strategy in SAP) instead of manual before in legacy since there is money matter involved and needs to control over investment on Inventory /services purchases.
    But where as GR, this is an incoming document, what the meaning in controlling it through approval process. That is the way you have to conveincene the client or company.
    Ok fine. If still they want this functionality to be implemented (that is to controlling at the GR level for the goods coming in. Then there is another way to control it through receiving the stocks into different stock types using the respective movement types, but not through Release strategy such as Blocking (GR blocking), Quality stock (for checking the quanlity standards thru Quality Inspection) and then later you can move these stocks to Unrestricted use stock, so that this can be allowed to use further.
    I dont think there is a functionality in the SRM as well. As I know that you can receive the Goods in SRM through Online Desktop confirmation that too partial or full quantity, that is nothing accepting/approval for the Partial or full quantity that is received against the PO which is created wrto to respective Shopping cart. And that is how you can control the goods that are coming inside / received at Stores/WH inorder to maintain the good quality of Inventory.
    Note: Controll always suggested at the time of making agreement  (i.e., Release strategy for the PO) but not at the time of receiving the goods. Here while receiving the goods only thing that a Stores person can see tmainly is needs to check for the Quantity, Quality of the goods that are ordered, Delivery time, Mode of transport, Shipping instructions, etc. This will help them further in evaluating the vendor.
    Hence there is no logic is going for that option
    Hope it clarifies,
    Regards,
    Sapsrin

  • Release strategy for quantity contract

    Hi Gurus,
    In quantity contract ..  target value will not filled by the value(in header details) as it is quantityt contract.
    We may have different line items with different cost..
    my doubt is how the release strategy will be triggered for the quanityt contract and how the system will consider the whole value of the contract..
    please explain/clarify
    regards
    subbu

    Hi,
    The release strategy for the contract will work in the exact mechanism as for the PO i.e. it will be determined  based upon the total net value of the entire purchasing document.
    Cheers,
    HT

  • Release strategy for Schedule lines in SD

    Hello All
    Can we create a release strategy for Schedule Lines in Scheduling Agreement? If Yes How?
    I have already maintained a release strategy for Item Level... which I want to put it for Schedule line as well....
    Thanks in advance.

    Hello,
    I think you are in the wrong forum. Please choose the right forum category and post it there.
    Matthias

  • Release strategy for Scheduling Agreement(SA)

    Dear Forum,
    This issue is with regards to the release strategy for Scheduling Agreement(SA)
    Until now release has only been applicable to contracts at our client site. But we now plan to introduce it for SA as well. Such a feature is available in SAP but the problem is that with the given release strategy GR is not allowed until the release is affected. The system allows you to post the delivery schedule.
    Now what I want is that after making the SA the system should not allow to make delivery schedule if release is not affected.
    We also have MRP run at client site..Kindly suggest the procedure as, how to configure it.Are der any User Exit for the same,if so please discuss..
    Warm Regards
    Nainesh
    SAP ECC 6.0

    Hi,
    What's the SA Type that was created via MRP.
    If it's LP (without release document), release will not do anything BUT
    If it's LPA (release document), then you will not be able to Post the GR until release is affected.
    Thanks.
    Scheduling Agreement can be categories as
    1) LP (without release document) and
    2) LPA (with release document)
    If use LP, you can do GR without release but with LPA, you need to release the schedule line via ME38.
    Thanks.
    NanoSAP  
    Posts: 58
    Registered: 1/5/09
    Forum Points: 6 
       Re: release strategy for Scheduling Agreement(SA)  
    Posted: Jun 26, 2009 8:32 AM    in response to: sathish.kumar           Reply 
    Dear Mr.Satish,
    Thanks a lot for your earliest reply...But my point is i want the system should not allow to make delivery schedule if release is not affected...Though schedule lines are generating through MRP run...Is is possible,by any chance...??

  • Purchase Order not subject to release strategy for contract rel. strategy

    Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
    So I have checked this release strategy with this codes:
    CL24N ok,
    CT04 ok,
    CL30N ok,
    CL20N ok,
    Release simulation in release strategy works,
    Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
    Thank you for your help in advance.

    I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
    I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
    Also compare your release strategy settings with many existing documents in SCN.
    Check your Classification should be like that.
    You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

  • Retriggering Release strategy for PR with Document Type, Company Code and Price Range as Characaterstics

    Hi Friends,
    I have a issue to fix. The issue is releated to PR.
    There are some PR's in the system which has wrong release strategy picked up or wrong approvers picked up due to some congif change. now that the config changes are rectified correctly, we need to find a solution to correct the PR's which got affected due this.
    I have to retrigger the release strategy for all the affected PR's.
    The characterstics which we have consider for release strategy is Document Type, Company Code and Price Range.
    Can anyone suggest how can we retrigger the PR in bulk or individual to all the affected PR's, so that it picks up correct release strategy as per new config changes.
    Regards,
    Manjunath K

    Hi,
    Refer the discussion to triggers release again on release code addition/change in release strategy.
    release code is changed on PR release strategy - old PR can´t be approved
    Regards,
    Biju K

  • Release strategy for PO and RO

    Hi All
    My release strategy for Purchase order and Release Order is same.My release strategy has material group and PO/RO value as characteristics. What I want is that my releaase strategy for PO should be based on value whereas for RO it should be based on material group. Is this possible since we cannot have different release group for PO and RO.
    Pl suggest how to go about?

    HI Satish,
    In the characteristic value screen we not only can give single values ,but also multiple values
    and also range of values.
    Since the Data type for this Feild is character ,that is the reason it is not taking Ranges
    So the same is not working for PO,I too Checked the same.
    So it is that you have to have material group ,then there is no other go but entering all the values for the same.
    As we cant add a new Release Class also
    Becoz the release class cant be different ,so as the characteristic values would be same.
    if i could find something else will post you soon.
    but as of know we cant do nothing in this case but create all the material group as charecterics values and add to that strategy.
    Thanks
    Anjanna.

Maybe you are looking for

  • Will I loose apps and settings if I move to Family Sharing instead of using one Apple ID?

    I am looking at setting up Family Sharing.  I currently have all of the families devices under my apple ID.  If I create new accounts for each member of the family, will they loose all the apps and data on their devices?

  • Prblem with Switch step in BPM

    Hi all, I have a problem with a switch step in my BPM. The condition on my BPM is that I have an xpath and that should have a particular constant value. If true, then proceed or else passs through the otherwise branch. The success branch has a transf

  • WIKI: Mapping Concepts in SAP XI

    Hi all, I have posted a WIKI for the mapping concepts in SAP XI, where you could find the details of various blogs and other links regarding the mapping concepts in SAP XI. Please refer this link: https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi

  • USB interface pressure sensors

     Hello all! I've recently acquired a DigiTacts pressure array sensor like those depicted in the following link: http://www.pressureprofile.com/products-digitacts Has anyone already worked with these sensors using LabView?  The interface is USB.  Will

  • Missing cables.....

    Missing cables.....< ?This is a current subject of EXTREME frustration for me. A whille back I purchsed an X-Fi Elite Pro sound card on a special deal with Creative HS-900 headphones. A month or so later I went ahead and purchsed the X-Fi I/O Consloe