Pricing

Lessons in this topic

• Pricing Routines, Requirements, and Alternative Calculation TypesHow requirement routines, alternative calculation type routines, and alternative base value routines extend standard condition technique logic to handle complex business rules that condition records alone cannot express.
• Understanding SAP SD Pricing FundamentalsAn introduction to why pricing exists in SAP SD, what business problems it solves, and how price determination fits into the order-to-cash cycle.
• Enterprise Pricing Architecture: Governance, Extensibility, and S/4HANA Migration StrategyArchitect-level guidance on designing scalable pricing architecture for multi-country templates, governing condition master data and configuration changes, choosing extensibility approaches per deployment model, and planning ECC-to-S/4HANA pricing migration.
• Configuring the Pricing Procedure and Condition TechniqueA deeper look at how pricing procedures are structured, how the condition technique determines which conditions apply, and how consultants configure and troubleshoot this at the intermediate level.
• Condition Record Maintenance, Scales, and Validity ManagementHow condition records are created, scaled, and time-bounded, and how these design choices affect pricing accuracy, maintenance effort, and downstream document behavior.

Interview questions covered

• A customer reports that a manually entered discount condition record disappeared from a recurring sales order template after mass condition record updates. How would you troubleshoot this using condition record maintenance?
• When configuring VKOA account determination for a billing document that includes both a tax condition (MWST) and a freight condition (KF00), how do you ensure each posts to its correct G/L account via distinct account keys?
• During a post-merger integration, two legacy access sequences for the same condition type PR00 need to be consolidated without disrupting thousands of existing condition records. What approach would you take to redesign the access sequence safely?
• A customer-specific discount condition record exists in VK13 but is not being picked up in the sales order pricing screen despite matching all key fields. Outline your systematic troubleshooting approach using the condition technique.
• In a complex billing scenario using graduated (interval) scales on a pricing condition, how does the scale basis (quantity vs. value) affect the final calculated amount, and what implementation pitfalls should be anticipated?
• You need to design condition tables for a complex pricing scenario where discounts vary by customer group, material group, and sales organization simultaneously, but performance and maintainability are both concerns. What design approach would you take?
• Freight condition records for a promotional shipping surcharge are maintained at the shipping point level, but the shipping point determination logic assigns different shipping points to deliveries from the same sales order depending on plant and loading group. As a result, freight amounts posted to FI-AR are inconsistent across split deliveries for the same customer order. How do condition record master data attributes interact with shipping point determination to cause this, and how would you resolve it?
• A customer complains that freight charges and tax are calculated inconsistently across delivery plants for the same material and destination. What areas would you investigate in shipping and pricing configuration to diagnose this?
• A global customer needs volume-based pricing where the discount percentage increases as cumulative order quantity across multiple orders in a month grows. How would you design this using scales, and what limitation must you flag to the business?
• What is the purpose of the 'Expected Price' field on a sales order item, and how does it differ from the actual pricing determined by the pricing procedure?
• A shipping condition (e.g., route or shipping point) is influencing freight pricing in the sales order, but freight charges posted to FI-AR appear inconsistent across deliveries from different shipping points. How do shipping configuration and the pricing procedure integrate, and where would you investigate?
• A retailer sells the same material through both wholesale and e-commerce channels, and finance requires revenue to post to different G/L accounts by channel while using a single material master. How would you design revenue account determination to achieve this without duplicating materials?
• When configuring scale-based pricing conditions that feed into VKOA account determination, what design considerations ensure the correct revenue account is hit as quantities cross scale thresholds?
• Free-of-charge deliveries are posting to revenue accounts unexpectedly instead of being fully cost-absorbed. As the architect, how do you diagnose and correct the sales document type and pricing configuration?
• A pricing procedure includes a discount condition type with an access sequence containing three access steps, each flagged as 'Exclusive'. Business users report that for a key account, the system picks a less specific condition record from a later access step instead of a highly specific customer/material record that exists in an earlier step, resulting in an incorrect discount amount flowing into the billing document and posting to FI-AR. As the architect, how would you diagnose this?
• When configuring condition exclusion groups in pricing, how can this configuration inadvertently affect revenue account determination (VKOA) results downstream?
• Freight charges determined via an access sequence keyed on shipping point and route are posting to the wrong G/L account during billing. How does the access sequence design connect to this downstream FI-AR posting issue?
• After a global rollout, one region reports that billing documents fail pricing with 'no condition record found' while another region works fine using the same pricing procedure. How would you diagnose whether the condition table structure is the root cause?
• What is the condition technique in SAP SD pricing, and what are its core building blocks?
• A client wants a special freight surcharge condition to never combine with a promotional discount condition on the same order line. How would you configure this, and what shipping-related impact should you check?

Related topics