Creating new plant in SAP

This tutorial guides you how to create/Define Plant in SAP step by step.

OX14 – Define Valuation Area (Once your system go live, no more changes possible)

SPRO > SAP Customizing Implementation Guide (IMG) > Enterprise Structure > Definition > Logistics – General > Define copy, delete, check plant [OX10]:

Enter new plant code and update the name and address of the plant:

After updating all mandatory fields click on save icon.

Create company code on IMG:

After creation of new plant you should MM, PP, FI and SD modules to check all their module specific business flows related to your new plant.

OVXB – Create, Change, View Division

OX02 – create Company code

OX18 – Assign Plant to company code

OBY6 – provide details for Company code global data

OX19 – Assignment of company code to the Controlling Area:

OB45 – Create credit Control Area

OB38 – Assign company code to Credit Control Area
OMJ7 – Assign business area to Plant/Valuation area and division

ZTOAD – alternate SQL builder (SAPLink)

ZTOAD – is an alternate SQL builder (SAPLink). It can be installed using SAPLink (SAPLink should be installed as well).

SAPLink is a tool for importing and exporting ABAP developments from one system to another. The main terms of SAPLink are nuggets and slinkies:
a) a slinkee file (.slnk) is used for single objects to be imported or exported. Slinkees are very quick and easy to use and recommended for single object collaboration. They can be imported and exported from the “Object” tab.
b) SAPLink nuggets are the SAPLink packaging system that enables multiple objects to be imported/exported in one handy dandy file (.nugg). Nuggets can be imported, created, and displayed from the “Nugget” tab.

With ZTOAD (called ZTOAD in reference of a famous query builder in the SQL) you can write and execute queries, in OpenSQL format (the format used in ABAP programs). Result is displayed in an ALV at bottom part of the screen:

The order is next:
1. Install SAPLink
2. Install DDic plugin (just import NUGG_SAPLINK_DDIC.nugg nugget file).
3. Install ZTOAD
4. Launch SE38 -> ZTOAD

P.S. In case of error “CLASS ZSAPLINK DEFINITION LOAD statement is missing.” just add the string

after the string

in the ZSAPLINK program.

P.P.S. “Plugin for object type TRAN is not installed on this system”: CLAS_ZSAPLINK_TRANSACTIONS.slnk,
“Plugin for object type DEVC is not installed on this system”: CLAS_ZSAPLINK_DEVC.slnk
and activate “Inactive local objects” in SE80.

Keep button – keep results pinned to the screen

The Keep button is available in possible options search pop up windows. You see this pop up window when you click on the Possible Entries button in a field on a criteria selection/definition screen.

Identified by pushpin icon – 

For example, go to MB51. Press the ‘Multiple selection’ button near Material field

Click on the ‘Possible entries’ or hit F4 key to select few materials.

Now, before double clicking on the material, click the Keep button so that it points downwards (i.e. it is pinned). Now double click.

Try to use it in any lists, e.g. ME21N:

When you are finished, click the Keep button to release the list.

NB: if pushpin is not pulled out before exiting the transaction, the screen can become orphaned, causing an error or a window that cannot be closed.

How to create a new material movement type in SAP

How to create movement types? What are the steps involved?
Let’s see how we can create a new material movement type in SAP.

Companies may request a new movement type to differentiate between the inventory posting transaction.

Assuming I want to create another movement type 9Z2.
Transaction – OMJJ

Menu path – IMG > Material Management > Inventory Management > Movement types > Copy, Change Movement types

To copy a movement type, select the field “Movement type” from the popup and choose Continue.

The dialog box Define work area appears.

In the dialog box “Define work area”, enter the movement type you want to copy in the “From:” field.
In the “To:” field, enter the name of the new movement type you want to create (the new MvT should either beginning with 9 or Z).

On “Change view movement type: overview” screen, select movement type to copy and click on “Copy as…” icon (F6):

Give the name and press “Enter” key:

Click on “Copy All” when a pop up window appears which says “the entry to be copied has dependant entries” and you should be able to see an information message after successful copy.

Check all views for the new movement type and, if necessary, change the control indicators. Please note that some views have a detail screen:

  • Short texts – here you can maintain transaction short text for different languages.
  • Allowed transactions – a list of transactions can be maintained which are allowed to post this movement type.
  • Help texts – this text will be visible to the user when he presses F1 for help. It can be maintained in different languages.
  • Field Selection – Over here required and optional entry fields can be maintained. The fields are grouped into logical groups like Account Assignment, Material Management etc. Based on the group, a desired field can be selected. This field can then be suppressed, made a required entry or an optional entry based on the radio button selection.
  • Update Control – This is applicable is Warehouse Management is active. The settings in this tab provide the reference movement type for Warehouse Management.
  • Account Grouping – In this screen you can maintain the account modification keys. The account modification key is to differentiate account determination for the goods movement. The values of this key are SAP predefined and cannot be changed (T030).
  • Reversal / follow on movement – Over here you can maintain the movement type for reversal movement. By Indicator type of posting in this screen, the system decides whether the quantity adopted from the reference document (which is getting reversed based on this movement type) may be changed or not.
  • Reason for movement – Over here you can define which reasons are allowed while posting the mentioned movement type. This field is usually used to differentiate the different scenarios (for reporting purpose) in which the said movement type can be used. The movement type configuration for Field Selection can be used to determine if this is a mandatory or an optional field while posting the document.
  • Deactivate QM inspection – By this setting you can configure the instances when this movement type is used and Quality Management is not active. As a result no inspection lots will be created for an inspection process.
  • LIS statistics group – Over here different statistic groups can be maintained for different possibilities of this movement type.

Now we can save it.

SAP SD Certification Exam (130 questions)

Spoiler: Large HTML table.

c. The availability control screen will be displayed During the sales order processing, a user will be alerted when stock is not available for material entered in the sales order if the availability check was carried out. In which of the following ways will the user be alerted about the situation?
a. An error message will appear on status bar alerting the user to the situation
b. The selected line will be marked and highlighted by the system
c. The availability control screen will be displayed
d. The incompletion log will display the unconfirmed schedule line as a missing field
b. Sales order number
c. Terms of payment
d. Payer
In the standard system, which of the following can be used as splitting criteria when creating an invoice?
a. Account group
b. Sales order number
c. Terms of payment
d. Payer
e. Sold-to-party
a. Whether document number is external or internally used
c. Whether an item is blocked for delivery
d. Whether a delivery document is created automatically
Which of the following does the sales document type control? (3)
a. Whether document number is external or internally used
b. Whether an item is to be delivered
c. Whether an item is blocked for delivery
d. Whether a delivery document is created automatically
e. Whether availability is checked

Continue reading SAP SD Certification Exam (130 questions)

SAP customer list in Russia

SAP customers in Russia:

X5 Reatil Group
IDGC of Centre (МРСК)
MRSK Urals
Невская косметика (NC)
Pension Fund of the Russian Federation
Sunway Group
OAO Slavneft-MegionNeftegaz
Produkty Pitania
Tactical Missiles Corporation
Smart Value
Russian Railways
Bezant (ТК БЕЗАНТ)
Victoria Group
Vympel NPO
Megapolis (
MKB Raduga
Велком (Velkom)
ROLF (group of companies)
Detski mir
Cherkizovo group
Ulmart (Юлмарт)
Tvoy Dom
Vnukovo Airlines
Norilsk Nickel
Moscow Metro
Nizhpharm (STADA CIS)
Arkhangelsk Pulp and Paper Mill
JSC “Belebeevsky zavod “Avtonormal” (“BelZAN”)
Альфа Цемент


Клиенты SAP в России


> Tables

Q: Как просмотреть списки существующих транзакций по маске?
A: SE93 -> M* Enter, F4

Q: Как изменить/редактировать книгу источника поставок (source list)?

SM04 – Список пользователей. Позволяет просмотреть с какими транзакциями работает пользователь и сколько режимов у него открыто.

AL08 – Список активных пользователей
SM50 – Обзор процессов. В частности позволяет просмотреть работает ли ваша “зависшая» транзакция
search_sap_menu – транзакция для поиска в SAP menu

s_BCE_68001399 – узнать какие люди связаны с ролью.
S_BCE_68002041 – какие транзакции в роли.
SM01 – списки транзакций как фильтр по коду, например ввести там ME8 и смотреть какие т-коды имеют отношение к отчетам по PO

При COGI заменить один материал другим: MIGO -> A08 Transfer Posting, R10 Other (MvtType 309) – указываем материал, количество, склад, себя в качестве поставщика и клиента. Check & save.
(дату здесь можно менять, если месяц уже закрыли)

CKMM – изменение Определения цены (Price determination) или Price control indicator (S/V) (Управление ценой)
(S – надо использовать для стандартных материалов, цена – 0 руб., V – для торговых изделий)

MB1B 311 или MIGO 311 – трансфер с одного склада на другой.

VL02N – изменить/удалить поставку.
VL06o – список исходящих поставок (с возможностью напечатать накладные ТОРГ-12)
VL09 – сторнировать входящую или исходящую поставку
VL32N – удалить входящую поставку
VL71 – напечатать ТОРГ-12 из поставки
VF01 – выдать исходящую счет-фактуру
VF02 – создать сопутствующий документ в бухгалтерию.
VF05N – список фактур, платежных документов (например, созданных в VF01)
VF11 – сторнировать фактуру
VF31 – печать документов ко счету.
VFX3 – просмотр ошибок со счетами
VA05N – просмотр и поиск сбытовых ордеров
VA33 – просмотр долгосрочных форкастов (конкретных заказов от клиента – PO от клиентов).
VA35N – просмотр и поиск сбытовых соглашений
VD01 – расширить (создать) дебитора.

SE16N –> таблица T001L – просмотр складов.
таблица MARA – поиск материала;
T030 – сопоставленный счету класс оценки
C001 – сопоставленный счету Acct assignment grp

MB02 – поиск по номеру документа материала (по проведенному номеру)
MBSM – по номеру документа был ли он сторнирован?
MBST – сторно документа материала поэтапно.
MM04 – просмотреть историю изменений материала
MM17 – массовое изменение материалов
MMRV – разрешить постинг в прошлом периоде (узнать какой период идет сейчас)
MMPV – закрыть период

ME2N – поиск среди закупок, список закупочных агриментов
ME2M – список закупочных документов агриментов с ценами
ME2L – поиск среди документов по поставщику. Например, если есть PO, но нет приходования MIGO, то можно вывести список, указав Document Type: NB (колонка To be delivered).
ME5A – вывод PR’ов с возможностью выборки лишь “полностью одобренных/деблокированных” (Processing Status = N для тех PR’ов к которым еще нет PO).
ME9F – печать документов (в ME22N можно редактировать Message, если что-то надо печатать повторно).
ME9E – печать расписания
ME9L – печать агриментов

MD01 – запуск MRP на весь завод.
MD02 – запуск MRP на конкретный материал.
MD04 – просмотр доступности требуемого материала (например, наличия на складе).
MFBF – выпуск (декларирование) готовых изделий (бэкфлаш), также ручное внесение количества трима за период (за смену, например)
MF41 – сторно бэкфлаш.
MF42N – то же что и MFBF, но внесение информации о нескольких материалах подряд.
ME38 – удалить Scheduling agreement
ME55 – деблокирование заявки на закупку.
ME54N – деблокирование позиции по отдельности.
ME84 – создать call-off релизы
NACE – conditions for output control (указываем по типу документа поставщиков – подставлять по умолчанию)

BD87 – перепроведение IDoc.

XD03 – Просмотреть данные по клиенту (FI – базовые функции)
VD03 – Просмотреть данные по клиенту (Sales) FI
FD03 – Просмотреть данные по клиенту (FI, бухгалтерия)

XK03 – Показать данные по поставщику (модуль FI – базовые функции)
FK03 – Показать данные по поставщику (бухгалтерия – FI)
MK03 – Показать данные по поставщику (закупки, FI – базовые функции)

FB03 – найти по номеру документа исходящую поставку (в рефренсе)

MIRO – новый входящий счет.

SU53 – просмотр прав
SIUM – (user information system) – просмотр списка юзеров 2155.
SU01 – просмотр / состояние паролей.
SU2 –
SM20 – transactions history
SM37C – jobs overview

VKOA – поменять счет выручки (Таблица 1, приложение V, условие KOFI, план счетов IKOP)

BD55 Правило преобразования для User Exit. Ссылка на правила преобразования User Exit для различных систем.
WE19 EDI тестирование. Используется для тестирования изменений в функциональных модулях.
WE31 Создание сегмента
WE30 Создание расширения типа IDOC
WE82 Разблокирование ссылки
WE57 Присвоение Функционального Модуля сообщению и типу IDOC

ME3L – Outline agreements per vendor
ME3M – Outline agreements per material
ME3C – Outline agreements per material group
ME3B – Outline agreements per requirement tracking number
ME3N – Outline agreements by agreement no.
MSRV5 – Service list for contract
ME3K – Outline agreements by account assignment

VA05 Список заказов
VA02 Изменить сбытовой заказ
VA32 изменение соглашения о поставках
VA42 изменить контракт
VA22 Изменить предложение
VF02 изменить фактуру
VL02N изменить поставку
VF11 сторнирование фактуры
VF04 обработать рабочий список фактур
VL04 рабочий список заказов клиентов/заказов на поставку
VKM3, VKM4 списки торговых документов
VKM1 блокированные документы Сбыта
VKM5 список поставок
VL06G список исходящих поставок для отпуска материала
VL06P исходящие поставки для комплектования
VL09 сторнирование движения материала
VT02N изменение транспортировки
VT70 выходные документы к транспортировкам


XD01 Create Customer (Centrally)
XD02 Change Customer (Centrally)
XD03 Display Customer (Centrally)
XD04 Customer Changes (Centrally)
XD05 Block customer (centrally)
XD06 Mark customer for deletion (centr.)
XD07 Change Customer Account Group
XD99 Customer master mass maintenance
XDN1 Maintain Number Ranges (Customer)


XEIP Number range maintenance: EXPIMP
XK01 Create vendor (centrally)
XK02 Change vendor (centrally)
XK03 Display vendor (centrally)
XK04 Vendor Changes (Centrally)
XK05 Block Vendor (Centrally)
XK06 Mark vendor for deletion (centrally)
XK07 Change vendor account group

Sales Order

VA00 Initial Sales Menu
VA01 Create Sales Order
VA02 Change Sales Order
VA03 Display Sales Order
VA05 List of Sales Orders
VA07 Compare Sales – Purchasing (Order)
VA08 Compare Sales – Purchasing (Org.Dt.)


VA11 Create Inquiry
VA12 Change Inquiry
VA13 Display Inquiry
VA14L Sales Documents Blocked for Delivery
VA15 Inquiries List


VA21 Create Quotation
VA22 Change Quotation
VA23 Display Quotation
VA25 Quotations List
VA26 Collective Processing for Quotations


VA41 – Create Contract
VA42 Change Contract
VA42W Workflow for master contract
VA43 Display Contract
VA44 Actual Overhead: Sales Order
VA45 List of Contracts
VA46 Coll.Subseq.Processing f.Contracts

Item Proposal

VA51 Create Item Proposal
VA52 Change Item Proposal
VA53 Display Item Proposal
VA55 List of Item Proposals
VA88 Actual Settlement: Sales Orders


VL00 Shipping
VL01 Create Delivery
VL01N Create Outbound Dlv. with Order Ref.
VL01NO Create Outbound Dlv. w/o Order Ref.
VL02 Change Outbound Delivery
VL02N Change Outbound Delivery
VL03 Display Outbound Delivery
VL03N Display Outbound Delivery
VL04 Process Delivery Due List
VL06 Delivery Monitor
VL06C List Outbound Dlvs for Confirmation
VL06D Outbound Deliveries for Distribution
VL06F General delivery list – Outb.deliv.
VL06G List of Oubound Dlvs for Goods Issue
VL06I Inbound Delivery Monitor
VL06IC Confirmation of putaway inb. deliv.
VL06ID Inbound Deliveries for Distribution
VL06IF Selection inbound deliveries
VL06IG Inbound deliveries for goods receipt
VL06IP Inbound deliveries for putaway
VL06L Outbound Deliveries to be Loaded
VL06O Outbound Delivery Monitor
VL06P List of Outbound Dlvs for Picking
VL06T List Outbound Dlvs (Trans. Planning)
VL06U List of Uncheckd Outbound Deliveries
VL08 Confirmation of Picking Request
VL09 Cancel Goods Issue for Delivery Note
VL10 Edit User-specific Delivery List
VL10A Sales Orders Due for Delivery
VL10B Purchase Orders Due for Delivery

Customer management

FD01 Create Customer (Accounting)
FD02 Change Customer (Accounting)
FD02CORE Maintain customer
FD03 Display Customer (Accounting)
FD04 Customer Changes (Accounting)
FD05 Block Customer (Accounting)
FD06 Mark Customer for Deletion (Acctng)
FD08 Confirm Customer Individually(Actng)
FD09 Confirm Customer List (Accounting)
FD10 Customer Account Balance
FD10N Customer Balance Display
FD10NA Customer Bal. Display with Worklist
FD10NET Customer Balance Display
FD11 Customer Account Analysis
FD15 Transfer customer changes: send
FD16 Transfer customer changes: receive
FD24 Credit Limit Changes
FD32 Change Customer Credit Management
FD33 Display Customer Credit Management
FD37 Credit Management Mass Change


V/03 Create Condition Table (SD Price)
V/04 Change Condition Table (Sales pr.)
V/05 Display Condition Table: (Sales Pr.)
V/06 Condition Categories: SD Pricing
V/07 Maintain Access (Sales Price)
V/08 Conditions: Procedure for A V
V/09 Condition Types: Account Determin.
V/10 Account Determination: Access Seqnc
V/11 Conditions: Account Determin.Proced.
V/12 Account Determination: Create Table
V/13 Account Determination: Change Table
V/14 Account Determination: Display Table


CS00 BOM Menu
CS01 Create Material BOM
CS02 Change Material BOM
CS03 Display Material BOM
CS05 Change Material BOM Group
CS06 Display Material BOM Group
CS07 Allocate Material BOM to Plant
CS08 Change Material BOM – Plant Alloc.
CS09 Display Allocations to Plant
CS11 Display BOM Level by Level
CS12 Multilevel BOM
CS13 Summarized BOM
CS14 BOM Comparison
CS15 Single-Level Where-Used List
CS20 Mass Change: Initial Screen
CS21 Mass Material Change: Initial Screen
CS22 Mass Document Change: Initial Screen
CS23 Mass Class Change: Initial Screen
CS25 Archiving for BOMs
CS26 BOM deletion
CS27 Retrieval of BOMs
CS28 Archiving for BOMs
CS31 Create class BOM
CS32 Change class BOM
CS33 Display class BOM
CS40 Create Link to Configurable Material
CS41 Change Material Config. Allocation
CS42 Display Material Config. Assignment
CS51 Create standard BOM
CS52 Change standard BOM
CS53 Display standard BOM
CS61 Create Order BOM
CS62 Change Order BOM
CS63 Display Order BOM
CS71 Create WBS BOM
CS72 Change WBS BOM
CS73 Display WBS BOM
CS74 Create multi-level WBS BOM
CS75 Change multi-level WBS BOM
CS76 Display multi-level WBS BOM
CS80 Change Documents for Material BOM
CS81 Change Documents for Standard BOM
CS82 Change documents for sales order BOM
CS83 Change documents for WBS BOM
CS84 Change documents for class BOM
CS90 Material BOM Number Ranges
CS91 Number Ranges for Standard BOMs
CS92 Number Ranges for Sales Order BOMs

Smart Forms vs Adobe PDF-based forms

Here is a comparison between the two largest print form formats.
All new forms delivered with the ERP will be PDF-based. So, it’s probably better to get ready to change.

Knowing those two print forms possibilities offered by SAP, you want to know more about what is the best technology to use.

Hopefully I’ll provide you some answers in this paper. I’ll probably write more complete comparisons as experiences with PDF forms grows.

Smart Forms architecture

The application program retrieves data from the database and is passed to the function module generated by the Smart Form. The application program, which collects data, has to be written. In many cases, a standard print program is copied, modified and then reused.

The Smart Form needs to be defined. With transaction SMARTFORMS, you can setup the layout you want. This is a powerful but quite old tool and its usage is requires some learning time.

PDF-based print forms architecture

At runtime, we notice the architecture is very close of the previous one.

In this case, a print program also needs to be written. The PDF form template, consuming data from its interface, is called by the generated function module. The call to the web service and the PDF is physically built during runtime.

The ADS component runs on the J2EE stack and exposes a web service allowing the rendering of PDF forms. This means extra calls between both stacks.

Note that you can use this web service to build other PDF forms.

Comparison: pro et contra


Every form has layout problems at some point in time. Text is too low the page; the first name is not aligned with the last name, tables don’t display correctly etc. In both cases, there are a lot of tests (“chipotages”, for the French-speaking people) to perform before a form version can be released.

There is a first advantage of PDF in comparison with Smart Forms. The Adobe LiveCycle Designer (ALD) is at first sight simple, yet powerful and comprehensive. So to build a layout is easier with PDF forms for people with limited experience.

When you have lots of forms to develop, you can enhance the custom objects in the ALD: you can add multiple UI objects and group them in one element which you can easily reuse. For instance, a ‘UserData’ element that contains firstname, lastname, street, postal code and city. Element types as well as the layout are stored locally (in folder C:\Users\\AppData\Adobe\Designer\en\objects\), so exchange with other forms developers is quick and easy.

So, bottom line is that development time can be reduced by using PDF forms. Of course, this also depends on your developers’ skills.


As you know, every object-oriented language has performance problems. So does Java… The ADS component is also heavy and the rendering time of a very complex PDF form, with lots of scripting logic and data to display, can take some time. This may result in heavy documents. Another reason for the sometimes slow performance is the web service connection.

This performance issue must be taken into account when considering high volume printing and complex forms.

Of course, be aware there are possibilities to improve PDF rendering time. Form bundling is one of them (the bundling principle is to send multiple forms in one call to ADS); another one, valid as of NetWeaver 2004s SP12, is described in SAP Note 993612.

Smart Forms, which run fully on the ABAP side, can be faster than PDF… for the moment. I’ll probably post more about performance comparisons in the future.

Regarding stability, both technologies are equivalent and I personally never had problems regarding this. Feel free to provide your input!


As said earlier, PDF requires a J2EE stack with ADS properly configured and with connections between both systems up and running. This is done in standard as of NetWeaver 2004 SR1 so don’t panic! Every recent SAP solution includes the J2EE stack including ADS.

There are web services calls between the ABAP and J2EE stacks, which makes for additional connections to handle.

In terms of architecture, the PDF seems to require more attention. Although, the J2EE stack with ADS is installed and configured in standard as of the ERP2004 so there should be no particular worries about this.

Front-end and clients

The PDF requires Adobe Reader to display PDF forms. Nowadays, almost every workstation has Adobe Reader installed on it. Reader is not required to print forms: hopefully, the normal PDF drivers are supported in SAP systems as well as most of standard printer drivers.

Smart Forms require no additional installations on top of the standard SAPGUI.


Customer examples

In this case, everything depends on your scenarios. Some examples for PDF: you need to respect a legal template, which is provided in PDF; PDF is already widely used in your company; you have all the other Adobe products; you need to send printed invoices to your customers automatically via mail with PDF format etc.

On the other hand, you can choose to use Smart Forms for various reasons: your SAP system printing documents is R/3 4.7; you have plenty of qualified developers who know Smart Forms very well; you need very high performance rather than flexibility etc.


One reference course for Smart Forms: BC470 – Form printing with SmartForms.

The Adobe LiveCycle Designer embedded in an SAP environment offers a lot of possibilities. More information can be found in SAP course BC480 – PDF based print forms (3 days).


Smart Forms is the faithful technology for those who know it. Still useful and reliable as well as very powerful.

On the other hand, the PDF-based print forms is highly appreciated for its comprehensiveness, compatibility, design possibilities. It’s also the future for form output in SAP solutions.

So, the choice is now yours. Personally (but as you may know, I’m not the most objective person when speaking about forms), my choice goes to the PDF for the reasons mentioned above.

© Francois Gendebien

SAP SD books


“Implementing SAP ERP Sales & Distribution”, Glynn C. Williams, 2008

“Configuring SAP ERP Sales and Distribution 2010”, Kapil Sharma, Ashutosh Mutsaddi, 2010


“100 Things You Should Know About Sales and Distribution in SAP”, Matt Chudy, Luis Castedo, 2012

Common SAP R/3 functions manual, 20.1 Mb

PP Material Requirements Planning


LO Batch Management

P.S. There are four books related to SAP SD Certification – TSCM60 (parts 1 & 2) and TSCM62 (parts 1 & 2).

General SD configuration

Enterprise Structure:

  1. Edit, Copy, Delete, Check Company Code (T001)
    Company is created by FI Consultant.
    The company code is an organizational unit used in accounting. It is used to structure the business organization from a financial accounting perspective.
    IMG -> Enterprise Structure -> Definition -> Financial Accounting -> Define, copy, delete, check Company Code
  2. Define Credit Control Area (T014)
    Company is created by FI Consultant.
    The credit control area is an organizational unit that specifies and checks a credit limit for customers.A credit control area can include one or more company codes. It is not possible to assign a company code to more than one control area. Within a credit control area, the credit limits must be specified in the same currency.
    IMG -> Enterprise Structure -> Definition -> Financial Accounting-> Define Credit Control Area
  3. Maintaining Sales Organization (TVKO)
    Sales Organization is an organizational unit responsible for the sale of certain products or services.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
  4. Assigning Sales Organization to Company Code (TVKO-BUKRS)
    This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
  5. Maintaining Distribution Channel (TVTW)
    Distribution Channel is the way, in which Products or Services reach Customers.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
  6. Assigning Distribution Channel to Sales Organization (TVKOV)
    This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
  7. Maintaining Division (TSPA)
    Division is a way of grouping materials, products, or services.
    IMG -> Enterprise Structure -> Definition -> Logistics – General -> Define, copy, delete, check division
  8. Assigning Division to Sales Organization (TVKOS)
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
  9. Setting up Sales Area (TVTA)
    All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
    IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
  10. Maintain sales office (TVBUR)
    The definition of sales offices is optional.
    For each sales office, you can determine the printer for output based on the sales documents in different ways
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Maintain Sales Office
  11. Assign sales office to sales area (TVKBZ)
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales Office to Sales Area
  12. Maintain sales Group (TVKGR)
    The definition of sales groups is optional. You can use the SD system without creating sales groups.
  13. Assign sales group to sales office (TVBVK)
    You can assign as many sales groups as desired to the sales offices. Any one sales group can belong to several sales offices.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales group to sales office
  14. Define Shipping Points (TVST)
    Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
    IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
  15. Define, copy, delete, check plant (T001W)
    Plant is created by MM Consultant.
    IMG -> Enterprise Structure -> Definition -> Logistics – General -> Define, copy, delete, check plant
  16. Assigning Shipping Point to Plant (TVSWZ)
    This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
    IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
  17. Assigning Sales Organization – Distribution Channel – Plant (TVKWZ)
    Plant is created by MM Consultant.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization – distribution channel – plant
    Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
  18. Defining Common Distribution Channels for Master Data (TVKOV-VKWKO TVKOV~VTWKU)
    The purpose of this activity is to define distribution channels which have common master data.  Access the activity using the following navigation:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
    Transaction Code: VOR1
  19. Defining Common Divisions for Master Data (TVKOS-SPAKO TVKOS~SPAKU)
    The purpose of this activity is to define distribution channels which have common master data. Access the activity using the following navigation:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
    Transaction Code: VOR2

Sales and Distribution