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

Similar Messages

  • Item level pricing condition record is not getting recognized

    Hi,
    In our scenario we have to maintain the additional charges based on Plant. For this purpose I have created the condition table 900 which contains the following fields
    Sales Org/Dist Chal/Divi./Plant
    I have maintained the condition record for the table, Which has been downloaded to CRM successfully.
    When I create the order in CRM price of the product is getting recognized where as additional charges condition records are not getting recognized.
    When I check the Access I found that header level data .i.e. sales org/dist chal / divion has been recognized and plant has not been recognized that values are like this 00000000000000000000000000
    I have checked the plant it has been downloaded successfully to CRM
    So, can anybody help me out?
    Thanks

    Hi,
    Check in the  access sequnce exclusive indicator activation, it might be selected to the previous Condition Tables, if it is  selected than system will not check  further available/maintained  condition reocrds.
    Regards
    Naren..

  • 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.

  • 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 record, calculation type F volume, scale basis E net weig

    HI SAP Gurus,
    I have a question on pricing condition records.
    I have a requirement that needs to populate discount based on total net weight on the PO.  For example, if total net weight is greater than 1000 LB, it should give 10 cents discount per GAL.  The base UOM of the material is EA, GAL is an alternative UOM and Order Pricing Unit.  I can make the pricing condition works if the discount is per LB.  However, it doesn't work for discount given per GAL.  The calculation type is F volume and sacle basis is E net weight.  Pls advise what I need to do to make it work.  Thank you so much!

    closed

  • Deletion of bulk pricing condition records

    Hello thr,
    I have thousands of pricing condition records to be deleted. I use condition type ZP01 in VK12 and select the key combination customer/material and then enter the details and then mark the condition record for deletion. To delete the next condition record, I need to go back and do the entire process again. Could someone please let me know if there is a txn that can help me do this in one step.
    Thanks very much for your help.

    Hi Swetha,
    If you want to delete all conditions for ZP01 condition type, you need to create a LSMW batch input from LSMW t-code. you can check and try followings:
    [https://wiki.sdn.sap.com/wiki/display/ABAP/LSMW%20steps%20-Batch%20Input%20Recording]
    [http://www.scmexpertonline.com/downloads/SCM_LSMW_StepsOnWeb.doc]
    You should go to in LSMW t-code, a recording should be created for one record from VK12 t-code and it can be run for all records like same from SM35 t-code.
    Please follow the links above for VK12 condition deletion.
    I hope these will meet your requirement fully.
    Regards,

  • 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

  • Coprying rule-Pricing Condition records

    Hi,
    When copying the condition records, it gave the message "*Copying is incomplete because no rules have been defined."Can anybody pls. guide as to how to define copying rule for pricing condition.
    Regards

    Prerequisites for Copying
    The following general prerequisites apply to copying condition records:
    If the condition tables differ between the source and target condition records, then:
    Only one field may differ between the two condition tables
    The condition tables must contain the same number of fields
    If the condition types differ between the source and target condition records, then each condition type must have the same calculation rule, scale type, condition class, and plus/minus indicator.
    Copying Rules
    Copying rules determine which condition types and condition tables you can use for copying between source and target condition records. The rules are defined in Customizing for Sales and must meet the prerequisites listed above. The standard R/3 System contains standard copying rules. If required, your system administrator can modify the standard copying rules or add new ones to meet your requirements. During processing, you can select from alternative copying rules, depending on what you are trying to copy.
    Examples of Different Copying Scenarios
    The following three scenarios describe how you can copy condition records.
    Scenario 1: Same condition types/same condition tables
    You offer a special discount to a particular price group (a group of customers defined in the customer master record). You want to make this discount available to other price groups by copying pricing details from the existing record. In this type of copying, the condition types (K020) and the condition tables (table 20) are identical for both source and target condition records. The only thing that varies in this case is the value of one of the key fields (the Price group field).
    Scenario 2: Same condition types/different condition tables
    The access sequences for a particular condition type can be defined in Customizing for Sales so that it accesses more than one condition table. This means condition records with the same condition type can have different keys. You can also copy condition records where the condition type is the same but the condition tables are different. Say you offer a material-specific discount to a particular price group (condition type K032, condition table 32). You can copy this material discount and create a new condition record for a specific customer (condition type K032, condition table 5).
    Scenario 3: Different condition types/different condition tables
    You can also copy condition records even when both condition types and condition tables are different. Say you offer a special discount to a particular price group (condition type K020, condition table 20) as you did in the first scenario. Here, however, you want to copy this condition record not to another price group but to a new customer-specific discount (condition type K007, condition table 7). In this case, both condition types and condition tables are different.
    Copying Process
    You can call up the copy function from the Edit menu in any of the following condition record screens:
    Creating
    Creating with reference
    Changing
    Overview
    There are several typical scenarios for using the copying function. You may want to copy an existing condition record into a number of new condition records. In this case, you use the change condition record function. Alternatively, you may want to create a new condition record and copy it to other records all in one step. In this case, you use the create condition record function. In both cases, you can change the copied data before you save the new condition records.
    Note:
    If the existing rules not suited to ur requirment , u have to contact Abapers to write the routines for ur requirement.
    Hope it is useful
    REWARD POINTS IF USEFUL...

  • 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.

  • 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.

  • 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

  • New Condition table / access not getting picked in purchase order.

    I have created a new condition table for the tax to be calculated for Site / Material combination. The access sequence is also crated.
    When I created the purchase order the condition / tax is not getting picked. When I checked in the analysis, I found that the error was Access not made (initalize field) for the site.  The material is being picked up.
    Please note that the site is getting picked from KOMK table ( I think it is a header table), while the site is actually there in the line item level in the po.
    Request your help at the earliest.
    Regards,
    Veena.

    TCODE OBQ2
    Select the tax access sequence. Click on accesses. Tick the right combination required site / article . then click on the fields tab. This will take you to the next screen. There click on the field for which you want to change the selection table and then click on field catalog at the bottom of the screen.
    This will take you to the field catalog screen. there select the table and field and then save.
    With this procedure you can select the required field into KOMK OR KOMP.
    Regards,
    Veena.

  • 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

  • Is there a  BAPI to create IS-Oil (formula) MM Pricing condition records

    Hi,
    Is there a standard BAPI to create IS-Oil (formula) MM Pricing condition records, which would include the maintaining of the formula?
    Regards
    Kasi

    no BAPI exists

Maybe you are looking for

  • How can I transfer PDF files from my Apple to my iPad?

    I can transfer "Word" documents from my Apple to my iPad by adding, within iTunes, the required files to the App. Pages and then sync. I can also add PDF files to my Pages App in iTunes using the same method, BUT I can't open them in Pages - only the

  • Message Splitting with out BPM

    Hi,     Is there anyway to split the message into different messages suppouse M1,M2,M3. And I want to route these messages i.e. M1, M2, M3 dynamically to receivers using enhanced receiver determination. i.e. M1 is to route R1,R2,R3. M2 needs to route

  • TCS2: linked project FM9 & RH8, impossible to update new FM parag

    In a linked project FM9 and RH8, everything works fine except the following update: If I add a new paragraph label in the FM9 document and save it; then if I run the overall update from RH8 everything seems to work fine, but when I try to edit the st

  • When I select "get media" nothing happens and the photo downloader does not respond.

    I am unable to download my photos to Elements 10.  The program recognizes my Canon camera and he number of photos on its card.  But when I tap "get media" nothing happens and I then cannot even cancel or close the photo downloader page, which Task Ma

  • PHP Help with inherited database site

    Hope someone can help with this, although I might be a bit vague. (But will be happy to post any code that might help.) Basically I do a few sites for a company, and everything is coming together nicely moving everything to a new reseller hosting acc