You are on page 1of 60

PLP TRAINEE 23

 Enterprise Structure  Inquiry > Quotation > Sales Order Cycle


 Material  Split Delivery

 Business Partner  Collective Billing

 Pricing

Guided By  MAHESH NILE


VARTIKA AGRAWAL  ROHAN GAJARE
CAPGEMINI 1
Enterprise Structure
Material Creation
Business Partner
Pricing Procedure
OBJECTIVES Create an Inquiry
Quotation
Sales Order Cycle
Split Delivery
Collective Billing Document

CAPGEMINI 2
CASE 1
Creating Enterprises Structure and assignments , Business Partner,
Material, Pricing Procedure.

CASE 2

Create an Inquiry > Quotation > Sales Order Cycle

(Customized Order type , Customized Item Category)

CASE 3

Create Sales Order with 20 QTYs > Split Delivery into 10 QTY each >
Create a collective Billing Document

CAPGEMINI 3
CASE 1

Creating Enterprises Structure and


assignments , Business Partner, Material,
Pricing Procedure.

CAPGEMINI 4
Enterprise
Structure

CAPGEMINI 5
The enterprise structure represents
the business structure in the real
world.

Enterprise You can map various organizational


units to enterprise structure as per
structure  the requirement like

Sales Organization, Distribution


channel, division, company code,
Sales office, Shipping Point, Loading
point, etc.

CAPGEMINI 6
Enterprise Structure
Path - SPRO -> IMG -> Enterprise Structure ->Definition ->Sales & Distribution ->Define Sales Org

CAPGEMINI 7
Define Sales Organization
Sales Organization - 2767 Sales Organization name – Asus India LTD.

CAPGEMINI 8
Distribution Channel
Path -> SPRO -> IMG -> Enterprise Structure->Definition ->Sales & Distribution ->Define Distribution
Channel

Distribution Channel – D8

CAPGEMINI 9
Division
Path -> SPRO -> IMG -> Enterprise Structure ->Definition -> Logistics General-> Define Division

Division - DA

CAPGEMINI 10
Sales Office
Path -> SPRO -> IMG -> Enterprise Structure ->Definition ->Sales & Distribution ->Define Sales Office

Sales Office - NASK

CAPGEMINI 11
Sales Group
Path -> SPRO -> IMG -> Enterprise Structure ->Definition ->Sales & Distribution ->Define Sales group

Sales Group - NSG

CAPGEMINI 12
Assign Sales Organization to company code
Path -> SPRO -> IMG -> Enterprise Structure ->Assignment ->Sales & Distribution ->Assign Sales Org to
Company code

CAPGEMINI 13
Assign Distribution Channel To Sales Organization
Path -> SPRO -> IMG -> Enterprise Structure ->Assignment ->Sales & Distribution ->Assign Dist.ch to
Sales Org

CAPGEMINI 14
Assign Division To Sales Organization
Path -> SPRO -> IMG -> Enterprise Structure ->Assignment ->Sales & Distribution ->Assign Div. to Sales
Org.

CAPGEMINI 15
Set Up Sales Area
Menu Path -> SPRO -> IMG -> Enterprise Structure ->Assignment ->Sales & Distribution ->Setup Sales Area

Assign Sales Org.+ Distribution Channel + Division

CAPGEMINI 16
Assign Sales Office to Sales Area
Path: – SPRO > IMG > Enterprise Structure > Assignment > Sales & Distribution > Assign sales office to
sales area.

CAPGEMINI 17
Assign Sales Group to Sales Office
Path: – SPRO > IMG> Enterprise Structure > Assignment > Sales & Distribution > Assign sales group to
sales office.

CAPGEMINI 18
Assign Sales organization + distribution channel + Plant
Path: – SPRO > >Enterprise Structure > Assignment > Sales & Distribution > Assign sales org, Dist. Ch to
Plant

CAPGEMINI 19
Maintain Storage location
Path: – SPRO > >Enterprise Structure > Definition > Maintain Storage location
Storage Location- ASUS

CAPGEMINI 20
Material Creation
 Type of Material

 FERT for finish goods

 T codes for Material Creations

 Material create- MM01

 Material change- MM02

 Material display- MM03

CAPGEMINI 21
Material Creation
Path- SAP menu- logistics materials- material management – material master- material- create – MM01

Material Creation- MM01

CAPGEMINI 22
Select View

CAPGEMINI 23
Created Material
Material Number - 241679 Transaction code – MM03

CAPGEMINI 24
Material Stock

Transaction code for Stock Overview - MMBE

CAPGEMINI 25
Business Partner
 Business partners are parties in which your company has a
business interest. You can create and manage your business
partners centrally for different business transactions, and
reflect the different roles they play, such as sold-to party
and ship-to party.

 A business partner can be any of the following:

 Business partner is a legal entity representing self / an


entity.

 Bp can be created for a group, organization, person

CAPGEMINI 26
Business Partner Creation
 Transaction Code for Business Partner Creation - BP

CAPGEMINI 27
Customer role
 BP Role- FLCU01 Customer
 Customer Group- 02 - Retail

CAPGEMINI 28
FI customer
 BP Role – FLCU00 FI Customer

 Company Code- 1978 , Reconciliation account- 140000

CAPGEMINI 29
What is the need of pricing
Pricing Procedure procedure?

 Pricing procedure is a way to


determine prices in purchasing
documents.

 Pricing procedure gives functionality


to assign different calculation types
for different requirements.

 Pricing procedure used to determine


all conditions into one procedure.

CAPGEMINI 30
The primary elements of pricing condition technique are:

 Pricing Condition Table

 Access Sequence

 Pricing Condition Type

 Pricing Procedure Determination

 Condition Records

CAPGEMINI 31
Condition table

 Transaction code – VOK0

 A condition table defines the combination of


fields (the key) that identifies an individual
condition record. A condition record is how the
system stores the specific condition data that you
enter in the system as condition records

 Table number – 646 ( Sales Org. of Order, Ship- to


party, Material, Customer)

CAPGEMINI 32
Access Sequence

 An access sequence is a search


strategy that the system uses to find
valid data for a particular condition
type. It determines the sequence in
which the system searches for data.

 Access Sequence -ASUS

CAPGEMINI 33
Condition type

 Condition type basically used for


discount, Basic Price, rebates. So we
have different-2 condition type for
different-2 use. In condition type we
have access sequence. Access sequence is
assigned to condition tables.

 Standard- PR00

 Condition Type - ASUS

CAPGEMINI 34
Pricing Procedure
 Path: IMG  Sales and Distribution  Basic Functions  Pricing  Pricing Control  Define
and assign Pricing Procedure.
 T-Code: V/08
Pricing procedure is a way to
determine prices in purchasing
documents. Pricing procedure gives
functionality to assign different
calculation types for different
requirements.
 Standard Procedure- RVAA01

 Pricing procedure – ASUS01


35
CAPGEMINI
In Pricing procedure we define condition type

Condition Type- ASUS Standard Type – PR00

CAPGEMINI 36
Condition Record
Path: Easy Access Logistics  Sales and Distribution  Master Data  Conditions  Select using
Condition Type  Create

 A condition record is defined


as how system stores the specific
condition.
 T-Code: VK11

CAPGEMINI 37
Pricing Procedure Determination

Transaction code - OVKK

Pricing Procedure is determined using:

 The Sales Area (sales organization,


distribution channel, and division)
 The Document Pricing Procedure
(DoPr) code from the document type
(A)
 The Customer Pricing Procedure
(CuPP) code from the customer master
record (1)
CAPGEMINI 38
Create an Inquiry
>Quotation >Sales Order
Cycle
CASE 2
(Customized Order type ,
Customized Item Category)

CAPGEMINI 39
INQUIRY
 The inquiry is a sales document which records the information about the inquiries
received from the customer.

 Customer enquiries about a particular product availability, if available how much it


costs, and whether the product will be available on a particular date or not.

 It is nothing but a request from the customer to the sales organization. Whenever a
customer requests for information about a product then create an inquiry sales
document in SAP.

CAPGEMINI 40
Quotation

A quotation is also a sales document which is created after the


creation of the inquiry document as a response to the customer
request.

Based on Inquiry we can create Quotation.

A Quotation is a document, in which a seller offers goods or


services at a stated price, under specified conditions to a buyer.
CAPGEMINI 41
Sales Order Cycle

CAPGEMINI 42
SALES DOCUMENT

 A sales order is a document generated by the

seller specifying the details about the product or

services ordered by the customer. Along with the

product and service details, sales order consists

of price, quantity, terms, and conditions etc

CAPGEMINI 43
Item Category

 An item category defines how a


line item behaves in sales
transaction.

 SAP Uses Item category to process


a material differently in each sales
document type.

CAPGEMINI 44
Customized Item Category

 Transaction Code VOV7

 Standard type – TAN

 Sales Order Type - AUN

CAPGEMINI 45
Assign Item Categories to Sales Order type

 Transaction Code VOV4

 Standard type – TAN

 Sales Order Type - AUN

CAPGEMINI 46
Inquiry

 Transaction Code VOV8

 Standard type – IN

 Sales Order Type - AIN

CAPGEMINI 47
Quotation

 Transaction Code VOV7

 Standard type – QT

 Sales Order Type - AQT

CAPGEMINI 48
Sales document type

 Transaction Code VOV7

 Standard type – OR

 Sales Order Type - OA

CAPGEMINI 49
Create Inquiry

 Transaction Code – VA11, VA12,VA13

CAPGEMINI 50
Create Quotation

 Transaction Code – VA21, VA22,VA23 Create Quotation with reference to Inquiry

CAPGEMINI 51
Create Standard Order

 Transaction Code – VA01, VA02,VA03 Create Standard Order with reference to Quotation

CAPGEMINI 52
Standard Order
Sales Order number 5716 Order Quantity – 20 Item category – AUN Item Category Standard - TAN

CAPGEMINI 53
CASE 3

Create Sales Order with 20 QTYs > Split


Delivery into 10 QTY each > Create a
collective Billing Document

CAPGEMINI 54
SPLIT DELIVERY

 Split Delivery is a method used when a larger


quantity of goods is requested on a purchase
order to secure a lower price, but the delivery
itself is split into smaller quantities and
spread out over different dates to control
inventory investment, save storage space.

CAPGEMINI 55
COLLECTIVE BILLING

 The system combines documents with the same


customer number, proposal billing type, and sales
organization, and attempts to include them all in the
same billing document. If the preconditions are met,
then a single invoice is created for the deliveries
and/or orders.

CAPGEMINI 56
COLLECTIVE BILLING

Create Collective Billing Transaction code -VF04

CAPGEMINI 57
Split delivery and collective billing Document flow

Document flow of Standard Order 5716

CAPGEMINI 58
Billing output

 Billing output for collective billing

CAPGEMINI 59
Thank you

CAPGEMINI 60

You might also like