$120 tested Claude codes · real before/after data · Full tier $15 one-timebuy --sheet=15 →
$Free 40-page Claude guide — setup, 120 prompt codes, MCP servers, AI agents. download --free →
clskills.sh — terminal v2.4 — 2,347 skills indexed● online
[CL]Skills_
SAPadvancedNew

SAP SD Pricing

Share

Configure SD pricing procedures, condition types, and access sequences

Works with OpenClaude

You are an SAP SD (Sales and Distribution) consultant specializing in pricing configuration. The user wants to configure SD pricing procedures, condition types, and access sequences to establish the complete pricing determination logic for sales orders.

What to check first

  • Run transaction SPRO and navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Procedures to see existing pricing procedure definitions
  • Verify your user has authorization object S_TABU_DIS with activity 03 (maintain) for table TKOMK
  • Check SAP version—pricing procedure configuration differs between ECC and S/4HANA in some condition type features

Steps

  1. In transaction IMG, navigate to Sales and Distribution > Basic Functions > Pricing > Pricing Control > Define and Assign Pricing Procedures
  2. Create or edit a pricing procedure in table TKOMK (Customizing: Pricing Procedures Header) using transaction V/08—enter procedure name (max 8 chars), document type eligibility (order, quotation, etc.), and calculation schema
  3. In transaction V/09, add condition types to your pricing procedure—for each row, specify step number, counter, condition type code (e.g., PR00 for price, RB00 for rebate), and required flag
  4. Define access sequences in transaction V/14—create sequence name, then populate access sequence table by specifying tables to query (like KNVV for customer-material info) with field selections and key fields (KUNNR, MATNR, etc.)
  5. Link condition types to access sequences in V/14—each condition type must have at least one access sequence that defines how SAP retrieves pricing data from master tables
  6. Configure calculation rules in transaction V/10 by entering condition type, formula (add/subtraction/percentage), rounding rules, and whether condition is editable in sales order
  7. Assign your pricing procedure to sales document types in V/07—ensure each order type (standard order, rush order, etc.) points to correct pricing procedure
  8. Test your configuration in VA01 (Create Order) with test material and customer; use pricing analysis button (icon or Shift+F5) to verify condition determination follows your access sequences

Code

" SAP SD Pricing Configuration via ABAP—Read and Validate Pricing Procedure
" This example reads condition types assigned to a pricing procedure and checks access sequences

REPORT zsd_pricing_config NO STANDARD PAGE HEADING.

DATA: lv_pricing_proc TYPE tkomk-komk,
      lt_komk TYPE TABLE OF tkomk,
      lt_komp TYPE TABLE OF komp,
      lt_koaw TYPE TABLE OF koaw,
      ls_komk TYPE tkomk,
      ls_komp TYPE komp,
      ls_koaw TYPE koaw,
      lv_output TYPE string.

PARAMETERS: p_proc TYPE tkomk-komk DEFAULT 'Z001'.

START-OF-SELECTION.

Note: this example was truncated in the source. See the GitHub repo for the latest full version.

Common Pitfalls

  • Treating this skill as a one-shot solution — most workflows need iteration and verification
  • Skipping the verification steps — you don't know it worked until you measure
  • Applying this skill without understanding the underlying problem — read the related docs first

When NOT to Use This Skill

  • When a simpler manual approach would take less than 10 minutes
  • On critical production systems without testing in staging first
  • When you don't have permission or authorization to make these changes

How to Verify It Worked

  • Run the verification steps documented above
  • Compare the output against your expected baseline
  • Check logs for any warnings or errors — silent failures are the worst kind

Production Considerations

  • Test in staging before deploying to production
  • Have a rollback plan — every change should be reversible
  • Monitor the affected systems for at least 24 hours after the change

Quick Info

CategorySAP
Difficultyadvanced
Version1.0.0
AuthorClaude Skills Hub
sapsdpricing

Install command:

curl -o ~/.claude/skills/sap-sd-pricing.md https://clskills.in/skills/sap/sap-sd-pricing.md

Related SAP Skills

Other Claude Code skills in the same category — free to download.

Want a SAP skill personalized to YOUR project?

This is a generic skill that works for everyone. Our AI can generate one tailored to your exact tech stack, naming conventions, folder structure, and coding patterns — with 3x more detail.