Professional Documents
Culture Documents
SD BBP
SD BBP
SUBMITTED BY
RELIANCE GLOBAL SERVICES PVT LTD
SD
BUSINESS BLUEPRINT SAMPLE SALES &
DISTRIBUTION
SD TEAM
PREPARED BY
REVIEWED BY
APPROVED BY
SIGN OFF BY
INDEX
1
Process Process Sub Process Sub Process Description
Number Description Number
SD 1.0 Enterprise SD 1.1
Sales organization
Structure
SD 1.2 Distribution channel
SD 1.3 Division
SD 2.5 Output
Sales Order
SD 3.0 Processing
SD 4.0 Shipping
2
SD 5.0 Billing
Complaints SD 6.1
SD 6.0 Processing Complaints
3
Business Process Overview
Virgo Sales & Marketing has focused on manufacture and sales of automated and manually operated
quarter turn valves. Over the years Virgo has acquired several prestigious international quality
certifications and approvals from major Oil and Engineering companies, becoming one of the leaders
in the Ball Valve industry.
A. Marketing, through Product Managers who take decision on pricing, business planning and
profitability of sales of steel materials in various sales regions.
B. Sales, viz., Outside sales through Sales Managers and Technical Service Managers based at various
locations and responsible to book orders and manage customer relationships. Inside Sales through
Sales-coordinators, who interface with Customers and respective mills
C. Planning, through Planning Managers responsible to monitor the load on aggregates in respective
Mills, and
E. Planning logistics.
Geographically, VIRGO Valves is responsible for sale of different products of valves to International
customers like Far East 1 and 2, Europe, Middle East and USA.
Director(Sales)
Sales Coordinators
SALES
4
Virgo Organizational Chart
5
SAP System Functions (Process Flow)
To facilitate sales transactions in SAP, it is mandatory to define following sales organizational units for present
business scenario. Each selling transaction is processed within a sales organization. Subsequently new sales
organization can be added by customizing transactions in SAP Configuration.
01 Direct Sales= Sale transaction that leads to Sales to Direct Sales Customers.
D2 Distributors (PUNE)
D4 Distributors (BANGALORE)
You use this menu item to define distribution channels which have common master data. The allocation is
valid within a sales organization.
6
Common Distribution Channel In SAP Description
SD 1.3 DIVISIONS
Main product categories are represented as Division. Following Divisions are required to define in
system.
7
SD 1.4 SALES OFFICE
From Virgo Sales & marketing perspective, Sales Regions are configured as Sales Offices in SAP.
PVQ1 PUNE
PVQ2 BANGALORE
Sales area is a combination of Sales organization - Distribution channel - Division. Following sales area
combinations are defined.
D1 11
VS01
VS01 D1 22
VS01 D1 33
VS01 D2 11
VS01 D2 22
VS01 D2 33
VS02 D3 44
VS02 D3 55
VS02 D3 66
VS02 D4 44
VS02 D4 55
VS02 D4 66
8
SD 1.6 SHIPPING POINT
Shipping point is an organizational unit where deliveries are planned and executed. A delivery is always
carried out by one shipping point only. It is proposed to use one shipping point for all company codes.
Company
Shipping Point Delivering Plant
Code
9
Table SALES AREA
As explained in above table SALES AREA is only for Virgo valves manufacturing Unit. Similar sales area will be
created for all sales organizations.
Following diagram shows sales area combination in Virgo Sales Organization + Distribution Channel + Divisions.
Similar Sales area combinations can be formed for other sales organizations (other company codes).
Sales Area
Distribution
Division
Channel
Plant MP01 (MM) Plant VI01 (MM)
CS VALVES
DISTRIBUTORS
INCONALS
SHP1 SHP2
10
SD 2.0: Master Data
The customer master record is the basis for all sales transactions as well as deliveries and payments. It
represents the data relevant to the entity being dealt with.
Here, we maintain Customer related information for all the customers of VIRGO VALVES in the following fields.
SAP allows only one address per customer record. The standard address in group will be maintained as Sold-
to-Party customer in SAP and the other addresses associated with the account will be defined as additional
partners in the Ship to, Bill to or Payer account groups and linked to the customer record with the standard
address through partner functions. SAP allows a 10 –digit number for the customer master record, which
means potentially a billion customer records can be created with the same starting digit.
VIRGO will have external number range for all account groups. The total number of customer records (including
different ship to, bill to and payers’) will be based on VIRGO’s estimate of their customer base and accordingly
a number range will be assigned for the customer master records.
11
• The material master data is used by the system to represent the data pertinent to the products
your company is selling or producing.
• It is configured much the same way as the customer master record with different views.
Maintain Material related information for all the materials of VIRGO VALVES ltd. in the following fields
1. Industry Sector
2. Material Types
3. Plants
4. Sales Organization
5. Distribution Channel
The material master will be maintained centrally for SD and MM purposes using transaction MM01.
Material Numbers will be created externally for all products and services.
A product hierarchy will be assigned to each material. Product hierarchy will be created based on the products
or service group.
Scenario: Material Master Creation Transaction: MM01 Organizational Level Plant Sales Organization
Distribution Level
Base Unit of Measure, Material Group, Material Group Packaging Material, Sales Organization, Delivering Plant,
Cash Discount Option, Product Hierarchy, Material Pricing Group, Account Assignment Group, Transportation
Group &Loading Group, Foreign Trade Export, Export / Import Group, Country of Origin, Region of Origin,
Exemption Certificate, Sales Text, Long Text& Short Text.
Customer Material Info Records also known as CMIRs are used to store customer specific information about a
material such as Customer’s number and name of a material, customer’s preference on material specific
shipping like delivering plant, under delivery and over delivery allowed, complete/partial delivery preference
etc.
12
SD 2.4 Pricing Procedure
Condition technique is a method by which system determines the values from the information stored in
condition record during sales order processing.
• Pricing Procedure
• Condition Table
In a condition table, you define the combination of fields for which you can create condition records.
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.
13
MAINTAIN ACCESS SEQUENCE (V/07)
The access sequence is a search strategy, which the SAP System uses to search for condition records valid for
a condition type.
VF00 Freight
MWST Output Tax
14
CONDITION TECHNIQUE:
CONDITION TABLE
CONDITION TYPE
PRICING PROCEDURE
It is one of the elements to determine the pricing procedure. We specify the customer determination
procedure in the customer master record for each sales area.
Cust. Pricing
Procedure DESC
1 Standard
It is also one of the elements to determine the pricing procedure. We specify the document pricing procedure
for each sales document type.
Cust. Pricing
Procedure DESC
A Standard
15
SD 2.5 OUTPUT DETERMINATION
Outputs are an important media for communicating with Business Partners or with your own employees in
sales processing. Sales and distribution output can be sent both electronically and by mail. Output control
which is dependent on various criteria allows output to be processed and sent subject to certain conditions
and restrictions.
• Print parameters
You can use the condition technique to propose output in SD documents. This can be done according to criteria
which you freely define. There are however some limitations to the condition technique in picking list. For
more information, see the chapter on output determination for picking lists in the Implementation Guide.
In this case, we can control output processing individually for each output recipient.
16
SD 2.6 ROUTE
For each and every line item in the Sales Order Route can be determined automatically. The material can
be transported from source to destination by using different mode of transports with different shipment
types. Route can be determined for a line item in the Sales Order.
Mode of transport:-
Key Description
10 Road
20 Rail
Key Description
30 Truck
40 Train
Key Description
50 Railway Station
17
SD 2.6.2 ROUTE DETERMINATION
Define Transportation Zone: Transportation Zone represents Ship to Party. System uses Transportation
Zone as a one of the factor to determine the route for a line item in the Sales Order.
Zone Description
0000000001 North Zone
0000000002 South Zone
System automatically determine route for a line item in the Sales Order by taking 4 factors into
consideration.
a. Country of Departure Zone
b. Country of Destination Zone
c. Shipping Conditions (From Sales Document Header)
d. Transportation Group (From Material Master)
The sales cycle in SAP starts with entering a sales order. The sales order contains customer details like sold-to
party, ship-to party, address etc., material details like material number and quantity, and a delivery schedule.
The delivery schedule can be changed before the delivery document is created – once the delivery document
is created, Shipping will start working on delivering the product.
Sales orders will be created using the SAP transaction code VA01.
When entering sales orders, it is important to distinguish between order types. VIRGO will use the following
order types.
1. VIRGO Regular sales orders: These include the regular orders, special orders and will call orders.
(SAP Standard Order including third party orders)
2. Credit memo requests
18
3. Debit memo requests
4. Returns order: This includes normal customer returns with reference
5. Free of Charge delivery will be a separate order type. The pricing will be automatically adjusted
for free delivery.
6. Rush Order process with automatic delivery creation as standard.
7. Consignment process.
• Internal number assignment (The SAP System automatically assigns a consecutive number from the defined
number range.)
• External number assignment (You specify a number from the external number range.)
19
Virgo Valves Limited is following the internal number ranges only.
When a sales order is being created, after the user enters a material number and quantity, SAP performs the
following functions:
For online orders, if the document value exceeds a certain preset limit for High and Medium Risk
Customers, a credit block should be placed on the order. For orders other than web orders, this block
should not be applied. For this reason, a separate internet order type has been envisaged for Regular and
Custom order types.
When creating a sales order, SAP performs an availability check. Availability check will behave differently for
Make-to-Stock items. Whether a material is MTS is determined by the planning strategy assigned to the
material in the MRP3 view on the material master.
For VIRGO, Daily requirements type will be used for availability check.
In VIRGO, have Samples sales processing. For that normal order type will be used. Some line items can be
sample. In case the line item is a sample being offered at no charge, CSA will manually insert a 100% discount
in the pricing procedure.
20
SD 3.6 DEBIT MEMO REQUEST AND CREDIT MEMO REQUEST PROCESSING-
The scenario in SAP consists of the following steps:
• A Sales Order (type Debit Memo or Credit Memo request) is created and a billing block is assigned
automatically – by Sales
• The billing block is removed - by Sales
• The billing is created – by Finance.
Standard Debit Memo Request (DR) and Credit Memo request (CR) will be used. These requests can be created
with reference to an existing sales order/ Invoice or without any document reference. The requests upon
creation will be blocked automatically for billing. Upon release of the block, respective Debit Memo or Credit
Memo can be created.
SD 4.0 SHIPPING
Shipping of stock to a customer starts with the creation of the delivery document, and ends with a Post Goods
Issue on the delivery document.
Standard SAP process will be followed for delivery creation in VIRGO. The sales order should be free of all
delivery blocks and credit check blocks before the delivery can be created. The requested delivery date in the
sales order will be defaulted to ‘order entry date’ which will be the system date.
All items will be picking relevant and packing relevant. Individual transfer orders will be created for items based
on the storage location/storage type.
All these separate Transfer orders will be combined and packed. Packing will be done with packing stations
defined in the system.
Number Range
S/No Doc with Descriptions From No. To No.
1 Delivery 80000000 83999999
21
SD 5.1 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.
Creation of:
• Invoices based on deliveries or services
• Request for Down payment
• Issue credit and debit memos
• Pro forma invoices
• Cancel billing transactions
• Issue rebates
• Transfer billing data to Financial Accounting (FI)
For VIRGO, the SAP standard billing document type F1 will be used for Order related billing and F2 will be
used for Delivery related billing.
Majority of VIRGO processes require physical delivery of material and hence delivery related billing will be
used for major part of business. In case a down payment is to be secured from a customer before delivering
the goods, order related billing will be done.
Pricing will be recalculated during billing to take into account any quantity variance during the picking
process.
Number Range
S/No Invoice doc with Descriptions From No. To No.
1 Invoices (F1/F2) 90000000 94999999
2 Credit Memos(G2) 90000000 94999999
3 Cancellation Invoice(S1/S3) 90000000 94999999
4 Debit memos( L2 ) 90000000 94999999
F1 is used for order related billing and F2 is used for delivery related billing.
22
SD: 6.1CUSTOMER COMPLAINTS
Scenario
Following is the list of different scenarios which can be part of this customer complaint process:
S. No. Description
Scenario 1. If customer returns the goods
Scenario 2. If customer wants refund for the amount
Scenario 3. If customer wants replacement
Scenario 4. The customer does not send the goods back
Scenario 5. For damaged replacement
Following is the list of different documents which can be part of handling customer complaints:
You can create the returns order in one of the following ways:
23
• with reference to an existing Invoice
• with reference to an existing Contracts
• with reference to an existing Contract Release Orders
It may be worthwhile ensuring the returns order reason was entered on the sales document. Thus,
it may be necessary to add this in an incompletion procedure for returns order.
It is advisable to indicate a shipping condition that is specifically used for returns order. This is
useful when running delivery due list (VL04).
24