Reject in release process of Contract

Hi Friends,
This is in ref. to release procedure for contract.
We have three release codes 00, 01,02 in perticular release strategy. 00 and 01 has been approved. Now it is pending with 02 to approve. He don't want to approve & want to reject so that it goes to 01 or 00 level.
I checked in system & sap.help.com, in which I didn;t find the solution. Is there any way to do this.
We can do this in Purchase order.
Thanks & Regards
Sai Krishna

Hi,
Check whether it is possible through maintaining the release indicator as reject which is maintain or called in release status of the release code.
Regards
Ravi Shankar.

Similar Messages

  • Release button Disabled whilst processing a Contract in EBP.

    Hi,
        we are on SRM 3.0 / EBP 4.0 ECS.User is trying to process a Contract in EBP,But the release button is greyed out.How can the Release button be Enabled.
    Thanks
    Rakesh.

    Hi,
    Normally when the contract has an error message, release button is not enabled.
    If you click on check button, is there any message available in the bottom of the screen?
    Kind regards,
    Ricardo

  • Define Release Procedure for Contracts in RE-FX

    Hi Gurus!
    I´d like to implement the release procedure for contracts in RE-FX similar at the MM module? Is it possible?
    I didn´t find in RE-FX.
    Thanks,
    Brunoro

    Hi Brunoro,
    To the extent I am aware in REM exact release process is not available. Instead you can control the Creation/Activation of contract by resticting access to activity 01/07 (respectively) in your seperate roles (with the help of Basis team).
    The person authoriosed for Activity 01 will not be authorised for activity 07. And communication between two users can be chanelled via worklist.
    Regards
    Rohit

  • ESYU: Planner Workbench Release process가 다른 user로부터 planned orders를 release

    Purpose
    Materials Requirement Planning - Version: 11.5.9 to 12.1
    Information in this document applies to any platform.
    11.5.9 ~ R12 version:
    두 명의 users가 MRP Planner Workbench에서 Release를 위해 records updating을 진행하는 경우, 두 명 중 한명만이 update 후 실제로 release를
    submit 했으나 두 명 user의 모든 records가 release 되어 버린다.
    User1은 자신의 Planned Orders 만을 release 할 수 있고, User2 또한 자신의 저장된 Planned Orders 만을 release 해야 한다.
    STEPS:
    1. User 1이 MRP Planned Workbench로 log
    2. User 1은 특정 planner code를 위한 current planned order recommendations 을 찾는다.
    3. User 2가 MRP Planned Workbench로 log
    4. User 2가 특정 planner code를 위한 current planned order recommendations 을 찾는다.
    5. User1은 All for Release를 선택
    6. User2도 All for Release를 선택
    7. User1은 checking process를 끝낸 후 저장
    8. User2는 아직 checking process를 끝내지 못해 save를 아지 않은 상태로 남아 있다.
    9. User1이 [Release] button을 선택
    10. User1이 [Release] button을 선택시 User1과 User2에 의해 저장되거나 check 된 모든 planned order recommendations이 Work in Process와
    Puchasing modules로 released 되어 버림
    Cause
    이 issue의 원인은 현재 MRP planning의 경우 expected functionality 이다.
    MRP Workbench Release process는 모든 planner에 의해 check 되거나 저장된 모든 planned orders를 항상 release 한다.
    Bug 891669 : Enhancement Request
    PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
    It is explained that this is current functionality in the following rejected Enhancement Request:
    Bug 891669 : PLANNER'S WORKBENCH SHOULD RELEASE ORDERS BASED ON PLANNER NAME NOT BY BATCH
    Solution
    Solution을 적용하기 위해 아래 steps을 실행:
    1. 모든 planner에 의해 check 되거나 저장된 모든 planned orders가 [Release] button에 의해 항상 release 되는것은 현재 MRP Workbench
    Release process에서는 correct functionality 이다.
    2. ASCP Planning의 경우엔 Planner/User에 의해 Release process가 아래 option에 의해 처리 가능하다.
    -- profile MSC:Released Only By User
    -- Standard MRP에서는 이 option은 사용할 수 없고 고려되지 않는다.
    Reference
    Note 311053.1

  • Configure Release Strategy for Contract

    Hi All,
    I want to Configure Release Strategy for Contract.
    I have configured Release Strategy  for PO. Is the process for both is similar?
    What should the table & field name should we use for configuring Release Strategy for Contract.
    Pls. guide.
    Regards,

    Thanks Neeraj for the reply.
    For PO, I have used Table CEBAN, Field BSART, GNETW.
    Could you pls. suggest what fields should we use.
    Also tell me what would be process of releasing the contract using ME35K, as the Screen seems to be different from ME29N.
    Regards,

  • Release PO against contract whit limit value for USER

    Dear colleague,
    We work SRM server 5.5 . SP14 extended classic scenario, and we use contract management.
    We need to release PO against contract and we want to LIMIT the users that PO value have  to be between 60 USD as minimum order value and 120 USD as maximum order value.
    We know that solution for the minimum order value is to use the u2018minimum order valueu2019 in the contract item with the value 60.
    Can someone help with the solution to limit user to maximum order value against contract.
    Thanks
    B.R.
    Gil shinar

    One option is that you could implement the maximum value logic in BADI BBP_DOC_CHECK_BADI and give out proper error message if the user enters value outside of the range.

  • Open Order quantity in Release order of Contracts

    Hi all,
    We are developing new PO format for Release Order ( Contract) where in we want to print the Open order quantity & Open order value along with Contract number.
    What is the best logic for Open order quantity, where in it has consider all the previous release order quantities minus the target quantity in contract.
    Open order quantity = target quantity in contract - all previously release order quantities.
    Thanks in advance.
    MM
    MM

    hai sajid,
    As u said,
    open order quantity = total quantity in contract - total quantity released against that contract ( Through release orders )
    it is right,
    with regards
    srinivas

  • Function Module to find out the release value in contract

    Dear All,
    I have to upload the contract with new accoutn assignment without changing the existing contract. For that i have to download all the existing contract data with value.
    In that case i have some issues regarding the value.
    For example : In the system old contract is created with value 1000 and the released value as 500.
    In that case i have to uload the new contract with all the details of existing contract with value of 500 (1000-500=500).
    How can i get the value (500) and from which table.Is there any functional module to find out the release value in contract.
    Thanks and regads,
    PM
    Edited by: PM on Jan 21, 2010 8:40 AM
    Edited by: PM on Jan 22, 2010 9:48 AM

    Hi
    You need to link the table VBFA and VBAK.
    For a contract you can check all the subsequent document (which you can filter whether you want to see Order / delivery / Billing) in VBFA and then from there pick the subsequent document no. and then from VBAK you can pick the Net value of these subsequent documents, and so you will have both the values (value of Contract and value in subsequent document) and you can determine the balance value.
    Regards
    Amitesh Anand

  • Release process problem

    Hi,
    I have a problem. currently our system using based on PO document type and net value to trigger release process. now new requirement to use based on account assignment item level so, po doesn't support line level i decided to use CEKKO - USRC1 = KNTTP based on user exit.
    When i set-up charecteistics and assign vaues
    then class assigned to charecteristics ( existing it self)
    When class assignment with release code values.
    Now when i create PO release process are not triggered please through me some lite whether config prob or user exit any thing need to done.
    Regards
    Jask

    goto transaction OMGSCK and check that alll steps are green except the sheckk re release group and releae class step
    in this step 
    Characteristic CEKKO_USRC1 exists (linked with CEKKO-USRC1) =  green
    You must maintain a customer exit for characteristic CEKKO_USRC1= yellow
    if this all looks fine then the master data problems or PO ceration problems

  • Release strategy of contract disappeared after using of  MEMASSCONTRACT

    Hi  All,
    May be some one can help me?
    I have next problem it tr. MEMASSCONTRACT(ECC6)
    Release strategy of contract disappeared after using of tr. MEMASSCONTRACT. I know why it happened, but I don't know how to correct it. Some time ago IN ECC5 we added a field to a table EKKO and used this field as one of characteristics in the release strategy of contracts. In order to transfer value of this field to field CEKKO-USRC1 we used User Exit EXIT_SAPLEBND_002. This User Exit is suitable only for online transactions (ME31K, ME32K). How can I feel field CEKKO-USRC1 in transaction MEMASSCONTRACT?
    Regards, Liza

    Thank you. Probably I didn't explain my problem clearly. It's section of code from User Exit EXIT_SAPLEBND_002:
    ATA: reference(20) TYPE c VALUE '(SAPMM06E)EKKO'.
    DATA: it_ekko TYPE ekko.
    FIELD-SYMBOLS: <ymm_icl> TYPE ANY.
    e_cekko = i_cekko.
    *THE "ICL Contract" FIELD IS ONLY RELEVENT IN THESE TRANSACTIONS
    IF sy-tcode EQ 'ME31K' OR sy-tcode EQ 'ME32K'
    OR sy-tcode EQ 'ME33K' .
      ASSIGN (reference) TO <ymm_icl>.
      it_ekko = <ymm_icl>.
      e_cekko-usrc1 = it_ekko-ymm_icl.
    ENDIF.
    Program SAPMM06E can only be reffered while using online transactions. Mass transactions does not use these program and it is completely class based. So,  may be someone know how can i do the same , but for tr. MASS in ECC6.

  • Purchase Order not subject to release strategy for contract rel. strategy

    Hello, I am trying to set release strategy for contracts (TCODE: ME31K). I have created characteristic, which use table CEKKO and field name BSTYP in Addnl data tab. I have checked values, and they are correct. Then I have assigned in release strategies in classification view value contract. But when I try to check release strategy in ME31K with green flag, it display error: Purchase Order not subject to release strategy. (I have tried to do the same strategy in purchase order, of course with value Purchase order, and it works nice).
    So I have checked this release strategy with this codes:
    CL24N ok,
    CT04 ok,
    CL30N ok,
    CL20N ok,
    Release simulation in release strategy works,
    Then I found out that I should check SE38, SE37 but I do not understand how to use them (according: Purchasing Document Not Subject to Release Strategy).
    Thank you for your help in advance.

    I haven't said to use EKPO table in characteristics. You have to use CEKKO - BSTYP in characteristics.
    I've just said the compare the value which you have given in Release strategy - Classification and EKPO table for the particular contract.
    Also compare your release strategy settings with many existing documents in SCN.
    Check your Classification should be like that.
    You may see the error message in ME31K. Just save the contract then go to ME32K/ME33K or ME35K you can see the release strategy will effect for the contract.

  • Problem in reversing the released Process order.

    Hi PP Gurus,
    When I'm trying to reverse the Process order release in change process order COR2 system is not allowing me as the menu option is Gray. When I released processed order Control recipe is generated and due to some problem in PI sheet I discarded in CO60 transaction code. So can anybody please tell me how to handle this situation? I mean is this can be resolved by configuration or enhancement?
    Thanks & Regards,
    Abu Arbab

    Hi Krishna,
    Thanks for reply.
    Now tell me what should be the approach we if we don't want to delete the Process order? Say PI sheet is created and sent to it's destination through Background job and later we found some error in PI sheet so and we've discarded that PI sheet. In case when I don't want to delete or Teco Process order, what will be the process in this case?
    Thanks & Regards,
    Abu Arbab

  • How to make invoice verification process non-release process?

    Hi friends,
    I am doing incoming invoice verification (MIRO), once post it, I will have a message saying (document XXXXXX was created (document is blocked)). then I have to go to T-code MRBR to release it.
    My question is: where could configure this process to be an non-release process?
    Thanks,
    Linda

    Config. path.
    MM \ LIV \ Invoice block \ Set tolerance limits
    See also Item amount check (same path) in case this has been activated too.
    Though presumably you want to have some tolerances unless it's a sandbox system.
    Cheers,
    Nick

  • PR/PO release process

    Need help SAP gurus!!! =)
    Our company has many approvers, so I maintained the appropriate release codes and strategies for the PR/PO release process. Now, they will have to release it using ME55. In the transaction, you will input the appropriate release code specific of the approving user.
    What I want to happen is, Once the approver will use the ME55 transaction its release code will automatically appear and it can not be change. How can I solve this? I tried creating a Transaction Variant, but still my problem can't be solved. PLS help! Many Thanks! =)
    Mik

    Hi Buddy,
    Option 1:
    In ME55 screen, enter the Release code and go to SYSTEM-User Profile-HOLD DATA.
    Once done acknowledgemetn message prompt as "Data was held"
    Try to execute for first time then go out to the screen try again to execute the ME55 you will see that the relecode is defualted.
    Option 2:
    In ME55, enter the release code and SAVE as variant. Once done try to execute for first time. Then go out to that screen.
    DO again ME55, rel code will be defaulted also.
    Hope this solves your issue.
    regards,
    Maia

  • 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

Maybe you are looking for