P Req Release Strategy

Hi,
We have scenario in which there are lot of strategies based on P Req's created for Cost centres, Assets, Orders and P Req created via MRP etc. In each of them depending on the Total Item value, Creation Indicator, Plant and Account Assignment Release Strategies varies. So Characteristics of each of the above were created and assigned to Class.
The problem occured when one of the Release Group required Material Group in their Strategy. So the Characteristic for Material Group (CEBAN-MATKL) was created and asssigned to the Class. But now this Material group gets reflected in other Strategies and appears as blank and the other Release Strategy which worked well before does not work as the Material Group is Blank. We cannot define the Material Group in each of them because there would be enough Material Group and its rather cumbersome to define for each and eveyone.
How can i overcome this situation?
Sonu

Hi,
this will happen like this only. There is a sap  Note 47089 - Release procedure for purching docs - Aggregation that explains this for material group if used as one of the charateristics.
Summary
*Symptom
Release procedure for purchasing documents
No strategy is found if the plant and material group were defined as characteristics and no blank entry was maintained.
Additional key words
OMGS, ME21, ME22, ME23
Cause and prerequisites
Solution
The release procedure for purchasing documents is carried out on header level. For this, the following values are aggregated from the items on header level:
item value
plant
material group
Example WERK:
The plant is only aggregated on header level if all items contain the same plant. If only one alternative plant exists, ' ' is aggregated on header level.
A release strategy is then searched for with this value.
Of course, a corresponding strategy is only found if the value ' ' was maintained for the haracteristic 'Value' as an object value.
The same functionality applies to the material group as for the plant.
this will info will resolve your issue.
if still have doubts let me know.
Thanks and Regards
Rajesh

Similar Messages

  • Creating Roles for Purchase Req. release strategy with classification

    Hi friends,
    Since I have created Purchase req rel strategy where I have four release strategy
    1. For Plant 1 When value <= 5000 (Officer) will release , release code 01 release release strategy r1 and rel code L1
    2 For Plant 1 When value >= 5000 (Manager) will release , release code 01 release release strategy r2and rel code L2
    Now the manager will have 2 release code,if  officer is absent he could release the requisition.
    Same has to be done for plant 2
    The release Group and code needs to be assigned to the Roles , could anybody tell  me  where i could know about roles and will be able to create roles and assign authorisation objects to the Roles , and release group and code to the enduser.
    though its a basis job , since I have no idea , I mean I have never worked with Roles ,as now I have created the Release strategy with classification I need to assign authorisation objects to the Roles as I have four release strategy
    1. For Plant 1 lower value of requisition 1 codeL1(Officer)
    2  For higher value of requisition 2 code say Li and L2(Manager)
    Manager should have 2 codes if  officer is absent he could release
    Same has to be done for Plant 2
    Thanks N Regards
    Siddhartha

    Hii,
    Steps:
    1) Create a Role
    2) Add the authorization Object  M_EINK_FRG by taking the manual option
    3) Assign Release Code and Release Grp
    4) Assign the Role to the User ID which has the authorization of the Release Code and Grp.
    Regards,
    Kumar

  • Purchase Req release strategy help

    PR's generated from MRP are being blocked, however when I convert a planned order from MRP into a PR it is automatically released. I want MRP generated Reqs to be also released. I tried creating a new class, characteristic and strategy group but ran into problems when assigning the class to the group. Basically we just want all reqs created from MRP to be released and not go through workflow. Any ideas? My inital thought was to use the creation indicator EBAN-ESTKZ with the value of B (MRP) and U (converted planned orders)

    hi Ryan
    U can use only one release class in PR release strategy
    error is because ur trying to use another class add the charactaristics ib existing class and configure release strategy
    Vishal...

  • Purchase Req Release strategy - Requestor /Approver

    We want to skip the Approver to release his own purchase requisition without workflow set up.Is it possible in ECC6.0 ?. Any help will be highly appreciated
    Thanks
    Nick

    Hi Nick
    While configurating add P group as one of charactaristic.Then maintain values of all P. Group in this charactaristic
    While defining Release strategy Do not tick against Approvers P group which means release strategy will be skiped for him
    ( Release strategy--classification here u difine value for P Group skip P group here)
    Cheers!!!
    Vishal...

  • PR Release Strategy Characteristic Changes

    I created several characteristics for a purchase req. release strategy. I added an incorrect value and then deleted it on one of the characteristics. Is there anything else that needs to be done to ensure that value is really deleted?
    I'm receiveing an error when I ALE that I have documents that won't post for the error:
    REQ_PURCH_ORG : Value "Structure Exists " not found
    Structure exists is not a value associated with this characteristic.

    Thanks for the solution that helped me to understand PR Release much better.
    Values: Plant (WERKS)& Itemvalue (GSWRT) & Now I created (GFWRT) For another class for Overall PR release.
    In my PR Release strategy with 2 levels I have these below things:
    Rel Groups : 1 Group with name AA
    Rel Codes: For AA is A1, For another AA is A2.
    Rel Indicator: nothing is selected, am not sure what to do in this step.
    Rel Strategy : For AA is S1, For another AA is S2.
    I created class Z_GFWRT but am not sure which group I should assign  it AA or I have to create another new group for Overall release.
    After I checked the release strategy the system is giving me this below message.
    No release group exists
    Message no. ME_RELCHK014
    Please can you walkme through in this process. This is first time I am creating a PR Release.
    Thank you Very Much
    Imraan

  • P Req. Release Strategy not Transported

    Hi,
    For Configuring the Purchase Requsition Release Strategy, We have Created Characteristics and Class in the Configuration Development Client. Created Release Groups, Assigned Release Codes with the Release Group, and Assigned Release Group with Release Strategy with Classification. Tested PR Release Strategy for the given Classification Values the Release Strategy triggered.
    We have Created same Charateristics and Class in the Testing Development Client (Since the Characteristics and Class are not Transportable). Transported Release Groups, Release Codes and Release Strategy from Configuration Development Client to Testing Development Client. When we check the Release Strategy Classification in the Testing Developmemnt Client, system showing Classification Error.
    Please let us know whether the Release Strategy Classification Requests are Transportable or not.
    Ravi

    Dear Ravi,
    The Release Strategy Configurations can be transported, in respect to the requests transported.
    But the assignment of the Characteristic Values to the respective classes needs to be done in respective destination clients. Since teh assignment will get transported.
    To Do the same, please use transaction CL24N, Enter the classes Used in your release strategy and assign the respective Characteristics Values.
    Hope this will serve the need.
    Njoy SAP
    - Regards,
      Saravanaganesh

  • 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

  • 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

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • Release Strategy for New & Change PO's - Using characteristic CEKKO-REVNO

    Hi All,
    I have the following requirement/scenario
    1. If PO is created manually no reference to PR, then the PO needs to be approved through a release strategy.
    2. If the PO has been created automatically either from a req or through SRM (for,eg) then the PO needs to be approved only if this PO has been changed. So this would need to go through a second release strategy.
    To distinguish between the two, we are using Version number field CEKKO-REVNO in the communication structure CEKKO to be a characteristic in the release strategy.
    This is what I hoped for would work after doing the necessary config,
    For create PO's, in my classification I have CEKKO-REVNO as >=0. So any PO whose version number is >=0, will trigger relase strategy S1 (for e,g).
    For change PO's in my classification I have CEKKO-REVNO > 0 And whenever you change PO, it will generate versions 1,2,3 and so on, and hence the release strategy will trigger.
    The problem
    Whenever I use CEKKO-REVNO as one of my characteristics, the release strategy is not triggered at all no matter what the conditions are on the PO. When i removed the REVNO from my classification, release strategy is getting triggered as per plan.  I have also activated version management and done all the necessary config. I would like to know why release strategy is not getting triggered when REVNO field is used from communication structure CEKKO. Have any of you experienced this issue before??
    Is their any other identifier I can use to address the requirement above? Let me know.
    Thanks
    Ashvin

    Thanks Charlie for your response.
    The conditions in the PO is not equal.
    On one occasion when I create the PO, I have given the classification as REVNO >=0 with a document type ZB for create (S1). So when I create the PO manually, the version starts with 0, so condition should satisfy here
    On the other when I change the PO (with/without reference to PR), I have given the classification as REVNO as > 0 with document type ZC (S2), so when the PO is created initially it will not satisfy strategy S1 as doc type is different for S1. When I change the PO created with ref to req, S2 should take into effect because when i change the version will change to 1 and S2 should trigger because REVNO is > 0 and doc type matches.
    So I dont know where the release strategy matches in both S1 & S2 for the system to not propose the release startegy.
    Let me know your thoughts.
    Thanks for your feedback.

  • Release Strategy - Approvers

    Hi,
    I want to know who are the approvers for a Particular POs? Where can i find this information.
    When i go to the PO and then go to the "Release Strategy",it is just displaying Buyer, L1,L2 approver etc.? Where can i find the names of the buyer ,L1 and L2 for this PO?
    Thanks

    hi,
    You need to check the authorisations via SU24 tcode..
    The authorisation object attached will be "M_EINK_FRG".
    If req. check with the basis consultant...
    Regards
    Priyanka.P
    Edited by: Priyanka Paltanwale on Jun 19, 2009 9:36 AM

  • Release Strategy and workflow in Purchase Requisition

    Hello All,
    My client wants to activate the release strategy and workflow at the purch req and PO levels. They allow users to create a Preq and reference that preq to the PO, or users may create a PO without referencing a Preq. Since they have the release strategy and workflow working on both levels, what they want done is, if a PO has a Preq reference, it does not need to go through another approval process on the PO level as it has already been approved on the Preq level. Therefore if a Preq is reference in a PO, the PO workflow and release strategy should not be taken into account. Can this happen as a standard config, or will this need a "user exit"?
    Thanks in advance for your help!!

    You will need to activate the user exit. This will keep the PO release strategy simple.
    Have a flag (use USRC1 or USRN1). In your PO release strategy classification, maintain only X in this characteristic.
    In the user exit, check whether the PO is created with reference to PR. If yes, pass "blank" to USRC1, else pass "X". The release will be triggered only in case of X.
    Just a couple of points:
    1) What will you do if one item in PO is created with reference to PR and the another item is not?
    2) What will you do if one item is partially referenced to PR (i.e PR quantity is 100, PO quantity is 200 - of which 100 is referenced to PR and other 100 is not - this is possible by changing in delivery schedule)?
    Hope this helps
    Lakshman

  • Release Strategy  for Preq

    Hi SAPgurus...
    I have release strategy implemented in my system with 7 level approvals for the Pur. Req . Now i need to Change the release strategy to 4 levels approval based on one of the Characterstics that is the Preq Net Price. Which cud be the best process to ahcieve it , since if i am going to keep the old one and create a new one then wheneve similar characterstics appear the system cant recognize which strategy to apply.......
    Please can any one advice me how can i approach ...
    Regards
    Balaji

    Hi Lakshman, Srini & Venki
    From ur statements i understand to modify the existing ones , okie as u said i will delete the extra release codes and modify it . Now fine..
    What happens when i moved to prodcution these changes then, say if i have Preq
    with older version of release strategy how it impacts.....How i can handle  this in
    effective manner...To my knowledge i think whenever if i go for a change in preq the new release strategy will be affected....( In this case its fine) what abt the ones which doesnt need a change and has to be released....
    Thanks for the time ...
    Regards
    Balaji

  • No release strategy tab for purchase requisition

    Hi Gurus
    i have a user who is complaining about the release strategy not appearing after saving the requisition, but when i try to test it from dev using his profile, it works fine. he can create the req fine on other pc's but not on his pc. i have check his patch level and if he is using the latest gui version and he has both.
    what could be causing this issue?
    Please help
    thank you in advance

    Hi Roy
    thanks for the reply
    am i  supposed to check this on his profile? he is the only person getting this issue other users are working fine. so my assumption is that it must something to do with his sap settings but i dont know the technical side of sap
    please help

  • Processor of PR item level release strategy

    Hi All,
    I need to pass the Processor determined from an item level Purchase Requisition release strategy to a WF container.  The event is RELEASESTEPCREATED in BUS2009. I have created an import element container called 'Processor' from ABAP dict. data type  MEACTOR.
    In the binding for the WF trigger RELEASESTEPCREATED I cannot bind the 'Processor' wf container to the Event Object. 
    What are the steps which I must follow to add the 'Processor' to the RELEASESTEPCREATED event?
    The release strategy in SPRO for item level Purchase Req release is complete and the Set-up procedure for Workflow is complete.  
    Thanks
    Mike

    Hi,
    Go to SWO1, enter BUS2009. Click on create subtype icon there. Then enter all fields as say ZBUS2009. Now save your new BO. then implement and release it , i.e;
    Edit> Change Release Status> Object type> to implemented. Again Edit> Change Release Status> Object type> to Released. Then go to events in this objects. Click on event RELEASESTEPCREATED. Then click on event parameter and create a event parameter.
    Hope this solves your problem.
    Don't forget to delegate ZBUS2009 with BUS2009 in SWO6.
    Let me know if you have any queries.
    Regards,
    Raj

Maybe you are looking for