Release strategy - item level

hii all
can some body tel me , how and where we have to configuration for PR release strategy at item overview level.
And the same item level release strategy is posssible to configure for PO also??
If not y what is reason???
Thanks in advance
SAP-MM

hi
> how and where we have to configuration for PR release strategy at item overview level.
http://www.sapstudymaterials.com/2008/08/purchase-requisition-pr-release.html
>And the same item level release strategy is posssible to configure for PO also??
hi we cant have itemised release for PO
logically thinking PR can have multiple item and no fixed vendors and even not sure for placing order
so the realing person will decide for the item to be purchase so it has itemised relase
now in PO ,u will raise PO only when u have confirmed the purchase and the order will be for one vendor
so for ordering u have to relese the whole po,
or u can say u will create PO for all the items which have to procure so release will be for whole PO
go to spro>MM>Purchase Requisition>Release Procedure  read the left side help for WITH and WITHOUT CLASSIFICATION
Edited by: Kunal Ingale on Mar 9, 2010 6:32 AM

Similar Messages

  • PO release at item level

    Hi all
    Is it possible to release PO at item level.
    Our requirement is as follows:
    We have a field in material master of each material to be checked before PO can be released.
    The PO price should not be greater than the value in the material master field for each material.
    Is there any way to do this.??
    Thanks in advance
    JOE

    Hello all
    Thanks for your responses.
    The industry is contract manufacturing  where we quote raw material cost also to customer.
    Actually this price is stored in the material master accounting 2 field.
    While creating the PO , buying price should not exceed this price.
    So we have a user exit to check the prices and give an error message.
    In some situations like short lead time for FG from customer, they agree for higher price of raw material because of short lead time.In this case higher authority need to approve the higher PO price.
    any suggestions.
    Thanks
    jo
    Edited by: Jo George on Jan 5, 2009 9:08 AM
    Edited by: Jo George on Jan 5, 2009 9:10 AM

  • PO Release process item level control

    Hi,
    Please guys any way to control  Release process at item level based on account assignment any configuration or user exit or bapi.
    JACK

    Hello Jack,
    Addition to my previous response, here is the step by step process to define release procedure.
    http://www.sap123.com/showthread.php?t=59
    When you maintain characteristic, consider the OSS note which I mentioned in my previous thread.
    Hope this helps.
    Regards
    Arif Mansuri

  • Release Strategy- two levels getting released at the same time

    I have created PR release startegy using 4 levels of $$.
    The first level (L0)is $0.00 to 1.00
    The second level ( L1) goes from 1.01 to 500.00 etc
    The level2 and 3 work fine but the problem I am running into is when I release level L0 the system automatically releasaes level L1 along with L0.
    Has anyone seen this before? what am I doing wrong.
    (my original system had L1, L2 and L3 and that worked fine but I had to add in L0 for buyre review so I created lower level dollar limit and I am now running into this dual release problem)
    Need ideas/ help thanks
    Raj

    Hi,
    Please check settings for release prerequisite in PO release strategy for L0 & L1.
    Regards,
    Manish

  • Release Strategy for Contract

    Hello Experts
        I am using release starategy for contract and using communication structure CEKKO in characteristics. I want to use other parameter such as material master number (MATNR) for characteristics. I see that CEKKO has component .INCLUDE (Communication Structure: PO release for User Exit). Does any one know how to use it in characteristics and if I use it can I design release strategy for particular materials?
    Thanks
    Ankit

    this has been discussed multiple times on this forum - "Release strategy at item level for purchasing docs - PO/SA/Contract" not possible...
    refer below threads
    Why release strategies for PO at header level only
    PO Release Strategy
    Release strategy - item level
    yogesh

  • Item level release

    Hi experts,
    what is mean item level release and header level release in PR. How to configure it.
    pls explain in detail
    regards
    arun

    Hi,
    Release Procedure
    Use
    You use this component if you wish to set up approval procedures for purchase requisitions or other purchasing documents. Under such a procedure, if a purchase requisition or external purchasing document fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving (clearing, or giving the "green light" to) a proposed item of expenditure is replicated in the SAP System by the "release procedure".
    It is sensible to define separate release procedures for different groups of materials for which different departments are responsible, and to define separate procedures for investment goods and consumption goods.
    Which Documents Can be Released (Approved)?
    Release procedures can be defined for the following documents:
    ·     Purchase Requisition
    ·     The external purchasing documents purchase order (PO), contract, scheduling agreement, request for quotation (RFQ), and service entry sheet
    Release Procedure for Purchase Requisitions
    Two different procedures are available for requisitions:
    ·     With classification
    With this procedure, requisitions can be released both at item level (i.e. item-by-item) and in total. The latter approach is also termed "overall release".
    ·     Without classification
    With this procedure, requisitions can only be released at item level.
    Release Procedure for External Purchasing Documents
    External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
    Regards,
    sasi

  • Item Level PR Release

    Dear all,
    I am using PR release at Item level,  I have 2line items in my PR i have  refused 1 line item & approved the other, now when i m creatin the PO from that PR it still shows both the line items...
    system should show only the released line items..
    please guide
    cheers

    Dear,
    As per my view, When you create purchase order with reference of purchase requisition system take both line item which you given.
    But if you want to restrict the creation of purchase order for not released line item of purchase requisition.
    Make Message no. 06055 as error message number via sap config.
    For do this follow bellow path.
    SPRO -> Material Management -> Purchasing -> Environment Data -> Define Attributes of System Messages
    and make it as error message.
    Regards,
    Mahesh Wagh

  • Precautions to be taken before going for new PR Release strategy

    Dear all,
    We are going to implement release strategy with classification at item level release. Current process in our company release strategy without classification at item level release was implemented and its Production for past 3 years.
    Need your advice on
    1)If we go for new release strategy as off  with existing release strategy -what are the precautions to be taken before implementing new strategy - any problem will happen to existing data with old releases, which already release, yet to release?
    2)Once after implementing the new releases, the PR with old release strategy (which is not release yet)u2026does this will trigger new release?
    3)Any other which I missed out, please suggest me
    Thanks
    RS

    Hi,
    It is better to release all existing PRs using your current procedure without classificaton and clean up.
    If you impliment procedure with classification, It depends on the parameters like Plant, value, purchasing group you are going to use in the strategy. Also you may decide whether to have overall req release or item level release of PR by having diffrent release groups.
    REgards
    Ram
    Edited by: ramachandran subramanian on Feb 18, 2009 7:00 AM

  • PR Release by Item Not Triggering

    Hi SAP Experts,
    Went thru the forums on this release issue but could not seem to find the solution for my problem.
    I've configured the release strategy for PR (to be released at item level). This PR is basically auto generated after the user entered a Sales Order when they changed the item category.
    The following characteristic are being used for this specific class (which have been pre-created as this is being used for other release strategies).
    Acct Assignment cat (CEBAN-KNTTP)
    Item Cat in Purchasing Doc (CEBAN-PSTYP)
    Document Type (CEBAN-BSART)
    Plant (CEBAN-WERKS)
    Creation Indicator (CEBAN-ESTKZ)
    Total Value of item (CEBAN-GSWRT)
    Material Group (CEBAN-MATKL)
    Purchasing Group (CEBAN-EKGRP)
    I have 2 different release strategies set up due to different levels of approval.
    Strategy 1 - Department Manager (for value less than 100K)
    Strategy 2 - Department Manager and General Manager (for value 100K and above)
    As for the value of the classification, I did not specify all the characteristics.
    Acct Assignment cat - Cost Center (K)
    Item Cat in Purchasing Doc - blank
    Document Type - ZRR (customized)
    Plant - P101 to P110
    Creation Indicator - blank
    Total Value of item - based on the above criteria
    Material Group - ZG1
    Purchasing Group - ZGL
    All values above are already ensured that they are allowed values, and I have assigned this release strategy in CL24N.
    When I ran the simulation - the release strategy works fine as well.
    However, when I wanted to do a test run by creating SO which leads to PR auto creation - the release strategy does not work.
    It prompted a message of ME297 in the PR document. Tried to go to ME54N and it shows message MEPO822.
    Thanks in advance.

    hi,
    Once check your relarse values in cl20n, cl30n,
    in spro->Materials Management->Purchasing->Purchase Requisition->Release Procedure->Procedure with Classification->Set Up Procedure with Classification in that exigute and remove the over all release check mark.
    and in
    spro->Materials Management->Purchasing->Purchase Requisition->Define Document Types
    in that do execute for your document type please remove the over all release tick  and save.
    Thanking you.

  • PR Release Strategies - Item Value & PR Value

    I have this requirement from user. For marketing department, they want to release PR base on total PR value whereas Supply Chain want to release by item level.
    I have created 2 classes and the only different is the characteristic whether to use PR value or PR item value. The other characteristic is CREATOR_USER_ID.
    In release group for class with PR value, I have ticked the 'OverReqRel'.
    Now the problem is that the one with PR item value work fine, but the PR Value is not working.
    What could go wrong?

    hi
    you should have two release strategy.
    combining the Creator Item Value one and
    The creator and PR value one.

  • PR overall release strategy (with shared PR document types)

    We are asked to configure 'overall' PR release for some of the plants of our client.Now ,we know,  this needs to be configured in two places in SPRO. One, in release group definition & two, document type (PR) definition. Our issue is that the doc types involved here is shared by some other plants as well who doesn't need 'overall' release. Is it possible to configure the requirement without disturbing the unwilling plants ?

    Hi ,
    The PR release strategy can be done at Item level also ,which has to be set that the PR has to be released at item level and after doing it ,all the item values can become characteristics values for the release strategy
    The Plant can be taken as one of the characteristic.
    The view CEBAN gives all the related views.
    check the below LInk for Futher information on the same.
    http://www.scribd.com/doc/531679/Release-Procedure-for-Purchase-Requisitions
    hope so it helps
    Regards
    Anjanna.

  • Customizing steps of workflow for Release strategy

    Hi Experts,
    Iam looking for step by step customizing details of workflow for Release Strategy for Purchase Requisition.
    I need necessary classification and Customizing settings for a release procedure in the purchase requisition to the workflow.
    I am looking for the steps, in which the purchase requisition can be edited straight from the workflow inbox.
    Regards
    Nani

    Hi Nani,
                First you have to confirm what kind of release it is in Purchase req you have Item level release and over all release.
    Item level release - WS00000038
    Over all Release - WS20000077
    Now please confirm with your MM consultant that he has done the release Strategy and tesed it Ok.
    Escecially things like assigning plant, Assigning Agents,Release codes and so on when everything is done by him in SPRO.
    Now your work starts If it is just release use the standard workflow.
    If they need additional notification mails and things like that copy the standard workflow and do the customization in the copied version and deactivate the standard workflow.
    You can also do dead line monitering (Factory Calander) and many more things.
    also please go through these 2 links you will get better idea.
    http://www.****************/Tutorials/Workflow/POReleaseStrategy/Details.htm
    http://www.****************/Tutorials/Workflow/PRRelease/PRRelease1.htm
    If you have any othere queries please feel to ask.
    Regards,
    Dheepak
    Edited by: dheepak on Dec 1, 2008 7:48 PM

  • Reset contract release strategy ME32K

    Hi Gurus,
    I need to reset the release strategy of the contract everytime some value on the item screen EKPO got changed.
    I've already implemented the EXIT -> EXIT_SAPLEBND_002, but it only changes the header EKKO with the structure CEKKO.
    Please help me ASAP.
    Thanks.

    For PR's, there is no header level data. Because vendor number is optional since it is internal document .
    If you are releasing all line items at a time, need header level release.
    If you release line item by line item, need item level release.
    But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
    That's vendor number is at header level field and line item in the PO are related to the single vendor.
    You can release all the  items in the PO or u can reject entire PO, not a single line item.
    That's why, only header level release is possible for the PO/Contract/SA.
    Other  than this information  please  for through this  link
    PO release at item level ? | SCN

  • How to disable the link for Credit -check at item level

    Hi Experts,
    I have an issue tht we want to make a block to the link available for
    credit-release at item level. In the view of the item, when we select the item
    in edit view we have a button saying MORE and in tht we have CHEC CREDIT RELEASE.
    We want to disable this.
    I found tht if we made some changes in do_prepare method, we can solve this issue.,but i was
    check fi anyother way we can do it.
    Awaiting for the replies.
    Thanks,
    SA

    Hey Saurabh,
    If you dont want the functionality occurred due to that button, just simply comment the event handler code for that particular button. That will definitely help.
    Let me know if that work.
    Regards,
    Shobhit

  • Service Entry Sheet Release Strategy

    Dear Friends,
    We are re-configuring Service entry sheet release strategy. My client wants 4 level release strategy like ,
    Level 1 (0-10 lacks )
    Level 2 ( 0-50lacks)
    Level 3 (0-100 lacks )
    Level 4 (> 100 lacks )
    I have created release group, with release object3.
    I have created 4 release codes and 4 release strategies.
    We have so many departments like commerciual, safety, HR, Projects.
    My client wants only 4 codes to be created. My problem is that, how each and every department’s HOD can release SES ? How I can control SES of his department to be released by him ?
    Please help.
    With Best Regards,
    Rajesh

    Hi,
    I've configured release strategy department wise(HOD's)
    For that you need to create new characteristic for Tracking number.
    You can enter tracking no such as HR,PRD, PUR etc.
    Now maintain these tracking no in classification.
    Release will work as per respective HODs.
    Seems bit lengthy but I found it very useful.
    Try it.
    Regards,
    Piyush

Maybe you are looking for

  • Can't iChat, can't SFTP

    I don't know what's up with my Airport Extreme but I think it is the problem behind my inability to iChat from any computer in the house, and my inability to SFTP (SSH) files to anyone like I used to. Heck, I can't even remote login to my dad's route

  • Missing bluetooth opt

    missing bluetooth option on my laptops, how can I go about it.

  • Itunes could not connect to iphone because pairing record is missing???

    I have just upgraded to iphone 4s from iphone 4 and when i connect it to my itunes i get the message "itunes could not connect to iphone 'iphone' because pairing record is missing. Any clues what i've missed??? Also my when i try to backup my iphone

  • HRMS Self Service User Comments

    Hi Experts, We need to capture user comments displayed in either the REVIEW or the APPROVAL Self Service page for reporting purpose. Checked HR tables and Workflow Notification tables, but was not able to find these user comments data. Thanks in adva

  • Need Intel HD display driver for my Satellite A660

    I recently have tried to use Windows Movie Maker, but get error message to say the Intel HD driver installed is blocked. (version 8.15.10.2014). When I try and update via the Intel updater am told cannot update as Operating Manufacturer has configure