Release startegy issue

we create a PR and PO against network for one project. the PR already go through release and approval .
but one user change in CJ20N, then the PR is set to initial release status again, how to prevent this and how to resolve this problem. thanks

May be you can try posting in MM forum.

Similar Messages

  • Release Startegy for Item Category

    Hi ,
    Can we have a release startegy for PO for Charcetrstic Item category.
    It do not have any reference in in Table  CEKKO for any field.
    Can you tell me how can I activate the item category as a charcetrstic value in PO release startegy.
    Thanks,
    Lekhram

    PO release strategy always work at the header level but if oyu want to add the item level field as a char (in your case Item category) than you need use the user exit to insert the field in CEKKOZZ include of the CEKKO structure.
    Use the user exit M06E0004 to insert your field in CEKKOZZ include.
    once you get the field in this include then create the Char and use in classification.
    But make sure one thing is that
    Suppose you create the first line item of PO with Item category D and than you insert the second line with item category L and your release stratey doesn't have the both the item category than you are in problem
    Or suppose your first line has blank item category and second one has item category than also you will have issue.
    so make sure you create the PO for same item category without any othe combination to work with release.

  • PR Release startegy

    PR release startegy  should be flexible so that if we add any of the parameters, the program should follow the rules. The parameters that can be changed are:
    1. Document Types
    2. Project Types (We will need a custom table)
    3. Plants Groups
    4. Threshold Amounts
    The routing of the Purchase requisition approval is primarily based on the amount on the requisition, the Plant, and the department the requisitioner belongs to.
    In standard sap we have static parameters for release staregy, but here requiremnet is dynamic, when ever you chnage any of the parameters the syatem should adapt those chnages and the existing rules must apply for new one.

    Why would you change Doc. Type?
    If your requirements are not firmed than you should not raise requisition.
    No matter how dynamic your business is, requisition raised for a particular requirement should not vanish or change in a day or so.
    Practically speaking, it seems your supply chain is not process driven.
    For such scenarios you should allow to create POs directly once the requirements are firmed and aprovals covered for POs only.
    Regards,
    Dakshesh

  • Release startegy for service PO

    Hi,
    Can you people help me out with release startegy for Service PO and service entry sheet?
    Regards,
    Satyendra

    Hi,
    Please refer below mention format.
    SPRO -> Material Management -> Purchasing -> Purchase Order -> Release Procedure for Purchase Orders.
    Three steps involved in release process of purchase order.
    1) Edit Characteristic: -
    Create characteristic for release purchase order. If you want to release purchase order on purchasing group base. So you can create characteristic for purchasing group. Take reference of CEKKO structure and BKGRP field for purchasing group in additional data of characteristic. E.g :- Purchasing group - BKGRP
    2) Edit Class: -
    After creation of characteristic, create class for release purchase order. In which you can take reference of
    Class Type: - 032,
    Status: - Release,
    Class group: - Release strategy class,
    And put reference of your characteristic, which are created by you in first step.
    E.g: - Class u2013 REL_PO
    3)Define Release Procedure of purchase order: -
    In this step four processes involved.
    1) Release Groups
    2) Release Codes
    3) Release indicator
    4) Release Strategies
    1) Release Group: - In which you can define release strategy group
    For Exa.: - Release group : - 01,Release object: - 01, Class: - REL_PO.
    2) Release code: - In which you can define release code. Enter value as
    Release group: - 01,release code: -01 u2013 Purchase Head,
    Release group: -01, release code: - 02 u2013 Auditor.
    3) Release indicator: - In this step you have to define release indicator.
    Like X u2013 Blocked, I u2013 Under process, S u2013 Release.
    4) Release Strategy: - This is the final step for release strategy.
    Assign release code 01, 02.
    Click on release prerequisites, select 02 u2013 check box and click on continue.
    Click on release status button, enter release indicator X, I, S and click continue
    Click on classification button, Enter values of purchasing group for which you want to created release strategy.
    Note: - Create characteristics for service order document type in CT04.
    Regards,
    Mahesh Wagh

  • External program to reset release startegy

    Hi All,
    Can anyone tell me how to reset release startegy from an external program. I understand that there are some exits avaialable to do it. I dont want to add my logic in an exit. Based on my program conditions I need to reset the release startegy of the P.O.
    Any Bapi of FM that is available.
    Thanks,
    Anupma

    BAPI_PO_RESET_RELEASE soved the probelm. U need to copy and remove std. check and it will work fine.
    Thanks,
    Anupma

  • Purchase order release startegy

    Dear Experts,
    We have got release startegy for five release codes i.e L1,L2,L3,L4 and L5 for purchase orders
    Release startegy is based on Pur order category,doctype, Net order value and Pur group.
    For L1-L5 authorisation(all authorisations) is given for General managers.
    Currently when emergency is there general Manager has to release L1 to L5 all release codes.
    Requirement is that instead of releasing all can it be possible to release only L5 so that all can be released.( This authorisation is for only for L5)
    Once the authorisation is there for all any customisation possible for releasing code L5 so that remaining all release codes can be released.
    Please suggest.
    Regards,
    Dayanand

    Hi Mr.Shawn,
    I have removed ticks for L1,L2,L3,L4 in Release prerequisites then release startegy L1 L2 L3 L4 kept as Released.
    Then Even if release one all releasing.
    But Requirement is that when only L5 is released only All shall be removed, other wise remaining Releases shall be based on the old procedure only. L1 to L4 shall be L1 is released then only L2 can be released principle. But in case of L5 releases all shall be released.
    Is it possible, what needs to be done ,please suggest.
    Regards,
    Dayanand

  • Reg Release startegy, Class n characeristics

    Hi
    This is regarding PO release strartegy
    I setup Release strategy for PO's in Development system, for each release startegy allowed characteristic values are mentioned during config as expected
    I released transport to quality [we have 2 systems
    1. In One quality system i forgot to maintain classes, i maintained class, but still i am getting error 'Error in classification (class 032 class type 032)'
    2. in another quality system class and characteristics are maintained before releasing transport. when i see SPRO, system hasn’t assigned allowed characteristics values for each release startegy?  why?
    Do i need to perform any thing else other than creating characteristics and classes?
    What task should i b doing in target system
    Thanks in advance

    Thank you
    i understood exept 'donot open the client in quality and assign the values' what does this mean ?
    I am doing CL20N in quality only ?
    i understood in Qulity[target sytem]i must perform below
    --> create characteristics
    --> create class and assign characteristics
    --->CL20N assign allowed characteristic values for each release startegy

  • Difrence between work flow n release startegy

    hii frnds
    can anybody tell me wats the difrence between work flow n release startegy ..
    thnks
    rohit

    Workflow could be generic and can be configured for any process you want.
    When you want to control the releases of the documents depending on the parameters that you want to configure, you use the release strategies. While configuring release strategies, you can develop some workflows.
    Release strategies is more of a functional concept and workflow is the technical implementation.
    Regards,
    Ravi

  • Release Build Issue

    Hello!
    I'm stuck on something pertaining to my release build. It's not working. I know there could be a lot of reasons for this, most related to path dependencies within my code. In my troubleshooting, however, I've stumbled across an issue that I think is at the root of the problem. I'm hoping someone has a solution!
    Here it is:
    I'm using Flex Builder 3, and it's an AS3 project. Running the project is no problem. Works great from the bin-debug folder. As soon as I pull the files in the bin-debug folder into another folder, however, it no longer runs. I'm doing this in the most basic way possible. Here are the steps I'm taking:
    1. create a new folder at the same level as bin-debug. Calling it, creatively, bin-debug2.
    2. copying all the files in bin-debug and pasting them in bin-debug2.
    3. opening my browser and surfing to bin-debug/project.html - works perfect.
    4. opening my browser and surfing to bin-debug2/project.html - doesn't work.
    How is it possible for the exact same files not to work just because the parent folder has a different name?
    I believe answering this will solve my release build issues.
    Thanks!!

    Hi Greg,
    Thank you for taking time to help me troubleshoot this.
    Running the bin-debug version of the projects main .html page in a browser works. Meaning, the page loads, I see the default background color I've set in the compiler, and the opening animation starts.
    Then I copy and paste all of the files in bin-debug to bin-debug2. Try running the exact same .html file. The page opens in the browser and I see the default background color I've set in the compiler. The opening animation never starts.
    Thanks,
    Jake

  • Release Startegy

    Hi,
    We have configured PO release strategy by taking characters as Plant, Document Type, Value & Material Group.
    To be clear release is working fine when we consider a single material in line item of PO.
    We have 60 material groups and the release startegy is common for the material groups from  1 to 50 and the remaining 10 material groups 51 to 60 have different release strategy.
    If I create a PO with the material group from 1 - 50 i.e. two or theree materials which belong different material groups the release is not applied for that PO.
    For the same materials  if I create PO for individual material i.e. only single material group the release is applied.
    The release for PO isconfigured at header level. but the material groups are at item level.
    Thanks & Regards
    Sachin

    Hi Sachin,
    PO release strategy is only in header level not item level. So u should not consider Plant & Material Group as both the fields are in Item level.
    Our release strategy willl work if the palnt & material groups are same for all the line items.
    If there are multiple combination of plant & material group then release strategy won't affect.
    Reward points if its helpful to you.
    Sangram

  • PO release startegy "common issue"

    if release strategy cirtera contains item level characterisitc then if po contains multiple line item with differnet values agains that char. then system does not blocks the PO and for time being let us say PLANT / MAterial group as char.
    now this issue is encountered by every one but i could not find the solution for this (i know the reason behind this issue but i dont know the precise solution some consultants say to maintain the blank value in char  value but i dont think system accepts blank value for char like plant/material group)
    i hope to get some soild reply

    so finally this is the solution for the issue
    Unfortunately there is no mechanism like entering a blank or * in order to make classification understand this characteristic is not relevant.
    The characteristic and its values will always been taken in consideration.
    In case you use a 'non-aggregated' field in your release strategy you need to enter all possible values for the corresponding characteristic (as a range - just in case of numeric characteristics).
    Example: You use item-wise release strategy for purchase requisitions
      and the plant is used in the release strategy (characteristic
      CEBAN-WERKS).
      Release strategy determination will be processed item by item.
      There will always be just one value for the plant (from the current
      item), multiple values and thus aggregation is not possible.
      In this case you have to enter all possible values for the
      characteristic CEBAN-WERKS.
    In case you use an 'aggregated' field in your release strategy (which is possible for overall release strategy for PRs and release strategy for POs) and multiple values are used for that field on a purchasing document, you can use a blank value for the corresponding characteristic if you'd like the release strategy be applied.
    Example: You use release strategy for a PO and the plant is one of the
      relevant fields (characteristic CEKKO-WERKS).
      You enter a first PO item with plant 0001 and a second item with plant
      0002.
      Since there are multiple values for the plant the system will
      'aggregate' to blank value and use blank value for searching for a
      release strategy.
      Since you have maintained a blank value for characteristic
      CEKKO-WERKS the system will find the corresponding release strategy.
    In this case please pay attention to note 732566.
    It causes an error in case blank values are used for release strategies.
    Even when the long text just talks about process orders the impact of the side effect is more general.
    Please take care note 754178 is implemented, it corrects note 732566.

  • Release Authority Issue

    Hi Experts,
    The senario is as a SOX measure we want to restrict the USER from releasing the PUR Doc. created by himself.
    Means Person who has created document should not be allowed to release the same.
    Is there any workarround.
    Thanks in adv. for the help

    Badi - ME_PROCESS_PO_CUST   Enhancements for Processing Enjoy Purchase Order: Customer
    Check it gets called on release
    Create a message, on Check/Save issue error if Approver = PO Creator.  I'm assuming there is more than one potential approver at the level, otherwise you need to determine a different approver before PO is saved.
    See also Exit
    M06E000  Role determination for release of purchasing documents
    You should be able to get what you want with one of these.
    Regards,
    Nick

  • PR item release workflow issue

    Hi All,
    I have 1 issue with PR item workflow. We have PR itme based workflow with different agents for each line item.
    The issue is when approver goes to execute the work item, all the other items are available to the approver to edit or release other items as well. We want to disable other items being available to the approver for which he is not the approver.
    Thanks and Regards,
    Srikar

    Hi Srikar,
       You can do this by using parallel processing in workflows. I am giving you the scenaio we use. We use this in invoices with multiple line items.
    This scenario is implemented using a sub workflow. In the main workflow when you insert a multistep task, go to "Miscellaneous" tab to implement parallel dynamic processing. here you have to pass a multi line container element containing line item numbers. Your sub workflow will trigger one for each entry in multi line element. Do not do any changes to you PR object with in Sub Workflow just get the results of decisions taken by user back to main workflow. Like (App - for approval, Rel - For release, Rej - for rejecetion, etc). When you have all decision collected and returned to main workflow, pass the results in a multi line container element to an activity. Then based on results decide weather you want to release or reject.
    Doing this if one person releases his line item, it will not effect the other workitems which have gone to other approvers.
    We do agent assignment based on profit centers.
    Best of luck.
    Regards
    Anuj Nagpal.

  • Segment Release version issue - ECC6 to older ver.

    Hi
    Our system was recently upgraded from ECC5 to ECC6 and we are facing an issue with one of the interfaces that is connected directly to the R/3 System.
    This issue is realted to an outbound interface and it used to work fine when we were on ECC5. The message we are sending is a bespoke extension based on basic type DELVRY03. The segment E1EDL24 have new fields added to them in the 701 release version compared to the 620 version which was the higest available on ECC5.
    I tried reducing the IDOC segment release version to 620 and 46C in the partner profile, but the message received by the thirdparty still contains the new fields which is causing an issue at their end.
    I would appreciate if you could provide me some guidanace on how to appraoch this issue.
    Thanks & Regards
    Praveen

    Hello Guy's,
    We have recenlyt upgraded our quality system to ECC6.
    I am also facing the same issue, As per my unnderstadning if I put segment release in WE20 then in ALE communication Layer Idoc should remove the fileds which are not intended for the given release. For example E1EDP01 is having highest release 008 for 701 release. If I set 40A in partner profile the Idoc should generate with fileds only available in 40A release i.e. version 003,but SAP is filling all thefilds which are available in701 relase.
    I don;t understand why SAP has given such a functionality though it actually not filter the data at communication layer!!.
    Could you please let me know did any of you really see the difference when you use segment release in WE20 when using PI as receiver? I did sevaral test for MATMAS, ORDERS found this segment release is useless.
    If you have applied any workarounds(other then updating receiver system mapping) please let me know. I think is there any modification in ECC6???
    Edited by: Naresh Reddy K on Jun 7, 2010 3:30 PM

  • PR release workflow - issue in mulitple level approval

    Hi Experts,
    I have developed a new workflow for PR release strategy.
    Business object: BUS2105 ( Purchase Requistion )
    Triggerring event: ReleaseStepCreated
    Step1: Workflow started ( Releasestepcreated)
    Step2: Approve PR ( Agent1)
    Step2a
    If yes --> Released to next level (Agent 2 )
    Step2b
    If No --> Rejected and notified initiator
    If Yes --> Notify intiator and exit
    Step3b.
    If no --> based on next release code and release
    group get the next level agent and go to
    step2
    Step4: Workflow ends.
    Issue:
    For single step PR release, workflow is working fine.
    When PR created with multiple level release, a workflow triggers and notifies the 1st level agent, when the agent releases the PR at 1st level and saves it , workflow is not proceeds to further steps to find the next level agent.
    Here i am using the FM to fetch the approvers and assigning the same for release codes.
    Please guide me...

    Hi
    ''workflow is not proceeds to further steps''... do you mean that RELEASESTEPCREATED event is not triggered for next step ?
    you can check this in SWEL that whether event is getting triggered after first release.
    If yes then the issue is in configuration of release strategy where for all release code you need to mark workflow parameter 1.

Maybe you are looking for