Purchase Order Controlled by Release Budget Amount.

Dear Friend's
I have created project upto level 2 wbs element.with ext services.
In Budgeting,
In CJ30 Tcode i have allocated budget Rs.100000/-
In CJ32 Tcode i have released above mentioned same amount for WBS 1.
In Purchase Ordering,
While creating PO In ME21N Tcode i have taken services for WBS 1 for which PO net amount is more than Rs.100000/-
When i go for saving of PO.The system must show Error "PO Amount is more than Released Budget.
Pls tell me the customizing setting for above mentioned scenario.By doing this setting system must show error while saving PO.
Pls help me urgently.
Thanks & Regards,
Sandeep N.Theurkar

Sandeep,
As far as I see, all the customizing settings are correct in this case. But just to summarize, please make sure:
a) In budgeting profile (OPS9) make sure flag "releases" is set
b) In CJ32 verify you have released budget for the WBS element (or superior)
c) In CJ02 verify that status BUDG and AVAC are active for the WBS element
d) In customizing path Project System > Costs > Budget > Define Tolerance Limits make sure you have entered the necessary tolerance limits for your budgeting profile. At least, one entry with Activity group ++,  action 3 and usage 100,00 is necessary in your case.
e) In OPTK transaction, please make sure you have not included any cost element for your controlling area.
f) In ME22N make sure the PO is correctly account assigned to the WBS element
Once all this is done, please run CJBN and retest.
If you still don´t get the error when posting the PO, please send the output of BPFCTRA0 report
Hope this helps
Regards
Martina

Similar Messages

  • Purchase order Revision and Releases

    Hello All
    Can any one tell me the keyfig for Purchase order Revisions and Releases.I am trying to built a report that has PO Revision count and PO Releases count.
    Any help would be appreciated
    Thanks

    Hi,
    PO release is a approval procedure. If a PO fulfills certain conditions (e.g. the total order value exceeds $10,000), it has to be approved (by the cost center manager, for instance) before it can be processed further. This process of approving is knows as release procedure.
    PO revision refers to changes made to PO. If an existing PO is changed, the system can print an amended PO displaying the changes. The first change is printed as 'amendment no. 1", the second as 'amendment no. 2" and so on.
    Hope this helps.

  • Purchase order yet not released

    Hi sap gurus,
    i have done purchse order .then i am creating goods receipt for that purchase order but i am getting these error purchase order yet not released.plz tell me how can i solve these problem

    Hi Prasad
    Its simple prasad ur PO is suject to release strategy (Approval process) so the authorized person has to release the PO through the following process -
    Just go to Transaction ME29N or ME28, enter ur PO no.
    If u follow ME28 give ur release grp / code enetr PO no. and execute ur PO will be reflected in the list put the cursor there and press Release+Save Iconit will release the PO and then u will able make the GR.
    If u follow ME29N then give ur PO no. and go to release tab at the header level and press release icon.
    Best regards
    Vineet Baweja

  • Purchase order changes after release

    Hi,
    How can I block a purchase order to any changes after release it and then, in case of need, mark for deletion the purchase order itens?
    Regards,
    Maria

    Hi,
    To block any changes in the purchase order to after release, set Changeability  indicator as 1 for  Release ID "R" in following path & save.:
    SPRO ->MM - Purchasing -> PO -> Rlease Procedure for PO -> Define Release for PO -> Release Indicator
    NOTE:If you set  Changeability  indicator as 3, PO can be changed after release and trigger a  new release strategy based on value changes.
    Regards,
    Biju K

  • Actual Commitment EXCEEDS Release Budget amount

    If budget is not available or if not released,can commitment amounts can be greater than the budget amount?Please note that we are working on 4.6B version.If commitments are allowed by the system to be greater than the budget amount,please tell how it could be rectified.Thanx in advance.

    Hi,
    There are lots of customize setting to not updating commitment, so you have to check below point:
    Check OPSV setting and maintenance order as 30 should be tick mark then check commitment report surely commitment will come under report.
    Check in COSP table if you have commitment value, with value type 21 wbs you can find it in PRPS table & check in COOI table , ME5J Reorts/ and S_ALR_87013558 reports, whether Commitment has captured.
    check below link also
    http://help.sap.com/saphelp_47x200/helpdata/en/4c/22756546e611d189470000e829fbbd/frameset.htm
    Regards,
    Sanjeev

  • Release Tab in purchase order disappear after release using ME29n

    Hi there,
    We are busy testing support stacks (upgrading from ECC6 SAP_APPL SAPKH60305 to SAPKH60307)and we've come accross a strange problem.  When we create a normal purchase order (ME21n) the purchase order does pick up a release strategy.  Using the older ME28 transaction to release this purchase order, everything is fine.  We can use ME28 to release the purchase order, as well as unreleasing the purchase order, as often as we want (the same purchase order).  When we use transaction ME29n the release tab in the purchase order just simply disappears after saving.  In the purchase order header changes, the release change is visible, but the release tab is missing.  This purchase order is now not subject for release, and a goods receipt is possible without release.  I checked in table EKKO as well and the release fields in this table for this purchase order is empty.
    Has anybody had a similar experience?  Any advise would be greatly appreciated.
    Regards
    Christo Vermeulen

    Hi Christo Vermeulen,
    I have detected the same problem as reported by you. Did you solve it? Do you know how can I procedure to solve it?
    Thanks in advanced,
    Eder Nicoleti

  • Purchase |Order cannot be released Message BL001

    Dear Friends,
    I am new to this forum.  I am facing a problem with Purchase Document release. 
    Two release codes GC and PH are assigned to same PO Class.  Charecteristics for release are different for each codes.  for release code GC is purchasing document type and Plant.  For PH is again Purchasing document type, purchase order value and Purchase group.  All have been put together in one class and i am not able to add a new class in release group.  Request you to provide a solution for this.
    rgds...KM

    can you give some more details that you assigned the two release codes in same release strategy or different release strategy.
    if it is assigned to same release strategy then the Charecteristics for release should be same.
    for ex: you have two plants A & B
    now you want to get a approval from a Asst.Manager, if the po price is more than Rs.200000. (for Plant A)
    and you want to get a approval from a Manager, if the po price is more than Rs.400000.
    in this case, you have to create two release code one is for Asst.Manager & another one is for Manager.
    But the characteristics should be same that is your plant & doc type.

  • Purchase Order on particular release date

    Friends,
    I am SAP HR consultant working on MM. I have one scenario how to find out the Purchase Orders on particular date.
    Is there is any tcode or report for that.

    Hi,
    There are many option.
    Just search in enjoy menu in Materials Management
    Some t.codes : ME2M, ME2N
    Cheers,
    Satish Purandare

  • Purchase order is created with less amount than the shipment cost amount.

    Hi All,
    Shipment has got 2 stages but the system wants to split the shipment cost to 3 parts (33% each) If we add the amount with manually to shipment cost document and we transfer it the PO will be created only for 2/3 (66%) part of the shipment cost.
    What could be the reason?

    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.

  • Purchase order pending for release report

    Hi Gurus,
    Is there any report which will give a list of POs pending for release?
    Regards,
    Kumar

    Hi ,
    You can view through report ME2N..
    In T-code you can select option dynamic selections > select header item> select Release status
    Then you can view the pending report.
    Regards
    SAM

  • Purchase order table for Release

    Dear All Expert,
    Is there any table for PO where I can find out the release indicator and who made relase, etc.
    Thanks & B.Rgds
    Bishnu
    05/07

    You can find the release indicator in EKKO  field "FRGSK"  and information about who released in table  CDHDR  by passing Object "EINKBELEG"  and   Object value  as the PO number . .  from CDHDR you will get the change document number , TCODE used for release "ME29N"  and the user name.  YOu cna pass the chnage document number to CDPOS table to get releease  status as well.
    Regards
    Raviraj

  • How to setup a release strategy for store generated purchase order

    Hi there,
    Does anybody know how to setup a release strategy for store/plant generated purchase order? I have a request from our client, but I never cross this before. Please help and let me know the step with every single detail.
    Greatly thank for your help.
    Kind Regards,
    2tea

    Please go thru the below Release Procedure and check whether you have maintained all the settings properly.
    PO RELEASE STRATEGY
    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.
    e.g. 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.
    CT04 - Create Characteristic e.g. NETVALUE
    Click Additional data Table name CEKKO Field name GNETW and 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 (X refers to tick),
    X Mutliple values
    X Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    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
    Release codes - New entries
    Grp Code
    02 01
    Release indicators
    Release indicators Release Description
    0 Blocked
    1 X Release
    Release Strategy
    Release group 02
    Rel.strategy 01
    Release codes 01
    Release status 01
    Classification Choose your check values
    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,
    Ashok

  • Release Strategy in Purchase Order

    Hi,
    Can any explain the usage of Release Strategy in Purchase Order.
    ganesh

    Hi Ganesh,
    Release strategy works the same way in purchasing documents (i.e. PR and PO). It is a form of control that company use to control the purchases made.
    In your scenario, a PO release strategy is used to control the PO release status for Good Receipt process. Once the PR is released by the relevant releaser, you will see that the PR is now unblocked for issuance of PO.
    Once the PO is issued with reference to the PR, it is now blocked again by a release strategy for user to perform Goods Issue. The releaser will evaluate the PO issued and determine if it is necessary to be released for GR / Service Acceptance process. At this stage, the releaser can still reject the PO although issued, and hence GR / Service Acceptance is not able to be performed. Different value will trigger different set of release strategy with different level of approvals, depending on how the PO release strategy is configured by the MM functional consultant. Usually, the PO release strategy has a flatter approving level as compared to PR release strategy, reason being that once the PR has been fully released by all releaser and the PO issued, usually the purchase is deemed necessary and PO releaser would usually consider to release the PO for GR  or Service Acceptance process, unless there is discrepancy or sudden change in decision of Management.
    Hence, all in all, the PO release strategy act as another form of control to the company to restrict the release of PO for GR or Service Acceptance.
    Hope this will give u a better understanding on the function of a PO release strategy.
    Rgds.

  • Purchase Order not subject to release strategy

    Good day everyone!
    I've created one release strategy for all my purchasing documents. The characteristic is net value, and the value of this characteristic is >=0.00. Meaning, ALL purchase orders are subject to release strategy.
    After I did the release strategy in SPRO, I created a few PO and when I tried to release them, I got this message: "Purchasing document 45xxxxxxxx not subject to release strategy".
    My question is: How to assign purchasing document to release strategy?
    Please help. Thank you in advance.
    Anisah

    hi
    yes you have to use table CEKKO for PO release strategy , now , in PO you can't create without clasification so it will be applicabe for whole PO not for line items ,
    now below i am giving u one by one steps , follow and let me know .
    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.
    e.g. 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.
    CT04 - Create Characteristic   e.g.  NETVALUE
    Click Additional data Table name CEKKO      Field name  GNETW    and 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 (X refers to tick),
    X    Mutliple values
    X    Interval values
    In the Value data, in the Char. value column, type >10000 and press enter
    Save your data
    CL02 - Class
    Class - Create REL_PUR
    Class type - 032
    Click Create
    Description - Release Procedure for Purchase Order
    In the Same Classification section, click Check with error
    In the Char. (characteristic) tab, type NETVALUE to assign your characteristics to the class
    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
    Release codes - New entries
    Grp         Code
    02           01
    Release indicators
    Release indicators           Release        Description
          0                                                        Blocked
          1                                     X                Release
    Release Strategy
    Release group   02
    Rel.strategy    01
    Release codes   01
    Release status   0
                            1
    Classification   Choose your check values
    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
    ravikant dewangan

  • Disabling selected Purchase Order field(s) after released/approved

    Hi Experts,
    I have a requirement to disable specific Purchase Order fields after released via ME29N.
    For example, in Purchase Requisition - I can "Release Indicator - Field Selection Key" to control Purchase Requisition screen layout. However, for Purchase Order - the configuration for "Release Indicator" consist only standard default "Chgable" options.
    Question:
    Is there a way to customize the Purchase Order "Release Indicator" for screen layout based on customer requirements other that using the default as mentioned above?
    Thank you.
    Steven

    Hi Padmasri,
    I understand your explanation on the standard SAP behavior.
    Nevertheless, I'm looking for some flexibility to meet customer requirement. Like in Purchase Requisition, there is option to further customize the screen layout by linking it to the "Release Indicator".
    Therefore, apart from the standard 6 options given by standard SAP, can we add/customize the options? For example, my customer may one to change a field in the Purchase Order even after released.
    Thank you.
    Steven

Maybe you are looking for