Sales Document Types 

The standard SAP R/3 System includes a variety of pre-defined sales document types. During the implementation of your system, these standard definitions may be modified to suit the particular needs of your organization. In addition, you may add your own sales document types. The sales document types in the standard system include the following:

Type of processing

Sales document type

Abbreviation

Presales

Inquiry

IN

 

Quotation

QT

 

Free-of-charge delivery

FD

Sales orders

Standard sales order

OR

 

Cash sale

BV

 

Rush order

SO

Outline agreements

Quantity contract

CQ

 

Maintenance contract

WV

 

Rental contract

MV

 

Scheduling agreement

DS

Complaints

Credit memo request

CR

 

Debit memo request

DR

 

Subsequent delivery, free-of-charge

SD

 

Returns

RE

 

Control Elements in Sales Document Types

You can use control elements, configured in Customizing for Sales and Distribution, to define each sales document type in such a way that it is provided with its own range of functions. The document types can be tailored to meet the requirements of your company. You can modify the existing document types or you can create your own if those specified in the standard version of the SAP R/3 System do not meet the needs of your sales organization. Your system administrator is responsible for maintaining control elements.

Your answers to the following questions help to decide how to define a particular sales document type:

General data

  • Can the document be entered only with reference to a preceding document?
    • Should the existing customer-material info record be taken into consideration?
    • Should the delivery date be proposed?
    • Must a customer number be entered when creating a document? For example, assortment modules can be entered
    without reference to a particular customer.
    • Which order probability is defined?
    • Should the division be taken from the material master record for every item or should an alternative division specified in the header take precedence over the item specifications?
    • How should the system respond if the division entered in the header deviates from the division in the items?
    • Should a credit limit check be made?
    • From which number range should the document number for internal or external number assignment come?
    • Which fields are relevant for the incompletion log? The validity period, for example, is important for contracts and must therefore be specified in the document.
    • Can an incomplete document be saved or must all data be complete?
    • Which partner functions are allowed and which ones are mandatory?

    Shipping data

    • Which delivery type should the delivery resulting from the order have?
      • Should delivery scheduling
      be carried out?
      • Should transportation scheduling
      be carried out?
      • Should a delivery block be set automatically for a specific reason? For example, a delivery block may be appropriate for a free-of-charge delivery.
      • You can define shipping conditions for a sales document type. These are copied into the document regardless of what is defined in the customer master record.

      Billing data

      • Which billing type should the invoice resulting from the order or the delivery have?
        • Should a billing block be set automatically for a specific reason? For example, a billing block may be appropriate if a credit memo request should first be checked before it is used as the basis for a credit memo.