Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home2/ofsap/public_html/ierp.us/static.php on line 49 VOV8 SAP t-code details
Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home2/ofsap/public_html/ierp.us/static.php on line 462
Total contributors: 2558
Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home2/ofsap/public_html/ierp.us/sap-tcodes/tcode.php on line 15
VOV8 SAP Transaction Code (T-code) Details
Description: Document Type Maintenance Program : Module:
SAP Menu Path: VOV8 tcode does not exist in SAP menu tree on SAP Easy Access screen. It might be in other place in SAP such as in SPRO menu path, or it might be a tcode that does not intend to be used by SAP end-users.
Info : VOV8 is an SD configuration tcode to maintain Sales Order (SO) document type.
The sales document types represent the different business transactions in Sales and perform a central controlling function for the entire sales order process. The definition and configuration of sales document types can be divided into three parts:
1. Definition of the sales document types themselves (for example, standard order OR)
2. Definition of additional sales document functions (for example, number ranges)
3. Configurations for general sales and distribution functions (for example, pricing)
1. Defining sales document types
To define sales document types, you must make a large number of controlling specifications which are listed below. Be careful that the sales document types are not isolated but are always closely linked with delivery types and billing types. When defining sales document types, you must therefore take settings into account which are listed for deliveries and billing documents.
This connection is apparent in the following examples:
You can allow a billing block to be proposed that must be checked by the billing department for each sales document type (for example, in the case of returns).
You can allow a certain delivery type to be proposed for a sales document type during delivery processing.
For each sales document type, you can configure the system to automatically propose the current date as a delivery date.
2. Defining additional sales document functions
When defining your own sales document types or adjusting the standard document types to your company-specific requirements, take the following settings into account in addition to the actual sales document types:
Screen sequence groups
Blocks for each sales document type
Reasons for rejection
Assignments to the different organizational units
3. Setting general SD functions
You have to configure a number of general SD functions for sales document types.
You can, for example, perform a certain type of pricing for each sales document type. In this case, process the sales document type and the pricing independently and allocate the required document pricing procedure for pricing to the sales document type.
You can also propose your own output for each sales document type. To do this, allocate your own output types and output determination procedures to the sales document type.
You have finished defining a sales document type when youi have processed the following general SD functions:
General procedure when setting up sales document types
You have three options for configuring new sales document types:
1. Change an existing sales document type.
2. Copy an existing sales document type and changee it according to your requirements.
3. Create a new sales document type.
For small changes, SAP recommends that you copy similar existing sales document types in the standard SAP R/3 System and make the appropriate changes. Small changes might, for example, be, a changed description, a different number range or a different increment for the numbering of items. The name is to start with the letter Z as SAP keeps this range free in the standard system. This procedure has the following advantages:
All the specifications of the existing sales document type are copied. In particular, the data concerning, for example, partner determination, pricing or document flow which you would otherwise have to edit manually is copied.
You can test your new sales document types in respect to the settings made without having to edit the other settings.
When copying sales document types, item categories and schedule line categories, the SAP R/3 System automatically creates a log with the copied data. Using the log, you can check whether all of the copied data applies to your sales document type or whether you need to make changes.
1. If you need to make further changes, you should define new sales document types. To do this, you enter an alphanumeric key with a maximum of four characters for a sales document type and a textual description for the key.
2. Maintain the specifications on the detail screen according to your requirements.
Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home2/ofsap/public_html/ierp.us/static.php on line 571
What do the people search on iERP.us? The latest 10 search queries: - ML91 in SPRO-Tcode - reverse miro in Tcode-Description - OB52 in SPRO-Description - OMSY in SPRO-Description - OAAQ in SPRO-Description - OB90 in SPRO-Description - ob90 in SPRO-Description - ML91 in SPRO-Description - pricing in SPRO-Description - OKB9 in Tcode-Description