Restrict Purchase Order Minimum Value

Hi,
We want that the SAP System should not allow the user to create a Purchase Order of Value less than Rs. 5000.
Is there any SAP Standard Functionality available for the same or we need to use the User Exit?
Regards,
PK

Thanks Shital for the reply.
We are not using Release Strategy, hence we want to out the check at the PO Creation level only.
Pls. advise.
Regards,
PK

Similar Messages

  • How to Retrieve Purchase order TAX value price

    Hi,
    I want to retrieve Purchase order TAX value price from the purchase order is there any function module to retrieve this value.  Or from which table we can retrieve this value using purchase order no.
    Thanks in advance

    Hi Pradeep,
    Have you looked BAPI <b>BAPI_PRICES_CONDITIONS</b>?
    Hope this will help.
    Regards,
    Ferry Lianto

  • Sales order minimum value issue

    Hello,
    Could you please provide some inforamtion regarding the sales order minimum value infoarmtion like where we can maintain that value?
    Regards|ksr

    hi
    You can specify a minimum order value for sales order processing. The following example illustrates how this function is used:
    You specify a minimum order value of USD 200.
    During sales order processing, the net value (after discounts and freight, before taxes) of an incoming order is USD 190.08.
    During pricing, the system determines that the net value falls below the minimum order value and calculates a minimum-order-value surcharge. In this example, the surcharge equals USD 9.92.
    The minimum order value and the surcharge appear as separate lines in the pricing screen. The minimum value is for information purposes only, and does not affect pricing. The system automatically adjusts the net value of the order (before taxes) to the minimum value allowed.
    If you use minimum-order-value requirements, you must create condition records for condition type AMIW. In these condition records, you specify customers and the corresponding minimum order values. During pricing, the system automatically uses these condition records as a reference for determining the relevant minimum order surcharges (condition type AMIZ). In the standard version, condition type AMIZ refers to AMIW. This means that the system automatically calculates values for AMIZ conditions; you do not need to create separate condition records.
    You may want to specify minimum order values by sales organization or division instead of by customer. In order to do this, your system administrator must define a new condition table with the appropriate fields in the table key. The condition table can then be included in the access sequence for condition type AMIW.

  • Could you restrict purchase orders based upon Vendor / Material Group?

    Hey everyone - I've got a general "could this be done" kind of question. 
    We would like to add on to the vendor purchasing view to include "valid" material groups.  This would then have what material groups could be purchased for which company code for that vendor.  Then in the purchase order creation / modification we would like to be able to validate this purchase order against this vendor / company code / material group combination.
    Obviously with enough custom code this could be done.  My question is whether it could be done without out introducing too much custom code - how would you construct such a solution to this problem?
    We are a SAP 4.7 shop.
    Thanks!   Ken Little

    >
    Ken Little wrote:
    > Hey everyone - I've got a general "could this be done" kind of question. 
    >
    > We would like to add on to the vendor purchasing view to include "valid" material groups.  This would then have what material groups could be purchased for which company code for that vendor.  Then in the purchase order creation / modification we would like to be able to validate this purchase order against this vendor / company code / material group combination.
    >
    > Obviously with enough custom code this could be done.  My question is whether it could be done without out introducing too much custom code - how would you construct such a solution to this problem?
    >
    > We are a SAP 4.7 shop.
    >
    > Thanks!   Ken Little
    By include "valid" material groups i think it means you are introducing a new field or some value in already existing field in vendor master.
    1) Now to restrict PO based upon material group a small custom code is needed.
        Use BAdI ME_PROCESS_PO_CUST....here write a code with help of your ABAP person that system will first select the 
        LIFNR (vendor code) entered in the PO...then it will check the same LIFNR in LFM1 table...here it will check the material
        group in the customized field & if found that it is within the list of previous listed material group then it will allow to process
        further or otherwise give a customized error message.
    or
    2) Use the field Group in OMSF...here maintain a common group against the material groups you want to do the purchase cycle.Now ask your BASIS person to use this group in carry out a specific activity, the user must have authorization for the combination of the activity and the authorization group.
    Regards,
    Indranil

  • Restrict purchase order document type at plant level

    Dear,
    I would like to restrict the purchase order document type at plant level,
    Plz help me.

    Hi Dear,
                 at the Plant level you have to use the below given Authorization Objects for the Users in different Plant
    M_BEST_BSA     Document Type in Purchase Order
    M_BEST_WRK     Plant in Purchase Order
    Give the values of the respective Plant and Order Type for the Respective Users.
    For more help you can contact your Security Team.
    but before that please check out in the T-Code SU24, if both the Objects are active, if not then ask the ABAP person to activate them.
    Hope it helps you.
    regards,
    yawar Khan

  • Release Strategies in Purchase Order - possible values of caracteristics

    Hello,
    I have the following situation at hand.
    We use in a company code a release strategy for POs. One of the caracteristics is the "plant" (CEKKO-WERKS, multiple values). Strategy is working fine.
    Now I have to implement in another company code- in the same Client - the PO release strategy but this company code has about 800 Plants asociated! moreover, the release strategies in this new company are not dependent on the "plant"!
    I can not change the caracteristics in the Release strateg because this would affect the already working strategies  and SAP does not allow to asign another Class to the PO release groups.
    Is there any way I can prevent that I have to create release strategies with each of them 800 Plants in the caracteristics "Plant" ?
    Can I use something generic in the caracteristics field of the strategy?
    Thanks for any help. It would save me a lot of time!
    Aart

    Note 493900 - FAQ: Release Strategy
    1. Question :
    Why is the release strategy not determined?
    Answer :
    Please check the following points :
    You can not use Release without classification and Release with classification.
    If there is an entry present in Release Group table (T16FG-FRGOT) only release with classification can be used.
    If you use version management, the determination of the release strategy starts when the version is completed.
    You complete a version by setting the "version completed" indicator in the version tab.
    Cost Center values (CEBAN-KOSTL) and Vendor values (CEBAN-LIFNR) in the release strategy characteristics should be entered with leading zeros.
    This is true for the other structures as well (CEKKO and CESSR). See note 52225.
    For OVERALL RELEASE (purchase order and purchase requisition) the item fields such as Plant and Material Group will be aggregated to header level.
    For example you use Plant as one of your characteristics. If all items do not belong to the same plant then the relase strategy will not be found unless you have maintained a blank value as one of your allowed values for the characteristic Plant. If all items belong to the same plant then that plant is aggregated to the header; if one or more is different then a blank is aggregated to the header. See note 47089.

  • Purchase Order Condition Value

    Hi,
    We have an issue with the Conditions in a Purchase Order raised by the client.
    In this purchase order, there are 151 items with PB00 or PBXX item conditions.
    However when these are totaled up (as a standard SAP functionality) and the values are displayed are at header level, we find that the totaled values are incorrect.
    For some values the quantity used for totaling at header level are incorrect.
    For eg. For one material, there are 2 line items of 16 qty each which total up to 32 items at 29.25 USD. However the header level shows the amount as 965.25 with amount as 29.25 and qty as 33.
    There are many such discrepancies between the header calculations and the item level quantities. In some cases items with PBXX conditions have been totaled up under PB00.
    Both PB00 and PBXX are configured as item  level conditions only.
    This results in Net Value of Purchase Order being wrongly calculated.
    Could anybody throw any light on why this happens and how it can be resolved.
    Regards
    Anjan

    Hello Anjan
    If u check the condition type PBXX and PB00, in PB00 in Group condition field , 'Group condition' check box needs to 'Tick'. Please check relevant help. I hope due to non tick in condition type, caculation in PO for above condition types are going wrong. Also check with Item and Header tick in condition type.
    Regards
    Amol

  • Purchase Order item value breakup condition type wise

    Dear Sir,
    We are developing a custom report and in this report we need to reflect  for Purchase Order item wise the break-up of values  at the condition type level .
    In Me23n , at at Item Level , when we click on tab <Condition> then all values break-up at condition type level gets displayed .
    But to use in custom program , we need to know the table  where this information is available .
    Kindly guide us pl .
    Regards
    B Mittal

    Hi,
    This suggestion is based on my understanding of your issue.  May not be straight forward SAP solution.
    I would suggest you to make following assessment for your custom program: (going through the condition tab will lead you to structures)
    1. Try to figure out how the pricing condition are maintained.  Normally you have your Base price PBXX or gross price per EA defined that can be found in the PIR of the material + Vendor combination or in the pricing condition you would have defined.
    2. In same way figure out all the other absolute condition types.  I mean any thing that is not % percentage based on PBXX value. (assess ;your pricing Schema to understand this.
    3. Once you know how is your pricing schema  breakup then try to pick the net price of PO and then do a backward calcuation based on PIR condition value.    .
    Hope this helps.
    thx
    MJ

  • Restricting Purchase order for a particular material type

    Hi All,
    How do I restrict a purchase order document type to be created for a particular material type.
    For eample PO document type NB should allow to create for materials with the material type ROH only and restrict the other material types by issuing an error.
    Many thanks in advance.
    Regard,
    Ravi

    Hi Ravi,
    This is not directly achievable in std. You will have to implement the check in a user exit, e.g. the BAdI ME_PROCESS_PO_CUST method PROCESS_ITEM.
    But why this strange reqmt? Maybe there's another solution whuch would keep you in std?
    BR
    Raf

  • Restrict Purchase Order to generate custom output message on condition.

    Hi Experts,
    We have custom message / output types ZEMA(E-Mail) & ZNEU(Standard Mail) configured for Purchase Orders.
    We have a requirement from client to restrict the generation of output message ZEMA, if the amount of the PO is greater than some limit say 100USD. And the message output should also be avoided to create entry in ME9F.
    Can you please advise if there are some way (User Exit?) that prevent the output message in this scenario (specific PO Type) without touching the current Condition setup?
    Here I would need the new PO object being created and the amount on the PO from the field NETWR.
    Thanks,
    Ankur

    Hi Jurgen,
    Sorry for missing out the Dump details earlier.Please find below an extract from the dump:
    Category               ABAP Programming Error
    Runtime Errors         POSTING_ILLEGAL_STATEMENT
    ABAP Program           FRMSCM0012
    Application Component  Not assigned
    Date and Time          10.06.2014 08:30:46
    Error analysis
         There is probably an error in the program
         "FRMSCM0012".
         This program is triggered in the update process. The following ABAP
         statements are illegal here:
         - CALL SCREEN
         - CALL DIALOG
         - CALL TRANSACTION
         - SET SCREEN
         - LEAVE TO LIST-PROCESSING
         - SUBMIT
         - LEAVE SCREEN
         - LEAVE LIST-PROCESSING
         - LEAVE PROGRAM
         - LEAVE TO TRANSACTION
         - MESSAGE I/W/E (if not handeld using EXCEPTIONS ERROR_MESSAGE)
         - MESSAGE A
    How to correct the error
         Probably the only way to eliminate the error is to correct the program.
    If the error occurs in a non-modfied SAP program, you might be able to
    find a solution in the SAP Notes system. If you have access to the SAP
    Notes system, check there first using the following keywords:
    "POSTING_ILLEGAL_STATEMENT"
    "FRMSCM0012" bzw. FRMSCM0012_SF
    "SFORM_PRINT_OUTPUT"
    Information on where terminated
        The termination occurred in ABAP program "FRMSCM0012", in
         "SFORM_PRINT_OUTPUT". The main program
        was "RSM13000 ".

  • Purchase order minimum

    System version: ERP 5.0
    When creating purchase orders using ME59,is there a way to block or flag any purchase order and/or purchase order line because it would not comply with rules such as:
    minimum quantity per line
    minimum $ amount per line
    minimum $ amount per PO.
    If it is possible, is there a way to have SAP to automatically proprose the addition of exisiting purchase order requisition further out in the horizon?
    Thanks in advance for your suggestions.

    Hi,
    This is not possible using standard SAP and so you would have to use a user exit or complex coding modification to achieve this.
    If your requirements are managed via MRP then it would be easy to achieve this because you would use the minimum lot sizes and the various lot size indicators to combine small requirements into more meaningful quantities (by looking at future requirements and bringing them in early, for instance)
    Steve B

  • Purchase order total value

    Hi all!
    Is there any table or any function module which gives the total value of the purchase order inclusive of all the taxes and conditions?

    Hi Gud Afnoon,
    Now Try EKBE / EKPO table in SE16 Tc.
    U hav to mention PO no there.
    Can i hav ur mail Id.

  • Purchase Order Discount Value

    Gurus,
    Need help in getting the source table of discount condition value in purchase order.
    This is under the header condition tab. T-code: ME23N
    Thanks in advance

    Dear Golddust,
    1st go to EKKO table, enter PO number, then get the EKKO-KNUMV value, then go to table konv, and paste the KNUMV value in doc.condition, then execute, from there you can get all PO header condition.
    Regards,
    w1n

  • Restrict purchase order line item selection in MEMASSPO

    How to restrict in authorizations of role which purchase order line item can be selected by user in the memasspo.
    I have a scenario where Business wants that no user should be allowed to select all the Purchase Order line items rather should be displayed sub set of the entire purchase Order line items while attempting to do mass change in the PO created.
    Thanks & Regards,
    Abhimanu

    The mass transaction is meant to change many POs and their items at one time.
    The user can not change anything with mass which he cannot do in ME22N.
    if he can do it in ME22N, why should he not be able to do it in MEMASSPO?
    Based on what criteria should a item be restricted from a change in your special case, how do you define your subset?

  • Purchase Order Condition values

    Hi Friends ,
                 I'm facing a problem in identifying a data source for  Purchase Order's. On searching in SDN Forum i came to know that there is no standard Datasource for Purchase order conditions.
                 Can some one give me little clue of how to pick up the conditions from R/3 to my biw system.
    Thanks and Regards,
    Vijay

    Hi Anil ,
             Thanks for your response.
             On analysing the condition table KONV in R/3 one thing striked my mind.
             Either it's Purchase order or Sale Order the condtion table is one , that is KONV. So if the condition number is available for a PO i think very well we can pick it for po's.
             Can you give me your suggestion on the above...please.
    regards,
    Vijay

Maybe you are looking for