Release Strategy for PR--------Help is required urgently.

Hello all,
I have one severe problem in PR release strategy. Whenever we create a PR the Release is triggering but the name of the processer who will release this PR is not triggering. I have done the PO13, where the HR positions are maintained as per the release levels and PA30 where the SAP user ids of these processers is given. But still the processor name is not triggering. Is there any other transaction where we have to maintain certain data?? Kindly help me as this is an urgent issue.
I will be very glad and give points to all of u.
Thanks and Regards,
Umakanth.

Hi,
Please check whether the relevant HR authorizations are given or not, especially relating to Org. management.
This is not only for the approver but also for the person viewing the requisition.
Hope this helps..

Similar Messages

  • Release Strategy for Sales Order-IMP

    Hi Gurus,
    I want to know regarding <b>Release Strategy for sales orders</b>. I want to know the detailed step-wise procedure for SO and not for PO. My understanding is that standard SAP does not support Release Strategy for SO in SD Module. Please l want the following queries to be answered
    1) Is my understanding on Release Strategy for SO correct as mentioned above?
    2) What are the other alternatives and the steps of configuration step-wise.?
    Kindly help me post this information as it is required urgently. Suitable full Reward Points will be given to all answers.
    Many Thanks,
    Pankaj Mishra
    E-Mail : [email protected]

    Pankaj,
    There is no release strategy for sales order.
    You can try it doing Authorisation /Status  profile with your BASIS person...
    REWARD IF U FINDS THIS AS USEFUL...
    Regds
    MM

  • 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 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 in sales order is required before MRP run

    Hi Experts,
    My requirement is Release strategy in sales order is required before MRP run. My client is doing the following process:
    1) Creation of Sale order (MTO).  Ex: User creates 10 sale orders per day.
    2) MD04- Stock Requirement List. All 10 Sale orders should be displayed. So no problem here.
    3) MD50-Make to order-Planning . Here when user gives the sale order number and sale order item and press enter, then only the released sale orders should be allowed and the rest sale orders it should throw a error message and it should not allow to process further.
    How this situation can be addressed in SAP.
    Kindly post some hints and comments.
    Regards,
    Kiran.

    Hi Kiran,
    Define and Assign status profile BS02 at sales order detail (line item) lets say with create and release status
    SD>Sales>Sales documents>Define and assign status profile
    Have create status as default while creating SO with item
    And do a user exit change for MD50 with ABAP consultant help and release it when user keys in SO and item.
    For other line item I believe it will give an error
    Pls try and update if it solves your requirment
    Regards,
    Siva

  • Release Strategy for a new material type in PR

    Dear Friends,
    One of our client require new Release Strategy for a particulat material type PR. Can u pl provide me the steps to configure a new release strategy for PR for a particular Material type.
    Regards,
    Ask

    Hi,
    Create a Char for your material types in CT04(MARA-Table,Field-MTART) and assign the same to your Class in CT02.
    Then follow all the cusmozation path for your PR release startegy .
    For Config part refer the below wiki link it may help you.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
    http://wiki.sdn.sap.com/wiki/display/ERPLO/ReleaseprocedureforPurchaseRequisitioninMM?focusedCommentId=195723808#comment-195723808

  • Release strategy for goods reservation.

    Hi Experts,
    I have client requirement for developing a custom release strategy for goods reservation in MM since there is no such strategy available in standard SAP.
    Would you please give some idea on how to go about it?
    Thnx in advance.
    Sudipto Choudhury.

    Hello Sudipto,
    Welcome to SDN.
    This is a really a large development and you need to talk to your MM consultant about the Functional spec.
    AS you need to find the flow first.
    Hope you understand what I mean. Without FS it is not possible to help.
    Regards,
    Suvendu

  • 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 SA/Contract/PO

    Hi friends,
    Should we have different release groups and release codes in contracting/ SA/ PO.
    Because...
    I have maintained 4 characteristics in release strategy for PO _[ Comp Co, plant, porg, total net order value].
    But i want to maintan only 2 characteristics in release strategy for contract  [plant, total net order value]
    because the same is reflecting in contract config also.
    Is it possible..please help me frnds.
    Prabhu

    Hi Prabhu,
    Unfortunately you need to maintain characteristics of all possible values for company code and plant for contractsu2019 to subject the release.
    Wish that SAP would be more flexible with release of PO, Contract and RFQ but it does not.
    Regards

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

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

  • 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

  • Want to change my existing Release strategy for - PR, PO & Service Entry

    Hallow Experts ,
    Here i have a requirement to change the existing Release strategy for Purchase Requisitions, Purchase Order and Service Entry sheet. Already There are unreleased Purchase Requisitions and Purchase Orders in Production system with the existing Release strategy.
    1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
    2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my  service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
    thanks in advance.
    regards
    vb

    Dear Vikrant,
    1. My Query is Before making change in Existing release strategy, should I need to release all PR and PO with unreleased status.
    Sol:  Not  Required but , doing it is recomandaed
    2. In PO scenario is like this, we have 4 purchacing groups and 4 document types(ZLOC,ZIMP,ZSER,NB) in release strategy, we need to add one more purchasing group that is to be aplicable to my service PO(ZSER) only . so should I need to creat another stretegy for the same, or I can add in the same strategy
    thanks in advance.
    Sol: No Only thing you have to  do is that   go to your class 32 and   chek what is the charaterstic define for the purchasing group  copy it
    2 Now go to  Tr.code: CT04, give that charaterstic and go to change mode and give the additional Purchasing group there, and save it
    3 Now go to Release strategy where you want to add that Purchasing group, go to classification tab and tik that new purchase group ,  that  group will now in fact of release Strategy

  • Release strategy for PO on Payment terms..

    Dear friends,
    Is it possible to have Release strategy for PO on Payment terms.....
    I checked in CEKKO, no field availble for payment terms.
    Is there any other way..........
    Plz help
    Rgds,
    Navin

    Hi,
    You can append Communication Structure "CEKKO" and add Payment Term (ZTERM)
    Use User Exit "M06E0004" (Changes to communication structure for release purch. doc.)
    Function module "EXIT_SAPLEBND_002" (Changes to Communication Structure for Release of Purchasing)

Maybe you are looking for