Changing currency in the Pricing Condition Records after saving

Hello,
I would like to know whether there is any way we can change the currency in VK12 in the pricing conditions records created via VK11. Please let me know.
For example, for PR00 condition type, I am maintaining condition records in VK11. I enter an amount and currency as USD and I save it. Now, in VK12, I would like to change the currency to EUR. Is this possible? Please share your ideas.
Regards,
Venkata Phani Prasad K

Closing this thread.

Similar Messages

  • How to Maintain the Pricing Condition Records in CRM

    Hi
    I am new to the CRM
    How to maintain the pricing condition records in crm for the particular condition type?
    as we do in SD(VK11)
    Thanks

    Hi Binu,
    First of all, you could maintain pricing conditions in the following places:
    1. In General Condition Maintenance (GCM)
    2. At the product maintenance level
    3. At the 'Price agreement' tab of Contracts
    4. As manual conditions during order processing at item level
    Now, if you want to maintain conditions using GCM, you first have to maintain a condition maintenance group in the customizing where in you can assign condition table and condition type for different counter values. I am assuming that you have done this activity successfully.
    When you run the transaction '/SAPCND/GCM', for application 'CRM', your condition maintenance group name and context 'GCM', you will be initially taken to a screen where in you'll have an item area which would be blank and then condition fields would be displayed in a tree on the left.
    Here, select the field 'Condition type' and click on icon 'Select records'. You would get a dialog prompting you to enter condition type. Here you can specifiy the condition type for which you want to maintain/view condition records.
    If no condition records are available, item area would be left blank. Here, you can choose a condition type using the standard F4 help. Depending on condition types that are assigned to condition maintenance group, different condition types would be displayed in the F4-help using which you can maintain condition records.
    Hope this helps.
    Regards,
    Pavithra
    **PS: Please reward points if this helps.

  • Extracting the pricing condition records

    Hi,
    I would like to extract the pricing condition records of a particular sales organization. I need to upload these records to another system.
    Any guidelines?
    Thanks a million.

    Hi,
    For Sales dacuments pricing conditions you can use :
    RV_PRICE_PRINT_HEAD  --Header pricing conditions
    RV_PRICE_PRINT_ITEM  -- Item level.
    Lanka
    Message was edited by: Lanka Murthy

  • Error in BDOC while uploading the pricing condition record to ECC from CRM

    Hi all,
    I have created a condition record for ECC pricing condition type (I have maintained all settings required for maintaining ECC condition type in CRM 7.0) in CRM 7.0. But theis condition record is not uploaded to ECC. I have checked BDOC, it is showing with error status for BDOC type "CND_M_SUP". The errors are as below.
    1. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
    Message no. CND_MAST064
    2. sBDoc CNBCCPSAP005 does not contain structure CDBD_CONDREF
    Message no. CND_MAST064
    3. Service that caused the error: CND_MAST_INT_DEEP_MB_TO_SBDOC
    Message no. SMO8047Diagnosis
    A service caused/ reported an error.
    Can some one help me in fixing this issue  please.
    Thanks in advance,
    JM
    Edited by: JM on Sep 7, 2010 4:46 PM

    Hi,
    sBDOCs are not used in ECC to CRM or CRM to ECC data replication scenario. You can either ignore the error or disable mobile bridge.
    Regards
    Prasenjit

  • Pricing condition records should not be picked up

    Hi,
    I have configured a scenario for Supplementary Invoice for which I created a new sales order type. The requirement is such that this order type should not pick the pricing condition records that have been created in VK11. Please suggest how can this be configured.
    Do I have to use any Userexits, if so which one?
    Regards,
    Abhishek

    As mentioned by you, you have created a new Sales Order Type, you can create a new document pricing procedure, based on which you can determine a new pricing procedure.
    To configure new Document Pricing Procedure:
    IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Define Document Pricing Procedure. (Maintain the new Document Pricing Procedure in new Sales Order Type)
    Maintain a new Pricing Procedure, maintaining the Condition Types as manual. Maintain the determination of Pricing Procedure appropriately.
    Pricing Procedure Determination:
    In SD, Pricing Procedure is determined (T.Code: OVKK) based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    Pricing Procedure Configuration:
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure (T.Code: V/08):  It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
    Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
    Regards,
    Rajesh Banka

  • Pricing condition record

    Hi All,
    There is a problem with the invoice condition records.In our case invoices are actually created via Idocs.
    Usually the condition record type is sent in the Idoc and the corresponding condn. type comes in the invoice.But in one case,the Idocs do not have a particular condition record type present in the data segment ,yet the invoice when created has the condition type in it.
    Does any one have  a idea if the condition type gets picked from any master table or is there any other way it  appears in the invoice.
    As far as the program that creates the Idocs,It picks the condition records from a Z table and fills in the Idocs.
    Thanks for your help!
    Regards,
    Gowthami SK

    Hi Sam,
    the preceding document is the sales order.
    the scenario is like the sales order gets created through Idocs (msg type:VLCCPO),the pricing condition record is filled in the Idoc ( KSCHL) and it appears in the invoice.
    But in a particular case,there is no condition type in the Idoc  ,yet the condition type appears in the invoice.
    Is it possible that any standard pricing condition has been defined???
    Regards,
    Gowthami SK.

  • Duplicate pricing condition records in Billing

    Helllo evry one,
    I have an issue with an Invoice document, Where the pricing  condition records is appearing twice both at the item level and header level. 
    It is appearing as
    Condition Type     Condition base value        Condition value      
    ZABC                               20.00                                       200.00
    ZABC                                20.00                                      200.00
    Any clue at what level is might happen and how can we avoid such issues
    Regards,
    Ganesh
    Edited by: Tcode on Dec 15, 2009 5:56 PM

    Hi,
    Check  Whether the CONDITION TYPE is a HEADER CONDITION
    Goto V/06 and check the HEADER DISCOUNT filed is activate for the condition type, if yes then it will copy to Item also.
    Please check and revert back.
    regards,
    santosh

  • Pricing condition records maintanence

    Hello All,
    We have a requirement to store the pricing condition records in 3 decimal places say 1.733 instead of 1.73 that way standard SAP is doing.
    Do we have any solution for this? Can we maintain the pricing condition records in 3 decimal places?
    Any suggestions would be appreciated ?
    Thanks,
    Vinay

    chk the following thread:
    https://forums.sdn.sap.com/click.jspa?searchID=5045505&messageID=3878405
    Regards
    AK

  • Bulk Pricing condition record upload

    can any body help out for , Is there any transaction code  for uploading the pricing condition record in BUlk.
    Ex: 1000 condition records upload for condition type PR00..
    Ragards

    Dear Ramesh,
                           This you can do by creating an LSMW,one of the mass upload tool.
    Regards,
    AKD
    Edited by: Ashish Dikshit on Sep 19, 2009 9:31 AM

  • Tracking deleted pricing condition records

    Hello,
    I Have a condition record for a condition type with a  particular price of USD 100 with validity date from 1.10.09 to 30.10.09.
    Now we create another condition record for the same condition type with a new price of USD 50 with same valid date from 1.10.09 to 30.10.09..
    So now the systems delete the old condition reocord of USD 100.This is standard sap.
    Now I want to know is there any way of tracking the deleted condition records like  the ones the system has deleted. If there is no standard report and if we have to develop a Z report, then how to develop that since the tables do not contain the old conditon records.
    regards
    sachin

    Hi,
    Yes, from the condition table that you are going to maintain the condition records (check the condition table assigned to the access sequence, from the condition type), we will get all the condition records maitained for specific combination/material
    Now go to se16 and enter the condition table name and give the proper selection criteria then you will get all the condition record numbers maintained to your selection with validity dates. then you can go to KONP and pass the condition record and you can get the condition values for that particular combination with proper validity dates.
    (Actually from VK13/VK12 based on validity date that we have mentioned in the selection screen will display the condition record valid on that paricular date, from the system those condition records will not be deleted at all)
    OR
    There are two possible methods of displaying change documents:
    Choose Environment -> Changes -> For condition record.
    Change data for the selected condition record(s) will be displayed.
    Choose Environment -> Changes -> Report.
    A selection screen will appear where you can choose multiple criteria for displaying change documents. The result of the selection report is displayed.
    Regards,
    Satya

  • Populating the bapi in retreiving the pricing condition

    Hi guys,
    given the ff data, how am i going to populate bapi_salesorder_simulate to retrieve the pricing condition?
    Condition      Table     Field                    SAP Field
    ABCD     907     Sales Org                   LIKP-VKORG
    ABCD     907     Customer                   LIKP-KUNNR         ABCD     907     Material                   LIPS-MATNR    XYZW     855     Sales Org                   LIKP-VKORG
    XYZW     855     Price Group     KNVV-KONDA
    XYZW     855     Material Group     MARA-MATKL
    XYZW     855     Duty Band                    MVKE-MVGR3
    Thanks a lot!
    Regards,
    Mark

    Hi Preet,
    I am sorry that we are back to square one. I checked OSS and two OSS notes specifically mention that you cannot do anything with condition records if you are in a version lower than 4.7.
    That leaves us with the option that I mentioned in your earlier posting which is to make config changes, and then write a small program to do repricing. That way all the sales orders will be repriced and based on the new configuration, the condition should disappear.
    You can give points by clicking the yellow star sign at the header of a post. You can give one 10 points for the post solving your issue, two 6 points for very helpful answers and unlimited 2 points for helpful answers.
    Regards,
    Srinivas
    Sorry forgot to mention the OSS notes. They are 593246 and 597970.
    Message was edited by: Srinivas Adavi

  • To make the Pricing Condition types inactive in Pricing Procedure

    Hi Experts,
    I am facing a senario where, in a sales order, pricing procedure, if one of the pricing condition type does not exist, then two other condition types (even though they are determined by condition records), should be either made inactive or should not appear in the pricing procedure.
    Example: If I have 3 condition types in Pricing Proc say
    YYY1, YYY2, YYY3, then the scenarios are
    a. If one of the condition types YYY1 is not determined, then, YYY2 and YYY3 should not be either determined in the sales order or should be made inactive. This same logic applies to both YYY2 and YYY3.
    b. If all three condition types are determined in Pricing Proc of the sales order, then, the price should be considered.
    If it was just YYY1 then, I could have done it in VOFM by writing a routine and assigning it to YYY2 and YYY3 in pricing proc. However, the scenario is to check the other condition types as well and make YYY1 inactive if any of the other condition type does not exist. Both condition types are determined after YYY1 which is another difficulty.
    I tried creating a dummy condition type  and assigning it to Pricing Proc (at the end of Pricing Proc). For this dummy condition I put in a pricing requirement which checks for all three condition types and if one does not exist, then it make other conitions inactive.
    However, this does not work in VA02 and VA03 as XKOMV is either not getting filled up or even if is getting filled, it is not having the condition type. It some times has condition records, and sometimes not... (not very sure why)
    So, I was thinking of using user exit for the same. However, I was unable to find a suitable user exit for the same where KONV table can be read or XKOMV can be filled.
    Can you please suggest if any user exit can be used for this or if we can implement it in a different way?
    Regards,
    Mukund S

    Hi,
    I think you can use condition exclusion functionality to select best pricing condition from a set of conditions in pricing.  You can compare conditions in many ways.
    I believe you can plot a solution with little research.  The below link is for your reference.
    [http://help.sap.com/saphelp_40b/helpdata/fr/93/743483546011d1a7020000e829fd11/content.htm]

  • Pricing condition record text maintenance in multiple language

    Hi friends,
    While maintaining condition record by VK31 transaction, there are options for multiple language selection. but after saving it appears only in English. Please let me know whether we can maintain text in multiple languages for a pricing condition record?
    Regards
    Manish
    9741178072

    HI Manish,
    You need to maintain the translations for the condition types in SPRO.
    The path is SPRO - Sales and Distribution - Basic Functions - Pricing - Pricing condition types - Maintain Condition types.
    Then selecting the particular condition type GOTO- Translations, you need to maintain the translation in the particular language as desired.
    Thanks
    Ani

  • Archive pricing condition record

    Hello everybody,
    I want to ask about how to archive MM pricing condition record?
    I tried with SARA, archive object CND_RECORD or program /SAPCND/CND_RECORD_WRITE but it doesnt work.
    Kindly advise,
    Thanks,
    HN

    Hello Jurgen,
    We're about to archive tens of millions of SD_COND entries - mainly to reduce the number of change records we have in table CDHDR, of type COND_A (COND_A is the change document object for SD Pricing conditions and we have over 100 million of them! And is now causing a few performance issues).
    Understandably this is going to take a long time to process so I was intrigued to read your post that no conditions should be maintained whilst the archiving programs run...
    I've tried searching OSS but haven't been able to locate any information about this.
    Could it be that you were referring to the old archive programs and not the newer ones such as those described in:
    Note 838768 - New archiving programs for condition records
    Any help you could offer would be much appreciated!

  • Pricing Condition Records initial upload - COND_A

    Hi,
    I have configured outbound COND_A pricing condition Idocs for Change documents. Whenever the pricing condition is changed IDoc will be generated.
    Now my requirement is how can I do the initial upload of existing Pricing Condition records to legacy system? I mean how can I generate Outbound IDocs for existing pricing condition records to do initial upload.
    Thanks in advance for your help.
    Rgds,
    AK

    HI,
    way1:
    if you are using Sretail (ARTMAS) then you can use BD10 tcode with the flag "send all data".
    In that case the COND_A for every ARTMAS is send.
    way2:
    1. if you want to send a all condition, then go to MEK3 choose your conditiont ype and push "condition Info".
    2. Make your selection and go ahead with F8
    3. Push "Send condition"

Maybe you are looking for