KT Review Presentation

Content
 Introduction (Working, SAP, Modules, Sales Activities and Enterprise structure )
 Master Data in Sales & Distribution
 Partner funtion
 Pricing Procedure
 Third Party Sales
 Output Types
 Idoc (Intermediate Document)
 Route
 Consignment Process
 5 Business models of Tetra Pak.
 References
 Material Management (MM) Sales & Distribution (SD)
1. Product Request (PR)
2. Inquiry
3. Quotation
4. Receive Quotation & Compare
5. Purchase Order (PO)
6. Sales Order (SO) with Delivery Date

7. Create Delivery & Good Issue (GI)

8. Invoice / Billing
9. Goods Receipt (GR)
10. Vendor Invoice / Invoice Receipt
11. Payment Release 12. Payment Received
Introduction
 SAP ERP is an enterprise resource planning software developed by the German company SAP SE.
 SAP SD (Sales and Distribution) is one of the significant modules of SAP ERP. It is used to store the
customer and product data of an organization. SAP SD helps to manage the shipping, billing, selling and
transportation of products and services of a company.
 SAP Modules
Material Management (MM)
Sales and Distribution (SD)
Production Planning (PP)
Human Resource Management (HRM)
Financial Accounting.
 Sales Activities
*Pre sales Activity: >> Inquiry >> Quotation
*Sales Activity: >> Order >> Delivery >> Invoice >> Payment
Post sales Activity: >> Warranty >> Relation Management
Enterprise Structure (SAP SD Key Data Structure )
 Company Code (Smallest unit to represent a Company and Unique) (Multi)
 Sales Organization:
Responsible for all activities & Services that happens in company.
Used to distribute product & Services.
 Distribution Channels (Channels/Ways through which goods are transferred to customer)
 Division (Groups of ranges of Products Example: Different Section in electronics shop).
 Sales Area = Sales Organization + Distribution Channels + Division
 Sales Office: (Organizational Unit represent as Branch, Consist of Salesperson which perform
direct/indirect sales)
 Sales Groups: (Multiple Salesperson working for various purposes, Multiple Sales Groups can be assigned
to single sales Office)
 Plant (Warehouse)
 Shipping point: Entity that ships the product to Customer.
Master data in Sales & Distribution
 Data about business Entities (in context of business transaction) is termed as Master data (MD).
 These are Classified as:
>> Customer MD
>> Material MD
>> Pricing Condition Records
 Customer Master Data:- data required to conduct business relationship with your customer.
General MD : Personal Info related to Business (like Name, Phone, Address etc).
Company Code MD: Smallest Unit >> Contain info such as Payment Terms/Tax info/Payments methods.
Sales Area MD: Sales related information about a specific region or area.
Tractional Code: XD01/XD02/XD03 – CRETAE/CHANGE/DISPLAY.
 Material Master Data:- Master data about the material & Services of Customer.
Minimum Order Quantity
Minimum Delivery Quantity.
Customer Material Information Records (CMIR):
(Information on material that applies for Specific Customer for buying Specific Material)
T-codes: MM01/MM02/MM03 - CRETAE/CHANGE/DISPLAY.
Partner Funtion
 Types of People whom the Business are carried out are termed as Partner Functions.
>> Ship to Party: the customer to whom the goods is Shipped to. (Address)
>> Sold to Party: the customer to whom we are selling the goods (Someone whose buying)
>> Bill to party: to whom we will create an invoice to.
>> Payer: One who will Pay the amount
All the four can be same or can be different
 T-code: VOPAN
Example: If I order online something for my friend (Say by Amazon):
Then, sold to Party:- Me
Ship to party:- friends House Address
Bill to Party :- TCS (Suppose tcs will be reimburse the amount)
Payer :- Me
Pricing Procedure
 Pricing in Sales and Distribution is used to define the calculation of prices for external vendors or
customers and cost.
 This information is stored as the master data in the form of Condition records.
 Example:
 Consider a case when customer orders specific quantity of a product on a particular day. Various
factors like customer, product, order quantity and date tells the final price to that customer.
 This information is stored in the system as master data in the form of condition records.
 There are various pricing elements like prices, surcharges, discounts, and taxes, which are
defined in SAP system as condition types.
 To manage pricing information for a pricing element in a system, you have to create condition
records.
 Pricing Controls:
A.> Condition Records. B.> Condition Tables. C.> Access Sequence. D.> Condition Types.
Condition Records
 A condition record is defined as how system stores the specific condition.
 Example: Entering the price of product or to Specify the discount for privileged customer.
 Pricing Condition Master Data contains:
Base price of product
Discount
Surplus charge
Tax information
 T code: VK11/VK12/VK13 – Create/change/display
Condition Table:
A Condition table is defined as a combination of keys to identify an individual condition record.
T-code: v/04
Access Sequence
 This is the Search strategy which is used by the system to find valid data for particular condition
type
 It tell about the order in which a system searches for data.
 Assess sequence is defined for each condition types where condition records are created.
 We can also customize the access sequence.
 T-code: ovko
Condition Type:
Condition type is defined as specific features of daily pricing activities in a SAP system.
Using the condition type, we can also put different condition types for each pricing, discounts on
goods, tax and surcharge that occurs in business transactions.
T-code: V/06
InShort:
Condition record >> Condition tables (key combination) >> condition type (OrderBy Access Sequence)
Third Party Sales

 Make to Order: (Specialized Product)

Company
 Sales order initiates the demand for production
 Example: Design material for tetra Pak
 Specialized product shape or Size
 Specialized Design / Printing

 Make to Stock (Produced already based on demand Customer Vendor

forecast)
 Available in stocks in large quantity
 Example: Caps, straw, etc.
Output Types
 Output type is used to control how the output should be transmitted i.e. by printing, email, fax or EDI
(Electronic data interchange).
 This is mainly used for Acknowledgement to customer for conformation.
 Example of output types in sales and distribution processing are order conformation, invoice etc.
 All the output type are stored in the NASE Table. To see the configure output you can use transaction
code as ‘NACE’
 Output determination for Sales Document.
vv11/vv12/vv13 – create / change/ display
 Output determination for Delivery Document.
vv21/vv22/vv23 – create / change/ display
 Output determination for Billing Document.
vv31/vv32/vv33 – create / change/ display
IDoc (Intermediate Document)
 IDOC is simply a data container that is used to exchange information between two systems
 Create IDOC: WE30
 Idoc Structure:
 Control Record : Technical details like type information, partner funtion details etc.
 Data Record: Data that is send by the IDOC
 Status Record : Idoc status whether its received successfully or not.

SPRO (T-code)
 Transaction code SPRO is used configure the SAP System as per clients requirement.
 After executing SPRO transaction code, you will see IMG (Implementation Management
Guide) menu which you will find customization settings for all modules.
Route
 It is a fundamental basis to create and plan shipment in SAP system and also a basis
for selection of upcoming deliveries.
 Example: DE0109
 Where DE = departed country
 01 = shipping type
 09 = No. of days (up to which date the product will delivered.)
 Create Route: 0VTC
Consignment Process
 Consignments are known as products, which are owned by your company and are located at the
client location.
 Customer has to only pay for goods, which are removed from the stock and only for the quantity
taken.
 Consignment goods are stored by the customers at their warehouse.
 As the consignment stock is still a part of company’s valuable stock, so there is a need to manage
this in the system.
 Consignment stock management includes four key activities in the system, which are −
Creating a Consignment Fill-Up (Stock is fill up at warehouse).
Creating Consignment Issue (Stock issued from warehouse).
Creating a Consignment Pick-Up (Stock return to manufacturer).
Displaying Consignment Returns (Stock return from customer).
T-Code for creating Consignment: VA01
Business Models in Tetra Pak
 There are five business model which exist currently these are:
Buy & Sell
One Company
Direct Trading
Trolling
Trolling Export

 Sample Example of Y2Tk Flow table:

Buying Company Trading Company Supply Company

Market Company (MC) Tetra Pak Intern. (TPI) Converting Factory (CF)
 Buy & Sell:
 In the Buy & sell scenario, Tetra Pak operates in three different entities which are as MC, TPI and CF.
 This business model is used for domestic market as well as export.
 This Scenario is also known as 3 company.
One Company Scenario

 One company scenario, Tetra Pak operates as a unique entity (MC+CF).

 There is no involvement of third entity “TPI”. Both MC and CF should be in
same country and location.
 In this Scenario, there Buying company works as Trading company and Supply
company

Buying Company Trading Company Supply Company

Data NA NA
Direct Trading / 2 Company scenario
Trolling / 2 Company scenario
 In the Tolling scenario, Tetra Pak operates in two different entities one is MC
and another one is TPI+CF.
 Where CF is acting on the behalf of TPI for domestic or export.
 In the Tolling Export scenario, Tetra Pak operates in three different entities
(MC, TPI and CF).
Reference’s

 KT Session
 INDUCTION MANUAL-OFPM
 https://www.tutorialspoint.com/sap_sd/index.htm
Thank You