Release Purchase Requisition - "Release strategy"

Hi there,
I am trying to release a purchase requisition. I looked in the table "EBAN" and i can see the entry or in other words, the requisition i created. In the Release indicator, Release status and Release strategy fields, these are empty. How do i add information to these fields which appear to have missing data?
Speedy repsponse would be very much appreciated.
Thanks
Motolani Fatuga

Hi Motolani
spro>Materials Management>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Release strategy
Select release strategy> Go to details>classification
here check what are the charactaristic and what are the values maintained for it
Check this for all release strategy
Mostly PR release strategy is based on Document type and PR Value
Check whether UR PR fits in release strategy criteria
Suppose Total value of requisition is maintained as 1000-2000
If UR PR value is less than 1000 Then PR will not subject to release
Vishal...

Similar Messages

  • 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

  • Purchase requisition release strategy

    I want each purchase requisition should be created with valid release strategy. The problem presently is that if somebody puts wrong parametes (such as purchasing group, currency) the purchase requisition will not be applicable to release and the purchase order can be easily created. So in such cases there is no need to release purchase requisition which is not correct for business point.
    Pls advise.

    Hi Balaji
    Ur need is appreciated but inorder for that to work we have to make sure that all the possible combinations exist in ur characteristics list which may not be possible all times.
    So better way would be to check whether the characteristics combinations of ur class and the corresponding data of ur requisitions matches and trigger error msg if differs.
    Ex: Plant and doc type be the characteristics used in ur class.
    Check whether the PR has only the plants and doc types that is specified in ur release strategy and if no trigger error msg.
    Try this using BAPI also. Get help from ur ABAPer.
    Thx
    Raja

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

  • 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

  • Workflow for purchase requisition release strategy

    Hi all,
    I need an urgent help on Workflow for Purchase Requisition Release. The requirement is that when a purchase requisition with a given combination (Purchasing Group, Material Group and Account Assignment Category) is created and saved, it should trigger a workflow for approval of release or rejection to one specific business manager. If he dont responds in 2 days, it should be sent to other business manager. If any one of them releases the requisition, it should send a mail to the requestor that the requisition is released. And if it is rejected, then also a mail to be sent to the requester informing that his requisition is rejected...
    Can anyone take some pain and guide me step by step procedure to implement this or to use any existing one.... I know its BUS2009 thats used in this but really dont know how to implement it properly.
    Its urgent...
    Edited by: Hima on Apr 11, 2008 12:45 PM

    Check this link
    http://help.sap.com/saphelp_47x200/helpdata/en/04/92762546f311d189470000e829fbbd/frameset.htm
    Thanks
    Arghadip

  • Purchase Requisition Release Problem

    Hi All,
    I have a release procedure set up, and the strategy pulls up correctly when a PR is made.  When I view collective release from ME55, the PR's show up, and I am able to release line items from that screen.  However, when viewing the PR from ME53N, in the Release Procedure tab there is no green check next to the release code with which to release the line.  Also, if I do release the PR from ME55, I cannot go to ME53N and cancel the release from the Release Procedure tab. 
    I am a user with all security access, so it is not an authorization role problem.  The release group is also configured to release by line item, so that is not the problem.  I have set up other release procedures which allow the release/cancel release function from ME53N before... what could be the problem this time?
    Thanks,
    J

    hi.
    There are two ways of releasing purchase requisitions:
    Individual release  (Tcode - ME54)
    You release items of an individual purchase requisition or - if the requisition has to be released in total - by releasing one item you simultaneously release all the others.
    Collective release (Tcode- ME55)
    You release all requisition items or complete requisitions that are awaiting processing by your release code. This is the preferred method if you frequently have to effect release.
    Display PR -with release status  (Tcode-ME53N)
    One can only see release status in ME53N & can not change release.
    hope it helps to you.
    Regards,
    Rahul

  • Purchase Requisition Release Procedure Modification

    Hi
    In Purchase Requisition Release, we have two deviations in business requirement from standard SAP behaviour:
    1. In multistep release, system allows PR release to be revoked by a lower level release authorized person even though higher level release has been done. Example, PR Release has release codes A1, A2 and A3, A2 can revoke release even after A3 has released the same. How do I prevent this from happening?
    2. If business requirement is to have release procedure based on item cost per unit and not on total value of the line item, how can this be achieved?
    Appreciate any guidance on these issues
    Thanks
    Sriram

    Hi,
    There is BADI ME_REQ_POSTED 
    in method POSTED  you can write your code to trigger the workflow and get the information related to release strategy and
    Purchase requisation  .
    for more than one PR use below logic .
    LOOP at im_eban into gwa_im_eban .
        concatenate gwa_im_eban-banfn gwa_im_eban-bnfpo into gwa_objkey .
      add data into container -----------------
          gwa_event_container-element = 'PurchaseRequisition'.
        gwa_event_container-value = gwa_im_eban-banfn.
        append gwa_event_container to gi_event_container.
        clear: gwa_event_container.
        gwa_event_container-element = 'ItemOfRequisition'.
        gwa_event_container-value = gwa_im_eban-bnfpo.
        append gwa_event_container to gi_event_container.
    get the other details and create event to start workflow .
    select single * from eban into lwa_eban where banfn = gwa_im_eban-banfn
                                                  and bnfpo = gwa_im_eban-bnfpo .
            if sy-subrc <> 0 .
          call function 'SWE_EVENT_CREATE'
            exporting
              objtype           = 'BUS2009'
              objkey            = gwa_objkey
              event             = 'zcreated'
            tables
              event_container   = gi_event_container
            exceptions
              objtype_not_found = 1
              others            = 2.
    ENDLOOP .
    Hope this will resolve your issue.
    Thanks and Regards,
    Deepanker Dwivedi

  • Purchase Requisition release

    Hi,
    Could anybody help me out with the configuration settings of purchase requisition Release.
    Client want to set release status for Purchase Requisition , where two persons will be responsible to release the requisition . when the first person releases the requisition , it will come to the second or final person for release ,when he releases then the requisition is released for purchase orders.
    Could anybody help me out with the configuration settings.
    Thanks N Regards,
    Siddhartha

    Use this steps. below is for PO same do it with PR. that is in place of PO take it as PR.
    Releasing Procedure for Purchase Documents
    Use
    This setting is incorporated to just give demonstration of how SAP Release procedure works.  The aim of this procedure is to replace manual written authorization procedures using signatures by an electronic one, while maintaining the dual Ctrl principle.  The person responsible processes the purchasing document in the system, thereby marking it with an "electronic signature" which can give the document legal force.
    3.4.24.1     Creation of Characteristics
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Characteristic
    Transaction Code     CT04
    2.     On the Characteristic screen, make the following entries.
    3.     In put POVAL in filed Characteristic and choose Create (White paper) icon or Ctrl + F3 to begin creation of characteristic.
    Field name     Description     User action and values     Note
    Select Addnl Data tab                
    Table Name     Table Name     CEKKO     
    Field Name     Field Name     GNETW     
    Choose Enter to continue, system will give an information message saying Format Data taken from ABAP dictionary, Choose Enter again to continue.
    Select Basic Data tab               
    Description     Description     Total net order value     
    Status     Status     Released      
    Data Type     Data type     Currency format     Selected by system
    Number of characters     Number of characters     15     
    Decimal places     Decimal places     2     
    Currency     Currency     INR     
    Interval vals allowed     Interval values allowed     Check this tick box     
    Multiple Values     Multiple values allowed     Select this radio button      
    4.     Choose Enter to complete the entries
    5.     Choose Save icon or Ctrl + S to save the characteristic.
    3.4.24.2     Creation of Class
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Edit Class
    Transaction Code     CL02
    2.     On the Class screen, make the following entries:
    Field name     Description     User action and values     Note
    Class     Class     PORELPROC     
    Class Type     Class Type     032     
    Choose Create icon or white paper icon to create new class.
    Description     Description     Purchase Order Release Procedure     
    Status     Status     Released     
    Choose Char. Tab to input characteristic name.
    Characteristic     Characteristic     POVAL     Created in above step
    3.     Choose Enter to complete the entries
    4.     Choose Save icon or Ctrl + S to save the characteristic.
    Result
    Class type 032: Class PORELPROC created.
    3.4.24.3     Configuration of Release Procedure
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Materials Management  Purchasing  Purchase Order  Release Procedure for Purchase Orders  Define Release Procedure for Purchase Orders
    Transaction Code     SPRO
    2.     On executing the transaction system will give a popup screen choose Release Groups, system will display Change View u201CRelease Groups: External Purchasing Documentu201D: Overview.
    3.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Rel. Group     Release Group     02     
    Class     Class Name      PORELPROC     Created in above step
    Description     Description     PO Release Procedure     
    4.     Choose Enter to complete the entries
    5.     Choose Save icon or Ctrl + S to save the entries.
    6.     Choose yellow arrow to go back to popup screen.
    7.     Choose Release Codes to select.
    8.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Grp     Release group     02     Created in above step
    Code     Release Code     01     
    Workflow     Workflow     Leave it blank     
    Description     Description     Purchase Officer     
    Grp     Release group     02     Created in above step
    Code     Release Code     02     
    Workflow     Workflow     Leave it blank     
    Description     Description     Materials Manager     
    9.     Choose Enter to complete the entries
    10.     Choose Save icon or Ctrl + S to save the entries.
    11.     Choose yellow arrow to go back to popup screen.
    12.     Choose Release indicator to select.
    13.     Choose New Entries icon and make the following entries:
    Field name     Description     User action and values     Note
    Release ind.     Release Indicator     1     
    Released     Released     Leave it blank     
    Chgable     Changeability     4     
    Value change %     Change of value     10%     
    Description     Description     Purchase Order Blocked     
    Go to 2nd line and input the following values:
    Release ind.     Release Indicator     2     
    Released     Released     Select Check box     
    Changeable     Changeability     6     
    Description     Description     Purchase Order Released     
    14.     Choose Enter to complete the entries
    15.     Choose Save icon or Ctrl + S to save the entries.
    16.     Choose yellow arrow to go back to popup screen.
    17.     Choose Release Strategies to select.
    18.     Choose New Entries icon and make the following entries:
    19.     System will give new screen New Entries: Details of Added Entries
    Field name     Description     User action and values     Note
    Release Group     Release group     02     
    Rel. Stategy     Release Strategy     S1     
              Capital Items Release     
    Release Code     Release Code 1     01     
    Release Code     Release Code 2     02     
    20.     Choose Enter to complete the entries.
    21.     Choose Release prerequisites icon and select check box 02 at the bottom and choose Enter.
    22.     Choose Release statuses icon, system will give a popup screen system will default 1, 1 and 2 entries one by one as a default.  Choose Continue.
    23.     Choose Classification icon, here you can see Total net order value is displayed, please input >= 1.00 INR value in the white placed and choose Enter.
    24.     Choose Next Screen icon or choose F8 to continue.
    25.     If you want to simulate the release procedure you can choose Release Simulation icon.
    26.     Choose Enter to complete the entries.
    27.     To save the settings choose Save icon or Ctrl + S.
    Result
    Release procedure is saved.
    3.4.24.4     Assignment of Values to Release Procedure 
    As a default all the purchase documents >= Rs. 1000000.00 is suggested in the following step of release procedure, if you want to have different one you need to change the value in the following step.  If you do not want release procedure you may change the value to Zero.
    Procedure
    1.     Access the activity using one of the following navigation options:
    IMG Menu     Cross-Application Components  Classification System  Assignments  Assign Object to Classes
    Transaction Code     CL20N
    2.     On the Class screen, make the following entries:
    Field name     Description          User action and values     Note
    Class Type     Class Type          032     
    Choose Enter to Assign values.
    Release group     Release Group          02     
    Rel. Strategy     Release strategy          S1     
    Choose Enter.
    System will give Class name in Assignments, Double choose Class Name.
    System will display Characteristic name Total net order value. Assign the value >= 1000000.00 INR  against filed Value.
    3.     Choose Enter to complete the entries
    4.     Choose Save icon or Ctrl + S to save the characteristic.
    Regards
    S

  • Purchase Requisition Release at Header Level

    Hi MM experts,
    We are on ERP6. Can we activate purchase requisition release at header level (ie overall requisition dollar level - sum total of all requisition line items) just for one business (company code) without affecting rest of client which uses release strategy at requisition line item level?
    Is it possible to share the same document type, e.g. NB that is used by other business?
    Many thanks.
    Thomas

    With the release procedure with out classification , it is possible to release the PR at header level based on the value of the PR . In determination of release strategy , you can maintain the value , currency and release stratergy .
    But to restrict this to a particular comany code , you may use the exit M06B0002 where in you can write the logic .
    -Hari.

  • ME51(2/3/4)N Reset release purchase requisition

    Hello,
    I need to reset the issue of the purchase request after a specific condition occurs.
    To reset the issue I found the user exit EXIT_SAPLMEREQ_010
    (Includes ZXM02U12 MEREQ001 and extension).
    I first used this function:
          CALL FUNCTION 'ME_REL_STRATEGIE_EBAN'
             EXPORTING
                i_eban_new           =  wa_im_eban
               I_EBAN_OLD          =  IM_T_EBAN_PERS
               I_EBKN_NEW          =  IM_T_EBKN
               I_EBKN_OLD          =  IM_T_EBKN_PERS
              I_XCLASS             =
              I_CHANGE_OK          =
              I_CHECK_ALWAYS       =
             IMPORTING
               E_EBAN                =  wa_eban
               E_RESET               =  wa_ereset
    but I did not understand how to use it.
    Then I used the field-symbol:
    DATE f_FRGKZ (30) VALUE '(SAPLMEREQ) EBAN-FRGKZ'.
    FIELD-symbols <FRGKZ>.
    ASSIGN (f_FRGKZ) TO <FRGKZ>.
            MOVE 'X' TO <FRGKZ>.
    But a dump is generated on the move: Error at assignment: overwritten protected field.
    HELP ME - I don't know what to do.
    Edited by: Ermelinda86 on Jul 8, 2010 10:36 AM

    Hi Ermelinda86,
    I had a problem similar to what you're experiencing. I solved by changing appropriately customizing.
    The route from the transaction "spro" is as follows:
    Material Management --> Purchasing ---> Purchase Requisition ---> Release Procedure -
    > Procedure with classification ---> Set Up procedure with classification -
    > Release Indicator     
    Material Management --> Purchasing ---> Purchase Requisition ---> Release Procedure -
    > Procedure with classification ---> Set Up procedure with classification -
    > Release Strategies ---> Release Statuses
    I also found a useful guide at this link:
    http://www.sap123.com/a/59/
    Bye
    Prode

  • WS2000077 (Purchase Requisition Release) problem

    Dear all
    workflow task WS2000077 (Purchase Requisition Release) causes the following problem:
    While executing an approval release (ME54N) through workflow, the result is always 'requisition release refused'.
    Does anyone know why?
    I appreciate your help in advance

    Hi,
      Go through the below links it may help you...
    Workflow Definition WS20000077 and sequence of the events, significantly...
    po release workflow issue/problem
    PR Workflow problem
    std workflow ; user to role agent assignment ?
    Regards,
    Udaya.

  • Purchase requisition release - reg.,

    Hi guru"s
    When Iam releasing purchase requisition one item is not getting into release? can anybody explain what is the problem
    thanks in advance
    tulja singh

    Hi,Tulja
    what is the message u r receiving when u release it. based on that we will try to dignose the problem
    frindly
    manickss

Maybe you are looking for