Show TOC

"Define sales document types"

In this menu option you define your document types which represent the different business transactions in sales.

You have the following options:

You cannot make any specifications in this menu option for the following functions:

You edit these functions later in the relevant menu options.

Therefore, a sales document type is not completely defined until you have edited these menu options.

You can maintain special keys for the sales document types in each language (see Actions).

You must check the following specifications in this menu option:

You use the document category to allocate a document type to a particular business transaction. This indicates whether a sales & distribution document is an order, scheduling agreement, delivery or credit memo, etc.
The document category must correspond to the specification on the transaction group.
Specify a one-character, alphanumeric key.
"Possible entries" inform you of the keys you may use.
You can define a block indicator which prevents a sales document from being created for a sales document type. Use this field when setting up a new sales document type. You cannot create sales documents if the sales document type has not been released.
Specify a number range for internal and/or external number assignment.
To do this, you must already have defined the number ranges. For more information on this, see the section "Define number ranges for sales documents types" .
Here you specify the increment for the number range used for items. Bear in mind that items added at a later point must be able to be slotted in to the number range that you define here.
You can define the transaction procedure for each sales document type:
Here, you define which screens are displayed in the SAP System during a particular transaction (for example, creating an order) and in which sequence they are to appear.
Here, you define which fields should be displayed on the header screens of the SAP System.
Here, you define with which transactions you can edit a sales document type in sales order processing.
The transaction group allocated to a transaction must correspond to the document category which you allocated to the same sales document type.
Here, you define which items the SAP System displays during document processing. For example, you can limit the display to the main items.
Here, you define the overview screen which is only displayed during sales order processing if you enter data on the initial screen.
The possible entries inform you which keys you can use here. Currently you cannot change the keys in Customizing.
Here, you define whether a reference document is mandatory when creating a sales document. If this is the case, you must also define to which document type the reference document must belong. You could define that returns must always be created with reference to an order, for example.
Here, you define whether the SAP System should search for a customer-material record by sales document item.
If you do not use customer-material records, you do not have to make any specification here.
Here, you define whether customer-specific data must be entered in a sales document of a particular document type.
If you enter the customer number 0, you cannot enter any data into the field "Customer number" in the sales document. This means you cannot allocate a partner determination procedure for which you have to enter sold-to-party data to the sales document as the SAP System requires a customer number to do this.
This field is used, for example, for product proposals. You define customer-independent data in a product proposal and use this later as a basis for a sales order.
Here, you define whether a sales document and all items contained in it must belong to the same division or not.
To do this, you make the following specifications:
Specify, whether the division is proposed at item level from the material master record of the item, or whether the division specified in the sales document header applies to all sales document items.
You define the system response if the division at header level deviates from that at item level.
The system response only works if different divisions are allowed at header and item level.
Here, you define whether the SAP System automatically proposes the current date as a requested delivery date.
You define the probability in percent with which an inquiry or a quotation will result in an order. The probability which you specified in the customer master record is also included in the calculation of order probability.
During the calculation, the specifications are multiplied together, thus determining the order probability and, for example, the order value of a quotation to be expected.
To analyze quotations according to the order value to be expected, you can list the quotations by order probability. Documents with the highest probability are at the top of this list.
You must specify the delivery type of the delivery to be used for a sales document type due for delivery.
You must have defined the delivery type which you specify here beforehand. For more information, see the section "Define delivery types".
In addition, you must define the copying rules (see the section "Define document flow transactions" ).
If you define a delivery block for a sales document type, this entry is copied into the sales document header. Thus, the sales document is blocked for the delivery types which are allocated to this delivery block. For more information on allocating delivery types to delivery blocks, see the section "Define reasons for blocking in shipping" . You can only remove the block from the sales document manually.
You must specify the billing type of the billing document to be used for a sales document type due for billing.
You must have defined the billing type which you specify here beforehand. For more information, see the section "Define billing types".
In addition, you must define the copying rules (see the section "Define document flow transactions" ).
For every sales document item, you can decide whether you want to use delivery-related or order-related invoicing:
You define the billing type with which delivery-related billing is to be carried out for a sales document item.
If you do not specify a billing type here, you cannot carry out delivery-related billing for sales document items.
You define the billing type with which order-related billing is to be carried out for a sales document item.
If you do not specify a billing type here, you cannot carry out order- related billing for sales document items.
If you define a billing block for a sales document type, this entry is copied into the sales document header. This way, the sales document is blocked for all billing types which are allocated to this billing block. Nevertheless, a delivery can be created. For more information on allocating billing blocks to billing types, see the section "Define reasons for blocking in billing" . You can only remove the block from the sales document manually.

SAP Recommendation

All specifications for the existing sales document type are copied. The data concerning partner determination, pricing, or the document flow which you do not edit in this menu option, is also copied. Consequently, you can test your new sales document types without having to edit the other menu options.

Actions

1. If only insignificant changes have to be made to the existing sales document types, make these changes.
An insignificant change would be a changed description, a different number range or numbering interval for the items.
2. If you have to make further changes, you should define new sales document types.
You can then define different availability checks for different sales document types. Or you can define that a particular sales document type may only contain materials from the same division to ensure that the division is taken into account at all times.
3. If you want to use language-dependent keys for sales document types, you have to allocate the language as well as the corresponding key for this language to the corresponding sales document types. To do this, enter the language-dependent key, which is alphanumeric and can have up to four digits, in the language conversion field.