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

Lesson 4 of 5

Failure points and diagnosis

12 min

Cross-functional scenarios fail at the seams: where sales hands over to purchasing, where purchasing hands over to accounts payable, and where one company hands over to another. Each seam has a small number of typical failures. Knowing them shortens defect triage from days to minutes.

Sales seamItem category determination, internal price condition, delivering plant
Purchasing seamRequisition creation, source of supply, PO price and approval
Payables seamSupplier invoice posting, quantity and price variance, inbound intercompany invoice
Billing seamBilling relevance, intercompany billing, output and transmission
Finance seamAccount determination, tax, trading partner, period
Where third-party and intercompany scenarios break.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-301

Third-party failure points

SymptomLikely causeWhere to look
No purchase requisitionItem category not TAS (item category group or determination)Sales order item: item category and schedule line category
Requisition exists but no PONo source of supply, or buyer did not convertRequisition: assigned supplier, info record, buyer worklist
PO price differs from expected costInfo record or contract price wrongPO conditions vs purchasing info record
Customer never billedSupplier invoice not posted, or due list run without order-related documentsPO history: invoice receipt; billing due list selection
Customer billed wrong quantitySupplier invoiced a different quantity; billing follows itPO history vs customer invoice quantity

Third-party symptoms and causes.

Intercompany failure points

SymptomLikely causeWhere to look
Order cannot use plant 1810Plant not allowed for the sales areaSales area and plant assignment settings
Transfer price missing or zeroNo condition record for the internal priceSales order conditions: PI01 or PI02
IV invoice not createdNo internal customer number for the sales org, or order type not allowedIntercompany billing settings
IV invoice created, 1710 has no payableOutput or inbound processing failedOutput status of the IV invoice; inbound message monitoring
Tax wrong on IV invoiceTax determination for the internal customerTax classification of the internal customer and product
Balances differ at month endTiming: IV billed in a later period than goods issueBilling due list for IV; posting dates

Intercompany symptoms and causes.

Pricing, tax and timing: the big three

Pricing breaks when condition records are missing or expired: the internal price for intercompany, the purchasing info record for third-party. Missing prices often do not stop the process; they produce zero or wrong values that only finance notices. Tax breaks because these flows involve parties and locations that the normal sell-from-stock flow does not: an internal customer, a ship-from plant in another company, a supplier shipping to a customer's address. Cross-border variants add customs and different tax rules, and need tax specialist review. Timing breaks when the documents in a chain post in different periods: supplier invoices posted late delay customer billing; IV invoices billed late leave intercompany balances unequal at close.

AnnoyanceEasy to see, low impact: a requisition with the wrong buyer group
Hidden leakHard to see, low impact: small rounding differences between IV and supplier invoice
Visible stopperEasy to see, high impact: IV invoice not created, process stops
Silent killerHard to see, high impact: zero transfer price or missing trading partner; surfaces only at close
Classifying cross-functional failures. Test hardest where defects are silent and costly.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-301
  1. Did every expected document get created?Yes → check values · No → find the last document created; the failure is in the next step
  2. Are the prices on each document the expected ones?Yes → check tax · No → condition records or copy control
  3. Is tax determined as expected on each invoice?Yes → check postings · No → tax classification of partners and products
  4. Did each company post in the same period?Yes → check trading partner · No → billing timing or posting dates
A diagnostic path for any third-party or intercompany defect.
The Sign-Off Table · thesignofftable.com/academy/sap-sd-301

What would you do?

Contoso's intercompany test passes in QAS client 100: all documents exist and both companies post. Dan notices that the 1810 revenue on the IV invoice is $0 for one product. Priya's tester says "process completed, no errors". How should this be classified?

Key points
  • Failures cluster at the seams between sales, purchasing, payables, billing and finance.
  • Third-party: item category, source of supply, info record price, supplier invoice posting, due list selection.
  • Intercompany: plant assignment, internal price, internal customer number, output and inbound processing, tax, timing.
  • Pricing, tax and timing defects are often silent; check values, not just document existence.
  • Diagnose by finding the last document created and then checking prices, tax, periods and trading partner.

Check your understanding · not graded

Lesson check

  1. 1. The IV invoice exists but company code 1710 has no payable. Where should you look?

  2. 2. A third-party customer has not been billed. What should be checked first?

  3. 3. Why are zero transfer prices dangerous?

  4. 4. What is the first diagnostic question for any failed cross-functional flow?