How to disable pricing condition create with reference in VK11, VK12 & VK13

we have given the release status for all pricing entry; from VK13 pricing display mode if we select create with reference then Proc status is defualtly it is in the released status.

Hi,
I feel that the Generation of Field is not properly done, while creating the table. you can create the new table with the same fields and click on the icon FIELD GENERATION at the left corner of the screen with red and white circle. you can confirm by clicking on the field attribute icon.
hope this will help,
Reward if help
Manoj

Similar Messages

  • How to disable pricing conditions from editing in sales order's(vA01) and (VA02)

    Hi Experts,
    We have a requirement to disable all the pricing conditions in a sales order from editing where some user's are changing the prices manually.
    This should be disabled for particular order types and also based on the user's role in SU01. can anyone help me to fulfill this requirement.
    Regards
    Sree kumar.

    Hi
    Check my below document in which I have explained this in detail.
    Authorization for entering/displaying manual condition in Sale order.
    Thank$

  • Can Two Invoice be created with reference to one Return order

    Dear All.
                  Can two SR Invoice be created with reference to one SR Order.

    Thanks JP Sir,
                       Much appriciated ,we are having SAP IS:AFS(Our Business is of Manufacturing & Marketiing.Consumer product.
    Sir- I created a SR Order after creating it forgot to do PGR & without  doing PGR I opened sales log in order & created SR Invoice without doing PGR & when I check it in VF03 ,Issue print out then there was not any material discription in Created Credit Invoice & when I checked Display document then there were no any delivery document then I came to know without doing PGR how material  can be copied  & then did PGR  with reference to same SR Order  n created another Invoice .but my question is that without cancelling previous SR Invoice how another Invoice can be created with reference to same SR Order.
    Thanks,
    Kamlesh

  • Add pricing condition within order created with reference to SPA

    Hi,
    I have a requirement wherein I need to add a $50 fine to order if the total order weight is below 75 kg.
    Problem I am facing is with orders created with reference to SPA wherin pricing is not calculated but copied from SPA.
    Please help me in solving this issue.
    Also, Please let me know the pricing userexit / BADI for CRM wherein this can be coded.
    Regards,
    Willban
    Edited by: willban_sap on Jul 21, 2010 11:43 AM

    Hi Willban,
    wonder wether you could use any weight dependent (net or gross) group condition with a scale. Delow 75 kg across all grouped items you would charge 50 $ and starting at 75 kg you would charge 0 $. As the scale base should get adjusted with the copy / create with reference step, I see no need for custom code.
    Best Regards,
    Michael

  • Condition types doubling/tripling/...when sales documents created with reference to other documents

    Hi,
    When I create a sales order with reference to a Quote, the pricing condition types are duplicating. Same is happening when subsequent documents like Billing, credit memo request and credit memo are created. Particularly, the condition types  are doubled/tripled/.... in the subsequent documents. Because of this, pricing net value is calculated wrong. For example, freight charges getting added twice. I searched the forum and found similar issue was discussed at Condition types - Doubling UP  raised by forum member Sridhar Vijjhalwar, however there is no solution added in it.
    Has any other member came across this issue and resolved?
    I have checked the access sequence and exclusive indicators are checked. Copy controls are also checked, looked good and I tested by adding copying type D/G. Checked OSS note also and found one OSS note 1459807 - Invoice has missing/incorrect conditions when created from a sales order.
    but it is not solving the problem either. Issue also elevated to SAP for their investigation. Our system is SAP ECC 6.0 - EHP6.
    Quote Pricing:
    Sales order Pricing:
    I appreciate any pointers to resolve the issue.
    Regards,

    what was the scenario, and how did you replicate?
    It is a configuration for a new project (France country), however we found that the same issue popping up for existing business processes also. As for replicating, we just tried the same procedures, the issue is found in subsequent documents.
    If you have observed one notable thing is - all the condition types which duplicated were Z Conditions, and the standard conditions were never duplicated at least in my case.
    In our case even standard condition types like MWST, SKTO, GRWR, VPRS also shows duplicating.
    if you can throw about the business process?
    As you have mentioned order created with reference to quote was only the straight forward scenario?
    I tested other scenario also, like creating a sales order, then delivery and then billing. In this case in billing document, the condition types are duplicating. If I create a credit memo request against the billing document, then it further duplicating.
    I am not sure what is causing this. I initially thought it may be copy control settings pertaining to the new project, however other business documents also has the same issue. Other business are using different document types.
    Thanks for your follow-up.
    Regards,

  • Create condition record with reference to existing condition record

    how to create condition record with reference to existing condition record?

    Hi,
    See this link :
    http://help.sap.com/saphelp_47x200/helpdata/en/de/7a8534c960a134e10000009b38f83b/frameset.htm
    You can create with reference with Tcode : VK14 (or VK34)
    Or in VK12, you can copy condition records with copy rules.
    Regards,
    Lionel

  • How to implement a Copy or Create with Reference scenario

    For business objects, you might want to implement a Copy or Create with Reference scenario. The following procedure describes the UI configuration that you need if you want to place a copy button (in our example on an OWL) that starts a quick activity floorplan (on the same BO = Copy, or a different BO = Create with Reference). Pre-requisie in the target BO: The target BO requires a BO element SourceBOID and a Copy action that reads the SourceBO by SourceBOID by query, and copies the elements from the source to the target BO.
    The UI configuration in the target floor plan is:
    1. Open the QAF floor plan of the target BO (target floor plan).
    2. In the DataModel view of the target floor plan, select the Root entry and select Add Data Field from the context menu. Rename the created data element to OBN_OriginBOID.
    3. Choose the Controller tap, and select INPORTS and choose ADD INPORT from the context menu. A new in-port is created. Rename the in-port, for example to Copy.
    4. In the in-port maintenance form, activate the check box OBN INPORT.
    5. Select the namespace of your solution and the target business object.
    6. In the input field SELECT OPERATION enter Copy. A new select operation is created. The combination of business object name (including namespace), business object node and operation identifies the in-port and therefore the related floor plan as navigation target.
    7. Select the port type package /SAP_BYD_UI/SystemPortTypes.PTP.uicomponent.
    8. In the PARAMETERS section of the form, click the ADD button. Maintain the binding of the created parameter to /Root/OBN_OriginBOID. Based on this configuration, the system will transfer the parameter of the in-port to the element in the data model when the OBN is executed.
    9. In the Properties view, select the drop-down list box of the property EVENTS u2022 ONFIRE. Scroll down and select the entry u2026 NEW EVENT HANDLER u2026. The system starts the maintenance window for event handlers. Rename the event handler to CopyIn.
    10. In the OPERATIONS table of the maintenance window for event handlers, select type: BUSINESS OBJECT OPERATION. In the form below the table select the value CREATE for the input field BUSINESS OBJECT OPERATION TYPE. This operation will create a BO instance in the backend when the OBN is executed.
    11. In the OPERATIONS table, create a new operation of type: DATAOPERATION.  In the configuration of the data operation, select the operation type ASSIGN, source expression /Root/OBN_OriginBOID and target expression /Root/<BO>/OriginBOID.
    12. Create a third operation of type: BUSINESS OBJECT ACTION. Select the Copy action of the target business object and click the BIND button. Note: This action enforces another roundtrip to the backend. The Copy action must be implemented so that it will read the origin BO and copy selected data from the origin to the newly created object.
    13. Test the changes in the preview. If no error message is issued, save and activate the floor plan.
    The following procedure describes the configuration in the source floor plan (e.g. OWL floorplan ):
    1. Open the Source BO OWL floor plan (source floor plan).
    2. In the Designer view, place cursor the on the toolbar area and select ADD u2022 APPLICATION-SPECIFIC BUTTON u2022 MY BUTTON from a context menu. Rename the new button to Copy.
    3. In the Properties view, select the drop-down list box of the property MENU INFORMATION u2022 NAVIGATION. The system launches the maintenance window for OBN configuration.
    4. Select the in-port of the target floor plan by selecting the target business object (with namespace and name) the target business object node and the target operation, and the operation Copy.
    5. Choose the navigation style NEWWINDOW.
    6. Close the OBN configuration maintenance window by clicking the OK button. The system creates the OBN configuration, an out-port, that is used by the OBN configuration, and an event handler that uses the out-port and that is assigned to the button (see Properties view, EVENTS u2022 ONFIRE).
    7. Go to the Controller view and rename the OBN configuration to Copy, the new out port to Copy and the new event handler to CopyOut.
    8. Check that the event handler CopyOut fires the out-port Copy.
    9. In the Parameters section of the out-port maintenance form, click the ADD button. Maintain the binding of the created parameter as /Root/<BO>/<BO>ID. Based on this configuration, the system will transfer the identifier of the selected source BO to the out-port data structure when the OBN is executed.
    10. In the Operations table, select type: FIREOUTPORT. In the form below the table select the out-port CopyOut.
    11. Test the changes in the preview. If no error message is issued, save and activate the floor plan.

    Hi Dries-
    There are no pre-packaged solutions with BADIs since they are, by definition, custom development.  If that's the path you need to go down then consider the following high level alternatives:
    Incorporate custom code into the BPC Write Back BADI.  You can restrict the execution of the BADI using filters on the BADI definition, so that the BADI execution only occurs when a data manager package is called, and only for some defined combination of applications/appsets.  Utilized the standard copy/move functions delivered in Data Manager. When the BADI is called, interrogate each record being processed (table CT_ARRAY) and determine if the record has a value you want to process (i.e. save to the target application).  Skip any record that has a zero value.
    Another alternative is to develop the BADI as custom logic.  Data Manager parameters can be picked up in Script Logic and the values can be sent to the BADI by adding parameters.  Please see an example of parmater use in the "How To" document for Destination App at:
    [EPM How To Guides|https://wiki.sdn.sap.com/wiki/display/BPX/Enterprise%20Performance%20Management%20%28EPM%29%20How-to%20Guides]  > "How-to Desitnation App"
    Regards,
    Sheldon

  • How to differentiate the Purch Orders created with reference to in table

    Hi all
      how to differentiate the Purch Orders which are created with reference to Purch requsitions, contract, manual by copying inforecord in the table EKKO/EKPO? Is there any Field Indicators?
    Rgds
    Ramesh

    Hi Ramesh,
    Go through  EKPO there is a Table BANFN it will update when you create a PO with reference to PR
    Do se11 > Table EKPO> CtrlShiftF10 > Assign any of PO no. in the EBELN > Execute > you will find BANFN table
    it indicates Purchase Requisition Number. it will update when you create PO with reference to PR.
    Regards,
    Vraj

  • Remove Header text from a sales order, created with reference to quotation

    Hi all,
    I have a sales order(in VA01) which is created with reference to quotation (in VA21).
    If header text (Notes for logistics, Note for responsible person, Header text Doc & Declaration) in texts tab is maintained in the quotation they are getting copied in Sales Order which is NOT the requirement.
    I need suggestions on how to disable the text that is getting copied.
    Any pointers would be of great help.
    Regards,
    Vamsee Priya.

    Hi Nilesh,
    I created a routine in vofm and this solved my problem.
    Now, I'm having a similar problem where I'm creating an Invoice(through transaction VF01) giving the delivery document number and document type (Invoice F2).
    we are maintaining Header text in Order through which the above mentioned delivery document number is created and this header text should get copied in the Invoice.
    For this, I went into Transaction VOTXN, from there selected billing header, from here kept a break point for the routine BEDINGUNG_PRUEFEN_001 through which the text will get copied.
    Now, when I'm creating the Invoice this routine is getting executed, but still the text is not getting copied.
    Any pointers on this would be of great help.
    Also at the end of your previous mail, you are telling about SPRO - text assignment. Can you please let me know how to I should navigate to this text-assignment??
    Thanks and Regards,
    Vamsee Priya.

  • Sales Order Created with reference to Contract - Exchange rate Issue

    When Sales Order created with reference to contract VBKD fields KURSK and KURSK_DAT gets copied from contract and not redetrmined based on pricing date and Exchange rate type. I expected it to be determined based on pricing date is standard. What I am missing, should it be controlled by data transfers
    If Document currency and condition currency are different it cause problems with incorrect condition values are calculated, as KOMP-KURSK are copied from VBKD-KURSK
    Any help or directions would be greatly appreciated . We are on 4.7 ISOIL
    Sincerely Julietta

    Well,
    and if we have the same issue, but we don't have OIL Version, but simple 4.6C, which solution has to be applied then?
    Thank you
    Standa

  • Credit memo to be created with reference to return delivery

    Dear Gurus,
    We have a requirement for mapping return process
    Credit memo to be created with reference to return delivery (instead of with reference to return order)
    Following issue faced in mapping the same:
    Billing document No. 1234 dated 25.03.2010 where there is 4% VAT.
    when we are creating return order with reference to billing document 1234
    4% VAT is calculated since the Service Rendered date is 25.03.2010 (Copied form Billing document)
    return delivery is created today 08.04.2010. (VAT revised to 5%)
    when credit memo is created with reference to delivery document
    VAT is calculated 5% which is applicable from 01.04.2010
    since the service rendered date is appearing in billing document
    08.04.2010 (the date of Post Goods Receipt).
    The VAT should be actually 4% in Credit Memo.
    regards,
    Rajesh T

    In the copy controls from delivery to Invoice, at the item level try to use pricing type C and Pricing source Blank ( Blank is order).
    If it doesnt work , then you might have to go for a requirement routine for this Tax , based on the document category that is being processed, read the tax from the originating order.Assign the routine to tax condition in the pricing procedure.
    Regards
    Sai

  • Scheduling agreement created with reference to contract-Issue

    Hi all,
               I had posted a query as how to update net price in the contract/scheduling agreement if the condition price is updated through inbound Idocs.I got the correct answer  as you need to run the report RM06ENP0/RM06ENP1 as per note 685117.
    But now I am having a different issue;the scenario is like: A scheduling agreement is created with reference to contract.So the SA is linked to contract now.I am now going to change the condition price of SA through Inbound Idoc.After the updation ,the condition price gets changed in all cases.
    In one server,I found that the net price gets updated and the link btn contract and SA is broken without running the report RM06ENP1(Ideal situation,this is what I want).In other server ,I found the net price is not getting updated,ie the link is not broken even after running the report RM06ENP1.
    Can anybody tell me why the second situation is happening?

    Hi,
    i have done ur scenario. According to ur scenario, quantity contract is created for 100 units may be kg, pc etc.. Then scheduling agreement is created with reference to that contract but for 200 units may be kg, pc etc.. Scheduling agreement is created without getting any error or warning message.
    In the Next step, i.e. maintain delivery schedule( Tcode: ME38). U get the ERROR message as Scheduling agreement document number xxxxx is does not exist after entering scheduling agreement number in the initial screen of ME38.
    if this information is useful for u, reward me according to ur usage.
    bye
    Narasimha Rao Gunda

  • Pricing condition,automatic display without doing VK11 firstly, how ?

    Hi all, another question.
    I have a pricing condition in my sale order. and its value is determined by Pricing Conditions Routines with Conditions Value.
    How can it automatic display in the condition of my sale order, without doing VK11 firstly.
    My english is poor, so I hope u can understand these.

    Hi
    As I said in my previous thread , go to VOFM->Pricing, and check in the requirements if any standard requirements are meeting your requirement or not .If it is not meeting then create a new requirement with the help of  technical consultant.  and assign the requirement  in the Pricing  procedure requirement feild for the condition type and then check wheather it is capturing the price or not in the sales order and billing documents.
    Regards
    Srinath

  • How to migrate pricing condition data using lsmw

    Hello All,
                 can any one explain how to migrate pricing condition data using lsmw.
    the scenario is we are trying to extend the pricing conditions from one sales area to other sales area on a combination of sales organization, distribution channel and division.

    Hi Sreedhar Kodali
    Pricing conditions can be extended with the following options:-
    1)  Customer / material with release status
    2)  Sales Org / Dist. Channel / Cust group / Material
    3)  Price List category / Currency / material with release status
    4)  Material with release status
    Assuming that your pricing condition in one sales area is different to another, first you have to create LSMW recording to extend the sales area and then pricing conditions can be uploaded accordingly.
    Thanks
    G. Lakshmipathi

  • BAPI Sales Order create with reference Invoice document

    Hi
      I am using BAPI ''SD_SALESDOCUMENT_CREATE''  to create debit memo request with reference Invoice document.
      First time its successfully created with reference Invoice.When i am going to create 2nd time debit memo request with  same reference Invoice and item
      no its giving following error.
          Reference quantity:             
    10 EA (total referenced:             
    40 EA)
           Error in SALES_ITEM_IN 000010
           Condition ZSLS is not allowed as header condition
           Sales document  was not changed
        Please help any one to resolved this issue.
       Regards
       Shyam

    SD_SALESDOCUMENT_CREATE is not a BAPI. Is there any specific reason you're using this FM when the actual BAPI exists?
    ZSLS is a custom condition. There might as well be some user exit that attempts to add it [possibly incorrectly], how would we know this on SCN? There is enough information in the error message to troubleshoot on your own, it seems. What kind of analysis have you done before posting on SCN?

Maybe you are looking for