Basic Transaction codes

Transaction codes are the short path to s specific screen in SAP. They are found by selecting
System Status. The SPRO transaction code is the shortcut for the business IMG. The standard
menu path is always described from the logistic screen (unless specifically stated from the
IMG). Thus the menu path to get to the IMG from the Logistics screen is as follows

Path:

Tools
Customizing
IMG
SPRO Edit Project
SAP Reference IMG

NOTE: Transaction codes call up screens, there must be a link from the screen you are trying
to access to the relevant screen you wish to call up; thus, you will not be able to use the
transaction codes whilst in the IMG. As a general rule, you can access every screen from the
logistics screen.

The Structure of SAP SD Master Data

Master data forms the basis of the SD processing. Master data is the responsibility of all
modules, as each module has an element of it. However, many other modules other than SD,
such as PP, FI, AND CO, will access the SD master data. The structure of this master data
represents how the system is to perform in the future. It is the highest level of data and thus it
has the largest effect on the standard business process. Master data in SD is divided into three
main areas:
Organizational Data:
This is the structure of the company, whereby each area of the business is represented by
hierarchical element. For example, a sales area is constructed of a sales organization, a
distribution channel, and a division. The Finance module uses the highest form of master
data, which is the company code. The SD module integrates with this company code via the
sales organization. Thus, due to the link between the sales organization and the company code
in Finance, SAP knows which company code to post a sales transaction to. This is based on
the sales organization in the sales order.
Customer and Material Master Data:
As goods and services are sold by the company, for which the organizational data has been
maintained, we need to represent this material and service data in our system as well as
maintain and represent all our different sold-to-parties and partners.
Document Master Data:
Business transactions are stored in the form of documents. These SD documents are
structured in such a way that all the necessary information is stored in a systematic way.
Relationships
Company-to-Company code:
One Company can have many company codes. But one company code has to be assigned to
one company. So the relation is one to many.
Company code to Sales Organization:
One company code can have many sales organizations. But one sales organization has to be
assigned to one company code. So the relation is one to many.
Sales Organization to Distribution Channel:
One sales organization can have many distribution channels. One distribution channel can be
assigned to many sales organizations. So the relation is many to many.
Sales Organization to Division:

One sales organization can have many divisions. One division can be assigned to many sales
organizations. So the relation is many to many.
Distribution Channel to Division:
One distribution channel can have many divisions. One division can be assigned to many
distribution channels. So the relation is many to many.
NOTE: Division is always sales organization specific. If sales organization wants to use a
plant that plant must be assigned to sales organization.

Master data
Master data is a pool of data that is going to be created centrally in the system and that is
available for relevant documents whenever they want to access master data.
Customer master:
The customer master record is the basis for all sales transactions as well as deliveries and
payments. It maintains the details of the customer in the form of master data. Every customer
master is made up with three (3) sections:
(A) General data [KNA1 Table]
(B) Company code data [KNB1 Table]
(C) Sales area data [KNVV Table]
The customer master partner functions captured into KNPA Table
The customer master shipping details captured into KNPS Table
VD01 is the customer record for sales view creation.
XD01 is the central customer master record creation with company code data.
General data section:
In general data section data about the customers personal details like name, address, and

Telephone numbers is maintained. The customer number, not by the company code or sales
area, only identifies this data.
Important fields:
KUNNR = Customer number
LAND1 = Country key
NAME1 = Name
NAME2 = Name
ORT1 = City
ANRED = Title
STCEG = VAT registration number
Company code data section:
It is only of interest to the accounting department. It includes information by more than one
sales organization.
Important fields:
VKORG = Sales organization
VTWEG = Distribution Channel
SPART = Division
KALKS = Pricing procedure
KDGRP = Customer group
KONDA = Pricing group
PLTYP = Price list type
INCO1 & 2 = Incoterms
LPRIO = Delivery priority
VSBED = Shipping conditions
WAERS = Currency
KKBER = Credit control area
Account group:
FI/CO consultants define account groups for each and every partner function. By using this
account group we can control customer master data by changing or assigning field status to
each and every field. As every customer master is made up with number of fields. Depending
upon the partner function and transaction we assign or change field status to a particular field.
Depending upon the field status system prevents the particular field in the customer master
while maintaining the customer master data.

The account group defines what fields are available in the customer master records.

A sold to party only needs sales relevant data. However, a sold to party can also be
created as all the partner functions.
A ship to party needs only shipping relevant data, such as unloading points and so on.
A payer is the individual or company who settles the invoices for a service or for delivered
goods.
The bill to party need only have the basic data such as address and output fields.
Partner functions:
In the business every partner while performing business transactions they have to fulfil
certain mandatory functions.
They are:
Sold to party
Ship to party
Bill to party
Payer
Standard account group Partner functions Description
Standard account
group
1
2

Partner
functions
Sold to party
Ship to party

3
4

Bill to party
Payer

Description
Who placed the order
Who receives the order
Who receives the
invoice
Who settles the bill

Field status: We can assign field status to each and every field.