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

Similar Messages

  • 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

  • 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

  • User Exit for getting Purchase Requisition Release Strategy

    Hi Experts,
    When a user creates a PR I need to know the user exit I need to implement so that the First Approver (Processor) text  in the Release Strategy is populated from a custom table. I have seen that the field is MEREL_S_GRID1-STEXT. I also need to know if I can implement a user exit so that it pulls the release strategy for a PR for assets (Acct Category A) since it is pulling for Acct Category K (Cost Centre) and the Release Strategy tab is appearing in this case.
    Kind Regards,
    Darlington

    Hi Meenakshi,
    Thanks for the very useful answer. It has given clues on how to resolve this issue. I have resolved this issue for the Asset item category using the following thread: user exit for requisition release strategy, and also SAP Note 365604.
    However, I have another issue, the release strategy for Stock Items, (item category blank) is not pulling through. I need to use the same method above but would like to know how it determines the funds centre for a specific stock item. I couldn't find where that is implemented in the material master and I need info on how to determine the account assignment for stock items based on the funds centre.
    Regards and Thanks.

  • Badi for Purchase Requisition Release Strategy

    Can any help me to know about the BADI for Purchase Requisition Release Strategy .Is their any BADI to  control the PO Price for a PR release strategy
    Thanks for your help

    This badi is for schedule agreement ?
    BAdI: Release Creation for Scheduling Agreements with Release Documentation
    Use
    You can use this Business Add-In (BAdI) to influence release creation.
    This BAdI is used in the application component Scheduling Agreements (MM-PUR-OA-SCH).
    This BAdI includes the following methods:
    Change Data Before Release Creation (BEFORE_CREATION)
    Change Data After Release Creation (AFTER_CREATION)
    This BAdI is called during manual and automatic release creation.

  • Redetermine release strategy for purchasing requisitions

    Hi Guys,
    How can I redetermine the release strategy for purchasing requisions when changes on the costcenter (EBKN-KOSTL)  are done -
    I know that it will be redermined when I add the costcenter as charateristics in customizing for release strategy but thats not an option
    I also tried to add coding in userexit for changing the communication strategy (Include ZXM06U13) but this exit doesn't provide information of the document number and position (EBAN, EBKN ..) so I can't find out if changes have been made
    I spend several hours trying to find solutions for this issue but no working results so far ..
    I hope you can help me on that
    TIA
    Manuel

    Hi,
    Note that EBKN will have entries corresponding to a PR only when it is        
    saved or checked, so KOSTL will not have any values for a PR which is under              
    creation. You should always use fields from structure CEBAN while             
    creating characteristics for Requisition release procedure as it              
    contains most of the relevant data about a PR under creation/change.
    I would advice you to check the note 365604.
    Please also check the changeability indicator in the customizing:
    transaction OLME -> Purchase Requisitions -> Release Procedure -> Procedure with Classification -> Set Up Procedure with Classification -> Release indicator -> check the detail screen for settings.
    Please check additionally the possible values for your characteristic cost centre (transaction CT04).
    Regards,
    Edit

  • Purchase Requisition with wrong purchasing group - release strategy

    Hello
    There is a lot questions about release strategies but I cannot find answer.
    I have release strategy based on:
    - Plant
    - Purchasing Group
    If I create Purchase Requisition with right purchasing group release strategy is assigned to PR item.
    When use wrong purchasing group - release strategy is not assigned.
    How to easy set control – if user use wrong purchasing group system automatically set one strategy which not allow to create purchase order.
    There is too many plants (150) and purchasing groups (60) to create all combinations in strategy. So I cannot do that.
    Maybe there is some useful user-exit?
    I use SAP ECC 6.0
    My problem occurred because SAP allow to create PO with reference to PR which have no assigned strategy.
    Thanks in advance for help
    Arek

    Yes it is solution
    But as I wrote before – there is too many incorrect combination.
    Example
    PG A1, A2, A3, A4…. A50
    Pl 2200, PG A1 – OK
    Pl 2200, PG A2 – OK
    Pl 2200, PG A3..50 NOK
    For this example I have to set 48 combinations (strategy with S).
    I noticed that I would have to set about 200 strategies. Client don’t want accept it.
    You wrote – “set up one unique strategy”. How? As I know I need 200 strategies (or there is something I don’t know
    Kind regards
    Arek

  • Problem in Purchase Requisition Release Strategy

    Hi sapgurus,
                           i am defining a release strategy for Purchase Requisition. but whenver in a strategy two release codes are incorporated suppose
    Release group :MM
    Release Codes: M1 and M2.
    but in relese simulation tab showing
       "M2   Release prerequisite missing"
    and M2 code is not working in releasing pr.only M1 is worked.
    Thanks in advance.
    Regards,
    Bipasha

    Actually I want to create two release strategy
    1. when total value in PR will be 1000.00 then one person can release PR.
    2. when value is greater than  1000.00 then two persons will release.
    For this i created a release group K1 with checkbox against  'OvRelPReq'  is ticked.Then i have created M1 and M2 release codes are created.
    Then I have given release indicator one for realesed and another for not released.
    After that , create a relase strategy
    where after M1 ,M2 can able to release the PR.in prerequisite button i ticked the checkbox near M2.
    It will not work.
    Plz give me a suggestion.

  • Purchase requisition release strategy tab missing

    Hi all
    I configured purchase requisition release strategy and ME51N is working issuing no error but it is not displaying Release Strategy Tab , please help me where i am wrong.

    hi,
    check few reasons:
    1. There might be more than 1 release strategy using the same class, due to which it is not possible for sap system to determine the unique rel. strategy..this normally happens when you copy the exsisting class and assign it to own new one...
    2. check the release strategy OMGSCK, is there any problem with your release strategy...
    3. Check whether you have maintained all the classified field in the document or not..
    4. check whether the release is assigned to any workflow...if so, then check the inbox pls...
    regards
    Priyanka.P

  • Reset Of Purchase Requisition Release Strategy

    Dear Peers,
    Release strategy for PR at header level is defined (Overall Release). If we make any changes or add another line item to the same PR, the release strategy is required to get reset to unreleased state. But this is not happening.
    Same for PO is valid & working ok
    Please suggest
    Mayank

    Read this -- With the Changeability indicator, you specify the effects of         
    changes to a requisition. For example, certain changes may require   
    a new release strategy to be determined for the requisition.         
    Via the Value change field, you can cause the release strategy to    
    be re-started if the value of a purchase requisition item is         
    increased by more than a certain percentage (e.g. 10%). To do so,    
    set the Changeability indicator to "4 - Changeable, new release in   
    case of new strategy or value change" and enter a percentage in the  
    Value change field.                                                  
    <b>
    The release stra can be reset in one case only and that is whenever you change the reqs which changes teh value of reqs then system will reset the release back to original statu and to do that you have to set the changebility indicatior to 4 and changes 0.1 that means whenever req change and value is changes to .1 % then ystem will reset the req to relase again </b>
    Hope this will help you

  • Tranposrt - Purchase Requisition Release Strategy with Classification

    Gurus!
    Tell me if I want to Transport the Purchase Requisition release strategy with classification. The Data in each charisteristics in each PR Strategy that I have set in Dev is not getting transported to Quality.
    Do I have to enter the data in characteristics again in Quality and the same procedure I have to apply for Production.
    If yes, in this scenario, Can I make Production modifiable.
    Regards
    Sajid

    Hello,
    Create a special ID in PRD with access to change characteristics. This ID should be released for specific purposes and with approval (project manager/SAP support manager). You can also turn on auditing so that all activites performed are logged which can be used to satify auditors.
    Cheers !

  • Overall Purchase requisition Release strategy : Changed after Rejected

    Hi All,
        I have activated overall purchase requisition Release strategy (20000077) . And its working fine when PR is released at each level and saved.
      Problem I have is when PR is rejected .
    When PR is rejected , workitem is created for initiator with ME52 transaction. When initiator changes the contents of PR and saves , the release strategy should resume back from where it stopped. Thats means when Approver A rejects the PR, after initiator make changes , the workflow should trigger back with a workitem for release to approver A.
    But its not happening as expected. When Approver A rejected the PR and initiator changes the PR , Nothing is triggered, as there is no event raised at this point. 
    ME52 changes for PR is not trigerring any event which can trigger the WF.
    Is there any way we can trigger Workflow in this scenerio.
    Please suggest.

    Hi Subhashini,
    This all depend on release strategy. release should reset completely on tha change.
    For the increase of quantities or values you can maintain tolerance limits in the Customizing. When you increase the amount or value via the tolerance limit the system will reset the release.
    When you reduce quantities or values the system only resets the release if another release strategy is determined for the lower quantity or the lower value.
    If no other release strategy is determined by the reduction of the
    amount or value, the system will keep already existing releases.
    changeability in Release indicator also play a major role. You should set it to either 3 or 4. Now if you change any field, which is also used in any charecteristics in release, it will lead to reset of release startegy.
    Sanjeev

  • Purchase Requisition Release Strategy wont trigger

    All:
    I have set up what i thought was a simple purchase requisition release strategy. Parameters are as follows:
    1.) Doc Type = NB set up as CEBAN-BSART
    2.) Acct Assn Category = k set up as CEBAN-KNTTP
    3.) Purch Org = 300 set up as CEBAN-EKORG
    4.) Overall Value = 0-1000, 1000-10000, 10000-50000, >50000 set up as CEBAN-GFWRT
    Release group is set for overall release, i've checked the release strategy with OMGQCK and everything was good to go, checked CL30N and everything was triggering, checked table T16FS and there weren't any fishy entries. Oh also, i've tried deleting and recreating the entire release strategy at least 3 times.
    Whenever i create a purchase requisition, i get no release tab. Not sure what else i'm missing here.
    Any help is appreciated!

    I created 4 characteristic with the above mentioned criteria (doc type, purch org, net value, & account assignment category). I assigned all 4 of these characteristics to a class.
    Matrix is as follows:
    0-1000, doc type NB, purch org 3000, acct  assignment 'k' needs approval from release code 01
    1000-10000 doc type NB, purch org 3000, acct  assignment 'k' needs approval from release code 01 & 02
    10000-50000 doc type NB, purch org 3000, acct  assignment 'k' needs approval from release code 01, 02, & 03
    >50000 doc type NB, purch org 3000, acct  assignment 'k' needs approval from release code 01, 02, 03, & 04

  • 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

  • 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

Maybe you are looking for

  • BI Beans under OC4J with a lot of errors -- !HEPL!

    All I have built some dimensions and cubes through BI Beans . but once all of them finished it will drop into an error. when I request a Presentation object(cross table) through web client,the console shows following: Fri Jun 18 21:49:21 CST 2004 TRA

  • Integration Of Cisco ACS and MS Active Directory !!!

    Hi all, We have and Cisco ACS v4.2 on a Cisco Appliance, and we need to integrate it with Active Directory. Can you help me?? Thanks for your help Regards!!! Rafael Turriago

  • Supply and Demand

    Hello, I have a query about supply and demand chart. I want to create a column chart for supply and demand by month. I can plot only one row how to plor second row so that it show two bars in each month? and there is data in both buckets. Please shar

  • Branch Accounting in Classic GL in one company code

    Dear Expert, Our client have 10 branches in India and now they requirement to open all branches in one company code. Client also working on class GL therefore document splitting is not possible. Please advise the best solution for branch accounting i

  • Final Cut 5 and HDV-HCR camera

    I have a new sony HDV-HCR camera and final cut pro 5. My tapes that have been recorded in HDV will log and caputure on my computer but the tapes that are recorded in DV will no show on my computer. I can work the camera but when I log and capture I a