Sales Order Creation Using SAP Web Dynpro

BITS ZG629T: Dissertation

by
Rohit Gupta
2013HT12230
Dissertation work carried out at
Altimetrk India Pvt Ltd, Bangalore

Submitted in partial fulfillment of M.S. Software Systems

Raja Premkumar (Project Manager)
Zieta Technologies Pvt Ltd, Bangalore

BIRLA INSTITUTE OF TECHNOLOGY & SCIENCE

PILANI (RAJASTHAN)
April, 2015

CERTIFICATE

This is to certify that the Dissertation entitled Sales Order

creation using SAP Web Dynpro and submitted by Rohit Gupta
having ID-No. 2013HT12230 for the partial fulfillment of the
requirements of M.S. Software Systems degree of BITS, embodies
the bonafide work done by him/her under my supervision.

Signature of the Supervisor

Place :BANGALORE
Date :30th March
Raja Premkumar
Project Manager
Zieta Technologies Pvt
Ltd, Bangalore

ABSTRACT
BITS ID No.

: 2013HT12230

NAME OF THE STUDENT

: ROHIT GUPTA

EMAIL ADDRESS

: rohit100187@gmail.com

STUDENTS EMPLOYING

: ALTIMETRIK INDIA PVT LTD,BANGALORE

ORGANIZATION & LOCATION

SUPERVISORS NAME

: RAJA PREMKUMAR

SUPERVISORS EMPLOYING

: ZIETA TECHNOLOGIES PVT LTD,BANGALORE

ORGANIZATION & LOCATION

SUPERVISORS EMAIL ADDRESS: raja.premkumar@zietatech.com
DISSERTATION TITLE

: SALES ORDER CREATION USING SAP WEB DYNPRO

Signature of the Student

Name : ROHIT GUPTA
Date: 30th March
Place: Bangalore

Signature of the Supervisor

Name: Raja Premkumar

Date: 30th March
Place: Bangalore

Acknowledgement
This project would not have been possible without the kind support and help of many
individuals and organizations. I would like to extend my sincere thanks to all of them.

I am highly indebted to Mr. Raja Premkumarfor his guidance and constant supervision
as well as for providing necessary information regarding the project & also for his
support in completing the project.

I would like to express my gratitude towards Mr. MahalingamUmayanan for his kind cooperation and encouragement which helped me in completion of this project.

I would like to express my special gratitude and thanks to industry persons for giving
me such attention and time.

My thanks and appreciations also go to my colleague in developing the project and

people who have willingly helped me out with their abilities.

Table of Contents
1. Chapter 1: Introduction
2. Chapter 2: Sales and Distribution Overview
3. Chapter 3: Introduction to SAP SD Module
4. Chapter 4: Creating Sales Order via SAP Netweaver
5. Chapter 5: Creating Sales Order via SAP Web Dynpro
Summary

Chapter 1
Introduction
Altimetrik is a Business Transformation and Technology Solutions
Partner to Global Enterprise Customers in the areas of Digital,
Connected Solutions, Consumer Technologies and Enterprise
Integration.
Delivering Innovation as part of the partnership promise, we partner
with our customers to transform their IT and Business capabilities to
address the above trends proactively, while accelerating the
solution delivery with a unique Idea-2-Deploy Methodology.
We strongly believe that experience-led consumer behavior will lead
the way in the future transformation of businesses and are investing
heavily in researching and building solutions and capabilities which
are likely to catalyze this transformation. Headquartered in
Southfield, Michigan (USA), we are building a rapidly growing global
workforce of high-caliber talent across our development locations in
New York City, Bangalore (India), Chennai (India) and Montevideo
(Uruguay).
Company Overview - Altimetrik, IT Services Company, SAP
Solutions
Altimetrik is a SAP Services partner since 2003, Altimetrik delivers
SAP consulting, SAP implementation, SAP integration and post-SAP
implementation services for its customers. Our SAP Support
services cover the entire SAP systems spectrum of services
spanning from configuration set up, customization/enhancement of
existing SAP functionality, and post-SAP implementation support, to
Business Process Analysis (BPA)/Gap Analysis and Business Process
mapping.

AltimetriksSAP Competency includes Consultants who are highly

skilled with high end cutting edge new dimension product
experience. Altimetrikleverages their skills and opportunities to
provide the best solutions to the customer.
1

Altimetrik addresses the process Needs of all customers, offering

wide range of end-to-end Solutions viz
SAP Consulting Services
SAP Implementation & Enhancement Services
SAP Upgrade from One Version to Higher Version
SAP Support & maintenance Services
SAP Business Intelligence (BI) Consulting Services
SAP Business One Implementation, Enhancement, Support &
Maintenance
SAP Security Maintenance Services
SAP Consulting Services
Altimetrik SAP Competency has the best consultants with cutting
edge SAP expertise to handle any kind of project of any complexity
and volume. We follow the Best practice procedures to address all
the requirements of the customers in an Offshore/onsite Model
An indicative list of services we offers you while being your
consulting partner, are:
Strategic consulting: Our business consultants bring in proven
methodologies, industry specific process flow maps, a host of tools
and accelerators to quickly scrutinize your existing processes and
suggest improvements guaranteeing an upfront performance
enhancement.
Feasibility study and solution assessment: Understanding that
every business poses a unique set of requirements, our consultants
conduct a regimented product evaluation study interviewing key
user communities and keeping in view the future requirements
while ensuring minimum extension / modification to SAP; we define
business cases, carry out TCO calculations, chalk out training
schedules, facilitate change management, define risk and mitigation
plan, cutover strategies etc
SAP Implementation & Enhancement Services
Our SAP Implementation Services include everything from
delivering solutions in implementation, integration of SAP across
applications, customization, and training, to implement change
management initiatives and data migration - all in an effort to
ensure a smooth go-live of SAP ERP.
Services include:
2

 Turnkey Implementation
Project Management
Functional Consulting
Technical Consulting (ABAP/4, Basis)
Prototype Development
Enhancement/Development Of Add On Applications
Data/Customization Migration
Documentation
Interfacing and Integration
Implementation Monitoring
Upgrade activities & Support maintenance
We enable companies to overcome the technical complexities and
high costs associated with upgrading and applying new Services to
their SAP environment.
We provide fast, accurate and comprehensive assessments with the
exceptional technical skills and expertise of our SAP-certified
professionals. Our upgrade offerings leverage SAP's latest SAP
Upgrade roadmap and utilize tools like PREPARE, R/3up, Upgrade
Assistant, etc. Based on our extensive experience in SAP upgrade
projects, we have developed a Best Practice surrounding this
service, which ultimately provides our customers with a smoother
upgrade process and accurate, predictable results and enables us to
accommodate every flavor of a customer's needs.
SAP Support & maintenance Services
Our offshore support solutions offer you a cost advantage over your
own support team.
Our SAP support services deliver the assistance you need to
optimize the performance of your software and manage your
business processes more effectively. You can adapt existing
solutions to changing market and business requirements, and take
advantage of the new innovations that will make your business
more successful.
3

We offer the following range of support services:

Help desk setup and management
SLA definition & management
24 x 7 production support
Performance analysis & optimization
Remote system support
SAP Business Intelligence (BI) Consulting Services
We are experts at managing multiple stakeholders across the
organization, cleansing and aggregating data from different systems
and creating Solutions that deliver the right results, on time and on
budget.
Strategic Assessments & Business Case Development
We investigate your business intelligence needs, perform fit / gap
analysis and determine where SAP BI can support and improve your
functional needs.
Business Intelligence Implementation
We provide full life cycle BI implementations of SAP BI products,
including SAP BW, BPS, SEM-CPM, SEM-BCS, and my SAP
SCM/APO.
Business Intelligence Enhancements
We help clients enhance existing BI solutions to provide more
visibility to critical business functions.
Business Intelligence Upgrades
Our teams are dedicated to providing the methodologies, tools,
solutions and resources your business needs to manage and deliver
SAP BI System upgrades.
Business Intelligence Application Outsourcing
We provide clients with BI application outsourcing services that
improve their business performance by maintaining, optimizing and
transforming their critical BI applications.
4

SAP Business One Implementation, Enhancement, Support &

Maintenance
Our Consultants work closely with you to understand your business
functions, processes and procedures, including your business
requirements and needs before implementing any solution. When
implementing a new system, selecting the right software is only the
beginning. The true work begins when the actual implementation
starts.
Our full range of implementation services are carefully aligned with
SAP Business One to include: strategic planning, defining business
requirements, software design, configuration, building, testing,
deployment, upgrades, maintenance, optimization and support.
Customer Relationship Management (CRM)
Our Customer relationship management (CRM) solutions team can
help transform the way a business interacts with its customers,
prospects, employees and partners, helping companies achieve
sustainable revenue growth and higher margins.
Our Core SAP CRM Team is capable to provide The Best solutions to
companies to refine the process which helps to become more
responsive to customer demands and external threats, as well as
enhance your business resilience.
SAP Net weaver Services
Our Net weaver competency a part of SAP Center of Excellence
(CoE) follows the methodologies and framework to provide the best
solutions involving re-usable Framework, components and tools.
The SAP Netweaver Team helps to provide best solutions to the
customers to reduce the turnaround time in the development which
significantly improves functional and technical processes.
Our Netweaver competency Team addresses the processes pointing
to People,Information, Process and applications of any size/volume
of business. Our Netweaver Team has the most expertise team to
address the gaps involved in Business and provide them the Best
Solution which reduces the Total time and cost .

Chapter 2
Sales and Distribution Overview

Chapter 3
Introduction to SAP SD Module
Sales & Distribution (SD) is one of the core and most-used modules
of SAP R/3 products beside Financial (FI), Controlling (CO), Material
Management (MM), and Production Planning (PP) modules.
The Sales & Distribution (SD) module consists of various
components also called sub-modules. Which are known as:

(SD-BF) Basic Functions and Master Data in SD Processing. (Also

subdivided in several components as: Pricing, Output etc.)
(SD-BF-PR) Pricing and Conditions
(SD-BF-EC) Extra Charge
(SD-BF-CM) Availability Check and Requirements in Sales and
Distribution Credit and Risk Management
(SD-BF-AS) Material Sorting
(SD-BF-OC) Output Determination
(SD-SLS) Sales
(SD-SLS-OA) Scheduling Agreements for Component Suppliers
(SD-SLS-OA) Customer Service Processing
(SD-FT) Foreign Trade/Customs
(SD-BIL) Billing
(SD-BIL-IV) Payment Card Processing
(CAS) Sales Support: Computer-Aided Selling
(SD-EDI) Electronic Data Interchange/IDoc Interface
(LE-SHP) Shipping
(LE-TRA) Transportation
(SD-IS-REP) Reports and Analyses

The main areas covered by this module and the sub modules are:
Pre-sales activities, including Inquiry and Quotation creation.
Sales Order processing, including Sales Order (SO) creation.
Shipping, including Outbound Delivery document creation.
Billing, including Billing document and invoice creation.
Sales & Distribution (SD) is a module highly integrated with other
SAP Modules as FI, CO, MM, PP & more. This can make SD a
complex module, so as part of this Introduction we will also try to

detail a normal sales process and how the activities integrate and
are covered by this module.

Pre-sales activities: It starts when a customer or a prospect

requests information by any source about a product or service
offered by the company. This request is processed through SAP
and the first integration we have is by the creation of a an
Inquiry Document or a Quotation Document. At this point of the
process we still havent effectively made a sale thats why it is
considered as a presale activity.

Sales Order processing: Our quotation document previously

created is send to our customer so they can make effective their
purchase procedure. At this point they may want to negotiate
payment terms, price, dates or any adjustments to the original
document created by us.
As soon as we receive a Purchase Order (PO) from our Customer we
create a Sales Order (SO) which makes reference to the previously
created Quotation Document. Now the scenario is adjusted based
on the business requirements. In some cases depending on the
business Sales Orders (SO) can be made without a previously
created quotation document as also in other scenario this can be a
requirement.

Inventory Sourcing: The product requirement from the Sales

Order at the required date needs to be available by one of the
following
options:
To fulfill the products requirement from an SO at the required
date, we can obtain them by one of these options:
o Taking from Available stock at warehouse. At this point the SD
module may trigger stock transfers between warehouses.
o Triggering a production order to produce the products inhouse.
o Triggering a purchasing order to purchase the products from
vendor.
10

Here is where the integration between Production Planning (PP) and

Material Management (MM) starts.
Shipping: When the product we sold is available at the
warehouse, the sales personnel can start shipping activities by
creating an outbound delivery document (Delivery Order/DO).
Now this Deliver Order (DO) can be created by referring to our
original Sales Order (SO). This will trigger the preparation of the
product by the personnel of the warehouse. If the Warehouse
Management (WM) module is integrated, a Deliver Order (DO)
can trigger a Transfer Order. When the products are ready to be
sent, the warehouse personnel will post the Goods Issue (GI)
transaction that refers to the DO. The GI transaction will reduce
the inventory level of products and then the warehouse
personnel sends the products to the customer by transportation
mode that has been determined in Sales Order (SO) document.
Billing: This whole process will be managed before the delivery
date specified in the Sales Order (SO) document. The finance
department will generate a billing document and send an invoice
form to the customer. The invoice will request the customer to
pay the products we have sent at the price condition and terms
of payment we have agreed in SO document.
As you can see integration is one of the fundamental aspects of this
module so a very good understanding of the process is required by
all SD Consultants. This document will continue with a more
detailed explanation between all these modules so dont forget to
stay tuned.

Enterprise Structure
As per SAP Help definition, it portrayal of an enterprise's hierarchy.
There are the following types of enterprise structure:

Logical enterprise structure, including the organizational units

required to manage the SAP System such as plant or cost center.
Social enterprise structure, description of the way in which an
enterprise is organized, in divisions or user departments. The HR
application component portrays the social structure of an enterprise
In other words, SAP enterprise structure is organizational structure
that represents an enterprise in SAP R/3 system. It consists of
11

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.
Organizational units may be assigned to a single module (such as a
sales organization assigned to Sales and Distribution (SD) module,
or to several modules (such as a plant assigned to Materials
Management (MM) and Production Planning (PP) module).
Following are some of the organizational units related to SAP
SALES & DISTRIBUTION module.
CLIENT

A client is an independent organizational unit.

A client is considered synonym for a group.
A client is self-contained technical unit.
General data & tables used for several organization structure are
stored at client level.
Client is positioned in the highest level in Enterprise Structure.
Several company code can be uniquely assigned to a client.
COMPANY CODE

A Company Code is a legal entity & independent accounting unit.

Balance Sheet & Profit & loss account are created at Company Code
level.
Company Code is organizational unit prepared by FI.
Several Company Code can be uniquely assigned to a Client.
Several Company Code under same client can have same chart of
accounts.
SALES ORGANIZATION

Sales Organization is an organizational unit of Logistics, which

groups the enterprise according to the requirement of Sales &
Distribution.
Sales Organization distributes goods & services.
Sales Organization is liable for sold products, responsible for the
customers right of recourse & negotiating sales condition.
12

One or more Sales Organization can be uniquely assigned to a

Company Code.
Sales Organization can be assigned to one or more plant. This
assignment is not unique, so several Sales Organizations can also
be assigned to one plant.
Each Sales Organization has its own master data, for eg customer &
material master data, as well as conditions, pricing & output type.
A Sales Organization is the highest level (after the Client) to which
sales figure are summed for SD with statistics currency.
Sales Organization can be used as selection criteria for listing of
sales document, as well as for creating delivery & billing work list.
Different output type can be defined for sales & billing document,
for each Sales Organization.
Sales Organization is also used to take regional, national,
international sub-division of the market into account.
DISTRIBUTION CHANNEL

A Distribution Channel is a mean through which saleable material or

services reach the customer.
A Distribution Channel represents the strategies to distribute goods
and / or services to the customers. Eg: wholesale, retail,
institutional, etc.
Distribution Channel can be assigned to one or more Sales
Organization.
Same customer can be served through one or more Distribution
Channel, within a Sales Organization.
Distribution Channel can be set as per company's marketing
strategies or internal organization.
Master data can vary (Customer & material Master data, Prices,
discounts / surcharge, output type, etc) for each Sales Organization
& Distribution Channel, i.e, within Distribution Channel master data
can be defined separately.
Master data created for one Distribution Channel can also be used in
other Distribution Channel.
Different sales document type can be defined for Distribution
Channel.
Sales Office can be assigned to Distribution Channel.
Items in a delivery & billing documents can belong to different
Distribution Channel.
Distribution Channel can be used as selection criteria for creating
lists.
13

DIVISION

Division represents a product line or grouping of materials or

services.
Division can be assigned to one or more sales organization.
Division can be assigned to one or more distribution channels.
Material always belongs to only one Division.
Master data can vary from Division to Division.
Different Division can share same master data, if shared master
data is created.
Sales Office can be assigned to Division .
In sales document type, if Item Division is not activated, it will
accept material from the Division at header level only & if material
at item level is from different Division from header level, the same
is not accepted.
Item in delivery or billing can belong to different Division.
Division can be used as selection criteria in sales document & also
for creating delivery work list.
Different output type can be used for printing sales document for
each Division.
SALES AREA

Sales Area is made up of combination of Sales Organization,

Distribution Channel & Division.
It defines the distribution channel a sales organization uses to sell
products from a certain division.
A Sales Area belongs to only one Company Code.
During the processing of SD documents, system accesses various
master data, according to Sales Area. The system also carries out
various checks concerning the validity of certain entries according to
Sales Area.
Sales document, delivery document & billing document is always
assigned to Sales Area.
Each SD document is assigned to exactly only one Sales Area. This
assignment cannot be changed.
Various analyses can be carried out within Sales Area. So,
Organization structure should be as simple as possible.
Sales Area is used for reporting & pricing.
The customer data record contains pages (views) with the data that
is specific to Sales Area.
14

PLANT & STORAGE LOCATION

In SD, a Plant represents the location from which material &

services are distributed & correspond to a distribution Centre which
is also known as Delivering Plant. The relevant stocks are kept
here.
In SD, the Plant has a central function:
At least one Plant is necessary in order to be able to use SD
module.
A Plant is uniquely assigned to a Company code.
Assignment between Sales organization & Plant is not unique.
Delivering Plant is important for determining shipping point.
For a Plant to deliver goods to the customers, it must be configured
appropriately as a delivering plant in SD customizing.
It is possible that a Plant in one company code may have
transaction with sales organization in another company code within
same client. This is known as *cross company sales.
Plant & Storage location are organizational units that can be used
by all logistic area in the system.
DELIVERING PLANT
For a plant to be a Delivering Plant, following are essential, i.e,

A plant is referred as delivering plant, when the said plant is

assigned to a combination of Sales Organization & Distribution
Channel.
Plant should be uniquely assigned to a company code.
Plant should also be assigned to sales organization & distribution
channel.
During sales process, the Delivering Plant is first used to verify
stock (availability check) & later to supply the goods the customer
has ordered.
Only if plant is a Delivering Plant, a shipping point can be assigned
to a plant. Material cannot be dispatched without a shipping point.
SHIPPING POINT

The Shipping Point is highest level organizational unit of shipping

that controls shipping activities.
Material can enter or leave the premises of an organization through
Shipping Point.
15

System determines Shipping Point on the bases of Delivering Plant,

Shipping Condition from Sold to Party & Loading Group from
material master.
The transaction code OVL3 is used to maintain the determination of
shipping point
Shipping Point can be changed manually, only if it is in close
proximity & relevant changes are permitted by the system in
customizing setting.
Each outbound delivery is processed by only one Shipping Point .
For example, loading ramp, mail depot, rail depot, group of
employees, etc.
Shipping Point is assigned to a plant.
Shipping Point is a physical place & should be near delivering plant.
Shipping Point can be assigned to more than one plant & a plant
can also have more than one shipping point. Assignment between
plant & shipping point is not unique.
WAREHOUSE
For efficient processing of goods receipt & goods issue, Warehouse
is made up of:

Warehouse number: The entire warehouse structure is managed

under one warehouse number.
Storage type: The different warehouse area, which differ with
respect to their organizational & technical features, are defined as
storage types.
Picking area: The picking area groups storage bins together in the
storage type.
Staging area: The staging area is an area in the warehouse where
the goods are stored immediately after unloading or shortly before
loading.
Doors: A door within a warehouse can be used both for inbound
delivery as well as outbound delivery of goods.
For Sales & Distribution, Lean Warehouses are applicable. This b'coz
lean warehouse have fixed bins as storage type.
BUSINESS AREA

Business Area represents an organizational unit, which can carry

out internal reporting.
A company code can be divided into multiple Business Areas.
16

A Business Area may also be shared by several company codes& in

such case, business area must have same description in all
company code.
Business Area can be used to prepare balance sheet & Profit & loss
statement not only for company code, but also for other internal
area (eg: division).
Determination of BUSINESS AREA takes placed based on following
rules:
Rule no 1:
Plant / Item Division
Rule no 2:
Sales Organization / Distribution Channel / Division, i.e Sales Area.
Rule no 3:
Sales Organization / Distribution Channel / Item Division.
SALES OFFICE

Sales Office is organizational unit responsible for sales &

distribution, within geographical area.
Sales Office establishes contact between company & customer.
Sales Office can be assigned to one or more sales area.
A Sales Office can be sub divided into several sales groups.
SALES GROUP

Sales Group is an organizational unit that carries out sales & is

responsible for the process internally.
Sales Group can be assigned to one or more sales office.
SALES PERSONS

A sales group consists of certain number of Sales Person.

A Sales Person is assigned to a sales office & sales group in the
sales employee record.
SAP R/3 system can represent a complex enterprise structure. Its
flexibility can integrate the structure of an enterprise by linking its
17

organizational unit. Enterprise structure design is a fundamental

process in a SAP implementation project. The design is mainly
determined by the business scenarios performed in an enterprise.
Once the design is determined, it will affect many things such as
how to perform a transaction and generate reports on SAP system.
Although its possible, it requires great effort to change the
enterprise structure. So , we must ensure that the enterprise
structure designed in the SAP implementation project can
accommodate all business scenarios and enterprises requirements
for current and future situation.

Chapter 4
Creating Sales Order via SAP Netweaver
Purpose
This session will give the basic step to create a Sales Order.
18

Overview
Transaction VA01: creating a Sales Order from the beginning.
Sales order data in first screen: Document type, Sales organization,
Distribution Channel, Division.
Sales order data in second screen: Ship to party, Sold to party,
Header and Item data.
VA01
1: Go to Transaction code VA01 to create the Sales Order
Or navigate in menu [Logistics -> Sales and Distribution -> Sales > Order ->Create ]
Here you have to fill the obligatory fields: Order type, Sales
Organization, Distribution Channel and Division.

2: Choose document type by F4 search in field Order Type. A

pop-up window will open with all available document types.
Double click to select one.

19

See below a list including all the default SAP Document types in
Sales:
Default document types :
CR

Credit Memo

GK

Master Contract

KA

Consignment Pick-up

KB

Consignment fill-up

KE

Consignment issue

FD

Delivery free of charge

CQ

Quantity contract

SD

Subsequent Del. Free of charge

KR

Consignment returns

DR

Debit memo request

PV

Item proposal
20

Default document types :

RE

Returns

RK

Invoice correction request

RZ

Returns scheduling agreement

SO

Rush order

OR

Standard Order

Select a Customer and enter some text in the Customer PO

Number field and either hit the return key or the Green check mark
button. This will ensure that SAP will validate the data you have
entered.
Sales
Organizatio
n:

Division:

Dist.
Channel:

Sales
Office:

Sales
Group:

organizational
unit within
Logistics.
Represents a
selling unit as
a legal entity.

Broad
product
range /
sales
structure.
Can be
assigned to
more than
one sales
organizatio
n

determine
s how
materials
or
services
are sold
and how
they are
distributed

Geographic
al aspects.
Territory or
regional.
Can be
assigned to
multiple
sales areas.

Employee
s of a
Sales
office can
be
assigned
to sales
groups
defined
for each
division or
distributio
n channel.
Assigned
to Sales
offices.

to
customers
, for
example,
retail,
wholesale,
selfcollection

3: VA02 second screen

Fill the Sold-to-party field. Ship to party will be filled automatically.
Insert a PO Number. Press ENTER.
21

In Sales Item, insert the Material and Item quantity.

22

See below the difference of Ship to party and Sold to party:

Sold to Party

Ship to Party

1 or more for ship to party.

A person or company that places
an order for goods or
services.

A person or company that

receives goods.
May not necessarily be the soldto party, the bill-to party, or the
payer.

4: By default SAP automatically proposes a Requested

Delivery date. This data is retrieved from the lead time
configuration in the Sales Order.
You can change the Requested Delivery Date before you enter the
line items.
5. In VA01 you can also include Header and Item data:

23

5.1 Header data. Main menu Goto>

Header

5.2 Header data. Main menu Goto>Item

24

After fill the Header and Item data, go back to main screen using
OK button
6: Double click on save button to finish the order. You will
see the saved order number at the bottom.

Go to VA02 to edit this Sales Order and VA03 to Display and Edit
the Sales Order
25

26

Chapter 5
Sales Order Creation via SAP Web Dynpro
Step 1 Create a Web Dynpro Component
Create a WebDynpro component with the windows name
SO_CREATE.

Step 2 Create nodes in the Component Controller

Now double click the Component Controller and navigate to the
Context Tab. Create four Nodes under that as shown below. In this
demo application only a few parameters of the
BAPI_SALESORDER_CREATEFROMDAT2 has been used. Incase real
time scenarios one might require to use all the parameters. Hence
there would be a need to create additional nodes in the Component
Controller.

27

28

Step 3 Create a methods to create sales order

The source code for the method is given below,

29

30

31

Step 4 Creating Views

Create a view named MAIN_VIEW and map the all node from the
component controller to it.

Now design the layout as shown below. Create 4 Groups one for
each node and add a button named CREATE to it.

Screen Development:
Screens are divided into four parts1. Initial Screen.
32

2. Overview Screen.
3. Header Data Screen.
4. Item Data Screen
Initial Screen:
a. In this screenwe are providing the basic information for sales
order creation like Order Type, Sales Organization, Distribution
Channel, Division, Sales Office, and Sales group.

Overview Screen:
a. In Overview screen we are providing brief header and item
details for sales order.
b. In this screen there are some tabs also created.

33

Header Data Screen:

a. In this screen we are providing header data related to sales
order. For sales orderheader data will store in SAP Table VBAK.
b. Header Data screen having following Tabs:
1. Sales
2. Shipping
3. Billing Document
4. Payment cards
5. Accounting
6. Conditions
7. Account Assignment
34

8. Partners
9. Texts
10. Order Data
11. Status
12. Additional Data A
13. Additional data B

35

36

37

38

Item Data Screen:

39

a. In this screen we are providing sales order item data which will
store in SAP Table VBAP.
b. Item Data Screen having following Tabs:
1. Sales A
2. Sales B

40

3. Shipping
4. Billing Document
5. Condition
6. Account Assignment
7. Schedule Lines
8. Partners
9. Texts
10. Order data
11. Status
12. Structure
13. Additional Data A
14. Additional Data B

41

Create an ACTION named CREATE_SALES_ORD for the CREATE button.

42

The implementation for the ONACTIONCREATE_SALES_ORD method

is given below,

Double click on save button to finish the order. You will see the
saved order number at the bottom.

43

Summary
A sales order is an internal document of the company, meaning it is
generated by the company itself. A sales order should record the
customer's originating purchase order which is an external
document. Rather than using the customer's purchase order
document, an internal sales order form allows the internal audit
control of completeness to be monitored as a sequential sales order
number can be used by the company for its sales order documents.
The customer's PO is the originating document which triggers the
creation of the sales order. A sales order, being an internal
document, can therefore contain many customer purchase orders
under it. In a manufacturing environment, a sales order can be
converted into a work order to show that work is about to begin to
manufacture, build or engineer the products the customer wants.
It is an order issued by a business to a customer. A sales
order may be for products and/or services. Given the wide variety
of businesses, this means that the orders can be fulfilled in several
ways. Broadly, the fulfillment modes, based on the relationship
between the order receipt and production, are as follows:

Digital copy - Where prices are digital and inventory is

maintained with a single digital master. Copies are made on
demand in real time and instantly delivered to customers.
Build to stock - Where products are built and stocked in
anticipation of demand. Most products for the consumer would
fall into this category
Build to order - Where products are built based on orders
received. This is most prevalent for custom parts where the
designs are known beforehand.
Configure-to-order - Where products are configured or
assembled to meet unique customer requirements e.g.
Computers
Engineer to order - Where some amount of product design work
is done after receiving the order
44

45