SAP SD Report on Sales Process, Master Data & Usage

The dissertation report of SAP in sales and distribution and usage of SAP in sales and distribution
THE DISSERTATION
REPORT OF SAP IN SALES
AND DISTRIBUTION AND
USAGE OF SAP
IN
SALES AND DISTRIBUTION
SUBMITTED TO: SUBMITTED BY:

Mr. Santosh Kumar Jena Dheeraj kumar singh
SAP Consultant, Webcom Technologies DBS/(win)09-11/16
INTERNAL GUIDE:
Page | 1
DELHI BUSINESS SCHOOL
Ms. Sweta Seth.
ACKNOWLEDGEMENT
I would like to express my gratitude to all those who gave me the possibilities
to complete this Project. I would like to thank Ms. Divya Rajput (Director)
and Ms. Sweta Seth; Delhi Business School, New Delhi; Mr. Santosh Kumar
Jena SAP Consultant, Webcom Technologies, New Delhi and college
authorities for providing me the opportunity to work with one of the
prestigious organization.
With a deep sense of gratitude and humble submission I would like to
express my heartiest gratefulness to my Faculty Guide Delhi Business
School , whose help, stimulating suggestions and encouragement helped me in
all the times of research for and writing of this Project.
Date:
Signature:
Page | 2
DECLARATION
I hereby declare that the project report entitled “THE DISSERTATION
REPORT OF SAP IN SALES AND DISTRIBUTION AND USAGE OF SAP
IN SALES AND DISTRIBUTION” is the outcome of my sincere effort. This
training Project Report is being submitted by me at WEBCOM
TECHNOLOGIES, New Delhi, for the partial fulfillment of the course
MBA+PGP (Industry Integrated), and the report has not been submitted to any
other educational institutions for any other purpose.
Date:
Signature
Page | 3
EXECUTIVE SUMMARY
This project report deals with the use of SAP SD module for the sales and
distribution in any organization. It contains the definition of the, enterprise
structure, sales organization, sales order cycle. In enterprise structure we
define the company, company code, sales area and shipping point and the
assignment of these areas with the company code. We also define the
distribution channel; division .Integration of subgroups is done. In sales order
cycle, we show how the sales process takes place in any organization.
In this report we also show all related transaction codes and path in the
enterprise structure, master data, sales document style, sales order cycle. We
have also given the different screen shots of different paths and features.
Page | 4
TABLE OF CONTENT
CHAPTERS PARTICULARS PAGE NO.
1. INTRODUCTION
1.1. SAP HISTORY
1.2. SAP ADVANTAGES
1.3. CURRENT PRODUCTS 7- 15
1.4. ORGANIZATIONAL LANDSCAPE
1.5. ASAP METHODOLOGY
1.6. SUCCESS OF SAP
2. MASTER DATA
2.1. ENTERPRISE STRUCTURE 16-41
2.1.1. DEFINITIONS
2.1.2. ASSIGNMENTS
2.1.3. BUSINESS AREA ASSIGNMENTS
3. MATERIAL MASTER DATA
3.1. MATERIAL MASTER
3.2. MATERIAL TYPE
3.3. USES 42-50
3.4. DIFFERENT TYPES OF MATERIAL AVAILABLE
3.5. LOADING GROUP
3.6. TRANSFER OF GOODS
3.7. TO SEE YOUR STOCKS
4. CUSTOMER MASTER DATA
4.1. PURPOSE
4.2. FEATURES
4.3. USES
4.4. DEFINE ACCOUNT GROUP WITH SCREEN LAYOUT
4.5. ASSIGN NUMBER RANGES TO CUSTOMER ACCOUNT GROUP 51- 58
SET UP PARTNER DETERMINATION
4.6. DEFINING PARTNER FUNCTIONS
4.7. CREATE CUSTOMER
4.8.
5. SHIPPING POINT DETERMINATION 59-60
5.1. SHIPING POINTS
Page | 5
6. PRICING AND CONDITION

6.1. DEFINE CONDITION TABLE
6.2. DEFINE ACCESS SEQUENCE
6.3. DEFINE CONDITION TYPES 61-67
6.4. DEFINE AND ASSIGN PRICING PROCEDURE
7. SALES DOCUMENT STYLE
7.1. ASSIGN SALES AREA TO SALES DOC TYPES 68-71
8. SALES ORDER CYCLE
8.1. INQUIRY
8.2. QUOTATION
8.3. ORDER
8.4. CONTACT 72-79
8.5. SCHEDULING AGREEMENT
8.6. OUTBOUND DELIVERY
8.7. BILLING
9. CONCLUSION
10. LIMITATION
11. BIBLIOGRAPHY
Page | 6
1. INTRODUCTION
SAP, started in 1972 by five former IBM employees in Mannheim, Germany, states that it is the
world's third-largest independent software vendor. The original name for SAP was German: System,
Anwendungen, and Produkte. It means "Systems Applications and Products." The goal of the company
was to provide large enterprise customers with the ability to interact with a corporate database in real-
time. Today, the company states that its goal is "to offer the industry's most comprehensive portfolio of
business performance and optimization solutions for companies of all sizes."
SAP's first software application was a financial accounting software suite that ran on a mainframe and
was known for its stability. It eventually became known as the R/1 system. The "R" stands for real-time.
During the 1980s, the company went international, and the second iteration of the R system (R/2)
accommodated different languages and currencies. In the 1990s, the third iteration (R/3) moved from the
mainframe to a client/server three-tier architecture composed of a database, software applications and a
common graphical user interface (GUI). SAP used the name R/3 until the 5.0 release. At that time the
name was changed from R/version to ERP Central Component (ECC). The most current version as of
November 2009 is ECC 6.0.
When the Internet became pervasive, SAP responded by providing companies with the software they
needed to sell goods and services online. Their product portfolio got a Web interface and was rebranded
MySAP.com. My SAP was designed to be a corporate Web portal with role-based permissions for
employees. The company promoted how SAP "solutions" could link commerce conducted over the
Internet (e-commerce) with traditional bricks and mortar commerce to provide one seamless view of the
business. Next came SAP Net Weaver, the company’s development and integration platform and
middleware component, and Business Suite, a bundling of SAP’s enterprise resource planning (ERP),
customer relationship management (CRM), supply chain management (SCM), product lifecycle
management (PLM) and supplier relationship management (SRM) applications. In 2008, SAP purchased
Business Objects, a French enterprise software company that specializes in business intelligence (BI),
which marked a major change in the company’s BI strategy, which was previously focused around
SAP's Business Explorer tools.
Page | 7
1(a).SUMMARY OF THE CHAPTERS:

 CHAPTER 1: General information regarding SAP. The history, advantages, the methodology to
implement SAP etc are discussed in this chapter.
 CHAPTER 2: The complete structures of a company, the business areas and sub areas, the
plants, storage location etc are mentioned in this chapter.
 CHAPTER 3: This chapter contains the detail regarding how to create material, how to see our
stocks etc.
 CHAPTER 4: Here in this chapter the uses, features, purpose of a customer and other
information regarding the customer and how to create and maintain customers are discussed in
detail.
 CHAPTER 5: The detail regarding the shipping points and the determination of shipping points
are introduced in this chapter.
 CHAPTER 6: The pricing strategies and the conditions for pricing that is the discounts, rebates
etc are calculated here and how to deal with these , the procedures are mentioned in this chapter.
 CHAPTER 7: This chapter contains the integration of sales order and the sales document types
are done here.
 CHAPTER 8: This chapter contains the full sales cycle that takes in a company. The creation of
inquiry, quotation, order, delivery and billing and the post order procedure are discussed in
detail.
 CHAPTER 9: The conclusions regarding the project are written here.
 CHAPTER 10: The limitation of SAP and the project is written here.
 CHAPTER 11: The references of the screen shots and the sources of the documents are
mentioned here.
1(b).PRIMARY OBJECTIVE:
To learn and understand the process of sales and distribution of a company. And also to understand
how to create integrate and the different documents and orders.
1(c).SECONDARY OBJECTIVE:
 To use SAP in future.
Page | 8
 To work in a project of SAP in real life environment.
1.1. SAP HISTORY:
 FROM START-UP SOFTWARE VENDOR TO GLOBAL MARKET LEADER
Over the course of three decades, SAP has evolved from a small, regional enterprise into a world-class
international company. Today, SAP is the global market leader in collaborative, inter-enterprise business
solutions. The company now employs more than 47 598 people, whose commitment and innovative
spirit pace our future success.
 The 1970s: A Real-Time Vision
In 1972, five former IBM employees – DietmarHopp, Hans-Werner Hector, HassoPlattner, Klaus
Tschira, and Claus Wellenreuther – launch a company called Systems Applications and Products in Data
Processing in Mannheim, Germany. Their vision: to develop standard application software for real-time
business processing.
One year later, the first financial accounting software is complete, forming the basis for the continuous
development of other software components in what later came to be known as the "R/1 system." "R"
stands for real-time data processing.
By the end of the decade, intensive examination of SAP's IBM database and dialog control system leads
to the birth of SAP R/2.
 The 1980s: Rapid Growth
SAP moves into the company's first building on Max-Planck-Strasse in an industrial park in Walldorf,
near Heidelberg. Our software development area and its 50 terminals are all now under one roof. Fifty of
the 100 largest German industrial firms are already SAP customers.
The SAP R/2 system attains the high level of stability of the previous generation of programs. Keeping
in mind its multinational customers, SAP designs SAP R/2 to handle different languages and currencies.
With this and other innovations in SAP R/2, SAP sees rapid growth.
Page | 9
By the middle of the decade, SAP founds its first sales organization outside Germany, in Austria. The
company makes its first appearance at the CeBIT computer fair in Hanover, Germany. Revenues reach
DM 100 million (around $52 million), earlier than expected.
In August 1988, SAP GmbH becomes SAP AG. Starting on November 4, 1.2 million shares are listed on
the Frankfurt and Stuttgart stock exchanges.
Germany's renowned business journal, manager magazine, names SAP its Company of the Year – a
distinction we would receive twice more in the next few years.
With the founding of subsidiaries in Denmark, Sweden, Italy, and the United States, SAP's international
expansion takes a leap forward.
 The 1990s: A New Approach to Software and Solutions
SAP R/3 is unleashed on the market. The client-server concept, uniform appearance of graphical
interfaces, consistent use of relational databases, and the ability to run on computers from different
vendors meets with overwhelming approval. With SAP R/3, SAP ushers in a new generation of
enterprise software – from mainframe computing to the three-tier architecture of database, application,
and user interface. To this day, the client-server architecture is the standard in business software.
A growing number of subsidiaries are managed out of Walldorf. The new Sales and Development
Center in Walldorf officially opens it doors. It symbolizes the global success of the company. In our
twentieth year, our business outside Germany exceeds 50 percent of total sales for the first time.
By 1996, the company has earned 1,089 new SAP R/3 customers. At the end of the year, SAP R/3 has
been installed in more than 9,000 systems worldwide.
SAP celebrates its twenty-fifth anniversary in 1997 and now employs approximately 12,900 people. We
continue to strengthen our industry focus and build more and more industry-specific solutions. Henning
Kagermann becomes Co-Chairman and CEO of SAP AG with HassoPlattner. On August 3, 1998, the
letters S-A-P appear for the first time on the Big Board at the New York Stock Exchange (NYSE), the
largest stock exchange in the world.
As the decade draws to a close, HassoPlattner, Co-Founder, Co-Chairman, and CEO announces the
mySAP.com strategy, heralding the beginning of a new direction for the company and our product
portfolio. mySAP.com links e-commerce solutions to existing ERP applications, using state-of-the-art
Web technology.
 The 2000s: Innovation for the New Millennium
With the Internet, the user becomes the focus of software applications. SAP develops SAP Workplace
and paves the way for the idea of an enterprise portal and role-specific access to information.
Page | 10
Currently, more than 12 million users work each day with SAP solutions. There are now 140,000
installations worldwide, More than 2,400 certified partners, over 25 industry-specific business solutions,
and more than 75,000 customers in 120 countries. SAP is the world's third-largest independent software
vendor.
With service-oriented architecture and the underlying integration and application platform SAP
NetWeaver, SAP is providing our customers with solutions for end-to-end business processes. With
SAP NetWeaver, your company can integrate people, information, and processes within the company
and beyond.
To further demonstrate our commitment for ongoing innovation, growth, and market leadership, SAP
acquired Business Objects in 2008. Together, SAP and Business Objects, an SAP company, offers the
industry's most comprehensive portfolio of business performance and optimization solutions for
companies of all sizes.
1.2. SAP ADVANTAGES:

Functionality:The R/3 System offers you a software solution that covers all commercial processes
and transactions commonly occurring in a company or group of companies.
• Integration: All work processes within a company or group of companies are linked through data
and functions using the R/3 System.
• User Friendliness:The R/3 System has a uniform graphical user interface for all application
areas.
• Individual Solutions:System-controlled customizing procedures allow you to create solutions

from a wide variety of prepared application variants to satisfy individual requirements.
• Flexible Structure: Whether in a departmental organization or on the warehouse or factory floor,

change is the only facet of your business that will not vary. Adaptability must be universal, and the R/3
System’s flexible structure and extensive integration helps make that easier.
• Enterprise-Wide Integration:SAP’s enterprise-wide R/3 System solutions meet the needs of

constantly changing, continually evolving businesses. The R/3 System’s application components are
fully integrated. Transaction-related process chains trigger the next activity as needed from engineering
to materials management, to production planning, to sales and distribution. The R/3 System’s full
integration pulls your enterprise together, promoting data access, flexibility, and productivity. No other
Page | 11
product or suite of products provides the R/3 System’s functional links between processes that multiply
the power of each person’s work.
• Real-Time Information:The R/3 System’s ability to “drill down” to whatever level of detail you
need is legendary. More than any other product, the R/3 System provides up-to-the-minute, real-time
information wherever and whenever you need it.
• Mission-Critical Business Processes:SAP has more than 20 years of experience designing

sophisticated application software for backbone and mission critical business processes. Nine of the top
ten Fortune 500 companies use SAP software. SAP developed most of the R/3 System’s functionality in
close cooperation with these customers. Consequently, it has integrated the best business practices of the
world’s most successful companies into the R/3 System. The R/3 System’s business processes are
flexible, pragmatic and well documented. Today they form a widely acknowledged standard for
Business Process Reengineering (BPR).
• Best of Breed:Users want standard software as well as standard business processes and guidance on
how to implement them successfully. With the R/3 System you get the “best of breed” for all common
business processes. You do not need to compromise on flexibility. If you need or want to fine tune or
tailor your R/3 System, the capability is there.
• Enterprise-wide three-tiered architecture:The R/3 System remains the only enterprise-wide,

three-tiered architecture. The R/3 System’s three-tiered client/server architecture separates the system
into areas devoted to database, application functionality, and desktop presentation. This structure
promotes maximum flexibility, freedom of application component choice and the ability to change and
add to the system as yourorganization grows. The development of the Internet, including the World-
Wide Web, promises to make dramatic changes in communications between businesses and customers.
SAP is working with several partners to develop enhanced Internet extensions for the R/3 System.
• Concurrent engineering:Concurrent engineering cuts time-to-market by stacking up business

processes whenever functions can take place concurrently rather than consecutively. The R/3 System’s
flexibility and integration help you form the real-time workflow application links required for
concurrent engineering.
• Lean Implementation:The R/3 System promotes lean implementation through its modular
structure. By selecting key portions of the R/3 System for first-time implementation, and minimizing
customization, new users bring the full power of the R/3 System to address their business issues with
great speed, at a reasonable cost. Once running, the R/3 System makes it easy to add more functional
pieces. Tools on various system levels allow you to fine tune all R/3 System functional modules.
Gradually adding functionality makes core solutions available sooner without sacrificing long-term
application muscle.
Page | 12
• Desktop Integration:Desktop integration in the R/3 System means that whenever you want data
moved into a desktop PC application, it is a mouse-click away. Download or export a file to your PC’s
hard drive and then open it in your favorite spreadsheet or word processor. No awkward or failure-prone
communications between hardware or to hinder hinders your productivity.
• Online Integrated Graphics:Online integrated graphics in the R/3 System save you time and
effort, while making your information more meaningful. From most locations in the R/3 System, you
can instantly create full-color 2-D or 3-D graphics from your data. If you change any data, you can
instantly see it affect the graphics you have selected. You can also use your mouse to change graphics
manually.
1.3.CURRENT PRODUCTS:
• SAP Net Weaver - service-oriented technology platform (SOA) for integrating information and
business processes across diverse technologies and organizational structures. Net Weaver provides the
foundation for other SAP software bundles.
• SAP Business Suite - software applications for large organizations and international corporations.
The applications support core business operations such as supply chain management, warehouse
management, sales, customer relationship management and administrative functions. SAP offers
software for 25 vertical industries, including banking, insurance, chemicals, and healthcare, retail and
consumer products.
• SAP Business All-in-One solutions, SAP Business by Design and SAP Business One - software
products that address the needs of small and mid-market companies.
1.4. ORGANIZATIONAL LANDSCAPE:

They system landscape basically is the set-up or arrangement of your SAP servers. Ideally, in an SAP
environment, a three-system landscape exists. A three-system landscape consists of the Development
Server-DEV, Quality Assurance Server-QAS and the Production Server-PROD. This kind of set-up is
not primarily designed to serve as server clusters in case of system failure, the objective to enhance
"configuration pipeline management".
Page | 13
Development Quality Production

Server Server Server
1. Development Server - It is the server where the consultants do the customization as per the
company's requirements.
2. Quality server -It is the servers where the core team members test the customization.
3.Production server -It is the server where live data is recorded.
At this juncture, it is important to state that a test system - Sandbox can also exit separately. The essence
of the sandbox is to test the configuration of the business processes of a company, especially at the
inception of the project (before the Business Blue Print is signed). It can also serve as a practice
environment, even after go-live.
Pipeline is the environment where the configuration in the development system is moved to the quality
assurance system and finally to the production system. The whole idea is to ensure that the configuration
of these systems is in sync at any point in time. Suffice to say that, configuration/changes are first made
in the Development system, thoroughly tested in the Quality Assurance system before been loaded into
the production (Live) system.
This approach throws up the transport management system concept. Transport management system is
the coordination of the movement of objects and configuration changes from the development system to
the Quality Assurance system and then to the Production system. At times, this sequence of movement is
not possible, especially in cases where an SAP note mandates that changes be made directly on the
production system.
In such rare cases, objectively confirm that the change transport cannot be performed. Very likely, your
system must have been configured to "not modifiable" (a system locking strategy that enforces the three-
system landscape change transport rule); unlock the system by changing the global setting option
to "modifiable" using transaction SE03. After you have done that, effect the change(s) on the system.
Page | 14
Immediately lock the system back by changing the global setting option to "not modifiable" using
transaction SE03. Replicate the changes on the other system. Note that transaction SCC4 can also be
used to lock the system so that client dependent and independent configuration changes are not carried
out directly on the production system.
By and large, the SAP system landscape ensures that the integrity of data is enhanced via enforcing a
controlled configuration changes effect on the target system - production.
1.5. ASAP METHODOLOGY(Accelerated System Application and

Products in Data Processing):
Accelerated SAP (ASAP) Methodology Prepared by Arun Prasad C R. Since Companies who
implement they will incorporate their quality process with standard ASAP methodology.
ASAP methodology means nothing but standard process for implementation of SAP, It consists of 5
phases.
1. Project preparation - Consists of identifying team members and developing strategy
2. Business Blue print - Consists of identifying the client current process, requirement and how SAP
provides solution. Consists of detailed documentation
3. Realization -The purpose of this phase is to implement all the business and process requirements
based on theBusiness Blueprint.
4. Final Preparation - The purpose of this phase is to complete testing, end-user training,
5. Go live and Support– The purpose is to give end users proper training and support.
Page | 15
1.6.REASONS BEHIND SUCCESS OF SAP IN IMPLEMENTING

ERP:
1. SAP Labs is the research and development organization of the parent company. SAP has its
development organization spread across the globe. Many, but not all, labs locations are hosting SAP
Research groups.
2. SAP customer support, also called Active Global Support (AGS) is a global organization to provide
support to SAP customers worldwide.
3. User Groups are independent, not-for-profit organizations of SAP customer companies and partners
within the SAP Ecosystem that provide education to their members, influence SAP product releases
and direction, exchange best practices, and provide insight into the market needs
4. In 2007, the SAP User Group Executive Network (SUGEN) has been established to foster the
information exchange and best practice sharing among SAP User Groups and to coordinate the
collaboration with SAP for strategic topics.
5. Partnerships are core to SAP’s strategy and in its 35 years of history the network of software solution
providers, value-added resellers, distributors, technology and services partners has developed into a
broad ecosystem that is among the industry's largest.
2. MASTER DATA
2.1. ENTERPRISE STRUCTURE
From MM view, the typical enterprise structure can be seen as following image.
Page | 16
SAP enterprise structure is organizational structure that represents an enterprise in SAP R/3
system. It consists of some organizational units which, for legal reasons or for other specific business-
related reasons or purposes, are grouped together. Organizational units include legal company entities,
sales offices, profit centers, etc. Organizational units handle specific business functions.
We must set the enterprise structure correctly in the first place. The change of it usually requires a great
effort and very time consuming. To set it up correctly we must have a comprehensive knowledge about
the business processes and how to map it to SAP configuration.
A specific organizational unit is defined by a specific function or module in SAP. Company code is
defined by FI module. Plant is defined by Logistics function. Storage Location and Purchasing
Organization are defined by MM module.
In SD module we have to define Sales Organization, Distribution Channel, and Division. We have an
option whether to use Sales Office, Sales Group, and Sales Person or not.
Page | 17
Enterprise structure consists of following components:

1. Company
2. Company Code
3. Credit Control Area
4. Sales Organization
5. Distribution Channel
6. Division
7. Sales Office
8. Sales Group
9. Sales Person
10.Plant
11.Storage Location
12.Warehouse
2.1.1.DEFNITIONS:
2.1.1(a).COMPANY:
Page | 18
A company is an organizational unit in Accounting which represents a business organization

according to the requirements of commercial law in a particular country. In the SAP system,
consolidation functions in financial accounting are based on companies. A company can comprise one
or more company codes.
When you create a company you should bear in mind the following points relating to group
accounting:
 If your organization uses several clients, the companies which only appear as group-internal
business partners, and are not operational in each system, must be maintained in each client. This
is a precondition for the account assignment of a group-internal trading partner.
 Companies must be cataloged in a list of company IDs which is consistent across the group. The
parent company usually provides this list of company IDs.
 It is also acceptable to designate legally dependent branches 'companies' and join them together
as a legal unit by consolidation.
2.1.1(b).COMPANY CODE:
A Company Code is a unit included in the balance sheet of a legally-independent enterprise.
Balance sheets and Profit and Loss statements, required by law, are created at company code level.
The Company Code is the smallest organizational unit for which we can have an independent
Page | 19
accounting department within external accounting, for example, a company within a corporate
group (client). In SAP, a company code is represented by a unique 4-digit alpha-numeric for a
specific client.
PATH TO CREATE COMPANY CODE:
Transaction code SPRO

Path Easy access screen >> EC01 >> Save as >> Back to easy access
>> SPRO >> IMG Screen >> Enterprise structure >> Definition >>
Financial accounting >> Edit, Copy, Delete, Check Company Code >>
Edit Company code data >> Address >> Save >> Back >> Define
company
Company Lava mobile pvt ltd

Company Code Lava
2.1.1(c). PLANT:
A plant is the place of production or simply a collection of several locations of material stocks in close
physical proximity. A plant is represented by a unique 4-digit alpha-numeric for a specific client. Plant
Page | 20
is used in Material Management (MM), Production Planning (PP), and Plant Maintenance (PM) module.
A plant is assigned to one company code.
The plant is embedded in the organizational structure as follows:
 The plant is assigned to a single company code. A company code can have several plants.
 Several storage locations in which material stocks are managed can belong to a plant.
 A single business area is assigned to a plant and to a division.
 A plant can be assigned to several combinations of sales organization and distribution

channel.
 A plant can have several shipping points. A shipping point can be assigned to several plants.
 A plant can be defined as a maintenance planning plant
PATH TO CREATE PLANT:

Path Easy access screen >> IMG >> Logistics General >> Define, copy,
delete, check Plant >> Copy As >> Save >> Define Plant
Plant Lava plant

Plant Code Lava
2.1.1(d). DIVISION:
Page | 21
Division is a way to group materials or services. A wide range of materials or services can be divided
into divisions. A material or service is always assigned to just one division.
In SAP SD, the use of divisions allows us organize our sales structure around groups of similar products
or product lines. We can define a division-specific sales structure. Within a division, we can also carry
out statistical analyses or devise our own marketing strategies.
In order to adapt the functional scope of a division to the organization in your company, you should
process the following check list:
 Allocate a division to one or more sales organizations.
 Allocate a division to one or more distribution channels.
 Allocate a business area to a division from a plant. This way, business area account assignment
can be carried out for transactions in Materials Management. As of Release 3.0, the business area
is determined in Materials Management from the division and the valuation area.
 A material is always assigned to one division only.
 Define master data within a division for customers as well as your own conditions and pricing.
 Create shared customer master data and conditions, which apply to several divisions, using a
common division.
 Define sales offices for a division.
 Define for each sales document type that all items of a sales document must belong to the same
division.
 The items of a delivery or a billing document can belong to different divisions.
 The division is used as a selection criterion for lists of sales documents and the work list for
deliveries.
PATH TO CREATE DIVISION

Page | 22

Path Easy access screen >> IMG >> Logistics General >> Define, copy,
delete, check Division >> Define Division
Division Lava division

Division Code Lava
2.1.1(f). SALES ORGAIZATION:

Page | 23
Sales organization is the basic organizational element in SD. All sales documents are created for a
sales organization. Sales organization can be defined based on:
 Division of sales function of the company based on

 Geography or sub-businesses of the company
 Any other sales criteria. Sales organization is defined as a 4-digit alpha numeric code with
external numbering.
The above sales organizations have been created because of following considerations –
 Within a sales organization, you can define your own master data. This allows a sales
organization to have its own customer and material master data as well as its own conditions
and pricing.
 Define sales document types within a sales organization.
 A sales organization is the highest summation level (after the organizational unit Client) for
sales statistics with their own statistics currency.
 To sum it up, the zonal nature of the organization structure is mapped using sales
organizations.
Page | 24
PATH TO CREATE SALES ORGANISATION

Path Easy access screen >>IMG >> Enterprise structure >> Definition >> Sales
and Distribution >> Define, copy, delete, check sales organization >> Copy,
delete, check, sales organization >>
Define Sales Organization.
Sales Organisation Lava Sales org

Sales Organisation Code Lava
Page | 25
2.1.1(g). DISTRIBUTION CHANNEL:

Distribution Channel is an organizational unit that represents the channel through which the
materials or services reach the customer, such as wholesale channel, direct sale channel, retail channel,
etc.
A distribution channel can be assigned to one or more sales organizations.

In order to adapt the functional scope of a distribution channel to the organization in your company, you
should process the following check list:
 Allocate a distribution channel to one or more sales organizations.
 Allocate one or more plants to a distribution channel.
 Within a distribution channel, you can define master data for customers or materials as well as
conditions and pricing.
 Create master data for a representative distribution channel which is then also used in other
distribution channels.
 For a distribution channel, determine sales document types.
 Determine sales offices for a distribution channel.
 All items of a sales document belong to a distribution channel. The entire sales document is
therefore entered for a distribution channel.
 The items of a delivery can belong to different distribution channels.
 All items of a billing document belong to a distribution channel.
 The distribution channel can be used as a selection criterion in lists.
 You can determine the printer destination for messages differently for every distribution channel
on the basis of the sales and billing documents.
Page | 26
PATH TO CREATE DISTRIBUTION CHANNEL

Path Easy access screen >>IMG >> Enterprise structure >> Definition >>
Sales and Distribution >> Define, copy, delete, check Distribution
Channel >> Define Distribution Channel
Distribution Channel lava dist chnl

Distribution Channel Code Lava
Page | 27
2.1.1(h). STORAGE LOCATION:

A Storage Location is a storage area comprising warehouses in close proximity. A Storage Location is
represented by a unique 4-digit alpha-numeric for a specific plant. Material stocks can be differentiated
within one plant according to storage location (inventory management). Storage locations are always
created for a plant.A storage location is the place where stock is physically kept within a plant.
A storage location has the following attributes:
 There may be one or more storage locations within a plant.
 A storage location has a description and at least one address.
 It is possible to store material data specific to a storage location.
 Stocks are managed only on a quantity basis and not on a value basis at storage location level.
 Physical inventories are carried out at storage location level.
 A storage location can be assigned to a warehouse number in the Warehouse Management

System . You can assign more than one storage location to the same warehouse number within a
plant.
 Storage locations are always created for a plant.
Page | 28
PATH TO CREATE STORAGE LOCATION

Material Management >> Maintain Storage Location
Storage location Lava storage

Storage location code lava
Page | 29
2.1.1(i). SHIPPING POINT:

The shipping point is the highest-level organizational unit of shipping that controls your shipping
activities. Each outbound delivery in the SAP system is processed by one shipping point.
The shipping point can be a loading ramp, a mail depot, or a rail depot. It can also be, for
example, a group of employees responsible (only) for organizing urgent deliveries.
You assign a shipping point in the SAP System at plant level. A shipping point is a physical place and
should be near the delivering plant. More than one shipping point can be assigned to a plant.
We can also assign several plants to a shipping point in the SAP system.
In order to adapt the functional scope of a shipping point to the organization in your company, we
should process the following check list:
 The shipping point is the top level in the organization for shipping.
 A shipping point can be allocated to several plants.
 A shipping point can be divided into several loading points.
 A delivery is always initiated from exactly one shipping point. Thus, all items of a delivery
belong to one shipping point. Groups of deliveries also belong to exactly one shipping point.
 The shipping point can be proposed automatically during order processing depending on the
plant, loading group and shipping condition.
 A shipping point has an address.
 The shipping point is used as a selection criterion for lists of deliveries and the work list
deliveries.
 The shipping point is used as a selection criterion for processing deliveries like printing, picking
or goods issue.
Page | 30
PATH TO CREATE SHIPPING POINT

Logistics Execution >>Define, copy, delete Shipping Point >>
Define Shipping point
Shipping Point Lava Shipping Point

Shipping Point Code Lava
Page | 31
2.1.2.ASSIGNMENTS:
2.1.2(a).Assign Company Code to Company:-
Company Lava mobile pvt ltd

Company Code Lava
Page | 32
2.1.2(b). Assign Plant to Company Code:

 In the step "Assign plant to company code", you assign each plant to a company code.
 A plant can only belong to one company code.
PATH:

Path Easy access screen >> IMG>> Enterprise structure >> Assignment >>
Logistics General >>Assign Plant to Company.
Plant lava
Company Code Lava
Page | 33
2.1.2(c). Assign Sales Organization to Company Code:

You can use this step to define the allocation of sales organizations to company codes.
This establishes a link between the SD and FI systems. A sales organization belongs to just one
company code.
PATH:

Path Easy access screen >>IMG >> Enterprise structure >> Assignment >>
Sales and Distribution >>Assign Sales organization to Company code
Sales organization lava

Company Code Lava
Page | 34
2.1.2(d). Assign Distribution Channel to Sales Organization:

In this step, allocation of the distribution channels to a sales organization is done. In this case, as many
distribution channels as desired can belong to a sales organization. In addition, a distribution channel
can be valid for several sales organizations.
PATH:

Sales and Distribution >>Assign Distribution channel to Sales
Organization.
Page | 35

Distribution Channel Lava
2.1.2(e). Assign Division to Sales Organization:

In this step, you allocate as many divisions as desired to a sales organization. Any one
division can belong to several sales organizations.
PATH:

Sales and Distribution >>Assign Division to Sales Organization.

Division Lava
Page | 36
2.1.2(f). Assign Division to Distribution Channel:

PATH:

Set up Sales Area >>Assign Division to Distribution channel.
Distribution channel lava

Division Lava
Page | 37
2.1.2(g). Assign Sales Organization – Distribution – Plant:

PATH:

Path Easy access screen >>IMG >> Enterprise structure >> Assignment
>> Set up Sales Area >>Assign Sales Org. , Dist. Channel to Plant

Plant Lava
Page | 38
2.1.3.Business Area Account Assignment:

2.1.3(a).Define Rules By Sales Area:-
PATH:

Business Area Account Assignment >> Define Rules by sales area.

Division Lava
Page | 39
Rule 2
2.1.3(b).Assign Business Area to Plant and Division:-
PATH:

Business Area Account Assignment >> Assign Business Area to Plant
and Division.
Plant Lava
Business area 0001
Page | 40
2.1.3(c).Assign Business Area by Sales Area:-

PATH:

>> Business Area Account Assignment >>Assign Business Area to
Sales Area
Sales organization ANPH

Distribution cahnnel lava
Page | 41
Division Lava
Business Area 0001
2.1.3(d)Assign Shipping Point to Plant:-

PATH:

>> Logistics Execution >>Assign Shipping point to Plant
Shipping point lava

Plant Lava
Page | 42
3. MATERIAL MASTER DATA
Division is a field in the material master data (it can be input/edited on “Basic Data 1” view by
MM01/MM02 t-code). That’s why a material is always assigned to just one division.
A material can be sold through one or more distribution channels in one or more sales organization. To
allow it, we have to maintain the material master data for each combination of sales organization and
distribution channel.
We can set different data of a material for each combination sales organization and distribution channel,
such as: “minimal order quantity” and “minimal delivery quantity” data. By doing so, for example, a
material must be ordered by customer minimal 1000 PC for wholesale channel and 10 PC for retail
channel (assumed we only have one sales organization).
3.1. Material Master:

It is a Master file which contains information of a particular material, depending upon the views
selected from the user departments.
Different types of views available in Material Master Record are
1. Basic data 1 & 2
2.Purchasing
3.General plant data storage 1 & 2
4.Warehouse Management 1 & 2
5.MRP (Material required planning) 1,2,3,4
6. Accounting 1 & 2
7. Costing 1 & 2
8. Quality Management
9. Plant Stock
10. Storage Location Stock
11. Classification
12.Forecasting
13. Purchase Order Text
14. Foreign Trade: Import Data
Page | 43
3.2. Material Type:

It is a key that assigns the material to a group of materials such as Raw materials, trading goods. This
allows you to manage different materials in a uniform manner in accordance with your company's
requirements.
The Material type defines certain attributes of the material and has important control functions.
3.3.Use
When creating a material master record, the material type determines:
• whether the material number is assigned internally or externally
• from which number range interval the material number comes
• which screens are displayed
• the order in which screens are displayed
• which department-specific data is displayed for the user to enter.
3.4.Different Material Types available:

ROH - Raw Material
FERT - Finished Product
HALB- Semi finished Product
HAWA- Trading goods
DIEN - Services
ERSA - Spare Parts
PIPE - Pipeline material
LEIH - Returnable Packaging
HERS- Manufacturer Parts
FGTR - Drinks
FOOD- Foods
FRIP - Perishable Goods
Configurable materials (KMAT): Configurable materials are materials that can have different variants.

For example, an automobile can have different types of paintwork, trim, and engine.
Finished products (FERT): Finished products are produced in-house. Since they cannot be ordered by
Purchasing, a material master record of this material type does not contain purchasing data.
Non-stock materials (NLAG): Non-stock materials are not held in stock because they are consumed

immediately.
Non-valuated materials (UNBW): Non-valuated materials are managed on a quantity basis, but not by

value.
Page | 44
Packaging materials (VERP): Packaging materials are used to transport goods and come with the

goods free of charge. A material master record of this material type is managed on both a quantity basis
and value basis.
Raw materials (ROH): Raw materials are always procured externally and then processed. A material

master record of this type contains purchasing data, but not sales data since they cannot be sold.
Semi finished products (HALB): Semi finished products can be procured externally and manufactured
in-house. The company then processes them. A material master record of this material type can contain
both purchasing and work scheduling data.
Services (DIEN): Services can be performed internally or procured externally (outsourced). They

cannot be stored or transported.
Spare parts (ERSA): Spare parts are used to replace defective parts. They may be kept in stock. A
material master record of this material type can contain purchasing data, but not sales data.
PATH TO CREATE MATERIAL MASTER DATA
Transaction code MM01

Path Easy access screen >> Logistics>> Material Management >> Material
Master >> Material >> Create (General) >> Immediately
After following path, select Industry Sector & Material Type and Press Enter.When you create a
material master record, you are required to classify the material according to industry sector and material
type.
Industry Sector: Key that specifies the branch of industry to which the material is assigned.
Screen of creating Material
Page | 45
 Now select the required nine tabs as:

1. Basic Data 1
2. Basic Data 2
3. Sales: Sales Org. Data 1
4. Sales: sales Org. Data 2
5. Sales: General/ Plant Data
6. General Plant Data Storage 1
8. Accounting 1
9. Accounting 2
 Then Click on Organization levels select Views & Press Enter.
 Enter Plant & Storage Location then Press Enter.
 After entering the window will open containing nine required fields like basic data 1, basic data
2, storage location 1, storage location 2, general plant, accounting information etc.
Fields in different views in Material Master
1. Basic Data 1
 Material Description
 Basic Unit of Measure
 Material Group
Page | 46
 General item category

 Gross Weight
 Net Weight
 Volume etc
2. Basic Data 2
 Contains Design Drawing information.

 Plant
 Division
 Storage Location
5. Sales: General/ Plant Data 1
 Basic Unit of measure

 Storage location
 Plant
 Gross weight
 Net Weight
8. Accounting 1
 Basic Unit of Measure

 Price control
 Price unit
 Currency
 Moving & Standard Price
 Total Stock
 Total Value
 Division
9. Accounting 2
 After entering all the required information save the data and the material will be generated.
Screen of Material creation:
Page | 47
Page | 48
Material electronics
Industry sector Mobile
Material type Finished product
3.4.Loading Group:
After creating material use Transaction Code OMWD-Loading Group.
Screen of loading group
Page | 49
Loading Group 0001

Company code lava
3.5.Transfer (Posting) of Goods- MB1C

After loading group we have to transfer goods to the storage location and use the Transaction Code
MB1C.
Write Document and Posting dates and Movement type 501 and Enter.
Page | 50
Window will open write the Material and quantity and Enter and then save it. After that the document
will be posted and ten digits code will be generated.
Screen of transfer of goods
Transaction code /NMB1C

Document 4900026913
3.6.To See your Stock / MMBE:

- We can see our stock in the storage location by using the Transaction Code MMBE
- After filling the material, plant and Storage location click on Execute button, we can see our stock.
Screen to see the stock / MMBE:

Page | 51
4. CUSTOMER MASTER DATA

4.1.Purpose
Page | 52
In the SAP System, all business transactions are posted to and managed in accounts. You must create a
master record for each account that you require. The master record contains data that controls how
business transactions are recorded and processed by the system. It also includes all the information about
a customer that you need to be able to conduct business with him.
4.2.Features
Specifications made in master records are used:
 As default values when you post items to the account
For example, the terms of payment you specify in the master record are defaulted for document
entry.
 For processing business transactions
Account control data, such as the number of the G/L reconciliation account
For example, the dunning procedure, the date of the last dunning notice, and the address are
required for the automatic dunning process.
 For working with master records
You can prevent certain users from accessing an account by setting up authorization groups.
 For communication with the customer
For example, the address and telephone and fax numbers.
 For the sales department
Order processing, shipping, and billing data.
4.3.Define Account Groups with Screen Layout (Customers)
Page | 53
Determination of the account groups for customers is done here. Define reference account
groups for one-time accounts. Use these to control the fields of the one-time account screen so that, for
example, certain fields are displayed as required fields or are hidden.
When creating a customer account, specify an account group. You can specify a reference account group
under "Control" in the "General data" part of a one-time account's master data. If you do not specify a
reference account group, then, as previously, all fields of the one-time account screen are ready for input
during document entry.
The account group is used to determine:
 the interval for the account numbers
 whether the number is assigned internally by the system or externally by the user (type of
number assignment)
 whether it is a one-time account
 which fields are ready for input or must be filled when creating and changing master records
(field status)
PATH TO DEFINE ACCOUNT GROUP WITH SCREEN LAYOUT

Path Easy access screen >> SPRO >> IMG >> Financial Accounting >>
Account receivable and account payable >> Customer Account >>
Master Data >> Preparation for creating Customer master data >>
Define Account group with screen layout ( customers)
Steps:
 Find ZAG2 from positions and then copy as.
 Give your account group and name.
 Go to general data and double click and select address.
 Select name 1/ last name and tick the required entry tab.
 Select company code data, then account management and then tick required entry of
reconciliation account.
 Select payment transaction then terms of payment and then tick required entry.
 Select sales data, then sales and then tick required entry in pricing procedure.
 Select shipping then tick required entry of shipping conditions.
 Select billing then billing and incoterms and tick required entry in both.
Screen to create account group with screen layout

Page | 54
Account group lava

Name dheeraj
4.4.Assign Number Ranges to Customer Account Groups
Page | 55
In this step we assign the number ranges we created in the preceding step to the account groups for
customers. We can use one number range for several account groups.
PATH TO ASSIGN RANGES TO CUSTOMER ACCOUNT GROUP

Path Easy access screen >> SPRO >> IMG >> Financial Accounting >>
Account receivable and account payable >> Customer Account >>
Master Data >> Assign number ranges to customer account group
Screen to assign no. ranges to customer account group
Group lava
Name Dheeraj
Number range 02
4.5. Set up Partner Determination

Page | 56
In this activity, we define the rules that should be used to perform automatic partner determination.
1. Define the partner functions that differentiate the roles of partners in your system.
2. Define the partner determination procedure, and assign the key of the relevant partner object
to this procedure.
3. Assign the partner functions you define to the account groups.
When we create a customer master record, the SAP system proposes the allowed partner functions for
maintenance. The partners are copied from the sold-to party's customer master records into the sales
documents, according to the rules we have defined.
For partner determination edit the following:
 Partner function
 Allowed partners for each account group
 Function key conversion
 Partner object
 Partner determination procedures
 Assigning procedures
The following partner objects exist:
 Customer master record
 Sales document
o Header
o Item
 Delivery
o Header
 Shipment
o Header
 Billing document
Page | 57
o Header
o Item
 Contact
4.6.Defining Partner Functions

When defining a partner function, enter whether the partner is, for example, a customer, vendor,
customer employee, or your own employee. Depending on the partner function, the system expects to
enter a customer number, vendor number, a personnel number, or another number.
Parameters for a partner function:
 Partner function
 Partner type
 Error group
 Super ordinate roles
 Unique in customer master record
 Customer hierarchy type
 Role key conversion
Page | 58
PATH TO CREATE SET UP PARTNER DETERMINATION

Path Easy access screen >> SPRO >> IMG >> Sales and distribution >>
Basic function >> Partner determination >> Set up partner
determination >> Set up partner determination for customer master
Screen of set up partner determination:
Page | 59
4.7. Create Customer - /NXD01
4.7.1.Customer
Business partner from whom receivables are due as a result of services rendered. Examples of these
services are:
 Goods delivered
 Services performed
 Rights transferred
Customer master data is maintained on four tabs for the following three views:
 General data
o General data for customers
 Company code data
 Sales area data

A) Sales
B) Shipping
C) Billing document
D) Partner
Screen of creating Customer
Account group Uttam mobile buyer

Page | 60
Customer number 0000100167

5. SHIPPING POINT DETERMINATION
5.1. Shipping Points
In this menu option, you allocate the shipping points to the desired combinations of shipping condition
and loading group for each plant.
Shipping conditions:
01 – As soon as possible
10 – Immediately
PATH TO ASSIGN SHIPPING POINTS

Path Easy access screen >> SPRO >> IMG >> Logistics Execution >>
Shipping >> Basic Shipping function >> Shipping points and Goods
Receiving point determination >> Assign Shipping points
Screen to assign shipping points as shipping condition 01:
Page | 61
Screen to assign shipping points as shipping condition 10:
Page | 62
6. PRICING AND CONDITIONS

The Pricing function is a method of determining prices using the condition technique. SAP Enterprise
Buyer uses Pricing when purchase documents are being created, for example, when a shopping cart or
purchase order is created. The system automatically determines the gross price and any surcharges and
discounts that apply to a specific vendor according to defined conditions. The system uses the gross
price and these surcharges or discounts to determine the net price.
Pricing consists of the following elements:
 Condition Type
A condition type serves to differentiate between prices in the system. You can define a separate
condition type for each type of price, surcharge or discount that may arise in your business
transactions. The condition type defines, for example, a discount as a fixed amount or as a
percentage.
 Access Sequence
An access sequence is a search strategy with which the system looks for valid data for a specific
condition type. You can define an access sequence for each condition type. In Enterprise Buyer
the access sequences are predefined, changes are not intended to be made by customers.
 Condition Table
A condition table contains price information on a master data type, for example, on a product
master. If you define a product price or a special discount, for example, you create condition
records in the relevant condition table.
Page | 63
6.1.Define Condition Tables

In this IMG activity, we define price dependencies. We can make prices, surcharges, and discounts
dependent on almost all the fields in a document. We define these dependencies using the condition
tables. In a condition table, we define the combination of fields for which you can create condition
records.
PATH TO CREATE CONDITION TABLE

Basic function >> Pricing >> Pricing Control >> Define Condition
Table >> Create condition table
STEPS:
 Give any number between 599-999 in table column.

 Double click on second customer and material and then generate.
 Click on local object and then save.
Screen to create condition table
Page | 64
Condition Table no. 822
6.2. Define Access Sequences
The access sequence is a search strategy which the SAP System uses to search for condition
records valid for a condition type.
For example, you can define for a price that the SAP System first searches for a customer-specific
price and then for a price list price.
PATH TO DEFINE ACCESS SEQUENCES

Basic function >> Pricing >> Pricing Control >> Define Access
Sequence >> Maintain Access Sequence
Screen to define access sequences
Page | 65
Access sequence Lava

Name uttam access sequence
Account no. 13
6.3.Define Condition Types

Price elements are represented in the SAP system by condition types. Price elements can be, for
example, prices, surcharges, discounts, taxes or, freight, and are stored in the system in condition
records.
We can, for example, define whether a discount is calculated as a percentage or a fixed amount using
the condition type. We specify an access sequence in every condition type. Thus, you define which
fields the SAP system checks when searching for a valid condition record.
PATH TO DEFINE CONDITION TYPES

Basic function >> Pricing >> Pricing Control >> Define Condition
Types >> Maintain Condition Types
Page | 66
Screen of Condition Types
Condition types Lava

Name uttam Condition Type
6.4.Define and Assign Pricing Procedures

We define the pricing procedures in this step. In addition, you assign the pricing procedures to the
transactions by defining the following dependencies:
 Customer
 Sales document type
 Sales area
In the pricing procedure, we define which condition types should be taken into account and in which
sequence. During pricing, the SAP System automatically determines which pricing procedure is valid
for a business transaction and it takes the condition types contained in it into account one after the other.
Page | 67
The determination of the procedure depends on the following factors:
 Customer determination procedure
 Document pricing procedure
To determine the procedure, we allocate the customer determination procedure and the document pricing
procedure to a pricing procedure within a sales area.
PATH TO MAINTAIN PRICING PROCEDURE

Basic function >> Pricing >> Pricing Control >> Define and assign
Pricing Procedure >> Maintain pricing procedure
Screen of maintain pricing procedure:
Page | 68
STEP CONDITION TYPE DESCRIPTION

15 lava PRICE
16 K004 MATERIAL
17 K007 CUSTOMER DISCOUNT
PATH TO DEFINE PRICING PROCEDURE DETERMINATON

Basic function >> Pricing >> Pricing Control >> Define and assign
Pricing Procedure >> Define pricing procedure determination.
Page | 69
Screen of define pricing procedure determination:
Pricing procedure uttam pricing procedure

Condition types uttamCondition Types
7. SALES DOCUMENT STYLES

Three types of sales documents are:
1. Sales order document
2. Delivery document
Page | 70
3. Billing document
7.1. Assign Sales Area to Sales Document Types

In this menu option, we allocate the allowed order types to each sales area group.
PATH TO COMBINE SALES ORGANIZATION

Sales >> Sales document >> Sales document header >> Assign sales
area to sales document types >> Combine sales organization
Screen to combine sales organization
Reference sales organization ANPH
PATH TO COMBINE DISTRIBUTION CHANNELS

area to sales document types >> Combine Distribution Channels
Page | 71
Screen to combine distribution channels
Reference Distribution Channel Lava1
PATH TO COMBINE DIVISIONS

Page | 72
area to sales document types >> Combine Divisions
Screen to combine divisions
Reference divisions Lava1
PATH TO ASSIGN SALES ORDER TYPES PERMITTED FOR SALES AREAS

Page | 73
order types permitted for sales areas
Screen to assign sales order types permitted for sales areas:
Sales org Distribution Division Sales order types Description

channel
Lava Lava Lava OR Standard order
Lava Lava Lava RO Rush order
Lava Lava Lava IN Inquiry
Lava Lava Lava QT Quotation
Lava Lava Lava CS Cash sales
Lava Lava Lava NMS Quantity Contract
lava lava Lava DS Scheduling agreement
8. SALES ORDER CYCLE

Page | 74
8.1.INQUIRY
It is a customer request to the company for the quotation for distributing goods and services.
Creation of Inquiry (VA11) – A new Inquiry is created only when the authorized person at
Depot receives an Inquiry from an existing or new Non Trade Customer.
PATH TO CREAT INQUIRY
PATH Easy access screen >> Logistics >> Sales and

distribution >> Sales >> Inquiry >> Create
T- code VA11
Screen of creation of Inquiry:
Material mobile
Inquiry no. 10000130
8.2.QUOTATION
Page | 75
It is an offer to customer for specific area.
Creation of Quotation (VA21) – Quotation is created when an inquiry is received from a

customer.
PATH TO CREAT QUOTATION

distribution >> Sales >> Quotation >> Create
T- code VA21
Screen of creation of Quotation
Material Mobile
Quotation no./ Offer 20000131
8.3.ORDER
Page | 76
We need customer material information, price information about financial statement of items. Delivery
date and the quantity, and shipping information of customer.
1. Creation of Sales Order for a Trade Customer (VA01) – A Sales order is created when a
purchase order is got from the Trade Customer.
2. Creation of Sales Order with reference to a Quotation (Non-Trade customer) (VA01) – A
Sales Order created when a Purchase Order received from the Customer w/out reference to a
Quotation
3. Creation of Sales Order for delivery of material from another depot (VA01) – A delivery
from another Depot directly to Customer shall be created on the Decision of the Depot In charge.
8.3.1.ORDER PROCESS
 Customer and material information.

 Price information about financial statement of an item.
 Delivery date and Quantity.
 Shipping information.
 Billing information.
8.3.2.Parties involved in Order process
1. Sold to Party: Party who placed the order.

2. Ship to Party: Party who receives the order.
3. Bill to Party: Party who receives the invoice.
4. Pay to Party: Party who pay the bill.
PATH TO CREAT ORDER

Page | 77
PATH Easy access screen >> Logistics >> Sales and distribution >>
Sales >> Order >> Create
T- code VA01
Screen of creation of Order
Material Mobile
Standard order 8334
8.4.OUTLINE AGREEMENT
Page | 78
It can be of two types:
1. Scheduling agreement
2. Contract
8.4.1.CONTRACT:
Contract is where you have a contract with the vendor, may be a for a predetermined quantity or
predefined value. So every time you need the material, we need to make PO ref the contract asking for
the delivery of the material. In such instance when PO is ref with contract it’s called contract release
orders or call off orders.
PATH TO CREATE CONTRACT

distribution >> Sales >> Contract >> Create
T- code VA41
Screen of creation of Contract:
Material mobile
Quantity contract 40000106
Page | 79
8.4.2. SCHEDULING AGREEMENT

Scheduling agreement is a long term purchase agreement, where you will keep
issuing the delivery schedules whenever there is a change in requirement or at predetermined
time intervals. The delivery schedule can be on hour/daily/weekly/monthly basis. But it will
contain different zones viz. firm/tradeoff/Forecast. Firm zone schedules are confirmed
requirement and need to be taken by ordered party. Tradeoff zone requirement is to purchase the
raw materials and ordering party is liable to pay raw material cost, in case of requirement
cancellation. Forecast zone requirement is to help the vendor to plan his requirements.
SA is also an agreement with the vendor for the supply of material, may be a quantity or value.
The delivery dates will be maintained in ME38 ref the SA which are called delivery schedules.
So you can maintain the delivery schedule and communicate the vendor on Forecast basis or JIT
basis. And when you need some more material then will only create SA deliveries using ME38.
SA could be of 2 types:- without release documentation-system will transmit the delivery info to
the vendor once you save the document.
PATH TO CREATE SCHEDULING AGREEMENT
PATH Easy access screen >> Logistics >> Sales and distribution
>> Sales >> Scheduling agreement >> Create
T- code VA31
Screen of creation of Scheduling agreement
Material Mobile
Scheduling agreement 30000068
Page | 80
8.5.OUTBOUND DELIVERY
We can create an outbound delivery in a shipping point for orders that are due for delivery.
The SAP System copies the relevant data from the order (one or many order) to the outbound delivery.
We can create one or several outbound deliveries from the order. We can also combine items from
several orders into one outbound delivery.
Delivery Process:
1. Order number
2. Confirmation date
3. Shipping point
PATH TO CREATE DELIVERY
PATH Easy access screen >> Logistics >> Sales and distribution >>
Shipping and Transportation >> Outbound Delivery >> Create
>> Single document ( with reference to sales order
T- code VLOIN
Screen of creation of Delivery
Order 8334
Page | 81
Delivery number 80011378
8.6.BILLING
Billing represents the final processing stage for a business transaction in sales and distribution.
Information on billing is available at every stage of order processing and delivery processing.
This component includes the following functions:
 Creation of
I. Invoices based on deliveries and services.
II. Issue Debit and Credit memo.
III. Pro forma invoices.
 Cancel billing transactions.
 Comprehensive pricing functions.
 Issue rebates.
 Transfer billing data to Financial Accounting (FI).
PATH TO CREATE BILLING
PATH Easy access screen >> Logistics >> Sales and distribution
>> Billing >> Billing document >> Create
T- code VLOIN
Screen of creation of Billing
Material Mobile
Billing document 90033130
Page | 82
9.CONCLUSION
This project helped us to understand the use of SAP in sales and distribution.
The entire sales order cycle i.e. the creation of inquiry, quotation, order,
delivery etc could be learnt. The creation of a company and the integration of
various departments of the company could be understood while working in
this project. This project helped us to differentiate between the manual system
and the SAP integrated system in a company.
 A Single Information System in One Enterprise.

 Improve Collaboration among Different Departments.
 Improve Operation Effectiveness and Efficiency.
 SAP provides user friendly environment, integration of data, flexible
structure, and real time information for the users.
 The best part of SAP is accessibility. Data can be access any time
whenever required.
 System-controlled customizing procedures allow you to create solutions
from a wide variety of prepared application variants to satisfy individual
requirements.
Page | 83
10.LIMITATION AND RECOMMENDATION

The limitations of SAP are:
 High understanding of the process is required.

 Time consuming for implementation.
 Huge documentation.
 GAP Analysis is to be done before implementation.
 Requires highly qualified staff for assistance.
 Large amount of money is involved.
The limitations of this project are:
Since it was not a real life environment there was a lot of problems which
were faced. Some of them are:
 Only 1 server was there so very often data was getting locked.
 Lot of user names were used but the problem could not be solved.
 It was time consuming because of 1 server.
 Many definitions had to be copied from the existing information
available in the server.
 It was possible for anybody to delete any of the information created by
us.
The recommendation for this project is:
As we were working in a demo server all the above problems were
faced. So according to me while we work in the real life environment these
problems will not be faced. But to enhance the effectiveness of the training
it should be done in the real life environment. This we can say because at
that time we will have different user names and id’s so the other problems
will also be solved.
Page | 84
11.BIBLIOGRAPHY
I have gathered all the information from the SAP Help Menu & various
websites like:
 www.sap.com
 www.thespot4sap.com
 www.sap-img.com
 www.sdn.sap.com
other than these I have gathered the information from my class notes and
other researches and papers available on SAP in the internet.
Page | 85

SAP SD Report on Sales Process, Master Data & Usage

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

SAP SD Report on Sales Process, Master Data & Usage

Enviado por

Direitos autorais:

Formatos disponíveis

The dissertation report of SAP in sales and distribution and usage of SAP in sales and distribution

SUBMITTED TO: SUBMITTED BY:

Ms. Sweta Seth.

6. PRICING AND CONDITION

1(a).SUMMARY OF THE CHAPTERS:

 To work in a project of SAP in real life environment.

1.1. SAP HISTORY:

 FROM START-UP SOFTWARE VENDOR TO GLOBAL MARKET LEADER

 The 1970s: A Real-Time Vision

 The 1980s: Rapid Growth

 The 1990s: A New Approach to Software and Solutions

 The 2000s: Innovation for the New Millennium

1.2. SAP ADVANTAGES:

• Individual Solutions:System-controlled customizing procedures allow you to create solutions

• Flexible Structure: Whether in a departmental organization or on the warehouse or factory floor,

• Enterprise-Wide Integration:SAP’s enterprise-wide R/3 System solutions meet the needs of

• Mission-Critical Business Processes:SAP has more than 20 years of experience designing

• Enterprise-wide three-tiered architecture:The R/3 System remains the only enterprise-wide,

• Concurrent engineering:Concurrent engineering cuts time-to-market by stacking up business

1.4. ORGANIZATIONAL LANDSCAPE:

Development Quality Production

3.Production server -It is the server where live data is recorded.

1.5. ASAP METHODOLOGY(Accelerated System Application and

1. Project preparation - Consists of identifying team members and developing strategy

1.6.REASONS BEHIND SUCCESS OF SAP IN IMPLEMENTING

Enterprise structure consists of following components:

A company is an organizational unit in Accounting which represents a business organization

Transaction code SPRO

Company Lava mobile pvt ltd

The plant is embedded in the organizational structure as follows:

 A single business area is assigned to a plant and to a division.

 A plant can be assigned to several combinations of sales organization and distribution

 A plant can be defined as a maintenance planning plant

PATH TO CREATE PLANT:

Transaction code SPRO

Plant Lava plant

 Allocate a division to one or more sales organizations.

 Allocate a division to one or more distribution channels.

 A material is always assigned to one division only.

 Define sales offices for a division.

 The items of a delivery or a billing document can belong to different divisions.

PATH TO CREATE DIVISION

Transaction code SPRO

Division Lava division

2.1.1(f). SALES ORGAIZATION:

 Division of sales function of the company based on

PATH TO CREATE SALES ORGANISATION

Transaction code SPRO

Sales Organisation Lava Sales org

2.1.1(g). DISTRIBUTION CHANNEL:

A distribution channel can be assigned to one or more sales organizations.

 Allocate a distribution channel to one or more sales organizations.

 Allocate one or more plants to a distribution channel.

 For a distribution channel, determine sales document types.

 Determine sales offices for a distribution channel.

 The items of a delivery can belong to different distribution channels.

 All items of a billing document belong to a distribution channel.

 The distribution channel can be used as a selection criterion in lists.

PATH TO CREATE DISTRIBUTION CHANNEL

Transaction code SPRO

Distribution Channel lava dist chnl

2.1.1(h). STORAGE LOCATION: