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

Similar Messages

  • Release code - Purchase requisition - Release Procedure

    Hello,
    In the purchase requisition release procedure with classification, we are defining release codes say K, P etc.
    My doubt is , Is this being defined else where based upon the designatin of the person in the organisation, or else, we are defining here straight away?
    Best regards,
    K.Kumaran.

    HI
    You are correct, you need to define the release code there only. There is no other place where it is defined. What you have to ensure is  make sure that it is of Two character and not single. Assign the codes against the designation of the person as per your requirement.
    Regards

  • Purchase requisition release procedure through User-Exit

    Hi Workflow Guru,
    I have a requirement to configure purchase requisition workflow . the workflow should trigger through release strategy.
    The approver should determine through user-exit and the approver should determine based on value and quantity and that can be define in user-exit. as per my knowledge the value should mantain in SPRO-Release procedure. Please clarify me is it possible through user-exit. I am worked on user-exit for release procedure based on purchasing group.
    Thanks in advance.
    Regards,
    Ranjan Tiwari

    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

  • Requisition Release Procedure No longer working

    Hi expert!
    My client raised an incident regarding the PR release strategy. Their Requisition Release procedure is based on document type.The user that is creating the requisition has the option of choosing document type NB (Non Release Requisition) or document type RNB(Release Requisition)
    If they choose NB the requisition will not go for Release.If they choose RNB the requisition will go for release.
    Then they created a new Purchase Requisition doc type(ZTP) and the transport has been moved to PRD. No config changes were made to the Purchase Requisition release procedure. Now the requisition release procedure is no longer working.
    I'm not sure why it's happen like this.Can anyone explain?

    Hi ,
    The transport request has nothing to do with your earlier release strategy.
    Just check the charactersitics values linked to Release Strategy.May be someone might have changed it in production.
    Regards
    Ramesh Ch

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

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

  • 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

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

  • Purchase Order release procedure

    Hi All,
    My client is having following requirement for Purchase Order release procedure.
    Plant 1                    -    1 Release code (Manager)
    Plant 2             -    2 Release Codes (Manager, Sr Manager)      
    Plant 3             -    3 Release Codes (Purchase Officer, Manager, Sr Manager)     
    All plants are assigned to one company code. Please advise me how I can map above requirement in sap.
    Thanks & Regards,
    Nagi

    Hi Nagi,
    In PO Realease startegy configuration, you need to decide and select the Release objects for which the system should trigger release for the document. you should work with Characteristics for each object (Your requirement is for 3plants) so in one of your characteristic WERKS should be your field along with other characteristics based on your requirements such as Total Net Value, Doc type etc.
    Create Characteristics in CT04 for the class type 032 and proceed maintaining the release Group and Release codes as per your requirement.
    Refer the following thread and revert if any confusions...
    http://**********************/2008/11/release-procedure-release-strategy-main.html
    Regards
    Shiva

  • 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

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

  • User Exit for me54n on purchase Requisition Release i.e EXIT_SAPLMEREQ_05

    HI   All Experts ,
                          I have one Requirement that  , i want to insert  data in Ztable  using all details from header data in me54n  on purchase release i.e When i will Click on Purchase release Requisition i want to insert records using few fields such as , matnr ,menge , item, quantity ,requisioner,plant storage locaton , date etc  . i am using user exit on this i.e smod EXIT_SAPLMEREQ_005 in mereq001  which is called when clicked on purchase requisition release , now how to collect that details  in this user exit .
    need some help regarding this .
    Thanks And Regards
    Deepak Dhamat

    Dear Peter ,
                   yes you are correct that ebeln is part of structure MEREQ_ITEM but  it is always empty .i want Purchase Requisition no i.e     PR. Manual           2000009940  which is present in me54n first line of screen  i.e above the header note .
    after looking at the property  of that field it show as given
      below
      Struct.          MEREQ_TOPLINE               
      Field name       BANFN_EXT                   
      Data element     BANFN                       
      DE supplement    0                           
      Parameter ID     BAN                                                                               
    Screen field     MEREQ_TOPLINE-BANFN_EXT     
      Program name     SAPLMEGUI                   
      Screen no.       0014

  • TWO CURRENCIES IN ONE Purchase Orders Release Procedure.

    TWO CURRENCIES IN ONE Purchase Orders Release Procedure.
    Please provide a solution if a release strategy is maintained for two currencies like USD and SGD for more clarification please Read the below Requirement.
    Requirement for Singapore:
    u2022          COMPANY Asia (Singapore) wants its own Purchase order release strategy is based on their local currency (SGD)
    u2022          Whereas COMPANY is using only USD as currency in Purchase order release strategy.
    u2022          Standard SAP works based on Character currency which is defining in Class of Purchase release strategy and converts with Local currency to compare with Character Currency.
    Required analysis:
    u2022          The value assigned in classification is based on Conversion from SGD to USD, Due to Exchange rate fluctuations the assigned value is differ by large amounts and hence system is either determining the higher release strategy or Lower release strategy
    u2022          But during Release Strategy Configuration the Net order Value is assigned as 3600 USD considering the Exchange as 1.388889.
    u2022          As per the exchange rate in the purchase order 1.3799 the system is calculation the PO Net order Value but the Strategy is Determined based on the value maintained according to exchange Rate 1.388889
    In the Purchase Order the system is 
    Ex:  Total Purchase Order Value is 4765.21 SGD and 3453.30 in USD
          For Level 1 the value limit is 5000 SGD if it exceeds 5000 SGD it has to go to his manager (Level 2) Exchange rate on 01.04.2008 is 1.3799.
    System Considerations:
    Possible Solution:
    1.        Create a new Class with Characteristic with Currency Value SGD System should determine the class based on the combination of Plant 6000 and Document Category F Purchase Order.
    2.        By using Enhancement spot with Function Module ME_RELEASE_STRATEGIE/ ME_RELEASE_STRATEGIE_EKKO
    Logic:
    1.        System will determine the class PUR_RELEASE from table T16FG if the system finds Plant as 6000 and Document Category as F Then replace PUR_RELEASE with New class as ZPUR _6000.
    2.        Maintain Z table for the combination of Plant and Class for future requirement
    Edited by: Mohammad Irfan on Jun 8, 2009 10:41 AM

    Hi Mohamed,
      You can create separate characteristics far all check points and assign those to class.
    Regards,
    Prasath

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

Maybe you are looking for