Net price field should not be edited in PO, when created reff. to contract

Dear friends,
I have a requirement like this.....
User referring the contract in creating the purchase order, details of the contracts are copied in to the purchase order. the price field is in edit mode....
requirement is that user should not edit this field, the price carried from the contract should be not edit mode. this is to be hapen only when purchase order is created referrence of contract.
here we are using only the standard document type is used for creating Purchase orders with and without the referrence of contract.   
Thanks in advance...
Shashidhar

What I did for a client was implementing enhancement (user exit) MM06E005 to perform checking during PO creation.
OSS note 310154 explains how to issue error messages from ME21N from the user exit.

Similar Messages

  • How to make net price field in Purchase Order Uneditable

    Hello all,
    I am facing a problem. During creation of purchase orders the material price is picked up from the Info Record, but the net price field is editable. Please guide me how through standard SAP can i make this net price field uneditable.
    Thanks in Advance,
    Ritesh.

    Hi Ritesh,
    You can goto:
    SPRO-MM-Purchasing-Purchase Order-Define Screen Layout at Document Level
    from here you select ME21N-Selection group-Quantity and Price.
    Make the price and price unit as DISPLAY.
    By this it will show only display for price, but you have to take not that there is also condition tab which user can change the price, this price is from INFOREC.
    Goto to M/06 select your Condition type, In Manual entries maintain "D"-Not possible to process manually
    Regards,
    Maia

  • Make net price field in me12 modifiable.

    How to make net price field in me12 modifiable.
    I have screen Layout & Screen variant but didnt get any clue.

    the net price is a calculated field  in case you maintained price conditions (big button on top of the screen), then it is not changable anymore.
    the net price is just information  for the user, it is not taken as price to a PO if no condition exists.

  • Massage No. 06217-Overflow for net price field during conversions

    Can anybody tell me the S note for the error?
    "Massage No. 06217-Overflow for net price field during conversions"
    There is a S note in OSS ( 576188) which is Obsolete now. I would like to have the correct S note to apply.
    thanks
    SACHIN

    Hi,
    SAP doesn't support item prices larger than 999.999.999,99. This is a limit of the system.
    The field has a length of 11 and output length of 16 for the commas and dots. Therefore, values entered in that field cannot exceed the total length of the field.
    Increasing the field length of the field is challenging. This would
    cause inconsistencies in the existing dataset and more problems in
    in Finance modules.
    You have to look for possible workarounds to resolve this. You may
    choose to split the documents, line items or quantities - what suits
    your business requirements best.
    You may choose to:
    1. Split the line items.
       This is applicable when your company wants to procure 1 single item
       with say 1 Billion value.
       for example:
       Qty  Unit       Net price
       1    EA          1,000,000,000.00
    This may be cost of one machine or asset.
    You may split this into accessories or mountings used for this as
    separate line items, so that the cost of the line item will be less
    than 1 Billion.
    2. Splitting the quantities,
       This is appliable when you are procuring more quantities with higher
       value items.
       For example:
       QTy        Unit        Net price
       1000000      EA          100000.00
    You may split this quantity into 250000 EA * 4 = 1000000. With this
    you may consider having four line items in the same PO or 4 differant
    PO's.
    3. Consider using pricing unit.
       If you use currencies in which higher values become necessary, SAP
       recommends to use smaller units of measure (for example "box"
       "pallet").
       For Example:
       Qty        Unit          Net price
       1        Pallet         1000000000.00
    In this case you may split this into Boxes. May be the Pallet contains
    more than 1 boxes. The net price of the box will be less than
    the Pallet.
    If your prices is not larger than 999.999.999,99 then please open a ticket in SAP, as this would be a bug and you would need a correction, that at the moment does not exist.
    Best Regards,
    Arminda Jack

  • Net Price column should be in grey Mode

    Hi All,
      I have one requirement. In ME21N Transaction the net price column should be in grey mode based on some vendors only. Those vendors will maintain in ZTable. If that vendor will give in ME21N then that line item netprice should be in grey mode.
    How can i achieve this?
    Please help me..
    Regards
    Nageswar.

    Hi Nageswar,
    Below simple configurations will help.
    SPRO->SAP Customizing Implementation Guide->Materials Management->Purchasing->Purchase Order-> Define Screen Layout at Document Level->Double click on ME21N row entry ->double click on Basic Data, Item -> Navigate to required Selection group.
    Regards
    Gangadhar

  • Header condition type should not be editable at item level

    Hi gurus,
    could  you please help me with the following question.
    Our requirement is to provide header discounts manually at header level which should not be editable at item level. So I've created condition type as Header condition.
    When we manually add this condition at header level in Sales order, it is copied to the item level and is not editable there.
    But after saving the SO, we find that the header discounts appearing at the item level becomes editable.
    Kindly  advice how to make the condition type as non-editable at item level.
    Thanks in advance.
    Sunny.

    hi Sunny,
    please check your condition type for discount in section 'Changes which can be made', wheather it used only for the header level or item level or both of it.
    if you want to make the condition is not editable in item level, then you must made the condition type just for the header level.
    beside changing the configuration in the condition type, you can protect it via BADI but it needs more programming.
    if you insist to use the BADI, you can made the implementation of class CRM_ORDER_FIELDCHECK BADI
    hopes it helps
    cheers

  • User should not have edit access in EAS

    Hello Gurus,
    My requirement is : I or my team mates are not supposed to have any access in EAS to make any changes to applications / databases on an Essbase server. i.e. I should only be able to view outline, see statistics, see if any sessions are running etc. I should not be able to copy application, create application, delete application, edit outlines etc.
    Please let me know if there is a way to do it.
    Thanks

    Viewing Active User Sessions
    "The Sessions window displays a list of active sessions. If you have Administrator permissions, the window lists active user sessions for all users on the Essbase Server. If you have Application Manager permissions, the window lists active sessions for all users, including yourself, who are connected to any application for which you have Application Manager permissions."
    Cheers
    John

  • User should not release the PR which is created by him

    Hi
    We didnu2019t use work flow functionality for PR Release. So same user can create PR and release the same PR in our system. Our requirement is user should not release the PR which is created by him. I would like to put this control in system.
    How can I achieve this requirement?
    Thanks
    Jeny

    Hi Ravi
    Thanks for your reply. but they need to have authroization for PR release . bec they are eligble to release PR as per delegation of authroity. but they should not release their own PR . they can relase other's PR within their level.
    Jeny.

  • Field should not display in the subtotal row in ALV report after sorting .

    we have a requirement, after sorting and subtotaling, the output in ALV is -
    vbeln        amount1  amount2  amount3
    123           11              12            13
    123           12             13             14
    123           23             25             27 
    133           11              12            13
    133           12             13             14
    133           23             25             27
    Now the customer wants the ALV outpput in this fashion -
    123           11              12            13
    123           12             13             14
                     23             25             27    --->123 (vbeln) should not come in subtotaling row
    133           11              12            13
    133           12             13             14
                      23             25             27--->133(vbeln) should not come in subtotaling row

    Hi,
    if it helps you could create a hierachy. In this way you can define the field catalog for the lines and for the subtotal columns. The only thing is that you would always show the subtotal rows.
    You have references of hierachy alvs in
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c060fcb4-2c62-2b10-d2b2-f32407a5cc6f
    ALV Hierarchy
    alv hierarchy
    In this case it also sorts
    Sorting for ALV hierarchy
    I hope it helps.
    Edited by: Oscar Pecharroman on Aug 2, 2010 1:13 PM

  • Basic price PB00 should not  be changed in PO

    Hi Friends,
    I need your help to solve the following issue
    The requirement is, if the Basic price PB00 is flown from info record to PO , then Buyer should not have option to change the price in PO.
    I made following setting but my requirement is not met
    For Condition type PB00 , I made “B-Automatic Entry has priority” in customizing , for  PO  “Net Price” I made the filed as “Display only”. While creating PO the price maintained in Info record is flowing and I am not able to change the price. That is fine. But  when I select manual basic price condition type PBXX and give the value then system is taking the value in PBXX which I do not want . The price flown from info record should be the final price. (if I maintain the PBXX also as ”No manual entry is possible” then  buyer can not select PBXX . But I want PBXX with manual entry as priority)
    Request your help to find a solution to this issue   
    Thx
    Deva

    Hi,
    In Info Record, you can maintain the required condition (PB00 / PBXX) & then click on 'Details' icon. There you will find the upper & lower limit. You can maintain both the limit values same as the basic condition. This will ensure that the user will not be able to change price in PO.
    Further you may restrict authority of Maintaining Info Record, so that the buyers will not be able to access & change Info Records.
    Regards,
    Prashant Kolhatkar
    - Reward points if answer is helpful.

  • Make Net Value Field at item level Editable in Sales Order

    Hi
    All pricing in our system are manual .
    So the client wants to change the Net Value Field in Credit and Debit Memo Request to be Editable ( Currently it is not modifiable)
    Plz suggest how to g about it.
    Do i need to use Userexit_ Field_ Modification, if yes how , The field VBAP-NETWR.
    REgards
    Rohit

    Hi Yadav
    Changing Net Value will effect the updation of various tables ...so u r right not the correct approach .
    Can i put condition type and its value in Credit Request Memo and its value aditable same as in screen for Sales Order .if yes how , changing screen sequence group in credit memo request is creating problems
    Regards
    Rohit

  • Net price field length limitation in purchase order

    Hi
    The maximum net price PO line item accepts is 999999999.99.
    If in given scenario, it is not possible to break the line into multiple lines nor possible to use alternate units, what are the solutions available?
    How to handle similar situation in services?
    Appreciate any guidance on this.
    Thanks
    Sriram

    I have two business cases that my clients is facing right now.
    1) Capital increase   (Actual)
    Due to the World financial crisis my clients like many other issues had a capital increase transactions done thoriugh issuing bonds. The client has a policy no PO no PAY and this is enforced 100% in this case they needed one SAP PO recorded covering a large amount   Amount was in THB and exceeded the unit price field limitation.
    Work around was to make the PO line item 2 x YYYYYYYYYY
    2) Purchase of a vessel  (Will happen in the future)
    This is a  transaction with 1 x YYYYYYYYYYYYYY large amount which again exceeds the limitation.
    Despite workarounds are available like increasing the quantity, using different currency.. the client is till questioning the limitation that SAP have.

  • SOME FIELDS SHOULD NOT SHOWN IN THE REPORT

    Hi,
    this is to inform you that,  there is a requriment in reporting perspective (ALV),
    Requriment:
    i have to generate a ALV report which is viewed by our CFO with one t.code, in that report suppose there are 10 fields. 
    That is a specific report if some body apart from my CFO uses the same tcode to generate the same report than it has to display only 5 fields.
    if my CFO uses the same t.code all the 10 fields must be visible.
    please help me how to do it.
    regards,
    balajia.

    There are couple of ways to achieve this,
    1) - Create 2 variants, 1 variant for CFO with all the fields  & 2nd variant with only relevant fields. Then use the authorization concept, where basis can restrict the access / execution of the report with specific variants.
    From the basis view, they create role & assign this variants in one of the object ( not sure). Basis assistance required
    2) - When developing report, write the validation for the respective fields such as maintain Customize table in which maintain userID's & fields which they can access. Display only those fields to the userID who executes this report. It should check this customize table for this UserID & only those fields listed should get displayed. ( for all the fields, instead maintaining each field, you can enter "ALL",
    Eg: UserID -
    Fields
           CFO -
    ALL ( report should display all the fields)
         NONCFO-------Field1 | Field2 | Field3 | Field4 | Field5 ( only these fields should get displayed)
    Note: In Customize table either you can maintain with User ID or Role. It will be more convinient in future as well.
    Regards,
    Reazuddin MD

  • Price field is not becoming invisible from the item overview of SRM quote

    Hi All,
    I am facing a very unique problem . I need make certain fields invisible in the SRM quotation . One of them is the price field at the item level.
    I have used BBP_UI_CONTROL_BADI for the same. However the field is NOT becoming invisible from the item overview. It is becoming invisible from the item detail but NOT from the item overview.
    Is it because the field is defined as display only in the code ?
    I have implemented note 1062639. Other than this price field I am able to make all other fields invisible from the item overview.
    Code :
    IF iv_fieldname eq 'BBPS_BID_UI_ITEM-PRICE'.
            cv_invisible = 'X'.
    ENDIF.
    IF iv_fieldname eq 'BBPS_BID_UI_ITEM-PRICE_UNIT'.
            cv_invisible = 'X'.
    ENDIF.
    Does anyone have any suggestion as to how to solve the problem ?
    Regards,
    Ajali Sen

    Dear Poster,
    As no response has been provided to the thread in some time I must assume the issue is resolved, if the question is still valid please create a new thread rephrasing the query and providing as much data as possible to promote response from the community.
    Best Regards,
    SDN SRM Moderation Team

  • Query..for Field should not accept the manual entry

    i wann query for remarks Field in JE It should Not accept the manual entry it should accept only sys drop data.
    Thanks & Regards
    yogi

    For this field level authorization, you may only use SDK or SP to reach your goal.  SP would be difficult to use in this case.
    Thanks,
    Gordon

Maybe you are looking for