Nonstock material PO value should not allow to change once it picked fromPR

Hi There,
when create PO for non stock material it will pick price from PR to PO once it pick the value again it should not allow to change.
so what ever value is there in PR same should be in PO also even if we try to change PO value system should not allow
so please advise me

Dear
If you want to copy the price from PR to PO do the following settings
Here we have to do:
First create a parameter in
SPRO>Materials Management>Purchasing>Authorization Management>Define Function
Authorizations for Buyers
set the following fields:
Order price adoption, Ref. to PReq, Change source, Change
OTy./it. cat. and with Field sel. equals to AKTH. After created
this parameter we have to set the users profile (using SU01 Transaction) with Parameter
EFB (Function Authorization: Purchase Order).
After doing all the settings what i mentioned, when you create the requisition that time before saving you have to select the price adoption as net or gross than only it will copy to the po because default is do not copy
so go Valuation tab in the requisition and in PO price field select as nte price or Gross price than save the reqs
now if oyu create the PO you will see the price
Regards

Similar Messages

  • PO data should not allow to change

    Dear Forums,
    Can any body so kind to find a way in solve the following business requirement:
    In my client business scenario the PR only subjected to release. PO against the PR not go for any release.
    My client require the user should not allow to change the data of PO which is pick from PR (PO created reference to PR).
    For example : user should not allow to change the quantity in the PO which capture from PR while creating the PO reference to PR.
    Your early reply should highly appreciated.
    Regards,
    sp sahu

    Hi,
    there is no standard way of doing this and I am not sure that it should be done.
    How are you going to be able to correct errors and set deletion flags, delivery completerd flags etc. if the PO is blocked for change?
    If you really want to do this then  I would create a new document type that has the requisition reference field set to mandatory. This means that the document tyoe can ONLY be used for creating POs that refer to requisitions. Then change the field settings for this new PO document to display only in ME22n.
    That way, POs that don't reference a requisition will use another PO document type that has the fields set to open for input in ME22n.
    Would this do what you need to do?
    You should also look at the EVO and EFB parameters and config (in the Purcashing config menu under environment data > Default values for buyers (the EVO paraneters are maintained here)  The EFB parameter (the more powerful settings) is configured in the purchasing > Authorisation Management > Define function authorisations for buyers)
    Read the configuration text help and note the flags and what they do.
    Steve B

  • How to set MM02 should not allow to change account and costing view

    Hi all guru's
    How to set MM02 should not allow to change account and costing view details for orher users expect me,plz help me
    thanks
    ramesh

    Hi Ramesh,
                       Use the Authorization Object:  M_MATE_STA     Material Master: Maintenance Statuses
    Below are the Views for the MM02, Field STATM
    Whichever not wanted to be changed, please dont provide them.
    A     Work scheduling
    B     Accounting
    C     Classification
    D     MRP
    E     Purchasing
    F     Production resources/tools
    G     Costing
    K     Basic data
    L     Storage
    P     Forecasting
    Q     Quality management
    S     Warehouse management
    V     Sales
    X     Plant stocks
    Z     Storage location stocks
    Regards,
    Yawar Khan
    Edited by: 1234_abcd on Jan 10, 2012 8:14 AM

  • After creation of PO system should not allow to change the price in PO

    Hi There,
    In my scenario once PO is created then after send to vendor PO print document,Users are changing the price in PO.so system should not allow to change the price in PO once PO got saved.
    So please advice.

    Hi,
    you could set in customizing for field selection keys the net price      
    to display for ME22N so that changes can not be made         
    (transaction OLME -> purchase order -> Define Screen Layout at Document Level).
    Please check that you have set all the relevant field selection      
    groups to display: AKTV, ME22, ME22N... (read and apply note 30316)                                                                               
    Other workaround is try to do by yourself with the badi                      
    ME_PROCESS_PO_CUST and send your own error message.    
    Regards,
    Edit

  • If PO is created Or approved   reference PR,  should not allow to change th

    Dear All
    I have one requirement
    If PO is created Or approved   reference PR,  should not allow to change the quantity or line item.
    And is it possible to assign this to user specific whether to allow or not .
    Thanks in advance
    Mahisap

    Thanks for reply
    MY Requirements are
    1)A  PR line item should not be changed after creation of PO or after PO approved
    2)In case PR is referenced for multiple po's then should check all the po's
    3)if po line  item deleted then system should allow to change PR
    4) Assign it to user specific
    plz get me outoff this
    regards
    mahisap

  • After approv status inquiry, it should not allow to change anything .

    Hi,
    As per the client requirement, we have assigned the three level status profile to in inquiry process like Block status, Review and approve status.
    Block status-It is initial status. After save the document it will be in block status
    Review status u2013It is the 2nd status. After review of authorized person, it will be changed as review status.
    Approve status- If everything is correct, then higher authority will give the approval for same and will change the status.
    Here client requirement is after approval of same inquiry document, it should not allow to anybody to change anything (quantity, material, any addition) in same document with va02 Tcode. Need your support if anything possibility is there for same requirement.
    Thanks
    Utpal mishra
    Sr.SD Consultant

    Already another thread is still open. Please maintain one thread for better monitoring.
    Thanks
    Regards,
    Reazuddin MD

  • Not allow to change pricing condition in Billing,,,

    Hi ,
    I want to know the user exit or other solution for following:
    System should not allow to change the value of basic pricing condition type in billing.
    Ex. In sales order value of condition PR00 is 100, then it should not allow
    to change the value of condition type PR00 in billing. If requires to change, it should allow
    to change in sales order only.
    Thanks & Regards,
    Sachin

    For this no need to use user exit
    goto V/06 condition type details
    choose which condition type u want to give display view 
    go to controlling tab or changes can be  made , uncheck the value and amount fields. than system should not allow to change the condition type in sales order level also.
    (or)
    if u want in billing document only
    configure copy controls between delivery document to billing document (VTFL)
    goto item category, select item category (TAN)> details and add pricing type E.
    try this
    regards
    siva

  • During PO creation system should not allow to save if it cross the PR value

    Hi,
    As I said in above subject line while creating the PO system should not allow to create more than the PR value and Quantity.
    Always system should allow the person to create the  Po with in PR value as well quantity in order to set up please let me know the configuration settings.
    thanks in advance.

    Hi,
    Please search the forum first for your queries for existance and then post queries., coz, the same question has been answered so many times before.

  • Restrict the user should not allow to select No Excise entry tab in MIGO

    Hi
    how to restrict the user should not allow to select No Excise entry tab in MIGO
    if the material Excisable user can bale to select the No Excise entry tab in MIGO . my requirement .... if the Pop come Please enter Excise Invoice number and Excise Invoice Date user should not change the No Excise how to restrict pls advise me
    @sakhi

    These are the options provided by SAP keeping in mind Indian Scenario. Sometimes, vendor forget to send excise invoice copy with the material, in such case, you can select 'Only Part I'.
    Even if you have maintain vendor excise details & material excise details (By mistake) in J1ID, system will throw an error message, excise invoice value is zero. In such case, we can select option 'No excise entry'.
    Your requirement can't be fulfilled in standard way. Even if you go for any Z- developement, you will lose the option.

  • The value  is not allowed for the field Cross-plant CM

    Hello All
    When i copy material in refernce to existin gone. I am getting this message
    "The value  is not allowed for the field Cross-plant CM"
    I am not putting any thing in this Basic-view Cross-plant CM, but still getting this message.
    Any help will be good...Thanks in advance...

    Hi,
    Please check the check box in front of the field config material is checked?
    If so then this material is configurable material
    A material that can have different variants.
    For example, a car can have different paint, trim, and engines.
    Configurable materials have a super bill of material (BOM) that contains all the components for producing every variant of the material. Similarly, they have a super task list that contains all the operations. When a material is configured, only the components and operations needed for a variant are selected.
    Please check
    BR
    Diwakar

  • Error in CJ88  Posting transaction is not possible (value date not allowed)

    When i try CJ88 with a wbs element, it shows the following error :
    Posting transaction is not possible (value date not allowed)
    Message no. AA 478
    Diagnosis
    A retirement was already posted on the asset 000022400733 0041 on 20091231. Based on the value date 20091231 of the transaction, this transaction should have been included in the calculation of values for the retirement.
    System Response
    The transaction is rejected.
    Procedure
    Check the value date of the transaction.
    In need to put year 2009 in date of the transaction, but it isnt posible. ¿Why? I dont know very much about asset accounting...

    Hi
    It is not allowing for WBS element final settlement, because of your asset already retairement was done.
    By best suggetion is, You will create the new WBS element and transfer the all cost line items from old WBS element to new WBS element, then you will try to settlement for another asset in CJ88.
    I hope it will use for you.
    Regards
    PVCPVC

  • PO values should not exceed PR values

    Hello
    PR value should proposed while creation of PO wr to PR, whenever Info records
    are not mainatained and PO values should not exceed the defined limit
    Regards
    sapman

    Hi,
    You cann't restrict the PO value based on PR value, because the PO value is taken from Info record, Previous PO or Manual entry.
    But PR value is from Material master or Manual entry.
    Moreover PO value also includes other conditions like discounts/freight/duties etc on the net value so there is no fixed value for PO net price.
    But PR will be always a fixed price means either from Material master or Manual entry based on the cost of the material.
    So SAP has provided only qty restiction from PR to PO ( Message no. 06076)
    but not for the PR value to PO value.
    rgds
    Chidanand

  • Billing value should not exceed contract(value based contract) value

    Hi,
    We are using value based contract and in item category we set E in incompletion rule which stops me to create relaease order where its value exceeds the contract value.
    But via release order we recognize revenue(service based revenue recognition) and we do billing directly through contract via milestone billing plan,
    At present i can bill more then my contract value.Now i want to system should not allow me to bill mre then contract value.
    I checked the option in VOV8 and VOV7 but all those are meant for release order not for bliing.
    Thanks in advance.

    Hi Satya
    You can set the billing amount in milestone billing plan itself. based on that value billing will done.

  • In Sales Order Users are not allowed to change price for any material

    Dear all,
    Please give me the solution :
    In Sales Order va02 Users are not allowed to change price for any material .

    Hi Amit
    If you  want that in VA01 manual as well as other pricing condiion entry and cahnges to be allowed and only in va02 users should be restricted ,then  you have following alternative.
    Go to  T.Code SHD0
    Select Transaction VA02.
    Create a new variant ,give suitable name.
    select option change with processing.
    So u can run a va02 transaction and for every screen u can create screen variant and control data entry whether required  , dispaly or hide.
    in this for  LV69a pricing  screen disable update button .
    so system wont change anything updated or cahnged in pricing.
    further you can create the variant transactions  from this transaction variant and assign to different users as per control requirements.
    I think this will help you
    Regards
    mandar

  • Duplicate record should not allow to enter

    hi
    i have three columns
    sno Number;
    in time date;
    out time date;
    this is the multiple taulat layout :
    User enter at run time values like this :
    1 01:15 03:00
    1 01:15 03:00 Here second record User should not allow to enter same Sno for Same In time and End time
    Before entering the data the total no of records : 0
    can u give me any suggestion.
    how to validate the columns.

    If you have a Unique Constraint on the table for these there columns it will prevent duplicate records.
    1 01:15 03:00 Here second record User should not allow to enter same Sno for Same In time and End timeBy "Second User" do you mean a user in a seperate Forms Session? If so, there is no way to check if the user in session 2 is entering a duplicate of a record entered by a user is session 1 accept through the use of a unique constraint on the table.
    There are methods available for checking for duplicates in the same Forms Session. Check out: Avoid duplicates in the same block and Forms: Record Group Processing (Duplicate Value Checking) for more information.
    Hope this helps,
    Craig B-)
    If someone's response is helpful or correct, please mark it accordingly.

Maybe you are looking for