PO release strategy, ref: plant and activity

Hi,
for PO release M_EINK_FRG is the object.
but along with this we need to give M_BEST_BSA & M_BEST_WRK, the activity is 02(change).
my concern is, if we give him the same objects authorization, he will be in a position to change the PO also, along with releasing the PO.
do we have any control for the same?

Hi,
In that case create  seperate Z roles according to
Combination of Rel Code,Pur Grp,and plant combination
You can have that role with combination of all these objects with limited
authority specific to plant and or doc type
And assign these seperate roles to each user id
Try this and confirm
BR
Diwakar

Similar Messages

  • Release strategy for PR and PO

    I have release strategy for PR and PO, suppose there is 3 levels of Release, at second level I want to set an alternative Release code,  if either of the employee releases then it should go to third release.
    How to configure for PO (with classifications) and PR (without classifications). 
    I am not using workflow than how to do it ???

    follow the steps below.
    Release prerequisites should not be checked
    Release statuses do the following settings for alternate release
    based on your requirement
    you can make the release or blocked status manually in release config
    than it will work.
    without classification it will not work

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

    Dearest Friends,
    we have Plant A & Plant B
    for Plant A     PR and PO <50K will be released by  R1   and  value >50K   by R1 and R2, R3.
    *for Plant B   PR and PO >50K will be released by R1, S1 and  >50K  R1, S1, R2, R3.
    how can we define the above release strategy.
    hope you guys will help me.
    Thanks and Best Regards,
    Rajesh G

    Hi,
    for Release streagty either for PR or PO.
    Steps :-
    1. Create a Class T code CL01....Put Class type "32".
    2. Crate Charateristics CT04 for ur case
    Suppose for Plant ....in Addidtional data Put Table Name CEKKO  and Field Name - WERKS
    For Value  ......... maintain CEKKO - GNETW 
    For PR .....
    Table Name CEBAN --- WERKS for Plant
                          CEBAN -- GSWRT for Value
    either go to se11, give the table name....u will get all the field there for which u want ur charterstics will work.
    3. Assign Charcatristic to Class either in CL01 or cl24n.
    3. Now go to Spro --> MM --> Purchase ---> release streatgy
    first define Release code  as R1, S1, R2, R3
    Define GRp and Streatgy....
    for Plant A PR and PO <50K will be released by R1
    Suppose Grp is XY and Release Ste R1....click on details ....fill release Code R1 and in classification maintain Values <=50 and plant A.
    Similarly Mainatin other....
    Also u can document from
    http://sapdocs.info/wp-content/uploads/2009/07/Step-by-step-guide-of-SAP-PR-Release-Strategy-configuration-a-case-study.pdf
    http://sapdocs.info/sap/materials-management-2/automating-purchasing-approval-sap-release-strategy-tips/
    Hope Help U !
    Regards,
    Pardeep malik
    Edited by: Pardeep  Malik on Sep 19, 2009 11:53 AM

  • Release Strategy different plant in one PO

    Hi.,
    Can u clarify, I want to set release strategy in PO .
    In PO two line item entered for each line item is different plant 1000, 2000.
    IS there Possible to do release strategy in this scenario .
    If  possible please guide me how to proceed this.
    Best Regards
    K

    yes you can do.you have to create a characteristics for Plant(field WERKS)and table CEKKO select multiple values in the characetristics.you add this with your class and in the classification of release strategy enter both plants 1000,1100(within same company code) along with your other characters.try it will work.
    note: you cannot do it for 2 company codes.because company code at header level and it is unique.
    hope this helps
    reward if useful.
    regards
    venkadesh

  • Release strategy for PO and Service Entry Sheet

    Hi
    I maintain characteristics- Plant, Doc Type , Order Value & Purchasing Group for PO release strategy.
    should I maintain the same characteristics for service entry sheet ?
    the approval will be the same for both

    Hi,
    The Po reselase strategy can be set up separately from the entry sheet release strategy, so you can use even different characteristics for your entry sheet release strategy. These are not connected!
    Please read note 672719 question 5 - How can I set up a release procedure for service entry sheets?
    Note: The release strategy must be based on the structure CESSR.
    The PO release strategy is based on the structure CEKKO.
    For the SEs release strategy you must create a different class.
    Regards,
    Edit

  • Release strategy for PO and RO

    Hi All
    My release strategy for Purchase order and Release Order is same.My release strategy has material group and PO/RO value as characteristics. What I want is that my releaase strategy for PO should be based on value whereas for RO it should be based on material group. Is this possible since we cannot have different release group for PO and RO.
    Pl suggest how to go about?

    HI Satish,
    In the characteristic value screen we not only can give single values ,but also multiple values
    and also range of values.
    Since the Data type for this Feild is character ,that is the reason it is not taking Ranges
    So the same is not working for PO,I too Checked the same.
    So it is that you have to have material group ,then there is no other go but entering all the values for the same.
    As we cant add a new Release Class also
    Becoz the release class cant be different ,so as the characteristic values would be same.
    if i could find something else will post you soon.
    but as of know we cant do nothing in this case but create all the material group as charecterics values and add to that strategy.
    Thanks
    Anjanna.

  • Release Strategy for PO and RFQ

    Hello
    iI have configured following Release Stategy for PO.
    0-1500 INR-Officer
    1500-50000-Manager
    >50000-General Manager.
    The same release startegy has got coped fr RFQ also which is fine.However after I for release in ME45 it is selecting Release Strtagey 0-1500 only.
    Even though I raise RFQ for more quantity I get the same Release Strategy applied.
    I am not sure why this is happening,can anybody explain the reason for the same.
    Regards

    Dear All
    Thanks,issue got resolved.

  • Release Strategy-estimation cost and po cost

    Hi
    Client issu like...in RS
    We are maintain our estimation cost in Ztable(Zdev).Purchase order net value is Actual Cost.
    My Purchase order cost is less then Estimation cost .NO Problem. We config the RS some Level.
    But My PO cost is Greater then Estimaton Cost ,that time client wants some RS in purchase order.
    How will i configure Release Starategy Negative Deviation occur in comparison Statement?
    Example estimation is RS 10000 (ztable)
    Actual PO cost is RS 13000(Ekko)
    Now Run Zreport (ZComp) The system Will give 3000 is negative deviation
    Nagative dev  RS 3000
    Above The RS 3000 ,How will i configure Release Strategy In PO?
    Rds
    Kavi

    Hi kavi,
    can you please eloberate your issue,
    as i under stood you are setting the releasestrategy for PO price.

  • Release strategy not triggering for Specif plant

    Hi Friends
    I configured a release strategy with three charecteristics. P.org, Plant, Net value.
    this stretegy is triggering for specific plants which are under a particular company code, and if I change to my plant and P.org. its not triggering.
    I have deleted all the classifications and release strategies from, no other data in VV_T16FS_2 , AUSP,T16FV,and T16FS tables except this release strategies data.
    do we have any settings at cocode level??????
    please respond if answer known
    Points would be awarded for for your valuable answer.

    Thank you deepak for your quick respond
    Actually There were already release strategies  with same charecteristics, and with the values of other plants and other P.orgs which are under certain companycode.
    these were triggering perfectly for PO
    Now created new strategy for plant and P.org under different plant code of different cocde. this strategy not triggering for PO.
    but if the release strtegy  values replaced by the erlier plants and P.org  again its triggering.
    Now I created new chars, class, and stategies still same problem persists.
    Release stategy working for the values of a prticular company code plants, Porgs.
    and already tried your suggestion Cocode as char. but same its working for only that company code not for my companycode

  • Problem in release strategy in a plant PO. Strategy does not appear

    Hi:
    I have a problem with release strategy in plant PO. When we create a PO in this plant, we have no tab for release strategy, if I change the plant in PO for a different one I get this tab with all data.
    I have checked OMGS, CL20N and everything seems to be in order. I think this is a problem in plant definition, but I really donu2019t know where I can look for. This plant is a copy of an existing one, and in this plant there is no problem.
    Please, any idea?
    Thank you very much in advance.

    you can test if one or more strategies can be found. (you should one find one, otherwise SAP is not able to determine which one should be used)
    go to CL30N.
    Enter your class and class type 032, hit enter
    Enter values for the characteristics. and click button for a search in initial class.
    I dont think it has something todo with plant customizing. Classification just takes the values that are in your PO and searches for a strategy  which has to be in table T16FS.

  • Removal of plant from P/R release strategy of another plant

    Dear Friends,
    In our office there are two plants P068 & P281 both belongs to two separate co codes. In its P/r release strategy in characteristics plants are mentioned so for each plant their should be separate p/r as they are located differently. But unfortunately plant P281 is added in the release strategy of plant P068 though there is a separate release strategy configured for plant P281. So while making P/r of plant P281 release strategy of plant P068 is getting called & the user is not able to release the same because of the restricted authorizations. We have tried to remove the plant P281for which we created the request on DEV server & transported to PRD server but this is not removed. It is still reflecting in P068 P/r release strategy. Kindly advise how we can remove this ? Is their any other alternative way?
    Rgds
    Prashant B

    You need to remove the plant from classification of release strategy. If system is modifiable, go into release strategy and classification and uncheck the plant, which is not required and save.
    OR
    If backend is unmodifiable, use this t-code CL20n/CL24n, put in the release code strategy combination and in the classification remove the plant of it and then save and your problem will be solved.
    Follow the above steps for adding the plant to new release strategy as well.
    Edited by: Afshad Irani on Apr 28, 2010 4:45 PM

  • Relation between Version and Release Strategy at Purchase Order level

    Our requirement is as follows:-
    Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
    now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
    Price-A can be equal to Price- B, Less than or greated than.
    I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
    Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
    and when i delete the version condition, we can see the release strategy tab in the PO.
    Thanks in advance,
    Vikas Rander.

    Our requirement is as follows:-
    Case: "Document Type" + "Purchase Group"+ "Price-A" ==== Release Strategy "XX" , and it got release by approving authority "YY"
    now, if i edit the vallue of above case to "Price-B", in such a case a new release strategy should trigger and it should go to approving authority "ZZ" in all the cases
    Price-A can be equal to Price- B, Less than or greated than.
    I come to know that, to acheive this we need to activate the version management, MM>>Purchassing>>Verion managemet>>for external document ( Here i have maintaned the veriosn for "F", and "Dcoument type" for "Purchase Org"
    Now the issue is when i created the version with REVNO and CEKKO table, and when i maintain the version for the release strategy , system dont show the tab of release strategy in PO screen, means release strategy is not getting applied on the PO,
    and when i delete the version condition, we can see the release strategy tab in the PO.
    Thanks in advance,
    Vikas Rander.

  • EXIT_SAPLEBND_002 -- user exit for release strategy

    Hi,
    This is regarding help on user exit for release strategy, ref: note no. 365604, however after going through all the config part given in the given note we activate the fm in cmod.... but after activating the release tab goes off from  me29n.
    That is after you activate in cmod and then if u create po and go to me29n the relese tab is not there.
    if u deactivate and create po and then relese the release tab in me29 would appear.
    All we are trying is that the po in me29n should be open to release again if we change the delivery date. However what coding and how is still a second step , first is as soon as the exit is active the tab goes off.
    New to user exit . plz help.

    Hi Again,
    I guess I have solved the issue temporarily, however Am not sure if this is the best which cld be doen to the issue.
    I didnt make any new characteristics in ct04, for the delivery dats since i didn't want to restrict the delivery date. All I did i yje coding below in the exit :
      DATA wa_eket TYPE LINE OF mmpur_beket.
      DATA wa_eket1 TYPE LINE OF mmpur_beket.
      data: c type i.
       data: p type i.
      break1.
      break2.
      e_cekko   = i_cekko.
    loop at it_beket into wa_eket . " for comparing previous and the current del date
      e_cekko-usrc1 = wa_eket-eindt.
      SELECT SINGLE * FROM eket INTO wa_eket1 WHERE ebeln = wa_eket-ebeln
      AND ebelp = wa_eket-ebelp.
      if wa_eket1-eindt <> wa_eket-eindt.
      import c from memory id 'CID'.
      c = c + 1.
      clear p.
      p = c mod 2.
      if p is not initial.             " adding 0.01 to the characteristic value for p.o amt.
      e_cekko-GNETW = e_cekko-GNETW + '0.01'.
      else.
      e_cekko-GNETW = e_cekko-GNETW - '0.01'.
      export c to memory id 'CID'.
      endif.
      endif.
      endloop.
    The logic I tried using is since the relese gets reset incase of p.o amnt and hence indirectly po amnt so i changed the value of p.o value by 0.01 incase of change in delivery date. cekok-gnetw doesnt reflect anywhere in the p.o as amnt, I guess its for defing range for relese stragey's amont in ct04 characteristics.
    However anything better incase u know plz let me know, or do u think this can cause any problems later....new to exits.
    Rgds,
    Anu.

  • Release Strategy - Purchase requistion go back to unreleased

    Hi Friends,
    I am facing  two  problem in release strategy in our client system.
    Problem. 1:- Purchase Requisition changes( Other then the characteristics maintained) causing PReq go back to Unreleased.
    Current System Settings;-
    Release Procedure:- Procedure with classification ( Also setting available for  setup procedure without classification maintained )
    Characteristic maintained in class :- ( Plant, Value , Creation Indicator)
    Value maintained in CL24N for plant , Creation indicator.
    Release Indicator:- 1 Stage:- X. Blocked
                                    2 Nd Stage:- 4.RFQ/PO no changes
    Scenario :- When  PR is created and released , If any one changes the Purchase Group in any line item  which is not part of the release Strategy. Release strategy gets retriggered and the relase staus goes Blank for some case and for some case release strategy retrigger. My Question is if Purchase Group is not part of my release Characteristic then why release strategy gets retriggerd.( I used only purchase group here for Example, Any other changes also effect the release strategy to retrigger)
    I checked all the system setting and it seems to be correct except when i  use transaction OMGQCK to check PR release strategies, the log shows 3 errors of type:
    Checks re requisns. with item-wise release 3
    -> Checks re release group and release class 2
    -> No release group exists 1
    Problem. 2:- Purchase Requisition not triggering when  PR is created from other source linked to SAP.
    Please suggest the solution for the above problem.

    Hello Kunal,
    A few thoughts and questions on your problem:
    You generally can't have both release procedure without classification and release procedure with classification working at the same time.
    To get the system with classification working, you have to have several things in place and consistent: You need a release group.  It should have a class.  That class should have all the characteristics you need to assign a strategy to every requisition (or item, if you're doing item-based release).  You should use CL20N (or CL24N) assign values to strategies so that you have no possible cases where a requisition (or item) doesn't get assigned to a strategy.
    You have to choose item-based or overall release for each requisition document type.  You mark this on the document type.  You must also choose the same option for the release groups that the document type will be assigned to.  Example: document type NB is item-based.  Document type ZB is overall.  Document type will be a characteristic.  CL20N will assign requisitions with document type NB to strategies in release group NN and requisitions with document type ZB to strategies in release group ZZ.  Release group NN will be marked as item-based.  Release group ZB will be marked as overall-based.  Usually, I think, you will  just use one or the other, and it will be less complicated, but the release group must match the document type.
    The indicators themselves have some configuration, including a field for changeability.  Your configuration defines the indicator assigned after a release, and that changeability field will determine whether the requisition can be changed and whether that determines a new release.
    As Prasoon mentioned, if there's an enhancement active, that could affect things beyond configuration.
    If you are using workflow, there might be custom events related to the business objects involved that  can change things, as well.
    Are you using workflow?
    Are you using overall or item-based release?
    Good luck,
    - Jeff

Maybe you are looking for