Stock Transfer Process in SAP SD (Interview Perspective + Configurations)

Stock Transfer Process is one of the most important topics in SAP SD for Global Rollout Projects — especially when dealing with Intercompany or Intracompany stock movements between plants or countries.

It’s frequently asked in Order-to-Cash (OTC) interviews to check how well you understand logistics integration between SD, MM, and FI.

1. What is Stock Transfer Process in SAP SD?

Stock Transfer Process is the movement of materials from one plant (or storage location) to another, either within the same company code (Intra Company) or between two different company codes (Intercompany).

Types of Stock Transfers:

2. Stock Transfer Process Flow

a) Intra Company Stock Transfer (Plant to Plant)

Same Company Code
No Billing Involved
Material Movement only

Process Flow:

1. Stock Transfer Order (STO) – (ME21N)
2. Outbound Delivery – (VL10B / VL02N)
3. Goods Issue Posting – (VL02N)
4. Goods Receipt Posting – (MIGO)

Accounting Entries:

3. Intercompany Stock Transfer Process

Between plants of different company codes
Intercompany Billing
FI Invoices

Process Flow:

1. Stock Transfer Order (STO) – (ME21N)
2. Outbound Delivery – (VL10B / VL02N)
3. Goods Issue – (VL02N)
4. Intercompany Billing (VF01)

Configuration Steps

Pricing Procedure Example

4. Configuration Steps (Step-by-Step)

a) Define Document Types for STO

ME21N (Purchase Order)

• NB – Standard PO
• UB – Stock Transport Order (Intra Company)
• ZUB – Intercompany STO

b) Assign Delivery Type to STO

• Delivery Type: NL (Intra Company)
• Delivery Type: NLCC (Intercompany)

c) Define Billing Document Type

• Billing Type: IV (Intercompany Invoice)
• Copy Control: Delivery Invoice

d) Assign Customer to Supplying Plant

• Create Customer Master using Account Group CPD (One-Time Customer)
• Use XD01 / BP to create the customer
• Link Customer to Supplying Plant via Assign Sales Area to Plant

Interview Questions

5. Common Issues in Global Rollouts

EDI Integration for Stock Transfer

• ORDERS Stock Transfer Order
• DESADV Advanced Shipping Notification
• INVOIC Intercompany Invoice

6. Configuration Objects Required

Special Scenarios

Final Summary

The post Stock Transfer Process in SAP SD: Complete Guide with Configurations & Interview Tips appeared first on HowtolearnSAP.

The Third-Party Process is one of the key business processes in SAP Sales and Distribution (SD), especially for industries where companies do not manufacture or stock products but directly procure goods from external vendors and ship them to customers.

It’s a hot topic in interviews — especially for any Global Rollout projects — because of its integration with MM, FI, and EDI.

What is the Third-Party Process?

In this process:

• The company does not deliver goods directly to the customer.
• Instead, the company creates a purchase order to procure goods from an external vendor.
• The vendor delivers the goods directly to the customer.
• The vendor sends the invoice to the company.
• The company bills the customer accordingly.

Key Process Flow

1. Sales Order Creation (VA01):
   • Sales order with Item Category TAS (Third-Party Item).
   • Schedule line category CS triggers PR creation automatically.
2. Purchase Requisition (PR):
   • Automatically created from the sales order.
3. Convert PR to Purchase Order (PO) (ME21N):
   • PO is sent to the vendor.
4. Vendor Delivers Goods to Customer (No Goods Receipt in SAP).
5. Vendor Invoice Receipt (MIRO):
   • Vendor sends an invoice to the company.
6. Customer Billing (VF01):
   • Company bills the customer based on the vendor invoice.

2. Master Data Pre-requisites

3. Configuration Steps

Step-by-Step Configuration

a) Define Item Category

TAS – Standard Third-Party

• Business Data: Billing Relevance F (Order-Related Billing)
• Schedule Line Allowed: CS

b) Schedule Line Category

CS – Third-Party

• Order Type: NB (Purchase Requisition)
• Purchase Requisition Type: Immediately
• Goods Movement: Blank (No Delivery)
• Account Assignment: X (Third-Party Sales)

c) Assign Item Category to Sales Document Type

• Sales Order Type: OR
• Item Category Group: BANS
• Automatic Item Category: TAS

d) Copy Control

• OR F2 (Order to Invoice)
• Billing Relevance: F

4. Pricing Integration

In third-party sales:

• The customer price is determined in the Sales Order.
• The vendor price is determined via Purchase Info Record.

Typical Pricing Procedure in Third-Party:

5. Accounting Entries

6. Special Scenarios

7. EDI Integration for Third-Party Process (ABC Company Perspective)

Typical EDI Flow:

• ORDERS Purchase Order to Vendor
• ORDRSP Purchase Order Acknowledgment
• DESADV Advanced Shipping Notification
• INVOIC Vendor Invoice

Common Interview Questions

Gaps/Challenges in Global Rollouts

Final Summary

• The third-Party Process is Order-Related Billing.
• It integrates with SD, MM, FI, and EDI.
• Use TAS with CS schedule lines.
• The most critical part of Global Rollouts.
• Focus on EDI, Pricing, and Custom Developments during interviews.

The post Third-Party Process in SAP SD (Interview Perspective + Configuration) appeared first on HowtolearnSAP.

In SAP SD (Sales and Distribution), pricing errors can occur for various reasons, such as incorrect condition records, missing configurations, or master data issues. Here are some common pricing errors in SAP SD and their resolutions from an Order-to-Cash (OTC) perspective:

1. Pricing Procedure Not Determined

Error Message: Pricing procedure not determined (Pricing procedure missing)
Cause:

• Incorrect assignment of pricing procedure in OVKK (Sales Org, Distribution Channel, Division, Document Pricing Procedure, and Customer Pricing Procedure).
  Resolution:
• Check OVKK and ensure the correct Sales Area, Document Pricing Procedure, and Customer Pricing Procedure combination is assigned to the right pricing procedure.

2. Missing Condition Record (Condition Record Not Found)

Error Message: Pricing error: Mandatory condition record missing
Cause:

• Condition record is not maintained in VK11 for the relevant condition type (e.g., PR00, MWST).
  Resolution:
• Maintain the condition record in VK11 for the required key combination.
• Use VK13 to check if a record exists for the specified validity period and key combination.

3. Condition Exclusion Issues

Error Message: Condition type is ignored (condition not included in pricing)
Cause:

• The condition exclusion group is activated, preventing multiple discounts from being applied.
• The condition type is manually excluded.
  Resolution:
• Check condition exclusion settings in V/06 and OV31 (Condition Exclusion Groups).
• If necessary, adjust the exclusion group in the pricing procedure.

4. Pricing Conditions Are Not Calculated Correctly

Error Message: Incorrect price calculation
Cause:

• Incorrect formula assigned in the pricing procedure step (V/08).
• The incorrect condition type calculation rule (V/06).
  Resolution:
• Check pricing procedure settings in V/08 and ensure the correct formula and calculation type are assigned.
• Check condition type settings in V/06 to ensure it is marked as statistical or active as needed.

5. Currency Conversion Issues

Error Message: Pricing amount in foreign currency is incorrect
Cause:

• Exchange rate missing or incorrectly maintained in OB08.
  Resolution:
• Maintain the correct exchange rate in OB08 (Currency Exchange Rates).
• Ensure the correct exchange rate type is used in the sales order.

6. Incorrect Tax Calculation (MWST/VAT Missing or Wrong Rate)

Error Message: MWST condition record missing or incorrect tax rate applied
Cause:

• Tax classification missing in customer or material master.
• Tax condition record not maintained in VK11.
• Incorrect tax determination rules in OVK1.
  Resolution:
• Check tax classification in XD02/VD02 (Customer Master) and MM02 (Material Master).
• Maintain tax condition records in VK11 under the correct combination.
• Validate tax determination settings in OVK1.

7. Condition Type Not Found in Pricing Procedure

Error Message: Condition type is missing in pricing procedure
Cause:

• The required condition type is not assigned to the pricing procedure.
  Resolution:
• Go to V/08, and check if the condition type is properly added to the pricing procedure.

8. Manual Price Change Not Allowed

Error Message: Condition type cannot be changed manually
Cause:

• Condition type is not set for manual entry in V/06.
  Resolution:
• In V/06, check if the “Manual Entries” field is set to “C” (No changes possible). If needed, allow manual changes.

9. Pricing Date Issue

Error Message: Pricing date is incorrect or expired
Cause:

• The pricing date used in the sales order does not match the validity of the condition records.
  Resolution:
• Check the pricing date in the sales order header.
• Recalculate pricing using Update Pricing (Conditions → Update in the sales order).

10. Net Price is Zero

Error Message: Net price is zero in the order
Cause:

• Missing or incorrect pricing condition records.
• Statistical condition type is incorrectly applied.
  Resolution:
• Maintain the correct pricing condition records in VK11.
• Ensure the condition type is not marked as statistical in the pricing procedure (V/08).

11. Error in Condition Formula or Routine

Error Message: Incorrect value in a pricing condition
Cause:

• A custom pricing routine (Formula in VOFM) is assigned incorrectly.
  Resolution:
• Verify and debug the assigned routine in VOFM (Formulas for Condition Types).

12. Pricing Not Redetermined After Changes in Order

Error Message: Pricing does not update after quantity change
Cause:

• Incorrect pricing control settings for the condition type.
  Resolution:
• Check the pricing type in V/06 for the relevant condition type.
• Use pricing update function in the sales order to recalculate.

These are the most common pricing errors encountered in SAP SD and their respective OTC resolutions. Let me know if you need more details on any specific issue!

Here are additional standard pricing errors in SAP SD and their Order-to-Cash (OTC) solutions:

13. Pricing Condition Record Found but Not Applied

Error Message: Condition record exists but is not applied in sales order
Cause:

• The condition type is set to inactive due to the Requirement Routine in V/08.
• The condition validity period has expired.
• The condition type is Statistical and does not affect pricing.
  Resolution:
• Check V/08 and verify the requirement routine assigned to the condition type.
• Verify condition record validity in VK13.
• Ensure the condition type is not marked as statistical unless intended.

14. Condition Value Calculation Error

Error Message: Condition amount is incorrect (miscalculated discount/tax)
Cause:

• Incorrect calculation formula or percentage maintained in VK11.
• Wrong calculation type (Fixed Amount, Percentage, Quantity Dependent).
  Resolution:
• Check Calculation Type in V/06 and adjust if necessary.
• Review condition record in VK11 and maintain correct values.

15. Duplicate Condition Types in Pricing Procedure

Error Message: Pricing inconsistency due to duplicate condition types
Cause:

• Same condition type is maintained twice in the pricing procedure.
  Resolution:
• Check V/08 and remove duplicate condition types from the pricing procedure.

16. Condition Base Value Incorrect

Error Message: Pricing calculation incorrect due to wrong base value
Cause:

• Incorrect base value formula in V/08 (Pricing Procedure).
• Condition record maintained with an incorrect key.
  Resolution:
• Check Base Calculation Formula in VOFM (Base Calculation).
• Verify pricing condition record (VK13) for any incorrect entries.

17. Currency Rounding Issues

Error Message: Small rounding difference in pricing values
Cause:

• Rounding difference in currency conversion.
  Resolution:
• Adjust rounding rules in OB90 (Define Rounding Rule for Currency).
• Ensure correct decimal settings in the pricing procedure (V/08).

18. Inconsistent Pricing Between Sales Order and Invoice

Error Message: Price in invoice is different from the sales order
Cause:

• Pricing type set to ‘Carry out new pricing’ in invoice.
• Changes in master data after sales order creation.
  Resolution:
• Check Pricing Type in copy control settings (VTFL for billing).
• Use correct pricing update type (e.g., B – Copy Pricing Elements Unchanged).

19. Rebate Condition Not Applied in Order

Error Message: Rebate condition missing in sales order
Cause:

• Customer or material not relevant for rebate processing.
• Rebate condition type missing in pricing procedure.
  Resolution:
• Verify customer rebate indicator in customer master (XD02/VD02).
• Ensure the rebate condition type is included in the pricing procedure (V/08).

20. Pricing Error Due to Scale Pricing

Error Message: Incorrect pricing for scaled quantity
Cause:

• Incorrect scale maintained in condition record (VK11).
• Scale type mismatch (Quantity-based vs. Value-based).
  Resolution:
• Check scale type settings in V/06.
• Maintain correct scale values in VK11.

21. Incorrect Freight or Surcharge Calculation

Error Message: Freight charge or surcharge is not calculated correctly
Cause:

• Freight condition type not assigned in the pricing procedure.
• Condition record for freight is missing in VK11.
  Resolution:
• Add freight condition type (e.g., KF00) in pricing procedure (V/08).
• Maintain freight charges in VK11.

22. Tax Jurisdiction Missing (US Localization)

Error Message: Tax jurisdiction code missing for tax calculation
Cause:

• Missing tax jurisdiction in customer or material master.
• Tax jurisdiction code not determined.
  Resolution:
• Maintain tax jurisdiction in XD02/VD02 (Customer Master).
• Ensure OVK1 (Tax determination settings) is properly configured.

23. Error in Condition Index Table (Missing or Incorrect Entries)

Error Message: Condition record not found due to missing index
Cause:

• Index table not updated in pricing configuration.
  Resolution:
• Run RV_PRICE_UPDATE to update pricing indexes.
• Check pricing table consistency in SE16N (e.g., KONH, KONP).

24. Customer or Material-Specific Pricing Not Triggered

Error Message: Standard price applied instead of customer-specific price
Cause:

• Incorrect key combination used in VK11.
  Resolution:
• Maintain customer/material-specific pricing records in VK11.

25. Pricing Formula Not Executing as Expected

Error Message: Incorrect formula calculation in pricing
Cause:

• Incorrect custom formula assigned in pricing procedure.
  Resolution:
• Check VOFM (Formulas for Pricing Conditions) and debug the routine.

26. Incorrect Price Determination Due to Access Sequence Issues

Error Message: Condition record exists but is not picked in pricing
Cause:

• Incorrect Access Sequence assigned to the condition type.
• Wrong field priority in the Access Sequence (e.g., Material-Dependent Price is applied instead of Customer-Specific Price).
  Resolution:
• Check Access Sequence (V/07) and ensure that the correct priority is set for condition tables.
• Use Analysis in the sales order (Extras → Analysis in Pricing) to identify the missing condition record.
• Ensure that VK11 condition records are maintained for the correct access keys.

27. Customer-Specific Price Not Overriding Standard Price

Error Message: Standard price applied instead of customer-specific price
Cause:

• Condition type has the wrong exclusion rule in the pricing procedure.
• The customer-specific price is not given a higher priority.
  Resolution:
• Check Condition Exclusion (OV31) to ensure that the correct condition sequence is applied.
• In V/08, ensure the correct pricing step sequence is used so that customer pricing is applied before standard pricing.

28. Group Condition Not Applied Correctly (Scale-Based Pricing Issue)

Error Message: Price per unit incorrect for bulk orders
Cause:

• Group condition (e.g., discounts based on total quantity across items) is not applied correctly.
  Resolution:
• Check the Group Condition flag in V/06 for the relevant condition type.
• Ensure the correct condition type is assigned to the pricing procedure in V/08.

29. Intercompany Billing Price Incorrect

Error Message: Internal price between company codes is incorrect
Cause:

• The intercompany pricing condition (PI01, PI02, IV01, IV02, etc.) is not maintained correctly.
• Copy control settings between billing documents are incorrect.
  Resolution:
• Maintain intercompany pricing condition records in VK11 under the appropriate key.
• Check copy control settings in VTFL (Billing to Billing Copy Control) to ensure the correct pricing type is set.

30. Manual Condition Value Not Considered in Final Pricing

Error Message: Manually entered discount not reflected in net price
Cause:

• The manual condition type is marked as statistical.
• Condition update settings prevent manual changes from applying.
  Resolution:
• Check condition type settings in V/06 to ensure manual changes are allowed.
• In V/08, ensure the pricing procedure allows the manual condition to affect the net price.

31. Retroactive Pricing Not Working for Open Orders

Error Message: New price not applied to existing sales orders
Cause:

• The pricing type does not allow for re-determination of new prices in open orders.
  Resolution:
• Use transaction V_PRICING_UPDATE to update open orders with new pricing.
• Check the pricing type setting in copy control (VTAA, VTLA, VTFL).

32. Rebate Accruals Not Calculating Correctly

Error Message: Rebate amount in billing is incorrect
Cause:

• The rebate condition type (e.g., BO01, BO02) is missing in the pricing procedure.
• Rebate agreement validity does not match the billing document date.
  Resolution:
• Ensure rebate condition types are included in V/08 (Pricing Procedure).
• Check rebate agreements in VBO3 to verify the condition validity.

33. Condition Supplement Not Working in Pricing Calculation

Error Message: Supplementary condition (e.g., Freight, Additional Charge) not applied
Cause:

• The condition supplement assignment is missing for the main condition.
  Resolution:
• Check the Condition Supplement Assignment in V/06 to ensure the correct relationships are maintained.
• Maintain condition records for supplements in VK11.

34. Pricing Condition Records Overwritten by Incorrect Condition Index Update

Error Message: Unexpected price change after running a pricing update
Cause:

• The condition index was rebuilt incorrectly, causing missing or duplicate records.
  Resolution:
• Run RV_PRICE_UPDATE to rebuild the condition index.
• Check pricing condition table entries in SE16N (KONH, KONP, KONV) to validate the data.

35. Pricing Issue Due to Multi-Level BOM in Sales Order (Variant Configuration)

Error Message: Pricing incorrect for configurable materials (KMAT)
Cause:

• The pricing condition records are not maintained for sub-items.
  Resolution:
• Check pricing condition records in VK13 for both the header (KMAT) and components.
• Verify configuration pricing settings in CU50/CU51 (Configuration Profile).

36. Invoice Price Not Matching Goods Issue Cost (Cost-Based Pricing Error)

Error Message: Invoice price different from actual cost in FI/CO
Cause:

• Condition type for cost (VPRS) is missing or incorrectly maintained in pricing procedure.
• Price determination in the material master is inconsistent.
  Resolution:
• Ensure VPRS (Cost Condition) is included in pricing procedure (V/08).
• Check standard price (S) or moving average price (V) in MM03 (Accounting View).

37. Condition Record Not Found Due to Incorrect Sales Document Type Assignment

Error Message: Pricing error due to missing condition record
Cause:

• Sales document type does not match the condition type requirements.
  Resolution:
• Check Document Pricing Procedure in OVKK and ensure it aligns with the correct pricing procedure.

38. Surcharge/Discount Not Applied for Specific Customers or Materials

Error Message: Expected discount/surcharge missing
Cause:

• Customer/material-specific condition is not set up properly.
  Resolution:
• Maintain the condition record in VK11 with the correct key (e.g., Customer + Material).
• Verify pricing exclusion rules in OV31.

39. Credit Memo or Debit Memo Pricing Issue

Error Message: Incorrect pricing in credit memo/debit memo request
Cause:

• Copy control settings in billing are not configured to redetermine the price.
  Resolution:
• Check copy control settings in VTFF (Billing to Billing) and VTFA (Order to Billing).
• Adjust pricing type in the copy control settings to allow price redetermination.

40. Pricing Calculation Affected by Incomplete Condition Formula Execution

Error Message: Condition calculation formula does not execute
Cause:

• The condition formula is incorrect or inactive in the system.
  Resolution:
• Debug the assigned pricing routine in VOFM (Condition Formula Development).
• Ensure that correct formula numbers are assigned in the pricing procedure (V/08).

Summary:

These errors are more complex and often require debugging at the configuration, master data, or custom routine level. Resolving them usually involves:
Checking the pricing procedure (V/08)
Verifying access sequences and condition records (V/07, VK11, VK13)
Reviewing copy control settings (VTFL, VTFA, VTAA)
Debugging pricing routines in VOFM

Here are more standard pricing errors in SAP SD and their Order-to-Cash (OTC) resolutions:

41. Inconsistent Pricing Across Sales Order Items

Error Message: Different pricing applied to similar items in the sales order
Cause:

• The pricing procedure is using different access sequences for similar materials.
• Pricing scales are applied incorrectly.
  Resolution:
• Check condition records in VK13 and ensure uniform pricing maintenance.
• Verify the access sequence in V/07 to ensure all items use the same pricing condition.

42. Pricing Not Updated After Sales Order Change

Error Message: Pricing remains the same after modifying the sales order
Cause:

• Pricing type does not allow re-determination.
• The order is set to “Manual Pricing.”
  Resolution:
• Use Update Pricing (Condition Tab → Update Button) in the sales order.
• Verify pricing update settings in V/06 and change the pricing type if necessary.

43. Free Goods Condition Not Applied

Error Message: Free goods discount not applied in the sales order
Cause:

• The free goods determination procedure is not configured correctly.
• Condition type for free goods (e.g., R100) is missing from the pricing procedure.
  Resolution:
• Check VBN1 (Free Goods Determination Records) to ensure proper records exist.
• Verify the pricing procedure in V/08 includes the free goods condition type.

44. Incorrect Freight or Transportation Cost Calculation

Error Message: Freight condition (e.g., HD00) not included in net price
Cause:

• The condition type for freight is not added to the pricing procedure.
• Freight condition is marked as “Statistical.”
  Resolution:
• Include the Freight Condition (HD00, KF00, etc.) in V/08.
• Check freight condition records in VK13 to ensure they exist.

45. Error in Condition Index Usage (Pricing Performance Issue)

Error Message: Condition index lookup is slow or does not retrieve records
Cause:

• Condition index is not activated or is inconsistent.
• Large volumes of condition records are slowing down retrieval.
  Resolution:
• Activate the condition index in V/06 for relevant condition types.
• Run RV_PRICE_UPDATE to rebuild and optimize the condition index.

46. Surcharge Not Applied to Specific Customer Group

Error Message: Surcharge condition missing in pricing for customer group
Cause:

• Condition record is missing in VK11 for customer groups.
• Incorrect pricing condition sequence.
  Resolution:
• Maintain the surcharge condition record in VK11 using the correct key (e.g., Customer Group + Material).
• Check pricing procedure (V/08) for surcharge condition type inclusion.

47. Tax Condition (MWST/VAT) Missing in Sales Order

Error Message: Tax condition record not found
Cause:

• Tax classification is missing in customer or material master.
• Tax determination rules are not configured correctly.
  Resolution:
• Check tax classification in XD02/VD02 (Customer Master) and MM02 (Material Master).
• Maintain tax condition records in VK11 under the correct combination.
• Validate tax determination settings in OVK1.

48. Condition Record Exists but Not Considered in Pricing

Error Message: Condition type ignored in pricing calculation
Cause:

• Condition is set as inactive due to requirement routine in V/08.
• A different condition type has a higher priority.
  Resolution:
• Check Requirement Routine (VOFM → Requirements: Pricing) to see if the condition is excluded.
• Adjust pricing step sequence in V/08.

49. Condition Record Validity Expired in Billing Document

Error Message: Condition record not found in billing document but available in the order
Cause:

• Condition record validity does not cover the billing date.
• Incorrect pricing type setting in copy control.
  Resolution:
• Verify condition record validity in VK13 and extend if necessary.
• Check copy control settings (VTFL) and set correct pricing type.

50. Condition Exclusion Not Working Properly

Error Message: Expected discount/surcharge not excluded
Cause:

• Incorrect configuration in OV31 (Condition Exclusion Groups).
• Manual condition entry overrides the exclusion logic.
  Resolution:
• Check condition exclusion settings in OV31.
• Ensure condition exclusion logic is applied in the pricing procedure (V/08).

51. Credit/Debit Memo Incorrectly Copies Pricing from Invoice

Error Message: Credit memo pricing not match expected amount
Cause:

• Copy control settings in VTFF/VTFA do not allow price redetermination.
  Resolution:
• Change the Pricing Type in Copy Control (VTFA, VTFF) to allow price redetermination.

52. Discount Not Applied in Billing Document

Error Message: Expected discount missing in invoice
Cause:

• The discount condition type is missing in the pricing procedure for billing.
  Resolution:
• Ensure discount condition type exists in the billing pricing procedure in V/08.
• Check condition record in VK13 to ensure it is valid.

53. Statistical Condition Type Affects Net Price Calculation

Error Message: Condition marked as statistical but still impacts net price
Cause:

• The statistical flag is missing in V/08 for the condition type.
  Resolution:
• Mark the condition type as Statistical in V/08 if it should not affect net price.

54. Multiple Pricing Conditions Overlapping (Conflicting Discounts/Charges)

Error Message: Unexpected price due to multiple discounts/surcharges
Cause:

• More than one condition type applies, leading to conflicting pricing logic.
  Resolution:
• Use condition exclusion groups in OV31 to ensure correct priority.
• Review pricing step sequence in V/08 and adjust as needed.

55. Sales Order Net Price Lower Than Allowed Minimum Price

Error Message: Net price below allowed threshold
Cause:

• Minimum price condition (e.g., PMIN) is not enforced.
  Resolution:
• Maintain a minimum price condition record (PMIN) in VK11.
• Ensure the condition type is active in the pricing procedure (V/08).

56. Wrong Price Due to Incorrect Unit of Measure (UOM) Conversion

Error Message: Price calculated based on wrong UOM
Cause:

• Incorrect conversion factor between sales and base unit.
  Resolution:
• Check the UOM conversion in MM03 (Additional Data → Units of Measure).
• Maintain correct conversion in CUNI (Transaction for Unit Conversion).

57. Condition Record Deleted but Still Considered in Pricing

Error Message: Deleted condition still applied in pricing
Cause:

• The deleted condition record is still cached.
  Resolution:
• Run RV_PRICE_UPDATE to refresh condition indexes.
• Ensure condition records are deleted properly from VK12.

58. Price Redetermination Not Working in Return Orders

Error Message: Return order price is incorrect
Cause:

• Copy control settings in VTAA prevent new pricing.
  Resolution:
• Adjust pricing type in VTAA (Order to Order Copy Control) to allow price redetermination.

Final Thoughts

These pricing errors can occur due to configuration, master data, or business process issues. The best way to resolve pricing issues is to:
Use pricing analysis in the sales order (Extras → Analysis in Pricing)
Check pricing procedures (V/08), condition types (V/06), and access sequences (V/07)
Ensure condition records are correctly maintained in VK11

The post Common SAP SD Pricing Errors & How to Fix Them (Order-to-Cash Guide) appeared first on HowtolearnSAP.