Purpose
You'll be able to easliy find out the answer/solution by yourself for the most frequently asked questions in SD pricing area on this page.
For an easier search, you can use Ctrl + F to find a specific error message, for example.
Overview
Collective FAQ page contains most useful SAP Notes/KBAs within SD pricing functionality.Provide quick path to the solution for the questions you may have about pricing.
The content is divided by topics of Pricing determination, Pricing calculation, Group condition/Header condition, Pricing copy, Rounding issue, Customizing, Condition update,Condition exclusion, Authorization, Pricing print out, Performance & Data inconsistency.
Pricing determination | |
|---|---|
| Questions you may have | SAP Notes/KBAs that you should check |
Have you got error "VE 108 Condition record exists, but has not been set" or "VE 008 Condition record exists (removed manually)" for pricing determination?
Are you using KOMP field for preliminary step of requirement? |
859876 - Condition is missing: Message VE 108 or VE 008 27636 - Message: Condition exists (removed manually)
1460297 - Message VE108 in pricing analysis for a sales document
130416 - Requirements in the condition preliminary step
156230 - Requirements: What is permitted, what is not?
363212 - "Pricing analysis" mode of operation
|
Have you met the problem that certain condition types not get (re)determined as you've expected /get (re)determinedunexpectedly when you trigger pricing update or during pricing copy?
What does it mean for each pricing type? How can I define my own pricing type? |
24832 - Pricing rules/TVCPF
|
| Why does the pricing not redetermined/not redetermined as expected when I change certain field in sales document? How is the pricing redetermination being triggered? Which pricing type will be used? |
26115 - Conditions not updated during field change
748827 - New pricing and batch conversion factors
|
| Have you found the pricing result in individual billing creation (VF01) differ from the result in collective processing(VF04)? Have you implemented your own defined logic to fill in fields of TKOMP or TKOMK? Have you met unexpected pricing result when you go to header condition screen or save the billing document? Are you using Document Date (KOMK-AUDAT) or Sales Document Type (KOMK-AUART_SD) fields for pricing in billing document via userexit or formulas? | |
| Why couldn't order reason field (KOMK-AUGRU) get filled correctly for pricing determination in billing? |
1391347 - KOMK-AUGRU in the billing document
|
| Why does the system display incorrect validity periods when calling up the display of condition record with pricing analysis? What is the workaround? |
131396 - Display of validity date in pricing analysis
|
| How does the fast enty of condition rates work on sales order item overview screen? What kind of customizing settings are required? Why does the system issue error V2131 when I try to enter in condition rate via fast entry of condition rates? How would the system behave when I change condition currency or condition rate via fast entry of condition rates? What's the system reaction if I enter in Zero prices via fast entry of condition rates? |
208882 - Default condition sales overview: Mode of operation
|
| I want to use the field PSTYV (Sales Document Item Category) contained in KOMP as a key for a condition table, but I cannot find it from the field catalog in V/03. How can I use PSTYV in the condition access? | 531835 - Using field PSTYV in the condition access |
| During an intercompany process, it's expected that the pricing to be determined base on the (physical) ship-to party in theintercompany billing. While the system always uses the internal customer for pricing determination. How could I avoid it? | 337764 - Conditions from ship-to party: Intercompany |
| How is the Exchange rate for Condition Currency (field KOMV-KKURS) determined? |
1481238 - How are different exchange rates (Price, FI postings and Conditions) determined in billing documents
92613 - Determining price exchange rates for billing date
97487 - No exchange rate determination for copied conditions
|
| What is the system reponse for duplication conditions (KDUPL = 'A' in Customizing for the condition type) concerning the condition exclusion with KMANU that were entered manually |
514174 - Duplication conditions during manual entry
106714 - Manual condition types displayed twice in the header
|
| Condition records for pricing that are created or changed (in VK11 or VF12 for example) by another user or in another mode during a current transaction (for example order processing in VA01 or VA02) are ineffective in the current transaction. | 65845 - Newly created condition records not used |
Pricing calculation | |
| Questions you may have | SAP Notes/KBAs that you should check |
| What's the difference between (re)determination and (re)valuation in pricing? When would the condition be (re)valuated? In what kind of situation, the condition basis/scale base/condition value would NOT be (re)calculated? |
930870 - (Re)determination and (re)valuation of conditions
|
How is the condition record accessed?
What are the important process steps of the pricing result calculation?
| 912340 - Pricing: Condition access occurs in two steps 900089 - Pricing: Processing steps for FORM XKOMV_BEWERTEN |
| How is the condition base value being determined for a condition type based on different customizing and with/without basis formula? |
834174 - How are 'value-related' condition bases determined?
|
| How is the condition rate (KBETR) being determined for a subtotal line? |
791944 - How is the KBETR determined in a subtotal?
|
| How is the condition value (KWERT) being determined for a subtotal line? |
1007110 - How is the KWERT determined in a subtotal?
|
How is the cumulation of scale base values made for group conditions?
How is the process of quantity conversions in pricing?
| 854978 - Function of cumulated scale base values (in SD) |
| How is the pricing unit and unit of measure being determined for item net price? How is the currency and value get determined for item net price? |
201830 - Calculation of the net price of an item
|
| To avoid the deactivation of previous conditions, I've set up prices in the pricing procedure as discounts or deduction. How can I achieve that the units/condition rate determination of subtotal line after this discount/deduction condition could behave the same as subtotal after price condition? |
133313 - Subtotals after discounts/deductions
|
| Why are some value fields displayed differently on screen than they're in database/debugging mode? How does the calculation work with/without fixed point arithmetic? |
886532 - Pricing: Displaying and rounding numbers
|
| What's the reason for field overflow error V1802 in pricing? What's the restriction of field condition rate (KBETR) and condition value (KWERT)? |
1973529 - KWERT (condition value) and KBETR (amount) field length
|
| What can I do if I need to enter price with more decimal places in SD documents? |
38881 - Pricing with different decimal places
|
| How to make use of the "Subto" field in pricing procedure? Which condition/subtotal line is taken into account? What can I do if the number of subtotal fields in the KOMP (KZWI1 - KZWI6) is insufficient? | |
| Why does the condition value change when I access a billed sales order item in VA02? What's the calculation logic for condition type(fixed with condition control 'F') in a billed sales order item? | |
How do I create my own formula?
How do I solve the dump PERFORM_NOT_FOUND in the call of a VOFM object?
Why does the system require an SSCR registration key, even though the VOFM is within the 'customer namespace'?
In which namespace can I create customer-specific VOFM objects?
How can I transport VOFM objects via the Change and Transport System ?
Which maintenance responsibility has SAP for customer-specific VOFM objects?
|
327220 - VOFM function and its objects
393012 - VOFM: Syntax error for user-defined routines
931466 - TABLES statement SAPLV61A program.
381348 - Using user exit, customer exit, VOFM in SD
|
Group condition/Header condition | |
| Questions you may have | SAP Notes/KBAs that you should check |
| I have a condition type customized as "Item" condition. Despite of that, I am able to add this condition manually in the header. The error message "Condition is not allowed as header condition" is not issued. How to solve this issue? | 2071090 - Transfer of incorrect conditions possible after SAP Note 2041849 implemented |
| Why does the tax/other group condition value get changed when I go to header condition screen or after saving the document? What is rounding difference comparison (field KDIFF)? When would KDIFF get filled? What is condition type DIFF used for? How to customize it and how does it work? |
1472505 - Unexpected tax condition value in item of saved document or billing document.
1158475 - Rounding differences: Field KDIFF versus condition type DIFF
97722 - Rounding for different tax codes
|
| For group condition, which item should get rounding difference comparison being distributed? |
403254 - Distribution rule for rounding difference comparison
|
| How to avoid the rounding difference comparison for group conditions? |
39034 - Group condition routine
|
| Have you met the issue that the conditions which you think belong to one group are not grouped together although you use group condition routine? How does the system handle fields in structure GKOMV_KEY when using group condition routine? |
24944 - Group conditions
|
| What is "actual" header condition? How should "actual" header condition be customized? How does the "actual" header condition work in distributing the pricing, in pricing copy? What is "item totals"? Why for some "item totals", it's being displayed on header condition screen by splitting into two or more rows? |
876617 - FAQ: Header conditions/header condition screen
|
| How is the value being distributed into items for header condition with calculation type B Fixed amount? |
370487 - Info: Distributn header conditions w/ calculation type 'B'
|
Pricing copy | |
| Questions you may have | SAP Notes/KBAs that you should check |
| Why does the condition rate of condition with calculation type 'B'(fixed amount) change during pricing copy? |
485740 - Conditions with fixed amount in copy activities
|
| Why does the condition appear in the billing or copied sales document although the requirement in pricing procedure is not fulfilled? |
1620451 - Unexpected pricing condition in billing document or copied sales document.
|
| When I create SD document with reference, the condition value of tax jurisdiction tax conditions is not determined correctly in the newly created document. How can I avoid this problem? |
1043372 - Fixing tax conditions with tax jurisdiction
|
Rounding issue | |
| Questions you may have | SAP Notes/KBAs that you should check |
| According to the pricing procedure settings, surcharges and discounts are related to net value, rounding issue might occur when calculating net price. How to avoid such kind of rounding issue? |
80183 - Rounding
|
| Why does the value in billing differ from the value in sales order in some delivery-related billing process (partial delivery or batch split exist)? |
1466873 - Different condition value between sales document and billing document
|
| How to avoid rounding issue when a currency conversion is needed for condition value calculation? |
1656732 - Rounding in condition value when condition has different currency
|
| During quantity conversion, rounding errors may occur due to condition base only have 3 decimal places. How to make condition basis to be calculated with more accuracy? |
22963 - Rounding problems in condition basis
|
Customizing | |
| Questions you may have | SAP Notes/KBAs that you should check |
| Why should the change of pricing procedure in the production environment be avoided? What kind of steps do you need to perform when you need to change pricing procedures? |
388112 - Change of pricing procedures in the production system
|
| What should I consider if I want to change the condition category of a condition type in the production environment? | 76754 - Change condition category in productive system |
| Why are standard pricing customizing missing or customer-specific customizing change get missing after system upgrade? What's the meaning of "delivery class" of each table? What's the system behavior during installation, upgrade and language import & client copy for different "delivery class"? |
217012 - Missing pricing Customzing after upgrade
|
| What's the effect if you set calculation type "G" for a condition type? |
912145 - Pricing: Significance of calculation type "G"
|
| What are the effects of the 'Plus/minus' setting (field T685A-KNEGA) in the Customizing of a condition type? | 774424 - Plus/minus sign of condition rate & value (KNEGA & SHKZG) |
| How to customize interval scales? What are the constraints for interval scales? |
930537 - Interval scales: Functions and restrictions
|
Condition update | |
| Questions you may have | SAP Notes/KBAs that you should check |
| How does the condition update work in general? How would condition with condition update behave when setting reason for rejection? Or when copying conditions/billingdocuments? Or when subsequently changing the order quantity? What're the constraints for condition update? |
615370 - Condition update: Functions and restrictions
|
| What is S071 used for? How should it be customized? |
931467 - S071: Customizing and performance aspects
|
| For some case when using condition update, why are the cumulative values greater than the maximal values defined in the condition record? | 19402 - Condition update: Cumulative values too large |
| How does the condition update work in returns? | 41033 - Maximum Condition Accumulated value & returns |
Condition exclusion | |
| Questions you may have | SAP Notes/KBAs that you should check |
| What are the options to exclude conditions from pricing result? What is the meaning of inactive indicator (KINAK)? How to exclude condition via exclusion indicator (KZNEP)? How to customize exclusion group? How does the "last price" logic work? |
836243 - How condition exclusion works in R/3
67958 - Mode of operation of the condition exclusion
|
| How would the system behave when I use condition exclusion with group conditions? |
217009 - Condition exclusion for group conditions
|
Authorization | |
| Questions you may have | SAP Notes/KBAs that you should check |
| How can I hide certain condition types and subtotal lines from being processed or displayed in the condition screen? | |
Pricing print out | |
| Questions you may have | SAP Notes/KBAs that you should check |
| Have you got error V1 806 when you perform some further operations after you go to print preview of sales document? Are you using your own defined output program? |
312423 - Pricing: Termination V1 806 after print preview
|
Performance | |
| Questions you may have | SAP Notes/KBAs that you should check |
| You're facing poor performance in pricing due to the condition tables (for example: A001 - A999, B001 - B999, C001 - C999, KOT001 - KOT999). |
23877 - Performance: Buffering condition tables
886773 - FAQ: General condition technique (Question 4)
|
| You're facing poor performance in pricing due to SD_COND_ACCESS. | 1738398 - Performance improvement with prestep for accesses |
You're facing poor performance in pricing when you save the document, or when you activate the data in the header condition screen, or when you leave the header condition screen.
|
63070 - Group condition processing in sales order
|
Data inconsistency | |
| Questions you may have | SAP Notes/KBAs that you should check |
| You've found for some SD documents, some or all conditions are missing from the document items. When you display the pricing conditions and return to overview screen, a different item net value (or zero value) is displayed. How to check the inconsistency for pricing in sales documents? |
141121 - SD documents - Table KONV is inconsistent
|
Cumulated conditions | |
Questions you may have
|
SAP Notes/KBAs that you should check
|
How do cumulated conditions work?
| 844141 - FAQ: Cumulated conditions |
Dump / Update termination | |
Questions you may have
|
SAP Notes/KBAs that you should check
|
How to solve the runtime error SQL_ARRAY_INSERT_DUPREC?
|
154638 - SQL_ARRAY_INSERT_DUPREC,LV45UF0K, KONV_BEARBEITEN
208627 - SQL_ARRAY_INSERT_DUPRECLV60UF0K KONV_BEARBEITEN
407607 - SQL_ARRAY_INSERT_DUPREC inRV_INVOICE_POST
|
Fonte: https://wiki.scn.sap.com/wiki/display/SD/FAQ+for+SD+Pricing+SD-BF-PR
Nenhum comentário:
Postar um comentário