VA43 — Display Sales Contract

VA43 opens a sales contract in display mode, showing header data (validity period, cancellation rules, contract type), item data (material, target quantity for a quantity contract or target value for a value contract), and the cumulative amount already released against that target. A sales contract is an outline agreement, not a document that itself triggers delivery or billing. The structural fact that causes most confusion is that everything a user sees as 'consumed' on the contract is actually the sum of separate release orders created with reference to it. If a release order was created without proper reference, or the reference was broken during copy control, the contract in VA43 will look under-consumed even though goods physically moved and were billed through that release order.

Consultants reach for VA43 when someone disputes remaining quantity or value on a contract, before creating a release order to confirm what is still available, during month-end or contract-expiry review, or when investigating why a release order was rejected for exceeding the contract limit. It sits between contract negotiation (VA41 to create) and the ongoing release order cycle (VA01/VA02 with contract reference). On S/4HANA the Fiori app for managing sales contracts covers the same review with a worklist and status filters, but VA43 remains the fastest single-document check when a specific contract number is already known, especially during an incident where the Fiori layer itself is suspect.

Pull VBAK for the contract number to get VBELN and AUART, confirm it is a recognized contract type. Then query VBFA where VBELV equals that contract number and VBTYP_V equals the contract document category, restricting VBTYP_N to the sales order category, to list every release order actually linked. Sum the relevant quantity or value field from the linked orders' VBAP entries and compare it against the target and cumulative fields on the contract's own VBAP row. A mismatch between the two sums is the proof point, not the number shown on the VA43 screen alone.

VA43 still works on S/4HANA and the underlying VBAK/VBAP contract data model is unchanged. The Fiori app for managing sales contracts adds a worklist view with filters on validity, status, and value bands, which is more useful for portfolio-level review, but for a single known contract number VA43 remains just as fast and is often preferred during troubleshooting because it bypasses the Fiori launchpad layer entirely.

Functional SD ownership. A clean handover states the contract number, the specific item and consumption field in question, the release order numbers already checked in VBFA, and whether the discrepancy is a missing reference, an incomplete order, or a configuration question on the document type. Escalate to ABAP only if a custom pricing or update routine is suspected of failing to post consumption.

Read VA41 and VA42 next to understand how contracts are created and changed, since VA43 only makes sense once the creation logic behind target quantity and value is clear. VOV8 explains the document type settings that govern cancellation rules and validity behavior seen in VA43. VK11 through VK13 are relevant when the dispute is really about a pricing condition tied to a value contract rather than about the quantity itself.