Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 5 of 5

Monitoring conversion and testing reference flows

9 min

Pre-sales documents matter because of what they turn into. Two things therefore need proving: that conversion works (the right data flows from quotation or contract into the order) and that the business can see how well it converts. This lesson covers both.

Monitoring quotation conversion

The quotation conversion rate is usually defined as the value (or number) of quotations converted into orders, divided by the value (or number) of quotations created in a period. SAP S/4HANA's embedded analytics cover quotation and contract conversion alongside incoming orders and sales volume; the exact app names vary by release, so search the launchpad for "quotation" in your system. Operationally, Manage Sales Quotations filtered by status and validity, the My Sales Overview card for open quotations, and VA25 (list of quotations) in SAP GUI show what is open, expiring or rejected.

MeasureDefinitionContoso June result
Quotations createdNet value of quotations with a creation date in the period$1,200,000
ConvertedNet value referenced by sales orders$540,000
RejectedNet value with a reason for rejection$300,000
OpenStill within validity, not converted or rejected$260,000
Expired, not closedValidity passed, no reason for rejection$100,000
Conversion rateConverted ÷ created45%

A worked quotation conversion summary. Figures are fictional.

The "expired, not closed" line is a data quality signal, not a sales result. Every dollar there should be either converted or rejected with a reason. A rising number means the sales team is not closing lost quotations, which flatters the open pipeline and distorts the conversion rate.

Batch follow-upLow value, plenty of time: include in the weekly review
Account manager focusHigh value, plenty of time: plan the next customer touchpoint
Quick closeLow value, expiring soon: call or let it lapse, then set a reason for rejection
EscalateHigh value, expiring soon: sales manager follow-up this week
Prioritizing open quotations by value and time to expiry.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-209

Testing reference document flows

A reference-flow test proves that a successor document copied the right things from its predecessor and updated the predecessor correctly. For Contoso, the core set is short.

#ScenarioExpected result
1Order with reference to a valid quotation, full quantityPrices, partners and terms equal the quotation; quotation item completed
2Order for part of the quoted quantityQuotation item partially referenced; remaining quantity open per completion rule
3Order with reference to an expired quotationConfigured warning or error appears; behavior matches the business decision
4Release order against a quantity contractContract price applied; released quantity increases; open quantity decreases
5Release order that would exceed a value contractConfigured message when the target value is exceeded
6Release order from a non-authorized ship-toRelease refused or warned per the contract's partner rules
7New delivery schedule on a scheduling agreementOld schedule replaced; delivery created from a due line
8Lost quotation closed with a reason for rejectionDisappears from open lists; counted as rejected in analytics

Reference-flow test scenarios.

  1. Expected valuesWrite the quoted or contract price, quantities and statuses you expect
  2. Create with referenceExecute the step, recording each document number
  3. Compare copied valuesSuccessor fields against the predecessor: price, quantity, partners, terms
  4. Check predecessor updateQuotation status, contract released quantity or schedule lines
  5. Capture document flowExpanded flow showing predecessor, successor and statuses
How to execute a reference-flow test.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-209

Defects that show up in reference flows

  • Quoted price replaced by the current list price because the pricing type re-determines all conditions.
  • Partners on the order differ from the quotation because partner determination re-ran instead of copying.
  • Quotation stays open after full conversion because the completion rule or quantity update is wrong.
  • Expired quotation converts silently when the business wanted a warning or a stop.
  • Release order does not reduce the contract balance because it was assigned at header level only.
  • Scheduling agreement deliveries miss a week after a schedule was replaced.

What would you do?

During regression testing after a support package, the quotation-to-order test passes: the order is created and the price matches. But the quotation still shows status "open" after full conversion. Grace wants to know whether this is worth a defect.

Key points
  • Conversion rate = converted ÷ created, by value or count, for a defined period.
  • Expired quotations without a reason for rejection are a data quality problem.
  • Reference-flow tests compare copied values and check the predecessor update.
  • Include partial conversion, expired validity, contract consumption, partner rules and schedule replacement.
  • Evidence: predecessor and successor side by side, plus the document flow with statuses.

Check your understanding · not graded

Lesson check

  1. 1. How is the quotation conversion rate usually calculated?

  2. 2. What does a growing "expired, not closed" value indicate?

  3. 3. In a reference-flow test, what must be checked besides the successor's values?

  4. 4. Which scenario tests contract partner rules?