SAPFree referencePDF, Excel, Word exportSAP ECC / S/4HANA

SAP Sales Document Types Reference: OR, QT, IN, RE, CR and More

Sales document types decide how an SD document behaves: number range, partner determination, pricing procedure, delivery type and billing type. This reference lists the standard types a consultant meets in almost every SAP SD project.

Download:

Doc type	Description	SD category	Group	Typical use
IN	Inquiry	A	Pre-sales	Records a customer request for information on prices or availability, no commitment.
QT	Quotation	B	Pre-sales	Binding offer with a validity period, can be referenced when creating the order.
OR	Standard Order	C	Order	Normal sales order that drives availability check, delivery and billing.
RO	Rush Order	C	Order	Order where the goods are delivered the same day or the next day, delivery is created automatically.
CS	Cash Sale	C	Order	Customer pays and takes the goods immediately, delivery and invoice are created together.
SD	Free of Charge Delivery	C	Order	Sample or replacement shipped without a charge, billing is not relevant.
KE	Consignment Fill-Up	C	Consignment	Moves stock to the customer's consignment stock at your cost, no invoice.
KA	Consignment Issue	C	Consignment	Transfers ownership from consignment stock to the customer when they consume it.
KB	Consignment Pick-Up	C	Consignment	Brings unused consignment stock back from the customer to your plant.
KR	Consignment Returns	H	Consignment	Returns goods the customer already consumed from consignment stock.
RE	Returns	H	Returns	Customer returns goods, a returns delivery and a credit memo normally follow.
G2	Credit Memo Request	K	Billing request	Blocks a credit memo for review before it is released to billing.
L2	Debit Memo Request	L	Billing request	Raises an extra charge to the customer, normally billing blocked until approved.
CQ	Quantity Contract	G	Contract	Agreed total quantity over a period, call-off orders reduce the contract quantity.
WK1	Value Contract (General)	G	Contract	Agreed total value over a period, release orders consume the contract value.
WK2	Value Contract (Material-Related)	G	Contract	Value contract limited to specific materials or material groups.
LP	Scheduling Agreement	E	Scheduling agreement	Long-term agreement where the customer sends delivery schedules, common in automotive.
LZ	Scheduling Agreement with External Service Agent	F	Scheduling agreement	Scheduling agreement where an external service agent handles the delivery.

Standard types are delivered in the SAP template client. Your system may have Z copies with different control settings. Verify in VOV8 (header controls) and check item categories and copy control for each Z type.

SAP SD configuration review

Optional: we can review your Z document types and copy control against a standard order-to-cash design and send a short list of findings.

Optional. The tool and every export work without this. No spam.

How to use this reference

Type a code such as RE or a word such as contract into the search box and the table filters instantly. Use it when you are scoping an order-to-cash design, preparing a fit-gap workshop or reading a Z document type you found in a client system. Each row shows the document category that SAP uses internally, which controls what a document can follow another in the document flow.

Search by code, name or category letter
Export the table to Excel for your blueprint
Compare the list with the types in the client system
Mark types that need a Z copy in your design

What a sales document type controls

A sales document type is configured once and then governs a whole family of behavior. In customizing (VOV8) you assign the document category, the number ranges, the item number increment, the default delivery type, the default billing type, the schedule line category used for availability, and flags such as billing block and delivery block. Sales area level settings then add the pricing procedure and partner determination. When two business processes differ in any of these, you normally need two document types.

Document category (VBTYP) drives document flow rules
Delivery type and billing type are defaults, not hard locks
Reference requirements control what can be copied in
Number range can be internal or external

Reading the categories

The SD document category is a single letter or number. Inquiry is A, quotation B, order C, scheduling agreement E, contract G, returns H, credit memo request K and debit memo request L. Delivery and billing documents have their own categories, for example J for a delivery and M for an invoice. Knowing the category helps when you debug copy control, because the same combination of source and target category must be allowed in the copy control tables.

Category C covers order, cash sale, rush order and consignment
Returns use H, not C
Contracts use G regardless of value or quantity
Billing documents are covered in the billing types reference

Common mistakes

The most common design mistake is cloning OR into a dozen Z types for each customer group when a single type with different item categories would do. Every extra type multiplies copy control, output and test effort. A second mistake is changing standard type behavior in place instead of copying it, which makes upgrades harder. Finally, teams forget to check that the plant, shipping point and sales area assignments exist for every new type before go-live testing.

Frequently Asked Questions

What is the difference between a sales document type and a sales document category?

The sales document type, such as OR or RE, is a customizing object you configure and can copy. The sales document category, a letter like C or H, is a fixed SAP classification each type belongs to. The category decides document flow and which processing rules apply.

Where do I maintain sales document types in SAP?

Use transaction VOV8 for the header-level controls, or SPRO under Sales and Distribution, Sales, Sales Documents, Sales Document Header. Item categories and schedule line categories are maintained in their own nodes and then assigned to the document type.

Should I use standard types or Z types?

Use the standard type where the behavior fits, and copy it to a Z type only when you need different controls such as a separate number range, pricing procedure or billing block. Never change delivered standard types in place, because upgrades and support packages may overwrite them.

Is this list complete?

No. It covers the standard types most projects use. The SAP delivered template has more, including industry and country variants, and every customer system adds its own Z types. Always confirm against table TVAK in the client system you are working on.

If you are mapping a large set of Z document types and want a faster way to inspect what each one actually does in your system, we can build a read-only analysis agent over your SAP configuration data.

Talk to an Expert Explore More Free Tools

Related Tools

SAP

More SAP tools

See all

Back to All Tools