Settlement Management
SD / O2Cintermediate

SD Settlement Management Part 2: Configuring Condition Contract Types, Conditions and Business Volume

Key takeaway

Configure settlement management: condition contract types, condition types for rebates and accruals, condition tables and eligibility, business volume selection, settlement calendars and settlement types, and document flow to billing and FI.

Explanation

📌 KEY POINTS
✅ Condition contract type controls partners, conditions, business volume selection, settlement settings and document types.

✅ Rebate and accrual condition types with their own pricing procedure calculate settlement and accrual amounts.

✅ Business volume selection defines which billing data counts (customers, materials, dates, eligibility).

✅ Settlement calendar and settlement types (partial, final, delta) drive when and how settlement happens.

⚠️ Wrong eligibility settings include or exclude sales silently — test with real data.

━━━━━━━━━━━━━━━━━━━━
▶ WHERE WE ARE

Part 1 introduced condition contracts. Now configuration.

━━━━━━━━━━━━━━━━━━━━
▶ 1. CONTRACT TYPE

  • Settlement party (customer), eligible partners (e.g. hierarchy).
  • Allowed condition types, settlement calendar defaults.

━━━━━━━━━━━━━━━━━━━━
▶ 2. CONDITIONS

  • Rebate condition type (percentage/scales).
  • Accrual condition type.
  • Condition tables/fields for eligibility (material group, sales org…).

━━━━━━━━━━━━━━━━━━━━
▶ 3. BUSINESS VOLUME

  • Selection from billing (sales volume) with fields matching conditions.
  • Performance options (stored vs calculated).

━━━━━━━━━━━━━━━━━━━━
▶ 4. SETTLEMENT

  • Settlement calendar dates; settlement types partial/final/delta.
  • Settlement document type → customer credit memo.

━━━━━━━━━━━━━━━━━━━━
▶ 5. INTEGRATION

  • Accruals with billing or periodic.
  • FI postings via account determination for settlement documents.

━━━━━━━━━━━━━━━━━━━━
▶ STEP BY STEP

  1. Review standard contract types and copy.
  2. Define conditions and eligibility.
  3. Configure business volume selection.
  4. Test a full cycle.

✅ CHECKPOINT: business volume matches the eligible billing documents and settlements post correctly.

Code example

ABAP Code
===== STEP 1: configuration areas (SPRO > Logistics - General > Settlement Management) =====Condition contract types | condition types (rebate, accrual) | condition tables and eligibilityBusiness volume selection | settlement calendar | settlement types | settlement document types ===== STEP 2: example contract =====Type: customer rebate | eligible: customer hierarchy node | condition: 2% on material group FG, scale by volumeCalendar: quarterly partial, yearly final | accrual: 2% with billing

Real project scenario

A distributor migrated rebates to condition contracts but business volume was consistently too high: eligibility used the sold-to, while contracts were agreed per payer group, so volumes of non-contract ship-tos were included. Adjusting eligibility to the customer hierarchy node and retesting with real invoices aligned volumes with the contracts.

Common mistakes

  • Wrong eligibility fields.
  • Missing accrual conditions.
  • No settlement calendar.
  • Untested business volume selection.
  • Copying classic rebate settings.

Best practices

  • Design eligibility with sales finance.
  • Test business volume with real data.
  • Configure accruals.
  • Use calendars for regular settlements.
  • Document contract types.

Interview angle

Questions: "How do you configure condition contracts?", "What determines business volume?", "What settlement types exist?"
Strong answer: contract types, rebate/accrual conditions, eligibility and business volume selection, settlement calendar with partial/final/delta, settlement document types and FI integration.

Practice this lesson

Quick check

1. Business volume in a condition contract includes sales to ship-tos not covered by the agreement. What should be checked?

2. Which settings define when a condition contract is settled?

3. A common intermediate-level question is how a rebate/settlement amount actually gets from a billing document into an accrual posting, and what configuration links them. In the Settlement Management context, which answer shows the strongest practical judgment?

Interview questions

1. Describe the end-to-end settlement management process for a customer rebate agreement from accrual creation during billing through final settlement, and identify where billing configuration decisions impact the accuracy of the settlement.

Answer it in your own words first, then compare.

2. A customer's orders are fulfilled from two shipping points feeding into a single condition contract's business volume, but finance notices the settlement run is double-counting volume for deliveries split across both shipping points. As the architect, how would you diagnose and correct the business volume selection design?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.

More lessons in this topic

Interview questions on this topic

Related SAP topics