# SAP SD Configuration Transactions (IMG T-Codes) Reference

> Source: https://netray.co/tools/sap-sd-configuration-transactions-reference
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Find the SAP SD customizing transaction for a setting, with the table it maintains and the question it answers.

## Category

sap

## Erp

SAP ECC / S/4HANA

## Audience

- SAP SD consultant
- SAP functional analyst

## Tool

**Kind:** worksheet

**Mode:** reference

**Columns:**

#### T-code

**Key:** tcode

**Type:** text

#### What it configures

**Key:** setting

**Type:** text

#### Area

**Key:** area

**Type:** text

#### Main table

**Key:** table

**Type:** text

**Rows:**

**Tcode:** VOV8

**Setting:** Define sales document types

**Area:** Sales document

**Table:** TVAK

**Tcode:** OVAZ

**Setting:** Assign sales area to sales document type

**Area:** Sales document

**Table:** TVAKZ

**Tcode:** VOV7

**Setting:** Define item categories

**Area:** Sales document

**Table:** TVAP

**Tcode:** VOV4

**Setting:** Assign item categories (item category determination)

**Area:** Sales document

**Table:** T184

**Tcode:** VOV6

**Setting:** Define schedule line categories

**Area:** Sales document

**Table:** TVEP

**Tcode:** VOPA

**Setting:** Maintain partner determination procedures

**Area:** Partners

**Table:** TPAR and related

**Tcode:** V/06

**Setting:** Maintain condition types

**Area:** Pricing

**Table:** T685

**Tcode:** V/07

**Setting:** Maintain access sequences

**Area:** Pricing

**Table:** T682

**Tcode:** V/08

**Setting:** Maintain pricing procedures

**Area:** Pricing

**Table:** T683

**Tcode:** OVKK

**Setting:** Pricing procedure determination

**Area:** Pricing

**Table:** T683V

**Tcode:** VKOA

**Setting:** Revenue account determination

**Area:** Account assignment

**Table:** Condition tables of KOFI

**Tcode:** VOFM

**Setting:** Requirements, formulas and copy routines

**Area:** Routines

**Table:** TFRM

**Tcode:** VTAA

**Setting:** Copy control: sales document to sales document

**Area:** Copy control

**Table:** TVCPA

**Tcode:** VTLA

**Setting:** Copy control: sales document to delivery

**Area:** Copy control

**Table:** TVCPL

**Tcode:** VTFL

**Setting:** Copy control: delivery to billing document

**Area:** Copy control

**Table:** TVCPF

**Tcode:** VTFA

**Setting:** Copy control: sales document to billing document

**Area:** Copy control

**Table:** TVCPF

**Tcode:** OVLK

**Setting:** Define delivery types

**Area:** Delivery

**Table:** TVLK

**Tcode:** OVL2

**Setting:** Define shipping points

**Area:** Delivery

**Table:** TVST

**Tcode:** VOFA

**Setting:** Define billing types

**Area:** Billing

**Table:** TVFK

**Tcode:** OB45

**Setting:** Define credit control areas

**Area:** Credit

**Table:** T014

**Tcode:** OVA8

**Setting:** Automatic credit control

**Area:** Credit

**Table:** T691F

**Tcode:** NACE

**Setting:** Output determination for applications

**Area:** Output

**Table:** T685 and output tables

**Notes:** Table names are the main table behind the transaction and can differ by release, so confirm in SE11 on your system. Always change customizing in the development client and transport it.

## Content

**Intro:** SD configuration jumps between many IMG nodes, and consultants memorize the transaction codes that jump straight to them. This reference lists the customizing transactions you need most for documents, pricing, copy control, delivery, billing and credit.

**Sections:**

#### How to use the reference

**Body:** Search for the setting you want to change, such as item category or copy control, and the table shows the transaction and the area. Open the code from the SAP command field, change the setting in the development client and save it to a transport request. Export the filtered rows to Excel for a configuration inventory or a fit gap workshop pack.

#### The order to configure in

**Body:** Configuration has dependencies, so work in a sensible order. Define org structure and assignments first, then partner and document types, then item and schedule line categories and their determination, then pricing, then delivery and billing types, then copy control, and finally output and credit. Copy control is where most late defects appear, because every pair of source and target types needs a row for both header and item levels.

**Bullets:**

- Org structure and sales area assignments
- Sales document types and item categories
- Pricing: conditions, access sequences, procedures
- Delivery and billing types
- Copy control, output, credit

#### Common mistakes

**Body:** Changing standard document types in place makes upgrades painful, so copy to the Z or Y namespace instead. Forgetting to assign the new type to the sales area in OVAZ makes it invisible at order entry. Forgetting a copy control entry gives the message that no follow-up document is possible. Change one thing at a time and test the full flow from order to billing.

**Cta:** If you want a documented inventory of your SD configuration read from the system, Netray can help produce one with a read-only extraction. Ask for a review.

**Faq:**

#### Where do I define sales document types in SAP?

**Answer:** Use transaction VOV8 to define sales document types, stored in table TVAK. After defining a type, assign it to the sales area in OVAZ so users can select it at order entry. Always copy a standard type rather than overwriting it.

#### Which transaction is for pricing procedures?

**Answer:** V/08 maintains pricing procedures. Their determination by sales area, document pricing procedure and customer pricing procedure is in OVKK. Condition types are in V/06 and access sequences in V/07.

#### What is copy control in SAP SD?

**Answer:** Copy control defines how data and quantities pass from one document to the next, such as order to delivery in VTLA or delivery to invoice in VTFL. It also holds the routines that control copying, and missing rows are a frequent go-live defect.

#### Why is my new order type not available in VA01?

**Answer:** The most common reason is that the type is not assigned to the sales area in OVAZ. Also check that it exists in the same client, that the authorization allows the type and that item category determination is set up for it.

## Search terms

sap sd configuration tcodes, vov8 sales document types, v/08 pricing procedure, ovkk pricing procedure determination, vtaa copy control, sap sd img path, sap sd customizing transactions, vkoa account determination

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json