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

Similar Messages

  • Release Strategy for reservation created from PM and PS

    Dear All,
    How to configure the release strategy for reservation generated  from PM and PS.
    Regards,
    Atanu

    do you talk about release strategie for requisitions, or really reservations?

  • 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! =)

  • Is there a process for moving costs from maintenance work orders to capital

    Is there a process for moving costs from maintenance work orders to capital projects?
    We have reversed the settlements on the work orders, and then trying to put the relevant NWA in , then receive error message :
    Rule for allocation of PM order to PS network is not maintained.

    hi
    check the allocation structure and the settlement related customization settings.

  • 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

  • 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

  • Release stratregy for PREQ

    Hi,
       I have configured release strategy for PREQ with classification. this procedure enables to release PREQ both item by item and in their entirely.
    my procedure is working fine.
    In PREQ Screen, the Release Strategy TAB is appearing at item level after contact person TAB.
    Is it ok?
    somebody told me in PREQ, it should appear at header after text TAB.
    Pl confirm
    Thanks

    Hi Ritalee,
    One doubt, is your configuration is by header means Over all release or by item level?
    If you want by header level, you have to select the Overall Rel box in SPRO-MM-PR-Define Doc types.
    You will have a Rel Strategy tab at the header level.
    If you practice by item level, this is not a problem for you.
    Hope this clear any doubt.
    Regards,
    Maia

  • Challenge for release strategy in Preq

    hi all.
    our maintenance department requested a very specific release strategy for purchase requisitions with account assignment F (workorder).
    their release is based on several factors:
    1) amount: 0>2000 it must be released by the main work center which of course, depends on what is on the workorder and can be one of 3 (WC1, or WC2, or WC3)
    2) amount 2001>6250 it must be released by the following:
    WC1and/or Maintenance manager
    or
    WC2 and/or maintenace manager
    or
    WC3 and/or maintenance manager.
    the and/or mean that if WC1/2/3 releases, the maintenance manager will still need to release but if the maintenance manager releases first the Preq is released and there is no further need to release by WCn.
    anything >6250 must be released by the maintenance manager.
    our release strategy is with classification and we will use a user exit to determine which WC is being used and needs to release but i have a problem with point 2: how can i set the strategy in such a way that it can perform the release and/or?
    can someone help?

    Hi Alisa,
                 Your Requirement is very Complex,
    first thing if you want to have the Release strategy for the Account Assignment, you need to have that Characteristics in the class, and make sure that same rule is followed by all the Other PR, directly created.
    Second thing if you say that any thing less then 2000 should be released by the Main Work Center responsible person, which you have maintained by the user Exit, there must b a cross check that the person belonging to one work center should not be allowed to release the PR being generated in other Main Work Center.
    for that you need to have different Release codes assigned to the user in the roles.
    for any thing >2000and <6250, you need the WC1 and Maintenance Manager should release, but only Maintenance manager releases then also the PR should be released,
    Question: in above case what is the need of the WC1 or WC2 or WC3, let it be released by Manager only
    Please revert back.
    Regards,
    Yawar Khan

  • Need to activate release strategy for PR from PS(a/c assignment N)

    Dear experts,
    I need to establish release strategy in PR raised from Project System. PR account assignment in 'N'= network. PR will be differentiated PR value wise . Please help in this regards,
    Thank you.
    Kind regards,
    Zusen

    Hi
    You already have account assignment category (KNTTP) in communication structure CEBAN. You can use it to define your release strategy. If you wan to use field which is not there in CEBAN then you need to append CEBAN with the help of apaper.
    Use this link as an example for release procedure and create your own with KNTTP.
    http://wiki.sdn.sap.com/wiki/display/ERPSCM/RELEASE+PROCEDURE
    Regards
    Antony

  • Work flow for release strategy for PO & PR

    Hi Gurus
    Can anybody explain workflow for release strategy for PO and PR
    Thanks in advance.
    Atul Kulkarni

    Hi,
    First you set your all required configuration fro release strategy(Class,Char,Rel.Group,Release Strategy ,Release Indicator )
    For Work flow settings,You have to do follwoing configuration:
    MM - purchasing - purchase order - release procedure - Define Release Procedure for Purchase Orders - Work flow - Enter release code, group, user ID, object type as user.
    Creation of work flow object,activation of workflow and other related settings will be done by Techinical  work flow consulant.
    Thanks,
    AMIT

  • New release strategy / Old PReqs

    Hi,
    New release strategy has been configured to be active only for purchase requisitions with account assignment cat. F (PReqs coming from work order). In the other words every time when Preq is automatically created from work order new release strategy comes up. So far so good.
    But problem appears when user opens old work order where Service Purchase Requisition exist with old release strategy. After saving work order, without making any changes, new release strategy comes up and Preq status changes from 'Release Completed' to 'In Release'.
    Do you know what causes mentioned system behavior? Why release strategy is changed only for old service Preqs not for Preqs which contains non stock components?
    Many thanks in advance for your clues.
    Regards,
    Grzegorz

    Hi,
    Release strategy will trigger for creating and chenging the PR. If you want to restrict the PR release strategy for change mode, create (select if any one is there) authorization object for PR change mode in SU22. Create a role in PFCG and assign the authorization object to this. In SU01 assign this role to users or group of users. This will resolve your issue. But when you want to change the PR and retrigger the release strategy means won;t work out. In your case after going to change mode and saving the release strategy triggered. Its a sap standard behaviour. If you want to see PR goto ME53N instead of ME52N. If you goto ME52N Don't select save button if no changes are there. Ultimately no new release strategy will trigger. I hope this will resolve your issue. Thanking you.

  • How to stop PR creation from PM work order for a particular vendor?

    Hello Experts,
    We have following scenario for breakdown maintenance activities.
    When a machine breaks down, a breakdown order is created in SAP. The external manintenance services are planned in the order. When the order is released, a single PR (with multiple item numbers corresponding to number of services) is created by SAP. The PR has a release strategy. When PR is released, PO is created followed by the SES.
    The practice followed AS -IS for breakdown outside business hours:- If the breakdown happens outside business working hours, the person releasing the PRs is not available & hence PR can not be released resulting in no PO & no subsequent SES.
    In this case, the maintenance is completed by the external agency & the work order is TECO. The next day, TECO is reveresed, new PR is created, released, converted into PO, & then SES.
    TO-BE process:- Client expects that, for certain vendors identified, PR should not get created at all from the breakdown order. (The list of  vendors will be maintained seperately). For these vendors, a framework order will be created at the start of fiscal year & SES will be created as & when required agaainst the framework order.
    My concern is :- How to stop PR creation from PM work order for a particular vendor? OR delete the created PR?
    Highly appreciate your quick response.
    Thank you.
    Amit
    Note:- My ABAP consultant has checked following BADI's, but could not find it useful.
    IWO1_ORDER_BADI
    ORDER_COSTING_CK
    DATA_EXTENSION_CK
    VALUATION_CK
    ME_REQ_OI_EXT
    IWO1_PREQ_BADI
    ME_CHECK_SOURCES
    ME_REQ_POSTED
    IWO1_ORDER_BADI

    Dear Amit
    I am giving a different dimension to your question check if it fulfills your requirement -
    As we know Vendor selection comes at a later stage only after your PR creation, approval & RFQ etc. & PR generation from maintaine. order is controllled through control key PM03.  While triggering PR from order you have to specify Material group, Purchase group and vendor. Try to control it through authorisation as all these are authorisation objects. The persons executing breakdown order shall no t be given this authoriations
    shakti

  • Release Strategy for contracts.

    Hi gurus,
    Good day,.
    Please help on this.
    We have a release strat for Contract. It is working fine when a contract is created, but when several changes were made on the Quantity, release srtat are not being triggered.
    Example.
    Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    what is the standard functionality for this? Should the decrease in quantity will trigger release strategy or not?
    Thank you.

    Dear Acel,
    The example you given was working just fine and correct.
    a)Contact created with qty 1000 --> release status is blocked. Then release it in ME35.
    b)After releasing, quantity was updated to 1200--> release status is blocked. Then release it in ME35.
    c)After releasing, quantity was updated to 1100--> release strategy was not triggered. Status was released.
    -> The release strategy will only be reset if the total net value for the contract was higher the previous
    value but not lower.
    As your example, quantity was updated to 1200, then it will reset when changing from 1000
    to 1200. However when it was decrease to 1100, then it will not reset anymore as you had
    release it for a quantity of 1200, then the total net value should higher than the current qty = 1100.
    In system, it always assume if you had approved for the total value of the higher 1 before, then
    it should be fine for the lower total net value for your management and therefore not need to re-approve
    again for redundancy job. This was very logic in common business scenario in many companies.
    However, like in your example , if you had define a different release strategy for a value that met the
    the 1100 quantity, it will redermine the different release strategy. For example:
    USD 1 for every quantity = 1
    Then your contract will be USD 1000 for quantity = 1000, USD 1100 for quantity = 1100 and
    USD 1200 for quantity = 1200.
    Release strategy A for 1000 , characteristics from USD 1000- lower than 1100
    Release strategy B for 1100 , characteristics from USD 1100- lower than 1200
    Release strategy C for 1200 , characteristics from USD 1200 onwards
    Then if you change the quantity from 1200 to 1100, it will redetermine the release
    strategy B which means from Release strategy C to Release strategy B. If you
    only had Release strategy C that had a characteristics from 1000-1200, then
    it will keep the Release strategy C as released and it won't be reset unless
    if you had change it and the condition of the total net value was higher than any value
    before.
    Hope this will explain the logic.
    Ian Wong

  • Release Strategy for PO not kicking in

    Hello SAP Experts,
    I have gone through all the steps of configuring release strategy for PO. I checked at the end with the transaction code OMGSCK and everything is good with no error. But when I test the strategy by creating a PO, the 'Release Strategy' tab does not come on in the PO Header. This means that the Release Strategy did not work. I have troubleshot over and over again right from the Characteristics/Class, all the way to the Release Strategy, but no breakthrough.
    I will appreciate and award points for helpful hints.
    Thank you in advance.
    Joel.

    Please list all your char you have created and the value of char.
    Than please tell the PO details.
    once i got this info than only i can see the problems.
    you can do one more thing
    goto CL30n and enter the class and class type 032
    than hit enter and enter the value of char which you have used in the PO and then hit find initial class button from top menu
    see if any release strategy is pulled or not?
    if it is determine morethan one that means you have same value exist in more than one release strategy

  • Setting release strategy for PR for mixed requirement

    Dear SAP gurus,
    I have a mixed requirement for PR release strategy. For instance, there will be 2 types of PR created in my company. One is created manually, the other one created from MRP. The requirement is that for PR created manually the release strategy will kicked based requisitioner data. While for PR created from MRP, the release strategy will be based on MRP controller.
    At first I thought that it is possible to have 2 class set for PR (both should be released at header level), but apparently it is not. So I'm forced to create ONE class that supposedly able to cater both condition.
    So at first I create one class with 2 chars: MRP controller and requistioner
    For PR which is created manually: I put requistioner eq 'FINANCE' and MRP controller blank (with the hope that ALL value doesnt matter),
    For PR which is created from MRP: I put MRP controler eq '001' and requsitioner blank (with the hope that it means that ALL value doesnt matter).
    However it seems that SAP consider that blank means blank. I tried with * it also not working. How can I configure this kind of scenario?
    Please help.
    Best regards,
    John

    The solution that we implement is to have an exit to determine the requisitioner in the PR based on the MRP controller. Thus we have a common solution for both PR

Maybe you are looking for

  • IPad app store message "Cannot connect to iTunes store"

    Recently my iPad (wifi) & my husband's iPhone (AT&T)have been unable to connect to the app store or iTunes. We get the message "cannot connect to iTunes store". The only thing that I have done recently is download a kindle book & add a Bluetooth keyb

  • Urgent help needed in configuring X1151A

    for RAC requirements I have to configure this card to use the interface name of ce1 but I have tried changing slots and puting /etc/hostname.ce1 file out there but it fails .. it always comes up as ce0. my question is : How can I cofigure this card t

  • Invalid page fault in module cvirte.dll

    I have updated two old programs using LabWindows 7.0 which were perviously created with an earlier version of LabWindows. I am having problems though updating a third program. I get an error stating... Characerization (the name of the program) caused

  • Displaying Image on th JSP page

    Hello All, I am using following code to display the image on the JSP page in my iView <% String PublicURL = componentRequest.getPublicResourcePath()+ "/images/Image1.gif"  ; %> <hbj:image id="Logo" width="70" height="35"                             s

  • Why does LabVIEW generate -0?

    I have attached a bit of code that occaisonally generates a value of -0. Solved! Go to Solution. Attachments: negative zero.vi ‏7 KB