Strategy To release For Budget

Hi,
I ' m  working to a customer for a module PS, he wants  to know if there is for the PS budget a kind of release strategy
Exactly can we  use a release strategy for the budget? If is possible something like Standard SAP
There will be several people who authorize the budget based on the WBS  ammount. we need something like a strategy of Purchase Order for a module MM.
Tanks for the attention
Regards
Alessandro

Hi,
As both Nitin and Vara have pointed out, there is no option of having a release strategy for the budget. However you can control this using authorizations to the users who are responsible for releasing the budget. I think this is the way most of the organizations handle this.
Regards,
Gokul

Similar Messages

  • PO Release Strategy not triggerred for particular Total Net Order Value

    Dear,
    I am currently facing the issue where release strategy for purchase orders is not getting triggered for a particular value or lower.
    For order value 1 INR or less, no release strategy is triggered for new created PO. And for value > 1 INR release strategy is getting triggered.
    All otehr PO characterstics are the same, I mean to say the values for other characterstics such as plant material group are identical.
    But the characterstics for release for Total net order value are <= 30000 INR. There are two system copies, where in one system the same release strategy is working as expected. But in other system the above mentioned issue occurs. There is no differnce which I can see in the release strategy setup.
    Please suggest for solution.
    Thank you.
    Warm Regards.

    Dear All,
    While looking further into the issue by going into debugging mode, we have found that in include LCLSCF2I, Internal table p_selection_criteria_tab , the value for ATFLV (Internal Floating point from) gets different values in the two systems. For example, in the affected system, for PO with 1INR tottal value, for one of the Total value chaaracterstics before INR characterstic, ATFLV value is 0,0000000000000000E+00, hence it gets out of loop and doesn't trigger release strategy.
    But in another system for same PO values and release setup, ATFLV value is 1,0000000000000000E+00 for that characterstic.
    May I know how the value for this field gets calculated.
    Thank you.
    Warm Regards.

  • Release strategy not triggering for Specif plant

    Hi Friends
    I configured a release strategy with three charecteristics. P.org, Plant, Net value.
    this stretegy is triggering for specific plants which are under a particular company code, and if I change to my plant and P.org. its not triggering.
    I have deleted all the classifications and release strategies from, no other data in VV_T16FS_2 , AUSP,T16FV,and T16FS tables except this release strategies data.
    do we have any settings at cocode level??????
    please respond if answer known
    Points would be awarded for for your valuable answer.

    Thank you deepak for your quick respond
    Actually There were already release strategies  with same charecteristics, and with the values of other plants and other P.orgs which are under certain companycode.
    these were triggering perfectly for PO
    Now created new strategy for plant and P.org under different plant code of different cocde. this strategy not triggering for PO.
    but if the release strtegy  values replaced by the erlier plants and P.org  again its triggering.
    Now I created new chars, class, and stategies still same problem persists.
    Release stategy working for the values of a prticular company code plants, Porgs.
    and already tried your suggestion Cocode as char. but same its working for only that company code not for my companycode

  • Release Strategy with Workflow for PR & PO

    Hi Experts,
    I have configured the PR & PO Release strategy and it is working fine. My client wants the Workflow concept in Releases.
    So User should get the information about the releases for PR & PO.
    But I don't have much idea on Workflow, how it works for Release strategy. Can anybody give information on how to configure the Release strategy with Workflow in PR & PO.
    Points will be awarded .
    thanks & rgds
    Swamy

    Hi Swamy,
    The release workflow is configured by MM functional consultant. As for the workflow determination (i.e. which level should approve first and so forth) depends solely/mainly on the Finance of the company. It differs from one company to another. And the level of approval also differ from one company to another. Hence, like you mentioned, this would be provided by the user, so it is okay. I have replied to someone on another thread asking about workflow, and this is how it works.
    How it works? For example, for a PR release strategy, once the PR is raised by a user for a certain value, the PR raised that matched the classification of the release strategy configured will be triggered. In this sense, once the release strategy is triggered, the releaser holding the release code to release this PR will receive a workflow in their SAP inbox (Not Outlook) for their execution, which is sent automatically by SAP system. These is accessible via the t-code SBWP. Each releaser have a unique login ID and password.
    Assuming the release strategy required 3 levels of release, for example A3, A2 and finally A1 (final release), A3 will first receive this workflow in his/her inbox. After A3 has released, A2 will subsequently receive workflow in his/her inbox for this same PR. In the PR, you will be able to see that A2 release is now possible. This flow will continue until the final releaser, A1 and then, the status of the PR will be unblocked for issuance of PO.
    How is it configured in SPRO? In the Workflow for PR release strategy, you are able to assign a unique ID (usually employee ID) to a particular release code, which these release codes are tied to one or more release strategies. The workflow determines who is to release for a release strategy with that particular release code via the assignment of the ID to that particular release code. Each assignment is only possible for one Plant, and you have to assign the same for many other Plants for the same ID in the workflow if you want him/her to have the authority to release purchasing docs in more than one Plant.
    How to configure?
    Before that, you need to obtain the following information - User ID of the releaser for the specified release code, Plant to be released by the user, and finally of course the Group and Release code (which you already have).
    For PR: IMG>MM>Purchasing>Purchase Requisition>Release Procedure>Procedure with Classification>Set Up Procedure with Classification-->Workflow
    For PO: IMG>MM>Purchasing>Purchase Order>Release Procedure for Purchase Orders>Define Release Procedure for Purchase Orders>Workflow.
    Maintain the details u already have in hand:
    For PR: Group (PR or PO), Code (release code), Plant (you have to maintain the same details for each of the Plant that the same release code releases) Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    For PO: Group (PR or PO), Code (release code), Object (US) and Agent ID (the user's ID used to login to SAP system and SBWP).
    Please note that PO is not Plant specific, and is usually one releaser to release the PO for GR. It is the PR that during the initial stage has the most level of release (up to max. 8 level) before a PR can be converted to PO.  After the PO is converted, it is usually deemed accepted, hence only one release code is usually required to release the PO.
    Hope this will give you an idea how the workflow works and how to configure it.
    Rgds.

  • Error message if no release strategy is applied for PO

    Dear All,
    In some cases there is no release strategy is applied for a PO, but still system is allowing me to make GRN against this PO.
    Is there any way to encounter this
    Means if no release strategy is applied for that PO then system might not allowed to SAVE PO.
    OR
    While making GRN against this PO, System will give message Like say ...  no release strategy is applied for the PO..
    Please reply  ...URGENT
    Regards,
    Rakesh Shelar

    Dear Thanx.
    my requirement is to block further processing of PO for which release strategy is not applicable due to some wrong combinations put while crating PO.
    In this, case  system is allowing to take GRN against such POs without release strategies

  • Configure of New Release strategy in PR for ERSA Mat type

    Dear Friends,
    Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Regards,
    Ask

    ashokkumardash wrote:>
    > Dear Friends,
    >
    > Pl provide me the solution for configure of New Release strategy in PR for ERSA Mat type with the approval of GE with a characterstic value of MRP Controller.
    Hi,
    Create Characteristic for Material type and Communication structure CEBAN and a create class with 023 and assign character to class and create Release group and code for MRP controller and finally assign this particulate role to the MRP controller User ID and he release the same.

  • How to set the Release Strategy without classification for PR

    Hi,
    I am able to set Release Strategy for PO with classification, however, now I want to set the Release Strategy for PR with classification. Can someone tell how to proceed to set the Release Strategy to PR with Account Assignment.
    I crated the Release Codes, however not able to find what options to choose in the following steps :-
    Release indicator
    Assign Release Indicators
    Release Points: Prerequisites
    Determination of Release Strategy
    Regards,
    Yogesh

    1. Release codes                                                            
       Create the release codes.     For  Purch. Officer, Manager and Sr. Manager                                                                               
    Like PO, MG, SM                                      
    2. Release indicators                                                       
       Define release indicators and branch to the detail screen. Here you      
       define whether fixed purchase requisitions may be changed by Materials   
       Planning, for example, and whether an RFQ or a purchase order may be     
       created from the requisition.                                            
       You can also determine the field selection here.                                                                               
    In the area "Changes after the start of the release procedure", you      
       specify whether a requisition may be changed after the release           
       procedure has begun. You specify whether the strategy has to be          
       redetermined after changes, or whether the release procedure has to      
       start all over again from the beginning.                                                                               
    This parameter bears a relation to the parameter "Value change". For     
       example, previous releases are not cancelled if the value of the         
       requisition item after the change does not exceed plus 10% of its        
       original value.                                                                               
    Attention:                                                               
       Be sure to create a release indicator (e.g. B for "blocked") that        
       serves as the starting point for subsequent indicators. Do not set the   
       indicators for release for the issue of RFQs and PO on the detail        
       screen for this indicator.                                               
       Also create a release indicator characterizing the released status.      
       Set the indicators for release for the issue of RFQs and PO on the       
       detail screen.                                                           
    You can use sytem defined indicator in this case you don’t have to do anything                                                                               
    3. Assignment of release indicators                                         
       Assign a release indicator in dependence on the status of the release.                                                                               
    Example:                                                                 
       You create a release strategy S1 consisting of two release codes 01      
       and 02. Release with 01 is a prerequisite for release with 02. If        
       release has been effected with 01, the requisition has been given the    
       "all clear" for the issue of RFQs.                                       
       You have created the release indicators B (blocked), 1 (cleared for      
       issue of RFQs) and 2 (cleared for RFQs and PO).                          
       Now enter the following as assignment:                                                                               
    Strategy   C1  C2  C3 ...                                                
       S1                          B (blocked)                                  
       S1         X                1 (RFQ)                                      
       S1         X   X            2 (RFQ/PO)                                                                               
    4. Release prerequisites                                                    
       Define which release codes are involved in a release strategy. Specify   
       whether a code is set for a release status following release, and        
       whether one release status is a prerequisite for another (+).            
       Example:                                                                 
      Strategy   Code  C1  C2  C3 ...                                  
    S1         01    X                                               
    S1         02    +   X                                                                               
    5. Determination of the release strategy                            
    Determine the conditions under which each release strategy is    
    assigned. The criteria are account assignment category, material 
    group, plant, and value of the requisition item.                                                                               
    Here you can define the you criteria but one thing you keep in mind that you hae to define all criteria.
    E.G if you will not define the Material group here but it will default in req in that case this will not work that’s the reason you have to work with Classification.               
    <b>In the classification whatever criteria you need that only you have to include like in your case you care about A/C category and value only.     </b>

  • Error while Releasing the budget

    Hi Gurus,
    We had activated AVAC at budget release (Overall & Release) with Error at 100% budget consumption. I am doing cost planning at activity level (Assigned Component, which will be effective after Activity release). When I try to release the budget, system gives an error message that Budget is exhausted. For eg. I had planned for 920/- and releasing the budget exactly for the same amount, system gives an error message ( Message no. : BP607),
    Item WBS element XXX budget exhausted
    Message no. BP607
    Diagnosis
    Budget  is exhausted in document item WBS element XXX.
    Whereas if I do the Cost planning at CJ40, I am  not facing this problem. But the requirement is to do Network planning for some cases. How to overcome this issue ?
    thanks in advance.

    Hi,
    Just check if the value you plan in Network is increasing the Assigned value for the Network. That Will consume the budget.
    Available Bud = Budget - Assigned Value.
    To avoid this Untick Assign Funds in plan indicator in OPSV T-code for Order category 20 and all Order types.
    Then Planned Values in Network will not increase assigned value and hope issue will get resolved
    Thanks
    Saikishore.Ganga

  • Components to be activated for Budget check in the table TRWCA

    hi,
    I want to know the components to be activated for budget check in the TRWCA table. I want to check the budget at the time of  PO creation , Goods reciept/Invoice receipt creation  using Network account assignment in PO  which is having WBS element and Project in its higher level.
    Thanks
    Rao

    ok well!
    Brother system will only check the budget, when your availability control is active.
    Further, as per your configuration, system will only prompt error  message when your budget exhausted 100%. ok
    please follow the same then  let me know
    check your WBS status is there avaiablity control active, when you entered the amount for budget/release.
    also check the transacion "CJBV - Activate Availability Control "
    Note: when ever you change the setting of your budget profie, must reconstruct the availability control transaction code is :CJBN/CJEN
    Thanks

  • How to release the budget in SAP Funds Management

    Hi
    How to release the budget in SAP Funds Management. Please let me know the proceedure and the transaction code
    Tks

    Hi,
    The answer depends on if you are using Former Budgeting or BCS.
    1) If you are using Former Budgeting:
    a. You should use transaction FR51 to enter Release or FR55 to distribute it.
    2) If you are using BCS:
    a. Within FMBBC transaction you have the option to release the budget, use document type as REL (release).
    b. You can activate the automatic release for each budget profile in Customizing of Funds Management Government.   To do this, in IMG select Funds Management Government ® Budgeting and Availability Control (Former Budgeting) ® Budget Profiles (Former Budgeting) ® Set Up Budget Profiles.
    With the automatic release, the corresponding background releases for expenditures FM account assignments with budget transfers are also posted. Take note that the maximum amount that this automated release can transfer from the sender is the amount that has already been released.
    If you do not activate the automated release, the maximum amount that can be transferred from the sender is that which has not yet been released.
    c. You can use the mass transaction for release, which is FMMPRELE.
    I hope that this answer your inquiry.
    Best Regards,
    Vanessa Barth.

  • 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

  • Three level release for appropriation request (IMA11)

    Hi
    we are using IM for budget control and within IM, appropriation request for budget approval.
    we have done the necessary configuration available in IM for budget release but still system not trigering work flow once appropriation request save. we want to sent the approval request is SAP inbox.
    experts are requested to revert with steps and T Code to get approval reqest in SAP mail box.
    Thanks & Regards

    Hello,
    Once you are sure that the configuration has been done perfectly, please check whether the system is publishing the event by going through the event log(SWEL). Before  checking the event log, make sure that the event trace is on in the system by using the transaction SWELS. Once the event trace is on, save the request again and check for the event in the event log by using the tcode SWEL.
    Once an event is publised in the system, use the same as the triggering event for the workflow template and then use the Sendmail step to send a mail to the SAP inbox.
    Hope this will help.
    Thanks,
    Samson

  • PR release for costcenter

    Hi
    We need to give authorizatin to relese PR/PO to the costcenter owners. how to set relese authorization to cost center level.
    In one PR/PO there can be seperate lines with differant costcenters. How to set relese authorization in line wise other than set it in header level. Plse advice on this.
    Regards
    Kesharika

    Hi Kehsarika,
    You can set item wise release for PR. for PO it is not possible to have item wise release.
    You have to set a practive for PO creation that each PO will have one cost center.
    It means the POs will be created per cost center.
    then you can set release strategy for PO and PR by using CEBAN and CEKKO.
    Satish Purandare

  • SO will not be taken into consideration for MRP until it is released for delivery.

    Dear Sir,
    We are following sales order basis planning (MTO basis planning strategy 50 is being used ).
    When sales order are created by default it is blocked for delivery. In our present system,  we have a scheduled total MRP procedure on daily basis. Hence, when sales are entered in the system it is taken into consideration for MRP RUN automatically.
    But our new proposed system we want , until the sales order is blocked for delivery, it will not be considered for MRP RUN. It will only be taken into consideration for MRP RUN when sales order will be released for delivery.
    Is it Possible ? If Yes, Please let me know the procedure.
    Regards,
    Amit Biswas

    Hi Krishnendu ,
    Then we are deviating from my requirement ,
    My requirement >>
    We are using  MTO planning  (Planning Strategy using 50),
    1. Sales order are created for material requirement planning .
    2.  under MD04 list sales order will be shown under FERT material .
    3. There is release procedure of Sales order.
    4. Daily scheduled MRP RUN has been introduced on total planning.
    5. MRP RUN only consider released sales order . If there is any sales order which is not released , that will not be consider for MRP RUN.
    6. Under FERT material , there may be number of sales order both released and not released sales order.
    Please let me know the process , sales order which are not released , this will not be under the scope of MRP RUN .
    Regards,
    Amit Biswas

  • Error while release the budget

    Hi ,
    We are carryforward the budget from 2007 to 2008.
    by using the TCODE:
    CJCF & CJCO
    Now we try to release the budget for year 2008 it gives error message
    "item WBS element INFORMATION SYSTEM  budget exceeded
    the document item WBS element INFORMATION SYSEM BUGDET for fiscal year 2008 was exceeded by 211 234.43 INR"
    PLEASE guide me for this
    every valuable suggestion will be reward by good points.
    thanks
    sunil jawalkar

    Hi,
    There is no availability control during the budget carryforward.
    For help you can use the following link:
    http://help.sap.com/saphelp_46c/helpdata/en/86/98853478616434e10000009b38f83b/frameset.htm
    Also its worth to have look at Note: 1048588.
    Hope it helps. Please reward point if found useful.
    Thanks!

Maybe you are looking for