PR Release Strategy for MRP & Manually created PR

There is a scenario in which it's required when,
PR is generated automaticaly through MRP then Release strategt should be applicable and when
PR is created manually then release strategy won't be applicale.
Please suggest about this..........
                                                       Thanks in advance.

Hi,
You should have two document types ( as required by you here), MRP PR document type  & Manual PR document type.Link plant, MRP group and the default order types as MRP PR document type  in OMDT t.code.
You should create release characteristics (CT04) with the table & field and add all release characteristics in release class. For document type release characteristics with CEBAN & BSART and do not keep value ZNB which you do not want, just keep value ZMNB. During design of release strategy keep value only for document type ZMNB with other character values.
Regards,
Biju K

Similar Messages

  • Purchase Requisition Release strategy for MRP based Requisition

    Hello Gurus
    We want to set up the urchase Requisition Release strategy for MRP based Requisition ..Any can one Please share your experience about the impact down the road?
    Thanks
    Nick

    Hi,
    If you want include the MRP related PR in Release strategy.
    You need to include the field CEBANESTKZ-Creation Indicator (Purchase Requisition/Schedule Lines) in one of the characteristics which you create and include the characteristics value as per the field values like AReal time, BMRP, CConverted Planned order etc.. and include the charactristic in the Release Strategy will release group & release codes.
    So when ever the PR is created through MRP run then this creation indicator will update in the PR as per that release Strategy will trigger in the PR.
    there is one more option you need to create the separate document type as MRP PR then create document type as characteristics and include the values of all these document types and include in Release strategy.
    But it will  not pop up for direct PR from MRP run only trigger when planned order is converted to PR manually there you need to select this MRP document type then release strategy will trigger.
    I think first one is best suited.
    rgds
    Chidanand

  • 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 strategy for Release POs

    Hi Every one,
    We have a requirement.
    A contract is created and approved as per the regular strategy.
    The releases (POs) are created against it and sent directly to the vendor.
    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract.
    But the business wants the PO releases too to follow the release strategy.
    Can you please look in to this and let me what changes we need to make this happen.
    Regards
    Pavan

    As the Contract is already approved, standard SAP does not apply the release strategy for the POs created for the contract
    This statement is not correct, it's upto you to use or Not to use Release Process for release Orders (PO) created w.r.to Contract.
    As the table & fields are Common for both Contract & PO release ..you need to choose the PO relevant fields & values in the Release Strategy..
    So that the Release Process is applicable to PO's created w.r.to Contract also..
    For ex: if you use the field purchase Doc category as a Character  in  the Release , it differentiates whether it is PO or Contract..
    So that you can define different Release Strategy for PO & Contract
    Or  if you maintain the Doc type of PO in the Contract Release Strategy in CL20N / CL24N trxn code..
    then the release strategy applies to PO also..

  • Release strategy for manual reservations

    hi!
    Is it possible to have a Release strategy for manual reservations ? how?
    Regards,
    Rajiv Kane

    Dear,
    There is no release procedure exists for Reservations in SAP.
    1. Either remove authorizations for MB21 to the low level employees and give authorizations for CREATE / CHANGE / DELETE reservation trans to management only.
    2. Or else instruct inventory people to only make movements (issues) against the printed signed copy of reservation from the concerned manager. Only the user brings the reservation print with manager sign or seal, then only the material can be issued.
    Meantime, instruct the management to time follow goods issues reference to reservations timely.
    Regards,
    Syed Hussain.

  • Release strategy for auto created PO's

    Hi Guys,
    I have a requirement to implement release strategy for automatically created PO's.
    PR's are created automatically and we have a program which create PO's automatically.
    we would want to release them before generating output to vendor.
    could anyone please have any inputs here.
    regards
    mittu

    Hi!
    You may use your existing release strategy or create a new one (depending on your requirement). You just have to add/ use the document type you used for your auto-generated POs.
    Hope this helps! =)

  • Release strategy for PREQs created from PM work order

    Hi All,
    I have an issue with determining  release strategy for purchase requisition for external services created via PM work order (iw31 transaction).
    We have activated release strategy for Purchase requisition based on the following characteristics:
    CEBAN_PLANT
    CEBAN_COST_CENTER_GROUP
    CEBAN_MANUAL
    Characteristic CEBAN_COST_CENTER_GROUP is defined via user exit based on the cost center used in the PREQ and a z table which contains all cost centers mapped to the corresponding  cost center goups.
    In the user exit we have consider to cases:
    The first one is when a purchase requisition is created with account assignment K (cost center) then system is checking the z table and determines the right cost center group.
    The second case is when a purchase requisition is created with account assignment F (internal order) then based on the order type and number the cost center in the order is defined and based on it the corresponding entry in the z table cost center group is assigned.
    The third case is when purchase requisition for services is created automatically from PM work order. In this case the PREQ is again with account assignment F, but at the time when user exit is checking the input parameters the real number of the work order does not exist and system can not defined the other parameters.
    We have defined  for this requisitions in the release strategy for characteristic CEBAN_MANUAL creation indicator " F".
    Has anybody of you defined release strategy for PREQs created out of work order before. How did you manage to trigger the release strategy?
    Best Regards,
    Desislava

    Hi,
    For PM order find the costcenter in the settlement rule of the order or else find the costcenter in the Location tab of the order.
    Consider this filed from order & write in the Z program to pick up the costcenter from there to find out the cost center group.
    Regards,
    Raj

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

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

  • Release strategy for PR with materials having different prices

    Hai Gurus
    Can we make a release strategy for a variant configured material ?
    I mean create a strategy in such a way that price is critical factor and the materials what ever we choose for the PR has different characteristics dependencies like for example ( A chair having different characteristics like color, material ( like steel, leather etc) and other features like wheels etc and whatever characteristics we choose has a different price.......... so when v come to the release strategy it has to be approved by the next level if it reaches $ 1000 and so on.
    please help me out in this issue

    Hello Arif Mansuri
    thanks for your reply, yes I have taken it as total value only. The scenario is I am asked to use three different characteristics ( total value, materials, MRP Controller) and assign them to a class and if the customer picks any number of different materials and if the price is more than 1000 then it has to reach to the next level for approval. i thought i am suppose to use object dependencies here......... can we do this in a normal release order if so how would be the strategy played here?
    thanks for your time

  • 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 Contract is not getting picked whereas it is ok for PO

    Dear Experts,
    I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    Kindly resolve the issue.
    Satish

    S0004830404 wrote:
    Dear Experts,
    >
    > I have created release strategy for PO with doc type, p.org, net value as chars and frg_ekko as class and release group as 02.
    > I kept NB,FO,MK and WK as char values. it is working fine for PO's whereas it is not getting picked for Contracts. we need same release strategy for PO as well as for Contract.
    >
    > Kindly resolve the issue.
    >
    > Satish
    hi,
    use create other characteristic for value CEKKO-GNETW in this use the mk , wk values in value field and assign this characteristic to your class and save.
    Thanking you

  • 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

  • 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

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

Maybe you are looking for