Release strategies for purchase requisitions

Hello,
I'm having trouble with profiles and roles for release strategies, this is the scenario:
-for purchase requisitions we have two approval levels, release code S1 and S2. When release code S1 is cleared, then S2 must be approved. The head of a certain purchasing group will use S1 to approve the requisitions from his own department, and then the financial director will approve with S2. However, finance is also a purchasing group, so in some instances the finance director will have to approve with S1 and then S2.
My question is: how can we use profiles and roles so that the finance director has access with S2 to all (*) purchasing groups, but with S1 for only a certain purchasing group (in this case "500")? we can't seem to be able to define certain purchasing groups to different release codes, purchasing groups must be defined at purchsing requisitiom level.
Many thanks
Daniel

HI,
Not necessarily, you just need a different strategy for each different combination of release codes involved.
So if certain P groups need to be put through a different sequence of approvals, then have one new strategy for this group of P groups and one for the other combination of P groups.
Or however many different variations you have.
Steve B

Similar Messages

  • Release strategy for purchase requisition does not kick in

    Hi Gurus!
    I've been struggling with this issue for some weeks now.
    I have set up the release strategy configuration for purchase requisitions with classifications.
    However, if I create a purchase requisition the release functionality is not taken into account by the system.
    See below some more information regarding my configuration:
    1. I've created a new characteristic "REL_PR_GROUP". Status: released, Multiple values, Number of Chars 3, 7 values (TR1, TR2, TR3....TR7), Table name: CEBAN, Field name: EKGRP, Procedure for value assignment set to not ready for input.
    2. I've created a new class: "REL_PR_ANPC". Class type 032, Status: released, Same classification: do not check, Char: "REL_PR_GROUP"
    3. I have one release group "T1", Rel. object 1, OverReqRel is marked, Class: "REL_PR_ANPC"
    4. I have 5 release codes. Grp: T1, Code: 01....05
    5. I have 2 release indicators:
    "R = Released", Rel. for ordering is marked, Changeabil: 4, Value chgs. 100,0
    "X = Blocked",  Changeabil: 4, Value chgs. 100,0
    6. I have 1 release strategy:
    "T1 with Grp T1"
    - one release group, 01 Manager
    - release prerequisites not applicable because of only one release group
    - release status, nothing marked = blocked, 01 marked = released
    - classification, purchasing group is TR1 or TR2 or TR3 or TR4 or TR5 or TR6 or TR7
    I intentionally kept the configuration as simple as possible so I can try to get it working first.
    Now if I create a purchase requisition for an item with release group T1, I would expect the release strategy to be activated. However, this is not the case. I don't see the "release status" tab in the PR, and if I try to relase via ME54 the system says the PR is not relevant for release.
    Could you please assist in getting this working?

    Hi,
    Have you checked in CL30/CL30N if your release strategy is derived successfully?
    See section 3 of Note 365604. A small section of it:
    You can use transaction CL30 search for an object using the data
    of the purchase requisition/purchase order. Here, it is important
    that the object search determines exactly one strategy. If this
    is not the case, this indicates that there are overlapping
    strategies in the system or that the release strategies in
    Customizing do not correspond with those from transaction CL24.
    See the previous point. If the object search returns more than
    one result, the system subsequently determines an incorrect
    release strategy or no release strategy at all.
    If it is derived successfully, next, check the user exit EXIT_SAPLEBND_001 as per Note 371667:
    The following assignment statement has to exist within activated SAP
    enhancements M06B0002 (include zxm06u13) and M06B0005 (include zxm06u31)
    for purchase requisitions:
         E_CEBAN = I_CEBAN.
    Regards,
    Purnima.

  • Redetermine release strategy for purchasing requisitions

    Hi Guys,
    How can I redetermine the release strategy for purchasing requisions when changes on the costcenter (EBKN-KOSTL)  are done -
    I know that it will be redermined when I add the costcenter as charateristics in customizing for release strategy but thats not an option
    I also tried to add coding in userexit for changing the communication strategy (Include ZXM06U13) but this exit doesn't provide information of the document number and position (EBAN, EBKN ..) so I can't find out if changes have been made
    I spend several hours trying to find solutions for this issue but no working results so far ..
    I hope you can help me on that
    TIA
    Manuel

    Hi,
    Note that EBKN will have entries corresponding to a PR only when it is        
    saved or checked, so KOSTL will not have any values for a PR which is under              
    creation. You should always use fields from structure CEBAN while             
    creating characteristics for Requisition release procedure as it              
    contains most of the relevant data about a PR under creation/change.
    I would advice you to check the note 365604.
    Please also check the changeability indicator in the customizing:
    transaction OLME -> Purchase Requisitions -> Release Procedure -> Procedure with Classification -> Set Up Procedure with Classification -> Release indicator -> check the detail screen for settings.
    Please check additionally the possible values for your characteristic cost centre (transaction CT04).
    Regards,
    Edit

  • Release Procedure for Purchase Requisitions

    HI
    i have making a class in cl01  then create Release Groups & link to class but when i save a group massage here  Please check release classes (see long text) can anybody help me
    thanks vijay

    pls check the following:
    http://www.sap123.com/showthread.php?t=59
    regards,
    indranil

  • Why release strategies for PO at header level only

    We have release strategy for Purchase Requisitions and Purchasing documents like PO, Contract and SA.
    In case of PREQ we have a choose for either item level release or header level release, whereas in case of PO, Contract and SA only header level release is possible.
    My question is why SAP has provided only the header level Release Strategy for PO, Contract and SA? I wan to know the reason and logic behind this.

    Hi,
    For PR's, there is no header level data. Becuause vendor number is optional since it is internal document from the user dep. to pur org. That's why, vendor number fields is at item level in the source of supply screen. But this is optional field.
    That's why, you can release PR line items one by one or all at a time.
    If you are releasing all line items at a time, need header level release.
    If you release line item by line item, need item level release.
    But in the case PO/Contract/SA, these are final reference documents and sending to the vendor as external documents.
    That's vendor number is at header level field and line item in the PO are related to the single vendor.
    That's why u cann't release line item by item, i.e., item level release.
    You can relase all the  items in the PO or u can reject entire PO, not a single line item.
    That's why, only header level release is possible for the PO/Contract/SA.
    Regards
    KRK

  • Release strategy for purchase requization on basis of document type

    Hi All
    can somebody can explain me the procedure for creating releasing strategy on basis of doc type
    Nabil

    Hi,
    The below link will help you to understand the process.
    Please open the below link and u will get the complete process to have the Release stretegy on the basis of Doc. Type.
    http://www.sap-img.com/materials/release-procedure-for-purchase-requisitions.htm

  • Release stratedires for Purchase Order

    Hi
    Dear All
    I need a clarification that my needs cost centre based release strategy for Po, but t is not in Cekko table.i have to use customer exit M06E0004 or any other way to use cost centre as char in release st.
    i appreciare if anybody can help/ give the suggestion in this regard
    MVRAo

    Hi,
    Which Documents Can be Released (Approved)?
    Release procedures can be defined for the following documents:
    <b>Purchase Requisition</b></b>
    The external purchasing documents purchase order (PO), contract, scheduling agreement,request for quotation (RFQ), and service entry sheet</b>
    Release Procedure for Purchase Requisitions
    Two different procedures are available for requisitions:
      <b>With classification</b>
    With this procedure, requisitions can be released both at item level (i.e. item-by-item)and in total. The latter approach is also termed „overall release“.
    <b> Without classification</b>
    With this procedure, requisitions can only be released at item level.
    The two procedures are mutually exclusive (that is to say, you must decide in favor
    of one of them only - you cannot use both).
    Release Procedure for External Purchasing Documents
    External purchasing documents (i.e. purchasing documents other than requisitions) are released at header level. Item-by-item release is not possible. These documents can only be released using the release procedure with classification.
    Procedure Without Classification (Requisition Items Only)
    The conditions can be based on one of the following item characteristics or a combination of
    these:
    <b> Account assignment category
      Material group
      Plant
      Total value</b>
    Hope this will answer your question
    Thanks
    Arun agrawal.

  • Can't use Overall Release for Purchase Requisitions

    I have two groups, AA and ZZ.  Each group has it's own Class.
    Group AA uses Cost Center Class (CN)  (uses Characteristics Cost Center and Line Amount)
    Group ZZ uses Order Class (OC) (uses Characteristic Order)
    I have built one and only one Release Strategy for each of these Groups.  These Strategies both work successfully when I select the other group to be the group for Overall Release.  That is, if I set ZZ to be for Overall Release, then create a requisition, the release strategy for Group AA is applied successfully.  However, if I modify the req the strategy for ZZ, does not get applied.
    The opposite is true.  When AA is set to be for Overall release, then ZZ works.  However, if I modify the req, then AA's release strategy does not get applied.
    Again, both strategies work correctly when the other Group is set to be the one to use for Overall Release.  However, neither strategy works if its group is set to be the one for Overall Release.
    What am I missing?  I only have two classes, two groups, and two release strategies.

    SAP Standard system allows only 8 levels of release codes.If client requirement is more than 8 then for excess release codes customisation is done by the technical team (Abapers).Lets take an example of 15 release levels required for a client according to his Business needs then in this case initial 7 codes are customised and remaining 8 release codes are configured in the system.
    Release procedure is of two types
    Release Procedure without classification
                 This procedure is applicable only for Purchase Requisitions.
                 Here PR is released Item by Item only.
    Release Procedure with classification
                This procedure is applicable to PR,RFQ,Service Entry sheet,RFQ,PO,Contract  and scheduling agreements.
                Item by Item and Header level releases can be configured
                For PR - both item by item and Header level release can be configured
                For external purchasing documents - Release is possible only at Header level.
    Step 1:
    Create Characteristics
    In this step we need to create characteristics - conditions to be satisfied for triggering Release startegy.For example client has asked to set release strategy based on 3 inputs.Combination of value, Plant and Purchasing group
                1) Total value of PR more than Rs 50,000
                   create  characteristic as "Release_PR_total_value" in transaction code CT04.
                  Tab -  Basic data " Data type --- CURR currency format", "Decimal places - eg. 2 " and "currency  eg. INR or USD"
                  Tab -values key in > 50000 INR
                  Tab -  Additional Data-  Table Name "CEBAN" and Field Name "GSWRT"
                  Tab - Restrictions - class type - 032 - Release strategy
                2) Plant
                     Create characteristic "Release_PR_plant" in transaction code CT04.
                     Tab - Basic data - Data type - CHAR; Number of chars - 4
                     Tab - Values - Key in all the plants for which you are required to configure release proc.  eg. 1000,2000,3000
                     Tab - Additional data - Table name CEBAN and Field Name is WERKS.
                3) Purchaisng Group
                     Create characteristic "Release_PR_PurchasingGroup" in TCode CT04
                    Tab - Basic data - Data Type - char, Number of chars eg. 3
                    Tab - values - Key in all the purchasing Groups for which Release proc. is to be configured as required by Client.
                    Tab - Addnl Data - Table Name CEKKO and field name - EKGRP
    Step 2:
    Define class in transaction code CL02
    Menu path SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Edit classes
    Here we assign all the above created Characteristics to a CLASS so that a release strategy to be triggered when all the conditions are met.
    Create a new class with free choice of names as "PR_Release_proc" in transaction code CL02.*Key in the class name and select class type as 032 - RELEASE STRATEGY then click on symbol create to enter all the details as mentioned below.
    Tab - Basic data - Enter description as "PR_Release-Proc",
    status- Released, Same classification - check the push button - Warning Message
    Tab- CHAR Enter above created 3 characteristics
    1.Release_PR_total_value
    2.Release_PR_plant
    3.Release_PR_PurchasingGroup
    step3:   
    Menu path is
    SPRO>Materials Mgmt>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>set up procedure with classification>
    here define
    1.Release Groups
    Release group 01 is used for Purchase requisitions and 02 for Purchase orders.
    Here assign class "PR_Release_proc" against release code "01"
    check "OvRelPReq" indicator for over all release (All line items )of document in one shot else it will be released line item wise.
    2.Release codes
    Release codes are assigned to Release groups, in Workflow these release codes are tagged to users' SAP IDs through which they will be able to approve or reject a PR in SBWP(Inbox in SAP Business workplace.
    PRs are released by users in transaction code ME54N.
    Eg
    Type of user            - Level -             Release code                    
    PR creator - clerk or Business user -  
    Approver    -  Supervisor                 -   R1
    Approver  -   Project Lead              -   R2
    Approver   -  Asst. Manager             -  R3
    Approver   -  HOD/General Manager  - R4
    Release codes R1 to R5 are assigned to corresponding users.Manager R4 can only approve the PR if prior approvals till R3 are completed else not in ideal situation.
    For detailed info please refer
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    3. Release Indicator:
    Release indicators show the release status of a Purchase Requisition.
    For detailed info please refer SAP Help official site
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    4.Release Pre requisites:
    These define the order in which individuals or departments release the PR in sequence.
    3.Release strategies
    Create a new release startegy  eg ."A1" or "U1" , write its description PR release for value >1 lakh
    Now select release codes according to the Chart of Authority set by your client.
    Eg.
    Release startegy " A1 - PR release for value >1 lakh"
    R1 - Supervisor   
    R2- Project Lead    
    R3- Asst. Manager 
    R4- General Manager
    Now click on" Release  Prerequisites "push button and check all the boxes in ascending order.Save the document
    click on "Release statuses" push button, check release statuses then click on "Continue" push button.
    In third push button you can maintain CLASSIFICATION data or later you can directly mainatain in transaction code CL20N for this strategy.
    Classification data for example
    1. Value - > 100000
    2. Plant - 1000,2000,3000 etc
    3. Purchasing groups - 101,102,103 etc
    By clicking on "Release Simulation" push button you can check whether release is getting affected for configured release codes or not.
    In this way you can configure all the required Release startegies.
    Now create a PR in T code ME51N with the above conditions then a new tab will appear in PR creation screen at the time of check.Save the document and this can be released by respective users in TCode ME54N.
    Tcode - ME54N - For Individual Release
    Tcode - ME55 - For Collective Release
    For detailed info please visit SAP HELP website
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    http://help.sap.com/saphelp_erp60_sp/helpdata/en/75/ee1fa755c811d189900000e8322d00/frameset.htm
    Regards,
    Indranil

  • Purchase Order Release Strategies for Changed Amount

    Hi Gurus,
    We have a unique request from the business to set the release strategies for POs based on the Still to Deliver amount, not the Net Total Amount of the PO.
    Example: Configuration is PO total amount <$5K requires only L1 approval.  PO total amount >$5K requires L1 and L2 approval.  PO was created for $8K and was release using L1 and L2 approvals.  Receipts were posted to PO in the amount of $7K.  Now the buyer has added an additional line item for $1K.  The PO total amount now shows $9K ($8K + $1K), the Still to Deliver field shows only $2K ($1K from original remaining amount + $1K from new line item).  Business wants the release strategy for this change order to go through L1 only since the Still to Deliver amount is <$5K.
    Has anyone done this before?  Any ideas??
    Thanks,
    Gabe

    from http://help.sap.com/saphelp_40b/helpdata/fr/dd/2d547bb435d1118b3f0060b03ca329/content.htm
    User exit M06E0004 is provided to enable you to adapt the release strategy determination process to meet your requirements.
    This user exit allows you to change the communication structure for determining the release strategy for purchasing documents.
    The following user fields are available:
    USRC1
    USRC2
    USRN1
    USRN2
    In addition, communication structure CEKKOZZ is available, allowing you to use your own fields.

  • 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

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

  • User exit/BADI  for Purchase requisition through release of Process order

    Hi ,
    i need to add some text to the Pur Req.
    The Pur Req will be created THROUGH the release of PROCESS order. Please let me know any exits are available for the same.
    regards

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001                                WE default quantity calc. and over/ underdelivery tolerance
    MM06E001                                User exits for EDI inbound and outbound purchasing documents
    MM06E003                                Number range and document number
    MM06E004                                Control import data screens in purchase order
    MM06E005                                Customer fields in purchasing document
    MM06E007                                Change document for requisitions upon conversion into PO
    MM06E008                                Monitoring of contr. target value in case of release orders
    MM06E009                                Relevant texts for "Texts exist" indicator
    MM06E010                                Field selection for vendor address
    MM06E011                                Activate PReq Block
    MMAL0001                                ALE source list distribution: Outbound processing
    MMAL0002                                ALE source list distribution: Inbound processing
    MMAL0003                                ALE purcasing info record distribution: Outbound processing
    MMAL0004                                ALE purchasing info record distribution: Inbound processing
    MMDA0001                                Default delivery addresses
    MMFAB001                                User exit for generation of release order
    MRFLB001                                Control Items for Contract Release Order
    AMPL0001                                User subscreen for additional data on AMPL
    LMEDR001                                Enhancements to print program
    LMELA002                                Adopt batch no. from shipping notification when posting a GR
    LMELA010                                Inbound shipping notification: Transfer item data from IDOC
    LMEQR001                                User exit for source determination
    LMEXF001                                Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001                                Customer-Specific Source Determination in Retail
    M06B0001                                Role determination for purchase requisition release
    M06B0002                                Changes to comm. structure for purchase requisition release
    M06B0003                                Number range and document number
    MEQUERY1                                Enhancement to Document Overview ME21N/ME51N
    MELAB001                                Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004                                Determine earliest delivery date f. check w. GR (only PO)
    MEETA001                                Define schedule line type (backlog, immed. req., preview)
    ME590001                                Grouping of requsitions for PO split in ME59
    M06E0005                                Role determination for release of purchasing documents
    M06E0004                                Changes to communication structure for release purch. doc.
    M06B0005                                Changes to comm. structure for overall release of requisn.
    M06B0004                                Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST                     Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ                          Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST                      Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO                           Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP                         Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV                            BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST                      Enhancements to Price Determination: Customer
    ME_PO_PRICING                           Enhancements to Price Determination: Internal
    ME_INFOREC_SEND                         Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO                              Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST                          Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK                    FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING                          Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED                      Purchasing Document Posted
    SMOD_MRFLB001                           Control Items for Contract Release Order
    EXTENSION_US_TAXES                      Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE                       BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK                       BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN                        Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP                    Determination of Delivery Address
    ME_WRF_STD_DNG                          PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP                          Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF                    BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS                     Tax jurisdiction code taken from address
    ME_REQ_POSTED                           Purchase Requisition Posted
    ME_REQ_OI_EXT                           Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE                       BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE                      Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB                        Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER                     Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION                     Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH                    BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK                     BAdI to check whether CCP process is active
    ME_BSART_DET                            Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC                     BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO                       BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT                            BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS                      Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE                    Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV                    Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH                    BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN                    Commitment for return item
    ME_CIP_REF_CHAR                         Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE                     Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO                         Copy PO data for use by Country version India
    ME_CIN_LEINRF2V                         BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R                         BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES                        Additional Checks in Source Determination/Checking
    ME_CHECK_OA                             Check BAdI for Contracts
    Reward points if useful
    Regards
    Anji

  • T code to get the detail of release strategies for all purchas groups?

    Hi,
    Is there any  T ode that i can run a report and get the current details of release strategies for all purchase groups exist at the moment?
    if so pls let me know
    or else how can i get that information?
    highly appreciate all of your assistance in this regard?
    thanks in advance
    Regards
    Sasika

    from T16FS you can only get which strategy are present.
    Which strategy you have can already be seen in the PO or requisition.
    But you are looking for the person. this is not really easy, as this can be more than one person.
    A strategy has the information what release code is needed.
    And this release code is in a role which is then assigned to an approver.
    So the only way would be to execute SUIM and then roles by authorization values.
    there you enter the authorization object M_EINK_FRG (hit enter) then you have to enter the release group and release code.
    Execute. SAP will list all roles that grand the authority to release order with this combination.
    in this list you can click another button to see the users that are assigned to this role.

  • Release Procudure for Purchase Order

    Hi Experts,
    I am new Release Procudure.My client wants release procedure for two users.
    End user wants create Purchase Order then other user wants release that purchase order and then another user wants final release. Please tell how can map this process in sap.
    Thanks in advance,
    Chandhu
    Edited by: chnadu9 on Jan 5, 2011 5:48 AM

    Hi,
    The release code is a two character ID allowing a person to release (clear, or approve) a requisition or an external purchasing document. The release codes is basically controlled via a system of authorizations (authorization object M_EINK_FRG).
    Use SE12, structure CEKKO to check all the fields available for controlling the Purchase Order.
    An example of configuring a Purchase Order Release Strategy
    If the total value for the Purchase Order exceeds 10,000, release strategy 01 is assigned to the Purchase Order. There is only one characteristic created in this example. For controlling the Purchase Order type, create characteristic for CEKKO-BSTYP and the value NB.
    Steps for configuring the PO release strategy
    Create the PO Characteristic
    Transaction code : CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data tabstrips
    Table name CEKKO Field name GNETW and press enter and you will see this information message :-
    Format data taken from Data Dictionary (press enter)
    (for currency dependent field, you are prompt to enter the currency which the system then converts the currency of the Purchasing document into this currency)
    In the Basic data tabsritps (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >=10000 (equal or greater than 10000) and press enter
    Save your data
    Create the Class of the PO Release Strategy
    Transaction code : CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create button
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tabstrips, type NETVALUE to assign your characteristics to the class
    Save your data and this message will appear :-
    Class type 032: Class REL_PUR created
    Define the Release Procedure
    OMGS - Define Release Procedure for Purchase Order Type
    Release Group - New entries
    Rel.group Rel. Object Class Description
    02 REL_PUR Rel. Strategy for PO
    Save your entries.
    Release codes - New entries
    Grp Code
    02 01
    Save your entries.
    Release indicators - New entries
    Release indicators Release Description
    0 Blocked
    1 X Release
    Save your entries
    Release Strategy - New entries
    Release group 02
    Rel.strategy 01 - Release
    Release codes 01
    Release status 0 - Blocked
    1 - Release
    Click the Release prerequisities button
    Click the Relase statuses button the click the Continue button
    Click the Classification button
    Choose your check values
    Click the Back button
    Save your entries
    Check your PO release configuration
    Finally, check your PO Release Strategy configuration to make sure that there are no errors.
    OMGSCK - Check Release Strategies
    (make sure there are no error messages)
    Once the Purchase Order is not release, buyers will not be able to print the Purchase Order.
    Goods Receipts will be shown with Message no. ME 390 - Purchasing document XXXXXXX not yet released.
    In 4.6c, Purchase Order with Release Strategy have a tabs at the end of the Header. This allowed the buyers to check the release status of the Purchase Order.
    The person with the release authorization have to use ME28 to release the Purchase Order.
    Regards,
    Mohar

  • Report - who is the current approver for purchase requisition

    Hi Experts
    Is there a report that can give information the status / who is the current approver for purchase requisition?
    currently if we open the PR directly, we can only know the release strategy, release code, status of approver, but we cannot have the information who is the person that should approve this PR.
    Thanks in advance
    Prashanth.v

    Hi All.
    Unfortunately we want to have this information for our end user, and they will not have the access to SE16.
    Another thinks is from CDHDR we will have the information if changes are made in PR. So it will give information user that already approve the PR
    What we want to have is a report of outstanding PR (not yet released) that have information who is the user (the user complete name / user id)  that should approve the PR.
    Thanks In Advance
    Prashanth.Venkategowda

Maybe you are looking for