Release strategy for PR in Third party case

Hi,
We have this third party scenario where Purchase reqs are created at the time of Sales Order creation. A release strategy is attached to these purchase req by defining a custom field in MMaster, whenever qty goes up or equal to tht field release strategy is applied.
The problem is, for the same material's PR, the release strategy is set in one case whereas for other PR (of different sales order) it is not set. Please help let me know what could have gone wrong.
Thx.
Amit

Per your information you say that based on a custom field qty in material master release strategy is triggered. Do you have any charecteristic maintained for the Release strategy anything other than this parameter- because there must be some difference between the 2 Reqs.
Or check the change history in Material master it may be possible that at the time of second sales order if the field value was changed so that release strategy was not triggered.
Please give more details
Thanks
Deepak

Similar Messages

  • 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

  • Problems with Purchase Req.no in relation to Third-party-case

    Hi,
    Im trying  to create a third-party-case invoice with Sales Order No. xxxxxxxx
    I'm getting  an error regarding missing Purchase req. no. (the customer's credit block had to be released).
    This concerns a product that we buy from Helsingborg as XXXX1 and we sell it in XXXX2
    one more question?
    From where the valuation price for PR (w.r.to SO) being generated is taken?
    Thnaks in advance
    Akkshaya

    Akkshya,
    Go to VKM1 Or VKM 4 and release the same..
    Ten try..
    REWARD IF U FINDS THIS AS USEFUL...
    Regds
    MM

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

  • Release strategy for Return PO

    Hi,
    Can we create Release strategy for Return PO's. ?
    Regards
    Sunil

    Hi,
    The process for return PO is:
    Process:
    - Create a return PO
    - Create a outbound delivery
    - Goods issue
    Release Strategy can be created for All Document Types as Document Types being one of the determining factors for Release strategies. So under Classification data Characteristics which we maintain determine the release strategies for a Particular Purchasing documents. Actually it depends on your Business case that for what all documents you want to have a release strategy config.
    regards,
    Prashant Rathore.

  • Cannot reset release strategy for RFQ

    Dear SAP gurus,
    I set release procedure for RFQ. I set anyway that the changeability is 6, and the tolerance is zero. I expect that after it is released, whenever anyone is changing everything the release strategy will be reset.
    But this is not happening. In my case, the manager already approve the RFQ but the RFQ has not been sent yet. Then someone change the quantity of the RFQ, and the release strategy is not reset. When I check again I realize that changeability 6 means the release will be reset if the value is changed; while in RFQ there is no value mentioned anywhere, it means that the release strategy for RFQ will never be reset.
    Do i miss something? Is there any way to make sure that the release for RFQ is reset if someone change anything in the RFQ?
    Best regards,
    John.

    Why are you having a value based release in RFQ? And more important, why do you need release for RFQ?
    However, if you still want to go ahead with release, then you need to use the user exit for purchasing document release to achieve your objective. Please search for my earlier posts on how to reset release even on decrease of PO value. You can use the same logic for RFQ also.
    Lakshman

  • Release strategy for Future validity period- (Outline agreements)

    Dear All,
    I want to create release strategy for Scheduling agreement.But I am creating the SA for furure validity period.In this case how the release strategy will triger.
    E.g Today 09.03.09 I create a Sceduling agreement and the validity period I maintain is from 01.06.09 to 31.12.09 and Amount say 100 Rs.
    I am using Characteristics Doct type and Amount.. The system checks the rate as on date (i.e on 09.03.09) and since it doesnt find any value the Release strategy is not trigeering.
    How to set up release strategy in the above case.
    Thanks in Advance.
    Regards
    Amar

    Hi Amar,
    1) if you maintain a target value (EKKO-KTWRT) in the header of the            
    contract this value is the basis for the determination of the release          
    strategy. If the target value is 0, the system will cumulate the               
    values of the items and will use this value for the determination.                                                                               
    2) So if the target value is 0 and you change the price of a condition         
    with a validity period in the future the system will react in the              
    following way:                                                                               
    Example:                                                                       
       the contract contains one item with quantity = 100 and a net price          
    of EUR 5,-.                                                                    
       all contracts with a target value from EUR 0 - 1.000,- should be            
    subject of a release strategy                                                  
       the contract is created and released on October the 1st                     
       ME32K -> October the 2nd you define a new price of EUR 7,- with a           
    validity period from 03.10.09 - 30-10.09 -> you save the contract              
    -> the release strategy is not reset, as the start date is not                 
    reached yet (system date < startdate of validity period)                       
       ME32K October the 3rd you change a field in the contract -> the             
    release strategy is reset                                                                               
    This is system design that a release strategy can only be reset through        
    an action by the user. The determination of the release strategy can't         
    be triggered automatically in the background.      
    If you create a document which is subject of an overall release strategy      
    (e.g. p.o., contract) the determination of the release strategy takes         
    place when the user hits the 'save' button or chooses the 'check'             
    function.                                                                     
    So there must be a kind of event that tells the system that something         
    has changed.                                                                               
    Regards,
    Edit

  • Release strategy for PR with multiple item category

    Hello,
    I'm trying to create a global release strategy for a PR based on the item category.   I have defined a caracteristic with different item categories (A and K).
    If I create a PR with item category A, the correct strategy is triggered as well as for an PR with item category K.  The problem is when I create a PR with 2 positions, one A and one K, there is no strategy triggered.
    How can I change my settings that there is also a strategy triggered in this case ?
    Thank you in advance for you help.
    Kind regards

    Hi,
    Solution is very small. Please maintain a blank entry too in the characteristics value. It will start working.
    Sanjeev

  • Release strategy for PR and PO

    I have release strategy for PR and PO, suppose there is 3 levels of Release, at second level I want to set an alternative Release code,  if either of the employee releases then it should go to third release.
    How to configure for PO (with classifications) and PR (without classifications). 
    I am not using workflow than how to do it ???

    follow the steps below.
    Release prerequisites should not be checked
    Release statuses do the following settings for alternate release
    based on your requirement
    you can make the release or blocked status manually in release config
    than it will work.
    without classification it will not work

  • Release Strategy for Condition Records

    Hi,
    This is a requirement from my client. The client needs to give 4 levels of release strategy for the condition records created. The selling price for the products will be entered by person 1. This has to be approved by the sales execute (person 2); then by the sales manager (person 3); finally by the General Manager (Person 4). The selling price of the products ranges from 10 lakhs to 40 lakhs. so, the release strategy is needed. This type of release strategy is available in MM for PR and PO. Please let me know whether similar facility is available in SD. Any alternative is also solicited.
    Regards,
    K Bharathi

    Hi,
    Thanks for your valuable reply.
    I defined 3 Processing status (Menu path: SPRO >> SD >> Basic Fn >> Pricing >> Define Processing status). They are EU-End user, KU-Key user, MD-Final authority. These processing statuses are assigned to Release status. First two processing status EU, KU were assigned to A (Blocked). The third processing status MD was assigned to Blank (Released). The purpose is: at processing status EU one person will upload the price master. Second person will check the price and will change the processing status to KU if he satisfies with the accuracy of the price master. The third person (final authority) will check the price and set the Processing status MD. Once the condition record gets the status MD, the prices can be used for creating sales order because it is released.
    In the condition record for PR00, when I enterthe processing status  EU or KU the release status shows 'Blocked' release statuses. When I enter MD in the processing status, the release status show 'released'.
    My question is how can assign the responsibilities of changing the processing statuses EU to KU, KU to MD to two different persons.
    Regards,
    K Bharathi

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

    Dear All,
    Can we have a Release strategy for the invoices ? Here my client wants to have approval for all the invoices irrespective of whether there is variation or not. They don't want to park & post option also.
    regds,
    CB

    Hi,
    For Inovices there is no release strategy but you can use
    If an invoice item containing a large amount is entered, it is advisable to initially block this invoice to check the amount, especially in the case of invoices that do not refer to a purchase order.
    In Customizing for Logistics Invoice Verification, you can define:
    Setting in Customizing for Logistics Invoice Verification
    If the invoiced amount should be checked then;
    Invoice Block>>> Item Amount Check>>> Activate Item Amount Check
    The purchase orders in which the amount should be checked in invoice items, depending on the item category and goods receipt indicator of the order item. then;
    Invoice Block >>> Item Amount Check >>> Set Item Amount Check
    The amount as of which an item should be blocked the ;
    Invoice Block >>>>Set Tolerance Limits.

  • 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 PO and Contract

    Hi,
    I maintain characteritic for PO
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    I maintain characteristic  for contract
    Company code
    Target Value
    Doc Type
    Purchasing group
    My class consist of
    Plant
    Doc Type
    Net Order Value
    Purchasing Group
    Company code
    Target value
    Q1: Do i need to maintain ALL characteristic value when i define my release strategy for PO or Contract as some characteristic only apply to PO only or contract only?
    Q2:  What option do i have if i need to maintain all characteristic value ? leave it blank ? empty
    Currently my PO release is working fine but when i try to maintain the contract release inside the class . my PO release is not triggering . I maintained diffrent release group for both PO and Contract .
    Thank for your advice

    First of all
    For purchasing like PO,pr,contract you can able to get in ekko table.No need to maintain separate release unless if it your business requirement.Take Document type as one of the characteristics it will distinguish whether it is PO or contract.
    You have to maintain all the characteristic value then only it will trigered release.
    Check the release indicator as well.
    Hope it will help.

  • 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

Maybe you are looking for